Service Management System

Abstract

Provided is a service providing method for coping with a case where a service contractor and a service user are different from each other, or a case where a service contractor and a service member are different from each other. 【Solution means】A service management system 1A includes an acquisition unit 113 that acquires a set of a contractor of a first service that requires identity verification at the time of contract and a user of the first service corresponding to the contractor, and allows the provision of a second service to the user without performing identity verification when the contractor and the user are the same person, and a service management unit 212 that does not allow the provision of the second service to the user when the contractor and the user are not the same person. The second service is a service that requires identity verification.

Description

Technical Field

[0001] The present invention relates to a service management system.

Background Art

[0002] When providing a service, if the contractor of the service and the user of the service do not match, problems may occur from the perspective of identity authentication.

[0003] Regarding identity authentication, for example, Patent Document 1 discloses a technique related to an authentication support device that enhances convenience and confidentiality in identity authentication. In this technique, a registration request acquisition unit acquires a registration request including a telephone number and a kana name. Also, an authentication processing unit refers to contractor information in which a telephone number and the kana name of the contractor corresponding to the telephone number are associated and stored in the authentication device. Further, the authentication processing unit authenticates the legitimacy of the telephone number and the user based on whether the kana name of the contractor corresponding to the telephone number included in the registration request matches the kana name included in the registration request in the contractor information.

Prior Art Documents

Patent Documents

[0004]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0005] However, in the technology according to Patent Document 1, although a comparison between the contractor and the user is made, when the contractor and the user are different, user information cannot be registered. In other words, the technology according to Patent Document 1 did not assume a case where the service contractor and the service user are different from each other and at the same time the service user is registered. Furthermore, the technology according to Patent Document 1 did not assume a case where the contractor of the first service and the member of the second service corresponding to the contractor are different from each other and at the same time the member of the second service is registered.

[0006] Therefore, the present invention can provide a method for providing a second service assuming a case where the contractor of the first service and the user of the first service are different from each other, or a case where the contractor of the first service and the member of the second service corresponding to the contractor are different from each other.

Means for Solving the Problem

[0007] A service management system according to a preferred aspect of the present invention includes an acquisition unit that acquires a pair of a contractor of a first service that requires identity verification at the time of contract and a user of the first service corresponding to the contractor, and when the contractor and the user are the same person, allows providing a second service without performing identity verification on the user, and when the contractor and the user are not the same person, does not allow providing the second service to the user, and the second service is a service that requires identity verification.

[0008] In addition, a service management system according to a preferred embodiment of the present invention includes an acquisition unit that forms a pair of a contractor of a first service that requires identity verification at the time of contract and a member of a platform service corresponding to the contractor, and when the contractor and the member are the same person, allows the second service to be provided to the member without performing identity verification, and when the contractor and the member are not the same person, does not allow the second service to be provided to the member. The platform service provides information in a unified manner for a plurality of services including the first service and the second service, and the second service is a service that requires identity verification.

Advantages of the Invention

[0009] According to the present invention, it is possible to provide a method for providing a second service assuming a case where the contractor of the first service and the user of the first service are different from each other, or a case where the contractor of the first service and the member of the second service corresponding to the contractor are different from each other.

Brief Description of the Drawings

[0010]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Embodiments for Carrying Out the Invention

[0011] 1: First Embodiment Hereinafter, with reference to FIGS. 1 to 6, the service management system 1A according to the present embodiment will be described.

[0012] The prior art did not assume a case where the contractor of the first service and the user of the first service are different while the user of the first service is registered. The service management system 1A of the present embodiment can provide a method for providing a second service assuming a case where the contractor of the first service and the user of the first service are different from each other.

[0013] 1-1: Configuration of the First Embodiment 1-1-1: Overall Configuration FIG. 1 is a block diagram showing the overall configuration of the service management system 1A according to the present embodiment. As shown in FIG. 1, the service management system 1A includes a management device 10A, a service providing server 20A, and terminals 30[1] to 30[n]. The management device 10A, the service providing server 20A, and the terminals 30[1] to 30[n] are communicably connected to each other via a communication network NET. n is an integer of 1 or more. k is an integer of 1 or more and n or less. In the following description, the terminals 30[1] to 30[n] may be collectively referred to as "terminal 30". In FIG. 1, the user U uses the terminal 30. Also, the user U[k] uses the terminal 30[k]. Note that in FIG. 1, the number of the management device 10A and the service providing server 20A being one is merely an example. The service management system 1A includes an arbitrary number of management devices 10A and service providing servers 20A. The number of the management device 10A and the service providing server 20A may be the same as each other or different from each other.

[0014] The terminal 30 is, as an example, a device used by the user U to utilize a telephone function. The telephone function is an example of the "first service". At the time of contracting the "first service", identity verification is required. Also, the user U is an example of the "user" of the "first service". Also, the terminal 30 is, as an example, a device used by the user U to purchase goods or services. An application is installed on the terminal 30. The application is, as an example, an application for electronic payment. When the application is an application for electronic payment, the user U[k] may settle the purchase amount of goods or services by using the application for electronic payment installed on the terminal 30[k]. Alternatively, the user U[k] may perform online payment after connecting the terminal 30[k] to the Internet.

[0015] The terminal 30 is preferably a mobile terminal. The terminal 30 may be, for example, a smartphone or a tablet. Alternatively, the terminal 30 may be a PC (Personal Computer).

[0016] As will be described later, the management device 10A determines whether the contractor and the user of the "first service" available on the terminal 30 are the same. Also, the management device 10A performs identity verification regarding the terminal 30.

[0017] The service providing server 20A is a server that provides a service that requires identity verification to the terminal 30. The service is an example of the "second service". The "second service" is, as an example, an electronic payment service that requires identity verification. Also, the electronic payment service is, as an example, an electronic payment service that can make payments using the funds in the account and can transfer the funds in the account. Here, "able to transfer the funds in the account" means that it is possible to recharge from a bank account. The electronic payment service is an example of the "first electronic payment service".

[0018] In addition, the service providing server 20A may provide the terminal 30 with an electronic payment service that does not require identity verification and is different from the above-mentioned "second service". The electronic payment service is an electronic payment service that can make payments using the funds in the account and cannot transfer the funds in the account. The electronic payment service is an example of the "second electronic payment service".

[0019] In addition, as another function provided by the "first electronic payment service" to the terminal 30 while the "second electronic payment service" is not provided to the terminal 30, it may include the transfer and withdrawal of the balance of the "first electronic payment service".

[0020] By the service providing server 20A providing the above-mentioned "first electronic payment service" and "second electronic payment service" to the terminal 30[k], as described above, the user U[k] can settle the purchase amount of goods or services.

[0021] 1-1-2: Configuration of the management device 10A FIG. 2 is a block diagram showing a configuration example of the management device 10A. As shown in FIG. 2, the management device 10A includes a processing device 11, a storage device 12, a communication device 13, a display device 14, and an input device 15. Each element of the management device 10A is interconnected by a single or a plurality of buses for communicating information.

[0022] The processing device 11 is a processor that controls the entire management device 10A. The processing device 11 is configured using, for example, one or more chips. Further, the processing device 11 is configured using, for example, a central processing unit (CPU) including an interface with peripheral devices, an arithmetic unit, registers, and the like. Note that part or all of the functions of the processing device 11 may be realized by hardware such as a DSP (Digital Signal Processor), an ASIC (Application Specific Integrated Circuit), a PLD (Programmable Logic Device), and an FPGA (Field Programmable Gate Array). The processing device 11 executes various processes in parallel or sequentially.

[0023] The storage device 12 is a recording medium that can be read from and written to by the processing device 11. The storage device 12 includes, for example, a non-volatile memory and a volatile memory. The non-volatile memory is, for example, a ROM (Read Only Memory), an EPROM (Erasable Programmable Read Only Memory), and an EEPROM (Electrically Erasable Programmable Read Only Memory). The volatile memory is, for example, a RAM (Random Access Memory). Further, the storage device 12 functions as a work area for the processing device 11. The storage device 12 stores the control program PR1 executed by the processing device 11 and the customer database CDB[1].

[0024] The customer database CDB[1] is a database in which data related to customers is stored. The customer is the user U of the terminal 30.

[0025] FIG. 3 is a diagram showing a configuration example of the customer database CDB[1]. Customer data CDS is stored in the customer database CDB[1]. The customer data CDS has items of "data ID", "terminal ID", "contractor", and "user". The "data ID" is an identifier for each customer data CDS. The "terminal ID" is an identifier for identifying terminals 30[1] to 30[n]. The "contractor" is a contractor of the "first service" that can be used by the terminal 30 indicated by the "terminal ID". When the "first service" is the telephone function of the terminal 30, the "contractor" is the line contractor of the telephone line used in the telephone function. The "user" is a user of the "first service" that can be used by the terminal 30 indicated by the "terminal ID". When the "first service" is the telephone function of the terminal 30, the "user" is the line user of the telephone line used in the telephone function. In FIG. 3, for simplicity of explanation, the data of the "contractor" is shown by an initial. However, in reality, the data of the "contractor" is shown by a full name. Alternatively, the data of the "contractor" may be shown by an identifier for identifying the "contractor". The same applies to the data of the "user" as the data of the "contractor".

[0026] In the customer database CDB[1] illustrated in FIG. 3, as an example, in the customer data CDS with the "data ID" of "001", the "contractor" and the "user" match. On the other hand, as an example, in the customer data CDS with the "data ID" of "002", the "contractor" and the "user" do not match.

[0027] In FIG. 2, the communication device 13 is hardware as a transceiver device for communicating with other devices. The communication device 13 is also called, for example, a network device, a network controller, a network card, or a communication module. The communication device 13 is provided with a connector for a wired connection and may be provided with an interface circuit corresponding to the above connector. Further, the communication device 13 may be provided with a wireless communication interface. Examples of the connector for a wired connection and the interface circuit include products compliant with wired LAN, IEEE1394, and USB. Examples of the wireless communication interface include products compliant with wireless LAN and Bluetooth (registered trademark).

[0028] The display device 14 is a device that displays images and character information. The display device 14 displays various images under the control of the processing device 11. For example, various display panels such as a liquid crystal display panel and an organic EL display panel are preferably used as the display device 14.

[0029] The input device 15 is a device that receives operations from the administrator of the management device 10A. For example, the input device 15 includes a pointing device such as a keyboard, a touch pad, a touch panel, or a mouse. Here, when the input device 15 includes a touch panel, it may also serve as the display device 14.

[0030] For example, the processing device 11 functions as a communication control unit 111, a reception unit 112, an acquisition unit 113, and a determination unit 114 by reading and executing the control program PR1 from the storage device 12.

[0031] The communication control unit 111 causes the communication device 13 to transmit and receive various data to and from other devices.

[0032] The reception unit 112 receives a request for determining whether the contractor and the user of the "First Service" used in the terminal 30[k] are the same person from the service providing server 20A.

[0033] In addition, the reception unit 112 directly receives a request for identity verification from the terminal 30[k]. The request for identity verification includes a request for determining whether the contract holder and the user of the "First Service" used in the terminal 30[k] are the same person.

[0034] The above request for determination includes data indicating the "terminal ID", which is the identifier of the terminal 30[k].

[0035] When the reception unit 112 receives a request for determination, the acquisition unit 113 refers to the customer database CDB[1] using the "terminal ID", which is the identifier of the terminal 30[k] included in the request for determination, to extract customer data CDS including the "terminal ID". Further, the acquisition unit 113 acquires the pair of the contract holder and the user included in the extracted customer data CDS. In other words, the acquisition unit 113 acquires the pair of the contract holder of the "First Service" that requires identity verification at the time of contract and the user of the "First Service" corresponding to the contract holder.

[0036] As an example, when the identifier of the terminal 30[k] is "A2875", the acquisition unit 113 acquires the pair of "H.A" as the "contract holder" and "H.A" as the "user". As another example, when the identifier of the terminal 30[k] is "K1973", the acquisition unit 113 acquires the pair of "T.O" as the "contract holder" and "S.H" as the "user".

[0037] When the reception unit 112 receives the above request for determination, the determination unit 114 determines whether the "contract holder" and the "user" are the same person in the pair of the "contract holder" and the "user" acquired by the acquisition unit 113.

