WO2019052174A1 - 一种改变承载类型的方法及装置、计算机存储介质 - Google Patents

一种改变承载类型的方法及装置、计算机存储介质 Download PDF

Info

Publication number
WO2019052174A1
WO2019052174A1 PCT/CN2018/084182 CN2018084182W WO2019052174A1 WO 2019052174 A1 WO2019052174 A1 WO 2019052174A1 CN 2018084182 W CN2018084182 W CN 2018084182W WO 2019052174 A1 WO2019052174 A1 WO 2019052174A1
Authority
WO
WIPO (PCT)
Prior art keywords
bearer
type
data
rlc entity
transmission
Prior art date
Application number
PCT/CN2018/084182
Other languages
English (en)
French (fr)
Inventor
唐海
Original Assignee
Oppo广东移动通信有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority claimed from PCT/CN2017/101888 external-priority patent/WO2019051775A1/zh
Application filed by Oppo广东移动通信有限公司 filed Critical Oppo广东移动通信有限公司
Priority to CN201880052002.1A priority Critical patent/CN111034155B/zh
Publication of WO2019052174A1 publication Critical patent/WO2019052174A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/22—Manipulation of transport tunnels
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/0001—Arrangements for dividing the transmission path
    • H04L5/0003—Two-dimensional division
    • H04L5/0005—Time-frequency
    • H04L5/0007—Time-frequency the frequencies being orthogonal, e.g. OFDM(A), DMT
    • H04L5/001—Time-frequency the frequencies being orthogonal, e.g. OFDM(A), DMT the frequencies being arranged in component carriers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/15—Setup of multiple wireless link connections
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/30—Connection release
    • H04W76/34—Selective release of ongoing connections

Definitions

  • the present invention relates to the field of mobile communications, and in particular, to a method and apparatus for changing a bearer type, and a computer storage medium.
  • DC Dual Connectivity
  • the user can maintain the connection with two base stations at the same time.
  • the user can receive data of one base station separately or receive data of two base stations at the same time.
  • the bearers of the user can be classified into different types according to the manner in which the base station provides services for the user, for example, a primary cell group bearer (MCG bearer), a secondary cell group bearer (SCG bearer), and a split bearer (Split bearer).
  • MCG bearer primary cell group bearer
  • SCG bearer secondary cell group bearer
  • Split bearer split bearer
  • the bearer type that it has can be changed from one bearer type to another bearer type, that is, a user has changed the bearer type.
  • the bearer can support the data replication type transmission, and the corresponding Packet Data Convergence Protocol (PDCP) layer has the function of copying data, and the duplicated data is separately transmitted to the PDCP layer.
  • PDCP Packet Data Convergence Protocol
  • RLC Radio Link Control
  • Two Radio Link Control (RLC) entities are then transmitted on different physical layer aggregation carriers. This scheme can also be called Carrier Aggregation (CA) duplication.
  • CA Carrier Aggregation
  • an embodiment of the present invention provides a method and apparatus for changing a bearer type, and a computer storage medium.
  • the terminal receives the control signaling, where the control signaling carries the first indication information, where the first indication information is used to indicate that the terminal changes from the source bearer type to the target bearer type;
  • At least one RLC entity corresponding to the source bearer type and/or creating at least one RLC entity corresponding to the target bearer type, based on the transmission feature of the source bearer type and the transmission feature of the target bearer type .
  • control signaling further carries the second indication information, where the second indication information is used to indicate whether the target bearer type supports data replication type transmission.
  • the source bearer type supports data copy type transmission, and the target bearer type does not support data copy type transmission;
  • the source bearer type does not support data copy type transmission, and the target bearer type supports data copy type transmission;
  • the source bearer type supports data copy type transmission, and the target bearer type supports data copy type transmission;
  • the source bearer type does not support data copy type transmission, and the target bearer type does not support data copy type transmission.
  • the source bearer type is a non-splitting bearer (Non-Split bearer);
  • the terminal releasing, by the terminal, the at least one RLC entity corresponding to the source bearer type, based on the transmission feature of the source bearer type and the transmission feature of the target bearer type, including:
  • the source bearer type supports data replication type transmission, determining whether the target bearer type is a split bearer
  • the target bearer type is the split bearer, releasing one RLC entity from two RLC entities corresponding to the source bearer type;
  • the target bearer type is not the split bearer, releasing two RLC entities from two RLC entities corresponding to the source bearer type.
  • the target bearer type can support data copy type transmission or does not support data copy type transmission.
  • the target bearer type is a Non-Split bearer
  • the terminal is configured to create at least one RLC entity corresponding to the target bearer type, based on the transmission feature of the source bearer type and the transmission feature of the target bearer type, including:
  • the target bearer type supports data replication type transmission, determining whether the source bearer type is a Split bearer
  • the source bearer type is the split bearer, create one RLC entity corresponding to the target bearer type
  • the source bearer type is not the split bearer, two RLC entities corresponding to the target bearer type are created.
  • the source bearer type can support data copy type transmission or does not support data copy type transmission.
  • the source bearer supports data replication type transmission, which means that the source bearer is configured with a packet data convergence protocol PDCP replication transmission.
  • the source bearer supports data replication type transmission, that is, the source bearer configuration and the PDCP copy transmission is activated.
  • the source bearer supports data replication type transmission and the source bearer is a offload bearer, no data retransmission operation is performed.
  • the source bearer supports data replication type transmission and the target bearer is a offload bearer, no data retransmission operation is performed.
  • the source bearer supports the data replication type transmission and there is at least one RLC entity that has been created and not re-established in the process of changing from the source bearer type to the target bearer type, no data is performed. Resend the operation.
  • the data retransmission operation is not performed, and the data retransmission operation in the PDCP entity data recovery operation is not performed.
  • the data retransmission operation is not performed.
  • the data retransmission operation does not perform the data retransmission operation by the RLC entity that has been created and not re-established, and does not pass the newly created RLC entity and/or the re-established RLC entity. Perform a data retransmission operation.
  • the data retransmission operation is performed: the data retransmission operation is not performed by the RLC entity that has been created but not re-established, but The data retransmission operation is performed by the newly created RLC entity and/or the re-established RLC entity.
  • a data retransmission operation is performed by the newly created RLC entity and/or the re-established RLC entity.
  • the data retransmission operation refers to: the RLC entity that has been sent to the released RLC entity and/or the re-established RLC entity before the data recovery operation is resent, and the acknowledgment message is not received successfully.
  • the data refers to: the RLC entity that has been sent to the released RLC entity and/or the re-established RLC entity before the data recovery operation is resent, and the acknowledgment message is not received successfully.
  • the resending PDCP entity has sent the data to the released RLC entity and/or the re-established RLC entity before the data recovery operation, and the data of the successful receipt of the acknowledgement message is not received, including:
  • the re-transmitted PDCP entity has been sent to the released RLC entity and/or the re-established RLC entity before the data recovery operation, and the PDCP entity is not sent to the created and non-reestablished RLC entity before the data recovery operation, and is not received.
  • the data that successfully received the confirmation message is not sent to the released RLC entity and/or the re-established RLC entity before the data recovery operation, and is not received.
  • the resending PDCP entity has sent the data to the released RLC entity and/or the re-established RLC entity before the data recovery operation, and the data of the successful receipt of the acknowledgement message is not received, including:
  • the retransmitted PDCP entity has been sent to the released RLC entity and/or the re-established RLC entity before the data recovery operation, and the success is not received. Received data for the confirmation message.
  • the resending PDCP entity has sent the data to the released RLC entity and/or the re-established RLC entity before the data recovery operation, and the data of the successful receipt of the acknowledgement message is not received, including:
  • the PDCP entity is resent to the released RLC entity and/or the re-established RLC entity before the data recovery operation, and the data of the successful receipt of the acknowledgement message is not received.
  • the data that has been sent to the RLC entity that has been created and not re-established before the data recovery operation is performed by the PDCP entity passes the newly created RLC entity and/or re The established RLC entity performs a data retransmission operation.
  • the data that is not sent to the RLC entity that has been created and not re-established before the PDCP entity performs the data recovery operation passes the newly created RLC entity and/or re
  • the established RLC entity and/or the RLC entity that has been created and not re-established performs a data retransmission operation.
  • 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
  • data retransmission is performed by the newly created RLC entity and/or the reestablished RLC entity. operating.
  • the source bearer supports data replication type transmission and the target bearer supports data replication type transmission and the target bearer is a offload bearer
  • data retransmission is performed by the newly created RLC entity and/or the reestablished RLC entity. operating.
  • the source bearer supports the data replication type transmission and the target bearer supports the data replication type transmission, and in the process of changing from the source bearer type to the target bearer type, at least one has been created and not re-established.
  • the RLC entity performs data retransmission operations through the newly created RLC entity and/or the re-established RLC entity.
  • the source bearer supports the data replication type transmission and the target bearer does not support the data replication type transmission, and in the process of changing from the source bearer type to the target bearer type, at least one has been created and is not re-established.
  • the established RLC entity performs data retransmission operations through the newly created RLC entity and/or the re-established RLC entity.
  • the target bearer supports data replication type transmission, which means that the target bearer is configured with PDCP replication transmission.
  • the target bearer supports data replication type transmission, which means that the target bearer configuration and the PDCP replication transmission are activated.
  • the source bearer supports data replication type transmission, which means that the source bearer is configured with PDCP replication transmission.
  • the source bearer supports data replication type transmission, that is, the source bearer configuration and the PDCP copy transmission is activated.
  • the receiving unit is configured to receive the control signaling, where the control signaling carries the first indication information, where the first indication information is used to indicate that the terminal changes from the source bearer type to the target bearer type;
  • a bearer type change unit configured to release at least one RLC entity corresponding to the source bearer type, and/or create a target bearer type corresponding to the transport feature of the source bearer type and the transport feature of the target bearer type At least one RLC entity.
  • control signaling further carries the second indication information, where the second indication information is used to indicate whether the target bearer type supports data replication type transmission.
  • the source bearer type supports data copy type transmission, and the target bearer type does not support data copy type transmission;
  • the source bearer type does not support data copy type transmission, and the target bearer type supports data copy type transmission;
  • the source bearer type supports data copy type transmission, and the target bearer type supports data copy type transmission;
  • the source bearer type does not support data copy type transmission, and the target bearer type does not support data copy type transmission.
  • the source bearer type is a Non-Split bearer
  • the bearer type changing unit includes:
  • a first determining subunit configured to determine, if the source bearer type supports data replication type transmission, whether the target bearer type is a Split bearer
  • releasing the subunit configured to release one RLC entity from the two RLC entities corresponding to the source bearer type if the target bearer type is the split bearer; if the target bearer type is not the Split bearer, Two RLC entities are released from two RLC entities corresponding to the source bearer type.
  • the target bearer type can support data copy type transmission or does not support data copy type transmission.
  • the target bearer type is a Non-Split bearer
  • the bearer type changing unit includes:
  • a second determining sub-unit configured to determine whether the source bearer type is a Split bearer if the target bearer type supports data replication type transmission;
  • Creating a sub-unit configured to: if the source bearer type is the split bearer, create one RLC entity corresponding to the target bearer type; if the source bearer type is not the split bearer, create the target bearer type Corresponding two RLC entities.
  • the source bearer type can support data copy type transmission or does not support data copy type transmission.
  • the device further includes:
  • the retransmission unit is configured to perform no data retransmission operation if the source bearer supports data copy type transmission.
  • the source bearer supports data replication type transmission, which means that the source bearer is configured with a packet data convergence protocol PDCP replication transmission.
  • the source bearer supports data replication type transmission, that is, the source bearer configuration and the PDCP copy transmission is activated.
  • the source bearer supports data replication type transmission and the source bearer is a offload bearer, no data retransmission operation is performed.
  • the source bearer supports data replication type transmission and the target bearer is a offload bearer, no data retransmission operation is performed.
  • the source bearer supports the data replication type transmission and there is at least one RLC entity that has been created and not re-established in the process of changing from the source bearer type to the target bearer type, no data is performed. Resend the operation.
  • the data retransmission operation is not performed, and the data retransmission operation in the PDCP entity data recovery operation is not performed.
  • the data retransmission operation is not performed.
  • the data retransmission operation does not perform the data retransmission operation by the RLC entity that has been created and not re-established, and does not pass the newly created RLC entity and/or the re-established RLC entity. Perform a data retransmission operation.
  • the data retransmission operation is performed: the data retransmission operation is not performed by the RLC entity that has been created but not re-established, but The data retransmission operation is performed by the newly created RLC entity and/or the re-established RLC entity.
  • the device further includes:
  • a retransmission unit configured to perform a data retransmission operation by using the newly created RLC entity and/or the re-established RLC entity if the PDCP entity performs a data recovery operation.
  • the data retransmission operation refers to: the RLC entity that has been sent to the released RLC entity and/or the re-established RLC entity before the data recovery operation is resent, and the acknowledgment message is not received successfully.
  • the data refers to: the RLC entity that has been sent to the released RLC entity and/or the re-established RLC entity before the data recovery operation is resent, and the acknowledgment message is not received successfully.
  • the resending PDCP entity has sent the data to the released RLC entity and/or the re-established RLC entity before the data recovery operation, and the data of the successful receipt of the acknowledgement message is not received, including:
  • the re-transmitted PDCP entity has been sent to the released RLC entity and/or the re-established RLC entity before the data recovery operation, and the PDCP entity is not sent to the created and non-reestablished RLC entity before the data recovery operation, and is not received.
  • the data that successfully received the confirmation message is not sent to the released RLC entity and/or the re-established RLC entity before the data recovery operation, and is not received.
  • the resending PDCP entity has sent the data to the released RLC entity and/or the re-established RLC entity before the data recovery operation, and the data of the successful receipt of the acknowledgement message is not received, including:
  • the retransmitted PDCP entity has been sent to the released RLC entity and/or the re-established RLC entity before the data recovery operation, and the success is not received. Received data for the confirmation message.
  • the resending PDCP entity has sent the data to the released RLC entity and/or the re-established RLC entity before the data recovery operation, and the data of the successful receipt of the acknowledgement message is not received, including:
  • the PDCP entity is resent to the released RLC entity and/or the re-established RLC entity before the data recovery operation, and the data of the successful receipt of the acknowledgement message is not received.
  • the retransmission unit passes the newly created RLC.
  • the entity and/or the re-established RLC entity performs a data retransmission operation.
  • the retransmission unit passes the newly created RLC.
  • the entity and/or the re-established RLC entity and/or the RLC entity that has been created and not re-established performs a data retransmission operation.
  • 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
  • data retransmission is performed by the newly created RLC entity and/or the reestablished RLC entity. operating.
  • the source bearer supports data replication type transmission and the target bearer supports data replication type transmission and the target bearer is a offload bearer
  • data retransmission is performed by the newly created RLC entity and/or the reestablished RLC entity. operating.
  • the source bearer supports the data replication type transmission and the target bearer supports the data replication type transmission, and in the process of changing from the source bearer type to the target bearer type, at least one has been created and not re-established.
  • the RLC entity performs data retransmission operations through the newly created RLC entity and/or the re-established RLC entity.
  • the source bearer supports the data replication type transmission and the target bearer does not support the data replication type transmission, and in the process of changing from the source bearer type to the target bearer type, at least one has been created and is not re-established.
  • the established RLC entity performs data retransmission operations through the newly created RLC entity and/or the re-established RLC entity.
  • the target bearer supports data replication type transmission, which means that the target bearer is configured with PDCP replication transmission.
  • the target bearer supports data replication type transmission, which means that the target bearer configuration and the PDCP replication transmission are activated.
  • the source bearer supports data replication type transmission, which means that the source bearer is configured with PDCP replication transmission.
  • the source bearer supports data replication type transmission, that is, the source bearer configuration and the PDCP copy transmission is activated.
  • the computer storage medium provided by the embodiment of the present invention has stored thereon computer executable instructions, and the computer executable instructions are implemented by the processor to implement the method for changing the bearer type.
  • the terminal receives the control signaling, where the control signaling carries the first indication information, where the first indication information is used to indicate that the terminal changes from the source bearer type to the target bearer type; And the terminal is configured to release at least one 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 feature of the source bearer type and the transmission feature of the target bearer type.
  • the change of the bearer type can be implemented in the dual-connection architecture in combination with the CA dulication, and the application scenario of the dual connectivity is improved.
  • FIG. 1 is a schematic diagram of a protocol structure in a DC scenario
  • FIG. 2 is a schematic structural diagram of a protocol in a CA duplication scenario
  • FIG. 3 is a schematic flowchart of a method for changing a bearer type according to an embodiment of the present invention
  • FIG. 4 is a schematic structural diagram 1 of a protocol for changing a bearer type according to an embodiment of the present invention
  • FIG. 5 is a schematic structural diagram 2 of a protocol for changing a bearer type according to an embodiment of the present invention
  • FIG. 6 is a schematic structural diagram 3 of a protocol for changing a bearer type according to an embodiment of the present invention.
  • FIG. 7 is a schematic structural diagram 4 of a protocol for changing a bearer type according to an embodiment of the present invention.
  • FIG. 8 is a first schematic structural diagram of a device for changing a bearer type according to an embodiment of the present invention.
  • FIG. 9 is a second 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.
  • FIG. 1 is a schematic diagram of a protocol structure in a DC scenario.
  • MN represents a master node on the network side
  • SN represents a slave node on the network side.
  • the MN is a Long Term Evolution (LTE) system
  • the SN is an NR (New Radio) system.
  • the MN is an NR system
  • the SN is an LTE system.
  • MN is the NR system and SN is also the NR system. It is worth noting that MN and SN represent two different network nodes, and the network types of the two different network nodes may be different or the same.
  • the user can maintain a connection with the MN and the SN at the same time, wherein the MN and the SN interact through the X2 interface.
  • the protocol structure in the DC scenario has a PDCP layer, an RLC layer, and a Media Access Control (MAC) layer on both the MN and the SN side.
  • MAC Media Access Control
  • it can maintain any type of bearer. The following describes the user's bearer type:
  • the bearer types include:
  • MCG bearer The wireless protocol carried is only located in the MCG
  • MCG split bearer the bearer wireless protocol is split in the MN, and is located at the MCG and the SCG;
  • SCG bearer The wireless protocol carried is only located in the SCG
  • SCG split bearer The bearer's wireless protocol is split at the SN and is located at both the SCG and the MCG.
  • the bearer types include:
  • MCG SRB Signaling bearer (SRB, Signaling Radio Bearers) between the MN and the UE;
  • MCG split SRB SRB between the MN and the UE, where the UE supports the RRC (Radio Resource Control) Protocol Data Unit (PDU) through the SN;
  • RRC Radio Resource Control
  • PDU Protocol Data Unit
  • SCG SRB SRB between the SN and the UE.
  • the transmission channel of the MCG bearer is shown in Figure 1.
  • the MCG bearer first passes through the MN PDCP layer.
  • the MN PDCP layer processes the MCG bearer and transmits it to the MN RLC layer.
  • the MN RLC layer processes the MCG bearer and transmits it to the MN MAC layer.
  • the MN MAC layer After processing the MCG bearer, the MCG bearer is sent to the user.
  • the transmission channel of the MCG split bearer is as shown in Figure 1.
  • the MCG split bearer first passes through the MN PDCP layer, and the MN PDCP layer processes the MCG split bearer to split the MCG split bearer into two parts, where: A part of the bearer is transmitted to the MN RLC layer, and the MN RLC layer processes the first part of the bearer and transmits it to the MN MAC layer.
  • the MN MAC layer processes the first part of the bearer and sends the first part of the bearer to the user; the second part of the bearer transmits to the SN in the SN.
  • the RLC layer, the SN RLC layer processes the second part bearer and transmits it to the SN MAC layer, and the SN MAC layer processes the second part bearer and sends the second part bearer to the user.
  • the transmission channel of the SCG bearer is shown in Figure 1.
  • the SCG bearer first passes through the SN PDCP layer.
  • the SN PDCP layer processes the SCG bearer and transmits it to the SN RLC layer.
  • the SN RLC layer processes the SCG bearer and transmits it to the SN MAC layer.
  • the SN MAC layer Send the SCG bearer to the user after processing the SCG bearer.
  • the transmission channel of the SCG split bearer is shown in Figure 1.
  • the SCG split bearer first passes through the SN PDCP layer, and the SN PDCP layer processes the SCG split bearer to split the SCG split bearer into two parts, where: A part of the bearer is transmitted to the SN RLC layer, and the SN RLC layer processes the first part of the bearer and transmits it to the SN MAC layer.
  • the SN MAC layer processes the first part of the bearer and then sends the first part of the bearer to the user.
  • the second part of the bearer transmits to the MN in the MN.
  • the RLC layer, the MN RLC layer processes the second part bearer and transmits it to the MN MAC layer
  • the MN MAC layer processes the second part bearer and sends the second part bearer to the user.
  • the protocol structure shown in FIG. 1 is applicable not only on the network side but also on the user side, that is, on the terminal side, and the protocol structure of the terminal corresponds to the protocol structure of the network.
  • the bearer types of the users may be mutually changed, as follows:
  • MCG split bearer 's transition to MCG split bearer
  • FIG 2 is a schematic diagram of the protocol structure in the CA duplication scenario.
  • the PDCP layer has the function of replicating data.
  • the PDCP service data unit SDU, Service Data Uint
  • SDU Service Data Uint
  • the function of copying data is configured. Therefore, the PDCP layer can copy the processed PDCP PDU to obtain a Duplicated PDCP PDU.
  • the PDCP PDU is transmitted to the RLC entity (Entity) a, and the Duplicated PDCP PDU is transmitted to the RLC Entity b.
  • RLC Entity a and RLC Entity b respectively correspond to two different logical channels, respectively processing two pieces of data through two RLC Entities, and then transmitting two pieces of data on different physical layer aggregate carriers through the MAC layer (eg Physical Carrier 1 and Physical Carrier 2 in Figure 2, thereby achieving frequency diversity gain to improve data transmission reliability.
  • the MAC layer eg Physical Carrier 1 and Physical Carrier 2 in Figure 2, thereby achieving frequency diversity gain to improve data transmission reliability.
  • one PDCP entity corresponds to one RLC entity
  • the CA duplication scenario is not considered, that is, the situation corresponding to two RLC entities under one PDCP entity is not considered.
  • the technical solution of the embodiment of the present invention can implement a change of a bearer type in combination with CA duplication.
  • the bearer as a data bearer as an example to explain the change of the bearer type
  • the change of the bearer type of the signaling bearer is also applicable to the technical solution of the embodiment of the present invention
  • the bearer type involved includes MCG bearer, MCG split bearer, SCG bearer, SCG split bearer, where MCG bearer and SCG bearer correspond to one network node on the network side, MCG bearer corresponds to MN, SCG bearer corresponds to SN; MCG split bearer and SCG split bearer are collectively referred to as Split bearer, Split bearer corresponds to two network nodes on the network side, namely MN and SN.
  • FIG. 3 is a schematic flowchart of a method for changing a bearer type according to an embodiment of the present invention. As shown in FIG. 3, the method for changing a bearer type includes the following steps:
  • Step 301 The terminal receives the control signaling, where the control signaling carries the first indication information, where the first indication information is used to indicate that the terminal changes from the source bearer type to the target bearer type.
  • the change of the bearer type may be, but is not limited to, triggered by:
  • Manner 1 During the movement of the terminal, the distance from the MN and the SN constantly changes.
  • the corresponding bearer type is the MCG bearer; when the terminal is located between the MN and the SN, the corresponding bearer type is the split bearer; when the terminal is closer to the SN, the corresponding bearer type is the SCG bearer.
  • the corresponding bearer type is switched from the MCG bearer to the split bearer (specifically, the MCG split bearer); when the terminal moves from the MN and the SN to the distance SN The corresponding bearer type is switched from the Split bearer to the SCG bearer.
  • the corresponding bearer type is switched from the SCG bearer to the Split bearer (specifically, the SCG split bearer); when the terminal moves from the MN to the SN to be closer to the MN The corresponding bearer type is switched from the Split bearer to the MCG bearer.
  • the MN and the SN adjust the bearer type of the terminal.
  • the bearer type of the terminal is MCG bearer.
  • the MN and the SN may The bearer type of the terminal is changed from the MCG bearer to the split bearer, so that the MN and the SN jointly provide services for the terminal to achieve load balancing.
  • the control signaling is sent to the terminal, where the control signaling carries the first indication information, where the first indication information is used to indicate that the terminal changes from the source bearer type to the target bearer.
  • the terminal After receiving the control signaling, the terminal changes the bearer type, that is, changes from the source bearer type to the target bearer type.
  • Step 302 The terminal releases at least one RLC entity corresponding to the source bearer type, and/or creates at least one corresponding to the target bearer type, based on the transmission feature of the source bearer type and the transmission feature of the target bearer type.
  • An RLC entity is an RLC entity.
  • control signaling further carries the second indication information, where the second indication information is used to indicate whether the target bearer type supports data replication type transmission (ie, CA duplication).
  • the DC architecture of the embodiment of the present invention combines the case of CA duplication. Therefore, the source bearer type and the target bearer type have the following three combinations of transport characteristics:
  • the source bearer type supports data replication type transmission, and the target bearer type does not support data replication type transmission;
  • the source bearer type supports data copy type transmission
  • the target bearer type supports data copy type transmission.
  • the source bearer type and the target bearer type also have the following transport characteristics:
  • the source bearer type does not support data copy type transmission
  • the target bearer type does not support data copy type transmission
  • the bearer type supporting the data copy type transmission may be: MCG bearer, SCG bearer, Split bearer.
  • the bearer types that do not support data replication type transmission may be: MCG bearer, SCG bearer, and split bearer.
  • the source bearer type is a Non-Split bearer; the terminal releases at least one corresponding to the source bearer type based on the transmission characteristics of the source bearer type and the transmission feature of the target bearer type RLC entities, including:
  • the source bearer type supports the data replication type transmission, determining whether the target bearer type is a Split bearer
  • the target bearer type is the split bearer, releasing one RLC entity from two RLC entities corresponding to the source bearer type;
  • the target bearer type is not the split bearer, releasing two RLC entities from two RLC entities corresponding to the source bearer type.
  • the target bearer type when the target bearer type is the Split bearer or not the Split bearer, the target bearer type can support data copy type transmission or does not support data copy type transmission.
  • the target bearer type is a Non-Split bearer; the terminal creates at least one 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.
  • RLC entities including:
  • the target bearer type supports data replication type transmission, determining whether the source bearer type is a Split bearer
  • the source bearer type is the split bearer, create one RLC entity corresponding to the target bearer type
  • the source bearer type is not the split bearer, two RLC entities corresponding to the target bearer type are created.
  • the source bearer type when the source bearer type is the Split bearer or not the Split bearer, the source bearer type can support data copy type transmission or does not support data copy type transmission.
  • the PDCP entity may not need to perform operations in the process of changing the bearer type, or needs to perform a data recovery operation, or needs to perform a reconstruction operation.
  • the source bearer type supports data replication type transmission, which means that 1) the source bearer type is configured with a packet data convergence protocol PDCP copy transmission. Or, 2) the source bearer type configures and activates the PDCP copy transmission.
  • Case 1 If the source bearer supports data replication type transmission and the source bearer is a offload bearer, no data retransmission operation is performed.
  • Case 3 If the source bearer supports the data replication type transmission and there is at least one RLC entity that has been 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. .
  • the data retransmission operation is not performed, and the data retransmission operation in the PDCP entity data recovery operation is not performed.
  • Case 1 The network does not send the data recovery operation indication information, and the terminal does not perform the data retransmission operation in the PDCP entity data recovery operation.
  • Case 2 The network sends the data recovery operation indication information, but the terminal does not perform the PDCP entity data recovery operation.
  • Case 3 The network sends the data recovery operation indication information, but the terminal does not perform the data retransmission operation in the PDCP entity data recovery operation.
  • the data retransmission operation does not perform the data retransmission operation by the RLC entity that has been created and not re-established, and does not pass the newly created RLC entity and/or the re-established RLC entity. Perform a data retransmission operation.
  • the data retransmission operation is performed: the data retransmission operation is not performed by the RLC entity that has been created but not re-established, but The data retransmission operation is performed by the newly created RLC entity and/or the re-established RLC entity.
  • a data retransmission operation is performed by the newly created RLC entity and/or the re-established RLC entity.
  • the data retransmission operation refers to: resending the PDCP entity to the released RLC entity and/or the re-established RLC entity before performing the data recovery operation, and receiving no data for successfully receiving the acknowledgement message.
  • the data retransmission operation refers to: the RLC entity that has been sent to the released RLC entity and/or the re-established RLC entity before the data recovery operation is resent, and the PDCP entity is not sent to the created data before the data recovery operation is performed.
  • the RLC entity has not been re-established, and no data has been received that successfully received the acknowledgment message.
  • the resending PDCP entity has sent the data to the released RLC entity and/or the re-established RLC entity before the data recovery operation, and does not receive the data of successfully receiving the acknowledgement message, including:
  • the PDCP entity is resent to the released RLC entity and/or the re-established RLC entity before the data recovery operation, and the data is not received. Data to the successful receipt of the confirmation message.
  • the PDCP entity is resent to the released RLC entity and/or the re-established RLC entity before the data recovery operation, and the data that successfully received the acknowledgement message is not received.
  • the data recovery operation mainly includes two steps: 1) transmitting a PDCP status report; 2) retransmitting data.
  • the newly created RLC entity means that the RLC entity is not originally created, and an RLC entity is newly created.
  • the re-established RLC entity refers to the original RLC entity, and the RLC entity is updated by resetting, etc.
  • RLC entity re-establishment means that the RLC entity clears all cached data (including data that has not been successfully sent) and some other operations.
  • the data retransmission operation is retransmitted is data that has been sent to the RLC entity that has been created and not re-established before the data recovery operation by the PDCP entity, the newly created RLC entity and/or re The established RLC entity performs a data retransmission operation.
  • the newly created RLC entity and/or re performs a data retransmission operation.
  • the data of the entity is performed by the newly created RLC entity and the RLC entity that has been created and not re-established; 3) another example: if the data retransmission operation is retransmitted before the PDCP entity performs the data recovery operation Data that is not sent to the RLC entity that has been created and not re-established is then re-transmitted by the re-established RLC entity and the RLC entity that has been created and not re-established.
  • data retransmission is performed by the newly created RLC entity and/or the reestablished RLC entity. operating.
  • data retransmission is performed by the newly created RLC entity and/or the reestablished RLC entity. operating.
  • the source bearer supports data replication type transmission and the target bearer supports data replication type transmission and in the process of changing from the source bearer type to the target bearer type, at least one has been created and not re-established
  • the RLC entity performs data retransmission operations through the newly created RLC entity and/or the re-established RLC entity.
  • the source bearer supports data replication type transmission and the target bearer does not support data replication type transmission and in the process of changing from the source bearer type to the target bearer type, at least one has been created and not re-established
  • the established RLC entity performs data retransmission operations through the newly created RLC entity and/or the re-established RLC entity.
  • the target bearer supports data replication type transmission, which means: 1) the target bearer is configured with PDCP replication transmission. Or, 2) the target bearer configuration and activate the PDCP copy transmission.
  • the source bearer supports data replication type transmission, which means: 1) the source bearer is configured with PDCP replication transmission. Or, 2) the source bearer configuration and activates the PDCP copy transmission.
  • the source bearer type supports data replication type transmission, that is, the source bearer type is MCG bearer or SCG bearer (the following description uses the source bearer type as MCG bearer as an example), and the target bearer type is Split bearer.
  • the source bearer type supports the data replication type transmission. Therefore, the PDCP layer of the source bearer type corresponds to two RLC entities (both RLC entities correspond to MN), which are respectively RLC Entity a and RLC Entity b;
  • the target bearer type is a split bearer.
  • the PDCP layer of the target bearer type also corresponds to two RLC entities (one RLC entity corresponds to the MN and the other RLC entity corresponds to the 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 is created.
  • the source bearer type supports data replication type transmission, that is, the source bearer type is MCG bearer or SCG bearer (the following description uses the source bearer type as MCG bearer as an example), and the target bearer type is not Split bearer.
  • the target bearer type is the SCG bearer or the MCG bearer.
  • the scenario is as follows: The source bearer type supports the data replication type transmission. Therefore, the source bearer type corresponds to the PDCP layer.
  • RLC entities both RLC entities corresponding to MN are respectively RLC Entity a and RLC Entity b; since 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 The RLC entity depends on whether the target bearer type supports data replication type transmission. 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 the SN), which is the RLC Entity.
  • the target bearer type supports data replication type transmission
  • the PDCP layer of the target bearer type corresponds to two RLC entities (two RLC entity corresponds SN), respectively, RLC Entity c, RLC Entity d. 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 are released, and the RLC Entity c corresponding to the target bearer type is created, or RLC Entity c and RLC Entity d.
  • the target bearer type supports data replication type transmission, that is, the target bearer type is MCG bearer or SCG bearer (the following description uses the target bearer type as SCG bearer as an example), and the source bearer type is Split bearer.
  • the target bearer type supports data replication type transmission. Therefore, the PDCP layer of the target bearer type corresponds to two RLC entities (both RLC entities correspond to SN), which are RLC Entity b and RLC Entity c respectively;
  • the source bearer type is a split bearer.
  • the PDCP layer of the source bearer type also corresponds to two RLC entities (one RLC entity corresponds to the MN and the other RLC entity corresponds to the 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 is created.
  • the target bearer type supports data replication type transmission, that is, the target bearer type is MCG bearer or SCG bearer (the following description uses the target bearer type as SCG bearer as an example), and the source bearer type is not Split bearer.
  • the source bearer type is the SCG bearer or the MCG bearer. The following describes the source bearer type as the MCG bearer.
  • the target bearer type supports the data replication type transmission. Therefore, the target bearer type corresponds to the PDCP layer.
  • RLC entities both RLC entities corresponding to SN
  • RLC Entity c and RLC Entity d are respectively RLC Entity c and RLC Entity d; since the source bearer type is MCG bearer, the PDCP layer of the source bearer type may correspond to one RLC entity, or may correspond to two Depending on whether the source bearer type supports data replication type transmission, if the source bearer type does not support data replication type transmission, the PDCP layer of the source bearer type corresponds to one RLC entity (the RLC entity corresponds to the MN), which is RLC Entity.
  • the PDCP layer of the source bearer type corresponds to two RLC entities (both RLC entities) Shall MN), respectively, RLC Entity a, RLC Entity b. It can be seen that, when the bearer type switching is implemented, the RLC Entity a corresponding to the source bearer type, or RLC Entity a and RLC Entity b, needs to be released, and RLC Entity c and RLC Entity d corresponding to the target bearer type are created.
  • FIG. 8 is a first schematic structural 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:
  • the receiving unit 801 is configured to receive the control signaling, where the control signaling carries the first indication information, where the first indication information is used to indicate that the terminal changes from the source bearer type to the target bearer type;
  • the bearer type change unit 802 is configured to release at least one RLC entity corresponding to the source bearer type, and/or create the target bearer type corresponding to the transport feature of the source bearer type and the transport feature of the target bearer type. At least one RLC entity.
  • each unit in the device of the change-bearing type shown in FIG. 8 can be understood by referring to the related description of the foregoing method for changing the bearer type.
  • the functions of the units in the device of the change-bearing type shown in FIG. 8 can be realized by a program running on the processor, or can be realized by a specific logic circuit.
  • FIG. 9 is a second structural 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:
  • the receiving unit 901 is configured to receive the control signaling, where the control signaling carries the first indication information, where the first indication information is used to indicate that the terminal changes from the source bearer type to the target bearer type;
  • the bearer type change unit 902 is configured to release at least one RLC entity corresponding to the source bearer type, and/or create the target bearer type corresponding to the transport feature of the source bearer type and the transport feature of the target bearer type. At least one RLC entity.
  • 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.
  • the source bearer type supports data copy type transmission, and the target bearer type does not support data copy type transmission;
  • the source bearer type does not support data copy type transmission, and the target bearer type supports data copy type transmission;
  • the source bearer type supports data copy type transmission, and the target bearer type supports data copy type transmission;
  • the source bearer type does not support data copy type transmission, and the target bearer type does not support data copy type transmission.
  • the source bearer type is a Non-Split bearer
  • the bearer type changing unit 902 includes:
  • the first determining sub-unit 9021 is configured to determine, if the source bearer type supports data replication type transmission, whether the target bearer type is a Split bearer;
  • a release subunit 9022 configured to release an RLC entity from two RLC entities corresponding to the source bearer type if the target bearer type is the split bearer; if the target bearer type is not the Split bearer, Then, two RLC entities are released from two RLC entities corresponding to the source bearer type.
  • the target bearer type can support data copy type transmission or does not support data copy type transmission.
  • the target bearer type is a Non-Split bearer
  • the bearer type changing unit 902 includes:
  • the second determining sub-unit 9023 is configured to determine, if the target bearer type supports data replication type transmission, whether the source bearer type is a Split bearer;
  • a sub-unit 9024 configured to: if the source bearer type is the split bearer, create one RLC entity corresponding to the target bearer type; if the source bearer type is not the split bearer, create the target bearer Two RLC entities corresponding to the type.
  • the source bearer type can support data copy type transmission or does not support data copy type transmission.
  • the device further includes:
  • a retransmission unit (not shown) for not performing a data retransmission operation if the source bearer supports data copy type transmission.
  • the source bearer supports data replication type transmission, that is, the source bearer is configured with a packet data convergence protocol PDCP replication transmission.
  • the source bearer supports data replication type transmission, that is, the source bearer configuration and the PDCP copy transmission is activated.
  • the source bearer supports data replication type transmission and the source bearer is a offload bearer, no data retransmission operation is performed.
  • the source bearer supports data replication type transmission and the target bearer is a offload bearer, no data retransmission operation is performed.
  • the source bearer supports the data replication type transmission and there is at least one RLC entity that has been created and not re-established in the process of changing from the source bearer type to the target bearer type, no data is performed. Resend the operation.
  • the not performing the data retransmission operation means that the data retransmission operation in the PDCP entity data recovery operation is not performed.
  • the not performing the data retransmission operation means: not performing the data retransmission operation by the RLC entity that has been created and not re-established, and does not pass the newly created RLC entity and/or the re-established RLC entity. Perform a data retransmission operation.
  • the data retransmission operation is performed: the data retransmission operation is not performed by the RLC entity that has been created but not re-established, but The data retransmission operation is performed by the newly created RLC entity and/or the re-established RLC entity.
  • the device further includes:
  • a retransmission unit (not shown) for performing a data retransmission operation by the newly created RLC entity and/or the re-established RLC entity if the PDCP entity performs a data recovery operation.
  • the data retransmission operation refers to: resending the PDCP entity to the released RLC entity and/or the re-established RLC entity before performing the data recovery operation, and receiving no data for successfully receiving the acknowledgement message.
  • the data that 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 the data that successfully received the acknowledgement message is not received includes:
  • the re-transmitted PDCP entity has been sent to the released RLC entity and/or the re-established RLC entity before the data recovery operation, and the PDCP entity is not sent to the created and non-reestablished RLC entity before the data recovery operation, and is not received.
  • the data that successfully received the confirmation message is not sent to the released RLC entity and/or the re-established RLC entity before the data recovery operation, and is not received.
  • the data that 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 the data that successfully received the acknowledgement message is not received includes:
  • the retransmitted PDCP entity has been sent to the released RLC entity and/or the re-established RLC entity before the data recovery operation, and the success is not received. Received data for the confirmation message.
  • the data that 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 the data that successfully received the acknowledgement message is not received includes:
  • the PDCP entity is resent to the released RLC entity and/or the re-established RLC entity before the data recovery operation, and the data of the successful receipt of the acknowledgement message is not received.
  • the retransmission unit passes the newly created RLC.
  • the entity and/or the re-established RLC entity performs a data retransmission operation.
  • the retransmission unit passes the newly created RLC.
  • the entity and/or the re-established RLC entity and/or the RLC entity that has been created and not re-established performs a data retransmission operation.
  • data retransmission is performed by the newly created RLC entity and/or the reestablished RLC entity. operating.
  • data retransmission is performed by the newly created RLC entity and/or the reestablished RLC entity. operating.
  • the source bearer supports data replication type transmission and the target bearer supports data replication type transmission and in the process of changing from the source bearer type to the target bearer type, at least one has been created and not re-established
  • the RLC entity performs data retransmission operations through the newly created RLC entity and/or the re-established RLC entity.
  • the source bearer supports data replication type transmission and the target bearer does not support data replication type transmission and in the process of changing from the source bearer type to the target bearer type, at least one has been created and not re-established
  • the established RLC entity performs data retransmission operations through the newly created RLC entity and/or the re-established RLC entity.
  • the target bearer supports data replication type transmission, that is, the target bearer is configured with PDCP replication transmission.
  • the target bearer supports data replication type transmission, which means that the target bearer configuration and activates PDCP replication transmission.
  • the source bearer supports data replication type transmission, that is, the source bearer is configured with a PDCP replication transmission.
  • the source bearer supports data replication type transmission, that is, the source bearer configuration and the PDCP copy transmission is activated.
  • each unit in the device of the change-bearing type shown in FIG. 9 can be understood by referring to the related description of the foregoing method for changing the bearer type.
  • the functions of the units in the device of the change-bearing type shown in FIG. 9 can be realized by a program running on the processor, or can be realized by a specific logic circuit.
  • the apparatus for changing the bearer type described above in 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 function module and sold or used as a stand-alone product.
  • the technical solution of the embodiments of the present invention may be embodied in the form of a software product in essence or in the form of a software product stored in a storage medium, including a plurality of instructions.
  • a computer device (which may be a personal computer, server, or network device, etc.) is caused to perform all or part of the methods described in various embodiments of the present invention.
  • the foregoing storage medium includes various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read only memory (ROM), a magnetic disk, or an optical disk.
  • program codes such as a USB flash drive, a mobile hard disk, a read only memory (ROM), a magnetic disk, or an optical disk.
  • the embodiment of the present invention further provides a computer storage medium, wherein the computer executable instructions are stored, and when the computer executable instructions are executed by the processor, the method for changing the bearer type of the embodiment of the present invention is implemented.
  • the terminal 100 may include one or more (only one shown) processor 12 (the processor 12 may include but is not limited to micro processing).
  • a processing device such as a Micro Controller Unit (MCU) or a Programmable Gate Array (FPGA), a memory 14 for storing data, and a transmission device 16 for communication functions.
  • MCU Micro Controller Unit
  • FPGA Programmable Gate Array
  • FIG. 10 is merely illustrative and does not limit the structure of the above electronic device.
  • the terminal 100 may further include more or less components than those shown in FIG. 10, or have a configuration different from that shown in FIG.
  • the memory 14 can be used to store software programs and modules of the application software, such as program instructions/modules corresponding to the method of changing the bearer type in the embodiment of the present invention, and the processor 12 executes by executing the software programs and modules stored in the memory 14 Various functional applications and data processing, that is, the above methods are implemented.
  • 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.
  • memory 14 may further include memory remotely located relative to processor 12, which may be connected to terminal 100 over a network. Examples of such networks include, but are not limited to, the Internet, intranets, local area networks, mobile communication networks, and combinations thereof.
  • Transmission device 16 is for receiving or transmitting data via a network.
  • the above specific network example may include a wireless network provided by a communication provider of the terminal 100.
  • the transmission device 16 includes a Network Interface Controller (NIC) that can be connected to other network devices through a base station to communicate with the Internet.
  • the transmission device 16 can be a radio frequency (RF) module for communicating with the Internet wirelessly.
  • NIC Network Interface Controller
  • RF radio frequency
  • the disclosed method and smart device may be implemented in other manners.
  • the device embodiments described above are merely illustrative.
  • the division of the unit is only a logical function division.
  • there may be another division manner such as: multiple units or components may be combined, or Can be integrated into another system, or some features can be ignored or not executed.
  • the coupling, or direct coupling, or communication connection of the components shown or discussed may be indirect coupling or communication connection through some interfaces, devices or units, and may be electrical, mechanical or other forms. of.
  • the units described above as separate components may or may not be physically separated, and the components displayed as the unit may or may not be physical units, that is, may be located in one place or 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.
  • each functional unit in each embodiment of the present invention may be integrated into one second processing unit, or each unit may be separately used as one unit, or two or more units may be integrated into one unit;
  • the above integrated unit can be implemented in the form of hardware or in the form of hardware plus software functional units.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本发明公开了一种改变承载类型的方法及装置、计算机存储介质，包括：终端接收到控制信令，所述控制信令携有第一指示信息，所述第一指示信息用于指示所述终端从源承载类型改变到目标承载类型；所述终端基于所述源承载类型的传输特征以及所述目标承载类型的传输特征，释放所述源承载类型对应的至少一个RLC实体，并创建所述目标承载类型对应的至少一个RLC实体。

