JP2006003996A - Use history management device, use history management method and use history management program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To manage a use history for every user in accordance with the rule of each user. <P>SOLUTION: A history management server 40 accepts service contract information including the storage rule or deletion rule of a use history from a user terminal 10, and stores it in a service contract information DB 42a for each user. Then, the history management server 40 accepts the service use history of a user from a service providing server 20, and when this satisfies the storage rule of the user, the history management server 40 stores it in a use history DB 42c for each user. Furthermore, the history management server 40 deletes the use history after the lapse of a preservation term designated by the deletion rule from the use history DB 42c based on the deletion rule of each user, and deletes the use history which exceeds disk capacity restriction designated by the deletion rule in the same way from the use history DB 42c. <P>COPYRIGHT: (C)2006,JPO&NCIPI

Description

  The present invention relates to a usage history management apparatus, a usage history management method, and a usage history management program for managing a usage history of a service used by a user.

  Conventionally, when various services are provided on a network, it is a common practice to collect and manage service usage histories (so-called logs) used by users. For example, Patent Document 1 (Japanese Patent Application Laid-Open No. 2003-141075) discloses a log management technique called log storage. Specifically, this is based on a service API (Application Program Interface) (Service Program (Application Program Interface)). The history sent for each process is converted into an XML (eXtensible Markup Language) file according to predetermined format information and stored in a database (DB). Also, with this log management technology, when the history exceeding the preset capacity is stored in the database, the storage capacity is secured by deleting the oldest history stored in the database. Yes.

