TWM608197U - System for applying services across servers - Google Patents

Abstract

A system for applying services across servers is provided. The system provides a first server, a second server and a temporary storage that is used to buffer user authentication data. A user can send a request of first service to the first server via a user device. In the meantime, user authentication data is also transmitted to the first server. The first server reviews the request of first service. The user authentication data is then buffered to the temporary storage. When the user sends another request of second service to the second server, the second server can retrieve the user authentication data from the temporary storage after getting authorization from the user, and afterwards reviews the request of second service.

Description

Cross-server application service system

The manual proposes a service application system, especially a system that uses temporary user authentication data to implement cross-server application service.

If there is a need for a service provided by a company or enterprise, the common practice is not only to submit an application in paper form, but also to connect to the web page where the service is applied. The user can fill in the relevant information according to the guidance of the web page (it can be called user authentication). Data) to the corresponding field, after confirming the submitted content, storing and user identity verification procedures, the application form for the service is sent out.

Then, if the user wants to apply for another service later, in addition to the paper application, he also needs to connect to the service application webpage again and fill in the relevant information to submit the service application. If there are more service requests, users still need to perform the same actions.

In the conventional technology, there are still solutions that can slightly simplify the filling of some field data. For example, through the function of saving the field on the web browser, the next time there is a relevant field to be filled in, it can be directly imported into the corresponding field, but Because of the protection of personal information or technical limitations, the conventional technology can still only be applied to basic information that does not involve security, such as e-mail.

In order to propose a data exchange solution that takes into account convenience, speed and security, and can be reused for applications for different service applications, the disclosure paper proposes a system of cross-server application services. System.

The proposed cross-server application service system mainly proposes a first server for receiving users' requests for applying for the first service, and reviewing applications for the first service; and a second server for receiving users The request for applying for the second service is also reviewed; the system also has a file server for temporarily storing user authentication data that can be exchanged between different servers.

In one embodiment, the file server implements a temporary storage area. The temporary storage area can be set in the first server, the second server, or a stand-alone file server that can be temporarily stored with secure encryption technology User authentication data obtained through user authorization. The first server, the second server, and the file server may be functional modules that provide different services in the same server system, or may be different servers that provide different services.

The method steps of the cross-server application service executed by the system include after the user device connects to the first server, an application for the first service is submitted, and the application for the first service is reviewed by the first server, and then the user device sends The user authentication data is sent to the first server and temporarily stored in the file server. Then, when the user device connects to the second server and applies for the second service, the second server can be authorized by the file server The server obtains user authentication data, and the user does not need to repeatedly submit application data, and the second server can review the application for the second service.

Preferably, the temporarily stored user authentication data can be set with a timeliness, when the user authentication data is automatically deleted after a set time after being stored in the temporary storage area, so that the user's personal privacy data can be appropriately protected .

In order to further understand the features and technical content of the present invention, please refer to the following detailed descriptions and drawings about the present invention. However, the drawings provided are only for reference and explanation, and are not used to limit the present invention.

10: Internet

15: User device

11: The first server

12: The second server

13: file server

31: User device

33: The first servo module

35: File Servo Module

37: The second servo module

Steps S101~S107: The process of applying for services across servers

Steps S301~S323: The process of applying for services across servers

Steps S401~S419: The process of applying for services across servers

Steps S501~S511: Process of applying for services across servers

Figure 1 shows a schematic diagram of an embodiment of the system architecture for applying for services across servers; Figure 2 shows a flowchart of an embodiment of a method for applying services across servers in a system; Figure 3 shows a flowchart of an embodiment of a method for applying for services across servers; Figure 4 shows A flow chart of one of the implementation examples of the method for applying for services across servers; and FIG. 5 shows a flow chart of the second implementation example of the method for applying for services across servers.

The following is a specific specific embodiment to illustrate the implementation of this creation, and those skilled in the art can understand the advantages and effects of this creation from the content disclosed in this specification. This creation can be implemented or applied through other different specific embodiments, and various details in this specification can also be based on different viewpoints and applications, and various modifications and changes can be made without departing from the concept of this creation. In addition, the drawings of this creation are merely schematic illustrations, and are not depicted in actual size, and are stated in advance. The following implementations will further describe the related technical content of this creation in detail, but the disclosed content is not intended to limit the protection scope of this creation.

It should be understood that although terms such as "first", "second", and "third" may be used herein to describe various elements or signals, these elements or signals should not be limited by these terms. These terms are mainly used to distinguish one element from another, or one signal from another signal. In addition, the term "or" used in this document may include any one or a combination of more of the associated listed items depending on the actual situation.

If the user authentication information can be effectively used in different service applications, the user can avoid the trouble of repeatedly filling in the information. In addition to retaining the information in a temporary storage area, it also proposes security and confidentiality measures to provide users with safe, fast and safe cross-checking. The server application service solution, according to the system embodiment of the cross-server application service proposed in the disclosure, you can refer to Figure 1 which shows the cross-server application service A schematic diagram of an embodiment of a service system architecture, and a flowchart of an embodiment of a method for implementing a cross-server application service in the system shown in FIG. 2 may be referred to.

This example shows that a cross-server application service system has a first server 11 and a second server 12 that provide different services. However, it can be extended to services provided by more servers. The system also proposes a file server 13 , This is used to temporarily store the user authentication data provided when the user applies for a specific service. Once authorized by the user, the first server 11, the second server 12, or more servers can share the file server 13 User authentication data stored.

The cross-server application service system provides a user to use the user device 15 to make a service request to any server via the network 10. For example, in the case of a financial system, the first server 11, the second server 12, or more servers can provide different services in financial institutions. The services can be application for digital accounts, securities accounts, and credit cards. User’s application services, these services require users to provide important and private information, and therefore require storage technology with security protection. The services to which the method is applicable also do not exclude services outside the financial industry, such as telecommunications services. In the cross-server service application method, the user can agree to apply for multiple services at once, and the user's authentication data will be temporarily stored in the file server 13. When any service is allowed and authorized by the user, The first server 11 or the second server 12 can obtain temporary user authentication data from the file server 13 and directly audit multiple services, and the user does not need to apply one by one.

According to the process described in FIG. 2, at the beginning, such as process step S101, the user operates a software program (such as a web browser or a specific application) in the user device 15 to connect to the first server 11, and according to the first server 11 provides the application form to fill in data (generating all or part of the user authentication data) to apply for the first service, and at the same time, it also transmits the user authentication data to the first server 11.

The first server 11 then reviews whether it agrees to provide the service according to the application information provided by the user. At this time, in step S103, the first server 11 can use the service provided by the user after authorization. The user authentication data (which can be all or part of it) is temporarily stored in the file server 13. The file server 13 is provided with a database for storing data and related security encryption measures, so that the user authentication data can be safely temporarily stored in the file server 13 based on user identification data (such as user ID).

Then, in step S105, when the user connects to the second server 12 through the user device 15 and applies for the second service from the second server 12, then the second server 12 can request the file server 13 with authorization. To obtain user authentication data, the computer program running in the file server 13 can extract (decrypt) user authentication data (part or all) based on the user identification data provided by the second server 12, and then provide it to the second server 12. Then, as in step S107, the procedure of applying for the second service is performed, and the second server 12 reviews the application for the second service.

Generally speaking, under the principle of protecting customer privacy data, when users apply for different services (such as financial services with high security requirements for customer data), authentication data should not be circulated without the user’s consent. In the cross-server service application method proposed in the disclosure, different service applications can share user authentication data through the file server 13 under the authorization of the user, so that the user can quickly and easily Apply for multiple services in the servo system.

