Managed Unit Device, Self-Optimization Method and System

Information

  • Patent Application
  • 20130339522
  • Publication Number
    20130339522
  • Date Filed
    August 20, 2013
    11 years ago
  • Date Published
    December 19, 2013
    11 years ago
Abstract
A managed unit executes a self-optimization according to a self-optimization trigger rule. The self-optimization trigger rule relates to a self-optimization capability supported by the managed unit. The self-optimization capability supported by the managed unit includes any one of or any combination of a self-optimization type, a self-optimization trigger condition, a self-optimization objective, and a self-optimization monitoring cycle.
Description
TECHNICAL FIELD

The present invention relates to the field of communication network technologies, and in particular, to a managed unit device, a self-optimization method and system.


BACKGROUND

Network optimization is one of major scenarios of daily maintenance of communication network. By collecting data such as Key Performance Indicators (KPI), tracking and a Measurement Report (MR) of a current network, a network operating state is monitored, aspects such as neighbor missing, a coverage hole and frequency interference that affect network operating performance are found in time, and adjustment is performed accordingly, so as to achieve the objective of improving the network operating performance.


During conventional network optimization, various network optimization tools are adopted to analyze and sort data, so as to locate and find problems, and maintenance personnel propose a solution of network optimization according to experience and based on the data. The scenario is complex, the process is complicated, and requirements on skills of the maintenance personnel are high.


For a Long Term Evolution (LTE) system of next generation wireless communication technologies, which is characterized by mass Network Elements (NEs), adopts the full Internet Protocol (IP), mixture of multi-vendor devices and different standards, operation and maintenance scenarios faced by the conventional network optimization are more complex. In order to avoid an enormous cost caused by the conventional network optimization which mainly depends on experience, judgment and operation of maintenance personnel, the 3rd Generation Partnership Project (3GPP), an organization for standardization of the next generation communication technologies, proposes the Self-Organizing Network (SON) technologies, that is, experience and intelligence of experts are solidified into programs, so that the network has capabilities to collect data automatically, analyze and identify problems automatically, and perform adjustment automatically. The SON technologies reduce manual intervention to some extent, decrease requirements on skills of maintenance personnel, and eventually achieve an objective of reducing the network operation and maintenance cost.


In the SON technologies, self-optimization as an important SON function covers a large scope, and self-optimization types currently under research of the 3GPP include: Handover optimization, Load Balancing optimization, Interference Control optimization, Capacity & Coverage optimization, Random Access Channel (RACH) optimization, and Energy Saving optimization.


In the prior art, in various self-optimization cases, after an optimization policy is formulated by analyzing, an optimization command is operated manually to execute an optimization process.


During the implementation of the present invention, the inventors find that the prior art at least has the following disadvantages. A northbound interface (Itf-N) between a Network Management System (NMS) and an Element Management System (EMS) does not provide control support of self-optimization operating functions. If a user is required to perform self-optimization on a communication system, possible optimization parameters are required to be acquired by manual analysis, and the self-optimization is completed by sending corresponding configuration modification commands, which greatly increases complexity and processing time of a self-optimization process.


SUMMARY OF THE INVENTION

In one aspect, the present invention provides a self-optimization method. A managed unit executes a self-optimization according to a self-optimization trigger rule that is created by a managing unit according to the self-optimization capability supported by the managed unit.


In one aspect, the present invention also provides a managed unit device. This device includes a self-optimization execution module that is configured to execute a self-optimization according to a self-optimization trigger rule. The rule is created by a managing unit according to the self-optimization capability supported by the managed unit.


In another aspect, the present invention further provides a self-optimization system. This system includes a managed unit that is configured to execute a self-optimization according to a self-optimization trigger rule. The rule is created by a managing unit according to the self-optimization capability supported by the managed unit.


In the proceeding technical solutions, a managed unit executes self-optimization according to a self-optimization trigger rule, so that the managed unit does not need to execute the self-optimization in the mode of receiving a command, which avoids completing the self-optimization in a mode in which a user sends a corresponding configuration modification command, thereby greatly decreasing the complexity of a self-optimization process, and reducing manual processing time for the self-optimization.





BRIEF DESCRIPTION OF THE DRAWINGS


FIG. 1A is a schematic diagram of inheritance of an SOManagementCapablity class, an SOTriggerRule class, and an SOProcess class in a self-optimization method according to an embodiment of the present invention;



FIG. 1B is another schematic diagram of inheritance of an SOManagementCapablity class, an SOTriggerRule class, and an SOProcess class in a self-optimization method according to an embodiment of the present invention;



FIG. 1C is a schematic diagram of inheritance of a SelfOptimizationIRP class in a self-optimization method according to an embodiment of the present invention;



FIG. 1D is a schematic diagram of relationships of a SelfOptimizationIRP class and an SOManagementCapablity class, an SOTriggerRule class, and an SOProcess class in a self-optimization method according to an embodiment of the present invention;



FIG. 2 is a flow chart of another self-optimization method according to an embodiment of the present invention;



FIG. 3 is a flow chart of still another self-optimization method according to an embodiment of the present invention; and



FIG. 4 is a schematic structural diagram of a self-optimization system according to an embodiment of the present invention.





DETAILED DESCRIPTION OF ILLUSTRATIVE EMBODIMENTS

A self-optimization method according to an embodiment of the present invention includes executing, by a managed unit, a self-optimization according to a self-optimization trigger rule. For example, if a self-optimization type set according to the self-optimization trigger rule is Load Balancing, and if the managed unit satisfies a trigger condition set according to the self-optimization trigger rule, the managed unit executes Load Balancing optimization.


In this embodiment, the managed unit executes self-optimization according to the self-optimization trigger rule, thereby preventing optimization executed by inputting a configuration modification command manually, greatly decreasing complexity of a self-optimization process, and reducing manual processing time of the self-optimization process.


In the proceeding embodiment, the self-optimization trigger rule may be set by the managed unit according to a capability of the managed unit by default. For example, if a managing unit does not set a self-optimization trigger rule, the managed unit may use the capability supported by the managed unit as a default self-optimization trigger rule by default.


Alternatively, a self-optimization trigger rule may also be created by the managing unit. Detailed descriptions are as follows.


A communication network includes Network elements (NEs). NEs are provided by various vendors. Meanwhile each of the vendors provides an EMS to manage the NEs of the vendor through their respective private interface, and an operator performs unified management on the network through an NMS. In an embodiment of the present invention, various classes dedicated to the self-optimization are configured between the NMS and the EMS and the classes are used in various self-optimization cases.


For convenience of description, in embodiments of the present invention, an Integrated Reference Point (IRP) manager IRPManager represents an operation initiator, that is, a managing unit such as an NMS. An IRP agent IRPAgent represents an operation executor, that is, a managed unit, such as an EMS and an NE. Refer to the 3GPP specifications for the IRPManager and the IRPAgent.


Classes that are set may include a self-optimization capability (SOManagementCapablity) class, a self-optimization trigger rule (SOTriggerRule) class, a self-optimization execution (SOProcess) class, and a self-optimization operation (SelfOptimizationIRP) class. Relationships of the classes are shown in FIG. 1A, FIG. 1B, FIG. 1C, and FIG. 1D. A schematic diagram of inheritance relationships of the SOManagementCapablity class, the SOTriggerRule class, and the SOProcess class is shown in FIG. 1A, and a parent class is a “Top” class.


Alternatively, a schematic diagram of inheritance relationships of the SOManagementCapablity class, the SOTriggerRule class, and the SOProcess class is shown in FIG. 1B. The parent class of the SOManagementCapablity class is a “GenCtrlCapability” class, the parent class of the SOTriggerRule class is a “GenCtrlTriggerRule” class, and the parent class of the SOProcess class is a “GenCtrlProcess” class.


