JP6525270B2 - Information distribution device and program - Google Patents

Description

  The present invention relates to an information delivery apparatus and program.

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

  For example, in Patent Document 1, when an application request is transmitted from a terminal to a server, the server device distributes application software to the terminal in the form of download, and data is transmitted using the application software received on the terminal A software distribution system has been described which allows for processing.

  Further, according to Patent Document 2, software is divided into a plurality of recombinable segment data and registered in a predetermined site, and a plurality of segment data is detected each time a user terminal is linked to the site. A technique has been described in which even large-volume data software can be transmitted without giving stress to the user by transmitting each of the above to the user terminal one by one.

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

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

  By the way, terminal devices such as ECR (sales data processing device) and payment terminals installed in stores differ in model for each store even in stores owned by the same company, and programs installed are different in each store There is a case. Further, even in the same store, there are cases where the terminal device model is different for each floor, and the programs installed for each floor are different. Moreover, even if it is a terminal device of the same model, a destination etc. differ with terminal devices, and the program mounted may differ.

  However, in the conventional program delivery technology, a data management apparatus such as a server only delivers a program in response to a request from a terminal, and a program installed like a terminal device installed in a store It has not been possible to update the programs of multiple terminal devices with different types of to be up-to-date.

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

An information distribution apparatus according to the present invention is an information distribution apparatus that distributes information to a terminal device, and controls distribution of predetermined information to the terminal device, and distributes the predetermined information to the terminal device. Control means for controlling such that the timing is limited when the state of the terminal device is in the first specific state at the start of processing and when the state of the terminal device is in the second specific state at the end of processing And, when there are a plurality of pieces of the predetermined information to be delivered to the terminal device, it is determined whether the plurality of pieces of information is the first information required for immediate delivery or the second information not required for immediate delivery And the control means is in the first specific state or in the second specific state with respect to the first information that requires immediate distribution, the terminal device serving as the distribution destination being the first specific state. or in the delivery regardless of Controlling the Migihitsuji, for unnecessary second information immediate delivery, and distributes when a and the second specific state so as to avoid delivery when the state of the terminal device is the first specific state controlled manner, characterized in that.
Further, a program according to the present invention is a program for controlling a computer of an information distribution apparatus that distributes information to a terminal device, and controls the computer to distribute predetermined information to the terminal device. At the same time, the delivery timing of the predetermined information to the terminal device is that the state of the terminal device is in the first specific state at the start of processing and the state of the terminal device is in the second specific state at the end of processing Sometimes, when there are a plurality of the predetermined information to be delivered to the terminal device, the control means for controlling so as to be limited, if the plurality of information is the first information required for the immediate delivery, immediately The control unit functions as a determination unit that determines whether the second information does not need to be distributed, and the control unit is configured to determine the state of the terminal device that is the distribution destination for the first information that requires immediate distribution. It is controlled to perform distribution regardless of whether it is the first specific state or the second specific state, and the state of the terminal device is the first specific state for the second information that does not require immediate distribution. And control to perform distribution when the second specific state is established.

According to the present invention, the network load and the system load can be suppressed by restricting the information distribution to the terminal device.

It is a block diagram showing an example of composition of a program delivery system in an embodiment of the present 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 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) FIG. 3 is a view showing an example of data storage of a program data storage unit of 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. FIG. 18 is a diagram showing an example of data storage of a program delivery information storage unit in the second embodiment. 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. FIG. FIG. 18 is a diagram showing an example of data storage of a program delivery information storage unit in the third embodiment. 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. FIG. 13 is a diagram showing an example of a configuration 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 showing a message interpretation process performed by the message control unit 201 of FIG. 17 in the fourth embodiment. 18 is a flowchart showing a program distribution process B executed by the program distribution unit 204 in FIG. 17 in the fourth embodiment. 18 is a flowchart showing program data encryption processing executed by the encryption control unit 205 in FIG. 17 in the fourth embodiment.

