CN111586711B

CN111586711B - Communication method and communication device in multi-air-interface connection

Info

Publication number: CN111586711B
Application number: CN201910117960.9A
Authority: CN
Inventors: 彭文杰; 王瑞; 仇力炜
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2019-02-15
Filing date: 2019-02-15
Publication date: 2022-04-12
Anticipated expiration: 2039-02-15
Also published as: CN111586711A

Abstract

The application provides a communication method in multi-air-interface dual-connection MR-DC, the primary node sends the original data radio bearer DRB identification ID and one or more candidate DRB IDs of a first bearer to the secondary node, the secondary node selects one from the one or more candidate DRB IDs as a new DRB ID, and the secondary node sends the new DRB ID to the primary node, so that the process of changing the DRB ID can be simplified, and the modification of the bearer can be completed.

Description

Communication method and communication device in multi-air-interface connection

Technical Field

The present application relates to the field of wireless communication technologies, and in particular, to a communication method and apparatus in a multi-air interface connection.

Background

To increase the throughput of data transmission, dual connectivity support is introduced. For example: Multi-Radio Dual Connectivity (MR-DC).

Fig. 1 is a schematic diagram of a dual-connection communication system. As shown in fig. 1, the terminal 21 may simultaneously communicate with a Master Node (MN) 01 and a Secondary Node (SN) 11, MN01 and SN11 may be connected, and both the master node a and the secondary node B may be connected to a core network element 31. The access technologies employed by MN01 and SN11 may be the same or different.

The MR-DC may specifically include the following scenarios:

1. evolved Universal Terrestrial Radio Access (E-UTRA) and New Radio Access (NR) Dual Connectivity (E-UTRA-NR Dual Connectivity, EN-DC)

Fig. 2 is a schematic diagram of an EN-DC scenario, as shown in fig. 2, a core network element 31 is an Evolved Packet Core (EPC) element, MN01 is an evolved node b (eNB), and SN11 is a new radio node b (gNB).

MN01 and SN11 can be connected through an X2 interface, and MN01 and SN11 can be connected through a user plane; the MN01 and the core network element 31 may be connected through an S1 interface, and the MN01 and the core network element 31 may have a user plane connection therebetween; the SN11 and the core network element 31 can be connected through an S1-U interface, and the SN11 core network element 31 can have a user plane connection.

2. Next Generation (NG) Radio Access Network (RAN) E-UTRA and NR Dual Connectivity (NG-RAN E-UTRA-NR Dual Connectivity, NGEN-DC)

Fig. 3 is a schematic diagram of an NGEN-DC scenario, and as shown in fig. 3, the core network element 31 is a fifth Generation (5G, 5th Generation) core network (5G core, 5GC) element, MN01 is an eNB, and SN11 is a gNB.

MN01 and SN11 can be connected through Xn interface, MN01 and SN11 can have user interface connection; the MN01 and the core network element 31 can be connected through an NG interface, and the MN01 and the core network element 31 can be connected through a user plane; the SN11 and the core network element 31 can be connected through an NG-U interface, and the SN11 and the core network element 31 can have a user plane connection.

3. Double ligation of NR and E-UTRA (NR-E-UTRA Dual Connectivity, NE-DC)

Fig. 4 is a schematic diagram of an NE-DC scenario, and as shown in fig. 4, the core network element 31 is a 5GC network element, MN01 is a gNB, and SN11 is an eNB.

MN01 and SN11 may be connected, for example, via an Xn interface, with a user plane connection between MN01 and SN 11; MN01 may be connected to the core network element 31, for example, through an NG interface, MN01 may have a user plane connection with the core network element 31; the SN11 and the core network element 31 may be connected, for example via a NG-U interface, and there may be a user plane connection between the SN11 and the core network element 31.

4. Double connection of NR to NR (NR-NR Dual Connectivity, NR-DC)

Fig. 5 is a schematic diagram of an NR-DC scenario, as shown in fig. 5, the core network element 31 is a 5GC network element, MN01 is a gNB, and SN11 is a gNB.

In MR-DC, how to modify the bearer configuration for the terminal 21 is an urgent problem to be solved.

Disclosure of Invention

The embodiment of the application provides a communication method, a device and a system in multi-air-interface dual-connection MR-DC, which can modify the configuration of a bearer.

In a first aspect, an embodiment of the present application provides a communication method in a multi-air-interface dual-connection MR-DC, where the method may be applied to a secondary node or a chip in the secondary node, and the method includes: receiving a DRB identification ID and one or more candidate DRB IDs of an original data radio bearer of a first bearer from a master node; and sending the new DRB ID of the first bearer to the master node, wherein the new DRB ID is one of the one or more candidate DRB IDs.

One or more candidate DRB IDs are sent to the auxiliary node by the main node, so that the auxiliary node can conveniently replace the DRB IDs according to the requirement of the auxiliary node, and further the configuration of the bearer can be modified.

Optionally, the one or more candidate DRB IDs are candidate DRB IDs of the first bearer; or the one or more candidate DRB IDs are candidate DRB IDs of a plurality of bearers, the plurality of bearers including the first bearer.

Optionally, the method further includes sending an evolved universal terrestrial radio access bearer E-RAB ID of the first bearer or the original DRB of the first bearer to the primary node.

Optionally, the method further includes determining the new DRB ID of the first bearer when the PDCP SN length of the first bearer changes.

Optionally, the method further includes generating first configuration information of the first bearer, where the first configuration information of the first bearer includes configuration information of release of a PDCP entity corresponding to the original DRB ID and configuration information of addition of the PDCP entity corresponding to the new DRB ID, and sending the first configuration information of the first bearer to the main node.

Optionally, the first configuration information of the first bearer further includes added configuration information of the SCG RLC entity corresponding to the new DRB ID.

Optionally, the method further includes determining the new DRB ID of the first bearer when the PDCP anchor of the first bearer changes and the PDCP SN length of the first bearer does not change.

Optionally, the method further includes generating first configuration information of the first bearer, where the first configuration information of the first bearer includes re-established configuration information of the PDCP entity; and sending the first configuration information of the first bearer to the master node.

Optionally, the re-established configuration information of the PDCP entity includes the new DRB ID of the first bearer and the original DRB ID of the first bearer.

In a second aspect, the present application provides a communication method in multi-air-interface dual-connection MR-DC, where the method may be applied to a master node or a chip in the master node, and the method includes: sending the original data radio bearer DRB identification ID and one or more candidate DRB IDs of a first bearer to a secondary node; receiving a new DRB ID of the first bearer from the secondary node, the new DRB ID being one of the one or more candidate DRB IDs.

Optionally, the one or more candidate DRB IDs are candidate DRB IDs of the first bearer; or

The one or more candidate DRB IDs are candidate DRB IDs for a plurality of bearers, the plurality of bearers including the first bearer.

Optionally, the method further includes:

receiving an evolved universal terrestrial radio access bearer (E-RAB) ID of the first bearer or the original DRB of the first bearer from the secondary node.

Optionally, the method further includes: receiving first configuration information of the first bearer from the secondary node, where the first configuration information of the first bearer includes released configuration information of a PDCP entity corresponding to the original DRB ID and added configuration information of a PDCP entity corresponding to the new DRB ID.

Optionally, the method further includes: receiving first configuration information of the first bearer from the secondary node, the first configuration information of the first bearer including re-established configuration information of a PDCP entity.

Optionally, the method further includes: and sending the first configuration information of the first bearer to a terminal.

Optionally, the method further includes: generating second configuration information of the first bearer, where the second configuration information of the first bearer includes configuration information of release of an MCG RLC entity corresponding to the original DRB ID and configuration information of addition of an MCG RLC entity corresponding to the new DRB ID, or the second configuration information of the first bearer includes configuration information of release of an MCG RLC entity corresponding to the original DRB ID.

Optionally, the method further includes: and the main node sends the second configuration information of the first bearer to a terminal.

In a third aspect, the embodiment of the present application provides a communication method in a multi-air-interface dual-connection MR-DC, which may be applied to a first CU or a chip in the first CU, where the first CU may be a CU in a secondary node.

The method includes the first CU receiving an original DRB ID and one or more candidate DRB IDs of a first bearer from a second CU; the first CU sends the new DRB ID of the first bearer to the second CU, the new DRB ID of the first bearer being one of the one or more candidate DRB IDs.

Alternatively, the second CU may be a CU in the master node.

Optionally, the method further includes: the first CU sends the new DRB ID of the first bearer to the first DU.

Optionally, the method further includes: the first CU sends the E-RAB ID of the first bearer to the second CU, and the first CU sends the E-RAB ID of the first bearer to the first DU; or the first CU sends the original DRB of the first bearer to the second CU, and the first CU sends the original DRB of the first bearer to the first DU.

Optionally, the first CU may generate configuration information of the PDCP of the first bearer, for example, configuration information of a release of the PDCP entity corresponding to the original DRB ID and configuration information of an addition of the PDCP entity corresponding to the new DRB ID, or configuration information of a re-establishment of the PDCP entity.

In a fourth aspect, the present application provides a communication method in a multi-air-interface dual-connection MR-DC, which may be applied to a first CU or a chip in the first CU, where the first CU may be a CU in a master node, and a second CU may be a CU in a slave node. The method comprises the following steps:

the first CU sends the original DRB ID and one or more candidate DRB IDs of the first bearer to the second CU;

the first CU receives a new DRB ID of the first bearer from the second CU, the new DRB ID of the first bearer being one of the one or more candidate DRB IDs.

Optionally, the method further includes: the first CU receiving the E-RAB ID of the first bearer from the second CU;

the first CU receiving the E-RAB ID of the first bearer from the first DU; or

The first CU receiving the original DRB of the first bearer from the second CU;

the first CU receives the original DRB of the first bearer from the first DU.

In a fifth aspect, the present application provides a communication method in a multi-air-interface dual-connection MR-DC, which may be applied in a first DU or a chip in the first DU, where the first DU may be a DU in an auxiliary node.

The method comprises the following steps: a new DRB ID for the first bearer is received from the first CU. The first CU may be a CU connected to a first DU, the secondary node comprising the first CU and the first DU.

Optionally, the method further includes: an E-RAB ID or an original DRB of the first bearer is received from the first CU.

Optionally, the method further includes: and generating configuration information of the SCG RLC and/or SCG logical channel of the first bearer, for example, added configuration information of the SCG RLC entity corresponding to the new DRB ID.

In a sixth aspect, an embodiment of the present application provides a communication method in a multi-air-interface dual-connection MR-DC, which may be applied in a first DU or a chip in the first DU, where the first DU may be a DU in a master node.

The method comprises the following steps: a new DRB ID for the first bearer is received from the first CU. The first CU may be a CU connected to a first DU, the master node comprising the first CU and the first DU.

Optionally, the method further includes: generating configuration information of the SCG RLC and/or SCG logical channel of the first bearer, for example, the configuration information of the release of the MCG RLC entity corresponding to the original DRB ID and the configuration information of the addition of the MCG RLC entity corresponding to the new DRB ID, or the second configuration information of the first bearer includes the configuration information of the release of the MCG RLC entity corresponding to the original DRB ID.

In a seventh aspect, an embodiment of the present application provides a communication method in a multi-air-interface dual-connection MR-DC, where the method may be applied to a master node, a chip in the master node, a slave node, or a chip in the slave node.

The method comprises the following steps: determining a new DRB ID of the first bearer, the DRB ID of the first bearer being an original DRB ID before the secondary node determines the new DRB ID of the first bearer; and sending the configuration information of the PDCP reestablishment of the first bearer to the terminal, wherein the configuration information of the PDCP reestablishment comprises the new DRB ID and the original DRB ID.

Optionally, determining the new DRB ID of the first bearer may include generating a new DRB ID by itself, or selecting a candidate DRB ID as the new DRB ID according to candidate DRB IDs received from other nodes, or receiving the new DRB ID of the first bearer from other nodes.

Optionally, when the method is executed by the secondary node or a chip in the secondary node, the configuration information for PDCP reestablishment of the first bearer is sent to the terminal, where the configuration information for PDCP reestablishment of the first bearer is sent by the secondary node to the terminal through an air interface, or the configuration information for PDCP reestablishment of the first bearer is sent by the secondary node to the primary node, and then is sent to the terminal by the primary node.

In an eighth aspect, the present application provides a communication method in a multi-air-interface dual-connection MR-DC, which can be applied to a terminal or a chip in the terminal.

The method comprises the following steps: and receiving configuration information for PDCP reconstruction of the first bearer, wherein the configuration information for PDCP reconstruction comprises the new DRB ID and the original DRB ID, and associating the PDCP entity to the new DRB ID when reconstructing the PDCP entity.

Alternatively, it may be received from the primary node or from the secondary node.

In a ninth aspect, embodiments of the present application provide a communication apparatus. The communication device comprises a processor coupled with a memory for storing a computer program or instructions, the processor executing the computer program or instructions such that the method of any of the first to eighth aspects is performed, the communication device may further comprise the memory.

In a tenth aspect, an embodiment of the present application provides a communication apparatus, which includes one or more modules for implementing the method of any one of the first to seventh aspects, where the one or more modules may correspond to the steps of the method of any one of the first to eighth aspects.

In an eleventh aspect, embodiments of the present application provide a chip, where the chip includes a processor and an interface circuit, where the interface circuit is coupled to the processor, and the processor is configured to execute a computer program or instructions to implement the method according to any one of the first to eighth aspects, and the interface circuit is configured to communicate with other modules outside the chip.

In a twelfth aspect, an embodiment of the present application provides a computer storage medium storing a program for implementing the method of any one of the first to eighth aspects. The program, when run in a wireless communication apparatus, causes the wireless communication apparatus to perform the method of any of the first to seventh aspects.

In a thirteenth aspect, an embodiment of the present application provides a computer program product, which includes a program that, when executed, causes the method of any one of the first to eighth aspects to be performed.

Drawings

In order to illustrate the present application more clearly, the drawings that are needed in the description of the embodiments will be briefly described below, it being obvious that the drawings in the following description are only some embodiments of the invention, and that other drawings may be derived from these drawings by a person skilled in the art without inventive exercise.

FIG. 1 is a schematic diagram of a dual-connectivity communication system;

FIG. 2 is a schematic diagram of an EN-DC;

FIG. 3 is a schematic diagram of an NGEN-DC;

FIG. 4 is a schematic diagram of a NE-DC;

FIG. 5 is a schematic diagram of NR-DC

FIG. 6a is a schematic diagram of a protocol architecture for a network-side perspective;

FIG. 6b is a schematic diagram of a protocol architecture for a terminal side angle;

fig. 7a is a schematic structural diagram of an access network device;

fig. 7b is a schematic structural diagram of a terminal;

FIG. 7c is a diagram of a CU-DU structure with MN 01;

FIG. 7d is a diagram of an SN11 for CU-DU architecture;

FIG. 8 is a schematic diagram of an embodiment of changing DRB IDs;

FIG. 9 is a schematic diagram of an embodiment of changing DRB IDs;

FIG. 10 is a schematic diagram of an embodiment of changing DRB IDs;

FIG. 11 is a schematic diagram of an embodiment of changing DRB IDs;

fig. 12 is a diagram illustrating a structure of a communication apparatus 1200;

fig. 13 is a diagram illustrating a structure of a communication apparatus 1300;

fig. 14 is a schematic diagram of a structure of a communication device 1400.

Detailed Description

The technical solution in the present application will be described below with reference to the drawings in the present application.

The technical scheme of the embodiment of the application can be applied to the communication system shown in fig. 1. It should be noted that the core network element, the MN, the SN, and the terminal included in the communication system shown in fig. 1 are only an example, and the connection relationship between the core network element and the MN or the SN is also only an example, and in this embodiment of the present application, the type and the number of the network elements included in the communication system, and the connection relationship between the network elements are not limited thereto.

In MR-DC, from the perspective of the network side (MN01 and SN11), there may be following 6 types of user plane bearers, fig. 6a is a schematic diagram of a protocol architecture at the perspective of the network side, as shown in fig. 6a, the following behavior examples respectively describe the data flow direction of each bearer type, and those skilled in the art can understand that the uplink is similar to the downlink, and are not described herein again.

1. MN terminated Master Cell Group (MCG) bearers.

Data is transmitted from the core network element 31 to the MN01, and is sequentially transmitted to the terminal 21 through a Packet Data Convergence Protocol (PDCP) layer, a Radio Link Control (RLC) layer, and a Media Access Control (MAC) layer of the MN 01.

2. MN terminated Secondary Cell Group (SCG) bearers.

The data is transmitted from the network element 31 of the core network to the MN01, transmitted to the RLC layer of the SN11 through the PDCP layer of the MN01, and transmitted to the terminal 21 through the RLC layer of the SN11 and the MAC layer in turn.

3. MN terminated Split (Split) bearers.

Data is sent from the network element 31 of the core network to the MN01, the PDCP layer of the MN101 shunts the data, a part of the data is sent to the terminal 21 through the RLC layer and the MAC layer of the MN01 in sequence, and the other part of the data is sent to the RLC layer of the SN11 and sent to the terminal 21 through the RLC layer and the MAC layer of the SN11 in sequence.

4. SN terminated Split bearers.

Data is sent from the network element 31 of the core network to the SN11, the PDCP layer of the SN11 shunts the data, a part of the data is sent to the terminal 21 through the RLC layer and the MAC layer of the SN11 in sequence, and the other part of the data is sent to the RLC layer of the MN101 and sent to the terminal 21 through the RLC layer and the MAC layer of the MN101 in sequence.

5. SN terminated MCG bearers.

The data is sent from the network element 31 of the core network to the SN11, sent to the RLC layer of MN01 via the PDCP layer of SN11, and sent to the terminal 21 via the RLC layer and the MAC layer of MN 01.

6. SN terminated SCG bearers.

The data is sent from the network element 31 of the core network to the SN11, and then sent to the terminal 21 through the PDCP layer, the RLC layer and the MAC layer of the SN 11.

The MCG bearer relates to an MCG air interface resource, the SCG bearer relates to an SCG air interface resource, and the Split bearer relates to an MCG air interface resource and an SCG air interface resource.

Optionally, in the multiple bearer types, the PDCP entities of MN01 and SN11 may be NR PDCP entities, and in an MN-terminated MCG bearer under EN-DC, the PDCP entity of MN01 may also be E-UTRA PDCP. When the network element 31 of the core network is a 5GC network element, the PDCP layer of MN01 may have an SDAP layer, and data is sent from the network element 31 of the core network to MN01, and reaches the PDCP layer of MN01 via the SDAP layer of MN 01; the PDCP layer of SN11 may have an SDAP layer on it, and data is sent from the core network element 31 to the SN11, through the SDAP layer of SN11, to the PDCP layer of SN 11.

In MR-DC, from the perspective of the terminal 21, the bearer on the terminal has a PDCP entity, which may be a PDCP entity corresponding to MN or a PDCP entity corresponding to SN, an RLC entity, which may be an RLC entity corresponding to MN and/or an RLC entity corresponding to SN, and a MAC entity, which may be a MAC entity corresponding to MN and/or a MAC entity corresponding to SN.

The RLC entity corresponding to MN01 can be understood as an RLC entity associated with MN01 carried on the terminal 21, and for convenience of description, the RLC entity corresponding to MN01 can be referred to as an MCG RLC entity. MN01 may generate configuration information for the MCG RLC entity for terminal 21.

The MAC entity corresponding to MN01 may be understood as a MAC entity associated with MN01 carried on the terminal 21, and for convenience of description, the MAC entity corresponding to MN01 may be referred to as an MCG MAC entity. MN01 may generate configuration information for the MCG MAC entity for terminal 21. The configuration of the MCG MAC entity by the MN01 for the terminal 21 may be accomplished by configuring an MCG logical channel, which may be similarly understood as a logical channel corresponding to MN01, or a logical channel carried on the terminal 21 associated with MN 01. Alternatively, multiple bearers on the terminal 21 may share the same MAC entity, and in this case, the MAC entity associated with the MN01 carried on the terminal 21 may be understood as the MAC entity on the terminal 21.

The RLC entity corresponding to the SN11 may be understood as an RLC entity associated with the SN11 carried on the terminal 21, and for convenience of description, the RLC entity corresponding to the SN may be referred to as an SCG RLC entity. The SN11 may generate configuration information for the SCG RLC entity for the terminal 21.

The MAC entity corresponding to the SN11 may be understood as a MAC entity associated with the SN11 carried on the terminal 21, and for convenience of description, the MAC entity corresponding to the SN11 may be referred to as an SCG MAC entity. The SN11 may generate configuration information for the SCG MAC entity for the terminal 21. The configuration of the SCG MAC entity by the SN11 for the terminal 21 may be accomplished by configuring an SCG logical channel, and similarly, the SCG logical channel may be understood as a logical channel corresponding to the SN11, or a logical channel carried on the terminal 21 is associated with the SN 11.

Fig. 6b is a schematic diagram of a protocol architecture of a terminal side angle, and the following describes entities that 3 types of bearer terminals 21 have respectively:

1. MCG bearer

The MCG bearer on the terminal may have a PDCP entity, an MCG RLC entity, and an MCG MAC entity.

2. Split bearing

The split bearer on the terminal can have a PDCP entity, an MCG RLC entity, an MCG MAC entity, an SCG RLC entity, an SCG MAC entity.

3. Secondary Cell Group (SCG) bearer

The SCG bearer on the terminal may have a PDCP entity, an SCG RLC entity, and an SCG MAC entity.

It should be noted that, from the perspective of the terminal 21, since there is only one PDCP entity, the terminal 21 may not distinguish whether the PDCP entity is associated with the MN01 or the SN 11. Technically the terminal 21 can distinguish whether the PDCP entity is associated with MN01 or SN11 by using a key.

The following describes an apparatus or device in an embodiment of the present application.

Fig. 7a is a schematic structural diagram of an access network device. MN01 or SN11 may refer to the structure shown in fig. 7 a.

The access network equipment includes at least one processor 1511, at least one memory 1512, at least one transceiver 1513, at least one network interface 1514, and one or more antennas 1515. The processor 1511, memory 1512, transceiver 1513, and network interface 1514 are coupled, such as by a bus. The antenna 1515 is connected to the transceiver 1513. The network interface 1514 is used to connect the access network device to other communication devices via a communication link, for example the access network device to the core network element 101 via an S1 interface. In the embodiment of the present application, the connection may include various interfaces, transmission lines, buses, and the like, which is not limited in this embodiment.

The memory 1512, which may be separate, is coupled to the processor 1511. Optionally, the memory 1512 may also be integrated with the processor 1511, for example, within a chip. The memory 1512 can store program codes for executing the technical solutions of the embodiments of the present application, and the processor 1511 controls execution of the program codes, and the executed computer program codes may also be regarded as drivers of the processor 1511. For example, the processor 1511 is configured to execute the computer program code stored in the memory 1512, so as to implement the technical solution in the embodiment of the present application.

A transceiver 1513 may be used to support the reception or transmission of radio frequency signals between the access network device and the terminal, and the transceiver 1513 may be coupled to an antenna 1515. The transceiver 1513 includes a transmitter Tx and a receiver Rx. Specifically, one or more antennas 1515 may receive radio frequency signals, and the receiver Rx of the transceiver 1513 is configured to receive the radio frequency signals from the antennas, convert the radio frequency signals into digital baseband signals or digital intermediate frequency signals, and provide the digital baseband signals or digital intermediate frequency signals to the processor 1511, so that the processor 1511 performs further processing on the digital baseband signals or digital intermediate frequency signals, such as demodulation processing and decoding processing. In addition, the transmitter Tx in the transceiver 1513 is also used to receive a modulated digital baseband signal or a digital intermediate frequency signal from the processor 1511, convert the modulated digital baseband signal or the digital intermediate frequency signal into a radio frequency signal, and transmit the radio frequency signal through the one or more antennas 1515. Specifically, the receiver Rx may selectively perform one or more stages of down-mixing and analog-to-digital conversion processes on the rf signal to obtain a digital baseband signal or a digital intermediate frequency signal, wherein the order of the down-mixing and analog-to-digital conversion processes is adjustable. The transmitter Tx may selectively perform one or more stages of up-mixing and digital-to-analog conversion processes on the modulated digital baseband signal or the modulated digital intermediate frequency signal to obtain the rf signal, where the order of the up-mixing and the digital-to-analog conversion processes is adjustable. The digital baseband signal and the digital intermediate frequency signal may be collectively referred to as a digital signal.

Fig. 7b is a schematic structural diagram of a terminal according to an embodiment of the present application. The structure of the terminal 21 can refer to the structure shown in fig. 7 b.

The terminal includes at least one processor 1611, at least one transceiver 1612, and at least one memory 1613. The processor 1611, memory 1613, and transceiver 1612 are connected. Optionally, the terminal 21 may also include an output device 1614, an input device 1615, and one or more antennas 1616. The antenna 1616 is coupled to the transceiver 1612, and the output device 1614 and the input device 1615 are coupled to the processor 1611.

The transceiver 1612, memory 1613, and antenna 1616 may perform similar functions as described with respect to fig. 7 a.

The processor 1611 may be a baseband processor or a CPU, and the baseband processor and the CPU may be integrated together or separated.

The processor 1611 may be used to implement various functions for the terminal, such as processing communication protocols and communication data, or controlling the entire terminal device, executing software programs, and processing data of the software programs; or to assist in completing computational processing tasks, such as processing of graphical images or audio, etc.; or processor 1211 may be used to perform one or more of the functions described above

An output device 1614 is in communication with the processor 1611 and may display information in a variety of ways. For example, the output device 1214 may be a Liquid Crystal Display (LCD), a Light Emitting Diode (LED) Display device, a Cathode Ray Tube (CRT) Display device, a projector (projector), or the like. The input device 1615 is in communication with the processor 1611 and may accept user input in a variety of ways. For example, the input device 1615 may be a mouse, a keyboard, a touch screen device, a sensing device, or the like.

Fig. 7c is a schematic diagram of a CU-DU architecture with MN 01. As shown in fig. 7c, when MN01 is a gNB, MN01 may be a Centralized Unit (CU) -Distributed Unit (DU) architecture, MN01 may include CU0111 and DU0121, e.g., in NE DC or NR-DC, MN01 is a gNB, MN01 may be a CU-DU architecture, and MN01 may include CU0111 and DU 0121. CU0111 and DU0121 are connected, for example, through an F1 interface, CU0111 is connected to a core network element 31, for example, through an NG interface, fig. 7c illustrates by taking 1 CU0111 and DU0121 as an example, in this embodiment, DU0121 may be multiple, the multiple DUs 0121 may share one CU0111, and the multiple DUs 0121 are all connected to CU0111, for example, through an F1 interface.

FIG. 7d is a diagram of an SN11 for CU-DU architecture. As shown in FIG. 7d, when SN11 is a gNB, SN11 may be a CU-DU architecture and SN11 may include CU1111 and DU1121, e.g., in EN-DC, NGEN-DC, or NR-DC, SN11 is a gNB, SN11 may be a CU-DU architecture, and SN11 may include CU1111 and DU 1121. The CU1111 is connected to the DU1121, for example, through an F1 interface, and the CU1111 is connected to the core network element 31, for example, through an NG interface, and fig. 7d illustrates, by taking 1 CU1111 and a DU1121 as an example, in this embodiment of the present application, the DU1121 may be multiple, the multiple DUs 1121 may share one CU1111, and the multiple DUs 1121 are all connected to the CU1111, for example, through an F1 interface.

When both MN01 and SN11 are CU-DU architectures, CU0111 and CU1111 may be connected.

Under the CU-DU architecture, part of functions of MN01 are deployed on CU0111, the other part of functions of MN01 are deployed on DU0121, and the functional division of CU0111 and DU0121 can be divided according to a wireless protocol stack. One possible method is to deploy a Radio Resource Control (RRC), a Service Data Adaptation (SDAP) layer, and a Packet Data Convergence Protocol (PDCP) layer in CU 0111; radio Link Control (RLC), Medium Access Control (MAC), and physical layer (PHY) are deployed in DU 0121. Another possible approach is to deploy RRC, PDCP, RLC, SDAP and MAC and partial physical layers in CU0111 and partial physical layers in DU 0121. It should be noted that the foregoing functional division is only an example, and other division manners are possible, which are not limited in this embodiment of the present application.

When the SN11 adopts the CU-DU architecture, the functions and functional division of the CU1111 and the DU1121 can refer to the related contents of the functions and functional division of the CU0111 and the DU0121 when the MN01 adopts the CU-DU architecture, which are not described herein again.

In the above communication system, when the network side (e.g. MN01 and SN11) modifies the configuration of the bearer for the terminal 21, the Data Radio Bearer (DRB) Identification (ID) of the bearer may need to be changed, and when the DRB ID of the bearer is changed, an interactive negotiation may need to be performed between MN01, SN11 and the terminal 21, which occupies communication resources. The embodiment of the application provides a scheme, which can simplify the process of changing the DRB ID and save communication resources.

Some terms in the embodiments of the present application are explained below.

1. The first bearer is terminated at MN01, which can be understood as the PDCP anchor point of the first bearer being MN01, and the PDCP anchor point of the first bearer being understood as the PDCP entity of the first bearer being MN01 from the network side.

2. The first bearer terminates at SN11, which may be understood as the PDCP anchor point of the first bearer being SN11, and the PDCP anchor point of the first bearer may be understood as the PDCP entity of the first bearer being at SN11 from the network side perspective.

The following describes aspects of embodiments of the present application.

Fig. 8 is a diagram illustrating an embodiment of changing a DRB ID. As shown in fig. 8:

s801: the MN01 sends the original DRB ID and the one or more candidate DRB IDs of the first bearer to the SN 11.

The one or more candidate DRB IDs may be DRB IDs for the first bearer, which may be understood as MN01 sending the one or more candidate DRB IDs to SN11 to facilitate SN11 altering the DRB ID of the first bearer if needed.

In the first embodiment, the one or more candidate DRB IDs are candidate DRB IDs of the first bearer, and it can be understood that the one or more candidate DRB IDs correspond to the first bearer, or the one or more candidate DRB IDs and the first bearer have a corresponding relationship.

In a second implementation, the one or more candidate DRB IDs are candidate DRB IDs of multiple bearers, where the multiple bearers include the first bearer. It is to be understood that there is no correspondence between the one or more candidate DRB IDs and the first bearer, and the one or more candidate DRB IDs may be selected by multiple bearers. Here, the multiple bearers may be understood as all bearers established by MN01 for SN11 for terminal 21, or may be understood as part of bearers established by MN01 for SN11 for terminal 21, for example, bearers anchored by PDCP anchor point on SN11, which is not limited in this embodiment of the present application.

S802: the SN11 sends a new DRB ID for the first bearer to MN01, the new DRB ID being one of the one or more candidate DRB IDs.

Optionally, the SN11 may also send the E-RAB ID of the first bearer or the original DRB of the first bearer to the MN 01.

Through the above scheme, MN01 may first provide one or more candidate DRB IDs for SN11, SN11 may determine whether to change the DRB ID, and when SN11 determines to change the DRB ID, select one of the one or more candidate DRB IDs as a new DRB ID and send it to MN01, so that MN01 and SN11 may generate configuration information for terminal 21 according to the new DRB ID. The flow of changing DRB ID is simplified, for example, when SN11 decides to change DRB ID, it sends a request to MN01, MN01 and SN11 negotiate new DRB ID.

The scheme in the embodiment of the present application is further described below with reference to the flowcharts in fig. 9 to fig. 11.

First, how to change the DRB ID in the secondary node addition request flow is described in conjunction with the secondary node addition request flow.

Fig. 9 is a schematic diagram of an embodiment of changing a DRB ID. As shown in fig. 9:

s901: the MN01 sends a secondary node addition request message to the SN11, the secondary node addition request message including the information related to the first bearer and the one or more candidate DRB IDs.

For example, processor 1511 of MN01 may send a secondary node addition request message to SN11 at network interface 1514 of MN 01. Similarly, processor 1511 of SN11 may receive a secondary node addition request message from MN01 through network interface 1514 of SN 11.

The MN01 may request the SN11 to allocate resources to the UE by sending a secondary node addition request message to the SN11, specifically, the SN11 may be requested to establish one or more bearers for the terminal 21, or change bearer types of one or more bearers for the terminal 21, which is described below with reference to the first bearer as an example.

For example, before the MN01 sends the secondary node addition request message to the SN11, the bearer type of the first bearer may be an MCG bearer terminated by the MN, the MN01 may determine the bearer type of the first bearer after the secondary node is added, and the first bearer may be terminated at the SN after the secondary node is added, that is, the PDCP anchor point of the first bearer after the secondary node is added is SN11, for example, the bearer type of the first bearer after the secondary node is an MCG bearer terminated by the SN, an SCG bearer terminated by the SN, or a split bearer terminated by the SN.

The secondary node addition request message may include information related to the first bearer, and the information related to the first bearer may include:

(1) DRB ID of the first bearer.

The DRB ID of the first bearer may be understood as the DRB ID of the first bearer (hereinafter, referred to as the original DRB ID of the first bearer for convenience of description) on MN01 before the secondary node is added, and after the secondary node is added, the secondary node may decide to change the DRB ID of the first bearer (hereinafter, referred to as the new DRB ID of the first bearer for convenience of description).

(2) And adding the indication information of the bearer type of the first bearer after the auxiliary node is added.

The indication information of the bearer type may explicitly indicate the bearer type, including the 6 bearer types described in fig. 6a, for example, any one of other bearer types in 5 except the MCG bearer terminated by the MN. Optionally, the indication may also be implicitly performed, for example, to indicate whether the PDCP entity of the first bearer after the secondary node is added is on the SN11, whether the first bearer after the secondary node is added has an MCG resource, and whether the first bearer after the secondary node is added has an SCG resource.

For example, after the auxiliary node is added, the PDCP anchor point of the first bearer is SN11, after the auxiliary node is added, the first bearer has an MCG resource, and there is no SCG resource, that is, after the auxiliary node is added, the bearer type of the first bearer is an MCG bearer terminated by SN; or, after the auxiliary node is added, the PDCP anchor point of the first bearer is SN11, after the auxiliary node is added, the first bearer does not have an MCG resource, and has an SCG resource, that is, after the auxiliary node is added, the bearer type of the first bearer is an SCG bearer terminated by SN; or, after the auxiliary node is added, the PDCP entity of the first bearer is located in SN11, and after the auxiliary node is added, the first bearer has MCG resources and SCG resources, that is, the bearer type of the first bearer after the auxiliary node is added is a split bearer terminated by SN.

(3) Adding configuration information of the PDCP entity of the first bearer on the MN01 before the secondary node.

For example, it may include increasing the PDCP SN length of the first bearer at MN01 before the secondary node, e.g., increasing the PDCP SN length of the first bearer at MN01 before the secondary node (hereinafter referred to as the first PDCP SN length for ease of description) may be 12 bits (bits) or 18 bits.

Optionally, the configuration information of the PDCP entity of the first bearer on the MN01 may be used to assist the SN11 in generating the configuration information of the PDCP entity after adding the secondary node.

Alternatively, the configuration information of the PDCP entity of the first bearer at MN01 may be understood as the configuration information of the PDCP entity of the first bearer when the first bearer is terminated at MN (before adding the secondary node).

Optionally, the secondary node addition request message may not include the configuration information of the PDCP entity of the first bearer on the MN01 before the addition of the secondary node, which depends on the implementation of the MN01, or depends on some special scenarios, for example, the first bearer is newly created for the terminal 21 by the MN01 in the secondary node addition procedure, and at this time, the configuration information of the PDCP entity of the first bearer on the MN01 before the addition of the secondary node is not added on the MN 01.

Optionally, when the core network element 31 is an EPC network element, the related information of the first bearer may include, in addition to the DRB ID of the first bearer, an evolved universal terrestrial radio access bearer (E-RAB, E-UTRAN radio access bearer) ID of the first bearer; when the core network element 31 is a 5GC network element, the configuration information of the first bearer may include a DRB ID of the first bearer, excluding the E-RAB ID.

In the above description taking the first bearer as an example, the MN01 may carry related information of one or more bearers of the terminal 21 through the secondary node addition request message, where the related information of each bearer includes an original DRB ID of the bearer, indication information of a bearer type of the bearer after the secondary node is added, and configuration information of a PDCP entity of the bearer on the MN01 before the secondary node is added, and reference may be made to contents in the related information of the first bearer, which is not described herein again.

Optionally, the secondary node addition request message may further include one or more candidate DRB IDs of the terminal 21.

Optionally, the one or more candidate DRB IDs are DRB IDs that the SN11 can use for one or more bearers of the terminal 21, and it is understood that, when the SN11 needs to change the DRB ID of a certain bearer, one candidate DRB ID can be selected from the one or more candidate DRB IDs as a new DRB ID of the bearer.

Optionally, the one or more candidate DRB IDs may be used for the SN11 to generate configuration information of at least one entity (which may include one or more of a PDCP entity, an SCG RLC entity, and an SCG logical channel) corresponding to the MN of the first bearer on the terminal 21 for the terminal 21. It can be understood that when the SN11 needs to generate configuration information of an entity (which may include one or more of a PDCP entity, an SCG RLC entity, and an SCG logical channel) of a certain bearer, the SN11 may change a DRB ID of the bearer, and the SN11 may determine a new DRB ID for a bearer from the one or more candidate DRB IDs and then generate configuration information of an entity corresponding to the new DRB ID of the bearer.

Two implementations of the one or more candidate DRB IDs described above are provided below.

As a first implementation manner, the one or more candidate DRB IDs of the terminal 21 have no correspondence with the first bearer. It is to be understood that the MN01 provides one or more candidate DRB IDs for the bearers of the terminal 21, and for each bearer of the terminal 21, the SN11 may select one candidate DRB ID from the one or more candidate DRB IDs as the new DRB ID for the bearer, for example, the SN11 may select one candidate DRB ID for the first bearer as the new DRB ID for the first bearer among the one or more candidate DRB IDs, and the SN11 may select one candidate DRB ID for the second bearer as the new DRB ID for the second bearer among the one or more candidate DRB IDs. The multiple bearers may be understood herein as all bearers that MN01 requests SN11 to establish for terminal 21, or as part of bearers that MN01 requests SN11 to establish for terminal 21, e.g. bearers anchored by PDCP anchor points on SN 11.

For example, a candidate DRB ID list (list) may be added in the secondary node addition request message, which may include one or more candidate DRB IDs.

For example, when the core network element 31 is an EPC network element, referring to section 9.1.4.1 of Technical Specification, TS, version (version, V)15.1.0 of third Generation Partnership Project (3 GPP) Technical Standard (TS) 36.423, the "new air interface node ADDITION REQUEST" message may further include an information element "candidate new data radio bearer identification list" (candidate DRB ID list), and a specific information element structure may be as shown in table 1 below:

TABLE 1

Similarly, when the core network element 31 is a 5GC network element, the first bearer has no E-RAB ID and has a DRB ID, and the candidate DRB ID list may be added in the secondary node addition request message. In the prior art, MN01 may send a DRB ID list to SN11 for SN11 to remap QoS flows to DRBs. The candidate DRB ID list introduced in this embodiment may reuse the DRB ID list in the prior art.

As a second implementation manner, the one or more candidate DRB IDs have a corresponding relationship with the first bearer, that is, the one or more candidate DRB IDs are candidate DRB IDs of the first bearer.

It is to be understood that MN01 provides one or more candidate DRB IDs to SN11 for each bearer of terminal 21, i.e., each bearer carries one or more candidate DRB IDs, and SN11 may select one candidate DRB ID for the bearer from the one or more candidate DRB IDs for the bearer.

Optionally, the candidate DRB IDs of different bearers may be different, for example, a first bearer carries one or more candidate DRB IDs, a second bearer carries one or more candidate DRB IDs, and each candidate DRB ID of the first bearer is different from each candidate DRB ID of the second bearer.

Optionally, the one or more candidate DRB IDs may be added to the configuration information of each bearer, and the following describes an example of adding one candidate DRB ID to the configuration information of the first bearer.

For example, when the core network element 31 is an EPC network element, referring To section 9.1.4.1 of 3GPP TS 36.423V15.1.0, an "candidate data radio bearer identification" (candidate DRB ID) cell may Be further included in an "E-RAB entry To Be Added" cell in an "SGNB ADDITION REQUEST", and a specific cell structure may Be as shown in table 2 below:

TABLE 2

Similarly, when the core network element 31 is a 5GC network element, the first bearer has no E-RAB ID and has a DRB ID, and a candidate DRB ID corresponding to the DRB ID may be added.

Optionally, after the SN11 receives the relevant information of the first bearer and one or more candidate DRB IDs, the memory 1512 of the SN11 may store the received information.

S902: the SN11 determines the new DRB ID for the first bearer.

For example, processor 1511 of SN11 may determine a new DRB ID for the first bearer.

Alternatively, the SN11 may change the DRB ID of the first bearer, at which point the SN11 needs to determine the new DRB ID of the first bearer.

As a first implementation, the SN11 may change the PDCP SN length of the first bearer, and when the PDCP SN length of the first bearer changes, the SN11 may change the DRB ID of the first bearer, and at this time, the SN11 may determine the DRB ID of the first bearer. Before S902, the SN11 may determine the PDCP SN length of the first bearer after the addition of the secondary node (hereinafter referred to as the second PDCP SN length for descriptive convenience).

For example, before adding the secondary node, the PDCP entity of the first bearer is on the MN01, and the length of the first PDCP SN of the first bearer is 12 bits; after the secondary node is added, the PDCP entity of the first bearer has SN11, SN11 may determine the PDCP SN length, and SN11 may determine that the second PDCP SN length of the first bearer after the secondary node is added is 18 bit. Since the PDCP SN length of the first bearer has changed, the SN11 may determine a new DRB ID for the first bearer.

It can be understood that, when the length of the PDCP SN of the first bearer changes, the network side needs to perform configuration of deleting and then adding the first bearer, specifically, needs to delete the bearer using the original DRB ID of the first bearer and add the bearer using the new DRB ID of the first bearer, and the network side includes MN01 and SN 11. The SN11 may generate configuration information of an entity corresponding to the SN11 of the first bearer on the terminal 21, and the MN01 generates configuration information of an entity corresponding to the MN01 of the first bearer on the terminal 21, which is specifically described in S903-S905.

As a second embodiment, the SN11 may not change the PDCP SN length of the first bearer, and when the PDCP SN length of a bearer does not change but the PDCP anchor point of the bearer changes, the SN11 may change the DRB ID of the first bearer, at which point the SN11 may determine the new DRB ID of the first bearer.

For example, before adding the secondary node, the PDCP entity of the first bearer is on the MN01, and the length of the first PDCP SN of the first bearer is 12 bits; after the secondary node is added, the PDCP entity of the first bearer is at SN11, SN11 may determine the PDCP SN length, and SN11 may determine that the second PDCP SN length of the first bearer is still 12 bits after the secondary node is added. Since the PDCP SN length of the first bearer has not changed but the PDCP anchor of the first bearer has changed, the SN11 may determine a new DRB ID for the first bearer.

Because the anchor point of the PDCP entity is encrypted by the key of the MN01 when the anchor point of the PDCP entity is at the MN01, when the anchor point of the PDCP entity is changed to the SN11, the key of the SN11 is used for encryption, the corresponding key is also changed, the change of the logic channel can be realized by changing the loaded DRB ID, the data encrypted by the old key can be continuously transmitted by the original logic channel, and the data encrypted by the new key is transmitted by the new logic channel, thereby avoiding the interruption of the service data caused by the key confusion.

It can be understood that, when the PDCP SN length of the first bearer does not change, but the PDCP anchor point of the first bearer changes, the new DRB ID of the first bearer and the original DRB ID of the first bearer may be used by the SN11 to generate configuration information of an entity corresponding to the SN11 of the first bearer on the terminal 21, and the MN01 generates configuration information of an entity corresponding to the MN01 of the first bearer on the terminal 21, where the release and added configuration information of which entities of the bearer are generated for the terminal 21 by the MN01 and the SN11 may be predefined.

Optionally, when the SN11 may determine that the configuration information of the entity corresponding to the at least one SN11 of the first bearer on the terminal 21 is to be generated, a new DRB ID of the first bearer is determined, which is specifically described in S903, and S903 may be before S902 or S903 may be after S903.

In the first implementation manner of the one or more candidate DRB IDs in S901, that is, the one or more candidate DRB IDs have no correspondence with the first bearer, the SN11 may select one candidate DRB ID from the one or more candidate DRB IDs as the new DRB ID of the first bearer.

In the second implementation manner of the one or more candidate DRB IDs in S901, that is, the one or more candidate DRB IDs have a corresponding relationship with the first bearer, the SN11 may select one candidate DRB ID from the one or more candidate DRB IDs of the first bearer as the new DRB ID of the first bearer.

Optionally, the new DRB ID of the first bearer and the original DRB ID of the first bearer are associated, which may be understood as that the new DRB ID and the original DRB ID both correspond to the first bearer, for example, when the core network element 31 is an EPC network element, the new DRB ID of the first bearer and the E-RAB identifier corresponding to the original DRB ID of the first bearer are the same; when the core network element 31 is a 5GC network element, the new DRB ID of the first bearer corresponds to the original DRB ID of the first bearer.

In connection with S903-S905, it is described how the MN01 and the SN11 generate configuration information of the first bearer for the terminal 21 according to the new DRB ID of the first bearer.

S903: the SN11 generates first configuration information for the first bearer from the new DRB ID for the first bearer.

For example, processor 1511 of SN11 may generate first configuration information for a first bearer.

The first configuration information of the first bearer may be configuration information of an entity corresponding to the SN11 of the first bearer on the terminal 21.

The bearer type of the first bearer before the auxiliary node is added is an MCG bearer terminated by MN, and the bearer type of the first bearer after the auxiliary node is added is an MCG bearer terminated by SN, an SCG bearer terminated by SN or a split bearer terminated by SN.

In the first embodiment, that is, the length of the PDCP SN of the first bearer changes, the first configuration information of the first bearer may include the following:

if the first bearer on the terminal 21 does not have an entity corresponding to a certain SN11 before the addition of the secondary node, and the first bearer on the terminal 21 has an entity corresponding to the SN11 after the addition of the secondary node, the first configuration information of the first bearer may include the configuration information of the entity corresponding to the SN11, and the entity corresponding to the SN11 may be a PDCP entity, an SCG RLC entity, or an SCG logical channel.

Optionally, before the auxiliary node is added, the PDCP anchor point of the first bearer is MN01, and after the auxiliary node is added, the PDCP anchor point of the first bearer is SN11, it can be understood that the PDCP entity of the first bearer on the terminal 21 is changed from being associated with MN01 to being associated with SN11, and the first configuration information of the first bearer may include configuration information of release of the PDCP entity corresponding to the original DRB ID and configuration information of increase of the PDCP entity corresponding to the new DRB ID, at this time, it is not necessary for MN01 to regenerate the configuration information of release of the PDCP entity corresponding to the original DRB ID.

For example, the bearer type of the first bearer before the auxiliary node is added is an MN-terminated MCG bearer, the bearer type of the first bearer after the auxiliary node is added is an SN-terminated MCG bearer, and the first configuration information of the first bearer may be the release of the PDCP entity corresponding to the original DRB ID and the added configuration information of the PDCP entity corresponding to the new DRB ID.

Optionally, the first configuration information of the first bearer may include, in addition to the release of the PDCP entity corresponding to the original DRB ID and the configuration information added to the PDCP entity corresponding to the new DRB ID, configuration information added to the SCG RLC entity corresponding to the new DRB ID and configuration information added to the SCG logical channel corresponding to the new DRB ID.

For example, the bearer type of the first bearer before the addition of the secondary node is an MN-terminated MCG bearer, the bearer type of the first bearer after the addition of the secondary node is an SN-terminated SCG bearer or an SN-terminated split bearer, and the first configuration information of the first bearer may include release of a PDCP entity corresponding to the original DRB ID and added configuration information of a PDCP entity corresponding to the new DRB ID, and added configuration information of an SCG RLC entity corresponding to the new DRB ID and added configuration information of a logical channel corresponding to the new DRB ID.

In the second embodiment, that is, the length of the first bearer PDCP SN is not changed, but the anchor point of the PDCP entity of the bearer is changed, the first configuration information of the first bearer may include the following:

if the entity corresponding to the SN11 is not established before the addition of the secondary node, and the first bearer on the terminal 21 after the addition of the secondary node has the entity corresponding to the SN11, the first configuration information of the first bearer may include the configuration information of the entity corresponding to the SN 11.

Optionally, before the auxiliary node is added, the PDCP anchor point of the first bearer is MN01, after the auxiliary node is added, the PDCP anchor point of the first bearer is SN11, the PDCP entity of the first bearer on the terminal 21 is changed from being associated with MN01 to being associated with SN11, and the first configuration information of the first bearer may include the reconstructed configuration information of the PDCP entity.

For example, the bearer type of the first bearer before the auxiliary node is added is an MCG bearer terminated by MN, the bearer type of the first bearer after the auxiliary node is added is an MCG bearer terminated by SN, and the first configuration information of the first bearer may include the reconstructed configuration information of the PDCP entity.

Optionally, the first configuration information of the first bearer may further include added configuration information of an SCG RLC entity corresponding to the new DRB ID and added configuration information of an SCG logical channel corresponding to the new DRB ID.

For example, the bearer type of the first bearer before the addition of the secondary node is an MN-terminated MCG bearer, the bearer type of the first bearer after the addition of the secondary node is an SN-terminated SCG bearer or an SN-terminated split bearer, and the first configuration information of the first bearer may include the reconstructed configuration information of the PDCP entity, the added configuration information of the SCG RLC entity corresponding to the new DRB ID, and the added configuration information of the SCG logical channel corresponding to the new DRB ID.

Optionally, in the second embodiment, when the core network element 31 is a 5GC network element or an EPC network element, the re-establishment configuration information of the PDCP entity may include an original data radio bearer identifier and information indicating that the terminal 12 re-establishes the PDCP entity.

Optionally, in the second embodiment, when the core network element 31 is an EPC, the added configuration information of the SCG RLC entity corresponding to the new DRB ID may include the new DRB ID and configuration information of a corresponding entity, and the added configuration information of the SCG logical channel corresponding to the new DRB ID may include the new DRB ID and configuration information of a corresponding entity.

Optionally, in the second embodiment, when the core network element 31 is a 5GC, the added configuration information of the SCG RLC entity corresponding to the new DRB ID may include the new DRB ID and the configuration information of the corresponding entity, and the added configuration information of the SCG logical channel corresponding to the new DRB ID may include the new DRB ID and the configuration information of the corresponding entity.

Optionally, in the second embodiment, when receiving the reestablishment information of the PDCP entity, the terminal 21 reestablishes the PDCP entity of the first bearer, but at this time, the DRB ID of the first bearer changes, and the terminal 21 needs to reestablish the PDCP entity and associate the PDCP entity with the new DRB ID. Two examples are provided below.

As a first example, the SN11 may send indication information to the terminal 21, the indication information indicating that the terminal 21 associates the PDCP entity to the new DRB ID when re-establishing the PDCP entity.

For example, the SN11 may add a new DRB ID in the re-established configuration information of the PDCP entity in the first configuration information of the first bearer.

For example, referring to section 6.3.2 of 3GPP TS 38.331V15.1.0, a DRB ("DRB-ToAddMod") cell to be added modified in a radio bearer configuration ("RadioBearerConfig") may further include a new data radio bearer identity ("newDRB-identity") in addition to the new data radio bearer identity ("DRB-identity") and the reconstructed PDCP ("reselabyshupdcp").

As a second example, the SN11 may not instruct the terminal 21 to associate the PDCP entity with the new DRB ID when the terminal 21 re-establishes the PDCP entity of the first bearer, and the terminal 21 determines whether the PDCP entity needs to be associated with the new DRB ID, which is specifically described in S906.

S904: the SN11 sends a secondary node addition request response message including the new DRB ID of the first bearer and the first configuration information of the first bearer to the MN 01.

Optionally, processor 1511 of SN11 may send a secondary node addition request response message to the MN01 through network interface 1514 of SN 11.

Optionally, the secondary node addition request response message may further include indication information indicating that the new DRB ID corresponds to the first bearer.

Optionally, when the core network element 31 is an EPC element, the indication information may be an E-RAB ID of the first bearer.

For example, when the core network element 31 is an EPC network element, referring to section 9.1.4.2 of 3GPP TS 36.423V15.1.0, a REQUEST response may be added at a "new air interface node" ("SGNB ADDITION REQUEST

An cell "new data radio bearer identification" (new DRB ID) is Added To an "allowed To-Be-Added E-RAB entry" ("E-RABs Admitted To Be Added Item") in an ACKNOWLEDGE ") message, and a specific cell structure may Be as shown in table 3 below:

TABLE 3

By carrying the E-RAB identifier of the first bearer and the new DRB ID of the first bearer in the secondary node addition request response message, MN01 can obtain the original DRB ID of the first bearer through the E-RAB identifier of the first bearer, thereby knowing that the DRB ID of the first bearer changes.

Optionally, when the core network element 31 is a 5GC network element, the indication information may be the original DRB ID.

For example, when the core network element 31 is a 5GC element, referring to section 9.2.1.7 of 3GPP TS 38.423V0.8.0, an SN terminated Packet Data Unit (PDU) Session Resource Response information ("PDU Session Resource Response Info-SN terminated") information element may include an information element as shown in table 4, and may further include a "new data radio bearer identification" (new DRB ID) in addition to an original data radio bearer identification (DRB ID).

TABLE 4

By carrying the original DRB ID of the first bearer and the new DRB ID of the first bearer in the secondary node addition request response message, the MN01 can learn that the DRB ID of the first bearer has changed.

Optionally, when the secondary node addition request message only carries one candidate DRB ID (which may or may not have a correspondence with the first bearer), the secondary node addition request response message may not include the new DRB ID. It is to be appreciated that when only one candidate DRB ID is carried in the secondary node addition request message, the MN01 may determine that the SN11 will use the candidate DRB ID as the new DRB ID of the first bearer, and the secondary node addition request response message is not required to carry the new DRB ID.

As an example, when the anchor point of the PDCP entity of a bearer changes, the SN11 needs to determine a new DRB ID for the bearer.

For example, when the secondary node addition request message only carries one candidate DRB ID, since the PDCP entity anchor of the first bearer is changed from MN01 to SN11 and the PDCP anchor is changed, MN01 may determine that SN11 may use the candidate DRB ID as the new DRB ID of the first bearer, and the secondary node addition request response message sent by SN11 may not carry the new DRB ID of the first bearer.

Optionally, MN01 and SN11 may predefine use one of the one or more candidate DRB IDs (which may or may not have a correspondence with the first bearer) as the new DRB ID of the first bearer, for example, MN01 and SN11 may predefine the first bearer to use the first candidate DRB ID as the new DRB ID of the first bearer, and at this time, the secondary node addition request response message may not include the new DRB ID of the first bearer. It will be appreciated that the MN01 can determine which candidate DRB ID the SN11 will use as the new DRB ID for the first bearer, and that the secondary node addition request response message is not required to carry the new DRB ID for the first bearer.

Optionally, when the SN11 changes the PDCP SN length, the secondary node addition request message may further include a second PDCP SN length of the first bearer.

After receiving the new DRB ID of the first bearer through the secondary node addition request response message, the MN01 may generate the second configuration information of the first bearer according to the new DRB ID of the first bearer, which is described below with reference to S905.

S905: the MN01 generates second configuration information of the first bearer according to the new DRB ID of the first bearer.

For example, processor 1511 of MN01 may generate second configuration information for the first bearer.

The second configuration information of the first bearer may be configuration information of an entity corresponding to MN01 of the first bearer on the terminal 21.

If the first bearer on the terminal 21 before the addition of the secondary node has an entity corresponding to a certain MN01, and no matter whether the first bearer on the terminal 21 after the addition of the secondary node has an entity corresponding to the MN01, the second configuration information of the first bearer may include the configuration information of the entity corresponding to the MN01, and the entity corresponding to the MN01 may be an MCG RLC entity or an MCG logical channel.

Optionally, the second configuration information of the first bearer may include configuration information of release of an MCG RLC entity corresponding to the original DRB ID and configuration information of addition of an MCG RLC entity corresponding to the new DRB ID, and configuration information of release of an MCG logical channel corresponding to the original DRB ID and addition of an MCG logical channel entity corresponding to the new DRB ID.

For example, the bearer type of the first bearer before the addition of the secondary node is an MCG bearer terminated by MN, the bearer type of the first bearer after the addition of the secondary node is an SN-terminated MCG or an SN-terminated split bearer, and the second configuration information of the first bearer includes configuration information of release of an MCG RLC entity corresponding to the original DRB ID and configuration information of addition of an MCG RLC entity corresponding to the new DRB ID, and configuration information of release of an MCG logical channel corresponding to the original DRB ID and addition of an MCG logical channel corresponding to the new DRB ID.

Optionally, when the core network element 31 is an EPC, the configuration information released by the MCG RLC entity corresponding to the original DRB ID may include the original DRB ID and the configuration information of the corresponding entity, and the configuration information added by the MCG RLC entity corresponding to the new DRB ID may include the new DRB ID and the configuration information of the corresponding entity; the configuration information of the release of the MCG logical channel corresponding to the original DRB ID may include the original DRB ID and the configuration information of the corresponding entity, and the configuration information of the addition of the MCG logical channel corresponding to the new DRB ID may include the new DRB ID and the configuration information of the corresponding entity.

Optionally, when the core network element 31 is a 5GC, the configuration information released by the MCG RLC entity corresponding to the original DRB ID may include the original DRB ID and the configuration information of the corresponding entity, and the configuration information added by the MCG RLC entity corresponding to the new DRB ID may include the new DRB ID and the configuration information of the corresponding entity; the configuration information of the release of the MCG logical channel corresponding to the original DRB ID may include the original DRB ID and the configuration information of the corresponding entity, and the configuration information of the addition of the MCG logical channel corresponding to the new DRB ID may include the new DRB ID and the configuration information of the corresponding entity.

Optionally, the second configuration information of the first bearer may include configuration information of release of an MCG RLC entity corresponding to the original DRB ID and configuration information of release of an MCG logical channel corresponding to the original DRB ID.

For example, the bearer type of the first bearer before the addition of the auxiliary node is an MCG bearer terminated by MN, the bearer type of the first bearer after the addition of the auxiliary node is an SCG bearer terminated by SN, and the second configuration information of the first bearer may further include configuration information of release of an MCG RLC entity corresponding to the original DRB ID and configuration information of release of an MCG logical channel corresponding to the original DRB ID.

Optionally, when the core network element 31 is an EPC, the configuration information released by the MCG RLC entity corresponding to the original DRB ID may include the original DRB ID and configuration information of a corresponding entity, and the configuration information released by the MCG logical channel corresponding to the original DRB ID may include the original DRB ID and configuration information of a corresponding entity.

Optionally, when the core network element 31 is a 5GC, the configuration information released by the MCG RLC entity corresponding to the original DRB ID may include the original DRB ID and the configuration information of the corresponding entity, and the configuration information released by the MCG logical channel corresponding to the original DRB ID may include the original DRB ID and the configuration information of the corresponding entity.

S906: MN01 sends an RRC connection reconfiguration message to terminal 21 including first configuration information of the first bearer and second configuration information of the first bearer.

For example, the processor 1511 of MN01 may send an RRC connection reconfiguration message to the terminal 21 through the transceiver 1513 of MN01 and the antenna 1515 of MN 01.

After receiving the RRC connection reconfiguration message, the terminal 21 may operate the entity of the first bearer on the terminal 21 according to the first configuration information of the first bearer and the second configuration information of the first bearer.

Optionally, when the first configuration information of the first bearer includes the re-establishment configuration information of the PDCP entity, the terminal 21 may re-establish the PDCP entity, and associate the PDCP entity with the new DRB ID.

As a first embodiment, the SN11 may instruct the terminal 21 to associate the PDCP entity with the new DRB ID when the PDCP entity is re-established.

As for the SN11 indicating that the terminal 21 rebuilds the PDCP entity, reference may be made to the relevant contents in S903.

For example, when the reconstructed configuration information of the PDCP entity in the first configuration information of the first bearer includes the new DRB ID, the terminal 21 may associate the PDCP entity with the new DRB ID when reconstructing the PDCP entity, or the terminal 21 may associate the PDCP entity with the new DRB ID first and then reconstruct the PDCP entity.

As a second embodiment, the SN11 may not instruct the terminal 21 to re-establish the PDCP entity, and associate the PDCP entity with the new DRB ID. At this time, the terminal 21 may determine whether to associate the PDCP entity with the new DRB ID when the PDCP entity is re-established.

Optionally, the terminal 21 may determine whether the first configuration information of the first bearer and the second configuration information of the first bearer include the released configuration information of one entity corresponding to the original DRB ID and the added configuration information of another entity corresponding to the new DRB ID, when the first configuration information of the first bearer and the second configuration information of the first bearer exist, it indicates that the DRB ID of the first bearer changes, and when the terminal 21 reestablishes the PDCP entity, the PDCP entity needs to be associated with the new DRB ID.

The first configuration information of the first bearer and the second configuration information of the first bearer include configuration information of a release of an entity corresponding to the original DRB ID and configuration information of an addition of another entity corresponding to the new DRB ID, and may include at least one of the following:

(1) the second configuration information of the first bearer includes the released configuration information of an entity corresponding to the original DRB ID and the added configuration information of another entity corresponding to the new DRB ID.

(2) The second configuration information of the first bearer includes the released configuration information of an entity corresponding to the original DRB ID, and the first configuration information of the first bearer includes the added configuration information of another entity corresponding to the new DRB ID.

For example, the bearer type of the first bearer before the addition of the auxiliary node is an MCG bearer terminated by MN, the bearer type of the first bearer after the addition of the auxiliary node is an SCG bearer terminated by SN, the second configuration information of the first bearer may include configuration information of release of an MCG RLC entity corresponding to an original DRB ID and configuration information of release of an MCG logical channel entity corresponding to an original DRB ID, and the first configuration information of the first bearer may include configuration information of addition of an SCG RLC entity corresponding to a new DRB ID and configuration information of addition of an SCG logical channel entity corresponding to a new DRB ID.

Optionally, when the core network element 31 is an EPC network element, the added configuration information of the entity corresponding to the new DRB ID includes the new DRB ID, and the released configuration information of the entity corresponding to the original DRB ID includes the original DRB ID, which may specifically refer to the relevant contents in the foregoing S903 and S905. Although the DRB ID of the first bearer is changed, the E-RAB ID of the first bearer is not changed, the original DRB ID and the new DRB ID both correspond to the same E-RAB ID, and the terminal 21 may determine that the first bearer has changed the DRB ID, thereby associating the PDCP entity to the new DRB ID.

For example, the second configuration information of the first bearer includes the release of the MCG RLC entity corresponding to the original DRB ID and the added configuration information of the MCG RLC entity corresponding to the new DRB ID, and the terminal 21 may know that the MCG RLC entity corresponding to the original DRB ID is deleted, but the terminal 21 adds a new DRB ID under the E-RAB ID corresponding to the original DRB ID to determine that the DRB ID of the first bearer changes, so that the terminal 21 associates the PDCP entity with the new DRB ID when the terminal 21 reconstructs the PDCP entity.

Optionally, when the core network element 31 is a 5GC network element, the added configuration information of the entity corresponding to the new DRB ID may include the new DRB ID and the configuration information of the corresponding entity; the released configuration information of the entity corresponding to the original DRB ID may include the original DRB ID and the configuration information of the corresponding entity. Although the DRB ID of the first bearer is changed, the Quality of Service (Qos, Quality of Service) flow (list) identifier of the first bearer is not changed, the original DRB ID and the new DRB ID both correspond to the same Qos flow list, and the terminal 21 may know that the DRB ID is changed for the first bearer, thereby associating the PDCP entity to the new DRB ID.

For example, the second configuration information of the first bearer includes the release of the MCG RLC entity corresponding to the original DRB ID and the added configuration information of the MCG RLC entity corresponding to the new DRB ID, the terminal 21 may know that the MCG RLC entity corresponding to the original DRB ID is deleted, but a new DRB ID is added under the Qos flow list corresponding to the original DRB ID, the terminal 21 may determine that the DRB ID of the first bearer changes, and when the terminal 21 reconstructs the PDCP entity, the terminal 21 associates the PDCP entity with the new DRB ID.

S907: the terminal 21 sends an RRC connection reconfiguration complete message to the MN 01.

The RRC connection reconfiguration complete message carries a SN reconfiguration complete message sent by the terminal 21 to the SN 11.

For example, processor 1611 of terminal 21 may send an RRC connection reconfiguration complete message to MN01 through transceiver 1612 of terminal 21 and antenna 1616 of terminal 21.

S908: MN01 sends a SN reconfiguration complete message to SN 11.

For example, the processor 1511 of MN01 may send a SN reconfiguration complete message to the SN11 through the network interface 1504 of MN 01.

S909: the terminal 21 completes random access with the SN 11.

With the scheme in fig. 9, MN01 may first provide SN11 with one or more candidate DRB IDs, SN11 may decide whether to change the DRB ID, and when SN11 determines to change the DRB ID, select one of the one or more candidate DRB IDs as a new DRB ID and send it to MN01, so that MN01 and SN11 may generate configuration information for terminal 21 according to the new DRB ID. The flow of changing the DRB ID is simplified, for example, when the SN11 decides to change the DRB ID, a request is sent to the MN01, the MN01 and the SN11 negotiate a new DRB ID, and in addition, the scheme reuses the existing auxiliary node to increase the request flow, thereby saving communication resources.

When the secondary node addition request message in S901 includes multiple candidate DRB IDs, after the secondary node addition request procedure in fig. 9 is ended, SN11 may also modify the procedure by triggering the secondary node to change the DRB ID of the first bearer.

How to change the DRB ID in the secondary node modification procedure is described below in conjunction with the secondary node modification procedure.

Fig. 10 is a schematic diagram of an embodiment of changing a DRB ID, as shown in fig. 10:

s1001: the SN11 determines the new DRB ID for the first bearer.

After the auxiliary node addition request procedure in fig. 9 is completed, the DRB ID of the first bearer is the new DRB ID of the first bearer in S902-S905, and on this basis, the SN11 may further change the DRB ID of the first bearer. It should be noted that, here, the original DRB ID of the first bearer is the new DRB ID of the first bearer in the secondary node addition request flow in fig. 9.

As a first implementation, the SN11 may change the PDCP SN length of the first bearer, and when the PDCP SN length of the first bearer changes, the SN11 may change the DRB ID of the first bearer, at which point the SN11 may determine a new DRB ID of the first bearer. It should be noted that the length of the PDCP SN of the first bearer changes, but the bearer type of the first bearer does not change, and the bearer type of the first bearer may be an SN-terminated MCG bearer, an SN-terminated SCG bearer, or an SN-terminated split bearer.

Since the PDCP entity of the first bearer is at SN11 after the secondary node is added, SN11 may change the PDCP SN length of the first bearer, and optionally, before S1101, SN11 may determine that the third PDCP SN length of the first bearer is different from the second PDCP SN length of the first bearer.

For example, after the secondary node is added, the PDCP entity of the first bearer is at SN11, SN11 may determine the PDCP SN length, and SN11 may determine to change the second PDCP SN length of the first bearer after the secondary node is added to the third PDCP SN length of the first bearer, for example, the second PDCP SN length of the first bearer is 18 bits, and the third PDCP SN length of the first bearer is 12 bits. Since the PDCP SN length of the first bearer has changed, the SN11 may determine a new DRB ID for the first bearer.

It can be understood that when the PDCP SN length of the first bearer changes, the new DRB ID of the first bearer can be used by the SN11 to generate configuration information of an entity corresponding to the SN11 of the first bearer on the terminal 21, and the MN01 generates configuration information of an entity corresponding to the MN01 of the first bearer on the terminal 21.

As a second implementation, the PDCP anchor of the first bearer changes, and the SN11 may determine a new DRB ID of the first bearer. For example, when the SN11 decides to release the first bearer, the PDCP anchor point of the first bearer will be changed from SN11 to MN01, and the SN11 can determine the new DRB ID of the first bearer. The bearer type of the first bearer may be changed from an SN-terminated MCG bearer, an SN-terminated SCG bearer, or an SN-terminated split bearer to an MN-terminated MCG bearer.

S1002: the SN11 generates first configuration information for the first bearer from the new DRB ID for the first bearer.

In the first embodiment, the length of the PDCP SN of the first bearer changes, but the bearer type of the first bearer does not change, and the first configuration information of the first bearer may include the following:

configuration information of an entity corresponding to SN11 of the first bearer on the terminal 21, the entity corresponding to SN11 may be a PDCP entity, an SCG RLC entity, or an SCG logical channel, depending on the bearer type of the first bearer, as will be illustrated below.

For example, the bearer type of the first bearer is an SN-terminated MCG bearer, and the first configuration information of the first bearer may include configuration information of release of a PDCP entity corresponding to the original DRB ID and configuration information of addition of a PDCP entity corresponding to the new DRB ID.

For example, the bearer type of the first bearer is an SN-terminated SCG bearer or an SN-terminated split bearer, and the first configuration information of the first bearer may include configuration information of release of a PDCP entity corresponding to an original DRB ID and configuration information of addition of a PDCP entity corresponding to a new DRB ID, configuration information of release of an SCG RLC entity corresponding to an original DRB ID and configuration information of addition of an SCG RLC entity corresponding to a new DRB ID, and configuration information of an SCG logical channel corresponding to an original DRB ID and configuration information of addition of an SCG logical channel corresponding to a new DRB ID.

In the second embodiment, the SN11 decides to release the first bearer, the PDCP anchor point of the first bearer is changed from SN11 to MN01, and the first configuration information of the first bearer may include the following:

configuration information of an entity corresponding to SN11 of the first bearer on the terminal 21, the entity corresponding to SN11 may be an SCG RLC entity or an SCG logical channel, depending on the bearer type of the first bearer, as will be illustrated below.

For example, the bearer type of the first bearer may be an SN-terminated SCG bearer or an SN-terminated split bearer, and is changed to an MN-terminated MCG bearer, and the first configuration information of the first bearer may include configuration information of release of an SCG RLC entity corresponding to the original DRB ID and configuration information of release of an SCG logical channel corresponding to the original DRB ID.

S1003: the SN11 sends a secondary node modification application message including the new DRB ID of the first bearer and the first configuration information of the first bearer to the MN 01.

Optionally, when the core network element 31 is an EPC network element, the secondary node modification application message may include, in addition to the new DRB ID, an E-RAB ID of the first bearer.

Optionally, when the core network element 31 is a 5GC network element, the auxiliary node modification application message may include the original DRB ID and the new DRB ID of the first bearer.

Optionally, in the first embodiment, the secondary node modification request message may further include a third PDCP SN length of the first bearer.

Specific contents may refer to the related contents in S904.

S1004: the MN01 generates second configuration information of the first bearer according to the new DRB ID of the first bearer.

After receiving the new DRB ID of the first bearer through the secondary node addition request response message, the MN01 may generate the second configuration information of the first bearer according to the new DRB ID of the first bearer.

In the first embodiment, the length of the PDCP SN of the first bearer changes, but the bearer type of the first bearer does not change, and the second configuration information of the first bearer may include the following:

configuration information of an entity corresponding to MN01 of the first bearer on the terminal 21, the entity corresponding to MN01 may be an MCG RLC entity or an MCG logical channel, depending on the bearer type of the first bearer, as will be exemplified below.

For example, the bearer type of the first bearer is a split bearer terminated by an SN, and the first configuration information of the first bearer may include configuration information of release of an MCG RLC entity corresponding to an original DRB ID and configuration information of addition of an MCG RLC entity corresponding to a new DRB ID, and configuration information of an MCG logical channel corresponding to the original DRB ID and configuration information of addition of an MCG logical channel corresponding to the new DRB ID.

In the second embodiment, the PDCP anchor point of the first bearer is changed from SN11 to MN01, and the second configuration information of the first bearer may include the following:

configuration information of an entity corresponding to MN01 of the first bearer on the terminal 21, and the entity corresponding to MN01 may be a PDCP entity, an MCG RLC entity and an MCG logical channel, which will be illustrated below.

Optionally, the PDCP anchor point of the first bearer is changed from SN11 to MN01, the PDCP entity of the first bearer on the terminal 21 is changed from being associated with SN11 to being associated with MN01, and the second configuration information of the first bearer may include re-established configuration information of the PDCP entity.

Optionally, the second configuration information of the first bearer may further include configuration information of release of the MCG RLC entity corresponding to the original DRB ID and configuration information of addition of the MCG RLC entity corresponding to the new DRB ID, and configuration information of release of the MCG logical channel corresponding to the original DRB ID and configuration information of addition of the MCG logical channel corresponding to the new DRB ID.

Optionally, the second configuration information of the first bearer may further include added configuration information of an MCG RLC entity corresponding to the new DRB ID and added configuration information of an MCG logical channel corresponding to the new DRB ID.

For example, the bearer type of the first bearer may be changed from an SN-terminated MCG bearer or an SN-terminated split bearer to an MN-terminated MCG bearer, and the second configuration information of the first bearer includes reconstructed configuration information of a PDCP entity, released configuration information of an MCG RLC entity corresponding to an original DRB ID and added configuration information of an MCG RLC entity corresponding to a new DRB ID, and released configuration information of an MCG logical channel corresponding to an original DRB ID and added configuration information of an MCG logical channel corresponding to a new DRB ID.

For example, the bearer type of the first bearer may be an SCG bearer terminated by an SN, and may be changed to an MCG bearer terminated by an MN, and the second configuration information of the first bearer includes reconstructed configuration information of a PDCP entity, added configuration information of an MCG RLC entity corresponding to a new DRB ID, and added configuration information of an MCG logical channel corresponding to the new DRB ID.

Optionally, in the second embodiment, when receiving the reestablishment information of the PDCP entity, the terminal 21 reestablishes the PDCP entity of the first bearer, but at this time, the DRB ID of the first bearer changes, and the terminal 21 needs to reestablish the PDCP entity and associate the PDCP entity with the new DRB ID. The MN01 may send indication information to the terminal 21 to indicate that the terminal 21 associates the PDCP entity with the new DRB ID when the PDCP entity is re-established, for example, the MN01 may add the new DRB ID to the re-established configuration information of the PDCP entity, or the MN01 may not send indication information to the terminal 21, and the terminal 21 determines whether the PDCP entity needs to be associated with the new DRB ID. The related content may refer to the related content in S903.

Other contents in S1002-S1004 may refer to related contents in S903-S905.

S1005: MN01 sends an RRC connection reconfiguration message to terminal 21 including first configuration information of the first bearer and second configuration information of the first bearer.

(1) the first configuration information of the first bearer includes the released configuration information of an entity corresponding to the original DRB ID, and the second configuration information of the first bearer includes the added configuration information of another entity corresponding to the new DRB ID.

For example, the bearer type of the first bearer is changed from an SN-terminated SCG bearer to an MN-terminated MCG bearer, and the first configuration information of the first bearer includes configuration information of release of an SCG RLC entity corresponding to the original DRB ID and configuration information of release of an SCG logical channel corresponding to the original DRB ID; the second configuration information of the first bearer includes added configuration information of an MCG RLC entity corresponding to the new DRB ID and added configuration information of an MCG logical channel corresponding to the new DRB ID.

(2) The second configuration information of the first bearer includes the released configuration information of an entity corresponding to the original DRB ID and the added configuration information of another entity corresponding to the new DRB ID.

For example, the bearer type of the first bearer is changed from an SN-terminated MCG bearer or an SN-terminated split bearer to an MN-terminated MCG bearer, and the second configuration information of the first bearer includes the released configuration information of the MCG RLC entity corresponding to the original DRB ID and the added configuration information of the MCG RLC entity corresponding to the new DRB ID, and the released configuration information of the MCG logical channel corresponding to the original DRB ID and the added configuration information of the MCG logical channel corresponding to the new DRB ID.

Optionally, when the core network element 31 is an EPC network element, the DRB ID of the first bearer is changed, but the E-RAB ID of the first bearer is not changed, the original DRB ID and the new DRB ID both correspond to the same E-RAB ID, and the terminal 21 may determine that the DRB ID is changed for the first bearer, so as to associate the PDCP entity to the new DRB ID.

Optionally, when the core network element 31 is a 5GC network element, the DRB ID of the first bearer is changed, but the Quality of Service (Quality of Service) flow list (list) identifier of the first bearer is not changed, the original DRB ID and the new DRB ID both correspond to the same Qos flow list, and the terminal 21 may know that the DRB ID is changed for the first bearer, so as to associate the PDCP entity with the new DRB ID.

Other contents in S1005 may refer to the related contents in S906.

S1006: the terminal 21 sends an RRC connection reconfiguration complete message to the MN 01.

S1007: MN01 sends a secondary node modification acknowledgement message to SN 11.

It should be noted that, in fig. 9 and fig. 10, when the DRB ID of the first bearer changes, the terminal 21 reconstructs the PDCP entity, and the terminal 21 needs to associate the PDCP entity with the new DRB ID, which may be applicable to other procedures such as changing bearer type and changing PDCP SN length.

In the scheme in fig. 10, SN11 may store one or more candidate DRB IDs provided by MN01, SN11 may decide whether to change the DRB ID, and when SN11 determines to change the DRB ID, one of the one or more candidate DRB IDs is selected as a new DRB ID and transmitted to MN01, so that MN01 and SN11 may generate configuration information for terminal 21 based on the new DRB ID. The flow of changing the DRB ID is simplified, for example, when the SN11 decides to change the DRB ID, a request is sent to the MN01, the MN01 and the SN11 negotiate a new DRB ID, and in addition, the scheme reuses the existing auxiliary node to increase the request flow, thereby saving communication resources.

In addition, in the scheme in fig. 10, SN11 may determine a new DRB ID and send the new DRB ID to MN01, which may avoid the situation that SN11 applies for a new DRB ID from MN01 and there is no DRB ID resource on MN 01.

Fig. 9 and fig. 10 respectively describe how to change the DRB ID in the secondary node addition procedure and the secondary node modification procedure, and a scheme for changing the DRB ID in combination with the secondary node addition procedure and the secondary node modification procedure is described below.

Fig. 11 is a diagram illustrating an embodiment of changing a DRB ID. As shown in fig. 11:

s1101: MN01 sends a secondary node addition request message to SN11, the secondary node addition request message including information related to the first bearer.

For example, before the MN01 sends the secondary node addition request message to the SN11, the bearer type of the first bearer may be an MCG bearer terminated by the MN, the MN01 may determine the bearer type of the first bearer after the secondary node is added, and the first bearer may be terminated at the SN after the secondary node is added, that is, the PDCP anchor point of the first bearer after the secondary node is added is on the SN11, for example, the bearer type of the first bearer after the secondary node is an MCG bearer terminated by the SN, an SCG bearer terminated by the SN, or a split bearer terminated by the SN.

The configuration information of the first bearer may include the original DRB ID of the first bearer, indication information of the bearer type of the first bearer after the secondary node is added, and configuration information of the PDCP entity of the first bearer on MN01 before the secondary node is added, where the configuration information of the PDCP entity of the first bearer on MN01 before the secondary node is added may include the PDCP SN length of the first bearer on MN01 before the secondary node (for convenience of description, hereinafter referred to as the first PDCP SN length), for example, 12 bits or 18 bits. The related content of the related information of the first bearer may refer to the related content in S901.

S1102: the SN11 sends a secondary node modification apply message to the MN01, the secondary node modification apply message including indication information for requesting a new DRB ID of the first bearer.

The SN11 may request a new DRB ID of the first bearer, and at this time, the secondary node may modify the application message to carry indication information for requesting the new DRB ID of the first bearer.

As a first implementation, the SN11 can change the PDCP SN length of the first bearer, and when the PDCP SN length of the first bearer changes, the SN11 decides to change the bearer identity of the first bearer. Prior to S1102, SN11 may determine the PDCP SN length of the first bearer (hereinafter referred to as the second PDCP SN length for convenience of description) after the addition of the secondary node of the first bearer.

For example, before adding the secondary node, the PDCP entity of the first bearer is on the MN, and the length of the first PDCP SN of the first bearer is 12 bits; after the secondary node is added, the PDCP entity of the first bearer has SN11, SN11 may determine the PDCP SN length, and SN11 may determine that the second PDCP SN length of the first bearer after the secondary node is added is 18 bit. Since the PDCP SN length of the first bearer has changed, the SN11 may request a new DRB ID for the first bearer.

It can be understood that, when the PDCP SN length of the first bearer changes, the new DRB ID of the first bearer and the original DRB ID of the first bearer may be used by the SN11 to generate configuration information of an entity corresponding to the SN11 of the first bearer on the terminal 21, and the MN01 generates configuration information of an entity corresponding to the MN01 of the first bearer on the terminal 21.

As a second embodiment, the SN11 may not change the PDCP SN length of the first bearer, and when the PDCP SN length of a bearer does not change but the anchor point of the PDCP entity of the bearer changes, the SN11 may change the DRB ID of the first bearer, at which point the SN11 may request a new DRB ID of the first bearer.

For example, before adding the secondary node, the PDCP entity of the first bearer is on the MN, and the length of the first PDCP SN of the first bearer is 12 bits; after the secondary node is added, the PDCP entity of the first bearer is at SN11, SN11 may determine the PDCP SN length, and SN11 may determine that the second PDCP SN length of the first bearer is still 12 bits after the secondary node is added. Since the PDCP SN length of the first bearer has not changed but the PDCP entity of the first bearer has changed, the SN11 may request a new DRB ID for the first bearer.

It can be understood that, when the PDCP SN length of the first bearer does not change, but the anchor point of the PDCP entity of the first bearer changes, the new DRB ID of the first bearer and the original DRB ID of the first bearer may be used for the SN11 to generate configuration information of an entity corresponding to the SN11 of the first bearer on the terminal 21, and the MN01 to generate configuration information of an entity corresponding to the MN01 of the first bearer on the terminal 21, where the configuration information of release and addition of which entities of the bearer are generated for the terminal 21 by the MN01 and the SN11 may be predefined.

Alternatively, when the SN11 may be determining to generate configuration information for an entity corresponding to at least one SN11 generating a first bearer on the terminal 21, a new DRB ID for the first bearer is requested from the MN 01.

It can be understood that, when the SN11 sends the secondary node modification application message to the MN01, the first bearer after the secondary node is added is not established yet, and at this time, the SN11 may request a new DRB ID of the first bearer based on a change in the PDCP SN length or a change in an anchor point of the PDCP entity of the first bearer. It should be noted that, the request of the SN11 for the new DRB ID of the first bearer from the MN01 is not limited to the above case, and the SN11 may request the new DRB ID of the first bearer from the MN01 based on other cases, which is not limited in this embodiment of the present application.

S1103: MN01 sends a secondary node modification request message to SN11, the secondary node modification request message including the new DRB ID of the first bearer.

S1104: SN11 sends a secondary node modification request acknowledgement message to MN 01.

S1105: MN01 sends a secondary node modification acknowledgement message to SN 11.

S1106: the SN11 generates first configuration information for the first bearer from the new DRB ID for the first bearer.

Reference may be made to the relevant content in S903.

The sequence of S1106, S1104 and S1105 is not limited in this embodiment of the application, and S1106 may be before S1104, or may be between S1104 and S1105, or may be after S1105.

S1107: the SN11 sends a secondary node addition request response message including the new DRBID for the first bearer and the first configuration information for the first bearer to the MN 01.

Reference may be made to the relevant contents in S904.

S1108: the MN01 generates second configuration information of the first bearer according to the new DRB ID of the first bearer.

Reference may be made to the relevant contents in S905.

S1109: MN01 sends an RRC connection reconfiguration message to terminal 21 including first configuration information of the first bearer and second configuration information of the first bearer.

S1110: the terminal 21 sends an RRC connection reconfiguration complete message to the MN 01.

S1111: MN01 sends a SN reconfiguration complete message to SN 11.

S1112: the terminal 21 completes random access with the SN 11.

Reference may be made to S1109-S1112 in relation to S906-S909.

In the scheme in fig. 11, by inserting the auxiliary node modification flow in the auxiliary node addition flow, it can be implemented that the DRB ID can be changed when the auxiliary node is started to be added and the bearer is not yet established, and it is not necessary to wait until the auxiliary node addition flow is completed, that is, the bearer is already established, and then modify the DRB ID of the bearer, so that the DRB ID can be changed in time.

In fig. 9 to 11, the DRB ID of the first bearer changes, the terminal 21 reconstructs the PDCP entity, and the terminal 21 needs to associate the PDCP entity with the new DRB ID, which may be applicable to other processes such as changing bearer types and changing PDCP SN lengths. The following is a description of the method.

M1201: the SN11 generates first configuration information for the first bearer.

M1202: the SN11 sends first configuration information of the first bearer to the MN 01.

M1203: MN01 generates second configuration information for the first bearer.

M1204: the MN01 transmits first configuration information of the first bearer and second configuration information of the first bearer to the terminal 21.

Optionally, the first configuration information of the first bearer or the second configuration information of the first bearer may include re-established configuration information of the PDCP entity.

As an embodiment, the SN11 or MN01 may instruct the terminal 21 to associate the PDCP entity with the new DRB ID when the PDCP entity is re-established, for example, the re-established configuration information of the PDCP entity includes the new DRB ID, and the terminal 21 may associate the PDCP entity with the new DRB ID when the PDCP entity is re-established.

As a second embodiment, the SN11 or MN01 may determine whether the PDCP entity needs to be associated with the new DRB ID by the terminal 21 without sending the indication information to the terminal 21.

The terminal 21 may determine whether the first configuration information of the first bearer and the second configuration information of the first bearer include the released configuration information of one entity corresponding to the original DRB ID and the added configuration information of another entity corresponding to the new DRB ID, and when the configuration information exists, it indicates that the DRB ID of the first bearer changes, and when the terminal 21 reestablishes the PDCP entity, the PDCP entity needs to be associated with the new DRB ID.

(2) The first configuration information of the first bearer includes configuration information of a release of an entity corresponding to the original DRB ID and configuration information of an addition of another entity corresponding to the new DRB ID.

(3) The second configuration information of the first bearer includes the released configuration information of an entity corresponding to the original DRB ID, and the first configuration information of the first bearer includes the added configuration information of another entity corresponding to the new DRB ID.

(4) The first configuration information of the first bearer includes the released configuration information of an entity corresponding to the original DRB ID, and the second configuration information of the first bearer includes the added configuration information of another entity corresponding to the new DRB ID.

Other contents in the scheme can refer to the related contents in fig. 9-11, such as S906 and S1005, etc.

In the above-mentioned scheme introduced from the interaction between MN01, SN11 and the terminal 21 in the embodiment of the present application, MN01 and SN11 may adopt CU-DU architecture, for example, MN01 includes CU0111 and DU0121, and SN11 includes CU1111 and DU 1121. In the architecture of the CU-DU, part of the protocol layers may be deployed on the CU, and part of the protocol layers may be deployed on the DU, and the following description will take the example that the PDCP layer is deployed on the CU, and the RLC layer, the MAC layer, and the physical layer are deployed on the DU.

It is understood that the configuration information of the PDCP entity in the above scheme may be generated by the CU, and the configuration information of the RLC entity and the logical channel may be generated by the DU.

Information interaction between MN01 and SN11 can be done by CU0111 and CU 1111.

Information interaction between the MN01 and the terminal 21 may be performed by the DU0121 and the terminal 21, and information interaction between the SN11 and the terminal 21 may be performed by the DU1121 and the terminal 21.

Optionally, CU1111 determines a new DRB ID of the first bearer, and CU1111 may send the new DRB ID of the first bearer to DU 1121.

Optionally, one or more candidate DRB IDs may be received from CU0111 before CU1111 determines the new DRB ID for the first bearer.

Optionally, the CU1111 may send, in addition to the new DRB ID of the first bearer to the DU1121, indication information that the new DRB ID corresponds to the first bearer to the DU1121, where the indication information may be an E-RAB ID (when the core network element 31 is an EPC), or the indication information may be an original DRB ID (when the core network element 31 is a 5GC), or the indication information may be other indication information that is displayed or implicit, which is not limited in this embodiment of the application.

Optionally, the CU1111 and the DU1121 may generate first configuration information of the first bearer, the CU1111 may generate configuration information of the PDCP entity according to the new DRB ID of the first bearer, and the DU1121 may generate configuration information of the SCG RLC entity and the SCG logical channel according to the new DRB ID of the first bearer.

Alternatively, the DU1121 may transmit configuration information of the SCG RLC entity and the SCG logical channel, which is generated according to the new DRB ID of the first bearer, to the CU1111, and the CU1111 transmits the first configuration information of the first bearer to the CU 0111.

Optionally, CU1111 may send the new DRB ID of the first bearer to CU 0111.

Optionally, CU1111 may send, in addition to sending the new DRB ID of the first bearer to CU0111, indication information that the new DRB ID corresponds to the first bearer to CU0111, where the indication information may be an E-RAB ID (when the core network element 31 is an EPC), or the indication information may be an original DRB ID (when the core network element 31 is a 5GC), or the indication information may be other indication information that is displayed or implicit, which is not limited in this embodiment of the present application.

Optionally, after CU0111 receives the new DRB ID of the first bearer from CU1111, CU0111 may send the new DRB ID of the first bearer to DU 0121.

Optionally, CU0111 may send, in addition to sending the new DRB ID of the first bearer to DU0121, to send, to DU0121, indication information that the new DRB ID corresponds to the first bearer, where the indication information may be an E-RAB ID (when core network element 31 is EPC), or the indication information may be an original DRB ID (when core network element 31 is 5GC), or the indication information may be other display or implicit indication information, which is not limited in this embodiment of the present application.

Optionally, CU0111 and DU0121 may generate second configuration information of the first bearer, CU0111 may generate configuration information of the PDCP entity according to the new DRB ID of the first bearer, and DU0121 may generate configuration information of the MCG RLC entity and the MCG logical channel according to the new DRB ID of the first bearer.

Alternatively, CU0111 may send, to DU0121, configuration information of the PDCP entity generated according to the new DRB ID of the first bearer, and the first configuration information of the first bearer received from CU 1111.

The DU0121 may transmit the first configuration information of the first bearer and the second configuration information of the first bearer to the terminal 21.

Optionally, when CU0111 generates the reconstructed configuration information of the PDCP for terminal 21, CU0111 may add indication information to the reconstructed configuration information of the PDCP, and associate the PDCP entity to the new DRB ID when indicating the reconstruction of the PDCP, for example, the reconstructed configuration information of the PDCP may carry the new DRB ID.

Optionally, when CU1111 generates the reconstructed configuration information of the PDCP for the terminal 21, CU1111 may add indication information to the reconstructed configuration information of the PDCP, and associate the PDCP entity to the new DRB ID when indicating the reconstruction of the PDCP, for example, the reconstructed configuration information of the PDCP may carry the new DRB ID.

For the content of the CU-DU architecture adopted by MN01 and SN11, reference may be made to other contents of the embodiments of the present application.

Fig. 12 is a schematic structural diagram of an apparatus 1200 according to an embodiment of the present disclosure.

The communication apparatus 1200 includes a processing unit 1201 and a communication unit 1202. Optionally, the communication device 1200 further includes a storage unit 1203. The processing unit 1201, the communication unit 1202, and the storage unit 1203 are connected by a communication bus.

The communication unit 1202 may be a device having a transceiving function for communicating with other network apparatuses or terminals.

The storage unit 1203 may include one or more memories.

The storage unit 1203 may be independent and connected to the processing unit 1201 through a communication bus. The storage unit 1203 may also be integrated with the processing unit 1201.

The communications apparatus 1200 may be used in a communications device, circuit, hardware component, or chip.

The communication apparatus 1200 may be MN01 or SN11 in the embodiment of the present application. A schematic diagram of MN01 or SN11 may be as shown in fig. 7 a. Optionally, the communication unit 1202 of the apparatus 1200 may include an antenna and a transceiver of an access network device, such as the antenna 1515 and the transceiver 1513 in fig. 7 a. The communication unit 1202 may also include a network interface of an access network device, such as network interface 1514 in fig. 7 a.

The communication apparatus 1200 may be a chip in MN01 or a chip in SN11 in the embodiment of the present application. The communication unit 1202 may be an input or output interface, pin or circuit, or the like. Optionally, the storage unit 1203 may store a computer-executable instruction of the method on the access network device side, so that the processing unit 1201 executes the method on the access network device side in the foregoing embodiment. The storage unit 1203 may be a register, a cache, a RAM, or the like, and the storage unit 1203 may be integrated with the processing unit 1201; the storage unit 1203 may be a ROM or other type of static storage device that may store static information and instructions, and the storage unit 1203 may be separate from the processing unit 1201. Alternatively, as wireless communication technology evolves, a transceiver may be integrated on the communication device 1200, e.g., the communication unit 1202 integrates the transceiver 1513 and the network interface 1514.

The communication apparatus 1200 may be the terminal 21 in the embodiment of the present application. Optionally, the communication unit 1202 of the apparatus 1200 may comprise an antenna and a transceiver of a terminal, such as the antenna 1616 and the transceiver 1612 in fig. 7 b. Optionally, the communication unit 1202 may also include output devices and input devices, such as output device 1614 and input device 1615 in fig. 7 b.

The communication apparatus 1200 may be a chip in the terminal 21 in the embodiment of the present application. The communication unit 1202 may be an input or output interface, pin or circuit, or the like. Alternatively, the storage unit 1203 may store computer-executable instructions of the method on the terminal side to cause the processing unit 1201 to execute the method of the terminal 21 in the above-described embodiment. The storage unit 1203 may be a register, a cache, a RAM, or the like, and the storage unit 1203 may be integrated with the processing unit 1201; the storage unit 1203 may be a ROM or other type of static storage device that may store static information and instructions, and the storage unit 1203 may be separate from the processing unit 1201. Alternatively, as wireless communication technology advances, a transceiver may be integrated with the communication device 1200, such as the communication unit 1202 integrated with the transceiver 1212.

When the communication apparatus 1200 is a chip in the SN11 or the SN11, the processing unit 1201 may perform the actions processed by the SN11 in the above method, the storage unit 1203 may perform the actions stored in the above method, and the communication unit 1202 may perform the actions interacting with the MN01 in the above method, as described in the following exemplary descriptions:

the communication unit 1202 may receive the original DRB ID and the one or more candidate DRB IDs of the first bearer from the MN01, and the communication unit 1202 may transmit a new DRB ID of the first bearer, which is one of the one or more candidate DRB IDs, to the MN 01.

Alternatively, the storage unit 1203 may store one or more candidate DRB IDs.

Optionally, the communication unit 1202 may further send an evolved universal terrestrial radio access bearer E-RAB ID of the first bearer or the original DRB of the first bearer to the MN 01.

Optionally, when the PDCP SN length of the first bearer changes, the processing unit 1201 may determine the new DRB ID of the first bearer.

Optionally, the processing unit 1201 may generate first configuration information of the first bearer, and the content of the first configuration information of the first bearer may refer to the content in other embodiments.

Alternatively, communication unit 1202 may send first configuration information of the first bearer to MN 01.

When the communication apparatus 1200 is a chip in MN01 or MN01, the processing unit 1201 may perform actions handled by MN01 in the above method, the storage unit 1203 may perform actions stored in the above method, and the communication unit 1202 may perform actions interacting with SN11 in the above method, as described in the following for example:

optionally, the communication unit 1202 may send the original data radio bearer DRB identification ID and the one or more candidate DRB IDs of the first bearer to the SN 11.

Optionally, the communication unit 1202 may receive a new DRB ID of the first bearer from the SN11, where the new DRB ID is one of the one or more candidate DRB IDs.

Optionally, the communication unit 1202 may receive an evolved universal terrestrial radio access bearer E-RAB ID of a first bearer or the original DRB of the first bearer from the SN 11.

Alternatively, the communication unit 1202 may receive the first configuration information of the first bearer from the SN11, and the content of the first configuration information of the first bearer may refer to that in other embodiments.

Optionally, the processing unit 1201 may generate the second configuration information of the first bearer, and the content of the second configuration information of the first bearer may refer to the content in other embodiments.

Alternatively, the communication unit 1202 may send the first configuration information of the first bearer and the second configuration information of the first bearer to the terminal 21.

When the communication apparatus 1200 is the terminal 21 or a chip in the terminal 21, the processing unit 1201 may perform the actions processed by the terminal 21 in the above method, the storage unit 1203 may perform the actions stored by the terminal 21 in the above method, and the communication unit 1202 may perform the actions interacting with the MN01 or the SN11 in the above method, which are exemplarily described as follows:

the communication unit 1202 may receive first configuration information of a first bearer and second configuration information of the first bearer.

The processing unit 1201 may associate the PDCP entity to the new DRB ID at PDCP re-establishment.

A communication apparatus 1300 according to an embodiment of the present application is described below. The communication device 1300 may be a chip in SN11 or SN 11. As shown in fig. 13:

communication apparatus 1300 includes a receiving unit 1301 and a transmitting unit 1302.

The receiving unit 1301 may be configured to receive, from the MN01, an original data radio bearer DRB identification ID and one or more candidate DRB IDs of a first bearer.

The sending unit 1302 may be configured to send a new DRB ID of the first bearer to the MN01, where the new DRB ID is one of the one or more candidate DRB IDs.

Optionally, the sending unit 1302 may be further configured to send an evolved universal terrestrial radio access bearer E-RAB ID of the first bearer or the original DRB of the first bearer to the MN 01.

Optionally, the communication apparatus 1300 further includes a determining unit 1303, where the determining unit 1303 is configured to determine the new DRB ID of the first bearer when the PDCP SN length of the first bearer changes, or the determining unit 1303 is configured to determine the new DRB ID of the first bearer when the PDCP anchor of the first bearer changes and the PDCP SN length of the first bearer does not change.

Optionally, the communication apparatus 1300 further includes a generating unit 1304, where the generating unit 1304 is configured to generate the first configuration information of the first bearer, and the content of the first configuration information of the first bearer may refer to the content in other embodiments.

A communication apparatus 1400 according to an embodiment of the present application is described below. The communication device 1400 may be a chip in MN01 or MN 01. As shown in fig. 14:

the communication apparatus 1400 includes a transmission unit 1401 and a reception unit 1402.

The sending unit 1401 is configured to send the DRB identification ID of the original data radio bearer of the first bearer and one or more candidate DRB IDs to the SN11 point.

A receiving unit 1401 is configured to receive a new DRB ID of the first bearer from the SN11, where the new DRB ID is one of the one or more candidate DRB IDs.

Optionally, the receiving unit 1401 is further configured to receive, from the SN11, an evolved universal terrestrial radio access bearer E-RAB ID of the first bearer or the original DRB of the first bearer.

Optionally, the receiving unit 1401 is further configured to receive the first configuration information of the first bearer from the SN11, and the content of the first configuration information of the first bearer may refer to the content in other embodiments.

Optionally, the communication apparatus 1400 includes a generating unit 1403, where the generating unit 1403 is configured to generate the second configuration information of the first bearer, and the content of the second configuration information of the first bearer may refer to the content in other embodiments.

The sending unit 1401 is configured to send, to the terminal 21, first configuration information of the first bearer and second configuration information of the first bearer.

Having described the method flow diagrams of embodiments of the present application, it is to be understood that MN01 may have functional elements corresponding to the steps of the MN01 method or flow, and SN11 may have functional elements corresponding to the steps of the SN11 method or flow.

One or more of the above modules or units may be implemented in software, hardware or a combination of both.

When any of the above modules or units are implemented in software, which is present as computer program instructions and stored in a memory, a processor may be used to execute the program instructions to implement the above method flows.

Processors in the present application may include, but are not limited to, at least one of: various computing devices that run software, such as a Central Processing Unit (CPU), a microprocessor, a Digital Signal Processor (DSP), a Microcontroller (MCU), or an artificial intelligence processor, may each include one or more cores for executing software instructions to perform operations or processing. The processor may be a single semiconductor chip or integrated with other circuits to form a semiconductor chip, for example, an SoC (system on chip) with other circuits (such as a codec circuit, a hardware acceleration circuit, or various buses and interface circuits), or may be integrated in the ASIC as a built-in processor of the ASIC, which may be packaged separately or together with other circuits. The processor may further include necessary hardware accelerators such as Field Programmable Gate Arrays (FPGAs), PLDs (programmable logic devices), or logic circuits implementing dedicated logic operations, in addition to cores for executing software instructions to perform operations or processes.

The memory in the embodiment of the present application may include at least one of the following types: read-only memory (ROM) or other types of static memory devices that may store static information and instructions, Random Access Memory (RAM) or other types of dynamic memory devices that may store information and instructions, and Electrically erasable programmable read-only memory (EEPROM). In some scenarios, the memory may also be, but is not limited to, a compact disk-read-only memory (CD-ROM) or other optical disk storage, optical disk storage (including compact disk, laser disk, optical disk, digital versatile disk, blu-ray disk, etc.), magnetic disk storage media or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer.

The embodiment of the application also provides a computer readable storage medium. The methods described in the above method embodiments may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. If implemented in software, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Computer-readable media may include computer storage media and communication media, and may include any medium that can communicate a computer program from one place to another. A storage media may be any available media that can be accessed by a computer.

As an alternative design, a computer-readable medium may include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer. Also, any connection is properly termed a computer-readable medium. For example, if the software is transmitted from a network node, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, Digital Subscriber Line (DSL), or wireless technologies such as infrared, radio, and microwave, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of medium. Disk and disc, as used herein, includes Compact Disc (CD), laser disc, optical disc, Digital Versatile Disc (DVD), floppy disk and blu-ray disc where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above should also be included within the scope of computer-readable media.

The embodiment of the application also provides a computer program product. The methods described in the above method embodiments may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. If implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. The procedures or functions described in the above method embodiments are generated in whole or in part when the above computer program instructions are loaded and executed on a computer. The computer may be a general purpose computer, a special purpose computer, a computer network, a network appliance, a user device, or other programmable apparatus.

Claims

1. A method of communication in a multi-air-port dual-connection MR-DC, the method comprising:

receiving a DRB identification ID and one or more candidate DRB IDs of an original data radio bearer of a first bearer from a master node;

sending a new DRB ID of the first bearer to the master node, wherein the new DRB ID is one of the one or more candidate DRB IDs;

determining the new DRB ID of the first bearer when the PDCP SN length of the first bearer changes;

generating first configuration information of the first bearer, where the first configuration information of the first bearer includes configuration information of release of a PDCP entity corresponding to the original DRB ID and configuration information of addition of a PDCP entity corresponding to the new DRB ID;

and sending the first configuration information of the first bearer to the master node.

2. The method of claim 1, wherein the one or more candidate DRB IDs are candidate DRB IDs of the first bearer; or

The one or more candidate DRB IDs are candidate DRB IDs of a plurality of bearers, including the first bearer.

3. The method of claim 1, further comprising:

and sending an evolved universal terrestrial radio access bearer (E-RAB) ID of the first bearer or the original DRB of the first bearer to the master node.

4. The method of claim 1, wherein the first configuration information of the first bearer further comprises added configuration information of an SCG RLC entity corresponding to the new DRB ID.

5. The method of claim 4, wherein the reconstructed configuration information of the PDCP entity comprises the new DRB ID of the first bearer and the original DRB ID of the first bearer.

6. The method of claim 4, wherein the first configuration information of the first bearer further comprises added configuration information of an SCG RLC entity corresponding to the new DRB ID.

7. A method of communication in a multi-air-port dual-connection MR-DC, the method comprising:

sending the original data radio bearer DRB identification ID and one or more candidate DRB IDs of a first bearer to a secondary node;

receiving a new DRB ID of the first bearer from the secondary node, the new DRB ID being one of the one or more candidate DRB IDs;

receiving first configuration information of the first bearer from the secondary node, where the first configuration information of the first bearer includes configuration information of a release of a PDCP entity corresponding to the original DRB ID and configuration information of an addition of a PDCP entity corresponding to the new DRB ID.

8. The method of claim 7, wherein the one or more candidate DRB IDs are candidate DRB IDs of the first bearer; or

9. The method of claim 7, further comprising:

receiving, from the secondary node, an evolved universal terrestrial radio access bearer (E-RAB) ID of the first bearer or the original DRB of the first bearer.

10. The method of claim 7, wherein the first configuration information of the first bearer further comprises added configuration information of an SCG RLC entity corresponding to the new DRB ID.

11. The method of claim 7, further comprising:

and sending the first configuration information of the first bearer to a terminal.

12. The method according to any one of claims 7-11, further comprising:

generating second configuration information of the first bearer, where the second configuration information of the first bearer includes configuration information of release of an MCG RLC entity corresponding to an original DRB ID and configuration information of addition of an MCG RLC entity corresponding to a new DRB ID, or the second configuration information of the first bearer includes configuration information of release of an MCG RLC entity corresponding to an original DRB ID.

13. The method of claim 12, further comprising:

and sending the second configuration information of the first bearer to a terminal.

14. A communications apparatus comprising a processor coupled to a memory, the memory storing a computer program or instructions, the processor being configured to execute the computer program or instructions such that the method of any of claims 1 to 6 or the method of any of claims 7 to 13 is performed.

15. A computer storage medium characterized by storing a program for implementing the method of any one of claims 1 to 6 or the method of any one of claims 7 to 13.