As shown in FIG. 1C, the parent class of the SelfOptimizationIRP class is a “ManagedGenericIRP” class. Relationships between the SelfOptimizationIRP class and the SOManagementCapablity class, the SOTriggerRule class and the SOProcess class are shown in FIG. 1D. The SelfOptimizationIRP class includes relevant operations on self-optimization function management. The SOTriggerRule sets a specific trigger rule based on functions supported by the SOManagementCapablity class. When a trigger condition configured by the SOTriggerRule is satisfied, the system automatically generates an entity of the SOProcess class to perform a specific optimization execution process.


The SOManagementCapablity class is shown in Table 1, which describes a self-optimization capability that the IRPAgent can provide.









TABLE 1







SOManagementCapablity class












Support
Read
Write



Attribute Name
Qualifier
Qualifier
Qualifier
Comment





Id
M
M

Object Identifier (ID)


Information of a managed unit
M
M

An entity class or an


(CtrlObjInformation)



entity providing a self-






optimization






capability, which may






be an EM; an attribute






capable of identifying






one or more






commonalities of an






NE; a NE type; and






one or more specific






NEs


A list of supported optimization
M
M

To describe the


trigger conditions



capability that can be


(offeredOptimization-



provided by the self-


TriggerRuleList)



optimization, which is






represented by a list,






each item of which






includes the following






information: a






supported self-






optimization type;






information of a






supported Performance






Measurement (PM)






indicator; and a policy






granularity supported






by the PM indicator.


A list of supported optimization
M
M

To describe self-


objectives



optimization


(offeredOptimizationObjectiveList)



objectives, which are






represented by a list






including optimization






objectives and






relationships between






the objectives.









In this table and the following tables, “M” indicates compulsory.


The SOManagementCapablity class is provided by the IRPAgent, and the IRPManager cannot modify the content of the SOManagementCapablity class. The SOManagementCapablity class mainly includes the following information: information of a managed unit, a list of supported optimization trigger conditions, and supported optimization objectives. The list of supported optimization trigger conditions includes a supported optimization type, that is, a supported self-optimization case, a PM indicator supported in a self-optimization trigger condition, and a policy granularity, which is a measurement cycle, supported by the PM indicator. The supported PM indicator is a corresponding PM that can be monitored by a managed unit such as an EMS and an NE. The supported self-optimization objectives include one or more self-optimization objectives, and particularly when the supported self-optimization objectives are multiple self-optimization objectives, relationships between the self-optimization objectives are also included. The relationships exist in multiple manners. For example, different optimization objectives may have different priorities or weights, or a certain arithmetic operation relationship exists between the different optimization objectives, or a certain logic operation relationship exists between the different optimization objectives.


The SOTriggerRule class, as shown in Table 2, describes a rule of triggering a self-optimization process. The self-optimization trigger rule may include: an object ID of a self-optimization trigger rule, information of a managed unit (CtrlObjInformation), an optimization type (OptimizationType), an optimization detection granularity (optimizationMonitoringGranularity), an optimization detection statistical information (optimizationMonitoringCounterInfo), optimization objective information (optimizationObjectiveInfo), and optimization confirmation (needConfirmationBeforeOptimization).


It should be noted that content further included in the rule of triggering a self-optimization process may be one of or any combination of the content listed in Table 2. The optimizationMonitoringGranularity attribute is used to indicate a detection cycle of a PM indicator. The optimizationMonitoringCounterInfo attribute is used to indicate statistical information of detection. The statistical information is a trigger condition that a managed unit executes self-optimization. If the managed unit detects the PM indicator by using the optimizationMonitoringGranularity as the cycle, and the detected statistical information satisfies the setting of the optimizationMonitoringCounterInfo in the SOTriggerRule, the execution of the self-optimization is started. The needConfirmationBeforeOptimization attribute is to set whether the self-optimization operation is required to be confirmed manually. If the needConfirmationBeforeOptimization is set that manual confirmation is required, the self-optimization operation can only be performed after the manual confirmation before the managed unit executes the self-optimization. If the needConfirmationBeforeOptimization is set that no manual confirmation is required, no manual confirmation is required, and the self-optimization is directly executed.









TABLE 2







SOTriggerRule class












Support
Read
Write



Attribute Name
Qualifier
Qualifier
Qualifier
Comment





