Data communication terminal, fee management system and fee management method and program

Abstract

The present invention determines whether the data traffic of the application is for private use or for business use and charges data communication charge to the appropriate user based on the traffic usage. The data communication terminal 100 runs an application, executes data communication to transmit tag information and the data traffic of the data communication to the charge management server 10 in response to the execution of the data communication. The charge management server 10 calculates the data communication charge corresponding to the data traffic received from the data communication terminal, and determines whether the data traffic is for private use or for business use based on the tag information received from the data communication terminal to calculate the data communication charge for each usage.

Claims

1. A charge management system comprising: a data communication terminal and a charge management server managing a charge for the data communication terminal, wherein the data communication terminal includes: a data communication unit running an application to execute data communication over a given data communication pathway; and a data communication information transmitter unit transmitting tag information and the data traffic of the data communication to the charge management server in response to the execution of the data communication; and the charge management server includes: a data communication charge calculating unit calculating data communication charge corresponding to the data traffic received from the data communication terminal via said given data communication pathway; and a usage-based charge calculating unit determining whether the data traffic over said given data communication pathway is for private use or for business use based on the tag information received from the data communication terminal to calculate data communication charge for each usage; wherein the usage-based charge calculating unit determines the usage based on an email address included in the received tag information to calculate the data communication charge for each usage.

2. A charge management system comprising: a data communication terminal and a charge management server managing a charge for the data communication terminal, wherein the data communication terminal includes: a data communication unit running an application to execute data communication over a given data communication pathway; and a data communication information transmitter unit transmitting tag information and the data traffic of the data communication to the charge management server in response to the execution of the data communication; and the charge management server includes: a data communication charge calculating unit calculating data communication charge corresponding to the data traffic received from the data communication terminal via said given data communication pathway; and a usage-based charge calculating unit determining whether the data traffic over said given data communication pathway is for private use or for business use based on the tag information received from the data communication terminal to calculate data communication charge for each usage; wherein the usage-based charge calculating unit determines the usage based on the size of an attached file included in the received tag information to calculate the data communication charge for each usage.

3. A charge management system comprising: a data communication terminal and a charge management server managing a charge for the data communication terminal, wherein the data communication terminal includes: a data communication unit running an application to execute data communication over a given data communication pathway; and a data communication information transmitter unit transmitting tag information and the data traffic of the data communication to the charge management server in response to the execution of the data communication; and the charge management server includes: a data communication charge calculating unit calculating data communication charge corresponding to the data traffic received from the data communication terminal via said given data communication pathway; and a usage-based charge calculating unit determining whether the data traffic over said given data communication pathway is for private use or for business use based on the tag information received from the data communication terminal to calculate data communication charge for each usage; wherein the usage-based charge calculating unit determines the usage based on the data traffic included in the received tag information to calculate data communication charge for each usage.

4. A data communication terminal managing its own data communication charge, comprising: a data communication unit running an application to execute the data communication over a given data communication pathway; a data communication information storage unit to acquire tag information and the data traffic of the data communication via said given data communication pathway in response to the execution of the data communication; a data communication charge calculating unit calculating data communication charge corresponding to the acquired data traffic; a usage-based charge calculating unit determining whether the data traffic communicated via said given data communication pathway is for private use or for business use based on the acquired tag information to calculate data communication charge for each usage; and a data communication charge transmitter unit transmitting the calculated data charge for each usage; wherein the usage-based charge calculating unit determines the usage based on the data traffic included in the received tag information to calculate data communication charge for each usage or wherein the usage-based charge calculating unit determines the usage based on the size of an attached file included in the received tag information to calculate the data communication charge for each usage; wherein the usage-based charge calculating unit determines the usage based on the data traffic included in the received tag information to calculate data communication charge for each usage or wherein the usage-based charge calculating unit determines the usage based on the size of an attached file included in the received tag information to calculate the data communication charge for each usage or wherein the usage-based charge calculating unit determines the usage based on an email address included in the received tag information to calculate the data communication charge for each usage.

