System, information processing apparatus, method of controlling information processing apparatus, and storage medium

Abstract

To provide a server device that contributes to providing an environment in which a disabled person belonging to a group such as a company can act comfortably.SOLUTION: The server device includes control means and giving means. The control means performs control related to determination of a supporter who supports a person requiring support who is a disabled person belonging to a group and has a request item to another person. The granting means grants a predetermined privilege to the supporter who has supported the person requiring assistance. When the supporter provides support related to a matter that allows the assistance recipient to receive the preferential treatment from the organization, the giving means may give the supporter a preferential treatment equivalent to the preferential treatment given to the assistance recipient from the organization.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present invention relates to a server device, a method for controlling a server device, and a program. [Background technology]

[0002] There is technology available to match care recipients with disabilities with caregivers.

[0003] For example, Patent Document 1 describes a system for providing nursing care services that enables the wide and rapid collection of nursing care information and the appropriate and rapid connection of such information. The system for providing nursing care services in Patent Document 1 includes a server device. The server device includes a caregiver information database that stores caregiver information, a care recipient information database that stores care recipient information, and a matching unit that matches caregivers with care recipients based on the information. This system enables the caregiver and the care recipient to be connected to each other, dramatically improving convenience for both the caregiver and the care recipient. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Japanese Patent Application Laid-Open No. 2001-338067 Summary of the Invention [Problem to be solved by the invention]

[0005] People with disabilities who work in companies sometimes want to receive support from others. However, there are also people with disabilities who are unable to proactively ask other employees for support due to concerns that they should not interfere with the work of other employees.

[0006] The main object of the present invention is to provide a server device, a method for controlling a server device, and a program that contribute to providing an environment in which people with disabilities who belong to organizations such as companies can move around comfortably. [Means for solving the problem]

[0007] According to a first aspect of the present invention, a server device is provided which includes a control means for controlling the selection of a supporter who supports a disabled person who belongs to an organization and needs support and has a request for others to make, and a granting means for granting a specified benefit to the supporter who supports the person in need of support.

[0008] According to a second aspect of the present invention, there is provided a method for controlling a server device, in which the server device controls the selection of a supporter who will support a disabled person who belongs to an organization and needs assistance and has a request for others, and grants a specified benefit to the supporter who supports the person in need of assistance.

[0009] According to a third aspect of the present invention, a program is provided for causing a computer installed in a server device to execute a process of controlling the selection of a supporter who will support a disabled person who belongs to an organization and needs support and has a request for others, and a process of granting a specified benefit to the supporter who supports the person needs support. [Effects of the Invention]

[0010] According to each aspect of the present invention, a server device, a method for controlling a server device, and a program are provided that contribute to providing an environment in which persons with disabilities who belong to an organization such as a company can move around comfortably. Note that the effects of the present invention are not limited to those described above. The present invention may achieve other effects instead of or in addition to the effects described above. [Brief explanation of the drawings]

[0011] [Figure 1] FIG. 1 is a diagram for explaining an outline of an embodiment. [Figure 2]FIG. 2 is a flowchart illustrating the operation of one embodiment. [Figure 3] FIG. 3 is a diagram illustrating an example of a schematic configuration of an information processing system according to an embodiment of the present disclosure. [Figure 4] FIG. 4 is a diagram illustrating an example of a display on a terminal according to an embodiment of the present disclosure. [Figure 5] FIG. 5 is a diagram illustrating an example of a display on a terminal according to an embodiment of the present disclosure. [Figure 6] FIG. 6 is a diagram illustrating an example of a display on the authentication terminal according to an embodiment of the present disclosure. [Figure 7] FIG. 7 is a diagram for explaining the operation of the information processing system according to the embodiment of the present disclosure. [Figure 8] FIG. 8 is a diagram illustrating an example of a processing configuration of the management server according to an embodiment of the present disclosure. [Figure 9] FIG. 9 is a diagram illustrating an example of a disability information database according to an embodiment of the present disclosure. [Figure 10] FIG. 10 is a diagram illustrating an example of a processing configuration of the support server according to an embodiment of the present disclosure. [Figure 11] FIG. 11 is a diagram illustrating an example of a user information database according to an embodiment of the present disclosure. [Figure 12] FIG. 12 is a diagram illustrating an example of a request item management database according to an embodiment of the present disclosure. [Figure 13] FIG. 13 is a flowchart illustrating an example of the operation of the support control unit according to an embodiment of the present disclosure. [Figure 14] FIG. 14 is a sequence diagram illustrating an example of the operation of the information processing system according to an embodiment of the present disclosure. [Figure 15] FIG. 15 is a diagram for explaining the operation of an information processing system according to a modified example of the embodiment of the present disclosure. [Figure 16] FIG. 16 is a diagram for explaining the operation of an information processing system according to a modified example of the embodiment of the present disclosure. [Figure 17] FIG. 17 is a diagram illustrating an example of a processing configuration of the support server according to an embodiment of the present disclosure. [Figure 18] FIG. 18 is a diagram illustrating an example of a display on a terminal according to an embodiment of the present disclosure. [Figure 19] FIG. 19 is a diagram illustrating an example of a processing configuration of the support server according to an embodiment of the present disclosure. [Figure 20] FIG. 20 is a diagram illustrating an example of a display of a user terminal according to an embodiment of the present disclosure. [Figure 21] FIG. 21 is a diagram for explaining the operation of the information processing system according to the embodiment of the present disclosure. [Figure 22] FIG. 22 is a diagram for explaining the operation of the information processing system according to the embodiment of the present disclosure. [Figure 23] FIG. 23 is a diagram illustrating an example of a hardware configuration of a support server according to the present disclosure. DETAILED DESCRIPTION OF THE INVENTION

[0012] First, an overview of one embodiment will be described. Note that the reference numerals in the drawings are added to each element for convenience as an example to facilitate understanding, and the description of this overview is not intended to be limiting in any way. Furthermore, unless otherwise specified, the blocks shown in each drawing represent functional units, not hardware units. Connection lines between blocks in each drawing include both bidirectional and unidirectional lines. Unidirectional arrows are used to schematically indicate the flow of main signals (data) and do not exclude bidirectionality. Note that in this specification and drawings, elements that can be similarly described may be assigned the same reference numerals to avoid redundant explanation.

[0013] A server device 100 according to one embodiment includes a control means 101 and a granting means 102 (see FIG. 1). The control means 101 controls the determination of a supporter who will support a person in need of support who is a person with a disability and belongs to an organization and has a request to make to others (step S1 in FIG. 2). The granting means 102 grants a predetermined benefit to the supporter who has supported the person in need of support (step S2).

[0014] The server device 100 controls the determination of supporters who support persons with disabilities who require support from others (those requiring support). For example, the server device 100 realizes a support bulletin board where persons with disabilities can post requests. The server device 100 provides predetermined benefits to supporters who support persons with disabilities. For example, the server device 100 provides supporters with benefits equivalent to those provided to persons with disabilities by organizations (e.g., discounts on meals, etc.) or points that can be used at in-house stores, etc. As a result, more supporters will be willing to support persons with disabilities, and an environment will be provided for persons with disabilities who belong to organizations such as companies where they can move around comfortably.

[0015] Specific embodiments will be described in more detail below with reference to the drawings.

[0016] [First embodiment] The first embodiment will be described in more detail with reference to the drawings.

[0017] [System Configuration] As shown in FIG. 3, the information processing system according to the first embodiment includes a support server 10, a management server 20, and an authentication terminal 30.

[0018] The support server 10 is a server (first server) managed and operated by an organization such as a company, a non-profit organization, a local government, or an educational institution. The support server 10 is a server that manages and controls members of the organization. For example, the support server 10 supports persons with disabilities who belong to the organization.

[0019] The support server 10 may be installed in the building of the organization, or may be installed on a network (on the cloud).

[0020] In the first embodiment, the configuration, operation, etc. of the information processing system will be described using a company as an example of the organization.

[0021] The management server 20 is a server (second server) managed and operated by a business that provides applications for people with disabilities. The management server 20 has a function related to the digitization of disability certificates. The management server 20 manages and stores information about people with disabilities.

[0022] The management server 20 may be installed in the building of the business operator, or may be installed on a network (on the cloud).

[0023] The authentication terminal 30 is a device used when members of an organization receive a predetermined service. The authentication terminal 30 is managed and operated by the same organization as the support server 10, for example.

[0024] Users (employees; disabled and able-bodied individuals) can receive various services via the authentication terminal 30. For example, users can pay for products and services via the authentication terminal 30. For example, the authentication terminal 30 is a POS (Point of Sale) terminal or a tablet.

[0025] A user carries a terminal 40. The user operates the terminal 40 to input various information to the support server 10, the management server 20, etc., and to acquire various information from the support server 10, etc.

[0026] The devices shown in Fig. 3 are interconnected. Specifically, the support server 10, management server 20, and authentication terminal 30 are connected by wired or wireless communication means and configured to be able to communicate with each other.

[0027] 3 is an example and is not intended to limit the configuration. For example, the information processing system may include multiple support servers 10 and multiple management servers 20. Load balancing and redundancy may be achieved by multiple support servers 10, etc.

[0028] [General operation] Next, the general operation of the information processing system according to the first embodiment will be described.

[0029] <Create an account for people with disabilities> A person with a disability creates a disability account on management server 20 in order to digitize his / her disability certificate. Specifically, the person with a disability operates terminal 40 to access management server 20. For example, the person with a disability starts an application installed on terminal 40 (for example, an application related to the digitized disability certificate) and accesses management server 20.

[0030] A person with a disability inputs into the management server 20 his / her name, sex, date of birth, address, login information (ID, password), contact information (for example, telephone number, email address), etc.

[0031] The management server 20, which has acquired the name and other information of the person with a disability, determines a person with a disability ID (key information with which the management server 20 identifies an individual) for identifying the person with a disability. For example, the management server 20 uses the email address of the person with a disability as the person with a disability ID.

[0032] The management server 20 stores the ID of a person with a disability, login information, name, date of birth, etc. in association with each other. The management server 20 stores the ID of a person with a disability, login information, name, etc. in a disability information database. Details of the disability information database will be described later.

[0033] <Disability Registration> Once the disabled person's account is created, the disabled person registers as a disabled person. The disabled person performs a predetermined action (for example, pressing the disabled person registration button) on their account.

[0034] In response to pressing the disability registration button, the management server 20 acquires information related to the user's disability (hereinafter referred to as disability-related information).

[0035] Here, the local government that issues disability certificates registers information about the disability certificates issued to each person with a disability so that the person with a disability can view it on a portal site (so-called My Number Portal) that serves as an online window for administrative services. In other words, a person with a disability can view information about their disability certificate by logging in to My Number Portal.

[0036] When the disability registration button is pressed, the management server 20 acquires information about the disability certificate issued to the user via Mynaportal. Specifically, the management server 20 acquires information about the disability certificate, such as the issuer of the disability certificate, the disability certificate number, the disability type, the disability level, and a facial image.

[0037] When the management server 20 acquires information related to the disability certificate, the management server 20 treats the acquired information as "disability-related information."

[0038] Management server 20 registers disability-related information in a disability information database. In this way, management server 20 obtains information related to the disability certificate (disability-related information) via Mynaportal, thereby guaranteeing the legitimacy, authenticity, etc. of the obtained information. In other words, by obtaining information related to the disability certificate via Mynaportal, management server 20 guarantees that a user who is registered as a disabled person is actually a disabled person.

[0039] <Create an internal account> A user (employee; disabled or able-bodied person) creates an in-house account at the company he or she belongs to. Specifically, the user operates the terminal 40 to access the support server 10.

[0040] The support server 10 acquires the name, gender, date of birth, address, login information (ID, password), contact information (e.g., telephone number, email address), biometric information, employee number, job title, department, etc. from a user registration site, etc.

[0041] Examples of biometric information include data (features) calculated from physical characteristics unique to an individual, such as a face, fingerprint, voiceprint, veins, retina, and iris pattern. Alternatively, the biometric information may be image data such as a face image or fingerprint image. The biometric information may be any information that includes the user's physical characteristics. In the embodiment disclosed herein, a case where biometric information related to a person's "face" (a face image or features generated from a face image) is used will be described.

[0042] When the user's name and other information are acquired, the support server 10 determines a user ID (key information by which the support server 10 identifies an individual) for identifying the user (employee). For example, the support server 10 uses an employee number as the user ID.

[0043] Furthermore, if the user is a person with a disability, the person with a disability registers a person with a disability ID (an email address registered in a person with a disability account) in the support server 10.

[0044] The support server 10 stores the user ID, login information, name, date of birth, biometric information, etc. in association with each other. The support server 10 stores the user ID, login information, name, etc. in a user information database. The user information database will be described in detail later.

[0045] <Support for people with disabilities> As described above, the support server 10 has a function to support persons with disabilities. In particular, the support server 10 supports in-house activities by persons with disabilities. Specifically, the support server 10 provides a "support bulletin board" where persons with disabilities can request support from others.

[0046] Employees who log in to their company accounts can view the support bulletin board (requests posted on the support bulletin board) on the intranet (internal portal).

[0047] A person with a disability who has a request operates the terminal 40 to log in to an account on the support server 10. When the person with a disability performs a predetermined action on the in-house portal site (for example, pressing the support request button), the support server 10 acquires the request from the person with a disability. For example, the support server 10 acquires the desired date and time of support, the support location, the request content (message), etc. from the person with a disability.

[0048] When the request items are acquired, the support server 10 publishes the information of the person with a disability, the acquired request items, etc. on a support bulletin board. For example, the support server 10 makes a support bulletin board such as that shown in Fig. 4 accessible from an in-house intranet or the like.

[0049] A user who has viewed the support bulletin board and is able to support a person with a disability presses the "Support" button displayed on the support bulletin board. When the support button is pressed, the support server 10 acquires a message from the user who is able to provide support to the person with a disability. For example, the support server 10 acquires the message using a GUI such as that shown in FIG. 5.

[0050] In the following explanation, users who support people with disabilities will be referred to as "supporters." Also, people with disabilities who post requests on the support bulletin board will be referred to as "people requiring support."

[0051] When a supporter for a request item posted on the support bulletin board is decided (when the "Send" button in FIG. 5 is pressed), the support server 10 stores the request item, etc. in a request item management database. Specifically, the support server 10 stores information about the request item (e.g., a request ID that identifies the request item, request content), information about the person requiring support (e.g., a user ID), and information about the supporter (e.g., a user ID) in the request item management database. Details of the request item management database will be described later.

[0052] Here, organizations such as companies may give certain preferential treatment to individuals with disabilities for certain actions. For example, if an individual with a disability eats in a cafeteria, they may receive a discount on their meal. In addition, the same preferential treatment may be given as a "benefit" to a supporter who supports the individual with a disability. Here, as shown in Figures 4 and 5, we consider a case where an individual with a disability requests meal support (for example, assistance with serving food) and one employee supports the individual with a disability.

[0053] The supporter provides support such as serving food in the cafeteria. When the meal is finished (or before the meal), the person requiring support (person with a disability) and the supporter pay for the meal at the authentication terminal 30. When the authentication terminal 30 detects a person in front of it, it displays a GUI such as that shown in FIG. 6. When the user presses the "Discount for Persons with Disabilities and Supporters" button, the authentication terminal 30 acquires the biometric information of the person requiring support and the supporter.

[0054] For example, the authentication terminal 30 acquires image data showing two faces (two persons to be authenticated). Upon acquiring the image data, the authentication terminal 30 requests the support server 10 to determine whether or not a discount is available for the meal costs of the two persons to be authenticated. Specifically, the authentication terminal 30 transmits an authentication request including the acquired image data to the support server 10 (see FIG. 7).

[0055] The support server 10 extracts two facial images from the acquired image data and performs a matching process using the two extracted facial images and the biometric information stored in the user management database. The support server 10 performs a matching process using the biometric information to determine the attribute (disabled person, able-bodied person) of the person to be authenticated.

[0056] If the person to be authenticated is a person requiring support (person with a disability) and a supporter, the support server 10 requests the management server 20 to provide disability-related information of the person requiring support. Specifically, the support server 10 transmits an "information provision request" including the disability ID of the identified person requiring support to the management server 20.

[0057] The management server 20 searches the disability information database using the disability ID included in the information request as a key to identify the corresponding entry. The management server 20 transmits the disability-related information stored in the identified entry to the support server 10. More specifically, the management server 20 transmits an affirmative response including the disability-related information to the support server 10.

[0058] The support server 10 determines whether or not a person requiring support (person with a disability) is qualified to receive predetermined preferential treatment, based on the disability-related information acquired from the management server 20. For example, the support server 10 determines whether or not the disability level of the person requiring support meets the company's regulations.

[0059] If the image data received from the authentication terminal 30 shows both the person requiring support and the person providing support, and the person requiring support (person with a disability) shown in the image data is eligible for preferential treatment within the company, the support server 10 determines that the authentication is successful.

[0060] If the image data received from the authentication terminal 30 does not include the person requiring support, or if a person other than the person with a disability is not the supporter, the support server 10 determines that the authentication has failed.

[0061] The support server 10 notifies the authentication terminal 30 of the authentication result (authentication success, authentication failure). Specifically, if the authentication is successful, the support server 10 transmits a positive response indicating that to the authentication terminal 30. If the authentication is unsuccessful, the support server 10 transmits a negative response indicating that to the authentication terminal 30.

[0062] If the authentication terminal 30 receives a successful authentication, it will provide a discount on the fee for both the person requiring support and the person providing support. If the authentication terminal 30 receives a failed authentication, it will not provide a discount on the fee. The authentication terminal 30 will settle the fee for the meal using means such as cash, electronic money, a transportation IC (Integrated Circuit) card, a credit card, or biometric authentication settlement.

[0063] Next, details of each device included in the information processing system according to the first embodiment will be described.

[0064] [Administration Server] 8 is a diagram illustrating an example of a processing configuration (processing module) of management server 20 according to an embodiment of the present disclosure. Referring to FIG. 8, management server 20 includes a communication control unit 201, an account control unit 202, a disability registration control unit 203, an information provision control unit 204, and a storage unit 205.

[0065] The communication control unit 201 is a means for controlling communication with other devices. For example, the communication control unit 201 receives data (packets) from the support server 10. The communication control unit 201 also transmits data to the support server 10. The communication control unit 201 passes data received from other devices to other processing modules. The communication control unit 201 transmits data acquired from other processing modules to other devices. In this way, other processing modules transmit and receive data to and from other devices via the communication control unit 201. The communication control unit 201 has a function as a receiving unit that receives data from other devices and a function as a transmitting unit that transmits data to other devices.

[0066] The account control unit 202 is a means for controlling the disabled person's account. The account control unit 202 acquires the name, gender, date of birth, address, login information (ID, password), contact information (e.g., telephone number, email address), etc. from the terminal 40 possessed by the user.

[0067] After acquiring the name, etc., the account control unit 202 determines a disability ID for identifying the person with a disability. Alternatively, the account control unit 202 generates a disability ID. The disability ID may be any information that can uniquely identify a person with a disability.

[0068] For example, the account control unit 202 treats the email address of the disabled person as the disabled person ID. In this case, the account control unit 202 notifies the disabled person that the email address registered by the disabled person in the management server 20 corresponds to the disabled person ID.

[0069] The account control unit 202 stores the ID, name, gender, etc. of the person with a disability in a disability information database (see FIG. 9). Note that the disability information database shown in FIG. 9 is an example and is not intended to limit the items to be stored.

[0070] The account control unit 202 authenticates a user who logs in to a disabled person account using the login information.

[0071] The disability registration control unit 203 is a means for controlling disability registration.

[0072] When a person with a disability performs a specified action (for example, pressing the disability registration button) in a disability account, the disability registration control unit 203 obtains the user's disability-related information (for example, disability type, disability level, facial image, etc.).

[0073] Specifically, the disability registration control unit 203 redirects the connection destination of the user's terminal 40 to Mynaportal (a portal site for the My Number system). The user follows instructions from Mynaportal to verify their identity using their My Number card and to give their consent to the provision of information related to their disability certificate.

[0074] After the user's identity is confirmed and the user's consent is obtained, the disability registration control unit 203 requests the local government (issuer of the disability certificate) to provide information about the user's disability certificate via Mynaportal. The disability registration control unit 203 acquires information about the disability certificate using a self-information acquisition API (Application Programming Interface) or the like.

[0075] When acquiring information related to the disability certificate, the disability registration control unit 203 treats all or part of the acquired information related to the disability certificate as "disability-related information."

[0076] The disability registration control unit 203 registers the disability-related information in the disability information database. Note that in Fig. 9, the disability-related information is written as "INFO_01", but in reality, information such as "Visual impairment: Grade 1" and a facial image are written.

[0077] In this way, the disability registration control unit 203 acquires information about the disability certificate issued to the disabled person. More specifically, the disability registration control unit 203 acquires information about the disability certificate from the local government that issued the disability certificate via the portal site of the My Number system. The disability registration control unit 203 registers the acquired information about the disability certificate in the disability information database as disability-related information.

[0078] The information provision control unit 204 is a means for controlling the provision of information to the support server 10. Specifically, the information provision control unit 204 processes an "information provision request" received from the support server 10.

[0079] The information provision control unit 204 searches the disability information database using the disability ID included in the information provision request as a key, and identifies a corresponding entry. The information provision control unit 204 transmits the disability-related information stored in the identified entry to the support server 10. More specifically, the information provision control unit 204 transmits an affirmative response (a response indicating that the disability-related information can be provided) including the disability-related information to the support server 10.

[0080] If an entry corresponding to the acquired disabled person ID does not exist in the disabled person information database, the information provision control unit 204 transmits a negative response to the support server 10 indicating that the disability-related information cannot be provided.

[0081] The storage unit 205 is a means for storing information necessary for the operation of the management server 20. For example, the storage unit 205 stores contact information for each of a plurality of disabled persons in association with the disabled person ID. Furthermore, the storage unit 205 stores disability-related information obtained from the disability certificate issued to each disabled person in association with the disabled person ID.

[0082] [Support Server] 10 is a diagram illustrating an example of a processing configuration (processing module) of the support server 10 according to an embodiment of the present disclosure. Referring to FIG. 10, the support server 10 includes a communication control unit 301, an account control unit 302, a support control unit 303, and a storage unit 304.

[0083] The communication control unit 301 is a means for controlling communication with other devices. For example, the communication control unit 301 receives data (packets) from the management server 20. The communication control unit 301 also transmits data to the management server 20. The communication control unit 301 passes data received from other devices to other processing modules. The communication control unit 301 transmits data acquired from other processing modules to other devices. In this way, other processing modules transmit and receive data to and from other devices via the communication control unit 301. The communication control unit 301 has a function as a receiving unit that receives data from other devices and a function as a transmitting unit that transmits data to other devices.

[0084] The account control unit 302 is a means for controlling employee internal company accounts. The account control unit 302 acquires information such as name, gender, date of birth, address, login information (ID, password), contact information (e.g., telephone number, email address), biometric information, employee number, job title, and department from a user registration site.

[0085] Alternatively, each employee's schedule may be managed in an employee account. For example, paid vacations and scheduled meetings may be registered in an internal company account.

[0086] Furthermore, when a face image is acquired as biometric information, the account control unit 302 generates a feature amount from the acquired face image.

[0087] Since existing technology can be used for the process of generating feature amounts, detailed description thereof will be omitted. For example, the account control unit 302 extracts the eyes, nose, mouth, etc. from the face image as feature points. After that, the account control unit 302 calculates the positions of each feature point and the distances between each feature point as feature amounts (generating a feature vector consisting of multiple feature amounts).

[0088] When a person with a disability wishes to register a person with a disability ID, the account control unit 302 acquires the person with a disability ID (the email address registered in the management server 20) from the user.

[0089] After acquiring the name, etc., the account control unit 302 determines a user ID for identifying the user (employee). Alternatively, the account control unit 302 generates a user ID. The user ID may be any information that can uniquely identify the user. For example, the account control unit 302 treats the user's employee number as the user ID.

[0090] The account control unit 302 stores the user ID, name, sex, biometric information (feature amount), etc. in a user information database (see FIG. 11). Note that the user information database shown in FIG. 11 is an example and is not intended to limit the items to be stored.

[0091] The account control unit 302 authenticates a user who logs in to an account using login information.

[0092] The support control unit 303 is a means for controlling support for people with disabilities.

[0093] The support control unit 303 has a function as a control unit and a function as an awarding unit. The control unit controls the determination of a supporter who will support a person with a disability who belongs to an organization and needs support and has a request to make to others. The awarding unit awards a predetermined benefit to the supporter who supports the person in need of support.

[0094] The support control unit 303 realizes a support bulletin board as a means for supporting people requiring assistance. More specifically, the support control unit 303 realizes a support bulletin board where people with disabilities can post requests and where multiple members of an organization (company) can view the requests.

[0095] When a person with a disability who has logged in to an internal company account performs a predetermined action on the internal company portal site (for example, pressing a support request button), the support control unit 303 acquires the request from the person with a disability. Upon acquiring the request from the person with a disability, the support control unit 303 assigns a request ID that identifies the request.

[0096] For example, the support control unit 303 acquires the desired support date and time, the support location, the request content (message), and the like from the terminal 40 of the person with a disability.

[0097] When the request items are acquired, the support control unit 303 publishes the acquired request items on a support bulletin board. For example, the support control unit 303 makes a support bulletin board such as that shown in Fig. 4 viewable from an in-house intranet or the like.

[0098] When a user (employee) who has logged in to an internal company account presses the "Support" button on the support bulletin board, the support control unit 303 acquires messages from supporters who can support persons with disabilities. For example, the support control unit 303 acquires messages using a GUI such as that shown in FIG.

[0099] When the message is received (when the "Send" button shown in FIG. 5 is pressed), the support control unit 303 determines that a supporter who will support the person with a disability requesting support has been decided. The support control unit 303 deletes the request item decided by the supporter from the support bulletin board.

[0100] Furthermore, the support control unit 303 stores the user ID of the person requiring support, the user ID of the supporter, information related to the requested item (for example, a request ID that identifies the requested item, the request content), etc. in a requested item management database (see FIG. 12). Note that the requested item management database shown in FIG. 12 is an example and is not intended to limit the items to be stored, etc.

[0101] The support control unit 303 processes an authentication request received from the authentication terminal 30 .

[0102] 13 is a flowchart showing an example of the operation of the support control unit 303 according to an embodiment of the present disclosure. The operation of the support control unit 303 when processing an authentication request will be described with reference to FIG.

[0103] When receiving an authentication request, the support control unit 303 attempts to extract two face images from the image data included in the authentication request (extracting two face images; step S101).

[0104] Note that the facial image extraction process by the support control unit 303 can use existing technology, and therefore detailed description thereof will be omitted. For example, the support control unit 303 may extract a facial image (face region) from image data using a learning model trained by a CNN (Convolutional Neural Network). Alternatively, the support control unit 303 may extract a facial image using a method such as template matching.

[0105] If two facial images cannot be extracted (step S102, No branch), the support control unit 303 transmits a negative response indicating authentication failure to the authentication terminal 30 (step S103).

[0106] If two facial images are extracted (step S102, Yes branch), the support control unit 303 executes a matching process using the two extracted facial images and the biometric information stored in the user management database (step S104).

[0107] The support control unit 303 executes a matching process using each face image and biometric information stored in the user management database, thereby determining the attributes (disabled person, able-bodied person) of each person to be authenticated.

[0108] Specifically, the support control unit 303 selects one of the two extracted face images as a face image to be determined.

[0109] The support control unit 303 generates features from the selected face image. The support control unit 303 sets the generated features as a matching target and performs matching processing (1:N matching; N is a positive integer, the same applies below) with features registered in the user information database.

[0110] The support control unit 303 calculates the similarity between the feature to be matched and each of the multiple feature values ​​on the registration side. The similarity can be calculated using chi-square distance, Euclidean distance, or the like. Note that the greater the distance, the lower the similarity, and the closer the distance, the higher the similarity.

[0111] The support control unit 303 determines that the matching process has failed if there is no feature among the multiple feature amounts registered in the user information database that has a similarity with the feature amount to be matched that is equal to or greater than a predetermined value.

[0112] The support control unit 303 determines that the matching process is successful if, among the multiple feature amounts registered in the user information database, there is a feature amount whose similarity with the feature amount to be matched is equal to or greater than a predetermined value. If the matching process is successful, the user of the entry with the highest similarity is identified as the person to be authenticated (the person to be authenticated who appears in the image data).

[0113] If the matching process fails, the support control unit 303 sets the attribute of the person to be judged to "unknown."

[0114] If the matching process is successful and a disabled person ID is set in the entry for the identified person to be authenticated, the support control unit 303 sets the attribute of the person to be judged to "disabled person."

[0115] If the matching process is successful and a disabled person ID is not set in the entry for the identified person to be authenticated, the support control unit 303 sets the attribute of the person to be judged to "able-bodied person."

[0116] When the determination of the attribute (disabled person, able-bodied person) for one face image is completed, the support control unit 303 determines the attribute (unknown, disabled person, able-bodied person) of the person to be authenticated for the other face images.

[0117] If there is no person with a disability among the two persons to be authenticated (step S105, No branch), the support control unit 303 transmits a negative response indicating authentication failure to the authentication terminal 30 (step S103).

[0118] If a person with a disability is included among the two persons to be authenticated (step S105, Yes branch), the support control unit 303 determines whether or not the person with a disability is a person requiring support.

[0119] If the user ID of the disabled person identified by the matching process is stored in the request management database, the support control unit 303 determines that the disabled person (the disabled person appearing in the image data) is a person requiring assistance (a disabled person who has requested support).

[0120] If the user ID of the person with a disability identified by the collation process is not stored in the request item management database, the support control unit 303 determines that the person with a disability is not a person requiring support.

[0121] If the person with a disability is not a person requiring support (step S106, No branch), the support control unit 303 transmits a negative response indicating authentication failure to the authentication terminal 30 (step S103).

[0122] If the person with a disability is a person requiring support (step S106, Yes branch), the support control unit 303 determines whether or not a person other than the person requiring support is a supporter.

[0123] The support control unit 303 determines that the person other than the person requiring support identified by the matching process is a supporter if the user ID of the person other than the person requiring support identified by the matching process is registered in the entry corresponding to the request of the person requiring support (entry in the request management database).

[0124] If the user ID of a person other than the person requiring support identified by the matching process is not registered in the entry corresponding to the request of the person requiring support, the support control unit 303 determines that the person other than the person requiring support is not a supporter.

[0125] If the supporter is not a person other than the person requiring support (step S107, No branch), the support control unit 303 transmits a negative response indicating authentication failure to the authentication terminal 30 (step S103).

[0126] If the supporter is a person other than the person requiring support (step S107, Yes branch), the support control unit 303 determines whether the person requiring support (person with a disability) is eligible to receive specified preferential treatment (determining eligibility; step S108).

[0127] Specifically, the support control unit 303 transmits to the management server 20 an "information provision request" including the disabled person ID of the person in need of support (person with a disability) identified by the matching process.

[0128] The support control unit 303 receives a response to the information provision request from the management server 20 .

[0129] When a negative response indicating that the disability-related information cannot be provided is received, the support control unit 303 determines that the person requiring support is not eligible to receive the predetermined preferential treatment.

[0130] When receiving a positive response indicating that the disability-related information can be provided, the support control unit 303 determines whether the person requiring support is a person with a disability who is eligible for predetermined preferential treatment, based on the disability-related information included in the positive response. For example, the support control unit 303 makes the above determination depending on whether the level of disability satisfies the company's regulations.

[0131] Specifically, if the disability level of a person requiring support is equal to or greater than a predetermined value, the person is determined to be eligible for the specified preferential treatment. Conversely, if the disability level of a person requiring support is less than the predetermined value, the person is determined to be ineligible for the specified preferential treatment.

[0132] If the person requiring support does not qualify for the predetermined preferential treatment (step S109, No branch), the support control unit 303 transmits a negative response indicating authentication failure to the authentication terminal 30 (step S103).

[0133] If the person requiring support is qualified to receive the predetermined preferential treatment (step S109, Yes branch), the support control unit 303 transmits an affirmative response indicating successful authentication to the authentication terminal 30 (step S110).

[0134] In this way, when a supporter provides support for an item for which the person in need of support is eligible to receive preferential treatment from an organization, the support control unit 303 determines whether the person in need of support is eligible to receive preferential treatment from the organization based on disability-related information, which is information about the disability of the person with a disability. If the person in need of support is eligible to receive preferential treatment from the organization, the support control unit 303 provides the supporter with preferential treatment equivalent to that given by the organization to the person in need of support.

[0135] At that time, the support control unit 303 transmits the disability ID of the person requiring support who is the subject of a determination as to whether or not the person is eligible for preferential treatment from the organization to an external server (management server 20) that stores the disability-related information of each of multiple disabled people in association with the disability ID. By transmitting the disability ID to the management server 20, the support control unit 303 acquires the disability-related information of the person requiring support who is the subject of a determination as to whether or not the person is eligible for preferential treatment from the organization.

[0136] The memory unit 304 is a means for storing information necessary for the operation of the support server 10. The memory unit 304 stores the disability IDs of at least one or more disabled persons belonging to the organization. Furthermore, a user information database is constructed in the memory unit 304. The user information database corresponds to a first database that stores the biometric information and user ID of each of multiple members (members of the organization). Furthermore, a request item management database is constructed in the memory unit 304. The request item management database corresponds to a second database that stores the user IDs of persons requiring support and the user IDs of supporters in association with each other.

[0137] [Authentication terminal] Detailed description of the authentication terminal 30 will be omitted. Examples of the authentication terminal 30 include a POS terminal, a tablet, etc. The authentication terminal 30 can be any equipment or device that can accept user operations and communicate with the support server 10.

[0138] [Device] Detailed description of the terminal 40 will be omitted. Examples of the terminal 40 include a smartphone, a mobile phone, a game console, a mobile terminal device such as a tablet, a computer (personal computer, laptop computer), etc. The terminal 40 can be any equipment or device that can accept user operations and communicate with the support server 10, etc.

[0139] [System Operation] Next, the operation of the information processing system according to the first embodiment will be described.

[0140] 14 is a sequence diagram showing an example of the operation of the information processing system according to the embodiment of the present disclosure. The operation of the information processing system according to the first embodiment will be described with reference to FIG.

[0141] The authentication terminal 30 transmits an authentication request including image data of a person with a disability who has requested support and a supporter who has supported the person with a disability to the support server 10 (step S01).

[0142] The support server 10 executes a matching process using the image data (biometric information) included in the authentication request and the biometric information stored in the user management database (step S02).

[0143] If the two persons to be authenticated identified by the matching process are a person requiring support and a supporter, the support server 10 transmits an information provision request including the disabled person ID of the person requiring support to the management server 20 (step S03).

[0144] The management server 20 transmits the disability-related information of the disabled person corresponding to the disabled person ID to the support server 10 (step S04).

[0145] The support server 10 determines whether or not the person in need of support is qualified to receive predetermined preferential treatment based on the acquired disability-related information (determining whether or not the person is qualified; step S05).

[0146] If the person in need of support is qualified to receive the predetermined preferential treatment, the support server 10 notifies the authentication terminal 30 of successful authentication (step S06).

[0147] When the authentication success is notified, the authentication terminal 30 gives a predetermined preferential treatment to the person requiring support and the supporter (giving preferential treatment; step S07). For example, the authentication terminal 30 gives a discount on the meal price for the two people.

[0148] In this way, when a supporter provides support for an item (e.g., a meal at a cafeteria) for which the person in need of support is eligible for preferential treatment from an organization, the support server 10 provides the supporter with preferential treatment (e.g., a discount on the meal price) equivalent to the preferential treatment provided by the organization to the person in need of support. The support server 10 also acquires biometric information of the two persons to be authenticated from the authentication terminal 30 used to provide a specified service. The support server 10 identifies the user IDs of the two persons to be authenticated by performing a matching process using the acquired two pieces of biometric information and the biometric information stored in the user information database. If the combination of the user IDs of the identified two persons to be authenticated is stored in the request item management database, the support server 10 notifies the authentication terminal 30 that the two persons to be authenticated are eligible for preferential treatment provided to the person in need of support.

[0149] Next, a modified example of the first embodiment will be described.

[0150] <Variation 1> In the above embodiment, a case has been described in which both the person with a disability (the person with a disability who requests support) and the supporter receive preferential treatment predetermined by the company, etc. However, the person with a disability can also receive the preferential treatment alone.

[0151] For example, if a person with a disability eats at a cafeteria, they can receive a discount on the meal price. In this case, the person with a disability presses the "Discount for Persons with Disabilities" button on the screen of the authentication terminal 30 shown in FIG.

[0152] When the disability discount button is pressed, the authentication terminal 30 takes a picture of the person to be authenticated and acquires image data. The authentication terminal 30 then transmits a "disability authentication request" including the acquired image data to the support server 10.

[0153] The support control unit 303 of the support server 10 identifies the person to be authenticated using image data of the person to be authenticated (biometric information of the person to be authenticated) and the biometric information stored in the user management database. If the identified person to be authenticated is not a person with a disability (if a person with a disability ID is not set in the identified entry), the support control unit 303 notifies the authentication terminal 30 of authentication failure.

[0154] If the identified person to be authenticated is a person with a disability, the support control unit 303 sends an information provision request including the person with a disability ID of the person with a disability to the management server 20. The support control unit 303 acquires disability-related information of the person with a disability from the management server 20.

[0155] The support control unit 303 determines whether or not the person with a disability (person to be authenticated) is eligible to receive preferential treatment based on the acquired disability-related information.

[0156] If the person with a disability (person to be authenticated) is not qualified to receive preferential treatment, the support control unit 303 notifies the authentication terminal 30 of authentication failure. If the person with a disability (person to be authenticated) is qualified to receive preferential treatment, the support control unit 303 notifies the authentication terminal 30 of authentication success.

[0157] The authentication terminal 30 performs processing according to the authentication result (authentication success, authentication failure). If authentication is successful, the authentication terminal 30 provides a predetermined preferential treatment (for example, a discount on the cost of a meal) to the person with a disability. If authentication is unsuccessful, the authentication terminal 30 notifies the person to be authenticated that the predetermined preferential treatment will not be provided.

[0158] <Variation 2> The support server 10 may perform control so that support for the disabled person is more reliably provided.

[0159] For example, if a supporter to support a person with a disability has not been decided by a predetermined time before the desired support date, the support control unit 303 may request support from employees within the company. For example, the support control unit 303 selects supporter candidates from among employees for a request item for which a supporter has not been decided one day before the desired support date. The support control unit 303 requests the selected supporter candidate to support the person with a disability.

[0160] For example, the support control unit 303 executes a matching process based on the request items, attribute information of the disabled person (the disabled person requesting support), attribute information of each employee, etc. By executing the matching process, the support control unit 303 selects at least one or more supporter candidates.

[0161] For example, the support control unit 303 determines matching conditions required of support candidates based on the request items and attribute information of the person with a disability (for example, gender, age, department, place of work, etc.). For example, the matching conditions may be determined such that the person is scheduled to be at work on the desired support day and that no meetings or other events are scheduled during the desired support time period.

[0162] The support control unit 303 identifies employees who satisfy the matching conditions and selects the identified employees as supporter candidates.

[0163] Alternatively, the support control unit 303 may rank supporter candidates based on attribute information of the person with a disability and attribute information of employees who meet the matching conditions. For example, the support control unit 303 uses the gender and age (date of birth) of the person with a disability and each employee to set a higher rank for employees of the same gender and age. The support control unit 303 may select employees of a predetermined rank or higher as supporter candidates.

[0164] Alternatively, the support control unit 303 may select supporter candidates using a learning model obtained by machine learning (AI (Artificial Intelligence)). For example, the support control unit 303 may select supporter candidates using a learning model that outputs attribute information required of supporter candidates when a request and attribute information of a person with a disability are input.

[0165] The learning model is obtained by machine learning using a large amount of training data in which labels (attribute information of supporter candidates) are assigned to the request items and attribute information of persons with disabilities. Any algorithm such as a support vector machine, boosting, or neural network can be used to generate the learning model. Note that known technologies can be used for the algorithms such as the support vector machine, and therefore a description thereof will be omitted.

[0166] Alternatively, the support control unit 303 may acquire attribute information required of a support candidate by inputting an appropriate prompt into a large language model (LLM). The support control unit 303 may generate the prompt using the request and attribute information of the person with a disability (the person with a disability seeking support).

[0167] The support control unit 303 selects employees who match the attribute information acquired from the learning model and large-scale language model as supporter candidates.

[0168] The support control unit 303 requests at least one selected supporter candidate to support the person with a disability. Specifically, the support control unit 303 sends a "support request" to the terminal 40 (email address stored in the user management database) owned by the support candidate (see FIG. 15). For example, the support control unit 303 sends the support request to the terminal 40, including the URL (Uniform Resource Locator) of a support bulletin board that lists the request item for which support is requested.

[0169] The terminal 40 that receives the support request accesses the support bulletin board. After checking the content posted on the support bulletin board, the employee (supporter candidate) decides whether or not to provide support. If support is possible, the supporter candidate presses the "Support" button shown in Figure 4.

[0170] If the supporter who will support the disabled person has not been decided even after the above matching is performed and support is requested from the supporter candidates, the support server 10 may instruct a predetermined person to support the disabled person. For example, the support control unit 303 may instruct a security guard or a person in charge of the human resources department to support the disabled person.

[0171] In this case, the support control unit 303 may send a "support instruction" including a URL of a support bulletin board that lists requests for support to the terminal 40 carried by the security guard or person in charge. In response to the instruction, the security guard or person in charge provides support to the person with a disability.

[0172] In this way, when a supporter for the person requiring support who posted the request item posted on the support bulletin board has not been decided before a predetermined time on the desired support date for the request item, the support server 10 executes a matching process targeting the person requiring support who posted the request item and multiple members. By executing the matching process, the support server 10 selects supporter candidates who will support the person requiring support who posted the request item, and requests support for the person requiring support who posted the request item from the selected supporter candidates. Furthermore, when the support server 10 has requested support for the person requiring support who posted the request item from the supporter candidates, but has not decided on a supporter to support the person requiring support who posted the request item, the support server 10 instructs a predetermined person to support the person requiring support who posted the request item.

[0173] <Variation 3> The support server 10 may post on the support bulletin board whether or not a support request from a person with a disability has been finally resolved. For example, when processing an authentication request received from the authentication terminal 30, the support control unit 303 may post "Resolved" on the support bulletin board for a request item for which authentication has been determined to be successful.

[0174] <Variation 4> The person with a disability who has received support may use his / her own terminal 40 to report the end of support from the supporter to the support server 10. For example, if the person in need of support receives support for a request unrelated to the authentication terminal 30, such as a request regarding the transportation of luggage, the person in need of support may operate his / her own terminal 40 to notify the support server 10 that the support from the supporter has ended.

[0175] In this case, the person requiring support takes a photo of the supporter who has provided support to the terminal 40. The terminal 40 transmits a "support end notification" including the user ID (employee number) of the person requiring support and the biometric information (e.g., a facial image) of the supporter obtained by photographing the supporter to the support server 10 (see FIG. 16).

[0176] The support control unit 303 executes a matching process using the biometric information included in the support end notice and the biometric information stored in the user management database to identify the support person. Furthermore, the support control unit 303 determines that support for the support-requiring person has ended if a combination of the user ID included in the support end notice and the user ID of the identified support person is stored in the request item management database.

[0177] In this case, the support control unit 303 may grant predetermined points as a benefit to the supporter. For example, the support control unit 303 may grant points that can be used at an in-house store or the like to the supporter as a benefit. Alternatively, the support control unit 303 may determine the number of points to be granted depending on the content (item) of the request for which support was provided.

[0178] <Variation 5> When registering as a person with a disability, a user may register information (private information) that is not recorded in the disability certificate in the management server 20. For example, a user may register information about an assistive device such as a wheelchair in the management server 20. More specifically, a user may register the type of assistive device (e.g., wheelchair), details of the assistive device (e.g., size and weight of the wheelchair), etc. in the management server 20 as additional information to the disability-related information.

[0179] In this case, when the user performs a predetermined action (for example, pressing an additional information registration button), the disability registration control unit 203 acquires the additional information using a GUI (Graphical User Interface) etc. The disability registration control unit 203 may acquire the additional information in a free-form description format, or may acquire the additional information using check boxes etc.

[0180] The disabled person registration control unit 203 stores the acquired additional information in the disabled person information database as part of the disability-related information.

[0181] <Variation 6> When a person with a disability posts a request on the support bulletin board, the support server 10 may post not only the information registered in the person's internal company account (e.g., name, department, etc.), but also information obtained from disability-related information on the support bulletin board.

[0182] For example, the support control unit 303 acquires the corresponding disability-related information by sending an information provision request including the disability ID of the logged-in user to the management server 20. The support control unit 303 may post all or part of the acquired disability-related information on a support bulletin board.

[0183] For example, the support control unit 303 may display a photograph of the face of a person with a disability, whether or not they need a wheelchair, etc., on a support bulletin board such as that shown in Fig. 4. As a result, a person with a disability does not need to input information about their disability into the support bulletin board every time they use the support bulletin board. This reduces the burden on people with disabilities who use the support bulletin board.

[0184] <Variation 7> The management server 20 may obtain information regarding the disability certificate (disability-related information) from image data depicting the disability certificate, rather than obtaining information regarding the disability certificate (disability-related information) via My Number Portal.

[0185] For example, when a user operates terminal 40 to access a predetermined website (person with a disability registration page), person with a disability registration control unit 203 acquires image data showing the person with a disability certificate held by the user using a GUI, etc. Specifically, person with a disability registration control unit 203 instructs the user to take a photo of the person with a disability certificate and acquires image data showing the person with a disability certificate.

[0186] The disability registration control unit 203 acquires disability-related information (e.g., disability type, disability level) from image data showing the disability certificate. Specifically, the disability registration control unit 203 reads out the disability type, disability level, etc. written in the disability certificate using OCR (Optical Character Recognition) technology.

[0187] Here, when acquiring information about the disability certificate from image data showing the disability certificate, the disability registration control unit 203 may use a learning model obtained by machine learning to determine the validity of the disability certificate used for disability registration. If the disability certificate is determined to be valid, the disability registration control unit 203 may perform disability registration.

[0188] As described above, the support server 10 according to the first embodiment realizes a support bulletin board on which persons with disabilities can post requests. The support server 10 provides predetermined benefits to supporters who support persons with disabilities. For example, the support server 10 may provide a discount on the cost of a meal for a supporter who provides meals to a person in need of support. Alternatively, the support server 10 may provide points that can be used at the company's convenience store to the supporter. As a result, company employees are motivated to more proactively support persons with disabilities, and an environment in which persons with disabilities who belong to an organization such as a company can move around comfortably is provided for the persons with disabilities.

[0189] [Second embodiment] Next, the second embodiment will be described in detail with reference to the drawings.

[0190] In the first embodiment, a case where a person with a disability transmits information to users via a support bulletin board is described. In the second embodiment, a case where information is transmitted to a person with a disability is described.

[0191] The configuration of the authentication system according to the second embodiment can be the same as that of the first embodiment, so a description corresponding to FIG. 3 will be omitted.

[0192] The following description will focus on the differences between the first and second embodiments.

[0193] 17 is a diagram illustrating an example of a processing configuration (processing module) of the support server 10 according to an embodiment of the present disclosure. Referring to FIG. 17, an information provision control unit 305 is added to the configuration of the support server 10 according to the first embodiment.

[0194] The information provision control unit 305 is a means for controlling the provision of information from in-house users to people with disabilities.

[0195] The information provision control unit 305 has a function as an acquisition means. The information provision control unit 305 acquires a first message from a member of the organization, addressed to at least one person with a disability who belongs to the organization. The information provision control unit 305 transmits an information distribution request including the acquired first message and the IDs of at least one person with a disability who belongs to the organization, to the management server 20 via the communication control unit 305 (transmission unit). The management server 20 corresponds to an external server that stores contact information for each of a plurality of people with a disability in association with the IDs of the person with a disability.

[0196] Users (employees) who wish to provide information to people with disabilities log in to their employee accounts. Once logged in, users can write a message on a designated website (message registration site).

[0197] For example, the information provision control unit 305 provides a message registration site as shown in Fig. 18. On the message registration site, users can post information such as information about employee benefits, congestion status of restrooms, requests for cooperation in demonstration experiments, disaster information, and the like.

[0198] When the user registers a message (when the send button is pressed), the information provision control unit 305 transmits the acquired message to persons with disabilities in the company.

[0199] Specifically, the information provision control unit 305 accesses the user management database and acquires at least one ID of a person with a disability set in each entry. The information provision control unit 305 then transmits an "information distribution request" including the acquired ID of a person with a disability and a message acquired from the user to the management server 20.

[0200] The management server 20 (information provision control unit 204) searches the disability information database using the disability ID included in the acquired information distribution request as a key, and identifies the corresponding entry (disabled person).

[0201] The management server 20 transmits the message acquired from the support server 10 to the terminal 40 held by the identified person with a disability. The management server 20 transmits the message acquired from the support server 10 to the email address registered in the account of the person with a disability. The terminal 40 displays the acquired message.

[0202] In this way, the support server 10 (first server) acquires a first message from a member of an organization addressed to at least one or more disabled persons belonging to the organization. The support server 10 transmits an information distribution request including the acquired first message and the disabled person IDs of at least one or more disabled persons belonging to the organization to the management server 20 (second server). The management server 20 transmits the first message to the contact information of the disabled person corresponding to the disabled person ID included in the received information distribution request.

[0203] Next, a modified example of the second embodiment will be described.

[0204] <Variation 1> The support server 10 may send a message including a questionnaire or the like to a person with a disability via the management server 20. In this case, the response (message) is sent to the response destination via the management server 20 and the support server 10.

[0205] For example, a user inputs a message including a questionnaire and a destination of the questionnaire (e.g., the email address of the person in charge) into the support server 10. When the terminal 40 of the person with a disability receives the message including the destination of the questionnaire, it transmits the answers entered by the person with a disability to the management server 20. The management server 20 transmits the received answers to the support server 10. The support server 10 transmits the answers to the questionnaire to the email address of the person in charge.

[0206] In this way, the management server 20 acquires the second message from the person with a disability who received the first message, addressed to the member of the organization, and transmits the acquired second message to the support server 10. The support server 10 transmits the received second message to the contact information of the member of the organization. In other words, the information provision control unit 305 has a function as a transfer means that receives, from an external server, the second message from the person with a disability who received the first message, addressed to the member of the organization, and transmits the received second message to the contact information of the member of the organization.

[0207] <Variation 2> The support server 10 may narrow down the recipients (disabled persons) of the information based on the content of the message entered by the user and the attribute information of the disabled person. For example, when information about a toilet on the third floor of a building is sent to the management server 20, the support server 10 may send to the management server 20 an information distribution request including the disabled person ID of a disabled person working on the third floor of the building and the message.

[0208] As described above, in the information processing system according to the second embodiment, messages (information) entered by other people are sent simultaneously to people who are registered as persons with disabilities. This method of sending messages does not constitute information provision limited to persons with disabilities, and therefore does not constitute sharing of a list of persons with disabilities. As a result, it becomes possible to send information to persons with disabilities from within the company (inside the organization), which leads to more active communication between persons with disabilities and other employees.

[0209] [Third embodiment] Next, the third embodiment will be described in detail with reference to the drawings.

[0210] In the first embodiment, the support server 10 supports activities of persons with disabilities within a company. In the third embodiment, the support server 10 supports a person in charge of management work related to persons with disabilities.

[0211] The configuration of the authentication system according to the third embodiment can be the same as that of the first embodiment, so a description corresponding to FIG. 3 will be omitted.

[0212] The following description will focus on the differences between the first to third embodiments.

[0213] 19 is a diagram illustrating an example of a processing configuration (processing module) of the support server 10 according to an embodiment of the present disclosure. Referring to FIG. 19, a document creation support unit 306 is added to the configuration of the support server 10 according to the first embodiment.

[0214] The document creation support unit 306 is a means for supporting the creation of documents that companies and the like submit to the government.

[0215] A user (e.g., a person in the human resources department) who prepares documents to be submitted to government agencies logs in to their company account. When the person in charge performs a predetermined operation (e.g., pressing the "Prepare government documents" button), the document preparation support unit 306 accesses the user management database and acquires at least one ID of a person with a disability set for each entry.

[0216] The document creation support unit 306 transmits an "information provision request" including the acquired disabled person ID to the management server 20. The management server 20 identifies entries corresponding to at least one disabled person ID included in the information provision request.

[0217] The management server 20 transmits all or part of the disability-related information of the identified entry (for example, the disability level and a facial photograph of the disabled person) to the support server 10.

[0218] The document creation support unit 306 creates documents (draft documents) to be submitted to the government using the acquired disability-related information. For example, the document creation support unit 306 creates documents to be submitted to the government by fitting the disability grade and facial photo obtained from the disability-related information into a predetermined template.

[0219] As described above, the support server 10 according to the third embodiment transmits an information request including the disability IDs of at least one or more disabled persons belonging to an organization to the management server 20. The management server 20 transmits disability-related information of disabled persons corresponding to the disability IDs included in the received information request to the support server 10. The support server 10 uses the received disability-related information to create prescribed documents related to at least one or more disabled persons belonging to the organization. As a result, the burden on the person in charge of administrative tasks related to disabled persons is reduced.

[0220] [Fourth embodiment] In the above embodiment, the operation, configuration, etc. of the information processing system are described assuming that information on employees (disabled and able-bodied) is stored in the support server 10. However, the information on employees may also be stored in a smartphone or the like carried by the employee.

[0221] In this case, the employee's smartphone may store at least a certificate related to receiving the service (service receiving certificate) in the digital wallet.

[0222] When an internal company account is created for a user, the smartphone (terminal 40) carried by the employee requests the support server 10 to issue a service certificate. Upon receiving the request, the support server 10 generates a service certificate that includes all or part of the information of the created account. For example, the support server 10 generates a service certificate that includes the employee's information (e.g., user ID, disability ID, name, gender, date of birth, biometric information), etc.

[0223] The support server 10 sends the generated service receipt certificate to the smartphone or the like. After sending the service receipt certificate, the support server 10 deletes the employee's biometric information and the like from the company account. The smartphone or the like stores the received service receipt certificate in its digital wallet.

[0224] When the user stands in front of the authentication terminal 30, the authentication terminal 30, which is a device used by the service provider, may request the smartphone to provide a service enjoyment certificate.

[0225] In response to the request, the smartphone transmits the service receiving certificate to the authentication terminal 30.

[0226] The authentication terminal 30 provides a service using the service receipt certificate obtained from the smartphone. Specifically, the authentication terminal 30 performs an authentication process using biometric information obtained from the service receipt certificate and biometric information (a facial image obtained by photographing) obtained from the user in front of the user. If the authentication process is successful, the authentication terminal 30 transmits the user ID and other information obtained from the service receipt certificate to the support server 10. The support server 10 may determine whether the person to be authenticated is a person with a disability (a person requiring support) based on the received user ID.

[0227] As described above, the information processing system according to the fourth embodiment may realize a self-sovereign identity system in which a user manages and controls the information necessary for receiving a service. That is, a user may receive a service from a service provider while proactively managing his or her own identity information. A user may provide a service provider with information required by the service provider in response to a request from the service provider. In this case, the certificate provided to the service provider may be a credential certificate. Furthermore, the service provider does not need to store and manage information that requires careful handling, such as the user's biometric information, when providing the service. As a result, the information management costs of the service provider are reduced.

[0228] For an explanation of digital wallets, certificate issuance, certificate usage, etc., please refer to the following.

[0229] <Digital Wallet> A digital wallet is an electronic information storage service that guarantees information security, including data integrity, reliability, and availability.

[0230] A user installs an application to realize a digital wallet on their user terminal 90. By opening a digital wallet on the user terminal 90, the user can store various digital content on the user terminal 90, such as electronic money, identification documents such as a student ID, passport or driver's license, various ticket information such as airline tickets or boarding passes, and certificates related to biometric information. Alternatively, the user may store service receipt certificates, information to be provided to others, etc. in the digital wallet.

[0231] For example, the user terminal 90 of a user stores digital content as shown in Fig. 20. The digital content stored in the user terminal 90 includes official identification documents such as passports and driver's licenses, employment certificates issued by companies and universities, graduation certificates, biometric information certificates relating to biometric information, etc.

[0232] The user terminal 90 may perform identity verification using an identification card issued by a public institution such as a government agency. For example, the user terminal 90 may perform identity verification of the user when opening a digital wallet, as necessary.

[0233] For example, the user terminal 90 performs identity verification using an identification card such as a passport that contains the biometric information of the holder.

[0234] Examples of biometric information include data (features) calculated from physical characteristics unique to an individual, such as a face, fingerprint, voiceprint, veins, retina, and iris pattern. Alternatively, biometric information may be image data such as a face image or fingerprint image. The biometric information may be any information that includes the user's physical characteristics.

[0235] The user terminal 90 acquires information about the holder (issuer) of the identification card from the user's identification card. For example, the user terminal 90 acquires information about the holder of the passport from an IC (Integrated Circuit) chip in the passport.

[0236] Specifically, the user terminal 90 acquires basic information of the passport holder (the so-called four basic pieces of information: name, sex, date of birth, and address) and biometric information (facial image) of the passport holder. The user terminal 90 may store the acquired basic information in a digital wallet and manage it so that it can be provided to others.

[0237] Furthermore, the user terminal 90 acquires biometric information of the user (the person who opened the digital wallet). For example, the user terminal 90 acquires a facial image by photographing the user.

[0238] The user terminal 90 performs a matching process (authentication process) using the biometric information acquired from the identification card and the user's biometric information. If the authentication process (one-to-one authentication) is successful, the user terminal 90 opens a digital wallet. The user terminal 90 confirms through a matching process (authentication process) using the biometric information that the person in whose name the identification card was issued and the user using the digital wallet of the user terminal 90 are the same person.

[0239] If identity verification is successful, the user terminal 90 stores the biometric information obtained from the identification card or the biometric information obtained by photographing the user. The user terminal 90 may acquire the user's biometric information when the user terminal 90 is started up or when the digital wallet is started up, and perform identity verification using the acquired biometric information and the stored biometric information.

[0240] <Certificate issuance> A user acquires digital content to be stored in a digital wallet. For example, the user operates user terminal 90 to request a certificate issuer to issue a certificate.

[0241] Specifically, the digital wallet application requests a certificate issuer to issue a certificate. The certificate issuer then issues VCs (Verifiable Credentials), whose contents can be verified online, as the certificate. The certificate issuer then issues a credential certificate.

[0242] Prior to requesting the issuance of a credential certificate, the user's user terminal 90 generates a pair of a public key and a private key. The user terminal 90 also generates a decentralized identifier (DID). The user terminal 90 registers the generated DID (user ID; holder ID) and public key in the blockchain (step S1001 in FIG. 21).

[0243] Furthermore, the user's user terminal 90 presents the user ID and requests the certificate issuer (issuer server 91 managed by the certificate issuer) to issue a credential certificate. Specifically, the user terminal 90 transmits a "certificate issuance request" including information about the certificate to be issued, information identifying the user, the user ID, etc. to the certificate issuer's issuer server 91 (step S1002).

[0244] The issuer server 91 generates and stores the issuer's DID (issuer ID), private key, and public key in advance.

[0245] Upon receiving a certificate issuance request, the certificate issuer determines whether the user requesting the issuance of a credential certificate (VC) is eligible to receive the certificate. If the user is eligible to receive a credential certificate, the issuer server 91 generates a credential certificate (VC) that includes the issuer ID and the user ID.

[0246] Specifically, the issuer server 91 generates a credential certificate (VC) that includes metadata including the type of credential certificate, the name of the issuing organization, the date and time of issue, etc., a qualification information body, and the issuer's public key information, electronic signature, etc. The qualification information body contains specific information to be certified by the issuer.

[0247] The issuer server 91 transmits the generated credential certificate to the user terminal 90 of the user (user who will become the certificate holder; person requesting issuance of the certificate) (certificate issuance; step S1003).

[0248] Furthermore, the issuer server 91 registers the issuer ID and the generated public key and the like in the block chain (step S1004).

[0249] The user terminal 90 stores the received credential certificates (VCs) in the digital wallet. For example, when the user terminal 90 requests the issuer to issue a biometric information certificate, it stores the credential certificates (VCs) that certify the validity of the biometric information in the digital wallet. Alternatively, when the user terminal 90 requests the issue of an employment certificate from the user's employer, it stores the credential certificates (VCs) related to the user's employment in the digital wallet. Alternatively, the user terminal 90 stores a service enjoyment certificate related to the service to be enjoyed in the digital wallet.

[0250] If information different from the certificate issued by another party is stored in the digital wallet, the user terminal 90 can acquire the information different from the certificate using a GUI (Graphical User Interface) and store it in the digital wallet. Also, the digital wallet may store a certificate based on a so-called public key infrastructure.

[0251] <Certificate usage> The user presents the certificate or the like required by the service provider to the service provider. The service provider provides the service to the user using a provider device 92 (see FIG. 22). The provider device 92 may be a server, a gate device, a kiosk terminal, a tablet, a signage, or the like, depending on the type of service provided by the service provider.

[0252] The provider device 92 transmits a "certificate request" to the user terminal 90 (step S1011). The certificate request includes information about at least one certificate or the like required for the service provider to provide the service.

[0253] The user terminal 90 and the provider device 92 communicate with each other using an internet line, a mobile line, etc. Alternatively, the user terminal 90 and the provider device 92 communicate with each other using a short-range wireless communication means such as Bluetooth (registered trademark) or NFC (Near Field Communication).

[0254] In response to receiving the certificate provision request, the user terminal 90 transmits the credential certificates (VCs) stored in the digital wallet to the provider device 92. Specifically, the user terminal 90 selects a specified credential certificate from among multiple credential certificates stored in the digital wallet. Then, the user terminal 90 signs the selected credential certificate using a private key corresponding to the user's DID (user ID). The user terminal 90 transmits at least one signed credential certificate to the provider device 92 (step S1012).

[0255] In addition, before sending the credential certificate to the provider device 92, the user terminal 90 may present the user with information about the certificate requested by the service provider and obtain consent (user consent) to provide the certificate to the service provider.

[0256] The provider device 92 acquires the issuer ID and the user ID from the received credential certificate. Furthermore, the provider device 92 acquires the public key corresponding to the acquired issuer ID and the public key corresponding to the acquired user ID from the blockchain (step S1013).

[0257] Thereafter, the provider device 92 verifies at least one credential certificate received from the user terminal 90. Specifically, the provider device 92 verifies the signature of the holder and the signature of the issuer attached to the credential certificate. By verifying these signatures, the provider device 92 confirms that the credential certificate obtained from the user (credential certificate holder) has not been tampered with and that it has been issued by a trustworthy issuer.

[0258] If the provider device 92 successfully verifies the acquired credential certificate, it provides the service to the user.

[0259] If the service provider requests the provision of information other than the credential certificate, the user terminal 90 may read the requested information from the digital wallet and transmit it to the provider device 92 .

[0260] Next, the hardware of each device constituting the information processing system will be described. Fig. 23 is a diagram showing an example of the hardware configuration of the support server 10.

[0261] The support server 10 can be configured by an information processing device (so-called computer), and has the configuration exemplified in Fig. 23. For example, the support server 10 includes a processor 311, a memory 312, an input / output interface 313, and a communication interface 314. The components such as the processor 311 are connected by an internal bus or the like, and are configured to be able to communicate with each other.

[0262] However, the configuration shown in Fig. 23 is not intended to limit the hardware configuration of the support server 10. The support server 10 may include hardware not shown, and may not include the input / output interface 313 as necessary. Furthermore, the number of processors 311 and the like included in the support server 10 is not intended to be limited to the example shown in Fig. 23, and for example, the support server 10 may include multiple processors 311.

[0263] The processor 311 is a programmable device such as a central processing unit (CPU), a micro processing unit (MPU), or a digital signal processor (DSP). Alternatively, the processor 311 may be a device such as a field programmable gate array (FPGA) or an application specific integrated circuit (ASIC). The processor 311 executes various programs including an operating system (OS).

[0264] The memory 312 is a random access memory (RAM), a read only memory (ROM), a hard disk drive (HDD), a solid state drive (SSD), etc. The memory 312 stores an OS program, application programs, and various data.

[0265] The input / output interface 313 is an interface for a display device and an input device (not shown). The display device is, for example, a liquid crystal display. The input device is, for example, a device that accepts user operations such as a keyboard or a mouse.

[0266] The communication interface 314 is a circuit, module, etc. that communicates with other devices. For example, the communication interface 314 includes a network interface card (NIC).

[0267] The functions of the support server 10 are realized by various processing modules. The processing modules are realized, for example, by the processor 311 executing a program stored in the memory 312. The program can be recorded on a computer-readable storage medium. The storage medium can be a non-transitory medium such as a semiconductor memory, a hard disk, a magnetic recording medium, or an optical recording medium. That is, the present invention can also be embodied as a computer program product. The program can be downloaded via a network or updated using a storage medium storing the program. The processing modules can also be realized by a semiconductor chip.

[0268] The management server 20 and the like can also be configured using an information processing device, similar to the support server 10, and the basic hardware configuration is no different from that of the support server 10, so a description thereof will be omitted.

[0269] The support server 10, which is an information processing device, is equipped with a computer, and the functions of the support server 10 can be realized by causing the computer to execute a program. The support server 10 also executes a control method for the support server 10 by the program.

[0270] [Variations] The configuration, operation, etc. of the information processing system described in the above embodiment are merely examples, and are not intended to limit the configuration, etc. of the system.

[0271] In the above embodiment, the configuration, operation, etc. of the information processing system have been described using meal support as an example of a request made by a person with a disability. However, it goes without saying that requests made by a person with a disability are not limited to meal support. For example, carrying luggage is an example of a request made by a person with a disability.

[0272] In the above embodiment, a case has been described in which one employee (supporter) supports one person with a disability (person requiring support). However, multiple employees (supporters) may support one person with a disability. In this case, each supporter may be given the same preferential treatment (benefits) as the person with a disability, or the preferential treatment given to multiple supporters may be equivalent to the preferential treatment given to one person with a disability.

[0273] In the above embodiment, the authentication terminal 30 acquires image data in which both the person requiring support and the support person are simultaneously photographed. However, the authentication terminal 30 may acquire image data for each of the person requiring support and the support person, and transmit the acquired two pieces of image data to the support server 10. The support server 10 may extract a face image from each piece of image data and execute the above-described processing.

[0274] When the support server 10 acquires a person with a disability ID from a person with a disability, the support server 10 may inquire whether the person with a disability is truly registered in the management server 20. Specifically, the support server 10 transmits the acquired person with a disability ID to the management server 20 and inquires whether a person with a disability corresponding to the transmitted person with a disability ID is registered. When the support server 10 receives a response from the management server 20 indicating that the corresponding person with a disability is registered, the support server 10 registers the person with a disability ID in an internal company account.

[0275] In the above embodiment, the case where the disability information database is configured inside the management server 20 has been described, but the database may also be configured on an external database server or the like. That is, some of the functions of the management server 20 may be implemented on another server. More specifically, the above-described "disability registration control unit (disability registration control means)" and the like may be implemented on any of the devices included in the system.

[0276] The form of data transmission and reception between each device (e.g., the support server 10, the management server 20, and the authentication terminal 30) is not particularly limited, but the data transmitted and received between these devices may be encrypted. Biometric information and the like is transmitted and received between these devices, and in order to appropriately protect this information, it is desirable to transmit and receive encrypted data.

[0277] In the flow charts (flowcharts, sequence diagrams) used in the above explanation, multiple steps (processes) are described in order, but the execution order of the steps executed in the embodiments is not limited to the order described. In the embodiments, the order of the illustrated steps can be changed to the extent that the content is not affected, such as by executing each process in parallel.

[0278] The above-described embodiments have been described in detail to facilitate understanding of the present disclosure, and it is not intended that all of the above-described configurations are required. Furthermore, when multiple embodiments are described, each embodiment may be used alone or in combination. For example, it is possible to replace part of the configuration of one embodiment with the configuration of another embodiment, or to add the configuration of another embodiment to the configuration of one embodiment. Furthermore, it is possible to add, delete, or replace part of the configuration of one embodiment with another configuration.

[0279] From the above explanation, the industrial applicability of the present invention is clear, and the present invention can be suitably applied to information processing systems that support people with disabilities.

[0280] Some or all of the above embodiments can be described as, but are not limited to, the following supplementary notes.

[0281] [Appendix 1] A control means for controlling the decision on a supporter who supports a person with a disability who belongs to an organization and needs support and has a request to another person; A granting means for granting a predetermined benefit to the supporter who has supported the person in need of support; A server device comprising:

[0282] [Appendix 2] The applying means is A server device as described in Appendix 1, which, if the supporter provides support regarding matters for which the person in need of support is eligible for preferential treatment from the organization, gives the supporter preferential treatment equivalent to the preferential treatment given by the organization to the person in need of support.

[0283] [Appendix 3] The server device described in Appendix 2, wherein the control means realizes a support bulletin board where the disabled person can post the request and where multiple members belonging to the organization can view it.

[0284] [Appendix 4] The control means If the supporter for the person requiring support who posted the request item has not been decided before a predetermined time of the desired support date for the request item posted on the support bulletin board, a matching process is performed for the person requiring support who posted the request item and the plurality of members to select a supporter candidate who will support the person requiring support who posted the request item; A server device as described in Appendix 3, which requests support from the selected support candidate for the person in need of support who posted the request.

[0285] [Appendix 5] The server device described in Appendix 4, wherein the control means instructs a predetermined person to support the person requiring support who posted the request item, if a supporter to support the person requiring support who posted the request item is not determined despite the supporter candidates being requested to support the person requiring support who posted the request item.

[0286] [Appendix 6] The applying means is When the supporter provides support regarding matters for which the person in need of support can receive preferential treatment from the organization, a determination is made as to whether the person in need of support can receive preferential treatment from the organization based on disability-related information, which is information about the disability of the person with a disability; A server device described in any one of Appendices 2 to 5, which, if the person in need of support is able to receive preferential treatment from the organization, provides the supporter with preferential treatment equivalent to that given by the organization to the person in need of support.

[0287] [Appendix 7] The server device described in Appendix 6, wherein the granting means acquires the disability-related information of the person requiring support who is being judged as to whether or not they are eligible for preferential treatment from the organization by sending the disability ID of the person requiring support who is being judged as to whether or not they are eligible for preferential treatment to an external server that stores the disability-related information of each of multiple disabled people in association with their disability ID.

[0288] [Appendix 8] a first database that stores biometric information and a user ID of each of the plurality of members; a second database that stores the user ID of the person requiring support and the user ID of the supporter in association with each other; The applying means is acquiring biometric information of two persons to be authenticated from an authentication terminal used to provide a predetermined service, and identifying user IDs of the two persons to be authenticated by performing a matching process using the acquired two pieces of biometric information and the biometric information stored in the first database; A server device as described in Appendix 7, which notifies the authentication terminal that, if the combination of user IDs of the two identified persons to be authenticated is stored in the second database, the two persons to be authenticated are eligible to receive preferential treatment given to the person in need of support.

[0289] [Appendix 9] In the server device, Supporting disabled people who belong to an organization and need assistance and have requests from others, and controlling the decision on who to provide assistance to. A control method for a server device that provides a predetermined benefit to the supporter who has supported the person in need of support.

[0290] [Appendix 10] The computer installed in the server device A process of controlling the decision of a supporter who supports a person with a disability who belongs to an organization and needs support and has a request to make to others; A process of granting a predetermined benefit to the supporter who has supported the person in need of support; A program to execute.

[0291] Furthermore, some or all of the configurations described in Supplementary Notes 2 to 8, which are dependent on Supplementary Note 1, may also be dependent on Supplementary Notes 9 and 10 in the same dependent relationship as Supplementary Notes 2 to 8. Furthermore, not limited to Supplementary Notes 1, 9, and 10, but within the scope of each of the above-mentioned embodiments, some or all of the configurations described as Supplements may also be dependent on various hardware, software, various recording means for recording software, or systems.

[0292] The disclosures of the above-cited prior art documents are incorporated herein by reference. Although the embodiments of the present invention have been described above, the present invention is not limited to these embodiments. Those skilled in the art will understand that these embodiments are merely illustrative and that various modifications are possible without departing from the scope and spirit of the present invention. In other words, the present invention naturally includes various modifications and alterations that may be made by those skilled in the art in accordance with the entire disclosure, including the claims, and the technical concepts thereof. [Explanation of symbols]

[0293] 10 Support Server 20 Management Server 30 Authentication Terminal 40 terminals 90 User terminal 91 Issuer Server 92 Provider device 100 Server device 101 Control means 102 Means of Granting 201 Communication control unit 202 Account Control Unit 203 User Registration Control Unit 204 Information provision control section 205 Storage section 301 Communication Control Unit 302 Account Control Unit 303 Support Control Unit 304 Storage section 305 Information provision control section 306 Document Preparation Support Department 311 processor 312 memory 313 Input / Output Interface 314 Communication Interface

Claims

1. a first acquisition means for acquiring employee information including an employee ID of a user; a second acquisition means for acquiring, when the user is a person with a disability, disability-related information including a disability ID of the user; a registration means for registering the acquired employee information and disability-related information in a database in association with each other; a third acquisition means for acquiring an employee ID of a user who uses the service from a terminal used to provide the service; a fourth acquisition means for acquiring the disability-related information of the user who uses the service and corresponds to the disability ID registered in the database in association with the acquired employee ID; an output means for outputting the acquired disability-related information; A system comprising:

2. a first acquisition means for acquiring first biometric information of a user and employee information; a second acquisition means for acquiring disability-related information of the user when the user is a person with a disability; a registration means for registering the acquired first biometric information, employee information, and disability-related information in a database in association with each other; a third acquisition means for acquiring second biometric information of a user who uses the service from a terminal used to provide the service; a fourth acquisition means for acquiring disability-related information of a user who uses the service and is identified by biometric authentication using the acquired second biometric information and the first biometric information registered in the database; and an output means for outputting the acquired disability-related information; A system comprising:

3. The system described in claim 1 or 2, further comprising a control means for realizing a bulletin board on which a person with a disability can post requests and which can be viewed by multiple members of the same organization as the person with a disability.

4. The control means The system described in claim 3, wherein a supporter is selected from among the plurality of members to support the disabled person who posted a request on the bulletin board, and when the selected supporter supports the disabled person, a specified benefit is granted to the supporter who supported the disabled person.

5. a first acquisition means for acquiring employee information including an employee ID of a user; a second acquisition means for acquiring, when the user is a person with a disability, disability-related information including a disability ID of the user; a registration means for registering the acquired employee information and disability-related information in a database in association with each other; a third acquisition means for acquiring an employee ID of a user who uses the service from a terminal used to provide the service; a fourth acquisition means for acquiring the disability-related information of the user who uses the service and corresponds to the disability ID registered in the database in association with the acquired employee ID; an output means for outputting the acquired disability-related information; An information processing device comprising:

6. a first acquisition means for acquiring first biometric information of a user and employee information; a second acquisition means for acquiring disability-related information of the user when the user is a person with a disability; a registration means for registering the acquired first biometric information, employee information, and disability-related information in a database in association with each other; a third acquisition means for acquiring second biometric information of a user who uses the service from a terminal used to provide the service; a fourth acquisition means for acquiring disability-related information of a user who uses the service and is identified by biometric authentication using the acquired second biometric information and the first biometric information registered in the database; and an output means for outputting the acquired disability-related information; An information processing device comprising:

7. Acquire employee information including the user's employee ID, If the user is a person with a disability, obtain disability-related information including the user's disability ID; The acquired employee information and disability-related information are associated and registered in a database; Acquire the employee ID of the user who uses the service from the terminal used to provide the service; Acquire the disability-related information of the user who uses the service, which corresponds to the disability ID registered in the database in association with the acquired employee ID; A control method for an information processing device that outputs the acquired disability-related information.

8. Acquire the user's first biometric information and employee information, If the user is a person with a disability, obtain disability-related information of the user; The acquired first biometric information, employee information, and disability-related information are associated with each other and registered in a database; acquiring second biometric information of a user who uses the service from a terminal used to provide the service; acquiring disability-related information of a user who uses the service and is identified by biometric authentication using the acquired second biometric information and the first biometric information registered in the database; A control method for an information processing device that outputs the acquired disability-related information.

9. On the computer, A process of acquiring employee information including the user's employee ID; If the user is a person with a disability, a process of acquiring disability-related information including a disability ID of the user; a process of registering the acquired employee information and disability-related information in a database in association with each other; A process of acquiring an employee ID of a user who uses the service from a terminal used to provide the service; A process of acquiring the disability-related information of the user who uses the service corresponding to the disability ID registered in the database in association with the acquired employee ID; A process of outputting the acquired disability-related information; A program to execute.

10. On the computer, A process of acquiring first biometric information and employee information of a user; If the user is a person with a disability, acquiring disability-related information of the user; a process of registering the acquired first biometric information, employee information, and disability-related information in a database in association with each other; A process of acquiring second biometric information of a user who uses a service from a terminal used to provide the service; a process of acquiring disability-related information of a user who uses the service and is identified by biometric authentication using the acquired second biometric information and the first biometric information registered in the database; A process of outputting the acquired disability-related information; A program to execute.

Images