WO2019024115A1

WO2019024115A1 - Method for acquiring data radio bearer identifier and base station

Info

Publication number: WO2019024115A1
Application number: PCT/CN2017/096111
Authority: WO
Inventors: 徐海博; 坦尼•纳坦•爱德华; 桑•爱民•贾斯汀
Original assignee: 华为技术有限公司
Priority date: 2017-08-04
Filing date: 2017-08-04
Publication date: 2019-02-07
Also published as: EP3664535A1; JP6987964B2; KR102560530B1; AU2021266272B2; BR112020002056A2; AU2017425816A1; US11277764B2; US20200322831A1; AU2017425816B2; EP3664535A4; KR20220147696A; KR102457284B1; US20220201539A1; JP2020529172A; KR20200033332A; CA3071469A1; AU2021266272A1; CN110741701A; CN110741701B; CN114698143A

Abstract

Provided are a method for acquiring a data radio bearer identifier and a base station. The method for acquiring a data radio bearer identifier comprises: a first base station sending a first message to a second base station, wherein the first message is used for requesting that a data radio bearer (DRB) is added; the first base station receiving a second message sent by a second base station, wherein the second message is used for indicating an identifier of at least one DRB; and the first base station sending first information to a user equipment, wherein the first information comprises DRB configuration information, and the DRB configuration information comprises the identifier of the at least one DRB. By means of the embodiments of the present application, the first base station can add a DRB according to a radio resource management policy and a network condition of its own so as to reconfigure a mapping relationship between a QoS flow and the DRB, such that the setting of a DRB is more flexible and effective.

Description

Method for acquiring data radio bearer identifier and base station

Technical field

The embodiments of the present invention relate to communication technologies, and in particular, to a method and a base station for acquiring a data radio bearer identifier.

Background technique

The core network may establish one or more Packet Data Unit (PDU) sessions for User Equipment (UE). Each PDU session contains one or more Quality of Service flows (QoS flows). The radio access network may establish one or more Data Radio Bearers (DRBs) for each PDU session. In order to ensure the service quality of data packets of different quality of service flows, the radio access network may map data packets of different quality of service flows belonging to the same PDU session to different DRBs, and may also provide different quality of service for the same PDU session. The packets of the stream are mapped to the same DRB. Specifically, the mapping of data packets to DRB is divided into two steps. The first step is the mapping of IP flow to QoS flow by the Non Access Stratum (NAS). The second step is the mapping of QoS flow to DRB done by the Access Stratum (AS). The mapping of QoS flow to DRB is determined by the base station of the radio access network. The mapping relationship between QoS flow and DRB can be a many-to-one relationship or a one-to-one relationship.

In order to improve the throughput of the data transmission of the UE and reduce the signaling overhead of the core network due to the mobility of the UE, the concept of dual connectivity is introduced in the LTE system, that is, the UE can send and receive data through two base stations. Among the two base stations, the base station that provides the UE with the control plane connection to the core network is called the master base station (Master eNB), and the other base station that provides the UE with additional radio resources is called the secondary base station (Secondary eNB). In the 5G system, Dual connectivity technology will still be used.

In the dual-connection architecture of the 5G core network connection, the master node (MN) determines to transfer part of the QoS flow of the UE to the secondary node (Scecondary Node, SN), and the SN determines the mapping of the part of the QoS flow to the DRB, where The MN may be a MegaNB (Master gNB) or an MeNB (Master eNB), and the SN may be a SgNB (Secondary gNB) or a SeNB (Secondary eNB). The SN may increase or decrease the DRB compared to the number of DRBs used by the MN to determine the mapping of QoS flow to DRB. Regardless of how the SN determines the mapping relationship between the QoS and the DRB, the ID of the DRB configured to the UE needs to be guaranteed to be unique, that is, the case where more than one DRB cannot share the same ID. Therefore, one problem that needs to be solved is how to manage the ID of the DRB.

Summary of the invention

An embodiment of the present application provides a method for acquiring a data radio bearer identifier and a base station, which can ensure the uniqueness of the ID of the DRB, so that the first base station can increase the DRB according to its own radio resource management policy and network status, and reconfigure the QoS flow and the DRB. The mapping relationship between the DRB makes the setting of the DRB more flexible and effective.

In a first aspect, an embodiment of the present application provides a method for acquiring a data radio bearer identifier, including: a first base The station sends a first message to the second base station, where the first message is used to request to increase the data radio bearer DRB; the first base station receives the second message sent by the second base station, where the second message is used to indicate at least An identifier of a DRB; the first base station sends first information to the user equipment, the first information includes DRB configuration information, and the DRB configuration information includes an identifier of the at least one DRB.

With reference to the first aspect, in a possible implementation manner of the first aspect, the first information further includes information about a mapping relationship between the uplink quality of service QoS flow and the at least one DRB.

In conjunction with the first aspect, or a possible implementation manner of the first aspect, in another possible implementation manner of the first aspect, the first base station is a secondary base station, and the second base station is a primary base station.

In conjunction with the first aspect or any one of the possible implementation manners of the first aspect, in another possible implementation manner of the first aspect, the first message includes any one or more of the following information: request to increase Information indicating the DRB; requesting to increase the number of DRBs; mapping to the QoS flow requesting the increased DRB; mapping to the QoS flow requesting the added DRB; mapping to the index of the packet requesting the increased DRB's QoS flow.

In conjunction with the first aspect or any one of the possible implementations of the first aspect, in another possible implementation of the first aspect, the second message includes any one or more of the following information: available The identifier of the DRB; the identifier of the at least one DRB; the identifier of the QoS flow that is allowed to be mapped to the at least one DRB; the identifier of the QoS flow that is rejected to the at least one DRB; the mapping relationship configuration information of the DRB and the QoS flow; the grouping of the DRB and the QoS flow The mapping relationship configuration information; the mapping relationship configuration information of the index of the packet of the DRB and the QoS flow.

In conjunction with the first aspect or any one of the possible implementation manners of the first aspect, in another possible implementation manner of the first aspect, before the first base station sends the first message to the second base station, the method further The first base station receives a third message sent by the second base station, where the third message is used to request to transfer at least one QoS flow to the first base station, or is used to request the first base station to add at least a QoS flow, or for requesting to transfer at least one DRB to the first base station, or for requesting the first base station to add at least one DRB;

The third message includes any one or more of the following information: an identifier of at least one QoS flow transferred to the first base station and a QoS parameter of the at least one QoS flow; the at least one QoS flow and the DRB Mapping relationship; indication information of the transfer type; wherein the transfer type includes at least one of QoS flow transfer and DRB transfer.

With reference to the first aspect, or any one of the possible implementation manners of the first aspect, in a first possible implementation manner of the first aspect, the first base station sends the first information to the user equipment, including: the first The base station sends a radio resource control reconfiguration message to the user equipment, where the radio resource control reconfiguration message includes the first information.

In conjunction with the first aspect, or any one of the possible implementation manners of the first aspect, in another possible implementation manner of the first aspect, the method further includes: sending, by the first base station, the second base station And a fourth message, where the fourth message includes any one or more of the following information: an identifier of an available DRB; an identifier of the DRB selected by the first base station; a QoS flow configured by the first base station, and a DRB Mapping relations.

With reference to the first aspect, or any one of the possible implementation manners of the first aspect, in a first possible implementation manner of the first aspect, the first base station sends the first information to the user equipment, including: the first The base station sends a fifth message to the second base station, where the fifth message includes the first information, the fifth message is used by the second base station to acquire the first information, and the first information is It is carried in a radio resource control reconfiguration message sent to the user equipment.

In conjunction with the first aspect or any one of the possible implementation manners of the first aspect, in another possible implementation manner of the first aspect, the first information is specifically configured in a radio resource control information container of the fifth message. in.

In a second aspect, the embodiment of the present application provides a method for acquiring a data radio bearer identifier, including: receiving, by a second base station, a first message sent by a first base station, where the first message is used to request to increase a data radio bearer DRB; The second base station sends a second message to the first base station, where the second message is used to indicate an identifier of the at least one DRB.

With reference to the second aspect, in a possible implementation manner of the second aspect, the first base station is a secondary base station, and the second base station is a primary base station.

In conjunction with the second aspect, or a possible implementation manner of the second aspect, in another possible implementation manner of the second aspect, before the second base station receives the first message sent by the first base station, The method further includes: the second base station transmitting a third message to the first base station, the third message being used to request to transfer at least one QoS flow to the first base station, or for requesting the first base station to increase At least one QoS flow, or for requesting to transfer at least one DRB to the first base station, or for requesting the first base station to add at least one DRB;

The third message includes any one or more of the following information: an identifier of at least one QoS flow transferred to the first base station and a QoS parameter of the at least one QoS flow; the at least one QoS flow and the DRB Mapping relationship; indication of the type of transfer. The transfer type includes at least one of a QoS flow transfer and a DRB transfer.

In conjunction with the second aspect, or any one of the possible implementation manners of the second aspect, the method further includes: the second base station receiving the sending by the first base station a fourth message, the fourth message includes any one or more of the following information: an identifier of an available DRB; an identifier of the DRB selected by the first base station; a QoS flow configured by the first base station, and a DRB Mapping relations.

In conjunction with the second aspect, or any one of the possible implementation manners of the second aspect, the method further includes: the second base station receiving, sending, by the first base station, a fifth message; the second base station acquires the first information from the fifth message; the second base station sends a radio resource control reconfiguration message to the user equipment, where the radio resource control reconfiguration message The first information is included.

With reference to the second aspect, or any one of the possible implementation manners of the second aspect, in a second possible implementation manner of the second aspect, the second base station acquires the first information from the fifth message, The method includes: the second base station acquiring the first information from a radio resource control information container of the fifth message.

In a third aspect, the embodiment of the present application provides a method for acquiring a data radio bearer identifier, where the first base station sends a first message to a second base station, where the first message is used to indicate an identifier of a currently available DRB; The first base station sends the first information to the user equipment, where the first information includes at least one of the configuration information of the added DRB and the identifier of the released DRB, and the configuration information of the added DRB includes the identifier of the added DRB.

With reference to the third aspect, in a possible implementation manner of the third aspect, the first base station sends the first message after the DRB identifier update generates the identifier of the currently available DRB, where the DRB identifier is updated. Reasons include at least one of increasing DRB and releasing DRB.

In conjunction with the third aspect or a possible implementation manner of the third aspect, in another possible implementation manner of the third aspect, the first information further includes mapping relationship information between the uplink QoS flow and the DRB.

With the third aspect or any one of the possible implementation manners of the third aspect, in another possible implementation manner of the third aspect, the first base station is a secondary base station, and the second base station is a primary base station; or The first base The station is a primary base station, and the second base station is a secondary base station.

In conjunction with the third aspect or any one of the possible implementation manners of the third aspect, in another possible implementation manner of the third aspect, the first message includes any one or more of the following information: currently available The identifier of the DRB; the identifier of the DRB occupied by the first base station; the identifier of the DRB released by the first base station; and the mapping relationship between the QoS flow and the DRB configured by the first base station.

With the third aspect or any one of the possible implementation manners of the third aspect, in another possible implementation manner of the third aspect, before the first base station sends the first message to the second base station, the method further The first base station receives a second message sent by the second base station, where the second message is used to indicate an identifier of an available DRB, and the first base station performs a DRB identifier update on the identifier of the available DRB, and generates The identifier of the currently available DRB.

In conjunction with the third aspect or any one of the possible implementation manners of the third aspect, in another possible implementation manner of the third aspect, the second message includes any one or more of the following information: available The identifier of the DRB; the identifier of the DRB occupied by the second base station; the identifier of the DRB released by the second base station; and the mapping relationship between the QoS flow and the DRB configured by the second base station.

With the third aspect or any one of the possible implementation manners of the third aspect, in another possible implementation manner of the third aspect, the method further includes: receiving, by the first base station, the second base station a third message, the third message is used to request to transfer at least one QoS flow to the first base station, or to request the first base station to add at least one QoS flow, or to request to transfer at least one DRB to the The first base station, or used to request the first base station to add at least one DRB;

The third message includes any one or more of the following information: an identifier of at least one QoS flow transferred to the first base station and a QoS parameter of the at least one QoS flow; the at least one QoS flow and the DRB Mapping relationship; indication of the type of transfer; identification of the available DRB. Wherein the transfer type includes at least one of QoS flow transfer and DRB transfer

With the third aspect or any one of the possible implementation manners of the third aspect, in another possible implementation manner of the third aspect, the first base station sends the first information to the user equipment, including:

The first base station sends a radio resource control reconfiguration message to the user equipment, where the radio resource control reconfiguration message includes the first information.

With the third aspect, or any one of the possible implementation manners of the third aspect, in another possible implementation manner of the third aspect, the first base station sends the first information to the user equipment, including: the first The base station sends a fourth message to the second base station, where the fourth message includes the first information, the fourth message is used by the second base station to acquire the first information, and the first information is It is carried in a radio resource control reconfiguration message sent to the user equipment.

In conjunction with the third aspect, or any one of the possible implementation manners of the third aspect, in another possible implementation manner of the third aspect, the fourth message further includes a second information, where the second information is used to indicate The reason for transmitting the fourth message is to change the mapping relationship between the QoS flow and the DRB.

In a fourth aspect, the embodiment of the present application provides a first base station, where the first base station has a function of implementing behavior of the first base station in the foregoing method embodiment. This function can be implemented in hardware or in hardware by executing the corresponding software. The hardware or software includes one or more modules corresponding to the functions described above.

In a fifth aspect, an embodiment of the present application provides a first base station, including: a processor, a memory, a bus, and a a memory interface for storing a computer to execute an instruction, the processor is connected to the memory through the bus, and when the first base station is in operation, the processor executes the computer-executed instruction stored in the memory, so that the first base station The method for acquiring a data radio bearer identifier according to any one of the preceding aspects, or the method for obtaining a data radio bearer identifier according to any one of the foregoing third aspects.

In a sixth aspect, the embodiment of the present application provides a computer readable storage medium, configured to store computer software instructions used by the first base station, and when executed on a computer, enable the computer to perform any of the foregoing first aspects. A method for acquiring a data radio bearer identifier, or a method for obtaining a data radio bearer identifier according to any one of the above third aspects.

In a seventh aspect, the embodiment of the present application provides a computer program product, including instructions, when the computer is running on a computer, so that the computer can perform the method for acquiring the data radio bearer identifier of any one of the foregoing first aspects, or The method for obtaining a data radio bearer identifier according to any one of the third aspect.

In an eighth aspect, the embodiment of the present application provides a second base station, where the second base station has a function of implementing behavior of the second base station in the foregoing method embodiment. This function can be implemented in hardware or in hardware by executing the corresponding software. The hardware or software includes one or more modules corresponding to the functions described above.

In a ninth aspect, the embodiment of the present application provides a second base station, including: a processor, a memory, a bus, and a communication interface; the memory is configured to store a computer execution instruction, and the processor is connected to the memory through the bus, when the When the two base stations are in operation, the processor executes the computer-executed instructions stored in the memory to cause the access and mobility management function component to perform the method for acquiring the data radio bearer identifier according to any one of the above second aspects.

In a tenth aspect, the embodiment of the present application provides a computer readable storage medium, configured to store computer software instructions used by the second base station, when executed on a computer, to enable the computer to perform any of the foregoing second aspects. A method for obtaining a data radio bearer identifier.

In an eleventh aspect, the embodiment of the present application provides a computer program product comprising instructions, when executed on a computer, to enable a computer to perform the method for acquiring a data radio bearer identifier according to any one of the foregoing second aspects.

According to a twelfth aspect, the embodiment of the present application provides a communication system, including the first base station according to the fourth aspect and the second base station according to the eighth aspect.

The method for acquiring the data radio bearer identifier and the base station in the embodiment of the present application, the first base station sends a first message to the second base station to request to increase the DRB, and the second base station feeds back the second message to the first base station, where the first base station according to the first The second message can obtain the identifier of the DRB that can be used by the first base station, and the first base station adds the DRB by using the identifier of the DRB, and the first base station sends the identifier of the added DRB to the user equipment, thereby ensuring the uniqueness of the ID of the DRB, and implementing the first The base station can increase the DRB according to its own radio resource management policy and network status, and reconfigure the mapping relationship between the QoS flow and the DRB, so that the DRB setting is more flexible and effective.

DRAWINGS

1 is a schematic diagram of a QoS architecture of the present application;

2A is a schematic diagram of a control plane of a dual connectivity architecture of the present application;

2B is a schematic diagram of a dual-connection architecture user plane of the present application;

3 is a flowchart of a method for acquiring a DRB identifier according to the present application;

4A is a schematic diagram of QoS flow transfer in a dual connectivity architecture;

4B is a schematic diagram of DRB transfer in a dual connectivity architecture;

FIG. 5 is a flowchart of another method for acquiring a DRB identifier according to the present application;

6 is a flowchart of still another method for acquiring a DRB identifier according to the present application;

FIG. 7 is a flowchart of still another method for acquiring a DRB identifier according to the present application;

8 is a flowchart of another method for acquiring a DRB identifier according to the present application;

9 is a flowchart of another method for acquiring a DRB identifier according to the present application;

10 is a flowchart of another method for acquiring a DRB identifier according to the present application;

11 is a flowchart of another method for acquiring a DRB identifier according to the present application;

12 is a flowchart of another method for acquiring a DRB identifier according to the present application;

13 is a flowchart of another method for acquiring a DRB identifier according to the present application;

14 is a flowchart of another method for acquiring a DRB identifier according to the present application;

15 is a flowchart of another method for acquiring a DRB identifier according to the present application;

16 is a flowchart of another method for acquiring a DRB identifier according to the present application;

17 is a schematic structural diagram of a first base station according to the present application;

FIG. 18 is a schematic structural diagram of a second base station according to the present application.

Detailed ways

The technical solutions in the embodiments of the present application are clearly and completely described in the following with reference to the accompanying drawings in the embodiments of the present application.

1 is a schematic diagram of a QoS architecture of the present application. As shown in FIG. 1, a User Plane Function (UPF) of a 5G core network (5G Core network) establishes one or more PDU sessions for a UE. For each PDU session of each UE, a base station (gNB) of a 5G access network (NG-RAN) establishes one or more DRBs, and the NG-RAN maps data packets belonging to different PDU sessions to different DRBs, specifically The 5GC and NR-RAN map the data packets of the PDU session to the appropriate QoS flow and DRB to ensure the service quality of the data packet. The mapping from QoS flow to DRB is determined by the base station. As shown in Figure 1, the mapping between QoS flow and DRB can be one-to-one or multiple-to-one. As shown in Figure 1, DRB1 carries QoS flow1 and QoS. Flow2, DRB2 carries QoS flow3.

2A is a schematic diagram of a dual-connection architecture control plane of the present application, and FIG. 2B is a schematic diagram of a dual-connection architecture user plane according to the present application. As shown in FIG. 2A and FIG. 2B, the UE can send and receive data through the MN and the SN. The control plane: the Access and Mobility Management Function (AMF) is connected to the MN, and the MN is connected to the SN, and the MN provides the UE with a control plane connection to the core network, where NG-C It is the control plane interface between AMF and MN, and Xn-C is the control plane interface between MN and SN. User plane: The UPF is connected to the MN and the SN respectively. The MN is connected to the SN. The MN and the SN jointly provide the UE with a user plane connection to the core network. The SN can provide additional radio resources for the UE. The NG-U is the UPF and the MN. The user plane interface between the UPF and the SN, and the Xn-U is the user plane interface between the MN and the SN. In the dual-connection architecture, the MN may transfer the QoS flow of the UE that is transmitted by itself or the DRB of the UE that is transmitted by itself to the SN, and the MN may perform the transmission by using the SN. The method for obtaining the DRB identifier in the embodiment of the present application can ensure the dual connectivity architecture. The uniqueness of the identifier of the DRB is implemented by the SN to determine the mapping relationship between the QoS flow and the DRB. That is, the SN can increase or release the DRB according to its own radio resource management policy and network status. The mapping between the QoS flow and the DRB is configured to make the setting of the DRB in the dual-connection architecture more flexible and effective.

FIG. 1 , FIG. 2A and FIG. 2B are both illustrated by using a 5G network as an example. It should be noted that the method for obtaining the DRB identifier in the embodiment of the present application is also applicable to the LTE network. The MN and the SN in the embodiment of the present application may be an eNB or a base station of the NG-RAN, that is, a gNB.

The UE involved in the present application may include a handheld device having a wireless communication function, an in-vehicle device, a wearable device, a computing device, or other processing device connected to the wireless modem, and various forms of User Equipment (UE). Mobile station (MS), terminal, terminal equipment, etc. For convenience of description, in the present application, it is simply referred to as a user equipment or a UE.

The DRB of the first base station of the present application, that is, the DRB of the SN may be an SCG DRB or an SCG split DRB.

For specific implementation manners of the method for obtaining the DRB identifier in the embodiment of the present application, refer to the explanation of the following embodiments.

FIG. 3 is a flowchart of a method for acquiring a DRB identifier according to the present application. As shown in FIG. 3, the embodiment includes a user equipment, a first base station, and a second base station. The method in this embodiment may include:

Step 101: The first base station sends a first message to the second base station, where the second base station receives the first message sent by the first base station, where the first message is used to request to increase the DRB.

When the first base station determines that the DRB needs to be added, the first message may be sent to the second base station to request to increase the DRB. The second base station receives the first message, and learns that the first base station needs to increase the DRB.

Step 102: The second base station sends a second message to the first base station, where the first base station receives the second message sent by the second base station, where the second message is used to indicate the identifier of the at least one DRB.

After the second base station learns that the first base station needs to increase the DRB, it may send a second message to the first base station according to the usage of the DRB identifier, where the second message is used to indicate the identifier of one or more DRBs, the one or more The identifier of the DRB is the identifier of the DRB allocated by the second base station to the first base station, that is, the identifier of the DRB that the second base station allows the first base station to use. The first base station can learn, according to the second message, the number of DRBs that the second base station allows the first base station to increase and the identifier of the corresponding DRB, and further complete the remapping between the DRB and the QoS flow and the DRB.

Step 103: The first base station sends the first information to the user equipment, where the user equipment receives the first information sent by the first base station, where the first information includes DRB configuration information, where the DRB configuration information includes an identifier of the at least one DRB.

After the step 101 and the step 102 are completed, the first base station may send the DRB configuration information to the user equipment, where the DRB configuration information may include an identifier of one or more DRBs. That is, the DRB configuration information may include an identifier of the DRB added by the SN. It can be understood that the DRB configuration information may also include configuration information of the PDCP, the RLC, and the logical channel corresponding to the DRB, which are not described herein.

Optionally, the first information may further include information about a mapping relationship between the uplink QoS flow and the at least one DRB. Specifically, in the downlink transmission scenario, the user equipment may not obtain the mapping relationship between the downlink QoS flow and the DRB, and the user equipment may obtain the identifier of the DRB added by the first base station and the corresponding PDCP, RLC, and logical channel configuration information. In the uplink transmission scenario, the user equipment needs to obtain the information about the mapping relationship between the uplink QoS flow and the DRB in addition to the identifier of the DRB added by the first base station, so the first letter is The information may further include information of a mapping relationship between the uplink QoS flow and the at least one DRB, and the mapping relationship between the uplink QoS flow and the at least one DRB may specifically be a mapping relationship between the identifier of the DRB and the identifier of the QoS flow. It can be understood that, in an implementation manner, the information about the mapping relationship between the uplink QoS flow and the at least one DRB may specifically be a mapping relationship between the DRB and the uplink QoS flow added by the first base station, and another implementation manner, The information of the mapping relationship between the uplink QoS flow and the at least one DRB may specifically be a mapping relationship between all DRBs of the first base station and the uplink QoS flow.

The first base station involved in the embodiment of the present application may be a secondary base station, that is, the SN shown in FIG. 2A and FIG. 2B, and the second base station may be the primary base station, that is, the MN shown in FIG. 2A and FIG. 2B.

There are many different ways to implement the specific form of the first message and the specific information carried.

In an implementation manner, the first message may be a new type of message, and the second base station receives the first message, so that the first base station requests to increase the DRB.

In another implementation manner, the first message may include any one or more of the following information: (1) requesting to increase the indication information of the DRB; (2) requesting to increase the number of DRBs; (3) remapping QoS The identity of the stream; (4) the packet information of the remapping QoS flow; and (5) the index of the packet of the remapping QoS flow.

The above information of the first message is specifically explained below.

In an implementation manner, the first message may include (1) an indication requesting to increase the DRB. The second base station determines, according to the request to increase the indication information of the DRB, that the first base station requests to increase the DRB, and feeds back the identifier of all currently available DRBs to the first base station.

In another implementation manner, the first message may include (2) requesting to increase the number of DRBs. The second base station determines that the first base station requests to increase the DRB according to the request to increase the number of DRBs, and feeds back the identifier of the at least one DRB to the first base station. It should be noted that the number of identifiers of the at least one DRB may be equal to the number of DRBs that are requested to be increased.

In another implementation, the first message may include (3) an identifier of the remapped QoS flow. The remapping QoS flow is a QoS flow that is mapped to the DRB that the SN needs to increase. The second base station determines, according to the identifier of the remapped QoS flow, that the first base station requests to increase the DRB, and feeds back the identifier of the at least one DRB to the first base station. It should be noted that the second base station may further feed back, to the first base station, an identifier of the QoS flow that allows or denies the remapping, or feedback configuration information of the mapping relationship between the DRB and the QoS flow, according to the identifier of the remapping QoS flow.

In another implementation, the first message may include (4) packet information of the remapped QoS flow. The remapping QoS flow is a QoS flow that is mapped to the DRB that the SN needs to increase. The second base station determines, according to the group information of the remapped QoS flow, that the first base station requests to increase the DRB, and feeds back the identifier of the at least one DRB to the first base station. It should be noted that the second base station may further feed back the mapping relationship configuration information of the group of the DRB and the QoS flow to the first base station according to the group information of the remapped QoS flow. The packet of the QoS flow specifically includes one or more QoS flows. The QoS flows within each packet can be mapped to the same newly added DRB. It can be understood that the number of packets may implicitly indicate the number of DRBs that the first base station requests to increase.

Yet another achievable manner, the first message may comprise (5) an index of a packet of the remapped QoS flow. The remapping QoS flow is a QoS flow that is mapped to the DRB that the SN needs to increase. The second base station determines, according to the index of the packet of the remapped QoS flow, that the first base station requests to increase the DRB, and feeds back the identifier of the at least one DRB to the first base station. It should be noted that the second base station may also be grouped according to the remapping QoS flow. The index feeds back mapping relationship configuration information of the index of the packet of the DRB and the QoS flow to the first base station. The index of the packet of the QoS flow specifically refers to an identifier used to indicate a packet including one or more QoS flows.

Yet another achievable manner, the first message may include (1) and (2);

Yet another achievable manner, the first message may include (1) and (3);

Yet another achievable manner, the first message may include (1) and (4);

Yet another achievable manner, the first message may include (1) and (5);

Yet another achievable manner, the first message may include (1), (2), and (3);

Yet another achievable manner, the first message may include (4) and (5);

Yet another achievable manner, the first message may include (1), (4), and (5);

The second base station receives the first message, and according to the foregoing information carried in the first message, learns that the first base station requests to increase the DRB.

After learning that the first base station requests to increase the DRB, the second base station may feed back a second message to the first base station to indicate the identifier of the at least one DRB of the first base station.

The specific form of the second message and the specific information carried there are also many different achievable ways.

The second message may specifically include any one or more of the following information: (1) an identifier of an available DRB; (2) an identifier of at least one DRB; and (3) an identifier of a QoS flow that is allowed to be mapped to at least one DRB. (4) Rejecting the identity of the QoS flow mapped to at least one DRB; (5) Mapping relationship configuration information of the DRB and the QoS flow; (6) Mapping relationship configuration information of the DRB and QoS flow packets; (7) DRB and QoS The mapping relationship configuration information of the index of the streamed packet.

The first base station can learn, according to the second message, the number of DRBs that the second base station allows the first base station to increase and the identifier of the corresponding DRB.

Optionally, the first base station may further determine, according to the foregoing (3) the identifier of the QoS flow that is allowed to be mapped to the at least one DRB, the QoS flow that the second base station allows to be mapped to the increased DRB. It should be noted that, when the second base station allows the first base station to request all the mapped QoS flows to be mapped to the added DRB, the second message may display an indication that all the QoS flows including the request mapping may be remapped. The second message may also implicitly indicate that all QoS flows of the request mapping may be remapped by not including any QoS flow information. Further, the first base station may determine that the second base station allows all QoS flows that are requested to be remapped to be mapped to Increased DRB.

The first base station may further determine, according to (4) rejecting the identifier of the QoS flow mapped to the at least one DRB, that the second base station rejects the QoS flow mapped to the increased DRB.

The first base station may further determine a mapping relationship between the DRB and the QoS flow according to the mapping relationship configuration information of the (5) DRB and the QoS flow. The mapping relationship configuration information of the (5) DRB and the QoS flow may be specifically a mapping relationship between the identifier of the DRB and the identifier of the QoS flow.

The first base station may further determine a mapping relationship between the DRB and the QoS flow packet according to the mapping relationship configuration information of the (6) DRB and the QoS flow packet. It should be noted that, when the second message includes the mapping relationship configuration information of the (6) DRB and the QoS flow packet, the second message may further include an identifier of the QoS flow of each packet, where the identifier of the QoS flow is used to indicate It is allowed to map to the QoS flow on the added DRB in the packet. It can be understood that for a certain packet not including the identifier of the QoS flow, implicitly indicating that all QoS flows in the packet can be mapped to the increased DRB. .

The first base station may also configure information according to the mapping relationship between the (7) DRB and the index of the packet of the QoS flow. A mapping relationship of indexes of packets of the DRB and the QoS flow is determined. The second message may further include an identifier of the QoS flow of the packet that can be remapped to the QoS flow on the increased DRB, including the above (7). It can be understood that the packet of one QoS flow in the second message is not Including the identifier of the QoS flow, all QoS flows in the packet indicating the QoS flow can be implicitly remapped.

The foregoing first message and the second message may be flexibly set according to requirements to manage the DRB identifier in the dual-connection architecture, so that the SN flexibly sets the mapping relationship between the DRB and the QoS flow in the dual-connection architecture.

Optionally, before the foregoing step 101, the method of the embodiment of the present application may further include: the first base station receives the third message sent by the second base station, and the second base station sends a third message to the first base station, where the third message is used. Requesting to transfer at least one QoS flow to the first base station, or for requesting the first base station to add at least one QoS flow, or for requesting transfer of at least one DRB to the first base station, or for requesting the A base station adds at least one DRB.

Specifically, the third message may include any one or more of the following information: an identifier of the at least one QoS flow that is transferred to the first base station, and a QoS parameter of the at least one QoS flow; the at least one QoS The mapping relationship between the flow and the DRB; the indication information of the transfer type.

The transfer type may include at least one of QoS flow transfer and DRB transfer.

The QoS flow transfer refers to the transfer of the QoS flow in the granularity of the QoS flow, that is, the transferred QoS flow is a partial QoS flow in the at least one DRB configured by the second base station, instead of all in the at least one DRB. QoS flow. For example, FIG. 4A is a schematic diagram of QoS flow transfer in a dual connectivity architecture, wherein the left side of FIG. 4A is a schematic diagram before the transition, and the left side of FIG. 4A is the intention after the transition, as shown in the right side of FIG. 4A. As shown, before the transfer, the DRB1 of the second base station transmits QoS flow 1, the QoS flow 1 belongs to the PDU session 1, the DRB2 of the second base station transmits the QoS flow 2, and the DRB3 of the second base station transmits the QoS flow 3 (3 in the figure) and QoS flow 4, QoS flow 2, QoS flow 3 and QoS flow 4 belong to PDU session 2, and the second base station can transfer QoS flow 4 to the first base station for transmission, as shown on the right side of FIG. 4A, after the transfer, PDU The QoS flow 4 of session 2 is transmitted by the DRB of the first base station, and the identity of the DRB of the DRB of the first base station uses the identity of the DRB allocated by the second base station.

The DRB transfer refers to the transfer of the QoS flow with the DRB as the granularity, that is, the transferred QoS flow is all the QoS flows in the at least one DRB configured by the second base station. For example, FIG. 4B is a schematic diagram of DRB transfer in a dual connectivity architecture, wherein the left side of FIG. 4B is a schematic diagram before the transition, and the right side of FIG. 4B is the intention after the transition, as shown in the schematic diagram on the left side of FIG. 4B. It is shown that before the transfer, the DRB1 of the second base station transmits the QoS flow 1, the QoS flow 1 belongs to the PDU session 1, the DRB2 of the second base station transmits the QoS flow 2, and the DRB3 of the second base station transmits the QoS flow 3 (3 in the figure) and the QoS Stream 4, QoS Flow 2, QoS Flow 3, and QoS Flow 4 belong to PDU Session 2, and the second base station can transfer DRB3 to the first base station for transmission, as shown on the right side of FIG. 4B, after the transfer, PDU Session 2 The QoS flow 3 and the QoS flow 4 are transmitted by the DRB of the first base station, and the ID of the DRB of the DRB of the first base station uses the identifier of the DRB allocated by the second base station, for example, the identifier of the DRB 3 before the transfer can be used.

4A and 4B are further exemplified. If the second base station transfers the PDU session 2 to the first base station process transmission, the transfer involves both QoS flow transfer and DRB transfer.

After the first base station accepts the foregoing transfer of the second base station, if it is determined that the DRB needs to be added to perform reconfiguration of the mapping of the QoS flow and the DRB, the subsequent steps 101 to 103 may be performed.

The indication information of the mapping relationship and the transfer type of the at least one QoS flow and the DRB is included in a radio resource control information container (RRC Container), and the radio resource control information container (RRC Container) Included in the third message.

Optionally, an implementation manner of the foregoing step 103 is that the first base station sends a radio resource control (RRC) reconfiguration message to the user equipment, and the user equipment receives the radio resource control reconfiguration message sent by the first base station. The radio resource control reconfiguration message may include the first information.

On the basis of the implementation of the foregoing step 103, the method for acquiring the identifier of the DRB in the embodiment of the present application may further include: the first base station sends a fourth message to the second base station, and the second base station receives the fourth message sent by the first base station. a message, the fourth message includes any one or more of the following information: (1) an identifier of an available DRB; (2) an identifier of the DRB selected by the first base station; and (3) a QoS flow configured by the first base station Mapping relationship with DRB.

It should be noted that the identifier of the available DRB in the fourth message is different from the identifier of the available DRB in the second message. Specifically, the identifier of the available DRB in the second message is that the second base station receives the first After the first message sent by the base station, the identifier of the currently available DRB is fed back, and the identifier of the available DRB in the fourth message is that the first base station selects the DRB used by the increased DRB in the identifier of the available DRB of the first message. After the identification, the ID of the DRB obtained after updating the ID of the available DRB of the first message is updated.

Optionally, another implementation manner of the foregoing step 103 is that the first base station sends a fifth message to the second base station, and the second base station receives the fifth message sent by the first base station, where the fifth message may include the first message. The fifth message is used by the second base station to acquire the first information, and the first information is carried in a radio resource control reconfiguration message sent to the user equipment.

The first information may be specifically included in a radio resource control information container (RRC Container), where the radio resource control information container is included in the fifth message.

It should be noted that, the foregoing second base station sends a second message to the first base station, to indicate that the first base station is allowed to increase the DRB, and when the second base station does not allow the first base station to increase the DRB, the second base station may send the first base station to the first base station. The reject message is rejected to indicate that the first base station has increased the DRB request.

In this embodiment, the first base station sends a first message to the second base station to request to increase the DRB, and the second base station feeds back a second message to the first base station, where the first base station can obtain the first base station can use according to the second message. The identifier of the DRB, the first base station adds the DRB by using the identifier of the DRB, and the first base station sends the identifier of the added DRB to the user equipment, thereby ensuring the uniqueness of the ID of the DRB, so that the first base station can be based on its own radio resource management policy and The network status is increased by the DRB, and the mapping relationship between the QoS flow and the DRB is reconfigured to make the DRB setting more flexible and effective.

The technical solutions of the method embodiment shown in FIG. 3 are described in detail below by using several specific embodiments.

FIG. 5 is a flowchart of a method for acquiring another DRB identifier according to the present application. In this embodiment, the first base station is an SN, and the second base station is a MN. As shown in FIG. 5, the method in this embodiment may include:

Step 201: The MN sends an SN addition request message to the SN.

Specifically, when the MN determines that the SN is requested to transmit a partial QoS flow of the UE, step 201 may be performed. The SN addition request message may include an identifier of the QoS flow that the MN requests the SN to transmit and a corresponding QoS parameter. The SN addition request message may further include an RRC Container, where the RRC Container includes the mapping relationship configuration information of the identifier of the QoS flow that is transferred to the SN and the DRB identifier configured by the MN.

The SN addition request message may be a specific implementation manner of the third message in the embodiment shown in FIG.

Step 202: The SN sends an SN addition request acknowledgement message to the MN.

Specifically, when the SN accepts the foregoing SN increase request message of the MN, step 202 may be performed. After receiving the SN addition request message sent by the MN, the SN is configured according to the mapping relationship between the QoS parameter, the QoS flow identifier, and the DRB identifier provided by the MN. In the SN addition request acknowledgement message, an identifier of the QoS flow that the SN agrees to accept may be included. In addition, in the SN addition request acknowledgement message, an RRC Container may also be included. The radio resource configuration information of the SN and the radio bearer configuration information are included in the RRC Container.

Step 203: The MN sends an RRC connection reconfiguration message to the UE.

The RRC connection reconfiguration message carries information in the RRC Container in the SN addition request acknowledgement message.

Step 204: The MN receives an RRC connection reconfiguration complete message sent by the UE.

Step 205: The MN sends an SN reconfiguration complete message to the SN.

Step 206: The SN initiates an SN modification process, and sends an SN modification requirement message to the MN.

The purpose of the SN initiating the SN modification procedure is to trigger the addition of the DRB. More specifically, the step is to request the MN to allocate the DRB ID. In this step, the SN modification request message may be a specific implementation manner of the first message in the embodiment shown in FIG. For a specific explanation of the step 206, reference may be made to the explanation of the step 101 of the embodiment shown in FIG. 3, and details are not described herein again. For the specific explanation of the first message, reference may also be made to the embodiment shown in FIG. Explain the explanation and will not repeat it here.

Step 207: The MN sends an SN modification confirmation message to the SN.

In this embodiment, the SN modification confirmation message may be a specific implementation manner of the second message in the embodiment shown in FIG. Specifically, the specific explanation of step 207 can be referred to the explanation of step 102 of the embodiment shown in FIG. 3, and details are not described herein again.

Step 208: The SN initiates an SN modification process, and the SN sends an SN modification requirement message to the MN.

The purpose of the SN initiating the SN modification process is to trigger an increase in the DRB. More specifically, this step is to configure the added DRB. In this step, the SN modification request message may be the fifth message in the embodiment shown in FIG. 3, and the specific explanation of the fifth message may be referred to the specific explanation of the embodiment shown in FIG. Narration. That is, the fifth message may include the first information. The first information may include configuration information of the added DRB and the like. Specifically, the fifth message may include an RRC Container, where the RRC Container carries the first information, that is, carries configuration information of the added DRB. The increased DRB configuration information may include an identifier of the DRB added by the SN. It can be understood that the added DRB configuration information may further include configuration information of the PDCP, the RLC, and the logical channel corresponding to the increased DRB.

Step 209: The MN sends an RRC connection reconfiguration message to the UE. The RRC Connection Reconfiguration message includes first information.

Specifically, the MN may take out the first information in the RRC Container in the SN modification request message received in step 208, and set the first information in the RRC connection reconfiguration message.

Step 210: The MN receives an RRC connection reconfiguration complete message sent by the UE.

Step 211: The MN sends an SN modification confirmation message to the SN.

In this embodiment, for the request message of the MN, the SN first accepts the request of the MN, and completes the configuration according to the configuration information in the increase request message, and then the SN sends a SN modification request message to initiate a DRB addition process, thereby ensuring the ID of the DRB. Uniquely, the SN can increase the DRB according to its own radio resource management policy and network status, and reconfigure the mapping relationship between QoS flow and DRB, so that the DRB is set. More flexible and effective.

FIG. 6 is a flowchart of a method for acquiring a DRB identifier according to another embodiment of the present application. The difference between the embodiment and the embodiment shown in FIG. 5 is that the SN directly sends an RRC connection reconfiguration message to the UE, as shown in FIG. The method of an embodiment may include:

Step 301: The MN sends an SN addition request message to the SN.

Step 302: The SN sends an SN addition request acknowledgement message to the MN.

For the specific explanation of the steps 301 and 302, reference may be made to the explanations of the steps 201 and 202 of the embodiment shown in FIG. 5, and details are not described herein again.

Step 303: The SN sends an RRC connection reconfiguration message to the UE.

The RRC connection reconfiguration message may carry the mapping relationship between the uplink QoS flow and the DRB and the related configuration information of the DRB, that is, the ID of the DRB, the PDCP, the RLC, and the configuration information of the logical channel of the DRB.

Step 304: The SN receives an RRC connection reconfiguration complete message sent by the UE.

Step 305: The SN sends an SN modification requirement message to the MN.

In this step, the SN modification request message may be a specific implementation manner of the first message in the embodiment shown in FIG.

Step 306: The MN sends an SN modification confirmation message to the SN.

In this step, the SN modification confirmation message may be a specific implementation of the second message in the embodiment shown in FIG.

For the specific explanation of the steps 305 and 306, reference may be made to the steps 206 and 207 of the embodiment shown in FIG. 5, and details are not described herein again.

Step 307: The SN sends an RRC connection reconfiguration message to the UE.

The RRC Connection Reconfiguration message includes first information.

For a detailed explanation of the first information, reference may be made to the explanation of the embodiment shown in FIG. 3, and details are not described herein again.

Step 308: The UE sends an RRC Connection Reconfiguration Complete message to the SN.

In this embodiment, for the request message of the MN, the SN first accepts the request of the MN, and completes the configuration according to the configuration information in the increase request message, and then the SN sends a SN modification request message to initiate a DRB addition process, thereby ensuring the ID of the DRB. Uniquely, the SN can increase the DRB according to its own radio resource management policy and network status, so as to reconfigure the mapping relationship between QoS flow and DRB, making the DRB setting more flexible and effective.

In the embodiment shown in FIG. 5 and FIG. 6, the SN always accepts the SN addition request message sent by the MN, and completes the configuration according to the configuration information in the SN addition request message, and then the SN initiates the DRB to the MN. The process of adding, that is, sending the first message, is different from the embodiment shown in FIG. 5 and FIG. 6. In the following two embodiments, for the SN increase request message sent by the MN, the SN may directly initiate the DRB increase process, that is, send the first message. For a detailed explanation of the message, reference may be made to the following embodiments.

FIG. 7 is a flowchart of a method for acquiring a DRB identifier according to another embodiment of the present application. As shown in FIG. 7, the method in this embodiment may include:

Step 401: The MN sends an SN addition request message to the SN.

For a detailed explanation of the step 401, reference may be made to the specific explanation of the step 301, and details are not described herein again.

Step 402: The SN initiates an SN modification process, and sends an SN modification requirement message to the MN.

After the SN receives the SN addition request message sent by the MN, if the SN needs to increase the DRB, the SN initiates the SN modification process, and sends the SN modification request message to the MN. The SN modification requirement message in this step may be as shown in FIG. A specific implementation manner of the first message of the embodiment, that is, the SN initiates the SN modification process for triggering the addition of the DRB. More specifically, the step is to request the MN to allocate the DRB ID. For a detailed explanation of the first message, reference may be made to the explanation of the embodiment shown in FIG. 3, and details are not described herein again. That is, the SN may determine that the DRB needs to be added according to the configuration information in the SN addition request message.

Step 403: The MN sends an SN modification confirmation message to the SN.

In this step, the SN modification confirmation message may be a specific implementation of the second message in the embodiment shown in FIG. For a detailed explanation of the second message, reference may be made to the explanation of the embodiment shown in FIG. 3, and details are not described herein again.

Step 404: The SN sends an SN addition request acknowledgement message to the MN.

For a detailed explanation of the step 404, reference may be made to the specific explanation of the step 202, and details are not described herein again. It should be noted that the SN addition request acknowledgement message in step 404 includes configuration information of the added DRB.

Step 405: The MN sends an RRC connection reconfiguration message to the UE.

Step 406: The MN receives an RRC connection reconfiguration complete message sent by the UE.

Step 407: The MN sends an SN reconfiguration complete message to the SN.

In this embodiment, for the MN increase request message, the SN determines that the DRB needs to be added according to the configuration information in the increase request message, and may initiate a DRB increase process by sending a SN modify request message, thereby ensuring the uniqueness of the DRB ID and implementing the SN. The DRB can be added according to its own radio resource management policy and network status to reconfigure the mapping between QoS flow and DRB, making the DRB setting more flexible and effective.

FIG. 8 is a flowchart of a method for acquiring a DRB identifier according to another embodiment of the present application. The difference between this embodiment and the embodiment shown in FIG. 7 is that the SN directly sends an RRC connection reconfiguration message to the UE, as shown in FIG. The method of the example may include:

Step 501: The MN sends an SN increase request message to the SN.

For a detailed explanation of the step 501, reference may be made to the specific explanation of the step 301, and details are not described herein again.

Step 502: The SN initiates an SN modification process, and the SN sends an SN modification requirement message to the MN.

The SN sends the SN modification process to the MN, and the SN modification request message in this step may be as shown in FIG. 3, after the SN receives the addition request message sent by the MN, if the SN needs to increase the DRB. A specific implementation manner of the first message of the embodiment, that is, the SN initiates the SN modification process for triggering the addition of the DRB. More specifically, the step is to request the MN to allocate the DRB ID. For a detailed explanation of the first message, reference may be made to the explanation of the embodiment shown in FIG. 3, and details are not described herein again.

Step 503: The MN sends an SN modification confirmation message to the SN.

Step 504: The SN sends an SN addition request acknowledgement message to the MN.

For a detailed explanation of the step 504, reference may be made to the specific explanation of the step 404, and details are not described herein again.

Step 505: The SN sends an RRC connection reconfiguration message to the UE.

Step 506: The SN receives an RRC connection reconfiguration complete message sent by the UE.

For the specific explanation of the steps 505 and 506, reference may be made to step 307 and step 308, and details are not described herein again.

FIG. 9 is a flowchart of a method for acquiring a DRB identifier according to another embodiment of the present application. The difference between this embodiment and the embodiment shown in FIG. 8 is that the MN sends the DRB ID of the added DRB to the SN through the SN modification request message, as shown in FIG. 9. As shown, the method of this embodiment may include:

Step 601: The MN sends an SN increase request message to the SN.

Step 602: The SN sends an SN addition request acknowledgement message to the MN.

Step 603: The MN sends an RRC connection reconfiguration message to the UE.

Step 604: The MN receives an RRC connection reconfiguration complete message sent by the UE.

Step 605: The MN sends an SN reconfiguration complete message to the SN.

Step 606: The SN initiates an SN modification process, and the SN sends an SN modification requirement message to the MN.

If the SN needs to increase the DRB, the SN initiates the SN modification process, and sends the SN modification request message to the MN. The SN modification request message in this step may be a specific implementation manner of the first message in the embodiment shown in FIG. The purpose of the SN initiating the SN modification procedure is to trigger the addition of the DRB. More specifically, the step is to request the MN to allocate the DRB ID.

Step 607: The MN sends an SN modification request message to the SN.

In this step, the SN modification request message may be a specific implementation of the second message in the embodiment shown in FIG. For a detailed explanation of the second message, reference may be made to the explanation of the embodiment shown in FIG. 3, and details are not described herein again. That is, the DRB ID of the added DRB is sent to the SN through the SN modification request message.

Step 608: The SN sends an SN modification request acknowledgement message to the MN.

In this step, the SN modification request acknowledgement message may be a specific implementation manner of the fifth message in the embodiment shown in FIG. For a detailed explanation of the second message, reference may be made to the explanation of the embodiment shown in FIG. 3, and details are not described herein again.

Step 609: The MN sends an RRC connection reconfiguration message to the UE. The RRC Connection Reconfiguration message includes first information.

Step 610: The MN receives an RRC connection reconfiguration complete message sent by the UE.

Step 611: The MN sends an SN modification confirmation message to the SN.

In this embodiment, for the request message of the MN, the SN first accepts the request of the MN, and completes the configuration according to the configuration information in the increase request message, and then the SN sends a SN modification request message to initiate a DRB addition process, thereby ensuring the ID of the DRB. Uniqueness, implementing SN can be based on its own wireless resource management strategy and network The DRB is added to the network to reconfigure the mapping between the QoS flow and the DRB, making the DRB setting more flexible and efficient.

FIG. 10 is a flowchart of a method for acquiring a DRB identifier according to another embodiment of the present application. As shown in FIG. 10, the method in this embodiment may include:

Step 701: The MN sends an SN addition request message to the SN.

Step 702: The SN sends an SN addition request acknowledgement message to the MN.

Step 703: The MN sends an RRC connection reconfiguration message to the UE.

Step 704: The MN receives an RRC connection reconfiguration complete message sent by the UE.

Step 705: The MN sends an SN reconfiguration complete message to the SN.

Step 706: The SN initiates an SN modification process, and the SN sends an SN modification requirement message to the MN.

If the SN needs to increase the DRB, the SN initiates the SN modification process and sends a first message to the MN, that is, the SN initiates the SN modification process for triggering the addition of the DRB. More specifically, the step is to request the MN to allocate the DRB ID. In this step, the SN modification request message may be a specific implementation manner of the first message in the embodiment shown in FIG.

Step 707: The MN sends an SN modification confirmation message to the SN.

For a specific explanation of the steps 701 to 708, reference may be made to the specific explanation of the steps 201 to 207 of the embodiment shown in FIG. 5, and details are not described herein again.

Step 708: The SN sends an RRC connection reconfiguration message to the UE. The RRC Connection Reconfiguration message includes first information.

Step 709: The SN receives an RRC connection reconfiguration complete message sent by the UE.

FIG. 11 is a flowchart of a method for acquiring a DRB identifier according to another embodiment of the present application. As shown in FIG. 11, the method in this embodiment may include:

Step 801: The MN sends an SN addition request message to the SN.

The increase request message includes a QoS flow ID of the QoS flow that the MN requests the SN to transmit and a corresponding QoS parameter. In addition, the RRC Container in the increase request message further includes a mapping relationship between the QoS flow ID and the DRB ID of the QoS flow transferred by the MN to the SN transmission.

Step 802: The SN sends an SN addition request acknowledgement message to the MN.

In this embodiment, after receiving the SN addition request message sent by the MN, the SN is configured according to the mapping relationship between the QoS flow ID and the DRB ID provided by the MN. In the increase request acknowledgement message, an RRC Container is included. The radio resource configuration of the SN and the radio bearer configuration are included in the RRC Container.

Step 803: The MN sends an RRC connection reconfiguration message to the UE.

The MN sends the information in the RRC Cotainer in the SN reply increase request acknowledgement message to the UE through the RRC connection reconfiguration message.

Step 804: The MN receives an RRC connection reconfiguration complete message sent by the UE.

Step 805: The MN sends an SN reconfiguration complete message to the SN.

Step 806: The SN initiates an SN modification process, and the SN sends an SN modification request message to the MN.

Step 807: The MN sends an SN modification confirmation message to the SN.

For the specific explanation of the steps 806 to 807, refer to step 706 and step 707, and details are not described herein again.

Step 808: The SN sends an RRC connection reconfiguration message to the UE.

After the SN receives the modification confirmation message sent by the MN, the SN determines the selected DRB ID. The SN sends an RRC connection reconfiguration message to the UE, where the RRC connection reconfiguration message includes configuration information of the updated mapping relationship between the QoS flow and the DRB transmitted by the SN.

Step 809: The SN receives an RRC connection reconfiguration complete message sent by the UE.

Step 810: The SN sends an SN configuration update message to the MN.

The SN configuration update message includes the remaining available DRB ID, or the DRB ID selected by the SN, or the mapping relationship between the updated QoS flow and the DRB.

In this embodiment, in the process of increasing the DRB, the uniqueness of the ID of the DRB can be ensured, and the SN can be configured to increase the DRB according to its own radio resource management policy and network status, so as to reconfigure the mapping relationship between the QoS flow and the DRB, so that the DRB The settings are more flexible and effective.

FIG. 12 is a flowchart of a method for acquiring a DRB identifier according to another embodiment of the present application. As shown in FIG. 12, the method in this embodiment may include:

Step 901: The MN sends an SN addition request message to the SN.

The increase request message includes a QoS flow ID of the QoS flow that the MN requests the SN to transmit and a corresponding QoS parameter. In addition, an available DRB ID is also included in the RRC Container in the increase request message.

Step 902: The SN sends an SN addition request acknowledgement message to the MN.

If the SN accepts the add request message, the SN determines the mapping relationship between the selected DRB ID and the QoS flow ID of the QoS flow that the MN requests to transmit through the SN according to the available DRB ID provided by the MN. The SN replies with a request acknowledgement message, which includes the remaining available DRB ID or the DRB ID occupied by the SN.

Step 903: The SN sends an RRC connection reconfiguration message to the UE.

The RRC connection reconfiguration message includes the updated mapping relationship configuration information of the QoS flow and the DRB transmitted by the SN.

Step 904: The SN receives an RRC connection reconfiguration complete message sent by the UE.

Step 905: The SN initiates an SN modification process, and the SN sends an SN modification request message to the MN.

Step 906: The MN sends an SN modification confirmation message to the SN.

For specific explanations of steps 906 to 907, reference may be made to step 706 and step 707, and details are not described herein again.

Step 907: The SN sends an RRC connection reconfiguration message to the UE.

After the SN receives the modification confirmation message sent by the MN, the SN determines the selected DRB ID. SN hair Sending an RRC connection reconfiguration message to the UE, where the RRC connection reconfiguration message includes configuration information of the updated mapping relationship between the QoS flow transmitted by the SN and the DRB.

Step 908: The SN receives an RRC connection reconfiguration complete message sent by the UE.

Step 909: The SN sends an SN configuration update message to the MN.

FIG. 13 is a flowchart of a method for acquiring a DRB identifier according to another embodiment of the present application. As shown in FIG. 13, the embodiment includes a user equipment, a first base station, and a second base station. The difference between this embodiment and the foregoing embodiments is that In this embodiment, the first base station requests to release the DRB according to the requirements of the user, and the method in this embodiment may include:

Step 1001: The first base station sends a first message to the second base station, where the second base station receives the first message sent by the first base station, where the first message is used to request to release at least one DRB.

When the first base station determines that the DRB needs to be reduced, the first message may be sent to the second base station to request to release the DRB. The second base station receives the first message, and learns the identifier of the DRB that the first base station needs to release.

The first message may specifically include any one or more of the following: an identifier of the at least one DRB that is requested to be released; and a mapping relationship between the DRB and the QoS flow configured by the first base station.

Step 1002: The first base station receives the second message sent by the second base station, and the second base station receives the second message sent by the first base station, where the second message is used to acknowledge receipt of the first message to the first base station.

Step 1003: The first base station sends the first information to the user equipment, where the user equipment receives the first information sent by the first base station, where the first information includes the identifier of the at least one DRB.

The identifier of the DRB included in the first information is the identifier of the released DRB.

It can be understood that the foregoing second message is used to feed back the acknowledgement release request to the first base station, and the second base station may further send a release reject message to reject the release request of the first base station.

In this embodiment, the first base station sends a first message to the second base station to request to release the DRB, and the second base station feeds back a second message to the first base station, where the first base station can determine the DRB that can be released according to the second message. A base station sends the identifier of the released DRB to the user equipment, so as to ensure the uniqueness of the ID of the DRB, so that the first base station can increase the DRB according to its own radio resource management policy and network status, so as to reconfigure the mapping between the QoS flow and the DRB. Relationships make DRB settings more flexible and efficient.

FIG. 14 is a flowchart of a method for acquiring a DRB identifier according to another embodiment of the present application. As shown in FIG. 14, the embodiment includes a user equipment, a first base station, and a second base station. The method in this embodiment may include:

Step 1101: The first base station sends a first message to the second base station, where the second base station receives the first message sent by the first base station, where the first message is used to indicate the identifier of the currently available DRB.

Specifically, the first base station sends a first message after the DRB identifier is updated to generate the identifier of the currently available DRB, and the reason for the DRB identifier update includes at least one of increasing the DRB and releasing the DRB.

The identifier of the currently available DRB does not include the identifier of the added DRB when the DRB identifier is updated because the DRB is updated.

When the reason for the DRB identifier update includes releasing the DRB, the identifier of the currently available DRB includes the released The ID of the DRB.

That is, the first base station needs to notify the second base station by using the first message after the DRB identifier is updated.

Step 1102: The first base station sends the first information to the user equipment, where the user equipment receives the first information sent by the first base station, where the first information may include at least one of the added DRB configuration information and the released DRB identifier. The configuration information of the added DRB may include an identifier of the added DRB.

The configuration information of the added DRB may further include other configuration information, such as a corresponding PDCP entity of the DRB, an RLC entity, and a configuration of a logical channel.

Optionally, the first information may further include mapping relationship information between the uplink QoS flow and the DRB.

An achievable manner, the first base station is a secondary base station, and the second base station is a primary base station; or

In another implementation manner, the first base station is a primary base station, and the second base station is a secondary base station.

Optionally, the first message may include any one or more of the following information: an identifier of the currently available DRB, an identifier of the DRB occupied by the first base station, an identifier of the DRB released by the first base station, and the first The mapping relationship between the QoS flow and the DRB configured by the base station.

Specifically, when the first message includes the identifier of the currently available DRB, the second base station acquires the identifier of the currently available DRB according to the first message.

When the first message includes the identifier of the DRB occupied by the first base station, the second base station determines the identifier of the currently available DRB according to the identifier of the DRB occupied by the first base station and the identifier of the available DRB maintained by the second base station.

When the first message includes the identifier of the DRB released by the first base station, the second base station determines the identifier of the currently available DRB according to the identifier of the DRB released by the first base station and the identifier of the available DRB maintained by the second base station.

When the first message includes the mapping relationship between the QoS flow and the DRB configured by the first base station, the second base station determines the identifier of the DRB occupied by the first base station according to the mapping relationship between the QoS flow and the DRB configured by the first base station, and is occupied according to the first base station. The identity of the DRB and the identity of the available DRB maintained by the second base station determine the identity of the currently available DRB.

Optionally, before the foregoing step 801 or after the foregoing step 802, the method may further include: the first base station receives the second message sent by the second base station, and the second base station sends the second message to the first base station, where the second The message is used to indicate the identifier of the available DRB; the first base station performs a DRB identity update on the identifier of the available DRB, and generates an identifier of the currently available DRB.

Specifically, the second base station maintains an identifier of the available DRB, and the second base station indicates, by using the second message, the identifier of the available DRB to the first base station. The first base station selects the identifier of the DRB from the identifier of the available DRB, adds the DRB, and updates the identifier of the DRB maintained by the first base station, generates an identifier of the currently available DRB, and passes the updated result. A message informs the second base station.

Optionally, the second message includes any one or more of the following information: an identifier of an available DRB; an identifier of a DRB occupied by the second base station; an identifier of the DRB released by the second base station; and the second base station The mapping between the configured QoS flow and the DRB.

Specifically, the first base station and the second base station both maintain the identifier of the available DRB, and after the usage of the identifier of the DRB of any one of the parties is updated, the updated result of the other party needs to be notified. The method of informing the other party of the updated result may be to directly inform the available DRB identifier, or to notify the other party of the ID of the DRB that is occupied or released by the other party, or the mapping relationship between the QoS flow and the DRB configured by the other party. The identified ID of the available DRB and the above information determine the updated result.

Optionally, when the first base station is the secondary base station, and the second base station is the primary base station, the method may further include: the first base station receiving the third message sent by the second base station, the third The message is for requesting to transfer at least one QoS flow to the first base station, or for requesting the first base station to add at least one QoS flow, or for requesting to transfer at least one DRB to the first base station, or for requesting Adding, by the first base station, at least one DRB;

The third message includes any one or more of the following information: an identifier of at least one QoS flow transferred to the first base station and a QoS parameter of the at least one QoS flow; the at least one QoS flow and the DRB Mapping relationship; indication of the type of transfer; identification of the available DRB.

The transfer type includes at least one of a QoS flow transfer and a DRB transfer.

The QoS flow transfer refers to the transfer of the QoS flow in the granularity of the QoS flow, that is, the transferred QoS flow is a partial QoS flow in the at least one DRB configured by the second base station, instead of all in the at least one DRB. QoS flow.

The DRB transfer refers to the transfer of the QoS flow with the DRB as the granularity, that is, the transferred QoS flow is all the QoS flows in the at least one DRB configured by the second base station.

After receiving the foregoing transfer, the first base station may perform subsequent steps 801 to 802 if it is determined that the DRB needs to be added to perform reconfiguration of the mapping of the QoS flow and the DRB.

The indication information of the mapping relationship between the at least one QoS flow and the DRB and the transfer type is included in a radio resource control information container (RRC Container), where the radio resource control information container (RRC Container) is included in the third message. in.

In an implementation manner of the foregoing step 802, the first base station sends a radio resource control reconfiguration message to the user equipment, where the radio resource control reconfiguration message includes the first information.

In another implementation manner of the foregoing step 803, the first base station sends a fourth message to the second base station, where the fourth message includes the first information, where the fourth message is used by the second base station to obtain the first information. And carrying the first information in a radio resource control reconfiguration message sent to the user equipment.

Optionally, the fourth message may further include second information, where the second information is used to indicate that the reason for sending the fourth message is to change a mapping relationship between the QoS flow and the DRB. Specifically, the fourth message includes the second information and the RRC Container, where the RRC Container includes the first information, and then, when receiving the fourth message, the second base station may first view the second information, where the fourth message carries the The second information indicates that the first base station modifies the mapping relationship between the QoS flow and the DRB, and then the second base station obtains the first information according to the first information and then the RRC Container, and if the second message does not carry the second information. For the information, the second base station may perform the step of acquiring information into the RRC Container, and directly transmit the RRC Container to the UE.

It should be noted that the fourth message and the first message in this embodiment may be two independent messages, or may be one message, which may be flexibly set according to requirements. The third message and the second message in this embodiment may be two independent messages, or may be one message, which can be flexibly set according to requirements.

In this embodiment, the first base station sends a first message to the second base station to indicate the identifier of the currently available DRB, and the first base station sends the first information to the user equipment, where the first information may include the configuration information of the added DRB and At least one of the identifiers of the released DRBs, thereby ensuring the uniqueness of the IDs of the DRBs, so that the first base station can increase the DRB according to its own radio resource management policy and network conditions, so as to reconfigure the mapping relationship between the QoS flows and the DRBs. This makes the DRB setting more flexible and effective.

The embodiment shown in Fig. 14 will be specifically explained below by using two specific embodiments.

15 is a flowchart of a method for acquiring a DRB identifier according to another embodiment of the present application. As shown in FIG. 15, the embodiment includes a UE, an MN, and an SN. The method in this embodiment may include:

Step 1201: The MN sends an SN addition request message to the SN.

Specifically, the MN decides to request the SN to transmit part of the QoS flow of the UE, and may send an SN addition request message to the SN. The SN addition request message may include (1) an identifier of the QoS flow that the MN requests the SN to transmit and a corresponding QoS parameter, and (2) a currently available DRB ID.

Optionally, the SN addition request message may further include: (3) a DRB ID of the at least one QoS flow that the MN allocates to the SN to transfer to the SN, and a mapping relationship between the QoS flow ID and the DRB ID.

(2) The currently available DRB ID can be carried in an RRC Container. If the content (3) is included in the increase request message, the content (3) may also be included in an RRC Container.

Step 1202: If the SN accepts the increase request, the SN replies to the SN to increase the request acknowledgement message.

In this embodiment, after receiving the SN addition request message sent by the MN, if the SN includes the content (3), the SN is configured according to the mapping relationship between the QoS flow ID and the DRB ID provided by the MN. . Otherwise, the SN itself selects the DRB ID according to the above contents (1) and (2), and determines the mapping relationship between the DRB ID and the QoS flow ID. In the increase request acknowledgement message, the QoS flow ID of the QoS flow that the SN agrees to accept may be included. In the increase request acknowledgement message, an RRC Container may also be included. The RRC Container includes radio resource configuration information of the SN, radio bearer configuration information, and a mapping relationship between the DRB and the QoS flow.

Step 1203: The MN sends an RRC connection reconfiguration message to the UE, where the RRC connection reconfiguration message includes information in the RRC Container in the SN reply increase request acknowledgement message.

Step 1204: The MN receives an RRC connection reconfiguration complete message sent by the UE.

Step 1205: The MN sends an SN reconfiguration complete message to the SN. The SN reconfiguration complete message is an Xn interface or an X2 interface message between the MN and the SN.

Step 1206: The SN sends an SN modification request message to the MN. The modification request message is used by the SN to initiate a modification process of the DRB.

The modification request message is the first message of the embodiment shown in FIG.

Specifically, when the SN needs to increase the DRB or release the DRB, the SN initiates the SN modification process and sends a modification request message to the MN. If the DRB needs to be added, before the SN initiates the SN modification process, the SN selects the DRB ID according to the available DRB ID provided by the MN, and determines the mapping relationship between the new QoS flow and the DRB.

For specific information included in the modification request message, refer to the explanation of the specific information of the first message in the embodiment shown in FIG. 10, and details are not described herein again.

Optionally, the SN may further include a reason for sending the modification request message in the modification request message, where the reason information of the modification request message may be set to QoS flow re-mapping, that is, changing the mapping relationship between the QoS flow and the DRB to notify the MN The reason for initiating the modification process. The MN may determine the remaining available DRB ID according to the DRB ID included in the modification request message, and whether the RN-assigned DRB ID conflicts with the MN-assigned DRB ID.

Step 1207: If the DRB IDs allocated by the MN and the SN do not conflict, the MN sends an RRC connection reconfiguration message to the UE. The RRC connection reconfiguration message carries the RRC Container in the modification request message sent by the SN. Information.

It can be understood that if the DRB ID assigned by the MN and the SN conflicts, the MN sends a modification rejection message to the SN.

Step 1208: The MN receives an RRC connection reconfiguration complete message sent by the UE.

Step 1209: The MN sends an SN modification confirmation message to the SN. The SN modification acknowledgement message is an Xn interface or an X2 interface message between the MN and the SN.

Step 1210: The MN updates the available DRB ID maintained by itself.

Step 1211: The MN sends an MN configuration update message to the SN. The MN configuration update message includes the available DRB ID after the MN is updated.

When the number of DRBs configured by the MN changes, the MN sends the updated available DRB ID to the SN through the configuration update message. Reasons for the change in the number of DRBs include MN increasing DRB and MN releasing DRB.

The configuration update message may be an SN modification request message. That is, when the number of DRBs configured by the MN changes, the MN initiates an SN modification process and sends an SN modification request message to the SN. The modified request message includes the available DRB ID after the MN is updated.

The configuration update message may also be a newly defined message.

In this embodiment, the uniqueness of the ID of the DRB can be ensured, and the SN can be configured to increase the DRB according to its own radio resource management policy and network status, so as to reconfigure the mapping relationship between the QoS flow and the DRB, so that the DRB setting is more flexible and effective.

FIG. 16 is a flowchart of a method for acquiring a DRB identifier according to another embodiment of the present application. As shown in FIG. 16, the embodiment includes a UE, an MN, and an SN. The method in this embodiment may include:

Step 1301: The MN sends an SN addition request message to the SN.

Step 1302: If the SN accepts the increase request, the SN replies to the SN to increase the request acknowledgement message.

For the specific implementation of the steps 1001 to 1002, refer to the specific explanation of the steps 901 to 902, and details are not described herein again.

Step 1303: The SN sends an RRC connection reconfiguration message to the UE, where the RRC connection reconfiguration message includes the updated mapping relationship between the QoS flow and the DRB transmitted by the SN. The mapping relationship between the QoS flow and the DRB may be a mapping relationship between the uplink QoS flow and the DRB.

Step 1304: The SN receives an RRC connection reconfiguration complete message sent by the UE.

Step 1305, the SN updates the available DRB ID.

Step 1306: The SN sends an SN configuration update message to the MN. The SN configuration update message carries the updated available DRB ID.

When the number of DRBs configured by the SN changes, the SN sends the updated available DRB ID to the MN through the configuration update message. The reasons for the change in the number of DRBs include SN increasing DRB and SN releasing DRB.

The configuration update message may be an SN modification requirement message. That is, when the number of DRBs configured by the SN changes, the SN initiates an SN modification process, and sends an SN modification request message to the MN. The modified request message includes an available DRB ID after the SN is updated.

The configuration update message may also be a newly defined message.

Step 1307: The MN updates the available DRB ID maintained by itself.

Step 1308: The MN sends an MN configuration update message to the SN. The MN configuration update message includes the available DRB ID after the MN is updated.

The configuration update message may also be a newly defined message.

FIG. 17 is a schematic structural diagram of a first base station according to the present application. As shown in FIG. 17, the first base station in this embodiment may include: a sending module 11 and a receiving module 12, where the sending module 11 is configured to use the second base station. Sending a first message, the first message is used to request to add a data radio bearer DRB, the receiving module 12 is configured to receive a second message sent by the second base station, and the second message is used to indicate an identifier of the at least one DRB, The sending module 11 is further configured to send first information to the user equipment, where the first information includes DRB configuration information, and the DRB configuration information includes an identifier of the at least one DRB.

Optionally, the first information further includes information about a mapping relationship between the uplink quality of service QoS flow and the at least one DRB.

Optionally, the first base station is a secondary base station, and the second base station is a primary base station.

Optionally, the first message includes any one or more of the following information: requesting to increase the indication information of the DRB; requesting to increase the number of DRBs; identifying the remapping QoS flow; grouping information of the remapped QoS flow The index of the packet of the remapping QoS flow.

Optionally, the second message includes any one or more of the following information: an identifier of an available DRB; an identifier of the at least one DRB; an identifier of the QoS flow that is allowed to be mapped to the at least one DRB; and the mapping is denied to the at least one The identifier of the QoS flow of the DRB; the mapping relationship configuration information of the DRB and the QoS flow; the mapping relationship configuration information of the packet of the DRB and the QoS flow; and the mapping relationship configuration information of the index of the packet of the DRB and the QoS flow.

Optionally, the receiving module 12 is further configured to: receive a third message sent by the second base station, where the third message is used to request to transfer at least one QoS flow to the first base station, or to request a The first base station adds at least one QoS flow, or is used to request to transfer at least one DRB to the first base station, or is used to request the first base station to add at least one DRB;

Optionally, the sending, by the sending module, the first information is sent to the user equipment, including: sending a radio resource control reconfiguration message to the user equipment, where the radio resource control reconfiguration message includes the first information.

Optionally, the sending module 11 is further configured to: send a fourth message to the second base station, where the fourth message includes any one or more of the following information: an identifier of an available DRB; The identifier of the DRB selected by the first base station; the mapping relationship between the QoS flow and the DRB configured by the first base station.

Optionally, the first base station in the embodiment of the present application may further include a processing module 13 and a storage module, where the storage module is configured to store program code and data of the first base station, where the processing module 13 is configured to invoke the program code of the storage module and The data, the transmitting module 11 and the receiving module 12 in this embodiment are controlled to perform the above operations.

The first base station in this embodiment may be used to implement the technical solution of the foregoing method embodiment, and the implementation principle and the technical effect are similar, and details are not described herein again.

FIG. 18 is a schematic structural diagram of a second base station according to the present application. As shown in FIG. 18, the second base station in this embodiment may include: a receiving module 21 and a sending module 22, where the receiving module 21 is configured to receive the first a first message sent by the base station, the first message is used to request to add a data radio bearer DRB, and the sending module 22 is configured to send a second message to the first base station, where the second message is used to indicate at least one DRB Logo.

Optionally, the sending module 22 is further configured to: send, to the first base station, a third message, where the third message is used to request to transfer at least one QoS flow to the first base station, or to request the The first base station adds at least one QoS flow, or is used to request to transfer at least one DRB to the first base station, or is used to request the first base station to add at least one DRB;

Optionally, the receiving module 21 is further configured to: receive a fourth message sent by the first base station, where the fourth message includes any one or more of the following information: an identifier of an available DRB; The identifier of the DRB selected by the first base station; the mapping relationship between the QoS flow and the DRB configured by the first base station.

Optionally, the second base station in the embodiment of the present application may further include a processing module 23 for storing program codes and data of the first base station, and a storage module, where the processing module 23 is configured to invoke the program code of the storage module and The data, the transmitting module 22 and the receiving module 21 in the present embodiment are controlled to perform the above operations.

The second base station in this embodiment may be used to implement the technical solution of the foregoing method embodiment, and the implementation principle and the technical effect are similar, and details are not described herein again.

The embodiment of the present application further provides another first base station, and the structure of the first base station is the same as that of FIG. 17. For details, refer to FIG. 17, the sending module of the first base station in this embodiment is used to send to the second base station. Sending a first message, where the first message is used to indicate an identifier of a currently available DRB;

The sending module is further configured to send the first information to the user equipment, where the first information includes at least one of an added DRB configuration information and a released DRB identifier, where the added DRB configuration information includes an increased The ID of the DRB.

Optionally, the first base station sends the first message after the DRB identifier update generates the identifier of the currently available DRB, and the reason for the DRB identifier update includes at least one of increasing a DRB and releasing a DRB.

Optionally, the first information further includes mapping relationship information between the uplink QoS flow and the DRB.

Optionally, the first base station is a secondary base station, and the second base station is a primary base station; or the first base station is a primary base station, and the second base station is a secondary base station.

Optionally, the first message includes any one or more of the following information: an identifier of a currently available DRB; an identifier of a DRB occupied by the first base station; an identifier of the DRB released by the first base station; The mapping relationship between the QoS flow and the DRB configured by the base station.

Optionally, the receiving module is configured to receive a second message sent by the second base station, where the second message is used to indicate an identifier of an available DRB, and the processing module is configured to perform DRB on an identifier of an available DRB. Identifying an update, generating an identifier of the currently available DRB.

Optionally, the receiving module is further configured to receive a third message sent by the second base station, where the third message is used to request to transfer at least one QoS flow to the first base station, or to request the The first base station adds at least one QoS flow, or is used to request to transfer at least one DRB to the first base station, or is used to request the first base station to add at least one DRB;

The third message includes any one or more of the following information: an identifier of at least one QoS flow transferred to the first base station and a QoS parameter of the at least one QoS flow; the at least one QoS flow and the DRB Mapping relationship; indication of the type of transfer; identification of the available DRB. The transfer type includes at least one of a QoS flow transfer and a DRB transfer.

It should be noted that the first base station in the embodiment shown in FIG. 17 may correspond to an object device having the same function, for example, a base station, and the sending module 11 in the embodiment of the present application may correspond to a transmitter of the base station, or may correspond to the base station. Transceiver. The receiving module 12 may correspond to a receiver of the base station, or may correspond to a transceiver of the base station. The processing module 13 may correspond to a processor of the base station, where the processor may be a central processing unit (CPU), or an application specific integrated circuit (ASIC), or complete the implementation of the embodiment of the present application. One or more integrated circuits. The base station may further include a memory for storing the instruction code, the processor invoking the instruction code of the memory, and controlling the sending module 11 and the receiving module 12 in the embodiment of the present application to perform the foregoing operations.

It should be noted that the second base station in the embodiment shown in FIG. 18 may correspond to an object device having the same function, for example, a base station, and the sending module 22 in the embodiment of the present application may correspond to a transmitter of the base station, or may correspond to the base station. Transceiver. The receiving module 21 may correspond to a receiver of the base station, or may correspond to a transceiver of the base station. The processing module 23 may correspond to a processor of the base station, where the processor may be a CPU, or an ASIC, or one or more integrated circuits that implement the embodiments of the present application. The base station may further include a memory for storing the instruction code, the processor invoking the instruction code of the memory, and controlling the sending module 22 and the receiving module 21 in the embodiment of the present application to perform the foregoing operations.

When the function of the method for acquiring the DRB identifier of the embodiment of the present application is implemented by software, the embodiment of the present application further provides a computer readable storage medium, where the computer readable storage medium is used to store the computer used by the first base station. The software instructions, when run on a computer, cause the computer to perform various possible DRB identification acquisition methods in the above method embodiments. When the computer-executed instructions are loaded and executed on a computer, the processes or functions described in accordance with embodiments of the present application may be generated in whole or in part. The computer instructions can be stored in a computer readable storage medium or transmitted from one computer readable storage medium to another computer readable storage medium, such as cellular communication, infrared, short-range wireless, microwave Etc.) Transfer to another website site, computer, server, or data center. The computer readable storage medium can be any available media that can be accessed by a computer or a data storage device such as a server, data center, or the like that includes one or more available media. The usable medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a DVD), or a semiconductor medium (such as a solid state disk (SSD)).

When the function of the method for acquiring the DRB identifier of the embodiment of the present application is implemented by software, the embodiment of the present application further provides a computer readable storage medium, where the computer readable storage medium is used to store the computer used by the second base station. The software instructions, when run on a computer, cause the computer to perform various possible DRB identification acquisition methods in the above method embodiments. When the computer-executed instructions are loaded and executed on a computer, the processes or functions described in accordance with embodiments of the present application may be generated in whole or in part. The computer instructions can be stored in a computer readable storage medium or transmitted from one computer readable storage medium to another computer readable storage medium, such as cellular communication, infrared, short-range wireless, microwave Etc.) Transfer to another website site, computer, server, or data center. The computer readable storage medium can be any available media that can be accessed by a computer or a data storage device such as a server, data center, or the like that includes one or more available media. The usable medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a DVD), or a semiconductor medium (eg, an SSD) or the like.

In addition, the embodiment of the present application further provides a computer program product, that is, a software product, which, when run on a computer, causes the computer to execute various possible DRB identifier acquisition methods in the foregoing method embodiments. The implementation principle and technical effect are similar, and will not be described here.

Finally, it should be noted that the above embodiments are only for explaining the technical solutions of the present application, and are not limited thereto; although the present application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that The technical solutions described in the foregoing embodiments may be modified, or some or all of the technical features may be equivalently replaced; and the modifications or substitutions do not deviate from the technical solutions of the embodiments of the present application. range.

Claims

A method for obtaining a data radio bearer identifier, comprising:

The first base station sends a first message to the second base station, where the first message is used to request to increase the data radio bearer DRB;

Receiving, by the first base station, a second message sent by the second base station, where the second message is used to indicate an identifier of the at least one DRB;

