WO2019153208A1 - Method for handling radio link failure (rlf) and terminal device - Google Patents

Abstract

Disclosed in an embodiment of the present invention are a method for handling a radio link failure (RLF) and a terminal device. The method comprises: if retransmission of data of a first radio bearer on a first radio link control (RLC) entity corresponding to the first radio bearer reaches a maximum retransmission count, a terminal device deactivating a data replication and transmission function of the first radio bearer, and/or the terminal device deactivating a data replication and transmission function of a second radio bearer, a carrier mapped by an RLC entity corresponding to the second radio bearer at least partially overlapping with a carrier mapped by the first RLC entity. The method and terminal device disclosed in the embodiment of the present invention facilitate improving reliability of data transmission.

Description

Method and terminal device for processing radio link failure RLF Technical field

The embodiments of the present application relate to the field of communications, and, more particularly, to a method and a terminal device for processing a radio link failure RLF.

Background technique

In a carrier aggregation scenario, a Packet Data Convergence Protocol (PDCP) entity corresponding to a radio bearer can support a duplicate data transmission function, that is, a PDCP Protocol Data Unit (PDU) is copied into two. This improves the reliability of data transmission. In the case where the copy data transmission function of a certain radio bearer is in an active state, a radio link failure (RLF) occurs, and how the terminal device should respond to the RLF is not involved in the current discussion.

Summary of the invention

In view of this, the embodiment of the present application provides a method and a terminal device for processing a radio link failure RLF, which is beneficial to improving reliability of data transmission.

In a first aspect, a method for processing a radio link failure RLF is provided, the method comprising: maximizing retransmission of data of a first radio bearer on a first radio link control RLC entity corresponding to the first radio bearer The number of times, the terminal device deactivates the duplicate data transmission function of the first radio bearer, and/or the terminal device deactivates the duplicate data transmission function of the second radio bearer, where the second radio bearer corresponds to the RLC entity mapping The carrier at least partially overlaps with the carrier mapped by the first RLC entity.

In a possible implementation, the terminal device deactivates the replication data transmission function of the first radio bearer, including: the terminal device stops the PDCP entity of the packet data convergence protocol PDCP entity of the first radio bearer from being copied; The terminal device stops submitting data to the first RLC entity and submits data to the second RLC entity corresponding to the first radio bearer.

In a possible implementation, the method further includes: the terminal device sending, to the network device, indication information, where the indication information is used to indicate that the first radio bearer has a radio link failure RLF, and/or the terminal device goes Activates the identity of the radio bearer that replicates the data transfer function.

In a possible implementation manner, the first radio bearer and the second radio bearer correspond to the same cell group or correspond to different cell groups.

In a possible implementation manner, the cell group includes a primary cell group MCG and/or a secondary cell group SCG.

In a possible implementation, the working mode of the first RLC entity is the acknowledge mode AM, and the working mode of the RLC entity corresponding to the second radio bearer is the acknowledge mode AM or the non-acknowledge mode UM.

In a possible implementation, the first RLC entity is a primary link of the first radio bearer, and the second RLC entity corresponding to the first radio bearer is a secondary link of the first radio bearer; or The first RLC entity is a secondary link of the first radio bearer, and the second RLC entity is a primary link of the first radio bearer.

In a second 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 means for performing the method of any of the above-described first aspect or any of the possible implementations of the first aspect.

In a third aspect, a terminal device is provided, the terminal device comprising: a memory, a processor, an input interface, and an output interface. The memory, the processor, the input interface, and the output interface are connected by a bus system. The memory is for storing instructions for executing the memory stored instructions for performing the method of any of the first aspect or the first aspect of the first aspect.

In a fourth aspect, a computer storage medium is provided for storing computer software instructions for performing the method of any of the above first aspect or any of the possible implementations of the first aspect, comprising program.

In a fifth aspect, a computer program product comprising instructions, when executed on a computer, causes the computer to perform the method of any of the first aspect or the optional implementation of the first aspect.

These and other aspects of the present application will be more readily apparent from the following description of the embodiments.

DRAWINGS

FIG. 1 is a schematic diagram of an application scenario of an embodiment of the present application.

Figure 2 shows a protocol architecture diagram in a carrier aggregation scenario.

FIG. 3 is a schematic block diagram of a method for processing a radio link failure RLF according to an embodiment of the present application.

FIG. 4 shows a schematic block diagram of a terminal device of an embodiment of the present application.

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

Detailed ways