JP 2003-141075 A

  By the way, the above-described conventional technology is merely for managing the history for each service (process), and for each user, the history cannot be managed from the viewpoint of each user, and the history browsing service for each user. There was a problem that it could not be provided.

  That is, a user who uses the service wants to store the service usage history in the database (history storage period), the disk capacity (history capacity limit) to be used for storing the service usage history, and even in the first place. Even if the service usage history that you do not want to store, the service usage history that you do not want to delete regardless of the history storage period or history capacity limit, etc. Since the conventional technology described above manages the history for each service (process), it has not been possible to meet such a request for each user.

  Therefore, the present invention has been made to solve the above-described problems of the prior art, and a usage history management device capable of managing a usage history in accordance with the rules of each user for each user. It is an object to provide a history management method and a usage history management program.

  In order to solve the above-described problems and achieve the object, the invention according to claim 1 is a usage history management device that manages a usage history of a service used by a user, and stores the usage history for each user. Use history storage means, rule storage means for storing rules for storing and / or deleting use history by the use history storage means for each user, and rules for each user stored in the rule storage means. And a control means for controlling storage and / or deletion of each user's usage history by the usage history storage means.

  The invention according to claim 2 is the above invention, wherein the usage history includes a service identifier for uniquely identifying a service used by a user, time information for specifying when the service is used, service Terminal information for specifying the user terminal used when using the information or information including a combination thereof, wherein the rule storage means uses the usage history from the new usage history of each user. A storage rule that pre-designates a service identifier, time information, terminal information, history item, or a combination of the usage history to be stored in the storage means is stored for each user, and the control means stores a new usage for each user. Of the history, only usage histories and / or history items corresponding to the user's storage rules stored in the storage rule storage means are stored in the usage history storage means. The features.

  According to a third aspect of the present invention, in the above invention, the rule storage unit stores, for each user, a deletion rule that specifies a storage period of a usage history by the usage history storage unit, and the control unit includes: Of the usage history of each user already stored in the usage history storage means, deleting the usage history that has passed the storage period specified by the deletion rule of the user stored in the rule storage means. Features.

  According to a fourth aspect of the present invention, in the above invention, the rule storage unit stores, for each user, a deletion rule that specifies a storage capacity of the usage history stored in the usage history storage unit, and the control unit includes: When the storage capacity of the usage history of each user already stored in the usage history storage means exceeds the storage capacity specified by the deletion rule of the user stored in the rule storage means, the usage A predetermined usage history is deleted from the user's usage history.

  Further, the invention according to claim 5 is the above invention, wherein the usage history includes a service identifier for uniquely identifying a service used by a user, time information for specifying when the service is used, service Terminal information for specifying the user terminal used when using the information, or information including a combination thereof, wherein the rule storage means stores the information of each user already stored in the use history storage means. A deletion rule that pre-designates a service identifier, time information, terminal information, history item, or a combination of these, which is permitted to be deleted from the usage history, is stored for each user, and the storage control means includes the usage history. When trying to delete the usage history of each user already stored in the storage means, the interest corresponding to the deletion rule of the user stored in the rule storage means And deletes only the history and / or history items.

  The invention according to claim 6 further comprises format information storage means for storing, for each service, format information for storing the usage history in the usage history storage means in the above invention, wherein the control means comprises: Based on the format information of each service stored in the format information storage means, the usage history of the service is stored in the usage history storage means.

  The invention according to claim 7 is a usage history management method for managing a usage history of a service used by a user, the usage history storing step of storing the usage history in a usage history storage means for each user; A rule storing step of storing a rule for storing and / or deleting a usage history by the usage history storage unit in the rule storage unit for each user, and a rule of each user stored in the rule storage unit And a control step for controlling storage and / or deletion of each user's usage history by the usage history storage means.

  Further, in the invention according to claim 8, in the above invention, the rule storing step stores a deletion rule specifying a storage period of the usage history by the usage history storage unit for each user in the usage history storage unit, The control step includes a usage history that has passed the storage period specified by the deletion rule of the user stored in the rule storage unit among the usage history of each user already stored in the usage history storage unit. It is characterized by deleting.

  In the invention according to claim 9, in the above invention, the rule storing step stores a deletion rule designating a storage capacity of the usage history by the usage history storage unit for each user in the usage history storage unit, In the control step, when the storage capacity of each user's usage history already stored in the usage history storage means exceeds the storage capacity specified by the user's deletion rule stored in the rule storage means Is characterized in that a predetermined usage history is deleted from the usage history of the user.

  The invention according to claim 10 is a usage history management program for causing a computer to execute a usage history management method for managing a usage history of a service used by a user, wherein the usage history is stored for each user. Stored in the rule storage means, a rule storage procedure for storing in the rule storage means for each user a rule relating to storage and / or deletion of the usage history by the usage history storage means, And a control procedure for controlling storage and / or deletion of each user's usage history by the usage history storage means based on the rules of each user.

  The invention according to claim 11 is the above invention, wherein the rule storing procedure stores a deletion rule specifying a storage period of the usage history by the usage history storage unit for each user in the usage history storage unit, The control procedure includes a usage history that has passed a storage period specified by the deletion rule of the user stored in the rule storage unit among the usage history of each user already stored in the usage history storage unit. It is characterized by deleting.

  Further, in the invention according to claim 12, in the above invention, the rule storing procedure stores a deletion rule designating a storage capacity of the usage history by the usage history storage unit for each user in the usage history storage unit, In the control procedure, when the storage capacity of each user's usage history already stored in the usage history storage means exceeds the storage capacity specified by the deletion rule of the user stored in the rule storage means Is characterized in that a predetermined usage history is deleted from the usage history of the user.

  According to the invention of claim 1, 7 or 10, rules relating to storage and deletion of usage history are stored for each user, and storage and deletion of usage history of each user is controlled based on such rules. The usage history can be managed for each user according to the rules of each user, and a service for browsing the usage history can be provided for each user.

  Further, according to the invention of claim 2, since a storage rule specifying a predetermined service, a predetermined use, a predetermined user terminal, and a predetermined history item is stored for each user, it is specified for each user. It is possible to store only specified history items for the service history and the use history related to the user terminal at the time of use. In addition, for users, usage history and history items that are not worthy of storage (no need to browse), usage history and history items that do not want to be stored (do not want to be browsed), etc. are reflected in the storage rules. It becomes possible to reduce the storage capacity of the history and prevent the leakage of the usage history.

  According to the invention of claim 3, 8 or 11, the deletion rule specifying the usage history storage period is stored for each user, so that the usage history after the specified storage period has been deleted for each user. It becomes possible. It is also possible to conclude a pay-as-you-go contract according to the storage period between the user and the history manager.

  According to the fourth, ninth, or twelfth aspect of the invention, the deletion history specifying the storage capacity of the usage history is stored for each user, so that the usage history exceeding the specified storage capacity can be stored for each user. It becomes possible to delete. It is also possible to conclude a pay-as-you-go contract according to the storage capacity between the user and the history manager.

  Further, according to the invention of claim 5, since a deletion rule specifying a predetermined service, a predetermined use, a predetermined user terminal, and a predetermined history item is stored for each user, it is specified for each user. It is possible to delete only the specified history item for the service history and the use history related to the user terminal at the time of use. In addition, for the user, it is possible to realize efficient storage of the usage history by reflecting the usage history, history items, etc. that do not want to be deleted (which must be browsed forever) in the deletion rule.

  According to the invention of claim 6, since the use history is stored based on the format information of each service stored for each service, it becomes possible to manage the use history for a plurality of services.

  Embodiments (embodiments 1 and 2) of a use history management apparatus, a use history management method, and a use history management program according to the present invention will be described below in detail with reference to the accompanying drawings.

  In Example 1 below, a system including a usage history device (history management server) according to the present invention is taken as an example, and the appearance of the example, the outline and features of the system, and each device constituting the system The function, details of the schema setting process, details of the history storage process, details of the history deletion process, effects of the first embodiment, and the like will be described in order.

[Users, service providers, history managers]
First, a user, a service provider, and a history management provider appearing in the following embodiments will be described with reference to FIG. FIG. 1 is a diagram for explaining a user, a service provider, and a history management provider that appear in the embodiment.

  The service provider is a person who provides a service to the user, and the user pays a service fee to the service provider and uses the service provided by the service provider ((1) and (See (2)). The history management business operator manages the usage history of the service used by the user, receives a history management fee from the service business operator, and manages the service usage history received from the service business operator (see FIG. (See (3) and (4)). Further, the user pays a service fee to the history management company and uses a history browsing service (usage history browsing, statistical information browsing, etc.) provided by the history management company (see (5) and (6) in the figure). ). It should be noted that the actual fee exchange may be performed through a settlement organization.

  Here, the service provided by the service provider is provided to the user via a network (a communication network formed by a public telephone network or the Internet), and the service usage history (log) of the user is provided when the service is provided. Any service that can be collected may be used. In the first embodiment, a service that converts a MPEG (Moving Picture Coding Experts Group / Moving Picture Experts Group) 2 format file received from a user into an MPEG 4 format, or an MPEG 2 format file that is converted into an MPEG 1 format. A service will be described as an example.

  Further, in this embodiment, as illustrated in FIG. 1, a case where there are a plurality of users and service providers and there is only one history management company will be described. The present invention can be applied to any one of a person and a history management company regardless of whether there is a plurality of persons or only one person.

[System overview and features]
FIG. 2 is a configuration diagram illustrating the configuration of the system according to the first embodiment. As shown in the figure, this system includes a user terminal 10 operated by a user, a service provider server 20 of a service provider, a service provider terminal 30 operated by a service provider, and a history of a history manager. The management server 40 is configured to be communicably connected to each other via a network (a communication network formed by a public telephone network or the Internet). The history management server 40 corresponds to a “use history management device” recited in the claims.

  The outline of this system is that a service usage history generated by a user operating the user terminal 10 to use a service of the service providing server 20 is managed by the usage history DB 42c of the history management server 40. . In this system, the service usage history management method has a main feature, and the usage history can be managed for each user according to the rules of each user.

  More specifically, the history management server 40 receives service contract information including usage history storage rules and deletion rules from the user terminal 10 and stores the service contract information for each user, and from the service provider terminal 30. File format information, which is a sample of service usage history, is received and stored (see (1) and (2) in FIG. 2).

  Here, the “storage rule” is a rule that specifies the service identifier of the usage history to be stored in the usage history DB 42c, and the “deletion rule” is a usage history storage period (storage period) or storage capacity. This is a rule that specifies (disk capacity limit) (see FIG. 4). The “file format information” is format information used when the service usage history received from the service providing server 20 is stored in the usage history DB 42c (see FIG. 5).

  On the other hand, the service providing server 20 receives an MPEG2 format file from the user terminal 10, converts it into the MPEG4 format, and returns it to the user terminal 10 (see (3) and (4) in FIG. 2). Then, the history management server 40 receives the service usage history of the user from the service providing server 20, and when this satisfies the storage rule of the user, the usage history DB 42c for each user based on the file format information. In addition, the storage work report is returned to the service providing server 20 (see (5) and (6) in the figure).

  In addition to the above storage operation, the history management server 40 deletes, from the usage history DB 42c, the usage history that has passed the storage period specified by the deletion rule, based on the deletion rule of each user, and also deletes the same. The usage history exceeding the disk capacity limit specified by the rule is deleted from the usage history DB 42c. Furthermore, the history management server 40 transmits the service usage history and statistical information requested to be browsed to the user terminal 10 in order to provide the user with a history browsing service (usage history browsing, statistical information browsing, etc.). (See (7)).

  As described above, according to the system according to the first embodiment, the usage history storage rules and the deletion rules are stored for each user, and the storage and deletion of the service usage history of each user is controlled based on the rules. As described above, the usage history can be managed for each user according to the rules of each user, and a service for browsing such usage history can be provided for each user. Become.

  In this embodiment, since there are a plurality of users and service providers, there are also a plurality of user terminals 1, service providing servers 20, and service provider terminals 30, but in the following, for convenience of explanation. A user terminal 10 of a certain user and a service provider server 20 and a service provider terminal 30 of a service provider that provides an MPEG file format conversion service will be described as an example.

[User terminal functions]
The user terminal 10 shown in FIG. 2 is a known personal computer or workstation, home game machine, Internet TV, PDA, mobile phone or PHS in which communication software such as e-mail software or browser software is installed. Such as a mobile communication terminal. The user terminal 10 has a function of accessing the service providing server 20 and the history management server 40 as a function closely related to the present invention, and a service including a usage history storage rule and a deletion rule in the history management server 40. History management of contract information transmission function, function of transmitting MPEG2 format file to service providing server 20, function of receiving converted MPEG4 format file from service providing server 20, history of service usage history and statistical information requested for browsing A function of receiving from the server 40 is included.

[Service providing server functions]
The service providing server 20 shown in FIG. 2 is a known server device that provides a user with an MPEG file format conversion service. The user terminal 10 has, as functions closely related to the present invention, a function of receiving an MPEG2 format file from the user terminal 10, a function of converting the received file into an MPEG4 format, and a converted MPEG4 format file. And the function of transmitting the service usage history generated at the time of providing the service to the history management server 40 after completion of the service, the function of receiving a storage work report from the history management server 40, and the like.

[Service provider terminal functions]
The service provider terminal 30 shown in FIG. 2 is a terminal such as a known personal computer or workstation in which communication software such as e-mail software and browser software is installed in the same manner as the user terminal 10 described above. The service provider terminal 30 has, as functions closely related to the present invention, a function of accessing the history management server 40, a function of transmitting file format information to the history management server 40, and the like.

[History management server functions]
The history management server 40 shown in FIG. 2 is a server device that manages a service usage history. The history management server 40 includes a communication control IF unit 41, a storage unit 42, and a control unit 43, as illustrated in FIG. FIG. 3 is a block diagram showing the configuration of the history management server 40.

  Among these, the communication control IF unit 41 is a processing unit that controls communication with the user terminal 10, the service providing server 20, and the service provider terminal 30 in accordance with a so-called HTTP communication protocol. Specifically, mainly the service contract information is received from the user terminal 10, the service usage history is received from the service providing server 20, the file format information is received from the service provider terminal 30, and the service requested to be viewed The usage history and statistical information are transmitted to the user terminal 10, and the storage work report is transmitted to the service providing server 20.

  The storage unit 42 is a storage unit (storage unit) that stores data and programs necessary for various processes performed by the control unit 43. The storage unit 42 is particularly closely related to the present invention, and includes a service contract information DB 42a, a file In addition to the format information DB 42b and the usage history DB 42c, an SQL (Structured Query Language) statement for operating these databases (DB) is stored. The service contract information DB 42a corresponds to the “rule storage means” described in the claims, the file format information DB 42b corresponds to the “format information storage means”, and the usage history DB 42c also corresponds to the “use history storage means”. Corresponding to

  Here, the service contract information DB 42a is a relational database that stores the service contract information received from the user terminal 10 for each user. Specifically, as illustrated in FIG. 4, the “service identifier of the usage history to be stored in the usage history DB 42 c in association with the“ user identifier ”for uniquely identifying the user (depending on the service provider). Stores a "storage rule" that specifies "a unique service identifier" and a "deletion rule" that specifies "retention period" and "disk space limit" for each user. To do. Further, the service contract information DB 42 a stores the “current usage capacity” of the disk in an updatable manner in the “deletion rule” as illustrated in FIG. Note that the usage history storage period and the disk capacity limit are determined by signing a pay-as-you-go contract according to the period and capacity between the user and the history management company.

  The file format information DB 42b is a relational database that stores file format information received from the service provider terminal 30 for each service. Specifically, as illustrated in FIG. 5, “root node name (schema identifier)” and “child node name” extracted from file format information (sample usage history) are stored in association with each other. The root node name and child node name stored as file format information will be described later.

  The usage history DB 42c is a relational database that stores the service usage history received from the service providing server 20 for each user and service. Specifically, as illustrated in FIG. 5, service usage histories are stored on a table classified for each user and classified for each service. For example, the service usage history shown in the figure is the usage history of the MPEG file format conversion service, and is used to uniquely identify the service used by the user and the user. “Registration time” for specifying when the service is used (when registered as a usage history), “file name” after format conversion, in association with “table name” consisting of “user identifier” A usage history (a usage history of one record) including “format (format)” after conversion and “conversion completion time” indicating the time required for the conversion is stored on the table. Each database described above is not necessarily in a relational format, and may be a database in another format.

  Returning to the description of FIG. 2, the control unit 43 has a control program such as an OS (Operating System), a program defining various processing procedures, and an internal memory for storing necessary data. A processing unit that executes processing, and particularly closely related to the present invention, includes a service contract unit 43a, a schema setting unit 43b, a history management unit 43c, and a history providing unit 43d. The history management unit 43c corresponds to “control unit” recited in the claims.

  Here, the service contract unit 43a stores the service contract information received from the user terminal 10 in the service contract information DB 42a, and updates the service contract information after the change when the service contract information changes. And a processing unit for storing the data.

  In addition, the schema setting unit 43b stores the file format information received from the service provider terminal 10 in the file format information DB 42b, and a table for storing a usage history (one that has not yet been stored with a specific history). Is a processing unit that generates in the usage history DB 42c. The schema setting process by the schema setting unit 43b will be described in detail later with reference to FIGS.

  The history management unit 43c is a processing unit that stores the service usage history received from the service providing server 20 in a table in the usage history DB 42c and deletes the service usage history already stored in the table. The history storage processing and history deletion processing by the history management unit 43c will be described in detail later with reference to FIGS.

  Further, the history providing unit 43d is a processing unit that creates a requested service usage history and statistical information (HTTP response) by referring to the usage history DB 42c in response to a request (such as an HTTP request) from the user terminal 10. is there. The created service usage history and statistical information messages are transmitted to the user terminal 10 via the communication control IF unit 41.

[Schema setting processing details]
Next, the details of the schema setting process by the schema setting unit 43b will be described with reference to FIG. FIG. 7 is a flowchart illustrating the flow of the schema setting process according to the first embodiment.

  As shown in the figure, when the history management server 40 receives file format information (a sample of usage history) from the service provider terminal 30 (step S701), the schema setting unit 43b converts the history sample into a DOM (Document Object). Model) (step S702). Specifically, as illustrated in FIG. 8, the schema setting unit 43b converts an XML file, which is a history sample, into a DOM formed from a root node and its child nodes by using an XML parser. When the history sample illustrated in FIG. 9 is input to the XML parser, the history sample is converted into a DOM including a root node and a child node as illustrated in FIG.

  Subsequently, the schema setting unit 43b obtains the name of the root node and the name of the child node from the DOM, and creates an initial state table (one in which no specific history is stored yet) in the usage history DB 42c ( Steps S703 and S704). Specifically, the root node name is acquired as a “table name” from the DOM, and the child node name is also acquired as a “column” from the DOM, and the SQL statement as illustrated in FIG. A table as illustrated is created in the usage history DB 42c. The root node name and child node name are obtained using the methods prepared by the above XML parser. However, the method of using such an XML parser differs depending on the product in the market. Based on this, the above name is acquired.

  Further, the schema setting unit 43b stores the file format information in the file format information DB 42b in accordance with the above DOM (step S705). Specifically, the root node name (schema identifier) and child node name are extracted from the DOM, and these are associated and stored in the file format information DB 42b (see FIG. 5). In the case of the table illustrated in FIG. 12, the disk capacity per record is 93 bytes (10 + 40 + 5 + 32 + 6 = 93 bytes).

[Details of history storage processing]
Next, details of the history storage processing by the history management unit 43c will be described with reference to FIG. FIG. 13 is a flowchart illustrating the flow of the history storage process according to the first embodiment.

  As shown in the figure, when the service provision to the user terminal 10 is completed (step S1301), the service provision server 20 transmits the service use history generated by the service provision to the history management server 40 (step S1302). Specifically, the service providing server 20 sends HTTPS / TCP to the CGI (Common Gateway Interface) program (/cgi-bin/post.pl in this embodiment) of the history management unit 43c of the history management server 40. On the / IP protocol, a service use history as illustrated in FIG. 14 is transmitted. The service usage history is an actual history corresponding to the history sample illustrated in FIG.

  On the other hand, when receiving the service usage history from the service providing server 20, the history management server 40 converts the service usage history into DOM in the history management unit 43c (step S1303). Specifically, the history management unit 43c also has the above-described XML parser, and converts the service usage history to DOM by the XML parser. For example, when the service usage history illustrated in FIG. 14 is input to the XML parser. 15 is converted into a DOM composed of a root node and a child node as illustrated in FIG. Note that this DOM corresponds to the DOM illustrated in FIG. 10, but since it is a result of processing a service usage history that is not a sample, each child node has a value.

  Subsequently, the history management unit 43c determines whether or not the DOM root node name exists in the file format information DB 42b (step S1304). That is, the root node name is extracted from the DOM illustrated in FIG. 15, and it is determined whether or not this root node name is stored in the file format information DB 42b. As a result, if it is not stored (No in step S1304), the history management unit 43c does not store the service usage history and indicates that “the service usage history was not stored because there is no file format information” The work report is transmitted to the service providing server 20 (step S1309).

  On the other hand, if the root node name is stored in the file format information DB 42b (Yes in step S1304), the history management unit 43c determines whether the storage condition stored in the service contract information DB 42a is satisfied. Is determined (step S1305). Specifically, based on the user identifier included in the root node name, the storage condition is extracted from the service contract information of the user corresponding to the user identifier, and is the service usage history corresponding to this storage condition? (That is, whether or not the service identifier of the service usage history is designated as a storage target) is determined.

  In this determination, when the storage condition is not satisfied (No at Step S1305), the history management unit 43c does not store the service usage history, and “the service usage history is not stored because the storage condition is not satisfied”. A work report to that effect is transmitted to the service providing server 20 (step S1309).

  On the other hand, if the storage condition is met (Yes at step S1305), the history management unit 43c stores the service usage history in the usage history DB 42c (step S1306). Specifically, the values of each child node are extracted from the DOM using an SQL statement as illustrated in FIG. 16, and the table in the usage history DB 42c corresponding to the root node name is extracted as illustrated in FIG. Stores the value of each child node.

  Following this, the history management unit 43c updates the current usage capacity of the service contract information (step S1307). That is, the capacity of the data stored in the table is calculated, and the current usage capacity is updated by adding the calculated data capacity to the value of the current usage capacity of the service contract information DB 42a (see FIG. 4). Then, the history management unit 43c transmits a work report indicating that the service usage history is stored to the service providing server 20 (step S1309).