The first base station sends first information to the user equipment, where the first information includes DRB configuration information, and the DRB configuration information includes an identifier of the at least one DRB.
The method according to claim 1, wherein the first information further comprises information of a mapping relationship between the uplink quality of service QoS flow and the at least one DRB.
The method according to claim 1 or 2, wherein the first base station is a secondary base station, and the second base station is a primary base station.
The method according to any one of claims 1 to 3, wherein the first message comprises any one or more of the following information:

Request to increase the DRB indication information;

Request to increase the number of DRBs;

The identity of the remapped QoS flow;

Grouping information of the remapped QoS flow;

The index of the packet of the remapped QoS flow.
The method according to any one of claims 1 to 4, wherein the second message comprises any one or more of the following information:

The ID of the available DRB;

At least one DRB identifier;

Allowing identification of QoS flows mapped to at least one DRB;

Rejecting an identifier of a QoS flow mapped to at least one DRB;

Mapping relationship information between the DRB and the QoS flow;

Mapping relationship configuration information of packets of the DRB and the QoS flow;

Mapping relationship configuration information of the index of the packet of the DRB and the QoS flow.
The method according to any one of claims 1 to 5, wherein before the first base station sends the first message to the second base station, the method further includes:

Receiving, by the first base station, a third message sent by the second base station, where the third message is used to request to transfer at least one QoS flow to the first base station, or used to request the first base station to add at least one QoS Flowing, or for requesting to transfer at least one DRB to the first base station, or for requesting the first base station to add at least one DRB;

The third message includes any one or more of the following information:

And an identifier of the at least one QoS flow transferred to the first base station and a QoS parameter of the at least one QoS flow;

a mapping relationship between the at least one QoS flow and the DRB;

Indication information of the transfer type;

The transfer type includes at least one of a QoS flow transfer and a DRB transfer.
The method according to any one of claims 1 to 6, wherein the method further comprises:

The first base station sends a fourth message to the second base station, where the fourth message includes any one or more of the following information:

The ID of the available DRB;

The identifier of the DRB selected by the first base station;

The mapping relationship between the QoS flow and the DRB configured by the first base station.
A method for obtaining a data radio bearer identifier, comprising:

Receiving, by the second base station, the first message sent by the first base station, where the first message is used to request to increase the data radio bearer DRB;

The second base station sends a second message to the first base station, where the second message is used to indicate an identifier of the at least one DRB.
The method according to claim 8, wherein the first base station is a secondary base station, and the second base station is a primary base station.
The method according to claim 8 or 9, wherein before the second base station receives the first message sent by the first base station, the method further includes:

The second base station sends a third message to the first base station, where the third message is used to request to transfer at least one QoS flow to the first base station, or is used to request the first base station to add at least one QoS flow. Or for requesting to transfer at least one DRB to the first base station, or for requesting the first base station to add at least one DRB;

The third message includes any one or more of the following information:

And an identifier of the at least one QoS flow transferred to the first base station and a QoS parameter of the at least one QoS flow;

a mapping relationship between the at least one QoS flow and the DRB;

Indication information of the transfer type;

The transfer type includes at least one of a QoS flow transfer and a DRB transfer.
The method according to any one of claims 8 to 10, wherein the method further comprises:

The second base station receives a fourth message sent by the first base station, where the fourth message includes any one or more of the following information:

The ID of the available DRB;

The identifier of the DRB selected by the first base station;

The mapping relationship between the QoS flow and the DRB configured by the first base station.
A method for obtaining a data radio bearer identifier, comprising:

The first base station sends a first message to the second base station, where the first message is used to indicate an identifier of the currently available DRB;

The first base station sends the first information to the user equipment, where the first information includes at least one of an added DRB configuration information and a released DRB identifier, where the added DRB configuration information includes an increased DRB. Logo.
The method according to claim 12, wherein the first base station sends the first message after the DRB identifier update generates the identifier of the currently available DRB, and the DRB identifies the updated reason packet. Including at least one of increasing DRB and releasing DRB.
The method according to claim 12 or 13, wherein the first information further comprises mapping relationship information between the uplink QoS flow and the DRB.
The method according to any one of claims 12 to 14, wherein the first base station is a secondary base station, and the second base station is a primary base station; or

The first base station is a primary base station, and the second base station is a secondary base station.
The method according to any one of claims 12 to 15, wherein the first message comprises any one or more of the following information:

The ID of the currently available DRB;

The identifier of the DRB occupied by the first base station;

The identifier of the DRB released by the first base station;

The mapping relationship between the QoS flow and the DRB configured by the first base station.
The method of claim 13 wherein the method further comprises:

Receiving, by the first base station, a second message sent by the second base station, where the second message is used to indicate an identifier of an available DRB;

The first base station performs a DRB identity update on the identifier of the available DRB, and generates an identifier of the currently available DRB.
The method according to any one of claims 12 to 15, wherein the second message comprises any one or more of the following information:

The ID of the available DRB;

The identifier of the DRB occupied by the second base station;

The identifier of the DRB released by the second base station;

The mapping relationship between the QoS flow and the DRB configured by the second base station.
A method according to any one of claims 12 to 18, wherein the method further comprises

Receiving, by the first base station, a third message sent by the second base station, where the third message is used to request to transfer at least one QoS flow to the first base station, or used to request the first base station to add at least one QoS Flowing, or for requesting to transfer at least one DRB to the first base station, or for requesting the first base station to add at least one DRB;

The third message includes any one or more of the following information:

And an identifier of the at least one QoS flow transferred to the first base station and a QoS parameter of the at least one QoS flow;

a mapping relationship between the at least one QoS flow and the DRB;

Indication information of the transfer type;

The ID of the available DRB;

The transfer type includes at least one of a QoS flow transfer and a DRB transfer.
A first base station, comprising:

a transmitter, configured to send a first message to the second base station, where the first message is used to request to increase the data radio bearer DRB;

a receiver, configured to receive a second message sent by the second base station, where the second message is used to indicate at least one ID of the DRB;

The transmitter is further configured to send first information to the user equipment, where the first information includes DRB configuration information, and the DRB configuration information includes an identifier of the at least one DRB.
The first base station according to claim 20, wherein the first information further comprises information of a mapping relationship between the uplink quality of service QoS flow and the at least one DRB.
The first base station according to claim 20 or 21, wherein the first base station is a secondary base station, and the second base station is a primary base station.
The first base station according to any one of claims 20 to 22, wherein the first message comprises any one or more of the following information:

Request to increase the DRB indication information;

Request to increase the number of DRBs;

The identity of the remapped QoS flow;

Grouping information of the remapped QoS flow;

The index of the packet of the remapped QoS flow.
The first base station according to any one of claims 20 to 23, wherein the second message comprises any one or more of the following information:

The ID of the available DRB;

At least one DRB identifier;

Allowing identification of QoS flows mapped to at least one DRB;

Rejecting an identifier of a QoS flow mapped to at least one DRB;

Mapping relationship information between the DRB and the QoS flow;

Mapping relationship configuration information of packets of the DRB and the QoS flow;

Mapping relationship configuration information of the index of the packet of the DRB and the QoS flow.
The first base station according to any one of claims 20 to 24, wherein the receiver is further configured to:

Receiving a third message sent by the second base station, where the third message is used to request to transfer at least one QoS flow to the first base station, or used to request the first base station to add at least one QoS flow, or Requesting to transfer at least one DRB to the first base station, or for requesting the first base station to add at least one DRB;

The third message includes any one or more of the following information:

And an identifier of the at least one QoS flow transferred to the first base station and a QoS parameter of the at least one QoS flow;

a mapping relationship between the at least one QoS flow and the DRB;

Indication information of the transfer type;

The transfer type includes at least one of a QoS flow transfer and a DRB transfer.
The first base station according to any one of claims 20 to 25, wherein the transmitter is further configured to:

Sending a fourth message to the second base station, where the fourth message includes any one or more of the following information:

The ID of the available DRB;

The identifier of the DRB selected by the first base station;

The mapping relationship between the QoS flow and the DRB configured by the first base station.
A second base station, comprising:

a receiver, configured to receive a first message sent by the first base station, where the first message is used to request to increase the data radio bearer DRB;

And a transmitter, configured to send a second message to the first base station, where the second message is used to indicate an identifier of the at least one DRB.
The second base station according to claim 27, wherein the first base station is a secondary base station, and the second base station is a primary base station.
The second base station according to claim 27 or 28, wherein the transmitter is further configured to:

Sending a third message to the first base station, the third message is used to request to transfer at least one QoS flow to the first base station, or to request the first base station to add at least one QoS flow, or for requesting Transferring at least one DRB to the first base station, or for requesting the first base station to add at least one DRB;

The third message includes any one or more of the following information:

And an identifier of the at least one QoS flow transferred to the first base station and a QoS parameter of the at least one QoS flow;

a mapping relationship between the at least one QoS flow and the DRB;

Indication information of the transfer type;

The transfer type includes at least one of a QoS flow transfer and a DRB transfer.
The second base station according to any one of claims 27 to 29, wherein the receiver is further configured to:

Receiving a fourth message sent by the first base station, where the fourth message includes any one or more of the following information:

The ID of the available DRB;

The identifier of the DRB selected by the first base station;

The mapping relationship between the QoS flow and the DRB configured by the first base station.
A first base station, comprising:

a transmitter, configured to send a first message to the second base station, where the first message is used to indicate an identifier of a currently available DRB;

The transmitter is further configured to send, to the user equipment, the first information, where the first information includes at least one of an increased DRB configuration information and a released DRB identifier, where the added DRB configuration information includes an increased The ID of the DRB.
The first base station according to claim 31, wherein the first base station sends the first message after the DRB identifier update generates the identifier of the currently available DRB, and the reason for the DRB identifier update includes adding At least one of DRB and release DRB.
The first base station according to claim 31 or 32, wherein the first information further comprises mapping relationship information between the uplink QoS flow and the DRB.
The first base station according to any one of claims 31 to 33, wherein the first base station is a secondary base station, and the second base station is a primary base station; or

The first base station is a primary base station, and the second base station is a secondary base station.
The first base station according to any one of claims 31 to 34, wherein the first message comprises any one or more of the following information:

The ID of the currently available DRB;

The identifier of the DRB occupied by the first base station;

The identifier of the DRB released by the first base station;

The mapping relationship between the QoS flow and the DRB configured by the first base station.
The first base station according to claim 32, wherein the first base station further comprises: a receiver and a processor;

The receiver is configured to receive a second message sent by the second base station, where the second message is used to indicate an identifier of an available DRB;

The processor is configured to perform a DRB identity update on the identifier of the available DRB, and generate an identifier of the currently available DRB.
The first base station according to any one of claims 32 to 34, wherein the second message comprises any one or more of the following information:

The ID of the available DRB;

The identifier of the DRB occupied by the second base station;

The identifier of the DRB released by the second base station;

The mapping relationship between the QoS flow and the DRB configured by the second base station.
The first base station according to any one of claims 32 to 37, wherein the receiver is further configured to:

Receiving a third message sent by the second base station, where the third message is used to request to transfer at least one QoS flow to the first base station, or used to request the first base station to add at least one QoS flow, or Requesting to transfer at least one DRB to the first base station, or for requesting the first base station to add at least one DRB;

The third message includes any one or more of the following information:

And an identifier of the at least one QoS flow transferred to the first base station and a QoS parameter of the at least one QoS flow;

a mapping relationship between the at least one QoS flow and the DRB;

Indication information of the transfer type;

The ID of the available DRB;

The transfer type includes at least one of a QoS flow transfer and a DRB transfer.