CN107801197B

CN107801197B - Communication service optimization method and system

Info

Publication number: CN107801197B
Application number: CN201610803732.3A
Authority: CN
Inventors: 吴修强
Original assignee: Datang Mobile Communications Equipment Co Ltd
Current assignee: Datang Mobile Communications Equipment Co Ltd
Priority date: 2016-09-05
Filing date: 2016-09-05
Publication date: 2020-07-28
Anticipated expiration: 2036-09-05
Also published as: CN107801197A

Abstract

The invention provides a communication service optimization method and a communication service optimization system, wherein the method comprises the steps of receiving a mobile load balancing M L B optimization event, judging whether the M L B optimization event conflicts with a Mobile Robustness Optimization (MRO) or not, rejecting the M L B optimization event if the M L B optimization event conflicts with the MRO, and optimizing the mobile load balancing M L B according to the M L B optimization event if the M L B optimization event conflicts with the MRO and the M L B in the prior art.

Description

Communication service optimization method and system

Technical Field

The present invention relates to the field of communications technologies, and in particular, to a method and a system for optimizing a communication service.

Background

In current SON (Self-Organized Networks) systems, Optimization of MRO (Mobility Robustness Optimization) and M L B (Mobility L ° balancing) is usually involved, and corresponding handover and reselection parameters need to be adjusted during the Optimization process of MRO and M L B.

The M L B solves the problem of load imbalance and guarantees the maximization of network capacity, the switching is promoted by adjusting parameters, the MRO solves the switching problem of UE (User Equipment) and guarantees the QoS (Quality of Service) of a User, and the early, late or ping-pong switching is avoided by adjusting the parameters.

Disclosure of Invention

The invention provides a communication service optimization method and a communication service optimization system, which are used for solving the problem of optimization conflict existing when MRO and M L B are optimized simultaneously.

In order to solve the above problems, the present invention discloses a communication service optimization method, which comprises:

receiving a mobile load balancing M L B optimization event;

judging whether the M L B optimization event conflicts with the Mobile Robustness Optimization (MRO) or not;

if yes, rejecting the M L B optimization event;

if not, performing mobile load balancing M L B optimization according to the M L B optimization event.

The invention also discloses a communication service optimization system, which comprises:

a receiving module, configured to receive an M L B optimization event;

a judging module, configured to judge whether there is a conflict between the M L B optimization event and the mobile robustness optimization MRO;

a first execution module for rejecting the M L B optimization event if the M L B optimization event conflicts with a Mobile Robustness Optimization (MRO);

a second execution module, configured to perform mobile load balancing M L B optimization according to the M L B optimization event if the M L B optimization event does not conflict with the mobile robustness optimization MRO.

Compared with the prior art, the invention has the following advantages:

the invention discloses a communication service optimization scheme which can receive an M L B optimization event, judge whether the M L B optimization event conflicts with a Mobile Robustness Optimization (MRO), if so, reject the M L B optimization event, if not, perform mobile load balancing (M L B) optimization according to the M L B optimization event, and therefore, in the invention, based on the judgment of the M L B optimization event, when the M L B conflicts with the MRO, the MRO optimization is preferably performed, only one optimization is ensured to be performed at the same time, the problem of the conflict between the optimization of the MRO and the optimization of the M L B is avoided, the switching success rate and the communication quality are ensured, and the user experience is improved.

Drawings

Fig. 1 is a flowchart illustrating steps of a communication service optimization method according to an embodiment of the present invention;

fig. 2 is a flowchart illustrating steps of a communication service optimization method according to a second embodiment of the present invention;

fig. 3 is a flowchart illustrating steps of a method for optimizing communication services according to a third embodiment of the present invention;

FIG. 4 is a flowchart illustrating the steps of M L B optimization according to a third embodiment of the present invention;

fig. 5 is a block diagram of a communication service optimization system according to a fourth embodiment of the present invention;

fig. 6 is a block diagram of a preferred communication service optimization system in the fourth embodiment of the present invention.

Detailed Description

In order to make the aforementioned objects, features and advantages of the present invention comprehensible, embodiments accompanied with figures are described in further detail below.

Example one

Referring to fig. 1, a flowchart illustrating steps of a communication service optimization method according to a first embodiment of the present invention is shown. In this embodiment, the communication service optimization method includes:

at step 102, an M L B optimization event is received.

In general, both MRO and M L B need to adjust the corresponding handover and reselection parameters during optimization, in this embodiment, an M L B optimization event sent by the base station side may be received.

Step 104, judging whether the M L B optimization event conflicts with the Mobile Robustness Optimization (MRO) or not.

Therefore, in the embodiment, whether the M L B optimization event conflicts with the MRO can be determined according to the parameters correspondingly adjusted according to the M L B optimization event, but not limited to the parameters, wherein if the conflicts exist, the following step 106 can be executed, and if the conflicts do not exist, the following step 108 can be executed.

Step 106, rejecting the M L B optimization event.

In this embodiment, if it is determined that the M L B optimization event conflicts with the MRO, it indicates that the MRO optimization may be being performed at this time, so that the optimization of M L B may be stopped, thereby preventing the conflict between the optimization of M L B and the MRO, and ensuring that the MRO optimization may be performed normally.

And step 108, carrying out mobile load balancing M L B optimization according to the M L B optimization event.

In this embodiment, if it is determined that the M L B optimization event does not conflict with MRO, it indicates that MRO optimization is not performed at this time, so that M L B optimization can be performed according to the M L B optimization event, and normal execution of M L B optimization service is ensured.

In summary, the communication service optimization method according to this embodiment may receive an M L B optimization event, determine whether the M L B optimization event conflicts with a mobile robustness optimization MRO, if so, reject the M L B optimization event, if not, perform mobile load balancing M L B optimization according to the M L B optimization event, and as a result, in this embodiment, based on the determination of the M L B optimization event, when the M L B conflicts with the MRO, perform MRO optimization preferentially, ensure that only one type of optimization is performed at the same time, avoid the problem of conflict between the MRO and the M L B optimizations, ensure a handover success rate and communication quality, and improve user experience.

Example two

Referring to fig. 2, a flowchart illustrating a method for optimizing communication services according to a second embodiment of the present invention is shown. In this embodiment, the communication service optimization method includes:

at step 202, an M L B optimization event is received.

As mentioned above, both MRO and M L B need to adjust the corresponding handover and reselection parameters during optimization, in this embodiment, M L B optimization events sent by the base station side can be received.

Step 204, determine whether there is a conflict between the M L B optimization event and the mobile robustness optimization MRO.

In this embodiment, it may be determined, but not limited to, whether there is a conflict between the M L B optimization event and the MRO according to the value of the parameter adjusted corresponding to the M L B optimization event, wherein if there is a conflict, the following step 206 may be performed, and if there is no conflict, the following step 208 may be performed.

At step 206, the M L B optimization event is rejected.

In this embodiment, rejecting the M L B optimization event may specifically include moving the M L B optimization event into a history list, and using a first identifier to identify the M L B optimization event, where the first identifier may be used to indicate that the M L B optimization fails because of a conflict with an MRO.

And step 208, carrying out mobile load balancing M L B optimization according to the M L B optimization event.

In a preferred embodiment of the present invention, the optimization of M L B can be achieved, but not limited to, by the following means:

sub-step 2082, determining whether there is an M L B optimization event for the same cell pair in the optimized monitored event list.

In this embodiment, the following sub-step 2084 may be performed if there is no M L B optimization event for the same cell pair, and the following sub-step 2086 may be performed if there is an M L B optimization event for the same cell pair.

Substep 2084, adding the M L B optimization event to the optimized monitoring event list.

Sub-step 2086, determining the corresponding event status of the M L B optimized event in the optimized monitored events list.

