JP2001148051A - Automatic vending machine and automatic vending machine management system - Google Patents

Abstract

(57) [Summary] [PROBLEMS] To enable a vending machine which can load a program from the outside to realize charging related to the execution of the program. SOLUTION: Execution right information and driver management information of each target program 141 loaded in a vending machine 10 are stored in a program management table 110.
The execution right information includes information on charging in the prepaid system, and the driver management information includes collected information for charging in accordance with the usage amount of the paid resource. The execution management unit 121 collects charging information related to the execution of the target program 141, and each of the drivers 105 to 108 collects the usage amount of the pay resource, and updates the charging information in the program management table 110. The accounting information in the program management table 110 is transmitted to the center device 20 or the mobile terminal 30 via the communication line I / F 103 or the mobile terminal I / F 104.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

The present invention relates to a vending machine and a vending machine management system.

[0002]

2. Description of the Related Art Conventionally, the functions of a vending machine have been executed by a program fixedly written in a ROM. For this reason, the function realized by the vending machine is fixed.

[0003] However, future vending machines are:
It is not just a function of selling goods, but 1) Improve serviceability 2) Improve customer attraction (campaigns such as discounts and premiums) 3) Expand applications (use as advertising towers and information terminals, etc.) There seems to be.

[0004]

As described above, the conventional vending machine cannot change the program dynamically, and cannot select and execute a program previously written in the ROM. By changing the parameters, some of the above functions 1) to 3) are realized. For this reason, the concept of charging for a program executed in a vending machine has not existed until now.

An object of the present invention is to realize the following charging system which has not been realized in a vending machine. (1) Collection of the usage fee of the program executed by the vending machine (or collection of data necessary for the collection) (2) According to the number of times or the execution time of the program executed by the vending machine (3) Collection of costs associated with execution of the program in the vending machine (or collection of data required for the collection) As an example, for example, a system in which a vending machine management company receives provision of a program from a program provider and pays a fee according to the usage amount of the program can be considered.

As an example of the above (2), for example, a system in which a vending machine management company purchases a program execution right from a program provider and executes the program up to the limit of the execution right can be considered.

[0007] The cost of (3) may be, for example, a discount, a premium, a communication fee, or a fee for using other paid resources. A system that provides a service on a vending machine by borrowing the right to use the vending machine from a management company is conceivable.

[0008]

According to a first aspect of the present invention, there is provided a vending machine which includes a program loading means for loading a program from the outside, and each of the loaded programs is individually related to the program. Storage means for storing charging information, and program management means for controlling execution of each program, collecting charging information related to the execution of each program, and updating charging information in the storage means based on the collection result And

According to the vending machine of the first aspect, it is possible to collect and manage billing information related to execution of each program. The vending machine according to the second aspect of the present invention further collects, in addition to the means provided in the vending machine according to the first aspect, charging information of a pay resource related to each of the programs, and adds the charging information to the collection result. A pay resource charging information collecting means for updating the charging information in the storage means based on the information.

According to the vending machine of the second aspect, it is possible to further collect and manage the billing information of the pay resources used by each program. A vending machine according to a third aspect of the present invention includes, in addition to the means provided in the vending machine according to the first or second aspect, furthermore, accounting information relating to the execution of each program or execution of each program. A program stopping means for stopping the execution of the program related to the billing information when the billing information of the pay resource exceeds the set upper limit.

According to the vending machine of the third aspect of the present invention, the upper limit value is set in the billing information related to the execution of each program or the billing information of the pay resource related to each program, so that the prepaid system can be used. Can be realized.

A vending machine according to a fourth aspect of the present invention further includes, in addition to the means provided in the vending machine according to the first, second, or third aspect, further the billing information stored in the storage means. A notification unit for notifying the external device is provided.

According to the vending machine of the fourth aspect of the present invention, the billing information can be notified to an external center device or the like via a network or the like. It can be used for the accounting process of.

The vending machine management system according to the present invention comprises: a program loading means for loading a program from the outside; a storage means for individually storing charging information relating to each of the loaded programs; A program management unit that controls execution of each program, collects billing information related to the execution of each program, and updates billing information in the storage unit based on the collection result; A vending machine comprising: a pay resource billing information collecting means for collecting billing information of resources and updating the billing information in the storage means based on the collection result; and storing the billing information from the vending machine in the storage means. Receiving means for receiving the billing information relating to each of the programs, based on the billing information received by the receiving means; And a center device comprising a calculation means for calculating an accounting fee of vending machines.

