Service delivery support methods and programs

Abstract

To provide a configuration capable of further enhancing security when providing personal information such as information on a physical disability certificate for service provisions.SOLUTION: A service provision support method according to one embodiment of the present disclosure comprises the steps of: acquiring information identifying a service transaction pertaining to service provision by a service provision system and information identifying a first user among one or a plurality of users via an application that has authenticated the first user; extracting personal information of the first user from a management system for managing personal information based on the information identifying the first user; and providing the information identifying the service transaction and the personal information of the first user to the service provision system.SELECTED DRAWING: Figure 12

Description

Technical Field

[0001] The present disclosure relates to methods and programs for supporting disabled persons and the like.

Background Art

[0002] In recent years, portable information terminals such as mobile phones have come to be used as devices for storing electronically processed tickets, certificates, payment information, and the like. Therefore, various technologies for securing such stored information in portable information terminals have been proposed, and some have been put into practical use (see, for example, Patent Document 1).

[0003] On the other hand, conventionally, services have been provided that discount the prices of various tickets by presenting a disabled person's handbook or the like. In this service, the service provider visually checks the disabled person's handbook presented by the user and determines whether to provide services such as a discount on the fee to the user. On the other hand, in order to automate the discount, there is a technology for providing a service in which the user reads a personal identification number card and a settlement card into a device set on the facility side to settle the discounted fee (see, for example, Patent Document 2).

[0004] Under such circumstances, the present applicant proposes a configuration for supporting disabled persons (see Patent Document 3). In the technology of Patent Document 3, when a part or all of the first information regarding a disabled person is held and the connection to the system under the management of a public organization using the authentication information owned by the disabled person is successful, the server device transmits the permission information sent from the server device to the system, which is required when the server device acquires the second information regarding the disabled person from the system, to the server device, receives matching information including information on whether the first information and the second information match from the server device, and causes the terminal device to execute a process of displaying a part or all of the first information and the matching information.

Prior Art Documents

Patent Documents

[0005] [Patent Document 1] Patent No. 4572519 [Patent Document 2] Japanese Patent Publication No. 2015-95153 [Patent Document 3] Patent No. 6851660 [Overview of the project] [Problems that the invention aims to solve]

[0006] Incidentally, it is conceivable that automated ticket machines could, for example, read information from a disability certificate to apply discounts. However, there are security management issues with automated ticket machines themselves, and providing information from disability certificates to these machines presents challenges.

[0007] This disclosure aims to provide a configuration that enhances security and supports the provision of more convenient services when providing personal information, such as information from a disability certificate, for the provision of services at automated payment machines and the like. [Means for solving the problem]

[0008] The first aspect of this disclosure is: Information identifying a service transaction related to service provision by a service provision system, and information identifying a first user among one or more users, are obtained through an application that accepts instructions from the first user who authenticates the first user. Based on the information that identifies the first user, the personal information of the first user is extracted from a management system that manages personal information, Providing the service provision system with information identifying the service transaction and the personal information of the first user, Equipped with Service delivery support methods To provide.

[0009] Preferably, the service provider is provided with information that identifies the service transaction and the personal information of the first user, so that the service provider provides the service provider with added value relating to the first user for the provision of the service.

[0010] Preferably, the service provision support method described above further comprises obtaining information identifying the service transaction and information identifying a second user among the one or more users via an application that accepts instructions from the second user authenticating the second user, wherein the extraction extracts the personal information of the second user from the management system based on the information identifying the second user, and the provision to the service provision system provides the information identifying the service transaction and the personal information of the second user to the service provision system.

[0011] Preferably, providing information to the service provision system includes providing only personal information of predetermined items in accordance with the service provision, which pertain to information identifying the service transaction among the stored personal information.

[0012] Preferably, the application further includes requesting the application to transmit a prompt to the authenticated user, prompting the user to enter an indication of intent to authorize the provision of the authenticated user's personal information to the service provider system, before providing it to the service provider system.

[0013] Preferably, the personal information includes information from at least one of the following: information from a physical disability certificate, information from a mental disability health and welfare certificate, and information from an intellectual disability certificate.

[0014] A second aspect of this disclosure is: In service provision by a service provision system, a method of providing personal information of a user to the service provision system so as to enable the service provision system to give added value related to the user who receives the service provision to the service transaction related to the service provision, obtaining information for specifying the service transaction; providing information for specifying the user and information for specifying the service transaction to a management system that is communicable with the service provision system and manages the personal information so as to send the personal information corresponding to the obtained information for specifying the service transaction to the service provision system; including a method is provided.

[0015] Preferably, obtaining information for specifying the service transaction further includes obtaining information for specifying the service transaction from the side of other users using the service transaction.

[0016] Preferably, it further includes transmitting a prompt that prompts the user to input a consent to provide the personal information corresponding to the obtained information for specifying the service transaction to the service provision system.

[0017] In the method of the second aspect, the personal information may include at least any one of information of a physical disability handbook, information of a mental disability health and welfare handbook, and information of a rehabilitation handbook.

[0018] The present disclosure also provides a program for causing a computer to execute the method of the first aspect or the method of the second aspect.

Advantages of the Invention

[0019] According to the disclosed technology, when providing personal information such as the information in the Disability Handbook for service provision, it becomes possible to enhance security and support the provision of a more convenient service.

Brief Description of the Drawings

[0020] [Figure 1] Example of the Disability Handbook [Figure 2] Overall Configuration of the Disability Support System in the First Embodiment [Figure 3] Hardware Block Diagram of the Terminal Device [Figure 4] Hardware Block Diagram of the Disability Service Support Server [Figure 5] Software Block Diagram of the Terminal Device [Figure 6] Software Block Diagram of the Disability Service Support Server [Figure 7] Examples of Personal Information Read from the Disability Handbook and Original Disability Handbook Information <00利用可能なメモリ容量が少ない場合には、メモリ容量を節約するために、前回のサービス提供におけるユーザーの利用履歴を保持しておくことができる。Flowchart of the Process Executed by the Terminal Device [Figure 9] Flowchart of the Process Executed by the Disability Service Support Server [Figure 10] Configuration Diagram of the Disability Support System in Service Provision [Figure 11] Block Diagram of the Service Provision System [Figure 12] Flowchart of Service Provision in the First Embodiment [Figure 13] Configuration Diagram of the Disability Support System in Service Provision in the Second Embodiment [Figure 14] Software Block Diagram of the Terminal Device in the Second Embodiment [Figure 15] Flowchart of Service Provision in the Second Embodiment [Figure 16] Configuration Diagram of the Disability Support System in Service Provision in the Third Embodiment<000利用可能なメモリ容量が少ない場合には、メモリ容量を節約するために、前回のサービス提供におけるユーザーの利用履歴を保持しておくことができる。 [Figure 17] Software Block Diagram of the Terminal Device in the Third Embodiment [Figure 18] Flowchart of service provision in the third embodiment [Modes for carrying out the invention]

[0021] An embodiment will be described below with reference to the drawings. First, the first embodiment will be described. However, the embodiments described below are merely illustrative and are not intended to limit the scope of the claims. Furthermore, while the embodiments described below illustrate the provision of services to users who possess a disability certificate, the certificate held by the user is not limited to a disability certificate; for example, it could be a mental disability health and welfare certificate or an intellectual disability certificate.

[0022] <Disability Certificate> First, let me explain what a disability certificate is. A disability certificate is a general term for a certificate that a person with a disability can obtain.

[0023] Figure 1 shows a physical disability certificate issued by a local government. Disability certificates come in various types depending on the type of disability, including physical disability certificates issued to people with physical disabilities, intellectual disability certificates issued to people with intellectual disabilities, and mental disability health and welfare certificates issued to people with mental illnesses. Disability certificates also include a grade indicating the degree of disability. In addition to this grade, there are also classifications called "Type 1" and "Type 2," which are mainly used for discounts on railway fares. Service providers other than railways also provide services based on the above grades or classifications. Furthermore, some services, such as taxis, may provide ancillary services such as transporting wheelchairs for people with disabilities.

[0024] For example, in the case of a disability certificate, the degree of disability is classified into grades from 1 to 6. In the example in Figure 1, a disability grade of 101 is shown to be "grade 2".

[0025] Furthermore, the example in Figure 1 shows that the passenger fare reduction 102 for the Japan Railway Company is "Type 1".

[0026] Generally, service providers visually verify the disability certificate presented by the user and decide whether or not to offer the user services such as discounts.

[0027] <Registration of disability certificate information>

[0028] <Overall structure of the disability support system> Figure 2 shows the overall configuration of the disability support system 200 for realizing the disability support services according to this embodiment. As shown in Figure 2, the disability support system 200 includes a disability service support server 210, a public server 220, a terminal device 230, and a service provision system 240.

[0029] The disability service support server 210 is a server managed by the provider of disability support services. The disability service support server 210 acquires and stores personal information, including information contained in the disability certificate, transmitted by the user (person with a disability) from the terminal device 230. The disability service support server 210 also uses permission information transmitted from the terminal device 230 held by the user to acquire the original disability certificate information from the public server 220. It then compares the personal information with the original disability certificate information and, based on the comparison results, provides matching information to the terminal device 230 held by the user. Furthermore, the disability service support server 210 manages the user's personal information, including the matching information. Here, the disability service support server 210 manages the user's personal information, including the matching information, by linking it to each user, that is, by associating it with information that identifies each user. Furthermore, the disability service support server 210 is managed by the person providing the disability support service.

[0030] The service provision system 240 is a system managed by the service provider. As will be described later in Figure 10, the service provision system 240 includes a server (hereinafter referred to as the service server) 240A, which is a computer managed by the service provider that provides ticket sales services, and a terminal device (hereinafter referred to as the service terminal) 240B that can communicate with the server 240. The services provided by the service provision system 240 are not limited to ticket sales services, but may include payment services related to the provision of various goods or services, such as parking management services. Furthermore, the service provision system 240 may be configured to include the service server 240A but not the service terminal 240B.

[0031] Public server 220 is, for example, a server managed by a public organization such as a government or local authority. Public server 220 manages various personal information, including the original disability certificate information of each user, linked to each user.

[0032] The terminal device 230 may be a mobile terminal such as a smartphone equipped with a display screen, or a laptop terminal. Although Figure 2 shows one terminal device 230, the number of terminal devices 230 in the disability support system 200 is not limited to one, but is generally multiple, and this is also true for other devices, such as the service terminal 240B in Figure 10. In this context, terminal device 230 is assumed to be in the possession of a user (a person with a disability). In the disability support system 200, a disability support program is pre-installed on terminal device 230, and the application starts up and becomes operational when this disability support program is executed. Alternatively, terminal device 230 may become operational by logging into a website or other website on the network, thereby providing the desired functions. When the user enters account information into terminal device 230 (or reads information from a card equipped with a predetermined IC chip, etc.), the application becomes an application that authenticates the user and connects to the disability service support server 210. Furthermore, the terminal device 230 can display disability information, including the above-mentioned matching information.

[0033] The disability service support server 210 and the public server 220 are connected to each other via a network 250, such as the Internet. Similarly, the disability service support server 210 and the terminal device 230 are connected to each other via a network 250, such as the Internet. The service provision system 240 is interconnected with the disability service support server 210 via a network 250, such as the Internet. The service provision system 240 may also be connected to the terminal device 230 via the network 250. In the service provision system 240, the aforementioned service server 240A and service terminal 240B are interconnected via the network 250, but they may also be connected via a dedicated line.

[0034] <Terminal device hardware configuration> Figure 3 is a block diagram showing an example of the hardware configuration of the terminal device 230. As shown in Figure 3, the terminal device 230 includes a CPU 301, a storage device 302, a display / operation unit 303, a communication unit 304, an imaging unit 305, and a memory control unit 306. The memory control unit 306 controls the storage and retrieval of information to and from the external memory 307. Examples of the external memory 307 include USB memory and memory cards. The disability support program that realizes each embodiment can be stored in the storage device 302 or the external memory 307. The application is launched by putting this disability support program into the execution state. This application authenticates the user after the user registers as a user and enters their account information.

[0035] The CPU 301 is a computing unit that comprehensively controls the entire terminal device 230. In particular, the CPU 301 executes a disability support program and provides the disability support services of this embodiment. The disability support program is executed by the CPU 301.

[0036] The storage device 302 stores various personal information of the user, disability support programs, etc. The display and operation unit 303 presents information to the user and accepts user operations. The display and operation unit 303 may have, for example, a touch panel. The communication unit 304 can control communications via the telephone network. Furthermore, the communication unit 304 may have, for example, near-field communication (NFC) to acquire information from IC cards or the like. The imaging unit 305 includes a lens 514a and an image sensor, and acquires the captured image.

[0037] <Hardware configuration of the disability service support server> Figure 4 is a block diagram showing an example of the hardware configuration of the disability service support server 210. As shown in Figure 4, the disability service support server 210 includes a CPU 401, RAM 402, ROM 403, HDD 404, network I / F 405, and the like.

[0038] The CPU 401 is a computing unit that comprehensively controls the entire disability service support server 210. The CPU 401 executes programs stored, for example, in the RAM 402, ROM 403, or HDD 404.

[0039] The HDD404 can record various types of information, including original disability certificate information and matching information. Network I / F 405 is an interface that enables communication between the public server 220, the terminal device 230, and the service provision system 240. The disability service support server 210 sends and receives information with the public server 220 and the terminal device 230 via Network I / F 405.

[0040] <Block diagram of terminal device> Figure 5 is a block diagram of the terminal device 230. The terminal device 230 includes a disability service support server connection unit 510, a public server connection unit 520, a data generation unit 530, a data storage unit 540, a screen generation unit 550, and an instruction receiving unit 570.

[0041] The disability service support server connection unit 510 includes a personal information provision unit 511, a permission information provision unit 512, a consistency information acquisition unit 513, and a provision permission unit 514. The personal information provision unit 511 transmits the user's personal information obtained from their disability certificate to the disability service support server 210. The permission information provision unit 512 transmits the permission information obtained from the public server 220 to the disability service support server 210. The consistency information acquisition unit 513 receives consistency information from the disability service support server 210, which is the result of comparing personal information with the information on the original disability certificate. The service provision authorization unit 514 transmits information to the disability service support server 210 for providing the user's personal information, preferably consistent information, obtained from the disability certificate to the service provision system 240.

[0042] The public server connection unit 520 includes an authentication request unit 521 and a permission information acquisition unit 522. The authentication request unit 521 sends the user's authentication information to the public server 220. The permission information acquisition unit 522 receives permission information from the public server 220 that allows the disability service support server 210 to access the public server 220, which is obtained as a result of transmitting the user's authentication information to the public server 220.

[0043] The data generation unit 530 generates personal information of the user (person with a disability) from the disability certificate. The data generation unit 530 may generate personal information of the user (person with a disability) from an image of the disability certificate using OCR functionality. More preferably, the data generation unit 530 may send an image of the disability certificate to the disability service support server 210, and the disability service support server 210 may receive the personal information extracted from the image of the disability certificate and generate the personal information. By having the disability service support server 210 acquire a photograph (image) of the disability certificate itself and digitize the information on the disability certificate on the disability service support server 210 side, the level of accuracy (reliability) of the digitized information on the disability certificate can be increased compared to digitizing the disability certificate using OCR or other methods on the terminal device 230. The data storage unit 540 stores various data generated by the data generation unit 530, as well as various data acquired by the disability service support server connection unit 510 and the public server connection unit 520. The screen generation unit 550 generates a display screen that includes, for example, an image of a disability certificate, information about a person with a disability including personal information written in the disability certificate, or consistency information related to the result of comparing personal information with original disability certificate information stored on the public server 220 of the public institution's system. The consistency information may include information indicating whether the results of the comparison of all items common to the personal information and the original disability certificate information matched in this comparison, as well as information indicating that the comparison has not yet been performed. The instruction receiving unit 570 receives instructions from the user (person with a disability). These instructions include instructions to display the disability information screen, verification instructions, and instructions to obtain information from the service provision system 240.

[0044] <Block diagram of the disability service support server> Figure 6 is a block diagram of the disability service support server 210. The disability service support server 210 includes a terminal device connection unit 610, a public server connection unit 620, a data storage unit 630, a data verification unit 640, and a service provision connection unit 650.

[0045] The terminal device connection unit 610 includes a personal information acquisition unit 611, a matching information provision unit 612, and an authorization information acquisition unit 613. The personal information acquisition unit 611 receives the user's personal information obtained from the disability certificate from the terminal device 230. The matching information provision unit 612 transmits matching information, which is the result of comparing personal information with original disability certificate information obtained from the public server 220, to the terminal device 230. The authorization information acquisition unit 613 receives information from the terminal device 230 that is necessary to provide personal information to the service provision system 240, i.e., authorization information.

[0046] The public server connection unit 620 has a disability certificate original information acquisition unit 621. The disability certificate original information acquisition unit 621 requests the disability certificate original information from the public server 220 and receives the disability certificate original information from the public server 220. The service provision connection unit 650 can send and receive various information related to the provision of services to and from the service provision system 240.

[0047] The data storage unit 630 can store various types of data acquired by the terminal device connection unit 610, the public server connection unit 620, and the service provision connection unit 650. The data matching unit 640 compares the personal information stored in the data storage unit 630 with the original disability certificate information obtained from the public server 220.

[0048] <Information on the original disability certificate> Figure 7 shows an example of personal information and original disability certificate information read from a disability certificate. As shown in Figure 7(b), the original disability certificate information includes, but is not limited to, the disability type / grade / issuing municipality / number / issue date / renewal date for each user (person with a disability), and may also include, for example, passenger fare reductions. The original disability certificate information is stored on a public server 220 managed by a public organization such as the government.

[0049] The disability service support server 210 stores the user's personal information obtained from the terminal device 230, linked to the user's account. The personal information managed by the disability service support server 210 includes, as shown in Figure 7(a), name, date of birth, type of disability, disability level, passenger fare reduction, issuing municipality, number, expiration date, issuance date, and renewal date. Users (people with disabilities) can register their personal information with the disability service support server 210 in advance when using disability support services. As already explained, this personal information includes data obtained from photographs of their disability certificates.

[0050] The disability service support server 210 compares personal information (Figure 7(a)) including information extracted from the disability certificate with the original disability certificate information (Figure 7(b)) received from the public server 220. In this matching process, if all items common to both the personal information and the original disability certificate information match, the disability service support server 210 generates consistency information, including that the personal information is consistent with the original disability certificate information held by the public server 220. On the other hand, if even one item does not match during this verification, the disability service support server 210 generates consistency information that includes a statement that the personal information is inconsistent with the original disability certificate information. In this case, it notifies the terminal device 230 of the inconsistency and requests that it re-acquire the image of the disability certificate, re-transmit the personal information, etc.

[0051] <Processing performed by the terminal device to generate consistency information> Figure 8 is a flowchart of the process performed by the terminal device 230. The process shown in Figure 8 is achieved when the CPU 301 of the terminal device 230 executes a disability support program installed on the terminal device 230.

[0052] As a prerequisite, users (persons with disabilities) are assumed to have registered their own accounts using their own terminal device 230 and to possess a user ID and password. Account registration is performed by connecting the terminal device 230 to the disability service support server 210. The combination of user ID and password is stored on the disability service support server 210. Note that account registration is not limited to the above process; existing SNS accounts may be used for account registration, and biometric authentication, two-factor authentication using a mobile phone, etc., may be used in combination. When registering a user, the user's name, date of birth, address, email address, telephone number, etc. may also be registered.

[0053] First, using Figure 8, we will explain the process until the terminal device 230 receives the matching information. Note that the terminal device 230 may retain default matching information until it receives matching information from the disability service support server 210. It is desirable that the default matching information includes information that has not yet been verified.

[0054] A user (person with a disability) logs in to an already registered account using their ID and password. Upon successful login, the application authenticating the user becomes operational, enabling information exchange between the terminal device 230 and the disability service support server 210 (S801). When logged in, the application authenticating the user is operational, and processes such as those shown in Figure 8 and Figure 12 become executable.

[0055] The terminal device 230 acquires personal information contained in the disability certificate owned by the user (person with a disability). This personal information may be only a portion of the information contained in the disability certificate. In addition, in connection with the acquisition of this personal information, information not contained in the disability certificate, such as information about assistive devices used by the user (person with a disability), such as whether the user uses a wheelchair, may also be acquired.

[0056] Information concerning persons with disabilities, i.e., personal information, is stored in the memory device 302 of the terminal device 230 (S802). For example, when a user captures an image of a disability certificate using the image sensor provided in the terminal device 230, the terminal device 230 obtains an image of the disability certificate from the captured image. Then, the terminal device 230 obtains the personal information (see Figure 7) written in the disability certificate through character recognition processing. The obtained personal information is transmitted to the disability service support server 210. In this character recognition process, the format of each disability certificate can be stored in advance, and the accuracy of character recognition can be improved by using the recorded format. For example, first, the system recognizes which format the disability certificate is in. For example, if it is known that the format is that of a disability certificate from Prefecture A, it is possible to predict what kind of information is written where. Therefore, by performing character recognition based on that format, more accurate character recognition can be achieved. Alternatively, as already explained, the disability service support server 210 may obtain personal information (see Figure 7) from the image of the disability certificate through character recognition processing. This personal information will be sent from the disability service support server 210 to the terminal device 230. In addition, the results of the character recognition processing on the disability service support server 210 may be combined with a visual check by an operator.

[0057] The system checks whether the user (person with a disability) has instructed the system to perform a consistency check with information from a public institution (S803). If the check is NO, the process ends. If the check is YES, the process moves to S804.

[0058] For example, terminal device 230 communicates with an IC card, which is stored at a public institution and contains authentication information that identifies the user, via short-range wireless communication provided in terminal device 230. This authentication information is received in an encrypted form via the terminal device 230 to the public server 220. If the authentication information is valid, the user's (disabled person's) operation is authenticated and a connection is established between the terminal device 230 and the public server 220 (S804).

[0059] When the user's (person with a disability) operation is authenticated (Y in S805), the terminal device 230 receives permission information from the public server 220 that allows the disability service support server 210 to access the public server 220. The terminal device 230 then forwards the received permission information to the disability service support server 210 (S806). If the user's (disabled person's) actions are not authenticated by the public server 220 (resulting in S805 as N), the process will terminate.

[0060] The disability service support server 210 receives the original disability certificate information from the public server 220 using the permission information received from the terminal device 230, and verifies whether it matches the personal information. This verification process will be described later based on Figure 9. The terminal device 320 receives the matching information, which is the result of this verification, from the disability service support server 210 (S807). If the personal information recorded in the disability certificate matches the original disability certificate information held by the public server 220, by completing the above processing, the user can present the terminal device 230 displaying the disability information with an added indication of authentication to the service provider when using services such as discounts on fees.

[0061] <Processing performed by the disability service support server when generating consistency information> Figure 9 is a flowchart of the processes performed by the disability service support server 210 when generating consistent information in the disability information support service. The process shown in Figure 9 is achieved when the CPU 401 of the disability service support server 210 executes a disability support program stored in a storage unit such as the HDD 404.

[0062] In S802 of Figure 8, when the terminal device 230 acquires personal information written in the user's (person with a disability) disability certificate, the disability service support server 210 receives the personal information from the terminal device 230. Alternatively, the disability service support server 210 may acquire the personal information written in the disability certificate by receiving an image of the disability certificate from the terminal device 230 and using its OCR function (S901).

[0063] Subsequently, in S806 of Figure 8, the terminal device 230 transfers permission information, and the disability service support server 210 receives the permission information (S902).

[0064] Upon receiving permission information, the disability service support server 210 connects to the public server 220 and retrieves the user's original disability certificate information stored on the public server 220 (S903). The disability service support server 210 then compares the personal information obtained in S901 with the original disability certificate information obtained in S903 (S904), and transmits the matching information, which is the result of the comparison, to the terminal device 230 (S905). As a result, the terminal device 230 can obtain the matching information (S807 in Figure 8). The obtained personal information (S901) and the generated matching information (S905) are also stored and retained in the disability service support server 210.

[0065] <Processing for service provision> Now, using Figures 10 to 12, we will explain the service provision in the disability support system 200.

[0066] The service provided here is a service provided by the service terminal 240B of the service provision system 240, and specifically, it is the sale of tickets. The tickets sold are admission tickets to the museum, and users with a disability certificate receive an added value in the form of a disability discount. It should be noted that ticket sales are just one example, and the service provided in this embodiment is not limited to the sale of tickets. For example, the service provided by the service terminal 240B of the service provision system 240 may be a service that allocates a dedicated parking space for people with disabilities, or it may be a variety of services that can be specially provided because of a person's disability.

[0067] In this ticket sales system, the terminal device 230 held by the user (person with a disability), the disability service support server 210, the service server 240A, and the service terminal 240B work together. More specifically, as shown in Figure 10, the terminal device 230 and the disability service support server 210 are connected to each other by a network 250, the disability service support server 210 and the service server 240A of the service provision system 240 are connected to each other by a network 250, and the service server 240A and the service terminal 240B of the service provision system 240 are connected to each other by a network 250.

[0068] When the terminal device 230 receives an instruction from the user (person with a disability) via its instruction receiving unit 570 to obtain information from the service provision system 240, it activates the provision authorization unit 514. The provision authorization unit 514 is one of the functional units of the application that authenticates the user, and transmits all or part of the user's personal information, preferably the consistent information, obtained from the disability certificate, to the disability service support server 210, that is, information to be provided to the service provision system 240. The information transmitted to the disability service support server 210 includes information that identifies the service transaction related to the service provision by the service provision system 240 (hereinafter referred to as service identification information) and information that identifies the user of this terminal device 230.

[0069] The service terminal 240B displays code 240C, which is a matrix-type two-dimensional code called QR code (registered trademark). Code 240C contains service-specific information related to the service provided by the service terminal 240B of the service provision system 240, and in particular, information that identifies the service terminal 240B. In this case, the information that identifies the service terminal 240B is the address of the service terminal 240B. If there are multiple services provided by the service terminal 240B, code 240C may also contain information that identifies one or more services provided by the service terminal 240B. Note that code 240C is not limited to a matrix-type two-dimensional code, and may also be a barcode, or information transmitted via wireless communication such as NFC.

[0070] The service authorization unit 514 of the terminal device 230 activates the imaging unit 305 to read the code 240C, or QR code, acquired through the lens 514a, and obtains service identification information. The service authorization unit 514 then links the user ID, which is information that identifies the user of the terminal device 230, to the service identification information and transmits it to the disability service support server 210. This user identification information and service identification information correspond to authorization information for providing personal information to the service provision system 240.

[0071] The authorization information acquisition unit 613 of the terminal device connection unit 610 of the disability service support server 210 receives authorization information transmitted from the terminal device 230 for providing personal information to the service provision system 240. From the acquired authorization information, the authorization information acquisition unit 613 extracts the items of the user's personal information to be provided to the service provision system 240 based on the service-specific information. The disability service support server 210 stores at least a portion of the service-specific information in relation to predetermined items of personal information depending on the service provided to the service provision system 240. Therefore, in this extraction, the data stored in the disability service support server 210 is searched based on at least a portion of the service-specific information to extract the items. In the service provision at service terminal 240B, as a discount for the ticket sales service, there is only a disability discount for holders of disability certificates, so only the item "Holds a disability certificate" included in the matching information is extracted. The authorization information acquisition unit 613 sends information (request information) to the terminal device 230 requesting confirmation of whether it is OK to provide this item of information to the service provision system 240. This request information is a request to the application to transmit a prompt to the authenticated user, prompting them to enter a declaration of intent to authorize the provision of the authenticated user's personal information to the service provision system 240. Specifically, upon receiving this request information, the application's provision authorization unit 514 in the terminal device 230 outputs a display unit 303a to the display / operation unit 303 of the terminal device 230, which displays the personal information of the items to be provided to the service provision system 240, and an input unit 303b to input the declaration of intent to authorize the provision. When the user enters a declaration of intent to authorize, the provision authorization unit 514 of the terminal device 230 transmits information indicating that declaration of intent to the disability service support server 210. As a result, the permission information acquisition unit 613 of the disability service support server 210 has fully acquired the permission information for providing personal information to the service provision system 240. The permission information thus acquired has been authenticated by the user's declaration of intent, and may therefore be called authenticated permission information. Note that the process of confirming the user's declaration of intent may be omitted.Alternatively, for example, if the user's intention is not confirmed within a certain period of time, the process may be terminated by logging out or similar actions (not shown).

[0072] Based on the acquisition of this authenticated authorization information, the user's personal information items to be provided to the service provision system 240, specifically the information "holder of a disability certificate," are transmitted along with the service-specific information to the service provision system 240 via the service provision connection unit 650, in this case to the service server 240A of the service provision system 240.

[0073] The service server 240A has a configuration similar to the disability service support server 210 described with reference to Figure 4, and includes a CPU, RAM, ROM, HDD, network I / F, etc. The CPU of the service server 240A is a computing unit that comprehensively controls the entire service provision system 240, and executes programs stored in, for example, RAM, ROM, or HDD.

[0074] Figure 11 is a block diagram of the service delivery system 240. The service server 240A of the service provision system 240 includes a disability service support server connection unit 710, a service terminal connection unit 720, a data storage unit 730, and a data verification unit 740.

[0075] The disability service support server connection unit 710 has a service provision information acquisition unit 711. The service provision information acquisition unit 711 receives information on the user's personal information items and service-specific information from the disability service support server 210.

[0076] The service terminal connection unit 720 has a verification information provision unit 721. The matching information provision unit 721 searches the database stored by the data matching unit 740 based on the information acquired by the service granting information acquisition unit 711, and transmits the matching result information (matching information) to the service terminal 240B.

[0077] The data storage unit 730 stores, in association with at least a portion of the service-specific information, items of personal information predetermined according to the service provided to the service provision system 240. For example, in the service provision of service terminal 240B, only the information "holder of a disability certificate" is required to provide the added value of a discount. The data storage unit 730 can also store various types of data acquired by the disability service support server connection unit 710. The data verification unit 740 searches the database stored in the data verification unit 740 based on the information acquired by the service provision information acquisition unit 711 and verifies whether the user's personal information necessary for providing services to the service terminal 240B is available. When the verification is complete, that is, when the verification result indicates that the user's personal information necessary for providing services to the service terminal 240B is available, the verification information provision unit 721 sends verification completion information to the service terminal 240B. When the verification is not complete, that is, when the verification result does not indicate that the user's personal information necessary for providing services to the service terminal 240B is available, the verification information provision unit 721 sends verification incomplete information to the service terminal 240B. In the case of incomplete verification, the service server 240A may return the incomplete verification information to the terminal device 230 via the disability service support server 210, or it may return it to the user of the terminal device 230 via the service terminal 240B.

[0078] The service terminal 240B includes a matching information receiving unit 750, a value-adding unit 760, and a service processing unit 770. In the service terminal 240B, the verification information receiving unit 750 receives verification information transmitted from the service server 240A. Then, the value-adding unit 760 performs processing to add value to the service provided to the user of the terminal device 230 according to the verification information received by the verification information receiving unit 750. The service processing unit 770 executes the service provision processing at the service terminal 240B of the service provision system 240, and if there is a value-adding process for that service provision, it executes the processing for providing the service with that value added. In this case, when selling tickets, tickets are sold at a discounted price.

[0079] The process of providing this service will be further explained based on the time chart in Figure 12. However, Figure 12 represents the above process in chronological order. In Figure 12, the service server 240A, service terminal 240B, terminal device 230, and disability service support server 210 of the service provision system 40 are arranged in order from left to right. Dashed lines are drawn from each of these in the figure, and time progresses from top to bottom in the figure, with processing blocks in the device or server corresponding to each dashed line.

[0080] Figure 12 shows an example of the process when a user of terminal device 230 wants to receive services at service terminal 240B and also wants to receive a disability discount. The service provision will be explained using ticket sales as an example. The consistency information generated based on the disability certificate information from terminal device 230 is stored in the disability service support server 210.

[0081] The user enters their account information on the terminal device 230 and logs into the application (S1201). In this state, when the terminal device 230 receives an instruction from the service provision system 240 to retrieve information from the user via the instruction receiving unit 570 (S1202), the terminal device 230 reads the QR code (1203a) containing the service identification information of the service terminal 240B via the lens 514a and obtains information that identifies the service transaction related to the service provision by the service provision system 240, i.e., service identification information (S1203). As a result, the terminal device 230 transmits the service identification information along with information that identifies the user to the disability service support server 210.

[0082] When the terminal device 230 receives service identification information along with user identification information ("User Information" in Figure 12) from the disability service support server 210 (S1204), the disability service support server 210 sends information requesting the application to the terminal device 230 (S1205) that requests the application to transmit a prompt to the authenticated user, instructing the user to input an indication of intent to provide the authenticated user's personal information to the service provision system 240. At this time, as described above, the request information may include, and is included in this case, information suggesting that all of the user's personal information or only certain items of personal information be provided.

[0083] When the terminal device 230 obtains the request information (S1206), it prompts the user to indicate their intention to grant permission (S1207). When the user enters an indication of their intention to grant permission (Y in S1207), the terminal device 230 transmits information indicating that indication to the disability service support server 210. Note that the user's confirmation process from steps S1205 to S1207 may be omitted.

[0084] As a result, the disability service support server 210 has fully obtained the permission information to provide personal information to the service provision system 240, and links, or associates, the user's personal information with the service-specific information (S1208). Then, the disability service support server 210 transmits, or provides, the service-specific information and personal information to the service provision system 240 (S1209).

[0085] When the service provision system 240 obtains service-specific information and personal information (S1210), it searches the database based on these and performs a verification regarding the service provision to the service terminal 240B (S1211). Then, it transmits the verification result information, i.e., verification information, to the service terminal 240B (S1212).

[0086] When the service terminal 240B obtains verification information (S1213), it performs service provision according to that verification information (S1214). In this case, if the verification is complete, the user can purchase a ticket at a discounted price in the ticket sales.

[0087] Furthermore, on terminal device 230, the user can log out at an appropriate time after entering their intention to grant permission (S1207) (S1215).

[0088] As explained above, with the above configuration, in service provision, the user's personal information is provided only from the disability service support server 210 to the service server 240A of the service provision system 240. In other words, the user's personal information is not provided to the service terminal 240B. This is because the service server 240A is provided with service-specific information along with the user's personal information, and the service server 240A performs a verification process (S1211) for service provision. Therefore, for service provision at the service terminal 240B, personal information such as information from the disability certificate is provided to the service server 240A without going through the service terminal 240B, thereby enhancing security.

[0089] Furthermore, when providing users' personal information to service server 240A, only personal information items predetermined according to the service provided will be used. Therefore, the handling of users' personal information can be kept to the bare minimum, thereby enhancing security.

[0090] Furthermore, with the above configuration, when providing personal information such as information from a disability certificate for service provision, the user can conveniently receive services from the service provision system 240 simply by obtaining service-specific information through the application on the user's terminal device 230. This is done through processing by the application on the terminal device 230 and / or the disability service support server 210. Therefore, the above processing can suitably support the provision of highly convenient services.

[0091] Next, the second embodiment will be described based on Figures 13 to 15. However, the following explanation will mainly focus on the differences from the first embodiment, and the same or similar components and steps described above will be denoted by the same reference numerals used previously, with other explanations omitted as much as possible.

[0092] In the second embodiment, when purchasing multiple tickets simultaneously in the ticket sales service at the service terminal 240B, a disability discount is applied to multiple tickets. As shown in Figure 13, in this case, when selling tickets at the service terminal 240B, the terminal device 230A of the first user (corresponding to the user in the first embodiment) and the terminal device 230B of the second user, who is a different user from the first user, cooperate.

[0093] As shown in Figure 14, in order to enable cooperation between the first user's terminal device 230A and the second user's terminal device 230B, terminal devices 230A and 230B have, in addition to the functions of the terminal device 230 of the first embodiment, a terminal device connection unit 560 which is a functional unit for communicating with other terminal devices. The terminal device connection unit 560 has an information sharing unit 561 for sharing information with other terminal devices.

[0094] When the first user's terminal device 230A acquires service identification information (S1203), it can associate another user, in this case the second user, with the acquired service identification information. Here, when the first user purchases tickets on behalf of both the first user and the second user, both the first user and the second user are disabled, and they want to purchase both tickets with a disability discount applied. Therefore, based on input from the first user, the first user's terminal device 230A acquires an instruction to share service identification information via the instruction receiving unit 570, and through the cooperation of terminal devices 230A and 230B, the second user's terminal device 230B provides the service identification information and the second user's personal information to the service server 240A of the service provision system 240.

[0095] Here, the cooperation between the first user's terminal device 230A and the second user's terminal device 230B, and the provision of the second user's personal information to the service server 240A will be explained based on Figure 15. In this second embodiment, as explained based on Figure 12, when providing services on the service terminal 240B, the first user's personal information is transmitted from the disability service support server 210 to the service server 240A, but further explanation of the provision of the first user's personal information will be omitted.

[0096] As explained with reference to Figure 12, when the first user's terminal device 230A acquires service identification information (S1203), the first user inputs an information sharing instruction on terminal device 230A, and terminal device 230A acquires that instruction (S1501). This allows, for example, the first user to input the address of the second user's terminal device 230B on terminal device 230A and input a request to send a message containing service identification information to the second user's terminal device 230B. When terminal device 230A acquires this message request (S1502), it sends the message to the second user's terminal device 230B. This message transmits service identification information for service provision to the service terminal 240B. Note that the transmission of service identification information from terminal device 230A to terminal device 230B is not limited to the message communication described above.

[0097] The second user's terminal device 230B receives a message from terminal device 230A (S1504). This allows terminal device 230B to display at least a portion of the message so that at least a portion of it is notified to the second user. If the application is not logged in on the second user's terminal device 230B, the application on terminal device 230B becomes logged in when the second user enters their account information (S1505). As a result, the second user's terminal device 230B receives information that identifies the service transaction, i.e., service identification information, from the first user's terminal device 230A (S1506). In this embodiment, since the service identification information is included in the message when it is received, the acquisition of service identification information may occur before login.

[0098] The acquisition of service-specific information on the second user's terminal device 230B (S1506) is substantially equivalent to the acquisition of service-specific information on the first user's terminal device 230A (S1203 in Figure 12). As a result, as shown in Figure 15, the second user's terminal device 230B authorizes the disability service support server 210 to provide the second user's personal information to the service server 240A (S1204-S1209), and the disability service support server 210 can then transmit, or provide, the second user's personal information to the service server 240A along with the service-specific information. The subsequent processing on the service server 240A (S1210-S1212) and the processing on the service terminal 240B (S1213 and S1214) are the same as those already explained based on Figure 12. As explained above, in the service provision of the second embodiment, information identifying the service transaction, i.e., service identification information, is transmitted from the terminal device 230A on the first user's side, which is using the service transaction, to the terminal device 230B of the second user, and the terminal device 230B of the second user can acquire it. The terminal device 230B of the second user can then provide information identifying the second user and the service identification information to the management system that manages the personal information of the second user, i.e., the disability service support server 210, which is able to communicate with the service provision system 240 and manages the personal information of the second user, so that the personal information of the second user corresponding to the acquired service identification information is sent to the service server 240A of the service provision system 240. As a result, the first user can receive the service at the service terminal 240B with enhanced security and can purchase multiple tickets at a discounted price.

[0099] Next, the third embodiment will be described based on Figures 16 to 18. However, the following explanation will mainly focus on the differences from the first embodiment, and the same or similar components and steps as those already described will be denoted by the same reference numerals, with other explanations omitted as much as possible. In addition, the process described in the second embodiment can also be carried out in the third embodiment in the same way, specifically, tickets for multiple people can be purchased at once with the disability discount applied, but this explanation will be omitted.

[0100] As shown in Figure 16, in the third embodiment, the user connects to the EC site 240W, which is the service provision site of the service provision system 240, using the terminal device 230C. Meanwhile, the user can log in to the above application 210A of the disability support service related to the disability support server 210 using the terminal device 230C. Note that logging in to this application 210A may also be logging in to the website of the disability support service related to the disability support server 210.

[0101] Figure 17 shows a block diagram of the terminal device 230C. The disability service support server connection unit 510 of the terminal device 230C has a link unit 515 that enables the exchange of information with other websites or applications, in addition to the functions of the terminal device 230 of the first embodiment. In this case, the link unit 515 performs the function of linking application 210A and EC site 240W, and operates by receiving a link instruction, i.e., a cooperation instruction, from the user to another site or application via the instruction receiving unit 570. Specifically, the user logs in to application 210A by clicking the icon for linking to application 210A on EC site 240W and entering a user ID, etc., and then the link between application 210A and EC site 240W is established by clicking the cooperation permission button with EC site 240W on application 210A. Clicking the cooperation permission button is one example of inputting a link instruction, but the link instruction may be integrated with logging in to application 210A. In other words, the user may simply click an icon on the e-commerce site 240W for linking to application 210A and enter their user ID, etc., to log in to application 210A and link application 210A to e-commerce site 240W. In this case, step S1801, described below, is omitted. The link instruction button may be under the management of the disability service support server 210, or under the management of the service server 240A and / or e-commerce site 240W. In other words, the user may first access the e-commerce site 240W, obtain a link containing service-specific information, and then log in to the disability service support server 210 based on the information in the link. Alternatively, the user may first log in to the disability service support server 210, obtain a link to the e-commerce site 240W, and then access the e-commerce site 240W. In this case, personal information may be provided to the e-commerce site 240W from the disability service support server 210 at an appropriate time. The EC site 240W may be implemented as a web page on the internet, or as an application installed in a terminal device that operates in cooperation with the EC site 240 and / or the service server 240W.

[0102] As shown in Figure 18, when a user accesses the e-commerce site 240W using terminal device 230C, logs into application 210A (S1201), and enters a link instruction, the link instruction is received by terminal device 230C (S1801). This allows application 210A to receive information from e-commerce site 240W.

[0103] Then, when a user purchases a ticket with a disability discount on the e-commerce site 240W, they instruct the terminal device 230C to acquire service-specific information, and the terminal device 230C receives this instruction to acquire service-specific information (S1202). As a result, the application 210A on the terminal device 230C acquires service-specific information 1203a from the e-commerce site 240W (S1203). With this acquisition of service-specific information, as described in the first embodiment, the user's personal information can be provided to the service server 240A via the disability service support server 210. The processing from step S1203 onward has already been described with reference to Figure 12, so further explanation is omitted here.

[0104] Furthermore, when a user accesses the e-commerce site 240W using terminal device 230C and performs the above processing, they may obtain a URI (Uniform Resource Identifier) ​​corresponding to service identification information and send that URI to other users, for example, via email. This allows other users to receive the same service that the original user received through their own terminal device, thereby further improving convenience. Note that this URI is an example of link information.

[0105] The steps included in the processing of each embodiment described above can be executed in any order, as long as there is no contradiction. Also, as long as there is no contradiction, multiple steps may be executed simultaneously, or certain steps may be skipped. [Explanation of symbols]

[0106] 200 Disability Support Systems 210 Disability Service Support Server 220 public servers 230 Terminal devices 240 service provider servers 240A Service Server 240B Service Terminal 250 Networks 302 Storage device 303 Display / operation section 304 Communications Department 305 Photography Department 306 Memory Control Unit 307 External memory 510 Disability Service Support Server Connection Section 511 Personal Information Provision Department 512 Permission Information Department 513 Consistency information acquisition unit 514 Provision Permission Department 520 Public Server Connection Section 521 Authentication Request Section 522 Permission Information Acquisition Unit 530 Data Generation Unit 540 Data Storage Unit 550 Screen generation section 610 Terminal device connection section 611 Personal Information Acquisition Department 612 Consistency Information Provision Department 613 Permit information acquisition department 620 Public Server Connection Section 621 Disability Certificate Original Information Acquisition Department 630 Data Storage Unit 631 Data Update Section 640 Data Verification Unit 650 Service Provision Connection Section

Claims

1. A service support method in which a computer assists in providing services to a user, Information identifying a service transaction related to the provision of a service by a service provision system including a service terminal and a service server that instructs the service terminal to provide a service, and information identifying a first user who is the target of the provision of the service, are obtained through an application that authenticates the first user and accepts instructions from the first user. From a management system for managing personal information, extract personal information of the first user linked to the information identifying the first user, specifically items predetermined according to the information identifying the service transaction. Without transmitting the personal information of the predetermined items to the service terminal, the service server provides the service server with information that identifies the service transaction and the personal information of the predetermined items, so that the service server sends information to the service terminal prompting it to perform the provision of the service based on the information that identifies the service transaction and the personal information of the predetermined items. Equipped with, The aforementioned personal information includes information from at least one of the following: information from a physical disability certificate, information from a mental disability health and welfare certificate, and information from an intellectual disability certificate. Methods for supporting service delivery.

2. Providing the aforementioned service server is: This includes providing the service server with information identifying the service transaction and the personal information of the first user in predetermined categories, without going through the service terminal, so that the service server is instructed to add value to the provision of the service based on the information identifying the service transaction and the personal information of the first user in predetermined categories. The service provision support method according to claim 1.

3. The information identifying the service transaction and the information identifying the second user are obtained through an application that authenticates the second user and accepts instructions from the second user. The extraction described above means This includes extracting personal information of the second user from the management system, which is linked to the information identifying the second user, and which includes personal information of predetermined items according to the information identifying the service transaction. Providing the aforementioned service server is: This includes providing the service server with information identifying the service transaction and the personal information of the second user of the predetermined items without going through the service terminal. The service provision support method according to claim 1.

4. Before providing it to the aforementioned service server, The application is instructed to prompt the user to enter a declaration of intent to authorize the provision of the predetermined personal information to the service provision system. The service provision support method according to claim 1, further comprising:

5. In the provision of services by a service provision system including a service terminal or site and a service server that prompts the service terminal or site to perform the provision of services by the service terminal or site, a management system for managing users' personal information provides the service server with the user's personal information in order to enable the provision of added value to the service transaction for the service, Obtaining information identifying the user and information identifying the service transaction from the application that authenticates the user, Providing the service server with information identifying the service transaction and personal information linked to the user, which is predetermined according to the information identifying the service transaction, without transmitting it to the service terminal or site. Includes, The aforementioned personal information includes information from at least one of the following: information from a physical disability certificate, information from a mental disability health and welfare certificate, and information from an intellectual disability certificate.

6. Obtaining information that identifies the aforementioned service transaction is, Obtaining information that identifies the service transaction from an application that authenticates other users using the service transaction. The method according to claim 5, further comprising:

7. The user is prompted to enter a declaration of intent to provide the service server with personal information of predetermined items, based on the information identifying the acquired service transaction. The method according to claim 5, further comprising:

8. A program that causes a computer to perform the method described in any one of claims 1 to 7.

Images