JP4131863B2 - Station data management apparatus and consistency check method - Google Patents

Description

  The present invention relates to a station data management apparatus that checks station data consistency when creating and managing station data to be input to a network element (NE), and a station data consistency check method.

A wide variety of network equipment (NE) exists in a mobile communication network. In order for the NE to perform call processing normally, station data for setting various information such as setting the identification number of the own station and setting the identification number of the connection destination is required.
The equipment design system creates these individual station data, and also inputs the created station data into the NE. The NE-compliant operation system (NE-OSS (Network Element-Operations Support) System)) is used to manage the original station data.

In the facility design system in the network so far,
・ Consistency check of station data using database ・ Consistency check using interpreter language to respond flexibly to changes in specifications of consistency check conditions ・ Station data in station data original management using database It has supported creation and input work.
As described above, in the conventional technology, since the database is used, when the consistency check condition becomes complicated, the processing capacity of the database becomes a bottleneck, and the processing time is significantly increased. was there.
In addition, since the consistency check condition is described in an interpreter language, there is a problem that the processing time of syntax analysis may become a bottleneck when the check condition is complicated.

In addition, since a database is used, there is a problem that it is difficult to perform data maintenance. That is, there is a problem that even if data stored in the database is displayed, it is difficult to visually understand the data contents, and it is difficult to edit data unless a dedicated editor is prepared.
In addition, since the database is used, the development cost at the time of the specification change becomes high, and there are problems such as unexpected impact on the application side due to the database development or support termination.

On the other hand, as a technology related to checking, Patent Document 1 describes a technology content in which check contents for an input item are patterned and stored in a database, and an input check is performed according to the check pattern. According to this technique, when the check pattern is changed, only the check pattern can be changed without changing the program itself, so that the check specification can be quickly changed.
Japanese Patent Laid-Open No. 06-274389

However, even in the technique described in Patent Document 1, since the database is used similarly to the equipment design system, the above-described drawbacks cannot be solved. The facility design system is a large-scale system, and the consistency check of station data to be input to the NE is different from the input check in Patent Document 1 in the technical field and preconditions in the first place.
With the rapid increase in mobile communication service subscribers in recent years and the advancement of mobile communication technology, the number of NEs has increased, and the specifications of the consistency check pattern of station data have not changed. Under such circumstances, there is a need for a mechanism that can be easily maintained when the specification change of the consistency check occurs.
The present invention has been made in view of the above problems, and provides a station data management apparatus and a consistency check method that can easily cope with a specification change of consistency check for station data to be input to an NE. The purpose is to provide.

In order to solve the above-mentioned problem, the invention described in claim 1 is the station data management apparatus for checking the consistency of the station data to be input to the network element, in which the given station data and the original station data are extracting the difference, and poured station data creation means for creating poured station data based on the extracted difference, the integrity check pattern to be performed with respect to the input station data created by the closing station data creating means Check pattern storage means for storing check pattern information to be expressed as a text file, check engine storage means for storing a check engine which is a program for analyzing check pattern information stored in the check pattern storage means, and the check Check pattern information stored in pattern storage means and previous Based on the check engine that is stored in the check engine storage means, to provide station data management apparatus characterized by comprising, a consistency check execution means for performing an integrity check of the input station data.

According to this configuration, since the station data management apparatus stores the check engine and check pattern information separately, it is only necessary to change the check pattern information when the specification change of the consistency check occurs, and the specification can be easily performed. Can respond to changes. Further, since the check pattern information is a text file, it is easy to understand what kind of check is visually performed, it is easy to edit, and maintenance efficiency is high.
In addition, since the consistency check is performed on the input station data created based on the difference between the given station data and the original station data, the data amount of the data subjected to the consistency check can be reduced. .

According to a second aspect of the present invention, in the station data management apparatus according to the first aspect, the check pattern information is described in XML (eXtensible Markup Language).
According to this configuration, it is possible to visually grasp the check pattern based on the XML syntax, and it is easy to understand what kind of consistency check is being performed.
According to a third aspect of the present invention, in the station data management apparatus according to the first or second aspect, the check pattern information includes a definition of a check condition for each pattern of the consistency check. And
According to this configuration, since the definition of the check condition is described for each of the consistency check patterns, it is possible to immediately grasp what kind of consistency check is being performed, and the maintainability is high.

  The invention described in claim 4 is the consistency check device according to any one of claims 1 to 3, further comprising check component storage means for storing a check component for executing the consistency check, In the check pattern information, identification information of a check component to be called is described, and the consistency check execution unit is described in the station data by starting a check engine stored in the check engine storage unit. A pattern of consistency check to be performed on the data contents being acquired, check pattern information representing the determined pattern of consistency check is acquired from the check pattern storage means, and the acquired check pattern information Based on the check component identification information described, the check component storage means stores the information. And they said to call the check parts that are.

  According to this configuration, it is easy to perform maintenance of the check pattern information by separating the check component that actually executes the consistency check from the check pattern information that is likely to change specifications. In addition, the check pattern information can describe only the definition of check conditions for what kind of check is performed, and it is easy to visually understand the check contents.

The invention according to claim 5 extracts a difference between given station data and original station data in a consistency check method in which the station data management apparatus checks the consistency of station data to be input to a network element. and, a charged point data generating step of generating a charged point data based on the extracted difference, the check pattern information indicating a consistency check pattern of the input station data created in the closing station data creation step as a text file A check pattern storing step for storing, a check engine storing step for storing a check engine which is a program for analyzing the check pattern information stored in the check pattern information storing step, and a check stored in the check engine storing step Engine A check engine startup step of starting the by activated check engine in the check engine starting step, an analysis step of analyzing the check pattern information stored in the check pattern storing step,
There is provided a consistency check method comprising: a consistency check step for performing consistency check of the input station data based on a result analyzed in the analysis step.
The operation and effect of this method are the same as in the first aspect.

  According to the present invention, the station data management device stores the check engine and the text-format check pattern information separately, so it is only necessary to change the check pattern information when a specification change of the consistency check occurs. Can easily cope with specification changes. Further, since the check pattern information is a text file, it is easy to understand what kind of check is visually performed, it is easy to edit, and maintenance efficiency is high.

Next, embodiments for carrying out the present invention will be described with reference to the drawings. In each drawing referred to in the following description, the same reference numerals are given to the same parts as in the other drawings.
[1. Constitution]
FIG. 1 is a diagram showing a configuration of an equipment design system 1 according to an embodiment of the present invention. As shown in FIG. 1, the facility design system 1 includes a station data creation device 20 and a station data management device 30. A terminal 10 operated by a user of the facility design system 1, a business management system 40, an NE-OSS 50, and an NE 60 are connected to the facility design system 1 via a communication network.

  Next, the equipment design system 1 will be described. The facility design system 1 creates station data necessary for the NE 60 to perform normal processing and manages the original data of the station data. The facility design system 1 employs a distributed configuration for load distribution. In the present embodiment, the facility design system 1 includes a station data creation device 20 and a station data management device 30. In addition, such a structure is only one embodiment. For example, the facility design system 1 may be configured by a plurality of devices having the same function, and creates station data for input. The apparatus may be composed of an apparatus, an apparatus for checking station data consistency, and an apparatus for managing station data originals.

The station data management device 30 provided in the facility design system 1 is a database server that manages the original station data as an XML file (original XML file). Further, the station data management apparatus 30 creates and manages a new version of the original XML file based on the difference XML file generated by the input of the user of the facility design system 1.
Next, the configuration of the station data creation device 20 will be described. The station data creation device 20 exchanges data via a communication network with a CPU (Central Processing Unit) that controls the entire device, a storage unit including a ROM (Read Only Memory), a RAM (Random Access Memory), and a hard disk. It has a communication interface to control.

  Various XML files and programs are stored in the storage unit of the station data creation device 20. For example, the storage unit of the station data creation device 20 has a plurality of control XML files for generating NE60 input station data from data input by the user of the facility design system 1 and a plurality of consistency check patterns. The described check condition XML file is stored in advance as a master file. Various transaction files are stored in the storage unit of the station data creation device 20. In addition, the storage unit of the station data creation device 20 includes a program for creating various XML files such as a difference XML file and an input station data XML file, and a program for checking the consistency of the input station data XML file. The engine is memorized.