The technical solutions in the embodiments of the present application will be clearly and completely described in the following with reference to the accompanying drawings in the embodiments.

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, General Packet Radio Service (GPRS), Long Term Evolution (LTE) system, LTE Frequency Division Duplex (FDD) system, LTE time division duplex (Time Division Duplex, TDD), Universal Mobile Telecommunication System (UMTS), Worldwide Interoperability for Microwave Access (WiMAX) communication system, New Radio (NR) or future 5G System, etc.

In particular, the technical solutions of the embodiments of the present application can be applied to various communication systems based on non-orthogonal multiple access technologies, such as a sparse code multiple access (SCMA) system, and a low-density signature (Low). Density Signature (LDS) system, etc., of course, the SCMA system and the LDS system may also be referred to as other names in the communication field; further, the technical solution of the embodiment of the present application can be applied to multi-carrier using non-orthogonal multiple access technology. Transmission system, for example, Orthogonal Frequency Division Multiplexing (OFDM), Filter Bank Multi-Carrier (FBMC), General Frequency Division Multiplexing (Generalized Frequency Division Multiplexing (OFDM)) Frequency Division Multiplexing (GFDM), Filtered Orthogonal Frequency Division Multiplexing (Filtered-OFDM, F-OFDM) system, and the like.

The terminal device in the embodiment of the present application may 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, and a wireless device. Communication device, 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 in the future evolution of the Public Land Mobile Network (PLMN) The terminal device and the like are not limited in the embodiment of the present application.

The network device in the embodiment of the present application may be a device for communicating with a terminal device, where the network device may be a Base Transceiver Station (BTS) in GSM or CDMA, or may be a base station (NodeB, NB) in a WCDMA system. And may be an evolved base station (eNB or eNodeB) in the LTE system, or may be a wireless controller in a cloud radio access network (CRAN) scenario, or the network device may be The embodiments of the present application are not limited to the relay station, the access point, the in-vehicle device, the wearable device, and the network device in the future 5G network or the network device in the future evolved PLMN network.

FIG. 1 is a schematic diagram of an application scenario of an embodiment of the present application. The communication system in FIG. 1 may include a terminal device 10 and a network device 20. The network device 20 is configured to provide communication services for the terminal device 10 and access the core network. The terminal device 10 accesses the network by searching for synchronization signals, broadcast signals, and the like transmitted by the network device 20, thereby performing communication with the network. The arrows shown in FIG. 1 may represent uplink/downlink transmissions by a cellular link between the terminal device 10 and the network device 20.

In the carrier aggregation scenario, the PDCP entity can support the data replication function, that is, the PDCP replication data function is used, so that the copied data is separately transmitted to two Radio Link Control (RLC) entities (corresponding to two different Logical channel), and finally ensure that the copied PDCP PDU can be transmitted on different physical layer aggregate carriers to achieve frequency diversity gain to improve data transmission reliability.

The specific protocol structure will be described below in conjunction with FIG. As shown in FIG. 2, the PDCP entity corresponding to a radio bearer has a split bearer replication function, and the data process of the PDCP Service Data Unit (SDU) is copied and encapsulated into PDCP PDU1 and PDCP PDU2, PDCP PDU1 and PDCP PDU2. Have the same content, that is, the data payload and the header header are the same. PDCP PDU1 and PDCP PDU2 are respectively mapped to different Radio Link Control (RLC) entities, that is, PDCP PDU1 is transmitted to RLC entity 1, and PDCP PDU2 is transmitted to RLC entity 2, and different RLC entities correspond to different logics. Channels, for Media Access Control (MAC), after learning which logical channels transmit the duplicated data of the same PDCP PDU, the replicated data is transmitted on different carriers, for example, the RLC entity 1 The transmitted duplicate data is transmitted on the physical carrier 1, and the replicated data transmitted in the RLC entity 2 is transmitted on the physical carrier 2.

In the case where the copy data transmission function of a certain radio bearer is in an active state, a radio link failure RLF occurs, and how the terminal device should respond to the RLF has not been involved in the current discussion.

FIG. 3 is a schematic block diagram of a method 100 of processing a radio link failure RLF in an embodiment of the present application. As shown in FIG. 3, the method 100 includes:

S110. If the data of the first radio bearer reaches the maximum number of retransmissions on the first radio link control RLC entity corresponding to the first radio bearer, the terminal device deactivates the replica data transmission function of the first radio bearer. And/or, the terminal device deactivates the duplicate data transmission function of the second radio bearer, where the carrier mapped by the RLC entity corresponding to the second radio bearer at least partially overlaps with the carrier mapped by the first RLC entity.

It should be noted that different radio bearers correspond to different PDCP entities, and a PDCP entity having a duplicate data transmission function may be configured to correspond to two RLC entities, and a replica data transmission function of the PDCP entity may also be a replica data transmission function of the radio bearer.

