CN106817777B

CN106817777B - Method and device for processing secondary base station SeNB

Info

Publication number: CN106817777B
Application number: CN201510870234.6A
Authority: CN
Inventors: 高音
Original assignee: ZTE Corp
Current assignee: ZTE Corp
Priority date: 2015-12-01
Filing date: 2015-12-01
Publication date: 2022-01-28
Anticipated expiration: 2035-12-01
Also published as: WO2016197845A1; CN106817777A

Abstract

The invention provides a method and a device for processing a secondary base station (SeNB), wherein the method comprises the following steps: a mobility management entity MME receives a first request message from a main base station MeNB, wherein the first request message is used for requesting the dual connectivity processing of the SeNB; and the MME sends 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 perform dual connectivity processing on the SeNB. The invention solves the problem that the double connection of the base station can not be realized when the X2 interface does not exist in the related technology, thereby achieving the effect of realizing the double connection of the base station under the condition that the X2 interface does not exist.

Description

Method and device for processing secondary base station SeNB

Technical Field

The invention relates to the field of communication, in particular to a method and a device for processing a secondary base station (SeNB).

Background

Fig. 1 is a schematic diagram of an overall architecture of a Long Term Evolution system in the related art, and as shown in fig. 1, a Long Term Evolution (Long Term Evolution, LTE) architecture includes: a Mobility Management Entity (MME), a Serving Gateway (SGW), a UU interface between a User Equipment (UE) and a base station (eNodeB), an S1-MME (S1 for the Control plane) interface between the eNB and the MME, 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 bottom to top: the L1 Protocol, the L2 Protocol, the Internet Protocol (IP for short), the Stream Control Transmission Protocol (SCTP for short), and the S1 Application Protocol (S1-Application Protocol for short, S1-AP). In LTE, the protocol stack of the S1-U interface is divided into the following protocol layers from bottom to top: l1 Protocol, L2 Protocol, User data Protocol/internet Protocol (UDP/IP), GPRS Tunneling Protocol-User plane (GTP-U for short).

At present, due to the shortage of frequency spectrum resources and the rapid increase of large-flow services of mobile users, in order to increase user throughput and enhance mobile performance, the requirement of hot spot coverage by adopting high frequency points such as 3.5GHz is increasingly obvious, and nodes with low power become a new application scene. However, because the signal attenuation of the high frequency point is comparatively severe, the coverage area of the new cell is comparatively small, and the new cell does not share the same site with the existing cell, so if the user moves between the new cells or between the new cell and the existing cell, frequent switching processes are necessarily caused, so that user information is frequently transmitted between the base stations, thereby causing great signaling impact to the core network, and further inhibiting the introduction of a large number of small cell base stations on the wireless side. Fig. 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 includes: the MME, the SGW, UU interfaces between the UE and the eNB, S1-MME interfaces between the MeNB and the MME, S1-U interfaces between the MeNB, the SeNB and the SGW, and Xn interfaces between the eNB. The user data may be delivered from the core network to the user through the MeNB, or may be delivered 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 connectivity can be realized by adding, modifying and deleting the SeNB through the X2 interface.

Meanwhile, due to network deployment limitations or constraints among different vendors, the X2 interface is not necessarily implemented in actual network operation. However, when the X2 interface does not exist, it is not possible to implement data offloading through the direct interface between the MeNB and the SeNB, and thus the 3C architecture cannot be implemented, thereby resulting in that dual connectivity of the base station cannot be implemented.

For the problem that dual connectivity of a base station cannot be achieved when no X2 interface exists in the related art, no effective solution has been proposed at present.

Disclosure of Invention

The invention provides a method and a device for processing a secondary base station (SeNB), which are used for at least solving the problem that double connection of a base station cannot be realized when an X2 interface does not exist in the related technology.

According to an aspect of the present invention, there is provided a method for processing a secondary base station SeNB, including: a mobility management entity MME receives a first request message from a main base station MeNB, wherein the first request message is used for requesting the dual connectivity processing of the SeNB; and the MME sends 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 perform dual connectivity processing.

Optionally, the receiving, by the MME, the first request message from the master base station MeNB includes: receiving the first request message through a first S1 interface with the MeNB, wherein the first request message comprises one of: routing information of the MeNB, routing information of the SeNB and processing information required for performing dual connectivity processing on the SeNB; the base station CONFIGURATION conversion message eNB CONFIGURATION conversion encapsulated with the processing information; and/or the sending, by the MME, the second request message to the SeNB according to the first request message includes: transmitting the second request message to the SeNB through a second S1 interface with the SeNB, wherein the second request message comprises one of: routing information of the MeNB, routing information of the SeNB, and the processing information; and the mobility management entity encapsulated with the processing information configures a conversion message MME CONFIGURATION TRANSFER.

Optionally, after the MME sends the second request message to the SeNB according to the first request message, the method further includes: the MME receiving, through the second S1 interface, a first response message from the SeNB, 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; the eNB CONFIGURATION TRANSFER encapsulated with the processing response information; the MME sending, to the MeNB through the first S1 interface according to the first response message, a second response message, wherein 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 encapsulating the MME CONFIGURATION TRANSFER with the processing response information.

Optionally, before the MME receives the first request message from the MeNB, the method further includes: the MME receives, through the second S1 interface, a first processing requirement message from the SeNB for indicating that processing of the SeNB is required, 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; encapsulating the eNB CONFIGURATION TRANSFER with the processing requirement information; the MME sends, to the MeNB through the first S1 interface according to the first processing requirement message, 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 encapsulating the MME CONFIGURATION TRANSFER with the processing requirement information.

Optionally, the receiving, by the MME, the first request message from the master base station MeNB includes: receiving the first request message through a third S1 interface with the MeNB, wherein the first request message includes an S1 Access Point Identifier (APID) allocated by the MeNB and/or the MME for a terminal UE, routing information of the SeNB, and processing information required for dual connectivity processing of the SeNB; and/or the sending, by the MME, the second request message to the SeNB according to the first request message includes: and sending the second request message to the SeNB through a fourth S1 interface with the SeNB, wherein the second request message comprises the processing information and an S1 Access Point Identification (APID) allocated by the MME and/or the SeNB for the terminal UE.

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 a third response message returned by the SeNB through the fourth S1 interface, where the third response message includes S1APID allocated by the SeNB and/or the MME to the UE, routing information of the MeNB, and processing response information after performing dual connectivity processing on the SeNB; and the MME sends a fourth response message to the MeNB through the third S1 interface according to the third response message, where the fourth response message includes the S1APID and the processing response information allocated by the MME and/or the MeNB to the UE.

Optionally, before the MME receives the first request message from the MeNB, the method further includes: the MME receiving, by 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 an S1APID allocated by the SeNB and/or the MME to the UE, routing information of the MeNB, and processing requirement information; the MME sends a fourth processing requirement message to the MeNB through the third S1 interface according to the third processing requirement message, where the fourth processing requirement message includes the S1APID and the processing requirement information allocated by the MME and/or the MeNB to the UE.

Optionally, the processing information includes rejection processing information that rejects the dual connectivity processing for the SeNB.

According to another aspect of the present invention, there is provided a method for processing a secondary base station SeNB, including: the method comprises the steps that a main base station (MeNB) sends a first request message for requesting dual connectivity processing of a SeNB to a Mobility Management Entity (MME) so as to request the MME to send a second request message to the SeNB, wherein the second request message is used for requesting the SeNB to perform dual connectivity processing.

Optionally, the sending, by the MeNB, the first request message to the MME includes: the MeNB sends the first request message to the MME through a first S1 interface with the MME, wherein 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; the base station CONFIGURATION conversion message eNB CONFIGURATION conversion encapsulated with the processing information; and/or the second request message is sent by the MME to the SeNB over a second S1 interface between the MME and the SeNB, wherein the second request message includes one of: routing information of the MeNB, routing information of the SeNB, and the processing information; and the mobility management entity encapsulated with the processing information configures a conversion message MME CONFIGURATION TRANSFER.

Optionally, 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 through the first S1 interface, 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, 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 encapsulating the MME CONFIGURATION TRANSFER with the processing response information.

Optionally, before the MeNB sends the first request message to the MME, the method further includes: the MeNB receives a second processing requirement message from the MME through 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 demand message includes at least one of: routing information of the MeNB, routing information of the SeNB, and processing requirement information; encapsulating the eNB CONFIGURATION TRANSFER with the processing requirement information; the second processing demand message includes at least one of: routing information of the MeNB, routing information of the SeNB, and processing requirement information; and encapsulating the MME CONFIGURATION TRANSFER with the processing requirement information.

Optionally, the sending, by the MeNB, the first request message to the MME includes: the MeNB sends the first request message to the MME through a third S1 interface between the MeNB and the MME, wherein the first request message comprises an S1 Access Point Identification (APID) distributed by the MeNB and/or the MME for a terminal UE, routing information of the SeNB and processing information required by dual connectivity processing of the SeNB; and/or the second request message is sent to the SeNB by the MME through a fourth S1 interface with the SeNB, wherein the second request message includes the S1 access point identification APID allocated by the MME and/or the SeNB for the terminal UE and the processing information.

Optionally, after the MeNB sends the first request message to the MME through the third S1 interface with the MME, the method further includes: the MeNB receives a fourth response message from the MME through the fourth S1 interface, where the fourth response message is obtained by the MME according to a received third response message from the SeNB, the third response message includes the S1APID allocated by the SeNB and/or the MME to the UE, the routing information of the MeNB, and processing response information after performing dual connectivity processing on the SeNB, and the fourth response message includes the S1APID allocated by the MME and/or the MeNB to the UE and the processing response information.

Optionally, before the MeNB sends the first request message to the MME, the method further includes: the MeNB receives a fourth processing requirement message from the MME through the third S1 interface, where the fourth processing requirement message is determined by the MME according to a third processing requirement message received from the SeNB and indicating that the SeNB needs to be processed, the third processing requirement message includes S1APID allocated by the SeNB and/or the MME to the UE, routing information of the MeNB, and processing requirement information, and the fourth processing requirement message includes S1APID allocated by the MME and/or the MeNB to the UE and processing requirement information.

According to another aspect of the present invention, there is provided a method for processing a secondary base station SeNB, including: the method includes that a SeNB receives a second request message from a mobility management entity MME, wherein the second request message is determined by the MME according to a received first request message from a main base station MeNB, the first request message is used for requesting the SeNB to perform dual connectivity processing, and the second request message is used for requesting the SeNB to perform dual connectivity processing.

Optionally, the receiving, by the SeNB, the second request message from the MME includes: the SeNB receives the second request message from the MME over a second S1 interface with the MME, wherein the second request message comprises one of: routing information of the MeNB, routing information of the SeNB and processing information required for performing dual connectivity processing on the SeNB; the mobility management entity encapsulated with the processing information configures a conversion 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, wherein the first request message includes one of: routing information of the MeNB, routing information of the SeNB, and the processing information; and the base station CONFIGURATION conversion message eNB CONFIGURATION conversion encapsulated with the processing information.

Optionally, 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 through the second S1 interface, 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 CONFIGURATION TRANSFER encapsulated with the processing response information; the first response message is used for instructing the MME to send a second response message to the MeNB, and the second response message comprises at least one of the following: routing information of the MeNB, routing information of the SeNB, and the processing response information; and encapsulating the MME CONFIGURATION TRANSFER with the processing response information.

Optionally, before the SeNB receives the second request message from the MME, the method further includes: the SeNB sends a first processing requirement message to the MME through 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; encapsulating the eNB CONFIGURATION TRANSFER with the processing requirement information; the first processing requirement message is used for instructing the MME to send 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; and encapsulating the MME CONFIGURATION TRANSFER with the processing requirement 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 through a fourth S1 interface with the MME, wherein the second request message includes an S1 Access Point Identity (APID) allocated by the SeNB and/or the MME for a terminal UE and processing information required for dual connectivity processing for the SeNB; and/or the first request message is sent to the MME by the MeNB through a third S1 interface between the MeNB and the MME, wherein the first request message includes an 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 processing information.

Optionally, 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 through the fourth S1 interface, where the third response message includes S1APID 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, the third response message is used to instruct the MME to send a fourth response message to the MeNB, and the fourth response message includes S1APID 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: the SeNB sends, to the MME through the fourth S1 interface, a third processing requirement message for indicating that the SeNB needs to be processed, so as to indicate that the MME sends a fourth processing requirement message to the MeNB, where the third processing requirement message includes S1APID allocated by the SeNB and/or the MME to the UE, routing information of the MeNB, and processing requirement information, and the fourth processing requirement message includes S1APID allocated by the MME and/or the MeNB to the UE and the processing requirement information.

According to another aspect of the present invention, there is provided a processing apparatus for a secondary base station SeNB, where the apparatus is applied in a mobility management entity MME, and includes: a first receiving module, configured to receive a first request message from a master base station MeNB, where the first request message is used to request a SeNB to perform dual connectivity processing; a first sending module, 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 through a first S1 interface with the MeNB, 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; the base station CONFIGURATION conversion message eNB CONFIGURATION conversion encapsulated with the processing information; and/or, the first sending module comprises: a first sending unit, configured to send the second request message to the SeNB through a second S1 interface with the SeNB, where the second request message includes one of: routing information of the MeNB, routing information of the SeNB, and the processing information; and the mobility management entity encapsulated with the processing information configures a conversion message MME CONFIGURATION TRANSFER.

Optionally, the apparatus further comprises: a second receiving module, configured to receive, through the second S1 interface, a first response message from the SeNB after sending the second request message to the SeNB according to the first request 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 CONFIGURATION TRANSFER encapsulated with the processing response information; a second sending module, configured to send a second response message to the MeNB through 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, routing information of the SeNB, and the processing response information; and encapsulating the MME CONFIGURATION TRANSFER with the processing response information.

Optionally, the apparatus further comprises: a third receiving module, configured to receive, before receiving the first request message from the MeNB, a first processing requirement message from the SeNB through the second S1 interface, where the first processing requirement message is used to indicate that the SeNB needs to be processed, and the first processing requirement message includes at least one of: routing information of the MeNB, routing information of the SeNB, and processing requirement information; encapsulating the eNB CONFIGURATION TRANSFER with the processing requirement information; a third sending module, configured to send, according to the first processing requirement message, a second processing requirement message to the MeNB through the first S1 interface, 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 encapsulating the MME CONFIGURATION TRANSFER with the processing requirement information.

Optionally, the first receiving module includes: a second receiving unit, configured to receive the first request message through 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 a terminal UE, routing information of the SeNB, and processing information required for performing dual connectivity processing on the SeNB; and/or, the first sending module comprises: a second sending unit, configured to send the second request message to the SeNB through a fourth S1 interface with the SeNB, where the second request message includes the S1 access point identity APID and the processing information that are allocated by the MME and/or the SeNB for the terminal UE.

Optionally, the apparatus further comprises: a fourth receiving module, configured to receive, through the fourth S1 interface, a third response message returned by the SeNB after the second request message is sent to the SeNB according to the first request message, where the third response message includes an S1APID allocated by the SeNB and/or the MME to 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 through the third S1 interface according to the third response message, where the fourth response message includes the S1APID and the processing response information that are allocated by the MME and/or the MeNB to the UE.

Optionally, the apparatus further comprises: a fifth receiving module, configured to receive, before receiving the first request message from the MeNB, a third processing requirement message from the SeNB through the fourth S1 interface, where the third processing requirement message includes an S1APID allocated by the SeNB and/or the MME to the UE, routing information of the MeNB, and processing requirement information, and is used for indicating that the SeNB needs to be processed; a fifth sending module, configured to send a fourth processing requirement message to the MeNB through the third S1 interface according to the third processing requirement message, where the fourth processing requirement message includes the S1APID and the processing requirement information that are allocated by the MME and/or the MeNB to the UE.

According to another aspect of the present invention, there is provided a processing apparatus for a secondary base station SeNB, the apparatus being applied in a primary base station MeNB, and including: a sixth sending module, configured to send, to a mobility management entity MME, a first request message for requesting dual connectivity processing for an SeNB, so as 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 through 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; the base station CONFIGURATION conversion message eNB CONFIGURATION conversion encapsulated with the processing information; and/or the second request message is sent by the MME to the SeNB over a second S1 interface between the MME and the SeNB, wherein the second request message includes one of: routing information of the MeNB, routing information of the SeNB, and the processing information; and the mobility management entity encapsulated with the processing information configures a conversion message MME CONFIGURATION TRANSFER.

Optionally, the apparatus further comprises: a sixth receiving module, configured to receive, through the first S1 interface, a second response message from the MME after sending the first request message to the MME, 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; 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 encapsulating the MME CONFIGURATION TRANSFER with the processing response information.

Optionally, the apparatus further comprises: a seventh receiving module, configured to receive, through the first S1 interface, a second processing requirement message from the MME before sending 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 demand message includes at least one of: routing information of the MeNB, routing information of the SeNB, and processing requirement information; encapsulating the eNB CONFIGURATION TRANSFER with the processing requirement information; the second processing demand message includes at least one of: routing information of the MeNB, routing information of the SeNB, and processing requirement information; and encapsulating the MME CONFIGURATION TRANSFER with the processing requirement information.

Optionally, the sixth sending module includes: a fourth sending unit, configured to send the first request message to the MME through 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 a 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 to the SeNB by the MME through a fourth S1 interface with the SeNB, wherein the second request message includes the S1 access point identification APID allocated by the MME and/or the SeNB for the terminal UE and the processing information.

Optionally, the apparatus further comprises: an eighth receiving module, configured to receive, through the fourth S1 interface, a fourth response message from the MME after the first request message is sent to the MME through the third S1 interface between the MME and the MME, 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 S1APID allocated by the SeNB and/or the MME to the UE, the routing information of the MeNB, and processing response information after performing dual connectivity processing on the SeNB, and the fourth response message includes the S1APID allocated by the MME and/or the MeNB to the UE and the processing response information.

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

According to another aspect of the present invention, there is provided a processing apparatus for a secondary base station SeNB, the apparatus being applied in the SeNB, and including: a tenth receiving module, 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 a received first request message from a master base station MeNB, the first request message is used to request a SeNB to perform dual connectivity processing, and 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 through 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; the mobility management entity encapsulated with the processing information configures a conversion 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, wherein the first request message includes one of: routing information of the MeNB, routing information of the SeNB, and the processing information; and the base station CONFIGURATION conversion message eNB CONFIGURATION conversion encapsulated with the processing information.

Optionally, the apparatus further comprises: a seventh sending module, configured to send, after receiving the second request message from the MME, a first response message to the MME through the second S1 interface, 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 CONFIGURATION TRANSFER encapsulated with the processing response information; the first response message is used for instructing the MME to send a second response message to the MeNB, and the second response message comprises at least one of the following: routing information of the MeNB, routing information of the SeNB, and the processing response information; and encapsulating the MME CONFIGURATION TRANSFER with the processing response information.

Optionally, the apparatus further comprises: an eighth sending module, configured to send, to the MME through the second S1 interface, a first processing requirement message before receiving 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; encapsulating the eNB CONFIGURATION TRANSFER with the processing requirement information; the first processing requirement message is used for instructing the MME to send 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; and encapsulating the MME CONFIGURATION TRANSFER with the processing requirement information.

Optionally, the tenth receiving module includes: a fourth receiving unit, configured to receive, through a fourth S1 interface with the MME, the second request message from the MME, where the second request message includes an S1 access point identity APID allocated by the SeNB and/or the MME for a terminal UE and processing information required for dual connectivity processing for the SeNB; and/or the first request message is sent to the MME by the MeNB through a third S1 interface between the MeNB and the MME, wherein the first request message includes an 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 processing information.

