JP6807817B2 - Terminal - Google Patents

Description

The present invention relates to a terminal provided with an IC chip for performing short-range wireless communication.

Conventionally, a function using short-range wireless communication has been realized by an NFC (Near Field Communication) chip or the like, which is an IC chip for performing short-range wireless communication provided in a mobile terminal (for example, Patent Document 1). .. Such functions include those related to various services such as electronic money and credit cards.

Japanese Unexamined Patent Publication No. 2008-294966

Normally, when using a function related to an NFC chip, it is necessary that the AID, which is an ID for specifying the function, is stored in the NFC chip. When using the function, a command specifying the AID is transmitted to the mobile terminal by communication by NFC, and the function is realized by the command.

In a mobile terminal, usually, the memory capacity of the NFC chip is not taken into consideration when registering the AID in the NFC chip. For example, in a mobile terminal, AID registration to an NFC chip is performed by a functional module called an NFC framework, but the NFC framework performs AID registration without considering the memory capacity of the NFC chip. Even if a large number of AIDs are registered in the NFC chip and the memory capacity is overflowed, the NFC framework tries to register a new AID, and as a result, the registration fails. The NFC framework cannot detect if registration fails. From the user of the mobile terminal, even if the AID registration to the NFC chip fails due to the overflow of the memory capacity, it seems to be successful. As a result, there is a risk of financial disadvantage such as not being able to actually use the electronic money that was supposed to be available.

The present invention has been made in view of the above, and an object of the present invention is to provide a terminal capable of preventing the memory capacity overflow of an IC chip for performing short-range wireless communication.

In order to achieve the above object, the terminal according to the present invention is an IC chip for performing short-range wireless communication and a terminal having a storage area other than the IC chip, and specifies a function using the IC chip. It is confirmed whether or not the registration request input unit for inputting the registration request of the ID to be registered in the IC chip and the information corresponding to the function related to the registration request input by the registration request input unit are stored in the storage area. It includes a confirmation unit and a registration unit that registers an ID in the IC chip in response to confirmation by the confirmation unit.

In the terminal according to the present invention, the ID is registered in the IC chip after confirming whether or not the information corresponding to the function related to the registration request is stored in the storage area other than the IC chip. For example, when the storage area stores information indicating that the function can be used in the terminal as information according to the function, the ID is registered in the IC chip. Therefore, only the ID of the function that can be used in the terminal can be registered in the IC chip, and the memory capacity of the IC chip can be prevented from overflowing.

According to the present invention, for example, only the ID of the function that can be used in the terminal can be registered in the IC chip, and the memory capacity of the IC chip can be prevented from overflowing.

It is a figure which shows the structure of the mobile terminal which is the terminal which concerns on embodiment of this invention. It is a flowchart which shows the process executed in the mobile terminal which is the terminal which concerns on embodiment of this invention. It is a figure which shows the hardware configuration of the mobile terminal which is the terminal which concerns on embodiment of this invention.

Hereinafter, embodiments of the terminal according to the present invention will be described in detail together with the drawings. In the description of the drawings, the same elements are designated by the same reference numerals, and duplicate description will be omitted.

FIG. 1 shows a mobile terminal 10 which is a terminal according to the present embodiment. The mobile terminal 10 is a device carried and used by a user. Specifically, the mobile terminal 10 corresponds to a mobile phone, a smartphone, or the like. The mobile terminal 10 can perform mobile communication. Further, the mobile terminal 10 can perform short-range wireless communication, specifically, communication by NFC. Communication by NFC is used to realize functions related to various services. The function relates to non-contact services such as electronic money and credit cards. This function is realized by exchanging signals between the mobile terminal 10 and the NFC reader / writer (Reader / Writer) 100 by short-range wireless communication. For example, in the case of a service for making payments by credit card, the payment is performed by exchanging a dedicated command between the mobile terminal 10 and the NFC reader / writer 100, which is a wireless payment terminal connected to the POS cash register. ..

In addition, this embodiment follows the specifications of AOSP (Android Open Source Project), the specifications of NFC Forum, and the Secure Element Access Control specifications of Global Platform.

As shown in FIG. 1, the mobile terminal 10 includes an NFC chip 20, a SIM card 30, an NFC framework 40, a telephony framework 50, and an application 60.

The NFC chip (CLF: Contactless Frontend) 20 is an IC chip for performing short-range wireless communication, and in the present embodiment, communication by NFC. As the NFC chip 20 itself, a conventional NFC chip can be used. The NFC chip 20 includes a storage area 21 and stores an AID (Application Identifier). The AID is an ID that identifies an application (applet 31 described later) used for a function using an NFC chip. That is, the AID is an ID that specifies a function using the NFC chip. The AID is a unique identifier for each function (service) and is preset. For example, in the case of a credit card function, an AID is set for each credit card. The NFC reader / writer 100 identifies the other application by AID. The AID is issued by ISO (International Organization for Standardization), which is an international standardization organization.

The information used for the function using the NFC chip 20 is stored in the secure element (NFCEE: NFC Execution Environment) which is a storage area other than the NFC chip 20 in the mobile terminal 10. A plurality of secure elements may be provided in the mobile terminal 10. The NFC chip 20 is connected to a secure element. When a plurality of secure elements are provided, a secure element and n star topology configurations are adopted for one NFC chip 20. The NFC chip 20 also stores information that identifies a secure element that stores information used for the function indicated by the AID in association with the AID. Based on this information, the NFC chip 20 distributes the AID command specified by the NFC reader / writer 100 to an appropriate secure element.

The NFC chip 20 does not store the AID for the preset default secure element among the secure elements. The default secure element is usually set in the application layer storage. The NFC chip 20 stores only the AID to be routed (transferred) to the non-default secure element as a whitelist.

When the NFC chip 20 receives a command from the NFC reader / writer 100, if the AID included in the command is the AID stored by itself, the NFC chip 20 routes the command to the secure element indicated by the information stored corresponding to the AID. To do. If the AID contained in the command is not the AID stored by itself, the NFC chip 20 routes the command to the default secure element. The NFC chip 20 performs AID distribution by the above mechanism. The function is realized by exchanging information between the secure element to which the command is rooted and the NFC reader / writer 100.

The SIM (SubscriberIdentity Module) card 30 is a subscriber authentication module that stores subscriber information, which is information necessary for the mobile terminal 10 to perform mobile communication. The SIM card 30 stores the information according to the contract between the user of the mobile terminal 10 and the communication carrier (communication carrier) of the mobile communication as the information. The mobile terminal 10 performs mobile communication by using the information stored in the SIM card 30. As the SIM card 30 itself, a conventional SIM card can be used.

The SIM card 30 is also one of the above-mentioned secure elements. The SIM card 30 in the present embodiment is a SIM card corresponding to a function using the NFC chip 20, and is, for example, compatible with the NFC Type A / B method. The SIM card 30 stores the applet 31 and the access rule 32 as information related to the function. The applet 31 is an application (software, program) for realizing a function using the above-mentioned NFC chip 20. The above-mentioned AID is given to the applet 31. The applet 31 stores information (for example, credit card number, balance information) used for the function, which is secure information. As described above, the function is realized by exchanging information between the applet 31 and the NFC reader / writer 100 via the NFC chip 20. The exchange of the information is usually performed by encrypted communication.

The access rule 32 is access control information that defines an access permission rule for the applet 31 of the SIM card 30 from the application 60. The access permission rule is such as which application 60 is permitted to access which applet 31 and what kind of processing request is permitted. The access rule 32 includes the AID of the corresponding applet 31 and the application signature information. The application signature information is information indicating a unique signature of the application 60 corresponding to the applet 31. The access rule 32 conforms to the above-mentioned Secure Element Access Control specification. As the AID and the application signature information itself, the same ones as before can be used.

The applet 31 and the access rule 32 are stored in the SIM card 30 in units of functions. Normally, the applet 31 and the access rule 32 are not pre-installed, and are installed on the mobile terminal 10 by using the application 60 as described later. In the mobile terminal 10, the function in which the applet 31 and the access rule 32 are not stored cannot be used. Only the communication carrier can rewrite the applet 31 and the access rule 32 stored in the SIM card 30.

The NFC framework 40 is a functional unit that controls functions related to the NFC chip 20. The NFC framework 40 is realized by software like the conventional NFC framework, and has the same functions as the conventional NFC framework. Access to the NFC chip 20 is done via the NFC framework 40. Further, as will be described later, the NFC framework 40 includes the functions according to the present embodiment.

The telephony framework 50 is a functional unit that controls functions related to the SIM card 30. The telephony framework 50 is realized by software like the conventional telephony framework, and has the same functions as the conventional telephony framework 50. Access to the SIM card 30 is done via the telephony framework 50. For the access, for example, the OpenMobile API included in the telephony framework 50 is used. Since the applet 31 stored in the SIM card 30 stores important personal information such as the credit card number, the telephony framework 50 is correct for the communication request from the application 60 to the SIM card 30. Only app 60 is allowed, and unauthorized access from unauthorized app 60 is not allowed.

The NFC framework 40 and the telephony framework 50 are provided in the framework layer of the mobile terminal 10.

The application 60 is an application (software, program) that runs on the OS (operating system) of the mobile terminal 10. For example, the application 60 is an Android application that operates on Android (registered trademark). The application 60 is provided in the application layer of the mobile terminal 10. The application 60 in the present embodiment is for making the function using the NFC chip 20 available in the mobile terminal 10, and more specifically, for creating an environment for making the function available. is there. In addition, the application 60 is responsible for the user's UI (user interface) for the function. The application 60 is a function unit, and is provided by, for example, a provider of the function (for example, a credit card operator). The application 60 stores the AID corresponding to the function. The application 60 is installed by the operation of the user's mobile terminal 10 like the conventional application. Alternatively, the application 60 may be pre-installed on the mobile terminal 10.

The provider of the application 60 obtains the permission of the communication carrier of the mobile communication which is the administrator of the SIM card 30, and for example, the applet 31 and the access rule 32 corresponding to the function are previously installed on the server 200 of the communication carrier in advance. Register. The app 60 requests the applet 31 and the access rule 32 from the server 200 via the mobile communication network or the like in response to the user's operation on the app 60 or the like. The server 200 transmits the applet 31 and the access rule 32 to the mobile terminal 10 in response to the request. At this time, the server 200 determines whether or not the user of the mobile terminal 10 is a user having a legitimate authority by using the subscriber information of the mobile terminal 10 or the like, and is determined to be a user having the authority. Only when the applet 31 and the access rule 32 are transmitted.

The mobile terminal 10 receives the applet 31 and the access rule 32 and installs them on the secure element (registers the AID) via the telephony framework. The secure element to be installed is a secure element set in advance for each function (app 60) as follows. If the set secure element is the SIM card 30, the applet 31 and the access rule 32 are installed on the SIM card 30. Normally, the applet 31 and the access rule 32 downloaded from the server 200 of the communication carrier are installed on the SIM card 30. The applet 31 and the access rule 32 may be pre-registered in the server 200 other than the communication carrier, and in that case, the applet 31 and the access rule 32 may be installed in a secure element other than the SIM card 30.

In addition, the application 60 requests the NFC framework 40 to register the AID in the NFC chip 20. Registration of AID from the application 60 to the NFC chip 20 via the NFC framework 40 is an AID declaration according to the AOSP specifications. The AID registration request is, for example, triggered by the operation of the user's mobile terminal 10 (app 60) or the restart of the mobile terminal 10 according to the application 60.

Since the AID registration request can be made without necessarily requiring the installation of the applet 31 and the access rule 32, the AID registration request can be made without the applet 31 and the access rule 32 being installed. That is, the AID registration request can be made even when the function using the NFC chip 20 cannot be used in the mobile terminal 10.

As described above, the secure element and the AID used for each function using the NFC chip 20 are preset and stored in the application 60. In addition, the application 60 stores the application signature information of the application 60. Specifically, the secure element, AID, and application signature information are stored (declared) in an xml file included in the application 60. As the xml file, the same xml file as the conventional one can be used. For example, the secure element used is the default if the xml file is tagged with <host-apdu-service>, and the default if it is tagged with <offhost-apdu-service>. It is said that it is not. If it is a non-default secure element, the secure element used is defined in the xml file. When the SIM card 30 is defined as the secure element to be used in the xml file, the SIM card 30 is used as the secure element in which the applet 31 and the access rule 32 are stored for the function. The AID is defined by the tag <a id-filter> in the xml file. In addition, the application signature information is defined by a preset tag in the xml file.

If the app 60 is correct, the app 60 has the above-mentioned functions and information. However, the application 60 and the xml file can be freely created by the application developer, and there is no guarantee that the contents are correct. For example, there may be a state in which the application 60 exists but the corresponding applet 31 does not exist.

Subsequently, the function according to the embodiment of the present invention will be described. As shown in FIG. 1, the NFC framework 40 of the mobile terminal 10 includes a registration request input unit 41, a confirmation unit 42, and a registration unit 43 as functional units according to the embodiment of the present invention. ..

The registration request input unit 41 is a functional unit for inputting a registration request for the AID to the NFC chip 20. The registration request input unit 41 inputs a registration request from the application 60. When the registration request input unit 41 inputs the registration request, the registration request input unit 41 notifies the confirmation unit 42 to that effect.

The confirmation unit 42 is a functional unit that confirms whether or not the information corresponding to the function related to the registration request input by the registration request input unit 41 is stored in the secure element. The confirmation unit 42 confirms whether or not the information corresponding to the function related to the registration request is stored in the secure element that is accessed (used) when the function is used. Specifically, the confirmation unit 42 confirms as follows.

When the confirmation unit 42 receives the notification from the registration request input unit 41, the confirmation unit 42 acquires the xml file from the application 60. The xml file to be acquired may be acquired only from the application 60 that made the registration request, or may be acquired from all the applications 60 related to the function using the NFC chip 20.

Further, the confirmation unit 42 acquires the AID and the application signature information included in the access rule 32 from the secure element. At this time, the confirmation unit 42 may acquire the AID and the application signature information from the secure element defined by the acquired xml. For example, if the defined secure element is the SIM card 30, the AID and the application signature information are acquired from the SIM card 30.

The confirmation unit 42 determines whether or not the secure element used is the default based on the acquired xml file. Specifically, the confirmation unit 42 makes a determination based on the tag of the xml file. If the xml file is tagged with <offhost-apdu-service>, the confirmation unit 42 determines that the secure element used is not the default, and tags it with <host-apdu-service>. If so, determine that the secure element used is the default.

If the confirmation unit 42 determines that the secure element used is not the default, the confirmation unit 42 subsequently includes the same information as the AID and application signature information included in the acquired xml file in the AID and application signature information acquired from the secure element. Determine if there is something that is.

If it is determined that there is the same information, the confirmation unit 42 outputs to the registration unit 43 information indicating the AID and the secure element to be accessed when using the function specified by the AID.

If it is determined that the secure element used is the default, or if it is determined that there is no one having the same information, the NFC framework 40 ends the process without registering the AID in the NFC chip 20. When the xml file is acquired from all the apps 60 related to the function using the NFC chip 20, the above processing is performed for each xml file.

The registration unit 43 is a registration unit that registers the AID in the NFC chip 20 in response to the confirmation by the confirmation unit 42. The registration unit 43 registers in the NFC chip 20 information indicating a secure element to be accessed when using the function specified by the AID in association with the AID. The registration unit 43 inputs information indicating the AID and the secure element from the confirmation unit 42, associates the information with each other, and registers the information in the NFC chip 20. The registration itself can be performed in the same manner as the conventional method. The above is the function according to the embodiment of the present invention.

Subsequently, the process (operation method performed by the mobile terminal 10) executed by the mobile terminal 10 according to the present embodiment will be described with reference to the flowchart of FIG. In this process, first, the application 60 is installed on the mobile terminal 10 (S01). Subsequently, the application 60 requests the applet 31 and the access rule 32 from the server 200 of the communication carrier, and the applet 31 and the access rule 32 are installed on the SIM card 30 (S02). In addition, the application 60 requests the NFC framework 40 to register the AID in the NFC chip 20.

In the NFC framework 40, the registration request is input by the registration request input unit 41 (S03). Subsequently, the confirmation unit 42 acquires an xml file from the application 60 (S04). In addition, the confirmation unit 42 acquires the AID and the application signature information from the SIM card 30 (S05). Subsequently, the confirmation unit 42 determines whether or not the xml file is provided with the tag <offhost-apdu-service> (S06). When it is determined that the tag is provided (YES in S06), the confirmation unit 42 subsequently includes the AID and the AID included in the acquired xml file in the AID and the application signature information acquired from the SIM card 30. It is determined whether or not there is information that is the same as the application signature information (S07). When it is determined that there is the same information (YES in S07), the information indicating the AID and the SIM card 30 is output from the confirmation unit 42 to the registration unit 43.

Subsequently, the registration unit 43 associates the information indicating the AID and the secure element and registers the information on the NFC chip 20 (S08). When it is determined in S06 that the above tag is not provided (NO in S06), or when it is determined in S07 that there is no same information (NO in S07), the AID is registered in the NFC chip 20. Is not done. The above is the process executed by the mobile terminal 10 according to the present embodiment.

In the present embodiment, the AID is registered in the NFC chip 20 after confirming whether or not the information corresponding to the function related to the registration request is stored in the secure element. Specifically, as in the present embodiment, when the secure element stores AID and application signature information, which are information indicating that the function can be used in the mobile terminal 10, as information according to the function, AID. Is registered in the NFC chip 20. Therefore, only the AID of the function that can be used in the mobile terminal 10 can be registered in the NFC chip 20.

As described above, when only the application 60 is installed and the applet 31 and the access rule 32 are not installed on the SIM card 30, the function cannot be used. In this case, the AID is not registered in the NFC chip 20. This makes it possible to prevent the memory capacity of the NFC chip 20 from overflowing.

AID registration is done on a first-come, first-served basis (in order of discovery of the app). Therefore, if an AID of a function that cannot be used in the mobile terminal 10, that is, an unnecessary (meaningless) AID is registered without performing the control according to the present embodiment, the memory of the NFC chip 20 overflows. The AID of the subsequent function (the secure element is not the default) cannot be registered in the NFC chip 20, and the function cannot be used. It should be noted that the NFC Forum regulation does not relate to the NFC chip capacity, and the implementation is not considered in Android.

Further, the secure element may be the SIM card 30 as in the present embodiment. As described above, the applet 31 and the access rule 32 are installed on the SIM card 30 only when the user is correctly authenticated by the communication carrier. Therefore, only the AID of the function approved for use by the communication carrier can be registered in the NFC chip 20. Since the number of applets 31 and access rules 32 in the SIM card 30 can be controlled by the communication carrier, it is possible to prevent the memory capacity from overflowing. However, the target secure element may be other than the SIM card 30.

Further, as in the present embodiment, the NFC chip 20 may store information indicating a secure element corresponding to the AID. As a result, the function using the NFC chip 20 can be appropriately operated.

In the present embodiment, the short-range wireless communication is NFC, but the present invention can be applied to a short-range wireless communication other than the NFC. Further, although the function according to the present embodiment is provided in the NFC framework 40, it does not necessarily have to be provided in the NFC framework 40. Further, the terminal according to the present invention does not necessarily have to be the mobile terminal 10, and may be any terminal provided with an IC chip for performing short-range wireless communication such as the NFC chip 20.

The block diagram used in the description of the above embodiment shows a block of functional units. These functional blocks (components) are realized by any combination of hardware and / or software. Further, the means for realizing each functional block is not particularly limited. That is, each functional block may be realized by one physically and / or logically coupled device, or directly and / or indirectly by two or more physically and / or logically separated devices. (For example, wired and / or wireless) may be connected and realized by these plurality of devices.

For example, the mobile terminal 10 according to the embodiment of the present invention may function as a computer that processes the mobile terminal 10 of the present embodiment. FIG. 3 is a diagram showing an example of the hardware configuration of the mobile terminal 10 according to the present embodiment. The mobile terminal 10 described above may be physically configured as a computer device including a processor 1001, a memory 1002, a storage 1003, a communication device 1004, an input device 1005, an output device 1006, a bus 1007, and the like. Further, the mobile terminal 10 includes an NFC chip 20 and a SIM card 30 in addition to the hardware. The SIM card 30 may be detachable.

In the following description, the word "device" can be read as a circuit, device, unit, or the like. The hardware configuration of the mobile terminal 10 may be configured to include one or more of the devices shown in the figure, or may be configured not to include some of the devices.

For each function of the mobile terminal 10, the processor 1001 performs calculations by loading predetermined software (programs) on hardware such as the processor 1001 and the memory 1002, and the communication device 1004 communicates with the memory 1002 and the storage 1003. It is realized by controlling the reading and / or writing of the data in.

Processor 1001 operates, for example, an operating system to control the entire computer. The processor 1001 may be composed of a central processing unit (CPU) including an interface with a peripheral device, a control device, an arithmetic unit, a register, and the like. For example, each function of the mobile terminal 10 may be realized by the processor 1001.

Further, the processor 1001 reads a program (program code), a software module, and data from the storage 1003 and / or the communication device 1004 into the memory 1002, and executes various processes according to these. As the program, a program that causes a computer to execute at least a part of the operations described in the above-described embodiment is used. For example, each function of the mobile terminal 10 may be realized by a control program stored in the memory 1002 and operated by the processor 1001, and other functional blocks may be realized in the same manner. Although it has been described that the various processes described above are executed by one processor 1001, they may be executed simultaneously or sequentially by two or more processors 1001. Processor 1001 may be mounted on one or more chips. The program may be transmitted from the network via a telecommunication line.

The memory 1002 is a computer-readable recording medium, and is composed of at least one such as a ROM (Read Only Memory), an EPROM (Erasable Programmable ROM), an EEPROM (Electrically Erasable Programmable ROM), and a RAM (Random Access Memory). May be done. The memory 1002 may be referred to as a register, a cache, a main memory (main storage device), or the like. The memory 1002 can store a program (program code), a software module, or the like that can be executed to carry out the method according to the embodiment of the present invention.

The storage 1003 is a computer-readable recording medium, for example, an optical disk such as a CD-ROM (Compact Disc ROM), a hard disk drive, a flexible disk, a magneto-optical disk (for example, a compact disk, a digital versatile disk, a Blu-ray). It may consist of at least one (registered trademark) disk), smart card, flash memory (eg, card, stick, key drive), floppy (registered trademark) disk, magnetic strip, and the like. The storage 1003 may be referred to as an auxiliary storage device. The storage medium described above may be, for example, a database, server or other suitable medium containing memory 1002 and / or storage 1003.

The communication device 1004 is hardware (transmission / reception device) for performing communication between computers via a wired and / or wireless network, and is also referred to as, for example, a network device, a network controller, a network card, a communication module, or the like. For example, each function of the mobile terminal 10 described above may be realized by the communication device 1004.

The input device 1005 is an input device (for example, a keyboard, a mouse, a microphone, a switch, a button, a sensor, etc.) that receives an input from the outside. The output device 1006 is an output device (for example, a display, a speaker, an LED lamp, etc.) that outputs to the outside. The input device 1005 and the output device 1006 may have an integrated configuration (for example, a touch panel).

Further, each device such as the processor 1001 and the memory 1002 is connected by a bus 1007 for communicating information. The bus 1007 may be composed of a single bus or may be composed of different buses between the devices.

Further, the mobile terminal 10 includes hardware such as a microprocessor, a digital signal processor (DSP: Digital Signal Processor), an ASIC (Application Specific Integrated Circuit), a PLD (Programmable Logic Device), and an FPGA (Field Programmable Gate Array). It may be configured, and the hardware may realize a part or all of each functional block. For example, processor 1001 may be implemented on at least one of these hardware.

Although the present embodiment has been described in detail above, it is clear to those skilled in the art that the present embodiment is not limited to the embodiment described in the present specification. This embodiment can be implemented as a modified or modified mode without departing from the spirit and scope of the present invention determined by the description of the claims. Therefore, the description of the present specification is for the purpose of exemplification and does not have any limiting meaning to the present embodiment.

The order of the processing procedures, sequences, flowcharts, etc. of each aspect / embodiment described in the present specification may be changed as long as there is no contradiction. For example, the methods described herein present elements of various steps in an exemplary order, and are not limited to the particular order presented.

The input / output information and the like may be stored in a specific location (for example, a memory), or may be managed by a management table. Input / output information and the like can be overwritten, updated, or added. The output information and the like may be deleted. The input information or the like may be transmitted to another device.

The determination may be made by a value represented by 1 bit (0 or 1), by a boolean value (Boolean: true or false), or by comparing numerical values (for example, a predetermined value). It may be done by comparison with the value).

Each aspect / embodiment described in the present specification may be used alone, in combination, or may be switched and used according to the execution. Further, the notification of predetermined information (for example, the notification of "being X") is not limited to the explicit notification, but is performed implicitly (for example, the notification of the predetermined information is not performed). May be good.

Software is an instruction, instruction set, code, code segment, program code, program, subprogram, software module, whether called software, firmware, middleware, microcode, hardware description language, or another name. , Applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures, features, etc. should be broadly interpreted to mean.

Further, software, instructions, and the like may be transmitted and received via a transmission medium. For example, the software uses wired technology such as coaxial cable, fiber optic cable, twist pair and digital subscriber line (DSL) and / or wireless technology such as infrared, wireless and microwave to websites, servers, or other When transmitted from a remote source, these wired and / or wireless technologies are included within the definition of transmission medium.

The information, signals, etc. described herein may be represented using any of a variety of different techniques. For example, data, instructions, commands, information, signals, bits, symbols, chips, etc. that may be referred to throughout the above description are voltages, currents, electromagnetic waves, magnetic fields or magnetic particles, light fields or photons, or any of these. It may be represented by a combination of.

In addition, the terms described in the present specification and / or the terms necessary for understanding the present specification may be replaced with terms having the same or similar meanings.

The terms "system" and "network" as used herein are used interchangeably.

Further, the information, parameters, etc. described in the present specification may be represented by an absolute value, a relative value from a predetermined value, or another corresponding information. ..

The names used for the above parameters are not limited in any way. Further, mathematical formulas and the like using these parameters may differ from those expressly disclosed herein.

Mobile terminals (mobile communication terminals) are subscriber stations, mobile units, subscriber units, wireless units, remote units, mobile devices, wireless devices, wireless communication devices, remote devices, mobile subscriber stations, access terminals, depending on the trader. , Mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, or some other suitable term.

As used herein, the terms "determining" and "determining" may include a wide variety of actions. “Judgment” and “decision” are, for example, judgment (judging), calculation (calculating), calculation (computing), processing (processing), derivation (deriving), investigating (investigating), searching (looking up) (for example, table). , Searching in a database or another data structure), ascertaining can be considered as a "judgment" or "decision". Also, "judgment" and "decision" are receiving (for example, receiving information), transmitting (for example, transmitting information), input (input), output (output), and access. (Accessing) (for example, accessing data in memory) may be regarded as "judgment" or "decision". In addition, "judgment" and "decision" mean that "resolving", "selecting", "choosing", "establishing", "comparing", etc. are regarded as "judgment" and "decision". Can include. That is, "judgment" and "decision" may include that some action is regarded as "judgment" and "decision".

As used herein, the phrase "based on" does not mean "based on" unless otherwise stated. In other words, the statement "based on" means both "based only" and "at least based on".

When the terms "first", "second", etc. are used herein, any reference to the elements does not generally limit the quantity or order of those elements. These designations can be used herein as a convenient way to distinguish between two or more elements. Thus, references to the first and second elements do not mean that only two elements can be adopted there, or that the first element must somehow precede the second element.

As long as "include", "including", and variations thereof are used within the scope of the present specification or claims, these terms are similar to the term "comprising". Is intended to be inclusive. Furthermore, the term "or" as used herein or in the claims is intended not to be an exclusive OR.

In the present specification, a plurality of devices shall be included unless the device has only one device apparently in the context or technically. In the whole of the present disclosure, if the context clearly does not indicate the singular, it shall include more than one.

10 ... mobile terminal, 20 ... NFC chip, 21 ... storage area, 30 ... SIM card, 31 ... applet, 32 ... access rule, 40 ... NFC framework, 41 ... registration request input unit, 42 ... confirmation unit, 43 ... registration Department, 50 ... Telephony framework, 60 ... App, 1001 ... Processor, 1002 ... Memory, 1003 ... Storage, 1004 ... Communication device, 1005 ... Input device, 1006 ... Output device, 1007 ... Bus.

Claims (3)

A terminal having an IC chip for short-range wireless communication and a storage area other than the IC chip.
A registration request input unit for inputting a registration request for an ID that specifies a function using the IC chip to the IC chip, and a registration request input unit.
A confirmation unit for confirming whether or not the information corresponding to the function related to the registration request input by the registration request input unit is stored in the storage area.
A registration unit that registers the ID in the IC chip in response to confirmation by the confirmation unit, and a registration unit.
A terminal equipped with. The terminal according to claim 1, wherein the storage area is a subscriber authentication module that stores information necessary for the terminal to perform mobile communication. The confirmation unit confirms whether or not the information corresponding to the function related to the registration request is stored in the storage area accessed when the function is used.
The terminal according to claim 1 or 2, wherein the registration unit registers information indicating a storage area to be accessed when using the function specified by the ID in the IC chip in association with the ID.

Images