JP3703098B1 - Mobile terminal device - Google Patents

Abstract

A non-contact card function content can be managed, and the non-contact card function content can be easily added / deleted.
A mobile terminal 11 according to the present invention includes a mobile device OS 31 that executes various functions of the mobile terminal 11, a Felica application manager (FAM) 32, and a Felica that drives a Felica OS 35 according to the control of the FAM 32. It mainly includes a device driver 33 and a Felica chip 34 that stores Felica content. On this FAM 32, a JAM 36 that manages a Java (registered trademark) application having a network computing function and an API for starting up a browser and a KVM 37 that executes an API operate, and other applications such as a browser 38 are operated. The menu 39 and the Felica viewer 40 operate.
[Selection] Figure 6

Description

  The present invention relates to a mobile terminal device, a contactless card function management system, and a contactless card function acquisition system, and more particularly, a mobile terminal device, a contactless card function management system, and a contactless card that can easily manage and acquire contactless card functions. The present invention relates to a contact card function acquisition system.

  In recent years, an IC card in which an IC is embedded in a plastic card has become widespread. This IC card can be equipped with functions such as various cards, credit cards, and debit cards. A technique for mounting this IC card function on a mobile terminal device has been developed.

  In a mobile terminal device equipped with an IC card function, a desired IC card function can be selected in accordance with a user operation on the display screen. When the user selects and executes a desired IC card function on the display screen, the application corresponding to the IC card function is activated to execute the IC card function.

JP 2003-76958 A

  However, in such a mobile terminal device, when processing for an IC card function, for example, addition processing or deletion processing is performed, an application corresponding to the IC card function must be started, and complicated operations are required. Met. Further, when the IC card function is viewed on the mobile terminal device, all the IC card functions are simply displayed, and the IC card functions are not managed at present.

  The present invention has been made in view of such a point, and provides a mobile terminal device capable of managing content for contactless card function and easily adding / deleting content for contactless card function. The purpose is to provide.

The mobile terminal device of the present invention has a terminal main body, a terminal operating system for operating various functions used in the terminal main body, and an area corresponding to a plurality of categories. Non-contact card storage means for storing in association with the non-contact card function control means for performing control for using the non-contact card function content using the various functions, and the non-contact card storage means Display means for displaying the content for contactless card function stored in the category in association with the category .

  According to this configuration, the contactless card function control means can manage the contactless card function content, and thus the contactless card function content can be used using various functions. As a result, the user can easily use the contactless card function content, for example, on the display screen.

In the mobile terminal device of the present invention, it is preferable that the contactless card function control means has an association table associating the contactless card function content with an application that provides the contactless card function content.

According to this configuration, since the association table that associates the application that provides the contactless card function content is provided, the contactless card function content can be managed. As a result, the content for contactless card function in the contactless card storage means can be displayed for each storage area in the storage means. In addition, since the content for contactless card function can be managed for each storage area by the related table, the capacity in the content for contactless card function can be grasped for each storage area.

In the mobile terminal device of the present invention, the association table has a deletion URL for each contactless card function content used when deleting the contactless card function content, and the contactless card function The control means preferably requests the deletion URL when deleting the contactless card function content on the display screen when the viewer function is used.

According to this configuration, since the deletion URL is managed by the related table, the content for contactless card function can be obtained at the link destination of the deletion URL without starting the content provider application that provides the content for contactless card function. Can be deleted.

In the mobile terminal device according to the present invention, the contactless card function control means includes the contactless card function in the related table when new contactless card function content is added to the contactless card storage means. It is preferable to update the content for use.

According to this configuration, when new contactless card function content is added, the information is updated in the related table, so that the contactless card function content can be managed in an organized state.

In the mobile terminal device of the present invention, it is preferable that the display means displays a remaining capacity of an area corresponding to the category in the contactless card storage means.

According to this configuration, the user can visually recognize the remaining capacity of the area in the contactless card storage means.

The mobile terminal device of the present invention displays a terminal main body, contactless card storage means for storing contactless card function content, and contactless card function content stored in the contactless card storage means. When the contactless card function content is deleted on the display means, the contactless card function from the contactless card storage means and from the server of the service provider that provides the contactless card function content Contactless card function control means for performing control to delete the content for use.

According to this configuration, since the contactless card function content can be deleted without activating the application, the contactless card function content can be easily deleted by a simple user operation. Convenience is improved.

In the mobile terminal device of the present invention, the contactless card function control means includes an association table including a deletion URL for each contactless card function content used when deleting the contactless card function content. Preferably, the contactless card function control means requests the deletion URL when the display means deletes the contactless card function content.

According to this configuration, since the deletion URL is managed by the related table, the content for contactless card function can be obtained at the link destination of the deletion URL without starting the content provider application that provides the content for contactless card function. Can be deleted.

  According to the present invention, addition / deletion control of content for contactless card function is controlled via an application that provides content for contactless card function, and addition of content for contactless card function is performed from an external acquisition means. Since the contactless card function control means for controlling is provided, the contactless card function content can be managed, and addition / deletion of the contactless card function content can be performed with a simple operation.

  The present inventors pay attention to the point that the contactless card function is executed by the operating system for the contactless card function and the other functions are executed by the terminal operating system. By providing a manager that can control other functions such as browser function, menu function, viewer function, etc., it is easy to manage content for contactless card function and add / delete content for contactless card function The present invention has been found out that it can be carried out.

  That is, the gist of the present invention is to control addition / deletion of contactless card function content via an application that provides contactless card function content, and from the external acquisition means, By providing contactless card function control means for performing additional control, the content for contactless card function is managed, and addition / deletion of the content for contactless card function is performed with a simple operation.