Description

一种改变承载类型的方法及装置、计算机存储介质 技术领域
本发明涉及移动通信领域，尤其涉及一种改变承载类型的方法及装置、计算机存储介质。
背景技术
在无线通信***中，由于单个基站的带宽资源和覆盖范围有限，因此需要不同类型或相同类型的基站协同组网，从而集中多个小区或者基站的无线资源来为用户提供服务，更容易满足用户的容量需求和覆盖需求，这种方式通常称之为多连接。双连接(DC，Dual Connectivity)就是一种常用的多连接方式。
在DC场景下，用户可以同时保持与两个基站的连接，在这种场景下，用户可以单独接收一个基站的数据，也可以同时接收两个基站的数据。根据基站为用户提供服务方式的不同，用户的承载可以分为不同的类型，例如：主小区群承载(MCG bearer)、辅小区群承载(SCG bearer)、分流承载(Split bearer)。对于某个用户而言，其所具有的承载类型可以从一个承载类型改变到另一个承载类型，也即某个用户发生了承载类型的改变。
对于某个用户的承载而言，其承载可以支持数据复制型传输，对应的分组数据汇聚协议(PDCP，Packet Data Convergence Protocol)层具有复制数据功能，通过PDCP层使复制的两份数据分别传输到两个无线链路控制协议(RLC，Radio Link Control)实体，而后在不同的物理层聚合载波上进行传输，这种方案也可以称为载波聚合(CA，Carrier Aggregation)复制(duplication)。
目前研究的承载类型改变并没有考虑到CA dulication的情况，如何结合CA dulication来实现承载类型的改变是有待解决的问题。
发明内容
为解决上述技术问题，本发明实施例提供了一种改变承载类型的方法及装置、计算机存储介质。
本发明实施例提供的改变承载类型的方法，包括：
终端接收到控制信令，所述控制信令携有第一指示信息，所述第一指示信息用于指示所述终端从源承载类型改变到目标承载类型；
所述终端基于所述源承载类型的传输特征以及所述目标承载类型的传输特征，释放所述源承载类型对应的至少一个RLC实体，和/或创建所述目标承载类型对应的至少一个RLC实体。
本发明实施例中，所述控制信令还携有第二指示信息，所述第二指示信息用于指示所述目标承载类型是否支持数据复制型传输。
本发明实施例中，所述源承载类型支持数据复制型传输，所述目标承载类型不支持数据复制型传输；或者，
所述源承载类型不支持数据复制型传输，所述目标承载类型支持数据复制型传输；或者，
所述源承载类型支持数据复制型传输，所述目标承载类型支持数据复制型传输；或者，
所述源承载类型不支持数据复制型传输，所述目标承载类型不支持数据复制型传输。
本发明实施例中，所述源承载类型为非分流负载(Non-Split bearer)；
所述终端基于所述源承载类型的传输特征以及所述目标承载类型的传输特征，释放所述源承载类型对应的至少一个RLC实体，包括：
如果所述源承载类型支持数据复制型传输，则判断所述目标承载类型是否为分流负载(Split bearer)；
如果所述目标承载类型是所述Split bearer，则从所述源承载类型对应的两个RLC实体中释放一个RLC实体；
如果所述目标承载类型不是所述Split bearer，则从所述源承载类型对应的两个RLC实体中释放 两个RLC实体。
本发明实施例中，所述目标承载类型能够支持数据复制型传输或者不支持数据复制型传输。
本发明实施例中，所述目标承载类型为Non-Split bearer；
所述终端基于所述源承载类型的传输特征以及所述目标承载类型的传输特征，创建所述目标承载类型对应的至少一个RLC实体，包括：
如果所述目标承载类型支持数据复制型传输，则判断所述源承载类型是否为Split bearer；
如果所述源承载类型是所述Split bearer，则创建所述目标承载类型对应的一个RLC实体；
如果所述源承载类型不是所述Split bearer，则创建所述目标承载类型对应的两个RLC实体。
本发明实施例中，所述源承载类型能够支持数据复制型传输或者不支持数据复制型传输。
本发明实施例中，在从所述源承载类型改变到所述目标承载类型的过程中，
如果源承载支持数据复制型传输，则不进行数据重发操作。
本发明实施例中，所述源承载支持数据复制型传输，是指：所述源承载配置了分组数据汇聚协议PDCP复制传输。
本发明实施例中，所述源承载支持数据复制型传输，是指：所述源承载配置并激活了PDCP复制传输。
本发明实施例中，如果源承载支持数据复制型传输且所述源承载为分流承载，则不进行数据重发操作。
本发明实施例中，如果源承载支持数据复制型传输且目标承载为分流承载，则不进行数据重发操作。
本发明实施例中，如果源承载支持数据复制型传输且在从所述源承载类型改变到所述目标承载类型的过程中，存在至少一个已创建且未重新建立的RLC实体，则不进行数据重发操作。
本发明实施例中，所述不进行数据重发操作，是指：不进行PDCP实体数据恢复操作中的数据重发操作。
本发明实施例中，如果目标承载未配置或未激活PDCP复制传输，则不进行数据重发操作。
本发明实施例中，所述不进行数据重发操作是指：不通过已创建且未重新建立的RLC实体进行数据重发操作，且不通过新创建的RLC实体和/或重新建立的RLC实体进行数据重发操作。
本发明实施例中，如果所述目标承载配置并激活了PDCP复制传输，则所述不进行数据重发操作是指：不通过已创建且未重新建立的RLC实体进行数据重发操作，但能够通过新创建的RLC实体和/或重新建立的RLC实体进行数据重发操作。
本发明实施例中，在从所述源承载类型改变到所述目标承载类型的过程中，
如果PDCP实体进行数据恢复操作，则通过新创建的RLC实体和/或重新建立的RLC实体进行数据重发操作。
本发明实施例中，所述数据重发操作，是指：重新发送PDCP实体进行数据恢复操作前已经发送给释放的RLC实体和/或重新建立的RLC实体，且没有收到成功收到确认消息的数据。
本发明实施例中，所述重新发送PDCP实体进行数据恢复操作前已经发送给释放的RLC实体和/或重新建立的RLC实体，且没有收到成功收到确认消息的数据，包括：
重新发送PDCP实体进行数据恢复操作前已经发送给释放的RLC实体和/或重新建立的RLC实体，且PDCP实体进行数据恢复操作前未发送给已创建且未重新建立的RLC实体，且没有收到成功收到确认消息的数据。
本发明实施例中，所述重新发送PDCP实体进行数据恢复操作前已经发送给释放的RLC实体和/或重新建立的RLC实体，且没有收到成功收到确认消息的数据，包括：
在源承载未配置和/或配置了但未激活数据复制传输的情况下，重新发送PDCP实体进行数据恢复操作前已经发送给释放的RLC实体和/或重新建立的RLC实体，且没有收到成功收到确认消息的数据。
本发明实施例中，所述重新发送PDCP实体进行数据恢复操作前已经发送给释放的RLC实体和/或重新建立的RLC实体，且没有收到成功收到确认消息的数据，包括：
在RLC实体均重新建立或释放的情况下，重新发送PDCP实体进行数据恢复操作前已经发送给释放的RLC实体和/或重新建立的RLC实体，且没有收到成功收到确认消息的数据。
本发明实施例中，如果所述数据重发操作重发的是PDCP实体进行数据恢复操作前已经发送给已创建且未重新建立的RLC实体的数据，则通过新创建的RLC实体和/或重新建立的RLC实体进行数据重发操作。
本发明实施例中，如果所述数据重发操作重发的是PDCP实体进行数据恢复操作前未发送给已创建且未重新建立的RLC实体的数据，则通过新创建的RLC实体和/或重新建立的RLC实体和/或已创建且未重新建立的RLC实体进行数据重发操作。
本发明实施例中，如果源承载支持数据复制型传输且目标承载支持数据复制型传输且所述源承载为分流承载，则通过新创建的RLC实体和/或重新建立的RLC实体进行数据重发操作。
本发明实施例中，如果源承载支持数据复制型传输且目标承载支持数据复制型传输且所述目标承载为分流承载，则通过新创建的RLC实体和/或重新建立的RLC实体进行数据重发操作。
本发明实施例中，如果源承载支持数据复制型传输且目标承载支持数据复制型传输且在从所述源承载类型改变到所述目标承载类型的过程中，存在至少一个已创建且未重新建立的RLC实体，则通过新创建的RLC实体和/或重新建立的RLC实体进行数据重发操作。
本发明实施例中，如果源承载支持数据复制型传输且目标承载不支持数据复制型传输且在从所述源承载类型改变到所述目标承载类型的过程中，存在至少一个已创建且未重新建立的RLC实体，则通过新创建的RLC实体和/或重新建立的RLC实体进行数据重发操作。
本发明实施例中，所述目标承载支持数据复制型传输，是指：所述目标承载配置了PDCP复制传输。
本发明实施例中，所述目标承载支持数据复制型传输，是指：所述目标承载配置并激活了PDCP复制传输。
本发明实施例中，所述源承载支持数据复制型传输，是指：所述源承载配置了PDCP复制传输。
本发明实施例中，所述源承载支持数据复制型传输，是指：所述源承载配置并激活了PDCP复制传输。
本发明实施例提供的改变承载类型的装置包括：
接收单元，配置为接收到控制信令，所述控制信令携有第一指示信息，所述第一指示信息用于指示所述终端从源承载类型改变到目标承载类型；
承载类型改变单元，配置为基于所述源承载类型的传输特征以及所述目标承载类型的传输特征，释放所述源承载类型对应的至少一个RLC实体，和/或创建所述目标承载类型对应的至少一个RLC实体。
本发明实施例中，所述控制信令还携有第二指示信息，所述第二指示信息用于指示所述目标承载类型是否支持数据复制型传输。
本发明实施例中，所述源承载类型支持数据复制型传输，所述目标承载类型不支持数据复制型传输；或者，
所述源承载类型不支持数据复制型传输，所述目标承载类型支持数据复制型传输；或者，
所述源承载类型支持数据复制型传输，所述目标承载类型支持数据复制型传输；或者，
所述源承载类型不支持数据复制型传输，所述目标承载类型不支持数据复制型传输。
本发明实施例中，所述源承载类型为Non-Split bearer；
所述承载类型改变单元包括：
第一判断子单元，配置为如果所述源承载类型支持数据复制型传输，则判断所述目标承载类型是否为Split bearer；
释放子单元，配置为如果所述目标承载类型是所述Split bearer，则从所述源承载类型对应的两个RLC实体中释放一个RLC实体；如果所述目标承载类型不是所述Split bearer，则从所述源承载类型对应的两个RLC实体中释放两个RLC实体。
本发明实施例中，所述目标承载类型能够支持数据复制型传输或者不支持数据复制型传输。
本发明实施例中，所述目标承载类型为Non-Split bearer；
所述承载类型改变单元包括：
第二判断子单元，配置为如果所述目标承载类型支持数据复制型传输，则判断所述源承载类型是否为Split bearer；
创建子单元，配置为如果所述源承载类型是所述Split bearer，则创建所述目标承载类型对应的一个RLC实体；如果所述源承载类型不是所述Split bearer，则创建所述目标承载类型对应的两个RLC实体。
本发明实施例中，所述源承载类型能够支持数据复制型传输或者不支持数据复制型传输。
本发明实施例中，所述装置还包括：
重传单元，用于如果源承载支持数据复制型传输，则不进行数据重发操作。
本发明实施例中，所述源承载支持数据复制型传输，是指：所述源承载配置了分组数据汇聚协议PDCP复制传输。
本发明实施例中，所述源承载支持数据复制型传输，是指：所述源承载配置并激活了PDCP复制传输。
本发明实施例中，如果源承载支持数据复制型传输且所述源承载为分流承载，则不进行数据重发操作。
本发明实施例中，如果源承载支持数据复制型传输且目标承载为分流承载，则不进行数据重发操作。
本发明实施例中，如果源承载支持数据复制型传输且在从所述源承载类型改变到所述目标承载类型的过程中，存在至少一个已创建且未重新建立的RLC实体，则不进行数据重发操作。
本发明实施例中，所述不进行数据重发操作，是指：不进行PDCP实体数据恢复操作中的数据重发操作。
本发明实施例中，如果目标承载未配置或未激活PDCP复制传输，则不进行数据重发操作。
本发明实施例中，所述不进行数据重发操作是指：不通过已创建且未重新建立的RLC实体进行数据重发操作，且不通过新创建的RLC实体和/或重新建立的RLC实体进行数据重发操作。
本发明实施例中，如果所述目标承载配置并激活了PDCP复制传输，则所述不进行数据重发操作是指：不通过已创建且未重新建立的RLC实体进行数据重发操作，但能够通过新创建的RLC实体和/或重新建立的RLC实体进行数据重发操作。
本发明实施例中，所述装置还包括：
重传单元，用于如果PDCP实体进行数据恢复操作，则通过新创建的RLC实体和/或重新建立的RLC实体进行数据重发操作。
本发明实施例中，所述数据重发操作，是指：重新发送PDCP实体进行数据恢复操作前已经发送给释放的RLC实体和/或重新建立的RLC实体，且没有收到成功收到确认消息的数据。
本发明实施例中，所述重新发送PDCP实体进行数据恢复操作前已经发送给释放的RLC实体和/或重新建立的RLC实体，且没有收到成功收到确认消息的数据，包括：
重新发送PDCP实体进行数据恢复操作前已经发送给释放的RLC实体和/或重新建立的RLC实体，且PDCP实体进行数据恢复操作前未发送给已创建且未重新建立的RLC实体，且没有收到成功收到确认消息的数据。
本发明实施例中，所述重新发送PDCP实体进行数据恢复操作前已经发送给释放的RLC实体和/或重新建立的RLC实体，且没有收到成功收到确认消息的数据，包括：
在源承载未配置和/或配置了但未激活数据复制传输的情况下，重新发送PDCP实体进行数据恢复操作前已经发送给释放的RLC实体和/或重新建立的RLC实体，且没有收到成功收到确认消息的数据。
本发明实施例中，所述重新发送PDCP实体进行数据恢复操作前已经发送给释放的RLC实体和/或重新建立的RLC实体，且没有收到成功收到确认消息的数据，包括：
在RLC实体均重新建立或释放的情况下，重新发送PDCP实体进行数据恢复操作前已经发送给释放的RLC实体和/或重新建立的RLC实体，且没有收到成功收到确认消息的数据。
本发明实施例中，如果所述数据重发操作重发的是PDCP实体进行数据恢复操作前已经发送给已创建且未重新建立的RLC实体的数据，则所述重传单元通过新创建的RLC实体和/或重新建立的RLC实体进行数据重发操作。
本发明实施例中，如果所述数据重发操作重发的是PDCP实体进行数据恢复操作前未发送给已创建且未重新建立的RLC实体的数据，则所述重传单元通过新创建的RLC实体和/或重新建立的RLC实体和/或已创建且未重新建立的RLC实体进行数据重发操作。
本发明实施例中，如果源承载支持数据复制型传输且目标承载支持数据复制型传输且所述源承载为分流承载，则通过新创建的RLC实体和/或重新建立的RLC实体进行数据重发操作。
本发明实施例中，如果源承载支持数据复制型传输且目标承载支持数据复制型传输且所述目标承载为分流承载，则通过新创建的RLC实体和/或重新建立的RLC实体进行数据重发操作。
本发明实施例中，如果源承载支持数据复制型传输且目标承载支持数据复制型传输且在从所述源承载类型改变到所述目标承载类型的过程中，存在至少一个已创建且未重新建立的RLC实体，则通过新创建的RLC实体和/或重新建立的RLC实体进行数据重发操作。
本发明实施例中，如果源承载支持数据复制型传输且目标承载不支持数据复制型传输且在从所 述源承载类型改变到所述目标承载类型的过程中，存在至少一个已创建且未重新建立的RLC实体，则通过新创建的RLC实体和/或重新建立的RLC实体进行数据重发操作。
本发明实施例中，所述目标承载支持数据复制型传输，是指：所述目标承载配置了PDCP复制传输。
本发明实施例中，所述目标承载支持数据复制型传输，是指：所述目标承载配置并激活了PDCP复制传输。
本发明实施例中，所述源承载支持数据复制型传输，是指：所述源承载配置了PDCP复制传输。
本发明实施例中，所述源承载支持数据复制型传输，是指：所述源承载配置并激活了PDCP复制传输。
本发明实施例提供的计算机存储介质，其上存储有计算机可执行指令，该计算机可执行指令被处理器执行时实现上述的改变承载类型的方法。
本发明实施例的技术方案中，终端接收到控制信令，所述控制信令携有第一指示信息，所述第一指示信息用于指示所述终端从源承载类型改变到目标承载类型；所述终端基于所述源承载类型的传输特征以及所述目标承载类型的传输特征，释放所述源承载类型对应的至少一个实体，和/或创建所述目标承载类型对应的至少一个RLC实体。采用本发明实施例的技术方案，能够在双连接架构中结合CA dulication的情况实现承载类型的改变，完善了双连接的应用场景。
附图说明
此处所说明的附图用来提供对本发明的进一步理解，构成本申请的一部分，本发明的示意性实施例及其说明用于解释本发明，并不构成对本发明的不当限定。在附图中：
图1为DC场景下的协议结构示意图；
图2为CA duplication场景下的协议结构示意图；
图3为本发明实施例的改变承载类型的方法的流程示意图；
图4为本发明实施例的承载类型改变的协议结构示意图一；
图5为本发明实施例的承载类型改变的协议结构示意图二；
图6为本发明实施例的承载类型改变的协议结构示意图三；
图7为本发明实施例的承载类型改变的协议结构示意图四；
图8为本发明实施例的改变承载类型的装置的结构组成示意图一；
图9为本发明实施例的改变承载类型的装置的结构组成示意图二；
图10为本发明实施例的终端的结构组成示意图。
具体实施方式
为了能够更加详尽地了解本发明实施例的特点与技术内容，下面结合附图对本发明实施例的实现进行详细阐述，所附附图仅供参考说明之用，并非用来限定本发明实施例。
图1为DC场景下的协议结构示意图，如图1所示，MN代表网络侧的主节点(Master Node)，SN代表网络侧的辅节点(Slave Node)。在一实施方式，MN为长期演进(LTE，Long Term Evolution)***，SN为NR(New Radio)***；在另一实施方式中，MN为NR***，SN为LTE***；在又一实施方式中，MN为NR***，SN也为NR***。值得注意的是，MN和SN代表了两个不同的网络节点，这两个不同的网络节点的网络类型可以不同，也可以相同。
在DC架构中，用户可以同时保持与MN和SN的连接，其中，MN与SN之间通过X2接口实现交互。DC场景下的协议结构如图1所示，在MN和SN侧，都具有PDCP层、RLC层、媒体接入控制(MAC，Media Access Control)层。对于某个用户而言，其可以保持任意一种承载类型，以下对用户的承载类型进行具体地解释说明：
1)对于数据承载而言，承载类型包括：
MCG bearer：承载的无线协议仅位于MCG；
MCG split bearer：承载的无线协议在MN进行分割，同时位于MCG和SCG；
SCG bearer：承载的无线协议仅位于SCG；
SCG split bearer：承载的无线协议在SN进行分割，同时位于SCG和MCG。
2)对于信令承载而言，承载类型包括：
MCG SRB：MN和UE之间的信令承载(SRB，Signalling Radio Bearers)；
MCG split SRB：MN和UE之间的SRB，其中，UE支持通过SN复制无线资源控制(RRC，Radio Resource Control)协议数据单元(PDU，Protocol Data Unit)；
SCG SRB：SN和UE之间的SRB。
下面结合数据承载的各个承载类型对协议栈的实现过程进行详细描述。
1)MCG bearer：
MCG bearer的传输通道如图1所示，MCG bearer首先经过MN PDCP层，MN PDCP层对MCG bearer处理后传输至MN RLC层，MN RLC层对MCG bearer处理后传输至MN MAC层，MN MAC层对MCG bearer处理后将MCG bearer发送给用户。
2)MCG split bearer：
MCG split bearer的传输通道如图1所示，MCG split bearer首先经过MN PDCP层，MN PDCP层对MCG split bearer进行处理的过程中会对MCG split bearer进行分割，分割成两部分bearer，其中：第一部分bearer传输至MN RLC层，MN RLC层对第一部分bearer处理后传输至MN MAC层，MN MAC层对第一部分bearer处理后将第一部分bearer发送给用户；第二部分bearer传输至SN中的SN RLC层，SN RLC层对第二部分bearer处理后传输至SN MAC层，SN MAC层对第二部分bearer处理后将第二部分bearer发送给用户。
3)SCG bearer：
SCG bearer的传输通道如图1所示，SCG bearer首先经过SN PDCP层，SN PDCP层对SCG bearer处理后传输至SN RLC层，SN RLC层对SCG bearer处理后传输至SN MAC层，SN MAC层对SCG bearer处理后将SCG bearer发送给用户。
4)SCG split bearer：
SCG split bearer的传输通道如图1所示，SCG split bearer首先经过SN PDCP层，SN PDCP层对SCG split bearer进行处理的过程中会对SCG split bearer进行分割，分割成两部分bearer，其中：第一部分bearer传输至SN RLC层，SN RLC层对第一部分bearer处理后传输至SN MAC层，SN MAC层对第一部分bearer处理后将第一部分bearer发送给用户；第二部分bearer传输至MN中的MN RLC层，MN RLC层对第二部分bearer处理后传输至MN MAC层，MN MAC层对第二部分bearer处理后将第二部分bearer发送给用户。
本领域技术人员应当理解，图1所示的协议结构不仅适用在网络侧，也适用在用户侧，也即终端侧，终端的协议结构与网络的协议结构是相对应的。
本发明实施例中，用户的承载类型可以相互转变，具体如下：
1)对于数据承载而言，具有如下类型转变：
MCG bearer与MCG split bearer之间的相互转变；
MCG bearer与SCG bearer之间的相互转变；
MCG bearer与SCG split bearer之间的相互转变；
SCG bearer与SCG split bearer之间的相互转变；
MCG bearer向MCG bearer的转变；
SCG bearer向SCG bearer的转变；
MCG split bearer向MCG split bearer的转变；
SCG split bearer向SCG split bearer的转变。
2)对于信令承载而言，具有如下类型转变：
MCG SRB与MCG split SRB之间的相互转变。
图2为CA duplication场景下的协议结构示意图，在CA duplication场景下，PDCP层具有复制数据功能，如图2所示，PDCP服务数据单元(SDU，Service Data Uint)传输至PDCP层，由于PDCP层配置有复制数据功能，因而PDCP层可以将处理得到的PDCP PDU复制一份，得到Duplicated PDCP PDU，之后，将PDCP PDU传输至RLC实体(Entity)a，将Duplicated PDCP PDU传输至RLC Entity b，这里，RLC Entity a和RLC Entity b分别对应两个不同的逻辑信道，通过两个RLC Entity分别对两份数据进行处理后再通过MAC层实现将两份数据在不同的物理层聚合载波上传输(如图2中的Physical Carrier1和Physical Carrier2)，从而达到频率分集增益以提高数据传输可靠性。
上述图1的方案中，对于MCG bearer和SCG bearer而言，一个PDCP实体下对应一个RLC实体，并没有考虑到CA duplication的场景，也即没有考虑到一个PDCP实体下对应两个RLC实体的情况，本发明实施例的技术方案能够结合CA duplication实现承载类型的改变。
本发明实施例的以下技术方案均以承载为数据承载为例来解释承载类型的改变，信令承载的承载类型的改变也同样适应于本发明实施例的技术方案，其中涉及到的承载类型包括：MCG bearer、MCG split bearer、SCG bearer、SCG split bearer，其中，MCG bearer和SCG bearer均对应网络侧的一个网络节点，MCG bearer对应MN，SCG bearer对应SN；MCG split bearer和SCG split bearer统称为Split bearer，Split bearer对应网络侧的两个网络节点，也即MN和SN。
图3为本发明实施例的改变承载类型的方法的流程示意图，如图3所示，所述改变承载类型的方法包括以下步骤：
步骤301：终端接收到控制信令，所述控制信令携有第一指示信息，所述第一指示信息用于指示所述终端从源承载类型改变到目标承载类型。
本发明实施例中，承载类型的改变可以但不局限于通过以下方式触发：
方式一：终端在移动的过程中，与MN和SN的距离不断发生变化。终端距离MN较近时，对应的承载类型为MCG bearer；终端位于MN和SN之间时，对应的承载类型为Split bearer；终端距离SN较近时，对应的承载类型为SCG bearer。进一步，终端从距离MN较近移动到MN和SN之间时，对应的承载类型由MCG bearer切换到Split bearer(具体为MCG split bearer)；终端从MN和SN之间移动到距离SN较近时，对应的承载类型由Split bearer切换到SCG bearer。反之，终端从距离SN较近移动到MN和SN之间时，对应的承载类型由SCG bearer切换到Split bearer(具体为SCG split bearer)；终端从MN和SN之间移动到距离MN较近时，对应的承载类型由Split bearer切换到MCG bearer。
方式二：MN和SN之间为了实现某种网络策略(如负载均衡策略)，调整终端的承载类型，例如：初始时终端的承载类型为MCG bearer，当MN的负载逐渐增大时，可以将该终端的承载类型由MCG bearer变换为Split bearer，从而通过MN和SN共同为终端提供服务，实现负载的均衡。
网络侧确定出终端需要改变承载类型时，向终端发送控制信令，所述控制信令携有第一指示信息，所述第一指示信息用于指示所述终端从源承载类型改变到目标承载类型。终端接收到控制信令后，进行承载类型的改变，即：从源承载类型改变到目标承载类型。
步骤302：所述终端基于所述源承载类型的传输特征以及所述目标承载类型的传输特征，释放所述源承载类型对应的至少一个RLC实体，和/或创建所述目标承载类型对应的至少一个RLC实体。
本发明实施例中，所述控制信令还携有第二指示信息，所述第二指示信息用于指示所述目标承载类型是否支持数据复制型传输(也即CA duplication)。
本发明实施例的DC架构结合了CA duplication的情况，因此，源承载类型和目标承载类型具有以下三种传输特征组合：
1)所述源承载类型支持数据复制型传输，所述目标承载类型不支持数据复制型传输；
2)所述源承载类型不支持数据复制型传输，所述目标承载类型支持数据复制型传输；
3)所述源承载类型支持数据复制型传输，所述目标承载类型支持数据复制型传输。
此外，源承载类型和目标承载类型还具有以下传输特征：
4)所述源承载类型不支持数据复制型传输，所述目标承载类型不支持数据复制型传输。
这里，支持数据复制型传输的承载类型可以是：MCG bearer、SCG bearer、Split bearer。不支持数据复制型传输的承载类型可以是：MCG bearer、SCG bearer、Split bearer。
对于源承载类型而言：所述源承载类型为Non-Split bearer；所述终端基于所述源承载类型的传输特征以及所述目标承载类型的传输特征，释放所述源承载类型对应的至少一个RLC实体，包括：
如果所述源承载类型支持数据复制型传输，则判断所述目标承载类型是否为Split bearer；
如果所述目标承载类型是所述Split bearer，则从所述源承载类型对应的两个RLC实体中释放一个RLC实体；
如果所述目标承载类型不是所述Split bearer，则从所述源承载类型对应的两个RLC实体中释放两个RLC实体。
这里，所述目标承载类型是所述Split bearer或不是所述Split bearer时，所述目标承载类型能够支持数据复制型传输或者不支持数据复制型传输。
对于目标承载类型而言：所述目标承载类型为Non-Split bearer；所述终端基于所述源承载类型的传输特征以及所述目标承载类型的传输特征，创建所述目标承载类型对应的至少一个RLC实体，包括：
如果所述目标承载类型支持数据复制型传输，则判断所述源承载类型是否为Split bearer；
如果所述源承载类型是所述Split bearer，则创建所述目标承载类型对应的一个RLC实体；
如果所述源承载类型不是所述Split bearer，则创建所述目标承载类型对应的两个RLC实体。
这里，所述源承载类型是所述Split bearer或不是所述Split bearer时，所述源承载类型能够支持数据复制型传输或者不支持数据复制型传输。
本发明实施例中，PDCP实体在承载类型改变的过程中可能不需要进行操作，或者需要进行数据恢复操作，或者需要进行重建操作。
在一实施方式中，在从所述源承载类型改变到所述目标承载类型的过程中，
如果源承载支持数据复制型传输，则不进行数据重发操作。
其中，所述源承载类型支持数据复制型传输，是指1)所述源承载类型配置了分组数据汇聚协议PDCP复制传输。或者，2)所述源承载类型配置并激活了PDCP复制传输。
上述方案中，所述不进行数据重发操作，具有如下几种情况：
情况一：如果源承载支持数据复制型传输且所述源承载为分流承载，则不进行数据重发操作。
情况二：如果源承载支持数据复制型传输且目标承载为分流承载，则不进行数据重发操作。
情况三：如果源承载支持数据复制型传输且在从所述源承载类型改变到所述目标承载类型的过程中，存在至少一个已创建且未重新建立的RLC实体，则不进行数据重发操作。
上述方案中，所述不进行数据重发操作，是指：不进行PDCP实体数据恢复操作中的数据重发操作。
这里，不进行PDCP实体数据恢复操作中的数据重发操作，具有如下几种情况：
情况一：网络不下发数据恢复操作指示信息，终端因此不会进行PDCP实体数据恢复操作中的数据重发操作。
情况二：网络下发数据恢复操作指示信息，但是终端不执行PDCP实体数据恢复操作。
情况三：网络下发数据恢复操作指示信息，但是终端不执行PDCP实体数据恢复操作中的数据重发操作。
在一实施方式中，如果目标承载未配置或未激活PDCP复制传输，则不进行数据重发操作。
本发明实施例中，所述不进行数据重发操作是指：不通过已创建且未重新建立的RLC实体进行数据重发操作，且不通过新创建的RLC实体和/或重新建立的RLC实体进行数据重发操作。
在一实施方式中，如果所述目标承载配置并激活了PDCP复制传输，则所述不进行数据重发操作是指：不通过已创建且未重新建立的RLC实体进行数据重发操作，但能够通过新创建的RLC实体和/或重新建立的RLC实体进行数据重发操作。
在一实施方式中，在从所述源承载类型改变到所述目标承载类型的过程中，
如果PDCP实体进行数据恢复操作，则通过新创建的RLC实体和/或重新建立的RLC实体进行数据重发操作。
其中，所述数据重发操作，是指：重新发送PDCP实体进行数据恢复操作前已经发送给释放的RLC实体和/或重新建立的RLC实体，且没有收到成功收到确认消息的数据。
进一步，所述数据重发操作，是指：重新发送PDCP实体进行数据恢复操作前已经发送给释放的RLC实体和/或重新建立的RLC实体，且PDCP实体进行数据恢复操作前未发送给已创建且未重新建立的RLC实体，且没有收到成功收到确认消息的数据。
这里，所述重新发送PDCP实体进行数据恢复操作前已经发送给释放的RLC实体和/或重新建立的RLC实体，且没有收到成功收到确认消息的数据，包括：
1)在源承载未配置和/或配置了但未激活数据复制传输的情况下，重新发送PDCP实体进行数据恢复操作前已经发送给释放的RLC实体和/或重新建立的RLC实体，且没有收到成功收到确认消息的数据。
2)在RLC实体均重新建立或释放的情况下，重新发送PDCP实体进行数据恢复操作前已经发送给释放的RLC实体和/或重新建立的RLC实体，且没有收到成功收到确认消息的数据。
上述方案中，数据恢复操作主要包括两个步骤：1)发送PDCP状态报告；2)重传数据。
上述方案中，新创建的RLC实体是指原来没有这个RLC实体，新创建了一个RLC实体；重新建立的RLC实体是指原来有这个RLC实体，通过重置等方式对该RLC实体进行了更新，RLC实体重新建立意味着RLC实体清空所有的缓存数据(包括还没有成功发送的数据)以及一些其他操作。
在一实施方式中，如果所述数据重发操作重发的是PDCP实体进行数据恢复操作前已经发送给已创建且未重新建立的RLC实体的数据，则通过新创建的RLC实体和/或重新建立的RLC实体进行数据重发操作。
在一实施方式中，如果所述数据重发操作重发的是PDCP实体进行数据恢复操作前未发送给已 创建且未重新建立的RLC实体的数据，则通过新创建的RLC实体和/或重新建立的RLC实体和/或已创建且未重新建立的RLC实体进行数据重发操作。1)例如：如果所述数据重发操作重发的是PDCP实体进行数据恢复操作前未发送给已创建且未重新建立的RLC实体的数据，则通过新创建的RLC实体和重新建立的RLC实体和已创建且未重新建立的RLC实体进行数据重发操作；2)再例如：如果所述数据重发操作重发的是PDCP实体进行数据恢复操作前未发送给已创建且未重新建立的RLC实体的数据，则通过新创建的RLC实体和已创建且未重新建立的RLC实体进行数据重发操作；3)又例如：如果所述数据重发操作重发的是PDCP实体进行数据恢复操作前未发送给已创建且未重新建立的RLC实体的数据，则通过重新建立的RLC实体和已创建且未重新建立的RLC实体进行数据重发操作。
在一实施方式中，如果源承载支持数据复制型传输且目标承载支持数据复制型传输且所述源承载为分流承载，则通过新创建的RLC实体和/或重新建立的RLC实体进行数据重发操作。
在一实施方式中，如果源承载支持数据复制型传输且目标承载支持数据复制型传输且所述目标承载为分流承载，则通过新创建的RLC实体和/或重新建立的RLC实体进行数据重发操作。
在一实施方式中，如果源承载支持数据复制型传输且目标承载支持数据复制型传输且在从所述源承载类型改变到所述目标承载类型的过程中，存在至少一个已创建且未重新建立的RLC实体，则通过新创建的RLC实体和/或重新建立的RLC实体进行数据重发操作。
在一实施方式中，如果源承载支持数据复制型传输且目标承载不支持数据复制型传输且在从所述源承载类型改变到所述目标承载类型的过程中，存在至少一个已创建且未重新建立的RLC实体，则通过新创建的RLC实体和/或重新建立的RLC实体进行数据重发操作。
上述方案中，所述目标承载支持数据复制型传输，是指：1)所述目标承载配置了PDCP复制传输。或者，2)所述目标承载配置并激活了PDCP复制传输。
上述方案中，所述源承载支持数据复制型传输，是指：1)所述源承载配置了PDCP复制传输。或者，2)所述源承载配置并激活了PDCP复制传输。
以下结合具体应用示例对本发明实施例的技术方案做进一步详细描述。
应用示例一
如图4所示，本示例中，源承载类型支持数据复制型传输，也即源承载类型为MCG bearer或SCG bearer(以下说明以源承载类型为MCG bearer为例)，目标承载类型是Split bearer，这种场景下：由于源承载类型支持数据复制型传输，因此，源承载类型的PDCP层对应两个RLC实体(两个RLC实体均对应MN)，分别为RLC Entity a和RLC Entity b；由于目标承载类型是Split bearer，因此，目标承载类型的PDCP层也对应两个RLC实体(一个RLC实体对应MN，另一个RLC实体对应SN)，分别为RLC Entity a和RLC Entity c。可见，在实现承载类型切换时，需要释放源承载类型对应的RLC Entity b，并创建目标承载类型对应的RLC Entity c。
应用示例二
如图5所示，本示例中，源承载类型支持数据复制型传输，也即源承载类型为MCG bearer或SCG bearer(以下说明以源承载类型为MCG bearer为例)，目标承载类型不是Split bearer，也即目标承载类型为SCG bearer或MCG bearer(以下说明以目标承载类型为SCG bearer为例)，这种场景下：由于源承载类型支持数据复制型传输，因此，源承载类型的PDCP层对应两个RLC实体(两个RLC实体均对应MN)，分别为RLC Entity a和RLC Entity b；由于目标承载类型是SCG bearer，因此，目标承载类型的PDCP层可以对应一个RLC实体，也可以对应两个RLC实体，这取决于目标承载类型是否支持数据复制型传输，如果目标承载类型不支持数据复制型传输，则目标承载类型的PDCP层对应一个RLC实体(该RLC实体对应SN)，为RLC Entity c；如果目标承载类型支持数据复制型传输，则目标承载类型的PDCP层对应两个RLC实体(两个RLC实体均对应SN)，分别为RLC Entity c、RLC Entity d。可见，在实现承载类型切换时，需要释放源承载类型对应的RLC Entity a和RLC Entity b，并创建目标承载类型对应的RLC Entity c，或者，RLC Entity c和RLC Entity d。
应用示例三
如图6所示，本示例中，目标承载类型支持数据复制型传输，也即目标承载类型为MCG bearer或SCG bearer(以下说明以目标承载类型为SCG bearer为例)，源承载类型是Split bearer，这种场景下：由于目标承载类型支持数据复制型传输，因此，目标承载类型的PDCP层对应两个RLC实体(两个RLC实体均对应SN)，分别为RLC Entity b和RLC Entity c；由于源承载类型是Split bearer，因此，源承载类型的PDCP层也对应两个RLC实体(一个RLC实体对应MN，另一个RLC实体对应SN)，分别为RLC Entity a和RLC Entity b。可见，在实现承载类型切换时，需要释放源承载类型对 应的RLC Entity a，并创建目标承载类型对应的RLC Entity c。
应用示例四
如图7所示，本示例中，目标承载类型支持数据复制型传输，也即目标承载类型为MCG bearer或SCG bearer(以下说明以目标承载类型为SCG bearer为例)，源承载类型不是Split bearer，也即源承载类型为SCG bearer或MCG bearer(以下说明以源承载类型为MCG bearer为例)，这种场景下：由于目标承载类型支持数据复制型传输，因此，目标承载类型的PDCP层对应两个RLC实体(两个RLC实体均对应SN)，分别为RLC Entity c和RLC Entity d；由于源承载类型是MCG bearer，因此，源承载类型的PDCP层可以对应一个RLC实体，也可以对应两个RLC实体，这取决于源承载类型是否支持数据复制型传输，如果源承载类型不支持数据复制型传输，则源承载类型的PDCP层对应一个RLC实体(该RLC实体对应MN)，为RLC Entity a；如果源承载类型支持数据复制型传输，则源承载类型的PDCP层对应两个RLC实体(两个RLC实体均对应MN)，分别为RLC Entity a、RLC Entity b。可见，在实现承载类型切换时，需要释放源承载类型对应的RLC Entity a，或者，RLC Entity a和RLC Entity b，并创建目标承载类型对应的RLC Entity c和RLC Entity d。
本发明实施例的应用示例不局限于以上几种，任何承载类型的转变，都可以采用本发明实施例的技术方案来实现，也即基于本发明实施例的思想所实现的任何承载类型的转变都属于本发明保护的范围。
图8为本发明实施例的改变承载类型的装置的结构组成示意图一，如图8所示，所述改变承载类型的装置包括：
接收单元801，配置为接收到控制信令，所述控制信令携有第一指示信息，所述第一指示信息用于指示所述终端从源承载类型改变到目标承载类型；
承载类型改变单元802，配置为基于所述源承载类型的传输特征以及所述目标承载类型的传输特征，释放所述源承载类型对应的至少一个RLC实体，和/或创建所述目标承载类型对应的至少一个RLC实体。
本领域技术人员应当理解，图8所示的改变承载类型的装置中的各单元的实现功能可参照前述改变承载类型的方法的相关描述而理解。图8所示的改变承载类型的装置中的各单元的功能可通过运行于处理器上的程序而实现，也可通过具体的逻辑电路而实现。
图9为本发明实施例的改变承载类型的装置的结构组成示意图二，如图9所示，所述改变承载类型的装置包括：
接收单元901，配置为接收到控制信令，所述控制信令携有第一指示信息，所述第一指示信息用于指示所述终端从源承载类型改变到目标承载类型；
承载类型改变单元902，配置为基于所述源承载类型的传输特征以及所述目标承载类型的传输特征，释放所述源承载类型对应的至少一个RLC实体，和/或创建所述目标承载类型对应的至少一个RLC实体。
所述控制信令还携有第二指示信息，所述第二指示信息用于指示所述目标承载类型是否支持数据复制型传输。
本发明实施例中，所述源承载类型支持数据复制型传输，所述目标承载类型不支持数据复制型传输；或者，
所述源承载类型不支持数据复制型传输，所述目标承载类型支持数据复制型传输；或者，
所述源承载类型支持数据复制型传输，所述目标承载类型支持数据复制型传输；或者，
所述源承载类型不支持数据复制型传输，所述目标承载类型不支持数据复制型传输。
本发明实施例中，所述源承载类型为Non-Split bearer；
所述承载类型改变单元902包括：
第一判断子单元9021，配置为如果所述源承载类型支持数据复制型传输，则判断所述目标承载类型是否为Split bearer；
释放子单元9022，配置为如果所述目标承载类型是所述Split bearer，则从所述源承载类型对应的两个RLC实体中释放一个RLC实体；如果所述目标承载类型不是所述Split bearer，则从所述源承载类型对应的两个RLC实体中释放两个RLC实体。
本发明实施例中，所述目标承载类型能够支持数据复制型传输或者不支持数据复制型传输。
本发明实施例中，所述目标承载类型为Non-Split bearer；
所述承载类型改变单元902包括：
第二判断子单元9023，配置为如果所述目标承载类型支持数据复制型传输，则判断所述源 承载类型是否为Split bearer；
创建子单元9024，配置为如果所述源承载类型是所述Split bearer，则创建所述目标承载类型对应的一个RLC实体；如果所述源承载类型不是所述Split bearer，则创建所述目标承载类型对应的两个RLC实体。
本发明实施例中，所述源承载类型能够支持数据复制型传输或者不支持数据复制型传输。
本发明实施例中，所述装置还包括：
重传单元(图中未示出)，用于如果源承载支持数据复制型传输，则不进行数据重发操作。
在一实施方式中，所述源承载支持数据复制型传输，是指：所述源承载配置了分组数据汇聚协议PDCP复制传输。
在一实施方式中，所述源承载支持数据复制型传输，是指：所述源承载配置并激活了PDCP复制传输。
在一实施方式中，如果源承载支持数据复制型传输且所述源承载为分流承载，则不进行数据重发操作。
在一实施方式中，如果源承载支持数据复制型传输且目标承载为分流承载，则不进行数据重发操作。
在一实施方式中，如果源承载支持数据复制型传输且在从所述源承载类型改变到所述目标承载类型的过程中，存在至少一个已创建且未重新建立的RLC实体，则不进行数据重发操作。
在一实施方式中，所述不进行数据重发操作，是指：不进行PDCP实体数据恢复操作中的数据重发操作。
在一实施方式中，如果目标承载未配置或未激活PDCP复制传输，则不进行数据重发操作。
在一实施方式中，所述不进行数据重发操作是指：不通过已创建且未重新建立的RLC实体进行数据重发操作，且不通过新创建的RLC实体和/或重新建立的RLC实体进行数据重发操作。
在一实施方式中，如果所述目标承载配置并激活了PDCP复制传输，则所述不进行数据重发操作是指：不通过已创建且未重新建立的RLC实体进行数据重发操作，但能够通过新创建的RLC实体和/或重新建立的RLC实体进行数据重发操作。
本发明实施例中，所述装置还包括：
重传单元(图中未示出)，用于如果PDCP实体进行数据恢复操作，则通过新创建的RLC实体和/或重新建立的RLC实体进行数据重发操作。
其中，所述数据重发操作，是指：重新发送PDCP实体进行数据恢复操作前已经发送给释放的RLC实体和/或重新建立的RLC实体，且没有收到成功收到确认消息的数据。
在一实施方式中，所述重新发送PDCP实体进行数据恢复操作前已经发送给释放的RLC实体和/或重新建立的RLC实体，且没有收到成功收到确认消息的数据，包括：
重新发送PDCP实体进行数据恢复操作前已经发送给释放的RLC实体和/或重新建立的RLC实体，且PDCP实体进行数据恢复操作前未发送给已创建且未重新建立的RLC实体，且没有收到成功收到确认消息的数据。
在一实施方式中，所述重新发送PDCP实体进行数据恢复操作前已经发送给释放的RLC实体和/或重新建立的RLC实体，且没有收到成功收到确认消息的数据，包括：
在源承载未配置和/或配置了但未激活数据复制传输的情况下，重新发送PDCP实体进行数据恢复操作前已经发送给释放的RLC实体和/或重新建立的RLC实体，且没有收到成功收到确认消息的数据。
在一实施方式中，所述重新发送PDCP实体进行数据恢复操作前已经发送给释放的RLC实体和/或重新建立的RLC实体，且没有收到成功收到确认消息的数据，包括：
在RLC实体均重新建立或释放的情况下，重新发送PDCP实体进行数据恢复操作前已经发送给释放的RLC实体和/或重新建立的RLC实体，且没有收到成功收到确认消息的数据。
在一实施方式中，如果所述数据重发操作重发的是PDCP实体进行数据恢复操作前已经发送给已创建且未重新建立的RLC实体的数据，则所述重传单元通过新创建的RLC实体和/或重新建立的RLC实体进行数据重发操作。
在一实施方式中，如果所述数据重发操作重发的是PDCP实体进行数据恢复操作前未发送给已创建且未重新建立的RLC实体的数据，则所述重传单元通过新创建的RLC实体和/或重新建立的RLC实体和/或已创建且未重新建立的RLC实体进行数据重发操作。
在一实施方式中，如果源承载支持数据复制型传输且目标承载支持数据复制型传输且所述源承 载为分流承载，则通过新创建的RLC实体和/或重新建立的RLC实体进行数据重发操作。
在一实施方式中，如果源承载支持数据复制型传输且目标承载支持数据复制型传输且所述目标承载为分流承载，则通过新创建的RLC实体和/或重新建立的RLC实体进行数据重发操作。
在一实施方式中，如果源承载支持数据复制型传输且目标承载支持数据复制型传输且在从所述源承载类型改变到所述目标承载类型的过程中，存在至少一个已创建且未重新建立的RLC实体，则通过新创建的RLC实体和/或重新建立的RLC实体进行数据重发操作。
在一实施方式中，如果源承载支持数据复制型传输且目标承载不支持数据复制型传输且在从所述源承载类型改变到所述目标承载类型的过程中，存在至少一个已创建且未重新建立的RLC实体，则通过新创建的RLC实体和/或重新建立的RLC实体进行数据重发操作。
在一实施方式中，所述目标承载支持数据复制型传输，是指：所述目标承载配置了PDCP复制传输。
在一实施方式中，所述目标承载支持数据复制型传输，是指：所述目标承载配置并激活了PDCP复制传输。
在一实施方式中，所述源承载支持数据复制型传输，是指：所述源承载配置了PDCP复制传输。
在一实施方式中，所述源承载支持数据复制型传输，是指：所述源承载配置并激活了PDCP复制传输。
本领域技术人员应当理解，图9所示的改变承载类型的装置中的各单元的实现功能可参照前述改变承载类型的方法的相关描述而理解。图9所示的改变承载类型的装置中的各单元的功能可通过运行于处理器上的程序而实现，也可通过具体的逻辑电路而实现。
本发明实施例上述改变承载类型的装置如果以软件功能模块的形式实现并作为独立的产品销售或使用时，也可以存储在一个计算机可读取存储介质中。基于这样的理解，本发明实施例的技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机、服务器、或者网络设备等)执行本发明各个实施例所述方法的全部或部分。而前述的存储介质包括：U盘、移动硬盘、只读存储器(ROM，Read Only Memory)、磁碟或者光盘等各种可以存储程序代码的介质。这样，本发明实施例不限制于任何特定的硬件和软件结合。
相应地，本发明实施例还提供一种计算机存储介质，其中存储有计算机可执行指令，该计算机可执行指令被处理器执行时实现本发明实施例的上述改变承载类型的方法。
图10为本发明实施例的终端的结构组成示意图，如图10所示，终端100可以包括一个或多个(图中仅示出一个)处理器12(处理器12可以包括但不限于微处理器(MCU，Micro Controller Unit)或可编程逻辑器件(FPGA，Field Programmable Gate Array)等的处理装置)、用于存储数据的存储器14、以及用于通信功能的传输装置16。本领域普通技术人员可以理解，图10所示的结构仅为示意，其并不对上述电子装置的结构造成限定。例如，终端100还可包括比图10中所示更多或者更少的组件，或者具有与图10所示不同的配置。
存储器14可用于存储应用软件的软件程序以及模块，如本发明实施例中的改变承载类型的方法对应的程序指令/模块，处理器12通过运行存储在存储器14内的软件程序以及模块，从而执行各种功能应用以及数据处理，即实现上述的方法。存储器14可包括高速随机存储器，还可包括非易失性存储器，如一个或者多个磁性存储装置、闪存、或者其他非易失性固态存储器。在一些实例中，存储器14可进一步包括相对于处理器12远程设置的存储器，这些远程存储器可以通过网络连接至终端100。上述网络的实例包括但不限于互联网、企业内部网、局域网、移动通信网及其组合。
传输装置16用于经由一个网络接收或者发送数据。上述的网络具体实例可包括终端100的通信供应商提供的无线网络。在一个实例中，传输装置16包括一个网络适配器(NIC，Network Interface Controller)，其可通过基站与其他网络设备相连从而可与互联网进行通讯。在一个实例中，传输装置16可以为射频(RF，Radio Frequency)模块，其用于通过无线方式与互联网进行通讯。
本发明实施例所记载的技术方案之间，在不冲突的情况下，可以任意组合。
在本发明所提供的几个实施例中，应该理解到，所揭露的方法和智能设备，可以通过其它的方式实现。以上所描述的设备实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，如：多个单元或组件可以结合，或可以集成到另一个***，或一些特征可以忽略，或不执行。另外，所显示或讨论的各组成部分相互之间的耦合、或直接耦合、或通信连接可以是通过一些接口，设备或单元的间接耦合或通信连接，可以是电性的、机械的或其它形式的。
上述作为分离部件说明的单元可以是、或也可以不是物理上分开的，作为单元显示的部件可以是、或也可以不是物理单元，即可以位于一个地方，也可以分布到多个网络单元上；可以根据实际的需要选择其中的部分或全部单元来实现本实施例方案的目的。
另外，在本发明各实施例中的各功能单元可以全部集成在一个第二处理单元中，也可以是各单元分别单独作为一个单元，也可以两个或两个以上单元集成在一个单元中；上述集成的单元既可以采用硬件的形式实现，也可以采用硬件加软件功能单元的形式实现。
以上所述，仅为本发明的具体实施方式，但本发明的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本发明揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本发明的保护范围之内。

