Method, device and system for selecting self-organizing network function

The present invention provides a method, a device, and a system for selecting a self-organizing network (SON) function. The method comprises: an SON function selecting entity receives SON capability information of an SON functional entity, the SON capability information of the SON functional entity comprising: an SON capability supported by the SON functional entity and an activated state of the SON capability supported by the SON functional entity; the SON function selecting entity acquires an SON function selecting policy; the SON function selecting entity performs SON function selection according to the SON capability information of the SON functional entity and the SON function selecting policy. The technical solutions provided by the present invention are applicable to the field of communications, and solve the problem in the prior art that during the operation of SON function coordination, execution conflicts occur among functional instances.

TECHNICAL FIELD

The present invention relates to the technical field of communications, and in particular to a method, a device and a system for selecting a self-organizing network function.

BACKGROUND

Self Organizing Network (Self Organizing Network, SON) is a key topic research of standardization carried out by the 3rd Generation Partnership Project (3rd Generation Partnership Project, 3GPP) standard organization during the R8/9/10 working period, and the core concept thereof is to reduce conventional manual operations and reduce the operation and maintenance cost of network operators through automation processes at the stages of network planning, deployment, optimization and maintenance.

The SON itself integrates multiple automatic functions, including a Self Configuration (Self Configuration), an Automatic Neighboring Relation (Automatic Neighboring Relation, ANR), a Mobility Robustness Optimization (Mobility Robustness Optimization, MRO), a Mobility Load Balancing (Mobility Load Balancing), a Coverage and Capacity Optimization (Coverage and Capacity Optimization, CCO), a Cell Outage Detection and Compensation (Cell Outage Detection and Compensation, CODC), a cell Energy Saving (Energy Saving, ES). In practice, multiple SON functions rather than one SON function cooperate with each other to achieve one purpose, for addressing a network problem (e.g., debugging) or optimizing the network. This may cause an issue of how to coordinate the cooperating SON functions, i.e., how to avoid the different SON functions from performing conflict operations, setting conflict parameters or generating contradictory targets on one network entity (e.g., a base station, a cell).

There are some methods to coordinate SON functions in the conventional technology. The methods include: a conflict avoidance method (a prior SON function coordination, i.e., determining a possible executing conflict and optimizing an executing sequence of multiple SON functions before executing the SON functions, to avoid such a conflict before execution) and a conflict resolution method (a posterior SON function coordination, i.e., addressing by setting a task priority a conflict that occurs in executing the multiple SON functions). In the process of coordinating SON functions, each entity supporting SON functions (e.g., a base station, or an operation and maintenance system, i.e., a network management system) only knows about its own SON function configuration but knows nothing about SON function configurations of surrounding entities. In this case, an executing conflict occurs between a SON function of an entity and SON functions of surrounding entities if the SON function of the entity is configured as the same as those of the surrounding entities or the SON function of the entity is configured as different from those of the surrounding entities but a conflict relation is preset between the SON functions of the entity and its surrounding entities.

SUMMARY

In summary, in the conventional technology, a function entity participating in an SON coordination can not learn SON capability information of its surrounding SON function entities or SON capability information of the SON function entities distributed in its management domain (in a case that the entity for coordinating SON functions is the network management system). The lack of SON capability information may result in an executing conflict between the SON functions of different entities participating in the SON function coordination in the level of use case, which does not involves the specific optimization, configuration parameters and optimization objects in the use case, thereby affecting the cooperation of the SON functions.

It is to provide a method, a device and a system for selecting a self-organizing network SON function, to solve the problem existing in the conventional technology that an entity supporting an SON function can not learn SON capability information of surrounding entities.

In one aspect, a method for selecting a self-organizing network SON function is provided according to an embodiment of the invention, including: receiving, by an SON function selecting entity, SON capability information of an SON function entity, where the SON capability information of the SON function entity includes an SON capability supported by the SON function entity and an activation state of the SON capability supported by the SON function entity; acquiring, by the SON function selecting entity, an SON function selection policy; and selecting, by the SON function selecting entity, an SON function based on the SON capability information of the SON function entity and the SON function selection policy.

In another aspect, a self-organizing network SON function selection entity is further provided according to an embodiment of the invention, including: a receiving unit, configured to receive SON capability information of an SON function entity sent by the SON function entity, where the SON capability information of the SON function entity includes an SON capability supported by the SON function entity and an activation state of the SON capability supported by the SON function entity; an acquisition unit, configured to acquire an SON function selection policy; and a selecting unit, configured to select an SON function based on the SON capability information of the SON function entity received by the receiving unit and the SON function selection policy acquired by the acquisition unit.

In another aspect, a self-organizing network SON function selection system is further provided according to an embodiment of the invention, including the SON function selection entity and at least one SON function entity.

By the foregoing technical solutions, the SON function selection entity receives SON capability information of an SON function entity, acquires an SON function selection policy, and selects an SON function based on the SON capability information and the SON function selection policy. In this way, the SON function selection entity can learn the SON capability information of the SON function entity, which facilitates the cooperation between the SON function selection entity and the SON function, thereby addressing the executing conflict among functional use cases in cooperation of the SON functions in the conventional technology.

DESCRIPTION OF EMBODIMENTS

The disclosure may be specified hereinafter in conjunction with drawings and embodiments, to make the object, technical solutions and advantages of the disclosure to be better understood. It may be understood that, the embodiments are only to illustrate the disclosure rather than to limit the disclosure.

FIG. 1is a flow chart of a method for selecting an SON capability according to an embodiment of the invention. The method includes S101to S103.

In S101, an SON function selection entity receives SON capability information of an SON function entity. The SON capability information of the SON function entity includes an SON capability supported by the SON function entity and an activation state of the SON capability supported by the SON function entity.

In the embodiment of the invention, the SON capability includes a centralized (centralized) SON function and/or a distributed (distributed) SON function. The centralized SON function includes a Network Management-centralized (Network Management-centralized, NM-centralized) SON function and/or an Element Management-centralized (Element Management-centralized, EM-centralized) SON function. In an implementation, the operator may determine an executing scheme of SON functions of SON function entities based on an overall target of SON functions, a network planning and historical operation data i.e., make a choice between the centralized SON function and the distributed SON function, and record an SON function selection policy into an Integration Reference Point Manager (Integration Reference Point Manager, IRPManager).

The centralized SON function may include: a centralized CCO, a centralized ES, a centralized ANR, a centralized MRO, a centralized MLB and a centralized Inter-Cell Interference Control (Inter-Cell Interference Control, ICIC). The distributed SON function may include a distributed CCO, a distributed ES, a distributed ANR, a distributed MRO, a distributed MLB, a distributed Random Access Channel (Random Access Channel, RACH) optimization and a distributed ICIC.

In the SON function information of the SON function entity, the SON capability supported by the SON function entity (e.g., SON Capability Name) refers to the specific SON capability supported by the SON function entity, such as the centralized CCO, the centralized ES, the centralized ANR, the centralized MRO, the centralized MLB, the centralized ICIC, the distributed CCO, the distributed ES, the distributed ANR, the distributed MRO, the distributed MLB, the distributed RACH optimization and the distributed ICIC. The activation state of the SON capability supported by the SON function entity (e.g., SON Capability Activated) refers to indication information of the activation state of the SON capability supported specifically by the SON function entity, i.e., indicating whether an SON capability is currently activated on the SON function entity.

In S102, the SON function selection entity acquires an SON function selection policy.

In S103, the SON function selection entity selects an SON function based on the SON capability information of the SON function entity and the SON function selection policy.

In the embodiment of the invention, the SON function selection entity selects the SON function based on the SON capability information of the SON function entity and the SON function selection policy, thereby disabling those SON functions which may result in a possible executing conflict before SON cooperation.

In the embodiment of the invention, the SON function selection entity receives the SON capability information of the SON function entity, acquires the SON function selection policy, and selects an SON function based on the SON capability information and the SON function selection policy, so that the SON function selection entity can learn the SON capability information of the SON function entity, which facilitates the cooperation between the SON function selection entity and the SON function entity, thereby addressing executing conflict among functional use cases in cooperation of the SON functions in the conventional technology.

In an implementation, the SON function selection entity and the SON function entity may be different network elements or management systems in different scenarios, for example:

scenario 1: the SON function selection entity is a first base station, and the SON function entity is a second base station;

scenario 2: the SON function selection entity is an IRPManager, and the SON function entity is a base station;

scenario 3: the SON function selection entity is an IRPManager, and the SON function entity is an Integration Reference Point Agent (Integration Reference Point Agent, IRPAgent);

scenario 4: the SON function selection entity is an IRPManager, and the SON function entity includes an IRPAgent and a base station;

scenario 5: the SON function selection entity is an IRPAgent, and the SON function entity is a base station.

The method for selecting the SON capability in the foregoing different scenarios may be described respectively hereinafter.

As shown inFIG. 2, a method for selecting an SON capability in scenario 1 is provided according to this embodiment. The SON function selection entity is a first base station, and the SON function entity is a second base station. The method includes S201to S203.

In S201, the first base station receives SON capability information of the second base station sent by the second base station. The SON capability information of the second base station includes an SON capability supported by the second base station and an activation state of the SON capability supported by the second base station.

In an implementation, the SON capability supported by the second base station (e.g., SON Capability Name) refers to the specific SON capability of the second base station supporting SON function, such as a distributed CCO, a distributed ES, a distributed ANR, a distributed MRO, a distributed MLB, a distributed RACH optimization and a distributed ICIC. The activation state of the SON capability supported by the second base station (e.g., SON Capability Activated) refers to indication information of the activation state of the SON capability, i.e., indicating whether an SON capability is currently activated on the base station.

In the embodiment of the invention, the first base station receiving the SON capability information of the second base station sent by the second base station includes: the first base station receiving the SON capability information of the second base station sent by the second base station via an X2 interface setup process, via a base station configuration update process, or via a mobility management entity configuration update process. The three processes are described hereinafter.

a. In the X2 interface setup process, the second base station after being powered on initially detects a network via an existing self-establishing process and establishes an initial connection with the first base station and an OAM system in the network, and the self-established second base station sends the SON capability information to the first base station in the X2 Setup process so that the first base station can receive the SON capability information of the second base station.

b. In the base station configuration update process, i.e., eNB Configuration Update process, the second base station sends updated SON capability information to the first base station in the base station configuration update process at the X2 interface in a case that the SON capability information of the second base station is changed.

c. In the mobility management entity configuration update process, i.e., MME Configuration Update process, the second base station sends updated SON capability information to an MME in a base station configuration update process at an S1 interface in a case that the SON capability information of the second base station is changed, and the MME sends the updated SON capability information to the first base station in the mobility management entity configuration update process at the 51 interface.

In S202, the first base station acquires an SON function selection policy.

In the embodiment of the invention, the first base station acquiring the SON function selection policy includes: the first base station receiving the SON function selection policy which is preset and sent by an IRPAgent, or receiving the SON function selection policy which is preset by an IRPManager and forwarded by an IRPAgent.

In S203, the first base station selects an SON function based on the SON capability information of the second base station and the SON function selection policy.

In the embodiment of the invention, the first base station selects the SON capability based on the SON capability information of the second base station and the SON function selection policy, thereby disabling the SON function which may result in a possible executing conflict before SON cooperation.

In the technical solution of the embodiment of the invention, the first base station receives the SON capability information of the second base station, acquires the SON function selection policy, and selects an SON function based on the SON capability information of the second base station and the SON function selection policy, so that the first base station learns the SON capability information of the second base station, which facilitates the cooperation between the first base station and the second base station, thereby addressing the executing conflict among functional use cases in cooperation of the SON functions in the conventional technology.

As shown inFIG. 3, a method for selecting an SON capability in scenario 2 is provided according to this embodiment of the invention. The SON function selection entity is an IRPManager, and the SON function entity is a base station. The method includes S301to S303.

In S301, the IRPManager receives SON capability information of the base station sent by an IRPAgent. The SON capability information of the base station includes an SON capability supported by the base station and an activation state of the SON capability supported by the base station.

In an implementation, the SON capability supported by the base station (e.g., SON Capability Name) refers to the specific SON capability of the base station supporting SON function, such as a centralized CCO, a centralized ES, a centralized ANR, a centralized MRO, a centralized MLB and a centralized ICIC. The activation state of the SON capability supported by the base station (e.g., SON Capability Activated) refers to indication information of the activation state of the SON capability, i.e., indicating whether an SON capability is currently activated on the base station.

In the embodiment, the IRPManager receiving the SON capability information of the base station sent by the IRPAgent includes: the base station sending, on its own initiative, the SON capability information to the IRPManager via the IRPAgent in a self-establishing process of the base station, or the IRPManager acquiring the SON capability information of the base station by subscribing a notification, subscribing a log or creating a trace task.

In S302, the IRPManager acquires an SON function selection policy.

In the embodiment of the invention, the IRPManager acquiring the SON function selection policy includes: the IRPManager acquiring an SON function selection policy preset by an operator in the IRPManager.

In S303, the IRPManager selects an SON function based on the SON capability information of the base station and the SON function selection policy.

In the embodiment of the invention, the IRPManager selects the SON function based on the SON capability information of the base station and the SON function selection policy, thereby disabling the SON function which may result in a possible executing conflict before SON cooperation.

The SON function selection policy in this embodiment is illustrated as follows.

1. The IRPManager enables the SON function to be executed coordinately in the base station, as follows. In a use case of enabling/disabling ES in a cell, both a base station that an energy-saving cell belonging to (e.g., eNB1) and a base station that a cell providing a coverage support for the energy-saving cell belonging to (e.g., eNB2) need to enable the ES function. In the case that the SON capability information reported by the eNB1indicates that the ES capability is configured and the function is activated and the SON capability information reported by the eNB2 indicates that the ES capability is configured and the function is not activated, the IRPManager sends a message to the eNB2 via an IRPAgent to instruct the eNB2 to enable the ES function so that the eNB2 can perform the ES function.

2. The IRPManager disables the SON function which has a potential executing conflict, as follows. A base station A initiates an MRO process, and if the base station A can learn capability information of an adjacent base station B, for example, the base station B also initiates an MRO process or initiates an ICIC process, the base station A can determine which SON capability may affect the MRO process of the base station A based on the SON capabilities initiated by the base station B (for example, the ICIC function of the base station B is to reduce a transmitting carrier frequency power of the base station B to reduce intra-frequency interference of cells, which affects an adjustment of a mobility parameter of a MRO function of the base station A). If a selection policy, which defines that the ICIC function is disabled in a cell adjacent to the base station A in a case that a cell of the base station A initiates the MRO process, is configured in the IRPManager, the IRPManager may disable, via the IRPAgent, the activated ICIC function of the base station B which is adjacent to the base station A based on the preset selection policy, after the SON capability information supported by the cell of the base station A and by the adjacent cell of the base station B is reported to the IRPManager.

In the embodiment of the invention, the IRPManager receives the SON capability information of the base station, acquires the SON function selection policy, and selects an SON function based on the SON capability information and the SON function selection policy, so that the IRPManager learns the SON capability information of the base station, which facilitates the cooperation between the IRPManager and the base station, thereby addressing the executing conflict among functional use cases in cooperation of the SON functions in the conventional technology.