Hereinafter, embodiments of the present invention will be described in detail with reference to the accompanying drawings.
FIG. 1 is a diagram showing a schematic configuration of a contactless card function management system and a contactless card function acquisition system according to an embodiment of the present invention.

  The system shown in FIG. 1 includes a mobile terminal 11 according to the present invention, a mobile communication network server 13 connected to the mobile terminal 11 via a mobile communication network 12, a mobile terminal 11 and the Internet 14. It is mainly composed of a Web server 15 and a contactless card function content server 16 connected via a simple network.

  The mobile terminal 11 has functions capable of executing various applications 111 and contactless card functions 112. In addition, the mobile terminal 11 includes a reader / writer (not shown) which is an acquisition unit capable of transmitting / receiving information to / from an external reader / writer (R / W) 17. The external reader / writer 17 is driven by the controller 18.

  The contactless card function 112 in the mobile terminal 11 refers to a function capable of adding / deleting a contactless card, for example, a content for contactless IC card function, such as Felica (registered trademark). In order to realize the contactless card function 112, the mobile terminal is equipped with a storage area for storing contents and an operating system (controller) for the contactless card function.

  The mobile communication network 12 is a network between the mobile terminal 11 and the mobile communication network server 13. The mobile communication network 12 includes a mobile packet communication network in addition to a normal mobile communication network. The mobile communication network server is, for example, an i-mode (registered trademark) server and has a gateway function for connecting the mobile communication network 12 and the Internet 14, and specifically includes an information distribution function, a mail transmission / reception function, and a mail storage. It has a function, a contract customer management function, an information provider management function, and an information fee billing function.

  The network includes the Internet 14 and other networks such as LAN and WAN. The Web server 15 is a server on the Internet 14 that stores an application 111 to be downloaded to the mobile terminal 11.

  The content server 16 stores content for contactless card functions provided from a plurality of service providers that provide content for contactless card functions, and contactlessly via a controller and a network that realizes the contactless card functions. Add / delete card function contents, initialize, and read / write data. In addition, the content server 16 also includes an application for performing processing on the controller that realizes the contactless card function from the content server 16. The content server may be provided on the Internet 14 by the service provider together with the Web server, or may be on a network different from the Internet 14 separately from the Web server of the service provider. For example, when the contactless card function is Felica, the content server 16 is a Felica server.

  In the system having the above-described configuration, the mobile terminal 11 controls addition / deletion of content for contactless card function via an application that provides content for contactless card function, and via R / W Perform additional control of the acquired content for contactless card function. In this way, the addition of the contactless card function content can be controlled through the application or from the R / W without going through the application, so that the user can easily add / delete the contactless card function content. Can be done by operation.

  When the mobile terminal 11 controls the addition / deletion of the contactless card function content via the application 111 that provides the contactless card function content, the application 111 of the mobile terminal 11, for example, an i-appli The contactless card function 112 is accessed by (registered trademark). Then, the content for contactless card function is added / deleted on the application 111.

  In the case where the mobile terminal 11 controls the addition of the contactless card function content via the R / W, the contactless card function content is directly added from the external R / W 17 without going through the application 111. . At this time, content information corresponding to the added contactless card function content is acquired from the Web server 15.

  In the system having the above configuration, it is possible to perform information distribution, mail transmission / reception, mail accumulation, contract customer management, information provider management, and information fee billing. Then, detailed procedures are not described.

  FIG. 2 is a diagram showing a configuration of a storage area for storing content for contactless card function of the mobile terminal device according to the embodiment of the present invention. This storage area is, for example, a Felica chip when the contactless card function is Felica. This storage area is composed of, for example, a common area 21, a public area 22, and a free area 23. These areas are classified according to, for example, the category of content for contactless card function, the difference in service level, and the level of security. For example, the common area 21 and the public area 22 are areas for storing content for contactless card functions of services having a relatively high service level and high security, and the free area 23 has a relatively low service level and security. The area for storing content for contactless card function with a lower service. Note that the storage area, category, service level, or security can be changed as appropriate. As described above, the storage area is divided according to the category, service level, security, and the like, so that the contactless card content can be managed for each category, service level, and security level.

  The contactless card function content stored in each of the common area 21, the public area 22, and the free area 23 can be displayed together in each area as shown in FIGS. . FIG. 3 is a diagram showing the content for contactless card function in the common area 21 on the display screen of the mobile terminal 11, and FIG. 4 is for contactless card function in the public area 22 on the display screen of the mobile terminal 11. FIG. 5 is a diagram showing content for contactless card function in the free area 23 on the display screen of the mobile terminal 11. Each of the services shown in FIGS. 3 to 5 is contactless card function content provided by a service provider.

  3 to 5, an indicator 24 indicating the remaining capacity of each area is displayed on the display screen. The remaining capacity in each area may be indicated by using the indicator 24 as shown in FIGS. 3 to 5. The number of storable contents is set in advance, and the set number of content display areas (3 in FIG. 3). 4, two in FIG. 4 and three in FIG. 5), and an unused content display area may be displayed in a blank. By providing such an indicator or a blank content display area, the user can visually recognize the remaining capacity of each area in the storage area.

  Furthermore, when newly adding content for contactless card function, the content capacity is compared with the remaining capacity of the area where the content is stored, and if the content capacity exceeds the remaining capacity, the capacity You may make it display that it is insufficient, and the content for the non-contact card function already stored needs to be deleted. By displaying in this way, the user can recognize the necessity of deleting the content for contactless card function.

  FIG. 6 is a diagram showing an internal configuration of the mobile terminal 11 according to the embodiment of the present invention. In FIG. 6, a case will be described in which the contactless card function is Felica, the storage area is a Felica chip, and the operating system (controller) for the contactless card function is a Felica operating system (Felica OS).

  In the configuration shown in FIG. 6, a terminal operating system (mobile device OS) 31 that executes various functions of the mobile terminal 11, a Felica Application Manager (FAM) 32 that is a contactless card function control means, The Felica device driver 33 that drives the Felica OS 35 under the control of the FAM 32 and the Felica chip 34 that stores Felica content are mainly included. On this FAM 32, a Java application manager (Java Application Manager: JAM) 36 that manages a Java (registered trademark) application having a network computing function, an API (Application Program Interface) for starting a browser, and an API are executed. A KVM (K Virtual Machine) 37 as a device operates, and other applications such as a browser 38, a menu 39, and a Felica viewer 40 operate. In FIG. 6, the browser 38, the menu 39, and the Felica viewer 40 operate on the FAM 32. However, this configuration is an example, and functions other than the Felica viewer 40 such as the browser 38 and the menu 39 are provided. In addition to operating on the FAM 32, the mobile device OS 31 may also be configured to operate.

  The mobile device OS 31 executes functions other than functions related to Felica, such as an information distribution function, a mail transmission / reception function, a mail storage function, a contract customer management function, an information provider management function, and an information fee billing function.

  The FAM 32 performs control for using the Felica content according to the present invention. In particular, the FAM 32 performs access control for easily acquiring content for contactless card functions from an external R / W, management of acquired Felica content, and issuance of commands for executing the browser 38, menu 39, and Felica viewer 40. . As a result, the FAM 32 can manage the Felica content, and the Felica content can be used by using functions such as the browser 38 and the Felica viewer 40. As a result, the user can easily use the Felica content, for example, display it on the display screen.

