JP7058631B2 - Information processing equipment and methods, and programs - Google Patents

Description

The present invention relates to an information processing device, a method, and a program, and in particular, an information processing device, a method, and a program suitable for use when updating data managed by a chip, a card, or the like corresponding to a plurality of communication protocols. Regarding.

Mobile phones have become widespread, and various services are provided by mobile phones. With reference 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 process for providing the service 13-1 to the user is performed by the application 14-1, and the process for providing the service 13-2 to the user is configured to be performed by the application 14-2.

An application is a set of executable modules that are written to software on a mobile phone, unlike services that are written to a chip. For mobile phones, if the product conforms to the MIDP 2.0 specifications shown in Non-Patent Document 1, Application Management Software (AMS) is used, and if the product conforms to the MIDP 2.0 specifications shown in Non-Patent Document 2, the product conforms to the MIDP 1.0 specifications. If so, JAM (Java (registered trademark) Application Manager) with the same function is installed, and it manages the applications installed in mobile phones. Management here means holding a series of state transitions such as application download, installation, and deletion.

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

Here, as shown in FIG. 1B, consider a case where the user changes from the mobile phone 11 to the mobile phone 31. For example, when a mobile phone 31 is purchased, a data transfer service from the mobile phone 11 to the mobile phone 31 is provided at the store where the mobile phone 31 is purchased. Service 13-1 and service 13-2 stored in the chip 12 of the mobile phone 11 (hereinafter, when it is not necessary to distinguish services 13-1 and 13-2 individually, they are simply described as service 13 and others. 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, but if there is no corresponding application 14, a message instructing the user to download the application 14 corresponding to the service 13 is sent. It is displayed on the display of the mobile phone 31. By downloading the application 14 as a process for the message, the user can use the service 13 even on the new mobile phone 31.

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, at present, the service 13 is 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 the UICC (Universal Integrated Circuit Card). It is conceivable 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 becomes available at 31.

In this case, the service 13 and the like stored in the UICC 51 will be transferred to the inserted mobile phone 31, but the information of the application management software 15 will not be 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 available.

Therefore, 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 is configured to be able to browse services and the like 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 has a viewer 71, so that the viewer 71 provides services managed by the UICC 51. 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 be provided with a function of displaying a message prompting the user to download the application. ..

The UICC 51 has, for example, a configuration as shown in FIG. On the UICC hardware 101, there is an application manager 102 in the UICC, on which the application 103, the application 104, and the application 105 are managed. The application 103 is, for example, an application for providing a service that realizes a credit card function. The application 104 is an application for providing a transport-type service used for, for example, paying a fee for getting on and off a transportation facility.

As an example, when JavaCardTM disclosed by Sun Microsystems (trademark) is used as the execution environment for the application manager 102 in the UICC, the installer controls the application installation / deletion function, and the management information by the registry specified by the Global Platform is used. , The integrated application management function is realized by using the authentication method.

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, service 106-1 is a service that realizes a credit function, service 106-2 is a service that provides transport-type services, and service 106-3 is a service that provides coupons.

When such an application is registered and the viewer 71 browses the application managed by the UICC 51, for example, the display as shown in FIG. 4 is performed. In order to recognize the application 103, the application 104, and the application 105, the viewer 71 has the names "service 103" which is the service name of the service provided by the application 103 and "service 104" which is the service name of the service provided by the application 104. To the user. Although there are a plurality of services provided by the application 105, the name "service 105", which is a general term for 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, and the application 105 provides the services. It is not possible to recognize even the services 106-1 to 106-3 to be performed and present the information to the user.

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

The information processing device on one aspect of the present technology corresponds to a communication control unit that controls communication by non-contact communication and a first communication method called Type A or Type B relating to the non-contact communication, and is a first service. A storage unit that stores a second application that supports a first application and a second communication method called Type F relating to the non-contact communication and provides a second service different from the first service. And the management unit having a function of installing or deleting the first application and the second application stored in the storage unit, information on the first service installed by the management unit, and the second. Based on the display control unit that controls the display of the service information on the display and the first data for registering the first service received by the communication control unit from another device, the first service is described. A service for registering the first service by processing the first application, or registering the second service by processing the second application based on the second data for registering the second service. The registration unit, the generation unit that generates the first information about the first service registered by the service registration unit, or the second information about the second service, and the generation unit generated by the generation unit. The management unit includes an update unit that updates the information stored in the storage unit with the information of 1 or the second information, and the management unit is an information processing device that is an execution environment for JavaCard (registered trademark).

An information processing device including a communication control unit that controls communication by non-contact communication, which is one aspect of the present technology, corresponds to a first communication method called Type A or Type B relating to the non-contact communication, and is a first service. A second application that supports a first application and a second communication method called Type F relating to the non-contact communication and provides a second service different from the first service is stored and stored. It manages to install or delete the first application and the second application, and controls to display the installed information of the first service and the information of the second service on the display . Based on the first data for registering the first service received from another device under the control of the communication control unit, the first service is registered by the processing of the first application, or the first service is registered. Based on the second data for registering the second service, the second service is registered by the processing of the second application, and the first information regarding the registered first service, or the first information. The second information about the service of 2 is generated, the generated first information or the information stored in the second information is updated, and the management is performed in the execution environment regarding JavaCard (registered trademark). It is an information processing method.

The program of one aspect of the present technology is applied to a computer that controls an information processing apparatus including a communication control unit that controls communication by non-contact communication, to a first communication method called Type A or Type B relating to the non-contact communication. A second application that corresponds and provides a first service and a second communication method called Type F relating to the non-contact communication and provides a second service different from the first service. The application is stored, the stored first application and the second application are installed or deleted, and the installed information of the first service and the information of the second service are displayed on the display. The first service is processed by the first application based on the first data for controlling the display and registering the first service received from another device under the control of the communication control unit. Based on the second data for registering the service or registering the second service, the second service is registered by the processing of the second application, and the registered first service is related to the first service. The management comprises a step of generating one piece of information, or a second piece of information about the second service, and updating the generated first piece of information or the information stored in the second piece of information, the management of which is a JavaCard. It is a computer-readable program that executes the processing performed in the execution environment related to (registered trademark).

In the information processing device, information processing method, and program of one aspect of the present technology, communication is controlled by non-contact communication, and it corresponds to the first communication method called Type A or Type B related to non-contact communication. A second application that supports a first application that provides a first service and a second communication method called Type F related to non-contact communication and that provides a second service different from the first service is stored. Management is performed to install or delete the stored first application and the second application, and control is performed to display the installed information of the first service and the information of the second service on the display. Further, based on the first data for registering the first service received from another device, the first service is registered by the processing of the first application, or the second service is registered. Based on the data of 2, the second service is registered by the processing of the second application, and the first information about the registered first service or the second information about the second service is generated and generated. The information stored in the first information or the second information is updated .

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

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

It is a figure for demonstrating the transition of the service in the conventional mobile phone. It is a figure for demonstrating the transition of a service when UICC is used. It is a figure for demonstrating the registration of a service in UICC. It is a figure which shows an example of the screen displayed by the processing 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 path. It is a figure for demonstrating a communication path. It is a figure for demonstrating a communication path. It is a figure for demonstrating the relationship between a communication method, a packet, and a command. It is a figure for demonstrating the hierarchy in each communication system. It is a figure which shows the display example of a service name. It is a figure for demonstrating service. It is a figure for demonstrating the 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 method. It is a flowchart for demonstrating the determination process of a communication method. It is a flowchart for demonstrating the determination process of a communication method. It is a flowchart for demonstrating the determination process of a communication method. It is a flowchart for demonstrating the determination process of a communication method. It is a flowchart for demonstrating the determination process of a communication method. It is a flowchart for demonstrating the determination process of a communication method. It is a flowchart for demonstrating the determination process of a communication method. It is a flowchart for demonstrating the determination process of a communication method. It is a figure for demonstrating the relationship between a communication method, a packet, and a command. It is a flowchart for demonstrating the registration of a service and a service name. It is a flowchart for demonstrating the registration of a service and a service name. It is a flowchart for demonstrating the registration of a service and a service name. It is a flowchart for demonstrating the registration of a service and a service name. It is a figure for demonstrating an application manager. It is a flowchart for demonstrating the registration of a service and a service name. It is a flowchart for demonstrating the registration of a service and a service name. It is a figure which shows the display example of a service name. It is a figure which shows the display example of a service name. It is a figure for demonstrating a recording medium.

Hereinafter, embodiments of the present invention will be described 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 in a non-contact manner. Although the description will be continued here as the mobile phone 201, the present invention can be applied to an IC card or the like that communicates with the reader / writer 202 and holds some data.

[About the configuration of mobile phone 201]
FIG. 6 is a diagram showing an internal configuration of the mobile phone 201. The mobile 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 transmitted and received by a UART (Universal Asynchronous Receiver Transmitter) 223. Further, the mobile phone 201 is also configured to include a CLF (Contactless Frontend) 224 that controls non-contact communication between the mobile phone 201 and the reader / writer 202.

Although the parts related to the present invention are illustrated and described here, the mobile phone 201 includes a part that functions as a telephone by a communication unit (not shown) and a part that realizes a function of connecting to a network. It is said that.

The UICC 222 includes UICC hardware 251, an application manager 252, and a registry 253. Further, it is assumed that the UICC 222 stores and manages the first application 254, the second application 255, and the third application 256 here. The first application 254 is, for example, an application for providing a service that realizes a credit card function in a mobile phone 201. Further, for example, the second application 255 is an application for providing a transport-type service used when paying a fee for getting on and off transportation by the mobile phone 201.

Further, 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 that realizes a credit function, a transport service, and a service that provides a coupon. Although not shown in FIG. 6, as will be described later with reference to FIG. 14, additional services may be registered in UICC222, and UICC222 also has a function of storing and managing the registered services. .. 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 in the factory default of the ROM or may be provided as a separate chip. obtain.

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

Further, the application manager 252 interprets the command supplied via the CLF 224, and based on the interpretation, executes a process of supplying data to the application or supplying data from the application to the CLF 224. Registry 253 manages information about services such as service names and service types provided by applications.

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

[Data flow during registration and update]
FIG. 7 is a diagram for explaining a 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 that accesses 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 on 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 CLF224 by the protocol corresponding to the first application 254, and the unique command acquired by the communication is passed from CLF224 to the UICC hardware 251. Further, what is transmitted to the first application 254 on the communication path 302 is a general-purpose command format corresponding to the communication protocol. Communication is performed between the reader / writer 202 and CLF224 by the protocol corresponding to the first application 254, and a command conforming to the general-purpose command format acquired by communication is passed from CLF224 to UICC hardware 251. That is, depending on the flowing command format, there is 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 302.

As will be described later, as the communication protocol, there are the Type A standard, the Type B standard, and the so-called Type F standard standardized in 18092, which correspond to 3 and 4 standardized in ISO 14443. As a general-purpose command format that uses the communication protocol, there is a command format called Application Protocol Data Unit (APDU) defined in ISO7816-4. A command conforming to the APDU command format is hereinafter referred to as an APDU command.

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

In this way, 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 set as the communication path 304.

Next, with reference to FIG. 8, the flow of data when accessing the second application 255 will be described. When accessing the second application 255, there is a communication path 321 that accesses 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. What is transmitted to the second application 255 on this communication path 321 is a command format corresponding to a general-purpose communication protocol.

Further, as in the first application 254, there is also a communication path 322 via a wired connection. The communication path 322 is a communication path for accessing the second application 255 from the host 221 via the wired UART223 and further via the UICC hardware 251 and the application manager 252 in the UICC222.

In this way, there are two communication paths for accessing the second application 255. Further, 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, with reference to FIG. 9, the flow of data when accessing the third application 256 will be described. When accessing the third application 256, there is a communication path 351 that accesses 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 that accesses 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 CLF224 by the protocol corresponding to the third application 256, and the command unique to the third application 256 acquired by the communication is passed from the CLF 224 to the UICC hardware 251.

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

That is, depending on the flowing command format, 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 communication path 352.

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

In this way, 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 set as the 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 given and described. The first application 254 supports a communication method called Type A or the like. Hereinafter, the communication method supported by the first application 254 will be described as the first communication method as appropriate, and a specific example of the first communication method will be described as Type A.

The first communication method conforms to ISO 14443-2 to ISO 14443-2 to 3 among the communication methods called Type A as the communication protocol, and also conforms to the one using the original packet as the transmission packet and 14443-4. There are two types that correspond to general-purpose packets.

The original packet is used for the purpose of transmitting and receiving a command unique to the first application 254. Therefore, when this original 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 its own standard, it is not processed by the application manager 252 and is supplied to the first application 254.

Depending on the method of realizing the first application 254, it may or may not go through the application manager 252. For example, when the first application 254 is realized in the UICC hardware 251 it is possible to move away from the control of the application manager 252 and operate in the hardware without going through the application manager 252. As another example, if the first application 254 is later deployed as a module in memory, it is placed under the control of the application manager 252, in which case it goes through the application manager 252. When accessing via the application manager, access is performed using a general-purpose command as described above.

Here, in the example shown in FIG. 7, that is, as described above, when the original packet is transmitted from the reader / writer 202, the command extracted by CLF 224 is sent to the first application 254 via the UICC hardware 251. It is supplied and the route continues to be described as the communication path 301.

In the following description, the original command is described as the first command in order to indicate that the original command is a command transmitted / received by the original packet (described as the first packet) of the first application 254. MIFARE ™ is an example of a first application that uses a unique command.

The application manager 252 handles the APDU command that is extracted after being processed by CLF224. 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 a process that the supplied command is a command to the first application 254, so that 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 supports a communication method called Type B or the like. Hereinafter, the communication method supported by the second application 255 will be described as the second communication method as appropriate, and a specific example of the second communication method will be described as Type B. This second communication method complies with ISO 14443-2 to 4 as a corresponding protocol.

In the second communication method (Type B), there is a general-purpose packet as a transmittable packet. As described above, the general-purpose packet is intended for sending and receiving a general-purpose command format, and is used for the purpose of sending and receiving APDU commands.

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 the packet 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 the processing that the command is for the second application 255, so that the command is supplied to the second application 255. Will be done.

As in the case of the first application 254, the second application 255 may or may not go through the application manager 252 depending on the method of realizing the second application 255. Here, as shown in FIG. 8, the description will be continued with an example via the application manager 252.

The third application 256 supports a communication method called Type F or the like. Hereinafter, the communication method supported by the third application 256 will be described as the third communication method as appropriate, and a specific example of the third communication method will be described as Type F. 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 packet in which a general-purpose packet is further mounted 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 CLF224 is supplied from CLF224 to the third application 256. This FeliCa packet is used for sending and receiving FeliCa commands.

As in the case of the first application 254, the third application 256 may or may not go through the application manager 252 depending on the method of realizing the third application 256. Here, as shown in FIG. 9, the description will be continued with reference to an example via the application manager 252 (communication example in 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 by a packet unique to the third application 256 (hereinafter referred to as a third packet).

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

When this general-purpose packet is transmitted from the reader / writer 202, the CLF224 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 on the communication path 352 (FIG. 9). In this case, the application manager 252 executes a process that the supplied APDU command is a command to the third application 256, so that the APDU command is supplied to the third application 256.

In this way, when the mobile phone 201 and the reader / writer 202 send and receive packets in a non-contact manner, when the packets are sent and received in packets corresponding to the service-specific commands such as the first packet and the third packet, and when the general-purpose APDU is sent and received. There are times when transmission and reception are performed in a command format that conforms to ISO7816-4, such as commands.

In addition, there is a wired communication channel. 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. The packets that can be sent and received include a packet unique to a wire and a packet of the TPDU (Transport Protocol Data Unit) (ISO 7816-3) standard.

When it is desired to perform processing on the third application 256, the original wired packet is used for sending and receiving a third command (FeliCa command). TPDU standard packets are used to send and receive general-purpose commands, in this case APDU commands.

With reference to FIG. 11, a first communication method (Type A), a second communication method (Type B), a third communication method (Type F), and a hierarchical structure in a wired manner 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 / collision prevention layer. Further, the first communication method supports a unique packet and a general-purpose packet of the ISO 14443-4 standard as a packet layer. The command layer of the first communication method corresponds to the original command format as the command layer corresponding to the original packet of the packet layer, and ISO 7816 as the command layer corresponding to the general-purpose packet of the ISO 14443-4 standard of the packet layer. It supports the APDU command format that conforms to -4.

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 supports general-purpose packets of the ISO 14443-4 standard as a packet layer. The Type B command layer corresponds to the ISO 7816-4 compliant APDU command format as a command layer corresponding to the general-purpose 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 / collision prevention layer. The third communication method supports ISO 14443-4 standard packets and FeliCa packets as the packet layer. The Type F command layer corresponds to the ISO 7816-4 compliant APDU command format as the command layer corresponding to the ISO 14443-4 standard packet of the packet layer, and corresponds to the FeliCa packet of the packet layer. As, it corresponds to the FeliCa command format.

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

In this way, 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 exchanging data. You need to judge.

Now, refer to FIG. 6 again. As shown in FIG. 6, when the UICC 222 manages the first application 254, the second application 255, and the third application 256, when the processing by the viewer 241 is executed, for example, as shown in FIG. Screen is provided to the user. The screen is, for example, a screen displayed on the display 401 of the mobile phone 201.

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 is a "first service" which is the name of the service provided by the first application 254, a "second service" which is the name of the service provided by the second application 255, and a service provided by the third application 256. The name "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 shown 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 registers on the application manager 252. Only the 1st application 254, the 2nd application 255, and the 3rd application 256 are recognized, and the 3-1 service 257, the 3-2 service 258, and the 3-3 service 259 are also recognized. Information cannot be presented to the user.

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

As shown in FIG. 14, a state in which the 3-1 service 257 is not registered in UICC222 (in order to show that it is not registered, it is shown by a dotted line in FIG. 14, and an application or the like is not shown). At this time, when registering the 3-1 service 257, data 431 for registering the service is transmitted from the outside of UICC222. The data for registering the service shall be the service registration data. This service registration data 431 is for registering the 3-1 service 257. Service registration using such service registration data 431 can be performed using the infrastructure that is still used at present. Explaining with reference 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, it is also possible to pass data from the host 221 to the UICC 222 via the UART.

However, even if the 3-1 service 257 is registered in the service registration data 431, the information of 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, it is necessary to perform a process for registering the service type and the name.

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

Suppose, 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, and sixth and the same as the third application. It is also conceivable 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. It may disappear.

In order to make it possible to browse individual services on 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 transmitted to each service name. It is conceivable to register. Here, it has been described that the third application 256 includes a plurality of services, but the same can be said even when 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 is accessible by a plurality of communication paths. Since the third application 256 has communication paths 351 to 354 (FIG. 9), for example, the third application 257 can be registered in the communication path 351 and the information in the registry 253 can be updated in the communication path 352. can.

In order to make such a thing possible, when the reader / writer 202 executes the registration / update process for the mobile phone 201, which communication path is used for registration and which communication path is used for updating. It is necessary to determine whether to perform the above, and based on that determination, generate an appropriate command, for example, a command with a packet of a protocol suitable for the selected channel.

[About the 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 communicates non-contact between a predetermined application (for example, a third application 256) and a UICC 222 including an application manager 252 that manages a service provided by the application (for example, the 3-1 service 257). To control.

The communication method determination unit 502 performs a process of determining a communication method when registering a predetermined service to UICC222 and a communication method when updating the registry 253, respectively.

The service registration unit 503 executes the generation of a command for registering a predetermined service in the UICC 222 in the communication method determined by the communication method determination unit 502. The update processing unit 504 executes the generation of a command for updating the information managed in the registry 253 of the UICC 222 in the communication method determined by the communication method determination 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 described later with reference to FIGS. 17 to 24.

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

First, a process for determining a communication method for registering a service for UICC222 executed in step S1 and a communication method for updating the registry 253 will be described. Eight examples of processing related to the determination of the communication method will be described.

[About the first determination process of the communication method]
As the first determination process of the communication method, a method of trying all communication methods and selecting a communication method capable of performing good communication will be described with reference to the flowchart of FIG. In step S11, it is determined whether or not the first communication method can be used. For example, by transmitting a packet in the first communication method and determining whether or not there is a response, it is determined whether or not the first communication method can be used.

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, an APDU command is generated, and it is determined whether or not there is a response to the APDU command, thereby determining whether or not the APDU command format is available.

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

That is, by executing the processes of steps S11 and S12, it is determined whether or not the CLF 224 can communicate by the first communication method, and if it is possible to communicate by the first communication method, further. It will be determined whether the APDU command format is available. Such a judgment result is appropriately retained.

In step S13, it is determined whether or not 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. Further, even if it is determined in step S14 that the APDU command format is not available, the process proceeds to step S15. Further, even 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 processes of step S13 and step S14, it is determined whether or not the mobile phone 201 can communicate by the second communication method, and if communication is possible by the second communication method, it is determined. Furthermore, it will be determined whether or not the APDU command format is available. Such a judgment 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. Further, even if it is determined in step S16 that the APDU command format is not available, the process proceeds to step S17. Further, even if it is determined in step S15 that the third communication method cannot be used, the process proceeds to step S17.

That is, by executing the processes of steps S15 and S16, it is determined whether or not the CLF 224 can communicate by the third communication method, and if it is possible to communicate by the third communication method, further. It will be determined whether the APDU command format is available. Such a judgment result is appropriately retained.

In step S17, all the determination results are retained. If it is available, it will be flagged, and if it is not available, a table managed under the condition that it will not be flagged will be used, and the judgment result at each step will be retained. You can do it.

In step S18, the optimum process is selected from the state. For this selection, the communication method that is considered to be available is selected. In some cases, a communication method for which the APDU command format is determined to be available is selected, or a communication method using a unique packet is selected. The order to be selected is set, and the communication method determined to be available is selected according to the order. Selection is made based on such preset selection conditions. Further, the selection is made by 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 by the first communication method. As a result, it is determined in step S20 whether or not the processing (communication) is successful. If the process is not performed normally for some reason, the communication with that communication method is stopped and a different communication method is selected.

That is, if it is determined in step S20 that the process in the selected communication method was not 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 processing was successful in the selected communication method, the processing of the flowchart shown in FIG. 17 related to the communication method determination processing is terminated. As a subsequent process, the service is registered and the registry 253 is updated by the selected communication method. Such processing will be described later.

The order of processing shown in FIG. 17 is an example and does not indicate a limitation. That is, since all the communication methods of the first communication method, the second communication method, and the third communication method are tried and the results are retained, there is no difference depending on which communication method is used, and any communication method may be used. ..

In this way, when the reader / writer 202 is configured to be able to communicate with the CLF 224 by a plurality of communication methods, it is determined for each communication method whether or not the reader / writer 202 can communicate with the CLF 224, and the communication can be performed. From the determined communication methods, the communication method judged 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 the communication with the selected communication method fails, recovery becomes easy.

[About the second determination process of the communication method]
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, and it is determined that the communication method can be used. Occasionally, a case where the communication method is determined by selecting the communication method will be described with reference to the flowchart of FIG.

The decision processing described with reference to the flowcharts of FIGS. 18 to 24 has the same basic process flow. First, one of a plurality of communication methods is selected, and the communication method is the UICC 222. Whether or not communication is possible is determined. Then, when it is determined that communication is not possible, another communication method is selected again, and communication with UICC222 is tried again. Then, when communication becomes possible with the selected communication method, the process of selecting the communication method at which the communication becomes possible is performed.

In step S51, it is determined whether or not 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 used, and the communication method determination process is terminated. That is, in this case, since communication is possible by the first communication method and the APDU command format can be used in the first communication method, the service is registered and the registry 253 is updated (of the registered service) in the first communication method. It is set when the name is added). In the subsequent processing, the service is registered and the service name is added by 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 or not 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, the registration and update processing is realized in the first communication method and the second communication method. Then it is set. Specifically, it is set that the service is registered by the first communication method and the service name is registered by the second communication method. Alternatively, it is set that the service and the service name are registered only by the second communication method.

In this case, since the second communication method is a method of communicating 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 won't get it.

In FIG. 18, the description "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 can be used. The same applies to other drawings, and in the case 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 or not 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, 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. Therefore, in step S58, the first communication method and the third communication are performed. It is set to realize registration and update processing by the method. In this case, one of the APDU commands in the first communication method, the third communication method, and the third communication method is used to register the service, and the APDU command in the third communication method is used to name the service. It is 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 the registration and update processing is 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 or not 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, it is determined that the third communication method and the APDU command format can be used in the third communication method. Therefore, in step S64, the registration and update processing is realized in the third communication method. Then it is set. Specifically, it is set that the service is registered by the APDU command in the third communication method or the third communication method, and the service name is registered by 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 by all the communication methods of the first communication method, the second communication method, and the third communication method, in other words, communication is performed with the CLF 224 by the communication method supported by the reader / writer 202. Since it is determined that communication is not possible, 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 determined that communication is possible by the third communication method, but the APDU command format cannot be used. Similarly, when 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 with the first communication method, but the APDU command format cannot be used, and communication is not possible with the second communication method and the third communication method.

Similarly, when 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 by the first communication method and the third communication method, but it is determined that communication using the APDU command format cannot be performed by either method.

A common situation when the process proceeds to these steps S59 is that the APDU command format cannot be used. If the APDU command format is not available, registry 253 cannot be updated. The details will be described later, but the registry 253 is updated by using the APDU command. Therefore, if the APDU command cannot be used, the registry 253 cannot be updated, which is realized by an additional function.

Realizing with an additional function means that the registry 253 is updated by providing some function on the UICC222 or the application side installed in the UICC. In other words, when it is set to be realized by the first communication method as in step S53, when it is not realized by the additional function, the service registration and the registry are performed with the current function on the UICC222 side. It means that 253 updates can be performed.

When the communication method is determined in this way, the registration of the service corresponding to steps S2 and S3 (FIG. 16) and the update of the registry 253 are executed as described later based on the determined communication method. ..

[About the third determination process of the communication method]
As the third 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 third communication method, and the second communication method, and it is determined that the communication method can be used. Occasionally, a case where the communication method is determined by selecting the communication method will be described with reference to the flowchart of FIG. Since the same processing as that in the flowchart of FIG. 18 is included, the description of the same processing will be omitted as appropriate.

In step S101, it is determined whether or not 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 used, and the communication method determination process is terminated. That is, in this case, since communication is possible by the first communication method and the APDU command format can be used in the first communication method, it is set that the service is registered and updated 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 or not 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, 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. Therefore, in step S106, the first communication method and the third communication It is set to realize registration and update processing by the method.

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 or not 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, the registration and update processing is realized in 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 or not 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 neither the first communication method nor the third communication method can use the APDU command format. Since it is determined, in step S110, it is set that the registration is performed by the first communication method or the third communication method, and the update process is realized by 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 or not 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, it is determined that the third communication method and the APDU command format can be used in the third communication method. Therefore, in step S114, the registration and update processing is realized in the third communication method. 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 or not 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, in step S116, it is set that the registration and update processing is 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 or not 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, it is determined that the third communication method and the second communication method can be used. Therefore, in step S118, the registration is performed in the third communication method and the update process is performed in the second communication method. Is set when the is realized.

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 by all the communication methods of the first communication method, the second communication method, and the third communication method, in other words, communication is performed with the CLF 224 by the communication method supported by the reader / writer 202. Since it is determined that communication is not possible, 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 the APDU command format cannot be used.

In such a case, by providing some function in UICC222, the registry 253 is updated and set (it is set when updating using the additional function of UICC222).

[About the fourth determination process of the communication method]
As the fourth determination process of the communication method, it is determined whether or not 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. Occasionally, 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 or not 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, in step S152, it is set that the registration and update processing is 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 or not 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 or not 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, since communication is possible using the first communication method and the APDU command format can be used in the first communication method, it is set in step S155 that the service is registered and updated in the first communication method. Will be 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 or not 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, 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. Therefore, in step S158, the first communication method and the third communication It is set to realize registration and update processing by the method. In this case, it is set that the service is registered by the first communication method or the third communication method, and is set when the service name is registered by 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 or not 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, it is determined that the third communication method and the APDU command format can be used in the third communication method. Therefore, in step S162, the registration and update processing is realized in 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 by all the communication methods of the first communication method, the second communication method, and the third communication method, in other words, communication is performed with the CLF 224 by the communication method supported by the reader / writer 202. Since it is determined that communication is not possible, it is determined that communication is not possible 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 step S161 that the APDU command format cannot be used, the process proceeds to step S163. Will be. In such a case, it means that it is determined that the APDU command format cannot be used. Therefore, when the registry 253 is updated by providing some function to the UICC222, it is set in step S163 (it is set when the update is performed using the additional function of the UICC222).

[About the fifth determination process of the communication method]
As the fifth determination process of the communication method, it is determined whether or not 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. Occasionally, 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 or not 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 the registration and update processing is 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 or not 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, since communication is possible using the third communication method and the APDU command format can be used in the third communication method, it is set in step S205 that the service is registered and updated in the third communication method. Will be 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 or not 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, it is determined that the APDU command format can be used in the third communication method, the first communication method, and the first communication method. Therefore, in step S208, the third communication method or the first communication It is set that the service is registered 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 or not 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 is determined that the APDU command format can be used in the first communication method and the first communication method, in step S211, the registration and update processing is 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 by all the communication methods of the first communication method, the second communication method, and the third communication method, in other words, communication is performed with the CLF 224 by the communication method supported by the reader / writer 202. Since it is determined that communication is not possible, it is determined that communication is not possible in step S213.

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. Will be. In such a case, it means that it is determined that the APDU command format cannot be used. Therefore, when the registry 253 is updated by providing some function to the UICC222, it is set in step S212 (it is set when the update is performed using the additional function of the UICC222).

[About the sixth determination process of the communication method]
As the sixth determination process of the communication method, it is determined whether or not 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. Occasionally, 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 or not 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 or not 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, since the third communication method can be used and the APDU command format can be used in the third communication method, it is set in step S253 when the service is registered and updated in the third communication method. To.

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 or not 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, it is determined that the APDU command format can be used in the third communication method, the first communication method, and the first communication method. Therefore, in step S256, the third communication method and the first communication are performed. It is set to realize registration and update processing by the method.

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 or not 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, the registration and update processing is 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 or not 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 neither the third communication method nor the first communication method can use the APDU command format. Since it is determined, in step S260, it is set that registration is performed by the third communication method or the first communication method, and the update process is realized by 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 or not 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, it is determined that the first communication method and the APDU command format can be used in the first communication method. Therefore, in step S264, the registration and update processing is realized in 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 or not 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, in step S266, it is set that the registration and update processing is 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 or not 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, it is determined that the first communication method and the second communication method can be used. Therefore, in step S268, the registration is performed in the first communication method and the update process is performed in the second communication method. Is set when the is realized.

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 by all the communication methods of the first communication method, the second communication method, and the third communication method, in other words, communication is performed with the CLF 224 by the communication method supported by the reader / writer 202. Since it is determined that communication is not possible, it is determined that communication is not possible in step S269.

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 the APDU command format cannot be used.

In such a case, it is set to realize the update of the registry 253 by providing some function to the UICC222 (it is set to perform the update using the additional function of the UICC222).

[About the 7th determination process of the communication method]
As the seventh determination process of the communication method, it is determined whether or not 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. Occasionally, 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 or not 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, since communication is possible by the third communication method and the APDU command format can be used in the third communication method, when registration and update are performed in the third communication method, it is 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 or not 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, the registration and update processing is 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 S304 that the second communication method cannot be used, the process proceeds to step S306. In step S306, it is determined whether or not 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, it is determined that the APDU command format can be used in the third communication method, the first communication method, and the first communication method. Therefore, in step S308, the third communication method or the first communication It is set when the service is registered by the method and the service name is registered by 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 or not 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 the registration and update processing is 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 or not 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 or not 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, it is determined that the first communication method and the APDU command format can be used in the first communication method. Therefore, in step S314, the registration and update processing is realized in 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 by all the communication methods of the third communication method, the second communication method, and the first communication method, in other words, communication is performed with the CLF 224 by the communication method supported by the reader / writer 202. Since it is determined that communication is not possible, it is determined that communication is not possible in step S315.

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. Will be. In such a case, it means that it is determined that the APDU command format cannot be used. Therefore, when the registry 253 is updated by providing some function to the UICC222, it is set in step S309 (it is set when the update is performed using the additional function of the UICC222).

[About the eighth determination process of the communication method]
As the eighth determination process of the communication method, refer to the flowchart of FIG. 24 for the case where 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. I will explain.

In step S351, it is determined whether or not 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, information exchange of communication methods is performed.

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

For example, the reader / writer 202 issues a command instructing the mobile phone 201 to notify the communication method supported by the mobile phone 201 to the mobile phone 201 by the third communication method, and the mobile phone 201 receives a command. By notifying the communication method supported by the user in response to the received command, information on the communication method is exchanged.

Alternatively, in the third communication method, the reader / writer 202 notifies the mobile phone 201 of the communication method supported by the reader / writer 202 itself, and the mobile phone 201 receiving the notification is among 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.

When the information exchange of the communication method is performed 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. The processing content is, for example, the content of executing the registration and update processing by the third communication method.

On the other hand, if it is determined in step S351 that the communication of the third communication method is not possible, the process proceeds to step S354. In step S354, it is determined whether or not 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 process in step S352 has been described above, but in this case, the second communication method is used and the information exchange of the communication method is performed, which is different from the above-mentioned case. Then, 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 the communication of the second communication method is not possible, the process proceeds to step S355. In step S355, it is determined whether or not 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 process in step S352 has been described above, but in this case, the first communication method is used and the information exchange of the communication method is performed, which is different from the above-mentioned case. Then, 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 the communication of 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 cannot be used, it is determined in step S356 that communication with the mobile phone 201 is impossible. And the process is finished.

In this way, when the reader / writer 202 is configured to be able to communicate with a plurality of communication methods, one of the plurality of communication methods is selected first, and communication with the UICC 222 is possible with that communication method. It is judged whether or not there is. Then, when it is determined that communication is possible, information exchange regarding the communication method is performed with UICC222 in the communication method, and the communication method is selected using the result of the information exchange.

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

Here, as the determination process of the communication method, the first determination process to the eighth determination process have been described as an example, but which of these determination processes is used for the process is determined. , It may be determined by the design stage of the reader / writer 202, the place where it is installed, and the like.

Further, for example, when the user can set the communication method, the decision process may be selected from the first decision process to the eighth decision process according to the communication method set by the user. For example, in the second determination process to the eighth determination process, first, whether or not any one of the first communication method, the second communication method, and the third communication method can be used. Is judged. Therefore, the 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 do so. Further, in this case, in the eighth determination process shown in the flowchart of FIG. 24, the determination process for determining whether or not the first communication method can be used may be executed first. ..

[Processing related to registration and renewal]
By executing the above-mentioned process, the communication method for registering the service and the communication method for updating the registry 253 (service name registration process) are determined. Here, a combination of communication methods that may be set as a result of the above processing is listed.

First combination (for example, set in step S314 of FIG. 23)
Both registration and update are performed using the first communication method (APDU command format can be used with the first communication method).
Second combination (for example, set in step S311 of FIG. 23)
A third combination of registration and update, both performed by the second communication method (for example, set in step S303 of FIG. 23).
Both registration and update are performed using the third communication method (APDU command format can be used with the third communication method).

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

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

Ninth combination (for example, set in step S309 of FIG. 23)
Realized by additional functions (add functions to UICC222 side to register and update)

In this way, nine combinations may be set. Further, in the above-mentioned communication method determination process, although the wired state is not described, there is also a wired line, for example, a communication path 353 shown in FIG. 9, and communication from the host 221 via the wired UART223.

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. Further, here, a case where the 3-1 service 257 is additionally registered in the third application 256 (a case as described with reference to FIG. 14) will be described as an example.

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

Since the APDU command format can be transmitted and received in the combination of the numbers 1, the APDU command format is used for the registration of the service and the registration of the service name. At this time, the service is registered by the 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 the third application 256's original command. Data associated with the command is generated and sent / received. Specifically, at this time, the service is registered by wrapping the third command in the APDU command format. In addition, the APDU command is used to register the service name (update the registry 253).

The communication method used in combination with the number 2 is the case of the third communication method. The combination of No. 2 corresponds to the third combination described above. In the combination of the 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 the registration of the service and the registration of the service name. At this time, the third command is used for registering the service. Further, the APDU command is used for registering the service name, and the APDU command format in the third communication method is used for the packet.

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

The communication method used in the combination of the numbers 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 No. 3 corresponds to the above-mentioned fifth to eighth combinations. Since the APDU command format and the third packet can be transmitted and received in the combination of the number 3, the APDU command format and the third packet are used for the registration of the service and the registration of the service name.

At this time, if the third communication method corresponds to the APDU command format, the third command is used for registering the service and the APDU command is used for registering the service name, as in the combination of the number 2. If the third communication method does not support the APDU command format, the service is registered by wrapping the third command in the APDU command format, and the service name is registered by using 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 the combination of numbers 4 to 6 is wired. The combination of number 4 is when the APDU command format can be sent and received, and as with the combination of number 1, the service is registered by wrapping the third command in the APDU command format, and the service name is registered. , APDU command is used.

The combination of the numbers 5 is when packets in the APDU command format and the wired protocol can be sent and received, the third command is used for registering the service, and the APDU command is used for registering the service name. Alternatively, as with the combination of numbers 4, the service can be registered by wrapping the third command in the APDU command format, and the service name can be registered by using the APDU command.

The communication method used in combination with the number 6 is wired, and is when packets in the wired protocol can be transmitted and received. The communication method used in combination with the number 7 is the third communication method, when the third packet can be transmitted and received. This combination of No. 6 and No. 7 corresponds to the above-mentioned ninth combination. This is when the communication method is supported only by the original packet.

If only the communication method using the original packet can be used, the service registration and service name cannot be registered only by processing the packet etc. on the reader / writer 202 side, so add a function to the UICC222 side and register. The update will be done. For example, new service registration data, new commands (or blocks) are registered and updated via the application (in this case, via the third application 256).

Next, a flowchart is provided for the processes 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 processes executed on the mobile phone 201 side. It will be explained with reference to.

[Registration of services and service names using the 3rd communication method and the 2nd communication method]
First, referring to the flowcharts of FIGS. 26 and 27, it was determined that the third communication method could be used, but it was determined that the APDU command format in the third communication method could not be used, and the third communication method was used. 2 The case where it is determined that the communication method can be used will be described.

Such a setting is made, for example, when the process of the flowchart shown in FIG. 23 is executed and, as a result, it is set in step S305 to be realized by the third communication method / the second communication method, as described above. It corresponds to the fifth combination and the sixth combination. Further, in FIG. 25, it corresponds to the combination of No. 3.

The flowchart of FIG. 26 is a process for registering a service. first. In step S601, the mobile phone 201 activates the card. The card is UICC222. As for the activation of the card, in step S1 (FIG. 16), when the process of determining the communication method is performed on the reader / writer 202 side, the reader / writer 202 and the mobile phone 201 (CLF224) 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 (CLF224) to respond in the third communication method. The mobile phone 201 (CLF224) that received such a request in step S602 returns a response in step S603. In this case, it is a response indicating that the communication is performed by the third communication method. The reader / writer 202 that received such a response from the mobile phone 201 (CLF224) in step S552 makes a request for reading data to the mobile phone 201 (CLF224) in step S553.

When the mobile phone 201 (CLF224) receives the request for reading the data from the reader / writer 202 in step S604, the mobile phone 201 (CLF224) transfers the request to the third application 256. In this case, since the 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 on the communication path 351 described with reference to FIG. 9.

In step S631, when a data read request from the reader / writer 202 is received in such a communication path 351 (FIG. 9), the data requested in the read request is read in step S632, and the mobile phone 201 (CLF224) 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 (CLF224) as a response confirms the state of the card included in the read data and confirms the service to be registered. For example, when the 3-1 service 257 (FIG. 14) is not registered, the data of the 3-1 service 257 is prepared. When the data is prepared, registration of the service is executed in step S556.

In this case, since the service is registered using the third packet in the third communication method, the data for service registration is packetized into the third packet, and the mobile phone 201 (CLF224) is used in the third communication method. ) Is executed 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 (CLF224) 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 by the process in step S633, the third application 256 executes the process of registering the service in step S634. In step S634, if the third application 256 executes the registration of the service and, as a result, succeeds or fails, the result of the registration process is output in step S635.

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

When the response indicates that the service registration was successful on the mobile phone 201 side, the reader / writer 202 subsequently started the service name registration (described later with reference to FIG. 27) and failed. When is indicated, for example, the service registration process is executed by executing the process of step S556 again. If the response from the mobile phone 201 (CLF224) indicates that the service has failed, the service registration process is executed using a communication method different from the communication method set at that time. You can do it. Here, the explanation is continued assuming that the service registration process is successful.

When it is determined that the service registration process is successful, the service name registration process is started. The process for registering the service name will be described with reference to the flowchart of FIG. 27. 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, in step S571, the reader / writer 202 requests the mobile phone 201 (CLF224) to respond in the second communication method.

The mobile phone 201 (CLF224) that received such a request in step S661 returns a response in step S662. In this case, it is a response indicating that the communication is performed by the second communication method. The reader / writer 202 that received such a response from the mobile phone 201 (CLF224) in step S572 issues a request to the mobile phone 201 to select the second communication method in step S573.

The mobile phone 201 (CLF224) that received such a request in step S663 switches to a state in which communication is performed by the second communication method, and then gives a response indicating that the second communication method is selected. This is performed for the reader / writer 202. The reader / writer 202 that received the response in step S574 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 (CLF224) can communicate with each other by the second communication method, in step S575, 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 mobile phone 201 is generated. Further, 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 process of registering the service name is executed by the reader / writer 202, so that the 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 CLF224 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 the data related to the registration of the service name in the APDU command format in step S692, the application manager 252 executes the process of registering the service name 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 these names and types is included in the APDU command supplied from the reader / writer 202.

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

When the reader / writer 202 receiving such a result in step S576 indicates that the response is successful, the reader / writer 202 recognizes the completion of the registration of the service name and ends the process. On the other hand, when the received response indicates that it has failed, for example, the process of step S575 is executed again to execute the process of registering the service name again.

In this way, 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. It is done. On the other hand, the second communication method (APDU command) that can be handled by the application manager 252 is used for the information about the 3-1 service 257, for example, the information such as the name of the 3-1 service 257 and the type of the service to be provided. Is done.

By registering the service and registering the service name in this way, the application manager 252 can manage the information related to the registered service in the registry 253. By managing the information of the registered service in the registry 253, the viewer 241 can browse the information. By making the viewer 241 viewable, 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 the 3-1 service 257, the 3-2 service 258, and the 3-3 service 259. It is possible to show the user that there are these three services. The method of presenting the present will be described later, and first, the registration of the service and the service name when another combination is set as the combination of the communication methods will be described.

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

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

In step S701, the reader / writer 202 requests the mobile phone 201 (CLF224) to respond in the second communication method. The mobile phone 201 (CLF224) that received such a request in step S802 returns a response in step S803. In this case, it is a response indicating that the communication is performed by the second communication method. The reader / writer 202, which receives such a response from the mobile phone 201 (CLF224) in step S702, issues a request to the mobile phone 201 (CLF224) to select the second communication method in step S703.

The mobile phone 201 (CLF224) that received such a request in step S804 is in a state of performing communication in the second communication method, and then a response indicating that the second communication method is selected is stepped. In S805, this is performed for the reader / writer 202. The reader / writer 202 that 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 (CLF224) can communicate with each other by the second communication method, in step S705, the reader / writer 202 sends a request for reading data to the mobile phone 201 (CLF224). Do it against.

When the mobile phone 201 (CLF224) receives the request for reading the data from the reader / writer 202 in step S806, the mobile phone 201 (CLF224) transfers the request to the third application 256. In this case, since communication is performed by the second communication method, the reader / writer 202 supplies the third command wrapped in the APDU command format to the UICC hardware 251 via CLF224 (FIG. 9). Further, it is supplied from the UICC hardware 251 to the application manager 252. The application manager 252 retrieves 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 the data read request (third command) from the reader / writer 202 via the communication path 352, the third application 256 reads the data requested by the third command in step S832, and the mobile phone 201. Supply to (CLF224). Upon receiving 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 out the data of the registered service in step S707. For example, if 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 state of the card is confirmed, and it is confirmed that there is no service to be registered, the service registration is executed in step S708.

In this case, since the service is registered 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 by the process in step S833, the third application 256 executes the service registration process in step S834. If the third application 256 executes the registration of the service in step S834 and as a result succeeds or fails, the result of the registration process is output to the application manager 252 in step S835.

The application manager 252 receiving 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 S811. In step S709, the response from the mobile phone 201 is received by the reader / writer 202.

When the received response indicates that the service registration was successful on the mobile phone 201 side, the reader / writer 202 continues to start the service name registration (described later with reference to FIG. 29). When it indicates that the failure has occurred, the service registration process is executed again, for example, by executing the process of step S708. Here, the explanation is continued assuming that the service registration process is successful.

In this way, 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. Data is generated, and the registration process is executed by exchanging the data. In other words, when registering the 3-1 service 257 provided by the third application 256, the third command handled by the third application 256 is wrapped in the APDU command format, and the registration process is executed.

Refer to the flowchart of FIG. 29 for the process when information about the registered service that is continuously performed after the service is registered by executing such a process, for example, information about the service name and the service type is registered. I will explain.

In this case, since the communication is already performed by the second communication method when the service is registered, the reader / writer 202 and the mobile phone 201 are in a state where they can communicate by the second communication method. Therefore, the process for starting the communication in the second communication method is omitted, and in step S751, the reader / writer 202 executes the 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. Further, the generated packet is a packet corresponding to the second communication method, that is, a packet including the APDU command in this case.

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

Due to the APDU command format, 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 the data related to the registration of the service name by the APDU command in step S882, the application manager 252 executes the process of registering the service name 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 these names and types is also included in the APDU command supplied from the reader / writer 202.

When the registration of the service name or the like is completed in step S882, the application manager 252 outputs the processing result to the CLF 224 as the processing of step S883. When the CLF 224 receives the processing result from the application manager 252 in step S852, it transmits it to the reader / writer 202 as a response in step S853. This response contains information indicating whether or not the service name registration process was successful.

When the reader / writer 202 receiving such a result in step S752 indicates that the response is successful, the reader / writer 202 recognizes the completion of the registration of the service name and ends the process. On the other hand, when the received response indicates that it has failed, for example, the process of step S751 is executed again to execute the process of registering the service name again.

In this way, when registering the 3-1 service 257 provided by the third application 256, 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. Things are used and done.

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

By registering the service and registering the service name in this way, the application manager 252 can manage the information related to the registered service in the registry 253. By managing the information of the registered service in the registry 253, the information can be viewed by the viewer 241. By making the viewer 241 viewable, it becomes possible to provide the information to the user.

[Processing by Application Manager]
Some UICC222s include an application called an application manager. The UICC 222 shown 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, UICC222, and controls resource management in UICC222, download of an application from an external device, and the like.

When the UICC 222 includes an application manager 601 each wirelessly compatible application, for example, a first application 254, a second application 255, or a third application 256 is installed via the application manager 601 at the time of installation. Each wirelessly compatible application needs to be assigned (selected) the operating authority from the application execution environment (Runtime Environment) at the time of operation. Further, when each application is executed, it is configured so that there is no direct influence from the application manager 601.

As shown in FIG. 30, for example, when the second application 255 and the third application 256 are installed, they are installed by using the APDU command via the application manager 601. After the installation, when the third application 256 is selected by the application manager 601, 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 including the application manager 601 such as this, the process for 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 is a process based on.

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

The processing of steps S1111 to S1115 executed on the mobile phone 201 side is the same processing as that of steps S801 to S805 of FIG. 28. That is, regarding the processing performed on the reader / writer 202 side and the mobile phone 201 side, the setting for performing communication by the second communication method is similarly performed regardless of whether or not the UICC 222 has the application manager 601. ..

As a result of the processing, when the communication can be performed by the second communication method, in step S1005, the reader / writer 202 issues a request for reading data to the mobile phone 201 (CLF224). When the mobile phone 201 (CLF224) receives the request for reading the data from the reader / writer 202 in step S1116, the mobile phone 201 (CLF224) transfers the request to the application manager 601.

The application manager 601 outputs the requested data to the CLF 224 in step S1152. Upon 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 the data from the mobile phone 201 (CLF224) as a response reads out the data of the service to be registered in step S1007.

In this case, since the service is registered 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 in the second communication method. The process is executed in step S1008. The mobile phone 201 (CLF224) 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.

The application manager 601 further transfers the supplied data to the third application 256 in step S1153. When the third application 256 acquires the supplied data by the process in step S1181, the third application 256 executes the service registration process in step S1182. If the third application 256 executes the registration of the service in step S1182 and as a result succeeds or fails, 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 CLF224. Upon receiving the result in the process in step S1120, the CLF 224 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, the response from the mobile phone 201 is received by the reader / writer 202, so that the service registration process is completed.

In this way, the reader / writer 202 also registers the service for the UICC 222 having the application manager 601 by executing the same processing as the processing for the UICC 222 not having the application manager 601. Can be done.

When the service is registered in this way, the service name registration process is continuously executed, but the process is the same as the process in the flowchart shown in FIG. 29, and thus the description thereof will be described here. Omit. That is, the process of registering the service name for the UICC 222 having the application manager 601 is performed in the same manner as the process of registering the service name with the UICC 222 not having 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 provided. The service name is registered in the process.

[Registration of services and service names using additional functions]
Next, with reference to the flowchart of FIG. 32, the service and the registration of the service name using the additional function will be described. 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, and the third application 256 provided by the third application 256 is used. The 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 the APDU command format in the third communication method cannot be used, it is determined that the packet of the third application 256 is transmitted / received. It's time. Such a determination is made, for example, when the processing of the flowchart shown in FIG. 20 is executed, and as a result, it is set to be realized by the additional function in step S163.

Among 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. 26. Therefore, the detailed description thereof will be omitted here. Further, among the processes in the flowchart shown in FIG. 32, the processes in steps S1401 to S1409 executed on the mobile phone 201 side are performed in the same manner as in steps S601 to S609 in the flowchart shown in FIG. The description is omitted.

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

In step S1453, when the third application 256 receives the third command relating to the registration of the service transmitted in the third packet from the reader / writer 202, the third application 256 executes the registration of the service based on the third command in step S1454. do. When the third application 256 completes the registration of the service, the third application 256 generates the service name in step S1455 and outputs the service name to the application manager 252.

That is, in this case, the third application 256 processes the command from the reader / writer 202 to generate the service name (information about the service) and supplies it 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 original packet is transmitted / received by 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 to access the registry 253.

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

Therefore, in step S1455 (FIG. 32), the service name is generated by the third application 256. The data for generating the service name is supplied from the reader / writer 202, and even if the processing of the supply itself is performed when the registration of the service is executed in step S1306, the data prepared in advance by the third application. It may be automatically generated from. Therefore, the reader / writer 202 transmits the data for registering the service and the data for registering the service name to the mobile phone 201 (third application 256) in the third packet.

Further, 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 automatically continue processing at the timing of registering the service. Further, the third application 256 side is configured to recognize such a command and execute the processing. In step S1455, 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 receiving the service name from the third application 256 and the command instructing the service name to be registered in the registry 253 via the API (Application Program Interface) receives the service name in step S1482. Based on the command issued, the received service name is registered in the registry 253. When the registration is completed, in step S1483, data indicating that the registration is completed is output to the third application 256.

When the third application 256 receives the data indicating the end of registration from the application manager 252 in step S1456, the third application 256 informs the CLF 224 of the data indicating that the registration of the service and the registration of the service name have been completed in step S1457. Output as a response. Upon receiving the 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 to recognize that the registration process is completed.

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

As pattern 1, as described above, a command that can be interpreted by the third application 256 is prepared. In the case of pattern 1, a definition is considered in which a command indicating the start indicating the start of service registration and an end indicating the end are prepared, and the exchange of service registration data between the start and the end is grouped as a unit of service. Will be.

As pattern 2, the act of creating a series of service areas is automatically determined as one service unit. In this case, the service area generated by one command or one block in which commands are combined is viewed as a unit of service.

In addition to the definition for such a 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 the 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, the registration of the service name can be executed by the third application 256.

As pattern 2, it is conceivable to register the 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 from the reader / writer 202 to the block 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 the service name by holding the correspondence table. In pattern 3, the third application 256 holds a correspondence table of numbers and service names for identifying areas such as system codes and service codes and services, and when the service is registered, the identification corresponding to the service is performed. The service name is registered by reading the number and the service name from the correspondence table. In addition, when a new service not listed in the retained correspondence table is provided, the correspondence table itself is updated. This correspondence table can also be updated by executing a process such as sending a command from the reader / writer 202 side.

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

[Processing related to service name display]
By registering the service and the service name in this way, when the viewer 241 presents the information of the registered service to the user, the information is presented on the screen as shown in FIG. 33 or FIG. 34. 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 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 has a "first service" which is the name of the service provided by the first application 254, a "second service" which is the name of the service provided by the second application 255, and a third. The "third service", which is the name of the 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 this information also refers to the registry 253. Since it is recognized by the above, these information are also displayed on the display 401.

That is, as shown in FIG. 33, under the name of "third service" corresponding to the third application 256, the name of "3-1 service" corresponding to the third service 257, third-2. The name "3-2 service" corresponding to service 258 and the name "3rd service" corresponding to 3rd service 259 are displayed as being associated with the name "3rd service". To.

By displaying such a display, the user can recognize that the third service includes three services, the 3-1 service, the 3-2 service, and the 3-3 service. .. Such display is 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.

As another display example, FIG. 34 is shown. In the display example shown in FIG. 34, first, "first service" which is the name of the service provided by the first application 254 and "second service" which is the name of the service provided by the second application 255 are displayed on the display 401. Has been done. Further, 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 "3rd service" corresponding to 259 is displayed.

By displaying such a display, the user recognizes that there are five services of the first service, the second service, the 3-1 service, the 3-2 service, and the 3-3 service. Can be done. In this case, the user does not recognize that the third application 256 provides the three services, and in the same line as the first service and the second service, the 3-1 service, the 3-2 service, and the third service. 3-3 It becomes possible to recognize the service. Such display is 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 difference in display is determined by how the service name is managed in the registry 253. Therefore, how to manage the service name will be described. First, it is conceivable to attach a dummy AID to the service and manage the service with the dummy AID. Further, the dummy AID is written in the registry 253 so that the information about the service is managed in the registry 253. AID is an abbreviation for Application IDentifier.

When a plurality of applications are registered in UICC222, for example, when the "name" of the file given to each application is the same by chance, it does not operate normally and the file may be corrupted. In order to prevent such a situation, an application identifier (AID) is assigned to ensure the uniqueness of the application. In this way, the application is managed by AID. Further, in order to ensure uniqueness, the AID is set to a unique value.

The AID is defined by ISO7816-5, and is composed of 16 bytes, 5 bytes are RID, and the remaining 11 bytes are PIX. The RID is a provider of the application, and is, for example, a unique ID acquired by a predetermined company. Therefore, the 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 numbered within the company to which the RID is assigned. Therefore, in the third application 256, a dummy AID is generated based on the following rules. The dummy AID is an AID assigned to an application that does not actually exist. Further, the dummy AID is provided for the purpose of displaying the application registered in UICC222 from the viewer 241.

Therefore, this dummy AID is not used for the user to select and start 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)

A dummy AID with such a configuration does not affect other applications. By writing the dummy AID to the registry 253, the dummy AID is configured within the framework of the third application 256 without having any influence on the first application 254 other than the third application 256, for example. Can be done. Therefore, when the application is called by designating the dummy AID, 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 in this way is registered in the registry 253 from the third application 256 via the API. Since the viewer 241 can see 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, for example, a screen as shown in FIGS. 33 and 34.

As shown in FIG. 33, it is also shown in FIG. 34 that the services realized by a predetermined application are displayed hierarchically depending on the configuration of the dummy AID itself, the method of attaching the dummy AID to the service, and the like. As such, it can be displayed in the same layer as the service realized by a predetermined application.

[About the effect]
In this way, even if the service provided by the third application 256 is independently registered in UICC222, for example, the existence of each service can be confirmed from the viewer 241 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 making the user recognize the existence of each service.

Further, the display can be, for example, as shown in FIG. 34, a display that can be referred to by the user as a service in the same row as a service provided by another application. Moreover, even if it is a new service, it can be displayed as a service in the same line as the service already registered. Alternatively, as shown in FIG. 33, the service provided by a predetermined application can be displayed hierarchically in association with the application.

In addition, if the existence of the service can be confirmed, it will be possible to add the opposite application when necessary. That is, it is possible to give a degree of freedom to the relationship between the service and the application.

In addition, service registration and service name registration can be performed by making the best use of the existing infrastructure. Therefore, even if the system is migrated to manage the service by UICC222, it is possible to reduce the cost after the migration. Furthermore, by being able to utilize the infrastructure, system migration can be performed without major changes, which may cause confusion for both users and developers. Can be prevented.

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

FIG. 35 is a block diagram showing an example of hardware configuration of a computer that executes the above-mentioned series of processes programmatically. 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 non-volatile memory, and the like. The communication unit 1009 includes a network interface and the like. 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 above-mentioned series. Is processed.

The program executed by the computer (CPU 1001) can be recorded and provided on the removable media 1011 as a package media or the like, for example. The program can also 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 mounting the removable media 1011 in 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 the ROM 1002 or the storage unit 1008 in advance.

The program executed by the computer may be a program in which processing is performed in chronological order according to the order described in the present specification, in parallel, or at a necessary timing such as when a call is made. It may be a program in which processing is performed.

Further, in the present specification, the system represents the entire device composed of a plurality of devices.

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 Unit, 502 Communication method determination unit, 503 Service registration unit, 504 Update processing unit

Claims (8)

A communication control unit that controls communication by non-contact communication,
It corresponds to the first communication method called Type A or Type B related to the non-contact communication, and corresponds to the first application providing the first service and the second communication method called Type F related to the contactless communication. , A storage unit that stores a second application that provides a second service different from the first service.
A management unit having a function of installing or deleting the first application and the second application stored in the storage unit, and
A display control unit that controls the display of the information of the first service and the information of the second service installed by the management unit on the display .
Based on the first data for registering the first service received from another device under the control of the communication control unit, the first service is registered by the processing of the first application, or the first service is registered. Based on the second data for registering the second service, the service registration unit that registers the second service by the processing of the second application, and the service registration unit.
A generation unit that generates first information about the first service or second information about the second service registered by the service registration unit.
An update unit that updates the information stored in the storage unit with the first information or the second information generated by the generation unit.
Equipped with
The management unit is an information processing device that is an execution environment for Java Card (registered trademark). The information processing apparatus according to claim 1, wherein the operation authority is transferred from the execution environment related to Java Card (registered trademark) when the first application or the second application is operated. The generation unit generates the first information or the second information by processing a command supplied from the other device by the first application or the second application. Or the information processing apparatus according to 2 . The generation unit and the update unit update the information stored in the storage unit from the contents of the definition block containing the first information or the second information specified in advance, according to claims 1 to 3. The information processing device described in any of them. The generation unit includes a correspondence table in which a number for identifying the first service or the second service is associated with the first information or the second information, and the correspondence table is referred to. , The information processing apparatus according to any one of claims 1 to 4 , which generates the first information or the second information. The information processing apparatus according to any one of claims 1 to 5 , wherein the first data or the second data is a packet in a communication method unique to the first application or unique to the second application. An information processing device equipped with a communication control unit that controls communication by non-contact communication
It corresponds to the first communication method called Type A or Type B related to the non-contact communication, and corresponds to the first application providing the first service and the second communication method called Type F related to the contactless communication. , Stores a second application that provides a second service that is different from the first service.
It manages to install or delete the stored first application and the second application, and manages to install or delete it.
Controls to display the installed information of the first service and the information of the second service on the display .
Based on the first data for registering the first service received from another device under the control of the communication control unit, the first service is registered by the processing of the first application, or the first service is registered. Based on the second data for registering the second service, the second service is registered by the processing of the second application.
Generate the first information about the registered first service or the second information about the second service,
The generated information stored in the first information or the second information is updated, and the information is updated.
The above management is performed in the execution environment related to Java Card (registered trademark).
Information processing method. For a computer that controls an information processing device equipped with a communication control unit that controls communication by non-contact communication,
It corresponds to the first communication method called Type A or Type B related to the non-contact communication, and corresponds to the first application providing the first service and the second communication method called Type F related to the contactless communication. , Stores a second application that provides a second service that is different from the first service.
It manages to install or delete the stored first application and the second application, and manages to install or delete it.
Controls to display the installed information of the first service and the information of the second service on the display .
Based on the first data for registering the first service received from another device under the control of the communication control unit, the first service is registered by the processing of the first application, or the first service is registered. Based on the second data for registering the second service, the second service is registered by the processing of the second application.
Generate the first information about the registered first service or the second information about the second service,
Update the generated information stored in the first information or the second information.
Including steps
The management is a computer-readable program that executes the processing performed in the execution environment related to Java Card (registered trademark).

Images