JP2002041997A - Charged tag accounting system for language with tag - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a system capable of accounting automatically by a tag used for contents utilizing a language with tag represented by XML. SOLUTION: This charged tag accounting system is composed of a user data base transmitting information on the Internet and storing information on an information transmission server having use contract of a charged tag of XML and an accounting server receiving an address of an XML file and data of the charged tag included in the XML file from a browser unit downloading the XML file provided by the information transmission server. The accounting server totals charges of the charged tag applying accounting to the information transmission server based on the data of the charged tag by referring to user charge data base having data base storing the relation of the user data base, the number of users, and the charge and tag data base having data base storing the relation of the tag and tag use charge.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a billing system according to a tag such as content using a tagged language such as XML.

[0002]

BACKGROUND OF THE INVENTION With the development of information technology and network infrastructure, a great deal of information is provided and used on the Internet. One of the most important protocols used there is HTT
This is a text transfer using P.

In many cases, text data includes a markup language (ML). A markup language is a tagged language for describing a document structure. In these tagged languages, commands having a functional meaning are written in text data.

[0004] For example, a Web browser reads a command, that is, a tag written in an HTML file, and performs display as specified by the tag.

[0005]

However, the HTM
The data that can be handled by the L file is limited, and the processing method of the data that can be expressed by the HTML file is also limited to a predetermined type.

On the other hand, XML (eXtensible Markup Language) has recently been used as a markup language that has received special attention.
e) there. This provides an environment in which computer systems that are not compatible like HTML can read and write in common. In particular, XML has a feature that tags can be freely defined.

[0007] In this case, a person who intends to use XML can introduce a tag corresponding to a function necessary for performing a new expression into the XML. Then, the data is interpreted by a corresponding browser or the like, and the data is processed. This goes beyond the limits of HTML
Free expression can be done in text format.

On the other hand, there is no effective system at present in terms of protecting the XML invention. That is,
By introducing a large amount of development cost and introducing a new tag, there is a problem that even if an unprecedented expression is possible, another Web server can easily start a service using the tag. .

Accordingly, it is an object of the present invention to provide a system that can effectively charge for the use of the invention made with respect to tagged languages such as XML.

[0010]

According to the present invention, there is provided a user database which transmits information on the Internet and stores information of an information transmission server which has a contract for using a paid tag of XML; From the browser that downloaded the XML file provided by the outgoing server,
Information about the address of the XML file;
An accounting server for receiving the data of the toll tag included in the ML file, wherein the accounting server uses the user database, a user fee database having a database storing the relationship between the number of users and the fee, and uses the tag and the tag. A charging system is provided in which a charge database for a pay tag to be charged to the information transmission server is totaled based on the data of the pay tag by referring to a tag database having a database storing a charge relationship. I do.

[0011]

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS First, to help understand the basic concept of the present invention, one specific example to which the present invention can be applied will be described.

For example, suppose that the tag <ums> was invented. This is a tag meaning "user management server". Specifically, the tag specifies a method of providing a virtual reality space to a plurality of users using XML.

As an example of the past virtual reality space, there is known a virtual reality space in which the real world is virtually reproduced on a computer screen so that a user can enter the world on the screen. Such a conventional cyberspace has its own language and data structure, and is generally difficult to construct and requires time and cost.

Therefore, by introducing the tag <ums> and some tags attached thereto, the user can very easily construct the virtual reality space. The details thereof are described in Japanese Patent Application No. 2000-142195 filed by the present applicant, and thus will not be described here.

The present invention is directed to a system that can effectively charge for the use of the invention made with respect to such tagged languages such as XML. Hereinafter, one embodiment of the present invention will be described with reference to the drawings.

FIG. 1 shows a conceptual diagram of the present embodiment. According to the present embodiment, the client, the Web server, and the billing server are network-connected by the Internet, and the user database, the tag database, and the user fee database belong to the user management server or are connected so as to be able to refer to.

Here, the client is, in the most typical case, a general personal computer user or a personal computer that browses a Web server. For example, an unspecified majority using a personal computer may be used.
It may be limited to members registered in the server b.

First, a client downloads an XML file forming a content from a Web server. The XML file is processed by the corresponding Web browser, and a list of tags is extracted. That is, a pair of <*> and </ *> is searched using * as an arbitrary character string, and <*> is collected as a text file. Then, a text file including the list of the tags is transmitted to the charging server together with the address of the Web server, and the authentication of each tag is requested.

The billing server refers to the user database for authentication of the requested tag and determines whether or not the tag is approved. here,
The user database stores addresses of Web servers permitted to use tags.

The authentication result is returned to the client, and at the same time, the usage fee obtained from the tag database for the authenticated tag is totaled, and the totaling result is stored in the user database. According to this user database, a usage fee is charged to each Web server. That is, the bill is made not to the client but to the Web server.

The above processing is summarized as follows with reference to the flowchart of the charging system according to the present embodiment in FIG. That is, in step 1, the client requests the Web server for the XML file. In step 2, the client receives the XML file and extracts a tag set therefrom. In step 3, the client transmits a tag set together with the address of the Web server to the accounting server, and requests authentication of each tag.
It is confirmed whether the tag set sent to the accounting server in step 4 is available for each tag. In step 5, the charging server totals the usage charges by referring to the tag database for the usage charges of each used tag. In step 6, the charging server compares the number of restricted users with the number of persons currently in use from the user database for the number-limited tag, and determines that the tag can be used if it is within the upper limit. Otherwise, it is determined to be unavailable. In step 7, the accounting server sends the tag set authentication result to the client, and if available, performs processing according to the content of the tag on the client Web browser. The web browser here is HTM
This software analyzes and processes tagged languages such as L and XML.

This embodiment will be described in more detail. FIG. 3 is a flowchart diagram between each server and client in the charging system according to the present embodiment. First, the client requests an XML file from the Web server according to the present embodiment. Next, tagged language data (XML file)
And extract a list of tags. Here, the extracted tag list is referred to as a tag set. or,
Here, a Web server is used as an example of the embodiment.
Uniquely, the type of server does not matter.

Based on the acquired tag information, the client accesses the charging server, transmits the tag set to the charging server, and authenticates a usable tag. As the protocol there, a unique protocol on HTTP is used. In the authentication, whether the tag can be used and the maximum number of simultaneous users of the tag are determined.

This tag authentication information can be declared in advance by the content creator to the person who manages the billing server, and a usage fee calculated based on the number of used tags and the number of users can be paid. You can also.
A specific example will be described later.

Here, tag authentication information such as whether a tag can be used and the maximum number of simultaneous users of the tag are stored in a user database, and this database may be in a charging server, or may be a server other than this. May be present. When a user database is installed in a place other than the billing server, the billing server needs to have information on where the user database exists.

That is, the tag set sent to the charging server performs authentication for whether each tag can be used. Here, if the amount of tags increases and it takes time to perform the processing, only the paid tags are detected and the processing is performed. Similarly, the tag set sent to the charging server is compared with information stored in a user database in advance, and authentication is performed as to whether the tag is usable. There are various types of authentication, but details will be described in embodiments for each tag described later. For the tag determined to be usable, the accounting server notifies the client of the approval, and the client processes the tag content.

Here, one embodiment of the tag is shown. Suppose there is a tag called <ums> described above. This tag specifies network identification information of the user management server, for example, a URL. Specifically, it indicates the address of the server that provides the virtual reality space. In the case of this specific example, FIG.
A user management server is further added to the basic diagram of FIG. 7, and the diagram is as shown in FIG.

The location information of the user management server on the network is obtained from the network identification information specified by the tag, so that the client can use the service provided by the user management server, in this case, the shared use service of the space. .

Also, in this case, it is possible to define the number of persons who can simultaneously log in or access contents constructed using the tagged language, for example, cyberspace. The setting of the number of persons is specified in the permitted number of persons in the user database of FIG. The tag set is sent from the client to the billing server. At that time, the number of people currently using this tag is compared with the maximum number of simultaneous users stored in the user database. If so, the use of the tag is authenticated. If it is more than this, the use of the tag is denied.

If rejected, the tag cannot be used, and simultaneous use on the content, in this case, for example, services such as sharing of space called cyber space cannot be used. That is, the Web browser receives the non-permission response and displays that fact.

To add another explanation to the authentication of the <ums> tag, a Web server user registers information of a server to which content is uploaded in advance. Here, the person who provides the service using the Web server is referred to as the Web server.
It is called b server user. For example, as shown in FIG. 4 and FIG.
LX is registered, and data existing in a directory below the registered URLX directory is approved. Here, the URLX is a URL of a Web server corresponding to the XML.

Here, the maximum number of simultaneous users and the fee are defined by a user fee database that defines the fee based on the number of users shown in FIG. When a Web server user performs registration, it is necessary to apply for the number of people in advance. Referring to the user fee database of FIG. 6, the fee corresponding to the number of applicants is stored in the user database of FIG. (Or, a relation is established.) As an example of the totalization of charges, the calculation example in the case of http://aaa.co.jp/~hoge in FIG.
It is 0 yen, and the number of authorized people is 1000 for 10 people
Yen, and the total 2000 yen is the monthly fee. In addition, a calculation method can be appropriately considered.

Of course, not only a tag such as <ums> tag for specifying the number of users who can use the device but also an unlimited tag may be provided. May be set.

Also, the number of simultaneous users is automatically counted so that the user can use even if the number of users exceeds the declared number, the fee is calculated from this fee table, the fee information is stored in the user database, and the content creator is stored. It is also conceivable to make a request. This is included in FIG. 4 as an overcharge entry.

In another embodiment, a plurality of pay tags may be managed by one charging server. For example, there is an <adv> tag. This tag specifies whether or not an advertisement can be inserted. The tag displays an advertisement in a browser or content based on information on the content of the advertisement specified by the tag, for example, a URL that is network identification information where an advertisement image exists. .

It is to be noted that instead of directly specifying the URL, there is a method of indirectly specifying the URL or the like in the tag as follows.

<Adv><talk> Click here! ! </ talk><www> http://www.hogehogenet.ne.jp/adv.htm </ www></adv> The usage fee for each tag of these tag sets is a fee registered in the tag database. Referenced in the price database by tag. One example is shown in FIG. Here, the usage fees of the used tags are automatically added together and recorded in the user fee database. From here, it is possible to charge a usage fee to a Web server user using such a tag.

In this embodiment, a paid tag to be used is declared in advance, and an undeclared tag cannot be used. However, a system is also conceivable in which a pay tag to be used is registered without being specified, and the used pay tag is automatically detected and charged.

In the above embodiment, the billing server is "cha
rge control server "to introduce the tag <ccs>
Requests authentication by accessing the URL specified by <ccs> at that address.

In this case, in addition to the tag itself, the related URL is also transmitted to the tag set sent to the charging server. That is, like <ums> or <adv>, the tag <*>
If the data indicated by is a URL, the URL is transmitted together with the tag.

In one embodiment, for example, a cyberspace server that wishes to provide a service of <ums> needs to be registered in advance with a charging server having the tag <ums>. The accounting server records the usage status for each URL specified by <ums>, and charges the usage fee (including the XML file address) to the cyberspace server together with the usage status.

Here, the cyberspace server is:
Although there is no XML file directly including the tag <ums>, the usage fee is charged because <ums> is used indirectly. Of course, W using this cyberspace server
The e-server is also charged as described above. In this case, the information of the Web server that uses the cyberspace server is provided to the cyberspace server.
It is also possible to use the cyberspace server side to calculate the usage fee to the Web server.

The same applies to <adv>, but in this case, <adv>
Is provided to the tag user Web server together with the advertiser's address, so on the Web server side,
It can also be used to calculate fees to advertisers.

The above description has been made on the assumption that the browser currently used by the client corresponds to the tag in advance. However, even if the browser is not compatible,
By using a plug-in which is software for processing an unsupported tag, it becomes possible to support it.