The FAM 32 has an association table that associates Felica content with an application (i-appli (registered trademark)) that provides the Felica content in order to manage the acquired Felica content. This association table is, for example, as shown in FIG. 7, and the services 1 to 3 that are Felica contents are associated with the i-αppli α _{1 to} α _{3 of} the service provider that provides the services 1 to ₃ . . Further, in this related table, the date when Felica content is acquired (registration date) and the date when Felica content is deleted (deletion date) are managed together. Further, in the association table, the URL of the site where the Felica content is actually deleted (deletion URL) and the area in the Felica chip 34 are also managed.

  Therefore, when Felica content is acquired, that is, when new Felica content is added, the service provider is registered in the application item, and the content is registered in the service item. In addition, the date of registration is registered as the registration date. Furthermore, a deletion URL used when deleting Felica content is also registered. At this time, there are no particular restrictions on the items to be registered in the application item and the service item. Thus, when new Felica content is added, it is possible to manage the Felica content in an organized state by updating the information in the related table.

  When Felica content is added via an application, when updating the related table, content information such as a service name is acquired via the application, and the related table is updated using the content information. On the other hand, when the Felica content is added from the external R / W 17, when the related table is updated, for example, the content information is stored in a predetermined address of the Felica chip 34, and when some user operation is performed, the FAM 32 Extracts new content information from the address and updates it in the related table. In addition, when adding Felica content from external R / W17, the method of updating a related table is not specifically limited.

  On the other hand, when deleting the Felica content, a deletion URL associated with the application or service corresponding to the Felica content to be deleted is referred to. At this time, the date of deletion is updated to the deletion date. In addition, this association table is used when the Felica Viewer 40 performs display for each area as shown in FIGS. That is, when the display as shown in FIGS. 3 to 5 is performed by the Felica viewer 40, the FAM 32 activates the Felica viewer 40 and refers to the related table. Thereby, it is possible to perform a very easy-to-see display for each region as shown in FIGS. As a result, the user can easily recognize the contents and state of the Felica content for each area.

  As described above, the FAM 32 has the association table as shown in FIG. Thereby, it becomes possible to display the Felica content for every area | region in the Felica chip | tip 34 as shown, for example in FIGS. Further, since the Felica chip 34 can be managed for each area by the related table, for example, the remaining capacity for each area of the Felica chip 34 is managed by the related table, so that the capacity in the Felica chip 34 is grasped for each area. Is possible. Furthermore, by managing the deletion URL with the related table, it is possible to delete the content at the link destination of the deletion URL without activating the i-appli.

  The FAM 32 controls the addition / deletion of Felica content via an application that provides Felica content, that is, activates the i-appli, and controls the addition of Felica content via the R / W. In this way, by controlling the addition of Felica content via an application such as an i-appli or from the R / W without going through the application, the user can easily add / delete the Felica content. The procedure for adding / controlling Felica content is as follows.

  In the mobile terminal 11, Felica content can be added / deleted on the display screen using the viewer function by the FAM 32. In this case, when a common area as shown in FIG. 3 is selected and a specific Felica content (in this case, mobile ANA) is activated, tabs are displayed as shown in FIG. Function selection becomes possible. You can use mobile ANA Felica content by selecting the “Use” tab. On the other hand, by selecting the “Delete” tab, the mobile ANA Felica content can be directly deleted without activating the i-appli.

  Here, a procedure for adding / deleting Felica content via the i-appli on the mobile terminal 11 and a procedure for adding Felica content via the R / W 17 will be described. FIG. 9 is a sequence diagram showing a procedure for adding / deleting Felica content via an application in the mobile terminal 11. FIG. 10 is a sequence diagram showing a procedure for adding Felica content via the R / W in the mobile terminal 11.

  A procedure for adding / deleting Felica content via an application in the mobile terminal 11 will be described with reference to FIG. First, a case where FeliCa content is added by starting an i-appli will be described. First, start i-αppli. The i-appli activation condition is not particularly limited, and may be activated from a specific tag described in HTML acquired by a browser, or may be activated from a specific description in the mail text.

  When an operation for acquiring Felica content is performed on the i-appli, a control signal for acquiring Felica content is transmitted from the i-appli to the FAM 32 (S11). When receiving this control signal, the FAM 32 requests the Felica OS 35 to convert the command (S12). The Felica OS 35 converts the command in response to the command conversion request, sends the command to the Felica server, and makes a request for the URL for content acquisition (S13). The Felica server provides Felica content in response to a request. The mobile terminal 11 downloads the Felica content from the Felica server and performs the actual content acquisition process (S14). This Felica content is stored in the Felica chip 34. When the Felica content is stored in the Felica chip 34, a completion notification is sent from the Felica server to the Felica OS 35 (S15). Then, a completion notice is sent from the Felica OS 35 to the FAM 32 (S16), and a completion notice is sent from the FAM 32 to the i-appli (S17).

  When the Felica content is stored in the Felica chip 34 in this way, the FAM 32 updates the information on the Felica content acquired in the association table. Thereafter, when the user starts the Felica viewer 40, the FAM 32 refers to the related table and displays the Felica content for each area. Thereby, the user can visually recognize the acquired Felica content on the viewer.

  Next, a case where FeliCa content is deleted by activating an i-appli will be described. First, start i-αppli. The i-appli activation condition is not particularly limited, and may be activated from a specific tag described in HTML acquired by a browser, or may be activated from a specific description in the mail text.

  When an operation for deleting the FeliCa content is performed on the i-appli, a control signal for deleting the FeliCa content is sent from the i-appli to the FAM 32 (S21). Upon receiving this control signal, the FAM 32 requests the Felica OS 35 to convert the command (S22). The Felica OS 35 converts the command in response to the command conversion request, sends the command to the Felica server, and makes a request for the URL for content deletion (S23). The Felica server deletes the Felica content in response to the request. In the mobile terminal 11, processing for deleting the Felica content from the Felica chip 34 is performed (S24). When the Felica content is deleted from the Felica chip 34, a completion notification is sent from the Felica server to the Felica OS 35 (S25). Then, a completion notice is sent from the Felica OS 35 to the FAM 32 (S26), and a completion notice is sent from the FAM 32 to the i-appli (S27).

  When the Felica content is deleted from the Felica chip 34 in this way, the FAM 32 deletes and updates the information on the Felica content in the related table. Thereafter, when the user starts the Felica viewer 40, the FAM 32 refers to the related table and displays the Felica content for each area. Thereby, the user can confirm on the viewer that the Felica content has been deleted. As a result, the user can recognize the availability of each area of the Felica chip 34 by deleting the Felica content.

  Next, a procedure for adding Felica content directly via the R / W in the mobile terminal 11 will be described with reference to FIG. When acquiring Felica content from the external R / W 17, the mobile terminal 11 is brought close to the external R / W. At this time, processing such as authentication is performed between the external R / W 17 and the Felica OS 35 (S31). When authentication is performed, Felica content is transmitted from the external R / W 17 via the R / W of the mobile terminal 11 (S32). This Felica content is stored in the Felica chip 34. When the Felica content is stored in the Felica chip 34, an end process or the like is performed between the external R / W 17 and the Felica OS 35 (S33).

  After adding the Felica content to the Felica chip 34 in this way, when the user opens the menu (S41), a request is made to refer to the related table from the menu to the FAM 32 (S42). Upon receipt of the request, the FAM 32 issues a command to the Felica chip 34 and acquires the registration status of the Felica content stored in the Felica chip 34 (S43). In addition, when there is newly registered Felica content, the FAM 32 acquires content information such as a service name from the Felica server (S44). The FAM 32 updates the content information acquired in this way to the related table (S45). Further, the FAM 32 responds to the menu with the storage status of the Felica content, and the menu displays the screen according to the storage status (S45).

  As described above, the mobile terminal 11 having the configuration shown in FIG. 6 can acquire Felica content directly from the external R / W without activating the i-appli. Felica content can be acquired, improving user convenience. Further, when the Felica content is directly acquired from the external R / W, the content information about the Felica content is acquired from the Felica server. Therefore, the Felica content acquired by starting the i-appli is acquired from the external R / W. Can be managed in the same way.

  Further, when deleting the Felica content on the screen shown in FIG. 8, the FAM 32 requests the deletion URL of the related table to delete the Felica content. In this way, in the mobile terminal 11 having the configuration shown in FIG. 6, it is possible to delete the Felica content on the screen without activating the i-appli, so that the Felica content can be easily performed by a simple operation of the user. The user convenience can be improved.

  As described above, the Felica content can be managed by the mobile terminal 11 according to the present invention, and the addition / deletion of the Felica content can be easily performed. Therefore, the user can perform simple operations, that is, from the external R / W 17. Addition and deletion of Felica content can be performed by adding Felica content and deleting Felica content on the mobile terminal 11 screen.

  Here, in order to clarify the effect of the present invention, the addition / deletion of Felica content in a mobile terminal that does not have the FAM 32 will be described. FIG. 11 is a diagram showing another internal configuration of the mobile terminal device that does not have the FAM. In the configuration shown in FIG. 11, a mobile device OS 51 that executes various functions of a mobile terminal, a Felica OS 54 that is an operating system for Felica, a Felica device driver 52 that drives the Felica OS 54, and Felica content are stored. It has a Felica chip 53 mainly. On this Felica OS 54, a JAM 55 that manages Java applications and a KVM 56 that is a device that executes an API and an API for starting a browser operate, and other applications such as a browser 57 and a menu 58 are run on the mobile device OS 51. Operate.

  In the configuration shown in FIG. 11, since FAM is not provided, the Felica OS 54 controls network computing related to Felica, and the browser 57 and the menu 58 cannot be controlled. For this reason, the Felica content cannot be displayed separately for each area on the screen, and all the Felica content is simply displayed as shown in FIG. Further, since the FAM is not provided, the addition / deletion of Felica content can be performed only by the procedure shown in FIG. 9, and cannot be directly acquired from the external R / W as shown in FIG. For this reason, the addition / deletion of Felica content must be performed by activating the i-appli.

  On the other hand, the mobile terminal 11 of the present invention includes a FAM 32 that controls the addition / deletion of Felica content via an application that provides Felica content and also controls the addition of Felica content from the external R / W 17. Therefore, the Felica content can be managed, and the Felica content can be directly acquired from the external R / W, so that the Felica content can be added / deleted with a simple operation.

  In the present embodiment, the case where the FAM function is built in the portable terminal device has been described. However, the FAM function according to the present invention is applied to a UIM card (User Identity Module card) or a SIM card (Subscriber Identity Module card). It is good also as a structure which stores in an IC card like this and makes the IC card removable to a portable terminal device. In this case, the portable terminal device is provided with a card insertion slot such as a slot into which an IC card can be inserted. In this way, by storing the FAM function (FAM, Felica device driver, Felica chip, Felica OS) in the IC card and inserting the IC card into another portable terminal device, the Felica content stored in the IC card is transferred to other It can be used in a portable terminal device. Thereby, Felica content can be freely moved between portable terminal devices, and the degree of freedom of use of Felica content is expanded.

  As described above, when the FAM function is mounted on the IC card, a part of the FAM function may be mounted on the portable terminal device, and the remaining functions of the FAM function may be mounted on the IC card. For example, a related table used by FAM for managing various contents is stored in an IC card, and other FAM control functions (devices, programs, applications) such as FAM, Felica device driver, Felica chip, and Felica OS are installed in the mobile terminal device. To do. As described above, by separating the FAM function and making the mounting locations different, it is possible to increase the security regarding the Felica content.

  When the related table is stored in the IC card in this way, as shown in FIG. 13, an area for user authentication information (for example, user ID and password) is provided in the related table, and this related table is used when the IC card is used. It is preferable to perform user authentication. For example, when an IC card storing such a related table is taken out from a mobile terminal device and inserted into another mobile terminal device to use Felica content, the FAM mounted on the mobile terminal device is an IC card. When the ID is identified and an unknown user is using it, that is, when the ID is different from the ID of the own apparatus, user authentication is performed. At this time, the user is requested to input a user ID and a password. In order to further increase security, it is preferable to use biometric technology such as fingerprint matching as user authentication. For example, a scanner that scans a fingerprint image is provided in the mobile terminal device, and the fingerprint image is acquired by sliding the finger or placing the finger on the scanner.

  The present invention is not limited to the embodiment described above, and can be implemented with various modifications. For example, the present invention is not limited to the configuration described in the above embodiment, and can be implemented with appropriate modifications without departing from the scope of the present invention. For example, in the above embodiment, a case has been described in which FAM is used as a control means for starting a browser, menu, and Felica viewer together with Felica. However, in the present invention, a browser, menu, and Felica viewer are started together with Felica. Other control means and management means that can be used may be used. Moreover, in the said embodiment, although the case where a non-contact card function is FeliCa is demonstrated, this invention is applied similarly when the non-contact card function is a non-contact card function other than Felica. Can do.

