JP4516191B2 - Pay tag billing system for tagged languages - Google Patents

Description

[0001]
BACKGROUND OF THE INVENTION
The present invention relates to a billing system according to tags such as contents using a tagged language such as XML.
[0002]
[Prior art]
With the development of information technology and network infrastructure, a great deal of information is being provided and used on the Internet. Therefore, one of the most important protocols used is text transfer using HTTP.
[0003]
In many cases, the text data includes a markup language (ML). The markup language is a tagged language for describing the document structure. In these tagged languages, commands having functional meaning are entered in text data.
[0004]
For example, a Web browser reads a command, that is, a tag entered in an HTML file, and displays it as specified by the tag.
[0005]
[Problems to be solved by the invention]
However, the data that can be handled by the HTML 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.
[0006]
On the other hand, there is XML (eXtensible Markup Language) as a markup language which has recently been particularly emphasized. This provides an environment in which incompatible computer systems can read and write in common as in HTML. 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 XML. Then, the data can be processed by being interpreted by a corresponding browser or the like, thereby enabling effective expression. Thereby, it is possible to perform free expression in a text format exceeding the limit of HTML.
[0008]
On the other hand, there is no effective system at present in terms of protecting the invention of XML. In other words, by introducing a large amount of development costs and introducing a new tag, even if an expression that has never been possible is possible, another Web server can easily start a service using that tag. There is.
[0009]
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 tagged languages such as XML.
[0010]
[Means for Solving the Problems]
The present invention provides a user database storing information of an information transmission server that transmits information on the Internet and contracts to use an XML pay tag, and an XML file provided by the information transmission server From the browser that downloaded the URL, and a billing server that receives the paid tag data included in the XML file. The billing server includes the user database, the number of users, and the charge Refer to the user fee database having the database storing the relationship and the tag database having the database storing the relationship between the tag and the tag usage fee, and charge the information transmission server based on the paid tag data Providing a billing system characterized by counting charges for paid tags That.
[0011]
DETAILED DESCRIPTION OF THE INVENTION
First, in order to help understand the basic concept of the present invention, one specific example that can be applied will be described.
[0012]
For example, assume that the tag <ums> was invented. This is a tag meaning "user management server". Specifically, the tag specifies a method for providing a virtual reality space to a plurality of users using XML.
[0013]
As an example of the past virtual reality space, there is known one in which the real world is virtually reproduced on a computer screen and the user can enter the world on the screen. Such conventional cyberspace has a unique language and data structure, and is generally difficult to construct and takes time and cost.
[0014]
Therefore, by introducing the tag <ums> and several tags accompanying it, the user can construct the virtual reality space very easily. Details thereof are described in Japanese Patent Application No. 2000-142195 filed by the present applicant, and are omitted here.
[0015]
The present invention relates to a system that can effectively charge for the use of the invention made with such tagged languages such as XML. Hereinafter, an embodiment of the present invention will be described with reference to the drawings.
[0016]
FIG. 1 shows a conceptual diagram of this embodiment. According to this embodiment, the client, the Web server, and the accounting server are connected to each other via the Internet network, and the user database, the tag database, and the user fee database belong to the user management server or are connected so that they can be referred to.
[0017]
Here, in the most typical case, the client is a general personal computer user or a personal computer that browses a Web server. For example, it may be an unspecified number using a personal computer, or may be limited to members registered in advance in a specific Web server.
[0018]
First, the client downloads an XML file that forms content from a Web server. The XML file is processed by a corresponding Web browser, and a list of tags is extracted. That is, using * as an arbitrary character string, a pair of <*> and </ *> is searched, and <*> is collected into a text file. Then, a text file including the list of tags is transmitted to the accounting server together with the address of the Web server, and a request is made for authentication of each tag.
[0019]
The billing server refers to the user database for the authentication of the requested tag, and decides whether to accept or reject it. Here, the user database stores the addresses of Web servers that are permitted to use tags.
[0020]
The authentication result is returned to the client, and the usage fee obtained from the tag database is totaled for the authenticated tag at the same time, and the total result is stored in the user database. In accordance with this user database, a usage fee is charged to each Web server. In other words, billing is made to the Web server, not the client.
[0021]
The above process is summarized as follows with reference to the flowchart of the accounting system according to the present embodiment in FIG. That is, in step 1, an XML file is requested from the client to the Web server. In step 2, the client receives the XML file and extracts a tag set therefrom. In step 3, the tag set is transmitted together with the address of the Web server from the client to the accounting server, and authentication of each tag is requested. It is confirmed whether the tag set sent to the billing server in step 4 can be used for each tag. In step 5, the billing server sums up the usage charges by referring to the tag database for the usage charges for each tag used. In step 6, the billing server compares the number of restricted users with the number of people currently in use from the user database, and determines that the tag can be used if it is within the upper limit. Otherwise, it is determined that it cannot be used. In step 7, the authentication result of the tag set is sent from the billing server to the client, and if it can be used, the processing is carried out according to the contents of the tag in the client web browser. Web browser here refers to software that analyzes and processes tagged languages such as HTML and XML.
[0022]
This embodiment will now be described in some detail. A flowchart between each server and client in the accounting system according to this embodiment is shown in FIG. The client first requests an XML file from the Web server according to the present embodiment. Next, the tagged language data (XML file) is acquired, and a list of tags is extracted. Here, the extracted tag list is referred to as a tag set. In addition, although a Web server is used here as an example of implementation, the type of server is not particularly limited.
[0023]
Based on the acquired tag information, the client accesses the billing server and sends a tag set to the billing server to authenticate the usable tag. As a protocol there, a unique protocol on HTTP is used. At the time of authentication, whether or not the tag can be used and the maximum number of simultaneous use of the tag are authenticated.
[0024]
The tag authentication information can be declared in advance from the content creator to the person who manages the billing server, or the usage fee calculated based on the number of tags used and the number of users can be paid. . Specific examples will be described later.
[0025]
Here, tag authentication information such as whether a tag can be used and the maximum number of simultaneous users of the tag is stored in a user database, which may be in a billing server or in a server other than this. May be. When the user database is set up other than the billing server, the billing server needs to have information on where the user database exists.
[0026]
That is, the tag set sent to the billing server is authenticated for each tag. Here, if the amount of tags increases and processing may take time, only paid tags are detected and processing is performed. Similarly, the tag set sent to the billing server is compared with information stored in advance in the user database to authenticate whether the tag can be used. Although there are various types of authentication, details will be described in an embodiment for each tag described later. The tag determined to be usable is notified of the approval from the accounting server to the client, and the tag contents are processed by the client.
[0027]
Here, one embodiment of the tag is shown. Suppose there is a tag <ums> mentioned above. This tag is a tag that defines network identification information of the user management server, such as a URL. Specifically, the address of the server that provides the virtual reality space is shown. In this specific example, a user management server is further added to the basic diagram of FIG. 1, resulting in a diagram as shown in FIG.
[0028]
The location information on the network of the user management server is obtained from the network identification information defined by this tag, and the client can use the service provided by the user management server, in this case, the shared use service of the space.
[0029]
Also, in this case, it is possible to define the number of people who can log in or access content built using a tagged language, for example, cyberspace at the same time. This setting of the number of people is defined in the number of permitted users 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 there is, the use of the tag is authenticated, and if it exceeds this, the use of the tag is denied.
[0030]
If denied, this tag cannot be used, and services such as simultaneous use on content, such as sharing a space called cyber space, cannot be used. That is, the Web browser receives an unacceptable response and displays it.
[0031]
In the <ums> tag authentication, another explanation will be added. The Web server user registers information of a server to which content is uploaded in advance. Here, a person who provides a service using a Web server is called a Web server user. For example, as shown in FIGS. 4 and 5, URLX for authentication is registered in the user database, and data existing in a directory below the registered URLX directory is approved. It is a mechanism. Here, URLX is a URL of a Web server corresponding to the XML.
[0032]
Further, here, the maximum number of simultaneous users and the fee are defined by the user fee database that defines the fee according to the number of users shown in FIG. When a Web server user registers, it is necessary to apply for the number of people in advance. With reference to the user fee database in FIG. 6, the fee corresponding to the number of applicants is stored in the user database in FIG. (Or a relation is created.)
As an example of totaling charges, the calculation example in the case of http://aaa.co.jp/~hoge in Fig. 4 is 1000 yen as a basic charge with a permission tag of <ums>, and the number of people allowed is ~ It is 1000 yen for 10 people, and the total of 2000 yen is the monthly fee. In addition, the calculation method can be considered as appropriate.
[0033]
Of course, there are not only tags that specify the number of people that can be used, such as <ums> tags, but there may also be unlimited tags, and even tags that specify the number of people that can be used are set separately for charges for unlimited use. Also good.
[0034]
In addition, the number of simultaneous users is automatically counted so that the user can use it even if the number of people exceeds the reported number, the fee is calculated from this fee table, the fee information is stored in the user database, and the content creator is charged. It is also possible to use this method. In FIG. 4, this is included as an entry for excess charges.
[0035]
In another embodiment, a plurality of pay tags may be managed by one billing server. For example, there is an <adv> tag. This tag defines whether or not the advertisement can be placed. The advertisement is displayed in the browser or content based on the information of the advertisement content defined by this tag, for example, the URL that is the network identification information in which the advertisement image exists. .
[0036]
In addition, instead of specifying the URL directly, there is a method of specifying the URL or the like indirectly in the tag as follows.
[0037]
<adv>
<talk> Click here! ! </ talk>
<www> http://www.hogehogenet.ne.jp/adv.htm </ www>
</ adv>
The usage fee for each tag in the tag set is referred to in the fee database for paid tags registered in the tag database. An example is shown in FIG. Here, the usage fees for the tags used 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.
[0038]
In this embodiment, paid tags to be used in advance are declared, and tags that have not been declared cannot be used. However, a system is also conceivable in which a pay tag to be used is registered without being specified, and the pay tag used is automatically detected and charged.
[0039]
In the above embodiment, the accounting server introduces a tag <ccs> in the meaning of “charge control server”, and accesses the URL specified by <ccs> to the address to request authentication.
[0040]
In this case, in addition to the tag itself, a related URL is also transmitted to the tag set sent to the billing server. That is, when the data indicated by the tag <*> is a URL, such as <ums> or <adv>, the URL is also transmitted together with the tag.
[0041]
In one embodiment, for example, a cyberspace server that wants to provide a service of <ums> needs to be registered in advance with a charging server that owns the tag <ums>. The accounting server records the usage status for each URL specified by <ums>, and charges the cyberspace server together with the usage status (including the address of the XML file).
[0042]
Here, the cyberspace server does not have an XML file including the tag <ums> directly, but uses <ums> indirectly and is charged a usage fee. Of course, the Web server using this cyber space server is charged as described above. In this case, since the information of the Web server that uses the cyberspace server is provided to the cyberspace server, the cyberspace server can also be used for calculating the usage fee for the Web server.
[0043]
The same applies to <adv>, but in this case, the usage status of <adv> is provided to the tag user's web server along with the advertiser's address, so the web server side can calculate the fee to the advertiser. It can also be used.
[0044]
In the above description, it is assumed that the browser currently used by the client corresponds to the tag in advance. However, even if the browser is not compatible, it can be supported by using a plug-in that is software for processing a tag that is not supported.
[0045]
Explaining in more detail now, tags that cannot be processed by the browser are selected by the billing server. Then, the client is instructed to download the plug-in to correspond to a tag that cannot be processed by the browser.
[0046]
As an example, there is a tag list in the tag database shown in FIG. 7, in which browser function information for the tag, for example, version information is stored. If the browser version is 1.0, for example, the tag <aaa> is not supported in version 1.0. Therefore, the computer identification information in which the plug-in exists in the client, the plug-in location information such as URL, It is a mechanism that handles plug-in downloads and tags that cannot be processed. The conceptual diagram is shown in FIG. 9, and the flowchart is shown in FIG.
[0047]
Referring to FIG. 10, in step 1, the client first requests an XML file from the Web server according to the present embodiment. In step 2, tagged language data (XML file) is acquired, and a list of tags is extracted. In step 3, URLX, tag set authentication request, and browser function information are sent from the client to the accounting server. In step 4, the charging server identifies whether or not the tag can be used based on the information in the user database for each tag. In step 5, the billing server refers to the browser function information and the usage fee for each tag used from the tag database, and totals the usage fees. In step 6, the billing server compares the number of restricted users with the number of people currently in use from the user database, and authenticates the use of the tag if it is within the upper limit. In step 7, the client browser function information is compared with the database information from the tag database. In step 8, the plug-in location information stored in the tag database is transmitted from the tag database if necessary from the authentication result of the tag set and the comparison result in step 7 from the accounting server to the client. In step 9, the client downloads the plug-in based on the plug-in position information, and performs processing according to the contents of the tag.
[0048]
【The invention's effect】
As described above, according to the present invention, it is possible to construct a system capable of automatically charging with a tag used for content using a tagged language represented by XML. In particular, since an XML file can be easily modified, it is possible to adjust costs very easily by adding or deleting a pay tag. Furthermore, the browser can flexibly cope with the tag of the updated XML file.
[Brief description of the drawings]
FIG. 1 is a conceptual diagram showing a pay tag accounting 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 accounting system according to the embodiment of the present invention.
FIG. 4 is a diagram illustrating a specific example of a database included in a user database in the pay tag accounting system according to the embodiment of this invention.
FIG. 5 is a diagram showing a specific example of URLX authentication in the pay tag accounting system according to the embodiment of the present invention.
FIG. 6 is a diagram showing a specific example of a database included in a user fee database in the pay tag accounting system according to the embodiment of the present invention.
FIG. 7 is a diagram illustrating a specific example of a database included in a tag database in the paid tag billing system according to the embodiment of this invention.
FIG. 8 is a conceptual diagram showing a pay tag accounting system according to an embodiment of the present invention, in which a user management server is further added to that of FIG.
FIG. 9 is a diagram showing an example in which a tag that cannot be processed by a client version currently used by a client is associated by downloading a plug-in by the paid tag accounting 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 client version currently used by a client is associated by downloading a plug-in by the paid tag accounting system according to the embodiment of this invention.

Claims (2)

Stores the identification information of the information transmission server that transmits information over the Internet, the information associated with the address on the information transmission server tagged language files constituting the cyberspace by the information transmitting server is provided Cyberspace user database and
An address on the information transmission server that is a download source of the tagged language file that constitutes the cyberspace from the browser that displays the cyberspace that downloaded the tagged language file that constitutes the cyberspace provided by the information transmission server And a cyberspace billing server that receives data on the paid tag included in the tagged language file that constitutes the cyberspace and counts the number of clients that have transmitted the tag ,
The cyberspace billing server has the cyberspace user database, and refers to the cyberspace user database based on the received address, and identifies the information transmission server that is the source of the tagged language file Get
By referring to the tag database with the database that stores the relationship between the usage fee of the user account database and the tag and the tag according to the cyber space utilization with a database that stores the relationship between the number of users and the fee you are logged in to the cyber space, the A cyberspace billing system characterized in that, based on the counted number and the data of the pay tag, the charge of the pay tag to be charged to the information transmitting server identified by the acquired identification information is totaled.   The billing server transmits the location information of the cyber space plug-in for processing the tag to the browser when the tag-capable language file constituting the cyber space includes a tag that cannot be processed by the browser. The cyberspace billing system according to claim 1, wherein:

Images