WO2019127292A1

WO2019127292A1 - Method and apparatus for controlling data replication transmission function

Info

Publication number: WO2019127292A1
Application number: PCT/CN2017/119606
Authority: WO
Inventors: 石聪
Original assignee: Oppo广东移动通信有限公司
Priority date: 2017-12-28
Filing date: 2017-12-28
Publication date: 2019-07-04
Also published as: CN109661831B; CN109661831A

Abstract

Embodiments of the present application provide a method and an apparatus for controlling a data replication transmission function of a terminal device. The invention can control a data replication transmission function between a cell group and a terminal device, and can avoid impacting on subsequent data transmissions when a transmission link is problematic. The method comprises: the terminal device suspending data transmissions on a first bearer when the data transmitted on the first bearer reaches the maximum number of retransmissions on a first radio link control (RLC) entity, the first bearer being a radio bearer for transmitting data in a data replication manner in a carrier aggregation (CA) scenario; and the terminal device reporting a radio link failure (RLF) message.

Description

Data copy transmission function control method and device

Technical field

Embodiments of the present invention relate to the field of communications, and, more particularly, to a method and apparatus for controlling a data copy transmission function.

Background technique

In a Carrier Aggregation (CA) scenario, multiple network nodes (Cell Groups, CGs) can serve terminal devices, and data replication can be transmitted between network nodes and terminal devices.

In some scenarios, for a specific bearer, when the data transmission on the Radio Link Control (RLC) entity of the bearer reaches the maximum number of transmissions, the data replication transmission function between the control network node and the terminal device needs to be controlled. To avoid impact on subsequent data transmission.

Summary of the invention

The embodiment of the present application provides a data copy transmission function control method and device, which can control a data replication transmission function between a network node and a terminal device to avoid impact on subsequent data transmission.

The first aspect provides a data copy transmission function control method, including: when the data transmitted on the first bearer reaches a maximum number of retransmissions on the first radio link control RLC entity, the terminal device suspends the A data transmission on a bearer, wherein the first bearer is a radio bearer that transmits data by means of data replication in a carrier aggregation CA scenario; the terminal device reports a radio link failure RLF message.

With reference to the first aspect, in a possible implementation manner of the first aspect, the first RLC entity is an RLC entity of a primary network node MCG or an RLC entity of a secondary network node SCG.

In conjunction with the first aspect, in a possible implementation manner of the first aspect, the first RLC entity of the first bearer transmits data only in a secondary cell.

In conjunction with the first aspect, in a possible implementation manner of the first aspect, the first bearer is a signaling radio bearer SRB or a data radio bearer DRB.

With reference to the first aspect, in a possible implementation manner of the first aspect, the terminal device suspending data transmission on the first bearer, including: the terminal device suspending the first bearer in a PDCP layer and an RLC Data transfer on the layer.

With reference to the first aspect, in a possible implementation manner of the first aspect, the terminal device suspending data transmission on the first bearer, including: the terminal device suspending the first bearer on an RLC layer data transmission.

With reference to the first aspect, in a possible implementation manner of the first aspect, the terminal device suspending data transmission of the first bearer on an RLC layer, including: the terminal device suspending the RLC layer Data transmission on the first RLC entity.

With reference to the first aspect, in a possible implementation manner of the first aspect, the terminal device suspending data transmission on the first bearer, including: the terminal device suspending data transmission on the first bearer, Simultaneously suspending the data transmission on the second bearer, wherein the second RLC entity of the second bearer performs a data transmission, and the first RLC entity uses the first RLC entity to perform data transmission. The sets of carriers at least partially overlap.

With reference to the first aspect, in a possible implementation manner of the first aspect, the second RLC entity performs a data transmission, and performs data transmission with the first RLC entity of the first bearer. At least partially overlapping between the used sets of carriers, including: a set of carriers used by the second RLC entity for data transmission, and a carrier set used for data transmission by the first RLC entity of the first bearer; Or the carrier set used by the second RLC entity to perform data transmission, including a carrier set used by the first RLC entity of the first bearer for data transmission; or the second RLC entity performs data transmission. There is an intersection between the set of carriers used and the set of carriers used for data transmission by the first RLC entity of the first bearer.

With reference to the first aspect, in a possible implementation manner of the first aspect, the second bearer is a radio bearer that transmits data by means of data replication in a CA scenario.

With reference to the first aspect, in a possible implementation manner of the first aspect, the terminal device simultaneously suspending data transmission on the second bearer, including: the terminal device suspending the second bearer in a PDCP layer and an RLC layer Data transfer on.

With reference to the first aspect, in a possible implementation manner of the first aspect, the terminal device simultaneously suspending data transmission on the second bearer, including: the terminal device suspending data of the second bearer on the RLC layer transmission.

With reference to the first aspect, in a possible implementation manner of the first aspect, the terminal device suspending data transmission of the second bearer on an RLC layer, including: the terminal device suspending the RLC layer Data transmission on the second RLC entity.

With reference to the first aspect, in a possible implementation manner of the first aspect, the terminal device suspending data transmission on the first bearer, including: the terminal device suspending data transmission on the first bearer, At the same time, the data transmission on the third bearer is suspended, wherein the third RLC entity of the third bearer performs data transmission in the secondary cell.

With reference to the first aspect, in a possible implementation manner of the first aspect, the third bearer is a radio bearer that transmits data by means of data replication in a CA scenario.

With reference to the first aspect, in a possible implementation manner of the first aspect, the terminal device simultaneously suspending data transmission on the third bearer, including: the terminal device suspending the third bearer in a PDCP layer and an RLC layer Data transfer on.

With reference to the first aspect, in a possible implementation manner of the first aspect, the terminal device simultaneously suspending data transmission on the third bearer, including: the terminal device suspending data of the third bearer on the RLC layer transmission.

With reference to the first aspect, in a possible implementation manner of the first aspect, the terminal device suspending data transmission of the third bearer on an RLC layer, including: the terminal device suspending the RLC layer Data transmission on the third RLC entity.

With reference to the first aspect, in a possible implementation manner of the first aspect, the terminal device that reports the RLF message includes: the terminal device sends the RLF message by using a first SRB, where the first SRB ends in the MCG .

With reference to the first aspect, in a possible implementation manner of the first aspect, the terminal device sends the RLF message by using the first SRB, where the terminal device passes the RLC entity of the MCG of the first SRB, Send the RLF message.

With reference to the first aspect, in a possible implementation manner of the first aspect, the terminal device sends the RLF message by using the first SRB, where the terminal device passes the RLC entity of the SCG of the first SRB, Send the RLF message.

With reference to the first aspect, in a possible implementation manner of the first aspect, the terminal device sends the RLF message by using the first SRB, where the terminal device passes the RLC entity of the MCG of the first SRB and The RLC entity of the SCG sends the RLF message.

With reference to the first aspect, in a possible implementation of the first aspect, the terminal device sends the RLF message by using an RLC entity of the MCG of the first SRB, including: the terminal device passes the The fourth RLC entity of the MCG of an SRB transmits the RLF message, and the fourth RLC entity transmits data using only the secondary cell.

With reference to the first aspect, in a possible implementation of the first aspect, the terminal device sends the RLF message by using an RLC entity of the MCG of the first SRB, including: the terminal device passes the The fifth RLC entity of the MCG of an SRB transmits the RLF message, and the fifth RLC entity is capable of transmitting data using the primary cell.

With reference to the first aspect, in a possible implementation of the first aspect, the terminal device sends the RLF message by using an RLC entity of the MCG of the first SRB, including: the terminal device passes the The fourth RLC entity of the MCG of an SRB and the fifth RLC entity transmit the RLF message, the fourth RLC entity uses only the secondary cell to transmit data, and the fifth RLC entity can transmit data using the primary cell.

With reference to the first aspect, in a possible implementation manner of the first aspect, the terminal device that reports the RLF message includes: the terminal device sends the RLF message by using a second SRB, where the second SRB ends in the SCG .