It is a figure which shows schematic structure of the non-contact card function management system and non-contact card function acquisition system which concern on one embodiment of this invention. It is a figure which shows the structure of the storage area which stores the content for non-contact card functions of the mobile terminal device which concerns on one embodiment of this invention. It is the figure which showed the content for non-contact card functions of a common area | region on the display screen of a mobile terminal device. It is the figure which showed the content for non-contact card functions of a public area in the display screen of a mobile terminal device. It is the figure which showed the content for non-contact card functions of a free area | region on the display screen of a mobile terminal device. It is a figure which shows the internal structure of the mobile terminal device which concerns on one embodiment of this invention. It is a figure which shows the related table which correlates the content for non-contact card functions, and the application which provides this content for non-contact card functions. It is a figure which shows the state which activated one of the contents for non-contact card functions of a common area | region on the display screen of a mobile terminal device. It is a sequence diagram which shows the procedure which adds / deletes the content for non-contact card functions via an application in a mobile terminal device. It is a sequence diagram which shows the procedure which adds the content for non-contact card functions via R / W in a mobile terminal device. It is a figure which shows the other internal structure of a mobile terminal device. It is the figure which showed the content for non-contact card functions in the display screen of the mobile terminal device shown in FIG. It is a figure which shows the other example of the related table which correlates the content for non-contact card functions, and the application which provides this content for non-contact card functions.

