Patent Description:
<FIG> shows a multi-connectivity scenario. One terminal device is connected to one primary network device and at least one secondary network device (one secondary network device is used as an example in the figure). The primary network device and the at least one secondary network device are connected to a core network. A standard of the primary network device and a standard of the secondary network device may be the same or different. When the standards of the two network devices are different, for example, one is a long term evolution (Long Term Evolution, LTE for short) base station, and the other is a new radio (New Radio, NR for short) base station, how the secondary network device sends a radio resource control (Radio resource control, RRC for short) configuration to the terminal device and how the terminal device performs feedback when determining that the RRC configuration fails both need to be resolved.

<NPL>, proposes that for the secondary node RRC message carried on SCG SRB, when UE is unable to comply with the SCG RRC reconfiguration, SCG failure indication procedure should be triggered and the SCGFailurelnformation should be sent to master node through MCG SRB.

<NPL>, proposes whether the SCG split bearer is maintained or not upon S-RLF in tight interworking should be a network decision, and that after receiving SCGFailurelnformation, the MeNB can notify the SgNB about the failure, and that after receiving SCGFailurelnformation, it is up to the SgNB which action to take, wherein upon S-RLF in tight interworking, SCG transmission is suspended, SCG-MAC is reset and SCGFailurelnformation is sent, and upon S-RLF, the UE changes the UL transmission direction from the SgNB to the MeNB.

Document <CIT> discloses a communication control method including controlling a dual connectivity communication using a master base station configured to establish an RRC connection with a user terminal and a secondary base station configured to provide additional radio resources to the user terminal. The controlling comprises the steps of: detecting, by the user terminal, a radio link failure between the user terminal and the secondary base station; reporting, by the user terminal, the radio link failure to the master base station; and transmitting, by the master base station, a stop instruction signal to the secondary base station.

Document <CIT> provides a method and apparatus for radio resource control connection and a method and an apparatus for solving radio link degradation, wherein user equipment (UE) may establish radio connections to two/plural cells. The method comprises: determining that at least one of the radio connections established by the UE and two/plural cells occur connection failure; and executing radio resource control (RRC) connection to implement dual/plural connectivity with the two/plural cells.

Document <CIT> relates to the technical field of mobile communications, and particularly relates to a cell configuration method and device, used to prevent severe data interruption and ensure normal communication for user equipment. The method comprises: in a scenario of jointly employing an MeNB and an SeNB, a first base station sends SCG configuration information to UE to perform SCG configuration; if the UE Determines that the SCG configuration fails, the UE sends to a network side SCG reconfiguration failure information; and then if an MCG configuration succeeds, then the UE and the network side keep the original SCG configuration information sent at the previous iteration unchanged, else an SCG release is triggered. In this way, when only an SCG configuration fails, the present invention uses original SCG configuration information instead of frequently launching RRC re-establishment, such that severe data interruption is effectively avoided.

<NPL>, discusses the use of MCG SRB and SCG SRB.

The following clearly and completely describes technical solutions in the embodiments of this application with reference to the accompanying drawings in the embodiments of this application.

Network architectures and service scenarios described in the embodiments of this application are intended to describe the technical solutions in the embodiments of this application more clearly, but do not constitute a limitation to the technical solutions provided in the embodiments of this application. A person of ordinary skill in the art may know that as the network architectures evolve and a new service scenario emerges, the technical solutions provided in the embodiments of this application are also applicable to a similar technical problem.

This application may be applied to an existing cellular communications system, for example, systems such as a global system for mobile communications (Global System for Mobile Communication, GSM for short), a wideband code division multiple access (Wideband Code Division Multiple Access, WCDMA for short) system, and a long term evolution (Long Term Evolution, LTE for short) system; or is applicable to a 5th generation mobile communications system (Srd-Generation, <NUM> for short) system, for example, communications systems such as an access network that uses new radio (New Radio, NR for short), a cloud radio access network (Cloud Radio Access Network, CRAN for short), and an LTE access network connected to a <NUM> core network; or may be extended to a similar wireless communications system, such as a wireless fidelity (Wireless-Fidelity, wifi for short) system, a worldwide interoperability for microwave access (Worldwide Interoperability for Microwave Access, WiMAX for short) system, and another related cellular system in the 3rd Generation Partnership Project (3rd Generation Partnership Project, 3GPP for short); or is applicable to another wireless communications system that uses an orthogonal frequency division multiplexing (Orthogonal Frequency Division Multiplexing, OFDM for short) access technology; and is also applicable to a future wireless communications system.

Network architectures and service scenarios described in this application are intended to describe the technical solutions in this application more clearly, but do not constitute a limitation to the technical solutions provided in this application. A person of ordinary skill in the art may know that as the network architectures evolve and a new service scenario emerges, the technical solutions provided in this application are also applicable to a similar technical problem.

For ease of understanding, some terminologies in this application are described below.

The term "and/or" in this application describes only an association relationship for describing associated objects and represents that three relationships may exist.

The following describes in more detail the solutions provided in the embodiments of this application with reference to the accompanying drawings.

<FIG> is a structural diagram of a network according to this application. A terminal device interacts with a primary network device and at least one secondary network device (one secondary network device is used as an example in the figure), and the terminal device includes a first unit and a second unit. The first unit may be a first RRC entity, a first RRC functional unit, or a first RRC unit, and is configured to control an RRC connection between the primary network device and the terminal device. The second unit may be a second RRC entity, a second RRC functional unit, or a second RRC unit, and is configured to control an RRC connection between the secondary network device and the terminal device.

For example, a core network is an evolved packet core (Evolved Packet Core, EPC for short). The primary network device is an LTE base station (such as an eNB), and a control plane connection and a user plane connection may be established between the primary network device and the EPC for the terminal device. The secondary network device is an NR base station (such as a gNB), and only a user plane connection can be established between the secondary network device and the EPC. The first unit is an LTE RRC entity, and is responsible for managing LTE radio resources. The second unit is an NR RRC entity, and is responsible for managing NR radio resources. In addition, for example, an S1 interface may be used between the core network and the primary network device; an S1 interface may be used between the core network and the secondary network device; and an X2 interface may be used between the primary network device and the secondary network device.

For another example, a core network is a next generation core (Next Generation Core, NGC for short), a <NUM> core network (<NUM> Core Network, <NUM>-CN for short), or a <NUM> core (<NUM> Core, 5GC for short). An example in which the core network is an NGC is used for description below. The primary network device is an LTE base station (such as an eNB), and a control plane connection and a user plane connection may be established between the primary network device and the NGC for the terminal device. The secondary network device is an NR base station (such as a gNB), and only a user plane connection can be established between the secondary network device and the NGC. The first unit is an LTE RRC entity, and is responsible for LTE radio resources. The second unit is an NR RRC entity, and is responsible for managing NR radio resources. In addition, for example, a next generation (Next Generation, NG for short) interface may be used between the core network and the primary network device; an NG interface may be used between the core network and the secondary network device; and an Xn interface (namely, a next generation interface) may be used between the primary network device and the secondary network device.

For another example, a core network is an NGC, a <NUM>-CN, or a 5GC. An example in which the core network is an NGC is used for description below. The primary network device is an NR base station (such as a gNB), and a control plane connection and a user plane connection may be established between the primary network device and the NGC for the terminal device. The secondary network device is an LTE base station (such as an eNB), and only a user plane connection can be established between the secondary network device and the NGC. The first unit is an NR RRC entity, and is responsible for NR radio resources. The second unit is an LTE RRC entity, and is responsible for managing LTE radio resources. In addition, for example, an NG interface may be used between the core network and the primary network device; an NG interface may be used between the core network and the secondary network device; and an Xn interface (namely, a next generation interface) may be used between the primary network device and the secondary network device.

Certainly, alternatively, the core network may be another core network, the primary network device may be another network device, such as various types of network devices mentioned above, and the secondary network device may also be another network device, such as various types of network devices mentioned above.

