WO2022005469A1

WO2022005469A1 - Updates for point of sale devices

Info

Publication number: WO2022005469A1
Application number: PCT/US2020/040465
Authority: WO
Inventors: Adrian L. PATSCHKE; Binh T. Truong; Pun Yi LEE; Yuk C. LO
Original assignee: Hewlett Packard Development Co LP
Current assignee: Hewlett Packard Development Co LP
Priority date: 2020-07-01
Filing date: 2020-07-01
Publication date: 2022-01-06
Anticipated expiration: 2023-01-01

Abstract

In some examples, a computing device can include a memory resource storing instructions to cause a processor resource to transmit a Unified Point of Sale (UPOS) call to a point of sale (POS) device to retrieve device information from the POS device, compare the device information to device reference information included in a database, and cause the device information to be updated in response to a failure to match the device information with the device reference information included in the database.

Description

UPDATES FOR POINT OF SALE DEVICES

Background

[0001] Point of sale (POS) devices may be utilized for interactions. For example, retail transactions may be facilitated utilizing POS devices. For instance, a customer in a retail setting may pay a merchant for goods via a POS device.

Brief Description of the Drawings

[0002] Figure 1 is an example of a computing device for updates for POS devices.

[0003] Figure 2 illustrates an example of a computing device for updates for

POS devices.

[0004] Figure 3 illustrates a block diagram of an example system for updates for POS devices.

[0005] Figure 4 illustrates an example of a method for updates for POS devices.

Detailed Description

[0006] A POS device may be utilized at a time and a place where a retail transaction is completed. As used herein, the term “POS device” refers to a hardware device utilized to process a POS operation. For example, when a customer wants to conduct a transaction, a merchant can utilize the POS device to calculate an amount owed by the customer and facilitate a transaction between the customer and the merchant. For instance, the customer may exchange payment for goods, services, or otherwise via cash, a debit card, credit card, etc. with the merchant via the POS terminal. The POS terminal may present an amount owed by the customer, facilitate the exchange of payment with the customer, and/or generate a receipt for the customer, among other services. In addition, the POS terminal may include functionality for the merchant, such as inventory management, customer relationship management, financial tracking, etc.

[0007] POS devices may include POS terminals and POS peripheral devices. As used herein, the term “POS terminal” refers to a computing device utilized to process a POS operation. As used herein, the term “computing device” refers to an electronic system having a processor resource and a memory resource. For example, a POS terminal can utilize a processor resource that can execute instructions stored on a memory resource to process a transaction such as, for instance, at a retail location. In some examples, the POS terminal can be a stationary computing device. In some examples, the POS terminal can be a mobile computing device which can be carried and/or worn by a user, such as a tablet, personal digital assistant (PDA), mobile phone, laptop, etc.

[0008] The POS terminal may utilize a POS peripheral device to process a transaction. As used herein, the term “POS peripheral device” refers to an electronic device that operates separately from a POS terminal but is connectable to the POS terminal in order to assist in processing a POS operation. For example, a POS terminal may utilize a scanner device (e.g., a POS peripheral device for scanning) to scan a barcode of an item a customer would like to purchase. The POS terminal may calculate an amount owed by the customer for the item, a line display (e.g., a POS peripheral device for displaying) may display the amount owed to the customer, and the customer may utilize a scanner (e.g., a POS peripheral device for scanning) to transmit credit card information from the customer to facilitate payment for the item. Such a combination of POS devices (e.g., POS terminals and POS peripheral devices) can be utilized by a merchant in order to facilitate transactions and/or other functions, as described above.

[0009] During setup and/or use of POS devices, such devices may develop operational issues. For example, while a manufacturer may produce POS devices, each merchant who procures and utilizes such POS devices may include their own device information such as firmware, drivers, operating systems (OS), etc. for operation. Such POS devices can develop operational issues as a result of outdated device information. For example, a POS device may be malfunctioning as a result of an outdated driver.

[0010] Determining whether such device information is outdated can be a difficult task. For example, different vendors may utilize different POS devices, and different POS devices may include different device information. Such a task can be a time and/or labor-intensive process as a result of the different device information, as different utilities and/or tools may have to be used in order to access the device information for different POS devices. Such a process could lead to a negative experience for merchants who purchase such devices.

[0011] Updates for POS devices can allow for a computing device to determine device information from POS devices in order to determine whether such device information should be updated. The computing device can determine device information from different types of POS devices and cause the device information of such types of POS devices to be updated. The computing device can therefore provide a centralized mechanism to determine information from and update POS devices including POS terminals and/or POS peripheral devices.

[0012] Figure 1 is an example of a computing device 102 for updates for POS devices. The computing device 102 can be connectable to POS devices 104-1, 104- 2, 104-N.

[0013] As illustrated in Figure 1, the computing device 102 can be connectable to POS devices 104-1, 104-2, 104-N. As described above, the POS devices 104-1, 104-2, 104-N can be utilized to process a transaction. For instance, in some examples POS device 104-1 can be a POS terminal and POS device 104-2 can be a receipt printer. A customer may pay for a good via the POS terminal (e.g., POS device 104-1), and the receipt printer (e.g., POS device 104-2) can print a receipt for the good for the customer.

[0014] Such POS devices 104-1, 104-2, 104-N may not be limited to a POS terminal and a receipt printer. For example, the POS devices 104-1, 104-2, 104-N can include a barcode scanner, cash drawer, line display, magnetic strip reader, pin pad, etc. Additionally, such POS devices 104-1, 104-2, 104-N may include components such as universal serial bus (USB) controllers, retail docks, powered serial ports, power delivery controllers, USB hubs, network adapters, storage devices, audio output devices, etc., where such components may be peripheral POS devices connectable to a POS terminal and/or peripheral POS devices integrated within a POS terminal. Such POS devices may include device information, such as firmware, drivers, operating systems (OS), etc. for operation, which may have to be updated. As used herein, the term "OS" refers to a collection of executable instructions that manage hardware, software, and provide services for a device. Such updates can ensure the POS devices 104-1, 104-2, 104-N function without operational issues.

[0015] In order to determine whether device information for a POS device

104-1, 104-2, 104-N should be updated, the computing device 102 can retrieve device information from a POS device 104-1, 104-2, 104-N. The computing device 102 can transmit a Unified Point of Service (UPOS) call to a POS device 104-1, 104- 2, 104-N to retrieve device information from the POS device 104-1, 104-2, 104-N.

As used herein, the term “UPOS call” refers to a request for information from a point of sale (POS) device having a peripheral architecture defined by the UPOS standard. As used herein, the term “device information” refers to data descriptive of a POS device. For example, device information can include a driver version of a POS device 104-1, 104-2, 104-N, a firmware version of a POS device 104-1, 104-2, 104- N, an OS version of a POS device 104-1, 104-2, 104-N, a connection status of a POS device 104-1, 104-2, 104-N, and/or a function status of a POS device 104-1, 104-2, 104-N, as is further described herein.

[0016] The computing device 102 can transmit the UPOS call to the POS device 104-1 , 104-2, 104-N via a wired or wireless connection. The wired or wireless network connection can be a network relationship that connects the computing device 102 to the POS devices 104-1, 104-2, 104-N. Examples of such a network relationship can include a local area network (LAN), wide area network (WAN), personal area network (PAN), a distributed computing environment (e.g., a cloud computing environment), storage area network (SAN), Metropolitan area network (MAN), a cellular communications network, Long Term Evolution (LTE), visible light communication (VLC), Bluetooth, Worldwide Interoperability for Microwave Access (WiMAX), infrared (IR) communication, Public Switched Telephone Network (PSTN), radio waves, and/or the Interet, among other types of network relationships.

[0017] Transmitting the UPOS call to a POS device 104-1, 104-2, 104-N can include transmitting an initialization call to the POS device 104-1, 104-2, 104-N. As used herein, the term “initialization call" refers to a request from a device to initialize communication with another device. The initialization call to a POS device 104-1, 104-2, 104-N can be utilized to determine whether the POS device 104-1, 104-2, 104-N is in use. If a POS device 104-1, 104-2, 104-N is in use (e.g., in communication with another device) when the initialization call is transmitted to the POS device 104-1, 104-2, 104-N, the POS device 104-1, 104-2, 104-N may not receive the initialization call, as is further described herein. If a POS device 104-1 , 104-2, 104-N is not in use, the initialization call can initialize communication between the POS device 104-1, 104-2, 104-N and the computing device 102. For example, the computing device 102 can transmit the initialization call to the POS device 104-1, 104-2, 104-N via a communication interface between the computing device 102 and the POS device 104-1, 104-2, 104-N, such as a COM port, a USB interface (e.g., USB human interface device (HID) interface, USB with virtual COM interface, etc.), Bluetooth, parallel port, etc.

[0018] The computing device 102 can transmit, in response to the initialization call initializing communication with the POS device 104-1, 104-2, 104-N, a retrieve call to the POS device 104-1, 104-2, 104-N to retrieve device information from the POS device 104-1, 104-2, 104-N. As used herein, the term “retrieve call” refers to a request from a device for information from another device. The retrieve call can be, for example, a retrievestatisticsQ call. The retrievestatisticsQ call can be a retrieve call defined by the UPOS standard that can be utilized to request device information from the POS device. For instance, the computing device 102 can transmit a UPOS call to POS device 104-2 (e.g., a magnetic strip reader) to request device information from the POS device 104-2 once in communication with the POS device 104-2. In response, the POS device 104-1, 104-2, 104-N can transmit device information to the computing device 102.

[0019] In some examples, the POS device 104-1, 104-2, 104-N may not receive the initialization call. For example, the POS device 104-1, 104-2, 104-N may be in use when the initialization call is transmitted to the POS device 104-1, 104-2, 104-N. In such an example, the computing device 102 can transmit, in response to the initialization call failing to initialize communication with the POS device 104-1, 104-2, 104-N, another initialization call to the POS device 104-1, 104-2, 104-N after a predetermined amount of time. For example, the computing device 102 may transmit an initialization call to the POS device 104-2 (e.g., a magnetic strip reader) which fails to initialize communication, as the POS device 104-2 may be in communication with another device (e.g., a modem). The computing device 102 can transmit another initialization call to the POS device 104-2 after one hour to initialize communication with the POS device 104-2. The predetermined amount of time may not be limited to one hour. For example, the predetermined amount of time may be two hours, eight hours, one day, or any other amount of time, and may be modifiable.

[0020] In some examples, the computing device 102 can transmit, in response to the initialization call failing to initialize communication with the POS device 104-1, 104-2, 104-N, another initialization call to the POS device 104-1, 104-2, 104-N at a predetermined time period. For example, the computing device 102 may transmit an initialization call at 10 AM on a weekday (e.g., a Monday) to the POS device 104-1, 104-2, 104-N which fails to initialize communication with the POS device 104-1, 104- 2, 104-N. The computing device 102 can transmit another initialization call to the POS device 104-1, 104-2, 104-N at a predetermined time period (e.g., after 5 PM during weekdays, during the weekend, etc.). The predetermined time period may correspond to hours in which a retail location including the POS device 104-1, 104-2, 104-N may be closed, for instance.

[0021] In some examples, the computing device 102 can transmit a direct access call to the POS device 104-1, 104-2, 104-N to retrieve the device information from the POS device 104-1, 104-2, 104-N in response to the initialization call failing to initialize communication with the POS device 104-1, 104-2, 104-N. As used herein, the term “direct access call” refers to a request from a device to access information directly at the physical location of the information at another device. For instance, the computing device 102 can transmit a direct access call to directly access device information at a location at which the device information is located at a POS device 104-1, 104-2, 104-N. For example, the computing device 102 can transmit a direct access call to directly access a firmware of a POS device 104-1 , 104-2, 104-N to retrieve the device information from the firmware of the POS device 104-1, 104-2, 104-N.

[0022] In some examples, transmitting a direct access call can include transmitting a first call to the POS device 104-1, 104-2, 104-N to cause the POS device 104-1, 104-2, 104-N to cease communication with another device. For example, POS device 104-1 (e.g., a POS terminal) may be in communication with another device (e.g., a modem) and as a result, the initialization call from a transmitted UPOS call can fail to initialize communication with the POS device 104- 1. As a result, the computing device 102 can transmit a direct access call to the POS device 104-1 by transmitting a first call to cause the POS device 104-1 to cease communication with the modem. [0023] In some examples, transmitting a direct access call can include transmitting a first call to the POS device 104-1, 104-2, 104-N in order to initialize communication with the POS device 104-1, 104-2, 104-N in parallel with the POS device 104-1, 104-2, 104-N being in communication with another device. For example, POS device 104-1 (e.g., a POS terminal) may be in communication with another device (e.g., a modem). As a result, the computing device 102 can transmit a direct access call to the POS device 104-1 by transmitting a first call to cause the POS device 104-1 to be in communication with the modem and the computing device 102 simultaneously.

[0024] In response to the POS device 104-1, 104-2, 104-N ceasing communication (e.g., with another device), the computing device 102 can transmit a second call to the POS device 104-1, 104-2, 104-N to retrieve the device information from the POS device 104-1, 104-2, 104-N. For example, the computing device 102 can transmit the second call to POS device 104-1 (e.g., a POS terminal) to request device information from the POS device 104-1 once in communication with the POS device 104-1. In response, the POS device 104-1, 104-2, 104-N can transmit device information to the computing device 102.

[0025] In response to the device information being retrieved from the POS device 104-1, 104-2, 104-N, the computing device 102 can transmit a third call to the POS device 104-1, 104-2, 104-N to cause the POS device 104-1, 104-2, 104-N to reinitialize communication with the another device. For example, the computing device 102 can transmit a third call to the POS device 104-1 (e.g., the POS terminal) to reinitialize communication with another device (e.g., a modem).

[0026] In some examples, the computing device 102 can transmit another initialization call (e.g., a second initialization call) using the UPOS call in response to a first initialization call failing to initialize communication with a POS device 104-1, 104-2, 104-N (e.g., after a predetermined amount of time or at a predetermined time period, as described above) and in response to the second initialization call failing to initialize communication with the POS device 104-1, 104-2, 104-N, transmit a direct access call. However, examples are not so limited. For instance, in some examples, in response to the first initialization call failing to initialize communication with a POS device 104-1, 104-2, 104-N via a UPOS call, the computing device 102 can transmit a direct access call (e.g., and not a second initialization call). In some examples, the computing device 102 can transmit a third initialization call in response to a first and second initialization call failing to initialize communication with a POS device 104-1, 104-2, 104-N via a UFOS call (e.g., and not transmit a direct access call).

[0027] As described above, device information refers to data descriptive of a POS device. In some examples, device information can include device status information of a POS device 104-1, 104-2, 104-N. As used herein, the term “device status information” refers to data descriptive of an operational condition of a POS device. For example, the device status information can include a connection status of a POS device 104-1, 104-2, 104-N and a function status of a POS device 104-1, 104-2, 104-N.

[0028] As used herein, the term “connection status” refers to data descriptive of an affiliation condition of a POS device. For example, the connection status of a POS device 104-1, 104-2, 104-N can include whether a POS device 104-1, 104-2, 104-N is connected or not connected to another device, such as another POS device 104-1, 104-2, 104-N. For example, POS device 104-1 can be a barcode scanner, and can include a connection status (e.g., connected) as to whether POS device 104-1 is connected to another POS device 104-2 (e.g., a POS terminal) or not connected to POS device 104-2.

[0029] As used herein, the term “function status" refers to data descriptive of an operational status of a POS device. For example, the function status of a POS device 104-1, 104-2, 104-N can include whether a POS device 104-1, 104-2, 104-N is communicating with another POS device 104-1, 104-2, 104-N, a mode of the POS device 104-1, 104-2, 104-N, a health of the POS device 104-1, 104-2, 104-N, etc.

For example, POS device 104-1 can be a magnetic strip reader with a pin pad, where the function status of the POS device 104-1 can include a communication mode of the POS device 104-1 (e.g., serial communication mode, USB composite mode, USB HID mode, etc.), whether the POS device 104-1 is communicating with another POS device 104-2, 104-N, a health of the POS device 104-1 (e.g., whether the POS device 104-1 is online, connected, and/or in a state to return an acknowledgment response back to the computing device 102 or other host, etc.)

[0030] In some examples, device information can include device state information of a POS device 104-1, 104-2, 104-N. As used herein, the term “device state information” refers to data descriptive of control and management attributes of a POS device. For example, the device state information can include a driver version of a POS device 104-1, 104-2, 104-N, a firmware version of a POS device 104-1, 104-2, 104-N, and an OS version of a POS device 104-1, 104-2, 104-N. [0031] The driver version of a POS device 104-1, 104-2, 104-N can include an identifier that can categorize a state of a driver of a POS device 104-1 , 104-2, 104-N. As used herein, the term “driver” refers to a collection of executable instructions that operate or control a particular type of device. For example, POS device 104-1 may be a receipt printer having a driver that controls operation of the receipt printer. The driver version of the driver controlling the POS device 104-1 may be version 1.0, which may indicate an initial release of the driver for the POS device 104-1 , or may be a different version (e.g., version 1.6), which may indicate that several updates for the driver for the POS device 104-1 have been released since the initial version 1.0 release. Accordingly, a first driver version that has a different version number than a second driver version can indicate that the first driver version can be in a different state than the second driver version, and as a result, the second driver version may operate or control a particular POS device 104-1, 104-2, 104-N differently than the first driver version.

[0032] The firmware version of a POS device 104-1, 104-2, 104-N can include an identifier that can categorize a state of firmware of a POS device 104-1 , 104-2, 104-N. As used herein, the term “firmware” refers to a collection of executable instructions that provide machine-level control for hardware associated with a device. For example, POS device 104-2 may be a power delivery controller including firmware that can provide machine-level control of the hardware included in the power delivery controller. The firmware version of the firmware for a POS device 104-1, 104-2, 104-N may be version 1.029.02935, for example. Similar to the driver version, a first firmware version that has a different version number than a second firmware version can indicate that the first firmware version can be in a different state than the second firmware version, and as a result, the second firmware version may provide machine-level control for hardware associated with the POS device 104-1, 104-2, 104-N differently than the first firmware version.

[0033] A firmware of a POS device 104-1, 104-2, 104-N can include a basic input/output system (BIOS) of the POS device 104-1, 104-2, 104-N. As used herein, the term “BIOS” refers to refers to hardware or hardware and instructions to initialize, control, or operate a POS device prior to execution of an OS of the POS device and/or provide runtime services for the OS of the POS device. In some examples, a BIOS is interchangeable with or may implement or include the Unified Extensible Firmware Interface (UEFI) specification or another specification or standard for initializing, controlling, or operating a POS device.

[0034] For example, the POS device 104-1 may be a POS terminal including an OS. The POS device 104-1 may include a BIOS having a first BIOS version, where a second BIOS version for the POS device 104-1 may perform hardware initialization during the booting process of the POS device 104-1 and provide runtime services for an OS of the POS device 104-1 differently than the first BIOS version for the POS device 104-1.

[0035] The OS version of a POS device 104-1, 104-2, 104-N can include an identifier that can categorize a state of an OS of a POS device 104-1 , 104-2, 104-N. For example, POS device 104-2 may be a POS terminal including an OS that can manage hardware, software, and provide services for the POS terminal. The OS version of the OS for a POS device 104-1 , 104-2, 104-N may be version 7.0, for example. Similar to the driver version, a first OS version that has a different version number than a second OS version can indicate that the first OS version can be in a different state than the second OS version, and as a result, the second OS version may manage hardware, software, and provide services for a POS device 104-1, 104- 2, 104-N differently than the first OS version.

[0036] As described above, device information can include device status information including a connection status of a POS device 104-1, 104-2, 104-N and/or a function status of a POS device 104-1, 104-2, 104-N. Additionally, the device information can include device state information including a driver version of a POS device 104-1, 104-2, 104-N, a firmware version of a POS device 104-1, 104-2, 104-N, and/or an OS version of a POS device 104-1 , 104-2, 104-N. Certain POS devices may include all of the above device information or some of the above device information. For example, a POS terminal may include a connection status, a function status, a driver version, a firmware version, and an OS version, whereas a magnetic strip reader may include a connection status, a function status, and a firmware version.

[0037] As described above, the computing device 102 can retrieve the device information from a POS device 104-1, 104-2, 104-N via a UPOS call and, if the initialization call of the UPOS call fails to initialize communication with the POS device 104-1, 104-2, 104-N, via a direct access call. For example, POS device 104- 1 can be a POS terminal, and the computing device 102 can retrieve device information including whether the POS terminal is connected to another device, a driver version of the POS terminal (e.g., version 1.0), a firmware version of the POS terminal (e.g., version 1.029.02935), and an OS version of the POS terminal (e.g., version 7.0). As another example, the POS device 104-2 can be a magnetic strip reader, and the computing device 102 can retrieve device information including whether the magnetic strip reader is connected to another device, whether the POS terminal is in a particular mode (e.g., serial communication mode), and a firmware version of the magnetic strip reader (e.g., version 2.025.53265). In some examples, the computing device 102 can retrieve the device information in a particular data format, such as Extensible Markup Language (XML), JavaScript Object Notation (JSON), Yet Another Markup Language (YAML), etc.

[0038] The computing device 102 can compare the device information to device reference information included in a database 106. As used herein, the term “device reference information” refers to data descriptive of a version of control and management attributes of a POS device. For example, the device reference information can include information describing the most recently updated and/or released versions of drivers, firmware, and OSs. The database can include, for instance, manufacturer and/or developer verified reference information.

[0039] The device reference information can, in some examples, be stored in a database 106. As illustrated in Figure 1, the database 106 can be remote from the computing device 102, and the computing device 102 can communicate with the database 106 via a network relationship. However, although not illustrated in Figure 1, in some examples the database 106 can be located locally at the computing device 102 (e.g., stored in a memory resource integrated within the computing device).

[0040] Continuing with the POS terminal example above, the POS device 104- 1 can be a POS terminal and the computing device 102 can compare the device information for POS device 104-1 (e.g., a driver version 1.0 of the POS terminal, a firmware version 1.029.02935, and an OS version 7.0) to device reference information included in the database 106. For example, the device reference information can include a driver version (e.g., driver version 1.5), a firmware version (e.g., firmware version 1.029.02935), and an OS version (e.g., OS version 10.0). As a result of the comparison, the computing device 102 can determine that certain device information for POS device 104-1 does match the device reference information (e.g., the firmware version of POS device 104-1 matches the device reference version of the firmware version), but other device information for POS device 104-1 does fails to match the device reference information. For example, the driver version for POS device 104-1 (e.g., version 1.0) does not match the driver version included in the device reference information (e.g., version 1.5) and the OS version for POS device 104-1 (e.g., version 7.0) does not match the OS version included in the device reference information (e.g., version 10.0).

[0041] The computing device 102 can cause the device information for a POS device 104-1, 104-2, 104-N to be updated in response to a failure to match the device information associated with the POS device 104-1, 104-2, 104-N with the device reference information included in the database 106. Updating the device information can include updating a firmware of a POS device 104-1, 104-2, 104-N, updating a driver of a POS device 104-1, 104-2, 104-N, and/or updating an OS of a POS device 104-1, 104-2, 104-N. For example, the computing device 102 can cause the driver version of the POS device 104-1 to be updated (e.g., from version 1.0 to version 1.5) and the OS version of the POS device 104-1 to be updated (e.g., from version 7.0 to version 10.0) in response to a failure to match the driver version and the OS version of the POS device 104-1 with the device reference information included in the database 106. Updating the OS version of a POS device 104-1 , 104- 2, 104-N can include updating the OS, applying a hotfix, applying a quick-fix engineering update (QFE), etc.