The functions shown in FIG. 2 are realized in the station data creation apparatus 20 by these hardware and software included in the station data creation apparatus 20. As shown in the figure, the station data creation device 20 includes a difference station data creation unit 21, an input station data creation unit 22, a check pattern storage unit 23, a check engine storage unit 24, and a consistency check execution unit 26. And.
The difference station data creation unit 21 compares the original XML file acquired from the station data management device 30 with the user XML file transmitted from the terminal 10 by executing a program for creating difference station data. A portion where the user XML file is different from the original XML file is extracted. Then, the difference station data creation unit 21 creates a difference XML file from the extracted portion.

The station data creation unit 22 performs a station data creation process for creating a station data XML file based on the difference XML file and the control XML file.
The station data creation process according to the present embodiment will be described in detail with reference to FIG. 3. First, the input station data creation unit 22 searches the attribute updateflg from the description of the difference XML file (step S1). The station data creation unit 22 searches the control XML file for an attribute trigger value that is the same as the attribute updateflg value described in the difference XML file (step S2). When all the values of the attribute name enclosed in the item tag of the difference XML file and the configuration of the value of the attribute commandscr of the control XML file match, the input station data creation unit 22 has, for example, the format shown in FIG. A station data XML file is created.

The check pattern storage unit 23 stores, as a text file, check pattern information representing a pattern of consistency check performed on the station data.
In this embodiment, the check pattern information is described in the XML format. FIG. 5 shows a format of a check condition XML file as an example of check pattern information. As shown in the drawing, in the check condition XML file, a check pattern ID for identifying a check pattern and a consistency check condition definition corresponding to the check pattern ID are described for each of a plurality of check patterns. Since a document written using XML is text data, it can be read normally by a human using a text editor and can also be edited. Thus, by describing for each check pattern, it is easy to understand and the maintainability is improved.

The consistency check pattern includes one or a plurality of combination patterns such as a duplication check, a digit number check, a range check, a presence check, a number check, and an IP address check.
The description format of the check pattern information is not limited to the XML format, and any text format that is easy for humans to understand and edit can be used.
The check engine storage unit 24 includes a check engine stored in the hard disk device. Here, the check engine is a program for executing a consistency check of station data in accordance with the description of the check condition XML file stored in the check pattern storage unit 23. The program is described in, for example, Java (registered trademark). Thus, maintainability is improved by designing the check engine and the check pattern separately.

  The check component storage unit 25 includes check components stored in the hard disk device. Here, the check component is a program module for actually executing each consistency check. The program module is described in, for example, Java (registered trademark). Check parts include check parts that have been made into parts in the minimum check content unit, such as duplicate check parts and range check parts.

The consistency check execution unit 26 checks the consistency of the input station data XML file based on the check condition XML file stored in the check pattern storage unit 23 and the check engine stored in the check engine storage unit 24. Execute. Here, the check execution process executed in the consistency check execution unit 26 will be described in detail with reference to FIG. First, the CPU of the station data creation device 20 starts the check engine stored in the check engine storage unit 24, thereby analyzing the input station data XML file. Then, the CPU specifies the data contents to be checked from the contents described in the input station data XML file, and determines the consistency check pattern to be executed for the data contents (step S11). The CPU determines a check pattern ID corresponding to the determined consistency check pattern based on a correspondence table between the check pattern ID and the consistency check pattern previously held in the storage unit. The CPU retrieves the condition definition identified by the determined check pattern ID from the check condition XML file, and acquires the corresponding condition definition (step S12). The CPU analyzes the acquired condition definition. As a result of analysis, it is necessary to compare the data content described in the input station data XML file with the data content described in the original XML file in order to perform data relevance check (parent-child relationship check etc.). In that case, the CPU reads necessary data from the original XML file (step S13).
Based on the identification information and parameters of the check component described in the condition definition, the CPU calls the check component stored in the check component storage unit 25 and performs a consistency check (step S14). The CPU outputs the check result to a check result file (step S15).

[2. Operation]
Next, the operation in the above configuration will be described with reference to FIG.
As a premise, it is assumed that the check condition XML file stored in the check pattern storage unit 23 describes the condition definition with the check pattern ID “001” shown in FIG. Further, it is assumed that a correspondence table indicating that the check pattern ID including the condition definition of the numerical range check and the IP address check is “001” is stored in the storage unit of the station data creation device 20 in advance. .

