WO2016197845A1 - Processing method and device for secondary evolved node b (senb) - Google Patents

Abstract

A processing method for a secondary evolved Node B (SeNB), comprising: a mobility management entity (MME) receiving a first request message from a master evolved Node B (MeNB), wherein the first request message is used for requesting to conduct dual connection processing on the SeNB; and the MME sending a second request message to the SeNB according to the first request message, wherein the second request message is used for requesting the SeNB to conduct dual connection processing. By means of the solution, the problem existing in the related art that a dual connection of an evolved Node B cannot be realized when no X2 interface exists is solved, so that the effect of the dual connection of the evolved Node B also can be realized in the case where no X2 interface exists.

Description

Processing method and device of secondary base station SeNB Technical field

The present application relates to, but is not limited to, the field of communications, and in particular, to a method and an apparatus for processing a secondary base station SeNB.

Background technique

1 is a schematic diagram of an overall architecture of a long-term evolution system in the related art. As shown in FIG. 1 , a Long Term Evolution (LTE) architecture includes: a Mobility Management Entity (MME) and a Serving Gateway. (Serving GetWay, abbreviated as SGW), is a Uu interface between a user equipment or a user equipment (UE) and a base station (eNodeB, eNB for short), and S1-MME between the eNB and the MME (S1 for the The control plane interface is an S1-U interface between the eNB and the SGW, and an X2-U (X2-User plane) and an X2-C (X2-Control plane) interface between the eNBs. In LTE, the protocol stack of the S1-MME interface is divided into the following protocol layers from the bottom to the top: L1 protocol, L2 protocol, Internet Protocol (IP), and Stream Control Transmission Protocol (Stream Control Transmission Protocol). It is abbreviated as SCTP) and S1 Application Protocol (S1-Application Protocol, S1-AP for short). In LTE, the protocol stack of the S1-U interface is divided into the following protocol layers from the bottom to the top: L1 protocol, L2 protocol, user data protocol/Internet protocol (UDP/IP), GPRS tunneling protocol-user plane (GPRS Tunneling) Protocol-User plane, referred to as GTP-U.

At present, due to the lack of spectrum resources and the surge of mobile users' large-traffic services, in order to increase user throughput and enhance mobile performance, the demand for hotspot coverage using high-frequency points such as 3.5 GHz is becoming more and more obvious, and the use of low-power nodes becomes new. Application scenario. However, since the signal attenuation at the high frequency point is relatively strong, the coverage of the new cell is relatively small and does not co-site with the existing cell, therefore, if the user moves between these new cells, or in the new cell and existing The small interval movement will inevitably lead to frequent handover procedures, causing frequent transmission of user information between base stations, which causes a large signaling impact on the core network, thereby suppressing the introduction of a large number of small cellular base stations on the wireless side. 2 is a schematic diagram of an overall architecture of a small cell base station system in the related art, as shown in FIG. 2, the architecture package Included: MME, SGW, Uu interface between UE and eNB, S1-MME interface between MeNB and MME, S1- between primary base station (MeNB, Master eNB), secondary base station (SeNB, Secondary eNB) and SGW The U interface, between the MeNB and the SeNB, is an Xn interface. User data can be delivered from the core network to the user through the MeNB, or from the core network to the user through the SeNB, that is, the 3C and 1A architectures. After the user accesses the MeNB, the dual connection can be implemented by adding, modifying, and deleting the SeNB through the X2 interface.

Due to network deployment restrictions or constraints between different vendors, the X2 interface is not necessarily implemented in actual network operations. However, when the X2 interface does not exist, data splitting through the direct interface between the MeNB and the SeNB cannot be implemented, and therefore the 3C architecture cannot be implemented, thereby making it impossible to implement dual connectivity of the base station.

When the X2 interface does not exist in the related art, the problem of dual connectivity of the base station cannot be achieved, and an effective solution has not been proposed yet.

Summary of the invention

The following is an overview of the topics detailed in this document. This Summary is not intended to limit the scope of the claims.

The embodiments of the present invention provide a method and a device for processing a secondary base station (SeNB), so as to solve at least the problem that the double connection of the base station cannot be implemented when there is no X2 interface existing in the related art.

According to an aspect of the present invention, a method for processing a secondary base station (SeNB) is provided, comprising: a mobility management entity (MME) receiving a first request message from a primary base station (MeNB), wherein the first The request message is used to request a dual connectivity process for the SeNB; the MME sends a second request message to the SeNB according to the first request message, where the second request message is used to request the SeNB to perform dual connectivity processing. .

Optionally, the receiving, by the MME, the first request message from the MeNB, the first request message is received by using a first S1 interface with the MeNB, where the first request message includes one of the following: Routing information of the MeNB, routing information of the SeNB, and processing information required for performing dual connectivity processing on the SeNB; a base station configuration conversion message (eNB CONFIGURATION TRANSFER) encapsulating the processing information; and/or , the MME root The sending the second request message to the SeNB according to the first request message includes: sending the second request message to the SeNB by using a second S1 interface with the SeNB, where the second The request message includes one of the following: routing information of the MeNB, routing information of the SeNB, and the processing information; and a mobility management entity configuration conversion message (MME CONFIGURATION TRANSFER) encapsulating the processing information.

Optionally, after the MME sends the second request message to the SeNB according to the first request message, the method further includes:

The MME receives the first response message from the SeNB by using the second S1 interface, where the first response message includes at least one of the following: routing information of the MeNB, routing information of the SeNB, and a pair Processing response information after the SeNB performs dual connectivity processing; an eNB CONFIGURATION TRANSFER encapsulating the processing response information;

The MME sends a second response message to the MeNB by using the first S1 interface according to the first response message, where the second response message includes at least one of: routing information of the MeNB, the Routing information of the SeNB and the processing response information; an MME CONFIGURATION TRANSFER encapsulating the processing response information.

Optionally, before the receiving, by the MME, the first request message from the MeNB, the method further includes:

The MME receives, by using the second S1 interface, a first processing requirement message from the SeNB for indicating that the SeNB needs to be processed, where the first processing requirement message includes at least one of the following: Routing information of the MeNB, routing information of the SeNB, and processing demand information; an eNB CONFIGURATION TRANSFER encapsulating the processing demand information;

The MME sends a second processing requirement message to the MeNB by using the first S1 interface according to the first processing requirement message, where the second processing requirement message includes at least one of the following: routing information of the MeNB And routing information and processing requirement information of the SeNB; and an MME CONFIGURATION TRANSFER encapsulating the processing requirement information.

Optionally, the receiving, by the MME, the first request message from the primary base station MeNB, the first request message is received by using a third S1 interface with the MeNB, where the first request message includes the The S1 access point identifier allocated by the MeNB and/or the MME for the terminal (UE) Knowledge (APID), routing information of the SeNB, and processing information required for performing dual connectivity processing on the SeNB; and/or, the MME sends a second request to the SeNB according to the first request message The message includes: sending, by the fourth S1 interface with the SeNB, the second request message to the SeNB, where the second request message includes the S1 allocated by the MME and/or the SeNB for the UE APID and the processing information.

Optionally, after the MME sends the second request message to the SeNB according to the first request message, the method further includes:

The MME receives, by using the fourth S1 interface, a third response message that is returned by the SeNB, where the third response message includes an S1 APID and a location that the SeNB and/or the MME allocate for the UE. Routing information of the MeNB and processing response information after performing dual connectivity processing on the SeNB;

The MME sends a fourth response message to the MeNB by using the third S1 interface according to the third response message, where the fourth response message includes the MME and/or the MeNB is the UE. The assigned S1 APID and the processing response information.

Optionally, before the receiving, by the MME, the first request message from the MeNB, the method further includes:

The MME receives, by using the fourth S1 interface, a third processing requirement message from the SeNB for indicating that the SeNB needs to be processed, where the third processing requirement message includes the SeNB and/or the Describe an S1 APID allocated by the MME for the UE, routing information of the MeNB, and processing requirement information;

The MME sends a fourth processing requirement message to the MeNB by using the third S1 interface according to the third processing requirement message, where the fourth processing requirement message includes the MME and/or the MeNB is The S1 APID allocated by the UE and the processing requirement information.

Optionally, the processing information includes reject processing information that refuses to perform dual connectivity processing on the SeNB.

According to another aspect of the present invention, a method for processing a secondary base station (SeNB) is provided, including: a primary base station (MeNB) transmitting a request for requesting dual connectivity processing to an SeNB to a mobility management entity (MME) a request message to request the MME to send a second request to the SeNB The message, the second request message is used to request the SeNB to perform dual connectivity processing.

Optionally, the sending, by the MeNB, the first request message to the MME includes: sending, by the MeNB, the first request message to the MME by using a first S1 interface with the MME, where The first request message includes one of: routing information of the MeNB, routing information of the SeNB, and processing information required for performing dual connectivity processing on the SeNB; and base station configuration conversion encapsulating the processing information. The message (eNB CONFIGURATION TRANSFER); and/or the second request message is sent by the MME to the SeNB through a second S1 interface between the MME and the SeNB, where the second request message The method includes one of the following: routing information of the MeNB, routing information of the SeNB, and the processing information; and a mobility management entity configuration conversion message (MME CONFIGURATION TRANSFER) encapsulating the processing information.

Optionally, after the sending, by the MeNB, the first request message to the MME, the method further includes: receiving, by the MeNB, a second response message from the MME by using the first S1 interface, where The second response message is obtained by the MME according to the received first response message from the SeNB; the first response message includes at least one of the following: routing information of the MeNB, routing information of the SeNB, and a pair The SeNB performs the dual-link processing processing response information; the eNB CONFIGURATION TRANSFER is encapsulated with the processing response information; the second response message includes at least one of the following: the routing information of the MeNB, and the routing information of the SeNB And processing the response information; MME CONFIGURATION TRANSFER encapsulating the processing response information.

Optionally, before the sending, by the MeNB, the first request message to the MME, the method further includes: receiving, by the MeNB, a second processing requirement message from the MME by using the first S1 interface, where The second processing requirement message is obtained by the MME according to the received first processing requirement message from the SeNB; the first processing requirement message includes at least one of: routing information of the MeNB, and information of the SeNB The routing information and the processing requirement information; the eNB CONFIGURATION TRANSFER that encapsulates the processing requirement information; the second processing requirement message includes at least one of: routing information of the MeNB, routing information of the SeNB, and processing requirement information; An MME CONFIGURATION TRANSFER encapsulating the processing demand information.

Optionally, the sending, by the MeNB, the first request message to the MME includes: sending, by the MeNB, the first request message to the MME by using a third S1 interface with the MME, where The first request message includes an S1 access point identifier (APID) allocated by the MeNB and/or the MME for the UE, routing information of the SeNB, and processing information required for performing dual connectivity processing on the SeNB. And/or, the second request message is sent by the MME to the SeNB through a fourth S1 interface with the SeNB, wherein the second request message includes the MME and/or the The S1 APID allocated by the SeNB for the UE and the processing information.

Optionally, after the sending, by the MeNB, the first request message to the MME by using the third S1 interface with the MME, the method further includes: the MeNB passing the third S1 interface Receiving a fourth response message from the MME, where the fourth response message is obtained by the MME according to the received third response message from the SeNB, where the third response message includes the SeNB And the S1 APID allocated by the MME to the UE, the routing information of the MeNB, and the processing response information after performing dual connectivity processing on the SeNB, where the fourth response message includes the MME and/or The S1 APID and the processing response information allocated by the MeNB to the UE.

Optionally, before the sending, by the MeNB, the first request message to the MME, the method further includes: receiving, by the MeNB, a fourth processing requirement message from the MME by using the third S1 interface, where The fourth processing requirement message is determined by the MME according to the received third processing requirement message from the SeNB for indicating that the SeNB needs to be processed, where the third processing requirement message includes the SeNB and And the S1 APID allocated by the MME for the UE, the routing information of the MeNB, and the processing requirement information, where the fourth processing requirement message includes the S1 APID and the MME and/or the MeNB allocated to the UE. Process demand information.

Optionally, the processing information includes reject processing information that refuses to perform dual connectivity processing on the SeNB.

According to another aspect of the present invention, a method for processing a secondary base station (SeNB) is provided, including: the SeNB receives a second request message from a mobility management entity (MME), where the second request message is The MME determines, according to the received first request message from the primary base station (MeNB), the first request message is used to request dual connectivity processing for the SeNB, and the second request message is used to request the SeNB to perform dual Connection processing.

Optionally, the receiving, by the SeNB, the second request message from the MME includes: receiving, by the SeNB, the second request message from the MME by using a second S1 interface with the MME, where The second request message includes one of: routing information of the MeNB, routing information of the SeNB, and processing information required for performing dual connectivity processing on the SeNB; and the mobile device encapsulating the processing information a MME CONFIGURATION TRANSFER; and/or the first request message is sent by the MeNB to the MME through a first S1 interface between the MeNB and the MME, where The first request message includes one of the following: routing information of the MeNB, routing information of the SeNB, and the processing information; and a base station configuration conversion message (eNB CONFIGURATION TRANSFER) encapsulating the processing information.