In this application, standards of the primary network device and the secondary network device may be the same or different. The following mainly provides description for a case in which the standards of the primary network device and the secondary network device are different. For example, the primary network device is an LTE base station, and the secondary network device is an NR base station; or the primary network device is an NR base station, and the secondary network device is an LTE base station. In addition, for ease of description, in this application, the first unit has a same standard as the primary network device, and the second unit has a same standard as the secondary network device. For example, when the primary network device is an NR base station, and the secondary network device is an LTE base station, the first unit is responsible for managing NR radio resources, for example, the first unit is an NR RRC entity; and the second unit is responsible for managing LTE radio resources, for example, the second unit is an LTE RRC entity. For another example, when the primary network device is an LTE base station, and the secondary network device is an NR base station, the first unit is responsible for managing LTE radio resources, for example, the first unit is an LTE RRC entity; and the second unit is responsible for managing NR radio resources, for example, the second unit is an NR RRC entity.

The terminal device may obtain radio resources from both an air interface of the primary network device and an air interface of the secondary network device to transmit data, thereby obtaining a gain of a transmission rate.

In this application, the first unit and the second unit are responsible for configurations in their respective standards, and do not understand each other's configuration.

The primary network device and the secondary network device are independent of each other. From a perspective of a network side, the primary network device and the secondary network device each have RRC and may generate a complete RRC message. In a scenario shown in <FIG>, an RRC message (carrying an RRC configuration of the secondary network device) generated by the secondary network device is sent to the primary network device; and the primary network device uses the RRC message of the secondary network device as a container (container), adds the container to an RRC message of the primary network device, and sends the RRC message of the primary network device to the terminal device. In other words, the terminal device receives the RRC message of the primary network device from the primary network device, the RRC message includes an RRC configuration of the primary network device and the RRC configuration of the secondary network device, and the RRC configuration of the secondary network device in the RRC message of the primary network device is sent by the secondary network device to the primary network device by using the RRC message of the secondary network device.

In an RRC configuration manner shown in <FIG>, which is also referred to as joint configuration in this application, the secondary network device sends the RRC configuration of the secondary network device to the primary network device, and the primary network device then sends the RRC configuration of the secondary network device to the terminal device; in addition, the primary network device may further send the RRC configuration of the primary network device to the terminal device. In other words, in the joint configuration scenario, the RRC configuration of the secondary network device needs to be sent to the terminal device by using the primary network device.

<FIG> is a structural diagram of another network according to this application. A core network, a primary network device, a secondary network device, a first unit, and a second unit in <FIG> have same types and same mutual relationships as the core network, the primary network device, the secondary network device, the first unit, and the second unit in <FIG>. For details, refer to the foregoing description. A main difference between <FIG> and <FIG> is as follows: In <FIG>, the secondary network device may directly send an RRC message to a terminal device, where the RRC message carries an RRC configuration of the secondary network device; and the primary network device sends an RRC message to the terminal device, where the RRC message carries an RRC configuration of the primary network device. Therefore, in an RRC configuration manner shown in <FIG>, which is also referred to as independent configuration in this application, the RRC configuration of the primary network device and the RRC configuration of the secondary network device are independently sent by the primary network device and the secondary network device to the terminal device, respectively.

The following describes in detail two failure processing methods provided in this application with reference to <FIG> and <FIG> respectively.

<FIG> is a flowchart of part of a failure processing method according to this invention. The method corresponds to the scenario shown in <FIG>, namely, the joint configuration scenario, and specifically includes the following steps. Step <NUM>: A primary network device sends a second RRC configuration of a secondary network device to a terminal device.

An RRC configuration is configuration information generated by an RRC entity of a network device, and is used to configure a terminal device. For example, the RRC configuration includes configurations of protocol layers, and includes but is not limited to a packet data convergence protocol (Packet Data Convergence Protocol, PDCP for short) configuration, a radio link control (Radio Link Control, RLC for short) configuration, a media access control layer (Media Access Control, MAC for short) configuration, and a physical layer configuration.

Optionally, the secondary network device adds the second RRC configuration of the secondary network device to an RRC message of the secondary network device, and sends the RRC message of the secondary network device to the primary network device. After receiving the RRC message of the secondary network device, the primary network device adds the RRC configuration of the secondary network device to an RRC message of the primary network device, and sends the RRC message of the primary network device to the terminal device. Optionally, the RRC message of the primary network device further carries a third RRC configuration of the primary network device. Step <NUM>: The terminal device receives the second RRC configuration of the secondary network device from the primary network device.

Step <NUM>: The terminal device sends a second message to the primary network device if the second RRC configuration fails.

The second message is used to request RRC connection reestablishment. Optionally, the second message is an RRC connection reestablishment message. Optionally, the second message includes third indication information, and the indication information is used to indicate that the second RRC configuration fails.

In a possible implementation, referring to <FIG>, a second unit of the terminal device generates fourth indication information if the second unit determines that the second RRC configuration of the secondary network device that is received by the terminal device from the primary network device fails, where the fourth indication information is used to indicate that the second RRC configuration fails. Then, the second unit sends the fourth indication information to a first unit. The terminal device sends the second message to the primary network device if the first unit receives the fourth indication information sent by the second unit. The second unit may be a second RRC entity of the terminal device.

In another possible implementation, referring to <FIG>, a second unit of the terminal device generates seventh indication information if the second unit determines that the second RRC configuration of the secondary network device that is received by the terminal device from the primary network device succeeds, where the seventh indication information is used to indicate that the second RRC configuration succeeds. Then, the second unit sends the seventh indication information to a first unit. The terminal device sends a fifth message to the primary network device if the first unit receives the seventh indication information sent by the second unit, where the fifth message is used to indicate that the second RRC configuration succeeds. The second unit may be a second RRC entity of the terminal device.

Step <NUM>: The primary network device receives the second message from the terminal device.

Step <NUM>: The primary network device sends a sixth message to the terminal device, where the sixth message is used to reestablish an SRB.

In step <NUM> to step <NUM>, the terminal device receives the second RRC configuration of the secondary network device from the primary network device; when the terminal device determines that the second RRC configuration fails, to be specific, the second unit of the terminal device determines that the second RRC configuration fails, and sends the fourth indication information to the first unit, the terminal device sends the second message to the primary network device to request the RRC connection reestablishment; and after receiving the second message, the primary network device sends a RRC connection reestablishment message.

Optionally, before or after any one of step <NUM> to step <NUM>, the method further includes:
the terminal device receives the third RRC configuration of the primary network device from the primary network device; and if the third RRC configuration fails, the terminal device performs at least one of the following actions: stopping executing the second RRC configuration, releasing the second RRC configuration, and suspending a radio bearer of the secondary network device.

Optionally, that the terminal device performs at least one of the following actions includes: if the second unit receives fifth indication information sent by the first unit, the terminal device performs at least one of the following actions, where the fifth indication information is used to indicate that the third RRC configuration fails.

To be specific, when the terminal device further receives the third RRC configuration of the primary network device from the primary network device, and the third RRC configuration fails, the first unit sends the fifth indication information to the second unit to indicate that the third RRC configuration fails, and the terminal device further stops executing the second RRC configuration, and/or releases the second RRC configuration, and/or suspends the radio bearer of the secondary network device.

In addition, if the third RRC configuration fails, the terminal device further needs to perform the following operation:
the terminal device sends a seventh message to the primary network device, where the seventh message is used to request RRC connection reestablishment. Optionally, the seventh message includes seventh indication information, and the seventh indication information is used to indicate that the third RRC configuration of the primary network device that is received by the terminal device from the primary network device fails.

<FIG> is a flowchart of another part of a failure processing method according to this invention. The method corresponds to the scenario shown in <FIG>, namely, an independent configuration scenario, and specifically includes the following steps.

Step <NUM>: A terminal device receives a first RRC configuration of a secondary network device from the secondary network device.