Id
M
M

An object ID, used






to distinguish






different instances






of the






SOTriggerRule class


CtrlObjInformation
M
M

An entity providing






a self-optimization






capability, that is, a






run entity of a self-






optimization






algorithm, which






may be an EMS; a






NE type; and one or






more specific NEs


OptimizationType
M
M

A self-optimization






type


OptimizationMonitoringGranularity
M
M

A policy cycle of a






PM indicator, that






is, a statistical cycle






of the indicator


OptimizationMonitoringCounterInfo
M
M

A self-optimization






trigger condition


OptimizationObjectiveInfo
M
M

A self-optimization






objective


needConfirmationBeforeOptimization
M
M

Whether the self-






optimization






operation is required






to be confirmed by






the IRPManager









The SOProcess class, as shown in Table 3, represents an execution process of the self-optimization. The attributes of the SOProcess class include an ID, a managed unit ID (CtrlObjectIdentification), a trigger rule ID (triggerRuleId), and a process status (processStatus).









TABLE 3







SOProcess class












Support
Read
Write



Attribute Name
Qualifier
Qualifier
Qualifier
Comment





Id
M
M

An object ID


CtrlObjectIdentification
M
M

A managed unit ID, that is, an






ID of an NE running self-






optimization


triggerRuleId
M
M

A trigger rule ID, that is, an






ID of an SOTriggerRule class






used by self-optimization


processStatus
M
M

An execution status of a self-






optimization process, which






is a wait-for-user-to-confirm






status, a self-optimization-is-






running status, or a self-






optimization-is-evaluating-a-






result status









The SelfOptimizationIRP class defines an IRP to perform self-optimization management. As shown in Table 4, interface operation functions provided by the SelfOptimizationIRP include a trigger rule creation function (CreateTriggerRule( )) and a self-optimization capability query function (ListSoCapabilities( )). The interface operation functions may further include a trigger rule deletion function (DeleteTriggerRule( )), a trigger rule query function (ListTriggerRule( )), a trigger rule modification function (ChangeTriggerRule( )), a self-optimization process query function (ListSoProcess( )), an optimization execution confirmation function (ConfirmOptimizationExecution( )), and a self-optimization process termination function (TerminateSOProcess( )).









TABLE 4







SOOptimizationIRP class










Operation





Function
Input Parameter
Output Parameter
Comment





CreateTriggerRule
triggerRuleId: a trigger rule object
triggerRuleId: ID
Create an


(triggerRuleId,
to be created, that is, a trigger rule
information of a trigger
SOTriggerRule


ctrlObjInformation,
ID; the parameter may also be
rule such as an ID of a
object


triggerRule,
replaced with trigger rule ID
created trigger rule


result)
information such as attribute
object



information capable of uniquely
Result: an execution



representing a trigger rule;
result, the legal value



ctrlObjInformation: information of
of which is success,



a managed unit, which is an NE
failure, or information



managing unit, capable of
indicating the created



identifying a common attribute of
rule overlaps an



a set of NEs, or one piece of or
existing rule



any combination of information
When the Result



of one or more NE entities
indicates information



triggerRule: a trigger rule
that indicates the



(including all attributes of a self-
created rule overlaps an



optimization trigger rule;
existing rule, the ID



information of a managed unit, a
information of the



self-optimization type, a self-
trigger rule includes ID



optimization detection granularity,
information of the



and a self-optimization trigger
conflicting existing rule



condition)


DeleteTriggerRule
TriggerRuleId: an ID of a
Result: an execution
Delete an


(TriggerRuleId,
TriggerRule object to be deleted,
result, the legal value
SOTriggerRule


result)
that is, ID information of a trigger
of which is success or
object



rule
failure


ListSoCapabilities
CtrlObjInformation: information
offeredOptimizationCapability
Query a self-


(CtrlObjInformation,
of a managed unit
List:
optimization


offeredOptimization

information of
capability of


CapabilityList,

supported capability
a managed


result)

Result: an execution
unit




result, the legal value
(SOManagement




of which is success or
Capablity)




failure


