Systems, methods, and computer-accessible media for suppressing or turning off the reading of digital tags

Abstract

The present invention provides a system, method, and computer-accessible medium for suppressing or turning off the reading of digital tags. [Solution] The method includes storing a digital tag in a first device. The tag is configured to be associated with at least one application on a second device such that receiving the tag on a second device triggers an application on the second device. The method also includes transmitting the digital tag from the first device to the second device. The application on the second device is configured to be launched in a special state if the second device is in at least one state from a predetermined list of states.

Description

Technical Field

[0004] ,

[0001] Cross - Reference to Related Applications This application claims priority to U.S. Patent Application No. 16 / 806,702, filed on March 2, 2020, the disclosure of which is hereby incorporated by reference in its entirety.

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

Background Art

[0003] Near - Field Communication (NFC) - enabled devices, such as smart cards and other devices, are becoming ubiquitous and increasingly popular. Similarly, smartphones have also become increasingly widespread in recent years. When an NFC range is brought close enough to an NFC smart card, the data contained in the NFC - enabled smart card can be read. This powers the NFC component of the smart card and enables information to be read from the smart card. Many smart cards are configured so that appropriate receiving devices can 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 as an NFC reader can read credit card information from a card chip. This allows the mobile device to read the card's information whenever the credit card is within the NFC range of the mobile device.

[0004] Certain operating systems are configured so that smartphones or other devices continuously operate an NFC range, allowing an NFC smart card brought close to the smartphone to be read. For example, devices running the Android® operating system by Google® are configured to always have an active NFC range. This means that when a smart card is brought close, an NFC-enabled smart card may be read unintentionally. For example, if an NFC-enabled card is placed in a user's pocket together with another NFC-enabled card, or if an adhesive wallet is used to store the card attached to the back of a mobile phone, the smart card may be read by a device that the user did not intend for the smartphone or other device to read information contained in that device.

[0005] In other cases, a smartphone may launch an application or perform other actions in response to receiving an NFC tag. This could be detrimental to a smooth user experience when using a smartphone, as users may not want to accidentally tap a smart card and launch an application. In other cases, When a user is carrying an NFC device (such as in their wallet), multiple NFC tags may be read due to proximity, potentially launching multiple applications or performing actions unintentionally. At the same time, users may not want to disable the NFC function on their device because it's convenient to use NFC-enabled smartphones and devices.

[0006] In other cases, the smart card's counter may be incremented each time the NFC-enabled smart card is read. However, this counter does not necessarily correspond to an independent counter maintained by the smart card issuer. The reason for this difference in correspondence is that, for example, while the smart card's counter may be incremented each time the smart card is read, the content or information read from the smart card cannot be transmitted to the smart card issuer. This difference can lead to security problems if the two counters are not synchronized. Therefore, it is necessary to maintain synchronization of the counters on an NFC-enabled smart card without disabling the smart card's NFC functionality.

[0007] Conventional methods related to NFC and the Near Field Wireless Data Interchange Format (NDEF) have limitations in that they do not allow application activation via NFC tag functionality, prevent unintended activation, and / or allow users to switch the functionality of, for example, an NFC smart card. These also have other shortcomings. Therefore, it may be beneficial to provide exemplary systems, methods, and computer-accessible media for selectively suppressing or turning off NFC tag reading by a smartphone. It may be even more beneficial to provide exemplary systems, methods, and computer-accessible media for switching the functionality of application activation in response to NFC tag reading by a smartphone, or for suppressing or turning off reading. Furthermore, it may 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 issuer of the smart card. [Overview of the project]

[0008] Embodiments of the present disclosure provide a system, method, and computer-accessible medium which may include, for example, storing a digital tag in a first device, the tag being configured to be associated with at least one application on a second device, the application being launched on the second device upon receiving the tag, the digital tag being transmitted from the first device to the second device, and the application on the second device being configured to be launched 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 a system, method, and computer-accessible medium which may further include, for example, receiving digital information from a first device in physical proximity to the first device; receiving a digital tag configured to be associated with an application from the first device; in response to the tag, invoking an application associated with the received digital tag; and intercepting additional digital information from the first device via the application for a period of time after the receipt of the digital tag, when the computer hardware device is in at least one state from a predetermined list of states.

