Connection mode configuration method, base station and communication system

Abstract

The present disclosure provides a connection mode configuration method, a base station and a communication system. After receiving the measurement information reported by the user terminal, the CU‑CP of the first base station determines the connection mode adopted by the user terminal after switching to the second base station according to the terminal capability of the user terminal and the connection mode supported by the CU‑UP of the first base station, and sends a switching request to the second base station; after receiving the secondary base station adding request sent by the second base station, the CU‑CP instructs the CU‑UP to update the bearer configuration according to the bearer configuration information included in the secondary base station adding request; the CU‑CP generates the first access configuration information according to the bearer configuration update result of the CU‑UP, and sends the first access configuration information to the second base station; after receiving the switching request response sent by the second base station, the CU‑CP instructs the CU‑UP to update the bearer configuration according to the bearer configuration information included in the switching request response. The present disclosure can realize the correct configuration of the core network connection mode and maintain the continuity of the bearer data during the user connection mode conversion process.

Description

Technical Field

[0001] The present disclosure relates to the field of wireless communications, and in particular to a connection mode configuration method, a base station, and a communication system. Background Art

[0002] As the main technology of the next generation of wireless networks, 5G has technical features such as supporting ultra-wideband and large connections. At present, in the wireless network architecture, the base station side adopts an architecture based on CU (Centralized Unit) and DU (Distributed Unit). The F1 interface is used between CU and DU to transmit information on the control plane and user plane. The CU entity is mainly responsible for the protocol functions of the PDCP (Packet Data Convergence Protocol), SDAP (Service Data Adaptation Protocol) and RRC (Radio Resource Control) layers, while the DU entity is mainly responsible for the physical layer, MAC (Media Access Control) layer, RLC (Radio Link Control) layer functions, and part of the RRC layer ASN.1 encoding and decoding functions. According to the current protocol regulations, the physical layer parameters of the base station are generated and configured by the DU and notified to the CU entity. The cell high-level parameters and radio resource management parameters are generated by the CU.

[0003] In order to further support the virtualization function on the base station side, in the current architecture, there is only one CP (Control Plane) entity on the base station side, and there can be multiple UP (User Plane) entities. The user plane and the control plane are connected through the E1 interface. When the UP and CP establish the E1 interface, the user plane entity needs to notify the control plane entity of the relevant information for relevant configuration settings, including a list of PLMNs (Public Land Mobile Networks) that the UP can support, and the type of core network that the user plane entity can connect to, such as connecting to the 4G core network, the 5G core network, and connecting to both the 4G core network and the 5G core network. Based on this capability, the control plane entity configures the network connection mode for the user terminal with the corresponding terminal capability.

[0004] When the configuration of the UP changes, the UP notifies the control plane entity of the new UP configuration information through E1 signaling. In this process, when the user plane configuration changes, only the control plane is notified of changes in the user plane capacity, supported PLMN, etc. However, if the core network connection mode changes, the CP is not notified of changes in the core network configuration to which the UP is connected in the related art.

[0005] In addition, when the bearer configuration changes, the CP needs to notify the UP to adjust the bearer-related configuration parameters, which indicates the update of the DRB (Data Resource Bearer) based on E-UTRAN (Evolved Universal Terrestrial Radio Access Network) or the PDU session configuration information based on NR (New Radio).

[0006] Taking into account the configuration changes of the mode in the NR base station, it is necessary to support the evolution from NSA (Non-Stand Alone, non-independent networking) single mode to NSA / SA (Stand Alone, independent networking) dual mode.

[0007] The current protocol supports switching from SA to NSA. A special scenario is that the NR side keeps the original node unchanged before and after the switch. During the handover request process, the source side base station gNB needs to notify the target side LTE (Long Term Evolution) base station about the UE NGAP (Next Generation Application Protocol) IE (Information Element) of the user terminal in the base station. Based on this information, after receiving the secondary base station addition request (SgNB Addition Request) message on the X2 interface, the source side base station determines whether it is the establishment request sent by the same user terminal based on this information, and keeps the context of the user terminal unchanged based on this. Summary of the invention

[0008] The inventors note that based on the current evolution direction of supporting NSA deployment to SA or dual-mode, when the user is in the current SA and NSA switching mode and the NR base station adopts a control plane and user plane separation architecture, the prior art still has the following problems:

[0009] -The control plane entity cannot understand the mode update of the user plane entity: When the core network connection capability supported by the user plane changes or the connection conditions of different PLMN configurations are different, the user plane entity in the related art cannot indicate the update information of its core network connection capability and the connection capability configured for each PLMN to the control plane entity. In this case, the control plane lacks understanding of the user plane connection capability, resulting in incorrect network connection configuration for user terminals with different capabilities or user terminals supporting different PLMNs, thereby causing the user terminal to drop calls or fail to switch.

[0010] - Unable to maintain data transmission continuity during mode transition: Currently, on the NR user side, when the bearer changes from SA state to NSA state, two terminal context modification (UE Context Modification) processes are required. The first process requires deleting the previous PDU (Protocol Data Unit) session bearer, and the second process message is to re-establish the DRB bearer based on E-UTRAN. This method will cause the previous received data and cache information to be cleared due to the mode transition, resulting in a longer user transmission recovery time.

[0011] - Unable to associate the relationship between E-RAB (Evolved Radio Access Bearer) and PDU session: Since two Bearer Context Modification processes are required, the user plane cannot understand the mapping relationship between the PDU session to be retained and the subsequently established E-RAB bearer. Therefore, the user plane entity cannot restore the bearer whose transmission is suspended and can only re-transmit data based on the newly created E-RAB bearer, resulting in a longer user transmission recovery time.

[0012] - Inadvertent deletion of bearer configuration: If the NR base station continues to serve as a secondary node of NSA after switching, when the control plane receives a switching completion message sent by a neighboring base station during the switching process, it generally uses a terminal context release (UE Context Release) message to delete all bearer configuration information in the cell. However, if the user plane still needs to be used as a secondary connection for the user, the above solution will cause data interruption for the user.

[0013] Based on this, the current 3GPP (3rd Generation Partnership Project) LTE and NR protocols cannot meet the needs and need to be enhanced in new ways to meet the needs of network deployment and optimization.

[0014] To this end, the present disclosure provides a connection mode configuration solution to solve at least one of the above problems.

[0015] According to a first aspect of an embodiment of the present disclosure, a method for configuring a connection mode is provided, the method being executed by a first base station, including: after receiving measurement information reported by a user terminal, a control plane entity of a centralized unit of the first base station determines, according to the terminal capability of the user terminal and the connection modes supported by the user plane entity of the centralized unit of the first base station, a connection mode that can be adopted by the user terminal after switching to a second base station, and sends a switching request to the second base station; after receiving a secondary base station adding request sent by the second base station, the control plane entity performs bearer configuration on the user plane entity according to first bearer configuration information included in the secondary base station adding request, generates second bearer configuration information according to the configuration result, and instructs the user plane entity to perform bearer configuration update according to the second bearer configuration information; the control plane entity generates first access configuration information according to the bearer configuration update result of the user plane entity, and sends the first access configuration information to the second base station; after receiving a switching request response sent by the second base station, the control plane entity generates fourth bearer configuration information for performing bearer configuration on the user plane entity according to third bearer configuration information included in the switching request response, and instructs the user plane entity to perform bearer configuration update according to the fourth bearer configuration information.