ListTriggerRule
triggerRuleId: an ID of a
TriggerRuleList: a list
Query


(triggerRuleId,
TriggerRule object to be queried,
of SOTriggerRule
information


CtrlObjInformation,
that is, an ID of a trigger rule, the
objects, that is, a self-
of the


TriggerRuleList,
parameter may also be replaced
optimization trigger
SOTriggerRule,


result)
with trigger rule ID information
rule list including
in which



such as attribute information
information of a
when the



capable of uniquely representing a
managed unit, a self-
triggerRuleId



trigger rule
optimization type, a
and the



CtrlObjInformation: information
self-optimization
ctrlObjInformation



of a managed unit to be queried
detection granularity,
are



When the two parameters are
and a self-optimization
default, it



default, that is are not set, self-
trigger condition
indicates that



optimization trigger rules of all
Result: an execution
all trigger



managed units are queried. When
result, the legal value
rules of all



the two parameters are configured
of which is success or
managed



by default other than specifically,
failure
units are



self-optimization trigger rules of

queried



all managed units are queried.


ListSOProcess(ctrl
CtrlObjInformation: an ID of a
SOMProcessList: a list
Query


ObjIdentification,
managed unit to be queried
of a self-optimization
information


SOMProcessList,
If no specific ID of a managed
process, which includes
of a running


result)
unit is specified, all IDs are
an ID, an ID of a
self-



queried.
managed unit, an ID of
optimization




a trigger rule, and
SOProcess




status information such
object, in




as an execution status
which when




of a self-optimization
no input




process
parameter is




Result: an execution
specified,




result, the legal value
status




of which is success or
information




failure
of a self-





optimization





process of all





managed





units is





queried


ConfirmOptimization
ctrlObjIdentification: an ID of a
Result: an execution
Confirm self-


Execution
managed unit, that is, an object ID
result, the legal value
optimization


(ctrlObjIdentification
corresponding to confirmed
of which is success or
operation to


List, result)
operation, which may be one or
failure
be executed



more managed unit IDs


TerminateSOProcess
ctrlObjIdentification: an ID of a
Result: an execution
Terminate a


(ctrlObjIdentification
managed unit, that is, an object ID
result, the legal value
self-


List, result)
corresponding to confirmed
of which is success or
optimization



operation, which may be one or
failure
process



more managed unit IDs


ChangeTriggerRule
triggerRuleId: an ID of a trigger
triggerRuleId: an ID of
Modify an


(triggerRuleId,
rule to be modified, that is, an
a modified trigger rule
SOTriggerRule


ctrlObjInformation,
object, ID information of the
object, that is, ID
object


triggerRule,
trigger rule; ctrlObjInformation:
information of a trigger


result)
information of a managed unit
rule



triggerRule: a trigger rule
Result: an execution



(including all attributes of a self-
result, the legal value



optimization trigger rule:
of which is success,



information of a managed unit, a
failure, or information



self-optimization type, a self-
indicating the created



optimization detection granularity,
rule overlaps an



and a self-optimization trigger
existing rule



condition)
When the Result




indicates information




that indicates the




created rule overlaps an




existing rule, the




triggerRuleId includes




ID information of the




conflicting existing rule










FIG. 2 is a flow chart of another self-optimization method according to an embodiment of the present invention. In this embodiment, pre-configured interfaces are used to trigger a self-optimization process, which includes the following steps.


Step 21: Acquire a self-optimization capability of a managed unit. In a specific implementation process, a managing unit may query and acquire the self-optimization capability of the managed unit (such as an NE) by invoking a self-optimization capability query function such as ListSOCapabilities( ).


Step 22: Create a self-optimization trigger rule according to the queried self-optimization capability of the managed unit, such as a self-optimization type, a PM indicator that can be monitored, and a policy granularity of monitoring the PM indicator. For example, in a specific implementation process, the managing unit may create a self-optimization trigger rule, such as a self-optimization type and a self-optimization trigger condition according to the queried self-optimization capability of the managed unit by invoking a trigger rule creation function, such as CreateTriggerRule( ).


