WO2010118612A1 - 一种安装非接触支付应用的方法、智能卡及移动终端 - Google Patents

一种安装非接触支付应用的方法、智能卡及移动终端 Download PDF

Info

Publication number
WO2010118612A1
WO2010118612A1 PCT/CN2009/075680 CN2009075680W WO2010118612A1 WO 2010118612 A1 WO2010118612 A1 WO 2010118612A1 CN 2009075680 W CN2009075680 W CN 2009075680W WO 2010118612 A1 WO2010118612 A1 WO 2010118612A1
Authority
WO
WIPO (PCT)
Prior art keywords
payment application
contactless payment
smart card
communication standard
card
Prior art date
Application number
PCT/CN2009/075680
Other languages
English (en)
French (fr)
Inventor
马景旺
贾倩
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2010118612A1 publication Critical patent/WO2010118612A1/zh

Links

Classifications

    • G—PHYSICS
    • G07—CHECKING-DEVICES
    • G07F—COIN-FREED OR LIKE APPARATUS
    • G07F7/00—Mechanisms actuated by objects other than coins to free or to actuate vending, hiring, coin or paper currency dispensing or refunding apparatus
    • G07F7/08—Mechanisms actuated by objects other than coins to free or to actuate vending, hiring, coin or paper currency dispensing or refunding apparatus by coded identity card or credit card or other personal identification means
    • G07F7/0866—Mechanisms actuated by objects other than coins to free or to actuate vending, hiring, coin or paper currency dispensing or refunding apparatus by coded identity card or credit card or other personal identification means by active credit-cards adapted therefor
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
    • G06Q20/34—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using cards, e.g. integrated circuit [IC] cards or magnetic cards
    • G06Q20/352—Contactless payments by cards

Definitions

  • the present invention relates to the field of mobile payment, and in particular, to a smart card, a method for installing a contactless payment application in a smart card, and a corresponding mobile terminal. Background technique
  • Integrated circuit (IC, Integrate Circuit) cards have been widely used in public transportation, access control, and small-scale electronic payment after more than ten years of development.
  • mobile terminals have experienced rapid development for more than two decades, and have been widely popular among residents, bringing great convenience to people's work and life.
  • Mobile terminals are becoming more powerful and have the tendency to integrate more features.
  • Combining mobile terminals with non-contact IC card technology, enabling mobile terminals to be applied in the field of electronic payment, will further expand the use of mobile terminals, bring more convenience to people's lives, and have broad application prospects.
  • the mobile terminal After the mobile terminal adds support for the contactless IC card, the mobile terminal can be simulated as a contactless IC card, and can interact with the contactless card reader of the payment system to implement a contactless payment application.
  • eNFC enhanced NFC
  • NFC Near Field Communication
  • the mainstream technical solution in the industry is eNFC, which is supported by operators and related terminal manufacturers.
  • the eNFC solution is an enhancement and improvement of the NFC solution. It is a short-range wireless communication technology operating at 13.56 MHz, which is derived from the fusion of radio frequency identification (RFID) and interconnection technology.
  • RFID radio frequency identification
  • an NFC analog front-end chip (CLF, Contactless Front-end) and an NFC antenna are added to the terminal, and a mobile user card supporting a single wire protocol (SWP) is used to move the user card. It can be a Subscriber Identity Module (SIM), a User Identity Model (UIM) card, a User Service Identity Module (USIM) card, or other mobile user card.
  • SIM Subscriber Identity Module
  • UIM User Identity Model
  • USIM User Service Identity Module
  • the communication standards supported by the NFC analog front-end chip include ISO 14443 Type A/Type B, Felica, Mifare, IS015693, and so on.
  • the NFC analog front-end chip and the NFC antenna in the mobile terminal implement a contactless communication function, and can communicate with an external contactless card reader in accordance with relevant communication standards.
  • the NFC analog front-end chip can communicate with the terminal main processor chip through a Universal Asynchronous Receiver/Transmitter (UART) interface, and the NFC analog front-end chip function is controlled by the mobile terminal main processor; NFC The analog front-end chip is connected to the C6 pin of the mobile user card through a signal line, and communicates with the mobile user card using the Single Wire Protocol (SWP) at the physical layer, and uses the host control interface (HCI, Host Control) at the logic layer.
  • SWP Single Wire Protocol
  • HCI Host Control
  • the card's reset (Reset), clock (CLK), and input/output (10) pins can correspond to C2, C3, and C7 pins, respectively.
  • the eNFC is characterized by storing an application related to electronic payment on a mobile user card, and storing and executing an electronic payment application by the mobile user card.
  • the NFC analog front end chip in the mobile terminal can establish communication according to the relevant communication standard and the contactless card reader and transmit the instruction sent by the contactless card reader to the mobile user.
  • the card, the mobile user card processes and pays the application-related instructions, and the response information returned by the mobile user card processing instruction can be sent to the contactless card reader through the NFC analog front end chip.
  • the eNFC technology can support the terminal power-down mode by connecting the power supply (VCC) of the mobile subscriber card, that is, the C1 pin to the NFC analog front-end chip.
  • VCC power supply
  • the NFC analog front-end chip and the mobile user card acquire energy from the electromagnetic field generated by the external contactless reader through the NFC antenna.
  • the mobile terminal can also work in the card emulation mode in the absence of power, and interact with an external contactless card reader to complete the electronic payment.
  • the NFC solution Similar to the eNFC solution, the NFC solution also needs to add NFC analog front-end chips and NFC antennas.
  • the supported communication standards include ISO 14443 Type A/Type B, Felica, Mifare, and IS015693.
  • the NFC analog front-end chip can be connected to the main processor of the mobile terminal through the UART interface, and the function of the NFC analog front-end chip is controlled by the mobile terminal main processor.
  • the NFC solution differs from the eNFC solution in that instead of using a mobile user card to save an electronic payment application, the NFC solution uses a security chip integrated on the mobile terminal or a pluggable memory card (such as a MicroSD memory card).
  • the security chip when using a security chip integrated on a mobile terminal to save a payment application, the security chip provides an operating environment for the payment application, and the security chip and the NFC analog front end chip pass the signal input/output communication interface (S2C, signal-in/ Signal-out communication interface ) Communicate.
  • S2C signal-in/ Signal-out communication interface
  • the NFC analog front end chip in the mobile terminal can establish communication according to the relevant communication standard and the contactless card reader and transmit the instruction sent by the contactless card reader to the security chip.
  • the security chip processes and pays the application-related instructions, and the response information returned by the security chip processing instruction can be sent to the contactless card reader through the NFC analog front end chip.
  • the mobile terminal needs to integrate a card slot that can support the memory card, and the card slot provides multiple pins.
  • the mobile terminal supplies power to the memory card through the pin of the card slot; the memory card is connected to the NFC analog front end chip through the pin of the card slot and establishes communication; the memory card is connected to the main processor of the mobile terminal through a part of the pin slot of the card slot,
  • the mobile terminal main processor manages the memory card through the connection.
  • the memory card provides the operating environment for the payment application.
  • the NFC analog front end chip in the mobile terminal can establish communication according to the relevant communication and contactless card reader and transmit the instruction sent by the contactless card reader to the memory card. Fingers related to memory card processing and payment applications Therefore, the response information returned after the memory card processing instruction can be sent to the contactless card reader through the NFC analog front end chip.
  • the above eNFC and NFC schemes are basically similar, using a mobile subscriber card, a memory card or a security chip to store payment applications.
  • mobile subscriber cards, memory cards and security chips are all in the category of smart cards.
  • Smart cards comply with the technical requirements in the Global Platform Card Specification V2.2. Smart cards can support multiple applications.
  • Payment applications from different application providers can be placed in different security domains of smart cards. Logic isolation is achieved, and the storage and operation between applications do not interfere with each other, thus providing a secure application operating environment.
  • the Java card has become the development trend of smart cards.
  • the smart card adopts the Java card specification.
  • the application running in the smart card can achieve platform independence.
  • the payment application developed according to the Java card technical specification can run in the Java card of different smart card manufacturers. Bringing 4 big technical advantages to the promotion of payment applications. Therefore, when the mobile terminal supports contactless payment, the smart card generally complies with the Java Card technical specification, and the payment application is written in the Java language and conforms to the Java Card technical specification.
  • Each application has a unique application identifier (AID, Application ID), which is registered by the application provider, RID (Registered Application Provider Identifier) and Proprietary Application Identifier Extension (PIX).
  • AID Application ID
  • RID Registered Application Provider Identifier
  • PIX Proprietary Application Identifier Extension
  • the payment application in the smart card may be preset in the smart card when the smart card is issued, or may be downloaded from the remote server to the smart card through the mobile terminal after the smart card is issued.
  • the application When the application is installed on a smart card, the information about the application is registered in the registry (Registry) in the smart card.
  • the registered information may include the name of the application, the AID, and the status of the application.
  • the mobile terminal simulates payment for the contactless card
  • the mobile terminal and the contactless reader of the contactless payment system use wireless communication technology for communication, generally adopting radio frequency identification technology, and some countries in foreign countries also adopt other short-distance communication. technology.
  • the communication between the contactless card or the terminal device used as the contactless card and the card reader of the contactless payment system in the existing contactless payment system does not adopt the same communication standard, but the contactless payment system. According to the system's own requirements, the corresponding communication standard is adopted.
  • the contactless card and the card reader communicate according to the radio frequency interface and the communication protocol specified in the adopted communication standard.
  • the communication standard applied in the contactless payment is mainly the radio frequency identification technology. Relevant standards include IS014443 Type A, IS014443 TypeB, Mifare, Felica and IS015693, and some foreign countries have adopted other short-range communication technologies.
  • the public transportation card payment system generally adopts the IS014443 Type A standard and the Mifare standard
  • the contactless bank card payment system generally adopts the ISO 14443 Type B standard.
  • the goal of mobile terminals using eNFC and NFC solutions for contactless payment is to support multiple contactless payment applications, support multiple communication standards, and be able to read cards according to the technical requirements of the corresponding communication standards and different contactless payment systems. Communicate.
  • the NFC analog front end chip in the mobile terminal should be able to support multiple communication standards, and the smart card also needs to be able to support multiple communication standards.
  • the electronic payment application Applet should be based on the javacard.framework. Applet class library, which needs to implement the installation defined in the "Runtime Environment Specification for the Java Card Platform, Version 2.2.2" ( install ), register ( register ), select ( select ), deselect ( deselect ), process ( process ), first use the Java compiler to compile the source code file into a binary class file (.class file), then use the converter And the validator converts the class file, and the converted file is an installation file that can be installed on the smart card, that is, a CAP (Converted Applet) file. After the installation file of the payment application is downloaded to the mobile user card, the installation of the payment application can be performed. Payment application complete installation and personal After the activation, the payment application can be enabled to perform the corresponding payment service.
  • Smart cards support contactless payment applications using IS014443 Type A and IS014443 Type B standards, while contactless payment applications downloaded to smart cards use the Mifare standard; although the application can be installed in a smart card, the smart card does not support Mifare
  • the standard causes the mobile terminal and the contactless card reader in the payment system corresponding to the contactless payment application to communicate according to the Mifare standard, so that the payment application cannot be used normally in the mobile terminal.
  • Another object of the present invention is to provide a method of installing a contactless payment application on a smart card, which can solve the compatibility problem between the payment application and the smart card in terms of communication standards.
  • the present invention is implemented as follows:
  • a method of installing a contactless payment application in a smart card comprising:
  • a smart card acquires a communication standard corresponding to the contactless payment application, and the communication standard is identified by the identification information provided in advance in the contactless payment application; b.
  • the smart card installs the contactless payment application when it is determined that the non-contact payment application is supported according to the communication standard corresponding to the contactless payment application.
  • step b includes:
  • the smart card determines whether the communication standard identified by the pre-provided identification information in the contactless payment application is included in the communication standard supported by itself, and if so, determines the support; if not, it determines that it is not supported.
  • the method also includes: pre-storing the communication standard supported by the smart card in a storage area of the smart card.
  • the identification information provided in advance by the contactless payment application is carried in the version number of the contactless payment application.
  • the communication standard corresponding to the contactless payment application is: a contactless card in the contactless payment system corresponding to the contactless payment application, or a terminal device used as a contactless card and a card reader in a contactless payment system
  • the communication standard corresponding to the communication technology used for communication.
  • the communication standard corresponding to the smart card acquisition contactless payment application is: obtained from the version number of the contactless payment application.
  • the contactless payment application provides the identification information in the version number as: when using the converter to convert the class file of the contactless payment application into an installation file that can be installed on the smart card, adding the contactless payment in the version parameter of the conversion command The identification information of the communication standard corresponding to the application.
  • the format of the version number of the contactless payment application is: AP_ "Identifier of the communication standard” _ “version number”, and the identifier of the communication standard can be represented by a letter.
  • the method further includes: when the contactless payment application is installed, writing the identification information to a registry.
  • a smart card including:
  • An obtaining unit configured to acquire a communication standard corresponding to the contactless payment application, where the communication standard is identified by identifier information pre-provided in the contactless payment application;
  • a storage unit configured to store a communication standard supported by the smart card;
  • a determining unit configured to determine whether a communication standard acquired by the acquiring unit is included in a communication standard stored by the storage unit;
  • an installation unit configured to start installation of the contactless payment application when the determination result of the determining unit is included.
  • the identification information is included in a version number of the contactless payment application.
  • a mobile terminal includes at least a smart card
  • the smart card further includes:
  • An obtaining unit configured to acquire a communication standard corresponding to the contactless payment application, where the communication standard is identified by identifier information pre-provided in the contactless payment application;
  • a storage unit configured to store a communication standard supported by the smart card
  • a determining unit configured to determine whether a communication standard acquired by the acquiring unit is included in a communication standard stored by the storage unit;
  • an installation unit configured to start installation of the contactless payment application when the determination result of the determining unit is included.
  • the installation process is not performed for the unsupported payment application, and the contactless payment application that is not supported by the smart card is installed in the smart card, thereby solving the compatibility problem between the contactless payment application and the smart card in the communication standard.
  • FIG. 1 is a schematic structural diagram of a smart card of the present invention
  • the present invention provides a smart card for installing a contactless payment application and places demands on a contactless payment application.
  • the present invention requires a contactless payment application to provide identification information to identify the pair The communication standard used by the contactless payment system.
  • the identification information can be included in the version number of the contactless payment application.
  • it can be implemented as follows: In the non-contact payment application publishing process, when the converter converts the class file into an installation file (ie, a CAP file) that can be installed on the smart card, the contactless payment is added to the version parameter in the conversion command.
  • the identification information of the communication standard corresponding to the application is used to identify the communication standard adopted by the corresponding contactless payment system by using the identification information in the version number of the contactless application.
  • the smart card of the present invention includes: an obtaining unit, configured to acquire a communication standard corresponding to the contactless payment application according to the identifier information provided by the contactless payment application; a communication standard for storing smart card support; a determining unit, configured to determine whether a communication standard acquired by the acquiring unit is included in a communication standard stored in the storage unit; and an installation unit, configured to: when the determination result of the determining unit is “included” , start the installation of the contactless payment application.
  • the present invention also provides a method of installing a contactless payment application in a smart card, the method being applicable to an eNFC solution and an NFC solution.
  • the smart card may be a mobile user card used in the eNFC solution, and the mobile user card includes a SIM card, a UIM card, a USIM card or other mobile user card, etc.; the smart card may also be integrated in the mobile terminal used in the NFC solution. Security chip, or a removable memory card.
  • the smart card When the non-contact payment application is installed in the smart card, the smart card first obtains the foregoing identification information, so as to know the communication standard adopted by the contactless payment application system corresponding to the identification information; and then, the smart card determines whether the non-contact payment application is supported by the smart card.
  • the communication standard is used to determine whether the contactless payment application is supported; if it is supported, it is installed; if it is not supported, it is not installed.
  • the process of obtaining the identification information by the smart card may be specifically: the smart card acquires the version number of the contactless payment application, and analyzes the identification information in the version number.
  • Whether the smart card determines whether to support the contactless payment application specifically determines whether the communication standard supported by the smart card itself includes the above-mentioned learned communication standard.
  • electronic payment applications are saved by smart cards, which provide a secure, open application operating environment.
  • the smart card can adopt Java card technology and comply with the Global Platform Card Specification V2.2 specification.
  • JCRE Java Card Runtime Environment
  • JVM Java Card Virtual Machine
  • Java Card Framework and API Java Card Framework and API
  • card provider-specified extension interfaces card provider-specified extension interfaces.
  • the program for the contactless electronic payment application should be based on the javacard.framework. Applet class library, which needs to implement the install, register, select, deselect defined in the ''Runtime Environment Specification for the Java CardTM Platform, Version 2.2.2').
  • Each application has a unique application identifier (AID, Application ID), and the AID is registered by the application provider identifier (RID) and the dedicated application identifier.
  • the character extension (PIX) is composed.
  • the encoding rules of the AID can refer to the requirements of ISO/IEC 7816-5 Identification cards - Integrated circuit cards - Part 5: Registration of application providers:2004.
  • Smart cards support multiple applications, and multiple applications can be installed on the card.
  • the payment application can be pre-installed to the smart card, or it can be downloaded from a remote server and installed to the smart card via the mobile communication network after the smart card is issued.
  • the smart card can obtain information such as the AID and the version number of the contactless payment application; when the application is installed on the smart card, the related information of the contactless payment application is registered to the registration of the smart card.
  • the registered information may include the name of the application, the AID, and the status of the application.
  • the converter is a bytecode tool provided by the Java Card Development kit. As a bytecode tool, it requires the help of a Java interpreter to run. It converts the class file into some output file.
  • the input file is: a class file generated by the compiler.
  • the output files are: Cap file, Export file, JCA file, and their suffixes are: *.cap, *.exp, *.jca, the file name is the same as the input file. They will be located in a subdirectory called Javacard under the Java Card project directory.
  • the format of the converter command line is:
  • Interpreter Provides the path and file name of the interpreter, such as c: ⁇ JDK ⁇ bin ⁇ java.exe.
  • the class that is executed is just some of the classes in the com ⁇ sun ⁇ j avacard ⁇ converter ⁇ converter ⁇ directory in converter.jar .
  • converter.bat which contains the command line: ⁇ interpreter> ⁇ - classpath> ⁇ class being executed >
  • Package name the name of the package to be converted
  • the converter in order for the contactless payment application to identify the communication standard adopted by the corresponding contactless payment system, the converter converts the class file of the contactless payment application into an installation file (ie, CAP) that can be installed on the smart card.
  • File in the "version” parameter in the conversion command, the identification information of the communication standard supported by the contactless payment application is added, and the corresponding contactless payment system is identified by the identification information in the version number of the contactless application.
  • the format of the version number can be: AP_ "Identifier of communication standard” _ "Version number”, the identifier of the communication standard can be represented by one letter, A is used to indicate IS014443 Type A standard, and B is used to indicate IS014443 Type B standard.
  • C denotes the Felica standard
  • M denotes the Mifare standard
  • F denotes the ISO18092 standard.
  • version number "AP_B_1.0" indicates that the contactless payment system corresponding to the contactless payment application adopts the communication standard IS014443 Type B, and the version is 1.0.
  • other version number encoding formats are also available as needed.
  • the file can be downloaded from the remote server to the smart card via the mobile communication network.
  • the eNFC solution is taken as an example to describe a method for implementing remote download of a payment application.
  • the mobile terminal in order to realize the remote download of the payment application, the mobile terminal needs to support the data service, and supports the over-the-air download (OTA, On The Air) by means of the data service; to realize the high-speed downloading of the data to the mobile user card, the mobile terminal
  • OTA Over-the-air download
  • BIP Bearer Independent Protocol
  • the BIP protocol is a connection-oriented transport protocol proposed in the 3rd Generation Partnership Project (3GPP) specification.
  • the supported high-speed channels include: GPRS, Enhanced Data Rate GSM Evolution Technology (Enhanced Data Rate for GSM Evolution, EDGE) and UMTS; support five active commands (specifically: OPEN CHANNEL, CLOSE CHANNEL, RECEIVE DATA, SEND DATA ( Send data), GET CHANNEL STATUS, and two events (specifically: Data available) and Channel status (channel status), enabling mobile subscriber cards to leverage the mobile terminal's bearer capabilities to establish and far A connection-oriented data channel between servers.
  • the mobile user card can be used to instruct the mobile terminal to connect to the remote OTA server through the mobile data service channel through the OPEN CHANNEL command, and browse the contactless payment application that can be downloaded on the OTA server through the CAT (Card Application Toolkit).
  • the application download request message is sent to the remote OTA server, and after receiving the application download request, the OTA server selects the security domain on the mobile user card, and the security domain is used to store the downloaded contactless payment application.
  • the OTA server and the security domain in the mobile user card establish a secure channel according to the Secure Channel (Secure Channel) specification in the Global Platform Card Specification V2.2 specification. Secure Channel
  • Secure Channel Secure Channel
  • the download of the contactless payment application begins between the mobile subscriber card and the OTA server.
  • the remote OTA server can send an INSTALL[for install] command to the smart card, instructing the smart card to install the downloaded payment application.
  • the smart card when the smart card installs the downloaded payment application, it first determines whether the downloaded contactless payment application is supported. If it can be supported, the installation process of the contactless payment application is normally performed; if not, the installation of the contactless payment application is not performed.
  • the method for the smart card to determine whether to support the downloaded contactless payment application is to obtain the communication standard adopted by the contactless payment system corresponding to the contactless payment application by using the identification information in the contactless payment application version number, and according to the communication standard supported by the smart card. Determine whether the communication standard corresponding to the contactless payment application is supported.
  • the smart card has identification information of a communication standard supported by the smart card, and the identification information is used to identify a communication standard supported by the smart card, and the identification information may be stored in a storage area of the smart card; when the smart card is issued, The identification information of the supported communication standard is configured by the card issuer.
  • the smart card may add the information of the communication standard adopted by the contactless payment system corresponding to the contactless payment application to the registry of the smart card.
  • the communication standard corresponding to the contactless payment application is recorded.
  • the registry of the smart card can set an identification information in the information for recording the installed contactless payment application, and the identification information is used for recording non-contact. Pay the communication standard corresponding to the application.
  • the identification information of the communication standard may adopt the coding rule of the communication standard identifier in the contactless payment application, using A for IS014443 Type A standard, B for IS014443 Type B standard, C for Felica standard, M for Mifare standard, and F for F Represents the ISO18092 standard.
  • a for IS014443 Type A standard B for IS014443 Type B standard
  • C for Felica standard M for Mifare standard
  • other encoding formats can also be used.
  • Step 201 Download the contactless payment application to the smart card.
  • the smart card can obtain the contactless payment application from the contactless payment application (ie, the CAP file) when the program is converted.
  • the contactless payment application ie, the CAP file
  • Step 202 The remote server sends an application installation command to the smart card.
  • the smart card after receiving the contactless payment application installation command INSTALL[for install] sent by the remote OTA server, the smart card first parses the version number of the contactless payment application, and parses according to the version number encoding rule described above. Obtain the communication standard adopted by the contactless payment system corresponding to the contactless payment application.
  • Step 203 The smart card determines, according to the identification information of the communication standard supported by the smart card, whether the smart card supports the contactless payment application to be installed. If the contactless payment application to be installed is not supported, step 204 is performed; if the smart card supports the contactless payment application to be installed, step 205 is performed.
  • Step 204 The smart card does not perform the installation of the contactless payment application, and reports the installation failure in the INSTALL[for install] response message sent to the remote OTA server.
  • the smart card can further delete the program files of the contactless payment application to be installed. End this process.
  • Step 205 The smart card performs an installation process of the contactless payment application, and the smart card invokes an install method of the non-contact payment application.
  • the install method create an instance of the contactless payment application and the required object, and perform an initialization operation to assign an initial value to the data; finally, the register method of the contactless payment application is called to register the contactless payment application to the registry in the smart card.
  • the information of the contactless payment application is added to the registry of the smart card when the registration is performed, and the information may include the name of the contactless payment application, the application identifier (AID), and the identification information of the communication standard corresponding to the contactless payment application.
  • the contactless payment application After the register method runs successfully, the contactless payment application is successfully installed, and the smart card can report the installation success in the INSTALL[for install] response message sent to the remote OTA server.
  • the contactless payment application can identify the communication standard adopted by the payment application, determine whether the smart card supports the contactless payment application when the smart card installs the contactless payment application, and does not perform the installation process for the unsupported payment application. Avoid installing on smart cards A contactless payment application not supported by a smart card, thereby solving the compatibility problem between the contactless payment application and the smart card in terms of communication standards.

Landscapes

  • Engineering & Computer Science (AREA)
  • Business, Economics & Management (AREA)
  • General Physics & Mathematics (AREA)
  • Physics & Mathematics (AREA)
  • Accounting & Taxation (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Microelectronics & Electronic Packaging (AREA)
  • Strategic Management (AREA)
  • General Business, Economics & Management (AREA)
  • Theoretical Computer Science (AREA)
  • Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Stored Programmes (AREA)

Abstract

本发明提供了一种在智能卡中安装非接触支付应用的方法，包括：（a）智能卡获取非接触支付应用对应的通信标准，该通信标准由非接触支付应用中预先提供的标识信息来标识；（b）智能卡通过判断其是否支持非接触支付应用所对应的通信标准来判断是否支持该非接触支付应用； 如果支持，则安装该非接触支付应用；如果不支持，则不安装。本发明还提供了相应的智能卡及移动终端。采用本发明的方案后，对不支持的支付应用不执行安装过程，避免了在智能卡中安装智能卡所不支持的非接触支付应用，从而解决了非接触支付应用和智能卡在通信标准方面的兼容性问题。

Description

一种安装非接触支付应用的方法、 智能卡及移动终端 技术领域
本发明涉及移动支付领域， 特别涉及一种智能卡、 在智能卡中安装非 接触支付应用的方法， 以及相应的移动终端。 背景技术
集成电路（IC， Integrate Circuit ) 卡、 特别是非接触式 IC卡经过十多 年的发展， 已经被广泛应用于公交、 门禁、 小额电子支付等领域。 与此同 时， 移动终端经历二十多年的迅速发展， 在居民中基本得到普及， 为人们 的工作及生活带来极大的便利。 移动终端的功能越来越强大， 并存在集成 更多功能的趋势。 将移动终端与非接触式 IC卡技术结合， 使移动终端应用 于电子支付领域， 会进一步扩大移动终端的使用范围， 为人们的生活带来 更多便捷， 存在着广阔的应用前景。
移动终端增加对非接触式 IC卡的支持后， 移动终端可以模拟为非接触 IC卡， 可以和支付系统的非接触读卡器进行交互， 实现非接触支付应用。 使用移动终端实现非接触支付的技术方案存在多种， 主要的是增强型 NFC ( eNFC, enhanced Near Field Communication ), 近场通信 ( NFC， Near Field Communication ) 方案。 目前业界的主流的技术方案为 eNFC, 该方案得到 了运营商和有关终端厂商的支持。
eNFC方案是对 NFC方案的增强和改进，是工作于 13.56MHz的一种近 距离无线通信技术， 由射频识别（RFID, Radio Frequency Identification ) ¾ 术及互连技术融合演变而来。 在移动通信终端上实现该方案需要在终端上 增加 NFC模拟前端芯片 （ CLF, Contactless Front-end )和 NFC天线， 并使 用支持单线协议（ SWP， Single Wire Protocol ) 的移动用户卡， 移动用户卡 可以是客户识别模块（ SIM, Subscriber Identity Module )卡、 用户识别模块 ( UIM, User Identity Model )卡、 用户服务识别模块（ USIM, User Service Identity Module )卡或者其它移动用户卡。 NFC模拟前端芯片支持的通信标 准包括 ISO 14443 Type A/Type B、 Felica、 Mifare, IS015693等。 移动终端 中的 NFC模拟前端芯片和 NFC天线实现非接触通信功能，可以和外部的非 接触读卡器按照有关通信标准进行通信。
在 eNFC方案中， NFC模拟前端芯片可以通过通用异步接收 /发送装置 ( UART, Universal Asynchronous Receiver/Transmitter )接口与终端主处理 器芯片通信， 由移动终端主处理器控制 NFC模拟前端芯片的功能； NFC模 拟前端芯片通过一根信号线与移动用户卡的 C6引脚连接，在物理层使用单 线通信协议（SWP, Single Wire Protocol )与移动用户卡通信， 在逻辑层采 用主机控制接口 （HCI, Host Control Interface ) 完成 NFC模拟前端芯片和 移动用户卡之间关于非接触卡模拟及读卡器模拟等应用的通信过程； 移动 用户卡通过 IS07816接口和终端的主处理器芯片连接， 该连接使用到了移 动用户卡的复位（Reset )、 时钟（CLK )、 输入输出 （10 ) 管脚， 可以分别 对应着 C2、 C3、 C7管脚。
eNFC的特点是将和电子支付有关的应用保存在移动用户卡， 由移动用 户卡进行电子支付应用的存储和执行。 移动终端进入支付系统的非接触读 卡器工作范围后， 移动终端中的 NFC模拟前端芯片可以按照有关通信标准 和非接触读卡器建立通信并将非接触读卡器发送的指令传递给移动用户 卡， 由移动用户卡处理和支付应用相关的指令， 移动用户卡处理指令后返 回的响应信息可以通过 NFC模拟前端芯片发送给非接触读卡器。 另外， 通 过将移动用户卡的电源（VCC )、 即 C1管脚与 NFC模拟前端芯片相连， 使 eNFC技术能够支持终端掉电模式。在这种模式下， NFC模拟前端芯片和移 动用户卡通过 NFC天线从外部的非接触读卡器产生的电磁场获取能量， 在 移动终端没电的情况下也同样能够工作在卡模拟模式下， 与外部的非接触 读卡器交互完成电子支付。
NFC方案和 eNFC方案类似， 移动终端上也需要增加 NFC模拟前端芯 片和 NFC天线， 支持的通信标准包括 ISO 14443 Type A/Type B、 Felica、 Mifare、 IS015693等。 NFC模拟前端芯片可以通过 UART接口和移动终端 的主处理器连接， 由移动终端主处理器控制 NFC模拟前端芯片的功能。
但 NFC方案和 eNFC方案不同的是，在 NFC方案中没有使用移动用户 卡保存电子支付应用， 而是使用集成在移动终端上的安全芯片或者可插拔 的存储卡（如 MicroSD存储卡）。
在 NFC方案中，在使用集成在移动终端上的安全芯片保存支付应用时， 安全芯片提供支付应用的运行环境， 安全芯片和 NFC模拟前端芯片通过信 号输入 /输出通信接口 ( S2C, signal-in/ signal-out communication interface ) 进行通信。 移动终端进入支付系统的非接触读卡器工作范围后， 移动终端 中的 NFC模拟前端芯片可以按照有关通信标准和非接触读卡器建立通信并 将非接触读卡器发送的指令传递给安全芯片， 由安全芯片处理和支付应用 相关的指令， 安全芯片处理指令后返回的响应信息可以通过 NFC模拟前端 芯片发送给非接触读卡器。
在 NFC方案中， 如果使用可插拔的存储卡保存支付应用， 移动终端中 需要集成可以支持存储卡的卡槽， 卡槽提供多个管脚。 移动终端通过卡槽 的管脚向存储卡供电； 存储卡通过卡槽的部分管脚和 NFC模拟前端芯片连 接并建立通信； 存储卡通过卡槽的部分管脚和移动终端的主处理器连接， 移动终端主处理器通过该连接对存储卡进行管理。 存储卡提供支付应用的 运行环境。 移动终端进入支付系统的非接触读卡器工作范围后， 移动终端 中的 NFC模拟前端芯片可以按照有关通信和非接触读卡器建立通信并将非 接触读卡器发送的指令传递给存储卡， 由存储卡处理和支付应用相关的指 令， 存储卡处理指令后返回的响应信息可以通过 NFC模拟前端芯片发送给 非接触读卡器。
上述的 eNFC和 NFC方案基本类似， 使用了移动用户卡、 存储卡或者 安全芯片保存支付应用， 概括来讲， 移动用户卡、 存储卡和安全芯片都属 于智能卡的范畴。 移动终端实现非接触支付时， 可以同时支持多个支付应 用。 智能卡遵守全球平台卡规范 V2.2 版本 （ Global Platform Card Specification V2.2 ) 中的技术要求， 智能卡可以支持多应用， 来自不同应用 提供商的支付应用可以放在智能卡不同的安全域， 安全域之间实现逻辑隔 离， 应用之间的存储和运行互不干扰， 从而提供安全的应用运行环境。 另 外， Java卡已经成为智能卡的发展趋势， 智能卡采用 Java卡规范， 运行在 智能卡中的应用可以实现平台无关性， 按照 Java卡技术规范开发的支付应 用能够运行在不同智能卡厂家的 Java卡中， 从而为支付应用的推广带来 4艮 大的技术优势。 因此，移动终端在支持非接触支付时， 智能卡通常遵守 Java 卡技术规范， 支付应用程序采用 Java语言编写并符合 Java卡技术规范。
每个应用拥有一个唯一的应用标识符 （AID, Application ID ), AID由 注册的应用提供者标口、 ( RID, Registered Application Provider Identifier )和 专用应用标只符扩展 ( PIX, Proprietary Application Identifier Extension )码 组成， AID的编码规则符合国际标准组织 7815-5规范:识别卡-集成电路卡- 第五部分： 应用提供者的注册 （ISO/IEC 7816-5 Identification cards ― Integrated circuit cards —Part 5: Registration of application providers :2004 ) ] 要求。
智能卡中的支付应用可以在智能卡发行时预置在智能卡中， 也可以在 智能卡发行后通过移动终端从远程服务器将支付应用下载到智能卡。 应用 在智能卡上进行安装时， 会将应用的有关信息注册到智能卡中的注册表 ( Registry ) 中， 注册的信息可以包括应用的名称、 AID和应用的状态等。 移动终端模拟为非接触卡进行支付时， 移动终端和非接触支付系统的 非接触读卡器之间采用无线通信技术进行通信， 一般采用射频识别技术， 国外有些国家也采用了其他的近距离通信技术。 目前， 现有的非接触支付 系统中非接触卡或者用作非接触卡的终端设备与非接触支付系统的读卡器 之间的通信并没有采用一个相同的通信标准， 而是非接触支付系统根据系 统自己的需求采用相应的通信标准， 非接触卡和读卡器之间按照采用的通 信标准中规定的射频接口和通信协议进行通信， 应用在非接触支付的通信 标准主要为射频识别技术的有关标准， 包括 IS014443 Type A、 IS014443 TypeB , Mifare、 Felica和 IS015693等， 国外的一些国家采用了其他的近距 离通信技术。 例如公共交通卡支付系统一般采用 IS014443 Type A标准和 Mifare标准， 非接触银行卡支付系统一般采用 ISO 14443 Type B标准。 移动 终端采用 eNFC方案和 NFC方案实现非接触支付的目标是能够支持多种非 接触支付应用， 可以支持多种通信标准， 能够按照相应的通信标准的技术 要求和不同的非接触支付系统的读卡器进行通信。 为了使移动终端可以支 持多种通信标准， 移动终端中的 NFC模拟前端芯片应能够支持多种通信标 准， 并且智能卡也需要能够支持多种通信标准。
电子支付应用程序 Applet应基于 javacard.framework. Applet类库, 需 要实现 "Java卡平台运行环境规范 V2.2.2版本" （" Runtime Environment Specification for the Java Card Platform, Version 2.2.2" ) 中定义的安装 ( install )、注册 ( register )、选择 ( select )、去选择 ( deselect )、进程 ( process ), 先使用 Java编译器将源代码文件编译为二进制的类文件（.class文件）， 再 使用转换器和校验器将类文件进行转换， 转换后的文件为可以安装到智能 卡上的安装文件， 即 CAP(Converted Applet)文件。 支付应用的安装文件下 载到移动用户卡后， 可以执行支付应用的安装。 支付应用完成安装及个人 化后， 可以启用该支付应用进行相应的支付业务。
目前， 下载到智能卡的电子支付应用不能标识其对应的非接触支付系 统所采用的通信标准， 而且智能卡有时不能支持所有的通信标准， 可能只 支持一个或者几个通信标准。 在这种情况下， 由于智能卡不能获知非接触 支付应用所对应的通信标准， 智能卡不能判断该非接触支付应用所对应的 非接触支付系统所采用的通信标准是否为自己所支持的通信标准； 进一步， 可能会产生非接触支付应用虽然可以在智能卡上安装， 但因智能卡不支持 该非接触支付应用所对应的通信标准， 从而造成该非接触支付应用在智能 卡上不能正常使用的兼容性问题。 例如： 智能卡支持采用 IS014443 Type A 和 IS014443 Type B标准的非接触支付应用，而下载到智能卡中的非接触支 付应用采用的是 Mifare标准； 该应用虽然可以在智能卡中安装， 但由于智 能卡不支持 Mifare标准， 导致不能使用该移动终端和该非接触支付应用对 应的支付系统中的非接触读卡器按照 Mifare标准进行通信， 使该支付应用 在移动终端中不能正常使用。
因此需要解决支付应用和智能卡在通信标准方面的兼容性问题。 发明内容
有鉴于此， 本发明的一个目的在于提供一种用以安装非接触支付应用 的智能卡以及相应的移动终端， 能够解决支付应用和智能卡在通信标准方 面的兼容性问题。
本发明的另一目的在于提供一种在智能卡安装非接触支付应用的方 法， 能够解决支付应用和智能卡在通信标准方面的兼容性问题。
本发明是这样实现的：
一种在智能卡中安装非接触支付应用的方法， 包括：
a. 智能卡获取非接触支付应用对应的通信标准， 所述通信标准由非接 触支付应用中预先提供的标识信息来标识； b. 智能卡根据非接触支付应用所对应的通信标准， 在判断出支持该非 接触支付应用时， 安装所述非接触支付应用。
步骤 b中所述判断包括：
所述智能卡判断非接触支付应用中预先提供的标识信息所标识的通信 标准是否包含在自身支持的通信标准中， 如果是， 则判断出支持； 如果不 是， 则判断出不支持。
该方法之前还包括： 预先将所述智能卡支持的通信标准存储在智能卡 的存储区中。
所述非接触支付应用预先提供的标识信息携带在所述非接触支付应用 程序的版本号中。
所述非接触支付应用对应的通信标准为： 所述非接触支付应用所对应 的非接触支付系统中的非接触卡， 或者用作非接触卡的终端设备与非接触 支付系统中的读卡器之间， 进行通信所采用的通信技术对应的通信标准。
所述智能卡获取非接触支付应用对应的通信标准为： 从所述非接触支 付应用程序的版本号中获取。
所述非接触支付应用在版本号中提供标识信息为： 在使用转换器将非 接触支付应用的类文件转换为可安装到智能卡上的安装文件时， 在转化命 令的版本参数中加入非接触支付应用所对应的通信标准的标识信息。
所述非接触支付应用程序的版本号的格式为： AP_ "通信标准的标识符 " _ "版本号"， 通信标准的标识符可以采用字母来表示。
该方法进一步包括： 所述非接触支付应用安装时， 将所述标识信息写 入注册表。
一种智能卡， 包括：
获取单元， 用于获取所述非接触支付应用对应的通信标准， 所述通信 标准由非接触支付应用中预先提供的标识信息来标识； 存储单元， 用于存储所述智能卡支持的通信标准；
判断单元， 用于判断所述获取单元获取的通信标准是否包含在所述存 储单元存储的通信标准中； 以及
安装单元， 用于在所述判断单元的判断结果为包含时， 启动非接触支 付应用的安装。
所述标识信息包含在所述非接触支付应用的版本号中。
一种移动终端， 至少包括智能卡；
所述智能卡进一步包括：
获取单元， 用于获取所述非接触支付应用对应的通信标准， 所述通信 标准由非接触支付应用中预先提供的标识信息来标识；
存储单元， 用于存储所述智能卡支持的通信标准；
判断单元， 用于判断所述获取单元获取的通信标准是否包含在所述存 储单元存储的通信标准中； 以及
安装单元， 用于在所述判断单元的判断结果为包含时， 启动非接触支 付应用的安装。
通过本发明方案， 对不支持的支付应用不执行安装过程， 避免了在智 能卡中安装智能卡所不支持的非接触支付应用， 从而解决了非接触支付应 用和智能卡在通信标准方面的兼容性问题。 附图说明
图 1为本发明智能卡的组成结构示意图；
图 2为本发明在智能卡中安装非接触支付应用的处理流程图。 具体实施方式 本发明提供了一种用以安装非接触支付应用的智能卡， 并对非接触支 付应用提出了要求。 本发明需要非接触支付应用提供标识信息来标识其对 应的非接触支付系统所采用的通信标准。 通常， 该标识信息可以包含在非 接触支付应用程序的版本号中。 具体可以这样实现： 在非接触支付应用程 序发布过程中， 使用转换器将类文件转换为可以安装到智能卡上的安装文 件（即 CAP文件） 时， 在转化命令中的版本参数中加入非接触支付应用所 对应的通信标准的标识信息， 通过非接触应用程序的版本号中的标识信息 来标识对应的非接触支付系统所采用的通信标准。
图 1为本发明智能卡的组成结构示意图， 如图 1所示， 本发明的智能 卡包括： 获取单元， 用于根据非接触支付应用提供的标识信息获取该非接 触支付应用对应的通信标准； 存储单元， 用于存储智能卡支持的通信标准； 判断单元， 用于判断获取单元获取的通信标准是否包含在存储单元存储的 通信标准中； 以及安装单元， 用于在判断单元的判断结果为 "包含" 时， 启动非接触支付应用的安装。
本发明还提供了一种在智能卡中安装非接触支付应用的方法， 该方法 适用于 eNFC方案和 NFC方案。
在本发明中，智能卡可以是 eNFC方案中使用的移动用户卡，移动用户 卡包括 SIM卡、 UIM卡、 USIM卡或者其它移动用户卡等； 智能卡也可以 是 NFC方案中使用的集成在移动终端上的安全芯片，或者可插拔的存储卡。
在向智能卡中安装非接触支付应用时， 智能卡首先获取上述标识信息， 从而获知该标识信息对应的非接触支付应用系统所采用的通信标准； 然后， 智能卡通过判断是否支持非接触支付应用所对应的通信标准来判断是否支 持该非接触支付应用； 如果支持， 则安装； 如果不支持， 则不安装。
智能卡获取标识信息的过程具体可采用： 智能卡获取非接触支付应用 的版本号， 分析版本号中的标识信息。
智能卡判断是否支持非接触支付应用具体是判断智能卡本身支持的通 信标准中是否包括上述获知的通信标准。 在 eNFC和 NFC方案中， 由智能卡保存电子支付应用， 智能卡提供安 全、 开放的应用运行环境。
在本发明中，智能卡可以采用 Java卡技术，并遵守 Global Platform Card Specification V2.2规范。 智能卡中存在 Java卡运行环境（ JCRE, Java Card Runtime Environment )。 JCRE包括 Java卡虚拟机（ JVM, Java Card Virtual Machine ), Java卡框架及 API接口 （ Java Card Framework and API )和卡提 供商指定的扩展接口。
非 接触 电 子 支 付应 用 的 程序 （ 即 Applet ) 应 基 于 javacard.framework. Applet 类库 , 需要实现 '' Runtime Environment Specification for the Java CardTM Platform, Version 2.2.2 " 中定义的 install , register, select, deselect, process方法， 以及按照对应的非接触支付应用规 范实现支付业务的处理。 每个应用拥有一个唯一的应用标识符 （AID , Application ID ), AID由注册的应用提供者标识（RID )和专用应用标识符 扩展（PIX )组成， AID的编码规则可以参照 ISO/IEC 7816-5 Identification cards ― Integrated circuit cards ― Part 5:Registration of application providers :2004的要求。
智能卡支持多应用， 可以在卡上安装多个应用。 支付应用可以预先安 装到智能卡， 也可以在智能卡发行后通过移动通信网络从远程服务器上下 载并安装到智能卡。 非接触支付应用的 CAP文件下载到智能卡后， 智能卡 可以获取到非接触支付应用的 AID和版本号等信息； 应用在智能卡上进行 安装时， 会将非接触支付应用的有关信息注册到智能卡的注册表中， 注册 的信息可以包括应用的名称、 AID和应用的状态等。
非接触支付应用程序发布时需要先使用 Java编译器将源代码文件编译 为二进制的类文件 （.class 文件）， 再使用转换器和校验器将类文件进行转 换， 转换后的文件为可以安装到智能卡上的安装文件， 即 CAP(Converted applet)文件。
转换器 (converter)是由 Java卡开发工具包 ( Java Card Development kit ) 提供的字节代码工具。作为字节代码工具， 它需要 Java解释器的帮助才能 运行。 它将 class 文件转换成一些输出文件。 转换时， 输入文件是： 由编 译器生成的 class 文件。输出文件是： Cap 文件， Export文件， JCA文件， 它们的后缀分别是： *.cap,*.exp,*.jca, 文件名与输入文件一致。 它们将位于 Java卡项目目录下的一个叫 Javacard 的子目录中。
转换器命令行的格式为：
<解释器 > <-classpath> <被执行的 class> <可选参数 > <包( 3。1¾86)名> 〈包 AID> <版本 > 。
解释器： 提供解释器的路径和文件名， 如 c:\JDK\bin\java.exe。
被 执 行 的 class ： 就 是 位 于 converter.jar 中 com\sun\j avacard\converter\converter\ 目录下的一些类。
在安装了 Java Card Development kit(Java卡开发工具）后，开发工具会 提供给一个批处理文件： converter.bat, 它包含的就是命令行中： 〈解释器> 〈- classpath> <被执行的 class> 这三部分内容。也就是说，在进行 Applet转 换时， 对这三部分参数的可以不十分了解， 而直接使用 converter.bat进行 文件转换。
命令行 的一些可选参数的介绍：
-classdir: 项目的才艮目录
-exportpath: 一些转换时要用到的 Exp 文件的父目录，
-d: 输出的路径， 它指明的是根目录
-applet [AID][classname]: 指明缺省 Applet 的 AID, 和含 Install() 方 法的 class 文件名
-out [CAP] [EXP] [JCA]: 说明要转换器生成什么文件， 一般默认为生成 CAP和 EXP文件
-nobanner: 信息使用标准输出
包 (package)名： 要被转换的包名
包 AID: 指定 Applet 的 AID
版本： 定义 Applet的版本号
Converter命令行的示例：
c:\JDK\bin\java.exe -classpath c:\jc211\bin\converter.jar com.sun.javacard.converter.Converter -out EXP JCA CAP -exportpath c:\jc211\api21 -applet 0xa0:0x0:0x0:0x0:0x62:0x3:0xl:0xc:0xl:0xl com.sun.javacard.samples.HelloWorld.HelloWorld
com. sun.j avacard. samples .Hello World OxaO :0x0: 0x0： 0x0 :0x62:0x3:0x1 : Oxc： Ox 1 V1.0 。
在本发明中， 为了使非接触支付应用可以标识对应的非接触支付系统 所采用的通信标准， 使用转换器将非接触支付应用程序的类文件转换为可 以安装到智能卡上的安装文件（即 CAP文件） 时， 在转化命令中的的 "版 本" 参数中加入非接触支付应用所支持的通信标准的标识信息， 通过非接 触应用程序的版本号中的标识信息来标识对应的非接触支付系统所对应的 通信标准。 版本号的格式可以为： AP_ "通信标准的标识符" _ "版本号"， 通信标准的标识符可以采用一个字母来表示，采用 A表示 IS014443 Type A 标准， 采用 B表示 IS014443 Type B标准， 采用 C表示 Felica标准， 采用 M表示 Mifare标准，采用 F表示 ISO18092标准。例如版本号为 "AP_B_1.0" 表示非接触支付应用对应的非接触支付系统所采用的通信标准为 IS014443 Type B标准， 版本为 1.0。 当然根据需要也可以其它的版本号编码格式。
非接触支付应用的程序在被转化为可以安装到智能卡上的 CAP 文件 后， 就可以将该文件通过移动通信网络从远程服务器上下载到智能卡。
下面以 eNFC方案为例，描述支付应用的远程下载的实现方法。在 eNFC 方案中， 为了实现支付应用程序的远程下载， 移动终端需要支持数据业务， 并支持采用数据业务的方式实现空中下载（OTA, On The Air ); 为实现数 据可以高速下载到移动用户卡， 移动终端和移动用户卡之间采用承载无关 协议 ( BIP, Bearer Independent Protocol )进行通信。
BIP 协议是在第三代移动通讯伙伴计划 （3rd Generation Partnership Project, 筒称为 3GPP )规范中提出的一种面向连接的传输协议， 可支持的 高速通道包括： GPRS,增强型数据速率 GSM演进技术（ Enhanced Data Rate for GSM Evolution, 筒称为 EDGE )以及 UMTS等； 支持五个主动命令 (具 体为： OPEN CHANNEL (打开信道）、 CLOSE CHANNEL (关闭信道）、 RECEIVE DATA (接收数据 )、 SEND DATA (发送数据 )、 GET CHANNEL STATUS (获取信道状态））及两种事件（具体为： Data available (数据可用） 和 Channel status (信道状态））， 使移动用户卡能利用移动终端的承载能力 建立与远端 ΟΤΑ服务器之间的面向连接的数据通道。
移动用户卡可通过 ΒΙΡ的 OPEN CHANNEL命令指示移动终端通过移 动数据业务通道连接到远程的 OTA服务器，通过卡应用工具包（CAT, Card Application Toolkit )的方式浏览 OTA服务器上可以下载的非接触支付应用。 在移动终端侧确定下载应用后将向远程的 OTA服务器发起应用下载请求消 息， OTA服务器收到应用下载请求后将选择移动用户卡上的安全域， 该安 全域用于存储下载的非接触支付应用。选择移动用户卡上的安全域后， OTA 服务器将和移动用户卡中的安全域按照 Global Platform Card Specification V2.2规范中对安全信道（Secure Channel )的规定建立安全信道。 安全信道 移动用户卡与 OTA服务器之间开始非接触支付应用的下载。
在支付应用下载完成后， 远程的 OTA服务器可以发送 INSTALL[for install]命令给智能卡， 指示智能卡安装下载的支付应用。 在本发明中， 智能卡安装下载的支付应用时， 会首先判断是否支持下 载的非接触支付应用。 如果可以支持， 则正常进行非接触支付应用的安装 过程； 如果不支持， 则不进行非接触支付应用的安装。 智能卡判断是否支 持下载的非接触支付应用的方法为通过非接触支付应用版本号中的标识信 息获得非接触支付应用所对应的非接触支付系统所采用的通信标准， 并根 据智能卡所支持的通信标准判断是否支持该非接触支付应用所对应的通信 标准。 同时， 在本发明中， 智能卡中存在智能卡所支持的通信标准的标识 信息， 该标识信息用于标识智能卡所支持的通信标准， 该标识信息可以保 存在智能卡的存储区内； 在智能卡发行时， 由卡发行商配置所支持的通信 标准的标识信息。
在本发明中， 在非接触支付应用的安装过程中， 执行非接触支付应用 的注册时， 智能卡可以将非接触支付应用对应的非接触支付系统所采用的 通信标准的信息添加到智能卡的注册表中， 通过注册表记录非接触支付应 用所对应的通信标准。 为了实现可以在智能卡的注册表中记录非接触支付 应用所对应的通信标准， 智能卡的注册表可以在记录已安装的非接触支付 应用的信息中设置一个标识信息， 该标识信息用于记录非接触支付应用所 对应的通信标准。 通信标准的标识信息可以采用非接触支付应用中通信标 准标识符的编码规则， 采用 A表示 IS014443 Type A标准， 采用 B表示 IS014443 Type B标准， 采用 C表示 Felica标准， 采用 M表示 Mifare标准， 采用 F表示 ISO18092标准。 当然也可以采用其它的编码格式。
下面结合图 2,描述在非接触支付应用下载到智能卡后， 非接触支付应 用在智能卡中的安装的步骤。
步骤 201 , 下载非接触支付应用程序到智能卡。
在本发明中， 非接触支付应用程序下载到智能卡后， 智能卡可以从非 接触支付应用程序 （即 CAP文件）获得非接触支付应用的程序在被转化时 在转化器命令行中指定的非接触支付应用的标识符 AID和版本号。
步骤 202, 远程服务器向智能卡发送应用安装命令。
在本发明中， 智能卡接收到远程 OTA服务器发送的非接触支付应用安 装命令 INSTALL[for install]后，首先对非接触支付应用程序的版本号进行解 析， 按照上面描述的版本号编码规则进行解析， 获得到非接触支付应用对 应的非接触支付系统所采用的通信标准。
步骤 203 , 智能卡根据自身所支持的通信标准的标识信息， 判断智能卡 是否支持准备安装的非接触支付应用。 如果不支持准备安装的非接触支付 应用， 则执行步骤 204; 如果智能卡支持准备安装的非接触支付应用， 则执 行步骤 205。
步骤 204,智能卡不执行非接触支付应用的安装，并在发送给远程 OTA 服务器的 INSTALL[for install]响应消息中报告安装失败。智能卡并可以进一 步删除准备安装的非接触支付应用的程序文件。 结束本流程。
步骤 205 , 智能卡执行非接触支付应用的安装过程， 智能卡会调用非接 触支付应用程序的 install方法。在 install方法中，创建非接触支付应用的实 例和所需要的对象， 并进行初始化操作， 为数据赋初值； 最后调用非接触 支付应用的 register方法将非接触支付应用注册到智能卡中的注册表中， 在 执行注册时将非接触支付应用的信息添加到智能卡的注册表， 信息可以包 括非接触支付应用的名称、 应用标识符（AID )和非接触支付应用所对应的 通信标准的标识信息。 register方法成功运行后， 非接触支付应用安装成功， 智能卡可以在发送给远程 OTA服务器的 INSTALL[for install]响应消息中报 告安装成功。
通过本发明提供的方法， 非接触支付应用可以标识支付应用所采用的 通信标准， 在智能卡安装非接触支付应用时判断智能卡是否支持该非接触 支付应用， 对不支持的支付应用不执行安装过程。 避免了在智能卡中安装 智能卡所不支持的非接触支付应用， 从而解决了非接触支付应用和智能卡 在通信标准方面的兼容性问题。

Claims

权利要求书
1、 一种在智能卡中安装非接触支付应用的方法， 其特征在于， 包括： a. 智能卡获取非接触支付应用对应的通信标准， 所述通信标准由非接 触支付应用中预先提供的标识信息来标识；
b. 智能卡根据非接触支付应用所对应的通信标准， 在判断出支持该非 接触支付应用时， 安装所述非接触支付应用。
2、 如权利要求 1所述的方法， 其特征在于， 步骤 b中所述判断包括： 所述智能卡判断非接触支付应用中预先提供的标识信息所标识的通信 标准是否包含在自身支持的通信标准中， 如果是， 则判断出支持； 如果不 是， 则判断出不支持。
3、 如权利要求 1或 2所述的方法， 其特征在于， 该方法之前还包括： 预先将所述智能卡支持的通信标准存储在智能卡的存储区中。
4、 如权利要求 3所述的方法， 其特征在于， 所述非接触支付应用预先 提供的标识信息携带在所述非接触支付应用程序的版本号中。
5、 如权利要求 1所述的方法， 其特征在于， 所述非接触支付应用对应 的通信标准为： 所述非接触支付应用所对应的非接触支付系统中的非接触 卡， 或者用作非接触卡的终端设备与非接触支付系统中的读卡器之间， 进 行通信所采用的通信技术对应的通信标准。
6、 如权利要求 4所述的方法， 其特征在于， 所述智能卡获取非接触支 付应用对应的通信标准为： 从所述非接触支付应用程序的版本号中获取。
7、 如权利要求 4所述的方法， 其特征在于， 所述非接触支付应用在版 本号中提供标识信息为： 在使用转换器将非接触支付应用的类文件转换为 可安装到智能卡上的安装文件时， 在转化命令的版本参数中加入非接触支 付应用所对应的通信标准的标识信息。
8、 如权利要求 6所述的方法， 其特征在于， 所述非接触支付应用程序 的版本号的格式为： AP_ "通信标准的标识符" _ "版本号"， 通信标准的标 识符可以采用字母来表示。
9、 如权利要求 1所述的方法， 其特征在于， 该方法进一步包括： 所述 非接触支付应用安装时， 将所述标识信息写入注册表。
10、 一种智能卡， 其特征在于， 包括：
获取单元， 用于获取所述非接触支付应用对应的通信标准， 所述通信 标准由非接触支付应用中预先提供的标识信息来标识；
存储单元， 用于存储所述智能卡支持的通信标准；
判断单元， 用于判断所述获取单元获取的通信标准是否包含在所述存 储单元存储的通信标准中； 以及
安装单元， 用于在所述判断单元的判断结果为包含时， 启动非接触支 付应用的安装。
11、 如权利要求 10所述的智能卡， 其特征在于， 所述标识信息包含在 所述非接触支付应用的版本号中。
12、 一种移动终端， 其特征在于， 至少包括智能卡；
所述智能卡进一步包括：
获取单元， 用于获取所述非接触支付应用对应的通信标准， 所述通信 标准由非接触支付应用中预先提供的标识信息来标识；
存储单元， 用于存储所述智能卡支持的通信标准；
判断单元， 用于判断所述获取单元获取的通信标准是否包含在所述存 储单元存储的通信标准中； 以及
安装单元， 用于在所述判断单元的判断结果为包含时， 启动非接触支 付应用的安装。
PCT/CN2009/075680 2009-04-14 2009-12-17 一种安装非接触支付应用的方法、智能卡及移动终端 WO2010118612A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN200910132868.6 2009-04-14
CN200910132868.6A CN101866514B (zh) 2009-04-14 2009-04-14 一种安装非接触支付应用的方法、智能卡及移动终端

Publications (1)

Publication Number Publication Date
WO2010118612A1 true WO2010118612A1 (zh) 2010-10-21

Family

ID=42958223

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2009/075680 WO2010118612A1 (zh) 2009-04-14 2009-12-17 一种安装非接触支付应用的方法、智能卡及移动终端

Country Status (2)

Country Link
CN (1) CN101866514B (zh)
WO (1) WO2010118612A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102624718A (zh) * 2012-03-02 2012-08-01 东信和平智能卡股份有限公司 适用于双界面Java智能卡通讯协议的控制方法及系统

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102760326A (zh) * 2012-07-10 2012-10-31 武汉天喻信息产业股份有限公司 基于Java虚拟机的多应用刷卡方法及终端
CN103198250B (zh) * 2013-03-11 2016-03-09 青岛海信传媒网络技术有限公司 智能电视应用程序的审核方法
CN104753569B (zh) * 2013-12-29 2018-02-23 中国移动通信集团公司 一种配置非接触参数的方法、nfc芯片及nfc设备
WO2016149925A1 (zh) * 2015-03-26 2016-09-29 华为技术有限公司 多主机环境应用管理方法、装置和设备
CN111079187B (zh) * 2019-12-23 2022-04-01 恒宝股份有限公司 一种智能卡及其文件管理方法

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1859103A (zh) * 2005-07-29 2006-11-08 华为技术有限公司 一种下载系统及下载方法
CN101014985A (zh) * 2004-04-05 2007-08-08 佩兹公司B.V. 使用作为储值装置的普通的移动装置使跨越不同的支付系统的非接触支付交易便利的系统和方法
WO2009042483A1 (en) * 2007-09-26 2009-04-02 Visa U.S.A. Inc. Form factor identification
US20090191916A1 (en) * 2008-01-27 2009-07-30 Sandisk Il Ltd. Generic identity module for telecommunication services

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2006061754A1 (en) * 2004-12-07 2006-06-15 Philips Intellectual Property & Standards Gmbh System and method for application management on multi-application smart cards
PL3211553T3 (pl) * 2007-01-31 2019-07-31 Nokia Technologies Oy Zarządzanie aplikacjami związanymi z bezpiecznymi modułami

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101014985A (zh) * 2004-04-05 2007-08-08 佩兹公司B.V. 使用作为储值装置的普通的移动装置使跨越不同的支付系统的非接触支付交易便利的系统和方法
CN1859103A (zh) * 2005-07-29 2006-11-08 华为技术有限公司 一种下载系统及下载方法
WO2009042483A1 (en) * 2007-09-26 2009-04-02 Visa U.S.A. Inc. Form factor identification
US20090191916A1 (en) * 2008-01-27 2009-07-30 Sandisk Il Ltd. Generic identity module for telecommunication services

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102624718A (zh) * 2012-03-02 2012-08-01 东信和平智能卡股份有限公司 适用于双界面Java智能卡通讯协议的控制方法及系统

Also Published As

Publication number Publication date
CN101866514A (zh) 2010-10-20
CN101866514B (zh) 2014-12-17

Similar Documents

Publication Publication Date Title
EP2421216B1 (en) Enhanced near field communication terminal, smart card and communication method thereof
US8424770B2 (en) Method and device for customizing a portable electronic entity
CN101833817B (zh) 一种非接触电子支付中实现应用选择的方法及终端
US20100084465A1 (en) Contactless management between a smart card and mobile terminal
WO2010118612A1 (zh) 一种安装非接触支付应用的方法、智能卡及移动终端
EP2116077A1 (en) Personal token having enhanced communication abilities for a hosted application
WO2012159521A1 (zh) 一种空中写卡实现方法、系统及装置
WO2010096991A1 (zh) 一种应用下载的系统和方法
Saminger et al. An NFC ticketing system with a new approach of an inverse reader mode
US11907931B2 (en) Method and system for managing virtual electronic card, secure chip, terminal and storage medium
WO2012037791A1 (zh) 射频识别应用信息的显示方法、装置和系统
CN101610475B (zh) 业务菜单处理方法及移动终端
CN110414651A (zh) 调试智能卡的方法及装置
US8844827B2 (en) Chip card, and method for the software-based modification of a chip card
KR20100013363A (ko) 글로벌 플랫폼 기반 아이씨 카드와 그 운영 방법 및 이를위한 기록매체
CN110795154B (zh) 跨平台设备驱动方法、装置、设备及计算机可读存储介质
KR101156664B1 (ko) 무선 정보 제공 방법
KR100971125B1 (ko) 마그네틱 스트라이프 기반 네트워크 카드 운영 방법
Edsbäcker SIM cards for cellular networks: An introduction to SIM card application development
KR20100013365A (ko) 글로벌 플랫폼 기반 애플리케이션 제공자 애플릿에 대한다기능 제공 방법과 이를 위한 무선단말 및 기록매체
KR101030024B1 (ko) 데이터 망을 이용한 음성통화 서비스를 제공하는 방법 및 시스템과 휴대폰 및 이를 위한 기록매체
KR100971128B1 (ko) 마그네틱 스트라이프 기반 네트워크 카드 운영 방법
KR20090114539A (ko) 금융정보 선정 방법 및 시스템, 금융정보 선정 기능 구비무선 단말과 프로그램 기록매체
KR100971126B1 (ko) 카드 운영 시스템
TWI498741B (zh) A signal transmission method, a transaction message display method, and a mobile device

Legal Events

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

Ref document number: 09843246

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 09843246

Country of ref document: EP

Kind code of ref document: A1