To explain in more detail, tags that cannot be processed by the browser are sorted out by the charging server. Then, the client is instructed to download the plug-in, and is made to correspond to a tag that cannot be processed by the browser.

As an example, there is a tag list in the tag database shown in FIG. 7, in which function information of the browser for the tag, for example, version information is stored.
Assuming that the version of the browser is 1.0, for example, the tag <aaa> is not supported in version 1.0, so the client sends the computer identification information where the plug-in exists, the plug-in position information such as the URL, and the like. It is a mechanism to download plug-ins and handle tags that cannot be processed. FIG. 9 is a conceptual diagram and FIG. 10 is a flow chart.

Referring to FIG. 10, step 1 will be described.
First, the client requests an XML file from the Web server according to the present embodiment. At step 2, tag-attached language data (XML file) is obtained, and a list of tags is extracted. In step 3, the client sends the URLX, the tag set authentication request and the browser function information to the accounting server. In step 4, the charging server determines whether or not the tag can be used for each tag based on information in the user database. In step 5, the charging server refers to the function information of the browser and the usage fee for each tag used from the tag database and totals the usage fee. In step 6, the charging server compares the number of restricted users with the number of persons currently in use from the user database for the number-limited tag, and if the number is within the upper limit, authenticates the use of the tag. In step 7, the browser function information of the client is compared with the information of the database from the tag database. In step 8, from the tag set authentication result and the comparison result in step 7, the plug-in position information stored in the tag database is sent from the tag database to the client from the charging server if necessary. In step 9, the client downloads the plug-in based on the position information of the plug-in, and performs processing according to the contents of the tag.

[0048]

As described above, according to the present invention,
It is possible to construct a system that can automatically charge for the content using a tagged language represented by XML based on the tag used. In particular, since the XML file can be easily modified, the cost can be adjusted very easily by adding or deleting a paid tag. Further updated XM
The browser can flexibly correspond to the tag of the L file.

[Brief description of the drawings]

FIG. 1 is a conceptual diagram showing a pay tag billing system according to an embodiment of the present invention.

FIG. 2 is a flowchart chart of the pay tag billing system according to the embodiment of the present invention.

FIG. 3 is an explanatory diagram showing communication in the pay tag billing system according to the embodiment of the present invention.

FIG. 4 is a diagram showing a specific example of a database of a user database in the pay tag billing system according to the embodiment of the present invention.

FIG. 5 is a diagram showing a specific example of URLX authentication in the pay tag charging system according to the embodiment of the present invention.

FIG. 6 is a diagram showing a specific example of a database of a user fee database in the paid tag billing system according to the embodiment of the present invention.

FIG. 7 is a diagram showing a specific example of a database of a tag database in a pay tag billing system according to an embodiment of the present invention.

FIG. 8 is a conceptual diagram showing a pay tag billing system according to an embodiment of the present invention, in which a user management server is further added to the one shown in FIG.

FIG. 9 is a diagram illustrating an example in which a tag that cannot be processed by a browser version currently used by a client is handled by downloading a plug-in by the paid tag charging system according to the embodiment of this invention.

FIG. 10 is a flowchart illustrating an example in which a tag that cannot be processed by a browser version currently used by a client is handled by downloading a plug-in by the paid tag charging system according to the embodiment of this invention.

Claims (2)

[Claims] 1. A user database that transmits information on the Internet and stores information on an information transmission server that has a contract for using a paid tag in a tagged language, and the information transmission server provides the user database. From the browser that downloaded the tagged language file, information on the address of the tagged language file, and a billing server that receives the data of the paid tag included in the tagged language file, the billing server comprises: With reference to the user database and the user fee database having a database storing the relationship between the number of users and the fee and the tag database having a database storing the relationship between the tag and the usage fee of the tag, based on the data of the paid tag, A feature is to aggregate the charges of the pay tags to be charged to the information transmission server. Billing system. 2. The charging server, when the tag-added language file includes a tag that cannot be processed by the browser, transmits the position information of a plug-in for processing the tag to the browser. The billing system according to claim 1, wherein: