WO2015188494A1 - 一种管理邻区关系的方法和装置、存储介质 - Google Patents

一种管理邻区关系的方法和装置、存储介质 Download PDF

Info

Publication number
WO2015188494A1
WO2015188494A1 PCT/CN2014/086848 CN2014086848W WO2015188494A1 WO 2015188494 A1 WO2015188494 A1 WO 2015188494A1 CN 2014086848 W CN2014086848 W CN 2014086848W WO 2015188494 A1 WO2015188494 A1 WO 2015188494A1
Authority
WO
WIPO (PCT)
Prior art keywords
enb
neighboring area
cell
neighboring
attribute
Prior art date
Application number
PCT/CN2014/086848
Other languages
English (en)
French (fr)
Inventor
王昕�
韩立锋
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2015188494A1 publication Critical patent/WO2015188494A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management

Definitions

  • the present invention relates to mobile communication technologies, and in particular, to a method and apparatus for managing a neighbor relationship, and a storage medium.
  • E-UTRAN evolved Evolved Universal Terrestrial Radio Access Network
  • an mobility management entity in a core network (CN, Core Network) has an S1-MME interface and is regarded as a mobility anchor by the CN.
  • a base station referred to as a primary base station (MeNB, Master eNB); a node connected to the MeNB and connected to the X2 interface to provide additional radio resources to the UE is called a secondary base station (SeNB, Secondary eNB).
  • the MeNB selects a suitable SeNB for the UE and triggers the SeNB to add a procedure.
  • the UE and the MeNB and the SeNB each have a wireless Uu port, that is, the UE is in dual connectivity ( DC, Dual Connectivity). This means that the UE can acquire radio resources from two eNBs, and its data transmission throughput can be greatly improved.
  • Neighbour Relations and corresponding attributes, and may respond to the neighboring area reported by the eNB by the consent/rejection class, the attributes are unidirectional, including: NoRemove, NoHO, and NoX2; the eNB may pass The communication between the UE and the neighboring eNB and the internal algorithm configure the NR, add or delete the Neighbor Relation List (NRT) maintained by itself, and keep in sync with the OAM node.
  • NRT Neighbor Relation List
  • the embodiments of the present invention provide a method and device for managing a neighbor relationship, and a storage medium, so that the eNB can automatically and quickly manage the neighbor relationship under the dual-connection system architecture. Reduce the burden on operators and unnecessary signaling between nodes.
  • the eNB acquires whether the neighboring cell information of the DC is supported, and performs inter-cell cooperation according to the neighboring cell information.
  • the acquiring, by the eNB, whether the neighboring area information of the DC is supported includes: acquiring, by the eNB, whether the neighboring area information of the DC is supported from the air interface.
  • the acquiring, by the eNB, whether the neighboring area information of the DC is supported includes: acquiring, by the eNB, the neighboring area information of the DC from the X2/S1 interface.
  • the acquiring, by the eNB, whether the neighboring area information of the DC is supported includes: acquiring, by the eNB, the neighboring area information of the DC from the OAM node.
  • the acquiring, by the eNB, whether the neighboring area information of the DC is supported by the air interface comprises: receiving, by the eNB, the neighboring area relationship reported by the user equipment (UE) and the corresponding attribute from the air interface, where the attribute is whether the neighboring area supports the DC by the eNB.
  • the neighbor relationship attribute, whether the neighboring area relationship attribute of the DC is supported, is obtained by the UE by reading the broadcast information of the neighboring area.
  • the acquiring, by the eNB, the neighboring area information of the DC from the X2/S1 interface includes: the eNB acquires a neighbor relationship and a corresponding attribute by performing X2 control plane signaling interaction with other eNBs, where the attribute is a neighboring area. Whether the eNB supports the DC neighbor relationship attribute; or the eNB communicates with the core network node through the S1 interface to obtain the information neighbor relationship and its corresponding attribute, where the attribute is whether the neighboring area supports the DC neighboring area of the eNB. Relationship attribute.
  • the acquiring, by the eNB, whether the neighboring area information of the DC is supported includes: the eNB acquiring the neighboring area relationship from the air interface or the X2/S1 interface, and the neighboring area relationship attribute of the neighboring area to the eNB supporting the DC, reporting the neighboring area relationship and Its attributes are given to OAM and receive an OAM consent response.
  • the performing inter-cell cooperation according to the neighboring area information comprises: performing inter-cell mobility operation, or load balancing, or service transmission according to whether the DC neighboring area information is supported.
  • the performing the inter-cell mobility operation according to whether the DC neighboring area information is supported includes: considering, when the inter-cell mobility operation is performed, the neighboring area of the eNB as the SeNB adding request according to the DC-supported neighboring area information One of the nodes does not add the neighboring cell of the eNB as the considered node of the SeNB addition request according to the neighboring cell information that does not support the DC.
  • the performing load balancing between cells according to whether the DC neighboring area information is supported includes: when performing load balancing between cells, using a neighboring area of the eNB as a target cell for load balancing according to the neighboring area information supporting the DC, according to The neighboring area information of the DC is not supported, and the neighboring area of the eNB is not used as the target cell for load balancing.
  • the performing the inter-cell service transmission according to whether the DC neighboring area information is supported includes: when performing the inter-cell service transmission, requesting resources from the neighboring area of the eNB according to the DC-supported neighboring area information, to jointly transmit the data,
  • the neighboring area information that does not support the DC does not request resources from the neighboring area of the eNB.
  • the method further includes: writing the acquired neighbor relationship and the neighbor relationship attribute of the neighboring area to whether the eNB supports DC to the neighbor relationship list (NRT).
  • NRT neighbor relationship list
  • the method further includes: after the eNB writes the neighbor relationship and the neighbor relationship attribute of the neighboring area to the eNB to support the DC to the NRT configured by the eNB, whether the neighbor relationship and the neighboring area support the DC by the neighboring area
  • the neighbor relationship attribute is reported to the OAM, so that the OAM is updated after the OAM is received.
  • An apparatus for managing a neighbor relationship is provided by an embodiment of the present invention, where the apparatus includes: an acquiring module and a processing module;
  • Obtaining a module configured to obtain the neighboring area information of the DC, and send the obtained neighboring area information to the processing module;
  • the processing module is configured to perform inter-cell cooperation according to the neighboring area information.
  • the acquiring module is specifically configured to acquire, from the air interface, whether the neighboring area information of the DC is supported.
  • the acquiring module is specifically configured to acquire, from the X2/S1 interface, whether the neighboring area information of the DC is supported.
  • the acquiring module is specifically configured to acquire, from the OAM, whether the neighboring cell information of the DC is supported.
  • the acquiring module is configured to receive the neighboring cell relationship reported by the UE and the corresponding attribute from the air interface, where the attribute is a neighboring cell relationship attribute of the neighboring cell to the eNB to which the acquiring module belongs, and whether the supporting attribute is supported.
  • the neighbor relationship attribute of the DC is obtained by the UE by reading the broadcast information of the neighboring area.
  • the acquiring module is configured to acquire a neighbor relationship and a corresponding attribute by performing X2 control plane signaling interaction with other eNBs other than the eNB to which the eNB belongs.
  • the attribute is an eNB of the neighboring cell to the acquiring module.
  • the S1 interface communicates with the core network node to obtain the information neighboring area relationship and its corresponding attribute, where the attribute is a neighboring area to whether the eNB to which the acquiring module belongs supports the DC neighboring area. Relationship attribute.
  • the acquiring module is configured to receive a new neighboring cell relationship and its corresponding attribute sent by the OAM, where the attribute is a neighboring cell relationship attribute of the neighboring cell to the eNB to which the acquiring module belongs.
  • the acquiring module is further configured to obtain a neighbor relationship from the air interface or the X2/S1 interface, and to determine whether the eNB of the acquiring module supports the DC neighbor relationship attribute, and report the neighbor relationship and its attribute to the OAM. After receiving the consent response of the OAM, the neighbor relationship and its attributes are sent to the processing module.
  • the apparatus further includes: a writing module configured to write the acquired neighbor relationship and the neighbor relationship attribute of the DC support to the NRT.
  • the processing module is specifically configured to perform inter-cell mobility operation, or load balancing, or service transmission according to whether the DC neighbor information is supported.
  • the processing module is configured to: when the inter-cell mobility operation is performed, use the neighboring area of the eNB as one of the considered nodes of the SeNB to add the request according to the neighboring area information supporting the DC, according to the neighboring area that does not support the DC.
  • the information does not add the neighboring cell of the eNB as the considered node of the SeNB addition request.
  • the processing module is configured to: when performing load balancing between cells, use the neighboring area of the eNB as a target cell for load balancing according to the neighboring area information supporting the DC, and the eNB according to the neighboring area information that does not support the DC.
  • the neighboring area is not used as the target cell for load balancing.
  • the processing module is configured to: when the inter-cell service transmission is performed, request resources from the neighboring area of the eNB according to the neighboring area information supporting the DC, to jointly transmit data, according to The neighboring area information supporting the DC does not request resources from the neighboring area of the eNB.
  • the acquiring module is further configured to report the neighbor relationship written in the NRT and the neighbor relationship relationship attribute of the DC to the OAM, so that the OAM saved by the OAM is updated after receiving the OAM.
  • an embodiment of the present invention provides a computer storage medium, where the computer storage medium stores computer executable instructions, where the computer executable instructions are used to perform the management of a neighbor relationship provided by the first aspect of the embodiments of the present invention. method.
  • An embodiment of the present invention provides a method and apparatus for managing a neighbor relationship, and a storage medium, wherein an eNB acquires whether to support DC neighbor information, and performs inter-cell cooperation according to the neighbor information; thus, in a dual connectivity system Under the architecture, the eNB can automatically and quickly manage the neighbor relationship, reducing the burden on the operator and unnecessary signaling between nodes.
  • FIG. 1 is a schematic diagram of deployment of a heterogeneous network in the prior art
  • FIG. 2 is a schematic flowchart of a method for managing a neighbor relationship according to an embodiment of the present invention
  • Embodiment 1 of the present invention is a schematic flowchart of Embodiment 1 of the present invention.
  • FIG. 5 is a schematic flowchart of Embodiment 3 of the present invention.
  • 6a is a schematic diagram of a cell relationship included in message 1 according to Embodiment 3 of the present invention.
  • 6b is a schematic diagram of a cell relationship included in message 2 in Embodiment 3 of the present invention.
  • FIG. 7 is a schematic structural diagram of an apparatus for managing a neighbor relationship according to an embodiment of the present invention.
  • the eNB acquires whether the neighboring area information of the DC is supported, and performs inter-cell cooperation according to the neighboring area information, so that, in the dual-link system architecture, the eNB can acquire the neighbor that cannot be used for the DC use in time and accurately.
  • Zone relationship, for the network's offloading service deployment, throughput l, signaling reduction has great benefits.
  • An embodiment of the present invention implements a method for managing a neighbor relationship. As shown in FIG. 2, the method mainly includes the following steps:
  • Step 201 The eNB acquires whether to support neighboring area information of the DC.
  • whether the DC neighbor information is supported may be the capability identification information of the DC, or may newly define a neighbor relationship attribute, and the neighbor relationship attribute indicates whether the DC is supported, for example, defining a new one.
  • the neighbor relationship attribute indicates that the neighbor relationship attribute indicates that the neighboring area supports the DC to the eNB, and the neighboring area relationship attribute is NoDC, indicating that the neighboring area does not support the DC to the eNB; thus, if the eNB detects that the neighbor relationship attribute is NoDC Then, the eNB cannot use the neighbor relationship for DC purposes.
  • the NoDC is only the name exemplified in the embodiment, and the attributes whose actual attributes are the same as those defined in the embodiment are all within the scope of protection of the present invention.
  • the manner in which the eNB obtains whether to support the neighboring area information of the DC includes but is not limited to the following three types:
  • the eNB obtains the neighboring area information of the DC from the air interface. Specifically, the eNB receives the neighboring area relationship reported by the UE and the corresponding attribute from the air interface, where the attribute is a neighboring area relationship attribute of the neighboring area to the eNB.
  • the neighboring cell relationship attribute of the neighboring cell to the eNB supporting the DC is obtained by the UE by reading the broadcast information of the neighboring cell.
  • the eNB obtains the neighboring area information of the DC from the X2/S1 interface. Specifically, the eNB acquires the neighbor relationship and its corresponding attribute by performing X2 control plane signaling interaction with other eNBs, where the attribute is a neighboring area pair. Whether the eNB supports the neighbor relationship attribute of the DC; wherein the X2 control plane signaling may be an existing X2-CP program, such as an X2 Setup (X2 Setup) or an eNB Configuration Update (eNB Configuration Update); Is the new X2 control surface program. In addition, the eNB may also communicate with the core network node through the S1 interface to obtain the information neighbor relationship. And its corresponding attribute, the attribute is a neighbor relationship attribute of whether the neighboring area supports the DC to the eNB.
  • the X2 control plane signaling may be an existing X2-CP program, such as an X2 Setup (X2 Setup) or an eNB Configuration Update (eNB Configuration Update); Is the new
  • the eNB obtains the neighboring area information of the DC from the OAM. Specifically, the eNB receives the new neighbor relationship and its corresponding attribute sent by the OAM, where the attribute is a neighbor relationship attribute of the neighboring area to the eNB.
  • the eNB can also obtain the neighbor relationship only from the air interface or the X2 interface, and the neighboring area interacts with the OAM by the eNB whether the eNB supports the DC neighbor relationship attribute. Come to get.
  • the step may further include: after the eNB obtains the neighbor relationship from the air interface or the X2/S1 interface, and the neighboring area supports the DC neighbor relationship attribute, the eNB first reports the neighbor relationship and its attribute to the OAM, and receives the OAM. After the OAM agrees to respond, the neighbor relationship and its attributes are written into the NRT;
  • the eNB relationship and its attributes are written into the NRT.
  • Step 202 The eNB performs inter-cell cooperation according to the neighboring area information.
  • the eNB performs mobility operations between cells, load balancing, or service transmission according to whether the DC neighbor information is supported, for example:
  • the eNB has a service and performance requirement. For example, if the load is too heavy, the large data volume service of the UE needs to be offloaded. If the measurement report of the UE is reported, the quality of the wireless signal of the detected cell (ie, the neighboring area of the eNB) is high, and The neighboring cell relationship attribute of the sounding cell to the eNB is a DC, and the eNB uses the sounding cell as one of the consideration nodes of the SeNB adding request; if the neighboring cell relationship attribute of the sounding cell to the eNB does not support DC And the eNB does not use the probe cell as a consideration node for adding a request to the SeNB;
  • the eNB when the eNB is performing load balancing, if the neighboring cell relationship attribute of the detecting cell to the eNB is DC, the eNB considers the detecting cell as a target cell when performing load balancing related determination; if the detecting cell If the neighbor relationship attribute of the eNB does not support DC, then the probe cell may be considered as having no additional potential load carrying capacity, and the eNB is When the relevant decision of load balancing is made, the detected cell is not included in the consideration of the target cell.
  • the eNB when the eNB is performing service transmission, its own resources are insufficient to provide the transmission speed required by the service. If the neighboring cell relationship attribute of the detecting cell to the eNB is DC, the eNB requests the resource from the detecting cell. The data is transmitted jointly; if the neighboring cell relationship attribute of the detecting cell to the eNB does not support DC, the eNB does not request resources from the detecting cell.
  • the eNB can obtain the neighbor relationship in a timely and accurate manner, which has great benefits for the off-network service deployment, throughput improvement, and signaling reduction of the entire network.
  • the serving eNB configures the UE to perform signal measurement, and reads and reports the neighbor relationship attribute broadcasted by the detecting cell.
  • the eNB updates the NRT after interacting with the OAM. This embodiment assumes the detecting 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:
  • the eNB1 is the current serving base station of the UE, and the eNB1 instructs the UE to measure the cell on the target frequency point by using the control plane signaling (Report Neighbour Request) (step 301), and the eNB1 receives the UE by reporting the neighboring neighbor.
  • a cell response (PCI, Physical Cell Identifier) of the cell detected at the target frequency (Report 302), the detected cell is eNB2;
  • the eNB1 instructs the UE to read the system broadcast of the eNB2 by using the PCI global parameter identification request (Report Global-CID Request) message (step 303), where the system broadcast includes: a globally unique identifier of the cell (ECGI, E-UTRAN Cell Global Identifier), Public Land Mobile Network (PLMN) parameters, and the neighboring zone relationship attribute of the eNB2 to the eNB1 supporting DC, where The neighbor relationship attribute is that eNB2 does not support DC to eNB1, and the neighbor relationship attribute of the eNB2 may be configured by OAM;
  • ECGI globally unique identifier of the cell
  • PLMN Public Land Mobile Network
  • the UE reads the system broadcast (Read BCCH) (step 304), and reports the obtained information to the eNB1 by reporting a Global Report (Report Global-CID) message (step 305);
  • the eNB1 saves the neighbor relationship relationship attribute that the eNB2 does not support DC to the eNB1, and performs mobility operation, load balancing, service transmission, and the like according to the neighbor relationship relationship attribute that does not support DC, for example:
  • the wireless signal quality of the eNB2 is known to be higher by the measurement reporting of the UE.
  • the eNB2 does not support the DC in the neighbor relationship attribute of the eNB1, so the eNB1 does not send the SeNB addition request message to the eNB2;
  • the eNB1 When the eNB1 considers load balancing, because the eNB2 does not support DC in the neighbor relationship attribute of the 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 consideration of the target cell when the decision is made.
  • the usage of the neighboring cell relationship attribute of the eNB that does not support the DC neighbor relationship attribute in the following embodiment is the same as that in the first embodiment, and will not be described again.
  • the manner in which the eNB1 synchronizes the neighbor relationship and its attributes with the OAM may be (the remaining embodiments are exemplified by one of them):
  • the eNB1 reports the neighbor relationship and the neighbor relationship attribute of the eNB2 to the eNB1 that does not support the DC to the OAM through the Neighbor Relation Report (step 306), and then receives the consent response of the OAM, such as adding /Update Neighbour Relation (Add/Update Neighbour Relation) (step 307), the eNB1 writes the neighbor relationship and the neighbor relationship attribute of the eNB2 to the eNB1 not supporting the DC into the NRT configured by itself;
  • the eNB1 associates the neighbor relationship with its neighboring area that eNB2 does not support DC for eNB1.
  • the attribute is written to the NRT configured by itself (step 308), and the neighbor relationship and the eNB2 report the neighbor relationship attribute of the eNB1 that does not support the DC to the OAM, and the OAM receives the NRT saved by itself after receiving.
  • the X2 interface is established between the macro base station and the low-power node through the X2 control plane program.
  • the signaling sending node can provide the signaling receiving node with its own configured serving cell and neighbor. The information of the area, including whether each cell supports the neighbor relationship attribute of the DC.
  • the eNB1 triggers an X2 Setup procedure (step 401) by transmitting an X2 SETUP REQUEST message to the eNB2, the eNB2 replies with an X2 SETUP RESPONSE message to complete the X2 Setup procedure (step 402).
  • the two X2 control plane signalings carry the Served Cell Information configured by the node, and may also carry Neighbor Information (NI) information, where the NI includes the serving cell Information such as the ECGI and the PCI of the directly adjacent E-UTRAN cell, and the two X2 control plane signalings also carry whether the neighboring cell relationship attributes of the DCs are supported by the cells;
  • NI Neighbor Information
  • the two X2 control plane signaling may further include a DC neighbor list, for example, a target cell list that may provide dual connectivity services for the serving cell and/or the neighboring cell;
  • the element may further include a list of PLMNs supported by the neighboring cell;
  • the eNB1 or the eNB2 reports the neighbor relationship indicated by the correspondent node and the neighbor relationship attribute of the DC support to the OAM through the Neighbor Relation Report (step 403), and then receives the consent of the OAM.
  • the eNB1 or eNB2 writes the neighbor relationship and the DC-related neighbor relationship attribute to the NRT configured by itself. (step 405);
  • the eNB1 or eNB2 If the eNB1 or eNB2 is overloaded with traffic and knows the peer node cell (including services) The radio signal quality of the cell or its neighboring cell is high, and the eNB1 or the eNB2 determines whether to send the SeNB addition request message to the peer node cell according to whether the cell supports the DC neighbor relationship attribute in the NRT. In an attempt to provide DC services to the UE.
  • the attribute of the neighbor relationship is unidirectional, that is, the attribute of the source cell to the target cell, so an X2 control plane procedure can be adopted, from the sending node to the opposite end.
  • the node requests the neighbor relationship and its attributes, and the peer node replies.
  • the sending node may update the neighbor relationship list after interacting with the OAM.
  • the eNB1 sends an X2 control plane message 1 (in the example of a Neighbor Relation Request in FIG. 5) to the eNB2 (step 501), where the message 1 includes at least each cell information configured by the eNB1, such as Cell1, Cell2, It is assumed that the cell configured by the eNB2 has Cell3 and Cell4, and the message 1 may further include the cell information of the neighboring eNB2 currently detected by the eNB1, as shown in FIG. 6(a), the neighbor of the Cell1.
  • the zone is the Cell3, Cell4, and the neighboring cell of the Cell2 is the Cell4;
  • the eNB2 replies to the eNB1 with a response message 2 (in the example of a Neighbor Relation Response (FIG. 502)) (step 502), where the message 2 includes the neighbor relationship and the neighbor relationship attribute of the cell of the eNB2.
  • the neighbor relationship attribute of Cell3 is to support DC with Cell1
  • the neighbor relationship attribute of Cell4 is to support DC with Cell2, but Cell4 does not support DC with Cell1.
  • the eNB2 may include all configured cells and the message in the message 2.
  • the neighbor relationship attribute of the eNB1 cell may be included.
  • the specific implementation of the program may be diverse.
  • the message 1 includes the currently configured neighbor relationship and its attributes.
  • the eNB2 verifies the content of the message 1 and carries the updated content.
  • the message 2 (step 504); or, the message 2 carries a target cell list supported by each configured cell of the eNB2 and can provide dual connectivity services, and the message 2 may further include the configuration of the eNB2.
  • PLMN information supported by the cell may be diverse.
  • the message 1 includes the currently configured neighbor relationship and its attributes.
  • the eNB2 verifies the content of the message 1 and carries the updated content.
  • the message 2 (step 504); or, the message 2 carries a target cell list supported by each configured cell of the eNB2 and can provide dual connectivity services, and the message 2 may further include the configuration of the eNB2.
  • PLMN information supported by the cell may be diverse.
  • the eNB1 reports the neighbor relationship and the neighbor relationship attribute indicated in the message 2 to the OAM (step 503), and then receives the consent response of the OAM, where the eNB1 associates the neighbor relationship with the
  • the neighbor relationship attribute is written into the NRT configured by itself (step 505).
  • the neighbor relationship attribute written to the NRT is a neighbor relationship attribute of Cell4 and Cell1 that do not support DC.
  • the embodiment of the present invention further provides an apparatus for managing a neighbor relationship, where the apparatus is generally disposed in an eNB, as shown in FIG. 7, the apparatus includes: an obtaining module 71, and a processing module 72;
  • the obtaining module 71 is configured to obtain the neighboring area information of the DC, and send the acquired neighboring area information to the processing module 72.
  • the processing module 72 is configured to perform inter-cell cooperation according to the neighboring area information.
  • the obtaining module 71 may be a protocol interface of an eNB, and the processing module 72 may be a processor of an eNB.
  • the obtaining module 71 is configured to acquire the neighboring area information of the DC from the air interface. Specifically, the acquiring module 71 is configured to receive, from the air interface, the neighbor relationship reported by the UE and its corresponding attribute, where the attribute is a neighbor. Whether the eNB to which the area pair acquisition module 71 supports the DC neighbor relationship attribute, whether the DC neighbor relationship attribute is supported by the UE is obtained by reading the broadcast information of the neighboring area;
  • the obtaining module 71 is configured to obtain, from the X2/S1 interface, whether to support DC neighboring area information.
  • the acquiring module 71 is configured to perform an X2 control plane by using an eNB other than the eNB to which the eNB belongs.
  • the signaling interaction acquires a neighbor relationship and a corresponding attribute thereof, where the attribute is a neighbor relationship attribute of the neighboring area pair acquiring module 71 to support DC;
  • the X2 control plane signaling may be an existing X2-CP program, such as X2 Setup, eNB Configuration Update; or may be a new X2 control plane program.
  • the acquiring module 71 may also communicate with the core network node to obtain the information neighboring cell relationship and its corresponding attribute by using the S1 interface, where the attribute is a neighboring cell relationship of the neighboring cell to the eNB to which the acquiring module 71 belongs. Attributes;
  • the obtaining module 71 is configured to acquire, from the OAM, whether to support the neighboring area information of the DC. Specifically, the acquiring module 71 is configured to receive a new neighboring area relationship and its corresponding attribute sent by the OAM, where the attribute Whether the neighboring cell pair access module 71 belongs to the eNB to support the DC neighbor relationship attribute.
  • the obtaining module 71 is further configured to: after obtaining the neighbor relationship and the neighboring cell to the eNB of the acquiring module 71 to support the DC neighbor relationship attribute, the neighboring area relationship and its attributes are first reported.
  • the OAM after receiving the OAM's consent response, sends the neighbor relationship and its attributes to the processing module 72.
  • the apparatus further includes a write module 73 configured to write the acquired neighbor relationship and whether the DC neighbor relationship attribute is supported to the NRT.
  • the processing module 72 is specifically configured to perform inter-cell mobility operations, or load balancing, or service transmission according to whether the DC neighbor information is supported, where the DC-supported neighbors are supported when performing inter-cell mobility operations.
  • the area information is used as one of the consideration nodes of the SeNB addition request, and the neighboring area of the eNB is not used as the consideration node for adding the request to the SeNB according to the neighboring area information that does not support the DC; when performing load balancing between the cells, according to the support
  • the neighboring area information of the DC uses the neighboring area of the eNB as the target cell for load balancing, and the neighboring area of the eNB is not used as the target cell for load balancing according to the neighboring area information that does not support the DC; when the service transmission between the cells is performed, according to the DC support
  • the neighboring area information requests resources from the neighboring area of the eNB to jointly transmit data, and does not request resources from the neighboring area of the eNB according to the neighboring area information that does
  • the obtaining module 71 is further configured to: write a neighbor relationship in the NRT and support DC The neighbor relationship attribute is reported to the OAM, so that the OAM is updated after the OAM is received.
  • the obtaining module, the processing module, and the writing module in the device for managing the neighbor relationship provided by the embodiment of the present invention may all be implemented by a processor in an evolved node (eNB); of course, the function performed by the processor may also pass specific logic.
  • the circuit is implemented; in a specific embodiment, the processor may be a central processing unit (CPU), a microprocessor (MPU), a digital signal processor (DSP), or a field programmable gate array (FPGA).
  • CPU central processing unit
  • MPU microprocessor
  • DSP digital signal processor
  • FPGA field programmable gate array
  • the method for managing the neighborhood relationship according to the embodiment of the present invention may also be stored in a computer readable storage medium if it is implemented in the form of a software function module and sold or used as a separate product. Based on such understanding, those skilled in the art will appreciate that embodiments of the present application can be provided as a method, system, or computer program product. Thus, the present application can take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment in combination of software and hardware.
  • the application can take the form of a computer program product embodied on one or more computer-usable storage media containing computer usable program code, including but not limited to a USB flash drive, a mobile hard drive, a read only memory (ROM, Read-Only Memory), disk storage, CD-ROM (Compact Disc Read-Only Memory), optical storage, and the like.
  • the computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the computer is readable and stored
  • the instructions in the reservoir produce an article of manufacture comprising an instruction device that implements the functions specified in one or more blocks of the flow or in a flow or block diagram of the flowchart.
  • an embodiment of the present invention further provides a computer storage medium, wherein a computer program is stored, and the computer program is used to execute a method for managing a neighbor relationship according to an embodiment of the present invention.
  • the eNB acquires whether the neighboring area information of the DC is supported, and performs inter-cell cooperation according to the neighboring area information; thus, the eNB can automatically and quickly self-manage the neighboring area relationship under the dual-connection system architecture. To reduce the burden on operators and unnecessary signaling between nodes.

Landscapes

  • Engineering & Computer Science (AREA)
  • Databases & Information Systems (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本发明公开了一种管理邻区关系的方法，演进节点B(eNB)获取是否支持双连接态（DC）的邻区信息，根据所述邻区信息进行小区间协作；本发明同时还公开了一种管理邻区关系的装置和存储介质。

Description

一种管理邻区关系的方法和装置、存储介质 技术领域
本发明涉及移动通信技术，尤其涉及一种管理邻区关系的方法和装置、存储介质。
背景技术
小小区的部署及能力方面的增强已经被第三代伙伴组织计划(3GPP，Third Generation Partnership Projects)确认为未来网络发展中最令人感兴趣的课题之一。目前，业界对在宏基站的覆盖范围内或边界处部署低功率节点、所述宏基站与低功率节点共同组成演进的通用陆地无线接入网(E-UTRAN，Evolved Universal Terrestrial Radio Access Network)系统架构中的接入网，从而为用户设备(UE，User Equipment)提供联合的数据传输服务的场景非常认同，并且已基本确定了这种系统架构。
在这种系统架构中，如图1所示，与核心网(CN，Core Network)中的移动性管理实体(MME，Mobility Management Entity)建有S1-MME接口、并被CN视作移动锚点的基站，称为主基站(MeNB，Master eNB)；与MeNB间以X2接口相连、为UE提供额外的无线资源的节点，称为次基站(SeNB，Secondary eNB)。在有性能需求且条件满足时，MeNB会为UE选择合适的SeNB并触发SeNB添加程序；该程序完成后，UE与MeNB、SeNB间均建有无线Uu口，也就是说，UE处于双连接(DC，Dual Connectivity)。这就意味着UE可以从两个eNB获取无线资源，其数据传输吞吐量能够得到极大的提升。
另一方面，在原有的单链接系统中，为了减轻运营商手动管理庞大的通讯系统内的各节点间的邻区关系，系统内可采用一种称为“自动邻区关 系(ANR，Automatic Neighbour Relation)”的功能进行管理。这项功能的主控在操作与管理(OAM，Operation and Management)节点，所述OAM节点为演进节点B(eNB)配置邻区关系(NR，Neighbour Relations)及相应的属性(attribute)，并可以对eNB上报的邻区关系进行同意/拒绝类的响应，所述属性是单向的，包括：NoRemove、NoHO和NoX2；eNB则可以通过与UE和相邻eNB间的通信及内部算法配置NR，添加或删除自身维护的邻区关系列表(NRT，Neighbour Relation Table)，并与OAM节点保持同步。
在DC系统架构下，如何减轻运营商管理复杂的通讯网络的负担，并避免MeNB对某些不能承担双连接传输的eNB发起SeNB添加程序，是亟需解决的技术问题。
发明内容
为解决现有存在的技术问题，本发明实施例提供一种管理邻区关系的方法和装置、存储介质，使得在双连接系统架构下，eNB可以对邻区关系进行自动、快速的自我管理，减轻运营商的负担及节点间不必要的信令。
本发明实施例的技术方案是这样实现的：
本发明实施例提供的一种管理邻区关系的方法，该方法包括：
eNB获取是否支持DC的邻区信息，根据所述邻区信息进行小区间协作。
优选地，所述eNB获取是否支持DC的邻区信息包括：eNB从空口获取是否支持DC的邻区信息。
优选地，所述eNB获取是否支持DC的邻区信息包括：eNB从X2/S1接口获取是否支持DC的邻区信息。
优选地，所述eNB获取是否支持DC的邻区信息包括：eNB从OAM节点获取是否支持DC的邻区信息。
优选地，所述eNB从空口获取是否支持DC的邻区信息包括：eNB从空口接收用户设备(UE)上报的邻区关系及其相应的属性，所述属性为邻区对eNB是否支持DC的邻区关系属性，所述是否支持DC的邻区关系属性为UE通过读取邻区的广播信息获取的。
优选地，所述eNB从X2/S1接口获取是否支持DC的邻区信息包括：eNB通过与其他eNB间进行X2控制面信令交互获取邻区关系及其相应的属性，所述属性为邻区对eNB是否支持DC的邻区关系属性；或者，eNB通过S1接口与核心网节点通信来获取所述信息邻区关系及其相应的属性，所述属性为邻区对eNB是否支持DC的邻区关系属性。
优选地，所述eNB从OAM获取不支持DC的邻区信息包括：eNB接收OAM发送的新的邻区关系及其相应的属性，所述属性为邻区对eNB是否支持DC的邻区关系属性。
优选地，所述eNB获取是否支持DC的邻区信息包括：eNB从空口或X2/S1口获取到邻区关系及邻区对eNB是否支持DC的邻区关系属性，上报所述邻区关系及其属性给OAM，并接收OAM的同意响应。
优选地，所述根据所述邻区信息进行小区间协作包括：根据是否支持DC的邻区信息进行小区间的移动性操作、或负荷均衡、或业务传输。
优选地，所述根据是否支持DC的邻区信息进行小区间的移动性操作包括：在进行小区间的移动性操作时，根据支持DC的邻区信息将eNB的邻区作为SeNB添加请求的考虑节点之一，根据不支持DC的邻区信息不将eNB的邻区作为SeNB添加请求的考虑节点。
优选地，所述根据是否支持DC的邻区信息进行小区间的负荷均衡包括：在进行小区间的负荷均衡时，根据支持DC的邻区信息将eNB的邻区作为负荷均衡的目标小区，根据不支持DC的邻区信息将eNB的邻区不作为负荷均衡的目标小区。
优选地，所述根据是否支持DC的邻区信息进行小区间的业务传输包括：在进行小区间的业务传输时，根据支持DC的邻区信息向eNB的邻区请求资源，以共同传输数据，根据不支持DC的邻区信息不向eNB的邻区请求资源。
优选地，该方法还包括：将获取的邻区关系及邻区对eNB是否支持DC的邻区关系属性写入邻区关系列表(NRT)。
优选地，该方法还包括：所述eNB将邻区关系及邻区对eNB是否支持DC的邻区关系属性写入自身配置的NRT后，将所述邻区关系及邻区对eNB是否支持DC的邻区关系属性上报给OAM，以使所述OAM接收后更新自身保存的NRT。
本发明实施例提供的一种管理邻区关系的装置，该装置包括：获取模块、处理模块；其中，
获取模块，配置为获取是否支持DC的邻区信息，将获取的所述邻区信息发送给处理模块；
处理模块，配置为根据所述邻区信息进行小区间协作。
优选地，所述获取模块，具体配置为从空口获取是否支持DC的邻区信息。
优选地，所述获取模块，具体配置为从X2/S1接口获取是否支持DC的邻区信息。
优选地，所述获取模块，具体配置为从OAM获取是否支持DC的邻区信息。
优选地，所述获取模块，具体配置为从空口接收UE上报的邻区关系及其相应的属性，所述属性为邻区对获取模块所属eNB是否支持DC的邻区关系属性，所述是否支持DC的邻区关系属性为UE通过读取邻区的广播信息获取的。
优选地，所述获取模块，具体配置为通过与除自身所属eNB以外的其他eNB间进行X2控制面信令交互获取邻区关系及其相应的属性，所述属性为邻区对获取模块所属eNB是否支持DC的邻区关系属性；或者，通过S1接口与核心网节点通信来获取所述信息邻区关系及其相应的属性，所述属性为邻区对获取模块所属eNB是否支持DC的邻区关系属性。
优选地，所述获取模块，具体配置为接收OAM发送的新的邻区关系及其相应的属性，所述属性为邻区对获取模块所属eNB是否支持DC的邻区关系属性。
优选地，所述获取模块，还配置为从空口或X2/S1口获取邻区关系及邻区对获取模块所属eNB是否支持DC的邻区关系属性，上报所述邻区关系及其属性给OAM，在收到OAM的同意响应后，将所述邻区关系及其属性发送给处理模块。
优选地，该装置还包括：写入模块，配置为将获取的邻区关系及所述是否支持DC的邻区关系属性写入NRT。
优选地，所述处理模块，具体配置为根据是否支持DC的邻区信息进行小区间的移动性操作、或负荷均衡、或业务传输。
优选地，所述处理模块，具体配置为在进行小区间的移动性操作时，根据支持DC的邻区信息将eNB的邻区作为SeNB添加请求的考虑节点之一，根据不支持DC的邻区信息不将eNB的邻区作为SeNB添加请求的考虑节点。
优选地，所述处理模块，具体配置为在进行小区间的负荷均衡时，根据支持DC的邻区信息将eNB的邻区作为负荷均衡的目标小区，根据不支持DC的邻区信息将eNB的邻区不作为负荷均衡的目标小区。
优选地，所述处理模块，具体配置为在进行小区间的业务传输时，根据支持DC的邻区信息向eNB的邻区请求资源，以共同传输数据，根据不 支持DC的邻区信息不向eNB的邻区请求资源。
优选地，所述获取模块，还配置为将NRT中写入的邻区关系及所述是否支持DC的邻区关系属性上报给OAM，以使所述OAM接收后更新自身保存的NRT。
第三方面，本发明实施例提供一种计算机存储介质，所述计算机存储介质中存储有计算机可执行指令，该计算机可执行指令用于执行本发明实施例第一方面提供的管理邻区关系的方法。
本发明实施例提供了一种管理邻区关系的方法和装置、存储介质，其中，eNB获取是否支持DC的邻区信息，根据所述邻区信息进行小区间协作；如此，使得在双连接系统架构下，eNB可以对邻区关系进行自动、快速的自我管理，减轻运营商的负担及节点间不必要的信令。
附图说明
图1为现有技术中异构网络的部署示意图；
图2为本发明实施例提供的管理邻区关系的方法流程示意图；
图3为本发明实施例一的流程示意图；
图4为本发明实施例二的流程示意图；
图5为本发明实施例三的流程示意图；
图6a为本发明实施例三中消息1包含的小区关系示意图；
图6b为本发明实施例三中消息2包含的小区关系示意图；
图7为本发明实施例提供的管理邻区关系的装置结构示意图。
具体实施方式
本发明实施例中，eNB获取是否支持DC的邻区信息，根据所述邻区信息进行小区间协作，这样，在双链接系统架构下，eNB可以及时、准确的获取不能用于DC用途的邻区关系，对于全网的分流业务部署、吞吐量提 升、信令减少都有极大的益处。
下面通过附图及具体实施例对本发明的技术方案做进一步的详细说明。
本发明实施例实现一种管理邻区关系的方法，如图2所示，该方法主要包括以下几个步骤：
步骤201：eNB获取是否支持DC的邻区信息；
本步骤中，是否支持DC的邻区信息可以是是否能做DC的能力标识信息，也可以是新定义一个邻区关系属性，由所述邻区关系属性指示是否支持DC，例如：定义新的邻区关系属性，所述邻区关系属性缺省表示邻区对eNB支持DC，所述邻区关系属性为NoDC表示邻区对eNB不支持DC；这样，如果eNB检测到邻区关系属性是NoDC，那么eNB不能将所述邻区关系用于DC用途。需要说明的是，NoDC仅为本实施例所举例的名称，实际属性与本实施例所述定义相同的属性均属于本发明所保护的范围。
本步骤eNB获取是否支持DC的邻区信息的方式包括但不限于以下三种：
1)eNB从空口获取是否支持DC的邻区信息，具体的，eNB从空口接收UE上报的邻区关系及其相应的属性，所述属性为邻区对eNB是否支持DC的邻区关系属性；这里，所述邻区对eNB是否支持DC的邻区关系属性为UE通过读取邻区的广播信息获取的。
2)eNB从X2/S1接口获取是否支持DC的邻区信息，具体的，eNB通过与其他eNB间进行X2控制面信令交互获取邻区关系及其相应的属性，所述属性为邻区对eNB是否支持DC的邻区关系属性；其中，所述X2控制面信令可以是现有的X2-CP程序，如X2建立程序(X2 Setup)、eNB配置更新程序(eNB Configuration Update)；还可以是新的X2控制面程序。另外，eNB也可以通过S1接口与核心网节点通信来获取所述信息邻区关系 及其相应的属性，所述属性为邻区对eNB是否支持DC的邻区关系属性。
3)eNB从OAM获取是否支持DC的邻区信息，具体的，eNB接收OAM发送的新的邻区关系及其相应的属性，所述属性为邻区对eNB是否支持DC的邻区关系属性。
对于第1)、2)种方式来说，eNB也可以只从空口或X2接口获取到邻区关系，而所述邻区对eNB是否支持DC的邻区关系属性由eNB通过与OAM间的交互来获取。
本步骤还可以包括：eNB从空口或X2/S1口获取到邻区关系及邻区对eNB是否支持DC的邻区关系属性后，先上报所述邻区关系及其属性给OAM，在收到OAM的同意响应后，将所述邻区关系及其属性写入NRT；
eNB从OAM获取邻区关系及邻区对eNB是否支持DC的邻区关系属性后，将所述邻区关系及其属性写入NRT。
步骤202：eNB根据所述邻区信息进行小区间协作；
具体地，eNB根据是否支持DC的邻区信息进行小区间的移动性操作、或负荷均衡、或业务传输等处理，例如：
eNB有业务、性能方面的需求，如负荷过重，需要将UE的大数据量业务进行分流，如果通过UE的测量上报而获知探测小区(即eNB的邻区)的无线信号质量较高，而且所述探测小区对eNB的邻区关系属性是支持DC，那么所述eNB将所述探测小区作为SeNB添加请求的考虑节点之一；如果所述探测小区对eNB的邻区关系属性是不支持DC，那么所述eNB不将所述探测小区作为SeNB添加请求的考虑节点；
再如，eNB在做负荷均衡时，如果探测小区对eNB的邻区关系属性是支持DC，那么所述eNB在做负荷均衡的相关决定时将所述探测小区作为目标小区进行考虑；如果探测小区对eNB的邻区关系属性是不支持DC，那么可以认为所述探测小区不具备额外的潜在负荷承载能力，所述eNB在 做负荷均衡的相关决定时不将所述探测小区包含在目标小区的考虑范围内。
又如，eNB在做业务传输时，自身的资源不足够提供业务所要求的传输速度，此时如果探测小区对eNB的邻区关系属性是支持DC，那么所述eNB向探测小区请求资源，以共同传输数据；如果探测小区对eNB的邻区关系属性是不支持DC，那么所述eNB不向探测小区请求资源。
通过本实施例的方法，在双链接系统架构下，eNB可以及时、准确的获取邻区关系，这对于全网的分流业务部署、吞吐量提升、信令减少都有极大的益处。
下面结合实施例来详细说明本发明的具体应用。
实施例一
在异构网络中，服务eNB配置UE进行信号测量、并读取、上报探测小区所广播的邻区关系属性；所述eNB在与OAM交互信息后更新NRT，本实施例假定探测小区与服务小区隶属于不同的基站，且探测小区是小小区。具体步骤如图3所示：
eNB1是UE当前的服务基站，所述eNB1通过控制面信令，如上报邻区请求(Report Neighbour Request)(步骤301)，指示UE测量目标频点上的小区，eNB1接收所述UE通过上报邻区响应(Report Neighbour Response)上报的在所述目标频点上探测到的小区的物理小区标识(PCI，Physical Cell Identifier)(步骤302)，所述探测到的小区为eNB2；
所述eNB1通过上报全球小区标识请求(Report Global-CID Request)消息指示所述UE以所述PCI为参数读取所述eNB2的系统广播(步骤303)，所述系统广播包括：小区全球唯一标识(ECGI，E-UTRAN Cell Global Identifier)、公共陆地移动网络(PLMN，Public Land Mobile Network)等参数，也包括所述eNB2对eNB1是否支持DC的邻区关系属性，这里，所述 邻区关系属性为eNB2对eNB1不支持DC，所述eNB2的邻区关系属性可以由OAM配置；
所述UE读取系统广播(Read BCCH)(步骤304)，将获取到的信息通过上报全球小区标识(Report Global-CID)消息上报给所述eNB1(步骤305)；
所述eNB1对接收到所述eNB2对eNB1不支持DC的邻区关系属性予以保存，根据所述不支持DC的邻区关系属性进行移动性操作、负荷均衡、业务传输等处理，例如：
如果所述eNB1有业务、性能方面的需求，如负荷过重，需要将UE的大数据量业务进行分流，那么虽然通过UE的测量上报而获知所述eNB2的无线信号质量较高，但因为所述eNB2对eNB1的邻区关系属性是不支持DC，因此所述eNB1不会向所述eNB2发送SeNB添加请求消息；
所述eNB1在做负荷均衡的考虑时，因为所述eNB2对eNB1的邻区关系属性是不支持DC，因此可以认为所述eNB2不具备额外的潜在负荷承载能力，所述eNB1在做负荷均衡的相关决定时不将所述eNB2包含在目标小区的考虑范围内。
以下实施例中接收到不支持DC的邻区关系属性的eNB对所述邻区关系属性的用法与实施例一所述相同，不再累述。
本实施例中，所述eNB1将所述邻区关系及其属性与OAM间的同步更新方式可以是(其余实施例以其中一种举例)：
所述eNB1将邻区关系及eNB2对eNB1不支持DC的邻区关系属性通过邻区关系报告(Neighbour Relation Report)上报给OAM(步骤306)，并随后接收到所述OAM的同意响应，如添加/更新邻区关系消息(Add/Update Neighbour Relation)(步骤307)，所述eNB1将所述邻区关系及eNB2对eNB1不支持DC的邻区关系属性写入自身配置的NRT；
或者，所述eNB1将邻区关系及其eNB2对eNB1不支持DC的邻区关 系属性写入自身配置的NRT(步骤308)，并将所述邻区关系及eNB2对eNB1不支持DC的邻区关系属性上报给所述OAM，所述OAM接收后更新自身保存的NRT。
实施例二
在异构网络中，宏基站与低功率节点间通过X2控制面程序建立X2接口，在X2控制面信令交互过程中，信令发送节点可为信令接收节点提供自身配置的服务小区及邻区的信息，包括各小区是否支持DC的邻区关系属性。具体步骤如图4所示：
eNB1通过向eNB2发送X2建立请求(X2 SETUP REQUEST)消息来触发X2建立(Setup)程序(步骤401)，所述eNB2回复X2建立响应(X2SETUP RESPONSE)消息以完成所述X2 Setup程序(步骤402)，其中两条X2控制面信令中都携带节点自身配置的服务小区信息(Served Cell Information)，还可以携带邻区信息(NI，Neighbour Information)信元，所述NI中包括与所述服务小区直接相邻的E-UTRAN小区的ECGI、PCI等信息，所述两条X2控制面信令中还携带各小区是否支持DC的邻区关系属性；
本实施例中，所述两条X2控制面信令还可以包含支持DC的邻区列表，例如：可以为服务小区和/或邻区提供双连接服务的目标小区列表；此外，所述NI信元还可以包括所述邻区支持的PLMN列表；
所述eNB1或eNB2将对端节点指示的邻区关系及是否支持DC的邻区关系属性通过邻区关系报告(Neighbour Relation Report)上报给OAM(步骤403)，并随后接收到所述OAM的同意响应，如添加/更新邻区关系消息(Add/Update Neighbour Relation)(步骤404)，所述eNB1或eNB2将所述邻区关系及所述是否支持DC的邻区关系属性写入自身配置的NRT(步骤405)；
如果所述eNB1或eNB2业务负荷过重且获知对端节点小区(包括服务 小区或其邻区)的无线信号质量较高，那么所述eNB1或eNB2根据自身的NRT中所述小区是否支持DC的邻区关系属性，决定是否向所述对端节点小区发送SeNB添加请求消息，以尝试为UE提供DC服务。
需要说明的是，本实施例以X2 Setup程序举例，但所述步骤及原理同样适用于其他现有X2/S1控制面流程，如eNB配置更新(eNB Configuration Update)程序。
实施例三
如背景介绍中所述，邻区关系的属性是单向的，即是源小区(source cell)到目标小区(target cell)的属性，因此可以采取一个X2控制面程序，由发送节点向对端节点请求邻区关系及其属性，对端节点予以回复。所述发送节点可以在与OAM交互信息后更新邻区关系列表。具体步骤如图5所示：
eNB1向eNB2发送X2控制面消息1(图5中以邻区关系请求(Neighbour Relation Request)示例)(步骤501)，所述消息1至少包含所述eNB1配置的各个小区信息，如Cell1、Cell2，同时假定所述eNB2配置的小区有Cell3、Cell4，所述消息1还可以包含所述eNB1当前检测到的相邻所述eNB2的小区信息，如图6(a)所示，所述Cell1的邻区是所述Cell3、Cell4，所述Cell2的邻区是所述Cell4；
所述eNB2向eNB1回复响应消息2(图5中以邻区关系响应(Neighbour Relation Response)示例)(步骤502)，所述消息2中包括所述eNB2的小区的邻区关系及邻区关系属性，如图6(b)所示，Cell3的邻区关系属性为支持与Cell1进行DC，Cell4的邻区关系属性为支持与Cell2进行DC，但Cell4不支持与Cell1进行DC。
需要说明的是，如果所述消息1中只包含了所述eNB1配置的各个小区的信息，而没有包含相邻小区列表，那么所述eNB2可以在所述消息2中包含所有配置小区与所述eNB1小区的邻区关系属性。
另一方面，所述程序的具体实现可以多样的，如消息1中包含当前已配置的邻区关系及其属性，eNB2收到后对消息1所含内容进行验证，并将更新的内容携带在消息2中(步骤504)；或者，所述消息2中携带的是所述eNB2各配置小区所支持的、可以提供双连接服务的目标小区列表，并且，所述消息2还可以包括eNB2各配置小区支持的PLMN信息。
所述eNB1将所述消息2中指示的邻区关系及邻区关系属性上报给OAM(步骤503)，并随后接收到所述OAM的同意响应，所述eNB1将所述邻区关系及所述邻区关系属性写入自身配置的NRT(步骤505)，这里，写入NRT的邻区关系属性为不支持DC的Cell4与Cell1的邻区关系属性。
本发明实施例还提供一种管理邻区关系的装置，该装置一般可以设置在eNB中，如图7所示，该装置包括：获取模块71、处理模块72；其中，
获取模块71，配置为获取是否支持DC的邻区信息，将获取的所述邻区信息发送给处理模块72；处理模块72，配置为根据所述邻区信息进行小区间协作。
所述获取模块71可以是eNB的协议接口，所述处理模块72可以是eNB的处理器。
所述获取模块71，配置为从空口获取是否支持DC的邻区信息，具体地，所述获取模块71，配置为从空口接收UE上报的邻区关系及其相应的属性，所述属性为邻区对获取模块71所属eNB是否支持DC的邻区关系属性，所述是否支持DC的邻区关系属性为UE通过读取邻区的广播信息获取的；
或者，所述获取模块71，配置为从X2/S1接口获取是否支持DC的邻区信息，具体地，所述获取模块71，配置为通过与除自身所属eNB以外的其他eNB间进行X2控制面信令交互获取邻区关系及其相应的属性，所述属性为邻区对获取模块71所属eNB是否支持DC的邻区关系属性；其中， 所述X2控制面信令可以是现有的X2-CP程序，如X2 Setup、eNB Configuration Update；还可以是新的X2控制面程序。另外，所述获取模块71也可以通过S1接口与核心网节点通信来获取所述信息邻区关系及其相应的属性，所述属性为邻区对获取模块71所属eNB是否支持DC的邻区关系属性；
或者，所述获取模块71，配置为从OAM获取是否支持DC的邻区信息，具体的，所述获取模块71，配置为接收OAM发送的新的邻区关系及其相应的属性，所述属性为邻区对获取模块71所属eNB是否支持DC的邻区关系属性。
所述获取模块71，还配置为从空口或X2/S1口获取到邻区关系及邻区对获取模块71所属eNB是否支持DC的邻区关系属性后，先上报所述邻区关系及其属性给OAM，在收到OAM的同意响应后，将所述邻区关系及其属性发送给处理模块72。
该装置还包括写入模块73，配置为将获取的邻区关系及是否支持DC的邻区关系属性写入NRT。
所述处理模块72，具体配置为根据是否支持DC的邻区信息进行小区间的移动性操作、或负荷均衡、或业务传输，其中，在进行小区间的移动性操作时，根据支持DC的邻区信息将eNB的邻区作为SeNB添加请求的考虑节点之一，根据不支持DC的邻区信息不将eNB的邻区作为SeNB添加请求的考虑节点；在进行小区间的负荷均衡时，根据支持DC的邻区信息将eNB的邻区作为负荷均衡的目标小区，根据不支持DC的邻区信息将eNB的邻区不作为负荷均衡的目标小区；在进行小区间的业务传输时，根据支持DC的邻区信息向eNB的邻区请求资源，以共同传输数据，根据不支持DC的邻区信息不向eNB的邻区请求资源。
所述获取模块71，还配置为将NRT中写入的邻区关系及是否支持DC 的邻区关系属性上报给OAM，以使所述OAM接收后更新自身保存的NRT。
本发明实施例提供的管理邻区关系的装置中的获取模块、处理模块和写入模块都可以通过演进节点(eNB)中的处理器来实现；当然处理器执行的功能也可通过具体的逻辑电路实现；在具体实施例的过程中，处理器可以为中央处理器(CPU)、微处理器(MPU)、数字信号处理器(DSP)或现场可编程门阵列(FPGA)等。
本发明实施例所述管理邻区关系的方法如果以软件功能模块的形式实现并作为独立的产品销售或使用时，也可以存储在一个计算机可读取存储介质中。基于这样的理解，本领域内的技术人员应明白，本申请的实施例可提供为方法、系统、或计算机程序产品。因此，本申请可采用完全硬件实施例、完全软件实施例、或结合软件和硬件方面的实施例的形式。而且，本申请可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质上实施的计算机程序产品的形式，所述存储介质包括但不限于U盘、移动硬盘、只读存储器(ROM，Read-Only Memory)、磁盘存储器、只读光盘(CD-ROM，Compact Disc Read-Only Memory)、光学存储器等。
本申请是根据本申请实施例的方法、设备(系统)、和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器，使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中，使得存储在该计算机可读存 储器中的指令产生包括指令装置的制造品，该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
相应地，本发明实施例还提供一种计算机存储介质，其中存储有计算机程序，该计算机程序用于执行本发明实施例的管理邻区关系的方法。
以上所述，仅为本发明的较佳实施例而已，并非用于限定本发明的保护范围，凡在本发明的精神和原则之内所作的任何修改、等同替换和改进等，均应包含在本发明的保护范围之内。
工业实用性
本发明实施例中，eNB获取是否支持DC的邻区信息，根据所述邻区信息进行小区间协作；如此，使得在双连接系统架构下，eNB可以对邻区关系进行自动、快速的自我管理，减轻运营商的负担及节点间不必要的信令。

Claims (29)

  1. 一种管理邻区关系的方法，该方法包括：
    演进节点eNB获取是否支持双连接DC的邻区信息，根据所述邻区信息进行小区间协作。
  2. 根据权利要求1所述的方法，其中，所述eNB获取是否支持DC的邻区信息包括：eNB从空口获取是否支持DC的邻区信息。
  3. 根据权利要求1所述的方法，其中，所述eNB获取是否支持DC的邻区信息包括：eNB从X2/S1接口获取是否支持DC的邻区信息。
  4. 根据权利要求1所述的方法，其中，所述eNB获取是否支持DC的邻区信息包括：eNB从操作与管理(OAM)节点获取是否支持DC的邻区信息。
  5. 根据权利要求2所述的方法，其中，所述eNB从空口获取是否支持DC的邻区信息包括：eNB从空口接收用户设备(UE)上报的邻区关系及其相应的属性，所述属性为邻区对eNB是否支持DC的邻区关系属性，所述是否支持DC的邻区关系属性为UE通过读取邻区的广播信息获取的。
  6. 根据权利要求3所述的方法，其中，所述eNB从X2/S1接口获取是否支持DC的邻区信息包括：eNB通过与其他eNB间进行X2控制面信令交互获取邻区关系及其相应的属性，所述属性为邻区对eNB是否支持DC的邻区关系属性；或者，eNB通过S1接口与核心网节点通信来获取所述信息邻区关系及其相应的属性，所述属性为邻区对eNB是否支持DC的邻区关系属性。
  7. 根据权利要求4所述的方法，其中，所述eNB从OAM获取不支持DC的邻区信息包括：eNB接收OAM发送的新的邻区关系及其相应的属性，所述属性为邻区对eNB是否支持DC的邻区关系属性。
  8. 根据权利要求1所述的方法，其中，所述eNB获取是否支持DC的邻区信息包括：eNB从空口或X2/S1口获取到邻区关系及邻区对eNB是否支持DC的邻区关系属性，上报所述邻区关系及其属性给OAM，并接收OAM的同意响应。
  9. 根据权利要求1所述的方法，其中，所述根据所述邻区信息进行小区间协作包括：根据是否支持DC的邻区信息进行小区间的移动性操作、或负荷均衡、或业务传输。
  10. 根据权利要求9所述的方法，其中，所述根据是否支持DC的邻区信息进行小区间的移动性操作包括：在进行小区间的移动性操作时，根据支持DC的邻区信息将eNB的邻区作为SeNB添加请求的考虑节点之一，根据不支持DC的邻区信息不将eNB的邻区作为SeNB添加请求的考虑节点。
  11. 根据权利要求9所述的方法，其中，所述根据是否支持DC的邻区信息进行小区间的负荷均衡包括：在进行小区间的负荷均衡时，根据支持DC的邻区信息将eNB的邻区作为负荷均衡的目标小区，根据不支持DC的邻区信息将eNB的邻区不作为负荷均衡的目标小区。
  12. 根据权利要求9所述的方法，其中，所述根据是否支持DC的邻区信息进行小区间的业务传输包括：在进行小区间的业务传输时，根据支持DC的邻区信息向eNB的邻区请求资源，以共同传输数据，根据不支持DC的邻区信息不向eNB的邻区请求资源。
  13. 根据权利要求5至7任一项所述的方法，其中，该方法还包括：将获取的邻区关系及邻区对eNB是否支持DC的邻区关系属性写入邻区关系列表(NRT)。
  14. 根据权利要求13所述的方法，其中，该方法还包括：所述eNB将邻区关系及邻区对eNB是否支持DC的邻区关系属性写入自身配置的 NRT后，将所述邻区关系及邻区对eNB是否支持DC的邻区关系属性上报给OAM，以使所述OAM接收后更新自身保存的NRT。
  15. 一种管理邻区关系的装置，该装置包括：获取模块、处理模块；其中，
    获取模块，配置为获取是否支持DC的邻区信息，将获取的所述邻区信息发送给处理模块；
    处理模块，配置为根据所述邻区信息进行小区间协作。
  16. 根据权利要求15所述的装置，其中，所述获取模块，配置为从空口获取是否支持DC的邻区信息。
  17. 根据权利要求15所述的装置，其中，所述获取模块，配置为从X2/S1接口获取是否支持DC的邻区信息。
  18. 根据权利要求15所述的装置，其中，所述获取模块，配置为从OAM获取是否支持DC的邻区信息。
  19. 根据权利要求16所述的装置，其中，所述获取模块，配置为从空口接收UE上报的邻区关系及其相应的属性，所述属性为邻区对获取模块所属eNB是否支持DC的邻区关系属性，所述是否支持DC的邻区关系属性为UE通过读取邻区的广播信息获取的。
  20. 根据权利要求17所述的装置，其中，所述获取模块，配置为通过与除自身所属eNB以外的其他eNB间进行X2控制面信令交互获取邻区关系及其相应的属性，所述属性为邻区对获取模块所属eNB是否支持DC的邻区关系属性；或者，通过S1接口与核心网节点通信来获取所述信息邻区关系及其相应的属性，所述属性为邻区对获取模块所属eNB是否支持DC的邻区关系属性。
  21. 根据权利要求18所述的装置，其中，所述获取模块，配置为接收OAM发送的新的邻区关系及其相应的属性，所述属性为邻区对获取模 块所属eNB是否支持DC的邻区关系属性。
  22. 根据权利要求15所述的装置，其中，所述获取模块，还配置为从空口或X2/S1口获取邻区关系及邻区对获取模块所属eNB是否支持DC的邻区关系属性，上报所述邻区关系及其属性给OAM，在收到OAM的同意响应后，将所述邻区关系及其属性发送给处理模块。
  23. 根据权利要求19至21任一项所述的装置，其中，该装置还包括：写入模块，配置为将获取的邻区关系及所述是否支持DC的邻区关系属性写入NRT。
  24. 根据权利要求15所述的装置，其中，所述处理模块，配置为根据是否支持DC的邻区信息进行小区间的移动性操作、或负荷均衡、或业务传输。
  25. 根据权利要求24所述的装置，其中，所述处理模块，配置为在进行小区间的移动性操作时，根据支持DC的邻区信息将eNB的邻区作为SeNB添加请求的考虑节点之一，根据不支持DC的邻区信息不将eNB的邻区作为SeNB添加请求的考虑节点。
  26. 根据权利要求24所述的装置，其中，所述处理模块，配置为在进行小区间的负荷均衡时，根据支持DC的邻区信息将eNB的邻区作为负荷均衡的目标小区，根据不支持DC的邻区信息将eNB的邻区不作为负荷均衡的目标小区。
  27. 根据权利要求24所述的装置，其中，所述处理模块，配置为在进行小区间的业务传输时，根据支持DC的邻区信息向eNB的邻区请求资源，以共同传输数据，根据不支持DC的邻区信息不向eNB的邻区请求资源。
  28. 根据权利要求23所述的装置，其中，所述获取模块，还配置为将NRT中写入的邻区关系及所述是否支持DC的邻区关系属性上报给 OAM，以使所述OAM接收后更新自身保存的NRT。
  29. 一种计算机存储介质，所述计算机存储介质中存储有计算机可执行指令，该计算机可执行指令用于执行权利要求1至14任一项所述管理邻区关系的方法。
PCT/CN2014/086848 2014-06-13 2014-09-18 一种管理邻区关系的方法和装置、存储介质 WO2015188494A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201410265950.7 2014-06-13
CN201410265950.7A CN105307149A (zh) 2014-06-13 2014-06-13 一种管理邻区关系的方法和装置

Publications (1)

Publication Number Publication Date
WO2015188494A1 true WO2015188494A1 (zh) 2015-12-17

Family

ID=54832798

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2014/086848 WO2015188494A1 (zh) 2014-06-13 2014-09-18 一种管理邻区关系的方法和装置、存储介质

Country Status (2)

Country Link
CN (1) CN105307149A (zh)
WO (1) WO2015188494A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP4120721A4 (en) * 2020-04-03 2023-09-06 Huawei Technologies Co., Ltd. COMMUNICATION METHOD, APPARATUS AND SYSTEM

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR102155171B1 (ko) * 2016-03-11 2020-09-11 후아웨이 테크놀러지 컴퍼니 리미티드 마이크로 기지국 기반 연결 동작 방법 및 단말기, 및 기지국
WO2019051671A1 (zh) 2017-09-13 2019-03-21 Oppo广东移动通信有限公司 配置anr的方法、终端设备、基站和核心网设备
AU2018403647A1 (en) * 2018-01-19 2020-07-30 Guangdong Oppo Mobile Telecommunications Corp., Ltd. Method for configuring neighbouring cell, network device and user equipment
CN110351892B (zh) * 2018-04-04 2021-10-29 维沃移动通信有限公司 一种通知方法及相关设备
CN114500271B (zh) * 2018-09-30 2024-04-30 中国电信股份有限公司 基站间通信方法、基站和通信系统

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102870450A (zh) * 2011-05-03 2013-01-09 联发科技股份有限公司 次服务小区无线电链路监测和无线电链路失败处理
CN103188663A (zh) * 2011-12-27 2013-07-03 华为技术有限公司 基站间载波聚合的安全通讯方法及设备
CN103731883A (zh) * 2014-01-20 2014-04-16 中国联合网络通信集团有限公司 一种负载均衡的方法及装置
WO2014056130A1 (en) * 2012-10-08 2014-04-17 Broadcom Corporation Method and apparatus for managing dual connection establishment
WO2014079017A1 (en) * 2012-11-22 2014-05-30 Broadcom Corporation Methods and apparatuses for discontinuous reception

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7873710B2 (en) * 2007-02-06 2011-01-18 5O9, Inc. Contextual data communication platform
CN101626601A (zh) * 2008-07-08 2010-01-13 中兴通讯股份有限公司 小区能力信息指示方法、基站、无线网络控制器
CN101478775B (zh) * 2009-01-20 2011-02-23 中兴通讯股份有限公司 一种多邻居连接状态的检测方法、系统和设备
CN102651879B (zh) * 2011-02-28 2017-02-08 中兴通讯股份有限公司 基于ue智能关联选取协作小区方法及协作用户设备
KR102040883B1 (ko) * 2012-08-23 2019-11-05 인터디지탈 패튼 홀딩스, 인크 무선 시스템에서의 다중 스케줄러들을 이용한 동작

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102870450A (zh) * 2011-05-03 2013-01-09 联发科技股份有限公司 次服务小区无线电链路监测和无线电链路失败处理
CN103188663A (zh) * 2011-12-27 2013-07-03 华为技术有限公司 基站间载波聚合的安全通讯方法及设备
WO2014056130A1 (en) * 2012-10-08 2014-04-17 Broadcom Corporation Method and apparatus for managing dual connection establishment
WO2014079017A1 (en) * 2012-11-22 2014-05-30 Broadcom Corporation Methods and apparatuses for discontinuous reception
CN103731883A (zh) * 2014-01-20 2014-04-16 中国联合网络通信集团有限公司 一种负载均衡的方法及装置

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP4120721A4 (en) * 2020-04-03 2023-09-06 Huawei Technologies Co., Ltd. COMMUNICATION METHOD, APPARATUS AND SYSTEM

Also Published As

Publication number Publication date
CN105307149A (zh) 2016-02-03

Similar Documents

Publication Publication Date Title
US10154535B2 (en) Method and apparatus for transmitting a handover report and an RLF report
WO2015188494A1 (zh) 一种管理邻区关系的方法和装置、存储介质
JP2019050617A (ja) 無線通信システムと方法と無線基地局と制御局
EP2427029A1 (en) Method for acquiring adjacent enb information and mobile management entity
JP5459690B2 (ja) 異周波数測定設定発信方法及び装置
CN105636111A (zh) 发现无线网络问题的方法、装置及系统
WO2017084005A1 (zh) 一种小区测量报告的方法及用户设备
WO2017012299A1 (zh) 一种网络共享中重建立小区的选择方法及装置
JP6467543B2 (ja) 通信システム、ユーザ端末、プロセッサ及び通信制御方法
WO2013189310A1 (zh) 认知无线电系统、基站及邻区关系的控制方法
CN105432116A (zh) 小区切换的方法、基站及系统
EP3123778B1 (en) System and method for identifying a handover target cell during cell reconfiguration periods
US20170366985A1 (en) Measuring Neighboring Cells By User Equipment Served By Master Radio Access Node and Secondary Radio Access Node
WO2015143914A1 (zh) 一种移动终端通信控制方法、设备和系统
WO2010078676A1 (zh) 获取目标基站传输地址的方法及建立x2接口连接的方法
US10383009B2 (en) Handover of a terminal in dual connectivity mode
WO2012092887A2 (zh) 受限网络小区的测量方法、用户设备和基站
WO2016184184A1 (zh) 获取邻区频段信息及移动性管理的方法和装置、存储介质
WO2017000165A1 (zh) 一种邻区确定方法及设备
WO2016070392A1 (zh) 无线资源管理方法、管理装置、监测方法和监测装置
WO2012088875A1 (zh) 邻区列表自动维护方法及系统
CN102238572B (zh) 一种添加邻接小区的方法、装置及系统
WO2012151835A1 (zh) 一种邻区切换、上报测量信息的方法及设备

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 14894625

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 14894625

Country of ref document: EP

Kind code of ref document: A1