CN111034155B

CN111034155B - Method and device for changing bearer type and computer storage medium

Info

Publication number: CN111034155B
Application number: CN201880052002.1A
Authority: CN
Inventors: 唐海
Original assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Current assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Priority date: 2017-09-15
Filing date: 2018-04-24
Publication date: 2020-12-04
Anticipated expiration: 2038-04-24
Also published as: CN111034155A; WO2019052174A1

Abstract

The invention discloses a method and a device for changing a bearing type and a computer storage medium, wherein the method comprises the following steps: a terminal receives a control signaling, wherein the control signaling carries first indication information, and the first indication information is used for indicating that the terminal is changed from a source bearing type to a target bearing type; and the terminal releases at least one RLC entity corresponding to the source bearing type and creates at least one RLC entity corresponding to the target bearing type based on the transmission characteristics of the source bearing type and the transmission characteristics of the target bearing type.

Description

Method and device for changing bearer type and computer storage medium

Technical Field

The present invention relates to the field of mobile communications, and in particular, to a method and an apparatus for changing a bearer type, and a computer storage medium.

Background

In a wireless communication system, due to the limited bandwidth resources and coverage of a single base station, base stations of different types or the same type need to be cooperatively networked, so that wireless resources of multiple cells or base stations are concentrated to provide services for users, and the capacity requirement and coverage requirement of the users are more easily met, which is generally referred to as multi-connection. Dual Connectivity (DC) is a common multi-connection method.

In a DC scenario, a user may simultaneously maintain a connection with two base stations, and in such a scenario, the user may receive data of one base station alone or data of two base stations simultaneously. According to different service modes provided by the base station for the user, the bearers of the user can be divided into different types, for example: a main cell group bearer (MCG bearer), a secondary cell group bearer (SCG bearer), and a Split bearer (Split bearer). For a certain user, the bearer type of the user can be changed from one bearer type to another bearer type, that is, the bearer type of the certain user is changed.

For a bearer of a certain user, the bearer may support Data replication type transmission, a corresponding Packet Data Convergence Protocol (PDCP) layer has a Data replication function, and the two copies of Data are transmitted to two RLC entities respectively through the PDCP layer and then transmitted on different physical layer Aggregation carriers, which may also be referred to as Carrier Aggregation (CA) replication.

The change of bearer types studied at present does not take the situation of CA redundancy into consideration, and how to implement the change of bearer types in combination with CA redundancy is a problem to be solved.

Disclosure of Invention

To solve the foregoing technical problem, embodiments of the present invention provide a method and an apparatus for changing a bearer type, and a computer storage medium.

The method for changing the bearing type provided by the embodiment of the invention comprises the following steps:

a terminal receives a control signaling, wherein the control signaling carries first indication information, and the first indication information is used for indicating that the terminal is changed from a source bearing type to a target bearing type;

and the terminal releases at least one RLC entity corresponding to the source bearing type and/or creates at least one RLC entity corresponding to the target bearing type based on the transmission characteristics of the source bearing type and the transmission characteristics of the target bearing type.

In this embodiment of the present invention, the control signaling further carries second indication information, where the second indication information is used to indicate whether the target bearer type supports data replication type transmission.

In the embodiment of the invention, the source bearer type supports data replication type transmission, and the target bearer type does not support data replication type transmission; or,

the source bearer type does not support data replication type transmission, and the target bearer type supports data replication type transmission; or,

the source bearer type supports data replication type transmission, and the target bearer type supports data replication type transmission; or,

the source bearer type does not support data replication type transmission and the target bearer type does not support data replication type transmission.

In the embodiment of the present invention, the source bearer type is Non-Split bearer (Non-Split bearer);

the terminal releases at least one RLC entity corresponding to the source bearer type based on the transmission characteristics of the source bearer type and the transmission characteristics of the target bearer type, including:

if the source bearer type supports data replication type transmission, judging whether the target bearer type is a Split load (Split bearer);

if the target bearing type is the Split bearer, releasing one RLC entity from the two RLC entities corresponding to the source bearing type;

and if the target bearer type is not the Split bearer, releasing two RLC entities from the two RLC entities corresponding to the source bearer type.

In the embodiment of the present invention, the target bearer type may support data replication type transmission or may not support data replication type transmission.

In the embodiment of the invention, the target bearing type is Non-Split bearer;

the terminal creates at least one RLC entity corresponding to the target bearer type based on the transmission characteristics of the source bearer type and the transmission characteristics of the target bearer type, including:

if the target bearer type supports data replication type transmission, judging whether the source bearer type is Split bearer;

if the source bearing type is the Split bearer, creating an RLC entity corresponding to the target bearing type;

and if the source bearing type is not the Split bearer, creating two RLC entities corresponding to the target bearing type.

In the embodiment of the present invention, the source bearer type may support data replication type transmission or may not support data replication type transmission.

In the embodiment of the present invention, in the process of changing from the source bearer type to the target bearer type, if the source bearer supports data replication type transmission, no data retransmission operation is performed.

In the embodiment of the present invention, the source bearer supports data replication type transmission, which means that: the source bearer is configured with packet data convergence protocol PDCP replication transport.

In the embodiment of the present invention, the source bearer supports data replication type transmission, which means that: the source bearer configures and activates PDCP duplicate transmission.

In the embodiment of the present invention, if the source bearer supports data replication type transmission and the source bearer is a split bearer, no data retransmission operation is performed.

In the embodiment of the present invention, if the source bearer supports data replication type transmission and the target bearer is a split bearer, no data retransmission operation is performed.

In the embodiment of the present invention, if the source bearer supports data replication type transmission and there is at least one created and unrequired RLC entity in the process of changing from the source bearer type to the target bearer type, no data retransmission operation is performed.

In the embodiment of the present invention, the not performing the data retransmission operation means: the data retransmission operation in the data recovery operation of the PDCP entity is not performed.

In the embodiment of the invention, if the target bearer is not configured or does not activate the PDCP copy transmission, the data retransmission operation is not carried out.

In the embodiment of the present invention, the not performing the data retransmission operation means: data retransmission operations are not performed by the created and non-re-established RLC entities and are not performed by newly created RLC entities and/or re-established RLC entities.

In this embodiment of the present invention, if the target bearer is configured and activated for PDCP duplicate transmission, the not performing data retransmission operation means: the data retransmission operation is not performed by the created and non-re-established RLC entity, but can be performed by the newly created RLC entity and/or the re-established RLC entity.

In the embodiment of the present invention, in the process of changing from the source bearer type to the target bearer type,

if the PDCP entity performs a data recovery operation, a data retransmission operation is performed through the newly created RLC entity and/or the re-established RLC entity.

In this embodiment of the present invention, the data retransmission operation refers to: the re-sending PDCP entity is already sent to the released RLC entity and/or the re-established RLC entity before the data recovery operation is performed, and does not receive data of the successfully received acknowledgement message.

In the embodiment of the present invention, the sending of the data that has been sent to the released RLC entity and/or the re-established RLC entity before the data recovery operation is performed by the re-sending PDCP entity and that has not received the data of the successfully received acknowledgement message includes:

and the PDCP entity is not sent to the created and non-reestablished RLC entity before the data recovery operation is carried out, and the data of the successfully received confirmation message is not received.

in the case that the source bearer is not configured and/or configured but data copy transmission is not activated, the re-sending PDCP entity is already sent to the released RLC entity and/or the re-established RLC entity before performing the data recovery operation, and data of the successfully received acknowledgement message is not received.

and under the condition that the RLC entities are all reestablished or released, the retransmission PDCP entity is already transmitted to the released RLC entity and/or the reestablished RLC entity before the data recovery operation is carried out, and the data of the successfully received confirmation message is not received.

In the embodiment of the present invention, if the data retransmission operation retransmits data that has been sent to an created and non-re-established RLC entity before a PDCP entity performs a data recovery operation, the data retransmission operation is performed by a newly created RLC entity and/or a re-established RLC entity.

In the embodiment of the present invention, if the data retransmission operation retransmits data that is not transmitted to the created and unrecreated RLC entity before the PDCP entity performs the data recovery operation, the data retransmission operation is performed by the newly created RLC entity and/or the re-created RLC entity and/or the created and unrecreated RLC entity.

In the embodiment of the present invention, if a source bearer supports data replication type transmission and a target bearer supports data replication type transmission and the source bearer is a offload bearer, a data retransmission operation is performed by a newly created RLC entity and/or a newly established RLC entity.

In the embodiment of the present invention, if the source bearer supports data replication type transmission and the target bearer is a offload bearer, a data retransmission operation is performed by using the newly created RLC entity and/or the re-established RLC entity.

In the embodiment of the present invention, if a source bearer supports data replication type transmission and a target bearer supports data replication type transmission and there is at least one created and unrecreated RLC entity in the process of changing from the source bearer type to the target bearer type, a data retransmission operation is performed by the newly created RLC entity and/or the re-created RLC entity.

In the embodiment of the present invention, if a source bearer supports data replication type transmission and a target bearer does not support data replication type transmission and there is at least one created and unrecreated RLC entity in the process of changing from the source bearer type to the target bearer type, a data retransmission operation is performed by the newly created RLC entity and/or the reestablished RLC entity.

In the embodiment of the present invention, the target bearer supports data replication transmission, which means: the target bearer is configured for PDCP replication transport.

In the embodiment of the present invention, the target bearer supports data replication transmission, which means: the target bearer configures and activates PDCP duplicate transmission.

In the embodiment of the present invention, the source bearer supports data replication type transmission, which means that: the source bearer is configured with PDCP duplicate transmissions.

The device for changing the bearing type provided by the embodiment of the invention comprises:

a receiving unit, configured to receive a control signaling, where the control signaling carries first indication information, and the first indication information is used to indicate that the terminal changes from a source bearer type to a target bearer type;

a bearer type changing unit configured to release the at least one RLC entity corresponding to the source bearer type and/or create the at least one RLC entity corresponding to the target bearer type based on the transmission characteristics of the source bearer type and the transmission characteristics of the target bearer type.

In the embodiment of the invention, the source bearing type is Non-Split bearer;

the bearer type changing unit includes:

a first determining subunit, configured to determine whether the target bearer type is Split bearer if the source bearer type supports data replication type transmission;

a releasing subunit configured to release one RLC entity from two RLC entities corresponding to the source bearer type if the target bearer type is the Split bearer; and if the target bearer type is not the Split bearer, releasing two RLC entities from the two RLC entities corresponding to the source bearer type.

the bearer type changing unit includes:

a second determining subunit, configured to determine whether the source bearer type is Split bearer if the target bearer type supports data replication type transmission;

a creating subunit, configured to create one RLC entity corresponding to the target bearer type if the source bearer type is the Split bearer; and if the source bearing type is not the Split bearer, creating two RLC entities corresponding to the target bearing type.

In the embodiment of the present invention, the apparatus further includes:

and the retransmission unit is used for not carrying out data retransmission operation if the source bearer supports data replication type transmission.

In the embodiment of the present invention, the apparatus further includes:

and the retransmission unit is used for performing data retransmission operation through the newly created RLC entity and/or the re-established RLC entity if the PDCP entity performs data recovery operation.

In the embodiment of the present invention, if the data retransmission operation retransmits data that has been already transmitted to an created and non-re-established RLC entity before a PDCP entity performs a data recovery operation, the retransmission unit performs a data retransmission operation through a newly created RLC entity and/or a re-established RLC entity.

In the embodiment of the present invention, if the data retransmission operation retransmits data that is not transmitted to the created and unrecreated RLC entity before the PDCP entity performs the data recovery operation, the retransmission unit performs the data retransmission operation through the newly created RLC entity and/or the re-created RLC entity and/or the created and unrecreated RLC entity.

The computer storage medium provided by the embodiment of the invention stores computer executable instructions thereon, and the computer executable instructions when executed by a processor realize the method for changing the bearing type.

In the technical scheme of the embodiment of the invention, a terminal receives a control signaling, the control signaling carries first indication information, and the first indication information is used for indicating that the terminal changes from a source bearing type to a target bearing type; and the terminal releases at least one entity corresponding to the source bearing type and/or creates at least one RLC entity corresponding to the target bearing type based on the transmission characteristics of the source bearing type and the transmission characteristics of the target bearing type. By adopting the technical scheme of the embodiment of the invention, the change of the bearing type can be realized in the double-connection framework by combining the CA redundancy condition, and the application scene of double connection is perfected.

Drawings

The accompanying drawings, which are included to provide a further understanding of the invention and are incorporated in and constitute a part of this application, illustrate embodiment(s) of the invention and together with the description serve to explain the invention without limiting the invention. In the drawings:

FIG. 1 is a schematic diagram of a protocol structure in a DC scenario;

FIG. 2 is a schematic diagram of a protocol structure in a CA duplicate scenario;

fig. 3 is a flowchart illustrating a method for changing bearer types according to an embodiment of the present invention;

fig. 4 is a first schematic diagram of a protocol structure for bearer type change according to an embodiment of the present invention;

fig. 5 is a schematic diagram of a protocol structure for bearer type change according to an embodiment of the present invention;

fig. 6 is a third schematic diagram of a protocol structure for bearer type change according to an embodiment of the present invention;

fig. 7 is a fourth schematic diagram of a protocol structure for bearer type change according to an embodiment of the present invention;

FIG. 8 is a first schematic structural diagram of an apparatus for changing a bearer type according to an embodiment of the present invention;

FIG. 9 is a schematic structural diagram of a device for changing a bearer type according to an embodiment of the present invention;

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

Detailed Description

So that the manner in which the features and aspects of the embodiments of the present invention can be understood in detail, a more particular description of the embodiments of the invention, briefly summarized above, may be had by reference to the embodiments, some of which are illustrated in the appended drawings.

Fig. 1 is a schematic diagram of a protocol structure in a DC scenario, and as shown in fig. 1, MN represents a Master Node (Master Node) on a network side, and SN represents a Slave Node (Slave Node) on the network side. In one embodiment, the MN is a Long Term Evolution (LTE) system, and the SN is an nr (new radio) system; in another embodiment, the MN is an NR system and the SN is an LTE system; in yet another embodiment, the MN is an NR system and the SN is also an NR system. It is noted that MN and SN represent two different network nodes, which may or may not be of different network types.

