JP5884850B2 - Information distribution apparatus and program - Google Patents

Description

The present invention relates to an information distribution apparatus and a program.

  2. Description of the Related Art Conventionally, various systems for distributing a program (software) from a server device to a terminal device via a communication network such as the Internet are known.

  For example, in Patent Document 1, when an application request is transmitted from the terminal to the server side, application software is distributed from the server device side to the terminal in the form of download, and data is received using the application software received on the terminal side. A software distribution system capable of processing is described.

  Patent Document 2 discloses that software is divided into a plurality of recombinable segment data and registered in a predetermined site, and each time a user terminal is detected to be linked to a site, a plurality of segment data is recorded. A technique is described in which each of the above is transmitted to a user terminal one by one so that even large-capacity data software can be transmitted without stressing the user.

  Patent Document 3 describes a software distribution method in a distributed system.

Japanese Patent Laid-Open No. 2005-18604 JP 2002-99476 A JP-A-8-95880

  By the way, terminal devices such as ECR (sales data processing device) and payment terminals installed in stores are different for each store even between stores set by the same company, and installed programs are different for each store. There is a case. In addition, even in the same store, the terminal device model is different for each floor, and the program installed on each floor may be different. In addition, even for terminal devices of the same model, the destination or the like differs depending on the terminal device, and the installed program may be different.

  However, in the conventional program distribution technology, a data management device such as a server only distributes a program in response to a request from a terminal, and the program installed like a terminal device installed in a store It was not possible to update the programs of a plurality of terminal devices of various types to the latest state.

An object of the present invention is to suppress network load and system load by restricting information distribution to a plurality of terminal devices .

Claim 1 is an information distribution apparatus for distributing information to a plurality of terminal devices, and when there is information to be distributed, a terminal that requires immediate distribution of the information among the plurality of terminal devices When it is determined that there is a terminal device that needs immediate distribution by the determination unit and a determination unit that determines a device, control is performed to distribute the information to be distributed first when the power of the terminal device is turned on. A first control unit; and a second control unit that controls to distribute the information to be distributed after the information distribution by the first control unit to a terminal device that does not require immediate distribution by the determination unit. It is characterized by comprising.
Claim 2 is an information distribution device for distributing information to a plurality of terminal devices, and when there is information to be distributed, a terminal that requires immediate distribution of the information among the plurality of terminal devices A determining unit that determines a device; and a control unit that controls distribution of information that needs immediate distribution when the terminal device starts processing for the terminal device that needs immediate distribution. to.

According to the present invention, network load and system load can be suppressed by restricting information distribution to a plurality of terminal devices .

It is a block diagram which shows the structural example of the program delivery system in embodiment of this invention. It is a block diagram which shows the internal structural example of the data management apparatus of FIG. It is a figure which shows the structural example of the function implement | achieved by cooperation with CPU11 of FIG. 2 and the application program memorize | stored in the memory | storage part. (A) is a figure which shows the data storage example of the store service master memory | storage part of FIG. 2, (b) is a figure which shows the data storage example of the program delivery information storage part of FIG. 2, (c) is FIG. 3 is a diagram illustrating a data storage example of a program data storage unit in FIG. 2. It is a block diagram which shows the example of an internal structure of ECR of FIG. It is a flowchart which shows the program data registration process performed by the program data registration part of FIG. It is a flowchart which shows the program delivery information registration process performed by the program delivery information registration part of FIG. It is a flowchart which shows the closing process performed by CPU of FIG. It is a flowchart which shows the service provision process performed by the store service port control part of FIG. It is a flowchart which shows the authentication process performed by the authentication control part of FIG. It is a flowchart which shows the program delivery confirmation process performed by the program delivery confirmation part of FIG. It is a flowchart which shows the program delivery process performed by the program delivery part of FIG. It is a figure which shows the example of data storage of the program delivery information storage part in Embodiment 2. It is a flowchart which shows the program delivery information registration process B performed by the program delivery information registration part of FIG. 3 in Embodiment 2. It is a figure which shows the example of data storage of the program delivery information storage part in Embodiment 3. It is a flowchart which shows the program delivery confirmation process B performed by the program delivery confirmation part of FIG. 3 in Embodiment 3. FIG. 10 is a diagram illustrating a configuration example of functions realized by cooperation of the CPU 11 of FIG. 2 and an application program stored in a storage unit in the fourth embodiment. 18 is a flowchart illustrating message interpretation processing executed by the message control unit 201 in FIG. 17 in the fourth embodiment. 18 is a flowchart illustrating a program distribution process B executed by the program distribution unit 204 of FIG. 17 in the fourth embodiment. 18 is a flowchart showing program data encryption processing executed by the encryption control unit 205 of FIG. 17 in Embodiment 4.

Embodiment 1
First, Embodiment 1 of the present invention will be described.
FIG. 1 shows a configuration example of a program distribution system 1 in the first embodiment. As shown in FIG. 1, a program distribution system 1 includes a data management device 10 and an ECR (Electronic Cash Resister) 20 (20A to 20D) as terminal devices connected via a communication network N so as to be able to transmit and receive data. It is configured. The communication network N is configured by a communication network such as a WAN (Wide Area Network) or the Internet, for example, but may include a LAN (Local Area Network) or the like, and may include a telephone line, a dedicated line, a mobile communication network, a communication A satellite network, CATV (Cable Television) line, Internet provider, etc. may be included. Moreover, although the number of ECR20 is illustrated as four units 20A-20D here, it is not specifically limited.

The data management apparatus 10 stores the latest version of program data corresponding to each ECR 20 connected via the communication network N, and for each ECR 20, a program indicating the type of installed program and the latest version of the program. A management code and the like are stored and managed, and in response to a request from each ECR 20, program distribution confirmation, program data distribution, and the like are performed.
The ECR 20 is provided in the store, and the merchandise transaction registration process (transaction date and time, merchandise name, merchandise sales quantity, sales amount data, registration process of the person in charge, etc.), inspection process, and settlement based on the operation of the operator This is a sales data processing device that performs processing, total sales in a store, and the like. As the ECR 20, for example, an electronic register or the like can be applied.