Optionally, after the SeNB receives the second request message from the MME, the method further includes: sending, by the SeNB, the first response message to the MME by using the second S1 interface, where The first response message includes at least one of the following: routing information of the MeNB, routing information of the SeNB, and processing response information after performing dual connectivity processing on the SeNB; and an eNB encapsulating the processing response information. The first response message is used to indicate that the MME sends a second response message to the MeNB, where the second response message includes at least one of: routing information of the MeNB, and routing information of the SeNB. And processing the response information; MME CONFIGURATION TRANSFER encapsulating the processing response information.

Optionally, before the receiving, by the SeNB, the second request message from the MME, the method further includes: sending, by the SeNB, the first processing requirement message to the MME by using the second S1 interface, where The first processing requirement message includes at least one of: routing information of the MeNB, routing information of the SeNB, and processing requirement information; an eNB CONFIGURATION TRANSFER encapsulating the processing requirement information; the first processing requirement The message is used to indicate that the MME sends a second processing requirement message to the MeNB, where the second processing requirement message includes at least one of: routing information of the MeNB, routing information of the SeNB, and processing requirement information; There is an MME CONFIGURATION TRANSFER that processes the demand information.

Optionally, the receiving, by the SeNB, the second request message from the MME includes: The SeNB receives the second request message from the MME by using a fourth S1 interface with the MME, where the second request message includes the S1 and/or the S1 allocated by the MME to the UE. An access point identifier (APID) and processing information required for performing dual connectivity processing on the SeNB; and/or, the first request message is used by the MeNB to pass between the MeNB and the MME The S1 interface is sent to the MME, where the first request message includes an S1 APID allocated by the MME and/or the MeNB for the UE, routing information of the SeNB, and the processing information.

Optionally, after the SeNB receives the second request message from the MME, the method further includes: sending, by the SeNB, a third response message to the MME by using the fourth S1 interface, where The third response message includes S1 APID allocated by the SeNB and/or the MME for the UE, routing information of the MeNB, and processing response information after performing dual connectivity processing on the SeNB, where The third response message is used to indicate that the MME sends a fourth response message to the MeNB, where the fourth response message includes an S1 APID allocated by the MME and/or the MeNB for the UE, and the processing response information. .

Optionally, before the SeNB receives the second request message from the MME, the method further includes: sending, by the SeNB, the MME to the MME by using the fourth S1 interface, a third processing requirement message that is processed by the SeNB, to indicate that the MME sends a fourth processing requirement message to the MeNB, where the third processing requirement message includes the SeNB and/or the MME allocates the UE The S1 APID, the routing information of the MeNB, and the processing requirement information, where the fourth processing requirement message includes an S1 APID and the processing requirement information allocated by the MME and/or the MeNB to the UE.

Optionally, the processing information includes reject processing information that refuses to perform dual connectivity processing on the SeNB.

According to another aspect of the present invention, a processing apparatus of a secondary base station (SeNB) is provided, where the apparatus is applied to a mobility management entity (MME), including:

a first receiving module, configured to receive a first request message from a primary base station (MeNB), where the first request message is used to request dual connectivity processing for the SeNB;

The first sending module is configured to send a second request message to the SeNB according to the first request message, where the second request message is used to request the SeNB to perform dual connectivity processing.

Optionally, the first receiving module includes: a first receiving unit, configured to receive the first request message by using a first S1 interface with the MeNB, where the first request message includes the following a routing information of the MeNB, routing information of the SeNB, and processing information required for performing dual connectivity processing on the SeNB; a base station configuration switching message (eNB CONFIGURATION TRANSFER) encapsulating the processing information; and The first sending module includes: a first sending unit, configured to send the second request message to the SeNB by using a second S1 interface with the SeNB, where the second request message The method includes one of: routing information of the MeNB, routing information of the SeNB, and the processing information; and a mobility management entity configuration conversion message (MME CONFIGURATION TRANSFER) encapsulating the processing information.

Optionally, the device further includes:

a second receiving module, configured to: after the first sending module sends the second request message to the SeNB according to the first request message, receive a first response from the SeNB by using the second S1 interface a message, where the first response message includes at least one of: routing information of the MeNB, routing information of the SeNB, and processing response information after performing dual connectivity processing on the SeNB; and the processing response is encapsulated Information eNB CONFIGURATION TRANSFER;

a second sending module, configured to send a second response message to the MeNB by using the first S1 interface according to the first response message, where the second response message includes at least one of: a route of the MeNB Information, routing information of the SeNB, and the processing response information; an MME CONFIGURATION TRANSFER encapsulating the processing response information.

Optionally, the device further includes:

a third receiving module, configured to receive, by the second S1 interface, the SeNB from the SeNB to indicate that the SeNB needs to be performed before the first receiving module receives the first request message from the MeNB Processing the first processing requirement message, where the first processing requirement message includes at least one of: routing information of the MeNB, routing information of the SeNB, and processing requirement information; and an eNB encapsulating the processing requirement information CONFIGURATION TRANSFER;

a third sending module, configured to pass the first S1 interface according to the first processing requirement message Transmitting, by the MeNB, a second processing requirement message, where the second processing requirement message includes at least one of: routing information of the MeNB, routing information of the SeNB, and processing requirement information; and the processing requirement is encapsulated MME CONFIGURATION TRANSFER of the message.

Optionally, the first receiving module includes: a second receiving unit, configured to receive the first request message by using a third S1 interface with the MeNB, where the first request message includes the The S1 APID allocated by the MeNB and/or the MME for the UE, the routing information of the SeNB, and processing information required for performing dual connectivity processing on the SeNB; and/or the first sending module includes: a second sending unit, configured to send the second request message to the SeNB by using a fourth S1 interface with the SeNB, where the second request message includes the MME and/or the SeNB is a UE The assigned S1 APID and the processing information.

Optionally, the device further includes:

a fourth receiving module, configured to: after the first sending module sends the second request message to the SeNB according to the first request message, receive, by using the fourth S1 interface, a third response returned by the SeNB a message, where the third response message includes an S1 APID allocated by the SeNB and/or the MME for the UE, routing information of the MeNB, and processing response information after performing dual connectivity processing on the SeNB. ;

a fourth sending module, configured to send a fourth response message to the MeNB by using the third S1 interface according to the third response message, where the fourth response message includes the MME and/or the MeNB The S1 APID assigned to the UE and the processing response information.

Optionally, the device further includes:

a fifth receiving module, configured to receive, by the fourth S1 interface, the S1 interface, by using the fourth S1 interface, to indicate that the SeNB needs to be performed, before the first receiving module receives the first request message from the MeNB a third processing request message, where the third processing requirement message includes an S1 APID allocated by the SeNB and/or the MME for the UE, routing information and processing requirement information of the MeNB;

a fifth sending module, configured to send, according to the third processing requirement message, a fourth processing requirement message to the MeNB by using the third S1 interface, where the fourth processing requirement message includes the MME and/or the The S1 APID allocated by the MeNB for the UE and the processing requirement information.

Optionally, the processing information includes reject processing information that refuses to perform dual connectivity processing on the SeNB.

According to another aspect of the present invention, a processing apparatus of a secondary base station (SeNB) is provided, where the apparatus is applied to a primary base station (MeNB), including: a sixth sending module, configured to be to a mobility management entity ( The MME) sends a first request message for requesting dual connectivity processing to the SeNB, to request the MME to send a second request message to the SeNB, where the second request message is used to request the SeNB to perform dual connectivity processing.

Optionally, the sixth sending module includes: a third sending unit, configured to send the first request message to the MME by using a first S1 interface with the MME, where the first request The message includes one of the following: routing information of the MeNB, routing information of the SeNB, and processing information required for performing dual connectivity processing on the SeNB; and base station configuration conversion message encapsulating the processing information (eNB CONFIGURATION) And the second request message is sent by the MME to the SeNB by using a second S1 interface between the MME and the SeNB, where the second request message includes the following a routing information of the MeNB, routing information of the SeNB, and the processing information; and a mobility management entity configuration conversion message (MME CONFIGURATION TRANSFER) encapsulating the processing information.

Optionally, the device further includes: a sixth receiving module, configured to receive, after the first sending message is sent by the sixth sending module to the MME, the first S1 interface to receive the MME from the MME a second response message, wherein the second response message is obtained by the MME according to the received first response message from the SeNB; the first response message includes at least one of: routing information of the MeNB, The routing information of the SeNB and the processing response information after performing the dual connectivity processing on the SeNB; the eNB CONFIGURATION TRANSFER encapsulating the processing response information; the second response message includes at least one of the following: routing information of the MeNB The routing information of the SeNB and the processing response information; an MME CONFIGURATION TRANSFER encapsulating the processing response information.

Optionally, the device further includes: a seventh receiving module, configured to receive, by the first S1 interface, the MME from the MME before the sixth sending module sends the first request message to the MME a second processing requirement message, where the second processing requirement message is obtained by the MME according to the received first processing requirement message from the SeNB; the first processing requirement message The at least one of the following: the routing information of the MeNB, the routing information of the SeNB, and the processing requirement information; the eNB CONFIGURATION TRANSFER encapsulating the processing requirement information; the second processing requirement message includes at least one of the following: The routing information of the MeNB, the routing information of the SeNB, and the processing requirement information; and an MME CONFIGURATION TRANSFER encapsulating the processing requirement information.

Optionally, the sixth sending module includes: a fourth sending unit, configured to send the first request message to the MME by using a third S1 interface with the MME, where the first request The message includes an S1 access point identifier APID allocated by the MeNB and/or the MME for the terminal UE, routing information of the SeNB, and processing information required for performing dual connectivity processing on the SeNB; and/or, The second request message is sent by the MME to the SeNB through a fourth S1 interface with the SeNB, where the second request message includes the MME and/or the SeNB allocates a terminal UE The S1 access point identifies the APID and the processing information.

Optionally, the apparatus further includes: an eighth receiving module, configured to: after the sixth sending module sends the first request message to the MME by using the third S1 interface with the MME Receiving, by the third S1 interface, a fourth response message from the MME, where the fourth response message is obtained by the MME according to the received third response message from the SeNB, where the The third response message includes the S1 APID allocated by the SeNB and/or the MME for the UE, routing information of the MeNB, and processing response information after performing dual connectivity processing on the SeNB, where the fourth response message is included. The S1 APID and the processing response information allocated by the MME and/or the MeNB to the UE are included.

Optionally, the device further includes: a ninth receiving module, configured to receive, by the third S1 interface, the MME from the MME before the sixth sending module sends the first request message to the MME a fourth processing requirement message, where the fourth processing requirement message is determined by the MME according to the received third processing demand message from the SeNB for indicating that the SeNB needs to be processed, the third The processing requirement message includes the S1 APID allocated by the SeNB and/or the MME for the UE, routing information and processing requirement information of the MeNB, and the fourth processing requirement message includes the MME and/or the MeNB S1 APID and processing demand information assigned to the UE.

Optionally, the processing information includes a reject that refuses to perform dual connectivity processing on the SeNB. Information.

According to another aspect of the present invention, a processing apparatus of a secondary base station (SeNB) is provided, where the apparatus is applied to an SeNB, including: a tenth receiving module, configured to receive from a mobility management entity (MME) a second request message, where the second request message is determined by the MME according to the received first request message from the primary base station (MeNB), where the first request message is used to request dual connectivity processing for the SeNB, The second request message is used to request the SeNB to perform dual connectivity processing.

Optionally, the tenth receiving module includes: a third receiving unit, configured to receive the second request message from the MME by using a second S1 interface with the MME, where the second The request message includes one of: routing information of the MeNB, routing information of the SeNB, and processing information required for performing dual connectivity processing on the SeNB; mobility management entity configuration conversion encapsulating the processing information The message (MME CONFIGURATION TRANSFER); and/or the first request message is sent by the MeNB to the MME through a first S1 interface between the MeNB and the MME, where the first request message The method includes one of: routing information of the MeNB, routing information of the SeNB, and the processing information; and a base station configuration conversion message (eNB CONFIGURATION TRANSFER) encapsulating the processing information.

Optionally, the device further includes: a seventh sending module, configured to send, after the tenth receiving module receives the second request message from the MME, to the MME by using the second S1 interface a first response message, where the first response message includes at least one of: routing information of the MeNB, routing information of the SeNB, and processing response information after performing dual connectivity processing on the SeNB; The eNB is configured to send a second response message to the MeNB, where the second response message includes at least one of: routing information of the MeNB. The routing information of the SeNB and the processing response information; an MME CONFIGURATION TRANSFER encapsulating the processing response information.

Optionally, the device further includes: an eighth sending module, configured to send, by using the second S1 interface, the MME, before the tenth receiving module receives the second request message from the MME a first processing requirement message, where the first processing requirement message includes at least one of: routing information of the MeNB, routing information of the SeNB, and processing requirement information; The eNB is configured to send the second processing demand message to the MeNB, where the second processing requirement message includes at least one of the following: Routing information of the MeNB, routing information of the SeNB, and processing requirement information; an MME CONFIGURATION TRANSFER encapsulating the processing requirement information.

