TWI765416B - Method and system for applying services across servers - Google Patents

Abstract

A method and a system for applying services across servers are 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

Method and system for applying for services across servers

The specification proposes a method for applying for a service, especially a method and system for applying for a service across servers by using temporarily stored user authentication data.

If there is a need for a service provided by a company or enterprise, the common practice is not only to apply on paper, but also to connect to the webpage for applying for this service. Users can fill in relevant information according to the guidance of the webpage (which can be called user authentication information) to the corresponding field, and after confirming the submitted content, storage and user identity verification and other procedures, the form for applying for the service will be sent out.

Then, if the user wants to submit another service application later, in addition to the paper application, he also needs to re-connect to the application page for the service and fill in the relevant information to submit the service application. If there are more service requests, the user still needs to perform the same action.

In the prior art, there are still solutions that can simplify the filling of some fields, for example, through the function of storing fields on a web browser, when there is a related field to be filled in next time, it can be directly imported into the corresponding field, but However, due to personal information protection 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 both convenience, speed and security into consideration, and can be reused for applications of different service applications, the disclosure proposes a method and system for applying for services across servers.

The proposed system for applying for services across servers mainly proposes a first server module for receiving a user's request for applying for the first service and reviewing the application for the first service; and a second server module for receiving When the user applies for the second service, the application for the second service is also checked; the system is further provided with a file server module for temporarily storing user authentication data that can be exchanged between different server modules.

In one embodiment, the file server module implements a temporary storage area, and the temporary storage area can be set in the first server module, in the second server module, or as an independent file server, which can be encrypted with security. The technology temporarily stores user authentication data obtained through user authorization. The first servo module, the second servo module and the file servo module can be the same as functional modules providing different services in the same server system, or can be different servers providing different services respectively.

The method and steps of the cross-server application service performed by the system include connecting the first server module with the user device, submitting an application for the first service, and the first server module examines the application for the first service, and then the user The device transmits the user authentication data to the first server module and temporarily stores it in the file server module. Then, when the user device connects to the second server module and applies for the second service, the second server module The user authentication data can be obtained by the file server module upon authorization, and the user can check the application of the second service by the second server module without repeatedly submitting the application data.

Preferably, the temporarily stored user authentication data can be provided with a time limit, and the user authentication data will be automatically deleted after a set period of time after being stored in the temporary storage area, so that the user's personal privacy data can be properly protected. .

For a further understanding of the features and technical content of the present invention, please refer to the following detailed descriptions and drawings of the present invention. However, the drawings provided are only for reference and description, and are not intended to limit the present invention.

The following are specific embodiments to illustrate the embodiments of the present invention, and those skilled in the art can understand the advantages and effects of the present invention from the content disclosed in this specification. The present invention can be implemented or applied through other different specific embodiments, and various details in this specification can also be modified and changed based on different viewpoints and applications without departing from the concept of the present invention. In addition, the drawings of the present invention are merely schematic illustrations, and are not drawn according to the actual size, and are stated in advance. The following embodiments will further describe the related technical contents of the present invention in detail, but the disclosed contents are not intended to limit the protection scope of the present invention.

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 primarily used to distinguish one element from another element, or a signal from another signal. In addition, the term "or", as used herein, should include any one or a combination of more of the associated listed items, as the case may be.

If the user authentication information can be effectively used in different service applications, it can avoid the trouble for users to fill in the information repeatedly. In addition to retaining the information in a temporary storage area, security and confidentiality measures are also proposed to provide users with a safe, fast and secure cross-connection. The solution to the server application service, according to the system embodiment of the cross-server application service proposed in the disclosure, can refer to FIG. A flowchart of an embodiment of a method for applying for services across servers.

This example shows that the system for applying for services across servers 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 , which is used to temporarily store the user authentication data provided by the user when applying for a specific service. Once the user is authorized, the first server 11, the second server 12 or more servers can share the file server 13 Stored user authentication data.

The system for applying for services across servers provides the user to make a service request to any server through the network 10 by using the user device 15 . For example, in the case of a financial system, the first server 11, the second server 12 or more servers may provide different services in financial institutions, and the services may be applying for digital accounts, securities accounts and credit cards These services require users to provide important and private information, so storage technology with security protection is required. The services to which the method is applicable also do not exclude services outside the financial industry, such as telecommunication services. In the cross-server application service method, the user can agree to apply for multiple services at one time, and the user's authentication data will be temporarily stored in the file server 13. When any service is approved and authorized by the user, The first server 11 or the second server 12 can obtain the temporarily stored user authentication data from the file server 13 to directly check multiple services, and users do not need to apply one by one.

According to the process described in FIG. 2 , at the beginning, as in 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 The application form provided by 11 fills in the data (generates all or part of the user authentication data) to apply for the first service, and also transmits the user authentication data to the first server 11 .

The first server 11 then verifies whether to agree to provide the service according to the application information provided by the user. At this time, as in step S103, the first server 11 can use the user authentication information (which may be all or part of the user authentication information provided by the user) after being authorized. copies) are 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 according to user identification data (eg, user ID).

Next, in step S105 , when the user connects to the second server 12 through the user device 15 and applies for the second service to the second server 12 , the second server 12 can request the file server 13 through authorization. After obtaining the user authentication data, the computer program running in the file server 13 can extract (decrypt) the user authentication data (part or all) according to 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 examines 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), the authentication data should not be exchanged without the user's consent. In the cross-server application service 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 conveniently Apply for a variety of 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 function modules that are combined with software programs and hardware. A first servo module, a second servo module and a file servo module are respectively formed, and these function modules can be the function modules that provide different services in one servo system. Furthermore, the file servo module implements a temporary storage area, and the temporary storage area can be a physical storage device or a memory provided in the first servo module, the second servo module or an independently operating file server. , and use a secure encryption technology to temporarily store the user authentication data obtained by the user's authorization. The independently operating file server may be an independently operating database in the server system, or a storage provided by a third party.

For the related process, please refer to FIG. 3 , which shows a flowchart of an embodiment of a method for applying for a service across servers running among the user device 31 , the first server module 33 , the file server module 35 , and the second server module 37 .

Initially, the user device 31 submits 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 identity verification (step S305 ). ). The first servo module 33 may use a password, a one-time password (OTP), a natural person certificate, or other verification methods, such as verification results of other third parties (such as joint test results), to confirm the user's identity. User identity.

Next, 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 checks the first service application issued by the user (step S309 ). In this example, after the first servo module 33 completes the verification, it can transmit the verification result to the user device 31 (step S311 ), which can also include a link to apply for the second service. For example, taking applying for financial services as an example, when a user completes a credit card application, the relevant page can continue to recommend the user to apply for a loan business. According to the method embodiment of the cross-server application service, subsequent application services can obtain The user authentication information provided at the first application can improve the inconvenience of repeatedly filling in the 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 for the 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 may be provided with a validity period, that is, the set data expiration time, when the user authentication data is stored in the temporary storage area a later It will be deleted automatically 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 server module 37 for the second service (step S315 ), and also transmits the user identification data (user ID) to the second server module 37 . Similarly, the second server module 37 The user's 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 the user authentication data from the file server module 35 according to the obtained user identification data (step S319 ). After confirming the user authorization, the second server module 37 also obtains user authentication from the file server module 35 . data (step S321 ), let the second servo module 37 verify the application for the second service proposed by the user according to 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 servo module 33 and the second servo module 37 can be various financial services provided by financial institutions. All services can share user authentication data through the file server module 35 , and for services with highly repetitive application data, users can smoothly apply. 4 , when the user transmits the user authentication data to the first servo module 33 through the user device 31 (such as step S305 ), the user can also authorize the second server through the service application interface. The server module 37 obtains user authentication data from the file server module 35 . Refer to FIG. 4 for the flow of the related embodiment.

In FIG. 4 , the first server initially receives the connection of the user device through the service interface (step S401 ), verifies the user identity through the service interface (step S403 ), and receives the first service application and user authentication data ( Step S405), at the same time, the information that the user can apply for the second service from the second server is also provided on the service interface, such as a recommended advertisement. Once the user agrees, the second server can be authorized through the service interface. The user authentication data submitted by the user this time is acquired (step S407 ).

In the process, on the one hand, the first server verifies the application for the first service this time (step S409 ), and on the other hand, the first server stores the user authentication data in the file server (step S411 ). After completing the review, the first server may notify the user of the review result.

The file server can set a time limit for each piece of user authentication data, that is, a time limit for data expiration. 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 a second service application through the service interface, which may include user identification information (step S415 ), so that the second server can access the user The identification data submits a request to the file server to obtain the user authentication data, and after confirmation, the second server obtains the user authentication data (step S417 ), and can directly examine 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, The second server is authorized to obtain user authentication data from the file server. For an embodiment, reference may be made to the flowchart shown in FIG. 5 .

Similarly, 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 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 information and authorization to obtain the user authentication information (step S507 ), so that the second server can obtain the user authentication information from the file server. Obtain user authentication data (step S509 ), and directly examine the application for the second service (step S511 ).

To sum up, according to the above embodiments, when the first server (or module) and the second server (or module) receive the service application request sent by the user device, they will first confirm the user identity, and Send the service interface to the user device, such as the service interface presented by a web interface or a user interface generated by a specific application, after the user fills in and generates the first consent form, the user authentication information is also sent to the file The server (or module) can also authorize the second server to obtain user authentication information in order to apply for the second service and generate a second consent form, in which the user authentication information can be automatically applied to the service application form to generate the first 2. Consent. Finally, the first server and the second server review the first consent form and the second consent form respectively. It is worth mentioning that, in addition to the characteristics of re-authorization of the proposed solution, the file server can set a timeliness for the user authentication data in it, so as to realize the data deletion right of personal data (or called the right to be deleted). The right to forget), and also realize the right to data portability in line with the spirit of the European Union Data Protection (GDPR).

The contents disclosed above are only preferred feasible embodiments of the present invention, and are not intended to limit the scope of the present invention. Therefore, any equivalent technical changes made by using the contents of the description and drawings of the present invention are included in the application of the present invention. within the scope of the patent.

10: Internet 15: User device 11: The first server 12: Second server 13: File server 31: User device 33: The first servo module 35: File Servo Module 37: Second Servo Module Steps S101 to S107: the process of applying for services across servers Steps S301-S323: the process of applying for services across servers Steps S401 to S419: the process of applying for services across servers Steps S501-S511: the process of applying for services across servers

FIG. 1 shows a schematic diagram of an embodiment of a system architecture for cross-server application service;

FIG. 2 shows a flow chart of an embodiment of a method for implementing a cross-server application service by the system;

3 shows a flowchart of an embodiment of a method for applying for services across servers;

FIG. 4 shows a flow chart of one embodiment of a method for applying for a service across servers; and

FIG. 5 shows a flowchart of the second embodiment of the method for applying for services across servers.

31: User device

33: The first servo module

35: File Servo Module

37: Second Servo Module

S301: Request the first service

S303: Authentication required

S305: Pass user authentication data

S307: Apply for the first service

S309: Review

S311: Audit result

S313: Temporarily store user authentication data

S315: Request the second service

S317: Confirm user identity

S319: Request user authentication data

S321: Obtain user authentication data

S323: Audit

Claims (6)

A method for applying for a service across servers, comprising: a user device connects to a first server module, and sends a request for applying for a first service, and the first server module examines the application for the first service; the The user device transmits a user authentication data to the first server module, and the first server module temporarily stores the user authentication data to a file server module, wherein the file server module is implemented in the first server module. A temporary storage area in the servo module, the second servo module or an independently operating file server, the file server module temporarily stores the user authentication data obtained through a user's authorization by a secure encryption technology ; and the user device is connected to a second server module, the user device sends a request for a second service to the second server module, and then authorizes the second server module to be served by the file server module The group obtains the user authentication data, and the second server module examines the application for the second service. The method for applying for services across servers as claimed in claim 1, wherein the temporarily stored user authentication data has a time limit, and when the user authentication data is stored in the temporary storage area after a set period of time, it will be Deleted automatically. A system for applying for services across servers, comprising: a first server module for receiving a request from a user device to apply for a first service, and reviewing the application for the first service; a second server module for receiving the The user device makes a request for applying for a second service, and examines the application for the second service; a file server module is used to store a user authentication data; wherein the system execution steps of the cross-server application service include: the The user device connects to the first server module, submits an application for the first service, and the first server module examines the application for the first service; the user device transmits the user authentication data to the first server module, and temporarily stored in the file server module, wherein the file server module implements a temporary storage area set in the first server module, the second server module or an independently operating file server, the file The server module temporarily stores the user authentication data obtained through a user's authorization by a secure encryption technology; and the user device is connected to the second server module, and the user device submits a request to the second server module When applying for the second service, the second server module is authorized to obtain the user authentication data from the file server module, and the second server module examines the application for the second service. The system for applying for services across servers as described in claim 3, wherein the first servo module, the second servo module and the file server module are the same function modules that provide different services in the same server system, or It is for different servers that provide different services. The system for cross-server application service according to claim 3 or 4, wherein the temporarily stored user authentication data has a time limit, when the user authentication data is stored in the temporary storage area after a set period of time is automatically deleted. The system for applying for services across servers as claimed in claim 5, wherein the first service and the second service provided by the first server module and the second server module respectively are multiple financial services provided by a financial institution , after the user's authorization, the various financial services share the user authentication data through the file server module.

Images