Claims (65)

  1. 一种改变承载类型的方法，所述方法包括：
    终端接收到控制信令，所述控制信令携有第一指示信息，所述第一指示信息用于指示所述终端从源承载类型改变到目标承载类型；
    所述终端基于所述源承载类型的传输特征以及所述目标承载类型的传输特征，释放所述源承载类型对应的至少一个无线链路控制协议RLC实体，和/或创建所述目标承载类型对应的至少一个RLC实体。
  2. 根据权利要求1所述的改变承载类型的方法，其中，所述控制信令还携有第二指示信息，所述第二指示信息用于指示所述目标承载类型是否支持数据复制型传输。
  3. 根据权利要求2所述的改变承载类型的方法，其中，
    所述源承载类型支持数据复制型传输，所述目标承载类型不支持数据复制型传输；或者，
    所述源承载类型不支持数据复制型传输，所述目标承载类型支持数据复制型传输；或者，
    所述源承载类型支持数据复制型传输，所述目标承载类型支持数据复制型传输；或者，
    所述源承载类型不支持数据复制型传输，所述目标承载类型不支持数据复制型传输。
  4. 根据权利要求3所述的改变承载类型的方法，其中，所述源承载类型为非分流负载；
    所述终端基于所述源承载类型的传输特征以及所述目标承载类型的传输特征，释放所述源承载类型对应的至少一个RLC实体，包括：
    如果所述源承载类型支持数据复制型传输，则判断所述目标承载类型是否为分流负载；
    如果所述目标承载类型是所述分流负载，则从所述源承载类型对应的两个RLC实体中释放一个RLC实体；
    如果所述目标承载类型不是所述分流负载，则从所述源承载类型对应的两个RLC实体中释放两个RLC实体。
  5. 根据权利要求4所述的改变承载类型的方法，其中，所述目标承载类型能够支持数据复制型传输或者不支持数据复制型传输。
  6. 根据权利要求3所述的改变承载类型的方法，其中，所述目标承载类型为非分流负载；
    所述终端基于所述源承载类型的传输特征以及所述目标承载类型的传输特征，创建所述目标承载类型对应的至少一个RLC实体，包括：
    如果所述目标承载类型支持数据复制型传输，则判断所述源承载类型是否为分流负载；
    如果所述源承载类型是所述分流负载，则创建所述目标承载类型对应的一个RLC实体；
    如果所述源承载类型不是所述分流负载，则创建所述目标承载类型对应的两个RLC实体。
  7. 根据权利要求6所述的改变承载类型的方法，其中，所述源承载类型能够支持数据复制型传输或者不支持数据复制型传输。
  8. 根据权利要求1至7任一项所述的改变承载类型的方法，其中，在从所述源承载类型改变到所述目标承载类型的过程中，
    如果源承载支持数据复制型传输，则不进行数据重发操作。
  9. 根据权利要求8所述的改变承载类型的方法，其中，所述源承载支持数据复制型传输，是指：所述源承载配置了分组数据汇聚协议PDCP复制传输。
  10. 根据权利要求8所述的改变承载类型的方法，其中，所述源承载支持数据复制型传输，是指：所述源承载配置并激活了PDCP复制传输。
  11. 根据权利要求8至10任一项所述的改变承载类型的方法，其中，
    如果源承载支持数据复制型传输且所述源承载为分流承载，则不进行数据重发操作。
  12. 根据权利要求8至10任一项所述的改变承载类型的方法，其中，
    如果源承载支持数据复制型传输且目标承载为分流承载，则不进行数据重发操作。
  13. 根据权利要求8至10任一项所述的改变承载类型的方法，其中，
    如果源承载支持数据复制型传输且在从所述源承载类型改变到所述目标承载类型的过程中，存在至少一个已创建且未重新建立的RLC实体，则不进行数据重发操作。
  14. 根据权利要求8至13任一项所述的改变承载类型的方法，其中，所述不进行数据重发操作，是指：不进行PDCP实体数据恢复操作中的数据重发操作。
  15. 根据权利要求8至14任一项所述的改变承载类型的方法，其中，
    如果目标承载未配置或未激活PDCP复制传输，则不进行数据重发操作。
  16. 根据权利要求8至15任一项所述的改变承载类型的方法，其中，所述不进行数据重发操作是指：不通过已创建且未重新建立的RLC实体进行数据重发操作，且不通过新创建的RLC实体和/或重新建立的RLC实体进行数据重发操作。
  17. 根据权利要求8至14任一项所述的改变承载类型的方法，其中，
    如果所述目标承载配置并激活了PDCP复制传输，则所述不进行数据重发操作是指：不通过已创建且未重新建立的RLC实体进行数据重发操作，但能够通过新创建的RLC实体和/或重新建立的RLC实体进行数据重发操作。
  18. 根据权利要求1至7任一项所述的改变承载类型的方法，其中，在从所述源承载类型改变到所述目标承载类型的过程中，
    如果PDCP实体进行数据恢复操作，则通过新创建的RLC实体和/或重新建立的RLC实体进行数据重发操作。
  19. 根据权利要求18所述的改变承载类型的方法，其中，所述数据重发操作，是指：重新发送PDCP实体进行数据恢复操作前已经发送给释放的RLC实体和/或重新建立的RLC实体，且没有收到成功收到确认消息的数据。
  20. 根据权利要求19所述的改变承载类型的方法，其中，所述重新发送PDCP实体进行数据恢复操作前已经发送给释放的RLC实体和/或重新建立的RLC实体，且没有收到成功收到确认消息的数据，包括：
    重新发送PDCP实体进行数据恢复操作前已经发送给释放的RLC实体和/或重新建立的RLC实体，且PDCP实体进行数据恢复操作前未发送给已创建且未重新建立的RLC实体，且没有收到成功收到确认消息的数据。
  21. 根据权利要求19至20任一项所述的改变承载类型的方法，其中，所述重新发送PDCP实体进行数据恢复操作前已经发送给释放的RLC实体和/或重新建立的RLC实体，且没有收到成功收到确认消息的数据，包括：
    在源承载未配置和/或配置了但未激活数据复制传输的情况下，重新发送PDCP实体进行数据恢复操作前已经发送给释放的RLC实体和/或重新建立的RLC实体，且没有收到成功收到确认消息的数据。
  22. 根据权利要求19至20任一项所述的改变承载类型的方法，其中，所述重新发送PDCP实体进行数据恢复操作前已经发送给释放的RLC实体和/或重新建立的RLC实体，且没有收到成功收到确认消息的数据，包括：
    在RLC实体均重新建立或释放的情况下，重新发送PDCP实体进行数据恢复操作前已经发送给释放的RLC实体和/或重新建立的RLC实体，且没有收到成功收到确认消息的数据。
  23. 根据权利要求18至22任一项所述的改变承载类型的方法，其中，
    如果所述数据重发操作重发的是PDCP实体进行数据恢复操作前已经发送给已创建且未重新建立的RLC实体的数据，则通过新创建的RLC实体和/或重新建立的RLC实体进行数据重发操作。
  24. 根据权利要求18至22任一项所述的改变承载类型的方法，其中，
    如果所述数据重发操作重发的是PDCP实体进行数据恢复操作前未发送给已创建且未重新建立的RLC实体的数据，则通过新创建的RLC实体和/或重新建立的RLC实体和/或已创建且未重新建立的RLC实体进行数据重发操作。
  25. 根据权利要求18至24任一项所述的改变承载类型的方法，其中，
    如果源承载支持数据复制型传输且目标承载支持数据复制型传输且所述源承载为分流承载，则通过新创建的RLC实体和/或重新建立的RLC实体进行数据重发操作。
  26. 根据权利要求18至25任一项所述的改变承载类型的方法，其中，
    如果源承载支持数据复制型传输且目标承载支持数据复制型传输且所述目标承载为分流承载，则通过新创建的RLC实体和/或重新建立的RLC实体进行数据重发操作。
  27. 根据权利要求18至26任一项所述的改变承载类型的方法，其中，
    如果源承载支持数据复制型传输且目标承载支持数据复制型传输且在从所述源承载类型改变到所述目标承载类型的过程中，存在至少一个已创建且未重新建立的RLC实体，则通过新创建的RLC实体和/或重新建立的RLC实体进行数据重发操作。
  28. 根据权利要求18至24任一项所述的改变承载类型的方法，其中，
    如果源承载支持数据复制型传输且目标承载不支持数据复制型传输且在从所述源承载类型改变到所述目标承载类型的过程中，存在至少一个已创建且未重新建立的RLC实体，则通过新创建的RLC实体和/或重新建立的RLC实体进行数据重发操作。
  29. 根据权利要求25至28任一项所述的改变承载类型的方法，其中，所述目标承载支持数据复制型传输，是指：所述目标承载配置了PDCP复制传输。
  30. 根据权利要求25至28任一项所述的改变承载类型的方法，其中，所述目标承载支持数据复制型传输，是指：所述目标承载配置并激活了PDCP复制传输。
  31. 根据权利要求25至30任一项所述的改变承载类型的方法，其中，所述源承载支持数据复制型传输，是指：所述源承载配置了PDCP复制传输。
  32. 根据权利要求25至30任一项所述的改变承载类型的方法，其中，所述源承载支持数据复制型传输，是指：所述源承载配置并激活了PDCP复制传输。
  33. 一种改变承载类型的装置，所述装置包括：
    接收单元，配置为接收到控制信令，所述控制信令携有第一指示信息，所述第一指示信息用于指示所述终端从源承载类型改变到目标承载类型；
    承载类型改变单元，配置为基于所述源承载类型的传输特征以及所述目标承载类型的传输特征，释放所述源承载类型对应的至少一个RLC实体，和/或创建所述目标承载类型对应的至少一个RLC实体。
  34. 根据权利要求33所述的改变承载类型的装置，其中，所述控制信令还携有第二指示信息，所述第二指示信息用于指示所述目标承载类型是否支持数据复制型传输。
  35. 根据权利要求34所述的改变承载类型的装置，其中，
    所述源承载类型支持数据复制型传输，所述目标承载类型不支持数据复制型传输；或者，
    所述源承载类型不支持数据复制型传输，所述目标承载类型支持数据复制型传输；或者，
    所述源承载类型支持数据复制型传输，所述目标承载类型支持数据复制型传输；或者，
    所述源承载类型不支持数据复制型传输，所述目标承载类型不支持数据复制型传输。
  36. 根据权利要求35所述的改变承载类型的装置，其中，所述源承载类型为非分流负载；
    所述承载类型改变单元包括：
    第一判断子单元，配置为如果所述源承载类型支持数据复制型传输，则判断所述目标承载类型是否为分流负载；
    释放子单元，配置为如果所述目标承载类型是所述分流负载，则从所述源承载类型对应的两个RLC实体中释放一个RLC实体；如果所述目标承载类型不是所述分流负载，则从所述源承载类型对应的两个RLC实体中释放两个RLC实体。
  37. 根据权利要求36所述的改变承载类型的装置，其中，所述目标承载类型能够支持数据复制型传输或者不支持数据复制型传输。
  38. 根据权利要求35所述的改变承载类型的装置，其中，所述目标承载类型为非分流负载；
    所述承载类型改变单元包括：
    第二判断子单元，配置为如果所述目标承载类型支持数据复制型传输，则判断所述源承载类型是否为分流负载；
    创建子单元，配置为如果所述源承载类型是所述分流负载，则创建所述目标承载类型对应的一个RLC实体；如果所述源承载类型不是所述分流负载，则创建所述目标承载类型对应的两个RLC实体。
  39. 根据权利要求38所述的改变承载类型的装置，其中，所述源承载类型能够支持数据复制型传输或者不支持数据复制型传输。
  40. 根据权利要求33至39任一项所述的改变承载类型的装置，其中，所述装置还包括：
    重传单元，用于如果源承载支持数据复制型传输，则不进行数据重发操作。
  41. 根据权利要求40所述的改变承载类型的装置，其中，所述源承载支持数据复制型传输，是指：所述源承载配置了分组数据汇聚协议PDCP复制传输。
  42. 根据权利要求40所述的改变承载类型的装置，其中，所述源承载支持数据复制型传输，是指：所述源承载配置并激活了PDCP复制传输。
  43. 根据权利要求40至42任一项所述的改变承载类型的装置，其中，如果源承载支持数据复制型传输且所述源承载为分流承载，则不进行数据重发操作。
  44. 根据权利要求40至42任一项所述的改变承载类型的装置，其中，如果源承载支持数据复制型传输且目标承载为分流承载，则不进行数据重发操作。
  45. 根据权利要求40至42任一项所述的改变承载类型的装置，其中，如果源承载支持数据复制型传输且在从所述源承载类型改变到所述目标承载类型的过程中，存在至少一个已创建且未重新建立的RLC实体，则不进行数据重发操作。
  46. 根据权利要求40至45任一项所述的改变承载类型的装置，其中，所述不进行数据重发操作，是指：不进行PDCP实体数据恢复操作中的数据重发操作。
  47. 根据权利要求40至46任一项所述的改变承载类型的装置，其中，
    如果目标承载未配置或未激活PDCP复制传输，则不进行数据重发操作。
  48. 根据权利要求40至47任一项所述的改变承载类型的装置，其中，所述不进行数据重发操作是指：不通过已创建且未重新建立的RLC实体进行数据重发操作，且不通过新创建的RLC实体和/或重新建立的RLC实体进行数据重发操作。
  49. 根据权利要求40至46任一项所述的改变承载类型的装置，其中，
    如果所述目标承载配置并激活了PDCP复制传输，则所述不进行数据重发操作是指：不通过已创建且未重新建立的RLC实体进行数据重发操作，但能够通过新创建的RLC实体和/或重新建立的RLC实体进行数据重发操作。
  50. 根据权利要求33至39任一项所述的改变承载类型的装置，其中，所述装置还包括：
    重传单元，用于如果PDCP实体进行数据恢复操作，则通过新创建的RLC实体和/或重新建立的RLC实体进行数据重发操作。
  51. 根据权利要求50所述的改变承载类型的装置，其中，所述数据重发操作，是指：重新发送PDCP实体进行数据恢复操作前已经发送给释放的RLC实体和/或重新建立的RLC实体，且没有收到成功收到确认消息的数据。
  52. 根据权利要求51所述的改变承载类型的装置，其中，所述重新发送PDCP实体进行数据恢复操作前已经发送给释放的RLC实体和/或重新建立的RLC实体，且没有收到成功收到确认消息的数据，包括：
    重新发送PDCP实体进行数据恢复操作前已经发送给释放的RLC实体和/或重新建立的RLC实体，且PDCP实体进行数据恢复操作前未发送给已创建且未重新建立的RLC实体，且没有收到成功收到确认消息的数据。
  53. 根据权利要求51至52任一项所述的改变承载类型的装置，其中，所述重新发送PDCP实体进行数据恢复操作前已经发送给释放的RLC实体和/或重新建立的RLC实体，且没有收到成功收到确认消息的数据，包括：
    在源承载未配置和/或配置了但未激活数据复制传输的情况下，重新发送PDCP实体进行数据恢复操作前已经发送给释放的RLC实体和/或重新建立的RLC实体，且没有收到成功收到确认消息的数据。
  54. 根据权利要求51至52任一项所述的改变承载类型的装置，其中，所述重新发送PDCP实体进行数据恢复操作前已经发送给释放的RLC实体和/或重新建立的RLC实体，且没有收到成功收到确认消息的数据，包括：
    在RLC实体均重新建立或释放的情况下，重新发送PDCP实体进行数据恢复操作前已经发送给释放的RLC实体和/或重新建立的RLC实体，且没有收到成功收到确认消息的数据。
  55. 根据权利要求50至54任一项所述的改变承载类型的装置，其中，
    如果所述数据重发操作重发的是PDCP实体进行数据恢复操作前已经发送给已创建且未重新建立的RLC实体的数据，则所述重传单元通过新创建的RLC实体和/或重新建立的RLC实体进行数据重发操作。
  56. 根据权利要求50至54任一项所述的改变承载类型的装置，其中，
    如果所述数据重发操作重发的是PDCP实体进行数据恢复操作前未发送给已创建且未重新建立的RLC实体的数据，则所述重传单元通过新创建的RLC实体和/或重新建立的RLC实体和/或已创建且未重新建立的RLC实体进行数据重发操作。
  57. 根据权利要求50至56任一项所述的改变承载类型的装置，其中，
    如果源承载支持数据复制型传输且目标承载支持数据复制型传输且所述源承载为分流承载，则通过新创建的RLC实体和/或重新建立的RLC实体进行数据重发操作。
  58. 根据权利要求50至57任一项所述的改变承载类型的装置，其中，
    如果源承载支持数据复制型传输且目标承载支持数据复制型传输且所述目标承载为分流承载，则通过新创建的RLC实体和/或重新建立的RLC实体进行数据重发操作。
  59. 根据权利要求50至58任一项所述的改变承载类型的装置，其中，
    如果源承载支持数据复制型传输且目标承载支持数据复制型传输且在从所述源承载类型改变到所述目标承载类型的过程中，存在至少一个已创建且未重新建立的RLC实体，则通过新创建的RLC实体和/或重新建立的RLC实体进行数据重发操作。
  60. 根据权利要求50至56任一项所述的改变承载类型的装置，其中，
    如果源承载支持数据复制型传输且目标承载不支持数据复制型传输且在从所述源承载类型改变到所述目标承载类型的过程中，存在至少一个已创建且未重新建立的RLC实体，则通过新创建的RLC实体和/或重新建立的RLC实体进行数据重发操作。
  61. 根据权利要求57至60任一项所述的改变承载类型的装置，其中，所述目标承载支持数据复制型传输，是指：所述目标承载配置了PDCP复制传输。
  62. 根据权利要求57至60任一项所述的改变承载类型的装置，其中，所述目标承载支持数据复制型传输，是指：所述目标承载配置并激活了PDCP复制传输。
  63. 根据权利要求57至62任一项所述的改变承载类型的装置，其中，所述源承载支持数据复制型传输，是指：所述源承载配置了PDCP复制传输。
  64. 根据权利要求57至62任一项所述的改变承载类型的装置，其中，所述源承载支持数据复制型传输，是指：所述源承载配置并激活了PDCP复制传输。
  65. 一种计算机存储介质，其上存储有计算机可执行指令，该计算机可执行指令被处理器执行时实现权利要求1至32任一项所述的方法步骤。