Optionally, the tenth receiving module includes: a fourth receiving unit, configured to receive the second request message from the MME by using a fourth S1 interface with the MME, where the second The request message includes an S1 access point identifier (APID) allocated by the SeNB and/or the MME for the UE, and processing information required for performing dual connectivity processing on the SeNB; and/or the first request The message is sent by the MeNB to the MME by using a third S1 interface between the MeNB and the MME, where the first request message includes the S1 allocated by the MME and/or the MeNB to the UE. APID, routing information of the SeNB, and the processing information.

Optionally, the device further includes: a ninth sending module, configured to send, after the tenth receiving module receives the second request message from the MME, to the MME by using the fourth S1 interface a third response message, where the third response message includes the S1 APID allocated by the SeNB and/or the MME for the UE, routing information of the MeNB, and dual connectivity processing performed on the SeNB. Processing a response message, the third response message is used to indicate that the MME sends a fourth response message to the MeNB, where the fourth response message includes the S1 allocated by the MME and/or the MeNB to the UE. APID and the processing response information.

Optionally, the apparatus further includes: a tenth sending module, configured to send, by the fourth S1 interface, to the MME, before the tenth receiving module receives the second request message from the MME a third processing requirement message for indicating that the SeNB needs to be processed, to indicate that the MME sends a fourth processing requirement message to the MeNB, where the third processing requirement message includes the SeNB and/or the An S1 APID allocated by the MME for the UE, routing information of the MeNB, and processing requirement information, where the fourth processing requirement message includes an S1 APID allocated by the MME and/or the MeNB for the UE, and the Process demand information.

Optionally, the processing information includes reject processing information that refuses to perform dual connectivity processing on the SeNB.

The embodiment of the invention further provides a computer readable storage medium, which stores a computer executable finger The processing method applied to the secondary base station on the MME side is implemented when the computer executable instructions are executed.

The embodiment of the present invention further provides a computer readable storage medium storing computer executable instructions, which are implemented to implement a processing method applied to a secondary base station on the MeNB side.

The embodiment of the invention further provides a computer readable storage medium storing computer executable instructions, which are implemented to implement a processing method applied to a secondary base station on the SeNB side.

The first request message from the primary base station (MeNB) is received by the mobility management entity (MME), where the first request message is used to request dual connectivity processing for the SeNB, and the MME is configured according to the embodiment of the present invention. The first request message sends a second request message to the SeNB, where the second request message is used to request the SeNB to perform dual connectivity processing. The problem that the double connection of the base station cannot be realized when the X2 interface does not exist in the related art is solved, thereby achieving the effect of realizing the double connection of the base station in the absence of the X2 interface.

Other aspects will be apparent upon reading and understanding the drawings and detailed description.

BRIEF abstract

The drawings described herein are intended to provide a further understanding of the present application, and are intended to be a part of this application. In the drawing:

1 is a schematic diagram of an overall architecture of a long term evolution system in related art;

2 is a schematic diagram of an overall architecture of a small cell base station system in the related art;

3 is a flowchart of a processing method of a first type of SeNB according to an embodiment of the present invention;

4 is a flowchart of a method for processing a second type of SeNB according to an embodiment of the present invention;

FIG. 5 is a flowchart of a method for processing a third SeNB according to an embodiment of the present invention; FIG.

FIG. 6 is a flowchart of a method for implementing dual connectivity of a base station according to Embodiment 1 of the present invention; FIG.

7 is a flowchart of a method for implementing dual connectivity of a base station according to Embodiment 2 of the present invention;

FIG. 8 is a flowchart of a method for implementing dual connectivity of a base station according to Embodiment 3 of the present invention; FIG.

9 is a flowchart of a method for implementing dual connectivity of a base station according to Embodiment 4 of the present invention;

10 is a flowchart of a method for implementing dual connectivity of a base station according to Embodiment 5 of the present invention;

11 is a structural block diagram of a processing apparatus of a first type of SeNB according to an embodiment of the present invention;

FIG. 12 is a structural block diagram 1 of a first receiving module 112 and/or a first transmitting module 114 in a processing apparatus of a first type of SeNB according to an embodiment of the present invention;

FIG. 13 is a block diagram 1 of an optional structure of a processing apparatus of a first type of SeNB according to an embodiment of the present invention; FIG.

14 is a block diagram 2 of an optional structure of a processing apparatus of a first type of SeNB according to an embodiment of the present invention;

FIG. 15 is a second structural block diagram of a first receiving module 112 and/or a first transmitting module 114 in a processing apparatus of a first type of SeNB according to an embodiment of the present invention;

16 is a block diagram 3 of an optional structure of a processing apparatus of a first type of SeNB according to an embodiment of the present invention;

17 is a block diagram 4 of an optional structure of a processing apparatus of a first type of SeNB according to an embodiment of the present invention;

FIG. 18 is a structural block diagram of a processing apparatus of a second type of SeNB according to an embodiment of the present invention; FIG.

FIG. 19 is a structural block diagram 1 of a sixth sending module 182 in a processing apparatus of a second type of SeNB according to an embodiment of the present invention;

20 is a block diagram 1 of an optional structure of a processing apparatus of a second type of SeNB according to an embodiment of the present invention;

21 is a block diagram 2 of an optional structure of a processing apparatus of a second type of SeNB according to an embodiment of the present invention;

FIG. 22 is a second structural block diagram of a sixth transmitting module 182 in a processing apparatus of a second type of SeNB according to an embodiment of the present invention;

23 is a block diagram 3 of an optional structure of a processing apparatus of a second type of SeNB according to an embodiment of the present invention;

FIG. 24 is a block diagram 4 of an optional structure of a processing apparatus of a second type of SeNB according to an embodiment of the present invention; FIG.

25 is a structural block diagram of a processing apparatus of a third type of SeNB according to an embodiment of the present invention;

FIG. 26 is a structural block diagram 1 of a tenth receiving module 252 in a processing apparatus of a third type of SeNB according to an embodiment of the present invention;

27 is a block diagram 1 of an optional structure of a processing apparatus of a third type of SeNB according to an embodiment of the present invention;

28 is a block diagram 2 of an optional structure of a processing apparatus of a third type of SeNB according to an embodiment of the present invention;

29 is a structural block diagram 2 of a tenth receiving module 252 in a processing apparatus of a third type of SeNB according to an embodiment of the present invention;

30 is a block diagram 3 of an optional structure of a processing apparatus of a third type of SeNB according to an embodiment of the present invention;

FIG. 31 is a block diagram showing an optional structure of a processing apparatus of a third type of SeNB according to an embodiment of the present invention.

Embodiments of the invention

The present application will be described in detail below with reference to the drawings in conjunction with the embodiments. It should be noted that the embodiments in the present application and the features in the embodiments may be combined with each other without conflict.

It should be noted that the terms "first", "second" and the like in the specification and claims of the present application and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or order.

A method for processing a secondary base station (SeNB) is provided in this embodiment. FIG. 3 is a flowchart of a method for processing a first type of SeNB according to an embodiment of the present invention. As shown in FIG. 3, the method includes the following steps:

Step S302, the mobility management entity (MME) receives a first request message from a primary base station (MeNB), where the first request message is used to request dual connectivity processing for the SeNB;

Step S304, the MME sends a second request message to the SeNB according to the first request message, where the second request message is used to request the SeNB to perform dual connectivity processing.

Through the above steps, the MME sends a message to the SeNB to perform dual-connection processing on the SeNB. In this manner, the X2 interface between the MeNB and the SeNB is not required, so that the X2 interface does not exist between the MeNB and the SeNB. In this case, the dual connection processing to the SeNB can also be implemented, thereby implementing dual connectivity of the base station. The problem that the double connection of the base station cannot be realized when the X2 interface does not exist in the related art is solved, thereby achieving the effect of realizing the double connection of the base station in the absence of the X2 interface.

In an optional embodiment, the foregoing MME receiving the first request message from the primary base station MeNB includes: receiving, by using the first S1 interface with the MeNB, the first request message, where the first request message includes the following a routing information of the MeNB, routing information of the SeNB, and processing information required for performing dual connectivity processing on the SeNB; a base station configuration switching message (eNB CONFIGURATION TRANSFER) encapsulating the processing information; and/or the MME according to the foregoing Sending the second request message to the SeNB by the request message includes: transmitting, by the second S1 interface with the SeNB, a second request message to the SeNB, where the second request message includes one of the following: routing information of the MeNB, and routing of the SeNB Information and the above processing information; a mobility management entity configuration conversion message (MME CONFIGURATION TRANSFER) encapsulating the above processing information. In this embodiment, the first S1 interface and the second S1 interface may be existing interfaces, that is, the transmission of the message may be implemented by means of the original S1 interface.

In an optional embodiment, after processing the SeNB, the MME may also receive a response message from the SeNB, and then feed back a response message to the MeNB. The following is an embodiment of the present invention, after the MME sends the second request message to the SeNB according to the first request message, the method further includes: the MME receiving the first response message from the SeNB by using the second S1 interface, where the The responsive message includes at least one of: routing information of the MeNB, routing information of the SeNB, and processing response information after performing dual connectivity processing on the SeNB; eNB CONFIGURATION TRANSFER encapsulating the processing response information; the MME passes the first response message according to the first response message An S1 interface sends a second response message to the MeNB, where the second response message includes at least one of: routing information of the MeNB, routing information of the SeNB, and processing response information; and an MME CONFIGURATION TRANSFER encapsulating the processing response information.

In the foregoing embodiment, the processing of the SeNB may be triggered by the MeNB, or may be triggered by the SeNB. The scheme triggered by the SeNB is described below. In an optional embodiment, the MME is receiving. Before the first request message from the MeNB, the method further includes: the MME receiving, by using the second S1 interface, a first processing requirement message from the SeNB for indicating that the SeNB needs to be processed, where the first processing requirement message includes the following at least One of: the routing information of the MeNB, the routing information of the SeNB, and the processing requirement information; the eNB CONFIGURATION TRANSFER encapsulating the processing requirement information; the MME sends the second processing requirement message to the MeNB through the first S1 interface according to the first processing requirement message, The second processing requirement message includes at least one of the following: routing information of the MeNB, routing information of the SeNB, and processing requirement information; and an MME CONFIGURATION TRANSFER encapsulating the processing requirement information.

In an optional embodiment, the foregoing MME receiving the first request message from the primary base station (MeNB) includes: receiving, by using a third S1 interface with the MeNB, a first request message, where the first request message includes a MeNB And/or an S1 access point identifier (APID) allocated by the MME for the UE, routing information of the SeNB, and processing information required for performing dual connectivity processing on the SeNB; and/or, the MME sends the SeNB to the SeNB according to the first request message. The second request message includes: sending a second request message to the SeNB by using a fourth S1 interface with the SeNB, where the second request message includes an S1 APID allocated by the MME and/or the SeNB for the UE and the foregoing processing information. In this embodiment, the third S1 interface and the fourth S1 interface may be interfaces in the related art, that is, the transmission of the message may be implemented by means of the original S1 interface.

In an optional embodiment, after the foregoing MME sends the second request message to the SeNB according to the first request message, the method further includes: receiving, by the MME, the third response message returned by the SeNB by using the fourth S1 interface, where the The third response message includes the S1 APID allocated by the SeNB and/or the MME for the UE, the routing information of the MeNB, and the processing response information after performing the dual connectivity processing on the SeNB. The MME sends the information to the MeNB through the third S1 interface according to the third response message. And a fourth response message, where the fourth response message includes an S1 APID allocated by the MME and/or the MeNB for the UE and the foregoing processing response information.

In the foregoing embodiment, the processing of the SeNB may be triggered by the MeNB, or may be triggered by the SeNB. The scheme triggered by the SeNB is described below. In an optional embodiment, the MME is receiving. Before the first request message from the MeNB, the method further includes: The MME receives, by using the foregoing fourth S1 interface, a third processing requirement message from the SeNB for indicating that the SeNB needs to be processed, where the third processing requirement message includes the S1 APID and the route of the MeNB allocated by the SeNB and/or the MME for the UE. Information and processing demand information; the MME sends a fourth processing requirement message to the MeNB through the third S1 interface according to the foregoing third processing requirement message, where the fourth processing requirement message includes an S1 APID allocated by the MME and/or the MeNB for the UE and the foregoing Process demand information.

In an optional embodiment, the foregoing processing information includes reject processing information that refuses to perform dual connectivity processing on the SeNB. In this embodiment, the SeNB may send the processing rejection information when the MeNB determines that the request to reject the SeNB needs to be rejected after the SeNB sends the processing request message to the MeNB by using the MME, or the MeNB may determine that the MeNB needs to reject according to other reasons. When the SeNB is processed, the transmitted processing rejects the information.

FIG. 4 is a flowchart of a method for processing a second type of SeNB according to an embodiment of the present invention. As shown in FIG. 4, the method includes the following steps:

Step S402, the primary base station (MeNB) sends a first request message for requesting dual connectivity processing to the SeNB to the mobility management entity (MME) to request the MME to send a second request message to the SeNB, where the second request message is used. The SeNB is requested to perform dual connectivity processing.

Through the above steps, the MeNB can send a dual-connection processing request to the SeNB through the MeNB. In this manner, the X2 interface between the MeNB and the SeNB is not needed, so that the SeNB can be implemented in the absence of the X2 interface. Processing, thereby implementing dual connectivity of the base station. The problem that the double connection of the base station cannot be realized when the X2 interface does not exist in the related art is solved, thereby achieving the effect of realizing the double connection of the base station in the absence of the X2 interface.

In an optional embodiment, the sending, by the MeNB, the first request message to the MME includes: sending, by the MeNB, a first request message to the MME by using a first S1 interface with the MME, where the first request message includes one of the following: : routing information of the MeNB, routing information of the SeNB, and processing information required for performing dual connectivity processing on the SeNB; base station configuration switching message (eNB CONFIGURATION TRANSFER) encapsulating the processing information; and/or the second request message The MME is sent to the SeNB by using the second S1 interface between the MME and the SeNB, where the second request message includes one of the following: routing information of the MeNB, routing information of the SeNB, and Processing information; a mobility management entity configuration conversion message (MME CONFIGURATION TRANSFER) encapsulating the above processing information. In this embodiment, the first S1 interface and the second S1 interface may be existing interfaces, that is, the transmission of the message may be implemented by means of the original S1 interface.

In an optional embodiment, after the foregoing MeNB sends the first request message to the MME, the method further includes: the MeNB receiving the second response message from the MME by using the first S1 interface, where the second response message is MME Obtaining, according to the received first response message from the SeNB, the first response message includes at least one of: routing information of the MeNB, routing information of the SeNB, and processing response information after performing dual connectivity processing on the SeNB; The eNB CONFIGURATION TRANSFER of the response information includes the following at least one of: routing information of the MeNB, routing information of the SeNB, and the processing response information; and an MME CONFIGURATION TRANSFER encapsulating the processing response information.

In the foregoing embodiment, the processing of the SeNB may be triggered by the MeNB, or may be triggered by the SeNB. The scheme triggered by the SeNB is described below. In an optional embodiment, the foregoing MeNB is in the direction. Before the MME sends the first request message, the method further includes: the MeNB receiving, by using the first S1 interface, a second processing requirement message from the MME, where the second processing requirement message is the first processing demand message from the SeNB according to the received MME. The foregoing first processing requirement message includes at least one of the following: the routing information of the MeNB, the routing information of the SeNB, and the processing requirement information; the eNB CONFIGURATION TRANSFER encapsulating the processing requirement information; the foregoing second processing requirement message includes the following at least A: routing information of the MeNB, routing information of the SeNB, and processing requirement information; an MME CONFIGURATION TRANSFER encapsulating the processing requirement information.

In an optional embodiment, the sending, by the MeNB, the first request message to the MME includes: sending, by the MeNB, a first request message to the MME by using a third S1 interface with the MME, where the first request message includes the MeNB and/or Or the MME allocates the S1 APID of the UE, the routing information of the SeNB, and the processing information required for performing the dual connectivity processing on the SeNB; and/or the second request message is sent by the MME to the fourth S1 interface between the SeNB and the SeNB. The SeNB, where the second request message includes an S1 APID allocated by the MME and/or the SeNB for the UE, and the foregoing processing information. In this embodiment, the third S1 interface and the fourth S1 interface may be interfaces in the related art, that is, the transmission of the message is implemented by using the existing S1 interface.

In an optional embodiment, after the foregoing MeNB sends the first request message to the MME by using the third S1 interface with the MME, the method further includes: receiving, by the MeNB, the fourth response from the MME by using the third S1 interface. a message, wherein the fourth response message is obtained by the MME according to the received third response message from the SeNB, where the third response message includes the S1 APID and the MeNB routing information and the pair allocated by the SeNB and/or the MME for the UE. The SeNB performs processing response information after the dual connectivity process, and the fourth response message includes the S1 APID allocated by the MME and/or the MeNB for the UE and the foregoing processing response information.

In the foregoing embodiment, the processing of the SeNB may be triggered by the MeNB, or may be triggered by the SeNB. The scheme triggered by the SeNB is described below. In an optional embodiment, the MeNB is directed to the MME. Before the first request message is sent, the method further includes: receiving, by the MeNB, a fourth processing requirement message from the MME by using the third S1 interface, where the fourth processing requirement message is used by the MME according to the received information from the SeNB to indicate the need for the SeNB. The third processing requirement message includes the S1 APID allocated by the SeNB and/or the MME for the UE, the routing information of the MeNB, and the processing requirement information, where the fourth processing requirement message includes the MME and/or the MeNB. The S1 APID and processing requirement information allocated by the UE.

In an optional embodiment, the foregoing processing information includes reject processing information that refuses to perform dual connectivity processing on the SeNB. In this embodiment, the SeNB may send the processing rejection information when the MeNB determines that the request to reject the SeNB needs to be rejected after the SeNB sends the processing request message to the MeNB by using the MME, or the MeNB may determine that the MeNB needs to reject according to other reasons. When the SeNB is processed, the transmitted processing rejects the information.

FIG. 5 is a flowchart of a method for processing a third SeNB according to an embodiment of the present invention. As shown in FIG. 5, the method includes the following steps:

Step S502, the SeNB receives a second request message from a mobility management entity (MME), where the second request message is determined by the MME according to the received first request message from the primary base station (MeNB), the first request message. It is used to request dual connectivity processing for the SeNB, and the second request message is used to request the SeNB to perform dual connectivity processing.

Through the above steps, the SeNB can receive the message from the MeNB through the MME. In this way, the X2 interface between the MeNB and the SeNB is not needed, so that the processing of the SeNB can be implemented in the absence of the X2 interface. In turn, dual connectivity of the base station is achieved. Solve When the X2 interface does not exist in the related art, the problem of dual connectivity of the base station cannot be achieved, and the effect of dual connectivity of the base station can be achieved even in the absence of the X2 interface.

In an optional embodiment, the foregoing SeNB receiving the second request message from the MME includes: the SeNB receiving the second request message from the MME by using a second S1 interface with the MME, where the second request message includes the following One of: routing information of the MeNB, routing information of the SeNB, and processing information required for performing dual connectivity processing on the SeNB; a mobility management entity configuration conversion message (MME CONFIGURATION TRANSFER) encapsulating the processing information; and/or, The first request message is sent by the MeNB to the MME by using the first S1 interface between the MeNB and the MME, where the first request message includes one of the following: routing information of the MeNB, routing information of the SeNB, and the foregoing processing information; The base station configuring the information described above configures a handover message (eNB CONFIGURATION TRANSFER). In this embodiment, the first S1 interface and the second S1 interface may be existing interfaces, that is, the transmission of the message may be implemented by means of the original S1 interface.

In an optional embodiment, after the SeNB receives the second request message from the MME, the method further includes: the SeNB sending a first response message to the MME by using the second S1 interface, where the first response message And including at least one of the following: the routing information of the MeNB, the routing information of the SeNB, and the processing response information after performing the dual connectivity processing on the SeNB; and the eNB CONFIGURATION TRANSFER encapsulating the processing response information; the first response message is used to indicate the MME direction The MeNB sends a second response message, where the second response message includes at least one of: routing information of the MeNB, routing information of the SeNB, and the foregoing processing response information; and an MME CONFIGURATION TRANSFER encapsulated with the processing response information.

In the foregoing embodiment, the processing of the SeNB may be triggered by the MeNB, or may be triggered by the SeNB. The scheme triggered by the SeNB is described below. In an optional embodiment, the SeNB is receiving. Before the second request message from the MME, the method further includes: the SeNB sending, by using the second S1 interface, the first processing requirement message to the MME, where the first processing requirement message includes at least one of: routing information of the MeNB, and SeNB The routing information and the processing requirement information; the eNB CONFIGURATION TRANSFER encapsulating the processing request information; the first processing requirement message is used to instruct the MME to send a second processing requirement message to the MeNB, where the second processing requirement message includes at least one of the following: MeNB Routing information, SeNB routing information and processing demand information; MME CONFIGURATION encapsulating the above processing requirements information TRANSFER.

In an optional embodiment, the foregoing SeNB receiving the second request message from the MME includes: the SeNB receiving the second request message from the MME by using a fourth S1 interface with the MME, where the second request message includes the SeNB And/or MME allocates an S1 access point identifier APID for the terminal UE and processing information required for performing dual connectivity processing on the SeNB; and/or, the foregoing first request message is used by the MeNB to pass the third between the MeNB and the MME. The S1 interface is sent to the MME, where the first request message includes the S1 access point identifier APID allocated by the MME and/or the MeNB for the terminal UE, the routing information of the SeNB, and the foregoing processing information. In this embodiment, the third S1 interface and the fourth S1 interface may be interfaces in the related art, that is, the transmission of the message is implemented by using the existing S1 interface.

In an optional embodiment, after the SeNB receives the second request message from the MME, the method further includes: the SeNB sending a third response message to the MME by using the fourth S1 interface, where the third response message is included. The SeNB and/or the MME allocates the S1 APID and the routing information of the MeNB and the processing response information after performing the dual connectivity processing on the SeNB, where the third response message is used to instruct the MME to send the second processing message to the MeNB, where the second processing is performed. The message includes the S1 APID allocated by the MME and/or the MeNB for the UE and the above processing response information.

In the foregoing embodiment, the processing of the SeNB may be triggered by the MeNB, or may be triggered by the SeNB. The scheme triggered by the SeNB is described below. In an optional embodiment, the SeNB is receiving. Before the second request message from the MME, the method further includes: the SeNB sending, by using the fourth S1 interface, a third processing requirement message indicating that the SeNB needs to be processed to the MME, to instruct the MME to send the fourth processing requirement to the MeNB. a message, where the third processing requirement message includes S1 APID allocated by the SeNB and/or the MME for the UE, routing information of the MeNB, and processing requirement information, where the fourth processing requirement message includes an S1 APID and an MME and/or an MeNB allocated for the UE. The above processing requirements information.

In an optional embodiment, the foregoing processing information includes reject processing information that refuses to perform dual connectivity processing on the SeNB. In this embodiment, the SeNB may send the processing rejection information when the MeNB determines that the request to reject the SeNB needs to be rejected after the SeNB sends the processing request message to the MeNB by using the MME, or the MeNB may determine that the MeNB needs to reject according to other reasons. When the SeNB is processed, the transmitted processing rejects the information.

In the foregoing embodiment, the description is made from the MME, the MeNB, and the SeNB, respectively. The overall process including the MME, the MeNB, and the SeNB is described below in conjunction with the embodiments.

Embodiment 1

FIG. 6 is a flowchart of a method for implementing dual connectivity of a base station according to the first embodiment of the present invention. As shown in FIG. 6, the method includes the following steps:

Step S602, the MeNB sends a message encapsulated with an X2 AP (corresponding to the first request message described above) to the MME;

Step S604, the MME sends a message encapsulated with an X2 AP (corresponding to the second request message described above) to the SeNB;

Step S606, the SeNB sends the message encapsulated with the X2 AP (the message may be a processing request message, or a processing response message processed by the SeNB) to the MME;

Step S608, the MME sends a message encapsulated with the X2 AP (the message may be a processing request message or a processing response message processed by the SeNB) to the MeNB.

The S1 interface between the MeNB and the MME is corresponding to the first S1 interface, the SeNB and the MME, and the S1 interface between the MeNB and the MME is configured to send and receive inter-base station messages. The S1 interface between the two corresponds to the second S1 interface described above.

In this embodiment, a new forwarding message may be defined, where the information includes the information of the source base station and the target base station (corresponding to the foregoing routing information), such as the identifier of the source base station and the target base station (ID). And/or the Tracking Area Identifier (TAI) information, and the encapsulated X2 AP message (corresponding to the above-mentioned processing information required for processing the SeNB).

Alternatively, the existing eNB CONFIGURATION TRANSFER (corresponding to the above-mentioned base station configuration conversion message) and the MME CONFIGURATION TRANSFER message (corresponding to the MME configuration conversion message described above) are reused, and the X2 AP message is encapsulated in the above message.

In this embodiment, the S1 interface path switching procedure is retained.

Embodiment 2

FIG. 7 is a flowchart of a method for implementing dual connectivity of a base station according to Embodiment 2 of the present invention. The process flow of adding the SeNB is taken as an example. As shown in FIG. 7, the method includes the following steps:

Step S702: The MeNB sends an add requirement message (corresponding to the first request message described above) to the MME, where the message includes at least S1 APID information allocated by the MeNB and the MME for the UE, and routing information of the target SeNB, such as a SeNB ID and a TAI, and The content included in the SeNB addition request message on other existing X2 AP interfaces (corresponding to the above processing information).

Step S704: The MME sends an add request message (corresponding to the second request message described above) to the target SeNB. The message is sent from the MME to the target SeNB, and includes at least the MME UE S1 APID allocated by the MME for the UE, and part of the content (corresponding to the above-mentioned processing information) included in the SeNB Add Request message on other existing X2 AP interfaces.

Step S706: If the SeNB process is successful, send an add request acknowledgement message (corresponding to the third response message described above) to the MME. Otherwise, go to step S710. The message is sent from the target SeNB to the MME, and includes at least S1 APID information allocated by the SeNB and the MME for the UE, and routing information of the source MeNB, such as the MeNB ID and the TAI, and bearer related information accepted and rejected by the target base station, and other existing information. There is a path switching request message on the S1 AP interface and a part of content (corresponding to the above processing response information) included in the SeNB addition request acknowledgement message on the X2 AP interface.

Step S708: The MME sends an add command message (corresponding to the fourth response message described above) to the source MeNB. The message is sent from the MME to the MeNB, and includes at least the S1 APID information allocated by the MeNB and the MME for the UE, and the path switching request message on the other existing S1 AP interface and the part content included in the SeNB addition request acknowledgement message on the X2 AP interface. In the above processing response information).

Step S710: If the SeNB fails to process, send an add request failure message (corresponding to the third response message described above) to the MME. The message is sent from the target SeNB to the MME, and includes at least S1 APID information allocated by the SeNB and the MME for the UE, and routing information of the source MeNB, such as the MeNB ID and the TAI, and the rejection reason (corresponding to the processing response information described above).

Step S712: The MME forwards the add request failure message (corresponding to the fourth response message described above) to the source MeNB. The message is sent from the MME to the MeNB, and at least the S1 APID information allocated by the MeNB and the MME for the UE, and the reason for rejection (corresponding to the processing response information described above) are included.

Embodiment 3

FIG. 8 is a flowchart of a method for implementing dual connectivity of a base station according to Embodiment 3 of the present invention. This embodiment is described by taking a process flow for modifying a SeNB as an example. As shown in FIG. 8, the method includes the following steps:

Step S802: The MeNB sends a modification request message (corresponding to the first request message described above) to the MME. The message includes at least S1 APID information allocated by the MeNB and the MME for the UE, and routing information of the target SeNB, such as the SeNB ID and the TAI, and part of the content included in the SeNB modification request message on other existing X2 AP interfaces (corresponding to the above) Processing information).

Step S804: The MME sends a modification request message to the SeNB. The message includes at least S1 APID information allocated by the SeNB and the MME for the UE, and part of the content (corresponding to the foregoing processing information) included in the SeNB modification request message on the other existing X2 AP interfaces.

Step S806: If the SeNB process is successful, send a modification request acknowledgement message (corresponding to the foregoing third response message) to the MME. The message includes at least S1 APID information allocated by the SeNB and the MME for the UE, and routing information of the source MeNB, such as the MeNB ID and the TAI, and part of the content included in the SeNB modification request acknowledgement message on other existing X2 AP interfaces (corresponding to The above processing response information). Otherwise, go to step S810.

Step S808: The MME sends a modification request acknowledgement message (corresponding to the fourth response message described above) to the source MeNB. The message includes at least S1 APID information allocated by the MeNB and the MME for the UE, and part of content (corresponding to the processing response information described above) included in the SeNB modification request acknowledgement message on other existing X2 AP interfaces.

Step S810: If the SeNB fails to process, send a modification reject message (corresponding to the third response message described above) to the MME. The message includes at least S1 APID information allocated by the SeNB and the MME for the UE, and routing information of the source MeNB, such as the MeNB ID and the TAI, and the modification rejection reason (corresponding to the processing response information described above).

Step S812: The MME sends a modification reject message (corresponding to the fourth response message described above) to the source MeNB. The message includes at least S1 APID information allocated by the MeNB and the MME for the UE, and a modification rejection reason (corresponding to the processing response information described above).

Embodiment 4

FIG. 9 is a flowchart of a method for implementing dual connectivity of a base station according to Embodiment 4 of the present invention. This embodiment is described by taking a process flow for modifying a SeNB as an example. In this embodiment, the modification procedure of the SeNB is performed by the SeNB. Initiated, as shown in FIG. 9, the method includes the following steps:

Step S902: The SeNB sends a modification request message (corresponding to the third processing requirement message described above) to the MME. The message includes at least S1 APID information allocated by the SeNB and the MME for the UE, and routing information of the source MeNB, such as the MeNB ID and the TAI, and part of the content included in the SeNB modification request message on other existing X2 AP interfaces (corresponding to the above) Processing requirements information).

Step S904: The MME sends a modification request message (corresponding to the fourth processing requirement message described above) to the MeNB. The message includes at least S1 APID information allocated by the MeNB and the MME for the UE, and part of the content (corresponding to the processing requirement information described above) included in the SeNB modification request message on the other existing X2 AP interfaces.

Step S906: If the MeNB agrees to modify, the SeNB modification process initiated by the MeNB is triggered. For details, see Embodiment 3. Otherwise, go to step S908.

Step S908: If the MeNB fails to process, send a modification reject message to the MME. The message includes at least the S1 APID information allocated by the MeNB and the MME for the UE, and the routing information of the target SeNB, such as the SeNB ID and the TAI, and the modification rejection reason. Optionally, the SCG configuration information recommended by the MeNB is included.

Step S910: The MME sends a modification reject message to the target SeNB. The message includes at least S1 APID information allocated by the SeNB and the MME for the UE, and the reason for the rejection is modified. Optionally, the SCG configuration information recommended by the MeNB is included.

Embodiment 5

10 is a flowchart of a method for implementing dual connectivity of a base station according to Embodiment 5 of the present invention. This embodiment is described by taking a process flow for releasing the SeNB as an example. The following describes the embodiment in combination with different scenarios:

Scenario 1: SeNB release procedure initiated by the MeNB;

Step S1002: The MeNB sends an SeNB release request message (corresponding to the first request message described above) to the MME. The message includes S1 APID information allocated by the MeNB and the MME for the UE, and a release reason (corresponding to the processing information described above).

Step S1004: The MME sends an SeNB release request message (corresponding to the second request message described above) to the target SeNB. The message includes S1 APID information allocated by the SeNB and the MME for the UE, and a release reason (corresponding to the above processing information). After the target SeNB receives the message, it releases all information related to the local UE.

Scenario 2: SeNB release procedure initiated by the SeNB;

Step S1006: The SeNB sends an SeNB release indication message (corresponding to the third processing requirement message described above) to the MME. The message includes S1 APID information allocated by the SeNB and the MME for the UE, and a release reason (corresponding to the processing requirement information described above).

Step S1008: The MME sends an SeNB release indication message (corresponding to the fourth processing requirement message described above) to the MeNB. The message includes S1 APID information allocated by the MeNB and the MME for the UE, and a release reason (corresponding to the processing requirement information described above).

Step S1010: After receiving the message, the MeNB sends an SeNB release confirmation message (corresponding to the first request message described above) to the MME if it agrees to release. The message includes S1 APID information allocated by the MeNB and the MME for the UE.

Step S1012: The MME sends an SeNB release confirmation message (corresponding to the second request message described above) to the SeNB. The message includes S1 APID information allocated by the SeNB and the MME for the UE. After the target SeNB receives the message, it releases all information related to the local UE.

Through the description of the above embodiments, those skilled in the art can clearly understand that the method according to the above embodiment can be implemented by means of software plus a necessary general hardware platform, and of course, by hardware, but in many cases, the former is A better implementation. Based on such understanding, the technical solution of the present application, which is essential or contributes to the related art, may be embodied in the form of a software product stored in a storage medium (such as ROM/RAM, disk, CD-ROM). The instructions include a number of instructions for causing a terminal device (which may be a cell phone, a computer, a server, or a network device, etc.) to perform the methods described in various embodiments of the present application.

A processing device of the secondary base station (SeNB) is also provided in this embodiment, and the device is used to implement the foregoing embodiments and optional implementations, and details are not described herein. As used below, the term "module" may implement a combination of software and/or hardware of a predetermined function. Although the apparatus described in the following embodiments is preferably implemented in software, hardware, or a combination of software and hardware Implementation is also possible and conceived.

FIG. 11 is a structural block diagram of a processing apparatus of a first type of SeNB according to an embodiment of the present invention. As shown in FIG. 11, the apparatus may be applied to a mobility management entity (MME), including a first receiving module 112 and a first sending. Module 114, the device will be described below.

The first receiving module 112 is configured to receive a first request message from the primary base station (MeNB), where the first request message is used to request dual connectivity processing for the SeNB; and the first sending module 114 is connected to the first receiving The module 112 is configured to send a second request message to the SeNB according to the foregoing first request message, where the second request message is used to request the SeNB to perform dual connectivity processing.

FIG. 12 is a structural block diagram 1 of a first receiving module 112 and/or a first sending module 114 in a processing apparatus of a first type of SeNB according to an embodiment of the present invention. As shown in FIG. 12, the first receiving module 112 includes a first The receiving unit 122 includes a first sending unit 124, and the first receiving unit 122 and the first sending unit 124 are described below.

The first receiving unit 122 is configured to receive the first request message by using the first S1 interface with the MeNB, where the first request message includes one of the following: routing information of the MeNB, routing information of the SeNB, and Processing information required for performing dual connectivity processing; base station configuration conversion message (eNB CONFIGURATION TRANSFER) encapsulated with the above processing information;

The first sending unit 124 is configured to send a second request message to the SeNB by using a second S1 interface with the SeNB, where the second request message includes one of the following: routing information of the MeNB, routing information of the SeNB, and the foregoing processing. Information; a mobility management entity configuration conversion message (MME CONFIGURATION TRANSFER) encapsulating the above processing information.

FIG. 13 is a block diagram showing an optional structure of a processing apparatus of a first type of SeNB according to an embodiment of the present invention. As shown in FIG. 13, the apparatus includes a second receiving module 132 and all but the modules shown in FIG. The second transmitting module 134 is described below.

The second receiving module 132 is connected to the first sending module 114, and is configured to receive the first request from the SeNB through the second S1 interface after the first sending module 114 sends the second request message to the SeNB according to the first request message. a response message, wherein the first response message includes at least one of: routing information of the MeNB, routing information of the SeNB, and processing response information after performing dual connectivity processing on the SeNB; and eNB CONFIGURATION encapsulating the processing response information. TRANSFER;

The second sending module 134 is connected to the second receiving module 132, and is configured to send a second response message to the MeNB by using the first S1 interface according to the first response message, where the second response message includes at least one of the following: Routing information, routing information of the SeNB, and processing response information; an MME CONFIGURATION TRANSFER encapsulating the processing response information described above.

FIG. 14 is a block diagram showing an optional structure of a processing apparatus of a first type of SeNB according to an embodiment of the present invention. As shown in FIG. 14, the apparatus includes a third receiving module 142 and all but the modules shown in FIG. The third transmitting module 144 will be described below.

The third receiving module 142 is configured to: before the first receiving module 112 receives the first request message from the MeNB, receive, by using the second S1 interface, a first processing demand message from the SeNB for indicating that the SeNB needs to be processed, where The first processing requirement message includes at least one of: routing information of the MeNB, routing information of the SeNB, and processing requirement information; an eNB CONFIGURATION TRANSFER encapsulating the processing requirement information;

The third sending module 144 is connected to the third receiving module 142 and the first receiving module 112, and is configured to send a second processing demand message to the MeNB through the first S1 interface according to the first processing requirement message, where the second processing requirement The message includes at least one of the following: routing information of the MeNB, routing information of the SeNB, and processing requirement information; and an MME CONFIGURATION TRANSFER encapsulating the processing requirement information.

FIG. 15 is a second structural block diagram of a first receiving module 112 and/or a first transmitting module 114 in a processing apparatus of a first type of SeNB according to an embodiment of the present invention. As shown in FIG. 15, the first receiving module 112 includes a second. The receiving unit 152, the first transmitting module 114 includes a second transmitting unit 154, and the second receiving unit 152 and the second transmitting unit 154 are described below.

The second receiving unit 152 is configured to receive a first request message by using a third S1 interface with the MeNB, where the first request message includes an S1 access point identifier (APID) allocated by the MeNB and/or the MME for the UE, Routing information of the SeNB and processing information required for performing dual connectivity processing on the SeNB;

The second sending unit 154 is configured to send a second request message to the SeNB by using a fourth S1 interface with the SeNB, where the second request message includes the MME and/or the SeNB allocates the UE The S1 APID and processing information required for processing the SeNB.

16 is a block diagram 3 of an optional structure of a processing apparatus of a first type of SeNB according to an embodiment of the present invention. As shown in FIG. 16, the apparatus includes a fourth receiving module 162 and all but the modules shown in FIG. The fourth transmitting module 164 will be described below.

The fourth receiving module 162 is connected to the first sending module 114, and is configured to receive the third response message returned by the SeNB through the fourth S1 interface after the first sending module 114 sends the second request message to the SeNB according to the first request message. The third response message includes the S1 APID allocated by the SeNB and/or the MME for the UE, the routing information of the MeNB, and the processing response information after performing dual connectivity processing on the SeNB.

The fourth sending module 164 is connected to the fourth receiving module 162, and is configured to send a fourth response message to the MeNB by using the third S1 interface according to the foregoing third response message, where the fourth response message includes the MME and/or the MeNB. The S1 APID assigned to the UE and the above processing response information.

FIG. 17 is a block diagram showing an optional structure of a processing apparatus of a first type of SeNB according to an embodiment of the present invention. As shown in FIG. 17, the apparatus includes a fifth receiving module 172 in addition to all the modules shown in FIG. The fifth transmitting module 174 will be described below.

The fifth receiving module 172 is configured to receive, by the fourth S1 interface, a third processing requirement message from the SeNB for indicating that the SeNB needs to be processed, before the first receiving module 112 receives the first request message from the MeNB, where The third processing requirement message includes the S1 APID allocated by the SeNB and/or the MME for the UE, the routing information of the MeNB, and the processing requirement information.

The fifth sending module 174 is connected to the fifth receiving module 172 and the first receiving module 112, and is configured to send a fourth processing demand message to the MeNB through the third S1 interface according to the third processing requirement message, where the fourth processing is performed. The demand message includes the S1 APID allocated by the MME and/or the MeNB for the UE and the above processing requirement information.

In an optional embodiment, the foregoing processing information includes reject processing information that refuses to perform dual connectivity processing on the SeNB.

FIG. 18 is a structural block diagram of a processing apparatus of a second SeNB according to an embodiment of the present invention. The apparatus may be applied to a primary base station (MeNB). As shown in FIG. 18, the apparatus includes a sixth sending module 182. The device is described.

The sixth sending module 182 is configured to send, to the mobility management entity (MME), a first request message for requesting dual connectivity processing to the SeNB, to request the MME to send a second request message to the SeNB, where the second request message is used. The SeNB is requested to perform dual connectivity processing.

FIG. 19 is a block diagram showing the structure of a sixth sending module 182 in a processing apparatus of a second type of SeNB according to an embodiment of the present invention. As shown in FIG. 19, the sixth sending module 182 includes a third sending unit 192. The unit is explained.

The third sending unit 192 is configured to send a first request message to the MME by using a first S1 interface with the MME, where the first request message includes one of the following: routing information of the MeNB, routing information of the SeNB, and Processing information required for dual connectivity processing for the SeNB; base station configuration conversion message (eNB CONFIGURATION TRANSFER) encapsulating the processing information.

In an optional embodiment, the foregoing second request message is sent by the MME to the SeNB through the second S1 interface between the MME and the SeNB, where the second request message includes one of the following: routing information of the MeNB, SeNB Routing information and the above processing information; a mobility management entity configuration conversion message (MME CONFIGURATION TRANSFER) encapsulating the above processing information.

FIG. 20 is a block diagram showing an optional structure of a processing apparatus of a second type of SeNB according to an embodiment of the present invention. As shown in FIG. 20, the apparatus includes a sixth receiving module 202, in addition to all the modules shown in FIG. The device will be described below.

The sixth receiving module 202 is connected to the sixth sending module 182, and is configured to receive a second response message from the MME by using the first S1 interface after the sixth sending module 182 sends the first request message to the MME, where the The second response message is obtained by the MME according to the received first response message from the SeNB; the first response message includes at least one of the following: routing information of the MeNB, routing information of the SeNB, and processing response information after performing dual connectivity processing on the SeNB. The eNB CONFIGURATION TRANSFER encapsulated with the processing response information; the second response message includes at least one of: routing information of the MeNB, routing information of the SeNB, and the processing response information; and an MME CONFIGURATION TRANSFER encapsulating the processing response information.

FIG. 21 is a second block diagram of an optional structure of a processing apparatus of a second type of SeNB according to an embodiment of the present invention. As shown in FIG. 21, the apparatus includes a seventh receiving module 212 in addition to all the modules shown in FIG. The device will be described below.

The seventh receiving module 212 is connected to the sixth sending module 182, and is configured to receive, by the first S1 interface, a second processing request message from the MME, before the sixth sending module 182 sends the first request message to the MME, where The second processing requirement message is obtained by the MME according to the received first processing requirement message from the SeNB; the first processing requirement message includes at least one of: routing information of the MeNB, routing information of the SeNB, and processing requirement information; The eNB CONFIGURATION TRANSFER for processing the demand information includes the following at least one of: routing information of the MeNB, routing information of the SeNB, and processing requirement information; and an MME CONFIGURATION TRANSFER encapsulating the processing requirement information.

FIG. 22 is a second structural block diagram of a sixth sending module 182 in a processing apparatus of a second type of SeNB according to an embodiment of the present invention. As shown in FIG. 22, the sixth sending module 182 includes a fourth sending unit 222. The unit is explained.

The fourth sending unit 222 is configured to send a first request message to the MME by using a third S1 interface with the MME, where the first request message includes an S1 access point identifier (APID) allocated by the MeNB and/or the MME for the UE. ), routing information of the SeNB and processing information required for performing dual connectivity processing on the SeNB.

In an optional embodiment, the foregoing second request message is sent by the MME to the SeNB through a fourth S1 interface with the SeNB, where the second request message includes an S1 APID and an MME and/or an SeNB allocated for the UE. The above processing information.

23 is a block diagram 3 of an optional structure of a processing apparatus of a second type of SeNB according to an embodiment of the present invention. As shown in FIG. 23, the apparatus includes an eighth receiving module 232 in addition to all the modules shown in FIG. The device will be described below.

The eighth receiving module 232 is connected to the sixth sending module 182, and is configured to receive, after the sixth sending module 182 sends the first request message to the MME through the third S1 interface between the MME and the MME, a fourth response message of the MME, where the second processing message is obtained by the MME according to the received third response message from the SeNB, where the third response message includes the S1 APID and the MeNB allocated by the SeNB and/or the MME for the UE. The routing information and the processing response information after performing the dual connectivity processing on the SeNB, wherein the fourth response message includes the S1 APID allocated by the MME and/or the MeNB for the UE and the processing response information.

FIG. 24 is a block diagram showing an optional structure of a processing apparatus of a second type of SeNB according to an embodiment of the present invention. 4. As shown in FIG. 24, the apparatus includes a ninth receiving module 242 in addition to all the modules shown in FIG. 18, and the apparatus will be described below.

The ninth receiving module 242 is connected to the sixth sending module 182, and is configured to receive, by the third S1 interface, a fourth processing demand message from the MME, before the sixth sending module 182 sends the first request message to the MME, where The fourth processing requirement message is determined by the MME according to the received third processing requirement message from the SeNB for indicating that the SeNB needs to be processed, where the third processing requirement message includes the S1 APID allocated by the SeNB and/or the MME for the UE, The routing information and processing requirement information of the MeNB, where the fourth processing requirement message includes an S1 APID allocated by the MME and/or the MeNB for the UE, and the foregoing processing requirement information.

In an optional embodiment, the foregoing processing information includes reject processing information that refuses to perform dual connectivity processing on the SeNB.

25 is a structural block diagram of a processing apparatus of a third type of SeNB according to an embodiment of the present invention. The apparatus may be applied to an SeNB. As shown in FIG. 25, the apparatus includes a tenth receiving module 252. .

The tenth receiving module 252 is configured to receive a second request message from a mobility management entity (MME), where the second request message is determined by the MME according to the received first request message from the primary base station (MeNB), where The first request message is used to request dual connectivity processing for the SeNB, and the second request message is used to request the SeNB to perform dual connectivity processing.

FIG. 26 is a block diagram showing the structure of a tenth receiving module 252 in a processing apparatus of a third type of SeNB according to an embodiment of the present invention. As shown in FIG. 26, the tenth receiving module 252 includes a third receiving unit 262. The unit is explained.

The third receiving unit 262 is configured to receive a second request message from the MME by using a second S1 interface with the MME, where the second request message includes one of the following: routing information of the MeNB, routing information of the SeNB, and The processing information required for performing dual connectivity processing on the SeNB; and the mobility management entity configuration conversion message (MME CONFIGURATION TRANSFER) encapsulating the processing information.

In an optional embodiment, the first request message is sent by the MeNB to the MME by using a first S1 interface between the MeNB and the MME, where the first request message includes one of the following: MeNB Routing information, routing information of the SeNB, and the above processing information; a base station configuration switching message (eNB CONFIGURATION TRANSFER) encapsulating the processing information.

FIG. 27 is a block diagram showing an optional structure of a processing apparatus of a third type of SeNB according to an embodiment of the present invention. As shown in FIG. 27, the apparatus includes a seventh sending module 272 in addition to all the modules shown in FIG. The device will be described below.

The seventh sending module 272 is connected to the tenth receiving module 252, and is configured to send a first response message to the MME through the second S1 interface after the tenth receiving module 252 receives the second request message from the MME, where The first response message includes at least one of the following: routing information of the MeNB, routing information of the SeNB, and processing response information after performing dual connectivity processing on the SeNB; eNB CONFIGURATION TRANSFER encapsulating the processing response information; And instructing the MME to send a second response message to the MeNB, where the second response message includes at least one of: routing information of the MeNB, routing information of the SeNB, and the foregoing processing response information; and an MME CONFIGURATION TRANSFER encapsulating the processing response information.

FIG. 28 is a block diagram showing an optional structure of a processing apparatus of a third type of SeNB according to an embodiment of the present invention. As shown in FIG. 28, the apparatus includes an eighth sending module 282 in addition to all the modules shown in FIG. The device will be described below.

The eighth sending module 282 is connected to the tenth receiving module 252, and is configured to send a first processing demand message to the MME through the second S1 interface before the tenth receiving module 252 receives the second request message from the MME, where the The first processing requirement message includes at least one of: routing information of the MeNB, routing information of the SeNB, and processing requirement information; an eNB CONFIGURATION TRANSFER encapsulating the processing requirement information;

The first processing requirement message is used to indicate that the MME sends a second processing requirement message to the MeNB, where the second processing requirement message includes at least one of: routing information of the MeNB, routing information of the SeNB, and processing requirement information; MME CONFIGURATION TRANSFER for demand information.

29 is a block diagram showing the structure of a tenth receiving module 252 in a processing apparatus of a third type of SeNB according to an embodiment of the present invention. As shown in FIG. 29, the tenth receiving module 252 includes a fourth receiving unit 292. The unit is explained.

The fourth receiving unit 262 is configured to receive a second request message from the MME by using a fourth S1 interface with the MME, where the second request message includes an S1 APID allocated by the SeNB and/or the MME for the UE, and is used for The SeNB performs processing information required for dual connectivity processing.

In an optional embodiment, the foregoing first request message is sent by the MeNB to the MME by using a third S1 interface between the MeNB and the MME, where the first request message includes the S1 allocated by the MME and/or the MeNB for the UE. APID, SeNB routing information and the above processing information.

30 is a block diagram 3 of an optional structure of a processing apparatus of a third type of SeNB according to an embodiment of the present invention. As shown in FIG. 30, the apparatus includes a ninth sending module 302, in addition to all the modules shown in FIG. The device will be described below.

The ninth sending module 302 is connected to the tenth receiving module 252, and is configured to send a third response message to the MME by using the fourth S1 interface after the tenth receiving module 252 receives the second request message from the MME, where The third response message includes the S1 APID allocated by the SeNB and/or the MME for the UE, the routing information of the MeNB, and the processing response information after performing the dual connectivity processing on the SeNB, where the third response message is used to instruct the MME to send the fourth response to the MeNB. The message includes the S1 APID allocated by the MME and/or the MeNB for the UE and the foregoing processing response information.

FIG. 31 is a block diagram showing an optional structure of a processing apparatus of a third type of SeNB according to an embodiment of the present invention. As shown in FIG. 31, the apparatus includes a tenth sending module 312, in addition to all the modules shown in FIG. The device will be described below.

The tenth sending module 312 is connected to the tenth receiving module 252, and is configured to send, after the tenth receiving module 252 receives the second request message from the MME, the third S1 interface to the MME to indicate that the SeNB needs to be processed. And a third processing request message, to indicate that the MME sends a fourth processing requirement message to the MeNB, where the third processing requirement message includes S1 APID allocated by the SeNB and/or the MME for the UE, routing information and processing requirement information of the MeNB, The foregoing fourth processing requirement message includes an S1 APID allocated by the MME and/or the MeNB for the UE and the foregoing processing requirement information.

In an optional embodiment, the foregoing processing information includes reject processing information that refuses to perform dual connectivity processing on the SeNB.

It should be noted that the above modules may be implemented by software or hardware. For the latter, the foregoing may be implemented by, but not limited to, the foregoing modules are all located in the same processor; or, the modules are respectively located in multiple processes. In the device.

The embodiment of the invention further provides a computer readable storage medium. Optionally, in the embodiment, the computer readable storage medium may be configured to store program code for performing the following steps:

Step S11: The mobility management entity (MME) receives a first request message from a primary base station (MeNB), where the first request message is used to request dual connectivity processing for the SeNB;

Step S12: The MME sends a second request message to the SeNB according to the first request message, where the second request message is used to request the SeNB to perform dual connectivity processing.

