Service Management System
The service management system addresses registration issues by determining matching subscribers/users and managing multiple services, ensuring proper access and offering alternatives when necessary, thus enhancing service provision efficiency.
Patent Information
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- NTT DOCOMO INC
- Filing Date
- 2024-12-20
- Publication Date
- 2026-07-02
AI Technical Summary
Existing technologies fail to address situations where the service subscriber and user are different, or the subscriber of a first service and member of a second service are different, leading to registration issues in personal authentication.
A service management system that includes an acquisition unit to pair subscribers/users and determines if they are the same person, allowing or denying access to services based on identity verification, and managing multiple services through a platform service.
Enables provision of services to users/subscribers without unnecessary identity verification, ensuring accurate service access and providing alternative services when discrepancies arise.
Smart Images

Figure 2026109892000001_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to a service management system.
Background Art
[0002] When providing a service, if the contract customer of the service does not match the user of the service, problems may occur from the perspective of personal authentication.
[0003] Regarding personal authentication, for example, Patent Document 1 discloses a technology related to an authentication support device that enhances convenience and confidentiality in personal authentication. In this technology, a registration request acquisition unit acquires a registration request including a telephone number and a kana name. Also, an authentication processing unit refers to contract customer information stored in the authentication device, which associates a telephone number with the kana name of the contract customer of the telephone number. Further, the authentication processing unit authenticates the legitimacy of the telephone number and the user based on whether the kana name of the contract customer corresponding to the telephone number included in the registration request matches the kana name included in the registration request in the contract customer 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 described in Patent Document 1, although a comparison is made between the subscriber and the user, if the subscriber and the user are different, the user information cannot be registered. In other words, the technology described in Patent Document 1 did not anticipate a case where the service subscriber and the service user are different, and at the same time, the service user is registered. Furthermore, the technology described in Patent Document 1 did not anticipate a case where the subscriber of the first service and the member of the second service corresponding to that subscriber are different, 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 that the subscriber of the first service and the user of the first service are different from each other, or that the subscriber of the first service and the member of the second service corresponding to that subscriber are different from each other. [Means for solving the problem]
[0007] A service management system according to a preferred embodiment of the present invention includes an acquisition unit that acquires a pair of a subscriber to a first service that requires identity verification at the time of contract and a user of the first service corresponding to the subscriber, and a service management unit that permits the provision of a second service to the user without performing identity verification if the subscriber and the user are the same person, and does not permit the provision of the second service to the user if the subscriber and the user are not the same person, wherein the second service is a service that requires identity verification.
[0008] Furthermore, a service management system according to a preferred embodiment of the present invention includes an acquisition unit that pairs a subscriber of a first service, which requires identity verification at the time of contract, with a member of a platform service corresponding to the subscriber; and a service management unit that, if the subscriber and the member are the same person, allows the provision of the second service to the member without performing identity verification, and does not allow the provision of the second service to the member if the subscriber and the member are not the same person, wherein the platform service provides information centrally for a plurality of services, including the first service and the second service, and the second service is a service that requires identity verification. [Effects of the Invention]
[0009] According to the present invention, a method for providing a second service can be provided, assuming that the subscriber of the first service and the user of the first service are different from each other, or that the subscriber of the first service and the member of the second service corresponding to said subscriber are different from each other. [Brief explanation of the drawing]
[0010] [Figure 1] A block diagram showing the overall configuration of service management system 1A. [Figure 2] A block diagram showing an example configuration of the control device 10A. [Figure 3] A diagram showing an example configuration of a customer database CDB[1]. [Figure 4] A block diagram showing an example configuration of service provider server 20A. [Figure 5] A sequence diagram showing the first operational example of the service management system 1A. [Figure 6] A sequence diagram showing a second operational example of the service management system 1A. [Figure 7] A diagram showing an example configuration of a customer database CDB[2]. [Figure 8] A diagram showing an example configuration of a customer database CDB[3]. [Modes for carrying out the invention]
[0011] 1: First Embodiment The service management system 1A according to this embodiment will be described below with reference to Figures 1 to 6.
[0012] Conventional technology did not consider the case where a user of the first service is registered, but the subscriber of the first service and the user of the first service are different. The service management system 1A of this embodiment can provide a method for providing the second service that takes into account the case where the subscriber 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 structure Figure 1 is a block diagram showing the overall configuration of the service management system 1A according to this embodiment. As shown in Figure 1, the service management system 1A comprises a management device 10A, a service provision server 20A, and terminals 30[1] to 30[n]. The management device 10A, the service provision server 20A, and terminals 30[1] to 30[n] are connected to each other via a communication network NET so that they can communicate with one another. n is an integer greater than or equal to 1. k is an integer between 1 and n (inclusive). In the following explanation, terminals 30[1] to 30[n] may be collectively referred to as "terminal 30". In Figure 1, user U uses terminal 30. Also, user U[k] uses terminal 30[k]. Note that in Figure 1, the number of management devices 10A and service provision servers 20A being one is merely an example. The service management system 1A can be equipped with any number of management devices 10A and service provision servers 20A. The number of management devices 10A and service provision servers 20A may be the same or different.
[0014] Terminal 30 is, for example, a device used by user U to utilize the telephone function. This telephone function is an example of "Service 1". Identity verification is required when contracting for "Service 1". User U is also an example of a "user" of "Service 1". 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 electronic payment application 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 an account and can transfer the funds in the account. Here, "can 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] Furthermore, the service provider server 20A may provide the terminal 30 with an electronic payment service that does not require identity verification and is different from the "second service" described above. This electronic payment service allows payments to be made using funds in the account, and does not allow the funds to be transferred from the account. This electronic payment service is an example of the "second electronic payment service."
[0019] Furthermore, other functions that the "First Electronic Payment Service" provides to terminal 30 but the "Second Electronic Payment Service" does not provide to terminal 30 may include the transfer and withdrawal of the balance of the "First Electronic Payment Service."
[0020] The service provider server 20A provides the above-mentioned "first electronic payment service" and "second electronic payment service" to the terminal 30[k], thereby enabling user U[k] to settle the purchase price of goods or services as described above.
[0021] 1-1-2: Configuration of Control Device 10A Figure 2 is a block diagram showing an example configuration of the management device 10A. As shown in Figure 2, the management device 10A comprises a processing unit 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 one or more buses for communicating information.
[0022] The processing unit 11 is a processor that controls the entire management device 10A. The processing unit 11 is configured using, for example, one or more chips. The processing unit 11 is also configured using a central processing unit (CPU) that includes, for example, interfaces with peripheral devices, an arithmetic unit, and registers. Some or all of the functions of the processing unit 11 may be implemented by hardware such as a DSP (Digital Signal Processor), ASIC (Application Specific Integrated Circuit), PLD (Programmable Logic Device), and FPGA (Field Programmable Gate Array). The processing unit 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, non-volatile memory and volatile memory. Non-volatile memory is, for example, ROM (Read Only Memory), EPROM (Erasable Programmable Read Only Memory), and EEPROM (Electrically Erasable Programmable Read Only Memory). Volatile memory is, for example, RAM (Random Access Memory). The storage device 12 also functions as a work area for the processing device 11. The storage device 12 also 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 that stores data about a customer. This customer is user U on terminal 30.
[0025] Figure 3 shows an example of the configuration of the customer database CDB[1]. The customer database CDB[1] stores customer data CDS. The customer data CDS has the following fields: "Data ID", "Terminal ID", "Subscriber", and "User". "Data ID" is the identifier for each customer data CDS. "Terminal ID" is the identifier for identifying terminals 30[1] to 30[n]. "Subscriber" is the subscriber of the "First Service" available on terminal 30 indicated by the "Terminal ID". If the "First Service" is the telephone function of terminal 30, "Subscriber" is the line subscriber for the telephone line used by that telephone function. "User" is the user of the "First Service" available on terminal 30 indicated by the "Terminal ID". If the "First Service" is the telephone function of terminal 30, "User" is the line user for the telephone line used by that telephone function. Note that in Figure 3, for the sake of simplicity, the "Subscriber" data is shown with initials. However, in practice, the "contractor" data is shown with their full name. Alternatively, the "contractor" data may be shown with an identifier that identifies the "contractor." The same applies to the "user" data.
[0026] In the customer database CDB[1] illustrated in Figure 3, for example, in customer data CDS with "Data ID" "001", the "Contractor" and "User" match. On the other hand, for example, in customer data CDS with "Data ID" "002", the "Contractor" and "User" do not match.
[0027] In Figure 2, the communication device 13 is hardware acting as a transmitting and receiving device for communicating with other devices. The communication device 13 is also called, for example, a network device, network controller, network card, or communication module. The communication device 13 may be equipped with a connector for wired connection and an interface circuit corresponding to the above-mentioned connector. The communication device 13 may also be equipped with a wireless communication interface. Examples of connectors and interface circuits for wired connection include products compliant with wired LAN, IEEE 1394, and USB. Examples of wireless communication interfaces include products compliant with wireless LAN and Bluetooth®.
[0028] The display device 14 is a device that displays images and text information. The display device 14 displays various images under the control of the processing unit 11. For example, various display panels such as liquid crystal display panels and organic EL display panels 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 is configured to include a keyboard, touchpad, touch panel, or pointing device such as a mouse. If the input device 15 is configured to include a touch panel, it may also serve as the display device 14.
[0030] The processing unit 11 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.
[0031] The communication control unit 111 causes the communication device 13 to send and receive various types of data with other devices.
[0032] The reception unit 112 receives a request from the service provision server 20A to determine whether the subscriber and user of the "first service" used at terminal 30[k] are the same person.
[0033] Furthermore, the reception unit 112 directly receives identity verification requests from terminal 30[k]. These identity verification requests include a request to determine whether the subscriber and user of the "First Service" used by terminal 30[k] are the same person.
[0034] The request for the above determination includes data indicating the "terminal ID," which is the identifier of terminal 30[k].
[0035] When the reception unit 112 receives a request for determination, the acquisition unit 113 uses the "terminal ID," which is the identifier of the terminal 30[k] included in the determination request, to refer to the customer database CDB[1] and extract customer data CDS containing the "terminal ID." Furthermore, the acquisition unit 113 acquires the pairs of subscribers and users included in the extracted customer data CDS. In other words, the acquisition unit 113 acquires the pairs of subscribers of the "first service" that require identity verification at the time of contract and the users of the "first service" corresponding to those subscribers.
[0036] For example, if the identifier of terminal 30[k] is "A2875", the acquisition unit 113 acquires a pair of "HA" as the "contractor" and "HA" as the "user". As another example, if the identifier of terminal 30[k] is "K1973", the acquisition unit 113 acquires a pair of "TO" as the "contractor" and "SH" as the "user".
[0037] The determination unit 114, triggered by the reception unit 112 receiving the request for the above determination, determines whether the "contractor" and "user" in the pair of "contractor" and "user" acquired by the acquisition unit 113 are the same person.
[0038] Furthermore, if the reception unit 112 receives the above-mentioned request for identity verification, the determination unit 114, triggered by the reception unit 112 receiving the above-mentioned request for identity verification, determines whether the "contractor" and "user" in the pair of "contractor" and "user" acquired by the acquisition unit 113 are the same person.
[0039] For example, as described above, if the acquisition unit 113 acquires a pair of "HA" as the "contractor" and "HA" as the "user", the determination unit 114 determines that the "contractor" and the "user" are the same person. In another example, if the acquisition unit 113 acquires a pair of "TO" as the "contractor" and "SH" 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 determination result determined by the determination unit 114 to be transmitted to the communication device 13 for use with other devices.
[0041] When the reception unit 112 receives the above determination request from the service provision server 20A, the communication control unit 111 causes the service provision server 20A to transmit the above determination result to the communication device 13. If the reception unit 112 receives a request for identity verification directly from terminal 30[k], the communication control unit 111 causes the communication device 13 to send the above determination result, along with the identity verification result, to terminal 30[k].
[0042] 1-1-3: Configuration of Service Provider Server 20A Figure 4 is a block diagram showing an example configuration of the service provision server 20A. As shown in Figure 4, the service provision server 20A comprises a processing unit 21, a storage device 22, a communication device 23, a display device 24, and an input device 25. Each element of the service provision server 20A is interconnected by one or more buses for communicating information.
[0043] The processing unit 21 is a processor that controls the entire service provision server 20A. The processing unit 21 is configured using, for example, one or more chips. The processing unit 21 is also configured using a central processing unit (CPU) that includes, for example, interfaces with peripheral devices, arithmetic units and registers. Some or all of the functions of the processing unit 21 may be implemented by hardware such as a DSP (Digital Signal Processor), ASIC (Application Specific Integrated Circuit), PLD (Programmable Logic Device), and FPGA (Field Programmable Gate Array). The processing unit 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, non-volatile memory and volatile memory. Non-volatile memory is, for example, ROM (Read Only Memory), EPROM (Erasable Programmable Read Only Memory), and EEPROM (Electrically Erasable Programmable Read Only Memory). Volatile memory is, for example, RAM (Random Access Memory). The storage device 22 also functions as a work area for the processing device 21. The storage device 22 also stores the control program PR2 that the processing device 21 executes.
[0045] The communication device 23 is hardware acting as a transmitting and receiving device for communicating with other devices. The communication device 23 is also called, for example, a network device, network controller, network card, or communication module. The communication device 23 may be equipped with a connector for wired connection and an interface circuit corresponding to the above-mentioned connector. The communication device 23 may also be equipped with a wireless communication interface. Examples of connectors and interface circuits for wired connection include products compliant with wired LAN, IEEE1394, and USB. Examples of wireless communication interfaces include products compliant with wireless LAN and Bluetooth®.
[0046] The display device 24 is a device that displays images and text information. The display device 24 displays various images under the control of the processing device 21. For example, various display panels such as liquid crystal display panels and organic EL display panels 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 provision server 20A. For example, the input device 25 is configured to include a keyboard, touchpad, touch panel, or pointing device such as a mouse. If the input device 25 is configured to include a touch panel, it may also function as the display device 24.
[0048] The processing unit 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 instructs the communication device 23 to send and receive various types of data with other devices. As an example, the communication control unit 211 causes the communication device 23 to receive a request from terminal 30[k] to use the "second service". This request to use the "second service" includes the request for the above determination. The communication control unit 211 causes the management device 10A to transmit the above determination request to the communication device 23.
[0050] Furthermore, 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 terminal 30[k]. For example, if the determination result received from the management device 10A indicates that the subscriber and the user are the same person, the service management unit 212 permits providing the "second service" to the user without verifying their identity. On the other hand, if the determination result received from the management device 10A does not indicate that the subscriber and the user are the same person, the service management unit 212 does not permit providing the "second service" to the user.
[0052] Specifically, when the service provision server 20A sends a request for determination to the management device 10A, and the management device 10A receives a determination result indicating that the subscriber and the user are the same person, the service management unit 212 causes the communication device 23 to send configuration data to enable the "second service" to terminal 30[k] without performing identity verification. On the other hand, if the above determination result does not indicate that the subscriber and the user are the same person, the service management unit 212 does not cause the communication device 23 to send configuration data to enable the "second service" to terminal 30[k]. As a result, user U[k] cannot use the "second service" on terminal 30[k]. In this case, the service management unit 212 causes the communication device 23 to send an error message to terminal 30[k]. This error message is displayed on terminal 30[k].
[0053] As described above, if the Service Management Department 212 provides the "Second Service" to the above-mentioned user without verifying their identity, and then a discrepancy is found between the above-mentioned subscriber and the above-mentioned user, the Service Management Department 212 may, for example, suspend the provision of the "Second Service" to the above-mentioned user.
[0054] As another example, if user U[k], as a user as described above, sends a request for identity verification from terminal 30[k] to management device 10A before starting to use the "second service," and the above determination result indicates that the subscriber 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, if the above determination result does not indicate that the subscriber 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, terminal 30[k] sends a request for identity verification to the management device 10A, and if the above determination result indicates that the subscriber and the user are the same person, the management device 10A also sends the determination result to the service provision server 20A. Upon receiving the determination result, the service management unit 212 causes terminal 30[k] to send configuration data to the communication device 23 so that the "second service" can be used. On the other hand, if the above determination result does not indicate that the subscriber and the user are the same person, the management device 10A also transmits the determination result to the service provision server 20A. Based on the determination result, the service management unit 212 does not have the communication device 23 send configuration data to terminal 30[k] to enable the "second service". As a result, user U[k] cannot use the "second service" on terminal 30[k]. In this case, the service management unit 212 has the communication device 23 send an error message to terminal 30[k]. This error message is displayed on terminal 30[k].
[0056] If the Service Management Department 212 does not permit the provision of the "Second Service," i.e., the "First Electronic Payment Service" which requires identity verification, to the above-mentioned user, the Service Management Department 212 may, as an example, permit the provision of the "Second Electronic Payment Service" which does not require identity verification to the said user.
[0057] 1-2: Operation of the First Embodiment 1-2-1: First example of operation Figure 5 is a sequence diagram showing a first example of operation of the service management system 1A according to the first embodiment.
[0058] In step S1, terminal 30[k] sends a request to the service provider server 20A to use the "second service".
[0059] In step S2, the service provider server 20A sends a request to the management device 10A to determine whether the subscriber and user of the "first service" used at terminal 30[k] are the same person. In step S2, the processing unit 11 of the management device 10A functions as a reception unit 112. The processing unit 11 receives a request from the service provision server 20A to determine whether the subscriber and user of the "first service" are the same person.
[0060] In step S3, the management device 10A determines whether the subscriber and user of the "first service" used by terminal 30[k] are the same person.
[0061] Specifically, the processing unit 11 provided in the management device 10A functions as an acquisition unit 113. The processing unit 11 acquires pairs of subscribers to the "first service" and users of the "first service" corresponding to those subscribers. Furthermore, the processing unit 11 functions as a determination unit 114. The processing unit 11 determines whether the "contractor" and "user" in the pair of "contractor" and "user" acquired by the acquisition unit 113 are the same person.
[0062] In step S4, the management device 10A transmits to the service provision server 20A the determination result determined by the processing unit 11 as it functions as the determination unit 114.
[0063] In step S5, the service provider server 20A sends the "second service" configuration data or error message to the terminal 30[k] based on the determination result received in step S4.
[0064] Specifically, the processing unit 21 functions as a service management unit 212. If the above determination result indicates that the subscriber and the user are the same person, the processing unit 21 causes the communication device 23 to send configuration data to terminal 30[k] to enable the "second service" without verifying the identity of the user. On the other hand, if the above determination result does not indicate that the subscriber and the user are the same person, the processing unit 21 does not cause the communication device 23 to send configuration data to terminal 30[k] to enable the "second service". In this case, the processing unit 21 causes the communication device 23 to send an error message to terminal 30[k]. This error message is displayed on terminal 30[k].
[0065] 1-2-2: Second example of operation Figure 6 is a sequence diagram showing a second example of operation of the service management system 1A according to the above embodiment.
[0066] In step S11, terminal 30[k] sends a request for identity verification to management device 10A.
[0067] In step S11, the processing unit 11 of the management device 10A functions as a reception unit 112. The processing unit 11 receives a request for identity verification from the terminal 30[k].
[0068] In step S12, the management device 10A verifies the identity of the user and determines whether the subscriber and user of the "first service" used by terminal 30[k] are the same person.
[0069] Specifically, the processing unit 11 provided in the management device 10A functions as an acquisition unit 113. The processing unit 11 acquires pairs of subscribers to the "first service" and users of the "first service" corresponding to those subscribers. Furthermore, the processing unit 11 functions as a determination unit 114. The processing unit 11 determines whether the "contractor" and "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 identity verification and the determination result determined by the processing device 11 as it functions as a determination unit 114.
[0071] Although not shown in Figure 7, the management device 10A may also transmit the above determination result to the service provision server 20A.
[0072] When the management device 10A transmits the above determination result to the service provision server 20A, the processing unit 21 provided in the service provision server 20A functions as a service management unit 212. If the above determination result indicates that the subscriber and the user are the same person, the processing unit 21 permits the provision of the "second service" to the user. On the other hand, if the above determination result does not indicate that the subscriber and the user are the same person, the processing unit 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 this embodiment comprises an acquisition unit 113 and a service management unit 212. The acquisition unit 113 acquires a pair of a subscriber to the first service, which requires identity verification at the time of contract, and a user of the first service corresponding to that subscriber. If the subscriber and the user are the same person, the service management unit 212 allows the provision of the second service to the user without performing identity verification. If the subscriber and the user are not the same person, the service management unit 212 does not allow the provision of the second service to the user. The second service is a service that requires identity verification.
[0074] By having the above configuration, the service management system 1A can provide a method for providing the second service, assuming that the subscriber of the first service and the user of the first service are different people.
[0075] Furthermore, the service management system 1A according to this embodiment further comprises 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 determines, based on the request, whether the above-mentioned subscriber and the above-mentioned user are the same person. If the result of the above determination is affirmative, the service management unit 212 permits the provision of the second service to the above-mentioned user. If 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 user.
[0076] By having the above configuration, the service management system 1A can control whether or not to provide the second service to the user in response to a request for identity verification from terminal 30.
[0077] Furthermore, in the service management system 1A according to this embodiment, if the service management unit 212 provides the second service to a user without performing identity verification, and then finds that the subscriber and the user do not match, it stops providing the second service to the user.
[0078] By having the above configuration, the service management system 1A can respond to situations where, after commencing the provision of the second service to a user, it becomes clear that the subscriber and the user are not the same person, without verifying whether the subscriber and the user are the same person.
[0079] Furthermore, in the service management system 1A according to this embodiment, the second service is the first electronic payment service that requires identity verification. Also, if the service management unit 212 does not permit the provision of the second service to the user, it permits the provision of the second electronic payment service that does not require identity verification.
[0080] By having the above configuration, the service management system 1A enables users who are unable to receive the first electronic payment service to receive the second electronic payment service, which serves as an alternative to the first electronic payment service.
[0081] Furthermore, in the service management system 1A according to this embodiment, the first electronic payment service allows payments using the funds in the account and allows the funds in the account to be moved. The second electronic payment service allows payments using the funds in the account, but does not allow the funds in the account to be moved.
[0082] By having the above configuration, the service management system 1A allows users to utilize more functions when using the first electronic payment service, which requires identity verification, compared to when using the second electronic payment service, which does not require identity verification.
[0083] 2: Second Embodiment The service management system 1B according to this embodiment will be described below with reference to Figure 7. For the sake of simplicity, the following description will primarily focus on the technical features of the service management system 1B that differ from those of the service management system 1A. Furthermore, for components of the service management system 1B that are identical to those of the service management system 1A, the same reference numerals will be used, and their functions may be omitted.
[0084] Conventional technology did not take into account the case where, even though a member of the second service is registered, the subscriber of the first service and the member of the second service corresponding to that subscriber are different. The service management system 1B of this embodiment can provide a method for providing the second service that takes into account the case where the subscriber of the first service and the member of the second service corresponding to that subscriber are different from each other.
[0085] In this embodiment, "service member" refers to a member of the platform service. The details of the "platform service" will be described later.
[0086] This embodiment is identical to the first embodiment except that the users of the "first service" are replaced with members of the platform service. An example of the configuration and operation of the service management system 1B according to this embodiment will be described below.
[0087] 2-1: Configuration of the second embodiment 2-1-1: Overall Structure The service management system 1B according to this embodiment is identical to the service management system 1A according to the first embodiment shown in Figure 1, except that it includes a management device 10B instead of a management device 10A and a service provision server 20B instead of a service provision server 20A. Therefore, the illustration of its overall configuration is omitted.
[0088] The terminal 30 provided in the service management system 1B has an application installed, similar to the terminal 30 in the first embodiment. This application is, for example, an application for electronic payment. In this embodiment, the "platform service" is a service that uses the application installed on the terminal 30. The platform service centrally manages information for multiple services, including the "first service" and the "second service" described above.
[0089] 2-1-2: Configuration of Control Device 10B The configuration of the management device 10B in the service management system 1B according to this embodiment is the same as that of the management device 10A shown in Figure 2, except that the storage device 12 stores customer database CDB[2] instead of customer database CDB[1], so its illustration is omitted.
[0090] The customer database CDB[2] is a database that stores data about a customer. This customer is user U on terminal 30.
[0091] Figure 7 shows an example of the configuration of the customer database CDB[2]. The customer database CDB[2] stores customer data CDS. The customer data CDS has the following fields: "Data ID", "Terminal ID", "Subscriber", and "Member". "Data ID" is the identifier for each customer data CDS. "Terminal ID" is the identifier for identifying terminals 30[1] to 30[n]. "Subscriber" is the subscriber of the "First Service" available on terminal 30 indicated by the "Terminal ID". If the "First Service" is the telephone function of terminal 30, "Subscriber" is the line subscriber for the telephone line used by that telephone function. "Member" is a member of the platform service available on terminal 30 indicated by the "Terminal ID". If the platform service is a service using an electronic payment application for terminal 30, "Member" is a member who can use that application. Note that in Figure 7, for the sake of simplicity, the "Subscriber" data is shown with initials. However, in reality, the "Subscriber" data is shown with the full name. Alternatively, the data for "contractors" may be represented by an identifier that identifies the "contractor." The same applies to the data for "members."
[0092] In the customer database CDB[2] illustrated in Figure 7, for example, in customer data CDS with "Data ID" "001", the "Contractor" and "Member" match. On the other hand, in customer data CDS with "Data ID" "002", for example, the "Contractor" and "Member" do not match.
[0093] The processing unit 11 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 in the first embodiment, the reception unit 112 in this embodiment receives a request from the service provision server 20A to determine whether the subscriber of the "first service" used at terminal 30[k] and the member of the platform service corresponding to that subscriber are the same person.
[0095] Furthermore, the reception unit 112 directly receives identity verification requests from terminal 30[k]. These identity verification requests include a request to determine whether the subscriber of the "First Service" used by terminal 30[k] and the member of the platform service corresponding to that subscriber are the same person.
[0096] Unlike the acquisition unit 113 in the first embodiment, the acquisition unit 113 in this embodiment, when the reception unit 112 receives a request for determination, uses the identifier of terminal 30[k] included in the determination request to refer to the customer database CDB[2] and extracts customer data CDS containing said identifier. Furthermore, the acquisition unit 113 acquires the pairs of subscribers and members included in the customer data CDS. In other words, the acquisition unit 113 acquires pairs of subscribers of the "first service" that require identity verification at the time of contract and members of the platform service corresponding to said subscribers.
[0097] Unlike the determination unit 114 in the first embodiment, the determination unit 114 in this embodiment, triggered by the reception unit 112 receiving the request for the above determination, determines whether the "contractor" and "member" in the pair of "contractor" and "member" acquired by the acquisition unit 113 are the same person. Furthermore, if the reception unit 112 receives the above-mentioned request for identity verification, the determination unit 114, triggered by the reception unit 112 receiving the above-mentioned request for identity verification, determines whether the "contractor" and "member" in the pair of "contractor" and "member" acquired by the acquisition unit 113 are the same person.
[0098] 2-1-3: Configuration of Service Provider Server 20B The configuration of the service provision server 20B included in the service management system 1B according to this embodiment is the same as the configuration of the service provision server 20A shown in Figure 4, so its illustration is omitted.
[0099] The processing unit 11 in the service provision 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 in the first embodiment, the service management unit 212 in this embodiment allows the provision of the "second service" to a member without identity verification if the determination result received from the management device 10B indicates that the subscriber and the member are the same person. On the other hand, the service management unit 212 does not allow the provision of the "second service" to a member if the determination result received from the management device 10B does not indicate that the subscriber and the member are the same person.
[0101] As described above, if the Service Management Department 212 provides the "Second Service" to the above member without verifying their identity, and then a discrepancy is found between the above-mentioned contractor and the above-mentioned member, the Service Management Department 212 may, as an example, suspend the provision of the "Second Service" to the above-mentioned member.
[0102] As another example, if user U[k], as a member, sends a request for identity verification from terminal 30[k] to management device 10B before starting to use the "second service," and the above determination result indicates that the subscriber and the member are the same person, the service management unit 212, unlike the service management unit 212 according to the first embodiment, permits the provision of the "second service" to the member. On the other hand, if the above determination result does not indicate that the subscriber and the member are the same person, the service management unit 212 does not permit the provision of the "second service" to the member.
[0103] If the Service Management Department 212 does not permit the provision of the "Second Service," i.e., the "First Electronic Payment Service" which requires identity verification, to the above-mentioned member, the Service Management Department 212 may, as an example, permit the provision of the "Second Electronic Payment Service" which does not require identity verification to the said member.
[0104] 2-2: Operation of the second embodiment The first operational example of the service management system 1B according to this embodiment is identical to the first operational example of the service management system 1A according to the first embodiment, except that "user" is replaced with "member," so its illustration and description are omitted. Similarly, the second operational example of the service management system 1B according to this embodiment is identical to the second operational example of the service management system 1A according to the first embodiment, except that "user" is replaced with "member," so its illustration and description are omitted.
[0105] 2-3: Effects of the second embodiment The service management system 1B according to this embodiment comprises an acquisition unit 113 and a service management unit 212. The acquisition unit 113 acquires pairs of subscribers to the first service, which require identity verification at the time of contract, and members of the platform service corresponding to the subscribers. The service management unit 212 permits the provision of the second service to the member without performing identity verification if the subscriber and the member are the same person. The service management unit 212 also does not permit the provision of the second service to the member if the subscriber and the member are not the same person. The platform service provides information centrally for multiple services, including the first service and the second service. The second service is a service that requires identity verification.
[0106] The service management system 1B according to this embodiment, having the above configuration, can provide a method for providing a second service, assuming that the subscriber of the first service and the member of the platform service are different people.
[0107] Furthermore, the service management system 1B according to this embodiment further comprises 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, based on the request, whether the above-mentioned contractor and the above-mentioned member are the same person. If 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. If 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 or not to provide the second service to a member in response to a request for identity verification from terminal 30.
[0109] Furthermore, in the service management system 1B according to this embodiment, if the service management unit 212 provides the second service to a member without performing identity verification, and then finds that the contracting party and the member do not match, it stops providing the second service to the member.
[0110] By having the above configuration, the service management system 1B can respond to situations where, after commencing the provision of the second service to a member, it becomes clear that the subscriber and the member are not the same person, without verifying whether the subscriber and the member are the same person.
[0111] Furthermore, in the service management system 1B according to this embodiment, the second service is a first electronic payment service that requires identity verification. Also, if the service management unit 212 does not permit the provision of the second service to a member, it 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 makes it possible for members who are unable to receive the first electronic payment service to receive the second electronic payment service, which serves as an alternative to the first electronic payment service.
[0113] Furthermore, in the service management system 1B according to this embodiment, the first electronic payment service allows payments using the funds in the account and allows the funds in the account to be moved. The second electronic payment service allows payments using the funds in the account, but does not allow the funds in the account to be moved.
[0114] By having the above configuration, the service management system 1B allows users to utilize more functions when using the first electronic payment service, which requires identity verification, compared to when using the second electronic payment service, which does not require identity verification.
[0115] 3: Variant This disclosure is not limited to the embodiments illustrated above. Specific variations are illustrated below. Two or more embodiments may be arbitrarily selected from the following examples.
[0116] 3-1: Variation 1 Figure 8 shows an example configuration of a customer database CDB[3] stored in the storage device 12 of the management device 10A in this modified example, instead of the customer database CDB[1] according to the first embodiment. The customer data CDS stored in customer database CDB[3] differs from the customer data CDS stored in customer database CDB[1] according to the first embodiment in that it does not have a "user" item.
[0117] In the service management system 1A according to the first embodiment, a request for determination including the terminal ID of terminal 30[k] was directly transmitted from terminal 30[k] to the management device 10A. Alternatively, a request for determination including the terminal ID of terminal 30[k] was indirectly transmitted from terminal 30[k] to the management device 10A via the service provision server 20A. Then, the acquisition unit 113 in the management device 10A used the "terminal ID" to refer to the customer database CDB[1] and extracted customer data CDS containing the "terminal ID". Furthermore, the acquisition unit 113 acquired the subscriber and user pairs included in the customer data CDS.
[0118] On the other hand, in this modified example, terminal 30[k] stores user data indicating user U[k], and the request for the above determination includes the user data in addition to the "customer ID". The acquisition unit 113 in the management device 10A uses the "terminal ID" to refer to the customer database CDB[3] and extracts customer data CDS that includes the "terminal ID". Furthermore, the acquisition unit 113 acquires the subscribers 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, terminal 30[k] stores member data indicating user U[k] who is a member of the platform service, and the request for the above determination may include the member data in addition to the "customer ID". The acquisition unit 113 in the management device 10A uses the "terminal ID" to refer to the customer database CDB[4] (not shown) and extracts customer data CDS that includes the "terminal ID". Furthermore, the acquisition unit 113 acquires the members included in the customer data CDS.
[0121] Then, the determination unit 114 determines whether the "contractor" acquired by the acquisition unit 113 and the "member" indicated by the member data included in the determination request are the same person. 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: Variation 2 In the service management system 1A according to the first embodiment, when the service provision server 20A receives a determination result from the management device 10A indicating that the subscriber and the user are the same person, the service management unit 212 causes the communication device 23 to send configuration data to the terminal 30[k] so that the "second service" can be used.
[0123] However, the service management unit 212 may have the communication device 23 send configuration data to an application management server (not shown) that manages applications installed on terminal 30[k], rather than to terminal 30[k] itself, so that the "second service" can be used on terminal 30[k].
[0124] The same applies to the service management system 1B according to the second embodiment.
[0125] 3-3: Modification 3 In the embodiments described above, the "second service" was, for example, an electronic payment service. However, the "second service" may be any other service. For example, the "second service" may be an account opening service for opening a bank account to be used with the electronic payment service.
[0126] 4: Other (1) In the embodiments described above, the storage devices 12 and 22 were exemplified as ROM and RAM, but other suitable storage media include flexible disks, magneto-optical disks (e.g., compact disks, digital multipurpose disks, Blu-ray® disks), smart cards, flash memory devices (e.g., cards, sticks, key drives), CD-ROMs (Compact Disc-ROMs), registers, removable disks, hard disks, floppy® disks, magnetic strips, databases, servers, and other appropriate storage media.
[0127] (2) In the embodiments described above, the information, signals, etc. may be represented using any of the various different techniques. For example, the data, instructions, commands, information, signals, bits, symbols, chips, etc. that may be mentioned 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 embodiments described above, the input and output information may be stored in a specific location (e.g., memory) or managed using a management table. The input and output information may be overwritten, updated, or appended to. The output information may be deleted. The input information may be transmitted to other devices.
[0129] (4) In the embodiments described above, the determination may be made by a value represented using 1 bit (0 or 1), by a boolean value (true or false), or by a numerical comparison (for example, a comparison with a predetermined value).
[0130] (5) The processing procedures, sequences, flowcharts, etc., exemplified in the embodiments described above may be rearranged in order, as long as they do not contradict each other. For example, the methods described in this disclosure present various step elements using an exemplary order and are not limited to the specific order presented.
[0131] (6) Each function illustrated in Figures 1 to 8 is implemented by any combination of at least one of hardware and software. Furthermore, the method of implementing each functional block is not particularly limited. That is, each functional block may be implemented using one device that is physically or logically coupled, or it may be implemented using two or more physically or logically separated devices that are directly or indirectly connected (for example, using wired or wireless connections). A functional block may also be implemented by combining the above one device or the above multiple devices with software.
[0132] (7) The programs illustrated in the embodiments described above should be broadly interpreted to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures, functions, etc., whether they are called software, firmware, middleware, microcode, hardware description languages or by other names.
[0133] Furthermore, software, instructions, information, etc., may be transmitted and received via a transmission medium. For example, if software is transmitted from a website, server, or other remote source using at least one of wired technology (such as coaxial cable, fiber optic cable, twisted pair, or digital subscriber line (DSL)) and wireless technology (such as infrared or microwave), then at least one of these wired and wireless technologies is included in the definition of a transmission medium.
[0134] (8) In each of the above-mentioned forms, the terms “system” and “network” shall be used interchangeably.
[0135] (9) The information, parameters, etc. described in this disclosure may be expressed using absolute values, relative values from a given value, or other corresponding information.
[0136] (10) In the embodiments described above, the terminal 30 may be a mobile station (MS). A mobile station may also 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 several other appropriate terms. In this disclosure, terms such as “mobile station,” “user terminal,” “user equipment (UE),” and “terminal” may be used interchangeably.
[0137] (11) In the embodiments described above, the terms “connected,” “coupled,” or any variation thereof, mean any direct or indirect connection or coupling between two or more elements, and may include the presence of one or more intermediate elements between two elements that are “connected” or “coupled” with each other. The coupling or connection between elements may be a physical coupling or connection, a logical coupling or connection, or a combination thereof. For example, “connection” may be reinterpreted as “access.” As used in this disclosure, two elements may be considered to be “connected” or “coupled” with each other using at least one of one or more wires, cables and printed electrical connections, and, in some non-limiting and non-exclusive examples, electromagnetic energy having wavelengths in the radio frequency domain, microwave domain and optical (both visible and invisible) domain.
[0138] (12) In the embodiments described above, the phrase “based on” does not mean “based solely on” unless otherwise specified. In other words, the phrase “based on” means both “based solely on” and “based at least on.”
[0139] (13) The terms “determining” and “determining” as used in this disclosure may encompass a wide variety of actions. “Determining” may include, for example, judging, calculating, computing, processing, deriving, investigating, looking up, searching, inquiry (e.g., searching in a table, database or other data structure), and ascertaining. “Determining” may also include, for example, receiving (e.g., receiving information), transmitting (e.g., sending information), input, output, and accessing (e.g., accessing data in memory). Furthermore, "judgment" and "decision" can include considering something as having been "judged" or "decided" after resolving, selecting, choosing, establishing, comparing, etc. In other words, "judgment" and "decision" can include considering something as having been "judged" or "decided" after some action. Also, "judgment (decision)" can be reinterpreted as "assuming," "expecting," or "considering."
[0140] (14) Where the terms “include,” “including,” and variations thereof are used in the embodiments described above, these terms are intended to be inclusive, as is the term “comprising.” Furthermore, the term “or” as used in this disclosure is not intended to be exclusive OR.
[0141] (15) In the present disclosure, if articles are added by translation, such as a, an, and the in English, the present disclosure may include the fact that the noun following these articles is plural.
[0142] (16) In this disclosure, the term “A and B are different” may mean “A and B are different from each other.” The term may also mean “A and B are each different from C.” Terms such as “separate” and “combine” may be interpreted in the same way as “different.”
[0143] (17) Each aspect / embodiment described herein may be used individually, in combination, or switched between as needed in practice. Furthermore, notification of certain information (e.g., notification that "X is") is not limited to explicit notification, but may also be implicit (e.g., by not providing such notification).
[0144] Although the present disclosure has been described in detail above, it will be clear to those skilled in the art that the present disclosure is not limited to the embodiments described herein. The present disclosure can be implemented in modified and altered forms without departing from the intent and scope of the present disclosure as defined by the claims. Accordingly, the descriptions in the present disclosure are illustrative and not restrictive in any way. [Explanation of symbols]
[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 Provisioning Server, 20B...Service Provisioning 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...Determination 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 to the first service who requires identity verification at the time of contract and a user of the first service corresponding to the subscriber, The system includes a service management unit that, if the subscriber and the user are the same person, permits the provision of the second service to the user without performing identity verification, and does not permit the provision of the second service to the user if the subscriber and the user are not the same person. The second service mentioned above is a service that requires identity verification. Service management system.
2. An acquisition unit that acquires a pair of a subscriber to the first service, which requires identity verification at the time of contract, and a member of the platform service corresponding to the said subscriber, A service management unit which, if the contracting party and the member are the same person, permits the provision of the second service to the member without performing identity verification, and if the contracting party and the member are not the same person, does not permit the provision of the second service to the member. The platform service provides information in a unified manner for multiple services, including the first service and the second service. The second service mentioned above is a service that requires identity verification. Service management system.
3. Before the user begins using the second service, a reception desk receives a request for identity verification from the terminal used by the user, A determination unit determines whether the contractor and the user are the same person, triggered by the aforementioned request. Furthermore, The aforementioned service management department, If the result of the above determination is positive, the provision of the second service to the user is permitted. If the result of the above determination is negative, the provision of the second service to the user is not permitted. The service management system according to claim 1.
4. Before the member begins using the second service, a reception desk receives a request for identity verification from the terminal used by the member, A determination unit determines whether the aforementioned contractor and the aforementioned member are the same person, triggered by the aforementioned request. Furthermore, The aforementioned service management department, If the result of the above determination is affirmative, the second service will be permitted to be provided to the member. If the result of the above determination is negative, the provision of the second service to the member shall not be permitted. The service management system according to claim 2.
5. The service management system according to claim 1, wherein the service management unit provides the second service to the user without performing identity verification, and if a mismatch is found between the subscriber and the user, the service management unit suspends the provision of the second service to the user.
6. The service management system according to claim 2, wherein the service management unit provides the second service to the member without performing identity verification, and if a mismatch is found between the contracting party and the member, the service management unit suspends the provision of the second service to the member.
7. The aforementioned second service is the first electronic payment service that requires identity verification. If the Service Management Department does not permit the provision of the second service to the user, it permits the provision of a second electronic payment service that does not require identity verification. The service management system according to claim 1.
8. The aforementioned second service is the first electronic payment service that requires identity verification. If the Service Management Department does not permit the provision of the second service to the member, it permits the provision of a second electronic payment service that does not require identity verification. The service management system according to claim 2.
9. The aforementioned first electronic payment service allows payments to be made using funds in an account, and allows funds to be transferred from the account. The aforementioned second electronic payment service allows payments to be made using funds in the account, and the funds in the account cannot be moved. The service management system according to claim 7.
10. The aforementioned first electronic payment service allows payments to be made using funds in an account, and allows funds to be transferred from the account. The aforementioned second electronic payment service allows payments to be made using funds in the account, and the funds in the account cannot be moved. The service management system according to claim 8.