JP2015029352A - Information processor and method, and program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To register a service and a name of the service such that the service name can be viewed in a viewer.SOLUTION: When a service is registered, data of the registered service is transmitted from a reader/writer 202 according to a communication system unique to a third application 256. The data is supplied to the third application 256 through a communication path 351. Information about a service name corresponding to the registered service is supplied to an application manager 252 through a communication path 352. The application manager 252 registers the service name on a registry 253 based on the supplied data. The present invention can be applied to a reader/writer communicating with an IC card in a non-contact manner.

Description

  The present invention relates to an information processing apparatus, method, and program, and more particularly to an information processing apparatus, method, and program suitable for use when updating data managed by a chip or a card that supports a plurality of communication protocols. About.

  Mobile phones have become widespread, and various services are provided by mobile phones. Referring to FIG. 1A, a chip 12 is incorporated in the mobile phone 11, and a service 13-1 and a service 13-2 are written on the chip 12. Further, the application 14-1 performs processing when providing the service 13-1 to the user, and the application 14-2 performs processing when providing the service 13-2 to the user.

  An application is a series of executable modules written in software on a mobile phone and is different from a service written on a chip. If the mobile phone is a product that conforms to the MIDP 2.0 specification shown in Non-Patent Document 1, application management software (AMS) is a product that conforms to the MIDP 1.0 specification shown in Non-Patent Document 2. If so, JAM (Java (registered trademark) Application Manager) having the same function is installed, and the application installed in the mobile phone is managed. The management here refers to holding a series of state transitions such as downloading, installing, and deleting an application.

  The application management software 15 first manages that the application 14-1 is installed in the mobile phone, and further manages that information when the application generates the service 13-1 in the chip. Similarly, when the service 13-2 is generated in the chip after the application 14-2 is installed, the information is associated. For example, when deleting the application 14-2, the application management software 15 needs to delete the associated service 13-2 in advance.

  Here, as shown in FIG. 1B, consider the case where the user changes from the mobile phone 11 to the mobile phone 31. For example, when the mobile phone 31 is purchased, a data transfer service from the mobile phone 11 to the mobile phone 31 is performed at the purchase store. Service 13-1 and service 13-2 stored in the chip 12 of the cellular phone 11 (hereinafter, when there is no need to distinguish between the services 13-1 and 13-2, they are simply described as service 13. The same description is transferred to the chip 32 of the mobile phone 31. Further, the information of the application management software 15 is also transferred to the application management software 33. However, the application 14 on the mobile phone that is not managed by the chip 12 is not transferred to the mobile phone 31.

  The application management software 33 of the mobile phone 31 has a service 13 stored in the chip 32. If there is no application 14 corresponding to the service 13, a message instructing the user to download the application 14 corresponding to the service 13 is displayed. It is displayed on the display of the mobile phone 31. When the user downloads the application 14 as processing for the message, the new mobile phone 31 can use the service 13.

Mobile Information Device Profile FOR Java TM 2 Micro Edition (JSR118) Mobile Information Device Profile (JSR-37) JCP Specification Java 2 Platform, Micro Edition, 1.0a

  As described above, the service 13 is currently managed by the chip 12, and the application management software 15 (33) is associated with the application 14, but the service 13 is stored in a UICC (Universal Integrated Circuit Card). It is possible to manage it. As shown in FIG. 2A, when the service 13 is stored in the UICC 51 of the mobile phone 11, the UICC 51 is removed from the mobile phone 11, and the UICC 51 is attached to another mobile phone 31. It is preferable that the service 13 is made available at 31.

  In this case, the service 13 and the like stored in the UICC 51 are transferred to the inserted mobile phone 31, but the information of the application management software 15 is not transferred to the application management software 33. As a result, the processing performed by the application management software 15 cannot be performed by the application management software 33, and as a result, the service 13 stored in the UICC 51 may not be used.

  In view of this, as shown in FIG. 2B, it is conceivable to provide a viewer 71 on the mobile phone 11. The viewer 71 is provided in each mobile phone and configured to allow browsing of services managed by the UICC 51. For example, when the UICC 51 attached to the mobile phone 11 is removed and attached to the mobile phone 31, the mobile phone 31 also includes the viewer 71, so that the service managed by the UICC 51 is provided by the viewer 71. You can browse.

  Further, for example, if the service 13 is managed but there is no application associated with the service 13, the viewer 71 may have a function of displaying a message prompting the user to download the application. .

  The UICC 51 is configured as shown in FIG. 3, for example. An application manager 102 in the UICC is provided on the UICC hardware 101, and an application 103, an application 104, and an application 105 are managed thereon. The application 103 is an application for providing a service that realizes a credit card function, for example. The application 104 is an application for providing a transport service used when, for example, paying a fee when getting on and off a transportation facility.

  For example, when the JavaCardTM disclosed by Sun Microsystems (trademark) is used as the execution environment, the application manager 102 in the UICC manages the application installation / deletion function, and management information based on the registry stipulated by the Global Platform Using an authentication method, an integrated application management function is realized.

  The application 105 is an application for providing a comprehensive service, and provides a service 106-1, a service 106-2, and a service 106-3. For example, the service 106-1 is a service that realizes a credit function, the service 106-2 is a service that provides a transport-type service, and the service 106-3 is a service that provides a coupon.

  When such an application is registered and the viewer 71 browses the application managed by the UICC 51, for example, the display shown in FIG. 4 is performed. Since the viewer 71 recognizes the application 103, the application 104, and the application 105, a name “service 103” that is a service name of a service provided by the application 103 and a name “service 104” that is a service name of a service provided by the application 104 are displayed. To the user. There are a plurality of services provided by the application 105, but the name “service 105”, which is a generic name of the application 105, is provided to the user.

  As described above, the application 105 provides the services 106-1 to 106-3, but the viewer 71 can recognize only the applications 103 to 105 registered on the application manager 102 in the UICC. The services 106-1 to 106-3 are also recognized and the information cannot be presented to the user.

  The present invention has been made in view of such a situation. For example, information in a device that manages predetermined information such as UICC can be accurately browsed by a viewer for browsing the information. At the same time, it will be possible to update using existing infrastructure.

  An information processing apparatus according to an aspect of the present invention is a card that manages a predetermined application and a service provided by the application, a communication unit that performs contactless communication with a card including an application manager, and the card, A first communication method for communication with the card for registering the service; and a setting means for setting a second communication method for communication with the card for registering information on the service to be registered. , First transmission means for creating and transmitting data for registering the service in the card by the first communication method set by the setting means; and the second transmission means set by the setting means Second transmission means for creating and transmitting data for registering the service information in the card by a communication method.

  The setting unit may set the first communication method to a communication method for accessing the application, and set the second communication method to a communication method for accessing the application manager.

  When the first communication method is set to a communication method for accessing the application manager by the setting unit, the first transmission unit includes a packet used in the set first communication method, Data associated with an application-specific command can be generated and transmitted.

  When the first communication method is set to a communication method for accessing the application manager by the setting means, the first transmission means is a packet used in the set first communication method, and It is possible to generate and send data that wraps an application-specific command.

  The communication means can communicate with a plurality of communication methods, and the selection means determines for each communication method whether or not communication with the card can be performed, and the communication method determined to be able to perform communication. You can choose from among them.

  The communication means can communicate with a plurality of communication methods, and the selection means selects one communication method from the plurality of communication methods, and the communication method cannot communicate with the card. If another communication method is selected, it is determined again whether or not communication with the card can be performed. When communication is possible with the selected communication method, the communication becomes possible. The selected communication method can be selected.

  The communication means can communicate with a plurality of communication methods, and the selection means selects one communication method from the plurality of communication methods, and the communication method cannot communicate with the card. When another communication method is selected, it is determined again whether or not communication with the card can be performed. When communication with the selected communication method becomes possible, the communication method Can exchange information regarding the communication method and select the communication method using the information exchange result.

  An information processing method according to an aspect of the present invention is an information processing method of an information processing apparatus including a predetermined application and a communication unit that performs contactless communication with a card that manages a service provided by the application. A first communication method for communication with the card for registering the service, and a second communication method for communication with the card for registering information on the service to be registered The data for registering the service in the card using the first communication method is created, transmitted by controlling the communication means, and the service information is transmitted in the set second communication method. Creating data to be registered in the card, and controlling and transmitting the communication means.

  A program according to an aspect of the present invention registers a service in an information processing apparatus including a predetermined application and a communication unit that performs contactless communication with a card that manages the service provided by the application. In order to register the first communication method of communication with the card and the information of the service to be registered, the second communication method of communication with the card is set, and the set first Creating data for registering the service in the card in a communication method, controlling and transmitting the communication means, and registering the service information in the card in the set second communication method Creating data and controlling and transmitting the communication means.

  In the information processing apparatus, method, and program according to one aspect of the present invention, communication is performed in a contactless manner with a predetermined application and a card that manages a service provided by the application. A first communication method used when a service is registered and a second communication method used when a service name is registered are set in the card. Then, the service and the service name are registered in the card by the set communication method.

  According to one aspect of the present invention, information in an apparatus that manages information can be browsed by a viewer that is commonly used by different devices. The browsing can accurately reflect the contents of individual information.

  According to one aspect of the present invention, information in a device that manages information can be updated using existing infrastructure.

It is a figure for demonstrating the transfer of the service in the conventional mobile telephone. It is a figure for demonstrating the transfer of a service when UICC is used. It is a figure for demonstrating registration of the service in UICC. It is a figure which shows an example of the screen displayed by the process of a viewer. It is a figure which shows the structure of one Embodiment of the system to which this invention is applied. It is a figure which shows the internal structure of an IC card. It is a figure for demonstrating a communication channel. It is a figure for demonstrating a communication channel. It is a figure for demonstrating a communication channel. It is a figure for demonstrating the relationship between a communication system, a packet, and a command. It is a figure for demonstrating the hierarchy in each communication system. It is a figure which shows the example of a display of a service name. It is a figure for demonstrating a service. It is a figure for demonstrating registration of a service and a service name. It is a figure for demonstrating the function of a reader / writer. It is a flowchart for demonstrating the determination process of a communication system. It is a flowchart for demonstrating the determination process of a communication system. It is a flowchart for demonstrating the determination process of a communication system. It is a flowchart for demonstrating the determination process of a communication system. It is a flowchart for demonstrating the determination process of a communication system. It is a flowchart for demonstrating the determination process of a communication system. It is a flowchart for demonstrating the determination process of a communication system. It is a flowchart for demonstrating the determination process of a communication system. It is a flowchart for demonstrating the determination process of a communication system. It is a figure for demonstrating the relationship between a communication system, a packet, and a command. It is a flowchart for demonstrating registration of a service and a service name. It is a flowchart for demonstrating registration of a service and a service name. It is a flowchart for demonstrating registration of a service and a service name. It is a flowchart for demonstrating registration of a service and a service name. It is a figure for demonstrating an application manager. It is a flowchart for demonstrating registration of a service and a service name. It is a flowchart for demonstrating registration of a service and a service name. It is a figure which shows the example of a display of a service name. It is a figure which shows the example of a display of a service name. It is a figure for demonstrating a recording medium.

  Embodiments of the present invention will be described below with reference to the drawings.

[About the system]
FIG. 5 is a diagram showing a configuration of an embodiment of a system to which the present invention is applied. The system shown in FIG. 5 includes a mobile phone 201 and a reader / writer 202. The mobile phone 201 and the reader / writer 202 communicate with each other without contact. Although the description is continued here as the mobile phone 201, the present invention can be applied to an IC card that communicates with the reader / writer 202 and holds some data.

[Configuration of mobile phone 201]
FIG. 6 is a diagram showing an internal configuration of the mobile phone 201. The cellular phone 201 includes a host 221 and a UICC (Universal Integrated Circuit Card) 222, and the host 221 and the UICC 222 are connected so that data can be exchanged by a UART (Universal Asynchronous Receiver Transmitter) 223. The mobile phone 201 also includes a CLF (Contactless Frontend) 224 that controls non-contact communication between the mobile phone 201 and the reader / writer 202.

  In addition, although the part concerning this invention is illustrated and demonstrated here, the mobile telephone 201 is a structure also including the part which implement | achieves the function which functions as a telephone by the communication part etc. which are not illustrated, the function connected to a network, etc. It is said that.

  The UICC 222 includes UICC hardware 251, an application manager 252, and a registry 253. Here, it is assumed that the UICC 222 stores and manages the first application 254, the second application 255, and the third application 256. The first application 254 is an application for providing, for example, a service for realizing a credit card function on the mobile phone 201. In addition, for example, the second application 255 is an application for providing the mobile phone 201 with a transport-related service used when paying a fee for getting on and off a transportation facility.

  For example, the third application 256 is an application for providing a comprehensive service. As will be described later, the third application 256 is an application for providing a plurality of services such as a service for realizing a credit function, a transport service, and a service for providing a coupon. Although not shown in FIG. 6, as will be described later with reference to FIG. 14, a service may be additionally registered in the UICC 222, and the UICC 222 also has a function of storing and managing the registered service. . Each application is managed by the application manager 252, but is not limited to being managed in the same execution environment. As an example, even if the application manager 252 is equipped with JavaCardTM and one application is realized by software, another application may be written at the time of shipment from the ROM or provided as a separate chip. obtain.

  The UICC hardware 251 is a hardware part that constitutes the UICC 222, and includes, for example, an interface that exchanges data with the CLF 224. The application manager 252 includes a registry 253. The application manager 252 refers to information written in the registry 253 and updates information in the registry 253 based on an instruction from the application.

  In addition, the application manager 252 interprets a command supplied via the CLF 224, and executes processing for supplying data to the application and supplying data from the application to the CLF 224 based on the interpretation. The registry 253 manages service-related information such as the name and service type of the service provided by the application.

  Here, the flow of data when an application or service is registered or updated will be described.

[About data flow during registration and update]
FIG. 7 is a diagram for explaining the flow of data when accessing the first application 254. When accessing the first application 254, there is a communication path 301 for accessing the first application 254 of the UICC 222 from the reader / writer 202 via the CLF 224 via the UICC hardware 251. Similarly, there is a communication path 302 for accessing the first application 254 from the reader / writer 202 via the CLF 224 and further via the UICC hardware 251 of the UICC 222 and the application manager 252.

  The difference between the communication path 301 and the communication path 302 is due to different command formats. What is transmitted to the first application 254 via the communication path 301 is a unique command format corresponding to the communication protocol of the first application 254. Communication is performed between the reader / writer 202 and the CLF 224 using a protocol corresponding to the first application 254, and a unique command acquired by communication is passed from the CLF 224 to the UICC hardware 251. Also, a general-purpose command format corresponding to the communication protocol is transmitted to the first application 254 through the communication path 302. Communication is performed between the reader / writer 202 and the CLF 224 using a protocol corresponding to the first application 254, and a command based on a general-purpose command format acquired by communication is passed from the CLF 224 to the UICC hardware 251. That is, depending on the command format that flows, there are a communication path 301 that goes to the first application without going through the application manager 252 and a communication path 302 that goes to the first application via the communication path.

  As will be described later, as communication protocols, there are Type A standards, Type B standards corresponding to 3 and 4 standardized by ISO 14443, and commonly known Type F standards standardized by 18092. As a general-purpose command format using the communication protocol, there is a command format called Application Protocol Data Unit (APDU) defined by ISO7816-4. A command conforming to the APDU command format is hereinafter referred to as an APDU command.

  Returning to FIG. 7, there is a communication path 303 as a communication path for accessing the first application 254. The communication path 303 is a communication path for accessing the first application 254 from the host 221 via the wired UART 223 and further via the UICC hardware 251 and the application manager 252 in the UICC 222.

  As described above, there are three communication paths for accessing the first application 254. Further, the first application 254 can access the registry 253 in the application manager 252, and this communication path is a communication path 304.

  Next, a data flow when accessing the second application 255 will be described with reference to FIG. When accessing the second application 255, there is a communication path 321 for accessing the second application 255 from the reader / writer 202 via the CLF 224 and further via the UICC hardware 251 of the UICC 222 and the application manager 252. A command format corresponding to a general-purpose communication protocol is transmitted to the second application 255 via the communication path 321.

  In addition, as with the first application 254, there is also a wired communication path 322. The communication path 322 is a communication path for accessing the second application 255 from the host 221 via the wired UART 223 and further via the UICC hardware 251 and the application manager 252 in the UICC 222.

  As described above, there are two communication paths for accessing the second application 255. The second application 255 is configured to be able to access the registry 253 in the application manager 252. This communication path is referred to as a communication path 323.

  Next, a data flow when accessing the third application 256 will be described with reference to FIG. When accessing the third application 256, there is a communication path 351 for accessing the third application 256 of the UICC 222 from the reader / writer 202 via the CLF 224 and the UICC hardware 251. Similarly, there is a communication path 352 for accessing the third application 256 from the reader / writer 202 via the CLF 224 and further via the UICC hardware 251 of the UICC 222 and the application manager 252.

  Similar to the first application 254, the difference between the communication path 351 and the communication path 352 in the third application 256 is also due to different command formats. Communication is performed between the reader / writer 202 and the CLF 224 using a protocol corresponding to the third application 256, and a command unique to the third application 256 acquired by communication is passed from the CLF 224 to the UICC hardware 251.

  What is transmitted to the third application 256 via the communication path 351 is a unique command format corresponding to the communication protocol of the third application 256. Also, a command format corresponding to a general-purpose protocol is transmitted to the third application 256 via the communication path 352. Communication is performed between the reader / writer 202 and the CLF 224 using a protocol corresponding to the third application 256, and a command conforming to a general-purpose command format acquired by communication is passed from the CLF 224 to the UICC hardware 251.

  That is, depending on the command format that flows, there is a communication path 351 that goes to the third application 256 without going through the application manager 252 and a communication path 352 that goes to the third application 256 via the application manager 252.

  As a communication path for accessing the third application 256, there is also a communication path 353. The communication path 353 is a communication path for accessing the third application 256 from the host 221 via the wired UART 223 and further via the UICC hardware 251 and the application manager 252 in the UICC 222.

  As described above, there are three communication paths for accessing the third application 256. Further, the third application 256 can access the registry 253 in the application manager 252, and this communication path is a communication path 354.

  With reference to FIG. 10, these communication paths, communication protocols, and command formats will be described. In FIG. 10, a specific example will be described. The first application 254 corresponds to a communication method called Type A or the like. Hereinafter, the communication method supported by the first application 254 will be described as a first communication method, and the description will be continued assuming that Type A is a specific example of the first communication method.

  The first communication method conforms to ISO 14443-2-3 among communication methods referred to as Type A as a communication protocol, and also conforms to 14443-4 using a unique packet as a transmission packet, There are two types corresponding to general-purpose packets.

  The unique packet is used for the purpose of transmitting / receiving a command unique to the first application 254. Therefore, when this unique packet is transmitted from the reader / writer 202, the command extracted by the CLF 224 is supplied to the first application 254 via the UICC hardware 251. In other words, since it is a packet of a unique standard, it is not processed by the application manager 252 but is supplied to the first application 254.

  Depending on how the first application 254 is implemented, the application manager 252 may or may not be used. For example, when the first application 254 is realized in the UICC hardware 251, the first application 254 can be operated in hardware without going through the application manager 252 away from the management of the application manager 252. As another example, when the first application 254 is later deployed in memory as a module, the first application 254 is placed under the management of the application manager 252, and in this case, the application manager 252 is used. When the application manager is used, the general command is used as described above.

  Here, in the example shown in FIG. 7, that is, as described above, when a unique packet is transmitted from the reader / writer 202, the command extracted by the CLF 224 is passed to the first application 254 via the UICC hardware 251. The description will be continued assuming that the communication path 301 is supplied.

  In the following description, the unique command is described as a first command to indicate that it is a command transmitted / received in a unique packet (described as the first packet) of the first application 254. One example of a first application that uses a unique command is MIFARE (trademark).

  The application manager 252 handles an APDU command extracted after being processed by the CLF 224. Therefore, when this APDU command is transmitted from the reader / writer 202, it is supplied to the first application 254 via the communication path 302 (FIG. 7), that is, the CLF 224, the UICC hardware 251, and the application manager 252. In this case, the application manager 252 executes processing that the supplied command is a command to the first application 254, whereby the command is supplied to the first application 254.

  This general-purpose packet is used for the purpose of transmitting and receiving a general-purpose command format, here, an APDU command.

  The second application 255 corresponds to a communication method called Type B or the like. Hereinafter, the communication method supported by the second application 255 will be described as a second communication method as appropriate, and the description will be continued assuming that Type B is a specific example of the second communication method. This second communication method conforms to ISO 14443-2-4 as a corresponding protocol.

  The second communication method (Type B) includes general-purpose packets as transmittable packets. As described above, the general-purpose packet is used for the purpose of transmitting / receiving a general-purpose command format, and is used for the purpose of transmitting / receiving an APDU command.

  When this general-purpose packet is transmitted from the reader / writer 202, the CLF 224 processes the packet, extracts the APDU command from the packet, and supplies it to the second application 255 via the UICC hardware 251 and the application manager 252. . In this case, after that, the application manager 252 processes the APDU command extracted from the supplied packet, and executes a process indicating that the command is to the second application 255, whereby the command is supplied to the second application 255. Will be.

  In the case of the second application 255, as in the case of the first application 254, there may be a case where the application manager 252 is not used or not, depending on how the second application 255 is realized. Here, as illustrated in FIG. 8, the description will be continued with an example through the application manager 252.

  The third application 256 corresponds to a communication method called Type F or the like. Hereinafter, the communication method supported by the third application 256 will be described as a third communication method, and the description will be continued assuming that Type F is a specific example of the third communication method. This third communication method conforms to ISO 18092 as a communication protocol.

  The third communication method (Type F) includes a FeliCa (trademark) packet as a transmittable packet and a general-purpose packet further placed on the FeliCa packet. The FeliCa packet is a unique packet of the third application 256. Therefore, when this FeliCa packet is transmitted from the reader / writer 202, the FeliCa command extracted by the CLF 224 is supplied from the CLF 224 to the third application 256. This FeliCa packet is used for the purpose of sending and receiving FeliCa commands.

  In the case of the third application 256, as in the case of the first application 254, there may be a case where the third application 256 is not routed through the application manager 252 depending on a method of realizing the third application 256. Here, as illustrated in FIG. 9, the description will be continued by taking an example via the application manager 252 (an example of communication on the communication path 351).

  In the following description, the FeliCa command is described as a third command to indicate that it is a command transmitted / received in a unique packet (hereinafter referred to as a third packet) of the third application 256.

  This Type F also supports transmission / reception of general commands by placing a general packet on the FeliCa packet as a transmittable packet. As described above, the general-purpose packet is used for the purpose of transmitting / receiving a general-purpose command, and is used for the purpose of transmitting / receiving an APDU command.

  When this general-purpose packet is transmitted from the reader / writer 202, the CLF 224 processes the packet, and the extracted APDU command is supplied to the third application 256 via the UICC hardware 251 and the application manager 252. . That is, the APDU command and its response data are exchanged over the communication path 352 (FIG. 9). In this case, the application manager 252 executes processing that the supplied APDU command is a command to the third application 256, whereby the APDU command is supplied to the third application 256.

  As described above, when the mobile phone 201 and the reader / writer 202 exchange packets without contact, when a packet corresponding to a service-specific command such as the first packet or the third packet is exchanged, a general-purpose APDU There are times when commands are exchanged in a command format conforming to ISO 7816-4.

  There is also a wired communication path. That is, referring to FIG. 10, when communication is performed on the communication path 303 (FIG. 7), the communication path 322 (FIG. 8), and the communication path 353 (FIG. 9), the protocol is a protocol for performing serial communication. As packets that can be transmitted and received, there are a wire-specific packet and a packet of TPDU (Transport Protocol Data Unit) (ISO 7816-3) standard.

  When it is desired to perform processing for the third application 256, the unique wired packet is used to exchange the third command (FeliCa command). The TPDU standard packet is used to exchange a general-purpose command, in this case, an APDU command.

  With reference to FIG. 11, the first communication method (Type A), the second communication method (Type B), the third communication method (Type F), and the hierarchical structure in cable will be described. The first communication method corresponding to the first application 254 corresponds to the ISO 14443-3 Type A standard as an initialization / anti-collision layer. The first communication method corresponds to a unique packet and a general-purpose packet conforming to the ISO 14443-4 standard as a packet layer. The command layer of the first communication method corresponds to a unique command format as a command layer corresponding to a unique packet of the packet layer, and ISO 7816 as a command layer corresponding to a general packet of the ISO 14443-4 standard of the packet layer. -4 conforms to the APDU command format.

  The second communication method corresponding to the second application 255 corresponds to the ISO 14443-3 Type B standard as an initialization / collision prevention layer. The second communication method corresponds to a general-purpose packet of the ISO 14443-4 standard as a packet layer. The Type B command layer corresponds to the APDU command format conforming to ISO 7816-4 as a command layer corresponding to the general packet of the ISO 14443-4 standard of the packet layer.

  The third communication method corresponding to the third application 256 corresponds to the ISO 18092 standard as an initialization / anti-collision layer. The third communication method corresponds to the ISO 14443-4 standard packet and the FeliCa packet as a packet layer. The command layer of Type F corresponds to the APDU command format conforming to ISO 7816-4 as the command layer corresponding to the packet of the ISO 14443-4 standard of the packet layer, and the command layer corresponding to the FeliCa packet of the packet layer It corresponds to the FeliCa command format.

  Since wired communication is not wireless communication, it is not necessary to provide an initialization / anti-collision layer. The physical connection is realized by ISO 7816-1 and 2. Wired is based on the ISO 7816-3 standard packet as a packet layer. The wired command layer corresponds to the APDU command format conforming to ISO 7816-4 as a command layer corresponding to the packet of the ISO 7816-3 standard of the packet layer.

  As described above, since there are a plurality of communication paths for accessing the first application 254, the second application 255, and the third application 256, the reader / writer 202 determines which communication path (communication method) is used for data transfer. It is necessary to judge.

  Here, FIG. 6 will be referred to again. As shown in FIG. 6, when the first application 254, the second application 255, and the third application 256 are managed by the UICC 222, when the processing by the viewer 241 is executed, for example, as shown in FIG. Screen is provided to the user. A screen is a screen displayed on the display 401 of the mobile phone 201, for example.

  As shown in FIG. 12, the viewer 241 recognizes the first application 254, the second application 255, and the third application 256 recognized by the application manager 252. The viewer 241 includes a “first service” that is a name of a service provided by the first application 254, a “second service” that is a name of a service provided by the second application 255, and a service provided by the third application 256. “Third service” is displayed on the display 401.

  The third application 256 is a comprehensive service and can provide a plurality of services as shown in FIG. That is, in the example illustrated in FIG. 13, the third application 256 is configured to be able to provide the 3-1 service 257, the 3-2 service 258, and the 3-3 service 259.

  Thus, even if the third application 256 can provide the 3-1 service 257, the 3-2 service 258, and the 3-3 service 259, the viewer 241 is registered on the application manager 252. Can recognize only the first application 254, the second application 255, and the third application 256, and also recognizes the 3-1 service 257, the 3-2 service 258, and the 3-3 service 259. Information cannot be presented to the user.

  This is because the registered service information is managed in the registry 253. Here, registration of applications and services will be described.

  As shown in FIG. 14, the 3-1 service 257 is not registered in the UICC 222 (in order to show that it is not registered, it is indicated by a dotted line in FIG. 14, and applications are not shown). At this time, when registering the 3-1 service 257, data 431 for registering the service is transmitted from outside the UICC 222. Data for registering a service is service registration data. This service registration data 431 is for registering the 3-1 service 257. Such service registration using the service registration data 431 can be performed using the infrastructure that is currently used. Referring to FIG. 14, the service registration data 431 can be passed from the reader / writer 202 to the UICC 222 via the CLF 224. Alternatively, data can be passed from the host 221 to the UICC 222 via the UART.

  However, even if the 3-1 service 257 is registered with the service registration data 431, the information on the 3-1 service 257 is not registered in the registry 253 of the application manager 252. Therefore, it cannot be recognized that such a service has been registered. Therefore, in order to update the information managed in the registry 253, a process for registering the service type and name needs to be performed.

  For example, it is necessary to send a service type / name command 432 to the application manager 252 and update management information (information in the registry 253) in the application manager 252. In this case, the third application 256 needs to be registered in the registry 253 of the application manager 252 with the service type / name command 432 that the 3-1 service 257 is included (newly registered).

  As in the third application, for each of the 3-1 service 257, the 3-2 service 258, and the 3-3 service 259 provided by the third application 256, the fourth, fifth, sixth, It is possible to register each. In this case, the 3-1 service 257, the 3-2 service 258, and the 3-3 service 259 can be registered as the fourth, fifth, and sixth applications, respectively. However, if such registration is performed, the existing service registration data 431 cannot be used, the operation using the relationship between the current applications cannot be applied, and the operation using the existing infrastructure can be performed. There is a possibility of disappearing.

  In order to make it possible to browse individual services with the viewer 241 while making the best use of the existing infrastructure, as described above, the service registration data 431 and the service type / name command 432 are respectively transmitted and the service name is transmitted. Can be registered. Here, the third application 256 has been described as including a plurality of services, but the same applies to the case where the first application 254 and the second application 255 include a plurality of services.

  As described with reference to FIGS. 7 to 11, each of the first application 254, the second application 255, and the third application 256 can be accessed through a plurality of communication paths. Since the third application 256 has the communication paths 351 to 354 (FIG. 9), for example, the 3-1 service 257 can be registered on the communication path 351 and the information on the registry 253 can be updated on the communication path 352. it can.

  In order to make this possible, when the reader / writer 202 executes registration or update processing for the mobile phone 201, the communication path is used for registration and the communication path is used for updating. It is necessary to generate an appropriate command based on the determination, for example, a command in a packet of a protocol suitable for the selected communication path.

[About reader / writer configuration]
Therefore, the reader / writer 202 is configured to have a function as shown in FIG. That is, the reader / writer 202 includes a communication control unit 501, a communication method determination unit 502, a service registration unit 503, and an update processing unit 504. The communication control unit 501 is a contactless communication between a predetermined application (for example, the third application 256) and the UICC 222 including the application manager 252 that manages a service (for example, the 3-1 service 257) provided by the application. To control.

  The communication method determination unit 502 performs a process of determining a communication method when registering a predetermined service in the UICC 222 and a communication method when updating the registry 253.

  The service registration unit 503 executes, for example, generation of a command for registering a predetermined service in the UICC 222 by the communication method determined by the communication method determining unit 502. The update processing unit 504 executes generation of a command for updating information managed in the registry 253 of the UICC 222 by the communication method determined by the communication method determining unit 502.

[About reader / writer processing]
Next, the processing of the reader / writer 202 will be described with reference to the flowchart of FIG. In step S1, the communication method determination unit 502 determines the communication method. The determination of the communication method executed in step S1 is performed by executing any one of the first to eighth determination processes to be described later with reference to FIGS.

  When a communication method for registering a service and a communication method for registering a service name are determined in step S1, a service registration process is first executed by the service registration unit 503 in the determined communication method in step S2. . In step S3, the update processing unit 504 executes a service name registration process (a process for updating the registry 253) using the determined communication method. Processing related to the registration of the service and the registration of the service name will be described later with reference to the flowcharts of FIG.

  First, a communication method for registering a service with the UICC 222 executed in step S1 and a process for determining a communication method for updating the registry 253 will be described. The process related to the determination of the communication method will be described with eight examples.

[About the first determination process of the communication method]
A first method for determining a communication method will be described with reference to a flowchart of FIG. 17 in which all communication methods are tried and a communication method capable of performing good communication is selected. In step S11, it is determined whether the first communication method can be used. For example, it is determined whether or not the first communication method can be used by determining whether or not a packet in the first communication method is transmitted and a response is received.

  If it is determined in step S11 that the first communication method can be used, the process proceeds to step S12. In step S12, it is determined whether or not the APDU command format can be used. For example, it is determined whether an APDU command format is available by generating an APDU command and determining whether there is a response to the APDU command.

  If it is determined in step S12 that the APDU command format can be used, the process proceeds to step S13. If it is determined in step S12 that the APDU command format is not usable, the process proceeds to step S13. Furthermore, if it is determined in step S11 that the first communication method cannot be used, the process proceeds to step S13.

  That is, by performing the processing of step S11 and step S12, it is determined whether or not the CLF 224 can communicate with the first communication method, and if communication is possible with the first communication method, A determination is made as to whether the APDU command format is available. Such a determination result is appropriately retained.

  In step S13, it is determined whether the second communication method can be used. If it is determined in step S13 that the second communication method can be used, the process proceeds to step S14. In step S14, it is determined whether or not the APDU command format can be used. If it is determined in step S14 that the APDU command format can be used, the process proceeds to step S15. If it is determined in step S14 that the APDU command format is not usable, the process proceeds to step S15. Furthermore, if it is determined in step S13 that the second communication method cannot be used, the process proceeds to step S15.

  That is, by executing the processing of step S13 and step S14, it is determined whether or not the mobile phone 201 can perform communication using the second communication method. When communication is possible using the second communication method, Further, it is determined whether or not the APDU command format is available. Such a determination result is appropriately retained.

  In step S15, it is determined whether or not the third communication method can be used. If it is determined in step S15 that the third communication method can be used, the process proceeds to step S16. In step S16, it is determined whether or not the APDU command format can be used. If it is determined in step S16 that the APDU command format can be used, the process proceeds to step S17. If it is determined in step S16 that the APDU command format is not usable, the process proceeds to step S17. Furthermore, if it is determined in step S15 that the third communication method cannot be used, the process proceeds to step S17.

  That is, by performing the processing of step S15 and step S16, it is determined whether or not the CLF 224 can communicate with the third communication method, and if communication with the third communication method is possible, A determination is made as to whether the APDU command format is available. Such a determination result is appropriately retained.

  In step S17, all determination results are held. If it is available, a flag is set, and if it is not available, a table managed under the condition that the flag is not set is used so that the judgment result at each step is held. Anyway.

  In step S18, the optimum process is selected from the state. In this selection, a communication method that is assumed to be usable is selected. Depending on the case, a communication method in which the APDU command format is determined to be usable is selected, or a communication method using a unique packet is selected. The order of selection is set, and the communication method determined to be usable is selected according to the order. Selection is performed based on such a preset selection condition. Further, the selection is performed reflecting the restrictions of the reader / writer 202 and the like.

  In step S19, communication is executed by the communication method selected in step S18. For example, when the first communication method is selected, communication is performed using the first communication method. As a result, it is determined in step S20 whether the process (communication) is successful. If the process is not performed normally for some reason, communication in that communication method is stopped and a different communication method is selected.

  That is, if it is determined in step S20 that the process using the selected communication method has not been successful, the process proceeds to step S21, the state (condition) is updated, and after the update, the process proceeds to step S18. Is returned, and the subsequent processing is repeated. The update executed in step S21 is, for example, a process of updating (changing) a communication method in which communication has failed to a determination result of an unusable communication method.

  On the other hand, if it is determined in step S20 that the process has been successful with the selected communication method, the process of the flowchart shown in FIG. 17 relating to the communication method determination process is terminated. As subsequent processing, service registration and registry 253 update are performed using the selected communication method. Such processing will be described later.

  Note that the order of the processing shown in FIG. 17 is an example, and does not indicate limitation. That is, all the communication methods of the first communication method, the second communication method, and the third communication method are tried, and the result is held. Therefore, there is no difference depending on which communication method is used, and any communication method may be used. .

  As described above, when the reader / writer 202 is configured to be able to communicate with the CLF 224 using a plurality of communication methods, it is determined for each communication method whether or not communication with the CLF 224 can be performed. From the determined communication methods, the communication method determined to be optimal at that time is selected.

  In this way, by determining the communication method by trying all the communication methods, there is an advantage that even if communication in the selected communication method fails, recovery is easy.

[Second communication method determination process]
As the second determination process of the communication method, it is determined whether or not the communication method can be used in the order of the first communication method, the second communication method, and the third communication method. A case where the communication method is determined by selecting the communication method will be described with reference to the flowchart of FIG.

  In the determination process described with reference to the flowcharts of FIGS. 18 to 24, the basic process flow is the same. First, one communication system is selected from among a plurality of communication systems, and the UICC 222 and the communication system are selected. It is determined whether communication is possible. When it is determined that communication is not possible, another communication method is selected again and communication with the UICC 222 is tried again. Then, when communication becomes possible with the selected communication method, the communication method that enables the communication is selected.

  In step S51, it is determined whether the first communication method can be used. If it is determined in step S51 that the first communication method can be used, the process proceeds to step S52. In step S52, it is determined whether or not the APDU command format can be used. If it is determined in step S52 that the APDU command format can be used, the process proceeds to step S53.

  In step S53, it is determined that the first communication method is realized, and the communication method determination processing ends. That is, in this case, communication is possible using the first communication method, and the APDU command format in the first communication method can be used. Therefore, service registration and registry 253 update (registration of registered service) can be performed using the first communication method. Set when name is added). In the subsequent processing, service registration and service name addition are performed using the set communication method.

  On the other hand, if it is determined in step S52 that the APDU command format cannot be used, the process proceeds to step S54. In step S54, it is determined whether the second communication method can be used. If it is determined in step S54 that the second communication method can be used, the process proceeds to step S55.

  In this case, since it is determined that the first communication method and the second communication method can be used, in step S55, registration and update processing are realized using the first communication method and the second communication method. Then it is set. Specifically, it is set when service registration is performed in the first communication method and service name registration is performed in the second communication method. Alternatively, it is set when a service and a service name are registered only in the second communication method.

  In this case, since the second communication method is a method in which communication is performed in the APDU command format, when it is determined that the second communication method can be used, it is determined whether the APDU command format can be used. I will not.

  In FIG. 18, “first communication method / second communication method” indicates that the APDU command format cannot be used in the first communication method described before “/”, and is described after “/”. In the second communication method, the APDU command format is usable. The same applies to other drawings. In the case of the description of A / B, A indicates that the APDU command format cannot be used, and B indicates that the APDU command format can be used.

  On the other hand, if it is determined in step S54 that the second communication method cannot be used, the process proceeds to step S56. In step S56, it is determined whether the third communication method can be used. If it is determined in step S56 that the third communication method can be used, the process proceeds to step S57.

  In step S57, it is determined whether or not the APDU command format can be used. If it is determined in step S57 that the APDU command format can be used, the process proceeds to step S58.

  In this case, since it is determined that the APDU command format can be used in the first communication method, the third communication method, and the third communication method, in step S58, the first communication method and the third communication method are used. This method is set when registration and update processing are realized. In this case, service registration is performed using any of the APDU commands in the first communication method, the third communication method, and the third communication method, and the service name is obtained using the APDU command in the third communication method. Set when registration is performed.

  On the other hand, if it is determined in step S51 that the first communication method cannot be used, the process proceeds to step S60. In step S60, it is determined whether or not the second communication method can be used. If it is determined in step S60 that the second communication method can be used, the process proceeds to step S61.

  In this case, since it is determined that the second communication method can be used, in step S61, it is set that registration and update processing are realized by the second communication method.

  On the other hand, if it is determined in step S60 that the second communication method cannot be used, the process proceeds to step S62. In step S62, it is determined whether the third communication method can be used. If it is determined in step S62 that the third communication method can be used, the process proceeds to step S63.

  In step S63, it is determined whether or not the APDU command format can be used. If it is determined in step S63 that the APDU command format can be used, the process proceeds to step S64.

  In this case, since it has been determined that the third communication method and the APDU command format in the third communication method can be used, in step S64, registration and update processing are realized in the third communication method. Then it is set. Specifically, it is set when the service registration is performed with the third communication method or the APDU command in the third communication method, and the service name is registered with the APDU command in the third communication method.

  On the other hand, if it is determined in step S62 that the third communication method cannot be used, the process proceeds to step S65. In this case, communication cannot be performed using all of the first communication method, the second communication method, and the third communication method. In other words, communication with the CLF 224 is performed using the communication method supported by the reader / writer 202. In this case, it is determined that communication is not possible in step S65.

  On the other hand, if it is determined in step S63 that the APDU command format cannot be used, the process proceeds to step S59. In this case, it is a time when it is determined that the APDU command format cannot be used although communication is possible using the third communication method. Similarly, if it is determined in step S56 that the third communication method cannot be used, the process proceeds to step S59. In this case, it is determined that communication is possible in the first communication method, but communication is not possible in the second communication method and the third communication method, in which the APDU command format cannot be used.

  Similarly, if it is determined in step S57 that the APDU command format cannot be used, the process proceeds to step S59. In this case, communication is possible in the first communication method and the third communication method, but it is when it is determined that communication using the APDU command format is not possible in either method.

  A common situation when the process proceeds to step S59 is that the APDU command format cannot be used. When the APDU command format cannot be used, the registry 253 cannot be updated. Although details will be described later, the registry 253 is updated by using an APDU command. Therefore, when the APDU command cannot be used, the registry 253 cannot be updated, so that it is realized by an additional function.

  Realization with an additional function means that the registry 253 is updated by providing some function on the UICC 222 or on the application side installed in the UICC. In other words, when it is set to be realized by the first communication method, for example, as in step S53, when it is not realized by the additional function, for example, the service registration or registry is maintained with the current function on the UICC 222 side. This means that 253 can be updated.

  As described above, when the communication method is determined, the registration of the service corresponding to step S2 and step S3 (FIG. 16) and the update of the registry 253 are executed based on the determined communication method as described later. .

