JP3874580B2 - Database integration system - Google Patents

Description

[0001]
BACKGROUND OF THE INVENTION
The present invention relates to a technique for integrating a plurality of databases so that an application can access them transparently.
[0002]
[Prior art]
As a business system using a database, for example, there is an operation support system (hereinafter simply referred to as “OSS”) that supports various operations of an operator in a communication business. Conventionally, in these OSS, a database accessed by an access method defined for each OSS has been used for storing various data.
[0003]
Now, with changes in the business form of the telecommunications business, it may be necessary to construct an OSS that uses the data of each OSS database that has been provided for each individual business. And in building an OSS that uses the data of each database in an integrated manner, it is extremely important that business applications that use these data can transparently access the data of each database using the same access method. It becomes.
[0004]
As a technology that can be used to transparently access data on multiple databases of such multiple systems, Soft Research Center “Distributed Object Oriented Technology CORBA” written by Hirofumi Onozawa, 1996 The technology of an object distribution system such as the object request broker described in the above is known.
[0005]
Also, an intermediate object that can be accessed by a business application is provided by a unified access method described in Japanese Patent Application Laid-Open No. 11-96054, “Database Integrated Application Construction System”, and objects on individual databases are integrated into this. Thus, a technique is also known in which an individual application can transparently access an object on an individual database through an intermediate object.
[0006]
[Problems to be solved by the invention]
However, the object request broker alone does not provide access transparency to the database, so it is necessary to implement a conversion program for each different access interface, and adapt to system scalability and changes. Is difficult. In addition, the technique described in Japanese Patent Laid-Open No. 11-96054 is based on the premise that all objects (object instances) that can be directly or indirectly accessed from a business application are always generated and managed. It will be necessary.
[0007]
For this reason, in a system with a large amount of data such as OSS, since the number of objects becomes enormous, the amount of resources required for the management may become excessive. In addition, every time an object model that defines the structure of an individual object (object instance) is changed due to a business change, all objects (object instances) must be regenerated. The amount of resources required may be excessive.
[0008]
Therefore, an object of the present invention is to make it possible to transparently access data on a plurality of databases with less resource consumption.
[0009]
[Means for Solving the Problems]
To achieve the above object, the present invention provides, for example, a database integration system including a plurality of databases and a server device that accesses data of the databases in accordance with a request from an application,
The server device
An object model storage means for storing an object model that defines a structure of an object including data of one or a plurality of databases;
An object that, when receiving a request for access to the object from the application, accesses the database according to the object model stored in the object model storage means, collects data to be included in the object, and creates an object Creating means;
There is provided an integrated database system comprising object access processing means for performing access requested by the application to the created object and responding to the result of the access.
[0010]
According to such a database integrated system, an object is created when an application requests access, so all objects (object instances) that may be accessed from the application are always generated and managed. There is no need to have. Therefore, it is possible to transparently access data on a plurality of databases with less resource consumption.
[0011]
Furthermore, in such a database integration system,
The object creation means receives a request for access to the object from the application together with designation of a variable that specifies a range of the object that requests access, and is included in a range specified by the designated variable as a result of creation. If it is configured to create only the objects that will be, only the objects that the application needs can be created when the application needs, so the processing when there is an access request from the application is more It becomes possible to carry out with less resource consumption.
[0012]
DETAILED DESCRIPTION OF THE INVENTION
Hereinafter, an embodiment of the present invention will be described taking application to an OSS (Operation Support System) used by a communication carrier as an example.
[0013]
First, the first embodiment will be described.
[0014]
FIG. 1 shows an OSS system configuration according to this embodiment.
[0015]
In the figure, the object virtual integration server 101 is a virtual integration interface unit 102 that collectively processes reference requests and operation requests from a plurality of business applications 100 to a plurality of database systems 120, and responds to requests from the business applications 100. A virtual object management unit 103 that generates and deletes common object instances, manages the state, an object instance storage unit 104 that stores common object instances, and a common object model that is definition information of the common object model An object model storage unit 105, an object model definition / extraction unit 106 for defining a common object model, a data access interface unit 108 for processing access to the database 120, and a customer database 300 are included. The interface repository 107 provides common object model interface information to the virtual integration interface unit 102 and the data access interface unit 108. In addition, the access from the data access interface unit 108 to each database system holds a data definition that defines an interface for the data adapter 110 to access the data of the database system 120 by the data access interface unit 108, On the interface defined by this data definition, the access to the data of the database system 120 from the data access interface unit 108 is accepted, and the database system 120 is accessed according to the access method specific to the database system 120 according to the received contents, and the result is obtained. Return to the data access interface unit.
[0016]
Here, as shown in FIG. 2, the object virtual integration server 101 is installed on a computer equipped with hardware of a CPU 201, a memory 202, an input / output interface 203, a display device 204, an input device 205, a storage device 206, and a network device 207. Can be built. In this case, a program for realizing each function of the object virtual integration server is read from the storage medium of the storage device 206 into the memory 202 and embodied as a process. Further, the virtual integrated server 101 and the external system 208 (100, 110, 120 in FIG. 1) are connected via a network device 207, for example.
[0017]
The OSS shown above can be applied to OSS that provides a service order and charge inquiry service to multiple customers who use the service as shown in Fig. 3, for example. can do.
[0018]
As shown in the figure, OSS303 of carrier Z is added for customer inquiry system 10010 that accepts inquiries from customers and returns responses, telephone service fee system 12010, its billing statement database 12011, and external data access Data adapter 11010 (having an identifier “Phone_BL_adapter”), data communication service charge system 12020, its charge statement database 12021, and data adapter 11020 added for external data access (having an identifier “Data_BL_adapter”) ), Telephone service order system 12030, its service order database 12031, data adapter 11030 added for external data access (with identifier "Phone_SO_adapter"), data communication service order system 12040, its service order Database 12041 Data adapter 11040 (with identifier “Data_SO_adapter”) added for external data access, object virtual integration server 101 for executing transparent access to data distributed to multiple systems, customer database 300, It consists of
[0019]
Here, the customer inquiry system 10010 corresponds to the business application 100 of FIG. Also, the telephone service fee system 12010 and the fee statement database 12011, the data communication service fee system 12020 and the fee statement database 12021, the telephone service order system 12030 and the service order database 12031, the data communication service order system 12040 and the service order database 12041 These correspond to the database system of FIG. In this example, each database system constitutes an independent OSS. For example, the telephone service order system 12030 and the service order database 12031 constitute an OSS for supporting a service order reception from a customer and a service order execution.
[0020]
In such a configuration, the object virtual integration server 101 creates a common object instance 10110 when there is an inquiry request from the customer A301, and creates a common object instance 10120 when there is an inquiry request from the customer X302, and uses these common objects. In each database, information on service orders and charges for customer A301 and customer X302 is collected and a response to the inquiry request is made.
[0021]
Hereinafter, the operation of the object virtual integration server 101 will be described using the OSS of the communication carrier shown in FIG. 3 as an example.
[0022]
FIG. 4 shows the procedure of the object model definition process performed in advance prior to the process of the inquiry request from the customer.
[0023]
As shown in the figure, in this process, first, the object model definition / extraction unit 106 creates a common object model according to the description of the administrator (step 601).
[0024]
Here, an object model that defines the structure of the object instance shown in FIG. 5 is created as the common object model.
[0025]
The common object instance shown in FIG. 5 includes a common object class name 900 (for example, “Customer_Support”), a customer ID 901 (for example, “011-233-12345” is substituted for the object instance), and a customer name 902 (for example, for the object instance). “Hitachi, Ltd.” is assigned, customer location 903 (for example, “292 Yoshida-cho, Totsuka-ku, Yokohama-shi” is assigned in the object instance), service order number-1 (for example, “SO-K in the object instance”) -05876921 "is substituted) ... number-n 904, billing number 1 (for example," BL-K-4456789 "is substituted in the object instance) ... number-n 905. An instance of a common object is identified by, for example, a customer ID that is uniquely assigned in all systems.
[0026]
However, in the common object model that defines such a common object instance, that is, the common object model created in step 601, only the common object class name 900 is set as shown in FIG. Is stipulated. In addition, the service order number and the billing number are defined as an arbitrary number of arrays, and according to this, when creating the object instance, the service order number-1 ... number-n 904, billing is required as required for the object instance. Number 1 ... number-n 905 items are generated and their values are set. Further, the data definition in the common object model shown in FIG.
[0027]
Returning to FIG. 4, once the common object model has been created, the administrator then defines an individual object model for each database system via the object model definition / extraction unit 106 (step 602).
[0028]
Here, as the individual object model, the telephone service charge system 12010 and the charge statement database 12011, the telephone service order system 12030 and the service order database 12031, the data communication service order system 12040 and the service order database 12041 are shown in FIG. The individual object model that defines the service order object instance as shown in Fig. 8 is defined for the data communication service charge system 12020 and the charge statement database 12021. To do.
[0029]
The service order object instance in FIG. 7 includes an object class name 9010 (for example, “Service_Order”), a service order number 9011 (for example, “SO_D_0234567”), a customer ID 901, an order type 9013 (for example, “new subscription”), and an application service type-1. (For example, “short mail service”)... Type-n 9014, service start desired date 9015 (for example, “99/08/01”), construction necessity 9016 (for example, “unnecessary”), service start scheduled date 9017 (for example, “99”) This individual object instance is uniquely identified by the service order number.
[0030]
However, in such an individual object model that defines an individual object instance, that is, an individual object model created in step 602, as shown in FIG. 9, only an object class name 9010 is set, and the others are the structure, Only the data definition that is an interface for accessing the data of the item on the database system 120 is defined.
[0031]
8 includes a common object class name 9020 (for example, “Billing_Info”), a billing number 9021 (for example, “BL_K_4456789”), a customer ID 901, a contract service type 9023 (for example, “mobile phone service”), basic Charge type 9024 (eg “plan SS”), discount charge type 9025 (eg “long-term discount”), optional service type 9026 (eg “interrupt call”), charge statement number -1 (eg “DT_9906_123456”) ... Number-n 9027, unpaid status 9028 (eg, “no unpaid”), and this individual object instance is uniquely identified by a billing number.
[0032]
However, in the individual object model that defines such an individual object instance, that is, the individual object model created in step 602, as shown in FIG. 10, only the object class name 9020 is set, and the others are the structure, Only the data definition that is an interface for accessing the data of the item on the database system 120 is defined.
[0033]
Here, for each individual object model, the attribute of the telephone service or the data communication service is given depending on whether the system created for the individual object model is a telephone service or a data communication service. Set.
[0034]
Returning to FIG. 4, once the individual object model is created, the administrator then defines the reference relationship between the common object model and the individual object model via the object model definition / extraction unit 106 (step 603). ).
[0035]
Here, a data item reference relationship table as shown in FIG. 11 is created as the reference relationship.
[0036]
Data item reference relationship table includes reference common object class name 911 (“Customer_Support”), reference destination 1-managed object class name 912 (“Service_Order”), reference destination 1-instance identification name 913 (“service order number”) Reference destination 1-data adapter name 914 (“Phone_SO_adapter”), reference destination 2 915-917, reference destination 3 918-920, and reference destination 4 921-923 are similarly configured as follows. For the reference 1-data adapter name 914, the attribute of the telephone service or the data communication service is set as an attribute depending on whether the system provided with the data adapter unit 110 is of the telephone service or the data communication service. Give and set.
[0037]
This data item reference relationship table shows the individual object model of the reference destination n-individual object class name for the item of the same name as the reference destination n-instance identification name of the common object model of the reference source common object class name 911. The database system 120 provided with the data adapter unit 110 of the reference n-data adapter name to be referenced is the same name as the reference n-instance identification name of the common object model of the reference source common object class name 911 And data corresponding to the individual object model of the reference destination n-individual object class name.
[0038]
Here, when the same reference destination n-instance identification name 913 is registered, there are a plurality of reference destinations to be referred to for the item.
[0039]
Now, returning to FIG. 4, when the reference relationship between the common object model and the individual object model is defined in this way, the individual object model created in step 602 is searched using the data item reference relationship table. The data definition corresponding to the item of the common object model is extracted, and the attribute (telephone service or data communication service) set for the individual object model from which the data definition is extracted is given to the common object model. The setting (step 604) processing is performed for all individual object models (step 605).
[0040]
Specifically, for example, for the item service order number of the common object model in FIG. 6, the data item reference relation table in FIG. 11 is searched for the reference n-instance identification name which is the service order number. Refer to the individual object model of the reference destination n-managed object class name set for the n-instance identification name, and change the data definition set for the field service order number in the individual object model to the common object Set for item service order number of model.
[0041]
Next, the created common object model, individual object model, and data item reference relationship table are stored in the object model storage unit 105 (step 606).
[0042]
Then, interface information for the business application to access the common object model is generated (step 607) and stored in the interface repository (step 608).
[0043]
The object model definition process performed in advance prior to the process of the inquiry request from the customer has been described above.
[0044]
Next, a process for responding to an inquiry request from a customer of the object virtual integration server 101 will be described.
[0045]
FIG. 12 shows the procedure of this processing.
[0046]
As illustrated, the customer inquiry system 10010 issues a specific object initialization request to the virtual integration interface unit 102 according to the interface information stored in the interface repository at the time of activation (step 701). The virtual object management unit 103 that has received the object initialization request via the virtual integration interface unit 102 reads the common object model from the object model storage unit 105 (step 702). Furthermore, the data access interface unit 108 connects the read common object to each data adapter unit 110 defined as the data adapter unit 110 with the name of the reference destination n-data adapter in the data item reference relation table ( Step 703).
[0047]
After that, if a reference request for a common object instance specifying a customer ID and a service type (telephone service or data communication service) is issued from the customer A301, the virtual object management unit 103 performs a virtual integration interface unit Received via 102 (step 704).
[0048]
Upon receiving the reference request, the virtual object management unit 103 checks whether a common object instance having the specified customer ID as the value of the item customer ID and the specified service type as an attribute has already been generated and generated. If not (step 705), only the common object instance 10110 of this customer ID is generated and stored in the object instance storage unit 104 (step 706).
[0049]
In the generation of the common object instance 10110, the value set in the common object model is set for the item of the object class name. For the items of customer name 902 and customer location 903, the customer name 902 and customer location corresponding to the customer ID are searched and set from the customer database 300 attached to the object virtual integration server 101. For service order number and billing number items, refer to the same n-instance identification name as the name of these items according to the interface defined by the data definition set with the attribute of the service type specified for these items. Inquires about the item data corresponding to the specified customer ID to the data adapter unit 110 of the reference destination n-data adapter name set with the attribute of the specified service type in the data item reference relation table. Set the value obtained as a result of the response. Then, the specified service type is set as the attribute in the generated common object model.
[0050]
If a common object instance having the specified customer ID is generated in this way, next, data referenced by the common object instance is collected (step 707).
[0051]
Here, the object model stores the individual object model with the specified service type attribute among the individual object models registered as the reference destination n-individual object model in the data item reference relation table for this common object model. In accordance with the individual object model, an individual object instance having the value of the item of the common object instance registered as the reference destination n-instance identification name as an identification value is generated according to the individual object model, and stored in the object instance storage unit 104. Store. However, individual object instances are not generated for items of common object instances for which values are not set.
[0052]
When generating an individual object instance, for example, if the individual object instance is the service order object instance shown in FIG. 7, first, the value set in the individual object model is set for the item of the object class name 9010. To do. For the item of the service order number 9011, the value of the item having the same name of the common object instance is set. For the other items, according to the interface defined by the data definition set for these items, it is set in the data item reference relationship table for the same reference destination n-instance identification name as the name of the service order number. The data adapter unit 110 with the name of the reference destination n-data adapter is inquired of the item data corresponding to the set service order number, and a value obtained as a result of the response is set.
[0053]
After creating the individual object instance in this way, the data of the created common object instance and individual object instance is appropriately processed and responded to the customer inquiry system 10010 via the virtual integration interface unit 102 (step 708). . In step 705, if a common object instance having the specified customer ID as the value of the item customer ID and the specified service type as an attribute has already been generated, the processing of steps 706 and 707 is performed. In short, the processing of step 708 is immediately performed.
[0054]
Upon receiving the response, the customer inquiry system 10010 displays the inquiry result from the customer A on a customer support information display screen 1500 as shown in FIG. 13, for example. On the screen, as shown in the figure, for example, a field 1510 for displaying and inputting customer basic information such as customer ID, customer name, customer location, etc., a button 1511 for searching using the customer ID as a key, service type, basic Field 1520 for displaying contract services such as plans and options, field 1530 for displaying fee details such as basic usage charges, call charges, option fees, discounts, delinquent charges, total charges, etc., for searching and displaying past charge details Button 1531, a field 1540 for displaying an order number, an order type, a desired service start date, a scheduled service start date, and the like, and a button 1541 for displaying detailed information on the service order.
[0055]
Returning to FIG. 12, if there is a reference request from the customer inquiry system, the process returns to step 704 to continue the process, and if there is a common object deletion request specifying the customer ID and service type (step 709), the specified Extract individual object instances generated for common object instances that have the customer ID as the value of the item customer ID and have the specified service type as an attribute by the reverse method of creation, and these individual object instances and common objects The instance is deleted from the object instance storage unit 104 (step 710).
[0056]
The first embodiment of the present invention has been described above.
[0057]
In the above embodiment, only the customer database is configured to be directly accessible from the object virtual integration server without going through the data definition or data adapter unit, but this is the same as the other database system 120. Access may be via the adapter unit.
[0058]
In the above embodiment, the case of referring to the data of the database system has been described as an example. However, the object virtual integration server replaces the reference of the data of the database system in the above embodiment with the data operation of the database system. Thus, the present invention can be similarly applied to various data operations such as updating of data in the database system.
[0059]
In the above embodiment, the generation of the individual object model and the individual object instance is performed on the object virtual integration server side. However, the generation of the individual object instance or the generation of the individual object model and the individual object instance corresponds to the corresponding data. You may make it perform in the adapter part 110. FIG.
[0060]
In this embodiment, the case where only one type of common object model is created has been described as an example. However, a plurality of types of common object models may be created. At this time, the same individual object model may be referred to in different common object models.
[0061]
As described above, according to the first embodiment, when a business application requires an object instance, it is generated and managed only within a required range, so that data on multiple databases can be transmitted with less resource consumption. Can be accessed automatically.
[0062]
Hereinafter, a second embodiment of the present invention will be described.
[0063]
In the second embodiment, an OSS that is applied as a monitoring system that monitors the mobile communication network 410 in an integrated manner will be described as an example.
[0064]
FIG. 14 shows a configuration of the monitoring system according to the present embodiment.
[0065]
As shown in the figure, the monitoring system includes a service area measurement system 12050, its coverage database 12051, a data adapter 11050 added for external data access (with an identifier “BTS_Test_adapter”), a geographic information system 12060, Map database 12061, data adapter 11060 added for external data access (with identifier "AreaMap_adapter"), fault monitoring system 12070, its alarm database 12071, data added for external data access Adapter 11070 (with the identifier “BTS_Alarm_adapter”), performance monitoring system 12080, its traffic database 12081, data adapter 11070 added for external data access (with the identifier “BTS_Traffic_adapter”), object virtual integration server 101, mobile Chikyoku monitoring system 10020, and from the area 1 the monitoring terminal 401 ... area n monitoring terminal 402 to display the operation screen in area units.
[0066]
In this embodiment, the data reference and operation of each database system 120 are the same as in the first embodiment, but in the second embodiment, the individual object model in the first embodiment is absorbed into the common object model. The common object model is created in the form. Therefore, the individual object is not used in the second embodiment. Therefore, in the data item reference relationship table, the relationship between the common object model and the individual object is not described, and only the name of the data adapter unit 110 of the database system 120 to which the item is referenced and the item of the common object model is described. Will be.
[0067]
FIG. 15 shows a common object instance according to the present embodiment.
[0068]
As shown in the figure, common object model instance consists of common object class name 1300 ("BTS_Management"), base station ID 1301 ("BTS-0125"), base station installation location 1302 ("Kamikurata, Totsuka-ku, Yokohama-shi"), base Generated at station X coordinate 1303 ("198765"), base station Y coordinate 1304 ("432178"), sector 1 coverage data 1305, sector 1 upstream traffic data 1306, sector 1 downstream traffic data 1307, sector 1 The alarm data 1308... Sector n also includes 1309 to 1312 and a data collection date 1313 (“99/08/10 12:15:30”).
[0069]
In the common object model that defines such a common object instance, as shown in FIG. 16, only the item of the common object class name is set, and the other items define only the structure. In this common object model, the reference item number 1 is set for the base station ID, the base station installation location, the base station X coordinate 1303, and the base station Y coordinate item group, and the reference item for the sector 1 coverage data item. Reference item number 3 is set for the item group of the upstream traffic data of sector 1, the downstream traffic data of sector 1, and reference item number 4 is set for the item of alarm data.
[0070]
In addition, as shown in FIG. 17, the data item reference relationship table of this embodiment includes a reference source common object class name 1321 (“BTS_Management”), a data adapter name 1322 (“AreaMap_adapter”) of reference destination 1, and a reference destination 2 The data adapter name 1323 (“BTS_Test_adapter”), the reference adapter 3 data adapter name 1324 (“BTS_Alarm_adapter”), and the reference adapter 4 data adapter name 1325 (“BTS_Traffic_adapter”) are described. The data adapter name of the reference destination n is the name of the data adapter unit 110 provided in the database system 120 that holds the data referred to by the item of the reference item number n of the common object model.
[0071]
In the monitoring system according to the present embodiment, the object virtual integration server 101 is requested to access the common object instance specifying area 1 from the area 1 monitoring terminal 401 via the mobile base station monitoring system 10020. The When this request is received, the object virtual integration server 101 first designates the coordinate range of area 1, and the base station ID, base station installation location, base station X coordinate 1303 of the mobile base station in the coordinate range , The geographic information system 12060 is connected to the base station Y coordinate set via the data adapter unit 110 of “AreaMap_adapter” registered in the data item reference relation table corresponding to the reference item number in the common object model of the item. And a database system query comprising the map database 12061, and a common object instance is created corresponding to each obtained set. Then, set the value of the corresponding item of the corresponding set in the items of base station ID, base station installation location, base station X coordinate 1303, base station Y coordinate of the created common object instance, and the rest excluding the data collection date Along with the value of the base station ID, each database system query through the data adapter unit 110 registered in the data item reference relation table corresponding to the reference item number of the item, and the result obtained Set. The creation date of the common object instance is set as the data collection date. Then, the access requested by the area 1 monitoring terminal 401 is performed on each generated common object instance, that is, the common object instance of the base station in the area 1.
[0072]
Similarly, in response to an access request from the area n monitoring terminal 402 to the common object instance via the mobile base station monitoring system 10020, a common object instance corresponding to the base station in the area n is created and The requested access is performed.
[0073]
On the other hand, each monitoring terminal connected to the mobile base station monitoring system 10020 displays the monitoring result on a base station monitoring map screen as shown in FIG. 18, for example. On the screen, for example, the location 16B of the base station “BTS-0125” and the alarm status / traffic status display 1610 on the map data 1600 corresponding to the corresponding monitoring area, the service covered by the base station “BTS-0125” Display area 1620.
[0074]
Now, the object virtual integration server 101 according to the present embodiment updates the state of the common object instance in response to a request from the database system 120 and notifies the area n monitoring terminal.
[0075]
FIG. 19 shows the procedure of such processing.
[0076]
As shown in the figure, in this process, first, an event issuance registration is performed from the data adapter unit 110 to the data access interface unit 108 (step 801). Here, the BTS_Alarm_adapter 11070 performs alarm event issuance registration received by the failure monitoring system 12070, and the BTS_Traffic_adapter 11080 performs traffic threshold excess event issuance registration for which the performance monitoring system 12080 has performed the determination processing.
[0077]
Next, event reception registration is performed with respect to the virtual integrated interface unit 102 from the mobile base station monitoring system 10020 (step 802). The data adapter unit 110 that has performed event issuance registration transmits this event to the data access interface unit 108 when an event that has been issued and registered occurs in the database system.
[0078]
When the data access interface unit 108 receives an event from the connected data adapter unit (step 803), the data access interface unit 108 notifies the virtual object management unit 103 of the event. The virtual object management unit 103 reflects the contents of the event on the state of the common object instance corresponding to the event origin (step 804). As a result, if the state of the object has been changed (step 805), the mobile base station monitoring system 10020 that has registered for event reception is notified of the state change (step 806). The mobile base station monitoring system 10020 notifies the monitoring terminal that monitors the area where the base station where the state has changed, of the state change, and the monitoring terminal updates the display screen of FIG. 18 according to the state change. Etc. to present the contents of the update to the supervisor.
[0079]
If the data adapter unit does not cancel the event issuance (step 807), the process returns to step 803 to continue the event reception process.
[0080]
As described above, according to the second embodiment, by managing the state of the common object based on the event notified asynchronously from the data adapter, it is possible to appropriately manage the network whose state is updated in real time. It becomes like this.
[0081]
Hereinafter, a third embodiment of the present invention will be described.
[0082]
The third embodiment is a mobile base station facility planning system 10030 that statistically analyzes traffic data and alarm data to determine future base station installation and the second object in the monitoring system of the second embodiment. A virtual integrated server 1012 is added.
[0083]
The common objects handled by the second object virtual integration server 1012 are the same as those shown in FIGS. 14 and 16, and the data item reference relationship table is the same as that shown in FIG.
[0084]
When the second object virtual integration server 1012 receives an access request from the moving body base station facility planning system 10030 to the common object instance for which the period is specified, the history data and traffic during the specified period in the alarm database 12071 are received. Query the historical data in the specified period of the database 12081 via the corresponding data adapter unit 110, create a common object instance for each response, and the value obtained as a result of the query for each item of each common object instance Set. Then, the requested access is made to the created common object instance.
[0085]
As described above, a plurality of object virtual integration servers 1012 may be provided, and the range of common object instances generated in response to a request from a business application is set according to any dimension including temporal and geographical objects. It may be a thing.
[0086]
【The invention's effect】
As described above, according to the present invention, it is possible to transparently access data on a plurality of databases with less resource consumption.
[Brief description of the drawings]
FIG. 1 is a block diagram showing a configuration of an operation support system according to an embodiment of the present invention.
FIG. 2 is a block diagram showing a hardware configuration of the object virtual integration server according to the embodiment of the present invention.
FIG. 3 is a block diagram showing an application example of the operation support system according to the first embodiment of the present invention to a customer inquiry system.
FIG. 4 is a flowchart showing a procedure of object model definition processing according to the embodiment of the present invention;
FIG. 5 is a diagram showing a common object instance according to the first embodiment of the present invention.
FIG. 6 is a diagram showing a common object model according to the first embodiment of the present invention.
FIG. 7 is a diagram showing an individual object instance according to the first embodiment of the present invention.
FIG. 8 is a diagram showing an individual object instance according to the first embodiment of the present invention.
FIG. 9 is a diagram showing an individual object model according to the first embodiment of the present invention.
FIG. 10 is a diagram showing an individual object model according to the first embodiment of the present invention.
FIG. 11 is a diagram showing a data item reference relationship table according to the first embodiment of the present invention.
FIG. 12 is a flowchart showing a processing procedure when a response is made to the inquiry request according to the embodiment of the present invention.
FIG. 13 is a diagram showing an inquiry result display screen according to the first embodiment of the present invention.
FIG. 14 is a block diagram showing an application example of the operation support system according to the second embodiment of the present invention to a monitoring system.
FIG. 15 is a diagram showing a common object instance according to the second embodiment of the present invention.
FIG. 16 is a diagram showing a common object model according to the second embodiment of the present invention.
FIG. 17 is a diagram showing a data item reference relationship table according to the second embodiment of the present invention.
FIG. 18 is a diagram showing a monitoring result display screen according to the second embodiment of the present invention.
FIG. 19 is a flowchart showing a procedure of status update notification processing according to the second embodiment of the present invention.
FIG. 20 is a block diagram showing an application example of the operation support system according to the third embodiment of the present invention to a monitoring system.
[Explanation of symbols]
DESCRIPTION OF SYMBOLS 101 ... Object virtual integration server, 102 ... Virtual integration interface part, 103 ... Virtual object management part, 104 ... Object instance storage part, 105 ... Object model storage part, 106 ... Object model definition and extraction part, 107 ... Interface repository, 108 ... Data access interface unit, 110 ... Data adapter unit, 201 ... CPU, 202 ... Memory, 203 ... Input / output interface unit, 204 ... Display device, 205 ... Input device, 206 ... Storage device, 207 ... Network device, 208 ... External system

Claims (3)

A database integration system comprising a plurality of databases and a server device that accesses data in the databases according to a request from an application,
The server device
An object model storage means for storing an object model that defines a structure of an object including data of one or a plurality of databases;
An object that, when receiving a request for access to the object from the application, accesses the database according to the object model stored in the object model storage means, collects data to be included in the object, and creates an object Creating means;
The created object, performs the access requested by the application, possess an object access processing means responsive to the result to said application,
The object creating means includes
A request for access to the object is received from the application together with a specification of a variable that specifies a range of the object that requests access, and only objects that are included in the range specified by the specified variable as a result of creation are received. The first means to create,
As a result of creation, the second type that creates only objects that contain data that has the value specified by the specified variable, equal to the value specified by the specified variable, or that has a value included in the value range. Means,
The database integration system , wherein the variable defines a type of data included in the object and a value or a range of the value . A database integration method that mediates access to data of each of the databases of the application so that the application can access data of a plurality of databases accessed by different access methods using the same access method,
An object model storage step for storing an object model that defines a structure of an object including data of one or a plurality of databases;
Receiving a request for access to the object from the application by a predetermined access method;
According to the object model stored in the object model storage means, accessing the database by the database access method, collecting data to be included in the object, and creating an object;
Object access is requested from the application performs the requested access, possess an object access process step of responding the result to the application,
The object creation step includes
A request for access to the object is received from the application together with a specification of a variable that specifies a range of the object that requests access, and only objects that are included in the range specified by the specified variable as a result of creation are received. The first step to create,
As a result of creation, the second type that creates only objects that contain data that has the value specified by the specified variable, equal to the value specified by the specified variable, or that has a value included in the value range. And having steps
The database integration method , wherein the variable defines a type of data included in the object and a value or a range of the value . A storage medium storing a program to be read and executed by an electronic computer,
The program is
A server that accesses a plurality of databases and data of the databases according to a request from an application,
An object model storage means for storing an object model that defines a structure of an object including data of one or a plurality of databases;
An object that, when receiving a request for access to the object from the application, accesses the database according to the object model stored in the object model storage means, collects data to be included in the object, and creates an object Creating means;
A server having object access processing means for performing access requested by the application to the created object and responding to the application with the result is constructed on the electronic computer ,
The object creating means includes
A request for access to the object is received from the application together with a specification of a variable that specifies a range of the object that requests access, and only objects that are included in the range specified by the specified variable as a result of creation are received. The first means to create,
As a result of creation, the second type that creates only objects that contain data that has the value specified by the specified variable, equal to the value specified by the specified variable, or that has a value included in the value range. Means,
The storage medium for recording a program, wherein the variable defines a type of data included in the object and a value or a range of the value .

Images