WO2012071810A1

WO2012071810A1 - Method and device for storing network management performance non-granularity data rapidly

Info

Publication number: WO2012071810A1
Application number: PCT/CN2011/071195
Authority: WO
Inventors: 陈占海; 李忆岚
Original assignee: 中兴通讯股份有限公司
Priority date: 2010-11-29
Filing date: 2011-02-23
Publication date: 2012-06-07
Also published as: CN102004783B; CN102004783A

Abstract

A method and device for storing network management performance non-granularity data rapidly are disclosed. The method includes: analyzing received performance data to determine the performance object to which the performance data belong; storing the performance data into the corresponding storage area in the memory database after integration operations for the performance data have been executed according to the performance object to which the performance data belong; uploading the performance data in the memory database to the network management system database when the performance data reports that granularity is reached. The technical solution changes the original method for storing the performance data, by buffering the performance data after executing integration operation for the performance data according to the type of the performance object in the memory database; when time granularity is reached, uploading the performance data in the memory database to the system database in bulk, thereby transferring a great quantity of discrete and frequent database in-stockroom operations to the memory. Simultaneously less system resources and system time are occupied, and efficiency and stability of the system are improved.

Description

Method and device for quickly storing non-granular data of network management performance

The present invention relates to the field of communications, and in particular, to a method and apparatus for quickly storing non-granular data of network management performance. Background technique

With the rapid development of mobile communication technology, the network management system operation and maintenance center in the wireless access network

The types of network elements managed by the Operations & Maintenance Center (OMC) are more and more complicated, and the number of network elements attached to a single base station controller (BSC) is becoming larger and larger. Therefore, the performance data from the network element that needs to be processed during the OMC operation process is increasing, which causes the pressure on the OMC processing to become larger and larger. Moreover, operators are increasingly demanding the accuracy and integrity of performance data, which makes OMC put forward higher requirements for data processing.

At present, the performance data reported from the network element mainly has two ways in time: One is to collect the granularity of the whole point, that is, to send the batch to the OMC when the set granularity time set by the task arrives, such as calling and releasing the class. Performance data; The other is real-time reporting, that is, when such a service occurs, it is reported immediately, such as failure cause analysis, neighboring area switching data, such data is frequently generated, the amount of data is large, and the location of the network element occurring at the same time is not fixed. For the real-time reporting class performance data network element processing method is to generate a performance data to send a performance data to the OMC, in general, 0MC is directly called the stored procedure in the database to integrate such data into the database after the granularity, but This type of frequent warehousing involves repeated I/O operations on the hard disk, taking up large systems and database resources. Summary of the invention

The main object of the present invention is to provide a method and a device for quickly storing non-granular data of network management performance, aiming at quickly and effectively counting the network quality in a mobile communication network, and the operation thereof is simple. The invention provides a method for quickly storing non-granular data of network management performance, the method comprising the following steps:

Determining the received performance data, determining the performance object to which the performance data belongs; storing the performance data in the corresponding storage area in the in-memory database according to the performance object to which the performance data belongs;

When the performance data reporting granularity is reached, the performance data in the in-memory database is uploaded to the network management system database.

Preferably, the received performance data is parsed to determine that the performance object to which the performance data belongs is:

Parsing the received performance data to obtain time, location information and function codes of the performance data;

The performance object to which the performance data belongs is determined according to the function code.

Preferably, the foregoing performance object to which the performance data belongs is stored in the corresponding storage area in the in-memory database after the performance data is integrated into the operation, including:

Obtain primary key information of performance data;

Determining whether the primary key information already exists in the in-memory database, if the performance data is integrated and stored in a corresponding storage area in the in-memory database; otherwise, a new storage area is created in the in-memory database, and the performance data is stored in the storage area. Describe the new storage area.

Preferably, storing the performance data in a corresponding storage area in the in-memory database according to the performance object to which the performance data belongs includes:

When the storage space of the in-memory database reaches the memory space threshold set by the network management system, a system alarm signal is generated, and the performance data in the in-memory database is triggered to be uploaded to the network management system database; when the network management system is abnormally restarted, the relevant time period is read. Performance data in the internal system database to the in-memory database.

Preferably, when the performance data reporting granularity is reached, the performance data in the in-memory database is The steps to upload to the network management system database include:

When the performance data reporting granularity is reached, the performance data in the in-memory database is generated into a text file in units of performance objects;

Upload the text file to the network management system database, and delete the text file.

The invention also provides a device for quickly storing non-granular data of network management performance, the device comprising:

a performance object planning module, configured to parse the received performance data, and determine a performance object to which the performance data belongs;

a data cache module, configured to store the performance data in a corresponding storage area in the in-memory database according to the performance object to which the performance data belongs;

The data uploading module is configured to upload the performance data in the in-memory database to the network management system database when the performance data reporting granularity is reached.

Preferably, the performance object planning module includes:

a parsing unit, configured to parse the received performance data, obtain time, location information, and function code of the performance data;

And a performance object determining unit, configured to determine, according to the function code, a performance object to which the performance data belongs. Preferably, the data cache module includes:

a primary key information obtaining unit, configured to acquire primary key information of performance data;

a storage location determining unit, configured to determine whether the primary key information already exists in the in-memory database; and a storage unit, configured to: when the primary key information exists in the in-memory database, store the performance data in an in-memory database The storage area is further configured to: when the primary key information does not exist in the in-memory database, establish a new storage area in the in-memory database, and store the performance data in the new storage area.

Preferably, the foregoing storage unit is further configured to:

When the storage space of the in-memory database reaches the threshold of the memory space set by the network management system, The system alarm signal is triggered to upload the performance data in the in-memory database to the network management system database. When the network management system restarts abnormally, the non-granularity performance data in the relevant time period of the network management system database is read into the in-memory database.

Preferably, the foregoing data uploading module includes:

a data exporting unit, configured to generate, when the performance data reporting granularity is reached, a text file in a performance data unit in the performance data in the in-memory database;

a data storage unit, configured to upload the text file to a network management system database, and delete the text file.

The invention changes the storage method of the original performance data, and caches the performance data in the in-memory database according to the performance object type, and uploads the performance data cached in the in-memory database to the system database in batches when the time granularity arrives. Therefore, a large number of discrete and frequent database inbound operations are transferred to the memory. At the same time, it also occupies less system resources and system time, which can greatly alleviate the system resource occupation of the network management system and the database server, and improve the efficiency and stability of the system. BRIEF DESCRIPTION OF THE DRAWINGS FIG. 1 is a schematic flow chart of an embodiment of a method for quickly storing non-granular data of network management performance according to the present invention; FIG.

2 is a schematic flow chart showing the steps of analyzing performance data in an embodiment of the method for rapidly storing non-granular data of the network management performance of the present invention;

3 is a schematic flow chart showing the steps of determining whether the performance data is valid in an embodiment of the method for quickly storing non-granular data of the network management performance of the present invention;

4 is a schematic flowchart of a step of buffering performance data to an in-memory database in an embodiment of the method for rapidly storing non-granular data of the network management performance of the present invention;

5 is a schematic flowchart of a method for batch uploading data in an in-memory database to a network management system database in an embodiment of a method for rapidly storing non-granular data of the network management performance of the present invention;

6 is a structural diagram showing an embodiment of a device for quickly storing non-granular data of network management performance according to the present invention; Intention

Figure Ί is a schematic structural diagram of a performance object planning module in an embodiment of the apparatus for rapidly storing non-granular data of the network management performance of the present invention;

FIG. 8 is another schematic structural diagram of a performance object planning module in an embodiment of the apparatus for rapidly storing non-granular data of the network management performance of the present invention; FIG.

9 is a schematic structural diagram of a data cache module in an embodiment of a device for quickly storing non-granular data of network management performance according to the present invention;