PCT/CN2018/084182 2017-09-15 2018-04-24 一种改变承载类型的方法及装置、计算机存储介质 WO2019052174A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201880052002.1A CN111034155B (zh) 2017-09-15 2018-04-24 一种改变承载类型的方法及装置、计算机存储介质

Applications Claiming Priority (6)

Application Number Priority Date Filing Date Title
PCT/CN2017/101888 WO2019051775A1 (zh) 2017-09-15 2017-09-15 一种改变承载类型的方法及装置、计算机存储介质
CNPCT/CN2017/101888 2017-09-15
CNPCT/CN2018/079908 2018-03-21
CN2018079908 2018-03-21
CN2018082655 2018-04-11
CNPCT/CN2018/082655 2018-04-11

Publications (1)

Publication Number Publication Date
WO2019052174A1 true WO2019052174A1 (zh) 2019-03-21

Family

ID=65722432

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/084182 WO2019052174A1 (zh) 2017-09-15 2018-04-24 一种改变承载类型的方法及装置、计算机存储介质

Country Status (2)

Country Link
CN (1) CN111034155B (zh)
WO (1) WO2019052174A1 (zh)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101291529A (zh) * 2007-04-20 2008-10-22 华为技术有限公司 识别承载类型的方法和设备
CN103858455A (zh) * 2011-10-07 2014-06-11 华为技术有限公司 用于通信***中多点传输的***和方法
CN104955064A (zh) * 2014-03-28 2015-09-30 上海贝尔股份有限公司 一种在双连接***中处理用户设备端rlc/pdcp实体的方法与设备
WO2016021820A1 (en) * 2014-08-08 2016-02-11 Lg Electronics Inc. Method for processing a packet data convergence protocol re-ordering function at a user equipment in a dual connectivity system and device therefor
EP3125640A1 (en) * 2014-03-28 2017-02-01 Fujitsu Limited Bear management device and method and communication system

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101291529A (zh) * 2007-04-20 2008-10-22 华为技术有限公司 识别承载类型的方法和设备
CN103858455A (zh) * 2011-10-07 2014-06-11 华为技术有限公司 用于通信***中多点传输的***和方法
CN104955064A (zh) * 2014-03-28 2015-09-30 上海贝尔股份有限公司 一种在双连接***中处理用户设备端rlc/pdcp实体的方法与设备
WO2015145255A2 (en) * 2014-03-28 2015-10-01 Alcatel Lucent Method and apparatus for processing rlc/ pdcp entities at a user equipment in a dual connectivity system
EP3125640A1 (en) * 2014-03-28 2017-02-01 Fujitsu Limited Bear management device and method and communication system
WO2016021820A1 (en) * 2014-08-08 2016-02-11 Lg Electronics Inc. Method for processing a packet data convergence protocol re-ordering function at a user equipment in a dual connectivity system and device therefor

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
VIVO: "Discussion on the bearer type change of duplicate bearer", vol. RAN WG2, no. Berlin, Germany; 20170821 - 20170825, 20 August 2017 (2017-08-20), XP051318354, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/Meetings_3GPP_SYNC/RAN2/Docs/> [retrieved on 20170820] *