When the copy data transmission function of the first radio bearer is in an active state, the terminal device determines that the first radio bearer has an RLF. That is to say, the terminal device may be replicating the PDCP PDU by using the PDCP entity of the first radio bearer, and performing data transmission by two RLC entities corresponding to the first radio bearer. When the terminal device determines that the RLF occurs on the first radio bearer, the terminal device may deactivate the duplicate data transmission function of the first radio bearer. Causing the terminal device to stop using the PDCP entity of the first radio bearer to copy the PDCP PDU, including the uplink replica PDCP PDU and/or the downlink replica PDCP PDU, and when there is new data to be transmitted, the terminal device stops using the corresponding corresponding to the first radio bearer. The RLC entity that generates the RLF performs data transmission, and uses the RLC entity corresponding to the first radio bearer to perform data transmission. When the RLF of the first radio bearer of the terminal device occurs, the terminal device may also deactivate the duplicate data transmission function of the second radio bearer. The carrier mapped by the RLC entity corresponding to the first radio bearer and the carrier mapped by the RLC entity corresponding to the second radio bearer at least partially overlap. For example, the carrier mapped by the RLC entity corresponding to the first radio bearer and the carrier mapped by the RLC entity corresponding to the second radio bearer may be a subset of each other. That is to say, when the RLF occurs on the first radio bearer, the data transmission of the second radio bearer may be affected, so further deactivating the duplicate data transmission function of the second radio bearer is beneficial to improving data transmission by using the second radio bearer. Reliability.

Optionally, the RLF is generated by the first radio bearer, and the data transmitted by the first RLC entity corresponding to the first radio bearer may reach the maximum number of retransmissions, or may be the second RLC entity corresponding to the first radio bearer. The data transmitted on it reaches the maximum number of retransmissions. If the data transmitted on the first RLC entity reaches the maximum number of retransmissions, the terminal device may stop using the first RLC entity to transmit data, and directly use the second RLC entity to transmit data. If the data transmitted on the second RLC entity reaches the maximum number of retransmissions, the terminal device may stop using the second RLC entity to transmit data, and directly use the second RLC entity to transmit data. If the data transmitted on the first RLC entity reaches the maximum number of retransmissions, the terminal device deactivates the duplicate data transmission function of the second radio bearer, and the carrier mapped by the RLC entity corresponding to the second radio bearer is mapped to the first RLC entity. The carriers are at least partially overlapping.

Optionally, the first radio bearer generates an RLF, and the data transmitted on a certain RLC entity corresponding to the third radio bearer reaches a maximum number of retransmissions, and the RLC entity corresponding to the second radio bearer The mapped carrier may partially overlap with the carrier mapped by the RLC entity corresponding to the first radio bearer.

Optionally, the maximum number of retransmissions of data transmitted on an RLC entity means that the working mode of the RLC entity may be an acknowledged mode (AM). In other words, in the RLC AM mode, the retransmission counter corresponding to a certain RLC SDU reaches the configured threshold.

Optionally, the foregoing third radio bearer may or may not have a duplicate data transmission function.

Optionally, the carrier mapped by the first RLC entity and the carrier mapped by the RLC entity corresponding to the second radio bearer at least partially overlap, for example, may correspond to at least one same secondary cell. The first radio bearer and the second radio bearer may also be the same or different cell groups, for example, a primary cell group (MCG) and/or a secondary cell group (SCG).

Optionally, the working mode of the RLC entity corresponding to the third radio bearer may be an AM mode or an Unacknowledged Mode (UM).

Optionally, if the link corresponding to the first RLC entity is the primary link, and the link corresponding to the second RLC entity is the secondary link, that is, after the replication data transmission function of the first radio bearer is deactivated, the network By default, the device configuration uses the first RLC entity for data transmission, and the default unused RLC entity configured by the network device is the second RLC entity.

If the RLF is generated on the primary link, the data is forwarded to the RLC entity corresponding to the primary link, and the data is forwarded to the RLC entity corresponding to the secondary link. The secondary link automatically becomes the primary link; When the RLF occurs, the data is delivered to the RLC entity corresponding to the secondary link, and the data is delivered to the RLC entity corresponding to the primary link.

Optionally, the method further includes: the terminal device sends indication information to the network device, where the indication information is used to indicate that the first radio bearer has a radio link failure RLF, and/or the terminal device deactivates the replica data transmission function. The identity of the radio bearer.