Explanation of symbols

DESCRIPTION OF SYMBOLS 11 Mobile terminal 12 Mobile communication network 13 Mobile communication network server 14 Internet 15 Web server 16 Contactless card function content server 17 External reader / writer 18 Controller 21 Common area 22 Public area 23 Free area 24 Indicator 31 Mobile device OS
32 FAM
33 Felica device driver 34 Felica chip 35 Felica OS
36 JAM
37 API, KVM
38 Browser 39 Menu 40 Felica Viewer 111 Application 112 Contactless Card Function

Claims (7)

A terminal main body, a terminal operating system that operates various functions used in the terminal main body, and a non-contact card that has an area corresponding to a plurality of categories and stores content for non-contact card functions in association with the category Storage means, contactless card function control means for performing control for using the contactless card function content using the various functions, and contactless card function storage stored in the contactless card storage means And a display means for displaying the content in association with the category . 2. The mobile terminal device according to claim 1 , wherein the contactless card function control means has an association table associating the contactless card function content with an application that provides the contactless card function content. . The related table has a deletion URL for each contactless card function content used when deleting the contactless card function content, and the contactless card function control means uses the viewer function. 3. The mobile terminal device according to claim 2 , wherein a request is made to the deletion URL when the contactless card function content is deleted on the display screen. The contactless card function control means updates the contactless card function content in the related table when new contactless card function content is added to the contactless card storage means. The mobile terminal device according to claim 2 or 3 . 5. The mobile terminal device according to claim 1, wherein the display means displays a remaining capacity of an area corresponding to the category in the contactless card storage means. On the display main body, a contactless card storage means for storing the contactless card function content, a display means for displaying the contactless card function content stored in the contactless card storage means, When deleting the contactless card function content, control is performed to delete the contactless card function content from the contactless card storage means and from a service provider server that provides the contactless card function content. And a contact card function control means. The contactless card function control means has an association table including a deletion URL for each contactless card function content used when deleting the contactless card function content, and the contactless card function control 7. The mobile terminal device according to claim 6, wherein said means requests said deletion URL when said display means deletes said content for contactless card function.

Images