[0016] In some embodiments, the control plane entity determines that the connection mode that the user terminal can adopt after switching to the second base station includes: when the user terminal only supports a single connection, the control plane entity determines that the user terminal establishes a single connection with the second base station after switching; when the user terminal supports dual connections and the core network connection capability of the user plane entity corresponding to the public land mobile network selected by the user terminal is to support the 5G core network, the control plane entity determines that the user terminal only establishes a single connection with the second base station after switching; when the user terminal supports dual connections and the core network connection capability of the user plane entity corresponding to the public land mobile network selected by the user terminal is to support the evolved packet core network and the 5G core network, the control plane entity determines, according to the signal strength, that the user terminal establishes a single connection with the second base station after switching, or establishes dual connections with the first base station and the second base station.

[0017] In some embodiments, the handover request includes address information of the second base station and handover assistance information, wherein the handover assistance information includes a next generation application protocol identifier allocated to the user terminal by a first core network corresponding to the first base station.

[0018] In some embodiments, when the user terminal can only establish a single connection with the second base station after switching, the switching request also includes measurement results associated with the wireless access technology used by the second base station; when the user terminal can establish dual connections with the first base station and the second base station after switching, the switching request also includes measurement results associated with the wireless access technology used by the first base station and measurement results associated with the wireless access technology used by the second base station; when the switching reason is evolved packet system fallback, and the control plane entity does not include measurement results in the switching request.

[0019] In some embodiments, the measurement result includes an identifier of the measured cell, and at least one of a signal strength or a signal quality associated with the identifier of the measured cell, the signal strength includes at least one of a reference signal reception power of a long term evolution cell or a reference signal reception power of a synchronization signal of a new air interface cell, and the signal quality includes at least one of a reference signal reception quality of a long term evolution cell or a reference signal reception quality of a synchronization signal of a new air interface cell.

[0020] In some embodiments, the control plane entity sending the switching request to the second base station includes: the control plane entity sending the switching request to the second base station through a first core network corresponding to the first base station and a second core network corresponding to the second base station.

[0021] In some embodiments, the control plane entity performs bearer configuration on the user plane entity according to the first bearer configuration information, including: the control plane entity determines whether the bearer of the first base station includes an evolved radio access bearer matching the protocol data unit session, when judging according to the next generation application protocol identifier that the user terminal has configured a context in the first base station and is performing a switching operation, wherein the service quality information of the protocol data unit session is the same as the service quality information of the matching evolved radio access bearer; if there is an evolved radio access bearer matching the protocol data unit session, the control plane entity determines that the protocol data unit session needs to be retained in the user plane entity after the user terminal is switched, and establishes a mapping relationship between the control plane entity and the matching evolved radio access bearer; if the protocol data unit session does not have a matching evolved radio access bearer, the control plane entity determines that the protocol data unit session needs to be deleted after the user terminal is switched; if the evolved radio access bearer does not have a matching protocol data unit session, a matching protocol data unit session is added to the evolved radio access bearer.

[0022] In some embodiments, the control plane entity instructs the user plane entity to update the bearer configuration according to the second bearer configuration information, including: the control plane entity sends a first bearer context modification request to the user plane entity; the user plane entity performs corresponding bearer configuration updates according to the second bearer configuration information included in the first bearer context modification request, and stops sending data to the user terminal; wherein the second bearer configuration information includes protocol data unit session information that needs to be deleted, protocol data unit session information that needs to be modified, and an evolved radio access bearer that needs to be added, wherein the protocol data unit session information that needs to be deleted includes a protocol data unit session identifier and a suspend operation indication, the protocol data unit session information that needs to be modified includes a protocol data unit session identifier, an evolved radio access bearer having a mapping relationship with the protocol data unit session, and a corresponding bearer type, and the evolved radio access bearer information that needs to be added includes an evolved radio access bearer identifier that needs to be added and corresponding quality of service information.

[0023] In some embodiments, after the user plane entity performs a corresponding bearer update operation, it sends a first bearer context modification response to the control plane entity, and the first bearer context modification response includes at least one item in a list of successfully added bearers, a list of successfully deleted bearers, a list of successfully modified bearers, or a successful list that cannot be successfully accepted.

[0024] In some embodiments, the control plane entity sending the first access configuration information to the second base station includes: the control plane entity encapsulating the first access configuration information in a wireless resource control container, and sending it to the second base station through the interface between the control plane entity and the second base station; the first access configuration information includes at least one item in the bearer list successfully added by the user plane entity, the bearer list successfully deleted, or the successful list that could not be successfully accepted.

[0025] In some embodiments, instructing the user plane entity to update the bearer configuration according to the fourth bearer configuration information includes: the control plane entity sends a second bearer context modification request to the user plane entity, wherein the second bearer context modification request includes the fourth bearer configuration information; the user plane entity configures the bearer to be added for uplink and downlink service transmission according to the fourth bearer configuration information, and deletes the identifier and all cached data of the bearer to be deleted.

[0026] In some embodiments, after receiving the access request sent by the user terminal, the control plane entity sends access indication information to the user plane entity; after receiving the access indication information, the user plane entity uses the configured bearer to process the uplink data and downlink data of the user terminal; wherein the access indication information includes a control plane user identifier assigned by the control plane entity, a user plane user identifier assigned by the user plane entity, and an access completion indication.

[0027] In some embodiments, the user plane entity determines its own core network connection capability based on the trigger information, and sends its own core network connection capability information to the control plane entity; the control plane entity determines the connection mode of the user terminal based on the core network connection capability information of the user plane entity itself.

[0028] In some embodiments, the core network connection capability information includes the public core network support capability of the user plane entity and a list of public land mobile networks supported by the user plane entity, wherein the list of public land mobile networks includes a public land mobile network identifier and the core network support capability of each public land mobile network.

[0029] In some embodiments, when the core network connection capability of one or more public land mobile networks changes, the user plane entity sends updated core network connection capability information to the control plane entity, so that the control plane entity determines the connection mode of the user terminal based on the updated core network connection capability information.

[0030] In some embodiments, when the user plane entity supports the evolved packet core network, the user terminal selecting the user plane entity can only configure the non-independent networking mode; when the user plane entity supports the 5G core network, the user terminal selecting the user plane entity can only configure the independent networking mode; when the user plane entity supports the evolved packet core network and the 5G core network, the user terminal selecting the user plane entity can configure at least one of the non-independent networking mode or the independent networking mode as needed.

[0031] According to a second aspect of an embodiment of the present disclosure, a base station is provided, comprising: a memory configured to store instructions; a processor coupled to the memory, the processor being configured to execute a method as described in any of the above embodiments based on the instructions stored in the memory.

[0032] According to a third aspect of an embodiment of the present disclosure, a method for configuring a connection mode is provided, the method being executed by a second base station, including: after receiving a switching request sent by a control plane entity of a first base station centralized unit, determining whether to use the first base station as a secondary base station of the user terminal; in the case of using the first base station as a secondary base station, sending a secondary base station addition request to the control plane entity, wherein the secondary base station addition request includes first bearer configuration information associated with a service that needs to be carried by the first base station; generating second access configuration information for the user terminal to access the second base station according to the first access configuration information sent by the control plane entity, and sending a switching request response to the control plane entity, wherein the switching request response includes third bearer configuration information for describing the bearer configurations of the first base station and the second base station.

[0033] In some embodiments, the judgment of whether to use the first base station as the secondary base station of the user terminal includes: when the terminal capability of the user terminal does not support adding a secondary connection during the switching process, determining not to use the first base station as the secondary base station of the user terminal; when the terminal capability of the user terminal supports adding a secondary connection during the switching process, and the switching reason is evolved packet system fallback, and there is no measurement result, determining to use the first base station as the secondary base station of the user terminal; when the terminal capability of the user terminal supports adding a secondary connection during the switching process, and the signal strength of the cell to which the first base station belongs is the highest in the measurement result, determining to use the first base station as the secondary base station of the user terminal.

[0034] In some embodiments, the first bearer configuration information includes a list of services carried by the first base station and a next-generation application protocol identifier allocated by the first core network to the user terminal, wherein the list of services carried by the first base station includes an identifier of each evolved wireless access bearer and corresponding service quality configuration information.

[0035] In some embodiments, after generating the second access configuration information, it also includes: placing the first access configuration information into a first wireless resource control container to instruct the user terminal to access the first base station during the switching process; placing the second access configuration information into a second wireless resource control container to instruct the user terminal to access the second base station during the switching process.

[0036] In some embodiments, the third bearer configuration information includes a list of bearers that the first base station can accommodate, a list of bearers that the second base station can accommodate, a list of bearers that the first base station cannot accommodate, and a list of bearers that the second base station cannot accommodate.

[0037] In some embodiments, sending the handover request response to the control plane entity includes: sending the handover request response to the first base station through a second core network corresponding to the second base station and a first core network corresponding to the first base station.

[0038] According to a fourth aspect of an embodiment of the present disclosure, a base station is provided, comprising: a memory configured to store instructions; a processor coupled to the memory, the processor being configured to execute a method as described in any of the above embodiments based on the instructions stored in the memory.

[0039] According to a fifth aspect of an embodiment of the present disclosure, a communication system is provided, including: a first base station, which is the base station described in the above second aspect; and a second base station, which is the base station described in the above fourth aspect.

[0040] In some embodiments, the communication system also includes a first core network corresponding to the first base station and a second core network corresponding to the second base station; the first core network maps the protocol data unit session included in the switching request sent by the first base station to evolved wireless access bearer information, records the mapping relationship between the protocol data unit session identifier and the evolved wireless access bearer identifier, writes the evolved wireless access bearer information into the switching request to update the switching request, and sends the updated switching request to the second core network; the second core network sends the updated switching request to the second base station.

[0041] In some embodiments, the second core network sends the switching request response sent by the second base station to the first core network; the first core network converts the evolved radio access bearer identifier included in the third bearer configuration information in the switching request response into a protocol data unit session identifier according to the mapping relationship between the protocol data unit session identifier and the evolved radio access bearer identifier to generate an updated switching request response; the first core network sends the updated switching request response to the first base station.

[0042] According to a sixth aspect of an embodiment of the present disclosure, a computer-readable storage medium is provided, wherein the computer-readable storage medium stores computer instructions, and when the instructions are executed by a processor, the method involved in any of the above embodiments is implemented.

[0043] Other features and advantages of the present disclosure will become apparent from the following detailed description of exemplary embodiments of the present disclosure with reference to the accompanying drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0044] In order to more clearly illustrate the embodiments of the present disclosure or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present disclosure. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative labor.

[0045] Figure 1 A schematic diagram of a connection mode configuration method according to an embodiment of the present disclosure;

[0046] Figure 2 A flowchart of a connection mode configuration method according to another embodiment of the present disclosure;

[0047] Figure 3 This is a schematic diagram of the structure of a base station according to an embodiment of the present disclosure;

[0048] Figure 4 A flowchart of a connection mode configuration method according to another embodiment of the present disclosure;

[0049] Figure 5 This is a schematic structural diagram of a base station according to another embodiment of the present disclosure;

[0050] Figure 6 A schematic diagram of the structure of a communication system according to an embodiment of the present disclosure;

[0051] Figure 7 A schematic diagram of the structure of a communication system according to another embodiment of the present disclosure;

[0052] Figure 8 A flowchart of a connection mode configuration method according to another embodiment of the present disclosure;

[0053] Fig. 9 The present invention is a flowchart of a connection mode configuration method according to another embodiment of the present invention. DETAILED DESCRIPTION

[0054] The following will be combined with the drawings in the embodiments of the present disclosure to clearly and completely describe the technical solutions in the embodiments of the present disclosure. Obviously, the described embodiments are only part of the embodiments of the present disclosure, rather than all of the embodiments. The following description of at least one exemplary embodiment is actually only illustrative and is by no means intended to limit the present disclosure and its application or use. Based on the embodiments in the present disclosure, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present disclosure.

[0055] Unless specifically stated otherwise, the relative arrangement of components and steps, the numerical expressions and numerical values ​​set forth in these embodiments do not limit the scope of the present disclosure.

[0056] At the same time, it should be understood that for the convenience of description, the sizes of the various parts shown in the drawings are not drawn according to the actual proportional relationship.

[0057] Technologies, methods, and apparatus known to ordinary technicians in the relevant field may not be discussed in detail, but where appropriate, such technologies, methods, and apparatus should be considered part of the authorization specification.

[0058] In all examples shown and discussed herein, any specific values ​​should be interpreted as merely exemplary and not as limiting. Therefore, other examples of the exemplary embodiments may have different values.

[0059] It should be noted that like reference numerals and letters refer to similar items in the following figures, and therefore, once an item is defined in one figure, it need not be further discussed in subsequent figures.

[0060] Figure 1 The following is a flow chart of a connection mode configuration method according to an embodiment of the present disclosure. In some embodiments, the following connection mode configuration method is executed by the first base station.

[0061] In step 101, a user plane entity CU-UP of a first base station centralized unit determines its own core network connection capability according to trigger information, and sends its own core network connection capability information to a control plane entity CU-CP of the first base station centralized unit.

[0062] In some embodiments, the trigger information may be network management configuration information.

[0063] In some embodiments, the CU-UP may send its own core network connection capability information to the CU-CP via a GNB-CU-UP E1 SETUP REQUEST message or a GNB-CU-CPE1 SETUP RESPONSE message.

[0064] In some embodiments, the core network connection capability information includes:

[0065] - CU-UP's public core network support capability: an enumeration type, including EPC (Evolved Packet Core), 5GC (5G core network) or Both options, indicating the software support capability of the core network user plane that the CU-UP can connect to

[0066] -PLMN list supported by CU-UP:

[0067] PLMN identity: PLMN information as defined in TS38.463,

[0068] Core network support capabilities of each PLMN: When this information is not configured, it means that the PLMN supports the same core network capabilities as the public core network support capabilities. If configured, it means that the PLMN will apply the capabilities defined in this information.

[0069] In step 102, the CU-CP determines the connection mode of the user terminal according to the core network connection capability information of the CU-UP itself.

[0070] For example, when CU-UP supports EPC, the user terminal that selects CU-UP can only configure the NSA mode; when CU-UP supports the 5G core network, the user terminal that selects CU-UP can only configure the SA mode; when CU-UP supports EPC and the 5G core network, the user terminal that selects CU-UP can configure at least one of the NSA mode or the SA mode as needed.

[0071] In some embodiments, when the core network connection capability of one or more PLMNs changes, CU-UP sends updated core network connection capability information to CU-CP so that CU-CP determines the connection mode of the user terminal based on the updated core network connection capability information.

[0072] For example, the CU-UP sends the updated core network connection capability information to the CU-CP through a GNB-CU-UP CONFIGURATION UPDATE message or a GNB-CU-CP CONFIGURATION UPDATE ACKNOWLEDGE message.

[0073] Therefore, CU-CP can determine the corresponding network access mode for users based on the core network connection capabilities of CU-UP.

[0074] Figure 2 The following is a flow chart of a connection mode configuration method according to another embodiment of the present disclosure. In some embodiments, the following connection mode configuration method is executed by the first base station.

[0075] In step 201, after receiving the measurement information reported by the user terminal, the CU-CP of the first base station determines the connection mode that the user terminal can adopt after switching to the second base station based on the terminal capability of the user terminal and the connection mode supported by the CU-UP of the first base station, and sends a switching request to the second base station so that the second base station determines whether to use the first base station as a secondary base station for the user terminal.

[0076] In some embodiments, the CU-CP determines that the connection mode that the user terminal can adopt after switching to the second base station includes: when the user terminal only supports a single connection, the CU-CP determines that the user terminal establishes a single connection with the second base station after switching; when the user terminal supports dual connections and the core network connection capability of the CU-UP corresponding to the PLMN selected by the user terminal is to support the 5G core network, the CU-CP determines that the user terminal only establishes a single connection with the second base station after switching; when the user terminal supports dual connections and the core network connection capability of the CU-UP corresponding to the PLMN selected by the user terminal is to support EPC and 5G core network, the CU-CP determines that the user terminal establishes a single connection with the second base station after switching, or establishes dual connections with the first base station and the second base station based on the signal strength.

[0077] In some embodiments, the handover request includes address information of the second base station and handover assistance information, wherein the handover assistance information includes an NGAP identifier allocated to the user terminal by the first core network corresponding to the first base station.

[0078] In some embodiments, when the user terminal can only establish a single connection with the second base station after the handover, the handover request also includes a measurement result associated with the RAT (Radio Access Technology) used by the second base station. When the user terminal can establish a dual connection with the first base station and the second base station after the handover, the handover request also includes a measurement result associated with the RAT used by the first base station and a measurement result associated with the RAT used by the second base station; when the handover reason is the evolved packet system fallback (EPS Fallback), the CU-CP handover request does not include the measurement result.

[0079] In some embodiments, the measurement result includes an identifier of the measured cell, and at least one of a signal strength or a signal quality associated with the identifier of the measured cell, the signal strength includes at least one of a reference signal received power RSRP of the LTE cell or a reference signal received power SS-RSRP of a synchronization signal of a new air interface cell, and the signal quality includes at least one of a reference signal received quality RSRQ of the LTE cell or a reference signal received quality SS-RSRQ of a synchronization signal of a new air interface cell.

[0080] In some embodiments, the CU-CP sends a switching request to the second base station through a first core network corresponding to the first base station and a second core network corresponding to the second base station.

[0081] In step 202, after receiving the secondary base station adding request sent by the second base station, the CU-CP performs bearer configuration on the CU-UP according to the first bearer configuration information included in the secondary base station adding request, generates second bearer configuration information according to the configuration result, and instructs the CU-UP to update the bearer configuration according to the second bearer configuration information.

[0082] In some embodiments, CU-CP performs bearer configuration of CU-UP according to the first bearer configuration information, including: when CU-CP determines according to the NGAP identifier that the user terminal has configured the context in the first base station and is performing a switching operation, it determines whether the bearer of the first base station includes an E-RAB that matches the PDU session, wherein the QoS information of the PDU session is the same as the QoS information of the matching E-RAB; if there is an E-RAB that matches the PDU session, the CU-CP determines that the PDU session needs to be maintained in the CU-UP after the user terminal is switched, and establishes a mapping relationship between the CU-CP and the matching E-RAB; if the PDU session does not have a matching E-RAB, the CU-CP determines that the PDU session needs to be deleted after the user terminal is switched; if the E-RAB does not have a matching PDU session, a matching PDU session is added to the E-RAB.

[0083] In some embodiments, the CU-CP instructs the CU-UP to perform a bearer configuration update according to the second bearer configuration information, including: the CU-CP sends a first bearer context modification request to the CU-UP, and the CU-UP performs a corresponding bearer configuration update according to the second bearer configuration information included in the first bearer context modification request, and stops sending data to the user terminal. The second bearer configuration information includes

[0084] -PDU session information to be deleted

[0085] PDU Session Identifier

[0086] Suspend operation indication: enumeration type, indicating that the PDU session is ready to be deleted and data transmission is suspended

[0087] -PDU session information that needs to be modified

[0088] PDU Session Identifier

[0089] Bearer type: enumeration type, indicating when a PDU session needs to be converted to an E-RAB DRB.

[0090] E-RAB mapped to the PDU session: E-RAB identifier assigned by the control plane to the PDU session

[0091] -E-RAB that needs to be added,

[0092] E-RAB identifier to be added

[0093] QoS information of the bearer.

[0094] In step 203, the CU-CP generates first access configuration information according to the bearer configuration update result of the CU-UP, and sends the first access configuration information to the second base station so that the second base station generates second access configuration information for the user terminal to access the second base station.

[0095] In some embodiments, after performing a corresponding bearer update operation, the CU-UP sends a first bearer context modification response to the CU-CP, where the first bearer context modification response includes:

[0096] - List of bearers added successfully: related E-RAB bearer identifiers

[0097] - List of bearers successfully deleted: related PDU session identifiers

[0098] - List of successfully modified bearers: the relevant PDU session identifiers and the E-UTRAN identifier corresponding to the PDU

[0099] - List of successful acceptances that could not be successfully accepted: related E-RAB bearer identifiers

[0100] In some embodiments, the CU-CP sending the first access configuration information to the second base station includes: the CU-CP encapsulating the first access configuration information in an RRC container, and sending the first access configuration information to the second base station through an interface between the CU-CP and the second base station.

[0101] The first access configuration information includes at least one item in a bearer list successfully added by the CU-UP, a bearer list successfully deleted, or a successful list that could not be successfully admitted.

[0102] In step 204, after receiving the switching request response sent by the second base station, the CU-CP generates fourth bearer configuration information for bearer configuration of the CU-UP according to the third bearer configuration information included in the switching request response, and instructs the CU-UP to update the bearer configuration according to the fourth bearer configuration information.

[0103] In some embodiments, the CU-CP instructs the CU-UP to update the bearer configuration according to the fourth bearer configuration information, including: the CU-CP sends a second bearer context modification request to the CU-UP, wherein the second bearer context modification request includes the fourth bearer configuration information. According to the fourth bearer configuration information, the CU-UP configures the bearer to be added for uplink service and downlink service transmission, and deletes the identifier and all cached data of the bearer to be deleted.

[0104] In some embodiments, after receiving the access request sent by the user terminal, the CU-CP sends access indication information to the CU-UP. After receiving the access indication information, the CU-UP uses the configured bearer to process the uplink data and downlink data of the user terminal. The access indication information includes the control plane user identifier assigned by the CU-CP, the user plane user identifier assigned by the CU-UP, and the access completion indication.

[0105] Figure 3 FIG. 1 is a schematic diagram of the structure of a base station according to an embodiment of the present disclosure. Figure 3 As shown, the base station includes a memory 31 and a processor 32.

[0106] The memory 31 is used to store instructions. The processor 32 is coupled to the memory 31. The processor 32 is configured to execute the instructions stored in the memory to implement the following. Figure 1 or Figure 2 The method of any one of the embodiments.

[0107] like Figure 3 As shown, the base station also includes a communication interface 33 for information exchange with other devices. At the same time, the device also includes a bus 34, through which the processor 32, the communication interface 33, and the memory 31 communicate with each other.

[0108] The memory 31 may include a high-speed RAM memory, and may also include a non-volatile memory, such as at least one disk memory. The memory 31 may also be a memory array. The memory 31 may also be divided into blocks, and the blocks may be combined into virtual volumes according to certain rules.

[0109] In addition, the processor 32 may be a central processing unit (CPU), or may be an application specific integrated circuit (ASIC), or may be configured to implement one or more integrated circuits of the embodiments of the present disclosure.

[0110] The present disclosure also relates to a computer-readable storage medium, wherein the computer-readable storage medium stores computer instructions, which are executed by a processor to implement the following Figure 1 or Figure 2 The method of any one of the embodiments.

[0111] Figure 4 This is a flow chart of a connection mode configuration method according to another embodiment of the present disclosure. In some embodiments, the following connection mode configuration method is executed by the second base station.

[0112] In step 401, after receiving a handover request sent by a CU-CP of a central unit of a first base station, it is determined whether to use the first base station as a secondary base station of a user terminal.

[0113] In some embodiments, determining whether to use the first base station as a secondary base station for the user terminal includes: when the terminal capability of the user terminal does not support adding a secondary connection during the switching process, determining not to use the first base station as a secondary base station for the user terminal; when the terminal capability of the user terminal supports adding a secondary connection during the switching process, and the switching reason is EPSFallback, and there is no measurement result, determining to use the first base station as a secondary base station for the user terminal; when the terminal capability of the user terminal supports adding a secondary connection during the switching process, and the signal strength of the cell to which the first base station belongs is the highest in the measurement result, determining to use the first base station as a secondary base station for the user terminal.

[0114] In step 402, when the first base station is used as a secondary base station, a secondary base station adding request is sent to the CU-CP, wherein the secondary base station adding request includes first bearer configuration information associated with a service that needs to be carried by the first base station.

[0115] In some embodiments, the first bearer configuration information includes a service list carried by the first base station and an NGAP identifier allocated by the first core network to the user terminal, wherein the service list carried by the first base station includes an identifier of each E-RAB and corresponding QoS configuration information.

[0116] In step 403, second access configuration information for the user terminal to access the second base station is generated according to the first access configuration information sent by the CU-CP, and a switching request response is sent to the CU-CP, wherein the switching request response includes third bearer configuration information for describing the bearer configuration of the first base station and the second base station.

[0117] In some embodiments, after generating the second access configuration information, the first access configuration information is also placed in the first RRC container to instruct the user terminal to access the first base station during the switching process; the second access configuration information is placed in the second RRC container to instruct the user terminal to access the second base station during the switching process.

[0118] In some embodiments, the third bearer configuration information includes a list of bearers that can be accepted by the first base station, a list of bearers that can be accepted by the second base station, a list of bearers that cannot be accepted by the first base station, and a list of bearers that cannot be accepted by the second base station.

[0119] In some embodiments, sending the handover request response to the CU-CP includes: the second base station sending the handover request response to the first base station through a second core network corresponding to the second base station and a first core network corresponding to the first base station.

[0120] Figure 5 The present invention is a schematic diagram of the structure of a base station according to an embodiment of the present invention. Figure 5 The system includes a memory 51, a processor 52, a communication interface 53 and a bus 54. The processor 52 is configured to execute instructions stored in the memory to implement the following. Figure 4 The method of any one of the embodiments.

[0121] The present disclosure also relates to a computer-readable storage medium, wherein the computer-readable storage medium stores computer instructions, which are executed by a processor to implement the following Figure 4 The method of any one of the embodiments.

[0122] Figure 6 FIG. 1 is a schematic diagram of the structure of a communication system according to an embodiment of the present disclosure. Figure 6 As shown, the communication system includes a first base station 61 and a second base station 62. The first base station 61 is Figure 3 In any of the embodiments, the second base station 62 is Figure 5 A base station involved in any one of the embodiments.

[0123] Figure 7 A schematic diagram of the structure of a communication system according to another embodiment of the present disclosure. Figure 7 and Figure 6 The difference is that in Figure 7 In the illustrated embodiment, the communication system further includes a first core network 63 corresponding to the first base station 61 and a second core network 64 corresponding to the second base station 62 .

[0124] In the process of the first base station sending a handover request to the second base station, the first core network 63 maps the PDU session included in the handover request sent by the first base station 61 to E-RAB information, records the mapping relationship between the PDU session identifier and the E-RAB identifier, writes the E-RAB information into the handover request to update the handover request, and sends the updated handover request to the second core network 64. The second core network 64 sends the updated handover request to the second base station 62.

[0125] In the process of the second base station sending the handover request response to the first base station, the second core network 64 sends the handover request response sent by the second base station 62 to the first core network 63. The first core network 63 converts the E-RAB identifier included in the third bearer configuration information in the handover request response to the PDU session identifier according to the mapping relationship between the PDU session identifier and the E-RAB identifier to generate an updated handover request response. The first core network 63 sends the updated handover request response to the first base station 61.

[0126] In some embodiments, the functional unit module described above can be implemented as a general-purpose processor, a programmable logic controller (PLC), a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components or any appropriate combination thereof for performing the functions described in the present disclosure.

[0127] The present disclosure is described below through specific embodiments.

[0128] Embodiment 1:

[0129] In this embodiment, the control plane and the user plane are separated in the first base station (NR base station). In the process of configuring the E1 interface, two network numbers, PLMN1 and PLMN2, are supported, and the user plane entities of the two network numbers only support connecting to EPC. Due to the software upgrade of the user plane entity, it supports simultaneous connection to 5GC, but the network management only configures PLMN1 to support the 5G core network 5GC. The update process is triggered by the user plane entity. Figure 8 As shown:

[0130] In step 801, the gNB-CU-CP determines the first core network connection capability supported by each PLMN according to the network management configuration, and includes the first core network connection capability information in the E1 interface establishment request (GNB-CU-UP E1SETUPREQUEST) and sends it to the gNB-CU-UP. The first core network connection capability information includes:

[0131] -Public core network support capabilities: EPC

[0132] -List of PLMNs supported by this user plane entity:

[0133] PLMN1

[0134] PLMN2

[0135] In step 802, the gNB-CU-UP stores the first core network connection capability information supported by the user plane entity, and determines that all users can only use the NSA access solution based on the public core network support capabilities.

[0136] In step 803, the core network connection capability of PLMN1 in the gNB-CU-CP is changed to support 5GC and EPC. The gNB-CU-CP sends the updated first core network connection capability to the gNB-CU-UP through a configuration update message (GNB-CU-UP CONFIGURATION UPDATE). The configuration information is:

[0137] -Public core network support capabilities: EPC

[0138] -List of PLMNs supported by this user plane entity:

[0139] PLMN1

[0140] ●Each PLMN core network supports: both

[0141] PLMN2

[0142] In step 804, after receiving the configuration update message, the gNB-CU-CP updates the stored first core network connection capability and determines the network access mode for the user based on the new first core network connection capability.

[0143] Embodiment 2:

[0144] This embodiment describes a process of switching from SA to NSA, which involves a voice interoperation process triggered by EPS Fallback and does not contain any measurement report information. Before the switch, only one default bearer service and one FTP download service are maintained on the NR side. The user plane entity supports two network numbers, PLMN1 and PLMN2. The user plane entities of the two network numbers only support connecting to EPC. Due to the software upgrade of the user plane entity, it supports simultaneous connection to 5GC, but the network management only configures PLMN1 to support 5GC. Fig. 9 As shown:

[0145] In step 901, the gNB-CU-CP determines the connection mode that the user can use after switching to the second base station eNB based on the user's UE capabilities and the connection modes supported by the user plane. Currently, the user supports NSA / SA mode and direct switching from SA to NSA, and the user terminal selects PLMN1. Based on the indication information of the user plane, the gNB-CU-CP determines that the user can support NSA / SA mode.

[0146] In step 902, the gNB-CU-CP determines that only the handover cause value is carried because the user is handing over based on EPS Fallback triggering and the measurement report of the UE has not yet been received. The gNB-CU-CP sends the measurement result and handover assistance information to the AMF to which the gNB is connected.

[0147] And the measurement results include the following information:

[0148] - Switching reason value: EPS Fallback

[0149] The switching auxiliary information includes the following:

[0150] -UE NGAP Logo:

[0151] In step 903, the AMF (Access and Mobility Management Function) determines the access mode of the eNB and the corresponding MME (Mobility Management Entity) according to the target base station address information carried in the switching request message, maps the PDU session information carried in the switching message into E-RAB information and puts it into the switching request message, records the mapping relationship between the user's PDU session identifier and the E-RAB identifier, and forwards the switching request message to the MME.

[0152] In step 904, after receiving the handover request message forwarded by the AMF, the MME determines the recipient of the handover message according to the target address information carried in the handover message, and sends the message to the eNB.

[0153] In step 905, after the eNB receives the switching request from the gNB-CU-CP, it determines to add the gNB as the user's secondary connection based on the switching reason being EPS Fallback and no measurement results.

[0154] In step 906, the eNB determines which services need to be carried by the gNB based on the pre-configuration information, and sends a secondary base station addition request (SgNB Addition Request) message containing the first bearer configuration information to the gNB-CU-CP through the X2 interface. The first bearer configuration information includes the following configuration information:

[0155] - List of services carried by gNB

[0156] Identifier of each E-RAB bearer

[0157] QOS configuration information for each bearer

[0158] -UE NGAP Logo

[0159] In step 907, the gNB-CU-CP determines whether the user has configured a context in the gNB according to the UE NGAP identifier and is performing a handover operation. If the context has been configured and a handover operation is being performed, the gNB-CU-CP retains the user's context information, and PDU session 1 and session 2 use the same QOS value, so they are mapped to E-RAB 1 at the same time. The gNB-CU-CP sends a BEARER CONTEXT MODIFICATION REQUEST message including the second bearer configuration information to the gNB-CU-UP. The second bearer configuration includes the following information:

[0160] -PDU session that needs to be modified:

[0161] Contains the identifier of the PDU session

[0162] Bearer type: enumeration type, E-RAB, indicates this field when a PDU session needs to be converted to an E-RAB DRB

[0163] E-RAB session to which the PDU session is mapped: E-RAB ID assigned by the control plane to the PDU session

[0164] In step 908, the gNB-CU-UP completes the update and addition operations of the PDU bearer and stops sending any data to the terminal.

[0165] In step 909, the gNB-CU-UP indicates the gNB-CU-CP bearer configuration information through a BEARER CONTEXT MODIFICATION RESPONSE message. The bearer configuration information includes the following:

[0166] - List of successfully modified bearers

[0167] PDU Session Identifier

[0168] E-UTRAN identifier corresponding to the PDU

[0169] In step 910, the gNB-CU-CP generates the first bearer configuration completion information, encapsulates the access configuration information in the RRC container, and sends a secondary connection update response message to the eNB through the X2 interface to notify it of the bearer update result and user parameter configuration information. The first bearer configuration completion information:

[0170] ●Added successful E-RAB list: E-RAB DRB1

[0171] In step 911, the eNB generates access configuration information generated by the eNB for the user according to the secondary connection update response message sent by the gNB-CU-CP, and puts the received access configuration information generated by the gNB for the user into two independent RRC containers to indicate that the user accesses the gNB and eNB respectively during the switching process.

[0172] In step 912, the eNB generates third bearer configuration information according to the secondary connection update response message sent by the gNB-CU-CP, and simultaneously places the access configuration information generated by the gNB and the eNB in ​​the handover response message and sends it to the MME. The third bearer configuration information includes but is not limited to the following information:

[0173] - Acceptable bearer information:

[0174] List of bearers that the eNB can accommodate: E-RAB ID of each bearer

[0175] List of bearers that gNB can accept: "List of E-RABs added successfully" in the first bearer configuration completion information

[0176] In step 913, the MME determines that the recipient of the switching response message is the AMF according to the target base station identification information carried in the switching response message, and forwards it to the AMF.

[0177] In step 914, the AMF converts the E-RAB identifier in the third bearer configuration information in the handover response into a PDU session identifier according to the stored mapping relationship between the E-RAB and PDU session identifiers, and sends the handover response message to the gNB-CU-CP according to the target base station identifier carried in the handover response message.

[0178] In step 915, after receiving the handover request response message, the gNB-CU-CP generates fourth bearer configuration information and sends it to the gNB-CU-UP via a bearer context modification request (BEARER CONTEXT MODIFICATION REQUEST) message. The fourth bearer configuration information includes but is not limited to the following:

[0179] - List of bearers to be added

[0180] PDU Session 1

[0181] PDU Session 2

[0182] In step 916, after the gNB-CU-UP receives the BEARER CONTEXT MODIFICATION REQUEST message, for the bearer to be added in the fourth bearer configuration information, the gNB-CU-UP configures that uplink and downlink transmission services can be performed. For the bearer to be deleted, the gNB-CU-UP deletes the identifier and all cached data of the bearer.

[0183] In step 917, after receiving the user random access request, the gNB-CU-CP sends access completion indication information to the gNB-CU-UP through the E1 interface. The access indication information includes but is not limited to the following:

[0184] -Control plane user ID: User ID assigned by the control plane

[0185] - User plane user ID: User ID assigned by the user plane

[0186] -Access completion indication: Completed

[0187] In step 918, after receiving the access completion indication information message, the gNB-CU-UP starts to transmit and receive the uplink and downlink data of the user.

[0188] By implementing the solution of the present disclosure, the following beneficial effects can be obtained:

[0189] 1) The disclosed solution can support automatically notifying the control plane of the connection mode configuration status of different PLMNs when the network connection mode changes, thereby avoiding the problem of decreased user experience caused by incorrect network connection mode configuration for users belonging to different PLMNs when the control plane configures the connection mode for the user in the CP / UP separation architecture.

[0190] 2) When switching from SA to NSA, the present disclosure introduces suspension indication information to avoid the delay and interruption problems caused by the bearer being deleted and then established in the existing solution, thereby reducing the user plane delay and improving the user perception.

[0191] 3) This solution has little modification to the terminal and has good backward compatibility and deployment feasibility. This solution enhances the existing protocol without introducing new protocol processes, and is relatively easy to implement.

[0192] A person skilled in the art will understand that all or part of the steps to implement the above embodiments may be accomplished by hardware or by instructing related hardware through a program, and the program may be stored in a computer-readable storage medium, and the above-mentioned storage medium may be a read-only memory, a disk or an optical disk, etc.

[0193] The description of the present disclosure is given for the purpose of illustration and description, and is not intended to be exhaustive or to limit the present disclosure to the disclosed form. Many modifications and variations will be apparent to those of ordinary skill in the art. The embodiments are selected and described in order to better illustrate the principles and practical applications of the present disclosure, and to enable those of ordinary skill in the art to understand the present disclosure and thereby design various embodiments with various modifications suitable for specific uses.

Claims

1. A method for configuring a connection mode, the method being performed by a first base station, comprising: After receiving the measurement information reported by the user terminal, the control plane entity of the first base station centralized unit determines, according to the terminal capability of the user terminal and the connection mode supported by the user plane entity of the first base station centralized unit, a connection mode that can be adopted by the user terminal after switching to the second base station, and sends a switching request to the second base station; After receiving the secondary base station adding request sent by the second base station, the control plane entity performs bearer configuration on the user plane entity according to the first bearer configuration information included in the secondary base station adding request, generates second bearer configuration information according to the configuration result, and instructs the user plane entity to update the bearer configuration according to the second bearer configuration information; The control plane entity generates first access configuration information according to the bearer configuration update result of the user plane entity, and sends the first access configuration information to the second base station, so that the second base station generates second access configuration information for the user terminal to access the second base station according to the first access configuration information, and sends a handover request response to the control plane entity, wherein the handover request response includes third bearer configuration information for describing the bearer configurations of the first base station and the second base station; After receiving the switching request response sent by the second base station, the control plane entity generates fourth bearer configuration information for bearer configuration of the user plane entity according to the third bearer configuration information included in the switching request response, and instructs the user plane entity to update the bearer configuration according to the fourth bearer configuration information.

2. The configuration method according to claim 1, wherein: The control plane entity determines that the connection mode that can be adopted by the user terminal after switching to the second base station includes: In a case where the user terminal only supports a single connection, the control plane entity determines that the user terminal establishes a single connection with the second base station after switching; When the user terminal supports dual connectivity and the core network connection capability of the user plane entity corresponding to the public land mobile network selected by the user terminal supports the 5G core network, the control plane entity determines that the user terminal establishes only a single connection with the second base station after switching; When the user terminal supports dual connections and the core network connection capability of the user plane entity corresponding to the public land mobile network selected by the user terminal is to support the evolved packet core network and the 5G core network, the control plane entity determines, based on the signal strength, whether the user terminal establishes a single connection with the second base station after switching, or establishes dual connections with the first base station and the second base station.

3. The configuration method according to claim 1, wherein: The handover request includes address information of the second base station and handover assistance information, wherein the handover assistance information includes a next generation application protocol identifier allocated to the user terminal by a first core network corresponding to the first base station.

4. The configuration method according to claim 3, wherein: In a case where the user terminal can only establish a single connection with the second base station after the handover, the handover request further includes a measurement result associated with the radio access technology used by the second base station; In a case where the user terminal can establish dual connectivity with the first base station and the second base station after the handover, the handover request further includes a measurement result associated with a radio access technology used by the first base station and a measurement result associated with a radio access technology used by the second base station; In the case where the handover cause is an evolved packet system fallback, the control plane entity does not include a measurement result in the handover request.

5. The configuration method according to claim 4, wherein: The measurement result includes an identifier of the measured cell, and at least one of a signal strength or a signal quality associated with the identifier of the measured cell, the signal strength includes at least one of a reference signal received power of a long term evolution cell or a reference signal received power of a synchronization signal of a new air interface cell, and the signal quality includes at least one of a reference signal received quality of a long term evolution cell or a reference signal received quality of a synchronization signal of a new air interface cell.

6. The configuration method according to claim 1, wherein: The control plane entity sending a handover request to the second base station includes: The control plane entity sends the switching request to the second base station through a first core network corresponding to the first base station and a second core network corresponding to the second base station.

7. The configuration method according to claim 3, wherein: The control plane entity performing bearer configuration on the user plane entity according to the first bearer configuration information includes: The control plane entity determines, when judging according to the next generation application protocol identifier that the user terminal has configured a context in the first base station and is performing a handover operation, whether the bearer of the first base station includes an evolved radio access bearer matching the protocol data unit session, wherein the quality of service information of the protocol data unit session is the same as the quality of service information of the matched evolved radio access bearer; If there is an evolved radio access bearer matching the protocol data unit session, the control plane entity determines that the protocol data unit session needs to be kept in the user plane entity after the user terminal is switched, and establishes a mapping relationship between the control plane entity and the matching evolved radio access bearer; If the protocol data unit session does not have a matching evolved radio access bearer, the control plane entity determines that the protocol data unit session needs to be deleted after the user terminal is switched; If the evolved radio access bearer does not have a matching protocol data unit session, a matching protocol data unit session is added to the evolved radio access bearer.

8. The configuration method according to claim 7, wherein: The control plane entity instructing the user plane entity to perform bearer configuration update according to the second bearer configuration information includes: The control plane entity sends a first bearer context modification request to the user plane entity; The user plane entity performs corresponding bearer configuration update according to the second bearer configuration information included in the first bearer context modification request, and stops sending data to the user terminal; The second bearer configuration information includes protocol data unit session information that needs to be deleted, protocol data unit session information that needs to be modified, and an evolved radio access bearer that needs to be added, wherein the protocol data unit session information that needs to be deleted includes a protocol data unit session identifier and a suspend operation indication, the protocol data unit session information that needs to be modified includes a protocol data unit session identifier, an evolved radio access bearer having a mapping relationship with the protocol data unit session, and a corresponding bearer type, and the evolved radio access bearer information that needs to be added includes an evolved radio access bearer identifier that needs to be added and corresponding quality of service information.

9. The configuration method according to claim 8, further comprising: After the user plane entity performs the corresponding bearer update operation, it sends a first bearer context modification response to the control plane entity, wherein the first bearer context modification response includes at least one of a bearer list that has been successfully added, a bearer list that has been successfully deleted, a bearer list that has been successfully modified, or a successful list that cannot be successfully accepted.

10. The configuration method according to claim 9, wherein: The control plane entity sending the first access configuration information to the second base station includes: The control plane entity encapsulates the first access configuration information in a radio resource control container, and sends the information to the second base station through an interface between the control plane entity and the second base station; The first access configuration information includes at least one item in a bearer list successfully added by the user plane entity, a bearer list successfully deleted, or a successful list that cannot be successfully accommodated.

11. The configuration method according to claim 1, wherein: Instructing the user plane entity to perform bearer configuration update according to the fourth bearer configuration information includes: The control plane entity sends a second bearer context modification request to the user plane entity, wherein the second bearer context modification request includes fourth bearer configuration information; The user plane entity configures the bearer to be added for uplink service and downlink service transmission according to the fourth bearer configuration information, and deletes the identifier of the bearer to be deleted and all cached data.

12. The configuration method according to claim 1, further comprising: After receiving the access request sent by the user terminal, the control plane entity sends access indication information to the user plane entity; After receiving the access indication information, the user plane entity processes the uplink data and downlink data of the user terminal using the configured bearer; The access indication information includes a control plane user identifier allocated by the control plane entity, a user plane user identifier allocated by the user plane entity, and an access completion indication.

13. The configuration method according to any one of claims 1 to 12, further comprising: The user plane entity determines its own core network connection capability according to the trigger information, and sends the core network connection capability information of the user plane entity to the control plane entity; The control plane entity determines the connection mode of the user terminal according to the core network connection capability information of the user plane entity itself.

14. The configuration method according to claim 13, wherein: The core network connection capability information includes the public core network support capability of the user plane entity and a list of public land mobile networks supported by the user plane entity, wherein the list of public land mobile networks includes a public land mobile network identifier and a core network support capability of each public land mobile network.

15. The configuration method according to claim 13, further comprising: When the core network connection capability of one or more public land mobile networks changes, the user plane entity sends updated core network connection capability information to the control plane entity, so that the control plane entity determines the connection mode of the user terminal according to the updated core network connection capability information.

16. The configuration method according to claim 14, wherein: In the case where the user plane entity supports an evolved packet core network, the user terminal selecting the user plane entity can only be configured with a non-standalone networking mode; In the case where the user plane entity supports the 5G core network, the user terminal selecting the user plane entity can only be configured with an independent networking mode; In the case where the user plane entity supports the evolved packet core network and the 5G core network, the user terminal that selects the user plane entity can configure at least one of the non-independent networking mode or the independent networking mode as needed.

17. A base station, comprising: a memory configured to store instructions; A processor is coupled to the memory, and the processor is configured to execute the method according to any one of claims 1 to 16 based on instructions stored in the memory.

18. A method for configuring a connection mode, the method being performed by a second base station, comprising: After receiving a handover request sent by a control plane entity of a first base station central unit, determining whether to use the first base station as a secondary base station of a user terminal; In the case where the first base station is used as a secondary base station, sending a secondary base station adding request to the control plane entity, wherein the secondary base station adding request includes first bearer configuration information associated with a service that needs to be carried by the first base station, so that the control plane entity performs bearer configuration on a user plane entity of the first base station according to the first bearer configuration information, generates second bearer configuration information according to the configuration result, instructs the user plane entity to perform bearer configuration update according to the second bearer configuration information, generates first access configuration information according to the bearer update result of the user plane entity, and sends the first access configuration information to the second base station; According to the first access configuration information sent by the control plane entity, second access configuration information for the user terminal to access the second base station is generated, and a switching request response is sent to the control plane entity, wherein the switching request response includes third bearer configuration information for describing the bearer configuration of the first base station and the second base station, so that the control plane entity generates fourth bearer configuration information for bearer configuration of the user plane entity according to the third bearer configuration information, and instructs the user plane entity to update the bearer configuration according to the fourth bearer configuration information.

19. The configuration method according to claim 18, wherein: The determining whether to use the first base station as a secondary base station of the user terminal includes: When the terminal capability of the user terminal does not support adding a secondary connection during the handover process, determining not to use the first base station as a secondary base station for the user terminal; When the terminal capability of the user terminal supports adding a secondary connection during the switching process, and the switching reason is an evolved packet system fallback, and there is no measurement result, determining to use the first base station as a secondary base station for the user terminal; If the terminal capability of the user terminal supports adding a secondary connection during the handover process and the signal strength of the cell to which the first base station belongs is the highest in the measurement result, it is determined to use the first base station as a secondary base station for the user terminal.

20. The configuration method according to claim 18, wherein: The first bearer configuration information includes a list of services carried by the first base station and a next-generation application protocol identifier allocated to the user terminal by the first core network corresponding to the first base station, wherein the list of services carried by the first base station includes the identifier of each evolved wireless access bearer and the corresponding service quality configuration information.

21. The configuration method according to claim 20, wherein: After the second access configuration information is generated, the method further includes: placing the first access configuration information into a first radio resource control container, so as to instruct the user terminal to access the first base station during the handover process; The second access configuration information is placed in a second radio resource control container to instruct the user terminal to access the second base station during the handover process.

22. The configuration method according to claim 21, wherein: The third bearer configuration information includes a list of bearers that can be accepted by the first base station, a list of bearers that can be accepted by the second base station, a list of bearers that cannot be accepted by the first base station, and a list of bearers that cannot be accepted by the second base station.

23. The configuration method according to claim 18, wherein: Sending a handover request response to the control plane entity includes: The switching request response is sent to the first base station through a second core network corresponding to the second base station and a first core network corresponding to the first base station.

24. A base station, comprising: a memory configured to store instructions; A processor is coupled to the memory, and the processor is configured to execute the method according to any one of claims 18 to 23 based on instructions stored in the memory.

25. A communication system comprising: The first base station is the base station according to claim 17; The second base station is the base station described in claim 24.

26. The communication system according to claim 25, further comprising a first core network corresponding to the first base station and a second core network corresponding to the second base station; The first core network maps the protocol data unit session included in the handover request sent by the first base station to evolved radio access bearer information, records a mapping relationship between the protocol data unit session identifier and the evolved radio access bearer identifier, writes the evolved radio access bearer information into the handover request so as to update the handover request, and sends the updated handover request to the second core network; The second core network sends the updated switching request to the second base station.

27. The communication system according to claim 26, wherein: The second core network sends the handover request response sent by the second base station to the first core network; The first core network converts the evolved radio access bearer identifier included in the third bearer configuration information in the handover request response into a protocol data unit session identifier according to a mapping relationship between the protocol data unit session identifier and the evolved radio access bearer identifier, so as to generate an updated handover request response; The first core network sends the updated handover request response to the first base station.

28. A computer-readable storage medium, wherein: The computer-readable storage medium stores computer instructions, and when the instructions are executed by a processor, the method according to any one of claims 1-16 and 18-23 is implemented.

Images