JP2001265805A - Platform service system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a platform service system which enables the use of a database and an application without developing a database and application softwares at each time by preparing middleware which connects plural application softwares and a common database together and making it possible to selectively use the application softwares through a user interface so that the common data base can be used corresponding to the plural application softwares. SOLUTION: The platform service system is equipped with the database in which various data are integrated and stored, the plural independent application softwares, the middleware which enables data to be stored in the database from the application softwares and the data stored in the database to be read out to the application softwares, and the user interface which uses at least one of the application softwares.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention provides a database in which various data generated from a plurality of application software are integrated and stored and shared in a logically one database engine, and a plurality of users share this database. Platform service system that can be used as a service, a billing system such as a database that determines the collection and distribution of database usage fees in each client-side management system, and a usage fee for data held by each client-side management system The present invention relates to a data usage fee distribution system that determines payment distribution.

[0002]

2. Description of the Related Art In recent years, with the development of communication technology and computer technology, many platform service systems using various application software from terminals have been put into practical use. Such a platform service system connects a center that manages application software and databases and terminal devices of each user to a telephone line or the like.
Connect with a network such as a LAN line, call the center from the terminal device and use the application software, and if necessary, search and acquire desired data from the database constructed corresponding to this application software, or Is stored. In the related art, a database according to a target and a purpose is constructed for each application software, and a dedicated user interface is used. The database uses a programming language dedicated to the database such as the SQL language, while the application uses a programming language such as the C language.

[0003]

In the conventional platform service system as described above, in order to retrieve data corresponding to a specific purpose from a database, dedicated application software and a user interface corresponding to the purpose are used. Must be prepared. However, the database uses a database-specific programming language such as SQL language, and the application software uses a programming language such as C language. Therefore, in order to construct the application software together with the database, a database language is required. It is necessary to be able to understand and use both the language for the application and the language for the application, and few developers have such ability and are limited to a specific person. In addition, since a database is constructed for each application, it is difficult to share data stored in each database across.

The present invention solves such a problem, and in order to use a common database corresponding to a plurality of application software, a middleware for connecting these application software and a database is prepared. To provide a platform service system that enables the use of databases and applications without having to develop a database or application software each time by making these application software selectively available through a user interface. It is intended for. Another object of the present invention is to provide a platform service system that can use a shared database constructed in advance from a user terminal simply by developing application software tailored to each purpose of use. It is. Another object of the present invention is to provide a platform service system that can share and use data stored in a database by different application software. Another object of the present invention is to provide a usage fee billing system for a database or the like that can determine the distribution of collection of a database usage fee from each client side management system when there are a plurality of client side management systems. It is. Another object of the present invention is to
An object of the present invention is to provide a data usage fee distribution system capable of determining a usage fee payment distribution of data held by each client side management system by a server side management system when there are a plurality of client side management systems.

[0005]