[0038] In addition, when the reception unit 112 receives the above request for identity verification, the determination unit 114 determines whether the "contract holder" and the "user" are the same person among the pairs of the "contract holder" and the "user" acquired by the acquisition unit 113 when the reception unit 112 receives the above request for identity verification.

[0039] As an example, as described above, when the acquisition unit 113 acquires the pair of "H.A" as the "contractor" and "H.A" as the "user", the determination unit 114 determines that the "contractor" and the "user" are the same person. As another example, when the acquisition unit 113 acquires the pair of "T.O" as the "contractor" and "S.H" as the "user", the determination unit 114 determines that the "contractor" and the "user" are not the same person.

[0040] The communication control unit 111 causes the communication device 13 to transmit the determination result determined by the determination unit 114 to another device.

[0041] When the reception unit 112 receives the above determination request from the service providing server 20A, the communication control unit 111 causes the communication device 13 to transmit the above determination result to the service providing server 20A. When the reception unit 112 directly receives the personal confirmation request from the terminal 30[k], the communication control unit 111 causes the communication device 13 to transmit the above determination result to the terminal 30[k] together with the personal confirmation result.

[0042] 1-1-3: Configuration of Service Providing Server 20A FIG. 4 is a block diagram showing a configuration example of the service providing server 20A. As shown in FIG. 4, the service providing server 20A includes a processing device 21, a storage device 22, a communication device 23, a display device 24, and an input device 25. Each element included in the service providing server 20A is interconnected by one or a plurality of buses for communicating information.

[0043] The processing device 21 is a processor that controls the entire service - providing server 20A. The processing device 21 is configured using, for example, one or more chips. Further, the processing device 21 is configured using, for example, a central processing unit (CPU) including an interface with peripheral devices, an arithmetic unit, and registers, etc. Note that part or all of the functions of the processing device 21 may be realized by hardware such as a DSP (Digital Signal Processor), an ASIC (Application Specific Integrated Circuit), a PLD (Programmable Logic Device), and an FPGA (Field Programmable Gate Array). The processing device 21 executes various processes in parallel or sequentially.

[0044] The storage device 22 is a recording medium that can be read from and written to by the processing device 21. The storage device 22 includes, for example, a non - volatile memory and a volatile memory. The non - volatile memory is, for example, a ROM (Read Only Memory), an EPROM (Erasable Programmable Read Only Memory), and an EEPROM (Electrically Erasable Programmable Read Only Memory). The volatile memory is, for example, a RAM (Random Access Memory). Further, the storage device 22 functions as a work area for the processing device 21. Also, the storage device 22 stores the control program PR2 executed by the processing device 21.

[0045] The communication device 23 is hardware as a transceiver device for communicating with other devices. The communication device 23 is also called, for example, a network device, a network controller, a network card, or a communication module. The communication device 23 is provided with a connector for wired connection and may be provided with an interface circuit corresponding to the above connector. Further, the communication device 23 may be provided with a wireless communication interface. Examples of the connector for wired connection and the interface circuit include products compliant with wired LAN, IEEE 1394, and USB. Examples of the wireless communication interface include products compliant with wireless LAN and Bluetooth (registered trademark).

[0046] The display device 24 is a device for displaying images and character information. The display device 24 displays various images under the control of the processing device 21. For example, various display panels such as a liquid crystal display panel and an organic EL display panel are preferably used as the display device 24.

[0047] The input device 25 is a device that receives operations from the administrator of the service providing server 20A. For example, the input device 25 includes a pointing device such as a keyboard, a touch pad, a touch panel, or a mouse. Here, when the input device 25 includes a touch panel, it may also serve as the display device 24.

[0048] The processing device 21 functions as a communication control unit 211 and a service management unit 212, for example, by reading and executing the control program PR2 from the storage device 22.

[0049] The communication control unit 211 causes the communication device 23 to transmit and receive various data to and from other devices. As an example, the communication control unit 211 causes the communication device 23 to receive a request for using the "second service" from the terminal 30[k]. The request for using the "second service" includes the above-described determination request. The communication control unit 211 causes the communication device 23 to transmit the above-described determination request to the management device 10A.

[0050] Further, the communication control unit 211 causes the communication device 23 to receive the determination result from the management device 10A.

[0051] The service management unit 212 manages the services provided to the terminal 30[k]. As an example, when the determination result received by the service management unit 212 from the management device 10A indicates that the contractor and the user are the same person, the service management unit 212 allows the "Second Service" to be provided to the user without identity verification. On the other hand, when the determination result received by the service management unit 212 from the management device 10A does not indicate that the contractor and the user are the same person, the service management unit 212 does not allow the "Second Service" to be provided to the user.

[0052] Specifically, when the service providing server 20A transmits a determination request to the management device 10A and receives a determination result indicating that the contractor and the user are the same person from the management device 10A, the service management unit 212 causes the communication device 23 to transmit setting data for enabling the "Second Service" to the terminal 30[k] without identity verification. On the other hand, when the above determination result does not indicate that the contractor and the user are the same person, the service management unit 212 does not cause the communication device 23 to transmit setting data for enabling the "Second Service" to the terminal 30[k]. As a result, the user U[k] cannot use the "Second Service" on the terminal 30[k]. In this case, the service management unit 212 causes the communication device 23 to transmit an error message to the terminal 30[k]. The error message is displayed on the terminal 30[k].

[0053] As described above, when the service management unit 212 provides the "Second Service" to the above user without identity verification and then the above contractor and the above user are found to be inconsistent, the service management unit 212, as an example, stops providing the "Second Service" to the above user.

[0054] Also, as another example, before the user U[k] as the above user starts using the "Second Service", the terminal 30[k] sends a request for identity verification to the management device 10A. When the above determination result indicates that the contractor and the user are the same person, the service management unit 212 permits the provision of the "Second Service" to the user. On the other hand, when the above determination result does not indicate that the contractor and the user are the same person, the service management unit 212 does not permit the provision of the "Second Service" to the user.

[0055] Specifically, when the terminal 30[k] sends a request for identity verification to the management device 10A and the above determination result indicates that the contractor and the user are the same person, the management device 10A also sends the determination result to the service providing server 20A. Triggered by the service providing server 20A receiving the determination result, the service management unit 212 causes the communication device 23 to send setting data for enabling the "Second Service" to the terminal 30[k]. On the other hand, when the above determination result does not indicate that the contractor and the user are the same person, the management device 10A also sends the determination result to the service providing server 20A. Based on the determination result, the service management unit 212 does not cause the communication device 23 to send setting data for enabling the "Second Service" to the terminal 30[k]. As a result, the user U[k] cannot use the "Second Service" on the terminal 30[k]. In this case, the service management unit 212 causes the communication device 23 to send an error message to the terminal 30[k]. The error message is displayed on the terminal 30[k].

[0056] When the service management unit 212 does not permit the provision of the "Second Service", that is, the "First Electronic Payment Service" that requires identity verification, to the above user, as an example, the service management unit 212 permits the provision of the "Second Electronic Payment Service" that does not require identity verification to the user.

[0057] 1-2: Operations of the First Embodiment 1-2-1: First operation example FIG. 5 is a sequence diagram showing a first operation example of the service management system 1A according to the first embodiment.

[0058] In step S1, the terminal 30[k] transmits a request to use the "Second Service" to the service providing server 20A.

[0059] In step S2, the service providing server 20A transmits a request to the management device 10A to determine whether the contract holder and the user of the "First Service" used by the terminal 30[k] are the same person. In step S2, the processing device 11 provided in the management device 10A functions as a reception unit 112. The processing device 11 receives a request from the service providing server 20A to determine whether the contract holder and the user of the "First Service" are the same person.

[0060] In step S3, the management device 10A determines whether the contract holder and the user of the "First Service" used by the terminal 30[k] are the same person.

[0061] Specifically, the processing device 11 provided in the management device 10A functions as an acquisition unit 113. The processing device 11 acquires a set of the contract holder of the "First Service" and the user of the "First Service" corresponding to the contract holder. Further, the processing device 11 functions as a determination unit 114. The processing device 11 determines whether the "contract holder" and the "user" in the set of the "contract holder" and the "user" acquired by the acquisition unit 113 are the same person.

[0062] In step S4, the management device 10A transmits the determination result determined by the processing device 11 functioning as the determination unit 114 to the service providing server 20A.

[0063] In step S5, based on the determination result received in step S4, the service providing server 20A transmits the setting data or error message of the "second service" to the terminal 30[k].

[0064] Specifically, the processing device 21 functions as a service management unit 212. When the above determination result indicates that the contractor and the user are the same person, the processing device 21 causes the communication device 23 to transmit the setting data for the "second service" to be available to the terminal 30[k] without performing identity verification. On the other hand, when the above determination result does not indicate that the contractor and the user are the same person, the processing device 21 does not cause the communication device 23 to transmit the setting data for the "second service" to be available to the terminal 30[k]. In this case, the processing device 21 causes the communication device 23 to transmit an error message to the terminal 30[k]. The error message is displayed on the terminal 30[k].

[0065] 1-2-2: Second operation example FIG. 6 is a sequence diagram showing a second operation example of the service management system 1A according to the above embodiment.

[0066] In step S11, the terminal 30[k] transmits a request for identity verification to the management device 10A.

[0067] In step S11, the processing device 11 provided in the management device 10A functions as a reception unit 112. The processing device 11 receives a request for identity verification from the terminal 30[k].

[0068] In step S12, the management device 10A performs identity verification and determines whether the contractor and the user of the "first service" used in the terminal 30[k] are the same person.

[0069] Specifically, the processing device 11 provided in the management device 10A functions as an acquisition unit 113. The processing device 11 acquires a pair of the contractor of the "first service" and the user of the "first service" corresponding to the contractor. Further, the processing device 11 functions as a determination unit 114. The processing device 11 determines whether or not the "contractor" and the "user" in the pair of "contractor" and "user" acquired by the acquisition unit 113 are the same person.

[0070] In step S13, the management device 10A transmits to the terminal 30[k] the result of the identity verification and the determination result determined by the processing device 11 functioning as the determination unit 114.

[0071] Although not shown in FIG. 7, the management device 10A may also transmit the above determination result to the service providing server 20A.

[0072] When the management device 10A transmits the above determination result to the service providing server 20A, the processing device 21 provided in the service providing server 20A functions as a service management unit 212. When the above determination result indicates that the contractor and the user are the same person, the processing device 21 permits the provision of the "second service" to the user. On the other hand, when the above determination result does not indicate that the contractor and the user are the same person, the processing device 21 does not permit the provision of the "second service" to the user.

[0073] 1-3: Effects of the First Embodiment The service management system 1A according to the present embodiment includes an acquisition unit 113 and a service management unit 212. The acquisition unit 113 acquires a pair of a contractor of a first service that requires identity verification at the time of contract and a user of the first service corresponding to the contractor. The service management unit 212 permits the provision of a second service to the above user without performing identity verification when the above contractor and the above user are the same person. Further, the service management unit 212 does not permit the provision of the second service to the above user when the above contractor and the above user are not the same person. Note that the second service is a service that requires identity verification.

[0074] The service management system 1A having the above configuration can provide a method of providing a second service assuming a case in which a subscriber to the first service and a user of the first service are different from each other.

[0075] Moreover, the service management system 1A according to this embodiment further includes a reception unit 112 and a determination unit 114. The reception unit 112 receives a request for identity verification from the terminal 30 used by the user before the user starts using the second service. The determination unit 114 uses the request as a trigger to determine whether the contractor and the user are the same person. If the result of the above determination is positive, the service management unit 212 allows the second service to be provided to the user. If the result of the above determination is negative, the service management unit 212 does not allow the second service to be provided to the user.

[0076] The service management system 1A, having the above-described configuration, can control whether or not to provide the second service to the user when a request for identity verification from the terminal 30 is received.

[0077] Furthermore, in the service management system 1A of this embodiment, if the service management unit 212 provides the second service to the user without performing identity verification and then finds that the above-mentioned contractor and the above-mentioned user do not match, the service management unit 212 stops providing the second service to the above-mentioned user.

[0078] By being equipped with the above-described configuration, the service management system 1A can respond to a case where, after starting to provide the second service to the user, it becomes clear that the subscriber and the user are not the same person, without confirming whether the subscriber and the user are the same person.

[0079] In the service management system 1A according to the present embodiment, the second service is a first electronic payment service that requires identity verification. When the service management unit 212 does not permit the provision of the second service to a user, it permits the provision of a second electronic payment service that does not require identity verification.

[0080] By having the above configuration, the service management system 1A enables a user who cannot receive the first electronic payment service to receive the second electronic payment service as an alternative to the first electronic payment service.

[0081] Also, in the service management system 1A according to the present embodiment, the above-mentioned first electronic payment service can be used to make payments using the funds in the account and the funds in the account can be transferred. Further, the above-mentioned second electronic payment service can be used to make payments using the funds in the account, but the funds in the account cannot be transferred.

[0082] By having the above configuration, when using the first electronic payment service that requires identity verification, the service management system 1A can utilize more functions compared to using the second electronic payment service that does not require identity verification.

[0083] 2: Second Embodiment Hereinafter, the service management system 1B according to the present embodiment will be described with reference to FIG. 7. In the following, for the sake of simplicity of explanation, mainly, among the technical features of the service management system 1B, the points different from the technical features of the service management system 1A will be described. Also, among the components provided in the service management system 1B, for the components identical to the components provided in the service management system 1A, the same reference numerals may be used and the description of their functions may be omitted.

[0084] The prior art did not assume the case where the member of the second service was registered while the contractor of the first service and the member of the second service corresponding to the contractor were different. The service management system 1B of the present embodiment can provide a method for providing the second service assuming the case where the contractor of the first service and the member of the second service corresponding to the contractor are different from each other.

[0085] Note that in this embodiment, the "service member" refers to a member of the platform service. The details of the "platform service" will be described later.

[0086] This embodiment is the same as the first embodiment, except that the user of the "first service" in the first embodiment is replaced by a member of the platform service. Hereinafter, an example of the configuration and operation of the service management system 1B according to this embodiment will be described.

[0087] 2-1: Configuration of the Second Embodiment 2-1-1: Overall Configuration The service management system 1B according to this embodiment is the same as the service management system 1A according to the first embodiment shown in FIG. 1, except that the management device 10A is replaced by the management device 10B and the service providing server 20A is replaced by the service providing server 20B. Therefore, the illustration of its overall configuration is omitted.

[0088] An application is installed on the terminal 30 provided in the service management system 1B in the same manner as the terminal 30 according to the first embodiment. As an example, the application is an application for electronic payment. In this embodiment, the above "platform service" is a service using the application installed on the terminal 30. The platform service manages information uniformly for a plurality of services including the above "first service" and the above "second service".

[0089] 2-1-2: Configuration of the Management Device 10B The configuration of the management device 10B provided in the service management system 1B according to this embodiment is the same as the configuration of the management device 10A shown in FIG. 2, except that the storage device 12 stores the customer database CDB[2] instead of the customer database CDB[1]. Therefore, the illustration thereof is omitted.

[0090] The customer database CDB[2] is a database that stores data related to customers. The customer is the user U of the terminal 30.

[0091] FIG. 7 is a diagram showing a configuration example of the customer database CDB[2]. Customer data CDS is stored in the customer database CDB[2]. The customer data CDS has items of "data ID", "terminal ID", "contractor", and "member". The "data ID" is an identifier for each customer data CDS. The "terminal ID" is an identifier for identifying terminals 30[1] to 30[n]. The "contractor" is a contractor of the "first service" that can be used in the terminal 30 indicated by the "terminal ID". When the "first service" is the telephone function of the terminal 30, the "contractor" is the line contractor of the telephone line used in the telephone function. The "member" is a member of the platform service that can be used in the terminal 30 indicated by the "terminal ID". When the platform service is a service using the application for electronic payment of the terminal 30, the "member" is a member who can use the application. In FIG. 7, for simplicity of explanation, the data of the "contractor" is shown by the initials. However, in reality, the data of the "contractor" is shown by the full name. Alternatively, the data of the "contractor" may be shown by an identifier for identifying the "contractor". The same applies to the data of the "member".

[0092] In the customer database CDB[2] illustrated in FIG. 7, as an example, in the customer data CDS with the "data ID" of "001", the "contractor" and the "member" are the same. On the other hand, as an example, in the customer data CDS with the "data ID" of "002", the "contractor" and the "member" are not the same.

[0093] The processing device 11 provided in the management device 10B functions as a communication control unit 111, a reception unit 112, an acquisition unit 113, and a determination unit 114, for example, by reading and executing the control program PR1 from the storage device 12.

[0094] Unlike the reception unit 112 according to the first embodiment, the reception unit 112 according to the present embodiment receives a request for determining whether the contractor of the "First Service" being used in the terminal 30[k] and the member of the platform service corresponding to the contractor are the same person from the service providing server 20A.

[0095] In addition, the reception unit 112 directly receives a request for identity verification from the terminal 30[k]. The request for identity verification includes a request for determining whether the contractor of the "First Service" being used in the terminal 30[k] and the member of the platform service corresponding to the contractor are the same person.

[0096] Unlike the acquisition unit 113 according to the first embodiment, when the reception unit 112 receives a request for determination, the acquisition unit 113 according to the present embodiment refers to the customer database CDB[2] using the identifier of the terminal 30[k] included in the request for determination, and extracts customer data CDS including the identifier. Further, the acquisition unit 113 acquires the pair of the contractor and the member included in the customer data CDS. In other words, the acquisition unit 113 acquires the pair of the contractor of the "First Service" that requires identity verification at the time of contract and the member of the platform service corresponding to the contractor.

[0097] Unlike the determination unit 114 according to the first embodiment, when the reception unit 112 receives the above-mentioned request for determination, the determination unit 114 according to the present embodiment determines whether the "contractor" and the "member" are the same person in the pair of the "contractor" and the "member" acquired by the acquisition unit 113. Also, when the reception unit 112 receives the above-mentioned request for identity verification, the determination unit 114 determines whether the "contractor" and the "member" are the same person among the pairs of the "contractor" and the "member" acquired by the acquisition unit 113, triggered by the reception unit 112 receiving the above-mentioned request for identity verification.

[0098] 2-1-3: Configuration of Service Providing Server 20B Since the configuration of the service providing server 20B provided in the service management system 1B according to the present embodiment is the same as that of the service providing server 20A shown in FIG. 4, the illustration thereof is omitted.

[0099] The processing device 11 provided in the service providing server 20B functions as a communication control unit 211 and a service management unit 212, for example, by reading and executing the control program PR2 from the storage device 22.

[0100] Unlike the service management unit 212 according to the first embodiment, the service management unit 212 according to the present embodiment permits providing the "Second Service" to the member without identity verification when the determination result received from the management device 10B indicates that the contractor and the member are the same person. On the other hand, when the determination result received from the management device 10B does not indicate that the contractor and the member are the same person, the service management unit 212 does not permit providing the "Second Service" to the member.

[0101] As described above, after the service management unit 212 provides the "Second Service" to the above member without identity verification, if the above contractor and the above member do not match, the service management unit 212, as an example, stops providing the "Second Service" to the above member.

[0102] Also, as another example, before the user U[k] as the above member starts using the "Second Service", a request for identity verification is sent from the terminal 30[k] to the management device 10B, and when the above determination result indicates that the contractor and the member are the same person, unlike the service management unit 212 according to the first embodiment, the service management unit 212 permits providing the "Second Service" to the member. On the other hand, when the above determination result does not indicate that the contractor and the member are the same person, the service management unit 212 does not permit providing the "Second Service" to the member.

[0103] When the Service Management Department 212 does not permit providing the "Second Service", i.e., the "First Electronic Payment Service" that requires identity verification, to the above-mentioned member, the Service Management Department 212, for example, permits providing the "Second Electronic Payment Service" that does not require identity verification to the member.

[0104] 2-2: Operations of the Second Embodiment The first operation example of the service management system 1B according to this embodiment is the same as the first operation example of the service management system 1A according to the first embodiment, except that the "user" is replaced by the "member" in the first operation example of the service management system 1A according to the first embodiment. Therefore, the illustration and description thereof are omitted. Similarly, the second operation example of the service management system 1B according to this embodiment is the same as the second operation example of the service management system 1A according to the first embodiment, except that the "user" is replaced by the "member" in the second operation example of the service management system 1A according to the first embodiment. Therefore, the illustration and description thereof are omitted.

[0105] 2-3: Effects of the Second Embodiment The service management system 1B according to this embodiment includes an acquisition unit 113 and a service management unit 212. The acquisition unit 113 acquires a set of a contractor of the first service that requires identity verification at the time of contract and a member of the platform service corresponding to the above-mentioned contractor. When the above-mentioned contractor and the above-mentioned member are the same person, the service management unit 212 permits providing the second service to the above-mentioned member without performing identity verification. Also, when the above-mentioned contractor and the above-mentioned member are not the same person, the service management unit 212 does not permit providing the second service to the above-mentioned member. The above-mentioned platform service provides information in a unified manner for a plurality of services including the first service and the second service. Note that the second service is a service that requires identity verification.

[0106] By having the above configuration, the service management system 1B according to this embodiment can provide a method for providing the second service assuming a case where the contractor of the first service and the member of the platform service are different from each other.

[0107] In addition, the service management system 1B according to this embodiment further includes a reception unit 112 and a determination unit 114. The reception unit 112 receives a request for identity verification from the terminal 30 used by the member before the member starts using the second service. The determination unit 114 determines whether the above-mentioned contractor and the above-mentioned member are the same person on the occasion of this request. When the result of the above determination is affirmative, the service management unit 212 permits the provision of the second service to the above-mentioned member. Also, when the result of the above determination is negative, the service management unit 212 does not permit the provision of the second service to the above-mentioned member.

[0108] By having the above configuration, the service management system 1B can control whether to provide the second service to the member on the occasion of a request for identity verification from the terminal 30.

[0109] Also, in the service management system 1B according to this embodiment, when the service management unit 212 provides the second service to the member without performing identity verification and then the above-mentioned contractor and the above-mentioned member are found to be inconsistent, the service management unit 212 stops providing the second service to the above-mentioned member.

[0110] By having the above configuration, the service management system 1B can respond when it becomes clear that the contractor and the member are not the same person after starting to provide the second service to the member without confirming whether the contractor and the member are the same person.

[0111] Also, in the service management system 1B according to this embodiment, the above-mentioned second service is a first electronic payment service that requires identity verification. Also, when the service management unit 212 does not permit the provision of the second service to the member, the service management unit 212 permits the provision of a second electronic payment service that does not require identity verification.

[0112] By having the above configuration, the service management system 1B enables a member who cannot receive the first electronic payment service to receive the second electronic payment service as an alternative to the first electronic payment service.

[0113] Also, in the service management system 1B according to the present embodiment, the above-mentioned first electronic payment service can be used to make payments using the funds in the account and the funds in the account can be transferred. Also, the above-mentioned second electronic payment service can be used to make payments using the funds in the account, and the funds in the account cannot be transferred.

[0114] By having the above configuration, when using the first electronic payment service that requires identity verification, the service management system 1B can utilize more functions compared to using the second electronic payment service that does not require identity verification.

[0115] 3: Modification Example The present disclosure is not limited to the embodiments exemplified above. Specific modification modes are exemplified below. Two or more modes arbitrarily selected from the following examples may be combined.

[0116] 3-1: Modification Example 1 FIG. 8 is a diagram showing a configuration example of a customer database CDB[3] stored in the storage device 12 provided in the management device 10A instead of the customer database CDB[1] according to the first embodiment in this modification example. The customer data CDS stored in the customer database CDB[3] does not have an item of "user", unlike the customer data CDS stored in the customer database CDB[1] according to the first embodiment.

[0117] In the service management system 1A according to the first embodiment, a request for determination including the terminal ID of the terminal 30[k] was directly transmitted from the terminal 30[k] to the management device 10A. Alternatively, a request for determination including the terminal ID of the terminal 30[k] was indirectly transmitted from the terminal 30[k] to the management device 10A via the service providing server 20A. Then, the acquisition unit 113 provided in the management device 10A referred to the customer database CDB[1] using the "terminal ID" to extract customer data CDS including the "terminal ID". Further, the acquisition unit 113 acquired the pair of the contractor and the user included in the customer data CDS.

[0118] On the other hand, in this modification, the terminal 30[k] stores user data indicating the user U[k] who is the user, and the above determination request includes the user data in addition to the "customer ID". The acquisition unit 113 provided in the management device 10A refers to the customer database CDB[3] using the "terminal ID" to extract customer data CDS including the "terminal ID". Further, the acquisition unit 113 acquires the contractor included in the customer data CDS.

[0119] Then, the determination unit 114 determines whether the "contractor" acquired by the acquisition unit 113 and the "user" indicated by the user data included in the determination request are the same person. As described above, the "contractor" acquired by the acquisition unit 113 and the "user" indicated by the user data included in the determination request correspond to the same "terminal ID".

[0120] Similarly, the terminal 30[k] stores member data indicating the user U[k] who is a member of the platform service, and the above determination request may include the member data in addition to the "customer ID". The acquisition unit 113 provided in the management device 10A refers to a customer database CDB[4] (not shown) using the "terminal ID" to extract customer data CDS including the "terminal ID". Further, the acquisition unit 113 acquires the member included in the customer data CDS.

[0121] Thereafter, the determination unit 114 determines whether the "contractor" acquired by the acquisition unit 113 is the same person as the "member" indicated by the member data included in the determination request. As described above, the "contractor" acquired by the acquisition unit 113 and the "member" indicated by the member data included in the determination request correspond to the same "terminal ID".

[0122] 3-2: Modification Example 2 In the service management system 1A according to the first embodiment, when the service providing server 20A receives, from the management device 10A, a determination result indicating that the contractor and the user are the same person, the service management unit 212 causes the communication device 23 to transmit setting data for making the "second service" available to the terminal 30[k].

[0123] However, the service management unit 212 may cause the communication device 23 to transmit setting data for making the "second service" available on the terminal 30[k] to an application management server (not shown) that manages the application installed on the terminal 30[k] instead of the terminal 30[k].

[0124] The same applies to the service management system 1B according to the second embodiment.

[0125] 3-3: Modification Example 3 In the above embodiment, the "second service" was, as an example, an electronic payment service. However, the "second service" may be other services. As an example, the "second service" may be an account opening service for opening a bank account used in the electronic payment service.

[0126] 4: Others (1) In the above-described embodiments, the storage devices 12 and 22 were exemplified as ROM and RAM, etc., but flexible disks, magneto-optical disks (e.g., compact disks, digital versatile disks, Blu-ray (registered trademark) disks), smart cards, flash memory devices (e.g., cards, sticks, key drives), CD-ROM (Compact Disc-ROM), registers, removable disks, hard disks, floppy (registered trademark) disks, magnetic strips, databases, servers, and other appropriate storage media.

[0127] (2) In the above-described embodiments, the information, signals, etc. described may be represented using any of various different technologies. For example, the data, instructions, commands, information, signals, bits, symbols, chips, etc. that may be referred to throughout the above description may be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, optical fields or photons, or any combination thereof.

[0128] (3) In the above-described embodiments, the input / output information, etc. may be stored in a specific location (e.g., memory) or may be managed using a management table. The input / output information, etc. may be overwritten, updated, or appended. The output information, etc. may be deleted. The input information, etc. may be transmitted to other devices.

[0129] (4) In the above-described embodiments, the determination may be made based on a value represented by 1 bit (0 or 1), or may be made based on a truth value (Boolean: true or false), or may be made by comparing numerical values (e.g., comparison with a predetermined value).

[0130] (5) In the above-described embodiments, the processing procedures, sequences, flowcharts, etc. exemplified may be reordered as long as there is no contradiction. For example, for the methods described in the present disclosure, the elements of various steps are presented using an exemplary order and are not limited to the specific order presented.

[0131] (6) Each function exemplified in FIGS. 1 to 8 is realized by any combination of at least one of hardware and software. Also, the method of realizing each functional block is not particularly limited. That is, each functional block may be realized using one physically or logically combined device, or two or more physically or logically separated devices may be directly or indirectly connected (for example, using wired, wireless, etc.), and realized using these multiple devices. The functional block may be realized by combining software with the above one device or the above multiple devices.

[0132] (7) The program exemplified in the above-described embodiments should be broadly interpreted to mean an instruction, instruction set, code, code segment, program code, program, subprogram, software module, application, software application, software package, routine, subroutine, object, executable file, execution thread, procedure, function, etc., whether it is called a software, firmware, middleware, microcode, hardware description language, or by another name.

[0133] Also, software, instructions, information, etc. may be transmitted and received via a transmission medium. For example, when software is transmitted from a website, server, or other remote source using at least one of wired technologies (coaxial cable, optical fiber cable, twisted pair, digital subscriber line (DSL), etc.) and wireless technologies (infrared, microwave, etc.), at least one of these wired and wireless technologies is included within the definition of the transmission medium.

[0134] (8) In each of the above-described embodiments, the terms "system" and "network" are used interchangeably.

[0135] (9) The information, parameters, etc. described in this disclosure may be represented using absolute values, relative values from a predetermined value, or using corresponding other information.

[0136] (10) In the above-described embodiments, the terminal 30 may include a case where it is a mobile station (MS: Mobile Station). A mobile station may be referred to by those skilled in the art as a subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, or some other suitable term. Also, in this disclosure, terms such as "mobile station", "user terminal", "user equipment (UE)", "terminal", etc. may be used interchangeably.

[0137] (11) In the above-described embodiments, the terms "connected" and "coupled", or any variations thereof, mean any direct or indirect connection or coupling between two or more elements, and can include the presence of one or more intermediate elements between two elements that are "connected" or "coupled" to each other. The coupling or connection between elements can be a physical coupling or connection, a logical coupling or connection, or a combination thereof. For example, "connected" may be read as "accessed". When used in this disclosure, two elements can be considered to be "connected" or "coupled" to each other using at least one of one or more electric wires, cables, and printed electrical connections, and also, as some non-limiting and non-inclusive examples, electromagnetic energy having wavelengths in the radio frequency region, microwave region, and optical (both visible and invisible) region.

[0138] In the above-described embodiments, unless otherwise specified, the description "based on" does not mean "only based on". In other words, the description "based on" means both "only based on" and "at least based on".

[0139] (13) The terms "determining" and "deciding" as used in this disclosure may encompass a wide variety of operations. "Determining" and "deciding" may include, for example, judging, calculating, computing, processing, deriving, investigating, looking up (e.g., searching in a table, database, or another data structure), ascertaining, and considering something as having "determined" or "decided" the ascertained matter. Also, "determining" and "deciding" may include receiving (e.g., receiving information), transmitting (e.g., transmitting information), inputting, outputting, accessing (e.g., accessing data in a memory), and considering something as having "determined" or "decided" the received, transmitted, input, or output matter. Further, "determining" and "deciding" may include resolving, selecting, choosing, establishing, comparing, etc., and considering something as having "determined" or "decided" the resolved, selected, chosen, established, or compared matter. That is, "determining" and "deciding" may include considering something as having "determined" or "decided" some operation. Also, "determining (deciding)" may be replaced by "assuming", "expecting", "considering", etc.

[0140] (14) In the above-described embodiments, when terms such as "include", "including" and their variants are used, these terms are intended to be inclusive, similar to the term "comprising". Further, the term "or" used in the present disclosure is not intended to be an exclusive disjunction.

[0141] (15) In the present disclosure, for example, when articles are added by translation, such as a, an and the in English, the present disclosure may include that the nouns following these articles are in the plural form.

[0142] (16) In the present disclosure, the term "A and B are different" may mean "A and B are different from each other". Note that the term may also mean "A and B are each different from C". Terms such as "separate", "coupled", etc. may also be interpreted in the same way as "different".

[0143] (17) Each aspect / embodiment described in the present disclosure may be used alone, in combination, or switched and used during execution. Also, the notification of predetermined information (for example, the notification of "being X") is not limited to an explicitly made notification, and may be made implicitly (for example, by not making the notification of the predetermined information).

[0144] As described above in detail, it is obvious to those skilled in the art that the present disclosure is not limited to the embodiments described in the present disclosure. The present disclosure can be implemented as modified and changed aspects without departing from the spirit and scope of the present disclosure defined by the claims. Therefore, the description of the present disclosure is for illustrative purposes and has no restrictive meaning for the present disclosure.

Description of Reference Numerals

[0145] 1A... Service management system, 1B... Service management system, 10A... Management device, 10B... Management device, 11... Processing device, 12... Storage device, 13... Communication device, 14... Display device, 15... Input device, 20A... Service providing server, 20B... Service providing server, 21... Processing device, 22... Storage device, 23... Communication device, 24... Display device, 25... Input device, 30... Terminal, 111... Communication control unit, 112... Reception unit, 113... Acquisition unit, 114... Judgment unit, 211... Communication control unit, 212... Service management unit, CDB... Customer database, CDS... Customer data, NET... Communication network, PR1... Control program, PR2... Control program, U... User

Claims

1. an acquisition unit that acquires a pair of a subscriber of a first service that requires identity verification at the time of signing a contract and a user of the first service corresponding to the subscriber; a service management unit that allows provision of a second service to the user without performing identity verification when the contractor and the user are the same person, and does not allow provision of the second service to the user when the contractor and the user are not the same person, The second service is a service that requires identity verification, the service management unit provides the second service to the user without performing identity verification, and then, when the contractor and the user do not match, stops providing the second service to the user. Service management system.

2. an acquisition unit that acquires a pair of a subscriber of a first service that requires identity verification at the time of signing a contract and a member of a platform service corresponding to the subscriber; a service management unit that allows the provision of a second service to the member without performing identity verification if the contract holder and the member are the same person, and does not allow the provision of the second service to the member if the contract holder and the member are not the same person, The platform service provides information on a plurality of services including the first service and the second service in a unified manner; The second service is a service that requires identity verification, the service management unit provides the second service to the member without performing identity verification, and then, when there is a mismatch between the contractor and the member, stops providing the second service to the member. Service management system.

3. a reception unit that receives a request for identity verification from a terminal used by the user before the user starts using the second service; a determination unit that determines whether the contractor and the user are the same person in response to the request; Further comprising: The service management unit If the result of the determination is positive, allowing the second service to be provided to the user; If the result of the determination is negative, the second service is not permitted to be provided to the user. The service management system according to claim 1 .

4. a reception unit that receives a request for identity verification from a terminal used by the member before the member starts using the second service; a determination unit which, in response to the request, determines whether the contractor and the member are the same person; Further comprising: The service management unit If the result of the determination is positive, permitting the second service to be provided to the member; If the result of the determination is negative, the second service is not permitted to be provided to the member. The service management system according to claim 2.

5. An acquisition unit that acquires a pair of a subscriber of a first service that requires identity verification at the time of contract and a user of the first service corresponding to the subscriber; a service management unit that allows provision of a second service to the user without performing identity verification when the contractor and the user are the same person, and does not allow provision of the second service to the user when the contractor and the user are not the same person, The second service is a service that requires identity verification, the second service is a first electronic payment service that requires identity verification; When the service management unit does not permit the provision of the second service to the user, the service management unit permits the provision of a second electronic payment service that does not require identity verification. Service management system.

6. An acquisition unit that acquires a pair of a subscriber of a first service that requires identity verification at the time of contract and a member of a platform service corresponding to the subscriber; a service management unit that allows the provision of a second service to the member without performing identity verification if the contract holder and the member are the same person, and does not allow the provision of the second service to the member if the contract holder and the member are not the same person, The platform service provides information on a plurality of services including the first service and the second service in a unified manner; The second service is a service that requires identity verification, the second service is a first electronic payment service that requires identity verification; When the service management unit does not permit the provision of the second service to the member, the service management unit permits the provision of a second electronic payment service that does not require identity verification. Service management system.

7. The first electronic payment service allows payments to be made using funds in an account and allows funds in an account to be transferred; The second electronic payment service allows payment using funds in the account and does not allow funds in the account to be transferred. The service management system according to claim 5.

8. The first electronic payment service allows payments to be made using funds in an account and allows funds in an account to be transferred; The second electronic payment service allows payment using funds in the account and does not allow funds in the account to be transferred. The service management system according to claim 6.

Images