CN105307149A - A method and device for managing neighbor relationship - Google Patents

Abstract

The present invention discloses a method for managing neighboring cell relations. An evolved node B (eNB) acquires neighboring cell information whether it supports dual connectivity (DC), and performs inter-cell cooperation according to the neighboring cell information; the present invention also discloses A device for managing neighbor relationship.

Description

A method and device for managing neighbor relationship

technical field

The present invention relates to mobile communication technology, in particular to a method and device for managing neighbor relationship.

Background technique

The deployment and capability enhancement of small cells has been confirmed by Third Generation Partnership Projects (3GPP, Third Generation Partnership Projects) as one of the most interesting topics in future network development. At present, the industry is concerned about deploying low-power nodes within the coverage area or at the border of macro base stations, and the macro base stations and low-power nodes together form the access network in the system architecture of Evolved Universal Terrestrial Radio Access Network (E-UTRAN, EvolvedUniversalTerrestrialRadioAccessNetwork). The scenario of providing joint data transmission services for user equipment (UE, UserEquipment) through a network is very recognized, and this system architecture has been basically determined.

In this system architecture, as shown in Figure 1, a base station that has an S1-MME interface with a mobility management entity (MME, MobilityManagementEntity) in the core network (CN, CoreNetwork) and is regarded as a mobility anchor by the CN, It is called the main base station (MeNB, Master eNB); the node connected to the MeNB through the X2 interface and provides additional wireless resources for the UE is called the secondary base station (SeNB, Secondary eNB). When there is a performance requirement and the conditions are met, the MeNB will select a suitable SeNB for the UE and trigger the SeNB addition procedure; after the procedure is completed, a wireless Uu interface is established between the UE, the MeNB, and the SeNB, that is, the UE is in dual connectivity ( DC, Dual Connectivity). This means that the UE can obtain radio resources from two eNBs, and its data transmission throughput can be greatly improved.

On the other hand, in the original single-link system, in order to reduce the operator's manual management of the neighbor relationship between the nodes in the huge communication system, a system called "Automatic NeighbourRelation" (ANR, Automatic NeighbourRelation) can be used in the system. " function to manage. The main control of this function is the operation and management (OAM, Operation and Management) node. The OAM node configures the neighbor relationship (NR, NeighborRelations) and corresponding attributes (attribute) for the evolved node B (eNB), and can report to the eNB Neighboring cell relationship to agree/deny response, the attributes are one-way, including: NoRemove, NoHO and NoX2; eNB can configure NR through communication with UE and adjacent eNB and internal algorithm, add or delete The neighbor relationship list (NRT, NeighborRelationTable) maintained by itself, and kept synchronized with the OAM node.

Under the DC system architecture, how to reduce the burden on operators to manage complex communication networks and prevent MeNB from initiating the SeNB addition procedure for some eNBs that cannot undertake dual-connection transmission is a technical problem that needs to be solved urgently.

Contents of the invention

In order to solve the existing technical problems, the present invention mainly provides a method and device for managing the relationship between adjacent cells.

Technical scheme of the present invention is realized like this:

A method for managing neighbor relationship provided by the present invention, the method includes:

The eNB acquires information about adjacent cells whether it supports DC, and performs inter-cell coordination according to the information about adjacent cells.

In the above solution, the eNB obtaining the information of neighboring cells whether supporting DC includes: the eNB obtaining the information of neighboring cells supporting DC from an air interface.

In the above solution, the obtaining by the eNB of the neighboring cell information of whether the DC is supported includes: the eNB obtaining the information of the neighboring cell of whether the DC is supported from the X2/S1 interface.

In the above solution, the eNB obtaining the neighboring cell information whether to support the DC includes: the eNB obtaining the neighboring cell information whether to support the DC from the OAM node.

In the above solution, the eNB obtains the neighbor cell information of whether DC is supported from the air interface including: the eNB receives the neighbor cell relationship reported by the user equipment (UE) and its corresponding attribute from the air interface, and the attribute is whether the neighbor cell supports the DC to the eNB. The neighbor relationship attribute of whether to support the DC is acquired by the UE by reading the broadcast information of the neighbor cell.

In the above solution, the eNB obtains the neighbor cell information whether it supports DC from the X2/S1 interface, including: the eNB obtains the neighbor cell relationship and its corresponding attributes through the X2 control plane signaling interaction with other eNBs. Whether the area pair eNB supports the neighbor relationship attribute of DC; or, the eNB communicates with the core network node through the S1 interface to obtain the information neighbor relationship and its corresponding attributes, and the attribute is whether the neighbor cell supports the DC neighbor relationship to the eNB Zone relationship attribute.

In the above solution, the eNB obtaining the neighbor cell information that does not support DC from the OAM includes: the eNB receives the new neighbor cell relationship sent by the OAM and its corresponding attributes, and the attribute is the neighbor cell relationship of whether the eNB supports DC Attributes.

In the above solution, the acquisition of the neighbor cell information of whether the eNB supports DC includes: the eNB obtains the neighbor cell relationship and the neighbor cell relationship attribute of whether the eNB supports DC from the air interface or the X2/S1 interface, and reports the neighbor cell relationship and its attributes to OAM, and receive the consent response from OAM.

In the above solution, performing inter-cell cooperation according to the neighboring cell information includes: performing inter-cell mobility operation, load balancing, or service transmission according to the neighboring cell information of whether DC is supported.

In the above scheme, performing the inter-cell mobility operation based on whether or not DC-supported neighbor cell information includes: when performing inter-cell mobility operation, using the eNB neighbor cell as the SeNB addition request according to the DC-supported neighbor cell information One of the consideration nodes does not take the neighbor cell of the eNB as the consideration node of the SeNB addition request according to the neighbor cell information that does not support the DC.

In the above scheme, performing load balancing between cells according to the information of neighboring cells supporting DC or not includes: when performing load balancing between cells, using the neighboring cells of the eNB as the target cell of load balancing according to the information of neighboring cells supporting DC, According to the information of neighboring cells that do not support DC, the neighboring cells of the eNB are not used as the target cells for load balancing.

In the above solution, the inter-cell service transmission according to the information of the neighboring cells supporting DC includes: when performing the service transmission between the cells, requesting resources from the neighboring cells of the eNB according to the information of the neighboring cells supporting DC to jointly transmit data , not requesting resources from neighboring cells of the eNB according to the information of neighboring cells that do not support DC.

In the above solution, the method further includes: writing the acquired neighbor relationship and the neighbor relationship attribute of whether the neighbor supports DC to the eNB into the neighbor relationship list (NRT).

In the above scheme, the method further includes: after the eNB writes the neighbor relationship attribute of the neighbor relationship and whether the neighbor supports DC to the eNB into the NRT configured by itself, writes the neighbor relationship and whether the neighbor supports the eNB The neighbor relationship attribute of the DC is reported to the OAM, so that the OAM updates the NRT stored by itself after receiving it.

A device for managing neighbor relationship provided by the present invention, the device includes: an acquisition module and a processing module; wherein,

An acquisition module, configured to acquire neighboring cell information of whether DC is supported, and send the acquired neighboring cell information to a processing module;

A processing module, configured to perform inter-cell cooperation according to the neighboring cell information.

In the above solution, the acquiring module is specifically configured to acquire the neighboring cell information of whether DC is supported or not from the air interface.

In the above solution, the acquiring module is specifically configured to acquire the neighboring cell information of whether DC is supported from the X2/S1 interface.

In the above solution, the acquiring module is specifically configured to acquire the neighboring cell information of whether DC is supported from the OAM.

In the above solution, the acquisition module is specifically used to receive the neighbor relationship reported by the UE from the air interface and its corresponding attributes, the attribute is the neighbor relationship attribute of whether the eNB to which the acquisition module belongs supports DC, and the whether The neighboring cell relation attribute supporting DC is obtained by the UE by reading the broadcast information of the neighboring cell.

In the above solution, the acquisition module is specifically used to obtain the neighbor cell relationship and its corresponding attributes through X2 control plane signaling interaction with eNBs other than its own eNB. The attribute is the neighbor cell to which the acquisition module belongs Whether the eNB supports the neighbor relationship attribute of the DC; or, communicate with the core network node through the S1 interface to obtain the information neighbor relationship and its corresponding attributes, and the attribute is whether the eNB of the neighbor pair acquisition module supports the neighbor relationship of the DC Zone relationship attribute.

In the above solution, the acquisition module is specifically used to receive the new neighbor relationship sent by OAM and its corresponding attribute, and the attribute is the neighbor relationship attribute of whether the eNB to which the acquisition module belongs supports DC.

In the above solution, the acquisition module is also used to acquire the neighbor relationship from the air interface or the X2/S1 interface and the neighbor relationship attribute of whether the eNB to which the acquisition module belongs supports DC, and report the neighbor relationship and its attributes to The OAM, after receiving the consent response from the OAM, sends the neighbor relationship and its attributes to the processing module.

In the above solution, the device further includes: a writing module, configured to write the acquired neighbor relationship and the neighbor relationship attribute of whether DC is supported into the NRT.

In the above solution, the processing module is specifically configured to perform inter-cell mobility operations, or load balancing, or service transmission according to information about neighboring cells supporting DC.

In the above scheme, the processing module is specifically configured to use the neighbor cell of the eNB as one of the considered nodes for the SeNB addition request according to the neighbor cell information supporting the DC when performing the mobility operation between cells, The cell information does not take the neighboring cell of the eNB as the considered node of the SeNB addition request.

In the above solution, the processing module is specifically used to set the eNB's neighbor cell as the load balancing target cell according to the neighbor cell information supporting DC when performing load balancing between cells, and set the eNB neighbor cell Neighboring cells are not the target cells for load balancing.

In the above solution, the processing module is specifically used to request resources from the neighboring cells of the eNB according to the information of the neighboring cells supporting the DC when performing service transmission between cells, so as to jointly transmit data, and according to the information of the neighboring cells not supporting the DC Request resources from neighboring cells of the eNB.

In the above solution, the acquisition module is further configured to report the neighbor relationship written in the NRT and the neighbor relationship attribute of whether DC is supported to the OAM, so that the OAM updates the NRT saved by itself after receiving it.

The present invention provides a method and device for managing the relationship between neighboring cells. The eNB obtains the information of neighboring cells whether it supports DC, and performs inter-cell cooperation according to the neighboring cell information; thus, under the dual connectivity system architecture, the eNB can Automatic and fast self-management of zone relations, reducing the burden on operators and unnecessary signaling between nodes.

Description of drawings

FIG. 1 is a schematic diagram of a heterogeneous network deployment in the prior art;

FIG. 2 is a schematic flowchart of a method for managing neighbor cell relationships provided by an embodiment of the present invention;

Fig. 3 is a schematic flow chart of Embodiment 1 of the present invention;

FIG. 4 is a schematic flow diagram of Embodiment 2 of the present invention;

Fig. 5 is a schematic flow chart of Embodiment 3 of the present invention;

FIG. 6a is a schematic diagram of cell relationships included in message 1 in Embodiment 3 of the present invention;

FIG. 6b is a schematic diagram of cell relationships included in message 2 in Embodiment 3 of the present invention;

FIG. 7 is a schematic structural diagram of an apparatus for managing neighbor cell relationships provided by an embodiment of the present invention.

detailed description

In the example of the present invention, the eNB obtains the information of neighboring cells supporting DC, and performs inter-cell cooperation according to the neighboring cell information. In this way, under the dual-linkage system architecture, the eNB can timely and accurately obtain the neighboring cells that cannot be used for DC purposes. The regional relationship is of great benefit to the distribution service deployment, throughput improvement, and signaling reduction of the entire network.

The present invention will be further described in detail below with reference to the accompanying drawings and specific embodiments.

The embodiment of the present invention implements a method for managing the relationship between adjacent cells, as shown in Figure 2, the method mainly includes the following steps:

Step 201: the eNB obtains the information of neighboring cells supporting DC;

In this step, whether to support the neighboring cell information of the DC can be the ability identification information of whether it can be a DC, or a newly defined neighboring cell relationship attribute, and the neighboring cell relationship attribute indicates whether to support the DC, for example: define a new Neighboring cell relationship attribute, the neighbor cell relationship attribute defaults to indicate that the neighbor cell supports DC for the eNB, and the neighbor cell relationship attribute is NoDC, indicating that the neighbor cell does not support DC for the eNB; thus, if the eNB detects that the neighbor cell relationship attribute is NoDC , then the eNB cannot use the neighbor relationship for DC purposes. It should be noted that NoDC is only an example name in this embodiment, and attributes whose actual attributes are the same as those defined in this embodiment belong to the protection scope of the present invention.

In this step, the eNB obtains the neighbor cell information of whether DC is supported, including but not limited to the following three methods:

1) The eNB obtains the neighbor cell information of whether DC is supported from the air interface. Specifically, the eNB receives the neighbor cell relationship reported by the UE and its corresponding attributes from the air interface, and the attribute is the neighbor cell relationship attribute of whether the eNB supports DC; Here, the neighbor cell relationship attribute of whether the eNB supports DC is acquired by the UE by reading the broadcast information of the neighbor cell.

2) The eNB obtains the neighbor cell information whether it supports DC from the X2/S1 interface. Specifically, the eNB obtains the neighbor cell relationship and its corresponding attributes through the X2 control plane signaling interaction with other eNBs. The attribute is the neighbor cell pair Whether the eNB supports the neighbor relationship attribute of the DC; wherein, the X2 control plane signaling can be an existing X2-CP program, such as the X2 setup program (X2Setup), eNB configuration update program (eNBConfigurationUpdate); it can also be a new one X2 control surface program. In addition, the eNB can also communicate with the core network node through the S1 interface to obtain the information about the neighbor cell relationship and its corresponding attribute, and the attribute is the neighbor cell relationship attribute of whether the eNB supports DC.

3) The eNB obtains from the OAM the neighbor cell information of whether it supports DC. Specifically, the eNB receives the new neighbor cell relationship and its corresponding attributes sent by the OAM. The attribute is the neighbor cell relationship attribute of whether the eNB supports DC.

For methods 1) and 2), the eNB can only obtain the neighbor relationship from the air interface or the X2 interface, and the neighbor relationship attribute of whether the eNB supports DC is determined by the interaction between the eNB and the OAM to get.

This step may also include: after the eNB acquires the neighbor relationship and the neighbor relationship attribute of whether the eNB supports DC from the air interface or the X2/S1 interface, first report the neighbor relationship and its attributes to the OAM, and after receiving After the OAM agrees to respond, write the neighbor cell relationship and its attributes into the NRT;

After the eNB acquires the neighbor cell relationship and the neighbor cell relationship attribute of whether the eNB supports the DC from the OAM, it writes the neighbor cell relationship and its attribute into the NRT.

Step 202: eNB performs inter-cell cooperation according to the neighbor cell information;

Specifically, the eNB performs inter-cell mobility operations, or load balancing, or service transmission processing according to whether the adjacent cell information of the DC is supported, for example:

The eNB has business and performance requirements. If the load is too heavy, it needs to offload the large data traffic of the UE. If the wireless signal quality of the detection cell (that is, the neighboring cell of the eNB) is known through the measurement report of the UE, and The neighbor relationship attribute of the detection cell to the eNB supports DC, then the eNB takes the detection cell as one of the considered nodes for the SeNB addition request; if the detection cell's neighbor relationship attribute to the eNB does not support DC , then the eNB does not use the probing cell as a considered node for the SeNB addition request;

For another example, when the eNB performs load balancing, if the neighbor cell relationship attribute of the detection cell to the eNB supports DC, then the eNB considers the detection cell as the target cell when making load balancing decisions; if the detection cell If the neighbor relationship attribute of the eNB does not support DC, it can be considered that the detection cell does not have additional potential load carrying capacity, and the eNB does not include the detection cell in the target cell when making load balancing decisions. within the scope of consideration.

For another example, when the eNB is performing service transmission, its own resources are not enough to provide the transmission speed required by the service. At this time, if the neighbor cell relationship attribute of the detection cell to the eNB supports DC, then the eNB requests resources from the detection cell to Commonly transmit data; if the attribute of the neighboring cell relationship between the probing cell and the eNB does not support DC, then the eNB does not request resources from the probing cell.

Through the method of this embodiment, under the dual-linkage system architecture, the eNB can obtain the neighbor cell relationship in a timely and accurate manner, which is of great benefit to offload service deployment, throughput improvement, and signaling reduction of the entire network.

The specific application of the present invention will be described in detail below in conjunction with the embodiments.

Embodiment one

In a heterogeneous network, the serving eNB configures the UE to perform signal measurement, and reads and reports the neighbor relationship attributes broadcast by the detection cell; the eNB updates the NRT after exchanging information with the OAM. This embodiment assumes that the detection cell and the serving cell belong to different base stations, and the detection cell is a small cell. The specific steps are shown in Figure 3:

eNB1 is the current serving base station of the UE. The eNB1 instructs the UE to measure the cell on the target frequency point through control plane signaling, such as the report neighbor request (ReportNeighbourRequest), and receives the report reported by the UE through the report neighbor response (ReportNeighbourResponse). A physical cell identifier (PCI, PhysicalCellIdentifier) of a cell detected on the target frequency point, where the detected cell is eNB2;

The eNB1 instructs the UE to use the PCI as a parameter to read the system broadcast of the eNB2 by reporting a Global Cell Identity Request (ReportGlobal-CIDRequest) message, and the system broadcast includes: E-UTRANCellGlobalIdentifier (ECGI, E-UTRANCellGlobalIdentifier ), public land mobile network (PLMN, PublicLandMobileNetwork) and other parameters, and also includes the neighbor relationship attribute of whether eNB2 supports DC to eNB1. Here, the neighbor relationship attribute is that eNB2 does not support DC to eNB1, and the eNB2 The neighbor relationship attribute can be configured by OAM;

The UE reads the system broadcast (ReadBCCH), and reports the acquired information to the eNB1 through a ReportGlobal-CID message;

The eNB1 saves the neighbor relationship attribute that the eNB2 does not support the DC to eNB1, and performs mobility operations, load balancing, and service transmission according to the neighbor relationship attribute that does not support the DC, for example:

If the eNB1 has service and performance requirements, such as heavy load, and needs to offload the large data volume service of the UE, then although it is known that the radio signal quality of the eNB2 is high through the measurement report of the UE, because the The eNB2 does not support the DC for the neighbor relationship attribute of the eNB1, so the eNB1 will not send a SeNB addition request message to the eNB2;

When the eNB1 is considering load balancing, because the eNB2 does not support DC for the neighbor relationship attribute of eNB1, it can be considered that the eNB2 does not have additional potential load carrying capacity, and the eNB1 is doing load balancing The eNB2 is not included in the scope of consideration of the target cell during relevant decisions.

In the following embodiment, the usage of the neighbor relationship attribute by the eNB that receives the neighbor relationship attribute that does not support DC is the same as that described in Embodiment 1, and will not be repeated here.

In this embodiment, the manner in which the eNB1 updates the neighbor cell relationship and its attributes with OAM synchronously may be (the rest of the embodiments take one of them as an example):

The eNB1 reports the neighbor relationship and eNB2's neighbor relationship attribute that eNB1 does not support DC to the OAM through the neighbor relationship report (NeighbourRelationReport), and then receives the OAM's consent response, such as adding/updating the neighbor relationship message (Add/UpdateNeighbourRelation), the eNB1 writes the neighbor relationship and eNB2's neighbor relationship attribute that eNB1 does not support DC into the NRT configured by itself;

Alternatively, the eNB1 writes the neighbor relationship and the neighbor relationship attribute of eNB2 to eNB1 that does not support DC into the NRT configured by itself, and reports the neighbor relationship and the neighbor relationship attribute of eNB2 to eNB1 that does not support DC to The OAM updates the NRT saved by the OAM after receiving it.

Embodiment two

In a heterogeneous network, the X2 interface is established between the macro base station and the low-power node through the X2 control plane program. During the X2 control plane signaling interaction process, the signaling sending node can provide the signaling receiving node with its own configured serving cell and neighbor Area information, including whether each cell supports the DC neighbor relationship attribute. The specific steps are shown in Figure 4:

eNB1 triggers the X2 Setup (Setup) procedure by sending an X2 Setup Request (X2SETUPREQUEST) message to eNB2, and the eNB2 replies with an X2 Setup Response (X2SETUPRESPONSE) message to complete the X2Setup procedure, wherein both X2 control plane signaling carry The serving cell information (ServedCellInformation) configured by the node itself may also carry a neighbor information (NI, NeighbourInformation) information element, and the NI includes information such as ECGI and PCI of the E-UTRAN cell directly adjacent to the serving cell, The two X2 control plane signalings also carry the neighbor relationship attribute of whether each cell supports DC;

In this embodiment, the two X2 control plane signaling may also include a list of neighboring cells that support DC, for example: a list of target cells that can provide dual connectivity services for the serving cell and/or neighboring cells; in addition, the NI signal The element may also include a list of PLMNs supported by the neighboring cell;

The eNB1 or eNB2 reports the neighbor relationship indicated by the peer node and the neighbor relationship attribute of whether it supports DC to the OAM through the neighbor relationship report (NeighbourRelationReport), and then receives the consent response from the OAM, such as adding/updating A neighbor relationship message (Add/UpdateNeighbourRelation), the eNB1 or eNB2 writes the neighbor relationship and the neighbor relationship attribute of whether DC is supported into the NRT configured by itself;

If the eNB1 or eNB2 has a heavy service load and learns that the wireless signal quality of the peer node cell (including the serving cell or its neighbors) is relatively high, then the eNB1 or eNB2 according to whether the cell supports DC in its own NRT Neighboring cell relationship attributes determine whether to send a SeNB addition request message to the peer node cell in order to try to provide DC services for the UE.

It should be noted that this embodiment uses the X2Setup program as an example, but the steps and principles described are also applicable to other existing X2/S1 control plane processes, such as the eNB Configuration Update (eNBConfigurationUpdate) program.

Embodiment three

As mentioned in the background introduction, the attribute of the neighbor cell relationship is one-way, that is, the attribute from the source cell (source cell) to the target cell (target cell), so an X2 control plane procedure can be adopted, and the sending node requests the peer node Adjacent cell relationship and its attributes are replied to the end node. The sending node may update the neighbor relationship list after exchanging information with the OAM. The specific steps are shown in Figure 5:

eNB1 sends an X2 control plane message 1 to eNB2 (NeighbourRelationRequest is an example in Figure 5), the message 1 contains at least the information of each cell configured by the eNB1, such as Cell1 and Cell2, and it is assumed that the eNB2 configures The cells of the cell include Cell3 and Cell4, and the message 1 may also include the cell information of the neighbor cell of the eNB2 currently detected by the eNB1, as shown in FIG. 6(a), the neighboring cells of the Cell1 are the Cell3, Cell4, the cell adjacent to Cell2 is Cell4;

The eNB2 replies to the eNB1 with a response message 2 (NeighbourRelationResponse is used as an example in Figure 5), and the message 2 includes the neighbor relationship and the neighbor relationship attributes of the cell of the eNB2, as shown in Figure 6(b ), the attribute of the neighbor relationship of Cell3 is to support DC with Cell1, the attribute of the neighbor relationship of Cell4 is to support DC with Cell2, but Cell4 does not support DC with Cell1.

It should be noted that if the message 1 only contains the information of each cell configured by the eNB1, but does not contain the list of neighboring cells, then the eNB2 may include all the configured cells and the The neighbor relationship attribute of the eNB1 cell.

