METHOD AND DEVICE FOR CONTROLLING A CASH REGISTER SYSTEM

Abstract

The invention relates to a cash register system (1), comprising a stationary unit (3), which is connected to at least one cash register peripheral unit (5.1, 5.2, 5.3) by means of at least one connection (4.1, 4.2, 4.3); a mobile unit (2), comprising a display device, and an input device, wherein the mobile unit is designed to execute cash register software, in the process of which the cash register peripheral unit (5.1, 5.2, 5.3) is accessed; a management unit (6), wherein the mobile unit (2) can be connected to the stationary unit (3) by means of a first connection (10), the mobile unit (2) can be connected to the management unit (6) by means of a second connection (11), the stationary unit (3) can be connected to the management unit (6) by means of a third connection (12), and the management unit (6) is designed to check, on the basis of a set of rules, whether a first logical connection (X) of the mobile unit (2) to the stationary unit (3) and/or a second logical connection (Y) of the mobile unit (2) to the at least one cash register peripheral unit must be established, and if the check is successful, access to the stationary unit (3) via the logical connection (X) of the mobile unit (2) and/or access to the cash register peripheral unit (5.1, 5.2, 5.3) via the logical connection (Y) of the mobile unit is permitted and the management unit (6) detects a corresponding logical connection (X) (Y) of the apparatuses.

Claims

1. A POS system (1) comprising: a stationary unit (3) which is connected by at least one connection (4.1, 4.2, 4.3) to at least one POS peripheral unit (5.1, 5.2, 5.3), a mobile unit (2) comprising a display device, as well as an input device, wherein the mobile unit being configured to execute a POS software, wherein in said process an access to the POS peripheral unit (5.1, 5.2, 5.3) takes place, a management unit (6), wherein the mobile unit (2) is connectable to the stationary unit (3) via a first connection (10), the mobile unit is connectable to the management unit (6) via a second connection (11), the stationary unit (3) is connectable to the management unit (6) via a third connection (12), and the management unit (6) is configured to check, based on a rules set, if a first logical connection (X) of the mobile unit (2) to the stationary unit (3) and/or a second logical connection (Y) of the mobile unit (2) to the at least one POS peripheral unit is to be set up, and if the check is successful, access is granted from the mobile unit (2) to the stationary unit (3) via the first logical connection (X) and/or access is granted form the mobile unit (2) to the POS peripheral unit (5.1, 5.2, 5.3) via the second logical connection (Y), and the management unit (6) registers the corresponding logical connections (X) (Y) of the units.

2. The POS system as claimed in claim 1, wherein the mobile unit (2) is connectable to the stationary unit (3) via the first connection (10), wherein the units are configured to send a request to the management unit (6) when establishing the connection for determining whether a connection (X) (Y) of the mobile unit (2) to the stationary unit (3) and/or to its POS peripheral unit (5.1, 5.2, 5.3) is grantable based on the rules set, and when it is grantable, the management unit (6) is configured to transmit a corresponding message to the mobile unit (2) and/or the stationary unit (3) to grant access via the logical links (X) (Y).

3. A POS system according to the preceding claim, wherein the management unit (6) is configured to receive both a request via the second connection (11) from the mobile unit (2) and in parallel a request via the third link (12) from the stationary unit (3) to allow access via the logical links (X) (Y).

4. The POS system according to one or more of the preceding claims, wherein an ID of the mobile unit (2) and/or an ID of the stationary unit (3) are recordable and transmittable to the management unit (6) for identification, and/or wherein the stationary unit (3) and the mobile unit (2) have to communicate with the management unit (6) within a defined period of time.

5. The POS system according to one or more of the preceding claims, wherein the mobile unit (2) or the stationary unit(3) are configured to transmit an ID via a physical contact connection or wireless local area connection which can be NFC., RFID, Zigbee, Bluetooth and/or Bluetooth low energy, in order to then transmit the ID to the management unit (6) via a network, which can be WLAN, Ethernet or Bluetooth.