According to the vending machine management system of the present invention, the vending machine collects and manages billing information related to execution of each program and billing information of pay resources related to each program. By receiving the billing information from the vending machine, the center device can collect and process the billing for each vending machine individually, and execute the program for each program, the number of times and the execution time of each program, and each paid resource. For example, detailed billing information can be created.

[0016]

Embodiments of the present invention will be described below with reference to the drawings. FIG. 1 is a diagram showing an overall configuration of a vending machine management system according to an embodiment of the present invention.

The system includes a vending machine 10, a center device 20, a portable terminal 30, a communication line 40, and other devices 50. The vending machine 10 and the center device 20 can communicate with each other via the communication line 40. The other device 50 is a communication partner with which the target program 141 performs communication for an individual purpose.

The communication line 40 includes, for example, a dedicated line, a public line, a wireless line (such as a mobile communication line), a satellite communication line,
Internet etc. The vending machine 10 includes a product tray 101, a coin mech / building bar 102, a communication line interface (communication line I / F) 103, a portable terminal interface (portable terminal I / F) 104, a coin mech /
Building Barrier Driver 105, Product Tray Driver 10
6. Mobile terminal driver 107, communication line driver 10
8. Program management table 110, execution management unit 12
1, a read notification unit 122, a timer 130, and at least one target program (execution program) 141.

The target program 141 is loaded from the center device 20 or the portable terminal 30 to the vending machine 10 and executed on the path indicated by the broken arrow. Each target program 141 is provided with a program ID 142, which is a unique identifier, and execution right information 143.

The program ID 142 is a code for identifying each target program 141. Further, the execution right information 143 includes the following information (1) and (2) relating to charging of the corresponding target program 141.

(1) Information on the Number of Executions and Execution Time of the Target Program 141 This information includes type 1 and type 2. Type 1: Measure and charge according to the performance (measured value) Type 2: Information specifying the maximum number of executions or maximum execution time of the target program 141 (2) Information on use of paid resources ・ Paid communication with outside・ Permission issue information ・ Presentation permission information ・ Discount permission information (an average discount rate can also be specified) ・ Other paid resource use permission information The above additional information is distributed as data together with the target program 141. The data is loaded from the center device 20 to the vending machine 10 together with the target program 141 by a method, a method of embedding the code in the target program 141, or the like. In consideration of security, the main body of the target program 141 and the program ID 142 may be encrypted, or the validity of the target program 141 may be checked.

The product tray 101 is a tray for storing products to be sold by the vending machine 10. The product tray driver 106 includes the target program 141 and the product tray 101
, And manages information on sold products and updates the value of the pay resource information in the program management table 110 based on the information.

The coin mech / building bar 102 includes a coin mech and a building bar. The coin mech and the bill validator discriminate and store coins (in the case of coin mech) and bills (in the case of bill valid) inserted into the vending machine 10 according to an instruction from the target program 141 or the like via the coin mech / bill validator 105. , Return, change, etc.

Coin Mech / Bill Bali Driver 105
Is the target program 141 and Coin Mech / Buil Bali 1
In addition to performing an interface with the pay resource information 02, the value of the paid resource information in the program management table 110 is updated based on the information.

The communication line I / F 103 and the communication line driver 108 are interfaces for connecting the vending machine 10 and the center device 20 via the communication line 40. The communication line driver 108 measures the amount of communication used, and updates the value of the pay resource information in the program management table 110.

The communication line I / F 103 and the communication line driver 108 transmit the information necessary for accounting stored in the program management table 110 to the portable terminal 30 via the communication line I / F 103, It is also used when loading the target program 141 into the vending machine 10 via the communication line 40 from.

The portable terminal I / F 104 and the portable terminal driver 107 are interfaces for connecting the vending machine 10 and the portable terminal 30 by communication. The mobile terminal I / F 104 and the mobile terminal 30 are connected by, for example, a cable or an infrared communication link.

The portable terminal driver 107 and the portable terminal I /
F104 transmits information necessary for charging stored in the program management table 110 to the portable terminal 30 via the portable terminal I / F 104, and automatically transmits the target program 141 from the portable terminal 30 to the portable terminal I / F 104. It is also used when loading the vending machine 30.

The execution management unit 121 controls each target program 1
In addition to controlling the loading and execution of the program 41, information (number of executions, execution time, etc.) necessary for charging related to the execution of the target program 141 is collected, and the program management table 110 is updated. Also, the program management table 1
10, the activation of the target program 141 is controlled.

The program management table 110 stores information on charging for each target program 141, as well as execution right information and an execution permission status flag given to each target program 141. The information stored in the program management table 110 may be encrypted and stored in order to prevent or detect data destruction or falsification.

The read notification unit 122 reads out the billing information from the program management table 110 and transmits it to the portable terminal 30 and the center device 20 via the portable terminal driver 107 and the communication line driver 108.

The timer 130 activates the execution management unit 121 or the read notification unit 122 periodically. Also,
Although not shown in FIG. 1, the center device 20 includes a receiving device that receives, from the vending machine 10, charging information for each of the target programs 141, which will be described later, and each of the target programs 141 based on the received charging information. An apparatus for calculating a billing fee for each is provided.

FIG. 2 is a diagram showing a data structure of the program management table 110. Program management table 1
10 includes information (execution management unit management information) 111 managed by the execution management unit 121 and drivers 105 to 105.
Information (driver management information) 112 managed by the storage unit 108 is stored.

The execution management section management information 111 includes items of “program ID”, “various program execution right information”, “program execution permission state flag”, “total execution time”, and “total execution count”. Also, driver management information 1
Reference numeral 12 includes n items from “paid resource 1 information” to “paid resource n information” managed by the drivers 105 to 108.

Among these items, the “program ID” and the “program various execution right information” are the target program 14.
1 is the fixed information stored at the time of registration, but the other items are updated when the target program 141 is executed.

FIG. 3 is a diagram showing a specific example of the program management table 110. In the figure, four entries 11
5-118 are shown. The execution right information of each of these entries includes “actual accounting / prepaid flag”, “upper limit of execution time”, “upper limit of number of executions”, “payable communication availability flag”, “discount availability (maximum discount rate)”, and “prize issuance”. Permission flag ”.

Actual charge / prepaid flag: "0" is set for actual charge and "1" is set for prepaid. Execution time upper limit: The upper limit of the execution time of the target program 141 is set in minutes. An upper limit of the number of executions of the target program 141 is set. Paid communication availability flag: “1” is set if paid communication is available, and “0” is set if paid communication is not available.

Whether discount is possible (maximum discount rate): If discount of the target prize is impossible, "0" is set, and if it is possible, the value (%) of the maximum discount rate is set. "1" if is possible,
If it is impossible, “0” is set. In each execution right information item, the item in which “−1” is set is invalid.

Next, other items of the program management table 110 will be described. Program execution permission status flag: target program 141
Is set to "1" if the execution of the command is permitted, and set to "0" if the command is not permitted. This flag is set to be not permitted when the target program 141 exceeds the upper limit of the execution time or the upper limit of the number of executions.

The total execution time is the cumulative execution time (unit: minute) of the target program 141, and is periodically updated by the execution management unit 121. The total execution count is the cumulative execution count of the target program 141, and the execution management unit. 121, the target program 141
Is updated (incremented by "1") each time the driver is started. Next, the driver management information 112 (paid resource 1 information to paid resource 5 information) shown in FIG. 3 will be described.

Total sales quantity: Cumulative sales quantity of a certain product and updated by the product tray driver 106 Total sales price: Cumulative sales price of a certain product and total discount amount updated by the coin mech / building driver 105 : Cumulative discount amount of a certain product, updated by the coin mech / build bar 105 The number of prizes issued: The number of prizes issued, updated by the product tray driver 106 Paid communication usage frequency: Cumulative charge of the target program 141 Frequency of communication (a predetermined unit), which is updated by the communication line driver 108 every time the target program 141 performs pay communication. In the program management table 110 shown in FIG.
When the program ID 142 is “24004” and “5801”
The target program 141 of “0” has been suspended. When the program ID 142 is the target program 141 of “24004”, the program ID 142 has exceeded the upper limit of the number of executions (because the prepaid amount for 300 times has been exceeded). Target program 141 of “58010”
In the case of, the user is stopped trying to execute the unpaid communication.

If the program ID 142 is "1100
The target program 141 of "2" is a prepaid type program whose execution time is permitted up to 100 minutes. However, since the total execution time is 68 minutes at present, the execution is not stopped. Also, the program ID 142
The target program 141 of “11001” is a type of program that charges for the actual result, the upper limit of the execution time and the number of executions is not set, and the paid communication is also permitted. There is no.

Next, the operation of the embodiment having the above configuration will be described. First, the operation of the execution management unit 121 will be described with reference to the flowcharts of FIGS.

FIG. 4 is a flowchart for explaining a process in which the execution management unit 121 registers the newly loaded target program 141 in the program management table 110.

When a new target program 141 is loaded from the center device 20 or the portable terminal 30, a new entry for the target program 141 is added to the program management table 110.
10 (step S11).

Next, the program ID 142 and the execution right information 14 attached or built into the target program 141
3 is set in the new entry (step S12), and the program registration process ends.

FIG. 5 is a flowchart for explaining processing when the execution management unit 121 activates the target program 141. When activating a certain target program 141, the execution management unit 121 first sets the program management table 1
10, referring to the entry of the target program 141,
The number of executions and the execution permission state flag are checked (step S21). The number of executions is checked by comparing the total number of executions with the upper limit of the number of executions.

Then, it is determined whether or not the target program 141 is in the execution permitted state (step S22). If the execution is permitted (step S22, Yes), the "execution count" of the target program 141 in the program management table 110 is determined. Is incremented by "1" (step S23), and the target program 141 is started (step S2).
4), end the process.

On the other hand, if it is determined in step S22 that the state is not the execution permission state (step S22, No), the process is immediately terminated. FIG. 6 shows that the execution management unit 121
9 is a flowchart for explaining processing when the timer is activated by a timer event.

The execution management unit 121 updates the “total execution time” of the currently activated (executing) target program 141 in the program management table 110 (step S 31).

Next, it is determined whether there is any target program 141 whose total execution time exceeds the execution time upper limit (step S32). If there is a target program 141 whose execution time exceeds the execution time upper limit (step S32, Yes), the target program 141 in the program management table 110
Is set to "0" (non-permitted) (step S33), the target program 141 is stopped (step S34), and the process ends.

On the other hand, if there is no target program 141 exceeding the execution time upper limit value in step S32 (step S32, No), the process is immediately terminated.
FIG. 7 is a flowchart for explaining the operation of each driver (105 to 108).

When each driver is requested by the target program 141 to use a paid resource, the driver executes the “execution right information” of the target program 141 in the program management table 110.
It is determined whether the target program 141 has the right to execute the pay resource (step S41).

If there is an execution right (step S4)
1, Yes), normal driver processing (original processing of the driver) is executed (step S42), and when the processing is completed, the program management table 110 according to the usage amount of the paid resource used by the target program 141 is set. Then, the “usage amount of the paid resource” of the target program 141 is updated (step S43).

Next, each driver determines whether or not the updated value of the paid resource exceeds the limit value permitted for the target program 141 (step S44). This determination is made by referring to “execution right information” of the target program 141 in the program management table 110.

If the limit value is exceeded (step S44, Yes), the "execution permission status flag" of the target program 141 in the program management table 110 is set to non-permission (step S45), and the target The program 141 is stopped (step S46), and the process ends.

When it is determined in step S41 that there is no execution right (step S41, No), or
When it is determined that the limit value has not been exceeded at 44 (No at Step S44), the process is terminated.

Next, the operation of the read notification unit 122 will be described with reference to the flowcharts of FIGS. FIG.
9 is a flowchart illustrating the operation of the read notification unit 122 when the read notification unit 122 is activated by a fixed-period timer event from the timer 130.

When activated by a timer event, the read notification unit 122 reads the contents of the program management table 110 and transmits the contents to the communication line driver 10.
8, Notify the center device 20 via the communication line I / F 103 and the communication line 40 (step S51), and terminate the process.

The period of the timer event is specified by the center device 20, for example. FIG. 9 is a flowchart illustrating an operation of the read notification unit 122 when a request to read charging-related information is received from the center device 20 or the mobile terminal 30.

The read notifying unit 122 determines, for example, at a predetermined cycle, whether or not the read request has been received (step S61). If it is determined that the read request has been received (step S61, Yes), the program management unit 122 executes the program management. The contents of the table 110 are read, and the contents are transmitted to the request source of the read request (the center device 20 or the mobile terminal 30) (step S62), and the process ends.

On the other hand, if it is determined in step S61 that the read request has not been received (step S61, No),
The process ends immediately. The same processing as in the flowchart of FIG. 9 may be performed by an interrupt event. In this case, the read notification unit 122 sends the vending machine 1
0 activates the read notification unit 122 each time the read request is received from the center device 20 or the mobile terminal 30.

[0063]

As described above, according to the present invention, with respect to a vending machine to which a program can be loaded from the outside, the use of the program and the use of a pay resource accompanying the use of the vending machine are restricted. Thus, data for requesting legitimate compensation can be collected. In addition, by enabling the collection of the data, it is possible to provide an environment which is a base for distribution of a program for loading a vending machine from the outside and provision of a service using the vending machine.

[Brief description of the drawings]

FIG. 1 is a block diagram showing an overall configuration of a vending machine management system according to an embodiment of the present invention.

FIG. 2 is a diagram showing a data structure of a program management table.

FIG. 3 is a diagram showing a specific example of a program management table.

FIG. 4 is a flowchart illustrating a program registration process executed by an execution management unit.

FIG. 5 is a flowchart illustrating a program activation process executed by the execution management unit.

FIG. 6 is a flowchart illustrating a timer event process executed by an execution management unit.

FIG. 7 is a flowchart illustrating the operation of each driver.

FIG. 8 is a flowchart illustrating a timer event process executed by a read notification unit.

FIG. 9 is a flowchart illustrating an operation when a read notification unit receives a read request.

[Explanation of symbols]

 DESCRIPTION OF SYMBOLS 10 Vending machine 101 Commodity tray 102 Coin mech / build validity 103 Communication line I / F 104 Mobile terminal I / F 105 Coin mech / build validity driver 106 Commodity tray driver 107 Mobile terminal driver 108 Communication line driver 110 Program management table 111 Execution management unit Management information 112 Driver management information 115, 116, 117, 118 Entry 121 Execution management unit 122 Read notification unit 130 Timer 141 Target program 142 Program ID 143 Execution right information

 ──────────────────────────────────────────────────続 き Continuing on the front page (72) Inventor Yukio Makita 1-1, Tanabe Nitta, Kawasaki-ku, Kawasaki, Kanagawa Prefecture Inside Fuji Electric Co., Ltd. (72) Inventor Masami Takada 1, Tanabe Nitta, Kawasaki-ku, Kawasaki, Kanagawa Prefecture No. 1 Inside Fuji Electric Co., Ltd. (72) Inventor Takeo Nakano 1-1, Tanabe-Nitta, Kawasaki-ku, Kawasaki-shi, Kanagawa Prefecture F-term inside Fuji Electric Co., Ltd. 3E044 AA01 CB01 CB05 DA01 DB02 DB12 DC06 DE01 DE03 DE04

Claims (5)

[Claims] 1. A program loading means for loading a program from the outside, and for each of the loaded programs,
Storage means for storing billing information related to the program; controlling execution of each program; collecting billing information related to the execution of each program; and collecting billing information in the storage means based on the collection result. A vending machine comprising: a program management means for updating; 2. A pay resource charging information collecting unit that collects charging information of a pay resource related to each of the programs and updates charging information in the storage unit based on the collection result. The vending machine according to claim 1, wherein 3. The method according to claim 1, further comprising: stopping the execution of the program related to the charge information when the charge information of the pay resource related to the execution of the program or related to the program exceeds a set upper limit. 3. The vending machine according to claim 1, further comprising program stop means. 4. The apparatus according to claim 1, further comprising a notifying unit for notifying an external device of charging information stored in said storage unit.
2. The vending machine according to 2 or 3. 5. A program loading means for loading a program from the outside, and for each of the loaded programs,
Storage means for storing billing information related to the program; controlling execution of each program; collecting billing information related to the execution of each program; and collecting billing information in the storage means based on the collection result. A vending machine comprising: a program management means for updating; and a pay resource billing information collecting means for collecting billing information of pay resources related to each program, and updating the billing information in the storage means based on the collection result. Receiving means for receiving, from the vending machine, charging information related to each of the programs stored in the storage means; and charging individually for each of the programs based on the charging information received by the receiving means. A vending machine management system comprising: a center device including a calculation unit for calculating a fee;