[Third communication method determination process]
As the third determination process of the communication method, it is determined whether the communication method can be used in the order of the first communication method, the third communication method, and the second communication method, and it is determined that the communication method can be used. A case where the communication method is determined by selecting the communication method will be described with reference to the flowchart of FIG. In addition, since the process similar to the process in the flowchart of FIG. 18 is included, the description regarding the same process is abbreviate | omitted suitably.

  In step S101, it is determined whether the first communication method can be used. If it is determined in step S101 that the first communication method can be used, the process proceeds to step S102. In step S102, it is determined whether or not the APDU command format can be used. If it is determined in step S102 that the APDU command format can be used, the process proceeds to step S103.

  In step S103, it is determined that the first communication method is realized, and the communication method determination processing ends. That is, in this case, communication is possible in the first communication method, and the APDU command format in the first communication method can be used. Therefore, setting is made when service registration and update are performed in the first communication method.

  On the other hand, if it is determined in step S102 that the APDU command format cannot be used, the process proceeds to step S104. In step S104, it is determined whether the third communication method can be used. If it is determined in step S104 that the third communication method can be used, the process proceeds to step S105.

  In step S105, it is determined whether or not the APDU command format can be used. If it is determined in step S105 that the APDU command format can be used, the process proceeds to step S106.

  In this case, since it is determined that the APDU command format can be used in the first communication method, the third communication method, and the third communication method, in step S106, the first communication method and the third communication method are used. This method is set when registration and update processing are realized.

  On the other hand, if it is determined in step S104 that the third communication method cannot be used, the process proceeds to step S107. In step S107, it is determined whether the second communication method can be used. If it is determined in step S107 that the second communication method can be used, the process proceeds to step S108.

  In this case, since it is determined that the first communication method and the second communication method can be used, in step S108, registration and update processing are realized using the first communication method and the second communication method. Then it is set.

  On the other hand, if it is determined in step S105 that the APDU command format cannot be used, the process proceeds to step S109. In step S109, it is determined whether the second communication method can be used. If it is determined in step S109 that the second communication method can be used, the process proceeds to step S110.

  In this case, it is determined that the first communication method, the third communication method, and the second communication method can be used, and both the first communication method and the third communication method cannot use the APDU command format. In step S110, registration is performed using the first communication method or the third communication method, and update processing is performed using the second communication method.

  On the other hand, if it is determined in step S101 that the first communication method cannot be used, the process proceeds to step S112. In step S112, it is determined whether the third communication method can be used. If it is determined in step S112 that the third communication method can be used, the process proceeds to step S113.

  In step S113, it is determined whether or not the APDU command format can be used. If it is determined in step S113 that the APDU command format can be used, the process proceeds to step S114.

  In this case, since it is determined that the third communication method and the APDU command format in the third communication method can be used, registration and update processing are realized in the third communication method in step S114. Then it is set.

  On the other hand, if it is determined in step S112 that the third communication method cannot be used, the process proceeds to step S115. In step S115, it is determined whether the second communication method can be used. If it is determined in step S115 that the second communication method can be used, the process proceeds to step S116.

  In this case, since it is determined that the second communication method can be used, it is set in step S116 that registration and update processing are realized by the second communication method.

  On the other hand, if it is determined in step S113 that the APDU command format cannot be used, the process proceeds to step S117. In step S117, it is determined whether the second communication method can be used. If it is determined in step S117 that the second communication method can be used, the process proceeds to step S118.

  In this case, since it is determined that the third communication method and the second communication method can be used, in step S118, registration is performed using the third communication method, and update processing is performed using the second communication method. Is set to achieve.

  On the other hand, if it is determined in step S115 that the second communication method cannot be used, the process proceeds to step S119. In this case, communication cannot be performed using all of the first communication method, the second communication method, and the third communication method. In other words, communication with the CLF 224 is performed using the communication method supported by the reader / writer 202. In this case, it is determined that communication is not possible in step S119.

  On the other hand, if it is determined in step S107, step S109, or step S117 that the second communication method cannot be used, the process proceeds to step S111. If it is determined in these steps that the second communication method cannot be used, it means that it is determined that the APDU command format cannot be used.

  In such a case, the UICC 222 is provided with some function so as to realize and set the update of the registry 253 (set when the update using the additional function of the UICC 222 is performed).

