CN115174665A

CN115174665A - Login state determination method, device, equipment and storage medium

Info

Publication number: CN115174665A
Application number: CN202210769154.1A
Authority: CN
Inventors: 刘林
Original assignee: Beijing Dajia Internet Information Technology Co Ltd
Current assignee: Beijing Dajia Internet Information Technology Co Ltd
Priority date: 2022-07-01
Filing date: 2022-07-01
Publication date: 2022-10-11
Anticipated expiration: 2042-07-01
Also published as: CN115174665B

Abstract

The disclosure relates to a login state determination method, a login state determination device, login state determination equipment and a login state determination storage medium, and relates to the technical field of the Internet. The method comprises the following steps: receiving an asynchronous verification request sent by gateway equipment; when the first server stores a service identifier of a target service and a service identifier of a first service, calling the first service, wherein the first service is used for indicating the gateway equipment to acquire at least one hash value corresponding to an account identifier of a target account from a second server; receiving the at least one hash value sent by the gateway device; and determining that the login state of the target account is normal under the condition that the target hash value is included in the at least one hash value. According to the method and the device, the first server can accurately and effectively determine the login state of the target account.

Description

Login state determination method, device, equipment and storage medium

Technical Field

The present disclosure relates to the field of internet technologies, and in particular, to a method, an apparatus, a device, and a storage medium for determining a login status.

Background

Currently, a user may send a request to a certain service server through a terminal to obtain service data provided by the service server. Before the request is sent to the service server, the gateway device needs to pass through the gateway device, and the gateway device may intercept the request, so as to check the login state of the user, for example, determine whether the login state of the user is normal by using a remote invocation manner, and forward the request to the service server if the login state is normal.

However, the above-mentioned manner of remote invocation increases the verification duration of the login state of the user, thereby reducing the determination efficiency of the login state.

Disclosure of Invention

The invention provides a login state determination method, a login state determination device, equipment and a storage medium, and solves the technical problem that the verification time of a user login state is prolonged by adopting a remote calling mode in the related art, so that the login state determination efficiency is reduced.

The technical scheme of the embodiment of the disclosure is as follows:

according to a first aspect of an embodiment of the present disclosure, a method for determining a login status is provided. The method can comprise the following steps: receiving an asynchronous verification request sent by gateway equipment, wherein the asynchronous verification request comprises a service identifier of a target service, an account identifier of a target account and a target hash value, and the account identifier and the target hash value are respectively an account identifier and a hash value obtained by analyzing an authorization token sent by the gateway equipment by the first server; the method comprises the steps that under the condition that a service identifier and a service identifier of a first service are stored in a first server, the first service is called, the first service is a service provided by gateway equipment, and the first service is used for indicating the gateway equipment to acquire at least one hash value corresponding to an account identifier from a second server; receiving the at least one hash value sent by the gateway device; and under the condition that the target hash value is included in the at least one hash value, determining that the login state of the target account is normal.

Optionally, the method for determining the login status further includes: in the case that the service identifier is stored in the first server and the service identifier of the first service is not stored, invoking a second service, where the second service is a service provided by a third server, and the second service is used to instruct the third server to determine whether the target hash value exists in the at least one hash value; and receiving a login state notification message sent by the third server, wherein the login state notification message is used for notifying that the login state of the target account is normal, and the login state notification message is sent by the third server under the condition that the target hash value exists in the at least one hash value.

Optionally, the asynchronous verification request further includes a target login time, where the target login time is login time obtained by analyzing the authorization token by the first server, and the login state determining method further includes: determining whether the target login time is after a preset login time under the condition that the service identifier and the service identifier of the first service are not stored in the first server; and determining that the login state of the target account is normal under the condition that the target login time is after the preset login time.

Optionally, before receiving the asynchronous verification request sent by the gateway device, the login status determining method further includes: receiving a synchronous verification request sent by the gateway device, wherein the synchronous verification request comprises the authorization token and is used for requesting to acquire account information of the target account; analyzing the authorization token to obtain the account identifier, the target hash value and target login time; and sending a synchronization check response to the gateway device, wherein the synchronization check response comprises the account identifier, the target hash value and the target login time.

According to a second aspect of an embodiment of the present disclosure, a login status determination method is provided. The method can comprise the following steps: sending a data acquisition request to a second server in response to a service calling indication sent by a first server, wherein the service calling indication comprises a service identifier of a first service, the first service is a service provided by the gateway device, the data acquisition request comprises an account identifier of a target account, the data acquisition request is used for requesting to acquire at least one hash value corresponding to the account identifier, and the service calling indication is sent by the first server under the condition that the service identifier of the target service and the service identifier of the first service are determined to be stored in the first server; receiving a data acquisition response sent by the second server, wherein the data acquisition response comprises the at least one hash value; and sending the at least one hash value to the first server, so that the first server determines that the login state of the target account is normal under the condition that the target hash value is included in the at least one hash value.

Optionally, before the sending the data obtaining request to the second server, the login status determining method further includes: sending a synchronous verification request to the first server, wherein the synchronous verification request comprises an authorization token and is used for requesting to acquire account information of the target account; and receiving a synchronization check response sent by the first server, wherein the synchronization check response comprises the account identification, the target hash value and the target login time.

Optionally, before the sending the data obtaining request to the second server, the login status determining method further includes: and sending an asynchronous verification request to the first server, wherein the asynchronous verification request comprises a service identifier of the target service, an account identifier of the target account and the target hash value, and the account identifier and the target hash value are respectively an account identifier and a hash value obtained by analyzing and processing the authorization token sent by the gateway device by the first server.

According to a third aspect of the embodiments of the present disclosure, there is provided a login status determination apparatus. The apparatus may include: the device comprises a receiving module, a processing module and a determining module; the receiving module is configured to receive an asynchronous verification request sent by a gateway device, where the asynchronous verification request includes a service identifier of a target service, an account identifier of a target account, and a target hash value, and the account identifier and the target hash value are an account identifier and a hash value obtained by analyzing, by the first server, an authorization token sent by the gateway device; the processing module is configured to, in a case that the service identifier and a service identifier of a first service are stored in the first server, invoke the first service, where the first service is a service provided by the gateway device, and the first service is used to instruct the gateway device to obtain at least one hash value corresponding to the account identifier from a second server; the receiving module is further configured to receive the at least one hash value sent by the gateway device; the determining module is configured to determine that the login status of the target account is normal if the target hash value is included in the at least one hash value.

Optionally, the processing module is further configured to, in a case that the service identifier is stored in the first server and the service identifier of the first service is not stored, invoke a second service, where the second service is a service provided by a third server, and the second service is used to instruct the third server to determine whether the target hash value exists in the at least one hash value; the receiving module is further configured to receive a login status notification message sent by the third server, where the login status notification message is used to notify that the login status of the target account is normal, and the login status notification message is sent by the third server when it is determined that the target hash value exists in the at least one hash value.

Optionally, the asynchronous verification request further includes a target login time, where the target login time is login time obtained by analyzing the authorization token by the first server; the determining module is further configured to determine whether the target login time is after a preset login time in a case that the service identifier and the service identifier of the first service are not stored in the first server; the determining module is further configured to determine that the login status of the target account is normal if the target login time is after the preset login time.

Optionally, the login status determining apparatus further includes a sending module; the receiving module is further configured to receive a synchronization check request sent by the gateway device, where the synchronization check request includes the authorization token, and the synchronization check request is used to request to acquire account information of the target account; the processing module is further configured to analyze the authorization token to obtain the account identifier, the target hash value and the target login time; the sending module is configured to send a synchronization check response to the gateway device, where the synchronization check response includes the account identifier, the target hash value, and the target login time.

According to a fourth aspect of the embodiments of the present disclosure, there is provided a login status determination apparatus. The apparatus may include: a transmitting module and a receiving module; the sending module is configured to send a data obtaining request to a second server in response to a service calling indication sent by a first server, wherein the service calling indication includes a service identifier of a first service, the first service is a service provided by a gateway device, the data obtaining request includes an account identifier of a target account, the data obtaining request is used for requesting to obtain at least one hash value corresponding to the account identifier, and the service calling indication is sent by the first server under the condition that the first server is determined to store a service identifier of a target service and the service identifier of the first service; the receiving module is configured to receive a data acquisition response sent by the second server, wherein the data acquisition response comprises the at least one hash value; the sending module is further configured to send the at least one hash value to the first server, so that in a case that a target hash value is included in the at least one hash value, the first server determines that the login state of the target account is normal.

Optionally, the sending module is further configured to send a synchronization check request to the first server, where the synchronization check request includes an authorization token, and the synchronization check request is used to request to acquire account information of the target account; the receiving module is further configured to receive a synchronization check response sent by the first server, where the synchronization check response includes the account identifier, a target hash value, and a target login time.

Optionally, the sending module is further configured to send an asynchronous verification request to the first server, where the asynchronous verification request includes a service identifier of the target service, an account identifier of the target account, and the target hash value, and the account identifier and the target hash value are an account identifier and a hash value obtained by analyzing, by the first server, the authorization token sent by the gateway device.

According to a fifth aspect of embodiments of the present disclosure, there is provided a server, which may include: a processor and a memory configured to store processor-executable instructions; wherein the processor is configured to execute the instructions to implement any one of the above-described first aspect optionally login status determination methods.

According to a sixth aspect of the embodiments of the present disclosure, there is provided a gateway device, which may include: a processor and a memory configured to store processor-executable instructions; wherein the processor is configured to execute the instructions to implement any one of the above-described second aspect optionally login status determination methods.

According to a seventh aspect of embodiments of the present disclosure, there is provided a computer-readable storage medium having instructions stored thereon, which, when executed by a processor of a device, enable the device to perform any one of the above-described first aspect optional login status determination methods, or perform any one of the above-described second aspect optional login status determination methods.

According to an eighth aspect of embodiments of the present disclosure, there is provided a computer program product comprising computer instructions which, when run on a processor of a device, cause the device to perform any one of the optionally logged-in status determination methods as in the first aspect, or to perform any one of the optionally logged-in status determination methods as in the second aspect.

The technical scheme provided by the embodiment of the disclosure at least brings the following beneficial effects:

based on any one of the above aspects, in the present disclosure, the first server may receive an asynchronous verification request sent by the gateway device, that is, request to determine whether the login status of the target account is normal; under the condition that the service identifier of the target service and the service identifier of the first service are stored in the first server, it is indicated that the target service is a preset service in the first server and the first service is successfully set in the gateway device, and at this time, the first server can call the first service, that is, the gateway device is instructed to acquire at least one hash value corresponding to the account identifier of the target account from the second server; the first server may then receive the at least one hash value sent by the gateway device; in a case that the target hash value is included in the at least one hash value, it indicates that the device currently logged in by the target account is one of the at least one device logged in by the target account, so that the first server may determine that the login state of the target account is normal. In this disclosure, under the condition that the service identifier of the target service and the service identifier of the first service are stored in the first server, the first server may determine to invoke the first service (i.e., a local service provided by the gateway device), specifically, instruct the gateway device to determine and obtain at least one hash value corresponding to the service identifier of the target service from the second server, and further determine whether the login state of the target account is normal based on the at least one hash value, so that the verification duration of the login state of the user can be reduced, and the determination efficiency of the login state is improved.

It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure.

Drawings

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present disclosure and, together with the description, serve to explain the principles of the disclosure and are not to be construed as limiting the disclosure.

Fig. 1 is a schematic diagram illustrating a login status determination system provided by an embodiment of the present disclosure;

fig. 2 is a schematic flowchart illustrating a login status determination method according to an embodiment of the present disclosure;

fig. 3 is a schematic flowchart illustrating a further login status determination method provided by an embodiment of the present disclosure;

fig. 4 is a flowchart illustrating a further login status determination method provided by the embodiment of the present disclosure;

fig. 5 is a flowchart illustrating a further login status determination method provided by the embodiment of the present disclosure;

fig. 6 is a flowchart illustrating a further login status determination method provided by the embodiment of the present disclosure;

fig. 7 is a flowchart illustrating a further login status determination method according to an embodiment of the present disclosure;

fig. 8 is a flowchart illustrating a further login status determination method provided by the embodiment of the present disclosure;

fig. 9 is a flowchart illustrating a further login status determination method provided by the embodiment of the present disclosure;

fig. 10 is a schematic structural diagram illustrating a login status determination apparatus according to an embodiment of the present disclosure;

fig. 11 is a schematic structural diagram of another login status determination apparatus provided in an embodiment of the present disclosure;

fig. 12 is a schematic structural diagram of another login status determination apparatus provided in the embodiment of the present disclosure;

fig. 13 shows a schematic structural diagram of still another login status determination apparatus according to an embodiment of the present disclosure.

Detailed Description

In order to make the technical solutions of the present disclosure better understood, the technical solutions in the embodiments of the present disclosure will be clearly and completely described below with reference to the accompanying drawings.

It should be noted that the terms "first," "second," and the like in the description and claims of the present disclosure and in the above-described drawings are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used is interchangeable under appropriate circumstances such that the embodiments of the disclosure described herein are capable of operation in other sequences than those illustrated or described herein. The implementations described in the exemplary embodiments below do not represent all implementations consistent with the present disclosure. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present disclosure, as detailed in the appended claims.

It will be further understood that the terms "comprises" and/or "comprising," when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.

It should be noted that, the user information (including but not limited to user device information, user personal information, user behavior information, etc.) and data (including but not limited to service identification, account identification, hash value, etc.) referred to in this disclosure are information and data that are authorized by the user or sufficiently authorized by each party.

In the related art, the verification duration of the login state of the user is increased by adopting a remote calling mode to determine whether the login state of the user is normal, so that the accuracy efficiency of the login state is reduced. Based on this, in a case that the service identifier of the target service and the service identifier of the first service are stored in the first server, the first server may determine to invoke the first service (i.e., the local service provided by the gateway device), specifically, instruct the gateway device to determine and obtain at least one hash value corresponding to the service identifier of the target service from the second server, and further determine whether the login state of the target account is normal based on the at least one hash value, so that the time length for checking the login state of the user can be reduced, and the efficiency for determining the login state can be improved.

The login state determining method, device, equipment and storage medium provided by the embodiment of the disclosure are applied to an application scenario in which a terminal acquires service data (specifically, a scenario in which a login state of a user account using the terminal is checked in a process in which the terminal acquires the service data). When the first server receives the asynchronous verification request sent by the gateway device, whether the login state of the target account is normal or not can be determined according to the method provided by the embodiment of the disclosure.

The following describes an exemplary login status determination method provided in the embodiments of the present disclosure with reference to the accompanying drawings:

fig. 1 is a schematic diagram of a login state determination system according to an embodiment of the present disclosure, as shown in fig. 1, the login state determination system may include a terminal 101, a gateway device 102, a server 103, a server 104, a server 105, and a server 106. In general, in practical applications, the above-mentioned devices may be connected through a wired network or a wireless network, and for convenience, the connection relationship between the devices is shown intuitively, which is illustrated by a solid line in fig. 1.

The terminal 101 may be a mobile phone, a tablet computer, a desktop, a laptop, a handheld computer, a notebook, an ultra-mobile personal computer (UMPC), a netbook, a cellular phone, a Personal Digital Assistant (PDA), an Augmented Reality (AR), a Virtual Reality (VR) device, and the disclosure does not limit the specific form of the terminal 101. The system can be used for man-machine interaction with a user through one or more modes of a keyboard, a touch pad, a touch screen, a remote controller, voice interaction or handwriting equipment and the like.

The servers (including the server 103, the server 104, the server 105, and the server 106) may be independent physical servers, may be a server cluster or a distributed system formed by a plurality of physical servers, and may be cloud servers providing basic cloud computing services such as a cloud service, a cloud database, cloud computing, a cloud function, cloud storage, a network service, cloud communication, a middleware service, a domain name service, a security service, a network acceleration service (CDN), and a big data and artificial intelligence platform.

Specifically, the terminal 101 may send a service data obtaining request to the gateway 102, so that the gateway 102 may send the service data obtaining request to the server 103, and the terminal 101 may further obtain the service data of the target service from the server 103.

Gateway device 102 may send an asynchronous verification request to server 104 and may also send a data acquisition request to server 105 requesting acquisition of at least one hash value corresponding to the account identification of the target account.

The server 104 may determine whether the service identifier of the target service and the service identifier of the first service are stored in the server 103, and determine whether to invoke the first service, i.e., the service provided by the gateway device 102.

The server 105 may store a plurality of hash values, and the gateway device 102 may determine and retrieve the at least one hash value from the server 105.

The server 106 may determine whether a target hash value exists in the at least one hash value.

As shown in fig. 2, when the login state determination method is applied to the server 104 described above, the login state determination method may include S101-S104.

S101, the first server receives an asynchronous verification request sent by the gateway equipment.

The asynchronous verification request comprises a service identifier of a target service, an account identifier of a target account and a target hash value, wherein the account identifier and the target hash value are respectively an account identifier and a hash value obtained by analyzing and processing an authorization token sent by the gateway device by the first server.

It should be appreciated that the asynchronous verification request is used to request a determination of whether the login status of the target account is normal.

In the embodiment of the present disclosure, a user corresponding to the target account may send a service data acquisition request to a service server (for example, the server 103 in fig. 1) through a terminal, so as to request to acquire service data of the target service. In the process that the terminal sends the service data acquisition request to the service server, the service data acquisition request will reach the gateway device first (the gateway device is located between the terminal and the service server, and has a connection relationship with the terminal and the service server, respectively), and the gateway device will intercept the service data acquisition request. When the first server determines that the login state of the target account is normal, the gateway device may send the service data acquisition request to the service server; when the first server determines that the login state of the target account is abnormal, the gateway device deletes the service data acquisition request and continues to intercept other service data acquisition requests sent by the terminal.

It can be understood that, since the service data obtaining request includes the service identifier of the target service, the gateway device may obtain the service identifier of the target service. In addition, after receiving an authorization token (token) sent by a first server, the gateway device may perform parsing on the authorization token to obtain an account identifier and a target hash value of the target account, and further send the account identifier and the target hash value to the first server, so that the first server may obtain the account identifier and the target hash value.

S102, under the condition that the service identification of the target service and the service identification of the first service are stored in the first server, the first server calls the first service.

The first service is a service provided by the gateway device, and the first service is used for instructing the gateway device to acquire at least one hash value corresponding to the account identifier of the target account from a second server.

It should be appreciated that a plurality of service identities may be stored in the first server. After the first server receives the asynchronous check request sent by the gateway device, the first server may determine whether the service identifier of the target service exists in the plurality of service identifiers, and further determine whether the service identifier of the target service is stored in the first server.

In addition, the gateway device may set the first service locally, specifically, may call a code in the first server to implement a function of the first service in the gateway device. When the first service is successfully set in the gateway device, the gateway device may send a service identifier of the first service to the first server, and the first server may receive and store the service identifier of the first service; accordingly, when the first service is not set (or not successfully set) in the gateway device, the first server may not be able to receive and store the service identifier of the first service.

Optionally, the first service may be a local service provided by the gateway device.

It can be understood that, in the case that the service identifier of the target service is stored in the first server, the target service is described as a preset service (for example, a service provided by an application) in the first server; and when the service identifier of the first service is stored in the first server, the first service is successfully set in the gateway device.

In an implementation manner of the embodiment of the present disclosure, the first server calls the first service, specifically, the first server sends a service call instruction to the gateway device, where the service call instruction is used to instruct the gateway device to acquire, from the second server, at least one hash value corresponding to the account identifier of the target account.

It will be appreciated that a plurality of hash values may be stored in the second server. After the first server invokes the first service, the gateway device may send a data acquisition request to the second server, the data acquisition request including the account identification of the target account. The second server, upon receiving the data acquisition request, may determine at least one hash value from the plurality of hash values that corresponds to the account identification of the target account based on the account identification of the target account and return the at least one hash value to the gateway device.

It should be noted that each of the at least one hash value may correspond to a device (or a terminal). Specifically, the device corresponding to each hash value is a device that has logged in the target account.

S103, the first server receives at least one hash value sent by the gateway equipment.

In connection with the above description of the embodiments, it should be understood that the at least one hash value is a hash value corresponding to an account identification of the target account. The gateway device may send the at least one hash value to the first server after receiving the at least one hash value.

And S104, under the condition that the at least one hash value comprises the target hash value, the first server determines that the login state of the target account is normal.

It will be appreciated that the first server may determine whether the target hash value is included in the at least one hash value. In a case that the at least one hash value includes the target hash value, it indicates that the device (or terminal) currently logged in by the target account is one of the at least one device logged in by the target account, so that the first server may determine that the login state of the target account is normal.

Optionally, in a case that the target hash value is not included in the at least one hash value, the first server may determine that a device currently logged in by the target account is not one of the at least one device logged in by the target account, so that the first server determines that the login status of the target account is abnormal.

The technical scheme provided by the embodiment can at least bring the following beneficial effects: as known from S101 to S104, the first server may receive an asynchronous verification request sent by the gateway device, that is, request to determine whether the login status of the target account is normal; under the condition that the service identifier of the target service and the service identifier of the first service are stored in the first server, it is indicated that the target service is a preset service in the first server and the first service is successfully set in the gateway device, and at this time, the first server can call the first service, that is, the gateway device is instructed to acquire at least one hash value corresponding to the account identifier of the target account from the second server; the first server may then receive the at least one hash value sent by the gateway device; in the case that the target hash value is included in the at least one hash value, it indicates that the device currently logged in by the target account is one of the at least one device logged in by the target account, so that the first server may determine that the login status of the target account is normal. In the embodiment of the disclosure, under the condition that the service identifier of the target service and the service identifier of the first service are stored in the first server, the first server may determine to invoke the first service (that is, the local service provided by the gateway device), specifically, instruct the gateway device to determine and obtain at least one hash value corresponding to the service identifier of the target service from the second server, and further determine whether the login state of the target account is normal based on the at least one hash value, so that the verification duration of the login state of the user can be reduced, and the determination efficiency of the login state is improved.

With reference to fig. 2, as shown in fig. 3, the login status determining method provided by the embodiment of the present disclosure further includes S105-S106.

S105, under the condition that the service identifier of the target service is stored in the first server and the service identifier of the first service is not stored, the first server calls the second service.

The second service is a service provided by a third server, and the second service is used for instructing the third server to determine whether a target hash value exists in the at least one hash value.

With reference to the description of the foregoing embodiment, it should be understood that, in a case that the service identifier of the target service is stored in the first server, the target service is a preset service in the first server; in the case where the service identifier of the first server is not stored in the first server, it indicates that the first service is not set (or not successfully set) in the gateway device. At this time, the first server may call the second service so that the third server may determine whether the target hash value exists in the at least one hash value.

Specifically, the first server invoking the second service may be understood as the first server sending a service invocation request to the third server, where the service invocation request is used to request to determine whether the target hash value exists in the at least one hash value. After receiving the service invocation request, the third server may send a data obtaining request to the second server, where the data obtaining request includes the account identifier of the target account, and the data obtaining request is used to request to obtain at least one hash value corresponding to the account identifier. The third server may determine whether the target hash value exists in the at least one hash value after receiving the at least one hash value sent by the second server.

It should be noted that the explanation for determining whether the target hash value exists in the at least one hash value by the third server is the same as or similar to the process for determining whether the target hash value is included in the at least one hash value by the first server, and details are not repeated here.

Optionally, the second service may be a remote service provided by the third server, such as a Remote Procedure Call (RPC) service.

S106, the first server receives the login state notification message sent by the third server.

The login state notification message is used for notifying that the login state of the target account is normal, and the login state notification message is sent by the third server under the condition that the target hash value exists in the at least one hash value.

It should be understood that when the third server determines that the target hash value exists in the at least one hash value, it indicates that the device currently logged in by the target account is one of the at least one device logged in by the target account, so that the third server may determine that the login status of the target account is normal, and send the login status notification message to the first server, so that the first server may determine that the login status of the target account is normal.

In an optional implementation manner, when the third server determines that the target hash value does not exist in the at least one hash value, it indicates that the device currently logged in by the target account is not one of the at least one device logged in by the target account, at this time, the third server may determine that the login status of the target account is abnormal, and may send a notification message for notifying that the login status of the target account is abnormal to the first server. In turn, the first server may receive the notification message and determine that the login status of the target account is abnormal.

For example, in this embodiment of the present disclosure, the first server may be a server corresponding to an account Software Development Kit (SDK), the second server may be a server corresponding to a data SDK, and the third server may be a server corresponding to an RPC service.

The technical scheme provided by the embodiment can at least bring the following beneficial effects: as can be seen from S105 to S106, in the case that the service identifier of the target service is stored in the first server and the service identifier of the first service is not stored, it indicates that the target service is a preset service in the first server, and the first server is not set (or is not successfully set) in the gateway device, at this time, the first server may invoke the second service, that is, instruct the third server to determine whether the target hash value exists in at least one hash value corresponding to the service identifier. Specifically, the first server may send the target hash value to a third server, and the third server may obtain the at least one hash value from the second server and then determine whether the target hash value exists in the at least one hash value. When the target hash value exists in the at least one hash value, the third server may send a login state notification message to the first server, where the login state notification message is used to notify that the login state of the target account is normal. That is, the first server may determine that the login status of the target account is normal after receiving the login status notification message. In the embodiment of the present disclosure, in a case that the first server stores the identifier of the target service, but does not store the service identifier of the first service, the first server may determine to invoke the second service (i.e., the remote service provided by the third server), so that the third server determines whether the target hash value exists in at least one hash value corresponding to the service identifier of the target service, and receives the login state notification message sent by the third server, that is, notifies that the login state of the target account is normal, so that the login state of the target account can be accurately and effectively determined.

With reference to fig. 2, as shown in fig. 4, the asynchronous check request further includes a target login time, where the target login time is a login time obtained by analyzing the authorization token by the first server, and the login state determining method provided in the embodiment of the present disclosure may further include S107 to S108.

S107, under the condition that the service identifier of the target service and the service identifier of the first service are not stored in the first server, the first server determines whether the target login time is after the preset login time.

It should be understood that, when the first server performs parsing processing on the authorization token, not only the account identifier of the target account and the target hash value may be obtained, but also the target login time may be obtained.

It is to be understood that, in a case that the service identifier of the target service and the service identifier of the first service are not stored in the first server, it indicates that the target service is not a preset service in the first server, and the first service is not set (or is not successfully set) in the gateway device, at this time, the first server may determine whether the target login time is after the preset login time.

In an implementation manner of the embodiment of the present disclosure, the first server may obtain the preset login time from a preset database (e.g., redis), and further determine whether the target login time is after the preset login time.

And S108, under the condition that the target login time is after the preset login time, the first server determines that the login state of the target account is normal.

It should be understood that, in the case that the target login time is after the preset login time, the target login time is valid, and the first server determines that the login status of the target account is normal.

Optionally, in a case that the target login time is before the preset login time, it is indicated that the target login time is invalid, and at this time, the first server may determine that the login status of the target account is abnormal.

The technical scheme provided by the embodiment can at least bring the following beneficial effects: from S107 to S108, in a case that the service identifier of the target service and the service identifier of the first service are not stored in the first server, it is indicated that the target service is not a preset service in the first server, and the first server is not set (or is not successfully set) in the gateway device, at this time, the first server may determine whether the target login time is after the preset login time; in the case that the target login time is after the preset login time, it is indicated that the target login time is valid, and at this time, the first server may determine that the login state of the target account is normal. In the embodiment of the disclosure, the first server may determine whether the target login time is valid based on the time sequence of the target login time and the preset login time, so as to determine whether the login state of the target account is normal. The determination efficiency of the login state can be improved.

With reference to fig. 2, as shown in fig. 5, before the receiving of the asynchronous check request sent by the gateway device, the login status determining method provided in the embodiment of the present disclosure may further include S109-S111.

S109, the first server receives the synchronous verification request sent by the gateway equipment.

The synchronous verification request comprises the authorization token, and is used for requesting to acquire account information of the target account.

It should be understood that, after intercepting the service data acquisition request sent by the terminal to the service server, the gateway device may send the synchronization check request to the first server.

S110, the first server analyzes the authorization token to obtain the account identification of the target account, the target hash value and the target login time.

In this embodiment of the present disclosure, an authorization token may be understood as an encrypted string, and the first server performs parsing on the encrypted string, so as to obtain the account identifier of the target account, the target hash value, and the target login time. It is understood that the account information of the target account includes the account identification, the target hash value, and the target login time.

S111, the first server sends a synchronization check response to the gateway equipment.

And the synchronous verification response comprises the account identification of the target account, the target hash value and the target login time.

It should be appreciated that the first server sends the synchronization check response to the gateway device so that the gateway device can obtain the account identification, the target hash value, and the target login time.

The technical scheme provided by the embodiment can at least bring the following beneficial effects: as known from S109-S111, the first server may receive a synchronization check request sent by the gateway device, where the synchronization check request includes the authorization token; the first server may then perform parsing processing on the authorization token to obtain an account identifier of the target account, a target hash value, and a target login time, and send a synchronization check response to the gateway device, where the synchronization check response includes the account identifier, the target hash value, and the target login time. In the embodiment of the disclosure, the first server may analyze the authorization token sent by the gateway device to obtain the account information of the target account, and send the target account information to the gateway device, so that the efficiency of the gateway device for obtaining the account information may be improved, and the login state of the target account may be conveniently and quickly determined.

As shown in fig. 6, when the login state determination method is applied to the gateway device 102 described above, the login state determination method may include S201 to S203.

S201, the gateway device responds to the service calling indication sent by the first server and sends a data acquisition request to the second server.

The service calling instruction comprises a service identifier of a first service, the first service is a service provided by the gateway device, the data acquisition request comprises an account identifier of a target account, the data acquisition request is used for requesting to acquire at least one hash value corresponding to the account identifier, and the service calling instruction is sent for the first server under the condition that the first server determines that a service identifier of a target service and the service identifier of the first service are stored in the first server.

In combination with the foregoing description of the embodiment, it should be understood that, in a case that the first server determines that the service identifier of the target service and the service identifier of the first service are stored in the first server, it indicates that the target service is a preset service in the first server and the first service is successfully set in the gateway device, at this time, the first server may invoke the first service, that is, send the service invocation indication to the gateway device. The gateway device may send a data acquisition request to the second server after receiving the service invocation indication.

S202, the gateway equipment receives the data acquisition response sent by the second server.

Wherein the data acquisition response includes the at least one hash value.

In connection with the description of the above embodiments, it should be understood that, after receiving a data acquisition request sent by a gateway device, the second server may determine and acquire at least one hash value corresponding to an account identification of a target account included in the data acquisition request from among a plurality of hash values stored by the second server based on the account identification, and send the data acquisition response, specifically send the at least one hash value, to the gateway device.

S203, the gateway device sends the at least one hash value to the first server, so that the first server determines that the login state of the target account is normal when the at least one hash value includes the target hash value.

It is to be understood that, after receiving the data acquisition response sent by the second server, the gateway device may send at least one hash value included in the data acquisition response to the first server. The first server, after receiving the at least one hash value, may determine whether the at least one hash value includes the target hash value; and determining that the login state of the target account is normal if the target hash value is included in the at least one hash value.

The technical scheme provided by the embodiment can at least bring the following beneficial effects: as known from S201 to S203, the gateway device may send a data obtaining request to the second server in response to the service invocation indication sent by the first server, that is, request to obtain at least one hash value corresponding to the account identifier of the target account. The second server, after receiving the data acquisition request, may determine and acquire the at least one hash value based on an account identification of the target account included in the data acquisition request, and send a data acquisition response to the gateway device. The gateway equipment receives the data acquisition response, namely the at least one hash value is acquired; the gateway device may then send the at least one hash value to the first server such that, if a target hash value is included in the at least one hash value, the first server may determine that the login status of the target account is normal. In the embodiment of the disclosure, the first server may invoke the first service when it is determined that the service identifier of the target service and the service identifier of the first service are stored in the first server, that is, send a service invocation indication to the gateway device, so that the gateway device may obtain at least one hash value corresponding to the service identifier from the second server and send the at least one hash value to the first server, thereby improving the obtaining efficiency of the at least one hash value. And the first server can determine the login state of the target account based on the at least one hash value, so that the determination efficiency of the login state can be improved.

With reference to fig. 6, as shown in fig. 7, before sending the data acquisition request to the second server, the login status determination method provided in the embodiment of the present disclosure may further include S204 to S205.

S204, the gateway equipment sends a synchronous verification request to the first server.

The synchronous verification request comprises the authorization token and is used for requesting to acquire account information of the target account.

In conjunction with the description of the above embodiments, it should be understood that the account information of the target account may include the account identification of the target account, the target hash value, and the target login time.

S205, the gateway device receives the synchronization check response sent by the first server.

And the synchronous verification response comprises the account identification, the target hash value and the target login time.

With reference to the description of the foregoing embodiment, it should be understood that, after receiving the synchronization check request, the first server may perform parsing processing on the authorization token included in the synchronization check request to obtain the account identifier, the target hash value, and the target login time; the first server may then send the synchronization check response to the gateway device, specifically send the account identifier, the target hash value, and the target login time to the gateway device.

The technical scheme provided by the embodiment can at least bring the following beneficial effects: as known from S204-S205, the gateway device may send a synchronization check request to the first server, that is, request to acquire account information of the target account. After receiving the synchronization check request, the first server may perform parsing processing on the authorization token included in the synchronization check request to obtain an account identifier of the target account, a target hash value, and a target login time, and send a synchronization check response to the gateway device. The gateway device may then receive the synchronization check response, i.e., receive the account identifier, the target hash value, and the target login time. In the embodiment of the disclosure, the gateway device may send the synchronous verification request to the first server to obtain the account information of the target account, so that the obtaining efficiency of the account information can be improved. Furthermore, the first server can complete the determination process of the login state through the data included in the account information, namely the account identifier, the target hash value and the target login time, so that the determination efficiency of the login state can be improved.

With reference to fig. 6, as shown in fig. 8, before the data acquisition request is sent to the second server, the login status determination method provided in the embodiment of the present disclosure may further include S206.

S206, the gateway equipment sends an asynchronous verification request to the first server.

With reference to the description of the foregoing embodiment, it should be understood that the asynchronous check request includes a service identifier of the target service, an account identifier of a target account, and a target hash value, where the account identifier and the target hash value are respectively an account identifier and a hash value obtained by the first server analyzing the authorization token sent by the gateway device.

It is understood that, after the network management device sends the asynchronous check request to the first server, the first server may receive the asynchronous check request, determine whether the first server stores the service representation of the target service and the service identifier of the first service, further receive at least one hash value sent by the gateway device, and determine whether the login status of the target account is normal based on whether the at least one hash value includes the target hash value. In the embodiment of the present disclosure, the process of determining the login state of the target account provided in the embodiment of the present disclosure may be triggered by the process of sending the asynchronous verification request to the first server through the gateway device, so that the login state of the target account can be accurately and effectively determined.

As shown in fig. 9, when the login state determination method is based on an interactive process between the gateway device and the first server, and an interactive process between the gateway device and the second server, the login state determination method may include S301-S312.

S301, the gateway device sends an asynchronous verification request to the first server.

The asynchronous verification request comprises a service identifier of a target service, an account identifier of a target account and a target hash value, wherein the account identifier and the target hash value are respectively obtained by analyzing and processing an authorization token sent by the gateway device by the first server.

S302, the first server receives an asynchronous verification request sent by the gateway equipment.

S303, the first server determines whether the service identifier of the target service and the service identifier of the first service are stored in the first server.

Wherein the first service is a service provided by the gateway device.

S304, the first server calls the first service under the condition that the service identification of the target service and the service identification of the first service are stored in the first server.

The first service is used for instructing the gateway device to obtain at least one hash value corresponding to the account identifier from a second server.

S305, the gateway device responds to the service calling indication sent by the first server and sends a data acquisition request to the second server.

The service calling indication includes a service identifier of a first service, the first service is a service provided by the gateway device, the data acquisition request includes an account identifier of a target account, the data acquisition request is used for requesting to acquire at least one hash value corresponding to the account identifier, and the service calling indication is sent by the first server when the first server determines that a service identifier of a target service and the service identifier of the first service are stored in the first server.

S306, the second server receives the data acquisition request.

S307, the second server determines at least one hash value according to the account identification of the target account.

S308, the second server sends a data acquisition response to the gateway equipment.

Wherein the data acquisition response includes the at least one hash value.

S309, the gateway device receives at least one hash value sent by the second server.

S310, the gateway device sends at least one hash value to the first server.

S311, the first server receives at least one hash value sent by the gateway device.

S312, in a case that the at least one hash value includes the target hash value, the first server determines that the login status of the target account is normal.

It should be understood that the explanations in S301 to S312 may refer to the descriptions in the above embodiments, and are not repeated here.

The technical scheme provided by the embodiment can at least bring the following beneficial effects: as known from S301 to S312, the gateway device may send an asynchronous check request to the first server, and the first server may determine whether the service identifier of the target service and the service identifier of the first service are stored in the first server after receiving the asynchronous check request; when the service identifier and the service identifier of the first service are stored in the first server, it indicates that the target service is a preset service in the first server and that the first service is successfully set in the gateway device, and at this time, the first server may invoke the first service, that is, instruct the gateway device to obtain at least one hash value corresponding to the account identifier from the second server.

The gateway device may send a data obtaining request to the second server in response to the service invocation indication sent by the first server (i.e., after the first service is started), that is, request to obtain at least one hash value corresponding to the account identifier of the target account, and after receiving the data obtaining request, the second server may determine the at least one hash value based on the account identifier of the target account included in the data obtaining request, and send a data obtaining response to the gateway device, specifically, send the at least one hash value to the gateway device. The gateway device may send the at least one hash value to the first server after receiving the at least one hash value, so that the first server may obtain the at least one hash value; the first server may then determine whether the at least one hash value includes a target hash value; in the case that the target hash value is included in the at least one hash value, it indicates that the device currently logged in by the target account is one of the at least one device logged in by the target account, so that the first server may determine that the login status of the target account is normal. In the embodiment of the disclosure, under the condition that the service identifier of the target service and the service identifier of the first service are stored in the first server, the first server may determine to invoke the first service (that is, the local service provided by the gateway device), specifically, instruct the gateway device to determine and obtain at least one hash value corresponding to the service identifier of the target service from the second server, and further determine whether the login state of the target account is normal based on the at least one hash value, so that the verification duration of the login state of the user can be reduced, and the determination efficiency of the login state is improved.

It is understood that, in practical implementation, the server/gateway device according to the embodiment of the present disclosure may include one or more hardware structures and/or software modules for implementing the foregoing corresponding login status determination method, and these hardware structures and/or software modules may constitute a server/gateway device. Those of skill in the art will readily appreciate that the present disclosure can be implemented in hardware or a combination of hardware and computer software for implementing the exemplary algorithm steps described in connection with the embodiments disclosed herein. Whether a function is performed as hardware or computer software drives hardware depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present disclosure.

Based on such understanding, the embodiment of the present disclosure further provides a login state determination apparatus correspondingly, and fig. 10 illustrates a schematic structural diagram of the login state determination apparatus provided in the embodiment of the present disclosure. As shown in fig. 10, the login status determination device 20 may include: a receiving module 201, a processing module 202 and a determining module 203.

The receiving module 201 is configured to receive an asynchronous verification request sent by a gateway device, where the asynchronous verification request includes a service identifier of a target service, an account identifier of a target account, and a target hash value, and the account identifier and the target hash value are an account identifier and a hash value obtained by analyzing, by the first server, an authorization token sent by the gateway device, respectively.

The processing module 202 is configured to, in a case that the service identifier and a service identifier of a first service are stored in the first server, invoke the first service, where the first service is a service provided by the gateway device, and the first service is used to instruct the gateway device to obtain, from a second server, at least one hash value corresponding to the account identifier.

The receiving module 201 is further configured to receive the at least one hash value sent by the gateway device.

A determining module 203 configured to determine that the login status of the target account is normal if the target hash value is included in the at least one hash value.

Optionally, the processing module 203 is further configured to, in a case that the service identifier is stored in the first server and the service identifier of the first service is not stored, invoke a second service, where the second service is a service provided by a third server, and the second service is used to instruct the third server to determine whether the target hash value exists in the at least one hash value.

The receiving module 201 is further configured to receive a login status notification message sent by the third server, where the login status notification message is used to notify that the login status of the target account is normal, and the login status notification message is sent by the third server when it is determined that the target hash value exists in the at least one hash value.

Optionally, the asynchronous verification request further includes a target login time, where the target login time is login time obtained by analyzing the authorization token by the first server.

The determining module 203 is further configured to determine whether the target login time is after a preset login time in case that the service identifier and the service identifier of the first service are not stored in the first server.

The determining module 203 is further configured to determine that the login status of the target account is normal if the target login time is after the preset login time.

Optionally, the login status determining apparatus 20 further includes a sending module 204.

The receiving module 201 is further configured to receive a synchronization check request sent by the gateway device, where the synchronization check request includes the authorization token, and the synchronization check request is used to request to acquire account information of the target account.

The processing module 202 is further configured to perform parsing processing on the authorization token to obtain the account identifier, the target hash value, and the target login time.

A sending module 204 configured to send a synchronization check response to the gateway device, where the synchronization check response includes the account identifier, the target hash value, and the target login time.

As described above, the embodiments of the present disclosure may perform the division of the functional modules on the login status determination apparatus according to the above method example. The integrated module can be realized in a hardware form, and can also be realized in a software functional module form. In addition, it should be noted that, the division of the modules in the embodiment of the present disclosure is schematic, and is only one logic function division, and there may be another division manner in actual implementation. For example, the functional blocks may be divided for the respective functions, or two or more functions may be integrated into one processing block.

With regard to the login state determining apparatus in the foregoing embodiment, the specific manner in which each module executes the operation and the beneficial effects thereof have been described in detail in the foregoing method embodiment, and are not described again here.

Fig. 11 is a schematic structural diagram of another login status determination apparatus provided in the present disclosure. As shown in fig. 11, the login status determination device 30 may comprise at least one processor 301 and a memory 303 for storing processor executable instructions. Wherein the processor 301 is configured to execute instructions in the memory 303 to implement the login status determination method in the above-described embodiments.

In addition, the login status determination device 30 may further comprise a communication bus 302 and at least one communication interface 304.

The processor 301 may be a Central Processing Unit (CPU), a micro-processing unit, an ASIC, or one or more integrated circuits for controlling the execution of programs according to the disclosed aspects.

The communication bus 302 may include a path that conveys information between the aforementioned components.

The communication interface 304 may be any device, such as a transceiver, for communicating with other devices or communication networks, such as an ethernet, a Radio Access Network (RAN), a Wireless Local Area Network (WLAN), etc.

The memory 303 may be, but is not limited to, a read-only memory (ROM) or other type of static storage device that may store static information and instructions, a Random Access Memory (RAM) or other type of dynamic storage device that may store information and instructions, an electrically erasable programmable read-only memory (EEPROM), a compact disk read-only memory (CD-ROM) or other optical disk storage, optical disk storage (including compact disk, laser disk, optical disk, digital versatile disk, blu-ray disk, etc.), a magnetic disk storage medium or other magnetic storage device, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer. The memory may be self-contained and connected to the processing unit by a bus. The memory may also be integrated with the processing unit.

The memory 303 is used for storing instructions for executing the disclosed solution, and is controlled to be executed by the processor 301. The processor 301 is configured to execute instructions stored in the memory 303 to implement the functions of the disclosed method.

In particular implementations, processor 301 may include one or more CPUs, such as CPU0 and CPU1 of FIG. 11, for example, as an embodiment.

In a specific implementation, the login status determination device 30 may include a plurality of processors, such as the processor 301 and the processor 307 in fig. 11, as an embodiment. Each of these processors may be a single-core (single-CPU) processor or a multi-core (multi-CPU) processor. A processor herein may refer to one or more devices, circuits, and/or processing cores that process data (e.g., computer program instructions).

In a specific implementation, the login status determination apparatus 30 may further include an output device 305 and an input device 306, as an embodiment. The output device 305 is in communication with the processor 301 and may display information in a variety of ways. For example, the output device 305 may be a Liquid Crystal Display (LCD), a Light Emitting Diode (LED) display device, a Cathode Ray Tube (CRT) display device, a projector (projector), or the like. The input device 306 is in communication with the processor 301 and can accept user input in a variety of ways. For example, the input device 306 may be a mouse, a keyboard, a touch screen device, a sensing device, or the like.

Fig. 12 is a diagram illustrating a result of another login status determination apparatus provided in the present disclosure. As shown in fig. 12, the login status determination device 40 may include: a sending module 401 and a receiving module 402.

The sending module 401 is configured to send, to a second server, a data obtaining request in response to a service invocation indication sent by a first server, where the service invocation indication includes a service identifier of a first service, the first service is a service provided by a gateway device, the data obtaining request includes an account identifier of a target account, the data obtaining request is used to request to obtain at least one hash value corresponding to the account identifier, and the service invocation indication is sent by the first server when it is determined that a service identifier of a target service and a service identifier of the first service are stored in the first server.

A receiving module 402 configured to receive a data acquisition response sent by the second server, where the data acquisition response includes the at least one hash value.

The sending module 401 is further configured to send the at least one hash value to the first server, so that in a case that a target hash value is included in the at least one hash value, the first server determines that the login state of the target account is normal.

Optionally, the sending module 401 is further configured to send a synchronization check request to the first server, where the synchronization check request includes an authorization token, and the synchronization check request is used to request to obtain account information of the target account.

The receiving module 402 is further configured to receive a synchronization check response sent by the first server, where the synchronization check response includes the account identifier, the target hash value, and the target login time.

Optionally, the sending module 401 is further configured to send an asynchronous check request to the first server, where the asynchronous check request includes a service identifier of the target service, an account identifier of the target account, and the target hash value, and the account identifier and the target hash value are obtained by analyzing, by the first server, the authorization token sent by the gateway device, and are an account identifier and a hash value respectively.

Fig. 13 is a schematic structural diagram of another login status determination apparatus provided in the present disclosure. As shown in fig. 13, the login status determination device 50 may comprise at least one processor 501 and a memory 503 for storing processor-executable instructions. Wherein the processor 501 is configured to execute instructions in the memory 503 to implement the login status determination method in the above embodiments.

In addition, the login status determination device 50 may further comprise a communication bus 502 and at least one communication interface 504.

The processor 501 may be a CPU, micro-processing unit, ASIC, or one or more integrated circuits for controlling the execution of programs in accordance with the disclosed aspects.

The communication bus 502 may include a path that conveys information between the aforementioned components.

The communication interface 504, using any transceiver or the like, is used for communication with other devices or communication networks, such as ethernet, RAN, WLAN, etc.

The memory 503 may be, but is not limited to, a ROM or other type of static storage device that can store static information and instructions, a RAM or other type of dynamic storage device that can store information and instructions, an EEPROM, a CD-ROM or other optical disk storage, optical disk storage (including compact disk, laser disk, optical disk, digital versatile disk, blu-ray disk, etc.), magnetic disk storage media or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer. The memory may be self-contained and connected to the processing unit by a bus. The memory may also be integrated with the processing unit.

The memory 503 is used for storing instructions for executing the disclosed solution, and is controlled by the processor 501. The processor 501 is configured to execute instructions stored in the memory 503 to implement the functions of the disclosed method.

In a specific implementation, processor 501 may include one or more CPUs, such as CPU0 and CPU1 in fig. 13, as an embodiment.

In a specific implementation, the login status determination device 50 may include a plurality of processors, such as the processor 501 and the processor 507 in fig. 13, as an embodiment. Each of these processors may be a single-core (single-CPU) processor or a multi-core (multi-CPU) processor. A processor herein may refer to one or more devices, circuits, and/or processing cores for processing data (e.g., computer program instructions).

In a specific implementation, the login status determination apparatus 50 may further include an output device 505 and an input device 506 as an embodiment. An output device 505, which is in communication with the processor 501, may display information in a variety of ways. For example, the output device 505 may be a Liquid Crystal Display (LCD), a Light Emitting Diode (LED) display device, a Cathode Ray Tube (CRT) display device, a projector (projector), or the like. The input device 506 is in communication with the processor 501 and can accept user input in a variety of ways. For example, the input device 506 may be a mouse, keyboard, touch screen device, or sensing device, among others.

It will be appreciated by those skilled in the art that the structure shown in fig. 11 or fig. 13 described above does not constitute a limitation of the login status determination apparatus, and may include more or less components than those shown, or combine some components, or adopt a different arrangement of components.

In addition, the present disclosure also provides a computer-readable storage medium comprising instructions that, when executed by a processor of a device, cause the device to perform the login status determination method as provided in the above embodiments.

Additionally, the present disclosure also provides a computer program product comprising instructions which, when executed by a processor of a device, cause the device to perform the login status determination method as provided in the above embodiments.

Other embodiments of the disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the disclosure disclosed herein. This disclosure is intended to cover any variations, uses, or adaptations of the disclosure following, in general, the principles of the disclosure and including such departures from the present disclosure as come within known or customary practice within the art to which the disclosure pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the disclosure being indicated by the following claims.

Claims

1. A login state determination method is applied to a first server, and is characterized by comprising the following steps:

receiving an asynchronous verification request sent by gateway equipment, wherein the asynchronous verification request comprises a service identifier of a target service, an account identifier of a target account and a target hash value, and the account identifier and the target hash value are respectively an account identifier and a hash value obtained by analyzing an authorization token sent by the gateway equipment by the first server;

calling a first service under the condition that the service identifier and a service identifier of the first service are stored in the first server, wherein the first service is a service provided by the gateway equipment, and the first service is used for indicating the gateway equipment to acquire at least one hash value corresponding to the account identifier from a second server;

receiving the at least one hash value sent by the gateway equipment;

and under the condition that the target hash value is included in the at least one hash value, determining that the login state of the target account is normal.

2. The login status determination method according to claim 1, wherein the method further comprises:

if the service identifier is stored in the first server and the service identifier of the first service is not stored, invoking a second service, wherein the second service is a service provided by a third server and is used for instructing the third server to determine whether the target hash value exists in the at least one hash value;

and receiving a login state notification message sent by the third server, wherein the login state notification message is used for notifying that the login state of the target account is normal, and the login state notification message is sent by the third server under the condition that the target hash value exists in the at least one hash value.

3. A login state determination method is applied to gateway equipment and is characterized by comprising the following steps:

sending a data acquisition request to a second server in response to a service calling indication sent by a first server, wherein the service calling indication comprises a service identifier of a first service, the first service is a service provided by the gateway device, the data acquisition request comprises an account identifier of a target account, the data acquisition request is used for requesting to acquire at least one hash value corresponding to the account identifier, and the service calling indication is sent by the first server under the condition that the service identifier of the target service and the service identifier of the first service are determined to be stored in the first server;

receiving a data acquisition response sent by the second server, wherein the data acquisition response comprises the at least one hash value;

sending the at least one hash value to the first server, so that the first server determines that the login state of the target account is normal if a target hash value is included in the at least one hash value.

4. A login status determination apparatus, comprising: the device comprises a receiving module, a processing module and a determining module;

the receiving module is configured to receive an asynchronous verification request sent by a gateway device, where the asynchronous verification request includes a service identifier of a target service, an account identifier of a target account, and a target hash value, and the account identifier and the target hash value are an account identifier and a hash value obtained by analyzing, by the first server, an authorization token sent by the gateway device;

the processing module is configured to invoke a first service under the condition that the service identifier and a service identifier of the first service are stored in the first server, wherein the first service is a service provided by the gateway device, and the first service is used for instructing the gateway device to acquire at least one hash value corresponding to the account identifier from a second server;

the receiving module is further configured to receive the at least one hash value sent by the gateway device;

the determining module is configured to determine that the login status of the target account is normal if the target hash value is included in the at least one hash value.

5. A login status determination apparatus, comprising: a transmitting module and a receiving module;

the sending module is configured to send a data obtaining request to a second server in response to a service calling indication sent by a first server, wherein the service calling indication includes a service identifier of a first service, the first service is a service provided by a gateway device, the data obtaining request includes an account identifier of a target account, the data obtaining request is used for requesting to obtain at least one hash value corresponding to the account identifier, and the service calling indication is sent by the first server under the condition that the first server is determined to store a service identifier of a target service and the service identifier of the first service;

the receiving module is configured to receive a data acquisition response sent by the second server, where the data acquisition response includes the at least one hash value;

the sending module is further configured to send the at least one hash value to the first server, so that in a case that a target hash value is included in the at least one hash value, the first server determines that the login state of the target account is normal.

6. A login state determination system, characterized in that the login state determination system comprises a first server and a gateway device;

the first server is configured to execute the login status determination method according to claim 1 or 2;

the gateway device is configured to perform the login status determination method of claim 3.

7. A server, characterized in that the server comprises:

a processor;

a memory configured to store the processor-executable instructions;

wherein the processor is configured to execute the instructions to implement the login status determination method according to claim 1 or 2.

8. A gateway device, characterized in that the gateway device comprises:

a processor;

a memory configured to store the processor-executable instructions;

wherein the processor is configured to execute the instructions to implement the login status determination method of claim 3.

9. A computer-readable storage medium having instructions stored thereon, wherein the instructions in the computer-readable storage medium, when executed by a processor of a device, enable the device to perform the login state determination method of claim 1 or 2, or perform the login state determination method of claim 3.

10. A computer program product, characterized in that it comprises computer instructions which, when run on a processor of a device, cause the device to perform the login status determination method according to claim 1 or 2, or to perform the login status determination method according to claim 3.