Step 23: When the trigger condition of the self-optimization rule is satisfied, the managed unit executes the self-optimization according to the trigger rule created in step 22. For example, if the self-optimization type specified in the trigger rule is Energy Saving, the managed unit executes self-optimization of the Energy Saving.


In the self-optimization method of the embodiment of the present invention, the self-optimization capability of the managed unit may be acquired by the managing unit by other means. For example, the managing unit acquires the self-optimization capability of the managed unit according to instructions in a user manual or content in a contract.


In addition, it should be noted that the managing unit may also create the self-optimization rule not according to the self-optimization capability of the managed unit, but according to, for example, configurations of the managing unit or saved relevant information.


The self-optimization method of the embodiment of the present invention may further include querying, by the managing unit, a currently existing self-optimization rule of the managed unit. For example, in a specific implementation process, a currently existing self-optimization rule of the managed unit may be queried by invoking a trigger rule query function in the SOOptimizationIRP class for querying a self-optimization trigger rule, for example, ListTriggerRule( ).


The self-optimization method of the embodiment of the present invention may further include starting, by the managed unit, a self-optimization process according to the set self-optimization trigger rule when conditions are satisfied. When the needConfirmation-BeforeOptimization attribute of the SOTriggerRule class is configured to be “true”, execution of the self-optimization process is suspended before the managed unit executes a specific self-optimization modification operation, until the managing unit confirms a self-optimization execution suggestion sent by the managed unit. For example, in a specific implementation process, the managing unit may confirm the self-optimization execution suggestion sent by the managed unit by invoking an optimization execution confirmation function, such as ConfirmOptimizationExecution( ). As shown in FIG. 3, after the self-optimization execution suggestion is confirmed by the managing unit, the managed unit executes the self-optimization.


The self-optimization method of the embodiment of the present invention may further include querying, by the managing unit, status information of the self-optimization process. For example, in a specific implementation process, the managing unit may query the status information of the self-optimization process by invoking a self-optimization process query function in the SOOptimizationIRP class for querying a self-optimization process, such as ListSOProcess( ).


Another self-optimization method of the embodiment of the present invention may further include terminating, by the managing unit, the self-optimization. For example, in a self-optimization execution process, the managing unit may terminate the self-optimization by invoking a self-optimization termination function in the SOOptimizationIRP class for terminating self-optimization, such as TerminateSOProcess( ).


Another self-optimization method of the embodiment of the present invention may further include: modifying, by the managing unit, the self-optimization trigger rule. For example, in a specific implementation process, the managing unit may modify the self-optimization trigger rule created in step 22 by invoking a trigger rule modification function in the SOOptimizationlRP class for modifying a self-optimization trigger rule, such as ChangeTriggerRule( ).


The self-optimization method of the embodiment of the present invention may further include deleting, by the managing unit, the self-optimization trigger rule. For example, in a specific implementation process, the managing unit may delete the self-optimization trigger rule created in step 22 by invoking a trigger rule deletion function in the SOOptimizationIRP class for deleting a self-optimization trigger rule, such as DeleteTriggerRule( ).


In the method according to the embodiment, the managing unit creates the self-optimization trigger rule to trigger the self-optimization, and the managed unit executes the self-optimization according to the self-optimization trigger rule created by the managing unit, thereby enhancing the flexibility of acquisition of the self-optimization trigger rule. Furthermore, rule modification and deletion and self-optimization termination are performed by invoking the classes, so that a user can monitor and manage the self-optimization process through the managing unit, thereby greatly reducing the complexity and processing time of the self-optimization process.


According to an embodiment of the present invention, a managed unit device, for example an EMS or an NE, is provided, which includes a self-optimization execution module. The self-optimization execution module is configured to execute a self-optimization according to a self-optimization trigger rule, so that a managed unit does not need to receive a command to execute self-optimization, which avoids completing the self-optimization in a mode in which a user sends a corresponding configuration modification command, thereby greatly reducing the complexity of a self-optimization process and the manual processing time of the self-optimization. In addition, a managing device can control the self-optimization by modifying the self-optimization trigger rule, so that the self-optimization process runs under the control and demand of the user.


A self-optimization system according to an embodiment of the present invention may include a managed unit. The managed unit may be the managed unit device in the embodiment of device, and is configured to execute a self-optimization according to a self-optimization trigger rule, so that the self-optimization system may execute the self-optimization without the need of receiving a command from a user, thereby greatly reducing the complexity of a self-optimization process and the manual processing time of the self-optimization. In addition, the user may control the self-optimization by modifying the self-optimization trigger rule, so that the self-optimization process runs under the control and demand of the user.



FIG. 4 is a schematic structural diagram of a self-optimization system according to an embodiment of the present invention. The system includes a managing unit 41 and a managed unit 42. The managing unit 41 creates a self-optimization trigger rule and the managed unit 42 executes self-optimization according to the self-optimization trigger rule created by the managing unit 41, thereby enhancing the flexibility of acquisition of the self-optimization trigger rule. The managing unit 41 may be an NMS and the managed unit 42 may be an EMS or an NE. The managing unit 41 may also delete or modify the self-optimization trigger rule.


In the proceeding method, device, and system according to the embodiments, the managed unit executes the self-optimization according to the self-optimization trigger rule, so that the managed unit does not need to receive a command to execute the self-optimization, which avoids completing the self-optimization in a mode in which a user sends a corresponding configuration modification command, thereby greatly reducing the complexity of a self-optimization process and the manual processing time of the self-optimization. In addition, the user may control the self-optimization by modifying the self-optimization trigger rule, so that the self-optimization process runs under the control and demand of the user.


The idea of the present invention is also applicable to management and control of a self-healing function of the managed unit performed by the managing unit. For the control of the self-healing function, the managed unit is required to provide capability of supporting alarm information. Relevant trigger rules are set for the alarm information.


Persons skilled in the art should understand that all or part of the steps of the method according to the embodiments of the present invention may be implemented by a program instructing relevant hardware. The program may be stored in a computer readable storage medium. When the program is run, the steps of the method according to the embodiments of the present invention are performed. The storage medium may be any medium capable of storing program codes, such as a ROM, a RAM, a magnetic disk, and an optical disk.


Finally, it should be noted that the above embodiments are merely provided for describing the technical solutions of the present invention, but not intended to limit the present invention. It should be understood by persons skilled in the art that although the present invention has been described in detail with reference to the foregoing embodiments, modifications may be made to the technical solutions described in the foregoing embodiments, or equivalent replacements may be made to some technical features in the technical solutions, as long as such modifications or replacements do not cause the essence of corresponding technical solutions to depart from the scope of the technical solutions of the embodiments of the present invention.

Claims
  • 1. A self-optimization method, comprising: executing, by a managed unit, a self-optimization according to a self-optimization trigger rule, wherein the self-optimization trigger rule relates to a self-optimization capability supported by the managed unit, and the self-optimization capability supported by the managed unit comprises any one of or any combination of a self-optimization type, a self-optimization trigger condition, a self-optimization objective, and a self-optimization monitoring cycle.
  • 2. The self-optimization method according to claim 1, wherein the self-optimization capability supported by the managed unit comprises a self-optimization type.
  • 3. The self-optimization method according to claim 1, wherein the self-optimization capability supported by the managed unit comprises a self-optimization trigger condition.
  • 4. The self-optimization method according to claim 1, wherein the self-optimization capability supported by the managed unit comprises a self-optimization objective.
  • 5. The self-optimization method according to claim 1, wherein the self-optimization capability supported by the managed unit comprises a self-optimization monitoring cycle.
  • 6. The self-optimization method according to claim 1, further comprising creating, by a managing unit, the self-optimization trigger rule.
  • 7. The self-optimization method according to claim 6, wherein creating the self-optimization trigger rule comprises creating the self-optimization trigger rule, by using any one of or any combination of identifier information of the trigger rule, information of the managed unit, a self-optimization type, a self-optimization monitoring cycle, a self-optimization objective, and a self-optimization trigger condition according to the self-optimization capability of the managed unit.
  • 8. The self-optimization method according to claim 1, wherein the self-optimization trigger rule comprises any one of or any combination of a self-optimization type, a self-optimization monitoring cycle, a self-optimization objective, a self-optimization trigger condition, and whether user confirmation is required before execution of the optimization.
  • 9. The self-optimization method according to claim 8, wherein the self-optimization trigger rule further comprises relationships of multiple self-optimization objectives when the self-optimization trigger rule comprises multiple self-optimization objectives.
  • 10. The self-optimization method according to claim 9, wherein the relationships of the multiple self-optimization objectives comprise any one of or any combination of a priority relationship, a weight relationship, an arithmetic operation relationship, and a logic operation relationship.
  • 11. The self-optimization method according to claim 1, further comprising acquiring, by the managing unit, the self-optimization capability of the managed unit.
  • 12. A device, comprising: a memory configured to store a self-optimization trigger rule; anda processor coupled to the memory and configured to execute a self-optimization according to the self-optimization trigger rule;wherein the self-optimization trigger rule relates to a self-optimization capability supported by the device, and the self-optimization capability supported by the device comprises any one of or any combination of a self-optimization type, a self-optimization trigger condition, a self-optimization objective, and a self-optimization monitoring cycle.
  • 13. The device according to claim 12, wherein the self-optimization trigger rule comprises any one of or any combination of a self-optimization type, a self-optimization monitoring cycle, a self-optimization objective, a self-optimization trigger condition, and whether user confirmation is required before execution of the optimization.
  • 14. A self-optimization system, comprising: a first device comprising a first processor and a computer program code, which, when executed by the first processor, will cause the first processor to execute a self-optimization according to a self-optimization trigger rule; anda second device configured to connect to the first device through an interface;wherein the self-optimization trigger rule relates to a self-optimization capability supported by the first device, and the self-optimization capability supported by the first device comprises any one of or any combination of a self-optimization type, a self-optimization trigger condition, a self-optimization objective, and a self-optimization monitoring cycle.
  • 15. The self-optimization system according to claim 14, wherein the second device comprises a second processor configured to create the self-optimization trigger rule.
  • 16. The self-optimization system according to claim 15, wherein the second processor is further configured to create the self-optimization trigger rule by using one of or any combination of identifier information of the trigger rule, information of a managed unit, a self-optimization type, a self-optimization monitoring cycle, a self-optimization objective, and a self-optimization trigger condition according to the self-optimization capability of the first device.
  • 17. The self-optimization system according to claim 14, wherein the self-optimization trigger rule comprises any one of or any combination of a self-optimization type, a self-optimization monitoring cycle, a self-optimization objective, a self-optimization trigger condition, and whether user confirmation is required before execution of the optimization.
  • 18. The self-optimization system according to claim 17, wherein the self-optimization trigger rule further comprises relationships of multiple self-optimization objectives when the self-optimization trigger rule comprises multiple self-optimization objectives.
  • 19. The self-optimization system according to claim 18, wherein the relationships of the multiple self-optimization objectives comprise any one of or any combination of a priority relationship, a weight relationship, an arithmetic operation relationship, and a logic operation relationship.
  • 20. The self-optimization system according to claim 14, wherein the second device comprises a second processor configured to acquire the self-optimization capability of the first device.
Priority Claims (2)
Number Date Country Kind
PCT/CN2009/070934 Mar 2009 CN national
200910149932.1 Jun 2009 CN national
Parent Case Info

This application is a continuation of U.S. patent application Ser. No. 13/257,770, filed on Nov. 29, 2011, which is a National Stage of International Application No. PCT/CN2010/071143, filed Mar. 19, 2010. The International Application claims priority to Chinese Patent Application No. 2009101499321.1, filed Jun. 19, 2009 and International Application No. PCT/CN2009/070934, filed on Mar. 20, 2009. All of these applications are incorporated herein by reference.

Continuations (2)
Number Date Country
Parent 13257770 Nov 2011 US
Child 13971345 US
Parent PCT/CN2010/071143 Mar 2010 US
Child 13257770 US