Optionally, the computer readable storage medium is further arranged to store program code for performing the steps of:

Step S21: The MeNB sends a first request message for requesting the SeNB to perform dual connectivity processing to the MME, to request the MME to send a second request message to the SeNB, where the second request message is used to request the SeNB to perform dual connectivity processing.

Optionally, the computer readable storage medium is further arranged to store program code for performing the steps of:

In step S31, the SeNB receives the second request message from the MME, where the second request message is determined by the MME according to the received first request message from the MeNB, where the first request message is used to request dual connectivity processing for the SeNB. The second request message is used to request the SeNB to perform dual connectivity processing.

Optionally, in this embodiment, the computer readable storage medium may include, but is not limited to, a USB flash drive, a Read-Only Memory (ROM), and a Random Access Memory (Random Access Memory). A variety of media that can store program code, such as RAM), removable hard drives, disks, or optical disks.

Optionally, in this embodiment, the processor executes the step flow in each of the foregoing embodiments according to the stored program code in the storage medium.

Optionally, specific examples in this embodiment may refer to the foregoing embodiment and the optional implementation manner. The described examples are not described herein again.

Those skilled in the art will appreciate that the various modules or steps of the present application described above may be implemented by a general-purpose computing device, which may be centralized on a single computing device or distributed over a network of multiple computing devices. Alternatively, they may be implemented by program code executable by a computing device such that they may be stored in a storage device by a computing device and, in some cases, may be executed in a different order than herein. The steps shown or described are either made separately into individual integrated circuit modules, or a plurality of modules or steps are fabricated as a single integrated circuit module. Thus, the application is not limited to any particular combination of hardware and software.

The above description is only an optional embodiment of the present application, and is not intended to limit the present application, and various changes and modifications may be made to the present application. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of this application are intended to be included within the scope of the present application.

Industrial applicability

The embodiment of the present invention provides a method and a device for processing a secondary base station, which solves the problem that the double connection of the base station cannot be implemented when the X2 interface does not exist in the related art, and thus, in the case where the X2 interface does not exist, It is also possible to achieve the effect of dual connectivity of the base station.

Claims (48)