FIG. 10 is a schematic structural diagram of a data uploading module in an embodiment of the apparatus for rapidly storing non-granular data of the network management performance of the present invention.

The implementation, functional features and advantages of the objects of the present invention will be further described in conjunction with the embodiments herein. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS The technical solutions of the present invention will be further described below in conjunction with the drawings and specific embodiments. It is understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.

BRIEF DESCRIPTION OF THE DRAWINGS Fig. 1 is a flow chart showing an embodiment of a method for quickly storing non-granular data of network management performance according to the present invention.

The method for quickly storing non-granular data in the network management performance of the embodiment includes the following steps: Step S10: Parse the received performance data to determine a performance object to which the performance data belongs;

Step S11: The performance data is integrated and stored in a corresponding storage area in the in-memory database according to the performance object to which the performance data belongs;

Step S12: When the performance data reporting granularity arrives, upload the performance data in the in-memory database to the network management system database.

This embodiment changes the storage method of the original performance data, and caches the performance data in the in-memory database according to the performance object type, and then caches the memory in the memory when the time granularity arrives. According to the performance data in the library, it is uploaded to the system database in batches, so that a large number of discrete and frequent database warehousing operations are transferred to the memory. At the same time, it also occupies less system resources and system time, which can greatly alleviate the system resource occupation of the network management system and the database server, and improve the efficiency and stability of the system.

Referring to FIG. 2, the above step S10 further includes:

Step S101: Parse the received performance data, and obtain time, location information, and function code of the performance data.

The performance data frame is received from the network element through a specific message flow mechanism, which may include a protected network interface such as Ethernet or fiber. After receiving the performance data, it parses it to obtain the time, location information and other information of the performance data, such as frame number, frame length, record length, number of records, start time, end time, system number and function. Code and so on.

Step S102: Determine, according to the function code, a performance object to which the performance data belongs.

Based on the function code obtained by parsing the performance data in step S101, a performance object or a set of performance objects to which the performance data belongs can be determined. It should be noted that when the performance data is the performance data of the failure cause class, the service object to which the performance data belongs is determined by the service code and the service type in the performance data. For example, " IX: voice drop cause object" and "PTT: switch failure cause object" all correspond to the same function code "0x45085500", when the service type in the parsed performance data is "voice drop reason", it indicates The performance data is data of "IX: Voice Drop Call Cause Object", and the service type of the parsed performance data is "PTT Target Side Enhanced Group Call Switching", "PTT Target Side Private Call Switching", "PTT Source Side Enhancement" When the group call is switched "or" on the PTT source side private call switch, the performance data indicating that the performance data is "PTT: Switch Failure Cause Object" is displayed.

Referring to FIG. 3, the foregoing step S101 and step S102 further include:

Step S103: Generate primary key information according to location and time information of the performance data; the primary key information is used as a unique identifier of the performance data, and the location and time information according to the performance data Information is generated by certain rules. The certain rule may be determined according to the specific situation, that is, the order of the position and time information, and the like, and is not limited herein.

Step S104, determining, according to the primary key information, whether the performance data is valid; if yes, executing step S102; otherwise, executing step S105;

Step S105, discarding the performance data, and returning to step S101.

After the above step S102, the method further includes:

Step S106: Integrate performance data in units of performance objects to generate performance data that can be recognized by the in-memory database.

In the foregoing step S104, the step of determining whether the performance data is valid includes:

Step A: determining whether the performance data frame is the first frame of the belonging packet, if yes, performing step A2; otherwise, performing step A3;

Querying whether there is data packet information corresponding to the primary key information in the data frame receiving hash table, if not, determining that the performance data frame is the first frame of the belonging packet; otherwise, determining that the performance data frame is not the first frame of the belonging packet .

Step A2, creating a data packet information structure, adding the performance data frame to the data packet information, adding the primary key information and the data packet information to the data frame receiving hash table, and performing step S102; Step A3, according to the primary key information Obtaining the data packet information from the data frame receiving hash table, and determining, according to the data packet information, whether the received performance data frame conflicts with the performance data frame received in the previous period, if yes, step A4 is performed; otherwise, step S102 is performed;