With reference to the first aspect, in a possible implementation manner of the first aspect, the terminal device sends the RLF message by using a second SRB, where the terminal device passes the sixth RLC of the SCG of the second SRB The entity sends the RLF message, and the sixth RLC entity only uses the secondary cell to transmit data.

With reference to the first aspect, in a possible implementation manner of the first aspect, the terminal device sends the RLF message by using a second SRB, where the terminal device passes the seventh RLC of the SCG of the second SRB The entity sends the RLF message, and the seventh RLC entity can transmit data using the primary cell.

With reference to the first aspect, in a possible implementation manner of the first aspect, the terminal device sends the RLF message by using a second SRB, where the terminal device passes the sixth RLC of the SCG of the second SRB The entity and the seventh RLC entity transmit the RLF message, the sixth RLC entity uses only the secondary cell to transmit data, and the seventh RLC entity can transmit data using the primary cell.

The second aspect provides a data copy transmission function control method, including: the network device receives a radio link failure RLF message reported by the terminal device, where the RLF message is used to indicate that the terminal device transmits on the first bearer. The data reaches a maximum number of retransmissions on the first radio link control RLC entity, where the first bearer is a radio bearer that transmits data by means of data replication in a carrier aggregation CA scenario.

With reference to the second aspect, in a possible implementation manner of the second aspect, the first RLC entity is an RLC entity of the primary network node MCG or an RLC entity of the secondary network node SCG.

With reference to the second aspect, in a possible implementation manner of the second aspect, the first RLC entity of the first bearer transmits data only in a secondary cell.

With reference to the second aspect, in a possible implementation manner of the second aspect, the first bearer is a signaling radio bearer SRB or a data radio bearer DRB.

With reference to the second aspect, in a possible implementation manner of the second aspect, the receiving, by the network device, the RLF message that is reported by the terminal device, the network device, by using the first SRB, receiving the RLF sent by the terminal device The message, the first SRB is cut off by the MCG.

With reference to the second aspect, in a possible implementation manner of the second aspect, the network device, by using the first SRB, to receive the RLF message sent by the terminal device, includes: the network device passing the first SRB The RLC entity of the MCG receives the RLF message sent by the terminal device.

With reference to the second aspect, in a possible implementation manner of the second aspect, the network device, by using the first SRB, to receive the RLF message sent by the terminal device, includes: the network device passing the first SRB The RLC entity of the SCG receives the RLF message sent by the terminal device.

With reference to the second aspect, in a possible implementation manner of the second aspect, the network device, by using the first SRB, to receive the RLF message sent by the terminal device, includes: the network device passing the first SRB The RLC entity of the MCG and the RLC entity of the SCG receive the RLF message sent by the terminal device.

With reference to the second aspect, in a possible implementation manner of the second aspect, the network device, by using the RLC entity of the MCG of the first SRB, receiving the RLF message sent by the terminal device, including: The network device receives the RLF message sent by the terminal device by using a fourth RLC entity of the MCG of the first SRB, where the fourth RLC entity transmits data only in the secondary cell.

With reference to the second aspect, in a possible implementation manner of the second aspect, the network device, by using the RLC entity of the MCG of the first SRB, receiving the RLF message sent by the terminal device, including: The network device receives the RLF message sent by the terminal device by using a fifth RLC entity of the MCG of the first SRB, where the fifth RLC is capable of transmitting data in the primary cell.

With reference to the second aspect, in a possible implementation manner of the second aspect, the network device, by using the RLC entity of the MCG of the first SRB, receiving the RLF message sent by the terminal device, including: Receiving, by the fourth RLC entity and the fifth RLC entity of the MCG of the first SRB, the RLF message sent by the terminal device, where the fourth RLC entity transmits data only in the secondary cell, the fifth RLC The entity is capable of transmitting data in the primary cell.

With reference to the second aspect, in a possible implementation manner of the second aspect, the receiving, by the network device, the RLF message that is reported by the terminal device, the network device, by using the second SRB, receiving the RLF sent by the terminal device The message, the second SRB is cut off by the SCG.

With reference to the second aspect, in a possible implementation manner of the second aspect, the network device, by using the second SRB, receiving the RLF message sent by the terminal device, includes: the network device adopting the second The sixth RLC entity of the SCG of the SRB receives the RLF message sent by the terminal device, and the sixth RLC entity uses only the secondary cell to transmit data.

With reference to the second aspect, in a possible implementation manner of the second aspect, the network device, by using the second SRB, receiving the RLF message sent by the terminal device, includes: the network device adopting the second The seventh RLC entity of the SCG of the SRB receives the RLF message sent by the terminal device, and the seventh RLC entity is capable of transmitting data using the primary cell.

With reference to the second aspect, in a possible implementation manner of the second aspect, the network device, by using the second SRB, receiving the RLF message sent by the terminal device, includes: the network device adopting the second The sixth RLC entity and the seventh RLC entity of the SCG of the SRB receive the RLF message sent by the terminal device, the sixth RLC entity uses only the secondary cell to transmit data, and the seventh RLC entity can use the primary cell to transmit data. .

In a third aspect, a terminal device is provided for performing the method of any of the above first aspect or any of the possible implementations of the first aspect. In particular, the terminal device comprises functional modules for performing the method of the first aspect or any of the possible implementations of the first aspect described above.

In a fourth aspect, a terminal device is provided, including a processor, a memory, and a transceiver. The processor, the memory, and the transceiver communicate with each other through an internal connection path, transmitting control and/or data signals, such that the network device performs the first aspect or any possible implementation of the first aspect The method in .

In a fifth aspect, a network device is provided for performing the method of any of the foregoing second aspect or any of the possible implementations of the second aspect. In particular, the control device comprises functional modules for performing the method of any of the possible implementations of the second aspect or the second aspect described above.

In a sixth aspect, a network device is provided, including a processor, a memory, and a transceiver. The processor, the memory, and the transceiver communicate with each other through an internal connection path, transmitting control and/or data signals, such that the network device performs any of the second or second aspects of the foregoing possible implementations The method in .

In a seventh aspect, a computer readable medium is provided for storing a computer program, the computer program comprising instructions for performing any one of the methods described above or any possible implementation.

Therefore, in the embodiment of the present application, when data transmission is performed by using the data replication mode in the CA scenario, when the RLC entity of the MCG or the SCG reaches the maximum number of retransmissions, the terminal device suspends transmission of at least part of the data on the radio bearer. The RLF message is reported, thereby realizing the control of the data replication transmission function of the terminal device, and when the transmission link has a problem, the influence on the subsequent data transmission can be avoided.

DRAWINGS

FIG. 1 is a schematic diagram of a protocol architecture of data replication according to an embodiment of the present application.

2 is a schematic diagram of a protocol architecture of data replication in accordance with an embodiment of the present application.

FIG. 3 is a schematic flowchart of a method for controlling a data replication transmission function of a terminal device according to an embodiment of the present application.

FIG. 4 is a schematic block diagram of a terminal device according to an embodiment of the present application.

FIG. 5 is a schematic block diagram of a network device according to an embodiment of the present application.

FIG. 6 is a schematic block diagram of a system chip in accordance with an embodiment of the present application.

FIG. 7 is a schematic block diagram of a communication device in accordance with an embodiment of the present application.

Detailed ways

The technical solutions in the embodiments of the present application will be described below with reference to the accompanying drawings.

It should be understood that the technical solutions of the embodiments of the present application can be applied to various communication systems, such as a Global System of Mobile Communication (GSM) system, a Code Division Multiple Access (CDMA) system, and a wideband code. Wideband Code Division Multiple Access (WCDMA) system, Long Term Evolution (LTE) system, LTE Frequency Division Duplex (FDD) system, LTE Time Division Duplex (TDD) , Universal Mobile Telecommunication System (UMTS), and future 5G communication systems.

The present application describes various embodiments in connection with a terminal device. The terminal device may also refer to a user equipment (User Equipment, UE), an access terminal, a subscriber unit, a subscriber station, a mobile station, a mobile station, a remote station, a remote terminal, a mobile device, a user terminal, a terminal, a wireless communication device, and a user agent. Or user device. The access terminal may be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA), with wireless communication. Functional handheld devices, computing devices or other processing devices connected to wireless modems, in-vehicle devices, wearable devices, terminal devices in future 5G networks, or future evolved land-based public land mobile network (PLMN) networks Terminal equipment, etc.

The present application describes various embodiments in connection with a network device. The network device may be a device for communicating with the terminal device, for example, may be a base station (Base Transceiver Station, BTS) in the GSM system or CDMA, or may be a base station (NodeB, NB) in the WCDMA system, or may be An evolved base station (Evolutional Node B, eNB or eNodeB) in an LTE system, or the network device may be a relay station, an access point, an in-vehicle device, a wearable device, and a network side device in a future 5G network or a future evolved PLMN network. Network side devices, etc.

In a 5G system, multiple network nodes (Cell Groups, CGs) can serve terminal devices, and cell groups and terminal devices can be transmitted by means of data replication.

It should be understood that in the embodiment of the present application, the CG may be equivalent to a network node or a network device or the like.

Optionally, the protocol architecture of the data replication transmission mode may be as shown in FIG. 1 and FIG. 2. The data replication transmission mode adopts a protocol scheme of a split bearer; for uplink and downlink, a Packet Data Convergence Protocol (PDCP) is located in a certain CG (Master CG (MCG)). Or SCG (Secondary CG, SCG)), which is the anchor CG (anchor CG). In any CG, PDCP can copy PDCP Protocol Data Units (PDUs) into the same two copies, such as one PDCP PDU, one Duplicated PDCP PDU, and two PDCPs through different CG wireless. The Layer Link Control (RLC) layer and the Media Access Control (MAC) layer reach the corresponding MAC and RLC layers of the terminal (downlink) or the base station (uplink) through the air interface, and finally converge to the PDCP. The PDCP layer detects that two PDCPs are the same duplicate version, that is, discard one of them and submit the other to the upper layer.

When the number of data transmissions on the RLC entity reaches the maximum number of retransmissions, it is necessary to control the data replication transmission function between the control network node and the terminal device to avoid impact on subsequent data transmission.

To this end, the embodiments of the present application provide the following solutions to solve the problem, thereby implementing control of the data copy transmission function of the terminal device.

FIG. 3 is a flow interaction diagram of a control method 300 of a data copy transmission function according to an embodiment of the present application. The method 300 includes at least some of the following.

In 310, when the data transmitted on the first bearer reaches the maximum number of retransmissions on the first RLC entity, the terminal device suspends data transmission on the first bearer.

The first bearer is a radio bearer that transmits data by means of data replication in a CA scenario.

Specifically, in the data transmitted on the first bearer, if the maximum number of retransmissions is reached on the first RLC entity during the transmission, the terminal device may suspend transmission of at least part of the data on the first bearer.

Optionally, the first RLC entity may be an RLC entity of the primary network node MCG or an RLC entity of the secondary network node SCG.

Optionally, the first RLC entity of the first bearer transmits data only in the secondary cell.

Optionally, the first bearer is a Signaling Radio Bearer (SRB) or a Data Radio Bearer (DRB).

Optionally, in 310, the terminal device suspends data transmission on the first bearer, including: the terminal device suspending data transmission of the first bearer on the PDCP layer and the RLC layer.

Optionally, in 310, the terminal device suspends data transmission on the first bearer, including: the terminal device suspending data transmission of the first bearer on the RLC layer.

Further, optionally, the terminal device suspends data transmission of the first bearer on the RLC layer, including: the terminal device suspending data transmission on the first RLC entity of the RLC layer.

Specifically, when the data transmission on the first RLC entity reaches the maximum number of retransmissions, the terminal device may suspend transmission of at least part of the data on the first bearer. For example, the transmission of all data on the first bearer may be suspended; or the data transmission of the first bearer on the PDCP layer and the RLC layer may be suspended; or, the data transmission of the first bearer on the RLC layer may be suspended only; or Only the data transmission of the first bearer on the first RLC entity of the RLC layer is suspended.

Optionally, in 310, the terminal device suspends data transmission on the first bearer, including: the terminal device suspending data transmission on the first bearer, and suspending data transmission on the second bearer. The carrier set used for data transmission by the second RLC entity of the second bearer at least partially overlaps with the carrier set used by the first RLC entity of the first bearer for data transmission.

That is, since there is an overlap between the set of carriers mapped by the second RLC entity of the second bearer and the set of carriers mapped by the first RLC entity of the first bearer, when the data transmission on the first bearer is suspended, The data transmission on the second bearer can be suspended at the same time.

The carrier set used for data transmission by the second RLC entity at least partially overlaps with the carrier set used by the first RLC entity for performing data transmission, including: the second RLC entity performs data The set of carriers used for the transmission is the same as the set of carriers used for data transmission by the first RLC entity of the first bearer; or the set of carriers used by the second RLC entity for data transmission, including the first bearer a set of carriers used by the first RLC entity for data transmission; or a set of carriers used by the second RLC entity for data transmission, and a carrier set used for data transmission by the first RLC entity of the first bearer There is an intersection.

Optionally, the second bearer is a radio bearer that transmits data by means of data replication in a CA scenario.

Optionally, the terminal device simultaneously suspends data transmission on the second bearer, including: the terminal device suspending data transmission of the second bearer on the PDCP layer and the RLC layer.

Optionally, the terminal device simultaneously suspends data transmission on the second bearer, including: the terminal device suspending data transmission of the second bearer on the RLC layer.

Further, optionally, the terminal device suspends data transmission of the second bearer on the RLC layer, including: the terminal device suspending data transmission on the second RLC entity of the RLC layer.

For the second bearer, the terminal device may suspend transmission of all data on the second bearer when the data of the first RLC entity reaches the maximum number of retransmissions; or, the second bearer may be suspended on the PDCP layer and the RLC layer. Data transmission; or, may only suspend data transmission of the second bearer on the RLC layer; or only suspend data transmission of the second bearer on the second RLC entity of the RLC layer, for example, only suspending the carrier set in the second bearer The RLC entity that overlaps with the set of carriers corresponding to the first RLC entity.

Optionally, in 310, the terminal device suspends data transmission on the first bearer, including: the terminal device suspends data transmission on the first bearer, and suspends data transmission on the third bearer. The third RLC entity of the third bearer performs data transmission only in the secondary cell.

That is, since the third RLC entity of the third bearer performs data transmission only in the secondary cell, that is, the carrier set mapped by the third RLC entity of the third bearer includes only the secondary carrier, then the first bearer is suspended. When data is transmitted, data transmission on the third bearer can also be suspended at the same time.

Optionally, the third bearer is a radio bearer that transmits data by means of data replication in a CA scenario.

Optionally, the terminal device simultaneously suspends data transmission on the third bearer, including: the terminal device suspending data transmission of the third bearer on the PDCP layer and the RLC layer.

Optionally, the terminal device simultaneously suspends data transmission on the third bearer, including: the terminal device suspending data transmission of the third bearer on the RLC layer.

Further, optionally, the terminal device suspends data transmission of the third bearer on the RLC layer, including: the terminal device suspending data transmission on the third RLC entity of the RLC layer.

For the third bearer, the terminal device may suspend transmission of all data on the third bearer when the data on the first RLC entity reaches the maximum number of retransmissions; or, the third bearer may be suspended on the PDCP layer and the RLC layer. Data transmission; or, may only suspend data transmission of the third bearer on the RLC layer; or only suspend data transmission of the third bearer on the third RLC entity of the RLC layer, for example, only pause the third bearer only The RLC entity that transmits data in the secondary cell.

Of course, the terminal device can also suspend data transmission on the first bearer, the second bearer, and the third bearer at the same time.