In this embodiment, when it is determined that the event state corresponding to the M L B optimization event in the optimized monitoring event list is the optimizing state, the M L B optimization event may be directly discarded, and when it is determined that the event state corresponding to the M L B optimization event in the optimized monitoring event list is the pending state, the original event corresponding to the M L B optimization event in the optimized monitoring event list may be deleted, and the M L B optimization event may be added to the optimized monitoring event list.

Preferably, when the M L B optimization event is added to the optimized monitoring event list, the adding may specifically include adding at least one of a source cell, a target cell, an event type, an optimized recommendation value, and reporting time information corresponding to the M L B optimization event to the optimized monitoring event list.

In another preferred embodiment of this embodiment, referring to fig. 3, a flowchart of steps of another communication service optimization method in the third embodiment of the present invention is shown.

Preferably, the step 208 may specifically include:

and a substep 3022, obtaining source cell information and target cell information corresponding to the M L B optimization event.

For example, cell information of a source cell a and a target cell B reported by the base station side may be obtained.

And a substep 3024 of querying whether a neighboring cell relation record of the cell pair exists according to the source cell information and the target cell information.

In this embodiment, the neighbor relation record may include: the neighbor relation record from the source cell A to the target cell B and the neighbor relation record from the target cell B to the source cell A. If there is no neighbor relation record of the cell pair, the following sub-step 3026 may be performed. If there is a neighbor relation record of the cell pair, the following step 3028 may be performed.

Sub-step 3026, moving the M L B optimization event into a history list and identifying the M L B optimization event using a second identification.

In this embodiment, the second identifier may be used to indicate that M L B fails in optimization, where the failure is a failure in neighbor relation lookup.

Substep 3028, respectively storing the cell individual offset in the neighbor cell relation record and the offset current value of the neighbor cell to the serving cell during reselection.

In this embodiment, the cell individual offset in the stored neighboring cell relation record and the offset current value of the neighboring cell to the serving cell during reselection may include:

cell individual offset from a source cell a to a target cell B;

reselection offset from source cell a to target cell B;

cell individual offset from target cell B to source cell B;

the target cell B to source cell BD reselection offset.

And a substep 30210, optimizing the individual cell offset and the current offset value of the serving cell from the neighboring cell during reselection respectively according to the optimization parameters corresponding to the M L B optimization event, and recording the optimization result.

Sub-step 30212, after receiving the parameter optimization response message on the base station side, moving the M L B optimization event into a history list.

In this embodiment, when the parameter optimization response message is a successful response, the cell individual offset before parameter optimization and the offset current value of the neighboring cell to the serving cell during reselection and the optimization result may be recorded, respectively, and a third identifier may be used to identify the M L B optimization event, where the third identifier is used to indicate that the M L B optimization is successful, when the parameter optimization response message is a failed response, the cell individual offset before parameter optimization and the offset current value of the neighboring cell to the serving cell during reselection and the parameter value of a successful part in the optimization result may be recorded, respectively, and a fourth identifier is used to identify the M L B optimization event, where the fourth identifier is used to indicate that the M L B optimization is failed and the failure reason is that the parameter optimization fails.

EXAMPLE III

With reference to the foregoing embodiments, this embodiment describes the communication service optimization method in detail by using a specific example of M L B optimization.

Referring to fig. 4, a schematic diagram illustrating a procedure flow of M L B optimization in a third embodiment of the present invention is shown, in this embodiment, the M L B optimization procedure may specifically be as follows:

and step 402, the SON server receives an M L B optimization event reported by the base station side.

Step 404, determine whether there is a conflict between the M L B optimization event and the MRO.

In this embodiment, if it is determined that there is a conflict with the MRO, step 406 may be executed; if it is determined that there is no conflict with the MRO, step 408 may be performed.

Step 406, move the M L B optimization event into a history list, and record the failure reason as a conflict with the MRO.