In the DC architecture, a user can simultaneously maintain a connection with a MN and a SN, where interaction between the MN and the SN is achieved through an X2 interface. As shown in fig. 1, the protocol structure in the DC scenario includes a PDCP layer, an RLC layer, and a Media Access Control (MAC) layer at both the MN and SN sides. For a certain user, it can maintain any bearer type, and the bearer type of the user is specifically explained as follows:

1) for data bearers, the bearer types include:

MCG bearer: the carried radio protocol is only located in the MCG;

MCG split bearer: the loaded wireless protocol is divided at the MN and is positioned at the MCG and the SCG simultaneously;

SCG bearer: the carried radio protocol is only located in SCG;

SCG split beer: the radio protocol carried is split at the SN, and is located at both SCG and MCG.

2) For signaling bearers, the bearer types include:

MCG SRB: signaling Bearers (SRBs) between the MN and the UE;

MCG split SRB: SRB between MN and UE, wherein the UE supports copying Radio Resource Control (RRC) Protocol Data Unit (PDU) through SN;

SCG SRB: SRB between SN and UE.

The following describes in detail the implementation procedure of the protocol stack with reference to each bearer type of the data bearer.

1)MCG bearer：

The transmission channel of the MCG bearer is as shown in fig. 1, the MCG bearer first passes through the MN PDCP layer, the MN PDCP layer processes the MCG bearer and then transmits the MCG bearer to the MN RLC layer, the MN RLC layer processes the MCG bearer and then transmits the MCG bearer to the MN MAC layer, and the MN MAC layer processes the MCG bearer and then transmits the MCG bearer to the user.

2)MCG split bearer：

As shown in fig. 1, a transmission channel of the MCG split bearer first passes through an MN PDCP layer, and the MN PDCP layer divides the MCG split bearer into two parts, where: the first part of bearer is transmitted to the MN RLC layer, the MN RLC layer processes the first part of bearer and then transmits the processed first part of bearer to the MN MAC layer, and the MN MAC layer processes the first part of bearer and then transmits the first part of bearer to the user; and the SN MAC layer processes the second part of bearer and then transmits the second part of bearer to a user.

3)SCG bearer：

As shown in fig. 1, a transmission channel of SCG bearer first passes through an SN PDCP layer, the SN PDCP layer processes SCG bearer and then transmits the SCG bearer to an SN RLC layer, the SN RLC layer processes SCG bearer and then transmits the SCG bearer to an SN MAC layer, and the SN MAC layer processes SCG bearer and then transmits the SCG bearer to a user.

4)SCG split bearer：

As shown in fig. 1, a transmission channel of the SCG split bearer first passes through an SN PDCP layer, and the SN PDCP layer divides the SCG split bearer into two parts, where: the first part of bearer is transmitted to an SN RLC layer, the SN RLC layer processes the first part of bearer and then transmits the processed first part of bearer to an SN MAC layer, and the SN MAC layer processes the first part of bearer and then transmits the first part of bearer to a user; and the second part of bearer is transmitted to an MN RLC layer in the MN, the MN RLC layer processes the second part of bearer and transmits the second part of bearer to an MN MAC layer, and the MN MAC layer processes the second part of bearer and then transmits the second part of bearer to the user.

Those skilled in the art will understand that the protocol structure shown in fig. 1 is applicable not only on the network side, but also on the user side, i.e. the terminal side, and the protocol structure of the terminal corresponds to that of the network.

In the embodiment of the present invention, the bearer types of the users may be mutually transformed, specifically as follows:

1) for data bearers, there are the following types of transitions:

the mutual transformation between the MCG bearer and the MCG split bearer;

mutual conversion between MCG bearer and SCG bearer;

the mutual conversion between MCG bearer and SCG split bearer;

mutual transformation between SCG bearer and SCG split bearer;

a transition from MCG bearer to MCG bearer;

the SCG bearer is converted into the SCG bearer;

transition of MCG split bearer to MCG split bearer;

transformation of SCG split bearer to SCG split bearer.

2) For signaling bearers, there are the following types of transitions:

the mutual transition between MCG SRB and MCG split SRB.

Fig. 2 is a schematic diagram of a protocol structure in a CA duplicate scenario, in which a PDCP layer has a Data copying function, and as shown in fig. 2, a PDCP Service Data unit (SDU, Service Data Uint) is transmitted to the PDCP layer, and the PDCP layer is configured with the Data copying function, so that the PDCP layer can copy one processed PDCP PDU to obtain a Duplicated PDCP PDU, and then transmit the PDCP PDU to an RLC Entity (Entity) a and transmit the Duplicated PDCP PDU to an RLC Entity b, where the RLC Entity a and the RLC Entity b respectively correspond to two different logical channels, and the two copies of Data are processed by the two RLC entities respectively and then transmitted on different Physical layer aggregation carriers by the MAC layer (e.g., Physical Carrier1 and Physical Carrier2 in fig. 2), thereby achieving a frequency diversity gain to improve Data transmission reliability.

In the scheme of fig. 1, for the MCG bearer and the SCG bearer, one PDCP entity corresponds to one RLC entity, and a CA duplicate scenario is not considered, that is, a situation that one PDCP entity corresponds to two RLC entities is not considered.

The following technical solutions of the embodiments of the present invention all use bearer as a data bearer as an example to explain a change of bearer types, and a change of bearer types of signaling bearers is also applicable to the technical solutions of the embodiments of the present invention, where the bearer types involved include: MCG bearer, MCG split bearer, SCG bearer and SCG split bearer, wherein the MCG bearer and the SCG bearer both correspond to a network node on a network side, the MCG bearer corresponds to MN, and the SCG bearer corresponds to SN; the MCG Split bearer and the SCG Split bearer are collectively referred to as Split bearer, and the Split bearer corresponds to two network nodes on the network side, that is, MN and SN.

Fig. 3 is a flowchart illustrating a method for changing a bearer type according to an embodiment of the present invention, where as shown in fig. 3, the method for changing a bearer type includes the following steps:

step 301: the terminal receives a control signaling, wherein the control signaling carries first indication information, and the first indication information is used for indicating that the terminal is changed from a source bearing type to a target bearing type.

In the embodiment of the present invention, the change of the bearer type may be, but is not limited to, triggered by the following manner:

the first method is as follows: in the moving process of the terminal, the distances between the terminal and the MN and the SN are changed continuously. When the terminal is closer to the MN, the corresponding bearing type is MCG bearer; when the terminal is positioned between the MN and the SN, the corresponding bearing type is Split bearer; and when the terminal is closer to the SN, the corresponding bearing type is SCG bearer. Further, when the terminal moves from a position closer to the MN to a position between the MN and the SN, the corresponding bearer type is switched from the MCG bearer to the Split bearer (specifically, MCG Split bearer); and when the terminal moves to be closer to the SN from the MN and the SN, the corresponding bearing type is switched to the SCG bearing from the Split bearing. On the contrary, when the terminal moves from a short distance to the position between the MN and the SN, the corresponding bearer type is switched from SCG bearer to Split bearer (specifically SCG Split bearer); when the terminal moves from between the MN and the SN to be closer to the MN, the corresponding bearing type is switched from the Split bearer to the MCG bearer.

