TW202025668A - System for maintaining login record to transfer data and method thereof - Google Patents

Abstract

A system for maintaining a login record to transfer data and a method thereof are provided. By providing servers registering by a platform, transferring login data from the platform to at least one of the server when the platform receives the login data sent from a client, updating a login record according to a verification result of the login data sent from the server, and transferring a report data from the platform to the servers which the client is logged in when the platform receives the report data sent from the client, the system and the method can reduce costs of human and financial of developing large number of similar small programs, and can achieve the effect of integrating large number of similar small programs.

Description

Device and method for maintaining log-in status record to transfer data

A data transfer device and method, in particular, refers to a device and method for maintaining log-in status records to transfer data.

Instant Messaging (IM) is a system that communicates through the Internet, allowing two or more people to use the Internet to communicate text messages, files, voice and video in real time. Services are usually provided in the form of websites, computer software or mobile applications.

In some instant messaging programs, users can be provided to install various small programs (or components). In fact, before the mini program can be installed and used in the instant messaging software, the developer needs to pay the management team of the instant messaging software, and provide the mini program to the management team of the instant messaging software for review, and after the review is passed Testing before going live. In other words, for developers, the process of applying for small programs to be installed and used in instant messaging software is tedious and lengthy.

However, in some cases, developers need to develop similar but slightly different small programs for the needs of different customers. When the number of such small programs is too large, when the developer is updating the version of the small program, each different small program needs to repeat the above payment, review and testing process. For the developer, it takes a lot of time. With money.

In summary, it can be seen that in the prior art, the development of a large number of similar small programs used on instant messaging software requires a lot of manpower, material resources and financial resources for maintenance. Therefore, it is necessary to propose improved technical methods. To solve this problem.

In view of the fact that the prior art has the problem that a lot of costs are required for maintenance when developing a large number of similar small programs, the present invention discloses a device and method for maintaining a log-in status record to transfer data, in which:

The device for maintaining log-in status records and transferring data disclosed in the present invention at least includes: a registration module for providing business server registration and generating registration data corresponding to the business server; and a login processing module for logging in according to When the status record judges that the client is not logged in to the business server, send the login data sent by the client to the business server, and receive the verification result sent by the business server when the login data is verified, so as to update the login status record based on the verification result , And used to determine that the client has logged in to the business server based on the login status record, and send report data to the business server that the client has logged in based on the registration data.

The method for maintaining log-in status records and transferring data disclosed in the present invention includes at least the steps of: the business server registers with the service platform, the service platform generates registration data corresponding to the business server; the client provides the input log-in data and transmits the log-in data To the service platform; the service platform sends the login data to the business server; the business server verifies the login data and sends the verification result corresponding to the login data to the service platform; the service platform updates the login status record according to the verification result; the client generates report data and Send report data to the service platform; when the service platform judges that the client has logged in to the business server based on the login status record, it sends the report data to the business server that the client has logged in based on the registration data.

The device and method disclosed in the present invention are as above. The difference between the present invention and the prior art is that after the present invention provides the service server registration through the service platform, when the client sends the login data, the login data is forwarded to the service server, and according to the business The verification result returned by the server updates the login status record, and when the client sends the report data, when the client judges that the client has logged in to the business server based on the login status record, the report data is forwarded to the client's logged-in business server based on the registration data It solves the problems of the prior art and can achieve the technical effect of integrating similar small programs.

The following will describe the features and implementation of the present invention in detail with the drawings and embodiments. The content is sufficient to enable anyone familiar with the relevant art to easily and fully understand the technical means used by the present invention to solve the technical problems and implement them accordingly. The achievable effect of the present invention.

The present invention can centrally manage multiple clients and multiple business servers through a service platform, so that each client can realize different business functions without mutual interference. Among them, the client mentioned in the present invention generally refers to a subprogram of an application program executed in a computing device, but the present invention is not limited to this. For example, it may also be an application program in a computing device.

In the following, the system architecture diagram of maintaining the login status record to transfer data mentioned in the present invention and the component diagram of the device for maintaining login status record to transfer data mentioned in the present invention are used to illustrate the present invention. Invented system operation. As shown in "Figure 1", the system of the present invention includes a business server 100, a service platform 200, and a computing device 400 including a client 410.

The business server 100 can be connected to the service platform 200 via a wired or wireless network, so as to transmit data or signals to the service platform 200, receive data or signals transmitted by the service platform 200, and communicate with the client 410 through the service platform 200.

The business server 100 is responsible for registering with the service platform 200. Generally speaking, the business server 100 can send identification data and interface information to the service platform 200 to register with the service platform 200. Among them, the identification data sent by the business server 100 is sufficient to represent the sent business server 100, which can be composed of any number of words, letters, numbers, and symbols, and the identification data is a unique value; the interface information is the business server The connection information of the service interface provided by 100, including but not limited to network address, port number, path, data format, etc.

In some embodiments, when the business server 100 registers with the service platform 200, in addition to sending identification data, it may also send a timestamp and/or signature to the service platform 200. Wherein, the above-mentioned signature may be a digital signature of the business server 100, or data calculated through a specific algorithm such as MD5, and the present invention is not particularly limited.

The business server 100 is also responsible for receiving the login information sent by the client 410 through the service platform 200 and verifying the received login information. Generally speaking, the business server 100 receives the login information through the provided service interface. The login data mentioned in the present invention is data that can identify the user identity of the client 410, including but not limited to account passwords, fingerprints, and the like.

The business server 100 may also generate a verification result corresponding to the login data after verifying the login data (for example, the login data is verified or not), and may send the generated verification result to the issuing party through the service platform 200 The client 410 corresponding to the login data. The business server 100 may also transmit the verification result only when the login data is verified.

In some embodiments, the business server 100 may also register with the service platform 200, receive the access security token sent by the service platform 200, and send the received authentication result to the service platform 200 together. Access security sign. The access security flag is data corresponding to the business server 100, and is usually a unique value, which can be formed by arbitrarily arranging any number of words, numbers, letters, and symbols.

The business server 100 is also responsible for receiving the report data sent by the client 410 through the service platform 200 and performing relevant business processing on the received report data. Generally speaking, the business server 100 receives the report data through the provided service interface. The report data includes data provided by the client 410 to the business server 100 for business processing. In some embodiments, the report data may also include login data and/or service parameters corresponding to one or more business servers 100. . Wherein, the service parameter is usually a unique value, which can be arbitrarily arranged by any number of words, letters, symbols, and numbers, and is used to represent the corresponding business server 100.

In some embodiments, the business server 100 may also generate a notification message after performing related business processing on the received report data, and send the generated notification message to the service platform 200.

The client 410 can connect to the service platform 200 through a wired or wireless network, so as to receive data or signals transmitted by the service platform 200, and transmit the data or signals to the service platform 200, and communicate with the service server 100 through the service platform 200 .

The client 410 can provide input login information, and send the input login information to the business server 100 through the service platform 200. The client 410 may also receive the verification result corresponding to the login data sent by the business server 100 through the service platform 200.

The client 410 can also receive the logged-in message and the non-logged-in message sent by the service platform through the communication module 210, and can provide input log-in information when receiving the non-logged-in message. The logged-in message may indicate that the client 410 has logged in to the service server 100, and the logged-in message may indicate that the client 410 has not logged in to the service server 100.

The client 410 is responsible for generating report data, and transmits the generated report data to the business server 100 through the service platform 200. In some embodiments, the client 410 may determine whether the client 410 has logged in to the service server 100 according to the received verification result before sending the report data. If yes, the client 410 can send the report data to the business server 100 through the service platform 200; and if the client determines that the business server 100 has not been logged in, the client 410 can first send the login data to the business server 100 through the service platform 200 , And after receiving the verification result that the login data has been verified by the business server 100 through the service platform 200, the report data is sent to the business server 100 through the service platform 200.

The service platform 200 is responsible for providing registration for the business server 100 and forwarding the report data generated by the client 410 to the corresponding business server 100. The service platform 200 further includes a communication module 210, a registration module 220, a login processing module 250, and an additional push module 290.

The communication module 210 is responsible for providing the service server 100 and the client 410 to connect to the service platform 200 through a wired or wireless network, and can transmit data or signals to the service server 100 and/or the client 410, and can also receive the service server 100 And/or the data or signal sent by the client 410.

The registration module 220 is responsible for providing registration of the business server 100 and generating registration data corresponding to the business server 100, so as to complete the registration of the business server 100. Among them, the registration data generated by the registration module 220 includes the interface information sent by each service server 100.

In some embodiments, the registration module 220 can generate an access security mark corresponding to the registered business server 100 after completing the registration of the business server 100, and pass the generated access security mark through the communication module. The group 210 is sent to the corresponding service server.

The registration module 220 can also periodically check whether each registered business server 100 is operating normally according to the interface information in the registration data. For example, the registration module 220 can be based on the business server 100 at a predetermined time or at regular intervals. The network address, port number (and path) of the service interface, send a heartbeat message (heart beat) to the business server 100 through the communication module 210, and based on whether the communication module 210 receives the return from the business server 100 The response message determines whether the business server 100 is operating normally.

The login processing module 250 is responsible for receiving the login data transmitted by the client 410 through the communication module 210, and is responsible for forwarding the received login data to the business server 100 through the communication module 210. The login processing module 250 can determine whether the login data contains service parameters. If the login data includes service parameters, the login processing module 250 can choose to send the login data to one or more business servers 100 corresponding to the service parameters; If the login data does not include service parameters, the login processing module 250 can send the login data to all the business servers 100.

The login processing module 250 is also responsible for receiving the verification result corresponding to the login data sent by the service server 100 through the communication module 210 after sending the login data to the service server 100. In some embodiments, the login processing module 250 may also send the received verification result to the client 410 that sends the login data corresponding to the verification result.

The login processing module 250 is also responsible for selecting whether to update the login status record according to the received verification result. In more detail, when the login processing module 250 receives the verification result sent by the business server 100, it can determine whether the received verification result indicates that the login data is verified. If the verification received by the login processing module 250 The result indicates that when the corresponding login data is verified, the login processing module 250 can use the identification data of the client 410 that sent the verified login data and the identification data of the business server 100 that sent the verification result as a piece of data and store it in the login In the status record; and if the verification result received by the login processing module 250 indicates that the corresponding login data has not been verified, the login processing module 250 may drop the login data and the verification data. The login status record is usually used to record the business server 100 that the client 410 has logged in, but is not limited to this. In some embodiments, the login status record can record the difference between the client 410 and the business server 100. The login relationship between, for example, logged in, denied login, or not logged in, etc.

The login processing module 250 is also responsible for determining whether the client 410 logs in to the service server 100. For example, when the login processing module 250 receives the login data/report data sent by the client 410 through the communication module 210, it can extract the identification data of the client 410 from the received login data/report data, and determine Whether the retrieved identification data of the client 410 and the identification data of any service server 100 are stored as the same data in the login status record, if yes, it means that the client 410 has passed the verification of at least one service server 100, and the login process The module 250 can determine that the client 410 has logged in to the service server 100; if not, it means that the client 410 has not passed the verification of any service server 100, and the login processing module 250 can determine that the client 410 has not logged in to any service server. 100.

If the login data/reported data received by the login processing module 250 through the communication module 210 also includes service parameters, the login processing module 250 can retrieve the service parameters when extracting the identification data of the client 410. And determine whether the extracted identification data of the client 410 and the identification data of the business server 100 corresponding to the extracted service parameters are stored as the same data in the login status record. If so, it means that the client 410 at least passed the service parameters Corresponding to the verification of the business server 100, the login processing module 250 can determine that the client 410 has logged in the business server 100 corresponding to the service parameter; if not, it means that the client 410 has not passed the verification of the business server 100 corresponding to the service parameter. The login processing module 250 can determine that the client 410 has not logged in to the service server 100 corresponding to the service parameter.

The login processing module 250 is also responsible for generating a logged-in message and sending the generated logged-in message to the client through the communication module 210 when judging that the client 410 has logged in to the business server 100 based on the login data sent by the client 410 The client 410 is responsible for sending the login data to all the service servers 100 or with the login data through the communication module 210 when judging that the client 410 has not logged in to the business server 100 of the purpose based on the login data sent by the client 410 The service parameter corresponds to one or more service servers 100; the login processing module 250 is also responsible for determining that the client 410 has logged in one or more service servers 100 based on the report data sent by the client 410, through the communication module The group 210 sends the report data to the business server 100 that the client 410 has logged in or one or more business servers 100 corresponding to the service parameters in the report data, and is responsible for judging the client based on the report data sent by the client 410 When 410 has not logged in to any service server 100 or the service server 100 corresponding to the service parameter in the report data, a non-login message is generated and the generated non-login message is sent to the client 410 through the communication module 210.

The login processing module 250 can send the login data to all the service servers 100 or one or more service servers 100 corresponding to the service parameters according to the interface information of each service server 100 in the registration data generated by the registration module 220 , Or send the report data to one or more service servers 100 that the client 410 has logged in or one or more service servers 100 corresponding to the service parameters.

The push module 290 can receive notification messages generated by each service server 100 through the communication module 210, and is used to select one or more client servers according to the setting data set by the client servers on the service platform 200, and The notification message can be sent to the selected client server through the communication module 210. Wherein, the aforementioned client server may be a specific business server 100, or may be another server connected to the service platform 200.

Next, the first embodiment is used to explain the operating system and method of the present invention, and please refer to "Figure 3A" for the flow chart of the method for maintaining the log-in status record and transferring data mentioned in the present invention. In this embodiment, it is assumed that the client 410 is a small program in the communication software executed on the computing device 400, but the invention is not limited to this.

First, the registration module 220 of the service platform 200 can provide registration services, so that the business server 100 can register with the service platform 200 (step 301), and the registration module 220 can generate registration data corresponding to the registered business server 100 (step 310). In this embodiment, it is assumed that the business server 100 can MD5 encode the identification data and timestamp twice to generate a signature, and send the identification data, interface information, timestamp, and signature to the service platform 200; service platform After the registration module 220 of the 200 receives the data transmitted by the business server 100 through the communication module 210 of the service platform 200, it can generate registration data corresponding to the business server 100 that transmits the data. Generally speaking, the registration module 220 can also generate an access security mark corresponding to the business server 100 that transmits the data, and can transmit the generated access security mark to the corresponding business server 100 through the communication module 210. .

After the business server 100 registers with the service platform 200, and the service platform 200 generates registration information, the client 410 can provide input login information, and send the input login information to the service platform 200 (step 320). In this embodiment, assuming that the login information is an account password, the client 410 may provide the user of the computing device 400 to input the login information.

After the communication module 210 of the service platform 200 receives the login data transmitted by the client 410, the login processing module 250 of the service platform 200 can forward the login data received by the communication module 210 to all the login data on the service platform 200 Registered business server 100 (step 330). In this embodiment, it is assumed that the login processing module 250 can send the login data to each service server 100 through the communication module 210 based on the interface information of each business server 100 included in the registration data generated by the registration module 220 of the service platform 200 Business server 100.

After the business server 100 receives the login data sent by the service platform 200, the business server 100 can verify the received login data, generate a corresponding verification result, and send the generated verification result to the service platform 200 (Step 340). In this embodiment, the business server 100 can compare whether the received login data is consistent with the stored account password. If so, the business server 100 can generate a verification result indicating that the login data has been verified, and can compare all The generated verification result and the access security mark received during registration are returned to the service platform 200; if not, the business server 100 can generate a verification result indicating that the login data has not been verified, and can send the generated verification result and The access security sign received during registration is transmitted back to the service platform 200.

After the communication module 210 of the service platform 200 receives the verification result sent by the business server 100, the login processing module 250 of the service platform 200 can determine whether the verification result received by the communication module 210 indicates that the login data has been verified. If yes, the login processing module 250 may use the identification data of the client 410 that has transmitted the authenticated login data and the identification data of the business server 100 that has transmitted the verification result as a piece of data and store it in the login status record (step 350). At the same time, the login processing module 250 can also send the received verification result back to the client 410 that sends the login data through the communication module 210. It should be noted that, in this embodiment, the login processing module 250 may first determine whether the access security flag received by the communication module 210 is the same as the access security flag sent to the service server 100 that sent the verification result. If not, the login processing module 250 can discard or not process the verification result received by the communication module 210; if so, the login processing module 250 can update the login status record as described above.

After the client 410 receives the verification result sent by the service platform 200, the client 410 can determine whether the verification result indicates that the login information has been verified. If not, the client 410 can provide the login information again and send the login through the service platform 200 The data is sent to the business server 100 (steps 320, 330), so that the business server 100 verifies the login information again, and returns the verification result through the service platform 200 (step 340), until the verification result indicates that the login data is verified or the client 410 rejects Provided to enter the login information.

After the client 410 determines that the received verification result indicates that the login information has been verified, the client 410 may generate report data, and send the generated report data to the service platform 200 (step 360). In this embodiment, it is assumed that the client 410 can scan the identification barcode on the device to be repaired through the computing device 400, so as to generate report data for repairing the device based on the scanned identification barcode.

After the communication module 210 of the service platform 200 receives the report data sent by the client 410, the login processing module 250 of the service platform 200 can determine whether the client 410 has logged in to any business server 100 (step 371). In this embodiment, it is assumed that the login processing module 250 can extract the identification data of the client 410 from the report data, and compare whether the identification data of the client 410 exists in the maintained login status record, so as to determine whether the client 410 is You have logged in to any business server 100 registered on the service platform 200.

If the identification data of the client 410 does not exist in the login status record, the login processing module 250 of the service platform 200 can generate a non-login message, and send the generated non-login message to the client through the communication module 210 of the service platform 200 410. After receiving the non-login message sent by the service platform 200, the client 410 can repeat the aforementioned login process, that is, the client 410 can provide input login information and send the login information to the business server 100 through the service platform 200 ( Steps 320, 330), the business server 100 verifies the login information and returns a verification result through the service platform 200 (step 340), until the verification result indicates that the login information is verified or the client 410 refuses to provide the input login information.

And if the identification data of the client 410 exists in the login status record, the login processing module 250 of the service platform 200 can transfer the registration data maintained by the registration module 220 of the service platform 200 through the communication module 210 of the service platform 200 The report data is sent to the business server 100 that the client 410 has logged in (step 375), so that the business server 100 can perform corresponding processing on the received report data. In this embodiment, it is assumed that the login processing module 250 can read the identification data of the business server 100 that is stored as the same data as the identification data of the client 410 from the login status record, and based on the read business server The identification data of 100 obtains the interface information of the corresponding business server 100 from the registration data, and sends the report data to the corresponding business server 100 according to the obtained interface information.

Continue to explain the operating system and method of the present invention with the second embodiment, and please continue to refer to "Figure 3A". In this embodiment, it is also assumed that the client 410 is a small program in the communication software executed on the computing device 400, but the invention is not limited to this.

First, the registration module 220 of the service platform 200 can provide that the service server 100 can register with the service platform 200 (step 301), and can generate registration data corresponding to the registered service server 100 after the service server 100 is registered (step 310).

After that, after the client 410 transmits the input login data to the service platform 200 (step 320), the login processing module 250 of the service platform 200 can read the service parameters from the login data received by the communication module 210. And forward the login information to one or more service servers 100 corresponding to the read service parameters (step 330).

After the business server 100 receives the login data sent by the service platform 200, the business server 100 can verify the received login data, generate a corresponding verification result, and send the generated verification result back to the service platform 200 (step 340). In this embodiment, it is assumed that the business server 100 can compare the received login data with the stored account password. If so, the business server 100 can generate a verification result indicating that the login data has been verified, and can compare The generated verification result is transmitted back to the service platform 200; if not, the business server 100 may not generate the verification result, and certainly does not send the verification result to the service platform 200.

After the communication module 210 of the service platform 200 receives the verification result returned by the business server 100, the login processing module 250 of the service platform 200 can transfer the identification data of the client 410 that sends the login data and the business that sends the verification result. The identification data of the server 100 is used as a piece of data and stored in the login status record (step 350). At the same time, the login processing module 250 can also send the received verification result back to the client 410 that sends the login data through the communication module 210. In this embodiment, it is assumed that the login processing module 250 can first determine whether the verification result received by the communication module 210 indicates that the login data has been verified. If so, the login processing module 250 can update the login status record as described above; if not, , The login processing module 250 can discard the verification result.

When the client 410 does not receive the verification result sent by the business server 100 through the service platform 200 within a period of time, the client 410 can determine that the login data has not passed the verification; the client 410 can also receive the verification result sent by the service platform 200 After the verification result, it is judged whether the verification result indicates that the login data is verified. If not, that is, the login data has not been verified, the client 410 can provide the login data again and send the login data to the business server 100 through the service platform 200 ( Steps 320, 330), until the business server 100 returns a verification result indicating that the login information is verified through the service platform 200 (step 340) or the client 410 refuses to provide the input login information.

If the client 410 determines that the received verification result indicates that the login data is verified, the client 410 may generate report data, and send the generated report data to the service platform 200 (step 360). In this embodiment, it is assumed that the user of the client 410 can input related information of the device to be repaired, so that the client 410 generates report data based on the input related information.

After the communication module 210 of the service platform 200 receives the report data sent by the client 410, the login processing module 250 of the service platform 200 can determine whether the client 410 has logged in to the business server corresponding to the service parameter in the report data. 100 (Step 371). In this embodiment, it is assumed that the login processing module 250 can extract the service parameters and the identification data of the client 410 from the report data, and compare whether the maintained login status record contains the identification data of the client 410 and the service The identification data of the business server 100 corresponding to the parameter is used to determine whether the client 410 has logged in one or more business servers 100 corresponding to the service parameter in the report data.

If the login status record does not contain both the identification data of the client 410 and the identification data of the business server 100 corresponding to the service parameters, the login processing module 250 of the service platform 200 can generate a non-login message and use the service The communication module 210 of the platform 200 transmits the generated non-login message to the client 410, and the client 410 can repeat the aforementioned login process after receiving the non-login message sent by the service platform 200.

If the login status record contains both the identification data of the client 410 and the identification data of the business server 100 corresponding to the service parameters, the login processing module 250 of the service platform 200 can be based on the registration module of the service platform 200 The registration data maintained by 220 is sent to the service server 100 where the client 410 has logged in through the communication module 210 of the service platform 200 (step 375), that is, the report data is sent to the service parameters in the report data The corresponding service server 100 enables the service server 100 to perform corresponding processing on the received report data after receiving the report data. In this embodiment, it is assumed that the login processing module 250 can read the identification data of the business server 100 corresponding to the service parameters, and obtain the corresponding business from the registration data according to the read identification data of the business server 100 The interface information of the server 100 and the report data are sent to the corresponding business server 100 based on the obtained interface information.

In this way, it can be seen from the above two embodiments that through the present invention, different clients generated by executing the same program on different computing devices can send report data to the corresponding business server through the service platform, so that each business server can be Different return data received execute different business procedures.

In the above two embodiments, the login processing module 250 of the service platform 200 transmits the report data to the client 410 through the communication module 210 of the service platform 200 according to the registration data maintained by the registration module 220 of the service platform 200. Log in to the business server 100 (step 375). After the business server 100 responds to the received report data, the business server 100 can generate a notification message and send it as shown in the process shown in "Figure 3B". The generated notification message is sent to the service platform 200 (step 380). After the communication module 210 of the service platform 200 receives the notification message sent by the service server 100, the push module 290 of the service platform 200 can use the setting data to The communication module 210 transmits the notification message received by the communication module 210 to the client server (step 390), for example, the dispatch server.

To sum up, it can be seen that the difference between the present invention and the prior art is that after the service platform provides the service server registration, when the client sends the login information, the login information is forwarded to the service server, and according to the service server. The returned verification result updates the login status record, and when the client sends the report data, when the client judges that the client has logged in to the business server based on the login status record, the report data is transferred to the client's logged-in business server based on the registration data. With this technical means, it can solve the problem that the prior art requires a lot of cost to maintain when developing a large number of similar small programs, and then achieve the technical effect of integrating similar small programs.

Furthermore, the method of maintaining log-in status records and transferring data of the present invention can be implemented in hardware, software, or a combination of hardware and software, and can also be implemented in a centralized manner in a computer system or distributed in a number of interconnections with different components. The decentralized way of connecting the computer system is realized.

Although the embodiments of the present invention are disclosed as above, the content described is not intended to directly limit the scope of patent protection of the present invention. Anyone with ordinary knowledge in the technical field to which the present invention belongs, without departing from the spirit and scope of the present invention, makes some modifications in the form and details of the implementation of the present invention, all belong to the patent protection of the present invention range. The scope of patent protection of the present invention shall still be determined by the scope of the attached patent application.

100: business server 200: service platform 210: communication module 220: registration module 250: login processing module 290: push broadcast module 400: computing device 410: client step 301: business server registration step with the service platform 310: The service platform generates registration data corresponding to the business server Step 320: The client sends the login data to the service platform Step 330: The service platform sends the login data to the business server Step 340: The business server verifies the login data and sends the verification result Go to the service platform Step 350: The service platform updates the login status record according to the verification result Step 360: The client sends the report data to the service platform Step 371: The service platform judges whether the client has logged in to the business server according to the login status record Step 375: The service platform registers according to the registration Data transmission report data to the business server that the client has logged in Step 380: The business server generates a notification message and sends the notification message to the service platform Step 390: The service platform sends a notification message to the client server based on the configuration data

Figure 1 is a diagram of the system architecture for maintaining log-in status records to transfer data according to the present invention. Figure 2 is a schematic diagram of the components of the device for maintaining log-in status records to transfer data according to the present invention. Figure 3A is a flow chart of the method for maintaining log-in status records to transfer data according to the present invention. Figure 3B is a flow chart of the method of data push provided by the present invention.

Step 301: The business server registers with the service platform

Step 310: The service platform generates registration data corresponding to the business server

Step 320: The client sends the login information to the service platform

Step 330: The service platform sends the login information to the business server

Step 340: The business server verifies the login information and sends the verification result to the service platform

Step 350: The service platform updates the login status record according to the verification result

Step 360: The client sends the report data to the service platform

Step 371: The service platform determines whether the client has logged in to the business server according to the login status record

Step 375: The service platform sends the report data to the business server that the client has logged in according to the registration data

Claims (10)

A method for maintaining log-in status records to transfer data, the method at least including the following steps: a plurality of business servers register with a service platform, so that the service platform generates registration data corresponding to the business servers; a client provides Enter a login information and send the login information to the service platform; the service platform sends the login information to the business servers; each of the business servers verifies the login information separately, and sends a verification result corresponding to the login information To the service platform; the service platform updates a login status record based on the verification result; the client generates a report data and transmits the report data to the service platform; the service platform determines that the client has logged in according to the login status record In the case of a business server, the report data is sent to the business servers that the client has logged in according to the registration data. For example, the method for maintaining log-in status records to transfer data as described in item 1 of the scope of patent application, wherein the steps for the business servers to register with the service platform are for each business server to send identification data and time stamps to the service. Platform, the service platform generates each access security mark corresponding to each business server, and transmits each access security mark to each corresponding business server. For example, the method for maintaining log-in status records to transfer data as described in item 1 of the scope of patent application, wherein after the steps of registering the service servers with the service platform, the method also includes the service platform regularly checking each service system server The steps of whether the device is normal. For example, the method of maintaining log-in status records to transfer data as described in the first item of the scope of patent application, wherein the method further includes the client after the service platform sends the report data to the business servers where the client has logged in Each of the business servers that have logged in generates a notification message and sends the notification message to the service platform, and the service platform sends the notification message to the client server according to the setting data. For example, the method of maintaining the log-in status record to transfer data as described in item 1 of the scope of patent application, wherein the service platform sends the log-in data to the business servers and the service platform sends the report data to the client. The steps of the business servers further include that the service platform selects at least one business server according to a service parameter included in the report data, and sends the login data or the report data to the selected business server step. A device for maintaining log-in status records to transfer data, providing a plurality of service servers and at least one client connection, the device at least includes: a registration module for providing registration of the service servers, and generating and connecting the services The server corresponds to a piece of registration data; and a login processing module for judging that the at least one client has not logged in to any of the business servers according to a log-in status record, and transmits a piece of the login data sent by the client to at least A business server, and receives a verification result sent by each business server when the login data is verified, so as to update the login status record according to the verification result, and to determine the client according to the login status record When any one of the service servers is logged in, the report data is sent to at least one of the service servers that the client has logged in according to the registration data. For example, the device for maintaining log-in status records to transfer data described in item 6 of the scope of patent application, wherein the registration module is further used to receive identification data and time stamps sent by each service server to complete the operation of each service server Register, and used to generate each access security flag corresponding to each business server, and send each access security flag to each corresponding business server, so that each business server sends the verification result , And send the corresponding one of the access security signs together. For example, the device for maintaining log-in status records to transfer data as described in item 6 of the scope of patent application, wherein the registration module is used to regularly check whether the servers of each business system are normal. For example, the device for maintaining log-in status records to transfer data as described in item 6 of the scope of patent application, wherein the device further includes a push module for receiving a notification message generated by each service server, and used for Set the data to send the notification message to the client server. For example, the device for maintaining log-in status records to transfer data as described in item 6 of the scope of patent application, wherein the log-in processing module is further used to select at least one service server according to one of the log-in data/the return data, And send the login data/the report data to the selected business server.

Images