Method for Obtaining Data Radio Bearer Identifier and Base Station

Abstract

An embodiment of the present application provides a method for obtaining a data radio bearer identifier and a base station. The method for obtaining a data radio bearer identifier in the present application includes: a first base station sends a first message to a second base station, and the first message is used to request to add a data radio bearer (DRB); the first base station receives a second message sent by the second base station, and the second message is used to indicate the identifiers of at least one DRB; the first base station sends first information to a user equipment, and the first information includes DRB configuration information, and the DRB configuration information includes the identifiers of the at least one DRB. The embodiment of the present application can enable the first base station to add a DRB according to its own radio resource management policy and network conditions, and reconfigure the mapping relationship between the QoS flow and the DRB, so that the setting of the DRB is more flexible and effective.

Description

Technical Field

[0001] Embodiments of the present application relate to communication technologies, and in particular, to a method for obtaining a data radio bearer identifier and a base station. Background Art

[0002] The core network may establish one or more packet data unit (PDU) sessions for a user equipment (UE). Each PDU session includes one or more quality of service (QoS) flows. The radio access network may establish one or more data radio bearers (DRBs) for each PDU session. To ensure the service quality of data packets of different QoS flows, the radio access network may map data packets of different QoS flows belonging to the same PDU session to different DRBs, or may map data packets of different QoS flows of the same PDU session to the same DRB. Specifically, the mapping of data packets to DRBs is divided into two steps. The first step is the mapping of IP flow to QoS flow completed by the non-access stratum (NAS), and the second step is the mapping of QoS flow to DRB completed by the access stratum (AS). Among them, 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 either a many-to-one relationship or a one-to-one relationship.

[0003] To improve the throughput of data transmission of the UE and reduce the signaling overhead of the core network caused by 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 connection to the core network control plane for the UE is called the master eNB, and the other base station that provides additional radio resources for the UE is called the secondary eNB. In the 5G system, the dual connection technology will still be adopted.

[0004] In the dual - connection architecture connected to the 5G core network, the Master Node (MN) determines to transfer a part of the UE's QoS flows to the Secondary Node (SN), and the SN determines the mapping of this part of the QoS flows to the DRBs. Among them, the MN can specifically be an MgNB (Master gNB) or an MeNB (Master eNB), and the SN can specifically be an SgNB (Secondary gNB) or an SeNB (Secondary eNB). Compared with the number of DRBs used in the mapping of QoS flows determined by the MN to DRBs, the SN may increase or decrease the DRBs. No matter how the SN determines the mapping relationship between QoS and DRBs, the IDs of the DRBs configured for the UE need to be ensured to be unique, that is, there cannot be a situation where more than one DRB shares the same ID. Therefore, a problem to be solved is how to manage the IDs of DRBs. Summary of the Invention

[0005] Embodiments of this application provide a method for obtaining a data radio bearer identifier and a base station, which can ensure the uniqueness of the DRB ID, enabling the first base station to increase DRBs according to its own radio resource management strategy and network conditions, and re - configure the mapping relationship between QoS flows and DRBs, making the setting of DRBs more flexible and effective.

[0006] In a first aspect, embodiments of this application provide a method for obtaining a data radio bearer identifier, including: the first base station sends a first message to the second base station, and the first message is used to request to increase a data radio bearer DRB; the first base station receives a second message sent by the second base station, and the second message is used to indicate the identifiers of at least one DRB; the first base station sends first information to the user equipment, and the first information includes DRB configuration information, and the DRB configuration information includes the identifiers of the at least one DRB.

[0007] In combination with the first aspect, in a possible implementation manner of the first aspect, the first information further includes information on the mapping relationship between the uplink quality of service QoS flow and the at least one DRB.

[0008] In combination 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 master base station.

[0009] Combined with the first aspect or any possible implementation manner 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: indication information for requesting to increase a DRB; the number of DRBs requested to be increased; the identifier of the QoS flow mapped to the DRB requested to be increased; the packet information of the QoS flow mapped to the DRB requested to be increased; the index of the packet of the QoS flow mapped to the DRB requested to be increased.

[0010] Combined with the first aspect or any possible implementation manner of the first aspect, in another possible implementation manner of the first aspect, the second message includes any one or more of the following information: the identifier of the available DRB; the identifier of at least one DRB; the identifier of the QoS flow allowed to be mapped to at least one DRB; the identifier of the QoS flow refused to be mapped to at least one DRB; the mapping relationship configuration information between the DRB and the QoS flow; the mapping relationship configuration information between the DRB and the packet of the QoS flow; the mapping relationship configuration information between the index of the packet of the DRB and the QoS flow.

[0011] Combined with the first aspect or any possible implementation manner 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 includes: 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 to request the first base station to increase at least one QoS flow, or to request to transfer at least one DRB to the first base station, or to request the first base station to increase at least one DRB;

[0012] The third message includes any one or more of the following information: the identifier of at least one QoS flow transferred to the first base station and the QoS parameters of the at least one QoS flow; the mapping relationship between the at least one QoS flow and the DRB; indication information of the transfer type; where the transfer type includes at least one of QoS flow transfer and DRB transfer.

[0013] Combined with the first aspect or any possible implementation manner of the first aspect, in another possible implementation manner of the first 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, and the radio resource control reconfiguration message includes the first information.

[0014] Combined with the first aspect or any possible implementation manner of the first aspect, in another possible implementation manner of the first aspect, the method further includes: the first base station sends a fourth message to the second base station, and the fourth message includes any one or more of the following information: the identifier of the available DRB; the identifier of the DRB selected by the first base station; the mapping relationship between the QoS flow configured by the first base station and the DRB.

[0015] Combined with the first aspect or any possible implementation manner of the first aspect, in another possible implementation manner of the first aspect, the first base station sends first information to the user equipment, including: the first base station sends a fifth message to the second base station, the fifth message includes the first information, and the fifth message is used for the second base station to obtain the first information and carry the first information in the radio resource control reconfiguration message sent to the user equipment.

[0016] Combined with the first aspect or any possible implementation manner of the first aspect, in another possible implementation manner of the first aspect, the first information is specifically set in the radio resource control information container of the fifth message.

[0017] In a second aspect, an embodiment of the present application provides a method for obtaining a data radio bearer identifier, including: the second base station receives a first message sent by the first base station, and 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, and the second message is used to indicate the identifier of at least one DRB.

[0018] Combined with 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.

[0019] Combined 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 sends a third message to the first base station, and 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 increase at least one QoS flow, or to request to transfer at least one DRB to the first base station, or to request the first base station to increase at least one DRB;

[0020] The third message includes any one or more of the following information: the identifier of at least one QoS flow transferred to the first base station and the QoS parameters of the at least one QoS flow; the mapping relationship between the at least one QoS flow and the DRB; the indication information of the transfer type. Wherein, the transfer type includes at least one of QoS flow transfer and DRB transfer.

[0021] Combined with the second aspect or any possible implementation manner of the second aspect, in another possible implementation manner of the second aspect, the method further includes: the second base station receives a fourth message sent by the first base station, and the fourth message includes any one or more of the following information: the identifier 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.

[0022] Combined with the second aspect or any possible implementation manner of the second aspect, in another possible implementation manner of the second aspect, the method further includes: the second base station receives a fifth message sent by the first base station; the second base station obtains the first information from the fifth message; the second base station sends a radio resource control reconfiguration message to the user equipment, and the radio resource control reconfiguration message includes the first information.

[0023] Combined with the second aspect or any possible implementation manner of the second aspect, in another possible implementation manner of the second aspect, the second base station obtaining the first information from the fifth message includes: the second base station obtains the first information from the radio resource control information container of the fifth message.

[0024] In a third aspect, an embodiment of the present application provides a method for obtaining a data radio bearer identifier, including: the first base station sends a first message to the second base station, and the first message is used to indicate the identifier of the currently available DRB; the first base station sends first information to the user equipment, and 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.

[0025] Combined with the third aspect, in a possible implementation manner of the third aspect, the first base station sends the first message after generating the identifier of the currently available DRB by DRB identifier update, and the reason for the DRB identifier update includes at least one of adding a DRB and releasing a DRB.

[0026] Combined 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 the mapping relationship information between the uplink QoS flow and the DRB.

[0027] Combined with the third aspect or any possible implementation manner 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 station is a primary base station and the second base station is a secondary base station.

[0028] Combined with the third aspect or any possible implementation manner 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: the identifier 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 flows and DRBs configured by the first base station.

[0029] Combined with the third aspect or any possible implementation manner 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 includes: the first base station receives a second message sent by the second base station, where the second message is used to indicate the identifier of the available DRB; the first base station performs a DRB identifier update on the identifier of the available DRB to generate the identifier of the currently available DRB.

[0030] Combined with the third aspect or any possible implementation manner 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: the identifier 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 flows and DRBs configured by the second base station.

[0031] Combined with the third aspect or any possible implementation manner of the third aspect, in another possible implementation manner of the third aspect, the method further includes: 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 to request the first base station to add at least one QoS flow, or to request to transfer at least one DRB to the first base station, or to request the first base station to add at least one DRB;

[0032] The third message includes any one or more of the following information: the identifier of at least one QoS flow transferred to the first base station and the QoS parameters of the at least one QoS flow; the mapping relationship between the at least one QoS flow and the DRB; the indication information of the transfer type; the identifier of the available DRB. Wherein, the transfer type includes at least one of QoS flow transfer and DRB transfer

[0033] Combined with the third aspect or any possible implementation manner 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:

[0034] The first base station sends a radio resource control reconfiguration message to the user equipment, and the radio resource control reconfiguration message includes the first information.

[0035] Combined with the third aspect or any possible implementation manner of the third aspect, in another possible implementation manner of the third aspect, the first base station sends first information to the user equipment, including: the first base station sends a fourth message to the second base station, the fourth message includes the first information, and the fourth message is used for the second base station to obtain the first information and carry the first information in a radio resource control reconfiguration message sent to the user equipment.

[0036] Combined with the third aspect or any possible implementation manner of the third aspect, in another possible implementation manner of the third aspect, the fourth message further includes second information, and the second information is used to indicate that the reason for sending the fourth message is to change the mapping relationship between the QoS flow and the DRB.

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

[0038] In a fifth aspect, an embodiment of the present application provides a first base station, including: a processor, a memory, a bus, and a communication interface; the memory is used to store computer execution instructions, the processor is connected to the memory through the bus, and when the first base station runs, the processor executes the computer execution instructions stored in the memory so that the first base station executes the method for obtaining the data radio bearer identifier according to any item in the first aspect above or the method for obtaining the data radio bearer identifier according to any item in the third aspect above.

[0039] In a sixth aspect, an embodiment of the present application provides a computer-readable storage medium, which is used to store computer software instructions for the above first base station. When it runs on a computer, it enables the computer to execute the method for obtaining the data radio bearer identifier according to any item in the first aspect above or the method for obtaining the data radio bearer identifier according to any item in the third aspect above.