[0010] Embodiments of the present disclosure provide a system, method, and computer-accessible medium which may further include, for example, transmitting a digital tag from a first device, the tag being configured to be a Near Field Wireless Communication Data Exchange Format specification, further configured to be an Android® application record launch tag, and further configured to be associated with at least one application on a second device so as to launch the application when the second device receives the tag, the application being 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 list of states.

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

[0012] [Figure 1] This figure shows a first device according to an exemplary embodiment of the present disclosure. [Figure 2] This figure shows a user device according to an exemplary embodiment of the present disclosure. [Figure 3] This is a flowchart of a method for launching an application on a device according to an exemplary embodiment of the present disclosure. [Figure 4] This is a flowchart of a method for launching an application on a device and synchronizing counters, according to an exemplary embodiment of the present disclosure. [Figure 5] This is a flowchart of a method for launching an application on a device and synchronizing counters, according to an exemplary embodiment of the present disclosure. [Figure 6] This is a flowchart of a method for modifying the digital tag of a smart card, according to an exemplary embodiment of the present disclosure. [Figure 7] This is a block diagram of an exemplary system according to an exemplary embodiment of the present disclosure. [Modes for carrying out the invention]

[0013] The following description of embodiments provides non-limiting representative examples that refer to figures specifically to illustrate features and teachings of different embodiments of the invention. It should be recognized from the description of embodiments that the described embodiments can be implemented separately or in combination with other embodiments. A person skilled in the art who considers the description of embodiments should be able to learn and understand the different described embodiments of the invention. The description of embodiments should facilitate the understanding of the invention to the extent that other implementations, which are not specifically covered but are within the knowledge of a person skilled in the art who has read the description of embodiments, should be understood to be consistent with the application of the invention.

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

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

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

[0017] In some cases, a mobile device may continuously monitor for the reception of digital tags on the mobile device. The mobile device may further include background services that can continuously monitor or retrieve information about the mobile device's state. In some cases, the background service may be part of the application identified by the digital tag. When a mobile device receives a digital tag, in combination with information about the mobile device's state 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 whether 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 mobile device's screen is unlocked and the digital tag is read within a threshold time (e.g., within 100 milliseconds, 200 milliseconds, or 400 milliseconds), the monitoring application may determine that this is an inattentive read and therefore the application will not be launched. Inadvertent reading of digital tags can occur for many reasons, including, but not limited to, proximity to the transmitting device or activation of the mobile device's wireless receiver when its screen is unlocked by the user.

[0018] Furthermore, if the mobile device detects another tap or reception of the same digital tag within a given time, the mobile device may launch the application associated with the digital tag in a visible state so that the user can interact with it. Additionally, if the application is launched invisibly in response to the reception of the digital tag, the mobile device may read additional information from the manifests of multiple tags stored on the smart card and send the payloads of such tags to a web service. If no additional digital tag readings occur within a given time, the application may terminate without the user of the device seeing the interface.

[0019] An application can be configured to write to an applet on a smart card compliant with JavaCard® or other smart card operating systems, either automatically or based on user input or settings. Typically, the smart card applet generates NFC-compatible tags, such as NDEF tags, whenever the smart card is powered from within range of a smartphone. Therefore, an application can toggle the smart card's functionality to turn off NFC tag creation, or modify the smart card to allow the user to choose whether to enable or disable the smart card's NFC functionality.

[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 the 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] Applications associated with digital tags may be further configured to perform various functions. For example, an application may send a notification to a user if the application is launched more than a predetermined number of times within a predetermined period. An application may also create a list of other applications installed on the device. Other functions commonly associated with applications on an operating system, such as an application on the Android (registered trademark) operating system, may be programmed into the device.

[0022] FIG. 1 is a diagram showing a first device 100. The first device can be any device that can store information so as to be able to access the stored information. The first device 100 can store a record 101. The first device may also have a processor 102. The processor 102 can be any suitable commercially available or custom-designed processing circuit. The first device may also have a communication interface 103 that can generate a first device communication range 104. The first device may also have a memory 105. The first device 100 can include a record 101 and can be any device that can communicate via the communication interface 103, which may include a payment card, credit card, debit card, user identification 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 and includes any type of card or first device that can perform the functions described herein.

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

[0024] Record 101 can contain any information accessible by a suitable computing device. Record 101 can be stored within the memory 105. Record 101 can 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 can also be stored as delimited data, fixed data, or mixed data. Record 101 can contain multiple data, and these can all have corresponding metadata. The record can also include custom data types or data fields. Non-limiting examples of data can include information such as the identifier number of the first device, credit card number, personal account number (PAN), username associated with the first device, expiration date of the first device, and card verification value (CVV) code.

[0025] Record 101 may also be stored in a way that allows data to be exchanged via the NFC Data Exchange Format (NDEF), which enables the exchange of information 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. An NDEF message can contain a payload 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 commonly understood formats. The NDEF data format can 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 content and size of the record. An NDEF record may contain two basic components: a record type used to provide context for the payload data, and the payload data itself. Together, these two components represent the action performed by the device upon receiving the NDEF record. A single NDEF message may contain multiple NDEF records. NDEF files themselves can be created dynamically. For example, an NDEF file may be based on data introduced from a random number generator or an external source. The NDEF file is read when the card or a chip contained within the card is exposed to a properly positioned magnetic field and a request for a specific NDEF message is issued.

[0026] Record 101 may be further 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 must use an Android® application explicitly defined to handle the NFC tag. An AAR launch tag may include a package attribute that can identify which Android® application will handle or process the NFC tag. The package attribute can 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 the core NFC library to read Type 1-5 Near Field Communication (NFC) tags containing data in the NFC Data Exchange format.

[0028] 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 programmable at the factory as read-only or one-time programmability. One-time programmability allows it to be written to once and read multiple 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 multiple times. Read / write memory can be programmed and reprogrammed multiple times after leaving the factory. Read / write memory can also be read multiple times. The memory of user device 200 may be programmed with instructions to generate record 101. Record 101 may further include digital tags that can be generated based on the instructions contained in memory 105. The memory of user device 200 may also include instructions stored as dedicated applets, such as JavaCard® applets. For example, memory 105 may generate one or more NDEF tags that can be further configured to become AAR NDEF records associated with a specific Android® application. Thus, memory 105 can be advantageously modified, as needed, to change which Android® application on an Android® device in response to the receipt of a tag. In another example, memory 105 may be configured to generate digital tags that are 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, algorithm, and encryption key, may also be stored in memory 105. Memory 105 may be divided into several zones, each having a different level of security. Processor 102 may track which memory addresses belong to which zone and the environments that can access each zone. In an exemplary embodiment, memory 102 may be divided into four zones: a secret zone, a confidential zone, a usage zone, and a public zone.

[0030] The secret zone may be used to store information that can only be used by processor 102, such as passwords and encryption keys. Information stored in this zone cannot be read outside of the first device 101. The zone may also include a dynamic algorithm that determines the tags that the transport device can transmit. In one example, the secret zone may be implemented by a separate processor capable of performing encryption functions. Encryption keys may be passed to the secret zone or generated in the secret zone, and 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 memory 105 without using the secret zone.

[0031] The communication interface 103 can be any suitable technology that can transmit or receive data over distance. Examples of such technologies include, for example, Wi-Fi, WLAN, RF, radio, IR, Bluetooth®, RFID, NFC, or any combination thereof, or other suitable architectures or systems that facilitate the communication of signals, data, and / or messages. Similarly, any suitable hardware-level and software-level algorithms can be selected to enable the transfer of data in the first device communication range 104. The first device communication range 104 can be generated by the communication interface 103 using one or more communication protocols, including asynchronous connectionless protocols, synchronous connection-oriented links, link management protocols, host controller interfaces, or low-energy link layers. Information can 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 and size of the record. An NDEF record may include two components: payload data and a record type used to provide context to the payload data. Together, these two components represent the actions performed by the device when an NDEF record is received.

[0032] Figure 2 shows 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. This disclosure is understood to be not limited to a specific type of user device and to include 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 further be configured to include one or more operating systems, such as the Android® operating system.

[0033] Memory 203 may be read-only memory, write-once read-multiple memory, or read / write memory, such as RAM, ROM, and EEPROM, and user device 200 may include one or more of these memories. Read-only memory may be factory programmable as read-only or one-time programmable. One-time programmability allows it to be written to once and read multiple 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 multiple times. Read / write memory may be programmed and reprogrammed multiple times after leaving the factory. It can also be read multiple 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, Android®, iOS®, Windows®, Debian®, Linux®, and Linux® variations such as Ubuntu®. A dedicated operating system may also be installed in memory 203. As another example, two or more operating systems may be installed in memory 203, and the user of user device 200 can select the operating system they wish to use.

[0035] The display 201 can 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. The user interface 202 can be selected from any suitable user input device, such as a touchpad, touchscreen, mechanical switch, natural language user interface, click wheel, QWERTY keyboard, mouse, gesture recognition, or capacitive touchscreen.

[0036] The user device communication interface 205 can be any suitable technology that can transmit or receive data over distance. Examples of such technologies include, for example, Wi-Fi, WLAN, RF, radio, IR, Bluetooth®, RFID, Near Field Communication (NFC), or any combination thereof, or any other suitable architecture or system that facilitates the communication of signals, data, and / or messages. Similarly, any suitable hardware-level and software-level algorithms can be selected to enable the transfer of data within the user device communication range 206. The user device communication range 206 can be generated by the user device communication interface 205. Examples of algorithms include asynchronous connectionless protocols, synchronous connection-oriented links, link management protocols, host controller interfaces, or low-energy link layers. Information can 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. The network may include, but is not limited to, Wi-Fi, WLAN, RF, radio, IR, Bluetooth®, cellular, near-field communication, SMS, MMS, telephone, any combination thereof, or any other suitable architecture or system that facilitates the communication of signals, data, and / or messages, or any means, mechanism, protocol, or path that enables the transfer of information between the first device 103 and the user device 200. The first device and the user device may communicate over a single network or multiple networks.

[0038] In exemplary embodiments, the first device 100 may become energized when it approaches an NFC reader, which may be included in a user device 200. The NFC reader may emit a magnetic field that can energize the first device 100 (e.g., a smart card) via inductance. The first device 100 (e.g., a smart card) may also generate a tag manifest through stored programming, such as an applet, which dynamically generates NFC tags, such as random numbers. The first device may emit an NFC signal when powered in this manner or otherwise. Upon detecting an 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, which is an AAR activation tag.

[0039] When the first device 100 and the user device 200 are physically close to each other, the user device may request information from the first device. The first device may respond to the request and forward it 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 be done, 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 achieved through the means described above.

[0040] The first device may be configured to include information such as a credit card number, and related information such as a CVV number, username, and expiration date. This 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 physically close together. As described above, upon receiving an NFC tag, the user device 200 may launch an application installed on, or otherwise associated with, the NFC tag. The application is typically launched in visible mode on the user device 200 and is fully interactive. 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 be further configured to include a background service. This background service may be installed in parallel with the installation of the application associated with the tag originating from the first device 100. In some examples, the background service may be part of the application associated with the tag originating 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 specific actions (e.g., a time threshold between unlocking the screen and reading the tag). The background service may also monitor whether the application associated with the digital tag has already been launched. Upon receiving a digital tag, the mobile device may detect the tag associated with the application and, after confirming the appropriate state of the device collected by the background service, launch the application associated with the received digital tag. The background service may then put the launch of the application associated with the digital tag received by the user device 200 into a special state, such as an invisible state, where the user cannot see or interact with the application's interface. Therefore, users will not be prevented from launching an application when they do not intend to launch it.

[0042] For example, a background service may function to stop the application from starting when user device 200 is within communication proximity to the first device 100 and the digital tag is read by user device 200. The state in which the application is launched by reading the digital tag while the screen of user device 200 is locked may be considered undesirable, as opposed to a state in which the user intentionally causes user device 200 to read the digital tag. The background service may monitor the time difference between the screen unlocking of user device 200 and the reading of the digital tag by user device 200 and compare this difference to a threshold. If the difference is smaller than the threshold (i.e., the time between the screen unlocking and the tag reading is too short), the application may be stopped from starting. If the difference is larger than the threshold (i.e., the time between the screen unlocking and the tag reading is sufficiently long), the application may continue to start.

[0043] As a further example, a background service may monitor and track the time whenever a specific event occurs, such as a user unlocking the screen of user device 200. The background service may then record the time a digital tag, such as an NFC tag, is received by user device 200. The background service may then compare the two times, and if the time falls within a threshold, such as a short period of 200 milliseconds, the background service may be configured not to launch the application associated with the NFC tag in a visible state, but rather to launch the application in an invisible state. In this state, other information received by user device 200, such as the rest of the payload encoded in NDEF format, may be stored by user device 200 in memory or storage. This information can be read and responded to by the application (which is still in an invisible state). For example, this information may be sent to a web service. This feature can be advantageously used to synchronize read counts between a smart card (e.g., first device 100) and an entity that issues smart cards (e.g., an institution, bank, or other entity).

[0044] In other examples, time tracking can be used as a guard against payload execution. For instance, a background service may initiate recording of events, such as when the user device 200 is powered on or after the user unlocks the screen of the user device 200, and the background service may prevent the execution of the NDEF payload for a threshold period, e.g., 10 seconds, from the time of the event. In another example, time tracking may be initiated when the user device 200 receives a digital tag.

[0045] In other embodiments, the first device 100 may be further configured to include in its record 101 tags, such as AAR activation tags, which are typically added to the information transmitted by the first device. The AAR activation tag may be configured to launch the application specified by the AAR activation tag when received by the user device. This tag may be configured to be sent first to the user device 200 before any other tags included in the first device 100 are forwarded. This application may be configured to allow the application associated with the second tag to be launched only if the first and second tags are received by the user device 200 within or outside 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 on a user device. If the same pair of tags are received within this period, it is likely that the card is close to the device (e.g., a wallet attached to a phone), and the user may not have intended the user device to respond to the tag. However, if the period for receiving the tags is within a specific time frame, the background service or application may allow the application to be launched in its complete form, visible to the user on the user device 200.

[0046] The first device 100 is also configured to include or generate a collection of tags, enabling this process of launching the application to be compatible between the operating system and the user device.

[0047] In another exemplary embodiment, an NFC tag contained in a smart card (e.g., a first device 100) may be selectively switched on or off by a user having a user device (e.g., a user device 200). As an example, the user device 200 may include an application that can be written to the first device 100 via one of the communication methods described above. For example, the user device 200 may communicate with the first device 100 via NFC. The user device 200 may include an application that allows the user of the user device 200 to switch (i.e., turn on or off, or change its operation) a signal transmitted from the first device 100. This may be achieved, for example, by an application on the user device that displays NFC options contained in 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., the smart card issuer, the smart card name, the smart card number, etc.) along with a digital tag that the user may wish to turn on or off. The application may 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, for example, one placed on a JavaCard® compliant card. By writing to this applet, or otherwise modifying it, the applet contained in the first device 100 may be modified so that it does not generate NFC-compatible tags, such as NDEF messages, each 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 achieve this by writing to a smart card applet and disabling the tag generation function. In some examples, the decision to turn tag reading on or off may be made for security purposes, for example, based on device status, location data, time, and / or other criteria.

[0048] Additional information to verify that only authorized changes are being made to the first device 100 may include security algorithms in the user device 200, the application, and either or both of 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] For example, a user may hold their smart card (e.g., device 100) on the back of an Android® phone (e.g., user device 200) or store the card in the phone's wallet located near the phone's NFC reader. By installing an application on the phone programmed to read the card's Europay®, MasterCard®, Visa® ("EMV") applet, the credit card number, personal information, CVV code, and expiration date can be read from the card. In addition, the NFC reader may activate an application upon receiving a digital tag, such as an NDEF record or an AAR activation tag.

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

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

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

[0053] A tag in the first device 100 may be further configured to cause the second device 200 to access a server and download the application associated with the tag in the first device 100. This can be achieved by including information in the first device 100 that identifies a specific application. The server may be a well-known standard server commercially used to communicate with devices over a network. In one example, a tag in the first device may interface a special application with the server and download the application. One example of such a special 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, which allows downloads of Windows® applications. Yet another example is the Canonical Store and the Ubuntu Software Center for the Ubuntu® operating system. Other special package managers exist for various operating systems.

[0054] In exemplary embodiments, 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, which reads a payload when activated in an invisible state. In this way, 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 of each EMV chip read with information of known payments made by the customer. In this way, 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 read of the EMV chip with all attempts to access the information contained in the EMV chip. This information may be used to synchronize smart card counters, such as those of the first device or a backend service.

[0055] Figure 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 present invention. The method begins in step 305, in which an applet or digital tag is stored in the first device 100. This applet may be configured to generate a collection or manifest of digital tags. These tags may be pre-generated, in which case the applet cannot optionally be used to generate the digital tags. In step 310, a signal is emitted from the first device. This may be emitted in response to an external trigger such as an electric field, or the first device 100 may be in a constant signaling state. The first device 100 may receive a request for information. This step may take the form of an NFC device within the first device 100 that is activated, for example, in the presence of an external range or device. This may also occur if the first device communication range 104 overlaps with other communication ranges. For example, when a card / chip is exposed to a properly tuned magnetic field and a request for a specific NDEF message is issued, the NDEF file is read. 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 additional information transmitted 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 so that when the second device receives the transmitted tag, it launches the associated application on the second device. The tag may also be further configured to be associated with an input on the second device. An input may also be a specific state of the user device (e.g., user device 200) where the device is in a particular state, such as the user device being unlocked, the user device screen 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 can specify specific actions that the Android® operating system will perform upon receiving an AAR launch tag. For example, it can specify a particular application to launch in response to a received tag.

[0056] Figure 4 illustrates a method 400, which is one embodiment of the present invention. This method begins in step 405, in which an applet or digital tag is stored in a first device 100. This applet may be configured to generate a collection or manifest of digital tags. These tags may be pre-generated, in which case the applet cannot optionally be used to generate the digital tags. In step 410, a signal is transmitted from the first device. This may be transmitted in response to an external trigger, such as an electromagnetic field, or the first device 100 may be in a constant transmitting state of signaling. The first device 100 may receive a request for information. This step may take the form of an NFC device within the first device 100 that is activated, for example, in the presence of an external range or device. This may also occur if the first device communication range 104 overlaps with other communication ranges. For example, if a card / chip is exposed to a properly tuned magnetic field and a request for a specific NDEF message is issued, the NDEF file is read. In step 415, 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 additional information transmitted 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 so that when the second device receives the transmitted tag, the second device launches the associated application. The tag may also be further configured to be associated with an input on the second device. An input may also be a specific state of the user device (e.g., user device 200) where the device is in a particular state, such as the user device being unlocked, the user device screen being active, or the screen being touched. In step 425, the transmitted tag may be configured to launch an application on the second device. This application may be launched, for example, when the transmitted tag is received, the payload is processed by the user device (e.g., user device 200), and as a result the application is launched on the user device.In this step, a background service may, for example, record whether the screen is on or off and, based on that and / or based on the reception of a transmitted tag, start a counter. For example, the background service may record the time the user device's screen was on. However, it is not necessary to start the background service in this step and it can be started separately. Step 430 consists of configuring the application associated with the digital tag to launch invisibly. In this state, the application can be run but is not visible to the user. Step 435 may consist of configuring the application so that its launch can be fully visible on the user device (e.g., user device 200). This step may be further configured by monitoring the time started by the background service or stopping the recording of the time when the user device receives a transmitted tag from 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 launched in a visible state.

[0057] Figure 5 illustrates Method 500, an embodiment of the present invention. Method 500 begins in step 505, when a user device (e.g., user device 200) is in physical proximity to the first device and information is requested from the first device (e.g., first device 100). This may occur when user device 200 recognizes the presence of the first device through the overlap of the communication ranges between the first device 100 and user device 200. This may also occur by software within user device 200 that recognizes the presence of a communication range outside of 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 by 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 launch tag. In step 515, an application associated with the transmitted digital tag may be launched in response to the received tag. For example, in the Android® operating system, a launched application may be defined by metadata or special fields in the received tag. If the second device cannot find the application specified by 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. In step 520, any additional tags received by the user device may be further intercepted. In step 525, any additional digital information received from the first device may be intercepted when the computer hardware device (e.g., user device 200) is in a particular state. For example, if the screen of a mobile phone is turned on, the mobile phone may be considered to be in a state in a given list of states.This may include, for example, one or more tags associated with or subsequently sent to a first digital tag, which instruct the device that received the tag to perform a specific action (e.g., launch an application) or otherwise deliver a payload to a second application. In step 530, an application launched in response to receiving a 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 on the first device associated with at least one application.

[0058] Figure 6 illustrates Method 600, 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 cannot optionally be used to generate the digital tags. The applet may also be modifiable or configurable, for example, by using flags that indicate the digital tags the applet can generate. In step 610, the digital tag is transmitted from the first device (e.g., first device 100). This may be transmitted in response to an external trigger, such as an electromagnetic field, or the first device 100 may be in a constant transmitting state of signaling. This step may take the form of an NFC device in which the first device (e.g., the 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., a user device 200), which induces power within the first device 100. The NFC device may also be activated when the first device communication range (e.g., the first device communication range 104) overlaps with other communication ranges, such as those belonging to the second device. In step 615, a tag transmitted from the first device (e.g., the first device 100) may be configured to be associated with at least one application, and further configured to activate the application on the second device (e.g., a user device 200). This may be accomplished by configuring the transmitted tag to be in a specific data format using a specific payload. For example, a digital tag may be configured to conform to the NDEF data format specification, and further configured to be an AAR activation tag. In step 620, the application associated with the transmitted 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 can be started whenever a second device (e.g., user device 200) is in a specific state, such as the second device's screen being on, the second device receiving user input, the second device being unlocked, or the second device being turned on. In step 620, the application associated with the digital tag may be launched or made to launch in a visible state. In this state, the user may interact with the application on the second device (e.g., user device 200). For example, the 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 a digital tag contained in a 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 a digital tag. The smart card may also include a communication medium, such as an NFC medium. Next, an application launched on a user device (e.g., user device 200) may, based on user input, cause the user device to send a command to the smart card to disable the generation of a particular digital tag. In another example, the smart card may include a flag that can disable the generation of a particular digital tag. Step 630 may further configure the application, when launched in a visible state, to modify the applet that generates the digital tag on the first device. This modification may be done to modify the specific payload of the digital tag generated on the first device.

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

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

[0061] Furthermore, the exemplary processing unit 705 may include, or may include, one or more input / output ports 735, which may include, for example, a wired network, a wireless network, the internet, an intranet, a data acquisition probe, a sensor, or any combination thereof. As shown in Figure 7, the exemplary processing unit 705 may communicate with an exemplary display device 730, which, according to certain exemplary embodiments of this disclosure, may be, for example, a touchscreen configured to input information to the processing unit in addition to outputting information from the processing unit. Furthermore, the exemplary display device 730 and / or storage device 725 may be used to display and / or store data in a user-accessible format and / or user-readable format.

[0062] Throughout the specification and claims, the following terms take on the meanings expressly associated herein, unless the context clearly indicates otherwise. The term “or” is intended to mean an inclusive “or.” Furthermore, the terms “a,” “an,” and “the” are intended to mean one or the plural, unless otherwise specified or evident from the context relating to the singular.

[0063] This description includes numerous specific details. However, it should be understood that the disclosed technology may be implemented without these specific details. In other instances, well-known methods, structures, and techniques are not described in detail so as not to obscure the understanding of this description. References to “several examples,” “other examples,” “one example,” “example,” “various examples,” “one embodiment,” “embodiment,” “several embodiments,” “exemplary embodiment,” “various embodiments,” “one implementation,” “implementation,” “example,” “various implementations,” and “several implementations” indicate that while the implementation of the disclosed technology described in this way may include certain features, structures, or characteristics, not all implementations necessarily include those specific features, structures, or characteristics. Furthermore, repeated use of phrases such as “in one example,” “in one embodiment,” or “in one implementation” does not necessarily refer to the same example, embodiment, or implementation, although it may.

[0064] As used herein, unless otherwise specified, the use of ordinal adjectives such as "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 described in this way must be in a given order, whether temporally, spatially, sequentially, or otherwise.

[0065] While specific implementations of the disclosed technology have been described in relation to what is considered to be the most practical and diverse implementations currently available, the disclosed technology should not be limited to the disclosed implementations, but rather is intended to cover a variety of modifications and equivalent configurations that fall within the scope of the appended claims. Certain terms are used herein, but they are used only in a general and descriptive sense and not for limitation.

[0066] This written description, using examples, discloses specific practices of the disclosed technology, including the best form, and enables a person skilled in the art to practice specific practices of the disclosed technology, including the creation and use of any device or system, and the execution of any incorporated method. The patentable scope of specific practices of the disclosed technology is defined in the claims and may include other examples that a person skilled in the art would recall. Such other examples are intended to be within the scope of the claims if they have structural elements that are not different from the language of the claims, or if they include equivalent structural elements that are substantially different from the language of the claims.

Claims

1. A method, wherein the said method is The invention involves storing a digital tag in a first device, wherein the tag is configured to be associated with at least one application on a second device such that receiving the tag on a second device triggers the launch of an application on the second device. Transmitting the aforementioned digital tag from the first device to the second device, Includes, The application of the second device, after receiving the tag on the second device, If the second device is in at least one of the first states from a predetermined state list, it starts up in a special state. During a certain period after receiving the digital tag, and while the second device is in at least the second state from a predetermined state list, it is configured to intercept additional digital information from the first device and store the additional digital information in the memory of the second device. method.

2. The method according to claim 1, wherein the first device is a contactless credit card.

3. The method according to claim 1, wherein the first device transmits a short-range wireless communication signal.

4. The method according to claim 1, wherein the second device is a smartphone.

5. The method according to claim 4, wherein the smartphone includes an Android®-based operating system.

6. The method according to claim 5, wherein the applet of the first device is further configured to generate a tag manifest, which is configured to generate at least one tag in the Near Field Wireless Communication Data Interchange Format (NDEF) specification.

7. The method according to claim 6, wherein the NDEF tag is further configured to be an Android® Application Record (AAR) activation tag.

8. The method according to claim 1, wherein the list of predetermined states includes at least screen unlocking.

9. It is a system, Computer hardware devices are When physically close to the first device, digital information is received from the first device. The first device receives a digital tag configured to be associated with an application, In response to the tag, the application associated with the received digital tag is launched. During a certain period after receiving the digital tag, if the computer hardware device is in at least one state from a predetermined state list, the application is configured to intercept additional digital information from the first device and store the additional digital information in the memory of the second device. system.

10. The system according to claim 9, wherein the activated application is configured to send a command to the first device to disable or deactivate the digital tag configured to be associated with the application.

11. The system according to claim 10, wherein the computer hardware device is configured to include an Android®-based operating system.

12. The system according to claim 11, wherein the computer hardware device is configured to launch the launched application in response to a Near Field Wireless Communication Data Interchange Format (NDEF) tag or an Android® Application Record (AAR) launch tag.

13. The aforementioned system, The system according to claim 9, further comprising the activated application recording the number of activations in response to a read from the first device.

14. The aforementioned system, The system according to claim 13, further comprising the activated application sending a notification to a server indicating the number of times it has been activated, thereby synchronizing the counter of the first device with the counter of the server.

15. The aforementioned system, The system according to claim 13, further comprising the computer hardware device installing the application in response to the receipt of the digital tag if the application is not present on the second device.

16. The method according to claim 1, wherein the first state and the second state are the same.

17. The aforementioned application is Receive the information set, The method according to claim 1, further configured to prevent a second application from accessing the information set.

18. It is a device, Processor and It includes memory for storing applications, After receiving the digital tag from the transmitting device, the application: The device is activated when it is in at least one of the first states from a predetermined list of states. During a certain period after receiving the digital tag, and while the device is in at least the second state from a predetermined list of states, it is configured to intercept additional digital information from the transmitting device and store the additional digital information in the memory. device.

19. The device according to claim 18, wherein the first state and the second state are the same.

20. The device according to claim 18, wherein the predetermined state list includes a locked state, an unlocked state, a screen-on state, and a screen-off state.

21. The device according to claim 18, wherein the application is configured to send a command to the transmitting device to disable the digital tag.

Images