According to a first aspect of the present invention, there is provided a platform service system comprising: a database for integrating and storing various data; a plurality of independent application software; and the database from each of the application software. And middleware that enables data to be stored in the database or read data stored in the database to the application software, and a user interface that uses at least one of the application software. And 3. The platform service system according to claim 2, wherein: a database for integrating and storing various data; a plurality of independent application software; and storing data from the respective application software in the database, or the database. And a middleware for pre-constructing middleware that enables the data stored in the application software to be read out to the application software, and provides a client-side device with a user interface using at least one of the application software. It is characterized by the following. 4. The platform service system according to claim 3, wherein: a database for integrating and storing various data; a plurality of independent application software; and storing data from the respective application software in the database, or the database. And a middleware for preliminarily establishing middleware capable of reading out the data stored in the application software, wherein the application software is provided to the client device. According to a fourth aspect of the present invention, there is provided the platform service system, wherein the server is provided with a database in which various data generated from a plurality of application software are integrated and stored and shared in a logically one database engine, and the database is provided by a user interface. A platform service system in which a client using application software and the server are connected to each other via a network, wherein data meeting predetermined conditions is extracted as sampling data from data registered in the database, and the sampling data or The present invention is characterized in that the information of the sampling data or the result of analysis is provided. The platform service system of the present invention according to claim 5, wherein the server is provided with a database in which various data generated from a plurality of application software are integrated and stored and shared in a logically one database engine, and the database is provided by a user interface. A platform service system in which a client using application software and the server are connected by a network, wherein condition data for extracting sampling data from data registered in the database, and distribution data relating to distribution contents. And providing the distribution data based on the extracted sampling data. The platform service system according to the present invention as claimed in claim 6, wherein the server is provided with a database in which various data generated from a plurality of application software are logically integrated and stored and shared in one database engine, and the database is provided by a user interface. A platform service system in which a client using application software and the server are connected by a network, wherein the client uses the application software, a procedure operated using the application software, and the application software. At least one of the selected contents is stored in the database as user extension data. According to a seventh aspect of the present invention, in the platform service system according to any one of the fourth to sixth aspects, the server stores data from the respective application software in the database or stores the data in the database. Middleware is provided, which is capable of reading stored data to the respective application software. 9. The server-side management system according to claim 8, wherein the server-side management system provides a database and stores various data from a plurality of client-side management systems in the database. A usage fee billing system such as a database for determining collection and distribution of the database usage fee in a system, wherein a user registration number, a user usage count, or a user usage time for each of the client-side management systems is determined at a predetermined timing. The number of data usage totaling means to be totalized in the respective client-side management systems, the total number of user registrations, the total number of user usages, or the total time of user usage for each of the client-side management systems totaled by the data usage number totaling means. Calculate utilization rate in management system Calculating means for determining the collection and distribution of the database usage fee in each of the client-side management systems based on the calculation result by the calculating means, and the amount of collection determined by the collection and distribution determining means And an output unit for displaying, printing, or transmitting the information. 10. The system according to claim 9, wherein the system includes a server-side management system that provides a database for storing various data, and a client-side management system that manages an interface that allows data to be stored in the database. In the case where there are a plurality of the client-side management systems, a usage fee billing system such as a database for determining the distribution of the database usage fee from each of the client-side management systems by the server-side management system. In addition, the client-side management system having a larger number of user registrations in the database, the number of times of use of the user, or the time of use of the user has a larger collection distribution of the database usage fee. The data usage fee distribution system according to the present invention provides a server-side management system that provides a database and stores various data from a plurality of client-side management systems in the database. A data usage fee distribution system for deciding usage fee payment distribution of retained data, wherein a group of data extracted according to predetermined conditions from data stored in the database is used by a user for each of the client-side management systems. A data utilization number totaling means for selecting and totaling data, and a utilization rate in each of the client-side management systems is calculated from the total number of uses for each of the client-side management systems totaled by the data utilization number totaling means. Calculation means, and a calculation result by the calculation means Payment distribution determining means for determining a usage fee payment distribution of the data held by each of the client-side management systems, and an output means for displaying, printing, or transmitting the payment amount determined by the payment distribution determining means. It is characterized by having. The data usage fee distribution system according to the present invention includes a server-side management system that provides a database for storing various data, and a client-side management system that manages an interface that enables data to be stored in the database. Having a plurality of client-side management systems, wherein the server-side management system is a data usage fee distribution system that determines the usage fee payment distribution of the data held by each of the client-side management systems, A group of data extracted under predetermined conditions from the data stored in the database is selected for each of the use management systems, and the use management system with a larger number of selected data allocates the usage fee payment distribution of the data more. It is characterized by many things.

[0006]

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS A platform service system according to first to third and seventh embodiments of the present invention stores data from a plurality of application software in a database, or stores data stored in the database, respectively. By constructing middleware that enables reading to application software, the database can be shared and used by a plurality of application software.

Further, the platform service system according to the first embodiment of the present invention can use each application software selectively by using a user interface independent of the application software.