5. The data communication terminal according to claim 4 further comprising a billing unit charging the data communication charge for each usage calculated by the usage-based charge calculating unit to a billing address based on the usage.

Description

BRIEF DESCRIPTION OF DRAWINGS

(1) FIG. 1 shows the system configuration diagram of a charge management system 1.

(2) FIG. 2 shows the functional block diagram of a charge management server 10 and a data communication terminal 100 in the first embodiment.

(3) FIG. 3 shows the flow chart of the charge management process executed by a charge management server 10 and a data communication terminal 100 in the first embodiment.

(4) FIG. 4 shows the sorting table stored by a charge management server 10.

(5) FIG. 5 shows the charge amount table stored by a charge management server 10.

(6) FIG. 6 shows the functional block diagram of a charge management server 10 and a data communication terminal 100 in the second embodiment.

(7) FIG. 7 shows the flow chart of the charge management process executed by a charge management server 10 and a data communication terminal 100 in the second embodiment.

DESCRIPTION OF EMBODIMENTS

(8) Hereinafter, a best mode of the present invention will be described with reference to the attached drawings. However, this is illustrative only, and the technological scope of the present invention is not limited thereto.

First Embodiment

Configuration of Charge Management System 1

(9) FIG. 1 is the configuration diagram of the charge management system 1 as a preferred embodiment of the first aspect of the present invention. The charge management system includes a charge management server 10, data communication terminals 100a, b, c (hereinafter merely referred to as data communication terminal 100 unless otherwise specified) and a common carrier DB 5. The charge management server 10 is communicatively connected with the data communication terminal 100 and the common carrier DB 5 through a public network 3 (the Internet network, third generation or fourth generation communication network, etc.)

(10) The charge management server 10 is a server device provided with the functions described later. Moreover, the data communication terminal 100 is electrical appliances provided with the functions described later.

(11) The data communication terminal 100 may be information appliances such as a smartphone, a tablet terminal, a net book terminal, a slate terminal, and an electronic book terminal in addition to a personal computer, a cellular phone, and a portable terminal.

(12) The common carrier DB 5 stores the price plan created by each common carrier.

(13) Functions

(14) The configuration of each device will be explained with reference to FIG. 2.

(15) The charge management server 10 may include a control unit 11 such as a central processing unit (hereinafter referred to as CPU), random access memory (hereinafter referred to as RAM), and read only memory (hereinafter referred to as ROM) and a communication unit 12 such as a device capable of communicating with other devices, for example a Wireless Fidelity or Wi-Fi enabled device complying with IEEE 802.11.

(16) The charge management server 10 also includes a data storage unit such as a hard disk, semiconductor memory, a recording medium, or a memory card as a storage unit 13 storing data and files. The charge management server 10 stores the sorting table and the charge amount table in the storage unit 13 described later.

(17) In the charge management server 10, the control unit 11 reads a predetermined program and cooperates with the communication unit 12 to achieve a data traffic receiver module 20, a tag information receiver module 21, a billing module 22, and a price plan acquisition module 23. The control unit 11 also reads a predetermined program and cooperates with the storage unit 13 to achieve a sorting table storing module 30, a data communication charge calculating module 31, and a usage-based charge calculating module 32.

(18) The data communication terminal 100 may include the control unit 110 such as a central processing unit (hereinafter referred to as CPU), random access memory (hereinafter referred to as RAM), and read only memory (hereinafter referred to as ROM) and the communication unit 120 such as a device capable of communicating with other devices, for example a Wireless Fidelity or Wi-Fi enabled device complying with IEEE 802.11, and LTE (Long Term Evolution) enabled device.

(19) The data communication terminal 100 may also include a display unit outputting data and images that are controlled by the control unit as an output unit; and a touch panel, a keyboard, a mouse, and the like that receive input from a user as an input unit.

(20) The control unit 110 also reads a predetermined program and cooperates with the communication unit 120 to achieve a data traffic transmitter module 200, a tag information transmitter module 210, and a data communication module 220.

(21) Charge Management Process

(22) FIG. 3 is the flow chart of the charge management process executed by the charge management server 10 and the data communication terminal 100. The process executed by the modules of each of the above-mentioned devices will be explained together with this process.

(23) The price plan acquisition module 23 of the charge management server 10 acquires the price plan of the data communication terminal 100 from the common carrier DB 5 beforehand (Step S10). In the step S10, the price plan acquired by the price plan acquisition module 23 may be a price plan for which each user or the administrator of charge management server 10 has contracted with a common carrier beforehand. Moreover, the price plan may not be a price plan of each data communication terminal 100 but a price plan for which the charge management server 10 has contracted in bulk with a common carrier. Moreover, it may be another price plan. The price plan acquisition module 23 of the charge management server 10 may acquire the price plan from the data communication terminal 10.

(24) The data communication module 220 of the data communication terminal 100 receives operation to the input-output unit of the data communication terminal 100 and the selection and the execution of an application. The data communication module 220 of the data communication terminal 100 starts the data communication of the executed application (Step S11). In the step S11, the application executed by the data communication module 220 includes various applications such as an email application, a web browser application, a groupware application, and a business oriented application.

(25) The data traffic transmitter module 200 of the data communication terminal 100 transmits the data traffic of the data communication by the application executed by the data communication module 220 to the charge management server 10 (Step S12). In the step S12, the data traffic transmitted from the data traffic transmitter module 200 is generated by each application. In the step S12, the data communication terminal 100 determines whether the on-going data communication is LTE or Wi-Fi. If the data communication terminal 100 determines that it is LTE, the data traffic transmitter module 200 transmits the data traffic. If the data communication terminal 100 determines that the on-going data communication is Wi-Fi, the data traffic transmitter module 200 terminates the current process without transmitting the data traffic.

(26) The data traffic receiver module 20 of the charge management server 10 receives the data traffic from the data traffic transmitter module 200 of the data communication terminal 100 (Step S13).

(27) The tag information transmitter module 210 of the data communication terminal 100 transmits the tag information of the data communication executed by the data communication module 220 to the charge management server 10 (Step S14). In the step S14, the tag information transmitted by the tag information transmitter module 210 includes the type of the used application and the data used by the application. The information on the data includes for example, the URL browsed through a web browser application, and the destination email address, the originating email address, the presence or absence of the attached file, and size of attached file that have sent through an email application.

(28) The tag information receiver module 21 of the charge management server 10 receives the tag information transmitted from the tag information transmitter module 210 of the data communication terminal 100 (Step S15).

(29) The data communication charge calculating module 31 of the charge management server 10 calculates data communication charge for the data traffic based on the received data traffic (Step S16).

(30) The sorting table storing module 30 of the charge management server 10 looks up the sorting table (Step 17) shown in FIG. 4 and determines whether the data communication is private use or business use based on the received tag information (Step S18 and Step S19).

(31) Sorting Table

(32) The sorting table referred by sorting table storing module 30 is described below with reference to FIG. 4.

(33) The sorting table is stored in the storage unit 13 of the charge management server 10. The sorting table associates the content of communication with the usage. Specifically, URL, the type of application, and email addresses are included in the content of the communication. The character string business or private is stored as the usage. In the sorting table, the content of the communication are associated with each usage.

(34) For example, the content of the communication associated with business use includes http://aaaaa.com for URL, In-house groupware application for the type of application, xxxxx@xxx.com for the email address and attached file size: 5 MB for the size of attached file. On the other hand, the content of the communication associated with private use includes http://www.xxxx.com for URL, YYYY application for the type of application, yyyyy@yyyy.com for the email address, and attached file size: 1 MB for the size of attached file. The item data of the sorting table may be entered by the user or the administrator of the charge management server 10. The item data other than those described in this embodiment may be registered beforehand.

(35) The usage-based charge calculating module 32 of the charge management server 10 determines whether the usage of the data communication received is for business or not based on the received tag information and the sorting table (Step S18).

