JP2019075837A - Server device, service providing method, and program - Google Patents

Abstract

To securely provide a service that is not restricted by a platform of a terminal device.SOLUTION: A user information database stores user data for each user, and an applet database stores an applet associated with specific identification information. A communication unit receives, from the mobile terminal device, authentication information for authenticating a mobile terminal device and identification information for identifying the applet. A data management unit identifies user data associated with the authentication information from the user data stored in the user information database on the basis of the authentication information received by the communication unit. An applet management unit selects an applet associated with the identification information received by the communication unit from the applets stored in the applet database by using the user data identified by the data management unit. The present invention is applicable to, for example, an information processing system that performs proximity communication.SELECTED DRAWING: Figure 6

Description

  The present invention relates to a server device, a service providing method, and a program, and more particularly, to a server device, a service providing method, and a program that can securely provide a service that is not limited to the terminal device platform.

  In recent years, in mobile terminal devices such as mobile phones equipped with an IC (Integrated Circuit) chip that performs proximity communication by contact or non-contact, various services can be provided by executing application programs related to proximity communication. It is done.

  However, in the mobile terminal device, since there is a limit to the storage capacity of the memory for storing the application program for providing the service, there is also a limit to the service that can be provided by the mobile terminal device alone.

  Therefore, an application program related to proximity communication is stored in a storage area associated with unique identification information on the server, and when the mobile terminal device provides a service, the application program is executed on the server. A proposed system has been proposed (see, for example, Patent Document 1). As a result, services can be provided without being limited by the storage capacity of the memory in the portable terminal device.

JP 2002-354143 A

  However, in the cited document 1, the data processed by executing the application program on the server is not mentioned.

  For example, no mention is made as to whether data processed by executing an application program on the server is stored on the server. Therefore, when data processed by executing the application program is stored on the portable terminal side, the capacity of the data is limited to the storage capacity of the memory of the portable terminal.

  Further, in the cited reference 1, it is not mentioned how security for data processed by executing an application program on a server is secured.

  The present invention has been made in view of such a situation, and aims to be able to securely provide a service that is not limited to the terminal device platform.

  The server apparatus according to the present invention includes a user information database storing user data for each user, an applet database storing an applet associated with unique identification information, authentication information for authenticating the portable terminal apparatus, and Among the user data stored in the user information database based on the communication unit that receives identification information for identifying the applet from the portable terminal device, and the authentication information received by the communication unit From the applet stored in the applet database using the data management unit for specifying the user data associated with the authentication information, and the user data specified by the data management unit. The application associated with the identification information received by the communication unit; A server apparatus and a applets management unit for selecting and.

  The service providing method of the present invention receives authentication information for authenticating a mobile terminal device and identification information for identifying an applet from the mobile terminal device, and a user based on the received authentication information. Among the user data stored in the user information database storing each user data, the user data associated with the authentication information is identified, and the user data identified by the data management unit is identified. Selecting the applet associated with the received identification information from among the applets stored in an applet database storing the applet associated with the unique identification information using the applet It is a service provision method.

  A program according to the present invention receives authentication information for authenticating a portable terminal device and identification information for identifying an applet from the portable terminal device, and based on the received authentication information, the authentication information for each user is received. Among the user data stored in a user information database storing user data, the user data associated with the authentication information is identified, and the user data identified by the data management unit is used. Selecting the applet associated with the received identification information from among the applets stored in an applet database storing the applet associated with the unique identification information It is a program to be executed by a computer.

  In the present invention, the authentication information for authenticating the portable terminal device and the identification information for identifying the applet are received from the portable terminal device, and the user for each user is received based on the received authentication information. From the user data stored in the user information database storing data, the user data associated with the authentication information is identified, and the user data identified by the data management unit is used. The applet associated with the received identification information is selected from the applets stored in the applet database storing the applet associated with the unique identification information.

  According to one aspect of the present invention, it is possible to securely provide a service that is not limited to the terminal device platform.

It is a figure showing the example of composition of the 1 embodiment of the information processing system to which the present invention is applied. It is a block diagram which shows the structural example of a portable terminal device. It is a block diagram which shows the structural example of an authentication server. It is a block diagram which shows the function structural example of a portable terminal device. It is a block diagram showing an example of functional composition of an authentication server. It is a block diagram showing an example of functional composition of SA server. It is a flowchart explaining the example of the service provision process. It is a block diagram which shows the other function structural example of SA server. It is a block diagram showing an example of composition of an information processing system which performs reference or update of user data. It is a flow chart explaining an example of processing of reference or update of user data. It is a flowchart explaining the other example of processing of a reference or update of user data. It is a flowchart explaining the further another example of processing of a reference or update of user data. It is a block diagram showing an example of composition of an information processing system which provides service in which processing speed is required. It is a flowchart explaining an example of offer processing of service in which processing speed is required.

  Hereinafter, embodiments of the present invention will be described with reference to the drawings.

[Configuration example of information processing system]
FIG. 1 is a block diagram showing a configuration example of an embodiment of an information processing system to which the present invention is applied. The information processing system of FIG. 1 provides services such as an electronic money service, a ticket inspection service, an attendance management service, or a room entry management service to a user who uses the portable terminal device 11, for example.

  The portable terminal device 11 is configured as a portable electronic device such as a portable telephone or a PDA (Personal Digital Assistant), and performs near field communication (NFC) with the reader / writer 12. Proximity communication is communication in which the distance between the communicating devices is within several tens of centimeters, and the communicating devices are contactlessly performed. A server (not shown) is connected to the reader / writer 12, and the reader / writer 12 performs close proximity communication with the mobile terminal device 11 and supplies information obtained as a result to the server (not shown).

  Also, the mobile terminal device 11 performs wireless communication with a base station (not shown) to allow the authentication server 13 and the SA (Secure Application) server 14 via a network such as the Internet connected to the base station (not shown). Communicate with The authentication server 13 and the SA server 14 are connected to each other by a network such as the Internet. The authentication server 13 performs an authentication process on the mobile terminal device 11 by communicating with the mobile terminal device 11. The SA server 14 communicates with the mobile terminal device 11 and executes a program for providing a service to the user who uses the mobile terminal device 11, thereby realizing the provision of the service to the user. The mobile terminal device 11, the authentication server 13, and the SA server 14 all have a tamper resistant function, and between the mobile terminal device 11 and the authentication server 13, and the mobile terminal device 11 and the SA server 14. And mutually authenticate each other.

[Configuration Example of Mobile Terminal Device]
Next, with reference to FIG. 2, a configuration example of the mobile terminal device 11 will be described.

  In FIG. 2, a CPU (Central Processor Unit) 31 executes various processes in accordance with a program stored in a ROM (Read Only Memory) 32 or a program loaded in a RAM (Random Access Memory) 33. The RAM 33 also stores data necessary for the CPU 31 to execute various processes.

  The CPU 31, the ROM 32 and the RAM 33 are mutually connected via a bus 34. An input / output interface 35 is also connected to the bus 34.

  The input / output interface 35 includes an input unit 36 including a key, a button, a touch panel, and a microphone, a display including an LCD (Liquid Crystal Display) and an organic EL (Electro-Luminescence), and an output unit 37 including a speaker or the like. A storage unit 38 configured of a hard disk or the like, a first communication unit 39 configured of an antenna configured to perform wireless communication, and a second communication unit 40 configured of an antenna configured to perform proximity communication are connected.

  The storage unit 38 stores information unique to the mobile terminal device 11 and the like for authenticating the mobile terminal device 11.

  The first communication unit 39 performs wireless communication processing with a base station (not shown), and the second communication unit 40 performs proximity communication processing with the reader / writer 12.

  The drive 41 is also connected to the input / output interface 35 as needed, and removable media 42 made of semiconductor memory or the like are appropriately installed, and a computer program read from them is installed in the storage unit 38 as needed. Be done.

[Example of configuration of authentication server]
Next, a configuration example of the authentication server 13 will be described with reference to FIG.

  In FIG. 3, the CPU 51 executes various processes in accordance with a program stored in the ROM 52 or a program loaded into the RAM 53. The RAM 53 also stores data necessary for the CPU 51 to execute various processes.

  The CPU 51, the ROM 52, and the RAM 53 are mutually connected via a bus 54. An input / output interface 55 is also connected to the bus 54.

  The input / output interface 55 includes an input unit 56 such as a keyboard and a mouse, a display such as a CRT (Cathode Ray Tube) and an LCD, an output unit 57 such as a speaker, and a hard disk A communication unit 59 is connected, which is configured by the reference numeral 58, a modem, a terminal adapter and the like.

  The communication unit 59 performs communication processing via a network such as the Internet.

  The drive 60 is also connected to the input / output interface 55 as necessary, and removable media 61 including a magnetic disk, an optical disk, a magneto-optical disk, or a semiconductor memory are appropriately attached, and a computer program read from them is , And installed in the storage unit 58 as necessary.

  The configuration of the SA server 14 is the same as that of the authentication server 13 described with reference to FIG.

[Example of Functional Configuration of Mobile Terminal Device]
Next, with reference to FIG. 4, an example of a functional configuration of the mobile terminal device 11 will be described.

  The mobile terminal device 11 of FIG. 4 includes a device driver 71, a virtual machine 72, middleware 73, a VSE applet 74, a communication unit 75, a secure element 76, and a CLF (Contactless Frontend) 77. The device driver 71, the virtual machine 72, the middleware 73, and the VSE applet 74 surrounded by a broken line in the portable terminal device 11 of FIG. 4 are realized by the CPU 31 (FIG. 2). It is assumed that the hierarchy is shown.

  The device driver 71 controls devices such as the communication unit 75, the secure element 76, and the CLF 77.

  The virtual machine 72 is configured, for example, as a process virtual machine such as a Dalvik virtual machine.

  The middleware 73 includes an API (Application Program Interface), and provides the VSE applet 74 with a function related to predetermined communication. For example, the middleware 73 provides the VSE applet 74 with a function for accessing the secure element 76 and a function related to communication via the communication unit 75 or the CLF 77. Note that a part or all of the middleware 73 may exist in the hierarchy between the device driver 71 and the virtual machine 72.

  A VSE (Virtual Secure Element) applet 74 is, for example, an application program operating on the virtual machine 72, and when the mobile terminal device 11 is operated by the user, processing corresponding to the operation is executed. Specifically, the VSE applet 74 executes processing related to communication between the reader / writer 12 and the SA server 14 according to the result of the authentication of the mobile terminal device 11.

  The communication unit 75 corresponds to the first communication unit 39 in FIG. 2 and communicates with the authentication server 13 and the SA server 14 by wireless communication with a base station (not shown).

  The secure element 76 stores secure data when an application program involved in close proximity communication with the reader / writer 12 is executed. The secure element 76 is assigned a secure ID which is information unique to the portable terminal device 11. In the prior art, the secure element stores an applet as an application program that is executed to provide a service such as an electronic money service, and persistent user data to be described later. In the information processing system, applets and user data are stored in the SA server 14.

  The CLF 77 corresponds to the second communication unit 40 in FIG. 2 and includes an antenna for performing near-field communication with the reader / writer 12 and a control unit for controlling near-field communication, and performs near-field communication with the reader / writer 12.

[Example of functional configuration of authentication server]
Next, with reference to FIG. 5, an example of a functional configuration of the authentication server 13 will be described.

  The authentication server 13 of FIG. 5 includes a communication unit 91 and an authentication processing unit 92.

  The communication unit 91 corresponds to the communication unit 59 in FIG. 3 and communicates with the mobile terminal device 11 and the SA server 14 via a network such as the Internet.

  The authentication processing unit 92 authenticates the portable terminal device 11 based on authentication information (for example, secure ID) for authenticating the portable terminal device 11 supplied from the portable terminal device 11 via the communication unit 91. . When the authentication processing unit 92 normally authenticates the mobile terminal device 11, the authentication processing unit 92 supplies access information for accessing the SA server 14 to the mobile terminal device 11 via the communication unit 91.