A platform service system according to a second embodiment of the present invention provides a user interface using at least one application software to a client-side device. Just by developing an interface, user terminals can use application software and shared databases that have been built in advance.

A platform service system according to a third embodiment of the present invention provides application software to a client-side device. By simply developing application software for each purpose of use, a platform service system is provided from a user terminal. It is possible to use a shared database that has been constructed in advance.

In the platform service systems according to the fourth to sixth embodiments of the present invention, various data generated from a plurality of application softwares are logically integrated into one database engine, stored, and shared. Since the database is provided in the server, data stored in the database by different application software can be shared and used.

[0011] Further, a system and the like for using a database and the like according to an eighth embodiment of the present invention determine collection and distribution of a database use fee in each client-side management system. The usage fee billing system such as this database is based on a data usage counting means for counting the number of user registrations for each client-side management system, and a total number of user registrations for each client-side management system. Calculating means for calculating the utilization rate in the client-side management system, collecting distribution determining means for determining the collection and distribution of the database usage fee in each client-side management system based on the calculation result, and the determined collection amount And output means for displaying, printing, or transmitting the information. When there are a plurality of client-side management systems, it is possible to determine the distribution of collection of the database usage fee from each of the client-side management systems.

[0012] In a ninth embodiment of the present invention, the usage fee billing system for a database or the like is different from the usage management system in which the number of registered users in the database, the number of times of use of the user, or the time of use of the user is longer. In the case where there are a plurality of client-side management systems, the collection and distribution of the database usage fee from each of the client-side management systems can be appropriately performed.

A data usage fee distribution system according to a tenth embodiment of the present invention determines distribution of usage fee payment of data held by each client-side management system. The data usage fee distribution system includes a data usage number counting unit that selects and totalizes a group of data extracted from data stored in the database under predetermined conditions into user data for each client-side management system. Calculating means for calculating the usage rate of each client-side management system from the total number of usages of each client-side management system, and the usage fee of data held by each client-side management system based on the calculation result By having a payment distribution determining means for determining the payment distribution, and an output means for displaying, printing, or transmitting the determined payment amount, when there are a plurality of client-side management systems, each of the server-side management systems Distribution of usage fee payment for data held by client-side management system It can be determined.

The data usage fee distribution system according to the eleventh embodiment of the present invention sorts a group of data extracted from data stored in a database under predetermined conditions for each usage management system. In the case where there is more than one client-side management system, the data usage fee distribution is more appropriate for each client-side management system. Can be done.

[0015]

An embodiment of the platform service system of the present invention will be described below with reference to the drawings. FIG. 1 is a conceptual diagram showing the overall configuration of a platform service system according to the present invention. The platform service system includes a database 10 for integrating and storing various data, and a plurality of independent application software 30.
And accumulation of data in the database 10 from each application software 30 or database 10
Middleware 20 for reading data stored in the application software 30 to each application software 30;
And a user interface 40 using at least one application software 30. The database 10 can be used by logically integrating various data generated from a plurality of application software 30 into one database engine, storing the data, and sharing the data. Various general-purpose data that can be searched and used by a user is stored in the database 10 in advance. The general-purpose data includes general-purpose data prepared by a database administrator or a client-side administrator that can be used by all users, and general-purpose data that can be used only by a specific user such as the same organization or the same member. Further, the database 10 includes a common database 11 for storing user-specific data, and a plurality of extended databases 12 respectively associated with the common database 11. The common database 11 sequentially registers and stores common minimum data such as a name or name, an address or place of residence, an address, a contact such as a telephone or a facsimile, and a unique code for each user. The extended database is configured for each client-side manager who operates or manages an organization or for each data content, and sequentially registers and stores data such as occupations, hobbies, and access record information. The common database 11 and the extended database 12 storing these user-specific data
Is prepared for use by a database administrator or a client-side administrator, and each user can use only a part of the data regarding his or her own data. The common database 11 and the extended database 12 include not only data registered by each user on their own will but also data registered without being based on their own will. The management and maintenance of these data is performed by a database administrator or client-side management. Perform. Even if the client-side administrator can manage and maintain the data, the target data is only the data relating to the user belonging to the own organization or member.

