Mobile terminal and information processing program
The mobile terminal adapts to store-specific identifiers to dynamically adjust screen layouts and content, addressing the challenge of uniformity in smartphone POS systems, enhancing the shopping experience by personalizing store interfaces.
Patent Information
- Application Number
- JP2024095892
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Filing Date
- 2024-06-13
- Publication Date
- 2025-12-11
- Estimated Expiration
- 2040-02-14
AI Technical Summary
Existing smartphone POS systems lack the ability to function as user interfaces that can adapt to the individuality of each store while maintaining a unified application across multiple stores, resulting in identical operation screens.
A mobile terminal equipped with a display device, storage device, identifier acquisition means, display control means, and notification means, which allows the system to store store-specific identifiers and dynamically adjust the layout, size, and content of operation objects based on the identified store, enabling personalized screen displays.
Enables the mobile terminal to function as a user interface that adapts to each store's unique identity, providing a personalized shopping experience while maintaining a unified application across multiple stores.
Smart Images

Figure 0007784480000001 
Figure 0007784480000002 
Figure 0007784480000003
Abstract
Description
[Technical Field]
[0001] An embodiment of the present invention comprises: Mobile devices and information processing programs. [Background technology]
[0002] Regarding commercial transactions at stores such as supermarkets, transaction processing systems that allow customers to use their mobile devices, such as smartphones, to register products to be traded are being considered, and are known as "smartphone POS systems." If such transaction processing systems could be used at multiple stores without changing the application on the mobile device, it would be convenient for customers and would eliminate the need to prepare separate applications for each store. However, the operation screen displayed on the mobile terminal to receive instructions from customers ends up being the same in every store. Given these circumstances, it has been desired to be able to make the mobile terminals carried by customers function as user interfaces using the same application, while still being able to present the uniqueness of each store with regard to the screen display on the mobile terminal. [Prior art documents] [Patent documents]
[0003] [Patent Document 1] Japanese Patent Application Laid-Open No. 2016-111375 Summary of the Invention [Problem to be solved by the invention]
[0004] The problem that this invention aims to solve is to make it possible to make the mobile terminals carried by customers function as user interfaces using the same application, while making it possible to express the individuality of each store regarding the screen display on the mobile terminal. Mobile devices and to provide an information processing program. [Means for solving the problem]
[0005] The mobile terminal of the embodiment includes a display device, a storage device, an identifier acquisition means, a display control means, an input means, and a notification means. The storage device stores a store-specific identifier for inputting customer instructions regarding product registration. (1) the layout position of the display area showing the same information on the operation screen, (2) the size of the operation object for receiving the same operation, (3) the character string displayed on the operation object, and (4) the layout position of the operation object on the operation screen. The storage device stores an operation screen. The identifier acquisition means acquires a store identifier for identifying the store visited by the customer. The display control means, in response to a request from the server device, causes the display device to display an operation screen corresponding to the store identified by the store identifier acquired by the identifier acquisition means from among the operation screens stored in the storage device. The input means inputs instructions from the customer regarding the registration of purchased items by operations performed in response to the operation screen displayed on the display device. The notification means notifies the server device of the instructions input by the input means. [Brief explanation of the drawings]
[0006] [Figure 1] FIG. 1 is a block diagram showing a schematic configuration of a transaction processing system according to an embodiment. [Figure 2] FIG. 2 is a block diagram showing the main circuit configuration of the mobile terminal in FIG. [Figure 3] FIG. 2 is a block diagram showing the main circuit configuration of the transaction processing server in FIG. 1. [Figure 4] FIG. 4 is a diagram schematically showing the configuration of a data record included in the management database in FIGS. 2 and 3. [Figure 5] 3 is a flowchart of UI processing in the processor in FIG. 2; [Figure 6] 4 is a flowchart of a transaction process in the processor in FIG. 3. [Figure 7] 10 is a flowchart showing an example of a part of a registration process. [Figure 8] FIG. 10 is a diagram showing an example of a list screen. [Figure 9] FIG. 10 is a diagram showing an example of a list screen. DETAILED DESCRIPTION OF THE INVENTION
[0007] An embodiment of a transaction processing system will be described below with reference to the drawings. The transaction processing system in this embodiment processes transactions in which a customer picks up and purchases an item displayed in a store from a display location.
[0008] FIG. 1 is a block diagram showing a schematic configuration of a transaction processing system 100 according to this embodiment. The transaction processing system 100 is configured so that a plurality of mobile terminals 10, a transaction processing server 20, and a plurality of store systems 30 can communicate with each other via a communication network 40.
[0009] The mobile terminal 10 is an information communication terminal that functions as a user interface for customers who shop at a store using the transaction processing system 100. The mobile terminal 10 has a function for wireless communication with the store system 30 and a function for wireless communication with the communication network 40. Transaction processing server 20 is a server device that executes information processing for processing transactions at each of multiple stores (hereinafter referred to as affiliated stores) that use transaction processing system 100. Transaction processing server 20 provides, for example, a transaction processing service (described later) as a cloud service via communication network 40.
[0010] FIG. 1 shows two store systems 30. These store systems 30 are installed at different affiliated stores that use the transaction processing system 100. There may be three or more affiliated stores, with a store system 30 installed for each affiliated store. The businesses operating the multiple affiliated stores may be the same or different. The communication network 40 may be, for example, the Internet, a virtual private network (VPN), a local area network (LAN), a public communication network, a mobile communication network, or the like, either alone or in appropriate combination. Typically, the communication network 40 is a combination of a mobile communication network and the Internet or a VPN.
[0011] The general configuration of each store system 30 is the same. That is, the store system 30 is configured so that the store server 31, payment machine 32, communication server 33, and access point 34 can communicate via an in-store communication network 35. However, the store server 31, communication server 33, payment machine 32, access point 34, and in-store communication network 35 only need to have the same functions for realizing the operations described below, and do not need to be completely identical. Furthermore, some store systems 30 may be equipped with devices not shown in FIG. 1. Furthermore, some or all of the store systems 30 may not be equipped with a payment machine 32.
[0012] The store server 31 executes information processing for managing transactions carried out at one affiliated store. The store server 31 has, for example, the same functions as an existing POS server. The payment machine 32 calculates the price of each purchased item for each transaction registered by the transaction processing server 20 and processes the payment for the customer. The transaction data generated by the transaction processing server 20 for the payment may be provided to the payment machine 32 via the store server 31 or directly via the store server 31. The payment methods available to the payment machine 32 for the payment may include all or any of the well-known payment methods, such as cash payment, credit card payment, electronic money payment, points payment, and code payment (also known as mobile payment or smartphone payment). The payment machine 32 may be operated by either a store clerk or a customer. The payment machine 32 may be, for example, a self-service payment machine used in an existing semi-self-service POS system. The payment machine 32 may also have the functionality to process information for registering items as purchased items. In this case, the payment machine 32 may be, for example, a face-to-face POS terminal used in an existing POS system or a self-service POS terminal used in an existing self-service POS system.
[0013] The communication server 33 performs communication processing for the store server 31 and the accounting machine 32 to exchange data with the transaction processing server 20 and the like via the communication network 40 . The access point 34 performs communication processing to enable the mobile terminal 10 to access the in-store communication network 35 via wireless communication. For example, a well-known communication device that performs wireless communication according to the IEEE802.11 standard can be used as the access point 34. The access point 34 is provided so that the mobile terminal 10 located near the entrance of the affiliated store can communicate wirelessly. The access point 34 is preferably installed so that the mobile terminal 10 carried by a customer can communicate wirelessly immediately after the customer enters the affiliated store through the entrance. Depending on the affiliated store, multiple access points 34 may be installed in one store system 30. The in-store communication network 35 may be the Internet, VPN, LAN, public communication network, mobile communication network, or the like, either alone or in appropriate combination. Typically, however, the in-store communication network 35 is a LAN.
[0014] FIG. 2 is a block diagram showing the main circuit configuration of the mobile terminal 10. As shown in FIG. The mobile terminal 10 includes a processor 11, a main memory 12, an auxiliary storage unit 13, a touch panel 14, a camera 15, a wireless communication unit 16, a mobile communication unit 17, and a transmission path 18. The processor 11 is capable of communicating with the main memory 12, the auxiliary storage unit 13, the touch panel 14, the camera 15, and the mobile communication unit 17 via the transmission path 18. The processor 11, the main memory 12, and the auxiliary storage unit 13 are connected by the transmission path 18 to form a computer for controlling the mobile terminal 10.
[0015] The processor 11 corresponds to the central part of the computer. The processor 11 executes information processing to realize various functions of the mobile terminal 10 in accordance with information processing programs such as an operating system and application programs. The processor 11 is, for example, a CPU (central processing unit).
[0016] The main memory 12 corresponds to the main storage portion of the computer. The main memory 12 includes a nonvolatile memory area and a volatile memory area. The main memory 12 stores the information processing program in the nonvolatile memory area. The main memory 12 may store data required for the processor 11 to execute information processing in either the nonvolatile or volatile memory area. The main memory 12 uses the volatile memory area as a work area where data is rewritten by the processor 11 as appropriate. The nonvolatile memory area is, for example, ROM (read only memory). The volatile memory area is, for example, RAM (random access memory).
[0017] The auxiliary storage unit 13 corresponds to the auxiliary storage portion of the computer. As the auxiliary storage unit 13, a storage unit using a well-known storage device such as an EEPROM (electric erasable programmable read-only memory), an HDD (hard disc drive), or an SSD (solid state drive) can be used. The auxiliary storage unit 13 stores data used by the processor 11 when performing various processes, or data created by the processes in the processor 11. The auxiliary storage unit 13 may also store the information processing program.
[0018] The touch panel 14 is a display device that displays various screens such as an operation screen, etc. The touch panel 14 is an operation device that receives operations according to the operation screen. The camera 15 includes an optical system and an image sensor, and generates image data representing an image within a field of view formed by the optical system using the image sensor.
[0019] The wireless communication unit 16 transmits and receives data via wireless communication in accordance with a wireless communication protocol to and from the access point 34. As the wireless communication unit 16, for example, a well-known communication device conforming to the IEEE802.11 standard can be used. The mobile communication unit 17 is an interface for data communication via the communication network 40. As the mobile communication unit 17, for example, a well-known communication device for performing data communication via a mobile communication network can be used. The transmission path 18 includes an address bus, a data bus, and control signal lines, and transmits data and control signals exchanged between the connected components.
[0020] The auxiliary memory unit 13 stores a smartphone POS app AP11, which is one of the information processing programs. The smartphone POS app AP11 is an application program that describes the information processing described below for making the mobile terminal 10 function as a user interface for the transaction processing system 100. The smartphone POS app AP11 is shared by multiple mobile terminals 10. The auxiliary memory unit 13 also uses part of its storage area as storage area for a management database DB11 and a screen file group SF11. The management database DB11 is a database for managing screen files included in the screen file group SF11. The screen file group SF11 includes multiple screen files representing operation screens. In other words, the auxiliary memory unit 13 is an example of a storage device that stores multiple operation screens.
[0021] The mobile terminal 10 may be implemented using hardware such as a smartphone or tablet device equipped with a data communication function. The mobile terminal 10 is typically transferred without the smartphone POS app AP11, management database DB11, and screen file group SF11 stored in the auxiliary storage unit 13. The mobile terminal 10 may then be configured by writing the smartphone POS app AP11 to the auxiliary storage unit 13 in response to an operator's operation. The smartphone POS app AP11 may be transferred by recording it on a removable recording medium such as a magnetic disk, a magneto-optical disk, an optical disk, or a semiconductor memory, or by communication via the communication network 40. The management database DB11 and screen file group SF11 are downloaded from the transaction processing server 20 and written to the auxiliary storage unit 13 by the processor 11, as described below. At least a portion of the smartphone POS app AP11, management database DB11, and screen file group SF11 may be stored in the main memory 12.
[0022] FIG. 3 is a block diagram showing the main circuit configuration of transaction processing server 20. Transaction processing server 20 includes processor 21, main memory 22, auxiliary storage unit 23, communication unit 24, and transmission path 25. Processor 21, main memory 22, auxiliary storage unit 23, and communication unit 24 are capable of communicating with each other via transmission path 25. Processor 21, main memory 22, and auxiliary storage unit 23 are connected by transmission path 25 to form a computer for controlling transaction processing server 20.
[0023] The processor 21 corresponds to the central part of the computer. The processor 21 executes information processing to realize various functions of the transaction processing server 20 in accordance with information processing programs such as an operating system and application programs. The processor 21 is, for example, a CPU.
[0024] 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 the information processing program in the nonvolatile memory area. The main memory 22 may store data required for the processor 21 to execute information processing in either the nonvolatile or volatile memory area. The main memory 22 uses the volatile memory area as a work area where data is rewritten by the processor 21 as appropriate. The nonvolatile memory area is, for example, a ROM. The volatile memory area is, for example, a RAM.
[0025] The auxiliary storage unit 23 corresponds to the auxiliary storage portion of the computer. As the auxiliary storage unit 23, a storage unit using a well-known storage device such as an EEPROM, HDD, or SSD can be used. The auxiliary storage unit 23 stores data used by the processor 21 when performing various processes, or data created by the processes in the processor 21. The auxiliary storage unit 23 may also store the information processing program.
[0026] The communication unit 24 performs communication processing for data communication via the communication network 40. As the communication unit 24, for example, a well-known internet connection device can be applied. The transmission path 25 includes an address bus, a data bus, and control signal lines, and transmits data and control signals exchanged between the connected components.
[0027] The auxiliary memory unit 23 stores a transaction processing application AP21. The transaction processing application AP21 is an application program that describes information processing for enabling customers to shop at each affiliated store using the mobile terminal 10. The auxiliary memory unit 23 also uses part of its memory area as memory area for a store database DB21, a management database DB22, and a screen file group SF21. The store database DB21 is a database for managing affiliated stores. The management database DB22 is a database for managing screen files included in the screen file group SF21. The screen file group SF21 includes multiple screen files that represent operation screens.
[0028] The store database DB21 is a collection of data records associated with each affiliated store. One data record includes, for example, an affiliated store identifier (hereinafter referred to as an affiliated store ID), store name, company identifier, company name, and SSID (service set identifier) for the associated affiliated store. The type of information included in a data record of the store database DB21 is arbitrary, but it should at least include the affiliated store ID and SSID. The affiliated store ID is an identifier that allows an associated affiliated store to be distinguished from other affiliated stores. The SSID is an identifier assigned to the access point 34 included in the store system 30 installed in the associated affiliated store. Instead of the SSID, another identifier that can identify the access point 34, such as a MAC address, may be used.
[0029] FIG. 4 is a diagram showing a typical structure of a data record DR11 contained in the management databases DB11 and DB22. The management databases DB11 and DB22 are a collection of data records DR11, the structure of which is shown in FIG. 4. Data record DR11 is associated with an affiliated store and includes fields F11, F12, F13, etc. Field F11 contains the affiliated store ID of the associated affiliated store. Fields F12 and subsequent fields contain screen management data for each of a plurality of operation screens that receive customer operations related to transaction processing instructions. The screen management data includes a screen identifier (hereinafter referred to as a "screen ID") and a file name. The screen ID is an identifier used by the processors 11 and 21 in the mobile terminal 10 and transaction processing server 20 to identify the operation screens that receive instructions at each stage of the transaction processing. In this embodiment, a single screen ID can be assigned to a different operation screen for each affiliated store. The file name is a name used to identify a screen file representing an operation screen assigned to a screen ID included in the same screen management data for the associated affiliated store. The assignment of an operation screen to a screen ID may be determined arbitrarily, for example, by a staff member at the affiliated store.
[0030] In principle, the management database DB11 includes data records DR11 associated with all member stores. In principle, the management database DB22 includes data records DR11 associated with some member stores. However, the management database DB22 may include data records DR11 associated with all member stores.
[0031] The screen files included in the screen file groups SF11 and SF21 are data files identified by file names included in the screen management data set in each field from field F12 onwards of data record DR11 included in the management databases DB11 and DB22 stored in the same auxiliary memory units 13 and 23.
[0032] The hardware of transaction processing server 20 may be, for example, a general-purpose server device. Transaction processing server 20 is generally transferred in a state in which transaction processing application AP21 is stored in auxiliary storage unit 23, but management database DB22 and screen file group SF21 are not. However, transaction processing application AP21 may be transferred separately from the hardware in a state in which transaction processing application AP21 is not stored in auxiliary storage unit 23, or in which a different version of the same application program is stored in auxiliary storage unit 23. Transaction processing server 20 may be configured by writing transaction processing application AP21 to auxiliary storage unit 23 in response to an operator's operation. Transaction processing application AP21 may be transferred by recording it on a removable recording medium such as a magnetic disk, magneto-optical disk, optical disk, or semiconductor memory, or by communication via communication network 40. Management database DB22 and screen file group SF21 are written to auxiliary storage unit 23 by processor 21 under the direction of an administrator of transaction processing server 20. At this time, processor 21 writes the management database DB22 and screen file group SF21, which have been read from a removable recording medium or obtained through communication via communication network 40, into auxiliary storage unit 23. Alternatively, processor 21 writes the management database DB22 and screen file group SF21, which have been generated under the instruction of an administrator of transaction processing server 20, into auxiliary storage unit 23. Note that at least a portion of transaction processing application AP21, management database DB22, and screen file group SF21 may be stored in main memory 22.
[0033] Next, the operation of the transaction processing system configured as described above will be described. Note that the contents of the various processes described below are merely examples, and it is possible to change the order of some of the processes, omit some of the processes, or add other processes as appropriate. For example, in the following description, in order to clearly explain the characteristic operations of this embodiment, explanation of some of the processes will be omitted. For example, if some kind of error occurs, processing may be performed to deal with the error, but a description of such processing will be omitted.
[0034] When a customer wishes to shop at an affiliated store using the transaction processing service provided by the transaction processing system 100, the customer enters the affiliated store carrying a mobile terminal 10 that has activated information processing (hereinafter referred to as UI processing) according to the smartphone POS app AP11. The access point 34 periodically transmits a packet (hereinafter referred to as a beacon) containing the SSID assigned to it. When a customer enters a member store, the wireless communication unit 16 of the mobile terminal 10 carried by the customer receives the beacon when communication with the access point 34 becomes possible. Note that beacons are also transmitted from communication devices other than the access points included in the store system 30, and the wireless communication unit 16 also receives such beacons. The wireless communication unit 16 may receive multiple beacons.
[0035] FIG. 5 is a flowchart of the UI processing in the processor 11. In ACT 1, the processor 11 waits for reception of the SSID. If the beacon is received by the wireless communication unit 16 as described above, the processor 11 determines YES and proceeds to ACT 2. At this time, the processor 11 stores the SSID included in the received beacon in the main memory 12 or the auxiliary storage unit 13.
[0036] In ACT2, processor 11 makes an entry inquiry. For example, processor 11 transmits inquiry data for the entry inquiry from mobile communication unit 17 to communication network 40, addressed to transaction processing server 20. For example, processor 11 causes the inquiry data to include at least identification data for identifying that the inquiry is about whether the store is an affiliated store and the SSID included in the beacon received by wireless communication unit 16.
[0037] The inquiry data transmitted to transaction processing server 20 via communication network 40 is received by communication unit 24. In response, processor 21 starts information processing (hereinafter referred to as transaction processing) in accordance with transaction processing application AP21. If, while processor 21 is executing the transaction processing started here, inquiry data transmitted from another mobile terminal 10 is received by communication unit 24, processor 21 executes the new transaction processing in parallel with the transaction processing already being executed. In other words, processor 21 may execute multiple transaction processing in parallel, each targeted at multiple mobile terminals 10. In the following description of transaction processing, when simply referred to as "mobile terminal 10," it refers to the mobile terminal 10 that is the target of that transaction processing.
[0038] FIG. 6 is a flowchart of the transaction processing in the processor 21. In ACT21, the processor 21 checks whether the mobile terminal 10 that made the inquiry is located inside a member store. For example, the processor 21 checks whether any of the SSIDs included in the inquiry data matches an SSID included in a data record in the store database DB21. If no matching SSID is found, the processor 21 determines that the mobile terminal 10 is not located inside a member store, judges NO, and proceeds to ACT22.
[0039] In ACT22, the processor 21 notifies the inquiring mobile terminal 10 that the customer has not entered the affiliated store. For example, the processor 21 transmits response data including identification data for identifying that the notification is of a non-entry status from the communication unit 24 to the communication network 40, addressed to the inquiring mobile terminal 10. The processor 21 then terminates the transaction processing.
[0040] If processor 21 finds an SSID in store database DB21 that matches any of the SSIDs included in the inquiry data in ACT 21, it determines that the user is located inside an affiliated store and proceeds to ACT 23. At this time, processor 21 determines that the store identified by the affiliated store ID included in the data record containing the found SSID is the affiliated store that has been entered.
[0041] In ACT23, the processor 21 notifies the inquiring mobile terminal 10 that the user has entered the affiliated store. For example, the processor 21 transmits response data including identification data for identifying that the notification is of entry to the affiliated store from the communication unit 24 to the communication network 40, addressed to the inquiring mobile terminal 10. For example, the processor 21 further includes in the response data a management record related to the entered affiliated store. The processor 21 determines that the management record is a data record DR11 included in the management database DB22, in which the affiliated store ID of the entered affiliated store is set in field F11.
[0042] The response data transmitted by the communication network 40 to the mobile terminal 10 is received by the mobile communication unit 17 .
[0043] If the processor 11 in the mobile terminal 10 makes an inquiry in ACT2 in FIG. 5, the process proceeds to ACT3.
[0044] In ACT3, the processor 11 waits for a response. If the response data is received by the communication unit 24 as described above, the processor 11 determines YES and proceeds to ACT4.
[0045] In ACT4, processor 11 checks whether the response data is a store entry notification. If processor 11 receives response data notifying that the user has not yet entered the store, it determines the answer as NO and returns to the standby state of ACT1. When processor 11 returns to the standby state of ACT1 in this way, it is preferable that processor 11 take measures to prevent repeated inquiries about the same SSID. For example, processor 11 determines the answer as YES only if an SSID different from the SSID included in the inquiry data the previous time ACT2 was executed is received.
[0046] If response data notifying the customer of store entry is received, the processor 11 determines YES in ACT4 and proceeds to ACT5. At this time, the processor 11 stores the management record included in the response data in the main memory 12 or the auxiliary storage unit 13. The management record includes the affiliated store ID of the affiliated store entered, and the affiliated store ID corresponds to a store identifier for identifying the store visited by the customer. Thus, by the processor 11 executing information processing based on the smartphone POS app AP11, the computer with the processor 11 as its central part functions as an identifier acquisition means.
[0047] In ACT5, processor 11 checks whether the screen file group SF11 contains a screen file group related to the entered affiliated store. For example, processor 11 searches the screen files contained in screen file group SF11 for screen files identified by all file names contained in the management record included in the response data. If processor 11 finds all the corresponding screen files, it determines that the corresponding screen file group exists and judges YES, and proceeds to ACT6.
[0048] In ACT6, the processor 11 notifies the transaction processing server 20 that the screen file has been downloaded. For example, the processor 11 transmits notification data for notifying the completion of download from the mobile communication unit 17 to the communication network 40, addressed to the transaction processing server 20. For example, the processor 11 includes identification data in the notification data to identify that the notification is a notification that the screen file has been downloaded. The processor 11 then proceeds to ACT9.
[0049] If even one corresponding screen file is not found, the processor 11 determines that there is no corresponding screen file group and determines NO, and proceeds to ACT7. In ACT7, the processor 11 downloads the screen file group. For example, the processor 11 transmits request data for requesting the download of the screen file group from the mobile communication unit 17 to the communication network 40, addressed to the transaction processing server 20. For example, the processor 11 includes identification data for identifying the request as a download request in the request data. The processor 11 may include at least one of the screen ID and file name of the screen file that was not found in the request data. If the mobile communication unit 17 receives a screen file transmitted from the transaction processing server 20 in response to this request, the processor 11 adds the screen file to the screen file group SF11. Note that the size of the storage area for storing the screen file group SF11 may be limited. In such a case, if adding a new screen file would cause the data size of the screen file group SF11 to exceed the limited size, the processor 11 deletes screen files that meet predetermined conditions from the screen file group SF11. Alternatively, the processor 11 may periodically delete screen files that meet predetermined conditions from the screen file group SF11, thereby ensuring that there is always room for adding new screen files. In this way, the processor 11 executes information processing based on the smartphone POS application AP11, and the computer with the processor 11 as its central part functions as a screen acquisition means.
[0050] In the transaction processing server 20, after notifying the customer of the store entry in ACT23 in FIG. 6, the processor 21 transitions to a standby state in ACT24 and ACT25. In ACT24, the processor 21 checks whether or not a notification has been sent to the effect that the download has been completed. If the processor 21 cannot confirm the notification, it determines that the result is NO and proceeds to ACT25. In ACT 25, the processor 21 checks whether a download has been requested. If the processor 21 cannot confirm the request, it determines NO and returns to ACT 24. Thus, the processor 21 waits for a notification that the download has been completed or a request for download in the standby state of ACT 24 and ACT 25. Then, if request data for requesting a download is received by the communication unit 24, the processor 21 determines YES in ACT 25 and proceeds to ACT 26.
[0051] In ACT26, the processor 21 transmits the screen files in response to the request. For example, if the request data does not include a screen ID or a file name, the processor 21 reads all screen files identified by the file names included in the data record DR11 included as a management record in the notification data in ACT23 from the screen file group SF21, and transmits them from the communication unit 24 to the requesting mobile terminal 10 via the communication network 40. Also, for example, if the request data includes a screen ID or a file name, the processor 21 reads all screen files identified by the screen IDs or file names from the screen file group SF21, and transmits them from the communication unit 24 to the requesting mobile terminal 10 via the communication network 40. At this time, the processor 21 notifies the requesting mobile terminal 10 of the screen IDs and file names of the screen files to be transmitted.
[0052] When the screen file transmitted from the transaction processing server 20 is received by the mobile communication unit 17 as described above, the processor 11 of the mobile terminal 10 adds the screen file to the screen file group SF11. Then, when the screen file transmitted from the transaction processing server 20 has been added to the screen file group SF11, the download of the screen file as ACT7 in Figure 5 is completed.
[0053] In ACT8, the processor 11 updates the management database DB11 to reflect the results of the download of the above screen file. For example, the processor 11 adds to the management database DB11 a new field in which screen management data including the screen ID and file name notified together with the screen file added to the screen file group SF11 in ACT7 is set.
[0054] When the processor 21 in the transaction processing server 20 has finished transmitting all the screen files to be transmitted, it proceeds to ACT27 in Fig. 6. If the processor 21 is notified that the files have been downloaded, it determines YES in ACT24, skips ACT26, and proceeds to ACT27. As ACT27, the processor 21 executes a registration process. The registration process is a process of registering a product that a customer has taken out of a display area as a purchased product in response to an instruction given by the customer operating the mobile terminal 10. Note that the processor 21 may execute a part of the registration process in cooperation with a store server 31 provided in the store where the mobile terminal 10 is located. The processor 21 may acquire data such as the product name and sales price from the store server 31, for example.
[0055] As ACT28, processor 21 executes the checkout process. The checkout process is a process for determining the price of the products registered as purchased products in the registration process and having the customer pay that price. Note that processor 21 may execute some of the checkout process in cooperation with a store server 31 and a payment machine 32 installed in the store where mobile terminal 10 is located. For example, if the customer wishes to pay using payment machine 32, processor 21 may send information for the checkout to payment machine 32 and leave subsequent processing to payment machine 32.
[0056] The contents of the registration process and the transaction process may be arbitrary. The registration process and the transaction process may be similar to those of an existing smartphone POS system, for example. However, in the registration process and the transaction process, the processor 21 requests the mobile terminal 10 to display various operation screens to receive instructions from the customer. The processor 21 then proceeds with the process according to the instructions given by the operation on the displayed operation screen. In order to instruct the display of the operation screen, the processor 21 sends instruction data from the communication unit 24 to the communication network 40, addressed to the mobile terminal 10 that made the inquiry. For example, the processor 21 may include in the instruction data the operation screen's display The command includes identification data for identifying the command and the screen ID of the operation screen to be displayed. The registration process and the accounting process are both examples of information processing for processing a transaction. Thus, by the processor 21 executing information processing based on the transaction processing application AP21, the computer with the processor 21 as its central part functions as a processing means.
[0057] In the mobile terminal 10, the processor 11 proceeds from ACT 6 or ACT 8 to ACT 9 in FIG. In ACT 9, processor 11 waits for a display instruction. When the instruction data transmitted from transaction processing server 20 as described above for instructing the mobile communication unit 17 to display the operation screen is received by processor 11, processor 11 determines the answer as YES and proceeds to ACT 10. In ACT10, processor 11 displays an operation screen on touch panel 14 in response to an instruction from transaction processing server 20. Then, with the operation screen displayed on touch panel 14, processor 11 transitions to a standby state for ACT11, ACT12, and ACT13.
[0058] In ACT 11, the processor 11 checks whether an instruction to display the operation screen has been issued. If the processor 11 cannot confirm the instruction, it determines NO and proceeds to ACT 12. In ACT 12, the processor 11 checks whether an operation for giving an instruction has been performed on the currently displayed operation screen. If the processor 11 cannot confirm the operation, it determines NO and proceeds to ACT 13. In ACT 13, the processor 11 checks whether or not an end notification has been sent. If the processor 11 cannot confirm the notification, it determines "NO" and returns to ACT 11. Thus, in the standby state of ACT11 to ACT13, the processor 11 waits for a display instruction, an operation, or an end notification.
[0059] The customer gives various instructions by operating in accordance with the operation screen displayed on the touch panel 14. An operation is, for example, tapping an operation object such as a soft key displayed on the operation screen. An operation is, for example, holding a product barcode over the camera 15 so that the product barcode appears in the image captured by the camera 15 and displayed on the operation screen. The operation may be any of various operations that can be performed on an existing communication terminal such as a smartphone or tablet terminal. Alternatively, the operation may be performed using an operation device not shown in FIG. 2, such as a hard key.
[0060] If an operation for giving an instruction is performed based on the operation screen being displayed in this way, the processor 11 determines YES in ACT12 and proceeds to ACT14. In ACT14, processor 11 notifies transaction processing server 20 of the performed operation. For example, processor 11 transmits notification data for notifying the operation from mobile communication unit 17 to communication network 40, addressed to transaction processing server 20. For example, processor 11 includes in the notification data identification data for identifying that it is an operation notification and an operation code for identifying the operation. For example, processor 11 includes in the notification data an operation code associated with the operation object that was the target of the above operation, from among the operation codes shown in a screen file representing the currently displayed screen and associated with each operation object on the screen.
[0061] At this time, processor 11 inputs the customer's instructions through operations performed in accordance with the operation screen displayed on touch panel 14 as a display device. Processor 11 then notifies transaction processing server 20 as a server device of the input instructions. In this way, processor 11 executes information processing based on smartphone POS app AP11, and the computer with processor 11 as its central part functions as input means and notification means. Then, the processor 11 returns to the standby state of ACT11 to ACT13.
[0062] If the need arises to display a new operation screen during the registration process or the transaction process, processor 21 in transaction processing server 20 instructs mobile terminal 10 to display that operation screen in the same manner as described above. In response to this instruction, processor 11 of mobile terminal 10 determines YES in ACT 11 and returns to ACT 10. That is, processor 11 displays a new operation screen in response to the instruction on touch panel 14 as described above in ACT 10, and then transitions to a standby state in ACT 11 to ACT 13.
[0063] When the processor 21 in the transaction processing server 20 completes the transaction processing in ACT28 in FIG. 6, it proceeds to ACT29. In ACT29, the processor 21 notifies the mobile terminal 10 of the completion of the transaction. For example, the processor 21 transmits notification data for notifying the mobile terminal 10 of the completion of the transaction from the communication unit 24 to the communication network 40. For example, the processor 21 includes identification data in the notification data for identifying that the notification is of the completion of the transaction. Then, the processor 21 ends the transaction processing of FIG.
[0064] When the notification data sent as described above from the transaction processing server 20 to notify the completion of the transaction is received by the mobile communication unit 17, the processor 11 of the mobile terminal 10 judges YES in ACT13 in Figure 5 and terminates the UI processing shown in Figure 5.
[0065] The operation when an operation is performed based on the operation screen will be described in more detail below. FIG. 7 is a flowchart showing an example of a part of the registration process. As ACT31, the processor 21 instructs the mobile terminal 10 to display a list screen. The list screen is a screen showing a list of registered purchased items. Thus, the processor 21 executes information processing based on the transaction processing application AP21, and the computer having the processor 21 as its central part functions as an instruction means for instructing the mobile terminal 10 on which operation screen to display.
[0066] FIG. 8 is a diagram showing an example of the list screen SC1. The list screen SC1 is one of the operation screens defined for a store named "ZZZ Supermarket." The list screen SC1 includes display areas AR11, AR12, and AR13 and buttons BU11, BU12, and BU13. The display area AR11 shows the store name. The display area AR12 shows the total number of purchased items and the total price of the purchased items. The display area AR13 shows a list of purchased items. The button BU11 is a soft key that allows the customer to declare that they want to cancel all purchased items and stop shopping. The button BU12 is a soft key that allows the customer to declare that they want to start scanning items to be registered as purchased items. The button BU13 is a soft key that allows the customer to declare that they want to start checkout.
[0067] FIG. 9 is a diagram showing an example of the list screen SC2. The list screen SC2 is one of the operation screens defined for a store named "YYY Tokyo Store." List screen SC2 includes display areas AR21, AR22, AR23 and buttons BU21, BU22. Display area AR21 shows the store name. Display area AR22 shows a list of purchased items. Display area AR23 shows the total number of purchased items and the total price of the purchased items. Button BU21 is a soft key that the customer presses to start scanning items to be registered as purchased items. The same operation code as button BU12 is assigned to button BU21. Button BU22 is a soft key that the customer presses to start payment. The same operation code as button BU13 is assigned to button BU22.
[0068] In order to make it easier to understand the difference between the list screen SC1 and the list screen SC2, the registration status of purchased products is the same in FIGS. 8 and 9. Display areas AR11 and AR12 have the same function, but display different contents, showing the store names of the respective stores. Display areas AR13 and AR22 are areas that display the same information, and have the same function, but are located at different positions on the screen. Display areas AR12 and AR23 are areas that display the same information, and have the same function, but are located at different positions on the screen. Buttons BU12 and BU21 are equivalent operation objects that receive operations for the same instructions, but are different in size, character string, and location. Buttons BU13 and BU22 are equivalent operation objects that receive operations for the same instructions, but are different in size, character string, and location. List screen SC2 does not include an operation object equivalent to button BU11 on list screen SC1.
[0069] The same screen ID is assigned to list screen SC1 and list screen SC2. The file name of the screen file representing list screen SC1 is set together with the above screen ID in one of fields F12 and subsequent fields of data record DR11 associated in management databases DB11 and DB22 with a store named "ZZZ Supermarket." Also, the file name of the screen file representing list screen SC2 is set together with the above screen ID in one of fields F12 and subsequent fields of data record DR11 associated in management databases DB11 and DB22 with a store named "YYY Tokyo Store."
[0070] 7 is issued to a mobile terminal 10 located at a store named "ZZZ Supermarket" (hereinafter referred to as Store A), the processor 11 of the mobile terminal 10, as ACT10 in FIG. 5, displays, for example, a list screen SC1 as shown in FIG. 8 on the touch panel 14. On the other hand, if a display instruction by the processor 21, as ACT31 in FIG. 7, is issued to a mobile terminal 10 located at a store named "YYY Tokyo Store" (hereinafter referred to as Store B), the processor 11 of the mobile terminal 10, as ACT10 in FIG. 5, displays, for example, a list screen SC2 as shown in FIG. 9 on the touch panel 14. In this way, the operation screen displayed on the mobile terminal 10 in response to the display instruction by the processor 21, as ACT31 in FIG. 7, differs depending on which store the mobile terminal 10 is located at. In other words, the processor 11 displays, on the touch panel 14, as a display device carried by the customer, an operation screen for the customer in a format corresponding to the store identified by the SSID acquired in ACT1. Thus, by the processor 11 executing information processing based on the smartphone POS application AP11, the computer with the processor 11 as its central part functions as a display control means.
[0071] After the processor 21 has finished issuing the display instruction in ACT 31 in FIG. 7, the processor 21 proceeds to ACT 32 with the list screen still displayed. In ACT 32, the processor 21 waits for notification of an operation on the list screen. Then, as will be described later, if notification of an operation is made from the mobile terminal 10, the processor 21 determines the answer as YES and proceeds to ACT 33.
[0072] In ACT 33, the processor 21 checks whether or not a command to start scanning of the product has been issued. If the command has not been issued, the processor 21 determines the result as NO and proceeds to ACT 34. In ACT 34, the processor 21 checks whether or not a shopping cancellation has been specified. If the processor 21 cannot confirm such a specification, it determines the answer as NO and proceeds to ACT 35. In ACT 35, the processor 21 checks whether or not the start of the transaction has been designated. If the processor 21 cannot confirm that the designation has been made, it determines that the decision is NO and returns to ACT 33. Thus, in ACT33 to ACT35, the processor 21 waits for a command to start scanning, stop scanning, or start accounting to be specified.
[0073] When a customer attempts to register a product as a purchased product, the customer performs a predetermined operation on the displayed list screen to instruct the start of scanning. For example, in store A, the customer taps button BU12 displayed on list screen SC1. For example, in store B, the customer taps button BU21 displayed on list screen SC2. As described above, the same operation code is assigned to buttons BU12 and BU21. Therefore, in response to these operations, the processor 11 notifies the customer of the operation to be performed in ACT14 in FIG. 5, which instructs the customer to perform the same operation to instruct the start of scanning.
[0074] If the processor 21 in the transaction processing server 20 is notified of an operation to instruct the start of scanning as described above, the processor 21 determines YES in ACT33 and proceeds to ACT36. The processor 21 executes an addition process for adding a new product as a purchased product as ACT 36. This addition process may be a well-known process such as that performed in an existing POS system.
[0075] If a customer wishes to cancel all registered purchased items and discontinue shopping, the customer performs a predetermined operation to instruct the customer to discontinue shopping on the displayed list screen. For example, in store A, the customer taps button BU11 displayed on list screen SC1. In store B, the customer cannot perform the corresponding operation. In response to the above operation, the processor 11 notifies the customer of the operation to be performed in ACT14 in FIG. 5 to instruct the customer to discontinue shopping.
[0076] If the processor 21 in the transaction processing server 20 is notified of the operation for instructing cancellation as described above, the processor 21 determines YES in ACT34 and proceeds to ACT37. The processor 21 executes a cancellation process to cancel all registered purchased items as ACT 37. This cancellation process may be a well-known process such as that performed in existing POS systems.
[0077] The addition process in ACT36 and the cancellation process in ACT37 are both examples of information processing for processing a transaction with a customer. That is, the processor 21 executes information processing for processing a transaction in accordance with instructions from the customer input and notified via the mobile terminal 10. In this way, the processor 21 executes information processing based on the transaction processing application AP21, and the computer with the processor 21 as its central part functions as a processing means.
[0078] If a customer wishes to start a transaction, the customer performs a predetermined operation on the displayed list screen to instruct the customer to start the transaction. For example, in store A, the customer taps button BU13 displayed on list screen SC1. For example, in store B, the customer taps button BU22 displayed on list screen SC2. As described above, the same operation code is assigned to buttons BU13 and BU22. Therefore, in response to these operations, processor 11 notifies the customer of the operation to be performed in ACT14 in FIG. 5, which instructs the customer to start the transaction in a similar manner. When the processor 21 in the transaction processing server 20 receives notification of the operation to start the transaction as described above, it determines YES in ACT 35 and ends the registration process. In this case, the processor 21 proceeds to ACT 28 in Figure 6 and starts the transaction process.
[0079] As described above, transaction processing system 100 receives customer operations through the same UI processing on mobile terminal 10 for transactions at any affiliated store. Therefore, customers do not need to use different applications depending on the store. Furthermore, transaction processing system 100 makes it possible to display different operation screens on mobile terminal 10 at each affiliated store, highlighting the uniqueness of each store and providing smartphone POS services as if they were unique to each store.
[0080] Furthermore, the transaction processing system 100 processes transactions at any affiliated store using a common transaction processing by the transaction processing server 20. Therefore, there is no need to perform the transaction processing individually at each store system 30, and it is possible to easily realize a smartphone POS service.
[0081] Furthermore, the transaction processing system 100 identifies the affiliated store that the customer enters by using a beacon transmitted by the access point 34 of the store system 30. Therefore, the customer does not have to go through the trouble of specifying the store.
[0082] Furthermore, in the mobile terminal 10, if a screen file related to an operation screen assigned to the entered affiliated store is included in the screen file group SF11, the processor 11 causes the touch panel 14 to display the operation screen based on the corresponding screen file. Therefore, there is no need to obtain a screen file from an external source every time an operation screen is displayed.
[0083] Furthermore, if the screen file group SF11 does not include a screen file related to the operation screen assigned to the affiliated store that the user has entered, the processor 11 of the mobile terminal 10 downloads the corresponding screen file promptly after entering the affiliated store, thereby enabling the subsequent operation screen to be displayed promptly.
[0084] This embodiment can be modified in various ways as follows. An identifier such as an SSID assigned to the access point 34 provided in the member store may be used as the store identifier as is.
[0085] A part or all of the information processing for processing a transaction with a customer may be executed by the processor 11 in the mobile terminal 10. In this case, the computer with the processor 11 as its central part has the function of processing means.
[0086] The processor 11 of the mobile terminal 10 may access the store database DB21 to acquire the affiliated store ID. In this case, the store database DB21 may be stored in any storage device other than the auxiliary storage unit 23 as long as it is accessible from the processor 11.
[0087] The screen file of the operation screen to be displayed on the mobile terminal 10 may be determined by the transaction processing server 20 or another server device. In this case, the device that made the determination specifies the screen file to the mobile terminal 10. Then, the processor 11 of the mobile terminal 10 displays a screen based on the specified screen file on the touch panel 14. The screen file may be specified to the mobile terminal 10 by notification of the file name or by transmission of the screen file.
[0088] The functions of the transaction processing server 20 may be realized by distributed processing using a plurality of server devices.
[0089] The processor 11 in the mobile terminal 10 may obtain an identifier for identifying the store visited by the customer from the store server 31 by communication via the access point 34. Alternatively, the processor 11 may obtain an identifier transmitted from a device other than the access point 34 that transmits any identifier.
[0090] The display device that displays the operation screen is not limited to the touch panel 14, and may be a device dedicated to display. Furthermore, the display device that displays the operation screen does not have to be provided in the mobile terminal 2. For example, the operation screen may be displayed on a display device provided in another terminal device that can directly communicate wirelessly with the mobile terminal 10.
[0091] Some or all of the functions realized by the processors 11 and 21 through information processing can be realized by hardware that executes information processing not based on a program, such as a logic circuit, etc. Each of the above functions can also be realized by combining the above hardware, such as the logic circuit, with software control.
[0092] Although several 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 embodied 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 and spirit of the invention, and are also included in the scope of the invention and its equivalents as defined in the claims. The inventions described in the original claims of this application are set forth below. [Appendix 1] Identifier acquisition means for acquiring a store identifier for identifying the store visited by the customer; a display control means for displaying an operation screen for the customer on a display device carried by the customer in a format corresponding to the store identified by the store identifier acquired by the identifier acquisition means; an input means for inputting instructions from the customer by performing an operation in accordance with the operation screen displayed by the display device; A transaction processing system comprising: [Supplementary Note 2] A processing means for executing information processing for processing a transaction with the customer at the store in accordance with the instruction input by the input means; 2. The transaction processing system of claim 1, further comprising: [Supplementary Note 3] A mobile terminal including the identifier acquisition means, the display control means, and the input means, and a server device including the processing means, an instruction means provided in the server device for instructing the mobile terminal which operation screen to display; a notification means provided in the mobile terminal for notifying the server device of the instruction input by the input means; Furthermore, the display control means causes the display device to display the operation screen instructed by the instruction means; the processing means executes the information processing in response to the instruction notified by the notifying means. 2. A transaction processing system as described in Appendix 2. [Appendix 4] The mobile terminal further includes a storage device for storing a plurality of operation screens in formats corresponding to the plurality of stores, the display control means displays the operation screen of the plurality of operation screens stored in the storage device in a format corresponding to the store identified by the store identifier acquired by the identifier acquisition means; 10. A transaction processing system as described in Appendix 3. [Supplementary Note 5] A screen acquisition means for acquiring the corresponding operation screen from the server device and storing it in the storage device when the operation screen in a format corresponding to the store identified by the store identifier acquired by the identifier acquisition means is not stored in the storage device; 5. The transaction processing system of claim 4, further comprising: [Appendix 6] A computer provided in a mobile terminal having a display device, an identifier acquisition means for acquiring a store identifier for identifying the store visited by the customer; a display control means for displaying an operation screen for the customer on the display device in a format corresponding to the store identified by the store identifier acquired by the identifier acquisition means; an input means for inputting instructions from the customer by performing an operation in accordance with the operation screen displayed by the display device; An information processing program that makes it function as such. [Explanation of symbols]
[0093] 1 0...mobile terminal, 20...transaction processing server, 11, 21...processor, 12, 22...main memory, 13, 23...auxiliary memory unit, 14...touch panel, 15...camera, 16...wireless communication unit, 17...mobile communication unit, 18, 25...transmission path, 24...communication unit, 30...store system, 31...store server, 32...accounting machine, 33...communication server, 34...access point, 35...in-store communication network, 40...communication network, 100...transaction processing system.
Claims
1. A mobile terminal capable of communicating with a server device that processes transactions with customers in a store, A display device; a storage device for storing an operation screen corresponding to the store for inputting customer instructions regarding product registration; an identifier acquisition means for acquiring a store identifier for identifying the store visited by the customer; a display control means for causing the display device to display, in response to a request from the server device, an operation screen in which one or more of (1) the position in the operation screen of a display area showing the same information, (2) the size of an operation object for receiving the same operation, (3) the character string shown in the operation object, and (4) the position in the operation screen of the operation object are changed according to the store identified by the store identifier acquired by the identifier acquisition means among the operation screens stored in the storage device; an input means for inputting customer instructions regarding the registration of purchased products by performing operations according to the operation screen displayed on the display device; a notification means for notifying the server device of the instruction input by the input means; A mobile terminal comprising:
2. the server device has a storage unit that stores a plurality of different operation screens corresponding to a plurality of stores, a requesting means for requesting the server device to download an operation screen when the storage device does not store an operation screen corresponding to the store identified by the store identifier when the store identifier is acquired by the identifier acquiring means; The mobile terminal of claim 1 further comprising:
3. The device is capable of communicating with a server device that processes transactions with customers at the store, A display device; a storage device for storing an operation screen corresponding to the store for inputting customer instructions regarding product registration; A computer provided in a mobile terminal including: an identifier acquisition means for acquiring a store identifier for identifying the store visited by the customer; a display control means for causing the display device to display, in response to a request from the server device, an operation screen in which one or more of (1) the position in the operation screen of a display area showing the same information, (2) the size of an operation object for receiving the same operation, (3) the character string shown in the operation object, and (4) the position in the operation screen of the operation object are changed according to the store identified by the store identifier acquired by the identifier acquisition means among the operation screens stored in the storage device; an input means for inputting customer instructions regarding the registration of purchased products by performing operations according to the operation screen displayed on the display device; a notification means for notifying the server device of the instruction input by the input means; An information processing program that makes it function as such.
Citation Information
Patent Citations
Store information provision system, store information provision, and program for receiving provision of store information
JP2005332134A
Self-order system by personalized menu
JP2014052944A
Settlement system and program
JP2015060262A
Keyword corresponding town retrieval system capable of acquiring purpose information corresponding to keyword and town retrieval method
JP2016111375A