CN112202836A - Method, system, terminal and storage medium for maintaining client session information - Google Patents
Method, system, terminal and storage medium for maintaining client session information Download PDFInfo
- Publication number
- CN112202836A CN112202836A CN202010922071.2A CN202010922071A CN112202836A CN 112202836 A CN112202836 A CN 112202836A CN 202010922071 A CN202010922071 A CN 202010922071A CN 112202836 A CN112202836 A CN 112202836A
- Authority
- CN
- China
- Prior art keywords
- client
- session
- identification
- identifier
- unique
- 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.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 33
- 230000006870 function Effects 0.000 claims description 8
- 238000004590 computer program Methods 0.000 claims description 3
- 235000014510 cooky Nutrition 0.000 description 19
- 238000005516 engineering process Methods 0.000 description 9
- 238000004891 communication Methods 0.000 description 5
- 238000010586 diagram Methods 0.000 description 5
- 230000008878 coupling Effects 0.000 description 3
- 238000010168 coupling process Methods 0.000 description 3
- 238000005859 coupling reaction Methods 0.000 description 3
- 230000003287 optical effect Effects 0.000 description 3
- 238000006467 substitution reaction Methods 0.000 description 3
- 230000000694 effects Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 230000008569 process Effects 0.000 description 2
- 238000012545 processing Methods 0.000 description 2
- 230000004044 response Effects 0.000 description 2
- 230000003068 static effect Effects 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000007812 deficiency Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 239000000284 extract Substances 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/14—Session management
- H04L67/143—Termination or inactivation of sessions, e.g. event-controlled end of session
- H04L67/145—Termination or inactivation of sessions, e.g. event-controlled end of session avoiding end of session, e.g. keep-alive, heartbeats, resumption message or wake-up for inactive or interrupted session
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/60—Protecting data
- G06F21/62—Protecting access to data via a platform, e.g. using keys or access control rules
- G06F21/6209—Protecting access to data via a platform, e.g. using keys or access control rules to a single file or object, e.g. in a secure envelope, encrypted and accessed using a key, or with access control rules appended to the object itself
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/60—Protecting data
- G06F21/64—Protecting data integrity, e.g. using checksums, certificates or signatures
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/14—Session management
- H04L67/146—Markers for unambiguous identification of a particular session, e.g. session cookie or URL-encoding
Abstract
The invention provides a method, a system, a terminal and a storage medium for maintaining client session information, which comprises the following steps: adding the preset unique client identifier to a request protocol of the client; extracting the unique identification from a request protocol sent by the client; judging whether an identifier matched with the unique identifier of the client exists locally: if yes, calling session information under the matching identification; if not, establishing a session storage file for the client according to the unique identifier of the client. The invention can ensure high data security and can still keep the previous session information after closing the browser.
Description
Technical Field
The present invention relates to the field of session technologies, and in particular, to a method, a system, a terminal, and a storage medium for maintaining client session information.
Background
When most websites need to log in, user names and passwords are stored, and when the e-commerce platform is not logged in, the session technology is used for adding the shopping cart function.
The Session technology is mainly used for client side technology (Cookie) and user storage technology (Session). A Cookie is actually a short piece of textual information. The client requests the server and issues a Cookie (written in the response header) to the client browser using response if the server needs to record the user state. The client browser will save the Cookie. When the browser requests the website again, the browser submits the requested website to the server together with the Cookie. The server checks the Cookie to identify the user status. Cookies are actually classified into two types: one is in the process of being stored in the browser, and the other is stored on the hard disk.
The working principle of Cookie can be summarized to issue a pass for client sides, one for each person, and the pass must be carried by anyone for access. The server can then confirm the identity of the client from the pass.
Session is another mechanism for recording client state, based on cookies, except that cookies are stored in a client browser, and Session is stored on a server. When the client browser accesses the server, the server records the client information on the server in a certain form, namely Session, and simultaneously writes Cookie information into the client. When the client browser accesses again, the state of the client only needs to be searched from the Session of the server through the Cookie information.
The operating principle of Session can be summarized as a client profile which is established on the server by a program, and the client only needs to query a client profile table when visiting. The system is equivalent to a customer information table of a barber shop, a page of personal information table is added after the barber shop transacts a card for the first time, and when you consume each time and do what items, which master can choose to store the information in the table for you to do, you can inquire the information at any time only by the id on the membership card of the master, and you can inquire the information at any time when consuming in the shop (equivalent to use in the conversation).
However, cookies are stored on the client side, and inherent security weaknesses exist. And confidential information such as user names, passwords, credit card numbers, etc. may be stored in the Cookie. The client will not retain this information after the Cookie is disabled, so these security concerns will not exist. But if cookies are not used, the session cannot be saved.
The existing solution is to adopt a technology called URL rewriting, namely, session id is attached to the back of a URL path, and there are two attaching modes, one is used as additional information of the URL path, and the other is used as a query character string attached to the back of the URL. The network remains in state throughout the interaction and must include this session id after the path that each client may request. The disadvantage is that there is no static page in the web page, otherwise the rewriting cannot be done. Still another way to carry the session id as a hidden form is to interpret the two as a difference between get and post, which has the disadvantage that it can only be used when each page is dynamically generated with form submission.
Disclosure of Invention
In view of the above-mentioned deficiencies of the prior art, the present invention provides a method, a system, a terminal and a storage medium for maintaining session information of a client, so as to solve the above-mentioned technical problems.
In a first aspect, the present invention provides a method for maintaining session information of a client, including:
adding the preset unique client identifier to a request protocol of the client;
extracting the unique identification from a request protocol sent by the client;
judging whether an identifier matched with the unique identifier of the client exists locally:
if yes, calling session information under the matching identification;
if not, establishing a session storage file for the client according to the unique identifier of the client.
Further, the method further comprises:
setting an identification format, wherein the identification format comprises a function classification number and a random number;
and distributing the identification formats to each client, and generating respective unique identification by each client according to the identification formats.
Further, the method further comprises:
classifying the clients according to the attribute information of the clients, and setting classification numbers of different classes;
and issuing the classification number to the client side of the corresponding classification.
Further, the retrieving session information under the matching identifier includes:
calling a session storage archive corresponding to the matching identifier, and returning session information in the corresponding session storage archive to the client;
and storing the newly added session information of the client into the corresponding session storage archive.
In a second aspect, the present invention provides a system for maintaining client session information, comprising:
the identification adding unit is configured to add the preset unique client identification to a request protocol of the client;
the identification extracting unit is configured to extract the unique identification from a request protocol sent by the client;
and the identification matching unit is configured to judge whether an identification matched with the unique identification of the client exists locally:
the session calling unit is configured to call session information under the matched identifier if the identifier matched with the unique identifier of the client exists locally;
and the archive establishing unit is configured to establish a session storage archive for the client according to the unique identifier of the client if the identifier matched with the unique identifier of the client does not exist locally.
Further, the system further comprises:
the format setting unit is configured for setting an identification format, and the identification format comprises a function classification number and a random number;
and the format distribution unit is configured to distribute the identification formats to the clients, and the clients generate respective unique identifications according to the identification formats.
Further, the system further comprises:
the category setting unit is configured for classifying the clients according to the client attribute information and setting classification numbers of different categories;
and the category issuing unit is configured to issue the category number to the client of the corresponding category.
Further, the session scheduling unit includes:
the session returning module is configured to call the session storage archive corresponding to the matching identifier and return the session information in the corresponding session storage archive to the client;
and the session storage module is configured to store the newly added session information of the client into the corresponding session storage archive.
In a third aspect, a terminal is provided, including:
a processor, a memory, wherein,
the memory is used for storing a computer program which,
the processor is used for calling and running the computer program from the memory so as to make the terminal execute the method of the terminal.
In a fourth aspect, a computer storage medium is provided having stored therein instructions that, when executed on a computer, cause the computer to perform the method of the above aspects.
The beneficial effect of the invention is that,
according to the method, the system, the terminal and the storage medium for maintaining the client session information, the unique identifier of the client is added in the HTTP/HTTPS request of the client, the unique identifier is transmitted by means of the request header in the HTTP/HTTPS protocol to realize the discrimination of the client, and compared with the current method that the URL technology is rewritten, the method, the system and the terminal can still maintain the previous session information after the browser is closed. The invention can ensure high data security and can still keep the previous session information after closing the browser.
In addition, the invention has reliable design principle, simple structure and very wide application prospect.
Drawings
In order to more clearly illustrate the embodiments or technical solutions in the prior art of the present invention, the drawings used in the description of the embodiments or prior art will be briefly described below, and it is obvious for those skilled in the art that other drawings can be obtained based on these drawings without creative efforts.
FIG. 1 is a schematic flow diagram of a method of one embodiment of the invention.
FIG. 2 is a schematic block diagram of a system of one embodiment of the present invention.
Fig. 3 is a schematic structural diagram of a terminal according to an embodiment of the present invention.
Detailed Description
In order to make those skilled in the art better understand the technical solution of the present invention, the technical solution in the embodiment of the present invention will be clearly and completely described below with reference to the drawings in the embodiment of the present invention, and it is obvious that the described embodiment is only a part of the embodiment of the present invention, and not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
The following explains key terms appearing in the present invention.
Cookie is client technology, and the server writes data of each user to the respective browser of the user in the form of Cookie. When the user uses the browser to access the web resource in the server, the user takes the respective data.
Session is used to store information about a user (understood that a client/browser could also be) Session. The Session variable holds information that is single user and can be used for all pages in an application. The approximate flow is as follows: the user opens the browser to access the website, the session ID is generated in the cookie of the browser, the session ID is automatically brought up when the user requests the website, and then the server side finds the corresponding session value according to the session ID. The session ID is equivalent to a key, the place where the session is stored on the server is equivalent to a cabinet, and the user can only take the key to open the cabinet to take the things of the user. session generally stores user-related information, such as user login status, authority control, and other information may be stored. In addition, sessionID is generated whether the user on your site is logged in or not.
FIG. 1 is a schematic flow diagram of a method of one embodiment of the invention. The execution subject in fig. 1 may be a system for maintaining session information of a client.
As shown in fig. 1, the method includes:
and 150, if not, establishing a session storage file for the client according to the unique identifier of the client.
Specifically, the method for maintaining the session information of the client includes:
and S1, adding the preset unique client identification to the request protocol of the client.
Firstly, setting a format of the unique identifier, wherein the format can be set by a client, for example, classifying the client according to the service category of the client, setting classification numbers of various categories, and distributing the classification numbers to the clients of corresponding categories. The number of bits of the random number is specified, the client generates a random number with a specified number of bits (such as 6 bits), and the classification number + the random number is used as a unique identifier of the client, for example: userId jfajkht @ rvtuesv @ # lf3920404 (unique identifier).
And adding the generated unique identifier to a request header (message header) of the client to the HTTP/HTTPS protocol, wherein the position of the unique identifier in the request header of the HTTP/HTTPS protocol is preset.
And S2, extracting the unique identification from the request protocol sent by the client.
And after receiving the request sent by the client, the server extracts the unique identifier from the request header according to the preset position.
S3, judging whether an identifier matched with the unique identifier of the client exists locally: if yes, calling session information under the matching identification; if not, establishing a session storage file for the client according to the unique identifier of the client.
The server judges whether the unique identifier extracted in step S2 has the same matching identifier locally, and if so, invokes a session storage archive corresponding to the matching identifier, returns session information in the corresponding session storage archive to the client, and stores new session information of the client in the corresponding session storage archive. And if the matching identification does not exist, establishing a session storage file for the client according to the extracted unique identification of the client.
As shown in fig. 2, the system 200 includes:
an identifier adding unit 210 configured to add the preset unique client identifier to a request protocol of the client;
an identifier extracting unit 220 configured to extract the unique identifier from a request protocol sent by the client;
an identifier matching unit 230 configured to determine whether an identifier matching the client unique identifier exists locally:
a session retrieving unit 240, configured to, if an identifier matching the unique client identifier exists locally, retrieve session information under the matching identifier;
the archive establishing unit 250 is configured to establish a session storage archive for the client according to the unique identifier of the client if there is no identifier matching with the unique identifier of the client locally.
Optionally, as an embodiment of the present invention, the system further includes:
the format setting unit is configured for setting an identification format, and the identification format comprises a function classification number and a random number;
and the format distribution unit is configured to distribute the identification formats to the clients, and the clients generate respective unique identifications according to the identification formats.
Optionally, as an embodiment of the present invention, the system further includes:
the category setting unit is configured for classifying the clients according to the client attribute information and setting classification numbers of different categories;
and the category issuing unit is configured to issue the category number to the client of the corresponding category.
Optionally, as an embodiment of the present invention, the session scheduling unit includes:
the session returning module is configured to call the session storage archive corresponding to the matching identifier and return the session information in the corresponding session storage archive to the client;
and the session storage module is configured to store the newly added session information of the client into the corresponding session storage archive.
Fig. 3 is a schematic structural diagram of a terminal 300 according to an embodiment of the present invention, where the terminal 300 may be configured to execute the method for maintaining client session information according to the embodiment of the present invention.
Among them, the terminal 300 may include: a processor 310, a memory 320, and a communication unit 330. The components communicate via one or more buses, and those skilled in the art will appreciate that the architecture of the servers shown in the figures is not intended to be limiting, and may be a bus architecture, a star architecture, a combination of more or less components than those shown, or a different arrangement of components.
The memory 320 may be used for storing instructions executed by the processor 310, and the memory 320 may be implemented by any type of volatile or non-volatile storage terminal or combination thereof, such as Static Random Access Memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic disk or optical disk. The executable instructions in memory 320, when executed by processor 310, enable terminal 300 to perform some or all of the steps in the method embodiments described below.
The processor 310 is a control center of the storage terminal, connects various parts of the entire electronic terminal using various interfaces and lines, and performs various functions of the electronic terminal and/or processes data by operating or executing software programs and/or modules stored in the memory 320 and calling data stored in the memory. The processor may be composed of an Integrated Circuit (IC), for example, a single packaged IC, or a plurality of packaged ICs connected with the same or different functions. For example, the processor 310 may include only a Central Processing Unit (CPU). In the embodiment of the present invention, the CPU may be a single operation core, or may include multiple operation cores.
A communication unit 330, configured to establish a communication channel so that the storage terminal can communicate with other terminals. And receiving user data sent by other terminals or sending the user data to other terminals.
The present invention also provides a computer storage medium, wherein the computer storage medium may store a program, and the program may include some or all of the steps in the embodiments provided by the present invention when executed. The storage medium may be a magnetic disk, an optical disk, a read-only memory (ROM) or a Random Access Memory (RAM).
Therefore, the unique identifier of the client is added in the HTTP/HTTPS request of the client, the unique identifier is transmitted by means of the request header in the HTTP/HTTPS protocol to realize the discrimination of the client, and compared with the prior art that the URL technology is rewritten, the method can still keep the previous session information after the browser is closed. The invention can ensure high data security, can still keep the previous session information after closing the browser, and has the technical effects that the technical effects can be achieved by the embodiment can be described in the above, and are not described again here.
Those skilled in the art will readily appreciate that the techniques of the embodiments of the present invention may be implemented as software plus a required general purpose hardware platform. Based on such understanding, the technical solutions in the embodiments of the present invention may be embodied in the form of a software product, where the computer software product is stored in a storage medium, such as a usb disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and the like, and the storage medium can store program codes, and includes instructions for enabling a computer terminal (which may be a personal computer, a server, or a second terminal, a network terminal, and the like) to perform all or part of the steps of the method in the embodiments of the present invention.
The same and similar parts in the various embodiments in this specification may be referred to each other. Especially, for the terminal embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant points can be referred to the description in the method embodiment.
In the embodiments provided in the present invention, it should be understood that the disclosed system and method can be implemented in other ways. For example, the above-described system embodiments are merely illustrative, and for example, the division of the units is only one logical functional division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, systems or units, and may be in an electrical, mechanical or other form.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
In addition, functional units in the embodiments of the present invention may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit.
Although the present invention has been described in detail by referring to the drawings in connection with the preferred embodiments, the present invention is not limited thereto. Various equivalent modifications or substitutions can be made on the embodiments of the present invention by those skilled in the art without departing from the spirit and scope of the present invention, and these modifications or substitutions are within the scope of the present invention/any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present invention. Therefore, the protection scope of the present invention shall be subject to the protection scope of the claims.
Claims (10)
1. A method for maintaining client session information, comprising:
adding the preset unique client identifier to a request protocol of the client;
extracting the unique identification from a request protocol sent by the client;
judging whether an identifier matched with the unique identifier of the client exists locally:
if yes, calling session information under the matching identification;
if not, establishing a session storage file for the client according to the unique identifier of the client.
2. The method of claim 1, further comprising:
setting an identification format, wherein the identification format comprises a function classification number and a random number;
and distributing the identification formats to each client, and generating respective unique identification by each client according to the identification formats.
3. The method of claim 2, further comprising:
classifying the clients according to the attribute information of the clients, and setting classification numbers of different classes;
and issuing the classification number to the client side of the corresponding classification.
4. The method of claim 1, wherein the retrieving session information that matches the identity comprises:
calling a session storage archive corresponding to the matching identifier, and returning session information in the corresponding session storage archive to the client;
and storing the newly added session information of the client into the corresponding session storage archive.
5. A system for maintaining client session information, comprising:
the identification adding unit is configured to add the preset unique client identification to a request protocol of the client;
the identification extracting unit is configured to extract the unique identification from a request protocol sent by the client;
and the identification matching unit is configured to judge whether an identification matched with the unique identification of the client exists locally:
the session calling unit is configured to call session information under the matched identifier if the identifier matched with the unique identifier of the client exists locally;
and the archive establishing unit is configured to establish a session storage archive for the client according to the unique identifier of the client if the identifier matched with the unique identifier of the client does not exist locally.
6. The system of claim 5, further comprising:
the format setting unit is configured for setting an identification format, and the identification format comprises a function classification number and a random number;
and the format distribution unit is configured to distribute the identification formats to the clients, and the clients generate respective unique identifications according to the identification formats.
7. The system of claim 6, further comprising:
the category setting unit is configured for classifying the clients according to the client attribute information and setting classification numbers of different categories;
and the category issuing unit is configured to issue the category number to the client of the corresponding category.
8. The system of claim 5, wherein the session scheduling unit comprises:
the session returning module is configured to call the session storage archive corresponding to the matching identifier and return the session information in the corresponding session storage archive to the client;
and the session storage module is configured to store the newly added session information of the client into the corresponding session storage archive.
9. A terminal, comprising:
a processor;
a memory for storing instructions for execution by the processor;
wherein the processor is configured to perform the method of any one of claims 1-4.
10. A computer-readable storage medium, in which a computer program is stored which, when being executed by a processor, carries out the method according to any one of claims 1-4.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010922071.2A CN112202836A (en) | 2020-09-04 | 2020-09-04 | Method, system, terminal and storage medium for maintaining client session information |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010922071.2A CN112202836A (en) | 2020-09-04 | 2020-09-04 | Method, system, terminal and storage medium for maintaining client session information |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112202836A true CN112202836A (en) | 2021-01-08 |
Family
ID=74005309
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010922071.2A Pending CN112202836A (en) | 2020-09-04 | 2020-09-04 | Method, system, terminal and storage medium for maintaining client session information |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112202836A (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113259429A (en) * | 2021-05-11 | 2021-08-13 | 鸬鹚科技(深圳)有限公司 | Session keeping control method, device, computer equipment and medium |
| CN113452948A (en) * | 2021-06-28 | 2021-09-28 | 苏州科达科技股份有限公司 | Conference terminal control method, conference terminal control device, conference terminal equipment and storage medium |
Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104811488A (en) * | 2015-04-13 | 2015-07-29 | 深信服网络科技（深圳）有限公司 | Load balancing equipment-based session keeping method and system and load balancing equipment |
-
2020
- 2020-09-04 CN CN202010922071.2A patent/CN112202836A/en active Pending
Patent Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104811488A (en) * | 2015-04-13 | 2015-07-29 | 深信服网络科技（深圳）有限公司 | Load balancing equipment-based session keeping method and system and load balancing equipment |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113259429A (en) * | 2021-05-11 | 2021-08-13 | 鸬鹚科技(深圳)有限公司 | Session keeping control method, device, computer equipment and medium |
| CN113259429B (en) * | 2021-05-11 | 2023-12-05 | 鸬鹚科技(深圳)有限公司 | Session maintenance management and control method, device, computer equipment and medium |
| CN113452948A (en) * | 2021-06-28 | 2021-09-28 | 苏州科达科技股份有限公司 | Conference terminal control method, conference terminal control device, conference terminal equipment and storage medium |
| CN113452948B (en) * | 2021-06-28 | 2022-07-26 | 苏州科达科技股份有限公司 | Conference terminal control method, device, equipment and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US9948629B2 (en) | Systems and methods of sharing information through a tag-based consortium | |
| US7996491B2 (en) | Personal criteria verification using fractional information | |
| CN108769041A (en) | Login method, system, computer equipment and storage medium | |
| US6983379B1 (en) | Method and system for monitoring online behavior at a remote site and creating online behavior profiles | |
| TWI227986B (en) | Device independent authentication system and method | |
| CN101127108B (en) | Method for accessing a information source via a computer system | |
| CN110430288B (en) | Node access method, node access device, computer equipment and storage medium | |
| CN108701309A (en) | A kind of distributed user profile authentication system for security of e-commerce transactions | |
| CN108108973A (en) | Business risk control method and device | |
| CN110688662A (en) | Sensitive data desensitization and inverse desensitization method and electronic equipment | |
| JPH1027036A (en) | Time-limited use charging system for internet | |
| EP2673708A2 (en) | DISTINGUISH VALID USERS FROM BOTS, OCRs AND THIRD PARTY SOLVERS WHEN PRESENTING CAPTCHA | |
| CN110096551A (en) | Credit data storage method, device, equipment and medium based on block chain | |
| KR100786478B1 (en) | System and Apparatus for verifing authenticity of a person useing customer behavior analysis information | |
| CN112202836A (en) | Method, system, terminal and storage medium for maintaining client session information | |
| CN109257321A (en) | Safe login method and device | |
| US20040250109A1 (en) | Secure Messaging Center | |
| CN108965291A (en) | Registration login method, system and the computer equipment of mixed application | |
| CN107644263A (en) | Method and server are handled in banking reservation | |
| CN111475365A (en) | Label type AB testing method and system based on cookie | |
| CN114513350A (en) | Identity verification method, system and storage medium | |
| JP3822474B2 (en) | Personal information integrated management system and program thereof, and medium storing the program | |
| CN103107976A (en) | Content provider/service provider (CP/SP) user identification authentication method and system and authentication support device | |
| CN105184559A (en) | System and method for payment | |
| US9723017B1 (en) | Method, apparatus and computer program product for detecting risky communications |
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 | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20210108 |
|
| RJ01 | Rejection of invention patent application after publication |