WO2019242773A1

WO2019242773A1 - Communication method and communication device in multi-rat dual connectivity

Info

Publication number: WO2019242773A1
Application number: PCT/CN2019/092442
Authority: WO
Inventors: 彭文杰; 李冠臣; 熊新; 戴明增
Original assignee: 华为技术有限公司
Priority date: 2018-06-22
Filing date: 2019-06-23
Publication date: 2019-12-26
Also published as: CN110557783B; CN110557783A

Abstract

The present application provides a communication method, device and system in multi-RAT dual connectivity. According to the method, when a PDCP SN length of a bearer is changed, an SN sends a PDCP SN length change indication to an MN, so that the MN and the SN can generate a bearer release and added configuration information for a terminal, thereby completing the change of the PDCP SN length.

Description

Communication method and communication device in multi-standard dual connection

This application is required to be submitted to the State Intellectual Property Office of China on June 22, 2018, with an application number of 201810653785.0, and the application name is "a communication method and communication device in a multi-standard dual connection", and it shall be submitted on November 02, 2018 The priority of the Chinese patent application of the State Intellectual Property Office of the People's Republic of China, application number 201811302962.7, and application name "A communication method and communication device in a multi-standard dual connection", the entire contents of which are incorporated herein by reference.

Technical field

The present application relates to the field of wireless communication technologies, and in particular, to a communication method and device in a multi-standard dual connection.

Background technique

In order to improve the throughput of data transmission, dual connections supporting different access technologies are introduced. For example: Multi-RAT Dual Connectivity (MR-DC).

FIG. 1 is a schematic diagram of a dual-connection communication system. As shown in FIG. 1, the terminal 21 can communicate with the master node (MN) 01 and the secondary node (SN) 11 at the same time, MN01 and SN11 can be connected, and both the primary node A and the secondary node B can communicate with the core. The network element 31 is connected. MN01 and SN11 can use different access technologies.

MR-DC can include the following scenarios:

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

As shown in Figure 2, core network element 31 is an evolved packet core (EPC), MN01 is an evolved node (evolved universal terrestrial radio access network NodeB, eNB), and SN11 is a new air interface node (new radio node) nodeB, gNB).

MN01 and SN11 can be connected through the X2 interface, MN01 and SN11 can be connected through the user plane; MN01 and the core network element 31 can be connected through the S1 interface, MN01 and the core network element 31 can be connected through the user plane; SN11 and The core network element 31 may be connected through an S1-U interface, and the SN11 core network element 31 may 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)

As shown in FIG. 3, the core network element 31 is a fifth generation (5G, 5th Generation) core network (5G, 5GC), MN01 is an eNB, and SN11 is a gNB.

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

3. Dual connection of NR and E-UTRA (NR-E-UTRA Dual Connectivity, NG-DC)

As shown in FIG. 4, the core network element 31 is 5GC, MN01 is gNB, and SN11 is eNB.

MN01 and SN11 can be connected. For example, through the Xn interface, there can be a user plane connection between MN01 and SN11; MN01 can be connected with the core network element 31. For example, through the NG interface, MN01 and the core network element 31 can have a user plane. Connection; SN11 and core network element 31 can be connected, for example, through the NG-U interface, there can be a user plane connection between SN11 core network element 31.

In each of the above scenarios, from the perspective of MN01 and SN11, the user plane can have the following six types of bearers, as shown in Figure 5. The following behavior examples introduce the data flow of each bearer type. Those skilled in the art It can be understood that the uplink is similar to the downlink, and is not repeated here.

1. The MN terminated Master Cell Group (MCG) bearer.

Data is sent from the core network element 31 to MN01, which in turn passes the packet data convergence protocol (PDCP), radio link layer control protocol (Radio Link Control, RLC) layer and media access control (Media) of MN01. The Access Control (MAC) layer is sent to the terminal 21.

2. Secondary cell group (SCG) bearer terminated by MN.

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

3. MN terminated split bearer.

The data is sent from the core network element 31 to MN01, and the PDCP layer of MN101 splits the data. Part of the data is sent to the terminal 21 through the RLC and MAC entities of MN01 in turn, and the other part of the data is sent to the RLC layer of SN11 and then SN11 The RLC layer and the MAC layer are sent to the terminal 21.

4. Split bearer terminated by SN.

The data is sent from the core network element 31 to SN11. The PDCP layer of SN11 splits the data. Part of the data is sent to the terminal 21 through the RLC and MAC entities of SN11 in turn, and the other part of the data is sent to the RLC layer of MN101 and then MN101 The RLC layer and the MAC layer are sent to the terminal 21.

5. MCG bearer terminated by SN.

Data is sent from the core network element 31 to SN11, and then sent to the RLC layer of MN01 via the PDCP layer of SN11, and then sent to the terminal 21 via the RLC layer and MAC layer of MN01.

6. SN terminated SCG bearer.

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

The above MCG bearer relates to MCG air interface resources, the SCG bearer relates to SCG air interface resources, and the split bearer relates to MCG air interface resources and SCG air interface resources.

The PDCP entity of the bearer terminating in the MN is on the MN, and the PDCP entity of the bearer terminating in the SN is on the SN. Both the PDCP entity terminated in the MN and the PDCP entity terminated in the SN can be configured as NR PDCP entities. The NR PDCP entity may add a PDCP sequence number (SN) to each PDCP packet, and is used by the terminal 21 to sort the multiple PDCP packets according to the PDCP SN after receiving multiple PDCP packets. The length of the PDCP SN can have multiple possibilities. For example, the length of the PDCP SN can be 12 bits or 18 bits. How to change the PDCP SN length of the bearer is an urgent problem.

Summary of the Invention

The embodiments of the present application provide a communication method, device, and system in a multi-standard dual connection, which can change the length of the PDCP that is carried.

In a first aspect, an embodiment of the present application provides a communication method in a multi-standard dual connection. The method can be applied to a secondary node or a chip in a secondary node.

The method may include generating a second PDCP SN length configuration of the first bearer, and the second PDCP SN length configuration of the first bearer may indicate a second PDCP SN length of the first bearer; when the first PD When the PDCP SN length is different from the first PDCP SN length of the first bearer, a PDCP SN length change indication of the first bearer is generated; the PDCP SN length change indication of the first bearer is sent to the MN; wherein, the first The PDCP SN length is the PDCP SN length of the first bearer and the PDCP SN length before the second PDCP SN length.

The secondary node sends a PDCP SN length change instruction to the primary node, so that the primary node can learn that the PDCP SN length has changed, and the secondary node and the primary node can generate bearer release and increased configuration information for the terminal to complete the PDCP SN length change.

Optionally, in this method, when the PDCP SN length of the first bearer is the first PDCP SN length, the first bearer terminates at the SN.

Optionally, in this method, the bearer type of the first bearer in the PDCP SN length to the first PDCP SN length is the same as the bearer type of the first bearer in the PDCP SN length to the second PDCP SN length.

Optionally, in this method, the bearer type of the first bearer with a PDCP SN length of the first PDCP and SN length is different from the bearer type of the first bearer with a PDCP SN length of the second PDCP and SN length.

Optionally, the method is characterized in that the SN sends the PDCP SN length change indication of the first bearer to the MN, including:

The SN sends a secondary node modification request message or a secondary node modification request response message to the MN, and the secondary node modification request message includes the PDCP SN length indication of the first bearer.

Optionally, the method further includes: the SN generates first configuration information of the first bearer; and the SN sends the first configuration information of the first bearer to the MN. The first configuration information of the first bearer includes release and added configuration information of a PDCP entity.

Optionally, in the method, the first configuration information of the first bearer further includes release and added configuration information of an RLC entity.

Optionally, in the method, before the secondary node SN generates the second PDCP SN length configuration of the first bearer, the first bearer terminates at the MN; the method further includes: the SN receives the first PDCP SN length configuration from the MN The first PDCP SN length is configured to indicate the first PDCP SN length.

Optionally, in the method, the SN sends the PDCP SN length change indication of the first bearer to the MN, including: sending a secondary node modification request message or a secondary node modification request response message to the MN, the secondary node modification request message, or The secondary node modification request response message includes an indication of the PDCP SN length change of the first bearer.

Optionally, in the method, when the PDCP SN length of the first bearer is the length of the first PDCP SN, the first bearer is an MCG bearer terminated by the MN; the SN sends the PDCP SN of the first bearer to the MN The length change indication includes: the SN sends a secondary node increase request response message to the MN, and the secondary node increase request response message includes the PDCP SN length change indication of the first bearer.

Optionally, the method further includes: the SN generates first configuration information of the first bearer; the SN sends the first configuration information of the first bearer to the MN; the first configuration information of the first bearer includes a PDCP entity Added configuration information.

Optionally, the method further includes: the SN generates first configuration information of the first bearer; the SN sends the first configuration information of the first bearer to the MN; the first configuration information of the first bearer includes a PDCP entity Deleted and added configuration information.

In a second aspect, an embodiment of the present application provides a communication method in a multi-standard dual connection. The method can be applied to a secondary node or a chip in a secondary node.

The method includes: receiving a second PDCP SN length of a second bearer from the MN; before receiving the second PDCP SN length of the second bearer from the MN, the PDCP length of the second bearer is the first PDCP SN length; when the When the length of the second PDCP SN of the second bearer is different from the length of the first PDCP SN of the second bearer, it is determined that the PDCP SN length of the second bearer is changed.

The MN sends the second PDCP SN length to the SN. The SN can save the second PDCP SN length. The SN can autonomously determine whether the PDCP SN length has changed. When the PDCP SN length can be more than 12 bits and 18 bits, the PDCP SN length changes. There may be many possibilities, and the SN can determine whether the PDCP SN length has changed, so that the SN can generate the release and increase configuration information of the bearer for the terminal to complete the PDCP SN length change.

Optionally, in the method, when the second bearer has a PDCP SN length that is the first PDCP SN length, the second bearer ends at the MN; when the second bearer has a PDCP SN length that is the second PDCP SN length, The second bearer ends at the MN.

Optionally, in this method, the type of the second bearer with a PDCP SN length of the first PDCP SN length and the type of the second bearer with the PDCP SN length of the second PDCP SN length are the same.

Optionally, in this method, the type of the second bearer whose PDCP SN length is the length of the first PDCP SN and the type of the second bearer whose PDCP SN length is the second PDCP SN length are different.

Optionally, the method further includes: generating the first configuration information of the second bearer; the SN sends the first configuration information of the second bearer to the MN; the first configuration information of the second bearer includes the release of the RLC entity And added configuration information.

Optionally, in the method, when the second bearer has a PDCP SN length that is the first PDCP SN length, the second bearer terminates at the SN; when the second bearer has a PDCP SN length that is the second PDCP SN length, The second bearer ends at the MN; the method further includes: the SN sends the first PDCP SN length to the MN.

Optionally, the method further includes: the SN generates first configuration information of the second bearer; the SN sends the first configuration information of the second bearer to the MN; the second configuration information of the second bearer includes a PDCP entity Released configuration information.

Optionally, the method is characterized in that the first configuration information of the second bearer further includes release and added configuration information of the RLC entity.

Optionally, the method further includes: the SN generates the first configuration information of the second bearer; the SN sends the first configuration information of the second bearer to the MN; the second configuration information of the second bearer includes the RLC entity Release and added configuration information.

In a third aspect, an embodiment of the present application provides a communication method in a multi-system dual connection, which can be applied to a master node or a chip in the master node.

The method includes: receiving a PDCP SN length change indication of a first bearer from an SN; and storing the PDCP SN length change indication of the first bearer.

By receiving the PDCP SN length change instruction from the secondary node through the primary node, the primary node can be informed that the PDCP SN length has changed, so that the secondary node and the primary node can generate bearer release and increased configuration information for the terminal, thereby completing the PDCP SN length change.

Optionally, in this method, before the PDCP SN length of the first bearer changes, the first bearer ends at the SN.

Optionally, in this method, the bearer type of the first bearer before the PDCP SN length changes and the bearer type of the first bearer after the PDCP SN length changes are the same.

Optionally, in this method, the bearer type of the first bearer before the PDCP SN length changes and the bearer type of the first bearer after the PDCP SN length changes are different.

Optionally, the method further includes: the MN receives the SN configuration information of the first bearer from the SN; and the MN sends the SN configuration information of the first bearer to the UE. The first configuration information of the first bearer includes release and added configuration information of the PDCP entity.

Optionally, the method further includes: generating the second configuration information of the first bearer according to the PDCP SN length change indication of the first bearer; sending the second configuration information of the first bearer to the terminal; the first The second configuration information carried includes release and added configuration information of the RLC entity.

Optionally, in the method, before the PDCP and SN lengths of the first bearer change, the first bearer ends at the MN;

The method further includes: the MN sends the PDCP SN length before the PDCP SN length of the first bearer is changed to the SN.

Optionally, in the method, the first configuration information of the first bearer includes added configuration information of a PDCP entity.

Optionally, in the method, the first configuration information of the first bearer includes release and added configuration information of the RLC entity.

Optionally, the method further includes: generating the second configuration information of the first bearer according to the PDCP SN length change indication of the first bearer; sending the second configuration information of the first bearer to the terminal; the first The second configuration information carried includes release configuration information of the PDCP entity.

Optionally, the method further includes: the MN generates second configuration information of the first bearer according to the PDCP SN length change indication of the first bearer; the MN sends the second configuration information of the first bearer to the terminal; the The second configuration information of the first bearer includes the release and added configuration information of the PDCP entity.

Optionally, in the method, the second configuration information of the first bearer further includes release and added configuration information of the RLC entity.

In a fourth aspect, an embodiment of the present application provides a communication method in a multi-standard dual connection, which can be applied to a master node or a chip in the master node.

The method includes: generating a second PDCP SN length of the second bearer; before generating the second PDCP SN length of the second bearer, the PDCP SN length of the second bearer is the first PDCP SN length; when the second bearer When the second PDCP SN length is different from the first PDCP SN length of the second bearer, it is determined that the PDCP SN length of the second bearer is changed.

The MN can autonomously determine whether the PDCP SN length has changed. When the PDCP SN length is not only 12bit or 18bit, there can be many possibilities for the PDCP SN length change. The MN can determine whether the PDCP SN length has changed, thereby The MN can generate the release of the bearer and the added configuration information for the terminal to complete the PDCP SN length change.

Optionally, in this method, when the length of the second bearer in the PDCP SN is the length of the first PDCP SN, the second bearer ends at the MN.

Optionally, the method further includes: receiving first configuration information of the second bearer from the SN; the first configuration information of the second bearer includes release and added configuration information of the RLC entity.

Optionally, the method further includes: generating second configuration information of the second bearer; the second configuration information of the second bearer includes release and added configuration information of the PDCP entity.

Optionally, in the method, the second configuration information of the second bearer further includes release and added configuration information of the RLC entity.

Optionally, in the method, when the length of the second bearer in the PDCP SN is the length of the first PDCP SN, the second bearer terminates in the SN; the method further includes: receiving the first PDCP SN length from the SN. The SN may carry the first PDCP SN length in a cell that the MN can read, and the MN may read the first PDCP SN length. Optionally, the MN may save the first PDCP SN length. The first PDCP SN length is sent to the MN through the SN, the MN reads the first PDCP SN length, and the MN can autonomously determine whether the PDCP SN length has changed.

Optionally, the method further includes: receiving the first configuration information of the second bearer from the SN; the first configuration information of the second bearer includes the released configuration information of the PDCP entity.

Optionally, the method further includes: the first configuration information of the second bearer includes release and added configuration information of the RLC entity.

Optionally, the method further includes: generating second configuration information of the second bearer; the second configuration information of the second bearer includes added configuration information of a PDCP entity.

Optionally, in the method, the second configuration information of the second bearer includes release and added configuration information of the RLC entity.

In a fifth aspect, an embodiment of the present application provides a communication device that can be applied to a secondary node or a chip in the secondary node. The communication device includes a memory and a processor. The memory is used to store a computer program, and the processor is used to call and run the computer program from the memory, so that the method of the first aspect or the second aspect described above.

In a sixth aspect, an embodiment of the present application provides a communication device that can be applied to a master node or a chip in the master node. The communication device includes a memory and a processor. The memory is used to store a computer program, and the processor is used to call and run the computer program from the memory, so that the method of the third aspect or the fourth aspect described above.

In a seventh aspect, an embodiment of the present application provides a computer storage medium that stores a program for implementing the method of the first aspect or the second aspect. When the program runs in a wireless communication device, the wireless communication device is caused to execute the method of the first aspect or the second aspect.

In an eighth aspect, an embodiment of the present application provides a computer storage medium that stores a program for implementing the method of the first aspect or the second aspect. When the program runs in a wireless communication device, the wireless communication device is caused to execute the method of the third aspect or the fourth aspect described above.

In a ninth aspect, an embodiment of the present application provides a computer program product. The program product includes a program that, when the program is executed, causes the foregoing method of the first aspect or the second aspect to be executed.

According to a tenth aspect, an embodiment of the present application provides a computer program product. The program product includes a program, and when the program is executed, the method of the third aspect or the fourth aspect is executed.

BRIEF DESCRIPTION OF THE DRAWINGS

In order to explain the present application more clearly, the accompanying drawings used in the description of the embodiments are briefly introduced below. Obviously, the accompanying drawings in the following description are only some embodiments of the present invention. In terms of creative work, other drawings can be obtained based on these drawings.

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

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

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

FIG. 4 is a schematic diagram of an NG-DC;

5 is a schematic diagram of a user plane bearer type in MR-DC;

FIG. 6a is a schematic diagram of a CU-DU architecture with MN01;

6b is a schematic diagram of a CU-DU architecture with SN11;

FIG. 7 is a schematic diagram of a CU-DU architecture in which MN01 and SN11 are both;

FIG. 8 is a schematic diagram of an embodiment of changing a PDCP SN length;

FIG. 9 is a schematic diagram of an embodiment of changing a PDCP SN length;

FIG. 10 is a schematic diagram of another embodiment of changing the length of PDCP and SN;

FIG. 11 is a schematic diagram of another embodiment of changing a PDCP SN length;

FIG. 12a is a schematic diagram of another embodiment of changing the length of the PDCP and SN;

12b is a schematic diagram of another embodiment of changing the length of the PDCP and SN;

FIG. 13 is a schematic diagram of another embodiment of changing the length of PDCP and SN;

FIG. 14 is a schematic diagram of an implementation manner of changing a PDCP SN length under a CU-DU architecture; FIG.

15 is a schematic structural diagram of an access network device;

16 is a schematic structural diagram of a terminal;

FIG. 17 is a schematic structural diagram of a device 1700;

FIG. 18 is a schematic diagram of another embodiment of changing the length of PDCP and SN;

FIG. 19 is a schematic diagram of another embodiment of changing a PDCP SN length;

FIG. 20 is a schematic diagram of another embodiment of changing the length of PDCP and SN.

detailed description

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

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

As shown in FIG. 6a, when MN01 is a gNB, MN01 can be a Centralized Unit (CU) -Distributed Unit (DU) architecture, and MN01 can include CU0111 and DU0121. For example, in NG DC, MN01 is a gNB, MN01 can be a CU-DU architecture, and MN01 can include CU0111 and DU0121. CU0111 is connected to DU0121, for example, through the F1 interface, and CU0111 is connected to the core network element 31, for example, through the NG interface. Figure 6a illustrates one CU0111 and DU0121 as an example. In the embodiment of this application, there may be multiple DU0121 The multiple DU0121s can share one CU0111, and the multiple DU0121s are all connected to CU0111, for example, through an F1 interface.

As shown in Figure 6b, when SN11 is a gNB, SN11 can be a CU-DU architecture, and SN11 can include CU1111 and DU1121. For example, in EN-DC or NGEN-DC, SN11 is a gNB and SN11 can be a CU-DU architecture. , SN11 can include CU1111 and DU1121. CU1111 and DU1121 are connected, for example, through the F1 interface, and CU1111 is connected to the core network element 31, for example, through the NG interface. Figure 6b illustrates one CU1111 and DU1121 as an example. In the embodiment of this application, there may be multiple DU1121. The multiple DU1121s can share one CU1111, and the multiple DU1121s are all connected to the CU1111, for example, through an F1 interface.

As shown in Figure 7, when both MN01 and SN11 are CU-DU architectures, CU0111 and CU1111 can be connected.

Under the CU-DU architecture, some functions of MN01 are deployed on CU0111, and other functions of MN01 are deployed on DU0121. The functional division of CU0111 and DU0121 can be divided according to the wireless protocol stack. One possible way is to deploy radio resource control (RRC), service data adaptation (SDAP) layer, and packet data convergence protocol (PDCP) layer at CU0111; wireless A link layer control protocol (Radio Link Control, RLC), media access control (MAC), and physical layer (PHY) are deployed in DU0121. Another possible way is to deploy RRC, PDCP, RLC, SDAP and MAC and part of the physical layer on CU0111 and part of the physical layer on DU0121. It should be noted that the above function division is only an example, and there may be other division manners, which are not limited in the embodiment of the present application.

When the SN11 adopts the CU-DU architecture, the functions and functional division of CU1111 and DU1121 can refer to the related content of the functions and functional division of CU0111 and DU0121 when the MN01 adopts the CU-DU architecture, which will not be repeated here.

In the above communication system, when the bearer ends at MN01 (or SN11), MN01 (or SN11) can change the PDCP SN length.

The embodiment of the present application provides a solution. In this solution, when the PDCP SN length of a bearer is changed, the bearer performs release and increase. In this solution, when the length of the PDCP SN changes, the interaction between MN01 and SN11 enables both MN01 and SN11 to know that the PDCP SN length has changed, thereby ensuring that MN01 and the terminal 21 can generate bearer release and increased configuration information for the terminal 21 at the same time. To complete the PDCP SN length change.

The above scheme may specifically include the first scheme, the second scheme, and the third scheme. In the first scenario, SN11 can generate a new PDCP SN length for the PDCP anchor bearer on SN11. When the new PDCP SN length changes compared to the previous PDCP SN length, SN11 sends the PDCP SN length to MN01. The change indication, and then MN01 and SN11 generate the release and addition configuration information of the bearer for the terminal 21. In the second solution, SN11 can send the PDCP SN length to MN01, and MN01 and SN11 can save the PDCP SN length. When the PDCP SN length changes, MN01 and SN11 generate terminal bearer release and increase configuration information. In the third solution, corresponding to a bearer type, a PDCP SN length can be fixedly used. When the bearer type changes, MN01 and SN11 can learn that the PDCP SN length has changed, thereby generating the release of the bearer for the terminal 21. And added configuration information.

The following may explain the words that may appear in the embodiments of the present application.

1. Generating the PDCP SN length of the first bearer can be understood as generating the PDCP SN length configuration information of the first bearer, and the PDCP SN length configuration of the first bearer can indicate the PDCP SN length of the first bearer. Sending or receiving the PDCP SN length of the first bearer can be understood as sending or receiving the PDCP SN length configuration information of the first bearer, and the PDCP SN length configuration of the first bearer can indicate the PDCP SN length of the first bearer.

2. The PDCP entity of the first bearer can be understood on the MN (or SN) as the PDCP anchor point of the first bearer on the MN (or) SN; or, the first bearer terminates on the MN (or SN); or, the MN ( Or a SN) PDCP entity exists on the first bearer, or a PDCP entity exists on the MN (or SN) on the first bearer.

The RLC entity (or MAC entity) where the first bearer exists on the MN (or SN) can be understood as the existence of the RLC entity (or MAC entity) on the MN (or SN).

3. The configuration information of the first bearer may include configuration information of one or more entities of the PDCP entity, the RLC entity, and the MAC entity of the first bearer. Different entities may have different names for entity operations, such as release or addition, and this embodiment of the present application does not limit this. For example, the increase of the MAC entity can be understood as the increase of the logical channel; or the release of the MAC entity can be understood as the release of the logical channel or the reset of the MAC entity.

The first scheme is described below first.

FIG. 8 is a schematic diagram of an embodiment of changing the length of PDCP and SN.

S801: SN11 generates a second PDCP SN length of the first bearer. This may be referred to as SN11 generating the second PDCP SN length configuration information of the first bearer.

Because the node where the PDCP entity of the bearer can generate PDCP SN, those skilled in the art can understand that when the length of the PDCP SN of the first bearer is the second PDCP SN, the PDCP entity of the first bearer is on SN11, that is, the first bearer is terminated SN.

S802: When the length of the second PDCP SN of the first bearer is different from the length of the first PDCP SN of the first bearer, the SN generates a PDCP SN length change indication of the first bearer.

The PDCP SN length change indication of the first bearer may indicate that the PDCP SN length of the first bearer has changed.

Wherein, before the length of the PDCP SN of the first bearer is before the length of the second PDCP SN, the length of the PDCP SN of the first bearer may be the length of the first PDCP SN. It can be understood that the second PDCP SN length of the first bearer is generated or determined at SN11. Before, the length of the PDCP SN of the first bearer was the length of the first PDCP SN. It can also be understood that before the length of the PDCP SN of the first bearer changes, the length of the PDCP SN of the first bearer is the length of the first PDCP SN, and the PDCP of the first bearer SN After the length is changed, the PDCP SN length of the first bearer is the second PDCP SN length.

As a first embodiment, when the length of the PDCP and SN of the first bearer is the length of the first PDCP and SN, the first bearer terminates at the SN. In other words, before the PDCP SN length of the first bearer changes, the PDCP entity of the first bearer is on SN11. SN11 can store the PDCP length of the first bearer. The PDCP configuration of the first PDCP SN length, such as the first PDCP. SN length, SN11 can read the first PDCP SN length, and then compare it with the second PDCP SN length, and generate a PDCP SN length change indication for the first bearer if they are not consistent.

In the first embodiment, before and after the PDCP SN length of the first bearer is changed, the first bearer is terminated at the SN, that is, the PDCP entities of the first bearer are all at SN11. Specifically, it may include but is not limited to the following possibilities: (1) The first bearer bears the same type before and after the PDCP SN length changes. For example, the first bearer bears the type before the PDCP SN length changes and after the PDCP SN length changes. MCG bearer, SN-terminated SCG bearer or SN-terminated split bearer; (2) the first bearer has a different bearer type before and after the SN length change, for example, the bearer type of the first bearer before the PDCP SN length change is SN-terminated MCG bearer, the first bearer type after PDCP SN length change is SN terminated SCG bearer or SN terminated split bearer; or, the first bearer before PDCP SN length change is SN terminated SCG bearer. A bearer whose PDCP SN length changes is a SN-terminated MCG bearer or a SN-terminated split bearer; or, the first bearer before the PDCP SN length is changed is an SN-terminated split bearer, and the first bearer is in PDCP The bearer type after SN length change is SN terminated MCG bearer or SN terminated SCG bearer.

As a second implementation manner, when the length of the first PDCP and the SN is the length of the first PDCP and the SN, the first bearer ends at the MN. That is, before the first bearer PDCP SN length changes, the PDCP entity of the first bearer is on MN01, and MN01 can store the PDCP length of the first bearer PDCP and the PDCP related configuration of the first PDCP SN length, such as the first PDCP SN length, MN01 can read the first PDCP SN length, and then MN01 sends the first PDCP SN length to SN11. After SN11 receives the first PDCP SN length, it compares it with the second PDCP SN length, and generates a PDCP SN length change indication.

In the second embodiment, the first bearer ends at the MN before the PDCP SN length changes, and the first bearer ends at the SN after the PDCP SN length changes. Specifically, it may include but is not limited to the following possibilities: For example, the bearer type of the first bearer before the PDCP SN length change is an MN terminated MCG bearer, the bearer type of the first bearer after the PDCP SN length change is an SN terminated MCG bearer, SN-terminated SCG bearer or SN-terminated split bearer; or, the bearer type of the first bearer before the PDCP SN length change is the MN-terminated SCG bearer, and the first bearer after the PDCP SN length change is the SN-terminated MCG Bearer, SN-terminated SCG bearer, or SN-terminated split bearer; or, the bearer type of the first bearer before the PDCP SN length change is the MN-terminated split bearer, and the first bearer after the PDCP SN length change is the SN-terminated MCG bearer, SN terminated SCG bearer, or SN terminated split bearer.

S803: SN11 sends a PDCP SN length change indication of the first bearer to MN01.

In the first embodiment, a secondary node modification request message (SN modification request) or a secondary node modification request response (SN modification request request) message may carry a PDCP SN length indication of the first bearer.

In the second implementation manner, the secondary node may add a request response message (SN addition request knowledge), the secondary node modify the request message, or the modification request response message carrying the PDCP SN length indication of the first bearer. For example, when the first bearer is an MCG bearer terminated by the MN before the PDCP SN length changes, the secondary node may also add a request response message or the secondary node modification request response message to carry the PDCP SN length change indication of the first bearer.

Optionally, MN01 can save after receiving the PDCP SN length change instruction sent by SN11.

Optionally, MN01 can learn the new PDCP SN length according to the PDCP SN length change instruction, such as the second PDCP SN length, and MN01 can save the second PDCP SN length, so that MN01 can determine whether the PDCP SN length has changed in the future.

Optionally, S804-S806 can also be included.

S804: SN11 generates first configuration information of the first bearer.

Optionally, S804 may occur simultaneously with S801, that is, when SN11 generates the second PDCP SN length of the first bearer, the first configuration information of the first bearer may be generated.

As a first example of the first embodiment, the first configuration information includes release and added configuration information of a PDCP entity.

The first configuration information includes the release and added configuration information of the PDCP entity, which can be implemented by a cell including both the release and added configuration information of the PDCP entity. Specifically, the identifier can be deleted and added in a cell. It is implemented by a same identifier, and the identifier may be a bearer identifier. For example, when SN11 is gNB, for example, in the EN-DC or NGEN-DC scenario, it can be implemented by using the RadioBearerConfig cell in section 6.3.2 of 3GPP TS38.331V15.1.0. The first configuration information may include RadioBearerConfig, and RadioBearerConfig includes The release configuration information of the PDCP entity, for example, the DRB-ToReleaseList in RadioBearerConfig includes the bearer identifier 1, and the RadioBearerConfig includes the added configuration information of the PDCP entity, for example, the DRB-ToAddMod in the RadioBearerConfig includes the bearer identifier 1. By deleting and adding the same bearer identifier, the PDCP entity of a bearer can be deleted and then added in a configuration message, so that the PDCP SN length can be changed.

For example, the first configuration information includes the release and added configuration information of the PDCP entity, and may include the possibility of the first bearer type listed in the first embodiment in S802 before and after the PDCP SN length changes.

As a second example of the first embodiment, based on the first example of the first embodiment described above, the first configuration information may further include release and added configuration information of the RLC entity.

The first configuration information includes the release and added configuration information of the RLC entity, which can be implemented by one cell including both the release and added configuration information of the RLC entity. Specifically, the identifier can be deleted and added in a cell. It is implemented by a same identifier, and the identifier may be a bearer identifier or a logical channel identifier. For example, when SN11 is gNB, for example, in the EN-DC or NGEN-DC scenario, it can be implemented by using the CellGroupConfig cell in section 6.3.2 of 3GPP TS38.331V15.1.0. The first configuration information may include CellGroupConfig, and CellGroupConfig includes Release configuration information of the RLC entity, for example, rlc-BearerToReleaseList in CellGroupConfig includes logical channel identification 1, and CellGroupConfig includes added configuration information of the RLC entity, for example, rlc-BearerToAddModList in CellGroupConfig includes logical channel identification 1. For example, when SN11 is an eNB, for example, in the NE-DC scenario, it can be implemented by using the RadioResourceConfigDedicated cell in section 6.3.2 of 3GPP TS36.331V15.1.0. The first configuration information can include RadioResourceConfigDedicated, DRB-ToReleaseList in RadioResourceConfigDedicated The bearer identifier 1 is included, and the DRB-ToAddMod includes the bearer identifier 1. By deleting and adding the same logical channel identifier or bearer identifier, the process of deleting a bearer RLC entity and then adding it in a configuration message can be achieved, thereby realizing a change in PDCP SN length.

For example, the first configuration information including the release and added configuration information of the RLC entity may include, but is not limited to, the possibility that the bearer type of the first bearer before the PDCP SN length change is an SN terminated SCG bearer, and the first bearer is in the PDCP SN The bearer type after the length change is an SN-terminated SCG bearer or the SN-terminated split bearer; or, the bearer type before the PDCP SN length change is the SN-terminated split bearer, and the first bearer is the PDCP SN-length changed The bearer type is an SN terminated SCG bearer or an SN terminated split bearer.

In the first embodiment, the first configuration information may be carried by the secondary node modification request response message or the secondary node modification request message.

As a first example of the second implementation manner, the first configuration information includes added configuration information of a PDCP entity.

The first configuration information includes the added configuration information of the PDCP entity, which can be achieved by including the added configuration information of the PDCP entity in a cell, for example, it can be implemented by adding an identifier in a cell, and the identifier can be a bearer identifier. . For example, it can be implemented using the RadioBearerConfig cell in section 6.3.2 of 3GPP TS38.331V15.1.0. The first configuration information can include RadioBearerConfig, and RadioBearerConfig includes the added configuration information of the PDCP entity. For example, DRB-ToAddMod in the RadioBearerConfig cell includes Bearer ID 1.

It should be noted that at this time, the first configuration information may not include the release configuration information of the PDCP entity. Before the PDCP SN length is changed, the PDCP entity of the first bearer is on MN01, and the MN01 can generate the PDCP entity release for the terminal 21 Configuration information.

For example, the first configuration information includes added configuration information of the PDCP entity, and may include the possibility of the first bearer type listed in the second embodiment in S802 before and after the PDCP SN length changes.

As a second example of the second implementation manner, the first configuration information includes release and added configuration information of a PDCP entity.

For reference, in the first example of the first embodiment, the first configuration information includes related content in the release and added configuration information of the PDCP entity, and details are not described herein again.

It should be noted that because the PDCP entity of the first bearer is on MN01 before the PDCP SN length is changed, and the PDCP entity of the first bearer is on SN11 after the PDCP SN length is changed, and the PDCP entity of MN01 and the PDCP entity of SN11 are both You can configure PDCP entities of the same standard, such as NR and PDCP entities. At this time, the release and added configuration information of the PDCP entity can be generated directly by SN11. At this time, MN01 does not need to generate the release configuration information of the PDCP entity for the terminal 21, which can simplify the network. And terminal implementation complexity.

As a third example in the second embodiment, based on the first example of the second embodiment and the second example of the second embodiment, the first configuration information may further include an RLC entity. Release and added configuration information.

For reference, in the second example of the first embodiment, the first configuration information includes related content in the release and added configuration information of the RLC entity, and details are not described herein again.

For example, the first configuration information includes the release and added configuration information of the RLC entity, and may include but is not limited to the possibility that the bearer type of the first bearer before the SN length change is an SCG bearer terminated by the MN, and the first bearer is in the PDCP. The bearer type after SN length change is SN terminated SCG bearer or SN terminated split bearer; or, the first bearer before PDSN SN length change bearer type is MN terminated split bearer, the first bearer after PDCP SN length change The bearer type is an SN terminated SCG bearer or an SN terminated split bearer.

In the second embodiment, the secondary node may add a request response message, and the secondary node modification request response message carries the first configuration information. For example, when the first bearer is an MCG bearer terminated by the MN before the PDCP SN length changes, the secondary node may also add a request response message or the secondary node modification request response message to carry the first configuration information.

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

Optionally, S803 and S805 may occur simultaneously. For example, the PDCP SN length change indication of the first bearer may be carried in the same message as the first configuration information of the first bearer and sent by SN11 to MN01.

S806: MN01 sends the first configuration information of the first bearer to the terminal 21.

For example, the MN01 may send an RRC connection reconfiguration message to the terminal 21, and the RRC connection reconfiguration message includes the first configuration information of the first bearer.

Optionally, S807-S808 can also be included.

S807: MN01 generates second configuration information of the first bearer according to the PDCP SN length change indication of the first bearer.

As an example of the first embodiment, the second configuration information includes configuration information of RLC release and addition.

The second configuration information includes the release and added configuration information of the RLC entity, which can be implemented by one cell including both the release and added configuration information of the RLC entity. Specifically, the identifier can be deleted and added in a cell. It is implemented by a same identifier, and the identifier may be a bearer identifier or a logical channel identifier. For example, when MN01 is a gNB, for example, in the NE-DC scenario, it can be implemented by using the CellGroupConfig cell in section 6.3.2 of 3GPP TS38.331V15.1.0. The first configuration information may include CellGroupConfig, and CellGroupConfig includes the release of the RLC entity. Configuration information, for example, rlc-BearerToReleaseList in CellGroupConfig includes logical channel identification 1, and CellGroupConfig includes added configuration information for RLC entities, for example, rlc-BearerToAddModList in CellGroupConfig includes logical channel identification 1. For example, when MN01 is an eNB, for example, in the EN-DC or NGEN-DC scenario, it can be implemented by using the RadioResourceConfigDedicated cell in section 6.3.2 of 3GPP TS36.331V15.1.0. The second configuration information can include RadioResourceConfigDedicated and RadioResourceConfigDedicated. The DRB-ToReleaseList includes the bearer identifier 1, and the DRB-ToAddMod includes the bearer identifier 1. By deleting and adding the same logical channel identifier or bearer identifier, it is possible to complete the process of deleting a bearer RLC entity and then adding it in a configuration message, thereby realizing the change of the PDCP SN length.

For example, the second configuration information includes the release and added configuration information of the RLC entity, and may include, but is not limited to, the possibility that the first bearer is a SN terminated MCG bearer before the SN length changes, and the first bearer is a PDCP The bearer type after SN length change is SN terminated MCG bearer or SN terminated split bearer. The first bearer type before PDSN is the SN terminated split bearer. The first bearer is PDCP after SN length change. MCG bearer terminated by SN or split bearer terminated by SN.

As a first example of the second implementation manner, the second configuration information includes configuration information of release of a PDCP entity.

The second configuration information includes the release configuration information of the PDCP entity, which can be implemented by one cell including the release configuration information of the PDCP entity. Specifically, it can be implemented by deleting an identifier in a cell, and the identifier can be Bearer ID. For example, it can be implemented using the RadioBearerConfig information element in section 6.3.2 of 3GPP TS38.331V15.1.0. The second configuration information may include RadioBearerConfig, RadioBearerConfig includes the release configuration information of the PDCP entity, for example, DRB-ToReleaseList in the RadioBearerConfig information element includes The bearer identifier 1 can implement the processing of deleting a bearer RLC entity and then adding it in a configuration message, thereby realizing the change of the PDCP SN length.

It should be noted that because the PDCP entity of the first bearer is on MN01 before the PDCP SN length is changed, and the PDCP entity of the first bearer is on SN11 after the PDCP SN length is changed, the MN01 can generate the PDCP entity release for the terminal 21 The configuration information of the PDCP entity is added by the SN11 to the terminal 21 for the PDCP entity. For example, under the possibility that the first bearer listed in the second embodiment of S802 bears before and after the PDCP SN length changes, the second configuration information may include the release configuration information of the PDCP entity,

As a second example of the second embodiment, based on the first example of the second embodiment, the second configuration information may further include release and added configuration information of the RLC entity.

For reference, in an example of the first implementation manner in S807, the second configuration information includes related content of RLC release and added configuration information, and details are not described herein again.