Step 408, determine whether there is an M L B optimization event of the same cell pair in the optimized monitoring event list.

In this embodiment, step 410 may be performed if there is no M L B optimization event for the same cell pair in the optimization monitoring event list, otherwise, step 416 may be performed.

Step 410, determining the event status corresponding to the M L B optimization event in the optimized monitoring event list.

In this embodiment, if it is determined that the event status corresponding to the M L B optimized event in the optimized monitoring event list is "in-optimization" status, step 412 may be executed, and if it is determined that the event status corresponding to the M L B optimized event in the optimized monitoring event list is "to-be-processed" status, step 414 may be executed.

At step 412, the M L B optimization event is discarded.

Step 414, deleting the original event corresponding to the M L B optimization event in the optimization monitoring event list.

Step 416, add the M L B optimization event to the optimized monitoring event list.

In step 418, the optimization mode of M L B is determined.

In this embodiment, the optimization mode of M L B may include a free mode and a controlled mode, wherein the following step 420 may be performed when the optimization mode of M L B is determined to be the free mode, and the following step 422 may be performed when the optimization mode of M L B is determined to be the controlled mode.

In step 420, the event status is set to "optimizing".

In the free mode, the SON server can record a source cell, a target cell, an event type, an optimization suggestion value and reporting time information into the optimization monitoring event list, set an event state as 'optimization', and not allow manual operation, and further process an M L B optimization event in the optimization monitoring event list, wherein the M L B optimization event in the optimization monitoring event list is inquired about adjacent cell relation records (two records of A- > B and B- > A) of a cell pair according to the source cell (such as the cell A) and the target cell (such as the cell B) information reported by a base station, if the inquiry fails, the M L B optimization event is moved into a history list, and the event state is set as 'optimization failure', the failure is caused by the search failure of the adjacent cell relation, and if the inquiry succeeds, cell offset in the two adjacent cell relation records of A- > B and B- > A and the current value (cell offset) of the adjacent cell to service cell during reselection are obtained and stored:

cell individual offset for cellAdjCellQoffset _ A2B A- > B

cell reselection offset for celladjcellindinavialoffset _ A2B a- > B

cell individual offset for cellAdjCellQoffset _ B2A B- > A

cell reselection offset for celladjcellinduvidalOffset _ B2A A- > B

Issuing a parameter optimization command according to the parameter adjustment deviation value delta L carried in the M L B optimization event, and recording two modified pairs of parameter values:

cellAdjCellQOffset_A2B_new＝cellAdjCellQOffset_A2B+ΔL

cellAdjCellIndividualOffset_A2B_new＝cellAdjCellIndividualOffset_A2B-ΔL

cellAdjCellQOffset_B2A_new＝cellAdjCellQOffset_B2A-ΔL

cellAdjCellIndividualOffset_B2A_new＝cellAdjCellIndividualOffset_B2A+ΔL

when the parameter optimization response message indicates success, 8 parameter values before and after optimization in the two directions of A- > B and B- > A can be recorded, the event state is optimization success, and when the parameter optimization response message indicates failure, 4 parameter values before optimization, the parameter values (if existing) after optimization success and the failure reason can be recorded, and the event state is optimization failure.

In step 422, the event status is set to "pending".

In the controlled mode, the SON server may record the source cell, the target cell, the event type, the optimization suggested value, and the reporting time information into the optimization monitoring event list, and set the event state to "pending", allowing manual operation parameter optimization.

Step 424, determine if the user confirms to optimize.

In this embodiment, when the user selects a "pending" event in a certain controlled mode and optimizes the right key operation parameter, the parameter value before optimization by the cell and the parameter adjustment offset value Δ L reported in the base station event may be displayed.

After the user confirms the optimization, step 402 may be executed to complete the optimization process of the parameters in the free mode.

In addition, the method can be realized through a software mode based on a network management side, and is simple and easy to operate.

