Conducting a transaction at a mobile POS terminal using a defined structure
First Claim
1. A system for conducting a mobile device transaction, the system comprising:
- a mobile device including;
a first client application installed on the mobile device, the first client application operating using a first application-specific data structure particular to the first client application, wherein the first application-specific data structure buffers the first client application from software or format changes of an accessory device;
a second client application installed on the mobile device, the second client application operating using second application-specific data structure particular to the second client application, wherein the second application-specific data structure buffers the second client application from software or format changes of the accessory device and wherein the second application-specific data structure is different from the first application-specific data structure; and
a mobile device software development kit (SDK) providing communications between the accessory device and the first client application using a first client application conversion module and/or between the accessory device and the second client application using a second client application conversion module;
wherein the mobile device SDK detects the accessory device, monitors the accessory device for an accessory device event, and receives, from the accessory device module, transaction data in an accessory device format upon an occurrence of an accessory device event,wherein the first client application conversion module converts the transaction data into the first application-specific data structure and the mobile device SDK provides the transaction data in the first application-specific data structure to the first client application; and
wherein the second client application conversion module converts the transaction data into the second application-specific data structure and the mobile device SDK provides the transaction data in the second application-specific data structure to the second client application, wherein the second client conversion module is separate and different from the first client application conversion module.
5 Assignments
0 Petitions
Accused Products
Abstract
A system and method configured for conducting a transaction between two parties using a mobile device, or a plurality of mobile devices. In various embodiments, a system for conducting a transaction can comprise an accessory device having an accessory device module and a hardware component, where the accessory device can have various accessory device capabilities. The system can further comprise a mobile device SDK incorporated into the client application and in communication with the accessory device, where the mobile device SDK includes an accessory conversion module in communication with the accessory device module and where the mobile device SDK provides data to the client application. The client application can request accessory device information and receive accessory device capabilities, and the transaction data for the transaction can be provided in a defined structure between the accessory device and the client application via the mobile device SDK.
-
Citations
19 Claims
-
1. A system for conducting a mobile device transaction, the system comprising:
a mobile device including; a first client application installed on the mobile device, the first client application operating using a first application-specific data structure particular to the first client application, wherein the first application-specific data structure buffers the first client application from software or format changes of an accessory device; a second client application installed on the mobile device, the second client application operating using second application-specific data structure particular to the second client application, wherein the second application-specific data structure buffers the second client application from software or format changes of the accessory device and wherein the second application-specific data structure is different from the first application-specific data structure; and a mobile device software development kit (SDK) providing communications between the accessory device and the first client application using a first client application conversion module and/or between the accessory device and the second client application using a second client application conversion module; wherein the mobile device SDK detects the accessory device, monitors the accessory device for an accessory device event, and receives, from the accessory device module, transaction data in an accessory device format upon an occurrence of an accessory device event, wherein the first client application conversion module converts the transaction data into the first application-specific data structure and the mobile device SDK provides the transaction data in the first application-specific data structure to the first client application; and wherein the second client application conversion module converts the transaction data into the second application-specific data structure and the mobile device SDK provides the transaction data in the second application-specific data structure to the second client application, wherein the second client conversion module is separate and different from the first client application conversion module. - View Dependent Claims (16)
-
2. A tangible non-transitory computer-readable medium having a mobile device software development kit (SDK) incorporated into a first client application and a second client application installed on a mobile device, the mobile device SDK comprising:
-
a first client application conversion module and a second client application conversion module communicating with an accessory device module of an accessory device, whereby the first client application conversion module provides communications between the first client application and the accessory device, and the second client application module provides communications between the second client application and the accessory device, wherein the second client conversion module is separate and different from the first client application conversion module; and wherein the mobile device SDK detects the accessory device, monitors the accessory device for an accessory device event, and receives, from the accessory device module, transaction data for a transaction in an accessory device format upon an occurrence of an accessory device event, wherein the first client application conversion module converts the transaction data into a first application-specific data structure, wherein the first application-specific data structure buffers the first client application from software or format changes of the accessory device, and the mobile device SDK provides the transaction data in the first application-specific data structure to the first client application; and wherein the second client application module converts the transaction data into a second application-specific data structure different from the first application-specific data structure, wherein the second application-specific data structure buffers the second client application from software or format changes of the accessory device, and the mobile device SDK provides the transaction data in the second application-specific data structure to the second client application. - View Dependent Claims (3, 17)
-
-
4. A computer-implemented method, performed by a mobile device, for conducting a transaction, the method comprising:
-
receiving, by the mobile device, a request for accessory device information from a first client application installed on the mobile device, wherein the mobile device includes a mobile device software development kit (SDK) configured to receive the request for accessory device information, wherein the mobile device SDK comprises a first client application conversion module providing communications between a first client application and a first accessory device, and a second client application conversion module providing communications between a second client application and the first accessory device, retrieving, by the mobile device, transaction data in a first accessory device-specific format from the first accessory device; using the first client application conversion module to convert the transaction data from the first accessory device-specific format to a first application-specific data structure, wherein the first application-specific data structure buffers the first client application from software or format changes of the first accessory device, and providing, by the mobile device, the transaction data in the first application-specific data structure to the first client application; and using the second client application conversion module to convert the transaction data from the accessory device format to a second application-specific data structure different from the first application-specific data structure, wherein the second application-specific data structure buffers the second client application from software or format changes of the first accessory device, and providing, by the mobile device, the transaction data in the second application-specific data structure to the second client application, wherein the second client conversion module is separate and different from the first client application conversion module. - View Dependent Claims (5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 18)
-
-
15. A non-transitory, tangible computer-readable storage medium having computer-executable instructions stored thereon that, if executed by a client application incorporating a mobile device software development kit (SDK) for conducting a transaction, cause the mobile device SDK to perform operations comprising:
-
determining, by the mobile device SDK, a plurality of application-specific data structures; receiving, by the mobile device SDK, a request for accessory device information from a first client application; determining, of the plurality of application-specific data structures, a first application-specific data structure corresponding to the first client application; receiving, by the mobile device SDK, transaction data in an accessory device format from the accessory device; converting the transaction data from the accessory device format to the first application-specific data structure, wherein the first application-specific data structure buffers the first client application from software or format changes of the accessory device and providing, by the mobile device SDK, the transaction data in the first application-specific data structure to the first client application installed on a mobile device; determining, of the plurality of application-specific data structures, a second application-specific data structure corresponding to the second client application installed on the mobile device, wherein the first application-specific data structure buffers the first client application from software or format changes of an accessory device and the second application-specific data structure is different from the first application-specific data structure; converting the transaction data from the accessory device format to the second application-specific data structure; and providing, by the mobile device SDK, the transaction data in the second application-specific data structure to the second client application. - View Dependent Claims (19)
-
Specification