The second method comprises the following steps: in order to implement a certain network policy (e.g., a load balancing policy), the bearer type of the terminal is adjusted between the MN and the SN, for example: the initial bearing type of the terminal is MCG bearer, and when the load of the MN is gradually increased, the MCG bearer can be converted into Split bearer, so that the MN and the SN jointly provide service for the terminal, and the load balance is realized.

And when the network side determines that the terminal needs to change the bearing type, sending a control signaling to the terminal, wherein the control signaling carries first indication information, and the first indication information is used for indicating the terminal to change from the source bearing type to the target bearing type. After receiving the control signaling, the terminal changes the bearer type, that is: from the source bearer type to the target bearer type.

Step 302: and the terminal releases at least one RLC entity corresponding to the source bearing type and/or creates at least one RLC entity corresponding to the target bearing type based on the transmission characteristics of the source bearing type and the transmission characteristics of the target bearing type.

In this embodiment of the present invention, the control signaling further carries second indication information, where the second indication information is used to indicate whether the target bearer type supports data replication type transmission (i.e. CA replication).

The DC architecture of the embodiment of the present invention combines the CA duplicate situation, and therefore, the source bearer type and the target bearer type have the following three transmission feature combinations:

1) the source bearer type supports data replication type transmission, and the target bearer type does not support data replication type transmission;

2) the source bearer type does not support data replication type transmission, and the target bearer type supports data replication type transmission;

3) the source bearer type supports data replication type transmission and the target bearer type supports data replication type transmission.

In addition, the source bearer type and the target bearer type also have the following transmission characteristics:

4) the source bearer type does not support data replication type transmission and the target bearer type does not support data replication type transmission.

Here, the bearer type supporting the data replication type transmission may be: MCG bearer, SCG bearer, Split bearer. Bearer types that do not support data replication type transmission may be: MCG bearer, SCG bearer, Split bearer.

For the source bearer type: the source bearing type is Non-Split bearer; the terminal releases at least one RLC entity corresponding to the source bearer type based on the transmission characteristics of the source bearer type and the transmission characteristics of the target bearer type, including:

if the source bearer type supports data replication type transmission, judging whether the target bearer type is Split bearer;

Here, when the target bearer type is the Split bearer or is not the Split bearer, the target bearer type may or may not support data replication type transmission.

For the target bearer type: the target bearing type is Non-Split bearer; the terminal creates at least one RLC entity corresponding to the target bearer type based on the transmission characteristics of the source bearer type and the transmission characteristics of the target bearer type, including:

Here, when the source bearer type is the Split bearer or is not the Split bearer, the source bearer type may or may not support data copy type transmission.

In the embodiment of the present invention, the PDCP entity may not need to perform an operation during the bearer type change process, or need to perform a data recovery operation, or need to perform a re-establishment operation.

In an embodiment, in the process of changing from the source bearer type to the target bearer type, if the source bearer supports data replication type transmission, no data retransmission operation is performed.

Wherein, the source bearer type supports data duplication type transmission, which means 1) the source bearer type configures packet data convergence protocol PDCP duplication transmission. Or, 2) the source bearer type configures and activates PDCP duplicate transmission.

In the above scheme, the data retransmission operation is not performed, and there are the following cases:

the first condition is as follows: if the source bearer supports data replication type transmission and the source bearer is a split bearer, no data retransmission operation is performed.

Case two: if the source bearer supports data replication type transmission and the target bearer is a split bearer, no data retransmission operation is performed.

Case three: if the source bearer supports data duplicate transmission and there is at least one RLC entity created and not re-established during the change from the source bearer type to the target bearer type, no data retransmission operation is performed.

In the above scheme, the not performing the data retransmission operation means: the data retransmission operation in the data recovery operation of the PDCP entity is not performed.

Here, the data retransmission operation in the PDCP entity data recovery operation is not performed, and there are several cases as follows:

the first condition is as follows: the network does not issue the indication information of the data recovery operation, and therefore the terminal does not perform the data retransmission operation in the data recovery operation of the PDCP entity.

Case two: the network issues the data recovery operation indication information, but the terminal does not perform the PDCP entity data recovery operation.

Case three: the network issues the data recovery operation indication information, but the terminal does not perform the data retransmission operation in the data recovery operation of the PDCP entity.

In an embodiment, if the target bearer is not configured or activated for PDCP duplicate transmission, no data retransmission operation is performed.

In an embodiment, if the target bearer configures and activates PDCP duplicate transmission, the not performing data retransmission operation refers to: the data retransmission operation is not performed by the created and non-re-established RLC entity, but can be performed by the newly created RLC entity and/or the re-established RLC entity.

In an embodiment, during the change from the source bearer type to the target bearer type,

Wherein, the data retransmission operation refers to: the re-sending PDCP entity is already sent to the released RLC entity and/or the re-established RLC entity before the data recovery operation is performed, and does not receive data of the successfully received acknowledgement message.

Further, the data retransmission operation refers to: and the PDCP entity is not sent to the created and non-reestablished RLC entity before the data recovery operation is carried out, and the data of the successfully received confirmation message is not received.

Here, the sending the PDCP entity to the RLC entity that is released and/or the RLC entity that is re-established before the data recovery operation is performed by the sending PDCP entity, and the data that the acknowledgement message is successfully received is not received, includes:

1) in the case that the source bearer is not configured and/or configured but data copy transmission is not activated, the re-sending PDCP entity is already sent to the released RLC entity and/or the re-established RLC entity before performing the data recovery operation, and data of the successfully received acknowledgement message is not received.

2) And under the condition that the RLC entities are all reestablished or released, the retransmission PDCP entity is already transmitted to the released RLC entity and/or the reestablished RLC entity before the data recovery operation is carried out, and the data of the successfully received confirmation message is not received.

In the above scheme, the data recovery operation mainly includes two steps: 1) sending a PDCP status report; 2) and retransmitting the data.

In the above scheme, the newly created RLC entity means that the RLC entity is not originally created, and a new RLC entity is created; the re-established RLC entity is the RLC entity which is updated by means of reset or the like, and the re-establishment of the RLC entity means that the RLC entity clears all buffered data (including data which has not been successfully transmitted) and some other operations.

In an embodiment, if the data retransmission operation retransmits data that has been transmitted to an RLC entity that has been created and not re-established before a PDCP entity performs a data recovery operation, the data retransmission operation is performed by a newly created RLC entity and/or a re-established RLC entity.

