The present application claims the benefit of U.S. patent application Ser. No. 14/744,836 for a Cloud-Based System for Reading of Decodable Indicia filed Jun. 19, 2015 (and published Oct. 8, 2015 as U.S. Patent Publication No. 2015/0288689), now U.S. Pat. No. 9,398,008, which claims the benefit of U.S. patent application Ser. No. 13/474,014 for a Cloud-Based System for Reading of Decodable Indicia filed May 17, 2012 (and published Nov. 21, 2013 as U.S. Patent Application Publication No. 2013/0306720), now U.S. Pat. No. 9,064,254. Each of the foregoing patent applications, patent publications, and patents is hereby incorporated by reference in its entirety.
The invention is generally related to systems for the reading of decodable indicia and is specifically related to cloud-based systems for the reading of decodable indicia.
Decodable indicia are patterns, marks, or messages which are designed to be scanned and interpreted by computer and/or other mechanical and/or automated methods. Many known types of decodable indicia fall under the category of barcodes. Barcodes are graphical representations of data, the most common of which are referred to as one dimensional (1D) and two dimensional (2D) barcodes. 1D barcodes are graphical entities that represent data by varying the widths and spacing of parallel lines. 2D barcodes are also graphical entities that represent data, but in addition to the parallel lines, or bars, a 2D barcode may contain rectangles, dots, hexagons and other geometric patterns in two dimensions. The data encoded in the barcodes are interpreted by optical scanners and/or software. Barcodes can be scanned by special optical scanners called barcode readers as well as by general purpose devices such as smart phones. Other types of decodable indicia include optical character recognition (OCR), glyphs, or other visual markings. Also, non-visual technologies such as magnetic strips, radio-frequency identification (RFID), and other non-visual technologies fall under the definition of decodable indicia as well.
In one embodiment, there is provided a data decoding system comprising one or more computers communicatively coupled to a network. The computers can execute at least one client authentication process and at least one decoding process. The authentication process can be configured to authenticate a client. The decoding process can be configured, responsive to receiving from the client a decoding request comprising an image of decodable indicia, to locate the decodable indicia within the image, and to decode the decodable indicia into a decoded message. The decoding process can be further configured, responsive to completing the decoding operation, to transmit to the client the decoded message and/or the decoding operation completion code.
In some embodiments, the authentication process and the decoding process can be executed by the same computer. Alternatively, the authentication process and the decoding process can be executed by different computers.
In some embodiments, the client authentication process can be configured, responsive to receiving an authentication request comprising a client certificate, to negotiate a common secret with the client. The authentication process can be further configured to create at least one cryptographic key based on the common secret, and to use the cryptographic key to encrypt messages transmitted to the client and/or decrypt messages received from the client.
In a further aspect, the computers can be further configured, responsive to receiving an authentication request comprising a client certificate, to validate the client certificate by transmitting a validation request to a certificate authority issuing the client certificate.
In another embodiment, there is provided a data decoding system comprising one or more computers communicatively coupled to a network. The computers can execute at least one decoding process and at least one logging process. The decoding process can be configured, responsive to receiving a decoding request comprising an image of decodable indicia, to locate the decodable indicia within the image, and to decode the decodable indicia into a decoded message. The decoding process can be further configured, responsive to completing the decoding operation, to transmit to the client the decoded message and/or the decoding operation completion code. The decoding process can be further configured, responsive to completing the decoding operation, to transmit a logging request to the logging process. The logging process can be configured, responsive to receiving the logging request, to create a usage tracking record in a usage tracking database. The usage tracking record can comprise a client identifier, the image, the decoded message, and/or the decoding operation completion code.
In some embodiments, the logging process and the decoding process can be executed by the same computer. Alternatively, the logging process and the decoding process can be executed by different computers.
In a further aspect, the decoding request and/or the usage tracking record can further comprise one or more values of client configuration parameters.
In yet another embodiment, there is provided a data decoding system comprising one or more computers communicatively coupled to a network. The computers can execute at least one decoding process. The decoding process can be configured, responsive to receiving from a client a decoding request comprising an image of decodable indicia, to locate the decodable indicia within the image. The decoding process can be further configured, responsive to successfully locating the decodable indicia, to decode the decodable indicia into a decoded message. The decoding process can be further configured, responsive to completing a decoding operation, to transmit to the client at least one of: the decoded message, a decoding operation completion code. The computers can be further configured to validate an entitlement of the client to receive decoding services responsive to receiving the decoding request and/or transmit a billing request to a billing system responsive to completing the decoding operation.
In a further aspect, the billing request can comprise the client identifier, the symbology type, and/or the number of decodable indicia items to be decoded.
In a further aspect, the computers can be configured to validate the entitlement of the client by transmitting a client entitlement validation request to the billing system. The client entitlement validation request can comprise a client identifier, the symbology type, and/or the number of decodable indicia items to be decoded.
In a further aspect, the decoding process can be configured to transmit the decoded message to the client responsive to receiving a billing transaction confirmation from the billing system.
For the purpose of illustrating the invention, the drawings show aspects of one or more embodiments of the invention. However, it should be understood that the present invention is not limited to the precise arrangements and instrumentalities shown in the drawings, wherein:
The drawings are not necessarily to scale, emphasis instead generally being placed upon illustrating the principles of the invention. In the drawings, like numerals are used to indicate like parts throughout the various views.
Capture of decodable indicia can utilize many types of technologies. Laser scanning or linear imaging can be used for the capture of 1D barcodes. Some 2D barcodes known as stacked codes, such as PDF417, can be read using these technologies as well, however 2D bar codes known as matrix codes require devices which can capture a 2 dimensional (2D) image of the bar code. These 2D images are also useful for decoding 1D, 2D stacked codes, as well as OCR or other visual decodable indicia. For things like RFID, magnetic strips or other non-visual decodable indicia, these may involve use of RF, magnetic reading heads, or other non-visual means of capture. For the purposes of this invention, the capture of any decodable indicia will be referred to generally as “imaging”, and the captured representation of the decodable indicia by a device will be referred to as an “image”.
A growing variety of devices are currently being used for bar code reading and decoding, ranging from specialized scanners to smart phones. Supporting multiple hardware and software platforms can become challenging for suppliers of decoding software. One solution to supporting a large number of bar code reading devices representing a variety of platforms is to split the imaging and decoding functions: an image comprising decodable indicia can be taken by a portable or stationary scanner, e.g., by a point-of-sale (POS) device, and can then be transmitted to an external server for decoding. Since the decoding client can be completely agnostic with respect to decoding algorithms employed by the server, the problem of supporting a large variety of client platforms can be solved by creating thin client imaging applications. A typical thin client imaging application only needs to be able to transfer an image of decodable indicia to a decoding server over a network, and then receive decoded message data from the server. As used herein, “message” is intended to denote a character string comprising alphanumeric and/or non-alphanumeric characters. An encoded message can be used to convey information, such as identification of the source and the model of a product, for example, in a UPC code.
In one embodiment, there is provided an optical indicia decoding system comprising-one or more computers communicatively coupled to a network and executing one or more decoding processes. A “computer” herein shall refer to a programmable device for data processing, including a central processing unit (CPU), a memory, and at least one communication interface. For example, in one embodiment, a computer can be provided by an Intel-based server running Linux operating system. In another embodiment, a computer can be provided by a virtual server, i.e., an isolated instance of a guest operating system running within a host operating system. A “network” herein shall refer to a set of hardware and software components implementing a plurality of communication channels between two or more computers. A network can be provided, e.g., by a local area network (LAN), or a wide area network (WAN). While different networks can be designated herein, it is recognized that a single network as seen from the network layer of the OSI model can comprise a plurality of lower layer networks. A “process” herein shall refer to an instance of a computer program that is being executed; in some operating systems, several processes can be instantiated simultaneously from the same computer program.
The decoding process can be configured, responsive to receiving from a decoding client a decoding request including a decodable indicia image, to locate the decodable indicia within the image, and then, responsive to successfully locating the decodable indicia, to decode the decodable indicia into a decoded message, and to transmit the decoded message back to the decoding client.
In one embodiment, schematically shown in
Wireless access point 140 could be configured to support Bluetooth, Near Field Communication (NFC) ISO/IEC 18092 and/or ISO/IEC 14443, the IEEE 802.11/802.15/802.16 protocol family, or other wireless technology. Cellular base station 145 could be configured to include HSPA/GSM/GPRS/EDGE protocol family, TDMA protocol, UMTS protocol, LTE protocol, the CDMA/1×EV-DO protocol family, and/or other cellular technology.
In one embodiment, the decoding system 1000 can follow a cloud computing model, by providing an on-demand network access to a shared pool of configurable computing resources (e.g., servers, storage, applications, and/or services) that can be rapidly provisioned and released with minimal or no resource management effort, including interaction with the service provider, by the consumer (operator of a thin client). One characteristic of the cloud computing model is that a consumer can unilaterally provision computing capabilities, such as CPU power and storage capacity on the network, as needed automatically without requiring human interaction with the service's provider. The resources of the cloud can be accessed by thin clients over a network.
In another aspect, decoding clients can access cloud-based decoding applications executed by computers 120a-120z via a single point of entry, e.g., via a single IP address or uniform resource identifier (URI). In one embodiment, the single point of entry IP address can be assigned to a load balancing component provided, e.g., by router 130a or by a dedicated load balancer 122. In another embodiment, the single point of entry URI can include a fully-qualified host name resolvable by a DNS server into one or more IP addresses of computers 120a-120z. In a yet another embodiment, the single point of entry URI can include a fully-qualified host name resolvable by a DNS server into an IP address of the dedicated load balancer 122 which can act as a server-side HTTP proxy by forwarding HTTP requests from the decoding clients 101a-101c to HTTP processes running on the decoding computers 120a-120z. The server-side HTTP proxy can preserve HTTP or application-level sessions by forwarding all TCP packets from one client to the same server. Thus, a decoding client accessing the cloud-based decoding applications can be agnostic with respect to the number of computers 120a-120z, topology of the local area networks 110a-110z, aspects of load balancing among the computers 120a-120z and other server-side implementation details.
For preventing unauthorized access to the cloud-based decoding services, decoding system 1000 can require a decoding client to be authenticated before processing any decoding requests. In one embodiment, the client authentication can be performed utilizing digital certificates. A digital certificate can be issued to a decoding client 101a-101c by a certificate authority controlled by a trusted third party or the decoding service provider. A digital certificate can be digitally signed by the issuing certificate authority and can comprise an identifier and a public encryption key of the certificate holder. The certificate authority can also provide a private encryption key to the certificate holder. The public/private key pair can be used to encrypt and decrypt messages so that a message encrypted by a public key can only be decrypted using the matching private key.
One embodiment of a method of authenticating a client by a cloud-based computer is now being described with references to
The authentication process 125 can then negotiate a common secret with the client 101. To prevent eavesdropping by a malicious third party, the authentication process 125 can encrypt the messages addressed to the client 101 using the client's public key, so that the messages could only be decrypted using the client's private key. Thus, a common secret can be negotiated by the client 101 and the authentication process 125 over a secure communication channel. The common secret can then be used by each of the client 101 and the authentication process 125 to derive a symmetric encryption key (e.g., by calculating a hash function of the common secret) used to encrypt and decrypt the subsequent communications.
In another embodiment, the authentication process 125 can perform a password-based authentication method. The operator of the decoding client device 101 can be prompted to enter a password via a user interface. The decoding client device 101 can transmit to the authentication process 125 a binary string derived from the password (e.g., a value of a pre-defined hash-function of the password string). The authentication process 125 can authenticate the client device 101 by calculating the hash function of the received binary string and comparing the value with a value stored in a permanent memory accessible by the authentication process 125 (e.g., a LDAP server).
In a further aspect, upon successfully authenticating the client device 101, the authentication process 125 can encrypt the messages addressed to the decoding client 101 using an encryption key derived from a common secret, e.g., by calculating a hash function of the common secret. In one embodiment, the common secret can be communicated to the decoding client 101 using an alternative communication channel (e.g., via an external memory device such as a USB memory stick, via a user interface, etc.).
In a yet another embodiment, the authentication process 125 can authenticate the decoding client 101 based on a network address (e.g., an IP address) of the decoding client. This embodiment can be particularly useful when one or more decoding clients are connecting to an enterprise network—with a known IP address range, and/or via a client-side proxy with a known IP address of the external (Internet-side) interface.
In a yet another embodiment, the authentication process 125 can authenticate the decoding client 101 based on biometric data (e.g., a fingerprint of the operator of the decoding client 101).
A skilled artisan would appreciate the fact that other authentication methods are within the scope of the invention.
With reference back to
In a further aspect, the authentication process can act as a transparent server-side proxy to at least one decoding process: upon authenticating a decoding client, the authentication process can receive one or more of decoding requests from the authenticated decoding client, and forward the decoding requests to the decoding process.
In a further aspect, a decoding process can, responsive to completing a decoding operation, transmit the decoding operation result including decoded message data and/or the decoding operation completion code to the decoding client. In one embodiment, the decoding process can transmit the decoding operation result to the authentication process, which then can forward the decoding operation result to the client that transmitted the decoding request.
In one embodiment, one or more of the cloud-based computers 120a-120z can execute at least one logging process configured to log decoding requests and results in a usage tracking database, by creating a usage tracking record comprising a client identifier, a decodable indicia image, a decoded message and/or a decoding operation completion code. In one embodiment, the decoding process can be configured, responsive to completing a decoding operation, to transmit a logging request to the logging process. The logging process can be configured, responsive to receiving a logging request from a decoding process, to create a usage tracking record in the usage tracking database. In one embodiment, the usage tracking database can be provided by a relational database. In another embodiment, the usage tracking database can be provided by a flat file.
In one embodiment, one or more logging processes can be executed by one or more dedicated computers 120a-120m, and one or more decoding processes can be executed by one or more dedicated computers 120n-120z. In another embodiment, at least one of computers 120a-120z can be configured to execute at least one decoding process and at least one logging process.
In a further aspect, a decoding request transmitted by the decoding client can comprise one or more client configuration parameters, for example, client device model, client device serial number, aperture value, shutter speed, and ISO value. In one embodiment, the decoding process can include one or more client configuration parameters into the usage tracking record.
One embodiment of a structure of the usage tracking database table is schematically shown in
In another aspect, the decoding system 1000 can support a variety of billing models, including usage-based model (“pay per scan”), unlimited usage model, and numerous hybrid models. In one embodiment, a decoding process can be configured, responsive to receiving a decoding request, to validate the client entitlement to receive decoding services. In one embodiment shown in
In one embodiment, schematically shown in
The billing system 400 can verify the entitlement of the client to receive the requested service and can return the validation result to the decoding process 127. Responsive to receiving a negative entitlement confirmation, the decoding process 127 can return a corresponding error code to the decoding client.
In a further aspect, responsive to completing a decoding operation, the decoding process 127 can transmit a billing request to the billing system. The billing request can include the client identifier and the type of performed service. For example, the billing request can include a processor elapsed time. In another example, the billing request can include number of decoding attempts. In a yet another example, the billing request can include the size of the image processed. In a yet another example, the billing request can include the type and/or the number of decoded decodable indicia.
In some embodiments, the entitlement request and the billing request can be combined into a single request.
In a further aspect, billing system 400 can support a variety of billing models, including usage-based model (“pay per scan”), unlimited usage model, and numerous hybrid models.
In a pay-per-scan model, billing system 400 can process a billing request by initiating a payment transaction. Alternatively, billing system 400 can process a billing request by appending a billing item to an invoice to be forwarded to the appropriate customer.
In some embodiment, responsive to successfully processing the billing request, billing system 400 can transmit a billing confirmation to decoding process 127. In some embodiment, transmitting decoding operation completion code and/or decoding message to the requesting client 101 by decoding process 127 can only be performed upon receiving the billing confirmation from the billing system.
In another aspect, the image of decodable indicia can be provided by a raw image byte stream or a compressed image byte stream (e.g., GIFF, TIFF, JPEG or other standard or proprietary format).
In another aspect, the decoding client can be provided by a large variety of imaging devices. In one embodiment, the decoding client can be provided by a mobile computing device (e.g., a mobile communication terminal, or a smartphone) comprising an integrated imaging device or a peripheral imaging device. An integrated imaging device can be provided, e.g., by a two-dimensional imager incorporated into the housing of the mobile computing device and communicatively coupled to other components of the mobile computing device, including, e.g., a data bus, a processor, or a communication interface. A peripheral imaging device can be provided, e.g., by a still image or video camera disposed in a separate housing and communicatively coupled to the mobile computing device (e.g., via Bluetooth interface).
In another embodiment, the decoding client can be provided by a general purpose computing device (e.g., a notebook computer or a desktop computer) comprising an integrated imaging device or a peripheral imaging device.
In a yet another embodiment, the decoding client can be provided by a computing device integrated into a POS system (e.g., a retail cashier's workstation) comprising an integrated imaging device or a peripheral imaging device.
As noted herein supra, in one embodiment, the decoding client can be provided by a mobile communication terminal. One embodiment of a mobile communication terminal 100 is shown in
While
In another illustrative embodiment, shown in
Mobile communication terminals described herein supra can be used, for example, for bar code reading in POS and other applications. A skilled artisan would appreciate the fact that other uses of Mobile communication terminals are within the scope of this disclosure.
Component-level diagram of one embodiment of a mobile communication terminal is now being described with references to
Mobile communication terminal 100 can further comprise a communication interface 840 communicatively coupled to the system bus 870. In one embodiment, the communication interface can be provided by a wireless communication interface. The wireless communication interface can be configured to support, for example, but not limited to, the following protocols: at least one protocol of the IEEE 802.11/802.15/802.16 protocol family, at least one protocol of the HSPA/GSM/GPRS/EDGE protocol family, TDMA protocol, UMTS protocol, LTE protocol, and/or at least one protocol of the CDMA/1×EV-DO protocol family.
Mobile communication terminal 100 can further comprise a keyboard interface 854 and a display adapter 855, both also coupled to the system bus 870. Mobile communication terminal 100 can further comprise a battery 856. In one embodiment, the battery 856 can be provided by a replaceable rechargeable battery pack. Mobile communication terminal 100 can further comprise a GPS receiver 880. Mobile communication terminal 100 can further comprise at least one connector 890 configured to receive a subscriber identity module (SIM) card. Mobile communication terminal 100 can further comprise an imaging device 830, provided, for example, by a two-dimensional imager.
While the present invention has been particularly shown and described with reference to certain exemplary embodiments, it will be understood by one skilled in the art that various changes in detail may be affected therein without departing from the spirit and scope of the invention as defined by claims that can be supported by the written description and drawings. Further, where exemplary embodiments are described with reference to a certain number of elements it will be understood that the exemplary embodiments can be practiced utilizing less than the certain number of elements.
A small sample of systems, methods, and apparatuses that are described herein is as follows:
A1. A data decoding system comprising one or more computers communicatively coupled to a network, said one or more computers executing at least one client authentication process and at least one decoding process;
wherein said client authentication process is configured to authenticate a client;
wherein said at least one decoding process is configured, responsive to receiving a decoding request from said client, said decoding request comprising an image of decodable indicia, to locate said decodable indicia within said image;
wherein said at least one decoding process is further configured, responsive to successfully locating said decodable indicia, to decode said decodable indicia into a decoded message; and
wherein said at least one decoding process is further configured, responsive to completing a decoding operation, to transmit to said client at least one of: said decoded message, a decoding operation completion code.
A2. The data decoding system of (A1), wherein said at least one authentication process and said at least one decoding process are executed by one computer.
A3. The data decoding system of (A1), wherein said at least one authentication process is executed by a first computer; and
wherein said at least one decoding process is executed by a second computer.
A4. The data decoding system of (A1), wherein said image of decodable indicia is provided by one of: a raw image byte stream, a compressed image byte stream.
A5. The data decoding system of (A1), wherein said client is provided by a mobile communication terminal comprising an optical reading device configured to output said image of decodable indicia.
A6. The data decoding system of (A1), wherein said client is provided by a mobile computing device comprising one of: an integrated imaging device, a peripheral imaging device.
A7. The data decoding system of (A1), wherein said client is provided by a desktop computer comprising one of: an integrated imaging device, a peripheral imaging device.
A8. The data decoding system of (A1), wherein said client is provided by a computing device integrated into a point-of-sale system, said computing device comprising one of: an integrated imaging device, a peripheral imaging device.
A9. The data decoding system of (A1), wherein said at least one client authentication process is configured, responsive to receiving from a client an authentication request comprising a client certificate, to negotiate a common secret with said client;
wherein said at least one authentication process is further configured to create at least one cryptographic key based on said common secret; and
wherein said at least one authentication process is further configured to use said at least one cryptographic key to perform at least one of: encrypting one or more messages transmitted to said client; decrypting one or more messages received from said client.
A10. The data decoding system of (A9), wherein said at least one computer is further configured, responsive to receiving from a client an authentication request comprising a client certificate, to validate said client certificate by transmitting a validation request to a certificate authority issuing said client certificate.
B1. A data decoding system comprising one or more computers communicatively coupled to a network, said one or more computers executing at least one decoding process and at least one logging process;
wherein said at least one decoding process is configured, responsive to receiving a decoding request comprising an image of decodable indicia from a client, to locate said decodable indicia within said image;
wherein said at least one decoding process is further configured, responsive to successfully locating said decodable indicia, to decode said decodable indicia into a decoded message;
wherein said at least one decoding process is further configured, responsive to completing a decoding operation, to transmit to said client at least one of: said decoded message, a decoding operation completion code;
wherein said at least one decoding process is further configured, responsive to completing said decoding operation, to transmit a logging request to said at least one logging process; and
wherein said at least one logging process is configured, responsive to receiving said logging request from said at least on decoding process, to create a usage tracking record in a usage tracking database, said usage tracking record comprising a client identifier, said image, and at least one of: said decoded message, said decoding operation completion code.
B2. The data decoding system of (B1), wherein said at least one decoding process and said at least one logging process are executed by one computer.
B3. The data decoding system of (B1), wherein said at least one decoding process is executed by a first computer; and
wherein said at least one logging process is executed by a second computer.
B5. The data decoding system of (B1), wherein said decoding request further comprises one or more values of client configuration parameters; and
wherein said usage tracking record further comprises said one or more values of client configuration parameters.
B5. The data decoding system of (B1), wherein said image of decodable indicia is provided by one of: a raw image byte stream, a compressed image byte stream.
B6. The data decoding system of (B1), wherein said client is provided by a mobile communication terminal comprising an optical reading device configured to output said image of decodable indicia.
B7. The data decoding system of (B1), wherein said client is provided by a mobile computing device comprising one of: an integrated imaging device, a peripheral imaging device.
B8. The data decoding system of (B1), wherein said client is provided by a desktop computer comprising one of: an integrated imaging device, a peripheral imaging device.
B9. The data decoding system of (B1), wherein said client is provided by a computing device integrated into a point-of-sale system, said computing device comprising one of: an integrated imaging device, a peripheral imaging device.
C1. A data decoding system comprising one or more computers communicatively coupled to a network;
wherein at least one computer of said one or more computers is configured, responsive to receiving from a client a decoding request comprising an image of decodable indicia, to locate said decodable indicia within said image;
wherein said at least one computer is further configured, responsive to successfully locating said decodable indicia, to decode said decodable indicia into a decoded message;
wherein said at least one computer is further configured, responsive to completing a decoding operation, to transmit to said client at least one of: said decoded message, a decoding operation completion code; and
wherein said at least one computer is further configured to perform at least one of: validating an entitlement of said client to receive decoding services responsive to receiving said decoding request, transmit a billing request to a billing system responsive to completing said decoding operation.
C2. The data decoding system of (C1), wherein said billing request comprises at least one of: an identifier of said client, a symbology type of said decodable indicia, a number of decodable indicia items to be decoded.
C3. The data decoding system of (C1), wherein said at least one computer is configured to validate said entitlement of said client by transmitting a client entitlement validation request to said billing system.
C4. The data decoding system of (C3), wherein said client entitlement validation request comprises at least one of: an identifier of said client, a symbology type of said decodable indicia, a number of decodable indicia items to be decoded.
C5. The data decoding system of (C1), wherein said at least one computer is configured to transmit said decoded message to said client responsive to receiving a billing transaction confirmation from said billing system.
C6. The data decoding system of C1, wherein said image of decodable indicia is provided by one of: a raw image byte stream, a compressed image byte stream.
C7. The data decoding system of C1, wherein said client is provided by a mobile communication terminal comprising an optical reading device configured to output said image of decodable indicia.
C8. The data decoding system of C1, wherein said client is provided by a mobile computing device comprising one of: an integrated imaging device, a peripheral imaging device.
C9. The data decoding system of C1, wherein said client is provided by a desktop computer comprising one of: an integrated imaging device, a peripheral imaging device.
C10. The data decoding system of C1, wherein said client is provided by a computing device integrated into a point-of-sale system, said computing device comprising one of: an integrated imaging device, a peripheral imaging device.
Number | Name | Date | Kind |
---|---|---|---|
6618709 | Sneeringer | Sep 2003 | B1 |
6659344 | Otto et al. | Dec 2003 | B2 |
7003138 | Wilson | Feb 2006 | B2 |
7015967 | Kochi et al. | Mar 2006 | B1 |
7159770 | Onozu | Jan 2007 | B2 |
7178163 | Reeves | Feb 2007 | B2 |
7237721 | Bilcu et al. | Jul 2007 | B2 |
7287696 | Attia et al. | Oct 2007 | B2 |
7308158 | Herbert et al. | Dec 2007 | B2 |
7405662 | Steinke et al. | Jul 2008 | B2 |
7407096 | McQueen et al. | Aug 2008 | B2 |
7419097 | Lee et al. | Sep 2008 | B2 |
7480737 | Chauffour et al. | Jan 2009 | B2 |
7494063 | Kotlarsky et al. | Feb 2009 | B2 |
7501950 | Suzuki | Mar 2009 | B2 |
7535361 | Doan et al. | May 2009 | B2 |
7551090 | Doan et al. | Jun 2009 | B2 |
7602288 | Broussard | Oct 2009 | B2 |
7627191 | Xu et al. | Dec 2009 | B2 |
7677602 | Bennett et al. | Mar 2010 | B2 |
7696874 | Stevens | Apr 2010 | B2 |
7702187 | Rusman et al. | Apr 2010 | B2 |
7708205 | Kotlarsky et al. | May 2010 | B2 |
7735731 | Skaaksrud et al. | Jun 2010 | B2 |
7756292 | Lev | Jul 2010 | B2 |
7756319 | Odell | Jul 2010 | B2 |
7786865 | Park | Aug 2010 | B2 |
7786925 | Knibbe et al. | Aug 2010 | B1 |
7815121 | Kotlarsky et al. | Oct 2010 | B2 |
7821400 | Tabet et al. | Oct 2010 | B2 |
7831082 | Holsing et al. | Nov 2010 | B2 |
7831912 | King et al. | Nov 2010 | B2 |
7855643 | Tuttle | Dec 2010 | B2 |
7861936 | Kotlarsky et al. | Jan 2011 | B2 |
7870999 | Skaaksrud et al. | Jan 2011 | B2 |
7883013 | Skaaksrud et al. | Feb 2011 | B2 |
7886972 | Skaaksrud et al. | Feb 2011 | B2 |
7950698 | Popadic et al. | May 2011 | B2 |
7951003 | Russell et al. | May 2011 | B2 |
7961908 | Tzur et al. | Jun 2011 | B2 |
7965186 | Downie et al. | Jun 2011 | B2 |
7988050 | Kitada et al. | Aug 2011 | B2 |
8046311 | Ferraro et al. | Oct 2011 | B2 |
8079525 | Zolotov | Dec 2011 | B1 |
8087583 | Hawes | Jan 2012 | B2 |
8115601 | Nonaka | Feb 2012 | B2 |
8120818 | Nagata | Feb 2012 | B2 |
8139117 | Dwinell et al. | Mar 2012 | B2 |
8139249 | Venable | Mar 2012 | B2 |
8149094 | Deoalikar et al. | Apr 2012 | B2 |
8256664 | Balfanz et al. | Sep 2012 | B1 |
8485430 | Qu et al. | Jul 2013 | B2 |
9064254 | Todeschini et al. | Jun 2015 | B2 |
9398008 | Todeschini et al. | Jul 2016 | B2 |
20010047426 | Hunter | Nov 2001 | A1 |
20020165758 | Hind et al. | Nov 2002 | A1 |
20050212817 | Cannon et al. | Sep 2005 | A1 |
20050283448 | Dixon et al. | Dec 2005 | A1 |
20060262961 | Holsing et al. | Nov 2006 | A1 |
20060266836 | Bilcu et al. | Nov 2006 | A1 |
20070008136 | Suzuki | Jan 2007 | A1 |
20070028001 | Phillips et al. | Feb 2007 | A1 |
20070063050 | Attia et al. | Mar 2007 | A1 |
20070102506 | Stevens | May 2007 | A1 |
20070199995 | Kotlarsky et al. | Aug 2007 | A1 |
20070215706 | Kotlarsky et al. | Sep 2007 | A1 |
20080037899 | Xu et al. | Feb 2008 | A1 |
20080061937 | Park | Mar 2008 | A1 |
20080111661 | Lin et al. | May 2008 | A1 |
20080129825 | DeAngelis et al. | Jun 2008 | A1 |
20080164313 | Kotlarsky et al. | Jul 2008 | A1 |
20080164317 | Kotlarsky et al. | Jul 2008 | A1 |
20080169343 | Skaaksrud et al. | Jul 2008 | A1 |
20080172303 | Skaaksrud et al. | Jul 2008 | A1 |
20080173706 | Skaaksrud et al. | Jul 2008 | A1 |
20080173710 | Skaaksrud et al. | Jul 2008 | A1 |
20080203147 | Skaaksrud et al. | Aug 2008 | A1 |
20080203166 | Skaaksrud et al. | Aug 2008 | A1 |
20080210749 | Skaaksrud et al. | Sep 2008 | A1 |
20080210750 | Skaaksrud et al. | Sep 2008 | A1 |
20080224870 | Yeo et al. | Sep 2008 | A1 |
20080244076 | Shah et al. | Oct 2008 | A1 |
20080247363 | Lee et al. | Oct 2008 | A1 |
20080285091 | Skaaksrud et al. | Nov 2008 | A1 |
20080300898 | Bacha et al. | Dec 2008 | A1 |
20090021353 | Nanaka | Jan 2009 | A1 |
20090040025 | Volpi et al. | Feb 2009 | A1 |
20090045913 | Nelson et al. | Feb 2009 | A1 |
20090045924 | Roberts et al. | Feb 2009 | A1 |
20090109484 | Honda | Apr 2009 | A1 |
20090121025 | Romanchik | May 2009 | A1 |
20090161964 | Tzur et al. | Jun 2009 | A1 |
20090190183 | Hosoda | Jul 2009 | A1 |
20090214137 | Takahashi | Aug 2009 | A1 |
20090218405 | Joseph et al. | Sep 2009 | A1 |
20090243801 | Strzelczyk | Oct 2009 | A1 |
20090245755 | Lee et al. | Oct 2009 | A1 |
20090300106 | Woodside et al. | Dec 2009 | A1 |
20090307232 | Hall | Dec 2009 | A1 |
20090322537 | Tapp et al. | Dec 2009 | A1 |
20100005156 | Wesby | Jan 2010 | A1 |
20100045436 | Rinkes | Feb 2010 | A1 |
20100046842 | Conwell | Feb 2010 | A1 |
20100048242 | Rhoads et al. | Feb 2010 | A1 |
20100072269 | Scott et al. | Mar 2010 | A1 |
20100073487 | Sogoh et al. | Mar 2010 | A1 |
20100084470 | Scott et al. | Apr 2010 | A1 |
20100091313 | Kitada et al. | Apr 2010 | A1 |
20100109903 | Carrick | May 2010 | A1 |
20100142825 | Maxwell et al. | Jun 2010 | A1 |
20100145709 | Kumar | Jun 2010 | A1 |
20100148985 | Lin et al. | Jun 2010 | A1 |
20100163632 | Tseng et al. | Jul 2010 | A1 |
20100187311 | Van Der Merwe et al. | Jul 2010 | A1 |
20100189367 | Van Der Merwe et al. | Jul 2010 | A1 |
20100200660 | Moed et al. | Aug 2010 | A1 |
20100201488 | Stern et al. | Aug 2010 | A1 |
20100201520 | Stern et al. | Aug 2010 | A1 |
20100220894 | Ackley et al. | Sep 2010 | A1 |
20100226530 | Lev | Sep 2010 | A1 |
20100232712 | Tomita et al. | Sep 2010 | A1 |
20100250351 | Gillenson et al. | Sep 2010 | A1 |
20100250356 | Gillenson et al. | Sep 2010 | A1 |
20100250359 | Gillenson et al. | Sep 2010 | A1 |
20100252621 | Ito et al. | Oct 2010 | A1 |
20100260426 | Huang et al. | Oct 2010 | A1 |
20100271187 | Uysal et al. | Oct 2010 | A1 |
20100296753 | Ito et al. | Nov 2010 | A1 |
20100303348 | Tolliver et al. | Dec 2010 | A1 |
20100308964 | Ackley et al. | Dec 2010 | A1 |
20100327066 | Khan | Dec 2010 | A1 |
20110000958 | Herzig | Jan 2011 | A1 |
20110011936 | Morandi et al. | Jan 2011 | A1 |
20110019220 | Kikuchi | Jan 2011 | A1 |
20110019816 | Inami et al. | Jan 2011 | A1 |
20110026081 | Hamada et al. | Feb 2011 | A1 |
20110029363 | Gillenson et al. | Feb 2011 | A1 |
20110034176 | Lord et al. | Feb 2011 | A1 |
20110052008 | Holsing et al. | Mar 2011 | A1 |
20110081948 | Shirai et al. | Apr 2011 | A1 |
20110084808 | Tuttle | Apr 2011 | A1 |
20110102642 | Wang et al. | May 2011 | A1 |
20110115947 | Oh | May 2011 | A1 |
20110115950 | Wach | May 2011 | A1 |
20110128125 | Kai et al. | Jun 2011 | A1 |
20110143811 | Rodriguez | Jun 2011 | A1 |
20110155808 | Santos et al. | Jun 2011 | A1 |
20110200256 | Saubat et al. | Aug 2011 | A1 |
20110205387 | Tzur et al. | Aug 2011 | A1 |
20110207531 | Gagner et al. | Aug 2011 | A1 |
20110210171 | Brown et al. | Sep 2011 | A1 |
20110211726 | Moed et al. | Sep 2011 | A1 |
20110212717 | Rhoads et al. | Sep 2011 | A1 |
20110222757 | Yeatman, Jr. et al. | Sep 2011 | A1 |
20110251093 | Xia et al. | Oct 2011 | A1 |
20110280447 | Conwell | Nov 2011 | A1 |
20110284625 | Smith et al. | Nov 2011 | A1 |
20110290883 | Kotlarsky et al. | Dec 2011 | A1 |
20110310442 | Popadic et al. | Dec 2011 | A1 |
20110311026 | Lalena | Dec 2011 | A1 |
20120037695 | Liu et al. | Feb 2012 | A1 |
20120047424 | Rothschild | Feb 2012 | A1 |
20120048920 | Iizaka | Mar 2012 | A1 |
20120063690 | Ashok et al. | Mar 2012 | A1 |
20120064971 | Devine et al. | Mar 2012 | A1 |
20120079544 | Massimino | Mar 2012 | A1 |
20120091204 | Shi | Apr 2012 | A1 |
20120221724 | Chor | Aug 2012 | A1 |
20130142444 | Qu et al. | Jun 2013 | A1 |
20130159080 | Wu et al. | Jun 2013 | A1 |
20130194077 | Vargas et al. | Aug 2013 | A1 |
20130277427 | Zumsteg et al. | Oct 2013 | A1 |
20130277430 | Zumsteg et al. | Oct 2013 | A1 |
20130278386 | Zumsteg | Oct 2013 | A1 |
20130278393 | Zumsteg | Oct 2013 | A1 |
20130306720 | Todeschini et al. | Nov 2013 | A1 |
20130306736 | Yeakley et al. | Nov 2013 | A1 |
20140001254 | Williams et al. | Jan 2014 | A1 |
20140014724 | Koziol et al. | Jan 2014 | A1 |
20140021256 | Qu et al. | Jan 2014 | A1 |
20140051054 | Wong et al. | Feb 2014 | A1 |
20140189353 | Apsangi et al. | Jul 2014 | A1 |
Entry |
---|
EPC GLOBAL, Specification for RFID Air Interface, EPC Radio-Frequency Identity Protocols Class-1 Generation-2 UHF RFID Protocol for Communications at 860 MHz-960 MHz, Version 1.0.9, Jan. 31, 2005, pp. 1-94. |
Number | Date | Country | |
---|---|---|---|
20160321372 A1 | Nov 2016 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 14744836 | Jun 2015 | US |
Child | 15211745 | US | |
Parent | 13474014 | May 2012 | US |
Child | 14744836 | US |