Systems, methods, and computer-accessible media for suppressing or shutting down reading of digital tags

Abstract

Systems, methods, and computer-accessible media for suppressing or shutting down reading of a digital tag 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 to receive that a tag in the second device launches an application on the second device; and transmitting the digital tag from the first device to the second device; wherein the application on the second device is configured to be started in a special state when the second device is in at least one state in the predetermined state list.

Description

[0001] This application is a divisional application of the patent application with application number "202180029651.1", application date "February 24, 2021", and titled "System, method and computer-accessible medium for inhibiting or turning off the reading of digital tags".

[0002] CROSS-REFERENCE TO RELATED APPLICATIONS

[0003] This application claims priority to U.S. Patent Application No. 16 / 806,702, filed on March 2, 2020, the disclosure of which is incorporated herein by reference in its entirety. Technical Field

[0004] The present disclosure generally relates to inhibiting or shutting down the use of a device (such as a smartphone (e.g., or Mobile phone)) reading digital tags (such as NFC tags). Background Art

[0005] Devices that support near field communication (NFC), such as smart cards and other devices, have become ubiquitous and continue to increase in popularity. Similarly, smartphones have become increasingly popular in recent years. The data contained in an NFC-enabled smart card can be read when the NFC field is close enough to the NFC smart card. This activates the NFC component on the smart card and allows information to be read from the smart card. Many smart cards are configured to allow any suitable receiving device to access the encoded information. This can cause security issues, especially when a mobile device is able to read data from a contactless chip. A mobile device configured with, for example, an NFC reader is able to read credit card information from a card chip. This can allow the mobile device to read the information on the card whenever the credit card is within the range of the mobile device's NFC field.

[0006] Some operating systems are configured to cause a smartphone or other device to continuously operate its NFC field, allowing the smartphone to read any NFC smart card that is brought into close proximity with the smartphone. As an example, running of The device with the operating system is configured to have a continuously active NFC field. This can result in the unintentional reading of a smart card when it is in close proximity to an NFC-enabled smart card. For example, when an NFC-enabled smart card is carried in a user's pocket, or when using a sticky wallet that attaches to the back of a phone to store the card, the smart card can be read by a device that the user does not expect the smartphone or other device to read the information contained on the smartphone or other device.

[0007] In other cases, the smartphone may launch an application or perform another action in response to receiving an NFC tag. This can be contrary to a smooth user experience of using a smartphone, as the user may not want to tap a smart card to launch an application without intending to. In other cases, due to close proximity when carried by the user (such as in the user's wallet), multiple NFC tags may be read, resulting in multiple applications being launched or taking actions without the user intending to perform those actions. At the same time, due to the convenience of using an NFC-enabled smartphone and NFC-enabled device, a user may not want to disable the NFC functionality of his or her device.

[0008] In other cases, a counter on the smart card may be incremented each time the NFC-enabled smart card is read. However, the counter does not necessarily correspond to an independent counter maintained at the issuer of the smart card. The difference in correspondence may occur because, for example, a counter on the smart card may be incremented each time the smart card is read, but the data or information read from the smart card may not be sent to the issuer of the smart card. This difference may lead to security issues when the two counters are not synchronized. Therefore, it is necessary to keep the counter on the NFC-enabled smart card synchronized without disabling the NFC capability of the smart card.

[0009] Conventional methods related to NFC and Near Field Data Exchange Format (NDEF) have limitations that do not allow the functionality of NFC tags to launch applications, prevent unintentional launches, and / or allow users to switch the functionality of, for example, NFC smart cards. These are other deficiencies that exist. Therefore, it may be beneficial to provide exemplary systems, methods, and computer-accessible media that selectively inhibit or turn off the reading of NFC tags by a smartphone. It may also be beneficial to provide exemplary systems, methods, and computer-accessible media to switch the functionality of inhibiting or turning off reading or launching an application in response to reading an NFC tag by a smartphone. Even further, it may be beneficial to provide exemplary systems, methods, and computer-accessible media that can synchronize (and / or maintain) a counter on a smart card with a counter on the issuer of the smart card. Summary of the invention

[0010] Embodiments of the present disclosure provide a system, method, and computer-accessible medium, which may include, for example, storing a digital tag on a first device, the tag being configured to be associated with at least one application on a second device so that reception of the tag on the second device launches the application on the second device; and transmitting the digital tag from the first device to the second device; wherein the application on the second device is configured to launch in a special state when the second device is in at least one state in a predetermined state list.

[0011] 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 when 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, launching an application associated with the received digital tag; and within a fixed duration after receiving the digital tag, when the computer hardware arrangement is in at least one state in a predetermined list of states, intercepting additional digital information from the first device through the application.

[0012] 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, wherein the tag is configured to be in a near field communication data exchange format specification, and is also configured to record a launch tag for an Android application, and is also configured to be associated with at least one application on a second device, so that reception of the tag on the second device launches the application, wherein the application is configured to intercept additional information transmitted from the first device within a fixed duration when the second device is in at least one state in a predetermined state list.

[0013] Further features of the disclosed design and the advantages provided thereby will be explained in more detail below with reference to specific example embodiments shown in the accompanying drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0014] Figure 1 is a diagram illustrating a first device according to an example embodiment of the present disclosure.

