CN108076149B - Session maintaining method and device - Google Patents
Session maintaining method and device Download PDFInfo
- Publication number
- CN108076149B CN108076149B CN201711350621.2A CN201711350621A CN108076149B CN 108076149 B CN108076149 B CN 108076149B CN 201711350621 A CN201711350621 A CN 201711350621A CN 108076149 B CN108076149 B CN 108076149B
- Authority
- CN
- China
- Prior art keywords
- specific field
- field
- keyword
- response
- request
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
-
- 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/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
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Health & Medical Sciences (AREA)
- Cardiology (AREA)
- General Health & Medical Sciences (AREA)
- Computer And Data Communications (AREA)
Abstract
The application provides a session maintaining method and a session maintaining device, which are applied to load balancing equipment and comprise the following steps: when a request message sent by a client is received, matching a first designated field in the request message with a preset request keyword; when a response message sent by a first service end is received, matching a second specified field in the response message with a preset response keyword; when the first specified field is matched with the request keyword and the second specified field is matched with the response keyword, extracting a first specific field from the request message based on a preset first extraction strategy, and extracting a second specific field from the response message based on a preset second extraction strategy; judging whether the first specific field is matched with the second specific field; and if the first specific field is matched with the second specific field, forwarding the request message sent by the client to the first service terminal. The technical scheme of the application can improve the efficiency and the safety of the service processing of the server.
Description
Technical Field
The present application relates to the field of communications technologies, and in particular, to a session maintaining method and apparatus.
Background
With the rapid development of networks, load balancing equipment is widely applied to a server cluster in a distributed system architecture, and the traffic of each client is distributed to each server based on a built-in scheduling algorithm. However, when load balancing is performed, the load balancing device usually further adopts a session maintenance mechanism, that is, traffic of the same client is distributed to the same server, so as to improve continuity and stability of user services.
In the related art, the load balancing device may use the database, that is, store all session information in the database to realize sharing of session information between different service terminals, and determine a service terminal for session maintenance through the database, but this increases the database load, thereby affecting the service processing efficiency. Alternatively, the load balancing device may also use a cookie, that is, store session information into the cookie, and subsequently determine a server for session maintenance through the cookie.
Disclosure of Invention
In view of this, the present application provides a session maintaining method and apparatus to improve efficiency and security of service processing.
Specifically, the method is realized through the following technical scheme:
in a first aspect, the present application provides a session holding method, where the method is applied to a load balancing device, and the method includes:
when a request message sent by a client is received, matching a first designated field in the request message with a preset request keyword;
when a response message sent by a first service end is received, matching a second specified field in the response message with a preset response keyword;
when the first specified field is matched with the request keyword and the second specified field is matched with the response keyword, extracting a first specific field from the request message based on a preset first extraction strategy, and extracting a second specific field from the response message based on a preset second extraction strategy;
judging whether the first specific field is matched with the second specific field;
and if the first specific field is matched with the second specific field, forwarding the request message sent by the client to the first service terminal.
In a second aspect, the present application provides a session holding apparatus, which is applied to a load balancing device, and includes:
the first matching unit is used for matching a first designated field in a request message with a preset request keyword when the request message sent by a client is received;
the second matching unit is used for matching a second specified field in the response message with a preset response keyword when the response message sent by the first service end is received;
an extracting unit, configured to extract a first specific field from the request message based on a preset first extraction policy and extract a second specific field from the response message based on a preset second extraction policy when the first specific field is matched with the request keyword and the second specific field is matched with the response keyword;
the judging unit is used for judging whether the first specific field is matched with the second specific field;
and the forwarding unit is used for forwarding the request message sent by the client to the first service terminal when the first specific field is matched with the second specific field.
By analyzing the technical scheme, the application provides a new session maintenance implementation method, and session maintenance is not required to be implemented by using a database or a cookie. Compared with the related technology, the technical scheme of the application can improve the continuity and stability of the user service and can also improve the efficiency and the safety of service processing of the server.
Drawings
FIG. 1 is a flow chart illustrating a session maintenance method according to an exemplary embodiment of the present application;
FIG. 2 is a diagram of a hardware configuration of a device in which a session holding apparatus is located according to an exemplary embodiment of the present application;
fig. 3 is a block diagram of a session-holding device according to an exemplary embodiment of the present application.
Detailed Description
Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, like numbers in different drawings represent the same or similar elements unless otherwise indicated. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present application. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present application, as detailed in the appended claims.
The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the application. As used in this application and the appended claims, the singular forms "a", "an", and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that the term "and/or" as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items.
It is to be understood that although the terms first, second, third, etc. may be used herein to describe various information, such information should not be limited to these terms. These terms are only used to distinguish one type of information from another. For example, first information may also be referred to as second information, and similarly, second information may also be referred to as first information, without departing from the scope of the present application. The word "if" as used herein may be interpreted as "at … …" or "when … …" or "in response to a determination", depending on the context.
Referring to fig. 1, a flowchart of a session holding method according to an exemplary embodiment of the present application is shown. The method can be applied to a load balancing device, and can comprise the following steps:
step 101: when a request message sent by a client is received, matching a first designated field in the request message with a preset request keyword.
Step 102: when a response message sent by a first service end is received, matching a second specified field in the response message with a preset response keyword.
In this embodiment, a user may first analyze the service executed by each client by himself, and determine a client that needs to perform session maintenance on the client. In addition, the user can also determine the server side for conversation maintenance.
The load balancing device may provide a user interface through which a user may set a request keyword in a request message sent by the user for a client that needs session maintenance, and set a response keyword in a response message sent by the user for a server that participates in session maintenance. The request keyword may be an HTTP (HyperText Transfer Protocol) header name and HTTP content in the message content of the request message, and the response keyword may be an HTTP header name and HTTP content in the message content of the response message. It should be noted that the same request keyword corresponds to clients of the same category, and such clients generally have the same model or specification, that is, different request keywords need to be set for clients of different categories. Similarly, the same response keyword also corresponds to the same class of service terminals, which generally have the same model or specification.
When receiving a request message sent by a certain client, the load balancing device may first extract a specified field (referred to as a first specified field) from the request message, where a position of the first specified field in the request message is a position of the request keyword in the request message sent by the client. Specifically, the load balancing device may extract the HTTP header name and the HTTP content in the message content of the request message as the first specified field of the request message. In another example, when the user sets the request keyword, the user may set a position of the request keyword in a request message sent by the client, for example: the request keyword is which field in the request message, and the subsequent load balancing device may extract the first specified field from the request message sent by the client based on the location set by the user. After extracting the first specified field in the request message sent by the client, the load balancing device may match the first specified field with the request keyword, for example: it may be determined whether the first specified field is the same as the request key.
Accordingly, when receiving a response message sent by a certain service end (referred to as a first service end), the load balancing device may first extract a specified field (referred to as a second specified field) from the response message, where a position of the second specified field in the response message is a position of the response message sent by the service end by the response keyword. Specifically, the load balancing device may extract the HTTP header name and the HTTP content in the message content of the response message as the second specified field of the response message. In another example, when the user sets the response keyword, the user may set the position of the response keyword in the response message sent by the server, for example: the response keyword is which field in the response message, and the subsequent load balancing device may extract the second specified field from the response message sent by the first service end based on the location set by the user. After extracting the second specified field in the response message sent by the first service end, the load balancing device may match the second specified field with the response keyword, for example: it is possible to judge whether the second specified field is the same as the above-mentioned response keyword.
It should be noted that there is no explicit timing relationship between step 101 and step 102. The load balancing device may determine that a first specified field in a request message sent by a certain client matches the request keyword, and then start to perform a step of matching a second specified field in a response message sent by the first service terminal with the response keyword when receiving the response message. Or, the load balancing device may perform the step of matching the first specified field in the request message with the request keyword when receiving the request message sent by the client, and perform the step of matching the second specified field in the response message with the response keyword when receiving the response message sent by the first server.
Step 103: when the first specified field is matched with the request keyword and the second specified field is matched with the response keyword, extracting a first specific field from the request message based on a preset first extraction strategy, and extracting a second specific field from the response message based on a preset second extraction strategy.
Step 104: and judging whether the first specific field is matched with the second specific field.
Step 105: and if the first specific field is matched with the second specific field, forwarding the request message sent by the client to the first service terminal.
In this embodiment, based on the matching results in the steps 101 and 102, if the first specified field matches the request keyword, it indicates that the client sending the request packet containing the first specified field is a client that needs session maintenance; if the first specified field does not match the request keyword, it indicates that the client sending the request packet containing the first specified field is not a client that needs session maintenance, and the load balancing device may allocate the request packet sent by the client to a certain service end based on a preset scheduling algorithm. On the other hand, if the second specified field is matched with the response keyword, the first server side which sends the response message containing the second specified field is the server side which participates in conversation maintenance; if the second specified field is not matched with the response keyword, it indicates that the first server sending the response message containing the second specified field is not a server participating in session maintenance, and the load balancing device may continue to match the second specified field in the response message with the response keyword when receiving the response message sent by the second server.
If only one server is included in the distributed system, or the response keyword corresponds to only one server (the response message sent by only the server includes the response keyword), the load balancing device may directly forward the request message sent by the client to the server when the first specified field matches the request keyword and the second specified field matches the response keyword, so as to implement session maintenance for the client.
However, a plurality of servers are usually included in the distributed system, and the servers often have the same model or specification, that is, the response keywords in the response messages sent by the servers are the same. In this case, when the first specified field matches the request keyword and the second specified field matches the response keyword, the load balancing device may further determine whether the client and the first service end correspond to each other, that is, whether the request packet of the client is forwarded to the first service end before. Specifically, the load balancing device may extract a first specific field from the request message sent by the client based on a preset first extraction policy, and extract a second specific field from the response message sent by the first server based on a preset second extraction policy. Wherein the first extraction strategy and the second extraction strategy can be preset by a user; the first extraction strategy may be the same as or different from the second extraction strategy.
In an alternative embodiment, the first extraction policy set by the user may include a first offset and a first end character, and the load balancing device may extract a first specific field from the request message according to the request keyword, the first offset, and the first end character, as shown in table 1 below:
TABLE 1
Similarly, the second extraction policy set by the user may include a second offset and a second end character, and the load balancing device may extract a second specific field from the response message according to the response keyword, the second offset, and the second end character, as shown in table 2 below:
TABLE 2
In this embodiment, after extracting the first specific field and the second specific field, the load balancing device may determine whether the first specific field and the second specific field are matched, for example: it is determined whether the first specific field and the second specific field are the same.
In practical applications, the first specific field and the second specific field may be matched by using a hash algorithm. In particular, the load balancing device may calculate its first hash value for the first particular field and its second hash value for the second particular field. Subsequently, the load balancing device may compare whether the first hash value and the second hash value are equal. If the first hash value and the second hash value are equal, that is, the first specific field is matched with the second specific field, it indicates that the client and the first service end correspond to each other, that is, the load balancing device forwards the request packet sent by the client to the first service end before, so that the load balancing device can forward the request packet sent by the client to the first service end at this time, so as to implement session maintenance for the client.
On the other hand, if the first specific field does not match the second specific field, it may be indicated that the client does not correspond to the first service end, that is, the load balancing device does not forward the request packet sent by the client to the first service end before. In this case, the load balancing device may continue to determine whether the first specific field matches a second specific field extracted from a reply message sent from the second server based on the second extraction policy. And the second specified field in the response message sent by the second server is also matched with the response keyword.
It should be noted that, if there are multiple servers, in addition to the first server, in the distributed system, where a second specified field in the sent reply message also matches the reply keyword, the load balancing device may randomly select one of the multiple servers as the second server, or may be based on a preset selection rule, for example: and selecting the server which receives the response message sent by the server firstly as a second server to continuously judge whether the client corresponds to the second server.
As can be seen from the above embodiments, the present application provides a new session maintenance implementation method without using a database or a cookie to implement session maintenance. Compared with the related technology, the technical scheme of the application can improve the continuity and stability of the user service and can also improve the efficiency and the safety of service processing of the server.
Corresponding to the embodiment of the session holding method, the application also provides an embodiment of the session holding device.
The embodiment of the session holding device can be applied to load balancing equipment. The device embodiments may be implemented by software, or by hardware, or by a combination of hardware and software. The software implementation is taken as an example, and is formed by reading corresponding computer program instructions in the nonvolatile memory into the memory for operation through the processor of the device where the software implementation is located as a logical means. From a hardware aspect, as shown in fig. 2, the present application is a hardware structure diagram of a load balancing device where a session holding apparatus is located, where the load balancing device where the apparatus is located in the embodiment may further include other hardware according to an actual function that the session holds, in addition to the processor, the memory, the network interface, and the nonvolatile memory shown in fig. 2, and details of this are not repeated.
Referring to fig. 3, a block diagram of a session holding apparatus according to an exemplary embodiment of the present application is shown. The apparatus 300 may be applied to the load balancing device shown in fig. 2, and includes:
a first matching unit 301, configured to match a first specified field in a request message sent by a client with a preset request keyword when the request message is received;
a second matching unit 302, configured to match a second specified field in a response message sent by a first service end with a preset response keyword when the response message is received;
an extracting unit 303, configured to extract a first specific field from the request message based on a preset first extraction policy and extract a second specific field from the response message based on a preset second extraction policy when the first specific field is matched with the request keyword and the second specific field is matched with the response keyword;
a determining unit 304, configured to determine whether the first specific field matches with the second specific field;
a forwarding unit 305, configured to forward the request packet sent by the client to the first service end when the first specific field matches the second specific field.
In an alternative embodiment, the determining unit 304 may include:
a computing subunit 3041, configured to compute a first hash value of the first specific field and compute a second hash value of the second specific field;
a comparing subunit 3042, configured to compare whether the first hash value and the second hash value are equal;
the forwarding unit 305 may include:
a forwarding sub-unit 3051, configured to forward, when the first hash value is equal to the second hash value, the request packet sent by the client to the first service end.
In another optional embodiment, the first specified field or the second specified field is an HTTP header name and an HTTP content in the message content.
In another alternative embodiment, the extracting unit 303 may include:
a first extracting subunit 3031, configured to extract a first specific field from the request message according to the request keyword, a preset first offset, and a first end character;
a second extracting subunit 3032, configured to extract a second specific field from the response message according to the response keyword, a preset second offset, and a second end character.
In another optional embodiment, the determining unit 304 may be further configured to, when the first specific field does not match the second specific field, continue to determine whether the first specific field matches a second specific field extracted from a response message sent from a second server based on the second extraction policy;
and the second specified field in the response message sent by the second server is matched with the response keyword.
The implementation process of the functions and actions of each unit in the above device is specifically described in the implementation process of the corresponding step in the above method, and is not described herein again.
For the device embodiments, since they substantially correspond to the method embodiments, reference may be made to the partial description of the method embodiments for relevant points. The above-described embodiments of the apparatus are merely illustrative, and 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 modules can be selected according to actual needs to achieve the purpose of the scheme of the application. One of ordinary skill in the art can understand and implement it without inventive effort.
The above description is only exemplary of the present application and should not be taken as limiting the present application, as any modification, equivalent replacement, or improvement made within the spirit and principle of the present application should be included in the scope of protection of the present application.
Claims (8)
1. A session holding method is applied to a load balancing device, and comprises the following steps:
when a request message sent by a client is received, matching a first designated field in the request message with a preset request keyword, and judging whether the first designated field is the same as the request keyword or not; the first designated field is an HTTP header name and HTTP content in the message content of the request message, and the request keyword is the HTTP header name and HTTP content in the message content of the request message sent by a preset client;
when a response message sent by a first service end is received, matching a second specified field in the response message with a preset response keyword, and judging whether the second specified field is the same as the response keyword or not; the second specified field is an HTTP header name and HTTP content in the message content of the response message, and the response keyword is the HTTP header name and HTTP content in the message content of the response message sent by a preset server;
when the first specified field is the same as the request keyword and the second specified field is the same as the response keyword, extracting a first specific field from the request message based on a preset first extraction strategy, and extracting a second specific field from the response message based on a preset second extraction strategy;
judging whether the first specific field is matched with the second specific field;
and if the first specific field is matched with the second specific field, forwarding the request message sent by the client to the first service terminal.
2. The method of claim 1, wherein the determining whether the first specific field and the second specific field match comprises:
calculating a first hash value of the first specific field and calculating a second hash value of the second specific field;
comparing whether the first hash value and the second hash value are equal;
if the first specific field is matched with the second specific field, forwarding the request message sent by the client to the first service end, including:
and if the first hash value is equal to the second hash value, forwarding the request message sent by the client to the first service end.
3. The method according to claim 1, wherein the extracting a first specific field from the request message based on a preset first extraction policy includes:
extracting a first specific field from the request message according to the request keyword, a preset first offset and a first end character;
the extracting a second specific field from the response message based on a preset second extracting strategy comprises the following steps:
and extracting a second specific field from the response message according to the response keyword, a preset second offset and a second ending character.
4. The method of claim 1, further comprising:
if the first specific field is not matched with the second specific field, continuously judging whether the first specific field is matched with the second specific field extracted from a response message sent from a second server based on the second extraction strategy;
and the second specified field in the response message sent by the second server is matched with the response keyword.
5. A session holding apparatus, wherein the apparatus is applied to a load balancing device, the apparatus comprising:
the first matching unit is used for matching a first designated field in a request message with a preset request keyword when the request message sent by a client is received, and judging whether the first designated field is the same as the request keyword or not; the first designated field is an HTTP header name and HTTP content in the message content of the request message, and the request keyword is the HTTP header name and HTTP content in the message content of the request message sent by a preset client;
the second matching unit is used for matching a second specified field in the response message with a preset response keyword when the response message sent by the first service end is received, and judging whether the second specified field is the same as the response keyword or not; the second specified field is an HTTP header name and HTTP content in the message content of the response message, and the response keyword is the HTTP header name and HTTP content in the message content of the response message sent by a preset server;
an extracting unit, configured to extract a first specific field from the request message based on a preset first extraction policy and extract a second specific field from the response message based on a preset second extraction policy when the first specified field is the same as the request keyword and the second specified field is the same as the response keyword;
the judging unit is used for judging whether the first specific field is matched with the second specific field;
and the forwarding unit is used for forwarding the request message sent by the client to the first service terminal when the first specific field is matched with the second specific field.
6. The apparatus according to claim 5, wherein the judging unit includes:
a calculating subunit, configured to calculate a first hash value of the first specific field, and calculate a second hash value of the second specific field;
a comparison subunit, configured to compare whether the first hash value and the second hash value are equal;
the forwarding unit includes:
and the forwarding subunit is configured to forward the request packet sent by the client to the first service end when the first hash value is equal to the second hash value.
7. The apparatus of claim 5, wherein the extraction unit comprises:
the first extraction subunit is used for extracting a first specific field from the request message according to the request keyword, a preset first offset and a first end character;
and the second extraction subunit is used for extracting a second specific field from the response message according to the response keyword, a preset second offset and a second ending character.
8. The apparatus of claim 5,
the judging unit is further configured to, when the first specific field does not match the second specific field, continue to judge whether the first specific field matches a second specific field extracted from a response message sent from a second server based on the second extraction policy;
and the second specified field in the response message sent by the second server is matched with the response keyword.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201711350621.2A CN108076149B (en) | 2017-12-15 | 2017-12-15 | Session maintaining method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201711350621.2A CN108076149B (en) | 2017-12-15 | 2017-12-15 | Session maintaining method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN108076149A CN108076149A (en) | 2018-05-25 |
| CN108076149B true CN108076149B (en) | 2021-07-23 |
Family
ID=62158386
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201711350621.2A Active CN108076149B (en) | 2017-12-15 | 2017-12-15 | Session maintaining method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN108076149B (en) |
Families Citing this family (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109510878B (en) * | 2018-12-24 | 2021-12-24 | 杭州迪普科技股份有限公司 | Long connection session keeping method and device |
| CN109474705B (en) * | 2018-12-28 | 2021-04-27 | 杭州迪普科技股份有限公司 | Session maintaining method and device |
| CN111147598B (en) * | 2019-12-30 | 2023-04-25 | 杭州迪普科技股份有限公司 | HTTP message processing method and device |
Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103457869A (en) * | 2013-08-28 | 2013-12-18 | 北京星网锐捷网络技术有限公司 | Conversation maintaining method and device |
Family Cites Families (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101166176B (en) * | 2006-10-19 | 2010-12-08 | 中兴通讯股份有限公司 | Method for dynamic load balance in distributed system based on session origination protocol |
| CN101340371B (en) * | 2008-08-12 | 2011-09-21 | 杭州华三通信技术有限公司 | Session keeping method and load balance apparatus |
| CN104836839A (en) * | 2015-03-30 | 2015-08-12 | 南京大学 | Universal user self-defining session system and session management method thereof |
| CN104811488B (en) * | 2015-04-13 | 2018-09-25 | 深信服网络科技（深圳）有限公司 | Session keeping method and system based on load-balancing device and load-balancing device |
-
2017
- 2017-12-15 CN CN201711350621.2A patent/CN108076149B/en active Active
Patent Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103457869A (en) * | 2013-08-28 | 2013-12-18 | 北京星网锐捷网络技术有限公司 | Conversation maintaining method and device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN108076149A (en) | 2018-05-25 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US9009232B2 (en) | Method and apparatus for processing authentication request message in a social network | |
| US9203734B2 (en) | Optimized bi-directional communication in an information centric network | |
| CN109586969B (en) | Content distribution network disaster tolerance method and device, computer equipment and storage medium | |
| CA2947325C (en) | Protocol type identification method and apparatus | |
| CN108076149B (en) | Session maintaining method and device | |
| US10848313B2 (en) | Methods and systems for network security using a cryptographic firewall | |
| CN110011935A (en) | Data flow processing method and relevant device | |
| US9544283B2 (en) | Method and apparatus for processing authentication request message in a social network | |
| CN110798402B (en) | Service message processing method, device, equipment and storage medium | |
| CN106254384B (en) | Service access method and device | |
| US11399016B2 (en) | System and method for identifying exchanges of encrypted communication traffic | |
| WO2016037489A1 (en) | Method, device and system for monitoring rcs spam messages | |
| CN111614726A (en) | Data forwarding method, cluster system and storage medium | |
| US10992702B2 (en) | Detecting malware on SPDY connections | |
| CN109474705B (en) | Session maintaining method and device | |
| WO2014201789A1 (en) | Service processing method, apparatus and system | |
| CN105960791A (en) | Stateless message routing | |
| CN110489231A (en) | Transaction Information recording method, equipment and computer readable storage medium | |
| CN105429802B (en) | The determination method, apparatus and server of qualitative data | |
| CN112637316B (en) | Communication method and device | |
| CN109451068B (en) | Method and device for inserting Set-Cookie value | |
| CN115665210B (en) | User problem processing method, user problem processing device and customer service system | |
| CN113259225B (en) | Instant messaging method, server and instant messaging system | |
| US12126618B1 (en) | System and method for identifying an application initiating a communication in a computing environment | |
| CN113923716B (en) | User information acquisition method and device and electronic equipment |
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 |