Step <NUM>: The terminal device sends first indication information to a primary network device.

The first indication information is used to indicate that the first RRC configuration fails.

Optionally, that the terminal device sends first indication information to a primary network device includes: the terminal device sends a first message to the primary network device, where the first message includes the first indication information.

Optionally, referring to <FIG>, that the terminal device sends first indication information to a primary network device includes: the terminal device sends the first indication information to the primary network device if a first unit of the terminal device receives second indication information sent by a second unit of the terminal device, where the second indication information is used to indicate that the first RRC configuration received from the secondary network device fails. In other words, the second unit sends the second indication information to the first unit if the second unit determines that the first RRC configuration fails, and the terminal device sends the first indication information to the primary network device if the first unit receives the second indication information sent by the second unit.

Step <NUM>: The primary network device receives the first indication information from the terminal device.

Step <NUM>: The primary network device sends a first request message to the secondary network device.

The first request message is used to request the secondary network device to update an RRC configuration or request to release the secondary network device.

After updating the RRC configuration, the secondary network device sends a new RRC configuration to the primary network device. The primary network device sends the new RRC configuration to the terminal device. In other words, the terminal device receives the new RRC configuration from the primary network device.

It should be noted that an RRC connection reestablishment process is performed between the primary network device and user equipment in this case.

Alternatively, after updating the RRC configuration, the secondary network device directly sends a new RRC configuration to the terminal device. In other words, the terminal device receives the new RRC configuration from the secondary network device. In this method, the terminal device directly receives the new RRC configuration from the secondary network device, and therefore a speed is higher than a speed in the method for receiving the new RRC configuration of the secondary network device from the primary network device.

Optionally, the first request message includes the first indication information.

In an alternative solution of step <NUM>, step <NUM> may alternatively be replaced with step 204a:
Step 204a: The primary network device releases the secondary network device.

After releasing the secondary network device, the primary network device may be further reconnected to a new secondary network device.

The implementation methods shown in <FIG> and <FIG> are used as a whole for understanding. To be specific, the terminal device may receive the first RRC configuration of the secondary network device from the secondary network device, and may also receive a second RRC configuration of the secondary network device from the primary network device.

The second unit sends failure indication information to the first unit if the terminal device determines that a link between the terminal device and the secondary network device fails. The failure indication information indicates a specific cause of the link failure. For example, the failure indication information is specifically used to indicate that a timer expires, a quantity of retransmission times exceeds a maximum quantity of times, random access fails, a secondary-cell group change fails, a key fails, a check fails, integrity protection fails, a secondary network configuration received from the secondary network device fails, or a secondary network configuration received from a primary network fails.

The timer may be started when the terminal device detects that a physical layer problem occurs in a primary cell of the secondary network device. The quantity of retransmission times may be a quantity of times of performing retransmission at an RLC layer, or may be a quantity of times of performing retransmission at another layer. That random access fails may indicate that random access to a cell of the secondary network device by the terminal device fails. That a secondary-cell group change fails may indicate that the terminal device fails to change a secondary-cell group. The secondary-cell group may be a cell group, of the secondary network device, that serves the terminal device. That a key fails may indicate that the terminal device cannot normally perform encryption and/or decryption because of key inconsistency between the terminal device and the secondary network device. That a check fails may indicate checking performed by the terminal device and the secondary network device fails. That integrity protection fails may indicate that integrity protection between the terminal device and the secondary network device fails. For detailed contents, refer to related contents in 3GPP TS <NUM> and 3GPP TS <NUM>. The foregoing description is merely used as an example, but no limitation is set to the foregoing description.

When the failure indication information is used to indicate that the secondary network configuration received from the secondary network device fails, the failure indication information is the second indication information described above.

When the failure indication information is used to indicate that the secondary network configuration received from the primary network fails, the failure indication information is the fourth indication information described above. Optionally, the failure indication information may be generated by the second unit when the second unit determines that the link between the terminal device and the secondary network device fails. Alternatively, a third unit of the terminal device may generate sixth indication information when determining that the link between the terminal device and the secondary network device fails, where the sixth indication information is used to indicate that the link between the terminal device and the secondary network device fails; the third unit sends the sixth indication information to the second unit; and after receiving the sixth indication information, the second unit generates the failure indication information. Alternatively, a third unit may generate failure indication information when determining that the link between the terminal device and the secondary network device fails, and then directly send the failure indication information to the first unit.

The third unit may be a second MAC entity, a second RLC entity, a second physical layer unit, or an application layer entity of the terminal device, and the second MAC entity, the second RLC entity, or the second physical layer unit has a same standard as the secondary network device.

After the first unit receives the failure indication information, the terminal device sends indication information to the primary network device if the failure indication information indicates that the timer expires, where the indication information is used to indicate that the timer expires. After receiving the indication information, the primary network device does not reestablish an RRC link.

After the first unit receives the failure indication information, the terminal device sends indication information to the primary network device if the failure indication information indicates that the quantity of retransmission times exceeds the maximum quantity of times, where the indication information is used to indicate that the quantity of retransmission times exceeds the maximum quantity of times. After receiving the indication information, the primary network device does not reestablish an RRC link.

After the first unit receives the failure indication information, the terminal device sends indication information to the primary network device if the failure indication information indicates that the random access fails, where the indication information is used to indicate that the random access fails. After receiving the indication information, the primary network device does not reestablish an RRC link.

After the first unit receives the failure indication information, the terminal device sends indication information to the primary network device if the failure indication information indicates that the secondary-cell group change fails, where the indication information is used to indicate that the secondary-cell group change fails. After receiving the indication information, the primary network device does not reestablish an RRC link.

After the first unit receives the failure indication information, the terminal device sends indication information to the primary network device if the failure indication information indicates that the key fails, where the indication information is used to indicate that the key fails. After receiving the indication information, the primary network device does not reestablish an RRC link.

After the first unit receives the failure indication information, the terminal device sends indication information to the primary network device if the failure indication information indicates that the check fails, where the indication information is used to indicate that the check fails. After receiving the indication information, the primary network device does not reestablish an RRC link.

After the first unit receives the failure indication information, the terminal device sends indication information to the primary network device if the failure indication information indicates that the integrity protection fails, where the first indication information is used to indicate that the integrity protection fails. After receiving the indication information, the primary network device does not reestablish an RRC link.

After the first unit receives the failure indication information, the terminal device sends the first indication information to the primary network device if the failure indication information indicates that the secondary network configuration received from the secondary network device fails, where the first indication information is used to indicate that the secondary network configuration received from the secondary network device fails (that is, the first RRC configuration described above fails). After receiving the first indication information, the primary network device does not reestablish an RRC link.

After the first unit receives the failure indication information, the terminal device sends a second message to the primary network device if the failure indication information indicates that the secondary network configuration received from the primary network fails, where the second message is used to request RRC connection reestablishment. After receiving the second message, the primary network device reestablishes an RRC link. Optionally, the second message further includes third indication information, and the third indication information is used to indicate that the secondary network configuration received from the primary network fails (that is, the second RRC configuration described above fails).

In the foregoing embodiments provided in this application, the failure processing methods provided in the embodiments of this application are described respectively from a perspective of each network element and from a perspective of interaction between network elements. It may be understood that, to implement the foregoing function, the network elements, such as the terminal device (for example, UE) and the network device (for example, a base station), include a corresponding hardware structure and/or software module for performing each function. A person skilled in the art should be easily aware that units and algorithm steps in the examples described with reference to the embodiments disclosed in this specification can be implemented in a form of hardware or in a form of a combination of hardware and computer software in this application. Whether a function is implemented by hardware or in a manner of driving hardware by computer software depends on particular applications and design constraints of the technical solutions.

In a scenario of handover between primary network devices, a first primary network device connected to a terminal device needs to be handed over to a second primary network device, a secondary network device connected to the terminal device remains unchanged, and a configuration of the secondary network device remains unchanged. According to the prior art, a first primary network device, a second primary network device, and a secondary network device have same standards, for example, they are all LTE network devices, or are all NR network devices. Therefore, a handover procedure is as follows: The first primary network device sends a configuration of the secondary network device to the second primary network device; and after receiving the configuration of the secondary network device, the second primary network device may read and understand the configuration, and therefore may generate a configuration based on the configuration and a capability of the terminal device, and ensure that the final configuration does not exceed the capability of the terminal device.

In consideration of another application scenario, a first primary network device and a second primary network device have same standards, and the standards are different from a standard of a secondary network device. In this case, according to the foregoing handover procedure, because the second primary network device cannot understand a configuration of the secondary network device, the first primary network device cannot be handed over to the second primary network device according to the foregoing handover method.

Therefore, this application further provides a handover method not being part of the present invention.

Step <NUM>: A first primary network device sends a third message to a second primary network device.

The third message is used to request handover. For example, the third message is a handover request message, and the third message includes a capability coordination result between the first primary network device and the secondary network device.

Optionally, the capability coordination result includes a size of a layer <NUM> buffer that can be used by the first primary network device and/or a band combination that can be used by the first primary network device.

The layer <NUM> buffer is a layer <NUM> buffer of a terminal device, and the band combination is a band combination (band combination) of the terminal device.

Step <NUM>: The second primary network device generates a configuration of the second primary network device based on the capability coordination result between the first primary network device and the secondary network device.

In other words, the configuration of the second primary network device is associated with the capability coordination result.

Optionally, the configuration is an RRC configuration.

Step <NUM>: The second primary network device sends the configuration of the second primary network device to the first primary network device.

Step <NUM>: The first primary network device receives the configuration of the second primary network device that is sent by the second primary network device.

By using step <NUM> to step <NUM>, the first primary network device directly sends the capability coordination result between the first primary network device and the secondary network device to the second primary network device, so that the second primary network device generates the configuration based on the capability coordination result without obtaining and understanding a configuration of the secondary network device, and it can be ensured that the second primary network device can successfully generate the configuration in a handover process.

Optionally, the first primary network device may further receive a configuration of the secondary network device. Further, the first primary network device sends the configuration of the second primary network device and the configuration of the secondary network device to the terminal device. That the first primary network device receives a configuration of the secondary network device includes: the first primary network device receives the configuration of the secondary network device from the second primary network device, or the first primary network device receives the configuration of the secondary network device from the secondary network device.

To be specific, by using the foregoing steps, the second primary network device sends the configuration of the second primary network device to the first primary network device. Optionally, the second primary network device further sends the configuration of the secondary network device to the first primary network device (or the secondary network device sends the configuration of the secondary network device to the first primary network device). After receiving the configuration of the second primary network device, optionally, the first primary network device further receives the configuration of the secondary network device. The first primary network device sends the configuration of the second primary network device to the terminal device, and optionally, further sends the configuration of the secondary network device to the terminal device.

Optionally, if the terminal device receives the configuration of the secondary network device that is sent by the first primary network device, and the configuration of the secondary network device fails, the terminal device sends a fourth message to the first primary network device, where the fourth message is used to indicate RRC connection reestablishment.

For a detailed process of a failure processing method used when the terminal device receives the configuration of the secondary network device that is sent by the first primary network device and the configuration of the secondary network device fails, refer to the foregoing description and the description shown in <FIG>.

The following provides description by using band combination coordination as an example. For capability coordination of band combination, an optional solution is to maintain a band combination list. For example, as shown in Table <NUM>, the first column is an index (index), the second column is a band combination that can be used by the first primary network device, and the third column is a band combination that can be used by the secondary network device when the first primary network device uses the band combination in the second column. Such a combination exists because a same radio frequency chain of a terminal device may be used in different bands, and the same radio frequency chain cannot be simultaneously used by the first primary network device and the secondary network device.

A network side can obtain information in Table <NUM> from a capability of the terminal device. Specifically, the first primary network device only needs to know a band combination that is of the first primary network device and that corresponds to an index, and the secondary network device only needs to know a band combination that is of the secondary network device and that corresponds to an index. In a capability coordination process, the first primary network device selects a band combination, and sends a corresponding index to the secondary network device. Therefore, the secondary network device may know a band combination that can be used by the secondary network device, thereby ensuring that a final configuration does not exceed the capability of the terminal device. For example, if a band combination selected by the first primary network device is <NUM>, <NUM>, and <NUM>, the first primary network device sends an index <NUM> to the secondary network device, and therefore the secondary network device learns that a band combination that can be used by the secondary network device is <NUM>, <NUM>, and <NUM>.

After determining the band combination that can be used by the first primary network device, for example, the band combination that can be used is <NUM>, <NUM>, and <NUM>, the first primary network device sends, to the second primary network device, the band combination that can be used by the first primary network device.

Then, the layer <NUM> buffer is used as an example. Assuming that a size of the layer <NUM> buffer of the terminal device is <NUM>, the first primary network device coordinates with the secondary network device, for example, to finally determine that the size of the layer <NUM> buffer that can be used by the first primary network device is <NUM>, and a size of a layer <NUM> buffer that can be used by the secondary network device is <NUM>.

After determining the size of the layer <NUM> buffer and the band combination that can be used by the first primary network device, the first primary network device sends, to the second primary network device, the size of the layer <NUM> buffer and the band combination that can be used by the first primary network device. The second primary network device then generates the configuration, for example, generates an RRC configuration, and sends the configuration to the first primary network device. The first primary network device then sends the configuration to the terminal device.

Optionally, the secondary network device generates the configuration based on the size of the layer <NUM> buffer and a band combination that can be used by the secondary network device, and sends the configuration to the second primary network device. The second primary network device sends the configuration of the secondary network device and the configuration of the second primary network device together to the first primary network device, and the first primary network device sends the configurations to the terminal device.

Based on a same inventive concept, an embodiment of this application further provides a network device <NUM>. As shown in <FIG>, the network device <NUM> may be configured to perform the method performed by the primary network device in the foregoing failure processing methods and the method performed by the first primary network device in the foregoing handover method. The network device <NUM> includes one or more remote radio units (remote radio unit, RRU for short) <NUM> and one or more baseband units (baseband unit, BBU for short) <NUM>. The RRU <NUM> may be referred to as a transceiver unit, a transceiver, a transceiver circuit, a transceiver, or the like; and may include at least one antenna <NUM> and a radio frequency unit <NUM>. The RRU <NUM> is mainly configured to receive/send a radio frequency signal and convert a radio frequency signal and a baseband signal. The BBU <NUM> is mainly configured to perform baseband processing, control the network device, and the like. The RRU <NUM> and the BBU <NUM> may be physically disposed together; or the RRU <NUM> and the BBU <NUM> may be physically separated, or in other words, the RRU <NUM> and the BBU <NUM> are devices in a distributed network.

The BBU <NUM> is a control center of the network device, or may be referred to as a processing unit, and is mainly configured to complete baseband processing functions such as channel coding, multiplexing, modulation, and spectrum spreading. For example, the BBU (processing unit) may be configured to control the network device to perform the method performed by the primary network device in any one of the foregoing failure processing methods and the method performed by the first primary network device in the foregoing handover method.

In an example, the BBU <NUM> may include one or more boards, and a plurality of boards may jointly support a radio access network (such as an LTE network) of a single access standard, or may support radio access networks of different access standards. The BBU <NUM> further includes a memory <NUM> and a processor <NUM>. The memory <NUM> is configured to store a necessary instruction and necessary data. The processor <NUM> is configured to control the network device to perform a necessary action, for example, is configured to control the network device to perform the method performed by the network device in any one of the foregoing embodiments. The memory <NUM> and the processor <NUM> may serve one or more boards. In other words, a memory and a processor may be separately disposed on each board. Alternatively, a plurality of boards may use a same memory and processor. In addition, a necessary circuit is further disposed on each board.

On an uplink, an uplink signal (including data and the like) sent by a terminal device is received by using the antenna <NUM>. On a downlink, a downlink signal (including data and/or control information) is sent to the terminal device by using the antenna <NUM>. In the processor <NUM>, service data and a signaling message are processed, and these units perform processing according to a radio access technology (such as access technologies in LTE, NR, and other evolved systems) used in a radio access network. The processor <NUM> is further configured to control and manage an action of the network device, and is configured to perform processing performed by the network device in the foregoing embodiment. The processor <NUM> is further configured to support the network device in performing processing procedures described in <FIG> and <FIG> and performed by the primary network device and the method described in <FIG> and performed by the first primary network device.

It may be understood that <FIG> shows only a simplified design of the network device. In actual application, the network device may include any quantity of antennas, memories, processors, radio frequency units, RRUs, BBUs, and the like, and all network devices that can implement this application fall within the protection scope of this application.

Specifically, in this application, for example, the RRU <NUM> is referred to as a transceiver. In this case, the transceiver and the processor in the network device <NUM> may be specifically configured to:
The transceiver is configured to receive first indication information from the terminal device, where the first indication information is used to indicate that a first RRC configuration of a secondary network device fails, and the first RRC configuration is received by the terminal device from the secondary network device.

The transceiver is further configured to send a first request message to the secondary network device, where the first request message is used to request the secondary network device to update an RRC configuration or request to release the secondary network device.

The transceiver and the processor in the network device <NUM> may be further specifically configured to:
If a second RRC configuration of a secondary network device fails, the transceiver is configured to receive a second message from the terminal device, where the second message is used to indicate RRC connection reestablishment, and the second RRC configuration is received by the terminal device from the primary network device.

The transceiver is further configured to initiate the RRC connection reestablishment to the terminal device. Optionally, the second message includes third indication information, and the indication information is used to indicate that the second RRC configuration fails.

The transceiver and the processor in the network device <NUM> may be further specifically configured to:
The transceiver is configured to send a third message to a second primary network device, where the third message is used to request handover, and the third message includes a capability coordination result between the first primary network device and the secondary network device.

The transceiver is further configured to receive a configuration of the second primary network device that is sent by the second primary network device, where the configuration of the second primary network device is associated with the capability coordination result.

Optionally, the transceiver is further configured to receive a configuration of the secondary network device.

The transceiver is further configured to send the configuration of the second primary network device and the configuration of the secondary network device to the terminal device.

Optionally, the transceiver is further configured to receive the configuration of the secondary network device from the second primary network device.

Optionally, if the configuration of the secondary network device fails, the transceiver is further configured to receive a fourth message from the terminal device, where the fourth message is used to indicate RRC connection reestablishment.

Based on a same inventive concept, an embodiment of this application further provides a terminal device <NUM>. For ease of description, <FIG> shows only main components of the terminal device. As shown in <FIG>, the terminal device <NUM> includes a processor, a memory, a control circuit, an antenna, and an input/output apparatus. The processor is mainly configured to: process a communications protocol and communication data, control the entire terminal device, execute a software program, and process data of the software program, for example, configured to support the terminal device <NUM> in performing the method performed by the terminal device <NUM> in any one of the foregoing embodiments. The memory is mainly configured to store the software program and the data. The control circuit is mainly configured to convert a baseband signal and a radio frequency signal and process a radio frequency signal. The control circuit, together with the antenna, may also be referred to as a transceiver that is mainly configured to receive/send a radio frequency signal in an electromagnetic wave form. The input/output apparatus, such as a touchscreen, a display screen, or a keyboard, is mainly configured to: receive data entered by a user and output data to the user.

After the terminal device is powered on, the processor may read a software program in a storage unit, explain and execute an instruction of the software program, and process data of the software program. When data needs to be sent in a wireless manner, the processor performs baseband processing on the to-be-sent data, and outputs a baseband signal to a radio frequency circuit. The radio frequency circuit performs radio frequency processing on the baseband signal, and then sends a radio frequency signal by using the antenna in an electromagnetic wave form. When data is sent to the terminal device <NUM>, the radio frequency circuit receives a radio frequency signal by using the antenna, converts the radio frequency signal into a baseband signal, and outputs the baseband signal to the processor, and the processor converts the baseband signal into data and processes the data.

A person skilled in the art may understand that, for ease of description, <FIG> shows only one memory and one processor. Actually, the terminal device may include a plurality of processors and a plurality of memories. The memory may also be referred to as a storage medium, a storage device, or the like. This is not limited in this application.

In an optional implementation, the processor may include a baseband processor and a central processing unit. The baseband processor is mainly configured to process a communications protocol and communication data, and the central processing unit is mainly configured to: control the entire terminal device <NUM>, execute a software program, and process data of the software program. Functions of the baseband processor and the central processing unit are integrated into the processor in <FIG>. A person skilled in the art may understand that the baseband processor and the central processing unit each may be an independent processor, and they are interconnected by using a technology such as a bus. A person skilled in the art may understand that the terminal device may include a plurality of baseband processors to adapt to different network standards, the terminal device <NUM> may include a plurality of central processing units to enhance a processing capability of the terminal device <NUM>, and all components of the terminal device <NUM> may be connected through various buses. The baseband processor may also be expressed as a baseband processing circuit or a baseband processing chip. The central processing unit may also be expressed as a central processing circuit or a central processing chip. A function of processing a communications protocol and communication data may be built into the processor, or may be stored in a storage unit in a form of a software program. The processor executes the software program to implement a baseband processing function.

For example, in this application, the antenna that has receiving and sending functions and the control circuit may be considered as a transceiver unit <NUM> of the terminal device <NUM>, and the processor having a processing function may be considered as a processing unit <NUM> of the terminal device <NUM>. As shown in <FIG>, the terminal device <NUM> includes the transceiver unit <NUM> and the processing unit <NUM>. The transceiver unit may also be referred to as a transceiver, a transceiver, a transceiver apparatus, or the like. Optionally, a component that is in the transceiver unit <NUM> and that is configured to implement a receiving function may be considered as a receiving unit, and a component that is in the transceiver unit <NUM> and that is configured to implement a sending function may be considered as a sending unit, in other words, the transceiver unit <NUM> includes the receiving unit and the sending unit. For example, the receiving unit may also be referred to as a receiver, a receiver, a receiver circuit, or the like, and the sending unit may be referred to as a transmitter, a transmitter, a transmit circuit, or the like.

On a downlink, a downlink signal (including data and/or control information) sent by a network device is received by using the antenna. On an uplink, an uplink signal (including data and/or control information) is sent to the network device by using the antenna. In the processor, service data and a signaling message are processed, and these units perform processing according to a radio access technology (such as access technologies in LTE, NR, and other evolved systems) used in a radio access network. The processor is further configured to control and manage an action of the terminal device, and is configured to perform processing performed by the terminal device in the foregoing embodiment. The processor is further configured to support the terminal device in performing processing procedures described in <FIG>, <FIG> and performed by the terminal device.

It may be understood that <FIG> shows only a simplified design of the terminal device. In actual application, the terminal device may include any quantity of antennas, memories, processors, and the like, and all terminal devices that can implement this application fall within the protection scope of this application.

Specifically, in this application, for example, the transceiver unit is referred to as a transceiver, and the processing unit is referred to as a processor. In this case, the transceiver and the processor in the terminal device <NUM> may be specifically configured to:
The transceiver is configured to receive a first RRC configuration of a secondary network device from the secondary network device.

The transceiver is further configured to send first indication information to a primary network device, where the first indication information is used to indicate that the first RRC configuration fails.

Optionally, the transceiver is further configured to send a first message to the primary network device, where the first message includes the first indication information.

Optionally, if a first unit of the terminal device receives second indication information sent by a second unit of the terminal device, the transceiver is further configured to send the first indication information to the primary network device, where the second indication information is used to indicate that the first RRC configuration received from the secondary network device fails, the first unit is configured to control an RRC connection between the primary network device and the terminal device, and the second unit is configured to control an RRC connection between the secondary network device and the terminal device.

Optionally, the first unit is a first RRC entity, and the second unit is a second RRC entity.

Optionally, the transceiver is further configured to receive a new RRC configuration from the secondary network device.

The transceiver and the processor in the terminal device <NUM> may be further specifically configured to:
The transceiver is configured to receive a second RRC configuration of a secondary network device from a primary network device.

If the second RRC configuration fails, the transceiver is further configured to send a second message to the primary network device, where the second message is used to request RRC connection reestablishment.

Optionally, the second message includes third indication information, and the third indication information is used to indicate that the second RRC configuration fails.

Optionally, if a first unit of the terminal device receives fourth indication information sent by a second unit of the terminal device, the transceiver is further configured to send the second message to the primary network device, where the fourth indication information is used to indicate that the second RRC configuration received from the primary network device fails, the first unit is configured to control an RRC connection between the primary network device and the terminal device, and the second unit is configured to control an RRC connection between the secondary network device and the terminal device.

Optionally, the transceiver is further configured to receive a third RRC configuration of the primary network device from the primary network device.

If the third RRC configuration fails, the processor performs at least one of the following actions: stopping executing the second RRC configuration, releasing the second RRC configuration, and suspending a radio bearer of the secondary network device.

Optionally, if the second unit receives fifth indication information sent by the first unit, the processor performs at least one of the following actions, where the fifth indication information is used to indicate that the third RRC configuration fails.

<FIG> is a schematic diagram of another terminal device according to this application, and the terminal device may be configured to perform an operation performed by the terminal device in any one of the foregoing embodiments. A processor may include a circuit used for audio/video and logical functions of the terminal device. For example, the processor may include a digital signal processor device, a microprocessor device, an analog-to-digital converter, a digital-to-analog converter, and the like. Control and signal processing functions of a mobile device may be allocated between these devices based on respective capabilities of the devices. The processor may further include an internal voice coder VC, an internal data modem DM, and the like. In addition, the processor may include functions for operating one or more software programs, and the software programs may be stored in a memory. Usually, the processor and the stored software instruction may be configured to enable the terminal device to perform an action. For example, the processor can operate a connection program.

The terminal device may further include a user interface. The user interface may include, for example, a headset or loudspeaker, a microphone, an output apparatus (for example, a display), and an input apparatus. The user interface may be operationally coupled to the processor. In this case, the processor may include a user interface circuit, configured to control at least some functions of one or more elements (for example, the loudspeaker, the microphone, and the display) of the user interface. The processor and/or the user interface circuit included in the processor may be configured to control one or more functions of the one or more elements of the user interface by using a computer program instruction (for example, software and/or firmware) stored in a memory accessible to the processor. Although not shown, the terminal device may include a battery configured to supply power to various circuits related to the mobile device. The circuit is, for example, a circuit that provides mechanical vibration as detectable output. The input apparatus may include a device that allows the apparatus to receive data, such as a keypad, a touch display, a joystick, and/or at least one other input device.

The terminal device may further include one or more connection circuit modules configured to share and/or obtain data. For example, the terminal device may include a short-range radio frequency RF transceiver and/or detector, to share data with an electronic device and/or obtain data from an electronic device based on an RF technology. The terminal device may include other short-range transceivers, such as an infrared IR transceiver, a used transceiver, and a wireless universal serial bus USB transceiver. A Bluetooth transceiver can perform an operation based on a low-power or ultra-low-power Bluetooth technology. In this case, the terminal device, more specifically, the short-range transceiver, can send data to and/or receive data from an electronic device near the apparatus (for example, within <NUM> meters). Although not shown, the terminal device can send data to and/or receive data from the electronic device based on various wireless networking technologies, and these technologies include: Wi-Fi, Wi-Fi low power consumption, and WLAN technologies such as an IEEE <NUM> technology, an IEEE <NUM> technology, and an IEEE <NUM> technology.

The terminal device may include a memory that can store an information element related to a mobile user, such as a subscriber identity module SIM. In addition to the SIM, the apparatus may further include another removable and/or fixed memory. The terminal device may include a transitory memory and/or a non- transitory memory. For example, the transitory memory may include a random access memory RAM, and the RAM includes a dynamic RAM and/or a static RAM, an on-chip and/or off-chip buffer, and the like. The non- transitory memory may be embedded and/or removable. The non-transitory memory may include, for example, a read-only memory, a flash memory, a magnetic storage device such as a hard disk, a floppy disk drive, or a magnetic tape, an optical disc drive and/or a medium, a non-transitory random access memory NVRAM, and the like. Similar to the transitory memory, the non-transitory memory may include a buffer area used for temporary storage of data. At least a part of the transitory memory and/or the non-transitory memory may be embedded into the processor. The memory may store one or more software programs, instructions, information blocks, data, and the like. The memory may be used by the terminal device to perform a function of a mobile terminal. For example, the memory may include an identifier that can uniquely identify the terminal device, such as an international mobile equipment identity IMEI code.

Based on a same inventive concept, an embodiment of this application further provides an apparatus <NUM>. The apparatus <NUM> may be a network device, or may be a terminal device. As shown in <FIG>, the apparatus <NUM> includes at least a processor <NUM> and a memory <NUM>, may further include a transceiver <NUM>, and may further include a bus <NUM>.

The processor <NUM>, the memory <NUM>, and the transceiver <NUM> are all connected through the bus <NUM>.

The memory <NUM> is configured to store a computer execution instruction.

The processor <NUM> is configured to execute the computer execution instruction stored in the memory <NUM>.

When the apparatus <NUM> is a network device, the processor <NUM> executes the computer execution instruction stored in the memory <NUM>, so that the apparatus <NUM> performs a step performed by the primary network device in any one of the foregoing failure processing methods, or a functional unit corresponding to the step is deployed for the primary network device; or the apparatus <NUM> performs a step performed by the first primary network device in the foregoing handover method, or a functional unit corresponding to the step is deployed for the first primary network device.

When the apparatus <NUM> is a terminal device, the processor <NUM> executes the computer execution instruction stored in the memory <NUM>, so that the apparatus <NUM> performs a step performed by the terminal device in any one of the foregoing failure processing methods or the handover method provided in the embodiments of this application, or a functional unit corresponding to the step is deployed for the terminal device.

The processor <NUM> may include processors <NUM> of different types, or may include processors <NUM> of a same type. The processor <NUM> may be any one of the following devices having a computing and processing capability, such as a central processing unit (Central Processing Unit, CPU for short), an ARM processor (English full name of AMR: Advanced RISC Machines, English full name of RISC: Reduced Instruction Set Computing, Chinese translation: reduced instruction set), a field programmable gate array (Field Programmable Gate Array, FPGA for short), and a dedicated processor. In an optional implementation, the processor <NUM> may be integrated as a many-core processor. The memory <NUM> may be any one or any combination of the following storage media, such as a random access memory (Random Access Memory, RAM for short), a read-only memory (read only memory, ROM for short), a non-transitory memory (non-transitory memory, NVM for short), a solid state drive (Solid State Drives, SSD for short), a mechanical hard disk, a magnetic disk, and a disk array.

The transceiver <NUM> is used by the apparatus <NUM> to exchange data with another device. For example, if the apparatus <NUM> is a network device, the network device may perform the method performed by the network device in any one of the foregoing embodiments. The network device exchanges data with a terminal device by using the transceiver <NUM>. If the apparatus <NUM> is a terminal device, the terminal may perform the method performed by the terminal device in any one of the foregoing embodiments. The terminal device exchanges data with a network device by using the transceiver <NUM>. The transceiver <NUM> may be any one or any combination of the following devices having a network access function, such as a network interface (such as an Ethernet interface) and a wireless network interface card.

The bus <NUM> may include an address bus, a data bus, a control bus, and the like. For ease of representation, the bus is represented by using a thick line in <FIG>. The bus <NUM> may be any one or any combination of the following components for wired data transmission: an industry standard architecture (Industry Standard Architecture, ISA for short) bus, a peripheral component interconnect (Peripheral Component Interconnect, PCI for short) bus, an extended industry standard architecture (Extended Industry Standard Architecture, EISA for short) bus, and the like. An embodiment of this application provides a computer-readable storage medium, where the computer-readable storage medium stores a computer execution instruction. A processor of a terminal device executes the computer execution instruction, so that the terminal device performs a step performed by the terminal device in the foregoing failure processing methods and the handover method provided in this application, or a functional unit corresponding to the step is deployed for the terminal device.

An embodiment of this application provides a computer-readable storage medium, where the computer-readable storage medium stores a computer execution instruction. A processor of a network device executes the computer execution instruction, so that the network device performs a step performed by the primary network device in the foregoing failure processing methods provided in this application, or a functional unit corresponding to the step is deployed for the network device; or the network device performs a step performed by the first primary network device in the foregoing handover processing method provided in this application, or a functional unit corresponding to the step is deployed for the network device.

An embodiment of this application provides a computer program product. The computer program product includes a computer execution instruction, and the computer execution instruction is stored in a computer-readable storage medium. A processor of a terminal device may read the computer execution instruction from the computer-readable storage medium. The processor executes the computer execution instruction, so that the terminal device performs a step performed by the terminal device in the foregoing methods provided in the embodiments of this application, or a functional unit corresponding to the step is deployed for the terminal device.

An embodiment of this application provides a computer program product. The computer program product includes a computer execution instruction, and the computer execution instruction is stored in a computer-readable storage medium. A processor of a network device may read the computer execution instruction from the computer-readable storage medium. The processor executes the computer execution instruction, so that the network device performs a step performed by the primary network device in the foregoing failure processing methods provided in the embodiments of this application, or a functional unit corresponding to the step is deployed for the network device; or the network device performs a step performed by the first primary network device in the foregoing handover method provided in the embodiments of this application, or a functional unit corresponding to the step is deployed for the network device.

This application further provides a chip system. The chip system includes a processor, configured to support a terminal device in implementing functions in the foregoing aspects, for example, generating, receiving, or processing data and/or information in the foregoing methods. In a possible design, the chip system further includes a memory. The memory may be configured to store a program instruction and data that are necessary for the terminal device. The chip system may include a chip, or may include a chip and another discrete device.

This application further provides a chip system. The chip system includes a processor, configured to support a network device in implementing functions in the foregoing aspects, for example, generating, receiving, or processing data and/or information in the foregoing methods. In a possible design, the chip system further includes a memory. The memory is configured to store a program instruction and data that are necessary for the data receiving device. The chip system may include a chip, or may include a chip and another discrete device.

Based on a same inventive concept, this application further provides a terminal device <NUM>. As shown in <FIG>, the terminal device <NUM> includes a processing unit <NUM> and a transceiver unit <NUM>, and may be configured to perform the method performed by the terminal device in any one of the foregoing embodiments. Optionally, the processing unit <NUM> and the transceiver unit <NUM> are configured to:
The transceiver unit <NUM> is configured to receive a first RRC configuration of a secondary network device from the secondary network device.

The transceiver unit <NUM> is further configured to send first indication information to a primary network device, where the first indication information is used to indicate that the first RRC configuration fails.

Optionally, the transceiver unit <NUM> is further configured to send a first message to the primary network device, where the first message includes the first indication information.

Optionally, if a first unit of the terminal device receives second indication information sent by a second unit of the terminal device, the transceiver unit <NUM> is further configured to send the first indication information to the primary network device, where the second indication information is used to indicate that the first RRC configuration received from the secondary network device fails, the first unit is configured to control an RRC connection between the primary network device and the terminal device, and the second unit is configured to control an RRC connection between the secondary network device and the terminal device.

Optionally, the transceiver unit <NUM> is further configured to receive a new RRC configuration from the secondary network device.

The processing unit <NUM> and the transceiver unit <NUM> are further configured to:
The transceiver unit <NUM> is configured to receive a second RRC configuration of a secondary network device from a primary network device.

If the second RRC configuration fails, the transceiver unit <NUM> is further configured to send a second message to the primary network device, where the second message is used to request RRC connection reestablishment.

Optionally, if a first unit of the terminal device receives fourth indication information sent by a second unit of the terminal device, the transceiver unit <NUM> is further configured to send the second message to the primary network device, where the fourth indication information is used to indicate that the second RRC configuration received from the primary network device fails, the first unit is configured to control an RRC connection between the primary network device and the terminal device, and the second unit is configured to control an RRC connection between the secondary network device and the terminal device.

Optionally, the transceiver unit <NUM> is further configured to receive a third RRC configuration of the primary network device from the primary network device.

If the third RRC configuration fails, the processing unit <NUM> performs at least one of the following actions: stopping executing the second RRC configuration, releasing the second RRC configuration, and suspending a radio bearer of the secondary network device.

Optionally, if the second unit receives fifth indication information sent by the first unit, the processing unit <NUM> performs at least one of the following actions, where the fifth indication information is used to indicate that the third RRC configuration fails.

Based on a same inventive concept, this application further provides a network device <NUM>. As shown in <FIG>, the network device <NUM> includes a processing unit <NUM> and a transceiver unit <NUM>, and may be configured to perform the method performed by the primary network device in the foregoing failure processing methods. Optionally, the processing unit <NUM> and the transceiver unit <NUM> are configured to:
The transceiver unit <NUM> is configured to receive first indication information from a terminal device, where the first indication information is used to indicate that a first RRC configuration of a secondary network device fails, and the first RRC configuration is received by the terminal device from the secondary network device.

The transceiver unit <NUM> is further configured to send a first request message to the secondary network device, where the first request message is used to request the secondary network device to update an RRC configuration or request to release the secondary network device.

Optionally, the processing unit <NUM> and the transceiver unit <NUM> are further configured to:
If a second RRC configuration of a secondary network device fails, the transceiver unit <NUM> is configured to receive a second message from a terminal device, where the second message is used to indicate RRC connection reestablishment, and the second RRC configuration is received by the terminal device from the primary network device.

The transceiver unit <NUM> is further configured to initiate the RRC connection reestablishment to the terminal device. Optionally, the second message includes third indication information, and the indication information is used to indicate that the second RRC configuration fails.

Optionally, the processing unit <NUM> and the transceiver unit <NUM> are further configured to:
The transceiver unit <NUM> is configured to send a third message to a second primary network device, where the third message is used to request handover, and the third message includes a capability coordination result between the first primary network device and the secondary network device.

The transceiver unit <NUM> is further configured to receive a configuration of the second primary network device that is sent by the second primary network device, where the configuration of the second primary network device is associated with the capability coordination result.

Optionally, the transceiver unit <NUM> is further configured to receive a configuration of the secondary network device. The transceiver unit <NUM> is further configured to send the configuration of the second primary network device and the configuration of the secondary network device to the terminal device.

Optionally, the transceiver unit <NUM> is further configured to receive the configuration of the secondary network device from the second primary network device.

Optionally, if the configuration of the secondary network device fails, the transceiver unit <NUM> is further configured to receive a fourth message from the terminal device, where the fourth message is used to indicate RRC connection reestablishment.

Based on a same inventive concept, as shown in <FIG>, this application further provides a communications device <NUM>. The communications device <NUM> may be a terminal device, a baseband chip, or the like, and includes a first unit <NUM> and a second unit <NUM>. For details, refer to <FIG> and <FIG>. The first unit <NUM> and the second unit <NUM> may be configured to respectively perform functions performed by the first unit <NUM> and the second unit <NUM> in the foregoing failure processing methods. For details, refer to the foregoing description.

For example, the following describes some functions of the first unit <NUM> and the second unit <NUM>. The first unit <NUM> is configured to control an RRC connection between the primary network device and the terminal device, and the second unit <NUM> is configured to control an RRC connection between the secondary network device and the terminal device.

Optionally, the second unit <NUM> generates second indication information if the second unit <NUM> determines that a first RRC configuration of the secondary network device that is received by the terminal device from the secondary network device fails, where the second indication information is used to indicate that the first RRC configuration fails. The second unit <NUM> sends the second indication information to the first unit <NUM>.

Optionally, the second unit <NUM> generates fourth indication information if the second unit <NUM> determines that a second RRC configuration of the secondary network device that is received by the terminal device from the primary network device fails, where the fourth indication information is used to indicate that the second RRC configuration fails. The second unit <NUM> sends the fourth indication information to the first unit <NUM>.

Optionally, the first unit <NUM> generates fifth indication information if the first unit <NUM> determines that a third RRC configuration of the secondary network device that is received by the terminal device from the primary network device fails, where the fifth indication information is used to indicate that the third RRC configuration fails. The first unit <NUM> sends the fifth indication information to the second unit <NUM>.

Optionally, the second unit sends failure indication information to the first unit, where the failure indication is used to indicate that a link between the terminal device and the secondary network device fails; and the first unit receives the failure indication information. Optionally, the failure indication information is specifically used to indicate any one of the following cases: a timer expires, a quantity of retransmission times exceeds a maximum quantity of times, random access fails, a secondary-cell group change fails, a key fails, a check fails, integrity protection fails, a secondary network configuration received from the secondary network device fails, and a secondary network configuration received from a primary network fails.

When the failure indication information is used to indicate that the secondary network configuration received from the primary network fails, the failure indication information is the fourth indication information described above. Optionally, the first unit <NUM> is a first RRC entity, and the second unit <NUM> is a second RRC entity.

All or some of the foregoing embodiments may be implemented by using software, hardware, firmware, or any combination thereof. When software is used to implement the embodiments, the embodiments may be implemented completely or partially in a form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on the computer, all or some of the procedures or functions in this application are generated. The computer may be a general-purpose computer, a dedicated computer, a computer network, or other programmable apparatuses. The computer instructions may be stored in a computer-readable storage medium or may be transmitted from a computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions may be transmitted from a website, computer, server, or data center to another website, computer, server, or data center in a wired (for example, a coaxial cable, an optical fiber, or a digital subscriber line (Digital Subscriber Line, DSL for short)) or wireless (for example, infrared, radio, or microwave) manner. The computer-readable storage medium may be any usable medium accessible by a computer, or a data storage device, such as a server or a data center, integrating one or more usable media. The usable medium may be a magnetic medium (for example, a floppy disk, a hard disk, or a magnetic tape), an optical medium (for example, a DVD), a semiconductor medium (for example, a solid state disk (Solid State Disk, SSD for short)), or the like.

A person skilled in the art can further understand that, the various illustrative logical blocks (illustrative logical block) and the steps (step) listed in this application may be implemented through electronic hardware, computer software, or a combination of the two. Whether the functions are implemented by using hardware or software depends on particular applications and a design requirement of an entire system. A person skilled in the art may use various methods to implement the described functions for each particular application, but it should not be considered that the implementation goes beyond the protection scope of this application.

Various illustrative logic units and circuits described in this application may implement or operate the described functions by using a general-purpose processor, a digital signal processor, an application-specific integrated circuit (Application specific integrated circuit, ASIC for short), a field programmable gate array (Field-Programmable Gate Array, FPGA for short) or another programmable logic apparatus, a discrete gate or transistor logic, a discrete hardware component, or a design of any combination of the foregoing. The general-purpose processor may be a microprocessor. Optionally, the general-purpose processor may also be any conventional processor, controller, microcontroller, or state machine. The processor may alternatively be implemented by a combination of computing apparatuses, such as a digital signal processor and a microprocessor, a plurality of microprocessors, one or more microprocessors together with a digital signal processor core, or any other similar configuration.

Steps of the methods or algorithms described in this application may be directly embedded into hardware, a software unit executed by the processor, or a combination thereof. The software unit may be stored in a random access memory (Random-Access Memory, RAM for short), a flash memory, a read-only memory (Read-Only Memory, ROM for short), an erasable programmable read only memory (Erasable Programmable Read Only Memory, EPROM for short), a register, a hard disk, a removable disk, a compact disc read-only memory (Compact Disc Read-Only Memory, CD-ROM for short), or any other form of storage medium in the art. For example, the storage medium may be connected to the processor, so that the processor may read information from the storage medium and write information to the storage medium. Alternatively, the storage medium may be integrated into the processor.

The processor and the storage medium may be disposed in an ASIC, and the ASIC may be disposed in a terminal device or a network device. Optionally, the processor and the storage medium may be disposed in different components of the terminal device or the network device.

In one or more example designs, the functions described in this application may be implemented by using hardware, software, firmware, or any combination thereof. If the functions are implemented by using software, the functions may be stored in a computer-readable medium or are transmitted to the computer-readable medium in a form of one or more instructions or code. The computer-readable medium includes a computer storage medium and a communications medium that enables a computer program to move from one place to another place. The storage medium may be an available medium that can be accessed by any general-purpose or special computer. For example, such a computer-readable medium may include but is not limited to a RAM, a ROM, an EEPROM, a CD-ROM or another optical disc storage, a disk storage or another magnetic storage apparatus, or any other medium that may be used to bear or store program code, where the program code is in a form of an instruction or a data structure or in a form that can be read by a general-purpose or special computer or by a general-purpose or special processor. In addition, any connection may be appropriately defined as a computer-readable medium. For example, if software is transmitted from a website, a server, or another remote resource by using a coaxial cable, an optical fiber computer, a twisted pair, a digital subscriber line (DSL) or in a wireless manner, such as infrared, radio, or microwave, the software is included in a defined computer-readable medium. The disc (disk) and the disk (disc) include a compressed disk, a laser disk, an optical disc, a digital versatile disc (Digital Versatile Disc, DVD for short), a floppy disk, and a Blu-ray disc. The disk generally copies data by a magnetic means, and the disc generally copies data optically by a laser means. The foregoing combination may also be included in the computer-readable medium. A person skilled in the art should be aware that in one or more of the foregoing examples, the functions described in this application may be implemented by using hardware, software, firmware, or any combination thereof. When the functions are implemented by software, these functions may be stored in a computer-readable medium or transmitted as one or more instructions or code in the computer-readable medium. The computer-readable medium includes a computer storage medium and a communications medium, where the communications medium includes any medium that enables a computer program to be transmitted from one place to another. The storage medium may be any available medium accessible to a general-purpose or dedicated computer.

Claim 1:
A failure processing method, the method is applied to a terminal device (<NUM>, <NUM>, <NUM>, <NUM>) wherein the method comprising:
receiving (<NUM>) a first radio resource control, RRC, configuration of a secondary network device (<NUM>, <NUM>, <NUM>) from the secondary network device (<NUM>, <NUM>, <NUM>),
sending (<NUM>) first indication information to a primary network device (<NUM>, <NUM>, <NUM>), wherein the first indication information is used to indicate that the first RRC configuration fails,
receiving (<NUM>) a second RRC configuration of the secondary network device (<NUM>, <NUM>, <NUM>) from the primary network device (<NUM>, <NUM>, <NUM>),
sending (<NUM>) a second message to the primary network device (<NUM>, <NUM>, <NUM>) if the second RRC configuration fails, wherein the second message is used to request RRC connection reestablishment between the primary network device (<NUM>, <NUM>, <NUM>) and the terminal device (<NUM>, <NUM>, <NUM>, <NUM>),
wherein the primary network device (<NUM>, <NUM>, <NUM>) and the secondary network device (<NUM>, <NUM>, <NUM>) are base stations.