Optionally, the apparatus further comprises: a ninth sending module, configured to send, after receiving the second request message from the MME, a third response message to the MME through the fourth S1 interface, where the third response message includes the S1APID allocated by the SeNB and/or the MME for the UE, the routing information of the MeNB, and processing response information after performing 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, and the fourth response message includes the S1APID allocated by the MME and/or the MeNB for the UE and the processing response information.

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

According to the invention, a mobility management entity MME is adopted to receive a first request message from a main base station MeNB, wherein the first request message is used for requesting the dual connectivity processing of the SeNB; and the MME sends 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 perform dual connectivity processing. The problem that double connection of the base station cannot be realized when an X2 interface does not exist in the related technology is solved, and the effect of realizing double connection of the base station under the condition that the X2 interface does not exist is achieved.

Drawings

The accompanying drawings, which are included to provide a further understanding of the invention and are incorporated in and constitute a part of this application, illustrate embodiment(s) of the invention and together with the description serve to explain the invention without limiting the invention. In the drawings:

FIG. 1 is a block diagram illustrating an overall architecture of a long term evolution system in the related art;

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

fig. 3 is a flow chart of a first method of processing an SeNB according to an embodiment of the present invention;

fig. 4 is a flow chart of a second method of SeNB processing according to an embodiment of the present invention;

fig. 5 is a flow chart of a third method of processing an SeNB according to an embodiment of the present invention;

fig. 6 is a flowchart of a method for implementing dual connectivity of base stations according to a first embodiment of the present invention;

fig. 7 is a flowchart of a method for implementing dual connectivity of base stations according to a second embodiment of the present invention;

fig. 8 is a flowchart of a method for implementing dual connectivity of base stations according to a third embodiment of the present invention;

fig. 9 is a flowchart of a method for implementing dual connectivity of base stations according to a fourth embodiment of the present invention;

fig. 10 is a flowchart of a method for implementing dual connectivity of base stations according to a fifth embodiment of the present invention;

fig. 11 is a block diagram of a processing device of a first secondary base station SeNB according to an embodiment of the present invention;

fig. 12 is a first block diagram illustrating a first structure of the first receiving module 112 and/or the first sending module 114 in the processing apparatus of the first secondary base station SeNB according to an embodiment of the present invention;

fig. 13 is a block diagram of a preferred structure of a processing device of a first secondary base station SeNB according to an embodiment of the present invention;

fig. 14 is a block diagram of a preferred structure of a processing device of the first secondary base station SeNB according to an embodiment of the present invention;

fig. 15 is a block diagram of a second structure of the first receiving module 112 and/or the first sending module 114 in the processing apparatus of the first secondary base station SeNB according to the embodiment of the present invention;

fig. 16 is a block diagram of a preferred structure of a processing device of the first secondary base station SeNB according to an embodiment of the present invention;

fig. 17 is a block diagram of a preferred structure of a processing device of the first secondary base station SeNB according to an embodiment of the present invention;

fig. 18 is a block diagram of a processing device of a second secondary base station SeNB according to an embodiment of the present invention;

fig. 19 is a first block diagram illustrating a sixth sending module 182 in a processing apparatus of a secondary base station SeNB according to an embodiment of the present invention;

fig. 20 is a block diagram of a preferred structure of a processing device of a secondary base station SeNB according to an embodiment of the present invention;

fig. 21 is a block diagram of a preferred structure of a processing device of a second secondary base station SeNB according to an embodiment of the present invention;

fig. 22 is a block diagram of a sixth sending module 182 in the processing apparatus of the second secondary base station SeNB according to the embodiment of the present invention;

fig. 23 is a block diagram of a preferred structure of a processing device of a second secondary base station SeNB according to an embodiment of the present invention;

fig. 24 is a block diagram of a preferred structure of a processing device of a second secondary base station SeNB according to an embodiment of the present invention;

fig. 25 is a block diagram of a processing device of a third secondary base station SeNB according to an embodiment of the present invention;

fig. 26 is a first block diagram illustrating a structure of a tenth receiving module 252 in a processing apparatus of a third secondary base station SeNB according to an embodiment of the present invention;

fig. 27 is a block diagram of a preferred structure of a processing device of a third secondary base station SeNB according to an embodiment of the present invention;

fig. 28 is a block diagram of a preferred structure of a processing device of a third secondary base station SeNB according to an embodiment of the present invention;

fig. 29 is a block diagram of a tenth receiving module 252 in the processing apparatus of the third secondary base station SeNB according to the embodiment of the present invention;

fig. 30 is a block diagram of a preferred structure of a processing device of a third secondary base station SeNB according to an embodiment of the present invention;

fig. 31 is a block diagram of a preferred structure of a processing device of a third secondary base station SeNB according to an embodiment of the present invention.

Detailed Description

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

It should be noted that the terms "first," "second," and the like in the description and claims of the present invention and in the drawings described above are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order.

In the present embodiment, a method for processing a secondary base station SeNB is provided, and fig. 3 is a flowchart of a method for processing a SeNB according to a first embodiment of the present invention, and as shown in fig. 3, the flowchart includes the following steps:

step S302, a mobility management entity MME receives a first request message from a main base station MeNB, wherein the first request message is used for requesting dual connectivity processing of an 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 steps, the MME sends the message for performing the dual connectivity processing on the SeNB to the SeNB, and the mode is adopted without passing through an X2 interface between the MeNB and the SeNB, so that the dual connectivity processing on the SeNB can be realized under the condition that the X2 interface does not exist between the MeNB and the SeNB, and the dual connectivity of the base station is further realized. The problem that double connection of the base station cannot be realized when an X2 interface does not exist in the related technology is solved, and the effect of realizing double connection of the base station under the condition that the X2 interface does not exist is achieved.

In an optional embodiment, the receiving, by the MME, the first request message from the master base station MeNB includes: receiving the first request message through a first S1 interface with the MeNB, wherein 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; the base station CONFIGURATION conversion message eNB CONFIGURATION conversion encapsulated with the processing information; and/or the sending, by the MME to the SeNB according to the first request message, the second request message includes: sending a second request message to the SeNB through a second S1 interface with the SeNB, wherein the second request message includes one of: routing information of the MeNB, routing information of the SeNB, and the processing information; the mobility management entity encapsulated with the processing information configures a conversion message MME CONFIGURATION TRANSFER. In this embodiment, the first S1 interface and the second S1 interface may be existing interfaces, i.e., the sending of messages may be implemented by means of the original S1 interface.

In an optional embodiment, after processing the SeNB, the MME may further receive a response message from the SeNB, and further feed back the response message to the MeNB, which is described below: after the MME sends the second request message to the SeNB according to the first request message, the method further includes: the MME receives a first response message from the SeNB through the second S1 interface, 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; encapsulating the eNB CONFIGURATION TRANSFER with the processing response information; the MME sends, according to the first response message, a second response message to the MeNB through the first S1 interface, 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 encapsulating the MME CONFIGURATION TRANSFER 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, and the scheme triggered by the SeNB is described below, in an optional embodiment, before the MME receives the first request message from the MeNB, the method further includes: the MME receives, through the second S1 interface, a first processing requirement message from the SeNB for indicating that processing of the SeNB is required, 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; encapsulating the eNB CONFIGURATION TRANSFER with the processing requirement information; the MME sends, to the MeNB through the first S1 interface according to the first processing requirement message, 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 encapsulating the MME CONFIGURATION TRANSFER with the processing requirement information.

In an optional embodiment, the receiving, by the MME, the first request message from the master base station MeNB includes: receiving a first request message through a third S1 interface with the MeNB, wherein the first request message comprises an S1 access point identification 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 sending, by the MME to the SeNB according to the first request message, the second request message includes: and sending a second request message to the SeNB through a fourth S1 interface with the SeNB, wherein the second request message comprises the S1 access point identification APID allocated by the MME and/or the SeNB for the terminal UE and the processing information. In this embodiment, the third S1 interface and the fourth S1 interface may be interfaces in the prior art, i.e., the sending of messages may be implemented by means of the original S1 interface.

In an optional embodiment, after the MME sends the second request message to the SeNB according to the first request message, the method further includes: the MME receives a third response message returned by the SeNB through a fourth S1 interface, wherein the third response message comprises S1APID 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; and the MME sends a fourth response message to the MeNB through a third S1 interface according to the third response message, wherein the fourth response message comprises the S1APID allocated by the MME and/or the MeNB for the UE and 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, and the scheme triggered by the SeNB is described below, in an optional embodiment, before the MME receives the first request message from the MeNB, the method further includes: the MME receives, through 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 S1APID, MeNB routing information, and processing requirement information allocated by the SeNB and/or the MME to the UE; and the MME sends a fourth processing requirement message to the MeNB through a third S1 interface according to the third processing requirement message, wherein the fourth processing requirement message comprises the S1APID allocated to the UE by the MME and/or the MeNB and the processing requirement information.

In an optional embodiment, the processing information includes rejection processing information for rejecting the dual connectivity processing for the SeNB. In this embodiment, the processing rejection information may be sent by the SeNB when the MeNB determines that the request of the SeNB needs to be rejected after sending the processing requirement message to the MeNB through the MME, or of course, the processing rejection information may be sent by the SeNB when the MeNB determines that the SeNB needs to be rejected for processing the SeNB according to other reasons.

Fig. 4 is a flowchart of a second method for processing an SeNB according to an embodiment of the present invention, where the flowchart includes the following steps, as shown in fig. 4:

step S402, the main base station MeNB sends a first request message for requesting the SeNB to perform dual connectivity processing to the mobility management entity MME, so as 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.

Through the steps, the MeNB can send the dual connectivity processing request to the SeNB through the MeNB, and the adoption of the mode does not need to use an X2 interface between the MeNB and the SeNB, so that the SeNB can be guaranteed to be processed under the condition that no X2 interface exists, and the dual connectivity of the base station is further realized. The problem that double connection of the base station cannot be realized when an X2 interface does not exist in the related technology is solved, and the effect of realizing double connection of the base station under the condition that the X2 interface does not exist is achieved.