In other words, the terminal device may report the RLF to the network device, or report the data transmission function of the radio bearer to the network device, for example, the network device may report the network data to the network device. The identity of these radio bearers. The terminal device may also report to the network that an RLF has occurred on a certain radio bearer, and may also report to the network those radio bearers that have been deactivated by the duplicate data transmission function.

It should be understood that the interaction between the network device and the terminal device described by the network device and related features, functions, and the like correspond to related features and functions of the terminal device. The related content has been described in detail in the above method 100. For brevity, no further details are provided herein.

It should also be understood that, in various embodiments of the present application, the size of the sequence numbers of the above processes does not mean the order of execution, and the order of execution of each process should be determined by its function and internal logic, and should not be implemented in the present application. The implementation of the examples constitutes any limitation.

It should also be understood that the term "and/or" herein is merely an association describing the associated object, indicating that there may be three relationships, for example, A and/or B, which may indicate that A exists separately, while A and B, there are three cases of B alone. In addition, the character "/" in this article generally indicates that the contextual object is an "or" relationship.

A method for processing a radio link failure RLF according to an embodiment of the present application is described in detail above. An apparatus for processing a radio link failure RLF according to an embodiment of the present application will be described below with reference to FIG. 4 and FIG. The technical features are applicable to the following device embodiments.

FIG. 4 shows a schematic block diagram of a terminal device 200 of an embodiment of the present application. As shown in FIG. 4, the terminal device 200 includes:

The processing unit 210 is configured to deactivate the data of the first radio bearer if the data of the first radio bearer reaches the maximum number of retransmissions on the first radio link control RLC entity corresponding to the first radio bearer. Transmitting, and/or deactivating a duplicate data transmission function of the second radio bearer, the carrier mapped by the RLC entity corresponding to the second radio bearer at least partially overlapping the carrier mapped by the first RLC entity.

Therefore, the terminal device in the embodiment of the present application is advantageous for improving the reliability of data transmission.

Optionally, in the embodiment of the present application, the processing unit is specifically configured to: stop, by the packet data convergence protocol PDCP entity of the first radio bearer, to copy a PDCP protocol data unit PDU; and stop submitting to the first RLC entity. Data and submit data to a second RLC entity corresponding to the first radio bearer.

Optionally, in the embodiment of the present application, the terminal device further includes: a sending unit, configured to send, to the network device, indication information, where the indication information is used to indicate that the first radio bearer has a radio link failure RLF And/or the terminal device deactivates the identity of the radio bearer that replicates the data transmission function.

Optionally, in the embodiment of the present application, the first radio bearer and the second radio bearer correspond to the same cell group or correspond to different cell groups.

Optionally, in the embodiment of the present application, the cell group includes a primary cell group MCG and/or a secondary cell group SCG.

Optionally, in the embodiment of the present application, the working mode of the first RLC entity is an acknowledge mode AM, and the working mode of the RLC entity corresponding to the second radio bearer is an acknowledge mode AM or a non-acknowledgement mode UM.

Optionally, in the embodiment of the present application, the first RLC entity is a primary link of the first radio bearer, and the second RLC entity corresponding to the first radio bearer is the first radio bearer. a secondary link; or the first RLC entity is a secondary link of the first radio bearer, and the second RLC entity is a primary link of the first radio bearer.

It should be understood that the terminal device 200 according to the embodiment of the present application may correspond to the terminal device in the method embodiment of the present application, and the foregoing and other operations and/or functions of the respective units in the terminal device 200 respectively implement the terminal in the method of FIG. The corresponding process of the device is not described here for brevity.

As shown in FIG. 5, the embodiment of the present application further provides a terminal device 300, which may be the terminal device 200 in FIG. 4, which can be used to execute the content of the terminal device corresponding to the method 100 of FIG. The terminal device 300 includes an input interface 310, an output interface 320, a processor 330, and a memory 340. The input interface 310, the output interface 320, the processor 330, and the memory 340 can be connected by a bus system. The memory 340 is for storing programs, instructions or codes. The processor 330 is configured to execute a program, an instruction or a code in the memory 340 to control the input interface 310 to receive a signal, control the output interface 320 to transmit a signal, and complete the operations in the foregoing method embodiments.

Therefore, the terminal device in the embodiment of the present application is advantageous for improving the reliability of data transmission.

It should be understood that, in the embodiment of the present application, the processor 330 may be a central processing unit (CPU), and the processor 330 may also be another general-purpose processor, a digital signal processor (DSP). , Application Specific Integrated Circuit (ASIC), Field Programmable Gate Array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware component, etc. The general purpose processor may be a microprocessor or the processor or any conventional processor or the like.

The memory 340 can include read only memory and random access memory and provides instructions and data to the processor 330. A portion of the memory 340 may also include a non-volatile random access memory. For example, the memory 340 can also store information of the device type.