In 320, the terminal device reports an RLF message.

Specifically, if the data transmitted on the first bearer reaches the maximum number of retransmissions on the first RLC entity, the terminal device reports the wireless transmission to the network device while suspending transmission of at least part of the data on the first bearer. A link failure (Rain Link Failure, RLF) message, so that the network device receives the RLF message reported by the terminal device, and can instruct the terminal device to control the data replication transmission function according to the received RLF message, for example, deactivating the terminal The data replication transmission function of the first bearer of the device, or the configuration of the first bearer or the like.

The RLF message is used to indicate that the data transmitted on the first bearer of the terminal device reaches the maximum number of retransmissions on the first RLC entity.

In this embodiment, the terminal device may report the RLF message to the network device by using the first SRB or the second SRB, which are respectively described below.

Mode 1

Optionally, in 320, the terminal device reports the RLF message, including: the terminal device sends the RLF message by using the first SRB, where the first SRB ends in the MCG.

The first SRB may also be referred to as SRB1, and the SRB1 is cut off from the MCG and may be used to transmit RRC signaling. The SRB1 may be transmitted and processed by the MCG, or may be transmitted to the MCG through the SCG and processed by the MCG for the control signaling carried by the SRB1.

Optionally, the terminal device sends the RLF message by using the first SRB, where the terminal device sends the RLF message by using an RLC entity of the MCG of the first SRB.

Optionally, the terminal device sends the RLF message by using the first SRB, where the terminal device sends the RLF message by using an RLC entity of the SCG of the first SRB.

Optionally, the terminal device sends the RLF message by using the first SRB, where the terminal device sends the RLF message by using an RLC entity of the MCG of the first SRB and an RLC entity of the SCG.

For example, if the RLF message is not reported in the manner of data replication, the RLF message may be carried in the SRB1 and reported through the path (MCG path) of the MCG. If the RLF message is reported by means of data replication, the RLF message may be carried in the SRB1 and reported through the path of the MCG and the path of the SCG (SCG path), or reported by the SCG path.

And, further, when the RLF message is reported by the MCG path, optionally, the terminal device sends the RLF message by using a fourth RLC entity of the MCG of the first SRB; or the terminal device passes the first SRB. The fifth RLC entity sends the RLF message; or the terminal device simultaneously sends the RLF message by using the fourth RLC entity and the fifth RLC entity of the MCG of the first SRB. The fourth RLC entity transmits data only on the secondary cell, and the fifth RLC entity is capable of transmitting data on the primary carrier and the secondary carrier.

In other words, in the MCG path, the RLF message may be transmitted through the SRB1 of the fourth RLC entity, when the RLF message is transmitted only in the secondary cell (secondary carrier); or the RLF message may be transmitted through the fifth RLC entity, which The RLF message may be transmitted by the primary carrier (primary cell) or the secondary cell (secondary carrier); or the RLF message may be simultaneously transmitted on the fourth RLC entity and the fifth RLC entity.

Mode 2

Optionally, in 320, the terminal device reports the RLF message, including: the terminal device sends the RLF message by using the second SRB, where the second SRB ends in the SCG.

The second SRB may also be referred to as SRB3, and the SRB3 is cut off from the SCG. The SRB3 is only transmitted on the SCG path, and the terminal device processes the SRB3 after receiving the SRB3 on the SCG.

Optionally, the terminal device sends the RLF message by using the second SRB, where the terminal device sends the RLF message by using a sixth RLC entity of the SCG of the second SRB, where the sixth RLC entity uses only the secondary cell to transmit data.

Optionally, the terminal device sends the RLF message by using the second SRB, where the terminal device sends the RLF message by using a seventh RLC entity of the SCG of the second SRB, where the seventh RLC entity can use the primary cell to transmit data.

Optionally, the terminal device sends the RLF message by using the second SRB, where the terminal device sends the RLF message by using the sixth RLC entity and the seventh RLC entity of the SCG of the second SRB, where the sixth RLC entity is only used. The secondary cell transmits data, and the seventh RLC entity can transmit data using the primary cell.

In other words, in the SCG path, the RLF message may be transmitted through the SRB1 of the sixth RLC entity, when the RLF message is transmitted only in the secondary cell (secondary carrier); or the RLF message may be transmitted through the seventh RLC entity, which The RLF message may be transmitted by the primary carrier (primary cell) or the secondary cell (secondary carrier); or the RLF message may also be simultaneously transmitted on the sixth RLC entity and the seventh RLC entity.

In 330, the network device receives the RLF message reported by the terminal device.

Similarly, in the embodiment of the present application, the network device may also receive the RLF message reported by the terminal device by using the first SRB or the second SRB.

Optionally, in 330, the network device receives the RLF message reported by the terminal device, where the network device receives the RLF message sent by the terminal device by using the first SRB, where the first SRB ends in the MCG.

Optionally, the network device receives the RLF message sent by the terminal device by using the first SRB, where the network device receives the RLF message sent by the terminal device by using an RLC entity of the MCG of the first SRB.

Optionally, the network device receives the RLF message sent by the terminal device by using the first SRB, and the network device receives the RLF message sent by the terminal device by using an RLC entity of the SCG of the first SRB.

Optionally, the network device receives the RLF message sent by the terminal device by using the first SRB, where the network device receives the RLF sent by the terminal device by using an RLC entity of the MCG of the first SRB and an RLC entity of the SCG. Message.

Further, optionally, the network device receives the RLF message sent by the terminal device by using an RLC entity of the MCG of the first SRB, where the network device receives the fourth RLC entity of the MCG of the first SRB. The RLF message sent by the terminal device, the fourth RLC entity only transmits data in the secondary cell.

Optionally, the network device receives the RLF message sent by the terminal device by using an RLC entity of the MCG of the first SRB, where the network device receives, by using the fifth RLC entity of the MCG of the first SRB, the terminal device to send The RLF message, the fifth RLC entity is capable of transmitting data in the primary cell.

Optionally, the network device receives the RLF message sent by the terminal device by using an RLC entity of the MCG of the first SRB, where the network device passes the fourth RLC entity and the fifth RLC entity of the MCG of the first SRB. Receiving the RLF message sent by the terminal device, the fourth RLC entity transmits data only in the secondary cell, and the fifth RLC entity is capable of transmitting data in the primary cell.

Optionally, in 330, the network device receives the RLF message that is reported by the terminal device, and the network device receives the RLF message sent by the terminal device by using the second SRB, where the second SRB ends in the SCG.

Optionally, the network device receives the RLF message sent by the terminal device by using the second SRB, where the network device receives the RLF message sent by the terminal device by using a sixth RLC entity of the SCG of the second SRB. The sixth RLC entity only uses the secondary cell to transmit data.

Optionally, the network device receives the RLF message sent by the terminal device by using the second SRB, where the network device receives, by using a seventh RLC entity of the SCG of the second SRB, the RLF message sent by the terminal device, where the The seven RLC entities are capable of transmitting data using the primary cell.

Optionally, the network device receives the RLF message sent by the terminal device by using the second SRB, where the network device receives, by using the sixth RLC entity and the seventh RLC entity of the SCG of the second SRB, the terminal device The RLF message, the sixth RLC entity uses only the secondary cell to transmit data, and the seventh RLC entity can use the primary cell to transmit data.

The first SRB is, for example, SRB1, and the second SRB is, for example, SRB3.

Therefore, when data transmission is performed by using the data replication mode in the CA scenario, when the RLC entity of the MCG or the SCG reaches the maximum number of retransmissions, the terminal device suspends transmission of at least part of the data on the radio bearer and reports the RLF message. The control of the data replication transmission function of the terminal device can avoid the influence on the subsequent data transmission when there is a problem in the transmission link.

FIG. 4 is a schematic block diagram of a terminal device 400 according to an embodiment of the present application. As shown in FIG. 4, the terminal device 400 includes a processing unit 410 and a transmitting unit 220, where:

The processing unit 410 is configured to: suspend data transmission on the first bearer when the data transmitted on the first bearer reaches a maximum number of retransmissions on the first radio link control RLC entity, where the first bearer A radio bearer that transmits data in a CA scenario by means of data replication;

The sending unit 420 is configured to: report an RLF message.

The first RLC entity is an RLC entity of the primary network node MCG or an RLC entity of the secondary network node SCG.

Optionally, the first bearer is a signaling radio bearer SRB or a data radio bearer DRB.

Optionally, the processing unit 410 is specifically configured to: suspend data transmission of the first bearer on the PDCP layer and the RLC layer.

Optionally, the processing unit 410 is specifically configured to: suspend data transmission of the first bearer on the RLC layer.

Optionally, the processing unit 410 is specifically configured to: suspend data transmission on the first RLC entity of the RLC layer.

Optionally, the processing unit 410 is specifically configured to: suspend data transmission on the first bearer, and suspend data transmission on the second bearer, where the second RLC entity of the second bearer performs data transmission. The set of carriers used at least partially overlaps with a set of carriers used by the first RLC entity of the first bearer for data transmission.

Optionally, the set of carriers used by the second RLC entity of the second bearer to perform data transmission at least partially overlaps with the set of carriers used by the first RLC entity of the first bearer for data transmission, The carrier set used by the second RLC entity for data transmission is the same as the carrier set used for data transmission by the first RLC entity of the first bearer, or the second RLC entity performs data transmission. The set of carriers used includes: a set of carriers used by the first RLC entity of the first bearer for data transmission; or a set of carriers used by the second RLC entity for data transmission, and the first There is an intersection between the set of carriers used by the first RLC entity for data transmission.

Optionally, the processing unit 410 is specifically configured to: suspend data transmission of the second bearer on the PDCP layer and the RLC layer.

Optionally, the processing unit 410 is specifically configured to: suspend data transmission of the second bearer on the RLC layer.

Optionally, the processing unit 410 is specifically configured to: suspend data transmission on the second RLC entity of the RLC layer.

Optionally, the processing unit 410 is specifically configured to: suspend data transmission on the first bearer, and suspend data transmission on the third bearer, where the third RLC entity of the third bearer is only in the secondary cell. Data transfer.

Optionally, the processing unit 410 is specifically configured to: suspend data transmission of the third bearer on the PDCP layer and the RLC layer.

Optionally, the processing unit 410 is specifically configured to: suspend data transmission of the third bearer on the RLC layer.

Optionally, the processing unit 410 is specifically configured to: suspend data transmission on the third RLC entity of the RLC layer.

Optionally, the sending unit 420 is specifically configured to: send, by using the first SRB, the RLF message, where the first SRB ends in the MCG.

Optionally, the sending unit 420 is specifically configured to: send, by using an RLC entity of the MCG of the first SRB, the RLF message.

Optionally, the sending unit 420 is specifically configured to: send, by using an RLC entity of the SCG of the first SRB, the RLF message.

Optionally, the sending unit 420 is specifically configured to: send the RLF message by using an RLC entity of the MCG of the first SRB and an RLC entity of the SCG.

Optionally, the sending unit 420 is specifically configured to: send, by using a fourth RLC entity of the MCG of the first SRB, the RLF message, where the fourth RLC entity uses only the secondary cell to transmit data.

Optionally, the sending unit 420 is specifically configured to: send, by using a fifth RLC entity of the MCG of the first SRB, the RLF message, where the fifth RLC entity can use the primary cell to transmit data.

Optionally, the sending unit 420 is specifically configured to: send, by using a fourth RLC entity and a fifth RLC entity of the MCG of the first SRB, the RLF message, where the fourth RLC entity uses only the secondary cell to transmit data, The fifth RLC entity is capable of transmitting data using the primary cell.

Optionally, the sending unit 420 is specifically configured to: send, by using the second SRB, the RLF message, where the second SRB ends in the SCG.

Optionally, the sending unit 420 is specifically configured to: send, by using a sixth RLC entity of the SCG of the second SRB, the RLF message, where the sixth RLC entity uses only the secondary cell to transmit data.

Optionally, the sending unit 420 is specifically configured to: send, by using a seventh RLC entity of the SCG of the second SRB, the RLF message, where the seventh RLC entity can use the primary cell to transmit data.

Optionally, the sending unit 420 is specifically configured to: send, by using the sixth RLC entity and the seventh RLC entity of the SCG of the second SRB, the RLF message, where the sixth RLC entity uses only the secondary cell to transmit data, The seventh RLC entity is capable of transmitting data using the primary cell.

It should be understood that the terminal device 400 may correspond to the terminal device in the method 300, and the operations implemented by the terminal device in the method 300 may be implemented. For brevity, no further details are provided herein.

FIG. 5 is a schematic block diagram of a network device 500 in accordance with an embodiment of the present application. As shown in FIG. 5, the terminal device 500 includes a receiving unit 510, configured to:

Receiving, by the terminal device, an RLF message, where the RLF message is used to indicate that the data transmitted on the first bearer of the terminal device reaches a maximum number of retransmissions on the first radio link control RLC entity, where the first bearer A radio bearer that transmits data in a carrier aggregation CA scenario by means of data replication.

Therefore, when data transmission is performed by using the data replication mode in the CA scenario, when the RLC entity of the MCG or the SCG reaches the maximum number of retransmissions, the network device device receives the RLF message reported by the terminal device, thereby implementing the data replication transmission function of the terminal device. Control, when there is a problem with the transmission link, can avoid the impact on subsequent data transmission.

Optionally, the first RLC entity is an RLC entity of the primary network node MCG or an RLC entity of the secondary network node SCG.

Optionally, the receiving unit 510 is specifically configured to: receive, by using the first SRB, the RLF message sent by the terminal device, where the first SRB ends in an MCG.

Optionally, the receiving unit 510 is specifically configured to: receive, by the network device, the RLF message sent by the terminal device by using an RLC entity of the MCG of the first SRB.

Optionally, the receiving unit 510 is specifically configured to: receive, by using an RLC entity of the SCG of the first SRB, the RLF message sent by the terminal device.

Optionally, the receiving unit 510 is specifically configured to: receive, by using an RLC entity of an MCG of the first SRB and an RLC entity of the SCG, the RLF message sent by the terminal device.

Optionally, the receiving unit 510 is specifically configured to: receive, by using a fourth RLC entity of the MCG of the first SRB, the RLF message sent by the terminal device, where the fourth RLC entity uses only the secondary cell to transmit data. .

Optionally, the receiving unit 510 is specifically configured to: receive, by using a fifth RLC entity of the MCG of the first SRB, the RLF message sent by the terminal device, where the fifth RLC entity is capable of transmitting data by using a primary cell. .

Optionally, the receiving unit 510 is configured to: receive, by using a fourth RLC entity and a fifth RLC entity of the MCG of the first SRB, the RLF message sent by the terminal device, where the fourth RLC entity is only Using the secondary cell to transmit data, the fifth RLC entity can transmit data using the primary cell.

Optionally, the receiving unit 510 is specifically configured to: receive, by using the second SRB, the RLF message sent by the terminal device, where the second SRB ends in the SCG.

Optionally, the receiving unit 510 is specifically configured to: receive, by using a sixth RLC entity of the SCG of the second SRB, an RLF message sent by the terminal device, where the sixth RLC entity uses only the secondary cell to transmit data.

Optionally, the receiving unit 510 is specifically configured to: receive, by using a seventh RLC entity of the SCG of the second SRB, an RLF message sent by the terminal device, where the seventh RLC entity can use the primary cell to transmit data.

Optionally, the receiving unit 510 is specifically configured to: receive, by using a sixth RLC entity and a seventh RLC entity of the SCG of the second SRB, an RLF message sent by the terminal device, where the sixth RLC entity uses only the auxiliary The cell transmits data, and the seventh RLC entity can transmit data using the primary cell.