It is worth mentioning that the first server 11, the second server 12, and the file server 13 are not only different servers providing different services, but also functional modules that are matched by software programs and hardware. The first servo module, the second servo module, and the file servo module are formed respectively, and these functional modules can be the same functional modules that provide different services in the same servo system. Furthermore, the file server module implements a register, and the register can be a physical storage device or a memory set in the first server module, the second server module, or an independent file server In the process, a secure encryption technology is used to temporarily store user authentication data obtained through user authorization. The independently operated file server may be an independently operated database in the server system, or a storage proposed by a third party.

For the related process, refer to FIG. 3, which shows running on the user device 31, the first servo module 33 (which can realize the first server as shown in FIG. 1), and the file servo module 35 (which can realize the file as shown in FIG. 1). Server) and the second server module 37 (which can implement the second server as shown in FIG. 1) cross-server application for service method embodiment flowchart.

Initially, the user device 31 makes a request for the first service to the first server module 33 (step S301). At this time, the first server module 33 generates a service interface (step S303) to request the user's identity to be verified (step S305). ). The first server module 33 may use passwords, one-time passwords (OTP), natural person certificates or other verification methods, such as verification results of other third parties (such as joint registration results), to confirm the user’s identity. User identity.

Then the user generates and transmits user authentication data through the user device 31 to apply for the first service (step S307), and the first server module 33 verifies the first service application sent by the user (step S309). In this example, after the first server module 33 completes the review, the review result may be transmitted to the user device 31 (step S311), which may also include a link to apply for the second service. For example, take the application for financial services as an example. When the user completes the credit card application, the relevant page can continue to recommend the user to apply for the loan business. According to the cross-server application service method embodiment, subsequent application services can be obtained The user authentication information provided in the first application can improve the inconvenience of repeatedly filling in user authentication information.

At this point in time, after the user's authorization, the first server module 33 can temporarily store the user authentication data provided by the user's first service application in the file server module 35 (step S313). In one embodiment, in the file server module 35, the temporarily stored user authentication data can be set with a timeliness, that is, the time when the data is set to expire, when the user authentication data is stored in this temporary storage area (or Register) will be automatically deleted after the set time. If the user authentication data in the file server module 35 is deleted, the user needs to provide the authentication data again when applying for any service in the future.

The user device 31 then requests the second service from the second server module 37 (step S315), and at the same time sends the user identification data (user ID) to the second server module 37. Similarly, the second server module 37 The user identity can also be confirmed through a password, a one-time password, a natural person certificate or other verification methods (step S317). After that, the second server module 37 requests user authentication data from the file server module 35 based on the obtained user identification data (step S319), and after confirming the user authorization, it also obtains user authentication from the file server module 35 Data (step S321), let the second server module 37 review the user's application for the second service based on the obtained user authentication data (step S323).

According to the above process embodiment, the first service and the second service respectively provided by the first server module 33 and the second server module 37 can be a variety of financial services provided by financial institutions. After user authorization, a variety of financial services can be used. All services can share user authentication data through the file server module 35, and there are highly repetitive services for application data, allowing users to apply smoothly. Wherein, referring to the flow of the embodiment in FIG. 4, when the user sends user authentication data to the first server module 33 through the user device 31 (such as step S305), the user can also authorize the second through the service application interface The server module 37 to the file server module 35 obtain user authentication data. Refer to FIG. 4 for the flow of related embodiments.

In Figure 4, the first server initially receives the user device connection through the service interface (step S401), and also verifies the user's identity through the service interface (step S403), and receives the first service application and user authentication data ( Step S405). At the same time, the service interface also provides information that the user can apply for the second service from the second server, such as a recommended advertisement. Once the user agrees, the second server can be authorized through the service interface. Obtain the user authentication data submitted by the user this time (step S407).

In the process, on the one hand, the first server reviews the application for the first service (step S409), and on the other hand, the first server saves the user authentication data to the file server (step S409). S411). After the first server completes the review, it can notify the user of the review result.

The file server can set a timeliness for each user authentication data, that is, the time limit for the data to become invalid. Therefore, the user can apply for the second service to the second server within the specified time limit. In the process, the second server receives the user device connection (step S413), and then receives the second service application through the service interface, which may include user identification data (step S415), so that the second server can access the user The identification data requests the file server to obtain the user authentication data. After confirmation, the second server obtains the user authentication data (step S417), and can also directly review the application for the second service (step S419).