[0040] In a seventh aspect, an embodiment of the present application provides a computer program product containing instructions. When it runs on a computer, it enables the computer to execute the method for obtaining the data radio bearer identifier according to any item in the first aspect above or the method for obtaining the data radio bearer identifier according to any item in the third aspect above.

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

[0042] In a ninth aspect, an embodiment of the present application provides a second base station, including: a processor, a memory, a bus, and a communication interface; the memory is used to store computer-executable instructions, the processor is connected to the memory through the bus, and when the second base station runs, the processor executes the computer-executable instructions stored in the memory, so that the access and mobility management function component executes the method for obtaining the data radio bearer identifier according to any one of the above-mentioned second aspects.

[0043] In a tenth aspect, an embodiment of the present application provides a computer-readable storage medium for storing computer software instructions used by the above-mentioned second base station. When it runs on a computer, it enables the computer to execute the method for obtaining the data radio bearer identifier according to any one of the above-mentioned second aspects.

[0044] In an eleventh aspect, an embodiment of the present application provides a computer program product containing instructions. When it runs on a computer, it enables the computer to execute the method for obtaining the data radio bearer identifier according to any one of the above-mentioned second aspects.

[0045] In a twelfth aspect, an embodiment of the present application provides a communication system, including the first base station described in the fourth aspect and the second base station described in the eighth aspect.

[0046] In the method for obtaining the data radio bearer identifier and the base station according to the embodiment of the present application, the first base station sends a first message to the second base station to request to add a DRB, the second base station feeds back a second message to the first base station, and the first base station can obtain the identifier of the DRB that the first base station can use according to the second message. The first base station uses the identifier of the DRB to add 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 enabling the first base station to add the DRB according to its own radio resource management strategy and network conditions, and reconfigure the mapping relationship between the QoS flow and the DRB, making the setting of the DRB more flexible and effective. BRIEF DESCRIPTION OF THE DRAWINGS

[0047] Figure 1 It is a schematic diagram of a QoS architecture of the present application;

[0048] Figure 2A It is a schematic diagram of the control plane of a dual-connection architecture of the present application;

[0049] Figure 2B It is a schematic diagram of the user plane of a dual-connection architecture of the present application;

[0050] Figure 3 It is a flowchart of a method for obtaining a DRB identifier of the present application;

[0051] Figure 4A Schematic diagram of QoS flow transfer in a dual-connection architecture;

[0052] Figure 4B Schematic diagram of DRB transfer in a dual-connection architecture;

[0053] Figure 5 Flowchart of another method for obtaining DRB identification in this application;

[0054] Figure 6 Flowchart of yet another method for obtaining DRB identification in this application;

[0055] Figure 7 Flowchart of yet another method for obtaining DRB identification in this application;

[0056] Figure 8 Flowchart of yet another method for obtaining DRB identification in this application;

[0057] Figure 9 Flowchart of yet another method for obtaining DRB identification in this application;

[0058] Figure 10 Flowchart of yet another method for obtaining DRB identification in this application;

[0059] Figure 11 Flowchart of yet another method for obtaining DRB identification in this application;

[0060] Figure 12 Flowchart of yet another method for obtaining DRB identification in this application;

[0061] Figure 13 Flowchart of yet another method for obtaining DRB identification in this application;

[0062] Figure 14 Flowchart of yet another method for obtaining DRB identification in this application;

[0063] Figure 15 Flowchart of yet another method for obtaining DRB identification in this application;

[0064] Figure 16 Flowchart of yet another method for obtaining DRB identification in this application;

[0065] Figure 17 Schematic diagram of the structure of a first base station in this application;

[0066] Figure 18 Schematic diagram of the structure of a second base station in this application. Detailed implementation manner

[0067] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the following will clearly and completely describe the technical solutions in the embodiments of this application with reference to the accompanying drawings in the embodiments of this application.

[0068] Figure 1 It is a schematic diagram of a QoS architecture of this application. As Figure 1 shown, the user plane function entity (UPF) on the 5G core network side (5G Core Network) will establish one or more PDU sessions for the UE. For each PDU session of each UE, the base station (gNB) of the 5G access network (NG-RAN) establishes one or more DRBs. The NG-RAN maps the 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 packets. Among them, the mapping from the QoS flow to the DRB is determined by the base station. As Figure 1 shown, the mapping relationship from the QoS flow to the DRB can be one-to-one or many-to-one. That is, as shown in 1, DRB1 carries QoS flow1 and QoS flow2, and DRB2 carries QoS flow3.

[0069] Figure 2A It is a schematic diagram of the control plane of a dual-connection architecture of this application. Figure 2B It is a schematic diagram of the user plane of a dual-connection architecture of this application. As Figure 2A and Figure 2BAs shown in the figure, the UE can send and receive data through the MN and SN. Among them, for the control plane: the Core Access and Mobility Management Function (AMF) is connected to the MN, the MN is connected to the SN, and the MN provides a control plane connection for the UE to the core network. Among them, NG-C is the control plane interface between the AMF and the MN, and Xn-C is the control plane interface between the MN and the SN. For the user plane: the UPF is respectively connected to the MN and the SN, the MN is connected to the SN, and the MN and the SN jointly provide a user plane connection for the UE to the core network. The SN can provide additional radio resources for the UE. Among them, NG-U is the user plane interface between the UPF and the MN, and between the UPF and the SN, and Xn-U is the user plane interface between the MN and the SN. In the dual-connection architecture, the MN can transfer the QoS flow of the UE it transmits or the DRB of the UE it transmits to the SN for transmission. The method for obtaining the DRB identifier in the embodiments of the present application can ensure the uniqueness of the DRB identifier in the dual-connection architecture, and enable the SN to determine the mapping relationship between its own QoS flow and the DRB, that is, the SN can add or release the DRB according to its own radio resource management policy and network conditions to reconfigure the mapping relationship between the QoS flow and the DRB, making the setting of the DRB in the dual-connection architecture more flexible and effective.

[0070] Figure 1 、 Figure 2A and Figure 2B All are described by taking the 5G network as an example. It should be noted that the method for obtaining the DRB identifier in the embodiments of the present application is also applicable to the LTE network. The MN and SN in the embodiments of the present application can specifically be eNB, or can also be the base stations of NG-RAN, that is, gNB.

[0071] The UE involved in the present application may include a handheld device with wireless communication functions, a vehicle-mounted device, a wearable device, a computing device, or other processing devices connected to a wireless modem, as well as various forms of user equipment (User Equipment, abbreviated as UE), mobile station (Mobile station, abbreviated as MS), terminal, terminal equipment, and so on. For the convenience of description, in the present application, it is simply referred to as user equipment or UE.

[0072] The DRB of the first base station of the present application, that is, the DRB of the SN, can be an SCG DRB or an SCG split DRB.

[0073] For the specific implementation manner of the method for obtaining the DRB identifier in the embodiments of the present application, reference can be made to the explanatory description in the following embodiments.

[0074] Figure 3 The flowchart of a method for obtaining a DRB identifier according to this application is as follows. As Figure 3 shown, this embodiment includes a user equipment, a first base station, and a second base station. The method of this embodiment may include:

[0075] Step 101: The first base station sends a first message to the second base station, and the second base station receives the first message sent by the first base station. This first message is used to request an increase in the DRB.

[0076] Among them, when the first base station determines that it is necessary to increase the DRB, it may send a first message to the second base station to request an increase in the DRB. After receiving this first message, the second base station learns that the first base station needs to increase the DRB.

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

[0078] Among them, 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 situation of the DRB identifier. This second message is used to indicate the identifier of one or more DRBs. The identifier of this one or more DRBs is the identifier of the DRB allocated by the second base station to the first base station, that is, the identifier of the DRB allowed by the second base station for the first base station to use. According to this second message, the first base station can learn the number of DRBs allowed by the second base station to increase for the first base station and the corresponding DRB identifiers, and then complete the increase of the DRB and the re - mapping between the QoS flow and the DRB.

[0079] Step 103: The first base station sends first information to the user equipment, and the user equipment receives the first information sent by the first base station. This first information includes DRB configuration information, and this DRB configuration information includes the identifier of at least one DRB.

[0080] Among them, after completing Step 101 and Step 102, the first base station may send the DRB configuration information to the user equipment. This DRB configuration information may include the identifier of one or more DRBs. That is, this DRB configuration information may include the identifier of the DRB with the increased SN. Of course, it can be understood that this DRB configuration information may also include the configuration information of the PDCP, RLC, and logical channels corresponding to this DRB, etc., which will not be elaborated here one by one.

[0081] Optionally, the first information may further include information on the mapping relationship between the uplink QoS flow and the at least one DRB. Specifically, in the downlink transmission scenario, the user equipment does not need to know the mapping relationship between the downlink QoS flow and the DRB. The user equipment can obtain the identifier of the DRB added by the first base station and the corresponding PDCP, RLC, and logical channel configuration information as described above. In the uplink transmission scenario, in addition to obtaining the identifier of the DRB added by the first base station, the user equipment also needs to obtain information on the mapping relationship between the uplink QoS flow and the DRB. Therefore, the first information may further include information on the mapping relationship between the uplink QoS flow and the at least one DRB. The mapping relationship between the uplink QoS flow and the at least one DRB may specifically be the mapping relationship between the identifier of the DRB and the identifier of the QoS flow. It can be understood that in one implementation, the information on the mapping relationship between the uplink QoS flow and the at least one DRB may specifically be the mapping relationship between the DRB added by the first base station and the uplink QoS flow. In another implementation, the information on the mapping relationship between the uplink QoS flow and the at least one DRB may specifically be the mapping relationship between all the DRBs of the first base station and the uplink QoS flow.

[0082] The first base station involved in the embodiments of the present application may specifically be a secondary base station, that is, Figure 2A and Figure 2B the SN shown, and the second base station may specifically be a master base station, that is, Figure 2A and Figure 2B the MN shown.

[0083] There are many different implementation manners for the specific form of the first message and the information specifically carried.

[0084] In one implementation, the first message may be a new type of message. When the second base station receives the first message, it can know that the first base station requests to add a DRB.

[0085] In another implementation, the first message may include any one or more of the following information: (1) indication information for requesting to add a DRB; (2) the number of DRBs requested to be added; (3) the identifier of the remapped QoS flow; (4) the packet information of the remapped QoS flow; (5) the index of the packet of the remapped QoS flow.

[0086] The above information of the first message will be specifically explained below.

[0087] In one implementation, the first message may include (1) indication information for requesting to add a DRB. The second base station determines that the first base station requests to add a DRB based on the indication information for requesting to add a DRB, and feeds back the identifiers of all currently available DRBs to the first base station.

[0088] In another implementable manner, the first message may include (2) a request to increase the number of DRBs. The second base station determines that the first base station requests to increase the number of DRBs based on the request to increase the number of DRBs, and feeds back the identifier of 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 requested to be increased.

[0089] In yet another implementable manner, the first message may include (3) the identifier of the remapped QoS flow. The remapped QoS flow is the QoS flow mapped to the DRB that needs to be increased at the SN. The second base station determines that the first base station requests to increase the number of DRBs based on the identifier of the remapped QoS flow, and feeds back the identifier of at least one DRB to the first base station. It should be noted that the second base station may also feed back to the first base station the identifier of the QoS flow that allows or rejects the remapping based on the identifier of the remapped QoS flow, or feedback the configuration information of the mapping relationship between the DRB and the QoS flow.

[0090] In still another implementable manner, the first message may include (4) the packet information of the remapped QoS flow. The remapped QoS flow is the QoS flow mapped to the DRB that needs to be increased at the SN. The second base station determines that the first base station requests to increase the number of DRBs based on the packet information of the remapped QoS flow, and feeds back the identifier of at least one DRB to the first base station. It should be noted that the second base station may also feed back to the first base station the configuration information of the mapping relationship between the DRB and the packet of the QoS flow based on the packet information of the remapped QoS flow. Wherein, the packet of the QoS flow specifically includes one or more QoS flows. The QoS flows within each packet may be mapped to the same newly added DRB. It can be understood that the number of packets may implicitly indicate the number of DRBs requested to be increased by the first base station.

[0091] In yet another implementable manner, the first message may include (5) the index of the packet of the remapped QoS flow. The remapped QoS flow is the QoS flow mapped to the DRB that needs to be increased at the SN. The second base station determines that the first base station requests to increase the number of DRBs based on the index of the packet of the remapped QoS flow, and feeds back the identifier of at least one DRB to the first base station. It should be noted that the second base station may also feed back to the first base station the configuration information of the mapping relationship between the index of the DRB and the packet of the QoS flow based on the index of the packet of the remapped QoS flow. Wherein, the index of the packet of the QoS flow specifically refers to the identifier used to indicate the packet including one or more QoS flows.

[0092] In yet another implementable manner, the first message may include (1) and (2);

[0093] In yet another implementable manner, the first message may include (1) and (3);

[0094] In another implementable manner, the first message may include (1) and (4);

[0095] In another implementable manner, the first message may include (1) and (5);

[0096] In another implementable manner, the first message may include (1), (2), and (3);

[0097] In another implementable manner, the first message may include (4) and (5);

[0098] In another implementable manner, the first message may include (1), (4), and (5);

[0099] After receiving the first message, the second base station learns, according to the information carried in the first message, that the first base station requests to add a DRB.

[0100] After learning that the first base station requests to add a DRB, the second base station may feedback a second message to the first base station to indicate the identifier of at least one DRB.

[0101] There are also many different implementable manners for the specific form of the second message and the information specifically carried.

[0102] The second message may specifically include any one or more of the following information: (1) the identifier of the available DRB; (2) the identifier of at least one DRB; (3) the identifier of the QoS flow allowed to be mapped to at least one DRB; (4) the identifier of the QoS flow refused to be mapped to at least one DRB; (5) the mapping relationship configuration information between the DRB and the QoS flow; (6) the mapping relationship configuration information between the group of the DRB and the QoS flow; (7) the mapping relationship configuration information between the index of the group of the DRB and the QoS flow.

[0103] According to the second message, the first base station can learn the number of DRBs allowed to be added by the second base station to the first base station and the identifiers of the corresponding DRBs.

[0104] Optionally, the first base station may also determine, according to the identifier of the QoS flow allowed to be mapped to at least one DRB in the above (3), the QoS flow allowed by the second base station to be mapped to the added DRB. It should be noted that when the second base station allows all QoS flows requested to be mapped by the first base station to be mapped to the added DRB, the second message may explicitly include an indication letter indicating that all QoS flows requested to be mapped can be remapped, or the second message may implicitly indicate that all QoS flows requested to be mapped can be remapped by not including any information about the QoS flow. Furthermore, the first base station can determine that the second base station allows all QoS flows requested to be remapped to be mapped to the added DRB.

[0105] The first base station may also determine, according to the identifier of the QoS flow mapped to at least one DRB as described above in (4), the QoS flow that the second base station refuses to map to the added DRB.

[0106] The first base station may also configure the mapping relationship between the DRB and the QoS flow according to the mapping relationship configuration information of the DRB and the QoS flow as described above in (5). Among them, the mapping relationship configuration information of the DRB and the QoS flow as described above in (5) may specifically be the mapping relationship between the identifier of the DRB and the identifier of the QoS flow.

[0107] The first base station may also determine the mapping relationship between the grouping of the DRB and the QoS flow according to the mapping relationship configuration information of the grouping of the DRB and the QoS flow as described above in (6). It should be noted that when the second message includes the mapping relationship configuration information of the grouping of the DRB and the QoS flow as described above in (6), the second message may further include the identifier of the QoS flow of each grouping, and the identifier of the QoS flow is used to indicate the QoS flow that is allowed to be mapped to the added DRB in the grouping. It can be understood that for a certain grouping that does not include the identifier of the QoS flow, it implicitly indicates that all QoS flows in the grouping can be mapped to the added DRB.

[0108] The first base station may also determine the mapping relationship between the index of the grouping of the DRB and the QoS flow according to the mapping relationship configuration information of the index of the grouping of the DRB and the QoS flow as described above in (7). On the basis that the second message includes the above (7), the second message may further include the identifier of the QoS flow of the grouping of the QoS flow that can be remapped to the added DRB. It can be understood that if a grouping of QoS flows in the second message does not include the identifier of the QoS flow, it can implicitly indicate that all QoS flows in the grouping of the QoS flow can be remapped.

[0109] The above first message and second message may specifically be flexibly set according to requirements to manage the identifier of the DRB in the dual-connection architecture and implement the flexible setting of the mapping relationship between the DRB and the QoS flow in the dual-connection architecture.

[0110] Optionally, before the above step 101, the method of the embodiment of the present application may further include: the first base station receives a third message sent by the second base station, and the second base station sends the third message to the first base station, and 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 first base station, or to request the first base station to add at least one DRB.

[0111] Specifically, the third message may include any one or more of the following information: the identifier of at least one QoS flow transferred to the first base station and the QoS parameters of the at least one QoS flow; the mapping relationship between the at least one QoS flow and the DRB; the indication information of the transfer type.

[0112] Wherein, the transfer type may include at least one of QoS flow transfer and DRB transfer.

[0113] The QoS flow transfer refers to the transfer of QoS flows in terms of QoS flow granularity, that is, the transferred QoS flows are partial QoS flows in at least one DRB configured by the second base station, rather than all QoS flows in the at least one DRB. For example, Figure 4A is a schematic diagram of QoS flow transfer in a dual-connection architecture, where Figure 4A the left side of is the schematic diagram before the transfer, Figure 4A the left side of is the intention after the transfer, as shown in the schematic diagram on the right side of Figure 4A Before the transfer, as shown in the schematic diagram on the right side of, DRB1 of the second base station transmits QoS flow 1, QoS flow 1 belongs to PDU session 1, DRB2 of the second base station transmits QoS flow 2, DRB3 of the second base station transmits QoS flow 3 (3 in the figure) and QoS flow 4, QoS flows 2, 3 and 4 belong to PDU session 2. The second base station may transfer QoS flow 4 to the first base station for transmission, as shown in Figure 4A the right side of. After the transfer, QoS flow 4 of PDU session 2 is transmitted by the DRB of the first base station, and the identifier of the DRB of the first base station uses the identifier of the DRB assigned by the second base station.

[0114] The DRB transfer refers to the transfer of QoS flows in terms of DRB granularity, that is, the transferred QoS flows are all QoS flows in at least one DRB configured by the second base station. For example, Figure 4B is a schematic diagram of DRB transfer in a dual-connection architecture, where Figure 4B the left side of is the schematic diagram before the transfer, Figure 4B the right side of is the intention after the transfer, as shown in Figure 4B the schematic diagram on the left side of. Before the transfer, DRB1 of the second base station transmits QoS flow 1, QoS flow 1 belongs to PDU session 1, DRB2 of the second base station transmits QoS flow 2, DRB3 of the second base station transmits QoS flow 3 (3 in the figure) and QoS flow 4, QoS flows 2, 3 and 4 belong to PDU session 2. The second base station may transfer DRB3 to the first base station for transmission, as shown in Figure 4BAs shown on the right side, after the transfer, QoS Flow 3 and QoS Flow 4 of PDU Session 2 are transmitted by the DRB of the first base station, and the identifier 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 DRB3 before the transfer can be used.

[0115] Take Figure 4A and Figure 4B as an example for further illustration. If the second base station transfers PDU Session 2 to the first base station for transmission, this transfer involves both QoS flow transfer and DRB transfer.

[0116] After the first base station accepts the above transfer from the second base station, if it is determined that DRBs need to be added to reconfigure the mapping between QoS flows and DRBs, subsequent steps 101 to 103 can be executed.

[0117] Among them, the indication information of the mapping relationship between the at least one QoS flow and DRB and the transfer type is included in the Radio Resource Control Information Container (RRC Container), and the Radio Resource Control Information Container (RRC Container) is included in the third message.

[0118] Optionally, one implementation of the above 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, and this Radio Resource Control reconfiguration message may include this first information.

[0119] Based on the implementation of the above step 103, the method for obtaining 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. The fourth message includes any one or more of the following information: (1) the identifier of the available DRB; (2) the identifier of the DRB selected by the first base station; (3) the mapping relationship between the QoS flows configured by the first base station and the DRB.

[0120] 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 the identifier of the currently available DRB fed back by the second base station after receiving the first message sent by the first base station, while the identifier of the available DRB in the fourth message is the identifier of the DRB obtained after the first base station selects the identifier of the added DRB from the identifier of the available DRB in the first message and updates the identifier of the available DRB in the first message.

[0121] Optionally, another implementation of step 103 above 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. The fifth message may include the first information, and the fifth message is used for the second base station to obtain the first information and carry the first information in the radio resource control reconfiguration message sent to the user equipment.

[0122] Wherein, the first information may specifically be included in a radio resource control information container (RRC Container), and the radio resource control information container is included in the fifth message.

[0123] It should be noted that the second base station sends a second message to the first base station to indicate permission for the first base station to increase the DRB. When the second base station does not permit the first base station to increase the DRB, the second base station may send a rejection message to the first base station to indicate that the request of the first base station to increase the DRB is rejected.

[0124] In this embodiment, the first base station sends a first message to the second base station to request an increase in the DRB, the second base station feeds back a second message to the first base station, the first base station can obtain the identifier of the DRB that the first base station can use according to the second message, the first base station uses the identifier of the DRB to increase the DRB, and the first base station sends the identifier of the increased DRB to the user equipment, thereby ensuring the uniqueness of the ID of the DRB, and enabling the first base station to increase the DRB according to its own radio resource management strategy and network conditions, and reconfigure the mapping relationship between the QoS flow and the DRB, making the setting of the DRB more flexible and effective.

[0125] The following uses several specific embodiments to Figure 3 detail the technical solutions of the method embodiments shown.

[0126] Figure 5 is a flowchart of another method for obtaining the DRB identifier in this application. In this embodiment, the first base station is the SN, and the second base station is the MN. As Figure 5 shown, the method of this embodiment may include:

[0127] Step 201, the MN sends an SN addition request message to the SN.

[0128] Specifically, when the MN determines to request the SN to transmit some QoS flows of the UE, step 201 may be executed. The SN addition request message may include the identifier of the QoS flow that the MN requests the SN to transmit and the corresponding QoS parameters. An RRC Container may also be included in the SN addition request message, and the mapping relationship configuration information between the identifier of the QoS flow configured by the MN to be transferred to the SN for transmission and the DRB identifier is included in the RRC Container.

[0129] Among them, the SN addition request message can be Figure 3 a specific implementation of the third message in the illustrated embodiment.

[0130] Step 202: The SN sends an SN addition request confirmation message to the MN.

[0131] Specifically, when the SN accepts the above SN addition request message from the MN, step 202 can be executed. Among them, after receiving the SN addition request message sent by the MN, the SN configures according to the mapping relationship of the QoS parameters, QoS flow identifiers, and DRB identifiers provided by the MN. In the SN addition request confirmation message, the identifier of the QoS flow that the SN agrees to admit can be included. In addition, in the SN addition request confirmation message, an RRC Container can also be included. The RRC Container includes the radio resource configuration information and radio bearer configuration information of the SN.

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

[0133] The RRC connection reconfiguration message carries the information in the RRC Container in the above SN addition request confirmation message.

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

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

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

[0137] The purpose of the SN initiating the SN modification process is to trigger the addition of a DRB. More specifically, this step is to request the MN to allocate a DRB ID. In this step, the SN modification requirement message can be Figure 3 a specific implementation of the first message in the illustrated embodiment. Specifically, for the detailed explanation of step 206, reference can be made to Figure 3 the explanation of step 101 in the illustrated embodiment, which will not be elaborated here. Among them, for the detailed explanation of the first message, reference can also be made to Figure 3 the explanation of the illustrated embodiment, which will not be elaborated here.

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

[0139] In this embodiment, the SN modification confirmation message can be Figure 3A specific implementation of the second message in the illustrated embodiment. Specifically, for the specific explanation of step 207, reference can be made to Figure 3 the explanation of step 102 in the illustrated embodiment, which will not be elaborated here.

[0140] Step 208, the SN initiates an SN modification process, and the SN sends an SN modification requirement message to the MN.

[0141] The purpose of the SN initiating the SN modification process is to trigger the addition of a DRB. More specifically, this step is to configure the added DRB. In this step, the SN modification requirement message can be Figure 3 the fifth message in the illustrated embodiment. Among them, for the specific explanation of the fifth message, reference can be made to Figure 3 the specific explanation of the illustrated embodiment, which will not be elaborated here. That is, the fifth message can include the first information. The first information can include the configuration information of the added DRB, etc. Specifically, the fifth message can include an RRC Container, and the first information is carried in the RRC Container, that is, the configuration information of the added DRB is carried. The configuration information of the added DRB can include the identifier of the DRB added by the SN. Of course, it can be understood that the configuration information of the added DRB can also include the configuration information of the PDCP, RLC, and logical channels corresponding to the added DRB, etc.

[0142] Step 209, the MN sends an RRC connection reconfiguration message to the UE. The RRC connection reconfiguration message includes the first information.

[0143] Specifically, the MN can extract the first information in the RRC Container in the SN modification requirement message received in step 208 and set the first information in the RRC connection reconfiguration message.

[0144] Step 210, the MN receives the RRC connection reconfiguration complete message sent by the UE.

[0145] Step 211, the MN sends an SN modification confirmation message to the SN.

[0146] In this embodiment, for the addition request message of the MN, the SN first accepts the request of the MN, completes the configuration according to the configuration information in the addition request message, and then the SN initiates a DRB addition process by sending an SN modification requirement message, so as to ensure the uniqueness of the DRB ID, and realize that the SN can add a DRB according to its own radio resource management strategy and network conditions to reconfigure the mapping relationship between the QoSflow and the DRB, making the setting of the DRB more flexible and effective.

[0147] Figure 6Flow chart of another method for obtaining DRB identifier in this application. The difference between this embodiment and the embodiment shown in Figure 5 is that the SN directly sends an RRC connection reconfiguration message to the UE. As shown in Figure 6 , the method of this embodiment may include:

[0148] Step 301, the MN sends an SN addition request message to the SN.

[0149] Step 302, the SN sends an SN addition request confirmation message to the MN.

[0150] Among them, for the specific explanations of Step 301 and Step 302, reference can be made to the explanations of Step 201 and Step 202 in the embodiment shown in Figure 5 , which will not be elaborated here.

[0151] Step 303, the SN sends an RRC connection reconfiguration message to the UE.

[0152] Among them, the RRC connection reconfiguration message may carry the mapping relationship between the uplink QoS flow and the DRB and the relevant configuration information of the DRB, that is, the ID of the DRB, the PDCP, RLC and logical channel configuration information of the DRB.

[0153] Step 304, the SN receives the RRC connection reconfiguration complete message sent by the UE.

[0154] Step 305, the SN sends an SN modification requirement message to the MN.

[0155] In this step, the SN modification requirement message may be Figure 3 a specific implementation manner of the first message in the embodiment shown in

[0156] Step 306, the MN sends an SN modification confirmation message to the SN.

[0157] In this step, the SN modification confirmation message may be Figure 3 a specific implementation manner of the second message in the embodiment shown in

[0158] Among them, for the specific explanations of Step 305 and Step 306, reference can be made to Step 206 and Step 207 in the embodiment shown in Figure 5 , which will not be elaborated here.

[0159] Step 307, the SN sends an RRC connection reconfiguration message to the UE.

[0160] The RRC connection reconfiguration message includes the first information.

[0161] For the specific explanation of the first information, reference can be made to Figure 3The explanation of the illustrated embodiment will not be elaborated here.

[0162] Step 308, the UE sends an RRC connection reconfiguration complete message to the SN.

[0163] In this embodiment, for the MN addition request message, the SN first accepts the request of the MN, completes the configuration according to the configuration information in the addition request message, and then the SN initiates a DRB addition process by sending an SN modification requirement message, thereby ensuring the uniqueness of the DRB ID, enabling the SN to increase the DRB according to its own radio resource management strategy and network conditions, reconfiguring the mapping relationship between the QoS flow and the DRB, and making the setting of the DRB more flexible and effective.

[0164] Figure 5 and Figure 6 In the illustrated embodiment for the MN addition request message, the SN always first accepts the SN addition request message sent by the MN, completes the configuration according to the configuration information in the SN addition request message, and then the SN initiates a DRB addition process to the MN, that is, sends a first message, and Figure 5 and Figure 6 different from the illustrated embodiment, in the following two embodiments, for the SN addition request message sent by the MN, the SN can directly initiate a DRB addition process, that is, send a first message, and the specific explanation can be referred to the following embodiments.

[0165] Figure 7 is a flowchart of another method for obtaining a DRB identifier of the present application. As Figure 7 shown, the method of this embodiment may include:

[0166] Step 401, the MN sends an SN addition request message to the SN.

[0167] Among them, the specific explanation of step 401 can be referred to the specific explanation of step 301, which will not be elaborated here.

[0168] Step 402, the SN initiates an SN modification process and sends an SN modification requirement message to the MN.

[0169] Among them, after receiving the SN addition request message sent by the MN, if the SN needs to increase the DRB, the SN initiates an SN modification process and sends an SN modification requirement message to the MN. The SN modification requirement message in this step can be Figure 3 a specific implementation manner of the first message in the illustrated embodiment, that is, the purpose of the SN initiating the SN modification process is to trigger the addition of the DRB. More specifically, this step is to request the MN to allocate a DRB ID. The specific explanation of the first message can be referred to Figure 3The explanation of the illustrated embodiment will not be repeated here. That is, the SN can determine the DRB to be added according to the configuration information in the SN addition request message.

[0170] Step 403, the MN sends an SN modification confirmation message to the SN.

[0171] In this step, the SN modification confirmation message can be Figure 3 a specific implementation manner of the second message of the illustrated embodiment. For the specific explanation of the second message, reference can be made to Figure 3 the explanation of the illustrated embodiment, which will not be repeated here.

[0172] Step 404, the SN sends an SN addition request confirmation message to the MN.

[0173] Among them, for the specific explanation of step 404, reference can be made to the specific explanation of step 202, which will not be repeated here. It should be noted that the SN addition request confirmation message in step 404 includes the configuration information of the added DRB.

[0174] Step 405, the MN sends an RRC connection reconfiguration message to the UE.

[0175] Step 406, the MN receives the RRC connection reconfiguration complete message sent by the UE.

[0176] Step 407, the MN sends an SN reconfiguration complete message to the SN.

[0177] In this embodiment, for the addition request message of the MN, the SN determines the DRB to be added according to the configuration information in the addition request message. The DRB addition process can be initiated by sending an SN modification requirement message, so as to ensure the uniqueness of the DRB ID, and enable the SN to add a DRB according to its own radio resource management policy and network conditions, so as to reconfigure the mapping relationship between the QoS flow and the DRB, making the setting of the DRB more flexible and effective.

[0178] Figure 8 It is a flowchart of another method for obtaining the DRB identifier of the present application. The difference between this embodiment and Figure 7 the illustrated embodiment is that the SN directly sends an RRC connection reconfiguration message to the UE. As Figure 8 shown, the method of this embodiment may include:

[0179] Step 501, the MN sends an SN addition request message to the SN.

[0180] Among them, for the specific explanation of step 501, reference can be made to the specific explanation of step 301, which will not be repeated here.

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

[0182] Among them, after the SN receives the add request message sent by the MN, if the SN needs to add a DRB, the SN initiates an SN modification process and sends an SN modification requirement message to the MN. The SN modification requirement message in this step can be Figure 3 A specific implementation manner of the first message in the illustrated embodiment, that is, the purpose of the SN initiating the SN modification process is to trigger the addition of a DRB. More specifically, this step is to request the MN to allocate a DRB ID. For the specific explanation of this first message, reference can be made to Figure 3 The explanation of the illustrated embodiment, which will not be elaborated here.

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

[0184] In this step, the SN modification confirmation message can be Figure 3 A specific implementation manner of the second message in the illustrated embodiment. Among them, for the specific explanation of this second message, reference can be made to Figure 3 The explanation of the illustrated embodiment, which will not be elaborated here.

[0185] Step 504: The SN sends an SN add request confirmation message to the MN.

[0186] Among them, for the specific explanation of step 504, reference can be made to the specific explanation of step 404, which will not be elaborated here.

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

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

[0189] Among them, for the specific explanations of step 505 and step 506, reference can be made to step 307 and step 308, which will not be elaborated here.

[0190] In this embodiment, for the add request message of the MN, the SN determines that a DRB needs to be added according to the configuration information in the add request message. The DRB addition process can be initiated by sending an SN modification requirement message, so as to ensure the uniqueness of the DRB ID, and enable the SN to add a DRB according to its own radio resource management strategy and network conditions, so as to reconfigure the mapping relationship between the QoS flow and the DRB, making the setting of the DRB more flexible and effective.

[0191] Figure 9 It is a flowchart of another method for obtaining a DRB identifier in this application. This embodiment is the same as Figure 8The difference between the illustrated embodiments is that the MN sends the DRB ID of the added DRB to the SN through an SN modification request message, as Figure 9 shown. The method of this embodiment may include:

[0192] Step 601, the MN sends an SN addition request message to the SN.

[0193] Step 602, the SN sends an SN addition request confirmation message to the MN.

[0194] Step 603, the MN sends an RRC connection reconfiguration message to the UE.

[0195] Step 604, the MN receives the RRC connection reconfiguration complete message sent by the UE.

[0196] Step 605, the MN sends an SN reconfiguration complete message to the SN.

[0197] Step 606, the SN initiates an SN modification process, and the SN sends an SN modification requirement message to the MN.

[0198] If the SN needs to add a DRB, the SN initiates an SN modification process and sends an SN modification requirement message to the MN. The SN modification requirement message in this step may be Figure 3 a specific implementation manner of the first message of the illustrated embodiment. That is, the purpose of the SN initiating the SN modification process is to trigger the addition of a DRB. More specifically, this step is to request the MN to allocate a DRB ID.

[0199] Step 607, the MN sends an SN modification request message to the SN.

[0200] In this step, the SN modification request message may be Figure 3 a specific implementation manner of the second message of the illustrated embodiment. For the specific explanation of the second message, reference may be made to Figure 3 the explanation of the illustrated embodiment, which will not be elaborated here. That is, the DRB ID of the added DRB is sent to the SN through the SN modification request message.

[0201] Step 608, the SN sends an SN modification request confirmation message to the MN.

[0202] In this step, the SN modification request confirmation message may be Figure 3 a specific implementation manner of the fifth message of the illustrated embodiment. For the specific explanation of the second message, reference may be made to Figure 3 the explanation of the illustrated embodiment, which will not be elaborated here.

[0203] Step 609, the MN sends an RRC connection reconfiguration message to the UE. The RRC connection reconfiguration message includes first information.

[0204] For the specific explanation of this first piece of information, reference can be made to Figure 3 the explanation of the illustrated embodiments, which will not be elaborated here.

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

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

[0207] In this embodiment, for the MN addition request message, the SN first accepts the request of the MN, completes the configuration according to the configuration information in the addition request message, and then the SN initiates the DRB addition process by sending an SN modification requirement message, thereby ensuring the uniqueness of the DRB ID, enabling the SN to add DRBs according to its own radio resource management strategy and network conditions to reconfigure the mapping relationship between the QoSflow and the DRB, making the setting of the DRB more flexible and effective.

[0208] Figure 10 It is a flowchart of another method for obtaining the DRB identifier of the present application. As Figure 10 shown, the method of this embodiment may include:

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

[0210] Step 702: The SN sends an SN addition request confirmation message to the MN.

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

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

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

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

[0215] If the SN needs to add a DRB, the SN initiates an SN modification process and sends a first message to the MN. That is, the purpose of the SN initiating the SN modification process is to trigger the addition of the DRB. More specifically, this step is to request the MN to allocate a DRB ID. In this step, the SN modification requirement message may be Figure 3 a specific implementation manner of the first message in the illustrated embodiment.

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

[0217] In this step, the SN modification confirmation message can be Figure 3 a specific implementation of the second message of the illustrated embodiment.

[0218] For the specific explanations of steps 701 to 708, reference can be made to Figure 5 the specific explanations of steps 201 to 207 of the illustrated embodiment, which will not be elaborated here.

[0219] In step 708, the SN sends an RRC connection reconfiguration message to the UE. The RRC connection reconfiguration message includes first information.

[0220] For the specific explanations of the first information, reference can be made to Figure 3 the explanations of the illustrated embodiment, which will not be elaborated here.

[0221] In step 709, the SN receives the RRC connection reconfiguration complete message sent by the UE.

[0222] In this embodiment, for the MN addition request message, the SN first accepts the request of the MN, completes the configuration according to the configuration information in the addition request message, and then the SN initiates a DRB addition process by sending an SN modification requirement message, so as to ensure the uniqueness of the DRB ID, and enable the SN to add DRBs according to its own radio resource management strategy and network conditions to reconfigure the mapping relationship between the QoS flow and the DRB, making the setting of the DRB more flexible and effective.

[0223] Figure 11 is a flowchart of another method for obtaining a DRB identifier of the present application. As Figure 11 shown, the method of this embodiment may include:

[0224] In step 801, the MN sends an SN addition request message to the SN.

[0225] The addition request message includes the QoS flow ID of the QoS flow that the MN requests the SN to transmit and the corresponding QoS parameters. In addition, in the RRC Container of the addition request message, the mapping relationship between the QoS flow ID of the QoS flow configured by the MN to be transferred to the SN for transmission and the DRB ID is also included.

[0226] In step 802, the SN sends an SN addition request confirmation message to the MN.

[0227] In this embodiment, after receiving the SN addition request message sent by the MN, the SN configures according to the mapping relationship between the QoS flow ID and the DRB ID provided by the MN. The addition request confirmation message contains an RRC Container. The RRC Container contains the radio resource configuration and radio bearer configuration of the SN.

[0228] Step 803, the MN sends an RRC connection reconfiguration message to the UE.

[0229] The MN sends the information in the RRC Cotainer in the addition request confirmation message replied by the SN to the UE through the RRC connection reconfiguration message.

[0230] Step 804, the MN receives the RRC connection reconfiguration complete message sent by the UE.

[0231] Step 805, the MN sends an SN reconfiguration complete message to the SN.

[0232] Step 806, the SN initiates an SN modification process, and the SN sends an SN modification requirement message to the MN

[0233] Step 807, the MN sends an SN modification confirmation message to the SN.

[0234] For the specific explanations of steps 806 to 807, reference can be made to steps 706 and 707, which will not be elaborated here.

[0235] Step 808, the SN sends an RRC connection reconfiguration message to the UE.

[0236] Among them, after receiving 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, and the RRC connection reconfiguration message includes the configuration information of the updated mapping relationship between the QoS flow transmitted by the SN and the DRB.

[0237] Step 809, the SN receives the RRC connection reconfiguration complete message sent by the UE.

[0238] Step 810, the SN sends an SN configuration update message to the MN.

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

[0240] In this embodiment, during the DRB addition process, the uniqueness of the DRB ID can be ensured, enabling the SN to add a DRB according to its own radio resource management policy and network conditions to reconfigure the mapping relationship between the QoS flow and the DRB, making the DRB setting more flexible and effective.

[0241] Figure 12 It is a flowchart of another method for obtaining a DRB identifier of this application. As Figure 12 shown, the method of this embodiment may include:

[0242] Step 901, the MN sends an SN addition request message to the SN.

[0243] This addition request message includes the QoS flow ID of the QoS flow that the MN requests the SN to transmit and the corresponding QoS parameters. Additionally, the available DRB ID is also included in the RRC Container in this addition request message.

[0244] Step 902, the SN sends an SN addition request confirmation message to the MN.

[0245] Among them, if the SN accepts this addition request message, the SN determines the selected DRB ID and the mapping relationship between the DRB ID and the QoS flow ID of the QoS flow that the MN requests to be transmitted by the SN according to the available DRB ID provided by the MN. The SN replies with an addition request confirmation message, and this addition request confirmation message contains the remaining available DRB ID or the DRB ID occupied by the SN.

[0246] Step 903, the SN sends an RRC connection reconfiguration message to the UE.

[0247] This RRC connection reconfiguration message contains the updated configuration information of the mapping relationship between the QoS flow transmitted by the SN and the DRB.

[0248] Step 904, the SN receives the RRC connection reconfiguration complete message sent by the UE.

[0249] Step 905, the SN initiates an SN modification process, and the SN sends an SN modification requirement message to the MN

[0250] Step 906, the MN sends an SN modification confirmation message to the SN.

[0251] Among them, for the specific explanations of steps 906 to 907, reference can be made to steps 706 and 707, which will not be elaborated here.

[0252] Step 907, the SN sends an RRC connection reconfiguration message to the UE.

[0253] Among them, 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, and the RRC connection reconfiguration message includes the configuration information of the updated mapping relationship between the QoS flow and the DRB transmitted by the SN.

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

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

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

[0257] In this embodiment, during the DRB addition process, the uniqueness of the DRB ID can be ensured, enabling the SN to add DRBs according to its own radio resource management strategy and network conditions to reconfigure the mapping relationship between the QoS flow and the DRB, making the DRB settings more flexible and effective.

[0258] Figure 13 It is a flowchart of another method for obtaining DRB identification in this application. As Figure 13 shown, this embodiment includes a user equipment, a first base station, and a second base station. The difference between this embodiment and the above embodiments is that in this embodiment, the first base station requests to release the DRB according to its own needs. The method of this embodiment may include:

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

[0260] Among them, when the first base station determines that it needs to reduce the DRB, it can send a first message to the second base station to request to release the DRB. After receiving the first message, the second base station learns the identification of the DRB that the first base station needs to release.

[0261] Among them, the first message may specifically include any one or more of the following: the identification of at least one DRB to be released; the mapping relationship between the DRBs configured by the first base station and the QoS flows.

[0262] Step 1002: The first base station receives a second message sent by the second base station, and the second base station receives the second message sent by the first base station. The second message is used to confirm to the first base station that it has received the first message.

[0263] Step 1003: The first base station sends the first information to the user equipment, and the user equipment receives the first information sent by the first base station. The first information includes the identifiers of the at least one DRB.

[0264] Among them, the identifier of the DRB included in the first information is the identifier of the released DRB.

[0265] It can be understood that the above second message is used to feedback to the first base station to confirm the acceptance of the release request. The second base station can also send a release rejection message to reject the release request of the first base station.

[0266] In this embodiment, the first base station sends a first message to the second base station to request the release of the DRB. The second base station sends a second message to the first base station. The first base station can determine the DRB that can be released according to the second message. The first base station sends the identifier of the released DRB to the user equipment, thereby ensuring the uniqueness of the DRB ID. The first base station can add a DRB according to its own radio resource management strategy and network conditions to reconfigure the mapping relationship between the QoS flow and the DRB, making the DRB setting more flexible and effective.

[0267] Figure 14 It is a flowchart of another method for obtaining the DRB identifier of the present application. As Figure 14 shown, this embodiment includes a user equipment, a first base station, and a second base station. The method of this embodiment may include:

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

[0269] Specifically, the first base station sends the first message after generating the identifier of the currently available DRB by updating the DRB identifier. The reasons for the DRB identifier update include at least one of adding a DRB and releasing a DRB.

[0270] Among them, when the reason for the DRB identifier update includes adding a DRB, the identifier of the currently available DRB does not include the identifier of the added DRB.

[0271] When the reason for the DRB identifier update includes releasing a DRB, the identifier of the currently available DRB includes the identifier of the released DRB.

[0272] That is, the first base station needs to inform the second base station through the first message after the DRB identifier is updated.

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

[0274] Among them, the configuration information of the added DRB may further include other configuration information, such as the configuration of the PDCP entity, RLC entity, and logical channel corresponding to the DRB, etc.

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

[0276] One implementation manner: The first base station is a secondary base station, and the second base station is a primary base station; or,

[0277] Another implementation manner: The first base station is a primary base station, and the second base station is a secondary base station.

[0278] Optionally, the first message may include any one or more of the following information: the identifier 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 configured by the first base station and the DRB.

[0279] Specifically, when the first message includes the identifier of the currently available DRB, the second base station obtains the identifier of the currently available DRB according to the first message.

[0280] 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.

[0281] 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.

[0282] When the first message includes the mapping relationship between the QoS flow configured by the first base station and the DRB, 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 configured by the first base station and the DRB, and 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.

[0283] Optionally, before the above step 801 or after the above step 802, the method may further include: the first base station receives a 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 message is used to indicate the identifier of the available DRB; the first base station performs DRB identifier update on the identifier of the available DRB to generate the identifier of the currently available DRB.

[0284] Specifically, the second base station maintains the identifier of the available DRB, and the second base station indicates the identifier of the available DRB to the first base station through the second message. The first base station selects the identifier of the DRB from the identifier of the available DRB for the added DRB, and updates the identifier of the DRB maintained by the first base station to generate the identifier of the currently available DRB, and notifies the second base station of the updated result through the first message.

[0285] Optionally, the second message includes any one or more of the following information: the identifier 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.

[0286] Specifically, both the first base station and the second base station maintain the identifier of the available DRB. After the usage status of the identifier of the DRB on either side is updated, it is necessary to notify the other party of the updated result. The way to notify the other party of the updated result can be to directly notify the identifier of the available DRB, or to notify the other party of the identifier of the DRB it occupies or releases, or the mapping relationship between the QoS flow and the DRB it configures, and the other party determines the updated result based on the identifier of the available DRB maintained by itself and the above information.

[0287] Optionally, when the first base station is a secondary base station and the second base station is a primary base station, the method may further include that 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 to request the first base station to add at least one QoS flow, or to request to transfer at least one DRB to the first base station, or to request the first base station to add at least one DRB;

[0288] The third message includes any one or more of the following information: the identifier of at least one QoS flow transferred to the first base station and the QoS parameters of the at least one QoS flow; the mapping relationship between the at least one QoS flow and the DRB; the indication information of the transfer type; the identifier of the available DRB.

[0289] Wherein, the transfer type includes at least one of QoS flow transfer and DRB transfer.

[0290] The QoS flow transfer refers to the transfer of QoS flows in terms of QoS flow granularity, that is, the transferred QoS flows are part of the QoS flows in at least one DRB configured by the second base station, rather than all QoS flows in the at least one DRB.

[0291] The DRB transfer refers to the transfer of QoS flows in terms of DRB granularity, that is, the transferred QoS flows are all QoS flows in at least one DRB configured by the second base station.

[0292] After the first base station accepts the above transfer, if it is determined that a DRB needs to be added to reconfigure the mapping between QoS flows and DRBs, subsequent steps 801 to 802 can be executed.

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

[0294] An implementable manner of the above step 802 is that the first base station sends a radio resource control reconfiguration message to the user equipment, and the radio resource control reconfiguration message includes this first information.

[0295] Another implementable manner of the above step 803 is that the first base station sends a fourth message to the second base station, the fourth message includes this first information, and the fourth message is used for the second base station to obtain this first information and carry the first information in the radio resource control reconfiguration message sent to the user equipment.

[0296] Optionally, the fourth message may further include second information, and the second information is used to indicate that the reason for sending the fourth message is to change the mapping relationship between QoS flows and DRBs. Specifically, the fourth message includes second information and an RRC Container, and the RRC Container includes this first information. Then, when the second base station receives the fourth message, it can first check the second information. The fact that the fourth message carries this second information indicates that the first base station has modified the mapping relationship between QoS flows and DRBs. Then, the second base station obtains the first information from the RRC Container according to this first information. If the second information is not carried in the fourth message, the second base station may not execute the step of obtaining information from the RRC Container and directly transparently transmit the RRC Container to the UE.

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

[0298] 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. The first base station sends first information to the user equipment, and the first information may include at least one of the configuration information of the added DRB and the identifier of the released DRB, thereby ensuring the uniqueness of the DRB ID, enabling the first base station to add DRBs according to its own radio resource management strategy and network conditions, and reconfiguring the mapping relationship between the QoS flow and the DRB, making the DRB setting more flexible and effective.

[0299] The following uses two specific embodiments to Figure 14 specifically explain the illustrated embodiment.

[0300] Figure 15 is a flowchart of another method for obtaining the DRB identifier of the present application. As Figure 15 shown, this embodiment includes a UE, an MN, and an SN. The method of this embodiment may include:

[0301] Step 1201, the MN sends an SN addition request message to the SN.

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

[0303] Optionally, the SN addition request message may further include (3) the DRB ID assigned by the MN to at least one QoS flow transferred by the SN for transmission by the SN, and the mapping relationship between the QoS flow ID and the DRB ID.

[0304] Among them, (2) the currently available DRB ID may be carried in an RRC Container. If the content (3) is included in the addition request message, the content (3) may also be included in an RRC Container.

[0305] Step 1202, if the SN accepts the addition request, the SN replies with an SN addition request confirmation message.

[0306] In this embodiment, after the SN receives the SN addition request message sent by the MN, if the addition request message includes the above content (3), the SN configures according to the mapping relationship between the QoS flow ID and the DRB ID provided by the MN. Otherwise, the SN selects the DRB ID by itself according to the above content (1) and (2), and determines the mapping relationship between the DRB ID and the QoS flow ID. In the addition request confirmation message, the QoS flow ID of the QoS flow that the SN agrees to admit may be included. In the addition request confirmation message, an RRC Container may also be included. The RRC Container includes the radio resource configuration information of the SN, the radio bearer configuration information, and the mapping relationship between the DRB and the QoS flow.

[0307] Step 1203, the MN sends an RRC connection reconfiguration message to the UE, and the RRC connection reconfiguration message includes the information in the RRC Container in the addition request confirmation message replied by the SN.

[0308] Step 1204, the MN receives the RRC connection reconfiguration complete message sent by the UE.

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

[0310] Step 1206, the SN sends an SN modification requirement message to the MN. The modification request message is used for the SN to initiate the modification process of the DRB.

[0311] Among them, the modification requirement message is Figure 10 the first message of the embodiment shown.

[0312] Specifically, when the SN reconfigures the mapping relationship between the QoS flow and the DRB it bears and needs to add or release the DRB, the SN initiates the SN modification process and sends a modification requirement message to the MN. If it is necessary to add a DRB, before the SN initiates the SN modification process, the SN selects the DRB ID by itself according to the available DRB IDs provided by the MN, and determines the mapping relationship between the new QoS flow and the DRB.

[0313] The specific information included in the modification requirement message can be seen in Figure 10 the explanation of the specific information of the first message of the embodiment shown, which will not be elaborated here.

[0314] Optionally, the SN may also carry in the modification request message the reason for sending the modification request message. Specifically, the reason information of the modification request message may be set to QoS flow remapping, that is, changing the mapping relationship between the QoS flow and the DRB, so as to notify the MN of the reason for initiating the modification process. The MN may determine the remaining available DRB IDs according to the DRB ID included in the modification request message, and whether the DRB ID allocated by the SN conflicts with the DRB ID allocated by the MN.

[0315] 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 information in the RRC Container in the modification request message sent by the SN.

[0316] It can be understood that if the DRB IDs allocated by the MN and the SN conflict, the MN sends a modification rejection message to the SN.

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

[0318] Step 1209: The MN sends an SN modification confirmation message to the SN. The SN modification confirmation message is a message on the Xn interface or the X2 interface between the MN and the SN.

[0319] Step 1210: The MN updates the available DRB IDs maintained by itself.

[0320] Step 1211: The MN sends an MN configuration update message to the SN. The MN configuration update message includes the updated available DRB IDs of the MN.

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

[0322] 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. In the modification request message, the updated available DRB IDs of the MN are included.

[0323] The configuration update message may also be a newly defined message.

[0324] This embodiment can ensure the uniqueness of the DRB IDs, enabling the SN to add DRBs according to its own radio resource management policy and network conditions to reconfigure the mapping relationship between the QoS flow and the DRB, making the DRB setting more flexible and effective.

[0325] Figure 16 This is a flowchart of another method for obtaining a DRB identifier in this application. As Figure 16 shown, this embodiment includes a UE, an MN, and an SN. The method of this embodiment may include:

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

[0327] Step 1302: If the SN accepts the addition request, the SN replies with an SN addition request confirmation message.

[0328] Among them, for the specific implementation manners of steps 1001 to 1002, reference can be made to the specific explanations of steps 901 to 902, which will not be elaborated here.

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

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

[0331] Step 1305: The SN updates the available DRB ID.

[0332] Specifically, when the SN reconfigures the mapping relationship between the QoS flow and the DRB it bears and needs to add or release a DRB, the SN initiates an SN modification process and sends a modification requirement message to the MN. If a DRB needs to be added, before the SN initiates the SN modification process, the SN selects a DRB ID by itself according to the available DRB ID provided by the MN and determines the new mapping relationship between the QoS flow and the DRB.

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

[0334] 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 the SN adding a DRB and the SN releasing a DRB.

[0335] 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 requirement message to the MN. The modified request message contains the available DRB IDs after the SN update.

[0336] The configuration update message may also be a newly defined message.

[0337] Step 1307: The MN updates the available DRB IDs maintained by itself.

[0338] Step 1308: The MN sends an MN configuration update message to the SN. The MN configuration update message includes the available DRB IDs after the MN update.

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

[0340] 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 contains the available DRB IDs after the MN update.

[0341] The configuration update message may also be a newly defined message.

[0342] This embodiment can ensure the uniqueness of the DRB IDs, enabling the SN to increase DRBs according to its own radio resource management strategy and network conditions to reconfigure the mapping relationship between QoS flows and DRBs, making the DRB settings more flexible and effective.

[0343] Figure 17 It is a schematic structural diagram of a first base station of the present application. As Figure 17 shown, the first base station of this embodiment may include: a sending module 11 and a receiving module 12. Among them, the sending module 11 is used to send a first message to the second base station, and the first message is used to request to increase a data radio bearer (DRB). The receiving module 12 is used to receive a second message sent by the second base station, and the second message is used to indicate the identifiers of at least one DRB. The sending module 11 is also used to send a first information to the user equipment, and the first information includes DRB configuration information, and the DRB configuration information includes the identifiers of the at least one DRB.

[0344] Optionally, the first information further includes information on the mapping relationship between the uplink quality of service (QoS) flow and the at least one DRB.

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

[0346] Optionally, the first message includes any one or more of the following information: indication information for requesting to increase a DRB; the number of DRBs requested to be increased; the identifier of the remapped QoS flow; the packet information of the remapped QoS flow; the index of the packet of the remapped QoS flow.

[0347] Optionally, the second message includes any one or more of the following information: the identifier of the available DRB; the identifier of at least one DRB; the identifier of the QoS flow allowed to be mapped to at least one DRB; the identifier of the QoS flow refused to be mapped to at least one DRB; the mapping relationship configuration information between the DRB and the QoS flow; the mapping relationship configuration information between the DRB and the packet of the QoS flow; the mapping relationship configuration information of the index of the packet of the DRB and the QoS flow.

[0348] 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 the first base station to increase at least one QoS flow, or to request to transfer at least one DRB to the first base station, or to request the first base station to increase at least one DRB;

[0349] The third message includes any one or more of the following information: the identifier of at least one QoS flow transferred to the first base station and the QoS parameters of the at least one QoS flow; the mapping relationship between the at least one QoS flow and the DRB; indication information of the transfer type. Wherein, the transfer type includes at least one of QoS flow transfer and DRB transfer.

[0350] Optionally, the sending module 11 is configured to send first information 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.

[0351] 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: the identifier of the available DRB; the identifier of the DRB selected by the first base station; the mapping relationship between the QoS flow configured by the first base station and the DRB.

[0352] Optionally, the first base station in the embodiment of the present application may further include a processing module 13 and a storage module. The storage module is used to store the program code and data of the first base station, and the processing module 13 is used to call the program code and data of the storage module to control the sending module 11 and the receiving module 12 in this embodiment to perform the above operations.

[0353] The first base station of this embodiment can be used to implement the technical solutions of the above method embodiments. The implementation principles and technical effects are similar and will not be elaborated here.

[0354] Figure 18 The following is a schematic structural diagram of a second base station of this application. As Figure 18 shown, the second base station of this embodiment may include: a receiving module 21 and a sending module 22. Among them, the receiving module 21 is used to receive a first message sent by the first base station, and the first message is used to request to add a data radio bearer (DRB); the sending module 22 is used to send a second message to the first base station, and the second message is used to indicate the identifier of at least one DRB.

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

[0356] Optionally, the sending module 22 is further used to: send a third message to the first base station, and 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 first base station, or to request the first base station to add at least one DRB;

[0357] The third message includes any one or more of the following information: the identifier of at least one QoS flow transferred to the first base station and the QoS parameters of the at least one QoS flow; the mapping relationship between the at least one QoS flow and the DRB; indication information of the transfer type. Among them, the transfer type includes at least one of QoS flow transfer and DRB transfer.

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

[0359] Optionally, the second base station of this application embodiment may further include a processing module 23 and a storage module. The storage module is used to store the program code and data of the first base station, and the processing module 23 is used to call the program code and data of the storage module to control the sending module 22 and the receiving module 21 in this embodiment to perform the above operations.

[0360] The second base station of this embodiment can be used to implement the technical solutions of the above method embodiments. The implementation principles and technical effects are similar and will not be elaborated here.

[0361] This application embodiment also provides another first base station. The schematic structural diagram of this first base station is the same asFigure 17 is the same. For details, please refer to Figure 17 As shown in Figure 17 , the sending module of the first base station in this embodiment is used to send a first message to the second base station, and the first message is used to indicate the identifier of the currently available DRB;

[0362] The sending module is further used to send first information to the user equipment, and 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.

[0363] Optionally, the first base station sends the first message after generating the identifier of the currently available DRB by DRB identifier update, and the reasons for DRB identifier update include at least one of adding a DRB and releasing a DRB.

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

[0365] 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.

[0366] Optionally, the first message includes any one or more of the following information: the identifier 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.

[0367] Optionally, the receiving module is used to receive a second message sent by the second base station, and the second message is used to indicate the identifier of the available DRB; the processing module is used to perform DRB identifier update on the identifier of the available DRB to generate the identifier of the currently available DRB.

[0368] Optionally, the second message includes any one or more of the following information: the identifier 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.

[0369] Optionally, the receiving module is further used to receive a third message sent by the second base station, and 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 first base station, or to request the first base station to add at least one DRB;

[0370] The third message includes any one or more of the following information: the identifier of at least one QoS flow transferred to the first base station and the QoS parameters of the at least one QoS flow; the mapping relationship between the at least one QoS flow and the DRB; the indication information of the transfer type; the identifier of the available DRB. Wherein, the transfer type includes at least one of QoS flow transfer and DRB transfer.

[0371] The first base station in this embodiment can be used to execute the technical solutions of the above method embodiments, and its implementation principles and technical effects are similar, which will not be elaborated here.

[0372] It should be noted that Figure 17 The first base station in the illustrated embodiment may correspond to an object device with the same functions. For example, for a base station, the sending module 11 in the embodiments of the present application may correspond to a transmitter of the base station, or may also correspond to a transceiver of the base station. The receiving module 12 may correspond to a receiver of the base station, or may also correspond to a transceiver of the base station. The processing module 13 may correspond to a processor of the base station. Here, the processor may be a central processing unit (CPU), or an application specific integrated circuit (ASIC), or one or more integrated circuits for implementing the embodiments of the present application. The base station may further include a memory for storing instruction codes, and the processor calls the instruction codes in the memory to control the sending module 11 and the receiving module 12 in the embodiments of the present application to perform the above operations.

[0373] It should be noted that Figure 18 The second base station in the illustrated embodiment may correspond to an object device with the same functions. For example, for a base station, the sending module 22 in the embodiments of the present application may correspond to a transmitter of the base station, or may also correspond to a transceiver of the base station. The receiving module 21 may correspond to a receiver of the base station, or may also correspond to a transceiver of the base station. The processing module 23 may correspond to a processor of the base station. Here, the processor may be a CPU, or an ASIC, or one or more integrated circuits for implementing the embodiments of the present application. The base station may further include a memory for storing instruction codes, and the processor calls the instruction codes in the memory to control the sending module 22 and the receiving module 21 in the embodiments of the present application to perform the above operations.

[0374] When at least a part of the functions of the method for obtaining DRB identifiers in the embodiments of the present application are implemented by software, the embodiments of the present application further provide a computer-readable storage medium, which is used to store computer software instructions for the above-mentioned first base station. When it runs on a computer, it enables the computer to execute various possible methods for obtaining DRB identifiers in the above-mentioned method embodiments. When the computer execution instructions are loaded and executed on the computer, the processes or functions described in the embodiments of the present application can 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. The transmission can be carried out wirelessly (such as cellular communication, infrared, short-range wireless, microwave, etc.) to another website, computer, server or data center. The computer-readable storage medium can be any available medium that can be accessed by a computer, or a data storage device such as a server or data center that includes one or more integrated available media. The available medium can be a magnetic medium (such as a floppy disk, hard disk, magnetic tape), an optical medium (such as a DVD), or a semiconductor medium (such as a Solid State Disk (SSD), etc.).

[0375] When at least a part of the functions of the method for obtaining DRB identifiers in the embodiments of the present application are implemented by software, the embodiments of the present application further provide a computer-readable storage medium, which is used to store computer software instructions for the above-mentioned second base station. When it runs on a computer, it enables the computer to execute various possible methods for obtaining DRB identifiers in the above-mentioned method embodiments. When the computer execution instructions are loaded and executed on the computer, the processes or functions described in the embodiments of the present application can 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. The transmission can be carried out wirelessly (such as cellular communication, infrared, short-range wireless, microwave, etc.) to another website, computer, server or data center. The computer-readable storage medium can be any available medium that can be accessed by a computer, or a data storage device such as a server or data center that includes one or more integrated available media. The available medium can be a magnetic medium (such as a floppy disk, hard disk, magnetic tape), an optical medium (such as a DVD), or a semiconductor medium (such as an SSD, etc.).

[0376] In addition, the embodiments of the present application further provide a computer program product containing instructions, that is, a software product. When it runs on a computer, it enables the computer to execute various possible methods for obtaining DRB identifiers in the above-mentioned method embodiments. The implementation principle and technical effects are similar and will not be elaborated here.

[0377] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present application, rather than limiting them; although the present application has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art should understand that they can still modify the technical solutions described in the foregoing embodiments, or perform equivalent replacements on some or all of the technical features; and these modifications or replacements do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of the present application.

Claims

1. A method for obtaining a data radio bearer identifier, characterized in that, it includes: The first base station receives a first message sent by the second base station, and the first message includes an identifier of a quality of service (QoS) flow for which the second base station requests to transfer to the first base station, QoS parameters corresponding to the QoS flow, and an identifier of an available data radio bearer (DRB); The first base station sends a second message to the second base station, and the second message includes an identifier of a DRB selected by the first base station according to the identifier of the available DRB; Wherein, the first base station is a secondary node in dual connectivity, the second base station is a master node in dual connectivity, the first message is a secondary node addition request message, and the second message is a secondary node addition request confirmation message.

2. The method according to claim 1, characterized in that, it further includes: The first base station sends first information to the user equipment, and the first information includes DRB configuration information, and the DRB configuration information includes the identifier of the selected DRB.

3. The method according to claim 2, characterized in that, the first information further includes information on the mapping relationship between the uplink quality of service (QoS) flow and the selected DRB.

4. The method according to any one of claims 1-3, characterized in that, the method further includes: the first base station sends a secondary node (SN) modification requirement message to the second base station, and the SN modification requirement message is used to request to add or release a DRB.

5. The method according to claim 4, characterized in that, the SN modification requirement message includes any one or more of the following information: Indication information for requesting to add a DRB; The number of DRBs requested to be added; The identifier of the DRB requested to be released; The identifier of the QoS flow to be remapped; The packet information of the QoS flow to be remapped; The index of the packet of the QoS flow to be remapped.

6. The method according to any one of claims 1-5, characterized in that, the first base station receives a secondary node (SN) modification confirmation message sent by the second base station, and the SN modification confirmation message includes any one or more of the following information: The identifier 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 identifier of the QoS flow allowed to be mapped to at least one DRB; The identifier of the QoS flow refused to be mapped to at least one DRB; The mapping relationship configuration information between the DRB and the QoS flow; The mapping relationship configuration information between the DRB and the packet of the QoS flow; The mapping relationship configuration information between the DRB and the index of the packet of the QoS flow.

7. The method according to any one of claims 1-6, characterized in that, the first message includes indication information of a transfer type; Wherein, the transfer type includes at least one of QoS flow transfer and DRB transfer.

8. The method according to any one of claims 1-7, characterized in that, the second message includes any one or more of the following information: The identifier of the remaining available DRB; The mapping relationship between the QoS flow and the DRB configured by the first base station.

9. The method according to claim 1 or 2, wherein, the method further comprises: after the first base station generates an identifier of a currently available DRB through DRB identifier update, the first base station sends a fifth message to the second base station, where the fifth message is used to indicate the identifier of the currently available DRB, and the reasons for the DRB identifier update include at least one of adding a DRB and releasing a DRB.

10. The method according to claim 2, wherein, the first information further comprises at least one of 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.

11. The method according to claim 9, wherein, the fifth message includes any one or more of the following information: the identifier of the currently available DRB; the identifier of the DRB released by the first base station.

12. The method according to claim 9, wherein, the method further comprises: the first base station performs DRB identifier update on the identifiers of the available DRBs to generate the identifier of the currently available DRB.

13. A method for obtaining a data radio bearer identifier, wherein, it comprises: the second base station sends a first message to the first base station, where the first message includes the identifier of the quality of service QoS flow that the second base station requests to transfer to the first base station, the QoS parameters corresponding to the QoS flow, and the identifier of the available data radio bearer DRB; the second base station receives a second message sent by the first base station, where the second message includes the identifier of the DRB selected by the first base station according to the identifier of the available DRB; wherein, the first base station is a secondary node in dual connectivity, the second base station is a master node in dual connectivity, the first message is a secondary node addition request message, and the second message is a secondary node addition request confirmation message.

14. The method according to claim 13, wherein, it further comprises: the second base station sends first information to the user equipment, where the first information includes DRB configuration information, and the DRB configuration information includes the identifier of the selected DRB.

15. The method according to claim 14, wherein, the first information further includes information on the mapping relationship between the uplink quality of service QoS flow and the selected DRB.

16. The method according to claim 13 or 14, wherein, the method further comprises: the second base station receives a secondary node SN modification requirement message sent by the first base station, where the secondary node SN modification requirement is used to request adding or releasing a DRB.

17. The method according to claim 16, wherein, the SN modification requirement message includes any one or more of the following information: indication information for requesting to add a DRB; the number of DRBs requested to be added; the identifier of the DRB requested to be released; the identifier of the remapped QoS flow; the packet information of the remapped QoS flow; the index of the packet of the remapped QoS flow.

18. The method according to any one of claims 13 - 17, wherein, the method further comprises: The second base station sends a secondary node SN modification confirmation message to the first base station, where the SN modification confirmation message includes any one or more of the following information: The identifier of the data radio bearer (DRB) occupied by the second base station; The identifier of the DRB released by the second base station; The mapping relationship between the QoS flows and DRBs configured by the second base station; The identifier of the QoS flow allowed to be mapped to at least one DRB; The identifier of the QoS flow refused to be mapped to at least one DRB; The mapping relationship configuration information of DRB and QoS flow; The mapping relationship configuration information of the group of DRB and QoS flow; The mapping relationship configuration information of the index of the group of DRB and QoS flow.

19. The method according to claim 13 or 14, the method further includes: The second base station receives a fifth message sent by the first base station, where the fifth message is used to indicate the identifier of the currently available DRB, and the reason for the update of the DRB identifier includes at least one of adding a DRB and releasing a DRB; the fifth message is sent by the first base station after generating the currently available DRB identifier during the DRB identifier update.

20. The method according to claim 14, characterized in that, The first information further 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.

21. The method according to claim 19, characterized in that, The fifth message includes any one or more of the following information: The identifier of the currently available DRB; The identifier of the DRB released by the first base station.

22. A first base station, characterized in that, includes: A transmitter, configured to receive a first message sent by a second base station, where the first message includes the identifier of the quality of service (QoS) flow that the second base station requests to transfer to the first base station, the QoS parameters corresponding to the QoS flow, and the identifier of the available data radio bearer (DRB); A receiver, configured to send a second message to the second base station, where the second message includes the identifier of the DRB selected by the first base station according to the identifier of the available DRB; wherein, the first base station is a secondary node in dual connectivity, the second base station is a master node in dual connectivity, the first message is a secondary node addition request message, and the second message is a secondary node addition request confirmation message.

23. The first base station according to claim 22, characterized in that, The transmitter is further configured to send first information to a user equipment, where the first information includes DRB configuration information, and the DRB configuration information includes the identifier of the selected DRB.

24. The first base station according to claim 23, characterized in that, The first information further includes information about the mapping relationship between the uplink quality of service (QoS) flow and the selected DRB.

25. The method according to any one of claims 22-24, characterized in that, The method further includes: the first base station sends a secondary node SN modification requirement message to the second base station, and the SN modification requirement message is used to request to add or release a DRB.

26. The first base station according to claim 25, It is characterized in that the SN modification requirement message includes any one or more of the following information: indication information for requesting to add a DRB; the number of DRBs requested to be added; the identifier of the DRB requested to be released; the identifier of the remapped QoS flow; the packet information of the remapped QoS flow; the index of the packet of the remapped QoS flow.

27. The first base station according to any one of claims 22-26, it is characterized in that the first base station receives the secondary node SN modification confirmation message sent by the second base station, and the SN modification confirmation message includes any one or more of the following information: 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 identifier of the QoS flow allowed to be mapped to at least one DRB; the identifier of the QoS flow refused to be mapped to at least one DRB; the mapping relationship configuration information between the DRB and the QoS flow; the mapping relationship configuration information between the DRB and the packet of the QoS flow; the mapping relationship configuration information between the DRB and the index of the packet of the QoS flow.

28. The first base station according to any one of claims 22-27, it is characterized in that the first message includes any one or more of the following information: indication information of the transfer type; wherein the transfer type includes at least one of QoS flow transfer and DRB transfer.

29. The first base station according to any one of claims 22-28, it is characterized in that the second message includes any one or more of the following information: the identifier of the remaining available DRB; the mapping relationship between the QoS flow and the DRB configured by the first base station.

30. The first base station according to any one of claims 22-24, it is characterized in that the transmitter is further configured to, after generating the identifier of the currently available DRB by DRB identifier update, send a fifth message to the second base station, and the fifth message is used to indicate the identifier of the currently available DRB, and the reason for the DRB identifier update includes at least one of adding a DRB and releasing a DRB.

31. The first base station according to claim 23, it is characterized in that the first information further 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.

32. The first base station according to claim 30, it is characterized in that the fifth message includes any one or more of the following information: the identifier of the currently available DRB; the identifier of the DRB released by the first base station.

33. The first base station according to claim 32, it is characterized in that the first base station further includes a processor; the processor is configured to perform DRB identifier update on the identifier of the available DRB to generate the identifier of the currently available DRB.

34. A second base station, it is characterized in that it includes: A transmitter, configured to send a first message to a first base station, where the first message includes an identifier of a Quality of Service (QoS) flow for which a second base station requests to transfer services to the first base station, QoS parameters corresponding to the QoS flow, and an identifier of an available Data Radio Bearer (DRB). A receiver, configured to receive a second message sent by the first base station, where the second message includes an identifier of a DRB selected by the first base station according to the identifier of the available DRB. Wherein, the first base station is a secondary node in a dual connection, the second base station is a primary node in the dual connection, the first message is a secondary node addition request message, and the second message is a secondary node addition request confirmation message.

35. The second base station according to claim 34, wherein, the transmitter is further configured to send first information to a user equipment, where the first information includes DRB configuration information, and the DRB configuration information includes the identifier of the selected DRB.

36. The second base station according to claim 35, wherein, the first information further includes information about a mapping relationship between an uplink Quality of Service (QoS) flow and the selected DRB.

37. The second base station according to any one of claims 34 - 36, wherein, the receiver is further configured to: receive a secondary node (SN) modification requirement message sent by the first base station, where the SN modification requirement message is used to request addition or release of a DRB.

38. The second base station according to claim 37, wherein, the SN modification requirement message includes any one or more of the following information: an indication information for requesting addition of a DRB; a number of DRBs to be added; an identifier of a DRB to be released; an identifier of a re - mapped QoS flow; packet information of a re - mapped QoS flow; an index of a packet of a re - mapped QoS flow.

39. The second base station according to any one of claims 34 - 38, wherein, the transmitter is further configured to: send a secondary node (SN) modification confirmation message to the first base station, where the SN modification confirmation message includes any one or more of the following information: an identifier of a DRB occupied by the second base station; an identifier of a DRB released by the second base station; a mapping relationship between QoS flows and DRBs configured by the second base station; identifiers of QoS flows allowed to be mapped to at least one DRB; identifiers of QoS flows refused to be mapped to at least one DRB; DRB and QoS flow mapping relationship configuration information; DRB and QoS flow packet mapping relationship configuration information; DRB and QoS flow packet index mapping relationship configuration information.

40. The second base station according to claim 34 or 35, the method further includes: the receiver is further configured to receive a fifth message sent by the first base station, where the fifth message is used to indicate an identifier of a currently available DRB, and reasons for updating the DRB identifier include at least one of addition of a DRB and release of a DRB; the fifth message is sent by the first base station after generating the identifier of the currently available DRB due to DRB identifier update.

41. The second base station according to claim 35, wherein, The first information further 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.

42. The second base station according to claim 40, wherein, the fifth message includes any one or more of the following information: the identifier of the currently available DRB; the identifier of the DRB released by the first base station.

43. A computer-readable storage medium, wherein, it stores computer instructions, and when the computer instructions are run on a computer, the computer is caused to execute the method according to any one of claims 1-12 or 13-18.

44. A computer program product, wherein, it includes computer instructions, and when the computer instructions are run on a computer, the computer is caused to execute the method according to any one of claims 1-12 or 13-18.

45. A base station, wherein, the base station includes a memory and a processor, the memory is used for storing instruction codes, and the processor is used for calling the instruction codes so that the base station executes the method according to any one of claims 1-12 or 13-18.

Images