Method and system for adaptive transceiver in mobile device

Abstract

A method using a mobile device is disclosed. The mobile device includes a contactless application including a bridge module and a computer readable medium including a contactless kernel, wherein the contactless kernel includes a transceiver interface coupled to a processor. The mobile device includes a contactless element coupled to the processor. The method includes receiving a trigger signal indicating a transaction to be performed. In response to receiving the trigger signal, the contactless kernel sends first data to the bridge module. The contactless kernel is operable in a first communication mode. The bridge module transforms the first data in the first communication mode to first data in a second communication mode and passes the first data to the contactless element. The contactless element sends the first data to a user device and subsequently receives second data from the user device to perform the transaction.

Description

[0001] Cross-referencing related applications

[0002] This application claims the benefit of U.S. Provisional Application No. 62 / 972,511, filed on February 10, 2020, which is incorporated herein by reference in its entirety for all purposes. Background Technology

[0003] Technology has evolved to enable contactless payment card transactions. Traditional point-of-sale (POS) terminals can communicate with payment cards using short-range wireless technologies such as Near Field Communication (NFC) and Radio Frequency Identification (RFID). Typically, POS terminals develop a kernel to communicate directly with contactless devices such as NFC readers and NFC adapters. For example, the kernel is developed based on a specific type of hardware platform that hosts the contactless device. Therefore, the kernel can only operate with respect to that specific type of hardware platform.

[0004] Recently, the number of deployed POS terminals has surged. Different POS terminals can employ different hardware platforms and programming interfaces. Therefore, different kernels will be developed to communicate with contactless devices deployed on each different type of hardware platform. This approach is clearly not scalable. The embodiments of this disclosure individually and collectively address these and other problems. Summary of the Invention

[0005] According to one embodiment, a method using a mobile device is provided, the mobile device including an application and a computer-readable medium, the application including a bridging module, the computer-readable medium including a contactless kernel, the contactless kernel including a transceiver interface coupled to a processor, and the mobile device including a contactless element coupled to the processor. The method includes: receiving a trigger signal indicating a transaction to be executed; in response to receiving the trigger signal, the contactless kernel sending first data to the bridging module; the contactless kernel being operable in a first communication mode; the bridging module transforming the first data in the first communication mode into the first data in a second communication mode; the bridging module passing the first data in the second communication mode to the contactless element, whereby the contactless element sends the first data to a user device; and the contactless element receiving second data from the user device to execute the transaction.

[0006] Another embodiment provides a mobile device including: a processor; and a non-transient computer-readable medium coupled to the processor, the non-transient computer-readable medium including code executable by the processor for implementing a method including receiving a trigger signal indicating a transaction to be executed. In response to receiving the trigger signal, a contactless core sends first data to a bridging module. The contactless core is operable in a first communication mode. The bridging module transforms the first data in the first communication mode into the first data in a second communication mode. The bridging module transmits the first data in the second communication mode to the contactless element, whereby the contactless element sends the first data to a user device. The contactless element receives second data from the user device to execute the transaction.

[0007] Another embodiment provides a system including a first mobile device and a second mobile device. The first mobile device includes: a first contactless core, the first contactless core including a first transceiver interface coupled to a first processor, the first contactless core being operable in a first communication mode; a first contactless element, the first contactless element being coupled to the first processor and deployed on a first platform of the first mobile device, the first contactless element being operable in a second communication mode; and a first application, the first application including a first bridging module, the first bridging module being implemented by the first processor and programmed to cause the first processor to: transform information received from the first contactless core in the first communication mode into information in the second communication mode; and transmit the information transformed into the second communication mode to the first contactless element. The second mobile device includes: a second contactless core, the second contactless core including a second transceiver interface coupled to a second processor, the second contactless core being operable in a first communication mode; a second contactless element, the second contactless element being coupled to the second processor and deployed on a second platform of the second mobile device, the second contactless element being operable in a third communication mode; and a second application, the second application including a second bridging module, the second bridging module being implemented by the second processor and programmed to cause the second processor to: transform information received from the second contactless core in the first communication mode into information in the third communication mode; and transmit the information transformed into the third communication mode to the second contactless element, wherein the first contactless core and the second contactless core are identical, and the first transceiver interface and the second transceiver interface are identical.

[0008] These and other embodiments are described in further detail below with reference to the accompanying drawings and specific implementation details. Attached Figure Description

[0009] Figure 1 A block diagram of the system according to an embodiment is depicted.

[0010] Figure 2 A block diagram depicts a mobile device and a user device according to an embodiment.

[0011] Figures 3A-3C An exemplary configuration of a contactless core communicatively coupled to a contactless element, according to some embodiments, is depicted.