In another embodiment, the user may not authorize the second server to obtain user authentication data from the file server when applying for the first service, but when applying for the second service to the second server, Only authorize the second server to obtain user authentication data from the file server. For the embodiment, reference may be made to the flowchart shown in FIG. 5.

In the same way, at the beginning, the first server receives the request for applying for the first service and the user authentication data from the user device (step S501), the first server reviews the application for the first service (step S503), and also sends the user The authentication data is stored in the file server (step S505).

After that, the second server receives the request for applying for the second service sent by the user device, which also includes the user identification data and the authorization to obtain user authentication data (step S507), so that the second server can obtain the request from the file server Obtain user authentication data (step S509), and directly review the application for the second service (step S511).

In summary, according to the above embodiments, the first server (or module) and the second server (or module) will first confirm the user's identity when receiving a service request request from the user device, and Send a service interface to the user device, such as a web interface or a user interface generated by a specific application. After the user fills in the first consent form, the user authentication information is also sent to the file Server (or module), which can also authorize The second server obtains the user authentication data to apply for the second service, and generates a second consent form, where the user authentication data can be automatically applied to the service application form to generate the second consent form. Finally, the first server and the second server respectively review the first consent letter and the second consent letter. It is worth mentioning that, in addition to the features of the proposed solution that can be re-licensed, the file server can set the timeliness of the user authentication data in it, so as to achieve the right to delete data (or be The right to forget) and the right to data portability are also in line with the spirit of the European Union Data Protection (GDPR).

The content disclosed above is only a preferred and feasible embodiment of the present model, and does not limit the scope of the patent application of the present model. Therefore, all equivalent technical changes made by using the description and schematic content of the present model are included in the application of the present model. Within the scope of the patent.

10: Internet

15: User device

11: The first server

12: The second server

13: file server

Claims (10)

A system for applying for services across servers, including: A first server, receiving a request from a user device to apply for a first service, and receiving a user authentication data sent by the user device to review the application for the first service; A file server, connected to the first server via a network, for storing the user authentication data obtained from the first server; and A second server connects to the file server via the network, receives a request from the user device to apply for a second service, and obtains the user authentication data from the file server to verify the second service Application. The cross-server application service system according to claim 1, wherein the file server implements a register, and the register is provided in the first server, the second server, or is an independent The operating file server temporarily stores the user authentication data obtained through the authorization of a user with a secure encryption technology. For the cross-server application service system described in claim 2, the temporarily stored user authentication data has a timeliness, when the user authentication data is stored in the register after a set time, it will be Automatically delete. The system for applying for services across servers as described in claim 2, wherein the first service and the second service provided by the first server and the second server are multiple financial services provided by a financial institution. The user authorizes the multiple financial services to share the user authentication data through the file server. The system for applying for services across servers according to claim 4, wherein the first server receives the request for the first service through a service interface and obtains the user authentication data, and the first server requests through the service interface Verify the identity of the user. The system for applying for services across servers according to claim 5, wherein after the first server completes the request for reviewing the first service, it transmits the review result to the user device, which includes the link to the second service . The system for applying for a service across servers according to claim 5, wherein the first server verifies the identity of the user by means of a password, a one-time password, a natural person certificate, or a third-party verification method through the service interface. The system for applying for services across servers according to claim 7, wherein when the user transmits the user authentication data to the first server through the user device, the second server is also authorized through the service interface at the same time The server obtains the user authentication data from the file server. The cross-server application service system according to claim 7, wherein only when the user device submits an application for the second service to the second server, the second server is authorized to the file server Obtain the user authentication data. For example, the cross-server application service system described in any one of claim items 1 to 9, wherein the temporarily stored user authentication data has a timeliness, when the user authentication data is stored in the file server It will be deleted automatically after a set time.

Images