In an embodiment, if the data retransmission operation retransmits data that is not transmitted to the created and non-re-established RLC entity before the PDCP entity performs the data recovery operation, the data retransmission operation is performed by the newly created RLC entity and/or the re-established RLC entity and/or the created and non-re-established RLC entity. 1) For example: if the data retransmission operation retransmits the data which is not transmitted to the created and unrecreated RLC entity before the PDCP entity performs the data recovery operation, performing the data retransmission operation through the newly created RLC entity, the created RLC entity and the created RLC entity; 2) for another example: if the data retransmission operation retransmits the data which is not transmitted to the created and unrecreated RLC entity before the PDCP entity performs the data recovery operation, performing the data retransmission operation through the newly created RLC entity and the created and unrecreated RLC entity; 3) another example is: and if the data retransmission operation retransmits the data which is not transmitted to the created and non-reestablished RLC entity before the PDCP entity performs the data recovery operation, performing the data retransmission operation through the reestablished RLC entity and the created and non-reestablished RLC entity.

In an embodiment, if the source bearer supports data replication type transmission and the target bearer supports data replication type transmission and the source bearer is a offload bearer, a data retransmission operation is performed by the newly created RLC entity and/or the re-established RLC entity.

In an embodiment, if the source bearer supports data replication type transmission and the target bearer is a offload bearer, a data retransmission operation is performed by the newly created RLC entity and/or the re-established RLC entity.

In an embodiment, if a source bearer supports data duplication type transmission and a target bearer supports data duplication type transmission and there is at least one created and non-re-established RLC entity in the process of changing from the source bearer type to the target bearer type, a data retransmission operation is performed through the newly created RLC entity and/or the re-established RLC entity.

In an embodiment, if a source bearer supports data duplication type transmission and a target bearer does not support data duplication type transmission and there is at least one created and non-re-established RLC entity in the process of changing from the source bearer type to the target bearer type, a data retransmission operation is performed through the newly created RLC entity and/or the re-established RLC entity.

In the foregoing solution, the target bearer supporting data replication transmission means: 1) the target bearer is configured for PDCP replication transport. Or, 2) the target bearer configures and activates PDCP duplicate transmission.

In the above scheme, the source bearer supporting data replication type transmission means: 1) the source bearer is configured with PDCP duplicate transmissions. Or, 2) the source bearer configures and activates PDCP duplicate transmission.

The technical solution of the embodiments of the present invention is further described in detail with reference to specific application examples.

Application example 1

As shown in fig. 4, in this example, the source bearer type supports data replication type transmission, that is, the source bearer type is MCG bearer or SCG bearer (the following description takes the source bearer type as MCG bearer as an example), the target bearer type is Split bearer, and in this scenario: because the source bearer type supports data replication type transmission, the PDCP layer of the source bearer type corresponds to two RLC entities (both of which correspond to MN), namely RLC Entity a and RLC Entity b; since the target bearer type is Split bearer, the PDCP layer of the target bearer type also corresponds to two RLC entities (one RLC Entity corresponds to MN, and the other RLC Entity corresponds to SN), which are RLC Entity a and RLC Entity c, respectively. It can be seen that, when the bearer type switching is implemented, the RLC Entity b corresponding to the source bearer type needs to be released, and the RLC Entity c corresponding to the target bearer type needs to be created.

Application example two

As shown in fig. 5, in this example, the source bearer type supports data replication type transmission, that is, the source bearer type is MCG bearer or SCG bearer (the source bearer type is MCG bearer in the following description), the target bearer type is not Split bearer, that is, the target bearer type is SCG bearer or MCG bearer (the target bearer type is SCG bearer in the following description), in this scenario: because the source bearer type supports data replication type transmission, the PDCP layer of the source bearer type corresponds to two RLC entities (both of which correspond to MN), namely RLC Entity a and RLC Entity b; because the target bearer type is SCG bearer, the PDCP layer of the target bearer type may correspond to one RLC Entity, or may correspond to two RLC entities, depending on whether the target bearer type supports data replication type transmission, and if the target bearer type does not support data replication type transmission, the PDCP layer of the target bearer type corresponds to one RLC Entity (the RLC Entity corresponds to SN), which is RLC Entity c; if the target bearer type supports data replication type transmission, the PDCP layer of the target bearer type corresponds to two RLC entities (both RLC entities correspond to SNs), which are RLC Entity c and RLC Entity d, respectively. It can be seen that, when the bearer type switching is implemented, the RLC Entity a and the RLC Entity b corresponding to the source bearer type need to be released, and the RLC Entity c corresponding to the target bearer type, or the RLC Entity c and the RLC Entity d need to be created.

Application example three

As shown in fig. 6, in this example, the target bearer type supports data replication type transmission, that is, the target bearer type is MCG bearer or SCG bearer (the following description takes the target bearer type as SCG bearer for example), the source bearer type is Split bearer, and in this scenario: because the target bearer type supports data replication type transmission, the PDCP layer of the target bearer type corresponds to two RLC entities (both RLC entities correspond to SNs), which are RLC Entity b and RLC Entity c, respectively; since the source bearer type is Split bearer, the PDCP layer of the source bearer type also corresponds to two RLC entities (one RLC Entity corresponds to MN, and the other RLC Entity corresponds to SN), which are RLC Entity a and RLC Entity b, respectively. It can be seen that, when the bearer type switching is implemented, the RLC Entity a corresponding to the source bearer type needs to be released, and the RLC Entity c corresponding to the target bearer type needs to be created.

Application example four

As shown in fig. 7, in this example, the target bearer type supports data replication type transmission, that is, the target bearer type is MCG bearer or SCG bearer (the target bearer type is SCG bearer in the following description as an example), the source bearer type is not Split bearer, that is, the source bearer type is SCG bearer or MCG bearer (the source bearer type is MCG bearer in the following description as an example), and in this scenario: because the target bearer type supports data replication type transmission, the PDCP layer of the target bearer type corresponds to two RLC entities (both RLC entities correspond to SNs), which are RLC Entity c and RLC Entity d, respectively; because the source bearer type is the MCG bearer, the PDCP layer of the source bearer type may correspond to one RLC Entity, or may correspond to two RLC entities, depending on whether the source bearer type supports data duplication type transmission, and if the source bearer type does not support data duplication type transmission, the PDCP layer of the source bearer type corresponds to one RLC Entity (the RLC Entity corresponds to MN), which is RLC Entity a; if the source bearer type supports data replication type transmission, the PDCP layer of the source bearer type corresponds to two RLC entities (both RLC entities correspond to MN), which are RLC Entity a and RLC Entity b, respectively. It can be seen that, when the bearer type switching is implemented, the RLC Entity a corresponding to the source bearer type, or the RLC Entity a and the RLC Entity b, need to be released, and the RLC Entity c and the RLC Entity d corresponding to the target bearer type are created.

The application examples of the embodiment of the present invention are not limited to the above examples, and any bearer type transition may be implemented by using the technical solution of the embodiment of the present invention, that is, any bearer type transition implemented based on the idea of the embodiment of the present invention belongs to the protection scope of the present invention.

Fig. 8 is a schematic structural composition diagram of a device for changing a bearer type according to an embodiment of the present invention, as shown in fig. 8, the device for changing a bearer type includes:

a receiving unit 801, configured to receive a control signaling, where the control signaling carries first indication information, and the first indication information is used to indicate that the terminal changes from a source bearer type to a target bearer type;

