Terminal management system, terminal management device, and its control program

Abstract

To provide a terminal management system, a terminal management device, and their control program capable of restricting the use of a purchase service including registration operations for purchased products and accounting processing operations by a mobile terminal in which an abnormal state has occurred.SOLUTION: In one embodiment, a terminal management device includes an acquisition unit, a detection unit, and a restriction unit. The acquisition unit acquires status information indicating an operating state of a mobile terminal operated by a customer and used for product purchase processing. The detection unit detects an abnormal state of the mobile terminal based on the status information acquired by the acquisition unit. The restriction unit restricts the purchase processing by the mobile terminal according to the number of abnormal states of the mobile terminal detected by the detection unit.SELECTED DRAWING: Figure 12

Description

[Technical field]

[0001] An embodiment of the present invention relates to a terminal management system, a terminal management device, and a control program therefor. [Background technology]

[0002] In recent years, various store systems have been devised in which customers can use a mobile terminal (such as a smartphone or a cart terminal) to register purchased items and make payments by themselves when shopping around the sales floor of a store. In such store systems, customers using mobile terminals, that is, users, operate the mobile terminals to register purchased items and make payments by themselves. This can lead to situations in which a user stops using the mobile terminal in the middle of registering purchased items and takes the purchased items out of the store without completing the payment (payment). There is a demand for a mechanism that can restrict the use of purchasing services including the registration and payment operations of purchased items by the mobile terminal (hereinafter, in this specification, may be simply referred to as "purchase processing by mobile terminal" or "transaction by mobile terminal") for a user who operates a mobile terminal in such an abnormal state. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2013-186875 A Summary of the Invention [Problem to be solved by the invention]

[0004] The problem that the embodiments of the present invention aim to solve is to provide a terminal management system, a terminal management device, and a control program thereof that can restrict the use of purchasing services, including operations for registering purchased items and operations for accounting, etc., by a mobile terminal in which an abnormal state has occurred. [Means for solving the problem]

[0005] In one embodiment, the terminal management device includes an acquisition unit, a detection unit, and a restriction unit. An output unit; The acquiring unit acquires status information indicating the operating state of a mobile terminal operated by a customer and used for purchasing a product. The detecting unit detects an abnormal state of the mobile terminal based on the status information acquired by the acquiring unit. The restricting unit restricts the purchasing process by the mobile terminal according to the number of times the abnormal state of the mobile terminal is detected by the detecting unit. The output unit outputs a list of abnormal conditions, each of which describes the date of occurrence of the abnormality and the content of the abnormality, to the mobile terminal when the restriction unit restricts the purchasing process by the mobile terminal. [Brief description of the drawings]

[0006] [Figure 1] 1 is a block diagram showing a schematic configuration of a terminal management system according to a first embodiment. [Diagram 2] FIG. 2 is a block diagram showing the main circuit configuration of a mobile terminal. [Diagram 3] FIG. 2 is a block diagram showing the main circuit configuration of a virtual POS server. [Figure 4] FIG. 4 is a schematic diagram showing an example of a purchase registration list. [Diagram 5] FIG. 13 is a schematic diagram showing an example of a time-series buffer. [Figure 6] FIG. 4 is a schematic diagram showing the data structure of an abnormal condition data record stored in an abnormal condition file. [Figure 7] FIG. 2 is a block diagram showing a main circuit configuration of a connection management server. [Figure 8] FIG. 4 is a schematic diagram showing an example of a connection management table. [Figure 9] FIG. 2 is a block diagram showing the main circuit configuration of the accounting machine. [Figure 10] 4 is a flowchart showing a control procedure of a main part of a processor in a mobile terminal. [Figure 11] 4 is a flowchart showing a control procedure of a main part of a processor in a mobile terminal. [Figure 12] 4 is a flowchart showing a control procedure of a main part of a processor in the virtual POS server. [Figure 13] 4 is a flowchart showing a control procedure of a main part of a processor in the virtual POS server. [Figure 14] 4 is a flowchart showing a control procedure of a main part of a processor in the virtual POS server. [Figure 15] 4 is a flowchart showing a main control procedure of a processor in the accounting machine. [Figure 16] 4 is a flowchart showing a control procedure of a main part of a processor in the virtual POS server. [Figure 17] 4 is a flowchart showing a control procedure of a main part of a processor in the virtual POS server. [Figure 18] 11 is a flowchart showing a control procedure of a main part of a processor in the connection management server. [Figure 19] 4 is a flowchart showing a control procedure of a main part of a processor in the virtual POS server. [Figure 20] FIG. 13 is a diagram showing an example of a usage restriction screen. [Figure 21] FIG. 13 is a diagram showing an example of a first abnormal condition list screen. [Figure 22] FIG. 11 is a block diagram showing a schematic configuration of a terminal management system according to a second embodiment. [Figure 23] FIG. 11 is a block diagram showing a main circuit configuration of a tallying server in the second embodiment. [Figure 24] FIG. 11 is a schematic diagram showing an example of an aggregated data record stored in an aggregated data file in the second embodiment. [Diagram 25] 11 is a flowchart showing a control procedure of a main part of a processor in the tallying server in the second embodiment. [Figure 26] 10 is a flowchart showing a control procedure of a main part of a processor in a virtual POS server in the second embodiment. [Figure 27] 11 is a flowchart showing a control procedure of a main part of a processor in the tallying server in the second embodiment. [Figure 28] FIG. 11 is a diagram showing an example of a second abnormal condition list screen in the second embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0007] Each embodiment will be described below with reference to the drawings.

[0008] (First embodiment) FIG. 1 is a block diagram showing a schematic configuration of a terminal management system SYA according to the first embodiment. The terminal management system SYA includes a store server 10, a virtual POS (Point Of Sales) server 20, a connection management server 30, a payment machine 40, an access point 50, and a mobile terminal 60. The store server 10, the virtual POS server 20, the connection management server 30, the payment machine 40, and the access point 50 are connected to a communication network 1 such as a LAN (Local Area Network). The mobile terminal 60 is equipped with a wireless unit 66 (see FIG. 2). The mobile terminal 60 performs wireless communication with the access point 50. The access point 50 relays communication between each device connected to the communication network 1, i.e., the store server 10, the virtual POS server 20, the connection management server 30, and the payment machine 40, and the mobile terminal 60. Although only one access point 50 is shown in FIG. 1, there may be two or more access points 50 depending on the size of the store, etc.

[0009] The store server 10 manages a product database. The product database stores product data records that record data on products sold in the store. The product data records include items such as product code, product name, and price. The product code is product identification information set for each product to identify the product individually. Each product is usually affixed with a barcode that represents the product code.

[0010] The virtual POS server 20 cooperates with the mobile terminal 60 to operate the mobile terminal 60 so as to realize the functions of a POS terminal. The virtual POS server 20 is an example of a terminal management device.

[0011] The connection management server 30 manages the communication connection state of the mobile terminal 60 that communicates with the terminal management system SYA. For example, the connection management server 30 manages whether the mobile terminal 60 is connected to a wireless LAN or the like in a store. The wireless LAN is, for example, compliant with the Wi-Fi (registered trademark) standard.

[0012] The payment machine 40 is a device that enables a store clerk or a user to process the payment for the products that a user wishes to purchase, so-called purchased products. There is no particular limit on the number of payment machines 40. The payment machines 40 include, for example, manned payment machines in which a store clerk performs operations related to the payment for purchased products, so-called manned payment machines 401, and self-service payment machines in which the user performs operations related to the payment for purchased products, so-called self-service payment machines 402. There is no particular limit on the number of manned payment machines 401. There is no particular limit on the number of self-service payment machines 402.

[0013] The mobile terminal 60 is a device that enables, for example, a user who is a customer operating the mobile terminal 60 to input data related to the registration of purchased items by himself / herself. The mobile terminal 60 is a device used for purchase processing including the registration operation of purchased items related to one transaction or the accounting processing operation. The mobile terminal 60 is a portable communication terminal. The mobile terminal 60 is, for example, a smartphone or tablet terminal equipped with a digital camera that is personally owned by a user. In a store, the mobile terminal 60 may be lent to a user who is, for example, a shopper. The mobile terminal 60 may be installed in a shopping cart, for example. The mobile terminal 60 has hardware for reading at least data codes such as barcodes and two-dimensional codes.

[0014] Fig. 2 is a block diagram showing the main circuit configuration of the mobile terminal 60. As shown in Fig. 2, the mobile terminal 60 includes a processor 61, an internal memory 62, an external memory 63, a touch panel 64, a camera 65, a wireless unit 66, and a system transmission path 67. The system transmission path 67 includes an address bus, a data bus, a control signal line, and the like. The mobile terminal 60 connects the processor 61, the internal memory 62, the external memory 63, the touch panel 64, the camera 65, and the wireless unit 66 to the system transmission path 67. The processor 61, the internal memory 62, and the external memory 63 are connected by the system transmission path 67 to configure a computer that performs information processing for controlling the mobile terminal 60.

[0015] The processor 61 corresponds to the central part of the computer. The processor 61 controls each part to realize various functions of the mobile terminal 60 according to an operating system or an application program. The processor 61 is, for example, a CPU (Central Processing Unit).

[0016] The built-in memory 62 corresponds to the main storage portion of the computer. The built-in memory 62 includes a non-volatile memory area and a volatile memory area. The built-in memory 62 stores an operating system or an application program in the non-volatile memory area. The built-in memory 62 stores data required for the processor 61 to execute processes for controlling each part in the volatile memory area. The built-in memory 62 also uses the volatile memory area as a work area where data is appropriately rewritten by the processor 61. The non-volatile memory area is, for example, a ROM (Read Only Memory). The volatile memory area is, for example, a RAM (Random Access Memory).

[0017] The external memory 63 corresponds to an auxiliary storage portion of the computer. For example, an SD memory card, a USB (universal serial bus) memory, etc. can be the external memory 63. The external memory 63 stores data used by the processor 61 when performing various processes, or data created by the processes in the processor 61. The external memory 63 may also store the above-mentioned application programs.

[0018] The application programs stored in the external memory 63 include a shopping application program. Hereinafter, the shopping application program is abbreviated as a shopping application. The shopping application is an application executed when shopping at a store in which the terminal management system SYA is installed. The method of installing the shopping application in the external memory 63 is not particularly limited. The control program can be recorded on a removable recording medium, or the control program can be distributed by communication via a network and installed in the external memory 63. The recording medium may be in any form, such as a CD-ROM or a memory card, as long as it can store a program and is readable by the device. The shopping application may be installed in the built-in memory 62 instead of the external memory 63.

[0019] The touch panel 64 is a device that combines an input device and a display device of the mobile terminal 60. The touch panel 64 detects a touch position on a displayed image, and outputs the touch position information to the processor 61.

[0020] The camera 65 is an imaging device built into the mobile terminal 60. The camera 65 operates as a still or video capturing device or as a scanning device for data codes such as bar codes and two-dimensional codes, depending on a shopping app installed in the mobile terminal 60.

[0021] The wireless unit 66 wirelessly communicates data with the access point 50 in accordance with a wireless communication protocol.

[0022] The mobile terminal 60 stores an application ID in the external memory 63. The application ID is a unique code assigned to each shopping application installed in the mobile terminal 60 in order to identify the shopping application.

[0023] 3 is a block diagram showing the main circuit configuration of the virtual POS server 20. The virtual POS server 20 includes a processor 21, a main memory 22, an auxiliary storage device 23, a clock 24, a communication interface 25, and a system transmission path 26. The system transmission path 26 includes an address bus, a data bus, a control signal line, and the like. The virtual POS server 20 connects the processor 21, the main memory 22, the auxiliary storage device 23, the clock 24, and the communication interface 25 to the system transmission path 26. In the virtual POS server 20, a computer is configured by the processor 21, the main memory 22, the auxiliary storage device 23, and the system transmission path 26 that connects them.

[0024] The processor 21 corresponds to the central part of the computer. The processor 21 controls each part to realize various functions of the virtual POS server 20 according to an operating system or an application program. The processor 21 is, for example, a CPU.

[0025] The main memory 22 corresponds to the main storage portion of the computer. The main memory 22 includes a nonvolatile memory area and a volatile memory area. The main memory 22 stores an operating system or an application program in the nonvolatile memory area. The main memory 22 may store data required for the processor 21 to execute processes for controlling each part in the nonvolatile or volatile memory area. The main memory 22 uses the volatile memory area as a work area where data is appropriately rewritten by the processor 21. The nonvolatile memory area is, for example, a ROM. The volatile memory area is, for example, a RAM.

[0026] The auxiliary storage device 23 corresponds to the auxiliary storage portion of the computer. For example, an EEPROM (registered trademark) (Electric Erasable Programmable Read-Only Memory), a HDD (Hard Disc Drive), or an SSD (Solid State Drive) can be the auxiliary storage device 23. The auxiliary storage device 23 stores data used by the processor 21 in performing various processes, or data created by the processes in the processor 21. The auxiliary storage device 23 may also store the application programs.

[0027] The clock 24 functions as a time information source for the virtual POS server 20. The processor 21 keeps track of the current date and time based on the time information kept by the clock 24.

[0028] The communication interface 25 is connected to the communication network 1. The communication interface 25 performs data communication with other devices connected via the communication network 1 in accordance with a communication protocol.

[0029] The virtual POS server 20 configured as above uses a part of the volatile memory area of ​​the main memory 22 as a purchase registration list 221 (see FIG. 4). The virtual POS server 20 can form multiple purchase registration lists 221 in this area. Note that the storage destination of the purchase registration list 221 is not limited to the main memory 22. The purchase registration list 221 may also be stored in the auxiliary storage device 23.

[0030] FIG. 4 is a schematic diagram showing an example of the purchase registration list 221. As shown in FIG. 4, the purchase registration list 221 has areas for writing an application ID, purchased product data 2211, a total amount, and an accounting code. The purchased product data 2211 includes the product code, product name, price, purchase number, purchase amount, etc. of the purchased product purchased by the user. The purchase number is the purchase number of the product identified by the product code, and the purchase amount is the total price based on the purchase number. The total amount is the total purchase amount included in the purchased product data 2211. The accounting code will be described later. The purchase registration list 221 is created in association with the application ID. It should be noted that the purchase registration list 221 is not limited to the items in FIG. 4.

[0031] Furthermore, the virtual POS server 20 uses a part of the storage area of ​​the auxiliary storage device 23 as an area for a time-series buffer 231 (see FIG. 5) and an abnormal state file 232. In this area, the time-series buffer 231 having the data structure shown in FIG. 5 is formed as many times as the number of mobile terminals 60 that use the terminal management system SYA in the store. Note that the storage destination of the time-series buffer 231 and the abnormal state file 232 is not limited to the auxiliary storage device 23. The time-series buffer 231 and the abnormal state file 232 may be stored in a part of the volatile memory area of ​​the main memory 22.

[0032] FIG. 5 is a schematic diagram showing an example of the time-series buffer 231. As shown in FIG. 5, the time-series buffer 231 has an area for writing the status ST in the order of the earliest current date and time DT for each application ID. The status ST is information indicating the operation state of the mobile terminal 60. The status ST includes "entering the store", "registering", "checkout", "checkout completed", and "leaving the store". "Entering the store" is, for example, a state in which an entry operation to enter a store has been performed. When the user reads the store entry data code prepared at the entrance of the store with the camera 65, the store entry operation is performed, and the status ST becomes "entering the store". The store entry data code is setting information specific to the store or the business entity that operates the store, coded in a predetermined two-dimensional code system. "Registering" is, for example, a state in which the user is accepting a registration operation of a purchased item by the user himself. When the first purchased item is registered, the status ST becomes "registering". Thereafter, the status ST maintains "registering" until a transition to checkout is declared. "Checkout" is, for example, a state from when the transition to checkout is declared until the checkout operation is completed. "Checkout completed" is, for example, a state in which the checkout operation for the purchased item is completed. "Leaving the store" is, for example, a state in which the store exit operation is performed to leave the store. When the user reads the store exit data code prepared at the store exit with the camera 65, the store exit operation is performed and the status ST becomes "Leaving the store". The store exit data code is a code of setting information specific to the store or the business entity that operates the store, coded in a predetermined two-dimensional code system. Usually, the status ST is written in the time-series buffer 231 in the order of "entering the store", "registering", "checkout", "checkout completed" and "leaving the store". Note that the operation of changing the status ST to "entering the store", "registering", "checkout", "checkout completed" or "leaving the store" is not limited to the above-mentioned operation. Furthermore, the status ST is not limited to "entering the store", "registering", "checkout", "checkout completed" and "leaving the store".

[0033] FIG. 6 is a schematic diagram showing the data structure of the abnormal state data record 2321 stored in the abnormal state file 232. As shown in FIG. 6, the abnormal state data record 2321 stores abnormal state data generated for each application ID. The abnormal state data record 2321 includes items such as an abnormality occurrence date, an abnormality content, and an invalid flag. The abnormality occurrence date is the date on which an abnormal state occurred. An abnormal state is, for example, a state in which a user is performing a purchase product registration operation at a store but the checkout process operation is not completed, or a state in which the mobile terminal 60 that was connected to the wireless LAN in the store during the purchase product registration operation becomes disconnected from the wireless LAN. The abnormality content is the content of the abnormal state. The abnormality content is, for example, "unpaid", "disconnected without payment", etc. The invalid flag is flag data for setting whether or not an abnormal state that occurred on the abnormality occurrence date is invalid. In this embodiment, if the abnormality occurrence date is outside a certain period set in advance, the invalid flag in the same row as the abnormality occurrence date is set to "1". The fixed period is, for example, three months from January 1, 2021 to March 31, 2021, or six months from January 1, 2021 to June 30, 2021. The invalid flag is in the initial state of "0" during the fixed period, and is set to "1" outside the fixed period. When the invalid flag is set to "1", all items in the same row as the invalid flag are invalidated. The abnormality occurrence date, abnormality content, and invalid flag are hereinafter referred to as abnormal state data. The abnormal state data record 2321 is an example of information related to the abnormal state of the mobile terminal 60. Note that the abnormal state data record 2321 is not limited to the items in FIG. 6. In addition, how the fixed period is set is arbitrary. The fixed period may be a fixed value in the virtual POS server 20, or may be changeable to a desired value by the store that manages the virtual POS server 20.

[0034] The processor 21 has functions as an acquisition unit 211, a detection unit 212, a restriction unit 213, and an output unit 214. The acquisition unit 211 has a function of acquiring status information indicating the operation state of a mobile terminal 60 operated by a customer and used for product purchasing processing. The acquisition unit 211 can be referred to as an acquisition means.

[0035] The detection unit 212 has a function of detecting an abnormal state of the mobile terminal 60 based on the status information acquired by the acquisition unit 211. The detection unit 212 can be rephrased as a detection means.

[0036] The limiting unit 213 is a function that limits purchasing processing by the mobile terminal 60 according to the number of times the abnormal state of the mobile terminal 60 has been detected by the detecting unit 212. The limiting unit 213 can be referred to as a limiting means.

[0037] The output unit 214 has the following two functions. The first function is to output a message to the mobile terminal 60 when the limiting unit 213 has limited the purchasing process by the mobile terminal 60. The second function is to output a list of abnormal states of the mobile terminal 60 detected by the detecting unit 212 to the mobile terminal 60. The output unit 214 can be referred to as an output means.

[0038] 7 is a block diagram showing the main circuit configuration of the connection management server 30. The connection management server 30 includes a processor 31, a main memory 32, an auxiliary storage device 33, a communication interface 34, and a system transmission path 35. The system transmission path 35 includes an address bus, a data bus, a control signal line, etc. The connection management server 30 connects the processor 31, the main memory 32, the auxiliary storage device 33, and the communication interface 34 to the system transmission path 35. In the connection management server 30, a computer is configured by the processor 31, the main memory 32, the auxiliary storage device 33, and the system transmission path 35 that connects them.

[0039] The processor 31 corresponds to the central part of the computer. The processor 31 controls each part to realize various functions of the connection management server 30 according to an operating system or an application program. The processor 31 is, for example, a CPU.

[0040] The main memory 32 corresponds to the main storage portion of the computer. The main memory 32 includes a nonvolatile memory area and a volatile memory area. The main memory 32 stores an operating system or an application program in the nonvolatile memory area. The main memory 32 may store data required for the processor 31 to execute processes for controlling each part in the nonvolatile or volatile memory area. The main memory 32 uses the volatile memory area as a work area where data is appropriately rewritten by the processor 31. The nonvolatile memory area is, for example, a ROM. The volatile memory area is, for example, a RAM.

[0041] The auxiliary storage device 33 corresponds to the auxiliary storage portion of the computer. For example, an EEPROM, a HDD, or an SSD can be the auxiliary storage device 33. The auxiliary storage device 33 stores data used by the processor 31 when performing various processes, or data created by the processes in the processor 31. The auxiliary storage device 33 may also store the application programs described above.

[0042] The communication interface 34 is connected to the communication network 1. The communication interface 34 performs data communication with other devices connected via the communication network 1 in accordance with a communication protocol.

[0043] The connection management server 30 configured as above uses a part of the volatile memory area of ​​the main memory 32 as an area for the connection management table 321 (see FIG. 8). The connection management server 30 can form the connection management table 321 in this area. Note that the storage destination of the connection management table 321 is not limited to the main memory 32. The connection management table 321 may be stored in the auxiliary storage device 33.

[0044] FIG. 8 is a schematic diagram showing an example of the connection management table 321. As shown in FIG. 8, the connection management table 321 describes the application ID and the communication connection state of the mobile terminal 60 in which the shopping application identified by the application ID is installed. The communication connection state includes "connected" and "disconnected". "Connected" is a state in which the mobile terminal 60 is connected to the wireless LAN in the store. Usually, the state is "connected" while the shopping application is being executed. "Disconnected" is a state in which the mobile terminal 60, which was connected to the wireless LAN in the store, is no longer connected to the wireless LAN. Examples of reasons why the mobile terminal 60 is no longer connected to the wireless LAN in the store include the battery of the mobile terminal 60 running out, some kind of problem occurring in the connection to the wireless LAN, the user intentionally disconnecting the connection to the wireless LAN, the user quitting the shopping application and leaving the store, etc. The communication connection state is not limited to "connected" and "disconnected".

[0045] 9 is a block diagram showing the main circuit configuration of the accounting machine 40. The accounting machine 40 includes a processor 411, a main memory 412, an auxiliary storage device 413, a clock 414, a change machine interface 415, a communication interface 416, a touch panel 417, a scanner 418, a reader 419, a printer 420, and a system transmission path 421. The system transmission path 421 includes an address bus, a data bus, a control signal line, and the like. The system transmission path 421 interconnects the processor 411 with the main memory 412, the auxiliary storage device 413, the clock 414, the change machine interface 415, the communication interface 416, the touch panel 417, the scanner 418, the reader 419, and the printer 420. The processor 411, the main memory 412, and the auxiliary storage device 413 are connected by the system transmission path 421 to form a computer of the accounting machine 40.

[0046] The processor 411 corresponds to the central part of the computer. The processor 411 controls each part to realize various functions of the payment machine 40 according to an operating system or an application program. The processor 411 is, for example, a CPU.

[0047] The main memory 412 corresponds to the main storage portion of the computer. The main memory 412 includes a nonvolatile memory area and a volatile memory area. The main memory 412 stores an operating system or an application program in the nonvolatile memory area. The main memory 412 may store data required for the processor 411 to execute processes for controlling each part in the nonvolatile or volatile memory area. The main memory 412 uses the volatile memory area as a work area where data is appropriately rewritten by the processor 411. The nonvolatile memory area is, for example, a ROM. The volatile memory area is, for example, a RAM.

[0048] The auxiliary storage device 413 corresponds to the auxiliary storage portion of the computer. For example, an EEPROM, a HDD, or an SSD can be the auxiliary storage device 413. The auxiliary storage device 413 stores data used by the processor 411 when performing various processes, data created by the processes in the processor 411, etc. The auxiliary storage device 413 may also store the above application programs.

[0049] The application programs stored in the main memory 412 or the auxiliary storage device 413 include a control program that describes information processing executed by the accounting machine 40. There are no particular limitations on the method for installing the control program into the main memory 412 or the auxiliary storage device 413. The control program can be recorded on a removable recording medium, or distributed by communication via a network, and installed into the main memory 412 or the auxiliary storage device 413. The recording medium may be in any form, such as a CD-ROM or memory card, as long as it can store a program and is readable by the device.

[0050] The clock 414 functions as a time information source for the payment device 40. The processor 411 keeps track of the current date and time (date and time) based on the time information kept by the clock 414.

[0051] The change machine interface 415 performs data communication with the automatic change machine. The change machine interface 415 receives data on the inserted amount, data on the number of stored coins, etc. from the automatic change machine. The change machine interface 415 transmits change data to the automatic change machine.

[0052] The communication interface 416 is connected to the communication network 1. The communication interface 416 performs data communication with other devices connected via the communication network 1 in accordance with a communication protocol.

[0053] The touch panel 417 is a device that serves as both an input device and a display device for the payment device 40. The touch panel 417 detects a touch position on a displayed image, and outputs the touch position information to the processor 411.

[0054] The scanner 418 is an example of a reading device that reads code symbols such as a barcode symbol and a QR code (registered trademark) and outputs the read data to the processor 411. The scanner 418 may be a type that reads a code symbol by scanning with a laser beam, or a type that reads a code symbol from an image captured by an imaging device.

[0055] The reader 419 reads data recorded on the recording medium and outputs the read data to the processor 411. The reader 419 is a magnetic card reader if the recording medium is a magnetic card, and is an IC card reader if the recording medium is a contact IC card. In the case of a recording medium using RFID (Radio Frequency Identification) such as a contactless IC card or a smartphone, an RFID reader is used as the reader 419.

[0056] The printer 420 issues receipts by printing various characters or images on receipt paper. A thermal printer or a dot-matrix printer, for example, can be used as this type of printer 420. The printer 420 functions as a printing device for the accounting machine 40.

[0057] 10 and 11 are flow charts showing the main control procedures executed by the processor 61 of the mobile terminal 60 according to the control program. FIGS. 12 to 14, 16, 17 and 19 are flow charts showing the main control procedures executed by the processor 21 of the virtual POS server 20 according to the control program. FIG. 15 is a flow chart showing the main control procedures executed by the processor 411 of the payment machine 40 according to the control program. FIG. 18 is a flow chart showing the main control procedures executed by the processor 31 of the connection management server 30 according to the control program. Below, the main operations of the terminal management system SYA will be explained using these figures. Note that the contents of the operations explained below are just an example. As long as similar results can be obtained, the operation procedures and contents are not particularly limited.

[0058] First, when a user goes to a store where the terminal management system SYA is installed, the user starts a shopping application installed on the mobile terminal 60 owned by the user before starting shopping. Then, the processor 61 starts information processing of the procedure shown in the flowchart of FIG. In this embodiment, the connection management server 30 acquires an application ID from the mobile terminal 60 that has launched the shopping application. Then, the connection management server 30 writes the application ID and “connected” as the communication connection status in the connection management table 321.

[0059] First, the processor 61 controls the touch panel 64 to display a check-in screen as ACT1. On the check-in screen, for example, a message instructing to read a store entry data code is displayed, along with an image of a "Yes" button for indicating that the user has confirmed the message. After confirming the check-in screen, the user touches the "Yes" button.

[0060] When the "Yes" button on the check-in screen is touched, the processor 61 starts the camera 65 as ACT2. The processor 61 then controls the touch panel 64 to display a camera screen. For example, an image showing a reading area for a two-dimensional code is displayed on the camera screen. After checking the camera screen, the user points the lens of the camera 65 at the store entry data code prepared at the entrance of the store so that the data code fits into the image showing the reading area.

[0061] In ACT3, the processor 61 waits for the store entry data code to be read by the camera 65. When the store entry data code falls within the image indicating the reading area, the processor 61 determines that the store entry data code has been read. The processor 61 determines YES in ACT3 and proceeds to ACT4.

[0062] The processor 61 controls the wireless unit 66 to transmit a store entry command as ACT4 to the virtual POS server 20. This control causes the wireless unit 66 to wirelessly transmit the store entry command. The store entry command is received by the access point 50 and is sent to the virtual POS server 20 via the communication network 1. The store entry command includes an application ID.

[0063] When the processor 21 of the virtual POS server 20 receives a command from the mobile terminal 60 via the communication interface 25, the processor 21 checks the type of the command. If the received command is a store entry command, the processor 21 starts a command reception process according to the procedure shown in the flowchart of FIG.

[0064] The processor 21 acquires the application ID from the store entry command as ACT31. Then, the processor 21 extracts the abnormal condition data record 2321 identified by the application ID from the abnormal condition file 232 as ACT32.

[0065] In ACT33, the processor 21 checks whether or not there is an abnormality occurrence date outside the fixed period in the abnormal condition data record 2321. The fixed period is stored, for example, in the auxiliary storage device 23. If there is no abnormality occurrence date outside the fixed period, the processor 21 judges NO in ACT33 and proceeds to ACT35. The processing of ACT35 will be described later.

[0066] If there is an abnormality occurrence date outside the fixed period, the processor 21 judges YES in ACT33 and proceeds to ACT34. In ACT34, the processor 21 sets the invalid flag in the same row as the abnormality occurrence date outside the fixed period to "1". That is, all items in the same row as the invalid flag set to "1" are invalidated. Note that if there are multiple abnormality occurrence dates outside the fixed period in the abnormal condition data record 2321, the invalid flag in the same row as each abnormality occurrence date is set to "1".

[0067] The processor 21 acquires the number of abnormal conditions from the abnormal condition data record 2321 as ACT35. Specifically, the processor 21 acquires the number of invalid flags set to "0", that is, the number of valid abnormal condition data including the date of abnormality occurrence during a certain period.

[0068] In ACT36, the processor 21 checks whether the number of abnormal states has exceeded the upper limit number using the function of the limiting unit 213. The upper limit number is stored, for example, in the auxiliary storage device 23. The upper limit number can be set in any way. The upper limit number may be a fixed value in the virtual POS server 20, or may be changeable to a desired value by the store that manages the virtual POS server 20. If the upper limit number has been exceeded, the processor 21 judges YES in ACT36 and proceeds to ACT37.

[0069] The processor 21, as ACT37, creates a usage restriction screen and a first abnormal condition list screen based on the abnormal condition data record 2321. The usage restriction screen and the first abnormal condition list screen will be described later.

[0070] The processor 21, as ACT38, controls the communication interface 25 using the function of the output unit 214 to send a denial response command to the mobile terminal 60. This control causes the denial response command to be sent via the communication interface 25. The denial response command is wirelessly transmitted from the access point 50 via the communication network 1, and received by the mobile terminal 60 that sent the entry command. The denial response command includes image data of the usage restriction screen and image data of the first abnormal status list screen. With this, the processor 21 ends the process of receiving the entry command.

[0071] If the number of abnormal states does not exceed the upper limit, the result of ACT36 is NO, and the process proceeds to ACT39. The processor 21 extracts the time-series buffer 231 identified by the application ID in ACT39.

[0072] The processor 21 sets the status ST to “entered the store” using the function of the acquisition unit 211 as ACT40. The processor 21 acquires the current date and time DT measured by the clock 24 as ACT41. Then, the processor 21 writes the current date and time DT and the status ST in association with each other in the time-series buffer 231 extracted in the processing of ACT39 as ACT42.

[0073] The processor 21 forms a purchase registration list 221 in the main memory 22 as the ACT 43. Then, the processor 21 stores the application ID in the purchase registration list 221.

[0074] The processor 21 controls the communication interface 25 to send an approval response command to the mobile terminal 60 as ACT44. This control causes the approval response command to be sent via the communication interface 25. The approval response command is wirelessly transmitted from the access point 50 via the communication network 1, and received by the mobile terminal 60 that sent the entry command. With this, the processor 21 ends the entry command receiving process.

[0075] Returning to the explanation of Figure 10. The processor 61 of the mobile terminal 60 that controlled the transmission of the store entry command in ACT4 waits for a response command from the virtual POS server 20 in ACT5. If a denial response command is received from the virtual POS server 20, the processor 61 judges NO in ACT5 and proceeds to ACT6.

[0076] The processor 61 controls the touch panel 64 so that the usage restriction screen 100 (see FIG. 20) is displayed as ACT 6. With this, the processor 61 ends the information processing of the procedure shown in the flowchart of FIG.

[0077] FIG. 20 is a diagram showing an example of the usage restriction screen 100. As shown in FIG. 20, the usage restriction screen 100 displays a message notifying the user of a certain period and the number of abnormal states that occurred during the certain period, and notifying the user that shopping will be done in a normal lane due to the occurrence of an abnormal state. Shopping in a normal lane means that a store clerk will register the purchased item and perform a transaction process at the manned accounting machine 401. Shopping in a normal lane means that the user cannot register the purchased item using the mobile terminal 60 and perform a transaction process at the self-checkout machine 402. In other words, the purchase process (transaction) using the mobile terminal 60 is restricted. In addition, an image of a "Yes" button 101 for indicating that the user has confirmed the message and a "Details" button 102 for indicating that a list related to the abnormal state is to be viewed are displayed. After confirming the usage restriction screen 100, the user touches the "Yes" button 101. When the "Yes" button 101 is touched, the shopping application ends. The user will shop in a normal lane. A user who wishes to view the list of abnormal conditions touches the "Details" button 102. When the "Details" button 102 is touched, a first abnormal condition list screen 200 (see FIG. 21) is displayed. Note that the contents of the text data and images displayed in FIG. 20 are merely examples.

[0078] Fig. 21 is a diagram showing an example of the first abnormal condition list screen 200. As shown in Fig. 21, the first abnormal condition list screen 200 displays a list in which the date of abnormality occurrence and the content of the abnormality are described. That is, the first abnormal condition list screen 200 displays a list related to the abnormal conditions of the mobile terminal 60. Also, an image of a "back" button 201 is displayed for instructing the user to return from the first abnormal condition list screen 200 to the usage restriction screen 100. When the "back" button 201 is touched, the usage restriction screen 100 is displayed again.

[0079] Returning to the explanation of Figure 10. If an approval response command is received from the virtual POS server 20, the processor 61 determines YES in ACT5 and proceeds to ACT7.

[0080] The processor 61 controls the touch panel 64 to display a check-in completion screen as ACT7. The check-in completion screen displays, for example, a message indicating that preparations for shopping are complete, along with an image of a "Yes" button. After checking the check-in completion screen, the user touches the "Yes" button.

[0081] After controlling the display of the check-in completion screen, the processor 61 waits for an instruction to start shopping in ACT 8. When the "Yes" button on the check-in completion screen is touched, the processor 61 determines that an instruction to start shopping has been given. The processor 61 determines YES in ACT 8 and proceeds to ACT 9.

[0082] The processor 61 controls the touch panel 64 to display a purchase registration screen as ACT 9. The purchase registration screen has areas for displaying, for example, the product name, unit price, number of items, purchase amount, and total amount of the registered product. Also, an image of a "Checkout" button for instructing checkout is displayed.

[0083] After checking the purchase registration screen, the user walks around the sales floor and places the purchased items in a container such as a shopping basket or shopping cart. For example, when placing the purchased items in a container, the user points the lens of camera 65 at the barcode attached to the purchased item. When the barcode is read by camera 65, the product code represented by the barcode is entered into mobile terminal 60.

[0084] The processor 61 checks whether or not the product code has been acquired in ACT 10. If the processor 61 checks that the product code has been acquired, it determines YES in ACT 10 and proceeds to ACT 12.

[0085] The processor 61 controls the wireless unit 66 to transmit a purchase registration command as ACT12 to the virtual POS server 20. This control causes the wireless unit 66 to wirelessly transmit the purchase registration command. The purchase registration command is received by the access point 50 and sent to the virtual POS server 20 via the communication network 1. The purchase registration command includes the application ID and the product code of the purchased product.

[0086] When the processor 21 of the virtual POS server 20 receives a purchase registration command from the mobile terminal 60 via the communication interface 25, it starts a command reception process according to the procedure shown in the flowchart of FIG.

[0087] The processor 21 acquires the application ID from the purchase registration command as ACT51. Then, the processor 21 extracts the time-series buffer 231 identified by the application ID as ACT52.

[0088] The processor 21 checks in ACT53 whether or not "registering" is written as the status ST in the last line of the time-series buffer 231. When "registering" is written as the status ST in the last line of the time-series buffer 231, this means that a purchased product has already been registered, and therefore the product is a second or subsequent purchased product. Therefore, when "registering" is written as the status ST, the processor 21 judges YES in ACT53 and proceeds to ACT57. The processing of ACT57 will be described later.

[0089] If “registering” is not described as the status ST, that is, if it is the first purchased item, the processor 21 determines NO in ACT53 and proceeds to ACT54. In ACT54, the processor 21 sets the status ST to “registering” using the function of the acquisition unit 211.

[0090] The processor 21 acquires, as ACT55, the current date and time DT measured by the clock 24. Then, as ACT56, the processor 21 writes, in the time-series buffer 231 extracted in the processing of ACT52, the current date and time DT and the status ST in association with each other.

[0091] The processor 21 extracts the purchase registration list 221 identified by the application ID as ACT57. The processor 21 creates purchased item data 2211 based on the item code included in the purchase registration command as ACT58, and writes the purchased item data 2211 to the purchase registration list 221. The processor 21 also updates the total amount in the purchase registration list 221 to an amount obtained by adding the purchase amount of the newly written purchased item data 2211 as ACT59.

[0092] Processor 21 controls communication interface 25 to transmit the registered command to mobile terminal 60 as ACT 60. This control causes the registered command to be transmitted via communication interface 25. The registered command is wirelessly transmitted from access point 50 via communication network 1, and received by mobile terminal 60 which sent the purchase registration command. The registered command includes purchase registration list 221. With this, processor 21 ends the purchase registration command reception process.

[0093] Returning to the explanation of Figure 10. The processor 61 of the mobile terminal 60, which controlled the transmission of the purchase registration command in ACT12, waits for a registered command from the virtual POS server 20 in ACT13. If a registered command is received from the virtual POS server 20, the processor 61 judges YES in ACT13 and proceeds to ACT14.

[0094] The processor 61 updates the purchase registration screen in ACT 14. That is, the processor 61 updates the purchase registration screen so that the product name, unit price, number of items, and purchase amount of the product registered for purchase are added, and the purchase amount is added to the total amount. Then, the processor 61 returns to ACT 9.

[0095] If the product code is not acquired, the processor 61 judges NO in ACT10 and proceeds to ACT11. The processor 61 checks whether the "Checkout" button has been touched in ACT11. As described above, an image of the "Checkout" button is displayed on a part of the purchase registration screen. After completing a purchase, the user touches the "Checkout" button. If the "Checkout" button has been touched, the processor 61 judges that checking out has been instructed. If the "Checkout" button has not been touched, the processor 61 judges NO in ACT11 and returns to ACT10. That is, the processor 61 returns to the standby state of ACT10 to ACT11.

[0096] When the processor 61 confirms that a transaction has been instructed, it judges YES in ACT11 and proceeds to ACT21 in Figure 11. In ACT21, the processor 61 controls the wireless unit 66 to send a transaction execution command to the virtual POS server 20. This control causes the wireless unit 66 to wirelessly transmit the transaction execution command. The transaction execution command is received by the access point 50 and sent to the virtual POS server 20 via the communications network 1. The transaction execution command includes the application ID stored in the external memory 63.

[0097] When the processor 21 of the virtual POS server 20 receives a transaction execution command from the mobile terminal 60 via the communications interface 25, it starts a command reception process according to the procedure shown in the flowchart of FIG.

[0098] The processor 21 acquires the application ID from the transaction execution command as ACT 61. The processor 21 then extracts the time-series buffer 231 identified by that application ID as ACT 62.

[0099] The processor 21 sets the status ST to “checkout in progress” using the function of the acquisition unit 211 as ACT63. The processor 21 acquires the current date and time DT measured by the clock 24 as ACT64. Then, the processor 21 writes the current date and time DT and the status ST in association with each other in the time-series buffer 231 extracted in the processing of ACT62 as ACT65.

[0100] The processor 21 extracts the purchase registration list 221 identified by the application ID as ACT 66. The processor 21 creates accounting code data as ACT 67. The accounting code is used to identify the user performing a transaction at the payment device 40. An accounting code is created for each user performing a transaction at the payment device 40.

[0101] The processor 21 stores the accounting code in the purchase registration list 221 in ACT 68. The processor 21 creates an accounting information screen in ACT 69. On the accounting information screen, for example, an accounting barcode representing the accounting code created in ACT 67 and a message urging the user to have the scanner 418 provided on the accounting machine 40 read the accounting barcode are displayed.

[0102] Processor 21 controls communications interface 25 to send a billing information command to mobile terminal 60 as ACT70. This control causes the billing information command to be sent via communications interface 25. The billing information command is wirelessly transmitted from access point 50 via communications network 1, and received by mobile terminal 60, the source of the billing execution command. The billing information command contains image data of the billing information screen created in ACT69. With this, processor 21 ends the billing execution command reception processing.

[0103] Returning to the explanation of Figure 11. The processor 61 of the mobile terminal 60, which controlled the sending of the transaction execution command in ACT21, waits for a transaction information command from the virtual POS server 20 in ACT22. If a transaction information command is received from the virtual POS server 20, the processor 61 determines YES in ACT22 and proceeds to ACT23.

[0104] The processor 61 controls the touch panel 64 to display a payment information screen as ACT 23. After checking the payment information screen, the user goes to the location of an available payment machine 40 and has the payment barcode read by the scanner 418 installed on that payment machine 40. The processor 411 of the payment machine 40 then begins information processing according to the procedure shown in the flowchart of FIG.

[0105] The processor 411 of the payment device 40 waits for the payment barcode to be read in ACT 71. If the payment barcode has been read, the processor 411 determines YES in ACT 71 and proceeds to ACT 72.

[0106] The processor 411 queries the virtual POS server 20 for the purchase registration list 221 using the read accounting barcode in ACT72. In response to this query, the virtual POS server 20 extracts the purchase registration list 221 in which the queried accounting barcode is stored, and transmits the purchase registration list 221 to the accounting device 40. The processor 411 then waits to receive the purchase registration list 221 in ACT73. If the processor 411 receives the purchase registration list 221, it determines YES in ACT73 and proceeds to ACT74.

[0107] The processor 411 executes the transaction process based on the purchased product data 2211 in the purchase registration list 221 received as ACT 74. This transaction process is an existing process that is well known, so a detailed description will be omitted.

[0108] The processor 411 controls the communication interface 416 to transmit the processed command to the virtual POS server 20 as ACT75. This control causes the processed command to be transmitted via the communication interface 416. The processed command is received by the virtual POS server 20 via the communication network 1. The processed command includes the application ID stored in the purchase registration list 221. With this, the processor 411 ends the information processing of the procedure shown in the flowchart of FIG.

[0109] When the processor 21 of the virtual POS server 20 receives the processed command from the payment device 40 via the communication interface 25, it starts a command receiving process according to the procedure shown in the flowchart of FIG.

[0110] The processor 21 acquires the application ID from the processed command as ACT 81. The processor 21 extracts the time-series buffer 231 identified by the application ID as ACT 82.

[0111] The processor 21 sets the status ST to "transaction completed" using the function of the acquisition unit 211 as ACT83. The processor 21 acquires the current date and time DT measured by the clock 24 as ACT84. Then, the processor 21 associates the current date and time DT with the status ST and writes it in the time-series buffer 231 extracted in the processing of ACT82 as ACT85.

[0112] The processor 21 controls the communication interface 25 to send an accounting completed command to the mobile terminal 60 as ACT86. This control causes the accounting completed command to be sent via the communication interface 25. The accounting completed command is wirelessly transmitted from the access point 50 via the communication network 1, and received by the mobile terminal 60. The accounting completed command includes an application ID. With this, the processor 21 ends the processed command receiving process.

[0113] Returning to the explanation of Figure 11. After displaying the transaction information screen, the processor 61 waits for a transaction completion command from the virtual POS server 20 in ACT24. If a transaction completion command is received from the virtual POS server 20, the processor 61 determines YES in ACT24 and proceeds to ACT25.

[0114] The processor 61 controls the touch panel 64 to display a checkout screen as ACT25. On the checkout screen, for example, a message instructing the user to read a store exit data code is displayed, along with an image of a "Yes" button to indicate that the user has confirmed the message. After confirming the checkout screen, the user touches the "Yes" button.

[0115] When the "Yes" button on the checkout screen is touched, the processor 61 starts the camera 65 as ACT 26. The processor 61 then controls the touch panel 64 to display the camera screen. After checking the camera screen, the user points the lens of the camera 65 at the store exit data code prepared at the store exit so that the code fits into the image indicating the reading area.

[0116] After displaying the camera screen, the processor 61 waits for the store exit data code to be read by the camera 65 in ACT 27. When the store exit data code falls within the image indicating the reading area, the processor 61 determines that the store exit data code has been read. The processor 61 determines YES in ACT 27 and proceeds to ACT 28.

[0117] The processor 61 controls the wireless unit 66 to transmit an exit command as ACT28 to the virtual POS server 20. This control causes the wireless unit 66 to wirelessly transmit the exit command. The exit command is received by the access point 50 and is sent to the virtual POS server 20 via the communication network 1. The exit command includes an application ID.

[0118] When the processor 21 of the virtual POS server 20 receives a store exit command from the mobile terminal 60 via the communication interface 25, the processor 21 starts a command receiving process according to the procedure shown in the flowchart of FIG.

[0119] The processor 21 acquires the application ID from the exit command as ACT 91. Then, the processor 21 extracts the time-series buffer 231 identified by the application ID as ACT 92.

[0120] The processor 21 sets the status ST to “Left store” using the function of the acquisition unit 211 as ACT93. The processor 21 acquires the current date and time DT measured by the clock 24 as ACT94. Then, the processor 21 writes the current date and time DT and the status ST in association with each other in the time-series buffer 231 extracted in the processing of ACT92 as ACT95.

[0121] In ACT96, processor 21 checks, by the function of detection unit 212, whether or not "payment completed" is written as status ST in time-series buffer 231. Specifically, processor 21 checks whether or not "payment completed" is written as status ST at a time earlier than the current date and time DT on the same day as the current date and time DT at which "Leaving store" was written as status ST in the processing of ACT95.

[0122] If "payment completed" is not described as the status ST, that is, if "entered the store", "registering", "payment in progress" and "left the store" are described as the status ST but "payment completed" is not described before "left the store", this means that the user has registered the purchased items at the store but left the store without completing the payment. Therefore, if "payment completed" is not described as the status ST, the processor 21 judges NO in ACT96 and proceeds to ACT97.

[0123] The processor 21 extracts the abnormal condition data record 2321 identified by the application ID as ACT97 from the abnormal condition file 232. The processor 21 writes the abnormal condition data in the abnormal condition data record 2321 as ACT98. Specifically, the processor 21 writes in the abnormal condition data record 2321 the current date and time DT acquired in the processing of ACT94 as the abnormality occurrence date and "unaccounted" as the abnormality content in association with each other. The processor 21 sets the invalid flag in the same row as the abnormality occurrence date and abnormality content written in association with each other to "0".

[0124] The processor 21 controls the communication interface 25 to transmit a denial response command as ACT99 to the mobile terminal 60. This control causes the denial response command to be transmitted via the communication interface 25. The denial response command is wirelessly transmitted from the access point 50 via the communication network 1, and received by the mobile terminal 60 that transmitted the exit command. With this, the processor 21 ends the process of receiving the exit command.

[0125] If "transaction completed" is described as the status ST, the processor 21 determines YES in ACT96 and proceeds to ACT100. The processor 21 controls the communication interface 25 to send an approval response command to the mobile terminal 60 in ACT100. This control causes the approval response command to be sent via the communication interface 25. The approval response command is wirelessly transmitted from the access point 50 via the communication network 1, and received by the mobile terminal 60 that sent the exit command. With this, the processor 21 ends the exit command reception process.

[0126] Returning to the explanation of Figure 11. If the processor 61 of the mobile terminal 60, which controlled the sending of the store exit command in ACT28, receives an approval response command from the virtual POS server 20 in ACT29, the processor 61 judges YES in ACT29 and terminates the information processing of the procedure shown in the flowcharts of Figures 10 and 11.

[0127] If a denial response command is received from the virtual POS server 20, the processor 61 determines NO in ACT29 and proceeds to ACT30. The processor 61 controls the touch panel 64 so that a not-yet-checkout screen is displayed in ACT30. The not-yet-checkout screen may display, for example, a message notifying the user that the checkout has not been completed, along with an image of a "Yes" button to indicate that the user has confirmed the message. After confirming the not-yet-checkout screen, the user touches the "Yes" button to return to the purchase registration screen, and then touches the "Checkout" button. This concludes the information processing procedure shown in the flow charts of FIGS. 10 and 11.

[0128] Incidentally, the connection management server 30 manages, in the connection management table 321, the mobile terminal 60 that was connected to the wireless LAN in the store but is no longer connected due to reasons such as the battery of the mobile terminal 60 running out, some kind of problem occurring in the connection to the wireless LAN, the user intentionally disconnecting the connection to the wireless LAN, the user terminating the shopping application and leaving the store, etc. That is, the processor 31 of the connection management server 30 waits for the existence of an application ID in which "disconnected" is described as the communication connection status among the application IDs described in the connection management table 321 as ACT101 in Fig. 18. If an application ID in which "disconnected" is described as the communication connection status exists, the processor 31 judges YES in ACT101 and proceeds to ACT102.

[0129] The processor 31 controls the communication interface 34 to transmit a disconnection command to the virtual POS server 20 as ACT102. This control causes the disconnection command to be transmitted via the communication interface 34. The disconnection command is received by the virtual POS server 20 via the communication network 1. The disconnection command includes an application ID in which "disconnected" is described as the communication connection status. With this, the processor 31 ends the information processing of the procedure shown in the flowchart of FIG.

[0130] When the processor 21 of the virtual POS server 20 receives a disconnection command from the connection management server 30 via the communication interface 25, the processor 21 starts a command reception process according to the procedure shown in the flowchart of FIG.

[0131] The processor 21 acquires the application ID from the disconnection command as ACT 111. Then, the processor 21 extracts the time-series buffer 231 identified by the application ID as ACT 112.

[0132] In ACT113, the processor 21 uses the function of the detection unit 212 to check whether data indicating a currently unpaid transaction is written in the time-series buffer 231.

[0133] If the data indicating the current unpaid transaction is not described, i.e., if the user has already paid at the store, it is possible that the mobile terminal 60 is no longer connected to the store's wireless LAN because the user has closed the shopping app and left the store. Therefore, if the data indicating the current unpaid transaction is not described, the processor 21 determines NO in ACT113 and ends the disconnection command reception process.

[0134] When data indicating a current unpaid transaction is written, for example, when the time-series buffer 231 writes "entered the store" and "registering" as the status ST but does not write "payment completed", or when the time-series buffer 231 writes "entered the store", "registering", and "payment in progress" as the status ST but does not write "payment completed", this means that the user is registering the purchased items at the store but has not completed the payment. Therefore, when data indicating a current unpaid transaction is written, the processor 21 determines YES in ACT113 and proceeds to ACT114. The processor 21 obtains the current date and time measured by the clock 24 in ACT114.

[0135] The processor 21 extracts the abnormal state data record 2321 identified by the application ID from the abnormal state file 232 as ACT115. The processor 21 writes the abnormal state data in the abnormal state data record 2321 as ACT116. Specifically, the processor 21 writes in the abnormal state data record 2321 the current date and time acquired in the processing of ACT114 as the abnormality occurrence date and "disconnected without accounting being performed" as the abnormality content in association with each other. The processor 21 sets the invalid flag in the same row as the abnormality occurrence date and abnormality content written in association with each other to "0". With this, the processor 21 ends the connection disconnection command reception processing.

[0136] Therefore, in such a terminal management system SYA, when an entry command is sent from the mobile terminal 60 to the virtual POS server 20, the number of abnormal conditions that occurred within a certain period of time is obtained from the abnormal condition data record 2321 identified by the application ID included in the entry command. If the number of abnormal states does not exceed the upper limit, the current date and time DT and "enter store" are associated and written as the status ST in the time-series buffer 231 identified by the application ID. Then, an approval response command is sent to the mobile terminal 60. That is, a purchase registration is performed using the mobile terminal 60. When a store exit command is sent from the mobile terminal 60 to the virtual POS server 20, the current date and time DT and "leave store" are associated and written as the status ST in the time-series buffer 231 identified by the application ID included in the store exit command. If "enter store", "registering", "checkout in progress", and "leave store" are written as the status ST in the time-series buffer 231, but "checkout completed" is not written before "leave store", abnormal state data (date of abnormality occurrence, abnormality content, and invalid flag) are written in the abnormal state data record 2321 identified by the application ID. Furthermore, when the connection management server 30 confirms that there is an application ID for which "disconnected" is written as the communication connection status in the connection management table 321, that is, an application ID that was connected to the in-store wireless LAN but is no longer connected, it sends a connection disconnection command to the virtual POS server 20. When the virtual POS server 20 receives a connection disconnection command, if the time-series buffer 231 identified by the application ID included in the connection disconnection command describes "entered the store" and "registering" as the status ST but does not describe "accounting completed," or if the status ST describes "entered the store," "registering," and "accounting in progress" but does not describe "accounting completed," then abnormal condition data is written in the abnormal condition data record 2321 identified by that application ID. On the other hand, if the number of abnormal states exceeds the upper limit, a denial response command including image data of the usage restriction screen 100 and image data of the first abnormal state list screen 200 is transmitted to the mobile terminal 60. Therefore, it is possible to restrict the purchasing process (transaction) using the mobile terminal 60 for the user who operated the mobile terminal 60 in which the abnormal state occurred.

[0137] The usage restriction screen 100 also displays a certain period of time, the number of times that an abnormal state occurred during the certain period of time, and a message notifying the user that the purchase processing by the mobile terminal 60 will be restricted due to the occurrence of the abnormal state. Therefore, the user can recognize the occurrence of the abnormal state.

[0138] Furthermore, when the "details" button 102 on the usage restriction screen 100 is touched, a first abnormal condition list screen 200 is displayed, allowing the user to check the details of the abnormal condition that has occurred.

[0139] Second embodiment Next, a second embodiment will be described with reference to FIGS. In the second embodiment, a terminal management system SYB including a tallying server 90 will be described. In the drawings and the following description of the second embodiment, the same elements as those in the first embodiment are denoted by the same reference numerals. Therefore, the description of the same elements may be omitted. Incidentally, since Figs. 2 to 11 and Figs. 13 to 20 used in the description of the first embodiment are also common to the second embodiment, the description thereof will be omitted here.

[0140] 22 is a block diagram showing a schematic configuration of a terminal management system SYB according to the second embodiment. The terminal management system SYB includes a plurality of store systems 80, a tallying server 90, a communication network 2, and a plurality of mobile terminals 60. The tallying server 90 is connected to a relay server 70 via the communication network 2.

[0141] A store system 80 is configured for each store that has introduced the terminal management system SYB. The number of stores is not particularly limited. FIG. 22 shows a store system 80 configured in store A and a store system 80 configured in store B. The corporate entity that operates store A may be the same as the corporate entity that operates store B, or may be different. Below, the store system of store A is represented as store system 81, and the store system of store B is represented as store system 82. Furthermore, when the store systems 81, 82, ... of each store are collectively referred to as store system 80.

[0142] The basic configuration of the store systems 80 is common. That is, the store system 80 includes a store server 10, a virtual POS server 20, a connection management server 30, a payment machine 40, an access point 50, a mobile terminal 60, and a relay server 70. The store server 10, the virtual POS server 20, the connection management server 30, the payment machine 40, the access point 50, and the relay server 70 are connected to a communication network 1.

[0143] The connection management server 30 manages the communication connection state of the mobile terminal 60 that communicates with the store system 80. The connection management server 30 manages, for example, whether or not the mobile terminal 60 is connected to a wireless LAN or the like in the store.

[0144] The relay server 70 relays communication between the tallying server 90 connected to the communication network 2 and each device connected to the communication network 1, namely, the store server 10, the virtual POS server 20, the connection management server 30, the accounting machine 40, and the access point 50. The communication network 2 is typically the Internet. The communication network 2 may be a dedicated closed network, or may include a mobile communication network.

[0145] The tallying server 90 collects and tallys the abnormal state files 232 managed by the virtual POS servers 20 of the respective stores. The tallying server 90 provides the tallying data to the virtual POS servers 20.

[0146] Fig. 23 is a block diagram showing the main circuit configuration of the tallying server 90. As shown in Fig. 23, the tallying server 90 includes a processor 91, a main memory 92, an auxiliary storage device 93, a clock 94, a communication interface 95, and a system transmission path 96. The system transmission path 96 includes an address bus, a data bus, a control signal line, and the like. The tallying server 90 connects the processor 91, the main memory 92, the auxiliary storage device 93, the clock 94, and the communication interface 95 to the system transmission path 96. In the tallying server 90, a computer is configured by the processor 91, the main memory 92, the auxiliary storage device 93, and the system transmission path 96 that connects them.

[0147] The processor 91 corresponds to the central part of the computer. The processor 91 controls each part to realize various functions of the tallying server 90 according to an operating system or an application program. The processor 91 is, for example, a CPU.

[0148] The main memory 92 corresponds to the main storage portion of the computer. The main memory 92 includes a nonvolatile memory area and a volatile memory area. The main memory 92 stores an operating system or an application program in the nonvolatile memory area. The main memory 92 may store data required for the processor 91 to execute processes for controlling each part in the nonvolatile or volatile memory area. The main memory 92 uses the volatile memory area as a work area where data is appropriately rewritten by the processor 91. The nonvolatile memory area is, for example, a ROM. The volatile memory area is, for example, a RAM.

[0149] The auxiliary storage device 93 corresponds to the auxiliary storage portion of the computer. For example, an EEPROM (registered trademark), a HDD, or an SSD can be the auxiliary storage device 93. The auxiliary storage device 93 stores data used by the processor 91 when performing various processes, or data created by the processes in the processor 91. The auxiliary storage device 93 may also store the application programs. The auxiliary storage device 93 functions as a storage unit that collects and stores information related to an abnormal state of the mobile terminal 60.

[0150] The clock 94 functions as a time information source for the tallying server 90. The processor 91 keeps track of the current date and time based on the time information kept by the clock 94.

[0151] The communication interface 95 is connected to the communication network 2. The communication interface 95 performs data communication with the relay server 70 of each store system 80 connected via the communication network 2 in accordance with a communication protocol.

[0152] The tallying server 90 uses a part of the storage area of ​​the auxiliary storage device 93 as an area for the tallying data file 931. Note that the storage destination of the tallying data file 931 is not limited to the auxiliary storage device 93. The tallying data file 931 may be stored in a part of the volatile memory area of ​​the main memory 92.

[0153] FIG. 24 is a schematic diagram showing an example of an aggregated data record 9311 stored in the aggregated data file 931. As shown in FIG. 24, the aggregated data record 9311 stores aggregated data generated for each application ID. The application ID is a unique code assigned to each shopping application to identify a shopping application executed when shopping at a store in which the terminal management system SYB is installed. The aggregated data record 9311 includes items such as an application ID, a cumulative number of abnormal states, a fixed period, and store data 9312. The cumulative number of abnormal states is the total number of valid abnormal state data included in the abnormal state data record 2321 of each store data 9312. The fixed period is set, for example, by an administrator who manages the terminal management system SYB. In this case, the fixed period is the same for each store in which the terminal management system SYB is installed. The store data 9312 includes a store code, a store name, an abnormal state data record 2321, and the like. There are as many store data 9312 as there are times when the shopping application is used at a store in which the terminal management system SYB is installed. The store code is a unique code assigned to each store to identify the store. The store name is the name of the store identified by the corresponding store code. Note that the aggregate data record 9311 is not limited to the items in FIG.

[0154] Figures 25 and 27 are flow charts showing the main control procedures executed by the processor 91 of the tallying server 90 in accordance with a control program in the second embodiment. Figure 26 is a flow chart showing the main control procedures executed by the processor 21 of the virtual POS server 20 in accordance with a control program in the second embodiment. Figure 26 corresponds to Figure 12 described in the first embodiment. The same process steps as in the first embodiment are therefore given the same reference numerals. Note that the content of the operation described below is an example. As long as similar results can be obtained, the operation procedures and contents are not particularly limited.

[0155] In the second embodiment, for example, at a predetermined time after closing time on each business day, the virtual POS server 20 transmits the store code and the abnormal state file 232 to the tallying server 90. The predetermined time can be set arbitrarily. The predetermined time may be a fixed value in the virtual POS server 20, or may be changeable to a desired value by the store that manages the virtual POS server 20. The store code is stored, for example, in the main memory 22 of the virtual POS server 20. In the second embodiment, for example, at a predetermined time from a predetermined time after closing time on each business day until before the store code and the abnormal condition file 232 are received, the tallying server 90 initializes the cumulative number of abnormal condition occurrences included in the aggregation data record 9311 stored in the aggregation data file 931. This initialization resets the cumulative number of abnormal condition occurrences to "0." The predetermined time may be a fixed value in the tallying server 90, or may be changeable to a desired value by an administrator who manages the tallying server 90.

[0156] The processor 91 of the tallying server 90 waits to receive the store code and the abnormal state file 232 in ACT121 of Fig. 25. When the store code and the abnormal state file 232 are received, the processor 91 judges YES in ACT121 and proceeds to ACT122.

[0157] The processor 91 extracts, from the aggregated data file 931, aggregated data records 9311 each including an application ID for each application ID that identifies the abnormal state data record 2321 stored in the abnormal state file 232 received as ACT122.

[0158] The processor 91 extracts the store data 9312 including the store code received as ACT123 from the aggregation data record 9311.

[0159] The processor 91 updates the abnormal condition data record 2321 included in the store data 9312 as ACT124 to the received abnormal condition data record 2321.

[0160] The processor 91 checks in ACT125 whether or not there is an abnormality occurrence date outside the fixed period in the abnormal condition data record 2321 updated in the processing of ACT124. The fixed period is a fixed period included in the aggregate data record 9311 extracted in the processing of ACT122. If there is no abnormality occurrence date outside the fixed period, the processor 91 judges NO in ACT125 and proceeds to ACT127. The processing of ACT127 will be described later.

[0161] If there is an abnormality occurrence date outside the fixed period, the processor 91 determines YES in ACT125 and proceeds to ACT126. In ACT126, the processor 91 sets the invalid flag in the same row as the abnormality occurrence date outside the fixed period to "1". That is, all items in the same row as the invalid flag set to "1" are invalidated. Note that if there are multiple abnormality occurrence dates outside the fixed period in the abnormal condition data record 2321, the invalid flag in the same row as each abnormality occurrence date is set to "1".

[0162] The processor 91 acquires, as ACT127, the number of abnormal states from the abnormal state data record 2321. When there are multiple store data 9312, the number of abnormal states is the sum of the number of abnormal states acquired from each of the abnormal state data records 2321 included in each store data 9312.

[0163] The processor 91 updates the cumulative number of abnormal state occurrences in ACT 128. Specifically, the processor 91 updates the cumulative number of abnormal state occurrences included in the aggregation data record 9311 to the number of abnormal state occurrences acquired in the processing of ACT 127. With this, the processor 91 ends the information processing of the procedure shown in the flowchart of FIG.

[0164] Incidentally, similarly to the first embodiment, in the second embodiment, when the processor 21 of the virtual POS server 20 receives a store entry command from the mobile terminal 60 via the communication interface 25, it starts a command receiving process according to the procedure shown in the flowchart of FIG. 26.

[0165] In the second embodiment, the process of ACT31 is followed by the process of ACT131 to ACT133. The processor 21 controls the communication interface 25 to transmit a tally command as ACT131 to the virtual POS server 20. This control causes the tally command to be transmitted via the communication interface 25. The tally command is received by the relay server 70 via the communication network 1, and transmitted to the tally server 90 via the communication network 2. The tally command includes the application ID acquired in the processing of ACT31.

[0166] When the processor 91 of the tallying server 90 receives a tallying command from the virtual POS server 20 via the communication interface 95, the processor 91 starts a command receiving process according to the procedure shown in the flowchart of FIG.

[0167] The processor 91 acquires the application ID from the tally command as ACT 141. Then, the processor 91 extracts the tally data record 9311 identified by the application ID from the tally data file 931 as ACT 142.

[0168] The processor 91 controls the communication interface 95 to transmit the aggregated command as ACT143 to the virtual POS server 20. This control causes the aggregated command to be transmitted via the communication interface 95. The aggregated command is received by the relay server 70 via the communication network 2, and transmitted to the virtual POS server 20 via the communication network 1. The aggregated command includes an aggregated data record 9311 identified by the application ID acquired in the processing of ACT141.

[0169] Returning to the explanation of Figure 26. The processor 21 of the virtual POS server 20 that controlled the transmission of the tallying command in ACT131 waits for a tallying command from the tallying server 90 in ACT132. When the tallying command is received from the tallying server 90, the processor 21 judges YES in ACT132 and proceeds to ACT133.

[0170] The processor 21, as ACT133, checks whether or not the cumulative number of abnormal states included in the aggregation data record 9311 included in the aggregation completed command by the function of the limiting unit 213 exceeds the upper limit number.

[0171] If the cumulative number of abnormal states does not exceed the upper limit, the result is determined as NO in ACT 133, and the process proceeds to ACT 39. The processes in ACT 39 to ACT 44 are the same as those in the first embodiment. With this, the processor 21 ends the process of receiving the store entry command.

[0172] In the second embodiment, if the upper limit number is exceeded, the processor 21 determines YES in ACT133 and proceeds to ACT134. The processor 21, as ACT 134, creates the usage restriction screen 100 and the second abnormal condition list screen based on the aggregated data record 9311. The second abnormal condition list screen will be described later.

[0173] The processor 21, as ACT135, controls the communication interface 25 using the function of the output unit 214 to send a denial response command to the mobile terminal 60. This control causes the denial response command to be sent via the communication interface 25. The denial response command is wirelessly transmitted from the access point 50 via the communication network 1, and received by the mobile terminal 60 that sent the entry command. The denial response command includes image data of the usage restriction screen 100 and image data of the second abnormal status list screen. With this, the processor 21 ends the process of receiving the entry command.

[0174] When a denial response command is received from the virtual POS server 20, the processor 61 controls the touch panel 64 to display the usage restriction screen 100. A user who wishes to view details of the abnormal condition touches the "Details" button 102. When the "Details" button 102 is touched, a second abnormal condition list screen 300 (see FIG. 28) is displayed.

[0175] Fig. 28 is a diagram showing an example of the second abnormal condition list screen 300. As can be seen by comparing Fig. 21 with Fig. 28, in the second embodiment, the store name is further displayed. Note that the contents of the text data and images displayed in Fig. 28 are merely examples.

[0176] Therefore, in such a terminal management system SYB, when an entry command is sent from the mobile terminal 60 to the virtual POS server 20, a tally command including the application ID included in the entry command is sent from the virtual POS server 20 to the tally server 90. The tally server 90 sends a tally command including the tally data record 9311 identified by the application ID to the virtual POS server 20. When the tally command is received by the virtual POS server 20, the cumulative number of abnormal conditions that have occurred during a certain period, which is included in the tally data record 9311, is acquired. If the cumulative number of abnormal conditions exceeds the upper limit, a denial response command including image data of the usage restriction screen 100 and image data of the second abnormal condition list screen 300 is sent to the mobile terminal 60. Therefore, for a user who operates a mobile terminal 60 in which abnormal states have occurred in multiple stores, purchasing processes (transactions) using that mobile terminal 60 can be restricted.

[0177] Furthermore, when the mobile terminal 60 receives a denial response command, the usage restriction screen 100 is displayed on the touch panel 64. When the "Details" button 102 on the usage restriction screen 100 is touched, a second abnormal condition list screen 300 is displayed, which further displays the store names. This allows the user to check the details of abnormal conditions that have occurred in multiple stores.

[0178] Although the first and second embodiments have been described above, the embodiments are not limited to these.

[0179] In the above embodiment, the store entry data code and the store exit data code are coded in a predetermined two-dimensional code system. For example, the store entry data code and the store exit data code may be coded in a one-dimensional code system depending on the amount of information to be included on the medium.

[0180] In the above embodiment, when the user reads the store entry data code prepared at the entrance of the store with the camera 65, the status ST becomes "enter store" as an entry operation has been performed. Also, when the user reads the store exit data code prepared at the exit of the store with the camera 65, the status ST becomes "exit store" as an exit operation has been performed. Even if the user enters or leaves the store without reading the store entry data code or the store exit data code, the status ST may be "enter store" or "exit store". For example, a gate device is provided at the entrance of the store. The gate device includes a passage sensor that detects that a customer has passed through the gate device and a reader that reads the terminal code of the mobile terminal 60. For example, a customer passes through the gate device in the direction of entering the store. When the terminal code of the mobile terminal 60 owned by the customer is read by the reader, the status ST may be "enter store". Also, for example, the customer passes through the gate device in the direction of leaving the store. When the terminal code of the mobile terminal 60 owned by the customer is read by a reader, it may be determined that the store exit operation has been performed, and the status ST may be set to "exited store."

[0181] In the above embodiment, in the case of the first purchased item, the status ST is set to "registering". For example, when the user deletes registered purchased items one by one or deletes them all at once (abandoning the transaction), and the purchased item data 2211 in the purchase registration list 221 no longer exists, the status ST may be set to "entered". In this case, the status ST is written in the time-series buffer 231 in the order of "entered", "registering", and "entered".

[0182] In the above embodiment, an example is given in which a not-yet-paid screen is displayed on the touch panel 64 of the mobile terminal 60. For example, a voice message to the effect that the payment has not yet been made may be output.

[0183] In the above embodiment, the connection management server 30 is illustrated as being connected to the communication network 1. For example, the connection management server 30 may be provided on the Internet as cloud computing.

[0184] In the above embodiment, the virtual POS server 20 uses a part of the storage area of ​​the auxiliary storage device 23 as the area of ​​the time-series buffer 231. For example, the time-series buffer 231 may be stored in the external memory 63 of the mobile terminal 60.

[0185] In the above embodiment, the virtual POS server 20 has been described as one aspect of the terminal management device. For example, the virtual POS server 20 further having a function as at least one of the store server 10, the connection management server 30, or the tallying server 90 may be used as the terminal management device. In other words, the store server 10, the connection management server 30, or the tallying server 90 having a function as the virtual POS server 20 may be used as the terminal management device.

[0186] In the second embodiment, the virtual POS server 20 transmits the store code and the abnormal state file 232 to the tallying server 90 at a predetermined time after the store closes on each business day. The timing of transmitting the data to the tallying server 90 may be, for example, a predetermined time before the store opens on each business day. In this case, the tallying server 90 may initialize the cumulative abnormal state count included in the tallying data record 9311 stored in the tallying data file 931 at a predetermined time, for example, from a predetermined time before the store opens on each business day until the store code and the abnormal state file 232 are received.

[0187] Although several other embodiments of the present invention have been described, these embodiments are presented as examples and are not intended to limit the scope of the invention. These novel embodiments can be implemented in various other forms, and various omissions, substitutions, and modifications can be made without departing from the spirit of the invention. These embodiments and their modifications are included within the scope of the invention and the scope of the invention and its equivalents described in the claims. In addition, the claims as originally filed of this application are set forth below. [C1] an acquisition unit that acquires status information indicating an operation state of a mobile terminal operated by a customer and used for product purchase processing; a detection unit that detects an abnormal state of the mobile terminal based on the status information acquired by the acquisition unit; a restriction unit that restricts purchase processing by the mobile terminal according to the number of times the abnormal state of the mobile terminal has been detected by the detection unit; A terminal management device comprising: [C2] an output unit that outputs a message to the mobile terminal when the restriction unit restricts the purchase process by the mobile terminal; The terminal management device according to C1, further comprising: [C3] The output unit outputs a list related to the abnormal state of the mobile terminal detected by the detection unit to the mobile terminal. The terminal management device of C2 further comprising: [C4] A plurality of terminal management devices each including an acquisition unit that acquires status information indicating an operation state of a mobile terminal operated by a customer and used for a product purchase process, and a detection unit that detects an abnormal state of the mobile terminal based on the status information acquired by the acquisition unit; a storage unit that collects and stores information related to the abnormal state of the mobile terminal detected by the detection unit; Including, The terminal management device a limiting unit that limits purchase processing by the mobile terminal in accordance with the number of times the mobile terminal has entered an abnormal state based on information related to the abnormal state of the mobile terminal stored in the storage unit; A terminal management system comprising: [C5] A computer of a terminal management device, An acquisition means for acquiring status information indicating an operation state of a mobile terminal operated by a customer and used for product purchase processing; a detection means for detecting an abnormal state of the mobile terminal based on the status information acquired by the acquisition means; and a limiting means for limiting purchase processing by the mobile terminal in accordance with the number of times the abnormal state of the mobile terminal has been detected by the detecting means; A terminal management program to function as a [Explanation of symbols]

[0188] 1, 2...communication network, 10...store server, 20...virtual POS server, 21, 31, 61, 91, 411...processor, 22, 32, 92, 412...main memory, 23, 33, 93, 413...auxiliary storage device, 24, 94, 414...clock, 25, 34, 95, 416...communication interface, 26, 35, 67, 96, 421...system transmission path, 30...connection management server, 40...accounting machine, 50...access point, 60...mobile terminal, 62...built-in memory, 63...external memory, 64, 417...touch panel, 65...camera, 66...wireless unit, 70...relay server, 80 (81, 82)...store system, 90...tallying server, 221...purchase registration list, 231...time series buffer, 232...abnormal status file, 321...connection management table, 401...manned checkout machine, 402...self-service checkout machine, 415...change machine interface, 418...scanner, 419...reader, 420...printer, 931...tallying data file, 2211...purchased item data, 2321...abnormal status data record, 9311...tallying data record, 9312...store data, SYA, SYB...terminal management system, 211...acquisition unit, 212...detection unit, 213...restriction unit, 214...output unit.

Claims

1. an acquisition unit that acquires status information indicating an operation state of a mobile terminal operated by a customer and used for product purchase processing; a detection unit that detects an abnormal state of the mobile terminal based on the status information acquired by the acquisition unit; a restriction unit that restricts purchase processing by the mobile terminal according to the number of times the abnormal state of the mobile terminal has been detected by the detection unit; an output unit that outputs a message to the mobile terminal when the restriction unit restricts the purchase process by the mobile terminal; Equipped with The output unit outputs to the mobile terminal a list of abnormal conditions, each of which describes the date when the abnormality occurred and the content of the abnormality in the mobile terminal detected by the detection unit.

2. an acquisition unit that acquires status information indicating an operation state of a mobile terminal operated by a customer and used for product purchase processing; a detection unit that detects an abnormal state of the mobile terminal based on the status information acquired by the acquisition unit; a storage unit that collects and stores information related to the abnormal state of the mobile terminal detected by the detection unit; Including, The terminal management device a limiting unit that limits purchase processing by the mobile terminal in accordance with the number of times the mobile terminal has entered an abnormal state based on information related to the abnormal state of the mobile terminal stored in the storage unit; an output unit that outputs a message to the mobile terminal when the restriction unit restricts the purchase process by the mobile terminal; Equipped with The output unit outputs to the mobile terminal a list of abnormal conditions, each describing the date when the abnormality occurred and the content of the abnormality in the mobile terminal detected by the detection unit.

3. A computer of a terminal management device, An acquisition means for acquiring status information indicating an operation state of a mobile terminal operated by a customer and used for product purchase processing; a detection means for detecting an abnormal state of the mobile terminal based on the status information acquired by the acquisition means; A limiting means for limiting purchase processing by the mobile terminal in accordance with the number of times the abnormal state of the mobile terminal is detected by the detecting means; and an output means for outputting a message to the mobile terminal when the restriction means restricts the purchase process by the mobile terminal; Function as a The output means is a terminal management program that outputs to the mobile terminal a list relating to abnormal conditions, in which the date of occurrence of the abnormality and the content of the abnormality in the mobile terminal detected by the detection means are described.

Images