CN111327573B - Device and method for maintaining log-in state record to transfer data - Google Patents
Device and method for maintaining log-in state record to transfer data Download PDFInfo
- Publication number
- CN111327573B CN111327573B CN201811535246.3A CN201811535246A CN111327573B CN 111327573 B CN111327573 B CN 111327573B CN 201811535246 A CN201811535246 A CN 201811535246A CN 111327573 B CN111327573 B CN 111327573B
- Authority
- CN
- China
- Prior art keywords
- data
- service
- client
- login
- servers
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
- H04L51/04—Real-time or near real-time messaging, e.g. instant messaging [IM]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/1066—Session management
- H04L65/1073—Registration or de-registration
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Hardware Design (AREA)
- Computer Security & Cryptography (AREA)
- Computing Systems (AREA)
- General Engineering & Computer Science (AREA)
- Business, Economics & Management (AREA)
- General Business, Economics & Management (AREA)
- Multimedia (AREA)
- Information Transfer Between Computers (AREA)
Abstract
A device and method for maintaining log-in state record to transfer data, after providing service server registration through service platform, when client end transmits log-in data, the log-in data is transferred to service server, and log-in state record is renewed according to verification result of log-in data returned by service server, and when client end transmits return data, return data is transferred to service server logged in client end according to registration data.
Description
Technical Field
A data transfer device and method, especially a device and method for maintaining log-in status record to transfer data.
Background
Instant Messaging (IM) is a system for communicating over a network that allows two or more people to communicate text messages, documents, voice and video instantly using the network. The services are typically provided as a website, computer software, or mobile application.
In part of the instant messaging program, the user may be provided with various applets (or components) to install. In fact, before the applet can be installed and used in the instant messaging software, a developer needs to pay a management team of the instant messaging software, and the applet needs to be provided to the management team of the instant messaging software for auditing and testing before being on-line after the auditing is passed. That is, it is cumbersome and tedious for the developer to apply for the applet to be installed and used in the instant messenger.
However, in some cases, developers need to develop similar but slightly different applets to the needs of different customers. When the number of such applets is too large, the developer needs to repeat the above processes of payment, review and testing for each different applet when updating the version of the applet, which takes a lot of time and money for the developer.
In summary, it is known that there is a problem in the prior art that a lot of manpower, material resources and financial costs are required to be expended for developing a lot of similar small programs used in instant messaging software for a long time, and therefore, an improved technical means is required to solve the problem.
Disclosure of Invention
In view of the problem of the prior art that a lot of similar small programs need to be developed and a lot of costs are needed for maintenance, the present invention discloses an apparatus and a method for maintaining log-in status records to transfer data, wherein:
the invention discloses a device for maintaining log-in state record to transfer data, which at least comprises: the registration module is used for providing registration of the service server and generating registration data corresponding to the service server; the login processing module is used for transmitting login data transmitted by the client to the service server when the login state record judges that the client does not log in the service server, receiving a verification result transmitted by the service server when the login data passes the verification, and further updating the login state record according to the verification result, and transmitting return data to the service server which is logged in by the client according to the login data when the login state record judges that the client logs in the service server.
The invention discloses a method for maintaining login state record to transfer data, which at least comprises the following steps: the service server registers to the service platform, and the service platform generates registration data corresponding to the service server; the client provides input login data and transmits the login data to the service platform; the service platform transmits login data to the service server; the service server verifies the login data and transmits a verification result corresponding to the login data to the service platform; the service platform updates the login state record according to the verification result; the client generates return data and transmits the return data to the service platform; and when the service platform judges that the client logs in the service server according to the login state record, transmitting return data to the service server which is logged in by the client according to the registration data.
The device and the method disclosed by the invention have the difference from the prior art that after the service server is registered through the service platform, when the client transmits login data, the login data is transferred to the service server, the login state record is updated according to the verification result returned by the service server, and when the client transmits the return data and judges that the client logs in the service server according to the login state record, the return data is transferred to the service server logged in by the client according to the registration data, so that the problems in the prior art are solved, and the technical effect of integrating similar small programs can be achieved.
Drawings
FIG. 1 is a diagram of a system architecture for maintaining log-in status records for transferring data according to the present invention.
FIG. 2 is a schematic diagram of a device for maintaining log-in status records to transfer data according to the present invention.
FIG. 3A is a flowchart of a method for maintaining a log-in status record for transferring data according to the present invention.
Fig. 3B is a flowchart of a data push method according to the present invention.
[ notation ] to show
100. Business server
200. Service platform
210. Communication module
220. Registration module
250. Login processing module
290. Push module
400. Computing device
410. Client terminal
Step 301 a business server registers with a service platform
Detailed Description
The features and embodiments of the present invention will be described in detail with reference to the accompanying drawings and examples, which are sufficient for those skilled in the art to easily understand the technical means applied to solve the technical problems of the present invention and to implement the technical means, thereby achieving the effects achieved by the present invention.
The invention can manage a plurality of clients and a plurality of service servers in a centralized way through the service platform, so that each client can realize different service functions without mutual interference. The client mentioned in the present invention generally refers to a subroutine of an application program executed in a computing device, but the present invention is not limited thereto, and for example, the client may also be an application program in a computing device.
The system operation of the present invention will be described with reference to fig. 1, which is a system architecture diagram of the present invention for maintaining a log-in status record to transfer data, and fig. 2, which is a schematic diagram of the apparatus for maintaining a log-in status record to transfer data. As shown in FIG. 1, the system of the present invention comprises a business server 100, a service platform 200, and a computing device 400 comprising a client 410.
The service server 100 can be connected to the service platform 200 through a wired or wireless network 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 service server 100 is responsible for registering with the service platform 200. Generally, the service server 100 can transmit the identification data and the interface information to the service platform 200, thereby registering with the service platform 200. The identification data transmitted by the service server 100 is enough to represent the transmitted service server 100, and can be formed by randomly arranging any number of characters, letters, numbers and symbols, and the identification data is a unique value; the interface information is connection information of a service interface provided by the service server 100, including but not limited to a network address, a port number, a path, a data format, and the like.
In some embodiments, the traffic server 100 may transmit a timestamp (timestamp) and/or a signature to the service platform 200 in addition to the identification data when registering with the service platform 200. The signature may be a digital signature of the service server 100 or data calculated by a specific algorithm such as MD5, and the invention is not limited thereto.
The service server 100 is also responsible for receiving login data transmitted by the client 410 through the service platform 200 and verifying the received login data. Generally, the business server 100 receives login data through a service interface provided. The login data provided by the present invention is data that can identify the user identity of the client 410, and includes but is not limited to an account password, a fingerprint, and the like.
The service server 100 may also generate a verification result corresponding to the login data (e.g., the login data is verified or not verified) after verifying the login data, and may transmit the generated verification result to the client 410 that issued the corresponding login data through the service platform 200. The service server 100 may transmit the authentication result only when the login data is authenticated.
In some embodiments, the service server 100 may also receive the access security flag transmitted by the service platform 200 after registering with the service platform 200, and may transmit the received access security flag together when transmitting the verification result to the service platform 200. The access security flag is data corresponding to the service server 100, and is usually a unique value, and may be formed by randomly arranging any number of characters, numbers, letters, and symbols.
The service server 100 is also responsible for receiving the reward data transmitted by the client 410 through the service platform 200 and performing relevant service processing on the received reward data. Generally, the service server 100 receives the report data through the provided service interface. The reward data includes data provided by the client 410 to the service server 100 for service processing, and in some embodiments, the reward data may also include login data and/or service parameters corresponding to one or more service servers 100. The service parameter is usually a unique value, and may be formed by randomly arranging any number of characters, letters, symbols, and numbers to represent the corresponding service server 100.
In some embodiments, the service server 100 may also generate a notification message after performing relevant service processing on the received reward data, and transmit the generated notification message to the service platform 200.
The client 410 can be connected to the service platform 200 through a wired or wireless network to receive data or signals transmitted by the service platform 200, transmit data or signals to the service platform 200, and communicate with the service server 100 through the service platform 200.
The client 410 may provide input login data and transmit the input login data to the service server 100 through the service platform 200. The client 410 may also receive a verification result corresponding to the login data transmitted by the service platform 200 through the service server 100.
The client 410 can also receive the logged-in message and the un-logged-in message transmitted by the service platform through the communication module 210, and can provide the input login data when receiving the un-logged-in message. Wherein the logged-in message may indicate that the client 410 has logged into the service server 100, and the logged-in message may indicate that the client 410 has not logged into the service server 100.
The client 410 is responsible for generating the report data and transmitting the generated report data to the service server 100 through the service platform 200. In some embodiments, before transmitting the reward data, the client 410 may determine whether the client 410 is logged into the service server 100 according to the received verification result. If yes, the client 410 may transmit the report data to the service server 100 through the service platform 200; if the client determines that the service server 100 is not logged in, the client 410 may first transmit login data to the service server 100 through the service platform 200, and after receiving a verification result indicating that the login data passes the verification transmitted by the service server 100 through the service platform 200, transmit report data to the service server 100 through the service platform 200.
The service platform 200 is responsible for registering the service server 100 and transmitting the report data generated by the client 410 to the corresponding service server 100. The service platform 200 further includes a communication module 210, a registration module 220, a login processing module 250, and an optional push module 290.
The communication module 210 is responsible for providing the connection between the service server 100 and the client 410 and 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 also receive data or signals transmitted by the service server 100 and/or the client 410.
The registration module 220 is responsible for providing registration of the service server 100 and generating registration data corresponding to the service server 100, thereby completing registration of the service server 100. The registration data generated by the registration module 220 includes interface information transmitted by each service server 100.
In some embodiments, the registration module 220 may generate an access security flag corresponding to the service server 100 that has completed registration after the registration of the service server 100 is completed, and transmit the generated access security flag to the corresponding service server through the communication module 210.
The registration module 220 may also periodically check whether each registered service server 100 is operating normally according to the interface information in the registration data, for example, the registration module 220 may transmit a heartbeat message (heartbeat message) to the service server 100 through the communication module 210 at a predetermined time or at intervals according to the network address, the port number (and the path) of the service interface of the service server 100, and determine whether the service server 100 is operating normally according to whether the communication module 210 receives a response message returned by the service server 100.
The login processing module 250 is responsible for receiving the login data transmitted by the client 410 through the communication module 210 and forwarding the received login data to the service server 100 through the communication module 210. The login processing module 250 may determine whether the login data includes the service parameter, and if the login data includes the service parameter, the login processing module 250 may select to transmit the login data to one or more service servers 100 corresponding to the service parameter; if the login data does not include the service parameter, the login processing module 250 may transmit the login data to all the service servers 100.
The login processing module 250 is also responsible for receiving the verification result corresponding to the login data transmitted by the service server 100 through the communication module 210 after transmitting the login data to the service server 100. In some embodiments, the login processing module 250 may also transmit the received verification result to the client 410 that issued 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. More specifically, the login processing module 250 may determine whether the received verification result indicates that the login data passes the verification when receiving the verification result transmitted by the service server 100, and if the verification result received by the login processing module 250 indicates that the corresponding login data passes the verification, the login processing module 250 may use the identification data of the client 410 transmitting the login data passing the verification and the identification data of the service server 100 transmitting the verification result as one data and store the data in the login status record; if the verification result received by the login processing module 250 indicates that the corresponding login data does not pass the verification, the login processing module 250 may discard (drop) the login data and the verification data. The log-in status record is usually used to record the service server 100 that the client 410 logs in, but not limited thereto, in some embodiments, the log-in status record may record a log-in relationship between the client 410 and the service server 100, for example, the client has logged in, refused to log in, or has not logged in.
The login processing module 250 is also responsible for determining whether the client 410 logs in the service server 100. For example, when the login processing module 250 receives the login data/report data transmitted by the client 410 through the communication module 210, the identification data of the client 410 is extracted from the received login data/report data, and whether the extracted 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 is determined, if yes, the client 410 is verified by at least one service server 100, and the login processing module 250 may determine that the client 410 is logged in the service server 100; if not, it means that the client 410 does not pass the authentication of any service server 100, and the login processing module 250 may determine that the client 410 has not logged in any service server 100.
If the login processing module 250 further includes the service parameter in the login data/report data received by the communication module 210, the login processing module 250 may take out the service parameter together when taking out the identification data of the client 410, and determine whether the taken out identification data of the client 410 and the identification data of the service server 100 corresponding to the taken out service parameter are stored as the same data in the login status record, if so, it indicates that the client 410 passes at least the verification of the service server 100 corresponding to the service parameter, and the login processing module 250 may determine that the client 410 has logged in the service server 100 corresponding to the service parameter; if not, it indicates that the client 410 fails to pass the verification of the service server 100 corresponding to the service parameter, and the login processing module 250 may determine that the client 410 has not logged in the service server 100 corresponding to the service parameter.
The login processing module 250 is also responsible for generating a login message and transmitting the generated login message to the client 410 through the communication module 210 when determining that the client 410 is logged in the service server 100 of the target according to the login data transmitted by the client 410, and for transmitting the login data to all the service servers 100 or one or more service servers 100 corresponding to the service parameters in the login data through the communication module 210 when determining that the client 410 is not logged in the service server 100 of the target according to the login data transmitted by the client 410; the login processing module 250 is also responsible for transmitting the report data to the service server 100 logged in by the client 410 or the one or more service servers 100 corresponding to the service parameters in the report data through the communication module 210 when determining that the client 410 is logged in to the one or more service servers 100 according to the report data transmitted by the client 410, and for generating an un-login message and transmitting the generated un-login message to the client 410 through the communication module 210 when determining that the client 410 is not logged in to any service server 100 or the service server 100 corresponding to the service parameters in the report data according to the report data transmitted by the client 410.
The login processing module 250 may transmit login data to all the service servers 100 or one or more service servers 100 corresponding to the service parameters, or transmit the report data to one or more service servers 100 registered by the client 410 or one or more service servers 100 corresponding to the service parameters according to the interface information of each service server 100 in the login data generated by the login module 220.
The push module 290 can receive the notification message 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 server on the service platform 200, and can transmit the notification message to the selected client server through the communication module 210. The client server may be a specific service server 100, or may be another server connected to the service platform 200.
Next, an operation system and method of the present invention are explained with reference to a first embodiment, and a flowchart of a method for maintaining a log-in status record to forward data is shown in fig. 3A. In the embodiment, the client 410 is assumed to be an applet in the communication software executed on the computing device 400, but the invention is not limited thereto.
First, the registration module 220 of the service platform 200 may provide a registration service so that the service server 100 may register with the service platform 200 (step 301), and the registration module 220 may generate registration data corresponding to the registered service server 100 (step 310). In this embodiment, it is assumed that the service server 100 may perform MD5 encoding on the identification data and the timestamp twice to generate a signature, and transmit the identification data, the interface information, the timestamp, the signature, and other data to the service platform 200; the registration module 220 of the service platform 200 may generate registration data corresponding to the service server 100 transmitting data after receiving the data transmitted by the service server 100 through the communication module 210 of the service platform 200. Generally, the registration module 220 may further generate an access security flag corresponding to the service server 100 for transmitting data, and may transmit the generated access security flag to the corresponding service server 100 through the communication module 210.
After the service server 100 registers with the service platform 200 and the service platform 200 generates the registration data, the client 410 may provide the input login data and transmit the input login data to the service platform 200 (step 320). In this embodiment, the client 410 may provide the user of the computing device 400 with the login data, assuming the login data is an account password.
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 may forward the login data received by the communication module 210 to all the service servers 100 registered on the service platform 200 (step 330). In this embodiment, it is assumed that the login processing module 250 can transmit the login data to each service server 100 through the communication module 210 according to the interface information of each service server 100 included in the registration data generated by the registration module 220 of the service platform 200.
After the service server 100 receives the login data transmitted by the service platform 200, the service server 100 may verify the received login data, generate a corresponding verification result, and may transmit the generated verification result to the service platform 200 (step 340). In this embodiment, the service server 100 may compare whether the received login data matches the stored account password, and if so, the service server 100 may generate an authentication result indicating that the login data passes the authentication, and may transmit the generated authentication result and the access security flag received during the registration back to the service platform 200; if not, the service server 100 may generate a verification result indicating that the login data is not verified, and may transmit the generated verification result and the access security flag received during registration back to the service platform 200.
After the communication module 210 of the service platform 200 receives the verification result transmitted by the service server 100, the login processing module 250 of the service platform 200 may determine whether the verification result received by the communication module 210 indicates that the login data passes the verification, and if so, the login processing module 250 may use the identification data of the client 410 transmitting the login data passing the verification and the identification data of the service server 100 transmitting the verification result as one data and store the data in the login status record (step 350). Meanwhile, the login processing module 250 may also transmit the received verification result back to the client 410 sending the login data through the communication module 210. It should be noted that, in the 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 transmitted to the service server 100 sending the verification result, and if not, the login processing module 250 may discard or not process the verification result received by the communication module 210; if so, the login processing module 250 may restore the login status record as described above.
After the client 410 receives the verification result transmitted by the service platform 200, the client 410 may determine whether the verification result indicates that the login data passes the verification, and if not, the client 410 may provide the input login data again and transmit the login data to the service server 100 through the service platform 200 (steps 320 and 330), so that the service server 100 verifies the login data again and transmits the verification result back through the service platform 200 (step 340) until the verification result indicates that the login data passes the verification or the client 410 refuses to provide the input login data.
After the client 410 determines that the received verification result indicates that the login data passes the verification, the client 410 may generate the report data and transmit 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, and thereby generate the report data for reporting the device to be repaired according to the scanned identification barcode.
After the communication module 210 of the service platform 200 receives the report data transmitted by the client 410, the login processing module 250 of the service platform 200 can determine whether the client 410 is logged into any of the service servers 100 (step 371). In this embodiment, it is assumed that the login processing module 250 can take out 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 has logged in any service server 100 registered on the service platform 200.
If the identification data of the client 410 does not exist in the log-in status record, the log-in processing module 250 of the service platform 200 may generate a non-log-in message and transmit the generated non-log-in message to the client 410 through the communication module 210 of the service platform 200, after receiving the non-log-in message transmitted by the service platform 200, the client 410 may repeat the log-in process, that is, the client 410 may provide the input log-in data and transmit the log-in data to the service server 100 through the service platform 200 (steps 320 and 330), the service server 100 verifies the log-in data and returns the verification result through the service platform 200 (step 340), until the verification result indicates that the log-in data passes the verification or the client 410 refuses to provide the input log-in data.
If the log-in status record includes the identification data of the client 410, the log-in processing module 250 of the service platform 200 can transmit the report data to the service server 100 logged in by 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 (step 375), so that the service 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 service server 100 stored as the same data as the identification data of the client 410 from the login status record, obtain the interface information of the corresponding service server 100 from the registration data according to the read identification data of the service server 100, and transmit the report data to the corresponding service server 100 according to the obtained interface information.
The operation system and method of the present invention are explained with reference to the second embodiment, and please continue to refer to fig. 3A. In the embodiment, it is also assumed that the client 410 is an applet in the communication software executed on the computing device 400, but the invention is not limited thereto.
First, the registration module 220 of the service platform 200 may provide that the service server 100 may register with the service platform 200 (step 301), and may generate registration data corresponding to the registered service server 100 after the service server 100 registers (step 310).
Thereafter, when the client 410 transmits the inputted login data to the service platform 200 (step 320), the login processing module 250 of the service platform 200 may read the service parameters from the login data received by the communication module 210 and forward the login data to the one or more service servers 100 corresponding to the read service parameters (step 330).
After the service server 100 receives the login data transmitted by the service platform 200, the service server 100 may verify the received login data, generate a corresponding verification result, and transmit the generated verification result back to the service platform 200 (step 340). In this embodiment, it is assumed that the service server 100 may compare whether the received login data matches the stored account password, and if yes, the service server 100 may generate an authentication result indicating that the login data passes the authentication, and may send the generated authentication result back to the service platform 200; if not, the service server 100 may not generate the verification result, and certainly not transmit 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 service server 100, the login processing module 250 of the service platform 200 may take the identification data of the client 410 transmitting the login data and the identification data of the service server 100 transmitting the verification result as one data and store the data in the login status record (step 350). Meanwhile, the login processing module 250 may also transmit the received verification result back to the client 410 sending the login data through the communication module 210. In this embodiment, it is assumed that the login processing module 250 may first determine whether the verification result received by the communication module 210 indicates that the login data passes the verification, and if so, the login processing module 250 may update the login status record as described above; if not, the login processing module 250 may discard the verification result.
When the client 410 does not receive the verification result transmitted by the service server 100 through the service platform 200 within a period of time, the client 410 may determine that the login data is not verified; the client 410 may also determine whether the verification result indicates that the login data passes the verification after receiving the verification result transmitted by the service platform 200, and if not, that is, the login data does not pass the verification, the client 410 may provide the input login data again and transmit the login data to the service server 100 through the service platform 200 (steps 320 and 330) until the service server 100 returns the verification result indicating that the login data passes the verification through the service platform 200 (step 340) or the client 410 rejects providing the input login data.
If the client 410 determines that the received verification result indicates that the login data passes the verification, the client 410 may generate the report data and transmit the generated report data to the service platform 200 (step 360). In this embodiment, it is assumed that a user of the client 410 can input related information of the device to be repaired, so that the client 410 generates the report data according to the input related information.
After the communication module 210 of the service platform 200 receives the report data transmitted by the client 410, the login processing module 250 of the service platform 200 can determine whether the client 410 is logged in the service server 100 corresponding to the service parameter in the report data (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 data including the identification data of the client 410 and the identification data of the service servers 100 corresponding to the service parameters, so as to determine whether the client 410 logs in one or more service servers 100 corresponding to the service parameters in the report data.
If the log-in status record does not contain the data including the identification data of the client 410 and the identification data of the service server 100 corresponding to the service parameter, the log-in processing module 250 of the service platform 200 may generate a non-log-in message and transmit the generated non-log-in message to the client 410 through the communication module 210 of the service platform 200, and the client 410 may repeat the log-in process after receiving the non-log-in message transmitted by the service platform 200.
If the log-in status record includes data including both the identification data of the client 410 and the identification data of the service server 100 corresponding to the service parameter, the log-in processing module 250 of the service platform 200 may transmit the report data to the service server 100 logged in by 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 (step 375), that is, transmit the report data to the service server 100 corresponding to the service parameter in the report data, so that the service server 100 may 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 service server 100 corresponding to the service parameter, obtain the interface information of the corresponding service server 100 from the registration data according to the read identification data of the service server 100, and transmit the report data to the corresponding service server 100 according to the obtained interface information.
Thus, it can be seen from the two embodiments that, according to the present invention, different clients that execute the same program on different computing devices can transmit the report data to the corresponding service servers through the service platform, so that each service server can execute different service programs according to the received different report data.
In the above two embodiments, after the login processing module 250 of the service platform 200 transmits the report data to the service server 100 logged in by 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 (step 375), and the service server 100 correspondingly processes the received report data, as shown in the flow of fig. 3B, the service server 100 may generate a notification message and transmit the generated notification message to the service platform 200 (step 380), and after the communication module 210 of the service platform 200 receives the notification message transmitted by the service server 100, the push module 290 of the service platform 200 may transmit the notification message received by the communication module 210 to the client server through the communication module 210 according to the setting data (step 390), for example, a dispatch server, and the like.
In summary, 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 for registration, when the client transmits the login data, the login data is transferred to the service server, and the login status record is updated according to the verification result returned by the service server, and when the client transmits the report data, and when the client determines that the client has logged in the service server according to the login status record, the report data is transferred to the service server that the client has logged in according to the registration data.
Furthermore, the method of maintaining log-in status record for transferring data of the present invention can be realized in hardware, software, or a combination of hardware and software, or realized in a centralized manner in a computer system or realized in a distributed manner with different components distributed among several interconnected computer systems.
Although the embodiments of the present invention have been described above, the description is not intended to limit the scope of the invention. It will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the spirit and scope of the invention as defined by the appended claims. The scope of the present invention should be determined by the following claims.
Claims (10)
1. A method for maintaining a log-in status record for transferring data, the method comprising the steps of:
a plurality of business servers register with a service platform, so that the service platform generates registration data corresponding to the business servers;
the client provides input login data and transmits the login data to the service platform;
the service platform transmits the login data to the plurality of business servers;
the service servers respectively verify the login data and transmit verification results corresponding to the login data to the service platform;
the service platform updates a login state record according to the verification result;
the client generates return data and transmits the return data to the service platform;
when the service platform judges that the client logs in any one of the business servers according to the login state record, the service platform transmits the return data to the business server logged in by the client according to the registration data;
the client generates report data and transmits the report data to the service platform, including:
the service platform transmits a verification result to the client;
the client side judges that the client side logs in the service server according to the verification result, generates return data and transmits the return data to the service platform;
the return data comprises data provided by the client to the service server for service processing, or comprises login data and/or service parameters corresponding to one or more service servers;
the client is an applet in the communication software executed on the computing device.
2. The method of claim 1, wherein the step of registering the service servers with the service platform respectively transmits identification data and a timestamp to the service platform, and the service platform respectively generates access security flags corresponding to the service servers and transmits the access security flags to the corresponding service servers.
3. The method of claim 1, further comprising the step of the service platform periodically checking whether each of the plurality of business servers is normal after the step of registering the business servers with the service platform.
4. The method as claimed in claim 1, wherein after the service platform transmits the report data to the plurality of service servers that the client has logged in, the method further comprises the steps of generating a notification message by each of the service servers that the client has logged in and transmitting the notification message to the service platform, and the service platform transmitting the notification message to a client server according to configuration data.
5. The method as claimed in claim 1, wherein the step of the service platform transmitting the login data to the plurality of service servers and the step of the service platform transmitting the report data to the plurality of service servers that the client has logged in further comprises the steps of the service platform selecting at least one of the service servers according to service parameters included in the report data and transmitting the login data or the report data to the selected service server.
6. An apparatus for maintaining log-in status records for forwarding data, providing a plurality of service servers and at least one client connection, the apparatus comprising:
the registration module is used for providing registration of the plurality of service servers and generating registration data corresponding to the plurality of service servers; and
a login processing module, configured to transmit login data transmitted by the client to at least one service server when determining that the at least one client is not logged in any one of the service servers according to a login status record, receive a verification result transmitted by each service server when the login data passes verification, update the login status record according to the verification result, and transmit return data generated by the client to at least one service server that the client is logged in according to the login status record when determining that the client is logged in any one of the service servers according to the login status record;
the service server transmits a verification result to the client, and the client judges that the client has accessed the service server according to the verification result and then generates return data;
the return data comprises data provided by the client to the service server for service processing, or comprises login data and/or service parameters corresponding to one or more service servers;
the client is an applet in the communication software executed on the computing device.
7. The apparatus for maintaining a log-in status record for forwarding data as claimed in claim 6, wherein the registration module is further configured to receive identification data and a timestamp respectively transmitted by each of the service servers to complete registration of each of the service servers, and to generate each access security flag corresponding to each of the service servers and transmit each of the access security flags to each of the corresponding service servers, so that each of the service servers transmits the corresponding access security flag together when transmitting the verification result.
8. The apparatus for maintaining a log-in status record for forwarding data as claimed in claim 6, wherein said registration module is further configured to periodically check whether each of said service servers is normal.
9. The apparatus as claimed in claim 6, further comprising a push module for receiving the notification message generated by each of the service servers and for sending the notification message to the client server according to the configuration data.
10. The apparatus according to claim 6, wherein the login processing module is further configured to select at least one of the service servers according to a service parameter of the login data/the report data, and transmit the login data/the report data to the selected service server.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811535246.3A CN111327573B (en) | 2018-12-14 | 2018-12-14 | Device and method for maintaining log-in state record to transfer data |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811535246.3A CN111327573B (en) | 2018-12-14 | 2018-12-14 | Device and method for maintaining log-in state record to transfer data |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111327573A CN111327573A (en) | 2020-06-23 |
| CN111327573B true CN111327573B (en) | 2022-12-02 |
Family
ID=71164878
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201811535246.3A Active CN111327573B (en) | 2018-12-14 | 2018-12-14 | Device and method for maintaining log-in state record to transfer data |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111327573B (en) |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101183932A (en) * | 2007-12-03 | 2008-05-21 | 宇龙计算机通信科技(深圳)有限公司 | Security identification system of wireless application service and login and entry method thereof |
| CN101420416A (en) * | 2007-10-22 | 2009-04-29 | 中国移动通信集团公司 | Identity management platform, service server, login system and federation method |
| CN103283209A (en) * | 2011-04-18 | 2013-09-04 | 北京新媒传信科技有限公司 | Application service platform system and implementation method thereof |
| CN104270391A (en) * | 2014-10-24 | 2015-01-07 | 中国建设银行股份有限公司 | Method and device for processing access request |
| TWM549407U (en) * | 2017-05-24 | 2017-09-21 | 許世賓 | Medical information system |
Family Cites Families (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20050015490A1 (en) * | 2003-07-16 | 2005-01-20 | Saare John E. | System and method for single-sign-on access to a resource via a portal server |
| US7324473B2 (en) * | 2003-10-07 | 2008-01-29 | Accenture Global Services Gmbh | Connector gateway |
| TW201105081A (en) * | 2009-07-21 | 2011-02-01 | Inventec Corp | Distributed user authentication system and method thereof |
| CN102724103B (en) * | 2011-03-30 | 2015-04-01 | 国际商业机器公司 | Proxy server, hierarchical network system and distributed workload management method |
| CN103685165A (en) * | 2012-09-06 | 2014-03-26 | 深圳第七大道网络技术有限公司 | Service processing method and service server |
| CN104253686B (en) * | 2013-06-25 | 2017-12-29 | 华为技术有限公司 | Method, equipment and the system that account logs in |
| CN109328348B (en) * | 2016-09-30 | 2023-03-03 | 华为技术有限公司 | Service authentication method, system and related equipment |
| TWI579729B (en) * | 2016-11-11 | 2017-04-21 | 南開科技大學 | Server login authentication system and method thereof |
| CN106411659A (en) * | 2016-11-29 | 2017-02-15 | 福建中金在线信息科技有限公司 | Business data monitoring method and apparatus |
| TW201824887A (en) * | 2016-12-27 | 2018-07-01 | 英業達股份有限公司 | System for using authentication server to implement free login in server group and method thereof |
| CN108521338B (en) * | 2018-03-09 | 2021-04-13 | 厦门集微科技有限公司 | Service processing method of service platform and service platform |
-
2018
- 2018-12-14 CN CN201811535246.3A patent/CN111327573B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101420416A (en) * | 2007-10-22 | 2009-04-29 | 中国移动通信集团公司 | Identity management platform, service server, login system and federation method |
| CN101183932A (en) * | 2007-12-03 | 2008-05-21 | 宇龙计算机通信科技(深圳)有限公司 | Security identification system of wireless application service and login and entry method thereof |
| CN103283209A (en) * | 2011-04-18 | 2013-09-04 | 北京新媒传信科技有限公司 | Application service platform system and implementation method thereof |
| CN104270391A (en) * | 2014-10-24 | 2015-01-07 | 中国建设银行股份有限公司 | Method and device for processing access request |
| TWM549407U (en) * | 2017-05-24 | 2017-09-21 | 許世賓 | Medical information system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111327573A (en) | 2020-06-23 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN104660557B (en) | operation processing method and device | |
| CN112527912B (en) | Data processing method and device based on block chain network and computer equipment | |
| CN106296144A (en) | Payment processes server, client and payment processing method | |
| KR20180113229A (en) | Loan service providing method using black chain and system performing the same | |
| CN104767613A (en) | Signature verification method, device and system | |
| US12113930B2 (en) | Decentralized automatic phone fraud risk management | |
| CN111241196B (en) | Advertisement frequency control method and system | |
| CN101495954A (en) | Computer status monitoring and support | |
| CN111460404A (en) | Double-recording data processing method and device, computer equipment and storage medium | |
| WO2021232590A1 (en) | User verification method and apparatus based on private chain, and computer device and storage medium | |
| CN112613877B (en) | Intelligent contract triggering method and device applied to block chain network and related equipment | |
| CN107682376B (en) | Wind control data interaction method and device | |
| CN113179282A (en) | Method and device for merging account numbers and server | |
| CN101151874A (en) | Network node and method for providing internet services on internet marketplaces | |
| US20160112369A1 (en) | System and Method for Validating a Customer Phone Number | |
| CN110941840B (en) | Data processing method, system and terminal | |
| CN108924159A (en) | The verification method and device in a kind of message characteristic identification library | |
| CN108322466A (en) | Verification method, server and the readable storage medium storing program for executing of APK based on Android | |
| CN111327573B (en) | Device and method for maintaining log-in state record to transfer data | |
| CN111050326B (en) | Block chain-based short message verification method, device, equipment and medium | |
| CN113765674A (en) | Cross-platform registration method and device based on block chain | |
| CN113379577A (en) | Transaction auditing method, device and equipment | |
| TWI683556B (en) | System for maintaining login record to transfer data and method thereof | |
| CN114677138B (en) | Data processing method, device and computer readable storage medium | |
| CA3222116A1 (en) | Sftp batch processing and credentials api for offline fraud assessment |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |