CN109391951B

CN109391951B - Method and equipment for bearing type conversion

Info

Publication number: CN109391951B
Application number: CN201710652924.3A
Authority: CN
Inventors: 吴昱民
Original assignee: Vivo Mobile Communication Co Ltd
Current assignee: Vivo Mobile Communication Co Ltd
Priority date: 2017-08-02
Filing date: 2017-08-02
Publication date: 2021-06-22
Anticipated expiration: 2037-08-02
Also published as: CN109391951A

Abstract

The application provides a method and equipment for bearing type conversion, wherein the method comprises the following steps: receiving configuration information sent by network equipment, wherein the configuration information comprises an ID (identity) of a target bearer and conversion mode indication information, the bearer type of the target bearer is a first bearer type, and the conversion mode indication information is used for indicating a second bearer type; and according to the configuration information, converting the bearer type of the target bearer from a first bearer type to a second bearer type, wherein at least one of the first bearer type and the second bearer type is a duplicate bearer, and when the first bearer type and the second bearer type are both duplicate bearers, the first bearer type is a master cell group duplicate bearer and the second bearer type is a secondary cell group duplicate bearer, or the first bearer type is a secondary cell group duplicate bearer and the second bearer type is a master cell group duplicate bearer. The method for bearing type conversion in the embodiment of the application can reduce signaling overhead in a communication system and avoid data packet loss.

Description

Method and equipment for bearing type conversion

Technical Field

The present application relates to the field of communications technologies, and in particular, to a method and an apparatus for bearer type transformation.

Background

A fifth Generation (5th-Generation, 5G) mobile communication system will employ a Dual Connectivity (DC) architecture. The DC architecture includes two cell groups: a Master Cell Group (MCG) and a Secondary Cell Group (SCG), and a DC architecture supports a Packet Data Convergence Protocol (PDCP) replication function. There will be multiple bearer types (Bear types) of bearers in a 5G mobile communication system.

If a bearer with a first bearer type exists in the communication system, and if the bearer with the first bearer type is not needed in the mobile communication system at a certain time and a bearer with a second bearer type is needed, according to the related scheme of the prior art, the communication system deletes the bearer with the first bearer type and then establishes the bearer with the second bearer type, which increases the signaling overhead of the communication system, and directly deleting the bearer will cause data packet loss.

Disclosure of Invention

The embodiment of the application provides a method and equipment for bearing type conversion, so that terminal equipment can realize the conversion of bearing types of bearings, reduce signaling overhead of a communication system and reduce data packet loss.

In a first aspect, a method for bearer type transformation is provided, where the method is performed by a terminal device, and the method includes:

receiving configuration information sent by network equipment, wherein the configuration information comprises an Identification (ID) of a target bearer and conversion mode indication information, the bearer type of the target bearer is a first bearer type, and the conversion mode indication information is used for indicating a second bearer type;

and according to the configuration information, converting the bearer type of the target bearer from the first bearer type to the second bearer type, wherein at least one of the first bearer type and the second bearer type is a duplicate bearer, and when both the first bearer type and the second bearer type are duplicate bearers, the first bearer type is a master cell group duplicate bearer and the second bearer type is a secondary cell group duplicate bearer, or the first bearer type is a secondary cell group duplicate bearer and the second bearer type is a master cell group duplicate bearer.

In a second aspect, a method for transforming a bearer type is provided, where the method is performed by a network device, and the method includes:

sending configuration information to a terminal device, wherein the configuration information comprises an identification ID (identity) of a target bearer and conversion mode indication information, the bearer type of the target bearer is a first bearer type, and the conversion mode indication information is used for indicating a second bearer type;

and according to the configuration information, converting the type of the target bearer from the first bearer type to the second bearer type, wherein at least one of the first bearer type and the second bearer type is a duplicate bearer, and when both the first bearer type and the second bearer type are duplicate bearers, the first bearer type is a master cell group duplicate bearer and the second bearer type is a secondary cell group duplicate bearer, or the first bearer type is a secondary cell group duplicate bearer and the second bearer type is a master cell group duplicate bearer.

In a third aspect, a terminal device is provided, which includes:

a transceiver module, configured to receive configuration information sent by a network device, where the configuration information includes an identifier ID of a target bearer and conversion mode indication information, a bearer type of the target bearer is a first bearer type, and the conversion mode indication information is used to indicate a second bearer type;

a processing module, configured to transform the bearer type of the target bearer from the first bearer type to the second bearer type according to the configuration information, where at least one of the first bearer type and the second bearer type is a duplicate bearer, and when the first bearer type and the second bearer type are both duplicate bearers, the first bearer type is a master cell group duplicate bearer and the second bearer type is a secondary cell group duplicate bearer, or the first bearer type is a secondary cell group duplicate bearer and the second bearer type is a master cell group duplicate bearer.

In a fourth aspect, a network device is provided, comprising:

a transceiver module, configured to send configuration information to a terminal device, where the configuration information includes an identifier ID of a target bearer and conversion mode indication information, a bearer type of the target bearer is a first bearer type, and the conversion mode indication information is used to indicate a second bearer type;

a processing module, configured to transform the type of the target bearer from the first bearer type to the second bearer type according to the configuration information, where at least one of the first bearer type and the second bearer type is a duplicate bearer, and when both the first bearer type and the second bearer type are duplicate bearers, the first bearer type is a master cell group duplicate bearer and the second bearer type is a secondary cell group duplicate bearer, or the first bearer type is a secondary cell group duplicate bearer and the second bearer type is a master cell duplicate bearer.

In a fifth aspect, a terminal device is provided, which includes a memory, a processor, and a bearer type transformation program stored in the memory and executable on the processor, and when executed by the processor, the bearer type transformation program implements the steps of the method for bearer type transformation according to the first aspect.

In a sixth aspect, there is provided a network device comprising a memory, a processor and a bearer type transformation program stored on the memory and executable on the processor, the bearer type transformation program, when executed by the processor, implementing the steps of the method of bearer type transformation according to the second aspect.

In a seventh aspect, a computer-readable medium is provided, on which a bearer type transformation program is stored, which, when being executed by a processor, implements the steps of the method of bearer type transformation according to the first aspect.

In an eighth aspect, a computer readable medium is provided, on which a bearer type transformation program is stored, which, when executed by a processor, implements the steps of the method of bearer type transformation according to the second aspect.

In a ninth aspect, there is provided a computer program product comprising instructions which, when executed by a computer, cause the computer to perform the method of bearer type transformation of the first aspect. In particular, the computer program product may be run on the terminal device of the third aspect described above.

In a tenth aspect, there is provided a computer program product comprising instructions which, when executed by a computer, cause the computer to perform the method of bearer type transformation of the second aspect. In particular, the computer program product may be run on the network device of the fourth aspect described above.

In the embodiment of the application, the terminal device receives the configuration information sent by the network device, and transforms the bearer type of the target bearer into the bearer type indicated by the conversion mode indication information according to the identifier of the target bearer and the bearer type indicated by the conversion mode indication information in the configuration information. Therefore, the terminal equipment does not need to delete the target bearer and then establish the bearer with the bearer type indicated by the conversion mode indication information, so that the signaling overhead of a communication system can be reduced, and the loss of data packets can be avoided.

Drawings

In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly introduced below, it is obvious that the drawings in the following description are only some embodiments described in the present application, and for those skilled in the art, other drawings can be obtained according to the drawings without any creative effort.

Fig. 1 is a schematic diagram of a primary cell group bearer and a secondary cell group bearer in a communication system according to an embodiment of the present application;

fig. 2 is a schematic diagram of a split bearer in a communication system according to an embodiment of the present application;

fig. 3 is a schematic diagram of a duplicate bearer in a communication system according to an embodiment of the present application;

fig. 4 is a schematic flow chart diagram of a method of bearer type transformation according to an embodiment of the present application;

fig. 5 is a schematic flow chart diagram of a method of bearer type transformation according to another embodiment of the present application;

fig. 6 is a schematic structural diagram of a terminal device according to an embodiment of the present application;

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

fig. 8 is a schematic structural diagram of a terminal device according to another embodiment of the present application;

fig. 9 is a schematic structural diagram of a network device according to another embodiment of the present application.

Detailed Description

In order to make those skilled in the art better understand the technical solutions in the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.

It should be understood that the technical solutions of the embodiments of the present application may be applied to various communication systems, for example: a Global System for Mobile communications (GSM) System, a Code Division Multiple Access (CDMA) System, a Wideband Code Division Multiple Access (WCDMA) System, a General Packet Radio Service (GPRS), a Long Term Evolution (Long Term Evolution, LTE) System, an LTE Frequency Division Duplex (FDD) System, an LTE Time Division Duplex (TDD), a Universal Mobile Telecommunications System (UMTS) or a Worldwide Interoperability for Microwave Access (WiMAX) communication System, a 5G System, or a New Radio (NR) System.

In the embodiment of the present application, the Terminal device may include, but is not limited to, a Mobile Station (MS), a Mobile Terminal (Mobile Terminal), a Mobile phone (Mobile Telephone), a User Equipment (UE), a handset (handset), a portable device (portable Equipment), a vehicle (vehicle), and the like, and the Terminal device may communicate with one or more core networks through a Radio Access Network (RAN), for example, the Terminal device may be a Mobile phone (or referred to as a "cellular" phone), a computer with a wireless communication function, and the Terminal device may also be a portable, pocket, handheld, computer-embedded, or vehicle-mounted Mobile apparatus.

The network device according to the embodiment of the present application is a device deployed in a radio access network to provide a wireless communication function for a terminal device. The network device may be a base station, and the base station may include various macro base stations, micro base stations, relay stations, access points, and the like. In systems employing different radio access technologies, the names of devices having a base station function may differ. For example, in an LTE network, referred to as an Evolved node B (eNB or eNodeB), in a third Generation (3rd Generation, 3G) network, referred to as a node B (node B), and so on.

Fig. 1 to 3 show schematic diagrams of bearer types in a communication system according to an embodiment of the present application. As shown in fig. 1 to fig. 3, the communication system includes 4 bearer types, which are respectively: master Cell Group (MCG) Bearer (Bearer), Secondary Cell Group (SCG) Bearer, Split Bearer (Split Bearer), and Duplicate Bearer (Duplicate Bearer). The Duplicate Bearer established between the terminal device and the network device in the primary cell may be referred to as a primary cell group replication Bearer, and the Duplicate Bearer established between the terminal device and the network device in the secondary cell may be referred to as a secondary cell group replication Bearer. The primary cell group replication bearer and the secondary cell group replication bearer are collectively referred to as a replication bearer.

As shown in fig. 1, the MCG Bearer corresponds to a Data Convergence Protocol (PDCP) entity, a Radio Link Control (RLC) entity, and a Medium Access Control (MAC) entity in the terminal device. The SCG Bearer and MCG Bearer types correspond to a PDCP entity, an RLC entity and an MAC entity in the terminal equipment. As shown in fig. 2, the Split Bearer corresponds to one PDCP entity, 2 RLC entities and 2 MAC entities in the terminal device, where 2 RLC entities are in different cell groups and 2 MAC entities are in different cell groups. As shown in fig. 3, the Duplicate Bearer corresponds to one PDCP entity, 2 RLC entities, and one MAC entity in one cell group in the terminal apparatus.

The method for bearer type transformation according to an embodiment of the present application will be described in detail below with reference to bearer types illustrated in fig. 1 to 3. As shown in fig. 4, the method 100 includes:

s110, receiving configuration information sent by a network device, wherein the configuration information includes an identification ID of a target bearer and conversion mode indication information, the bearer type of the target bearer is a first bearer type, and the conversion mode indication information is used for indicating a second bearer type.

And S120, according to the configuration information, converting the bearer type of the target bearer from the first bearer type to the second bearer type, wherein at least one of the first bearer type and the second bearer type is a duplicate bearer, and when both the first bearer type and the second bearer type are duplicate bearers, the first bearer type is a master cell group duplicate bearer and the second bearer type is a secondary cell group duplicate bearer, or the first bearer type is a secondary cell group duplicate bearer and the second bearer type is a master cell group duplicate bearer.

Specifically, in some embodiments, after receiving the configuration information sent by the network device, the terminal device may further determine whether a key corresponding to the target bearer is changed, and transform the bearer type of the target bearer from the first bearer type to the second bearer type according to a result of the determination and the configuration information. Here, the determination, by the terminal device, whether the key corresponding to the target bearer is changed may be determined according to other information in the configuration information, or may be determined in other manners, which is not limited in this embodiment of the present application.

Specifically, in the embodiment of the present application, a method for implementing bearer transformation by a terminal device mainly includes the method described in the following embodiment:

the first embodiment is as follows: conversion from Duplicate beer to MCG beer or SCG beer

In S110, the first Bearer type is Duplicate Bearer, the second Bearer type is MCG Bearer or SCG Bearer, it is assumed that the target Bearer corresponds to the first PDCP entity, the first RLC entity, the second RLC entity, and the first MAC entity in the terminal device, and the configuration information further includes first indication information, where the first indication information is used to indicate that the first RLC entity needs to be released.

Correspondingly, in S120, if the terminal device determines that the key corresponding to the target bearer is not changed, the terminal device will Re-establish (Re-initialization) the first RLC entity, and release the Re-established first RLC entity and the logical channel corresponding to the Re-established first RLC entity. And if the terminal equipment judges that the key corresponding to the target bearer is changed, the terminal equipment reconstructs the first PDCP entity, the first RLC entity and the second RLC entity, then the terminal equipment releases the reconstructed first RLC entity and the logic channel corresponding to the reconstructed first RLC entity, and resets (Reset) the first MAC entity.

Optionally, in S110, the first indication information includes a number of the first RLC entity and/or a logical channel number corresponding to the first RLC entity. If the first indication information only includes the number of the first RLC entity, the terminal device may determine, according to the first indication information, that the first RLC entity needs to be released, and determine, according to the correspondence between the RLC entity and the logical channel, the logical channel corresponding to the first RLC entity. If the first indication information only includes the logical channel number corresponding to the first RLC entity, the terminal device can also determine that the first RLC entity needs to be released according to the correspondence between the RLC entity and the logical channel, and determine the logical channel indicated by the logical channel number as the logical channel corresponding to the first RLC entity. If the first indication information includes the number of the first RLC entity and the logical channel number corresponding to the first RLC, the terminal device may directly determine, according to the first indication information, that the first RLC entity needs to be released and the logical channel corresponding to the logical channel number needs to be released.

Example two: conversion from Duplicate beer to Split beer

In S110, the first Bearer type is Duplicate Bearer, the second Bearer type is Split Bearer, it is assumed that the target Bearer corresponds to the first PDCP entity, the first RLC entity, the second RLC entity, and the first MAC entity in the terminal device, and the configuration information further includes second indication information, where the second indication information is used to indicate that the first RLC entity needs to change the cell group.

Correspondingly, in S120, if the terminal device determines that the key corresponding to the target Bearer is not changed, the terminal device obtains the corresponding second MAC entity with the Bearer type of Split Bearer from the Re-attribute first RLC entity, and configures the corresponding relationship between the reconstructed first RLC entity and the reconstructed second MAC entity. If the terminal equipment judges that the key corresponding to the target Bearer changes, the terminal equipment Re-examination bearing first PDCP entity, the first RLC entity and the second RLC entity, resets the first MAC entity, acquires the second MAC entity with the corresponding Bearer type of Split Bearer, and then reconfigures the corresponding relationship between the reconstructed first RLC entity and the second MAC entity.

Optionally, as an example, after the first RLC entity is reconstructed, the terminal device determines whether a logical channel number corresponding to the reconstructed first RLC entity changes. If the terminal equipment judges that the logic channel corresponding to the reconstructed first RLC entity changes, the terminal equipment also needs to reconfigure the logic channel corresponding to the reconstructed first RLC entity. The terminal device may determine whether the reconstructed logical channel corresponding to the first RLC entity changes according to the configuration of the network device. If the terminal equipment judges that the logic channel corresponding to the reconstructed first RLC entity does not change, the terminal equipment does not need to reconfigure the logic channel corresponding to the reconstructed first RLC entity.

Optionally, as another example, if the terminal device does not establish the MAC entity whose corresponding Bearer type is Split Bearer before transforming the Bearer type of the target Bearer, the terminal device establishes the second MAC entity. If the terminal device has already established the MAC entity with the corresponding Bearer type of Split Bearer before transforming the Bearer type of the target Bearer, the terminal device may directly select the established MAC entity as the second MAC entity.

Optionally, as another example, the second indication information includes a number of the first RLC entity and/or a logical channel number corresponding to the first RLC entity. If the second indication information only comprises the number of the first RLC entity, the terminal equipment can judge that the first RLC entity needs to change the cell group according to the second indication information, and determines the logical channel corresponding to the first RLC entity according to the corresponding relation between the RLC entity and the logical channel. If the second indication information only includes the logical channel number corresponding to the first RLC entity, the terminal device can also determine, according to the correspondence between the RLC entity and the logical channel, the cell group to be changed of the first RLC entity, and determine the logical channel indicated by the logical channel number as the logical channel corresponding to the first RLC entity. If the second indication information includes the number of the first RLC entity and the logical channel number corresponding to the first RLC entity, the terminal device may directly determine, according to the second indication information, that the first RLC entity needs to be changed into the cell group, and that the logical channel corresponding to the logical channel number needs to be changed into the cell group.

Example three: conversion from Duplicate beer to Duplicate beer

It should be noted that the specific cell groups corresponding to the Duplicate Bearer before and after the change are different in the third embodiment. In other words, if the first Bearer type is the master cell group Duplicate Bearer, the second Bearer type is the secondary cell group Duplicate Bearer, or if the first Bearer type is the secondary cell group Duplicate Bearer, the second Bearer type is the master cell group Duplicate Bearer.

In S110, the first Bearer type is a master cell group Duplicate Bearer and the second Bearer type is a secondary cell group Duplicate Bearer, or the first Bearer type is a secondary cell group Duplicate Bearer and the second Bearer type is a master cell group Duplicate Bearer. Assume that a target bearer corresponds to a first PDCP entity, a first RLC entity, a second RLC entity, and a first MAC entity in a terminal device.

Correspondingly, in S120, if the terminal device determines that the key corresponding to the target bearer is not changed, the terminal device reconfigures at least one entity of the first PDCP entity, the first RLC entity, the second RCL entity, and the first MAC entity. For example, if the configuration information includes parameter configuration information, the terminal device reconfigures at least one entity of the first PDCP entity, the first RLC entity, the second RCL entity, and the first MAC entity according to the parameter configuration information. And if the terminal equipment judges that the key corresponding to the target bearer is not changed, the terminal equipment reconstructs the first PDCP entity, the first MAC entity and the second MAC entity and reconstructs the first MAC entity.

Example four: conversion from MCG Bearer or SCG Bearer to Duplicate Bearer

In S110, the first Bearer type is MCG Bearer or SCG Bearer, the second Bearer type is Duplicate Bearer, and it is assumed that the target Bearer corresponds to the first PDCP entity, the first RLC entity, and the first MAC entity in the terminal device. Then, in S120, if the terminal device determines that the key corresponding to the target bearer is not changed, the terminal device will establish a second RLC entity corresponding to the target bearer and establish a logical channel corresponding to the second RLC entity. If the terminal equipment judges that the key corresponding to the target bearer changes, the terminal equipment rebuilds the first PDCP entity and the first RLC entity, establishes a second RLC entity corresponding to the target bearer, establishes a logical channel corresponding to the second RLC entity, and resets the first MAC entity.

Example five: conversion from Split beer to Duplicate beer

In S110, the first Bearer type is Split Bearer, the second Bearer type is Duplicate Bearer, and it is assumed that the terminal device corresponds to a first PDCP entity, a first RLC entity, a second RCL entity, a first MAC entity, and a second MAC entity in the terminal device, and the first RLC entity corresponds to the first MAC entity and the second RLC entity corresponds to the second MAC entity. The configuration information further includes third indication information, and the third indication information indicates that the first RLC entity needs to change the cell group.

Correspondingly, in S120, if the terminal device determines that the key corresponding to the target Bearer is not changed, the terminal device reconstructs the first RLC entity, releases the configuration that the Bearer type corresponding to the first MAC entity is Split Bearer, and configures the corresponding relationship between the reconstructed first RLC entity and the second MAC entity. If the terminal equipment judges that the key corresponding to the target Bearer is changed, the terminal equipment reconstructs the first PDCP entity, the first RLC entity and the second RLC entity, resets the first MAC entity and the second MAC entity, releases the configuration of the Bearer type of the reconstructed first MAC entity being Split Bearer, and then configures the corresponding relationship between the reconstructed first RLC entity and the reconstructed second MAC entity.

Optionally, as an example, after the first RLC entity is reconstructed, the terminal device determines whether a logical channel number corresponding to the reconstructed first RLC entity changes, and if the terminal device determines that the logical channel corresponding to the reconstructed first RLC entity changes, the terminal device further needs to reconfigure the logical channel corresponding to the reconstructed first RLC entity. The terminal device may determine whether the reconstructed logical channel corresponding to the first RLC entity changes according to the configuration of the network device. If the terminal equipment judges that the logic channel corresponding to the reconstructed first RLC entity does not change, the terminal equipment does not need to reconfigure the logic channel corresponding to the reconstructed first RLC entity.

Optionally, as another example, the network device instructs the terminal device to release the configuration with the Bearer type of Split Bearer in the first MAC entity, or the terminal device releases the configuration with the Bearer type of Split Bearer in the first MAC entity according to an agreement with the network device. Therefore, if the terminal device does not need to reset the first MAC entity, the terminal device releases the configuration that the Bearer type corresponding to the first MAC entity is Split Bearer, and if the terminal device needs to reset the first MAC entity, the terminal device releases the configuration that the Bearer type corresponding to the first MAC entity after being reset is Split Bearer.

It can be seen from the foregoing embodiments that, in the method for bearer type conversion according to the present application, the terminal device implements direct conversion of different bearer types by controlling behaviors of different protocol layer entities according to configuration information sent by the network device, so that signaling overhead of the communication system can be reduced, and loss of data packets can be avoided.

The method for bearer type transformation according to the embodiment of the present application is described in detail from the terminal device side in conjunction with fig. 4 above, and the method for bearer type transformation according to another embodiment of the present application will be described in detail from the network device side in conjunction with fig. 5 below.

Fig. 5 illustrates a method of bearer type transformation according to another embodiment of the present application. As shown in fig. 5, the method 200 includes:

s210, sending configuration information to a terminal device, wherein the configuration information comprises an identification ID (identity) of a target bearer and conversion mode indication information, the bearer type of the target bearer is a first bearer type, and the conversion mode indication information is used for indicating a second bearer type.

And S220, according to the configuration information, converting the type of the target bearer from the first bearer type to the second bearer type, wherein at least one of the first bearer type and the second bearer type is a duplicate bearer, and when both the first bearer type and the second bearer type are duplicate bearers, the first bearer type is a master cell group duplicate bearer and the second bearer type is a secondary cell group duplicate bearer, or the first bearer type is a secondary cell group duplicate bearer and the second bearer type is a master cell group duplicate bearer.

Specifically, in some embodiments, the network device may further determine whether a key corresponding to the target bearer is changed, and transform the bearer type of the target bearer from the first bearer type to the second bearer type according to a result of the determination and the configuration information.

Specifically, in this embodiment of the present application, a method for implementing bearer transformation by a network device mainly includes the method described in the following embodiment:

example six: conversion from Duplicate beer to MCG beer or SCG beer

In S210, the first Bearer type is Duplicate Bearer, the second Bearer type is MCG Bearer or SCG Bearer, it is assumed that a target Bearer corresponds to a first PDCP entity, a first RLC entity, a second RLC entity, and a first MAC entity in the network device, and the first PDCP entity, the first RLC entity, the second RLC entity, and the first MAC entity in the network device correspond to the first PDCP entity, the first RLC entity, the second RLC entity, and the first MAC entity in the terminal device corresponding to the target Bearer, respectively. The configuration information further includes first indication information, where the first indication information is used to indicate that the first RLC entity in the terminal device needs to be released.

Correspondingly, in S220, if the network device determines that the key carried by the target is not changed, the network device will release the reconstructed first RLC entity and the logical channel corresponding to the reconstructed first RLC entity in the network device. If the network equipment judges that the key corresponding to the target bearer is changed, the network equipment reconstructs a first PDCP entity, a first RLC entity and a second RLC entity in the network equipment, then the network equipment releases the reconstructed first RLC entity and a logic channel corresponding to the reconstructed first RLC entity in the network equipment, and resets (Reset) a first MAC entity in the network equipment.

Optionally, in S210, the first indication information includes a number of the first RLC entity in the terminal device, and/or a logical channel number corresponding to the first RLC entity in the terminal device.

Example seven: conversion from Duplicate beer to Split beer

In S210, the first Bearer type is Duplicate Bearer, the second Bearer type is Split Bearer, and it is assumed that the target Bearer corresponds to a first PDCP entity, a first RLC entity, a second RLC entity, and a first MAC entity in the network device, and the first PDCP entity, the first RLC entity, the second RLC entity, and the first MAC entity in the network device correspond to the first PDCP entity, the first RLC entity, the second RLC entity, and the first MAC entity in the terminal device corresponding to the target Bearer, respectively. The configuration information further includes second indication information, where the second indication information is used to indicate that the first RLC entity in the terminal equipment needs to change the cell group.

Correspondingly, in S220, if the network device determines that the key corresponding to the target Bearer is not changed, the network device configures a first RLC entity in the Re-interest network device with a second MAC entity in the network device, so that the Bearer type corresponding to the second MAC entity is Split Bearer, and configures a corresponding relationship between the first RLC entity reconstructed in the network device and the second MAC entity in the network device. If the network device judges that the key corresponding to the target Bearer is changed, a first PDCP entity, a first RLC entity and a second RLC entity in the network device Re-authorization network device reset a first MAC entity in the network device, and configures a second MAC entity in the network device, so that the Bearer type corresponding to the second MAC entity is a Split Bearer, and then reconfigures the corresponding relationship between the first RLC entity and the second MAC entity after reconstruction in the network device.

Optionally, as an example, after reconstructing the first RLC entity in the network device, the network device determines whether a logical channel number corresponding to the reconstructed first RLC entity changes, and if the network device determines that the logical channel corresponding to the reconstructed first RLC entity changes, the network device further needs to reconfigure the logical channel corresponding to the reconstructed first RLC entity. If the network equipment judges that the logic channel corresponding to the reconstructed first RLC entity does not change, the network equipment does not need to reconfigure the logic channel corresponding to the reconstructed first RLC entity.

Optionally, as another example, if the network device determines that the terminal device does not establish the MAC entity whose corresponding Bearer type is Split Bearer before transforming the Bearer type of the target Bearer, the network device configures a function of a second MAC entity in the network device. If the network device determines that the terminal device has established the MAC entity with the corresponding Bearer type of Split Bearer before transforming the Bearer type of the target Bearer, the network device may directly select the MAC entity corresponding to the MAC entity with the corresponding Bearer type of Split Bearer that has been established by the terminal device as the second MAC entity.

Optionally, as another example, the second indication information includes a number of the first RLC entity in the terminal device, and/or the second indication information includes a logical channel number corresponding to the first RLC entity in the terminal device.

Example eight: conversion from Duplicate beer to Duplicate beer

It should be noted that the cell groups specifically corresponding to the Duplicate Bearer before and after the change in example eight are different. In other words, if the first Bearer type is the master cell group Duplicate Bearer, the second Bearer type is the secondary cell group Duplicate Bearer, or if the first Bearer type is the secondary cell group Duplicate Bearer, the second Bearer type is the master cell group Duplicate Bearer.

In S210, the first Bearer type is a master cell group Duplicate Bearer and the second Bearer type is a secondary cell group Duplicate Bearer, or the first Bearer type is a secondary cell group Duplicate Bearer and the second Bearer type is a master cell group Duplicate Bearer. Assume that a target bearer corresponds to a first PDCP entity, a first RLC entity, a second RLC entity, and a first MAC entity in a network device, and the first PDCP entity, the first RLC entity, the second RLC entity, and the first MAC entity in the network device correspond to the first PDCP entity, the first RLC entity, the second RLC entity, and the first MAC entity in a terminal device corresponding to the target bearer, respectively.

Correspondingly, in S220, the network device reconfigures at least one of the first PDCP entity, the first RLC entity, the second RLC entity, and the first MAC entity in the network device. Specifically, if the network device carries the parameter configuration information in the configuration information, the network device configures at least one entity of a first PDCP entity, a first RLC entity, a second RLC entity, and a first MAC entity in the network device according to the parameter configuration information. If the network device judges that the key corresponding to the target bearer is not changed, the network device reconstructs the first PDCP entity, the first MAC entity and the second MAC entity in the network device and resets the first MAC entity in the network device.

Example nine: conversion from MCG Bearer or SCG Bearer to Duplicate Bearer

In S210, the first Bearer type is MCG Bearer or SCG Bearer, the second Bearer type is Duplicate Bearer, and it is assumed that the target Bearer corresponds to the first PDCP entity, the first RLC entity, and the first MAC entity in the network device, and the first PDCP entity, the first RLC entity, and the first MAC entity in the network device correspond to the first PDCP entity, the first RLC entity, and the first MAC entity in the terminal device corresponding to the target Bearer, respectively.

Correspondingly, in S220, if the network device determines that the key corresponding to the target bearer is not changed, the network device establishes a second RLC entity corresponding to the target bearer and establishes a logical channel corresponding to the second RLC entity. If the network equipment judges that the key corresponding to the target bearer changes, the network equipment rebuilds a first PDCP entity and a first RLC entity in the network equipment, establishes a second RLC entity corresponding to the target bearer in the network equipment, establishes a logical channel corresponding to the second RLC entity, and resets a first MAC entity in the network equipment.

Example ten: conversion from Split beer to Duplicate beer

In S210, the first Bearer type is Split Bearer, the second Bearer type is Duplicate Bearer, and it is assumed that the target Bearer corresponds to a first PDCP entity, a first RLC entity, a first MAC entity, and a second MAC entity in the network device, and the first PDCP entity, the first RLC entity, the first MAC entity, and the second MAC entity in the network device correspond to the first PDCP entity, the first RLC entity, the first MAC entity, and the second MAC entity in the terminal device corresponding to the target Bearer, respectively. The configuration information further includes third indication information, and the third indication information indicates that the first RLC entity in the terminal equipment needs to change the cell group.

Correspondingly, in S220, if the network device determines that the key corresponding to the target Bearer is not changed, the network device reconstructs the first RLC entity in the network device, releases the configuration that the Bearer type corresponding to the first MAC entity in the network device is Split Bearer, and configures the corresponding relationship between the reconstructed first RLC entity in the network device and the second MAC entity in the network device. If the network device judges that the key corresponding to the target Bearer is changed, the network device reconstructs a first PDCP entity, a first RLC entity and a second RLC entity in the network device, resets the first MAC entity and the second MAC entity in the network device, releases the configuration that the Bearer type corresponding to the reconstructed first MAC entity in the network device is Split Bearer, and then configures the corresponding relationship between the reconstructed first RLC entity and the reconstructed second MAC entity in the network device.

Optionally, as an example, after the network device reconstructs the first RLC entity in the network device, the network device determines whether a logical channel number corresponding to the reconstructed first RLC entity changes, and if the network device determines that the logical channel corresponding to the reconstructed first RLC entity in the network device changes, the network device further needs to reconfigure the logical channel corresponding to the reconstructed first RLC entity in the network device. If the network device determines that the logical channel corresponding to the reconstructed first RLC entity in the network device does not change, the network device does not need to reconfigure the logical channel corresponding to the reconstructed first RLC entity in the network device.

Optionally, as another example, the network device instructs, through the third indication information, the terminal device to release the configuration that the Bearer type corresponding to the first MAC entity in the terminal device is Split Bearer.

It can be seen from the foregoing embodiments that, in the method for bearer type conversion according to the present application, the network device implements direct conversion of different bearer types by controlling behaviors of different protocol layer entities according to configuration information sent to the terminal device, so that signaling overhead of a communication system can be reduced, and loss of data packets can be avoided.

The method for bearer type conversion according to the embodiment of the present application is described above with reference to fig. 4 and 5. A terminal device according to an embodiment of the present application will be described in detail below with reference to fig. 6.

Fig. 6 shows a schematic structural diagram of a terminal device according to an embodiment of the present application. As shown in fig. 6, the terminal device 10 includes:

the transceiver module 11 is configured to receive configuration information sent by a network device, where the configuration information includes an identifier ID of a target bearer and conversion mode indication information, the bearer type of the target bearer is a first bearer type, and the conversion mode indication information is used to indicate a second bearer type.

A processing module 12, configured to transform the bearer type of the target bearer from the first bearer type to the second bearer type according to the configuration information, where at least one of the first bearer type and the second bearer type is a duplicate bearer, and when the first bearer type and the second bearer type are both duplicate bearers, the first bearer type is a master cell group duplicate bearer and the second bearer type is a secondary cell group duplicate bearer, or the first bearer type is a secondary cell group duplicate bearer and the second bearer type is a master cell group duplicate bearer.

According to the terminal device of the embodiment of the application, the configuration information sent by the network device is received, and the bearer type of the target bearer is converted into the bearer type indicated by the conversion mode indication information according to the identifier of the target bearer in the configuration information and the bearer type indicated by the conversion mode indication information. Therefore, the terminal equipment does not need to delete the target bearer and then establish the bearer with the bearer type indicated by the conversion mode indication information, so that the signaling overhead of a communication system can be reduced, and the loss of data packets can be avoided.

Optionally, as an embodiment, the processing module 12 is further configured to: judging whether the key corresponding to the target bearer is changed;

wherein, in the aspect that the bearer type of the target bearer is converted from the first bearer type to the second bearer type according to the configuration information, the processing module 12 is specifically configured to:

and converting the bearer type of the target bearer from the first bearer type to the second bearer type according to the judgment result and the configuration information.

Optionally, as an embodiment, the first bearer type is a duplicate bearer, the second bearer type is a master cell group bearer or a secondary cell group bearer, the target bearer corresponds to a first PDCP entity, a first RLC entity, a second RLC entity, and a first MAC entity in the terminal device, the configuration information further includes first indication information, and the first indication information is used to indicate that the first RLC entity needs to be released;

wherein the processing module 12 is specifically configured to:

if the key corresponding to the target bearer is not changed, the first RLC entity is reestablished, and the reestablished first RLC entity and the logic channel corresponding to the reestablished first RLC entity are released;

if the key corresponding to the target bearer is changed, the first PDCP entity, the first RLC entity and the second RLC entity are re-established, the re-established first RLC entity and the logical channel corresponding to the re-established first RLC entity are released, and the first MAC entity is reset.

Optionally, as an embodiment, the first indication information includes: the number of the first RLC entity, and/or the logical channel number corresponding to the first RLC entity.

Optionally, as an embodiment, the first bearer type is a duplicate bearer, the second bearer type is a separate bearer, the target bearer corresponds to a first PDCP entity, a first RLC entity, a second RLC entity, and a first MAC entity in the terminal device, and the configuration information further includes second indication information, where the second indication information is used to indicate that the first RLC entity needs to change a cell group;

wherein the processing module 12 is specifically configured to:

if the key corresponding to the target bearer is not changed, reconstructing the first RLC entity, acquiring a second MAC entity of which the corresponding bearer type is a separated bearer, and configuring the corresponding relationship between the reconstructed first RLC entity and the second MAC entity;

if the key corresponding to the target bearer is changed, reconstructing the first PDCP entity, the first RLC entity and the second RLC entity, resetting the first MAC entity, acquiring the second MAC entity with the corresponding bearer type being a separate bearer, and reconfiguring the corresponding relationship between the reconstructed first RLC entity and the second MAC entity.

Optionally, as an embodiment, after re-establishing the first RLC entity, the processing module 12 is further configured to:

judging whether the serial number of the logic channel corresponding to the reconstructed first RLC entity changes or not;

if the logic channel corresponding to the reconstructed first RLC entity changes, the logic channel corresponding to the reconstructed first RLC entity is reconfigured.

Optionally, as an embodiment, the processing module 12 is specifically configured to: judging whether the terminal equipment has an MAC entity with a corresponding bearer type of a separated bearer; if the corresponding bearer type in the terminal equipment is the MAC entity of the separated bearer, acquiring the MAC entity as a second MAC entity; and if the corresponding bearing type of the MAC entity which is the separated bearing does not exist in the terminal equipment, establishing the MAC entity of which the corresponding bearing type is the separated bearing as a second MAC entity.

Optionally, as an embodiment, the second indication information includes: the number of the first RLC entity, and/or the logical channel number corresponding to the first RLC entity.

Optionally, as an embodiment, the first bearer type is a master cell group replication bearer and the second bearer type is a secondary cell group replication bearer, or the first bearer type is a secondary cell group replication bearer and the second bearer type is a master cell group replication bearer, and the target bearer corresponds to a first PDCP entity, a first RLC entity, a second RLC entity, and a first MAC entity in the corresponding terminal device;

wherein the processing module 12 is specifically configured to:

if the key corresponding to the target bearer is not changed, reconfiguring at least one of the first PDCP entity, the first RLC entity, the second RLC entity and the first MAC entity;

if the key corresponding to the target bearer is changed, re-establishing that the first PDCP entity, the first RLC entity and the second RLC entity are entities, and re-establishing the first MAC entity.

Optionally, as an embodiment, the configuration information further includes parameter configuration information;

wherein the processing module 12 is specifically configured to:

and reconfiguring at least one of the first PDCP entity, the first RLC entity, the second RLC entity and the first MAC entity according to the parameter configuration information.

Optionally, as an embodiment, the first bearer type is a master cell group bearer or a secondary cell group bearer, the second bearer type is a duplicate bearer, and the target bearer corresponds to a first PDCP entity, a first RLC entity, and a first MAC entity in the terminal device;

wherein the processing module 12 is specifically configured to:

if the key corresponding to the target bearer is not changed, establishing a second RLC entity corresponding to the target bearer, and establishing a logical channel corresponding to the second RLC entity;

if the key corresponding to the target bearer is changed, the first PDCP entity and the first RLC entity are rebuilt, a second RLC entity corresponding to the target bearer is established, a logic channel corresponding to the second RLC entity is established, and the first MAC entity is reset.

Optionally, as an embodiment, the first bearer type is a separate bearer, the second bearer type is a duplicate bearer, the target bearer corresponds to a first PDCP entity, a first RLC entity, a second RLC entity, a first MAC entity, and a second MAC entity in the terminal device, the first RLC entity corresponds to the first MAC entity, the second RLC entity corresponds to the second MAC entity, the configuration information further includes third indication information, and the third indication information is used to indicate that the first RLC entity needs to change a cell group;

wherein the processing module 12 is specifically configured to:

if the key corresponding to the target bearer is not changed, reconstructing the first RLC entity, releasing the corresponding bearer type in the first MAC entity as a separate bearer configuration, and configuring the corresponding relationship between the reconstructed first RLC entity and the second MAC entity;

if the key corresponding to the target bearer is changed, reconstructing the first PDCP entity, the first RLC entity and the second RLC entity, resetting the first MAC entity and the second MAC entity, releasing the bearer type corresponding to the reset first MAC entity to be a configuration of separated bearer, and configuring a corresponding relationship between the reconstructed first RLC entity and the reset second MAC entity.

judging whether the logic channel number corresponding to the reconstructed first RLC entity changes or not;

if the number of the logic channel corresponding to the reconstructed first RLC entity changes, the logic channel corresponding to the reconstructed first RLC entity is reconfigured.

Optionally, as an embodiment, the third indication information is further used to indicate that the bearer type corresponding to the first MAC entity is released as a configuration of a separate bearer.

The terminal device according to the embodiment of the present application may refer to the flow corresponding to the method 100 of the embodiment of the present application, and each unit/module and the other operations and/or functions in the terminal device are respectively for implementing the corresponding flow in the method 100, and for brevity, no further description is provided here.

Fig. 7 is a schematic structural diagram of a network device according to an embodiment of the present application. As shown in fig. 7, the network device 20 includes:

the transceiver module 21 is configured to send configuration information to a terminal device, where the configuration information includes an identifier ID of a target bearer and conversion mode indication information, the bearer type of the target bearer is a first bearer type, and the conversion mode indication information is used to indicate a second bearer type.

A processing module 22, configured to transform the type of the target bearer from the first bearer type to the second bearer type according to the configuration information, where at least one of the first bearer type and the second bearer type is a duplicate bearer, and when the first bearer type and the second bearer type are both duplicate bearers, the first bearer type is a master cell group duplicate bearer and the second bearer type is a secondary cell group duplicate bearer, or the first bearer type is a secondary cell group duplicate bearer and the second bearer type is a master cell group duplicate bearer.

According to the network device of the embodiment of the application, the configuration information is sent to the terminal device, and the bearer type of the target bearer is converted into the bearer type indicated by the conversion mode indication information according to the identifier of the target bearer in the configuration information and the bearer type indicated by the conversion mode indication information. Therefore, the network equipment does not need to delete the target bearer and then establish the bearer with the bearer type indicated by the conversion mode indication information, so that the signaling overhead of a communication system can be reduced, and the loss of data packets can be avoided.

Optionally, as an embodiment, the processing module 22 is further configured to: judging whether the key corresponding to the target bearer is changed;

wherein, in the aspect that the bearer type of the target bearer is converted from the first bearer type to the second bearer type according to the configuration information, the processing module 22 is specifically configured to: and converting the bearer type of the target bearer from the first bearer type to the second bearer type according to the judgment result and the configuration information.

Optionally, as an embodiment, the first bearer type is a duplicate bearer, the second bearer type is a master cell group bearer or a secondary cell group bearer, the target bearer corresponds to a first PDCP entity, a first RLC entity, a second RLC entity, and a first MAC entity in the network device, the first PDCP entity, the first RLC entity, the second RLC entity, and the first MAC entity in the network device respectively correspond to the first PDCP entity, the first RLC entity, the second RLC entity, and the first MAC entity in the terminal device corresponding to the target bearer, and the configuration information further includes first indication information, where the first indication information is used to indicate that the first RLC entity in the terminal device needs to be released;

wherein the processing module 22 is specifically configured to:

if the key corresponding to the target bearer is not changed, reconstructing a first RLC entity in the network equipment, releasing the reconstructed first RLC entity in the network equipment and a logical channel corresponding to the reconstructed first RLC entity in the network equipment;

if the key corresponding to the target bearer is changed, reconstructing a first PDCP entity in the network device, a first RLC entity in the network device, and a second RLC entity in the network device, releasing the reconstructed first RLC entity in the network device and a logical channel corresponding to the reconstructed first RLC entity in the network device, and resetting the first MAC entity in the network device.

Optionally, as an embodiment, the first indication information includes: the number of the first RLC entity in the terminal device, and/or the logical channel number corresponding to the first RLC entity in the terminal device.

Optionally, as an embodiment, the first bearer type is a duplicate bearer, the second bearer type is a separate bearer, the target bearer corresponds to a first PDCP entity, a first RLC entity, a second RLC entity, and a first MAC entity in the network device, the first PDCP entity, the first RLC entity, the second RLC entity, and the first MAC entity in the network device respectively correspond to the first PDCP entity, the first RLC entity, the second RLC entity, and the first MAC entity in the terminal device corresponding to the target bearer, the configuration information further includes second indication information, and the second indication information is used to indicate that the first RLC entity in the terminal device needs to change a cell group;

wherein the processing module 22 is specifically configured to:

if the key corresponding to the target bearer is not changed, reconstructing a first RLC entity in the network equipment, configuring a function of a second MAC entity in the network equipment, enabling the bearer type corresponding to the second MAC entity to be a separate bearer, and configuring a corresponding relationship between the reconstructed first RLC entity in the network equipment and the second MAC entity in the network equipment;

if the key corresponding to the target bearer is changed, reconstructing a first PDCP entity in the network device, a first RLC entity in the network device, and a second RLC entity in the network device, resetting the first MAC entity in the network device, and configuring a function of the second MAC entity in the network device, so that the bearer type corresponding to the second MAC entity is a separate bearer, and reconfiguring a correspondence between the reconstructed first RLC entity in the network device and the second MAC entity in the network device.

