JP2004023459A - Charging method, repeating device, program and recording medium - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To charge a supplier of data. <P>SOLUTION: A gateway server 300 repeats communication made between a portable telephone set 600 and a content server 100 by using HTTP. The gateway server 300 decides an object of charging preformed on an HTTP request and an HTTP response being a pair with the HTTP request based on a charging destination designation header included in the HTTP request transmitted from the content server 100 in accordance with the HTTP request transmitted from a portable telephone set 100. <P>COPYRIGHT: (C)2004,JPO

Description

[0001]
TECHNICAL FIELD OF THE INVENTION
The present invention relates to a technology for charging a communication fee to a user of a communication network.
[0002]
[Prior art]
In a mobile communication terminal such as a mobile phone, a user of the mobile communication terminal uses a WWW (World Wide Web) browser to open a Web page that is a page described in a markup language such as CHTML (Compact Hyper Text Markup Language). 2. Description of the Related Art Accessing a providing server via a mobile communication network and browsing a Web page is performed.
Some of the data communication between the mobile phone and the server uses packet communication. In packet communication performed in a mobile communication network, a billing method in which billing is performed in accordance with the amount of communication is preferably used, and a user of a mobile phone is provided to a mobile phone user based on the amount of packets transmitted and received by the mobile phone. Billing has been done.
[0003]
[Problems to be solved by the invention]
Among providers who provide Web pages, there are those who want many people to browse the Web pages for the purpose of advertisement or advertisement.
However, the user of the mobile phone, in the related art, is charged based on the amount of packets generated by the packet communication. Therefore, the user of the mobile phone may be afraid of viewing a large number of web pages and increasing the communication fee. Hesitate to access a Web page other than the page. For this reason, among Web pages that perform advertisements and advertisements, there are Web pages that do not have a large number of viewers as much as a provider of the Web page thinks.
[0004]
Among those who provide Web pages that carry these advertisements and advertisements, there are those who think that the number of times that Web pages will be viewed will increase if users of mobile phones can view the Web pages for free. Some consider that the user may pay money for a Web page that carries an advertisement or promotion so that the user can browse the Web page free of charge, or that the user can browse the Web page free of charge for a certain period of time. There are those who are willing to pay money.
In order to increase the number of viewers of the Web page, the provider of the Web page pays money among providers who provide such Web pages, and the mobile phone is provided according to the provided Web page, date, and the like. There has been a demand for a billing method that allows a user to browse a Web page for free.
[0005]
The present invention has been made in view of the above-described circumstances, and when communication with accounting is performed in a communication network, not only a person who acquires information but also a provider who provides information is charged. It is an object of the present invention to provide a charging method, a relay device, a program, and a recording medium capable of performing the following.
[0006]
[Means for Solving the Problems]
In order to solve the above problems, the present invention provides a portable communication terminal capable of using a communication network, which determines a billing destination of billing to be performed for relayed communication with a data acquisition request to request data acquisition. An acquisition request transmitting step of transmitting the data acquisition request to the relay device via the communication network, the relay device receiving the data acquisition request, and transmitting the received data acquisition request to a server device including a storage unit for storing data An acquisition request relaying step, wherein the server device receives the data acquisition request, and in response to the received data acquisition request, sets the billing destination to a user of the mobile communication terminal or a data provider that provides the data. A data response transmission step of transmitting a data acquisition response including the charging target person information for specifying any one of the information and data requested by the mobile communication terminal to the relay device; An acquisition response receiving step in which the relay device receives the data acquisition response transmitted in the data response transmission step; and the accounting included in the data acquisition response received by the relay device in the acquisition response receiving step. A billing person determination step of determining a billing destination of billing performed for the data acquisition request relayed by the relay device and the data acquisition response paired with the data acquisition request, based on the subject person information; A relay device that transmits the data acquisition response received in the acquisition response receiving step to the mobile communication terminal.
[0007]
Further, the present invention provides a server device provided with a storage unit for storing data, wherein a charging destination for charging performed for communication relayed by the relay device is determined by a user of a portable communication terminal capable of using the communication network or the data. A distribution data transmission step of transmitting distribution data including the billing person information and the data for specifying to any of the data providers that provide the transmission data to the relay device; and A distribution data receiving step of receiving the transmitted distribution data; and the relay device relays the relay device based on the charging target person information included in the distribution data received in the distribution data receiving step. A billing person determination step of determining a billing destination for billing performed on the distribution data; and the relay device receives the distribution data in the distribution data receiving step. To provide a charging method and a distribution data relaying sending transmit data communications network to the available mobile communication terminal.
[0008]
The present invention further includes a storage unit that receives a data acquisition request for requesting data acquisition from a portable communication terminal that can use the communication network via the communication network, and stores the received data acquisition request in data. Acquisition request relaying means for transmitting to the server device provided with, charging target person information for specifying either a user of the mobile communication terminal or a data provider providing the data, and the mobile communication terminal An acquisition response receiving unit that receives a data acquisition response including the requested data from the server device, and based on the billing person information included in the data acquisition response received by the acquisition response receiving unit, A billing person determining means for deciding a billing destination for billing performed in response to the data acquisition request relayed by the device and the data acquisition response corresponding to the data acquisition request; Data acquisition response received by the answer receiving means to provide a relay device and a data acquisition response relay section that transmits to said mobile communication terminal.
[0009]
The present invention also provides a computer device, which receives a data acquisition request to request data acquisition from a portable communication terminal capable of using a communication network via the communication network, and stores the received data acquisition request in data. Acquisition request relay means for transmitting to a server device having a storage unit, billing target information for specifying a billing destination to either a user of the portable communication terminal or a data provider for providing the data, An acquisition response receiving unit that receives a data acquisition response including the data requested by the mobile communication terminal from the server device, based on the chargeable person information included in the data acquisition response received by the acquisition response receiving unit; And determining a billing destination of billing performed for the data acquisition request relayed by the computer device and the data acquisition response paired with the data acquisition request. Provided is a payment target determining unit, a program for functioning as a data acquisition response relay unit for transmitting the data acquisition response received by the acquisition response receiving unit to the portable communication terminal, and a recording medium on which the program is recorded. .
[0010]
BEST MODE FOR CARRYING OUT THE INVENTION
Hereinafter, embodiments of the present invention will be described with reference to the drawings. However, the present invention is not limited to such an embodiment, but includes any aspect within the scope described in the claims.
[0011]
[1. Configuration of Embodiment]
FIG. 1 is a diagram illustrating an overall configuration of a communication system 10 according to the present invention.
Although a large number of mobile phones and content servers exist in the communication system 10, FIG. 1 shows only predetermined mobile phones 600 and content servers 100 in order to prevent the drawing from becoming complicated. .
[0012]
The content server 100 whose domain name as an identifier for identifying the server is “www.abc.co.jp” is operated by a communication provider that provides a Web page (hereinafter, referred to as a Web page provider). Server. The telecommunications carrier that operates the content server 100 provides a web page to mobile phones housed in the mobile communication network 200 free of charge. The content server 100 has a function of performing packet communication with a mobile phone owned by a subscriber of the mobile communication network 200 using the mobile communication network 200, and is installed in the mobile communication network 200. Connected to the gateway server 300 via a dedicated line. The packet transmitted from the content server 100 includes information for identifying the content server 100 that is the transmission source of the packet and information for identifying the mobile phone that is the destination of the packet.
[0013]
The mobile communication network 200 is a communication network that provides mobile data communication services such as general mobile telephone call service and packet communication to mobile phones accommodated in the mobile communication network 200. The mobile communication network 200 includes a wireless base station (not shown) for performing wireless communication with a mobile phone accommodated in the mobile communication network 200, an exchange (not shown) connected to the wireless base station, and a connection to the exchange. A gateway server 300, a subscriber database 400, and a billing system 500.
The mobile communication network 200 relays packet communication performed between the mobile phone and the content server 100 by using a wireless base station, an exchange, and a gateway server 300 installed in the network.
[0014]
The gateway server 300 is a server provided in the mobile communication network 200, and is a server that interconnects the content server 100 and the mobile communication network 200. The gateway server 300 performs mutual conversion between a communication protocol used for packet communication in the mobile communication network 200 and TCP / IP (Transmission Control Protocol / Internet Protocol) which is a communication protocol used in the content server 100. It relays communication performed between the mobile communication network 200 and the content server 100.
Further, the gateway server 300 has a proxy function, and relays communication performed by a mobile phone accommodated in the mobile communication network 200 for browsing a Web page.
Further, the gateway server 300 has a function of counting the amount of packets relayed in packet communication performed between the mobile phone accommodated in the mobile communication network 200 and the content server 100. Is transmitted to the billing system connected to the gateway server 300.
[0015]
The subscriber database 400 includes a file storing data relating to subscribers of the mobile communication network 200 (hereinafter referred to as a subscriber file) and a file storing data relating to a Web page provider (hereinafter referred to as a carrier file). Is a database for storing the information.
FIG. 2 is a diagram illustrating a format of data stored in a subscriber file and a carrier file. The subscriber file F1 includes data for identifying the subscriber for each subscriber, data for identifying the mobile phone owned by the subscriber, data indicating the gender of the subscriber, and subscription. Data indicating the contractor's address is stored. The telecommunications carrier file F2 includes a business operator identifier for identifying a Web page provider for each Web page provider and an identifier for identifying a content server operated by the Web page provider (hereinafter, referred to as a server identifier). ), Data indicating a domain name as an identifier for identifying a server, and data indicating an address of a Web page provider.
[0016]
The billing system 500 is a system for billing each user of the communication service provided by the mobile communication network 200 for the use of the communication service and calculating a communication fee charged to the user.
Charging system 500 calculates the amount of communication fee to be charged for each user based on data indicating the amount of packets transmitted from gateway server 300 and information for identifying a person to be charged for packet communication. And create an invoice.
[0017]
The mobile phone 600 is a mobile communication terminal that performs wireless communication with a wireless base station installed in the mobile communication network 200 and can receive a call service and a packet communication service provided by the mobile communication network 200.
The mobile phone 600 has a function of performing packet communication with the content server 100 via the mobile communication network 200 and the gateway server 300. The packet transmitted from the mobile phone 600 includes “0 * 0-1111-2222”, which is information for identifying the mobile phone that is the source of the packet (hereinafter, referred to as a mobile phone identifier), and the destination of the packet. And information for identification.
[0018]
[1-1. Configuration of Mobile Phone]
The mobile phone 600 includes an operation unit including a CPU (Central Processing Unit), a ROM (Read Only Memory), a RAM (Random Access Memory), a numeric keypad for operating the mobile phone 600, and the like. It has a liquid crystal display for displaying a menu screen and the like for operation, a communication unit (all not shown) for performing wireless communication, an antenna, and the like. In the mobile phone 600, when the operation unit is operated by the user, the content of the user's instruction is grasped based on the screen displayed on the liquid crystal display and the operation performed on the operation unit, and a process corresponding to the operation content is performed. Is performed.
[0019]
The ROM of the mobile phone 600 stores a telephone number of the mobile phone 600, a control program for controlling the mobile phone 600, a WWW browser program for browsing a Web page, and the like. When the power of the mobile phone 600 is turned on by the user, the CPU of the mobile phone 600 reads out and executes the control program from the ROM. After executing the control program, the CPU of the mobile phone 600 reads out and executes the WWW browser program from the ROM when the user operates the operation unit to start the WWW browser.
[0020]
The WWW browser executed on the mobile phone 600 has a function of performing communication using HTTP (HyperText Transfer Protocol). When an operation of inputting a URL (Uniform Resource Locator) for browsing a Web page by a user and an operation of displaying a Web page specified by the URL are performed on the mobile phone 600, In order to display the Web page specified by the URL, transmission of a request (hereinafter referred to as an HTTP request) using an HTTP GET method including the URL as a parameter, and transmission of an HTTP request transmitted as a response to the HTTP request A response (hereinafter, referred to as an HTTP response) is received by packet communication.
[0021]
[1-2. Content Server Configuration]
FIG. 3 is a diagram illustrating a hardware configuration of the content server 100. As shown in FIG. 3, each unit of the content server 100 is connected by a bus 110.
[0022]
The communication unit 101 is connected to a dedicated line for connecting the gateway server 300 and the content server 100, and controls communication performed between the content server 100 and another device. The operation unit 102 has a mouse and a keyboard, not shown. When the user of the content server operates the mouse or keyboard of the operation unit 102, a signal indicating the operation content is output to the CPU 107. The display unit 103 has a liquid crystal display (not shown) and a control circuit for controlling the liquid crystal display. Upon receiving the control signal transmitted from CPU 107, display section 103 displays a menu screen or the like for operating content server 100 on the liquid crystal display based on the control signal.
[0023]
The storage unit 104 has a non-volatile memory such as a hard disk, for example, and stores data “abc.html” (hereinafter referred to as Web page data) for displaying a Web page described using CHTML and a server. The server identifier “12345678” for identification is stored.
[0024]
The ROM 105 stores an initialization program for initializing each part of the CPU 107 and the content server 100, a server program for transmitting and receiving data to and from a mobile phone housed in the mobile communication network 200 using HTTP, and the like. ing. The RAM 106 is used as a work area of the CPU 107, and temporarily stores data used by a program executed by the CPU 107.
[0025]
When the power of the content server 100 is turned on, the CPU 107 reads out the initialization program from the ROM 105 and executes it. When executing the initialization program, the CPU 107 performs initialization of the CPU 107 itself and initialization processing of each unit of the content server 100. After the initialization process is completed, the CPU 107 reads out a server program for transmitting and receiving data using the HTTP from the ROM 105 and executes the server program.
[0026]
When the communication unit 101 receives an HTTP request transmitted from a mobile phone accommodated in the mobile communication network 200, the received HTTP request is sent to the CPU 107. Upon receiving the HTTP request, the CPU 107 executing the server program reads, from the storage unit 104, Web page data specified by a URL included as a parameter in the HTTP request in response to the received HTTP request. Since the domain name of the content server is “www.abc.co.jp”, the CPU 107 determines that the URL is “http://www.abc.co.jp” which is a URL for acquiring “abc.html”. In the case of “/abc.html”, “abc.html” is read from the storage unit 104. After reading the Web page data, the CPU 107 transmits an HTTP response including the Web page data to the mobile phone that has transmitted the HTTP request by packet communication.
[0027]
The server program executed by the CPU 107 is a packet communication performed for transmitting an HTTP request generated by a mobile phone accommodated in the mobile communication network 200 and an HTTP response generated by the content server 100. Has a function of designating whether to charge the user to the user of the mobile phone that transmitted the HTTP request or to the Web page provider.
[0028]
The HTTP response generated by the CPU 107 includes, in addition to the Web page data, header data including information indicating the version of the HTTP used by the server program and information indicating the date. When transmitting the HTTP response, the CPU 107 adds a billing destination designation header “X-DCM:” to the header data as information for designating a billing target person.
“A / BBBBBBBBB” is added as a parameter to the billing destination designation header. In the “A” part of the parameter, a numerical value for designating whether the user to be charged is a user of a mobile phone accommodated in the mobile communication network 200 or a Web page provider is set. In the parameter “BBBBBBBBB”, an identifier for identifying a content server that generates an HTTP response when a chargeable person is a Web page provider is set.
[0029]
CPU 107 sets the parameter “A” to “1” and sets the billing destination designation header to “1” when designating the person to be charged for packet communication performed to acquire Web page data as the user of mobile phone 600. X-DCM: 1/999999999 ". The CPU 107 sets the parameter “A” to “2” in the case where the billing target of the packet communication performed to acquire the Web page data is designated as the Web page provider, and the CPU 107 stores the parameter “A” in the storage unit 104. The server identifier “12345678” is set in the parameter “BBBBBBBBBB”, and the billing destination designation header is set to “X-DCM: 2/12345678”.
[0030]
[1-3. Configuration of Gateway Server]
FIG. 4 is a diagram illustrating a hardware configuration of the gateway server 300. As shown in FIG. 4, each unit of the gateway server 300 is connected by a bus 310.
[0031]
The first communication unit 301 has a communication interface function for communicating with equipment such as an exchange and a charging system 500 in the mobile communication network 200. The first communication unit 301 exchanges data with a mobile phone housed in the mobile communication network 200 using a communication protocol used for packet communication in the mobile communication network 200 under the control of the CPU 308. Do. The second communication unit 302 has a communication interface function for communicating with the content server 100, and exchanges data with the content server 100 using TCP / IP under the control of the CPU 308.
[0032]
The operation unit 303 has a mouse and a keyboard not shown. When the user of the gateway server operates the mouse or keyboard of the operation unit 303, a signal indicating the operation content is output to the CPU 308. The display unit 304 has a liquid crystal display (not shown) and a control circuit for controlling the liquid crystal display. Upon receiving the control signal transmitted from CPU 308, display unit 304 displays a menu screen or the like for operating gateway server 300 on the liquid crystal display based on the control signal.
[0033]
The storage unit 305 has a non-volatile memory such as a hard disk, for example, and stores data related to packet communication performed by a user of the mobile communication network 200 in the format F3 illustrated in FIG. As shown in FIG. 5, the storage unit 305 stores a mobile phone accommodated in the mobile communication network 200 in association with a connection ID for identifying a TCP connection between the gateway server 300 and the content server 100. An identifier for identification, data indicating the amount of packets generated by the HTTP request, data indicating the amount of packets generated by the HTTP response, and a person to be charged for the packet communication generated by the connection Is stored.
[0034]
The ROM 306 stores an initialization program for initializing each unit of the CPU 308 and the gateway server 300, a control program for controlling each unit of the gateway server 300, and the like. The RAM 307 is used as a work area of the CPU 308, and temporarily stores data used by a program executed by the CPU 308.
[0035]
When the power of the gateway server 300 is turned on, the CPU 308 reads the initialization program from the ROM 306 and executes it. When executing the initialization program, the CPU 308 performs initialization of the CPU 308 itself and initialization processing of each unit of the gateway server 300. After the initialization process is completed, the CPU 308 reads out the control program from the ROM 306 and executes it.
[0036]
The control program includes a proxy function for relaying communication using HTTP performed between the mobile phone accommodated in the mobile communication network 200 and the content server 100, and an amount of packets generated by communication using HTTP. And a packet amount totalizing function of transmitting data indicating the totalized amount of packets to the billing system. FIG. 6 shows the flow of processing performed by the packet amount totalizing function.
[0037]
When the first communication unit 301 of the gateway server 300 receives the HTTP request, the processing illustrated in FIG. 6 is executed.
First, the CPU 308 receives, from the first communication unit 301, an HTTP request using the GE method transmitted from a mobile phone accommodated in the mobile communication network 200 (step SA1). Next, in order to relay the received HTTP request, the CPU 308 establishes a connection with the server specified by the URL included in the received HTTP request as a parameter of the GET method, and specifies the HTTP request by the URL. (SA2). The CPU 308 generates an identifier for identifying the connection when the connection is established (hereinafter, referred to as a connection identifier).
[0038]
After relaying the HTTP request, the CPU 308 totalizes the amount of packets generated by the HTTP request transmitted from the mobile phone accommodated in the mobile communication network 200 by packet communication. After totalizing the amount of the packet, the CPU 308 associates the identifier (hereinafter, referred to as a mobile phone identifier) for identifying the mobile phone that has transmitted the HTTP request included in the packet with the HTTP identifier in association with the connection identifier. Is stored in the storage unit 305 (SA3).
[0039]
Next, CPU 308 determines whether or not an HTTP response transmitted to gateway server 300 has been received from second communication unit 302 as a response to the HTTP request transmitted in step SA2 (SA4).
When determining that the HTTP response has not been received (SA4: NO), the CPU 308 determines whether or not a predetermined time has elapsed in step SA5. If CPU 308 determines in step SA5 that the predetermined time has not elapsed, the process returns to step SA4. If the CPU 308 determines “YES” in step SA5, the data relating to the packet communication stored in the storage unit 305 using the connection identifier of the HTTP request corresponding to the HTTP response waiting to be received as a key. Search for the corresponding mobile phone identifier from.
[0040]
Next, the CPU 308 searches the subscriber file F1 of the subscriber database 400 using the read mobile phone identifier as a key. When finding the relevant mobile phone identifier from the subscriber file F1, the CPU 308 reads the user identifier for identifying the user using the mobile phone, stored in association with the mobile phone identifier. The CPU 308 stores the read user identifier in the area for storing the chargeable person identifier in association with the connection identifier (step SA6).
After specifying the billing destination for the packet communication performed for the HTTP request in step SA6, the CPU 308 transmits to the billing system 500 a billing information notification including the billing person identifier and the packet amount generated by the HTTP request. (SA7), the processing ends.
[0041]
When determining “YES” in step SA4, the CPU 308 totals the amount of packets generated in the HTTP response received by the packet communication, associates the amount of the packets with the connection identifier, and generates the total number of packets generated in the HTTP response. Is stored in the storage unit 304 (SA8).
[0042]
Next, the CPU 308 refers to the billing destination specification header included in the received HTTP response, and determines a billing target of the HTTP response and the packet communication performed for the HTTP response that is paired with the HTTP response. (SA9).
[0043]
If CPU 308 determines that the contents of the billing destination designation header instructs the user of the mobile phone accommodated in mobile communication network 200 to perform billing (SA9: NO), the process proceeds to step S9. In SA3, the subscriber file F1 in the subscriber database 400 is searched using the mobile phone identifier stored in the storage unit 304 as a key. When finding the relevant mobile phone identifier from the subscriber file F1, the CPU 308 reads the user identifier for identifying the user using the mobile phone, stored in association with the mobile phone identifier. CPU 308 stores the read user identifier in the area for storing the chargeable person identifier in association with the connection identifier (step SA10).
[0044]
If the CPU 308 determines that the contents of the billing destination designation header instructs the carrier operating the server that provides the Web page to charge (SA9: YES), the billing destination designation is performed. Using the server identifier added to the parameter of the header as a key, a search is made for the carrier file F2 in the subscriber database 400. When finding the corresponding server identifier from the communication carrier file F2, the CPU 308 reads the carrier identifier stored in association with the server identifier. The CPU 308 stores the read provider identifier in the area for storing the chargeable party identifier in association with the connection identifier (step SA11).
[0045]
After specifying the billing destination for the packet communication performed for the HTTP request and the HTTP response in step SA10 or step SA11, the CPU 308 determines the billing target identifier, the packet amount generated by the HTTP request, and the packet generated by the HTTP response. A billing information notification including the quantity is transmitted to billing system 500 (SA12).
[0046]
After transmitting the billing information notification, the CPU 308 deletes the billing destination designation header from the header data of the received HTTP response, and transmits the HTTP response with the billing destination designation header deleted to the mobile phone that is the destination of the HTTP response. (SA13).
[0047]
[2. Operation example]
Next, an operation example of the embodiment of the present invention will be described with reference to FIG.
In the operation described below, in the content server 100, a server program that is turned on by the administrator of the content server 100 and that transmits and receives data based on HTTP with a mobile phone accommodated in the mobile communication network 200 has already been executed. It is assumed that
In the gateway server 300, the power is turned on by the administrator of the gateway server 300, and a control program for controlling each unit of the gateway server 300 is already executed.
In the mobile phone 600, it is assumed that the power is turned on by the user, the WWW browser is already executed by the user's operation, and the browser screen M1 shown in FIG. 8 is displayed.
[0048]
The operation in which the mobile phone 600 acquires the web page data provided by the content server 100 starts when the user of the mobile phone 600 operates the mobile phone 600 and tries to acquire the web page data.
[0049]
First, the user of the mobile phone 600 writes “http://www.abc.co.jp/abc.html”, which is the URL of the Web page provided by the content server 100, in the text box for specifying the URL in the browser screen. Is performed, the browser screen M2 shown in FIG. 8 is displayed on the display unit of the mobile phone 600 (step S101).
Next, when the user of the mobile phone 600 performs an operation of clicking a “display” button on the browser screen to display the Web page specified by the input URL (step S102), the mobile phone 600 An HTTP request using “GET” which is one of the methods is generated. This HTTP request includes the URL “http://www.abc.co.jp/abc.html” input in the text box for inputting the URL as a parameter of the GET method.
[0050]
The HTTP request generated by the mobile phone 600 is transmitted from the mobile phone 600 to a wireless base station of the mobile communication network 200. The HTTP request received by the wireless base station is transmitted to the gateway server 300 via the exchange (Step S103).
[0051]
The first communication unit 301 of the gateway server 300 that has received the HTTP request sends the received HTTP request to the CPU 308. The CPU 308 transmits the received HTTP request to the content server 100 specified by the URL “http://www.abc.co.jp/abc.html” that is a parameter of the GET method included in the HTTP request. To this end, first, a connection is established with the content server 100 indicated by the URL included in the received HTTP request (step S104). Upon establishing the connection, the CPU 308 generates “ID001” as a connection identifier to identify the connection. After the connection is established, the CPU 308 transmits the received HTTP request to the content server 100 via the second communication unit 302 (Step S105).
[0052]
After relaying the HTTP request, CPU 308 counts the amount of packets generated by the HTTP request transmitted from mobile phone 600 by packet communication, and establishes a connection identifier for identifying the connection between gateway server 300 and content server 100. The storage unit 305 stores the mobile phone identifier “0 * 0-1111-2222” included in the transmitted packet and the data “10” indicating the packet amount generated by the HTTP request in association with “ID001”. It is stored (step S106).
[0053]
The HTTP request transmitted from the gateway server 300 is received by the communication unit 101 of the content server 100. The HTTP request received by the communication unit 101 is sent to the CPU 107.
Upon receiving the HTTP request, the CPU 107 stores Web page data specified by the URL “http://www.abc.co.jp/abc.html” which is a parameter of the GET method included in the HTTP request. The data is read from the memory 104 (step S107).
[0054]
The CPU 107 adds “X-DCM”, which is a header for designating a person to be charged for packet communication performed to obtain “abc.html” to the header data indicating the date and time and the like in the read Web page data. :: ”is added.
Since the communication company that operates the content server 100 is a communication company that provides a Web page to users of mobile phones accommodated in the mobile communication network 200 free of charge, the CPU 107 sets the charge destination designation header. In the parameter, “2” indicating that the chargeable person is the Web page provider and a server identifier “12345678” for identifying the content server 100 are set (step S108).
[0055]
Next, the CPU 107 generates an HTTP response including the Web page data to which the charging destination header is added. The generated HTTP response is transmitted from the content server 100 to the gateway server 300 (Step S109).
[0056]
The second communication unit 302 of the gateway server 300 that has received the HTTP response sends the received HTTP response to the CPU 308. The CPU 308 that has received the HTTP response totals the amount of packets generated in the HTTP response transmitted from the content server 100 by packet communication. Next, the CPU 308 stores data “100” indicating the amount of packets generated in the HTTP response in the storage unit 305 in association with the connection identifier “ID001” that identifies the connection between the gateway server 300 and the content server 100. (Step S110).
[0057]
Next, the CPU 308 refers to the charging destination designation header “X-DCM: 2/12345678” included in the HTTP response transmitted from the content server 100. Since the parameter of the billing destination designation header is “2/12345678”, the CPU 308 searches the communication carrier file F2 of the subscriber database 400 using the server identifier “12345678” as a key. When finding the server identifier “12345678” from the Web page provider file F2, the CPU 308 reads the business identifier “ABC company” stored in association with the server identifier, and replaces the read business identifier with the connection identifier “ It is stored in the area for storing the chargeable person identifier in association with “ID001” (step S111). When the process of step S111 is performed, data related to the packet communication with the connection ID “ID001” is stored in the format F3 shown in FIG.
[0058]
Next, the CPU 308 generates a billing information notification including the HTTP request and the packet amount generated in the HTTP response paired with the HTTP request, and a billing target person identifier, and transmits the generated billing information notification to the billing system 500. (Step S112).
In the billing system 500 that has received the billing information notification, the billing process is performed based on the data included in the billing information notification, and billing is performed for the communication carrier whose carrier identifier is “ABC company”.
[0059]
After transmitting the accounting information notification to the accounting system 500, the CPU 308 deletes the accounting destination designation header “X-DCM: 2/12345678” from the header data included in the HTTP response.
[0060]
The HTTP response from which the billing destination designation header has been deleted is transmitted from the gateway server 300 and received by the mobile phone 600 (step S113).
In the mobile phone 600 that has received the HTTP response, the Web page data included in the HTTP response is read, and the browser screen M3 illustrated in FIG. 8 is displayed on the display unit of the mobile phone 600 according to the read Web page data. . The connection between the content server 100 and the gateway server 300 is disconnected after the HTTP response from which the accounting destination designation header is deleted is transmitted from the gateway server 300 (step S114).
[0061]
As described above, according to the present embodiment, it is possible to charge not only the user of the mobile phone 600 but also the Web page provider, which is performed when the user of the mobile phone 600 browses the Web page. Become. Thus, the user of the mobile phone 600 can browse the Web page for free. Further, if the user of the mobile phone 600 can browse the Web page free of charge, the number of viewers of the Web page provided by the content server 100 will increase.
[0062]
[3. Modification]
In the above-described embodiment, the content server 100 sets the chargeable person to the communication carrier that operates the content server 100 in the chargeee designation header of the HTTP response, but the content server 100 provides a plurality of Web page data. In this case, the charging target may be switched between the Web page provider and the user of the mobile phone for each Web page data.
[0063]
In the above-described embodiment, the provider of the Web page data is the communication company that operates the content server 100. However, the provider of the Web page data is not the communication company that operates the content server 100, but the Web company. A person who has made a contract to rent the storage unit 104 of the content server 100 to provide the page data may be used.
Further, in such an embodiment, when the content server 100 provides a plurality of Web page data, a contract for renting the storage unit 104 of the content server 100 with the chargeable person rather than the communication company that operates the content server 100 is made. You may be. When performing such an aspect, the parameter of the billing destination designation header is changed from the server identifier to an identifier for identifying the person who provides the Web page, and the server identifier of the communication carrier file F2 is changed to the person who provides the Web page. If the identifier is used for identification, it becomes possible to charge for each person who provides the Web page. According to such an aspect, the person who provides the Web page data does not need to operate the server, and many people can provide the Web page data.
[0064]
If the Web page data includes image data such as a banner advertisement, the user of the mobile phone 600 is charged for packet communication performed to acquire the Web page data, and the Web page data is acquired. For the packet communication performed to acquire the image data of the banner advertisement performed after the above, the communication company operating the content server 100 may be charged.
[0065]
Further, in a case where the Web page data includes image data such as a banner advertisement, a fee is charged to a provider that provides the Web page data for packet communication performed to acquire the Web page data, For the packet communication performed to acquire the image data of the banner advertisement performed after the acquisition of the page data, a person who provides the data of the banner advertisement may be charged.
When performing such an aspect, the parameter of the billing destination designation header is changed from the server identifier to an identifier for identifying a person who provides Web page data or banner advertisement data, and the server identifier of the communication carrier file F2 is changed to Web. If the identifier is used to identify a person who provides page data or banner advertisement data, it becomes possible to charge a person who provides banner advertisement data.
[0066]
When the chargeable person is a Web page provider, the content server 100 is provided with a clock function, and the storage unit 104 stores a date and a period for providing the Web page free of charge, and specifies the date and the period. Web pages may be browsed for free.
[0067]
In the above-described embodiment, the content server 100 connected to the gateway server 300 by a dedicated line provides the web page data. However, the content server 100 is connected to the Internet, and the server device connected to the Internet is a content device. Web page data may be provided via the server 100 and the gateway server 300.
[0068]
In the above-described embodiment, the case of communication using HTTP has been described, but another protocol such as HTTPS may be used.
[0069]
In the above-described embodiment, a description will be given of a pull-type information service in which the mobile phone 600 acquires Web page data stored in the content server 100, that is, a user of a client device actively acquires information. However, the present invention is not limited to a pull-type information service, but may be applied to a push-type information service in which a server device actively provides information to a user.
As the push-type information service, for example, the following services can be considered.
The content server 100 transmits an e-mail to the mobile phone 600 by using SMTP (Simple Mail Transfer Protocol). The header data of the e-mail sent from the content server 100 includes information indicating a destination, information indicating a transmission source, and a billing destination designation header.
The e-mail transmitted from the content server 100 is received by the gateway server 300. The gateway server 300 refers to the billing destination designation header in the header data of the e-mail, and charges the billing destination specified by the billing destination designation header.
According to such an aspect, it is possible to charge a communication carrier that provides information not only in the pull-type information service but also in the push-type information service.
[0070]
Also, the gateway server 300 determines the content of the HTTP request transmitted from the mobile phone 600, and if the HTTP request is a request using the GET method, performs the operation described in the operation example of the embodiment. If the request is to perform a push-type operation, normal billing may be performed.
[0071]
Further, the mobile phone identifier is not limited to the telephone number of the mobile phone, but may be another code as long as the mobile phone can be identified.
[0072]
In the above-described embodiment, the billing system 500 for billing and the subscriber database 400 storing data on subscribers and Web page providers are configured independently of the gateway server 300. 300, the subscriber database 400 and the billing system 500 may be integrated.
[0073]
Further, in the above-described embodiment, the gateway server 300 deletes the charging destination specification header when transmitting the HTTP response to the mobile phone 600. However, the gateway server 300 does not delete the charging destination specification header but sends the HTTP response to the mobile phone 600 as it is. May be transmitted.
[0074]
In the above-described embodiment, the GET method is used in the HTTP request. However, the present invention is not limited to this, and another method such as a POST method or a CONNECT method may be used.
[0075]
In the above-described embodiment, the billing target person is set only by the billing destination designation header. However, the billing target person is designated by the method described below instead of setting the billing target person only by the billing destination designation header. You may make it.
FIG. 9 is a diagram showing a modification (F4) of the format of the communication carrier file stored in the subscriber database 400. As shown in FIG. 9, the domain name of the server operated by the company identified by the company identifier is added to the format F2 shown in FIG.
FIG. 10 is a flowchart showing a modified example of the packet amount totalizing function shown in FIG. In the case of the modification, when the HTTP request is received by the first communication unit of the gateway server 300, the processing illustrated in FIG. 10 is executed.
[0076]
The processing from step SB1 to step SB3 is the same as the processing from step SA1 to step SA3 shown in FIG. 6, and a description thereof will be omitted.
[0077]
The CPU 308 searches the communication carrier file F4 of the subscriber database 400 using the domain name indicated by the URL included in the received HTTP request as a parameter of the GET method as a key, and matches the HTTP request with the HTTP request. It is determined whether or not the person to be charged for the packet communication performed for the HTTP response becomes the user of the mobile phone that has transmitted the HTTP request (step SB4).
[0078]
If there is no corresponding domain name as a result of the search (step SB4: NO), the CPU 308 searches the subscriber file F1 of the subscriber database 400 using the mobile phone identifier as a key. When finding the relevant mobile phone identifier from the subscriber file F1, the CPU 308 reads the user identifier for identifying the user using the mobile phone, stored in association with the mobile phone identifier. The CPU 308 stores the read user identifier in the RAM 307 as data indicating the provisional person to be charged in association with the connection identifier (step SB5).
[0079]
Next, the CPU 308 determines whether an HTTP response transmitted to the gateway server 300 has been received as a response to the HTTP request relayed by the CPU 308 (SB6).
The processing when the CPU 308 determines that the HTTP response has not been received (step SB6: NO) is the same as the processing from steps SA4 to SA7 in FIG. 6, and therefore the description thereof is omitted.
[0080]
When determining “YES” in step SB6, the CPU 308 totals the amount of packets generated in the HTTP response received by the packet communication, associates the amount of the packets with the connection identifier, and generates the packet generated in the totaled HTTP response. Is stored in the storage unit 304 (SB10).
[0081]
Next, the CPU 308 refers to the status header added to the header of the HTTP response, and determines whether the HTTP request corresponding to the HTTP response has been normally processed at the destination of the HTTP response (SB11). .
[0082]
If the CPU 308 refers to the status header and determines that the HTTP request corresponding to the HTTP response has been normally processed by the server specified by the URL included in the HTTP request (step SB11: YES), With reference to the billing destination designation header included in the received HTTP response, a person to be charged for packet communication performed for the HTTP response and the HTTP response that is paired with the HTTP response is determined (SB12).
[0083]
The CPU 308 determines whether the provisional person to be charged set in step SB5 is the user of the mobile phone, or the content of the billing destination designation header is set to the user of the mobile phone accommodated in the mobile communication network 200. If it is determined that charging is instructed (SB12: NO), a search is made for the subscriber file F1 in the subscriber database 400 using the mobile phone identifier stored in the storage unit 304 as a key in step SB3. I do. When finding the relevant mobile phone identifier from the subscriber file F1, the CPU 308 reads the user identifier for identifying the user using the mobile phone, stored in association with the mobile phone identifier. The CPU 308 stores the read user identifier in the area for storing the chargeable person identifier in association with the connection identifier (step SB13).
[0084]
The CPU 308 bills the provisional billing target set in step SB5 not to the user of the mobile phone, and the content of the billing destination designation header is charged to the communication carrier operating the server that provides the Web page. Is determined (SB12: YES), the communication carrier file F4 of the subscriber database 400 is searched using the server identifier added to the parameter of the billing destination designation header as a key. . When finding the corresponding server identifier from the communication carrier file F4, the CPU 308 reads the carrier identifier stored in association with the server identifier. The CPU 308 stores the read provider identifier in the area for storing the chargeable party identifier in association with the connection identifier (step SB14).
[0085]
If the CPU 308 determines “NO” in the step SB11, the CPU 308 uses the connection identifier of the HTTP request corresponding to the HTTP response as a key and selects the corresponding mobile phone from the data related to the packet communication stored in the storage unit 305. Search for an identifier.
[0086]
Next, the CPU 308 searches the subscriber file F1 of the subscriber database 400 using the read mobile phone identifier as a key. When finding the relevant mobile phone identifier from the subscriber file F1, the CPU 308 reads the user identifier for identifying the user using the mobile phone, stored in association with the mobile phone identifier. The CPU 308 stores the read user identifier in the area for storing the chargeable person identifier in association with the connection identifier (step SB13).
[0087]
The CPU 308 specifies the billing destination for the packet communication performed for the HTTP request and the HTTP response by the processes of steps SB11 to SB14, and then, the billing target identifier, the packet amount generated by the HTTP request, and the amount generated by the HTTP response. A charging information notification including the packet amount is transmitted to charging system 500 (SB15).
[0088]
After transmitting the billing information notification, the CPU 308 deletes the billing destination designation header from the header data of the received HTTP response, and transmits the HTTP response with the billing destination designation header deleted to the mobile phone that is the destination of the HTTP response. (SB16).
[0089]
According to the above-described aspect, even if a server that is not registered in the subscriber database 400 sets the billing destination designation header with the server registered in the subscriber database 400 as the billing destination, the server is not designated in the billing destination designation header. The communication carrier is not charged, and it is possible to prevent disadvantages caused by disguising the charging destination designation header.
Further, according to the above-described embodiment, when the HTTP response is not transmitted to the mobile phone 600 normally, the user of the mobile phone 600 is charged. Specifically, when the user of the mobile phone 600 disconnects the connection before or during the reception of the HTTP response and the Web page is not normally displayed on the mobile phone 600, the user of the mobile phone 600 is charged. Will be done. As a result, it is possible to avoid a disadvantage that the communication service provider is charged even though the Web page is not normally provided, and the communication service provider is disadvantaged.
[0090]
【The invention's effect】
As described above, according to the present invention, when a portable communication terminal acquires data provided by a data provider, the person to be charged for communication performed to acquire the data is It can be a data provider. In addition, the billing destination can be specified by the server operated by the data provider, so that the billing destination can be specified as desired by the data provider.
[Brief description of the drawings]
FIG. 1 is a diagram illustrating an overall configuration of a communication system 10 according to an embodiment of the present invention.
FIG. 2 is a diagram illustrating a format of a subscriber file and a carrier file stored in a subscriber database 400 according to the embodiment of the present invention.
FIG. 3 is a diagram illustrating a hardware configuration of a content server 100 according to the embodiment of the present invention.
FIG. 4 is a diagram illustrating a hardware configuration of the gateway server 300 according to the embodiment of the present invention.
FIG. 5 is a diagram illustrating a format of data relating to packet communication stored in a storage unit 305 of the gateway server 300 according to the embodiment of the present invention.
FIG. 6 is a flowchart exemplifying a flow of a process of counting the amount of packets performed by the gateway server 300 according to the embodiment of the present invention.
FIG. 7 is a sequence diagram for explaining the operation of the embodiment of the present invention.
FIG. 8 is a diagram exemplifying a screen displayed on a display unit of the mobile phone 600 according to the embodiment of the present invention.
FIG. 9 is a diagram exemplifying a format of data relating to packet communication stored in a storage unit 305 of the gateway server 300 according to a modification of the present invention.
FIG. 10 is a flowchart illustrating a flow of a process of counting the amount of packets performed by a gateway server 300 according to a modification of the present invention.
[Explanation of symbols]
10 Communication system.
100: content server, 200: mobile communication network, 300: gateway server, 400: subscriber database, 500: billing system.
101: communication unit, 102: operation unit, 103: display unit, 104: storage unit, 105: ROM, 106: RAM, 107: CPU, 110 ... bus.
301 ... first communication unit, 302 ... second communication unit, 303 ... operation unit, 304 ... display unit, 305 ... storage unit, 306 ... ROM, 307 ... RAM 308 CPU, 310 bus.

Claims (7)

A portable communication terminal capable of using a communication network transmits a data acquisition request for requesting data acquisition to the relay device that determines a charging destination for charging performed for the relayed communication via the communication network. An acquisition request sending step;
An acquisition request relaying step in which the relay device receives the data acquisition request and transmits the received data acquisition request to a server device including a storage unit that stores data.
The server device receives the data acquisition request, and in response to the received data acquisition request, specifies the billing destination as either a user of the mobile communication terminal or a data provider that provides the data. A data response transmission step of transmitting a data acquisition response including the billing person information and the data requested by the mobile communication terminal to the relay device,
An acquisition response receiving step in which the relay device receives the data acquisition response transmitted in the data response transmitting step,
The relay device is paired with the data acquisition request and the data acquisition request relayed by the relay device based on the billing person information included in the data acquisition response received in the acquisition response receiving step. A billing person determining step of determining a billing destination of billing performed for the data acquisition response;
A data acquisition response relaying step of transmitting, to the mobile communication terminal, the data acquisition response received by the relay device in the acquisition response receiving step. The portable communication terminal includes a data transmission step of transmitting a data transmission request including a data transmission destination and data to the relay device via the communication network,
The relay device, upon receiving the data transmission request transmitted in the data transmission step, sets a billing destination for the data transmission request relayed by the relay device to a user of the mobile communication terminal. The method according to claim 1, wherein the data transmission request is transmitted to a destination included in the data transmission request. A server device having a storage unit for storing data, the data provision for providing a user of a mobile communication terminal capable of using the communication network or a user of a billing destination of a billing performed for communication relayed by the relay device; Distribution data transmission step of transmitting, to the relay device, distribution data including the billing person information and the data for specifying any of the persons,
A delivery data receiving step of receiving the delivery data transmitted in the delivery data transmitting step,
The relay device determines a billing destination of a billing performed on the distribution data relayed by the relay device based on the billing target information included in the distribution data received in the distribution data receiving step. Billing person determination step to be performed;
A relay data transmitting step of transmitting the distribution data received in the distribution data receiving step to a portable communication terminal capable of using a communication network. The communication performed by the mobile communication terminal, the relay device, and the server device is a packet communication, and the communication network performs charging based on an amount of packets relayed by the relay device. The charging method according to 1 or 3. A data acquisition request for requesting data acquisition is received from a portable communication terminal capable of using a communication network via the communication network, and the received data acquisition request is transmitted to a server device having a storage unit for storing data. Acquisition request relay means to be transmitted;
The server obtains a data acquisition response including billing target information for specifying a billing destination as either a user of the portable communication terminal or a data provider providing the data, and data requested by the portable communication terminal. Acquisition response receiving means for receiving from the device;
Based on the billing person information included in the data acquisition response received by the acquisition response receiving means, the data acquisition request relayed by the device and the data acquisition response that is paired with the data acquisition request Billing person determination means for determining a billing destination for billing to be performed,
A relay unit that transmits a data acquisition response received by the acquisition response receiving unit to the mobile communication terminal. Computer equipment,
A data acquisition request for requesting data acquisition is received from a mobile communication terminal capable of using a communication network via the communication network, and the received data acquisition request is transmitted to a server device having a storage unit for storing data. Acquisition request relay means to
The server obtains a data acquisition response including billing target information for specifying a billing destination as either a user of the portable communication terminal or a data provider providing the data, and data requested by the portable communication terminal. Acquisition response receiving means for receiving from the device;
Based on the chargeable person information included in the data acquisition response received by the acquisition response receiving unit, the computer device relays the data acquisition request and the data acquisition response that is paired with the data acquisition request. Chargeable person determination means for determining a billing destination for billing performed on the person;
A program for functioning as a data acquisition response relay unit that transmits a data acquisition response received by the acquisition response reception unit to the mobile communication terminal. A computer-readable recording medium on which the program according to claim 6 is recorded.

Images