WO2014080584A1 - Billing system, billing device, device control method, billing method, and billing program - Google Patents

Abstract

A rule transmission means (91) transmits a billing rule to a device (70). A ticket transmission means (81) transmits a ticket to the device (70). On the basis of the billing rule received from the rule management server (90) a ticket subtraction means (71) of the device (70) subtracts the user's tickets in accordance with the use of the device by the user. When the tickets of the user using the device run out, a ticket request means (72) requests an additional amount of tickets for the user from a ticket management server (80). When an additional amount of tickets cannot be obtained from the ticket management server (80) a control means (73) restricts the use of the device by the user.

Description

Billing system, billing apparatus, device control method, billing method, and billing program

The present invention relates to a billing system, a billing apparatus, a device control method, a billing method, and a billing program that perform billing according to the use of a device or service by a user.

In recent years, a type of service has emerged that is not shared or owned by other users, but is used by individuals. For example, there are cases where terminal resources and computer resources are shared among a plurality of arbitrary students, such as a computer room in a university. Especially in recent years, services such as cloud computing have been developed. For this reason, devices and resources are no longer occupied by individuals, and a rental method of borrowing and using only the necessary amount has been adopted as one of service forms.

Also, for example, in car sharing services, multiple families residing in condominiums, etc. share a single car and try to make the best use of a small number of cars by sharing time to use the car. Has been done. Further, for example, a computer resource leasing service can also be said to be a form of a service that shares and uses a device with other users.

料 金 A problem in executing such a service is the charge calculation method and payment method. Due to the recent miniaturization of computer devices and the development of the field of Machine-To-Machine (M2M), various communication environments have been established. For example, it is possible to mount a high-performance computer in a device such as a passenger car and communicate with the server side in real time.

With the establishment of such a communication environment, for example, it is possible to construct various billing systems that are more advanced than the simple prepaid billing process used so far.

Patent Document 1 describes a method for managing points for members to receive services. In the method described in Patent Document 1, when a deposit from a member is confirmed, an operation of adding service points according to the deposited amount is performed. Also, service points can be withdrawn by receiving a notification from the service support system at the time of service reservation, so that points corresponding to the service to be provided are automatically withdrawn.

Patent Document 2 describes a system that lends software on a time basis according to a prepaid amount purchased by a user. The system described in Patent Document 2 uses the time count program to total the usage time of each software, and subtracts the total usage time from the purchase time.

Note that Patent Document 3 describes an exchange that charges a fee according to the amount of information transmitted and received by a subscriber. The exchange described in Patent Document 3 provides a charge notification message with a data communication protocol in a PVC (PermanentmanVirtual Circuit) link.

JP 2007-011389 A JP 2004-152283 A JP 09-238133 A

By the way, in a general billing method, a usage fee may be calculated based on a usage amount for a predetermined period. For example, the case where a computer resource is shared in a university is taken as an example. In this case, a detailed log is collected about which user used when and how much, and the log is processed based on the charging rule by batch processing about once a month. In this way, the contribution (charge amount) for each user is calculated.

However, when such a method is used, even if a user uses resources exceeding the user's ability to pay, there is a problem that it will be detected once a month. There is. In this way, if the usage fee of each user cannot be grasped in real time, a fee collection failure may occur.

In addition, when a service is performed using computer resources or vehicles shared by a plurality of users, generally, a log is collected about the amount of each user occupying these resources, and based on the log and charging rules Pay-per-use. For example, when a user uses a workstation, a usage fee is charged for the usage time. For example, when a user performs car sharing and uses a vehicle, a metered charge is made for the amount of gasoline used by the use.

FIG. 16 is an explanatory diagram showing a general billing system. When the user 210 and the user 211 use the computer resource 206 and the vehicle 207, the computer resource 206 and the vehicle 207 transmit logs to the accounting calculation processing server 201. The billing calculation processing server 201 determines the billing amount 203 based on the received log according to the billing rule for each user.

Therefore, in the general system shown in FIG. 16, the charge amount for the user is not determined until the log is transferred to the charge calculation processing server 201 and the charge amount calculation process is completed. Therefore, penalty processing (for example, service to the user) performed when the billing amount exceeds the amount that can be used by the user (hereinafter, it may be described that the billing has expired or the ticket balance has been exhausted). There was a problem that the provision restrictions, etc.) were not performed in real time.

For this problem, for example, in the field of telephone exchanges, the method described in Patent Document 1 may be used. Specifically, each device immediately transfers user billing information to the billing calculation processing server using a special packet. In this case, the billing process can be given immediacy.

However, in the case of the method described in Patent Document 1, not all the information included in the log is transferred to the accounting management processing server. In the method described in Patent Document 1, the accounting information is compressed by compressing the log based on a certain rule agreed between the accounting management processing server and the apparatus (or by making use of the log characteristics peculiar to the field). Transfer only a part of. Since such a process is performed, the field to which the method described in Patent Document 1 is applied is limited.

On the other hand, there is a form in which a user uses a device using a prepaid type ticket, like a prepaid card type public telephone. In this case, the device provides a service as a price for the ticket. In the case of a public telephone, the public telephone performs subtraction processing of the usable amount indicated by the prepaid card type ticket. Note that when the usable amount becomes 0, the ticket may be expired.

In addition, when the balance of the prepaid card runs out (that is, when a ticket expires state), the public telephone can immediately hang up the call as a penalty for billing out. That is, in such a form, penalty processing can be performed immediately.

However, in the case of a form using a prepaid ticket, there is a problem that the charging method and the content of penalty processing cannot be differentiated for each user because the user cannot be specified.

As a medium for solving such a problem, there is a prepaid ticket in which user information and service contents for the user are recorded. For example, on an IC card issued by a railway company, information on the owner (user) and the rights of the user (for example, information on discount services) are recorded in advance.

In such a method of using an IC card, when the IC card is used for service settlement, the service providing apparatus reads discount service information from the IC card and executes a discount service to the user.

However, in the case of using the IC card, there is a problem that after the service content such as discount service is written on the card, the service content cannot be easily changed later on the service provider side. Therefore, it is preferable that the service content applied to each user can be reflected in each process at an appropriate timing.

In addition, in the case of the method described in Patent Document 1, points are withdrawn collectively at the time of reservation for the service depending on the service to be used. That is, the method described in Patent Document 1 is effective when the points to be withdrawn at the start of service use are clear. However, in the pay-per-use billing that is charged according to the usage amount, it is difficult to apply the method described in Patent Document 1 because the usage amount is unknown at the start of service use.

In addition, in the system described in Patent Document 2, the usage fee of software is first purchased as usage time, and a prepaid file including the purchase time is downloaded to each device. In the system described in Patent Document 2, the usage time is only consumed after the prepaid file is downloaded, so it is difficult to deal with the usage method of the usage time for each user. .

Therefore, the present invention reflects a charging rule applied to each user at an appropriate timing and can perform a charging process according to the use of the user, a charging apparatus, a device control method, a charging method, and a charging The purpose is to provide a program.

A charging system according to the present invention includes a device used by a user, a ticket management server that manages a ticket representing the amount that the device can be used for each user, and a charging rule that defines a ticket subtraction method according to the use of the device. A rule management server that manages a user for each user, the rule management server includes a rule transmission unit that transmits a charging rule to the device, and the ticket management server includes a ticket transmission unit that transmits a ticket to the device. Based on the charging rule received from the rule management server, ticket subtraction means for subtracting the user's ticket according to the user's use of the device, and ticket management when the user's ticket using the device is exhausted Requests for additional tickets for the user from the server And Tsu DOO request means, if it can not obtain the additional portion of the ticket from the ticket management server, characterized in that it comprises a control means for limiting the use of its own device by the user.

A billing apparatus according to the present invention is a billing apparatus that includes a device used by a user and performs a billing process according to the use of the device, and manages a ticket representing the amount of usable device for each user. Receiving a ticket from the server, and managing a charging rule for each user that regulates a charging rule that defines the ticket subtraction method according to the device usage. A ticket subtracting means for subtracting the user's ticket in response, a ticket requesting means for requesting the ticket management server for an additional ticket of the user when the user's ticket is lost, and a ticket management server If an additional ticket cannot be obtained from the Characterized in that a control means for limiting the use of the scan.

In the device control method according to the present invention, a ticket management server that manages a ticket representing a usable amount of a device used by a user for each user transmits the ticket to the device, and subtracts the ticket according to the use of the device. A rule management server that manages a charging rule that defines a method for each user transmits the charging rule to the device, and the device responds to the use of the device by the user based on the charging rule received from the rule management server. Subtract the user's ticket, and if the device runs out of tickets for the user using the device, the device requests the ticket management server for the additional ticket for the user, and the device adds the additional ticket from the ticket management server. If the ticket cannot be obtained, the user can use his / her device. Characterized in that it limited.

A billing method according to the present invention is a billing method that includes a device used by a user and performs billing processing in accordance with the use of the device, and manages a ticket representing the amount of usable device for each user. Receives the ticket from the server and receives the charging rule from the rule management server that manages the charging rule for each user that specifies the ticket subtraction method according to the device usage, and uses the device by the user based on the charging rule The user's ticket is subtracted according to the request, and when there is no ticket for the user using the device, the ticket management server requests the ticket for the additional user and obtains the additional ticket from the ticket management server. If not, it is characterized by restricting the use of the user's own device by the user. .

A billing program according to the present invention is a billing program applied to a computer that includes a device used by a user and performs a billing process in accordance with the use of the device, and represents a quantity that can be used for the computer. Receive the ticket from the ticket management server that manages the user for each user, and receive the charging rule from the rule management server that manages the charging rule that defines the ticket subtraction method according to the use of the device for each user. Based on the rules, ticket subtraction processing that subtracts the user's ticket according to the user's use of the device, and when the user's ticket using the own device is exhausted, the ticket management server requests the ticket for the additional user Ticket request processing and ticket management server Failure to obtain the additional portion of the ticket from, characterized in that to execute a control process for limiting the use of its own device by the user.

According to the present invention, it is possible to reflect the charging rule applied to each user at an appropriate timing and perform the charging process according to the user's use.

It is explanatory drawing which shows the outline | summary of the charging system by this invention. It is a sequence diagram which shows the example of the process which a device performs. It is a block diagram which shows the structural example of 1st Embodiment of the charging system by this invention. It is explanatory drawing which shows the example of the screen which inputs user device link information. It is explanatory drawing which shows the example of a charging rule. It is explanatory drawing which shows the example of the accounting rule delivered. It is explanatory drawing which shows the example of the content of a ticket. It is explanatory drawing which shows the example of the screen which registers a ticket. It is explanatory drawing which shows the example of the ticket delivered. It is a sequence diagram which shows the operation example of a charging system. It is a sequence diagram which shows the operation example of a charging system. It is explanatory drawing which shows the modification of the charging system by this invention. It is explanatory drawing which shows the other modification of the charging system by this invention. It is a block diagram which shows the example of the minimum structure of the charging system by this invention. It is a block diagram which shows the example of the minimum structure of the charging device by this invention. It is explanatory drawing which shows a general charging system.

Hereinafter, embodiments of the present invention will be described with reference to the drawings. In the following description, a device means a device used by a user or a device that realizes a service provided to the user. Computer resources and vehicles are examples of devices. In addition, using a device includes not only using the device itself but also using a service provided by the device via the device.

First, an outline of a charging system according to the present invention will be described.
It is assumed that when a user uses a certain device, billing processing using a log indicating the use of the device is performed. However, the charge amount can be calculated from the log using the charge rule. One feature of the present invention is that, based on the association between a user and a device, the charging rule of the user who occupies the device is transferred to the device, and the calculation processing of the charging amount is performed on the device side. is there. Since the charging process is performed by the device in this way, the entire apparatus including the device can also be called a charging apparatus.

When the association between the user and the device is changed, a new charging rule indicating the relationship between the user and the device is distributed again to the device, and the charging rule on the device side is overwritten.

In the present invention, the calculated billing amount is realized by a process of consuming a ticket. Further, the process of consuming this ticket is performed on the device side. Therefore, it is possible to immediately impose a penalty for charging out to the user.

A certain user saves his / her ticket in advance by a certain amount on the ticket management server before receiving the service. Thereafter, when the user starts to occupy a certain device, a part of the ticket of the user or a part of the stocked ticket is transferred to the device.

When a device provides a service to a user, it generates a log. A charge amount is calculated based on this log and the charge rule distributed by the method described above. The device subtracts the ticket held by the user by the calculated charge amount.

When all the tickets held by the user are consumed at a certain stage, the device requests an additional ticket from the ticket management server. Here, when communication with the ticket management server is not possible, or when the user's stocked ticket does not exist in the ticket management server, the ticket request to the ticket management server fails.

In this case, the device controls the execution of the service provided to the user. With this control, it is possible to immediately impose a penalty on the user.

As described above, the billing system according to the present invention can perform the penalty processing to the user in real time by performing the billing process inside the device without transferring the log from the device to the billing management server. And

Also, immediately before the user uses the device, the accounting rule is distributed to the device. Therefore, the device can perform a service for the user and a penalty process for charging out based on the latest rule.

FIG. 1 is an explanatory diagram showing an outline of a charging system according to the present invention. The charging system illustrated in FIG. 1 includes a charging rule management server 301, a ticket management server 302, and a device 309. In the example illustrated in FIG. 1, the charging rule management server 301 and the ticket management server 302 are connected to the device 309 via the communication network 307. The communication network 307 may be the Internet, an intranet, or a mobile phone network as long as information can be transferred to each device.

The user 311 is provided with a user service 310 from the device 309. For example, when the device 309 is a computer, a service is provided based on the right to use computer resources. For example, when the device 309 is an automobile, a service is provided based on the driving right of the automobile.

As a preparation stage for using the device 309, the user 311 registers information (hereinafter referred to as user / device link information) that associates the user 311 with the device 309 in the charging rule management server 301 (an arrow 303 shown in FIG. 1). ).

In addition, the user 311 registers his or her own ticket in the ticket management server 302 as a preparation stage for using the device 309 (arrow 304 shown in FIG. 1). Here, the ticket represents the amount that the user can use the device 309, and is information indicating the right to use the device 309 and how much the device 309 can be used based on the right. In other words, it can be said that the ticket is a numerical value representing the user's right to use the device as a quantity. For example, it can be specified that one ticket can be received for each ticket.

The user pays for the ticket when registering the ticket. For example, the user may pay for the ticket by making a payment with a credit card, or may pay the price by another method. The execution order of the user / device link information registration and the ticket registration is arbitrary.

As shown by an arrow 305 in FIG. 1, the charging rule management server 301 transmits a charging rule for the user 311 using the device 309 to the device 309. The charging rule transmission timing may be any timing before or immediately before starting the service for the user 311 or at the same time as starting the service.

In addition, as indicated by an arrow 306 in FIG. 1, the ticket management server 302 transmits a part or all of the ticket held by the user 311 to the device 309.

The device 309 registers the received charging rule and ticket therein (arrow 308 shown in FIG. 1). When the charging rule and the ticket registration are completed, the device 309 starts providing the user service 310 to the user 311. Hereinafter, the stage in which the service is provided is referred to as a service execution stage.

In the service execution stage, every time the resource of the device 309 is consumed, the device 309 executes various processes. Here, resource consumption will be described. For example, when the device 309 is a public telephone, the resource is a call time, and the resource unit is represented by time. For example, when the device 309 is an automobile, the resource is fuel, and the unit of the resource is expressed in liters.

FIG. 2 is a sequence diagram illustrating an example of processing executed by the device 309. First, the device 309 provides a service to the user 311 (step S1301). By providing the service, the resources of the device 309 are consumed.

The device 309 determines whether or not a certain amount of resources has been consumed (step S1302). If it is determined that a certain amount of resources has not been consumed (NO in step S1302), the device 309 performs processing subsequent to step S1301. On the other hand, if it is determined that a certain amount of resources has been consumed (YES in step S1302), the device 309 subtracts the ticket based on the received charging rule (step S1303).

The device 309 determines whether or not the ticket balance has been exhausted (step S1304). If the ticket balance has not been exhausted (NO in step S1304), the device 309 performs the processing from step S1301 onward. On the other hand, if there is no more ticket balance (YES in step S1304), the device 309 attempts to acquire an additional ticket from the ticket management server 302 (step S1305).

If an additional ticket can be acquired from the ticket management server 302 (YES in step S1306), the device 309 performs processing in step S1303 and subsequent steps. On the other hand, when an additional ticket cannot be acquired from the ticket management server 302 (NO in step S1306), the device 309 executes processing (penalty processing) at the time of rule violation such as service stop processing for the user 311. (Step S1307).

The ticket acquisition method and the ticket subtraction method are arbitrary. For example, the ticket management server 302 transmits to the device 309 a numerical value encrypted in a format that cannot be decrypted by the user 311. The device 309 decodes and records the numerical value at a secure location inside the device 309. Thereafter, the device 309 subtracts the ticket in a secure manner protected from the user 311.

Next, an embodiment of a charging system according to the present invention will be described. FIG. 3 is a block diagram showing an embodiment of a charging system according to the present invention. The charging system of the present embodiment includes a charging rule management server 101, a ticket management server 119, and a device 108. 3 illustrates one device 108, the number of devices 108 is not limited to one and may be two or more.

The charging rule management server 101 includes a user relevance management unit 103, a charging rule distribution unit 105, and a charging rule storage unit 102.

The user association management unit 103 manages information (that is, user / device link information) that associates the device 108 with the user 126. For example, the user 126 inputs user / device link information to the user association management unit 103 through the route 124. Here, the path 124 indicates an arbitrary means for inputting user / device link information to the user association management unit 103.

FIG. 4 is an explanatory diagram showing an example of a screen for inputting user / device link information. The input via the path 124 is realized using, for example, a screen 701 illustrated in FIG. The screen 701 includes an input part 702 for inputting a user name, an input part 703 for inputting a terminal number, and a link execution button 704 for instructing completion of input.

For example, the Web screen illustrated in FIG. 4 is presented to the user 126, and the user name and the terminal number are input to the input part 702 and the input part 703 on the Web screen. When the link execution button 704 is pressed after the input, user / device link information is input to the user association management unit 103. At this time, the user association management unit 103 may perform an authentication process for the user 126 and a process for confirming whether the user 126 is surely using the device 108.

The charging rule storage unit 102 stores a charging rule for each user. The charging rule storage unit 102 provides the charging rule to the charging rule distribution unit 105 via the path 106. In the charging rule, a ticket subtraction method corresponding to the use of the device 108 is defined. In addition, the charging rule may include a penalty process when the balance of the ticket is exhausted. Further, since charging is performed by performing ticket subtraction processing, the charging rule can also be referred to as a subtraction rule. The charging rule is given in advance and stored in the charging rule storage unit 102.

FIG. 5 is an explanatory diagram showing an example of a charging rule. FIG. 5 illustrates a charging rule in which a terminal (that is, a device) used for each user, a rule indicating a subtraction method, and a process when a rule is violated are associated with each other. The charging rule storage unit 102 may store charging rules in the format of the table 901 illustrated in FIG. The charging rule storage unit 102 is realized by, for example, a database management system.

The charging rule distribution unit 105 distributes a charging rule corresponding to the user 126 using the device 108 via the path 107 to the device 108 (specifically, a charging rule execution unit 109 described later). The path 107 is a communication network such as the Internet, for example.

FIG. 6 is an explanatory diagram showing an example of a billing rule to be distributed. For example, the charging rule distribution unit 105 distributes the charging data 1001 to the device identified by PC # 1 in the format illustrated in FIG. 6A and transfers the charging data 1001 to the device identified by PC # 2 as shown in FIG. The billing data 1002 may be distributed in the format exemplified in FIG. That is, the charging rule distributed to the device 108 is a part of data stored in the charging rule storage unit 102.

The charging rule distribution unit 105 transmits the charging rule to the device 108 before the device 108 is used. The timing at which the charging rule is distributed is arbitrary as long as the device 108 is not used.

The ticket management server 119 includes a ticket distribution unit 120.

The ticket distribution unit 120 manages the balance of tickets for each user. Specifically, the ticket distribution unit 120 stores the amount indicated by the ticket for each user. FIG. 7 is an explanatory diagram showing an example of the contents of a ticket. The ticket distribution unit 120 may store the ticket in a table format illustrated in FIG. FIG. 7 shows that the ticket distribution unit 120 stores a table 1101 that represents the amount indicated by the ticket as the number of held tickets.

For example, the user 126 makes an application for charging his / her ticket through the route 122 to the ticket distribution unit 120. FIG. 8 is an explanatory diagram showing an example of a screen for registering a ticket. The screen 801 has an input part 802 for inputting a user name, an input part 803 for inputting a card number for identifying a card used for charging a ticket, an input part 804 for inputting a charge amount of a ticket, and an instruction for completion of input. A ticket charge execution button 805.

For example, the Web screen illustrated in FIG. 8 is presented to the user 126, and the user name, card number, and charge amount are input to the input portion 802, the input portion 803, and the input portion 804 on the Web screen. When the ticket charge execution button 805 is pressed after the input, the application is completed. With this application process, payment for the service is made.

In addition, the ticket distribution unit 120 distributes a part of the ticket corresponding to the user 126 using the device 108 to the device 108 (specifically, a ticket holding unit 113 described later). In this case, the delivered tickets are subtracted from the tickets stored in the ticket delivery unit 120.

FIG. 9 is an explanatory diagram showing an example of a ticket to be distributed. For example, the ticket distribution unit 120 distributes the ticket 1201 to the device identified by PC # 1 in the format illustrated in FIG. 9A, and transmits the ticket 1201 to the device identified by PC # 2 as illustrated in FIG. The ticket 1202 may be distributed in the format illustrated.

The device 108 includes a charging rule execution unit 109, a ticket holding unit 113, a control execution unit 115, a user service execution unit 117, and a log generation unit 111.

The charging rule execution unit 109 subtracts the ticket of the user 126 according to the use of the device 108 by the user 126 based on the charging rule received from the charging rule management server 101.

Specifically, the charging rule execution unit 109 calculates a charging amount for a log generated by the log generation unit 111 described later using the charging rules of the user 126 using the device 108. Then, the charging rule execution unit 109 requests a ticket subtraction process based on the calculated charging amount via the path 112 to the ticket holding unit 113 described later. The target log is transmitted from the log generation unit 111 to the charging rule execution unit 109 via the path 110. The charging rule is distributed from the charging rule distribution unit 105 through the path 107.

The ticket holding unit 113 holds the ticket distributed from the ticket management server 119. The ticket holding unit 113 receives a ticket subtraction request from the charging rule execution unit 109 and subtracts the ticket of the user 126 held by itself based on the calculated charging amount.

When the ticket of the user 126 that uses the device 108 has run out, the ticket holding unit 113 adds the user 126 to the ticket management server 119 (specifically, the ticket distribution unit 120) via the route 121. Request a ticket for.

If the additional ticket cannot be acquired from the ticket management server 119, the ticket holding unit 113 requests the control execution unit 115 to restrict the use of the device 108 by the user 126 via the path 114 (that is, a penalty). Process control request). The case where the additional ticket cannot be acquired includes a case where a request for the additional ticket is not accepted, or a case where the request does not reach the ticket management server 119 and communication times out.

The control execution unit 115 receives a penalty processing control request from the ticket holding unit 113 via the route 114 and restricts the use of the device 108 by the user 126. That is, when an additional ticket cannot be acquired from the ticket management server 119, the control execution unit 115 performs a penalty process for restricting the use of the device 108 by the user 126.

Penalty processing performed for the user 126 is determined in advance. For example, if the penalty rule is included in the charging rule when the ticket balance runs out, the charging rule execution unit 109 holds the contents of the penalty processing. Therefore, the control execution unit 115 may read the contents of penalty processing from the charging rule execution unit 109.

Then, the control execution unit 115 controls the execution of the user service performed by the user service execution unit 117 via the path 116.

The user service execution unit 117 provides a user service 123 to the user 126. For example, when the device 108 is a computer terminal, the service 123 for the user represents provision of calculation capability. Further, for example, when the device 108 is a vehicle, the service 123 for the user represents provision of driving ability. Therefore, the user service 123 provided by the user service execution unit 117 has various modes, and the contents depend on the device 108.

The user service execution unit 117 consumes an arbitrary resource held by the device 108 when executing the user service 123. For example, when the device 108 is a computer terminal, resource consumption includes CPU usage time, power consumption, consumption of input devices provided in the terminal, cost amortization cost for usage time, and the like. For example, when the device 108 is a vehicle, consumption of gasoline and oil, consumption of a storage battery according to traveling, and the like correspond to resource consumption.

In other words, it can be said that the user service execution unit 117 has a function of providing a service to the user 126 by consuming resources held by the device 108. The service execution unit 117 for users notifies the log generation unit 111 of information on consumed resources (hereinafter also referred to as resource consumption information) via the path 118.

The log generation unit 111 receives information on the resource consumed via the route 118 from the service execution unit 117 for the user, and stores the information on the consumed resource as a trail in the form of a log. The log generation unit 111 stores the generated log in the log generation unit 111. In addition, the log generation unit 111 transmits a log to the charging rule execution unit 109 via the path 110 at an arbitrary timing determined by the charging rule execution unit 109. The billing amount is calculated using this log.

The charging rule execution unit 109, the ticket holding unit 113, the control execution unit 115, the user service execution unit 117, and the log generation unit 111 are realized by a CPU of a computer that operates according to a program (charging program). For example, the program is stored in a storage unit (not shown) of the device 108, and the CPU reads the program, and according to the program, the charging rule execution unit 109, the ticket holding unit 113, the control execution unit 115, and the service execution for the user The unit 117 and the log generation unit 111 may operate.

Further, the charging rule execution unit 109, the ticket holding unit 113, the control execution unit 115, the user service execution unit 117, and the log generation unit 111 may each be realized by dedicated hardware. Further, in the present embodiment, the charging rule management server 101 and the ticket management server 119 are shown as examples realized by different apparatuses, but the functions of the charging rule management server 101 and the ticket management server 119 are provided. May be realized by one server.

Next, the operation of the billing system of this embodiment will be described. 10 and 11 are sequence diagrams showing an operation example of the charging system of the present embodiment. FIG. 10 illustrates an operation in a preparation stage using a device, and FIG. 11 illustrates an operation in a stage in which a service by a device is executed.

First, a process until a charging rule is registered in the device 108 will be described.
First, the user 126 creates information (that is, user / device link information) in which the device 108 to be used and the user 126 are associated with each other, and registers the information in the user association management unit 103 (step S401 in FIG. 10). . The user association management unit 103 in which the user / device link information is registered requests the charging rule distribution unit 105 to distribute the charging rule (step S402).

The charging rule distribution unit 105 reads the charging rule from the charging rule storage unit 102 into itself in preparation for the process of transferring the charging rule to the device 108 (step S403). However, if the charging rule stored in the charging rule storage unit 102 is updated, the charging rule distribution unit 105 may immediately replace the read charging rule with the latest charging rule.

The charging rule distribution unit 105 distributes the charging rule to the charging rule execution unit 109 of the device 108 at a certain opportunity (step S404). The certain opportunity may be, for example, the timing when the device 126 is associated with the user 126 by the user 126, or may be immediately before the device 108 executes the service for the user.

Next, processing until the user's ticket is registered in the device 108 will be described.
The user 126 applies a ticket to the ticket distribution unit 120 at an arbitrary timing and registers the ticket (step S405). After the ticket is registered, the ticket distribution unit 120 distributes the ticket to the ticket holding unit 113 (step S406).

Next, processing at a stage where the service is executed will be described.
The service execution unit 117 for the user of the device 108 provides a service to the user 126 using the resources of the device 108 (step S501 in FIG. 11). The user service execution unit 117 sequentially transmits the resource consumption information to the log generation unit 111 during the execution of the service (step S502).

The log generation unit 111 generates a usage log of the device 108 based on the received resource consumption information, and transmits the generated log to the charging rule execution unit 109 at a certain timing (step S503). Note that the log transmission timing differs depending on the device type, the user service type, and the contents of the charging rule.

Further, it is assumed that the charging rule stipulates that charging calculation is performed based on a log describing the occupation time of the device 108. In this case, the log transmitted from the log generation unit 111 needs to include the time at at least two times and the resource balance at each time.

The charging rule execution unit 109 calculates a charging amount based on the log received from the log generation unit 111 (step S504). The method for calculating the billing amount is arbitrary. For example, a function that outputs an amount of a ticket to be subtracted (that is, a billing amount) using an argument as a log is prepared in advance, and the billing rule execution unit 109 may calculate the billing amount based on this function. .

When the amount of the ticket to be subtracted is determined by the processing in step S504, the charging rule execution unit 109 immediately notifies the ticket holding unit 113 that the amount is to be subtracted (step 505). Upon receiving the notification, the ticket holding unit 113 subtracts the ticket of the corresponding user 126 from the held ticket pool (step S506).

When the balance of the ticket pool of the user 126 is exhausted during the subtraction process, the ticket holding unit 113 requests the ticket distribution unit 120 for the ticket of the user 126 (steps S507 and S508). Then, the ticket holding unit 113 checks whether or not an additional ticket has been acquired (step S509).

If an additional ticket can be acquired (Y in step S509), the ticket holding unit 113 requests the control execution unit 115 to execute the service in order to continue the service (step S511). The control execution unit 115 instructs the service execution unit 117 for the user to continue execution of the service (steps S515 and S516).

On the other hand, if an additional ticket cannot be acquired (N in step S509), the ticket holding unit 113 issues a control request to the control execution unit 115 to execute a penalty process for the user 126 (step S512). The control execution unit 115 performs control for performing a penalty process on the service execution unit 117 for the user based on the process when the rule defined in the charging rule is violated (step S513).

In response to the control of the control execution unit 115, the service execution unit 117 for the user executes a penalty process for the service used by the user 126 (step S514). For example, when the device 108 is a computer terminal, the service execution unit 117 for the user may display that the user's usage screen has expired as a penalty process. For example, when the device 108 is a public telephone, the service execution unit 117 for a user may perform a process of disconnecting a call as a penalty process.

As described above, according to the present embodiment, the charging rule management server 101 transmits a charging rule to the device 108, and the ticket management server 119 transmits a ticket to the device 108. On the other hand, the ticket holding unit 113 of the device 108 subtracts the ticket of the user 126 according to the use of the user's device by the user 126 based on the received billing rule, and the ticket of the user 126 that uses the user's device disappears. In addition, the ticket management server 119 is requested for a ticket for the additional user 126. When the additional ticket cannot be acquired from the ticket management server 119, the control execution unit 115 restricts the use of the own device by the user 126.

With the configuration as described above, it is possible to reflect the charging rule applied to each user at an appropriate timing and perform the charging process according to the user's use.

Specifically, according to the present embodiment, real-time accounting processing can be realized. The reason is that the charging rule is arranged on the device side (that is, the charging rule distribution unit 105 transmits the charging rule to the device 108), thereby eliminating the process of transferring the log to the server that performs the charging management. .

Further, according to the present embodiment, even when a service for a user is performed using the same device, a different charging system can be constructed for each user, or a penalty can be imposed. This is because the accounting rule management server 101 manages the correspondence between devices and users using accounting rules that define different accounting systems and penalty processes for each user.

In addition, according to the present embodiment, it is possible to execute different charging processes for each user on the device side, always using the latest charging rule. The reason is that the charging rule distribution unit 105 transmits the charging rule to the device after associating the user and the device.

Further, according to the present embodiment, even when communication between the device and the charging rule management server and the ticket management server is partially disconnected, the service can be continued. This is because the right to use the service (usable amount) is expressed in the form of a ticket, and the ticket distribution unit 120 partially distributes the ticket to the device side. As a result, the billing process, service execution, and penalty process are constructed in a closed system in the device.

Next, a modification of the billing system according to the present invention will be described. FIG. 12 is an explanatory diagram showing a modification of the charging system according to the present invention. In this modification, a case where a plurality of users use one device will be described. That is, the device is used by a plurality of users, and the charging rule management server transmits a charging rule for each user who uses the device.

12 includes a charging rule management server 601, a ticket management server 602, a computer device 610, and a computer device 611. The charging rule management server 601 and the ticket management server 602 are realized by a computer that operates under program control.

In the example shown in FIG. 12, the charging rule management server 601 and the ticket management server 602 are connected to the computer device 610 and the computer device 611 via the communication network 605. The communication network 605 may be the Internet, an intranet, or a mobile phone network as long as information can be transferred to each device.

In this modification, it is assumed that the user 617 and the user 618 use the computer device 610 and the user 619 uses the computer device 611. That is, the computer device 610 provides the use of a computer as a service to two users 617 and 618.

As shown in the present modification, in the charging system according to the present invention, it is not necessary that the user and the device correspond one-to-one, and a plurality of users may occupy one device at the same time. At least one of the user 617 and the user 618 registers the user 617 or / and information (user / device link information) associating the user 618 and the computer device 610 with the charging rule management server 601 as a preparation stage for using the computer device 610. (Arrow 603 shown in FIG. 12).

For example, the accounting rule management server 601 displays the screen 701 illustrated in FIG. 4 on the computer device 610 or the computer device 611. Then, the user 617 or the user 618 may notify the charging rule management server 601 of information for associating the user with the device (user / device link information) by inputting various information on the displayed screen. As a result of the notification, the charging rule management server 601 may store the charging rules in the format of the table 901 illustrated in FIG. 5, for example.

Each user registers a ticket in the ticket management server 602. For example, the ticket management server 602 displays the screen 801 illustrated in FIG. 8 on the computer device 610 or the computer device 611. And each user may register a ticket into the ticket management server 602 by inputting various information on the displayed screen. As a result of registration, the ticket management server 602 may store the ticket in the form of a table 1101 illustrated in FIG. 7, for example.

In this modification, when each user completes registration of the user / device link information in the charging rule management server 601, as shown by arrows 606, 607, 608 and 609 in FIG. 601 distributes charging rules to the computer devices 610 and 611, and the ticket management server 602 distributes tickets to the computer devices 610 and 611.

For example, the accounting rule management server 601 distributes the information illustrated in FIG. 6 to the computer device 610 and the computer device 611. As shown in FIG. 12, when there are a plurality of users occupying a device (computer device 610), the charging rules (for example, the charging rules shown in FIG. 6A) of the plurality of users occupying the device are simultaneously set. be delivered. Note that the accounting rule shown in FIG. 6B is distributed to the computer device 611 as indicated by an arrow 607 in FIG.

For example, the ticket management server 602 distributes the information illustrated in FIG. 9 to the computer device 610 and the computer device 611. For example, as shown by an arrow 608 in FIG. 12, the ticket management server 602 distributes the ticket 1201 to the computer apparatus 610 in the format illustrated in FIG. 9A.

For example, it is assumed that the ticket management server 602 stores the ticket illustrated in FIG. 7 and distributes the ticket illustrated in FIG. In this case, the total ticket of the user A stored in the ticket management server 602 is 200000, but it shows that 10,000 tickets are distributed. Similarly, although the total number of tickets for user B is 100,000, it shows that 10,000 tickets are distributed.

7 and 9, the total amount of tickets held by each user is stored in the ticket management server 602, and the ticket management server 602 distributes a part or all of the tickets to the device. Similarly, the ticket management server 602 distributes the ticket 1202 to the computer device 611 in the format illustrated in FIG. 9B as indicated by an arrow 609 in FIG.

When the above preparation is completed, the computer apparatus 610 starts providing the service 614 and the service 615 to the user 617 and the user 618, and the computer apparatus 611 starts providing the service 616 to the user 619.

While the computer device 610 and the computer device 611 provide services, the computer device 610 and the computer device 611 regularly generate usage logs. The usage log includes, for example, information such as the CPU usage for each time, the name of the application being used, and the name of the running process.

The computer device 610 and the computer device 611 regularly calculate the amount of tickets to be consumed based on the usage log using the charging rules of the users who use the service, and subtract the tickets held by each user. (Arrows 612 and 613 shown in FIG. 12). If the computer device 610 and the computer device 611 determine that the user's tickets have run out at a certain stage, the computer device 610 and the computer device 611 request additional tickets from the ticket management server 602.

When an additional ticket cannot be acquired from the ticket management server 602, the computer device 610 and the computer device 611 execute a penalty process for the user. The case where the additional ticket cannot be acquired includes a case where a request for the additional ticket is not accepted or a case where communication with the ticket management server 602 cannot be performed.

The computer apparatus 610 and the computer apparatus 611 may display, for example, a message “please charge a ticket” on the screen as a penalty process, or turn off the power of the computer apparatus.

Next, the effect of this modification will be described. For example, in a general model, logs are concentrated and transferred to a single server, and processing for calculating logs in a batch is performed on the server. On the other hand, in this modification, a charging rule for the user is provided in each device (computer device), and charging processing is performed in the device. Therefore, a penalty process for the user can be immediately performed.

In addition, according to the present modification, it is not necessary to store the charging system of a user who may be used in all computer devices in advance. This is because the accounting rule management server displays a screen for managing the relationship between the user and the device (computer device) on another device. That is, when a user uses a computer device, information indicating the relationship between the user and the computer device can be notified to the charging rule management server using this screen, and the charging rule management server receives the notification of the information. This is because the charging rule can be distributed to each computer device.

Next, another modification of the billing system according to the present invention will be described. FIG. 13 is an explanatory view showing another modification of the accounting system according to the present invention. In the above embodiment, the charging rule and the method for registering the ticket using the device itself used by the user have been described. In this modification, a case will be described in which a user registers a charging rule and a ticket in each server using an apparatus (for example, a mobile terminal) different from the device used by the user.

The charging system illustrated in FIG. 13 includes a charging rule management server 1401, a ticket management server 1402, a car 1409 used by the user 1411, and a mobile terminal 1413 held by the user 1411. The charging rule management server 1401 and the ticket management server 1402 are realized by a computer that operates under program control.

In the example shown in FIG. 13, the charging rule management server 1401 and the ticket management server 1402 communicate with the automobile 1409 via the communication network 1405.

The car 1409 is assumed to be a car used for a car sharing service. That is, the automobile 1409 may be used by an unspecified number of users. Here, it can be said that the automobile 1409 provides the user 1411 with a service of riding the automobile.

The user 1411 registers information (user / device link information) for associating the user with the device (automobile 1409) in the charging rule management server 1401 (arrow 1403 shown in FIG. 13).

For example, the charging rule management server 1401 displays the screen 701 illustrated in FIG. 4 on the mobile terminal 1413. Then, the user 1411 may notify the charging rule management server 1401 of information (user / device link information) that associates the user with the device by inputting various types of information on the displayed screen. For example, the mobile terminal 1413 may display a screen 701 illustrated in FIG. 4 using a browsing function of the mobile terminal 1413.

Also, the user 1411 registers a ticket in the ticket management server 1402. For example, the ticket management server 1402 causes the portable terminal 1413 to display a screen 801 illustrated in FIG. The user 1411 may register a ticket in the ticket management server 1402 by inputting various information on the displayed screen.

In addition, although the case where the user 1411 registers a ticket using the portable terminal 1413 is illustrated in this modification, the user 1411 may register the ticket using a home computer, for example.

In this modification, when the user 1411 completes registration of the user / device link information in the charging rule management server 1401, the charging rule management server 1401 charges the automobile 1409 as indicated by arrows 1406 and 1407 in FIG. The rule is distributed, and the ticket management server 1402 distributes the ticket to the automobile 1409.

Upon completion of the preparation described above, the automobile 1409 starts providing the service 1410 to the user 1411 based on the right to drive the automobile.

While the automobile 1409 provides services, the microcomputer mounted on the automobile 1409 periodically generates a usage log. The usage log includes, for example, information such as vehicle position information, travel distance, remaining fuel amount, engine speed, and coolant temperature for each time.

The automobile 1409 periodically calculates the amount of tickets to be consumed based on the usage log using the charging rules of the users who use the service, and subtracts the tickets held by each user (shown in FIG. 13). Arrow 1408). If the automobile 1409 determines that the user's tickets have run out at a certain stage, the automobile 1409 requests the ticket management server 1402 for additional tickets.

If an additional ticket cannot be acquired from the ticket management server 1402, the car 1409 executes a penalty process for the user. The case where the additional ticket cannot be acquired includes a case where a request for the additional ticket is not accepted or a case where communication with the ticket management server 1402 cannot be performed.

The automobile 1409 may stop functions other than the minimum function for driving the automobile as penalty processing. For example, the car 1409 may disable the cooler, may stop using the on-board car navigation system, and periodically displays a message stating “please charge a ticket”. The sound may be flown into the vehicle.

Next, the effect of this modification will be described. As in the case of the above-described modification, for example, in a general model, logs are concentrated and transferred to one server, and processing for calculating logs in a batch is performed by the server. On the other hand, in this modification, a charging rule for the user is provided in each device (automobile), and charging processing is performed in the device. Therefore, a penalty process for the user can be immediately performed.

In addition, according to the present modification, it is not necessary to store the charging system of a user who may be used in all automobiles in advance. The reason is that the charging rule management server displays a screen for managing the relationship between the user and the device (automobile) on the mobile terminal. In other words, when the user uses the computer device, information indicating the relationship between the user and the car can be notified to the charging rule management server using this screen. Therefore, the charging rule management server receives the notification of the information. This is because the charging rule can be distributed to each car.

Next, an example of the minimum configuration of the charging system according to the present invention will be described. FIG. 14 is a block diagram showing an example of the minimum configuration of the charging system according to the present invention. The charging system according to the present invention includes a device 70 (for example, device 108) used by a user (for example, user 126) and a ticket management server 80 (for example, for managing tickets representing the amount that the device can be used) for each user. A ticket management server 119), and a rule management server 90 (for example, a charging rule management server 101) that manages a charging rule that defines a ticket subtraction method according to use of the device for each user.

The rule management server 90 includes a rule transmission unit 91 (for example, a charging rule distribution unit 105) that transmits a charging rule to the device 70, and the ticket management server 80 includes a ticket transmission unit 81 (for example, a ticket that transmits a ticket to the device 70). Ticket distribution unit 120).

Based on the charging rule received from the rule management server 90, the device 70 subtracts a ticket subtracting means 71 (for example, a ticket holding unit 113) that subtracts the user's ticket according to the use of the user's own device, When there are no more tickets for the user to be used, the ticket requesting means 72 (for example, the ticket holding unit 113) that requests the ticket management server 80 for the additional ticket for the user, and the additional ticket from the ticket management server 80 If it cannot be obtained, it includes control means 73 (for example, control execution unit 115) that restricts the use of the user's own device by the user.

With such a configuration, it is possible to reflect a charging rule applied to each user at an appropriate timing and perform a charging process according to the use of the user.

Further, the rule management server 90 may manage a charging rule including a penalty process when a ticket runs out for each user. Then, the control means 73 of the device 70 may control the use of the own device by the user who has run out of the ticket based on the penalty process.

With such a configuration, it is possible to perform an appropriate penalty process for each user by reflecting the charging rule applied to each user at an appropriate timing.

Further, the device 70 may be used by a plurality of users. In that case, the rule transmission means 91 may transmit a charging rule for each user who uses the device 70.

