Classifications

• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04M—TELEPHONIC COMMUNICATION
  • H04M1/00—Substation equipment, e.g. for use by subscribers
  • H04M1/72—Mobile telephones; Cordless telephones, i.e. devices for establishing wireless links to base stations without route selection
  • H04M1/724—User interfaces specially adapted for cordless or mobile telephones
  • H04M1/72403—User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality
  • H04M1/72406—User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality by software upgrading or downloading
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04M—TELEPHONIC COMMUNICATION
  • H04M1/00—Substation equipment, e.g. for use by subscribers
  • H04M1/72—Mobile telephones; Cordless telephones, i.e. devices for establishing wireless links to base stations without route selection
  • H04M1/724—User interfaces specially adapted for cordless or mobile telephones
  • H04M1/72403—User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality
  • H04M1/72409—User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality by interfacing with external accessories
  • H04M1/72412—User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality by interfacing with external accessories using two-way short-range wireless interfaces

Definitions

• the present invention relates to a mobile terminal device, a contactless card function management system, and a contactless force card function acquisition system, and more particularly, a mobile terminal device and a contactless card that can easily manage and acquire contactless card functions.
• the present invention relates to a function management system and a contactless card function acquisition system.
• a desired IC card function can be selected on the display screen in accordance with a user operation.
• the application corresponding to the IC card function is started to execute the IC card function.
• An object of the present invention is to provide a mobile terminal device capable of comprehensively managing content for contactless card functions and easily adding and deleting content for contactless card functions. And a contactless card function management system and a contactless card function acquisition system.
• the contactless card function can only be controlled by an application corresponding to the contactless card function. Therefore, when registering content for the contactless card function, Registration to the application corresponding to the content for contact card function is indispensable. In addition, if the application corresponding to the content for contactless card function is not registered, even if the content for contactless card function is actually stored in the mobile terminal device, the content is reflected in the list display. Can't let
• the present inventors have focused on the point of executing the contactless card function in the operation system for the contactless card function and executing other functions in the terminal operation system.
• Management of content for contactless card function, contactless card by providing a manager that can control the function and other functions (native function) installed in the mobile device, such as browser function, menu function, view function, etc.
• the addition and deletion of the function content can be performed with a simple operation, and the reader has found that the contents of the contactless card function content can be reflected in the list display, and has led to the present invention.
• the gist of the present invention is to control addition / deletion of content for contactless card function via an application for providing content for contactless card function, and to obtain external power of contactlessness.
• Contactless card for additional control of card function content By providing function control means, the content for contactless card function can be managed, and the content for contactless card function can be added and deleted with simple operation. Is reflected in the list display.
• a mobile terminal device of the present invention includes a terminal main body, a terminal operation system that operates various functions used in the terminal main body, contactless card storage means for storing content for contactless card functions, Contactless card function control means for performing control for using the content for the contactless card function using the various functions.
• 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. .
• the user can easily use the content for contactless card function, for example, on the display screen.
• a mobile terminal device includes a terminal main body, contactless card storage means for storing contactless card function content, and control for using the contactless card function content.
• the addition of the content for the contactless card function can be controlled by the reader / writer card or the like via the application or without passing through the application. You can easily delete files
• the contactless card function control means includes an association table associating the contactless card function content with an application that provides the contactless card function content. It is preferable to have.
• the association table is associated with the application that provides the contactless card function content
• the contactless card function content is managed. It becomes possible.
• the contactless card function content in the contactless card storage means can be displayed for each storage area in the storage means.
• the capacity in the content for contactless card function can be grasped for each storage area.
• the related table has a deletion URL for each contactless card function content used when deleting the contactless card function content
• the contactless card function control means preferably requests the deletion URL when deleting the contactless card function content on the display screen when the view function is used.
• the contactless card is linked at the link destination of the deletion URL without activating the content provider application that provides the content for the contactless card function. It is possible to delete functional content.
• the contactless card function control means adds the contactless card function control means to 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 contact card functions.
• the contactless card storage means has a plurality of areas for storing the contactless card function content.
• the various functions include a view eye function
• the contactless card function control means uses the view eye function and the plurality of functions in the storage means.
• the content for the contactless card function is displayed for each of the areas. It is preferable to show.
• the contactless card function control means deletes the content for the contactless card function on a display screen when the view function is used. Preferably it is done.
• a contactless card function management system is connected to the mobile terminal device and the mobile terminal device via a network, and provides a content for the contactless card function.
• the contactless card function content server for storing the obtained plurality of contactless card function contents.
• the mobile terminal device can manage the content for contactless card function, and can easily add and delete the content for contactless card function. It is possible to realize a system that can add and delete content for contactless card functions with a simple operation.
• a contactless card function acquisition system of the present invention includes a mobile terminal device, a provider server connected to the mobile terminal device via a network, and providing the contactless card function content;
• the mobile terminal device includes a terminal body, contactless card storage means for storing contactless card function content, and control for using the contactless card function content.
• the content information corresponding to the added contactless card function content is acquired from the server.
• control of addition / deletion of content for contactless card function is performed via an application that provides content for contactless card function, and a contactless card is used as an external acquisition means. Since it has a contactless card function control means for controlling the addition of functional content, it can manage the content for contactless card functions, and can easily add and delete content for contactless card functions. It can be done with simple operation.
• 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.
• 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 one embodiment of the present invention.
• FIG. 3 is a diagram showing content for a contactless card function in a common area on a display screen of a mobile terminal device.
• FIG. 4 is a diagram showing a content for a contactless card function in a public area on a display screen of a mobile terminal device.
• FIG. 5 is a diagram showing a contactless card function content in a free area on the display screen of the mobile terminal device.
• FIG. 6 is a diagram showing an internal configuration of a mobile terminal apparatus according to an embodiment of the present invention.
• FIG. 7 is a diagram showing an association table associating content for contactless card function with an application that provides the content for contactless card function.
• FIG. 8 is a diagram showing a state where one of the contents for the contactless card function in the common area is activated on the display screen of the mobile terminal device.
• FIG. 9 is a flowchart showing a procedure for deleting fertile content in the mobile terminal 11.
• FIG. 10 Sequence showing the procedure for deleting ferri-force content on the mobile terminal 11
• FIG. 11 is a sequence diagram showing a procedure for deleting fertile content for the mobile terminal 11.
• FIG. 12 is a sequence diagram showing a procedure for deleting fertile content for the mobile terminal 11.
• FIG. 13 is a sequence diagram showing a procedure for deleting fertile content for the mobile terminal 11.
• FIG. 14 is a sequence diagram showing a procedure for adding content for contactless card function via RZW in a mobile terminal device.
• FIG. 15 is a diagram showing another internal configuration of the mobile terminal device.
• FIG. 16 is a diagram showing a contactless card function content in the display screen of the mobile terminal device shown in FIG. 15.
• FIG. 17 is a diagram showing another example of a relation table associating content for contactless card function with an application that provides the content for contactless card function.
• 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, and a mobile terminal 11 connected to the mobile terminal 11.
• the Web server 15 and the contact server function content server 16 connected via a network such as the network 14 are also mainly configured.
• the mobile terminal 11 has a function capable of executing various applications 111 and a contactless card function 112.
• 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 (RZW) 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 that can add and delete content for contactless cards, such as contactless IC card functions, such as Felica (registered). Trademark).
• the mobile terminal is equipped with a storage area for storing contents and an operation 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, which has a gateway function to connect the mobile communication network 12 and the Internet 14, and specifically includes an information distribution function, a mail transmission / reception function, and a mail. It has a storage 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 a LAN and a 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 the content for each contactless card function that is also provided with a plurality of service provider capabilities that provide the content for contactless card function, and also has a controller and a network for realizing the contactless card function. Add / delete, initialize, and read / write data for contactless card function.
• the content server 16 is also equipped with an application for processing from the content server 16 to the controller that realizes the contactless card function.
• This content server may be provided on the Internet 14 by the service provider together with the Web server.
• the content server may be on a different network from the Internet 14 apart from the Web server of the service provider. For example, if the contactless card function is ferry power, the content server 16 is a ferry force server.
• the mobile terminal 11 adds the contactless card function content via an application that provides the contactless card function content.
• it also controls the tracking of content for contactless card functions acquired via RZW.
• RZW the tracking of content for contactless card functions acquired via RZW.
• the mobile terminal 11 controls the addition and deletion of the content for contactless card function via the application 111 that provides the content for contactless card function
• the mobile terminal 11 The non-contact card function 112 is accessed by an application 111 such as i- ⁇ ppli (registered trademark). Then, the content for contactless card function is added or deleted on the application 111.
• the mobile terminal 11 When the mobile terminal 11 performs additional control of the content for contactless card function via the RZW, the content for the contactless card function is added directly from the external RZW17 without going through the application 111. I do. At this time, content information corresponding to the added contactless card function content is acquired from the Web server 15.
• FIG. 2 is a diagram showing a configuration of a storage area for storing the 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 ferry force chip when the contactless card function is a ferry force.
• This storage area is composed of a common area 21, a public area 22, and a free area 23, for example. These areas are divided by, for example, the category of content for contactless card functions, the difference in service levels, and the level of security.
• the common area 21 and public area 22 are areas for storing content for contactless card functions of services with a relatively high service level and high security
• the free area 23 is a security area with a relatively low service level.
• the area for storing the content for the contactless card function of the service is also low.
• FIGS. 3 to 5 show the non-contact card function content stored in each of the common area 21, public area 22 and free area 23.
• Figure 3 shows the common area 2 on the display screen of the mobile terminal 11.
• 4 is a diagram showing the content for contactless card function 1
• FIG. 4 is a diagram showing the content for contactless card function in the public area 22 on the display screen of the mobile terminal 11
• FIG. 6 is a diagram showing a contactless card function content in a free area 23 on the display screen of the terminal 11;
• Each of the services shown in FIGS. 3 to 5 is contactless card function content provided with service pronoid capabilities.
• an indicator 24 indicating the remaining capacity of each area is displayed on the display screen.
• the remaining capacity in each area is set in advance by the number of contents that can be stored by using the indicator 24 as shown in FIGS. 3 to 5, and the set number of content display areas (in FIG. 3) 3 and 2 in FIG. 4 and 3 in FIG. 5) may be displayed, and the unused content display area may be displayed blank.
• the user can visually recognize the remaining capacity of each area in the storage area.
• the content capacity is compared with the remaining capacity of the area for storing the content, and the content capacity exceeds the remaining capacity May indicate that the capacity is insufficient or that the stored content for the contactless card function needs to be deleted.
• the user can recognize the necessity of deleting the content for the 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.
• the contactless card function is a ferriforce
• the storage area is a ferriforce chip
• the operation system (controller) for the contactless card function is a ferrica system (ferriforce OS). I will explain it.
• a terminal operation system (mobile device OS) 31 that executes various functions of the mobile terminal 11 and a ferri-force application manager (contactless card function control means) Felica Application Manager (FAM) 32, a ferri force device driver 33 that drives the ferri force OS 35 according to the control of the FAM 32, and a ferri force chip 34 that stores the ferri force content.
• FAM Felica Application Manager
• Java that manages Java (registered trademark) applications with network computing functions on this FAM32
• the application manager Java Application Manager: JAM
• the API Application Program Interface
• KVM K Virtual Machine
• Native functions such as browser 38, menu 39, and ferri force view 40 operate.
• the force that the browser 38, menu 39, and ferri force view 40 operate on the FAM32 This configuration is an example, and functions other than the ferri force view 40 such as the browser 38 and menu 39 are provided. May be configured to run on FAM32 and on mobile OS31 as well.
• Mobile device OS31 has functions other than functions related to flicker, such as information distribution function, mail transmission / reception function, mail storage function, contract customer management function, information provider management function, and information fee billing function. Execute.
• the FAM 32 is middleware that performs control for using the ferri-force content according to the present invention.
• FAM32 issues access control for easily acquiring contactless card function content from an external RZW, management of acquired ferri-force content, and commands for executing the browser 38, menu 39, and ferri-force view 40.
• the FAM 32 can manage the ferri-force content, and thus the ferri-force content can be used by using functions such as the browser 38 and the ferri force view screen 40.
• the user can easily use the fertile content, for example, display it on the display screen.
• the FAM 32 has an association table for associating ferri-force content with an application (i-appli (registered trademark)) that provides the ferri-force content in order to manage the acquired ferri-force content.
• This association table is, for example, as shown in FIG. 7, and the services 1 to 3 that are the ferric contents and the i- ⁇ ppli ⁇ to ⁇ of the service provider that provides the services 1 to 3 are associated with each other. .
• i-appli registered trademark
• the date when the content was acquired (registration date) and the date when the ferri- force content was deleted (deletion date) are also managed. Furthermore, in the related table, the URL (deletion URL) of the site that actually deletes the ferry content and the area in the ferry force chip 34 are also managed. In this way, Ferry content is managed in FAM32. It is possible to manage the contents in the ferripower chip 34 in association with each category. Therefore, when the mobile terminal 11 is equipped with the FAM 32, a plurality of ferri force contents can be classified and grouped, and display control can be performed so that the user can easily see.
• the service provider is registered in the application item, and the content is registered in the service item.
• the date of registration is registered as the registration date.
• a deletion URL that is used when deleting ferrility content is also registered.
• the related content When the related content is added through the application and the related table is updated, the content information such as the service name is acquired through the application, and the related table is created using the content information. Update.
• the ferritic content is added from the external RZW 17
• the related table when the related table is updated, for example, the content information is stored in a predetermined address of the ferritic force chip 34, and when any user operation is performed, FAM32 extracts new content information from the address and updates it to the related table. Note that there is no particular limitation on the method for updating the related table when the ferrous content is added from the external RZW17.
• the delete URL associated with the application or service corresponding to the delete ferri-force content is referred to.
• the date of the deletion is updated to the deletion date.
• this relation table is used when displaying for each area as shown in FIGS. That is, when the display shown in FIGS. 3 to 5 is performed on the ferri force view 40, the FAM 32 activates the ferri force view 40 and refers to the related table. As a result, 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 fertile content for each area.
• the FAM 32 has the related table as shown in FIG. 7, so that the Felica content can be managed.
• This makes it possible to display the ferri-force content for each region in the ferric chip 34 as shown in FIGS. 3 to 5, for example.
• the ferriforce chip 34 can be managed for each area using the related table, for example, by managing the remaining capacity for each area of the ferriforce chip 34 using the related table, the capacity in the ferriforce chip 34 can be managed for each area. It becomes possible to grasp.
• by managing the deletion URL in the related table it is possible to delete the content at the link destination of the deletion URL without starting the i-appli.
• FAM32 controls the addition / deletion of ferri-force content via an application that provides ferri-force content, that is, launches an i-appli and also controls the addition of ferric content via RZW. I do.
• an application such as an i-appli or RZW power without going through the application, the user can easily add or delete the ferri-force content. it can .
• the procedure of “addition of ferri-force content” control is performed as follows.
• FAM 32 can be used to add or delete the fiercer content on the display screen using the view function.
• a tab will appear as shown in Fig. 8, for example, "Use” Functions such as “Delete” can be selected.
• “Use” tab you can use mobile ANA's ferry power content.
• “Delete” tab you can directly delete mobile ANA's ferry content without starting i- ⁇ ppli.
• the function content displayed on the tab is not limited to the above, but can be freely set by the content provider, and in addition to the above, for example, "update”, "property”, etc. can be set .
• FIG. 9 is a flowchart showing a procedure for deleting the fertile content in the mobile terminal 11.
• FIG. 10 to FIG. 13 are sequence diagrams showing a procedure for deleting the fertile content in the mobile terminal 11.
• FIG. 14 is a sequence diagram showing a procedure for adding ferri-force content to the mobile terminal 11 via RZW.
• deletion of ferri-force content that is, deletion of ferri-force content in the IC card area of the ferric chip 34, deletion of ferric content in the application area, and ferri-force server (IP Sano) user data can be performed by a single operation by the user.
• ferri-force server IP Sano
• the user selects a service (fellow content) to be “deleted” from the “list display” on the mobile terminal 11 (S 111).
• a deletion request for the selected service is made (S112).
• the related table force in FAM32 also detects the data of this service (S113).
• the mobile terminal 11 makes a deletion request for the selected service to the IC card area in the ferripower chip 34 (S114).
• IP server Filterry Force Server
• connection to the deletion URL it is determined whether or not the connection to the deletion URL is completed (S117).
• the ferripower server IP server
• updates the data so that the user cannot use the service (i-appli deletion) S118.
• the connection to the deletion URL is not completed, a connection request is made to the deletion URL again.
• the mobile terminal 11 issues a request to delete the i-appli (S120). If the service stop processing has not been completed, a connection request is made to the deletion URL again.
• the mobile terminal 11 deletes the data of the relevant ferritic content in the related table of FAM32 (S122), and the list display data is overwritten and stored (S123). . If deletion of the i-appli has not been completed, a request to delete the i-appli is made again.
• i- ⁇ ppli deletion requires access to the ferry force server, and the error rate is high, so the ferry force content in the IC area of the ferry force chip 34 is deleted first. However, i- ⁇ ppli deletion and IC area deletion may be performed in the reverse order.
• the user selects from “list display” a service to be “deleted” from the IC menu of the mobile terminal 11 (S201).
• FAM32 selects the relevant service in the related table, 1) the request for deletion to the IC area of the ferripower chip 34, and 2) the deletion URL is referenced, and the Ferry power server corresponding to the deletion URL is referred to.
• An i-appli deletion request is made (S202).
• the ferri-force OS 35 executes the deletion of the target service for the ferri-force chip 34 (S203, S204). Then, a deletion completion report is sent from the ferry force chip 34 to the FAM 32 (S205).
• the ferry power server saves the user's use suspension data (S206). Then, the deletion completion report is sent from the Felica server to the mobile terminal 11 (S207), and the application area deletion process is performed for the i-appli (S208). Then, the deletion completion report is sent from the i-appli to FAM32 (S209).
• FAM32 since the ferri-power chip 34 and i-appli service (ferrica content) have been deleted, the data of the target service in the related table is deleted (S210). Thereafter, the information is sent to the IC menu (S211), and the list display data (IC area usage rate, service name, etc.) is overwritten (S212).
• the flica server Upon receipt of the i- ⁇ ppli deletion request (S309), the flica server stores the usage suspension data of the user (S310). Then, a deletion completion report is sent from the ferri force Sano to the mobile terminal 11 (S311), and an application area deletion process is performed in the i-appli (S312). Then, a deletion completion report is sent from the i-appli to FAM32 (S313). In FAM32, since the ferry force chip 34 and the i-appli service (ferry force content) have been deleted, the data of the target service in the related table is deleted (S314). Then, the information is sent to the IC menu (S315), and the list display data (IC area usage rate, service name, etc.) is overwritten (S316).
• the service is selected from “list display” (S401).
• FAM32 selects the relevant service in the related table, refers to 1) the request for deletion to the IC area of the ferripower chip 34, and 2) refers to the deletion URL.
• An application deletion request is made (S402).
• the ferri-force OS 35 executes deletion of the target service for the ferri-force chip 34 (S404). Then, a deletion completion report is sent to the ferri force tip 34 force FAM 32 (S405).
• the ferry power server stores the user's use cancellation data (S406). Then, a deletion completion report is sent from the flicker server to the mobile terminal 11 (S407), and an application area deletion process is performed in the i-appli (S408). If an error is detected in the i-appli at this time, error information is generated (S409), and an error report is sent to FAM32 (S410). When FAM32 receives the error report, it does not delete the target data in the related table (S411), but only makes a deletion request to the i-appli corresponding to the deletion URL again (retry) (S412). This retry is repeated until the i- ⁇ ppli delete request is sent normally. There is no particular limitation on the retry interval.
• the deletion process is executed and a deletion completion report is sent to the FAM 32 (S414).
• FAM32 the ferry force chip 34 and i- ⁇ ppli service (ferry force content) have been deleted.
• Data is deleted (S415). Thereafter, it is sent to the information power C menu (S416), and the list display data (IC area usage rate, service name, etc.) is overwritten (S417).
• the user selects a service to be “deleted” from the “list display” from the IC menu of the mobile terminal 11 (S501).
• FAM32 selects the relevant service in the related table, 1) the request for deletion to the IC area of the ferripower chip 34, and 2) the deletion URL is referenced, and the i-appli to the ferripower server corresponding to the deletion URL Delete request (S502).
• the ferry power server stores the user's usage suspension data (S503).
• deletion completion report is sent from the ferri force Sano to the mobile terminal 11 (S504), and the application area deletion process is performed in the i-appli (S505). Then, a deletion completion report is sent from the i-appli to FAM32 (S506).
• the ferri-force OS 35 executes the deletion of the target service for the ferri-force chip 34 (S507, S508). At this time, if an error is detected in the ferri force chip 34, error information is generated (S509), and an error report is sent to the FAM 32 (S510).
• FAM32 receives the error report, it does not delete the target data in the related table (S511), but only makes a deletion request to the flicker chip 34 corresponding to the deletion URL (retry) (S512). This retry is repeated until the deletion request at the flicker chip 34 is sent normally. There is no particular limitation on the retry interval.
• the ferry force chip 34 Upon receiving the deletion request (S513), the ferry force chip 34 executes the deletion processing of the IC area (S514) and reports the deletion completion to the FAM 32 (S515).
• the ferry force chip 34 and i-appli service have been deleted, the data of the target service in the related table is deleted (S516). Thereafter, the information is sent to the IC menu (S517), and the list display data (IC area usage rate, service name, etc.) is overwritten (S518).
• ferri force content is pursued to the ferri force chip 34!
• a request to refer to the related table is made from the menu to the FAM 32 (S605).
• the FAM 32 receives the request, it issues a command to the ferri force chip 34 and acquires the registration status of the ferri force content stored in the ferri force chip 34 (S606).
• the FAM 32 acquires content information such as a service name from the ferry power server (S607).
• the FAM 32 updates the content information acquired in this way to the related table (S608).
• the FAM32 responds to the menu with the storage status of the ferri content, and the menu displays the screen according to the storage status (S609).
• the fertile content can be managed by the mobile terminal 11 according to the present invention, and the addition and deletion of the fertile content can be easily performed.
• adding ferri-force content from the external RZW 17 and deleting ferri-force content on the mobile terminal 11 screen it is possible to delete additional ferri-force content.
• FIG. 15 is a diagram showing another internal configuration of the mobile terminal apparatus that does not have FAM.
• a mobile device OS 51 that performs various functions of a mobile terminal
• a ferri-force OS 54 that is an operation system for ferri-force
• a ferri-force device driver 52 that drives the ferri-force OS 54
• It has a ferri-power chip 53, which contains the content of the fierica content.
• JAM55 that manages Java (registered trademark) applications and KVM56, a device that executes APIs, and devices that execute APIs operate on OS54 and other applications such as browsers. 57 and menu 58 work.
• the Ferri force OS 54 controls the network computing related to the fibers, and the browser 57 and the menu 58 cannot be controlled. For this reason, it is not possible to display fertile content on the screen separately for each area, but simply display all the fertile content as shown in FIG.
• it since it does not have FAM, it is possible to add / delete ferrility content only via an application, and it cannot be obtained directly from an external RZW as shown in FIG. For this reason, adding / deleting ferritic content must be done by starting i- ⁇ ppli.
• control of addition / deletion of ferri-force content is performed via an application that provides ferri-force content, and an external RZW1 FAM32 that controls the addition of ferri-force content from 7 is provided, so it is possible to manage Felica content, and it is also possible to acquire ferri-force content directly from an external RZW. Adding and deleting can be done with a simple operation
• the power described for the case where the FAM function is built in the mobile terminal device is stored in the UI M card (User Identity Module). card) or SIM card (Subscriber Identity Module card), and the IC card may be detachable from the mobile terminal device.
• the portable terminal device is provided with a card slot entrance such as a slot into which an IC card can be inserted.
• the FAM function (FAM, Ferri-Force Device Dryino, Felica Chip, Ferri-Force OS) is stored in the IC card, and the IC card is stored in the IC card by inserting it into another mobile terminal device.
• Ferry content can be used on other mobile terminal devices. As a result, flicker content can be freely moved between mobile terminal devices, and the degree of freedom of using ferry content is expanded.
• FAM stores related tables used for managing various contents on IC cards, and other FAM control functions (devices, programs, applications) such as FAM, Ferry Force Device Dryino, Ferry Force Chip, Ferry Force OS, etc. Installed in mobile terminal devices. By separating the FAM function and mounting it in this way, security related to Felica content can be increased.
• an area for user authentication information (for example, user ID and password) is provided in the related table, and this table is used when the IC card is used. It is preferable to perform user authentication using related tables. For example, when an IC card storing such a related table is also taken out from the mobile terminal device and inserted into another mobile terminal device to use ferri-force content, the FAM installed in the mobile terminal device is the IC card. If an unknown user is using it, that is, if the ID is different from the ID of the local device, user authentication is performed. At this time, Prompt for user ID and password. For higher security, it is preferable to use biometrics technology such as fingerprint verification as user authentication. For example, a scanner for scanning a fingerprint image is provided in a portable terminal device, and the fingerprint image is obtained by sliding the finger or placing the finger on the scanner.
• biometrics technology such as fingerprint verification
• FIGS. 3 to 5 and 8 show the service name of the ferri-force content currently stored in its own mobile terminal and the remaining value of the storage capacity of each area.
• the screen configuration is not limited to that shown here as long as the user can easily perform processing such as “deletion”.
• the screen configuration may be such that the service names of all the areas are not displayed separately in a list for each area but are displayed in a list on one page.
• the content in the same area as the area where new content should be stored should be deleted. For example, if new content is content that is stored in the free area, and content needs to be deleted when adding this new! / ⁇ content, make it possible to delete content already stored in the free area. It is desirable to be able to delete content stored in other areas.
• the service names of all areas are listed, and only the contents that are stored in the free area on the screen are deleted.
• the present invention is not limited to the above embodiment, and can be implemented with various modifications.
• 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.
• the browser Other control means and management means that can activate the menu and ferri force view ⁇ may be used.
• the case where the contactless card function is a ferrica is described.
• the present invention is similarly applied to a case where the contactless card function is a contactless card function other than ferri-force. can do.

Landscapes

• Engineering & Computer Science (AREA)
• Human Computer Interaction (AREA)
• Computer Networks & Wireless Communication (AREA)
• Signal Processing (AREA)
• Telephone Function (AREA)
• Telephonic Communication Services (AREA)
• Mobile Radio Communication Systems (AREA)
• Management, Administration, Business Operations System, And Electronic Commerce (AREA)
• Stored Programmes (AREA)

Priority Applications (3)

Applications Claiming Priority (4)

Publications (1)

Family

ID=36000132

Family Applications (1)

Country Status (6)

Families Citing this family (33)

Citations (4)

Family Cites Families (12)

• 2005
  • 2005-04-22 JP JP2005125050A patent/JP4763332B2/ja not_active Expired - Fee Related
  • 2005-08-31 TW TW094129830A patent/TW200625981A/zh not_active IP Right Cessation
  • 2005-09-01 WO PCT/JP2005/015992 patent/WO2006025483A1/ja not_active Ceased
  • 2005-09-01 CN CN2005800371956A patent/CN101049043B/zh not_active Expired - Fee Related
  • 2005-09-01 US US11/661,953 patent/US8374647B2/en not_active Expired - Fee Related
  • 2005-09-01 EP EP05776766.7A patent/EP1786229B1/en not_active Expired - Lifetime

Patent Citations (4)

Non-Patent Citations (1)

Also Published As

Similar Documents

Legal Events