Systems, methods, and computer-accessible media for inhibiting or turning off digital tag reading

Abstract

Exemplary systems, methods, and computer-accessible media may include, for example, storing a digital tag on a first device, the tag configured to be associated with at least one application on the second device, such that receipt of the tag at the second device launches the application on the second device; and transmitting the digital tag from the first device to the second device, the application on the second device configured to launch in a special state when the second device is in at least one state from a predetermined list of states.

Description

[Technical Field]

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS This application claims priority to U.S. Patent Application No. 16 / 806,702, filed March 2, 2020, the disclosure of which is incorporated herein by reference in its entirety.

[0002] Field of Disclosure The present disclosure generally relates to inhibiting or turning off the reading of digital tags, such as NFC tags, by user devices such as smartphones (e.g., iPhone® or Android® phones). [Background technology]

[0003] Near-field communication (NFC)-enabled devices, such as smart cards and other devices, have become ubiquitous and continue to grow in popularity. Similarly, smartphones have become increasingly popular in recent years. Data contained on an NFC-enabled smart card can be read by bringing the NFC range close enough to an NFC smart card. This powers the smart card's NFC components, allowing information to be read from the smart card. Many smart cards are configured to allow an appropriate receiving device to access the encoded information. This can lead to security issues, especially in the context of mobile devices that can read data from contactless chips. For example, a mobile device configured with an NFC reader can read credit card information from the card chip. This allows the mobile device to read the card's information whenever the credit card is within the mobile device's NFC range.

[0004] Certain operating systems are configured to continuously operate an NFC range for a smartphone or other device, allowing the smartphone to read an NFC smart card brought into proximity. By way of example, devices running the Android® operating system by Google® are configured to always have an active NFC range. This can result in an NFC-enabled smart card being unintentionally read when the smart card is brought into proximity. For example, if an NFC-enabled card is placed in a user's pocket or an adhesive wallet is used to store the card by attaching it to the back of the mobile phone, the smart card can be read by a device not intended by the user to read information contained on the smartphone or other device.

[0005] In other cases, the smartphone may launch an application or perform other actions in response to receiving an NFC tag. This can be counter to a smooth user experience when using a smartphone, as users may not want to inadvertently tap their smart card to launch an application. When carried by a user, proximity (such as to a user's wallet) can result in multiple NFC tags being read, multiple applications being launched, or actions being performed without the user's consent. At the same time, users may find it convenient to use NFC-enabled smartphones and devices and may not want to disable the NFC functionality on their devices.

[0006] In still other cases, a counter on an NFC-enabled smart card may be incremented each time the smart card is read. However, the counter does not necessarily correspond to an independent counter maintained by the smart card's issuer. The reason for this difference in correspondence is, for example, that a counter on the smart card may be incremented each time the smart card is read, but the content or information read from the smart card may not be transmitted to the smart card's issuer. This difference can create security issues if the two counters are not synchronized. Therefore, there is a need to keep counters on NFC-enabled smart cards synchronized without disabling the smart card's NFC functionality.

[0007] Conventional methods related to NFC and the Near Field Communication Data Exchange Format (NDEF) are limited in that they do not allow users to launch applications via NFC tag functionality, prevent unintended launch, and / or toggle functionality on, for example, an NFC smart card. These, among other deficiencies, exist. Therefore, it would be beneficial to provide exemplary systems, methods, and computer-accessible media for selectively inhibiting or turning off NFC tag reading by a smartphone. It would further be beneficial to provide exemplary systems, methods, and computer-accessible media for toggling application launch in response to an NFC tag being read by a smartphone, or the ability to inhibit or turn off reading. Furthermore, it would be beneficial to provide exemplary systems, methods, and computer-accessible media that can synchronize (and / or maintain synchronization) a counter on a smart card and the smart card's issuer. Summary of the Invention

[0008] Embodiments of the present disclosure provide systems, methods, and computer-accessible media, which may include, for example, storing a digital tag on a first device, the tag configured to be associated with at least one application on a second device, causing an application on the second device to launch upon receipt of the tag at the second device, transmitting the digital tag from the first device to the second device, and the application on the second device configured to launch in a special state when the second device is in at least one state from a predetermined list of states.

[0009] Embodiments of the present disclosure provide systems, methods, and computer-accessible media that may further include, for example, receiving digital information from a first device upon physical proximity to the first device; receiving a digital tag from the first device configured to be associated with an application; launching the application associated with the received digital tag in response to the tag; and intercepting additional digital information from the first device via the application for a period of time after receipt of the digital tag when the computer hardware apparatus is in at least one state from a predetermined list of states.

[0010] Embodiments of the present disclosure provide systems, methods, and computer-accessible media, which may further include, for example, transmitting a digital tag from the first device, the tag configured to be in a Near Field Communication Data Exchange Format Specification, further configured to be an Android® Application Record Activation Tag, and further configured to be associated with at least one application of the second device to activate the application upon receiving the tag at the second device, the application configured to intercept additional information transmitted from the first device within a certain period of time when the second device is in at least one state from a predetermined state list.

[0011] Further features of the disclosed design and advantages offered thereby are described in more detail below with reference to specific exemplary embodiments that are illustrated in the accompanying drawings. [Brief explanation of the drawings]

[0012] [Figure 1] FIG. 2 illustrates a first device according to an exemplary embodiment of the present disclosure. [Figure 2] FIG. 1 illustrates a user device according to an exemplary embodiment of the present disclosure. [Figure 3] 1 is a flow diagram of a method for launching an application on a device according to an exemplary embodiment of the present disclosure. [Figure 4] FIG. 1 is a flow diagram of a method for launching an application and synchronizing counters on a device according to an exemplary embodiment of the present disclosure. [Figure 5] FIG. 1 is a flow diagram of a method for launching an application and synchronizing counters on a device according to an exemplary embodiment of the present disclosure. [Figure 6] FIG. 2 is a flow diagram of a method for modifying a digital tag of a smart card according to an exemplary embodiment of the present disclosure. [Figure 7] FIG. 1 is a block diagram of an exemplary system according to an exemplary embodiment of the present disclosure. DETAILED DESCRIPTION OF THE INVENTION

[0013] The following description of the embodiments provides non-limiting representative examples that refer to numerals to particularly explain the features and teachings of different aspects of the present invention. It should be recognized from the description of the embodiments that the described embodiments can be implemented separately or in combination with other embodiments. Those skilled in the art who review the description of the embodiments should be able to learn and understand the different described aspects of the present invention. The description of the embodiments should facilitate understanding of the present invention to the extent that other implementations not specifically covered but within the knowledge of those skilled in the art who read the description of the embodiments will be understood to be consistent with the application of the present invention.

[0014] For example, exemplary systems, methods, and computer-accessible media may be provided that can facilitate device blocking or inhibition of reading of information contained on a smart card by a computer or smartphone. The smartphone may be an Android® phone, although any smartphone having the functionality described in this disclosure is within the scope of the present invention.

[0015] A smart card may be, for example, an identity card that can be read by a mobile device. For example, information encoded on a user's smart card may be read by a mobile device or other similar device when the smart card is physically near the device. Often, smart cards are encoded to provide digital information to the device without configuration. Thus, the information on the card can be read by any software installed on the digital device. However, a smart card may be encoded to include, for example, a digital tag. When the smart card is near the device, the digital tag may first be read by the mobile device. Typically, receiving the digital tag automatically launches an application identified by the digital tag or configured to be associated with the payload in the digital tag.

[0016] A digital tag may be configured, when read by a mobile device, to first launch an application identified by the digital tag. The application is typically launched in response to receiving the digital tag. Additionally, if desired, the digital tag may be configured to download and install an application on the mobile device before launching the application. In some examples, the digital tag may be configured to cause the mobile device to launch an application store associated with the operating system running on the mobile device (e.g., Google® Play Store for Android® devices) to facilitate the download and installation of the application.

[0017] In some examples, the mobile device may continuously monitor for receipt of a digital tag at the mobile device. The mobile device may further include a background service that may continuously monitor or obtain information regarding the state of the mobile device. In some examples, the background service may be part of an application identified by the digital tag. When the mobile device receives the digital tag, in combination with information regarding the state of the mobile device collected by the background service (e.g., whether the screen is on, whether the device is locked / unlocked, whether power saving is on / off, which applications are running, which tasks are pending completion, whether the communication interface is on / off, whether the device is waiting for user input, whether the processor is operating above or below a certain level, whether the battery is above or below a certain level, or if the target application is already launched or engaged in a task), the mobile device may invisibly launch the application associated with the digital tag. For example, if the digital tag is read within a threshold time (e.g., within 100 milliseconds, within 200 milliseconds, or within 400 milliseconds) after the mobile device screen is unlocked, the monitoring application may determine this to be an inadvertent read, and the application is not launched. An inadvertent reading of a digital tag can occur for many reasons, including but not limited to proximity to a transmitting device or activation of the mobile device's radio receiver when its screen is unlocked by the user.

[0018] Additionally, if the mobile device detects another tap or receipt of the same digital tag within a predetermined time, the mobile device may visibly launch the application associated with the digital tag for the user to interact with. Additionally, if the application is launched invisibly in response to receiving the digital tag, the mobile device may read additional information from a multi-tag manifest stored on the smart card and send such tag payloads to the web service. If there are no additional reads of the digital tag within a predetermined time, the application may terminate without the device user seeing the interface.

[0019] The application may be configured to write, automatically or based on user input or settings, to an applet located on a smart card that is compliant with JavaCard® or other smart card operating systems. Typically, the applet on the smart card generates an NFC-compatible tag, such as an NDEF tag, whenever the smart card receives power from within range of a smartphone. Thus, the application may toggle the smart card's capabilities to turn off NFC tag creation, or modify the smart card so the user can select whether to enable or disable the smart card's NFC capabilities.

[0020] The launched application may be configured, for example, to prevent other applications on the smartphone device from accessing the requested information. The application associated with the digital tag may be installed on the device by a user. The tag may be generated in the NDEF data format specification. The NDEF tag may be further configured as an Android® Application Record (AAR) launch tag.

[0021] The application associated with the digital tag may be further configured to perform various functions. For example, the application may send a notification to the user if the application is launched more than a predetermined number of times within a predetermined period of time. The application may also create a list of other applications installed on the device. Other functions typically associated with applications on operating systems, such as applications on the Android® operating system, may be programmed into the device.

[0022] FIG. 1 illustrates a first device 100. The first device may be any device capable of storing information such that the stored information can be accessed. The first device 100 may store a record 101. The first device may also have a processor 102. The processor 102 may be any suitable commercially available or custom-designed processing circuit. The first device may also have a communication interface 103 capable of generating a first device communication range 104. The first device may also have memory 105. The first device 100 may be any device capable of containing the record 101 and communicating via the communication interface 103, including a payment card, credit card, debit card, user identity card, mobile phone, smartphone, RFID card, tablet, computer, NFC card, or other communication device. It is understood that the present disclosure is not limited to a particular type of card or first device, but includes any type of card or first device capable of performing the functions described herein.

[0023] The first device 100 may also be a smart card having any suitable smart card operating system stored thereon. For example, the operating system may be stored in memory 105. The card operating system may be executed using the processor 102 of the first device 100. Two examples of operating systems that may be used for smart cards include JavaCard® and MULTOS Card Operating System®. The card operating system may enable on-card application development for programs that need to run within the secure environment of the smart card chip, such as chip activation, issuance, file control, and data load management. Specific applications may be installed on the card operating system to, for example, generate NDEF tags that conform to certain specified parameters. These generated tags may be stored in record 101.

[0024] Record 101 may include any information accessible by a suitable computing device. Record 101 may be stored in memory 105. Record 101 may be stored in any suitable data type, including Boolean, byte, cbyte, date, decimal, integer, long, number, string, or any combination of these data types. Record 101 may also be stored as delimited data, fixed data, or mixed data. Record 101 may include multiple data, all of which may have corresponding metadata. Record may also include custom data types or data fields. Non-limiting examples of data may include information such as a first device identifier number, a credit card number, a personal account number (PAN), a username associated with the first device, an expiration date for the first device, and a card verification value (CVV) code.

[0025] Record 101 may also be stored in a manner that allows data to be exchanged via the NFC Data Exchange Format (NDEF), which allows information to be exchanged between any compatible NFC device and other NFC devices or tags. NDEF is strictly a message format. It is a binary message encapsulation format that enables exchange between NFC-enabled devices. NDEF messages can contain payloads of any type and size. The NDEF data format can be used to store and exchange information such as uniform resource identifiers (URIs), plain text, etc., using a commonly understood format. The NDEF data format may further support the exchange of NDEF messages as a mechanism that enables the exchange of NDEF records. Each NDEF record may contain a structure that identifies the record contents and the record size. An NDEF record may contain two basic components: a record type, which is used to provide context for the payload data, and the payload data. These two components together represent the action to be performed by the device upon receiving the NDEF record. A single NDEF message may contain multiple NDEF records. The NDEF file itself may be created dynamically. For example, an NDEF file can be based on a random number generator or externally introduced data. NDEF files are read when the card or a chip contained within it is exposed to a properly positioned magnetic field and a specific NDEF message request is issued.

[0026] Record 101 may further be stored as an AAR launch tag. An AAR launch tag is a special type of NDEF record used in Google's Android operating system to indicate to an NFC device that it should use an explicitly defined Android application to handle the NFC tag. The AAR launch tag may include a package attribute, which may identify which Android application will handle or process the NFC tag. The package attribute may identify which Android application will be launched in response to the tag.

[0027] Record 101 may also be stored in a format compatible with the iOS® operating system framework. For example, the iOS operating system can use a core NFC library to read Near Field Communication (NFC) tags of types 1-5, which contain data in the NFC Data Exchange format.

[0028] The memory 105 may be read-only memory, write-once read-multiple memory, or read / write memory, such as RAM, ROM, and EEPROM, and the first device 100 may include one or more of these memories. Read-only memory may be factory programmable as a read-only or one-time program. One-time programmability allows writing once and reading many times. Write-once read-multiple memory may be programmed after the memory chip leaves the factory. Once programmed, the memory cannot be rewritten but can be read many times. Read / write memory may be programmed and reprogrammed many times after leaving the factory. Read / write memory may also be read many times. The memory of the user device 200 may be programmed with instructions to generate the record 101. The record 101 may further include a digital tag that may be generated based on instructions contained in the memory 105. The memory of the user device 200 may also include instructions stored as a dedicated applet, such as a JavaCard® applet. For example, memory 105 may generate one or more NDEF tags that may be further configured to become AAR NDEF records associated with a particular Android® application. Thus, memory 105 may be advantageously modified, as needed, to modify which Android® applications on the Android® device in response to receiving the tag. In other examples, memory 105 may be configured to generate digital tags configured to be compatible with different operating systems or different applications.

[0029] Memory 105 may store other information, such as a user identifier. Record 101 may also be included in memory 105. Other information, such as a user identifier, algorithms, and encryption keys, may also be stored in memory 105. Memory 105 may be divided into several zones, each zone having a different level of security. Processor 102 may track which memory addresses belong to which zone and the circumstances under which each zone may be accessed. In an exemplary embodiment, memory 102 may be divided into four zones: a secret zone, a confidential zone, a use zone, and a public zone.

[0030] The secret zone may be used to store information that only the processor 102 can use, such as passwords, encryption keys, etc. Information stored in this zone cannot be read outside the first device 101. The zone may also include a dynamic algorithm that determines tags that the forwarding device may transmit. In one example, the secret zone may be implemented in a separate processor that can perform encryption functions. Encryption keys may be passed to the secret zone or generated in the secret zone; in either case, the keys may be stored in the secret zone and used to support encryption services. Encryption keys may be exported from the secret zone as needed. Encryption keys and passwords may also be stored directly in the memory 105 without using a secret zone.

[0031] The communication interface 103 may be any suitable technology capable of transmitting or receiving data over distance. Examples of such technologies include, for example, Wi-Fi, WLAN, RF, wireless, IR, Bluetooth, RFID, NFC, or any combination thereof, or any other suitable architecture or system facilitating communication of signals, data, and / or messages. Similarly, any suitable hardware-level and software-level algorithms may be selected to enable the transfer of data within the first device communication range 104. The first device communication range 104 may be generated by the communication interface 103 using one or more communication protocols, including an asynchronous connectionless protocol, a synchronous connection-oriented link, a link management protocol, a host controller interface, or a low energy link layer. Information may be communicated using the NDEF data exchange format. This format allows for the exchange of both NDEF messages and NDEF records. The NDEF data format may support NDEF messages, which are a mechanism that enables the exchange of NDEF records. Each NDEF record may include a structure that identifies the contents of the record and the size of the record. An NDEF record may include two components: payload data and a record type, which is used to provide context to the payload data. These two components together represent the actions to be performed by the device upon receiving an NDEF record.

[0032] 2 is a diagram illustrating a user device 200. Non-limiting examples of user device 200 include any NFC reading device, such as a personal computer, laptop, tablet, mobile phone, NFC reader, or smartphone. It is understood that the present disclosure is not limited to a particular type of user device and includes any type of user device capable of performing the functions described herein. User device 200 may include a display 201, a user interface 202, memory 203, a processor 204, and a user device communication interface 205 having a user device communication range 206. User device 200 may be further configured to include one or more operating systems, such as, for example, the Android® operating system.

[0033] The memory 203 may be read-only memory, write-once read-multiple memory, or read / write memory, such as RAM, ROM, and EEPROM, and the user device 200 may include one or more of these memories. Read-only memory may be factory programmable as read-only or one-time program. One-time programmability allows it to be written once and read many times. Write-once read-multiple memory may be programmed at a time after the memory chip leaves the factory. Once programmed, the memory cannot be rewritten, but it can be read many times. Read / write memory may be programmed and reprogrammed many times after leaving the factory and can also be read many times.

[0034] Memory 203 may be further configured to be installed with an operating system or special instructions. The installed operating system may be further configured to install additional compatible software, such as applications and programs. Examples of commercial operating systems include, for example, the Android® operating system, iOS®, Windows®, Debian®, Linux®, and Linux® variations such as Ubuntu®. Proprietary operating systems may also be installed in memory 203. As another example, two or more operating systems may be installed in memory 203, allowing the user of user device 200 to select the operating system they wish to use.

[0035] Display 201 may be selected from any suitable two-dimensional or three-dimensional display, such as a light-emitting diode, liquid crystal display, digital light processing display, or organic light-emitting diode display. User interface 202 may be selected from any suitable user input device, such as a touchpad, touch screen, mechanical switches, a natural language user interface, a click wheel, a QWERTY keyboard, a mouse, gesture recognition, or a capacitive touch screen.

[0036] The user device communication interface 205 may be any suitable technology capable of transmitting or receiving data over a distance. Examples of such technologies include, for example, Wi-Fi, WLAN, RF, wireless, IR, Bluetooth, RFID, near field communication (NFC), or any combination thereof, or any other suitable architecture or system that facilitates communication of signals, data, and / or messages. Similarly, any suitable hardware-level and software-level algorithms may be selected to enable the transfer of data over the user device communication range 206. The user device communication range 206 may be generated by the user device communication interface 205. Example algorithms include an asynchronous connectionless protocol, a synchronous connection-oriented link, a link management protocol, a host controller interface, or a low energy link layer. Information may be communicated using the NDEF data exchange format. This format allows for the exchange of both NDEF messages and NDEF records. The NDEF data format may support NDEF messages, which are a mechanism that enables the exchange of NDEF records.

[0037] The first device 100 and the user device 200 may also communicate with each other using a network. A network may be any means, mechanism, protocol, or pathway that allows for the transfer of information between the first device 103 and the user device 200, including, but not limited to, Wi-Fi, WLAN, RF, wireless, IR, Bluetooth, cellular, near field communication, SMS, MMS, telephone, any combination thereof, or other suitable architecture or system that facilitates communication of signals, data, and / or messages. The first device and the user device may communicate via a single network or multiple networks.

[0038] In an exemplary embodiment, the first device 100 may be energized when it is in proximity to an NFC reader, which may be included in the user device 200. The NFC reader may emit a magnetic field that may energize the first device 100 (e.g., a smart card) through inductance. The first device 100 (e.g., a smart card) may also generate a tag manifest through stored programming, such as an applet that dynamically generates an NFC tag, such as a random number. The first device may emit an NFC signal when powered in this manner or otherwise. Upon detecting the NFC signal emitted by the first device 100, the user device 200 may automatically attempt to read an NDEF message by sending an NDEF request to the first device 100. The first device 100 may accept the request from the user device 200 and respond with an NDEF message. The NDEF message may further include at least one record that is an AAR activation tag.

[0039] When the first device 100 and the user device 200 are in physical proximity to one another, the user device may request information from the first device. In response to the request, the first device may forward the request to the user device 200. The first device may also be configured to automatically transmit information to any user device 200 that can receive information from the first device 100. This may occur, for example, when the first device communication range 104 overlaps with the user device communication range 206. This transfer of information between the first device and the user device may be accomplished through the means described above.

[0040] The first device 100 may be configured to include information such as a credit card number and associated information such as a CVV number, username, and expiration date. The first device 100 may be further configured to transfer this information to the user device 200 using NFC or a similar medium. This information may be accessed by any second device if the two devices are in physical proximity. As described above, upon receiving an NFC tag, an application installed on or otherwise associated with the NFC tag may be launched by the user device 200. The application is typically launched in a visible mode on the user device 200 with full interactivity. Inadvertent launching of one or more applications may interfere with the user's intended use of the NFC functionality of the first device 100 and the user device 200.

[0041] However, the user device 200 may further be configured to include a background service. This background service may be installed in parallel with the installation of an application associated with the tag transmitted from the first device 100. In some examples, the background service may be part of the application associated with the tag transmitted from the first device 100. The background service installed on the user device 200 may monitor the state in which the user device 200 is located. For example, the background service may monitor the device state, such as whether the device screen is active, whether the screen is locked or unlocked, the device's battery or power, and the timing between certain actions (e.g., the time threshold between unlocking the screen and reading the tag). The background service may also monitor whether the application associated with the digital tag is already launched. Upon receiving a digital tag, the mobile device may detect the tag associated with the application and, upon verifying the appropriate device state collected by the background service, launch the application associated with the received digital tag. The background service may then place the launch of the application associated with the digital tag received by the user device 200 in a special state, such as an invisible state in which the user cannot see or interact with the application's interface. Thus, the user is not prevented from launching an application when he or she does not intend to launch the application.

[0042] As an example, the background service may function to stop the launch of an application when the user device 200 is within communication proximity with the first device 100 and a digital tag is read by the user device 200. A situation in which the screen of the user device 200 is locked and an application is launched by reading the digital tag may be considered undesirable, as opposed to a situation in which the user intentionally causes the user device 200 to read the digital tag. The background service may monitor the time difference between the screen of the user device 200 unlocking and the user device 200 reading the digital tag and compare this difference with a threshold. If the difference is less than the threshold (i.e., if the time between unlocking the screen and reading the tag is too short), the background service may stop the launch of the application. If the difference is greater than the threshold (i.e., if the time between unlocking the screen and reading the tag is long enough), the application may continue to launch.

[0043] As a further example, a background service may monitor and track the time whenever a particular event occurs, such as a user unlocking the screen of the user device 200. The background service may then record the time when a digital tag, such as an NFC tag, is received by the user device 200. The background service may then compare the two times, and if the time is within a threshold, such as a short period of 200 milliseconds, the background service may be configured to launch the application associated with the NFC tag in a visibly state rather than invisibly launch the application. In this state, other information received by the user device 200, such as the remainder of the payload encoded in NDEF format, may be stored by the user device 200 in memory or storage. This information may be read and acted upon by the application (still in a visibly state). For example, this information may be transmitted to a web service. This feature may be advantageously used to synchronize read counts between the smart card (e.g., the first device 100) and the entity issuing the smart card (e.g., an institution, bank, or other entity).

[0044] In another example, time tracking may be utilized as a guard against payload execution. For example, a background service may begin recording the time after an event, such as powering on the user device 200 or a user unlocking the screen of the user device 200, and the background service may prevent execution of the NDEF payload for a threshold period, such as 10 seconds, from the time of the event. As another example, time tracking may begin upon receipt of a digital tag by the user device 200.

[0045] In other embodiments, the first device 100 may be further configured to include in its record 101 a tag, such as an AAR activation tag, that is typically added to information transmitted by the first device. When received by the user device, the AAR activation tag may be configured to activate an application specified by the AAR activation tag. This tag may be configured to be transmitted to the user device 200 first before any other tags included in the first device 100 are transmitted. This application may be configured to allow the application associated with the second tag to be activated only if the first tag and the second tag are received by the user device 200 within or outside of a predetermined period. For example, a typical period of 100 milliseconds may be used, which may correspond to a typical human reaction time when tapping a card against a user device. If the same pair of tags is received within this period, it is likely that the card is near the device (e.g., in a wallet attached to a phone) and the user may not have intended for the user device to respond to the tag. However, if the period for receiving the tag is within a certain time frame, a background service or application may allow the application to be activated in its complete state, visible to the user of the user device 200.

[0046] The first device 100 is also configured to include or generate a collection of tags, allowing this process of launching an application to be compatible across operating systems and user devices.

[0047] As another exemplary embodiment, an NFC tag included in a smart card (e.g., first device 100) can be selectively toggled or turned on or off by a user with a user device (e.g., user device 200). As an example, user device 200 may include an application that can write to first device 100 via any of the communication methods described above. For example, user device 200 may communicate with first device 100 via NFC. User device 200 may include an application that allows a user of user device 200 to toggle (i.e., turn on or off, or change its behavior) a signal transmitted from first device 100. This may be accomplished, for example, by an application on the user device that displays NFC options included on a particular smart card. For example, the application may display the name of the smart card, some identifying information about the smart card (e.g., smart card issuer, smart card name, smart card number, etc.), along with a digital tag that the user may wish to turn on or off. The application may then communicate with the user device 200 using NFC or other communication media and then write to the memory of the first device 100. The application may then write to an applet located on, for example, a JavaCard®-compliant card. By writing to or otherwise modifying this applet, the applet included in the first device 100 may be modified to not generate NFC-compatible tags, such as NDEF messages, every time the first device 100 is energized by the user device 200, for example, via a magnetic field. The application on the user device 200 may accomplish this by writing to the applet on the smart card and disabling its ability to generate tags. In some examples, the decision to turn tag reading on or off may be made for security purposes, for example, based on device state, location data, time, and / or other criteria.

[0048] Additional information to verify that only authorized changes are made to the first device 100 may include security algorithms on either or both of the user device 200, the application, and the first device 100. For example, a secret code or hash may be transmitted between the first device 100 and the user device 200 when such a change is attempted.

[0049] As an example, a user may hold their smart card (such as first device 100) on the back of an Android® phone (such as user device 200) or store the card in the phone's wallet in close proximity to the phone's NFC reader. An application installed on the phone programmed to read the card's Europay®, MasterCard®, Visa® ("EMV") applet may read the credit card number, personal information, CVV code, and expiration date from the card. In addition, the NFC reader may launch the application upon receiving, for example, an NDEF record or a digital tag such as an AAR activation tag.

[0050] The addition of an NDEF record to the smart card does not prevent an application already launched by a user on the user device 200 from accessing or requesting information from the first device 100. Applications in the Android® operating system may be launched automatically in the presence of an event, such as the presence of an NFC signal. However, if no applications are active on the user device 200, the NDEF record ensures that a first-party application is launched on the user device 200 in response to receiving an NDEF tag. The Android® operating system is configured to allow only one application at a time to access information from an NFC signal. This may occur, for example, when the user device 200 is in a locked state or when the screen of the user device 200 is inactive. However, if an application has already been launched by the user of the user device 200, the user is not prevented from accessing or using that application in the manner intended.

[0051] As an example, a user may carry their NFC-enabled card in a wallet or purse. Valid cards may be brought into proximity with the user's personal user device or other NFC-enabled user devices throughout the day to power and read the card. For example, a user may have a device with the Android® operating system installed on it. The first device may be further configured to include a tag in its record 101, such as, for example, an AAR activation tag configured to launch the Capital One® application on the Android® phone. If the application is not already installed on the device, the tag may be further configured for the Android® phone to launch the Google® Play Store or other similar platform and allow the specified application to be installed.

[0052] The NDEF tag or AAR launch tag consists of the package name of a specific Android® application. Thus, upon receiving the specific AAR launch tag or NDEF tag, the operating system or Android® operating system launches the specified application when the contactless card is tapped to the phone. If the specified application is not currently installed on the Android® device, the Google® Play Store may be launched to a page where the specified application can be downloaded and installed on the Android® device.

[0053] The tag in the first device 100 may be further configured to cause the second device 200 to access a server and download an application associated with the tag in the first device 100. This may be accomplished by including information in the first device 100 that identifies the specific application. The server may be a well-known standard server commercially used to communicate with devices over a network. In one example, the tag in the first device may cause a specialized application to interface with the server and download the application. One example of such a specialized application is the Google® Play Store for the Android® operating system. Other examples of such applications include the App Store for the iOS operating system and the Microsoft Store from which Windows® applications can be downloaded. Still other examples are the Canonical Store and Ubuntu Software Center for the Ubuntu® operating system. Other specialized package managers exist for various operating systems.

[0054] In an exemplary embodiment, a backend service may be notified of each read of the EMV chip contained in the first device 100 or each NFC read. This may occur through an application associated with a digital tag originating from the first device 100 that reads a payload when invisibly activated. In this manner, a provider of the first device 100, such as a smart card or credit card provider, may be aware of each specific use of the first device 100. For example, a credit card provider may be notified of each EMV chip read. Thus, the credit card provider may compare the information from each EMV chip read with information from known payments made by the customer. In this manner, the credit card provider may use the comparison for fraud prevention. In another example, a smart card issuer may be aware of each read from the EMV chip and compare each known EMV chip read with all attempts to access information contained on the EMV chip. This information may be used to collectively synchronize smart card counters, such as those in the first device and the backend service.

[0055] FIG. 3 is a flowchart illustrating a method 300 for transferring information from a first device 100 to a user device 200 in an exemplary embodiment of the invention. The method begins in step 305, where an applet or digital tags are stored in the first device 100. The applet can be configured to generate a collection or manifest of digital tags. These tags can be pre-generated, in which case the applet can optionally not be used to generate the digital tags. In step 310, a signal is emitted from the first device. This can be emitted in response to an external trigger, such as an electric field, or the first device 100 can be in a constant state of signal emission. The first device 100 can receive a request for information. This step can take the form of, for example, an NFC device within the first device 100 that is activated in the presence of an external range or device. This can also occur when the first device communication range 104 overlaps with other communication ranges. For example, the NDEF file is read when the card / chip is exposed to a properly adjusted magnetic field and a request for a specific NDEF message is issued. In step 315, the first device 100 may transmit a digital tag. In this step, the first device 100 may transmit additional information along with the digital tag. Examples of the additional information transmitted along with the digital tag may include user information or credit card information. In step 320, the transmitted tag may be configured to be associated with at least one application such that, upon receiving the transmitted tag at the second device, the associated application is launched on the second device. The tag may also be further configured to be associated with an input on the second device. The input may also be a specific state of the user device (e.g., the user device 200) in which the device is in a specific state, such as the user device being unlocked, the screen of the user device being active, or the screen being touched. The tag may be configured in a manner corresponding to the NDEF format or the AAR format.The AAR format is compatible with Android® operating system devices and may specify particular actions for the Android® operating system to take upon receipt of an AAR launch tag, such as a particular application to launch in response to a received tag.

[0056] FIG. 4 illustrates a method 400, one embodiment of the present invention. The method begins in step 405, where an applet or digital tag is stored in the first device 100. The applet can be configured to generate a collection or manifest of digital tags. These tags can be pre-generated, in which case the applet can optionally be used to generate the digital tags. In step 410, a signal is emitted from the first device. This can be emitted in response to an external trigger, such as an electromagnetic field, or the first device 100 can be in a constant state of signal emission. The first device 100 can receive a request for information. This step can take the form of, for example, an NFC device within the first device 100 that is activated in the presence of an external range or device. This can also occur when the first device communication range 104 overlaps with other communication ranges. For example, the NDEF file is read when the card / chip is exposed to a properly tuned magnetic field and a request for a specific NDEF message is issued. In step 415, the first device 100 can emit a digital tag. In this step, the first device 100 may transmit additional information along with the digital tag. Examples of the additional information transmitted along with the digital tag may include user information or credit card information. In step 420, the transmitted tag may be configured to be associated with at least one application, such that receiving the transmitted tag at the second device launches the associated application at the second device. The tag may also be further configured to be associated with an input at the second device. The input may also be a specific state of the user device (e.g., user device 200) in which the device is in a specific state, such as the user device being unlocked, the screen of the user device being active, or the screen being touched. In step 425, the transmitted tag may be configured to launch an application at the second device. This application may be launched, for example, when the transmitted tag is received and the payload is processed by the user device (e.g., user device 200), resulting in the application being launched at the user device.In this step, the background service may, for example, record whether the screen is on or off and start a counter based thereon and / or based on the receipt of the transmitted tag. For example, the background service may record the time the screen of the user device is turned on. However, starting the background service at this step is not required and may be started separately from this step. Step 430 may comprise configuring an application associated with the digital tag to launch invisibly. In this state, the application may be running but not displayed to the user. Step 435 may comprise configuring the application so that its launch can be fully visible on the user device (e.g., user device 200). This step may further comprise monitoring the time initiated by the background service or stopping the recording of the time when the user device receives a tag transmitted by the background service (e.g., an Android® broadcast receiver). This time may be used, as described, to determine whether the application associated with the digital tag should be visibly launched.

[0057] FIG. 5 illustrates a method 500 according to an embodiment of the present invention. Method 500 begins in step 505, where information is requested from a first device (e.g., first device 100) when the user device (e.g., user device 200) is in physical proximity to the first device. This may occur when the user device 200 recognizes the presence of the first device through overlapping communication ranges between the first device 100 and the user device 200. This may also occur due to software within the user device 200 recognizing the presence of communication range outside of the user device 200. In step 510, a digital tag is received from the first device 100 (e.g., first device 100). This digital tag may be information not requested from the first device 100. This digital tag may be platform or operating system specific. In some embodiments, this digital tag may be configured to be an AAR activation tag. In step 515, an application associated with the emitted digital tag may be launched in response to the received tag. For example, in the Android® operating system, the launched application may be defined by metadata or a special field in the received tag. If the second device cannot find the application specified in the transmitted digital tag, it may launch a package manager or application manager, such as the Google® Play Store, to identify the specified application and make it available for the user to download. At step 520, any additional tags received by the user device may be intercepted. At step 525, any additional digital information received from the first device when the computer hardware device (e.g., user device 200) is in a particular state may be intercepted. For example, if the mobile phone's screen is on, the mobile phone may be considered to be in a state that is among a list of predetermined states.This may include, for example, one or more tags associated with or subsequently transmitted from the first digital tag that instruct the device receiving the tag to perform a particular action (e.g., launch an application) or otherwise deliver a payload to a second application. In step 530, the application launched in response to receiving the digital tag from the first device may send instructions to the first device. These instructions may disable, overwrite, or deactivate one or more digital tags of the first device associated with at least one application.

[0058] FIG. 6 illustrates a method 600 according to an embodiment of the present invention. Method 600 may begin in step 605, in which at least one digital tag is stored in a first device (e.g., first device 100). An applet may also be stored in the first device, which may be further configured to generate a collection or manifest of digital tags. These tags may be pre-generated, in which case the applet may optionally not be used to generate the digital tags. The applet may also be changeable or configurable, such as by using a flag indicating the digital tags the applet may generate. In step 610, a digital tag is emitted from the first device (e.g., first device 100). This may be in response to an external trigger, such as an electromagnetic field, or the first device 100 may be in a constant state of emitting a signal. This step may take the form of an NFC device in which the first device (e.g., first device 100) is activated in the presence of an external field, such as a magnetic or electric field from a second device (e.g., user device 200), that induces power within the first device 100. The NFC device may also be activated when the first device communication range (e.g., first device communication range 104) overlaps with another communication range, such as that belonging to a second device. In step 615, a tag emitted from the first device (e.g., first device 100) may be configured to be associated with at least one application and may be further configured to launch an application on the second device (e.g., user device 200). This may be performed by configuring the emitted tag to be in a particular data format using a particular payload. For example, a digital tag may be configured to be in the NDEF data format specification and further configured to be an AAR-activated tag. In step 620, the application associated with the emitted tag may be configured to launch only in either a visible or invisible state depending on the information received from the background process.This background process may be initiated, for example, whenever the second device (e.g., user device 200) is in a particular state, such as when the screen of the second device is on, when the second device receives user input, when the second device is unlocked, or when the second device is turned on. In step 620, an application associated with the digital tag may be launched or caused to launch in a visible state. In this state, a user may interact with the application on the second device (e.g., user device 200). For example, a user may interact with the second device using the touchscreen of the second device. In step 625, the application may be further configured to include an option to configure the digital tag included in the smart card (e.g., first device 100). As an example, the smart card may include a smart card operating system, and its memory may further include an applet configured to generate the digital tag. The smart card may also include a communication medium, such as an NFC medium. An application launched on the user device (e.g., user device 200) may then, based on user input, cause the user device to send a command to the smart card to disable generation of a particular digital tag. In another example, the smart card may include a flag that may disable generation of a particular digital tag. Step 630 may comprise further configuring the application, when launched in a visible state, to modify an applet that generates a digital tag on the first device. This modification may be made to modify a particular payload of a digital tag generated on the first device.

[0059] 7 shows a block diagram of an exemplary embodiment of a system 700 according to the present disclosure, which may be used to perform the procedures described below. For example, the exemplary procedures according to the present disclosure described herein may be performed by a processing and / or computing device (e.g., computer hardware device) 705. Such a processing / computing device 705 may be, for example, in whole or in part, a computer / processor 710, which may include, for example, but is not limited to, one or more microprocessors, and uses instructions stored on a computer-accessible medium (e.g., RAM, ROM, hard drive, or other storage device).

[0060] 7, for example, computer-accessible medium 715 (e.g., a storage device such as a hard disk, floppy disk, memory stick, CD-ROM, RAM, ROM, etc., or a collection thereof) may be provided (e.g., in communication with processing unit 705). Computer-accessible medium 715 may include executable instructions 720. Additionally, or alternatively, storage device 725 may be provided separate from computer-accessible medium 715, which may provide instructions to processing unit 705 to configure the processing unit to perform certain example procedures, processes, and methods, as described above herein.

[0061] Additionally, the exemplary processing device 705 may comprise or include one or more input / output ports 735, which may include, for example, a wired network, a wireless network, the Internet, an intranet, data collection probes, sensors, etc., or any combination thereof. As shown in FIG. 7 , the exemplary processing device 705 may communicate with an exemplary display device 730, which, according to certain exemplary embodiments of the present disclosure, may be, for example, a touchscreen configured for inputting information into the processing device in addition to outputting information from the processing device. Additionally, the exemplary display device 730 and / or storage device 725 may be used to display and / or store data in a user-accessible and / or user-readable format.

[0062] Throughout the specification and claims, the following terms shall take at least the meaning expressly associated therewith, unless the context clearly dictates otherwise. The term "or" is intended to mean an inclusive "or." Furthermore, the terms "a," "an," and "the" are intended to mean one or more unless otherwise specified or clear from the context directed to the singular.

[0063] In this description, numerous specific details are set forth. However, it should be understood that implementations of the disclosed technology may be practiced without these specific details. In other instances, well-known methods, structures, and techniques have not been shown in detail so as not to obscure an understanding of this description. References to "some examples," "other examples," "one example," "example," "various examples," "one embodiment," "embodiment," "some embodiments," "exemplary embodiments," "various embodiments," "one implementation," "implementation," "example," "various implementations," "some implementations," etc., indicate that implementations of the disclosed technology so described may include particular features, structures, or characteristics, but not all implementations necessarily include the particular feature, structure, or characteristic. Furthermore, repeated use of the phrase "in one example," "in one embodiment," or "in one implementation" does not necessarily refer to the same example, embodiment, or implementation, although it may do so.

[0064] As used herein, unless otherwise specified, the use of ordinal adjectives "first," "second," "third," etc. to describe a common object merely indicates that different instances of a similar object are being referred to and is not intended to imply that the objects so described must be in a predetermined order, whether temporally, spatially, ordinal, or in any other manner.

[0065] While particular implementations of the disclosed technology have been described in connection with what are presently considered to be the most practical various implementations, the disclosed technology is not intended to be limited to the disclosed implementations, but on the contrary, it is intended to cover various modifications and equivalent arrangements included within the scope of the appended claims. Although specific terms are employed herein, they are used in a generic and descriptive sense only and not for purposes of limitation.

[0066] This written description, using examples, illustrates particular implementations of the disclosed technology, including the best mode. and discloses the making and use of any device or system, and any It will be apparent to those skilled in the art that certain implementations of the disclosed technology, including the execution of the incorporated methods, may be accomplished. The patentable scope of particular implementations of the disclosed technology is defined in the following claims. and may include other examples that occur to those skilled in the art. Such other examples are set forth in the claims. or equivalents that do not substantially differ from the wording of the claim. If it includes a structural element, it is intended to be within the scope of the claims. The methods, systems, and devices according to the various aspects of the present disclosure may have the following features. [Aspect 1] 1. A method, comprising: storing a digital tag on a first device, the tag configured to be associated with at least one application on the second device such that receipt of the tag on the second device launches the application on the second device; transmitting the digital tag from the first device to a second device; Including, The application on the second device, after receiving the tag on the second device, booting up in a special state if the second device is in at least a first state from a predefined list of states; configured to intercept additional digital information from the first device and store the additional digital information in a memory of the second device for a period of time after receiving the digital tag and when the second device is in at least a second state from a predetermined list of states; method. [Aspect 2] 2. The method of aspect 1, wherein the first device is a contactless credit card. [Aspect 3] The method of aspect 1, wherein the first device transmits a short-range wireless communication range. [Aspect 4] 2. The method of claim 1, wherein the second device is a smartphone. [Aspect 5] 5. The method of embodiment 4, wherein the smartphone includes an Android®-based operating system. [Aspect 6] 6. The method of aspect 5, wherein the applet of the first device is further configured to generate a tag manifest configured to generate at least one tag in a Near Field Communications Data Exchange Format (NDEF) specification. [Aspect 7] 7. The method of embodiment 6, wherein the NDEF tag is further configured to be an Android® Application Record (AAR) activation tag. [Aspect 8] 2. The method of claim 1, wherein the list of predetermined states includes at least an unlocked screen. [Aspect 9] 1. A system comprising: Computer hardware devices include: receiving digital information from the first device upon physical proximity to the first device; receiving a digital tag from the first device configured to be associated with an application; In response to the tag, launching the application associated with the received digital tag; configured to intercept additional digital information from the first device and store the additional digital information in a memory of the second device when the computer hardware device is in at least one state from a predetermined list of states through the application for a certain period of time after receiving the digital tag; system. [Aspect 10] A system as described in aspect 9, wherein the launched application is configured to send an instruction to the first device to disable or deactivate the digital tag configured to be associated with the application. [Aspect 11] 11. The system of claim 10, wherein the computer hardware device is configured to include an Android®-based operating system. [Aspect 12] 12. The system of claim 11, wherein the computer hardware device is configured to launch the launched application in response to a Near Field Communication Data Exchange Format (NDEF) tag or an Android® Application Record (AAR) launch tag. [Aspect 13] The system comprises: 10. The system of aspect 9, further comprising the launched application recording a number of launches in response to reading the first device. [Aspect 14] The system comprises: 14. The system of aspect 13, further comprising the launched application sending a notification to a server indicating the number of launches to synchronize a counter on the first device with a counter on the server. [Aspect 15] The system comprises:

[0023] Aspect 14. The system of aspect 13, further comprising, if the application is not present on the second device, in response to receiving the digital tag, the computer hardware device installing the application. [Aspect 16] 2. The method of embodiment 1, wherein the first state and the second state are the same. [Aspect 17] The application receive the information set, 2. The method of embodiment 1, further configured to prevent a second application from accessing the information set. [Aspect 18] A device, a processor; a memory for storing an application; After receiving the digital tag from the transmitting device, the application: waking up when the device is in at least a first state from a list of predetermined states; configured to intercept additional digital information from the transmitting device and store the additional digital information in the memory for a period of time after receiving the digital tag and when the device is in at least a second state from a list of predetermined states; device. [Aspect 19] 19. The device of embodiment 18, wherein the first state and the second state are the same. [Aspect 20] 20. The device of embodiment 18, wherein the predetermined state list comprises a locked state, an unlocked state, a screen on state, and a screen off state. [Aspect 21] 20. The device of aspect 18, wherein the application is configured to send an instruction to the transmitting device to disable the digital tag.

Claims

1. 1. A system comprising an application stored in a memory of a user device, The application launching in response to receiving a digital tag associated with the application from a first device; recording the number of activations in response to said digital tag; configured to send a notification to a server indicating the number of times the activation occurred; system.

2. the first device comprises a smart card and the user device comprises a smartphone; The system of claim 1 .

3. The application is further configured to intercept digital information transmitted by the first device when the first device is in at least one state from a list of predetermined states. The system of claim 1 .

4. the list of predetermined states includes a locked state and an unlocked state; The system of claim 3.

5. the list of predetermined states includes a screen-on state, a screen-off state, and a screen-touched state; The system of claim 3.

6. The application Receive digital information, and further configured to prevent a second application from accessing the received digital information. The system of claim 1 .

7. The application receiving a Near Field Radio Data Exchange Format (NDEF) payload; further configured to prevent execution of the NDEF payload for a predetermined period of time. The system of claim 1 .

8. the time period is calculated from the time of the event; The event includes at least one selected from the group consisting of powering on the user device and unlocking a screen of the user device. The system of claim 7.

9. the time period is calculated from receipt of the digital tag; The system of claim 7.

10. sending the notification synchronizes a counter at the user device with a counter at the server; The system of claim 1 .

11. launching, by an application stored in a memory of the user device, in response to receiving from the first device a digital tag associated with said application; recording the number of launches by the application; sending, by the application, a notification to a server indicating the number of times the application has been invoked; method.

12. and intercepting, by the application, digital information transmitted by the first device. The method of claim 11.

13. the application intercepts digital information transmitted by the first device for a period of time after receiving the digital tag; 13. The method of claim 12.

14. receiving, by the application, a Near Field Wireless Data Exchange Format (NDEF) payload; and preventing execution of the NDEF payload by the application for a predetermined period of time. The method of claim 11.

15. the time period is calculated from receipt of the digital tag; 15. The method of claim 14.

16. the time period is calculated from the time of the event; The event includes at least one selected from the group consisting of powering on the user device and unlocking a screen of the user device.

15. The method of claim 14.

17. A computer-accessible medium containing executable instructions that, when executed by a processor, configure the processor to perform the following steps: The procedure comprises: launching, by an application stored in a memory of the user device, in response to receiving a digital tag associated with said application; recording the number of launches by the application; sending, by the application, a notification to a server indicating the number of times the application has been invoked; Computer-accessible media.

18. The application is launched in a visible or invisible state based on the state of the user device.

18. The computer-accessible medium of claim 17.

19. The state of the user device includes at least one selected from the group consisting of a screen active state, a screen inactive state, a screen locked state, a screen unlocked state, and a battery power state.

20. The computer-accessible medium of claim 18.

20. The procedure comprises: monitoring, by the application, the time period between unlocking the screen of the user device and receiving the digital tag; activating, by the application, if the time period is greater than a threshold; and stopping, by the application, the launch if the time period is less than a threshold.

18. The computer-accessible medium of claim 17.

Images