In addition, the billing system may include a terminal device (for example, a mobile terminal 1413) different from the device 70. The terminal device may register the user's ticket in the ticket management server 80.

In addition, the device 70 includes a service execution unit (for example, a service execution unit 117 for the user) that executes a service provided to the user, and a log generation unit that generates a use log according to the use of the own device based on the execution of the service ( For example, it may include a log generation unit 111) and a charge amount calculation unit (for example, a charge rule execution unit 109) that calculates a charge amount of the user based on the charge rule received from the rule management server 90 and the usage log. Good. And the ticket subtraction means 71 may subtract a user's ticket according to a charge amount.

FIG. 15 is a block diagram showing an example of the minimum configuration of the accounting apparatus according to the present invention. A billing apparatus according to the present invention is a billing apparatus that includes a device (for example, device 108) used by a user and performs billing processing according to the use of the device, and includes a ticket subtracting means 71, a ticket requesting means 72, And a control means 73. The contents of the ticket subtracting means 71, the ticket requesting means 72, and the control means 73 are the same as the contents illustrated in FIG.

Even with the above-described configuration, it is possible to reflect a charging rule applied to each user at an appropriate timing and perform a charging process according to the use of the user.

As mentioned above, although this invention was demonstrated with reference to embodiment and an Example, this invention is not limited to the said embodiment and Example. Various changes that can be understood by those skilled in the art can be made to the configuration and details of the present invention within the scope of the present invention.

This application claims priority based on Japanese Patent Application No. 2012-255034 filed on November 21, 2012, the entire disclosure of which is incorporated herein.

The present invention is preferably applied to a billing system that performs billing according to the use of a device or service by a user. For example, it is also available in the fields of computer leasing, shared use of computers, cloud computing, log processing of distributed servers and devices, shared use of learning terminals in schools, car sharing, rental cars, rental cycles, and Machine To Machine. The invention can be applied.

101, 301, 601, 1401 Charging rule management server 102 Charging rule storage unit 103 User relevance management unit 105 Charging rule distribution unit 108, 309 Device 109 Charging rule execution unit 111 Log generation unit 113 Ticket holding unit 115 Control execution unit 117 User Service execution unit 119, 302, 602, 1402 Ticket management server 120 Ticket distribution unit 123, 310, 614 to 616, 1410 Service 126, 311, 617 to 619, 1411 User 307, 605, 1405 Communication network 610, 611 Computer Device 1409 Car 1413 Mobile terminal

Claims (10)

The device used by the user;
A ticket management server that manages, for each user, a ticket representing the amount that the device can be used;
A rule management server that manages, for each user, a charging rule that defines a method for subtracting the ticket according to the use of the device;
The rule management server
A rule transmitting means for transmitting the charging rule to the device;
The ticket management server
Including ticket sending means for sending the ticket to the device;
The device is
Based on the charging rule received from the rule management server, ticket subtracting means for subtracting the user's ticket according to the use of the user's own device;
Ticket request means for requesting the ticket management server an additional ticket for the user when the ticket of the user using the own device runs out;
And a control unit that restricts use of the user's own device when the additional ticket cannot be acquired from the ticket management server. The rule management server manages billing rules including penalty processing for each user when tickets run out,
The charging system according to claim 1, wherein the device control unit controls the use of the device by the user who has run out of the ticket based on the penalty process. The device is used by multiple users,
The charging system according to claim 1, wherein the rule transmission unit transmits a charging rule for each user who uses the device. It has a terminal device different from the device,
The charging system according to any one of claims 1 to 3, wherein the terminal device registers a user's ticket in the ticket management server. The device
Service execution means for executing a service provided to a user;
Log generation means for generating a usage log according to the use of the device based on the execution of the service;
Charging amount calculation means for calculating a charging amount of the user based on the charging rule received from the rule management server and the usage log,
The charging system according to any one of claims 1 to 4, wherein the ticket subtracting unit subtracts the user's ticket according to the charging amount. A charging device that includes a device used by a user and performs a charging process according to the use of the device,
A rule for receiving a ticket from a ticket management server that manages a ticket representing the amount that can use the device for each user, and managing a charging rule that defines a method for subtracting the ticket according to the use of the device for each user Ticket subtraction means for receiving the charging rule from the management server and subtracting the ticket of the user according to the use of the device by the user based on the charging rule;
Ticket request means for requesting the ticket management server for a ticket for the user when the user's ticket using the device is exhausted;
A charging device comprising: control means for restricting use of the user's own device when the additional ticket cannot be obtained from the ticket management server. A ticket management server that manages, for each user, a ticket that represents the amount of the device that can be used by the user, sends the ticket to the device,
A rule management server that manages, for each user, a charging rule that defines a method for subtracting the ticket according to use of the device, transmits the charging rule to the device,
Based on the charging rule received from the rule management server, the device subtracts the user's ticket according to the user's use of the device,
When the ticket of the user who uses the device is lost, the device requests a ticket for the user to be added to the ticket management server,
When the device fails to obtain an additional ticket from the ticket management server, use of the device by the user is restricted. The rule management server manages billing rules including penalty processing for each user when tickets run out,
The device control method according to claim 7, wherein the device controls use of the device by a user who has run out of tickets based on the penalty process. A billing method including a device used by a user and performing billing processing according to the use of the device,
Receiving the ticket from a ticket management server that manages a ticket representing the amount that the device can be used for each user;
Receiving the charging rule from a rule management server that manages, for each user, a charging rule that defines a method for subtracting the ticket according to the use of the device;
Based on the billing rules, the user's use of the device subtracts the user's ticket,
When the ticket of the user who uses the own device is exhausted, the ticket management server is requested for the ticket for the additional user,
A charging method, wherein, when an additional ticket cannot be acquired from the ticket management server, use of the device by the user is restricted. A billing program applied to a computer that includes a device used by a user and performs billing processing according to the use of the device,
In the computer,
A rule for receiving a ticket from a ticket management server that manages a ticket representing the amount that can use the device for each user, and managing a charging rule that defines a method for subtracting the ticket according to the use of the device for each user A ticket subtraction process for receiving the charging rule from the management server and subtracting the ticket of the user according to the use of the device by the user based on the charging rule;
A ticket request process for requesting the ticket management server for an additional ticket for the user when there is no ticket for the user using the device; and
An accounting program for executing a control process for restricting the use of the user's own device when the additional ticket cannot be obtained from the ticket management server.

Images