Information system, management center device, and user authentication method

Abstract

A routing device (7) comprises a storage unit (71), and a routing control unit (74). The storage unit (71) stores first associating information associating a first attribute and a first user, and second associating information associating a second attribute and a second user. The routing control unit (7) acquires the second attribute corresponding to the second user from a first center device (3) corresponding to the first attribute, upon receipt of authentication information for the second user, and requests a second center device (4) corresponding to the second attribute to perform authentication processing for the second user.

Description

CROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This international application claims priority based on Japanese Patent Application No. 2021-110908 filed with the Japan Patent Office on July 2, 2021, and the entire contents of Japanese Patent Application No. 2021-110908 are incorporated by reference into this international application. [Technical field]

[0002] The present disclosure relates to user authentication techniques. [Background technology]

[0003] The authentication system described in the following Cited Document 1 includes a user terminal, an authentication server connected to the user terminal, and a plurality of service provider systems connected to the authentication server. The authentication server centrally manages personal information of users, and centrally authenticates users when they log in to online services of each service provider system. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] JP 2018-74388 A Summary of the Invention

[0005] As a result of detailed investigation by the inventors, it was found that, due to the characteristics of personal information, it may not be possible to centrally manage personal information used for multiple services on a single server device. One aspect of the present disclosure is that it is desirable to be able to realize authentication of a user when the user uses data of a center device that does not manage personal information of the user.

[0006] A routing device according to one aspect of the present disclosure is capable of communicating with a first center device and a second center device related to providing a service to a first vehicle associated with a first user and a second vehicle associated with a second user, and includes a storage unit and a routing control unit. The storage unit is configured to store first linking information linking a first attribute with a first user belonging to the first attribute, and second linking information linking a second attribute with a second user belonging to the second attribute. The routing control unit is configured to acquire a second attribute corresponding to the second user from the storage unit in response to receiving authentication information of the second user from the first center device corresponding to the first attribute, and to request authentication processing of the second user from the second center device corresponding to the second attribute.

[0007] In response to receiving the authentication information of the second user from the first center device, the routing device acquires the second attribute corresponding to the second user from the storage unit and requests the second center device corresponding to the second attribute to perform authentication processing of the second user. Therefore, when the second user uses a service based on data of the first center device that does not correspond to the second attribute, the second user can use the service by receiving user authentication by the second center device corresponding to the second attribute.

[0008] A user authentication method according to another aspect of the present disclosure includes, in response to receiving authentication information of a second user from a first center device corresponding to a first attribute, acquiring a second attribute corresponding to the second user from a table in which first linking information linking the first attribute with a first user belonging to the first attribute and second linking information linking the second attribute with a second user belonging to the second attribute are defined. Furthermore, the authentication method requests an authentication process for the second user from a second center device corresponding to the acquired second attribute.

[0009] The above user authentication method provides the same effects as the above routing device.

[0010] A user authentication program according to yet another aspect of the present disclosure causes a routing device capable of communicating with a first center device and a second center device to, in response to receiving authentication information of a second user from a first center device corresponding to a first attribute, acquire a second attribute corresponding to the second user from a table that specifies first linking information linking a first attribute with a first user belonging to the first attribute and second linking information linking a second attribute with a second user belonging to the second attribute, and to request authentication processing of the second user from a second center device corresponding to the acquired second attribute.

[0011] By executing the user authentication program, the same effects as those of the routing device are achieved.

[0012] A management center device according to yet another aspect of the present disclosure is used in a system including a first center device, a second center device, and a routing device. The management center device includes a first center device. The first center device is configured to manage authentication information of a first user belonging to a first attribute. The second center device is configured to manage authentication information of a second user belonging to a second attribute. The routing device includes a storage unit that stores first linking information linking the first attribute with the first user and second linking information linking the second attribute with the second user, and is configured to acquire a second attribute corresponding to the second user from the second linking information in response to receiving the authentication information of the second user from the first center device and transmit information related to the acquired second attribute to the first center device. The first center device is configured to request authentication processing of the second user to the second center device in response to receiving information related to the second attribute from the routing device.

[0013] When the management center device receives the authentication information of the second user, it transmits the authentication information of the second user to the routing device and receives information on the second attribute corresponding to the second user from the routing device. Then, the management center device requests authentication processing of the second user from a second center device corresponding to the second attribute. In other words, when the management center device receives authentication information of a user other than the managed user, it requests authentication processing from another center device that manages the authentication information of that user. Therefore, when the second user uses a service based on data of the first center device that does not correspond to the second attribute, the second user can use the service by receiving user authentication by the second center device corresponding to the second attribute. [Brief description of the drawings]

[0014] [Figure 1] FIG. 1 is a block diagram showing a configuration of a mobility IoT system according to a first embodiment. [Diagram 2] FIG. 2 is a diagram showing a configuration of standardized vehicle data according to the first embodiment. [Diagram 3] FIG. 2 is a block diagram showing a configuration of a management center according to the first embodiment. [Figure 4] 1 is a block diagram showing a configuration of a routing device according to a first embodiment. [Diagram 5] 2 is a block diagram showing a functional configuration of a management center according to the first embodiment. FIG. [Figure 6] FIG. 4 is a sequence diagram showing a processing procedure of user authentication according to the first embodiment. [Figure 7] FIG. 4 is a diagram showing data stored in a region discrimination DB according to the first embodiment. [Figure 8] FIG. 2 is a diagram showing data stored in a URL DB according to the first embodiment. [Figure 9] 13 is a block diagram showing another example of the configuration of the management center according to the first embodiment. FIG. [Figure 10] FIG. 11 is a sequence diagram showing a procedure of user authentication according to the second embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0015] Hereinafter, exemplary embodiments for carrying out the present disclosure will be described with reference to the drawings.

[0016] 1. First embodiment <1-1. Configuration> The configuration of a mobility Internet of Things 1 (hereinafter, IoT) according to this embodiment will be described with reference to Fig. 1. The mobility IoT 1 includes a plurality of edge devices 2, a first management center 3, a second management center 4, a third management center 5, a service providing server 6, and a routing device 7. In this embodiment, the mobility IoT 1 includes the first management center 3, the second management center 4, and the third management center 5, but the third management center 5 may be excluded from the mobility IoT 1. Alternatively, the mobility IoT 1 may include one or more management centers in addition to the first management center 3, the second management center 4, and the third management center 5.

[0017] The edge device 2 is mounted on a vehicle. The edge device 2 collects various vehicle data, normalizes the collected vehicle data, converts it into a standard format, and structures the data. By normalizing the vehicle data, the vehicle data is converted into vehicle data in which the same physical quantities indicate the same values, regardless of the vehicle model and vehicle manufacturer.

[0018] The edge device 2 also generates standardized vehicle data. The standardized vehicle data is generated for each vehicle (i.e., for each edge device 2) and has a multi-layer structure. For example, as shown in FIG. 2, the standardized vehicle data includes items set in the top first layer, such as "attribute information," "powertrain," "energy," "Advanced Driver Assistance System (ADAS) / Autonomous Driving (AD)," "body," "multimedia," and "other." In the layers below each item, data related to each item is stored. Data converted into the standard format is stored in the lowest layer of the "attribute information" item.

[0019] The edge device 2 performs data communication with any one of the first to third management centers 3 to 5 via the wide area wireless communication network NW. The edge device 2 uploads the generated vehicle standardized data to any one of the first to third management centers 3 to 5 via a communication device (not shown).

[0020] The service providing server 6 provides a service to the user by using data from any of the first to third management centers 3 to 5. For example, the service providing server 6 provides a service for managing vehicle operation to the user via the edge device 2. Note that the mobility IoT system 1 includes multiple service providing servers 6, and the multiple service providing servers 6 may provide different services by using data from any of the first to third management centers 3 to 5.

[0021] The first to third management centers 3 to 5 manage the mobility IoT system 1. The first to third management centers 3 to 5 share standardized vehicle data by replication or the like. The first to third management centers 3 to 5 perform data communication with a plurality of edge devices 2, a service providing server 6, and a routing device 7 via a wide area wireless communication network NW. The first to third management centers 3 to 5 also perform data communication with each other via the wide area wireless communication network NW.

[0022] The first to third management centers 3 to 5 correspond to different attributes. That is, the first to third management centers 3 to 5 are assigned different attributes. The first management center 3 corresponds to the first attribute and manages personal information of a first user registered for the first attribute. The second management center 4 corresponds to the second attribute and manages personal information of a second user registered for the second attribute. The third management center 5 corresponds to the third attribute and manages personal information of a third user registered for the third attribute. The personal information includes the user's name, address, telephone number, vehicle registration number, etc., as well as authentication information used to authenticate the user. The authentication information is, for example, a user service ID and a password.

[0023] Due to personal information protection rules applied according to attributes, the first to third management centers 3 to 5 do not manage personal information of users registered for attributes that they do not support. In other words, the first to third management centers 3 to 5 do not share the personal information they manage. The second and third management centers 4 and 5 do not manage personal information of the first user. Furthermore, the first and third management centers 3 and 5 do not manage personal information of the second user. The first and second management centers 3 and 4 do not manage personal information of the third user. The first to third management centers 3 to 5 share information that is not subject to personal information protection with each other.

[0024] The attribute is, for example, a region, a country, etc. In this embodiment, the first attribute corresponds to a first region to which the first user belongs (specifically, a region to which the personal information is registered), the second attribute corresponds to a second region to which the second user belongs, and the third attribute corresponds to a third region to which the third user belongs. Each country or region has rules for protecting personal information, and the first to third management centers 3 to 5 must comply with the rules of the corresponding region. Among the rules for protecting personal information, there is a rule that restricts the personal information of a user belonging to a specific region from being taken out of the specific region. In this embodiment, it is assumed that the first region, the second region, and the third region have rules that restrict the personal information of a user belonging to each region from being taken out of the region. In addition, the attribute may be, for example, an organization such as a company, a school, or a club team.

[0025] The service providing server 6 provides a service by using data from one of the first to third management centers 3 to 5, which is based on the attributes at the time of using the service (for example, the area where the user is currently located), rather than the attributes registered by the user. For example, when a first user, a second user, and a third user use a service provided by the service providing server 6 in a first area, the service providing server 6 uses data from the first management center 3. That is, even if the personal information of the first user is registered in the first management center 3, the personal information of the second user is registered in the second management center 4, and the personal information of the third user is registered in the third management center 5, the service providing server 6 uses data from the first management center 3 to provide a service to the first user, the second user, and the third user.

[0026] As shown in FIG. 3, the first to third management centers 3 to 5 each include a control unit 14, a communication unit 13, and a storage unit 11.

[0027] The control unit 14 is an electronic control device in the form of a microcomputer including a CPU 141, a ROM 142, and a RAM 143. The various functions of the first to third management centers 3 to 5 are realized by the CPU 141 executing a program stored in a non-transient substantial recording medium. In this embodiment, the ROM 142 corresponds to the non-transient substantial recording medium storing the program. Furthermore, the execution of this program executes a method corresponding to the program. Note that some or all of the functions executed by the CPU 141 may be configured in the form of hardware using one or more ICs or the like. Furthermore, the number of microcomputers configuring the control unit 14 may be one or more.

[0028] The communication unit 13 performs data communication with the multiple edge devices 2, the service providing server 6, the routing device 7, and other management centers via the wide area wireless communication network NW. The storage unit 11 is a storage device that stores various data.

[0029] The routing device 7 stores linking information that links each attribute with a user belonging to each attribute. The routing device 7 stores information that is not restricted in taking out or the like under the rules of personal information protection, that is, information that is not subject to personal information protection. For example, the routing device 7 stores a service user ID for identifying a user and a code indicating an attribute in association with each other.

[0030] Specifically, the routing device 7 stores the first linking information, the second linking information, and the third linking information. The first linking information links the first attribute with the first user belonging to the first attribute. The second linking information links the second attribute with the second user belonging to the second attribute. The third linking information links the third attribute with the third user belonging to the third attribute. For example, the service user ID=0001 is linked with the area code X, and the service user ID=0002 is linked with the area code Y. For example, a list of service user IDs belonging to the area code X corresponds to the first linking information, a list of service user IDs belonging to the area code Y corresponds to the second linking information, and a list of service user IDs belonging to the area code Z corresponds to the third linking information. The routing device 7 may store the first to third linking information together. That is, the routing device 7 may store a list in which the service user IDs are associated with the area codes.

[0031] As shown in FIG. 4, the routing device 7 includes a control unit 74, a communication unit 73, a URL DB 72, and a region determination DB 71.

[0032] The control unit 74 is an electronic control device in the form of a microcomputer including a CPU 741, a ROM 742, and a RAM 743. Various functions of the routing device 7 are realized by the CPU 741 executing a program stored in a non-transitive real recording medium. In this embodiment, the ROM 742 corresponds to the non-transitive real recording medium storing the program. Furthermore, the execution of this program executes a method corresponding to the program. Note that some or all of the functions executed by the CPU 741 may be configured in hardware form using one or more ICs or the like. Furthermore, the number of microcomputers constituting the control unit 74 may be one or more.

[0033] The communication unit 73 performs data communication between the first to third management centers 3 to 5 via the wide area wireless communication network NW.

[0034] The area discrimination DB 71 stores attributes (specifically, registered areas) and service user IDs of users registered for those attributes in association with each other. Specifically, the area discrimination DB 71 stores the above-mentioned first association information, second association information, and third association information. The area discrimination DB 71 is also referred to as an attribute discrimination DB. The URL DB 72 stores attributes in association with management centers (specifically, URLs of the management centers) corresponding to the attributes. An individual URL is assigned to each of the first to third management centers 3 to 5. This URL is a URL for data communication with each of the first to third management centers 3 to 5.

[0035] 5 shows functions realized by the first management center 3 and the second management center 4. The first and second management centers 3 and 4 include the functions of block units 31 and 41, authentication units 32 and 42, access Application Programming Interfaces (APIs) 33 and 43, and data management units and .

[0036] The data management units 34, 44 manage the uploaded standardized vehicle data. For example, a first management center 3 installed in a first region manages the standardized data uploaded from vehicles currently in the first region, and a second management center 4 installed in a second region manages the standardized data uploaded from vehicles currently in the second region.

[0037] The access APIs 33 and 43 are standard interfaces for the service providing server 6 to access the data management units 34 and 44 .

[0038] The block units 31 and 41 restrict access to the data managed by the data management units 34 and 44 for each service. That is, the block units 31 and 41 request authentication of a user who uses the data managed by the data management units 34 and 44 for each service.

[0039] The authentication units 32 and 42 authenticate users who are authorized to use the data managed by the data management units 34 and 44 via the service providing server 6.

[0040] <1-2. Processing> Next, user authentication in the case where a second user in a first region uses a service of the service providing server 6 will be described with reference to FIG. 5 and FIG. 6 according to the first embodiment. That is, user authentication in the case where a second user having attributes of the second region is currently in the first region and receives a service will be described. The service providing server 6 acquires the current location of the second user by communicating with a mobile terminal or the like possessed by the second user, and grasps that the second user is in the first region. In the first region, the service providing server 6 accesses data of the first management center 3 provided in the first region. The first management center 3 requests authentication of the second user, but cannot execute authentication processing of the second user because it does not manage authentication information of the second user. If the second user is not authenticated, the service providing server 6 cannot provide the second user with a service using data of the first management center 3.

[0041] Therefore, the routing device 7 requests the second management center 4 located in the second area, which manages the authentication information of the second user, to perform authentication processing of the second user. Such authentication processing of a user occurs, for example, when the second user residing in the second area travels to the first area, rents a car, and uses in the first area a service provided by the service providing server 6 that was used in the second area.

[0042] In S1, the service providing server 6 transmits authentication information of the second user to the block unit 31. The authentication information includes a service user ID and a password.

[0043] In S2, the block unit 31 transmits the authentication information to the routing device 7.

[0044] In S3, the routing device 7 transmits the second user's current region (ie, the first region in which the first management center 3 is located) and the authentication information to the URL DB 72.

[0045] In S4, the routing device 7 transmits the current area and authentication information from the URL DB 72 to the area determination DB 71, and stores the current area in the area determination DB 71. As shown in Fig. 7, the area determination DB 71 stores a service user ID, a registered area name, and a current area name in association with each other.

[0046] In S5, the routing device 7 acquires the registered area name (i.e., the second area which is an attribute) associated with the service user ID from the area discrimination DB 71, and acquires the login URL (i.e., the URL of the second management center 4) associated with the registered area name from the URL DB 72. As shown in Fig. 8, the URL DB 72 stores the registered area name and the login URL associated with each other.

[0047] In S6, the routing device 7 switches the destination for requesting authentication processing to the acquired login URL.

[0048] In S7, the routing device 7 transmits the authentication information of the second user to the switched login URL and requests the authentication process of the second user. That is, the routing device 7 requests the second management center 4 to perform the authentication process of the second user.

[0049] In S8, the authentication unit 42 of the second management center 4 receives the authentication request of the second user and executes authentication processing for the second user.

[0050] Next, in S9, if the authentication of the second user is successful, the authentication unit 42 transmits an authentication token to the service providing server 6. By transmitting the URL of the service providing server 6 together with the authentication information of the second user, the authentication token can be transmitted to the service providing server 6.

[0051] In S10, in response to receiving the authentication token, the service providing server 6 transmits an API request with the authentication token and the current region attached to the routing device 7. The API request is, for example, a request to acquire vehicle data or a request to control the vehicle.

[0052] In S11, the routing device 7 checks whether the current area received from the service providing server 6 matches the current area stored in the area determination DB 71 in S4. If the current areas do not match, in S12, an error notification is sent to the service providing server 6. If the second user moves across areas between the time of S4 and the time of S10, a mismatch in the current areas occurs.

[0053] If the current region matches, the routing device 7 transmits an API request with an authentication token to the authentication unit 42 of the second management center 4 in S13.

[0054] In S14, the authentication unit 42 transmits an API request with the authentication token to the access API 43.

[0055] In S15, the access API 43 verifies whether the authentication token is valid.

[0056] In S16, the access API 43 transmits an API response to the authentication unit 42 if the authentication token is valid.

[0057] In S17, the authentication unit 42 transmits the API response to the service providing server 6. As a result, the second user can use the service of the service providing server 6.

[0058] When the first user uses a service of the service providing server 6 in the first region, the routing device 7 acquires a login URL of the first management center 3 and requests the first management center 3 to perform authentication processing of the first user. The first management center 3 may perform authentication processing of the first user in the authentication unit 32 without requesting authentication from the routing device 7. When the first user uses a service of the service providing server 6 in the second region, the routing device 7 acquires a login URL of the first management center 3 and requests the first management center 3 to perform authentication processing of the first user based on a request from the second management center 4.

[0059] Here, the routing device 7 has been described above as a device separate from the first to third management centers 3 to 5, but the routing device 7 may be included in any of the first to third management centers 3 to 5. FIG. 9 shows an example in which the first management center 3 includes the routing device 7. The first management center 3 includes a URL DB 72 and a region discrimination DB 71 in addition to the control unit 15, the communication unit 13, and the storage unit 11. The control unit 15 includes a CPU 151, a ROM 152, and a RAM 153, and realizes the functions realized by the control unit 74 in addition to the functions realized by the control unit 14. By providing the routing device 7 in any of the first to third management centers 3 to 5, the mobility IoT system 1 can be simplified and costs can be reduced.

[0060] <1-3.Effects> According to the first embodiment described above in detail, the following effects are achieved.

[0061] (1) In response to receiving the authentication information of the second user from the first management center 3, the routing device 7 acquires the second region, which is the registered region of the second user, from the region determination DB 71, and requests authentication processing of the second user from the second management center 4 corresponding to the second region. Therefore, the second user is authenticated by the second management center 4 and can use a service based on the data of the first management center 3, which does not have the authentication information of the second user.

[0062] (2) When a second user belonging to a second region moves to a first region, the second user can use the data of the first management center 3 to receive the same services as those he or she received in the first region.

[0063] 2. Second Embodiment <2-1. Differences from the first embodiment> The second embodiment has a basic configuration similar to that of the first embodiment, and therefore differences will be described below. Note that the same reference numerals as those in the first embodiment indicate the same configuration, and the preceding description will be referred to.

[0064] In the above-described first embodiment, the routing device 7 acquires a login URL of the second management center 4 and requests authentication of the second user from the second management center 4. In contrast, the second embodiment differs from the first embodiment in that the routing device 7 acquires a login URL of the second management center 4 and transmits the acquired login URL to the first management center 3.

[0065] <2-2. Processing> Next, user authentication according to the second embodiment in the case where a second user uses a service of the service providing server 6 in a first region will be described with reference to FIG.

[0066] In steps S21 to S25, the first management center 3 and the routing device 7 execute the same processes as those in steps S1 to S5.

[0067] In S26, the routing device 7 transmits the acquired login URL to the first management center 3.

[0068] In S27, the first management center 3 transmits the authentication information of the second user to the received login URL and requests authentication processing of the second user. That is, the first management center 3 requests authentication processing of the second user to the second management center 4.

[0069] In S28 to S37, the second management center 4, the service providing server 6, and the routing device 7 execute the same processes as in S8 to S17.

[0070] When the first user uses a service of the service providing server 6 in the second region, an authentication process for the first user is requested from the second management center 4 to the first management center 3. In response to the request for authentication of the first user from the second management center 4, the first management center 3 executes the authentication process for the first user.

[0071] Similarly to the first embodiment, the routing device 7 may be included in any one of the first to third management centers 3 to 5.

[0072] <2-3.Effects> According to the second embodiment described above in detail, in addition to the effect (2) of the first embodiment described above, the following effect is further achieved.

[0073] (3) Upon receiving the authentication information of the second user, the first management center 3 transmits the authentication information of the second user to the routing device 7 and receives the second region, which is the registered region of the second user, from the routing device 7. The first management center 3 then requests the second management center 4 corresponding to the second region to perform authentication processing of the second user. That is, when the first management center device receives authentication information of a user other than the managed user, it requests authentication processing from the second management center 4 that manages the authentication information of that user. Therefore, the second user can receive user authentication by the second management center 4 when using a service based on data of the first management center 3 that does not have the authentication information of the second user.

[0074] 3. Other Embodiments Although the embodiments of the present disclosure have been described above, the present disclosure is not limited to the above-described embodiments and can be implemented in various modified forms.

[0075] (a) In the above embodiment, the attribute is a region, but the attribute is not limited to a region. The attribute may be, for example, age, sex, occupation, the presence or absence of a certain qualification, etc.

[0076] (b) Multiple functions possessed by one component in the above embodiments may be realized by multiple components, or one function possessed by one component may be realized by multiple components. Also, multiple functions possessed by multiple components may be realized by one component, or one function realized by multiple components may be realized by one component. Also, part of the configuration of the above embodiments may be omitted. Also, at least part of the configuration of the above embodiments may be added to or substituted for the configuration of another of the above embodiments.

[0077] (c) In addition to the routing device and management center described above, the present disclosure can also be realized in various forms, such as a system having a routing device and two or more management centers as components, a program for causing a computer to function as a routing device or a management center, and a non-transient physical recording medium such as a semiconductor memory on which this program is recorded.

Claims

1. 1. An information system comprising: a first center device (3) corresponding to a first attribute; a second center device (4) corresponding to a second attribute; a service providing server (6) capable of communicating with the first center device and the second center device, and configured to provide a service to a first user belonging to the first attribute and linked to a first vehicle and / or a second user belonging to the second attribute and linked to a second vehicle, by using data of the first center device and / or the second center device; a routing device (7) capable of communicating with the first center device and the second center device, the service providing server is configured to transmit authentication information of the second user to the routing device via the first center device in order to provide the second user with a service that uses data of the first center device; the first center device is configured to transmit the authentication information of the second user received from the service providing server to the routing device; The routing device includes: A storage unit (71) configured to store first linking information linking the first attribute with the first user and second linking information linking the second attribute with the second user; a routing control unit (74) configured to, in response to receiving authentication information of the second user from the first center device corresponding to the first attribute, acquire the second attribute corresponding to the second user from the storage unit, and request authentication processing of the second user from the second center device corresponding to the second attribute; the second center device is configured to receive a request for authentication processing of the second user from the routing control unit, execute the authentication processing of the second user, and transmit an authentication token to the service providing server when the authentication of the second user is successful. Information systems.

2. the routing control unit (74) is configured to, in response to receiving authentication information of the first user from the first center device (3) corresponding to the first attribute, acquire the first attribute corresponding to the first user from the storage unit (71), and request authentication processing of the first user to the first center device corresponding to the first attribute.

2. The information system of claim 1.

3. The routing device (7) is included in the first center device (3) or the second center device (4).

3. An information system according to claim 1 or 2.

4. The first attribute includes a first region to which the first user belongs; The second attribute includes a second region to which the second user belongs; The routing control unit (74) is configured to, in response to receiving authentication information of the second user from the first center device (3) installed in the first area, acquire the second area corresponding to the second user from the storage unit (71), and request authentication processing of the second user to the second center device (4) installed in the second area.

3. An information system according to claim 1 or 2.

5. A management center device (4) including the second center device according to claim 1, an authentication unit configured to manage authentication information of the second user and to execute authentication processing of the second user in response to a request for authentication processing of the second user from the routing device (7); Management center device.

6. a service providing server (6) transmits authentication information of a second user belonging to a second attribute to the first center device (3) in order to provide a service to the second user belonging to a second attribute by using data of the first center device (3) corresponding to the first attribute; The first center device transmits the authentication information of the second user to a routing device in response to receiving the authentication information of the second user; In response to receiving the authentication information of the second user, the routing device (7) acquires the second attribute corresponding to the second user from a table (71) included in the routing device, the table defining first linking information linking the first attribute with a first user belonging to the first attribute and second linking information linking the second attribute with the second user; the routing device requests a second center device (4) corresponding to the acquired second attribute to perform authentication processing of the second user; the second center device executes the authentication process of the second user upon receiving a request for the authentication process of the second user, and transmits an authentication token to the service providing server when the authentication of the second user is successful. How the user is authenticated.

7. 1. An information system comprising: A first center device (3) configured to manage authentication information of a first user belonging to a first attribute; a second center device (4) configured to manage authentication information of a second user belonging to a second attribute; a service providing server (6) capable of communicating with the first center device and the second center device and configured to provide a service to the first user and / or the second user by using data of the first center device and / or the second center device; a routing device (7) capable of communicating with the first center device and the second center device, the service providing server is configured to transmit authentication information of the second user to the routing device via the first center device in order to provide the second user with a service that uses data of the first center device; the first center device is configured to transmit the authentication information of the second user received from the service providing server to the routing device; The routing device includes: A storage unit (71) configured to store first linking information linking the first attribute with the first user and second linking information linking the second attribute with the second user; a routing control unit (74) configured to acquire the second attribute corresponding to the second user from the second association information in response to receiving authentication information of the second user from the first center device, and to transmit information related to the acquired second attribute to the first center device; the first center device is configured to, in response to receiving information about the second attribute from the routing device, request the second center device corresponding to the information about the second attribute to perform authentication processing of the second user; the second center device is configured to receive a request for authentication processing of the second user from the first center device, execute the authentication processing of the second user, and transmit an authentication token to the service providing server when the authentication processing of the second user is successful. Information systems.

8. the first center device (3) is configured to execute authentication processing of the first user in response to a request for authentication processing of the first user from the second center device (4); 8. The information system of claim 7.

9. The first center device (3) includes the routing device (7).

9. An information system according to claim 7 or 8.

10. The first attribute includes a first region to which the first user belongs; The second attribute includes a second region to which the second user belongs; the routing device (7) is configured to acquire the second region corresponding to the second user from the second association information in response to receiving authentication information of the second user from the first center device (3) installed in the first region, and to transmit the acquired second region to the first center device.

9. An information system according to claim 7 or 8.

11. a service providing server (6) transmits authentication information of a second user belonging to a second attribute to the first center device (3) in order to provide a service to the second user belonging to a second attribute by using data of the first center device (3) corresponding to the first attribute; The first center device transmits the authentication information of the second user to a routing device in response to receiving the authentication information of the second user; In response to receiving the authentication information of the second user, the routing device (7) acquires the second attribute corresponding to the second user from a table (71) included in the routing device, the table defining first linking information linking the first attribute with a first user belonging to the first attribute and second linking information linking the second attribute with the second user; the routing device transmits the acquired information regarding the second attribute to the first center device; In response to receiving the information on the second attribute, the first center device requests a second center device (4) corresponding to the information on the second attribute to perform authentication processing of the second user; the second center device executes the authentication process of the second user upon receiving a request for the authentication process of the second user, and transmits an authentication token to the service providing server when the authentication of the second user is successful. How the user is authenticated.

Images