On the other hand, the specific implementation of the program can be various. For example, message 1 contains the currently configured neighbor relationship and its attributes. After receiving eNB2, it will verify the content contained in message 1 and carry the updated content in the In message 2; or, the message 2 carries a list of target cells that are supported by each configured cell of the eNB2 and can provide dual connectivity services, and the message 2 may also include the PLMN supported by each configured cell of the eNB2 information.

The eNB1 reports the neighbor relationship and the attribute of the neighbor relationship indicated in the message 2 to OAM, and then receives the consent response from the OAM, and the eNB1 reports the neighbor relationship and the attribute of the neighbor relationship Write the NRT configured by itself. Here, the neighbor relationship attribute written into the NRT is the neighbor relationship attribute of Cell4 and Cell1 that do not support DC.

The present invention also provides a device for managing the relationship between neighboring cells. The device can generally be set in the eNB. As shown in FIG. 7, the device includes: an acquisition module 71 and a processing module 72; wherein,

The obtaining module 71 obtains the information of adjacent cells supporting DC, and sends the obtained adjacent cell information to the processing module 72; the processing module 72 performs inter-cell cooperation according to the adjacent cell information.

The obtaining module 71 may be a protocol interface of the eNB, and the processing module 72 may be a processor of the eNB.

The acquiring module 71 can acquire the neighboring cell information whether to support DC from the air interface. Specifically, the acquiring module 71 receives the neighboring cell relationship and the corresponding attribute reported by the UE from the air interface, and the attribute is the adjacent cell pair acquiring module 71 Whether the eNB to which it belongs supports the neighbor relationship attribute of the DC, and whether the neighbor relationship attribute of the DC is supported is obtained by the UE by reading the broadcast information of the neighbor cell;

Alternatively, the obtaining module 71 obtains the neighboring cell information of whether DC is supported from the X2/S1 interface. Specifically, the obtaining module 71 obtains the neighboring cell through X2 control plane signaling interaction with other eNBs except the eNB to which it belongs. The relationship and its corresponding attributes, the attribute is the neighbor cell relationship attribute of whether the eNB to which the acquisition module 71 belongs supports DC; wherein, the X2 control plane signaling can be an existing X2-CP program, such as X2Setup, eNBConfigurationUpdate; it can also be a new X2 control plane program. In addition, the acquisition module 71 can also communicate with the core network node through the S1 interface to acquire the information neighbor relationship and its corresponding attribute, the attribute is the neighbor relationship of whether the eNB to which the acquisition module 71 belongs supports DC Attributes;

Alternatively, the acquiring module 71 acquires the neighboring cell information of whether DC is supported from the OAM, specifically, the acquiring module 71 receives the new neighboring cell relationship and its corresponding attribute sent by the OAM, and the attribute is the neighboring cell pair acquiring module 71 Whether the eNB to which it belongs supports the neighbor relationship attribute of the DC.

The acquisition module 71 is also used to obtain the neighbor relationship and the neighbor relationship attribute of whether the eNB to which the acquisition module 71 belongs supports DC from the air interface or the X2/S1 interface, and then first report the neighbor relationship and its attributes To the OAM, after receiving the consent response from the OAM, send the neighbor relationship and its attributes to the processing module 72 .

The device also includes a writing module 73, configured to write the acquired neighbor relationship and the neighbor relationship attribute of whether DC is supported into the NRT.

The processing module 72 is specifically configured to perform mobility operations, load balancing, or service transmission between cells according to the information of neighboring cells supporting DC, wherein, when performing mobility operations between cells, according to the neighboring cells supporting DC The area information regards the neighboring cell of the eNB as one of the considered nodes for the SeNB addition request, and does not take the eNB’s neighboring cell as the consideration node for the SeNB addition request according to the neighboring cell information that does not support DC; when performing load balancing between cells, according to the support The neighboring cell information of DC regards the neighboring cell of eNB as the target cell of load balancing, and the neighboring cell of eNB is not regarded as the target cell of load balancing according to the neighboring cell information that does not support DC; Neighboring cell information of eNB requests resources from neighboring cells of eNB to jointly transmit data, and does not request resources from neighboring cells of eNB according to information of neighboring cells that do not support DC.

The acquisition module 71 is also configured to report the neighbor relationship written in the NRT and the attribute of whether it supports DC to the OAM, so that the OAM can update the NRT stored by itself after receiving it.

If the method for managing neighbor relationship in the embodiment of the present invention is implemented in the form of software function modules and sold or used as an independent product, it can also be stored in a computer-readable storage medium. Based on such understanding, those skilled in the art should understand that the embodiments of the present application may be provided as methods, systems, or computer program products. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Moreover, the present application may take the form of a computer program product implemented on one or more computer-usable storage media containing computer-usable program code therein, including but not limited to U disk, removable hard disk, read-only memory ( ROM, Read-Only Memory), disk storage, CD-ROM, optical storage, etc.