First, the user of the facility design system 1 selects the NE 60 for which station data is to be created on the terminal 10 (step S21). Thereby, the terminal 10 notifies the equipment design system 1 of the selected NE 60.
Upon receiving the notification from the terminal 10, the station data creation apparatus 20 of the facility design system 1 copies the original XML file for the selected NE 60 from the original XML file managed by the station data management apparatus 30 ( Step S22). Then, the station data creation device 20 transmits the copied original XML file to the terminal 10 (step S23).

The terminal 10 displays the original XML file received from the station data creation device 20 on the display.
The user of the facility design system 1 edits the original XML file displayed on the display and creates station data (step S24). Since the data displayed on the display is in a text format (XML language), the user can edit the data with an ordinary editor. In this operation example, it is assumed that the user edits station data for setting an IP address. After editing is completed, the user inputs completion of station data creation. As a result, the terminal 10 transmits the station data created by the user (hereinafter referred to as “user XML file”) to the equipment design system 1 (step S25).

The difference station data creation unit 21 of the station data creation device 20 creates a difference XML file based on the original XML file and the user XML file received from the terminal 10 (step S26).
The station data creation unit 22 creates the station data XML file shown in FIG. 4 based on the user XML file and the control XML file (step S27).

  The consistency check execution unit 26 performs a consistency check on the data contents described in the input station data XML file (step S28). Specifically, the consistency check execution unit 26 analyzes the input station data XML file shown in FIG. 4 and, based on the value of the attribute “commamdscr” included in the input station data XML file, the consistency check pattern And the check pattern ID corresponding to the determined check pattern is determined. In this operation example, since the numerical value and the IP address are described as the value of “commamdscr”, the consistency check execution unit 26 determines that the numerical value range check and the IP address check need to be performed. Then, the consistency check execution unit 26 determines that the check pattern ID corresponding to the check content is “001” based on the correspondence table stored in advance in the storage unit. The consistency check execution unit 26 searches the condition definition identified by the check pattern ID “001” shown in FIG. 7 from the check condition XML file stored in the check pattern storage unit 23.

  The consistency check execution unit 26 interprets the description of the check condition XML file shown in FIG. 7 and calls the corresponding check component from the check component storage unit 25 to check the consistency. Specifically, in this operation example, the consistency check execution unit 26 calls the check component based on the description content in the Condition tag. First, in the description of D41 shown in FIG. 7, since “1 ^ 512” is described in the Condition tag, the first parameter of cre_apn is called by calling the range check component stored in the check component storage unit 25. It is checked whether or not the value “1” is in the range of 1 to 52.

Next, also in the description of D42, since “0 ^ 255” and “0 ^ 30” are described in the Condition tag, the consistency check execution unit 26 is stored in the check component storage unit 25. The range check component is called to check whether each value of the second parameter value “192.168.10.8/30” of cre_apn is within the range.
Next, also in the description of D43, since “0 ^ 255” is described in the Condition tag, the consistency check execution unit 26 calls the range check component stored in the check component storage unit 25, and It is checked whether or not each value of the third parameter value “192.168.10.8” of cre_apn is in the range of 0 to 255.

  Next, in the description of D44, since “$ lp = 1” is described in the Condition tag, the consistency check execution unit 26 is stored in the check component storage unit 25 in this operation example. The IP address check component is called to check whether the third parameter value “192.168.10.8” of cre_apn is within the band of the second parameter value “192.168.10.8/30”.

After the check is completed, the consistency check execution unit 26 outputs the comparison result to the check result XML file and calls the check part, executes the check until all the checks on the check target data included in the input station data XML file are completed, and Repeat the result output.
After all the checks are completed, the station data creation device 20 transmits a message to the terminal 10 that the consistency check has been completed. If there is no problem in consistency, the station data creation apparatus 20 passes the input station data XML file to the station data management apparatus 30 in order to register the input station data XML file as data waiting for input to the NE 60 (step S29). On the other hand, if there is a problem with consistency, the station data creation device 20 transmits a message to that effect to the terminal 10 and prompts the user of the facility design system 1 to re-edit the data.

The station data management apparatus 30 manages the input station data XML file for which the consistency check has been completed as station data waiting for input to the NE 60.
The business management system 40 schedules the station data input business, and when the input time has come, input the input station data XML file transferred from the station data management apparatus 30 (step S30) to the NE 60 via the NE-OSS 50. (Step S31).

  The station data management apparatus 30 of the facility design system 1 receives a notification of the station data input result from the business management system 40 to the NE 60 (step S32). If the notified input result indicates normality, the station data management device 30 converts the data into an original (step S33) and stores it as the latest version of the original XML file. Subsequent station data creation work is performed based on the latest version of the original XML file. On the other hand, if the input result indicates an abnormality, the facility design system 1 notifies the terminal 10 to that effect and prompts the user of the facility design system 1 to reconfirm the station data.

As described above, the facility design system 1 stores and manages the separately designed check engine and check condition XML file, so that the check condition XML file is changed when the specification change of the consistency check occurs. It is only necessary to deal with the specification change. Also, since the check condition XML file is a text file, it is easy to see what kind of check is visually performed, and the maintenance efficiency is good.
Moreover, since the user of the facility design system 1 adopts XML when creating the station data, the station data can be created with an arbitrary editor, so that the data can be compared with the creation method using the conventional database. The access time can be shortened, and a considerable amount of time can be shortened when creating a large amount of data.

In addition, since XML is used for all files held by the facility design system 1, the file contents are more visible than when a database is used, backup and restoration are easy, and maintenance operation time is reduced. Can do. Also, complex consistency checks can be performed without being affected by the database processing capability and program parsing time.
In addition, since middleware is not used, development costs can be kept low even for specification changes in the facility design system 1.
The above-described method for creating the difference XML file and the formats of the input station data XML file and the check condition XML file are merely examples, and can be appropriately changed according to the version of the language used and the configuration of the network equipment.

It is a figure which shows the structure of the equipment design system which concerns on embodiment of this invention. It is a figure which shows the function structure of the station data creation apparatus concerning the embodiment. It is a figure for demonstrating the procedure of the station data creation process which the input station data preparation part which concerns on the embodiment performs. It is an example of a format of the input station data XML file according to the embodiment. It is an example of a format of a check condition XML file according to the embodiment. It is a figure for demonstrating the procedure of the check execution process which the consistency check execution part which concerns on the embodiment performs. It is a figure which shows an example of the description of the check condition XML file which concerns on the embodiment.

Explanation of symbols

DESCRIPTION OF SYMBOLS 1 Equipment design system 10 Terminal 20 Station data creation apparatus 21 Difference station data creation part 22 Input station data creation part 23 Check pattern memory | storage part 24 Check engine memory | storage part 25 Check component memory | storage part 26 Consistency check execution part 30 Station data management apparatus 40 Business management system 50 NE-OSS
60 NE

Claims (5)

In the station data management device that checks the consistency of station data to be input to the network element,
Extracting a difference between the station data to be given station data and original, and poured station data creation means for creating poured station data based on the extracted difference,
A check pattern storage means for storing a check pattern information indicating a consistency check pattern to be performed with respect to the input station data created by the closing station data creation means as a text file,
Check engine storage means for storing a check engine which is a program for analyzing check pattern information stored in the check pattern storage means;
Consistency check execution means for performing consistency check of input station data based on the check pattern information stored in the check pattern storage means and the check engine stored in the check engine storage means;
A station data management device comprising: The station data management apparatus according to claim 1, wherein the check pattern information is described in XML (eXtensible Markup Language). The station data management apparatus according to claim 1, wherein the check pattern information includes a definition of a check condition for each consistency check pattern. A check component storage means for storing a check component for executing the consistency check;
In the check pattern information, identification information of a check part to be called is described,
The consistency check execution means includes:
By activating the check engine stored in the check engine storage means, a pattern of consistency check to be performed on the data content described in the station data is determined,
Obtaining check pattern information representing the determined consistency check pattern from the check pattern storage means;
4. The check component stored in the check component storage unit is called based on the identification information of the check component described in the acquired check pattern information. The station data management device described in 1. In the consistency check method in which the station data management device checks the consistency of the station data to be input to the network element,
Extracting a difference between the station data to be given station data and original, and poured station data creation step of creating a charged point data based on the extracted difference,
A check pattern storage step of storing the check pattern information indicating a consistency check pattern of the input station data created in the closing station data creation step as a text file,
A check engine storage step for storing a check engine that is a program for analyzing the check pattern information stored in the check pattern information storage step;
A check engine start step for starting the check engine stored in the check engine storage step;
An analysis step of analyzing the check pattern information stored in the check pattern storage step by the check engine started in the check engine start step;
A consistency check step of performing a consistency check of the input station data based on a result analyzed in the analysis step.

Images