(36) In the step S18, the usage-based charge calculating module 32 determines whether the usage is for business or not based on the usage associated with tag information received by the tag information receiver module 21. If determining that the usage is for business (Step S18: YES), the usage-based charge calculating module 32 calculates the usage-based charge and stores the amount of charge and the data amount in the charge amount table shown in FIG. 5 described later (Step S20).

(37) In the step S18, the process executed by the usage-based charge calculating module 32 is described specifically below.

(38) When the tag information received is http://aaaaa.com as URL, the usage-based charge calculating module 32 looks up the sorting table to acquire the usage associated with the URL. The usage-based charge calculating module 32 determines that the usage is for business because the usage associated with the URL is for business. When the tag information received is In-house groupware application as the type of application, the usage-based charge calculating module 32 looks up the sorting table to acquire the usage associated with the type of application. The usage-based charge calculating module 32 determines that the usage is for business because the usage associated with the type of application is for business. When the tag information received is xxxxx@xxx.com as email address, the usage-based charge calculating module 32 looks up the sorting table to acquire the usage associated with the email address. The usage-based charge calculating module 32 determines that the usage is for business because the usage associated with the email address is for business. When the tag information received is attached file size: 5 MB as size of attached file, the usage-based charge calculating module 32 looks up the sorting table to acquire the usage associated with the size of attached file. The usage-based charge calculating module 32 determines that the usage is for business because the usage associated with the size of the attached file is for business.

(39) In the step S18, another method may be used to determine whether the usage is for business or not. For example, the information on whether the attached file is included in the transmitted email may be received as the tag information to determine whether the usage is for business or not based on the presence of the attached file. In this case, the usage is determined to be for business if the attached file is included.

(40) Moreover, when the attached file is included in the transmitted email and the information on the size of attached file is received as the tag information to determine whether the usage is for business or not based on the size of attached file. In this case, the usage is determined to be for business if the size of attached file is equal to or larger than a predefined size.

(41) Moreover, in the step S18, not the destination address but the originating address may be received as the tag information to determine whether the usage is for business or not based on the originating address. In this case, the usage is determined to be for business if the originating address is an email address provided in the office.

(42) Moreover, in the step S18, the data traffic may be received as the tag information to determine whether the usage is for business or not based on the data traffic. In this case, the usage is determined to be for business if the data traffic is equal to or larger than a predefined value.

(43) Moreover, the above-mentioned methods may be combined. For example, it may determine whether the usage is for business or not based on the data traffic and the size of attached file. In this case, the usage may be determined to be for business if the data traffic is equal to or larger than a predetermined value and the size of attached file is equal to or larger than a predetermined size. Moreover, another method may be used to determine whether the usage is for business or not.

(44) In the step S18, if determining that the usage is not for business (Step S18: NO), the usage-based charge calculating module 32 determines whether the usage is for private or not (Step S19).

(45) In the step S19, the usage-based charge calculating module 32 determines whether the usage is for private or not based on the usage associated with the tag information received by the tag information receiver module 21. If determining that the usage is for private (Step S19: YES), the usage-based charge calculating module 32 calculates the usage-based charge and stores the amount of charge and the data amount in the charge amount table shown in FIG. 5 described later (Step S20). Moreover, in the step S19, if determining that the usage is not for private (Step S19: NO), the usage-based charge calculating module 32 terminates the current process.

(46) If determining that the usage is not for business in the above-mentioned step S18 and is not for private in the step S19, the usage may be considered to be for either business or private to calculate the data communication charge. Moreover, in this case, the notification may be sent to the administrator of the charge management server 10 to notify that the usage is unknown, and a process to add the tag information on whether the usage is for business or private for the data communication to the sorting table may be executed.

(47) In the step S19, the process executed by the usage-based charge calculating module 32 is described specifically below.

(48) When the tag information received is http://www.xxxx.com as URL, the usage-based charge calculating module 32 looks up the sorting table to acquire the usage associated with the URL. The usage-based charge calculating module 32 determines that the usage is for private because the usage associated with the URL is for private. When the tag information received is YYYY application as the type of application, the usage-based charge calculating module 32 looks up the sorting table to acquire the usage associated with the type of application. The usage-based charge calculating module 32 determines that the usage is for private because the usage associated with the type of application is for private. When the tag information received is yyyyy@yyyy.com as email address, the usage-based charge calculating module 32 looks up the sorting table to acquire the usage associated with the email address. The usage-based charge calculating module 32 determines that the usage is for private because the usage associated with the email address is for private. When the tag information received is attached file size: 1 MB as size of attached file, the usage-based charge calculating module 32 looks up the sorting table to acquire the usage associated with the size of attached file. The usage-based charge calculating module 32 determines that the usage is for private because the usage associated with the size of attached file is for private.

(49) In the step S19, another method can be used to determine whether the usage is for private or not. For example, information on whether the attached file is included in the transmitted email may be received as the tag information to determine whether the usage is for private or not based on the presence of the attached file. In this case, the usage is determined to be for private if the attached file is not included.

(50) Moreover, when the attached file is included in the transmitted email and the information on the size of attached file is received as the tag information, the usage may be determined to be for private or not based on the size of attached file. In this case, the usage is determined to be for business if the size of attached file is smaller than a predefined size.

(51) Moreover, in the step S18, not the destination address but the originating address may be received as the tag information to determine whether the usage is for private or not based on the originating address. In this case, the usage is determined to be for private if the originating address is not an email address provided in the office.

(52) Moreover, in the step S18, the data traffic may be received as the tag information to determine whether the usage is for private or not based on the data traffic. In this case, the usage is determined to be for private if the data traffic is smaller than a predefined value.

(53) Moreover, the above-mentioned methods may be combined. For example, it may determine whether the usage is for private or not based on the data traffic and the size of attached file. In this case, the usage may be determined to be for private if the data traffic is smaller than a predetermined value and the size of attached file is smaller than a predetermined size. Moreover, another method may be used to determine whether the usage is for private or not.

(54) The usage-based charge calculating module 32 of the charge management server 10 calculates the usage-based charge based on the result of the above-mentioned step S18 or step S19 and the data traffic acquired in the step S13 (Step S20).

(55) In the step S20, the usage-based charge calculated by the usage-based charge calculating module 32 is calculated based on the price plan acquired in the step S10, and the amount of charge and the data amount are stored in the charge amount table shown in FIG. 5 described later.

(56) Charge Amount Table

(57) With reference to FIG. 5, the charge amount table calculated and stored by the usage-based charge calculating module 32 is described below.

(58) The charge amount table is stored in the storage unit 13 of the charge management server 10. The charge amount table associates the usages, the data amount transferred in the data communication, and the amount of charge. The charge amount table stores the amount of charge and the data amount according to the usage, which are calculated by the usage-based charge calculating module 32 in the step S20. Whenever the data communication terminal 100 executes data communication, the usage-based charge calculating module 32 updates the data amount and the amount of charge for business use or for private use in the charge amount table. The charge amount table may be not updated at each data communication but may additionally store the data amount and the amount of charge with the usage.

(59) The billing module 22 of the charge management server 10 executes the charging process based on the charge amount table (Step S21).

(60) In the step S21, the billing module 22 charges the amount of charges for private use and for business use based on the charge amount table. The amount of charge for business use is charged to the company, and the amount of charge for private use is charged to the user.

(61) The billing module 22 of the charge management server 10 executes the payment process to pay the total amount of charges for private use and for business use to the common carrier (Step S22). Above-mentioned process is the charge management process executed by the charge management server 10 and the data communication terminal 100.

Second Embodiment

System Configuration of Charge Management System 1

(62) The second preferred embodiment of the present invention will be explained below. The explanation of the system configuration of the charge management system 1 is omitted because it is the same as that of the system configuration diagram of FIG. 1.

(63) Functions

(64) The configuration of each device is described below with reference to FIG. 6. Details of the configuration same as that of the first embodiment are omitted.

(65) The charge management server 10 provides with a control unit 11 and a communication unit 12 in the same way as the first embodiment. The control unit 11 reads a predetermined program and cooperates with the communication unit 12 to achieve a billing module 22 and a charging information receiver module 24.

(66) The data communication terminal 100 includes a control unit 110, a communication unit 120 and an input-output unit in the same way as the first embodiment.

(67) The data communication terminal 100 also includes a data storage unit such as a hard disk, semiconductor memory, a recording medium, or a memory card as a storage unit 130 storing data and files. The data communication terminal 100 stores the above-mentioned sorting table and the charge amount table in the storage unit 130.

(68) The control unit 110 also reads a predetermined program and cooperates with the communication unit 120 to achieve a data traffic acquisition module 300, a tag information acquisition module 310, a data communication module 320, a charging information transmitter module 330, and the price plan acquisition module 340. The control unit 110 also reads a predetermined program and cooperates with the storage unit 130 to achieve the sorting table storing module 400, a data communication charge calculating module 410, and a usage-based charge calculating module 420.

(69) Charge Management Process

(70) FIG. 7 is the flowchart of the charge management process executed by the charge management server 10 and the data communication terminal 100. The process executed by the modules of each of the above-mentioned devices will be explained together with this process.

(71) The price plan acquisition module 340 of the data communication terminal 100 acquires the price plan beforehand from the common carrier DB 5 beforehand (Step S30). In the step S30, the price plan acquired by the price plan acquisition module 340 may be a price plan for which each user has contracted with the common carrier or stored in the data communication terminal 100 beforehand. The price plan may be a plan for which the administrator of charge management server 10 contracted with a common carrier beforehand. Moreover, the price plan may not be a price plan of each data communication terminal 100 but a price plan for which the charge management server 10 has contracted in bulk with a common carrier. Moreover, the price plan stored in the charge management server 10 may be acquired. Moreover, it may be another price plan.

(72) The data communication module 320 of the data communication terminal 100 receives the operation to the input-output unit of the data communication terminal 100 and the selection and the execution of an application. The data communication module 320 of the data communication terminal 100 starts the data communication of the executed application (Step S31). The explanation of the application executed by the data communication module 320 is omitted because it is the same way as that of the application executed by the above-mentioned data communication module 220.

(73) The data traffic acquisition module 300 of the data communication terminal 100 acquires the data traffic of the data communication by the application executed by the data communication module 320 (Step S32). In the step S32, the data traffic acquired by the data traffic acquisition module 300 is generated by each application. In the step S32, the data communication terminal 100 determines whether the on-going data communication is LTE or Wi-Fi. If the data communication terminal 100 determines that it is LTE, the data traffic acquisition module 300 acquires the data traffic. If the data communication terminal 100 determines that the on-going data communication is Wi-Fi, the data traffic acquisition module 300 terminates the current process without acquiring the data traffic.

(74) The tag information acquisition module 310 of the data communication terminal 100 acquires tag information of the data communication executed by the data communication module 320 (Step S33). In the step S33, the explanation of the tag information acquired by the tag information acquisition module 310 is omitted because it is the same as that of the above-mentioned tag information.

(75) The data communication charge calculating module 410 of the data communication terminal 100 calculates data communication charge for the data traffic based on the acquired data traffic (Step S34).

(76) The sorting table storing module 400 of the data communication terminal 100 looks up the sorting table (Step S35) and determines whether data communication is private use or business use based on the acquired tag information (Step S36 and Step S37). In this embodiment, the sorting table is stored in the storage unit 130 of the data communication terminal 100. The explanation of each item of the sorting table is omitted because it is the same as that of the first embodiment.

(77) The registration of each item to the sorting table may be entered by the user, or item data entered by the administrator of charge management server 10 may be downloaded and stored in the data communication terminal 100. Moreover, other items may be registered beforehand in the same way as the first embodiment.

(78) The usage-based charge calculating module 420 of the data communication terminal 100 determines whether the usage of the data communication received is for business or not based on the acquired tag information and the sorting table (Step S36).

(79) In the step S36, the usage-based charge calculating module 420 determines whether the usage is for business or not based on the usage associated with the tag information acquired by the tag information acquisition module 310. If determining that the usage is for business (Step S36: YES), the usage-based charge calculating module 420 calculates the usage-based charge and stores the amount of charge and the data amount in the charge amount table described later (Step S38). In the step S36, the explanation of the process executed by the usage-based charge calculating module 420 is omitted because it is the same as that of the process in the step S18 mentioned above.

(80) In the step S36, if the usage is determined not to be for business (Step S36: NO), the usage-based charge calculating module 420 determines whether the usage is for private or not (Step S37).

(81) In the step S37, the usage-based charge calculating module 420 determines whether the usage is for private or not based on the usage associated with the tag information acquired by the tag information acquisition module 310. If determining that the usage is for private (Step S37: YES), the usage-based charge calculating module 420 calculates the usage-based charge and stores the amount of charge and the data amount in the charge amount table described later (Step S38). Moreover, in the step S37, if determining that the usage is not for private (Step S37: NO), the usage-based charge calculating module terminates the current process.

(82) If determining that the usage is not for business in the above-mentioned step S36 and is not for private in the step S37, the usage may be considered to be for either business or private to calculate the data communication charge. Moreover, in this case, the notification may be sent to the administrator of the charge management server 10 to notify the usage is unknown, and a process to add the information on whether the usage is for business or private to the sorting table may be executed.

(83) In the step S37, the process executed by the usage-based charge calculating module 420 is omitted because it is the same as that of the process in the above-mentioned step S19.

(84) The usage-based charge calculating module 420 of the data communication terminal 100 calculates the usage-based charge based on the result of the above-mentioned step S36 or step S37, and the data traffic acquired in the step S32 (Step S38).

(85) In the step S38, the usage-based charge calculated by the usage-based charge calculating module 420 is calculated based on the price plan acquired in the step S30 and the amount of charge, and the data amount is stored in the charge amount table described later. In this embodiment, the charge amount table is stored in the storage unit 130 of the data communication terminal 100. The explanation of each item of the charge amount table is omitted because it is the same as that of the first embodiment.

(86) The charging information transmitter module 330 of the data communication terminal 100 transmits the amount of charge stored in the charge amount table as charging information to the charge management server 10 (Step S39).

(87) The charging information receiver module 24 of the charge management server 10 receives charging information from the charging information transmitter module 330 of the data communication terminal 100 (Step S40).

(88) The billing module 22 of the charge management server 10 executes the charging process based on the received charging information (Step S41). In the step S40, the billing module 22 charges the amount of charge for private use and for business use based on the received charging information. The billing module 22 charges the amount of charge for business use to the company, and charges the amount of charge for private use to the user.

(89) The billing module 22 of the charge management server 10 executes the payment process to pay the total amount of charges for private use and for business use to the common carrier (Step S42). Above-mentioned process is the charge management process executed by the charge management server 10 and the data communication terminal 100 in the second embodiment.

(90) To achieve the means and the function that are described above, a computer (including CPU, an information processor, and various terminals) reads and executes a predetermined program. For example, the program is provided in the form recorded in a computer-readable medium such as a flexible disk, CD (CD-ROM, etc.), and DVD (DVD-ROM, DVD-RAM, etc.). In this case, a computer reads a program from the recording medium, forwards and stores the program to and in an internal or an external storage, and executes it. The program may be previously recorded in, for example, a storage (recording medium) such as a magnetic disk, an optical disk, and a magneto-optical disk and provided from the storage to a computer through a communication line.

(91) The embodiment of the present invention is described above. However, the present invention is not limited to the above-mentioned embodiment. The effect described in the embodiment of the present invention is only the most preferable effect produced from the present invention. The effect of the present invention is not limited to those described in the embodiment of the present invention.

REFERENCE SIGNS LIST

(92) 1 charge management system 5 common carrier DB 10 charge management server 100 data communication terminal