[00421 Updates for POS devices can allow for the automatic determination of

POS device information for different POS devices without having to utilize specialized development tools for POS devices having various different types, manufacturers, and utilized by different merchants in previous approaches. By retrieving and comparing such device information to device reference information included in a database, time and/or labor-intensive processes can be avoided, which can lead to a positive experience for merchants and/or others.

[0043] Such device reference information may, from time to time, be updated. For example, a manufacturer or developer may release an updated driver version, firmware version, and/or OS version. The database 106 can update the device reference information included in the database 106 in response to an updated version of the device reference information being released. For example, in response to an updated driver version, firmware version, and/or OS version being released, the device reference information included in the database 106 can correspondingly be updated in order to ensure that device information for POS devices 104-1, 104-2, 104-N is up to date.

[0044] In some examples, the manufacturer or developer may store updated device reference information in a remote database (e.g., not illustrated in Figure 1). Such updated device information may be updated according to a predetermined release schedule. For example, a manufacturer or developer may release updated device reference information each quarter. Accordingly, the database 106 can compare versions of the device reference information included in the database 106 to device reference information included in the remote database at a predetermined time interval. For instance, the database 106 can compare a driver version, firmware version, and/or OS version included in the database 106 to a driver version, firmware version, and/or OS version included in the remote database every quarter (e.g., or any other time interval).

[0045] In response to a failure to match the version of the device reference information included in the database 106 with the version of the device reference information included in the remote database, the database 106 can update the version of the device reference information included in the database 106 to correspond to the version of the device reference information included in the remote database. For example, the database 106 can compare an OS version (e.g., version 10.0) included in the database 106 to an OS version (e.g., version 11.0) included in the remote database, and since the OS version in the database 106 does not match the OS version in the remote database, the database 106 can update the OS version (e.g., version 10.0) to the updated OS version (e.g., version 11.0) included in the remote database 106.

[0046] In some examples, a manufacturer or developer may release updated device reference information and notify the database 106 of such an update. For example, the database 106 can receive an input indicating that an updated version of device reference information has been released. Accordingly, the database 106 can update the device reference information included in the database 106 to correspond to the updated device reference information included in the remote database in response to receiving the input The input may be, for instance, automatically generated and sent by the remote database to the database 106, may be transmitted in response to a manual input to the remote database, etc.

[0047] When the database 106 is updated with newly released/updated device reference information, a POS device 104-1, 104-2, 104-N can be correspondingly updated as described above with the newly released/updated device reference information. For example, an OS version 11.0 may be released and the database 106 can be updated with the updated OS version 11.0. The computing device 102 can retrieve updated device information from a POS device 104-1, 104-2, 104-N.

The computing device 102 may retrieve the updated device reference information from the POS device 104-1, 104-2, 104-N by transmitting a UPOS call or a direct access call if the UPOS call fails to initialize communication with the POS device 104-1, 104-2, 104-N.

[0048] The computing device 102 can compare the retrieved updated device information from the POS device 104-1, 104-2, 104-N with the updated device reference information included in the database 106. For example, the computing device 102 can retrieve the updated device information of the POS device 104-1 (e.g., an OS version 10.0), and the computing device 102 can compare the updated device information for the POS device 104-1 (e.g., OS version 10.0) to updated device reference information included in the database 106 (e.g., OS version 11.0).

In response to a failure to match the updated device information associated with the POS device 104-1, 104-2, 104-N with the updated device reference information, the computing device 102 can cause the updated device information of the POS device 104-1, 104-2, 104-N to again be updated. For example, the computing device 102 can cause the OS version of the POS device 104-1 to be updated (e.g., from OS version 10.0 to OS version 11.0). In such a manner, the device information of POS devices 104-1, 104-2, 104-N can be updated when the device reference information of the database 106 is updated.

[0049] Figure 2 illustrates an example of a computing device 202 for updates for POS devices. Although not illustrated in Figure 2, the computing device 202 may include a processor and a non-transitory machine-readable storage medium. Although the following descriptions refer to a single processor and a single machine- readable storage medium, the descriptions may also apply to a system with multiple processors and multiple machine-readable storage mediums. In such examples, the computing device 202 may be distributed across multiple non-transitory machine- readable storage mediums and across multiple processors. Put another way, the instructions executed by the computing device 202 may be stored across multiple machine-readable storage mediums and executed across multiple processors, such as in a distributed or virtual computing environment.

[0050] Processor resource 210 may be a central processing unit (CPU), a semiconductor-based microprocessor, and/or other hardware devices suitable for retrieval and execution of machine-readable instructions 214, 216, 218 stored in a memory resource 212. Processor resource 210 may fetch, decode, and execute instructions 214, 216, 218. As an alterative or in addition to retrieving and executing instructions 214, 216, 218, processor resource 210 may include a plurality of electronic circuits that include electronic components for performing the functionality of instructions 214, 216, 218.

[0051] Memory resource 212 may be any electronic, magnetic, optical, or other physical storage device that stores executable instructions 214, 216, 218 and/or data. Thus, memory resource 212 may be, for example, Random-Access Memory (RAM), an Electrically-Erasable Programmable Read-Only Memory (EEPROM), a storage drive, an optical disc, and the like. Memory resource 212 may be disposed within computing device 202, as shown in Figure 2. Additionally, memory resource 212 may be a portable, external or remote storage medium, for example, that causes computing device 202 to download the instructions 214, 216, 218 from the portable/extemal/remote storage medium.

[0052] The computing device 202 may include instructions 214 stored in the memory resource 212 and executable by the processor resource 210 to transmit a UPOS call to a POS device to retrieve device information from the POS device. The device information can include, for instance, device status information including a connection status of a POS device and/or a function status of a POS device. The device information can also include device state information, including a driver version of a POS device, a firmware version of a POS device, and/or an OS version of a POS device.

[0053] The computing device 202 may include instructions 216 stored in the memory resource 212 and executable by the processor resource 210 to compare the device information to device reference information included in a database. For example, the processor resource 210 can compare a driver version, a firmware version, and/or an OS version of a POS device to device reference information included in the database.

[0054] The computing device 202 may include instructions 218 stored in the memory resource 212 and executable by the processor resource 210 to cause the device information to be updated in response to a failure to match the device information associated with the POS device with the device reference information included in the database. For example, the processor resource 210 can determine that a driver version, a firmware version, and/or an OS version of a POS device does not match a driver version, a firmware version, and/or an OS version included in the database and, in response, can cause the driver version, firmware version, and/or the OS version of the POS device to be updated.

[0055] Figure 3 illustrates a block diagram of an example system 320 for updates for POS devices. In the example of Figure 3, system 320 includes a computing device 302 having a processor resource 310 and a non-transitory machine-readable storage medium 322. Although the following descriptions refer to a single processor resource and a single machine-readable storage medium, the descriptions are applicable to a system with multiple processors and multiple machine-readable storage mediums. In such examples, the instructions may be distributed across multiple machine-readable storage mediums and the instructions may be distributed across multiple processors. Put another way, the instructions may be stored across multiple machine-readable storage mediums and executed across multiple processors, such as in a distributed computing environment.

[0056] Processor resource 310 may be a central processing unit (CPU), microprocessor, and/or other hardware device suitable for retrieval and execution of instructions stored in machine-readable storage medium 322. In the particular example shown in Figure 3, processor resource 310 may receive, determine, and send instructions 324, 326, 328, and 330. As an alternative or in addition to retrieving and executing instructions, processor resource 310 may include an electronic circuit comprising a number of electronic components for performing the operations of the instructions in machine-readable storage medium 322. With respect to the executable instruction representations or boxes described and shown herein, it should be understood that part or all of the executable instructions and/or electronic circuits included within one box may be included in a different box shown in the figures or in a different box not shown. [0057] Machine-readable storage medium 322 may be any electronic, magnetic, optical, or other physical storage device that stores executable instructions. The executable instructions may be “installed” on the system 320 illustrated in Figure 3. Machine-readable storage medium 322 may be a portable, external or remote storage medium, for example, that allows the system 320 to download the instructions from the portable/extemal/remote storage medium. In this situation, the executable instructions may be part of an “installation package”.

[0058] Transmit a UPOS call instructions 324, when executed by a processor such as processor resource 310, may cause system 320 to transmit a UPOS call to a POS device to retrieve device information from the POS device. The device information can include, for instance, device status information including a connection status of a POS device and/or a function status of a POS device. The device information can also include device state information, including a driver version of a POS device, a firmware version of a POS device, and/or an OS version of a POS device.

[0059] Transmit a direct access call instructions 326, when executed by a processor such as processor resource 310, may cause system 320 to transmit, in response to the UPOS call failing to initialize communication with the POS device, a direct access call to the POS device to retrieve the device information from the POS device. For example, in an event in which the UPOS call fails to initialize communication with the POS device, the system 320 can transmit a direct access call to retrieve the device information from the POS device.

[0060] Compare device information to device reference information instructions 328, when executed by a processor such as processor resource 310, may cause system 320 to compare the device information to device reference information included in a database. For example, the system 320 can compare a driver version, a firmware version, and/or an OS version of a POS device to device reference information included in the database.

[0061] Cause the device information to be updated instructions 330, when executed by a processor such as processor resource 310, may cause system 320 to cause the device information to be updated in response to a failure to match the device information associated with the POS device with the device reference information included in the database. For example, the system 320 can determine that a driver version, a firmware version, and/or an OS version of a POS device does not match a driver version, a firmware version, and/or an OS version included in the database and, in response, can cause the driver version, firmware version, and/or the OS version of the POS device to be updated.

[0062] Figure 4 illustrates an example of a method 432 for updates for POS devices. For example, method 432 can be performed by a computing device (e.g., computing device 102, 202, 302, previously described in connection with Figures 1- 3, respectively).

[0063] At 434, the method 432 includes transmitting, by a computing device, a

UPOS call to a POS device to retrieve device information from the POS device. The device information can include, for instance, device status information including a connection status of a POS device and/or a function status of a POS device. The device information can also include device state information, including a driver version of a POS device, a firmware version of a POS device, and/or an OS version of a POS device.

[0064] At 436, the method 432 includes transmitting, by the computing device in response to the UPOS call failing to initialize communication with the POS device, a direct access call to the POS device to retrieve the device information from the POS device. For example, in an event in which the UPOS call fails to initialize communication with the POS device, the computing device can transmit a direct access call to retrieve the device information from the POS device.

[0065] At 438, the method 432 includes comparing, by the computing device, the device information to device reference information included in a database. For example, the computing device can compare a driver version, a firmware version, and/or an OS version of a POS device to device reference information included in the database.

[0066] At 440, the method 432 can include causing, by the computing device, the device information to be updated in response to a failure to match the device information associated with the POS device with the device reference information included in the database. For example, the computing device can determine that a driver version, a firmware version, and/or an OS version of a POS device does not match a driver version, a firmware version, and/or an OS version included in the database and, in response, can cause the driver version, firmware version, and/or the OS version of the POS device to be updated. [0067] At 442, the method 432 can include updating, by the database, the device reference information in response to an updated version of the device reference information being released. In some examples, the database can compare a driver version, a firmware version, and/or an OS version included in the database to driver version, a firmware version, and/or an OS version included in a remote database and in response to a failure to match the driver version, the firmware version, and/or the OS version in the database with the driver version, the firmware version, and/or the OS version in the remote database, update the driver version, the firmware version, and/or the OS version in the database. In some examples, the database can receive an input indicating that an updated version of a driver version, a firmware version, and/or an OS version has been released and in response, update the driver version, the firmware version, and/or the OS version. While the database is described above as being updated after the computing device causes the device information of the POS device to be updated, examples are not so limited. For example, the database may be updated at any time in order to keep the device reference information up to date for comparison by the computing device. [0068] In the foregoing detailed description, reference is made to the accompanying drawings that form a part hereof, and in which is shown by way of illustration how examples may be practiced. These examples are described in sufficient detail to enable those of ordinary skill in the art to practice the examples described herein, and it is to be understood that other examples may be utilized and that process, electrical, and/or structural changes may be made without departing from the scope of the specification. Further, as used herein, “a” can refer to one such thing or more than one such thing.

[0069] The figures herein follow a numbering convention in which the first digit corresponds to the drawing figure number and the remaining digits identify an element or component in the drawing. For example, reference numeral 102 may refer to element 102 in Figure 1 and an analogous element may be identified by reference numeral 202 in Figure 2. Additionally, the designator “N”, as used herein, particularly with respect to reference numerals in the drawings, indicates that an amount of the particular feature so designated can be included with an amount of examples described herein. Elements shown in the various figures herein can be added, exchanged, and/or eliminated to provide additional examples. In addition, the proportion and the relative scale of the elements provided in the figures are intended to illustrate the examples described herein and should not be taken in a limiting sense.

[0070] It can be understood that when an element is referred to as being "on," "connected to", “coupled to”, or "coupled with" another element, it can be directly on, connected, or coupled with the other element or intervening elements may be present. In contrast, when an object is “directly coupled to” or “directly coupled with" another element it is understood that are no intervening elements (adhesives, screws, other elements) etc.

[0071] The above specification, examples and data provide a description of the method and applications and use of the system and method. Since many examples can be made without departing from the spirit and scope of the system and method, this specification merely sets forth some of the many possible example configurations and implementations.

Claims

What is claimed is:

1. A computing device, comprising: a processor resource; and a non-transitory memory resource storing machine-readable instructions to cause the processor resource to: transmit a Unified Point of Service (UPOS) call to a point of sale (POS) device to retrieve device information from the POS device; compare the device information to device reference information included in a database; and cause the device information to be updated in response to a failure to match the device information with the device reference information included in the database.

2. The computing device of claim 1 , wherein retrieving the device information via the transmitted UPOS call includes instructions to cause the processor resource to transmit an initialization call to the POS device.

3. The computing device of claim 2, including instructions to cause the processor resource to transmit, in response to the initialization call initializing communication with the POS device, a retrieve call to the POS device to retrieve the device information from the POS device.

4. The computing device of claim 2, including instructions to cause the processor resource to transmit, in response to the initialization call failing to initialize communication with the POS device, another initialization call to the POS device after a predetermined amount of time.

5. The computing device of claim 2, including instructions to cause the processor resource to transmit, in response to the initialization call failing to initialize communication with the POS device, a direct access call to the POS device to retrieve the device information from the POS device.

6. The computing device of claim 1 , wherein the device information includes device status information including: a connection status of the POS device; or a function status of the POS device.

7. The computing device of claim 1 , wherein the device information includes device state information including: a driver version of the POS device; a firmware version of the POS device; or an operating system (OS) version of the POS device.

8. A non-transitory machine-readable medium including instructions that when executed cause a processor resource to: transmit a Unified Point of Service (UPOS) call to a point of sale (POS) device to retrieve device information from the POS device; transmit, in response to the UPOS call failing to initialize communication with the POS device, a direct access call to the POS device to retrieve the device information from the POS device; compare the device information to device reference information included in a database; and cause the device information to be updated in response to a failure to match the device information associated with the POS device with the device reference information included in the database.

9. The medium of claim 8, wherein transmitting the direct access call includes instructions to cause the processor resource to transmit a first call to the POS device to cause the POS device to cease communication with another device.

10. The medium of claim 9, including instructions to cause the processor resource to transmit in response to the POS device ceasing communication, a second call to the POS device to retrieve the device information from the POS device.

11. The medium of claim 10, including instructions to cause the processor resource to transmit, in response to the device information being retrieved from the POS device, a third call to the POS device to cause the POS device to re-initialize communication with the another device.

12. A method, comprising: transmitting, by a computing device, a Unified Point of Service (UPOS) call to a point of sale (POS) device to retrieve device information from the POS device; transmitting, by the computing device in response to the UPOS call failing to initialize communication with the POS device, a direct access call to the POS device to retrieve the device information from the POS device; comparing, by the computing device, the device information to device reference information included in a database; causing, by the computing device, the device information to be updated in response to a failure to match the device information associated with the POS device with the device reference information included in the database, wherein updating the device information includes updating: a firmware of the POS device; a driver of the POS device; or an operating system (OS) of the POS device; and updating, by the database, the device reference information in response to an updated version of the device reference information being released.

13. The method of claim 12, wherein: updating the device reference information includes comparing, by the database, a version of the device reference information included in the database to the updated version of device reference information included in a remote database at a predetermined time interval; and the method includes updating, by the database in response to a failure to match the version of the device reference information included in the database with the updated version of the device reference information included in the remote database, the version of the device reference information to correspond to the version of the updated device reference information.

14. The method of claim 12, wherein updating the device reference information includes: receiving, by the database, an input indicating that the updated version of the device reference information has been released; and updating, by the database, the device reference information in the database to correspond to the updated device reference information included in the remote database in response to the input.

15. The method of claim 12, wherein the method further includes: retrieving, by the computing device, the updated device information from the

POS device; comparing, by the computing device, the updated device reference information to the updated device reference information included in the database; and causing, by the computing device, the updated device information to be updated in response to a failure to match the updated device reference information associated with the POS device with the updated device reference information included in the database.