Hereinafter, each apparatus which comprises the program delivery system 1 is demonstrated.
First, the data management apparatus 10 will be described.
FIG. 2 shows an internal configuration example of the data management apparatus 10. As shown in FIG. 2, the data management device 10 includes a CPU (Central Processing Unit) 11, an input unit 12, a RAM (Random Access Memory) 13, a display unit 14, a storage unit 15, and a communication unit 16. The time measuring unit 17 is configured to be connected to each other via a bus 18.

  The CPU 11 centrally controls each unit of the data management apparatus 10. The CPU 11 expands a program designated from the system program and various application programs stored in the storage unit 15 in the RAM 13 and executes various processes in cooperation with the program expanded in the RAM 13.

FIG. 3 shows a functional configuration example realized by cooperation of the CPU 11 and various application programs stored in the storage unit 15. As shown in FIG. 3, the store service information registration unit 100 and the store service port control unit 200 as registration means are realized by the cooperation of the CPU 11 and the program.
More specifically, the store service information registration unit 100 includes a store service master registration unit 101, a program data registration unit 102, and a program distribution information registration unit 103.
Based on the input from the input unit 12, the store service master registration unit 101 registers the master information regarding the ECR 20 that is a program distribution target in the data management apparatus 10 in the store service master storage unit 151.
The program data registration unit 102 executes program data registration processing to be described later, and registers program data to be distributed to at least one of the ECRs 20 and attribute information thereof in the program data storage unit 153 based on an input from the input unit 12. .
When the master information is registered by the store service master registration unit 101, the program distribution information registration unit 103 provides information (program distribution information) for confirming the program distribution for the ECR 20 in which the master information is registered. Register in the program distribution information storage unit 152. The program distribution information registration unit 103 registers the program distribution information in the program distribution information storage unit 152 when the program data is registered by the program data registration unit 102.

More specifically, the store service port control unit 200 includes a message control unit 201, an authentication control unit 202, a program distribution confirmation unit 203, and a program distribution unit 204.
The message control unit 201 performs protocol processing of communication data received via the communication unit 16 and interprets request data included in the communication data.
The authentication control unit 202 serving as an authentication unit executes an authentication process to be described later, refers to master information registered in the store service master storage unit 151, and authenticates the ECR 20 connected via the communication unit 16.
The program distribution confirmation unit 203 as a distribution confirmation unit executes a program distribution confirmation process to be described later, acquires program distribution information for the ECR 20 that is the request source of the program distribution confirmation from the program distribution information storage unit 152, and needs to distribute the program. It is determined whether or not there is, and the result is transmitted to the requesting ECR 20.
The program distribution unit 204 serving as a distribution unit executes a program distribution process to be described later, reads program data stored in the program data storage unit 153, and transmits the program data to the ECR 20 that is the distribution request source of the program.

  The input unit 12 includes a keyboard having cursor keys, characters, numeric input keys, various function keys, and the like, and outputs an operation signal indicating that each key is pressed by the operator to the CPU 11. The input unit 12 may include a pointing device such as a mouse, and may receive a position input signal and transmit it to the CPU 11.

  The RAM 13 is a volatile memory. The RAM 13 has a work area for storing various programs to be executed and data related to these various programs.

  The display unit 14 includes an LCD (Liquid Crystal Display), a CRT (Cathode Ray Tube), and the like, and performs screen display according to a display control signal from the CPU 11.

  The storage unit 15 includes an HDD (Hard Disk Drive) or the like, and stores various programs and various data in a readable and writable manner. In this embodiment, as shown in FIG. 2, the storage unit 15 includes a store service master storage unit 151, a program distribution information storage unit 152 as a distribution information storage unit, and a program data storage unit 153 as a program storage unit. ing.

FIG. 4A shows an example of data storage in the store service master storage unit 151. The store service master storage unit 151 stores master information for each registered ECR 20, and as shown in FIG. 4A, a “terminal device code” field, a “group code” field, a “company code” ”Field,“ store code ”field,“ model code ”field, and“ connection classification ”field.
The “terminal device code” field stores a terminal device code uniquely assigned to the ECR 20. The “group code” field stores a group code indicating a classification category when the ECR 20 is classified according to a predetermined standard. The “company code” field stores a company code representing a company in which the ECR 20 is installed. The “store code” field stores a store code representing a store where the ECR 20 is installed. The “model code” field stores a model code representing the terminal model of the ECR 20. The model code is composed of the upper 3 digits, and is composed of a major code uniquely assigned to the model and a lower 3 digits and a minor code indicating the destination. The “connection classification” field stores a flag indicating whether or not the ECR 20 can be connected (“1” if connection is possible, “0” if connection is not possible).

FIG. 4B shows an example of data storage in the program distribution information storage unit 152. The program distribution information storage unit 152 stores program distribution information for each program installed in each ECR 20 that is a program distribution target. As illustrated in FIG. 4B, the “terminal device code” field, It has a “group code” field, a “company code” field, a “store code” field, a “program identification code” field, and a “program management code” field.
The “terminal device code” field stores a terminal device code of the ECR 20 that is a distribution target of the program. The “group code” field stores a group code, the “company code” field stores a company code, and the “store code” field stores a store code. The “program identification code” field stores a program identification code representing the type of program. The “program management code” field stores a program management code indicating the version of the program to be distributed.
Note that the version of the program to be distributed is the latest version. Each ECR 20 is loaded with a plurality of types of programs for each function, and the program identification code represents the type of program for each function.

FIG. 4C shows an example of data storage in the program data storage unit 153. The program data storage unit 153 stores program data of a program to be distributed and attribute information of the program. As shown in FIG. 4C, a “model code” field, a “program identification code” field, It has a “program management code” field, a “program data size” field, and a “program data” field.
The “model code” field stores the model code of the ECR 20 corresponding to the program data. The “program identification code” field stores a program identification code representing the type of program. The “program management code” field stores a program management code indicating the latest version of the program. The “program data size” field stores information indicating the size of the program data. The “program data” field stores program data.

  As described above, the model code is composed of a major code uniquely assigned to the model and a minor code indicating the destination. As shown in FIG. 4C, in the program data storage unit 153, the program data is stored and managed for each combination of the model code and the program identification code. That is, even if the model is the same, different program data can be distributed between ECRs 20 with different destinations.

The communication unit 16 includes a modem, a TA (Terminal Adapter), a router, a network card, and the like. The communication unit 16 transmits / receives data to / from an external device such as on the connected communication network N.
The timer unit 17 has a built-in timer circuit, measures the current time and the current date, and outputs them to the CPU 11.

Next, the configuration of the ECR 20 as a terminal device will be described.
FIG. 5 shows an internal configuration example of the ECR 20. As shown in FIG. 5, the ECR 20 includes a CPU 21, an input unit 22, a RAM 23, a display unit 24, a storage unit 25, a communication unit 26, a timing unit 27, a drawer 28, a print unit 29a, Each part is configured to be connected via a bus 29b.

  The CPU 21, RAM 23, and communication unit 26 are the same as the configurations of the CPU 11, RAM 13, and communication unit 16 of the data management apparatus 10, respectively, and different parts will be mainly described.

  The CPU 21 centrally controls each part of the ECR 20. The CPU 21 develops a program designated from the system program and various application programs stored in the storage unit 25 in the RAM 23, and executes various processes in cooperation with the program expanded in the RAM 23.

  For example, the CPU 21 reads out various application programs in accordance with the operation of the input unit 22 by the operator, and cooperates with the read-out application program to register a product transaction, check processing, checkout processing, store sales total processing in the store Etc.

  The CPU 21 reads the opening process program at the time of opening, that is, when the power key of the input unit 22 is operated and the power is turned on, and executes the opening process in cooperation with the read program. That is, the CPU 21 connects to the data management apparatus 10 to transmit a program distribution confirmation request, and whether or not the program distribution confirmation response received from the data management apparatus 10 includes information indicating that the program needs to be updated. If it is determined that the information indicating that the program needs to be updated is included, a program distribution request is transmitted to the data management apparatus 10 to acquire the program data, and the program is acquired by the acquired program data. Update (install).

  Further, the CPU 21 reads the closing process program when the input unit 22 instructs closing, and executes the closing process (see FIG. 8) in cooperation with the read program.

  The input unit 22 includes a cash register keyboard including a power key, cursor keys, characters, numeric input keys, various function keys, and the like, and outputs an operation signal to the CPU 21 when each key is pressed by the operator. The display unit 24 is composed of an LCD or the like, and performs screen display according to a display control signal from the CPU 21. The input unit 22 may be configured as a touch panel integrally with the display unit 24. Further, the input unit 22 may include a barcode reader, a barcode scanner, or the like that reads a barcode provided on the product.

  The storage unit 25 is configured by a flash memory or the like. The storage unit 25 stores various types of data such as various programs and sales data, and master information (terminal device code, group code, company code, store code, model code, etc.) of the ECR 20 in a readable and writable manner. The storage unit 25 may be configured with an HDD or the like.

The communication unit 26 transmits / receives data to / from an external device such as the data management device 10 on the communication network N.
The timer unit 27 has a built-in timer circuit, measures the current time and the current date, and outputs them to the CPU 21.

  The drawer 28 is a drawer that stores cash such as coins and banknotes. The drawer 28 opens the drawer, for example, according to an instruction from the CPU 21.

  The printing unit 29a is, for example, a thermal printer, and has receipt and journal roll papers, and prints out data such as the amount of money on each roll paper in accordance with an instruction input from the CPU 21.

  Next, main operations of the data management apparatus 10 and the ECR 20 in the first embodiment will be described in detail with reference to flowcharts.

(Program data registration process)
FIG. 6 shows a flow of program data registration processing executed by the program data registration unit 102 of the data management apparatus 10. It is assumed that the program data file to be registered is stored in the storage unit 15.

  First, a program registration screen (not shown) is displayed on the display unit 14, and directory information in which program data to be registered is stored, and attribute information of program data to be registered, that is, model code, program identification code, program management An input from the input unit 12 such as a code is accepted (step S1).

  Next, the program data to be registered is read into the RAM 13 and the program data size is acquired (step S2).

  Next, the attribute information of the program data to be registered, that is, the model code, the program identification code, the program management code, and the program data size acquired in step S2 are registered in the program data storage unit 153. At the same time, the read program data is registered in the RAM 13 (step S3).

  When the registration of the program data is completed, the program distribution information registration unit 103 executes a program distribution information registration process (step S4), and this process ends.

FIG. 7 shows a flow of program distribution information registration processing executed by the program distribution information registration unit 103 in step S4.
In the program distribution information registration process, first, a record having the model code of the program data registered in step S3 is searched in the store service master storage unit 151, and the searched record is read to the RAM 13 (step S101). .

  Next, in the program distribution information storage unit 152, a record including the terminal device code of each record retrieved in step S101 and the program identification code of the registered program data is retrieved, and the retrieved record is read into the RAM 13 ( Step S102).

  Next, the program management code of the record read into the RAM in step S102 is changed to the program management code of the registered program data, and the program distribution information in the program distribution information storage unit 152 is updated with the changed contents (step S102). S103), the process ends.

  When a new version of program data is registered in the program data storage unit 153 by the program data registration process, the program management code in the program distribution information storage unit 152 for the ECR 20 to which the new version of program data is to be distributed is automatically set. Can be updated.

(Closed processing)
FIG. 8 shows a flow of the closing process executed by the CPU 21 of each ECR 20. This process is executed when a closing instruction is input by the input unit 22 at the end of the business in the store.
First, communication connection to the data management apparatus 10 is performed by the communication unit 26 (step S11). Next, settlement processing such as printing of daily sales data in a journal, saving of daily sales data, resetting, etc. is performed (step S12).

  Next, a program distribution confirmation request is transmitted to the data management apparatus 10 by the communication unit 26 (step S13), and a program distribution confirmation response from the data management apparatus 10 is received (step S14).

  Here, when various requests are transmitted from the ECR 20 to the data management apparatus 10, request data in a predetermined format is transmitted. The request data has a header part and a data part. The header portion includes information necessary for data communication between the ECR 20 and the data management device 10, such as an address on the communication network N of the destination (data management device 10), an address on the communication network N of the transmission source, and the like. Is included. Further, encryption information about the data portion may be included. The data part includes the type of request (for example, program distribution confirmation, program distribution, etc.), parameters delivered to the data management apparatus 10 when making various requests, and the like.

  For example, the data part of the authentication request data includes the terminal device code of ECR20. The data part of the program distribution confirmation request data includes a terminal device code of the ECR 20, a program identification code of each program stored in the storage unit 25, and a program management code. The data part of the distribution request data includes a terminal device code of the ECR 20, a model code, a program identification code of a program that requests distribution, and a program management code.

  Similarly, when various responses are transmitted from the data management apparatus 10 to the ECR 20, response data in a predetermined format is transmitted. The response data has a header part and a data part. The header part includes information necessary for data communication between the ECR 20 and the data management apparatus 10. Further, encryption information about the data portion may be included. In the data portion, the response content (for example, in the case of a response to a program distribution confirmation request, distribution confirmation information for each program identification code (information indicating whether or not the program distribution is necessary), a response to the program distribution request In this case, program data) is included.

  When the program delivery confirmation response is received, the processing of loop 1 in steps S15 to S21 is repeatedly executed for the number of programs (the number of program identification codes) included in the received response data.

First, distribution confirmation information corresponding to one program identification code is extracted from the response data (step S16), it is determined whether or not program distribution (update) is necessary, and program distribution (update) is necessary. If it is determined that there is (step S17; YES), a program distribution request is transmitted to the data management device 10 by the communication unit 26 (step S18). In requesting program distribution, distribution request data is transmitted to the data management apparatus 10. When response data of a program distribution response from the data management device 10, that is, program data is received by the communication unit 26 (step S 19), the program stored in the storage unit 25 is updated (installed) with the distributed program data. (Step S20), the process proceeds to the loop 1 process for the delivery confirmation information corresponding to the next program identification code in the response data.
The program data transmitted from the data management apparatus 10 includes program data attribute information, and the ECR 20 can recognize the program identification code and the program management code of the program data.

  On the other hand, if it is determined that program distribution (update) is not necessary (step S17; NO), the process proceeds to loop 1 processing for distribution confirmation information corresponding to the next program identification code.

  When the processing of the loop 1 corresponding to the number of programs included in the received response data (the number of program identification codes) is completed (step S21), the communication unit 26 is disconnected from the data management device 10 (step S22). The process ends.

  In each ECR 20, the opening process executed when the power is turned on is the same as the closing process described with reference to FIG. 8 except that the process of step S12 described above is not performed.

  Through the above-described closing process and opening process, the ECR 20 inquires of the data management apparatus 10 whether or not program distribution (update) is necessary at the time of opening and closing, and if necessary, a program data distribution request. To update the program.

(Service provision processing)
FIG. 9 shows a flow of service providing processing executed by the store service port control unit 200 of the data management apparatus 10. This process is a process executed on the data management apparatus 10 side corresponding to the closing process and the opening process in the ECR 20 described above.

  First, when the communication unit 16 receives a connection request from the ECR 20, connection with the ECR 20 is started in response to the connection request (step S31). Next, the communication unit 16 waits for reception of request data from the ECR 20 (step S32). When the request data is received (step S32; YES), the message control unit 201 performs message analysis processing of the request data, The content of the requested process is specified (step S33).

  As a result of the analysis by the message control unit 201, when it is determined that the content of the received request data is an authentication request (step S34; authentication request), the authentication control unit 202 executes the authentication process shown in FIG. Step S35).

FIG. 10 shows a flow of authentication processing executed by the authentication control unit 202 in step S35 of FIG.
In the authentication process, first, a record having a terminal device code included in the request data is searched in the store service master storage unit 151 (step S201). As a result of the search, if it is determined that the record having the terminal device code included in the request data does not exist in the store service master storage unit 151 (step S202; NO), authentication NG to the ECR 20 connected via the communication unit 16 is performed. (Step S205), and the process returns to step S32 in FIG.

  As a result of the search, if it is determined that a record including the terminal device code of the request data exists in the store service master storage unit 151 (step S202; YES), the connection classification of the record is referred to and the connection classification is “1”. If there is any (step S203; YES), the ECR 20 connected via the communication unit 16 is notified that the authentication is OK (step S204), and the process returns to step S32 in FIG. When the connection classification is “0” (step S203; NO), the ECR 20 connected via the communication unit 16 is responded to the authentication NG (step S205), and the process returns to step S32 in FIG.

  Returning to FIG. 9, if it is determined that the content of the received request data is a program distribution confirmation request as a result of analysis by the message control unit 201 (step S34; program distribution confirmation request), the program distribution confirmation unit 203 11 is executed (step S36). The program distribution confirmation process and the program distribution process are executed only when the connected ECR 20 is authenticated in the above authentication process.

FIG. 11 shows a flow of the program distribution confirmation process executed by the program distribution confirmation unit 203 in step S36 of FIG.
In the program distribution confirmation process, first, a record having a terminal device code included in the request data is searched in the program distribution information storage unit 152, and a record having the terminal device code included in the request data is read to the RAM 13 ( Step S301).

  Next, the processing of loop 2 in steps S302 to S308 is repeatedly executed for the number of program identification codes (the number of types of programs) included in the received request data.

  First, one program identification code and a program management code corresponding to the program identification code are extracted from the received request data (step S303). Next, it is determined whether or not a record of program distribution information having the extracted program identification code exists in the RAM 13, and if it is determined that the record does not exist (step S304; NO), the type of the type corresponding to the program identification code is determined. It is determined that program distribution is not necessary, program distribution confirmation information indicating that program distribution of the program identification code is not necessary is set in the response data (step S307), and loop 2 processing for the next program identification code Migrate to

  On the other hand, if it is determined that the record of the program distribution information having the program identification code extracted in step S303 exists in the RAM 13 (step S304; YES), the program management code corresponding to the program identification code extracted from the request data Is determined to be different from the program management code in the record having the program identification code read to the RAM 13 in step S301. If it is determined that it is different (step S305; YES), it is necessary to distribute the program. The program delivery confirmation information indicating that the delivery of the program of the type corresponding to the program identification code is necessary is set in the response data (step S306), and the processing of loop 2 for the next program identification code is performed. Row.

  On the other hand, when it is determined that the program management code corresponding to the program identification code extracted from the request data is the same as the program management code in the record having the program identification code read to the RAM 13 in step S301 (step S301). S305; NO), it is determined that it is not necessary to distribute the program of the type corresponding to the program identification code, and program distribution confirmation information indicating that the program distribution of the program identification code is unnecessary is set in the response data (step In step S307, the process proceeds to loop 2 for the next program identification code.

  When the processing of loop 2 for all the program identification codes included in the received request data is completed (step S308), the set response data is transmitted to the ECR 20 connected by the communication unit 16 (step S309), and the processing is Control proceeds to step S32 in FIG.

  Returning to FIG. 9, as a result of the analysis by the message control unit 201, if it is determined that the content of the received request data is a program distribution request (step S34; program distribution request), the program distribution unit 204 shows that in FIG. A program distribution process is executed (step S37).

FIG. 12 shows a flow of program distribution processing executed by the program distribution unit 204 in step S37 of FIG.
In the program distribution process, first, in the program data storage unit 153, program data having attribute information that matches the model code, the program identification code, and the program management code included in the request data is searched and the corresponding program data is read out. (Step S401).

  Next, the read program data is set as response data and transmitted to the authenticated ECR 20 connected by the communication unit 16 (step S402). Then, the process returns to step S32 in FIG.

  Returning to FIG. 9, when it is determined that the content of the received request data is a disconnection request as a result of analysis by the message control unit 201 (step S34; disconnection request), the communication unit 16 disconnects the communication with the ECR20. (Step S38), this process ends.

As described above, in the program distribution system 1, the program management information indicating the type of program installed in the ECR 20 to be distributed by the data management apparatus 10 and the latest version to be distributed is stored in the program distribution information storage unit. 152, when a program distribution confirmation request is transmitted by each ECR 20 at the time of opening and closing, the version of each program installed in the source ECR 20 is compared with the information indicating the latest version. If they are different, it responds to the connected ECR 20 that distribution is necessary. In the ECR 20, when a response is received from the data management apparatus 10 that the program needs to be distributed, a program distribution request is made to the data management apparatus 10 to acquire and update the program data.
Therefore, the latest program corresponding to the ECR 20 can be distributed to each of the plurality of ECRs 20 connected to the communication network N, and each ECR 20 can always operate with the latest program.

[Embodiment 2]
Hereinafter, Embodiment 2 of the present invention will be described.
In the first embodiment, when a new version of program data is registered in the program data storage unit 153 by the program data registration unit 102, the program distribution information registration unit 103 performs a program distribution information registration process, and performs the pre-upgrade version processing. The program management code of all program distribution information of the ECR 20 in which the same kind of program is installed is changed to a program management code indicating a new version. However, when the opening and closing of the ECR 20 are concentrated in a predetermined time zone, if the program management codes of all corresponding ECRs 20 are changed at once, the program distribution requests to the data management apparatus 10 are concentrated, and the network load or Increases system load.
Therefore, in the second embodiment, in order to prevent the concentration of program distribution requests to the data management apparatus 10, network load and system load are suppressed by restricting update targets of program distribution information performed at a time.

  FIG. 13 shows a data storage example of the program distribution information storage unit 152 in the second embodiment. As illustrated in FIG. 13, the program distribution information storage unit 152 according to the present embodiment includes a “delivery result” field in addition to the fields described with reference to FIG. 4B in the first embodiment. The “delivery record” field stores distribution record information (undelivered flag “0”, distributed flag “1”) indicating that the program data has been distributed after the program data is updated.

  Other configurations in the second embodiment are the same as those described in the first embodiment, and thus description thereof is omitted.

Next, the operation in the second embodiment will be described.
In the second embodiment, the program distribution information registration process executed in step S4 (see FIG. 6) of the program distribution process and the program data registration process is different from that in the first embodiment.

  In the program distribution process according to the second embodiment, after the process of step S402 described in FIG. 12, the terminal device code of the ECR 20 that is the distribution target of the program data and the program identification code of the distributed program in the program distribution information storage unit 152 A process is performed in which “1” is set in the “delivery result” field of the record having.

  In the program distribution information registration process (referred to as program distribution information registration process B in order to distinguish from the first embodiment) in the second embodiment, the process is performed according to the flow shown in FIG. In the following description, group codes are grouped into predetermined ranges (for example, 001 to 100, 101 to 200, 201 to 300,...), And the program distribution target ECR 20 is divided into groups. A description will be given assuming that the program management code of the distribution information is updated.

  In the program distribution information registration process B, first, in the store service master storage unit 151, a record including the model code registered in step S3 of the program data registration process shown in FIG. (Step S501).

  Next, in the program distribution information storage unit 152, a record including the terminal device code of each record retrieved in step S501 and the program identification code of the registered program data is retrieved, and the retrieved record is read to the RAM 13 ( Step S502).

  Next, the records read to the RAM 13 in step S502 are divided into groups for each predetermined group code range (step S503), and records belonging to groups in a predetermined range (for example, 001 to 100) are recorded. The program management code is changed to the program management code of the newly registered program data, the distribution result field is initialized to “0”, and the information in the program distribution information storage unit 152 is updated with the changed contents. (Step S504). Further, the date and time information output by the time measuring unit 17 at the time of update is stored in the RAM 13 as an update date and time (step S505).

  Next, the processing of loop 3 in steps S506 to S513 is repeatedly executed until the update of all groups is completed.

  First, a sleep state is set for a predetermined time (for example, 1 hour) (step S507), and then it is determined whether or not a predetermined period (for example, 3 days) has elapsed since the update of the program distribution information of the group to be updated last time. If it is determined that the predetermined period has elapsed (step S508; YES), the process proceeds to step S511.

  If it is determined that the predetermined period has not elapsed since the update of the program distribution information of the group that was updated last time (step S508; NO), the record of the program distribution information having the group code that was updated last time is the program distribution. It is acquired from the information storage unit 152 (step S509), and it is determined whether or not the record in which the “delivery result” field is “1” exceeds a predetermined ratio (for example, 80%) (step S510). If it is determined that the record with the distribution result flag “1” exceeds the predetermined ratio (step S510; YES), the process proceeds to step S511. If it is determined that the record whose “delivery record” field is “1” does not exceed a predetermined ratio (step S510; NO), the processing of the next loop 3 is executed.

  In step S511, the program management code of the record having the group code corresponding to the group to be updated next among the records read to the RAM 13 in step S502 is the program management code of the newly registered program data. In addition, the distribution result field is initialized to “0”, and the information in the program distribution information storage unit 152 is updated with the changed contents. Further, the update date and time stored in the RAM 13 is updated with the date and time information output by the time measuring unit 17 at the time of update in step S510 (step S512), and the processing of the next loop 3 is executed.

  When the update for all the groups is completed (step S513), this process ends.

  As described above, in the second embodiment, the update target of the corresponding program distribution information when a new version of program data is registered in the program data storage unit 153 in the data management apparatus 10 is within a predetermined group code range. Restricted to a group, the program distribution information of the next group is updated after a predetermined period after update or when the program distribution performance of the updated group exceeds a predetermined ratio. As described above, since the program distribution information is updated at different times for each group, it is possible to prevent concentration of program distribution requests to the data management apparatus 10 and to suppress network load and system load.

[Embodiment 3]
Hereinafter, Embodiment 3 of the present invention will be described.
In the first and second embodiments, the ECR 20 connects to the data management apparatus 10 at the time of opening and closing, makes a distribution confirmation request for the program installed therein, and if necessary, obtains program data of the corresponding program. It has been described that the program is updated upon request for distribution. By configuring in this way, all the programs of the ECR 20 can always be updated. However, since it takes time to download and install the program data, it may be difficult to operate even if the power is turned on at the time of opening. Therefore, in the third embodiment, only the program that needs to be updated immediately at the time of establishment is distributed, and the program is distributed at the time of closing other than that.

  FIG. 15 shows a data storage example of the program distribution information storage unit 152 in the third embodiment. As shown in FIG. 15, the program distribution information storage unit 152 according to the present embodiment includes a “distribution timing” field in addition to the fields described with reference to FIG. 4B in the first embodiment. The “distribution timing” field stores distribution timing information (“immediate” for a program to be distributed immediately, “normal” for a program that does not need to be distributed immediately).

  Other configurations in the third embodiment are the same as those described in the first embodiment, and thus the description thereof is omitted.

Next, the operation in the third embodiment will be described.
In the third embodiment, the request data of the program distribution confirmation request transmitted to the data management apparatus 10 in the closing process and opening process executed by the ECR 20 indicates whether it is a closing process or an opening process. It is different from the first embodiment that information is included.

  Further, the program data registration process executed in the data management apparatus 10 and the program distribution confirmation process executed in step S36 of the service providing process in FIG. 9 are different from those in the first embodiment.

  In the program data registration process according to the third embodiment, whether or not the program data to be registered needs immediate distribution together with the model code, program identification code, and program confirmation code of the program data to be registered in step S1 of FIG. Information is entered. Immediately corresponds to a case where the program needs to be updated immediately due to a serious failure, for example. In step S103 of FIG. 7, the program management code of the program distribution information is changed to the program management code of the registered program data, and the “immediate” or “normal” information input in step S1 is the distribution timing. Information is added to the “distribution timing” field, and the program distribution information storage unit 152 is updated with the added or changed contents.

  Further, in the program distribution confirmation process in the third embodiment (the program distribution confirmation process B is distinguished from the first embodiment), the process is performed according to the flow shown in FIG.

  In the program distribution confirmation process B, first, a record having a terminal device code included in the request data is retrieved in the program distribution information storage unit 152, and the retrieved record is read into the RAM 13 (step S601).

  Next, the process of loop 4 in steps S602 to S609 is repeatedly executed for the number of program identification codes (the number of types of programs) included in the received request data.

  First, a program identification code and a program management code corresponding to the program identification code are extracted from the received request data (step S603). Next, it is determined whether or not the record of the program distribution information having the extracted program identification code exists in the RAM 13, and if it is determined that it does not exist (step S604; NO), the type corresponding to the program identification code is determined. It is determined that program distribution is not necessary, distribution confirmation information indicating that program distribution of the program identification code is not necessary is set in the response data (step S608), and the next program identification code included in the request data is determined. The process proceeds to loop 4 processing.

  On the other hand, if it is determined that the record of the program distribution information having the program identification code extracted in step S603 is present in the RAM 13 (step S604; YES), the program management code corresponding to the program identification code extracted from the request data Is determined to be different from the program management code of the record having the program identification code read to the RAM 13 in step S601 (NO in step S605). It is determined that it is not necessary to distribute the type of program corresponding to the program identification code, distribution confirmation information indicating that program distribution of the program identification code is unnecessary is set in the response data (step S608), and the request data includes Next step included The process proceeds to loop 4 for Gram identification code.

  If it is determined that the program management code corresponding to the program identification code extracted from the request data is different from the program management code of the record having the program identification code read to the RAM 13 in step S601 (step S605; YES). Based on the request data and the delivery timing information of the record including the program identification code read to the RAM 13 in step S601, either the connected ECR 20 is closed or is a program that requires immediate delivery. It is determined whether or not this is true (step S606).

  If it is determined that the connected ECR 20 is closed or the program requires immediate distribution (step S606; YES), it is determined that the program needs to be distributed. Distribution confirmation information indicating that it is necessary to distribute the type of program corresponding to the program identification code is set in the response data (step S607), and the processing proceeds to loop 4 for the next program identification code included in the request data. To do.

  If it is determined that the connected ECR 20 is not closed or is a program that requires immediate distribution (step S606; NO), the type of program corresponding to the program identification code is determined. It is determined that distribution is not necessary, distribution confirmation information indicating that program distribution of the program identification code is unnecessary is set in the response data (step S608), and loop 4 for the next program identification code included in the request data Move on to processing.

  When the processing of loop 4 for all the program identification codes included in the received request data is completed (step S609), the set response data is transmitted to the ECR 20 connected by the communication unit 16 (step S610), and the processing is Control proceeds to step S32 in FIG.

  As described above, in the program distribution confirmation processing according to the third embodiment, when the ECR 20 makes a distribution confirmation request when the ECR 20 is closed, or the distribution timing of the program that requested the distribution confirmation is immediately set in the program distribution information storage unit 152. In this case, distribution confirmation information indicating that distribution is necessary is set in the response data. Therefore, only the programs that need to be updated immediately are opened at the time of opening, and other updates are performed at the time of closing, so that it is possible to update the programs without impairing the convenience of the user. Become.

[Embodiment 4]
Embodiment 4 of the present invention will be described below.
In the fourth embodiment, data (for example, request data and program data) transmitted and received between the ECR 20 and the data management apparatus 10 is encrypted.

FIG. 17 shows a functional configuration example realized by the cooperation of the CPU 11 of the data management apparatus 10 according to the fourth embodiment and various application programs stored in the storage unit 15.
As shown in FIG. 17, in the fourth embodiment, the store service port control unit 200 includes an encryption control unit 205. The encryption control unit 205 performs decryption of request data transmitted from the ECR 20, encryption of program data transmitted to the ECR 20, and the like.

  In the fourth embodiment, each ECR 20 and the data management apparatus 10 exchange encryption keys used for each encryption method in advance, and the storage unit 15 stores the terminal device code and encryption key of each ECR 20 in association with each other. doing.

  Further, the ECR 20 can set the encryption strength when performing data communication with the data management apparatus 10 by operating the input unit 22. Specifically, it is possible to set the encryption method of the encryption strength desired by the user from among RSA (Rivest Shamir Adleman), T-DES (Triple DES), DES (Data Encryption Standard), and plaintext. Yes. The ECR 20 stores encryption processing programs for encrypting and decrypting data using the RSA, T-DES, and DES encryption methods, and the data encryption and decryption are performed in cooperation with the CPU 21 and the encryption processing program. Decoding can be performed.

  Other configurations in the fourth embodiment are the same as those described in the first embodiment, and thus the description thereof is omitted.

Next, the operation in the fourth embodiment will be described.
In the fourth embodiment, when performing a closing process and an opening process in the ECR 20 and making a program distribution request and a program transmission request to the data management apparatus 10, an encryption processing program of a preset encryption method is read and the request After the data part of the data is encrypted by a preset encryption method, it is transmitted to the data management apparatus 10 via the communication part 26.

  In the data management apparatus 10, when a request from the ECR 20 is received in the service providing process shown in FIG. 9, the message control unit 201 executes the message interpretation process shown in FIG. 18 in step S33.

  In the message interpretation process, first, the encryption information in the header portion of the request data received in step S32 is referred to (step S701), and the encryption method that encrypts the request data is determined (step S702). When it is determined that the encryption method of the request data is RSA (step S702; RSA), the encryption control unit 205 uses the encryption key (public key) of the request source ECR 20 to change the data portion of the request data according to the RSA algorithm. Decoding is performed (step S703), and the process proceeds to step S706.

  On the other hand, if it is determined that the encryption method of the request data is T-DES (step S702; T-DES), the encryption control unit 205 uses the encryption key of the request source ECR 20 to convert the data portion of the message to T-DES. Decoded by the algorithm (step S704), the process proceeds to step S706.

  On the other hand, when it is determined that the encryption method of the request data is DES (step S702; DES), the encryption control unit 205 decrypts the data portion of the request data by the DES algorithm using the encryption key of the requesting ECR 20 ( In step S705), the process proceeds to step S706.

  If it is determined that the request data is plain text (step S702; plain text), the process proceeds to step S706.

  In step S706, the decrypted or plaintext request data is analyzed by the message control unit 201, and the content of the requested process is specified (step S706). The process proceeds to step S34 in FIG. The process is executed.

  In the present embodiment, when the request specified in step S706 is a program distribution process, in step S4 of FIG. 6, the program distribution process shown in FIG. 19 (to be distinguished from the first embodiment, the program distribution process B). Is executed.

  In the program distribution process B, first, program data having attribute information matching the model code, program identification code, and program management code included in the request data is searched in the program data storage unit 153, and the corresponding program data is found. Read is performed (step S801).

  Next, program data encryption processing is executed by the encryption control unit 205, and the read program data is encrypted (step S802).

  FIG. 20 shows the program data encryption process executed in step S802 of FIG. In the program data encryption process, the encryption method of the request data received from the ECR 20 is determined. If it is determined that the encryption method of the request data is RSA (step S901; RSA), the program data read by the encryption control unit 205 in step S801 of FIG. 19 is RSA using the encryption key of the request source ECR20. Encryption is performed by the algorithm (step S902), and the process proceeds to step S803 in FIG.

  On the other hand, when it is determined that the encryption method of the request data is T-DES (step S901; T-DES), the program data read out in step S801 by the encryption control unit 205 uses the encryption key of the requesting ECR 20 as an encryption key. The data is encrypted using the T-DES algorithm (step S903), and the process proceeds to step S803 in FIG.

  On the other hand, if it is determined that the encryption method of the request data is DES (step S901; DES), the program data read out in step S801 by the encryption control unit 205 uses the encryption key of the requesting ECR 20 to create a DES algorithm. (Step S904), and the process proceeds to step S803 in FIG.

  On the other hand, if it is determined that the request data is plain text (step S901; plain text), the process proceeds to step S803 in FIG.

  In step S803 of FIG. 19, plain text or encrypted program data is set as response data and transmitted to the ECR 20 connected by the communication unit 16 (step S803). Then, the process returns to step S32 in FIG.

  As described above, in the fourth embodiment, the data management apparatus 10 encrypts and transmits the program data with the encryption strength corresponding to the distribution destination ECR 20. Therefore, the program data can be encrypted and transmitted with the encryption strength changed according to the level of security required for each ECR 20, and the program data can be efficiently transmitted while balancing the load on the encryption process and the safety. Can be delivered.

In the fourth embodiment, when the request data is encrypted and transmitted by the encryption method set in each ECR 20, the data management apparatus 10 specifies the encryption method of the request data and encrypts the program data by the encryption method. The transmission is made to the requesting ECR 20 and the program code is encrypted by an encryption method corresponding to the ECR 20, but the present invention is not limited to this.
For example, an encryption method is determined in advance for each model code of the ECR 20, and the data management apparatus 10 specifies the model code of the requesting ECR 20 with reference to the store service master storage unit 151, and responds to the specified model code. The program data distributed by the encryption method may be encrypted. In this way, the program data can be encrypted and transmitted with the encryption strength corresponding to the level of security required for each model of the ECR 20, and while balancing the load on the encryption process and the safety, It becomes possible to distribute program data efficiently.
Further, for example, an encryption method is predetermined for each type of program, and the data management apparatus 10 encrypts program data to be distributed by an encryption method according to the type of program data requested for distribution. Also good. In this way, program data can be encrypted and transmitted with the encryption strength corresponding to the security level required for each program, and the load on the encryption process and the safety can be balanced and efficiently Program data can be distributed.

Note that the description in each of the above embodiments is a preferred example of the program distribution system 1 according to the present invention, and the present invention is not limited to this.
For example, in the above-described embodiment, the case where the terminal device is ECR20 has been described as an example. However, the present invention is not limited to this. For example, the terminal device reads the card information of the customer's credit card in the store and includes the card information. A payment terminal that transmits payment data and a payment approval request to a card company device may be used, and a program may be distributed to the payment terminal by the data management device 10.

  In the above embodiment, when the latest version of program data of a certain type of program is newly registered, the program management code for all ECRs 20 loaded with the program stored in the program distribution information storage unit 152 is stored. However, only the ECR 20 having a specific terminal device code, company code, or store code may be updated individually. In this way, for example, limited distribution such as distribution of the monitoring program at the time of the failure to the ECR 20 where the failure has occurred becomes possible.

  In the fourth embodiment, encryption and decryption are performed using a fixed encryption key. However, the encryption key is periodically updated in the data management apparatus 10 and updated in the program to be distributed. You may make it deliver by embedding. Thereby, it is possible to improve the safety of communication between the data management apparatus 10 and the ECR 20.

  In addition, the detailed configuration and detailed operation of each device constituting the program distribution system 1 can be changed as appropriate without departing from the spirit of the invention.

1 Program Distribution System 10 Data Management Device 11 CPU
12 Input unit 13 RAM
14 Display unit 15 Storage unit 151 Store service master storage unit 152 Program distribution information storage unit 153 Program data storage unit 16 Communication unit 17 Timekeeping unit 18 Bus 20 ECR
21 CPU
22 Input unit 23 RAM
24 display unit 25 storage unit 26 communication unit 27 timing unit 28 drawer 29a print unit 29b bus 100 store service information registration unit 101 store service master registration unit 102 program data registration unit 103 program distribution information registration unit 200 store service port control unit 201 telegram Control unit 202 Authentication control unit 203 Program distribution confirmation unit 204 Program distribution unit 205 Cryptographic control unit

Claims (7)

An information distribution device that distributes information to a plurality of terminal devices,
A discriminating means for discriminating a terminal device that needs immediate delivery of the information among the plurality of terminal devices when there is information to be distributed;
A first control unit that controls to distribute the information to be distributed first when the terminal device is powered on when it is determined by the determining unit that there is a terminal device that needs immediate distribution;
A second control means for controlling to distribute the information to be distributed after the information distribution by the first control means for a terminal device that does not require immediate distribution by the determination means;
An information distribution apparatus comprising: An information distribution device that distributes information to a plurality of terminal devices,
A discriminating means for discriminating a terminal device that needs immediate delivery of the information among the plurality of terminal devices when there is information to be distributed;
For a terminal device that requires immediate distribution, control means for controlling distribution of the information when processing is started at the terminal device;
An information distribution apparatus comprising: For terminal devices that do not require immediate distribution, second control means for controlling distribution of the information after information distribution by the control means;
The information distribution apparatus according to claim 2, further comprising: For the terminal device that does not require immediate distribution, second control means for controlling the distribution of the information upon termination of processing in the terminal device;
The information distribution apparatus according to claim 2, further comprising: The determining means determines a terminal device having information that needs immediate delivery among the plurality of terminal devices as a terminal device that needs immediate delivery.
The information distribution apparatus according to claim 1, wherein the information distribution apparatus is an information distribution apparatus. A program for controlling a computer of an information distribution apparatus that distributes information to a plurality of terminal devices,
The computer,
A discriminating means for discriminating a terminal device that needs immediate distribution of the information among the plurality of terminal devices when there is information to be distributed;
A first control unit that controls to distribute the information to be distributed first when the terminal device is powered on when it is determined that there is a terminal device that needs immediate distribution;
A second control means for controlling to distribute the information to be distributed after the information distribution by the first control means for a terminal device that does not require immediate distribution by the determination means;
A program designed to function as A program for controlling a computer of an information distribution apparatus that distributes information to a plurality of terminal devices,
The computer,
A discriminating means for discriminating a terminal device that needs immediate distribution of the information among the plurality of terminal devices when there is information to be distributed;
For a terminal device that requires immediate delivery, a control unit that controls delivery of information that requires immediate delivery at the start of processing in the terminal device;
A program designed to function as

Images