WO2019168782A1 - Système et procédé de gestion de la fonctionnalité d'étiquettes sans fil - Google Patents

Système et procédé de gestion de la fonctionnalité d'étiquettes sans fil Download PDF

Info

Publication number
WO2019168782A1
WO2019168782A1 PCT/US2019/019397 US2019019397W WO2019168782A1 WO 2019168782 A1 WO2019168782 A1 WO 2019168782A1 US 2019019397 W US2019019397 W US 2019019397W WO 2019168782 A1 WO2019168782 A1 WO 2019168782A1
Authority
WO
WIPO (PCT)
Prior art keywords
tag
enhanced
computing device
wireless tag
portable computing
Prior art date
Application number
PCT/US2019/019397
Other languages
English (en)
Inventor
Zvika Ashkenazi
Original Assignee
Thin Film Electronics Asa
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Thin Film Electronics Asa filed Critical Thin Film Electronics Asa
Publication of WO2019168782A1 publication Critical patent/WO2019168782A1/fr

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
    • G06Q20/32—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using wireless devices
    • G06Q20/327—Short range or proximity payments by means of M-devices
    • G06Q20/3278—RFID or NFC payments by means of M-devices
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/08—Payment architectures
    • G06Q20/12—Payment architectures specially adapted for electronic shopping systems
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/38—Payment protocols; Details thereof
    • G06Q20/387—Payment using discounts or coupons
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/80—Services using short range communication, e.g. near-field communication [NFC], radio-frequency identification [RFID] or low energy communication

Definitions

  • the present invention generally relates to the field(s) of managing interactions between users, wireless tags and mobile applications. More specifically, embodiments of the present invention pertain to computer-implemented methods for authenticating users and unlocking functions of wireless tags and related applications operating on mobile computing devices.
  • 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.
  • a brand owner may want only current, loyal customers with an installed merchant registered app on their mobile device to see certain information about a product to which a tag is attached.
  • Current tag tracking and management systems do not have any mechanism for hiding the functionality of a tag since the tag information is readily discernible to any tag reader application on a mobile device.
  • a merchant may want to reward customers who use an associated merchant application on a user's device, by granting them access to additional app functionality or content, including product promotional offers, coupons, etc. Typically this requires engaging the customer through a website or other channel to interact with the application.
  • Embodiments of the present invention include systems and methods of securing and unlocking functionality of a tag using a mobile application, and, conversely of unlocking functionality of content in a mobile application using a wireless tag.
  • One aspect of the disclosure is directed to a computer-implemented method for enabling secure communications between a mobile application executing on a portable computing device and a cloud-based server system, comprising associating a first wireless tag having a first identification code with a tag metadata stored at a cloud based server system; associating the first wireless tag with a secure communications key enabling secure communications between the mobile application and the cloud based server system, where preferably the secure communications key includes at least: a) a first component in the form of a resource locator comprising a first partial portion of the secure communications key, and b) a second component in the form of a payload for the mobile application and comprising a second partial portion of the secure communications key; registering the mobile application with the cloud-based server system; enabling push notifications to the registered mobile application from the cloud-based server system; reading the first wireless tag with the mobile application; communicating a tag payload for the first wireless tag to the cloud based server system; responding to the mobile application by communicating the first partial portion of the secure communications
  • the tag metadata is not included as part of the first wireless tag, but is useable by the mobile application to provide additional information to a user of the portable computing device about an article to which the first wireless tag is affixed.
  • the tag metadata acts as an access key useable by the mobile application to provide functionality to a user of the portable computing device within a restricted area of a mobile application.
  • the first wireless tag appears as a conventional tag with a standard payload to mobile applications that are not registered with the cloud-based server system.
  • the only content decodable by a conventional reader is a uniform resource locator (URL).
  • the second partial portion of the secure communications key is preferably dynamically generated and is adapted to expire at an end of a communications session through the separate second network channel. Further in preferred embodiments, the first partial portion of the secure communications key and the second partial portion of the secure communications key are sent in parallel at substantially the same time.
  • the first network channel is the Internet
  • the second network channel is a message-based network.
  • the first wireless tag is preferably a flexible electronic tag printed with an electronic ink, adapted to respond to a near-field-communications (NFC) interrogation signal, and formatted with non-alterable non-volatile memory data fields identifying at least a manufacturer ID and a product ID.
  • NFC near-field-communications
  • Still another aspect of the disclosure concerns a cloud computing system method for using a wireless tag to present enhanced content for a physical article through a secure channel to a portable computing device comprising: a) associating the first physical article with first enhanced content, where preferably the first enhanced content is configured to be presented within a graphical user interface (GUI) on the portable computing device for the first physical article; b) associating a first enhanced content wireless tag with the first physical article, which first enhanced content wireless tag is coded with a first tag identification code (TIC); c) processing a request from the portable computing device received over a first network for the first enhanced content, the processing including performing a first verification of the TIC presented by the portable computing device within a tag payload, and a second verification of the portable computing device as registered to receive first enhanced content for the first enhanced wireless tag identification code; d) generating and communicating a first partial portion of the first enhanced content to the portable communications device through the first network after the verifications; and e) generating and communicating a second partial portion of the first
  • the result is that the first enhanced content is communicated securely and in a form that permits the first enhanced content to be reconstructed by a mobile application and presented on a graphical user interface (GUI) of the portable electronic device.
  • GUI graphical user interface
  • a secure communications link is established between the portable computing device and the cloud computing system through a two-factor combination of content communicated through the first network and the second wireless network.
  • the enhanced content for the first enhanced content wireless tag can be presented on a case-by- case basis and only for selected users in selected locations based on the device registration information and user information.
  • 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;
  • 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
  • FIG. 2B is a diagram of an exemplary cloud-based Tag Mfr/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
  • 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
  • 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.
  • 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
  • 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
  • FIG. 5A is a diagram of an exemplary cloud-based system enabling an application to unlock enhanced tag data and/or app functions within a mobile computing device for an end user in accordance with the teachings of the present disclosure
  • FIG. 5B depicts an exemplary display on the GUI of a computer or a mobile device presenting an enhanced tag experience for a tagged item in accordance with embodiments of the present invention.
  • FIG. 6 is a flow chart showing an exemplary method for unlocking an enhanced tag data and/or app features experience for a tagged item in accordance with embodiments of the present invention.
  • 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.
  • the terms“coupled to,”“connected to,” and“in communication with” 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.
  • 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.
  • 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.
  • 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 SpeedTapTM and OpenSense.TM
  • 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).
  • PDPS printed doped polysilicon
  • FIG. 3A 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:
  • 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 any additional commands from a reader before transmitting its code, and for security reasons, preferably does not acknowledge/recognize any commands from the reader
  • 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.
  • TTF Tag-Talks-First
  • 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.
  • 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.
  • 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.
  • the 128 bit code 330 includes an 8-bit (l-byte)
  • Manufacturer ID field 332 consisting of a start bit and a 7-bit ID.
  • TTF Tag-Talks-First
  • 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.
  • 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.
  • tag identification codes are assigned to products in accordance with the teachings of application serial 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.
  • 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).
  • 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.
  • 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.
  • 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.
  • 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.).
  • 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.
  • 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.
  • 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 Mfr/Service Provider Computing Support systeml50 (shown in more detail in FIG.
  • 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.
  • tags can be managed by system 100 including wireless security tags (e.g., continuity sensing tag 135') a wireless identification tag 135, and other known types.
  • 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 PlatformTM or Amazon Web ServicesTM.
  • 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.
  • SaaS software as a service
  • the tag manufacturer (service provider) applications 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.
  • client devices such as the mobile device 120
  • program e.g., application
  • 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.
  • 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.
  • 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 manufacturers 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.
  • a tag 135 or 135' which can be in the form of a roll, sheet, etc.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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).
  • 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, 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.
  • 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
  • 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. 2A).
  • 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.
  • AR augmented reality
  • 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
  • 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.
  • 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.
  • 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/or M-tag).
  • 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.
  • 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.
  • product tag ID i.e. wool sweater
  • 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.
  • 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.
  • a customized CPU 122 for executing mobile applications
  • a memory 123 which may take different forms, including volatile DRAM/SRAM and non-volatile EEPROM
  • sensors 124 camera, microphone, touch, gyroscopic to name a few
  • UICC Universal
  • 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.
  • OS Operating System
  • IOS Internet
  • software applications l25c executing on the device and enabling different functions I/O and computational functions.
  • 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.
  • 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 provisions tag application l29e.
  • AR augmented reality
  • 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.
  • 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 provisions tag application l29e.
  • AR augmented reality
  • a tag A affixed to an article of clothing B may have a payload C that is readable by a generic reader application, and includes a simple URL D to a merchant site E that includes basic product marketing information F about the item.
  • the end user in this instance is thus provided a basic level or experience F from tag A.
  • a registered enhanced tag application on the user's device is configured to read the same tag A, and render additional information G (including promotional or marketing information) securely to an end-user from a tag service provider computing system complementing the merchant's native computing operations.
  • additional information G including promotional or marketing information
  • a merchant may want known existing customers to obtain additional promotional discounts when sampling products when they visit particular establishments at particular times.
  • a merchant may want to engage in a secure, two-factor authentication transaction with the end user.
  • These experiences can be controlled using the dynamic tag provisioning system disclosed herein.
  • a merchant may want to encourage potential customers to use an associated merchant application on a user's device. This functionality can be enabled by encouraging potential customers to interact with tags as a condition of unlocking additional enhanced application functions.
  • FIGs. 5 A - 5B are diagrams of an exemplary cloud-based system 1600 enabling an application to unlock secured enhanced tag data and/or app functions respectively within a mobile computing device for an end user in accordance with the teachings of the present disclosure.
  • an enhanced, secure tag experience is enabled by merchant related components in the front-end cloud computing system 110 that cooperate with requests from an application 522 executing on user devices 520.
  • an article of clothing 533 includes an associated tag 535.
  • Each tag includes a unique ID as explained above.
  • An application 522 on device 520 is activated and used to read the tag 535 using NFC with a tap gesture as further noted above.
  • the application 522 invokes an enhanced tag experience for the object, and then preferably communicates the details of the tap event 826a, including the tag payload (which may include a tag ID as well, along with object ID data) along with user identification (UID), app registration information and location information to tag engagement module 151 (FIG. 2B) in front-end cloud computing system 110 over network channel l05a.
  • tag engagement module 151 FIG. 2B
  • a first partial payload for the tag 826b is retrieved from db 159 (FIG. 2B) and returned to device 520 through IP channel l05a where it can be rendered on the user's device in accordance with parameters provided by a merchant computing system 160 (FIG.
  • the lst partial payload is simply a URL, and communicates nothing more than this basic information, which can be presented within a browser or app portion 527 of display 525.
  • this lst partial payload can also be derived from the tag payload but non-registered applications, but it does not provide any alterning or hint of additional functionality bound up in the tag.
  • the cloud computing system 110 then verifies if the application 522 is registered for push notifications, checks the tag ID to determine if it is valid as well, and, if so, pushes an additional 2nd portion of the tag payload 826c (which is preferably encrypted and generated dynamically) to device 520 over a second, separate channel l05b.
  • Application 522 then decrypts the second payload, and combines the two payloads to reconstruct an enhanced payload for the tag. This then permits additional functionality for the tag, which may include, for example, additional content or URLs that identify hidden information and offers for other products that are presented in another portion 528 of display 525. Other examples of enhanced tag functionality provisioning will be apparent to skilled artisans.
  • the 2nd payload and enhanced payload have a limited lifetime, and are treated as valid by cloud computing system 110 only during a single session.
  • the combination of two separate components, including the first partial payload and the second partial payload, constitute effectively a form of secure communications key between the user's device 520 and cloud computing system 110.
  • a webpage 527 for the tagged product is presented and supplemented with enhanced metadata 528 (in this instance, information on offers of related products) generated from reconstructing an enhanced tag payload from the two partial payloads received from different channels.
  • enhanced metadata 528 in this instance, information on offers of related products
  • the second portion of the payload is dynamic and only valid during the duration of the user's session.
  • the embodiment of FIG. 5A permits a form of secure messaging between the cloud computing system 110 and the user device 520, which is enabled through selected tags.
  • Those skilled in the art will appreciate that other components can be utilized in system 500 in accordance with the present teachings.
  • FIG. 5B shows a similar complementary use of system 500 in which an enhanced, secure application experience is enabled by NFC tags that unlock additional functionality in a user device. For example, it is possible to secure sections of a mobile application, and make them accessible only by unlocking them with a designated key.
  • an item 533 in this case, a bottle of beer
  • Each tag includes a unique ID as explained above.
  • An application 522 on device 520 is activated and used to read the tag 535 using NFC with a tap gesture as further noted above.
  • the application 522 invokes an enhanced application experience for the object, and then preferably communicates the details of the tap event 526a, including the tag payload (which may include a tag ID as well, along with object ID data) along with user identification (UID), app registration information and location information to tag engagement module 151 (FIG. 2B) in front-end cloud computing system 110 over network channel l05a.
  • tag engagement module 151 FIG. 2B
  • a first partial payload for the tag 526b is retrieved from db 159 (FIG. 2B) and returned to device 520 through IP channel l05a where it can be rendered on the user's device in accordance with parameters provided by a merchant computing system 160 (FIG.
  • the lst partial payload is simply a URL, and communicates nothing more than this basic information, which can be presented within a browser or app portion 527 of display 525.
  • this lst partial payload can also be derived from the tag payload by non-registered applications, but it does not provide any alterning or hint of additional functionality bound up in the tag.
  • the cloud computing system 110 then verifies if the application 522 is registered for push notifications, checks the tag ID to determine if it is valid as well, and, if so, pushes an additional 2nd portion of the tag payload 526c (which is preferably generated dynamically and encrypted) to device 520 over a second, separate channel l05b.
  • Application 522 then decrypts the second component, and combines the two payloads to reconstruct an enhanced payload for the tag. This then permits additional functionality (unlocks features) for application 522, which may include, for example, additional content or URLs that identify hidden information and offers for other products that are presented in another portion 528 of display 525.
  • additional functionality unlocks features
  • the 2d payload and enhanced payload have a limited lifetime, and are treated as valid by cloud computing system 110 only during a single session.
  • the combination of two separate components, including the first partial payload and the second partial payload, constitute effectively a form of secure communications key between the user's device 520 and cloud computing system 110.
  • a webpage 527 for the tagged product is presented and supplemented with enhanced metadata 528 (in this instance a coupon for the user for the beer product) generated from reconstructing an enhanced tag payload from the two partial payloads received from different channels. Similar benefits, such as loyalty points, or access to premium services may also be offered or included as part of the enhanced tag payload.
  • the second portion of the payload is preferably encrypted, dynamic and only valid during the duration of the user's session.
  • FIG. 6 is a flow chart showing an exemplary method 600 for unlocking an enhanced tag data and/or app features experience for a tagged item in accordance with embodiments of the present invention.
  • a user may elect to have his/her tag app and/or device registered at cloud system 110.
  • a user tap on a tag for an article is detected by device 520 in the manner described above in connection with FIGs. 3A-3F.
  • the tag id (included in some or all of payload 136) is then extracted and read at step 610.
  • the user id (which may be any one or more of a username, password, or application registration ID) and location data can also be derived from the application and device sensors (i.e.
  • a formal user enhanced tag request is then presented to cloud computing system 110 at step 620, which then determines at step 630, from available tag and uid databases (FIG. 2B, databases 157/158) if the request is valid. When these request parameters are invalid, the process simply terminates at step 625, by returning a reply to the user that there is no available data for the tag in question.
  • the Tag and UID information (which may include a device or application ID) are determined to be valid, a lst portion of the tag payload is returned through an IP based channel l05a back to the user's device. As seen in FIG.
  • this first component of the tag payload may be simply a URL to a merchant or tag service provider webpage with base product information.
  • context and rendering rules (FIG. 2C, modules 163/166) may be considered and processed as well for determining applicability of the lst tag payload to the particular user, device, time, location, etc.
  • cloud computing system 110 determines if the user's application and/or device is/are registered for push notifications. When the registration determination is negative, no further payload or tag information is presented to the user device and, at least for the tag in question, the session is deemed completed at step 645.
  • the second portion or component of the tag payload (which may or may not be encrypted) is returned to the user's device 620 through a separate network channel, which may be a cellular network.
  • the total tag payload based on the two separate payload components is then reconstructed at the user's device in accordance with any number of known techniques at step 655.
  • the second component of the tag may be encrypted according to a known encryption process, such that it can be decrypted with a private key on application 623.
  • additional metadata or content can be presented within the application, as seen in FIG. 5A.
  • step 665 the process flow proceeds to step 665, as seen in FIG. 5B.
  • the reconstructed app payload is used as a form of key to unlock any secured areas of application 622 controlled by a particular merchant/vendor associated with the tag 635 in question.
  • This form of engagement with end-users described above permits customization and enhancement of tags without requiring dedicated, fixed tag identification codes provided at a factory. Instead, tag functionality can be enhanced through a secure exchange by a mobile application with a cloud computing server. Similarly, content and functions of a mobile application can be unlocked through physical tags, and without requiring further engagement with the end-user with a merchant website or the like.
  • modules of the present invention 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.
  • a network such as the Internet
  • 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.
  • 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.

Landscapes

  • Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • Engineering & Computer Science (AREA)
  • Strategic Management (AREA)
  • Physics & Mathematics (AREA)
  • General Business, Economics & Management (AREA)
  • General Physics & Mathematics (AREA)
  • Theoretical Computer Science (AREA)
  • Finance (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

La présente invention concerne des étiquettes sans fil et des applications mobiles associées, qui comprennent une combinaison de fonctionnalité publique et cachée. Les caractéristiques cachées d'étiquette peuvent être déverrouillées au moyen d'une application mobile personnalisée se coordonnant avec un serveur par l'intermédiaire de deux canaux séparés. Réciproquement, des caractéristiques cachées d'une application mobile sont rendues accessibles par lecture d'étiquettes sans fil codées. La combinaison d'étiquette et d'application mobile permet d'obtenir une forme simplifiée et pratique d'authentification à deux facteurs.
PCT/US2019/019397 2018-02-27 2019-02-25 Système et procédé de gestion de la fonctionnalité d'étiquettes sans fil WO2019168782A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US201862635704P 2018-02-27 2018-02-27
US62/635,704 2018-02-27

Publications (1)

Publication Number Publication Date
WO2019168782A1 true WO2019168782A1 (fr) 2019-09-06

Family

ID=67805896

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2019/019397 WO2019168782A1 (fr) 2018-02-27 2019-02-25 Système et procédé de gestion de la fonctionnalité d'étiquettes sans fil

Country Status (1)

Country Link
WO (1) WO2019168782A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115630990A (zh) * 2022-08-18 2023-01-20 芯电智联(北京)科技有限公司 一种结合nfc防伪标签的积分系统

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20130124482A1 (en) * 2011-11-16 2013-05-16 General Electric Company Systems and methods for application reuse
US20130325594A1 (en) * 2012-06-05 2013-12-05 Yahoo! Inc. Sponsored applications
US20150019342A1 (en) * 2013-07-09 2015-01-15 Qualcomm Incorporated Real-time context aware recommendation engine based on a user internet of things environment
US20170351504A1 (en) * 2016-06-03 2017-12-07 Afero, Inc. Integrated development tool with preview functionality for an internet of things (iot) system

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20130124482A1 (en) * 2011-11-16 2013-05-16 General Electric Company Systems and methods for application reuse
US20130325594A1 (en) * 2012-06-05 2013-12-05 Yahoo! Inc. Sponsored applications
US20150019342A1 (en) * 2013-07-09 2015-01-15 Qualcomm Incorporated Real-time context aware recommendation engine based on a user internet of things environment
US20170351504A1 (en) * 2016-06-03 2017-12-07 Afero, Inc. Integrated development tool with preview functionality for an internet of things (iot) system

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115630990A (zh) * 2022-08-18 2023-01-20 芯电智联(北京)科技有限公司 一种结合nfc防伪标签的积分系统
CN115630990B (zh) * 2022-08-18 2023-06-06 芯电智联(北京)科技有限公司 一种结合nfc防伪标签的积分系统

Similar Documents

Publication Publication Date Title
US10546290B2 (en) Methods, systems, and computer readable media for provisioning and utilizing an aggregated soft card on a mobile device
US9947183B2 (en) Payment processing with automatic no-touch mode selection
US9378496B1 (en) System and method for providing contactless payment with a near field communications attachment
EP2947617A1 (fr) Dispositifs, systèmes et procédés de génération d'étiquettes lisibles par machine
US20140273857A1 (en) Systems and methods to secure short-range proximity signals
US20150081538A1 (en) Systems and methods for providing secure digital identification
US10026078B1 (en) System and method for accessing multiple accounts
WO2019232345A1 (fr) Système et procédé permettant de faire varier une fonction déclenchée par une communication en champ proche
KR101663168B1 (ko) 멀티 카드 생성 방법, 멀티 카드 사용 방법 및 멀티 카드 시스템
CN104584041A (zh) 信息提供方法、用于信息提供的移动终端和显示装置
US9985699B1 (en) NFC center
WO2019168780A9 (fr) Système et procédé permettant de fournir une expérience de réalité augmentée à des objets à l'aide d'étiquettes sans fil
KR20160145962A (ko) 역방향 nfc 결제를 위한 사용자 장치, nfc 결제 단말기, 그를 포함하는 역방향 nfc 결제 시스템, 그의 제어 방법 및 컴퓨터 프로그램이 기록된 기록매체
US20140258046A1 (en) Method for managing a transaction
CN114096981A (zh) 利用支付卡认证语音交易
WO2019168783A9 (fr) Système et procédé de transfert sécurisé de propriété d'étiquettes sans fil
WO2019168782A1 (fr) Système et procédé de gestion de la fonctionnalité d'étiquettes sans fil
Sabella NFC for Dummies
WO2019168785A1 (fr) Système et procédé de codage automatique d'étiquettes sans fil
KR102110274B1 (ko) 단말과 서비스 제공 장치, 그를 포함하는 전자 지갑 시스템, 그 제어 방법 및 컴퓨터 프로그램이 기록된 기록매체
Chugunov Near Field Communication Tag Management System: TagMan case study
KR102312352B1 (ko) 단말과 pos 단말, 그를 포함하는 전자 지갑 시스템, 그 제어 방법 및 컴퓨터 프로그램이 기록된 기록매체

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 19761080

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 22/01/2021)

122 Ep: pct application non-entry in european phase

Ref document number: 19761080

Country of ref document: EP

Kind code of ref document: A1