JP7720743B2 - Service collaboration system, server, and service collaboration method - Google Patents

Description

The present invention relates to technology for sharing numbers recorded on a recording medium among multiple service systems.

Technology for linking multiple services is known. For example, Patent Document 1 discloses that, in response to a user request, if a first account for using a first service and a second account for using a second service are valid, the accounts for the first service and the second service are associated with an intermediary device and stored as a user account that can use a linked service that links the first service and the second service; and when the user wants to use the linked service, the intermediary device is queried to control its use.

Patent No. 6097953

The technology described in Patent Document 1 does not allow the number recorded on the recording medium to be shared among a plurality of service systems.
In response to this, the present invention provides a technique for sharing a number recorded on a recording medium among a plurality of service systems.

One aspect of the present disclosure provides a service collaboration system including a relay server that communicates with a first server that is an administrative server of a first service that uses a recording medium, and a second server that is an administrative server of a second service that is different from the first service, wherein the relay server has a number acquisition means that acquires a first number input on a user terminal via an input screen that accepts input of a first number that corresponds to the recording medium and is disclosed to the user in the first service, a delivery request means that transmits a delivery request to the first server, the delivery request including the first number received by the number acquisition means, a response receiving means that receives from the first server, as a response to the delivery request, number information that includes at least one of the encrypted first number, a second number that corresponds to the first number and is unique to the recording medium, and a third number that corresponds to the first number and is provided in the first service, and a registration request means that transmits a registration request that includes the number information and identification information of the user to the administrative server of the second service, and wherein the second server has a registration means that, in response to the registration request from the relay server, registers the number information in a record that corresponds to the user's identification information in a database related to the second service.

The second service may be an access management platform service, the service collaboration system may have a third server that provides a third service on the platform service, the third server may have a screen transmission means that transmits a screen to the user terminal to display the input screen on the user terminal, and the number acquisition means may acquire the first number from the third server.

The relay server may have a screen transmission means for transmitting a screen to the user terminal for displaying the input screen on the user terminal, and the number acquisition means may acquire the first number from the user terminal.

In the response, at least one of the second number and the third number may be hashed.

The delivery request may be an API request, and the response may be an API response.

The relay server may have an information receiving means for receiving, from the first server, stop information indicating that a specific recording medium has been stopped, and a notification means for notifying the second server upon receiving the stop information that use of the recording medium has been stopped. In response to the notification, the registration means in the second server may write a flag indicating that the recording medium is in a stopped state to a database related to the second service.

The database related to the second service may include, for each of a plurality of users, the number of recording media allocated to that user, and when a request is made for a user to register a new recording medium that exceeds the number of recording media allocated to that user, the registration means may write, to the database related to the second service, information for invalidating at least one recording medium already recorded in association with that user in the database related to the second service, and at least one of the second number and the third number corresponding to the new recording medium.

Another aspect of the present disclosure relates to a first service that uses a recording medium, and provides a server having: a number acquisition means for acquiring a first number input in a user terminal via an input screen that accepts input of a first number that corresponds to the recording medium and is disclosed to the user in the first service; a delivery request means for sending a delivery request including the first number received by the number acquisition means to a management server of the first service; a response receiving means for receiving from the management server, in response to the delivery request, number information including at least one of the encrypted first number, a second number that corresponds to the first number and is unique to the recording medium, and a third number that corresponds to the first number and is provided in the first service; and a registration request means for sending a registration request including the number information and the user's identification information to a management server of a second service that is different from the first service.

Yet another aspect of the present disclosure is a service collaboration method in a system having a relay server that communicates with a first server that is a management server of a first service that uses a recording medium, and a second server that is a management server of a second service that is different from the first service, the method including the steps of: the relay server acquiring, for the first service that uses a recording medium, a first number that is input in a user terminal via an input screen that accepts input of a first number that corresponds to the recording medium and that is disclosed to a user in the first service; the relay server transmitting a delivery request including the first number to the management server of the first service; a step of receiving, from a management server of the second service, number information including at least one of the encrypted first number, a second number corresponding to the first number and unique to the recording medium, and a third number corresponding to the first number and given in the first service, as a response to the delivery request; a step of the relay server transmitting a registration request including the number information and user identification information to a management server of the second service; and a step of the management server of the second service registering the number information in a record corresponding to the user identification information in a database related to the second service in response to the registration request from the relay server.

According to the present invention, numbers recorded on a recording medium can be shared among multiple service systems.

1 is a diagram showing an overview of a service collaboration system 1 according to an embodiment. FIG. 1 is a diagram illustrating an example of the functional configuration of a service collaboration system 1. FIG. 2 is a diagram illustrating an example of the hardware configuration of a server 10. FIG. 2 is a diagram illustrating an example of the hardware configuration of a user terminal 90. FIG. 3 is a diagram illustrating data recorded in a medium database 211. 4 is a sequence chart showing the operation of the service collaboration system 1. FIG. 3 is a diagram illustrating data recorded in a database 311. FIG. 10 is a diagram illustrating an example of an input screen for entry and exit management information. FIG. 10 is a diagram illustrating an example of an input screen for a hotel reservation. FIG. 10 is a diagram illustrating an example of an input screen for adding or changing a recording medium. FIG. 10 is a diagram illustrating an example of an input screen for adding or changing a recording medium.

1. Configuration FIG. 1 is a diagram illustrating an overview of a service collaboration system 1 according to an embodiment. The service collaboration system 1 is a system for providing a service (hereinafter referred to as an "integrated service") that collaborates among service systems 2, 3, and 4. "Collaborating" these service systems refers to sharing user data, particularly user identification numbers, among the multiple service systems. The service systems 2, 3, and 4 are systems that provide different services to users. The service systems 2, 3, and 4 are each operated by different operators. In one example, the service system 2 is a system that provides a service (first service) that uses a recording medium, the service system 3 is a system that provides an access management platform service (second service) that manages access to places or objects with different security levels (hereinafter referred to as "access objects"; in this embodiment, the access objects are physical objects or places, and simple data is not included in the access objects), and the service system 4 is a system that provides a service (third service) to end users on the platform service provided by the service system 3.

In one example, the first service is a fare payment service using a transportation IC card, and the second service is a platform service for access control using the cloud. The third service may be any service that uses the platform of the second service. Conventionally, registering a transportation IC card used in the first service so that it can be used in the third service required the second service or the operator of the third service to physically take custody of the transportation IC card and register the data, which was cumbersome. Service collaboration system 1 addresses this problem. In other words, service collaboration system 1 allows users to easily register a transportation IC card used in the first service in the second service, thereby making it easy to use the transportation IC card in the third service provided on the platform of the second service.

The third service uses a media reader (not shown) to read data from a recording medium. In one example, this recording medium and media reader are a so-called contactless IC card and its card reader (more specifically, an IC card and card reader that communicates in accordance with standards such as NFC Type-F, Type-A, Type-B, or ISO/IEC 15693). In other words, a user can access an object by holding a registered recording medium over the card reader. The service system 4 has a management terminal (not shown) that communicates with this card reader. The management terminal is a computer device connected to the card reader and controls the card reader. The management terminal has the function of communicating with other devices, such as server 30, via a network such as the Internet. A single management terminal may control multiple card readers. Alternatively, the card reader and management terminal may be integrated.

Service collaboration system 1, service system 2, service system 3, and service system 4 each have at least a server. The servers of service collaboration system 1, service system 2, service system 3, and service system 4 are referred to as server 10 (an example of a relay server), server 20 (an example of a first server), server 30 (an example of a second server), and server 40 (an example of a third server), respectively. Server 10, server 20, server 30, and server 40 are connected via the Internet or a dedicated line, etc. Users of these services can access each service system from a user terminal 90.

Server 20 is a server for providing a first service, server 30 is a server for providing a second service, and server 40 is a server for providing a third service. Server 10 is a relay server that relays data between server 20 and server 30.

Figure 2 is a diagram illustrating the functional configuration of the service collaboration system 1. The service collaboration system 1 has a storage means 11, a screen transmission means 12, a number acquisition means 13, a delivery request means 14, a response receiving means 15, a registration request means 16, an information receiving means 17, a notification means 18, a control means 19, a storage means 21, a screen transmission means 22, a notification means 23, a control means 29, a storage means 31, a receiving means 32, a registration means 33, a screen transmission means 34, a number transmission means 35, a control means 39, a storage means 41, a screen transmission means 42, a number transmission means 43, a control means 49, a storage means 91, a receiving means 92, a UI means 93, a transmission means 94, and a control means 99. In this example, the storage means 11, screen transmission means 12, number acquisition means 13, delivery request means 14, response receiving means 15, registration request means 16, information receiving means 17, notification means 18, and control means 19 are implemented in server 10, the storage means 21, notification means 23, and control means 29 are implemented in server 20, the storage means 31, reception means 32, registration means 33, screen transmission means 34, number transmission means 35, and control means 39 are implemented in server 30, the storage means 41, screen transmission means 42, number transmission means 43, and control means 49 are implemented in server 40, and the storage means 91, reception means 92, UI means 93, transmission means 94, and control means 99 are implemented in user terminal 90.

In the server 10, the storage means 11 stores various data and programs. In this example, the data stored in the storage means 11 includes a management database 111. The management database 111 is a database that records, for each of a plurality of recording media, the first number of that recording medium and the identification information of the second service that sent the registration request, in association with each other. The number acquisition means 13 acquires the first number entered via an input screen on the user terminal 90. This input screen is sent to the user terminal 90 from the server that provides the service (e.g., server 30 or server 40).

The delivery request means 14 transmits a delivery request including the first number received by the number acquisition means 13 to the management server of the first service (i.e., server 20). The response receiving means 15 receives a response to the delivery request from the management server. This response includes number information. The number information includes either (1) or (2) below.
(1) Encrypted first number.
(2) A number corresponding to the first number, which is at least one of a second number unique to the recording medium and a third number given in the first service.
The term "encryption" as used herein is a concept that includes not only a process of reversibly converting information using an encryption key, but also a process of irreversibly converting information, such as hashing. The registration request means 16 transmits a registration request including the number information included in the response to the delivery request and the user's identification information to the management server of the second service (i.e., server 30). The control means 19 performs various controls.

The information receiving means 17 receives stop information from the management server of the first service indicating that use of a specific recording medium has been stopped. Upon receiving the stop information, the notification means 18 notifies the management server of the second service, which is recorded in association with the recording medium in the management database, that use of the recording medium has been stopped.

In the server 20, the storage means 21 stores various data and programs. In this example, the data stored in the storage means 21 includes a media database 211. The media database 211 is a database that records information about the recording media used in the service system 2. The control means 29 performs various controls.

In the server 30, the storage means 31 stores various data and programs. In this example, the data stored in the storage means 31 includes a database 311. The database 311 is a database that records the correspondence between users of the second service and recording media. The receiving means 32 receives various information from other devices. In this example, the information received by the receiving means 32 includes a registration request from the relay server. In response to the registration request from the relay server, the registration means 33 registers at least one of the second number and the third number in a record corresponding to the user's identification information in the database related to the second service.

In this example, the server 30 not only provides platform services to other businesses, but also provides services on this platform to end users. The functions of the screen transmission means 34 and number transmission means 35 described below are functions related to the services provided on this platform. The screen transmission means 34 transmits data to the user terminal 90 for displaying an input screen that accepts input of the first number disclosed to the user in the first service. The number transmission means 35 transmits the first number entered via this input screen on the user terminal 90 to the server 10. The control means 39 performs various controls.

In the server 40, the storage means 41 stores various data and programs. In this example, the data stored in the storage means 41 includes a database (not shown) that records the attributes of users of the third service and objects to be accessed. The screen transmission means 42 transmits data to the user terminal 90 for displaying an input screen that accepts input of the first number. The number transmission means 43 transmits the first number entered via this input screen on the user terminal 90 to the server 10. The control means 49 performs various controls.

In the user terminal 90, the storage means 91 stores various data and programs. The receiving means 92 receives information from other devices. The UI means 93 presents information to the user and accepts instructions or information input from the user. The transmitting means 94 transmits information to other devices.

Figure 3 is a diagram illustrating the hardware configuration of server 10. Server 10 is a computer device having a CPU (Central Processing Unit) 101, memory 102, storage 103, and communication IF 104. CPU 101 is a processing device that performs various calculations according to programs. Memory 102 is a main storage device that functions as a work area when CPU 101 executes programs, and includes, for example, RAM (Random Access Memory). Storage 103 is an auxiliary storage device that stores various data and programs, and includes, for example, an HDD (Hard Disc Drive) or SSD (Solid State Drive). Communication IF (Interface) 104 is a device that communicates according to a predetermined communication standard (for example, Ethernet (registered trademark)), and includes, for example, a NIC (Network Interface Card).

In this example, the programs stored in storage 103 include a program (hereinafter referred to as the "relay server program") that causes the computer device to function as server 10 of service collaboration system 1. When CPU 101 is executing the relay server program, at least one of memory 102 and storage 103 is an example of storage means 11. Communication IF 104 is an example of screen transmission means 12, number acquisition means 13, response reception means 15, information reception means 17, and notification means 18. CPU 101 is an example of delivery request means 14, registration request means 16, and control means 19.

Servers 20, 30, and 40 have the same hardware configuration as server 10. In Figure 3, the symbols for the elements of servers 20, 30, and 40 are shown in parentheses.

In the server 20, the programs stored in the storage 203 include a program (hereinafter referred to as the "first server program") that causes the computer device to function as the server 20 of the service collaboration system 1. When the CPU 201 is executing the first server program, at least one of the memory 202 and the storage 203 is an example of storage means 21. The CPU 101 is an example of notification means 23 and control means 29. The communication IF 104 is an example of screen transmission means 22.

In the server 30, the programs stored in the storage 303 include a program (hereinafter referred to as the "second server program") that causes the computer device to function as the server 30 of the service collaboration system 1. When the CPU 301 is executing the second server program, at least one of the memory 302 and the storage 303 is an example of storage means 31. The communication IF 304 is an example of receiving means 32 and screen transmission means 34. The CPU 301 is an example of registration means 33 and control means 39.

In the server 40, the programs stored in the storage 403 include a program (hereinafter referred to as the "third server program") for causing the computer device to function as the server 40 of the service collaboration system 1. When the CPU 401 is executing the third server program, at least one of the memory 402 and the storage 403 is an example of storage means 41. The CPU 401 is an example of control means 49. The communication IF 404 is an example of screen transmission means 42.

Figure 4 is a diagram illustrating the hardware configuration of a user terminal 90. The user terminal 90 is a computer device, such as a smartphone or personal computer, having a CPU 901, memory 902, storage 903, communication IF 904, display 905, and input device 906. The CPU 901 is a processing device that performs various calculations according to programs. The memory 902 is a main storage device that functions as a work area when the CPU 901 executes programs, and includes, for example, RAM. The storage 903 is an auxiliary storage device that stores various data and programs, and includes, for example, an SSD or HDD. The communication IF 104 is a device that communicates according to a predetermined communication standard (e.g., LTE (registered trademark), 5G, Wi-Fi, etc.), and includes, for example, an LTE chip and antenna. The display 905 is a device that displays information, and includes, for example, an LCD or organic EL display. The input device 906 is a device for inputting instructions or information to the user terminal 90, and includes, for example, at least one of a touch screen, keyboard, and pointing device.

In this example, the programs stored in storage 903 include a program (hereinafter referred to as the "client program") for causing a computer device to function as a user terminal 90 of the service collaboration system 1. The client program is a dedicated application program or a general-purpose web browser. When the CPU 901 is executing the client program, at least one of the memory 902 and storage 903 is an example of storage means 91. The communication IF 904 is an example of receiving means 92 and transmitting means 94. The display 905 and input device 906 are examples of UI means 93. The CPU 901 is an example of control means 99.

2. Operation 2-1. Basic Operation First, we will explain the basic operation of the service collaboration system 1. In the following, functional elements such as the delivery request means 14 may be described as the subject of processing, which means that a hardware element such as the CPU 101 executing a program executes processing in cooperation with other hardware elements.

Here, we consider a certain user (hereinafter referred to as "User X"). User X is using the first service before the start of the processing described below, and possesses an issued recording medium (e.g., an IC card). User X is attempting to register information about the recording medium he owns in the service collaboration system 1 in order to receive other services, such as the third service. In other words, before the start of the sequence in Figure 6, User X is registered as a user in the service system 2. Specifically, in the server 20, information about the recording medium that has been issued to User X is recorded in the media database 211.

The term "recording medium" as used here refers to a medium on which data such as identification information is electromagnetically recorded, and in one example refers to a medium from which data can be read via contactless communication or near-field wireless communication. This recording medium may, for example, be in the shape of a card (a so-called contactless IC card). Alternatively, this recording medium may be a computer device such as a smartphone or wearable device on which an application program is installed to function as a recording medium for the first service.

Figure 5 is a diagram illustrating data recorded in the media database 211. The media database 211 includes multiple records. Each record includes information about the recording medium, such as user identification information, a first number, a second number, and a third number.

User identification information is information for uniquely identifying a user of the first service, such as an email address, user number, or account name. The user identification information may be specified by the user or may be automatically generated by the service system 2.

The first number is an identification number uniquely assigned to the recording medium. The first number is assigned, for example, by a provider of the first service. The first number is visually displayed on the recording medium. In this respect, the first number can be said to be a number disclosed to the user. Specifically, for example, if the recording medium is a contactless IC card, the first number is issued in a form linked to the contactless IC card. In one example, the first number is printed on the front or back of the card. Alternatively, if the recording medium is a smartphone with an application program installed, the first number is displayed on the screen of the application. Note that the method of disclosing the first number to the user is not limited to these. For example, the first number may not be printed on the card, but may be notified to the user via another medium (e.g., email or written document). Since the first number is a number uniquely assigned to the recording medium, it may be updated to a new number, for example, in the following cases:
・When a contactless IC card is reissued.
- When switching from contactless IC cards to smartphone applications.
- If you change your smartphone device (so-called model change).

The second number is an identification number uniquely assigned to the recording medium. The second number is assigned, for example, by the manufacturer of the recording medium. In that sense, the second number can be said to be the manufacturing number of the recording medium. The second number and the first number are independent and are assigned according to different rules. In one example, the second number is recorded on an IC chip when the recording medium is manufactured and cannot be rewritten after the recording medium has been distributed. In another example, when a smartphone or wearable device (e.g., a smartwatch) is used as the recording medium, the second number may be written to the IC chip after the smartphone or wearable device is manufactured. Unlike the first number, the second number is not actively disclosed to the user (although it may be disclosed).

The third number is an identification number assigned to users of the first service. The third number is assigned, for example, by the provider of the first service. In this example, the third number is a value obtained by inputting the first number into a specified conversion formula, and has a one-to-one correspondence with the first number. The first number can be obtained by inputting the third number into the inverse function of this conversion formula. In this example, the third number is recorded in an encrypted area on the recording medium, and the third number itself cannot be read externally from the recording medium without the encryption key corresponding to this encrypted area.

Figure 6 is a sequence chart showing the operation of one embodiment of the service collaboration system 1. In step S101, the number acquisition means 13 of the server 10 acquires the first number to be registered. In this example, there are at least four routes by which the number acquisition means 13 can acquire the first number. That is, a route in which the first number is acquired directly from the user (without going through another server), a route in which the first number is acquired from server 20, a route in which the first number is acquired from server 30, and a route in which the first number is acquired from server 40. In this example, the number acquisition means 13 may acquire the first number from any of these four routes. Here, we will first explain an example in which the server 10 acquires the first number directly from the user.

Details of step S101 are as follows: User X accesses server 40 from his/her user terminal 90. Upon receiving access from user terminal 90, server 40 transmits data to user terminal 90 for displaying a menu screen for the third service. User terminal 90 displays the menu screen for the third service according to this data. This menu screen includes a UI object (e.g., a "Register" button) for newly registering a recording medium that has already been registered in the first service but not yet registered in the linked service in the third service. When user X operates this UI object, the connection destination is redirected to server 10 (step S1011). User terminal 90 accesses server 10, which is the redirect destination (step S1012). Upon receiving access from user terminal 90, screen transmission means 12 in server 10 transmits data of an input screen that accepts input of the first number to user terminal 90 (step S1013). At this time, screen transmission means 12 transmits data of the input screen corresponding to the redirect source. Note that the method for changing the connection destination of the user terminal 90 from server 40 to server 10 is not limited to redirection; a method of presenting a hyperlink to server 10 on the user terminal 90 may also be used.

In the user terminal 90, the receiving means 92 receives the data from this input screen. The UI means 93 displays this input screen (step S1014). The UI means 93 accepts input of the first number and specification of additional information related to this recording medium (e.g., information related to the corresponding service) via user operation on this input screen (step S1015). When an instruction is input via the UI object for sending a registration request for the first number (e.g., when the registration button is pressed), the transmitting means 94 sends a registration request for the input first number to the server 10 (step S1016). This registration request includes the input first number and additional information related to the target service. In this way, the number acquisition means 13 acquires the first number (step S102).