[Details of history deletion processing]
Next, details of the history deletion processing by the history management unit 43c will be described with reference to FIGS. 18 and 19 are flowcharts showing the flow of history deletion processing according to the first embodiment.

  As shown in the figure, this history deletion process is executed in parallel with the above-described history storage process when the history management server 40 receives a service usage history from the service providing server 20. That is, when the history management server 40 receives the service usage history from the service providing server 20 (Yes in step S1801), the history management unit 43c converts the service usage history into DOM, and the usage included in the root node name of this DOM. Based on the user identifier, a deletion rule related to the “storage period” is extracted from the service contract information of the user corresponding to the user identifier (step S1802).

  Then, the history management unit 43c determines whether there is a service usage history that has passed the storage period in the service usage history stored in the usage history DB 42c in association with the user identifier included in the root node name. (Step S1803). That is, among the service usage histories of the user stored in the usage history DB 42c (that is, each record stored in each table), the record whose “registration time” is older than “current time−storage period”. Determine if there is any.

  As a result, when there is no old record (No at Step S1803), the process proceeds to Step S1901 described later, but when there is an old record whose storage period has passed (Yes at Step S1803), the history management unit 43c The record (service usage history) is deleted from the table of the usage history DB 42c (step S1804). Then, the history management unit 43c updates the current usage capacity of the service contract information (step S1805). That is, the capacity of the data deleted from the table is calculated, and the current usage capacity is updated by subtracting the calculated data capacity from the value of the current usage capacity of the service contract information DB 42a (see FIG. 4).

  Subsequently, based on the user identifier included in the root node name of the DOM described above, the history management unit 43c determines “disk capacity limit” and “current limit” from the service contract information of the user corresponding to the user identifier. A deletion rule relating to “utilized capacity” is extracted (step S1901 in FIG. 19).

  Then, the history management unit 43c determines whether or not the “current use capacity” exceeds the “disk capacity limit” (step S1902), and if not (No at step S1902), the history deletion process is terminated. To do. On the other hand, when the “current use capacity” exceeds the “disk capacity limit” (Yes in step S1902), the history management unit 43c uses the user ID in association with the user identifier included in the root node name. The record with the oldest “registration time” is deleted from the service usage history (that is, each record stored in each table) stored in the history DB 42c (step S1903).

  Then, the history management unit 43c updates the current usage capacity of the service contract information (step S1904), as in step S1805 described above. That is, the capacity of the data deleted from the table is calculated, and the current usage capacity is updated by subtracting the calculated data capacity from the value of the current usage capacity of the service contract information DB 42a (see FIG. 4).

  Subsequently, the history management unit 43c returns to step S1901 described above, extracts “disk capacity limit” and “current usage capacity (current usage capacity after update)” from the service contract information, and updates the current “current usage capacity”. It is determined again whether the “capacity used” exceeds the “disk capacity limit” (steps S1901 and S1902). That is, the oldest records are deleted in order from the record with the oldest “registration time” until the updated “current use capacity” becomes equal to or less than the “disk capacity limit”.

[Effect of Example 1]
As described above, according to the first embodiment, the rules for storing and deleting the usage history are stored for each user (see FIG. 4), and the usage history of each user is stored and deleted based on the rules. Since the control is performed, it is possible to manage the usage history according to the rules of each user for each user, and it is possible to provide a service for browsing such usage history for each user.

  Further, according to the first embodiment, since the storage rule designating a predetermined service is stored for each user (see FIG. 4), it is possible to store only the usage history related to the designated service for each user. Become. In addition, for users, the storage capacity of usage histories is reduced by reflecting usage histories that are not worthy of storage (no need for browsing) and usage histories that do not want to be stored (do not want to be browsed) in the storage rules. And the leakage of usage history can be prevented.

  In addition, according to the first embodiment, since the deletion rule specifying the storage period (storage period) of the usage history is stored for each user (see FIG. 4), the usage history after the specified storage period has elapsed for each user. It becomes possible to delete. It is also possible to conclude a pay-as-you-go contract according to the storage period between the user and the history manager.

  In addition, according to the first embodiment, by storing a deletion rule specifying the storage capacity (disk capacity limit) of the usage history for each user, the usage history exceeding the specified disk capacity limit for each user is stored. It becomes possible to delete. It is also possible to conclude a pay-as-you-go contract according to the disk capacity limit between the user and the history manager.

  Further, according to the first embodiment, since the use history is stored based on the format information (see FIG. 5) of each service stored for each service, it is possible to manage the use history for a plurality of services in an integrated manner. .

  The system according to the first embodiment (particularly the history management server 40) has been described so far, but the present invention may be implemented in various different forms other than the above-described embodiments. Therefore, various different embodiments will be described below as (1) to (5) as the history management server according to the second embodiment.

(1) Storage Rule For example, in the first embodiment, the case where the storage target service identifier is specified as the storage rule has been described (see FIG. 4). However, the present invention is not limited to this, and FIG. As illustrated, the service identifier of the usage history to be stored, time information (information for specifying when the service is used), terminal information (information for specifying the user terminal used when using the service) ) And history items may be designated as storage rules.

  That is, in this case, the history management unit 43c stores only the designated history item in the usage history DB 42c for the service usage history that satisfies the specified service identifier, time information, and terminal information. However, it is not necessarily limited to the case where all of these are specified as storage rules, and any service identifier, time information, terminal information, history item, or a combination thereof may be specified. Further, instead of specifying what should be stored (so-called white list), it is also possible to specify what not to store (so-called black list).

  In this manner, by storing a storage rule specifying a predetermined service, a predetermined user terminal, a predetermined user terminal, and a predetermined history item for each user (see FIG. 20), It becomes possible to store only the specified history items for the service and the use history related to the user terminal at the time of use. In addition, for users, usage history and history items that are not worthy of storage (no need to browse), usage history and history items that do not want to be stored (do not want to be browsed), etc. are reflected in the storage rules. It becomes possible to reduce the storage capacity of the history and prevent the leakage of the usage history.

  In the first embodiment, the case where the service usage history is stored after determining whether or not the storage rule is satisfied has been described. However, the present invention is not limited to this, and such a determination is performed. Alternatively, all service usage histories may be stored, and the service usage history may be managed based on only the “deletion rule”.

(2) Deletion Rule In the first embodiment, the case where the storage period and the disk capacity limit are designated as the deletion rule has been described (see FIG. 4), but the present invention is not limited to this, and FIG. As illustrated in FIG. 5, not only the storage period and the disk capacity limitation, but also the service identifier, time information, terminal information, and history item of the usage history that allows deletion may be designated as the deletion rule.

  That is, in this case, the history management unit 43c, when attempting to delete a predetermined service usage history based on the storage period or the disk capacity limit, uses a service that satisfies the specified service identifier, time information, and terminal information. For the history, only the designated history item is deleted from the usage history DB 42c. However, this is not necessarily limited to the case where all of these are specified as deletion rules, as long as the storage period, disk capacity limit, service identifier, time information, terminal information, history item, or a combination thereof is specified. Good. Further, instead of designating what is permitted to be deleted, it is possible to designate what is not permitted to be deleted.

  As described above, by storing a predetermined service, a predetermined user terminal, a deletion rule specifying a predetermined history item for each user (see FIG. 21), It becomes possible to delete only the specified history item for the service and the use history related to the user terminal at the time of use. In addition, for the user, it is possible to realize efficient storage of the usage history by reflecting the usage history, history items, etc. that do not want to be deleted (which must be browsed forever) in the deletion rule.

  In the first embodiment, the case where the service usage history is deleted based on the storage period and the disk capacity limitation has been described. However, the present invention is not limited to this, and the service usage history is not deleted at all. The service usage history may be managed based only on the “storage rule” described above.