The packet information includes its data frame information, such as a packet number, a set start time, a set end time, and the like. Determining whether the data packet information corresponding to the received performance data frame is completely consistent with the data packet information corresponding to the performance data frame received in the previous period. If they are consistent, the received performance data frame does not conflict with the performance data frame received in the previous period; Otherwise it indicates a conflict.

Step A4, determining whether the performance data frame is a garbage frame, if yes, performing step A6; otherwise, performing step A5; According to the information such as the frame number of the received performance data frame and the start collection time, it can be determined whether the performance data frame is a data frame that has existed in the previous period, and then the performance data frame is determined to be a garbage frame; otherwise, the performance data frame is determined not to be Junk frame.

Step A6, discarding the performance data frame, and returning to step S101;

Step A5: Replace the data packet information of the current performance data frame with the data packet information of the performance data frame received in the hash table in the hash table, and perform step S102.

Referring to FIG. 4, the foregoing step S11 specifically includes:

Step S111: Obtain primary key information of performance data.

The primary key information is used as a unique identifier of the performance data frame, and is generated according to the location and time information of the performance data by certain rules. The certain rule may be determined on a case-by-case basis, that is, the order in which the position and time information are arranged, and the like, and is not limited herein. According to the analysis result of the performance data in step S10, the primary key information of the performance data can be obtained.

Step S112, determining whether the primary key information already exists in the in-memory database, if yes, executing step S113; otherwise, executing step S114;

The in-memory database sets a separate memory area for each type of performance object data, and each memory area is identified by primary key information, and the primary key information is consistent with the format of the primary key information obtained in step S111. The primary key information obtained in step S111 is compared with the primary key information in the memory area, and it is determined whether the primary key information acquired in step S111 is already present in the in-memory database.

Step S113: Store performance data in a corresponding storage area in the in-memory database;

When it is determined that the primary key information acquired in step S111 is already present in the in-memory database, the performance data is stored in a corresponding storage area in the in-memory database, for example, the data entry requiring frequent data such as "number of failures, number of handovers" in the performance data. When the number of times indicator is used, it is only necessary to accumulate the values in the storage area corresponding to the primary key information of the existing in-memory database.

Step S114: Establish a new storage area in the in-memory database, and store the performance data in the new storage area. When it is determined that the primary key information acquired in step S111 does not exist in the in-memory database, a new storage area is created in the in-memory database, the performance data is stored in the new storage area, and the primary key information of the performance data identifies the new storage. Area.

In the above step S11, in the process that the performance data is stored in the corresponding storage area of the in-memory database, the storage space of the in-memory database is monitored in real time, and the capacity of the performance data stored in the storage space of the in-memory database has reached the memory set by the network management system. If the space is wide, the system alarm signal is generated, and the performance data in the in-memory database is uploaded to the network management system database. When the network management system restarts abnormally, the performance data in the system database in the relevant time period is read into the in-memory database.

The foregoing step S 111 further includes the steps of: reading performance data of the relevant time period from the network management system database, and updating to the in-memory database. In this way, when the OMC is started, the data in the in-memory database can be kept consistent with the data in the network management system database when the OMC is restarted, thereby ensuring abnormal recovery of data.

Referring to FIG. 5, the foregoing step S12 specifically includes:

Step S121: When performance data reporting granularity is reached, generating performance data in the in-memory database into a text file in units of performance objects;

The generated text file will be named with the performance object number and performance data collection start time and stored in the temporary folder. If the text file has a duplicate name, it will be replaced directly.

Step S122: Upload the text file to the network management system database, and delete the text file. Traverse the temporary folder and upload all the performance data in the temporary folder to the network management system database in batches. During this process, some performance data may not be successfully uploaded, so text files that cannot be uploaded for performance data will be stored in the Expert Analysis folder, and then all text files in the temporary folder will be deleted.