For example, in the following possibility of the bearer type before and after the PDCP SN length changes, the second configuration information may also include the release and added configuration information of the RLC entity: the bearer type of the first bearer before the PDCP SN length change is MN terminated MCG bearer, the first bearer bearer type after PDCP SN length change is SN terminated MCG bearer or SN terminated split bearer; or, the first bearer bearer type before PDCP SN length change is MN terminated split bearer. A bearer whose PDCP SN length is changed is a SN terminated MCG bearer or a SN terminated split bearer.

As a third example of the second implementation manner, the second configuration information includes release and added configuration information of the RLC entity.

It should be noted that, at this time, the second configuration information may not include the release configuration information of the PDCP entity, and the SN11 may generate the release configuration information of the PDCP entity for the terminal 21.

For example, in the following possibility of the bearer type before and after the PDCP SN length changes, the second configuration information may include the release and added configuration information of the RLC entity: the bearer type before the PDCP SN length change is the MCG terminated by the MN Bearer, the first bearer type after PDCP SN length change is SN terminated MCG bearer or SN terminated split bearer; or the first bearer before PDCP SN length change is MN terminated split bearer, first The bearer type after PDCP SN length change is SN terminated MCG bearer or SN terminated split bearer.

S808: MN01 sends the second configuration information of the first bearer to the terminal 21.

For example, MN01 may send an RRC connection reconfiguration message to the terminal 21, where the RRC connection reconfiguration message includes the second configuration information of the first bearer.

Optionally, S806 and S808 may occur at the same time. For example, MN01 sends a message to terminal 21, the message carries both the first configuration information and the second configuration information of the first bearer, and the message may be an RRC connection reconfiguration message.

The description of changing the length of the PDCP and SN is further described below with reference to FIGS. 9 to 12a.

The following describes how to change the PDCP SN length in the SN increase request process in combination with the SN increase request process.

FIG. 9 is a schematic diagram of an embodiment of changing the length of PDCP and SN.

S901: MN01 sends a secondary node addition request message to SN11.

Before MN01 sends a secondary node addition request message to SN11, the bearer type of the first bearer can be the MCG bearer terminated by the MN, MN01 can decide the bearer type of the first bearer after adding the secondary node, and the first bearer can be terminated after adding the secondary node. SN, that is, the PDCP entity of the first bearer after adding the secondary node is on SN11. For example, the type of the bearer of the first bearer after adding the secondary node is an SN terminated MCG bearer, an SN terminated SCG bearer, or an SN terminated split bearer.

The secondary node addition request message may include:

(1) The bearer identifier of the first bearer.

(2) The indication information of the bearer type of the first bearer after adding the secondary node.

For example, it may include whether the PDCP entity of the first bearer after adding the secondary node is on SN11, whether the MCG resource exists on the first bearer after adding the secondary node, and whether the SCG resource exists on the first bearer after adding the secondary node.

For example, the PDCP entity of the first bearer after adding the secondary node is on SN11. MCG resources exist in the first bearer after adding the secondary node, and there is no SCG resource, that is, the bearer type of the first bearer after adding the secondary node is the SN terminated MCG bearer. Alternatively, the PDCP entity of the first bearer after adding the secondary node is on SN11. There is no MCG resource and SCG resource for the first bearer after adding the secondary node, that is, the bearer type of the first bearer after adding the secondary node is an SN terminated SCG bearer. Alternatively, the PDCP entity of the first bearer after adding the secondary node is on SN11. The first bearer after adding the secondary node has MCG resources and SCG resources, that is, the bearer type of the first bearer after adding the secondary node is an SN terminated split bearer.

(3) The configuration information of the PDCP entity carried on the first bearer on MN01 includes the PDCP SN length of the first bearer on MN01, that is, the first PDCP SN length in FIG. 8, for example, the first PDCP SN length may be 12 bits. The configuration information of the PDCP entity carried by the first bearer on the MN01 may be used to assist the SN11 to generate configuration information of a new PDCP entity.

The following S902-S907 are further described as an example of S801-S808.

S902: SN11 generates a second PDCP SN length of the first bearer.

Prior to S902, since the first PDCP entity carried on the secondary node was added to SN11, SN11 may decide to generate the PDCP SN length, that is, the second PDCP SN length in S801 in FIG. 8, for example, the second PDCP SN length is 18 bits.

S903: When the length of the second PDCP SN of the first bearer is different from the length of the first PDCP SN of the first bearer, SN11 generates a PDCP SN length change indication of the first bearer.

Wherein, when the length of the PDCP SN of the first bearer is before the length of the second PDCP SN, the length of the PDCP SN of the first bearer may be the length of the first PDCP SN. It can be understood that before the SN11 generates the second PDCP SN length of the first bearer, The PDCP SN length of the first bearer is the first PDCP SN length. It can also be understood that before the PDCP SN length of the first bearer changes, the PDCP SN length of the first bearer is the first PDCP SN length, and the PDCP SN length of the first bearer changes. Then, the length of the PDCP SN of the first bearer is the length of the second PDCP SN.

For example, the length of the first PDCP SN of the first bearer is 12 bits, the length of the second PDCP SN of the first bearer is 18 bits, the length of the first PDCP SN is different from the length of the second PDCP SN, and SN11 generates a PDCP SN length indication of the first bearer. .

S904: SN11 generates first configuration information of the first bearer.

Optionally, S902 may occur at the same time as S904, that is, when SN11 generates the first configuration information of the first bearer, it may generate the second PDCP SN length of the first bearer.

The first configuration information of the first bearer may be configuration information of the first bearer on the SN11 generated by the SN11 for the terminal 21.

Because there is no entity on the SN11 before adding the secondary node, for example, the type of the first bearer before adding the secondary node is the MCG bearer terminated by MN. The PDCP entity, RLC entity, and MAC entity of the first bearer are all on MN01. The first PDCP entity carried by the secondary node is on SN11. The RLC entity or MAC entity may or may not be on SN11, and the RLC entity or MAC entity may or may not be on MN01. For example, after the secondary node is added, the bearer type of the first bearer is SN. Terminated MCG bearer, PDCP entity of the first bearer is on SN11, RLC entity and MAC entity of the first bearer are on MN01; after adding a secondary node, the bearer type of the first bearer is an SN terminated SCG bearer, and PDCP of the first bearer Entity, RLC entity, and MAC entity are on SN11; after adding a secondary node, the first bearer bearer type is an SN-terminated split bearer, the first bearer PDCP entity is on SN11, and the first bearer RLC entity and MAC entity are on MN01 and On SN11.

If the previous entity (such as PDCP entity, RLC entity, or MAC entity) of the secondary node is not on SN11, and the entity is on SN11 after adding the secondary node, the first configuration information on the first bearer may include the additional configuration information of the entity. .

The first configuration information of the first bearer may include configuration information of the PDCP entity, such as added configuration information of the PDCP entity; or, for example, the first configuration information may include release and added configuration information of the PDCP entity, for example, MN01 and SN11 All PDCPs can be NR PDCP, MN01 can generate the release information of PDCP entity for terminal 21, or it can directly generate the release configuration information of PDCP entity while generating the additional configuration information of PDCP entity by SN11, MN01 is not needed at this time Regenerate the configuration information of the PDCP entity.

Optionally, the first configuration information of the first bearer may further include configuration information of the RLC entity and configuration information of the MAC entity, such as added configuration information of the RLC entity and configuration information of the MAC entity.

For example, the bearer type of the first bearer before the secondary node is added is the MN terminated MCG bearer, and the bearer type of the first bearer after the secondary node is added is the SN terminated MCG bearer. The first configuration information of the first bearer may include the addition of the PDCP entity. Configuration information or release and added configuration information of the PDCP entity.

For example, the bearer type of the first bearer before the secondary node is added is an MN terminated MCG bearer, the bearer type of the first bearer after the secondary node is added is an SN terminated SCG bearer or an SN terminated split bearer, and the first configuration information of the first bearer is It may include the added configuration information of the PDCP entity or the release and added configuration information of the PDCP entity, as well as the added configuration information of the RLC entity and the added configuration information of the MAC entity.

In the embodiment of the present application, for example, the configuration information of the PDCP entity on MN01 or SN01 may be implemented by the RadioBearerConfig cell in section 6.3.2 of 3GPP TS38.331V15.1.0; the configuration of the RLC entity and the MAC entity of MN01 or SN01 The information can be implemented through the CellGroupConfig cell in 3GPP TS38.331V15.1.0 section 6.3.2 or the RadioResourceConfigDedicated cell in 3GPP TS36.331V15.1.0 section 6.3.2.

S905: SN11 sends a secondary node addition request response message to MN01.

The secondary node addition request response message may include a bearer identifier of the first bearer, a PDCP SN length change indication of the first bearer, and first configuration information of the first bearer.

Optionally, the secondary node may define a new cell in the request response message, and the PDCP SN length change indication of the first bearer may be carried in this new cell. You can use 1 bit to carry the PDCP SN length change indication. For example, 1 represents the PDCP SN length change, and 0 represents the PDCP SN length has not changed.

S906: MN01 generates the second configuration information of the first bearer according to the PDCP SN length change indication of the first bearer.

The second configuration information of the first bearer may be configuration information of the first bearer on the MN01 generated by the MN01 for the terminal 21.

If the previous entity (such as PDCP entity, RLC entity, or MAC entity) of the secondary node is added to MN01, and the entity is added to MN01 after the secondary node is added, the first configuration information on the first bearer may include the release and addition of the entity. Configuration information; if the previous entity (such as PDCP entity, RLC entity, or MAC entity) of the secondary node is added on MN01, the entity is not on MN01 after the secondary node is added, the first configuration information on the first bearer may include the release of the entity Configuration information.

The second configuration information carried by the first bearer may include configuration information of the PDCP entity, for example, release information of the PDCP entity. At this time, the MN01 generates the release configuration information of the PDCP entity for the terminal 21. Alternatively, the second configuration information of the first bearer may not include the release configuration information of the PDCP entity, and the SN 11 generates the release configuration information of the PDCP entity for the terminal 21.

Optionally, the second configuration information carried by the first bearer may include configuration information of the RLC entity and the MAC entity, such as the release and addition configuration information of the RLC entity and the release and addition configuration information of the MAC entity.

For example, the bearer type of the first bearer before adding the secondary node is the MN terminated MCG bearer, and the bearer type of the first bearer after the secondary node is added is the SN terminated MCG or the SN terminated split bearer.

Optionally, the second configuration information of the first bearer may further include configuration information released by the RLC entity and configuration information released by the MAC entity.

For example, the bearer type of the first bearer before adding the secondary node is an MN terminated MCG bearer, and the bearer type of the first bearer after adding the secondary node is an SN terminated SCG bearer.

S907: MN01 sends an RRC connection reconfiguration message to the terminal 21.

The RRC connection reconfiguration message may include the identifier of the first bearer, the first configuration information of the first bearer, and the second configuration information of the first bearer.

S908: The terminal 21 sends an RRC connection reconfiguration completion message to the MN01.

The terminal 21 performs a delete-before-add operation of the bearer according to the bearer identifier included in the RRC connection reconfiguration message, the first configuration information of the first bearer, and the second configuration information of the first bearer.

S909: MN01 sends an SN reconfiguration completion message to SN11.

S910: The terminal 21 and the SN11 complete random access.

The following describes how to change the PDCP and SN length in the secondary node modification process in conjunction with the secondary node triggering the secondary node modification process.

After the secondary node is added, for example, you can refer to the related content in Figure 9. The PDCP entity of the first bearer can be on SN11. For example, the bearer type of the first bearer is SN terminated MCG bearer, SN terminated SCG bearer, or SN. The end of the split bearer. SN11 can maintain PDCP configuration. For example, through the secondary node modification process, SN11 can modify the PDCP SN length without changing the bearer type.

FIG. 10 is a schematic diagram of another embodiment of changing the length of the PDCP and SN.

S1001: SN11 generates a second PDCP SN length of the first bearer.

For example, the length of the second PDCP SN may be 12 bits.

For example, the first bearer is an SN terminated MCG bearer, an SN terminated SCG bearer, or an SN terminated split bearer.

S1002: SN11 generates first configuration information of the first bearer.

Optionally, S1002 may occur simultaneously with S1001, that is, when SN11 generates the first configuration information of the first bearer, it may generate the second PDCP SN length of the first bearer.

Before and after the PDCP SN length is changed, the bearer type of the first bearer remains unchanged. The PDCP entity of the first bearer is on SN11. The RLC entity and the MAC entity may or may not be on SN11. For example, the first bearer is an SN terminated MCG bearer. One bearer PDCP entity is on SN11, RLC entity and MAC entity are not on SN11; the first bearer is the SN terminated SCG bearer or the SN terminated split bearer, the first bearer PDCP entity is on SN11, and the RLC entity and MAC entity are on On SN11.

For example, if a previous entity (such as a PDCP entity, an RLC entity, or a MAC entity) is added to the SN11 and the secondary node is added to the SN11, the first configuration information on the first bearer may include the release of the entity and the Added configuration information.

The first configuration information of the first bearer may include configuration information of the PDCP entity, such as release and added configuration information of the PDCP entity.

Optionally, the first configuration information of the first bearer may further include configuration information of the RLC entity and the MAC entity, such as release and added configuration information of the RLC entity and the MAC entity.

For example, the first bearer is an MCG bearer terminated by an SN, and the first configuration information of the first bearer may include release and added configuration information of the PDCP entity.

For example, the first bearer is an SN terminated SCG bearer or an SN terminated split bearer. The first configuration information of the first bearer may include release and addition configuration information of the PDCP entity, and release and addition configuration of the RLC entity and the MAC entity. information.

S1003: When the second PDCP SN length of the first bearer is different from the first PDCP SN length of the first bearer, SN11 generates a PDCP SN length change indication of the first bearer.

Before changing the PDCP SN length, the first bearer ends at SN11. SN11 can obtain the first PDCP SN length. For example, the first PDCP SN length can be 18 bits.

For example, the length of the first PDCP SN may be 18 bits, the length of the second PDCP SN may be 12 bits, the length of the first PDCP SN is different from the length of the second PDCP SN, and SN11 generates a PDCP SN length indication of the first bearer.

S1004: SN11 sends a secondary node modification request message to MN01.

The secondary node modification request message may include a bearer identifier of the first bearer, a PDCP SN length change indication of the first bearer, and first configuration information of the first bearer.

Optionally, a new cell can be defined in the secondary node modification request message, and the PDCP SN length change indication of the first bearer can be carried in this new cell. You can use 1 bit to carry the PDCP SN length change indication. For example, 1 represents the PDCP SN length change, and 0 represents the PDCP SN length has not changed.

S1005: MN01 generates the second configuration information of the first bearer according to the PDCP SN length change indication of the first bearer.

For example, if the previous entity (such as the RLC entity or the MAC entity) of the secondary node is added to MN01, and the entity is added to MN01 after the secondary node is added, the first configuration information on the first bearer may include the release of the entity and the added configuration. information.

The second configuration information carried by the first bearer may include configuration information of the RLC entity and the MAC entity, such as the release and addition configuration information of the RLC entity and the release and addition configuration information of the MAC entity.

For example, the first bearer is an SN-terminated MCG bearer or an SN-terminated split bearer. The second configuration information of the first bearer may include release and added configuration information of the RLC entity and the MAC entity.

For example, when the first bearer is an SCG bearer terminated by an SN, the first bearer is not physically located on MN01, and the second configuration information of the first bearer may not be generated.

S1006: MN01 sends an RRC connection reconfiguration message to terminal 21.

S1007: The terminal 21 sends an RRC connection reconfiguration completion message to the MN01.

S1008: MN01 sends a secondary node modification confirmation message to SN11.

The following describes how to change the PDCP SN length in the secondary node modification process in conjunction with the secondary node modification process.

After the addition of the secondary node or the modification of the secondary node triggered by the secondary node is completed, for example, reference may be made to the related content in FIG. 9 and FIG. 10. The PDCP entity of the first bearer may be on the SN11. For example, the bearer type of the first bearer is SN termination. MCG bearer, SN terminated SCG bearer, or SN terminated split bearer. Optionally, MN01 can initiate a secondary node modification process, or SN11 can request MN01 to initiate a secondary node modification process to change the bearer type of the first bearer, for example, the type of the first bearer is MN terminated MCG bearer, MN terminated SCG Bearer or split bearer terminated by MN. The MN01 can initiate the secondary node modification process, or the SN11 can request the MN01 to initiate the secondary node modification process. The above six types of bearers of the first bearer can be used to change or not change the bearer type, and the PDCP and SN length can be modified by SN11. .

FIG. 11 is a schematic diagram of another implementation manner of changing the length of the PDCP and SN.

S1101: MN01 sends a secondary node modification request message to SN11.

Before MN01 sends a secondary node modification request message to SN11, the bearer type of the first bearer can be MN terminated MCG bearer, MN terminated SCG bearer, MN terminated split bearer, SN terminated MCG bearer, SN terminated SCG bearer, or SN terminated split bearer.

MN01 can modify the bearer type of the first bearer through the secondary node modification request message. For example, the bearer type of the first bearer can be changed to the SN-terminated bearer type. For example, the three types of MN-terminated bearer types can be modified to any kind of SN. Terminated bearer type. The above-mentioned SN-terminated bearer type can be modified to the other two SN-terminated bearer types.

The secondary node modification request message may include:

(1) The bearer identifier of the first bearer.

(2) The indication information of the modified bearer type.

The modified bearer type may be an SN terminated bearer type.

For example, it may include whether the PDCP entity of the first bearer after the bearer type is modified is on SN11, whether the MCG resource exists in the first bearer after adding the secondary node, and whether the SCG resource exists in the first bearer after adding the secondary node.

(3) Optionally, before changing the bearer type of the first bearer, the first bearer terminates on MN01, which may include configuration information of the PDCP entity of the first bearer on MN01, and may include the PDCP SN length of the first bearer on MN01, That is, the first PDCP SN length in FIG. 8, for example, the first PDCP SN length may be 12 bits. The configuration information of the PDCP entity carried by the first bearer on the MN01 may be used to assist the SN11 to generate configuration information of a new PDCP entity.

Optional Before S1101, S1100 can also be included.

S1100: SN11 sends a secondary node modification request message to MN01.

MN11 may request MN01 to initiate a secondary node modification process.

S1102: SN11 generates a second PDCP SN length of the first bearer.

After the bearer type of the first bearer is modified, the first bearer can be terminated at the SN, and the SN11 can generate the second PDCP SN length of the first bearer, that is, the second PDCP SN length in S801 in FIG. 8, such as the second PDCP SN length It is 18bit.

S1103: When the second PDCP SN length of the first bearer is different from the first PDCP SN length of the first bearer, SN11 generates a PDCP SN length change indication of the first bearer.

Wherein, before the length of the PDCP SN of the first bearer is before the length of the second PDCP SN, the length of the PDCP SN of the first bearer may be the length of the first PDCP SN.

S1104: SN11 generates first configuration information of a first bearer.

Optionally, S1103 can occur simultaneously with S1102, that is, when SN11 generates the first configuration information of the first bearer, it can generate the second PDCP SN length of the first bearer.

Before the bearer type is changed, the first bearer may be terminated at the SN. The PDCP entity of the first bearer may be at SN11 before the bearer type is changed. The RLC entity and the MAC entity may or may not be at SN11. The RLC entity or the MAC entity may or may not be at. On MN01. For example, before the bearer type is changed, the first bearer is an SN terminated MCG bearer. The PDCP entity is on SN11, and the RLC entity and the MAC entity are on MN01. For example, before the bearer type is changed, the first bearer is an SN terminated SCG bearer, the PDCP entity, The RLC entity and the MAC entity are on SN11; for example, before the bearer type is changed, the first bearer is the split bearer terminated by SN, the PDCP entity is on SN11, and the RLC entity and the MAC entity are on MN01 and SN01. After the bearer type is changed, the first bearer may be terminated at the SN. For the entity on the SN11, refer to the related description of the first bearer entity on the SN11 before the bearer type is changed.

Before the bearer type is changed, the first bearer may be terminated at the MN. Before the bearer type is changed, the PDCP entity of the first bearer may be on MN01, the RLC entity and the MAC entity may or may not be on MN01, and the RLC entity or the MAC entity may be on or off. On SN11. For example, before changing the bearer type, the first bearer is the MCG bearer terminated by the MN, the PDCP entity is on MN01, and the RLC entity and the MAC entity are on the MN01; for example, before the bearer type is changed, the first bearer is the MN terminated SCG bearer, the PDCP entity can On MN01, the RLC entity and the MAC entity are on SN11; for example, before changing the bearer type, the first bearer is the split bearer terminated by MN, the PDCP entity is on MN01, and the RLC entity and the MAC entity are on MN01 and SN01. After the bearer type is changed, the first bearer may be terminated at the SN. For the entity on the SN11, refer to the related description of the first bearer entity on the SN11 before the bearer type is changed.

If an entity (such as a PDCP entity, an RLC entity, or a MAC entity) is not on the SN11 before the bearer type is changed, and the entity is on the SN11 after the bearer type is changed, the first configuration information on the first bearer may include the addition of the entity. Configuration information; if an entity (such as a PDCP entity, an RLC entity, or a MAC entity) was on SN11 before the bearer type was changed, the entity was on SN11 after the bearer type was changed, and the first configuration information on the first bearer may include the release of the entity And added configuration information; if an entity (such as a PDCP entity, an RLC entity, or a MAC entity) was on SN11 before the bearer type was changed, the entity was not on SN11 after the bearer type was changed, and the first configuration information on the first bearer may include the Release configuration information for the entity.

Before changing the bearer type, the first bearer terminates in the SN, that is, the first bearer is modified from the SN-terminated MCG bearer, the SN-terminated SCG bearer, or the SN-terminated split bearer. The other of the SCG bearer or the SN terminated split bearer, the first configuration information of the first bearer may include the following:

As a first example, the first configuration information of the first bearer may include configuration information of a PDCP entity, such as release and added configuration information of a PDCP entity.

As a second example, on the basis of the first example, the first configuration information of the first bearer may further include configuration information of the RLC entity and the MAC entity, such as release and added configuration information of the RLC entity and the MAC entity.

As a third example, based on the first example, the first configuration information of the first bearer may further include configuration information of the RLC entity and the MAC entity, for example, configuration information of the release of the RLC entity and the MAC entity.

As a fourth example, on the basis of the first example, the first configuration information of the first bearer may further include configuration information of the RLC entity and the MAC entity, for example, increased configuration information of the RLC entity and the MAC entity.

For example, before the bearer type is modified, the bearer type of the first bearer is an SN-terminated SCG bearer, and after the bearer type is modified, the bearer type of the first bearer is an SN-terminated split bearer; or, before the bearer type is modified, the bearer type of the first bearer is SN. Terminated split bearer. After the bearer type is modified, the bearer type of the first bearer is the SCG bearer terminated by SN. The first configuration information of the first bearer may include the release of the PDCP entity and the added configuration information, and the release of the RLC entity and the MAC entity. Added configuration information.

For example, before the bearer type is modified, the bearer type of the first bearer is an SCG bearer or split bearer terminated by the SN. After the bearer type is modified, the bearer type of the first bearer is an SN terminated MCG bearer. The first configuration information of the first bearer may include PDCP. Release information of the entity and added configuration information and release configuration information of the RLC entity and MAC entity.

For example, before the bearer type is modified, the bearer type of the first bearer is an SN terminated MCG bearer. After the bearer type is modified, the bearer type of the first bearer is an SN terminated split bearer or an SN terminated SCG bearer. The first configuration information of the first bearer is It may include the release and added configuration information of the PDCP entity and the added configuration information of the RLC entity and the MAC entity.

Before changing the bearer type, the first bearer terminates at the MN, that is, one of the MCG bearer terminated by the MN, the SCG bearer terminated by the SN, or the split bearer terminated by the SN is modified to the SN terminated MCG bearer or the SN terminated The SCG bearer or the SN terminated split bearer. The first configuration information of the first bearer may include the following:

As a first example, the first configuration information of the first bearer may include configuration information of the PDCP entity, such as added configuration information of the PDCP entity, or, for example, the first configuration information of the first bearer may include release and addition of PDCP Configuration information. For example, the PDCP of MN01 and SN11 can both be NR and PDCP. MN01 can generate the release information of the PDCP entity for the terminal 21, or it can directly generate the release configuration information of the PDCP entity while generating the additional configuration information of the PDCP entity. At this time, MN01 does not need to generate the configuration information of the release of the PDCP entity again.

As a second example, on the basis of the first example, the first configuration information of the first bearer may include configuration information of the RLC entity and the MAC entity, such as release and added configuration information of the RLC entity and the MAC entity.

As a third example, on the basis of the first example, the first configuration information of the first bearer may include configuration information of the RLC entity and the MAC entity, for example, configuration information of the release of the RLC entity and the MAC entity.

As a fourth example, on the basis of the first example, the first configuration information of the first bearer may include configuration information of the RLC entity and the MAC entity, for example, increased configuration information of the RLC entity and the MAC entity.

For example, the bearer type of the first bearer before the bearer type is modified is the MCG bearer terminated by the MN, and the bearer type of the first bearer after the bearer type is modified is the SN terminated MCG bearer. The first configuration information of the first bearer may include the configuration of the PDCP entity. Information or PDCP release and added configuration information.

For example, before the bearer type is modified, the bearer type of the first bearer is an MN terminated SCG bearer or the MN terminated split bearer. After the bearer type is modified, the bearer type of the first bearer is an SN terminated SCG bearer or an SN terminated split bearer. The first configuration information carried may include configuration information of the PDCP entity or configuration information of release and addition of the PDCP, and configuration information of release and addition of the RLC entity and the MAC entity.

For example, before the bearer type is modified, the bearer type of the first bearer is an MN terminated MCG bearer. After the bearer type is modified, the bearer type of the first bearer is an SN terminated SCG bearer or a split bearer. The first configuration information of the first bearer may include PDCP. The configuration information of the entity or the release and added configuration information of the PDCP, and the added configuration information of the RLC entity and the MAC entity.

For example, before the bearer type is modified, the bearer type of the first bearer is an SCG bearer terminated by the MN or the split bearer of the MN terminates. After the bearer type is modified, the bearer type of the first bearer is the MCG bearer terminated by the SN. The first configuration information of the first bearer It may include configuration information of the PDCP entity or release and addition configuration information of the PDCP, and configuration information of release of the RLC entity and the MAC entity.

S1105: SN11 sends a secondary node modification request response message to MN01.

The secondary node modification request response message may include a bearer identifier of the first bearer, a PDCP SN length change indication of the first bearer, and first configuration information of the first bearer.

Optionally, a new cell can be defined in the secondary node modification request response message, and the PDCP SN length change indication of the first bearer can be carried in this new cell. You can use 1 bit to carry the PDCP SN length change indication. For example, 1 represents the PDCP SN length change, and 0 represents the PDCP SN length has not changed.

S1106: MN01 generates the second configuration information of the first bearer according to the PDCP SN length change indication of the first bearer.

If an entity (such as a PDCP entity, an RLC entity, or a MAC entity) is not on MN01 before the bearer type is changed, and the entity is on MN01 after the bearer type is changed, the second configuration information on the first bearer may include the addition of the entity. Configuration information; if an entity (such as a PDCP entity, an RLC entity, or a MAC entity) was on MN01 before the bearer type was changed, and the entity was on MN01 after the bearer type was changed, the second configuration information on the first bearer may include the release of the entity And added configuration information; if an entity (such as a PDCP entity, an RLC entity, or a MAC entity) was on MN01 before the bearer type was changed, the entity was not on MN01 after the bearer type was changed, and the second configuration information on the first bearer may include the Release configuration information for the entity.

Before changing the bearer type, the first bearer terminates in the SN, that is, the first bearer is modified from the SN-terminated MCG bearer, the SN-terminated SCG bearer, or the SN-terminated split bearer. For the other of the SCG bearer or the SN terminated split bearer, the second configuration information of the first bearer may include the following:

As a first example, the second configuration information of the first bearer may include configuration information of the RLC entity and the MAC entity, such as release and added configuration information of the RLC entity and the MAC entity.

As a second example, the second configuration information of the first bearer may include configuration information of the RLC entity and the MAC entity, such as release configuration information of the RLC entity and the MAC entity.

As a third example, the second configuration information of the first bearer may include configuration information of the RLC entity and the MAC entity, for example, increased configuration information of the RLC entity and the MAC entity.

For example, before modifying the bearer type, the bearer type of the first bearer is an SN terminated MCG bearer, and after modifying the bearer type, the bearer type of the first bearer is an SN terminated split bearer; or before the bearer type is modified, the bearer type of the first bearer is SN terminated. Split bearer. After the bearer type is modified, the bearer type of the first bearer is the MCG bearer terminated by the SN. The second configuration information of the first bearer may include the release and added configuration information of the RLC entity and the MAC entity.

For example, before the bearer type is modified, the bearer type of the first bearer is an SN terminated MCG bearer or the SN terminated split bearer. After the bearer type is modified, the bearer type of the first bearer is an SN terminated SCG bearer, and the second configuration information of the first bearer is The configuration information of the release of the RLC entity and the MAC entity may be included.

For example, before the bearer type is modified, the bearer type of the first bearer is an SN terminated SCG bearer. After the bearer type is modified, the bearer type of the first bearer is an SN terminated MCG bearer or an SN terminated split bearer. The second configuration information of the first bearer is Added configuration information for RLC entities and MAC entities may be included.

As a first example, the second configuration information of the first bearer may include configuration information of a PDCP entity, such as deleted configuration information of a PDCP entity.

As a second example, on the basis of the first example, the second configuration information of the first bearer may further include configuration information of the RLC entity and the MAC entity, such as release and added configuration information of the RLC entity and the MAC entity.

As a third example, on the basis of the first example, the second configuration information of the first bearer may further include configuration information of the RLC entity and the MAC entity, for example, increased configuration information of the RLC entity and the MAC entity.

As a fourth example, on the basis of the first example, the second configuration information of the first bearer may further include configuration information of the RLC entity and the MAC entity, such as release configuration information of the RLC entity and the MAC entity.

For example, before modifying the bearer type, the bearer type of the first bearer is an SCG bearer terminated by the MN. After modifying the bearer type, the bearer type of the first bearer is an SCG bearer terminated by the SN. The second configuration information of the first bearer may include deletion of the PDCP entity. MN01 may not generate the second configuration information, or does not include the deleted configuration information of the PDCP entity.

For example, before the bearer type is modified, the bearer type of the first bearer is the MCG bearer or split bearer terminated by the MN. After the bearer type is modified, the bearer type of the first bearer is the MCG bearer or the split bearer terminated by the SN. The second configuration information of the first bearer is It may include deleted configuration information of the PDCP entity, or does not include deleted configuration information of the PDCP entity, and release and added configuration information of the RLC entity and the MAC entity.

For example, before the bearer type is modified, the bearer type of the first bearer is the MCG bearer or split bearer terminated by the MN. After the bearer type is modified, the bearer type of the first bearer is the SN terminated SCG bearer. The second configuration information of the first bearer may include PDCP. The deleted configuration information of the entity, or does not include the deleted configuration information of the PDCP entity, and the released configuration information of the RLC entity and the MAC entity.

For example, before the bearer type is modified, the bearer type of the first bearer is an MN terminated SCG bearer. After the bearer type is modified, the bearer type of the first bearer is an SN terminated MCG bearer or an SN terminated split bearer. The second configuration information of the first bearer is It may include the deleted configuration information of the PDCP entity, or does not include the deleted configuration information of the PDCP entity, and the added configuration information of the RLC entity and the MAC entity.

S1107: MN01 sends an RRC connection reconfiguration message to terminal 21.

The RRC connection reconfiguration message may include a bearer identifier of the first bearer, first configuration information of the first bearer, and second configuration information of the first bearer.

S1108: The terminal 21 sends an RRC connection reconfiguration completion message to the MN01.

S1109: MN01 sends a secondary node modification confirmation (SN) confirmation message to SN11.

FIG. 12a is a schematic diagram of another implementation manner of changing the length of the PDCP and SN.

The first bearer can be terminated at the SN. SN11 can request MN01 to initiate a secondary node modification process to modify the bearer type of the first bearer. The modified first bearer is terminated at the SN. The bearer type can be modified to two other SN-terminated bearer types.

S1201: SN11 generates a second PDCP SN length of the first bearer.

S1202: When the second PDCP SN length of the first bearer is different from the first PDCP SN length of the first bearer, SN11 generates a PDCP SN length change indication of the first bearer.

S1203: SN11 sends a secondary node modification request message to MN01.

The secondary node modification request message includes a PDCP SN length indication of the first bearer.

Optionally, a new cell may be defined in the secondary node addition request response message, and the PDCP SN length change indication of the first bearer may be carried in this new cell. You can use 1 bit to carry the PDCP SN length change indication. For example, 1 represents the PDCP SN length change, and 0 represents the PDCP SN length has not changed.

S1204: MN01 sends a secondary node modification request message to SN11.

S1205: SN11 generates first configuration information of the first bearer.

S1206: SN11 sends a secondary node modification request response message to MN01.

S1207: MN01 generates the second configuration information of the first bearer according to the PDCP SN length change indication of the first bearer.

S1208: MN01 sends an RRC connection reconfiguration message to terminal 21.

S1209: The terminal 21 sends an RRC connection reconfiguration completion message to the MN01.

S1210: MN01 sends a SN modification confirmation message to the SN11.

For other contents of S1201-S1210, reference may be made to the related content in FIG. 11, for example, related content about "the first bearer may be terminated at the SN before the bearer type is changed".

In the first solution, the MN01 and SN01 exchange PDCP SN length change instructions, so that MN01 and SN11 generate the release and added configuration information of the bearer for the terminal 21 to complete the PDCP SN length change. In addition, when the PDCP SN length can be 12 bits or 18 bits, after receiving the PDCP SN length change instruction, MN01 can learn the new PDCP SN length in combination with the PDCP SN length saved by MN01, so that MN01 can determine the PDCP SN length in the future. Whether it has changed so that subsequent releases and additions of configuration information are generated for the bearer.

The second solution is described below.

FIG. 12b is a schematic diagram of another implementation manner of changing the length of the PDCP and SN.

S12b01: SN11 generates a second PDCP SN length of the first bearer.

You can refer to the related content in S801.

S12b02: SN11 determines whether the PDCP SN length has changed.

When the second PDCP SN length of the first bearer is different from the first PDCP SN length of the first bearer, the PDCP SN length changes.

As a first implementation manner, when the PDCP SN length of the first bearer is the first PDCP SN length, the first bearer ends at the SN, and SN11 can obtain the first PDCP SN length.

As a second implementation manner, when the length of the PDCP SN of the first bearer is the length of the first PDCP SN, the first bearer terminates at the MN, and may further include the MN01 sending the first PDCP SN length to the SN11, for example, a request message may be added through a secondary node The secondary node sends a first PDCP SN length to modify the request message.

For other contents, please refer to the related contents in S802.

When the PDCP and SN lengths change, the steps of S1203 and S1205-S1208 can also be included.

S12b03: SN11 generates first configuration information of the first bearer.

Optionally, S1203 can occur simultaneously with S1201, that is, when SN11 generates the first configuration information of the first bearer, it can generate the second PDCP SN length of the first bearer.

Reference may be made to S804 in FIG. 8, and details are not described herein again.

S12b04: SN11 sends the second PDCP SN length of the first bearer to MN01.

For example, SN11 may send the second PDCP SN length of the first bearer through the secondary node adding a request message, a secondary node modification request message, or a secondary node modification request message.

As a first example, SN11 may send a second PDCP SN length to MN01 when it determines that the PDCP SN length changes in S1202.

As a second example, SN11 may send the second PDCP SN length to MN01 after generating the second PDCP SN length. That is, when the PDCP SN length changes or does not change, SN11 can send the second PDCP SN length to MN01.

MN01 can read the second PDCP SN length of the first bearer. Optionally, MN01 can save the second PDCP SN length of the first bearer.

For example, SN11 may carry the second PDCP SN length in a cell that MN01 will read, and send it to MN01.

For example, SN11 may define a new cell that includes the second PDCP SN length, and MN01 may read the second PDCP SN length in the cell.

You can refer to Section 9.1.3.2 of 3GPP TS36.423 and V15.1.0. SN11 can add the configuration response generated by SN11 for terminal 21 in the secondary node add request response message. For example, the configuration information can be a container. The container can be Including the second PDCP SN length, but at this time MN01 is not required to read the content of the container, so MN01 will not read the second PDCP SN length carried in the container.

Here, you can define a new cell or carry the second PDCP SN length in a cell that MN01 will read, so that MN01 reads the second PDCP SN length, so MN01 can determine whether the PDCP SN length has changed. Thereby, the release and added configuration information of the first bearer is generated for the terminal 21.

S12b05: SN11 sends the first configuration information of the first bearer to MN01.

Optionally, S1204 and S1205 can occur at the same time. For example, the second PDCP SN length and the first configuration information of the first bearer can be sent to MN01 in the same message, such as a secondary node addition request response message or a secondary node modification request response. Message.

S12b06: MN01 sends the first configuration information of the first bearer to the terminal 21.

S12b07: MN01 determines whether the length of the PDCP SN changes.

As a first embodiment, when the PDCP SN length of the first bearer is the first PDCP SN length, the first bearer terminates at the SN, and SN11 can send the first PDCP SN length of the first bearer to MN01. For details, refer to the relevant part of S1203. content.

As a second implementation manner, when the PDCP SN length of the first bearer is the first PDCP SN length, the first bearer ends at the MN, and MN01 can obtain the first PDCP SN length of the first bearer.

S12b08: MN01 is the second configuration information for generating the first bearer.

For details, refer to S807 in FIG. 8.

S12b09: MN01 sends the second configuration information of the first bearer to the terminal 31.

For details, refer to S808 in FIG. 8.

Optionally, S12b09 and S12b06 can occur simultaneously. For example, SN11 sends a message to MN01. The message includes the first configuration information of the first bearer and the second configuration information of the first bearer. For example, the message is an RRC connection reconfiguration message. .

In the second scheme, MN01 and SN11 are respectively used to determine whether the PDCP SN length has changed, so that MN01 and SN11 generate the release and added configuration information of the bearer for the terminal 21 to complete the PDCP SN length change. In addition, when there are more than 3 possibilities for PDCP SN length, such as 3, 4, or more, there may be more possibilities for changes in PDCP SN length. Both MN01 and SN11 can know the latest PDCP SN length, MN01 And SN11 can more accurately determine whether the PDCP SN length has changed.

The third solution is described below.

You can configure the PDCP SN length corresponding to the bearer type. MN01 and SN11 can store the PDCP SN length corresponding to each bearer type. When the bearer type changes, MN01 or SN11 can know whether the PDCP SN length has changed. When the change occurs, MN01 And SN11 generate release information and added configuration information for the bearer for the terminal 21.

For example, bearers involving single air interface resources can be configured, such as MN terminated or SN terminated MCG bearers, MN terminated or SN terminated SCG bearers are a PDCP SN length, such as 12-bit PDCP SN length; The bearer, such as the MN-terminated or SN-terminated split bearer, has a different PDCP SN length, such as an 18-bit PDCP SN length. The following description is made by taking such a case as an example. Those skilled in the art can understand that the following content is also applicable to other cases.