In the implementation process, each content of the above method may be completed by an integrated logic circuit of hardware in the processor 330 or an instruction in a form of software. The content of the method disclosed in the embodiments of the present application may be directly implemented as a hardware processor, or may be performed by a combination of hardware and software modules in the 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 340, and the processor 330 reads the information in the memory 340 and completes the contents of the above method in combination with its hardware. To avoid repetition, it will not be described in detail here.

In a specific implementation, the processing unit of the terminal device 200 may be implemented by the processor 330 of FIG. 5, and the transmitting unit of the terminal device 200 may be implemented by the output interface 320 of FIG.

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 may be Integrate 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 purpose 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.

This functionality, if implemented as a software functional unit and sold or used as a standalone product, can be stored on a computer readable storage medium. 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 various embodiments of the present application. The foregoing storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, and the like, which can store program codes. .

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 protection of the claims.

Claims (14)

A method for processing a radio link failure RLF, comprising: The terminal device deactivates the duplicate data transmission function of the first radio bearer if the data of the first radio bearer reaches the maximum number of retransmissions on the first radio link control RLC entity corresponding to the first radio bearer. And/or, the terminal device deactivates the duplicate data transmission function of the second radio bearer, where the carrier mapped by the RLC entity corresponding to the second radio bearer at least partially overlaps with the carrier mapped by the first RLC entity. The method according to claim 1, wherein the deactivating the copy data transmission function of the first radio bearer by the terminal device comprises: The terminal device causes the packet data convergence protocol PDCP entity of the first radio bearer to stop copying the PDCP protocol data unit PDU; The terminal device stops submitting data to the first RLC entity and submits data to a second RLC entity corresponding to the first radio bearer. The method according to claim 1 or 2, wherein the method further comprises: The terminal device sends indication information to the network device, where the indication information is used to indicate that the first radio bearer has a radio link failure RLF, and/or the terminal device deactivates the identifier of the radio bearer that replicates the data transmission function. . The method according to any one of claims 1 to 3, wherein the first radio bearer and the second radio bearer correspond to the same cell group or correspond to different cell groups. The method according to claim 4, wherein the group of cells comprises a primary cell group MCG and/or a secondary cell group SCG. The method according to any one of claims 1 to 5, wherein the working mode of the first RLC entity is an acknowledge mode AM, and the working mode of the RLC entity corresponding to the second radio bearer is an acknowledge mode. AM or unacknowledged mode UM. The method according to any one of claims 1 to 6, wherein the first RLC entity is a primary link of the first radio bearer, and a second RLC entity corresponding to the first radio bearer. a secondary link of the first radio bearer; or The first RLC entity is a secondary link of the first radio bearer, and the second RLC entity is a primary link of the first radio bearer. A terminal device, the terminal device includes: a processing unit, configured to deactivate the data transmission of the first radio bearer if the data of the first radio bearer reaches a maximum number of retransmissions on the first radio link control RLC entity corresponding to the first radio bearer The function, and/or deactivation of the duplicate data transmission function of the second radio bearer, where the carrier mapped by the RLC entity corresponding to the second radio bearer at least partially overlaps with the carrier mapped by the first RLC entity. The terminal device according to claim 8, wherein the processing unit is specifically configured to: And causing the packet data convergence protocol PDCP entity of the first radio bearer to stop copying the PDCP protocol data unit PDU; Stop submitting data to the first RLC entity and submit data to a second RLC entity corresponding to the first radio bearer. The terminal device according to claim 8 or 9, wherein the terminal device further comprises: a sending unit, configured to send, to the network device, indication information, where the indication information is used to indicate that the first radio bearer has a radio link failure RLF, and/or the terminal device deactivates the radio bearer of the replica data transmission function Logo. The terminal device according to any one of claims 8 to 10, wherein the first radio bearer and the second radio bearer correspond to the same cell group or correspond to different cell groups. The terminal device according to claim 11, wherein the group of cells comprises a primary cell group MCG and/or a secondary cell group SCG. The terminal device according to any one of claims 8 to 12, wherein the working mode of the first RLC entity is an acknowledge mode AM, and the working mode of the RLC entity corresponding to the second radio bearer is a confirmation Mode AM or non-acknowledgment mode UM. The terminal device according to any one of claims 8 to 13, wherein the first RLC entity is a primary link of the first radio bearer, and a second RLC corresponding to the first radio bearer The entity is a secondary link of the first radio bearer; or The first RLC entity is a secondary link of the first radio bearer, and the second RLC entity is a primary link of the first radio bearer.

Images