The addition or deletion of general-purpose data available to all users and the modification of existing data are performed by a database administrator or a client-side administrator. The application software 30 includes, for example, a user management application 31, a mail distribution application 32, a search application 33, and the like, as illustrated. The user interface 40 includes, for example, a fan club interface 41, a comic work interface 42, a music search interface 43, and the like, as illustrated. The user interface 40
In order to use the database 10, various parts are directly operated by the user and provided by the database administrator in association with the application software 30 according to the search purpose. That is, the user interface 40 and the application software 30 are stored in the database 10
The database administrator constructs this in advance according to the search target and the search content. Alternatively, only the application software 30 may be constructed in advance, and the user interface 40 may be provided according to the request of the client-side administrator.
The client-side administrator may construct the system independently. Alternatively, only the database 10 and the middleware 20 may be constructed, and the application software 30 may be constructed independently by the client-side administrator. As described above, the database 10 and the middleware 20 are constructed at least in advance, and the application software 30, the application software 30, the user interface 40, or the user interface 40 or the service providing the user interface 40 is provided in accordance with the client-side administrator. The side administrator has a low cost database 1
0 can be used. In particular, database 10
And a plurality of application software 3 used for it
0 and the middleware 20 in advance, it is possible to provide the client-side administrator with a user interface 40 for using those applications 30 according to the demand. Is less.

In addition, the database 10 is provided with a sampling database 13 which stores sampling data extracted under predetermined conditions from the common database 11 and the extended database 12 as necessary. The sampling data stored in the sampling database 13 is provided as information 51 such as mail distribution or marketing data after being tabulated or analyzed in some cases. It is also possible to receive information 52 of condition data for extracting sampling data from data registered in the database 10 and distribution data relating to distribution contents, and provide distribution data based on the extracted sampling data. it can. In this case, the user address data registered and extracted in the common database 11 by the database administrator is
The distribution data is distributed by mail using the mail distribution application 32. Further, the distribution data can be distributed using the respective user interfaces 40. The database 10 usually uses the SQL language, and the application software 30 uses the C language or the like.

Next, the configuration of the middleware 20 will be described with reference to FIG. The middleware 20 is roughly divided into an interface unit 21 and a server unit 22 which is a resident process. The interface unit 21 is further divided into an I / F function unit 23 and a client unit 24, and the server unit 22 has a plurality of individual SQLs for actually operating the database 10 and a connection management process 25 receiving a request from the client unit 24. It consists of a process 26. Data exchange between the client unit 24 and the connection management process 25 and between the connection management process 25 and the individual SQL process 26 are performed using packets. Basically, the flow of the packet is transmitted from the client unit 24 to the connection management process 25.
From the connection management process 25 to the individual SQL process 26, from the individual SQL process 26 to the connection management process 25, and from the connection management process 25 to the client unit 24 in order. Client unit 24
Is a group of processes for actually exchanging with the server unit 22, and comprises a connection process 24A, a start request process 24B, an SQL request process 24C, an end request process 24D, and a disconnection process 24E. The I / F function unit 23 is established by calling these processes. The connection process 24A is a process for starting socket communication with the server unit 22. The start request process 24B transmits a request to the connection management process 25 of the server unit 22 to allocate its own individual SQL process 26. The start request processing 24B is configured to write in a connection request packet and wait for the return. The individual SQL process 26 assigned at this time performs a rollback process 26B. SQL request processing 24C
Transmits a table operation request to the server unit 22. The SQL request processing 24C is configured to put an SQL statement in the data portion of a packet, write it in the packet, and wait for return. The termination request processing 24D transmits a request to release the assignment of the own individual SQL process 26 to the connection management process 25 of the server unit 22. This termination request processing 24D writes the termination request packet,
It is just waiting for the return. At this time, the individual SQL process 26 assigned at this time
Perform A. The disconnection processing 24E is a function for disconnecting the socket communication with the server unit 22. Connection management process 2
5 is required to be connected by a plurality of client units 24,
Association start processing 25A with the individual SQL process 26,
An association process 25B with the individual SQL process 26 and an association termination process 25C with the individual SQL process 26 are performed. The individual SQL process 26 establishes a connection with the database 10 at the time of startup, continues the connection until the connection management process 25 ends, and continues the connection with the connection management process 25. This is to improve the response by always establishing a session with the database 10 in the server unit 22. Also, the individual SQL process 26 performs the commissioning process 2 by the received packet.
6A, rollback processing 26B, addition / deletion processing 26
C, perform a search process 26D. In the individual SQL process 26, what kind of processing is actually performed is determined from information in the header part of the packet. Outsourcing process 26A
Performs a commit when a packet is sent. This packet is sent from the client unit 24, and the result is set and returned to the client unit 24. For the addition / deletion processing 26C and the search processing 26D, the SQL text of the data portion transmitted by the packet is used as the dynamic SQL
Is performed using the method described in Rollback processing 26B
SQL of database 10 when packet was sent
Execute the statement. This packet is sent during SQL request processing 24C from the client unit 24. Then, the result is set and returned to the client unit 24. add to/
The deletion process 26C executes an SQL statement in the database 10 when a packet is sent. This packet is sent during SQL request processing 24C from the client unit 24. The result is set and returned to the client unit 24. The search process 26D executes an SQL statement in the database 10 when a packet is sent. This packet is sent during SQL request processing 24C from the client unit 24. Set the result and set the client part 2
Return to 4.

FIG. 3 shows a more detailed relationship among the client unit 24, the connection management process 25, and the individual SQL process 22. The connection management process 25 is requested to connect from a plurality of client units 24. The maximum number of connections between the connection management process 25 and the client unit 24 is assumed to be m. Individual SQL process 26
Generates n connections when the connection management process 25 is started, and connects to the connection management process 25 immediately after the connection is generated. That is, the connection management process 25
Can maintain m + n connections. As described above, the connection management process 25 can simultaneously perform m connections with the client unit 24 and simultaneously perform n connections with the individual SQL process 26. In the connection management process 25, the connection state between the client unit 24 and the individual SQL process 26 is managed in a table. That is, in the connection management process 25,
When a connection request is issued from the client unit 24, an individual SQL process 26 corresponding to the connection request is allocated, and the connection is held until a disconnection request is made from the client unit 24. In FIG. 3, the client unit 24-1 has an individual SQL
A process 26-1 is assigned to the client unit 24-2, and an individual SQL process 26-2 is assigned to the client unit 24-3.
Then, each client unit 24 requests the individual SQL process 26 to perform processing until the client unit 24 is disconnected. The individual SQL process 26 that has performed the processing transmits the result to the connection management process 25,
Refers to the correspondence table and returns the result to the client unit 24. As described above, the connection management process 25 establishes the association between the client unit 24 and the individual SQL process 26, passes the packet passed from the client unit 24 as it is to the associated individual SQL process 26, From the client unit 24 to the corresponding client unit 24.

According to the middleware 20 of the present embodiment, a mechanism that receives an SQL statement from the client unit 24, passes it to the individual SQL process 26, processes it, and returns the result to the client unit 24, The realization of the server unit 22 allows the development of only the I / F function unit 23 for the new application software 30 in the future. Therefore, the client unit 24 and the server unit 22 can be shared, and the database 10 can be shared. In some cases, the number of connected client units 24 may be larger than the number of the individual SQL process 26. In this case, the connection management process 25 stores the start request packet of the connected client unit 24 in an internal buffer, and When the other client unit 24 is disconnected, the allocation is performed to the vacant individual SQL process 26, and the request stored in the internal buffer is passed. For example, in the case shown in FIG. 3, if the client unit 24-3 is disconnected, the client unit 24-m is allocated to the individual SQL process 26-n. This waiting function allows more connections than the individual SQL process 26 when viewed from the client unit 24 side. Further, in the connection management process 25, when the socket communication is suddenly cut off from the client unit 24 due to the disappearance of the process on the client unit 24 side, the association with the corresponding individual SQL process 26 is canceled, and If the client unit 24 is present, the association is reconnected. Further, when such a sudden socket disconnection phenomenon of the client unit 24 occurs, the individual SQL process 26 may be performing some processing. When a connection with a new client unit 24 is started during processing of a request from the previous client unit 24, a request result of the past client unit 24 is sent to the new client unit 24. There can be. In this case, the past request result of the client unit 24 is discarded when returning to the connection management process 25. The contents of the function combine the client part (function group), issue a processing request to the server side, and receive the return value. The middleware 20 performs two timeout processes. One is a case where the client unit 24 is in a waiting state for a certain period or more. In this case, a packet is transmitted as a timeout and the socket communication is disconnected. The other is a case where a request issued by the individual SQL process 26 to the database 10 has not responded for a certain period of time. Also in this case, the process is interrupted by the database 10 and the packet is transmitted.

Next, an embodiment of the configuration of the server side management system and the client side management system of the database provider will be described with reference to FIG. In the figure,
Clients include fan club managers, comic book managers, and music search managers. The fan club administrator manages the fan club interface 41, the comic book manager manages the comic book interface 42,
The music search manager manages the music search interface 43. Each client has registered a plurality of users as members, and these users use their respective interfaces. In addition, the fan club manager, manga work manager, and music search manager use a database of idol information, manga works, or music information that each of them owns or each of which has obtained a license as general-purpose data that can be used by the user. Register to 10. The basic information about the user belonging to the fan club manager, the comic book manager, or the music search manager is stored in the common database 1.
1 is registered. This user registration can be performed by each administrator, and also by the user who applies for registration.

The server-side management system 110 of the database provider, a user 141 belonging to a fan club, a user 142 belonging to a manga work, and a user 14 belonging to music search.
3 is connected by a line 100 such as the Internet. The server-side management system 110 includes the database 10, the middleware 20, and the plurality of application software 30 described in the above embodiment. The user 141 belonging to the fan club, the user 142 belonging to the manga work, and the user 143 belonging to the music search are connected to the line 100 so that the fan club interface 41, the manga work interface 42, and the music search interface to which the respective users belong. 43 and download the server-side management system 11 using these interfaces.
The user can access the application software 30 in the database 10 and the information registered in the database 10. The fan club interface 41, the comic work interface 42, and the music search interface 43 are provided from the server-side management system 110. Note that, in addition to the server-side management system 110, a form provided by a client-side management system owned by a client such as a fan club manager, a manga work manager, or a music search manager may be provided, or the form may be provided in each user terminal. It may be.

Next, another embodiment of the configuration of the server side management system and the client side management system of the database provider will be described with reference to FIG. In FIG. 5, for example, a client-side management system 140 is provided with a unique application 30 such as employee attendance management and product management, and an interface 40 for using the application 30. A user such as an employee can use the interface 40 from each terminal device. Is used to access the application software 30. The server-side management system 120 includes the database 10 and the middleware 20 described in the above embodiment. The application software 30 in the client-side management system 140
00, the middleware 20 in the server-side management system 120 uses the database 10. As described above, the database 10 stores the general-purpose data 111 that can be used by the user, and the common data and extended data related to the user in an integrated manner. Then, among these data, data that has been obtained in advance by the client or the user can be used as sampling data.

Next, an embodiment of a usage fee billing system for a database or the like in the server-side management system will be described with reference to FIG. This usage fee billing system such as a database is a system that determines the distribution of collection of the database usage fee in each client-side management system. The usage fee billing system such as a database according to the present embodiment includes a data use number totaling unit 61 and a calculating unit 62.
And a collection distribution determining means 63 and an output means 64. The data usage counting means 61 counts the number of registered users, the number of times of use of the user, or the time of use of the user for each client-side management system at a predetermined timing. The calculating means 62 calculates the usage rate in each client-side management system from the total number of user registrations, the total number of user usages, or the total user usage time of each client-side management system totaled by the data usage totaling means 61. Is calculated. The collection distribution determination unit 63 determines the collection distribution of the database usage fee in each client-side management system based on the calculation result by the calculation unit 62. The output unit 64 displays, prints, or transmits the collection amount determined by the collection distribution determination unit 63. Then, the higher the number of user registrations in the database 10, the number of times of use of the user, or the time of use of the client by the client management system, the larger the distribution of collection of the database usage fee. As described above, according to the usage fee billing system such as the database of the present embodiment, when there are a plurality of client-side management systems, the collection and distribution of the database usage fee from each of the client-side management systems can be determined.

Next, an embodiment of a data usage fee distribution system in the server-side management system will be described with reference to FIG. This data usage fee distribution system is a system for determining the usage fee payment distribution of data held by each client-side management system. The data usage fee distribution system according to the present embodiment includes
, Calculation means 72, payment distribution determination means 73, and output means 74. The data usage number counting means 71 selects and counts a group of data extracted from data stored in the database 10 under predetermined conditions into user data for each client-side management system. The calculating means 72 calculates the usage rate in each client-side management system from the total number of usages of each client-side management system counted by the data usage number counting means 71. The payment distribution determining means 73 determines the usage fee payment distribution of the data held by each client-side management system based on the calculation result by the calculation means 72. The output unit 74 displays, prints, or transmits the payment amount determined by the payment distribution determining unit 73. Then, the usage management system having a larger number of selected data sets a higher usage fee payment distribution of the data. As described above, according to the data usage fee distribution system of the present embodiment, when there are a plurality of client side management systems, and when there are a plurality of client side management systems, payment of the data usage fee to each client side management system is performed. Distribution can be performed properly.

[0026]

According to the present invention, in order to use a common database corresponding to a plurality of application software, middleware for connecting the application software and the database is prepared. By making application software selectively available through the user interface,
The database and the application can be used without developing the database and the application software each time. Also, according to the present invention, only by developing application software for each purpose of use,
From the user terminal, a shared database constructed in advance can be used. Further, according to the present invention, data stored in the database by different application software can be shared and used. Further, according to the present invention, when there are a plurality of client-side management systems, it is possible to determine the distribution of collection of the database usage fee from each of the client-side management systems. Further, according to the present invention, when there are a plurality of client-side management systems, it is possible to determine, by the server-side management system, the distribution of usage fee payment of data held by each of the client-side management systems.

[Brief description of the drawings]

FIG. 1 is a conceptual diagram showing an overall configuration of a platform system according to an embodiment of the present invention.

FIG. 2 is a conceptual diagram showing the configuration of middleware according to the embodiment.

FIG. 3 is a conceptual diagram showing a detailed relationship inside the middleware according to the embodiment.

FIG. 4 is a conceptual diagram showing a configuration of a server-side management system and a client-side management system of a database provider according to the embodiment;

FIG. 5 is a conceptual diagram showing a configuration of a server-side management system and a client-side management system of a database provider according to another embodiment.

FIG. 6 is a block diagram showing a usage fee billing system for a database or the like in a server-side management system according to an embodiment of the present invention;

FIG. 7 is a block diagram showing a data usage fee distribution system in a server-side management system according to an embodiment of the present invention;

[Explanation of symbols]

 10 Database 20 Middleware 30 Application Software 40 User Interface

Claims (11)

[Claims] 1. A database for integrating and storing various types of data, a plurality of independent application software, and accumulation of data from the respective application software to the database, or each of data stored in the database. A platform service system comprising: middleware capable of reading the application software; and a user interface using at least one application software. 2. A database for integrating and storing various types of data, a plurality of independent application software, and accumulating data from the respective application software in the database, or each of data stored in the database. A platform system in which middleware capable of reading the application software is constructed in advance, wherein a platform for providing a user interface using at least one of the application software to a client device is provided. . 3. A database for integrating and storing various types of data, a plurality of independent application software, and accumulating data from each of the application software in the database, or each of data stored in the database. A platform service system in which middleware capable of reading the application software is configured in advance, wherein the platform service system provides the application software to a client device. 4. A server which has a database in which various data generated from a plurality of application software are logically integrated and stored in a single database engine and shared by a server, and a client which uses the application software by a user interface. A platform service system in which a server and a server are connected by a network, wherein data that satisfies predetermined conditions is extracted from the data registered in the database as sampling data, and the sampling data or the totaling or analysis result of the sampling data is extracted. A platform service system that provides information. 5. A server which is provided with a database in which various data generated from a plurality of application software are integrated and stored and shared in a logically one database engine, and a client which uses the application software by a user interface. A platform service system connected to a server via a network, wherein the server receives condition data for extracting sampling data from data registered in the database and distribution data on distribution contents, and A platform service system for providing the distribution data based on data. 6. A server in which a database in which various data generated from a plurality of application software are integrated and stored and shared in a logically one database engine is provided on a server, and a client which uses the application software by a user interface is provided. A server and a platform service system connected by a network, wherein the client uses at least one of a time using the application software, a procedure operated using the application software, and a content selected using the application software. A platform service system, wherein one data is stored in the database as user extension data. 7. The server includes middleware that is capable of accumulating data from the respective application software in the database or reading out data stored in the database to the respective application software. The platform service system according to any one of claims 4 to 6, wherein: 8. A server-side management system that provides a database and stores various data from a plurality of client-side management systems in the database, and determines the distribution of collection of the database usage fee in each of the client-side management systems. A usage fee billing system such as a database, wherein the number of user registrations for each of the client-side management systems, the number of times a user is used, or the number of times a user is used is counted at a predetermined timing; Calculating means for calculating the usage rate in each of the client-side management systems from the total number of registered users, the total number of users, or the total usage time of the users for each of the client-side management systems counted by the number-of-uses counting means; , Based on the calculation result by the calculation means And a collection distribution determining means for determining the distribution of the database usage fee in each of the client-side management systems, and an output means for displaying, printing, or transmitting the collection amount determined by the collection distribution determining means. A usage fee billing system for a database or the like, characterized in that: 9. A server-side management system that provides a database for storing various data, and a client-side management system that manages an interface that enables data to be stored in the database. When present, a usage fee billing system such as a database for determining collection and distribution of the database usage fee from each of the client side management systems by the server side management system, wherein the number of registered users in the database, A usage fee billing system for a database or the like, wherein the collection distribution of the database usage fee is increased for a client-side management system in which the number of times of use or the user's usage time is longer. 10. A server-side management system that provides a database and stores various data from a plurality of client-side management systems in the database, and determines a distribution of usage fee payment for data held by each of the client-side management systems. A data usage fee distribution system, wherein a group of data extracted from data stored in the database under predetermined conditions is sorted into user data for each of the client-side management systems, and the number of data usage is counted. Totalizing means, calculating means for calculating the utilization rate in each of the client-side management systems from the total number of uses for each of the client-side management systems totaled by the data use number totaling means, and a calculation result by the calculating means Based on each of the client side It has a payment distribution determining means for determining a distribution of usage fees for the data held by the management system, and an output means for displaying, printing, or transmitting the payment determined by the payment distribution determining means. Data usage fee distribution system. 11. A server-side management system that provides a database for storing various data, and a client-side management system that manages an interface that enables data to be stored in the database. A data usage fee distribution system for determining a usage fee payment distribution of the data held by each of the client-side management systems by the server-side management system, wherein the data usage fee distribution system determines a predetermined usage fee based on data stored in the database. A data usage fee, wherein a group of data extracted according to a condition is selected for each of the usage management systems, and the usage management system having a larger number of selected data has a higher usage fee payment distribution of the data. Distribution system.