FIG. 13 is a schematic diagram of another embodiment of changing the length of PDCP and SN.

S1301: SN11 determines whether the length of the PDCP SN changes.

For example, SN11 can be determined by the following steps: (1) determining whether the bearer type of the first bearer has changed, (2) whether the PDCP corresponding to the bearer type before the change and the PDCP SN length corresponding to the changed bearer type have occurred Variety. The SN11 may receive the bearer type of the first bearer from the MN01, for example, it may add a request message through a secondary node and modify the request message through a secondary node.

For example, the bearer type of the first bearer changes. Before the change, the MCG bearer terminated by the MN and the split bearer terminated by the SN. SN11 shows that the PDCP length of the MCG bearer terminated by the MN is 12 bits. The SN length is 18 bits, so the PDCP SN length changes.

S1302: SN11 generates first configuration information of the first bearer for the terminal 21.

When the PDCP SN length changes, the first configuration information of the first bearer may include the configuration information of the first bearer entity on SN11. For example, when the entity is on the SN11 before the PDCP SN length changes, before the PDCP SN length changes Not on SN11, the first configuration information may include the release information of the entity; when the entity is on the SN11 before the PDCP SN length changes, and on the SN11 before the PDCP SN length changes, the first configuration information may include the release and addition of the entity Configuration information; when the entity is not on SN11 before the PDCP SN length changes and on the SN11 before the PDCP SN length changes, the first configuration information may include additional information for the entity, and the entity may be a PDCP entity, an RLC entity, or a MAC entity .

Please refer to the related content in FIG. 8 to FIG. 11.

S1303: SN11 sends the first configuration information of the first bearer to MN01.

For example, the first configuration information of the first bearer may be sent through the secondary node adding a request response message or the secondary node modifying a request response message.

S1304: MN01 determines whether the length of the PDCP SN changes.

You can refer to related content in S1301.

S1305: MN01 generates second configuration information of the first bearer for the terminal 21.

When the PDCP SN length changes, the second configuration information of the first bearer may include the configuration information of the first bearer entity on MN01. For example, when the entity is on the MN01 before the PDCP SN length changes, before the PDCP SN length changes Not on MN01, the second configuration information may include the release information of the entity; when the entity is on the MN01 before the PDCP SN length changes, and on the MN01 before the PDCP SN length changes, the second configuration information may include the release and addition of the entity Configuration information; when the entity is not on MN01 before the PDCP SN length changes and on the MN01 before the PDCP SN length changes, the second set of information may include additional information about the entity, and the entity may be a PDCP entity, an RLC entity, or a MAC entity .

Please refer to the related content in FIG. 8 to FIG. 11.

S1306: MN01 sends the first configuration information of the first bearer and the second configuration information of the first bearer to the terminal 21.

For example, the first configuration information of the first bearer and the second configuration information of the first bearer may be sent through the RRC connection reconfiguration message.

In the three solutions, MN01 or SN11 can adopt the CU-DU architecture. Part of the protocol layer can be deployed on the CU. Part of the protocol layer can be deployed on the DU. The PDCP layer is deployed on the CU below. The RLC layer, MAC layer, and physical The layer is deployed on the DU as an example.

In the embodiment of the present application, the action sent or received by the SN11 may be performed by the CU1111. The configuration information of the PDCP entity in the first configuration information of the first bearer generated by the SN11 is generated by the CU1111, and the configuration information of the RLC entity or the configuration information of the MAC entity in the first configuration information is generated by the DU1121.

CU1111 can generate a PDCP SN length change instruction, CU1111 can send a PDCP SN length change instruction to the DU1121, and DU1121 generates RLC entity configuration information or MAC configuration information according to the PDCP SN length change instruction of the first bearer. The CU1111 may send a PDCP SN length change indication of the first bearer to the MN01, for example, CU0111.

CU1111 can generate the PDCP SN length, CU1111 can send the PDCP SN length of the first bearer to DU1121, and DU1121 determines whether the PDCP SN length has changed based on the received PDCP SN length of the first bearer, and generates configuration information or MAC of the RLC entity Configuration information. The CU1111 may send the PDCP SN length of the first bearer to the MN01, for example, to the CU0111.

In the embodiment of the present application, the action sent or received by MN01 may be performed by CU0111. The configuration information of the PDCP entity in the second configuration information of the first bearer generated by MN01 is generated by CU0111, and the configuration information of the RLC entity or MAC entity in the second configuration information is generated by DU0121. CU0111 can send the first The PDCP SN length change instruction of one bearer, DU0112 generates configuration information of the RLC entity or MAC configuration information according to the PDCP SN length change instruction of the first bearer. CU0111 may receive a PDCP SN length change indication of the first bearer from SN11, for example, CU1111, and then may send a PDCP SN length change indication of the first bearer to DU0112.

CU0111 can generate the PDCP SN length, CU0111 can send the PDCP SN length of the first bearer to DU0121, and DU0121 determines whether the PDCP SN length has changed based on the received PDCP SN length of the first bearer, and generates configuration information or MAC of the RLC entity Configuration information. CU0111 may send the PDCP SN length of the first bearer to SN11, for example, to CU1111.

FIG. 14 is a schematic diagram of an embodiment of changing a PDCP SN length under a CU-DU architecture. Taking CU1111 and DU1121 as examples for description, those skilled in the art can understand that the same applies to CU0111 and DU0121.

S1401: CU1111 generates configuration information of the PDCP entity.

S1402: CU1111 sends a PDCP SN length change indication of the first bearer to DU1121.

Or, as another embodiment, in 1402, CU1111 sends the PDCP SN length of the first bearer to DU1121, and CU1111 may carry the PDCP SN length of the first bearer in the cell read by DU1121. For example, CU1111 may define a A new cell, which carries the PDCP SN length of the first bearer, and the DU1121 reads the PDCP SN length of the first bearer from the cell.

S1403: DU1121 generates configuration information of the RLC entity and configuration information of the MAC entity.

The DU1121 can generate configuration information of the RLC entity and configuration information of the MAC entity according to the PDCP SN length change indication.

As another implementation manner, DU1121 can read the PDCP SN length sent by CU1111, and DU1121 can determine whether the PDCP SN length has changed based on the received PDCP SN length of the first bearer. Configuration information or MAC configuration information.

S1404: DU1121 sends the configuration information of the RLC entity and the configuration information of the MAC entity to the CU1111.

Here, the configuration information of the PDCP entity may include released configuration information, added configuration information, or released and added configuration information of the PDCP entity in the embodiments of the present application.

Here, the configuration information of the RLC entity may include the released configuration information, the added configuration information, or the released and added configuration information of the RLC entity in the embodiments of the present application.

Here, the configuration information of the MAC entity may include released configuration information, added configuration information, or released and added configuration information of the MAC entity in the embodiments of the present application.

For details, reference may be made to related content in FIG. 8 to FIG. 13, and details are not described herein again.

The method flowchart of the embodiment of the present application is introduced above. It should be understood that MN01 may have functional units corresponding to the MN01 method or process steps, and SN11 may have functional units corresponding to the SN11 method or process steps.

For example, SN11 may include a generating unit and a communication unit, and the generating unit may generate a second PDCP SN length of the first bearer, and the generating unit may also be configured when the second PDCP SN length of the first bearer is different from the first PDCP When the first PDCP SN length of a bearer is generated, the PDCP SN length change indication of the first bearer is generated, and the communication unit may send the PDCP SN length change indication of the first bearer to the MN. Optionally, the generating unit may be further configured to generate first configuration information of the first bearer, and the communication unit is configured to send the first configuration information of the first bearer to the MN01.

For example, SN11 may include a communication unit and a storage unit. The communication unit may be used to receive a PDCP SN length change indication of the first bearer from the SN, and the storage unit may be used to store the PDCP SN length change indication of the first bearer. Optionally, the SN11 may further include a generating unit, which may be configured to generate the second configuration information of the first bearer, and the communication unit may send the first configuration information of the first bearer and the second configuration information of the first bearer to the terminal 21 Configuration information.

The following describes the device or device in the embodiments of the present application.

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

The access network device 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, the memory 1512, the transceiver 1513, and the network interface 1514 are connected, for example, through a bus. The antenna 1515 is connected to the transceiver 1513. The network interface 1514 is used to enable the access network device to connect with other communication devices through a communication link, for example, the access network device is connected to the core network element 101 through an S1 interface. In the embodiment of the present application, the connection may include various interfaces, transmission lines, or buses, which is not limited in this embodiment.

The processor in the embodiment of the present application, such as the processor 1511, may include at least one of the following types: a general-purpose central processing unit (Central Processing Unit), a digital signal processor (Digital Signal Processor, DSP), a microprocessor, Application-Specific Integrated Circuit (ASIC), Microcontroller Unit (MCU), Field Programmable Gate Array (FPGA), or integrated circuit for implementing logic operations . For example, the processor 1111 may be a single-CPU processor or a multi-CPU processor. The at least one processor 1111 may be integrated in one chip or located on multiple different chips.

The memory in the embodiment of the present application, such as the memory 1512, may include at least one of the following types: read-only memory (ROM) or other types of static storage devices that can store static information and instructions, and random access memory (random access memory, RAM) or other types of dynamic storage devices that can store information and instructions, and can also be electrically erasable programmable read-only memory (EEPROM). In some scenarios, the memory can also be a compact disc (read-only memory, CD-ROM) or other disc storage, disc storage (including compact discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, 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 can be accessed by a computer, but is not limited to this.

The memory 1512 may exist independently and is connected to the processor 1511. Optionally, the memory 1512 may also be integrated with the processor 1511, for example, integrated in a chip. The memory 1512 can store program code that executes the technical solutions of the embodiments of the present application, and is controlled and executed by the processor 1511. The executed computer program codes can also be regarded as the driver program of the processor 1511. For example, the processor 1511 is configured to execute computer program code stored in the memory 1512, so as to implement the technical solution in the embodiment of the present application.

The transceiver 1513 may be used to support reception or transmission of radio frequency signals between the access network device and the terminal, and the transceiver 1513 may be connected to the antenna 1515. The transceiver 1513 includes a transmitter Tx and a receiver Rx. Specifically, one or more antennas 1515 may receive a radio frequency signal, and a receiver Rx of the transceiver 1513 is configured to receive the radio frequency signal from the antenna, convert the radio frequency signal into a digital baseband signal or a digital intermediate frequency signal, and convert the digital The baseband signal or the digital intermediate frequency signal is provided to the processor 1511, so that the processor 1511 performs further processing on the digital baseband signal or the digital intermediate frequency signal, such as demodulation processing and decoding processing. In addition, the transmitter Tx in the transceiver 1513 is also used to receive the modulated digital baseband signal or digital intermediate frequency signal from the processor 1511, and convert the modulated digital baseband signal or digital intermediate frequency signal into a radio frequency signal, and pass a Or multiple antennas 1515 send the radio frequency signal. Specifically, the receiver Rx may selectively perform one or more levels of downmix processing and analog-to-digital conversion processing on the radio frequency signal to obtain a digital baseband signal or a digital intermediate frequency signal. The sequence is adjustable. The transmitter Tx may selectively perform one or more levels of upmixing processing and digital-to-analog conversion processing on the modulated digital baseband signal or digital intermediate frequency signal to obtain a radio frequency signal. The upmixing processing and digital-to-analog conversion processing The sequence is adjustable. Digital baseband signals and digital intermediate frequency signals can be collectively referred to as digital signals.

When the access network device is SN11, the access network device can implement the method performed by SN11 in the embodiment of the present application. For example, the processor 1111 can generate a second PDCP length of the first bearer and a PDCP of the first bearer. SN length change indication, the first configuration information of the first bearer, the processor 1111 may send the PDCP of the first bearer to the MN01 through the network interface 1114, the SN length change indication and the first configuration information of the first bearer, and the memory 1112 may store the first The length of the PDCP SN carried, such as the length of the first PDCP SN and / or the length of the second PDCP SN. For other steps implemented by the access network device through its components, reference may be made to the method performed by the SN11 in the embodiment of the present application, and details are not described herein again.

When the access network device is MN01, the access network device can implement the method performed by MN01 in the embodiment of the present application. For example, it can receive the PDCP SN length change indication of the first bearer and the first bearer through the network interface 1114. The first configuration information, the processor 1111 may generate the second configuration information of the first bearer according to the PDCP SN length indication of the first bearer, and the antenna 1115 may send the first configuration information of the first bearer and the first bearer first configuration information to the terminal 21. Second configuration information, the memory 1112 may store the PDCP SN length of the first bearer, such as the first PDCP SN length and / or the second PDCP SN length. For other steps implemented by the access network device through its components, reference may be made to the method performed by the MN01 in the embodiment of the present application, and details are not described herein again.

As shown in FIG. 16, it is a schematic structural diagram of a terminal according to an embodiment of the present application. For the structure of the terminal 21, reference may be made to the structure shown in FIG.

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

For the transceiver 1612, the memory 1613, and the antenna 1616, reference may be made to the related description in FIG. 15 to implement similar functions.

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

The processor 1611 may be used to implement various functions for the terminal, for example, to process communication protocols and communication data, or to control the entire terminal device, execute a software program, and process data of the software program; or to assist completion Calculation processing tasks, such as graphics and image processing or audio processing; or the processor 1211 is used to implement one or more of the above functions

The output device 1614 communicates with the processor 1611 and can 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, or a projector. Wait. The input device 1615 communicates with the processor 1611 and can accept user input in a variety of ways. For example, the input device 1615 may be a mouse, a keyboard, a touch screen device, or a sensing device.

When the terminal is the terminal 21, the access network device may implement the method performed by the terminal 21 in the embodiment of the present application. For example, the first configuration information of the first bearer and the first configuration of the first bearer may be received from the MN01 through the antenna 1616. Second configuration information. For other steps implemented by the terminal through its components, reference may be made to the method performed by the terminal 21 in the embodiment of the present application, and details are not described herein again.

As shown in FIG. 17, it is a schematic structural diagram of a device 1700 according to an embodiment of the present application.

The communication device 1700 includes a processor 1701, a communication interface 1702, and the processor 1701 is connected to the communication interface 1702. Optionally, the communication device 1700 may further include a memory 1703, and the memory 1703 is connected to the processor 1701 and the communication interface 1702.

The processor 1701 may include at least one of the following types: a general-purpose central processing unit (CPU), a digital signal processor (DSP), a microprocessor, and an application-specific integrated circuit (Application-Specific Integrated Circuit) Specific Integrated Circuit (ASIC), microcontroller (MCU), Field Programmable Gate Array (FPGA), or integrated circuit for implementing logic operations. For example, the processor 1711 may be a single-CPU processor or a multi-CPU processor. The at least one processor 1711 may be integrated in one chip or located on multiple different chips.

The memory 1703 may include at least one of the following types: read-only memory (ROM) or other types of static storage devices that can store static information and instructions, random access memory (RAM), or Other types of dynamic storage devices that store information and instructions can also be electrically erasable programmable read-only memories (EEPROMs). In some scenarios, the memory can also be a compact disc (read-only memory, CD-ROM) or other disc storage, disc storage (including compact discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, 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 can be accessed by a computer, but is not limited to this.

The communication interface 1702 may have a transmitting and receiving function, and is configured to communicate with other communication devices or other devices in the communication device.

The memory 1703 may exist independently, and is connected to the processor 1701 through a communication bus. The memory 1703 may also be integrated with the processor 1701.

The device 1700 may be a MN (e.g. MN01), a chip in MN (e.g. MN01), a SN (e.g. SN11), a chip in SN (e.g. SN11), a CU (e.g. CU0111 or CU1111), a CU (e.g. CU0111 or CU1111) Chip, DU (such as DU0121 or DU1121).

When the device 1700 is a chip in MN01 or MN01, the memory 1703 may store instructions and data of the method executed by MN01 in the embodiment of the present application, and the processor 1701 may read the method instructions and data in the memory 1703 and run , So as to implement the method executed by MN01 in the embodiment of the present application. When the device 1700 is MN01, the communication interface 1703 may include interfaces with other access network devices, such as an interface with SN11, and the communication interface may further include an antenna and a transceiver, such as the antenna 1515 and the transceiver 1513 in FIG. 15 When the device 1700 is a chip in the MN01, the communication receiving 1703 may be an input or output interface, a pin, or a circuit, and the processor 1701 and the memory 1703 may be integrated together.

When the device 1700 is a chip in SN11 or SN11, the memory 1703 may store instructions and data of the method executed by SN11 in the embodiment of the present application, and the processor 1701 may read the method instructions and data in the memory 1703 and run , So as to implement the method executed by SN11 in the embodiment of the present application. When the device 1700 is SN11, the communication interface 1703 may include interfaces with other access network devices, such as an interface with MN01, and the communication interface may further include an antenna and a transceiver, such as the antenna 1515 and the transceiver 1513 in FIG. 15 When the device 1700 is a chip in the SN11, the communication receiving 1703 may be an input or output interface, a pin, or a circuit, and the processor 1701 and the memory 1703 may be integrated together.

When the device 1700 is a chip in CU0111 (or CU1111) or CU1111 (or CU1111), the memory 1703 may store instructions and data of the method executed by CU0111 (or CU1111) in the embodiment of the present application, and the processor 1701 may The method instructions and data in the memory 1703 are read and run, thereby implementing the method executed by CU0111 (or CU1111) in the embodiment of the present application. When the device 1700 is CU0111 (or CU1111), the communication interface 1703 may include an interface with DU0121 (or DU1121), and may also include an interface with CU1111 (or CU0111); when the device 1700 is CU0111 (or CU1111) When the chip is installed, the communication receiving 1703 may be an input or output interface, a pin or a circuit, etc. The processor 1701 and the memory 1703 may be integrated together.

When the device 1700 is a chip in DU0121 (or DU1121) or DU0121 (or DU1121), the memory 1703 may store instructions and data of the method executed by DU0121 (or DU1121) in the embodiment of the present application, and the processor 1701 may The method instructions and data in the memory 1703 are read and run, thereby implementing the method executed by DU0121 (or DU1121) in the embodiment of the present application. When the device 1700 is DU0121 (or DU1121), the communication interface 1703 may include an interface with CU0111 (or CU1111), and may further include a transceiver and an antenna. The transceiver and the antenna may be used to send to or from the terminal 21 Receive data, such as the first configuration information of the first bearer and the second configuration information of the first bearer; when the device 1700 is a chip in CU0111 (or CU1111), the communication reception 1703 may be an input or output interface, a pin, or a circuit Etc., the processor 1701 and the memory 1703 may be integrated together.

An embodiment of the present application further provides a computer-readable storage medium. The methods described in the foregoing 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 can include computer storage media and communication media, and can also include any medium that can transfer computer programs from one place to another. A storage media may be any available media that can be accessed by a computer.

As an optional design, the 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 with instructions or data structures The required program code is stored in a form and can be accessed by a computer. Also, any connection is properly termed a computer-readable medium. For example, if you use coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technology (such as infrared, radio, and microwave) to transmit software from a network node, server, or other remote source, coaxial cable, fiber optic Cable, twisted pair, DSL or wireless technologies such as infrared, radio and microwave are included in the definition of the medium. Magnetic disks and optical discs as used herein include compact discs (CDs), laser discs, optical discs, digital versatile discs (DVDs), floppy discs, and Blu-ray discs, where magnetic discs typically reproduce data magnetically, and optical discs use lasers to reproduce data optically. Combinations of the foregoing should also be included within the scope of computer-readable media.

The embodiment of the present application also provides a computer program product. The methods described in the foregoing method embodiments may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. If implemented in software, it may be implemented in whole or in part in the form of a computer program product. A computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the procedures or functions described in the foregoing method embodiments are generated. The computer may be a general-purpose computer, a special-purpose computer, a computer network, a network device, a user equipment, or another programmable device.

Figure 18-20 below introduces a scheme for changing the length of PDCP and SN. In this scheme, when PDCP SN length changes, MN01 can assign a new bearer identifier to the bearer, and then MN01 and SN11 generate the old bearer identifier of the bearer. The release configuration information of the corresponding entity and the added configuration information of the entity corresponding to the new bearer identifier of the bearer, the terminal 21 executes the release of the entity corresponding to the old bearer identifier of the bearer and the entity corresponding to the new bearer identifier of the bearer. increase. The method is described below from the perspective of the primary node and the secondary node.

The following M1 method can be executed by a master node or a chip in the master node. The M1 method includes:

M101: Obtain the second PDCP SN length of the first bearer.

Optionally, the second PDCP SN length of the first bearer may be generated or determined by the master node, or the second PDCP SN length of the first bearer may be received from the secondary node.

M102: When the length of the second PDCP SN of the first bearer is different from the length of the first PDCP SN of the first bearer, determine the second bearer identifier of the first bearer.

The first PDCP SN length of the first bearer may be the length of the first bearer stored by the master node before the second PDCP SN length of the first bearer is obtained.

Optionally, the second bearer identifier of the first bearer is different from the first bearer identifier of the first bearer.

Optionally, the first bearer identifier of the first bearer may be the bearer identifier of the first bearer when the PDCP SN length of the first bearer is the first PDCP SN length.

Optionally, the first bearer identifier of the first bearer may be the bearer identifier of the first bearer stored by the master node.

M103: Send the second bearer identifier of the first bearer to the secondary node.

Optionally, the method may further include M104-M106.

M104: Receive the secondary node configuration information of the first bearer from the secondary node.

Optionally, the secondary node configuration information of the first bearer may include increased configuration information of an entity on the secondary node corresponding to the second bearer identifier of the first bearer.

Optionally, the secondary node configuration information of the first bearer may include configuration information of release of an entity on the secondary node corresponding to the first bearer identifier of the first bearer.

M105: Generate master node configuration information of the first bearer.

Optionally, the configuration information of the master node of the first bearer may include added configuration information of entities on the master node corresponding to the second bearer identifier of the first bearer.

Optionally, the configuration information of the master node of the first bearer may include the release configuration information of the entity on the master node corresponding to the first bearer identifier of the first bearer.

M106: Send the secondary node configuration information of the first bearer and the primary node configuration information of the first bearer to the terminal.

The following M2 method can be executed by a secondary node or a chip in the secondary node.

M201: Determine the second PDCP SN length of the first bearer.

M201 is optional.

M202: Receive the second bearer identifier of the first bearer from the master node.

M203: Send the secondary node configuration information of the first bearer to the primary node.

The following is further described with reference to FIGS. 18 to 20.

FIG. 18 is a schematic diagram of an implementation manner of changing a PDCP SN length, where an EN-DC scenario is taken as an example.

S1801: MN01 sends a first request message to SN11.

Optionally, the first request message may be a first secondary node addition request message or a first secondary node modification request message.

For example, the first request message may be a first secondary node addition request message. Before the MN01 sends a secondary node addition request message to the SN11, the bearer type of the first bearer may be an MCG bearer terminated by the MN, and MN01 may decide to add a secondary node. The bearer type of a bearer. The first bearer can be terminated at the SN after adding the secondary node, that is, the PDCP entity of the first bearer after adding the secondary node is on SN11. For example, the bearer type of the first bearer after adding the secondary node is SN terminated MCG Bearer, SN terminated SCG bearer or SN terminated split bearer.

For example, the first request message may be a first secondary node modification request message, and the first secondary node modification request message may indicate a modification of the bearer type of the first bearer. Before the MN01 sends the secondary node modification request message to the SN11, the bearer of the first bearer is modified. The type can be terminated at the MN or SN. MN01 can decide to modify the bearer type of the first bearer. After modifying the bearer type, the first bearer can be terminated at the SN, that is, the PDCP entity of the first bearer after adding the secondary node is at SN11. The bearer type of the first bearer after the secondary node is added is an SN terminated MCG bearer, an SN terminated SCG bearer, or an SN terminated split bearer.

The first request message may include:

(1) The identifier (ID) on the interface of the terminal 21 allocated by the MN01 to the terminal 21.

This interface is the interface between MN01 and SN11.

The ID of the terminal 21 assigned by the MN01 to the terminal 21 is used to identify the terminal 21 on the interface between the MN01 and the SN11.

For example, in the EN-DC scenario, the interface between MN01 and SN11 is an X2 interface, and the ID assigned by the MN01 to the terminal 21 at the interface is an X2 application protocol (AP) ID.

For another example, in the NGEN-DC, NR-DC and NR and E-UTRA dual connection (NR-E-UTRA Dual Connectivity, NE-DC) scenario, the interface between MN01 and SN11 is the Xn interface, and MN01 is the terminal 21 The ID assigned on the interface is XnAP ID. It should be noted that in the NR-DC, the core network element 31 is 5GC, MN01 is gNB, and SN11 is gNB. In NGEN-DC and NE-DC, the core network element 31 is 5GC.

(2) Evolved universal terrestrial radio access network (E-UTRAN) radio bearer (E-UTRAN) radio access bearer (E-RAB) ID of the first bearer.

(3) The first bearer identifier of the first bearer.

(4) The indication information of the bearer type of the first bearer after the bearer type is modified.

(5) Modify the configuration information of the PDCP entity of the first bearer before the bearer type.

For example, before adding SN11, the bearer type of the first bearer is the MCG bearer terminated by the MN, and the configuration information of the PDCP entity of the first bearer is the configuration information of the PDCP entity carried by the MN terminated MCG.

The configuration information of the PDCP entity of the first bearer before the bearer type is modified may be used to assist the SN11 in generating the configuration information of the new PDCP entity.

The configuration information of the PDCP entity of the first bearer before modifying the bearer type may include the first PDCP SN length of the first bearer, for example, the first PDCP SN length may be 12 bits, and the first PDCP SN length of the first bearer is the first before adding SN11. PDCP SN length of the bearer.

Here, the first PDCP SN length of the first bearer may include one or two of the first uplink PDCP SN length of the first bearer and the first downlink PDCP SN length of the first bearer, such as the first PDCP of the first bearer. The SN length may be the first uplink PDCP SN length of the first bearer; or the first PDCP SN length of the first bearer may be the first downlink PDCP SN length of the first bearer; or the first PDCP SN of the first bearer The length may be the first uplink PDCP SN length of the first bearer and the first downlink PDCP SN length of the first bearer. The first uplink PDCP SN length of the first bearer is the uplink PDCP SN length of the first bearer before SN11 is increased; the first downlink PDCP SN length of the first bearer is the downlink PDCP SN length of the first bearer before SN11 is increased.

For example, when the first request message is a first secondary node addition request message, the first secondary node addition request message may refer to the 3rd Generation Partnership Project (3GPP) Technical Specification (TS) 36.423 V15 .1.0 Section 9.1.4.1 related to the "auxiliary gNB addition request" ("SGNB ADDITION REQUEST"), for example, the above information (2) (3) can be obtained through "SGNB ADDITION REQUEST" "to be added E- The cell "E-RAB Item" and the cell "Data Radio Bearer ID" ("DRB ID") in the "RAB Item" ("E-RABs") are carried.

For example, when the first request message is the first secondary node modification request message, the first secondary node modification request message can refer to the relevant content of "SGNB Modification Certificate" in section 9.1.4.5 of 3GPP TS 36.423 V15.1.0, for example, the above Information (2) (3) can be carried by the cell "E-RAB ID" and the cell "DRB ID" in the "E-RABs To Be Added Item" in the "SGNB Modification Request".

S1802: SN11 determines the second PDCP SN length of the first bearer.

The second PDCP SN length of the first bearer is the PDCP SN length of the first bearer after adding SN11.

For example, when the first request message is a secondary node addition request message, the secondary node addition request message may indicate that the PDCP entity of the first bearer after adding SN11 is on SN11, and SN11 may generate the second PDCP SN length of the first bearer.

For example, when the first request message is a secondary node modification request message, the secondary node modification request message may indicate that the PDCP entity of the first bearer is on SN11 after modifying the bearer type, and SN11 may generate the second PDCP SN length of the first bearer.

The length of the second PDCP SN of the first bearer may be different from the length of the first PDCP SN of the first bearer.

For example, the length of the second PDCP SN of the first bearer may be 18 bits.

Optionally, the second PDCP SN length may include one or two of the second uplink PDCP SN length of the first bearer and the second downlink PDCP SN length of the first bearer, such as the second PDCP SN length of the first bearer. It may be the second uplink PDCP SN length of the first bearer; or, the second PDCP SN length of the first bearer may be the second downlink PDCP SN length of the first bearer; or the second PDCP SN length of the first bearer may be The length of the second uplink PDCP SN of the first bearer and the length of the second downlink PDCP SN of the first bearer. The second uplink PDCP SN length of the first bearer is the uplink PDCP SN length of the first bearer before the bearer is modified; the second downlink PDCP SN length of the first bearer is the downlink PDCP SN length of the first bearer before the bearer type is modified.

It should be noted that in the embodiment of the present application, the length of the second PDCP SN is different from the length of the first PDCP SN. It can be understood that the length of the second uplink PDCP SN is different from the length of the first uplink PDCP SN, or the length of the second downlink PDCP The length of the first downlink PDCP SN is different.

S1803: SN11 sends a first request response message to MN01.

Optionally, the first request corresponding message may be a secondary node addition request response message or a secondary node modification request response message.

For example, when the first request message is the first secondary node addition request message, the first request response message is the first secondary node addition request response message; when the first request message is the first secondary node modification request message, the first request The response message is a first secondary node modification request response message.

The first request response message may include:

(1) The ID of the terminal 21 assigned by the MN01 to the terminal 21 on the interface

You can refer to the related content in the ID of the terminal 21 assigned to the terminal 21 by MN01 in S1801.

(2) The ID of the terminal 21 assigned by the SN11 to the terminal 21 on the interface

The interface is an interface between MN01 and SN11.

The ID on the interface of the terminal 21 allocated by the SN11 to the terminal 21 is used to identify the terminal 21 on the interface between the SN11 and the MN01.

For example, in the EN-DC scenario, the interface between MN01 and SN11 is the X2 interface, and the ID on the interface of the terminal 21 allocated by the SN11 to the terminal 21 is X2AP ID.

For another example, in the NGEN-DC, NR-DC, and NE-DC scenarios, the interface between MN01 and SN11 is an Xn interface, and the ID on the interface assigned by SN11 to terminal 21 is XnAPID.

(3) E-RAB identification of the first bearer

It may be the same as the E-RAB identifier of the first bearer carried in the first request message in S1801, and may refer to the related content of the E-RAB identifier in S1801.

(4) Second PDCP SN length of the first bearer

Optionally, when SN11 determines the second PDCP SN length of the first bearer, and the second PDCP SN length of the first bearer is different from the first PDCP SN length of the first bearer, SN11 may not generate the first The configuration information of the entity on the SN11 corresponding to the bearer identifier, the first response message may not include the configuration information of the entity on the SN11 corresponding to the first bearer identifier of the first bearer, and wait until the first After the second bearer identifier, the configuration information of the first bearer on the SN11 is delivered, which can save communication resources.

S1804: MN01 sends a second request message to SN11.

Optionally, the second request message may be a second secondary node addition request message or a second secondary node modification request message.

For example, when the first request message is a request message for a first secondary node addition, the second request message may be a request message for a second secondary node or a second secondary node modification request message.

For example, when the first request message is the first secondary node modification request message, the second request message may be the second secondary node modification request message.

In S1803, after receiving the first request response message sent by SN11, MN01 can obtain the second PDCP SN length of the first bearer, and MN01 can compare the first PDCP SN length of the first bearer with the second PDCP SN length of the first bearer. When different, it indicates that SN11 changed the PDCP SN length of the first bearer. MN01 can provide the second bearer identifier for the first bearer and send it to SN11 for SN11 to perform the release and increase of the bearer first. The second bearer identifier is different from the first bearer identifier of the first bearer.

The second request message may include:

For details, refer to the ID on the interface of the terminal 21 allocated by the MN01 to the terminal 21 in S1801.

(2) E-RAB identification of the first bearer

It may be the same as the E-RAB identifier of the first bearer carried in the first request message in S1801, and the E-RAB identifier of the first bearer carried in the first request response message in S1803.

(3) The second bearer identifier of the first bearer

The first bearer identifier of the first bearer and the second bearer identifier of the first bearer correspond to the same E-RAB identifier.

Optionally, for the case where the second request message is the second secondary node modification request message, at this time, it is necessary to indicate the E-RAB ID of the first bearer in the bearer modification list in the second secondary node modification request message. At the same time, a second bearer identifier of the first bearer is indicated.

For example, the cell "DRB ID" can be added to the "E-RAB item to be modified" ("E-RABs To Be Modified Item") in the "SGNB Modifications REQUEST" section of 9.1.4.5 in 3GPP TS 36.423 V15.1.0. ", The specific cell structure can be shown in Table 1 below:

Table 1

Optionally, the second request message may further include first indication information.

As a first optional implementation manner, the first indication information is used to indicate that a bearer identifier of the first bearer is changed.

As a second optional implementation manner, the first indication information may indicate that the second request message is related to the first request message, and where the second request message is related to the first request message, it can be understood that the second request message changes the first request. The bearer identifier in the message, or the second request message is a continuation of the first request message.

As a third optional implementation manner, the first indication information may indicate that the second request message is related to the first request response message. Here, the second request message is related to the first request response message. It can be understood that the second request message is based on the first request message. A request response message is generated, or the second request message is a response to the first request response message.

As a fourth optional implementation manner, the first indication information may instruct the SN11 to generate configuration information based on the second bearer identifier of the first bearer. For example, when the second request message is a second secondary node modification request message, the SN11 is required to generate a complete set of configurations. The first indication information can be used to instruct the SN11 to generate a full configuration, instead of based on the configuration generated in S1803. Make a delta configuration.

It should be noted that the first indication information may be carried by an existing cell, and the existing cell may be used by the MN01 to request the latest configuration on the SN11 from the SN11. In the embodiment of the present application, the meaning of the cell may be extended. After receiving the second bearer identifier and the first indication information of the first bearer, the SN11 may generate a complete configuration for the terminal 21. For example, the existing cell may be the cell "SCG Configuration Query" in 39.2 TS36.423 V15.1.0 section 9.2.103.

Alternatively, a new cell may be defined, and the first indication information may be carried by a new cell, and the new cell is used to instruct the SN 11 to generate a complete configuration for the terminal 21.

The above are all exemplary illustrations without any limitation.

In the foregoing multiple optional implementation manners, the first indication information may specifically include one or two of the ID of the terminal 21 allocated by the SN11 to the terminal 21 and the first bearer identifier of the first bearer, or may be Others are not limited in the embodiments of the present application.

Optionally, MN01 and SN11 may negotiate the first indication when the second request message includes one or two of the ID of the terminal 21 allocated by the SN11 for the terminal 21 and the first bearer identifier of the first bearer. The information may indicate the contents of the various optional embodiments described above.

When the second request message is the second secondary node addition request message, by carrying the first instruction information in the second secondary node addition request message, it is possible to avoid SN11 after receiving the second secondary node addition request message due to the second secondary node The node addition request message is the same as the E-RAB identifier of the first bearer carried in the first secondary node addition request message, and SN11 treats the second secondary node addition request message as an abnormal message without processing.

When the second request message is the second secondary node modification request message, by carrying the first indication information in the second secondary node modification request message, it can be avoided that SN11 considers the second secondary node to receive the second secondary node modification request message after receiving the second secondary node modification request message. The node modification request message is used to modify the identity of the first bearer, so as to modify only the bearer identity of the first bearer, for example, from the first bearer identity to the second bearer identity.

Optionally, the second request message may not include the first indication information, for example, the first request response message in S1803 does not include the configuration information of the entity on the SN11 corresponding to the first bearer identifier of the first bearer, indicating that SN11 has determined that the occurrence In order to change the PDCP SN length without generating a configuration in S1803, at this time, SN11 knows that a complete set of configuration needs to be generated at this time, and no additional instructions are required.

The following describes, with reference to S1805-S1807, MN01 and SN11 for the terminal 21 to generate the release configuration information of the entity corresponding to the first bearer identifier and the added configuration information of the entity corresponding to the second bearer identifier.

S1805: SN11 generates secondary node configuration information of the first bearer.

After receiving the second bearer identifier of the first bearer, the SN11 can generate the secondary node configuration information of the first bearer.

Optionally, the configuration information of the secondary node of the first bearer includes configuration information released by the PDCP entity corresponding to the first bearer identifier and configuration information added by the PDCP entity corresponding to the second bearer identifier.

For example, before the bearer type is modified, the bearer type of the first bearer is the MCG bearer terminated by the MN. After the bearer type is modified, the bearer type of the first bearer is the MCG bearer terminated by the SN. The configuration information of the secondary node of the first bearer may include the first bearer identifier Release of the corresponding PDCP entity and configuration information added by the PDCP entity corresponding to the second bearer identifier.

Optionally, the configuration information of the secondary node of the first bearer may further include added configuration information of the RLC entity corresponding to the second bearer identifier, and optionally, it may further include configuration information of the logical entity corresponding to the second bearer identifier.

For example, before the bearer type is modified, the bearer type of the first bearer is the MCG bearer terminated by the MN. After the bearer type is modified, the bearer type of the first bearer is the SN terminated SCG bearer or the SN terminated split bearer. The configuration information of the secondary node of the first bearer is It may include the release configuration information of the PDCP entity corresponding to the first bearer identifier and the added configuration information of the PDCP entity corresponding to the second bearer identifier, and the added configuration information of the RLC entity corresponding to the second bearer identifier and the second bearer identifier. Added configuration information for the MAC entity.

Optionally, the configuration information of the secondary bearer of the first bearer may further include the configuration information of the release of the RLC entity corresponding to the first bearer identifier and the added configuration information of the RLC entity corresponding to the second bearer identifier. Configuration information of release of a logical channel corresponding to one bearer identifier and addition of a logical channel corresponding to the second bearer identifier.

For example, before the bearer type is modified, the bearer type of the first bearer is an MN terminated split bearer. After the bearer type is modified, the bearer type of the first bearer is an SN terminated SCG bearer or an SN terminated split bearer. It may include the release configuration of the PDCP entity and RLC entity corresponding to the first bearer identifier and the addition configuration of the PDCP entity and RLC entity corresponding to the second bearer identifier. Optionally, it may also include the release configuration of the logical channel corresponding to the first bearer identifier Increased configuration of the logical channel corresponding to the second bearer identifier.

S1806: SN11 sends a second request response message to MN01.

The second request response message may include secondary node configuration information of the first bearer.

Optionally, the second request response message may be a second secondary node addition request response message or a second secondary node modification request response message.

For example, when the second request message adds a request message to the second secondary node, the second request response message adds a request response message to the second secondary node; when the second request message is the second secondary node modification request message, the second request The response message is a modification request response message for the second secondary node.

S1807: MN01 generates master node configuration information of the first bearer.

Optionally, the configuration information of the master node of the first bearer may include the release configuration information of the RLC entity corresponding to the first bearer identifier of the first bearer and the added configuration information of the RLC entity corresponding to the second bearer identifier. Optionally, the release configuration of the logical channel corresponding to the first bearer identifier and the increase configuration information of the logical channel corresponding to the second bearer identifier may also be included.

For example, before the bearer type is modified, the first bearer type is an MN terminated MCG bearer or the MN terminated SPLIT bearer. After the bearer type is modified, the first bearer type is an SN terminated MCG bearer or an SN terminated SPLIT bearer. The master node configuration information of the bearer may include configuration information of release of the RLC entity corresponding to the first bearer identifier and added configuration information of the RLC entity corresponding to the second bearer identifier. Optionally, the release configuration of the logical channel corresponding to the first bearer identifier and the increase configuration information of the logical channel corresponding to the second bearer identifier may also be included.

Optionally, the configuration information of the master node of the first bearer may include the release configuration information of the RLC entity corresponding to the first bearer identifier of the first bearer. Optionally, the release configuration information of the logical channel corresponding to the first bearer identifier may also be included.

For example, before the bearer type is modified, the bearer type of the first bearer is the MCG bearer terminated by the MN or the SPLIT bearer of the MN terminates. After the bearer type is modified, the bearer type of the first bearer is the SN terminated SCG bearer. The master node configuration information of the first bearer It may include release configuration information of the RLC entity corresponding to the first bearer identifier of the first bearer and release configuration information of the logical channel corresponding to the first bearer identifier.

S1808: MN01 sends an RRC connection reconfiguration message to terminal 21.

The RRC connection reconfiguration message may include the second bearer identifier of the first bearer, the primary node configuration information of the first bearer, and the secondary node configuration information of the first bearer.

Optionally, according to the bearer identifier included in the RRC connection reconfiguration message, the terminal 21 performs the first delete and then add operation of the first bearer according to the primary node configuration information of the first bearer and the secondary node configuration information of the first bearer.

Optionally, the terminal 21 may perform deletion of the first bearer corresponding to the first bearer identifier and addition of the first bearer corresponding to the second bearer identifier according to the RRC connection reconfiguration message.

Optionally, according to the RRC connection reconfiguration message, the terminal 21 may perform an operation of deleting an entity corresponding to the first bearer identifier and adding an entity corresponding to the second bearer identifier.

S1809: The terminal 21 sends an RRC connection reconfiguration completion message to the MN01.

S1810: MN01 sends an SN reconfiguration completion message to SN11.

S1811: The terminal 21 and the SN11 complete random access.

Figure 18 uses the EN-DC scenario as an example, but the method in Figure 18 is also applicable to the NGEN-DC, NR-DC, and NE-DC scenarios, that is, the core network element 31 is 5GC. The following describes when the core network element 31 is 5GC. Changes in Figure 18.

Optionally, in the message that needs to carry the E-RAB ID in FIG. 18, the E-RAB identifier may not be carried or may be replaced with the first bearer identifier of the first bearer.

In S1801, the first request message may be a first secondary node addition request message or a first secondary node modification request message. The first request message may not carry the E-RAB identifier, and may carry the first bearer of the first bearer in S1801. Logo.

In S1803, the first request response message may be a first secondary node addition request response message or a first secondary node modification request response message, and the first bearer identifier of the first bearer may be used instead of the E-RAB identifier. For example, the first request The response message may not carry the E-RAB identifier and carry the first bearer identifier of the first bearer.

In S1804, when the second request message is an additional request message for the second secondary node, the second request message may not carry the E-RAB identifier, and carry the first bearer identifier of the first bearer and the second bearer identifier of the first bearer in S1804. Bearer identifier; when the second request message is the second secondary node modification request message, the second secondary node modification request message may not carry the E-RAB identifier, and carry the first bearer identifier of the first bearer and the first bearer identifier in S1804. For example, the second bearer identifier may refer to Table 1. The first bearer identifier of the first bearer and the second bearer identifier of the first bearer may be carried by the cell "DRB ID" of Table 1.

For example, taking the first request message in FIG. 18 as the first secondary station addition request message and the second request message as the second secondary station modification request message as an example, the second request message carries the first bearer identifier and the corresponding first The second bearer identification information is used to instruct the SN11 to change the bearer identification, that is, to replace the first bearer identification with the second bearer identification.

With the above solution, when the core network 31 is 5GC, by replacing the E-RAB identifier with the first bearer identifier of the first bearer, MN01 and SN11 can learn that the second bearer identifier corresponds to the first bearer identifier. The bearer, that is, the bearer identifier of the first bearer has changed.

In the method in FIG. 18, the present application also provides an alternative implementation manner. The second bearer identifier of the first bearer can be carried in S1803, without the need to carry the first bearer identifier of the first bearer. After receiving the second request message, it is determined that the second request message includes the bearer identifier of the first bearer, for example, the second bearer identifier of the first bearer. After receiving the second request message, SN11 may use the new bearer identifier to generate the first bearer identifier. The configuration information of the secondary node of a bearer, for example, the secondary node configuration information of the first bearer is used to generate the secondary node configuration information of the first bearer.

FIG. 19 is a schematic diagram of an embodiment of the variable PDCP SN length. Taking EN-DC as an example, in this embodiment, the first bearer ends at MN01 before and after the bearer type is modified; in addition, the first bearer is established at MN01 and SN11 before and after the bearer type is modified.

S1901: MN01 determines the second PDCP SN length of the first bearer.

The first bearer ends at MN01 before and after the bearer type is modified. MN01 can determine the PDCP SN length of the first bearer after the bearer type is modified. Here, the PDCP SN length of the first bearer after the bearer type is modified is called the second PDCP SN length The length of the PDCP SN of the first bearer before the bearer type is modified is called the first PDCP SN length.

Optionally, the second PDCP SN length of the first bearer may be an uplink PDCP SN length and / or a downlink PDCP SN length. For details, refer to the related content of the second PDCP SN length in S1802.

S1902: MN01 sends a secondary node modification request message to SN11.

When the length of the second PDCP SN is different from the length of the first PDCP SN, MN01 can regenerate a bearer identifier for the first bearer. Here, the bearer identifier of the first bearer with the modified bearer type is referred to as the second bearer identifier of the first bearer. The bearer identifier of the first bearer before the bearer type is modified is referred to as the first bearer identifier of the first bearer.

The secondary node modification request message may include the ID on the interface allocated by the MN01 to the terminal 21, the E-RAB ID of the first bearer, and the second PDCP SN length of the first bearer.

The secondary node modification request message may further include a second bearer identifier of the first bearer.

Optionally, the bearer modification list in the secondary node modification request message may indicate the E-RAB ID of the first bearer and the second bearer identifier of the first bearer.

For example, the cell "DRB ID" can be added to the "E-RABs To Be Modified Item" in the "SGNB Modifications REQUEST" section 9.1.4.5 of 3GPP TS 36.423 V15.1.0. The specific cell structure can be as shown in Table 1 above. As shown.

When the MN01 modifies the configuration of the bearer, the bearer modification list in the secondary node modification request message does not carry the identifier of the bearer. The secondary node modification request message carries the second bearer identifier of the first bearer, so that SN11 can learn that MN01 has been modified. The length of the PDCP and SN of the bearer needs to regenerate the configuration information of the bearer secondary node.

The following describes how MN01 and SN11 generate configuration information of the first bearer. MN01 and SN11 generate, for the terminal 21, configuration information of release of an entity corresponding to the first bearer identifier and added configuration information of an entity corresponding to the second bearer identifier.

S1903: SN11 generates secondary node configuration information of the first bearer.

After SN11 receives the second bearer identifier of the first bearer in S1903, it can obtain the first bearer identifier of the first bearer through the E-RAB identifier of the first bearer. For example, SN11 stores the E-RAB identifier and the corresponding first bearer identifier. The first bearer identifier of the bearer; then SN11 can compare the first bearer identifier of the first bearer and the second bearer identifier of the first bearer. When the first bearer identifier and the second bearer identifier of the first bearer are different, it means that MN01 is again The bearer is assigned a bearer identifier, and the SN11 can generate the secondary node configuration information of the first bearer.

Optionally, the secondary node configuration information of the first bearer may include configuration information of release of the RLC entity corresponding to the first bearer identifier and added configuration information of the RLC entity corresponding to the second bearer identifier. Optionally, the secondary node configuration information of the first bearer may include configuration information of the release of the logical channel corresponding to the first bearer identifier and increased configuration information of the logical channel corresponding to the second bearer identifier.

For example, the first bearer is an SCG bearer terminated by the MN before the bearer type is modified, the first bearer is an SPLIT bearer terminated by the MN after the bearer type is modified, or the first bearer is the SPLIT bearer terminated by the MN before the bearer type is modified. The bearer is an SCG bearer terminated by the MN after the bearer type is modified. The configuration information of the secondary node of the first bearer may include the configuration information of the release of the RLC entity corresponding to the first bearer identifier and the logical channel, and the RLC entity corresponding to the second bearer identifier. Added configuration information for logical channels.

S1904: SN11 sends a secondary node modification request response message to MN01.

The secondary node modification request response message includes the secondary node configuration information of the first bearer.

S1905: MN01 generates master node configuration information of the first bearer.

Optionally, the configuration information of the master node of the first bearer may include the release configuration information of the PDCP entity corresponding to the first bearer identifier and the added configuration information of the PDCP entity corresponding to the second bearer identifier.

Optionally, the configuration information of the master node of the first bearer may further include the added configuration information of the RLC entity corresponding to the second bearer identifier. Optionally, it may further include added configuration information of the logical channel corresponding to the first bearer identifier.

Optionally, the configuration information of the master node of the first bearer may further include release configuration information of the RLC entity corresponding to the first bearer identifier, and optionally, may also include configuration information of release of the logical channel corresponding to the first bearer identifier.

For example, the first bearer is an SCG bearer terminated by the MN before the bearer type is modified, and the first bearer is an SPLIT bearer terminated by the MN after the bearer type is modified. The master node configuration information of the first bearer may include a PDCP entity corresponding to the first bearer identifier. The released configuration information and the increased configuration information of the PDCP entity corresponding to the second bearer identifier, and the increased configuration information of the RLC entity corresponding to the second bearer identifier.

For example, the first bearer is an SPLIT bearer terminated by the MN before the bearer type is modified, and the first bearer is an SCG bearer terminated by the MN after the bearer type is modified. The master node configuration information of the first bearer may include a PDCP entity corresponding to the first bearer identifier. The released configuration information and the added configuration information of the PDCP entity corresponding to the second bearer identifier, and the released configuration information of the RLC entity corresponding to the first bearer identifier.

S1906: MN01 sends an RRC connection reconfiguration message to terminal 21.

The RRC connection reconfiguration message may include a second bearer identifier of the first bearer, secondary node configuration information of the first bearer, and master node configuration information of the first bearer.

S1907: The terminal 21 sends an RRC connection reconfiguration completion message to the MN01.

S1908: MN01 sends a secondary node modification confirmation (SN) confirmation message to SN11.

Figure 19 takes the EN-DC scenario as an example, but the method in Figure 19 is also applicable to the NGEN-DC, NR-DC, and NE-DC scenarios, that is, the core network element 31 is 5GC. The following describes when the core network element 31 is 5GC. Changes in Figure 19.

Optionally, in the message that needs to carry the E-RAB ID in FIG. 19, the E-RAB identifier may be replaced with the first bearer identifier of the first bearer.

In S1902, the secondary node modification request message may not carry the E-RAB identifier, and may carry the first bearer identifier of the first bearer. In S1903, SN11 can judge the first bearer identifier of the first bearer and the second bearer identifier of the first bearer. When the first bearer identifier and the second bearer identifier of the first bearer are different, it means that MN01 has reassigned the bearer. Bearer ID. SN11 can generate the secondary node configuration information of the first bearer.

FIG. 20 is a schematic diagram of an implementation manner of changing the length of a PDCP SN, where an EN-DC scenario is taken as an example.

S2001: SN11 determines the second PDCP SN length of the first bearer.

The first bearer ends at SN11. SN11 may decide to change the PDCP SN length of the first bearer, for example, change the PDCP length of the first bearer from the first PDCP SN length to the second PDCP SN length.

Optionally, the first PDCP SN length may be the first uplink PDCP SN length and / or the first downlink PDCP SN length, and the second PDCP SN length may be the second uplink PDCP SN length and / or the second downlink PDCP SN length. Please refer to the related content in FIG. 18 and FIG. 19.

S2002: SN11 sends a secondary node modification request message to MN01.

The secondary node modification request message includes the ID of the terminal 21 assigned by the MN01 for the terminal 21, the ID of the terminal 21 assigned by the SN11 for the terminal 21, the E-RAB ID of the first bearer, and the second PDCP of the first bearer SN length.

After receiving the modification request message of the secondary node, MN01 can obtain the first PDCP SN length of the first bearer through the E-RAB ID of the first bearer. When the first PDCP SN length of the first bearer is different from the second bearer of the first bearer, When the length of the PDCP is SN, MN01 can determine the second bearer identifier of the first bearer. The second bearer identifier of the first bearer is different from the first bearer identifier of the first bearer. The first bearer identifier of the first bearer is that MN01 receives the secondary node. Before modifying the application message, the bearer identifier of the first bearer, for example, MN01 can save the E-RAB ID of the first bearer and the first bearer identifier of the first bearer.

S2003: MN01 sends a secondary node modification request message to SN11.

The secondary node modification request message may include an E-RAB identifier and a second bearer identifier of the first bearer.

Optionally, the bearer modification list in the second secondary node modification request message may indicate the E-RAB ID of the first bearer and the second bearer identifier of the first bearer.

For example, the cell "DRB ID" can be added to the "E-RABs To Be Modified Item" in the "SGNB Modifications REQUEST" section of Section 9.1.4.5 of 3GPP TS 36.423 V15.1.0. The specific cell structure can be as shown in Table 1 above. As shown.

S2004: SN11 generates secondary node configuration information of the first bearer.

Optionally, the configuration information of the secondary node of the first bearer may include release information of the PDCP entity corresponding to the first bearer identifier of the first bearer and the added configuration information of the PDCP entity corresponding to the second bearer identifier of the first bearer.

Optionally, the configuration information of the secondary node of the first bearer may include release information of the RLC entity corresponding to the first bearer identifier of the first bearer and the added configuration information of the RLC entity corresponding to the second bearer identifier of the first bearer. The configuration information of the release of the logical channel corresponding to the first bearer identifier of the first bearer and the added configuration information of the logical channel corresponding to the second bearer identifier of the first bearer may also be included.

For example, the first bearer is an SN-terminated MCG bearer before and after the PDCP SN length changes. The configuration information of the secondary node of the first bearer may include the release of the PDCP entity corresponding to the first bearer identifier of the first bearer and the second bearer of the first bearer. Added configuration information of the PDCP entity corresponding to the bearer identification.

For example, the first bearer is a SPLIT bearer terminated by SN before and after the SN length changes. The configuration information of the secondary node of the first bearer may include the release configuration of the PDCP entity and the release of the RLC entity corresponding to the first bearer identifier of the first bearer. The information and the added configuration information of the PDCP entity and the RLC entity corresponding to the second bearer identifier of the first bearer may optionally include configuration information of the release of the logical channel corresponding to the first bearer identifier of the first bearer and the first Added configuration information of the logical channel corresponding to the second bearer identifier of the bearer

S2005: SN11 sends a secondary node modification request response message to MN01.

The secondary node modification request response message may include secondary node configuration information of the first bearer.

S2006: MN01 generates master node configuration information of the first bearer.

Optionally, the configuration information of the master node of the first bearer may include the release of the RLC entity corresponding to the first bearer identifier of the first bearer and the added configuration information of the RLC entity corresponding to the second bearer identifier of the first bearer. The configuration information of the release of the logical channel corresponding to the first bearer identifier of the first bearer and the added configuration information of the logical channel corresponding to the second bearer identifier of the first bearer may also be included.

For example, the first bearer is an SN-terminated MCG bearer or an SN-terminated SPLIT bearer before and after the PDCP SN length changes. The master node configuration information of the first bearer may include the release of the RLC entity and the corresponding second bearer identifier of the first bearer The added configuration information of the RLC entity may optionally include configuration information of release of the logical channel corresponding to the first bearer identifier of the first bearer and added configuration information of the logical channel corresponding to the second bearer identifier of the first bearer. .

S2007: MN01 sends an RRC connection reconfiguration message to terminal 21.

S2008: The terminal 21 sends an RRC connection reconfiguration completion message to the MN01.

S2009: MN01 sends a secondary node modification confirmation message to SN11.

Figure 20 uses the EN-DC scenario as an example, but the method in Figure 20 is also applicable to the NGEN-DC, NR-DC, and NE-DC scenarios, that is, the core network element 31 is 5GC. The following describes when the core network element 31 is 5GC. Changes in Figure 20.

In S2002, the secondary node modification request message may not carry the E-RAB ID of the first bearer, and carry the first bearer identifier of the first bearer.

In S2003, the secondary node modification request message may not carry the E-RAB ID of the first bearer and the first bearer identifier of the first bearer, that is, the secondary node modification request message may carry the first bearer identifier of the first bearer and The second bearer identifier of the first bearer.

The M1 method, M2 method, and Figures 18 to 20 introduce the flowcharts of several methods for changing the length of PDCP and SN. It should be understood that MN01 may have functional units corresponding to the MN01 method or process steps, and SN11 may exist with SN11. Functional units corresponding to steps of a method or process.

The actions performed by MN01 in the M1 method, the M2 method, and the methods in FIG. 18 to FIG. 20 may be implemented by the communication device provided in FIG. 6a, FIG. 15 or FIG. 17; The actions performed by the SN11 may be implemented by the structure of the SN11 provided in FIG. 6b, FIG. 16 or FIG. For details, please refer to the related content in FIG. 6a, FIG. 6, and FIG. 15-17.

The M1 method, the M2 method, and the methods in FIG. 18 to FIG. 20 may be implemented by using a computer-readable storage medium and a computer program product. For details, refer to the related content of the embodiments of the present application regarding the computer-readable storage medium and the computer program product.

An embodiment of the present application provides a communication device including a memory and a processor. The memory is used to store a computer program, and the processor is used to call and run the computer program from the memory, so that the communication device M1 method, M2 method, FIG. 18 -The method performed by MN01 in FIG. 20.

An embodiment of the present application provides a communication device including a memory and a processor. The memory is used to store a computer program, and the processor is used to call and run the computer program from the memory, so that the communication device M1 method, M2 method, FIG. 18 -The method performed by SN11 in FIG. 20.

An embodiment of the present application provides a computer storage medium that stores a program of the M1 method, the M2 method, and the methods of MN01 or SN11 in FIG. 18 to FIG. 20.

The embodiment of the present application provides a computer program product. The program product includes a program. When the program is executed, the M1 method, the M2 method, and the MN01 or SN11 method in FIG. 18 to FIG. 20 are executed.

The M1 method, the M2 method, and the methods in FIG. 18 to FIG. 20 may be cross-referenced and cited with the content of the rest of the embodiments of the present application.

Claims

A communication method in dual connectivity, characterized in that the method includes:

The master node receives first PDCP SN length information from the secondary node, and the first PDCP SN length information is used to indicate the first PDCP SN length of the first bearer;

Obtaining, by the master node, the first PDCP SN length.
The method according to claim 1, wherein the obtaining, by the master node, the first PDCP SN length comprises:

The master node reads the first PDCP SN length in the first PDCP SN length information.
The method according to claim 1 or 2, further comprising:

Receiving, by the master node, first configuration information of the first bearer from the secondary node, where the first configuration information includes release and added configuration information of a PDCP entity of the first bearer;

Sending, by the master node, the first configuration information of the first bearer to a terminal.
The method according to claim 3, wherein the first configuration information further comprises release and added configuration information of a radio link layer control protocol RLC entity of the first bearer.
The method according to claim 4, wherein the release and added configuration information of the RLC entity includes configuration information of release of an RLC entity corresponding to a bearer identifier of the first bearer and RLC corresponding to the bearer identifier Added configuration information for the entity.
The method according to any one of claims 3-5, wherein the release and added configuration information of the PDCP entity includes configuration information of release of a PDCP entity corresponding to a bearer identifier of the first bearer and the configuration information of the PDCP entity. Added configuration information of the PDCP entity corresponding to the bearer identification.
The method according to any one of claims 1-6, further comprising:

Before receiving the first PDCP SN length information, the PDCP SN length of the first bearer is the second PDCP SN length;

When the length of the first PDCP SN is different from the length of the second PDCP SN, the master node generates second configuration information of the first bearer;

The master node sends the second configuration information to a terminal, and the second configuration information of the first bearer includes release and added configuration information of an RLC entity of the first bearer.
The method according to claim 7, wherein the release and added configuration information of the RLC entity of the first bearer includes the release configuration information of the RLC entity corresponding to the bearer identifier of the first bearer and the bearer Identifies the added configuration information of the corresponding RLC entity.
The method according to claim 7 or 8, wherein when the PDCP SN length of the first bearer is the second PDCP SN length, the first bearer ends at the master node, the method Also includes:

Generating, by the master node, the second PDCP SN length information, where the second PDCP SN length information is used to indicate the second PDCP SN length;

The method further includes:

Sending, by the master node, the second PDCP SN length information to the secondary node.
The method according to claim 7 or 8, characterized in that when the PDCP SN length of the first bearer is the second PDCP SN length, the first bearer ends at the secondary node, the method Also includes:

The master node receives second PDCP SN length information from the secondary node, and the second PDCP SN length information indicates the second PDCP SN length.
The method according to any one of claims 1 to 10, wherein the primary node receiving first PDCP SN length information from the secondary node comprises:

The primary node receives the first PDCP SN length information from the secondary node through a secondary node addition request response message, a secondary node modification request response message, or a secondary node modification request message.
A communication method in dual connectivity, characterized in that the method includes:

The secondary node generates the first packet data convergence protocol PDCP sequence number SN length information;

The secondary node sends the first PDCP SN length information to the master node, and the first PDCP SN length information is used to indicate to the master node the first PDCP SN length of the first bearer.
The method according to claim 12, wherein:

Before generating the first PDCP SN length information, the PDCP SN length of the first bearer is the second PDCP SN length, and the method further includes:

When the length of the first PDCP SN is different from the length of the second PDCP SN, the secondary node generates first configuration information of the first bearer;

The secondary node sends the first configuration information to the primary node, where the first configuration information includes release and added configuration information of the PDCP entity of the first bearer.
The method according to claim 13, wherein the first configuration information further comprises release and added configuration information of a radio link layer control protocol RLC entity of the first bearer.
The method according to claim 14, wherein the release and added configuration information of the RLC entity includes configuration information of release of an RLC entity corresponding to a bearer identifier of the first bearer and RLC corresponding to the bearer identifier Added configuration information for the entity.
The method according to any one of claims 13 to 15, wherein the release and added configuration information of the PDCP entity includes configuration information of release of a PDCP entity corresponding to a bearer identifier of the first bearer and the configuration information of the PDCP entity. Added configuration information of the PDCP entity corresponding to the bearer identification.
The method according to any one of claims 13-16, wherein when the PDCP SN length of the first bearer is the second PDCP SN length, the first bearer terminates at a secondary node, and the The method also includes:

The secondary node generates second PDCP SN length information, and the second PDCP SN length information indicates the second PDCP SN length;

The secondary node sends the second PDCP SN length information to the primary node.
The method according to any one of claims 13 to 16, wherein when the PDCP SN length of the first bearer is the length of the second PDCP SN, the first bearer terminates at the master node, The method includes:

The secondary node receives second PDCP SN length information from the master node, and the second PDCP SN length information indicates the second PDCP SN length.
The method according to any one of claims 13 to 18, wherein the secondary node sending the first PDCP SN length information to the primary node comprises:

When the length of the first PDCP SN is different from the length of the second PDCP SN, the secondary node sends the first PDCP SN length information to the primary node.
The method according to any one of claims 13 to 19, wherein the secondary node sending the first PDCP SN length information to the primary node comprises:

The secondary node sends the first PDCP SN length information to the primary node through a secondary node addition request response message, a secondary node modification request response message, or a secondary node modification request message.
A communication method in dual connectivity, characterized in that the method includes:

The terminal receives first configuration information of the first bearer from the secondary node through the primary node, where the first configuration information includes release and added configuration information of the PDCP entity of the first bearer;

The terminal configures the first bearer according to the first configuration information.
The method according to claim 21, wherein the first configuration information further comprises release and added configuration information of a radio link layer control protocol RLC entity of the first bearer.
The method according to claim 22, wherein the release and added configuration information of the RLC entity comprises release configuration information of an RLC entity corresponding to a bearer identifier of the first bearer and RLC corresponding to the bearer identifier Added configuration information for the entity.
The method according to any one of claims 21 to 23, wherein the release and added configuration information of the PDCP entity includes the release configuration information of the PDCP entity corresponding to the bearer identifier of the first bearer and the Added configuration information of the PDCP entity corresponding to the bearer identification.
The method according to any one of claims 21 to 24, wherein the terminal receives second configuration information of the first bearer from the master node, and the second configuration information includes the first bearer Release and added configuration information of the RLC entity;

The terminal configures the first bearer according to the second configuration information.
The method according to any one of claims 21 to 25, wherein the release and added configuration information of the RLC entity of the first bearer includes configuration information of release of the RLC entity corresponding to the bearer identifier of the first bearer and Added configuration information of the RLC entity corresponding to the bearer identifier.
The method according to any one of claims 21-26, wherein the configuring the first bearer according to the first configuration information comprises:

The terminal releases the PDCP entity of the first bearer and increases the PDCP entity of the first bearer according to the release of the PDCP entity of the first bearer and the increased configuration information, wherein the PDCP SN length of the released PDCP entity The PDCP SN length is different from the added PDCP entity.
A communication device, comprising a processor, the processor being coupled to a memory, the memory being used to store a computer program or instruction, and the processor being used to execute the computer program or instruction in the memory, The communication device is caused to perform the method according to any one of claims 1 to 11.
A communication device, comprising a processor, the processor being coupled to a memory, the memory being used to store a computer program or instruction, and the processor being used to execute the computer program or instruction in the memory, The communication device is caused to perform the method according to any one of claims 12 to 20.
A communication device, comprising a processor, the processor being coupled to a memory, the memory being used to store a computer program or instruction, and the processor being used to execute the computer program or instruction in the memory, The communication device is caused to perform the method according to any one of claims 21 to 27.
A device for performing the method according to any one of claims 1-11.
A device for performing the method according to any one of claims 12-20.
A device for performing the method according to any one of claims 21-27.
A computer storage medium is used for storing computer software instructions, and when the computer software instructions are executed, the method according to any one of claims 1-26 is implemented.
A computer program product, characterized in that the computer program product includes computer-executable instructions, and when the computer-executable instructions are executed, the method according to any one of claims 1-26 is implemented.
A communication system includes the device according to any one of claims 27 and 30, and the device according to any one of claims 28 and 31.
A communication method, characterized in that the method includes:

The first DU receives PDCP SN length configuration information from the first CU, where the PDCP SN length configuration information is used to indicate a PDCP SN length of the first bearer;

Obtaining, by the first DU, the length of the PDCP sequence number SN.
The method according to claim 37, further comprising:

Sending first configuration information to the first CU, where the first configuration information includes release and added configuration information of a radio link layer control protocol RLC entity of the first bearer.
The method according to claim 37, wherein sending the first configuration information to the first CU comprises:

When the first DU determines that the PDCP SN length is changed, the first configuration information is sent to the first CU.
The method according to claim 38 or 39, wherein the release and added configuration information of the RLC entity includes release configuration information of the RLC entity corresponding to the bearer identifier of the first bearer and the bearer identifier corresponds to Added configuration information for RLC entities.
A communication method, characterized in that the method includes:

The first CU determines the packet data convergence protocol PDCP sequence number SN length configuration information, and the PDCP SN length configuration information is used to indicate a PDCP SN length of the first bearer;

Sending, by the first CU, the PDCP SN length configuration information to a first DU.
The method according to claim 41, wherein the determining, by the first CU, the PDCP SN length configuration information comprises:

Generating, by the first CU, the PDCP SN length configuration information, or

The first CU is a CU in a master node, and the first CU receives the PDCP SN length configuration information from a secondary node, or

The first CU is a CU in a secondary node, and the first CU receives the PDCP SN length configuration information from a primary node.
The method according to claim 41 or 42, further comprising:

Receiving first configuration information from the first DU, where the first configuration information includes release and added configuration information of a radio link layer control protocol RLC entity of the first bearer.
The method according to any one of claims 41-43, wherein when the first CU determines that the PDCP SN length is changed, it sends the PDCP SN length configuration information to the first DU.
The method according to claim 43 or 44, wherein the release and added configuration information of the RLC entity includes release configuration information of the RLC entity corresponding to the bearer identifier of the first bearer and the bearer identifier corresponds to Added configuration information for RLC entities.
A communication method, characterized in that the method includes:

The CU of the master node receives the first PDCP SN length information from the secondary node, where the first PDCP SN length information is used to indicate the first PDCP SN length of the first bearer;

The CU of the master node obtains the first PDCP SN length.
The method according to claim 46, wherein the obtaining of the first PDCP SN length by the CU of the master node comprises:

The CU of the master node reads the first PDCP SN length according to the first PDCP SN length information.
The method according to claim 46 or 47, further comprising:

The CU of the master node receives first configuration information of the first bearer from the secondary node, and the first configuration information includes release and added configuration information of a PDCP entity of the first bearer;

The CU of the master node sends the first configuration information of the first bearer to a terminal through a DU of the master node.
The method according to claim 48, wherein the first configuration information further comprises release and added configuration information of a radio link layer control protocol RLC entity of the first bearer.
The method according to claim 49, wherein the release and added configuration information of the RLC entity comprises release configuration information of an RLC entity corresponding to a bearer identifier of the first bearer and RLC corresponding to the bearer identifier Added configuration information for the entity.
The method according to any one of claims 48 to 50, wherein the release and added configuration information of the PDCP entity includes the release configuration information of the PDCP entity corresponding to the bearer identifier of the first bearer and the Added configuration information of the PDCP entity corresponding to the bearer identification.
The method according to any one of claims 46-51, wherein the method further comprises:

Before receiving the first PDCP SN length information, the PDCP SN length of the first bearer is the second PDCP SN length;

When the length of the first PDCP SN is different from the length of the second PDCP SN, the CU of the master node sends the second PDCP SN length to the DU of the master node;

The CU of the master node receives second configuration information of the first bearer from the DU of the master node, and the second configuration information of the first bearer includes an RLC entity of the first bearer Release and added configuration information;

The CU of the master node sends the second configuration information to a terminal through the DU of the master node.
The method according to claim 52, wherein the release and added configuration information of the RLC entity of the first bearer includes the release configuration information of the RLC entity corresponding to the bearer identifier of the first bearer and the bearer Identifies the added configuration information of the corresponding RLC entity.
The method according to claim 52 or 53, wherein when the PDCP SN length of the first bearer is the second PDCP SN length, the first bearer ends at the master node, and the method Also includes:

The CU of the master node generates the second PDCP SN length information, and the second PDCP SN length information is used to indicate the second PDCP SN length;

The method further includes:

The CU of the master node sends the second PDCP SN length information to the secondary node.
The method according to claim 52 or 53, wherein when the PDCP SN length of the first bearer is the second PDCP SN length, the first bearer ends at the secondary node, and the method Also includes:

The CU of the master node receives second PDCP SN length information from the secondary node, and the second PDCP SN length information indicates the second PDCP SN length.
The method according to any one of claims 46-55, wherein the CU of the primary node receives first PDCP SN length information from the secondary node, comprising:

The CU of the primary node receives the first PDCP SN length information from the secondary node through a secondary node addition request response message, a secondary node modification request response message, or a secondary node modification request message.
A communication method in dual connectivity, characterized in that the method includes:

The CU of the secondary node generates the first packet data convergence protocol PDCP sequence number SN length information;

The CU of the secondary node sends the first PDCP SN length information to the master node, and the first PDCP SN length information is used to indicate to the master node the first PDCP SN length of the first bearer.
The method according to claim 57, wherein:

Before generating the first PDCP SN length information, the PDCP SN length of the first bearer is the second PDCP SN length, and the method further includes:

When the length of the first PDCP SN is different from the length of the second PDCP SN, the CU of the secondary node generates release and added configuration information of the PDCP entity of the first bearer;

The CU of the secondary node sends first configuration information to the primary node, where the first configuration information includes release and added configuration information of the PDCP entity of the first bearer.
The method according to claim 58, wherein the first configuration information further comprises release and added configuration information of a radio link layer control protocol RLC entity of the first bearer, and the method further comprises:

The CU of the secondary node sends the first PDCP SN length information to the secondary node's DU;

The CU of the secondary node receives release and added configuration information of a radio link layer control protocol RLC entity of the first bearer from the DU of the secondary node.
The method according to claim 59, wherein the release and added configuration information of the RLC entity includes configuration information of release of an RLC entity corresponding to a bearer identifier of the first bearer and RLC corresponding to the bearer identifier Added configuration information for the entity.
The method according to any one of claims 58 to 60, wherein the release and added configuration information of the PDCP entity includes the release configuration information of the PDCP entity corresponding to the bearer identifier of the first bearer and the Added configuration information of the PDCP entity corresponding to the bearer identification.
The method according to any one of claims 58 to 61, wherein when the PDCP SN length of the first bearer is the second PDCP SN length, the first bearer terminates at a secondary node, and the The method also includes:

The CU of the secondary node generates second PDCP SN length information, and the second PDCP SN length information indicates the second PDCP SN length;

The CU of the secondary node sends the second PDCP SN length information to the primary node.
The method according to any one of claims 58-61, wherein when the PDCP SN length of the first bearer is the second PDCP SN length, the first bearer terminates at the master node, The method includes:

The CU of the secondary node receives second PDCP SN length information from the master node, and the second PDCP SN length information indicates the second PDCP SN length.
The method according to any one of claims 58 to 63, wherein the CU of the secondary node sends the first PDCP SN length information to the primary node, including:

When the length of the first PDCP SN is different from the length of the second PDCP SN, the CU of the secondary node sends the first PDCP SN length information to the master node.
The method according to any one of claims 57 to 63, wherein the CU of the secondary node sends the first PDCP SN length information to the primary node, including:

The CU of the secondary node sends the first PDCP SN length information to the primary node through a secondary node addition request response message, a secondary node modification request response message, or a secondary node modification request message.
A communication device, comprising a processor, the processor being coupled to a memory, the memory being used to store a computer program or instruction, and the processor being used to execute the computer program or instruction in the memory, The communication device is caused to perform the method according to any one of claims 37 to 40.
A communication device, comprising a processor, the processor being coupled to a memory, the memory being used to store a computer program or instruction, and the processor being used to execute the computer program or instruction in the memory, The communication device is caused to perform the method according to any one of claims 41 to 65.
A device for performing the method according to any one of claims 37-40.
A device for performing the method according to any one of claims 41-65.
A computer storage medium is used for storing computer software instructions, and when the computer software instructions are executed, the method according to any one of claims 37-65 is implemented.
A computer program product, characterized in that the computer program product comprises computer-executable instructions, and when the computer-executable instructions are executed, the method according to any one of claims 37-65 is implemented.
A communication system comprising the device according to any one of claims 66 and 68 and the device according to any one of claims 67 and 69.
The communication system according to claim 72, further comprising the device according to any one of claims 29 and 32.
A communication method in a multi-system dual connection is characterized in that the method includes:

Generating the second packet data convergence protocol PDCP sequence number SN length configuration information of the first bearer, and the second PDCP SN length configuration information of the first bearer is used to indicate the second PDCP SN length of the first bearer;

When the length of the second PDCP SN of the first bearer is different from the length of the first PDCP SN of the first bearer, generating a PDCP SN length change indication of the first bearer;

Sending the PDCP SN length change indication of the first bearer to the master node MN;

The first PDCP SN length is the PDCP SN length of the first bearer and the PDCP SN length before the second PDCP SN length.
The method according to claim 74, wherein when the PDCP SN length of the first bearer is the length of the first PDCP SN, the first bearer terminates at a secondary node SN.
The method according to claim 74, further comprising:

Generating first configuration information of the first bearer;

Sending the first configuration information of the first bearer to the MN;

The first configuration information of the first bearer includes release and added configuration information of a PDCP entity.
The method according to claim 76, wherein the first configuration information of the first bearer further comprises release and added configuration information of a radio link layer control protocol RLC entity.
The method according to claim 74, wherein:

Before generating the second PDCP SN length configuration of the first bearer, the first bearer ends at the MN;

The method further includes:

Receiving first PDCP SN length configuration information from the MN, where the first PDCP SN length configuration information is used to indicate the first PDCP SN length.
The method according to claim 78, further comprising:

Generating first configuration information of the first bearer;

Sending the first configuration information of the first bearer to the MN;

The first configuration information of the first bearer includes added configuration information of a PDCP entity.
The method according to claim 78, further comprising:

Generating first configuration information of the first bearer;

Sending the first configuration information of the first bearer to the MN;

The first configuration information of the first bearer includes deletion and addition configuration information of a PDCP entity.
The method according to claim 79 or 80, wherein the first configuration information of the first bearer further includes release and added configuration information of an RLC entity.
A communication method in a multi-system dual connection is characterized in that the method includes:

Receive a packet data convergence protocol PDCP sequence number SN length change indication from the secondary node SN.
The method according to claim 82, wherein before the PDCP SN length of the first bearer changes, the first bearer ends at the SN.
The method according to claim 83, further comprising:

Receiving the SN configuration information of the first bearer from the SN;

Sending the SN configuration information of the first bearer to a terminal.

The first configuration information of the first bearer includes release and added configuration information of a PDCP entity.
The method according to claim 84, wherein the first configuration information of the first bearer further includes release and added configuration information of an RLC entity.
The method according to any one of claims 83-85, wherein the method further comprises:

Generating the second configuration information of the first bearer according to the PDCP SN length change indication of the first bearer;

Sending the second configuration information of the first bearer to a terminal;

The second configuration information of the first bearer includes release and added configuration information of an RLC entity.
The method according to claim 82, wherein before the PDCP SN length of the first bearer changes, the first bearer terminates at the master node MN;

The method further includes:

Sending the PDCP SN length before the PDCP SN length change of the first bearer to the SN.
The method according to claim 87, wherein the first configuration information of the first bearer includes added configuration information of a PDCP entity.
The method according to claim 87, wherein the first configuration information of the first bearer includes release and added configuration information of a PDCP entity.
The method according to claim 88 or 89, wherein the first configuration information of the first bearer includes release and added configuration information of an RLC entity.
The method according to any one of claims 87-90, wherein the method further comprises:

Generating the second configuration information of the first bearer according to the PDCP SN length change indication of the first bearer;

Sending the second configuration information of the first bearer to a terminal;

The second configuration information of the first bearer includes configuration information of release of a PDCP entity.
The method according to any one of claims 87-90, wherein the method further comprises:

Generating second configuration information of the first bearer according to the PDCP SN length change indication of the first bearer;

Sending the second configuration information of the first bearer to a terminal;

The second configuration information of the first bearer includes release and added configuration information of the RLC entity.
The method according to claim 91, wherein the second configuration information of the first bearer further includes release and added configuration information of an RLC entity.
A communication device, comprising a memory and a processor, where the memory is used to store a computer program, and the processor is used to call and run the computer program from the memory, so that the communication device executes any one of claims 74 to 81 Methods.
A communication device, comprising a memory and a processor, where the memory is used to store a computer program, and the processor is used to call and run the computer program from the memory, so that the communication device executes any one of claims 82 to 83 Methods.
A computer storage medium, characterized by storing a program, wherein the program is used to implement the method according to any one of claims 74 to 93.