[0012] Figure 4 A flowchart illustrating a method performed by a mobile device according to an embodiment is shown. Detailed Implementation

[0013] Embodiments of this disclosure provide an adaptive transceiver. Specifically, embodiments of this disclosure provide a contactless kernel including a transceiver that can be used as a general-purpose contactless kernel. In other words, the general-purpose contactless kernel can operate in multiple mobile devices, each of which may include contactless components deployed on different hardware platforms.

[0014] Before discussing specific embodiments of the invention, some descriptions of certain terms may be useful.

[0015] "User" can include an individual. In some embodiments, a user can be associated with one or more personal accounts and / or portable devices. In some embodiments, a user can also be referred to as a cardholder, account holder, or consumer.

[0016] A “user device” can be any suitable device that can be used by a user (e.g., a payment card or mobile phone). A user device can take any suitable form. Some examples of user devices include cards with magnetic stripes or contactless elements (e.g., payment cards such as debit cards, credit cards, and prepaid cards), cellular phones, PDAs, personal computers (PCs), tablet computers, etc. In some embodiments where the user device is a mobile device, the mobile device may include a display, memory, processor, computer-readable medium, and any other suitable components.

[0017] A “mobile device” (sometimes referred to as a mobile communication device) can include any electronic device that a user can transport or operate, and that also provides the ability to communicate remotely with a network. A mobile communication device can communicate using mobile phone (wireless) networks, wireless data networks (e.g., 3G, 4G, or similar networks), Wi-Fi, Bluetooth, Bluetooth Low Energy (BLE), Wi-Max, or any other communication medium that provides access to networks such as the Internet or private networks. Examples of mobile devices include mobile phones (e.g., cellular phones), PDAs, tablet computers, netbooks, laptops, wearable devices (e.g., watches), vehicles (e.g., cars and motorcycles), personal music players, handheld dedicated readers, etc. A mobile device can include any suitable hardware and software for performing such functions, and can also include multiple devices or components (e.g., when a device remotely accesses a network by being attached to another device—that is, using another device as a modem—two devices used together can be considered a single mobile device).

[0018] "Contactless" communication can be communication that exchanges data between two devices without the two devices being physically coupled. Without limiting the generality of the foregoing, "contactless" communication can include data transmission via near field communication (NFC) transceivers, laser, radio frequency, infrared communication or other radio frequency or wireless communication protocols, such as Bluetooth, Bluetooth Low Energy (BLE), Wi-Fi, iBeacon, etc.

[0019] "Interaction" can include reciprocal effects or influences. "Interaction" can include communication, contact, or exchange between parties, devices, and / or entities. Example interactions include transactions between two parties and data exchange between two devices. In some embodiments, an interaction can include a payment transaction in which devices may interact to facilitate the payment.

[0020] "Interaction data" can include data related to an interaction. In some embodiments, interaction data can be transaction data. Transaction data can include multiple data elements having data values ​​associated with a transaction. In some embodiments, interaction data can include identifiers, credentials, amounts, dates, times, etc.

[0021] "Interactive input messages" can be communications received during an interaction. For example, a message sent by an access device or resource provider device can be an interactive input message for receiving a portable device. An example of an interactive input message may include an Application Protocol Data Unit (APDU) command.

[0022] An "interactive output message" can be a communication sent during an interaction in response to an interactive input message. An example of an interactive output message can include an APDU response sent by a mobile device in response to receiving an APDU command.

[0023] A “module” can include a set of standardized components or individual units that can be used to build more complex structures. In some embodiments, a module can include any one of many different but interconnected units from which procedures can be built or complex activities can be analyzed.

[0024] A “kernel” can include the core of an operating system. In some embodiments, the kernel can include interface routines, security and control functions, and logic for managing a set of commands and responses to retrieve necessary data from, for example, a mobile device to complete an interaction. In some embodiments, kernel processing can encompass interactions with the portable device between selecting a portable device application (exclusion) and processing the results of the interaction (exclusion).

[0025] A "resource provider" can be an entity capable of providing resources such as goods, services, information, and / or access to a location (e.g., a parking space, a transfer terminal, etc.). Examples of resource providers include businesses, government agencies, and secure data providers. A resource provider may operate one or more resource provider computers.

[0026] An "acquiring party" can typically be a business entity that has a business relationship with a particular merchant or other entity (e.g., a commercial bank). Some entities can perform the functions of both an issuer and an acquirer. Some embodiments may cover such a single entity as an issuer-acquiring party. The acquirer can operate an acquiring party computer, which may also generally be referred to as a "transfer computer".

[0027] An "authorizing computer" or "authorizing entity computer" can include any system involved in transaction authorization. The authorizing computer can determine whether a transaction can be authorized and can generate an authorization response message that includes the authorization status (also known as an authorization decision). In some embodiments, the authorizing computer can be a payment account issuer computer. In some cases, the authorizing computer can store contact information for one or more users. In other embodiments, the authorizing computer can authorize non-financial transactions involving users. For example, the authorizing computer can make an authorization decision regarding whether a user can access a resource. In some cases, the authorizing computer can be a content provider server computer associated with a content provider entity that manages one or more resources accessible to users. The authorizing computer can be referred to as an authorizing entity computer. The authorizing computer may include an "access control server" that can be configured to authenticate users.

[0028] An "authorization request message" can be an electronic message requesting authorization for a transaction. In some embodiments, the message is sent to the issuer of a payment processing network and / or a payment account to request authorization for a payment transaction. Authorization request messages according to some embodiments may conform to ISO 8583, a standard for systems for exchanging information about electronic transactions associated with payments made by consumers using payment devices or payment accounts. Authorization request messages may also include additional data elements corresponding to "identification information," including, for example, service codes, CVVs (card verification values), dCVVs (dynamic card verification values), expiration dates, etc. Authorization request messages may also include "transaction data," such as any information associated with the current transaction (e.g., transaction amount, merchant identifier, merchant location, etc.) and any other information that can be used to determine whether to identify and / or authorize the payment transaction.

[0029] An "authorization response message" can be a response to an authorization request message. In some embodiments, the authorization response message can be an electronic message response to an authorization request message generated by an issuing financial institution (i.e., the issuer) or a payment processing network. According to some embodiments, the authorization response message may conform to ISO 8583, a standard for systems for exchanging electronic transaction information associated with payments made by consumers using payment devices or payment accounts. The authorization response message may include an authorization code, which can be a code returned by the account issuing bank to the merchant's access device (e.g., a point-of-sale terminal) in response to an authorization request message in an electronic message, indicating approval of the transaction (whether directly or via the payment processing network). The code can serve as evidence of authorization. As described above, in some embodiments, the payment processing network may generate and / or forward authorization response messages to the merchant.

[0030] A "payment credential" may include any suitable information associated with an account (e.g., payment account and / or payment device associated with the account). This information may be directly related to the account or derived from account-related information. Instances of account information may include PAN (primary account number or "account number"), username, expiry date, CVV (card verification value), dCVV (dynamic card verification value), CVV2 (card verification value 2), CVC3 card verification value, and so on. CVV2 is generally understood to be a static verification value associated with a payment device. CVV2 values ​​are typically visible to the user (e.g., a consumer), while CVV and dCVV values ​​are typically embedded in memory or authorization request messages and are not easily known to the user (although they are known to the issuer and payment processor). A payment credential may be any information identifying a payment account or associated with a payment account. A payment credential can be provided to make payments from a payment account. A payment credential may also include a username, expiry date, gift card number or code, and any other suitable information.

[0031] A "token" can be an alternative value for a credential. A token can be a string of numbers, letters, or any other suitable characters. Instances of tokens include access tokens, such as payment tokens, and data that can be used to access a secure system or location.

[0032] A "server computer" or "back-end server computer" can include a powerful computer or cluster of computers. For example, a server computer can be a mainframe, a small cluster of computers, or a group of servers that work like cells. In one instance, a server computer can be a database server coupled to a web server. A server computer can include one or more computing devices and can use any of a variety of computing architectures, arrangements, and compilations to serve requests from one or more client computers.

[0033] "Processor" can refer to any suitable one or more data computing devices. A processor can include one or more microprocessors that work together to perform the desired function. A processor can include a CPU, which includes at least one high-speed data processor sufficient to execute program components for performing user and / or system-generated requests. A CPU can be a microprocessor, such as AMD's Athlon, Duron, and / or Opteron; IBM and / or Motorola's PowerPC; IBM and Sony's Cell processors; Intel's Celeron, Itanium, Pentium, Xeon, and / or XScale; and / or similar processors.

[0034] "Memory" can be any suitable one or more devices capable of storing electronic data. Suitable memory may include non-transient computer-readable media whose storage contains instructions executable by a processor to implement a desired method. Instances of memory may include one or more memory chips, disk drives, etc. Such memory can be operated using any suitable electrical, optical, and / or magnetic modes of operation.

[0035] Figure 1 A block diagram of a system 100 including several components according to embodiments of the present disclosure is depicted. System 100 includes a user 101 operating a user device 103 communicatively coupled to a mobile device 102. For clarity, Figure 1 A specific number of components are shown. It should be understood that embodiments of this disclosure may include more than one of each component.

[0036] In some embodiments, mobile device 102 may include multiple service provider applications, such as mobile wallet applications, payment applications, or access applications, which may be pre-configured with access data to enable user device 103 to conduct transactions. For example, according to one embodiment, mobile device 102 may be used as a point-of-sale terminal, and user 101 may use user device 103, such as a credit card or debit card, to pay for goods or services by performing a tap operation of user device 103 relative to mobile device 102. In some embodiments, user device 103 may communicate operationally with mobile device 102 via contactless or contact communication. User device 103 may communicate via, for example, NFC (Near Field Communication), Bluetooth, etc. TM Low-power Bluetooth TM The mobile device 102 communicates with short-range contactless communication modes such as BLE and Wi-Fi. In some embodiments, the contactless communication mode may also include the use of audible signals and optical signals.

[0037] As described above, the user device 103 according to some embodiments may be in the form of a card, such as a credit card or debit card. In these cases, the user device 103 includes a substrate, such as a plastic substrate. A contactless element for connection to a data access or data transmission device may be on or embedded within the substrate of the user device. The contactless element may include a chip and be capable of transmitting and transferring data using Near Field Communication (NFC) technology or other short-range communication technologies. The user device 103 may also include a memory that can store user information such as account number, expiration date, and username. Such information may also be printed or embossed on the substrate. The substrate may also include a magnetic stripe that the user can use to perform a card swipe operation at a point-of-sale terminal.

[0038] Figure 2 Block diagrams of a mobile device and a user device according to embodiments are depicted. The mobile device 102 may include a processor 102A (e.g., a microprocessor) for processing functions of the mobile device 102 and a display 102G for allowing a user to view information. The mobile device 102 may also include input elements 102E (e.g., a touchscreen, keyboard, touchpad, biometric sensor, etc.), a speaker 102H, and a microphone 102F, each operatively coupled to the processor 102A. A contactless component interface 102J, an antenna 102D, a memory 102C, and a computer-readable medium 102B may also be operatively coupled to the processor 102A.

[0039] Computer-readable medium 102B and memory 102C may reside within body 102P. Body 102P may take the form of a plastic substrate, housing, or other structure. In some cases, memory 102C may be a security element and / or may also store information such as access data, including tokens, PANs, etc. Information in memory 102C may be transmitted by mobile device 102 to another device using antenna 102D or contactless component interface 102J. Mobile device 102 may use antenna 102D for wireless data transmission (e.g., using wireless networking protocols such as IEEE 802.11) or mobile phone communication (e.g., 3G, 4G, and / or LTE). Antenna 102K of contactless component interface 102J may be configured to transmit and receive wireless signals at frequencies specified by different wireless protocols such as NFC (Near Field Communication), BLE (Bluetooth Low Energy), RFID (Radio Frequency Identification), or any other suitable form of short- or mid-range communication mechanism.

[0040] In some embodiments, the contactless component interface 102J is implemented in the form of a semiconductor chip (or other data storage element) having associated wireless transmission (e.g., data transmission) elements, such as an antenna. Data or control commands transmitted via a cellular network can be applied to the contactless component interface 102J. The contactless component interface 102J is capable of transmitting and receiving data using short-range wireless communication capabilities. Therefore, the mobile device 102 is capable of transmitting and receiving data or control commands via a cellular network (or any other suitable wireless network, such as the Internet or other data networks) or any short-range communication mechanism.

[0041] Computer-readable medium 102B may include code executable by a processor for implementing a method according to an embodiment. For example, computer-readable medium 102B may include code executable by processor 102A for implementing a method comprising: receiving a trigger signal indicating a transaction to be executed; in response to receiving the trigger signal, sending first data to a bridging module by a contactless kernel, wherein the contactless kernel is operable in a first communication mode; the bridging module transforming the first data in the first communication mode into the first data in a second communication mode; the bridging module passing the first data in the second communication mode to the contactless element, whereby the contactless element sends the first data to a user device; and the contactless element receiving second data from the user device to execute the transaction. The bridging module described above is a module implemented by processor 102A and embedded within an application on mobile device 102. See later. Figures 3A-3C Describe the details related to the bridging module.

[0042] Computer-readable medium 102B may contain one or more service provider applications 102B-1-102B-n. The service provider applications 102B-1-102B-n may be combined with processor 102A to allow mobile device 102 to communicate with various service provider computers. Each application provides functionality provided by its respective service provider. Examples of service provider applications may include digital wallet applications, payment applications (e.g., mobile banking applications designed and maintained by a bank or payment processing network), merchant applications (e.g., applications enabling users to participate in loyalty reward programs), switching applications (e.g., applications storing credit limits from prepaid cards), ticketing applications (e.g., applications storing pre-purchased tickets for accessing events or locations), and so on.

[0043] User device 103 includes a processor 103A. Processor 103A is operatively coupled to a memory 103C that may include a device type identifier, a contactless element interface 103B that may include an antenna 103K, and a communication port 103E. Contactless element interface 103B is configured to communicate (send and / or receive data) with contactless element interface 102K of mobile device 102. In one embodiment, communication port 103D includes hardware to facilitate wireless network communication (e.g., IEEE 802.11). In one embodiment, the user device identifier may be an Access Device Type Identifier (ADTI) that identifies one or more functions of the access device (e.g., the ability to process specific proprietary message formats, the ability to provide enhanced services such as typical payment transactions (e.g., loyalty reward programs offered by specific merchants)) and / or the types of behavior that user device 103 allows and / or expects mobile device 102 to support.

[0044] As mentioned earlier, when a contactless kernel deployed in a mobile device communicates with contactless components of the mobile device, the contactless kernel is developed (in advance) based on criteria associated with the contactless components. For example, a contactless kernel can be developed based on a specific type of mobile platform that hosts contactless components. Therefore, there is a one-to-one relationship between the contactless kernel and the contactless components. In other words, the contactless kernel is specifically developed for the type of mobile platform that hosts the contactless components.

[0045] In this scenario, consider the need to develop a contactless kernel to communicate with different contactless components (e.g., three contactless components, each deployed on a different mobile platform). In this case, three different instances of the contactless kernel would need to be developed to communicate with the different contactless components respectively. Therefore, the aforementioned technique for deploying a contactless kernel is not scalable. Below, mechanisms for addressing the aforementioned scalability problem are described according to embodiments of this disclosure.

[0046] Now refer to Figures 3A-3C The document describes an exemplary configuration of a contactless core that is communicatively coupled to a contactless element of a mobile device, according to some embodiments.

[0047] refer to Figure 3A The image depicts a contactless core 310 including a transceiver interface 305. The contactless core 310 is configured to communicate with contactless components deployed on a platform of a mobile device. For example, such as... Figure 3A As shown, the contactless element may include an NFC (Near Field Communication) API 331, an NFC driver 333, and NFC hardware 335. The NFC API 331 and NFC driver 333 may be deployed on a mobile platform 330. For simplicity, a type of mobile platform with the NFC API and NFC driver deployed is referred to as a type A mobile platform. The contactless element of the mobile device can be configured to transmit and receive wireless signals at frequencies specified by different wireless protocols, such as NFC, BLE (Bluetooth Low Energy), RFID (Radio Frequency Identification), or any other suitable form of short-range or mid-range communication mechanism. For example, the contactless element can exchange messages, such as Application Protocol Data Unit (APDU) messages, with a user device communicatively coupled to the mobile device.

[0048] Additionally, the mobile device includes a contactless application (A) 320, such as a tap-to-pay application installed therein. The contactless application 320 includes a bridging module 315. The bridging module 315 is configured to implement a transceiver interface 305 and form a communication channel between the contactless core 310 and contactless components deployed on the mobile platform 330, as described below.

[0049] Figure 3B The configuration described in the text is different Figure 3A This configuration is because Figure 3B The bridging module 315 resides within another application (B) 321 installed on the mobile device. It should be noted that contactless components (i.e., NFC API 331, NFC driver 333, and NFC hardware 335) are deployed on the mobile platform 330, which is connected to… Figure 3A The mobile platform is the same. See also... Figure 3C The configuration depicts another contactless application (C) 351, which includes a bridging module 357 deployed on a mobile device. The bridging module 357 communicates with contactless components (i.e., NFC API 361, NFC driver 363, and NFC hardware 365) deployed on a mobile platform (B) 360, which is different from... Figure 3A and 3B Mobile platform 330.

[0050] exist Figures 3A to 3C In the above configuration, the contactless core 310 is developed to operate in a first communication mode. Specifically, the transceiver interface 305 within the contactless core 310 is designed independently of the type of contactless element with which the contactless core wishes to communicate. Therefore, in Figures 3A to 3C In this configuration, the contactless kernel can be used to send / receive information in a first communication mode. It should be noted that the first communication mode can be associated with a first messaging format used by the contactless kernel when transmitting information.

[0051] To enable uninterrupted communication between the contactless core and different types of contactless components, such as different NFC APIs deployed on different mobile platforms, a bridging module (e.g., 315 or 357) is configured to receive data transmitted from the contactless core in a first communication mode and transform the received data to a second communication mode. According to some embodiments, the bridging module determines the second communication mode based on the type of the contactless component, such as the type of NFC interface, the type of NFC driver, the type of mobile platform on which the contactless component is deployed, etc. Therefore, the bridging module ensures that information received from the contactless core in the first communication mode is transformed into a communication mode compatible with the contactless component (e.g., the second communication mode). It should be noted that the second communication mode may differ from the first communication mode. When transforming data from the first communication mode to the second communication mode, according to some embodiments, the bridging module may transform (i.e., change) the data's message transmission format from the first message transmission format (i.e., the format associated with the data transmitted from the contactless core to the bridging module) to the second message transmission format associated with the second communication mode. The transformed data in the second message transmission format is then sent by the bridging module to the contactless component.

[0052] In this way, the contactless kernel is a universal contactless kernel capable of operating in multiple mobile devices, each including different types of contactless components. For example, a contactless kernel operable in a first communication mode can be deployed in a first mobile device to communicate with a contactless component operable in a second communication mode (i.e., the contactless component is deployed on a first type of mobile platform). The same contactless kernel can be deployed on a second mobile device to communicate with different contactless components operable in a third communication mode, i.e., the different contactless components are deployed on a second type of mobile platform, which is different from the first type of mobile platform. Therefore, in embodiments of this disclosure, a single contactless kernel can be developed for different mobile devices, independent of the underlying mobile platform and / or application programming interface. Thus, a single contactless kernel (operable in a first communication mode) along with a bridging module (configured to transform the first communication mode into different communication modes) can solve the transceiver scalability problem previously stated.

[0053] Figure 4 A flowchart illustrating a method performed by a mobile device according to an embodiment is depicted. Specifically, Figure 4 The method 400 described corresponds to using a mobile device as a point-of-sale terminal and conducting contactless transactions with a user device holding a card, such as a credit card or debit card. Furthermore, the mobile device can be a mobile phone, such as an Android phone or an iOS phone. Additionally, for clarity, this document uses... Figure 4 You can also refer to the discussion. Figure 2 and Figure 3A Some of the components.

[0054] The method begins at step S410, where the mobile device receives a trigger signal from the user device. The trigger signal indicates a transaction to be executed. The trigger signal may correspond to a signal received by the mobile device when it detects the user device at a location extremely close to the mobile device (i.e., within a threshold distance). Furthermore, as referenced... Figure 2 The mobile device and the user device can communicate in a contactless manner via contactless component interfaces 102J and 103B, respectively. Furthermore, the mobile device can detect the user device, for example, when a user performs a touch operation on the user device, i.e., by touching the user device with a reader within the mobile device.

[0055] In response to receiving the signal, in step S420, the contactless core sends first data to the bridging module. The first data can be sent in a first communication mode, i.e., in a first message passing format. For example, refer to... Figure 3AThe contactless kernel 310 can send first data to the bridging module 315. The first data may correspond to, for example, a request message indicating a request for certain information from the user device, such as an identifier, account information, etc. It should be noted that the contactless kernel 310 wishes to communicate with the contactless components of the mobile device (i.e., NFC API 331, NFC driver 333, and NFC hardware 335) so that the request can be relayed to the user device via the contactless components.

[0056] The contactless component of the mobile device can operate in a second communication mode, i.e., associated with a second messaging format, which differs from the first messaging format of the contactless core. Therefore, in step S430, the bridging module 315 transforms the first data (i.e., the request) from the first communication mode to a second communication mode compatible with the contactless component. In step S440, the bridging module 315 transmits the transformed first data in the second communication mode to the contactless component.

[0057] The method then proceeds to step S450, where the contactless element transmits first data (in a second communication mode) to the user device. It should be understood that communication between the mobile device and the user device can be a short-range contactless communication mode, such as NFC (Near Field Communication) or Bluetooth. TM Low-power Bluetooth TM (BLE), Wi-Fi, etc. In step S460, the contactless component of the mobile device receives second data from the user device. According to some embodiments, the second data may correspond to data sent by the user device in response to receiving the first data (i.e., a request message). Furthermore, the second data may correspond to, for example, user information, payment tokens, etc. The received second data may be forwarded to a bridging module, which further transforms the data from a second communication mode to a first communication mode. The bridging module may then forward the transformed information to the contactless kernel for further transaction processing.

[0058] While some of the specific embodiments described above are in the context of mobile devices that can accept or receive data in the form of a payment card from a user device, the embodiments of this disclosure are not limited thereto. For example, embodiments of this disclosure can be used with mobile devices that can act as access terminals to allow access to secure locations such as venues (e.g., theaters) and transfer terminals, or to secure data (e.g., public information machine type devices that allow users to access data stored on a remote server).

[0059] The following describes an exemplary payment transaction flow associated with a transaction performed by a user through interaction with a mobile device using a user device. Specifically, a user can pay for goods or services using a user device, such as a credit card or debit card, by performing a tap operation of the user device relative to the mobile device. The tap payment application installed on the mobile device executes and completes the transaction, as described below.

[0060] As described in the embodiments of this disclosure, multiple software modules can process transactions initiated by a user. To complete the payment associated with the transaction, the mobile device can communicate with the authorized entity computer (operated by the issuer) via a transmission computer (operated by the acquirer) and a processing network such as a payment processing network.

[0061] A payment processing network may include data processing subsystems, networks, and operations for supporting and delivering authorization services, exception handling services, and clearing and settlement services. An exemplary payment processing network may include VisaNet. TM Payment processing networks such as VisaNet TM It can process credit card transactions, debit card transactions, and other types of business transactions. VisaNet TM This includes, in particular, the VIP system (Visa Integrated Payment System) for processing authorization requests and the Base II system for performing clearing and settlement services. The payment processing network can use any suitable wired or wireless network, including the Internet.

[0062] In response to a user tapping action—specifically, tapping the user device on the mobile device—interaction initiation data is transmitted from the user device to the mobile device. The interaction initiation data received by the mobile device may correspond to a transaction identifier, PAN, payment token, verification value, expiration date, etc. The interaction initiation data is received by the mobile device via a contactless interface. The mobile device utilizes multiple software modules to process the transaction. To process the payment associated with the transaction, the mobile device may then generate an authorization request message, which includes the information received from the user device (i.e., the interaction initiation data) and additional transaction information (e.g., transaction amount, merchant-specific information, etc.), and send this information electronically to a transmission computer. The transmission computer can then receive, process, and forward the authorization request message to the processing network for authorization.

[0063] Generally, prior to a credit or debit card transaction, the processing network has an agreement with each authorizing computer regarding how the transaction will be authorized for the issuer. In some cases, such as when the transaction amount is below a threshold, the processing network can be configured to authorize the transaction based on its information about the user account without generating and sending an authorization request message to the authorizing entity computer. In other cases, such as when the transaction amount is above a threshold, the processing network can receive the authorization request message, identify the issuer associated with the user device, and forward the authorization request message for the transaction to the authorizing entity computer for verification and authorization. Once the transaction is authorized, the authorizing entity computer can generate an authorization response message (which may include an authorization code indicating that the transaction is approved or rejected) and send this electronic message to the processing network via the authorizing entity computer's external communication interface. The processing network can then forward the authorization response message to a transmission computer, which can subsequently send an electronic message including the authorization indication to the mobile device. The mobile device can then send this information to the user device.

[0064] According to some embodiments, if the access data is in the form of a token, the processing network can exchange the token for a real credential (e.g., a PAN). Any authorization request message can then be modified to include the real credential, and the authorization request message can be forwarded to the authorizing entity computer for verification. The authorizing entity computer can generate an authorization response message with approval or rejection. The authorization response message can be sent to the processing network, and the processing network can replace the credential with the token. The processing network can then send the authorization response message back to the mobile device. At the end of the day or at some other suitable time, a clearing and settlement process can be performed on the transaction between the resource computer, the transmission computer, the processing network, and the authorizing entity computer.

[0065] It should be understood that the present invention described above can be implemented in a modular or integrated manner using computer software in the form of control logic. Based on this disclosure and the teachings provided herein, those skilled in the art will know and understand other ways and / or methods of implementing the present invention using hardware and combinations of hardware and software.

[0066] Any software component or function described in this application may be implemented as software code executed by a processor using any suitable computer language, such as Java, C++, or Perl, using conventional or object-oriented technologies. The software code may be stored as a series of instructions or commands on a computer-readable medium, such as random access memory (RAM), read-only memory (ROM), magnetic media such as a hard disk drive or floppy disk, or optical media such as a CD-ROM. Any such computer-readable medium may reside on or within a single computing device, and may exist on different computing devices or within a system or network.

[0067] While certain exemplary embodiments have been described in detail and shown in the accompanying drawings, it should be understood that such embodiments are merely illustrative of the invention and not limiting, and that the invention is not limited to the specific arrangements and constructions shown and described, as various other modifications will be apparent to those skilled in the art.

[0068] As used herein, unless explicitly indicated otherwise, the use of “a” or “the” is intended to mean “at least one”.

Claims

1. A method using a mobile device, the mobile device including a contactless application, the contactless application including a bridging module and a contactless kernel, the contactless kernel including a transceiver interface coupled to a processor, the mobile device including contactless elements coupled to the processor, the method comprising: Receive a trigger signal from the user device indicating a transaction to be executed; In response to receiving the trigger signal, the contactless kernel included in the contactless application installed on the mobile device sends first data to the bridging module, the contactless kernel being capable of operating in a first communication mode; The bridging module transforms the first data in a first message passing format associated with the first communication mode into the first data in a second message passing format associated with the second communication mode. The bridging module transmits the first data, in the second message transmission format associated with the second communication mode, to the contactless element deployed on the platform running on the mobile device. The first data is transmitted to the user device by the non-contact element; as well as The contactless element receives second data from the user device to execute the transaction, wherein the first message transmission format is different from the second message transmission format.

2. The method of claim 1, wherein the bridging module determines the second communication mode at least in part based on the type of the contactless element.

3. The method of claim 1, wherein the contactless element comprises an NFC API, an NFC driver, and an antenna.

4. The method of claim 1, wherein the trigger signal corresponds to the detection of the user device near the mobile device.

5. The method according to claim 1, wherein the first communication mode is different from the second communication mode.

6. The method of claim 1, wherein the user device is a card and the mobile device is a mobile phone.

7. The method of claim 1, wherein the first communication mode is associated with a first messaging format and the second communication mode is associated with a second messaging format, wherein the first messaging format is different from the second messaging format.

8. The method of claim 1, wherein the transaction is an access transaction for accessing a secure location.

9. A mobile device, comprising: processor; as well as A non-transient computer-readable medium coupled to the processor, the non-transient computer-readable medium including code executable by the processor for implementing methods including the following: Receive trigger signals indicating that a transaction is pending execution; In response to receiving the trigger signal, a first data is sent to the bridging module by a contactless kernel included in a contactless application installed on the mobile device, the contactless kernel being capable of operating in a first communication mode; The bridging module transforms the first data in a first message passing format associated with the first communication mode into the first data in a second message passing format associated with the second communication mode. The bridging module transmits the first data, in the second message transmission format associated with the second communication mode, to a contactless element deployed on the platform running on the mobile device. The first data is transmitted to the user device by the non-contact element; as well as The contactless element receives second data from the user device to execute the transaction, wherein the first message transmission format is different from the second message transmission format.

10. The mobile device of claim 9, wherein the contactless element comprises at least an NFC API, an NFC driver, and an antenna.

11. The mobile device of claim 9, wherein the bridging module determines the second communication mode at least in part based on the type of the contactless element.

12. The mobile device according to claim 9, wherein the first communication mode is different from the second communication mode.

13. The mobile device of claim 9, wherein the contactless core is a universal contactless core capable of operating in a plurality of mobile devices, each of the plurality of mobile devices comprising a different type of contactless element.

14. A system comprising: A first mobile device, the first mobile device comprising: A first contactless core, the first contactless core including a first transceiver interface coupled to a first processor, the first contactless core being operable in a first communication mode; A first contactless element, coupled to the first processor and deployed on a first platform of the first mobile device, is operable in a second communication mode; and A first contactless application, the first contactless application including a first bridging module, the first bridging module being implemented by the first processor and programmed to cause the first processor to: Information received from the first contactless kernel included in the first contactless application is transformed from a first messaging format associated with the first communication mode to information according to a second messaging format associated with the second communication mode; and Sending information, converted to the second messaging format associated with the second communication mode, to the first contactless element; and A second mobile device, the second mobile device comprising: The second contactless core includes a second transceiver interface coupled to the second processor, and the second contactless core is capable of operating in the first communication mode. A second contactless element, coupled to the second processor and deployed on a second platform of the second mobile device, is operable in a third communication mode; and A second contactless application, the second contactless application including a second bridging module, the second bridging module being implemented by the second processor and programmed to cause the second processor to: Information received from the second contactless kernel included in the second contactless application is transformed from the first messaging format associated with the first communication mode to information according to the third messaging format associated with the third communication mode; and Information is converted to the third messaging format associated with the third communication mode and sent to the second contactless element, wherein the first contactless core and the second contactless core are the same, and the first transceiver interface and the second transceiver interface are the same.

15. The system of claim 14, wherein the first platform of the first mobile device is different from the second platform of the second mobile device.

16. The system of claim 14, wherein the second communication mode is different from the third communication mode.

17. The system of claim 14, wherein the first mobile device further comprises a third contactless application, the third contactless application comprising a third bridging module implemented by the first processor and programmed to cause the first mobile device to: Transform information received from the first contactless kernel in the first message passing format associated with the first communication mode into information in the second message passing format associated with the second communication mode; and Information is converted to the second messaging format associated with the second communication mode and sent to the first contactless element.

18. The system of claim 14, wherein the second mobile device further comprises a fourth contactless application, the fourth contactless application comprising a fourth bridging module implemented by the second processor and programmed to cause the second mobile device to: Transform information received from the second contactless kernel according to the first messaging format associated with the first communication mode into information according to the third messaging format associated with the third communication mode; and The information, transformed into the third messaging format associated with the third communication mode, is sent to the second contactless element.

Images