6. The POS system according to the previous requirements, wherein the first connection (10) and/or the connection (10.1) is arranged between the mobile units (2), the stationary unit (3), the management unit (6) or the POS peripheral unit (5.1, 5.2, 5.3) as an encrypted connection, and wherein the management unit (6) is preferably configured to transmit keys of an encryption key pair to the mobile unit and/or stationary unit, and can also be configured to generate them.

7. The POS system according to one or more of the preceding claims, wherein a virtual interface, which can be RS232 or USB, of the POS system application is provided on the mobile unit (2) which is configured to establish a logical connection (X) (Y) to the stationary unit (3) and/or POS peripheral unit (5.1, 5.2, 5.3), and the authentication is carried out via the management unit (6).

8. The POS system according to one or more of the preceding claims, wherein by the rule set verifies whether the allocation, the ID, the timing, the spatial distance, the user login and/or the category of the POS peripheral unit are allowable in order to grant a connection.

9. The POS system according to one or more of the preceding claims, wherein the mobile unit (2) is configured to allow an interactive selection of stationary units (3) and/or POS peripheral units (5.1, 5.2, 5.3), and/or wherein a physical interlock is provided to physically to establish a interlock after a physical connection of the stationary unit (3) to the mobile unit (2), wherein the lock being controlled by the management unit (6) according to the rule set.

10. The POS system according to one or more of the preceding claims, wherein the POS peripheral unit (5.1, 5.2, 5.3) is one or more of the following components: an automatic cash safe, a cash drawer, a printer, a keyboard, a scanner, a 3d scanner, a pin pad (over LAN), a card reader, a monitor, a line display, a scale, a NFC reader, a banknote deposit device, a banknote disburse device, a coin deposit device and/or a coin disburse device.

11. A method for controlling a POS system (1), the POS system comprising: a stationary unit (3), which is connected via at least one connection (4.1, 4.2, 4.3) to at least one POS peripheral unit (5.1, 5.2, 5.3), a mobile unit (2), comprising a display device, as well as an input device, wherein the mobile unit is configured to execute a POS software, in the execution of which access to the POS peripheral unit (5.1, 5.2, 5.3) takes place, an administrative unit (6) which manages a rules set; in which the mobile unit is connectable to the stationary unit (3) via a first connection (10), the mobile unit is connectable to the management unit (6) via a second connection (11), the stationary unit (3) is connectable to the management unit (6) via a third connection (12), and comprising the steps of: establishing a connection between the mobile unit (2) and the stationary unit to access the POS peripheral units; requesting from the mobile unit (2) and/or the stationary unit (3) to the management unit (6) if a logical connection (X) (Y) is possible from the mobile unit, checking by the management unit (6) based on the rule set whether a first logical connection (X) (Y) is possible, if a logical connection is possible, notifying to the mobile unit and/or stationary unit that a connection is possible, establishing the logical connection by the mobile unit and/or stationary unit to the POS peripheral units.

12. The Method according to the preceding method claim, wherein the management unit (6) receives both a request via the second connection (11) from the mobile unit (2) and in parallel has to receive a request via the third connection (12) from the stationary unit (3) to allow access via the logical connection (X) (Y), and the inquiries should arrive within a defined time window.

13. The Method according to one or more of the preceding claims, wherein an ID of the mobile unit (2) and/or an ID of the stationary unit (3) are acquired and these are transmitted to the management unit (6) for identification.

14. The Method according to the preceding claim, wherein the connections between the mobile unit (2), the stationary unit (3), the management unit (6) and/or the POS peripheral unit (5.1, 5.2, 5.3) are encrypted.

15. The Method according to one or more of the preceding claims, wherein a virtual interface, which can be RS232, USB on the mobile unit (2) is provided to the POS software, which is provided as logical connection (X) (Y) to the stationary unit (3) and/or to the POS peripheral unit (5.1, 5.2, 5.3).

16. The Method according to one or more of the preceding claims, wherein the rule set is used to check whether the assignment, the ID, the timing, the spatial distance, the user login and/or the category of the POS peripheral unit are allowed.

17. The Method according to one or more of the preceding claims, wherein a physical interlock is present and an interlocking occurs after a physical connection of the stationary unit (3) to the mobile unit (2) is determined, wherein the interlocking is performed by the management unit (6) according to the rules set.

Description