a bearer type changing unit 802, configured to release at least one RLC entity corresponding to the source bearer type and/or create at least one RLC entity corresponding to the target bearer type based on the transmission characteristics of the source bearer type and the transmission characteristics of the target bearer type.

It should be understood by those skilled in the art that the implementation functions of each unit in the apparatus for changing bearer types shown in fig. 8 can be understood by referring to the related description of the method for changing bearer types. The functions of the units in the bearer type changing apparatus shown in fig. 8 may be implemented by a program running on a processor, or may be implemented by specific logic circuits.

Fig. 9 is a schematic structural composition diagram of a device for changing a bearer type according to an embodiment of the present invention, as shown in fig. 9, the device for changing a bearer type includes:

a receiving unit 901, configured to receive a control signaling, where the control signaling carries first indication information, where the first indication information is used to indicate that the terminal changes from a source bearer type to a target bearer type;

a bearer type changing unit 902, configured to release at least one RLC entity corresponding to the source bearer type and/or create at least one RLC entity corresponding to the target bearer type based on the transmission characteristics of the source bearer type and the transmission characteristics of the target bearer type.

The control signaling also carries second indication information, where the second indication information is used to indicate whether the target bearer type supports data replication type transmission.

the bearer type changing unit 902 includes:

a first determining subunit 9021, configured to determine whether the target bearer type is Split bearer if the source bearer type supports data replication type transmission;

a releasing subunit 9022, configured to release one RLC entity from two RLC entities corresponding to the source bearer type if the target bearer type is the Split bearer; and if the target bearer type is not the Split bearer, releasing two RLC entities from the two RLC entities corresponding to the source bearer type.

the bearer type changing unit 902 includes:

a second determining subunit 9023, configured to determine whether the source bearer type is Split bearer if the target bearer type supports data replication type transmission;

a creating subunit 9024, configured to create, if the source bearer type is the Split bearer, an RLC entity corresponding to the target bearer type; and if the source bearing type is not the Split bearer, creating two RLC entities corresponding to the target bearing type.

In the embodiment of the present invention, the apparatus further includes:

a retransmission unit (not shown in the figure) for not performing a data retransmission operation if the source bearer supports data replication type transmission.

In one embodiment, the source bearer supports data replication type transmission, and means: the source bearer is configured with packet data convergence protocol PDCP replication transport.

In one embodiment, the source bearer supports data replication type transmission, and means: the source bearer configures and activates PDCP duplicate transmission.

In one embodiment, if the source bearer supports data replication type transmission and the source bearer is a split bearer, no data retransmission operation is performed.

In one embodiment, if the source bearer supports data replication type transmission and the target bearer is a split bearer, no data retransmission operation is performed.

In an embodiment, if a source bearer supports data replication type transmission and there is at least one RLC entity that has been created and not re-established during a change from the source bearer type to the target bearer type, no data retransmission operation is performed.

In one embodiment, the not performing the data retransmission operation refers to: the data retransmission operation in the data recovery operation of the PDCP entity is not performed.

In one embodiment, the not performing the data retransmission operation includes: data retransmission operations are not performed by the created and non-re-established RLC entities and are not performed by newly created RLC entities and/or re-established RLC entities.

In the embodiment of the present invention, the apparatus further includes:

a retransmission unit (not shown in the figure) for performing a data retransmission operation through the newly created RLC entity and/or the re-established RLC entity if the PDCP entity performs a data recovery operation.

In an embodiment, the sending of the data to the release RLC entity and/or the re-established RLC entity before the re-sending PDCP entity performs the data recovery operation, and the receiving of the data with the successful receipt of the acknowledgement message includes:

In an embodiment, if the data retransmission operation retransmits data that has been transmitted to an RLC entity that has been created and not re-established before a PDCP entity performs a data recovery operation, the retransmission unit performs a data retransmission operation through the newly created RLC entity and/or the re-established RLC entity.

In an embodiment, if the data retransmission operation retransmits data that is not transmitted to the created and non-re-established RLC entity before the PDCP entity performs the data recovery operation, the retransmission unit performs the data retransmission operation through the newly created RLC entity and/or the re-established RLC entity and/or the created and non-re-established RLC entity.

In an embodiment, the target bearer supports data replication type transmission, and means: the target bearer is configured for PDCP replication transport.

In an embodiment, the target bearer supports data replication type transmission, and means: the target bearer configures and activates PDCP duplicate transmission.

In one embodiment, the source bearer supports data replication type transmission, and means: the source bearer is configured with PDCP duplicate transmissions.

It should be understood by those skilled in the art that the implementation functions of each unit in the apparatus for changing bearer types shown in fig. 9 can be understood by referring to the related description of the method for changing bearer types. The functions of the units in the bearer type changing apparatus shown in fig. 9 may be implemented by a program running on a processor, or may be implemented by specific logic circuits.

The device for changing the bearing type according to the embodiment of the present invention may also be stored in a computer-readable storage medium if it is implemented in the form of a software functional module and sold or used as a stand-alone product. Based on such understanding, the technical solutions of the embodiments of the present invention may be essentially implemented or a part contributing to the prior art may be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the methods described in the embodiments of the present invention. And the aforementioned storage medium includes: various media capable of storing program codes, such as a usb disk, a removable hard disk, a Read Only Memory (ROM), a magnetic disk, or an optical disk. Thus, embodiments of the invention are not limited to any specific combination of hardware and software.

Accordingly, the embodiment of the present invention further provides a computer storage medium, in which computer executable instructions are stored, and when the computer executable instructions are executed by a processor, the method for changing bearer types described above in the embodiment of the present invention is implemented.

Fig. 10 is a schematic structural component diagram of a terminal according to an embodiment of the present invention, and as shown in fig. 10, the terminal 100 may include one or more (only one shown in the figure) processors 12 (the processors 12 may include, but are not limited to, a processing device such as a Microprocessor (MCU) or a Programmable logic device (FPGA), a memory 14 for storing data, and a transmission device 16 for a communication function. It will be understood by those skilled in the art that the structure shown in fig. 10 is merely illustrative and is not intended to limit the structure of the electronic device. For example, terminal 100 may also include more or fewer components than shown in FIG. 10, or have a different configuration than shown in FIG. 10.

The memory 14 can be used for storing software programs and modules of application software, such as program instructions/modules corresponding to the method for changing bearer types in the embodiment of the present invention, and the processor 12 executes various functional applications and data processing by running the software programs and modules stored in the memory 14, so as to implement the method described above. Memory 14 may include high speed random access memory and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some examples, the memory 14 may further include memory located remotely from the processor 12, which may be connected to the terminal 100 via a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.

The transmission means 16 are used for receiving or transmitting data via a network. The above-described specific examples of the network may include a wireless network provided by a communication provider of the terminal 100. In one example, the transmission device 16 includes a Network adapter (NIC) that can be connected to other Network devices through a base station so as to communicate with the internet. In one example, the transmission device 16 may be a Radio Frequency (RF) module, which is used to communicate with the internet in a wireless manner.

The technical schemes described in the embodiments of the present invention can be combined arbitrarily without conflict.

In the embodiments provided in the present invention, it should be understood that the disclosed method and intelligent device may be implemented in other ways. The above-described device embodiments are merely illustrative, for example, the division of the unit is only a logical functional division, and there may be other division ways in actual implementation, such as: multiple units or components may be combined, or may be integrated into another system, or some features may be omitted, or not implemented. In addition, the coupling, direct coupling or communication connection between the components shown or discussed may be through some interfaces, and the indirect coupling or communication connection between the devices or units may be electrical, mechanical or other forms.

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

In addition, all the functional units in the embodiments of the present invention may be integrated into one second processing unit, or each unit may be separately regarded as one unit, or two or more units may be integrated into one unit; the integrated unit can be realized in a form of hardware, or in a form of hardware plus a software functional unit.

The above description is only for the specific embodiments of the present invention, but the scope of the present invention is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present invention, and all the changes or substitutions should be covered within the scope of the present invention.

Claims

1. A method of changing bearer types, the method comprising:

a terminal receives a control signaling, wherein the control signaling carries first indication information and second indication information, and the first indication information is used for indicating that the terminal is changed from a source bearing type to a target bearing type; the second indication information is used for indicating whether the target bearer type supports data replication type transmission;

under the condition that the source bearing type is non-flow load, if the source bearing type supports data replication type transmission and the target bearing type is flow load, releasing one RLC entity from two RLC entities corresponding to the source bearing type; if the source bearer type supports data replication type transmission and the target bearer type is not the shunting load, releasing two RLC entities from two RLC entities corresponding to the source bearer type;

under the condition that the target bearer type is non-flow load, if the target bearer type supports data replication type transmission and the source bearer type is the flow load, establishing an RLC entity corresponding to the target bearer type; and if the target bearer type supports data replication type transmission and the source bearer type is not the shunting load, creating two RLC entities corresponding to the target bearer type.

2. The method of changing bearer types according to claim 1,

the source bearer type supports data replication type transmission, and the target bearer type does not support data replication type transmission; or,

3. A method of changing bearer types according to claim 1, wherein the target bearer type may or may not support data replication type transmission.

4. A method of changing bearer types according to claim 1, wherein the source bearer type may or may not support data replication type transmission.

5. A method of changing bearer type according to any one of claims 1 to 4, wherein in changing from the source bearer type to the target bearer type,

if the source bearer supports data replication type transmission, no data retransmission operation is performed.

6. The method of claim 5, wherein the source bearer supports data replication type transmission, and the method comprises: the source bearer is configured with packet data convergence protocol PDCP replication transport.

7. The method of claim 5, wherein the source bearer supports data replication type transmission, and the method comprises: the source bearer configures and activates PDCP duplicate transmission.

8. The method of changing bearer types according to any one of claims 5 to 7,

if the source bearer supports data replication type transmission and the source bearer is a split bearer, no data retransmission operation is performed.

9. The method of changing bearer types according to any one of claims 5 to 7,

if the source bearer supports data replication type transmission and the target bearer is a split bearer, no data retransmission operation is performed.

10. The method of changing bearer types according to any one of claims 5 to 7,

if the source bearer supports data duplicate transmission and there is at least one RLC entity created and not re-established during the change from the source bearer type to the target bearer type, no data retransmission operation is performed.

11. The method for changing bearer types according to any one of claims 5 to 10, wherein the not performing data retransmission operation refers to: the data retransmission operation in the data recovery operation of the PDCP entity is not performed.

12. The method of changing bearer types according to any one of claims 5 to 11,

if the target bearer is not configured or activated for PDCP duplicate transmission, no data retransmission operation is performed.

13. The method for changing bearer types according to any one of claims 5 to 12, wherein the not performing data retransmission operation means: data retransmission operations are not performed by the created and non-re-established RLC entities and are not performed by newly created RLC entities and/or re-established RLC entities.

14. The method of changing bearer types according to any one of claims 5 to 11,

if the target bearer is configured and the PDCP copy transmission is activated, the not performing the data retransmission operation refers to: the data retransmission operation is not performed by the created and non-re-established RLC entity, but can be performed by the newly created RLC entity and/or the re-established RLC entity.

15. A method of changing bearer type according to any one of claims 1 to 4, wherein in changing from the source bearer type to the target bearer type,

16. The method of claim 15, wherein the data retransmission operation is: the re-sending PDCP entity is already sent to the released RLC entity and/or the re-established RLC entity before the data recovery operation is performed, and does not receive data of the successfully received acknowledgement message.

17. The method of changing bearer types according to claim 16, wherein the retransmitting PDCP entity having sent to the released RLC entity and/or the re-established RLC entity before performing the data recovery operation and not receiving the data successfully receiving the acknowledgement message comprises:

18. The method of changing bearer types according to any of claims 16 to 17, wherein the retransmitting PDCP entity having sent to the released RLC entity and/or the re-established RLC entity before the data recovery operation and not receiving the data of the successfully received acknowledgement message comprises:

19. The method of changing bearer types according to any of claims 16 to 17, wherein the retransmitting PDCP entity having sent to the released RLC entity and/or the re-established RLC entity before the data recovery operation and not receiving the data of the successfully received acknowledgement message comprises:

20. The method of changing bearer types according to any one of claims 15 to 19,

and if the data retransmission operation retransmits the data which is already transmitted to the created and non-reestablished RLC entity before the PDCP entity performs the data recovery operation, performing the data retransmission operation through the newly created RLC entity and/or the reestablished RLC entity.

21. The method of changing bearer types according to any one of claims 15 to 19,

and if the data retransmission operation retransmits the data which is not transmitted to the created and non-reestablished RLC entity before the PDCP entity performs the data recovery operation, performing the data retransmission operation through the newly created RLC entity and/or the reestablished RLC entity and/or the created and non-reestablished RLC entity.

22. The method of changing bearer types according to any one of claims 15 to 21,

if the source bearer supports data replication type transmission and the target bearer supports data replication type transmission and the source bearer is a offload bearer, performing a data retransmission operation through the newly created RLC entity and/or the re-established RLC entity.

23. The method of changing bearer types according to any one of claims 15 to 22,

if the source bearer supports data replication type transmission and the target bearer is a offload bearer, performing a data retransmission operation through the newly created RLC entity and/or the re-established RLC entity.

24. The method of changing bearer types according to any one of claims 15 to 23,

if the source bearer supports data duplication type transmission and the target bearer supports data duplication type transmission and there is at least one created and non-reestablished RLC entity in the process of changing from the source bearer type to the target bearer type, performing a data retransmission operation through the newly created RLC entity and/or the reestablished RLC entity.

25. The method of changing bearer types according to any one of claims 15 to 21,

if the source bearer supports data duplication type transmission and the target bearer does not support data duplication type transmission and there is at least one created and non-re-established RLC entity in the process of changing from the source bearer type to the target bearer type, performing a data retransmission operation through the newly created RLC entity and/or the re-established RLC entity.

26. A method of changing bearer types according to any one of claims 22 to 25, wherein the target bearer supports data replication type transmission, and is: the target bearer is configured for PDCP replication transport.

27. A method of changing bearer types according to any one of claims 22 to 25, wherein the target bearer supports data replication type transmission, and is: the target bearer configures and activates PDCP duplicate transmission.

28. A method of changing bearer types according to any one of claims 22 to 27, wherein the source bearer supports data replication type transmission, and is: the source bearer is configured with PDCP duplicate transmissions.

29. A method of changing bearer types according to any one of claims 22 to 27, wherein the source bearer supports data replication type transmission, and is: the source bearer configures and activates PDCP duplicate transmission.

30. An apparatus for changing bearer types, the apparatus comprising:

a receiving unit, configured to receive a control signaling, where the control signaling carries first indication information and second indication information, and the first indication information is used to indicate that a terminal changes from a source bearer type to a target bearer type; the second indication information is used for indicating whether the target bearer type supports data replication type transmission;

a bearer type changing unit, configured to, if the source bearer type is a non-offload bearer, if the source bearer type supports data replication type transmission and the target bearer type is an offload load, release one RLC entity from two RLC entities corresponding to the source bearer type; if the source bearer type supports data replication type transmission and the target bearer type is not the shunting load, releasing two RLC entities from two RLC entities corresponding to the source bearer type; under the condition that the target bearer type is non-flow load, if the target bearer type supports data replication type transmission and the source bearer type is the flow load, establishing an RLC entity corresponding to the target bearer type; and if the target bearer type supports data replication type transmission and the source bearer type is not the shunting load, creating two RLC entities corresponding to the target bearer type.

31. The apparatus for changing bearer types according to claim 30,

32. The apparatus of claim 30, wherein the target bearer type can support data replication type transmission or not support data replication type transmission.

33. The apparatus of claim 30, wherein the source bearer type can support data replication type transmission or not support data replication type transmission.

34. An apparatus for changing bearer types according to any one of claims 30 to 33, wherein the apparatus further comprises:

35. The apparatus of claim 34, wherein the source bearer supports data replication type transmission, and is configured to: the source bearer is configured with packet data convergence protocol PDCP replication transport.

36. The apparatus of claim 34, wherein the source bearer supports data replication type transmission, and is configured to: the source bearer configures and activates PDCP duplicate transmission.

37. An apparatus for changing bearer types according to any of claims 34 to 36, wherein if a source bearer supports data replication type transmission and the source bearer is a breakout bearer, no data retransmission operation is performed.

38. Apparatus for changing bearer types according to any of claims 34 to 36, wherein if the source bearer supports data replication type transmission and the target bearer is a split bearer, no data retransmission operation is performed.

39. An apparatus for changing bearer type according to any one of claims 34 to 36, wherein if a source bearer supports data replication type transmission and there is at least one RLC entity created and not re-established in the process of changing from the source bearer type to the target bearer type, no data retransmission operation is performed.

40. The apparatus for changing bearer types according to any one of claims 34 to 39, wherein the not performing data retransmission operation means: the data retransmission operation in the data recovery operation of the PDCP entity is not performed.

41. Device for changing bearer types according to any of claims 34 to 40,

42. The apparatus for changing bearer types according to any one of claims 34 to 41, wherein the not performing data retransmission operation means: data retransmission operations are not performed by the created and non-re-established RLC entities and are not performed by newly created RLC entities and/or re-established RLC entities.

43. Device for changing bearer types according to any of claims 34 to 40,

44. An apparatus for changing bearer types according to any one of claims 30 to 33, wherein the apparatus further comprises:

45. The apparatus for changing bearer types according to claim 44, wherein the data retransmission operation refers to: the re-sending PDCP entity is already sent to the released RLC entity and/or the re-established RLC entity before the data recovery operation is performed, and does not receive data of the successfully received acknowledgement message.

46. The apparatus for changing bearer types according to claim 45, wherein the re-sending PDCP entity has sent to the released RLC entity and/or the re-established RLC entity before performing the data recovery operation and has not received the data of the successfully received acknowledgement message, comprising:

47. The apparatus for changing bearer types according to any one of claims 45 to 46, wherein the apparatus for changing bearer types, which has been sent to the released RLC entity and/or the re-established RLC entity before the re-sending PDCP entity performs the data recovery operation and has not received the data of the successful receipt confirmation message, comprises:

48. The apparatus for changing bearer types according to any one of claims 45 to 46, wherein the apparatus for changing bearer types, which has been sent to the released RLC entity and/or the re-established RLC entity before the re-sending PDCP entity performs the data recovery operation and has not received the data of the successful receipt confirmation message, comprises:

49. Device for changing bearer types according to any one of claims 44 to 48,

if the data retransmission operation retransmits the data which is already transmitted to the created and non-reestablished RLC entity before the PDCP entity performs the data recovery operation, the retransmission unit performs the data retransmission operation through the newly created RLC entity and/or the reestablished RLC entity.

50. Device for changing bearer types according to any one of claims 44 to 48,

if the data retransmission operation retransmits the data which is not transmitted to the created and non-reestablished RLC entity before the PDCP entity performs the data recovery operation, the retransmission unit performs the data retransmission operation through the newly created RLC entity and/or the reestablished RLC entity and/or the created and non-reestablished RLC entity.

51. Device for changing bearer types according to any one of claims 44 to 50,

52. Device for changing bearer types according to any of claims 44 to 51,

53. Device for changing bearer types according to any one of claims 44 to 52,

54. Device for changing bearer types according to any one of claims 44 to 50,

55. The apparatus for changing bearer types according to any one of claims 51 to 54, wherein the target bearer supports data replication type transmission, and is configured to: the target bearer is configured for PDCP replication transport.

56. The apparatus for changing bearer types according to any one of claims 51 to 54, wherein the target bearer supports data replication type transmission, and is configured to: the target bearer configures and activates PDCP duplicate transmission.

57. The apparatus for changing bearer types according to any one of claims 51 to 56, wherein the source bearer supports data replication type transmission, and is configured to: the source bearer is configured with PDCP duplicate transmissions.

58. The apparatus for changing bearer types according to any one of claims 51 to 56, wherein the source bearer supports data replication type transmission, and is configured to: the source bearer configures and activates PDCP duplicate transmission.

59. A computer storage medium having stored thereon computer-executable instructions which, when executed by a processor, carry out the method steps of any of claims 1 to 29.

60. A terminal, comprising: a processor, a memory, and a transmission device, wherein,

the memory is for storing a computer program capable of running on the processor,

the transmission device is configured to receive a control signaling, where the control signaling carries first indication information and second indication information, and the first indication information is used to indicate that the terminal is changed from a source bearer type to a target bearer type; the second indication information is used for indicating whether the target bearer type supports data replication type transmission;

the processor is configured to, if the source bearer type is a non-offload load and the source bearer type supports data replication type transmission and the target bearer type is an offload load, release one RLC entity from two RLC entities corresponding to the source bearer type; if the source bearer type supports data replication type transmission and the target bearer type is not the shunting load, releasing two RLC entities from two RLC entities corresponding to the source bearer type; under the condition that the target bearer type is non-flow load, if the target bearer type supports data replication type transmission and the source bearer type is the flow load, establishing an RLC entity corresponding to the target bearer type; and if the target bearer type supports data replication type transmission and the source bearer type is not the shunting load, creating two RLC entities corresponding to the target bearer type.