In an optional embodiment, the sending, by the MeNB, the first request message to the MME includes: the MeNB sends a first request message to the MME through a first S1 interface with the MME, wherein 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; the base station CONFIGURATION conversion message eNB CONFIGURATION conversion encapsulated with the processing information; and/or the second request message is sent to the SeNB by the MME through a second S1 interface between the MME and the SeNB, wherein the second request message includes one of: routing information of the MeNB, routing information of the SeNB, and the processing information; the mobility management entity encapsulated with the processing information configures a conversion message MME CONFIGURATION TRANSFER. In this embodiment, the first S1 interface and the second S1 interface may be existing interfaces, i.e., the sending of messages may be implemented by means of the original S1 interface.

In an optional embodiment, 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 through 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; 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 encapsulating the MME CONFIGURATION TRANSFER 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, and the scheme triggered by the SeNB is described below, in an optional embodiment, before the MeNB sends the first request message to the MME, the method further includes: the MeNB receives a second processing requirement message from the MME through 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; encapsulating the eNB CONFIGURATION TRANSFER with 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; and encapsulating the MME CONFIGURATION TRANSFER with the processing requirement information.

In an optional embodiment, the sending, by the MeNB, the first request message to the MME includes: the MeNB sends a first request message to the MME through a third S1 interface between the MeNB and the MME, wherein the first request message comprises an S1 access point identification APID which is allocated by the MeNB and/or the MME for the terminal UE, routing information of the SeNB and processing information which is required for carrying out dual connectivity processing on the SeNB; and/or sending a second request message to the SeNB by the MME through a fourth S1 interface between the MME and the SeNB, wherein the second request message comprises the S1 access point identification APID allocated by the MME and/or the SeNB for the terminal UE and the processing information. In this embodiment, the third S1 interface and the fourth S1 interface may be interfaces in the prior art, that is, the existing S1 interface is utilized to realize the transmission of messages.

In an optional embodiment, after the MeNB sends the first request message to the MME through the third S1 interface with the MME, the method further includes: the MeNB receives a fourth response message from the MME through a fourth S1 interface, where the fourth response message is obtained by the MME according to a third response message received from the SeNB, the third response message includes a S1APID 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, and the fourth response message includes a S1APID allocated by the MME and/or the MeNB for the UE and 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, and the scheme triggered by the SeNB is described below, in an optional embodiment, before the MeNB sends the first request message to the MME, the method further includes: the MeNB receives a fourth processing requirement message from the MME through a third S1 interface, where the fourth processing requirement message is determined by the MME according to a third processing requirement message received from the SeNB and indicating that the SeNB needs to be processed, the third processing requirement message includes S1APID allocated by the SeNB and/or the MME for the UE, routing information of the MeNB, and processing requirement information, and the fourth processing requirement message includes S1APID allocated by the MME and/or the MeNB for the UE and processing requirement information.

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

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

Through the steps, the SeNB can receive the message from the MeNB through the MME, and in this way, the X2 interface between the MeNB and the SeNB does not need to be used, so that the SeNB can be guaranteed to be processed under the condition that the X2 interface does not exist, and further dual connectivity of the base station is realized. The problem that double connection of the base station cannot be realized when an X2 interface does not exist in the related technology is solved, and the effect of realizing double connection of the base station under the condition that the X2 interface does not exist is achieved.

In an optional embodiment, the receiving, by the SeNB, the second request message from the MME includes: the SeNB receives a second request message from the MME over a second S1 interface with the MME, wherein the second request message comprises one of: routing information of the MeNB, routing information of the SeNB, and processing information required for performing dual connectivity processing on the SeNB; the mobility management entity encapsulated with the processing information configures a conversion 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, wherein the first request message includes one of: routing information of the MeNB, routing information of the SeNB, and the processing information; and the base station CONFIGURATION conversion message eNB CONFIGURATION conversion encapsulated with the processing information. In this embodiment, the first S1 interface and the second S1 interface may be existing interfaces, i.e., the sending of messages 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 sends a first response message to the MME through the second S1 interface, 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 CONFIGURATION TRANSFER encapsulated with the processing response information; the first response message is used to instruct the MME to send a second response message to the MeNB, where the second response message includes at least one of the following: routing information of the MeNB, routing information of the SeNB, and the processing response information; and encapsulating the MME CONFIGURATION TRANSFER with the processing response information.

In the foregoing embodiment, the SeNB may be triggered by the MeNB or the SeNB, and a scheme triggered by the SeNB is described below, in an optional embodiment, before the SeNB receives the second request message from the MME, the method further includes: the SeNB sends a first processing requirement message to the MME through the second S1 interface, wherein the first processing requirement message includes at least one of: routing information of the MeNB, routing information of the SeNB, and processing requirement information; encapsulating the eNB CONFIGURATION TRANSFER with the processing requirement 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: routing information of the MeNB, routing information of the SeNB, and processing requirement information; and encapsulating the MME CONFIGURATION TRANSFER with the processing requirement information.

In an optional embodiment, the receiving, by the SeNB, the second request message from the MME includes: the SeNB receives a second request message from the MME through a fourth S1 interface between the SeNB and the MME, wherein the second request message comprises an S1 Access Point Identification (APID) distributed by the SeNB and/or the MME for the terminal UE and processing information required by dual connectivity processing of the SeNB; and/or the first request message is sent to the MME by the MeNB through a third S1 interface between the MeNB and the MME, wherein the first request message includes an S1 access point identifier APID allocated by the MME and/or the MeNB for the terminal UE, routing information of the SeNB, and the processing information. In this embodiment, the third S1 interface and the fourth S1 interface may be interfaces in the prior art, that is, the existing S1 interface is utilized to realize the transmission of messages.

In an optional embodiment, 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 through a fourth S1 interface, where the third response message includes S1APID 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, the third response message is used to instruct the MME to send a second processing message to the MeNB, and the second processing message includes S1APID allocated by the MME and/or the MeNB for the UE and the processing response information.

In the foregoing embodiment, the processing of the SeNB may be triggered by the MeNB or the SeNB, and the scheme triggered by the SeNB is described below, in an optional embodiment, before the SeNB receives the second request message from the MME, the method further includes: the SeNB sends a third processing requirement message for indicating that the SeNB needs to be processed to the MME through a fourth S1 interface, so as to indicate the MME to send a fourth processing requirement message to the MeNB, where the third processing requirement message includes the S1APID allocated by the SeNB and/or the MME to the UE, the routing information of the MeNB, and the processing requirement information, and the fourth processing requirement message includes the S1APID allocated by the MME and/or the MeNB to the UE and the processing requirement information.

In the above embodiments, the description is made from the MME, MeNB, and SeNB sides, respectively, and the following describes an overall flow including the MME, MeNB, and SeNB in conjunction with the embodiments.

Example one

Fig. 6 is a flowchart of a method for implementing dual connectivity of base stations according to a first embodiment of the present invention, as shown in fig. 6, the method includes the following steps:

step S602, the MeNB sends a message (corresponding to the first request message) encapsulating the X2 AP to the MME;

step S604, the MME sends a message (corresponding to the second request message) encapsulating the X2 AP to the SeNB;

step S606, the SeNB sends a message (which may be a processing demand message or a processing message after processing the SeNB) encapsulated with X2 AP to the MME;

in step S608, the MME sends a message encapsulating the X2 AP (the message may be a processing requirement message or a processing message after processing the SeNB) to the MeNB.

Wherein, there is no X2 interface between the MeNB and the SeNB, and the inter-base-station message transmission and reception can be performed through an S1 interface between the MeNB and the MME, wherein an S1 interface between the MeNB and the MME corresponds to the first S1 interface, and an S1 interface between the SeNB and the MME corresponds to the second S1 interface.

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

Or reuse the existing eNB CONFIGURATION TRANSFER (corresponding to the MeNB CONFIGURATION TRANSFER message described above) and MME CONFIGURATION TRANSFER message (corresponding to the MME CONFIGURATION TRANSFER message described above) in which the X2 AP message is encapsulated.

In this embodiment, the S1 interface path switching flow remains.

Example two

Fig. 7 is a flowchart of a method for implementing dual connectivity of a base station according to a second embodiment of the present invention, which is described by taking a process flow of adding an SeNB as an example, and as shown in fig. 7, the method includes the following steps:

step S702: the MeNB sends an addition required message (corresponding to the first request message described above) to the MME. At least comprising S1APID information allocated by MeNB and MME for UE, and routing information of target SeNB, such as SeNB ID and TAI. And part of the contents (corresponding to the processing information described above) contained in the SeNB addition request message on the other existing X2 AP interface.

Step S704: the MME sends an add request message (corresponding to the second request message described above) to the target SeNB. This message is sent from the MME to the target SeNB, containing at least the MME UE S1AP ID assigned by the MME to the UE, and part of the content contained in the SeNB addition request message on the other existing X2 AP interface (corresponding to the processing information described above).

Step S706: if the SeNB process is successful, an addition request acknowledgement message (corresponding to the third response message described above) is sent to the MME. Otherwise, go to step S710. The message is sent from the target SeNB to the MME, containing at least S1AP ID information allocated by the SeNB and MME for the UE, and routing information of the source MeNB, such as MeNB ID and TAI. And information about bearers accepted and rejected by the target base station. And part of the contents (corresponding to the above-described process response information) contained in the path switch request message on the other existing S1AP interface and the SeNB addition request confirm message on the X2 AP interface.

Step S708: the MME sends an add command message (corresponding to the second processing message described above) to the source MeNB. The message is sent from the MME to the MeNB, and includes at least S1AP ID information allocated by the MeNB and the MME to the UE, and part of the content (corresponding to the above-mentioned processing response information) included in the path switch request message on the existing S1AP interface and the SeNB addition request acknowledgement message on the X2 AP interface.