[0015] Figure 2 is a diagram illustrating a user equipment according to an example embodiment of the present disclosure.

[0016] Figure 3 is a flowchart of a method for launching an application on a device according to an exemplary embodiment of the present disclosure.

[0017] Figure 4 is a flowchart of a method for launching an application on a device and synchronizing a counter according to an example embodiment of the present disclosure.

[0018] Figure 5 is a flowchart of a method for launching an application on a device and synchronizing a counter according to an example embodiment of the present disclosure.

[0019] Figure 6 is a flow chart of a method for modifying a digital tag of a smart card according to an example embodiment of the present disclosure.

[0020] Figure 7 is an illustration of a block diagram of an example system according to an example embodiment of the present disclosure. DETAILED DESCRIPTION

[0021] The following description of the embodiments provides non-limiting representative examples of reference numbers to specifically describe the features and teachings of different aspects of the present invention. The described embodiments should be recognized as being able to be implemented individually or in combination with other embodiments from the description of the embodiments. Those of ordinary skill 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 promote the understanding of the present invention so that other embodiments that are not specifically covered but are within the knowledge of those skilled in the art who have read the description of the embodiments will be understood to be consistent with the application of the present invention.

[0022] An exemplary system, method, and computer-accessible medium may be provided that may facilitate preventing or inhibiting a device from reading information contained on a smart card, such as a computer or a smart phone. The smart phone may be Mobile phone, but any smart phone with the functions described in this disclosure is within the scope of the present invention.

[0023] A smart card can be, for example, an identification card that can be read by a mobile device. For example, a mobile device or other similar device can read the encoded information on a user's smart card when the smart card is physically close to the device. Smart cards are typically encoded to provide digital information to a device without any configuration required - therefore, the information on the card can be read by any software installed on the digital device. However, a smart card can be encoded to include, for example, a digital tag. When the smart card is close to the device, the digital tag can first be read by the mobile device. Typically, when the digital tag is received, the application identified by the digital tag, or otherwise configured to be associated with the payload in the digital tag, is automatically launched.

[0024] The digital tag can be configured to, when read by the mobile device, first launch the application identified by the digital tag. The application is typically launched in response to receiving the digital tag. In addition, if desired, the digital tag can be configured to prompt the mobile device to download and install the application before launching the application. In some examples, the digital tag can be configured to cause the mobile device to launch an application store associated with an operating system running on the mobile device (e.g., for Equipment Play Store) to easily download and install apps.

[0025] In some examples, the mobile device may continuously monitor the reception of one or more digital tags on the mobile device. The mobile device may also include a background service that may continuously monitor or otherwise capture information about the state of the mobile device. In some examples, the background service may be part of an application identified by a digital tag. After the mobile device receives the digital tag, and in combination with the information collected by the background service about the state of the mobile device (e.g., whether the screen is on, whether the device is locked / unlocked, whether the power saving mode is on / off, which applications are running, which tasks are waiting to be completed, whether the communication interface is connected / disconnected, whether the device is waiting for user input, whether the processor is running above or below a certain level, whether the battery is above or below a certain level, or whether the target application has been started or is involved in a task), the mobile device may start the application associated with the digital tag into an invisible state. 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 that this is an unintentional read, and therefore the application will not be started. Unintentional reading of a digital tag may be caused by a variety of reasons, including, but not limited to, proximity to a transmitting device and activation of a mobile device's radio receiver when a user unlocks the mobile device's screen.

[0026] In addition, if the mobile device detects another tap or receives the same digital tag within a predetermined time period, the mobile device can then launch the application associated with the digital tag in a visible state for user interaction. In addition, if the application is launched into an invisible state in response to receiving the digital tag, the mobile device can also read additional information from a manifest of multiple tags stored on the smart card and send the payloads of these tags to the network service. If there is no additional reading of the digital tag within the predetermined time period, the application can exit without the user of the device ever seeing the interface.

[0027] The application can also be configured to automatically or based on user input or preference write to the or an applet on the smart card for another smart card operating system. The applet on the smart card will typically generate an NFC compatible tag such as an NDEF tag whenever the smart card is powered by the field of the smartphone. The application can thus switch the functionality of the smart card to turn off the creation of NFC tags, or otherwise modify the smart card so that the user can choose whether he wants the NFC functionality of the smart card to be enabled or disabled.

[0028] The launched application can be configured, for example, to prevent other applications on the smartphone device from accessing the requested information. The application associated with the digital tag can be installed on the device by the user. The tag can be generated in the NDEF data format specification. The NDEF tag can also be configured to Application Record (AAR) launch tag.

[0029] The application associated with the digital tag may also be configured to perform various functions. For example, when the application is launched more than a predetermined number of times within a predetermined time period, the application may send a notification to the user. The application may also create a list of other applications installed on the device. Any other functions that are typically associated with applications on an operating system, such as, for example, Any application on the operating system can be programmed into the device.