[Example of functional configuration of SA server]
Next, referring to FIG. 6, an example of the functional configuration of the SA server 14 will be described.

  The SA server 14 in FIG. 6 includes a communication unit 111, an operating system 112, an applet DB (Data Base) 114, and a personalized DB 115.

  The communication unit 111 communicates with the portable terminal device 11 and the authentication server 13 via a network such as the Internet (not shown).

  The operating system 112 manages and controls the entire SA server 14. The operating system 112 includes a data management unit 112 a and an applet management unit 112 b.

  The data management unit 112a functions as a file system, and manages data (hereinafter referred to as user data) stored in the personalized DB 113. The data management unit 112 a selects user data stored in the personalized DB 113 based on the authentication information (secure ID) of the mobile terminal device 11 supplied from the mobile terminal device 11 via the communication unit 111. , Identify user data associated with the authentication information.

  The applet management unit 112 b manages applets (application programs) stored in the applet DB 114. The applet management unit 112 b is an applet corresponding to the identification information among the applets stored in the applet DB 114 based on the identification information for identifying the applet, which is supplied from the portable terminal device 11 through the communication unit 111. Select and start (execute).

  The personalized DB 113 has a storage area for each piece of authentication information unique to the mobile terminal device 11 (that is, for each user), and stores user data associated with the authentication information in each storage area. In the personalized DB 113, user data stored in a storage area for each user is regarded as persistent data.

  The applet DB 114 stores applets executed to provide services such as electronic money service to the user of the portable terminal device 11. Applet-specific identification information is associated with the applet stored in the applet DB 114. The applet stored in the applet DB 114 is activated by transmission of identification information unique to the applet from the portable terminal device 11. Note that in the applet DB 114, for example, each applet is registered in advance for each content provider that provides the applet.

  The applet DB 114 stores, for example, an applet having a function such as FeliCa (trademark) OS. In general, FeliCa OS executes processing related to services such as electronic money service, and an electronic device equipped with FeliCa OS is used for commerce as a substitute for a credit card, a prepaid card or the like. The applet management unit 112 b of the operating system 112 starts the noncontact or contact IC card applet such as FeliCa OS originally installed in the portable terminal device 11 in the SA server 14 to allow the portable terminal device 11 to communicate with the portable terminal device 11. The service such as the electronic money service is provided to the user of the portable terminal device 11 by communication.

  In this manner, an applet for executing a service related to the near field communication with the reader / writer 12 which has conventionally been activated on the portable terminal device 11 is activated on the SA server 14.

[About user registration]
Here, user registration by the mobile terminal device 11 will be described.

  First, in the mobile terminal device 11, a user registration screen for performing user registration for using an applet provided by a content provider is displayed on the Web browser by a user operation, and in conjunction with this, the VSE applet 74 is activated. Then, the VSE applet 74 connects the portable terminal device 11 and the authentication server 13. Then, the authentication processing unit 92 of the authentication server 13 authenticates the portable element 11 by authenticating the secure element 76 via the VSE applet 74. When the portable terminal device 11 is successfully authenticated, the authentication server 13 acquires the secure ID stored in the secure element 76 via the VSE applet 74. Specifically, the VSE applet 74 accesses the secure element 76, acquires a secure ID, and transmits the acquired secure ID to the authentication server 13 via the communication unit 75 as authentication information of the mobile terminal device 11 (see FIG. Supply).

  The authentication server 13 transmits (supplies) the acquired secure ID to the SA server 14. In the SA server 14, the operating system 112 stores the secure ID from the authentication server 13 in a storage unit (not shown). User registration is performed. At this time, individual information (personalized data) such as the user's membership number and name required by the content provider is also stored together with the secure ID. Further, in the SA server 14, the data management unit 112a secures a storage area corresponding to the secure ID in the personalized DB 113, and generates a data area used for the user registered applet in the storage area in the storage area. Set initial values for data (user data).

  The user registration is performed via the VSE applet 74. However, the present invention is not limited thereto. For example, the content provider (CP) can respond to the user's operation on the user registration screen displayed on the web browser. It may be performed via the owning CP server.

[About an example of service provision processing]
Next, with reference to the flowchart of FIG. 7, an example of service provision processing by activating the applet stored in the SA server 14 as described above will be described.

  At this time, the user brings the portable terminal device 11 and the reader / writer 12 into proximity communication by bringing the portable terminal device 11 owned by the user into proximity with the reader / writer 12, and is attempting to receive a desired service.

  In the mobile terminal device 11, for example, when the icon of the VSE applet 74 displayed on the display screen is tapped by the user, in step S11, the mobile terminal device 11 starts the VSE applet 74, and the VSE applet 74 is activated. Connects the portable terminal device 11 and the authentication server 13 (step S12 and step S31). In step S 32, the authentication processing unit 92 of the authentication server 13 authenticates the mobile element 11 by authenticating the secure element 76 via the VSE applet 74. When the portable terminal device 11 is successfully authenticated, the VSE applet 74 accesses the secure element 76 to obtain a secure ID.

  In step S13, the VSE applet 74 transmits (supplies) the acquired secure ID to the authentication server 13 via the communication unit 75, a base station, and a network such as the Internet.

  In step S33, the communication unit 91 of the authentication server 13 receives the secure ID transmitted from the mobile terminal device 11 via the network such as the Internet, and supplies the secure ID to the authentication processing unit 92.

  In step S33, when the secure ID from the communication unit 91 is supplied to the authentication processing unit 92, the authentication processing unit 92 is access information for the portable terminal device 11 to access the SA server 14, and is only once. Issue one-time URL (Uniform Resource Locator), which is valid access information. The access information for the portable terminal device 11 to access the SA server 14 is not limited to the one-time URL, but may be other information.

  In step S34, the communication unit 91 of the authentication server 13 transmits the one-time URL issued by the authentication processing unit 92 to the VSE applet 74 via the network such as the Internet and the base station.

  In step S14, when the VSE applet 74 receives the one-time URL from the authentication server 13, in step S15, the VSE applet 74 transmits a connection request to the SA server 14 based on the one-time URL. The connection request includes a secure ID.

  In step S51, the communication unit 111 of the SA server 14 receives the connection request from the VSE applet 74. When the operating system 112 confirms that the user is a registered user based on the secure ID included in the connection request from the VSE applet 74, the communication unit 111 responds to the connection request in step S52 by the VSE applet 74. Send to The VSE applet 74 receives a response from the SA server 14 in step S16. Thereby, the connection between the VSE applet 74 (portable terminal device 11) and the SA server 14 is established.

  Thereafter, in step S53, the operating system 112 of the SA server 14 enters an applet activation standby state (standby state).

  In step S17, the VSE applet 74 activates the portable terminal device 11. More specifically, the VSE applet 74 changes the display color on the display screen of the mobile terminal device 11 and puts the CLF 77 in a standby state for proximity communication.

  As described above, the display color of the display screen of the portable terminal device 11 is changed, so that the user recognizes that the portable terminal device 11 is in a state capable of proximity communication, and the reader / writer 12 uses the portable terminal device 11. Make it close.

  In a state in which the portable terminal device 11 and the reader / writer 12 are in proximity to each other, the reader / writer 12 transmits a polling command (hereinafter, simply referred to as polling) to the CLF 77 in step S71. When the CLF 77 receives the polling from the reader / writer 12 in step S91, the CLF 77 transmits a response to the polling to the reader / writer 12 in step S92. In step S72, the reader / writer 12 receives a response from the CLF 77. In this manner, the reader / writer 12 captures the portable terminal device 11 as a communication partner by transmitting polling.

  Here, the communication protocol of the near field communication performed between the mobile terminal device 11 and the reader / writer 12 is a Type A method or a Type B method standardized by ISO 14443. As a general-purpose command format in these communication protocols (communication methods), there is a command format called Application Protocol Data Unit (APDU) defined in ISO 7816-4. The commands conforming to the APDU command format are hereinafter referred to as APDU commands.

  Returning to the explanation of FIG. 7, after the processing of steps S71 and S72 and steps S91 and S92, communication of Type A method or Type B method is repeated between the portable terminal device 11 and the reader / writer 12, and ISO When communication by 14443-3 is performed, in step S73, the reader / writer 12 transmits select (AID) which is a command for selecting and activating an applet (application) in the APDU command to the CLF 77. .

  Here, AID (Application Identifier) is identification information for identifying an applet defined in ISO 7816-5, and is uniquely assigned to the applet.

  In step S 93, when the CLF 77 receives select (AID) from the reader / writer 12, the CLF 77 supplies the received select (AID) to the VSE applet 74.

  In step S18, when the VSE applet 74 receives select (AID) from the CLF 77, the VSE applet 74 transmits the received select (AID) to the SA server 14.

  The communication protocol for communication performed between the VSE applet 74 (mobile terminal device 11) and the SA server 14 is HTTP (Hyper Text Transfer Protocol) or HTTPS (Hyper Text Transfer Protocol Secure), which has a higher security level than HTTP. Specifically, for example, Thin Client Application Protocol (TCAP) is used. TCAP is a communication protocol for operating FeliCa-compatible mobile phones and reader / writers from the application of a FeliCa-compatible server via a network, and is used for electronic payment and the like. The communication protocol between the mobile terminal device 11 and the SA server 14 is not limited to HTTP and HTTPS, and may be TCP / IP (Transmission Control Protocol / Internet Protocol).

  In step S 54, the communication unit 111 of the SA server 14 receives select (AID) from the VSE applet 74 and supplies it to the operating system 112.

  In step S55, the data management unit 112a of the operating system 112 is in the storage area corresponding to the secure ID of the personalized DB 113 based on the secure ID received in step S51 and the select (AID) from the VSE applet 74. Among the user data, the user data of the data area used for the applet identified by the AID of select (AID) is specified.

  In step S56, the applet management unit 112b of the operating system 112 selects an applet corresponding to the AID of select (AID) from the VSE applet 74 from the applet DB 114, using the user data specified by the data management unit 112a. ,to start.

  In step S57, the operating system 112 supplies a response to select (AID) to the communication unit 111, and causes the VSE applet 74 to transmit the response using TCAP.

  In step S19, when the VSE applet 74 receives a response to select (AID) from the SA server 14, the VSE applet 74 transmits a response to the received select (AID) to the CLF 77.

  In step S94, when the CLF 77 receives the response from the VSE applet 74, the CLF 77 transmits the received response to the reader / writer 12. In step S74, the reader / writer 12 receives the response from the CLF 77.

  After step S74, the reader / writer 12 transmits an APDU command such as an authentication request command, a READ command (reference command), a WRITE command (update command), etc. to the CLF 77. The CLF 77 supplies the APDU command from the reader / writer 12 to the VSE applet 74, and the VSE applet 74 transmits the APDU command to the SA server 14. The SA server 14 executes processing in accordance with the transmitted APDU command, and transmits a response (processing result) to the VSE applet 74. The VSE applet 74 supplies the response transmitted from the SA server 14 to the CLF 77, and the CLF 77 transmits the response to the reader / writer 12.

  As described above, the mobile terminal device 11 (VSE applet 74) behaves like a gateway, whereby an APDU command is transmitted and received between the reader / writer 12 and the SA server 14, and the applet is executed on the SA server 14. Then, the service is provided to the user of the mobile terminal device 11.

  At this time, in the same manner as the user enjoys the service executed by the applet on the portable terminal device 11 by causing the portable terminal device 11 and the reader / writer 12 to perform close proximity communication as in the conventional case, The service executed by the applet on the SA server 14 can be enjoyed.

  According to the above process, the portable terminal device 11 is authenticated by the secure ID, and the reader / writer 12 performing proximity communication with the authenticated portable terminal device 11 requests the applet activation via the portable terminal device 11 via the mobile terminal device 11. The user data is transmitted to the SA server 14 and user data corresponding to the secure ID and used for the applet requested to be activated is specified, and the applet is activated using the user data. As described above, since user data is stored on the SA server 14 and applets are executed, there is no need to store user data or execute applets on the portable terminal device 11. It is possible to provide the user with a service related to the near field communication without being dependent on the processing capability of the mobile terminal device 11 or being limited by the storage capacity of the memory. Moreover, since user data is managed by secure ID which is the authentication information of the portable terminal device 11, security of user data can be ensured sufficiently. Therefore, it is possible to securely provide a service not limited to the terminal device.

  In addition, when user data is stored on the mobile terminal device 11, the storage area of user data used for applets provided by the content provider (CP) is also limited due to the limitation of the storage capacity, but a large amount of Since user data is stored in the secure SA server 14, it is possible to flexibly allocate the storage area of user data used for each applet, and provide a fair system to the content provider (CP). Will be able to

  Furthermore, in the conventional system, it is not easy to manage the log (transaction log) of proximity communication of the portable terminal device 11 collectively, but in the configuration described above, the transaction log consists of the reader / writer 12 and the SA server Since this is equal to the log of communication between the server and the transaction log, the transaction log can be easily and collectively managed by the SA server. As a result, it is possible for the SA server 14 side to grasp what kind of service the user using the portable terminal device 11 has enjoyed, etc., for example, to be able to provide a service that better meets the user's preference. become.

  Although the authentication server 13 and the SA server 14 are separately configured in the above, they may be integrally configured as shown in FIG.

  FIG. 8 is a block diagram showing an example of the functional configuration of the SA server 14 in which the function of the authentication server 13 is included. In the SA server 14 of FIG. 8, the same name and the same reference numeral are attached to the configuration having the same function as that provided to the SA server 14 of FIG. 6, and the description thereof will be appropriately omitted. I assume.

  That is, the SA server 14 of FIG. 8 differs from the SA server 14 of FIG. 6 in that an authentication processing unit 131 is newly provided. In addition, since the authentication processing unit 131 has the same function as the authentication processing unit 92 in the authentication server 13 of FIG. 5, the description thereof will be omitted.

  In the case of the configuration of the SA server 14 shown in FIG. 8, in the processing described in the flowchart of FIG. 7, the SA server 14 does not have to transmit the onetime URL to the VSE applet 74 after authentication of the VSE applet 74. .

  By the way, as described above, since the user data is managed by the SA server 14 side, the user may refer to or update the user data as well as the content provider.

  In the following, the configuration of the information processing system in which the user or the content provider can refer to or update the user data of the SA server 14 will be described.

[Configuration Example of Information Processing System for Referencing or Updating User Data]
FIG. 9 shows a configuration example of an information processing system in which the user or the content provider can refer to or update the user data of the SA server 14.

  In the information processing system of FIG. 9, the same name and the same reference numeral are attached to the configuration having the same function as that provided in the information processing system of FIG. 1, and the description thereof will be appropriately omitted. I assume.

  That is, the information processing system of FIG. 9 differs from the information processing system of FIG. 1 in that the reader / writer 12 is deleted and a CP (content provider) server 151 is newly provided.

  The mobile terminal device 11 communicates with the authentication server 13 and the SA server 14 through a network such as the Internet connected to a base station (not shown) by performing wireless communication with a base station (not shown). And communicate with the CP server 151. The authentication server 13, the SA server 14, and the CP server 151 are connected to one another by a network such as the Internet.

  The CP server 151 provides the mobile terminal device 11 with predetermined content in response to a request from the mobile terminal device 11. Further, the CP server 151 issues a permit for enabling access to the SA server 14 and transmits the permit to the mobile terminal device 11 or the authentication server 13. The CP server 151 can access the SA server 14 by authenticating the permit by the mobile terminal device 11 or the authentication server 13.

  The process of referring to or updating user data in the information processing system of FIG. 9 will be described below.

[Example 1 of processing of reference or update of user data]
First, with reference to the flowchart in FIG. 10, a process in which the user of the mobile terminal device 11 refers to or updates user data of the SA server 14 via the CP server 151 will be described.

  First, when the user operates the content request to the CP server 151 in the web browser of the portable terminal device 11, the CP server 151 sends the web page corresponding to the request to the portable terminal device 11 in step S111. Send.

  The portable terminal device 11 receives the web page from the CP server 151 in step S131, and displays it on the web browser in step S132.

  For the web page displayed on the web browser of the portable terminal device 11, the user presses an activation link button for activating the VSE applet 74, and the operation for activating the VSE applet 74 is performed. Then, the portable terminal device 11 activates the VSE applet 74 in step S133. Thereafter, in the portable terminal device 11, the VSE applet 74 functions as a plug-in on the web browser.

  Thereafter, when the VSE applet 74 acquires the URL of the CP server 151 for accessing the CP server 151 from the web browser, the VSE applet 74 permits the CP server 151 to access the SA server 14 in step S134. Request (permission request) is sent to the CP server 151. The URL of the CP server 151 is stored, for example, in a launch link button for launching the VSE applet 74 of the web page displayed on the web browser.

  When the CP server 151 receives the permit request from the VSE applet 74 in step S112, the CP server 151 issues a permit for enabling access to the SA server 14. In step S113, the permit is transmitted to the portable terminal device Send to 11 The permit may be stored in advance in the CP server 151.

  When the portable terminal device 11 receives the permit from the CP server 151 in step S135, the portable terminal device 11 authenticates the received permit in step S136. When the permit is successfully authenticated, the VSE applet 74 of the mobile terminal device 11 connects the mobile terminal device 11 and the authentication server 13 (steps S137 and S151). In step S152, the authentication processing unit 92 of the authentication server 13 authenticates the mobile element 11 by authenticating the secure element 76 via the VSE applet 74. When the portable terminal device 11 is successfully authenticated, the VSE applet 74 accesses the secure element 76 to acquire a secure ID, and transmits the acquired secure ID to the authentication server 13 in step S138.

  In step S153, the communication unit 91 of the authentication server 13 receives the secure ID transmitted from the mobile terminal device 11, and supplies the secure ID to the authentication processing unit 92.

  In step S153, when the secure ID from the communication unit 91 is supplied to the authentication processing unit 92, the authentication processing unit 92 issues a one-time URL.

  In step S154, the communication unit 91 of the authentication server 13 transmits the one-time URL issued by the authentication processing unit 92 to the mobile terminal device 11.

  In step S139, when the VSE applet 74 of the portable terminal device 11 receives the one-time URL from the authentication server 13, in step S140, the VSE applet 74 transmits a connection request to the SA server 14 based on the one-time URL. The connection request includes a secure ID.

  In step S171, the communication unit 111 of the SA server 14 receives the connection request from the VSE applet 74. When the operating system 112 confirms that the user is a registered user based on the secure ID included in the connection request from the VSE applet 74, in step S172, the communication unit 111 responds to the connection request as a portable terminal device. Send to 11

  In step S 141, upon receiving the response from the SA server 14, the VSE applet 74 of the mobile terminal device 11 transmits the response to the CP server 151. In step S114, the CP server 151 receives the response from the VSE applet 74. Thereby, the connection between the CP server 151 and the SA server 14 via the mobile terminal device 11 is established.

  Here, when an operation for referring to or updating user data is performed by the user with respect to the web page displayed on the web browser of the portable terminal device 11, the CP server 151 determines that the user is the user in step S115. A request command for requesting reference or update of data is transmitted to the mobile terminal device 11. The request command includes an AID that identifies an applet for which user data to be referenced or updated is used.

  In step S142, the mobile terminal device 11 receives the request command from the CP server 151, and transmits the request command to the SA server 14 using TCAP. At this time, the request ID includes the secure ID of the mobile terminal device 11.

  In step S173, upon receiving the request command from the portable terminal device 11, the SA server 14 refers to or updates the user data specified by the secure ID and AID included in the request command in step S174.

  In step S175, the SA server 14 transmits a response to the request command to the mobile terminal device 11 using TCAP.

  In step S143, upon receiving the response from the SA server 14, the mobile terminal device 11 transmits the received response to the CP server 151.

  In step S116, when the CP server 151 receives a response from the portable terminal device 11, the CP server 151 transmits the content corresponding to the response as a Web page to the portable terminal device 11.

  The request command transmitted by the CP server 151 is a READ command (reference command) or a WRITE command (update command). More specifically, when the user of the mobile terminal device 11 requests reference to user data, the CP server 151 transmits a READ command, and the SA server 14 transmits a response to the READ command. In addition, when the user of the mobile terminal device 11 requests updating of user data, the CP server 151 requests reference to user data, and after receiving a response, transmits a WRITE command, and the SA server 14 WRITE Send a response to a command.

  In the mobile terminal device 11, the VSE applet 74 executes processing corresponding to the command from the CP server 151 like a script. Here, the command transmitted and received between the mobile terminal device 11 and the SA server 14 needs to conform to the APDU command format, but the command transmitted and received between the mobile terminal device 11 and the CP server 151 Is not this limitation.

  As described above, the user of the mobile terminal device 11 can refer to or update the user data of the SA server 14 via the CP server 151.

  In the above, the CP server 151 transmits the request command to the SA server 14 via the mobile terminal device 11. However, the CP server 151 transmits the request command directly to the SA server 14 It is also good.

[Example 2 of processing of referring or updating user data]
Here, referring to the flowchart of FIG. 11, the CP server 151 directly transmits a request command to the SA server 14, whereby the user of the portable terminal device 11 refers to user data of the SA server 14 via the CP server 151. Or, the process of updating will be described.

  In the flowchart of FIG. 11, the processing of steps S211 to S213 by the CP server 151, the steps S231 to S238 of the portable terminal device 11, and the steps S251 to S254 of the authentication server 13 are performed by the CP server 151 in the flowchart of Steps S111 to S113, steps S131 to S138 by the portable terminal device 11, and steps S151 to S154 by the authentication server 13 are the same as the steps S111 to S113.

  That is, when the VSE applet 74 of the mobile terminal device 11 receives the one-time URL from the authentication server 13 in step S239, the VSE applet 74 transmits the secure ID acquired from the secure element to the CP server 151 together with the one-time URL.

  When the CP server 151 receives the one-time URL and the secure ID from the portable terminal 11 in step S214, the CP server 151 transmits a connection request to the SA server 14 based on the one-time URL in step S215. The connection request includes a secure ID.

  In step S 271, the communication unit 111 of the SA server 14 receives a connection request from the CP server 151. When the operating system 112 authenticates the CP server 151 based on the secure ID included in the connection request from the CP server 151, the communication unit 111 transmits a response to the connection request to the CP server 151 in step S272. In step S216, the CP server 151 receives a response from the VSE applet 74. Thereby, the connection between the CP server 151 and the SA server 14 is established.

  Here, when an operation for referring to or updating user data is performed by the user with respect to the web page displayed on the web browser of the portable terminal device 11, the CP server 151 displays the user in step S217. A request command requesting data reference or update is sent to the SA server 14 using TCAP. The request command includes the secure ID of the mobile terminal device 11 and an AID for identifying an applet in which the user data to be referenced or updated is used.

  When the SA server 14 receives the request command from the CP server 151 in step S273, it refers or updates user data specified by the secure ID and AID included in the request command in step S274.

  In step S275, the SA server 14 transmits a response to the request command to the CP server 151 using TCAP.

  In step S218, when the CP server 151 receives a response to the request command from the SA server 14, the CP server 151 transmits the content corresponding to the response as a Web page to the portable terminal device 11.

  The command transmitted and received between the CP server 151 and the SA server 14 conforms to the APDU command format.

  As described above, even when the CP server 151 directly transmits the request command to the SA server 14, the user of the mobile terminal device 11 refers to or updates the user data of the SA server 14 via the CP server 151. You will be able to

  Although the process in the case where the user of the portable terminal device 11 refers to or updates the user data of the SA server 14 via the CP server 151 has been described above, the CP (content provider) possessing the CP server 151 The user data of the SA server 14 can also be referenced or updated.

[Example 3 of processing of reference or update of user data]
Here, with reference to the flowchart of FIG. 12, a process in which the CP owning the CP server 151 refers to or updates user data of the SA server 14 will be described.

  When the CP server 151 and the authentication server 13 are connected, the authentication server 13 transmits a permit request to the CP server 151 in step S331.

  When the CP server 151 receives the permit request from the authentication server 13 in step S311, the CP server 151 issues a permit for accessing the SA server 14, and transmits the permit to the authentication server 13 in step S312.

  When the authentication server 13 receives the permit from the CP server 151 in step S332, the authentication server 13 authenticates the received permit in step S333. When the permit is successfully authenticated, the authentication processing unit 92 of the authentication server 13 issues a one-time URL.

  In step S334, the communication unit 91 of the authentication server 13 transmits the one-time URL issued by the authentication processing unit 92 to the CP server 151.

  In step S313, when the CP server 151 receives the one-time URL from the authentication server 13, in step S314, the CP server 151 transmits a connection request to the SA server 14 based on the one-time URL.

  When the communication unit 111 of the SA server 14 receives the connection request from the CP server 151 in step S351, the communication unit 111 transmits a response to the connection request to the CP server 151 in step S352. In step S315, the CP server 151 receives a response from the SA server. Thereby, the connection between the CP server 151 and the SA server 14 is established.

  Here, when the CP server 151 is operated by the CP to refer to or update user data used for a particular applet, the CP server 151 refers to or updates the user data in step S316. Is sent to the SA server 14 using TCAP. The request command contains an AID that identifies a particular applet.

  When receiving the request command from the CP server 151 in step S353, the SA server 14 refers to or updates the user data specified by the AID included in the request command in step S354. The user data referred to or updated here may be used for a specific applet, and user data corresponding to a plurality of secure IDs (a plurality of mobile terminal devices 11, ie a plurality of users) is referred or updated. Become so.

  In step S355, the SA server 14 transmits a response to the request command to the CP server 151 using TCAP.

  In step S317, when the CP server 151 receives a response to the request command from the portable terminal device 11, the CP server 151 outputs the content corresponding to the response to a display unit or the like (not shown) of the CP server 151.

  As described above, the content provider who owns the CP server 151 can directly reference or update the user data of the SA server 14. As a result, the content provider can easily grasp the user data stored in the portable terminal device 11 conventionally owned by each user, so for example, based on the statistics of the user data Services can be provided, and user data can be shared with other content providers to broaden the range of services.

  In the above, the information processing system of FIG. 1 can provide, for example, services such as an electronic money service, a ticket inspection service, an attendance management service, or an entry management service to a user who uses the portable terminal device 11. It has been explained.

  However, in the process described with reference to FIG. 7, it takes a certain amount of time until the request from the reader / writer 12 is sent to the SA server 14 and the response is received by the reader / writer 12. Can not provide the required service.

  Therefore, in the following, configurations and processes that can provide services that require processing speed will be described.

[Another configuration example of the information processing system]
FIG. 13 is a block diagram of an information processing system in which a ticket inspection service at a railway station is provided to a user who uses the portable terminal device 11, in particular.

  In the information processing system of FIG. 13, the same name and the same reference numeral are attached to the configuration having the same function as that provided in the information processing system of FIG. 1, and the description thereof will be appropriately omitted. I assume.

  That is, the information processing system of FIG. 13 differs from the information processing system of FIG. 1 in that the authentication server 13 is deleted and a station server 171 is newly provided.

  In addition, the reader-writer 12 is comprised as a part of station services, such as an automatic ticket gate in a railway station, and is connected to the station server 171. As shown in FIG.

  The station server 171 manages information obtained by processing in the station service including the reader / writer 12 and supplies the information to the SA server 14 as necessary. The SA server 14 and the station server 171 are connected to each other by a network such as the Internet or an intranet.

  In addition, the SA server 14 includes the function of the authentication server 13 and is the SA server 14 described with reference to FIG.

[On an example of processing for providing service that requires processing speed]
Next, an example of service provision processing by the information processing system of FIG. 13 will be described with reference to the flowchart of FIG.

  First, in the mobile terminal device 11, for example, when the icon of the VSE applet 74 displayed on the display screen is tapped by the user, in step S411, the mobile terminal device 11 starts up the VSE applet 74 and performs VSE. The applet 74 connects the portable terminal device 11 and the SA server 14 (steps S412 and S431). In step S432, the authentication processing unit 131 of the SA server 14 authenticates the mobile element 11 by authenticating the secure element 76 via the VSE applet 74. When the portable terminal device 11 is successfully authenticated, the VSE applet 74 accesses the secure element 76 to obtain a secure ID.

  In step S413, the VSE applet 74 transmits (supplies) the acquired secure ID to the SA server 14 via the communication unit 75, a base station, and a network such as the Internet, and user data corresponding to the secure ID. Send a request for

  In step S 433, the communication unit 111 of the SA server 14 receives the secure ID transmitted from the mobile terminal device 11 via the network such as the Internet, and supplies the secure ID to the operating system 112.

  In step S434, in response to the request for user data corresponding to the secure ID, the data management unit 112a of the operating system 112 specifies the user data corresponding to the secure ID in the personalized DB 113, and copies the user data (copy ) To the communication unit 111. Here, the data management unit 112a encrypts the copy of the user data with a signature. In addition, the data management unit 112a may add time information (time stamp) indicating the time at that time to the user data of the identified personalized DB 113 and the copy of the user data.

  In step S434, the communication unit 111 transmits a copy of the user data identified by the data management unit 112a to the VSE applet 74.

  In step S 414, upon receiving the copy of the user data from the SA server 14, the VSE applet 74 supplies the copy of the user data to the middleware 73. In step S451, the middleware 73 acquires a copy of the user data from the VSE applet 74, and caches it in a storage area (not shown) in step S452.

  Here, in the mobile terminal device 11, a copy of user data may be temporarily stored in a storage area (not shown) or is stored as persistent data, and a copy of new user data is stored from the SA server 14. The permanent data may be updated each time it is sent.

  In addition, in step S415, the VSE applet 74 activates the portable terminal device 11. More specifically, the VSE applet 74 changes the display color on the display screen of the mobile terminal device 11 and puts the CLF 77 in a standby state for proximity communication.

  As described above, the display color of the display screen of the portable terminal device 11 is changed, so that the user recognizes that the portable terminal device 11 can be in the close proximity communication state, and is configured as a part of the automatic ticket gate. The mobile terminal device 11 is turned (proximized) to the reader / writer 12.

  When the portable terminal device 11 and the reader / writer 12 approach each other, although not shown, the reader / writer 12 transmits a polling to the CLF 77, and the CLF 77 returns the response to the reader / writer 12. That is, the reader / writer 12 captures the mobile terminal device 11 as a communication partner.

  Then, in step S471, the reader / writer 12 transmits a system code, which is information for identifying the system, to the CLF 77. The system code transmitted here indicates that the system in which the mobile terminal device 11 is used is a ticket gate system.

  In step S 491, upon receiving the system code from the reader / writer 12, the CLF 77 supplies the system code to the middleware 73.

  When the middleware 73 acquires the system code from the CLF 77 in step S453, the middleware 73 transitions to the emulation mode in step S454. As a result, the middleware 73 executes processing related to the ticket processing. It is to be noted that the reader / writer 12 may transmit not the system code but information that the middleware 73 can emulate an applet that executes processing related to the ticket processing. For example, select (AID), which is one of the APDU commands described above, may be transmitted from the reader / writer 12.

  Further, although the middleware 73 emulates an applet that executes processing related to the ticket processing here, the VSE applet 74 may emulate an applet that executes processing related to the ticket processing.

  Thereafter, in step S455, the middleware 73 supplies a response to the system code to the CLF 77. In step S 492, when the CLF 77 receives a response from the middleware 73, the CLF 77 transmits the response to the reader / writer 12.

  When the reader / writer 12 receives the response from the CLF 77 in step S472, it transmits a READ request (READ command) for user data in step S473. When the CLF 77 receives the READ request from the reader / writer 12 in step S493, the CLF 77 supplies the READ request to the middleware 73.

  When the middleware 73 receives the READ request from the CLF 77 in step S456, it copies the signed user data cached in the storage area (not shown) in step S457 as a response to the READ request. Supply to CLF77.

  In step S494, when the CLF 77 receives a response (copy of user data) from the middleware 73, the CLF 77 transmits the response to the reader / writer 12.

  When the reader / writer 12 receives the response from the CLF 77 in step S474, the reader / writer 12 opens and closes the gate of the automatic ticket gate in step S475. Also, if the copy of the user data is accompanied by a signature or time information, the reader / writer 12 checks the signature or time information and, depending on the result, opens and closes the gate of the automatic ticket gate. You may

  In this way, the user of the mobile terminal device 11 can pass the gate of the automatic ticket gater by turning the mobile terminal device 11 to the reader / writer 12 as a part of the automatic ticket gate.

  In step S 476, the reader / writer 12 supplies the station server 171 with a WRITE request for user data stored in the SA server 14 based on the response (copy of user data) from the CLF 77. Here, it is assumed that the above-described signature is attached to the WRITE request.

  When the station server 171 acquires the WRITE request from the reader / writer 12 in step S511, the station server 171 transmits the WRITE request to the SA server 14 in step S512. The station server 171 transmits an authentication request to the SA server 14 before transmitting the WRITE request to the SA server 14, and transmits a WRITE request to the SA server 14 after receiving the response. May be

  When receiving the WRITE request from the station server 171 in step S435, the SA server 14 updates the user data to which the signature is attached based on the signature attached to the WRITE request in step S436. More specifically, the balance information of electronic money stored as user data in the personalized DB 113 is rewritten to balance information reduced by the boarding fare of the railway used by the user of the mobile terminal device 11. When time information is attached to the user data, the SA server 14 matches the user data based on the time indicated by the time information and the time when the WRITE request from the station server 171 is received. You may check the sex.

  According to the above process, the copy of the user data stored in the SA server 14 is cached in the portable terminal device 11, and based on the copy of the user data, the process related to the close proximity communication is not on the SA server 14 Since it is executed on the mobile terminal device 11, it is possible to provide a service that requires a processing speed such as a ticket inspection service.

  The processing from the transmission of the WRITE request by the station server 171 to the update of the user data by the SA server 14 does not have to be performed in real time, and may be performed by batch processing.

  In the above, although the authentication information of the portable terminal device 11 is the secure ID of the secure element 76, it may be any information that can securely authenticate the portable terminal device 11. For example, when the mobile terminal device 11 is a mobile phone, the telephone number may be used as authentication information, or when the mobile terminal device 11 has a biometric authentication function such as fingerprint authentication, the biometric information is used. It may be authentication information. Also, conventionally, information unique to a Universal Integrated Circuit Card (UICC) for storing an applet executed in the mobile terminal device 11 may be used as authentication information.

  Also, in the above, the close proximity communication between the mobile terminal device 11 and the reader / writer 12 is performed by Type A method or Type B method, but the Type A method or the method standardized by ISO 18092 is used. It may be made to be performed by methods other than Type B method. Furthermore, the close proximity communication between the portable terminal device 11 and the reader / writer 12 may be not contactless communication but contact communication using a terminal.

  Furthermore, although one SA server 14 is provided in the information processing system described above, an SA server may be provided for each applet (that is, for each content provider that provides an applet).

  Furthermore, although the VSE applet 74 has a plurality of functions in the above, the plurality of VSE applets 74 may have the respective functions.

  The series of processes described above can be performed by hardware or software. When a series of processes are executed by software, various functions may be executed by installing a computer in which programs constituting the software are incorporated in dedicated hardware or various programs. The program can be installed from a program storage medium, for example, on a general-purpose personal computer.

  A program recording medium for storing a program installed in a computer and made executable by the computer is, as shown in FIG. 3, a magnetic disk (including a flexible disk), an optical disk (CD-ROM (Compact Disc-Read Only) Removable media 61, which is a package medium comprising a memory (including a Digital Versatile Disc), a magneto-optical disc, or a semiconductor memory, or a ROM 52 or RAM 53 in which a program is temporarily or permanently stored. The hard disk etc. which comprise are comprised. The program is stored in the program storage medium through a communication unit such as a network, a local area network, the Internet, and a digital satellite broadcast via a communication unit (not shown), which is an interface such as a router or a modem as required It is done using.

  Furthermore, the program executed by the computer may be a program that performs processing in chronological order according to the order described in this specification, in parallel, or when necessary, such as when a call is made. It may be a program to be processed.

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

  11 mobile terminal device 12 reader writer 13 authentication server 14 SA server 74 VSE applet 75 communication unit 76 secure element 77 CLF 92 authentication processing unit 112 operating system 112a data management unit 112b applet management unit , 113 personalized DB, 114 applet DB, 131 authentication processing unit

Claims (7)

A user information database storing user data for each user;
An applet database storing applets associated with unique identification information;
A communication unit that receives authentication information for authenticating a mobile terminal device and the identification information for identifying the applet from the mobile terminal device;
A data management unit for specifying the user data associated with the authentication information from the user data stored in the user information database based on the authentication information received by the communication unit;
The applet associated with the identification information received by the communication unit is selected from the applets stored in the applet database using the user data specified by the data management unit A server apparatus comprising an applet management unit and The server apparatus according to claim 1, wherein the authentication information is biometric information transmitted from the portable terminal apparatus having a biometric authentication function. The server apparatus according to claim 1, wherein the applet database stores the applet that provides an electronic money service. The server apparatus according to claim 3, wherein the user data is balance information of electronic money. The communication unit receives a request command for requesting reference or update of the user data,
The server apparatus according to claim 1, wherein the data management unit refers to or updates the user data associated with the authentication information based on the request command received by the communication unit. Authentication information for authenticating the mobile terminal device and identification information for identifying an applet are received from the mobile terminal device,
Based on the received authentication information, the user data associated with the authentication information is specified from among the user data stored in a user information database storing user data for each user,
The specified identification information is associated with the received identification information from among the applets stored in an applet database storing the associated applet, using the identified user data A method of providing a service comprising the step of selecting the applet. Authentication information for authenticating the mobile terminal device and identification information for identifying an applet are received from the mobile terminal device,
Based on the received authentication information, the user data associated with the authentication information is specified from among the user data stored in a user information database storing user data for each user,
The specified identification information is associated with the received identification information from among the applets stored in an applet database storing the associated applet, using the identified user data A program that causes a computer to execute processing including the step of selecting the applet.

Images