It should be noted that the foregoing method embodiments are described as a series of acts or combinations for simplicity in explanation, but it should be understood by those skilled in the art that the present invention is not limited by the order of acts or acts described, as some steps may occur in other orders or concurrently in accordance with the invention. Further, those skilled in the art will appreciate that the embodiments described in the specification are presently preferred and that no particular act is required to implement the invention.

Example four

Based on the same inventive concept as the above method embodiments, referring to fig. 5, a block diagram of a communication service optimization system in a fourth embodiment of the present invention is shown. In this embodiment, the communication service optimization system includes:

a receiving module 502, configured to receive an M L B optimization event.

A determining module 504, configured to determine whether the M L B optimization event conflicts with the mobile robustness optimization MRO.

A first executing module 506, configured to reject the M L B optimization event if the M L B optimization event conflicts with the mobile robustness optimization MRO.

A second performing module 508, configured to perform mobile load balancing M L B optimization according to the M L B optimization event if the M L B optimization event does not conflict with the mobile robustness optimization MRO.

It can be seen that, in this embodiment, based on the judgment of the M L B optimization event, when M L B conflicts with MRO, MRO optimization is preferably performed, and it is ensured that only one kind of optimization is performed at the same time, so that the problem of conflict between MRO and M L B optimization is avoided, the handover success rate and communication quality are ensured, and the user experience is improved.

In a preferred embodiment of this embodiment, referring to fig. 5, a block diagram of a preferred communication service optimization system in a fourth embodiment of the present invention is shown.

Preferably, the first executing module 506 is specifically configured to, if the M L B optimization event conflicts with the mobile robustness optimization MRO, move the M L B optimization event into a history list, and identify the M L B optimization event by using a first identifier, where the first identifier is used to indicate that the M L B optimization fails and the failure reason is that the M L B optimization fails because of conflicting with the MRO.

In a preferred embodiment, the second performing module 508 may specifically include a determining submodule 5082, configured to determine whether an M L B optimization event of the same cell pair exists in an optimized monitoring event list, an adding submodule 5084, configured to add the M L B optimization event to the optimized monitoring event list if an M L B optimization event of the same cell pair does not exist, a determining submodule 5086, configured to determine an event state of the M L B optimization event in the optimized monitoring event list if an M L B optimization event of the same cell pair exists, and a discarding submodule 5088, configured to discard the M L B optimization event when it is determined that the event state of the M L B optimization event in the optimized monitoring event list is an optimized state, wherein the adding submodule 5084 may further be configured to, when it is determined that the event state of the M L B optimization event in the optimized monitoring event list is a pending state, delete the M L B optimization event in the optimized monitoring event list, and delete the M L optimization event.

Further preferably, when the M L B optimization event is added to the optimized monitoring event list, the adding sub-module 5084 may specifically include adding at least one of a source cell, a target cell, an event type, an optimized suggested value, and reporting time information corresponding to the M L B optimization event to the optimized monitoring event list.

In another preferred embodiment, the second performing module 508 may specifically include an obtaining sub-module 50810, configured to obtain source cell information and target cell information corresponding to the M L B optimization event, an inquiring sub-module 50812, configured to inquire whether a neighbor relation record of a cell pair exists according to the source cell information and the target cell information, a moving sub-module 50814, configured to move the M L B optimization event into a history list if the neighbor relation record of the cell pair does not exist, and identify the M L B optimization event by using a second identifier, where the second identifier is used to indicate that M L B optimization fails due to failure of neighbor relation search, and a storing sub-module 50816, configured to store a cell individual offset in the neighbor relation record and an offset current value of a neighbor cell to a serving cell during reselection, respectively, if the neighbor relation record of the cell pair exists, store the cell individual offset of the neighbor cell pair in the neighbor relation record and the offset current value of the neighbor cell to the serving cell during reselection, an optimizing sub-module 50818, configured to move the optimization result of the neighbor cell pair offset to the optimization sub-module 50814, and send the optimization event to the optimization sub-module 50L, where the optimization sub-module may further receive the optimization event, and send the optimization message, wherein the optimization sub-50L.