As shown inFIG. 4, a method for selecting an SON capability in scenario 3 is provided according to this embodiment. The SON function selection entity is an IRPManager, and the SON function entity is an IRPAgent. The method includes S401to S403.

In S401, the IRPManager receives SON capability information of the IRPAgent sent by the IRPAgent. The SON capability information of the IRPAgent includes an SON capability supported by the IRPAgent and an activation state of the SON capability supported by the IRPAgent.

In an implementation, the SON capability supported by the IRPAgent (e.g., SON Capability Name) refers to the specific SON capability of the IRPAgent supporting SON function, such as a centralized COO, a centralized ES, a centralized ANR, a centralized MRO, a centralized MLB and a centralized ICIC. The activation state of the SON capability supported by the IRPAgent (e.g., SON Capability Activated) refers to indication information of the activation state of the SON capability, i.e., indicating whether the SON capability is currently activated on the IRPAgent.

In the embodiment, the IRPManager receiving the SON capability information of the IRPAgent sent by the IRPAgent includes: the IRPAgent sending, on its own initiative, the SON capability information to the IRPManager in a self-establishing process, or the IRPManager acquiring the SON capability information of the IRPAgent by subscribing a notification, subscribing a log or creating a trace task.

In S402, the IRPManager acquires an SON function selection policy.

In the embodiment of the invention, the IRPManager acquiring the SON function selection policy includes: the IRPManager acquiring the SON function selection policy preset by an operator in the IRPManager.

In S403, the IRPManager selects an SON function based on the SON capability information of the IRPAgent and the SON function selection policy.

In the embodiment of the invention, the IRPManager selects the SON function based on the SON capability information of the IRPAgent and the SON function selection policy, thereby disabling the SON function which may result in a possible executing conflict before SON cooperation.

In the embodiment of the invention, the IRPManager receives the SON capability information of the IRPAgent, acquires the SON function selection policy, and selects an SON function based on the SON capability information and the SON function selection policy, so that the IRPManager learns the SON capability information of the IRPAgent, which facilitates the cooperation between the IRPManager and the IRPAgent, thereby addressing the executing conflict among functional use cases in cooperation of the SON functions in the conventional technology.

As shown inFIG. 5, a method for selecting an SON capability in scenario 4 is provided according to this embodiment. The SON function selection entity is an IRPManager, and the SON function entity includes an IRPAgent and a base station. The method includes S501to S504.

In S501, the IRPManager receives SON capability information of the IRPAgent sent by the IRPAgent. The SON capability information of the IRPAgent includes an SON capability supported by the IRPAgent and an activation state of the SON capability supported by the IRPAgent.

In an implementation, the SON capability supported by the IRPAgent (e.g., SON Capability Name) refers to the specific SON capability of the IRPAgent supporting SON function, such as a centralized COO, a centralized ES, a centralized ANR, a centralized MRO, a centralized MLB and a centralized ICIC. The activation state of the SON capability supported by the IRPAgent (e.g., SON Capability Activated) refers to indication information of the activation state of the SON capability, i.e., indicating whether the SON capability is currently activated on the IRPAgent.

In S502, the IRPManager receives SON capability information of the base station sent by the IRPAgent. The SON capability information of the base station includes an SON capability supported by the base station and an activation state of the SON capability supported by the base station.

In an implementation, the SON capability supported by the base station (e.g., SON Capability Name) refers to the specific SON capability of the base station supporting SON function, such as a centralized COO, a centralized ES, a centralized ANR, a centralized MRO, a centralized MLB and a centralized ICIC. The activation state of the SON capability supported by the base station (e.g., SON Capability Activated) refers to indication information of the activation state of the SON capability, i.e., indicating whether the SON capability is currently activated on the base station.

In the embodiment, the execution sequence of S501and S502is not limited.

In the embodiment, the IRPManager receiving the SON capability information of the IRPAgent and the SON capability information of the base station sent by the IRPAgent includes: the IRPAgent sending, on its own initiative, the SON capability information to the IRPManager in a self-establishing process, or the IRPManager acquiring the SON capability information of the IRPAgent by subscribing a notification, subscribing a log or creating a trace task.

In S503, the IRPManager acquires an SON function selection policy.

In the embodiment of the invention, the IRPManager acquiring the SON function selection policy includes: the IRPManager acquiring the SON function selection policy preset by an operator in the IRPManager.

In S504, the IRPManager selects an SON function based on the SON capability information of the base station, the SON capability information of the IRPAgent and the SON function selection policy.

The SON function selection policy in the embodiment is illustrated as follows: the IRPManager prohibits the same SON function configured in different entities from being executed simultaneously. For example, the IRPManager may be provided with an centralized ES function and the base station may be provided with a distributed ES function, then the IRPManager may enable the ES function of one entity and disable the ES function of another entity base on a certain policy after the IRPManager acquires the ES capability information of the IRPAgent and the base station.

In the embodiment of the invention, the IRPManager selects the SON function based on the SON capability information of the IRPAgent and the SON function selection policy, thereby disabling the SON function which may result in a possible executing conflict before SON cooperation.

In the embodiment of the invention, the IRPManager receives the SON capability information of the IRPAgent, acquires the SON function selection policy, and selects an SON function based on the SON capability information and the SON function selection policy, so that the IRPManager learns the SON capability information of the IRPAgent, which facilitates the cooperation between the IRPManager and the IRPAgent, thereby addressing the executing conflict among functional use cases in cooperation of the SON functions in the conventional technology.

In the foregoing Embodiments 3, 4 and 5, the IRPManager may send directly a request to the IRPAgent for acquiring the SON capability information of the base station and/or the IRPAgent in a case that the IRPManager is the SON function selection entity and the base station and/or the IRPAgent is the SON function entity. The process includes the steps as follows.

1. The IRPManager sends an acquisition request to the IRPAgent to acquire the SON capability information of a specified base station and/or IRPAgent;

2. The IRPAgent returns the current SON capability information of the base station and/or the IRPAgent based on the request of the IRPManager; and

3. The IRPManager determines, based on the SON capability information of multiple specified base stations and/or IRPAgents and in conjunction with the SON function selection policy configured in the IRPManager, whether to enable or disable some of the SON functions of the base stations and/or IRPAgents.

As shown inFIG. 6, a method for selecting an SON capability in scenario 5 is provided according to this embodiment. The SON function selection entity is an IRPAgent, and the SON function entity is a base station. The method includes S601to S603.

In S601, the IRPAgent receives SON capability information of the base station sent by the base station. The SON capability information of the base station includes an SON capability supported by the base station and an activation state of the SON capability supported by the base station.

In an implementation, the SON capability supported by the base station (e.g., SON Capability Name) refers to the specific SON capability of the base station supporting SON function, such as a centralized COO, a centralized ES, a centralized ANR, a centralized MRO, a centralized MLB and a centralized ICIC. The activation state of the SON capability supported by the base station (e.g., SON Capability Activated) refers to indication information of the activation state of the SON capability, i.e., indicating whether the SON capability is currently activated on the base station.

In S602, the IRPAgent acquires an SON function selection policy.

In the embodiment of the invention, the IRPAgent acquiring the SON function selection policy includes: the IRPAgent receiving the SON function selection policy set and sent by an IRPManager.

In S603, the IRPAgent selects an SON function based on the SON capability information of the base station and the SON function selection policy.

In the embodiment of the invention, the IRPAgent selects the SON function based on the SON capability information of the base station and the SON function selection policy, thereby disabling the SON function which may result in a possible executing conflict before SON cooperation.

In the technical solution of the embodiment of the invention, the IRPAgent receives the SON capability information of the base station, acquires the SON function selection policy, and selects an SON function based on the SON capability information and the SON function selection policy, so that the IRPAgent learns the SON capability information of the base station, which facilitates the cooperation between the IRPAgent and the base station, thereby addressing the executing conflict among functional use cases in cooperation of the SON functions in the conventional technology.

FIG. 7is a structure diagram of a device for selecting a self-organizing network SON function provided according to this embodiment of the invention. For convenience of the description, only the part which is related to the embodiment is illustrated, including a receiving unit71, an acquisition unit72and a selecting unit73.

The receiving unit71is configured to receive SON capability information of an SON function entity. The SON capability information of the SON function entity includes an SON capability supported by the SON function entity and an activation state of the SON capability supported by the SON function entity.

In the embodiment of the invention, the SON capability in the capability information received by the receiving unit71includes a centralized SON function and/or a distributed SON function. The contents of the centralized SON function and the distributed SON function may refer to the description in Embodiment 1, and the detailed description thereof is omitted herein.

In the SON function information of the SON function entity, the SON capability supported by the SON function entity and the activation state of the SON capability supported by the SON function entity may refer to the description in Embodiment 1, and the detailed description is omitted herein.

The acquisition unit72is configured to acquire an SON function selection policy.

The selecting unit73is configured to select an SON function based on the SON capability information of the SON function entity received by the receiving unit71and the SON function selection policy acquired by the acquisition unit72.

In the embodiment of the invention, the selecting unit73selects an SON function based on the SON capability information of the SON function entity received by the receiving unit71and the SON function selection policy acquired by the acquisition unit72, thereby disabling the SON function which may result in a possible executing conflict before SON cooperation.

In an implementation, the SON function selection entity and the SON function entity may be different network elements in different scenarios, and illustrations of a few selectable scenarios are described in the following.

Scenario 1: the SON function selection entity is a first base station, and the SON function entity is a second base station.

In this scenario, the receiving unit71is further configured to receive SON capability information of the second base station sent by the second base station. The SON capability information of the second base station includes an SON capability supported by the second base station and an activation state of the SON capability. The acquisition unit72is further configured to receive an SON function selection policy which is preset and sent by an IRPAgent or receive the SON function selection policy which is preset by an IRPManager and forwarded by an Integration Reference Point Agent IRPAgent. The selecting unit73is further configured to select an SON function based on the SON capability information of the second base station received by the receiving unit71and the SON function selection policy acquired by the acquisition unit72.

In this embodiment, the content of the SON capability information of the second base station received by the receiving unit71may refer to the content of the method embodiment 2, and the detailed description thereof is omitted herein. The method of receiving, by the first base station, the SON capability information of the second base station sent by the second base station may refer to the content of the method embodiment 2, and the detailed description thereof is omitted herein.

Scenario 2: the SON function selection entity is an IRPManager, and the SON function entity is a base station.

In this scenario, the receiving unit71is further configured to receive SON capability information of the base station sent by an IRPAgent. The SON capability information of the base station includes an SON capability supported by the base station and an activation state of the SON capability. The acquisition unit72is further configured to acquire an SON function selection policy preset by an operator in the IRPManager. The selecting unit73is further configured to select an SON function based on the SON capability information of the base station received by the receiving unit71and the SON function selection policy acquired by the acquisition unit72.

Scenario 3: the SON function selection entity is an IRPManager, and the SON function entity is an IRPAgent.

In this scenario, the receiving unit71is further configured to receive SON capability information of the IRPAgent sent by the IRPAgent. The SON capability information of the IRPAgent includes an SON capability supported by the IRPAgent and an activation state of the SON capability supported by the IRPAgent. The acquisition unit72is further configured to acquire an SON function selection policy preset by an operator in the IRPManager. The selecting unit73is further configured to select an SON function based on the SON capability information of the IRPAgent received by the receiving unit71and the SON function selection policy acquired by the acquisition unit72.

Scenario 4: the SON function selection entity is an IRPManager, and the SON function entity includes an IRPAgent and a base station.

In this scenario, the receiving unit71is further configured to receive SON capability information of the IRPAgent and SON capability information of the base station sent by the IRPAgent. The SON capability information of the IRPAgent includes an SON capability supported by the IRPAgent and an activation state of the SON capability supported by the IRPAgent. The SON capability information of the base station includes an SON capability supported by the base station and an activation state of the SON capability supported by the base station. The acquisition unit72is further configured to acquire an SON function selection policy preset by an operator in the IRPManager. The selecting unit73is further configured to select an SON function based on the SON capability information of the base station and the SON capability information of the IRPAgent received by the receiving unit71and the SON function selection policy acquired by the acquisition unit72.

Scenario 5: the SON function selection entity is an IRPAgent, and the SON function entity is a base station.

In this scenario, the receiving unit71is further configured to receive SON capability information of the base station sent by the base station. The SON capability information of the base station includes an SON capability supported by the base station and an activation state of the SON capability. The acquisition unit72is further configured to receive an SON function selection policy preset and sent by an IRPManager. The selecting unit73is further configured to select an SON function based on the SON capability information of the base station received by the receiving unit71and the SON function selection policy acquired by the acquisition unit72.

In the embodiment, the SON function selection entity selects an SON function based on the SON capability information of the SON function entity and the SON function selection policy, thereby disabling the SON function which may result in a possible executing conflict before SON cooperation.

The SON function selection entity in the embodiment receives the SON capability information of the SON function entity, acquires the SON function selection policy, and selects an SON function based on the SON capability information and the SON function selection policy, so that the SON function selection entity learns the SON capability information of the SON function entity, which facilitates the cooperation between the SON function selection entity and the SON function entity, thereby addressing the executing conflict among functional use cases in cooperation of the SON functions in the conventional technology.

A system for selecting a self-organizing network SON function is further provided according to an embodiment of the invention. The system includes the SON function selection entity as described in the embodiment 7 and at least one SON function entity.

The SON function selection entity may be the first base station in the scenario 1 of the embodiment 7, and the SON function entity may be the second base station.

Alternatively, the SON function selection entity may be the IRPManager in the scenario 2 of the embodiment 7, and the SON function entity may be the base station.

Alternatively, the SON function selection entity may be the IRPManager in the scenario 3 of the embodiment 7, and the SON function entity may be the IRPAgent.

Alternatively, the SON function selection entity may be the IRPManager in the scenario 4 of the embodiment 7, and the SON function entity may include the IRPAgent and the base station.

Alternatively, the SON function selection entity may be the IRPAgent in the scenario 5 of the embodiment 7, and the SON function entity may be the base station.

In the embodiment, the SON function selection entity selects an SON function based on the SON capability information of the SON function entity and the SON function selection policy, thereby disabling the SON function which may result in a possible executing conflict before SON cooperation.

In the system provided by the embodiment, the SON function selection entity receives the SON capability information of the SON function entity, acquires the SON function selection policy, and selects an SON function based on the SON capability information and the SON function selection policy, so that the SON function selection entity learns the SON capability information of the SON function entity, which facilitates the cooperation between the SON function selection entity and the SON function entity, thereby addressing executing conflict among functional use cases in cooperation of the SON functions in the conventional technology.

It may be understood by those skilled in the art that a few or all of the procedures implementing the above method of the embodiments may be realized by instructing the related hardware via computer programs. The programs may be stored in a computer-readable storage medium. The programs, when being executed, include the procedures in the above method of embodiments. The storage medium may be a disk, an optical disk, a Read-Only Memory (Read-Only Memory, ROM) or a Random Access Memory (Random Access Memory, RAM).

The foregoing disclosure is only the preferable embodiments of the invention, which do not limit the protection scope of the invention. Those skilled in the art can understand a few or all of the procedures implementing the foregoing embodiments, and the equivalent variation made by those skilled in the art based on the claims of the invention fall into the protection scope of the invention.