Embodiment 1
First, the first embodiment of the present invention will be described.
FIG. 1 shows an example of the configuration of a program distribution system 1 according to the first embodiment. As shown in FIG. 1, in the program delivery system 1, a data management apparatus 10 and an ECR (Electronic Cash Resistor) 20 (20A to 20D) as a terminal device are connected so as to be able to transmit and receive data via a communication network N. It is configured. The communication network N is constituted by, for example, a communication network such as WAN (Wide Area Network) or the Internet, but may include LAN (Local Area Network) etc. A telephone line, a private line, a mobile communication network, communication Satellite networks, CATV (Cable Television) circuits, Internet providers, etc. may be included. Moreover, although the number of ECR 20 is illustrated as four units of 20A to 20D here, it is not particularly limited.

The data management apparatus 10 stores program data of the latest version corresponding to each ECR 20 connected via the communication network N, and shows a program indicating the type of installed program and the latest version of the program for each ECR 20. A management code etc. is stored and managed, and in response to a request from each ECR 20, program delivery confirmation, program data delivery, etc. are performed.
The ECR 20 is provided in a store, and registration processing of merchandise transactions based on the operation of the operator (traded date and time, merchandise name, sales quantity of merchandise, sales amount data, registration processing of person in charge etc.), check processing, settlement of accounts It is a sales data processing device that performs processing, sales totaling in a store, and the like. For example, an electronic register or the like is applicable as the ECR 20.

Hereinafter, each apparatus which comprises the program delivery system 1 is demonstrated.
First, the data management device 10 will be described.
An example of the internal configuration of the data management device 10 is shown in FIG. As shown in FIG. 2, the data management apparatus 10 includes a central processing unit (CPU) 11, an input unit 12, a random access memory (RAM) 13, a display unit 14, a storage unit 15, and a communication unit 16. , And a timer unit 17, and each unit is connected via a bus 18 and configured.

  The CPU 11 centrally controls each part of the data management device 10. The CPU 11 expands a program designated from among 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 an example of a functional configuration realized by cooperation of the CPU 11 and various application programs stored in the storage unit 15. As shown in FIG. 3, a store service information registration unit 100 as a registration unit and a store service port control unit 200 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 delivery information registration unit 103.
Based on the input from the input unit 12, the store service master registration unit 101 registers, in the store service master storage unit 151, master information on the ECR 20 to be a program distribution target in the data management apparatus 10.
Program data registration unit 102 executes program data registration processing described later, and registers program data to be distributed to at least one of ECRs 20 and the attribute information thereof in program data storage unit 153 based on the input from input unit 12. .
The program delivery information registration unit 103 receives information (program delivery information) for performing delivery confirmation of the program for the ECR 20 in which the master information is registered when the store service master registration unit 101 registers the master information. It is registered in the program distribution information storage unit 152. When program data is registered by program data registration unit 102, program distribution information registration unit 103 registers program distribution information in program distribution information storage unit 152.

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 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 delivery confirmation unit 203 as delivery confirmation means executes program delivery confirmation processing described later, acquires program delivery information for the ECR 20 that is the request source of the program delivery confirmation from the program delivery information storage unit 152, and needs delivery of the program. It judges whether or not there is, and sends the result to the request source ECR 20.
The program distribution unit 204 as a distribution unit executes program distribution processing described later, reads out 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 including cursor keys, characters, number input keys, various function keys, and the like, and outputs to the CPU 11 an operation signal with which each key is pressed by the operator. Further, 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. In addition, the RAM 13 has a work area for storing various programs to be executed, data related to the various programs, and the like.

  The display unit 14 is configured by an LCD (Liquid Crystal Display), a CRT (Cathode Ray Tube), or the like, and performs screen display in accordance with a display control signal from the CPU 11.

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

An example of data storage of the store service master storage unit 151 is shown in FIG. The store service master storage unit 151 stores master information on each of the registered ECRs 20, and as shown in FIG. 4A, the "terminal device code" field, the "group code" field, the "company code""Field","storecode" 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 classification when 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 a terminal model of the ECR 20. The model code consists of the upper three digits, the major code uniquely assigned to the model, and the lower three digits and the minor code indicating the destination. The “connection classification” field stores a flag (“1” if connection is possible, “0” if not possible) indicating connection availability of the ECR 20.

FIG. 4B shows an example of data storage of the program delivery information storage unit 152. As shown in FIG. The program delivery information storage unit 152 stores program delivery information for each program installed in each ECR 20 to be a program delivery target, and as shown in FIG. 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 the terminal device code of the ECR 20 to which the program is to be distributed. 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 delivered.
The version of the program to be delivered 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 of 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, and 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 program data. The "program data" field stores program data.

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

The communication unit 16 is configured by a modem, a terminal adapter (TA), a router, a network card, and the like. The communication unit 16 exchanges data with an external device such as the communication network N to be connected.
The clock unit 17 incorporates a clock circuit, clocks the current time and the current date, and outputs the clock to the CPU 11.

Next, the configuration of the ECR 20 as a terminal device will be described.
FIG. 5 shows an example of the internal configuration 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 clock unit 27, a drawer 28, and a printing unit 29a. The respective units are connected via a bus 29b.

  The CPU 21, the RAM 23, and the communication unit 26 are the same as the configurations of the CPU 11, the RAM 13, and the communication unit 16 of the data management device 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 among the system program and various application programs stored in the storage unit 25 in the RAM 23 and executes various processing in cooperation with the program developed in the RAM 23.

  For example, the CPU 21 reads various application programs according to the operation of the input unit 22 by the operator, and cooperates with the read application programs to register goods transaction, check processing, settlement processing, sales totalization processing in the store Etc.

  Further, at the time of opening, that is, when the power key of the input unit 22 is operated and the power is turned on, the CPU 21 reads the opening process program and executes the opening process in cooperation with the read program. That is, the CPU 21 is connected to the data management apparatus 10 to transmit a program distribution confirmation request, and whether 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 it is necessary to update the program is included, a program distribution request is transmitted to the data management device 10 to acquire program data, and the program is obtained according to the acquired program data. Update (Install)

  Further, when the closing instruction is instructed by the input unit 22, the CPU 21 reads the closing processing program, and executes the closing processing (see FIG. 8) in cooperation with the read program.

  The input unit 22 includes a keyboard for cash register provided with a power key, a cursor key, characters, numeric input keys, various function keys and the like, and outputs an operation signal with which each key is pressed by the operator to the CPU 21. The display unit 24 is configured by an LCD or the like, and performs screen display in accordance with a display control signal from the CPU 21. The input unit 22 may be integrated with the display unit 24 to configure a touch panel. In addition, the input unit 22 may include a barcode reader, a barcode scanner, or the like that reads a barcode provided on a product.

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

The communication unit 26 exchanges data with an external device such as the data management device 10 on the communication network N.
The clock unit 27 incorporates a clock circuit, clocks the current time and the current date, and outputs the clock to the CPU 21.

  The drawer 28 is a drawer for storing cash such as coins and bills. The drawer 28 opens the drawer, for example, according to an instruction of the CPU 21.

  The printing unit 29a is, for example, a thermal printer, has roll paper for receipt and journal, 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 device 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 file of program data 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 the program data to be registered is stored and attribute information of the 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, program data to be registered is read out to the RAM 13, and the program data size is acquired (step S2).

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

  When the registration of the program data is completed, the program distribution information registration unit 103 executes the program distribution information registration process (step S4), and the 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 delivery information registration process, first, in the store service master storage unit 151, a record having a model code of program data registered in step S3 is retrieved, and the retrieved record is read into the RAM 13 (step S101). .

  Next, in the program delivery 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 out to the RAM in step S102 is changed to the program management code of the registered program data, and the program distribution information of the program distribution information storage unit 152 is updated with the changed contents (step S103), the process ends.

  When program data of the new version 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 program data of the new version should be delivered is automatically made. It can be updated.

(Closed process)
FIG. 8 shows a flow of closing processing executed by the CPU 21 of each ECR 20. The said process is performed when the instruction | indication of closing is input by the input part 22 at the time of the completion | finish of the work in a shop.
First, communication connection to the data management apparatus 10 is performed by the communication unit 26 (step S11). Next, printing of sales data of one day to a journal, storage of sales data of one day, and settlement processing such as reset are performed (step S12).

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

  Here, transmission of various requests from the ECR 20 to the data management apparatus 10 is performed by transmitting request data of a predetermined format. The request data has a header part and a data part. The header section contains information necessary for data communication between the ECR 20 and the data management apparatus 10. For example, the address on the communication network N of the destination (data management apparatus 10), the address on the communication network N of the transmission source, etc. Is included. In addition, encrypted information and the like for the data part may be included. The data section includes types of requests (for example, program distribution confirmation, program distribution, etc.), parameters to be 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 the ECR 20. The data portion of the program distribution confirmation request data includes the terminal device code of the ECR 20, the program identification code of each program stored in the storage unit 25, and the program management code. The data portion of the distribution request data includes a terminal device code of the ECR 20, a model code, a program identification code of a program requesting distribution, and a program management code.

  Similarly, when transmitting various responses from the data management device 10 to the ECR 20, response data of a predetermined format is transmitted. The response data has a header part and a data part. The header portion includes information and the like necessary when performing data communication between the ECR 20 and the data management device 10. In addition, encrypted information and the like for the data part may be included. In the data part, response contents (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 needs to be distributed)), a response to the program distribution request Program data etc. are included.

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

First, the delivery confirmation information corresponding to one program identification code is taken out from the response data (step S16), it is judged whether the delivery (update) of the program is necessary, and the delivery (update) of the program is necessary. If it is determined that there is (step S17; YES), the communication unit 26 transmits a program distribution request to the data management apparatus 10 (step S18). In the program distribution request, distribution request data is transmitted to the data management device 10. When the response data of the program distribution response from the data management apparatus 10, that is, the program data is received by the communication unit 26 (step S19), the program stored in the storage unit 25 is updated with the distributed program data (install (Step S20), and shifts to the processing of loop 1 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 attribute information of the program data, and the ECR 20 can recognize the program identification code of the program data and the program management code.

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

  When loop 1 processing for the number of programs (number of program identification codes) included in the received response data is completed (step S21), the communication unit 26 disconnects the connection with the data management apparatus 10 (step S22). The process ends.

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

  In the closing process and the opening process described above, the ECR 20 inquires of the data management apparatus 10 whether or not distribution (update) of the program is necessary at opening and closing, and when it is necessary, the distribution request of program data To update the program.

(Service provision processing)
FIG. 9 shows a flow of service provision processing executed by the store service port control unit 200 of the data management device 10. The said process is a process performed by the data management apparatus 10 side corresponding to the closing process in above-mentioned ECR20, and opening process.

  First, when the communication unit 16 receives a connection request from the ECR 20, the 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), and when request data is received (step S32; YES), the message control unit 201 performs message analysis processing of request data, The content of the requested process is identified (step S33).

  As a result of analysis by the message control unit 201, if 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 the authentication process executed by the authentication control unit 202 in step S35 of FIG.
In the authentication process, first, in the store service master storage unit 151, a record having a terminal device code included in the request data is searched for (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), the authentication NG to the ECR 20 connected via the communication unit 16 Is notified (step S205), and the process returns to step S32 of FIG.

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

  Referring back to FIG. 9, when 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 Program distribution confirmation processing shown in 11 is executed (step S36). The program distribution confirmation process and the program distribution process are executed only when the connected ECR 20 is determined as the authentication OK in the above-described authentication process.

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

  Next, the processing of loop 2 of steps S302 to S308 is repeatedly executed by 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 judged whether or not the record of program distribution information having the extracted program identification code exists in the RAM 13, and if it is judged that it does not exist (step S304; NO), the type of the program corresponding to the program identification code It is determined that program distribution is not necessary, and program distribution confirmation information indicating that program distribution of the program identification code is unnecessary is set in the response data (step S307), and the processing of loop 2 for the next program identification code is performed. Migrate to

  On the other hand, when 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 judged to be different from the program management code in the record having the program identification code read out to the RAM 13 in step S301, and if it is judged to be different (step S305; YES), distribution of the program is necessary. Program distribution confirmation information indicating that the program of the type corresponding to the program identification code needs to be distributed is set in the response data (step S306), and processing of loop 2 for the next program identification code is performed. Row.

  On the other hand, if it is determined that the program management code corresponding to the program identification code extracted from the request data is identical to the program management code in the record having the program identification code read out to the RAM 13 in step S301 (step S305; NO), it is determined that the program distribution of the type corresponding to the program identification code is not necessary, and program distribution confirmation information indicating that program distribution of the program identification code is unnecessary is set in the response data (step Step S307): Go to the processing of loop 2 for the next program identification code.

  When the process of loop 2 for all 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 process It transfers to step S32 of FIG.

  Referring back to FIG. 9, when it is determined that the content of the received request data is a program distribution request as a result of analysis by the message control unit 201 (step S34; program distribution request), the program distribution unit 204 displays it in FIG. Program distribution processing 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, program data storage unit 153 searches for program data having attribute information that matches the model code, program identification code, and program management code included in the request data, and the corresponding program data is read out. (Step S401).

  Next, the read program data is set as response data, and is 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), communication with the ECR 20 is disconnected by the communication unit 16. (Step S38), the process ends.

As described above, in the program delivery system 1, the program delivery information storage unit is a program management code indicating the type of program installed in the ECR 20 that is the program delivery target by the data management apparatus 10 and the latest version to be delivered. When stored in 152 and each ECR 20 transmits a program distribution confirmation request at opening and closing, the version of each program installed in the sender ECR 20 is compared with the information indicating the latest version And if different, respond to the connected ECR 20 that delivery is required. In the ECR 20, when the data management device 10 responds that it is necessary to distribute the program, the ECR 20 makes a distribution request of the program corresponding to the data management device 10 and acquires and updates 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.

Second Embodiment
The second embodiment of the present invention will be described below.
In the first embodiment, when the program data registration unit 102 registers a new version of program data in the program data storage unit 153, the program distribution information registration unit 103 performs program distribution information registration processing, and before version upgrade. The program management code of all program distribution information of ECR 20 loaded with the same type of program was changed to a program management code indicating a new version. However, if the ECR 20 establishment and closure concentrate on a predetermined time zone, changing the program management code of all the ECRs 20 at one time concentrates program distribution requests to the data management apparatus 10, causing network load and so on. System load increases.
Therefore, in the second embodiment, in order to prevent concentration of program distribution requests to the data management apparatus 10, the network load and the system load are suppressed by restricting the update target of the program distribution information performed at one time.

  FIG. 13 shows an example of data storage of the program delivery information storage unit 152 in the second embodiment. As shown in FIG. 13, the program delivery information storage unit 152 in the present embodiment has a “delivery result” field in addition to the fields described using FIG. 4B in the first embodiment. The "delivery result" field stores delivery result information (non-delivery flag "0", delivery completion flag "1") indicating that the program data has been delivered after updating the program data.

  The other configuration in the second embodiment is the same as that described in the first embodiment, so the description will be omitted.

Next, the operation in the second embodiment will be described.
The second embodiment differs from the first embodiment in program distribution processing and program distribution information registration processing executed in step S4 (see FIG. 6) of program data registration processing.

  In the program delivery process in the second embodiment, after the process of step S402 described in FIG. 12, the terminal equipment code of the ECR 20 that is the delivery target of program data and the program identification code of the delivered program in the program delivery information storage unit 152. "1" is set in the "delivery result" field of the record having "1".

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

  In program distribution information registration process B, first, in 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. 6 is searched, and the searched record is RAM 13 Is read out (step S501).

  Next, in the program delivery 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 into the RAM 13 ( Step S502).

  Next, the record read out to the RAM 13 in step S502 is divided into groups for each predetermined range of group code (step S503), and the group code belongs to a predetermined range of (for example, 001 to 100) groups of records. The program management code is changed to the program management code of the newly registered program data, the delivery result field is initialized to "0", and the information in the program delivery information storage unit 152 is updated with the changed contents. Step S504. Further, the date and time information output by the timekeeping unit 17 at the time of updating is stored in the RAM 13 as the updating date and time (step S505).

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

  First, a sleep state is set for a predetermined time (for example, one hour) (step S507), and then it is determined whether or not a predetermined period (for example, three days) has elapsed from the update of 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 to be updated last time (step S508; NO), the record of the program distribution information having the group code to be updated last time is the program distribution It is determined whether or not the record having “1” in the “delivery record” field acquired from the information storage unit 152 exceeds a predetermined ratio (for example, 80%) (step S510). If it is determined that the record of which the distribution result flag is “1” exceeds the predetermined ratio (step S510; YES), the process proceeds to step S511. If it is determined that the record of the "delivery record" field is "1" does not exceed the predetermined ratio (step S510; NO), the processing of the next loop 3 is executed.

  In step S511, of the records read out to the RAM 13 in step S502, the program management code of the record having the group code corresponding to the next group to be updated is the program management code of the program data newly registered. Further, the distribution result field is initialized to "0", and the information of the program distribution information storage unit 152 is updated with the changed content. Further, the update date and time stored in the RAM 13 is updated by the date and time information output by the clock unit 17 at the time of updating 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), the process ends.

  As described above, in the second embodiment, the update target of the corresponding program delivery information when the program data of the new version is registered in the program data storage unit 153 in the data management apparatus 10 has a predetermined group code range. The program distribution information of the next group is updated after a predetermined period of time has passed after updating, or when the program distribution record of the updated group exceeds a predetermined ratio. As described above, since the update of the program distribution information is performed by shifting the time for each group, concentration of the program distribution request to the data management apparatus 10 can be prevented, and the network load and the system load can be suppressed.

Third Embodiment
The third embodiment of the present invention will be described below.
In the first and second embodiments, the ECR 20 makes a distribution confirmation request for the program that is connected to the data management apparatus 10 at the time of opening and closing and is installed by the ECR 20, and if necessary, the program data of the corresponding program. It has been described that delivery is requested and the program is updated. By configuring in this manner, all programs of the ECR 20 can be always updated. However, since it takes time to download and install 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 opening is distributed, and in the other cases, the program is distributed at the time of closing.

  FIG. 15 shows an example of data storage of the program delivery information storage unit 152 in the third embodiment. As shown in FIG. 15, the program delivery information storage unit 152 in the present embodiment has a “delivery timing” field in addition to the fields described using FIG. 4B in the first embodiment. The "delivery timing" field stores delivery timing information ("immediate" for programs to be delivered immediately, "normal" for programs that do not need to be delivered immediately).

  The other configuration in the third embodiment is the same as that described in the first embodiment, so the description will be 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 the opening process performed by the ECR 20 indicates whether the process is the closing process or the opening process. It differs from Embodiment 1 in that information is included.

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

  In the program data registration process according to the third embodiment, in step S1 of FIG. 6, it is determined whether the program data to be registered requires immediate distribution together with the model code of the program data to be registered, the program identification code and the program confirmation code. Information is entered. In the case of immediate control, for example, the case where it is necessary to update the program immediately due to a serious failure or the like is applicable. Then, 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 distributed timing The program delivery information storage unit 152 is updated with the contents added, changed, and added to the “delivery timing” field as information.

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

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

  Next, the processing of loop 4 of steps S602 to S609 is repeatedly executed by 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 judged whether or not the record of program distribution information having the extracted program identification code exists in the RAM 13, and if it is judged that it does not exist (step S604; NO), the type of the program corresponding to the program identification code It is determined that delivery of the program is not necessary, and delivery confirmation information indicating that program delivery of the program identification code is unnecessary is set in the response data (step S608), and the next program identification code included in the request data is Transfer to loop 4 processing.

  On the other hand, when it is determined that the record of program delivery information having the program identification code extracted in step S603 exists in the RAM 13 (step S604; YES), the program management code corresponding to the program identification code extracted from the request data Is judged to be different from (not identical to) the program management code of the record having the program identification code read out to the RAM 13 in step S601 (step S605; NO), It is determined that delivery of a program of the type corresponding to the program identification code is not necessary, and delivery confirmation information indicating that program delivery of the program identification code is unnecessary is set in the response data (step S608). Next program 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 out to the RAM 13 in step S601 (step S605; YES) According to the request data and the delivery timing information of the record including the program identification code read out to the RAM 13 in step S601, either the ECR 20 connected is closed or the program requires immediate delivery. It is determined whether or not it corresponds to (step S606).

  If it is determined that the connected ECR 20 is either closed or a program that requires immediate delivery (step S 606; YES), it is determined that the program needs to be delivered, Delivery confirmation information indicating that the program of the type corresponding to the program identification code needs to be delivered is set in the response data (step S 607), and the process proceeds to loop 4 processing for the next program identification code included in the request data Do.

  If it is determined that the connected ECR 20 is neither closed nor a program requiring immediate delivery (step S606; NO), the type of program corresponding to the program identification code It is determined that delivery is not necessary, and delivery confirmation information indicating that program delivery 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. Transfer to processing of

  When the processing of loop 4 for all 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 It transfers to step S32 of FIG.

  As described above, in the program distribution confirmation process of the third embodiment, the distribution timing of the program for which the ECR 20 made the distribution confirmation request at the time of closing or the distribution confirmation request is immediately set in the program distribution information storage unit 152. If it is, delivery confirmation information indicating that delivery is necessary is set in the response data. Therefore, at the time of opening, only the program that needs to be updated is immediately updated, and at the other time, the update is performed at the time of closing, so it is possible to update the program without impairing the user's convenience. Become.

Embodiment 4
The fourth embodiment 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 an example of a functional configuration realized by cooperation of the CPU 11 of the data management apparatus 10 in 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 is configured to include an encryption control unit 205. The encryption control unit 205 performs decryption of request data transmitted from the ECR 20, encryption of program data to be transmitted to the ECR 20, and the like.

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

  Further, the ECR 20 can set an encryption strength when performing data communication with the data management device 10 by the operation of the input unit 22. Specifically, it is possible to set an encryption method of the encryption strength desired by the user from RSA (Rivest Shamir Adleman), T-DES (Triple DES), DES (Data Encryption Standard), and plain text. There is. In the ECR 20, an encryption processing program for encrypting and decrypting data is stored in each encryption method of RSA, T-DES and DES, and the data encryption is performed by the cooperation of the CPU 21 and the encryption processing program, It is possible to perform decryption.

  The other configuration in the fourth embodiment is the same as that described in the first embodiment, so the description will be omitted.

Next, the operation in the fourth embodiment will be described.
In the fourth embodiment, when the ECR 20 performs closing processing and opening processing and makes a program distribution request and program transmission request to the data management apparatus 10, the encryption processing program of the encryption method set in advance is read, and the request is made. After the data portion of the data is encrypted according to a preset encryption method, the data portion is transmitted to the data management apparatus 10 via the communication unit 26.

  In the data management device 10, when the request from the ECR 20 is received in the service providing process shown in FIG. 9, the message control process shown in FIG. 18 is executed by the message control unit 201 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). If 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 and the data portion of the request data uses the RSA algorithm. The decryption is performed (step S703), and the process proceeds to step S706.

  On the other hand, when it is determined that the encryption method of 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 use T-DES for the data part of the message. The algorithm is decoded (step S704), and the process proceeds to step S706.

  On the other hand, if 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 using the encryption key of the request source ECR 20 by the DES algorithm ( The process proceeds to step S706).

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

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

  In the present embodiment, when the request specified in step S706 is program distribution processing, the program distribution processing shown in FIG. 19 in step S4 of FIG. 6 (referred to as program distribution processing B to distinguish from the first embodiment) Is executed.

  In program distribution processing B, first, program data storage unit 153 searches for program data having attribute information that matches the model code, program identification code, and program management code included in the request data, and the corresponding program data is It is read out (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 system of request data received from the ECR 20 is determined. If it is determined that the encryption method of request data is RSA (step S901; RSA), the program data read out in step S801 of FIG. 19 by the encryption control unit 205 is RSA using the encryption key of the request source ECR 20. 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 request data is T-DES (step S901; T-DES), the program data read out in step S801 by the encryption control unit 205 is the encryption key of the ECR 20 of the request source. It is encrypted using the T-DES algorithm (step S 903), and the process proceeds to step S 803 in FIG.

  On the other hand, when it is determined that the encryption method of the request data is DES (step S 901; DES), the program data read out in step S 801 by the encryption control unit 205 uses the encryption key of the request source ECR 20 to execute DES algorithm. Is encrypted (step S904), and the process proceeds to step S803 in FIG.

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

  In step S803 in FIG. 19, plaintext or encrypted program data is set as response data, and is 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 program data with an encryption strength corresponding to the ECR 20 of the distribution destination, and transmits the encrypted program data. Therefore, it is possible to encrypt and transmit program data by changing the encryption strength according to the level of security required for each ECR 20, and efficiently program data while balancing the load on the encryption processing and security. It is possible to deliver the

In the fourth embodiment, when request data is encrypted and transmitted by the encryption method set in each ECR 20, the data management apparatus 10 identifies the encryption method of the request data, and encrypts the program data by the encryption method. Although transmission is made to the request source ECR 20 and the program code is to be encrypted by the encryption method according to the ECR 20, the present invention is not limited to this.
For example, an encryption method is determined in advance for each model code of ECR 20, and data management apparatus 10 identifies the model code of ECR 20 of the request source with reference to store service master storage unit 151, and responds to the identified model code. The program data to be distributed may be encrypted according to the encryption method. In this way, program data can be encrypted and transmitted with the encryption strength according to the security level required for each model of ECR 20, and the balance between the load on encryption processing and the security can be achieved, Program data can be distributed efficiently.
Further, for example, an encryption method is determined in advance 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. It is also good. In this way, the program data can be encrypted and transmitted with the encryption strength according to the security level required for each program, and the balance between the load on encryption processing and the security can be efficiently achieved. It becomes possible to deliver program data.

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, although the case where the terminal device is ECR 20 has been described as an example in the above embodiment, the present invention is not limited to this. For example, the terminal device reads card information of a customer's credit card at a store and includes the card information The payment data and the payment approval request may be transmitted to the card company's device as a payment terminal, and the data management device 10 may be configured to deliver the program to the payment terminal.

  In the above embodiment, when program data of the latest version of a certain type of program is newly registered, the program management code for all the ECRs 20 loaded with the program stored in the program distribution information storage unit 152. 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 a monitoring program at the time of failure occurrence to the ECR 20 in which a 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 the encryption key updated in the distributed program May be embedded and delivered. This makes it possible to enhance the security of communication between the data management device 10 and the ECR 20.

  In addition, the detailed configuration and the detailed operation of each device constituting the program delivery system 1 can be appropriately changed without departing from the scope of the invention.

1 Program Delivery System 10 Data Management Device 11 CPU
12 Input section 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 Timing Unit 18 Bus 20 ECR
21 CPU
22 Input 23 RAM
24 display unit 25 storage unit 26 communication unit 27 clock 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 delivery information registration unit 200 store service port control unit 201 message Control unit 202 Authentication control unit 203 Program distribution confirmation unit 204 Program distribution unit 205 Encryption control unit

Claims (3)

An information delivery apparatus for delivering information to a terminal device, the information delivery apparatus comprising:
Distribution control of predetermined information to the terminal device, and distribution timing of the predetermined information to the terminal device, when the state of the terminal device is in a first specific state at the start of processing, and the terminal device Control means for controlling so as to be limited when the second specific state at the end of the process is present;
When there are a plurality of pieces of the predetermined information to be distributed to the terminal device, it is determined whether the plurality of pieces of information is the first information required for immediate distribution or the second information not required for immediate distribution Means,
Equipped with
It said control means for said first information required for immediate delivery, to perform delivery regardless of whether the destination to become terminal equipment state is the second specific state or a first specific state Control is performed, and the second information not requiring immediate distribution is controlled so as to avoid distribution when the state of the terminal device is in the first specific state and to perform distribution when in the second specific state Do,
An information delivery apparatus characterized by The control means controls, among a plurality of terminal devices, the delivery of the first information to the delivery destination of the first information that requires immediate delivery.
The information delivery apparatus according to claim 1, A program for controlling a computer of an information distribution apparatus for distributing information to a terminal device, comprising:
The computer,
Distribution control of predetermined information to the terminal device, and distribution timing of the predetermined information to the terminal device, when the state of the terminal device is in a first specific state at the start of processing, and the terminal device Control means for controlling so as to be limited when the second specific state at the end of the process is present,
When there are a plurality of pieces of the predetermined information to be distributed to the terminal device, it is determined whether the plurality of pieces of information is the first information required for immediate distribution or the second information not required for immediate distribution means,
To act as
The control means distributes the first information that requires immediate distribution regardless of whether the state of the terminal device that is the distribution destination is the first specific state or the second specific state. Control is performed, and the second information not requiring immediate distribution is controlled so as to avoid distribution when the state of the terminal device is in the first specific state and to perform distribution when in the second specific state Do,
A program characterized by

Images