Step S710: if the SeNB process fails, an add request failure message (corresponding to the third response message described above) is sent to the MME. This message is sent from the target SeNB to the MME, containing at least the S1AP ID information allocated by the SeNB and MME for the UE, as well as the routing information of the source MeNB, such as MeNB ID and TAI, and the reject cause (corresponding to the above-mentioned process response information).

Step S712: the MME forwards an add request failure message (corresponding to the second handling message described above) to the source MeNB. This message is sent from the MME to the MeNB, and contains at least S1AP ID information allocated by the MeNB and MME to the UE, and a reject cause (corresponding to the processing response information described above).

EXAMPLE III

Fig. 8 is a flowchart of a method for implementing dual connectivity of a base station according to a third embodiment of the present invention, which is described by taking a process flow for modifying an SeNB as an example, and 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. At least comprising S1APID information allocated by MeNB and MME for UE, and routing information of target SeNB, such as SeNB ID and TAI. And part of the contents (corresponding to the processing information described above) contained in the SeNB modification request message on the other existing X2 AP interface.

Step S804: the MME sends a modification request message to the SeNB. The message at least includes S1APID information allocated by the SeNB and MME to the UE, and partial content (corresponding to the processing information) included in the SeNB modification request message on the existing X2 AP interface.

Step S806: if the SeNB process is successful, a modification request acknowledgement message (corresponding to the third response message) is sent to the MME. The message at least contains S1APID information allocated by the SeNB and MME for the UE, and routing information of the source MeNB, such as MeNB ID and TAI, and partial content (corresponding to the above processing response information) contained in the SeNB modification request acknowledgement message on the existing X2 AP interface. Otherwise, go to step S810.

Step S808: the MME sends a modification request confirm message (corresponding to the second handling message described above) to the source MeNB. The message at least includes the S1APID information allocated by the MeNB and MME to the UE, and partial content (corresponding to the processing response information) included in the SeNB modification request acknowledgement message on the other existing X2 AP interface.

Step S810: if the SeNB process fails, a modification rejection message (corresponding to the third response message described above) is sent to the MME. The message at least contains S1APID information allocated by the SeNB and MME for the UE, as well as routing information of the source MeNB, such as MeNB ID and TAI, and a modification rejection reason (corresponding to the above-mentioned processing response information).

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

Example four

Fig. 9 is a flowchart of a method for implementing dual connectivity of a base station according to a fourth embodiment of the present invention, where the embodiment is described by taking a process flow for modifying an SeNB as an example, and in the embodiment, the process flow for modifying the SeNB is initiated by the SeNB, as shown in fig. 9, the method includes the following steps:

step S902: the SeNB sends a modification required message (corresponding to the third processing required message described above) to the MME. At least comprising S1APID information allocated by the SeNB and MME for the UE, and routing information of the source MeNB, such as MeNB ID and TAI. And part of the contents (corresponding to the processing requirement information) contained in the SeNB modification requirement message on the other existing X2 AP interface.

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

Step S906: if the MeNB agrees to modify, the MeNB initiated SeNB modification procedure is triggered, which is specifically seen in embodiment three. Otherwise, go to step S908.

Step S908: and if the MeNB fails to process, sending a modification rejection message to the MME. The message at least contains S1APID information allocated by the MeNB and MME for the UE, and routing information of the target SeNB, such as SeNB ID and TAI. And modifying the reject cause. Optionally containing MeNB proposed SCG configuration information.

Step S910: the MME sends a modification reject message to the target SeNB. The message at least contains S1APID information allocated by the SeNB and the MME to the UE, and a modification rejection reason. Optionally containing MeNB proposed SCG configuration information.

EXAMPLE five

Fig. 10 is a flowchart of a method for implementing dual connectivity of a base station according to a fifth embodiment of the present invention, which is described by taking a process flow for releasing an SeNB as an example, and the following describes this embodiment with reference to different scenarios:

scene 1: a SeNB release procedure initiated by the MeNB;

step S1002: the MeNB sends a SeNB release request message (corresponding to the first request message described above) to the MME. The message includes S1AP ID information allocated by the MeNB and MME to the UE, and a release reason (corresponding to the processing information described above).

Step S1004: the MME sends a SeNB release request message (corresponding to the second request message described above) to the target SeNB. The message includes S1AP ID information allocated by the SeNB and MME to the UE, and a release reason (corresponding to the processing information described above). When the target SeNB receives the message, all information related to the local UE is released.

Scene 2: a SeNB release procedure initiated by the SeNB;

step S1006: the SeNB sends a SeNB release indication message (corresponding to the third processing requirement message described above) to the MME. The message includes S1AP ID information allocated by the SeNB and MME to the UE, and a release reason (corresponding to the processing requirement information described above).

Step S1008: the MME sends a SeNB release indication message (corresponding to the fourth processing requirement message described above) to the MeNB. The message includes S1AP ID information allocated by the MeNB and MME to 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) to the MME if the release is granted. The message includes S1AP ID information allocated by the MeNB and MME to the UE.

Step S1012: the MME sends a SeNB release confirm message (corresponding to the second request message described above) to the SeNB. The message includes S1AP ID information allocated by the SeNB and the MME to the UE. When the target SeNB receives the message, all information related to the local UE is released.

Through the above description of the embodiments, those skilled in the art can clearly understand that the method according to the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but the former is a better implementation mode in many cases. Based on such understanding, the technical solutions of the present invention may be embodied in the form of a software product, which is stored in a storage medium (e.g., ROM/RAM, magnetic disk, optical disk) and includes instructions for enabling a terminal device (e.g., a mobile phone, a computer, a server, or a network device) to execute the method according to the embodiments of the present invention.

In this embodiment, a processing apparatus for a secondary base station SeNB is further provided, and the apparatus is used to implement the foregoing embodiments and preferred embodiments, and the description of which has been already made is omitted. As used below, the term "module" may be a combination of software and/or hardware that implements a predetermined function. Although the means described in the embodiments below are preferably implemented in software, an implementation in hardware, or a combination of software and hardware is also possible and contemplated.

Fig. 11 is a block diagram of a processing apparatus of a first secondary base station SeNB according to an embodiment of the present invention, and as shown in fig. 11, the apparatus may be applied to a mobility management entity MME, and includes a first receiving module 112 and a first transmitting module 114, and the apparatus is described below.

A first receiving module 112, configured to receive a first request message from a master base station MeNB, where the first request message is used to request a dual connectivity process for an SeNB; a first sending module 114, connected to the first receiving module 112, 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 on the SeNB.

Fig. 12 is a first block diagram of a first receiving module 112 and/or a first sending module 114 in a processing apparatus of a first secondary base station SeNB according to an embodiment of the present invention, where, as shown in fig. 12, the first receiving module 112 includes a first receiving unit 122, and the first sending module 114 includes a first sending unit 124, and the first receiving unit 122 and the first sending unit 124 are described below.

A first receiving unit 122, configured to receive a first request message through a first S1 interface with the MeNB, 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; the base station CONFIGURATION conversion message eNB CONFIGURATION conversion encapsulated with the processing information;

a first sending unit 124, configured to send a second request message to the SeNB through a second S1 interface with the SeNB, where the second request message includes one of: routing information of the MeNB, routing information of the SeNB, and the processing information; the mobility management entity encapsulated with the processing information configures a conversion message MME CONFIGURATION TRANSFER.

Fig. 13 is a block diagram of a preferred structure of a first processing apparatus of a secondary base station SeNB according to an embodiment of the present invention, and as shown in fig. 13, the apparatus includes a second receiving module 132 and a second transmitting module 134 in addition to all modules shown in fig. 11, and the apparatus is described below.

A second receiving module 132, connected to the first sending module 114, configured to receive a first response message from the SeNB through the second S1 interface after sending a second request message to the SeNB according to the first request 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 CONFIGURATION TRANSFER encapsulated with the processing response information; a second sending module 134, connected to the second receiving module 132, configured to send a second response message to the MeNB through the first S1 interface according to the first response message, where the second response message includes at least one of the following: routing information of the MeNB, routing information of the SeNB, and processing response information; and encapsulating the MME CONFIGURATION TRANSFER with the processing response information.

Fig. 14 is a block diagram of a preferred structure of a processing apparatus of a first secondary base station SeNB according to an embodiment of the present invention, and as shown in fig. 14, the apparatus includes a third receiving module 142 and a third transmitting module 144 in addition to all modules shown in fig. 11, and the apparatus is described below.

A third receiving module 142, configured to receive, before receiving the first request message from the MeNB, a first processing requirement message from the SeNB through the second S1 interface, where the first processing requirement message is used to indicate that the SeNB needs to be processed, and the first processing requirement message includes at least one of: routing information of the MeNB, routing information of the SeNB, and processing requirement information; encapsulating the eNB CONFIGURATION TRANSFER with the processing requirement information; a third sending module 144, connected to the third receiving module 142 and the first receiving module 112, configured to send a second processing requirement message to the MeNB through 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; and encapsulating the MME CONFIGURATION TRANSFER with the processing requirement information.

Fig. 15 is a block diagram of a structure of the first receiving module 112 and/or the first sending module 114 in the processing apparatus of the first secondary base station SeNB according to the embodiment of the present invention, where as shown in fig. 15, the first receiving module 112 includes a second receiving unit 152, the first sending module 114 includes a second sending unit 154, and the second receiving unit 152 and the second sending unit 154 are described below.

A second receiving unit 152, configured to receive a first request message through 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 terminal UE, routing information of the SeNB, and processing information required for performing dual connectivity processing on the SeNB;

a second sending unit 154, configured to send a second request message to the SeNB through a fourth S1 interface with the SeNB, where the second request message includes an S1 access point identity APID allocated by the MME and/or the SeNB for the terminal UE and processing information required for processing the SeNB.

Fig. 16 is a block diagram of a preferred structure of a processing apparatus of a first secondary base station SeNB according to an embodiment of the present invention, and as shown in fig. 16, the apparatus includes a fourth receiving module 162 and a fourth transmitting module 164 in addition to all modules shown in fig. 11, and the apparatus is described below.

A fourth receiving module 162, connected to the first sending module 114, configured to receive, through a fourth S1 interface, a third response message returned by the SeNB after sending the second request message to the SeNB according to the first request message, where the third response message includes S1APID 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 164, connected to the fourth receiving module 162, configured to send a fourth response message to the MeNB through a third S1 interface according to the third response message, where the fourth response message includes the S1APID allocated by the MME and/or the MeNB for the UE and the processing response information.

Fig. 17 is a block diagram of a preferred structure of a processing apparatus of a first secondary base station SeNB according to an embodiment of the present invention, and as shown in fig. 17, the apparatus includes a fifth receiving module 172 and a fifth transmitting module 174, in addition to all modules shown in fig. 11, and the apparatus is described below.

A fifth receiving module 172, configured to receive, before receiving the first request message from the MeNB, a third processing requirement message from the SeNB through the fourth S1 interface, where the third processing requirement message is used to indicate that the SeNB needs to be processed, and includes S1APID allocated by the SeNB and/or the MME for the UE, routing information of the MeNB, and processing requirement information; a fifth sending module 174, connected to the fifth receiving module 172 and the first receiving module 112, configured to send a fourth processing requirement message to the MeNB through a third S1 interface according to the first processing requirement message, where the fourth processing requirement message includes the S1APID allocated by the MME and/or the MeNB to the UE and the processing requirement information.

In an optional embodiment, the processing information includes rejection processing information for rejecting the dual connectivity processing for the SeNB.

Fig. 18 is a block diagram of a processing apparatus of a second secondary base station SeNB according to an embodiment of the present invention, which may be applied to a primary base station MeNB, and includes a sixth transmitting module 182, as shown in fig. 18, and is described below.

A sixth sending module 182, configured to send, to a mobility management entity MME, a first request message for requesting dual connectivity processing for an SeNB, so as to request the MME to send, to the SeNB, a second request message, where the second request message is used to request the SeNB to perform dual connectivity processing.

Fig. 19 is a first block diagram of a sixth sending module 182 in the processing apparatus of the secondary base station SeNB according to the embodiment of the present invention, and as shown in fig. 19, the sixth sending module 182 includes a third sending unit 192, which is described below.

A third sending unit 192, configured to send, to the MME, a first request message through the 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 the base station CONFIGURATION conversion message eNB CONFIGURATION conversion encapsulated with the processing information.

In an optional embodiment, 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 includes one of: routing information of the MeNB, routing information of the SeNB, and the processing information; the mobility management entity encapsulated with the processing information configures a conversion message MME CONFIGURATION TRANSFER.

Fig. 20 is a block diagram of a preferred structure of a processing apparatus of a second secondary base station SeNB according to an embodiment of the present invention, which includes, as shown in fig. 20, a sixth receiving module 202 in addition to all modules shown in fig. 18, and is described below.

A sixth receiving module 202, connected to the sixth sending module 182, configured to receive, through the first S1 interface, a second response message from the MME after sending the first request message to the MME, 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; 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 encapsulating the MME CONFIGURATION TRANSFER with the processing response information.

Fig. 21 is a block diagram of a preferred structure of a second processing apparatus of a secondary base station SeNB according to an embodiment of the present invention, and as shown in fig. 21, the apparatus includes a seventh receiving module 212 in addition to all modules shown in fig. 18, and the apparatus is described below.

A seventh receiving module 212, connected to the sixth sending module 182, configured to receive, through the first S1 interface, a second processing requirement message from the MME before sending 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 demand message includes at least one of: routing information of the MeNB, routing information of the SeNB, and processing requirement information; encapsulating the eNB CONFIGURATION TRANSFER with 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; and encapsulating the MME CONFIGURATION TRANSFER with the processing requirement information.

Fig. 22 is a block diagram of a sixth sending module 182 in the processing apparatus of the secondary base station SeNB according to the second embodiment of the present invention, where, as shown in fig. 22, the sixth sending module 182 includes a fourth sending unit 222, which is described below.

A fourth sending unit 222, configured to send, to the MME through a third S1 interface with the MME, a first request message, where the first request 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.

In an optional embodiment, 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 S1 access point identifier APID allocated by the MME and/or the SeNB for the terminal UE and the processing information.

Fig. 23 is a block diagram of a preferred structure of a processing apparatus of a second secondary base station SeNB according to an embodiment of the present invention, and as shown in fig. 23, the apparatus includes an eighth receiving module 232 in addition to all modules shown in fig. 18, and the apparatus is described below.

An eighth receiving module 232, connected to the sixth sending module 182, configured to receive, through the fourth S1 interface, a fourth response message from the MME after sending the first request message to the MME through the third S1 interface between the MME and the MME, where the second response message is obtained by the MME according to the third response message received from the SeNB, the third response message includes S1APID 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, and the fourth response message includes S1APID allocated by the MME and/or the MeNB for the UE and the processing response information.

Fig. 24 is a block diagram of a preferred structure of a processing apparatus of a second secondary base station SeNB according to an embodiment of the present invention, and as shown in fig. 24, the apparatus includes a ninth receiving module 242 in addition to all modules shown in fig. 18, and the apparatus is described below.

A ninth receiving module 242, connected to the sixth sending module 182, configured to receive, before sending the first request message to the MME, a fourth processing requirement message from the MME through 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, the third processing requirement message includes S1APID allocated by the SeNB and/or the MME for the UE, routing information of the MeNB, and processing requirement information, and the fourth processing requirement message includes S1APID allocated by the MME and/or the MeNB for the UE, and the processing requirement information.

Fig. 25 is a block diagram of a processing apparatus of a third secondary base station SeNB according to an embodiment of the present invention, which may be applied to the SeNB, and includes a tenth receiving module 252, as shown in fig. 25, and is described below.

A tenth receiving module 252, 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 master base station MeNB, the first request message is used to request to perform dual connectivity processing on the SeNB, and the second request message is used to request the SeNB to perform dual connectivity processing.

Fig. 26 is a first block diagram illustrating a structure of a tenth receiving module 252 in a processing apparatus of a third secondary base station SeNB according to an embodiment of the present invention, and as shown in fig. 26, the tenth receiving module 252 includes a third receiving unit 262, which is described below.

A third receiving unit 262, configured to receive a second request message from the MME through 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; the mobility management entity encapsulated with the processing information configures a conversion message MME CONFIGURATION TRANSFER.

In an optional embodiment, 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: routing information of the MeNB, routing information of the SeNB, and the processing information; and the base station CONFIGURATION conversion message eNB CONFIGURATION conversion encapsulated with the processing information.

Fig. 27 is a block diagram of a first preferred structure of a processing apparatus of a third secondary base station SeNB according to an embodiment of the present invention, and as shown in fig. 27, the apparatus includes a seventh sending module 272 in addition to all modules shown in fig. 25, and the apparatus is described below.

A seventh sending module 272, connected to the tenth receiving module 252, configured to send, after receiving the second request message from the MME, a first response message to the MME through a 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; the eNB CONFIGURATION TRANSFER encapsulated with the processing response information; the first response message is used to instruct the MME to send a second response message to the MeNB, where the second response message includes at least one of the following: routing information of the MeNB, routing information of the SeNB, and the processing response information; and encapsulating the MME CONFIGURATION TRANSFER with the processing response information.

Fig. 28 is a block diagram of a preferred structure of a processing apparatus of a third secondary base station SeNB according to an embodiment of the present invention, and as shown in fig. 28, the apparatus includes an eighth sending module 282 in addition to all modules shown in fig. 25, and the apparatus is described below.

An eighth sending module 282, connected to the tenth receiving module 252, configured to send, to the MME through the second S1 interface, a first processing requirement message before receiving the second request message from the MME, 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 requirement information; encapsulating the eNB CONFIGURATION TRANSFER with the processing requirement 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: routing information of the MeNB, routing information of the SeNB, and processing requirement information; and encapsulating the MME CONFIGURATION TRANSFER with the processing requirement information.

Fig. 29 is a block diagram of a structure of a tenth receiving module 252 in the processing apparatus of the secondary base station SeNB according to the third embodiment of the present invention, and as shown in fig. 29, the tenth receiving module 252 includes a fourth receiving unit 292, which is described below.

A fourth receiving unit 262, configured to receive, through a fourth S1 interface with the MME, a second request message from the MME, where the second request message includes an S1 access point identity 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.

In an optional embodiment, the first request message is sent by the MeNB to the MME through a third S1 interface between the MeNB and the MME, where the first request message includes an S1 access point identifier APID allocated by the MME and/or the MeNB for the terminal UE, routing information of the SeNB, and the processing information.

Fig. 30 is a block diagram of a preferred structure of a third processing apparatus of a secondary base station SeNB according to an embodiment of the present invention, and as shown in fig. 30, the apparatus includes a ninth sending module 302 in addition to all modules shown in fig. 25, and the apparatus is described below.

A ninth sending module 302, connected to the tenth receiving module 252, configured to send, after receiving the second request message from the MME, a third response message to the MME through the fourth S1 interface, where the third response message includes the S1APID 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 third response message is used to instruct the MME to send a fourth response message to the MeNB, and the fourth response message includes the S1APID allocated by the MME and/or the MeNB for the UE and the processing response information.

Fig. 31 is a block diagram of a preferred structure of a processing apparatus of a third secondary base station SeNB according to an embodiment of the present invention, and as shown in fig. 31, the apparatus includes a tenth transmitting module 312 in addition to all modules shown in fig. 25, and the apparatus is explained below.

A tenth sending module 312, connected to the tenth receiving module 252, configured to send, to the MME through the fourth S1 interface, a third processing requirement message for indicating that the SeNB needs to be processed before receiving the second request message from the MME, so as to indicate the MME to send a fourth processing requirement message to the MeNB, where the third processing requirement message includes the S1APID allocated by the SeNB and/or the MME for the UE, the routing information of the MeNB, and the processing requirement information, and the fourth processing requirement message includes the S1APID allocated by the MME and/or the MeNB for the UE and the processing requirement information.

It should be noted that, the above modules may be implemented by software or hardware, and for the latter, the following may be implemented, but not limited to: the modules are all positioned in the same processor; alternatively, the modules are respectively located in a plurality of processors.

The embodiment of the invention also provides a storage medium. Alternatively, in the present embodiment, the storage medium may be configured to store program codes for performing the following steps:

s11, the MME receives a first request message from the master base station MeNB, where the first request message is used to request the SeNB to perform dual connectivity processing;

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 storage medium is further arranged to store program code for performing the steps of:

s21, the main base station MeNB sends, to the mobility management entity MME, a first request message for requesting the SeNB to perform dual connectivity processing, so as to request the MME to send, to the SeNB, a second request message for requesting the SeNB to perform dual connectivity processing.

s31, the SeNB receives a second request message from the mobility management entity MME, where the second request message is determined by the MME according to a received first request message from the master base station MeNB, the first request message is used to request the SeNB to perform dual connectivity processing, and the second request message is used to request the SeNB to perform dual connectivity processing.

Optionally, in this embodiment, the storage medium may include, but is not limited to: various media capable of storing program codes, such as a usb disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a removable hard disk, a magnetic disk, or an optical disk.

Optionally, in this embodiment, the processor executes the flow of steps in the above embodiments according to program codes stored in the storage medium.

Optionally, the specific examples in this embodiment may refer to the examples described in the above embodiments and optional implementation manners, and this embodiment is not described herein again.

It will be apparent to those skilled in the art that the modules or steps of the present invention described above may be implemented by a general purpose computing device, they may be centralized on a single computing device or distributed across a network of multiple computing devices, and alternatively, they may be implemented by program code executable by a computing device, such that they may be stored in a storage device and executed by a computing device, and in some cases, the steps shown or described may be performed in an order different than that described herein, or they may be separately fabricated into individual integrated circuit modules, or multiple ones of them may be fabricated into a single integrated circuit module. Thus, the present invention is not limited to any specific combination of hardware and software.

The above description is only a preferred embodiment of the present invention and is not intended to limit the present invention, and various modifications and changes may be made by those skilled in the art. Any modification, equivalent replacement, or improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.

Claims

1. A method for processing a secondary base station (SeNB) is characterized by comprising the following steps:

a mobility management entity MME receives a first request message from a main base station MeNB over a first S1 interface with the main base station MeNB, wherein the first request message is for requesting dual connectivity handling for an SeNB, and 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; the base station CONFIGURATION conversion message eNB CONFIGURATION conversion encapsulated with the processing information;

and the MME sends 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 perform dual connectivity processing.

2. The method of claim 1,

the sending, by the MME, the second request message to the SeNB according to the first request message includes: transmitting the second request message to the SeNB through a second S1 interface with the SeNB, wherein the second request message comprises one of:

routing information of the MeNB, routing information of the SeNB, and the processing information;

and the mobility management entity encapsulated with the processing information configures a conversion message MME CONFIGURATION TRANSFER.

3. The method of claim 2, wherein the MME, after sending the second request message to the SeNB in accordance with the first request message, further comprises:

the MME receiving, through the second S1 interface, a first response message from the SeNB, 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; the eNB CONFIGURATION TRANSFER encapsulated with the processing response information;

the MME sending, to the MeNB through the first S1 interface according to the first response message, a second response message, wherein 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 encapsulating the MME CONFIGURATION TRANSFER with the processing response information.

4. The method of claim 2, wherein the MME, prior to receiving the first request message from the MeNB, further comprises:

the MME receives, through the second S1 interface, a first processing requirement message from the SeNB for indicating that processing of the SeNB is required, 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; encapsulating the eNB CONFIGURATION TRANSFER with the processing requirement information;

the MME sends, to the MeNB through the first S1 interface according to the first processing requirement message, 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 encapsulating the MME CONFIGURATION TRANSFER with the processing requirement information.

5. The method of claim 1,

the MME receiving a first request message from a main base station (MeNB) comprises the following steps: receiving the first request message through a third S1 interface with the MeNB, wherein the first request message includes an S1 Access Point Identifier (APID) allocated by the MeNB and/or the MME for a terminal UE, routing information of the SeNB, and processing information required for dual connectivity processing of the SeNB; and/or the presence of a gas in the gas,

the sending, by the MME, a second request message to the SeNB according to the first request message includes: and sending the second request message to the SeNB through a fourth S1 interface with the SeNB, wherein the second request message comprises the processing information and an S1 Access Point Identification (APID) allocated by the MME and/or the SeNB for the terminal UE.

6. The method of claim 5, wherein the MME, after sending the second request message to the SeNB in accordance with the first request message, further comprises:

the MME receives a third response message returned by the SeNB through the fourth S1 interface, where the third response message includes S1APID allocated by the SeNB and/or the MME to the UE, routing information of the MeNB, and processing response information after performing dual connectivity processing on the SeNB;

and the MME sends a fourth response message to the MeNB through the third S1 interface according to the third response message, wherein the fourth response message comprises the S1APID and the processing response information, which are allocated to the UE by the MME and/or the MeNB.

7. The method of claim 5, wherein the MME, prior to receiving the first request message from the MeNB, further comprises:

the MME receiving, by 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 an S1APID allocated by the SeNB and/or the MME to the UE, routing information of the MeNB, and processing requirement information;

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

8. The method according to any of claims 2 to 7, wherein the processing information comprises rejection processing information for rejecting a dual connectivity process to the SeNB.

9. A method for processing a secondary base station (SeNB) is characterized by comprising the following steps:

the method comprises the steps that a main base station (MeNB) sends a first request message for requesting dual connectivity processing of a SeNB to a Mobility Management Entity (MME) so as to request the MME to send a second request message to the SeNB, wherein the second request message is used for requesting the SeNB to perform dual connectivity processing.

10. The method of claim 9,

the MeNB sending the first request message to the MME includes: the MeNB sends the first request message to the MME through a first S1 interface with the MME, wherein 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;

the base station CONFIGURATION conversion message eNB CONFIGURATION conversion encapsulated with the processing information;

and/or the presence of a gas in the gas,

the second request message is sent by the MME to the SeNB over a second S1 interface between the MME and the SeNB, wherein the second request message includes one of:

11. The method of claim 10, wherein the MeNB, after sending the first request message to the MME, further comprises:

the MeNB receives a second response message from the MME through the first S1 interface, 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, 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 encapsulating the MME CONFIGURATION TRANSFER with the processing response information.

12. The method of claim 10, wherein the MeNB sends the first request message to the MME, and wherein the method further comprises:

the MeNB receives a second processing requirement message from the MME through 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 demand message includes at least one of: routing information of the MeNB, routing information of the SeNB, and processing requirement information; encapsulating the eNB CONFIGURATION TRANSFER with the processing requirement information;

the second processing demand message includes at least one of: routing information of the MeNB, routing information of the SeNB, and processing requirement information; and encapsulating the MME CONFIGURATION TRANSFER with the processing requirement information.

13. The method of claim 9,

the MeNB sending the first request message to the MME includes: the MeNB sends the first request message to the MME through a third S1 interface between the MeNB and the MME, wherein the first request message comprises an S1 Access Point Identification (APID) distributed by the MeNB and/or the MME for a terminal UE, routing information of the SeNB and processing information required by dual connectivity processing of the SeNB; and/or the presence of a gas in the gas,

the second request message is sent to the SeNB by the MME through a fourth S1 interface with the SeNB, where the second request message includes an S1 access point identity APID and the processing information allocated by the MME and/or the SeNB for a terminal UE.

14. The method of claim 13, wherein after the MeNB sends the first request message to the MME over the third S1 interface with the MME, the method further comprises:

the MeNB receives a fourth response message from the MME through the fourth S1 interface, where the fourth response message is obtained by the MME according to a received third response message from the SeNB, the third response message includes the S1APID allocated by the SeNB and/or the MME to the UE, the routing information of the MeNB, and processing response information after performing dual connectivity processing on the SeNB, and the fourth response message includes the S1APID allocated by the MME and/or the MeNB to the UE and the processing response information.

15. The method of claim 13, wherein before the MeNB sends the first request message to the MME, the method further comprises:

the MeNB receives a fourth processing requirement message from the MME through the third S1 interface, where the fourth processing requirement message is determined by the MME according to a third processing requirement message received from the SeNB and indicating that the SeNB needs to be processed, the third processing requirement message includes S1APID allocated by the SeNB and/or the MME to the UE, routing information of the MeNB, and processing requirement information, and the fourth processing requirement message includes S1APID allocated by the MME and/or the MeNB to the UE and processing requirement information.

16. The method according to any of claims 10 to 15, wherein the processing information comprises rejection processing information rejecting a dual connectivity processing for the SeNB.

17. A method for processing a secondary base station (SeNB) is characterized by comprising the following steps:

the method includes that a SeNB receives a second request message from a mobility management entity MME, wherein the second request message is determined by the MME according to a received first request message from a main base station MeNB, the first request message is used for requesting the SeNB to perform dual connectivity processing, and the second request message is used for requesting the SeNB to perform dual connectivity processing, wherein the first request message comprises 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 the base station CONFIGURATION conversion message eNB CONFIGURATION conversion encapsulated with the processing information.

18. The method of claim 17,

the SeNB receiving the second request message from the MME includes: the SeNB receives the second request message from the MME over a second S1 interface with the MME, wherein the second request message comprises one of:

19. The method of claim 18, wherein the SeNB, after receiving the second request message from the MME, further comprises:

the SeNB sends a first response message to the MME through the second S1 interface, 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 CONFIGURATION TRANSFER encapsulated with the processing response information;

the first response message is used for instructing the MME to send a second response message to the MeNB, and the second response message comprises at least one of the following: routing information of the MeNB, routing information of the SeNB, and the processing response information; and encapsulating the MME CONFIGURATION TRANSFER with the processing response information.

20. The method of claim 18, wherein the SeNB, prior to receiving the second request message from the MME, further comprises:

the SeNB sends a first processing requirement message to the MME through 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; encapsulating the eNB CONFIGURATION TRANSFER with the processing requirement information;

the first processing requirement message is used for instructing the MME to send 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; and encapsulating the MME CONFIGURATION TRANSFER with the processing requirement information.

21. The method of claim 17,

the SeNB receiving the second request message from the MME includes: the SeNB receives the second request message from the MME through a fourth S1 interface with the MME, wherein the second request message includes an S1 Access Point Identity (APID) allocated by the SeNB and/or the MME for a terminal UE and processing information required for dual connectivity processing for the SeNB; and/or the presence of a gas in the gas,

the first request message is sent to the MME by the MeNB through a third S1 interface between the MeNB and the MME, where the first request message includes an S1 access point identifier APID allocated by the MME and/or the MeNB for a terminal UE, routing information of the SeNB, and the processing information.

22. The method of claim 21, wherein the SeNB, after receiving the second request message from the MME, further comprises:

the SeNB sends a third response message to the MME through the fourth S1 interface, where the third response message includes S1APID 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, the third response message is used to instruct the MME to send a fourth response message to the MeNB, and the fourth response message includes S1APID allocated by the MME and/or the MeNB for the UE and the processing response information.

23. The method of claim 21, wherein the SeNB, prior to receiving the second request message from the MME, further comprises:

the SeNB sends, to the MME through the fourth S1 interface, a third processing requirement message for indicating that the SeNB needs to be processed, so as to indicate that the MME sends a fourth processing requirement message to the MeNB, where the third processing requirement message includes S1APID allocated by the SeNB and/or the MME to the UE, routing information of the MeNB, and processing requirement information, and the fourth processing requirement message includes S1APID allocated by the MME and/or the MeNB to the UE and the processing requirement information.

24. The method according to any of claims 18 to 23, wherein the processing information comprises rejection processing information rejecting dual connectivity processing for the SeNB.

25. A processing device of a secondary base station (SeNB) is applied to a Mobility Management Entity (MME), and comprises:

a first receiving module, configured to receive a first request message from a master base station MeNB through a first S1 interface with the master base station MeNB, where the first request message is used to request a dual connectivity process for an SeNB, and 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; the base station CONFIGURATION conversion message eNB CONFIGURATION conversion encapsulated with the processing information;

a first sending module, 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.

26. The apparatus of claim 25,

the first transmitting module includes: a first sending unit, configured to send the second request message to the SeNB through a second S1 interface with the SeNB, where the second request message includes one of:

27. The apparatus of claim 26, further comprising:

a second receiving module, configured to receive, through the second S1 interface, a first response message from the SeNB after sending the second request message to the SeNB according to the first request 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 CONFIGURATION TRANSFER encapsulated with the processing response information;

a second sending module, configured to send a second response message to the MeNB through 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, routing information of the SeNB, and the processing response information; and encapsulating the MME CONFIGURATION TRANSFER with the processing response information.

28. The apparatus of claim 26, further comprising:

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

a third sending module, configured to send, according to the first processing requirement message, a second processing requirement message to the MeNB through the first S1 interface, 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 encapsulating the MME CONFIGURATION TRANSFER with the processing requirement information.

29. The apparatus of claim 25,

the first receiving module includes: a second receiving unit, configured to receive the first request message through 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 a terminal UE, routing information of the SeNB, and processing information required for performing dual connectivity processing on the SeNB; and/or the presence of a gas in the gas,

the first transmitting module includes: a second sending unit, configured to send the second request message to the SeNB through a fourth S1 interface with the SeNB, where the second request message includes the S1 access point identity APID and the processing information that are allocated by the MME and/or the SeNB for the terminal UE.

30. The apparatus of claim 29, further comprising:

a fourth receiving module, configured to receive, through the fourth S1 interface, a third response message returned by the SeNB after the second request message is sent to the SeNB according to the first request message, where the third response message includes an S1APID allocated by the SeNB and/or the MME to 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 through the third S1 interface according to the third response message, where the fourth response message includes the S1APID and the processing response information that are allocated by the MME and/or the MeNB to the UE.

31. The apparatus of claim 29, further comprising:

a fifth receiving module, configured to receive, before receiving the first request message from the MeNB, a third processing requirement message from the SeNB through the fourth S1 interface, where the third processing requirement message includes an S1APID allocated by the SeNB and/or the MME to the UE, routing information of the MeNB, and processing requirement information, and is used for indicating that the SeNB needs to be processed;

a fifth sending module, configured to send a fourth processing requirement message to the MeNB through the third S1 interface according to the third processing requirement message, where the fourth processing requirement message includes the S1APID and the processing requirement information that are allocated by the MME and/or the MeNB to the UE.

32. The apparatus according to any of claims 26 to 31, wherein the processing information comprises rejection processing information rejecting dual connectivity processing for the SeNB.

33. A processing device of a secondary base station (SeNB), applied in a main base station (MeNB), comprises:

a sixth sending module, configured to send, to a mobility management entity MME, a first request message for requesting dual connectivity processing for an SeNB, so as 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, and 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 the base station CONFIGURATION conversion message eNB CONFIGURATION conversion encapsulated with the processing information.

34. The apparatus of claim 33,

the sixth sending module includes: a third sending unit, configured to send the first request message to the MME through a first S1 interface with the MME, where the first request message includes one of:

and the base station CONFIGURATION conversion message eNB CONFIGURATION conversion encapsulated with the processing information.

35. The apparatus of claim 34, further comprising:

a sixth receiving module, configured to receive, through the first S1 interface, a second response message from the MME after sending the first request message to the MME, where the second response message is obtained by the MME according to the received first response message from the SeNB;

36. The apparatus of claim 34, further comprising:

a seventh receiving module, configured to receive, through the first S1 interface, a second processing requirement message from the MME before sending 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;

37. The apparatus of claim 33,

the sixth sending module includes: a fourth sending unit, configured to send the first request message to the MME through 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 a terminal UE, routing information of the SeNB, and processing information required for performing dual connectivity processing on the SeNB; and/or the presence of a gas in the gas,

38. The apparatus of claim 37, further comprising:

an eighth receiving module, configured to receive, through the fourth S1 interface, a fourth response message from the MME after the first request message is sent to the MME through the third S1 interface between the MME and the MME, 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 S1APID allocated by the SeNB and/or the MME to the UE, the routing information of the MeNB, and processing response information after performing dual connectivity processing on the SeNB, and the fourth response message includes the S1APID allocated by the MME and/or the MeNB to the UE and the processing response information.

39. The apparatus of claim 37, further comprising:

a ninth receiving module, configured to receive, before sending the first request message to the MME, a fourth processing requirement message from the MME through the third S1 interface, where the fourth processing requirement message is determined by the MME according to a third processing requirement message received from the SeNB and used for indicating that the SeNB needs to be processed, the third processing requirement message includes the S1APID allocated by the SeNB and/or the MME to the UE, the routing information of the MeNB, and the processing requirement information, and the fourth processing requirement message includes the S1APID allocated by the MME and/or the MeNB to the UE and the processing requirement information.

40. The apparatus according to any of claims 34 to 39, wherein the processing information comprises rejection processing information rejecting dual connectivity processing for the SeNB.

41. A processing device of a secondary base station (SeNB) is applied to the SeNB and comprises the following steps:

a tenth receiving module, 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 a received first request message from a master base station MeNB, the first request message is used to request a SeNB to perform dual connectivity processing, and the second request message is used to request the SeNB to perform dual connectivity processing, 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 the base station CONFIGURATION conversion message eNB CONFIGURATION conversion encapsulated with the processing information.

42. The apparatus of claim 41,

the tenth receiving module includes: a third receiving unit, configured to receive the second request message from the MME through a second S1 interface with the MME, where the second request message includes one of:

43. The apparatus of claim 42, further comprising:

a seventh sending module, configured to send, after receiving the second request message from the MME, a first response message to the MME through the second S1 interface, 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 CONFIGURATION TRANSFER encapsulated with the processing response information;

44. The apparatus of claim 42, further comprising:

an eighth sending module, configured to send, to the MME through the second S1 interface, a first processing requirement message before receiving 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; encapsulating the eNB CONFIGURATION TRANSFER with the processing requirement information;

45. The apparatus of claim 41,

the tenth receiving module includes: a fourth receiving unit, configured to receive, through a fourth S1 interface with the MME, the second request message from the MME, where the second request message includes an S1 access point identity APID allocated by the SeNB and/or the MME for a terminal UE and processing information required for dual connectivity processing for the SeNB; and/or the presence of a gas in the gas,

46. The apparatus of claim 45, further comprising:

a ninth sending module, configured to send, after receiving the second request message from the MME, a third response message to the MME through the fourth S1 interface, where the third response message includes the S1APID allocated by the SeNB and/or the MME for the UE, the routing information of the MeNB, and processing response information after performing 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, and the fourth response message includes the S1APID allocated by the MME and/or the MeNB for the UE and the processing response information.

47. The apparatus of claim 45, further comprising:

a tenth sending module, configured to send, to the MME through the fourth S1 interface, a third processing requirement message for indicating that the SeNB needs to be processed before receiving the second request message from the MME, so as to indicate that the MME sends a fourth processing requirement message to the MeNB, where the third processing requirement message includes the S1APID allocated by the SeNB and/or the MME for the UE, the routing information of the MeNB, and the processing requirement information, and the fourth processing requirement message includes the S1APID allocated by the MME and/or the MeNB for the UE and the processing requirement information.

48. The apparatus according to any of claims 42 to 47, wherein the processing information comprises rejection processing information rejecting dual connectivity processing for the SeNB.