A method for processing a secondary base station SeNB includes: The mobility management entity MME receives the first request message from the primary base station MeNB, where the first request message is used to request dual connectivity processing for the SeNB; And the MME sends a second request message to the SeNB according to the first request message, where the second request message is used to request the SeNB to perform dual connectivity processing. The method of claim 1 wherein Receiving, by the MME, the first request message from the MeNB, the first request message is received by using a first S1 interface with the MeNB, where the first request message includes one of the following: Routing information of the MeNB, routing information of the SeNB, and processing information required for performing dual connectivity processing on the SeNB; a base station configuration conversion message eNB CONFIGURATION TRANSFER encapsulating the processing information; and / or, The sending, by the MME, the second request message to the SeNB according to the first request message includes: sending, by using a second S1 interface with the SeNB, the second request message to the SeNB, where The second request message includes one of the following: Routing information of the MeNB, routing information of the SeNB, and the processing information; The mobility management entity encapsulating the processing information configures a conversion message MME CONFIGURATION TRANSFER. The method according to claim 2, after the MME sends the second request message to the SeNB according to the first request message, the method further includes: The MME receives the first response message from the SeNB by using the second S1 interface, where the first response message includes at least one of the following: routing information of the MeNB, routing information of the SeNB, and a pair Processing response information after the SeNB performs dual connectivity processing; an eNB CONFIGURATION TRANSFER encapsulating the processing response information; The MME sends a second response message to the MeNB by using the first S1 interface according to the first response message, where the second response message includes at least one of: routing information of the MeNB, the Routing information of the SeNB and the processing response information; an MME CONFIGURATION TRANSFER encapsulating the processing response information. The method according to claim 2, before the MME receives the first request message from the MeNB, the method further includes: The MME receives, by using the second S1 interface, a first processing requirement message from the SeNB for indicating that the SeNB needs to be processed, where the first processing requirement message includes at least one of the following: Routing information of the MeNB, routing information of the SeNB, and processing demand information; an eNB CONFIGURATION TRANSFER encapsulating the processing demand information; The MME sends a second processing requirement message to the MeNB by using the first S1 interface according to the first processing requirement message, where the second processing requirement message includes at least one of the following: routing information of the MeNB And routing information and processing requirement information of the SeNB; and an MME CONFIGURATION TRANSFER encapsulating the processing requirement information. The method of claim 1 wherein Receiving, by the MME, the first request message from the MeNB, the first request message is received by using a third S1 interface with the MeNB, where the first request message includes the MeNB and/or the The S1 access point identifier APID allocated by the MME for the terminal UE, the routing information of the SeNB, and processing information required for performing dual connectivity processing on the SeNB; and/or, The sending, by the MME, the second request message to the SeNB according to the first request message includes: sending, by using a fourth S1 interface with the SeNB, the second request message to the SeNB, where the The second request message includes an S1 access point identifier APID allocated by the MME and/or the SeNB for the terminal UE, and the processing information. The method according to claim 5, after the MME sends the second request message to the SeNB according to the first request message, the method further includes: The MME receives, by using the fourth S1 interface, a third response message that is returned by the SeNB, where the third response message includes an S1 APID and a location that the SeNB and/or the MME allocate for the UE. The routing information of the MeNB and the double connection processing to the SeNB Information response The MME sends a fourth response message to the MeNB by using the third S1 interface according to the third response message, where the fourth response message includes the MME and/or the MeNB is the UE. The assigned S1 APID and the processing response information. The method of claim 5, before the MME receives the first request message from the MeNB, the method further includes: The MME receives, by using the fourth S1 interface, a third processing requirement message from the SeNB for indicating that the SeNB needs to be processed, where the third processing requirement message includes the SeNB and/or the Describe an S1 APID allocated by the MME for the UE, routing information of the MeNB, and processing requirement information; The MME sends a fourth processing requirement message to the MeNB by using the third S1 interface according to the third processing requirement message, where the fourth processing requirement message includes the MME and/or the MeNB is The S1 APID allocated by the UE and the processing requirement information. The method according to any one of claims 2 to 7, wherein the processing information includes rejection processing information that denies double connection processing to the SeNB. A method for processing a secondary base station SeNB includes: The primary base station MeNB sends a first request message for requesting dual connectivity processing to the SeNB to the mobility management entity MME to request the MME to send a second request message to the SeNB, where the second request message is used to request the SeNB. Double connection processing. The method of claim 9 wherein The sending, by the MeNB, the first request message to the MME includes: sending, by the MeNB, the first request message to the MME by using a first S1 interface with the MME, where the first request The message includes one of the following: Routing information of the MeNB, routing information of the SeNB, and processing information required for performing dual connectivity processing on the SeNB; a base station configuration conversion message eNB CONFIGURATION TRANSFER encapsulating the processing information; and / or, The second request message is sent by the MME to the SeNB by using a second S1 interface between the MME and the SeNB, where the second request message includes one of the following: Routing information of the MeNB, routing information of the SeNB, and the processing information; The mobility management entity encapsulating the processing information configures a conversion message MME CONFIGURATION TRANSFER. The method according to claim 10, after the MeNB sends the first request message to the MME, the method further includes: The MeNB receives a second response message from the MME by using the first S1 interface, where the second response message is obtained by the MME according to the received first response message from the SeNB; The first response message includes at least one of: routing information of the MeNB, routing information of the SeNB, and processing response information after performing dual connectivity processing on the SeNB; and eNB CONFIGURATION encapsulating the processing response information. TRANSFER; The second response message includes at least one of: routing information of the MeNB, routing information of the SeNB, and the processing response information; and an MME CONFIGURATION TRANSFER encapsulating the processing response information. The method according to claim 10, before the sending, by the MeNB, the first request message to the MME, the method further includes: The MeNB receives a second processing requirement message from the MME by using the first S1 interface, where the second processing requirement message is obtained by the MME according to the received first processing requirement message from the SeNB; The first processing requirement message includes at least one of: routing information of the MeNB, routing information of the SeNB, and processing requirement information; an eNB CONFIGURATION TRANSFER encapsulating the processing requirement information; The second processing requirement message includes at least one of the following: routing information of the MeNB, routing information of the SeNB, and processing requirement information; and an MME CONFIGURATION TRANSFER encapsulating the processing requirement information. The method of claim 9 wherein The sending, by the MeNB, the first request message to the MME includes: sending, by the MeNB, the first request message to the MME by using a third S1 interface with the MME, where the first request The message includes an S1 access point identifier APID allocated by the MeNB and/or the MME for the terminal UE, routing information of the SeNB, and processing information required for performing dual connectivity processing on the SeNB; and/or, The second request message is sent by the MME to the SeNB through a fourth S1 interface with the SeNB, where the second request message includes the MME and/or the SeNB allocates a terminal UE The S1 access point identifies the APID and the processing information. The method according to claim 13, after the MeNB sends the first request message to the MME by using the third S1 interface with the MME, the method further includes: The MeNB receives a fourth response message from the MME by using the third S1 interface, where the fourth response message is obtained by the MME according to the received third response message from the SeNB. The third response message includes the S1 APID allocated by the SeNB and/or the MME for the UE, routing information of the MeNB, and processing response information after performing dual connectivity processing on the SeNB, where the fourth response message includes: The S1 APID and the processing response information allocated by the MME and/or the MeNB to the UE are included in the response message. The method of claim 13, before the sending, by the MeNB, the first request message to the MME, the method further includes: The MeNB receives a fourth processing requirement message from the MME by using the third S1 interface, where the fourth processing requirement message is that the MME receives the indication from the SeNB according to the received And determining, by the SeNB and the third MME, the S1 APID allocated by the SeNB and the MME for the UE, routing information and processing requirement information of the MeNB, where The fourth processing requirement message includes S1 APID and processing requirement information allocated by the MME and/or the MeNB for the UE. The method according to any one of claims 10 to 15, wherein the processing information includes rejection processing information that denies double connection processing to the SeNB. A method for processing a secondary base station SeNB includes: The SeNB receives a second request message from the mobility management entity MME, where the second The request message is determined by the MME according to the received first request message from the primary base station MeNB, where the first request message is used to request dual connectivity processing for the SeNB, and the second request message is used to request the SeNB to perform Double connection processing. The method of claim 17, wherein Receiving, by the SeNB, the second request message from the MME, that the SeNB receives the second request message from the MME by using a second S1 interface with the MME, where the The second request message includes one of the following: Routing information of the MeNB, routing information of the SeNB, and processing information required for performing dual connectivity processing on the SeNB; a mobility management entity that encapsulates the processing information configures a conversion message MME CONFIGURATION TRANSFER; and / or, The first request message is sent by the MeNB to the MME by using a first S1 interface between the MeNB and the MME, where the first request message includes one of the following: Routing information of the MeNB, routing information of the SeNB, and the processing information; The base station encapsulating the processing information configures a handover message eNB CONFIGURATION TRANSFER. The method according to claim 18, after the SeNB receives the second request message from the MME, the method further includes: The SeNB sends a first response message to the MME by using the second S1 interface, where the first response message includes at least one of the following: routing information of the MeNB, routing information of the SeNB, and a pair Processing response information after the SeNB performs dual connectivity processing; an eNB CONFIGURATION TRANSFER encapsulating the processing response information; The first response message is used to indicate that the MME sends a second response message to the MeNB, where the second response message includes at least one of: routing information of the MeNB, routing information of the SeNB, and the Processing response information; MME CONFIGURATION TRANSFER encapsulating the processing response information. The method of claim 18, the SeNB is receiving from the MME Before the second request message, the method further includes: The SeNB sends a first processing requirement message to the MME by using the second S1 interface, where the first processing requirement message includes at least one of: routing information of the MeNB, routing information of the SeNB, and Processing demand information; an eNB CONFIGURATION TRANSFER encapsulating the processing demand information; The first processing requirement message is used to indicate that the MME sends a second processing requirement message to the MeNB, where the second processing requirement message includes at least one of: routing information of the MeNB, and routing information of the SeNB. And processing demand information; an MME CONFIGURATION TRANSFER encapsulating the processing demand information. The method of claim 17, wherein Receiving, by the SeNB, the second request message from the MME, the SeNB receiving the second request message from the MME by using a fourth S1 interface with the MME, where the The second request message includes an S1 access point identifier APID allocated by the SeNB and/or the MME for the terminal UE, and processing information required for performing dual connectivity processing on the SeNB; and/or, The first request message is sent by the MeNB to the MME by using a third S1 interface between the MeNB and the MME, where the first request message includes the MME and/or the MeNB The S1 access point assigned to the terminal UE identifies the APID, the routing information of the SeNB, and the processing information. The method of claim 21, after the SeNB receives the second request message from the MME, the method further includes: The SeNB sends a third response message to the MME by using the fourth S1 interface, where the third response message includes the S1 APID allocated by the SeNB and/or the MME for the UE, The routing information of the MeNB and the processing response information after performing the dual connectivity processing on the SeNB, the third response message is used to instruct the MME to send a fourth response message to the MeNB, where the fourth response message includes The S1 APID and the processing response information allocated by the MME and/or the MeNB for the UE. The method of claim 21, the SeNB is receiving from the MME Before the second request message, the method further includes: And the SeNB sends, by using the fourth S1 interface, the third processing requirement message that is required to be processed to the SeNB, to indicate that the MME sends a fourth processing requirement message to the MeNB, where The third processing requirement message includes an S1 APID allocated by the SeNB and/or the MME for the UE, routing information and processing requirement information of the MeNB, and the fourth processing requirement message includes the MME and/or Or the S1 APID and the processing requirement information allocated by the MeNB to the UE. The method according to any one of claims 18 to 23, wherein the processing information comprises rejection processing information rejecting double connectivity processing for the SeNB. A processing device of the secondary base station SeNB is applied to the mobility management entity MME, and includes: a first receiving module, configured to receive a first request message from the primary base station MeNB, where the first request message is used to request dual connectivity processing for the SeNB; The first sending module is configured to send a second request message to the SeNB according to the first request message, where the second request message is used to request the SeNB to perform dual connectivity processing. The device according to claim 25, wherein The first receiving module includes: a first receiving unit, configured to receive the first request message by using a first S1 interface with the MeNB, where the first request message includes one of the following: Routing information of the MeNB, routing information of the SeNB, and processing information required for performing dual connectivity processing on the SeNB; a base station configuration conversion message eNB CONFIGURATION TRANSFER encapsulating the processing information; and / or, The first sending module includes: a first sending unit, configured to send the second request message to the SeNB by using a second S1 interface with the SeNB, where the second request message includes the following One: Routing information of the MeNB, routing information of the SeNB, and the processing information; The mobility management entity encapsulating the processing information configures a conversion message MME CONFIGURATION TRANSFER. The apparatus of claim 26, the apparatus further comprising: a second receiving module, configured to: after the first sending module sends the second request message to the SeNB according to the first request message, receive a first response from the SeNB by using the second S1 interface a message, where the first response message includes at least one of: routing information of the MeNB, routing information of the SeNB, and processing response information after performing dual connectivity processing on the SeNB; and the processing response is encapsulated Information eNB CONFIGURATION TRANSFER; a second sending module, configured to send a second response message to the MeNB by using the first S1 interface according to the first response message, where the second response message includes at least one of: a route of the MeNB Information, routing information of the SeNB, and the processing response information; an MME CONFIGURATION TRANSFER encapsulating the processing response information. The apparatus of claim 26, the apparatus further comprising: a third receiving module, configured to receive, by the second S1 interface, the SeNB from the SeNB to indicate that the SeNB needs to be performed before the first receiving module receives the first request message from the MeNB Processing the first processing requirement message, where the first processing requirement message includes at least one of: routing information of the MeNB, routing information of the SeNB, and processing requirement information; and an eNB encapsulating the processing requirement information CONFIGURATION TRANSFER; a third sending module, configured to send a second processing requirement message to the MeNB by using the first S1 interface according to the first processing requirement message, where the second processing requirement message includes at least one of the following: Routing information of the MeNB, routing information of the SeNB, and processing requirement information; an MME CONFIGURATION TRANSFER encapsulating the processing requirement information. The device according to claim 25, wherein The first receiving module includes: a second receiving unit, configured to receive the first request message by using a third S1 interface with the MeNB, where the first request message includes the MeNB and/or The S1 access point identifier APID allocated by the MME to the terminal UE, the SeNB Routing information and processing information required for dual connectivity processing of the SeNB; and/or, The first sending module includes: a second sending unit, configured to send the second request message to the SeNB by using a fourth S1 interface with the SeNB, where the second request message includes the The S1 access point identifier APID and the processing information allocated by the MME and/or the SeNB for the terminal UE. The device of claim 29, the device further comprising: a fourth receiving module, configured to: after the first sending module sends the second request message to the SeNB according to the first request message, receive, by using the fourth S1 interface, a third response returned by the SeNB a message, where the third response message includes an S1 APID allocated by the SeNB and/or the MME for the UE, routing information of the MeNB, and processing response information after performing dual connectivity processing on the SeNB. ; a fourth sending module, configured to send a fourth response message to the MeNB by using the third S1 interface according to the third response message, where the fourth response message includes the MME and/or the MeNB The S1 APID assigned to the UE and the processing response information. The device of claim 29, the device further comprising: a fifth receiving module, configured to receive, by the fourth S1 interface, the S1 interface, by using the fourth S1 interface, to indicate that the SeNB needs to be performed, before the first receiving module receives the first request message from the MeNB a third processing request message, where the third processing requirement message includes an S1 APID allocated by the SeNB and/or the MME for the UE, routing information and processing requirement information of the MeNB; a fifth sending module, configured to send, according to the third processing requirement message, a fourth processing requirement message to the MeNB by using the third S1 interface, where the fourth processing requirement message includes the MME and/or the The S1 APID allocated by the MeNB for the UE and the processing requirement information. The apparatus according to any one of claims 26 to 31, wherein the processing information includes reject processing information that denies double connection processing to the SeNB. A processing device of the secondary base station SeNB is applied to the primary base station MeNB, and includes: a sixth sending module, configured to send, to the mobility management entity MME, a first request message for requesting dual connectivity processing to the SeNB, to request the MME to send a second request to the SeNB The message, the second request message is used to request the SeNB to perform dual connectivity processing. The device according to claim 33, wherein The sixth sending module includes: a third sending unit, configured to send the first request message to the MME by using a first S1 interface with the MME, where the first request message includes the following One: Routing information of the MeNB, routing information of the SeNB, and processing information required for performing dual connectivity processing on the SeNB; a base station configuration conversion message eNB CONFIGURATION TRANSFER encapsulating the processing information; and / or, The second request message is sent by the MME to the SeNB by using a second S1 interface between the MME and the SeNB, where the second request message includes one of the following: Routing information of the MeNB, routing information of the SeNB, and the processing information; The mobility management entity encapsulating the processing information configures a conversion message MME CONFIGURATION TRANSFER. The device of claim 34, the device further comprising: a sixth receiving module, configured to receive a second response message from the MME by using the first S1 interface after the sixth sending module sends the first request message to the MME, where the The second response message is obtained by the MME according to the received first response message from the SeNB; The first response message includes at least one of: routing information of the MeNB, routing information of the SeNB, and processing response information after performing dual connectivity processing on the SeNB; and eNB CONFIGURATION encapsulating the processing response information. TRANSFER; The second response message includes at least one of: routing information of the MeNB, routing information of the SeNB, and the processing response information; and an MME CONFIGURATION TRANSFER encapsulating the processing response information. The device of claim 34, the device further comprising: a seventh receiving module, configured to receive, by the first S1 interface, a second processing request message from the MME, before the sixth sending module sends the first request message to the MME, where The second processing requirement message is obtained by the MME according to the received first processing requirement message from the SeNB; The first processing requirement message includes at least one of: routing information of the MeNB, routing information of the SeNB, and processing requirement information; an eNB CONFIGURATION TRANSFER encapsulating the processing requirement information; The second processing requirement message includes at least one of the following: routing information of the MeNB, routing information of the SeNB, and processing requirement information; and an MME CONFIGURATION TRANSFER encapsulating the processing requirement information. The device according to claim 33, wherein The sixth sending module includes: a fourth sending unit, configured to send the first request message to the MME by using a third S1 interface with the MME, where the first request message includes the The M1 and/or the MME allocates an S1 access point identifier APID allocated by the terminal UE, routing information of the SeNB, and processing information required for performing dual connectivity processing on the SeNB; and/or, The second request message is sent by the MME to the SeNB through a fourth S1 interface with the SeNB, where the second request message includes the MME and/or the SeNB allocates a terminal UE The S1 access point identifies the APID and the processing information. The device of claim 37, the device further comprising: An eighth receiving module, configured to receive, after the first sending message is sent by the third sending module to the MME by using the third S1 interface with the MME, receiving, by using the third S1 interface, a fourth response message of the MME, where the fourth response message is obtained by the MME according to the received third response message from the SeNB, where the third response message includes the SeNB and/or Or the S1 APID allocated by the MME to the UE, the routing information of the MeNB, and the processing response information after performing dual connectivity processing on the SeNB, where the fourth response message includes the MME and/or the The S1 APID and the processing response information allocated by the MeNB to the UE. The device of claim 37, the device further comprising: a ninth receiving module, configured to receive, by the third S1 interface, a fourth processing demand message from the MME, before the sixth sending module sends the first request message to the MME, where The fourth processing requirement message is determined by the MME according to the received third processing requirement message from the SeNB for indicating that the SeNB needs to be processed, where the third processing requirement message includes the SeNB and/or The S1 APID allocated by the MME for the UE, the routing information of the MeNB, and processing requirement information, where the fourth processing requirement message includes an S1 APID and processing allocated by the MME and/or the MeNB for the UE demand information. The apparatus according to any one of claims 34 to 39, wherein the processing information includes reject processing information that denies double connection processing to the SeNB. A processing device of the secondary base station SeNB, which is applied to the SeNB, includes: a tenth receiving module, configured to receive a second request message from the mobility management entity MME, where the second request message is determined by the MME according to the received first request message from the primary base station MeNB, A request message is used to request dual connectivity processing for the SeNB, and the second request message is used to request the SeNB to perform dual connectivity processing. The apparatus according to claim 41, wherein The tenth receiving module includes: a third receiving unit, configured to receive the second request message from the MME by using a second S1 interface with the MME, where the second request message includes the following one: Routing information of the MeNB, routing information of the SeNB, and processing information required for performing dual connectivity processing on the SeNB; a mobility management entity that encapsulates the processing information configures a conversion message MME CONFIGURATION TRANSFER; and / or, The first request message is sent by the MeNB to the MME by using a first S1 interface between the MeNB and the MME, where the first request message includes one of the following: Routing information of the MeNB, routing information of the SeNB, and the processing information; Base station configuration conversion message eNB CONFIGURATION encapsulating the processing information TRANSFER. The device of claim 42, the device further comprising: a seventh sending module, configured to send a first response message to the MME by using the second S1 interface, after the tenth receiving module receives the second request message from the MME, where the The response message includes at least one of the following: routing information of the MeNB, routing information of the SeNB, and processing response information after performing dual connectivity processing on the SeNB; and an eNB CONFIGURATION TRANSFER encapsulating the processing response information; The first response message is used to indicate that the MME sends a second response message to the MeNB, where the second response message includes at least one of: routing information of the MeNB, routing information of the SeNB, and the Processing response information; MME CONFIGURATION TRANSFER encapsulating the processing response information. The device of claim 42, the device further comprising: And an eighth sending module, configured to send, by using the second S1 interface, a first processing requirement message to the MME, before the tenth receiving module receives the second request message from the MME, where The first processing requirement message includes at least one of: routing information of the MeNB, routing information of the SeNB, and processing requirement information; an eNB CONFIGURATION TRANSFER encapsulating the processing requirement information; The first processing requirement message is used to indicate that the MME sends a second processing requirement message to the MeNB, where the second processing requirement message includes at least one of: routing information of the MeNB, and routing information of the SeNB. And processing demand information; an MME CONFIGURATION TRANSFER encapsulating the processing demand information. The apparatus according to claim 41, wherein The tenth receiving module includes: a fourth receiving unit, configured to receive the second request message from the MME by using a fourth S1 interface with the MME, where the second request message includes Determining, by the SeNB and/or the MME, an S1 access point identifier APID allocated by the terminal UE and processing information required for performing dual connectivity processing on the SeNB; and/or, The first request message is sent by the MeNB to the MME by using a third S1 interface between the MeNB and the MME, where the first request message includes the MME and/or Or the S1 access point identifier APID allocated by the MeNB for the terminal UE, the routing information of the SeNB, and the processing information. The device of claim 45, the device further comprising: a ninth sending module, configured to send a third response message to the MME by using the fourth S1 interface, after the tenth receiving module receives the second request message from the MME, where the The third response message includes the S1 APID allocated by the SeNB and/or the MME for the UE, routing information of the MeNB, and processing response information after performing dual connectivity processing on the SeNB, where the third response message is included. And the fourth MME sends a fourth response message to the MeNB, where the fourth response message includes an S1 APID and the processing response information that are allocated by the MME and/or the MeNB to the UE. The device of claim 45, the device further comprising: a tenth sending module, configured to send, by using the fourth S1 interface, the MME to indicate that the SeNB needs to be processed before the tenth receiving module receives the second request message from the MME And a third processing request message, to indicate that the MME sends a fourth processing requirement message to the MeNB, where the third processing requirement message includes an S1 APID allocated by the SeNB and/or the MME to the UE The routing information and processing requirement information of the MeNB, where the fourth processing requirement message includes an S1 APID and the processing requirement information allocated by the MME and/or the MeNB for the UE. The apparatus according to any one of claims 42 to 47, wherein the processing information includes reject processing information that denies double connection processing to the SeNB.

Images