When the number acquisition means 13 receives the registration request, the delivery request means 14 sends a delivery request to the server 20 (step S103). This delivery request includes the first number included in the registration request. In one example, the delivery request means 14 sends this delivery request as an API (Application Programming Interface) request.

When a delivery request is received from the server 10, the control means 29 in the server 20 determines whether a record including the first number included in the delivery request is recorded in the media database 211 stored in the storage means 21. If it is determined that a record including the first number included in the delivery request is recorded, the control means 29 extracts information from this record (step S104). In one example, the extracted information includes the first number. In another example, the extracted information includes at least one of the second number and the third number. The control means 29 converts the extracted number information into another value (step S105). In one example, the control means 29 hashes the extracted number information. The hash function used for hashing here is the same as the hash function used to hash the number read by the reader/writer described below. Note that if it is determined that a record including the first number included in the delivery request is not recorded, the control means 29 performs error processing.

The control means 29 sends a delivery response including the hashed number information to the server 10 that sent the delivery request (step S106). In one example, the control means 29 sends this delivery response as an API response.

In the server 10, the response receiving means 15 receives the delivery response (step S107). When the response receiving means 15 receives the delivery response from the server 10, the control means 19 writes the hashed number information included in the delivery response to the record corresponding to user X in the management database 111. Note that the process of writing this data to the management database 111 may be omitted.

When the response receiving means 15 in the server 10 receives the delivery response from the server 20, the registration request means 16 sends a registration request to the server 30 (step S107). This registration request includes hashed number information, user X's identification information, and the target service's identification information. User X's identification information is the user's identification information in the linked service. User X's identification information is determined, for example, by a login process. The target service's identification information is included in the registration request received in step S102.

In server 30, receiving means 32 receives a registration request from server 10. Registration means 33 writes the hashed number information and target service identification information included in the registration request to a record in management database 311 corresponding to user X's identification information (step S108).

Figure 7 is a diagram illustrating the data recorded in database 311. Database 311 includes multiple data sets. Each data set includes user identification information, service identification information, access object identification information, recording medium identification information, and access conditions. An access object is, for example, an electric lock. In this example, multiple services can be registered for one user. One or more access objects are registered for each service. One or more recording media are registered for each access object. Access conditions are registered for each recording media. Access conditions indicate the conditions (e.g., date, day of the week, and/or time period) under which access to the access object is permitted. In other words, database 311 can be said to record the correspondence between services, access objects, recording media, and access conditions for each user.

For example, the example in Figure 7 shows that a user with identification information "1234567" has registered a recording medium to "Service A." This user has registered access objects with identification numbers "501" and "726." The access object with identification number "501" has registered a recording medium with the first number "AB12345678912345." The access condition for the recording medium with the first number "AB12345678912345" is registered as "from 3:00 PM on July 8, 2021 to 10:00 AM on July 9, 2021." The access object with identification number "726" has registered a recording medium with the first number "AB12345678912345" and a recording medium with the first number "AB98765432198765." The condition registered as the access condition for these two recording media is "from 3:00 PM on July 24, 2021 to 9:00 AM on July 27, 2021." As will be described later, in database 311, the identification information for each recording medium includes hashed number information. In database 311, the hashed number information does not need to include all of the first number, second number, and third number, and may include only a portion of them (for example, only the first number).

Service system 4 can manage access using recording media registered in database 311 in service system 3. Access to the object to be accessed is performed, for example, as follows:

(1) Access example 1
When a user holds a recording medium they own over a card reader (not shown) corresponding to the object to be accessed, the card reader reads the third number from the recording medium. The card reader inputs the read third number into a predetermined conversion formula to obtain the first number. This conversion formula is the same as the conversion formula used to generate the third number to be recorded on the recording medium. The card reader then hashes the first number obtained by the conversion. The hash function used by the card reader to hash the first number is the same as the hash function used by the server 20 to hash the number information. The card reader then transmits an authentication request to a management terminal (not shown) that includes the hashed first number and identification information of the electric lock corresponding to the card reader. The management terminal is a computer device installed in a physical area (e.g., in the same building) that includes the object to be accessed and connected to the card reader. The management terminal communicates with the server 30 via a network such as the Internet. The management terminal then transmits the authentication request received from the card reader to the server 30.

Upon receiving an authentication request, server 30 refers to database 311 to determine whether to authenticate the authentication request. Database 311 stores the electric lock's identification information, the hashed first number of the registered recording medium, and the corresponding access conditions. Server 30 compares the authentication request with database 311. If database 311 contains a record containing data identical to the combination of the hashed first number and electric lock's identification information included in the authentication request and the authentication request satisfies the access conditions, server 30 affirms the authentication request. If database 311 does not contain a record containing data identical to the combination of the hashed first number and electric lock's identification information included in the authentication request, or if the access conditions are not satisfied, server 30 denies the authentication request. Server 30 sends an authentication response indicating the authentication result to the management terminal that sent the authentication request.

When the management terminal receives an authentication response from the server 30, it outputs a signal to the card reader according to the authentication result. If the authentication is confirmed, the management terminal outputs an unlock signal to the card reader. If the authentication is denied, the management terminal outputs an error signal to the card reader. When the card reader receives an unlock signal from the management terminal, it outputs an unlock signal to the corresponding electric lock. When the card reader receives the unlock signal, the electric lock unlocks. When the card reader receives an error signal from the management terminal, it performs error processing (for example, by outputting a beep).

In the above example, the server 30 determines whether to authenticate the authentication request, but as another example, the management terminal or electronic lock may perform the authentication (without querying the server 30). In this case, the management terminal or electronic lock has a whitelist (i.e., a list of numbers that are allowed for authentication) and refers to this whitelist to make the authentication decision.

(2) Access example 2
When a user holds a recording medium they own over a card reader corresponding to the object to be accessed, the card reader reads the second number from the recording medium. The card reader hashes the read second number. The hash function used by the card reader to hash the second number is the same as the hash function used by the server 20 to hash the number information. The card reader sends an authentication request including the hashed second number and identification information of the electric lock corresponding to the card reader to a management terminal (not shown). The management terminal sends the authentication request received from the card reader to the server 30.

Upon receiving an authentication request, server 30 refers to database 311 to determine whether to authenticate the authentication request. Database 311 stores the electric lock's identification information, the hashed second number of the registered recording medium, and the corresponding access conditions. Server 30 compares the authentication request with database 311. If database 311 contains a record containing data identical to the combination of the hashed second number and electric lock's identification information included in the authentication request and the authentication request satisfies the access conditions, server 30 acknowledges the authentication request. If database 311 does not contain a record containing data identical to the combination of the hashed second number and electric lock's identification information included in the authentication request, or if the access conditions are not met, server 30 denies the authentication request. Server 30 sends an authentication response indicating the authentication result to the management terminal that sent the authentication request.

When the management terminal receives an authentication response from the server 30, it outputs a signal to the card reader according to the authentication result. If the authentication is confirmed, the management terminal outputs an unlock signal to the card reader. If the authentication is denied, the management terminal outputs an error signal to the card reader. When the card reader receives an unlock signal from the management terminal, it outputs an unlock signal to the corresponding electric lock. When the card reader receives the unlock signal, the electric lock unlocks. When the card reader receives an error signal from the management terminal, it performs error processing (for example, by outputting a beep).

The number information used for authentication differs between Access Example 1 and Access Example 2. Database 311 only needs to record the number information used for authentication. The number information used for authentication is determined, for example, depending on the service or the reader/writer being used.

2-2. Usage Examples Below, we will explain some specific examples of access to the access object.

2-2-1. Entrance/Exit Management System First, we will explain an example of a service provided by the service system 3. In this example, the service system 3 is a building entrance/exit (or access/exit) management service, and the objects to be accessed are areas with different security levels, more specifically, gates installed at the boundaries of these areas.

User X is an employee of an organization (e.g., a company or hospital) that uses service system 3. Database 311 records, as an object, the identification information of the electric lock on the gate installed at the boundary of the security-segregated area. User X has already registered as a user with service system 3 in order to use this access control system. User X accesses server 30 from user terminal 90. Server 30 sends data to user terminal 90 to display an input screen for entering access control information.

Figure 8 is a diagram showing an example of an input screen for entry and exit management information. This input screen includes input fields 991, 992, and a register button 993. Input field 991 is an area for entering information specifying access restrictions. In this example, the organization using service system 3 is a hospital. In this example, security levels within the hospital are categorized according to the attributes of the visitors, such as "visitors," "nurses," and "doctors." For example, it is defined that doctors can enter and exit all areas at any time, nurses can only enter and exit their assigned wards and examination rooms, and visitors can enter and exit inpatient wards with time restrictions. Input field 992 is a UI object for entering the first number. Register button 993 is a UI object for instructing a reservation request related to the information entered in input field 991.

In this example, User X is the receptionist at the inpatient ward. A family member (i.e., a visitor) who wishes to visit an inpatient presents their transportation IC card to User X at the reception desk of the inpatient ward. At this time, User X may request that the visitor enter the visitor's name and contact information, as well as the name of the inpatient. User X enters the first number and other information on the transportation IC card they have been presented with on the input screen shown in Figure 8.

When the registration button 993 is pressed, the server 30 sends a registration request for the recording medium to the server 10. This registration request includes the first number and associated information entered in the input field 992. The associated information includes identification information indicating the security level (e.g., "visitor"). The server 30 stores a database (not shown) that records the correspondence between security levels and the identification information of electric locks for this organization. The server 30 references this database to identify the electric lock that corresponds to the specified security level.

Upon receiving this registration request, server 10 acquires from server 20 the hashed number information of the recording medium corresponding to this first number, as described in Figure 6. Server 10 then transmits a registration request for the acquired hashed number information to server 30. This registration request includes a security level as additional information corresponding to this first number.

The server 30 registers the following items A to C in the database 311 in the record corresponding to the identifier of the electric lock included in the registration request.
a) User identification information (for visitors and other non-employee members of the organization, User X may register the name he or she has heard from the visitor, or a common identification such as "visitor" may be used)
a) The first number of the recording medium, hashed number information; c) Security level; d) Contact information of the external user who will use the recording medium; e) Time period, if any. When the registration of data about this visitor is complete, the server 30 notifies the user terminal 90, i.e., user X, that the data registration is complete. The server 30 may also notify the visitor that the data registration is complete. For example, the server 30 sends an email containing a message that the addition is complete to the visitor who has completed adding the recording medium.

In this example, regular hospital employees, as well as non-regular employees such as temporary and part-time staff, can be given time-limited access privileges. Visitors to hospitalized patients can also be granted access privileges only to areas that they are authorized to access using their transportation IC card. By installing electronic locks in each patient room and defining access restrictions, access control for each patient room is also possible.

Here, we have used an example of hospital entrance/exit management, but entrance/exit management for corporate visitors can also be performed in a similar manner. Furthermore, the reception desk can be left unmanned and visitors or guests can operate the user terminal 90 themselves, registering their own transportation IC card when entering the building.

2-2-2. Hotel Reservation Management Next, an example of a service in the service system 4 will be described. In this example, the service system 4 is a hotel reservation management service, and the object to be accessed is the electric lock of a guest room. The database 311 records the identification information of the electric lock of the guest room of this hotel as the object. User X has already registered as a user in the service system 4 to make a reservation for accommodation at this hotel. User X accesses the server 40 from a user terminal 90. The server 40 transmits data to the user terminal 90 for displaying an input screen for inputting a reservation.

Figure 9 is a diagram illustrating an example of an input screen for hotel reservations. This input screen includes input fields 994, 995, and a register button 993. Input field 994 is a UI object for entering information for reserving a hotel room (in this example, room type, number of guests, number of nights, check-in time, and check-out time). Input field 995 is a UI object for entering a first number. Note that in input field 995, first numbers of recording media can be entered up to the same number as the number of guests staying (for example, if two people are staying, first numbers of two recording media can be entered). Register button 993 is a UI object for issuing a reservation request related to the information entered in input field 994. User X, for example, enters the first number of his or her own transportation IC card in input field 994.

When the registration button 993 is pressed, the server 40 determines whether a room can be allocated for this accommodation reservation request. The server 40 stores a database (not shown) that records guest rooms and their reservation status. The server 40 references this database to determine whether a room can be allocated for this accommodation reservation request.

If it is determined that a room can be allocated in response to this accommodation reservation request, server 40 sends a recording medium registration request to server 10. This registration request includes the first number entered in input field 992 and additional information about the accommodation reservation service. In this example, the additional information includes the identification information of the user who made the accommodation reservation, the identification information of the electronic lock corresponding to the reserved room, and the check-in time and check-out time. Server 40 stores a database (not shown) that records the correspondence between the identification information of the room and the identification information of the electronic lock. Server 40 references this database to identify the electronic lock corresponding to the reserved room.

Upon receiving this registration request, server 10 acquires from server 20 the hashed number information of the recording medium corresponding to this first number, as described in Figure 6. Server 10 then transmits a registration request for the acquired hashed number information to server 30. This registration request includes additional information about the accommodation reservation service corresponding to this first number.

The server 30 registers the following items A to C in the database 311 in the record corresponding to the identifier of the electric lock included in the registration request.
a) User identification information b) First number of the recording medium, hashed number information c) Check-in time and check-out time Once the registration of the data related to this reservation is complete, server 30 notifies server 40, the sender of the registration request, that the data registration has been completed.

When server 30 receives notification that data registration is complete, server 40 notifies user terminal 90 that the reservation is complete. This notification includes, for example, the guest room number. Once the registered check-in time has passed, the user can enter the guest room using the registered recording medium.

When user X holds his or her transportation IC card over a card reader (not shown) corresponding to the electronic lock in the guest room, the card reader reads the second number from the transportation IC card. The card reader hashes the read second number. The hash function used by the card reader to hash the second number is the same as the hash function used by server 20 to hash the second number. The card reader sends an authentication request including the hashed second number and identification information of the electronic lock corresponding to the card reader to a management terminal (not shown). The management terminal is a computer device installed in the hotel and connected to the card reader. The management terminal communicates with server 30 via a network such as the Internet. The management terminal sends the authentication request received from the card reader to server 30.

Upon receiving an authentication request, server 30 refers to database 311 to determine whether to authenticate the authentication request. Database 311 stores the electric lock's identification information, the hashed second number of the registered recording medium, and the corresponding access conditions. Server 30 compares the authentication request with database 311. If a record containing data identical to the combination of the hashed second number and electric lock's identification information included in the authentication request is stored in database 311, and the authentication request satisfies the access conditions (for example, the authentication request time is between the check-in time and the check-out time), server 30 acknowledges the authentication request. If a record containing data identical to the combination of the hashed second number and electric lock's identification information included in the authentication request is not stored in database 311, or if the access conditions are not met, server 30 denies the authentication request. Server 30 sends an authentication response indicating the authentication result to the management terminal that sent the authentication request.

When the management terminal receives an authentication response from the server 30, it outputs a signal to the card reader according to the authentication result. If the authentication is confirmed, the management terminal outputs an unlock signal to the card reader. If the authentication is denied, the management terminal outputs an error signal to the card reader. When the card reader receives an unlock signal from the management terminal, it outputs an unlock signal to the corresponding electric lock. When the card reader receives the unlock signal, the electric lock unlocks. When the card reader receives an error signal from the management terminal, it performs error processing (for example, by outputting a beep).

Previously, in order to enable user X to unlock the guest room's electronic lock with his or her transportation IC card, the hotel operator had to obtain and manage user X's transportation IC card number, which made the process complicated and raised security concerns. However, with this example, the hotel does not need to obtain or manage user X's transportation IC card number. Furthermore, with this example, hotel operators can reduce personnel and material costs by eliminating guest check-in and check-out procedures at the reception counter (e.g., issuing and collecting card keys).

2-2-3. Keys to a Residential Apartment Building In this example, the service system 4 is an entry management service for a residential apartment building, and the objects to be accessed are the electric locks of each unit. The database 311 records the identification information of the electric locks of each unit in this apartment building as the objects. Each unit is assigned a maximum number of recording media that can be registered. User X is a resident of this apartment building, and has already registered as a user with the service system 4 in order to lock and unlock his or her home using his or her own transportation IC card. User X accesses the server 40 from a user terminal 90. The server 40 sends data to the user terminal 90 to display an input screen for inputting the addition or change of recording media.

Figure 10 is a diagram illustrating an input screen for adding or changing a recording medium. This input screen includes an input field 996, an input field 997, and a register button 993. The input field 996 is a UI object for entering the type of use (temporary or permanent) of the recording medium to be added or changed, and, if temporary, the period of use. The input field 997 is a UI object for entering the first number. Note that in this example, the input field 997 is part of the input field 996. In this example, a pet name and the corresponding external user's contact information can be recorded for each recording medium, and the input field 995 also includes input fields for the pet name and contact information. The register button 993 is a UI object for issuing a request to add or change a recording medium related to the information entered in the input field 991. For example, User X enters the first number of a transportation IC card held by a family member or friend who lives separately into the input field 992 so that the family member or friend can temporarily enter his or her home when User X is not present.

When the registration button 993 is pressed, the server 40 sends a request to register the recording medium to the server 10. This registration request includes the first number and additional information about the residence entered in the input field 996. In this example, the additional information includes the type of use, pet name, contact information, and, in the case of temporary use, the period of use. The server 40 stores a database (not shown) that records the correspondence between the identification information of each household and the identification information of the electric lock. The server 40 references this database to identify the electric lock corresponding to the specified residence. Here, the "electric lock corresponding to the specified residence" may include the electric lock on the front door of the residence, as well as electric locks in shared spaces (e.g., apartment building entrances, garbage disposal areas, meeting halls, bicycle parking areas, and parking lots). Alternatively, whether or not to include electric locks in these shared spaces may be selected individually on the input screen of FIG. 10.

Upon receiving this registration request, server 10 obtains from server 20 the hashed number information of the recording medium corresponding to this first number, as described in Figure 6. Server 10 then transmits a registration request for the hashed number information thus obtained to server 30. This registration request includes additional information about the residence corresponding to this first number.

The server 30 registers the following items A to C in the database 311 in the record corresponding to the identifier of the electric lock included in the registration request.
a) User identification information b) First number of the recording medium, hashed number information c) Type of use d) Contact information of the external user who will use the recording medium e) In the case of temporary use, for that period Once registration of data regarding this residence is completed, server 30 will notify server 40, the sender of the registration request, that the data registration has been completed.

When server 30 receives notification that data registration has been completed, server 40 notifies user terminal 90 that the reservation has been completed. In addition to the user terminal 90 that sent the registration request, server 40 may also notify the contact information of the external user corresponding to the newly added or changed recording medium that the recording medium has been registered. For example, server 40 sends an email containing a message that the addition has been completed to the external user who has completed adding the recording medium.

When an external user possessing a recording medium registered by User X visits User X's apartment and holds their transportation IC card over a card reader (not shown) corresponding to the electric lock at the entrance or the card reader corresponding to the electric lock on the front door of User X's residence, the card reader reads the second number from the transportation IC card. The card reader hashes the read second number. The hash function used by the card reader to hash the second number is the same as the hash function used by Server 20 to hash the second number. The card reader sends an authentication request to a management terminal (not shown) that includes the hashed second number and identification information of the electric lock corresponding to the card reader. The management terminal is a computer device installed in the apartment and connected to the card reader. The management terminal communicates with Server 30 via a network such as the Internet. The management terminal sends the authentication request received from the card reader to Server 30. The following processing for this authentication request is the same as that described in 2-2-1.

Previously, in order to allow a family member or friend of User X to unlock the electronic lock on an apartment building using a transportation IC card, the apartment building management company had to obtain and manage the external user's transportation IC card number, which made the process complicated and raised security concerns. However, with this example, the apartment building management company does not need to obtain or manage User X's transportation IC card number.

2-2-4. Key Management for Rental Properties In this example, the service system 4 is a key management service for rental housing, and the object to be accessed is an electric lock installed on the front door of the rental property. The database 311 records the identification information of the electric lock of the rental property as the object. User X is the owner of this rental property, and has already registered as a user in the service system 4 so that a management company or real estate agent can lock/unlock the property when managing or viewing the property. User X accesses the server 40 from a user terminal 90. The server 40 sends data to the user terminal 90 to display an input screen for inputting additions and changes to recording media.

Figure 11 is a diagram illustrating an input screen for adding or changing a recording medium. This input screen includes an input field 998, an input field 999, and a register button 993. The input field 998 is a UI object for entering the type of use (temporary or permanent) of the recording medium to be added or changed, and, if temporary, the period of use. The input field 999 is a UI object for entering a first number. Note that in this example, the input field 999 is part of the input field 998. In this example, it is possible to record contact information for external users for each recording medium, and the input field 997 includes a contact information input field. The register button 993 is a UI object for issuing a request to add or change a recording medium related to the information entered in the input field 998. For example, User X enters the first number of the transportation IC card held by the real estate agent into the input field 999 so that the real estate agent can guide (or show) prospective tenants to the property.

When the registration button 993 is pressed, the server 40 sends a request to register the recording medium to the server 10. This registration request includes the first number entered in the input field 996 and additional information about the property. In this example, the additional information includes the type of use, contact information, and, in the case of temporary use, the period of use. The server 40 stores a database (not shown) that records the correspondence between property identification information and electric lock identification information. The server 40 references this database to identify the electric lock corresponding to the specified property. Here, the "electric lock corresponding to the specified property" may include not only the electric lock on the property's front door, but also the electric locks in common spaces (e.g., the apartment building entrance, garbage area, meeting hall, bicycle parking area, and parking lot) if the property is an apartment building. Alternatively, whether or not to include the electric locks in these common spaces may be selected individually on the input screen of FIG. 11.

Upon receiving this registration request, server 10 acquires from server 20 the hashed number information of the recording medium corresponding to this first number, as described in Figure 6. Server 10 then transmits a registration request for the acquired hashed number information to server 30. This registration request includes additional information about the property corresponding to this first number.

The server 30 registers the following items A to C in the database 311 in the record corresponding to the identifier of the electric lock included in the registration request.
a) User identification information b) First number of the recording medium, hashed number information c) Type of use d) Contact information of the external user who will use the recording medium e) In the case of temporary use, for that period Once the registration of data regarding this property is completed, server 30 will notify server 40, the sender of the registration request, that the data registration has been completed.

When server 30 receives notification that data registration has been completed, server 40 notifies user terminal 90 that registration has been completed. In addition to notifying the user terminal 90 that sent the registration request, server 40 may also notify the contact information of the external user corresponding to the newly added or changed recording medium that the recording medium has been registered. For example, server 40 sends an email containing a message that the addition has been completed to the external user (e.g., a real estate agent) who has completed adding the recording medium.

When an external user possessing a recording medium registered by User X visits User X's rental property and holds their transportation IC card over a card reader (not shown) corresponding to the electric lock on the front door or a card reader corresponding to the electric lock on the front door of User X's residence, the card reader reads the second number from the transportation IC card. The card reader hashes the read second number. The hash function used by the card reader to hash the second number is the same as the hash function used by Server 20 to hash the second number. The card reader sends an authentication request to the management terminal (not shown) that includes the hashed second number and identification information of the electric lock corresponding to the card reader. The management terminal is a computer device installed in the property and connected to the card reader. The management terminal communicates with Server 30 via a network such as the Internet. The management terminal sends the authentication request received from the card reader to Server 30. The following processing for this authentication request is the same as that described in 2-2-1.

Previously, in order to be able to unlock an apartment building's electronic lock using a transportation IC card held by a real estate agent or management company, the property owner (or someone entrusted with management by the owner) had to obtain and manage the external user's transportation IC card number, which made the process complicated and raised security concerns. However, with this example, the property owner does not need to obtain or manage the transportation IC card number of the real estate agent or management company.

This external user may be a tenant of the property. Alternatively, an external user with permission from the property owner may access the server 40 and register their own recording medium on behalf of the property owner. In this case, the owner, for example, registers the account of the person authorized to register the recording medium in the service system 4.

3. Modifications The present invention is not limited to the above-described embodiment, and various modifications are possible. Several modifications are described below. Two or more of the features described in the modifications described below may be used in combination.

3-1. Access Authentication In the embodiment, an example has been described in which a hashed second number is used for access authentication to an access target object, but the information used for access authentication is not limited to this. Either Access Example 1 or Access Example 2 may be used for access authentication. Alternatively, both the hashed second number and the hashed third number may be used. Furthermore, as a further alternative, the card reader may output at least one of the second number and the third number without hashing, and access authentication may be performed using the unhashed second number or the unhashed third number.

Furthermore, server 10 does not need to send number information that is not used for access authentication to the management server of the second service. For example, server 10 has a database (not shown) that records the identification information of the management server of the service and the type of number (second number or third number) used for access authentication in that service. Server 10 refers to this database to decide whether to send the hashed second number or the hashed third number.

3-2. Transmission of Input Screen The device that transmits the screen for inputting the first number to the user terminal 90 is not limited to the server 10. Instead of the server 10, the server 20 (i.e., the first server) may transmit the screen for inputting the first number to the user terminal 90. In this case, the input screen includes a UI object for inputting information specifying the service to which the recording medium is to be registered. In this case, the server 10 acquires the first number from the server 20. In an example in which the server 10 acquires the first number from the server 20 or directly from the user terminal 90, the first number can be handled without going through another service such as the second service, thereby improving security compared to when the first number is transmitted via another service.

It should be noted that multiple servers among server 10, server 20, server 30, and server 40 may all have a screen transmission means. In this case, the server accessed by user terminal 90 (e.g., server 40) determines which server will transmit the input screen depending on the type of recording medium (more specifically, the issuer of the recording medium). In this case, for example, server 40 accepts input of information indicating the type of recording medium. If this information indicates that the recording medium is issued by a specific issuer, server 40 will redirect to server 10; otherwise, server 40 will redirect to server 20.

3-3. Method for Inputting the First Number The method for inputting the first number of the recording medium in the user terminal 90 is not limited to the example exemplified in the embodiment. For example, the user terminal 90 may photograph the first number printed on the surface of the recording medium with a camera (not shown) and read the first number from the image. The first number on the surface of the recording medium may be represented not as a character string but as an image code such as a QR Code (registered trademark). If the user terminal 90 and the recording medium are integrated (for example, if the recording medium is a contactless IC card chip of a smartphone), the user terminal 90 may automatically obtain the first number using an application program that reads data from the contactless IC card chip.

3-4. Notification of discontinuation of use of recording medium In this example, the service system 2 manages the issuance or activation of recording media. A user who wishes to discontinue use of a recording medium or who has lost a recording medium notifies the service system 2 that they will discontinue use of the recording medium. Upon receiving notification from the user that they will discontinue use of the recording medium, the server 20 rewrites the information indicating the usage status of the recording medium in the media database 211, specifically, for example, the value of the valid/invalid flag, to "invalid." If the value of this flag is "invalid," the server 20 does not transmit the second number or the third number in response to a delivery request from the server 30 or the server 40.

Furthermore, in this example, the notification means 23 of the service system 2 notifies the server 10 of the identification information (e.g., the first number) of the recording medium whose flag value has been rewritten to "invalid." The information receiving means 17 of the server 10 receives this notification. When the information receiving means 17 receives this notification, the notification means 18 sends a notification to the management server of the access management platform service (i.e., server 30) that the recording medium will be suspended. This notification includes the identification information (e.g., the first number) of the recording medium.

Upon receiving this notification, the registration means 33 of the server 30 writes a flag indicating that the recording medium is in a disabled state to the database 311. When an authentication request is received for a recording medium whose flag indicates that it is in a disabled state, the server 30 denies the authentication request. In other words, a recording medium that is registered as being in a disabled state in service system 2 can also be disabled in other service systems, such as service system 3 and service system 4 provided on the platform of service system 3.

3-5. Writing a Disabled Flag The server 30 may write a disabled flag to the database 311 without receiving a notification from the server 20. In this example, the database 311 records the number of recording media allocated to each user. When a request is made to register a new recording medium that exceeds the number of allocated recording media, the registration means 33 writes information to invalidate at least one recording medium already recorded in the database 311 for that user (rewrites the usage status flag to "invalid"). Furthermore, the registration means 33 writes the hashed second number and hashed third number corresponding to the new recording medium to the database 311.

3-6. Multiple Platform Services In the above embodiment, an example was described in which a platform service for access management using a recording medium is provided by a single system (service system 3). However, the platform service for access management using a recording medium may be provided by multiple different systems. In this case, the server 10 transmits a registration request for the recording medium to the servers of these multiple systems. Alternatively, the server 10 may have a database (not shown) that records the correspondence between services and platforms, and may refer to this database to select a server for the access management platform service to which to transmit the registration request. For example, when a registration request for a recording medium for "Service A" is received from the server 40, the server 10 transmits the registration request for the recording medium to the server of the platform service that is shown to correspond to Service A in the database.

3-7. Other Modifications The structures of the various input screens and databases described in the embodiments are merely examples, and the present invention is not limited to these. For example, the server 10 does not need to have the management database 111.

The hardware configuration of the devices constituting each system, such as service collaboration system 1, is not limited to that exemplified in the embodiments. For example, each server may be a physical server or a virtual server (e.g., a so-called cloud). Furthermore, the functional configuration of each system, such as service collaboration system 1, is not limited to that exemplified in the embodiments. At least some of the functional elements of each system may be omitted. Furthermore, the correspondence between the functional elements and hardware elements in each system, such as the service collaboration system, is not limited to that exemplified in the embodiments. For example, various databases may be stored in a device separate from the server that performs processing by referencing those databases. Alternatively, some of the functions described in the embodiments as being implemented in a single server device may be implemented in another server device or a user terminal.

Programs executed by processors such as CPU 101 may be downloaded via a network such as the Internet, or may be provided recorded on a non-transitory recording medium such as a CD-ROM.

1...service collaboration system, 2...service system, 3...service system, 4...service system, 10...server, 11...storage means, 12...screen transmission means, 13...number acquisition means, 14...delivery request means, 15...response receiving means, 16...registration request means, 17...information receiving means, 18...notification means, 19...control means, 20...server, 21...storage means, 22...screen transmission means, 23...notification means, 29...control means, 30...server, 31...storage means, 32...receiving means, 33...registration means, 34...screen transmission means, 35...number transmission means, 39...control means, 40...server, 41...storage means, 42...screen transmission means, 43...number transmission means, 49...control means, 90...user terminal, 91...storage means Stage, 92...receiving means, 93...UI means, 94...transmitting means, 99...control means, 101...CPU, 102...memory, 103...storage, 111...management database, 201...CPU, 202...memory, 203...storage, 211...media database, 301...CPU, 302...memory, 303...storage, 311...management database, 401...CPU, 402...memory, 403...storage, 901...CPU, 902...memory, 903...storage, 905...display, 906...input device, 991...input field, 992...input field, 993...registration button, 994...input field, 995...input field, 996...input field, 997...input field, 998...input field, 999...input field.

Claims (9)

a relay server that communicates with a first server that is a management server for a first service that uses a recording medium;
a second server that is a management server for a second service different from the first service;
The relay server
a number acquiring means in the user terminal for acquiring a first number input via an input screen that accepts input of a first number that corresponds to the recording medium and is disclosed to the user in the first service;
a delivery request means for transmitting a delivery request including the first number received by the number acquisition means to the first server;
a response receiving means for receiving, from the first server, number information including at least one of the encrypted first number, a second number corresponding to the first number and unique to the recording medium, and a third number corresponding to the first number and given in the first service, as a response to the delivery request;
a registration request means for transmitting a registration request including the number information and the user's identification information to the management server of the second service,
The second server,
a registration means for registering the number information in a record corresponding to the user's identification information in a database related to the second service in response to the registration request from the relay server. the first server has a screen transmission means for transmitting a screen for displaying the input screen on the user terminal to the user terminal,
The service collaboration system according to claim 1 , wherein the number acquisition means acquires the first number from the first server. the second service is an access management platform service;
the service collaboration system includes a third server that provides a third service on the platform service;
The third server,
a screen transmission means for transmitting to the user terminal a screen for displaying the input screen on the user terminal,
The service collaboration system according to claim 1 , wherein the number acquisition means acquires the first number from the third server. the relay server has a screen transmission means for transmitting to the user terminal a screen for displaying the input screen on the user terminal,
The service collaboration system according to claim 1 , wherein the number acquisition means acquires the first number from the user terminal. The service collaboration system according to claim 1 , wherein at least one of the second number and the third number in the response is encrypted. The relay server
an information receiving means for receiving, from the first server, suspension information indicating that the use of a specific recording medium has been suspended;
a notification means for notifying the second server that use of the recording medium has been stopped upon receiving the stop information,
6. The service collaboration system according to claim 1, wherein in the second server, the registration means writes information indicating that the recording medium is in a disabled state into a database related to the second service in response to the notification. the database relating to the second service includes, for each of a plurality of users, the number of recording media allocated to that user;
7. The service collaboration system according to claim 1, wherein, when the user requests the registration of a new recording medium that exceeds the number of allocated recording media, the registration means writes, to the database for the second service, information for invalidating at least one recording medium that is already recorded in association with the user in the database for the second service, and at least one of the second number and the third number corresponding to the new recording medium. a number acquisition means for acquiring, in a user terminal, a first number corresponding to the recording medium and disclosed to a user in the first service, the first number being input via an input screen that accepts input of the first number;
a delivery request means for transmitting a delivery request including the first number received by the number acquisition means to a management server of the first service;
a response receiving means for receiving, from the management server, as a response to the delivery request, number information including at least one of the encrypted first number, a second number corresponding to the first number and unique to the recording medium, and a third number corresponding to the first number and given in the first service;
and a registration request means for transmitting a registration request including the number information and the user's identification information to a management server of a second service different from the first service. A service collaboration method in a system having a relay server that communicates with a first server that is a management server of a first service that uses a recording medium, and a second server that is a management server of a second service different from the first service, comprising:
a step in which the relay server acquires, in relation to a first service using a recording medium, a first number that is input via an input screen in a user terminal, the first number corresponding to the recording medium and disclosed to the user in the first service;
the relay server sending a delivery request including the first number to a management server of the first service;
a step of receiving, from the management server, number information including at least one of the encrypted first number, a second number corresponding to the first number and unique to the recording medium, and a third number corresponding to the first number and given in the first service, as a response to the delivery request by the relay server;
the relay server transmitting a registration request including the number information and user identification information to a management server of the second service;
A service collaboration method comprising: a step in which the management server of the second service registers the number information in a record corresponding to the user's identification information in a database related to the second service in response to the registration request from the relay server.