DESCRIPTION OF THE FIGURES

[0037] The figures briefly described below are referred to in the following detailed description of possible embodiments.

[0038] It shows:

[0039] FIG. 1 is a conventional POS system according to the prior art in which the POS system is connected to a series of POS peripheral units and has a fixed monitor;

[0040] FIG. 2 shows the structure according to the present invention wherein a control computer takes the function of a stationary unit and a tablet computer takes over the function of the mobile unit connected by a wireless connection;

[0041] FIG. 3 shows the connection of the mobile unit (Tablet PC) to the stationary unit (POS device HUB), wherein an ID is exchanged during the connection;

[0042] FIG. 4 shows a possible structure of the present invention and the nature of the network interfaces including the management computer;

[0043] FIG. 5 shows the steps of a method in which a mobile unit connects to the stationary unit (POS), wherein the management unit (server) is integrated into the steps, a user intervenes in the steps by means of corresponding user interfaces with dialogs;

[0044] FIG. 6 shows the physical connections and logical connections of the mobile and stationary units of the present invention.

DESCRIPTION OF POSSIBLE EMBODIMENTS

[0045] FIG. 1 shows a conventional POS system, according to the prior art, with a stationary POS system, which is connected by cable connections to different POS peripheral units. This POS system usually has a screen which, in a preferred embodiment, allows a touch input. The stationary POS system, also known as the stationary unit, is connected to a keyboard, scanner, printer, cash drawer, scale, line display or an EFT payment terminal via an RS232, USB or special ports.

[0046] A traditional POS system thus essentially consists of: [0047] the POS system itself, which consists of a PC-like computer with a certain amount of USB, RS232 and special port connections for the peripheral units; [0048] various peripheral units, such as a bond printer, an EFT terminal for payment, a label reader (scanner), a multi-line customer display (line display), an automatic cash safe, printer, keyboard, scanner, 3D scanner, card reader, monitor, scale, NFC reader, banknote deposit device, banknote disburse device, coin deposit device, coin disburse device and/or a cash drawer; [0049] a screen for displaying operator dialogs for the user. Often also with a so-called touch input, so that the user can operate the displayed dialogues with the finger directly; [0050] in addition, also a keyboard for the user e.g. to enter article numbers can be connected.

[0051] With the increased use of mobile devices, the demand for the use of mobile devices at the POS workplace also becomes important. Current procedures usually require changes in two thematic areas, which are complex and cost-intensive: [0052] a new adaptation of the application program in order to access peripheral devices is necessary. [0053] an adaptation of the connection type of peripheral devices, e.g. instead of USB and/or RS232 now an Ethernet connection, is necessary.

[0054] FIG. 2 shows the modified form, in which the POS system consists of two components: a mobile unit which is preferably designed as a tablet and has a touch-sensitive input device. This mobile unit is preferably connected to a control computer via a wireless connection, also referred to as a stationary unit, which is then in turn connected to the POS peripheral units.

[0055] The invention presented here makes it possible to continue using the systems in both thematic areas.

[0056] The tablet can have the same operating system as the PC-like computer used at the POS. Other operating systems such as Linux, Unix, iOS, Blackberry or Android are also possible. The management unit may employ an operating system which corresponds to the operating system of the tablet or use an alternative operating system from the above-mentioned list.

[0057] FIG. 6 shows the POS system 1, which consists of one or more mobile units 2 (moPOS1, moPOS2). Further constituents are one or more stationary units 3 (POS HUB1, POS HUB2), which are respectively connected to POS system peripherals units 5.1, 5.2, 5.3 via connections 4.1, 4.2, 4.3. Furthermore, there is also an administration unit 6 (administration server) which is connected via a connection 11 to the mobile unit 2 and via a connection 12 to the stationary unit 3. Furthermore, there is at least one connection 10 between the mobile unit and the stationary unit. In a preferred embodiment, there is also a connection 10.1, which is to be considered in particular when the devices are physically connected to one another, in particular when the mobile unit is inserted into the stationary unit. Access to the POS peripheral units takes place via the logical connections X or Y, wherein the physical access usually being via the connection 10 and 4.1,4.2,4.3.

