INFORMATION PROCESSING APPARATUS AND SERVER APPARATUS FOR STORE SYSTEM WITH PERIPHERAL DEVICE BROKERING

According to an embodiment, an information processing apparatus includes a device connection unit to allow a plurality of devices to be detachably connected thereto, a processor, and a network communication interface to communicate with a server apparatus. The processor receives from, the device connection unit, an input of first identification information from a first device connected to the device connection unit. The first identification information identifies a particular mobile terminal connected to the network. The processor notifies the server apparatus, via the network communication interface, of an association between the first identification information and second identification information of the information processing apparatus to cause the server apparatus to relay information between the mobile terminal and the information processing apparatus. The processor also executes an accounting processing, using one or more devices connected to the device connection unit, for receiving payments for items registered by the mobile terminal.

CROSS-REFERENCE TO RELATED APPLICATION

This application is based upon and claims the benefit of priority from Japanese Patent Application No. 2021-203707, filed Dec. 15, 2021, the entire contents of which are incorporated herein by reference.

FIELD

Embodiments described herein relate generally to an information processing apparatus and a server apparatus for retail store systems with peripheral device brokering, sharing, or the like.

BACKGROUND

In stores such as supermarkets, a system that enables purchasing of items using a mobile terminal, such as a smartphone or a tablet terminal, has been introduced. In such a system, in order to use various peripheral devices, such as a receipt printer, provided at the store, as part of a transaction, the mobile terminal can be connected to the peripheral device by wireless communication.

However, in this system described above, whenever the peripheral device is to be used, the mobile terminal and the device need to communicate with each other, which requires separately establishing a connection for each different device use, and this complicates the operations of the system. In addition, there is always a possibility that the connection between the mobile terminal and the peripheral device cannot be established at the required time, and thus there is room for improvement in terms of convenience for such a system.

DETAILED DESCRIPTION

In general, according to one embodiment, an information processing apparatus and a server apparatus that enable use of a peripheral-type device by a mobile terminal without requiring directly connecting the mobile terminal to the device are provided.

According to one embodiment, an information processing apparatus includes a device connection unit configured to allow a plurality of devices to be detachably connected thereto, a network communication interface configured to communicate with a server apparatus, and a processor. The processor is configured to receive from the device connection unit an input of first identification information from a first device connected to the device connection unit, the first identification information identifying a particular mobile terminal connected to the network; notify the server apparatus, via the network communication interface, of an association between the first identification information and second identification information of the information processing apparatus to cause the server apparatus to relay information between the particular mobile terminal and the information processing apparatus; and execute accounting processing for a commodity registered by the particular mobile terminal, the accounting processing using one or more devices connected to the device connection unit.

Hereinafter, certain example embodiments of an information processing apparatus and a server apparatus will be described with reference to the drawings. The example embodiments concern a checkout system at a retail store such as a supermarket, but disclosed embodiments are not limited to such an application nor to the specific details of the example embodiments.

FIG.1is a diagram illustrating an example of a configuration of a checkout system1. The checkout system1includes a mobile terminal10, a device broker20, a server apparatus30, and a clerk terminal40.

The mobile terminal10is connected to a network N by wireless communication via an access point or the like. In addition, the device broker20, the server apparatus30, and the clerk terminal40are connected to the network N in a wired or wireless manner. Here, the network N is, for example, a local area network (LAN) provided in the store.

The number of mobile terminals10, device brokers20, clerk terminals40, and server apparatuses30connected to the network N are not limited to the example illustrated inFIG.1. In some examples, the clerk terminal40may be wirelessly connected to the network N.

The mobile terminal10is a mobile device such as a smartphone or a tablet terminal. For example, the mobile terminal10may be a terminal device such as a smartphone owned by a customer or a clerk, or may be a terminal device lent to the customer by the store. In the latter case, the mobile terminal10may be, for example, a tablet terminal attached to a shopping cart (a so-called “cart terminal” or “cart POS”). For the present embodiment, the customer operates the mobile terminal10, but in other embodiments a store clerk may operate the mobile terminal10. Hereinafter, a customer who operates the mobile terminal10is also referred to as an “operator”.

The mobile terminal10executes a process for purchasing a commodity (hereinafter, also referred to as commodity sales data processing) in response to an operation by the operator. Specifically, the mobile terminal10executes a registration for registering a commodity to be purchased in response to the operation of the operator. That is, the mobile terminal10of the present embodiment functions as a registration machine that executes the registration of the commodity.

The device broker20is an example of an information processing apparatus. The device broker20allows various devices DV that may serve as peripheral equipment of the mobile terminal10to be connected to, or otherwise accessed by, the mobile terminal10. The device broker20is placed, for example, at a predetermined position in the store. Specifically, the device broker20includes a device connection unit205(refer toFIG.3) that allows one or a plurality of devices DV to be detachably connected thereto.

For example, a code reading device DVa capable of reading a code symbol such as a bar code or a two-dimensional code is connected to the device broker20as one type of a device DV. A wireless tag reading device DVb capable of reading (or writing) a wireless tag such as a radio frequency identifier (RFID) tag is connected to the device broker20as one type of a device DV. A printer DVc such as a receipt printer is connected to the device broker20as one type of a device DV. A card settlement device DVd that allows payment by a credit card is connected to the device broker20as one type of a device DV. A cash recycler DVe having a function of receiving money (banknotes or coins), sorting the money by denomination and storing the money, and a function of dispensing change from stored money is connected to the device broker20as one type of a device DV. A cash recycler DVe may also be referred to as a cash handler device, a cash handling device, a money handling device, currency handler, or the like.

The types and the numbers of the devices DV connected to the device broker20are not particularly limited, but at least a device DV that can be used for inputting association information (for example, a code reading device DVa), is connected to the device broker20.

In addition, in the present embodiment, a device DV that permits payment for the registered commodity is connected to the device broker20. The device broker20may also execute an accounting process (also referred to as a settlement) for registered commodities in cooperation with the connected devices DV. That is, the device broker20and the device DV of the present embodiment collectively function as an accounting machine that executes the accounting on the registered commodity in the commodity sales data processing.

The server apparatus30is, for example, a store server provided in the store. The server apparatus30integrally manages the checkout system1. For example, the server apparatus30stores and manages information related to the commodities sold in the store. In addition, the server apparatus30tracks/manages a state of each device broker20and a state of each device DV connected to the device broker20. The server apparatus30also manages the association between the mobile terminal10and the device broker20.

The clerk terminal40is a terminal device operated by a clerk (e.g., a store employee or the like) at the store. The clerk terminal40may be a stationary terminal device such as a personal computer (PC), or may be a mobile terminal device such as a smartphone.

In the checkout system1described above, the operator of the mobile terminal10registers a commodity for purchase using the mobile terminal10, and then pays for the registered commodity using a device DV connected to the device broker20. That is, the checkout system1realizes a checkout system of a type in which registration and accounting can be performed by the customer by himself/herself without interaction with the clerk (this is also referred to as a self-service type system or the like). In a system in which the clerk operates the mobile terminal10, the checkout system1can be of a type in which operations related to registration are performed by the clerk but operations related to settlement are performed by the customer (this is also referred to as a semi-self-service type system or a pre-handling type system).

Next, a configuration of devices of the checkout system1will be described. First, a hardware configuration of the mobile terminal10will be described with reference toFIG.2.FIG.2is a diagram illustrating an example of the hardware configuration of the mobile terminal10.

As illustrated inFIG.2, the mobile terminal10includes a central processing unit (CPU)101, a read only memory (ROM)102, and a random access memory (RAM)103.

The CPU101is an example of a processor and controls an operation of the mobile terminal10. The ROM102stores various programs. The RAM103is a workspace for loading the programs and various data. The CPU101, the ROM102, and the RAM103are connected via a bus or the like and constitute a control unit100. The control unit100executes various processes by the CPU101operating in accordance with a control program1051stored in the ROM102or a storage unit105and loaded into the RAM103.

The CPU101is connected to a communication unit104and the storage unit105via a bus or the like. The communication unit104is a wireless communication interface connectable to the network N. The communication unit104communicates with the server apparatus30via the network N.

The storage unit105is a storage device such as a hard disk drive (HDD), a solid-state drive (SSD), or a flash memory, and maintains stored content even when power is turned off. The storage unit105stores, for example, the control program1051.

The control program1051is for controlling the operation of the mobile terminal10. The control unit100(more specifically, the CPU101) executes with the control program1051to realize various functions.

The control program1051may include a communication program or setting information for automatically connecting to the server apparatus30. The storage unit105may store other data. For example, the storage unit105may store a commodity master3052, and the like.

In addition, the CPU101is connected to a display unit106, an operation unit107, and an imaging unit108via a bus or the like.

The display unit106includes a display device such as a liquid crystal display. The display unit106displays various screens under the control of the CPU101. For example, the display unit106displays an operation screen for supporting a registration operation of the commodity. The display unit106may include a touch panel.

The operation unit107includes various operation keys, pointing devices, user input devices, and the like to receive input operations of the operator of the mobile terminal10. The operation unit107may be a touch panel provided on a display surface of the display unit106.

The imaging unit108is an imaging device including an imaging element such as a charge coupled device (CCD) or a complementary MOS (CMOS) element. In the present embodiment, the imaging unit108is used to read a code symbol attached to the commodity.

Next, a hardware configuration of the device broker20will be described with reference toFIG.3.FIG.3is a diagram illustrating an example of the hardware configuration of the device broker20. In some examples, the device broker20may also be usable as, or at least correspond in outward appearance to, a self-service point-of-sale terminal, a semi-self-service point-of-sale terminal, a customer checkout kiosk, or the like.

As illustrated inFIG.3, the device broker20includes a CPU201, a ROM202, and a RAM203.

The CPU201is an example of a processor and controls an operation of the device broker20. The ROM202stores various programs. The RAM203is a workspace for loading the programs and various data. The CPU201, the ROM202, and the RAM203are connected via a bus or the like to constitute a control unit200. The control unit200executes various processes by the CPU201operating in accordance with a control program2061stored in the ROM202or a storage unit206and loaded into the RAM203.

In addition, the CPU201is connected to a communication unit204, the device connection unit205, and the storage unit206via a bus or the like. The communication unit204is a communication interface connectable to the network N. The communication unit204communicates with the server apparatus30via the network N.

The device connection unit205is also referred to as a connection unit, a device interface board, a peripheral device interface unit, or the like. The device connection unit205includes a plurality of interfaces that allow the device DV to be detachably connected thereto. The device connection unit205may include various interface types such as universal serial bus (USB) and/or RS-232C.

The storage unit206is a storage device such as an HDD, an SSD, or a flash memory, and maintains stored content even when power is turned off. The storage unit206stores, for example, the control program2061and a device management table2062.

The control program2061is for controlling the operations of the device broker20. The control unit200(more specifically CPU201) executes the control program2061to realize various functions.

The device management table2062is a data table for managing the state of the devices DV connected to the device broker20.FIG.4is a diagram illustrating an example of a data configuration of the device management table2062.

As illustrated inFIG.4, the device management table2062stores device state information illustrating the state of a device DV connected to the device broker20. The device state information includes, for example, a device ID and a state.

Here, the device ID is identification information for uniquely identifying each of the devices DV connected to the device broker20. The state is information indicating the present state of the device DV corresponding to the device ID. The state column stores, for example, entries such as “operating”, “idle” (standby), or “unusable” (due to occurrence of an abnormality) or the like. In addition, the state column may store information indicating a cause of an unusable state (e.g., an error code). For example, a cause of the unusable state, a paper out notice or the like may be stored in the state column in a case of the printer DVc, or a change empty notice or the like may be stored in the state column in a case of the cash recycler DVe.

The data configuration of the device management table2062is not limited toFIG.4. For example, the device management table2062may store the device state information in association with identification information for identifying each individual interface (interface ID) of the device connection unit205rather than (or in addition to) the device IDs of the connected devices DV per se. With such a data configuration, it is possible to easily confirm relationships between the interfaces of the device connection unit205and the devices DV.

Next, a hardware configuration of the server apparatus30will be described with reference toFIG.5.FIG.5is a diagram illustrating an example of the hardware configuration of the server apparatus30.

As illustrated inFIG.5, the server apparatus30includes a CPU301, a ROM302, and a RAM303.

The CPU301is an example of a processor and controls operations of the server apparatus30. The ROM302stores various programs. The RAM303is a workspace for loading the programs and various data. The CPU301, the ROM302, and the RAM303are connected via a bus or the like to constitute a control unit300. The control unit300executes various processes by the CPU301operating in accordance with a control program3051stored in the ROM302or a storage unit305and loaded into the RAM303.

The CPU301is connected to a communication unit304and the storage unit305via a bus or the like. The communication unit304is a communication interface connectable to the network N. The communication unit304communicates with an external device such as the mobile terminal10, the device broker20, or the clerk terminal40via the network N.

The storage unit305is a storage device such as an HDD, an SSD, or a flash memory, and maintains a stored content even when power is turned off. The storage unit305stores, for example, the control program3051, a commodity master3052, a device broker management table3053, a shopping information management table3054, and an association management table3055.

The control program3051is for controlling the operations of the server apparatus30. The control unit300(more specifically CPU301) executes the control program3051to realize various functions.

The commodity master3052is a master file that stores commodity information related to commodities sold in the store. Specifically, the commodity master3052stores and manages a commodity name, a price, and the like in association with identification information for identifying each commodity.

FIG.6is a diagram illustrating an example of a data configuration of the commodity master3052. As illustrated inFIG.6, the commodity master3052stores commodity information about a commodity corresponding to a commodity code in association with the commodity code. Here, the commodity code is an example of the identification information for identifying the commodity. The commodity code can be, for example, a JAN code. The commodity information includes, for example, the commodity name, the type, and the price of the commodity.

The data configuration of the commodity master3052is not limited toFIG.6. For example, the commodity master3052may include and store image data representing an appearance or a feature of the commodity in the commodity information.

Returning toFIG.5, the device broker management table3053is a data table for managing the state of the device broker20. Specifically, the device broker management table3053stores the device state information of each device DV connected to a device broker20, in association with identification information for identifying the device broker20. In general, there may be more than one device broker20, and thus more than one device broker ID may be listed in the device broker management table3053.

FIG.7is a diagram illustrating an example of a data configuration of the device broker management table3053. As illustrated inFIG.7, the device broker management table3053stores the device state information of the device(s) DV connected to the device broker20in association with a device broker ID for the particular device broker20. Here, the device broker ID is an example of the identification information capable of identifying the device broker20. For example, the device broker ID can be an IP address, a host name, or a unique identifier.

The device state information includes, for example, the device ID and the present state values as the device state information in a manner similar to that described forFIG.4.

The data configuration of the device broker management table3053is not limited toFIG.7. For example, the device broker management table3053may additionally store available settlement methods at the device broker20as determined by a support information providing unit33on the basis of the device state information.

Returning toFIG.5, the shopping information management table3054is a data table for tracking commodities registered with the mobile terminal10. Specifically, the shopping information management table3054stores shopping information indicating the details of the registered commodities that have been registered in the particular mobile terminal10associated with the identification information for identifying the mobile terminal10.

FIG.8is a diagram illustrating an example of a data configuration of the shopping information management table3054. As illustrated inFIG.8, the shopping information management table3054stores the shopping information in association with a mobile terminal ID. Here, the mobile terminal ID is an example of the identification information for identifying a particular mobile terminal10. For example, the mobile terminal ID can be an IP address, a host name, and/or a unique identifier.

The shopping information includes, for example, the commodity code and the quantity of each of the registered commodities. The data configuration of the shopping information management table3054is not limited toFIG.8. For example, the shopping information management table3054may store additional commodity information corresponding to the commodity in association with the commodity code.

Returning toFIG.5, the association management table3055is a data table for tracking the presently set association between a mobile terminal10and a device broker20. Specifically, the association management table3055stores the identification information of a mobile terminal10in association with the identification information of a device broker20.

FIG.9is a diagram illustrating an example of a data configuration of the association management table3055. As illustrated inFIG.9, the association management table3055stores the mobile terminal ID of a mobile terminal10and the device broker ID of a device broker20in association with each other. That is, when a particular device broker20has been assigned to, designated by, or otherwise set to be associated with a particular mobile terminal10, the corresponding mobile terminal ID and device broker ID are stored together in the association management table3055. The server apparatus30of the present embodiment controls the relaying of information between a mobile terminal10and a device broker20by reference to the associated IDs in the association management table3055.

The data configuration of the association management table3055is not limited toFIG.9. For example, the association management table3055may also store a date and time indicating when the association relation was set.

Next, functional aspects of the mobile terminal10, the device broker20, and the server apparatus30will be described with reference toFIG.10. Here,FIG.10is a diagram illustrating an example of the functional configurations of the mobile terminal10, the device broker20, and the server apparatus30.

As illustrated inFIG.10, the mobile terminal10provides a registration unit11, an association information output unit12, and an association support unit13as functional units. A part or all of the functional units of the mobile terminal10may have a software configuration implemented by cooperation between a processor (for example, the CPU101) of the mobile terminal10and the control program1051stored in a memory (for example, the storage unit105). In addition, a part or all of the functional units of the mobile terminal10may have a hardware configuration implemented by a dedicated circuit or the like mounted on the mobile terminal10.

The device broker20provides a device control unit21, a device management unit22, an association information reception unit23, an association unit24, and an accounting unit25as functional units. A part or all of the functional units of the device broker20may have a software configuration implemented by cooperation between a processor (for example, the CPU201) of the device broker20and the control program2061stored in a memory (for example, the storage unit206). In addition, a part or all of the functional units of the device broker20may have a hardware configuration implemented by a dedicated circuit or the like mounted on the device broker20.

The server apparatus30provides a device broker management unit31, a shopping information management unit32, a support information providing unit33, and an association control unit34as functional units. A part or all of the functional units of the server apparatus30may have a software configuration implemented by cooperation between a processor (for example, the CPU301) of the server apparatus30and the control program3051stored in a memory (for example, the storage unit305). In addition, a part or all of the functional units of the server apparatus30may have a hardware configuration implemented by a dedicated circuit or the like mounted on the server apparatus30.

First, functions related to state management of the devices DV connected to each of the device brokers20will be described.

The device control unit21of the device broker20controls an operation of a device DV connected to the device broker20. Specifically, the device control unit21controls the operation of a device DV for a mobile terminal10in cooperation with a device driver and the like introduced in advance.

The device management unit22of the device broker20monitors the state of the device DV connected to the device broker20and stores the state in the device management table2062. Specifically, the device management unit22confirms the state for each connected device DV and stores the confirmed device state information in association with the corresponding device ID in the device management table2062.

In addition, the device management unit22transmits the device state information stored in the device management table2062to the server apparatus30. Specifically, the device management unit22transmits the device state information to the server apparatus30together with the device broker ID of the device broker20.

The device management unit22may transmit device state information indicating a reason why a device DV is in an unusable state. The timing at which the device management unit22confirms the device state and the timing at which the device management unit22transmits the device state information to the server apparatus30are not particularly limited, but it is preferable to periodically perform checks and updates so the device state information will reflect real-time performance. In addition, the device control unit21may be configured to include a function of the device management unit22.

The device broker management unit31of the server apparatus30is an example of a collection unit. The device broker management unit31collects the device state information transmitted from the device broker(s)20and stores the device state information in the device broker management table3053. Specifically, when receiving the device state information from each of several device brokers20, the device broker management unit31stores the device state information in association with the relevant device broker IDs in the device broker management table3053. More specifically, the device broker management unit31updates the device state information stored in association with the device broker ID on the basis of the received device state information.

By the cooperation between the device broker20and the server apparatus30, a latest state of the devices DV connected to each of the device brokers20is recorded in the device broker management table3053.

The registration unit11of the mobile terminal10executes the registration of the commodity being purchased by the customer. Specifically, the registration unit11reads a commodity code attached to the commodity being purchased by the customer from an image of the commodity captured by the imaging unit108, in response to an operation of the customer. More specifically, the registration unit11detects the code symbol in the captured image and decodes the detected code symbol to acquire a commodity code encoded in the code symbol.

The registration unit11identifies a commodity corresponding to the acquired commodity code by reference to the commodity master3052of the server apparatus30. The registration unit11causes the display unit106to display commodity information of the identified commodity to notify the operator of the registered commodity.

Then, the registration unit11transmits shopping information related to accounting of the identified commodity to the server apparatus30together with the mobile terminal ID of the mobile terminal10to register the shopping information in the shopping information management table3054. Here, the shopping information includes, for example, information indicating details of the commodity to be purchased such as the commodity code and the quantity of the commodity being purchased. The quantity value may be separately input via the operation unit107, or may be the accumulated number of the same commodity code input to the mobile terminal10.

The shopping information management unit32of the server apparatus30stores the shopping information transmitted from the mobile terminal10in the shopping information management table3054. Specifically, when receiving a combination of the mobile terminal ID and the shopping information from the mobile terminal10, the shopping information management unit32stores the combination in an associated manner in the shopping information management table3054.

By the cooperation between the mobile terminal10and the server apparatus30, the shopping information of the commodity read by the mobile terminal10is registered in the shopping information management table3054of the server apparatus30.

The association information output unit12of the mobile terminal10outputs association information related to an association with a device broker20. The association information also includes the identification information of the mobile terminal10. Specifically, when receiving an operation for instructing an end of the registration of the commodity, that is, an operation for starting the accounting (transaction settlement process), the association information output unit12causes the display unit106to display the association information including the mobile terminal ID of the mobile terminal10. Here, the association information is output as a code symbol CS such as a two-dimensional code.

The association information reception unit23receives the association information via a device DV connected to the device broker20. Specifically, the association information reception unit23receives the association information from the code reading device DVa.

The association unit24notifies the server apparatus30of the association information received by the association information reception unit23. Specifically, the association unit24transmits the device broker ID of the device broker20to the server apparatus30together with the association information to instruct an association to be registered between the device broker20and the mobile terminal10identified in the association information. Accordingly, the server apparatus30begins relaying of information, data, commands, or the like between the associated device broker20and the mobile terminal10under control of the association control unit34.

The association control unit34of the server apparatus30is an example of a relaying unit. The association control unit34controls the association between the mobile terminal10and the device broker20. When receiving a combination of the device broker ID and the association information from the device broker20, the association control unit34registers the combination in the association management table3055. Specifically, the association control unit34registers the received device broker ID and the mobile terminal ID included in the association information in the association management table3055.

In addition, the association control unit34relays information, data, commands, or the like between the mobile terminal10and the device broker20on the basis of information registered in the association management table3055.

With the configuration described above, association information provided by the mobile terminal10is read by the code reading device DVa of a particular device broker20. Therefore, by the cooperation between the device broker20and the server apparatus30, the mobile terminal10and the device broker20become associated with each other, and communication between the two devices can be relayed by the server apparatus30rather than conducted directly. Accordingly, in the checkout system1, information related to the accounting and the like of the commodities registered in the mobile terminal10can be input and output using a device DV of the device broker20.

The association support unit13of the mobile terminal10supports operations and processes related to the association with the device broker20. For example, the association support unit13requests the server apparatus30provide information related to the device brokers20(also referred to as sending an association support request) in response to a user operation of starting the accounting or the like. In addition, the association support unit13acquires information (“association support information”) indicating the state of the device brokers20from the server apparatus30in response to the association support request. Then, the association support unit13causes the display unit106to display a screen (“an association support screen”) based on the acquired association support information).

The support information providing unit33provides the association support information to the mobile terminal10in response to the association support request from the mobile terminal10. Specifically, the support information providing unit33generates the association support information on the basis of the device broker management table3053and the association management table3055. Then, the support information providing unit33transmits the generated association support information to the requesting mobile terminal10.

As an example, the support information providing unit33determines whether each of the device brokers20is presently in use, in an idle state, in an unusable state, or the like on the basis of the information registered in the device broker management table3053and the association management table3055. Then, the support information providing unit33generates the association support information including an indication as to whether a device broker20can be used.

Specifically, the support information providing unit33determines whether a device broker20can be used on the basis of the state of each device DV registered in the device broker management table3053. For example, when an abnormality occurs in the code reading device DVa used for inputting the association information, the support information providing unit33determines that the corresponding device broker20is in the unusable state. In addition, the support information providing unit33determines that the device brokers20registered in the association management table3055are presently in use and that the device brokers20not registered in the association management table3055are in the idle state. However, when a particular device broker20is determined to be in both the unusable state and the idle state (or in use), the unusable state is prioritized.

As another example, the support information providing unit33may also determines which settlement methods are available at a device broker20on the basis of the states of each device DV registered in the device broker management table3053in association with the device broker20. Then, the support information providing unit33generates the association support information including an indication of available settlement methods for each device broker20or the like.

Specifically, the support information providing unit33determines the usable settlement methods on the basis of the states of the devices DV connected to the device broker20that must be used in the specific payment methods. For example, when the cash recycler DVe is in the usable state, the support information providing unit33determines that cash settlement is possible. When the code reading device DVa is in the usable state, the support information providing unit33determines that electronic settlement using a two-dimensional code (hereinafter, also referred to as code settlement) is possible. When the wireless tag reading device DVb is in the usable state, the support information providing unit33determines that electronic settlement using a wireless tag (hereinafter, also referred to as RFID settlement) is possible. When the card settlement device DVd is in the usable state, the support information providing unit33determines that settlement using a credit card (hereinafter, also referred to as credit settlement) is possible.

The association support unit13may also cause the display unit106to display, for example, an association support screen as illustrated inFIG.11on the basis of the support information provided from the server apparatus30. Here,FIG.11is a diagram illustrating one example of the association support screen.

As illustrated inFIG.11, support information SI provided from the server apparatus30is displayed on an association support screen GA. Here, the support information SI includes states of four device brokers20whose device broker IDs are #001 to #004. Specifically, as the states of the device brokers20,FIG.11illustrates that the device brokers20#001, #002, and #004 are in the idle state and the device broker20#003 is in use. In addition, as the settlement methods that can be used in the device brokers20,FIG.11illustrates that the device brokers20#001 and #002 support cash settlement, credit settlement, RFID settlement, and code settlement. In addition,FIG.11illustrates that the device broker20#003 supports cash settlement, credit settlement, and code settlement, but the device broker20#004 supports just credit settlement and code settlement.

The operator of the mobile terminal10can easily grasp which device broker20can be used for a preferred settlement method and is also presently in the idle state by viewing the support information SI. Accordingly, the checkout system1can support the operator of the mobile terminal10to select a particular device broker20as an association target.

In addition, the association support screen GA ofFIG.11displays the code symbol CS which is the association information generated by the association information output unit12, and also a message Ma for prompting the operator to scan or otherwise input the code symbol CS at a device broker20.

Accordingly, the operator of the mobile terminal10can easily grasp that the code symbol CS is to be scanned at the device broker20selected on the basis of the support information SI. Therefore, convenience for the operator of the mobile terminal10can be improved in the checkout system1.

The association support screen GA is not limited to the example ofFIG.11. For example, inFIG.11, the code symbol CS and the massage Ma are displayed on the association support screen GA, but the code symbol CS and the massage Ma may also be displayed on another screen. In addition, the association information output unit12may include functions of the association support unit13.

The present embodiment is an example in which the device broker20executes the accounting process.

The accounting unit25of the device broker20executes the accounting for the commodities registered in an associated mobile terminal10. Specifically, the accounting unit25acquires, from the server apparatus30, shopping information in association with the identification information included in the association information received by the association information reception unit23. More specifically, the accounting unit25transmits an acquisition request of the shopping information, which specifies the mobile terminal ID included in the association information, to the server apparatus30.

When receiving the acquisition request of the shopping information from the device broker20, the shopping information management unit32of the server apparatus30provides the shopping information specified by the acquisition request to the device broker20. Specifically, the shopping information management unit32extracts the shopping information corresponding to the specified mobile terminal ID from the shopping information management table3054. Then, the shopping information management unit32transmits the extracted shopping information to the device broker20as the request source.

After acquiring the shopping information from the server apparatus30, the accounting unit25of the device broker20calculates a total amount due for the registered commodities on the basis of the commodity codes and quantities of each commodity included in the shopping information. Specifically, the accounting unit25identifies the commodity information by commodity code by referencing the commodity master3052of the server apparatus30. Next, the accounting unit25multiplies the price included in the identified commodity information by the quantity, and adds up the amounts due for each commodity to calculate the total amount due for the registered commodities. Upon receiving a payment via a device DV connected to the device broker20, the accounting unit25executes the accounting for settling the total amount according to the received payment amount.

In addition, when the accounting is completed, the accounting unit25causes the printer DVc connected to the device broker20to issue a receipt on which information indicating the registered commodities and the content of the settlement are printed. When the accounting is completed, the accounting unit25notifies the server apparatus30of the completion of the accounting. Specifically, the accounting unit25transmits the completion notification of the accounting, which specifies the association information or the mobile terminal ID included in the association information, to the server apparatus30.

Upon receiving the completion notification of the accounting from the device broker20, the shopping information management unit32of the server apparatus30excludes (e.g., deletes, removes, or invalidates) the shopping information for which the accounting has just been completed from the shopping information management table3054. Specifically, the shopping information management unit32excludes an entry of the shopping information (for example, the mobile terminal ID and the shopping information) associated with the association information (or the identification information) specified by the completion notification from the shopping information management table3054. Here, in this example, “exclude” means deleting from the shopping information management table3054, moving to another table, or attaching a flag or the like to distinguish from an unaccounted entry.

After receiving the completion notification of the accounting from the device broker20, the association control unit34of the server apparatus30cancels the association of the device broker20and the mobile terminal10. Specifically, when receiving the completion notification of the accounting from the device broker20, the association control unit34deletes an entry related to the device broker ID of the device broker20from the association management table3055.

Accordingly, the operator of the mobile terminal10can pay for the registered commodities using the devices DV connected to a device broker20. Therefore, in the checkout system1, the commodities registered with the mobile terminal10can be paid for using a device DV without establishing direct communication between the mobile terminal10and the device broker20, and thus the convenience for the operator of the mobile terminal10can be improved.

The accounting unit25may provide information or a screen indicating a process state of the accounting to the mobile terminal10via the server apparatus30. In this case, the association support unit13of the mobile terminal10causes the display unit106of the mobile terminal10to display the information or a screen indicating the process state of the accounting as provided from the server apparatus30. In addition, for example, the accounting unit25may provide the mobile terminal10with a screen for announcing a settlement method supported by the device broker20or a selection screen for selecting a desired settlement method to be used, on the basis of the state of each device DV stored in the device management table2062.

Accordingly, the operator of the mobile terminal10can easily grasp the process state of the accounting by viewing the display unit106of the mobile terminal10. Therefore, the checkout system1can improve the convenience for the operator of the mobile terminal10related to the accounting.

The device control unit21of the device broker20may control switching of an operation mode of a device DV connected to the device broker20in accordance with a state of the association with the mobile terminal10. For example, when not associated with a mobile terminal10, the device control unit21may cause the devices DV other than the code reading device DVa to shift to an idle state such as a power saving mode. In addition, when the association with the mobile terminal10is started by the association unit24, the device control unit21causes the devices DV in the standby state to shift to a normal state (also referred to as an active state), and brings all the devices DV into a usable state. When the accounting unit25provides the selection screen of the settlement method to the mobile terminal10, the device control unit21may cause a device DV related to the selected payment method to shift to the active state.

Accordingly, when the device broker20is not in association with the mobile terminal10, a power consumption of the device DV connected to the device broker20can be reduced, and thus power saving can be achieved.

Next, an operation example of the checkout system1described above will be described.

First, the device state management executed by the device broker20and the server apparatus30will be described with reference toFIG.12.FIG.12is a flowchart illustrating an example of the device state management executed by the device broker20and the server apparatus30.

First, the device management unit22of the device broker20acquires the state of each device DV connected to the device broker20(Act11). The device management unit22updates the device state information of the device management table2062on the basis of the acquired state of the device DV (Act12). Next, the device management unit22transmits the updated device state information to the server apparatus30(Act13).

The device broker management unit31of the server apparatus30waits (Act21; No) until the device state information is received from the device broker20. Upon receiving the device state information (Act21; Yes), the device broker management unit31stores the received device state information in the device broker management table3053in association with the device broker ID of the device broker20to update the device state information (Act22).

The processes in Acts11to13are executed by each of the device brokers20, whereby the state of each device DV connected to each of the device brokers20is registered in the device broker management table3053of the server apparatus30.

Next, the commodity registration executed by the mobile terminal10and the server apparatus30will be described with reference toFIG.13.FIG.13is a flowchart illustrating an example of the commodity registration executed by the mobile terminal10and the server apparatus30.

First, in the mobile terminal10, when the registration of the commodity is started by the operation of the operator, the registration unit11determines whether the commodity code is read from the image captured by the imaging unit108(Act31). When the commodity code cannot be read (Act31; No), the process proceeds to Act34.

In Act31, when the commodity code is read (Act11; Yes), the registration unit11identifies the commodity corresponding to the commodity code by reference to the commodity master3052of the server apparatus30(Act32). Next, the registration unit11transmits the shopping information for the identified commodity to the server apparatus30together with the mobile terminal ID of the mobile terminal10(Act33), and the process proceeds to Act34.

The shopping information management unit32of the server apparatus30determines whether the shopping information has been received from the mobile terminal10(Act41). Here, when the shopping information management unit32does not receive the shopping information (Act41; No), the process proceeds to Act43.

When the shopping information has been received from the mobile terminal10(Act41; Yes), the shopping information management unit32registers the received mobile terminal ID and shopping information in the shopping information management table3054in association with each other (Act42), and the process proceeds to Act43.

In the mobile terminal10, after Act33, the registration unit11determines whether the start of the accounting has been instructed via the operation unit107(Act34). Here, if the start of the accounting is not yet instructed (Act34; No), the process returns to Act31. If the start of the accounting has been instructed (Act34; Yes), the association support unit13transmits the association support request to the server apparatus30(Act35).

The support information providing unit33of the server apparatus30determines whether the association support request has been received from the mobile terminal10(Act43). Here, if the association support request is not yet received (Act43; No), the process returns to Act41. If the association support request has been received from the mobile terminal10(Act43; Yes), the support information providing unit33generates the association support information (Act44) and transmits the generated association support information to the requesting mobile terminal10(Act45).

Upon receiving the association support information from the server apparatus30as a response to the association support request (Act36), the association support unit13of the mobile terminal10causes the display unit106to display the association support screen GA on the basis of the association support information (Act37).

Next, the association information output unit12of the mobile terminal10generates the association information including the mobile terminal ID of the mobile terminal10and causes the display unit106to display the association information (Act38).

The processes at Acts31to38are executed by the mobile terminal10, so that the association information for associating with the device broker20is displayed on the display unit106. The operator of the mobile terminal10moves to a desired device broker20(e.g., selected on the basis of the association support screen GA) and causes a code reading device DVa to read the association information, thereby starting the association between the mobile terminal10and the device broker20.

In some examples, the mobile terminal10may display the association information immediately after receiving the instruction to start the accounting in Act34by skipping Acts35to37. In this case, the association support request may be transmitted in response to a predetermined operation via the operation unit107other than the accounting instruction. In addition, the mobile terminal10might not transmit an association support request or display an association support screen.

Next, the association executed by the device broker20and the server apparatus30will be described with reference toFIG.14.FIG.14is a flowchart illustrating an example of the association executed by the device broker20and the server apparatus30.

First, the association information reception unit23of the device broker20waits (Act51; No) until the association information is input via the code reading device DVa. When the association information is input (Act51; Yes), the association information reception unit23transmits the association information to the server apparatus30together with the device broker ID of the device broker20(Act52).

The association control unit34of the server apparatus30waits (Act61; No) until the association information is transmitted from the device broker20. When the association information is received (Act61; Yes), the association control unit34registers the mobile terminal ID included in the received device association information in the association management table3055in association with the device broker ID of the device broker20as the transmission source (Act62). Next, the association control unit34starts the relaying between the mobile terminal10and the device broker20which are now registered in the association management table3055(Act63).

Through the association described above, information can be exchanged between the mobile terminal10and the device broker20via the server apparatus30. Accordingly, in the checkout system1, information with respect to the mobile terminal10, for example, information related to the accounting of the commodity can be input and output using the devices DV connected to the device broker20.

Next, the associated accounting executed by the mobile terminal10, the device broker20, and the server apparatus30will be described with reference toFIG.15.FIG.15is a flowchart illustrating an example of the associated accounting executed by the mobile terminal10, the device broker20, and the server apparatus30. The present process includes a process executed by the mobile terminal10and the device broker20that are in the association relation after the association illustrated inFIG.14.

First, the accounting unit25of the device broker20acquires the shopping information related to the mobile terminal10of the association target (Act71). Specifically, the accounting unit25transmits, to the server apparatus30, an acquisition request for the shopping information in which the mobile terminal ID of the mobile terminal10of the association target is specified, thereby acquiring the corresponding shopping information from the server apparatus30.

Next, the accounting unit25transmits, to the server apparatus30, a selection screen on which a desired settlement method can be selected from settlement methods supported by the device broker20on the basis of the state of each device DV stored in the device management table2062(Act72). The selection screen transmitted from the accounting unit25is relayed to the associated mobile terminal10by the association control unit34of the server apparatus30(Act81). Then, when receiving the selection screen via the server apparatus30, the association support unit13of the mobile terminal10causes the display unit106to display the selection screen (Act91).

When receiving the selection of the settlement method via the selection screen (Act92), the association support unit13of the mobile terminal10transmits instruction information for instructing the received settlement method to the server apparatus30(Act93). The instruction information transmitted from the mobile terminal10is relayed to the associated device broker20by the association control unit34of the server apparatus30(Act82).

When receiving the instruction information for instructing the settlement method via the server apparatus30, the device control unit21of the device broker20causes the device(s) DV related to the instructed settlement method to shift to the active state (Act73). Next, the accounting unit25of the device broker20acquires payment information indicating the payment amount via a device DV activated at Act73(Act74), and executes the accounting (Act75).

Next, when the accounting is completed, the accounting unit25of the device broker20outputs the receipt from the printer DVc (Act76). In addition, the accounting unit25transmits the completion notification of the accounting to the server apparatus30(Act77).

The completion notification of the accounting transmitted from the accounting unit25is relayed to the associated mobile terminal10by the association control unit34of the server apparatus30(Act83). Then, when receiving the completion notification of the accounting via the server apparatus30, the association support unit13of the mobile terminal10causes the display unit106to display an accounting completion screen indicating that the accounting is completed (Act94).

The shopping information management unit32of the server apparatus30excludes an entry of the corresponding shopping information from the shopping information management table3054in response to the completion notification of the accounting (Act84). The association control unit34of the server apparatus30cancels an association setting related to the notifying device broker20in response to the completion notification of the accounting (Act85) and ends the relaying between the mobile terminal10and the device broker20(Act86).

When the accounting is completed, the device control unit21of the device broker20causes the device DV activated in Act73to shift to the idle state (Act78), and ends the process.

Through the associated accounting described above, the operator of the mobile terminal10can pay for the registered commodities using a device DV of an associated device broker20. Accordingly, in the checkout system1, the commodities registered in the mobile terminal10can be paid for using various devices DV without establishing any direct communication between the mobile terminal10and the device broker20, and thus the convenience for the operator of the mobile terminal10can be improved.

As described above, in the checkout system1of the present embodiment, the association information displayed on the display unit106of the mobile terminal10is taken in by the code reading device DVa connected to the device broker20, so that information can be subsequently exchanged between the mobile terminal10and the device broker20via relay through the server apparatus30. Accordingly, in the checkout system1, the commodities can be paid for using a device DV without directly connecting the mobile terminal10to a device DV, and thus the devices DV can be more easily used.

In addition, the checkout system1of the present embodiment provides the mobile terminal10with the association support information for supporting the association with the device broker20at a timing when the commodity registration in the registered10is completed. Accordingly, in the checkout system1, the operator of the mobile terminal10can provide information to be referred to when selecting the device broker20, and thus convenience related to the selection of the device broker20can be improved.

The above-described embodiment can be modified in various aspects. Furthermore, the various modifications described below may be implemented individually or in combination with one another as appropriate.

In the embodiment described above, the mobile terminal ID of the mobile terminal10is used as the identification information for identifying the mobile terminal10, but is not limited thereto. For example, identification information such as an ID or a name of the operator who operates the mobile terminal10may be used as the identification information for identifying the mobile terminal10.

In addition, identification information for identifying a transaction related to the purchase of the commodities registered in the mobile terminal10may be used as the identification information for identifying the mobile terminal10. Here, a “transaction” refers to a period from the start to the end of the registration of the commodity for the same customer. For example, when a unique transaction ID is issued every time the operation of starting the registration of the commodities is performed in the mobile terminal10, each of the mobile terminals10can be uniquely identified using transactions ID.

The identification information of the operator or the transaction may be used instead of the mobile terminal ID of the mobile terminal10, and may be used together with the mobile terminal ID. Accordingly, similar to the embodiment described above, the association with the device broker20can be set on the basis of the identification information of the operator or the transaction, and the shopping information can be acquired, and thus effects similar to those of the embodiment described above can be achieved.

In the embodiment described above, the shopping information of the commodities registered in the mobile terminal10is stored by the server apparatus30, but is not limited thereto, and may also or instead be stored by the mobile terminal10. In this case, the registration unit11of the mobile terminal10registers the commodity by storing the shopping information of the commodity read by the imaging unit108in the RAM103or the storage unit105.

The accounting unit25of the device broker20may thus acquire the shopping information from an associated mobile terminal10via the server apparatus30. Then, when receiving the completion notification of the accounting from the device broker20, via the server apparatus30, the registration unit11of the mobile terminal10deletes (or otherwise excludes) the shopping information registered in the RAM103or the storage unit105.

When the configuration according to the present modification is employed, the checkout system1can also receive payments for the registered commodity by using a device DV without directly connecting the mobile terminal10and the device DV, and thus effects similar to those of described above can be achieved.

In an embodiment described above, each device broker20is connected to devices DV of types and numbers corresponding to the configuration of an accounting machine (e.g., a self-service point-of-sale terminal, a semi-self-service checkout machine, a checkout kiosk, or the like), but is not limited to this form. In other examples, one device broker20may be connected to devices DV of types and numbers corresponding to a plurality of accounting machines. In this case, each device broker20can be used by a plurality of operators in parallel, but it is still typically preferable to divide the devices DV into groups (sets) corresponding to the configuration of a single accounting machine so that the devices DV do not conflict with each other in use.

In such a case, the device management unit22of the device broker20may track the state of each device DV using the device management table2062illustrated inFIG.16. Here,FIG.16is a diagram illustrating an example of the data configuration of the device management table2062according to a third modification.

As illustrated inFIG.16, in the device management table2062, the device state information of each device DV is managed as groups (sets) of devices DV with each group (set) corresponding to the configuration of a one accounting machine. Here, a set ID is used as identification information of a virtual accounting machine or the like corresponding to a particular group (set) of devices DV. That is, devices DV with the same set ID are managed by device ID as components of a virtual accounting machine corresponding to the set ID. When transmitting the device state information to the server apparatus30, the device management unit22also transmits the corresponding set ID to the server apparatus30in association with the device state information.

In addition, in this case, the device broker management unit31of the server apparatus30manages the state of each device DV connected to each device broker20using, for example, the device broker management table3053illustrated inFIG.17. Here,FIG.17is a diagram illustrating an example of the data configuration of the device broker management table3053according to the third modification.

As illustrated inFIG.17, the device broker management table3053stores the set ID and the device state information in association with the device broker ID of the device broker20. That is, the device broker management table3053tracks the state of the devices DV in each device broker20by set ID.

In this case, the association unit24of the device broker20transmits a set ID to which the code reading device DVa input with the association information belongs to the server apparatus30together with the association information. Then, the association control unit34of the server apparatus30associates the identification information of the mobile terminal10and the device broker20and registers the identification information in the association management table3055and also registers the set ID transmitted together with the association information in the association management table3055.

Accordingly, in the present modification, among the devices DV connected to the device broker20, a device DV of the set ID registered in the association management table3055can be used for the accounting and the like. That is, in the present modification, when a plurality of sets (virtual accounting machines) formed of the devices DV connected to a single device broker20, each set can be separately associated with a mobile terminal10.

The sets of the devices DV connected to the device broker20are preferably grouped separately from one another or otherwise provided with an identifying label or the like displaying the respective set ID to which the device DV belongs so as prevent confusion between the sets.

An embodiment described above described an example in which the state of the device DV connected to the device broker20is detected as the unusable state due to a failure or the like. In this case, the server apparatus30may notify the clerk terminal40of the presence of a device DV in the unusable state.

For example, the device broker management unit31of the server apparatus30monitors the device state information transmitted from the device brokers20and determines whether any device DV in the unusable state is included therein. When detecting a device DV in the unusable state in the device state information, the device broker management unit31transmits the device broker ID of the relevant device broker20and the device ID of the device DV in the unusable state to the clerk terminal40as error information.

Upon receiving the error information from the server apparatus30, the clerk terminal40notifies the clerk of the presence of the device DV in the unusable state by, for example, displaying or otherwise notifying that error information has been received. Accordingly, the clerk operating the clerk terminal40can easily identify the device DV in the unusable state by confirming the error information transmitted from the server apparatus30.

In the case of a configuration in which the unusable state is recorded along with the cause thereof, the device broker management unit31preferably transmits the error information to the clerk terminal40including the cause. Accordingly, the clerk operating the clerk terminal40can identify the cause of the unusable state, and thus the convenience can be improved.

When the clerk responds by, for example, replacing or repairing the device DV previously in the unusable state, the device management unit22of the device broker20updates the device state information of the corresponding device DV. Accordingly, a state of the device DV after the response can be promptly reflected in the device management table2062and the device broker management table3053.

When the device ID is changed due to the replacement or the like of the device DV, the device management unit22of the device broker20updates the device state information using the changed device ID.

As described above, by employing the present modification, even when the device DV is in the unusable state, the device DV can be rapidly handled, and thus an efficiency of the entire checkout system1can be improved.

Programs executed in each apparatus of an embodiment can be provided by being incorporated in a ROM, a storage device, or the like in advance. The programs executed by each apparatus of an embodiment may be provided by being recorded in a non-transitory, computer-readable recording medium such as a CD-ROM, a flexible disk (FD), a CD-R, or a digital versatile disk (DVD) in an installable or executable form of a file.

Further, the programs executed by each apparatus described above may be stored on a computer connected to a network, such as the Internet, and downloaded via the network. In addition, the programs executed by each apparatus of the embodiment described above may be accessed or distributed across a network, such as the Internet.

The embodiments of the disclosure have been described, but these embodiments are merely presented as examples, and are not intended to limit the scope of the disclosure. Such new exemplary embodiments and modifications thereof can be implemented in other various forms, and various omissions, replacements, and changes can be made without departing from the spirit of the exemplary embodiments described herein. The embodiments and modifications thereof are included in the scope and gist of the exemplary embodiments described herein, and are also included in the exemplary embodiments described in the claims and equivalents thereof.