Also Published As

Publication number Publication date
CN111034155A (zh) 2020-04-17
CN111034155B (zh) 2020-12-04

Similar Documents

Publication Publication Date Title
CN114826498B (zh) 分组复制操作模式之间的切换
US20220124868A1 (en) Method and apparatus for transmitting and receiving data in wireless communication system
US11805443B2 (en) Method and apparatus for data processing in wireless communication system
CN109691155B (zh) 无线通信***中管理用户平面操作的方法和装置
KR102299118B1 (ko) 신규 무선 접속 기술에서의 중복 및 rlc 동작
KR102460350B1 (ko) 통신 시스템에서 데이터 송수신 방법 및 장치
KR102293998B1 (ko) Tcp/ip를 고려한 데이터 처리 방법
EP3031281B1 (en) Use of packet status report from secondary base station to master base station in wireless network
CN111373837B (zh) 用于在无线通信***中发送和接收数据的方法和装置
JP2020511842A (ja) ネットワーク接続の復旧方法、装置及び通信システム
WO2019153517A1 (zh) 无线链路失败处理方法及相关产品
JP2017526302A (ja) 無線ネットワーク内の多重接続性
CN114731560A (zh) 下一代无线通信***中在daps移交期间驱动pdcp实体的方法和装置
US20220377602A1 (en) Method and apparatus for performing feedback-based ethernet header compression or decompression in wireless communication system
US20200045766A1 (en) Wireless node communication method and apparatus in wireless communication system
CN113396607A (zh) 用于在无线通信***中执行切换的方法和设备
JP2018500802A (ja) セカンダリ基地局ベアラの変更
CN112105092B (zh) 双连接重建立中数据的处理方法及装置
US20220201786A1 (en) Methods and apparatus to reduce packet latency in multi-leg transmission
KR20210054998A (ko) 무선 통신 시스템에서 피드백 기반 이더넷 헤더 압축 또는 압축 해제를 수행하는 방법 또는 장치
WO2020090442A1 (ja) 無線通信方法及び装置
WO2022120744A1 (zh) 数据传输处理方法及相关装置
CN111034155B (zh) 一种改变承载类型的方法及装置、计算机存储介质
WO2020178918A1 (ja) 無線通信システム
KR20200114943A (ko) Mcg rlf 시 하향링크 srb 메시지를 처리하는 방법 및 장치

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 18857122

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 18857122

Country of ref document: EP

Kind code of ref document: A1