[0030] Figure 1 is a diagram showing a first device 100. The first device may be any device capable of storing information so that the stored information can be accessed. The first device 100 may be capable of storing 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 field 104. The first device may also have a memory 105. The first device 100 may be any device capable of containing a record 101 and capable of communicating through a communication interface 103, including a payment card, a credit card, a debit card, a user identification card, a mobile phone, a smart phone, an RFID card, a tablet computer, a computer, an NFC card, or any other communication device. It should be 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 capable of performing the functions described herein.

[0031] The first device 100 may also be a smart card having any suitable smart card operating system stored on the first device 100. For example, the operating system may be stored on the memory 105. The card operating system may be run using the processor 102 of the first device 100. Two examples of operating systems that may be used for smart cards include and MULTOS card operating system The card operating system can allow on-card application development of programs that need to run in the secure environment of the smart card chip, such as, for example, chip activation, issuance, control files, and management data loading. Specific applications can be installed on the card operating system to, for example, generate NDEF tags that comply with certain specified parameters. These generated tags can be stored in record 101.

[0032] 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 precision, number, string, or any combination of these data types. Record 101 may also be stored as delimited, fixed, or mixed data. Record 101 may contain multiple pieces of data, all of which may have corresponding metadata. Records may also include custom data types or data fields. Non-limiting examples of data may include information such as an identifier number of a first device, a credit card number, a personal account number (PAN), a user name associated with a first device, an expiration date of a first device, and a card verification value (CVV) code.

[0033] Record 101 can also be stored in a manner that allows data to be exchanged through the NFC Data Exchange Format (NDEF), which allows information to be exchanged between any compatible NFC device and another NFC device or tag. NDEF is strictly a message format. It is a binary message encapsulation format that allows 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 using commonly understood formats, such as uniform resource identifiers (URIs), plain text, etc. The NDEF data format can further support the exchange of NDEF messages as a mechanism to allow the exchange of NDEF records. Each NDEF record can contain a structure that identifies the content of the record and the size of the record. The NDEF record can contain two components at a basic level, a record type that is used to provide context to the payload data, and payload data. These two components together represent the action to be taken by the device when receiving the NDEF record. An NDEF message can contain more than one NDEF record. The NDEF file itself can be created dynamically. For example, the NDEF file can be based on a random number generator or externally introduced data. The NDEF file is read when the card or the chip contained in the card is exposed to a properly aligned magnetic field and a request is made for the specified NDEF message.

[0034] Record 101 may also be stored as an AAR Start Tag. The AAR Start Tag is a special type of NDEF record that is created by Google. Used by the operating system to indicate a well-defined The application should be used to handle NFC tags. The AAR launch tag can include a package attribute that identifies which The application will handle or process the NFC tag. The package attribute can identify which The application will be launched in response to the tag.

[0035] Record 101 may also be stored in a format compatible with the iOS operating system framework. For example, the iOS operating system allows the use of a core NFC library to allow near field communication (NFC) tags of types 1 to 5 to be read, which contain data in the NFC data exchange format.

[0036] The memory 105 may be a read-only memory, a write-once-read-many memory, or a read / write memory, such as a RAM, a ROM, and an EEPROM, and the first device 100 may include one or more of these memories. The read-only memory may be programmed at the factory to be read-only or one-time programmable. One-time programmability provides the opportunity to write once and then read multiple times. The write-once / read-many memory may be programmed at a certain point in time after the memory chip leaves the factory. Once the memory is programmed, it cannot be rewritten, but it can be read multiple times. The read / write memory may be programmed and reprogrammed multiple times after leaving the factory. The read / write memory may also be read multiple times. The memory of the user device 200 may be programmed with instructions to generate a record 101. The record 101 may also include a digital tag, which may be generated based on the instructions included in the memory 105. The memory of the user device 200 may also include a program stored as a dedicated applet (such as For example, the memory 105 may generate one or more NDEF tags, which may be further configured to be associated with a specific The associated AAR NDEF record is applied. Thus the memory 105 can be advantageously modified if changes are required in response to receiving a tag. Which on the device In another example, the memory 105 may be configured to generate a digital tag, which is configured to be compatible with different operating systems or different applications.

[0037] Memory 105 may store other information, such as a user identifier. Record 101 may also be included in memory 105. User identifiers, algorithms, other information such as encryption keys may also be stored in memory 105. Memory 105 may be divided into several areas, each with a different security level. Processor 102 may keep track of which memory addresses belong to which areas and the circumstances under which each area may be accessed. In an example embodiment, memory 102 may be divided into four areas: a confidential area, a secret area, a use area, and a public area.

[0038] The confidentiality area can be used to store information that can only be used by the processor 102, such as passwords, encryption keys. The information stored in this area is unreadable outside the first device 101. The area can also contain a dynamic algorithm that determines the tags that can be sent by the transmitting device. In one example, the confidentiality area can be implemented using a separate processor capable of performing encryption functions. The encryption key can be transferred to the confidentiality area, or it can be generated in the confidentiality area, and in either case, the key can be stored in the confidentiality area and used to support encryption services. If necessary, the encryption key can be derived from the confidentiality area. The encryption key and password can also be stored directly in the memory 105 without using the confidentiality area.

[0039] The communication interface 103 can be any suitable technology capable of sending or receiving data at a certain distance. Examples of such technologies include, for example, Wi-Fi, WLAN, RF, radio, IR, Bluetooth, RFID, NFC or any combination thereof, or any other suitable architecture or system that facilitates signal, data and / or message communication. Similarly, any suitable hardware-level and software-level algorithms can be selected to allow data to be transmitted on the first device communication field 104. The first device communication field 104 can 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 can be communicated using the NDEF data exchange format. NDEF messages and NDEF records can be exchanged using this format. The NDEF data format can support NDEF messages, which is a mechanism that allows NDEF records to be exchanged. Each NDEF record can contain a structure that identifies the content of the record and the size of the record. The NDEF record can contain two components, payload data and a record type that is used to provide context to the payload data. These two components together represent the action to be taken by the device when the NDEF record is received.

[0040] Figure 2 200. Non-limiting examples of user device 200 include any NFC reading device, such as a personal computer, notebook, tablet, mobile phone, NFC reader, or smart phone. It should be 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 screen 201, user interface 202, memory 203, processor 204, and user device communication interface 205 having user device communication field 206. User device 200 may also be configured to include one or more operating systems, such as operating system.

[0041] The memory 203 may be a read-only memory, a write-once-read-many memory, or a read / write memory, such as a RAM, a ROM, and an EEPROM, and the user device 200 may include one or more of these memories. The read-only memory may be programmed to be read-only or one-time programmable at the factory. One-time programmability provides the opportunity to write once and then read multiple times. The write-once-read-many memory may be programmed at a certain point in time after the memory chip leaves the factory. Once the memory is programmed, it cannot be rewritten, but it can be read multiple times. The read / write memory may be programmed and reprogrammed multiple times after leaving the factory. It may also be read multiple times.

[0042] The memory 203 may also be configured to have an operating system or special instructions installed. The installed operating system may also be configured to install additional compatible software, such as applications or programs. Examples of commercial operating systems include, for example, operating system, as well as Variants such as A dedicated operating system may also be installed on memory 203. As another example, more than one operating system may be installed on memory 203, allowing a user of user device 200 to select an operating system that the user wishes to use.

[0043] Screen 201 can be selected from any suitable two-dimensional or three-dimensional display, such as a light emitting diode, a liquid crystal display, a digital light processing display, or an organic light emitting diode display. User interface 202 can be selected from any suitable user input device, such as a touch pad, a touch screen, a mechanical switch, a natural language user interface, a click wheel, a qwerty keyboard, a mouse, gesture recognition, or a capacitive touch screen.

[0044] The user equipment communication interface 205 can be any suitable technology capable of sending or receiving data at a 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 promotes signal, data and / or message communication. Similarly, any suitable hardware-level and software-level algorithms can be selected to allow data to be transmitted on the user equipment communication field 206. The user equipment communication field 206 can be generated by the user equipment 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. NDEF messages and NDEF records can be exchanged using this format. The NDEF data format can support NDEF messages, which is a mechanism that allows NDEF records to be exchanged.

[0045] The first device 100 and the user device 200 may also communicate with each other using a network. The network may be any means, mechanism, protocol, or approach that allows information to be transmitted between the first device 103 and the user device 200, including but 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. The first device and the user device may communicate via a single network or multiple networks.

[0046] In an example embodiment, the first device 100 may be excited when the first device 100 approaches an NFC reader that may be included on the user device 200. The NFC reader may emit a magnetic field that may inductively excite the first device 100 (e.g., a smart card). The first device 100 (e.g., a smart card) may also generate a tag list through stored programming such as an applet that dynamically generates NFC tags such as random numbers. Once the first device is powered by one or another method, it may emit an NFC signal. 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 also include at least one record that is an AAR startup tag.

[0047] When the first device 100 and the user device 200 are physically close to each other, the user device can request information from the first device. The first device can respond to the request and transmit the request to the user device 200. The first device can also be configured to automatically transmit information to any user device 200 that can receive information from the first device 100. This can be implemented, for example, when the first device communication field 104 overlaps with the user device communication field 206. Such information transmission between the first device and the user device can be achieved by the above-mentioned means.

[0048] The first device can be configured to include information such as a credit card number and associated information such as a CVV number, a user name, and an expiration date. The first device 100 can also be configured to transmit this information to the user device 200 using NFC or a similar medium. When the two devices are physically close, the information can be accessed by any second device. As described above, upon receiving the NFC tag, the user device 200 can launch an installed application or an application otherwise associated with the NFC tag. The application will typically be launched in a visual mode on the user device 200, with full interactivity. The unintentional launch of one or more applications will interfere with the user's intended use of the NFC functionality of the first device 100 and the user device 200.

[0049] However, the user device 200 may also be configured to include a background service. The installation of the background service may be in tandem with the installation of an application associated with the tag emitted from the first device 100. In some examples, the background service may be part of an application associated with the tag emitted from the first device 100. The background service installed on the user device 200 may monitor the state of the user device 200. For example, the background service may monitor the state of the device, such as whether the device screen is active, whether the screen is locked or unlocked, the battery or power supply of the device, and the timing between certain actions (e.g., the time threshold between screen unlocking and tag reading). The background service may also monitor whether the application associated with the digital tag has been started. After receiving the digital tag, the mobile device may enable the application associated with the received digital tag to be started when the tag associated with the application is detected and when the appropriate state of the device collected by the background service is reviewed. Then, the background service may enable the application associated with the digital tag received by the user device 200 to be started in a special state (such as an invisible state), in which the user cannot see the interface of the application or interact with it. Thus, the user is not hindered by the launching of an application when he or she does not intend to launch the application.

[0050] As an example, when the user device 200 is within communication proximity with the first device 100 and the digital tag is read by the user device 200, the background service can act to stop the launch of the application. Compared with the state in which the user intentionally causes the user device 200 to read the digital tag, the state in which the user device 200 screen is locked and the application is launched when the digital tag is read can be considered undesirable. The background service can monitor the time difference between the unlocked screen of the user device 200 and the reading of the digital tag by the user device 200, and compare the difference with a threshold. If the difference is less than the threshold (i.e., if the time between the screen unlocking and the tag reading is too small), the launch of the application can be stopped. If the difference is greater than the threshold (i.e., if the time between the screen unlocking and the tag reading is long enough), the launch of the application can continue.

[0051] As another example, the background service can monitor and track the time each time a specific event occurs, for example, the user unlocks the screen of the user device 200. Thereafter, the background service can record the time when a digital tag (such as an NFC tag) is received on the user device 200. The background service can then compare the two times, and if the time is within a threshold, such as, for example, a short period of time of 200 milliseconds, the background service can be configured not to start the application associated with the NFC tag in a visible state, but to start the application in an invisible state. In this state, other information received by the user device 200, such as, for example, the remainder of the payload encoded in the NDEF format, can be stored by the user device 200 in a memory or storage device. Then, the application (still in an invisible state) can read the information and operate on it. For example, this information can be sent to a web service. This feature can be advantageously used to synchronize read counts between a smart card (e.g., the first device 100) and an entity that issues the smart card (e.g., an agent, a bank, or other entity).

[0052] In another example, time tracking can be used to prevent execution of a payload. For example, a background service can begin recording time after an event (e.g., power-on of user device 200 or a user unlocking the screen of user device 200), and the background service can prevent execution of the NDEF payload within a threshold time period (e.g., 10 seconds) from the time of the event. As another example, time tracking can begin when user device 200 receives a digital tag.

[0053] In another embodiment, the first device 100 may also be configured to include in its record 101 a tag attached to information typically sent by the first device, such as an AAR launch tag. The AAR launch tag may be configured to launch an application specified by the AAR launch tag once received by the user device. The tag may be configured to be first sent to the user device 200 before any other tags contained in the first device 100 are transmitted. The application may be configured to allow the application associated with the second tag to be launched only when the first tag and the second tag are received by the user device 200 within or outside a predetermined time period. For example, a typical time period of 100 milliseconds may be used, which may correspond to a typical human reaction time to tap a card to a user device. If the same pair of tags is received within this time period, the card is likely to be near the device (such as on a wallet attached to a mobile phone), and the user does not intend for the user device to respond to the tag. However, if the time period for receiving the tag is within a specific time frame, the background service or application may allow the application to be launched in a fully visible state to the user of the user device 200.

[0054] The first device 100 may also be configured to include or generate a tag set to allow a process of launching an application to be compatible across operating systems and user devices.

[0055] As another example embodiment, an NFC tag included on a smart card (e.g., first device 100) can be selectively switched or turned on or off by a user having a user device (e.g., user device 200). As an example, user device 200 may include an application that can be written to first device 100 via any of the above-mentioned communication methods. For example, user device 200 can communicate with first device 100 via NFC. User device 200 may include an application that allows a user of user device 200 to switch a signal sent from first device 100 (i.e., turn on or off, or modify the behavior of a signal sent from first device 100). This can be implemented, for example, by an application on the user device that displays NFC options included on a particular smart card. For example, the application can display the name of the smart card, some identification information about the smart card (such as, for example, the issuer of the smart card, the name on the smart card, or the number on the smart card), and a digital tag that the user may wish to turn on or off. The application can communicate with the memory of the first device 100 using NFC or other communication media on user device 200, and then write to the memory in the first device 100. For example, the application can write to the memory located at An applet on a compatible card. By writing or otherwise modifying the applet, the applet included on the first device 100 can be modified to not generate an NFC-compatible tag, such as an NDEF message, whenever the first device 100 is stimulated by, for example, a magnetic field by the user device 200. The application on the user device 200 can achieve this by writing a function to disable the generation of tags to the applet on the smart card. In some examples, the determination to turn the reading of tags on or off can be made for security purposes and based on, for example, the state of the device, location data, time, and / or other criteria.

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

[0057] As an example, a user may hold his smart card (such as the first device 100) to his The user may place their card on the back of a mobile phone (such as user device 200), or store their card in a mobile wallet close to the phone's NFC reader. An application may be installed on the phone that has been programmed to read the NFC on the card. and ("EMV") applet that can read the credit card number, personal information, CVV code, and expiration date from the card. In addition, the NFC reader can launch an application when it receives a digital tag (such as, for example, an NDEF record or an AAR launch tag).

[0058] Adding the NDEF record to the smart card does not prevent an application on the user device 200 that has been launched by the user from accessing or requesting information on the first device 100 . Applications on the operating system can be automatically launched when an event (such as the occurrence of an NFC signal) occurs. However, when no application is active on the user device 200, the NDEF record ensures that the first party application is launched in the user device 200 in response to receiving the NDEF tag. The operating system is configured to allow only one application to access information from the NFC signal at a time. This can 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, when an application has been launched by a user of the user device 200, accessing or using the application in a manner desired by the user is not prohibited.

[0059] As an example, a user may carry his or her NFC-enabled card in his or her purse or wallet. Throughout the day, the supported card may be brought into proximity with the user's personal user device, or into proximity with other NFC-enabled user devices, so that the card may be activated and read. For example, a user may have a NFC-enabled card installed on his or her device. The first device may also be configured to include a tag in its record 101, such as an AAR startup tag, which is configured to start, for example Capital on mobile If the application is not already installed on the device, the tag can be further configured to Mobile phone startup Play Store or other similar platform to allow specific apps to be installed.

[0060] NDEF tags or AAR enabled tags are configured with a specific The package name of the application. Therefore, after receiving a specific AAR launch tag or NDEF tag, the operating system or The operating system will launch the specified application when the contactless card is tapped to the phone. If the specified application is not currently installed device, it can cause The Play Store is launched into which the specified app can be downloaded and installed Device page.

[0061] The tag in the first device 100 may be further configured to cause the second device 200 to access a server to download an application associated with the tag in the first device 100. This may be accomplished by including information identifying a specific application in the first device 100. The server may be a standard server that is well known and commercially used to communicate with devices over a network. In one example, the tag in the first device may cause a specialized application to communicate with the server and cause the application to be downloaded. An example of such a specialized application is On the operating system Other examples of such apps include the App Store on the iOS operating system and the Play Store, which allows downloading Microsoft Store for apps. Another example is The Canonical Store and Ubuntu Software Center on the operating system. Other specialized package managers are available for various operating systems.

[0062] In an example embodiment, the 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 emitted from the first device 100, which reads the payload when it is activated in an invisible state. In this way, the provider of the first device 100 (such as a provider of a smart card or credit card) may be made aware of each specific use of the first device 100. For example, a credit card provider may be notified of each read of the EMV chip. Thus, the credit card provider may match the information of each read of the EMV chip with the information of known payments made by the customer. In this way, the credit card provider may use the comparison for fraud protection. In another example, the issuer of the smart card may be made aware of each read from the EMV chip, and each known read of the EMV chip may be compared with all attempts to access the information contained in the EMV chip. This information may be used to jointly synchronize counters on smart cards, such as counters on the first device and the backend service.

[0063] Figure 33 is a flow chart showing a method 300 of transmitting information from a first device 100 to a user device 200 in an example embodiment of the present invention. The method begins at step 305, where an applet or digital tag is stored on the first device 100. This applet may be configured to generate a collection or list of digital tags. These tags may be pre-generated, in which case the applet may optionally not 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 state of continuously emitting a signal. The first device 100 may receive a request for information. This step may, for example, take the form of an NFC device in the first device 100 being activated in the presence of an external field or device. This may also occur when the first device communication field 104 overlaps with another communication field. For example, when the card / chip is exposed to a properly aligned magnetic field and a request is made for a specified NDEF message, the NDEF file is read. In step 315, the first device 100 may emit a digital tag. In this step, the first device 100 may transmit additional information along with the digital tag. Examples of additional information sent with the digital tag may include user information or credit card information. In step 320, the transmitted tag may be configured in such a manner that the transmitted tag may be associated with at least one of the applications such that receipt of the transmitted tag on the second device 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. The input may also be a specific state of the user device (e.g., user device 200), where the device is in a specific state, such as the user device is unlocked, the screen of the user device is activated, or the screen is touched. The configuration of the tag may also be performed in a manner corresponding to the NDEF format or the AAR format. The AAR format is similar to the NDEF format. The operating system device is compatible and can be specified The specific action that the operating system takes when it receives an AAR launch tag. For example, it can specify a specific application to launch in response to the received tag.

[0064] Figure 4One embodiment of the present invention, namely method 400, is described. The method begins at step 405, where an applet or digital tag is stored on a first device 100. This applet may be configured to generate a collection or list of digital tags. These tags may be pre-generated, in which case the applet may optionally not 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 state of continuously transmitting a signal. The first device 100 may receive a request for information. This step may, for example, take the form of an NFC device in the first device 100 being activated in the presence of an external field or device. This may also occur when the first device communication field 104 overlaps with another communication field. For example, when the card / chip is exposed to a properly aligned magnetic field and a request is made for a specified NDEF message, 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 sent with the digital tag may include user information or credit card information. In step 420, the transmitted tag can be configured in such a way that the transmitted tag can be associated with at least one of the applications, so that the reception of the transmitted tag on the second device starts the associated application on the second device. The tag can also be further configured to be associated with an input on the second device. The input can also be a specific state of the user device (e.g., user device 200), where the device is in a specific state, such as the user device is unlocked, the screen of the user device is activated, or the screen is touched. In step 425, the transmitted tag can be configured to start the application on the second device. For example, the application can be started when the transmitted tag is received, and the payload is processed by the user device (e.g., user device 200) to cause the application to be started on the user device. In this step, the background service can record, for example, whether the screen is turned on or off, and based on this and / or receiving the transmitted tag, start a counter. For example, the background service can record the time when the screen of the user device is turned on. However, the background service does not need to be started at this step and can be started independently of this step. Step 430 includes configuring the application associated with the digital tag to start in an invisible state. In this state, the application can run but is not visible to the user. Step 435 may include configuring the application so that the launch of the application can be in a fully visible state on the user device (e.g., user device 200). This step may also include when the user device receives a request from a background service (e.g., When a tag is transmitted by a broadcast receiver, monitor the time or stop the time recording started by the background service. The time can be used as described to determine whether the application associated with the digital tag should be launched in a visible state.

[0065] Figure 5 One embodiment of the present invention, namely method 500, is described. Method 500 begins at step 505, where information is requested from a first device (e.g., first device 100) when a user device (e.g., user device 200) is physically close to the first device. This may occur when the user device 200 recognizes the presence of the first device by overlapping communication fields of the first device 100 and the user device 200. This may also occur by software in the user device 200 recognizing the presence of a communication field external to the user device 200. In step 510, a digital tag is received from the first device 100 (e.g., first device 100). The digital tag may be information that is not requested from the first device 100. The digital tag may be platform or operating system specific. In some embodiments, the digital tag may be configured as 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 application launched on the operating system may be defined by a dedicated field or metadata in the received tag. The second device may launch a package manager or application manager, such as Play Store to identify and allow the user to download the specified application. In step 520, any additional tags received by the user device can be further intercepted. In step 525, when the computer hardware arrangement (e.g., user device 200) is in a specific state, any additional digital information received from the first device can be intercepted. For example, if the mobile phone turns on its screen, it can be regarded as being in a state in a predetermined state list. This can include, for example, one or more tags associated with or sent after the first digital tag, which instructs the device receiving the tag to perform a specific action (e.g., start the application) or otherwise pass a payload to the second application. In step 530, the application launched in response to receiving the digital tag from the first device can send instructions to the first device. These instructions can disable, overwrite or deactivate one or more digital tags associated with at least one application on the first device.

[0066] Figure 6One embodiment of the present invention, namely method 600, is described. Method 600 may begin at step 605, where at least one digital tag is stored on a first device (e.g., first device 100). An applet may also be stored on the first device, which may also be configured to generate a collection or list of digital tags. These tags may be pre-generated, in which case the applet may optionally not be used to generate digital tags. The applet may also be modifiable or configurable, such as by using a flag that may indicate which digital tags the applet may generate. In step 610, a digital tag is emitted from a first device (e.g., first device 100). This may be emitted in response to an external trigger (such as an electromagnetic field), or the first device 100 may be in a state of continuously emitting a signal. This step may, for example, take the form of an NFC device of the first device (e.g., first device 100) being activated in the presence of an external field (such as a magnetic field or an electric field) from a second device (e.g., user device 200) that induces power within the first device 100. When the first device communication field (e.g., the first device communication field 104) overlaps with another communication field (such as, a communication field belonging to the second device), the NFC device may also be activated. In step 615, the tag emitted 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 enable the application to be started on the second device (e.g., the user device 200). This may be achieved by configuring the emitted tag to have a specific data format with a specified payload. For example, the digital tag may be configured as an NDEF data format specification, and may also be configured as an AAR startup tag. In step 620, the application associated with the emitted tag may be configured to be started only in a visible or invisible state, depending on the information received from the background process. For example, whenever the second device (e.g., the user device 200) is in a specific state, such as, for example, when the screen of the second device is turned on, the second device receives user input, or the second device is unlocked, or the second device is turned on, the background process may be started. In step 620, the application associated with the digital tag may be started or enabled in a visible state. In this state, the user can interact with the application on the second device (e.g., user device 200). For example, the user can interact with the second device using the touch screen of the second device. In step 625, the application can also be configured to include an option for configuring a digital tag included on a smart card (e.g., first device 100). As an example, the smart card can include a smart card operating system and further include in its memory an applet configured to generate a digital tag. The smart card can also include a communication medium, such as an NFC medium. Then, the application launched on the user device (e.g., user device 200) can cause the user device to send a command to the smart card to disable a specific digital tag to be generated based on user input.In another example, the smart card may include a flag that may prohibit the generation of a particular digital tag. Step 630 may include further configuring the application to modify the applet that generates the digital tag on the first device once it is launched in a visual state. This modification may be performed to modify a particular payload of the digital tag generated on the first device.

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

[0068] like Figure 7 As shown, for example, a computer-accessible medium 715 (e.g., a storage device such as a hard disk, a floppy disk, a memory stick, a CD-ROM, a RAM, a ROM, etc., or a collection thereof) may be provided (e.g., in communication with the processing arrangement 705). The computer-accessible medium 715 may contain executable instructions 720 thereon. Additionally, or alternatively, a storage arrangement 725 may be provided separately from the computer-accessible medium 715, which may provide instructions to the processing arrangement 705 so as to configure the processing arrangement to perform the specific exemplary procedures, processes, and methods as described above.

[0069] In addition, the exemplary processing arrangement 705 may be provided with or 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 collection probe, a sensor, etc., or any combination thereof. Figure 7 As shown, the exemplary processing arrangement 705 can communicate with the exemplary display arrangement 730, which according to certain exemplary embodiments of the present disclosure can be a touch screen configured to input information to the processing arrangement in addition to outputting information from the processing arrangement. In addition, the exemplary display arrangement 730 and / or the storage arrangement 725 can be used to display and / or store data in a user-accessible format and / or a user-readable format.

[0070] Throughout the specification and claims, the following terms have at least the meanings explicitly associated herein unless the context clearly dictates otherwise. The term "or" is intended to include "or". In addition, the terms "a", "an", and "the" mean one or more unless otherwise specified or the context clearly dictates to be directed to the singular.

[0071] In this specification, many specific details have been set forth. However, it should be understood that the embodiments of the disclosed technology can be practiced without these specific details. In other cases, in order not to obscure the understanding of this description, well-known methods, structures and techniques are not shown in detail. References to "some examples", "other examples", "an example", "example", "various examples", "an embodiment", "embodiment", "some embodiments", "example embodiments", "various embodiments", "an implementation", "implementation", "implementation", "example implementation", "various implementations", "some implementations", etc. indicate that one or more embodiments of the disclosed technology described in this way may include specific features, structures or characteristics, but not every implementation must include specific features, structures or characteristics. In addition, the repeated use of the phrase "in an example", "in an embodiment" or "in an implementation" does not necessarily refer to the same example, embodiment or implementation, although it can be so.

[0072] As used herein, unless otherwise specified, the use of ordinal adjectives "first," "second," "third," etc. to describe common objects merely indicates that different instances of similar objects are referenced and does not imply that the objects described are necessarily in a given sequence in time, space, ranking, or in any other manner.

[0073] Although certain embodiments of the disclosed technology have been described in connection with what are currently considered to be the most practical and various embodiments, it should be understood that the disclosed technology is not limited to the disclosed embodiments and 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.

[0074] This written description uses examples to disclose certain embodiments of the disclosed technology, including the best mode, and also to enable those skilled in the art to practice certain embodiments of the disclosed technology, including making and using any devices or systems and performing any combined methods. The patentable scope of certain embodiments of the disclosed technology is defined in the claims, and may include other examples that occur to those skilled in the art. Such other examples are intended to be within the scope of the claims if they have structural elements that differ from the literal language of the claims, or if they include equivalent structural elements that do not differ substantially from the literal language of the claims.

Claims

1. A method comprising: storing a digital tag on a first device, the tag being configured to be associated with at least one application on a second device such that receipt of the tag on the second device launches an application of the second device; as well as transmitting the digital tag from the first device to the second device; The application on the second device is configured to, after receiving the tag on the second device: when the second device is in at least a first state from a predetermined list of states, starting in a special state, and Within a fixed duration after receiving the digital tag, and while the second device is in at least a second state from a predetermined list of states, additional digital information from the first device is intercepted and stored in a memory of the second device.

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 near field communication field.

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 on the first device is further configured to generate a manifest of tags, which is configured to generate at least one tag in a Near Field Communication Data Exchange Format (NDEF) specification.

7. The method according to claim 6, wherein: The NDEF tag is also configured as Application Record (AAR) launch tag.

8. The method according to claim 1, wherein: The predetermined status list at least includes screen unlocking.

9. A system comprising: The computer hardware arrangement is configured as follows: receiving digital information from a first device while in physical proximity to the first device; receiving, from the first device, a digital tag configured to be associated with an application; In response to the tag, launching an application associated with the received digital tag; and Within a fixed duration after receiving the digital tag, and when the computer hardware arrangement is in at least one state in a predetermined list of states, additional digital information from the first device is intercepted by the application and stored in a memory of the second device.

10. The system according to claim 9, wherein: The launched application is configured to send an instruction to the first device, the instruction disabling or deactivating a digital tag configured to be associated with the application.

Images