JP2004348670A - Log intermediation system - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To obtain a log intermediation system having enhanced extendability and efficiency. <P>SOLUTION: The log intermediation system 1a comprises: log conversion sections 30, 31, 32, 33; I service universal data 40; J service universal data 41; and support data generation sections 50-52. A service category I, for example, an I server 10 made by a company A and its log 20 and an I server 11 made by a company B and its log 21, and a service category J, for example, a J server 12 made by a company C and its log 22 and a J server 13 made by a company D and its log 23 are located at a logs-supply side adjacent the log intermediation system 1a. External data DB (DataBase) 60-63 exist as a device supplying the external data. For example, support systems 80-82 exist as a support system supported by the log intermediation system 1a. <P>COPYRIGHT: (C)2005,JPO&NCIPI

Description

[0001]
TECHNICAL FIELD OF THE INVENTION
The present invention collects information such as logs output from a plurality of servers that perform services and a plurality of types of servers, converts the information, unifies the logs, and supplies the information to the servers. It concerns the mediation system.
[0002]
[Prior art]
As an example of the related art, IPDR / NDM-U (Internet Protocol Detail Record-Network Data Management-Usage) has a three-layer model corresponding to a plurality of support systems, and a plurality of log data acquired from a plurality of servers. , And the acquired external data are converted into IPDR 270 in a unified format, and this is provided to each support system. At that time, the data items and data formats provided to each support system were all the same for each type of service provided by the server (hereinafter referred to as "service category" as appropriate). That is, all the support systems receive the same data, and the data is stored and stored in the data format, that is, the data format after the acquisition of the external data.
[0003]
Further, as another example, collecting logs from a plurality of service systems, converting a plurality of types of logs into a unified format, and having a high scalability with a four-layer structure corresponding to a plurality of BSSs (Business Support Systems). There is one showing a system design (for example, see Patent Document 1).
[0004]
[Patent Document 1]
JP-A-2002-82849
[0005]
[Problems to be solved by the invention]
In the related art, the same data is provided to all support systems for each service category. In that case, there is a problem that unnecessary data is sent to a certain support system. In addition, external data is used to store and accumulate data after the conversion. In that case, however, there is a problem that if the specification of the support system is changed or the function is expanded, the data stored until then cannot be used. Further, there is a problem that if there is a change in the specifications of the support system or a function expansion, many modules need to be modified.
[0006]
Further, in the example shown in Patent Document 1, there is a problem that logs of a plurality of service categories are not supported, and a plurality of usage methods and a design with high expandability are not considered.
[0007]
SUMMARY OF THE INVENTION The present invention has been made to solve the above problems, and has as its object to obtain a log mediation system with improved scalability and efficiency.
[0008]
[Means for Solving the Problems]
A log mediation system according to the present invention provides a service via a network to a client in a log mediation system that supplies support data to a support system that supports a service, and outputs a log for each access from the client. A log conversion means for unifying the log output from the server and the log output from the server in a specified format to form data, and obtaining a unified data and defining a log between the support system based on the data. It has a data generating means for generating data in a format, and a data transmitting means for transmitting the data generated by the data generating means to the support system.
[0009]
BEST MODE FOR CARRYING OUT THE INVENTION
Hereinafter, an embodiment of the present invention will be described.
First, an outline of a technology related to a log mediation system common to the embodiments will be described with reference to FIG.
[0010]
As shown in FIG. 1, the basic configuration of the log mediation system 1 includes a log conversion unit 4, unified data 5, and a support data generation unit 7, and is a log that records log information from a server 2 that performs various services. The log information is obtained from the external data 6 and converted from the log information, and supplied to the support system 9 as support data 8.
[0011]
First, the operation of the log conversion unit 4 will be described. The outline of the operation of the log conversion unit 4 is as follows. A plurality of types of logs output from a plurality of different types of servers 2 are collected, and data of a unified format (hereinafter, referred to as a service category) which is a type of service to be provided is defined in advance. (Referred to as “unified data”) and save as unified data 5. One log conversion unit 4 is provided for each type of server 2, one for each service category, or one for all servers 2.
[0012]
When one log conversion unit 4 is prepared for each type of server 2, each log conversion unit 4 has a function of converting the log of the corresponding server 2 into unified data of the service category to which the server 2 belongs. Have. When one log conversion unit 4 is prepared for each service category, or when one log conversion unit 4 is provided for all servers 2 (that is, when one log conversion unit 4 corresponds to a plurality of servers 2), log conversion is performed. The unit 4 has a function of determining what type of server 2 the acquired log has been output and converting it into appropriate unified data. The service category includes a plurality of types of servers 2. For example, when the service category is Web, the types of the server 2 include Apache, IIS (Internet Information Server), and the like.
[0013]
It is assumed that the log conversion unit 4 is started in batches at regular time intervals such as every day or every week, or when a new log is generated on each server 2.
[0014]
First, the log conversion unit 4 acquires a log from one or a plurality of preset servers 2 via a network. The log to be acquired is usually the log 3 in the text format stored on the server 2, but may be in a binary format or may be directly connected to the server program to acquire the data. The log acquired by the log conversion unit 4 is stored in a disk (not shown) provided in the log mediation system as a file, and then read or directly input to the log conversion unit 4.
[0015]
Next, the log conversion unit 4 converts the read log into data in a unified format defined in advance for each service category. In the normal log, one record (one line) of a log is generated for one access or operation of a client, that is, a computer or a mobile terminal. The log of one record includes the access date and time of the client or the date and time when the log was recorded, the file name accessed by the client, the environment of the client machine (that is, OS, client software name, version, etc.), the contents of the request, Data such as the protocol used between the servers is recorded.
[0016]
The log conversion unit 4 reads each record of the log and converts it into a format unified for each service category. Since the format and meaning of the log output by the server 2 are different, when performing the conversion, if necessary, (i) data having the same meaning but different notation (for example, if the data format or data unit is (Ii) extracting only necessary parts from a certain character string, (iii) calculating required values from a plurality of data, and (iv) converting the contents of one log into a unified format. In some cases, (v) generating one record in a unified format from data values recorded in a plurality of log records, and the like.
[0017]
Finally, the log conversion unit 4 saves the unified data on the disk. It is desirable to save the data in a highly versatile storage format such as a relational database or an XML (Extensible Markup Language) text file. In any form, such as the binary form of However, the condition in this case is a format in which the stored data can be read by the subsequent support data generation unit 7.
[0018]
In this way, by converting the data into the unified format for each service category and storing it, even if the logs are output from different types of servers 2 in the same service category, the log data can be uniformly handled in the subsequent processing. There is a merit. Also, for example, even if the support system 9 and the support data generator 7 are changed, it is not necessary to change the log converter 4. Furthermore, since external data other than the log has not been obtained at this time, even if the support system 9 or the support data generation unit 7 is changed, the data in the unified format stored up to that time is changed. It can be used without need.
[0019]
Next, the operation of the support data generation unit 7 will be described. The outline of the operation of the support data generation unit 7 is that it is necessary to acquire external data from unified data and external data 6 unified for each of a plurality of types of service categories, and to specify the acquired data in advance with the support system 9. Generating sufficient data and outputting the generated data to the support system 9. Since the support data generators 7 and the support systems 9 have a one-to-one correspondence, the same number of support data generators 7 as the support systems 9 exist.
[0020]
The activation of the support data generation unit 7 is performed in a fixed time interval such as (i) every day, every week, or (ii) in real time when a log in a unified format is newly generated, or (iii) 3.) Start the operation at any point when a request is received from the corresponding support system 9. The activation timing of each support data generation unit 7 does not need to be simultaneous.
[0021]
First, the support data generation unit 7 acquires one or a plurality of data unified for each service category. Next, the support data generation unit 7 acquires necessary external data from the external data DB (database) 6. The external data to be obtained differs depending on the corresponding support data generator 7. For example, in the case of a support data generation function that assumes billing, a service to be charged or external data indicating a content and a usage fee for the service is required. It is considered that external data indicating information and content information is required.
[0022]
The support data generation unit 7 selects, tabulates, combines, and the like the acquired unified data and external data, and finally generates necessary and sufficient data for each of the support systems 9 defined in advance. Output.
[0023]
Since the operation of the support data generation unit 7 differs depending on the individual support data generation units 7 and also differs depending on the mounting method, the entire operation cannot be described in detail here. (File Transfer Protocol) service will be briefly described.
[0024]
When performing charging, the name of the support system is "charging service", the support data transmitted to the charging service is "charging data", and the support data generating unit 7 for generating charging data is "charging data generating unit". Shows the operation. The details of the support system related to the billing service will be described in Embodiments 3, 4, and 5 below.
[0025]
First, the billing data generation unit acquires streaming and FTP unified data and a billing rule existing as external data. In the unified data, information "who used what and how much" is recorded, and in the charging rule, information "what, how much, how much, and how much" is specified. The specific method of determining the usage fee depends on each operation rule. For example, if (a) streaming determines the fee based on the playback time of each content, and (b) FTP determines the usage fee based on the number of transfer bytes regardless of the content, the charging rules acquired from the outside are: , (A) for all the streaming contents, a charge generated when the contents are reproduced for one second, and (b) a charge generated when transferring 1 Kbyte by FTP are specified in a predetermined format. In the unified data, the user name, the file name of the used streaming content, and the usage amount, for example, the playback time on the client in the case of streaming, the number of K bytes transferred in the case of FTP, and the like are recorded.
[0026]
Next, the billing data generation unit tallies the acquired unified data and calculates a fee for each user. More specifically, referring to the unified data, in the case of streaming, the data “user A, file A, and total time x during which user A played file A” is totaled for all combinations of user names and file names. I do. In the case of the FTP, it is only necessary to total the data for each user, and the data “user B, number of transferred K bytes x” is totaled for all the user names. With respect to this aggregated data, a charge per unit time and a unit transfer amount is obtained from the charging rule, and multiplied by the reproduction time and the transfer amount, "User A, file A, and user A have reproduced file A. Data such as “total time x, usage fee y (yen)” on the left, and “user B, number of transferred K bytes x, usage fee y (yen) on the left” are generated.
[0027]
Finally, the data collected by the above method is output to the support system 9 that supports the corresponding billing system. It is assumed that the billing system that receives the data setstles the user or performs processing such as generating a screen that displays the billing status up to that point in response to the introduction from the user or the billing administrator. You.
[0028]
As described above, by managing the charges for a plurality of services such as streaming and FTP collectively, there is an advantage that the administrator and the user can easily understand. Also, setting different types of services, for example, a discount set fee, can be easily realized by describing the set discount in the charging rule.
By providing a support data generation unit 7 corresponding to each support system and providing specific necessary and sufficient data for each support system 9, there is an advantage that each support system 9 does not need to acquire unnecessary data. is there.
[0029]
Although not shown in the above example, when the support data generation unit 7 starts operation in response to a request from the support system 9, the unified data is designated by specifying a specific parameter in the request from the support system 9. It is possible to specify the range to be totaled. For example, by designating a user name as a parameter, only billing information relating to the designated user can be obtained. For example, by giving the date and time as a parameter, it is possible to acquire only the billing information relating to or after the designated date and time, and by using this function, the above-described billing system saves once received data to a local disk. After that, after that, the support data generation unit 7 is activated by designating the date and time, and only the difference from the previous time is received and added to the previously saved data, so that the processing time can be reduced.
[0030]
Embodiment 1 FIG.
The log mediation system 1a according to the first embodiment of the present invention will be described with reference to FIGS. FIG. 2 is a diagram showing a configuration of the log mediation system 1a according to the first embodiment, and FIG. 3 is a diagram showing a state in which logs are accumulated by access from a client of the log mediation system 1a. FIG. 4 is a diagram showing the flow of BSS mediation in the log mediation system 1a.
[0031]
As shown in FIG. 2, the log mediation system 1a includes log conversion units 30, 31, 32, and 33, I service unified data 40, J service unified data 41, and support data generation units 50 to 52. Is done. For the log mediation system 1a, the service category I, for example, the company A I server 10 and its log 20, the company B I server 11 and its log 21, and the service category J, for example, the company C J server 12 and its log The log 22, the J server 13 manufactured by Company D and its log 23 are on the side that supplies logs, the external data DBs 60 to 63 are devices that supply external data, and as a support system supported by the log mediation system 1a, There are support systems 80-82.
[0032]
The A-company I server 10 and the B-company I server 11 are different types of servers, but provide the same or the same type of service (in this case, service category I) to clients via a network. When there is access from the client, the access information and the information of the client are stored in the logs 20 and 21. The same kind of service means, for example, Web, streaming, FTP, etc., and the different kind of device means Apache, IIS, etc. for Web, and Windows (registered trademark) Media, RealSystem, etc. for streaming. I do. That is, Apache and IIS are different types of devices, but are servers that provide the same type of service Web.
[0033]
The J server 12 made by C company and the J server 13 made by D company are different types of devices like the I server 10 made by A company and the I server 11 made by B company, and the same or the same kind of service J is connected to the network. Is a server provided to clients via the Internet. When there is access from the client, the access information and the information of the client are stored in the logs 22 and 23. In FIG. 1, these servers are illustrated as one server 2, but a plurality of servers may be load-balanced.
[0034]
The log output from each server and stored in the logs 20 to 23 is a set of log records. The log record is generated when a client accesses the server. Is a set of information sent from. The log is stored in a file in a text format or a binary format on a disk on a server, or is referred to directly from the outside via a network, or is stored directly on a disk of an external computer (hereinafter referred to as "all" Log "). Since the I-server 10 manufactured by Company A, the I-server 11 manufactured by B, the J-server 12 manufactured by C, and the J-server 13 manufactured by D are all different, the log data items and data formats of the logs 20 to 23 are usually different.
[0035]
The log conversion units 30 to 33 correspond one-to-one with the I-server 10 manufactured by A company, the I server 11 manufactured by B company, the J server 12 manufactured by C company, and the J server 13 manufactured by D company, respectively. There are as many as the types of servers. Each of the log converters 30 to 33 acquires a log output from the corresponding server, converts the log into a unified data item and data format for each service category of the corresponding server, and obtains I service unified data 40 and J service unified data. 41.
[0036]
The external data DBs 60 to 63 correspond to at least one of the support data generators 50 to 52, and have different data contents. The external data recorded in the external data DBs 60 to 63 is data for complementing the data of the I service unified data 40 and the J service unified data 41, and the data finally required in the support systems 80 to 82 is stored in advance. Has been saved.
[0037]
The support data generation units 50 to 52 correspond one-to-one with the support systems 80 to 82, respectively, and are the same in number as the support systems. The support data generation units 50 to 52 respectively acquire all the unified data of the I service unified data 40 and the J service unified data 41 and zero or more external data of the external data DBs 60 to 63, and obtain the acquired unified data and external data. The data is selected, tabulated, combined, and generates support data 70 to 72 having data items and data formats defined with the corresponding support system, and provides the support data to the corresponding support systems 80 to 82.
[0038]
Each of the support data generation units 50 to 52 can provide a parameter at the start of processing. At this time, only the record corresponding to the given parameter is extracted from the logs 20 to 23, and only the data corresponding to the parameter is extracted. Has a function of generating the support data 70 to 72 of. For example, the support systems 80 to 82 can activate the support data generation units 50 to 52 using a certain user name as a parameter, and acquire the support data 70 to 72 including only the data related to the specified user name. Each of the support systems 80 to 82 has a function of supporting services provided by the I-server 10 manufactured by A, the I-server 11 manufactured by B, the J-server 12 manufactured by C, and the J-server 13 manufactured by D based on the acquired data. Having.
[0039]
Next, the operation of the log mediation system 1a will be described.
FIG. 3 shows a situation where the client accesses the I-server 10 manufactured by A, the I-server 11 manufactured by B, the J-server 12 manufactured by C, and the J-server 13 manufactured by D. The user accesses one or more load-balanced servers 94 from the client computers 90 and 91 and the portable terminal 92 via the network 93 to receive the service. At this time, the server 94 records data such as client access information, client information, and access date and time as a log 95.
[0040]
Next, in FIG. 2, the log conversion units 30 to 33 perform processing in real time (here, real time refers to the time when unified data is generated, and is used in the same sense hereinafter) or periodically (that is, batch processing). ), Logs 20 to 23 are collected from the I-server 10 manufactured by the company A, the I-server 11 manufactured by the company B, the J-server 12 manufactured by the company C, and the J-server 13 manufactured by the company D, to generate data unified for each service category. The I service unified data 40 and the J service unified data 41 are stored in the XML format or the relational database format.
[0041]
Next, one or more of the support data generation units 50 to 52 may execute the I service unified data 40 and the J service in real time, periodically, or at a time when a request is received from each of the support systems 80 to 82. Collecting and acquiring unified data of the unified data 41, further acquiring external data from the external data DBs 60 to 63, selecting, tabulating, combining the acquired unified data and external data, and finally, a corresponding support system Provide necessary and sufficient data for 80-82.
[0042]
Also, when the support data generation units 50 to 52 receive a request from the support systems 80 to 82 and start up, if a parameter is specified in the request, the support data generation units 50 to 52 Data (or all data other than unnecessary data) can be generated, and data different from data provided when no parameter is specified can be provided to the support systems 80 to 82. For example, when a user name is specified in a request from the support systems 80 to 82, only the data recorded when the specified user accesses the server is extracted from the unified data, and the processing is performed. Only the data regarding the performed user is transmitted to the support systems 80 to 82.
[0043]
Next, the operation of the support data generation units 50 to 52 will be described with reference to the flowchart of FIG. The support data generation units 50 to 52 activate the support data generation function in real time, periodically, or at a time when a request is received from the support system 80 to 82 (step ST101). 52 acquires necessary unified data (step ST102). Next, external data is acquired from the external data DBs 60 to 63 (step ST103).
[0044]
Next, the support data generation units 50 to 52 start processing in response to a request from the support system 80 to 82, and determine whether or not the request from the support system includes a request parameter (step ST104). If it is included (YES), processing is performed on only necessary data or all data other than unnecessary data in accordance with the value of the received parameter to generate data in a unified format (step ST105). . On the other hand, if the parameter is not included (NO), the process is performed on all the data as usual, to generate data in a unified format (step ST106), and the generated data is transmitted to the support system (step ST106). Step ST107). Based on the received data, the support systems 80 to 82 receiving the data as described above, based on the received data, use the I server 10 manufactured by A, the I server 11 manufactured by B, the J server 12 manufactured by C, and the D server manufactured by D. The service of the J server 13 is supported.
[0045]
As described above, according to the first embodiment, necessary and sufficient data can be acquired in each support system by changing data to be provided for each support system. Also, when adding a new support system or changing the specifications of an existing support system, it is only necessary to add or change the module data format of the corresponding support system. Furthermore, when adding a new support system or changing the use of an existing support system, it is possible to use the stored unified data without changing it.
This makes it possible to easily add and extend various support systems to an environment that provides a plurality of types of services.
[0046]
Embodiment 2 FIG.
A log mediation system 1b according to Embodiment 2 of the present invention will be described with reference to FIG. FIG. 5 is a diagram showing a configuration of the log mediation system 1b according to the second embodiment. In the above-described first embodiment, the architecture of the present invention has been described. In the second embodiment, an embodiment in which the present invention is implemented will be described as analysis of a user's usage trend with respect to a streaming service. That is, the second embodiment is a specific example in which one support system is applied to one service category.
[0047]
The log mediation system 1b according to the second embodiment includes log conversion units 130 and 131, stream unified data 140, and a usage trend analysis data generation unit 152. The log 120, the streaming server 111 manufactured by Company B and its log 121 are on the side supplying the log, and the content information DB 162 and the user information DB 163 provide information to the log mediation system 1b, and are supported by the log mediation system 1b. There is a usage trend analysis system 182 as a support system.
[0048]
The streaming server 110 manufactured by company A and the streaming server 111 manufactured by company B are different types of devices, and are servers that provide streaming services to clients via a network. The information is stored in the logs 120 and 121. In FIG. 5, each of the streaming server 110 manufactured by the company A and the streaming server 111 manufactured by the company B is illustrated as one server, but a plurality of servers with load distribution may be used.
[0049]
The logs 120 and 121 are logs output from the streaming server 110 manufactured by the company A and the streaming server 111 manufactured by the company B. The logs 120 and 121 are different data because they are different servers.
[0050]
The log conversion units 130 and 131 collect logs output from the streaming server 110 manufactured by Company A and the streaming server 111 manufactured by Company B, convert them into data items and formats unified by streaming, and unify the streams into stream unified data 140. Save as data.
[0051]
The content information DB 162 and the user information DB 163 are databases including data for complementing the stream unified data when the usage trend analysis data 172 is generated from the stream unified data. For example, in the content information DB, the file name, title, classification (eg, music, movie, drama, etc.) of each content provided to the user from the streaming server 110 manufactured by Company A and the streaming server 111 manufactured by Company B, Includes copyright owners. The user information DB includes, for example, the user name, name, age, occupation, mail address, and the like of the user who receives the streaming service.
[0052]
The usage trend analysis data generation unit 152 obtains information from the stream unified data 140, the content information DB 162, and the user information DB 163, selects, totals, and combines the obtained data, generates usage trend analysis data 172, and uses the usage trend analysis data 172. It has a function to be provided to the analysis system 182.
[0053]
The usage trend analysis system 182 has a function of supporting services provided by the streaming server 110 manufactured by Company A and the streaming server 111 manufactured by Company B based on the acquired data.
[0054]
Next, the operation of the log mediation system 1b will be described.
First, the log converters 130 and 131 collect the logs 120 and 121 in real time or periodically from the streaming server 110 manufactured by the company A and the streaming server 111 manufactured by the company B, generate streaming unified data, and output the data in the XML format or It is stored in the streaming unified data 140 in a relational database format.
[0055]
Next, the usage trend analysis data generation unit 152 acquires the unified data from the stream unified data 140 at any time, in real time, periodically, or when a request is received from each support system. External data is acquired from the user information DB 163, the acquired unified data and the acquired external data are selected, tabulated, and combined to generate usage trend analysis data 172, and provided to the usage trend analysis system 182.
[0056]
Further, when a parameter is specified in the request received from the usage trend analysis system 182 by the usage trend analysis data generation unit 152, the usage trend analysis data generation unit 152 generates only necessary data according to the parameter, and sets the parameter. Data different from the data provided when not specified can be provided to the usage trend analysis system 182. For example, when the user name is specified in the request from the usage trend analysis system 182, only the data recorded by the specified user accessing the server is extracted from the unified data, and the processing is performed. Only the data on the performed user is transmitted to the usage trend analysis system 182.
[0057]
The usage trend analysis system 182 that has received the data executes a process of analyzing the usage trend of the service provided by the A company streaming server 110 and the B company streaming server 111 based on the received data.
[0058]
As described above, according to the second embodiment, when the logs of a plurality of streaming distribution servers are processed by the four-layer model, the unified data stored is unchanged even if the specifications of the support system are changed. It is possible to use it.
[0059]
Embodiment 3 FIG.
A log mediation system 1c according to Embodiment 3 of the present invention will be described with reference to FIG. FIG. 6 is a diagram showing a configuration of the log mediation system 1c according to the third embodiment. In the above-described first embodiment, the architecture of the present invention is shown, and in the second embodiment, a form in which the use trend analysis of streaming is performed is shown as a specific example. However, in the third embodiment, streaming and Web service This is a specific example of a case where one support system is applied to a plurality of service categories for performing charging.
[0060]
The log mediation system 1c of the third embodiment includes log conversion units 120 to 123, stream unified data 140, Web unified data 141, and a billing data generation unit 150. The server 110 and its log 120, the B company streaming server 111 and its log 121, the C company Web server 112 and its log 122, the D company Web server 113 and its log 123 are on the log supply side, and A charging rule DB 160 provides information to the log mediation system 1c, and a charging system 180 is a support system supported by the log mediation system 1c.
[0061]
The streaming server 110 manufactured by company A and the streaming server 111 manufactured by company B are different types of devices, and are servers that provide streaming services to clients via a network. The information is stored in logs 120 and 121, respectively. Further, the Web server 112 manufactured by Company C and the Web server 113 manufactured by Company D are different devices, and are servers that provide Web services to clients via a network. The information is stored in logs 122 and 123, respectively. In FIG. 6, each of the streaming server 110 manufactured by the company A, the streaming server 111 manufactured by the company B, the web server 112 manufactured by the company C, and the web server 113 manufactured by the company D are illustrated as one server. It may be.
[0062]
The logs 120 to 123 are logs output from the A company streaming server 110, the B company streaming server 111, the C company Web server 112, and the D company Web server 113. The streaming server 110 manufactured by Company A and the streaming server 111 manufactured by Company B are servers that provide the same streaming service, but the logs 120 and 121 output are different data because they are different servers.
The Web server 112 manufactured by Company C and the Web server 113 manufactured by Company D are servers that provide the same Web service. However, since they are different servers, the output log 122 and log 123 are different data.
[0063]
The log conversion units 130 and 131 have a function of collecting logs output from the streaming server, converting the logs into data items and formats unified by streaming, and forming the stream unified data 140. The log conversion units 132 and 133 have a function of collecting logs output from the Web server, converting the logs into data items and formats unified by the Web, and converting the data into Web unified data 141.
[0064]
The charging rule DB 160 is a database that stores information for complementing the stream unified data 140 and the Web unified data 141, and stores data finally required by the charging system 180. In the charging rule DB, for example, each stream content and its price, each Web service and its price, and the like are recorded.
[0065]
The billing data generation unit 150 has a function of selecting, tabulating, and combining the stream unified data 140, the Web unified data 141, and the data acquired from the billing rule DB to generate the billing data 170, and providing the billing system 180 with the billing data 170.
[0066]
The billing system 180 has a function of supporting services provided by the streaming server 110 manufactured by Company A, the streaming server 111 manufactured by Company B, the Web server 112 manufactured by Company C, and the Web server 113 manufactured by Company D based on the acquired data. .
[0067]
Next, the operation of the log mediation system 1c will be described.
First, the log converters 130 and 131 collect the logs 120 and 121 in real time or periodically from the streaming server 110 manufactured by Company A and the streaming server 111 manufactured by Company B, generate stream unified data 140, and generate the XML format or the relational data. Save in database format. Similarly, the log conversion units 132 and 133 collect the logs 122 and 123 from the C-company Web server 112 and the D-company Web server 113 in real time or periodically, generate Web unified data 141, and generate Or in the form of a relational database.
[0068]
Next, the charging data generation unit 150 acquires data from the stream unified data 140, the Web unified data 141, and the charging rule DB 160 at any time in real time, periodically, or when a request is received from the charging system. These acquired data are selected, totalized, and combined to finally generate pre-defined charging data 170 and provide it to the charging system 180.
[0069]
When a parameter is specified in the request received from the charging system 180 by the charging data generating unit 150, the charging data generating unit 150 generates only necessary data according to the parameter, and when the parameter is not specified, Data different from the provided data can be provided to the support system. For example, when the user name is specified in the request from the billing system 180, only the data recorded when the specified user accesses the server is extracted from the unified data, and the processing is performed. Only data relating to the user is transmitted to billing system 180.
[0070]
The charging system 180 that has received the data is provided by the streaming server 110 manufactured by A company, the streaming server 111 manufactured by B company, the Web server 112 manufactured by C company, and the Web server 113 manufactured by D company based on the received data. Execute the billing process for the existing service.
[0071]
As described above, according to the third embodiment, it is possible to process logs of a plurality of service categories. Also, by handling logs of a plurality of service categories, for example, it is possible to unify the charging of the Web service and the streaming. In this case, if the charging is performed at one place, the user can use which service and how much. It is easier to manage how much you paid. Further, for example, it is possible to perform more detailed click analysis and to analyze more detailed user preference by combining Web service and streaming usage trend analysis.
[0072]
Embodiment 4 FIG.
A log mediation system 1d according to Embodiment 4 of the present invention will be described with reference to FIG. FIG. 7 is a diagram showing the configuration of the log mediation system 1d according to the fourth embodiment.
[0073]
The log mediation system 1d according to the fourth embodiment includes log conversion units 130 and 131, stream unified data 140, charging data generation unit 150, quality evaluation data generation unit 151, and usage trend analysis data generation unit 152. On the other hand, for example, the streaming server 110 manufactured by Company A and its log 120, and the streaming server 111 manufactured by Company B and its log 121 are on the log supply side, and the charging rule DB 160, the system configuration information DB 161, the content information DB 162, The user information DB 163 provides information to the log mediation system 1d, and a support system supported by the log mediation system 1d includes a billing system 180, a quality evaluation system 181, and a usage trend analysis system 182.
[0074]
The streaming server 110 manufactured by the company A and the streaming server 111 manufactured by the company B are different devices, and are servers that provide streaming services to the clients via the network. It is stored in logs 120 and 121. In FIG. 7, each of the streaming server 110 manufactured by the company A and the streaming server 111 manufactured by the company B is illustrated as one server, but a plurality of servers with load distribution may be used.
[0075]
The logs 120 and 121 are logs output from each of the streaming server 110 manufactured by Company A and the streaming server 111 manufactured by Company B. The streaming server 110 manufactured by the company A and the streaming server 111 manufactured by the company B are servers that provide the same streaming service, but since they are different servers, the output logs 120 and 121 are different data.
[0076]
Each function of the log converters 130 and 131 has a function of acquiring a log output from the streaming server, converting the log into data items and data formats unified by streaming, and storing the converted data in the stream unified data 140 as stream unified data. .
[0077]
The charging rule DB 160, the system configuration information DB 161, and the content information DB 162 are databases storing information for complementing the stream unified data, and are finally required by the charging system 180, the quality evaluation system 181, and the usage trend analysis system 182. Data is stored.
[0078]
For example, the charging rule DB 160 records each stream content and its price, each Web service and its price, and the like. The system configuration information DB 161 records the arrangement and specifications of servers constituting the system, the configuration of the network, and the like. In the content information DB 162, file names, titles, classifications (for example, music, movies, dramas, etc.), copyrights, and the like of each content provided to the user from the streaming server 110 manufactured by the company A and the streaming server 111 manufactured by the company B are provided. Rights holders are included. Further, the user information DB 163 includes a user name, a name, an age, an occupation, an e-mail address, and the like of a user who receives a streaming service from the streaming server of the company A streaming server 110 and the company B streaming server 111.
[0079]
The billing data generation unit 150 has a function of selecting, tabulating and combining data obtained from the stream unified data 140 and the billing rule DB 160 to generate billing data 170 and providing the billing data 180 to the billing system 180.
[0080]
The quality evaluation data generation unit 151 acquires data from the stream unified data 140 and the system configuration information DB, selects, totals, and combines the acquired data to generate quality evaluation data 171, and provides the quality evaluation data 181 to the quality evaluation system 181. Having.
[0081]
The usage trend analysis data generation unit 152 obtains data from the stream unified data 140, the content information DB 162, and the user information DB 163, selects, tabulates, and combines the obtained data to generate usage trend analysis data 172, and performs usage trend analysis. It has a function to be provided to the stem 182.
[0082]
The billing system 180, the quality evaluation system 181, and the usage trend analysis system 182 have a function of supporting services provided by the A company streaming server 110 and the B company streaming server 111 based on the acquired data.
[0083]
Next, the operation of the log mediation system 1d will be described.
First, the log converters 130 and 131 collect the logs 120 and 121 in real time or periodically from the streaming server 110 manufactured by Company A and the streaming server 111 manufactured by Company B to generate unified stream data, and generate the XML format or Save in relational database format.
[0084]
Next, the billing data generation unit 150 acquires data from the stream unified data 140 and the billing rule DB 160 at any time in real time, periodically, or when a request is received from the billing system 180, and The billing data 170 is generated by selecting, tabulating, and combining the billing data 170 and provided to the billing system 180.
[0085]
When a parameter is specified in the request received from the charging system 180 by the charging data generating unit 150, the charging data generating unit 150 generates only necessary data according to the parameter and does not specify the parameter. Data different from the data provided to the support system can be provided to the support system. For example, when the user name is specified in the request from the billing system 180, only the data recorded when the specified user accesses the server is extracted from the unified data, and the processing is performed. Only data relating to the user is transmitted to billing system 180.
[0086]
The quality evaluation data generation unit 151 obtains data from the stream unified data 140 and the system configuration information DB 161 at any time in real time, periodically, or at the time when a request is received from the quality evaluation system 181. The quality evaluation data 171 is generated by selection, aggregation, and combination, and is provided to the quality evaluation system 181.
[0087]
Further, when a parameter is specified in a predetermined format in the request received from the quality evaluation system 181 by the quality evaluation data generation unit 151, the quality evaluation data generation unit 151 outputs only necessary data according to the parameter. The generated data can be provided to the support system different from the data provided when no parameter is specified. For example, when the host name is specified in the request from the quality evaluation system 181, only the data recorded in the server having the specified host name is extracted from the unified data and processed, and the processing related to the specified host is performed. Send only the data to the quality assessment system.
[0088]
The usage trend analysis data generation unit 152 obtains data from the stream unified data 140, the content information DB 162, and the user information DB 163 at any time in real time, periodically, or when a request is received from the usage trend analysis system 182. Then, the obtained data is selected, tabulated, and combined to generate usage trend analysis data 172, and provided to the usage trend analysis system 182.
[0089]
When the usage trend analysis data generation unit 151 specifies a parameter in the request received from the usage trend analysis system 182, the usage trend analysis data generation unit 152 generates only necessary data according to the parameter, and Can be provided to the support system that is different from the data provided when the is not specified. For example, when the content name is specified in the request from the usage trend analysis system 182, only the data recorded by accessing the specified content is extracted from the unified data, and the processing is performed. The data of only the data related to the content is transmitted to the usage trend analysis system 182.
[0090]
Based on the received data, the charging system 180, the quality evaluation system 181, and the usage trend analysis system 182, which have received the data, charge the services provided by the A-company streaming server 110 and the B-company streaming server 111. Perform processing, quality evaluation and usage trend analysis.
[0091]
As described above, according to the fourth embodiment, it is possible to handle a plurality of support systems in a unified manner. Therefore, it is not necessary to separately construct a dedicated system for each support system, and when developing a new support system, it is possible to add only some modules to the present system.
[0092]
Embodiment 5 FIG.
A log mediation system 1e according to Embodiment 5 of the present invention will be described with reference to FIG. FIG. 8 is a diagram showing the configuration of the log mediation system 1e according to the fifth embodiment. The fifth embodiment is a specific example in which a plurality of support systems are applied to a plurality of service categories for performing charging, usage trend analysis, and service quality evaluation for streaming and Web services.
[0093]
The log mediation system 1e according to the fifth embodiment includes log conversion units 130 to 133, stream unified data 140, Web unified data 141, a charging data generation unit 150, a quality evaluation data generation unit 151, and usage trend analysis data generation. For example, a streaming server 110 manufactured by Company A and its log 120, a streaming server 111 manufactured by Company B and its log 121, a Web server 112 manufactured by Company C and its log 122, and a Web server manufactured by D The server 113 and its log 123 are on the log supply side, and the charging rule DB 160, the system configuration information DB 161, the content information DB 162, and the user information DB 163 provide information to the log mediation system 1e. Support system supported by Gold systems 180, quality evaluation system 181, there is a usage trend analysis system 182.
[0094]
The streaming server 110 manufactured by company A and the streaming server 111 manufactured by company B are different devices and provide a streaming service to the client via a network. When the client accesses the server, the access information and the client information are logged. 120 and 121. The C company Web server 112 and the D company Web server 113 are different devices and provide a Web service to the client via a network. When the client accesses the server, the access information and the client information are logged. The data is stored in 122 and 123. In FIG. 8, each of the streaming server 110 manufactured by the company A, the streaming server 111 manufactured by the company B, the web server 112 manufactured by the company C, and the web server 113 manufactured by the company D are illustrated as one server. It may be.
[0095]
Logs 120 to 123 are logs output from each of the streaming server 110 manufactured by A company, the streaming server 111 manufactured by B company, the Web server 112 manufactured by C company, and the Web server 113 manufactured by D company. The streaming server 110 manufactured by the company A and the streaming server 111 manufactured by the company B are servers that provide the same streaming service, but since they are different servers, the output logs 120 and 121 are different data. Similarly, the Web server 112 manufactured by Company C and the Web server 113 manufactured by Company D are servers that provide the same Web service, but since they are different servers, the log 122 and the log 123 output are different data.
[0096]
The log converters 130 and 131 have a function of acquiring logs output from the streaming server, converting the logs into data items and formats unified by streaming, and converting the data into stream unified data 140. Similarly, the log conversion units 132 and 133 have a function of acquiring a log output from a Web server, converting the log into data items and formats unified by the Web, and converting the data into Web unified data 141.
[0097]
The charging rule DB 160, the system configuration information DB 161, the content information DB 162, and the user information DB 163 are databases for supplementing the stream unified data and the web unified data, and are any of the charging system 180, the quality evaluation system 181, and the usage trend analysis system 182. The necessary data is stored in advance in the support system.
[0098]
The billing data generation unit 150 acquires data from the stream unified data 140, the Web unified data 141, and the billing rule DB 160, selects, tabulates, and combines the acquired data, generates billing data 170, and provides the billing system 180. It has a function to do.
[0099]
The quality evaluation data generation unit 151 acquires data from the stream unified data 140, the Web unified data 141, and the system configuration information DB 161. It has a function of selecting, tabulating and combining the acquired data to generate quality evaluation data 171 and providing the quality evaluation data 171 to the quality evaluation system 181.
[0100]
The usage trend analysis data generation unit 152 acquires data from the stream unified data 140, the Web unified data 141, the content information DB 162, and the user information DB 163. It has a function of selecting, tabulating and combining the acquired data to generate usage trend analysis data 172 and providing the data to the usage trend analysis system 182.
[0101]
The billing system 180, the quality evaluation system 181, and the usage trend analysis system 182, based on the acquired data, use the streaming server 110 manufactured by A company, the streaming server 111 manufactured by B company, the web server 112 manufactured by C company, and the web server 113 manufactured by D company. Has the function to support the services provided by
[0102]
Next, the operation of the log mediation system 1e will be described.
First, the log converters 130 and 131 collect the logs 120 and 121 in real time or periodically from the streaming server 110 manufactured by Company A and the streaming server 111 manufactured by Company B to generate unified streaming data, and output the data in XML format or Save in relational database format. Similarly, the log converters 132 and 133 collect the logs 122 and 123 in real time or periodically from the Web server 112 manufactured by Company C and the Web server 113 manufactured by Company D, generate the Web unified data 141, and generate the XML format. Or in the form of a relational database.
[0103]
Next, the billing data generation unit 150 acquires and acquires the data from the stream unified data 140, the Web unified data 141, and the billing rule DB 160 at any timing of real time, periodic, or when a request is received from the billing system. The data is selected, tabulated and combined, and finally, pre-defined charging data 170 is generated and provided to the charging system 180.
[0104]
Also, if a parameter is specified in a predetermined format in the request received by the charging data generation unit 150 from the charging system 180, the charging data generation unit 150 generates only necessary data according to the parameter, Data different from the data provided when no parameter is specified can be provided to the support system. For example, when the user name is specified in the request from the billing system 180, only the data recorded when the specified user accesses the server is extracted from the unified data, and the processing is performed. Only data relating to the user is transmitted to billing system 180.
[0105]
The quality evaluation data generation unit 151 obtains data from the stream unified data 140, the Web unified data 141, and the system configuration information DB 161 at any timing in real time, periodically, or when a request is received from the quality evaluation system 181. The acquired data is selected, tabulated, combined, and finally generates predefined quality evaluation data 171 and provides it to the quality evaluation system 181.
[0106]
Further, when a parameter is specified in a predetermined format in the request received from the quality evaluation system 181 by the quality evaluation data generation unit 151, the quality evaluation data generation unit 151 outputs only necessary data according to the parameter. The generated data can be provided to the support system different from the data provided when no parameter is specified. For example, when the host name is specified in the request from the quality evaluation system 181, only the data recorded in the server having the specified host name is extracted from the unified data and processed, and the processing related to the specified host is performed. Only the data is transmitted to the quality evaluation system 181.
[0107]
The usage trend analysis data generation unit 152 transmits the stream unified data 140, the Web unified data 141, the content information DB 162, and the user information DB 163 in real time, periodically, or at a timing when a request is received from the usage trend analysis system 182. The data is acquired, the acquired data is selected, totalized, combined, and finally, usage trend analysis data 172 that is defined in advance is generated and provided to the usage trend analysis system 182.
[0108]
Also, when a parameter received in a request received by the usage trend analysis data generation unit 152 from the usage trend analysis system 182 is specified in a format that is defined in advance, the usage trend analysis data generation unit 152 determines a required value in accordance with the parameter. Only the data can be generated, and data different from the data provided when no parameter is specified can be provided to the support system. For example, when the content name is specified in the request from the usage trend analysis system 182, only the data recorded by accessing the specified content is extracted from the unified data, and the processing is performed. The data of only the data related to the content is transmitted to the usage trend analysis system 182.
[0109]
Based on the received data, the charging system 180, the quality evaluation system 181, and the usage trend analysis system 182, which have received the data, provide a streaming server 110 manufactured by A company, a streaming server 111 manufactured by B company, a web server 112 manufactured by C company, The charge processing, quality evaluation, and usage trend analysis for the service provided by the company Web server 113 are executed.
[0110]
As described above, according to the fifth embodiment, a plurality of support systems can be uniformly handled for a plurality of types of services. Therefore, there is no need to construct a dedicated system for each set of service and support system. In other words, if there are N types of normal services and M types of support systems, N × M systems will be required, but by using the log mediation system 1e, one system can handle all of them in a unified manner. It is possible to deal with changes in specifications, addition of functions, etc., only by modifying and adding some modules.
[0111]
【The invention's effect】
As described above, according to the present invention, it is possible to obtain necessary and sufficient data for each support system, and when adding a new support system or changing the specifications of an existing support system. In doing so, it is possible to respond to the support system only by adding or changing the module data format of the corresponding support system.
This makes it possible to easily add and extend various support systems to an environment that provides a plurality of types of services.
[Brief description of the drawings]
FIG. 1 is a diagram for describing an overview of a log mediation system according to the present invention.
FIG. 2 is a diagram showing a configuration of a log mediation system according to the first embodiment of the present invention.
FIG. 3 is a diagram showing a state in which logs are accumulated by access from a client in the log mediation system according to the first embodiment of the present invention.
FIG. 4 is a diagram showing a flow of BSS mediation in the log mediation system according to the first embodiment of the present invention.
FIG. 5 is a diagram showing an execution form of a log mediation system according to a second embodiment of the present invention.
FIG. 6 is a diagram showing an execution form of a log mediation system according to Embodiment 3 of the present invention.
FIG. 7 is a diagram showing an execution form of a log mediation system according to a fourth embodiment of the present invention.
FIG. 8 is a diagram showing an execution form of a log mediation system according to Embodiment 5 of the present invention.
[Explanation of symbols]
1, 1a, 1b, 1c, 1d, 1e Log mediation system, 2 servers, 3, 20, 21, 22, 23, 120, 121, 122, 123 logs, 4, 30, 31, 32, 33, 130, 131 , 132, 133 Log conversion unit (log conversion means), 5 unified data, 6 external data DB, 7, 50, 51, 52 support data generation unit (data generation means), 8 support data, 9 support system, 10A company Company I server, 11B company I server, 12C company J server, 13D company J server, 40 I service unified data, 41 J service unified data, 60, 61, 62, 63 external data DB, 70, 71, 72 support data, 80, 81, 82 support system, 90 client computer A, 91 client computer B, 92 mobile terminal 93 network, 94 server, 95 log, 96 wireless line, 110A company streaming server, 111B company streaming server, 112C company Web server, 113D company Web server, 140 stream unified data, 141 Web unified data , 150 charging data generation unit, 151 quality evaluation data generation unit, 152 usage trend analysis data generation unit, 160 charging rule DB, 161 system configuration information DB, 162 content information DB, 163 user information DB, 170 charging data, 171 quality evaluation Data, 172 usage trend analysis data, 180 billing system, 181 quality evaluation system, 182 usage trend analysis system.

Claims (9)

In a log mediation system that supplies support data to a support system that supports services,
A server that provides a service to a client via a network and outputs a log every time the client accesses the server;
Log conversion means for unifying logs output from the server in a prescribed format to form data,
A data generating unit that acquires the unified data and generates data in a format defined between the support system and the data based on the data,
A data transmission unit that transmits data generated by the data generation unit to the support system. 2. The log mediation system according to claim 1, comprising a plurality of types of data generation means, and supporting a plurality of types of support systems. 3. The log mediation system according to claim 1, wherein logs are unified for each type of service. 4. The log mediation system according to claim 3, wherein logs unified for each type of service are stored in a relational database. 4. The log mediation system according to claim 3, wherein logs unified for each type of service are stored as general-purpose data in XML format. The log mediating system according to any one of claims 1 to 5, wherein the log converting means converts the log into unified data when the log is obtained or periodically. The log mediation system according to any one of claims 1 to 6, wherein the data generation means obtains, from the outside, data that cannot be obtained from a log among data required by the support system. The data generating means generates support data from the unified data when a log is obtained, periodically, or when a request from the support system is transmitted, and transmits the generated support data to the support system. The log mediation system according to any one of claims 1 to 7. 9. The data processing apparatus according to claim 1, wherein, when a data request is made from a support system to a data generation unit by designating a condition, only data meeting the condition is supplied. Log mediation system described in section.

Images