The present application is described according to the flowcharts and/or block diagrams of the methods, devices (systems), and computer program products of the embodiments of the present application. It should be understood that each procedure and/or block in the flowchart and/or block diagram, and a combination of procedures and/or blocks in the flowchart and/or block diagram can be realized by computer program instructions. These computer program instructions may be provided to a general purpose computer, special purpose computer, embedded processor, or processor of other programmable data processing equipment to produce a machine such that the instructions executed by the processor of the computer or other programmable data processing equipment produce a An apparatus for realizing the functions specified in one or more procedures of the flowchart and/or one or more blocks of the block diagram.

These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing apparatus to operate in a specific manner, such that the instructions stored in the computer-readable memory produce an article of manufacture comprising instruction means, the instructions The device realizes the function specified in one or more procedures of the flowchart and/or one or more blocks of the block diagram.

Correspondingly, an embodiment of the present invention further provides a computer storage medium, in which a computer program is stored, and the computer program is used to execute the method for managing neighbor relationship in the embodiment of the present invention.

The above description is only a preferred embodiment of the present invention, and is not used to limit the protection scope of the present invention. Any modifications, equivalent replacements and improvements made within the spirit and principles of the present invention shall be included in the within the protection scope of the present invention.

Claims (28)

1. A method for managing a neighbor relation, the method comprising:

an evolved node B (eNB) acquires neighbor cell information whether Dual Connectivity (DC) is supported, and performs inter-cell cooperation according to the neighbor cell information.

2. The method of claim 1, wherein the eNB obtaining the neighbor cell information whether DC is supported comprises: and the eNB acquires the neighbor cell information whether to support the DC from the air interface.

3. The method of claim 1, wherein the eNB obtaining the neighbor cell information whether DC is supported comprises: the eNB acquires the neighbor information whether DC is supported or not from the X2/S1 interface.

4. The method of claim 1, wherein the eNB obtaining the neighbor cell information whether DC is supported comprises: the eNB acquires neighbor information whether DC is supported from an Operation and Administration (OAM) node.

5. The method of claim 2, wherein the eNB acquiring, from the air interface, the neighbor cell information whether the eNB supports DC comprises: the method comprises the steps that an eNB receives a neighboring cell relation reported by User Equipment (UE) and corresponding attributes of the neighboring cell relation from an air interface, wherein the attributes are the neighboring cell relation attributes of whether the neighboring cell supports the DC or not to the eNB, and the neighboring cell relation attributes of whether the DC is supported or not are acquired by the UE through reading broadcast information of the neighboring cell.

6. The method of claim 3, wherein the eNB obtaining the neighbor information whether DC is supported from an X2/S1 interface comprises: the eNB acquires the neighbor cell relationship and corresponding attributes thereof through carrying out X2 control plane signaling interaction with other eNBs, wherein the attributes are the neighbor cell relationship attributes of whether the neighbor cell supports the DC to the eNB; or, the eNB communicates with the core network node through an S1 interface to obtain the information neighbor relation and its corresponding attribute, where the attribute is a neighbor relation attribute of whether the neighbor supports DC for the eNB.

7. The method of claim 4, wherein the eNB obtaining non-DC capable neighbor cell information from OAM comprises: and the eNB receives a new neighbor cell relation and corresponding attributes thereof sent by the OAM, wherein the attributes are the neighbor cell relation attributes of whether the neighbor cell supports the DC or not to the eNB.

8. The method of claim 1, wherein the eNB obtaining the neighbor cell information whether DC is supported comprises: the eNB acquires the neighbor relation and the neighbor relation attribute of whether the neighbor supports the DC to the eNB from an air interface or an X2/S1 interface, reports the neighbor relation and the attribute to the OAM, and receives an approval response of the OAM.

9. The method of claim 1, wherein the performing inter-cell cooperation according to the neighbor cell information comprises: and carrying out mobility operation, load balancing or service transmission among the cells according to the adjacent cell information whether the DC is supported or not.

10. The method of claim 9, wherein the performing mobility operations between cells according to the neighbor cell information of whether DC is supported comprises: when mobility operation among cells is carried out, the neighbor cell of the eNB is used as one of the considered nodes of the SeNB addition request according to the neighbor cell information supporting DC, and the neighbor cell of the eNB is not used as the considered node of the SeNB addition request according to the neighbor cell information not supporting DC.

11. The method of claim 9, wherein the performing load balancing among cells according to the neighbor cell information of whether DC is supported comprises: and when the load among the cells is balanced, taking the adjacent cell of the eNB as a target cell for load balancing according to the adjacent cell information supporting DC, and not taking the adjacent cell of the eNB as the target cell for load balancing according to the adjacent cell information not supporting DC.

12. The method of claim 9, wherein the performing the inter-cell traffic transmission according to the neighbor cell information whether DC is supported comprises: when the service transmission between the cells is carried out, resources are requested to the adjacent cell of the eNB according to the adjacent cell information supporting the DC so as to transmit data together, and the resources are not requested to the adjacent cell of the eNB according to the adjacent cell information not supporting the DC.

13. The method of any one of claims 5 to 7, further comprising: and writing the obtained neighbor relation and the neighbor relation attribute of whether the neighbor pair eNB supports the DC into a neighbor relation list (NRT).

14. The method of claim 13, further comprising: and after writing the neighbor relation attribute of whether the neighbor relation and the neighbor pair eNB support the DC into the NRT configured by the eNB, reporting the neighbor relation and the neighbor relation attribute of whether the neighbor pair eNB support the DC to the OAM so as to update the NRT stored by the eNB after receiving the OAM.

15. An apparatus for managing neighbor relations, the apparatus comprising: the device comprises an acquisition module and a processing module; wherein,

the system comprises an acquisition module, a processing module and a processing module, wherein the acquisition module is used for acquiring the adjacent cell information whether to support the DC and sending the acquired adjacent cell information to the processing module;

and the processing module is used for carrying out inter-cell cooperation according to the neighbor cell information.

16. The apparatus of claim 15, wherein the obtaining module is specifically configured to obtain, from an air interface, neighboring cell information whether DC is supported.

17. The apparatus of claim 15, wherein the obtaining module is specifically configured to obtain the neighbor information of whether DC is supported from an X2/S1 interface.

18. The apparatus according to claim 15, wherein the obtaining module is specifically configured to obtain, from OAM, neighbor information whether DC is supported.

19. The apparatus of claim 16, wherein the obtaining module is specifically configured to receive, from an air interface, a neighboring cell relationship reported by the UE and a corresponding attribute thereof, where the attribute is a neighboring cell relationship attribute of whether the eNB to which the neighboring cell pair obtaining module belongs supports DC, and the neighboring cell relationship attribute of whether the DC is supported is obtained by reading broadcast information of a neighboring cell by the UE.

20. The apparatus of claim 17, wherein the obtaining module is specifically configured to obtain the neighboring cell relationship and the corresponding attribute thereof through performing X2 control plane signaling interaction with other enbs than the eNB to which the obtaining module belongs, where the attribute is a neighboring cell relationship attribute indicating whether the eNB to which the neighboring cell pair obtaining module belongs supports DC; or, the information neighbor relation and the corresponding attribute thereof are obtained through communication between an interface S1 and a core network node, where the attribute is a neighbor relation attribute of whether the eNB to which the neighbor pair obtaining module belongs supports DC.

21. The apparatus according to claim 18, wherein the obtaining module is specifically configured to receive a new neighbor relation sent by OAM and a corresponding attribute thereof, where the attribute is a neighbor relation attribute of whether an eNB to which the neighbor pair obtaining module belongs supports DC.

22. The apparatus of claim 15, wherein the obtaining module is further configured to obtain, from an air interface or an X2/S1 interface, the neighboring cell relationship and a neighboring cell relationship attribute of whether an eNB to which the neighboring cell pair obtaining module belongs supports DC, report the neighboring cell relationship and the attribute thereof to the OAM, and send the neighboring cell relationship and the attribute thereof to the processing module after receiving an approval response of the OAM.

23. The apparatus of any one of claims 19 to 21, further comprising: and the writing module is used for writing the obtained adjacent region relationship and the adjacent region relationship attribute of whether the DC is supported into the NRT.

24. The apparatus of claim 15, wherein the processing module is specifically configured to perform mobility operation between cells, or load balancing, or service transmission according to whether or not DC-capable neighbor cell information is supported.

25. The apparatus of claim 24, wherein the processing module is configured to, when performing mobility operation between cells, use a neighboring cell of the eNB as one of the considered nodes of the SeNB addition request according to the DC-capable neighboring cell information, and not use the neighboring cell of the eNB as the considered node of the SeNB addition request according to the DC-incapable neighboring cell information.

26. The apparatus of claim 24, wherein the processing module is specifically configured to, when performing load balancing between cells, use a neighboring cell of the eNB as a target cell for load balancing according to DC-capable neighboring cell information, and use a neighboring cell of the eNB not as a target cell for load balancing according to non-DC-capable neighboring cell information.

27. The apparatus of claim 24, wherein the processing module is specifically configured to, when performing inter-cell service transmission, request resources to a neighbor cell of the eNB according to DC-capable neighbor cell information to jointly transmit data, and not request resources to the neighbor cell of the eNB according to non-DC-capable neighbor cell information.

28. The apparatus of claim 23, wherein the obtaining module is further configured to report the neighbor relation written in the NRT and the attribute of the neighbor relation whether DC is supported to the OAM, so that the OAM receives and then updates the NRT stored in itself.