Application independent DEX/UCS interface

• US 9,978,088 B2
• Filed: 05/08/2015
• Issued: 05/22/2018
• Est. Priority Date: 05/08/2015
• Status: Active Grant

• Current Assignee: Hand Held Products Incorporated (Honeywell International Inc.)
• Original Assignee: Hand Held Products Incorporated (Honeywell International Inc.)
• Inventors: Pape, Philip P.
• Primary Examiner(s): Goyea, Olusegun
• Application Number:
  US14/707,123
• Publication Number:
  US 20160328762A1
• Time in Patent Office: 1,110 Days
• Field of Search: 358 115, 358400, 709217, 709203, 709224, 709230, 709219, 709204, 705 13, 705 28, 705 30, 705 39, 705 64
• CPC Class Codes: G06F 15/00 Digital computers in general details G06F1/00 – G06F13/00; Data processing equipment in general
• CPC Class Codes: G06F 15/16 Combinations of two or more digital computers each having at least an arithmetic unit, a program unit and a register, e.g. for a simultaneous processing of several programs coordinating program control therefor G06F9/52; in regulating and control system G05B
• CPC Class Codes: G06Q 10/08 Logistics, e.g. warehousing, loading or distribution; Inventory or stock management
• CPC Class Codes: G06Q 10/087 Inventory or stock management, e.g. order filling, procurement or balancing against orders
• CPC Class Codes: G06Q 20/00 Payment architectures, schemes or protocols apparatus for performing or posting payment transactions G07F7/08, G07F19/00; electronic cash registers G07G1/12
• CPC Class Codes: G06Q 20/20 Point-of-sale [POS] network systems
• CPC Class Codes: G06Q 20/40 Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
• CPC Class Codes: G06Q 30/04 Billing or invoicing

Abstract

Systems, methods, and devices are described for an application independent DEX/UCS interface (AIDI). The AIDI is a “plug and play” DEX/UCS solution that removes the requirement for developers to know the structure, function, and format of DEX/UCS transaction sets and to make the DEX/UCS process independent from the existing business logic of many mobile applications.

Claims

1. A device, comprising:

at least one communication interface;

at least one storage repository;

a control system communicatively coupled to the at least one communication interface and the at least one storage repository and comprising at least one hardware processor and a memory storing at least one first program code, and at least one second program code, wherein;

the at least one first program code is operable to;

receive transaction information;

create a first data file in the storage repository, wherein the first data file is based on the transaction information;

send a message to the at least one second program code to initiate a creation of one or more Direct Exchange/Uniform Communication Standard (DEX/UCS) transactions from the transaction information, the DEX/UCS transactions being in an exchange format comprising a DEX/UCS format;

receive a message from the at least one second program code denoting success or failure of the creation of the one or more DEX/UCS transactions from the transaction information in the exchange format; and

the at least one second program code is operable to;

receive a message from the at least one first program code to initiate a creation of the one or more DEX/UCS transactions from the transaction information in the exchange format;

read the transaction information from the first data file;

create the one or more DEX/UCS transactions from the transaction information in the exchange format; and

send a message to the at least one first program code denoting success or failure of the creation of the one or more DEX/UCS transactions from the transaction information in the exchange format.

2. The device of claim 1, wherein the transaction information is selected from the group consisting of:

sales information, return information, adjustment information, and counter-adjustment information.

3. The device of claim 1, wherein the message is of a type selected from the group consisting of:

a signal, an inter-process communication, and a notification.

4. The device of claim 1, wherein the exchange format is administered by GS1.

5. The device of claim 1, wherein:

the at least one first program code is further operable to;

issue a prompt for a connection to a second device;

send a signal to the second program code to initiate a communication of the one or more DEX/UCS transactions from the transaction information in the exchange format;

receive a message from the at least one second program code denoting success or failure of the communication of the one or more DEX/UCS transactions in the exchange format; and

the at least one second program code is further operable to;

receive a message from the at least one first program code to initiate the communication of the one or more DEX/UCS transactions in the exchange format;

exchange the one or more DEX/UCS transactions with the second device; and

send a message to the at least one first program code denoting success or failure of the communication of the one or more DEX/UCS transactions to the second device.

6. The device of claim 5, wherein the communication is of a type selected from the group of:

a sending communication and a receiving communication.

7. The device of claim 5, wherein:

the at least one first program code is further operable to;

receive a message from the at least second program code including information about a second data file comprising adjustments to the transaction information, the adjustments pertaining to one or more acknowledged transactions;

read the second data file;

update the transaction information corresponding to the one or more acknowledged transactions;

display the transaction information corresponding to transactions that require reconciliation;

determine if there is additional transaction information;

if there is additional transaction information, receive the additional transaction information and create a third data file in the storage repository, wherein the third data file is based on the additional transaction information; and

the at least one second program code is further operable to;

analyze the transaction information exchanged with the second device;

create the second data file in the storage repository, wherein the second data file is based on analyzed transaction information; and

send a message to the at least one first program code including information about the second data file.

8. The device of claim 7, wherein the additional transaction information is selected from the group consisting of:

sales information, return information, adjustment information, and counter-adjustment information.

9. The device of claim 7, wherein the third data file and the first data file are the same file.

10. The device of claim 7, wherein the information about the second data file includes the location of the file in the storage repository.

21. The device of claim 1, wherein the second program code corresponds to an application independent DEX/UCS interface (AIDI).

22. The device of claim 1, wherein the first program code corresponds to a mobile business application (MBA).

11. A system, comprising:

a first device comprising;

at least one communication interface;

at least one storage repository;

a control system communicatively coupled to the at least one communication interface and the at least one storage repository and comprising at least one hardware processor and a memory storing program codes operable to;

receive transaction information;

create a first data file in the storage repository, wherein the first data file is based on the transaction information;

send a message to the at least one second program code to initiate a creation of one or more Direct Exchange/Uniform Communication Standard (DEX/UCS) transactions from the transaction information in an exchange format;

receive a message from the at least one second program code denoting success or failure of the creation of the one or more DEX/UCS transactions from the transaction information in the exchange format; and

a second device comprising;

at least one communication interface;

at least one storage repository;

a control system communicatively coupled to the at least one communication interface and the at least one storage repository and comprising at least one hardware processor and a memory storing program codes operable to;

receive a message from the at least one first program code to initiate a creation of the one or more DEX/UCS transactions in the exchange format;

read the transaction information from the first data file;

create the one or more DEX/UCS transactions in the exchange format; and

send a message to the at least one first program code denoting success or failure of the creation of the one or more DEX/UCS transactions in the exchange format.

12. The system of claim 11, wherein the transaction information is selected from the group consisting of:

sales information, return information, adjustment information, and counter-adjustment information.

13. The system of claim 11, wherein the message is of a type selected from the group consisting of:

a signal, an inter-process communication, and a notification.

14. The system of claim 11, wherein the exchange format is administered by GS1.

15. The system of claim 11, wherein:

the control system of the first device is further operable to;

issue a prompt for a connection to a third device;

send a signal to the second program code to initiate a communication of the one or more DEX/UCS transactions from the transaction information in an exchange format;

receive a message from the at least one second program code denoting success or failure of the communication of the one or more DEX/UCS transactions in the exchange format; and

the control system of the second device is further operable to;

receive a message from the at least one first program code to initiate the communication of the one or more DEX/UCS transactions in the exchange format;

exchange the one or more DEX/UCS transactions with the third device; and

send a message to the at least one first program code denoting success or failure of the communication of the one or more DEX/UCS transactions to the third device.

16. The system of claim 15, wherein the communication is of a type selected from the group of:

a sending communication and a receiving communication.

17. The system of claim 15, wherein:

the control system of the first device is further operable to;

receive a message from the at least second program code including information about a second data file comprising adjustments to the transaction information, the adjustments pertaining to one or more acknowledged transactions;

read the second data file;

update the transaction information corresponding to the one or more acknowledged transactions;

display the transaction information corresponding to transactions that require reconciliation;

determine if there is additional transaction information;

if there is additional transaction information, receive the additional transaction information and create a third data file in the storage repository, wherein the third data file is based on the additional transaction information; and

the control system of the second device is further operable to;

analyze the transaction information exchanged with the third device;

create the second data file in the storage repository, wherein the second data file is based on analyzed transaction information; and

send a message to the at least one first program code including information about the second data file.

18. The system of claim 17, wherein the additional transaction information is selected from the group consisting of:

sales information, return information, adjustment information, and counter-adjustment information.

19. The system of claim 17, wherein the third data file and the first data file are the same file.

20. The system of claim 17, wherein the information about the second data file includes the location of the file in the storage repository.