(3) History Deletion Process In the first embodiment, the case where the history deletion process is also performed in accordance with the service usage history storage process has been described. However, the present invention is not limited to this. Independently, for example, a deletion process may be performed on a service usage history of a predetermined user at a predetermined time every predetermined period.

  In the first embodiment, the case where the retention period is designated for each user has been described. However, the present invention is not limited to this, and the retention period is designated for each user and for each service. May be. That is, each user may be able to set the length of the storage period for the service usage history for each service.

  In the first embodiment, when the disk capacity limit is exceeded, the oldest record (service usage history) is deleted in order, but the present invention is not limited to this. For example, a predetermined service It may be deleted in a predetermined order, such as deleting in order from the service usage history of the identifier, or deleting in order from the service usage history with a large amount of data.

(4) Service Usage History In the first embodiment, the case where the service usage history formed by the XML file is received from the service providing server 20 has been described. However, the present invention is not limited to this, and history management is performed. Any service usage history formed in another format may be used as long as the server 40 can interpret the format.

  Further, in the first embodiment, as illustrated in FIG. 14, a case has been described in which a service usage history including various history items is transmitted to the history management server 40, but the present invention is not limited to this. Any other history item may be included as long as it is a service usage history including at least a user identifier. This is because the service usage history can be managed for each user if at least the user identifier is included.

(5) System configuration etc. In addition, among the processes described in the first embodiment, all or a part of the processes described as being automatically performed can be manually performed, or can be manually performed. All or a part of the processing described as a thing can also be automatically performed by a known method. In addition, the processing procedure, control procedure, specific name, and information including various data and parameters (for example, the information shown in FIG. 4 and FIG. 5) shown in the above-mentioned documents and drawings may be specially described. It can be arbitrarily changed except for.

  Each component of the illustrated devices (particularly, the history management server illustrated in FIG. 3) is functionally conceptual and does not necessarily need to be physically configured as illustrated. In other words, the specific form of distribution / integration of each device is not limited to that shown in the figure, and all or a part thereof may be functionally or physically distributed or arbitrarily distributed in arbitrary units according to various loads or usage conditions. Can be integrated and configured. Furthermore, each processing function performed by each device (particularly, the history management server) is realized by a CPU and a program that is analyzed and executed by the CPU, or by wired logic. It can be realized as hardware.

  In the first embodiment, each device (for example, a user terminal, a service providing server, a service provider terminal, and a history management server) that realizes the present invention has been described in terms of functions. It can also be realized by causing a computer such as a personal computer or a workstation to execute the program. That is, the various processing procedures described in the present embodiment can be realized by executing a prepared program on a computer. These programs can be distributed via a network such as the Internet. Further, these programs can be recorded on a computer-readable recording medium such as a hard disk, a flexible disk (FD), a CD-ROM, an MO, and a DVD, and can be executed by being read from the recording medium by the computer. That is, to give an example, a CD-ROM storing a user terminal program, a service providing server program, a service provider terminal program, and a history management server program as shown in the first embodiment (separately for each apparatus). CD-ROM may be distributed, and each computer may read and execute the program stored in the CD-ROM.

  As described above, the usage history management device, the usage history management method, and the usage history management program according to the present invention are useful when managing the usage history of services used by the user, and in particular, for each user. Suitable for managing the usage history according to the user's rules.

It is a figure for demonstrating the user who appears in Example 1, a service provider, and a history management trader. 1 is a configuration diagram illustrating a configuration of a system according to Embodiment 1. FIG. It is a block diagram which shows the structure of a log | history management server. It is a figure which shows the example of the information memorize | stored in service contract information DB. It is a figure which shows the example of the information memorize | stored in file format information DB. It is a figure which shows the example of the information memorize | stored in utilization log | history DB. 6 is a flowchart illustrating a flow of schema setting processing according to the first embodiment. It is a figure for demonstrating the process by an XML parser. It is a figure which shows the example of the log | history sample input into an XML parser. It is a figure which shows the example of DOM converted from the log | history sample. It is a figure which shows the example of the SQL sentence used when producing | generating a table. It is a figure which shows the example of the table produced | generated by the schema setting process. 6 is a flowchart illustrating a flow of history storage processing according to the first embodiment. It is a figure which shows the example of the service utilization log | history which a log | history management server receives. It is a figure which shows the example of DOM converted from the service utilization log | history. It is a figure which shows the example of the SQL sentence used when inserting a line into a table. It is a figure which shows the example of the table in which the service utilization log | history was stored. 6 is a flowchart illustrating a flow of history deletion processing according to the first embodiment. 6 is a flowchart illustrating a flow of history deletion processing according to the first embodiment. It is a figure which shows the example of the information memorize | stored in service contract information DB. It is a figure which shows the example of the information memorize | stored in service contract information DB.

Explanation of symbols

DESCRIPTION OF SYMBOLS 1 Network 10 User terminal 20 Service provision server 30 Service provider terminal 40 History management server 41 Communication control IF part 42 Storage part 42a Service contract information DB
42b File format information DB
42c Usage history DB
43 control unit 43a service contract unit 43b schema setting unit 43c history management unit 43d history providing unit

Claims (12)

A usage history management device that manages the usage history of services used by users,
Usage history storage means for storing the usage history for each user;
Rule storage means for storing, for each user, a rule relating to storage and / or deletion of the use history by the use history storage means;
Control means for controlling storage and / or deletion of each user's usage history by the usage history storage means based on the rules of each user stored in the rule storage means;
A usage history management device comprising: The usage history includes a service identifier for uniquely identifying the service used by the user, time information for specifying when the service is used, and a user terminal used when using the service. Information including terminal information or a combination thereof,
The rule storage means stores in advance a service identifier, time information, terminal information, history items, or a combination of these to be stored in the usage history storage means from among the new usage history of each user. Remember the rules for each user,
The control means stores, in the usage history storage means, only usage histories and / or history items corresponding to the user's storage rules stored in the storage rule storage means among the new usage histories of each user. The usage history management apparatus according to claim 1, wherein: The rule storage means stores, for each user, a deletion rule that specifies a storage period of the usage history by the usage history storage means,
The control means uses the usage history of each user already stored in the usage history storage means after the storage period specified by the deletion rule of the user stored in the rule storage means has elapsed. The usage history management device according to claim 1, wherein the usage history management device is deleted. The rule storage means stores, for each user, a deletion rule that specifies the storage capacity of the usage history stored by the usage history storage means.
The control means, when the storage capacity of each user's usage history already stored in the usage history storage means exceeds the storage capacity specified by the user's deletion rule stored in the rule storage means The usage history management apparatus according to claim 1, wherein a predetermined usage history is deleted from the usage history of the user. The usage history includes a service identifier for uniquely identifying the service used by the user, time information for specifying when the service is used, and a user terminal used when using the service. Information including terminal information or a combination thereof,
The rule storage means stores in advance a service identifier, time information, terminal information, history items, or a combination of the usage history that allows deletion from the usage history of each user already stored in the usage history storage means. Remember the specified delete rule for each user,
When the storage control means tries to delete the usage history of each user already stored in the usage history storage means, the usage history corresponding to the deletion rule of the user stored in the rule storage means Only the history item is deleted, and / or the usage history management device according to any one of claims 1 to 4. Format information storage means for storing format information for storing the usage history in the usage history storage means for each service;
The said control means stores the usage history of the said service in the said usage history storage means based on the format information of each service memorize | stored in the said format information storage means. The use history management apparatus according to one. A usage history management method for managing the usage history of services used by users,
A usage history storage step of storing the usage history in a usage history storage means for each user;
A rule storing step of storing a rule relating to storage and / or deletion of the use history by the use history storage means for each user in the rule storage means;
A control step of controlling storage and / or deletion of each user's usage history by the usage history storage unit based on the rules of each user stored in the rule storage unit;
A usage history management method characterized by including: In the rule storing step, a deletion rule specifying a storage period of the usage history by the usage history storage unit is stored in the usage history storage unit for each user.
The control step includes a usage history that has passed the storage period specified by the deletion rule of the user stored in the rule storage unit among the usage history of each user already stored in the usage history storage unit. The usage history management method according to claim 7, wherein the usage history management method is deleted. The rule storing step stores a deletion rule designating a storage capacity of the usage history by the usage history storage unit for each user in the usage history storage unit,
In the control step, when the storage capacity of each user's usage history already stored in the usage history storage means exceeds the storage capacity specified by the user's deletion rule stored in the rule storage means The usage history management method according to claim 7, wherein a predetermined usage history is deleted from the usage history of the user. A usage history management program for causing a computer to execute a usage history management method for managing a usage history of a service used by a user,
A usage history storage procedure for storing the usage history in a usage history storage means for each user;
A rule storing procedure for storing a rule relating to storage and / or deletion of the usage history by the usage history storage unit in the rule storage unit for each user;
A control procedure for controlling storage and / or deletion of the usage history of each user by the usage history storage means based on the rules of each user stored in the rule storage means;
A usage history management program characterized by causing a computer to execute. In the rule storing procedure, a deletion rule specifying a storage period of the usage history by the usage history storage unit is stored in the usage history storage unit for each user,
The control procedure includes a usage history that has passed a storage period specified by the deletion rule of the user stored in the rule storage unit among the usage history of each user already stored in the usage history storage unit. The usage history management program according to claim 10, wherein the usage history management program is deleted. In the rule storing procedure, a deletion rule specifying the storage capacity of the usage history by the usage history storage unit is stored in the usage history storage unit for each user,
In the control procedure, when the storage capacity of each user's usage history already stored in the usage history storage means exceeds the storage capacity specified by the deletion rule of the user stored in the rule storage means The usage history management program according to claim 10, wherein a predetermined usage history is deleted from the usage history of the user.

Images