WO2019168785A1

WO2019168785A1 - System and method for automatically coding wireless tags

Info

Publication number: WO2019168785A1
Application number: PCT/US2019/019407
Authority: WO
Inventors: Zvika Ashkenazi; Karthik RAMKUNAR
Original assignee: Thin Film Electronics Asa
Priority date: 2018-02-27
Filing date: 2019-02-25
Publication date: 2019-09-06

Abstract

Wireless tag identification codes can be requested through a mobile application coordinating with a cloud service based tag management system. The codes are used to encode new tags to include readily accessible web content (such as URLs) associated with commercial product literature including marketing.

Description

SYSTEM AND METHOD FOR AUTOMATICALLY CODING WIRELESS TAGS

CROSS REFERENCE TO RELATED APPLICATION

[0001] This application claims the benefit of U.S. Provisional Pat. Appl. No.

62/635,714, filed on February 27, 2018, incorporated herein by reference as if fully set forth herein.

FIELD OF THE INVENTION

[0002] The present invention generally relates to the field(s) of managing generation of wireless tag identification codes. More specifically, embodiments of the present invention pertain to computer-implemented methods for securely requesting and procuring tag IDs for commercial products.

DISCUSSION OF THE BACKGROUND

[0003] Wireless near field communication (NFC) and radio frequency (RF) security and/or identification tags are used to digitally track and manage products by their manufacturers and distributors. Such wireless tags are often associated with a product by a manufacturer of the tag, and subsequently shipped to the manufacturer or distributor of the product. Wireless tags are sometimes shipped with a preexisting fixed physical tag identification code imprinted by a tag manufacturer that may or may not be extremely useful or useable to a merchant who intends to affix the tag to a commercial product. In other instances, tags may be reprogrammable, and include either a blank tag ID, or a tag ID that can be overwritten. The merchant may have a set of items that they want to associate with the tags in question, but cannot easily avail themselves of the existing tag ID. Existing technical solutions require enterprise level desktop computers and encoding devices to generate and write tag IDs. There is a need in the art, therefore, for a solution that provides merchants with the ability to create new tag IDs which can be mapped to an existing tag ID, or which can be used by an automated writer to imprint on blank tags, using more portable, lightweight computing tools.

[0004] This “Discussion of the Background” section is provided for background information only. The statements in this “Discussion of the Background” are not an admission that the any particular subject matter disclosed in this “Discussion of the Background” section constitutes prior art to the present disclosure, and excepting for those portions specifically identified as prior art no part of this“Discussion of the Background” section may be used as an admission that any part of this application, including this “Discussion of the Background” section, constitutes prior art to the present disclosure.

SUMMARY OF THE INVENTION

[0005] A main aspect of the invention concerns a system and method for making encoding of tags faster, more intuitive, and without the need for extensive/expensive support software. In embodiments of the invention, wireless tag identification codes are automatically generated at a cloud computing system for an end-user desiring a set of tag codes. Centralizing this function at a cloud computing system makes it easier to track and manage tags in all aspects of their lifecycle.

[0006] Another aspect of the disclosure concerns a computer-implemented method for managing wireless tags in a cloud computing system, the method comprising storing physical tag identification information at the cloud computing system for a first wireless tag, where preferably the physical tag identification information corresponds to a first physical wireless tag identification code embodied in a non-volatile memory within such tag; processing a request at the cloud computing system for a new virtual tag identification code for the first wireless tag, where preferably the request includes both a user identification code and the first physical wireless tag identification code and is presented by a portable application executing on a portable computing device; authenticating both the user identification code and the first physical wireless tag identification code at the cloud computing system; based on authenticating the user identification code and the first physical wireless tag identification code, generating a first virtual tag identification code for the first wireless tag responsive to the request; the first virtual tag identification code is preferably generated uniquely for a combination of the user identification code and the first physical wireless tag identification code; associating the first virtual tag identification code with the first physical wireless tag identification code at the cloud computing system; communicating the first virtual tag identification code to the portable application on the portable computing device; and encoding the first virtual tag identification code within the non-volatile memory within the first wireless tag using the portable application.

[0007] In some embodiments, multiple tags can be assigned the same first physical wireless tag identification code. In other applications, a requester can specify any number (N) of new unique virtual tag identification codes. The virtual tag identification codes are preferably generated randomly by the cloud computing system. Typically, the first virtual tag identification code corresponds directly to a uniform resource locator for a product landing page, but can include other content as well. In some instances, the first virtual tag identification code is mapped by the cloud computing system to a separate uniform resource locator for a product landing page in response to a read of the first wireless tag by a portable computing device. For some applications, the first physical wireless tag identification code is a unique serial number associated with the first wireless tag. To read and write the first virtual tag identification code, a wireless near field communications (NFC) device (which in some embodiments can be situated on the portable computing) is employed. The reading and writing are preferably performed during tap events, which occur when the portable computing device is placed in a physical proximity sufficient to establish near field communications with the first wireless tag. In preferred embodiments, the first augmented experience wireless tag comprises a flexible electronic tag printed with an electronic ink and is configured in a continuous, low power transmit mode to respond to a near-field- communications (NFC) interrogation signal.

[0008] A further aspect is directed to a computer-implemented method for managing wireless tags with a portable computing device, the method comprising reading a first wireless tag with a reader integrated within a first portable computing device to determine at least a first tag identification code in a first physical tap event; processing a new tag identification request initiated within a mobile application on the portable computing device for the first wireless tag; communicating and presenting the request to a cloud computing system for a new virtual tag identification code for the first wireless tag with the mobile application, where preferably the request includes both a user identification code and the first tag identification code; receiving the new virtual tag identification code at the portable computing device; and encoding the first virtual tag identification code within the non volatile memory within the first wireless tag using the portable application.

[0009] In some embodiments, the portable application further communicates both location information and vendor information for the request to be used by the cloud computing system in generating the new virtual tag identification code.

[0010] Another aspect of the disclosure concerns a computer-implemented method for managing wireless tags in a cloud computing system effectuated by a cloud computing system which performs the operations of storing physical tag identification information for a first wireless tag; the physical tag identification information preferably corresponds to a first physical wireless tag identification code embodied in a non-volatile memory within such tag; processing a request for a new virtual tag identification code for the first wireless tag received from a mobile application executing on a portable computing device, the request includes both a user identification code and the first physical wireless tag identification code; authenticating both the user identification code and the first physical wireless tag identification code; based on authenticating the user identification code and the first physical wireless tag identification code, generating a first virtual tag identification code for the first wireless tag responsive to the request, where preferably the first virtual tag identification code is generated uniquely for a combination of the user identification code and the first physical wireless tag identification code; associating the first virtual tag identification code with the first physical wireless tag identification code; and communicating the first virtual tag identification code to the portable application on the portable computing device.

[0011] Other aspects of the disclosure are directed to specialized devices, mobile computer programs, and customized hardware systems incorporate the above functionalities for creating new tag identification codes through portable devices.

[0012] These and other advantages of the present invention will become readily apparent from the detailed description of various embodiments below.

BRIEF DESCRIPTION OF THE DRAWINGS

[0013] FIG. 1 is a diagram of an exemplary cloud-based tag management system enabling a service provider to, among other functions, coordinate tag creation, tag transfers, tag transactions, tag product assignments, tag marketing, etc. for and between manufacturers, merchants and end users in accordance with the teachings of the present disclosure;

[0014] FIG. 2A is a diagram of an exemplary cloud-based Product

Manufacturing/Tag Computing Support system enabling a manufacturer to create and manage tags in connection with product manufacturing operations in accordance with the teachings of the present disclosure;

[0015] FIG. 2B is a diagram of an exemplary cloud-based Tag Manufacturer/Service

Provider Computing Support system enabling a tag service provider to manage and coordinate tags for manufacturers, merchants and end users in accordance with the teachings of the present disclosure; [0016] FIG. 2C is a diagram of an exemplary cloud-based Merchant Product/Tag

Computing Support system enabling a merchant to manage tags, products, etc. in connection with product marketing and sales operations in accordance with the teachings of the present disclosure;

[0017] FIGs. 3A - 3F are diagrams and flowcharts depicting the structure and operation of exemplary tags in accordance with one or more embodiments of the present invention;

[0018] FIG. 4A is a diagram of exemplary hardware and software employed in a mobile computing device implemented as a Tag User Computing Support system enabled with tag management functions in accordance with one or more embodiments of the present invention;

[0019] FIG. 4B depicts an exemplary graphical interface of a mobile computing device enabled with tag management functions in accordance with one or more embodiments of the present invention;

[0020] FIG. 5A is a diagram of an exemplary cloud-based system enabling generation of tag identifiers within a mobile computing device for an end user in accordance with the teachings of the present disclosure; and

[0021] FIG. 6 is a flow chart showing an exemplary method for generating and managing tag identification codes in accordance with embodiments of the present invention.

DETAILED DESCRIPTION

[0022] Reference will now be made in detail to various embodiments of the invention, examples of which are illustrated in the accompanying drawings. While the invention will be described in conjunction with the following preferred embodiments, it will be understood that the descriptions are not intended to limit the invention to these embodiments. On the contrary, the invention is intended to cover alternatives, modifications and equivalents reasonably understood by persons of ordinary skill in the art to be included within the spirit and scope of the invention. Furthermore, in the following detailed description, numerous specific details are set forth in order to provide a thorough understanding of the present invention. However, it will be readily apparent to one skilled in the art that the present invention may be practiced without these specific details. In other instances, well-known methods, procedures and components have not been described in detail so as not to unnecessarily obscure aspects of the present invention. Furthermore, it should be understood that the possible permutations and combinations described herein are not meant to limit the invention. Specifically, it will be understood by those skilled in the art that variations that are not inconsistent may be mixed and matched as desired.

[0023] In the context of this application, some additional guidance is provided for particular terms used herein to better appreciate the scope of the invention. As used herein the term“signal” refers to any known structure, construction, arrangement, technique, method and/or process for physically transferring data or information from one point to another. Unless indicated otherwise from the context of its use herein, the terms “information” and“data” may be used interchangeably, although each term is generally given its art-recognized meaning. Furthermore, unless indicated otherwise from the context of its use herein, the terms“coupled to,”“connected to,” and“in communication with” (and grammatical variations thereof) may be used interchangeably and indicate both direct and indirect couplings, connections and communications, but each term is also generally given its art-recognized meaning. Unless indicated otherwise from the context of its use herein, the terms“known,”“fixed,”“given,”“certain” and“predetermined” generally refer to a value, quantity, parameter, constraint, condition, state, process, procedure, method, practice, or combination thereof that is, in theory, variable, but is typically set in advance and not varied thereafter when in use.

[0024] The term "wireless tag" (or simply "tag") as used herein preferably refers to near-field communication (NFC), radio frequency (RF), high frequency (HF), very high frequency (VHF), or ultra high frequency (UHF) tags. The mobile or portable device may comprise a smart phone configured to communicate wirelessly with the wireless tags. The tags may be associated with a user account using a customized tag application on the mobile device.

[0025] In preferred embodiments described herein, the tags are of the NFC type manufactured by Thin Film Electronics ASA (TFEA) in printed integrated circuit (PIC) form (preferably made using TFEA's proprietary printed dopant polysilicon (PDPS) technology) under the tradenames SpeedTap™ and OpenSense.™ In a preferred embodiment, the wireless tags are manufactured using printed doped polysilicon (PDPS) technology (see, e.g., U.S. Pat. Nos. 7,314,513 [Attorney Docket No. IDR0302], 7,485,691 [Attorney Docket No. IDR0422], 8,846,507 [Attorney Docket No. IDR0884], 9,045,653 [Attorney Docket No. IDR1102], and 9,359,513 [Attorney Docket No. IDR1942], the relevant portions of which are incorporated herein by reference).

[0026] A circuit diagram identifying the main components of a preferred example of a tag 300 used in the present embodiments is shown in FIG. 3A. These tags preferably include the following general characteristics:

• Passive (no battery required)

• 13.56MHz operating frequency

• 128 or 256-bit Read-Only Memory (ROM) which is factory programmed and non- electrically modifiable (FIG. 3D).

• 106 Kb/s Data Transfer Rate Manchester bit encoding and OOK load modulation at 847 kHz

• Tag-Talks-First (TTF) Protocol/Mode, meaning the tag preferably transmits its code after it receives enough power from a reader field (FIG. 3E). The tag does not wait for or require and additional commands from a reader before transmitting its code, and for security reasons, preferably does not acknowledge/recognize any commands from the reader

• Adheres to Subset of ISO 14443 A

• 16 bits CRC for data integrity verification

• Operating Range of a Few Centimeters to enable Tap event detection (depends on field strength, antenna design, etc.)

• Single-tag mode for precise one-on-one interaction

[0027] Additional details may be found in datasheets published by TFEA for its tag products, including in materials identified as Thinfilm NFC Barcode Protocol for NFC OpenSense™ & NFC SpeedTap™ Tags available at the manufacturer's website as of the date of filing of this application and incorporated by reference herein.

[0028] As seen in FIGs. 3B, 3C and 3E, these types of tags preferably comply with the NFC Barcode protocol, a common NFC protocol supported by top-tier NFC controllers from NXP, Broadcom, Samsung, Sony, Toshiba, and others. The tags are preferably passive, l28-bit NFC tags operating at l3.56MHz and using a Tag-Talks-First (TTF) protocol. These types of NFC tags operate preferably in a read-only mode to transmit l28-bit codes to NFC- enabled devices, such as phones, tablets, PCs, and set-top boxes. Preferably, the data in the tags is also primarily stored in permanent, unalterable read-only memory but may in some embodiments include a number of reprogrammable dynamic bits to reflect the status of connected or integrated sensors and other information that could change over time. Because these types of tags do not receive information via RF, all data transmissions are unidirectional, from tag 300 to reader 310.

[0029] The NFC SpeedTap and NFC OpenSense tags also preferably store data following the NFC Barcode data formats (previously known as the Kovio NFC Barcode data formats). These are standardized representations of data so that operating systems and applications can consistently interpret the l28-bit data stream. An example of a memory map 330 preferably used by such tags is shown in FIG. 3D. As seen in FIG. 3D the tags preferably include dedicated fields for such parameters as a manufacturers ID field 332, a data format specifier field 334, a data payload field 336 and a CRC field 338.

[0030] In a preferred embodiment, the l28-bit code 330 includes an 8-bit (l-byte)

Manufacturer ID field 332 consisting of a start bit and a 7-bit ID. Under current standards, when implementing a Tag-Talks-First (TTF) format of an NFC Barcode, it is typically required that the first bit is set to‘1’ to serve as an identifiable start bit for an NFC controller that is attempting to read the tag. A 7-bit manufacturer ID (based on the least significant 7 bits of the manufacturer IDs specified in the ISO/IEC 7816-6 specification) follows the standard logical‘1’ start bit. An 8-bit (l-byte) data format identifier field 334 then describes how an NFC reader should interpret the contents of the payload field 336. The data format identifier preferably contains two sections: Reserved bits and a Data Type Format. In one preferred embodiment, the 3-bit Reserved section is set to‘000’ for a l28-bit NFC Barcode. A 5-bit Data Type Format allows for 32 possible data types. The data payload field 336 is preferably 96 bits, and may include separate components such as a tag ID 336a, an object/item ID 336b and a vendor ID 336c or some other convenient format for the application in question. The payload 336 can be used for any number of data purposes including for identifying a uniform resource locator (URL) having different formats, an electronic product code (EPC) or any other desired identification/metadata information. The CRC field 338 can be coded in accordance with any number of conventional specifications as needed to support a particular application. In preferred embodiments, described herein, the tag identification codes are assigned to products in accordance with the teachings of U.S. Pat. Application No. 15/904,178, also assigned to the present applicant, and hereby incorporated by reference. Again, it should be understood that other NFC Barcode data formats can be used in other applications, and as standards for tags evolve, it is expected that other variations will be employed in the future.

[0031] As seen in FIGs. 3B and 3C when placed proximate to such that it can communicate with an NFC compatible reader 310 (see FIG. 3B) the tag (initially in a sleep mode) transmits after a wake-up time (typically 5ms) in the presence of a sufficiently large interrogation field. As used herein, a "tap" or "tapping event" refers to the transmission of the NFC code by the tag when it is sufficiently close to be read by an NFC controller as may be embodied in a portable computing device (e.g. smartphone). Those skilled in the art will appreciate that the term "tap" in this instance does not require physical contact or bumping of the tag, but, rather, merely waving or placing the reader in close proximity to the tag. The distance range of detectable taps or tapping events can be adjusted of course, by altering field strength, reader antenna size and other physical/transmission parameters. As seen in FIGs. 3C and 3E, the tag continues, at a predetermined interval and standardized protocol, to re transmit the entire length as long as the NFC Barcode is powered up in the reader’s field. The transmission intervals are separated by sleep cycles, which timing periods are again predefined according to an operating standard used in the particular application.

[0032] In addition to other applications, wireless near field communication (NFC) and radio frequency (RF) security and/or identification tags can be used by manufacturers, distributors and other entities to digitally identify, track and manage products and other objects. The term "owned" in connection with a tag means generally that it is associated with a user account by the manufacturer of the tags before receipt by the user (e.g., a product manufacturer, distributor, reseller, packager, end user [consumer], etc.). The term "give away" refers to tags are not pre-associated with a user account, and may be associated with a user account by the user of the mobile device. Give-away tags may be given away at conferences or demonstrations or as samples, or may be sold as a commodity item.

[0033] The term "group" when used herein preferably refers to tags manufactured on a common roll or sheet, and/or which have at least some common manufacturing ID 332 (FIG. 3D) data, payload data 336, etc. It will be understood that in some embodiments, tags which have different physical tag ids 330 may nonetheless be logically associated to create groupings at different logical levels by the support software described herein.

[0034] Note that in the present disclosure, like numbered structures/steps in the drawings are intended to reference the same or substantially the same structure/step in counterpart drawings.

Tag Management System Architecture

[0035] FIG. 1 is a diagram of an exemplary cloud-based tag management system 100 enabling a service provider to, among other functions, coordinate tag creation, tag transfers, tag transactions, tag product assignments, tag marketing, etc. for and between manufacturers, merchants and end users in accordance with the teachings of the present disclosure. The tag management system 100 preferably includes a front-end cloud computer system 110 and a back-end cloud computing system 170 connected through a secure connection 114. The system 100 further preferably includes separate computing support systems for the different tag stakeholders, including a Product Manufacturing/Tag Computing Support system 140 (shown in more detail in FIG.2A) a Tag Manufacturer/Service Provider Computing Support systeml50 (shown in more detail in FIG. 2B) and a Merchant Product/Tag Computing Support system 160 (shown in more detail in FIG. 2C), all of which preferably include respective suitable portal application software to permit interfacing with their corresponding cloud support systems. It will be understood by those skilled in the art that the functionalities of each of these separate systems may be subsumed and/or integrated into the cloud environments 110/170 respectively in different applications. The tag management system further preferably comprises a tag user computing support system for end-users, including consumers, including one or more mobile devices 120 (or conventional PCs) executing a mobile tag manager application 125 (or web portal 126) and connected through both TCP/IP protocol network l05a (preferably the Internet) and a cellular network l05b. Various forms of tags can be managed by system 100 include wireless security tags (e.g., continuity sensing tag 135') a wireless identification tag 135, and other known types.

[0036] The cloud computing systems (110, 170) may provide shared computer processing resources and data to the other devices in the system, and may be implemented using a cloud computing service such as Google Cloud Platform™ or Amazon Web Services™. The computing systems (110, 170) may be implemented using a service model such as software as a service (SaaS). Some or all of the data may be accessed by authorized users, but is protected from access by unauthorized users.

[0037] In the SaaS service model, the tag manufacturer (service provider) applications (e.g., the mobile application 125 or portal application 126) may be partially executed using the cloud computer 110. The tag manufacturer applications are accessible from a support system 150, as well as through various client devices (such as the mobile device 120) through either a web browser or a program (e.g., application) interface. In a preferred embodiment, the various stakeholders, including tag manufacturer, product manufacturers, merchants (distributor, reseller) or end-users do not manage or control the underlying infrastructure in the cloud computer 110 or 170 including any network, servers, operating systems, and/or storage devices. As will be apparent to skilled artisans, FIG. 1 depicts only those components of system 100 critical to understanding the present teachings. Moreover, other components and software modules may be employed in system 100 consistent with the present teachings.

[0038] FIG. 2A is a diagram of an exemplary cloud-based tag manufacturing support system enabling a manufacturer to create and manage tags with a back-end cloud computing system for product manufacturing operations in accordance with the teachings of the present disclosure. System 170 is a back end cloud computing system that includes one or more computing servers 172, product database 178, tag database 179 and related software modules that support manufactures integrating tags with any type of product/object, such as apparel, consumables, household items, pharmaceuticals, or any other commercial article 137 on which a tag 135 or 135' (which can be in the form of a roll, sheet, etc.) can be affixed directly or as part of packaging during a manufacturing process. The product-tag support system further preferably comprises a host computing system 140 (e.g. a PC, smartphone, etc.), typically onsite at the product manufacturer facility, which system further includes a portal application (not shown, but which may take on any number of conventional forms) to permit communications with a cloud system 170, including a manufacturing administrative module 174, a manufacturing interface module 173, and various tag ID management applications in module 177. A manufacturer tag writer/application module 176 controls the application of tags to products/packaging during the manufacture of the articles of interest at a fabrication facility 175. The various software modules of FIG. 2A assist product manufacturers in managing the creation, application and tracking of products including tags.

[0039] A manufacturing admin module 174 provides visualization and configuration tools, including for enabling users to designate particular tag types/IDs for particular products. The tag IDs are provided by a tag manufacturer through an interface module 173 by a service provider, or, in some instances can be generated directly by a tag ID management module 177. Under either scenario, a product manufacturer can maintain separate databases of both tags (M-Tag 178) and products (M-Product 179). The type and form of the data in such databases may be specified in any convenient form most suitable for the manufacturer's particular operations, infrastructure, etc. Since it is conceivable that the same tag or product can be managed and tracked differently by different stakeholders using different data formats and logical identifiers, the nomenclature in FIG. 2A, i.e., M-Prod db 179 and M-Tag dB 178 denotes such distinction. The application of specific tag ids to specific products is controlled and monitored by a module 176 at the product manufacturing facility 175. In this manner, a product manufacturer can maintain an accurate inventory and record of tag/product pairings. This product/tag pairing data 176’ then be shared with other systems as desired, including through an API call or other known mechanisms known in the art. While shown as part of front-end cloud computing system 170, it will be appreciated by those skilled in the art that some or all portions of such modules, databases, interfaces, etc. in FIG. 2A can be implemented as part of host computing system 140 as well.

[0040] FIG. 2B is a diagram of an exemplary cloud-based tag service provider support system enabling a tag service provider to create, manage and coordinate tags for manufacturers, merchants and end users in accordance with the teachings of the present disclosure. A front-end cloud-computing system 110 is accessed by a tag manufacturing (and/or tag service provider) host system 150. As seen in FIG. 2A, tags 135 are manufactured in a tag fabrication facility 138 in the form of rolls, sheets, or other conventional forms. The tags are physically coded during manufacture in accordance with any number of tag identification code types and formats (see, e.g., FIG. 3, 336a, 336b, 336c). System 110 includes specified by a tag management module 156, which is a front-end cloud computing system that includes one or more computing servers 112, a tag ID (S-tag) database 158, a tag metadata database 159, a user identification code database 157, and related software modules that support tag creation support and management functions. The type and form of the data in such databases may be specified in any convenient form most suitable for the tag provider's particular operations, infrastructure, etc. As the tag IDs tracked by system 110 may be the same or have different physical IDs than those tracked by system 170, the tag IDs are designated with a (potentially) different dB index (i.e., S-tag as opposed to M-tag).

[0041] The tag manufacturer/provider system further preferably comprises a host computing system 150 (e.g. a PC, smartphone, etc.), typically onsite at the tag manufacturer facility, which system further includes a portal application (not shown, but which may take on any number of conventional forms) to permit communications with a cloud system 110, including a service administrative module 154, a manufacturing interface module 152 which communicates over a secure connection to back-end cloud system 170 and to a merchant support system 160 (FIG. 2C) and a tag management module 156 that comprises various tag ID management applications. A tag engagement module 151 interacts with and coordinates transactions with end-user systems such as seen in FIG. 2D, including through receipt and processing of tap events, user identification information, and related context data from user computing devices. Tag engagement module 151 further generates and provides any necessary responses from system 110 as described further below, including tag AR metadata, enhanced tag secure data, tag ownership transaction details and tag identification codes. The various software modules of FIG. 2D assist product manufacturers in managing the creation, application and tracking of products including tags. While shown as part of front-end cloud computing system 110, it will be appreciated by those skilled in the art that some or all portions of such modules, databases, interfaces, etc. in FIG. 2B can be implemented as part of host computing system 150 as well.

[0042] FIG. 2C is a diagram of an exemplary cloud-based tag merchant support system enabling a merchant to manage tags, products, etc. in connection with product marketing and sales operations in accordance with the teachings of the present disclosure. A front-end cloud-computing system 110 is accessible to a merchant product/tag host system

160. As seen in FIG. 2C, product/tag ID information 176' from one or more manufacturers can be input from a source including a back-end cloud computing system 170 (FIG. 2 A). In the example shown in FIG. 2C, the product is a consumable item (beer) 137, which has an affixed tag (integrated as part of the label). A merchant/vendor can customize additional content for the product, including multi-media data (video, audio, graphics, etc.) 138 which can be presented when the product tag is read as part of an augmented reality (AR) experience discussed further below.

[0043] System 160 includes a combination of hardware and software components that support merchant (retailer/distributor) product-tag marketing, promotions and sales operations, including one or more server computing machines 164, a host computing system

161, and associated databases containing content and index data for tags (R-Tag db 163), products (R-Product db 169), customers (R-Customer db 167) and customized content (R- Custom Content db 167). The type and form of the data in such databases for such entities may be specified in any convenient form most suitable for the merchant's particular operations, infrastructure, etc. System 160 also supports a merchant website 139, which can be configured with product/marketing/sales webpages in any number of styles known in the art and made accessible to web-enabled browsers (including on smartphones) through conventional uniform resource locators (URLs). Resources and control access to system 160 can also be made through secure applications executing on smartphones 16G and similar portable computing devices.

[0044] The tag manufacturer/provider system further preferably comprises a host computing system 161 (e.g. a PC, smartphone, etc.), typically onsite at the merchant facility, which system further includes a portal application (not shown, but which may take on any number of conventional forms) to permit communications with a cloud system 110. Merchant support system 160 further includes a number of software modules, including a merchant (retailer/distributor or R-tag) management module 165 that enables and supports tag creation, tag-product association, tag-content association, and related management/marketing functions attendant to the marketing, promotion and sales of products including physical tags. As the tag IDs tracked by system 160 may be the same or have different physical IDs than those tracked by systems 110/170, the tag IDs are designated with a (potentially) different dB index (i.e., R-Tag, as opposed to S-tag and M-tag).

[0045] System 160 may further include an AR Context Rules module 163 and AR

Device Rendering Logic module 166, which are responsible for identifying, selecting and presenting customized content to end-user devices 120 within a customized application 125 (see FIG. 1) or as part of a customized experience within a browser accessing website 139. In general, AR Context Rules module 163 dictates user, time, place, manner controls and filters, so that, for example, certain content may be presented for a designated product tag ID (i.e. wool sweater) only to selected users meeting certain criteria (i.e. new customers) at particular locations (i.e., designated partner store) at particular times (i.e. in fall months). All of such parameters can be extracted from the end-user's device 121, product tag 135 and other merchant customer information in db 167. Other examples of context controls will be apparent to those skilled in the art, and may be selected/customized on a tag-by-tag, or customer-to-customer basis. Providing similar support is AR Device Rendering Logic module 166, which is responsible for providing appropriate metadata in the right format for the particular desired AR experience on a target device. For example, a merchant may specify that a designated graphics overlay with particular dimensions should be made on a particular portion of a target device (i.e., model A smartphone by brand X). Again, any form of software tools and controls for overlaying, supplementing and augmenting existing media files (e.g., a graphical image captured by a phone) can be used for this module. While shown as a standalone system in FIG. 2C, it will be understood by skilled artisans that part or all of system 160 could be implemented by front end cloud computing system 110 and controlled/managed through portal applications with basic devices 161, 16G and the like.

[0046] FIG. 4A is a diagram of exemplary hardware and software employed in a mobile computing device 120 enabled with tag management functions in accordance with one or more embodiments of the present invention. The device 120 includes a customized CPU 122 for executing mobile applications, a memory 123 (which may take different forms, including volatile DRAM/SRAM and non-volatile EEPROM), a set of different types of sensors 124 (camera, microphone, touch, gyroscopic to name a few) for capturing different physical stimuli, a Universal Integrated Circuit Card (UICC) or SIM card 126 for communicating over a cellular channel (such as a carrier network 105), Bluetooth/GPS and WiFi communication circuits 127, and various I/O circuits, including display, speakers, etc. Most usefully, as concerns the present disclosure, a mobile computing device includes one or more Near Field Communication (NFC) support circuits, including an NFC communications IC l2la, an associated Secure Element l2lb and an NFC receive/transmit antenna l2lc. Device 120 further includes a number of firmware and software components, including an Operating System (OS) l25a (e.g., Android, IOS), a web/network software interface l25b (e.g., Safari, Chrome, etc.) for establishing communication sessions over an IP network channel l05a (e.g. Internet) and one or more software applications l25c executing on the device and enabling different functions I/O and computational functions.

[0047] For purposes of the present disclosure, user applications which are of most interest are shown in FIG. 4B which depicts an exemplary graphical interface of a mobile computing device enabled with tag management functions in accordance with one or more embodiments of the present invention. These applications generally include an augmented reality (AR) tagged Item application l29a, an enhanced tag/app application l29b, a tag transfer application l29c, an assign new tag application l29d, and a provision tag application l29e. It will be understood by skilled artisans that other hardware and software components may be included in embodiments of a mobile computing device 120 discussed herein.

Programmably Generating Tag Identifiers

[0048] As explained herein, tags may have preexisting stored physical identification codes that are assigned to or are owned by a particular entity, such that reading the tag yields a URL, pointer or other data that then maps to a particular webpage for a particular product and so on. Different stakeholders can thus control a user experience by assigning a particular physical ID to the tag which directly maps to a resource identified by an end-user's mobile application.

[0049] In instances where a tag has no existing ID, or is reprogrammable, it can be newly written with a new physical ID. The new ID can then direct an application to a resource in the same manner as above.

[0050] There may arise instances where a merchant requires additional tag identification codes for the purpose of physically programming new tags (i.e., a set of identification tags with a common ID to be affixed on a particular type of product, or for a set of identification codes with unique IDs to be affixed to unique products for example), or alternatively, assigning virtual tag identification codes to unalterable tags with preexisting physical codes. In other words, for the latter case, while the tag cannot be reprogrammed, a merchant may nonetheless want to logically map a physical ID through a cloud intermediary to another logical pointer that corresponds to a target resource. Both options permit a merchant to direct and control the user experience when the latter reads a tag with their mobile device.

[0051] FIG. 5A is a diagram of an exemplary cloud-based system 1200 enabling generation of tag identifiers within a mobile computing device for an end user in accordance with the teachings of the present disclosure. In a preferred embodiment, a first mobile device 520 invokes an application 522 within interface 525 to initiate a request for new tag identification codes. The end user in this instance may be a retailer, distributor, etc. who desires to write/imprint a target tag identification code on a set of reprogrammable tags 536 with a known NFC writer device 538 for packaging/affixing to a corresponding set of products (not shown). The tag identification codes may, among other things, contain URLs that point to particular merchant pages on a website 539.

[0052] The tag request 526a, including the number of tag ID(s) and other related context information, including user/device ID, location information, etc. can be sent along with the request to front end cloud computing system 110. Alternatively, the request can be initiated in response to the user tapping the tag(s) in question to read their existing identification codes, and associate new ID codes that are either physical (i.e., codes that are overwritten) or logical (i.e., codes that are appended to or mapped to by the existing code). The cloud computing system (specifically, a tag engine component of tag management module, FIG. 2B) then dynamically generates the desired tag IDs for the particular merchant. The tag IDs 526b are then returned to the application 522 where they can be coded to tags by a writer 538. The tags can then be assigned as desired to particular products as part of a marketing campaign for the merchant, with the resulting tag payloads returned at 526c to front end cloud computing system 110 where they can be encoded as part of tag-product db for the merchant. More preferably the tag identification codes are assigned to products in accordance with the teachings of U.S. Pat. Application No. 15/904,178, also assigned to the present applicant, and hereby incorporated by reference. Accordingly when the tag is later tapped and presented by an end-user to front end cloud computing system 110, the merchant's webpage(s) 539 can be returned as a response.

[0053] FIG. 6 is a flow chart showing an exemplary method 600 for generating tag identification codes for an end user in accordance with embodiments of the present invention. At step 602, an end-user merchant may elect to have their tag app and/or device registered at cloud system 110. As noted earlier, two different modes of adding tags are supported are available at step 601 for creating new tag ids, depending on whether the tag already includes an existing physical written ID or not. In a first mode (mode 1) associated with step 606 the user taps the tag(s) in question, and extracts a current physical tag ID at step 610. In a second mode (mode 2) the merchant simply requests identification code(s) for a set of tags at step 607.

[0054] At step 620, either or both of the extracted tag ID and user ID (which may be any one or more of a username, password, or application registration ID) are verified by checking a database at step 630, to determine for example if the user has a registered account. In the event the tag has an existing ID, the user is also checked to confirm they are a current known owner of the tag. Location data can also be derived from the application and device sensors (i.e. GPS and similar techniques). The tag and UID databases (FIG. 2B, databases 157/158) are consulted as part of step 630. When the tag has an existing owner not matching the requester, the request to generate a new ID is denied at step 625. [0055] When the tag ID generation request is validated the tag identification codes are generated at step 690, preferably using some form of randomization algorithm that creates unique codes. At step 696, if tag already includes a physical code, the additional generated code can either be mapped to such existing physical code, or appended thereto. When the tag does not already have a physical ID, it is registered and stored with the new ID at step 696. This new association between existing code and new code is then stored in a merchant tag database at step 631. When end-users select the tag in the future, the ID can be read and mapped to the appropriate tag/product/vendor record by decoding the new physically written ID or the combination of old ID and appended/mapped new ID.

[0056] The new tag IDs are then communicated at step 694, to application 622. They can then be written to the tags (when the latter reprogrammable) as new identification codes by writer 638 at step 698. Furthermore, as noted above, they can also be assigned or mapped to products as desired by the merchant in question.

[0057] It will be understood by those skilled in the art that the above descriptions are merely examples and that countless variations of the same can be implemented in accordance with the present teachings. A number of other conventional steps that would be included in a commercial application have been omitted, as well, to better emphasize the present teachings.

[0058] It will also be apparent to those skilled in the art that the modules of the present invention, including those illustrated in the figures can be implemented using any one of many known programming languages suitable for creating applications that can run on large scale computing systems, including servers connected to a network (such as the Internet) as part of a cloud computing system. The details of the specific implementation of the present invention will vary depending on the programming language(s) used to embody the above principles, and are not material to an understanding of the present invention. Furthermore, in some instances, a portion of the hardware and software will be contained locally to a user's computing system, which can include a portable machine or a computing machine at the user's premises, such as a personal computer, a PDA, digital video recorder, receiver, etc.

[0059] Furthermore, it will be apparent to those skilled in the art that this is not the entire set of software modules that can be used, or an exhaustive list of all operations executed by such modules. It is expected, in fact, that other features will be added by system operators in accordance with customer preferences and/or system performance requirements. Furthermore, while not explicitly shown or described herein, the details of the various software routines, executable code, etc., required to effectuate the functionality discussed above in such modules are not material to the present invention, and may be implemented in any number of ways known to those skilled in the art. Such code, routines, etc. may be stored in any number of forms of machine-readable media. It is understood that the protection afforded the present invention also comprehends and extends to embodiments different from those above, but which fall within the scope of the claims presented below.

Claims

CLAIMS What is claimed is:

1. A computer-implemented method for managing wireless tags in a cloud computing system, the method comprising:

storing physical tag identification information at the cloud computing system for a first wireless tag, wherein said physical tag identification information corresponds to a first physical wireless tag identification code in a non-volatile memory within such tag;

processing a request at the cloud computing system for a new virtual tag identification code for said first wireless tag, wherein said request includes a user identification code and said first physical wireless tag identification code and is presented by a portable application executing on a portable computing device;

authenticating said user identification code and said first physical wireless tag identification code at the cloud computing system;

generating a first virtual tag identification code for the first wireless tag responsive to said request based on authenticating said user identification code and said first physical wireless tag identification code, wherein said first virtual tag identification code is generated uniquely for a combination of said user identification code and said first physical wireless tag identification code;

associating said first virtual tag identification code with said first physical wireless tag identification code at the cloud computing system;

communicating said first virtual tag identification code to said portable application on said portable computing device; and

encoding said first virtual tag identification code within said non-volatile memory within said first wireless tag using said portable application.

2. The method of claim 1, wherein said first wireless tag is part of a group of wireless tags associated with the same first physical wireless tag identification code, and all of said first wireless tags in said group of wireless tags are assigned the same first virtual tag identification code.

3. The method of claim 1, wherein said portable application can specify any number (N) of new unique virtual tag identification codes.

4. The method of claim 1, wherein said first virtual tag identification code is generated randomly by the cloud computing system.

5. The method of claim 1, wherein said first virtual tag identification code corresponds directly to a uniform resource locator for a product landing page, which is presented in response to a read of said first wireless tag by a portable computing device.

6. The method of claim 1, wherein said first virtual tag identification code is mapped by the cloud computing system to a separate uniform resource locator for a product landing page in response to a read of said first wireless tag by a portable computing device.

7. The method of claim 1, wherein said first physical wireless tag identification code is a unique serial number associated with said first wireless tag.

8. The method of claim 1, wherein said portable application controls a wireless near field communications (NFC) writer on said portable computing for reading said physical tag identification information and writing said first virtual tag identification code.

9. The method of claim 8, wherein said reading and writing are performed during tap events, wherein said tap events occur when said portable computing device is placed in a physical proximity sufficient to establish near field communications with said first wireless tag.

10. The method of claim 1, wherein said first augmented experience wireless tag comprises a flexible electronic tag printed with an electronic ink.

11. The method of claim 1, wherein said first augmented experience wireless tag is adapted to respond to a near-field-communications (NFC) interrogation signal.

12. The method of claim 1, wherein the first augmented experience wireless tag is configured in a continuous, low power transmit mode.

13. A computer-implemented method for managing wireless tags with a portable computing device, the method comprising:

reading a first wireless tag with a reader integrated within a first portable computing device to determine at least a first tag identification code in a first physical tap event;

processing a new tag identification request initiated within a mobile application on the portable computing device for said first wireless tag;

communicating and presenting said request to a cloud computing system for a new virtual tag identification code for said first wireless tag with the mobile application, wherein said request includes a user identification code and said first tag identification code;

receiving said new virtual tag identification code at said portable computing device; and encoding said first virtual tag identification code within said non-volatile memory within said first wireless tag using said portable application.

14. The method of claim 13, wherein said portable application can specify any number (N) of new unique virtual tag identification codes.

15. The method of claim 13, wherein said portable application further communicates location information and vendor information for said request to be used by the cloud computing system in generating said new virtual tag identification code.

16. The method of claim 1, wherein said portable application controls a wireless near field communications (NFC) writer on said portable computing for reading said physical tag identification information and writing said first virtual tag identification code.

17. The method of claim 15, wherein said reading and writing are performed during tap events, wherein said tap events occur when said portable computing device is placed in a physical proximity sufficient to establish near field communications with said first wireless tag.

18. A computer-implemented method for managing wireless tags in a cloud computing system, the method comprising:

storing physical tag identification information for a first wireless tag, wherein said physical tag identification information corresponds to a first physical wireless tag identification code embodied in a non-volatile memory within such tag;

processing a request for a new virtual tag identification code for said first wireless tag received from a mobile application executing on a portable computing device, wherein said request includes a user identification code and said first physical wireless tag identification code;

authenticating said user identification code and said first physical wireless tag identification code;

associating said first virtual tag identification code with said first physical wireless tag identification code; and communicating said first virtual tag identification code to said portable application on said portable computing device.

19. A computing system configured for managing wireless tags in a cloud computing system comprising:

one or more software modules adapted to execute on a portable computing device and/or a cloud-based server system and perform at least the following functions:

storing physical tag identification information at the cloud computing system for a first wireless tag, wherein said physical tag identification information corresponds to a first physical wireless tag identification code embodied in a non volatile memory within such tag;

encode said first virtual tag identification code within said non-volatile memory within said first wireless tag using said portable application.

20. A computer program having executable instructions stored on a non-transitory machine-readable medium on a portable computing device adapted to facilitate creation of identification codes for wireless tags, the computer program comprising:

one or more software modules adapted to execute on the portable computing system and perform at least the following functions: reading a first wireless tag with a reader integrated within the first portable computing device to determine at least a first tag identification code in a first physical tap event;

processing a new tag identification request initiated within a graphical interface on the portable computing device for said first wireless tag;

communicating and presenting said request to a cloud computing system for a new virtual tag identification code for said first wireless tag, wherein said request includes a user identification code and said first tag identification code;

receiving said new virtual tag identification code; and

encoding said first virtual tag identification code within said non-volatile memory within said first wireless tag using a writer.

21. A cloud computing system configured to manage wireless tags comprising:

one or more software modules adapted to execute on computing hardware of the cloud computing system and perform at least the following functions:

associating said first virtual tag identification code with said first physical wireless tag identification code; and

communicating said first virtual tag identification code to said portable application on said portable computing device.