It should be understood that the network device 500 may correspond to the network device in the method 300, and the operations implemented by the network device in the method 500 may be implemented. For brevity, no further details are provided herein.

FIG. 6 is a schematic structural diagram of a system chip 600 according to an embodiment of the present application. The system chip 600 of FIG. 6 includes an input interface 601, an output interface 602, the processor 603, and a memory 604 that can be connected by an internal communication connection line. The processor 603 is configured to execute code in the memory 604.

Optionally, when the code is executed, the processor 603 implements the corresponding operations performed by the terminal device or network device in the method 300. For the sake of brevity, it will not be repeated here.

FIG. 7 is a schematic block diagram of a communication device 700 in accordance with an embodiment of the present application. As shown in FIG. 7, the communication device 700 includes a processor 710 and a memory 720. The memory 720 can store program code, and the processor 710 can execute the program code stored in the memory 720.

Alternatively, as shown in FIG. 7, the communication device 700 can include a transceiver 730 that can control the transceiver 730 to communicate externally.

Optionally, the processor 710 can call the program code stored in the memory 720 to perform the corresponding operations performed by the terminal device or the network device in the method 300. For brevity, details are not described herein again.

It should be understood that the processor of the embodiment of the present application may be an integrated circuit chip with signal processing capability. In the implementation process, each step of the foregoing method embodiment may be completed by an integrated logic circuit of hardware in a processor or an instruction in a form of software. The processor may be a general-purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a Field Programmable Gate Array (FPGA), or the like. Programming logic devices, discrete gates or transistor logic devices, discrete hardware components. The methods, steps, and logical block diagrams disclosed in the embodiments of the present application can be implemented or executed. The general purpose processor may be a microprocessor or the processor or any conventional processor or the like. The steps of the method disclosed in the embodiments of the present application may be directly implemented by the hardware decoding processor, or may be performed by a combination of hardware and software modules in the decoding processor. The software module can be located in a conventional storage medium such as random access memory, flash memory, read only memory, programmable read only memory or electrically erasable programmable memory, registers, and the like. The storage medium is located in the memory, and the processor reads the information in the memory and combines the hardware to complete the steps of the above method.

It is to be understood that the memory in the embodiments of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memory. The non-volatile memory may be a read-only memory (ROM), a programmable read only memory (PROM), an erasable programmable read only memory (Erasable PROM, EPROM), or an electric Erase programmable read only memory (EEPROM) or flash memory. The volatile memory can be a Random Access Memory (RAM) that acts as an external cache. By way of example and not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (Synchronous DRAM). SDRAM), Double Data Rate SDRAM (DDR SDRAM), Enhanced Synchronous Dynamic Random Access Memory (ESDRAM), Synchronous Connection Dynamic Random Access Memory (Synchlink DRAM, SLDRAM) ) and direct memory bus random access memory (DR RAM). It should be noted that the memories of the systems and methods described herein are intended to comprise, without being limited to, these and any other suitable types of memory.

Those of ordinary skill in the art will appreciate that the elements and algorithm steps of the various examples described in connection with the embodiments disclosed herein can be implemented in electronic hardware or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the solution. A person skilled in the art can use different methods to implement the described functions for each particular application, but such implementation should not be considered to be beyond the scope of the present application.

A person skilled in the art can clearly understand that for the convenience and brevity of the description, the specific working process of the system, the device and the unit described above can refer to the corresponding process in the foregoing method embodiment, and details are not described herein again.

In the several embodiments provided by the present application, it should be understood that the disclosed systems, devices, and methods may be implemented in other manners. For example, the device embodiments described above are merely illustrative. For example, the division of the unit is only a logical function division. In actual implementation, there may be another division manner, for example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored or not executed. In addition, the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be in an electrical, mechanical or other form.

The units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the objectives of the solution of the embodiment.

In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

The functions may be stored in a computer readable storage medium if implemented in the form of a software functional unit and sold or used as a standalone product. Based on such understanding, the technical solution of the present application, which is essential or contributes to the prior art, or a part of the technical solution, may be embodied in the form of a software product, which is stored in a storage medium, including The instructions are used to cause a computer device (which may be a personal computer, server, or network device, etc.) to perform all or part of the steps of the methods described in various embodiments of the present application.

The foregoing is only a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto, and any person skilled in the art can easily think of changes or substitutions within the technical scope disclosed in the present application. It should be covered by the scope of protection of this application. Therefore, the scope of protection of the present application should be determined by the scope of the claims.

Claims

A method for controlling a data replication transmission function of a terminal device, comprising:

When the data transmitted on the first bearer reaches the maximum number of retransmissions on the first radio link control RLC entity, the terminal device suspends data transmission on the first bearer, where the first bearer is a carrier aggregation CA A radio bearer that transmits data by means of data replication in a scenario;

The terminal device reports a radio link failure RLF message.
The method according to claim 1, wherein the first RLC entity is an RLC entity of a primary network node MCG or an RLC entity of a secondary network node SCG.
The method according to claim 1 or 2, wherein the first RLC entity of the first bearer transmits data only in the secondary cell.
The method according to any one of claims 1 to 3, wherein the first bearer is a signaling radio bearer SRB or a data radio bearer DRB.
The method according to any one of claims 1 to 4, wherein the terminal device suspends data transmission on the first bearer, including:

The terminal device suspends data transmission of the first bearer on the PDCP layer and the RLC layer.
The method according to any one of claims 1 to 4, wherein the terminal device suspends data transmission on the first bearer, including:

The terminal device suspends data transmission of the first bearer on the RLC layer.
The method according to claim 6, wherein the terminal device suspends data transmission of the first bearer on the RLC layer, including:

The terminal device suspends data transmission on the first RLC entity of the RLC layer.
The method according to any one of claims 1 to 7, wherein the terminal device suspends data transmission on the first bearer, including:

The terminal device suspends data transmission on the first bearer, and suspends data transmission on the second bearer, wherein the second RLC entity of the second bearer performs a data carrier used for data transmission, and the first The set of carriers used by the first RLC entity of the bearer for data transmission at least partially overlaps.
The method according to claim 8, wherein the second RLC entity performs a carrier set used for data transmission, and a carrier set used for data transmission with the first RLC entity of the first bearer. At least partially overlap, including:

The set of carriers used by the second RLC entity for data transmission is the same as the set of carriers used for data transmission by the first RLC entity of the first bearer; or

The set of carriers used by the second RLC entity to perform data transmission includes a carrier set used by the first RLC entity of the first bearer for data transmission; or

The carrier set used by the second RLC entity for data transmission has an intersection with a carrier set used for data transmission by the first RLC entity of the first bearer.
The method according to claim 8 or 9, wherein the second bearer is a radio bearer that transmits data by means of data replication in a CA scenario.
The method according to any one of claims 8 to 10, wherein the terminal device simultaneously suspends data transmission on the second bearer, including:

The terminal device suspends data transmission of the second bearer on the PDCP layer and the RLC layer.
The method according to any one of claims 8 to 10, wherein the terminal device simultaneously suspends data transmission on the second bearer, including:

The terminal device suspends data transmission of the second bearer on the RLC layer.
The method according to claim 12, wherein the terminal device suspends data transmission of the second bearer on the RLC layer, including:

The terminal device suspends data transmission on the second RLC entity of the RLC layer.
The method according to any one of claims 1 to 7, wherein the terminal device suspends data transmission on the first bearer, including:

The terminal device suspends data transmission on the first bearer, and suspends data transmission on the third bearer, wherein the third RLC entity of the third bearer performs data transmission only in the secondary cell.
The method according to claim 14, wherein the third bearer is a radio bearer that transmits data by means of data replication in a CA scenario.
The method according to claim 14 or 15, wherein the terminal device simultaneously suspends data transmission on the third bearer, including:

The terminal device suspends data transmission of the third bearer on the PDCP layer and the RLC layer.
The method according to claim 14 or 15, wherein the terminal device simultaneously suspends data transmission on the third bearer, including:

The terminal device suspends data transmission of the third bearer on the RLC layer.
The method according to claim 17, wherein the terminal device suspends data transmission of the third bearer on the RLC layer, including:

The terminal device suspends data transmission on the third RLC entity of the RLC layer.
The method according to any one of claims 1 to 18, wherein the reporting, by the terminal device, the RLF message comprises:

The terminal device sends the RLF message by using a first SRB, where the first SRB ends in the MCG.
The method according to claim 19, wherein the sending, by the terminal device, the RLF message by using the first SRB comprises:

The terminal device sends the RLF message by using an RLC entity of the MCG of the first SRB.
The method according to claim 19, wherein the sending, by the terminal device, the RLF message by using the first SRB comprises:

The terminal device sends the RLF message by using an RLC entity of the SCG of the first SRB.
The method according to claim 19, wherein the sending, by the terminal device, the RLF message by using the first SRB comprises:

The terminal device sends the RLF message by using an RLC entity of the MCG of the first SRB and an RLC entity of the SCG.
The method according to claim 20 or 22, wherein the terminal device sends the RLF message by using an RLC entity of the MCG of the first SRB, including:

The terminal device sends the RLF message by using a fourth RLC entity of the MCG of the first SRB, where the fourth RLC entity uses only the secondary cell to transmit data.
The method according to claim 20 or 22, wherein the terminal device sends the RLF message by using an RLC entity of the MCG of the first SRB, including:

The terminal device sends the RLF message by using a fifth RLC entity of the MCG of the first SRB, and the fifth RLC entity is capable of transmitting data by using a primary cell.
The method according to claim 20 or 22, wherein the terminal device sends the RLF message by using an RLC entity of the MCG of the first SRB, including:

Transmitting, by the terminal device, the RLF message by using a fourth RLC entity and a fifth RLC entity of the MCG of the first SRB, where the fourth RLC entity uses only the secondary cell to transmit data, and the fifth RLC entity can use the primary The cell transmits data.
The method according to any one of claims 1 to 18, wherein the reporting, by the terminal device, the RLF message comprises:

The terminal device sends the RLF message by using a second SRB, where the second SRB ends in the SCG.
The method according to claim 26, wherein the sending, by the terminal device, the RLF message by using the second SRB comprises:

The terminal device sends the RLF message by using a sixth RLC entity of the SCG of the second SRB, where the sixth RLC entity uses only the secondary cell to transmit data.
The method according to claim 26, wherein the sending, by the terminal device, the RLF message by using the second SRB comprises:

The terminal device sends the RLF message by using a seventh RLC entity of the SCG of the second SRB, and the seventh RLC entity is capable of transmitting data by using a primary cell.
The method according to claim 26, wherein the sending, by the terminal device, the RLF message by using the second SRB comprises:

Transmitting, by the terminal device, the RLF message by using a sixth RLC entity and a seventh RLC entity of the SCG of the second SRB, where the sixth RLC entity uses only the secondary cell to transmit data, and the seventh RLC entity can use the primary The cell transmits data.
A method for controlling a data replication transmission function of a terminal device, comprising:

The network device receives the radio link failure RLF message reported by the terminal device, where the RLF message is used to indicate that the data transmitted on the first bearer of the terminal device reaches the maximum number of retransmissions on the first radio link control RLC entity, where The first bearer is a radio bearer that transmits data by means of data replication in a carrier aggregation CA scenario.
The method according to claim 30, wherein the first RLC entity is an RLC entity of a primary network node MCG or an RLC entity of a secondary network node SCG.
The method according to claim 30 or 31, wherein the first RLC entity of the first bearer transmits data only in the secondary cell.
The method according to any one of claims 30 to 32, wherein the first bearer is a signaling radio bearer SRB or a data radio bearer DRB.
The method according to any one of claims 30 to 33, wherein the receiving, by the network device, the RLF message reported by the terminal device comprises:

The network device receives the RLF message sent by the terminal device by using a first SRB, where the first SRB ends in an MCG.
The method according to claim 34, wherein the receiving, by the network device, the RLF message sent by the terminal device by using the first SRB comprises:

The network device receives the RLF message sent by the terminal device by using an RLC entity of the MCG of the first SRB.
The method according to claim 34, wherein the receiving, by the network device, the RLF message sent by the terminal device by using the first SRB comprises:

The network device receives the RLF message sent by the terminal device by using an RLC entity of the SCG of the first SRB.
The method according to claim 36, wherein the receiving, by the network device, the RLF message sent by the terminal device by using the first SRB comprises:

The network device receives the RLF message sent by the terminal device by using an RLC entity of the MCG of the first SRB and an RLC entity of the SCG.
The method according to claim 35 or 37, wherein the network device receives the RLF message sent by the terminal device by using an RLC entity of the MCG of the first SRB, including:

Receiving, by the network device, the RLF message sent by the terminal device by using a fourth RLC entity of the MCG of the first SRB, where the fourth RLC entity transmits data only in the secondary cell.
The method according to claim 35 or 37, wherein the network device receives the RLF message sent by the terminal device by using an RLC entity of the MCG of the first SRB, including:

The network device receives the RLF message sent by the terminal device by using a fifth RLC entity of the MCG of the first SRB, and the fifth RLC entity is capable of transmitting data in the primary cell.
The method according to claim 35 or 37, wherein the network device receives the RLF message sent by the terminal device by using an RLC entity of the MCG of the first SRB, including:

Receiving, by the network device, the RLF message sent by the terminal device by using a fourth RLC entity and a fifth RLC entity of the MCG of the first SRB, where the fourth RLC entity transmits data only in the secondary cell, where the The five RLC entities are capable of transmitting data in the primary cell.
The method according to any one of claims 30 to 33, wherein the receiving, by the network device, the RLF message reported by the terminal device comprises:

The network device receives the RLF message sent by the terminal device by using a second SRB, where the second SRB ends in the SCG.
The method according to claim 41, wherein the receiving, by the network device, the RLF message sent by the terminal device by using the second SRB, includes:

Receiving, by the network device, the RLF message sent by the terminal device by using a sixth RLC entity of the SCG of the second SRB, where the sixth RLC entity uses only the secondary cell to transmit data.
The method according to claim 41, wherein the receiving, by the network device, the RLF message sent by the terminal device by using the second SRB, includes:

The network device receives the RLF message sent by the terminal device by using a seventh RLC entity of the SCG of the second SRB, and the seventh RLC entity is capable of transmitting data by using the primary cell.
The method according to claim 41, wherein the receiving, by the network device, the RLF message sent by the terminal device by using the second SRB, includes:

Receiving, by the network device, the RLF message sent by the terminal device by using a sixth RLC entity and a seventh RLC entity of the SCG of the second SRB, where the sixth RLC entity uses only the secondary cell to transmit data, where the The seven RLC entities are capable of transmitting data using the primary cell.
A terminal device, comprising:

a processing unit, when the data transmitted on the first bearer reaches a maximum number of retransmissions on the first radio link control RLC entity, suspending data transmission on the first bearer, where the first bearer is a carrier A radio bearer that transmits data by means of data replication in an aggregation CA scenario;

The sending unit is configured to report a radio link failure RLF message.
The terminal device according to claim 45, wherein the first RLC entity is an RLC entity of a primary network node MCG or an RLC entity of a secondary network node SCG.
The terminal device according to claim 45 or 46, wherein the first RLC entity of the first bearer transmits data only in the secondary cell.
The terminal device according to any one of claims 45 to 47, wherein the first bearer is a signaling radio bearer SRB or a data radio bearer DRB.
The terminal device according to any one of claims 45 to 48, wherein the processing unit is specifically configured to:

The data transmission of the first bearer on the PDCP layer and the RLC layer is suspended.
The terminal device according to any one of claims 45 to 49, wherein the processing unit is specifically configured to:

The data transmission of the first bearer on the RLC layer is suspended.
The terminal device according to claim 50, wherein the processing unit is specifically configured to:

Suspending data transmission on the first RLC entity of the RLC layer.
The terminal device according to any one of claims 45 to 51, wherein the processing unit is specifically configured to:

Suspending data transmission on the first bearer, and suspending data transmission on the second bearer, wherein the second RLC entity of the second bearer performs a data carrier used for data transmission, and the first bearer The set of carriers used by the first RLC entity for data transmission at least partially overlaps.
The terminal device according to claim 52, wherein the second RLC entity of the second bearer performs a data transmission used by the second RLC entity, and performs data transmission with the first RLC entity of the first bearer. The set of carriers used at least partially overlap, including:

The set of carriers used by the second RLC entity for data transmission is the same as the set of carriers used for data transmission by the first RLC entity of the first bearer; or

The set of carriers used by the second RLC entity to perform data transmission includes a carrier set used by the first RLC entity of the first bearer for data transmission; or

The carrier set used by the second RLC entity for data transmission has an intersection with a carrier set used for data transmission by the first RLC entity of the first bearer.
The terminal device according to claim 52 or 53, wherein the second bearer is a radio bearer that transmits data by means of data replication in a CA scenario.
The terminal device according to any one of claims 52 to 54, wherein the processing unit is specifically configured to:

The data transmission of the second bearer on the PDCP layer and the RLC layer is suspended.
The terminal device according to any one of claims 52 to 54, wherein the processing unit is specifically configured to:

The data transmission of the second bearer on the RLC layer is suspended.
The terminal device according to claim 56, wherein the processing unit is specifically configured to:

Suspending data transmission on the second RLC entity of the RLC layer.
The terminal device according to any one of claims 45 to 51, wherein the processing unit is specifically configured to:

Suspending data transmission on the first bearer while suspending data transmission on the third bearer, wherein the third RLC entity of the third bearer performs data transmission in the secondary cell.
The terminal device according to claim 58, wherein the third bearer is a radio bearer that transmits data by means of data replication in a CA scenario.
The terminal device according to claim 58 or 59, wherein the processing unit is specifically configured to:

The data transmission of the third bearer on the PDCP layer and the RLC layer is suspended.
The terminal device according to claim 58 or 59, wherein the processing unit is specifically configured to:

The data transmission of the third bearer on the RLC layer is suspended.
The terminal device according to claim 61, wherein the processing unit is specifically configured to:

Suspending data transmission on the third RLC entity of the RLC layer.
The terminal device according to any one of claims 45 to 62, wherein the transmitting unit is specifically configured to:

The RLF message is sent by using the first SRB, and the first SRB is terminated by the MCG.
The terminal device according to claim 63, wherein the sending unit is specifically configured to:

Sending the RLF message by using an RLC entity of the MCG of the first SRB.
The terminal device according to claim 63, wherein the sending unit is specifically configured to:

And sending the RLF message by using an RLC entity of the SCG of the first SRB.
The terminal device according to claim 63, wherein the sending unit is specifically configured to:

The RLF message is sent by an RLC entity of the MCG of the first SRB and an RLC entity of the SCG.
The terminal device according to claim 64 or claim 66, wherein the sending unit is specifically configured to:

Transmitting, by the fourth RLC entity of the MCG of the first SRB, the RLF message, where the fourth RLC entity uses only the secondary cell to transmit data.
The terminal device according to claim 64 or claim 66, wherein the sending unit is specifically configured to:

The RLF message is sent by a fifth RLC entity of the MCG of the first SRB, and the fifth RLC entity is capable of transmitting data using the primary cell.
The terminal device according to claim 64 or claim 66, wherein the sending unit is specifically configured to:

And transmitting, by the fourth RLC entity and the fifth RLC entity of the MCG of the first SRB, the fourth RLC entity uses only the secondary cell to transmit data, and the fifth RLC entity is capable of transmitting data by using the primary cell.
The terminal device according to any one of claims 45 to 62, wherein the transmitting unit is specifically configured to:

The RLF message is sent by the second SRB, and the second SRB is cut off by the SCG.
The terminal device according to claim 70, wherein the sending unit is specifically configured to:

The RLF message is sent by a sixth RLC entity of the SCG of the second SRB, and the sixth RLC entity uses only the secondary cell to transmit data.
The terminal device according to claim 70, wherein the sending unit is specifically configured to:

The RLF message is sent by a seventh RLC entity of the SCG of the second SRB, and the seventh RLC entity is capable of transmitting data using the primary cell.
The terminal device according to claim 70, wherein the sending unit is specifically configured to:

And transmitting, by the sixth RLC entity and the seventh RLC entity of the SCG of the second SRB, the sixth RLC entity uses only the secondary cell to transmit data, and the seventh RLC entity is capable of transmitting data by using the primary cell.
A network device, comprising:

a receiving unit, configured to receive a radio link failure RLF message reported by the terminal device, where the RLF message is used to indicate that the data transmitted on the first bearer of the terminal device reaches a maximum retransmission on the first radio link control RLC entity The number of times, wherein the first bearer is a radio bearer that transmits data by means of data replication in a carrier aggregation CA scenario.
The network device according to claim 74, wherein the first RLC entity is an RLC entity of a primary network node MCG or an RLC entity of a secondary network node SCG.
A network device according to claim 74 or 75, wherein said first hosted first RLC entity transmits data only in the secondary cell.
The network device according to any one of claims 74 to 76, wherein the first bearer is a signaling radio bearer SRB or a data radio bearer DRB.
The network device according to any one of claims 74 to 77, wherein the receiving unit is specifically configured to:

Receiving, by the first SRB, the RLF message sent by the terminal device, where the first SRB ends in the MCG.
The network device according to claim 78, wherein the receiving unit is specifically configured to:

The network device receives the RLF message sent by the terminal device by using an RLC entity of the MCG of the first SRB.
The network device according to claim 78, wherein the receiving unit is specifically configured to:

Receiving, by the RLC entity of the SCG of the first SRB, the RLF message sent by the terminal device.
The network device according to claim 78, wherein the receiving unit is specifically configured to:

Receiving, by the RLC entity of the MCG of the first SRB and the RLC entity of the SCG, the RLF message sent by the terminal device.
The network device according to claim 79 or 81, wherein the receiving unit is specifically configured to:

Receiving, by the fourth RLC entity of the MCG of the first SRB, the RLF message sent by the terminal device, where the fourth RLC entity transmits data only in the primary cell.
The network device according to claim 79 or 81, wherein the receiving unit is specifically configured to:

Receiving, by the fifth RLC entity of the MCG of the first SRB, the RLF message sent by the terminal device, where the fifth RLC entity is capable of transmitting data in the primary cell.
The network device according to claim 79 or 81, wherein the receiving unit is specifically configured to:

Receiving, by the fourth RLC entity and the fifth RLC entity of the MCG of the first SRB, the RLF message sent by the terminal device, where the fourth RLC entity transmits data only in the secondary cell, and the fifth RLC entity can Data is transmitted in the primary cell.
The network device according to any one of claims 74 to 77, wherein the receiving unit is specifically configured to:

Receiving, by the second SRB, the RLF message sent by the terminal device, where the second SRB ends in the SCG.
The network device according to claim 85, wherein the receiving unit is specifically configured to:

Receiving, by the sixth RLC entity of the SCG of the second SRB, the RLF message sent by the terminal device, where the sixth RLC entity uses only the secondary cell to transmit data.
The network device according to claim 85, wherein the receiving unit is specifically configured to:

Receiving, by the seventh RLC entity of the SCG of the second SRB, the RLF message sent by the terminal device, where the seventh RLC entity can use the primary cell to transmit data.
The network device according to claim 85, wherein the receiving unit is specifically configured to:

Receiving, by the sixth RLC entity and the seventh RLC entity of the SCG of the second SRB, the RLF message sent by the terminal device, where the sixth RLC entity uses only the secondary cell to transmit data, and the seventh RLC entity can The primary cell is used to transmit data.