FIG. 6 is a schematic structural diagram of an apparatus for quickly storing non-granular data of network management performance according to the present invention. The apparatus for quickly storing non-granular data in the network management performance of the embodiment includes:

The performance object planning module 10 is configured to parse the received performance data, and determine a performance object to which the performance data belongs;

The data cache module 11 is configured to store the performance data in a corresponding storage area in the in-memory database according to the performance object to which the performance data belongs;

The data uploading module 12 is configured to upload the performance data in the in-memory database to the network management system database when the performance data reporting granularity is reached.

This embodiment changes the storage method of the original performance data, and caches the performance data in the in-memory database according to the performance object type, and uploads the performance data cached in the in-memory database to the system database when the time granularity arrives. Thus, a large number of discrete and frequent database inbound operations are transferred to the memory. At the same time, it also occupies less system resources and system time, which can greatly alleviate the system resource occupation of the OMC system and the database server, and improve the efficiency and stability of the system.

Referring to FIG. 7, the foregoing performance object planning module 10 specifically includes:

The parsing unit 101 is configured to parse the received performance data, obtain time, location information, and function code of the performance data;

The performance object determining unit 102 is configured to determine, according to the function code, a performance object to which the performance data belongs.

The performance data frame is received from the network element through a specific message circulation mechanism, and the receiving interface may include a protected network interface such as Ethernet or optical fiber. After receiving the performance data, the parsing unit 101 parses the time data, the location information, and other information, such as the frame number, the frame length, the record length, the number of records, the start time, the end time, and the system. Number and function code, etc. The performance object determining unit may determine the performance object or the performance object set to which the performance data belongs according to the function code obtained by the parsing unit 101 parsing the performance data. It should be noted that when the performance data is the performance data of the failure cause class, the function code and the sex are required. The types of services in the data can be used together to determine the performance objects to which the performance data belongs. Referring to FIG. 8, the performance object planning module 10 further includes:

The primary key information generating unit 103 is configured to generate primary key information according to location and time information of the performance data;

The primary key information determining unit 104 is configured to determine, according to the primary key information, whether the performance data is valid; if yes, discard the performance data; otherwise, the performance object determining unit 102 determines the performance object to which the performance data belongs;

The performance data integration unit 105 is configured to integrate performance data in units of performance objects to generate performance data that can be recognized by the in-memory database.

The specific step of determining whether the performance data is valid in the primary key information judging unit 104 is as described in detail in step S104 of the above method.

Referring to FIG. 9, the data cache module 11 specifically includes:

a primary key information obtaining unit 111, configured to acquire primary key information of performance data;

The storage location determining unit 112 is configured to determine whether the primary key information already exists in the in-memory database;

The storage unit 113 is configured to: when the primary key information is present in the in-memory database, store the performance data in a corresponding storage area in the in-memory database; and when the primary key information does not exist in the in-memory database, A new storage area is created in the in-memory database, and the performance data is stored in the new storage area.

The in-memory database sets a separate memory area for each type of performance object data, and each memory area is identified by primary key information, and the primary key information is consistent with the format of the primary key information obtained by the primary key information obtaining unit 111. The primary key information acquired by the primary key information acquiring unit 111 is compared with the primary key information of the memory area, and it can be determined whether the primary key information acquired by the primary key information acquiring unit 111 already exists in the in-memory database.

When the storage location determining unit 112 determines that the primary key information acquired by the primary key information acquiring unit 111 has been When present in the in-memory database, the storage unit 113 stores the performance data in a corresponding storage area in the in-memory database. For example, in the performance data, as for the number of times of frequent data entry, such as the number of failures and the number of times of switching, it is only necessary to accumulate the values in the storage area corresponding to the primary key information of the existing in-memory database. When the storage location determining unit 112 determines that the primary key information acquired by the primary key information acquiring unit 111 does not exist in the in-memory database, the storage unit 113 creates a new storage area in the in-memory database, stores the performance data in the new storage area, and The primary key information of the performance data identifies the new storage area.

The above storage unit 113 is also used to:

When the storage space of the in-memory database reaches the threshold of the memory space set by the network management system, a system alarm signal is generated, and the performance data in the in-memory database is triggered to be uploaded to the network management system database; when the network management system is abnormally restarted, the network management system database is Non-granularity performance data during the relevant time period is read into the in-memory database. In order to ensure that the data in the memory database is consistent with the data in the network management system database when the network management system is restarted, the data recovery is ensured.

During the storage of the performance data in the corresponding storage area of the in-memory database, the storage unit 113 monitors the storage space of the in-memory database in real time, and the capacity of the performance data stored in the storage space of the in-memory database has reached the memory space set by the network management system. The threshold value generates a system alarm signal and triggers uploading performance data in the in-memory database to the network management system database.

Referring to FIG. 10, the data uploading module 12 specifically includes:

The data exporting unit 121 is configured to generate performance data in the in-memory database as a text file in units of performance objects when the performance data reporting granularity is reached;

The data storage unit 122 is configured to upload the text file to the network management system database, and delete the text file.

The text file generated by the data export unit 121 will be named after the performance object number and the performance data collection start time and stored in the temporary folder, if the text file has a duplicate name, then Then replace it with the overlay.

The data storage unit 122 traverses the temporary folder, and uploads all the performance data in the temporary folder to the network management system database in units of performance objects. During this process, some performance data may not be successfully uploaded, so text files that cannot be uploaded by performance data will be stored in the Expert Analysis folder, and then all text files in the temporary folder will be deleted.

The above description is only a preferred embodiment of the present invention, and is not intended to limit the scope of the patents. The equivalent structure or equivalent process transformations made by the description of the present invention and the drawings are directly or indirectly applied to other related technical fields. The same is included in the scope of patent protection of the present invention.

Claims

Claim

A method for quickly storing non-granular data of network management performance, characterized in that the method comprises the following steps:

The method for quickly storing non-granular data of network management performance according to claim 1, wherein the performance data is parsed to determine that the performance object to which the performance data belongs is:

The method for rapidly storing non-granularity data of the network management performance according to claim 2, wherein the performance data is integrated into the corresponding storage in the in-memory database according to the performance object to which the performance data belongs. The area includes:

Obtain primary key information of performance data;

The method for rapidly storing non-granular data of network management performance according to claim 3, wherein the performance data is stored in a corresponding storage area in the in-memory database according to the performance object to which the performance data belongs. :

When the storage space of the in-memory database reaches the memory space set by the network management system, The system alarm signal is generated, and the performance data in the in-memory database is triggered to be uploaded to the network management system database;

When the network management system restarts abnormally, the performance data in the system database in the relevant time period is read into the in-memory database.

The method for rapidly storing non-granular data of network management performance according to any one of claims 1 to 4, wherein, when the performance data reporting granularity is reached, the performance data in the in-memory database is uploaded to the network management system database. The steps include:

6. A device for quickly storing non-granular data of network management performance, characterized in that the device comprises:

The device for quickly storing non-granular data of the network management performance according to claim 6, wherein the performance object planning module comprises:

And a performance object determining unit, configured to determine, according to the function code, a performance object to which the performance data belongs.

The apparatus for quickly storing non-granular data of the network management performance according to claim 6, wherein the data caching module comprises: a primary key information obtaining unit, configured to acquire primary key information of performance data;

9. The apparatus of claim 8, wherein the storage unit is further configured to:

When the storage space of the in-memory database reaches the threshold of the memory storage space set by the network management system, a system alarm signal is generated, and the performance data in the in-memory database is triggered to be uploaded to the network management system database;

When the network management system restarts abnormally, the non-granularity performance data in the relevant time period of the network management system database is read into the in-memory database.

The device for quickly storing non-granular data of the network management performance according to any one of claims 6 to 9, wherein the data uploading module comprises: