CN111131250B - Client identification method and device - Google Patents
Client identification method and device Download PDFInfo
- Publication number
- CN111131250B CN111131250B CN201911349834.2A CN201911349834A CN111131250B CN 111131250 B CN111131250 B CN 111131250B CN 201911349834 A CN201911349834 A CN 201911349834A CN 111131250 B CN111131250 B CN 111131250B
- Authority
- CN
- China
- Prior art keywords
- field name
- access request
- client
- name keyword
- common field
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/10—Network architectures or network communication protocols for network security for controlling access to devices or network resources
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/30—Managing network names, e.g. use of aliases or nicknames
- H04L61/3015—Name registration, generation or assignment
-
- 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
Abstract
This specification proposes a client identification method and apparatus, apply to the network device, dispose the common field name keyword set in advance in the network device, the common field name keyword set includes the common field name keyword used for disposing the client label, the method includes: acquiring an access request sent by a client; judging whether the access request carries a common field name keyword in a preset common field name keyword set or not; and under the condition that the access request carries the common field name keywords, determining the field value corresponding to the common field name keywords as the identifier of the client. Based on the technical scheme of the specification, unified configuration management can be performed on all network devices, client identification can be achieved without independently configuring the network devices according to the identification distribution rule of the server, and complexity of manual configuration of workers are avoided.
Description
Technical Field
The present disclosure relates to the field of network communication technologies, and in particular, to a client identification method and apparatus.
Background
In order to ensure the security and load health of the server, the access request sent by the client to the server is limited, and meanwhile, in order to avoid affecting the processing performance of the server, the access request sent by the client needs to be limited before reaching the server, so a third-party network device is often added between the client and the server to limit the access request of the client.
The network device can only limit the access of the client on the basis of identifying the client, so that how the network device effectively identifies the client becomes a key for guaranteeing the safety and load health of the server.
When the client accesses the server for the first time, the server adds the identifier allocated to the client in the response message, and when the client sends a request to the server again, the client identifier is added to the access request, so that the server can identify the client. However, since the identifier assigned to the client by the server is not recorded in the network device, the network device cannot identify the client.
In the prior art, a worker needs to know a rule for a server to allocate a client identifier to a client first, and then manually configure a search rule on a network device based on the allocation rule, where the configured search rule may include: message header name, keywords, etc. After the network device stores the search information, the network device may search the client identifier in the access request sent by the client based on the search information, and then may determine whether to limit the access request according to the client identifier. Since different servers have different rules for allocating client identifiers, different servers require a worker with professional experience to configure different search rules for the network device, and thus manual configuration is very complicated and complicated.
Disclosure of Invention
In view of the above technical problems, the present specification provides a client identification method and device, and the technical scheme is as follows:
according to a first aspect of the present specification, there is provided a client identifying method, applied to a network device, where a common field name keyword set is pre-configured in the network device, where the common field name keyword set includes a common field name keyword for configuring a client identifier, the method including:
acquiring an access request sent by a client;
judging whether the access request carries a common field name keyword in a preset common field name keyword set or not;
and under the condition that the access request carries the common field name keywords, determining the field value corresponding to the common field name keywords as the identifier of the client.
According to a second aspect of the present specification, there is provided a client identification apparatus, applied to a network device, where a common field name keyword set is configured in advance in the network device, where the common field name keyword set includes a common field name keyword for configuring a client identifier, the apparatus including:
the acquisition module is used for acquiring an access request sent by a client;
the judging module is used for judging whether the access request carries a common field name keyword in a preset common field name keyword set or not;
and the determining module is used for determining the field value corresponding to the common field name keyword as the identifier of the client under the condition that the access request carries the common field name keyword.
In the specification, a common field name keyword set is configured in a network device in advance, the network device is configured between a client and a server and used for identifying the client, and as the common field name keyword set comprises a common field name keyword used for configuring a client identifier, under the condition that an access request carries the common field name keyword in the preset common field name keyword set, a field value corresponding to the common field name keyword can be determined, namely the identifier allocated to the client by the server.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the specification.
Drawings
In order to more clearly illustrate the embodiments of the present specification or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments described in the embodiments of the present specification, and other drawings can be obtained by those skilled in the art according to the drawings.
FIG. 1 is a schematic diagram of a network architecture according to an embodiment of the present disclosure;
fig. 2 is a schematic flowchart of a first client identifying method according to an embodiment of the present disclosure;
fig. 3 is a flowchart illustrating a second client identification method according to an embodiment of the present disclosure;
fig. 4 is a flowchart illustrating a third client identifying method according to an embodiment of the present disclosure;
fig. 5 is a schematic diagram of a client identification apparatus according to an embodiment of the present disclosure;
fig. 6 is a schematic diagram of another client identification device according to an embodiment of the present disclosure.
Detailed Description
In order to make the technical solutions in the embodiments of the present disclosure better understood by those skilled in the art, the technical solutions in the embodiments of the present disclosure will be described in detail below with reference to the drawings in the embodiments of the present disclosure, and it is apparent that the described embodiments are only a part of the embodiments of the present disclosure, but not all embodiments. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments in the present specification should be within the scope of protection.
The terminology used in the description herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the description. As used in this specification 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 should be understood that although the terms first, second, third, etc. may be used herein to describe various information, these information should not be limited to these terms. These terms are only used to distinguish one type of information from another. For example, the first information may also be referred to as second information, and similarly, the second information may also be referred to as first information, without departing from the scope of the present specification. The word "if" as used herein may be interpreted as "at … …" or "when … …" or "in response to a determination", depending on the context.
In order to ensure the security and load health of the server, the access request sent by the client to the server is limited, for example, the number of accesses of the same client in a preset time needs to be limited, so that server overload caused by malicious access to the server is avoided. In addition, in order to avoid affecting the processing performance of the server, it is necessary to limit the access request sent by the client before the access request reaches the server, so a third-party network device is often added between the client and the server to limit the access request of the client, the network architecture is as shown in fig. 1, the network device is disposed between the links of the client and the server, and is responsible for receiving the access requests sent by all the clients and determining whether to allow the access requests to pass, i.e., determining whether to forward the access requests to the server.
The network device can only limit the access of the client on the basis of identifying the client, so that how the network device effectively identifies the client becomes a key for guaranteeing the safety and load health of the server.
When the client accesses the server for the first time, the server adds the identifier allocated to the client in the response message, the client is kept in the local, and when the client sends a request to the server again, the client identifier is added to the access request, so that the server can identify the client. However, since the identifier assigned to the client by the server is not recorded in the network device, the network device cannot identify the client. For example, referring to fig. 1, when a client a accesses a server a for the first time, the server a will add a client identifier allocated to the client a in a response message sent to the client a, and the client a will store the identifier after receiving the response message and will add the identifier to the access request every time the client a accesses the server a, so that the server a can recognize the client a. However, the client identity configuration rules of different servers may be different, for example, server a assigns a field name of the use of the client identity as sessionid, server B assigns a field name of the use of the client identity as Jsessionid, and server C assigns a field name of the use of the client identity as phpsessionid. For example, if the identifier assigned to the client a by the server a is 1, the client a adds a field name and a field value of "sessionid 1" to the access request sent to the server a except for the first time, so that the server a can recognize the client a.
In the prior art, a worker needs to know a rule for a server to allocate a client identifier to a client first, and then manually configure a search rule on a network device based on the allocation rule, where the configured search rule may include: message header name, keywords, etc. The method includes the steps that a worker needs to know identification distribution rules of different servers served by network equipment in a network architecture first, and then the identification distribution rules are set in the network equipment according to the identification distribution rules, after the network equipment stores the search information, the network equipment can search a client identification in an access request sent by a client based on the search information, and then whether the access request is limited or not can be determined according to the client identification. In addition, in the case of different clients, the staff of the network equipment manufacturer needs to set different search rules for the servers of the client locally in the network equipment, and a large amount of human resources are consumed.
In order to solve the above problem, a scheme provided in this specification is that a common field name keyword set is uniformly and pre-configured in all network devices, where the common field name keyword set includes a common field name keyword in which a client identifier is configured by a server, and the network device obtains an access request sent by a client, and determines whether the access request carries the common field name keyword in a preset common field name keyword set, and in a case where the access request carries the common field name keyword, a field value corresponding to the common field name keyword can be determined as the identifier of the client sending the access request. Therefore, the identification of the network equipment to the client is realized, and the search rule is not required to be configured for the network equipment independently according to the distribution rule of the server, so that the complexity and complexity caused by manual configuration are avoided.
Fig. 2 is a schematic flow chart of a client identification method shown in this specification, where the method may be applied to a network device, where a common field name keyword set is preconfigured in the network device, and the common field name keyword set includes a common field name keyword for configuring a client identifier, and the method includes:
s201, acquiring an access request sent by a client;
the network device may be a web firewall, or may also be a load balancing device or other devices, which is not limited in this specification. The network equipment is arranged between the client and the server, and all the access requests sent by the client need to pass through the network equipment first, so that the network equipment can acquire the access requests sent by all the servers, and meanwhile, the network equipment can select whether to forward the access requests sent by the client to the server, thereby protecting the server.
S202, judging whether the access request carries a common field name keyword in a preset common field name keyword set or not;
the network device stores a common field name keyword set, and the common field name keyword set comprises common field name keywords for configuring client identifiers. For example, the field name keywords in the set may include: sessionid, jsissonid, phpsessionid, ID, user, etc. Therefore, after receiving the access request sent by the client, the network device may further determine whether the access request carries a keyword in the field name keyword set. The message header, URL or payload content of the access request may be searched for the field name key.
S203, determining a field value corresponding to the common field name keyword as the identifier of the client when the access request carries the common field name keyword.
Since the server assigns a client identifier to the client when the client accesses the server for the first time, the client identifier is added to the access request every time the client accesses the server except for the first time. Referring to fig. 1, when a client a accesses a server a for the first time, the server a assigns an identifier 1 to the client a, where the field name used is "sessionid", and when the client a accesses the server a again, the client a adds a field name and a field value of "sessionid 1" to the access request, so that the server a can recognize the field name and the field value. When the network equipment receives an access request sent to the server A by the client A, the network equipment determines that the access request carries a keyword of the field name of 'sessionid' by searching. Therefore, the field value "1" corresponding to the keyword of the field name of "sessionid" can be determined as the identifier of the client a, and the client is identified.
In this specification, a common field name keyword set is preconfigured in a network device, and it is determined whether an access request sent by a client carries a keyword in the keyword set, and in the case of carrying the keyword in the keyword set, a field value of the field name keyword carried in the access request can be determined to be an identifier of the client, so that the client is identified, and inconvenience caused by setting different search rules in the network device for different servers is avoided.
Of course, if the client accesses the server for the first time, the identifier is not obtained yet, so that the identifier is not added to the access request.
Therefore, in one embodiment, it is determined that the access request does not carry the client identifier under the condition that the access request does not carry the common field name keyword.
For example, the client B accesses the server a for the first time, and the identifier allocated to the client B is not yet provided by the server a, and at this time, the access request sent by the client B to the server a does not include an identifier, and does not include a field name keyword used by the server a to allocate the identifier. Therefore, the access request can be determined not to carry the client identifier under the condition that the access request does not carry the keyword of the common field name.
Referring to fig. 1, the network device identifies the client using the same common field name keyword set for each of the server a, the server B, and the server C, and since there are many keywords in the field name keyword set, it takes a certain time to determine whether the access request includes a keyword. On the basis, the present specification further proposes that, when it is determined that the access request carries a common field name keyword, a target server to which the access request is sent is determined, and the carried common field name keyword is stored as an individualized field name keyword of the target server.
As shown in fig. 3, S204 is also included after S203,
s204, under the condition that the access request carries the common field name keyword, determining a target server to which the access request is sent, and storing the carried common field name keyword as the personalized field name keyword of the target server.
With reference to the example of S203, when it is determined that the access request sent by the client a carries the common field name keyword, the target server sent by the access request may be determined, where the target server may be determined by a target URL included in the access request, and after the determination, it is found that the target server to which the access request is sent is the server a, and at this time, it may be determined that the field name keyword used by the server a to allocate the client identifier is "sessionid". The server a may store the personalized field name "sessionid", and since the field name keys used by the server to assign identifiers are generally uniform, that is, the field names used by the server to assign identifiers to any client requesting data are all consistent, it may be determined that the field names used by the server a to assign identifiers to all clients are "sessionid". The personalized field name "sessionid" may be stored for server a.
The present specification proposes another client identification method on the basis of providing a personalized field name keyword stored for a server, as shown in fig. 4, which is a flow diagram of another client identification method proposed in the present specification,
s401, after an access request sent by a client is obtained, a target server sent by the access request is determined;
after the access request sent by the client is obtained, the target server to which the access request is sent may be determined according to the target URL in the message.
S402, determining whether the personalized field name key word aiming at the target server is stored;
after determining the target server to which the access request is to be sent, for example, determining that the target server is server C in conjunction with fig. 1, further determining whether a personalized field name keyword for server C is stored, if yes, performing S403, and if not, performing S404.
S403, under the condition that the personalized field name keyword for the target server is stored, further judging whether the access request carries the personalized field name keyword;
wherein, under the condition that the access request carries the personalized field name keyword, the field value corresponding to the personalized field name keyword is determined as the identifier of the client,
and under the condition that the access request does not carry the personalized field name keyword, determining that the access request does not carry a client identifier.
If the personalized field name keyword for the server C is stored, it indicates that the server C uses the personalized field name keyword to allocate an identifier for each client, for example, the personalized field name keyword stored for the server C is "phpsessionid", so it can be directly determined whether the access request carries the personalized field name keyword, if so, it indicates that the field value corresponding to the personalized field name keyword is an identifier of the client sending the access request, for example, the access request carries "phpsessinide" 2 ", it indicates that the identifier allocated to the client by the server C is 2, and if the access request does not carry the personalized field name keyword, it also can directly indicate that the access request does not carry a client identifier, and the server C is accessed for the first time.
S404, if the personalized field name keyword for the target server is not stored, further determining whether the access request carries a common field name keyword in a preset common field name keyword set.
And determining a field value corresponding to the common field name keyword as the identifier of the client under the condition that the access request carries the common field name keyword.
And under the condition that the access request does not carry the common field name key word, determining that the access request does not carry the client identifier.
The detailed description of steps S202 to S203 may be referred to for the identification method in the case where the personalized field name keyword for the target server is not stored, and this description is not repeated here.
In the above-mentioned client identification method, after the access request is obtained, the target server to which the access request is sent is judged first, after the target server is determined, whether the personalized field name keyword for the target server is stored is further judged, if yes, whether the personalized field name keyword of the target server is carried in the access request can be directly determined, if yes, the field value corresponding to the personalized field name keyword is determined to be the identifier of the client sending the access request, and if not, the identifier is also directly indicated not to be carried in the access request, so that the client can be identified quickly.
After the client identifier is identified, the access records of each client can be further recorded according to the client identifier, in one implementation manner, for the safety of the server, when the number of times that the client accesses the server within the preset time reaches a preset threshold, the access request is subjected to packet loss processing, so that the influence of the client accessing the server for multiple times on the server is avoided, and when the number of times that the client accesses the server does not reach the threshold, the access request can be forwarded to the server. Of course, this description does not limit how the access request is restricted based on the client identifier.
Corresponding to the aforementioned client identification method, the present specification further provides a client identification apparatus, applied to a network device, in which a common field name keyword set is pre-configured, where the common field name keyword set includes a common field name keyword for configuring a client identifier,
as shown in fig. 5, the apparatus includes:
an obtaining module 510, configured to obtain an access request sent by a client;
a determining module 520, configured to determine whether the access request carries a common field name keyword in a preset common field name keyword set;
a determining module 530, configured to determine, when the access request carries a common field name keyword, that a field value corresponding to the common field name keyword is an identifier of the client.
As shown in fig. 6, in one embodiment, the apparatus further comprises:
the storage module 540 is configured to determine a target server to which the access request is sent when the access request carries the common field name keyword, and store the carried common field name keyword as the personalized field name keyword of the target server.
In one embodiment, the determining module 520 is specifically configured to determine a target server to which the access request is sent, and determine whether a personalized field name keyword for the target server is stored; under the condition that the personalized field name keyword aiming at the target server is stored, further judging whether the access request carries the personalized field name keyword or not;
the determining module 530 is specifically configured to determine, when the access request carries the personalized field name keyword, a field value corresponding to the personalized field name keyword as the identifier of the client.
In one embodiment, the determining module 520 is specifically configured to determine a target server to which the access request is sent, and determine whether a personalized field name keyword for the target server is stored; under the condition that the personalized field name keywords aiming at the target server are not stored, whether the access request carries the common field name keywords in a preset common field name keyword set or not is further judged;
the determining module 530 is specifically configured to determine, when the access request carries a common field name keyword, a field value corresponding to the common field name keyword as the identifier of the client.
In an embodiment, the determining module 530 is further configured to determine that the access request does not carry the client identifier when the access request does not carry the common field name key.
The implementation processes of the functions and actions of the components in the device are specifically described in the implementation processes of the corresponding steps in the method, and are not described herein again.
Since the device embodiments basically correspond to the method embodiments, reference may be made to the partial description of the method embodiments for relevant points. The above-described apparatus embodiments are merely illustrative. Some or all of the modules can be selected according to actual needs to achieve the purpose of the solution in the specification. One of ordinary skill in the art can understand and implement it without inventive effort.
Thus, particular embodiments of the subject matter have been described. Other embodiments are within the scope of the following claims. In some cases, the actions recited in the claims can be performed in a different order and still achieve desirable results. Further, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In some implementations, multitasking and parallel processing may be advantageous. The embodiments in the present specification are described in a progressive manner, and the same and similar parts among the embodiments can be referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, the device embodiments are substantially similar to the method embodiments and therefore are described in a relatively simple manner, and reference may be made to some of the description of the method embodiments for relevant points. The above-described apparatus embodiments are merely illustrative, and the modules described as separate components may or may not be physically separate, and the functions of the modules may be implemented in one or more software and/or hardware when implementing the embodiments of the present disclosure. Some or all of the modules may be selected according to actual needs to achieve the purpose of the embodiment. One of ordinary skill in the art can understand and implement it without inventive effort.
The above description is only for the purpose of illustrating the preferred embodiments of the present disclosure and is not to be construed as limiting the present disclosure, and any modifications, equivalents, improvements, etc. made within the spirit and principle of the present disclosure are intended to be included within the scope of the present disclosure.
Claims (8)
1. A client identification method is applied to network equipment, a common field name keyword set is configured in the network equipment in advance, the common field name keyword set comprises common field name keywords used for configuring client identifications, and the method comprises the following steps:
acquiring an access request sent by a client;
judging whether the access request carries a common field name keyword in a preset common field name keyword set or not;
under the condition that the access request carries common field name keywords, determining field values corresponding to the common field name keywords as the identification of the client;
and under the condition that the access request carries the common field name keyword, determining a target server to which the access request is sent, and storing the carried common field name keyword as the personalized field name keyword of the target server.
2. The method according to claim 1, wherein the determining whether the access request carries a common field name keyword in a preset common field name keyword set specifically comprises:
determining a target server to which the access request is sent, and judging whether personalized field name keywords aiming at the target server are stored or not;
under the condition that the personalized field name keyword aiming at the target server is stored, further judging whether the access request carries the personalized field name keyword or not;
the determining that the field value corresponding to the common field name keyword is the identifier of the client specifically includes:
and under the condition that the access request carries the personalized field name keyword, determining a field value corresponding to the personalized field name keyword as the identifier of the client.
3. The method according to claim 1, wherein the determining whether the access request carries a common field name keyword in a preset common field name keyword set specifically comprises:
determining a target server to which the access request is sent, and judging whether personalized field name keywords aiming at the target server are stored or not;
under the condition that the personalized field name keywords aiming at the target server are not stored, whether the access request carries the common field name keywords in a preset common field name keyword set or not is further judged;
the determining that the field value corresponding to the common field name keyword is the identifier of the client specifically includes:
and under the condition that the access request carries the common field name keywords, determining the field value corresponding to the common field name keywords as the identifier of the client.
4. The method of claim 1, further comprising:
and under the condition that the access request does not carry the key words of the common field names, determining that the access request does not carry the client identification.
5. A client identification apparatus, applied to a network device, where a common field name keyword set is preconfigured in the network device, where the common field name keyword set includes a common field name keyword for configuring a client identifier, and the apparatus includes:
the acquisition module is used for acquiring an access request sent by a client;
the judging module is used for judging whether the access request carries a common field name keyword in a preset common field name keyword set or not;
a determining module, configured to determine, when the access request carries a common field name keyword, a field value corresponding to the common field name keyword as an identifier of the client;
and the storage module is used for determining a target server to which the access request is sent under the condition that the access request carries the common field name keyword, and storing the carried common field name keyword as the personalized field name keyword of the target server.
6. The apparatus of claim 5,
the judging module is specifically configured to determine a target server to which the access request is sent, and judge whether an individualized field name keyword for the target server is stored; under the condition that the personalized field name keyword aiming at the target server is stored, further judging whether the access request carries the personalized field name keyword or not;
the determining module is specifically configured to determine, when the access request carries the personalized field name keyword, a field value corresponding to the personalized field name keyword as the identifier of the client.
7. The apparatus of claim 5,
the judging module is specifically configured to determine a target server to which the access request is sent, and judge whether an individualized field name keyword for the target server is stored; under the condition that the personalized field name keywords aiming at the target server are not stored, whether the access request carries the common field name keywords in a preset common field name keyword set or not is further judged;
the determining module is specifically configured to determine, when the access request carries a common field name keyword, a field value corresponding to the common field name keyword as the identifier of the client.
8. The apparatus of claim 5,
the determining module is further configured to determine that the access request does not carry the client identifier under the condition that the access request does not carry the keyword of the common field name.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911349834.2A CN111131250B (en) | 2019-12-24 | 2019-12-24 | Client identification method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911349834.2A CN111131250B (en) | 2019-12-24 | 2019-12-24 | Client identification method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111131250A CN111131250A (en) | 2020-05-08 |
| CN111131250B true CN111131250B (en) | 2022-04-26 |
Family
ID=70500539
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911349834.2A Active CN111131250B (en) | 2019-12-24 | 2019-12-24 | Client identification method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111131250B (en) |
Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104394122A (en) * | 2014-10-31 | 2015-03-04 | 杭州安恒信息技术有限公司 | HTTP (Hyper Text Transport Protocol) service firewall based on adaptive agent mechanism |
| CN104640114A (en) * | 2015-01-04 | 2015-05-20 | 中国联合网络通信集团有限公司 | Verification method and device of access request |
| CN105245626A (en) * | 2015-07-02 | 2016-01-13 | 中国人民武装警察部队司令部信息化部 | Method for realizing website addressing by using shortcut domain name in private network |
| CN105608227A (en) * | 2016-01-26 | 2016-05-25 | 唐山新质点科技有限公司 | Document data retrieval method and device |
| CN106506641A (en) * | 2016-11-07 | 2017-03-15 | 杭州迪普科技股份有限公司 | A kind of ident value extracting method of client device and device |
| CN106911649A (en) * | 2015-12-23 | 2017-06-30 | 北京奇虎科技有限公司 | A kind of method and apparatus for detecting network attack |
| CN107920138A (en) * | 2016-10-08 | 2018-04-17 | 腾讯科技（深圳）有限公司 | A kind of user's unifying identifier generation method, apparatus and system |
| CN109274779A (en) * | 2017-07-17 | 2019-01-25 | 华为技术有限公司 | A kind of alias management method and equipment |
| CN110086886A (en) * | 2019-05-14 | 2019-08-02 | 北京天融信网络安全技术有限公司 | Dynamic session keeping method and device |
| CN110213208A (en) * | 2018-05-09 | 2019-09-06 | 腾讯科技（深圳）有限公司 | A kind of method and apparatus and storage medium of processing request |
Family Cites Families (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8037097B2 (en) * | 2008-05-30 | 2011-10-11 | Yahoo! Inc. | Universal device identifier for globally identifying and binding disparate device identifiers to the same mobile device |
| JP5304817B2 (en) * | 2011-03-09 | 2013-10-02 | コニカミノルタ株式会社 | Image forming apparatus, image forming system, image forming apparatus control method, and image forming apparatus control program |
| US9208211B2 (en) * | 2011-03-23 | 2015-12-08 | Red Hat, Inc. | Performing object relational mapping for a data grid |
-
2019
- 2019-12-24 CN CN201911349834.2A patent/CN111131250B/en active Active
Patent Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104394122A (en) * | 2014-10-31 | 2015-03-04 | 杭州安恒信息技术有限公司 | HTTP (Hyper Text Transport Protocol) service firewall based on adaptive agent mechanism |
| CN104640114A (en) * | 2015-01-04 | 2015-05-20 | 中国联合网络通信集团有限公司 | Verification method and device of access request |
| CN105245626A (en) * | 2015-07-02 | 2016-01-13 | 中国人民武装警察部队司令部信息化部 | Method for realizing website addressing by using shortcut domain name in private network |
| CN106911649A (en) * | 2015-12-23 | 2017-06-30 | 北京奇虎科技有限公司 | A kind of method and apparatus for detecting network attack |
| CN105608227A (en) * | 2016-01-26 | 2016-05-25 | 唐山新质点科技有限公司 | Document data retrieval method and device |
| CN107920138A (en) * | 2016-10-08 | 2018-04-17 | 腾讯科技（深圳）有限公司 | A kind of user's unifying identifier generation method, apparatus and system |
| CN106506641A (en) * | 2016-11-07 | 2017-03-15 | 杭州迪普科技股份有限公司 | A kind of ident value extracting method of client device and device |
| CN109274779A (en) * | 2017-07-17 | 2019-01-25 | 华为技术有限公司 | A kind of alias management method and equipment |
| CN110213208A (en) * | 2018-05-09 | 2019-09-06 | 腾讯科技（深圳）有限公司 | A kind of method and apparatus and storage medium of processing request |
| CN110086886A (en) * | 2019-05-14 | 2019-08-02 | 北京天融信网络安全技术有限公司 | Dynamic session keeping method and device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111131250A (en) | 2020-05-08 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| EP3327992B1 (en) | Method of selecting network slice and system utilizing same | |
| CN110896355B (en) | Network slice selection method and device | |
| CN112039942A (en) | Subscription and publishing method and server | |
| CN110166570B (en) | Service session management method and device, and electronic device | |
| CN105228140B (en) | A kind of data access method and device | |
| US11218385B2 (en) | Network entity and method for identifier allocating and/or mapping of network services | |
| US8924562B2 (en) | Dynamic policy generation and assignment | |
| CN111327668B (en) | Network management method, device, equipment and storage medium | |
| CN110691042A (en) | Resource allocation method and device | |
| US11265254B1 (en) | Systems and methods for determining a policy that allocates traffic associated with a network protocol type to a network slice | |
| CN113285926B (en) | Honey pot trapping method and device for power monitoring system and computer equipment | |
| US7552210B1 (en) | Method of and system for handling cookies | |
| CN110677475A (en) | Micro-service processing method, device, equipment and storage medium | |
| CN112804679A (en) | Network slice connection method and device, storage medium and electronic device | |
| CN107948979B (en) | Information processing method and device and auditing equipment | |
| EP3016423A1 (en) | Network safety monitoring method and system | |
| CN106060006B (en) | Access method and device | |
| CN109743357B (en) | Method and device for realizing service access continuity | |
| CN111131250B (en) | Client identification method and device | |
| US9847927B2 (en) | Information processing device, method, and medium | |
| EP2881861A1 (en) | Load distribution device, information processing system, method, and program | |
| CN115826444A (en) | Security access control method, system, device and equipment based on DNS analysis | |
| CN108011801B (en) | Data transmission method, equipment, device and system | |
| CN110545336A (en) | IP address replacing method, device, computer equipment and storage medium | |
| CN114125025A (en) | Data transmission method and device under multi-target network |
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 |