Further preferably, when the moving-in submodule 50814 receives a parameter optimization response message from the base station side, and moves the M L B optimization event into the history list, the moving-in submodule may specifically include, when the parameter optimization response message is a successful response, recording current offset values of the serving cell from the neighboring cell before parameter optimization and during reselection, and the optimization result, and identifying the M L B optimization event by using a third identifier, where the third identifier is used to indicate that M L B optimization is successful, when the parameter optimization response message is a failed response, recording current offset values of the serving cell from the neighboring cell before parameter optimization and during reselection, and parameter values of a successful optimization part in the optimization result, and identifying the M L B optimization event by using a fourth identifier, where the fourth identifier is used to indicate that M L B optimization fails, and the failure cause is parameter optimization failure.

To sum up, the communication service optimization system according to this embodiment may receive an M L B optimization event, determine whether the M L B optimization event conflicts with a mobility robustness optimization MRO, if so, reject the M L B optimization event, and if not, perform mobility load balancing M L B optimization according to the M L B optimization event.

For the device embodiment, since it is basically similar to the method embodiment, the description is simple, and for the relevant points, refer to the partial description of the method embodiment.

The embodiments in the present specification are described in a progressive manner, each embodiment focuses on differences from other embodiments, and the same and similar parts among the embodiments are referred to each other.

The method and system for optimizing communication service provided by the present invention are described in detail above, and a specific example is applied in the text to explain the principle and the implementation of the present invention, and the description of the above embodiment is only used to help understanding the method and the core idea of the present invention; meanwhile, for a person skilled in the art, according to the idea of the present invention, there may be variations in the specific embodiments and the application scope, and in summary, the content of the present specification should not be construed as a limitation to the present invention.

Claims

1. A method for optimizing communication traffic, comprising:

receiving a mobile load balancing M L B optimization event;

if yes, rejecting the M L B optimization event;

if not, performing mobile load balancing M L B optimization according to the M L B optimization event;

wherein the performing of the mobile load balancing M L B optimization according to the M L B optimization event comprises:

judging whether M L B optimization events of the same cell pair exist in the optimization monitoring event list;

if not, adding the M L B optimization event to the optimized monitoring event list;

if yes, determining the corresponding event state of the M L B optimization event in the optimization monitoring event list;

when the event state corresponding to the M L B optimization event in the optimization monitoring event list is determined to be an optimizing state, discarding the M L B optimization event;

when the event state corresponding to the M L B optimization event in the optimization monitoring event list is determined to be a pending state, deleting an original event corresponding to the M L B optimization event in the optimization monitoring event list, and adding the M L B optimization event to the optimization monitoring event list.

2. The method of claim 1, wherein said rejecting the M L B optimization event comprises:

and moving the M L B optimization event into a history list, and identifying the M L B optimization event by using a first identifier, wherein the first identifier is used for indicating that the M L B optimization fails because of conflict with MRO.

3. The method of claim 1, wherein adding the M L B optimization event to the list of optimization monitoring events comprises:

and adding at least one of a source cell, a target cell, an event type, an optimization suggestion value and reporting time information corresponding to the M L B optimization event into the optimization monitoring event list.

4. The method of claim 1, wherein the mobile load balancing M L B optimization according to the M L B optimization event further comprises:

acquiring source cell information and target cell information corresponding to the M L B optimization event;

inquiring whether a neighbor relation record of a cell pair exists or not according to the source cell information and the target cell information;

if the M L B optimization event does not exist, moving the M L B optimization event into a history list, and identifying the M L B optimization event by using a second identification, wherein the second identification is used for indicating that the M L B optimization fails, and the failure reason is that the neighbor relation search fails;

if the current offset exists, the individual offset of the cell in the adjacent cell relation record and the offset current value of the adjacent cell to the service cell during reselection are respectively stored;

respectively optimizing the individual cell offset and the offset current value of the adjacent cell to the serving cell during reselection according to the optimization parameters corresponding to the M L B optimization event, and recording the optimization result;

and after receiving a parameter optimization response message at the base station side, moving the M L B optimization event into a history list.

5. The method of claim 4, wherein moving the M L B optimization event into a history list after receiving the parameter optimization response message from the base station comprises:

when the parameter optimization response message is a successful response, recording the individual offset of the cell before parameter optimization and the offset current value of the adjacent cell to the serving cell during reselection and the optimization result respectively, and using a third identifier to identify the M L B optimization event, wherein the third identifier is used for indicating that the M L B optimization is successful;

and when the parameter optimization response message is a failure response, respectively recording the individual offset of the cell before parameter optimization and the offset current value of the adjacent cell to the serving cell during reselection, and the parameter value of the successful optimization part in the optimization result, and identifying the M L B optimization event by using a fourth identifier, wherein the fourth identifier is used for indicating that the M L B optimization fails, and the failure reason is the failure of the parameter optimization.

6. A communication traffic optimization system, comprising:

a receiving module, configured to receive an M L B optimization event;

a second execution module, configured to perform mobile load balancing M L B optimization according to the M L B optimization event if the M L B optimization event does not conflict with the mobile robustness optimization MRO;

the second execution module includes:

the judging submodule is used for judging whether the M L B optimization events of the same cell pair exist in the optimization monitoring event list or not;

an adding submodule, configured to add the M L B optimization event to the optimized monitoring event list if there is no M L B optimization event of the same cell pair;

a determining submodule, configured to determine, if there is an M L B optimization event of the same cell pair, an event state corresponding to the M L B optimization event in the optimized monitoring event list;

a discard submodule, configured to discard the M L B optimization event when it is determined that the event status corresponding to the M L B optimization event in the optimization monitoring event list is an optimization status;

the adding sub-module is further configured to delete an original event in the optimized monitoring event list corresponding to the M L B optimized event when it is determined that the event state of the M L B optimized event in the optimized monitoring event list is a pending state, and add the M L B optimized event to the optimized monitoring event list.

7. The system of claim 6, wherein the first execution module is configured to move the M L B optimization event into a history list and identify the M L B optimization event using a first identifier if the M L B optimization event conflicts with a Mobile Robustness Optimization (MRO), and wherein the first identifier is used to indicate that the M L B optimization fails due to a conflict with the MRO.

8. The system of claim 6, wherein the add submodule, when adding the M L B optimization event to the list of optimization monitoring events, comprises:

9. The system of claim 6, wherein the second execution module further comprises:

the obtaining submodule is used for obtaining source cell information and target cell information corresponding to the M L B optimization event;

the query submodule is used for querying whether the neighbor relation record of the cell pair exists or not according to the source cell information and the target cell information;

the immigration submodule is used for moving the M L B optimization event into a history list if no adjacent cell relation record of the cell pair exists, and identifying the M L B optimization event by using a second identifier, wherein the second identifier is used for indicating that the M L B optimization fails, and the failure reason is that the adjacent cell relation search fails;

the storage submodule is used for respectively storing the individual cell offset in the neighbor cell relation record and the offset current value of the neighbor cell to the service cell during reselection if the neighbor cell relation record of the cell pair exists;

the optimization submodule is used for respectively optimizing the individual offset of the cell and the offset current value of the adjacent cell to the serving cell during reselection according to the optimization parameters corresponding to the M L B optimization event, and recording an optimization result;

the moving-in submodule is further used for moving the M L B optimization event into a history list after receiving a parameter optimization response message of the base station side.

10. The system of claim 9, wherein the move-in submodule, when moving the M L B optimization event into the history list after receiving the parameter optimization response message from the base station, comprises: