Methods, systems, apparatuses, and non-transitory computer readable media for validating encoded information

CROSS-REFERENCE

This application is a continuation application of U.S. application Ser. No. 16/526,378, filed on Jul. 30, 2019, which is a continuation application of U.S. application Ser. No. 15/193,626, filed on Jun. 27, 2016, the entire contents of each of which are hereby incorporated by reference.

BACKGROUND

Field

The present disclosure relates to methods, systems, apparatuses and/or non-transitory computer readable media for validating coded information, and more specifically to systems and apparatuses for formatting and/or validating encoded information, and methods and non-transitory computer readable media for validating the same.

Description

Various techniques currently exist for encoding and/or validating coded information. Coded information may be used to express various types of information for use in many different types of applications, such as data gathering applications, real-time tracking applications, transmittal of information to stand alone electronic appliance applications, etc. While there is a great range of applications that encoded information may be used with, and great utility may be derived from the use of encoded information, one particular challenge faced with the use of a new encoded information system is generating wide adoption of the new encoded information system by various stakeholders/actors. More particularly, some of the issues that prohibit and/or decrease the adoption of a new encoded information system are directly caused by the expense and inconvenience of having to acquire and install new hardware elements compatible with the new encoded information system and/or upgrading existing hardware elements to be compatible with the new encoded information system. Another issue inhibiting the adoption of new encoded information systems pertains to issues where pre-existing hardware systems for validating encoded information may use proprietary and/or customized hardware elements that have limited to no upgrade capability. For example, a pre-existing hardware system may not have sufficient memory capacity, processing capability, networking capability, etc., to support a new and/or updated encoded information system. This is particularly worrisome when a particular encoded information system requires new, additional, and/or updated security functionality, rule sets, procedures, etc., to account for or deter potential attacks, hacks, fraud, etc., from being performed on the hardware system. Therefore, there exists a demand for formatting and/or validating apparatuses, systems, methods, and non-transitory computer readable media that enable the upgrading of pre-existing encoded information systems to be compatible with new encoded information systems. There also exists a demand for formatting and/or validating apparatuses, systems, methods, and non-transitory computer readable media that may operate in conjunction with future encoded information hardware systems without requiring special modification and/or customization of the future encoded information hardware system.

SUMMARY

At least one example embodiment relates to a formatting device for validating encoded information. In at least one example embodiment, the formatting device includes an input-output (I/O) interface configured to receive encoded information from a connected scanning device, a memory having stored thereon computer readable instructions, and at least one processor configured to execute the computer readable instructions to format the received encoded information into formatted data compatible with a point-of-sale (POS) terminal, classify the formatted data into at least one classification layer of a plurality of classification layers in accordance with attributes associated with the received encoded information and a plurality of matching rules stored in the memory, determine a destination to transmit the formatted data based on the classification layer, the formatted data including metadata associated with the received encoded information and token information, and transmit the formatted data to the determined destination.

In at least one example embodiment, the determined destination may be at least one of a local rules server, the POS terminal, a cloud server, and at least one second formatting device.

Some example embodiments provide that the device may include a wireless transceiver configured to transmit the formatted data to the local rules server when the determined destination is the local rules server, and receive modified formatted data compatible with the POS terminal from the local rules server, the modified formatted data including a message indicating results of a validation determination performed by the local rules server and the attributes associated with the received encoded information, the validation determination indicating whether the attributes associated with the received encoded information are valid. The at least one processor may be further configured to transmit the modified formatted data to the POS terminal.

Some example embodiments provide that the POS terminal may be configured to extract the message and the attributes associated with the received encoded information from the modified formatted data, determine whether the attributes associated with the received encoded information is valid based on the extracted message, and process results of the determination.

Some example embodiments provide that the message may be one of at least a message indicating that the attributes associated with the received encoded information is valid, a message indicating that the attributes associated with the received encoded information is invalid, a message indicating that an error occurred, and a null message.

Some example embodiments provide that the wireless transmitter may be configured to connect to the local rules server over a Personal Area Network (PAN).

Some example embodiments provide that the I/O interface may be configured to transmit the received encoded information directly to the POS terminal if it is not in communication with a local rules server.

Some example embodiments provide that the POS terminal may be configured to provide power to the formatting device.

Some example embodiments provide that the encoded information may be an encrypted unique code that is displayed to the scanning device.

Some example embodiments provide that the plurality of classification layers may include a first classification layer associated with printed encoded information, a second classification layer associated with one-time use encoded information, and a third classification layer associated with a set of custom matching rules, the set of custom matching rules stored on the memory.

At least one example embodiment relates to a validation system for validating encoded information. In at least one example embodiment, the validation system includes at least one scanning device configured to read encoded information, at least one point-of-sale (POS) terminal, at least one local rules server configured to store a plurality of validation rules, and at least one formatting device, the device including an input-output (I/O) interface configured to receive the encoded information from the scanning device, a memory having stored thereon computer readable instructions, and at least one processor configured to format the received encoded information into formatted data compatible with the point-of-sale (POS) terminal, classify the formatted data into at least one classification layer of a plurality of classification layers in accordance with attributes associated with the received encoded information and a plurality of matching rules stored in the memory, determine a destination to transmit the formatted data based on the classification layer, the formatted data including metadata associated with the received encoded information and token information, and transmit the formatted data to the determined destination.

Some example embodiments provide that the at least one formatting device may include a plurality of formatting devices, and each of the plurality of formatting devices may include a wireless transceiver configured to transmit the formatted data to the local rules server when the determined destination is the local rules server, receive modified formatted data compatible with the POS terminal from the local rules server, and the modified formatted data including a message indicating results of a validation determination performed by the local rules server and the attributes associated with the received encoded information, the validation determination indicating whether the attributes associated with the received encoded information are valid. The at least one processor may be further configured to transmit the modified formatted data to the POS terminal.

Some example embodiments provide that the plurality of formatting devices may be configured to communicate via a personal area network (PAN).

Some example embodiments provide that the at least one local rules server may include a database storing the plurality of validation rules, the plurality of validation rules associated with a plurality of encoded information and validation state information regarding the plurality of encoded information. The local rules server may be configured to receive the formatted data from the at least one formatting device, extract the attributes associated with the received encoded information from the formatted data, the extracted attributes including at least one of a formatting device identifier, a store identifier, value information from the encoded information, and time information, validate the formatted data based on the extracted attributes and the plurality of validation rules, store the results of the validation and at least a subset of the extracted attributes in the database, generate the modified formatted data compatible with the POS terminal based on the results of the validation, and transmit the modified formatted data to the at least one of formatting device.

Some example embodiments provide that the system may further include a cloud server configured to transmit new validation rules to the local rules server database, and receive the results of the validation from the local rules server and the validation state information from the local rules server.

Some example embodiments provide that the cloud server may be configured to transmit software updates to the local rules server and receive hardware status information from the local rules server.

Some example embodiments provide that the local rules server may be configured to communicate with the cloud server over a network.

Some example embodiments provide that the local rules server may include a cellular transceiver configured to communicate with the cloud server over a cellular network.

Some example embodiments provide that the cloud server may be further configured to generate the encoded information using an encryption algorithm and the validation rules, the encoded information being an encrypted unique code.

At least one example embodiment relates to a method for validating encoded information. In at least one example embodiment, the method includes receiving, using at least one processor, encoded information from a scanning device, formatting, using the at least one processor, the received encoded information into formatted data compatible with a point-of-sale (POS) terminal, classifying, using the at least one processor, the formatted data into at least one classification layer of a plurality of classification layers in accordance with attributes associated with the received encoded information and a plurality of matching rules stored in memory of a formatting device, determining, using the at least one processor, a destination to transmit the formatted data based on the classification layer, the formatted data including metadata associated with the received encoded information and token information, and transmitting, using the processor, the formatted data to the determined destination.

In at least one example embodiment the method may further include transmitting, using the at least one processor, the formatted data to the local rules server based on the results of the determining, receiving, using the at least one processor, a modified formatted data compatible with the POS terminal from the local rules server, the modified formatted data including a message indicating results of a validation determination performed by the local rules server and the attributes associated with the received encoded information, the validation determination indicating whether the attributes associated with the received encoded information are valid, and transmitting, using the at least one processor, the modified formatted data to the POS terminal.

At least one example embodiment relates to a validation device. In at least one example embodiment, the validation device includes a memory having computer readable instructions stored thereon and a database that includes a plurality of validation rules, and at least one processor configured to execute the computer readable instructions to receive formatted data from at least one formatting device, extract attributes associated with encoded information from the formatted data, the extracted attributes including at least one of a formatting device identifier, a store identifier, value information from the encoded information, and time information, validate the formatted data based on the extracted attributes and the plurality of validation rules, store the results of the validation and at least a subset of the extracted attributes in the database, generate modified formatted data compatible with a POS terminal based on the results of the validation, and transmit the modified formatted data to the at least one of formatting device.

Some example embodiments provide that the validation device may include at least one transceiver configured to communicate with the at least one formatting device and a cloud server.

Some example embodiments provide that the at least one processor may be further configured to receive new validation rules from the cloud server, install the new validation rules on the database, and transmit at least one of the results of the validation, validation state information, and hardware status information to the cloud server.

Some example embodiments provide that the at least one processor may be further configured to receive software updates from the cloud server, determine whether to update software installed on the at least one formatting device based on the received software updates, and transmit the software updates to the at least one formatting device based on results of the determining.

Some example embodiments provide that the software updates may include at least one of software upgrades for the validation device, software upgrades for the at least one formatting device, and new custom matching rules for the at least one formatting device.

Some example embodiments provide that the at least one processor may be further configured to receive content from the cloud server, and transmit the content to at least one device, the device including at least one of a mobile device, the POS terminal, and an electronic display.

Some example embodiments provide that the content may be multimedia content.

Further areas of applicability will become apparent from the description provided herein. The description and specific examples in this summary are intended for purposes of illustration only and are not intended to limit the scope of the present disclosure.

BRIEF DESCRIPTION OF THE DRAWINGS

Example embodiments will be described in more detail with regard to the figures, wherein like reference numerals refer to like parts throughout the various figures unless otherwise specified, and wherein:

<figref idref="DRAWINGS">FIG. 1</figref> illustrates a system for validating encoded information according to at least one example embodiment.

<figref idref="DRAWINGS">FIG. 2</figref> illustrates a hardware configuration of a formatting device according to at least one example embodiment.

<figref idref="DRAWINGS">FIG. 3</figref> illustrates a block diagram for the software modules of a formatting device according to at least one example embodiment.

<figref idref="DRAWINGS">FIG. 4</figref> illustrates a hardware configuration of a validation device according to at least one example embodiment.

<figref idref="DRAWINGS">FIG. 5</figref> illustrates a block diagram for the software modules of a validation device according to at least one example embodiment.

<figref idref="DRAWINGS">FIG. 6</figref> is a flowchart diagram illustrating a method for validating encoded information according to at least one example embodiment.

<figref idref="DRAWINGS">FIG. 7</figref> is a block diagram of a message envelope format for a data stream according to at least one example embodiment.

<figref idref="DRAWINGS">FIGS. 8A, 8B, 8C, 8D, and 8E</figref> are flowchart diagrams illustrating the transmission of messages between the elements of a encoded information validation system according to some example embodiments.

It should be noted that these figures are intended to illustrate the general characteristics of methods and/or structure utilized in certain example embodiments and to supplement the written description provided below. These drawings are not, however, to scale and may not precisely reflect the precise structural or performance characteristics of any given embodiment, and should not be interpreted as defining or limiting the range of values or properties encompassed by example embodiments.

DETAILED DESCRIPTION

One or more example embodiments will be described in detail with reference to the accompanying drawings. Example embodiments, however, may be embodied in various different forms, and should not be construed as being limited to only the illustrated embodiments. Rather, the illustrated embodiments are provided as examples so that this disclosure will be thorough and complete, and will fully convey the concepts of this disclosure to those skilled in the art. Accordingly, known processes, elements, and techniques, may not be described with respect to some example embodiments. Unless otherwise noted, like reference characters denote like elements throughout the attached drawings and written description, and thus descriptions will not be repeated.

Although the terms “first,” “second,” “third,” etc., may be used herein to describe various elements, regions, layers, and/or sections, these elements, regions, layers, and/or sections, should not be limited by these terms. These terms are only used to distinguish one element, region, layer, or section, from another region, layer, or section. Thus, a first element, region, layer, or section, discussed below may be termed a second element, region, layer, or section, without departing from the scope of this disclosure.

Spatially relative terms, such as “beneath,” “below,” “lower,” “under,” “above,” “upper,” and the like, may be used herein for ease of description to describe one element or feature's relationship to another element(s) or feature(s) as illustrated in the figures. It will be understood that the spatially relative terms are intended to encompass different orientations of the device in use or operation in addition to the orientation depicted in the figures. For example, if the device in the figures is turned over, elements described as “below,” “beneath,” or “under,” other elements or features would then be oriented “above” the other elements or features. Thus, the example terms “below” and “under” may encompass both an orientation of above and below. The device may be otherwise oriented (rotated 90 degrees or at other orientations) and the spatially relative descriptors used herein interpreted accordingly. In addition, when an element is referred to as being “between” two elements, the element may be the only element between the two elements, or one or more other intervening elements may be present.

As used herein, the singular forms “a,” “an,” and “the,” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises” and/or “comprising,” when used in this specification, specify the presence of stated features, integers, steps, operations, and/or elements, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, and/or groups, thereof. As used herein, the term “and/or” includes any and all combinations of one or more of the associated listed items. Expressions such as “at least one of,” when preceding a list of elements, modify the entire list of elements and do not modify the individual elements of the list. Also, the term “exemplary” is intended to refer to an example or illustration.

When an element is referred to as being “on,” “connected to,” “coupled to,” or “adjacent to,” another element, the element may be directly on, connected to, coupled to, or adjacent to, the other element, or one or more other intervening elements may be present. In contrast, when an element is referred to as being “directly on,” “directly connected to,” “directly coupled to,” or “immediately adjacent to,” another element there are no intervening elements present.

Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which example embodiments belong. Terms, such as those defined in commonly used dictionaries, should be interpreted as having a meaning that is consistent with their meaning in the context of the relevant art and/or this disclosure, and should not be interpreted in an idealized or overly formal sense unless expressly so defined herein.

Example embodiments may be described with reference to acts and symbolic representations of operations (e.g., in the form of flow charts, flow diagrams, data flow diagrams, structure diagrams, block diagrams, etc.) that may be implemented in conjunction with units and/or devices discussed in more detail below. Although discussed in a particular manner, a function or operation specified in a specific block may be performed differently from the flow specified in a flowchart, flow diagram, etc. For example, functions or operations illustrated as being performed serially in two consecutive blocks may actually be performed simultaneously, or in some cases be performed in reverse order.

Units and/or devices according to one or more example embodiments may be implemented using hardware, or a combination of hardware and software. For example, hardware devices may be implemented using processing circuitry such as, but not limited to, a processor, Central Processing Unit (CPU), a controller, an arithmetic logic unit (ALU), a digital signal processor, a microcomputer, a field programmable gate array (FPGA), a System-on-Chip (SoC), a programmable logic unit, a microprocessor, or any other device capable of responding to and executing instructions in a defined manner.

Software may include a computer program, program code, instructions, or some combination thereof, for independently or collectively instructing or configuring a hardware device to operate as desired. The computer program and/or program code may include program or computer-readable instructions, software modules, data files, data structures, and/or the like, capable of being implemented by one or more hardware devices, such as one or more of the hardware devices mentioned above. Examples of program code include both machine code produced by a compiler and higher level program code that is executed using an interpreter.

For example, when a hardware device is a computer processing device (e.g., a processor, Central Processing Unit (CPU), a controller, an arithmetic logic unit (ALU), a digital signal processor, a microcomputer, a microprocessor, etc.), the computer processing device may be configured to carry out program code by performing arithmetical, logical, and input/output operations, according to the program code. Once the program code is loaded into a computer processing device, the computer processing device may be programmed to perform the program code, thereby transforming the computer processing device into a special purpose computer processing device. In a more specific example, when the program code is loaded into a processor, the processor becomes programmed to perform the program code and operations corresponding thereto, thereby transforming the processor into a special purpose processor.

Software and/or data may be embodied permanently or temporarily in any type of machine, element, physical or virtual equipment, or computer storage medium or device, capable of providing instructions or data to, or being interpreted by, a hardware device. The software also may be distributed over network coupled computer systems so that the software is stored and executed in a distributed fashion. In particular, for example, software and data may be stored by one or more computer readable recording mediums, including the tangible or non-transitory computer-readable storage media discussed herein.

According to one or more example embodiments, computer processing devices may be described as including various functional units that perform various operations and/or functions to increase the clarity of the description. However, computer processing devices are not intended to be limited to these functional units. For example, in one or more example embodiments, the various operations and/or functions of the functional units may be performed by other ones of the functional units. Further, the computer processing devices may perform the operations and/or functions of the various functional units without sub-dividing the operations and/or functions of the computer processing units into these various functional units.

Units and/or devices according to one or more example embodiments may also include one or more storage devices. The one or more storage devices may be tangible or non-transitory computer-readable storage media, such as random access memory (RAM), read only memory (ROM), a permanent mass storage device (such as a disk drive), solid state (e.g., NAND flash) device, and/or any other like data storage mechanism capable of storing and recording data. The one or more storage devices may be configured to store computer programs, program code, instructions, or some combination thereof, for one or more operating systems and/or for implementing the example embodiments described herein. The computer programs, program code, instructions, or some combination thereof, may also be loaded from a separate computer readable storage medium into the one or more storage devices and/or one or more computer processing devices using a drive mechanism. Such separate computer readable storage medium may include a Universal Serial Bus (USB) flash drive, a memory stick, a Blu-ray/DVD/CD-ROM drive, a memory card, and/or other like computer readable storage media. The computer programs, program code, instructions, or some combination thereof, may be loaded into the one or more storage devices and/or the one or more computer processing devices from a remote data storage device via a network interface, rather than via a local computer readable storage medium. Additionally, the computer programs, program code, instructions, or some combination thereof, may be loaded into the one or more storage devices and/or the one or more processors from a remote computing system that is configured to transfer and/or distribute the computer programs, program code, instructions, or some combination thereof, over a network. The remote computing system may transfer and/or distribute the computer programs, program code, instructions, or some combination thereof, via a wired interface, an air interface, and/or any other like medium.

The one or more hardware devices, the one or more storage devices, and/or the computer programs, program code, instructions, or some combination thereof, may be specially designed and constructed for the purposes of the example embodiments, or they may be known devices that are altered and/or modified for the purposes of example embodiments.

A hardware device, such as a computer processing device, may run an operating system (OS) and one or more software applications that run on the OS. The computer processing device also may access, store, manipulate, process, and create data in response to execution of the software. For simplicity, one or more example embodiments may be exemplified as one computer processing device; however, one skilled in the art will appreciate that a hardware device may include multiple processing elements and multiple types of processing elements. For example, a hardware device may include multiple processors or a processor and a controller. In addition, other processing configurations are possible, such as parallel processors.

Although described with reference to specific examples and drawings, modifications, additions and substitutions of example embodiments may be variously made according to the description by those of ordinary skill in the art. For example, the described techniques may be performed in an order different with that of the methods described, and/or elements such as the described system, architecture, devices, circuit, and the like, may be connected or combined to be different from the above-described methods, or results may be appropriately achieved by other elements or equivalents.

<figref idref="DRAWINGS">FIG. 1</figref> illustrates a system for formatting and validating encoded information according to at least one example embodiment. The validation system <b>100</b> includes one or more encoded information scanners (e.g., <b>110</b>, <b>111</b>), one or more formatting devices (e.g., <b>120</b>, <b>121</b>), one or more validation devices (e.g., <b>140</b>), and one or more end point terminals (e.g., <b>130</b>, <b>131</b>). According to some example embodiments, the system may also include one or more servers (not shown), such as a cloud server, or platform server. While two encoded information scanners, two formatting devices, one validation device, and two end point terminals are illustrated in <figref idref="DRAWINGS">FIG. 1</figref>, the example embodiments are not limited thereto and there may be a greater or lesser number of each individual element in the system and/or other additional elements included in the system according to other example embodiments, such as a cloud server.

According to various example embodiments, the encoded information scanners and the end point terminals may be pre-existing conventional scanners and terminals that have been used for and/or are compatible with pre-existing and/or other encoded information systems. For example, the encoded information scanners <b>110</b>, <b>111</b> may be barcode scanners, document scanners, cameras, video cameras, etc., that are used to capture information related to encoded information. The end point terminals <b>130</b>, <b>131</b> may be Point-of-Sale (POS) terminals, computer terminals, servers, cash registers, OCR capable systems, electronic turnstiles, security checkpoints, etc., that are used to process and/or apply encoded information to provide a result (e.g., apply a discount to a purchase amount, allow/deny access to a secured location, etc.). The end point terminals may include a display device that may display the results of the encoded information validation, operator instructions related to the encoded information validation results, and/or other information to the end point terminal operator. Examples of an encoded information system include document verification systems (e.g., passport verification systems, driver's license verification systems, airline boarding pass verification systems, ticket verification systems, bank note verification systems, currency verification systems, other identity verification systems, etc.), point of sale systems (e.g., in-store POS systems, gift card systems, coupon validation systems, product purchasing systems, loyalty card systems, membership verification systems, etc.), item tracking systems (e.g., warehouse item tracking systems, shipping tracking systems, library book tracking systems, etc.), etc., but the example embodiments are not limited thereto and may be applicable to other uses as well. Examples of the encoded information include barcodes, quick response (QR) codes, holograms, unique alphanumeric identifiers, unique images/pictures, character/numeric text strings, unique audible signals, information encoded in magnetic strips, etc., but the example embodiments are not limited thereto.

For example, in the Point-of-Sale (POS) context, the encoded information scanners <b>110</b> and <b>111</b> may be barcode scanners, RFID scanners, and/or image scanners (e.g., cameras, flatbed scanners, etc.), etc., that read encoded information, such as a barcode, QR code, alphanumeric string, unique image, etc., from a paper document, a product's packaging, a mobile device (e.g., a smartphone, tablet, a personal digital assistant (PDA), a laptop computer, a wearable device, etc.) displaying the encoded information, etc. The encoded information may conform to and/or be generated according to a specific encoded information system, such as a Universal Product Code (UPC) encoding system, an International Article Number (EAN) encoding system, an International Standard Book Number (ISBN) encoding system, other well-known coding systems, an RFID identification system, a holographic encoding system, etc. The encoded information may include information that is to be verified and/or applied by the end point terminal, such as personal identification information, biometric information, product information, price information, coupon information, promotion information, membership information, loyalty program information, expiration/validity information (e.g., expiration date, date ranges that the coupon is valid for, etc.), value information, etc.

Additionally, in a document verification context (such as security checkpoints, airport terminal/customs security, ticketing checkpoints (e.g., sports events, concerts, etc.), currency verification, banknote verification, etc.), the encoded information scanners <b>110</b> and <b>111</b> may be barcode scanners, radio frequency identification (RFID) scanners, image scanners, infra-red (IR)/ultra-violet (UV) scanners, holographic image detectors, near field communication (NFC) scanners, etc., for detecting and/or reading encoded information from security features of a document. The encoded information may conform to and/or be generated according to specific secure encoded information systems, such as information printed special ink only detectable under IR/UV light, special holograms, magnetic dots, magnetic inks, security threads, unique serial numbers, biometric information, encrypted and/or tokenized information requiring public/private key decryption methods, etc. The encoded information may contain information that is to be verified and/or applied by the end point terminal, such as personal identification information, biometric information, currency information, banknote information, membership information, ticket/seat information, etc.

The formatting devices <b>120</b> and <b>121</b> are processing devices that are connected to the encoded information scanners <b>110</b> and <b>111</b>, respectively, over a wired and/or wireless connection, such as a universal serial bus (USB) connection, a FireWire connection, a Serial Digital Interface (SDI) connection, an Ethernet connection, a Bluetooth connection, a WiFi connection, an infra-red (IR) connection, a Code Division Multiple Access (CDMA) connection, a Global System for Mobile Communications (GSM) connection, a 3G connection, a 4G connection, a 5G connection, an LTE connection, other cellular network connections, a satellite connection, etc., or combinations thereof. The formatting devices <b>120</b> and <b>121</b> may receive the encoded information scanned by the encoded information scanners <b>110</b> and <b>111</b>, analyze the received encoded information according to one or more rules stored on the formatting devices, determine the destination of the received encoded information according to the results of the analysis, such as the validation device <b>140</b> and/or the end point terminals <b>130</b> and <b>131</b>, etc., and then format the received encoded information into a format compatible with the destination based on the specifications of the destination, for example formatting the received encoded information using a desired barcode system and/or proprietary messaging system that the POS terminal is preconfigured to read and interpret. The formatted encoded information may also include tokenized information/data that includes the results of the analysis, as well as metadata pertaining to the validation state of the received encoded information (e.g., has this encoded information type been scanned before, was this encoded information type scanned before, previous verification of the encoded information (i.e., was the encoded information accepted/rejected previously), etc.), metadata pertaining to the operating status of the encoded information scanner(s) and/or formatting device, aggregated statistics stored on the formatting device, etc. Once the received encoded information has been formatted into a format compatible with the destination, the formatting device <b>120</b> and/or <b>121</b> transmits the formatted encoded information to the destination for further processing. Additional information regarding the formatting device will be discussed in connection with <figref idref="DRAWINGS">FIGS. 2 and 3</figref>.

The validation device <b>140</b> is a processing device that is connected to (in other words, associated with) one or more formatting devices (e.g., formatting devices <b>120</b> and <b>121</b>) over a wired and/or wireless connection. The process of connecting the validation device <b>140</b> with the one or more formatting devices may also be referred to as associating the formatting devices to the validation device, or pairing the formatting devices to the validation device (e.g., through a Bluetooth and/or other wireless communication pairing process). The validation device <b>140</b> may be located in the same physical location and/or network as the one or more formatting devices (e.g., same LAN network, same intranet network, same building, same retail store, a personal area network (PAN), a Bluetooth network, etc.), or may reside at a different physical location and/or different network, and acts as a local rules server for the one or more associated formatting devices. For example, the validation device <b>140</b> may be a server and may reside on a cloud network, the Internet, a private network specific to the present encoded information validation system, a cellular network, etc. The validation device <b>140</b> is associated with one or more formatting devices and serves as a “clearinghouse” for the validation processing of all of the received encoded information for the one or more associated formatting devices. If the formatting device determines that the destination of the received encoded information is the validation device (e.g., the received encoded information requires validation), the validation device will receive the formatted encoded information and process the encoded information using local rule sets associated with one or more types/categories of encoded information stored on the validation device.

The validation device may include a database storing rules regarding one or more encoded information types/categories, such as multi-use coupons, one-time use coupons, limited time product promotions, product sales information, other limited use offers, one-time use ticket information, allowed/restricted personnel information, allowed/restricted passenger information, information related to how to verify security products, valid/invalid serial numbers, etc., and may analyze the formatted encoded information using the rules stored in the database. Once the validation process has been performed, the validation device modifies the formatted encoded information by including the results of the validation in the formatted encoded information message, include a message regarding the validation status of the encoded information, and/or include instructions for the terminal operator (e.g., process the encoded information manually, apply extra security measures, contact security, contact law enforcement, etc.) to be displayed on a display device associated with the end point terminal (e.g., POS terminal, etc.). Additionally, the validation device may transmit software updates to the formatting devices, such as providing new and/or updated rules, new and/or updated security policy information, new and/or updated encryption/decryption keys, firmware updates, etc. The formatting device may install the received software updates based on a determination that the software updates are of a higher version number than the software currently installed on the formatting device.

For example, in the POS context, a plurality of formatting devices may be installed in a single retail store, each of the plurality of formatting devices associated with at least one barcode scanner and at least one POS terminal (e.g., cash register, checkout kiosk, etc.). In the security context, a plurality of formatting devices may be installed at various security checkpoints and/or turnstiles in a physical location, such as an airport, sports arena, office building, etc. Each of the plurality of formatting devices is associated with a single validation device that is associated with the retail store/physical building. The plurality of formatting devices may connect to the validation device over a wired/wireless connection (e.g., USB, Bluetooth, wired/wireless LAN, cellular connection, etc.). In some example embodiments, the formatting devices and validation device connect over a secure private network, such as a Bluetooth PAN, etc., that is separate and/or independent from the retail store's/physical location's existing network, thereby providing additional security over the communications between the formatting devices and the validation device by requiring separate security credentials to access the network, while advantageously appearing transparent to the existing retail store's/physical location's computer network and existing POS terminal/security terminal system. With this system configuration, the retail store's/physical location's information technology (IT) maintenance costs are reduced because the encoded information validation system is independent from the retail store's/physical location's existing IT infrastructure, provides for greater security because the security of the encoded information validation system is independent from the security of the retail store's/physical location's pre-existing system since the two systems operate on separate networks that require separate security credentials, integrates seamlessly with the retail store's/physical location's pre-existing terminal system (e.g., the retail store's barcode scanners and POS terminals, security scanner system, building security badge system, etc.) without modification to any network settings, and allows the pre-existing POS terminal system to operate normally without requiring awareness of and/or additional software customized for the encoded information validation system.

The validation device <b>140</b> may also be connected over a wired and/or wireless connection to a platform server, such as a cloud server. The validation device <b>140</b> may transmit statistics regarding received encoded information (aggregated and/or individual), validation determination results (aggregated and/or individual), formatting device operating status information, validation device operating status information, etc. Additionally, the cloud server may transmit software updates to the validation device <b>140</b>, such as new and/or updated validation rules for the validation device <b>140</b>, new and/or updated forwarding rules for the formatting device <b>120</b>, new and/or updated custom matching rules for the formatting device <b>120</b>, new and/or updated security policy information for the validation device <b>140</b> and/or formatting device <b>120</b>, new and/or updated encryption/decryption keys for the validation device <b>140</b> and/or formatting device <b>120</b>, firmware updates for the validation device <b>140</b> and/or formatting device <b>120</b>, multimedia content to be displayed and/or broadcast by the validation device <b>140</b>, etc. Additional information regarding the validation device <b>140</b> will be provided in connection with <figref idref="DRAWINGS">FIGS. 4 and 5</figref>.

<figref idref="DRAWINGS">FIG. 2</figref> illustrates the hardware configuration of the formatting device <b>120</b> according to at least one example embodiment. In various example embodiments, the formatting device, such as formatting device <b>120</b> or <b>121</b>, includes at least a housing <b>210</b>, a client interface <b>220</b>, a microcontroller (MCU) <b>230</b> and memory <b>235</b>, a wireless transmitter <b>240</b>, and a host interface <b>250</b>. The housing <b>210</b> may be formed according to various form factors, particularly small form factors, such as a USB device form factor. The client interface <b>220</b> is a physical interface configured to physically connect the formatting device <b>120</b> with other elements of the encoded information validation system, such as the end point terminal <b>130</b> and/or the validation device <b>140</b>. Additionally, the formatting device <b>120</b> may also include a second physical interface, host interface <b>250</b>, which physically connects the formatting device <b>120</b> with other elements of the encoded information validation system, such as the scanning device <b>110</b>. The client interface <b>220</b> and the host interface <b>250</b> are compatible with the scanning device <b>110</b> and the end point terminal <b>130</b>, with the scanning device <b>110</b> and end point terminal <b>130</b> sharing the same communication protocol/standard.

For example, according to at least one example embodiment, the client interface <b>220</b> and the host interface <b>250</b> may be USB communication protocol interfaces, and the host interface <b>250</b> may connect to a US B-type scanning device and the client interface <b>220</b> may connect to an end point terminal with USB ports. The formatting device <b>120</b> may be installed in-line between the scanning device <b>110</b> and the end point terminal <b>130</b>, e.g., the USB connector of the scanning device <b>110</b> that would normally connect to the end point terminal <b>130</b> is instead connected to the USB host interface <b>250</b> of the formatting device <b>120</b>, and the USB client interface <b>220</b> of the formatting device <b>120</b> is connected to a USB port (and/or USB cable connected to the USB port) of the end point terminal <b>130</b>. Accordingly, the scanning device <b>110</b> may natively transmit the received encoded information (e.g., a barcode, QR code, image, etc.) to the formatting device <b>120</b> using the native connection type that the scanning device <b>110</b> and the end point terminal <b>130</b> is configured for using the native communication protocol for the scanning device/end point terminal system, while the formatting device <b>120</b> transparently intercepts and/or redirects the communication for validation and/or further processing, or in the event that validation and/or further processing is not necessary, directly passes the native communication from the scanning device <b>110</b> to the end point terminal <b>130</b> without interruption or modification. Additionally, the formatting device <b>120</b>, when installed in-line with the end point terminal <b>130</b>, may receive electrical power from the end point terminal <b>130</b> through the client interface <b>220</b> and may not require an external electrical power source. For example, when the formatting device <b>120</b> connects to the end point terminal <b>130</b> via a USB port, the formatting device <b>120</b> may receive electrical power from the end point terminal <b>130</b> via the USB connection sufficient to power the formatting device <b>120</b>.

Moreover, the client interface <b>220</b> and the host interface <b>250</b> are not limited to a wired USB interface, but may be any suitable wired connection interface, such as a RS-232 interface, FireWire interface, PCIe interface, Serial ATA interface, a fiber-optic interface, etc. Additionally, according to at least one example embodiment, the scanning device <b>110</b> and the formatting device <b>120</b>, and/or the formatting device <b>120</b> and the end point terminal <b>130</b> may communicate over a wireless connection using the wireless transmitter <b>240</b>, such as a Bluetooth network, wireless LAN network, a cellular network, etc., instead of, or in addition to, the wired connection.

Referring again to <figref idref="DRAWINGS">FIG. 2</figref>, the formatting device <b>120</b> also includes a MCU <b>230</b> and memory <b>235</b>. According to at least one example embodiment, the MCU <b>230</b> and memory <b>235</b> may be combined into one unit, but is not limited thereto and may be separate units. The MCU <b>230</b> is a processing device, such as a microcontroller, a central processing unit (CPU), an arithmetic logic unit (ALU), a digital signal processor, a microcomputer, a field programmable gate array (FPGA), a System-on-Chip (SoC), a programmable logic unit, a microprocessor, or any other device capable of responding to and executing instructions in a defined manner. Advantageously, the MCU <b>230</b> may be a low power processing device, such as a low power ARM based processor, a low power CISC based processor (e.g., x86 ISA), etc., in order to perform the forwarding rules (and/or custom matching rules) determination. The memory <b>235</b> may comprise one or more non-transitory computer storage media, such as one or more of ROM memory, RAM memory, flash memory, solid state disk, etc. The MCU <b>230</b> is configured to execute computer readable instructions stored in the memory <b>235</b> to perform the wired and/or wireless communications, such as the USB communication between the scanning device <b>110</b>, the formatting device <b>120</b>, and the end point terminal <b>130</b>, etc., and/or the Bluetooth communication between the formatting device <b>120</b>, the formatting device <b>121</b>, and/or the validation device <b>140</b>, etc. The MCU <b>230</b> is also configured to analyze the received encoded information from the scanning device <b>110</b> based on a set of classification rules, forwarding rules, and/or custom matching rules stored in the memory <b>235</b>. The memory <b>235</b> may store configuration information specific to the particular end point terminal model to which the formatting device <b>120</b> is connected.

For instance, there are many different POS terminal manufacturers that provide proprietary (i.e., non-standard) input/output (I/O) protocols for use with their individual POS terminal models. In addition, each manufacturer may have incompatible model lines and/or product types that may use different I/O protocols as well. Therefore, there may exist many different individual proprietary I/O protocols, each with its own proprietary message types, data formats, etc., that are incompatible with each other. Moreover, the formatting device <b>120</b> may be loaded with specialized configuration information to be executed by the MCU <b>230</b> for the one or more types of end point terminals that it may be connected to (either manually or through an automatic update from the validation device <b>140</b>). The type of end point terminal may be obtained either manually (i.e., a human operator may determine the end point terminal type and load the necessary configuration information into the formatting device and/or validation device), or an automatic discovery process may be executed by the formatting device <b>120</b> and/or validation device <b>140</b> in order to determine the compatible configuration information for use with the end point terminal(s) for that installation location (e.g., end point terminals <b>130</b> and <b>131</b>).

The formatting device <b>120</b> may also include a wireless transmitter <b>240</b>. The wireless transmitter <b>240</b> may be a transmitter/receiver configured to connect to various wireless networks, such as Bluetooth network, a wireless LAN network, a cellular network (e.g., CDMA, GSM, 4G LTE, etc.), a satellite network, etc. For example, the wireless transmitter <b>240</b> may be a Bluetooth low energy (BLE) transmitter/receiver capable of connecting to a Bluetooth PAN. The wireless transmitter <b>240</b> may connect to various hardware devices capable of connecting to the network associated with the encoded information validation system, such as the validation device <b>140</b>, other formatting devices (e.g., formatting device <b>121</b>) located within the wireless network's broadcast range (e.g., other formatting devices located in the same retail store, same airport, same office building, etc.). The wireless transmitter <b>240</b> may also connect to electronic displays configured to operate on the encoded information validation network, such as electronic signs, billboards, televisions, monitors, etc., and transmit multimedia content to the electronic displays (e.g., promotional information, advertisements, security warnings, real-time news, real-time weather, etc.) located within the wireless network's broadcast range. Further, the wireless transmitter <b>240</b> may also connect to mobile devices compatible with the encoded information validation network, such as smartphones, laptops, tablets, wearable devices, etc., in order to transmit and/or broadcast the multimedia content and/or personalized content (e.g., content personalized for the owner associated with the mobile device, such as personalized coupons, sales promotions, etc.) to the mobile device.

For example, the wireless transmitter <b>240</b> may act as a Bluetooth beacon for various mobile devices that have Bluetooth transmitters and are open to new Bluetooth connections and thereby transmit the multimedia content, personalized content, security alerts, real-time news, etc., to the mobile devices. Additionally, in certain example embodiments, the wireless transmitter <b>240</b> may connect to one or more scanning devices (e.g., scanning devices <b>110</b>, <b>111</b>) and/or end point terminals (e.g., end point terminals <b>130</b>, <b>131</b>) to transmit/receive the encoded information and messages related to the encoded information.

<figref idref="DRAWINGS">FIG. 3</figref> illustrates a block diagram for the software modules of the formatting device <b>120</b> according to at least one example embodiment. The memory <b>235</b> stores various computer readable instructions related to the example embodiments, such as instructions that cause the MCU <b>230</b> to execute a low resource operating system (OS). Moreover, the memory <b>235</b> stores software modules that cause the MCU <b>230</b> to form a stream manager <b>310</b>, a connection manager <b>320</b>, a classification engine <b>330</b>, a TCP/IP connection manager <b>340</b>, a stream processor <b>350</b>, a personal area network (or other network) manager <b>360</b>, and/or an event dispatcher <b>370</b>. Additionally, the memory <b>235</b> stores various device drivers related to the wired and wireless connections, such as, for example, a driver associated with the wireless connection (e.g., Bluetooth driver <b>380</b>), and/or a driver associated with the wired connection (e.g., USB Host driver <b>390</b> and USB Client driver <b>395</b>). The memory <b>235</b> may store additional device drivers to facilitate communication/interoperability with one or more scanning devices (e.g., scanning device <b>110</b>, <b>111</b>), one or more validation devices and/or local rules servers (e.g., validation device <b>140</b>), one or more formatting devices (e.g., formatting device <b>120</b>, <b>121</b>), and/or one or more end point terminals (e.g., end point terminal <b>130</b>, <b>131</b>). The additional device drivers may be included with and/or combined with the wired and/or wireless connection device drivers (e.g., the USB Host driver <b>390</b> may act as a device driver for the end point terminal driver, the USB Client driver <b>395</b> may act as a device driver for the scanning device, etc.).

For example, the computer readable instructions may include instructions related to an event dispatcher <b>370</b> that is configured to detect inbound encoded information (e.g., encoded information transmitted from the scanning device <b>110</b> to the end point terminal <b>130</b>) and communication events from the validation device <b>140</b>. If the event dispatcher <b>370</b> detects an inbound encoded information event, the event dispatcher may initiate the stream processor <b>350</b>, which is configured to intercept the inbound encoded information that was formatted using the scanning device/end point terminals native communication protocol, such as a binary data format that contains the information encoded in the encoded information. For example, the inbound encoded information may be formatted using a proprietary data format specific to the end point terminal <b>130</b>. The stream processor <b>350</b> then normalizes the inbound encoded information into a standard data packet format for use with the validation system (for example, the data packet format to be discussed in detail in connection with <figref idref="DRAWINGS">FIG. 7</figref>) as a data stream. In other words, the stream processor <b>350</b> will transform the inbound encoded information into a data stream compatible with the formatting device <b>120</b> and/or the validation device <b>140</b>. After normalizing the inbound encoded information into a data stream and/or standard data packet format, the stream processor <b>350</b> transfers the data stream to the classification engine <b>330</b>. The classification engine <b>330</b> then analyzes the data stream according to a set of classification rules stored in the memory <b>235</b> that classifies encoded information into one of a plurality of classification layers, or in other words, a classification type.

For example, the data stream may be analyzed by the classification engine <b>330</b> for particular attributes and/or characteristics, such as a desired string pattern, the formatting type of the encoded information (e.g., Codabar, Bar Code 2/5 interleaved, EAN 8, ISBN, ITF-14, SCC-14, UPC A, UPC E, GS1 Databar, QR code, etc.), the length of the encoded information, an embedded string sequence within a desired location of the encoded information (e.g., the last 8 bits of the encoded information), a desired image embedded in the data stream, etc. The data stream may be classified based on the results of the analysis. In the retail store context, the classification layers/types may include encoded information related to a print coupon, a one-time use coupon, an electronic coupon, a product package, a QR coupon, a coupon image, an image of a promotion, a gift card, a loyalty card, a club membership card, a subscriber card, etc., but is not limited thereto. In the identity verification context, the classification layers/types may include encoded information related to a barcode format associated with a state driver's license, a barcode format associated with a passport, an image of a social security card, an image of a birth certificate, RFID/NFC chip information including biometric information from an e-pas sport, etc. In the airport ticketing context, the classification layers/types may include encoded information related to a printed boarding pass, an electronic boarding pass, a barcode associated with a luggage claim ticket, a frequent flyer account, etc.

Once the classification layer of the data stream is determined, the stream manager <b>310</b> is initiated and applies a routing decision based on the classification layer of the data stream, a set of forwarding rules (e.g., matching rules), and/or custom matching rules stored in the memory <b>235</b>. The set of forwarding/matching rules determines the forwarding destination for each of the classification layer/types that the data stream may be classified under. There may be a set of forwarding/matching rules for each of the plurality of classification layers and/or a single set of forwarding/matching rules applied for all classification layers. For example, if the barcode is classified as a one-time-use barcode, it is forwarded (e.g., routed) to the validation device <b>140</b> for further processing. As another example, if the data stream is classified as a valid, but unknown barcode (e.g., the barcode is associated with certain loyalty card programs, membership programs, gift card programs, credit card accounts, financial accounts, etc., that do not require validation processing, etc.), then the data stream is immediately forwarded/routed to the POS terminal. The custom matching rules refer to rules related to custom encoded information, such as, for example, uniquely generated encoded information using the web service associated with the validation system discussed in further detail in connection with <figref idref="DRAWINGS">FIG. 5</figref>, that may not fall under one of the forwarding rules. Additionally, the stream manager <b>310</b> is configured to forward/route data streams directly to the end point terminal, such as end point terminal <b>130</b>, if the wired and/or wireless connection to the validation device <b>140</b> is not established, lost, times out, etc., as a failover and/or default state in order to ensure transparent, normal processing of encoded information by the pre-existing end point terminal system when there are issues with the encoded information validation system.

<figref idref="DRAWINGS">FIG. 4</figref> illustrates the hardware configuration of a validation device, such as validation device <b>140</b>, according to at least one example embodiment. In various example embodiments, the validation device <b>140</b> includes a housing <b>410</b>, a physical interface <b>420</b>, at least one processor <b>430</b>, a memory <b>435</b>, and a wireless transmitter <b>440</b>. The validation device <b>140</b> may additionally include an interface bridge <b>425</b>, a cellular transmitter <b>445</b>, a power module <b>450</b>, and a power interface <b>455</b>. While various elements of validation device <b>140</b> are illustrated in <figref idref="DRAWINGS">FIG. 4</figref>, the example embodiments are not limited thereto, and there may be a greater or lesser number of hardware elements in the validation device according to other example embodiments. For example, there may be additional non-transitory storage devices included in other example embodiments of the validation device, the wireless transmitter <b>440</b> and the cellular transmitter <b>445</b> may be combined and the like. Additionally, according to at least one example embodiment, the validation device <b>140</b> may be combined with the formatting device <b>120</b> and may be configured to serve as a master formatting device.

The housing <b>410</b> may be formed according to various form factors, particularly small form factors, such as a USB device form factor. The physical interface <b>420</b> is configured to physically connect the validation device <b>140</b> with other elements of the encoded information validation system, such as one or more formatting devices, such as the formatting devices <b>120</b> and <b>121</b>, and/or one or more end point terminals, such as end point terminal <b>130</b> and <b>131</b>. The physical interface <b>420</b> may be configured to be compatible with various interface protocols, such as the USB standard. When the physical interface <b>420</b> is physically connected to a formatting device, the validation device may transmit software to the formatting device, such as new and/or updated forwarding rules for the formatting device, new and/or updated custom matching rules for the formatting device, new and/or updated security policy information for the formatting device, new and/or updated encryption/decryption keys for the formatting device, firmware updates for the formatting device, configuration information related to a desired end point terminal system (e.g., configuration information related to the end point terminal that the formatting device is connected), etc. Additionally, the validation device may receive various data stored on the formatting device, such as information regarding the encoded information that was intercepted by the formatting device, operating status information regarding the formatting device, etc.

When the physical interface <b>420</b> is physically connected to an end point terminal, the validation device <b>140</b> may execute various auto-detection software routines to determine the model number of the end point terminal and to determine the appropriate configuration information related to the model number of the end point terminal. The auto-detection software routine is configured to determine the model number of the end point terminal by, for example, detecting metadata related to the end point terminal, initiating a communication session with the end point terminal (e.g., telnet session, etc.) and interrogating the end point terminal, determining the communication protocol used by the end point terminal, executing a series of specific commands related to various manufacturers and/or product lines to determine a positive response, etc. Additionally, the validation device <b>140</b> may be manually updated and/or configured using the physical interface <b>420</b> by attaching an external device (e.g., a USB thumb drive, an external hard drive, a PC, a laptop, a smartphone, a tablet, etc.) to the to the physical interface <b>420</b> and uploading the new software to the validation device <b>140</b>. The validation device <b>140</b> may also transmit/receive data and/or software updates over a wireless network, such as the wireless network associated with the wireless transmitter <b>440</b> and/or the cellular transmitter <b>445</b>.

The validation device <b>140</b> also includes at least one processor <b>430</b> and memory <b>435</b>. According to at least one example embodiment, the processor <b>430</b> and memory <b>435</b> may be combined into one unit, but is not limited thereto and may be separate units. The processor <b>430</b> is a processing device, such as a microcontroller, a central processing unit (CPU), an arithmetic logic unit (ALU), a digital signal processor, a microcomputer, a field programmable gate array (FPGA), a System-on-Chip (SoC), a programmable logic unit, a microprocessor, or any other device capable of responding to and executing instructions in a defined manner. The memory <b>435</b> may comprise one or more non-transitory computer storage media, such as one or more of ROM memory, RAM memory, flash memory, solid state disk, etc. The processor <b>430</b> is configured to execute computer readable instructions stored in the memory <b>435</b> to perform the wired and/or wireless communications, such as the Bluetooth communication between the formatting device <b>120</b>, the formatting device <b>121</b>, etc., and/or the cellular network communication between the validation device and one or more servers, such as a cloud server and/or platform server. The processor <b>430</b> is also configured to analyze the data stream transmitted by a formatting device (e.g., formatting device <b>120</b> and/or <b>121</b>) based on a set of validation rules stored in the memory <b>435</b>. Additionally, the memory <b>435</b> may store configuration information specific to the particular end point terminal model to which the formatting device associated with the validation device <b>140</b>, such as formatting devices <b>120</b> and <b>121</b>, are connected.

The validation device <b>140</b> may also include a wireless transmitter <b>440</b> and/or a cellular transmitter <b>445</b>. The wireless transmitter <b>440</b> may be a transmitter/receiver configured to connect to various wireless networks, such as Bluetooth network, a wireless LAN network, etc., and the cellular transmitter <b>445</b> may be a transmitter/receiver configured to connect to a cellular network (e.g., CDMA, GSM, 4G LTE, etc.), a satellite network, etc. The wireless transmitter <b>440</b> and the cellular transmitter <b>445</b> may also be combined according to various example embodiments. For example, the wireless transmitter <b>440</b> may be a Bluetooth low energy (BLE) transmitter/receiver capable of operating and/or connecting to a Bluetooth PAN. The wireless transmitter <b>440</b> may connect to various hardware devices capable of connecting to the network associated with the encoded information validation system, such as the one or more formatting devices (e.g., formatting devices <b>120</b> and <b>121</b>) located within the wireless network's broadcast range (e.g., formatting devices located in the same retail store, same airport, same office building, etc.). The wireless transmitter <b>440</b> may also connect to electronic displays configured to operate on the encoded information validation network, such as electronic signs, billboards, televisions, monitors, etc., and transmit multimedia content to the electronic displays (e.g., promotional information, advertisements, security warnings, real-time news, real-time weather, etc.) located within the wireless network's broadcast range. Further, the wireless transmitter <b>440</b> may also connect to mobile devices compatible with the encoded information validation network, such as smartphones, laptops, tablets, wearable devices, etc., in order to transmit and/or broadcast the multimedia content and/or personalized content (e.g., content personalized for the owner associated with the mobile device, such as personalized coupons, sales promotions, etc.) to the mobile device. For example, the wireless transmitter <b>440</b> may act as a Bluetooth beacon for various mobile devices that have Bluetooth transmitters and are open to new Bluetooth connections and thereby transmit the multimedia content, personalized content, security alerts, real-time news, etc., to the mobile devices.

The validation device <b>140</b> is configured to serve as a synchronization point for all formatting devices installed in a single physical location (e.g., a retail store, office building, airport, etc.). The validation device <b>140</b> may store in memory <b>435</b> information and/or data, such as logging information, software releases, factory installations, etc., related to the validation device itself and the formatting devices located within the same location. The validation device <b>140</b> may also include a power module <b>450</b> and a power interface <b>455</b> configured to provide external power to the validation device <b>140</b>.

<figref idref="DRAWINGS">FIG. 5</figref> illustrates a block diagram for the software modules of a validation device, such as validation device <b>140</b> according to at least one example embodiment. The memory <b>435</b> stores various computer readable instructions related to the example embodiments, such as instructions that cause the processor <b>430</b> to execute an operating system (OS) (not shown). Moreover, the memory <b>435</b> stores software modules that cause the processor <b>430</b> to form an event dispatcher <b>550</b>, a connection manager <b>520</b>, a TCP/IP connection manager <b>530</b>, a personal area network (or other network) manager <b>540</b>, a cellular network manager <b>541</b>, an encoder/decoder module <b>510</b>, a synchronizer <b>511</b>, a web services manager <b>512</b>, and/or a device client manager <b>513</b>. Additionally, the memory <b>435</b> stores various device drivers, such as, for example, a cellular transmitter driver <b>560</b>, a flash memory driver <b>561</b>, and Bluetooth driver <b>562</b>, etc.

For example, the computer readable instructions may include instructions related to an event dispatcher <b>550</b> that is configured to accept connections from authorized formatting devices over, for example, a Bluetooth connection or wireless LAN connection. The connection may be over a private network configured to support the encoded information validation system that may require secure authentication before a connection to the private network is established. The connection manager may be initiated and executed to initiate the private network and to execute the secure authentication scheme of the private network according to at least one example embodiment, but the example embodiments are not limited thereto. The event dispatcher <b>550</b> is also configured to detect incoming communications from the one or more formatting devices, such as transmitted data streams transmitted from the formatting devices to be validated by the validation device <b>140</b>. Once a data stream has been detected and received by the event dispatcher <b>550</b>, the processor <b>430</b> executes the computer readable instructions related to the encoded information algorithm module <b>510</b> that includes a plurality of sets of validation rules stored in memory <b>435</b> related to a plurality of encoded information sets. For example, in the retail store context, the memory <b>435</b> may include a set of validation rules associated with a plurality of products (e.g., specific validation rules related to desired UPC codes, barcodes, product packaging images, etc.), a plurality of manufacturer specific validation rules, a plurality of retailer specific validation rules (e.g., desired store locations that a particular encoded information is valid/invalid for, etc., time restriction rules, age restriction rules, etc.), validation rules related to one-time use coupons, validation rules related to uniquely generated encrypted coupons, validation rules related to images, etc.

The processor <b>430</b> then executes the encoder/decoder module <b>510</b> instructions to cause the processor <b>430</b> to form a tokenizer. The tokenizer processes the data stream and extracts any additional information embedded in the data stream associated with the original received encoded information. In at least one example embodiment, the tokenizer may extract information, such as an identifier, a name, a username, a transaction id, a serial number, a store id, an electronic signature, a security signature, a barcode, an address, a transaction amount, a discount amount, an expiration date, a time range for validity, special validity instructions, biometric information, seat number, gate number, flight number, etc., based on a pre-configured position of the data within the data stream.

Further, according to at least one example embodiment, the data stream may include encrypted embedded information that may be decrypted by the tokenizer. For example, the encrypted embedded information may be encrypted encoded information generated by a related cloud server (and/or other server, web platform, web service, etc.) using a public key associated with the validation device <b>140</b>. The encrypted encoded information may then be transmitted to a user who presents the encrypted encoded information to the scanning device <b>110</b>. Once scanned and/or received by the scanning device <b>110</b>, the encrypted encoded information may be decrypted by the tokenizer using a private key stored on the validation device <b>140</b>. As another example, the encrypted embedded information may have been encrypted using a digital signature stored on the cloud server (and/or other server, web platform, web service, etc.) that may be decrypted using a decryption algorithm stored on the validation device <b>140</b>. In at least one example embodiment, the encoded information being encrypted by, for example, the cloud server and/or web service platform, may represent unique information (e.g., biometric information, a unique identifier (such as a social security number, a currency note serial number, a credit card number, a bank account number, etc.), a one-time use coupon, a unique message, a unique special instruction, a unique and/or random computer generated number, a unique and/or random computer generated image, etc.).

Next, the processor <b>430</b> determines the validation state information regarding the encoded information embedded in the data stream (e.g., determine whether the encoded information is valid/invalid, accepted/rejected, authentic/counterfeit, etc.), and then modifies the data stream to include additional information such as the validation state information of the encoded information (e.g., the results of the validation processing), a text message regarding the validation status of the encoded information, and/or include textual instructions for the terminal operator (e.g., “process the encoded information manually,” “apply extra security measures,” “contact security,” “contact law enforcement,” etc.) to be displayed on a display device associated with the end point terminal, as well as additional tokenized information (e.g., the additional information extracted by the tokenizer function) related to the validation processing. Advantageously, the addition of the tokenized information to the data stream, i.e., the tokenization of the data stream, allows the data stream to be processed asynchronously. In other words, the tokenization of the data stream and the stored tokenized information allows the data stream to be processed by the validation system at any time, and the system is not dependent on the immediate, or time-constrained, completion of the validation process, and the tokenized data stream may be saved by the user/consumer/etc., electronically or on paper, and may be processed by the end point terminal <b>130</b> at any later point in time. The tokenizer may also encrypt the tokenized information and/or the modified data stream in accordance with an encryption algorithm. For example, in the security verification context, certain biometric information included in the encoded information may have been encrypted and the biometric information, along with the results of the validation of the biometric information, may be encrypted by the tokenizer in order to secure the information being validated from any potential hacking and/or other attack during the validation process. Next, the processor <b>430</b> then transmits the modified data stream to the originating formatting device using the wireless transmitter <b>440</b> and/or cellular transmitter <b>445</b>. After the formatting device receives the modified data stream, the formatting device forwards the modified data stream to the end point terminal connected to the formatting device.

Additionally, the encoded information may also relate to a non-binary determination state, such as a multi-use ticket/pass, money stored in a gift card, etc., and the state information will be updated based on the results of the validation determination (e.g., the multi-use ticket/pass will be decremented, the total amount stored on the gift card will be decremented, etc.). The encoded information (e.g., the unique identifier associated with the encoded information, a serial number associated with the encoded information, etc.), the validation results of the encoded information, and/or state information of the encoded information may be stored in a database table (not shown) in the memory <b>435</b>. The processor <b>430</b>, executing the computer readable instructions related to the synchronizer <b>511</b>, may transfer/synchronize in real-time, on demand, and/or on a periodic basis, some or all of the database table with the formatting devices associated with (e.g., paired with) the validation device <b>140</b>, other validation devices over the cellular network, and/or the one or more cloud servers/platform servers. For example, the validation device <b>140</b> may synchronize information regarding one-time use coupons with the formatting devices paired with the validation device <b>140</b>, other validation devices, and/or the cloud servers, in order to decrease and/or prevent the fraudulent use of one-time use coupons multiple times by automatically updating/synchronizing the state information of the identifier associated with the one-time use coupon with the formatting devices, validation devices, and/or servers. As another example, the validation device <b>140</b> may determine that a particular credit card number has been declined by the card's authorizing bank due to suspicious activity on the account, and may then synchronize the validation status of the credit card number with the formatting devices, validation devices, and/or servers. As a further example, a security officer may access the validation device <b>140</b> via the web service manager <b>512</b> connected to a cloud server and place a security flag on a desired person's identification information (e.g., driver's license number, social security number, unique identifier associated with the desired person's passport, etc.) and the validation device <b>140</b> may synchronize/update the validation status of the identification information associated with the desired person in the formatting devices and/or other validation devices.

The synchronizer <b>511</b> may also perform synchronization of information and/or algorithms associated with the encoder/decoder <b>510</b>, such as the encryption/decryption keys, encryption/decryption algorithms, encoding/decoding algorithms, etc., with the information and/or algorithms stored on the formatting devices paired with the validation device <b>140</b>, other validation devices, and/or the cloud servers. For example, if an encryption key and/or algorithm associated with a cloud server service is modified and/or updated (e.g., a time based aging of encryption keys), the synchronizer <b>511</b> may download the modified and/or updated encryption key and/or algorithm from the cloud server service, and may transfer the downloaded encryption key and/or algorithm to the formatting devices paired with the validation device <b>140</b>, other validation devices, or vice versa. Additionally, the synchronizer <b>511</b> may also perform similar synchronization of new and/or updated rules, new and/or updated security policy information, and/or firmware updates between the cloud server and the validation device <b>140</b>, the formatting devices paired with the validation device <b>140</b>, other validation devices, etc.

Further, the processor <b>430</b> may execute the web services manager <b>512</b> in order to enable web functionality for the validation device <b>140</b>. For example, validation information regarding desired encoded information may be created and/or updated by a user accessing the web service (e.g., through a cloud service and/or service platform), including creating new one-time use encoded information, creating/updating validation rules related to one or more encoded information (e.g., creating rules related to various restrictions placed on a particular set of encoded information, such as time restrictions on the use of the encoded information set, location restrictions on the use of the encoded information, frequency restrictions on the use of the encoded information, etc.), uploading new multimedia content (e.g., advertisement videos, textual advertisements, security warnings, real-time news, promotional information, coupons, etc.) to be broadcast by the validation device <b>140</b> and/or uploaded to electronic displays, mobile devices, etc., proximate to the validation device <b>140</b>, etc. Further, a user of the cloud service may also create unique encrypted coupons using a private key associated with the cloud service and/or the validation device, where the unique encrypted coupon may be transmitted to one or more customers and the information necessary to process the unique encrypted coupon, e.g., the validation information, validation rules, and/or decryption key, may be transmitted to the validation device <b>140</b> for use when the data stream indicates that the unique encrypted coupon has been intercepted by a formatting device associated with the validation device <b>140</b>.

<figref idref="DRAWINGS">FIG. 6</figref> is a flowchart diagram illustrating a method for validating encoded information according to at least one example embodiment. For the sake of clarity, a method related to the retail store/POS terminal context will be discussed, but the example embodiments are not limited thereto, and the operations of the method may be applied to other example embodiments, such as example embodiments related to the document verification context, security context, identity verification context, airport ticketing context, etc.

At operation <b>610</b>, an operator, such as a cashier, utilizes a scanning device <b>110</b>, such as a barcode reader, to scan, swipe, and/or otherwise receive a barcode <b>671</b>, i.e., the encoded information. Next, in operation <b>620</b>, the scanning device <b>110</b> transmits the scanned barcode <b>671</b> to the formatting device <b>120</b>. The formatting device <b>120</b> transforms and/or formats the scanned barcode <b>671</b> into a barcode data stream <b>672</b> compatible with the end point terminal <b>130</b> by decoding the information encoded in the barcode <b>671</b>. The data stream <b>672</b> includes the information originally stored in the barcode <b>671</b>, as well as additional information for use by the validation device <b>140</b>. For example, the information decoded from the scanned barcode <b>671</b> and stored in the barcode data stream <b>672</b> may be an alphanumeric text string “johndoe1120161234512345678912XYZ3#B”. The formatting device <b>120</b> then classifies the scanned barcode <b>671</b> into at least one classification layer (and/or classification type) of a plurality of classification layers based on attributes extracted from the scanned barcode <b>671</b> (e.g., a desired string pattern, the formatting type of the encoded information, the length of the encoded information, an embedded string sequence within a desired location of the encoded information, a desired image embedded in the data stream, and/or other design parameters that may be configurable by the manufacturer, system operator, client, user, etc.). In this example, the “#B” at the end of the data stream <b>672</b> text string may be a design parameter attribute that indicates that the data stream is to be classified in the one-time use coupon classification layer.

Next, at operation <b>630</b>, the formatting device <b>120</b> applies a plurality of matching rules or forwarding rules (e.g., matching rules <b>673</b>) stored on the formatting device <b>120</b> based on the classification layer of the data stream <b>672</b> to determine the destination of the data stream <b>672</b>. The matching or forwarding rules may be design parameters that are configurable by the manufacturer, system operator, client, user, etc., that may be based on the validation system configuration, the end point terminal system configuration, client/user demands, etc. In this example, if the formatting device <b>120</b> determines that the data stream <b>672</b> does not apply to any of the matching rules <b>673</b>, the formatting device <b>120</b> appends a null message to the data stream <b>672</b> and transmits the data stream <b>672</b> to the end point terminal <b>130</b> (operation <b>660</b>). If the formatting device <b>120</b> determines that the data stream <b>672</b> does apply to one or more of the matching rules <b>673</b>, at operation <b>640</b> the formatting device <b>120</b> will then forward the data stream <b>672</b> to the validation device <b>140</b>. However the example embodiments are not limited thereto, and the destination may be another element of the validation system.

At operation <b>650</b>, once the validation device <b>140</b> receives the data stream <b>672</b>, the validation device <b>140</b> analyzes the data stream <b>672</b> using a tokenizer and extracts any additional data embedded within the data stream <b>672</b> related to the original barcode <b>671</b>. For example, the additional data may be an identifier, a name, a username, a transaction id, a serial number, a store id, an electronic signature, a security signature, a barcode, an address, a transaction amount, a discount amount, an expiration date, usage policy for the encoded information, a time range for validity, special validity instructions, biometric information, seat number, gate number, flight number, etc., that is parsed from the data stream <b>672</b> by the tokenizer. The tokenized information may be stored in a database table, such as database table <b>675</b>, on the validation device <b>140</b>. The validation device <b>140</b> may also store validation transaction information related to the scanning of the encoded information <b>671</b> in a transaction database table <b>674</b> stored on the validation device <b>140</b>. The transaction database table <b>674</b> may include information such as the unique identifier for the formatting device <b>120</b> that transmitted the data stream <b>672</b> to the validation device <b>140</b>, the identifier associated with the data stream <b>672</b> (e.g., the alphanumeric string represented by the barcode <b>671</b>), the results of the validation of the data stream <b>672</b>, the time that the data stream <b>672</b> was scanned by the scanning device <b>610</b>, the classification layer of the data stream <b>672</b>, a link to the related database table entry in the tokenized information database <b>675</b>, information related to the store/location that the validation device is associated with, information regarding the product, service, operation associated with the validation operation (e.g., the name of the product being sold, the manufacturer of the product, etc.), and/or other data. Once the validation device <b>140</b> tokenizes the additional embedded information stored in the data stream <b>672</b>, the validation device <b>140</b> will apply validation rules to the data stream <b>672</b>, including any usage policies associated with the data stream <b>672</b>, such as time/date restrictions to the usage of the encoded information, one-time use restrictions, frequency of use restrictions, age restrictions, identification verification restrictions, store restrictions (e.g., coupons that may only be valid at desired store locations), location restrictions (e.g., geographical location restrictions), minimum/maximum discount amount restrictions, access restrictions (e.g., restrictions on the offices/floors/areas of a building that the user may have access to, restrictions to the computers, networks, files, equipment, etc. a user has access to, etc.), and the like, and determine a response based on the results of the validation determination. The validation device <b>140</b> will then modify the data stream <b>672</b> to include the determined response, such as the results of the validation determination, message regarding the validation status of the encoded information, and/or include instructions for the terminal operator (e.g., process the encoded information manually, apply extra security measures, contact security, contact law enforcement, etc.). In at least one example embodiment, the modification of the data stream <b>672</b> may include the validation device <b>140</b> initiating and executing the tokenizer to insert or append a desired and/or predetermined token into the data stream <b>672</b>, and then inserting and/or appending the determined response. The token is configured to act as a trigger for the end point terminal <b>130</b> and indicates that information, data, and/or messages related to the validation system is included in the modified data stream <b>672</b> and will cause the end point terminal <b>130</b> to analyze, process, and execute the modified data stream <b>672</b> accordingly. The validation device <b>140</b> will then transmit the modified data stream <b>672</b> to the formatting device <b>120</b>.

In operation <b>660</b>, the formatting device <b>120</b> transmits the data stream <b>672</b> to the appropriate end point terminal <b>130</b>. Once the data stream <b>672</b> is received by the end point terminal <b>130</b>, the data stream <b>672</b> is analyzed and processed. In at least one example embodiment, the contents of the original encoded information, the results of the validation determination, the message regarding the validation status, and/or instructions for end point terminal operator are extracted from the data stream <b>672</b>. For example, the original encoded information may be maintained as originally received by the scanning device <b>110</b>, and the results of the validation determination, message regarding the validation status, and the instructions for the operator may be encoded using the same barcode system that the end point terminal <b>130</b> is configured to use, such as the message barcoding system that many general purpose POS terminals use. In other example embodiments, the end point terminal <b>130</b> is installed with additional computer instructions that configure the end point terminal <b>130</b> to properly process the messages encoded the results of the validation determination, message regarding the validation status, and the instructions for the operator. Once the end point terminal extracts and processes the data stream <b>672</b>, the end point terminal may display on an included display device one or more messages regarding the validation status, instructions for the operator, such as “One-time use barcode already used,” “Accept Paper Coupon Manually,” “System Error, Barcode rejected,” “Contact Law Enforcement,” etc. The end point terminal also processes the results of the validation determination, and if the results of the validation determination indicate that the encoded information is valid, will then apply the original encoded information normally (e.g., apply the coupon discount to the item being purchased, grant access to the user to the building, venue, etc.).

<figref idref="DRAWINGS">FIG. 7</figref> is a block diagram of a message envelope for a data stream according to at least one example embodiment. As described above in connection to <figref idref="DRAWINGS">FIGS. 3 to 6</figref>, the formatting device <b>120</b> may transform a received encoded information into a data stream <b>700</b> that is compatible with the native communication protocol data format of the scanning device <b>110</b> and the end point terminal <b>130</b>, while still including additional information relevant to the validation system. The data stream <b>700</b> is formatted as a data message and includes a header section <b>710</b> that includes information to identify the data stream <b>700</b> as a validation system message, an original encoded information payload <b>720</b> that includes the original encoded information (e.g., the scanned barcode, etc.) in a format that complies with and/or is compatible with the native communication protocol data format of the scanning device <b>110</b> and the end point terminal <b>130</b>, thereby ensuring that the data stream <b>700</b> can be read by the end point terminal <b>130</b>. The data stream <b>700</b> also includes a validation system payload <b>730</b> that may include the validation determination results, additional tokenized information/additional embedded information, a message regarding the validation status of the encoded information, instructions for the terminal operator (e.g., process the encoded information manually, apply extra security measures, contact security, contact law enforcement, etc.), and/or additional metadata, etc. Additionally, according to some example embodiments, the data stream <b>700</b> may be packaged in an appropriate communication envelope, such as a TCP/IP envelope, etc., and/or based on an encoded information envelope, such as PDF 417 barcode, Code 128C barcode, etc., based on the communication protocol used between the formatting device <b>120</b>, the validation device <b>140</b>, and/or the cloud server/platform server.

<figref idref="DRAWINGS">FIGS. 8A to 8E</figref> are flowchart diagrams illustrating the transmission of messages between the elements of the validation system according to some example embodiments.

According to the example embodiment illustrated in <figref idref="DRAWINGS">FIG. 8A</figref>, in operation <b>810</b> a retail product's barcode is scanned by the barcode scanner <b>110</b> and is transmitted to the formatting device <b>120</b>. In operation <b>820</b>, the formatting device <b>120</b> analyzes the scanned barcode and determines that the barcode is unknown. The formatting device <b>120</b> then applies the appropriate classification layer to the barcode, transforms the barcode into a data stream envelope that includes the original barcode and then determines that the destination is the POS terminal <b>130</b> based on the forwarding rules. In some example embodiments, the formatting device <b>120</b> may also include a message indicating that the barcode is unknown, include a null character (or other special character or code) to indicate that the barcode is unknown, or include no message at all. In operation <b>830</b>, the POS terminal <b>130</b> receives the data stream and processes and/or applies the barcode normally, as if the barcode had been transmitted directly from the barcode scanner <b>110</b> to the POS terminal <b>130</b>.

According to another example embodiment illustrated in <figref idref="DRAWINGS">FIG. 8B</figref>, in operation <b>910</b>, the barcode scanner <b>110</b> may scan the barcode for a one-time use coupon and transmit the barcode to the formatting device <b>120</b>. In operation <b>920</b>, the formatting device <b>120</b> analyzes the scanned barcode and determines that the barcode is a one-time use coupon. The formatting device <b>120</b> then applies the appropriate classification layer to the barcode, transforms the barcode into a data stream envelope that includes the original barcode and at least a message indicating that the barcode is a one-time use coupon, and then determines that the destination is the validation device <b>140</b> based on the forwarding rules. If the destination is the validation device <b>140</b>, the formatting device <b>120</b> also determines whether the validation device <b>140</b> is operating correctly (e.g., whether the validation device <b>140</b> is receiving network transmissions). In operation <b>930</b>, the data stream is transmitted by the formatting device <b>120</b> to the validation device <b>140</b>. In operation <b>940</b>, the validation device <b>140</b> then checks the database table to determine whether the barcode is valid by applying such validation rules as, for example, determining whether the barcode associated with the one-time use coupon has been previously used, determining whether the store that the validation device is installed at is a valid participating store, determining whether the user presenting the one-time use coupon has been blacklisted, etc., and updates the database with the results of the validity determination. According to some example embodiments, the validation device may also detect the specific location (e.g., the location of the validation device and/or the formatting device that receives the encoded information, the location of a mobile device of the user (such as a user's smartphone or wearable device, etc.) that is used to transmit the encoded information to the validation system, etc.) that the encoded information is being validated and may validate the encoded information based on the validation location. For example, a one-time use coupon may be restricted to a single particular store location, a sporting event ticket may only provide access to a particular gate, a security badge may be restricted for use to a particular door, etc.

In operation <b>950</b>, the validation device <b>140</b> then modifies the data stream to include the results of the validation determination and additional messages, metadata, etc., and transmits the modified data stream to the formatting device <b>120</b>. In operation <b>960</b>, the formatting device <b>120</b> forwards the modified data stream to the POS terminal <b>130</b>, in this example including a message indicating that the one-time use coupon is valid. The POS terminal <b>130</b> then processes and/or applies the barcode normally, as if the barcode had been transmitted directly from the barcode scanner <b>110</b> to the POS terminal <b>130</b>.

According to another example embodiment illustrated in <figref idref="DRAWINGS">FIG. 8C</figref>, in operation <b>1010</b>, the barcode scanner <b>110</b> may scan the barcode for a one-time use coupon and transmit the barcode to the formatting device <b>120</b>. In operation <b>1020</b>, the formatting device <b>120</b> analyzes the scanned barcode and determines that the barcode is a one-time use coupon. The formatting device <b>120</b> then applies the appropriate classification layer to the barcode, transforms the barcode into a data stream envelope that includes the original barcode and at least a message indicating that the barcode is a one-time use coupon, and then determines that the destination is the validation device <b>140</b> based on the forwarding rules. If the destination is the validation device <b>140</b>, the formatting device <b>120</b> also determines whether the validation device <b>140</b> is operating correctly (e.g., whether the validation device <b>140</b> is receiving network transmissions). In operation <b>1030</b>, the data stream is transmitted by the formatting device <b>120</b> to the validation device <b>140</b>. In operation <b>1040</b>, the validation device <b>140</b> then checks the database table to determine whether the barcode is valid by applying such validation rules as, for example, determining whether the barcode associated with the one-time use coupon has been previously used, determining whether the store that the validation device is installed at is a valid participating store, determining whether the user presenting the one-time use coupon has been blacklisted, etc., and updates the database with the results of the validity determination. In operation <b>1050</b>, the validation device <b>140</b> then modifies the data stream to include the results of the validation determination and additional messages, metadata, etc., and transmits the modified data stream to the formatting device <b>120</b>. In operation <b>1060</b>, the formatting device <b>120</b> forwards the modified data stream, which in this example also includes a message indicating that the one-time use coupon is invalid, to the POS terminal <b>130</b>, which receives the data stream and displays the message indicating that the coupon is invalid and blocking the processing of the one-time use coupon.

According to another example embodiment illustrated in <figref idref="DRAWINGS">FIG. 8D</figref>, in operation <b>1110</b>, the barcode scanner <b>110</b> may scan the barcode for a one-time use coupon and transmit the barcode to the formatting device <b>120</b>. In operation <b>1120</b>, the formatting device <b>120</b> analyzes the scanned barcode and determines that the barcode is a one-time use coupon. The formatting device <b>120</b> then applies the appropriate classification layer to the barcode, transforms the barcode into a data stream envelope that includes the original barcode and at least a message indicating that the barcode is a one-time use coupon, and then determines that the destination is the validation device <b>140</b> based on the forwarding rules. If the destination is the validation device <b>140</b>, the formatting device <b>120</b> also determines whether the validation device <b>140</b> is operating correctly (e.g., whether the validation device <b>140</b> is receiving network transmissions). However, in this example, the formatting device <b>120</b> also determines that communication with the validation device <b>140</b> is not possible (e.g., due to the failure of the validation device, network issues, etc.), so therefore the appropriate destination is determined to be POS terminal <b>130</b>. The data stream is then modified to include an error message indicating that the validation device <b>140</b> is not operating correctly. In operation <b>1130</b>, the formatting device <b>120</b> forwards the data stream to the POS terminal <b>130</b> for processing and/or application of the one-time use barcode as normal, the POS terminal <b>130</b> also displaying to the operator the error message indicating that the validation device <b>140</b> is not operating correctly.

According to another example embodiment illustrated in <figref idref="DRAWINGS">FIG. 8E</figref>, in operation <b>1210</b>, the barcode scanner <b>110</b> scans the barcode for a paper coupon and transmits the barcode to the formatting device <b>120</b>. In operation <b>1220</b>, the formatting device <b>120</b> analyzes the scanned barcode and determines that the barcode is a paper coupon. The formatting device <b>120</b> then applies the appropriate classification layer to the barcode, transforms the barcode into a data stream envelope that includes the original barcode and at least a message indicating that the barcode is a paper coupon, and then determines that the destination is the validation device <b>140</b> based on the forwarding rules. If the destination is the validation device <b>140</b>, the formatting device <b>120</b> also determines whether the validation device <b>140</b> is operating correctly (e.g., whether the validation device <b>140</b> is receiving network transmissions). In operation <b>1230</b>, the data stream is transmitted by the formatting device <b>120</b> to the validation device <b>140</b>. In operation <b>1240</b>, the validation device <b>140</b> then checks the database table to determine whether the barcode is valid by applying such validation rules as, for example, determining whether the barcode associated with the one-time use coupon has been previously used, determining whether the store that the validation device is installed at is a valid participating store, determining whether the user presenting the one-time use coupon has been blacklisted, etc., and updates the database with the results of the validity determination. In this example, the validation device <b>140</b> determines that paper coupons are to be handled manually by the POS terminal operator. In operation <b>1250</b>, the validation device <b>140</b> then modifies the data stream to include the results of the validation determination and additional messages, metadata, etc., such as the operator instruction message indicating that the paper coupon must be handled manually, and transmits the modified data stream to the formatting device <b>120</b>. In operation <b>1260</b>, the formatting device <b>120</b> forwards the modified data stream, which in this example includes the instruction message indicating that the paper coupon must be handled manually by the POS terminal operator, to the POS terminal <b>130</b>. The POS terminal <b>130</b> then displays the instruction message to the operator.

The foregoing description has been provided for purposes of illustration and description. It is not intended to be exhaustive or to limit the disclosure. Individual elements or features of a particular example embodiment are generally not limited to that particular embodiment, but, where applicable, are interchangeable and can be used in a selected embodiment, even if not specifically shown or described. The same may also be varied in many ways. Such variations are not to be regarded as a departure from the disclosure, and all such modifications are intended to be included within the scope of the disclosure.