[Communication method fourth determination process]
As the fourth determination process of the communication method, it is determined whether the communication method can be used in the order of the second communication method, the first communication method, and the third communication method, and it is determined that the communication method can be used. A case where the communication method is determined by selecting the communication method will be described with reference to the flowchart of FIG.

  In step S151, it is determined whether the second communication method can be used. If it is determined in step S151 that the second communication method can be used, the process proceeds to step S152.

  In this case, since it is determined that the second communication method can be used, it is set in step S152 that registration and update processing are realized by the second communication method.

  On the other hand, if it is determined in step S151 that the second communication method cannot be used, the process proceeds to step S153. In step S153, it is determined whether the first communication method can be used. If it is determined in step S153 that the first communication method can be used, the process proceeds to step S154. In step S154, it is determined whether the APDU command format can be used. If it is determined in step S154 that the APDU command format can be used, the process proceeds to step S155.

  In this case, communication is possible in the first communication method, and the APDU command format in the first communication method can be used. Therefore, in step S155, setting is performed when service registration and update are performed in the first communication method. Is done.

  On the other hand, if it is determined in step S154 that the APDU command format cannot be used, the process proceeds to step S156. In step S156, it is determined whether the third communication method can be used. If it is determined in step S156 that the third communication method can be used, the process proceeds to step S157. In step S157, it is determined whether or not the APDU command format can be used. If it is determined in step S157 that the APDU command format can be used, the process proceeds to step S158.

  In this case, since it has been determined that the APDU command format can be used in the first communication method, the third communication method, and the third communication method, in step S158, the first communication method and the third communication method are used. This method is set when registration and update processing are realized. In this case, it is set when the service registration is performed in the first communication method or the third communication method, and is set when the service name is registered in the third communication method.

  On the other hand, if it is determined in step S153 that the first communication method cannot be used, the process proceeds to step S160. In step S160, it is determined whether the third communication method can be used. If it is determined in step S160 that the third communication method can be used, the process proceeds to step S161. In step S161, it is determined whether or not the APDU command format can be used. If it is determined in step S161 that the APDU command format can be used, the process proceeds to step S162.

  In this case, since it has been determined that the third communication method and the APDU command format in the third communication method can be used, in step S162, registration and update processing are realized by the third communication method. Then it is set.

  On the other hand, if it is determined in step S160 that the third communication method cannot be used, the process proceeds to step S164. In this case, communication cannot be performed using all of the first communication method, the second communication method, and the third communication method. In other words, communication with the CLF 224 is performed using the communication method supported by the reader / writer 202. In this case, it is determined that communication is impossible in step S164.

  On the other hand, if it is determined in step S156 that the third communication method cannot be used, or if it is determined in step S157 or S161 that the APDU command format cannot be used, the process proceeds to step S163. It is done. In such a case, it means that it is determined that the APDU command format cannot be used. Therefore, when updating of the registry 253 is realized by providing some function in the UICC 222, it is set in step S163 (set when updating using the additional function of the UICC 222).

[About the fifth determination process of the communication method]
As the fifth determination process of the communication method, it is determined whether the communication method can be used in the order of the second communication method, the third communication method, and the first communication method, and it is determined that the communication method can be used. A case where the communication method is determined by selecting the communication method will be described with reference to the flowchart of FIG.

  In step S201, it is determined whether the second communication method can be used. If it is determined in step S201 that the second communication method can be used, the process proceeds to step S202.

  In this case, since it is determined that the second communication method can be used, in step S202, it is set that registration and update processing are realized by the second communication method.

  On the other hand, if it is determined in step S201 that the second communication method cannot be used, the process proceeds to step S203. In step S203, it is determined whether the third communication method can be used. If it is determined in step S203 that the third communication method can be used, the process proceeds to step S204. In step S204, it is determined whether or not the APDU command format can be used. If it is determined in step S204 that the APDU command format can be used, the process proceeds to step S205.

  In this case, communication is possible in the third communication method, and the APDU command format in the third communication method can be used. Therefore, in step S205, setting is performed when service registration and update are performed in the third communication method. Is done.

  On the other hand, if it is determined in step S204 that the APDU command format cannot be used, the process proceeds to step S206. In step S206, it is determined whether the first communication method can be used. If it is determined in step S206 that the first communication method can be used, the process proceeds to step S207. In step S207, it is determined whether or not the APDU command format can be used. If it is determined in step S207 that the APDU command format can be used, the process proceeds to step S208.

  In this case, since it is determined that the APDU command format in the third communication method, the first communication method, and the first communication method can be used, in step S208, the third communication method or the first communication method is used. This is set when service registration is performed by the method and the service name is updated by the APDU command in the first communication method.

  On the other hand, if it is determined in step S203 that the third communication method cannot be used, the process proceeds to step S209. In step S209, it is determined whether the first communication method can be used. If it is determined in step S209 that the first communication method can be used, the process proceeds to step S210. In step S210, it is determined whether or not the APDU command format can be used. If it is determined in step S210 that the APDU command format can be used, the process proceeds to step S211.

  In this case, since it has been determined that the first communication method and the APDU command format in the first communication method can be used, in step S211, registration and update processing are realized in the first communication method. Then it is set.

  On the other hand, if it is determined in step S209 that the first communication method cannot be used, the process proceeds to step S213. In this case, communication cannot be performed using all of the first communication method, the second communication method, and the third communication method. In other words, communication with the CLF 224 is performed using the communication method supported by the reader / writer 202. Therefore, in step S213, it is determined that communication is not possible.

  On the other hand, if it is determined in step S206 that the first communication method cannot be used, or if it is determined in step S207 or step S210 that the APDU command format cannot be used, the process proceeds to step S212. It is done. In such a case, it means that it is determined that the APDU command format cannot be used. Therefore, when updating of the registry 253 is realized by providing some function in the UICC 222, it is set in step S212 (set when updating using the additional function of the UICC 222).

[About the communication system sixth determination process]
As the sixth determination process of the communication method, it is determined whether the communication method can be used in the order of the third communication method, the first communication method, and the second communication method, and it is determined that the communication method can be used. A case where the communication method is determined by selecting the communication method will be described with reference to the flowchart of FIG.

  In step S251, it is determined whether the third communication method can be used. If it is determined in step S251 that the third communication method can be used, the process proceeds to step S252. In step S252, it is determined whether the APDU command format can be used. If it is determined in step S252 that the APDU command format can be used, the process proceeds to step S253.

  In this case, the third communication method can be used, and the APDU command format in the third communication method can be used. Therefore, when service registration and update are performed in the third communication method, the setting is made in step S253. The

  On the other hand, if it is determined in step S252 that the APDU command format cannot be used, the process proceeds to step S254. In step S254, it is determined whether the first communication method can be used. If it is determined in step S254 that the first communication method can be used, the process proceeds to step S255. In step S255, it is determined whether or not the APDU command format can be used. If it is determined in step S255 that the APDU command format can be used, the process proceeds to step S256.

  In this case, since it is determined that the APDU command format in the third communication method, the first communication method, and the first communication method can be used, in step S256, the third communication method and the first communication method are used. This method is set when registration and update processing are realized.

  On the other hand, if it is determined in step S254 that the first communication method cannot be used, the process proceeds to step S257. In step S257, it is determined whether the second communication method can be used. If it is determined in step S257 that the second communication method can be used, the process proceeds to step S258.

  In this case, since it is determined that the third communication method and the second communication method can be used, in step S258, registration and update processing are realized by the third communication method and the second communication method. Then it is set.

  On the other hand, if it is determined in step S255 that the APDU command format cannot be used, the process proceeds to step S259. In step S259, it is determined whether the second communication method can be used. If it is determined in step S259 that the second communication method can be used, the process proceeds to step S260.

  In this case, it is determined that the third communication method, the first communication method, and the second communication method can be used, and both the third communication method and the first communication method cannot use the APDU command format. In step S260, registration is performed using the third communication method or the first communication method, and update processing is performed using the second communication method.

  On the other hand, if it is determined in step S251 that the third communication method cannot be used, the process proceeds to step S262. In step S262, it is determined whether the first communication method can be used. If it is determined in step S262 that the first communication method can be used, the process proceeds to step S263. In step S263, it is determined whether or not the APDU command format can be used. If it is determined in step S263 that the APDU command format can be used, the process proceeds to step S264.

  In this case, since it has been determined that the first communication method and the APDU command format in the first communication method can be used, in step S264, registration and update processing are realized by the first communication method. Then it is set.

  On the other hand, if it is determined in step S262 that the first communication method cannot be used, the process proceeds to step S265. In step S265, it is determined whether the second communication method can be used. If it is determined in step S265 that the second communication method can be used, the process proceeds to step S266.

  In this case, since it is determined that the second communication method can be used, it is set in step S266 that registration and update processing are realized by the second communication method.

  On the other hand, if it is determined in step S263 that the APDU command format cannot be used, the process proceeds to step S267. In step S267, it is determined whether the second communication method can be used. If it is determined in step S267 that the second communication method can be used, the process proceeds to step S268.

  In this case, since it is determined that the first communication method and the second communication method can be used, in step S268, registration is performed using the first communication method, and update processing is performed using the second communication method. Is set to achieve.

  On the other hand, if it is determined in step S265 that the second communication method cannot be used, the process proceeds to step S269. In this case, communication cannot be performed using all of the first communication method, the second communication method, and the third communication method. In other words, communication with the CLF 224 is performed using the communication method supported by the reader / writer 202. Therefore, in step S269, it is determined that communication is not possible.

  On the other hand, if it is determined in step S257, step S259, or step S267 that the second communication method cannot be used, the process proceeds to step S261. If it is determined in these steps that the second communication method cannot be used, it means that it is determined that the APDU command format cannot be used.

  In such a case, it is set to update the registry 253 by providing some function in the UICC 222 (set when updating using the additional function of the UICC 222).

[About the seventh determination process of the communication method]
As the seventh determination process of the communication method, it is determined whether the communication method can be used in the order of the third communication method, the second communication method, and the first communication method, and it is determined that the communication method can be used. A case where the communication method is determined by selecting the communication method will be described with reference to the flowchart of FIG.

  In step S301, it is determined whether the third communication method can be used. If it is determined in step S301 that the third communication method can be used, the process proceeds to step S302. In step S302, it is determined whether or not the APDU command format can be used. If it is determined in step S302 that the APDU command format can be used, the process proceeds to step S303.

  In this case, communication is possible in the third communication method, and the APDU command format in the third communication method can be used. Therefore, when registration and update are performed in the third communication method, they are set in step S303.

  On the other hand, if it is determined in step S302 that the APDU command format cannot be used, the process proceeds to step S304. In step S304, it is determined whether the second communication method can be used. If it is determined in step S304 that the second communication method can be used, the process proceeds to step S305.

  In this case, since it is determined that the third communication method and the second communication method can be used, in step S305, registration and update processing are realized using the third communication method and the second communication method. Then it is set.

  On the other hand, if it is determined in step S304 that the second communication method cannot be used, the process proceeds to step S306. In step S306, it is determined whether the first communication method can be used. If it is determined in step S306 that the first communication method can be used, the process proceeds to step S307. In step S307, it is determined whether or not the APDU command format can be used. If it is determined in step S307 that the APDU command format can be used, the process proceeds to step S308.

  In this case, since it is determined that the APDU command format in the third communication method, the first communication method, and the first communication method can be used, in step S308, the third communication method or the first communication method is used. This is set when service registration is performed using the method, and service name registration is performed using the APDU command format in the first communication method.

  On the other hand, if it is determined in step S301 that the third communication method cannot be used, the process proceeds to step S310. In step S310, it is determined whether the second communication method can be used. If it is determined in step S310 that the second communication method can be used, the process proceeds to step S311.

  In this case, since it is determined that the second communication method can be used, in step S311, it is set that registration and update processing are realized by the second communication method.

  On the other hand, if it is determined in step S310 that the second communication method cannot be used, the process proceeds to step S312. In step S312, it is determined whether the first communication method can be used. If it is determined in step S312 that the first communication method can be used, the process proceeds to step S313. In step S313, it is determined whether the APDU command format can be used. If it is determined in step S313 that the APDU command format can be used, the process proceeds to step S314.

  In this case, since it is determined that the first communication method and the APDU command format in the first communication method can be used, in step S314, registration and update processing are realized by the first communication method. Then it is set.

  On the other hand, if it is determined in step S312 that the first communication method cannot be used, the process proceeds to step S315. In this case, communication cannot be performed with all of the third communication method, the second communication method, and the first communication method. In other words, communication with the CLF 224 is performed with the communication method supported by the reader / writer 202. Therefore, in step S315, it is determined that communication is not possible.

  On the other hand, if it is determined in step S306 that the first communication method cannot be used, or if it is determined in step S307 or step S313 that the APDU command format cannot be used, the process proceeds to step S309. It is done. In such a case, it means that it is determined that the APDU command format cannot be used. Therefore, when updating of the registry 253 is realized by providing some function in the UICC 222, it is set in step S309 (set when updating using the additional function of the UICC 222).

[Eighth communication processing determination process]
As an eighth communication method determination process, refer to the flowchart of FIG. 24 when the communication method is determined by communicating with the mobile phone 201 and acquiring information on the communication method supported by the mobile phone 201. To explain.

  In step S351, it is determined whether the third communication method can be used. If it is determined in step S351 that the third communication method can be used, the process proceeds to step S352. In step S352, communication method information is exchanged.

  In this case, since it is determined in step S351 that the third communication method can be used, communication with the mobile phone 201 is performed in the third communication method, and the mobile phone 201 and the reader / writer 202 support each other. Exchange of information on the communication method being performed is performed.

  For example, the reader / writer 202 issues a command for instructing the mobile phone 201 to notify the communication method supported by the mobile phone 201 to the mobile phone 201 using the third communication method. The communication method information is exchanged by notifying the communication method supported by itself in response to the received command.

  Alternatively, in the third communication method, the reader / writer 202 notifies the mobile phone 201 of a communication method supported by the reader / writer 202 itself, and the mobile phone 201 that has received the notification notifies the mobile communication device of the notified communication methods. By selecting a communication method supported by itself and returning the selected information to the reader / writer 202, information exchange of the communication methods supported by each other is performed.

  If communication method information is exchanged in step S352, the process proceeds to step S353. In step S353, the processing content is determined from the communication methods acquired as a result of the information exchange. This processing content is, for example, the content of executing registration and update processing in the third communication method.

  On the other hand, if it is determined in step S351 that communication of the third communication method is not possible, the process proceeds to step S354. In step S354, it is determined whether the second communication method can be used. If it is determined in step S354 that the second communication method can be used, the process proceeds to step S352.

  The processing in step S352 has been described above, but in this case, the second communication method is used and information exchange of the communication method is performed, which is different from the above-described case. In step S353, the processing content is determined from the information regarding the communication method obtained as a result of the information exchange.

  On the other hand, if it is determined in step S354 that communication using the second communication method is not possible, the process proceeds to step S355. In step S355, it is determined whether the first communication method can be used. If it is determined in step S355 that the first communication method can be used, the process proceeds to step S352.

  The processing in step S352 has been described above, but in this case, the first communication method is used and information exchange of the communication method is performed, which is different from the above-described case. In step S353, the processing content is determined from the information regarding the communication method obtained as a result of the information exchange.

  On the other hand, if it is determined in step S355 that communication using the first communication method is not possible, the process proceeds to step S356. In this case, since it is determined that the first communication method, the second communication method, and the third communication method are not available, it is determined in step S356 that communication with the mobile phone 201 is impossible. And the process is terminated.

  As described above, when the reader / writer 202 is configured to be able to communicate with a plurality of communication methods, first, one communication method is selected from the plurality of communication methods, and communication with the UICC 222 is possible with the communication method. It is determined whether or not there is. When it is determined that communication is possible, information regarding the communication method is exchanged with the UICC 222 using the communication method, and a communication method is selected using the information exchange result.

  Here, it has been described that it is determined whether or not the use is possible in the order of the third communication method, the second communication method, and the first communication method, but this means that it is limited to this order. is not.

  Here, the first determination process to the eighth determination process have been described as examples of the communication method determination process, but which determination process is used to perform the process? It may be determined according to the design stage of the reader / writer 202, the installation location, and the like.

  For example, when the user can set the communication method, the determination process may be selected from the first determination process to the eighth determination process according to the communication method set by the user. For example, in the second determination process to the eighth determination process, it is first determined whether any one of the first communication method, the second communication method, and the third communication method can be used. Judging. Accordingly, a determination process for determining whether or not the communication method selected by the user can be used first may be selected.

  For example, when the user selects the first communication method, the second determination process shown in the flowchart of FIG. 18 may be started, or the third determination process shown in the flowchart of FIG. 19 is started. You may make it. In this case, in the eighth determination process shown in the flowchart of FIG. 24, a determination process for determining whether or not the first communication method can be used first may be executed. .

[Registration and update processing]
By executing the processing described above, a communication method for registering a service and a communication method for updating the registry 253 (service name registration processing) are determined. Here, combinations of communication methods that may be set as a result of the processing described above are listed.

First combination (for example, set in step S314 in FIG. 23)
Both registration and update are performed in the first communication method (APDU command format can be used in the first communication method)
Second combination (for example, set in step S311 in FIG. 23)
3rd combination (for example, set by step S303 of FIG. 23) which performs both registration and update by the 2nd communication system
Both registration and update are performed in the third communication method (APDU command format can be used in the third communication method).

Fourth combination (for example, set in step S55 in FIG. 18)
Registration is performed using the first communication method, and updating is performed using the second communication method (the APDU command format cannot be used in the first communication method).
Fifth combination (for example, set in step S260 in FIG. 22)
Registration is performed in the first communication method or the third communication method, and update is performed in the second communication method (the APDU command format cannot be used in the first communication method and the third communication method).
Sixth combination (for example, set in step S305 in FIG. 23)
Registration is performed by the third communication method, and update is performed by the second communication method (the APDU command format cannot be used in the third communication method).

Seventh combination (for example, set in step S58 in FIG. 18)
Registration is performed using the first communication method, and updating is performed using the third communication method (the APDU command format cannot be used in the first communication method).
Eighth combination (for example, set in step S308 of FIG. 23)
Registration is performed by the third communication method, and update is performed by the first communication method (the APDU command format cannot be used in the third communication method).

Ninth combination (for example, set in step S309 in FIG. 23)
Realize with additional functions (add functions to UICC 222 and register and update)

  In this way, nine combinations may be set. Further, in the above-described communication method determination processing, although wired is not described, there is communication via wired, for example, the communication path 353 shown in FIG.

  Here, as described above, the case where the third application 256 is an application that provides the 3-1 service 257, the 3-2 service 258, and the 3-3 service 259 will be described as an example. Here, a case where the 3-1 service 257 is additionally registered in the third application 256 (the case described with reference to FIG. 14) will be described as an example.

  It is conceivable to register and update the 3-1 service 257 with a combination of commands as shown in FIG. Referring to FIG. 25, the communication method used in the combination of number 1 is the case of the first communication method or the second communication method. The combination of number 1 corresponds to the first combination or the second combination described above.

  In the combination of number 1, since the APDU command format can be transmitted and received, the APDU command format is used for service registration and service name registration. At this time, for registration of the service, a packet in the APDU command format used in the set communication method (in this case, the first communication method or the second communication method) and a third command that is a unique command of the third application 256 are used. Data associated with the command is generated and transmitted / received. Specifically, at this time, the service registration is performed by wrapping the third command in the APDU command format. An APDU command is used for registering the service name (updating the registry 253).

  The communication method used in the combination of number 2 is the case of the third communication method. The combination of number 2 corresponds to the above-described third combination. In the combination of number 2, since the APDU command format and the third packet can be transmitted and received, the APDU command format and the third packet are used for service registration and service name registration. At this time, the third command is used for service registration. In addition, an APDU command is used for registration of the service name, and the APDU command format in the third communication method is used for the packet.

  In the case of the number 2 combination, as in the case of the number 1 combination, the service registration is performed by wrapping the third command in the APDU command format, and the service name is registered (update of the registry 253). It is also possible to use an APDU command in the third communication method.

  The communication method used in combination with the number 3 is a combination of the first communication method and the third communication method, or a combination of the second communication method and the third communication method. The combination of number 3 corresponds to the fifth to eighth combinations described above. In the combination of number 3, since the APDU command format and the third packet can be transmitted and received, the APDU command format and the third packet are used for service registration and service name registration.

  At this time, if the third communication method corresponds to the APDU command format, the third command is used for service registration, and the APDU command is used for service name registration, as in the case of the combination of number 2. If the third communication method does not support the APDU command format, the service registration uses the third command wrapped in the APDU command format, and the service name registration uses the APDU command. . At this time, transmission / reception of the APDU command format for wrapping the third command is performed based on the first communication method or the second communication method corresponding to the APDU command format.

  The communication method used in combination with numbers 4 to 6 is wired. The combination of number 4 is when the APDU command format can be transmitted / received. Like the combination of number 1, the service registration uses the third command wrapped in the APDU command format, and the service name is registered. APDU command is used.

  The combination of number 5 is when a packet in the APDU command format and the wired protocol can be transmitted and received, the third command is used for service registration, and the APDU command is used for service name registration. Alternatively, similar to the combination of number 4, the service registration may be performed by wrapping the third command in the APDU command format, and the service name may be registered using the APDU command.

  The communication method used in combination with the number 6 is wired, and is when the packet in the wired protocol can be transmitted and received. The communication method used in combination with the number 7 is the third communication method, which is when the third packet can be transmitted and received. This combination of numbers 6 and 7 corresponds to the ninth combination described above. This is the case when only a unique packet is supported as a communication method.

  If only a communication method using a unique packet can be used, the reader / writer 202 cannot register a service or service name simply by processing the packet. Updates are made. For example, new service registration data and a new command (or block) are registered and updated via an application (in this case, via the third application 256).

  Next, regarding the processing related to the registration of the service executed in step S2 (FIG. 16) and the registration of the service name executed in step S3, together with the processing executed on the mobile phone 201 side, a flowchart is shown. The description will be given with reference.

[Registration of services and service names using the third communication method and the second communication method]
First, with reference to the flowcharts of FIG. 26 and FIG. 27, it is determined that the third communication method can be used, but it is determined that the APDU command format in the third communication method cannot be used, and A case where it is determined that the two communication methods can be used will be described.

  The setting is made when, for example, the third communication method / second communication method is set in step S305 as a result of executing the processing of the flowchart shown in FIG. This corresponds to the fifth combination or the sixth combination. In FIG. 25, this corresponds to the combination of number 3.

  The flowchart in FIG. 26 is a process for registering a service. First. In step S601, the mobile phone 201 activates the card. The card is the UICC 222. When the card is activated in step S1 (FIG. 16) when the communication method is determined on the reader / writer 202 side, the reader / writer 202 and the mobile phone 201 (CLF 224) are communicating with each other. At that time, the card is activated on the mobile phone 201 side.

  In step S551, the reader / writer 202 requests the mobile phone 201 (CLF 224) to respond in the third communication method. The mobile phone 201 (CLF 224) that has received such a request in step S602 returns a response in step S603. In this case, the response indicates that the communication with the third communication method is accepted. The reader / writer 202 that has received such a response from the mobile phone 201 (CLF 224) in step S552 makes a data read request to the mobile phone 201 (CLF 224) in step S553.

  When the mobile phone 201 (CLF 224) receives a data read request from the reader / writer 202 in step S604, the mobile phone 201 (CLF 224) transfers the request to the third application 256. In this case, since communication is performed by the third communication method, the third packet from the reader / writer 202 is supplied to the third application 256 via the CLF 224 (FIG. 9). That is, in this case, the packet from the reader / writer 202 is supplied to the third application 256 through the communication path 351 described with reference to FIG.

  In step S631, when a data read request is received from the reader / writer 202 through such a communication channel 351 (FIG. 9), the data requested by the read request is read in step S632, and the cellular phone 201 (CLF 224) is read. ). In step S606, the CLF 224 transmits the data supplied from the third application 256 as a response corresponding to the request from the reader / writer 202.

  In step S554, the reader / writer 202 that has acquired the data from the mobile phone 201 (CLF 224) as a response confirms the status of the card included in the read data and the service to be registered in step S555. For example, when the 3-1 service 257 (FIG. 14) is not registered, data of the 3-1 service 257 is prepared. When the data is prepared, service registration is executed in step S556.

  In this case, since the service registration is performed using the third packet in the third communication method, data for service registration is packetized into the third packet, and the mobile phone 201 (CLF 224) is packetized in the third communication method. ) Is transmitted in step S556. This process corresponds to, for example, the process of transmitting the service registration data 431 described with reference to FIG. The mobile phone 201 (CLF 224) that has received the data for service registration from the reader / writer 202 in step S607 supplies the received data to the third application 256.

  When the third application 256 acquires the supplied data in the process in step S633, the third application 256 executes a service registration process in step S634. In step S634, the third application 256 executes registration of the service. As a result, if it succeeds or fails, the result of the registration processing is issued in step S635.

  In step S609, the cellular phone 201 (CLF 224) that has received the result in the process in step S608 transmits the result of the registration process in the third application 256 to the reader / writer 202 as a response. In step S557, the response from the mobile phone 201 (CLF 224) is received by the reader / writer 202.

  When the response indicates that the service registration is successful on the mobile phone 201 side, the reader / writer 202 continues to start the service name registration (described later with reference to FIG. 27) and fails. Is displayed again, for example, the service registration process is executed by executing the process of step S556. If the response from the mobile phone 201 (CLF 224) indicates failure, the service registration process is executed in a communication method different from the communication method set at that time. Anyway. Here, the description will be continued assuming that the process of service registration has been successful.

  If it is determined that the service registration process is successful, the service name registration process is started. Processing for registering the service name will be described with reference to the flowchart of FIG. In this case, since the service registration process described above is performed by the third communication method and the service name registration process is performed by the second communication method, it is necessary to switch the communication method. Therefore, the reader / writer 202 requests the mobile phone 201 (CLF 224) to respond in the second communication method in step S571.

  The mobile phone 201 (CLF 224) that has received such a request in step S661 returns a response in step S662. In this case, the response indicates that the communication with the second communication method is accepted. The reader / writer 202 that has received such a response from the mobile phone 201 (CLF 224) in step S572 issues a request to the mobile phone 201 to select the second communication method in step S573.

  The mobile phone 201 (CLF 224) that has received such a request in step S663 switches to a state in which communication by the second communication method is performed, and then a response (response) indicating that the second communication method has been selected, This is performed for the reader / writer 202. The reader / writer 202 that has received the response in step S574 confirms that the second communication method has been selected on the mobile phone 201 side by confirming the received response.

  In this way, when the reader / writer 202 and the mobile phone 201 (CLF 224) can communicate with each other in the second communication method, the reader / writer 202 executes processing for registering the service name in step S575. For example, in this case, since the 3-1 service 257 is registered, a packet for registering the service name of the 3-1 service 257 in the registry 253 of the mobile phone 201 is generated. The generated packet includes a packet corresponding to the second communication method, that is, in this case, data conforming to the APDU command format.

  In step S575, the reader / writer 202 executes a service name registration process so that data transmitted from the reader / writer 202 to the mobile phone 201 is received by the mobile phone 201 in step S665. The received data is supplied to the application manager 252.

  Since it is an APDU command format, the APDU command format received by the CLF 224 is supplied to the application manager 252 via the UICC hardware 251. The APDU command format is a packet that can be processed by the application manager 252. When the application manager 252 receives data related to service name registration in the APDU command format in step S691, the application manager 252 executes service name registration processing in step S692.

  The application manager 252 writes information such as the name and type of the newly registered service in the registry 253 according to the received APDU command. Information such as the name and type is included in the APDU command supplied from the reader / writer 202.

  In step S692, when the registration of the service name and the like is completed, the application manager 252 outputs the processing result to the CLF 224 as the processing in step S693. When the CLF 224 receives the processing result from the application manager 252 in step S666, the CLF 224 transmits it as a response to the reader / writer 202. This response includes information indicating whether or not the service name registration process is successful.

  The reader / writer 202 that has received such a result in step S576 recognizes that the registration of the service name has been completed when the response indicates a successful response, and ends the process. On the other hand, when the received response indicates failure, for example, the process of registering the service name is executed again by executing the process of step S575 again.

  Thus, when registering the 3-1 service 257 provided by the third application 256, the registration itself is used by the third communication method (third packet and third command) that can be handled by the third application 256. Done. On the other hand, the second communication method (APDU command) that can be handled by the application manager 252 is used for information on the 3-1 service 257, for example, information such as the name of the 3-1 service 257 and the type of service provided. Done.

  As described above, the service is registered and the service name is registered, so that the application manager 252 can manage information related to the registered service in the registry 253. Information on registered services is managed in the registry 253, so that the viewer 241 can browse the information. By enabling the viewer 241 to browse, the information can be provided to the user.

  Therefore, when the third application 256 is an application for providing a comprehensive service and provides three services of a 3-1 service 257, a 3-2 service 258, and a 3-3 service 259, It is possible to present to the user that there are these three services. The method of presentation will be described later, and first, registration of a service and a service name when another combination is set as a combination of communication methods will be described.

[Registering services and service names using the second communication method]
Next, referring to the flowcharts of FIG. 28 and FIG. 29, when it is determined that only the second communication method can be used (when it is set to register the service and service name in the second communication method) ).

  Such a setting is made, for example, when the execution of the process of the flowchart shown in FIG. 23 is executed and, in step S311, it is set to be realized by the second communication method. The flowchart in FIG. 28 is a process for registering a service. First, in step S801, the mobile phone 201 activates the card (UICC 222).

  In step S701, the reader / writer 202 requests the mobile phone 201 (CLF 224) to respond in the second communication method. The mobile phone 201 (CLF 224) that has received such a request in step S802 returns a response in step S803. In this case, the response indicates that the communication with the second communication method is accepted. The reader / writer 202 that has received such a response from the mobile phone 201 (CLF 224) in step S702 issues a request to the mobile phone 201 (CLF 224) to select the second communication method in step S703.

  The mobile phone 201 (CLF 224) that has received such a request in step S804 enters a state in which communication by the second communication method is performed, and thereafter, a response (response) indicating that the second communication method has been selected In step S805, the process is performed on the reader / writer 202. The reader / writer 202 that has received the response in step S704 recognizes that the second communication method has been selected on the mobile phone 201 side by confirming the received response.

  In this way, when the reader / writer 202 and the mobile phone 201 (CLF 224) can communicate with each other in the second communication method, the reader / writer 202 sends a data read request to the mobile phone 201 (CLF 224) in step S705. Against.

  When the mobile phone 201 (CLF 224) receives a data read request from the reader / writer 202 in step S806, the mobile phone 201 (CLF 224) transfers the request to the third application 256. In this case, since communication is performed in the second communication method, the third command wrapped in the APDU command format is supplied from the reader / writer 202 to the UICC hardware 251 via the CLF 224 (FIG. 9). Further, it is supplied from the UICC hardware 251 to the application manager 252. The application manager 252 extracts the third command by processing the supplied APDU command format and supplies it to the third application 256.

  The flow of this packet is the communication path 352 described with reference to FIG. When the third application 256 receives a data read request (third command) from the reader / writer 202 via the communication path 352, in step S832, the third application 256 reads the data requested by the third command, (CLF224). When the CLF 224 receives the data supplied from the third application 256 in step S807, the CLF 224 transmits the data as a response corresponding to the request from the reader / writer 202 in step S808.

  In step S706, the reader / writer 202 that has acquired the data from the mobile phone 201 as a response reads the registered service data in step S707. For example, when the 3-1 service 257 (FIG. 14) is not registered as the service list information, it is found that the 3-1 service 257 should be registered. When the data is read, the card status is confirmed, and it is confirmed that there is no service to be registered, service registration is executed in step S708.

  In this case, since the service registration is performed using the APDU command format in the second communication method, the data for service registration is packetized in the APDU command format and transmitted to the mobile phone 201 in the second communication method. The process for doing so is executed in step S708. The mobile phone 201 (application manager 252) that has received the data for service registration from the reader / writer 202 in step S809 supplies the received data to the third application 256.

  When the third application 256 acquires the supplied data in the process in step S833, the third application 256 executes a service registration process in step S834. In step S834, the third application 256 executes service registration. As a result, if the service is successful or unsuccessful, the result of the registration process is output to the application manager 252 in step S835.

  In step S811, the application manager 252 that has received the result in the process in step S810 transmits the result of the registration process in the third application 256 to the reader / writer 202 as a response. In step S 709, the response from the mobile phone 201 is received by the reader / writer 202.

  When the received response indicates that the registration of the service is successful on the mobile phone 201 side, the reader / writer 202 continues the process of registering the service name (described later with reference to FIG. 29), If it indicates that the service has failed, for example, the service registration process is executed again by executing the process of step S708. Here, the description will be continued assuming that the process of service registration has been successful.

  Thus, when registering the 3-1 service 257 provided by the third application 256, the packet (APDU command format) used in the set communication method is associated with the command unique to the third application 256. The data is generated, and the registration process is executed when the data is exchanged. In other words, when registering the 3-1 service 257 provided by the third application 256, the registration process is executed by wrapping the third command handled by the third application 256 in the APDU command format.

  Refer to the flowchart of FIG. 29 for processing when information related to a registered service that is subsequently performed, for example, information related to a service name or service type, is registered after the service is registered by executing such processing. To explain.

  In this case, when the service is registered, since the communication is already performed in the second communication method, the reader / writer 202 and the mobile phone 201 are in a state in which communication can be performed in the second communication method. Therefore, the process for starting communication in the second communication method is omitted, and in step S751, the reader / writer 202 executes a process for registering the service name.

  For example, in this case, since the 3-1 service 257 is registered, a packet for registering the service name of the 3-1 service 257 in the registry 253 of the application manager 252 in the UICC is generated. In addition, the generated packet is a packet corresponding to the second communication method, that is, a packet including an APDU command in this case.

  In step S751, the reader / writer 202 executes a service name registration process, so that data transmitted from the reader / writer 202 to the mobile phone 201 is received by the mobile phone 201 (CLF 224) in step S851. The The received data is supplied to the application manager 252.

  Since the APDU command format is used, the APDU command received by the CLF 224 is supplied to the application manager 252 via the UICC hardware 251. When the application manager 252 receives data related to service name registration in the APDU command in step S881, the application manager 252 executes service name registration processing in step S882.

  The application manager 252 writes information such as the name and type of the newly registered service in the registry 253 according to the received APDU command. Information such as the name and type is also included in the APDU command supplied from the reader / writer 202.

  In step S882, when the registration of the service name and the like is completed, the application manager 252 outputs the processing result to the CLF 224 as the processing in step S883. Upon receiving the processing result from the application manager 252 in step S852, the CLF 224 transmits the result to the reader / writer 202 as a response in step S853. This response includes information indicating whether or not the service name registration process is successful.

  The reader / writer 202 that has received such a result in step S752 recognizes the completion of registration of the service name when the response is successful, and ends the process. On the other hand, when the received response indicates failure, for example, the service name registration process is performed again by executing the process of step S751 again.

  In this way, when the 3-1 service 257 provided by the third application 256 is registered, the third command that can be handled by the third application 256 is wrapped in the APDU command format that can be handled by the application manager 252. It is done using things.

  Further, information regarding the 3-1 service 257, for example, information such as the name of the 3-1 service 257 and the type of service to be provided is performed using an APDU command that can be handled by the application manager 252.

  As described above, the service is registered and the service name is registered, so that the application manager 252 can manage information related to the registered service in the registry 253. Information on registered services is managed in the registry 253, so that the information can be browsed by the viewer 241. When the viewer 241 can browse, the information can be provided to the user.

[Processing by Application Manager]
Some UICCs 222 include an application called an application manager. The UICC 222 illustrated in FIG. 30 includes an application manager 601. The application manager 601 is an application stored in an IC chip on a predetermined IC card, in this case, the UICC 222, and controls resources in the UICC 222 and downloads applications from external devices.

  When the UICC 222 includes the application manager 601, each wireless application, for example, the first application 254, the second application 255, or the third application 256 is installed via the application manager 601 at the time of installation. Each wireless application needs to transfer (select) the operating authority from the runtime environment of the application when operating. In addition, when each application is executed, there is no direct influence from the application manager 601.

  As shown in FIG. 30, for example, when the second application 255 or the third application 256 is installed, it is installed using an APDU command via the application manager 601. When the third application 256 is selected by the application manager 601 after installation, the third application 256 is in operation and operates without going through the application manager 601. In this case, the third packet is directly supplied to the third application 256.

  In the case of the UICC 222 having such an application manager 601, the processing when registering the 3-1 service 257 in the second communication method described with reference to the flowchart of FIG. 28 is the flowchart shown in FIG. It becomes processing based on.

  The processing in steps S1001 to S1009 executed on the reader / writer 202 side is the same as the processing in steps S701 to S709 in FIG. That is, the process on the reader / writer 202 side can perform service registration by the same process regardless of whether the UICC 222 includes the application manager 601 or not. This means that the service can be registered using the same infrastructure regardless of whether the UICC 222 includes the application manager 601 or not.

  The processes in steps S1111 to S1115 executed on the mobile phone 201 side are the same processes as steps S801 to S805 in FIG. In other words, the setting for performing communication using the second communication method is performed in the same manner regardless of whether or not the UICC 222 includes the application manager 601 regarding the processing performed on the reader / writer 202 side and the mobile phone 201 side. .

  As a result of the processing, when the communication with the second communication method is enabled, in step S1005, the reader / writer 202 issues a data read request to the mobile phone 201 (CLF 224). When the mobile phone 201 (CLF 224) receives a data read request from the reader / writer 202 in step S1116, the mobile phone 201 (CLF 224) transfers the request to the application manager 601.

  In step S1152, the application manager 601 outputs the requested data to the CLF 224. When receiving the data in step S1117, the CLF 224 transmits the data as a response corresponding to the request from the reader / writer 202 in step S1118. In step S1006, the reader / writer 202 that has acquired data from the mobile phone 201 (CLF 224) as a response reads out data of the service to be registered in step S1007.

  In this case, since the service registration is performed by using the APDU command in the second communication method, the data for service registration is packetized in the APDU command format and transmitted to the mobile phone 201 by the second communication method. Processing is performed in step S1008. The mobile phone 201 (CLF 224) that has received the data for service registration from the reader / writer 202 in step S1119 supplies the received data to the application manager 601.

  In step S1153, the application manager 601 further transfers the supplied data to the third application 256. When the third application 256 acquires the supplied data in the process in step S1181, the third application 256 executes a service registration process in step S1182. In step S1182, the third application 256 executes service registration. As a result, when the service is successful or unsuccessful, the result of the registration process is passed to the application manager 601 in step S1183.

  In step S1154, the application manager 601 receives the result from the third application 256, and in step S1155, the result of the registration process is passed to the CLF 224. The CLF 224 that has received the result in the process in step S1120 transmits the result of the registration process in the third application 256 to the reader / writer 202 as a response in step S1121. In step S1009, when the response from the mobile phone 201 is received by the reader / writer 202, the service registration process is terminated.

  In this way, the reader / writer 202 performs service registration for the UICC 222 including the application manager 601 by executing the same processing as that performed for the UICC 222 not including the application manager 601. Can do.

  When the service registration is performed in this way, the service name registration process is continued. This process is performed in the same manner as the process in the flowchart shown in FIG. Omitted. That is, the process for registering a service name with respect to the UICC 222 including the application manager 601 is performed in the same manner as the process for registering a service name with respect to the UICC 222 not including the application manager 601.

  In other words, since the registration of the service name is performed by the process of the application manager 252, there is no process in the application manager 601. Therefore, the process on the mobile phone 201 side is the same as in the case where the application manager 601 is not present. The service name is registered in the process.

[Registering services and service names using additional functions]
Next, registration of a service and a service name using an additional function will be described with reference to a flowchart of FIG. Here, it is determined that the third communication method can be used, but it is determined that the APDU command format in the third communication method cannot be used. A case where one service 257 is registered will be described as an example.

  When it is determined that the third communication method can be used, but when it is determined that the APDU command format in the third communication method cannot be used, it is determined that the packet unique to the third application 256 is transmitted / received. Is the time. Such a determination is made, for example, when the execution of the processing of the flowchart shown in FIG. 20 is executed and, in step S163, it is set to be realized by the additional function.

  Of the processes in the flowchart shown in FIG. 32, the processes in steps S1301 to S1307 executed on the reader / writer 202 side are performed in the same manner as steps S551 to S557 in the flowchart shown in FIG. Therefore, detailed description thereof is omitted here. 32, the processes in steps S1401 to S1409 executed on the mobile phone 201 side are performed in the same manner as steps S601 to S609 in the flowchart shown in FIG. The description is omitted.

  32, the processes of steps S1451 and S1452 executed on the third application 256 side are performed in the same manner as steps S631 and S632 of the flowchart shown in FIG. The description is omitted.

  In step S1453, when the third application 256 receives from the reader / writer 202 the third command related to service registration transmitted in the third packet, the third application 256 executes service registration based on the third command in step S1454. To do. When the third application 256 finishes registration of the service, the service name is generated and output to the application manager 252 in step S1455.

  That is, in this case, the third application 256 generates a service name (information on the service) by processing a command from the reader / writer 202 and supplies the service name to the application manager 252.

  Refer to FIG. 9 again. When only the packet of the communication protocol of the third application 256 can be transmitted / received, the unique packet is transmitted / received via the communication path 351. That is, the third packet from the reader / writer 202 is received by the CLF 224 and supplied from the CLF 224 to the third application 256 via the UICC hardware 251. Therefore, since the third application 256 can be accessed, the 3-1 service 257 provided by the third application 256 can be registered.

  However, since there is no communication protocol for accessing the application manager 252, the registry 253 managed by the application manager 252 cannot be directly accessed from the reader / writer 202. On the other hand, the third application 256 has a communication path 354 that accesses the registry 253.

  Therefore, the third application 256 issues an instruction to the application manager 252 so that the application manager 252 can update information in the registry 253. That is, in this case, information such as a service name and a service type is registered in the registry 253 by the processing of the third application 256.

  For this purpose, a service name is generated by the third application 256 in step S1455 (FIG. 32). Data for generating a service name is supplied from the reader / writer 202, and even if the supply itself is performed when the service registration is executed in step S1306, the data prepared by the third application in advance is provided. You may generate automatically from. Therefore, the reader / writer 202 transmits data for registering a service and data for registering a service name to the mobile phone 201 (third application 256) in a third packet.

  In addition, a command for the third application 256 to generate a service name may be prepared, and the command may be transmitted from the reader / writer 202. The third application may continue processing automatically at the timing of registering the service. The third application 256 side is configured to recognize such a command and execute the processing. In step S 1455, such a command is interpreted by the third application 256, a service name is generated, and is output to the application manager 252.

  In step S1481, the application manager 252 that has received a service name from the third application 256 and a command for registering the service name in the registry 253 via an API (Application Program Interface) receives the service name in step S1482. The received service name is registered in the registry 253 based on the received command. When the registration is completed, data indicating that the registration is completed is output to the third application 256 in step S1483.

  In step S1456, the third application 256 receives data indicating the end of registration from the application manager 252. In step S1457, the third application 256 transmits data indicating that service registration and service name registration have ended to the CLF 224. Output as a response. When the CLF 224 receives a response from the third application 256 in step S1408, the CLF 224 transfers the response to the reader / writer 202 in step S1409.

  In step S1307, the reader / writer 202 receives the response and interprets the response, thereby recognizing that the registration process has ended.

  As described above, the third application 256 executes a process for registering the service name. In order to enable such processing, it is conceivable to define the service as follows.

  As pattern 1, a command that can be interpreted by the third application 256 is prepared as described above. In the case of pattern 1, a command that indicates the start indicating the start of service registration and the end indicating the end is prepared, and the exchange of service registration data between the start and the end is considered as a unit of service. It is done.

  As pattern 2, the act of creating a series of service areas is automatically determined as one service unit. In this case, a service area generated by one command or one group obtained by combining commands is viewed as a service unit.

  In addition to the definition of the service, it is necessary to define how to pass the service name to the service, in other words, how to generate and register the service name executed in step S1455.

  As pattern 1, a command for instructing generation and registration of a service name is prepared so that the third application 256 can interpret the command. By transmitting a command from the reader / writer 202 side, it becomes possible to cause the third application 256 to execute service name registration.

  As pattern 2, it is conceivable to register a service name by preparing a new area. In pattern 2, a definition block for entering a service name is defined, its contents are interpreted, and the registry 253 of the application manager 252 is updated. In this case as well, writing to the block from the reader / writer 202 is required, and input from the reader / writer 202 is required. In other words, since the update is performed by the input from the reader / writer 202, the update timing and the like can be controlled on the reader / writer 202 side.

  As pattern 3, it is conceivable to register a service name by holding a correspondence table. In the pattern 3, the third application 256 holds a correspondence table between numbers and service names for identifying areas and services such as system codes and service codes, and when a service is registered, an identification corresponding to that service The service name is registered by reading the number and the service name to be read from the correspondence table. Further, when a new service that is not described in the held correspondence table is provided, the correspondence table itself is updated. The correspondence table can also be updated by executing processing such as sending a command from the reader / writer 202 side.

  Any one of these patterns is adopted, and service name generation and registration processing is executed. The third application 256 registers the generated service name in the registry 253 via the API.

[Processing related to service name display]
In this way, when the service and the service name are registered, when the viewer 241 presents the registered service information to the user, the information is presented on the screen as shown in FIG. 33 or FIG. Will be able to.

  As shown in FIG. 33, the viewer 241 recognizes the first application 254, the second application 255, and the third application 256 recognized by the application manager 252. Further, in the registry 253, the above-described processing is executed, so that the third application 256 has information about the services of the 3-1 service 257, the 3-2 service 258, and the 3-3 service 259. Since it is registered, the viewer 241 also recognizes those services.

  As a result of such recognition, the viewer 241 receives the “first service” that is the name of the service provided by the first application 254, the “second service” that is the name of the service provided by the second application 255, and the third A “third service” that is the name of a service provided by the application 256 is displayed on the display 401.

  Further, the third application 256 is a comprehensive service, and is configured to be able to provide the 3-1 service 257, the 3-2 service 258, and the 3-3 service 259, and these information also refers to the registry 253. This information is also displayed on the display 401.

  That is, as shown in FIG. 33, under the name “third service” corresponding to the third application 256, the name “3-1 service” corresponding to the 3-1 service 257, 3-2 The name “third service” corresponding to the service 258 and the name “third service” corresponding to the third service 259 are displayed in association with the name “third service”. The

  By displaying such a display, the user can recognize that the third service includes three services of the 3-1 service, the 3-2 service, and the 3-3 service. . Such a display is made possible by managing the service names corresponding to the 3-1 service 257, the 3-2 service 258, and the 3-3 service 259 in the registry 253.

  FIG. 34 shows another display example. In the display example shown in FIG. 34, first, “first service” that is the name of the service provided by the first application 254 and “second service” that is the name of the service provided by the second application 255 are displayed on the display 401. Has been. Furthermore, below that, the name “3-1 service” corresponding to the 3-1 service 257, the name “3-2 service” corresponding to the 3-2 service 258, and the 3-3 service The name “3-3 Service” corresponding to 259 is displayed.

  With this display, the user recognizes that there are five services: the first service, the second service, the 3-1 service, the 3-2 service, and the 3-3 service. Can do. In this case, the user recognizes that the third application 256 provides the three services, and has the 3-1 service, the 3-2 service, and the first service in the same way as the first service and the second service. 3-3 Services can be recognized. Such a display is made possible by managing the service names corresponding to the 3-1 service 257, the 3-2 service 258, and the 3-3 service 259 in the registry 253.

  Such a display difference is determined by how the service name is managed in the registry 253. Therefore, how to manage service names will be described. First, it is conceivable that a dummy AID is attached to a service and the service is managed with the dummy AID. Further, the dummy AID is written in the registry 253 so that information on the service is managed by the registry 253. AID is an abbreviation for Application IDentifier.

  When a plurality of applications are registered in the UICC 222, for example, if the “name” of a file assigned to each application is accidentally the same, the application may not operate normally, and file destruction may occur. In order to prevent such a situation, an application identifier (AID) is assigned to ensure the uniqueness of the application. Thus, the application is managed by AID. In order to ensure uniqueness, the AID is a unique value.

  AID is defined by ISO7816-5, and is composed of 16 bytes, 5 bytes are composed of RID, and the remaining 11 bytes are composed of PIX. The RID is a provider of the application, for example, a unique ID acquired by a predetermined company. Therefore, RID is basically one ID per company. RID is an abbreviation for Registered application provider Identifier, and PIX is an abbreviation for Proprietary application Identifier eXtension.

  PIX is an ID that can be uniquely assigned within a company to which an RID is assigned. Therefore, the third application 256 generates a dummy AID based on the following rules. The dummy AID is an AID assigned to an application that does not actually exist. The dummy AID is provided for the purpose of displaying an application registered in the UICC 222 from the viewer 241.

  Therefore, this dummy AID is not used when the user selects and activates the application. Further, the service in the third application 256 does not actually have an AID.

The dummy AID has the following configuration.
Dummy AID = (RID) + (value assigned to the third application 256 (part of PIX) + unique service number specified by the company (part of PIX))

  The dummy AID having such a configuration does not affect other applications. By writing the dummy AID into the registry 253, the dummy AID is configured within the framework of the third application 256 without any influence on the first application 254 other than the third application 256, for example. Can do. Therefore, when an application is called with a dummy AID specified, the third application may be called because it partially matches the AID of the third application that is the source of the dummy.

  The dummy AID configured as described above is registered in the registry 253 from the third application 256 via the API. Since the viewer 241 sees the dummy AID managed in the registry 253, the viewer 241 can recognize the application to which the dummy AID is assigned.

  In this case, since the service is assigned to the dummy AID, the viewer 241 recognizes the registered service as a result. By enabling such recognition, the screen provided by the processing of the viewer 241 can be a screen as shown in FIG. 33 or 34, for example.

  As shown in FIG. 33, the services realized by a predetermined application can be hierarchically displayed as shown in FIG. 33, depending on the configuration of the dummy AID itself and how the dummy AID is attached to the service. In this way, the service can be displayed in the same hierarchy as the service realized by a predetermined application.

[Effect]
In this way, even if the service provided by the third application 256 is registered alone in the UICC 222, for example, the presence of each service can be confirmed from the viewer 241 that is commonly used by different mobile phones 201. become. By being able to perform such confirmation, as described above, it is possible to present a screen for allowing the user to recognize the existence of each service.

  Further, for example, as shown in FIG. 34, the display can be a display that can be referred to by the user as a service in the same row as a service provided by another application. In addition, even a new service can be displayed as a service in the same row as a registered service. Alternatively, as shown in FIG. 33, a service provided by a predetermined application can be displayed in a hierarchical manner associated with the application.

  In addition, if it becomes possible to confirm the existence of a service, it becomes possible to add an opposite application when necessary. That is, it is possible to give a degree of freedom to the relationship between the service and the application.

  Service registration and service name registration can be performed using existing infrastructure as much as possible. Therefore, even if the system is migrated so that the service is managed by the UICC 222, the cost after the migration can be reduced. In addition, because the infrastructure can be utilized, system migration can be performed without significant changes, causing confusion associated with system migration for both users and developers. Can be prevented.

[About recording media]
The series of processes described above can be executed by hardware or can be executed by software. When a series of processing is executed by software, a program constituting the software is installed in the computer. Here, the computer includes, for example, a general-purpose personal computer capable of executing various functions by installing a computer incorporated in dedicated hardware and various programs.

  FIG. 35 is a block diagram illustrating a hardware configuration example of a computer that executes the above-described series of processing by a program. In a computer, a CPU (Central Processing Unit) 1001, a ROM (Read Only Memory) 1002, and a RAM (Random Access Memory) 1003 are connected to each other by a bus 1004. An input / output interface 1005 is further connected to the bus 1004. An input unit 1006, an output unit 1007, a storage unit 1008, a communication unit 1009, and a drive 1010 are connected to the input / output interface 1005.

  The input unit 1006 includes a keyboard, a mouse, a microphone, and the like. The output unit 1007 includes a display, a speaker, and the like. The storage unit 1008 includes a hard disk, a nonvolatile memory, and the like. The communication unit 1009 includes a network interface. The drive 1010 drives a removable medium 1011 such as a magnetic disk, an optical disk, a magneto-optical disk, or a semiconductor memory.

  In the computer configured as described above, the CPU 1001 loads the program stored in the storage unit 1008 into the RAM 1003 via the input / output interface 1005 and the bus 1004 and executes the program, for example. Is performed.

  The program executed by the computer (CPU 1001) can be provided by being recorded on the removable medium 1011 as a package medium, for example. The program can be provided via a wired or wireless transmission medium such as a local area network, the Internet, or digital satellite broadcasting.

  In the computer, the program can be installed in the storage unit 1008 via the input / output interface 1005 by attaching the removable medium 1011 to the drive 1010. Further, the program can be received by the communication unit 1009 via a wired or wireless transmission medium and installed in the storage unit 1008. In addition, the program can be installed in advance in the ROM 1002 or the storage unit 1008.

  The program executed by the computer may be a program that is processed in time series in the order described in this specification, or in parallel or at a necessary timing such as when a call is made. It may be a program for processing.

  Further, in this specification, the system represents the entire apparatus constituted by a plurality of apparatuses.

  The embodiment of the present invention is not limited to the above-described embodiment, and various modifications can be made without departing from the gist of the present invention.

  201 mobile phone, 202 reader / writer, 221 host, 222 UICC, 223 UART, 224 CLF, 251 UICC hardware, 252 application manager, 253 registry, 254 first application, 255 second application, 256 third application, 501 communication control , 502 communication method determination unit, 503 service registration unit, 504 update processing unit

Claims (9)

A communication unit that is a card that manages a predetermined application and a service provided by the application, and that performs contactless communication with a card including an application manager;
A first communication method for communication with the card for registering the service in the card and a second communication method for communication with the card for registering information on the service to be registered are registered in the card. Setting means to
First transmission means for creating and transmitting data for registering the service in the card by the first communication method set by the setting means;
An information processing apparatus comprising: a second transmission unit configured to create and transmit data for registering the service information in the card by the second communication method set by the setting unit. The setting means includes
Set the first communication method to a communication method for accessing the application,
The information processing apparatus according to claim 1, wherein the second communication method is set to a communication method for accessing the application manager. When the first communication method is set to a communication method for accessing the application manager by the setting unit, the first transmission unit includes a packet used in the set first communication method, The information processing apparatus according to claim 1, wherein data associated with an application-specific command is generated and transmitted. When the first communication method is set to a communication method for accessing the application manager by the setting means, the first transmission means is a packet used in the set first communication method, and The information processing apparatus according to claim 1, wherein data obtained by wrapping an application-specific command is generated and transmitted. The communication means can communicate by a plurality of communication methods,
The information processing apparatus according to claim 1, wherein the selection unit determines whether or not communication with the card can be performed for each communication method, and performs selection from communication methods determined to be able to perform communication. The communication means can communicate by a plurality of communication methods,
The selection means selects one communication method from the plurality of communication methods, and when communication with the card is not possible with the communication method, reselects another communication method, and again, Determine if you can communicate with the card,
The information processing apparatus according to claim 1, wherein when the communication becomes possible with the selected communication method, the communication method that enables the communication is selected. The communication means can communicate by a plurality of communication methods,
The selection means selects one communication method from the plurality of communication methods, and when communication with the card is not possible with the communication method, reselects another communication method, and again, Determine if you can communicate with the card,
The information according to claim 1, wherein when communication is possible with the selected communication method, information is exchanged with the card using the communication method, and a communication method is selected using a result of the information exchange. Processing equipment. In an information processing method of an information processing apparatus including a predetermined application and a communication unit that performs non-contact communication with a card that manages a service provided by the application,
A first communication method for communication with the card for registering the service in the card and a second communication method for communication with the card for registering information on the service to be registered are registered in the card. And
Create data for registering the service in the card with the set first communication method, control the communication means and transmit,
An information processing method comprising the steps of: creating data for registering the service information in the card by the set second communication method, and controlling and transmitting the communication means. An information processing apparatus including a predetermined application and a communication unit that performs contactless communication with a card that manages a service provided by the application,
A first communication method for communication with the card for registering the service in the card and a second communication method for communication with the card for registering information on the service to be registered are registered in the card. And
Create data for registering the service in the card with the set first communication method, control the communication means and transmit,
A computer-readable program for executing processing including a step of creating data for registering the service information in the card by the set second communication method and controlling and transmitting the communication means.

Images