Optionally, as an embodiment, after re-establishing the first RLC entity in the network device, the processing module 22 is further configured to:

judging whether a logic channel number corresponding to the reconstructed first RLC entity in the network equipment changes or not;

if the logic channel number corresponding to the reconstructed first RLC entity in the network equipment changes, reconfiguring the logic channel corresponding to the reconstructed first RLC entity in the network equipment.

Optionally, as an embodiment, before configuring the function of the second MAC entity in the network device, the processing module 22 is further configured to: and determining that the corresponding bearer type does not exist in the terminal equipment as the MAC entity of the separated bearer.

Optionally, as an embodiment, the second indication information includes: the number of the first RLC entity in the terminal device, and/or the logical channel number corresponding to the first RLC entity in the terminal device.

Optionally, as an embodiment, the first bearer type is a master cell group duplicate bearer and the second bearer type is a secondary cell group duplicate bearer, or the first bearer type is a secondary cell duplicate bearer and the second bearer type is a master cell duplicate bearer, the target bearer corresponds to a first PDCP entity, a first RLC entity, a second RLC entity, and a first MAC entity in the network device, and the first PDCP entity, the first RLC entity, the second RLC entity, and the first MAC entity in the network device correspond to the first PDCP entity, the first RLC entity, the second RLC entity, and the first MAC entity in the terminal device corresponding to the target bearer, respectively;

wherein the processing module 22 is specifically configured to:

if the key corresponding to the target bearer is not changed, reconfiguring at least one of a first PDCP entity in the network equipment, a first RLC entity in the network equipment, a second RLC entity in the network equipment and a first MAC entity in the network equipment;

if the key corresponding to the target bearer is changed, reestablishing that a first PDCP entity in the network equipment, a first RLC entity in the network equipment and a second RLC entity in the network equipment are entities, and resetting a first MAC entity in the network equipment.

wherein the processing module 22 is specifically configured to: and reconfiguring at least one of the first PDCP entity in the network equipment, the first RLC entity in the network equipment, the second RLC entity in the network equipment and the first MAC entity in the network equipment according to the parameter configuration information.

Optionally, as an embodiment, the first bearer type is a master cell group bearer or a secondary cell group bearer, the second bearer type is a duplicate bearer, the target bearer corresponds to a first PDCP entity, a first RLC entity, and a first MAC entity in the network device, and the first PDCP entity, the first RLC entity, and the first MAC entity in the network device correspond to the first PDCP entity, the first RLC entity, and the first MAC entity in the terminal device corresponding to the target bearer, respectively;

wherein the processing module 22 is specifically configured to:

if the key corresponding to the target bearer is not changed, establishing a second RLC entity corresponding to the target bearer in the network equipment, and establishing a logical channel corresponding to the second RLC entity;

if the key corresponding to the target bearer is changed, reconstructing a first PDCP entity in the network device and a first RLC entity in the network device, establishing a second RLC entity corresponding to the target bearer in the network device, establishing a logical channel corresponding to the second RLC entity, and resetting the first MAC entity in the network device.

Optionally, as an embodiment, the first bearer type is a split bearer, the second bearer type is a duplicate bearer, the target bearer corresponds to a first PDCP entity, a first RLC entity, a second RLC entity, a first MAC entity and a second MAC entity in the network device, the first PDCP entity, the first RLC entity, the second RLC entity, the first MAC entity and the second MAC entity in the network equipment respectively correspond to the first PDCP entity, the first RLC entity, the second RLC entity, the first MAC entity and the second MAC entity in the terminal equipment corresponding to the target bearer, a first RLC entity in the network device corresponds to a first MAC entity in the network device, the second RLC entity in the network device corresponds to a second MAC entity in the network device, the configuration information further includes third indication information, where the third indication information is used to indicate that a first RLC entity in the terminal device needs to change a cell group;

wherein the processing module 22 is specifically configured to:

if the key corresponding to the target bearer is not changed, reconstructing a first RLC entity in the network equipment, releasing the configuration that the bearer type corresponding to a first MAC entity in the network equipment is a separate bearer, and configuring the corresponding relationship between the reconstructed first RLC entity in the network equipment and a second MAC entity in the network equipment;

if the key corresponding to the target bearer is changed, reconstructing a first PDCP entity in the network device, a first RLC entity in the network device, and a second RLC entity in the network device, resetting the first MAC entity in the network device and the second MAC entity in the network device, releasing the configuration that the bearer type corresponding to the first MAC entity after the reconfiguration in the network device is a separate bearer, and configuring a corresponding relationship between the first RLC entity after the reconfiguration in the network device and the second MAC entity after the reconfiguration in the network device.

judging whether the number of the logic channel corresponding to the reconstructed first RLC entity in the network equipment changes or not;

if the number of the logic channel corresponding to the reconstructed first RLC entity in the network equipment changes, reconfiguring the logic channel corresponding to the reconstructed first RLC entity in the network equipment.

Optionally, as an embodiment, the third indication information is further used to indicate that the bearer type corresponding to the first MAC entity in the terminal device is released to be a configuration of a separate bearer.

The network device according to the embodiment of the present application may refer to the flow corresponding to the method 200 of the embodiment of the present application, and each unit/module and the other operations and/or functions in the network device are respectively for implementing the corresponding flow in the method 200, and are not described herein again for brevity.

Fig. 8 shows a schematic structural diagram of a terminal device according to another embodiment of the present application. As shown in fig. 8, the terminal device 100 includes a processor 110 and a memory 120. Wherein the memory 120 stores therein a bearer type transformation program operable on the processor 110, the bearer type transformation program, when executed by the processor 110, causing the processor 110 to:

The terminal device 100 according to the embodiment of the present application may refer to the terminal device 10 corresponding to the embodiment of the present application, and each unit/module and the other operations and/or functions in the terminal device are respectively for implementing a corresponding flow in the method 100, and for brevity, no further description is provided here.

Fig. 9 is a schematic structural diagram of a network device according to another embodiment of the present application, and as shown in fig. 9, the network device 200 includes: a processor 210 and a memory 220. Wherein the memory 220 stores therein a bearer type transformation program operable on the processor 210, the bearer type transformation program, when executed by the processor 210, causing the processor 210 to:

The network device 200 according to the embodiment of the present application may refer to the network device 20 corresponding to the embodiment of the present application, and each unit/module and the other operations and/or functions in the network device are respectively for implementing a corresponding flow in the method 200, and are not described herein again for brevity.

It should be understood that the processor of the embodiments of the present application may be an integrated circuit chip having signal processing capabilities. In implementation, the steps of the above method embodiments may be performed by integrated logic circuits of hardware in a processor or instructions in the form of software. The Processor may be a general purpose Processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), an off-the-shelf Programmable Gate Array (FPGA) or other Programmable logic device, discrete Gate or transistor logic device, or discrete hardware components. The various methods, steps and logic blocks disclosed in the embodiments of the present invention may be implemented or performed. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of the method disclosed in connection with the embodiments of the present invention may be directly implemented by a hardware decoding processor, or implemented by a combination of hardware and software modules in the decoding processor. The software module may be located in ram, flash memory, rom, prom, or eprom, registers, etc. storage media as is well known in the art. The storage medium is located in a memory, and a processor reads information in the memory and completes the steps of the method in combination with hardware of the processor.

It will be appreciated that the memory in embodiments of the invention may be either volatile memory or nonvolatile memory, or may include both volatile and nonvolatile memory. The non-volatile Memory may be a Read-Only Memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an Electrically Erasable PROM (EEPROM), or a flash Memory. Volatile Memory can be Random Access Memory (RAM), which acts as external cache Memory. By way of example, but not limitation, many forms of RAM are available, such as Static random access memory (Static RAM, SRAM), Dynamic Random Access Memory (DRAM), Synchronous Dynamic random access memory (Synchronous DRAM, SDRAM), Double Data Rate Synchronous Dynamic random access memory (DDR SDRAM), Enhanced Synchronous SDRAM (ESDRAM), Synchronous Link SDRAM (SLDRAM), and Direct Rambus RAM (DR RAM). It should be noted that the memory of the systems and methods described herein is intended to comprise, without being limited to, these and any other suitable types of memory.

The embodiment of the present application further provides a computer program product including instructions, and when a computer executes the instructions of the computer program product, the computer executes the method for bearer type transformation of the above method embodiment. In particular, the computer program product may be run on the terminal device and the network device described above.

Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.

In the several embodiments provided in the present application, it should be understood that the disclosed system, apparatus and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.

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

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

The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application or portions thereof that substantially contribute to the prior art may be embodied in the form of a software product stored in a storage medium and including instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: various media capable of storing program codes, such as a usb disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk.

The above description is only for the specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present application, and shall be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

1. A method for bearer type transformation, the method being performed by a terminal device, the method comprising:

according to the configuration information, the bearer type of the target bearer is converted from the first bearer type to the second bearer type, and at least one of the first bearer type and the second bearer type is a duplicate bearer;

the method further comprises the following steps:

judging whether the key corresponding to the target bearer is changed;

wherein the transforming the bearer type of the target bearer from the first bearer type to the second bearer type according to the configuration information comprises:

according to the judgment result and the configuration information, converting the bearing type of the target bearing from the first bearing type into the second bearing type;

wherein:

the first bearer type is a duplicate bearer, the second bearer type is a master cell group bearer or a secondary cell group bearer, the target bearer corresponds to a first PDCP entity, a first RLC entity, a second RLC entity and a first MAC entity in the terminal device, the configuration information further includes first indication information, and the first indication information is used for indicating that the first RLC entity needs to be released; wherein the converting the bearer type of the target bearer from the first bearer type to the second bearer type according to the result of the determining and the configuration information includes: if the key corresponding to the target bearer is not changed, the first RLC entity is reestablished, and the reestablished first RLC entity and the logic channel corresponding to the reestablished first RLC entity are released; and/or the presence of a gas in the gas,

the first bearer type is a duplicate bearer, the second bearer type is a separate bearer, the target bearer corresponds to a first PDCP entity, a first RLC entity, a second RLC entity and a first MAC entity in the terminal device, the configuration information further includes second indication information, and the second indication information is used for indicating that the first RLC entity needs to change a cell group; wherein the converting the type of the target bearer from the first bearer type to the second bearer type according to the result of the determining and the configuration information includes: if the key corresponding to the target bearer is not changed, reconstructing the first RLC entity, acquiring a second MAC entity of which the corresponding bearer type is a separated bearer, and configuring the corresponding relationship between the reconstructed first RLC entity and the second MAC entity; and/or the presence of a gas in the gas,

the first bearer type is a master cell group replication bearer and the second bearer type is a secondary cell group replication bearer, or the first bearer type is a secondary cell group replication bearer and the second bearer type is a master cell group replication bearer, and the target bearer corresponds to a first PDCP entity, a first RLC entity, a second RLC entity and a first MAC entity in the terminal equipment; wherein the converting the type of the target bearer from the first bearer type to the second bearer type according to the result of the determining and the configuration information includes: if the key corresponding to the target bearer is not changed, reconfiguring at least one of the first PDCP entity, the first RLC entity, the second RLC entity and the first MAC entity; and/or the presence of a gas in the gas,

the first bearing type is a main cell group bearing or an auxiliary cell group bearing, the second bearing type is a copy bearing, and the target bearing corresponds to a first PDCP entity, a first RLC entity and a first MAC entity in the terminal equipment; wherein the converting the type of the target bearer from the first bearer type to the second bearer type according to the result of the determining and the configuration information includes: if the key corresponding to the target bearer is not changed, establishing a second RLC entity corresponding to the target bearer, and establishing a logical channel corresponding to the second RLC entity; and/or the presence of a gas in the gas,

the first bearer type is a separate bearer, the second bearer type is a duplicate bearer, the target bearer corresponds to a first PDCP entity, a first RLC entity, a second RLC entity, a first MAC entity and a second MAC entity in the terminal device, the first RLC entity corresponds to the first MAC entity, the second RLC entity corresponds to the second MAC entity, the configuration information further includes third indication information, and the third indication information is used for indicating that the first RLC entity needs to change a cell group; wherein the converting the type of the target bearer from the first bearer type to the second bearer type according to the result of the determining and the configuration information includes: if the key corresponding to the target bearer is not changed, the first RLC entity is reestablished, the configuration that the corresponding bearer type in the first MAC entity is a separated bearer is released, and the corresponding relationship between the reestablished first RLC entity and the second MAC entity is configured.

2. The method of claim 1, wherein if the first bearer type is a duplicate bearer, the second bearer type is a primary cell group bearer or a secondary cell group bearer, the target bearer corresponds to a first PDCP entity, a first RLC entity, a second RLC entity, and a first MAC entity in the terminal device, the configuration information further includes first indication information, and the first indication information is used to indicate that the first RLC entity needs to be released, the method, according to the result of the determination and the configuration information, converts the bearer type of the target bearer from the first bearer type to the second bearer type, further comprising:

if the key corresponding to the target bearer is changed, re-establishing the first PDCP entity, the first RLC entity and the second RLC entity,

releasing the reconstructed first RLC entity and the logical channel corresponding to the reconstructed first RLC entity,

resetting the first MAC entity.

3. The method of claim 2, wherein the first indication information comprises:

the number of the first RLC entity,

and/or a logical channel number corresponding to the first RLC entity.

4. The method of claim 1, wherein if the first bearer type is a duplicate bearer and the second bearer type is a separate bearer, and the target bearer corresponds to a first PDCP entity, a first RLC entity, a second RLC entity, and a first MAC entity in the terminal device, and the configuration information further includes second indication information, where the second indication information is used to indicate that the first RLC entity needs to change a cell group, the converting the type of the target bearer from the first bearer type to the second bearer type according to a result of the determining and the configuration information, further comprising:

resetting the first MAC entity and obtaining a second MAC entity with the corresponding bearer type being a separate bearer,

and reconfiguring the corresponding relation between the reconstructed first RLC entity and the second MAC entity.

5. The method of claim 4, wherein after re-establishing the first RLC entity, the method further comprises:

6. The method according to claim 4 or 5, wherein the obtaining the second MAC entity with the corresponding bearer type being a split bearer comprises:

judging whether the terminal equipment has an MAC entity with a corresponding bearer type of a separated bearer;

if the corresponding bearer type in the terminal equipment is the MAC entity of the separated bearer, acquiring the MAC entity as a second MAC entity;

and if the corresponding bearer type is not the MAC entity of the separated bearer in the terminal equipment, establishing the MAC entity of the separated bearer as the second MAC entity.

7. The method according to claim 4 or 5, wherein the second indication information comprises:

the number of the first RLC entity,

and/or a logical channel number corresponding to the first RLC entity.

8. The method of claim 1, wherein if the first bearer type is a primary cell group replication bearer and the second bearer type is a secondary cell group replication bearer, or the first bearer type is a secondary cell group replication bearer and the second bearer type is a primary cell group replication bearer, and the target bearer corresponds to a first PDCP entity, a first RLC entity, a second RLC entity, and a first MAC entity in the terminal device, the transforming the type of the target bearer from the first bearer type to the second bearer type according to the result of the determination and the configuration information, further comprising:

9. The method according to claim 8, wherein the configuration information further includes parameter configuration information;

wherein the reconfiguring at least one of the first PDCP entity, the first RLC entity, the second RLC entity, and the first MAC entity comprises:

10. The method of claim 1, wherein if the first bearer type is a primary cell group bearer or a secondary cell group bearer, the second bearer type is a duplicate bearer, and the target bearer corresponds to a first PDCP entity, a first RLC entity, and a first MAC entity in the terminal device, the converting the type of the target bearer from the first bearer type to the second bearer type according to the determination result and the configuration information further comprises:

if the key corresponding to the target bearer is changed, re-establishing the first PDCP entity and the first RLC entity,

establishing a second RLC entity corresponding to the target bearer and establishing a logical channel corresponding to the second RLC entity,

resetting the first MAC entity.

11. The method of claim 1, wherein if the first bearer type is a split bearer, the second bearer type is a duplicate bearer, the target bearer corresponds to a first PDCP entity, a first RLC entity, a second RLC entity, a first MAC entity, and a second MAC entity in the terminal device, the first RLC entity corresponds to the first MAC entity, the second RLC entity corresponds to the second MAC entity, the configuration information further includes third indication information, and the third indication information is used to indicate that the first RLC entity needs to change a cell group, then the type of the target bearer is converted from the first bearer type to the second bearer type according to a result of the determination and the configuration information, further comprising:

if the key corresponding to the target bearer is changed, reconstructing the first PDCP entity, the first RLC entity and the second RLC entity, resetting the first MAC entity and the second MAC entity, releasing the bearer type corresponding to the reset first MAC entity as a configuration of separated bearer, and configuring a corresponding relationship between the reconstructed first RLC entity and the reset second MAC entity.

12. The method of claim 11, wherein after re-establishing the first RLC entity, the method further comprises:

13. The method according to claim 11 or 12, wherein the third indication information is further used to indicate that the configuration that the corresponding bearer type in the first MAC entity is a split bearer is released.

14. A method for bearer type transformation, the method being performed by a network device, the method comprising:

according to the configuration information, converting the type of the target bearer from the first bearer type to the second bearer type, wherein at least one of the first bearer type and the second bearer type is a duplicate bearer;

the method further comprises the following steps:

judging whether the key corresponding to the target bearer is changed;

wherein:

the first bearer type is a duplicate bearer, the second bearer type is a master cell group bearer or a secondary cell group bearer, the target bearer corresponds to a first PDCP entity, a first RLC entity, a second RLC entity and a first MAC entity in the network device, the first PDCP entity, the first RLC entity, the second RLC entity and the first MAC entity in the network device respectively correspond to the first PDCP entity, the first RLC entity, the second RLC entity and the first MAC entity in the terminal device corresponding to the target bearer, the configuration information further includes first indication information, and the first indication information is used for indicating that the first RLC entity in the terminal device needs to be released; wherein the converting the bearer type of the target bearer from the first bearer type to the second bearer type according to the result of the determining and the configuration information includes: if the key corresponding to the target bearer is not changed, reconstructing a first RLC entity in the network equipment, releasing the reconstructed first RLC entity in the network equipment and a logical channel corresponding to the reconstructed first RLC entity in the network equipment; and/or the presence of a gas in the gas,

the first bearer type is a duplicate bearer, the second bearer type is a separate bearer, the target bearer corresponds to a first PDCP entity, a first RLC entity, a second RLC entity and a first MAC entity in the network device, the first PDCP entity, the first RLC entity, the second RLC entity and the first MAC entity in the network device respectively correspond to the first PDCP entity, the first RLC entity, the second RLC entity and the first MAC entity in the terminal device corresponding to the target bearer, the configuration information further includes second indication information, and the second indication information is used for indicating that the first RLC entity in the terminal device needs to change a cell group; wherein the converting the type of the target bearer from the first bearer type to the second bearer type according to the result of the determining and the configuration information includes: if the key corresponding to the target bearer is not changed, reconstructing a first RLC entity in the network equipment, configuring a function of a second MAC entity in the network equipment, enabling the bearer type corresponding to the second MAC entity to be a separate bearer, and configuring a corresponding relationship between the reconstructed first RLC entity in the network equipment and the second MAC entity in the network equipment; and/or the presence of a gas in the gas,

the first bearer type is a master cell group replication bearer and the second bearer type is a secondary cell group replication bearer, or the first bearer type is a secondary cell replication bearer and the second bearer type is a master cell replication bearer, the target bearer corresponds to a first PDCP entity, a first RLC entity, a second RLC entity and a first MAC entity in the network device, and the first PDCP entity, the first RLC entity, the second RLC entity and the first MAC entity in the network device correspond to the first PDCP entity, the first RLC entity, the second RLC entity and the first MAC entity in the terminal device corresponding to the target bearer, respectively; wherein the converting the type of the target bearer from the first bearer type to the second bearer type according to the result of the determining and the configuration information includes: if the key corresponding to the target bearer is not changed, reconfiguring at least one of a first PDCP entity in the network equipment, a first RLC entity in the network equipment, a second RLC entity in the network equipment and a first MAC entity in the network equipment; and/or the presence of a gas in the gas,

the first bearer type is a master cell group bearer or an auxiliary cell group bearer, the second bearer type is a duplicate bearer, the target bearer corresponds to a first PDCP entity, a first RLC entity and a first MAC entity in the network device, and the first PDCP entity, the first RLC entity and the first MAC entity in the network device correspond to the first PDCP entity, the first RLC entity and the first MAC entity in the terminal device corresponding to the target bearer, respectively; wherein the converting the type of the target bearer from the first bearer type to the second bearer type according to the result of the determining and the configuration information includes: if the key corresponding to the target bearer is not changed, establishing a second RLC entity corresponding to the target bearer in the network equipment, and establishing a logical channel corresponding to the second RLC entity; and/or the presence of a gas in the gas,

the first bearer type is a separate bearer, the second bearer type is a duplicate bearer, the target bearer corresponds to a first PDCP entity, a first RLC entity, a second RLC entity, a first MAC entity and a second MAC entity in the network device, the first PDCP entity, the first RLC entity, the second RLC entity, the first MAC entity and the second MAC entity in the network equipment respectively correspond to the first PDCP entity, the first RLC entity, the second RLC entity, the first MAC entity and the second MAC entity in the terminal equipment corresponding to the target bearer, a first RLC entity in the network device corresponds to a first MAC entity in the network device, the second RLC entity in the network device corresponds to a second MAC entity in the network device, the configuration information further includes third indication information, where the third indication information is used to indicate that a first RLC entity in the terminal device needs to change a cell group; wherein the converting the type of the target bearer from the first bearer type to the second bearer type according to the result of the determining and the configuration information includes: if the key corresponding to the target bearer is not changed, reconstructing a first RLC entity in the network equipment, releasing the configuration that the bearer type corresponding to the first MAC entity in the network equipment is a separate bearer, and configuring the corresponding relationship between the reconstructed first RLC entity in the network equipment and a second MAC entity in the network equipment.

15. The method according to claim 14, wherein if the first bearer type is a duplicate bearer, the second bearer type is a primary cell group bearer or a secondary cell group bearer, the target bearer corresponds to a first PDCP entity, a first RLC entity, a second RLC entity, and a first MAC entity in the network device, the first PDCP entity, the first RLC entity, the second RLC entity, and the first MAC entity in the network device respectively correspond to the first PDCP entity, the first RLC entity, the second RLC entity, and the first MAC entity in the terminal device corresponding to the target bearer, and the configuration information further includes first indication information, where the first indication information is used to indicate that the first RLC entity in the terminal device needs to be released; then, the transforming the bearer type of the target bearer from the first bearer type to the second bearer type according to the result of the determination and the configuration information further includes:

if the key corresponding to the target bearer is changed, reconstructing a first PDCP entity in the network device, a first RLC entity in the network device, and a second RLC entity in the network device, and releasing the reconstructed first RLC entity in the network device and a logical channel corresponding to the reconstructed first RLC entity in the network device, and resetting the first MAC entity in the network device.

16. The method of claim 15, wherein the first indication information comprises:

the number of the first RLC entity in the terminal device,

and/or a logical channel number corresponding to a first RLC entity in the terminal equipment.

17. The method according to claim 14, wherein if the first bearer type is a duplicate bearer, the second bearer type is a separate bearer, the target bearer corresponds to a first PDCP entity, a first RLC entity, a second RLC entity, and a first MAC entity in the network device, the first PDCP entity, the first RLC entity, the second RLC entity, and the first MAC entity in the network device respectively correspond to the first PDCP entity, the first RLC entity, the second RLC entity, and the first MAC entity in the terminal device corresponding to the target bearer, and the configuration information further includes second indication information, where the second indication information is used to indicate that the first RLC entity in the terminal device needs to change a cell group; then, the converting the type of the target bearer from the first bearer type to the second bearer type according to the result of the determination and the configuration information further includes:

18. The method of claim 17, wherein after re-establishing the first RLC entity in the network device, the method further comprises:

19. The method according to claim 17 or 18, wherein prior to configuring the functionality of the second MAC entity in the network device, the method further comprises:

and determining that the corresponding bearer type does not exist in the terminal equipment as the MAC entity of the separated bearer.

20. The method according to claim 17 or 18, wherein the second indication information comprises:

the number of the first RLC entity in the terminal device,

21. The method of claim 14, wherein if the first bearer type is a master cell group replication bearer and the second bearer type is a secondary cell group replication bearer or the first bearer type is a secondary cell replication bearer and the second bearer type is a master cell replication bearer, the target bearer corresponds to a first PDCP entity, a first RLC entity, a second RLC entity, and a first MAC entity in the network device, and the first PDCP entity, the first RLC entity, the second RLC entity, and the first MAC entity in the network device correspond to the first PDCP entity, the first RLC entity, the second RLC entity, and the first MAC entity in the terminal device corresponding to the target bearer, respectively, the type of the target bearer is transformed from the first bearer type to the second bearer type according to the result of the determination and the configuration information, further comprising:

22. The method of claim 21, wherein the configuration information further comprises parameter configuration information;

wherein the reconfiguring at least one of the first PDCP entity in the network device, the first RLC entity in the network device, the second RLC entity in the network device, and the first MAC entity in the network device comprises:

and reconfiguring at least one of the first PDCP entity in the network equipment, the first RLC entity in the network equipment, the second RLC entity in the network equipment and the first MAC entity in the network equipment according to the parameter configuration information.

23. The method of claim 14, wherein if the first bearer type is a master cell group bearer or a secondary cell group bearer, the second bearer type is a duplicate bearer, the target bearer corresponds to a first PDCP entity, a first RLC entity, and a first MAC entity in the network device, and the first PDCP entity, the first RLC entity, and the first MAC entity in the network device respectively correspond to the first PDCP entity, the first RLC entity, and the first MAC entity in the terminal device corresponding to the target bearer, the converting the type of the target bearer from the first bearer type to the second bearer type according to the result of the determination and the configuration information, further comprising:

24. The method of claim 14, wherein if the first bearer type is a split bearer, the second bearer type is a duplicate bearer, the target bearer corresponds to a first PDCP entity, a first RLC entity, a second RLC entity, a first MAC entity and a second MAC entity in the network device, the first PDCP entity, the first RLC entity, the second RLC entity, the first MAC entity and the second MAC entity in the network device correspond to the first PDCP entity, the first RLC entity, the second RLC entity, the first MAC entity and the second MAC entity in the terminal device corresponding to the target bearer, respectively, the first RLC entity in the network device corresponds to the first MAC entity in the network device, the second RLC entity in the network device corresponds to the second MAC entity in the network device, and third indication information is further included in the configuration information, the third indication information is used to indicate that the first RLC entity in the terminal equipment needs to change the cell group, and then the method converts the type of the target bearer from the first bearer type to the second bearer type according to the result of the determination and the configuration information, further includes:

if the key corresponding to the target bearer is changed, re-establishing a first PDCP entity in the network device, a first RLC entity in the network device, and a second RLC entity in the network device, re-establishing a first MAC entity in the network device and a second MAC entity in the network device, releasing a configuration that a bearer type corresponding to the re-established first MAC entity in the network device is a separate bearer, and configuring a corresponding relationship between the re-established first RLC entity in the network device and the re-established second MAC entity in the network device.

25. The method of claim 24, wherein after re-establishing the first RLC entity in the network device, the method further comprises:

if the logic channel corresponding to the reconstructed first RLC entity in the network equipment changes, the logic channel corresponding to the reconstructed first RLC entity in the network equipment is reconfigured.

26. The method according to claim 24 or 25, wherein the third indication information is further used to indicate that the configuration that the bearer type corresponding to the first MAC entity in the terminal device is a split bearer is released.

27. A terminal device, comprising:

a processing module, configured to transform the bearer type of the target bearer from the first bearer type to the second bearer type according to the configuration information, where at least one of the first bearer type and the second bearer type is a duplicate bearer;

the processing module is further configured to:

judging whether the key corresponding to the target bearer is changed;

wherein, in the aspect that the bearer type of the target bearer is converted from the first bearer type to the second bearer type according to the configuration information, the processing module is specifically configured to:

wherein:

the first bearer type is a duplicate bearer, the second bearer type is a master cell group bearer or a secondary cell group bearer, the target bearer corresponds to a first PDCP entity, a first RLC entity, a second RLC entity and a first MAC entity in the terminal device, the configuration information further includes first indication information, and the first indication information is used for indicating that the first RLC entity needs to be released; wherein the processing module is specifically configured to: if the key corresponding to the target bearer is not changed, the first RLC entity is reestablished, and the reestablished first RLC entity and the logic channel corresponding to the reestablished first RLC entity are released; and/or the presence of a gas in the gas,

the first bearer type is a duplicate bearer, the second bearer type is a separate bearer, the target bearer corresponds to a first PDCP entity, a first RLC entity, a second RLC entity and a first MAC entity in the terminal device, the configuration information further includes second indication information, and the second indication information is used for indicating that the first RLC entity needs to change a cell group; wherein the processing module is specifically configured to: if the key corresponding to the target bearer is not changed, reconstructing the first RLC entity, acquiring a second MAC entity of which the corresponding bearer type is a separated bearer, and configuring the corresponding relationship between the reconstructed first RLC entity and the second MAC entity; and/or the presence of a gas in the gas,

the first bearer type is a master cell group replication bearer and the second bearer type is a secondary cell group replication bearer, or the first bearer type is a secondary cell group replication bearer and the second bearer type is a master cell group replication bearer, and the target bearer corresponds to a first PDCP entity, a first RLC entity, a second RLC entity and a first MAC entity in the terminal equipment; wherein the processing module is specifically configured to: if the key corresponding to the target bearer is not changed, reconfiguring at least one of the first PDCP entity, the first RLC entity, the second RLC entity and the first MAC entity; and/or the presence of a gas in the gas,

the first bearing type is a main cell group bearing or an auxiliary cell group bearing, the second bearing type is a copy bearing, and the target bearing corresponds to a first PDCP entity, a first RLC entity and a first MAC entity in the terminal equipment; wherein the processing module is specifically configured to: if the key corresponding to the target bearer is not changed, establishing a second RLC entity corresponding to the target bearer, and establishing a logical channel corresponding to the second RLC entity; and/or the presence of a gas in the gas,

the first bearer type is a separate bearer, the second bearer type is a duplicate bearer, the target bearer corresponds to a first PDCP entity, a first RLC entity, a second RLC entity, a first MAC entity and a second MAC entity in the terminal device, the first RLC entity corresponds to the first MAC entity, the second RLC entity corresponds to the second MAC entity, the configuration information further includes third indication information, and the third indication information is used for indicating that the first RLC entity needs to change a cell group; wherein the processing module is specifically configured to: if the key corresponding to the target bearer is not changed, the first RLC entity is reestablished, the configuration that the corresponding bearer type in the first MAC entity is a separated bearer is released, and the corresponding relationship between the reestablished first RLC entity and the second MAC entity is configured.

28. The terminal device of claim 27, wherein if the first bearer type is a duplicate bearer, the second bearer type is a primary cell group bearer or a secondary cell group bearer, the target bearer corresponds to a first PDCP entity, a first RLC entity, a second RLC entity, and a first MAC entity in the terminal device, the configuration information further includes first indication information, and the first indication information is used to indicate that the first RLC entity needs to be released, the processing module is further specifically configured to:

29. The terminal device of claim 28, wherein the first indication information comprises:

the number of the first RLC entity,

and/or a logical channel number corresponding to the first RLC entity.

30. The terminal device of claim 27, wherein if the first bearer type is a duplicate bearer, the second bearer type is a separate bearer, the target bearer corresponds to a first PDCP entity, a first RLC entity, a second RLC entity, and a first MAC entity in the terminal device, the configuration information further includes second indication information, and the second indication information is used to indicate that the first RLC entity needs to change a cell group, the processing module is further specifically configured to:

31. The terminal device of claim 30, wherein after re-establishing the first RLC entity, the processing module is further configured to:

32. The terminal device according to claim 30 or 31, wherein the processing module is specifically configured to:

and if the corresponding bearing type of the MAC entity which is the separated bearing does not exist in the terminal equipment, establishing the MAC entity of which the corresponding bearing type is the separated bearing as a second MAC entity.

33. The terminal device according to claim 30 or 31, wherein the second indication information comprises:

the number of the first RLC entity,

and/or a logical channel number corresponding to the first RLC entity.

34. The terminal device of claim 27, wherein if the first bearer type is a master cell group replication bearer and the second bearer type is a secondary cell group replication bearer, or the first bearer type is a secondary cell group replication bearer and the second bearer type is a master cell group replication bearer, and the target bearer corresponds to a first PDCP entity, a first RLC entity, a second RLC entity, and a first MAC entity in the terminal device, the processing module is further specifically configured to:

35. The terminal device according to claim 34, wherein the configuration information further includes parameter configuration information;

wherein the processing module is specifically configured to:

36. The terminal device of claim 27, wherein if the first bearer type is a master cell group bearer or a secondary cell group bearer, the second bearer type is a duplicate bearer, and the target bearer corresponds to a first PDCP entity, a first RLC entity, and a first MAC entity in the terminal device, the processing module is further specifically configured to:

37. The terminal device of claim 27, wherein if the first bearer type is a split bearer, the second bearer type is a duplicate bearer, the target bearer corresponds to a first PDCP entity, a first RLC entity, a second RLC entity, a first MAC entity, and a second MAC entity in the terminal device, the first RLC entity corresponds to the first MAC entity, the second RLC entity corresponds to the second MAC entity, the configuration information further includes third indication information, and the third indication information is used to indicate that the first RLC entity needs to change a cell group, the processing module is further specifically configured to:

if the key corresponding to the target bearer is changed, reconstructing the first PDCP entity, the first RLC entity and the second RLC entity, resetting the first MAC entity and the second MAC entity, releasing the configuration that the bearer type corresponding to the reset first MAC entity is a separate bearer, and configuring a corresponding relationship between the reconstructed first RLC entity and the reset second MAC entity.

38. The terminal device of claim 37, wherein after re-establishing the first RLC entity, the processing module is further configured to:

39. The terminal device according to claim 37 or 38, wherein the third indication information is further used to indicate that the configuration that the bearer type corresponding to the first MAC entity is a split bearer is released.

40. A network device, comprising:

a processing module, configured to transform the type of the target bearer from the first bearer type to the second bearer type according to the configuration information, where at least one of the first bearer type and the second bearer type is a duplicate bearer;

the processing module is further configured to:

judging whether the key corresponding to the target bearer is changed;

wherein:

the first bearer type is a duplicate bearer, the second bearer type is a master cell group bearer or a secondary cell group bearer, the target bearer corresponds to a first PDCP entity, a first RLC entity, a second RLC entity and a first MAC entity in the network device, the first PDCP entity, the first RLC entity, the second RLC entity and the first MAC entity in the network device respectively correspond to the first PDCP entity, the first RLC entity, the second RLC entity and the first MAC entity in the terminal device corresponding to the target bearer, the configuration information further includes first indication information, and the first indication information is used for indicating that the first RLC entity in the terminal device needs to be released; wherein the processing module is specifically configured to: if the key corresponding to the target bearer is not changed, reconstructing a first RLC entity in the network equipment, releasing the reconstructed first RLC entity in the network equipment and a logical channel corresponding to the reconstructed first RLC entity in the network equipment; and/or the presence of a gas in the gas,

the first bearer type is a duplicate bearer, the second bearer type is a separate bearer, the target bearer corresponds to a first PDCP entity, a first RLC entity, a second RLC entity and a first MAC entity in the network device, the first PDCP entity, the first RLC entity, the second RLC entity and the first MAC entity in the network device respectively correspond to the first PDCP entity, the first RLC entity, the second RLC entity and the first MAC entity in the terminal device corresponding to the target bearer, the configuration information further includes second indication information, and the second indication information is used for indicating that the first RLC entity in the terminal device needs to change a cell group; wherein the processing module is specifically configured to: if the key corresponding to the target bearer is not changed, reconstructing a first RLC entity in the network equipment, configuring a function of a second MAC entity in the network equipment, enabling the bearer type corresponding to the second MAC entity to be a separate bearer, and configuring a corresponding relationship between the reconstructed first RLC entity in the network equipment and the second MAC entity in the network equipment; and/or the presence of a gas in the gas,

the first bearer type is a master cell group replication bearer and the second bearer type is a secondary cell group replication bearer, or the first bearer type is a secondary cell replication bearer and the second bearer type is a master cell replication bearer, the target bearer corresponds to a first PDCP entity, a first RLC entity, a second RLC entity and a first MAC entity in the network device, and the first PDCP entity, the first RLC entity, the second RLC entity and the first MAC entity in the network device correspond to the first PDCP entity, the first RLC entity, the second RLC entity and the first MAC entity in the terminal device corresponding to the target bearer, respectively; wherein the processing module is specifically configured to: if the key corresponding to the target bearer is not changed, reconfiguring at least one of a first PDCP entity in the network equipment, a first RLC entity in the network equipment, a second RLC entity in the network equipment and a first MAC entity in the network equipment; and/or the presence of a gas in the gas,

the first bearer type is a master cell group bearer or an auxiliary cell group bearer, the second bearer type is a duplicate bearer, the target bearer corresponds to a first PDCP entity, a first RLC entity and a first MAC entity in the network device, and the first PDCP entity, the first RLC entity and the first MAC entity in the network device correspond to the first PDCP entity, the first RLC entity and the first MAC entity in the terminal device corresponding to the target bearer, respectively; wherein the processing module is specifically configured to: if the key corresponding to the target bearer is not changed, establishing a second RLC entity corresponding to the target bearer in the network equipment, and establishing a logical channel corresponding to the second RLC entity; and/or the presence of a gas in the gas,

the first bearer type is a separate bearer, the second bearer type is a duplicate bearer, the target bearer corresponds to a first PDCP entity, a first RLC entity, a second RLC entity, a first MAC entity and a second MAC entity in the network device, the first PDCP entity, the first RLC entity, the second RLC entity, the first MAC entity and the second MAC entity in the network equipment respectively correspond to the first PDCP entity, the first RLC entity, the second RLC entity, the first MAC entity and the second MAC entity in the terminal equipment corresponding to the target bearer, a first RLC entity in the network device corresponds to a first MAC entity in the network device, the second RLC entity in the network device corresponds to a second MAC entity in the network device, the configuration information further includes third indication information, where the third indication information is used to indicate that a first RLC entity in the terminal device needs to change a cell group;

wherein the processing module is specifically configured to: if the key corresponding to the target bearer is not changed, reconstructing a first RLC entity in the network equipment, releasing the configuration that the bearer type corresponding to the first MAC entity in the network equipment is a separate bearer, and configuring the corresponding relationship between the reconstructed first RLC entity in the network equipment and a second MAC entity in the network equipment.

41. The network device according to claim 40, wherein if the first bearer type is a duplicate bearer, the second bearer type is a master cell group bearer or a secondary cell group bearer, the target bearer corresponds to a first PDCP entity, a first RLC entity, a second RLC entity, and a first MAC entity in the network device, the first PDCP entity, the first RLC entity, the second RLC entity, and the first MAC entity in the network device correspond to the first PDCP entity, the first RLC entity, the second RLC entity, and the first MAC entity in the terminal device corresponding to the target bearer, respectively, the configuration information further includes first indication information, and the first indication information is used to indicate that the first RLC entity in the terminal device needs to be released, the processing module is further specifically configured to:

42. The network device of claim 41, wherein the first indication information comprises:

the number of the first RLC entity in the terminal device,

43. The network device of claim 40, wherein if the first bearer type is a duplicate bearer, the second bearer type is a separate bearer, the target bearer corresponds to a first PDCP entity, a first RLC entity, a second RLC entity, and a first MAC entity in the network device, the first PDCP entity, the first RLC entity, the second RLC entity, and the first MAC entity in the network device respectively correspond to the first PDCP entity, the first RLC entity, the second RLC entity, and the first MAC entity in the terminal device corresponding to the target bearer, the configuration information further includes second indication information, and the second indication information is used to indicate that the first RLC entity in the terminal device needs to change a cell group, then the processing module is further specifically configured to:

if the key corresponding to the target bearer is changed, reconstructing a first PDCP entity in the network device, a first RLC entity in the network device, and a second RLC entity in the network device, and reconfiguring a first MAC entity in the network device, and configuring a function of the second MAC entity in the network device, so that the bearer type corresponding to the second MAC entity is a separate bearer, and reconfiguring a correspondence between the reconstructed first RLC entity in the network device and the second MAC entity in the network device.

44. The network device of claim 43, wherein after re-establishing the first RLC entity in the network device, the processing module is further configured to:

45. The network device of claim 43 or 44, wherein before configuring the functionality of the second MAC entity in the network device, the processing module is further configured to:

46. The network device of claim 43 or 44, wherein the second indication information comprises:

the number of the first RLC entity in the terminal device,

47. The network device of claim 40, wherein if the first bearer type is a master cell group replication bearer and the second bearer type is a secondary cell group replication bearer, or the first bearer type is a secondary cell replication bearer and the second bearer type is a master cell replication bearer, the target bearer corresponds to a first PDCP entity, a first RLC entity, a second RLC entity, and a first MAC entity in the network device, and the first PDCP entity, the first RLC entity, the second RLC entity, and the first MAC entity in the network device correspond to the first PDCP entity, the first RLC entity, the second RLC entity, and the first MAC entity in the terminal device corresponding to the target bearer, respectively, the processing module is further specifically configured to:

48. The network device of claim 47, wherein the configuration information further comprises parameter configuration information;

wherein the processing module is specifically configured to:

49. The network device of claim 40, wherein if the first bearer type is a master cell group bearer or a secondary cell group bearer, the second bearer type is a duplicate bearer, the target bearer corresponds to a first PDCP entity, a first RLC entity, and a first MAC entity in the network device, and the first PDCP entity, the first RLC entity, and the first MAC entity in the network device correspond to the first PDCP entity, the first RLC entity, and the first MAC entity in the terminal device corresponding to the target bearer, respectively, the processing module is further specifically configured to:

50. The network device of claim 40, wherein if the first bearer type is a separate bearer, the second bearer type is a duplicate bearer, the target bearer corresponds to a first PDCP entity, a first RLC entity, a second RLC entity, a first MAC entity and a second MAC entity in the network device, the first PDCP entity, the first RLC entity, the second RLC entity, the first MAC entity and the second MAC entity in the network device respectively correspond to the first PDCP entity, the first RLC entity, the second RLC entity, the first MAC entity and the second MAC entity in the terminal device corresponding to the target bearer, the first RLC entity in the network device corresponds to the first MAC entity in the network device, the second RLC entity in the network device corresponds to the second MAC entity in the network device, and the configuration information further includes third indication information, the third indication information is used to indicate that the first RLC entity in the terminal device needs to change the cell group, and the processing module is further specifically configured to:

if the key corresponding to the target bearer is changed, reconstructing a first PDCP entity in the network equipment, a first RLC entity in the network equipment and a second RLC entity in the network equipment,

resetting a first MAC entity in the network equipment and a second MAC entity in the network equipment, releasing the configuration that the corresponding bearing type in the reset first MAC entity in the network equipment is separated bearing, and configuring the corresponding relation between the reset first RLC entity in the network equipment and the reset second MAC entity in the network equipment.

51. The network device of claim 50, wherein after re-establishing the first RLC entity in the network device, the processing module is further configured to:

52. The network device according to claim 50 or 51, wherein the third indication information is further used to indicate that the configuration that the bearer type corresponding to the first MAC entity in the terminal device is a split bearer is released.

53. A terminal device, comprising: memory, processor and a bearer type transformation program stored on the memory and executable on the processor, which when executed by the processor implements the steps of the method of bearer type transformation according to any of claims 1 to 13.

54. A network device, comprising: memory, processor and a bearer type transformation program stored on the memory and executable on the processor, which when executed by the processor implements the steps of the method of bearer type transformation according to any of claims 14 to 26.

55. A computer-readable medium, characterized in that the computer-readable medium has stored thereon a bearer type transformation program which, when executed by a processor, implements the steps of the method of bearer type transformation according to any one of claims 1 to 13.

56. A computer-readable medium, characterized in that the computer-readable medium has stored thereon a bearer type transformation program which, when executed by a processor, implements the steps of the method of bearer type transformation according to any one of claims 14 to 26.