CN108900562A - Sharing method, device, electronic equipment and the medium of logging state - Google Patents
Sharing method, device, electronic equipment and the medium of logging state Download PDFInfo
- Publication number
- CN108900562A CN108900562A CN201811183437.8A CN201811183437A CN108900562A CN 108900562 A CN108900562 A CN 108900562A CN 201811183437 A CN201811183437 A CN 201811183437A CN 108900562 A CN108900562 A CN 108900562A
- Authority
- CN
- China
- Prior art keywords
- alliance
- information
- identity
- account
- login
- 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.)
- Granted
Links
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
- H04L63/0807—Network architectures or network communication protocols for network security for authentication of entities using tickets, e.g. Kerberos
-
- 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
- H04L63/0815—Network architectures or network communication protocols for network security for authentication of entities providing single-sign-on or federations
-
- 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
- H04L63/0876—Network architectures or network communication protocols for network security for authentication of entities based on the identity of the terminal or configuration, e.g. MAC address, hardware or software configuration or device fingerprint
Landscapes
- Engineering & Computer Science (AREA)
- Computer Hardware Design (AREA)
- Computer Security & Cryptography (AREA)
- Computing Systems (AREA)
- General Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Power Engineering (AREA)
- Information Transfer Between Computers (AREA)
Abstract
Present disclose provides a kind of sharing methods of logging state, including:The user's request for carrying cookie is received, the cookie includes the Alliance Identity and transaction id of the first alliance side;According to the Alliance Identity of the first alliance side in the cookie, verification be stored in the information of alliance's account information chain whether include the first alliance side Alliance Identity;If including determining that the login Alliance Identity of other alliance sides relevant to the first alliance side, the login Alliance Identity are stored in account log-on message chain according to the transaction id in the cookie;According to the login Alliance Identity of other described alliance sides, the logging state of the first alliance side is shared to other described alliance sides, wherein, the first alliance side and other alliance sides share a login account, and alliance's account information chain and the account log-on message chain are block chain.The disclosure additionally provides sharing means, electronic equipment and the medium of a kind of logging state.
Description
Technical field
This disclosure relates to which the technical field of internet more particularly to a kind of sharing method of logging state, device, electronics are set
Standby and medium.
Background technique
Increase with the development of internet technology with corresponding application and website, more and more people select using identical
The different system of Account Logon.For example, user can log in Sina website, everybody website, www.baidu.com using identical account
Etc..But when using identical Account Logon different system, the logging state of each system can not be shared, thus
Lead to the system that user is different using the login of identical account repeatedly, reduces user experience.
Summary of the invention
In view of this, the disclosure provides sharing method, device, electronic equipment and the medium of a kind of logging state, Jin Erzhi
Partially solves the problems, such as caused by the limitation and defect due to the relevant technologies one or more.
The first aspect of the disclosure provides a kind of sharing method of logging state, including:Reception carries cookie
User request, the cookie include the first alliance side Alliance Identity and transaction id;According to first in the cookie
The Alliance Identity of alliance side, verification be stored in the information of alliance's account information chain whether include the first alliance side alliance
Mark;If including determining other alliance sides relevant to the first alliance side according to the transaction id in the cookie
Alliance Identity is logged in, the login Alliance Identity is stored in account log-on message chain;Joined according to the login of other described alliance sides
Alliance mark, the logging state of the first alliance side is shared to other described alliance sides, wherein the first alliance side and other
Alliance side shares a login account.
In accordance with an embodiment of the present disclosure, this method further includes:If in the information for being stored in alliance's account information chain
Do not include the Alliance Identity of the first alliance side, then sends logging in again for task to the first alliance side;Described in reception
The information that first alliance side logins successfully again, and a login transaction is inserted into order to log in the first alliance side again
Successful information is synchronized to the account log-on message chain and alliance's account information chain respectively;Based on the first alliance side
Again the information logined successfully and the transaction id for logging in transaction, generate the cookie, and send the cookie.
In accordance with an embodiment of the present disclosure, according to the login Alliance Identity of other described alliance sides, to other described alliance sides
The logging state for sharing the first alliance side further includes:According to the login Alliance Identity of other described alliance sides and described first
The information of forming an alliance of alliance side determines the allied member to form an alliance with the first alliance side from other described alliance sides;To with
The logging state of the first alliance side is shared by the allied member that the first alliance side forms an alliance.
In accordance with an embodiment of the present disclosure, the first alliance side is shared to the allied member to form an alliance with the first alliance side
Logging state include:Whether the logging state for inquiring the first alliance side is online;If be online,
Then judge whether log in the time of the first alliance side and the time interval of current time is greater than the out-of-service time;If it is lower,
The logging state of the first alliance side is shared to the allied member to form an alliance with the first alliance side.
In accordance with an embodiment of the present disclosure, this method further includes:When the user by the login account from described first
When alliance side nullifies or exits, the cancellation or the information exited are written to all comprising forming an alliance with the first alliance side
In the cookies of the information of alliance side.
In accordance with an embodiment of the present disclosure, alliance's account information chain and the account log-on message chain are block chain.
The second aspect of the disclosure provides a kind of sharing means of logging state, including:First receiving module, is used for
The user's request for carrying cookie is received, the cookie includes the Alliance Identity and transaction id of the first alliance side;Calibration mode
Block, for the Alliance Identity according to the first alliance side in the cookie, verification is stored in the information of alliance's account information chain
In whether include the first alliance side Alliance Identity;Determining module, if including, according to the transaction in the cookie
Id determines that the login Alliance Identity of other alliance sides relevant to the first alliance side, the login Alliance Identity are stored in
Account log-on message chain;Sharing module, for the login Alliance Identity according to other described alliance sides, to other described alliance sides
Share the logging state of the first alliance side, wherein the first alliance side and other alliance sides share a login account.
In accordance with an embodiment of the present disclosure, which further includes:Sending module, if described be stored in alliance's account information chain
Information in do not include the first alliance side Alliance Identity, then send the logging in again of the task to the first alliance side;
Second receiving module, the information logined successfully again for receiving the first alliance side, and be inserted into logins trade so as to
It is synchronized to the account log-on message chain and alliance's account respectively in the information for logining successfully the first alliance side again
Number information chain;Generation module, information and the friendship for logging in transaction for being logined successfully again based on the first alliance side
Easy id generates the cookie, and sends the cookie.
In accordance with an embodiment of the present disclosure, according to the login Alliance Identity of other described alliance sides, to other described alliance sides
The logging state for sharing the first alliance side further includes:According to the login Alliance Identity of other described alliance sides and described first
The information of forming an alliance of alliance side determines the allied member to form an alliance with the first alliance side from other described alliance sides;To with
The logging state of the first alliance side is shared by the allied member that the first alliance side forms an alliance.
In accordance with an embodiment of the present disclosure, the first alliance side is shared to the allied member to form an alliance with the first alliance side
Logging state include:Whether the logging state for inquiring the first alliance side is online;If be online,
Then judge whether log in the time of the first alliance side and the time interval of current time is greater than the out-of-service time;If it is lower,
The logging state of the first alliance side is shared to the allied member to form an alliance with the first alliance side.
In accordance with an embodiment of the present disclosure, which further includes:Writing module, when the user by the login account from institute
When stating the cancellation of the first alliance side or exiting, the cancellation or the information exited are written to comprising forming an alliance with the first alliance side
All alliance sides information cookies in.
In accordance with an embodiment of the present disclosure, alliance's account information chain and the account log-on message chain are block chain.
A kind of electronic equipment is provided in terms of the third of the disclosure, including:One or more processors, and storage dress
It sets.The storage device is for storing one or more programs.Wherein, when one or more of programs are by one or more
When a processor executes, so that one or more of processors execute the sharing method of logging state as described above.
4th aspect of the disclosure provides a kind of computer-readable medium, is stored thereon with executable instruction, this refers to
Enable the sharing method for making processor execute logging state as described above when being executed by processor.
5th aspect of the disclosure provides a kind of computer program, and the computer program includes that computer is executable
Instruction, described instruction is when executed for realizing the sharing method of logging state.
The sharing method for the logging state that the disclosure provides has the beneficial effect that:
Technical solution provided by the present disclosure can be by being stored in the information checking user request of alliance's account information chain
Cookie, in order to determine cookie in whether include the first alliance side Alliance Identity, if including, according to be stored in connection
Alliance's account information determines the login Alliance Identity of other alliance sides relevant to the first alliance side, then according to other alliances
The login Alliance Identity of side, the logging state of the first alliance side is shared to other alliance sides, to realize different connection
Shared judgement of the alliance side to the logging state of same account, it is straight from the system of a listed alliance side to facilitate user in this way
The system for jumping to other alliance sides is connect, is efficiently avoided in the related technology when the system different using identical Account Logon
When, the logging state of each system can not be shared, and also need user different using the login of identical account repeatedly
The defect of system.
It should be understood that above general description and following detailed description be only it is exemplary and explanatory, not
The disclosure can be limited.
Detailed description of the invention
Fig. 1 diagrammatically illustrates the flow chart of the sharing method of the logging state according to the embodiment of the present disclosure;
Fig. 2 diagrammatically illustrates the flow chart of the sharing method of the logging state according to the disclosure another embodiment;
Fig. 3 diagrammatically illustrates the flow chart of the sharing method of the logging state according to the disclosure another embodiment;
Fig. 4 diagrammatically illustrates the block diagram of the sharing method of the logging state according to the disclosure another embodiment;
Fig. 5 diagrammatically illustrates the block diagram of the sharing means of the logging state according to the embodiment of the present disclosure;
Fig. 6 diagrammatically illustrates the block diagram of the sharing means of the logging state according to the disclosure another embodiment;
Fig. 7 diagrammatically illustrates the block diagram of the computer system of the electronic equipment according to the embodiment of the present disclosure.
Specific embodiment
Hereinafter, will be described with reference to the accompanying drawings embodiment of the disclosure.However, it should be understood that these descriptions are only exemplary
, and it is not intended to limit the scope of the present disclosure.In addition, in the following description, descriptions of well-known structures and technologies are omitted, with
Avoid unnecessarily obscuring the concept of the disclosure.
Term as used herein is not intended to limit the disclosure just for the sake of description specific embodiment.It uses herein
The terms "include", "comprise" etc. show the presence of the feature, step, operation and/or component, but it is not excluded that in the presence of
Or add other one or more features, step, operation or component.
There are all terms (including technical and scientific term) as used herein those skilled in the art to be generally understood
Meaning, unless otherwise defined.It should be noted that term used herein should be interpreted that with consistent with the context of this specification
Meaning, without that should be explained with idealization or excessively mechanical mode.
It, in general should be according to this using statement as " at least one in A, B and C etc. " is similar to
Field technical staff is generally understood the meaning of the statement to make an explanation (for example, " system at least one in A, B and C "
Should include but is not limited to individually with A, individually with B, individually with C, with A and B, with A and C, have B and C, and/or
System etc. with A, B, C).Using statement as " at least one in A, B or C etc. " is similar to, generally come
Saying be generally understood the meaning of the statement according to those skilled in the art to make an explanation (for example, " having in A, B or C at least
One system " should include but is not limited to individually with A, individually with B, individually with C, with A and B, have A and C, have
B and C, and/or the system with A, B, C etc.).It should also be understood by those skilled in the art that substantially arbitrarily indicating two or more
The adversative conjunction and/or phrase of optional project shall be construed as either in specification, claims or attached drawing
A possibility that giving including one of these projects, either one or two projects of these projects.For example, phrase " A or B " should
A possibility that being understood to include " A " or " B " or " A and B ".
Embodiment of the disclosure provides a kind of sharing method of logging state, including:Receive the use for carrying cookie
Family request, the cookie include the Alliance Identity and transaction id of the first alliance side;According to the first alliance in the cookie
The Alliance Identity of side, verification are stored in the information of alliance's account information chain whether the alliance including the first alliance side marks
Know;If including according to the transaction id in the cookie, determination is stepped on to described other relevant alliance sides of first alliance side
Alliance Identity is recorded, the login Alliance Identity is stored in account log-on message chain;According to the login alliance of other described alliance sides
Mark, the logging state of the first alliance side is shared to other described alliance sides, wherein the first alliance side and other connection
Alliance side shares a login account.
The sharing method of the logging state provided by the disclosure can be by being stored in the information of alliance's account information chain
The cookie in user's request is verified, in order to determine in cookie whether include the Alliance Identity of the first alliance side, if wrapped
It includes, according to alliance's account information is stored in, determines the login Alliance Identity of other alliance sides relevant to the first alliance side, so
Afterwards according to the login Alliance Identity of other alliance sides, the logging state of the first alliance side is shared to other alliance sides, thus
Shared judgement of the different alliance sides to the logging state of same account is realized, it is listed from one to facilitate user in this way
The system that the system of alliance side jumps directly to other alliance sides efficiently avoids in the related technology when the identical account of use
When logging in different systems, the logging state of each system can not be shared, and also need user anti-using identical account
The defect of the different system of multiple login.
Fig. 1 diagrammatically illustrates the flow chart of the sharing method of the logging state according to the embodiment of the present disclosure.
As shown in Figure 1, the sharing method of logging state includes step S101~step S104.
In step s101, the user's request for carrying cookie is received, the cookie includes the connection of the first alliance side
Alliance's mark and transaction id.
In step s 102, according to the Alliance Identity of the first alliance side in the cookie, verification is stored in alliance's account
In the information of number information chain whether include the first alliance side Alliance Identity.
In step s 103, if including, according to the transaction id in the cookie, determination and first alliance side phase
The login Alliance Identity of other the alliance sides closed, the login Alliance Identity are stored in account log-on message chain.
In step S104, according to the login Alliance Identity of other described alliance sides, institute is shared to other described alliance sides
State the logging state of the first alliance side, wherein the first alliance side and other alliance sides share a login account.
This method can by be stored in alliance's account information chain information checking user request in cookie, in order to
Determine whether the Alliance Identity including the first alliance side, according to alliance's account information is stored in, determines if including in cookie
Then the login Alliance Identity of other alliance sides relevant to the first alliance side is marked according to the login alliance of other alliance sides
Know, the logging state of the first alliance side is shared to other alliance sides, to realize different alliance sides to same account
Logging state shared judgement, facilitate user in this way from the system of a listed alliance side and jump directly to other connection
The system of alliance side efficiently avoids in the related technology when using identical Account Logon different system, each system
Logging state can not be shared, and user is also needed to use the defect of the different system of the login of identical account repeatedly.
In some embodiments of the present disclosure, the user's request for carrying cookie is being received, the cookie includes the
Before the Alliance Identity and transaction id of one alliance side, usually defaults the user and used above-mentioned login account logged first
The system of alliance side.
In some embodiments of the present disclosure, the information of each alliance side can be stored in alliance in a manner of alliance's chain
Account information chain, and user is logged in side of the logging state to trade of the system of each alliance side using above-mentioned login account
Account log-on message chain is written in formula, to realize shared judgement of the different alliance sides to the logging state of same account, Yong Huke
Directly its alliance system is jumped to from a listed system.Wherein, above-mentioned alliance's account information chain and the account log in
Information chain is block chain.
In some embodiments of the present disclosure, the characteristics of alliance's chain be exactly it is shared, block chain is written for each alliance side
In data, while other alliance side's nodes can be written into, and can be directly viewable by other alliance sides.For accessing alliance's chain
Each alliance side, all there are unique primary account number of confirmation in all alliance sides to each account, in order to which each alliance side is sentenced
It is disconnected.
In some embodiments of the present disclosure, the information for being stored in alliance's account information chain can be each account each
It is as follows to enter chain data format for information in alliance:
Primary account number | The sub- account of alliance | Alliance Identity | The domain alliance Cookie |
Wherein, primary account number can be above-mentioned login account, for example, identification card number or cell-phone number etc. can be used in login account
Identity;Sub- account is account information of each user in corresponding alliance, and to prevent from divulging a secret, cryptographic means guarantor can be used
It deposits;Alliance Identity is the unique identification of corresponding alliance side, for example, it may be number or character string, it is desirable that all to be added to alliance
Each Alliance Identity in chain is not reproducible;The domain alliance Cookie, the domain letter of stored cookie save location when being for logging in
Breath, for example, domain information can refer to different top-level domains, such as:Jd.com, baidu.com, qq.com etc..
In some embodiments of the present disclosure, the information by other the alliance sides to form an alliance with the first alliance side is needed to be stored in
Alliance's account information chain.For example, other alliance sides be the second alliance side, third alliance side, fourth federation side etc., if second
Alliance side, third alliance side, fourth federation side and the first alliance side form an alliance, then can log in four connection using same primary account number
The system of alliance side needs in this lower situation by the sub- account of the alliance of the second alliance side, third alliance side and fourth federation side
Number, Alliance Identity and the domain alliance cookie be stored in alliance's account information chain, in order to in access visitor's HTTP request
Cookie information verified.
In some embodiments of the present disclosure, account log-on message chain is used to save the login of each account/publish information,
It is as follows that it enters chain data format:
Primary account number | Login time | Log in Alliance Identity | Log in type |
Wherein, primary account number can be above-mentioned login account, for example, identification card number or cell-phone number etc. can be used in login account
Identity;Login time can be the time that each alliance's method, system is logged in using primary account number;Logging in Alliance Identity can be
Use the Alliance Identity of the logged each alliance's method, system of primary account number;Login type, which can be, logs in each alliance using primary account number
The logging state of method, system publishes state, be also possible to log in using primary account number the presence of each alliance's method, system or from
Linear state.
In some embodiments of the present disclosure, the information by other the alliance sides to form an alliance with the first alliance side is needed to be stored in
Alliance's account information chain.For example, other alliance sides be the second alliance side, third alliance side, fourth federation side etc., if second
Alliance side, third alliance side, fourth federation side and the first alliance side form an alliance, if user uses same primary account number logged four
The system of alliance side needs to log in the primary account number system of the second alliance side, third alliance side is in this lower situation
System and fourth federation side system login time, log in Alliance Identity (such as the alliance side of each alliance side alliance mark
Know), log in type (such as log in or publish) storage arrive account log-on message chain.
In some embodiments of the present disclosure, user can access first based on the URL of the first alliance side in browser end
The system of alliance side, in access, server end can receive the user's request for carrying cookie, be may be implemented in this way to clear
The cookie at device end of looking at is verified.For example, the URL of the first alliance side can include but is not limited to www.jd.com,
Www.baidu.com, www.qq.com etc..
In some embodiments of the present disclosure, above-mentioned cookie may include key and value.Wherein, key can be
The Alliance Identity of one alliance side, value can be transaction id.For example, the Alliance Identity of the first alliance side can be character string and
Number.Transaction id can be to be generated when storing first alliance side's information to block chain, and the transaction for inquiring the secondary transaction is remembered
Record.For example, transaction record can be inquired (for example, the transaction record can be account log-on message chain using Value as transaction id
In transaction record), if transaction record is there is no showing that Value is to forge, need to log in the first alliance side again at this time is
Otherwise system then obtains the login Alliance Identity of other alliance sides relevant to the first alliance side from transaction record.
In some embodiments of the present disclosure, the login Alliance Identity of other alliance sides relevant to the first alliance side can be with
Refer to the system that user uses current other logged alliance sides of primary account number for logging in first alliance's method, system, in this case,
The Alliance Identity of other alliance sides can be referred to as to log in Alliance Identity.
In some embodiments of the present disclosure, other alliance sides can be multiple or one.And in other alliance sides
It can be part alliance side to form an alliance with the first alliance side, the logging state of the first alliance side can be shared into part alliance at this time
The system of side.Certainly it is also possible to all alliance sides in other alliance sides all to form an alliance with the first alliance side, it at this time can be by
The system that the logging state of one alliance side shares to all alliance sides.That is, each alliance customized can join with other
It forms an alliance alliance side.
In some embodiments of the present disclosure, this method further includes:When the user by the login account from described
When one alliance side nullifies or exits, the cancellation or the information exited are written to the institute comprising forming an alliance with the first alliance side
In the cookies for having the information of alliance side.For example, when user browser end by login account from the system of the first alliance side
When nullifying or exiting, received server-side to the cancellation or the information exited, and the cancellation or the information exited are directed to block
Chain is inserted into a transaction, in order to other alliance sides that information notice is formed an alliance with the first alliance side.For example, user is from first
Nullify or log off in the system of alliance side account when, the transaction published can be written, into block chain in order to rear
Continue other federation nodes and does correct judgement.Specifically, login account (i.e. primary account number) can be inquired from alliance's account information chain
Then corresponding all alliance sides traverse all alliances label of alliance side's list, corresponding to delete owning in Response
Cookie information.
Fig. 2 diagrammatically illustrates the flow chart of the sharing method of the logging state according to the disclosure another embodiment.
As shown in Fig. 2, the above method further includes step S201~step S203.
In step s 201, if in the information for being stored in alliance's account information chain not including the first alliance side
Alliance Identity, then send the logging in again of the task to the first alliance side.
In step S202, the information that the first alliance side logins successfully again is received, and is inserted into a login transaction
In order to which the information for logining successfully the first alliance side again is synchronized to the account log-on message chain and described respectively
Alliance's account information chain.
In step S203, the information and the transaction for logging in transaction that are logined successfully again based on the first alliance side
Id generates the cookie, and sends the cookie.
In the method, if be stored in the information of alliance's account information chain do not include the first alliance side alliance mark
Know, then sends logging in again for task to the first alliance side, then receive the information that the first alliance side logins successfully again, and insert
Enter login transaction in order to the information for logining successfully the first alliance side again be synchronized to respectively account log-on message chain and
Alliance's account information chain, the transaction id of the information and login transaction that are then logined successfully again based on the first alliance side, is generated
Cookie, and cookie is sent, facilitate that shape can be logged in when user logs in the system of the first alliance side next time in this way
State shares to other the alliance sides to form an alliance with the first alliance side.
In some embodiments of the present disclosure, the information that above-mentioned first alliance side logins successfully again may include that user makes
Primary account number, the Alliance Identity of the first alliance side, the sub- account of alliance of the first alliance side, the domain name of the first alliance side, may be used also
To include the time for logging in first alliance's method, system, log in Alliance Identity (i.e. the Alliance Identity of the first alliance side), login type
(logging in or online).
It, can be with after receiving the information that the first alliance side logins successfully again in some embodiments of the present disclosure
It is inserted into a transaction to block chain, it at this time can be sub by the alliance of primary account number, the Alliance Identity of the first alliance side, the first alliance side
Account, the domain name of the first alliance side are synchronized to alliance's account information chain, and the time, the login that will log in first alliance's method, system
Alliance Identity (i.e. the Alliance Identity of the first alliance side), login type (logging in or online) are synchronized to account log-on message chain.
In some embodiments of the present disclosure, the information logined successfully again based on the first alliance side and the friendship for logging in transaction
Easy id may include that Alliance Identity based on the first alliance side and transaction id generate cookie, in order to can be with when logging in next time
The user's request for carrying the cookie is received, school is carried out to the cookie by being stored in the information of block chain to realize
It tests.
Fig. 3 diagrammatically illustrates the flow chart of the sharing method of the logging state according to the disclosure another embodiment.
As shown in figure 3, above-mentioned steps 104 can specifically include step S301 and step S302.
In step S301, according to the letter of forming an alliance of the login Alliance Identity of other described alliance sides and the first alliance side
Breath, determines the allied member to form an alliance with the first alliance side from other described alliance sides.
In step s 302, the login of the first alliance side is shared to the allied member to form an alliance with the first alliance side
State.
In some embodiments of the present disclosure, the alliance to form an alliance therewith can be arranged in each alliance that block chain is added
Side (forming alliance group), jumps the allied member not in group, it is still desirable to carry out the judgement of alliance side, can keep away in this way
Exempt from the logging state that the first alliance side is shared to the allied member not in group.
Fig. 4 diagrammatically illustrates the flow chart of the sharing method of the logging state according to the disclosure another embodiment.
As shown in figure 4, above-mentioned steps 302 can specifically include step S401~step S403.
In step S401, whether the logging state for inquiring the first alliance side is online.
In step S402, if be online, judge to log in the first alliance side time and it is current when
Between time interval whether be greater than the out-of-service time.
In step S403, if it is lower, sharing described first to the allied member to form an alliance with the first alliance side
The logging state of alliance side.
In some embodiments of the present disclosure, if the logging state of the first alliance side is to log in or online, and log in the
The time of one alliance side and the time interval of current time are greater than the out-of-service time, then are not necessarily to the alliance to form an alliance with the first alliance side
Member shares the logging state of the first alliance side, effectively reduces the loss of user.For example, user is logged in using public computer
The system of first alliance side, account of not nullifying or log off after user is using complete computer, in this case,
If not executing above-mentioned steps S402, it is likely to result in the loss of user.Therefore, it is necessary to judge the time of the first alliance side of login
Whether it is greater than the out-of-service time with the time interval of current time, can further determines whether to tie with the first alliance side in this way
The logging state of the first alliance side is shared by the allied member of alliance.
In some embodiments of the present disclosure, if the logging state of the first alliance side is to publish, and log in the first alliance
The time of side and the time interval of current time are less than the out-of-service time, then without total to the allied member to form an alliance with the first alliance side
The logging state of the first alliance side is enjoyed, this can also reduce the loss of user.
In some embodiments of the present disclosure, according to the Alliance Identity of login combine current federation node self maintained (or
Otherwise obtain) alliance's group information be made whether log in alliance be alliance group membership judgement;If alliance group judges not
It sets up, then show current alliance side and has logged in not yet shared login state before alliance's square mesh, it is therefore desirable to log in again, otherwise then
The state of login is obtained from transaction record;If logging state is to publish, shows that user has published, needs to log in again,
Otherwise the login time in current time and chain is judged, checks whether current time is greater than the session out-of-service time and adds
Login time;If more than then showing that currently logged on user has been failed, needs to log in again, otherwise show that logging state is normal, step on
It records successfully.
Fig. 5 diagrammatically illustrates the block diagram of the sharing means of the logging state according to the embodiment of the present disclosure.
As shown in figure 5, the sharing means 500 of logging state include the first receiving module 510, correction verification module 520, determine mould
Block 530 and sharing module 540.
First receiving module 510, for receiving the user's request for carrying cookie, the cookie includes the first alliance
The Alliance Identity and transaction id of side.
Correction verification module 520, for the Alliance Identity according to the first alliance side in the cookie, verification is stored in alliance
In the information of account information chain whether include the first alliance side Alliance Identity.
Determining module 530, if including, according to the transaction id in the cookie, determination and first alliance side phase
The login Alliance Identity of other the alliance sides closed, the login Alliance Identity are stored in account log-on message chain.
Sharing module 540, it is shared to other described alliance sides for the login Alliance Identity according to other described alliance sides
The logging state of the first alliance side, wherein the first alliance side and other alliance sides share a login account.
The sharing means 500 of the logging state can be requested by being stored in the information checking user of alliance's account information chain
In cookie, in order to determine in cookie whether include the first alliance side Alliance Identity, if including, according to being stored in
Alliance's account information determines the login Alliance Identity of other alliance sides relevant to the first alliance side, then according to other connection
The login Alliance Identity of alliance side, the logging state of the first alliance side is shared to other alliance sides, to realize different
Shared judgement of the alliance side to the logging state of same account facilitates system of the user from a listed alliance side in this way
The system for jumping directly to other alliance sides, efficiently avoid in the related technology when using identical Account Logon it is different be
When system, the logging state of each system can not be shared, and also need user different using the login of identical account repeatedly
System defect.
In accordance with an embodiment of the present disclosure, the sharing means 500 of the logging state can be used to implement the description of Fig. 1 embodiment
The sharing method of logging state.
Fig. 6 diagrammatically illustrates the block diagram of the sharing means of the logging state according to the disclosure another embodiment.
As shown in fig. 6, in addition to the first receiving module 510 of Fig. 1 description, correction verification module 520, determining module 530 and sharing
Except module 540, the sharing means 600 of logging state further include sending module 610, the second receiving module 620, generation module
630 and writing module 640.
Sending module 610, if in the information for being stored in alliance's account information chain not including the first alliance side
Alliance Identity, then send the logging in again of the task to the first alliance side.
Second receiving module 620, the information logined successfully again for receiving the first alliance side, and be inserted into one and step on
Record transaction in order to the information for logining successfully the first alliance side again be synchronized to respectively the account log-on message chain and
Alliance's account information chain.
Generation module 630, what information and the login for being logined successfully again based on the first alliance side were traded
Trade id, generates the cookie, and send the cookie.
Writing module 640, when the login account is nullified or exited from the first alliance side by the user, by institute
State the cookies that the information nullified or exited is written to the information of all alliance sides comprising forming an alliance with the first alliance side
In.
In the sharing means 600 of the logging state, if being stored in the information of alliance's account information chain does not include
The Alliance Identity of one alliance side then sends logging in again for task to the first alliance side, then receives the first alliance side and step on again
Successful information is recorded, and is inserted into a login transaction in order to which the information for logining successfully the first alliance side again is synchronized to respectively
Account log-on message chain and alliance's account information chain, the information and login transaction then logined successfully again based on the first alliance side
Transaction id, generate cookie, and send cookie, facilitate in this way when user logs in the system of the first alliance side next time,
Its logging state can be shared to other the alliance sides to form an alliance with the first alliance side.
In accordance with an embodiment of the present disclosure, the sharing means 600 of the logging state can be used to implement Fig. 2~Fig. 4 embodiment
The sharing method of the logging state of description.
It is understood that the first receiving module 510, correction verification module 520, determining module 530, sharing module 540, transmission
Module 610, the second receiving module 620, generation module 630 and writing module 640, which may be incorporated in a module, to be realized,
Or any one module therein can be split into multiple modules.Alternatively, one or more modules in these modules
At least partly function can be combined at least partly function of other modules, and be realized in a module.According to the present invention
Embodiment, the first receiving module 510, correction verification module 520, determining module 530, sharing module 540, sending module 610, second
At least one of receiving module 620, generation module 630 and writing module 640 can at least be implemented partly as hardware
Circuit, such as field programmable gate array (FPGA), programmable logic array (PLA), system on chip, the system on substrate, envelope
The system loaded onto, specific integrated circuit (ASIC), or can be to carry out any other reasonable side that is integrated or encapsulating to circuit
The hardware such as formula or firmware realize, or is realized with software, the appropriately combined of three kinds of implementations of hardware and firmware.Alternatively,
First receiving module 510, correction verification module 520, determining module 530, sharing module 540, sending module 610, the second receiving module
620, at least one of generation module 630 and writing module 640 can at least be implemented partly as computer program mould
Block can execute the function of corresponding module when the program is run by computer.
Fig. 7 diagrammatically illustrates the block diagram of the computer system of the electronic equipment according to the embodiment of the present disclosure.Fig. 7 is shown
Computer system be only an example, should not function to the embodiment of the present disclosure and use scope bring any restrictions.
As shown in fig. 7, include processor 701 according to the computer system 700 of the electronic equipment of the embodiment of the present disclosure, it can
To be loaded into random access storage device according to the program being stored in read-only memory (ROM) 702 or from storage section 708
(RAM) program in 703 and execute various movements appropriate and processing.Processor 701 for example may include general purpose microprocessor
(such as CPU), instruction set processor and/or related chip group and/or special microprocessor are (for example, specific integrated circuit
(ASIC)), etc..Processor 701 can also include the onboard storage device for caching purposes.Processor 701 may include using
In the different movements for executing the method flow according to the embodiment of the present disclosure with reference to FIG. 1 to FIG. 4 description single treatment units or
Person is multiple processing units.
In RAM 703, it is stored with system 700 and operates required various programs and data.Processor 701, ROM 702 with
And RAM 703 is connected with each other by bus 704.Processor 701 is held by executing the program in ROM 702 and/or RAM 703
The various steps of the sharing method for the logging state that row is described above with reference to FIG. 1 to FIG. 4.It is noted that the program can also deposit
Storage is in one or more memories in addition to ROM 702 and RAM 703.Processor 701 can also be stored in by executing
Program in the one or more memory come execute the logging state described above with reference to FIG. 1 to FIG. 4 sharing method it is each
Kind step.
In accordance with an embodiment of the present disclosure, system 700 can also include input/output (I/O) interface 707, input/output
(I/O) interface 707 is also connected to bus 704.System 700 can also include be connected to I/O interface 705 with one in lower component
Item is multinomial:Importation 706 including keyboard, mouse etc.;Including such as cathode-ray tube (CRT), liquid crystal display (LCD)
Deng and loudspeaker etc. output par, c 707;Storage section 708 including hard disk etc.;And including such as LAN card, modulatedemodulate
Adjust the communications portion 709 of the network interface card of device etc..Communications portion 709 executes communication process via the network of such as internet.
Driver 710 is also connected to I/O interface 705 as needed.Detachable media 711, such as disk, CD, magneto-optic disk, semiconductor
Memory etc. is mounted on as needed on driver 710, in order to be pacified as needed from the computer program read thereon
It is packed into storage section 708.
In accordance with an embodiment of the present disclosure, it may be implemented as computer software journey above with reference to the method for flow chart description
Sequence.For example, embodiment of the disclosure includes a kind of computer program product comprising carry meter on a computer-readable medium
Calculation machine program, the computer program include the program code for method shown in execution flow chart.In such embodiments,
The computer program can be downloaded and installed from network by communications portion 709, and/or be pacified from detachable media 711
Dress.When the computer program is executed by processor 701, the above-mentioned function of limiting in the system of the embodiment of the present disclosure is executed.Root
According to embodiment of the disclosure, system as described above, unit, module, unit etc. can by computer program module come
It realizes.
It should be noted that computer-readable medium shown in the disclosure can be computer-readable signal media or meter
Calculation machine readable storage medium storing program for executing either the two any combination.Computer readable storage medium for example can be --- but not
Be limited to --- electricity, magnetic, optical, electromagnetic, infrared ray or semiconductor system, device or device, or any above combination.Meter
The more specific example of calculation machine readable storage medium storing program for executing can include but is not limited to:Electrical connection with one or more conducting wires, just
Taking formula computer disk, hard disk, random access storage device (RAM), read-only memory (ROM), erasable type may be programmed read-only storage
Device (EPROM or flash memory), optical fiber, portable compact disc read-only memory (CD-ROM), light storage device, magnetic memory device,
Or above-mentioned any appropriate combination.In the disclosure, computer readable storage medium can be it is any include or storage journey
The tangible medium of sequence, the program can be commanded execution system, device or device use or in connection.And at this
In open, computer-readable signal media may include in a base band or as the data-signal that carrier wave a part is propagated,
Wherein carry computer-readable program code.The data-signal of this propagation can take various forms, including but unlimited
In electromagnetic signal, optical signal or above-mentioned any appropriate combination.Computer-readable signal media can also be that computer can
Any computer-readable medium other than storage medium is read, which can send, propagates or transmit and be used for
By the use of instruction execution system, device or device or program in connection.Include on computer-readable medium
Program code can transmit with any suitable medium, including but not limited to:Wirelessly, electric wire, optical cable, RF etc. or above-mentioned
Any appropriate combination.In accordance with an embodiment of the present disclosure, computer-readable medium may include above-described ROM 702
And/or one or more memories other than RAM 703 and/or ROM 702 and RAM 703.
Flow chart and block diagram in attached drawing are illustrated according to the system of the various embodiments of the disclosure, method and computer journey
The architecture, function and operation in the cards of sequence product.In this regard, each box in flowchart or block diagram can generation
A part of one module, program segment or code of table, a part of above-mentioned module, program segment or code include one or more
Executable instruction for implementing the specified logical function.It should also be noted that in some implementations as replacements, institute in box
The function of mark can also occur in a different order than that indicated in the drawings.For example, two boxes succeedingly indicated are practical
On can be basically executed in parallel, they can also be executed in the opposite order sometimes, and this depends on the function involved.Also it wants
It is noted that the combination of each box in block diagram or flow chart and the box in block diagram or flow chart, can use and execute rule
The dedicated hardware based systems of fixed functions or operations is realized, or can use the group of specialized hardware and computer instruction
It closes to realize.
As on the other hand, the disclosure additionally provides a kind of computer-readable medium, which can be
Included in equipment described in above-described embodiment;It is also possible to individualism, and without in the supplying equipment.Above-mentioned calculating
Machine readable medium carries one or more program, when said one or multiple programs are executed by the equipment, makes
Obtain the sharing method for the logging state that the equipment is executed according to the embodiment of the present disclosure.This method includes:Reception carries cookie
User request, the cookie include the first alliance side Alliance Identity and transaction id;According to first in the cookie
The Alliance Identity of alliance side, verification be stored in the information of alliance's account information chain whether include the first alliance side alliance
Mark;If including determining other alliance sides relevant to the first alliance side according to the transaction id in the cookie
Alliance Identity is logged in, the login Alliance Identity is stored in account log-on message chain;Joined according to the login of other described alliance sides
Alliance mark, the logging state of the first alliance side is shared to other described alliance sides, wherein the first alliance side and other
Alliance side shares a login account.
Embodiment of the disclosure is described above.But the purpose that these embodiments are merely to illustrate that, and
It is not intended to limit the scope of the present disclosure.Although respectively describing each embodiment above, but it is not intended that each reality
Use cannot be advantageously combined by applying the measure in example.The scope of the present disclosure is defined by the appended claims and the equivalents thereof.It does not take off
From the scope of the present disclosure, those skilled in the art can make a variety of alternatives and modifications, these alternatives and modifications should all fall in this
Within scope of disclosure.
Claims (14)
1. a kind of sharing method of logging state, including:
The user's request for carrying cookie is received, the cookie includes the Alliance Identity and transaction id of the first alliance side;
According to the Alliance Identity of the first alliance side in the cookie, verification, which is stored in the information of alliance's account information chain, is
The no Alliance Identity including the first alliance side;
If including determining other alliance sides relevant to the first alliance side according to the transaction id in the cookie
Alliance Identity is logged in, the login Alliance Identity is stored in account log-on message chain;
According to the login Alliance Identity of other described alliance sides, the login of the first alliance side is shared to other described alliance sides
State, wherein the first alliance side and other alliance sides share a login account.
2. according to the method described in claim 1, wherein, this method further includes:
If not including the Alliance Identity of the first alliance side in the information for being stored in alliance's account information chain, to institute
It states the first alliance side and sends logging in again for task;
It receives the information that the first alliance side logins successfully again, and is inserted into logins and trades in order to by described first
The information that alliance side logins successfully again is synchronized to the account log-on message chain and alliance's account information chain respectively;
The information that is logined successfully again based on the first alliance side and the transaction id for logging in transaction, described in generation
Cookie, and send the cookie.
3. according to the method described in claim 1, wherein, according to the login Alliance Identity of other described alliance sides, to it is described its
The logging state that the first alliance side is shared by his alliance side further includes:
According to the information of forming an alliance of the login Alliance Identity of other described alliance sides and the first alliance side, from other described alliances
The allied member to form an alliance with the first alliance side is determined in side;
The logging state of the first alliance side is shared to the allied member to form an alliance with the first alliance side.
4. according to the method described in claim 3, wherein, sharing described to the allied member to form an alliance with the first alliance side
The logging state of one alliance side includes:
Whether the logging state for inquiring the first alliance side is online;
If be online, judge whether the time interval of the time for logging in the first alliance side and current time is big
In the out-of-service time;
If it is lower, sharing the logging state of the first alliance side to the allied member to form an alliance with the first alliance side.
5. according to the method described in claim 3, wherein, this method further includes:
When the login account is nullified or exited from the first alliance side by the user, by the cancellation or the letter exited
Breath is written in the cookies of information of all alliance sides comprising forming an alliance with the first alliance side.
6. method described in any one according to claim 1~5, wherein alliance's account information chain and the account are stepped on
Record information chain is block chain.
7. a kind of sharing means of logging state, including:
First receiving module, for receiving the user's request for carrying cookie, the cookie includes the connection of the first alliance side
Alliance's mark and transaction id;
Correction verification module, for the Alliance Identity according to the first alliance side in the cookie, verification is stored in alliance's account letter
Cease chain information in whether include the first alliance side Alliance Identity;
Determining module, if including, according to the transaction id in the cookie, determine it is relevant to the first alliance side other
The login Alliance Identity of alliance side, the login Alliance Identity are stored in account log-on message chain;
Sharing module shares described the to other described alliance sides for the login Alliance Identity according to other described alliance sides
The logging state of one alliance side, wherein the first alliance side and other alliance sides share a login account.
8. device according to claim 7, wherein the device further includes:
Sending module, if in the information for being stored in alliance's account information chain not including alliance's mark of the first alliance side
Know, then sends logging in again for task to the first alliance side;
Second receiving module, the information logined successfully again for receiving the first alliance side, and it is inserted into a login transaction
In order to which the information for logining successfully the first alliance side again is synchronized to the account log-on message chain and described respectively
Alliance's account information chain;
Generation module, information and the transaction id for logging in transaction for being logined successfully again based on the first alliance side,
The cookie is generated, and sends the cookie.
9. device according to claim 7, wherein according to the login Alliance Identity of other described alliance sides, to it is described its
The logging state that the first alliance side is shared by his alliance side further includes:
According to the information of forming an alliance of the login Alliance Identity of other described alliance sides and the first alliance side, from other described alliances
The allied member to form an alliance with the first alliance side is determined in side;
The logging state of the first alliance side is shared to the allied member to form an alliance with the first alliance side.
10. device according to claim 9, wherein shared described to the allied member to form an alliance with the first alliance side
The logging state of first alliance side includes:
Whether the logging state for inquiring the first alliance side is online;
If be online, judge whether the time interval of the time for logging in the first alliance side and current time is big
In the out-of-service time;
If it is lower, sharing the logging state of the first alliance side to the allied member to form an alliance with the first alliance side.
11. device according to claim 9, wherein the device further includes:
Writing module, when the login account is nullified or exited from the first alliance side by the user, by the cancellation
Or the information exited is written in the cookies of information of all alliance sides comprising forming an alliance with the first alliance side.
12. according to device described in claim 7~11 any one, wherein alliance's account information chain and the account
Log-on message chain is block chain.
13. a kind of electronic equipment, including:
One or more processors;And
Storage device, for storing one or more programs,
Wherein, when one or more of programs are executed by one or more of processors, so that one or more of
Processor executes method described in any one according to claim 1~6.
14. a kind of computer-readable medium, is stored thereon with executable instruction, which hold processor when being executed by processor
Method described in capable any one according to claim 1~6.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201811183437.8A CN108900562B (en) | 2018-10-11 | 2018-10-11 | Login state sharing method and device, electronic equipment and medium |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201811183437.8A CN108900562B (en) | 2018-10-11 | 2018-10-11 | Login state sharing method and device, electronic equipment and medium |
Publications (2)
Publication Number | Publication Date |
---|---|
CN108900562A true CN108900562A (en) | 2018-11-27 |
CN108900562B CN108900562B (en) | 2021-07-20 |
Family
ID=64360368
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CN201811183437.8A Active CN108900562B (en) | 2018-10-11 | 2018-10-11 | Login state sharing method and device, electronic equipment and medium |
Country Status (1)
Country | Link |
---|---|
CN (1) | CN108900562B (en) |
Cited By (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN110659463A (en) * | 2019-08-23 | 2020-01-07 | 苏州浪潮智能科技有限公司 | Distributed operation method and device of stateless system |
CN113778832A (en) * | 2021-09-28 | 2021-12-10 | 京东方科技集团股份有限公司 | Device information processing method and device, readable storage medium and electronic device |
WO2022001717A1 (en) * | 2020-06-30 | 2022-01-06 | 京东科技信息技术有限公司 | Blockchain-based user information processing method and system |
CN114679302A (en) * | 2022-03-01 | 2022-06-28 | 中信百信银行股份有限公司 | Method, device, equipment and storage medium for docking single sign-on system |
Citations (12)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN105450637A (en) * | 2015-11-09 | 2016-03-30 | 歌尔声学股份有限公司 | Single sign-on method and device for multiple application systems |
US20160210626A1 (en) * | 2015-01-19 | 2016-07-21 | Royal Bank Of Canada | Secure processing of electronic payments |
CN105827658A (en) * | 2016-05-30 | 2016-08-03 | 无锡天脉聚源传媒科技有限公司 | Method and device for multi-application synchronization login |
US20170017936A1 (en) * | 2015-07-14 | 2017-01-19 | Fmr Llc | Point-to-Point Transaction Guidance Apparatuses, Methods and Systems |
CN106790252A (en) * | 2017-01-24 | 2017-05-31 | 北京奇虎科技有限公司 | Log-on message sharing method and device |
WO2018044282A1 (en) * | 2016-08-30 | 2018-03-08 | Visa International Service Association | Biometric identification and verification among iot devices and applications |
CN108023881A (en) * | 2017-12-04 | 2018-05-11 | 泰康保险集团股份有限公司 | Login method, device, medium and the electronic equipment of application program |
KR101857223B1 (en) * | 2017-11-13 | 2018-05-11 | 주식회사 온더 | Method and system for user identification based block chain token |
CN108156159A (en) * | 2017-12-27 | 2018-06-12 | 质数链网科技成都有限公司 | A kind of multi-application system login method and block chain distribution general ledger system |
CN108173850A (en) * | 2017-12-28 | 2018-06-15 | 杭州趣链科技有限公司 | A kind of identity authorization system and identity identifying method based on block chain intelligence contract |
CN108235805A (en) * | 2017-12-29 | 2018-06-29 | 深圳前海达闼云端智能科技有限公司 | Account unifying method and device and storage medium |
CN108551437A (en) * | 2018-03-13 | 2018-09-18 | 百度在线网络技术(北京)有限公司 | Method and apparatus for authentication information |
-
2018
- 2018-10-11 CN CN201811183437.8A patent/CN108900562B/en active Active
Patent Citations (12)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20160210626A1 (en) * | 2015-01-19 | 2016-07-21 | Royal Bank Of Canada | Secure processing of electronic payments |
US20170017936A1 (en) * | 2015-07-14 | 2017-01-19 | Fmr Llc | Point-to-Point Transaction Guidance Apparatuses, Methods and Systems |
CN105450637A (en) * | 2015-11-09 | 2016-03-30 | 歌尔声学股份有限公司 | Single sign-on method and device for multiple application systems |
CN105827658A (en) * | 2016-05-30 | 2016-08-03 | 无锡天脉聚源传媒科技有限公司 | Method and device for multi-application synchronization login |
WO2018044282A1 (en) * | 2016-08-30 | 2018-03-08 | Visa International Service Association | Biometric identification and verification among iot devices and applications |
CN106790252A (en) * | 2017-01-24 | 2017-05-31 | 北京奇虎科技有限公司 | Log-on message sharing method and device |
KR101857223B1 (en) * | 2017-11-13 | 2018-05-11 | 주식회사 온더 | Method and system for user identification based block chain token |
CN108023881A (en) * | 2017-12-04 | 2018-05-11 | 泰康保险集团股份有限公司 | Login method, device, medium and the electronic equipment of application program |
CN108156159A (en) * | 2017-12-27 | 2018-06-12 | 质数链网科技成都有限公司 | A kind of multi-application system login method and block chain distribution general ledger system |
CN108173850A (en) * | 2017-12-28 | 2018-06-15 | 杭州趣链科技有限公司 | A kind of identity authorization system and identity identifying method based on block chain intelligence contract |
CN108235805A (en) * | 2017-12-29 | 2018-06-29 | 深圳前海达闼云端智能科技有限公司 | Account unifying method and device and storage medium |
CN108551437A (en) * | 2018-03-13 | 2018-09-18 | 百度在线网络技术(北京)有限公司 | Method and apparatus for authentication information |
Cited By (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN110659463A (en) * | 2019-08-23 | 2020-01-07 | 苏州浪潮智能科技有限公司 | Distributed operation method and device of stateless system |
CN110659463B (en) * | 2019-08-23 | 2021-11-12 | 苏州浪潮智能科技有限公司 | Distributed operation method and device of stateless system |
WO2022001717A1 (en) * | 2020-06-30 | 2022-01-06 | 京东科技信息技术有限公司 | Blockchain-based user information processing method and system |
CN113778832A (en) * | 2021-09-28 | 2021-12-10 | 京东方科技集团股份有限公司 | Device information processing method and device, readable storage medium and electronic device |
CN113778832B (en) * | 2021-09-28 | 2024-05-14 | 京东方科技集团股份有限公司 | Device information processing method and device, readable storage medium and electronic device |
CN114679302A (en) * | 2022-03-01 | 2022-06-28 | 中信百信银行股份有限公司 | Method, device, equipment and storage medium for docking single sign-on system |
CN114679302B (en) * | 2022-03-01 | 2024-05-10 | 中信百信银行股份有限公司 | Method, device, equipment and storage medium for docking single sign-on system |
Also Published As
Publication number | Publication date |
---|---|
CN108900562B (en) | 2021-07-20 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CN108900562A (en) | Sharing method, device, electronic equipment and the medium of logging state | |
JP2020198127A (en) | Communication delay leveling device, method, and system | |
JP6682514B2 (en) | System and method for semi-open market | |
AU2019203081A1 (en) | Techniques for facilitating electronic trading | |
US8868786B1 (en) | Apparatus, systems and methods for transformation services | |
US10580038B2 (en) | Systems and methods for leveraging social queuing to identify and prevent ticket purchaser simulation | |
CN105556919B (en) | Dual factor anthentication is carried out using service request bill | |
CN109146490A (en) | block generation method, device and system | |
JP2018516417A (en) | Payment method, apparatus and system | |
CN111556153B (en) | Information processing method, apparatus, device and medium executed by first server | |
AU2019301479A1 (en) | Peer-to-peer money transfers | |
CN112583834B (en) | Method and device for single sign-on through gateway | |
CN110401630A (en) | Verification method, device, electronic equipment and the medium of transaction certificate | |
CN112329049A (en) | Business data management method, device, electronic equipment and medium | |
CN110516463A (en) | Method and apparatus for generating information | |
CN110223179A (en) | The data processing method of fund, device, system, medium | |
CN109150898A (en) | Method and apparatus for handling information | |
CN108390878A (en) | Method, apparatus for verifying network request safety | |
US10861036B2 (en) | Systems and methods for randomized reward distribution exchange for loyalty points | |
CN109272318B (en) | Resource flow transaction method, device, equipment and medium applied to requester client | |
CN113079085B (en) | Business service interaction method, business service interaction device, business service interaction equipment and storage medium | |
CN108141434B (en) | Providing multi-factor authentication credentials via device notifications | |
CN113761586A (en) | Method and device for randomly sampling and inspecting articles based on block chain | |
CN109787937A (en) | Method of counting, device and the server of access times | |
CN108898446A (en) | Method and apparatus for output information |
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 |