[0058] FIG. 3 shows a contact-related authentication. If the tablet PC/mobile unit is plugged into the intelligent docking unit/stationary unit, an ID data exchange between the microcontroller integrated in the tablet PC (via the two contacts (any other number of contacts is also possible) is performed on the tablet and the docking unit (ULPMC) and the microcontroller in the intelligent docking unit. A 64 bit (unique ID) is transmitted as identification/authentication of the tablet. The intelligent docking unit transmits this ID via USB to the POS device HUB/stationary unit.

[0059] Alternatively, contactless authentication is conceivable.

[0060] There are various possibilities for authentication, e.g.: [0061] reading an NFC tag on the docking unit using the NFC reader integrated into the tablet, [0062] reading of an RFID tag attached to the tablet by means of a Mifare reader connected to the POS device HUB/stationary unit, [0063] reading in of a Tablet ID through a contact-connected connection between the tablet and the docking unit.

[0064] The ID or identification of the tablet and the logical ID of the POS device HUB can now be sent via LAN to an administration server administration unit.

[0065] In order to increase security, the tablet ID is exchanged between the tablet (mobile unit) and the administration server on different transmission paths (contact-bound and/or wireless).

[0066] The management unit checks whether this specific tablet/mobile unit is allowed to access the peripherals/POS peripheral units on the POS device HUB. This information is transferred to the POS application running on the tablet PC via a WLAN access point (FIG. 4). Thus, the peripherals are logically connected (docked) to the Tablet PC and the POS application can access the devices.

[0067] For other tablet PCs the access is denied, and this state is indicated by an LED on the docking unit of the stationary unit (POS HUB) until the peripherals are released again, or a time-out situation occurs and the pairing is interrupted after a message from the tablet or the tablet POS-Device HUB to the administration server.

[0068] For this purpose, the peripheral devices are not connected to a POS system but rather to the substantially simpler POS device HUB computer (stationary unit) (FIG. 2, FIG. 4, FIG. 6). A small operating system can run on this stationary unit.

[0069] For the data transmission from the peripheral device to the application program, a multiplexer program which receives data from all peripheral devices, transmits them via the wireless transmission path to the mobile device (tablet) in packets with a device identifier on the control computer (stationary unit). Therefore, the package identification is read with a corresponding demultiplexer program. The individual packets are unblocked according to the packet identification and distributed to so-called virtual RS232 ports, which offer the same interface in the direction of the application program for the peripheral devices. A virtual RS232 port is assigned to each of the peripheral devices. The virtual RS232 port is realized by a program which on the operating system treats the same application program calls that are used on the traditional POS system for connected RS232 devices.

[0070] The same procedure takes place for data transmission from the application program to the peripheral device, but the multiplexer program runs on the mobile device and the de-multiplexer program runs on the control computer. In the same way, the data is transmitted in packets with peripheral identification via the wireless transmission link:

[0071] The application calls a WRITE, which transports the data to the virtual RS232 port program. This transports the data to the multiplexer program, which then transmits it as a packet with a device identifier via the wireless transmission link. The packet is received at the control computer, wherein the packet identification in the demultiplexer program is evaluated and sent to the addressed peripheral device.

[0072] As wireless communication, industrial standards such as Wireless LAN (WLAN), Bluetooth, Bluetooth Low Energy, Bluetooth Low Energy Beacon Technology or ZigBee can he used. The question of which industrial standard is suitable also decides whether the wireless transmission path guarantees latencies (better: response delays) that are shorter than the times which are implemented in application and software layers as timeout times for access to RS232 devices. These are usually within the ten millisecond range and can be achieved with some standards.

[0073] WLAN is used here because of the higher range for peripheral devices which are regarded as not time-critical, while Bluetooth or ZigBee is used for communication with devices which have to be treated with a fixed maximum response time (see above). Bluetooth or even ZigBee offer a better interference-free transmission as WLAN, however, depending on the selected device class, at shorter distances.

[0074] This results in the advantage of maintaining a short distance between the mobile device and devices which are critically to be handled in a financial manner, such as the cash drawer (safe). The user is thus forced to stay in the vicinity of the cash drawer when it is opened.

[0075] Data traffic under Bluetooth or other wireless local area connectivity technologies should be protected against possible manipulation by means of an additional software layer (e.g. RSA encryption). The receiver key is transmitted on a different data path as a Bluetooth or ZigBee (e.g. WLAN).

[0076] In order to guarantee the required monitoring-proof and tamper-proof transmission to the peripheral devices, the payment terminal and the cash drawer, the packets are encoded inside the multiplexer and demultiplexer program according to a symmetrical or asymmetrical encryption method, in particular. In order to increase security, the key exchange between the tablet and the control computer is done on an alternative transmission path. This can either be wireless, but with an alternative industry standard that is not used for regular data transfer, or otherwise by data transfer (e.g. USB stick) which has to be inserted at the tablet and at the control computer with every key exchange, or also via another route, e.g. through the management unit/administration server.

[0077] The application program on the tablet can directly access the POS peripheral units on the virtual RS232 ports provided here with the multiplexer and demultiplexer program. Herein, it is hidden from the application program that a wireless communication is used.

[0078] Since there generally is a device control layer below the application program which allows the control of USB peripherals and their RS232 variant in the same way, USB devices can also be controlled via virtual RS232 ports without an application program change. The same also applies to devices which are controlled by special physical connection types.

[0079] Furthermore, alternative wire-bound or wireless connections to another peripheral set are conceivable.

[0080] Alternatively, a mobile device can connect, e.g. by an installation parameter or by a separate dialog, with another control computer, thus accessing a different POS peripheral unit set.

[0081] The control computer only allows the connection with one mobile device to avoid the fact that several users are simultaneously accessing e.g. a cash drawer or perform a printing job. A change can always take place after the completion of a receipt transaction. To do this, the mobile device connected before must disconnect before another mobile device can log on.

[0082] The logon and logout of a mobile device to the control computer also takes place by means of data transmission with a symmetrical or asymmetrical versification/encryption. The necessary key exchange is performed in the same manner as described above. The above-described rule set on the management unit finally decides which mobile unit is allowed to connect with which stationary unit and thus also the interlocking of the mobile unit is triggered. In addition, it is also possible to define which mobile unit is allowed to connect with which peripheral device at a stationary unit.

[0083] The rules evaluate parameters such as e.g. current time, individual user authorizations, permitted or forbidden assignments of mobile units to the stationary unit (“black list” or “whitelist”), and occupancy status of the stationary unit.

[0084] To do this, the rule set can use a database with certain tables.

[0085] Here is an example of a possible simple rule set. The control parameters are stored in a database in the form of tables which are then evaluated by the rules in order to make the decision as to whether a connection is valid or not.

EXAMPLE

[0086]

TABLE-US-00001 TABLE 1 Listing of all participating devices: network-address connection- # Name typ TCP/IP ID state 1 tablet1 mobile 196.168.0.10 2723ebaf 2 tablet2 mobile 196.168.0.11 2723ebae devicehub1 3 devicehub1 fixed 196.168.0.20 abef1234 tablet2 4 devicehub2 fixed 196.168.0.21 Ffefabab

[0087] Table 1 lists all devices and the current connection status of all mobile and stationary units involved.

[0088] In the event that a permitted connection could be established between two units—that is, the authentication was successful—the name of the other station, which is connected to the relevant station, is entered in the column “connection-state” 3).

[0089] When the connection is resolved, the entries in the “connections-state” column are deleted again.

[0090] The following rule is used as a first rule to determine whether a connection is valid: [0091] In principle, only connections between two units should be permitted if one unit is a mobile unit (column “type” contains the value “mobile”) and the other unit is a stationary one (column “type” contains the value “fixed”). If this is not the case, the connection is rejected. [0092] In principle, only connection requests from units are permitted if the sender has a TCP/IP address that is contained in the table. if the TCP/IP address is not found, the connection is rejected. [0093] Furthermore, the ID which should have a minimum length of 64 bits is compared with the one listed in the “ID” column. If it is not found, the connection request is rejected, [0094] If both units—the mobile and the stationary unit—are used with two IDs during the authentication request, both IDs are compared. If one of the IDs is not coherent or does not match the TCP/IP address, the connection is rejected.

[0095] Further verifications of the authenticity of the requesting unit via its so-called network MAC address beside the TCP/IP address would be possible by means of a further column “MAC address”. Alternatively, authentication can also be performed exclusively via the MAC address, in the case that dynamic TCP/IP addresses are used. Connection rejection always means that no interlocking of the mobile unit takes place.

[0096] In a further development stage, it is also conceivable to carry out a so-called “black list” which is to refuse possible connections that are statutory according to the basic list. For this purpose, a further table can be defined, which contains pairs of mobile units which are not allowed to be connected to each other. For pairs not listed, a connection is allowed.

EXAMPLE

[0097]

TABLE-US-00002 TABLE 2 Black list: # Name-mobile Name-stationary 1 tablet1 devicehub2 2 . . . . . . 3 tablet3 *

[0098] For example, the above table defines: [0099] the mobile unit tablet1 must never connect to the stationary unit devicehub2 (line 1). [0100] This can he useful, for example, if the tablets of operating personnel in the first floor of a department store want to connect to the stationary units of the second floor, but this is not wanted. Then all combinations of the tablets of the first floor with the stationary units of the second floor would be entered into the “black list”: [0101] that the mobile unit tablet3 is not allowed to connect to any stationary unit. [0102] This can he useful, for example, if a tablet has been lost due to theft.

[0103] Instead of a black list, a white list table is also conceivable: the combinations of mobile and stationary units, which are only allowed, are then enumerated. All other combinations are not allowed.

[0104] As a further design stage of the set of rules, it is conceivable that connections from mobile units to stationary units can only take place at certain times (e.g. Opening times, working hours, vacation times, shift times, etc.—are permitted. This can for instance be achieved by an additional table that is defining corresponding time windows:

TABLE-US-00003 TABLE 3 Timing: # Name-mobile time Days of the week 1 tablet1 8:00-12:00, 13:00-20:00 Mo, Tu, We, Thu, Fr 2 tablet2 8:00-12:00, 13:00-16:00 Sa, Su 3 . . . . . . . . .

[0105] The table contains the times for all mobile units in which connections to stationary units are allowable.

[0106] Outside the defined time windows, connection requests are rejected. If an mobile unit that is already connected is connected to a stationary unit and the user exceeds the defined time window, it is useful not to automatically perform a connection termination, but rather: [0107] only after the explicit, intended end of the connection by the user, or [0108] to perform an automatic connection termination after a defined period of inactivity of the mobile unit.

[0109] This approach is useful in order to complete a sales transaction that has already begun and to terminate the necessary control of the periphery.

[0110] As a further embodiment of the rule set, it is conceivable to extend the authentication of permitted connections to a user control. Particularly when mobile units are not exactly assigned to one user and several operating forces share mobile units at different working times. Here, tables 2, 3 can be extended by a further column “Users” which are then used for evaluation.

TABLE-US-00004 Example Table 2b - as Black List: # Name-mobile Name-stationary User 1 tablet1 devicehub2 2 . . . . . . 3 tablet3 * 4 tablet2 * User1 5 * * User2

[0111] The query could be as follows: [0112] if the row entry in the “User” column of Table 2 is empty, the rule applies to all users. [0113] if the row entry in the User column of Table 2 contains one or more users, the rule is only valid if the current user name is one with the User column.

[0114] In the example of table 2b, the additional entry in line 4 causes the mobile unit “tablet2” to be no longer used for the drive of the stationary unit for the user 1.

[0115] In the example table 2b, the add-on entry in line 5 causes all mobile units for the user 2 to be no longer used for controlling any stationary units.

[0116] The same can be defined for Table 3.

[0117] As a further design stage of the rule set it is conceivable to define the authentication of permitted connections not only between mobile and stationary units with reference to the stationary unit, but additionally to extend the authentication to the connected peripheral units. Furthermore, it can, e.g., be defined that certain users only have access to the cash drawer, since they are authorized as collector to handle cash rather than just for example a consultant who is allowed to use peripherals such as the printer, the display, and the scanner.

[0118] The rule set is then be expanded in such a way that, if the result “connection allowed” has been generated in the case of an evaluation carried out with the other rules, a further table is searched in order to determine which of the peripheral devices can be used.

TABLE-US-00005 Example Table 4 - Peripheral Control: # Name-mobile User Peripheral unit 1 tablet1 User1 Scanner, Printer, LineDisplay 2 tablet1 UserBoss * 3 tablet1 User3 Scanner, Printer, Line Display 4 tablet2 * *

[0119] In this example, the following rules are defined: [0120] Line 1: If a connection setup for the tablet is classified to be “allowed” to a stationary unit with the previous rules as “in the name-mobile” column, and the user “User1” has logged in, the access to the peripheral equipment scanners, printers, line display is granted. The cash drawer and the scale cannot be controlled by the user. [0121] Line 2: If a connection set-up for the tablet is classified as “allowed” to a stationary unit with the previous rules as “allowed” in the column “Name-mobile”, and the user “UserChef” Access all I/O devices (e.g, an open cash drawer), [0122] Line 3 describes the same rule as line 1, but for the user “user3” [0123] Line 4: If the Tablet 2 is used and the previous rules have classified a connection set as “allowed”, each user is allowed to access all peripheral devices.

[0124] How the tablets that are not listed in this table are treated ultimately depends on the definition of the rules. It is conceivable that this rule extension leads to the fact that the connection is again classified as “not allowed” for all rules not listed above,

[0125] Alternatively, it is also conceivable that non-listed tablets cause this rule not to be applied, but the result of the previous rules is used as the final result.

[0126] In a further embodiment of the rule set, it is conceivable that an access to the cash drawer can only be effective if a minimum distance between the mobile unit and the stationary unit with the cash drawer connected thereto is ensured. For this purpose, a so-called ibeacon™ can be attached to the cash drawer or the stationary unit. This sends a unique identification number (UUID). The mobile input device can then use the signal strength to determine the distance from which the stationary device and the cashbox connected thereto are located, The following table shows a possible parameterization of the rule set:

TABLE-US-00006 Example Table 5 - Distance-dependent access to the cash drawer: Access to cash # Distance Status drawer Peripheral unit 1 Unknown Not granted Cash drawer 2 Far (to 30 m) Not granted * 3 Near (to 2 m) granted * 4 Immediate granted * (to 50 cm)

[0127] FIG. 5 shows a corresponding exemplary sequence of steps for a Windows operating system. Alternatively, the method can also be implemented on other operating systems such as Linux, Unix, iOS, Blackberry and/or Android. [0128] The user moves with the mobile unit in the direction of the stationary unit/POS device HUB or alternatively The mobile unit is plugged into the docking unit of the stationary unit/POS device HUB. [0129] The NFC reader of the mobile unit detects the NFC tag of the POS device HUB, which contains the device ID with a minimum length of 64 bits. [0130] The mobile unit receives a message from the NFC Reader with tag #. With this tag, the administration unit/admin server is contacted in order to obtain the name of the assigned stationary device. The function is POSDeviceHUB (getPDHID (NFCtag #)), it should be noted that the name of the POS device HUB can alternatively be obtained from a central point in the store provided by the POS application server. [0131] The tablet/mobile unit connects to the POS Device Hub via the virtual driver with its name and is ready for the next transaction. [0132] Performing a transaction (receipt): scanning goods, entering goods, determining the total amount, printing the receipt document, opening the cash drawer, calculating the bill of exchange, and closing the cash drawer. [0133] The user moves with the mobile unit away from the POS device HUB, or alternatively: [0134] the user presses the “undock” button in the user interface of the mobile unit; the docking unit of the POS device HUB releases the mobile unit and the user moves with the mobile unit away from the POS device HUB. [0135] The NFC reader of the mobile unit, detects the absence of the NFC tag of the POS device HUB. [0136] The mobile unit is detached from the POS Device Hub and is ready for another transaction.

[0137] In this method, it has been described how the mobile unit can be connected to the stationary unit with the integration of the management unit.

[0138] In the following, the invention is described by the claims, which are to be interpreted in a broadest form. The scope of protection is determined according to the claims. The description is not intended to be limiting to scope of protection.