CN113922952B - Access request response method, device, computer equipment and storage medium - Google Patents

Access request response method, device, computer equipment and storage medium Download PDF

Info

Publication number
CN113922952B
CN113922952B CN202111161126.3A CN202111161126A CN113922952B CN 113922952 B CN113922952 B CN 113922952B CN 202111161126 A CN202111161126 A CN 202111161126A CN 113922952 B CN113922952 B CN 113922952B
Authority
CN
China
Prior art keywords
client
request
server
random number
time
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
Application number
CN202111161126.3A
Other languages
Chinese (zh)
Other versions
CN113922952A (en
Inventor
陈优优
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Hengzhong Chuangmei Shenzhen Development Partnership Enterprise LP
Original Assignee
Hengzhong Chuangmei Shenzhen Development Partnership Enterprise LP
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Hengzhong Chuangmei Shenzhen Development Partnership Enterprise LP filed Critical Hengzhong Chuangmei Shenzhen Development Partnership Enterprise LP
Priority to CN202111161126.3A priority Critical patent/CN113922952B/en
Publication of CN113922952A publication Critical patent/CN113922952A/en
Application granted granted Critical
Publication of CN113922952B publication Critical patent/CN113922952B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/08—Key distribution or management, e.g. generation, sharing or updating, of cryptographic keys or passwords
    • H04L9/0861—Generation of secret information including derivation or calculation of cryptographic keys or passwords
    • H04L9/0869—Generation of secret information including derivation or calculation of cryptographic keys or passwords involving random numbers or seeds
    • 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/04—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks
    • H04L63/0428—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks wherein the data content is protected, e.g. by encrypting or encapsulating the payload
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/32—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials
    • H04L9/3297—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials involving time stamps, e.g. generation of time stamps

Abstract

The application discloses an access request response method, an access request response device, computer equipment and a storage medium. The method comprises the following steps performed by the server: receiving a first type of request, wherein the first type of request is used for acquiring time characteristic data and an encryption key of a server, and the time characteristic data is determined according to the acquisition time; transmitting the time feature data and the encryption key to the client; receiving a second type request, wherein the second type request comprises request parameters and duplicate checking information, the duplicate checking information is obtained by encrypting a client random number by adopting an encryption key according to time characteristic data, and the client random number is generated by a client; decrypting the duplicate checking information by adopting a decryption key to obtain time characteristic data and a client random number; and determining whether to respond to the second type of request according to the request parameters according to the time characteristic data and the client random number. The access request response method can improve the utilization rate of server resources.

Description

Access request response method, device, computer equipment and storage medium
Technical Field
The present disclosure relates to the field of communications technologies, and in particular, to an access request response method, an access request response device, a computer device, and a storage medium.
Background
Today, the complexity of application programs is higher and higher, and the interaction between a client and a server is more and more frequent, so that codes in many application programs may be written inaccurately, and thus a situation that the client repeatedly interacts with the server for a plurality of times may occur in one operation. Sometimes, a timer can cause the client to continuously request the server, which wastes server resources to a certain extent.
Disclosure of Invention
In view of this, the embodiments of the present application provide an access request response method, apparatus, computer device, and storage medium for preventing excessive interaction between a client and a server, so as to solve the problem of server resource waste caused by repeated and excessive interaction between the server and the client.
In a first aspect, an embodiment of the present application provides an access request response method, including the following steps performed by a server:
receiving a first type of request, wherein the first type of request is used for acquiring time characteristic data and an encryption key of the server, the server stores a decryption key, the decryption key is used for decrypting information encrypted by the encryption key, and the time characteristic data is determined according to the acquisition time;
Transmitting the time feature data and the encryption key to a client;
receiving a second type request, wherein the second type request comprises request parameters and duplicate checking information, the duplicate checking information is obtained by encrypting the encryption key according to the time characteristic data and a client random number, and the client random number is generated by the client;
decrypting the duplicate checking information by adopting the decryption key to obtain the time characteristic data and the client random number;
and determining whether to respond to the second type request according to the request parameters according to the time characteristic data and the client random number.
Aspects and any one of the possible implementations as described above, further provides an implementation,
when the time feature data is a server random number and a timestamp, determining whether to respond to the second type request according to the request parameter according to the time feature data and the client random number includes:
based on a pre-acquired client ID, verifying the values of the server random number sent by the client and the server random number stored by the server, and if the values of the server random number sent by the client and the server random number stored by the server are the same, acquiring the timestamp sent by the client and the client random number, wherein a first mapping relation exists between the client ID and the server random number stored by the server;
Based on a pre-acquired client ID, verifying the timestamp sent by the client and the timestamp stored by the server, wherein a second mapping relationship exists between the client ID and the timestamp stored by the server;
if the time stamp sent by the client is different from the time stamp stored by the server, rejecting to respond to the second type request;
if the time stamp sent by the client is the same as the time stamp stored by the server, comparing the client random number with a client comparison random number generated in a first preset time area;
and if the numerical comparison result of the client random number and the client comparison random number generated in the first preset time area is the same as the numerical value, responding to the first received second type request according to the request parameter.
Aspects and any one of the possible implementations as described above, further provides an implementation,
when the time feature data is an identification index, determining whether to respond to the second type request according to the request parameter according to the time feature data and the client random number includes:
Checking the index value of the identification index;
if the index value which is the same as the identification index exists, responding to the second type request according to the request parameter based on the identification index;
if the index value which is larger than one and is the same as the identification index exists, comparing the client random number with the client comparison random number generated in a second preset time area in a numerical value, wherein the request corresponding to the client random number is a request corresponding to the identification index with the same index value;
and if the client random number is the same as the client random number value comparison result of the client comparison random number generated in the second preset time region, responding to the first received second type request according to the request parameter.
In accordance with aspects and any one of the possible implementations described above, there is further provided an implementation, before the receiving the first type of request, the method further including:
and in a test stage of determining the time when the identification index exists in the cache, if the index value which is the same as the identification index does not exist, the time when the identification index exists in the cache is prolonged according to a preset time amount.
In a second aspect, embodiments of the present application provide another access request response method, including the following steps performed by a client:
sending a first type request to a server, wherein the first type request is used for acquiring time characteristic data and an encryption key of the server;
receiving the time characteristic data and the encryption key;
generating a client random number;
encrypting by adopting the encryption key according to the time characteristic data and the client random number to obtain duplicate checking information;
and sending a second type request to the server, wherein the second type request comprises request parameters and the duplicate checking information.
In the aspect and any possible implementation manner described above, there is further provided an implementation manner, where the encrypting with the encryption key according to the time feature data and the client random number to obtain duplication checking information includes:
splicing the time characteristic data and the client random number in a preset splicing mode to obtain splicing information;
and encrypting the splicing information by adopting the encryption key to obtain the duplicate checking information.
In a third aspect, an embodiment of the present application provides an access request response apparatus, including:
The system comprises a first receiving module, a second receiving module and a first receiving module, wherein the first receiving module is used for receiving a first type request, the first type request is used for acquiring time characteristic data and an encryption key of the server, the server stores a decryption key, the decryption key is used for decrypting information encrypted by the encryption key, and the time characteristic data is determined according to the acquisition time;
the first sending module is used for sending the time characteristic data and the encryption key to the client;
the second receiving module is used for receiving a second type request, wherein the second type request comprises request parameters and duplicate checking information, the duplicate checking information is obtained by encrypting the encryption key according to the time characteristic data and a client random number, and the client random number is generated by the client;
the decryption module is used for decrypting the duplicate checking information by adopting the decryption key to obtain the time characteristic data and the client random number;
and the response determining module is used for determining whether to respond to the second type of request according to the request parameters according to the time characteristic data and the client random number.
In a fourth aspect, embodiments of the present application provide another access request response device, including:
The second sending module is used for sending a first type of request to the server, wherein the first type of request is used for acquiring time characteristic data and an encryption key of the server;
a third receiving module for receiving the time feature data and the encryption key;
the generation module is used for generating a client random number;
the encryption module is used for obtaining duplicate checking information by adopting the encryption key according to the time characteristic data and the client random number;
and the third sending module is used for sending a second type request to the server, wherein the second type request comprises a request parameter and the duplicate checking information.
In a fifth aspect, embodiments of the present application provide a computer device comprising a memory, a processor, and computer readable instructions stored in the memory and executable on the processor, the processor executing the steps of the access request response method according to the first aspect or the steps of the access request response method according to the second aspect.
In a sixth aspect, embodiments of the present application provide a computer-readable storage medium storing computer-readable instructions that, when executed by a processor, implement the steps of the access request response method according to the first aspect, or that, when executed by a processor, implement the steps of the access request response method according to the second aspect.
In the embodiment of the application, based on the time feature data and the client random number, when the client and the server interact, the server judges whether the second type request sent by the client is repeated or not based on the time uniqueness of the time feature data and the client random number, so as to determine whether to respond to the second type request according to the request parameter and execute the function operation corresponding to the request parameter. The embodiment of the application adopts the self-checking method of the server, so that even if an uncontrollable repeated request sending event occurs at the client side, the server can actively avoid excessive interaction with the client side, and the utilization rate of the server resource can be improved.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings that are needed in the embodiments will be briefly described below, it being obvious that the drawings in the following description are only some embodiments of the present application, and that other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
FIG. 1 is a flow chart of an access request response method in an embodiment of the present application;
FIG. 2 is a functional block diagram of an apparatus according to one embodiment of the present application in one-to-one correspondence with an access request response method performed by a server;
FIG. 3 is a functional block diagram of an apparatus according to one embodiment of the present application in one-to-one correspondence with an access request response method performed by a client;
FIG. 4 is a schematic diagram of a computer device in an embodiment of the present application.
Detailed Description
For a better understanding of the technical solutions of the present application, embodiments of the present application are described in detail below with reference to the accompanying drawings.
It should be understood that the described embodiments are merely some, but not all, of the embodiments of the present application. All other embodiments, which can be made by one of ordinary skill in the art without undue burden from the present disclosure, are within the scope of the present disclosure.
The terminology used in the embodiments of the application 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 be understood that the term "and/or" as used herein is merely one of the same fields describing the associated object, meaning that there may be three relationships, e.g., a and/or B, may represent: a exists alone, A and B exist together, and B exists alone. In addition, the character "/" herein generally indicates that the front and rear associated objects are an "or" relationship.
It should be understood that although the terms first, second, third, etc. may be used in the embodiments of the present application to describe a preset range, etc., these preset ranges should not be limited to these terms. These terms are only used to distinguish one preset range from another. For example, a first preset range may also be referred to as a second preset range, and similarly, a second preset range may also be referred to as a first preset range without departing from the scope of embodiments of the present application.
Depending on the context, the word "if" as used herein may be interpreted as "at … …" or "at … …" or "in response to a determination" or "in response to detection". Similarly, the phrase "if determined" or "if detected (stated condition or event)" may be interpreted as "when determined" or "in response to determination" or "when detected (stated condition or event)" or "in response to detection (stated condition or event), depending on the context.
FIG. 1 is a flow chart of an access request response method in an embodiment of the present application. The access request response method can be applied to the scene that the application program realizes certain functional operations, and can be realized on terminal equipment such as mobile phones, tablets, wearable equipment and the like. As shown in fig. 1, the access request response method includes the steps of:
s10: the client sends a first type request to the server, wherein the first type request is used for acquiring time characteristic data and an encryption key of the server, and the time characteristic data is determined according to the acquisition time.
In this embodiment, the request that an application on a client interacts with a server to perform some functional operations is divided into two phases, where the first phase is a first type of request, and the first type of request is mainly used for encrypting and verifying information between the client and the server, so that the server can prevent the situation of repeatedly responding to the same request of the client. The server may receive requests of a first type sent by multiple clients simultaneously.
Specifically, the first type of request is for acquiring time characteristic data and an encryption key of a server. The encryption key is used for encrypting interaction information between the client and the server, so that the security in information interaction can be improved. The time feature data refers to data which is generated by the server and is related to time and used for verification, and in the embodiment of the application, the characteristic that the time has unique timeliness can be used for judging whether a request which is received by the server and requires to execute a certain operation is repeated or not, so that the function of repeatedly verifying the request is realized at the server side. Further, the time feature data is determined according to the acquisition time, such as a time stamp of one of the time feature data, the value of which is determined according to the acquisition time.
S20: the server receives a first type of request, wherein the server stores a decryption key used for decrypting information encrypted by the encryption key.
Wherein the server stores a decryption key and also stores an encryption key. The encryption key may be sent to the client to enable the client to encrypt the sent information, and the decryption key is a private key that decrypts information sent by the client that has been encrypted using the encryption key.
S30: the server transmits the time characteristic data and the encryption key to the client.
S40: the client receives the time characteristic data and the encryption key.
S50: the client generates a client random number.
Wherein the client nonce is used to check the repeatability of the server's received request for performing an operation. In an embodiment, the client random number is related to the generated time, has uniqueness in time, and can realize the repeatability check on the request according to the client random number by the server so as to avoid the server from always responding to the repeated request of the client.
S60: and the client encrypts the data by adopting an encryption key according to the time characteristic data and the client random number to obtain duplicate checking information.
The duplication checking information refers to information for checking whether a request issued by a client is a duplicate request. In the embodiment of the application, the time feature data generated by the server and the time uniqueness of the client random number are adopted to be used for the repeatability check of the server side on the request sent by the client.
Specifically, the time feature data may be a timestamp generated by the server, when the server performs repeatability verification on a request sent by the client, the server may verify the identity of the client according to the received timestamp, determine that the client sends a first type of request to the server, and then determine whether the request sent by the client to the server is a repeated request according to the client random number, and if the received client random numbers are different, the request may be considered to be not repeated.
S70: the client sends a second type request to the server, wherein the second type request comprises request parameters and duplicate checking information.
Where the second type of request refers to a request that requires the server to perform some functional operation. The second type of request comprises a request parameter and duplicate checking information, wherein the request parameter indicates the functional operation to be executed by the client, such as the functional operation of popping up certain designated pages, jumping pages and the like on the application program. And the duplicate checking information determines whether the second type of request is a repeated request sent by the client, and if so, the server does not respond to the corresponding functional operation according to the request parameters.
S80: the server receives the second type of request.
S90: and the server decrypts the duplicate checking information by adopting the decryption key to obtain the time characteristic data and the client random number.
In one embodiment, the time feature data is generated by a server and the client random number is generated by a client, including time-sensitive information generated by two different computer devices. In the embodiment of the application, time characteristic data with timeliness and generated by a client and a server and a client random number are used for repeated verification of a request, and from the perspective of double-side verification, after the client is determined to send a first type request to the server, whether a second type request is repeated or not is judged according to the client random number.
It should be noted that, the first type of request and the second type of request may be regarded as a complete request in general, and in this embodiment of the present application, the server is mainly configured to distinguish between the client that has received the time feature data and the encryption key sent by the server when performing the repeatability check of the request.
S100: the server determines whether to respond to the second type of request according to the request parameters based on the time characteristic data and the client random number.
In an embodiment, the time feature data generated by the server is mainly used for verifying whether the client sends the first type request to the server, and the client random number is mainly used for verifying whether the frequency of sending the second type request is too high, if so, the second type request can be determined as a repeated request, and the operation corresponding to the second type request is refused to be executed.
In step S10-S100, based on the time feature data and the client random number, when the client and the server interact, the server determines whether the second type request sent by the client is repeated based on the time uniqueness of the time feature data and the client random number, so as to determine whether to respond to the second type request according to the request parameter, and execute the function operation corresponding to the request parameter. The embodiment of the application adopts the self-checking method of the server, so that even if an uncontrollable repeated request sending event occurs at the client side, the server can actively avoid excessive interaction with the client side, and the utilization rate of the server resource can be improved.
Further, when the time feature data is a server random number and a timestamp, in step S100, it is determined whether to respond to the second type request according to the request parameter according to the time feature data and the client random number, and specifically includes the following steps:
s10011: and checking the values of the server random numbers sent by the client and the server random numbers stored by the server based on the client ID obtained in advance, and obtaining the timestamp sent by the client and the client random numbers if the values of the server random numbers sent by the client and the server random numbers stored by the server are the same, wherein the client ID and the server random numbers stored by the server have a first mapping relation.
Wherein the server random number is related to the generated time and can be used for checking the identity of the client.
The first mapping relation stores a mapping relation between the client ID and the server random number stored by the server. It will be appreciated that when the server generates a server random number from a received request of the first type, the server random number is stored and the mapping relationship between the server random number and the client ID that sent the request of the first type is stored.
It may be appreciated that the second type of request sent by the client to the server includes the server random number sent by the client, and in this embodiment, the value verification is performed by using the server random number sent by the client and the server random number stored by the server.
In an embodiment, the server and the client simultaneously send the server ID and the client ID to each other in the interaction process, when checking the values of the server random number sent by the client and the server random number stored by the server, the server may first obtain the client ID, then determine, according to the first mapping relationship established in advance, the value of the server random number generated by the server when the first type request is received according to the client ID, and compare the value with the value of the server random number sent by the client at this time, and if the values of the server random number sent by the client and the server random number stored by the server are the same, may initially consider that the client has just sent the first type request to the server in the near future.
S10012: and checking the timestamp sent by the client and the timestamp stored by the server based on the pre-acquired client ID, wherein the client ID and the timestamp stored by the server have a second mapping relation.
The second mapping relation stores a mapping relation between the client ID and a timestamp stored by the server.
It will be appreciated that the server random numbers may initially screen out requests of a second type that may require corresponding functional operations to be performed, but may include repeated requests of a second type that have the same server random number but different time stamps. It will be appreciated that in a small time interval (e.g. 1 ms) the larger probability of the generated random number is the same (the random number is random beyond a certain time interval to achieve the effect of randomness), then it is possible to generate multiple identical server random numbers under different time stamps, and therefore, adding the decision to the time stamp can determine that there are more repeated requests. In the embodiment of the application, the timestamp sent by the client and the timestamp stored by the server are checked by using the second mapping relation to determine the repeated requests with different timestamps and same server random numbers.
S10013: and if the time stamp sent by the client is different from the time stamp stored by the server, refusing to respond to the second type request.
It will be appreciated that due to the uniqueness of the time stamps, for requests of the second type, where the server random numbers are the same but the time stamps are different, the server may be considered as duplicate requests, refusing to execute these requests of the second type.
S10014: and if the time stamp sent by the client is the same as the time stamp stored by the server, comparing the client random number with the client comparison random number generated in the first preset time region.
The client side compares the random number with the random number generated by the client side, and mainly aims to distinguish the random number from the random number of the client side generated by the client side after receiving the time characteristic parameter, and the purpose of the generation is to compare the random number of the client side generated by the client side after receiving the time characteristic parameter. The client-side comparison random number is generated in the first preset time zone in the embodiment and comprises a plurality of client-side comparison random numbers.
Further, even if the server random numbers of the second type of requests are the same and the time stamps are the same, the problem of repeated requests still occurs. It may be appreciated that, after the time feature data generated at the same time is sent to the client, the client may generate a plurality of client random numbers in the first preset time area under the influence of a retransmission factor such as a timer, and generate a plurality of second type requests to send to the server. In the embodiment of the application, the random number of the client is compared with the comparison random number of the client generated in the first preset time zone according to the characteristics of the generated random number of the client (the random numbers generated by the client are the same in the smaller time zone). The first preset time zone is a smaller time zone, and the values generated by the client random numbers in the time zone are the same.
S10015: if the value comparison result of the client side random number and the client side comparison random number generated in the first preset time area is the same as the value, responding to the first received second type request according to the request parameter.
In this embodiment of the present application, if the value comparison result of the client random number and the client comparison random number generated in the first preset time area is the same as the value, it may be considered that there are multiple repeated second type requests, then only the first received second type request is executed, or only one of the received second type requests is executed.
In the steps S10011-S10015, the second type request repeatedly sent by the client can be judged by using the rule of random number generation and the uniqueness of the time stamp, so that excessive interaction between the client and the server is prevented, access request response can be more reasonably realized, and the utilization rate of server resources is effectively improved.
Further, when the time feature data is the identification index, in step S100, it is determined whether to respond to the second type request according to the request parameter according to the time feature data and the client random number, and the method specifically includes the following steps:
s10021: the server verifies the index value identifying the index.
The identification index may be an identification that uniquely identifies the functional operation corresponding to the second type request. The identification index is temporarily available to be used to verify that duplicate second type requests are distinguished.
The identification index may be specifically generated by the server when the first type request is sent to the server, and temporarily stored in the cache, so as to distinguish the second type requests of different types according to the identification index, and reject to execute the repeated response. In an embodiment, if the time feature data is the identification index, it may be determined whether the second type request is repeated according to the identification index.
S10022: if there is an index value identical to the index, the server responds to the second type request according to the request parameters based on the index.
S10023: if the index value which is larger than one and is the same as the identification index exists, numerical comparison is carried out on the client random number and the client comparison random number generated in the second preset time area, wherein the request corresponding to the client random number is a request corresponding to the identification index with the same index value.
It will be appreciated that if there is only one index value that is the same as the index of the identity, then it is stated that there is and only one request of the second type needs to be responded to; if there is more than one index value that is the same as the index, it is stated that there may be multiple duplicate requests of the second type.
S10024: if the comparison result of the client random number and the client comparison random number generated in the second preset time area is the same as the numerical value, responding to the first received second type request according to the request parameter.
In order to prevent the situation that the second type request is possibly rejected by mistake due to overlong existing time of the identification index, the embodiment of the application takes the index value which is the same as the identification index as a screening condition, screens out the second type request which is the same as the identification index and is used for making the numerical comparison of the client random number and the client contrast random number generated in a second preset time area, if the client contrast random number in the second time area (the second preset time area is a smaller time area and is as small as the random number generated by the client in the time area) is the same, and on the premise that the screening is completed, a plurality of second type requests are considered to be the same, only the first received second type request is processed at the moment, or one of the second type requests can be processed. In this way, situations where false rejections may occur with the identification index may be avoided.
In step S10021-S10024, the combination of the identification index and the client random number is adopted to determine the possible repeated requests, firstly, the identification index is used to screen the possible repeated second-class requests, and then, whether the repeated second-class requests exist or not is determined in the screened second-class requests through the client random number, so that the repeated verification of the second-class requests can be rapidly realized.
Further, before step S10, i.e. before receiving the request of the first type, the method further comprises:
and in a test stage of determining the time of the identification index in the cache, if the index value which is the same as the identification index does not exist, the time of the identification index in the cache is prolonged according to the preset time amount.
It will be appreciated that the time that the index is identified as being in the cache is limited and short, and that too long may falsely reject a response to a request. In one embodiment, an implementation is provided that determines a time when an identification index is present in a cache. Specifically, in the test stage, if none of the index values identical to the index value of the index indicates that the index value of the index disappears too quickly, the time for which the index exists in the cache should be prolonged after the successive test according to the preset time until the index value identical to the index value of the index is present. The time for which the index exists can be set to be smaller just at the beginning, and then the optimal time is tested according to a plurality of tests.
It will be appreciated that the presence of an identification index too long can affect normal responses and take up capacity, and that the presence of an identification index too short can not be effective in responding to a request. The embodiment of the application provides a specific implementation mode for identifying the existence duration of the index, which can obtain more reasonable identification of the existence duration of the index.
Further, in step S60, that is, the client encrypts the check information by using the encryption key according to the time feature data and the client random number, the method specifically further includes the following steps:
s61: and the client splices the time characteristic data and the client random number in a preset splicing mode to obtain splicing information.
S62: and the client encrypts the spliced information by adopting the encryption key to obtain duplicate checking information.
The preset splicing mode can be preset by the client and the server, and after the server decrypts the duplicate checking information, the server can disassemble the splicing information based on the preset splicing mode to obtain time characteristic data and the client random number.
In step S61-S62, the time characteristic data and the client random number are spliced in a preset splicing manner, so that the security of information transmission can be further improved.
In the embodiment of the application, based on the time feature data and the client random number, when the client and the server interact, the server judges whether the second type request sent by the client is repeated or not based on the time uniqueness of the time feature data and the client random number, so as to determine whether to respond to the second type request according to the request parameter and execute the function operation corresponding to the request parameter. The embodiment of the application adopts the self-checking method of the server, so that even if an uncontrollable repeated request sending event occurs at the client side, the server can actively avoid excessive interaction with the client side, and the utilization rate of the server resource can be improved.
Further, in combination with the server random number and the time stamp, more existing duplicate requests can be determined.
Further, by utilizing the rule of random number generation and the uniqueness of the time stamp, the second type request repeatedly sent by the client can be judged, so that excessive interaction between the client and the server is prevented, access request response can be more reasonably realized, and the utilization rate of server resources is effectively improved.
Further, the second type of requests which are possibly repeated are screened by using the identification index, and then whether the second type of requests which are repeated exist is determined in the screened second type of requests through the client random number, so that the repeatability verification of the second type of requests can be rapidly realized.
Further, the existence of the identification index affects normal response and occupies capacity, and the existence of the identification index is too short and does not occur even if the identification index responds to a request.
Furthermore, the time characteristic data and the client random number are spliced in a preset splicing mode, so that the safety of information transmission can be further improved.
It should be understood that the sequence number of each step in the foregoing embodiment does not mean that the execution sequence of each process should be determined by the function and the internal logic of each process, and should not limit the implementation process of the embodiment of the present application in any way.
Fig. 2 is a schematic block diagram of an apparatus according to an embodiment of the present application, which corresponds to an access request response method executed by a server one by one. As shown in fig. 2, the access request responding means executed by the server includes a first receiving module 10, a first transmitting module 20, a second receiving module 30, a decrypting module 40, and a response determining module 50. The implementation functions of the first receiving module 10, the first sending module 20, the second receiving module 30, the decryption module 40, and the response determining module 50 correspond to the steps corresponding to the access request response method executed by the server one by one, and in order to avoid redundancy, this embodiment is not described in detail one by one.
Further, when the time characteristic data is a server random number and a timestamp, the response determining module 50 is specifically configured to:
and checking the values of the server random numbers sent by the client and the server random numbers stored by the server based on the client ID obtained in advance, and obtaining the timestamp sent by the client and the client random numbers if the values of the server random numbers sent by the client and the server random numbers stored by the server are the same, wherein the client ID and the server random numbers stored by the server have a first mapping relation.
And checking the timestamp sent by the client and the timestamp stored by the server based on the pre-acquired client ID, wherein the client ID and the timestamp stored by the server have a second mapping relation.
And if the time stamp sent by the client is different from the time stamp stored by the server, refusing to respond to the second type request.
And if the time stamp sent by the client is the same as the time stamp stored by the server, comparing the client random number with the client comparison random number generated in the first preset time region.
If the value comparison result of the client side random number and the client side comparison random number generated in the first preset time area is the same as the value, responding to the first received second type request according to the request parameter.
Further, when the temporal feature data is an identification index, the response determination module 50 is specifically configured to:
the check identifies the index value of the index.
If the index value which is the same as the identification index exists, the second type request is responded according to the request parameter based on the identification index.
If the index value which is larger than one and is the same as the identification index exists, numerical comparison is carried out on the client random number and the client comparison random number generated in the second preset time area, wherein the request corresponding to the client random number is a request corresponding to the identification index with the same index value.
If the comparison result of the client random number and the client comparison random number generated in the second preset time area is the same as the numerical value, responding to the first received second type request according to the request parameter.
Further, the access request response device executed by the server is specifically configured to:
and in a test stage of determining the time of the identification index in the cache, if the index value which is the same as the identification index does not exist, the time of the identification index in the cache is prolonged according to the preset time amount.
Fig. 3 is a schematic block diagram of an apparatus according to an embodiment of the present application, which corresponds to an access request response method performed by a client one by one. As shown in fig. 3, the access request responding apparatus executed by the client includes a second transmitting module 60, a third receiving module 70, a generating module 80, an encrypting module 90, and a third transmitting module 100. The implementation functions of the second sending module 60, the third receiving module 70, the generating module 80, the encrypting module 90, and the third sending module 100 are in one-to-one correspondence with the steps corresponding to the access request response method executed by the client, and in order to avoid redundancy, this embodiment is not described in detail.
Further, the encryption module 90 is specifically configured to:
And splicing the time characteristic data and the client random number by adopting a preset splicing mode to obtain splicing information.
And encrypting the spliced information by adopting an encryption key to obtain duplicate checking information.
FIG. 4 is a schematic diagram of a computer device in an embodiment of the present application.
As shown in fig. 4, computer device 110 includes a processor 111, a memory 112, and computer readable instructions 113 stored in memory 112 and executable on processor 111. The processor 111, when executing the computer readable instructions 113, implements the steps of an access request response method performed by a server or client. Alternatively, the processor 111, when executing the computer readable instructions 113, performs the functions of the various modules/units of the access request response device that are executed by the server or client.
Illustratively, the computer readable instructions 113 may be partitioned into one or more modules/units, which are stored in the memory 112 and executed by the processor 111 to complete the present application. One or more of the modules/units may be a series of computer readable instructions capable of performing a particular function, the instruction describing the execution of the computer readable instructions 113 in the computer device 110.
The computer device 110 may be a desktop computer, a notebook computer, a palm computer, a cloud server, or the like. Computer devices may include, but are not limited to, a processor 111, a memory 112. It will be appreciated by those skilled in the art that fig. 4 is merely an example of computer device 110 and is not intended to limit computer device 110, and may include more or fewer components than shown, or may combine certain components, or different components, e.g., a computer device may also include an input-output device, a network access device, a bus, etc.
The processor 111 may be a central processing unit (Central Processing Unit, CPU), but may also be other general purpose processors, digital signal processors (Digital Signal Processor, DSP), application specific integrated circuits (Application Specific Integrated Circuit, ASIC), field programmable gate arrays (Field-Programmable Gate Array, FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, or the like. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
The memory 112 may be an internal storage unit of the computer device 110, such as a hard disk or memory of the computer device 110. The memory 112 may also be an external storage device of the computer device 110, such as a plug-in hard disk provided on the computer device 110, a Smart Media Card (SMC), a Secure Digital (SD) Card, a Flash Card (Flash Card), or the like. Further, the memory 112 may also include both internal storage units and external storage devices of the computer device 110. Memory 112 is used to store computer readable instructions as well as other programs and data required by the computer device. The memory 112 may also be used to temporarily store data that has been output or is to be output.
The embodiment of the application can acquire and process the related data based on the artificial intelligence technology. Among these, artificial intelligence (Artificial Intelligence, AI) is the theory, method, technique and application system that uses a digital computer or a digital computer-controlled machine to simulate, extend and extend human intelligence, sense the environment, acquire knowledge and use knowledge to obtain optimal results.
Artificial intelligence infrastructure technologies generally include technologies such as sensors, dedicated artificial intelligence chips, cloud computing, distributed storage, big data processing technologies, operation/interaction systems, mechatronics, and the like. The artificial intelligence software technology mainly comprises a computer vision technology, a robot technology, a biological recognition technology, a voice processing technology, a natural language processing technology, machine learning/deep learning and other directions.
In this embodiment of the present application, the server may be an independent server, or may be a cloud server that provides cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, content delivery networks (ContentDelivery Network, CDN), and basic cloud computing services such as big data and artificial intelligence platforms.
It will be apparent to those skilled in the art that, for convenience and brevity of description, only the above-described division of the functional units and modules is illustrated, and in practical application, the above-described functional distribution may be performed by different functional units and modules according to needs, i.e. the internal structure of the apparatus is divided into different functional units or modules to perform all or part of the above-described functions.
In addition, each functional unit in each embodiment of the present application may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit. The integrated units may be implemented in hardware or in software functional units.
The integrated modules/units, if implemented in the form of software functional units and sold or used as stand-alone products, may be stored in a computer readable storage medium. Based on such understanding, the present application implements all or part of the flow of the method of the above embodiments, and may also be implemented by means of computer readable instructions to instruct related hardware, where the computer readable instructions may be stored in a computer readable storage medium, where the computer readable instructions, when executed by a processor, implement the steps of the method embodiments described above. Wherein the computer readable instructions comprise computer readable instruction code which may be in the form of source code, object code, executable files, or in some intermediate form, etc. The computer readable medium may include: any entity or device capable of carrying the computer readable instruction code, a recording medium, a USB flash disk, a removable hard disk, a magnetic disk, an optical disk, a computer Memory, a Read-Only Memory (ROM), a random access Memory (RAM, random Access Memory), an electrical carrier wave signal, a telecommunications signal, a software distribution medium, and so forth. It should be noted that the computer readable medium may include content that is subject to appropriate increases and decreases as required by jurisdictions in which such content is subject to legislation and patent practice, such as in certain jurisdictions in which such content is not included as electrical carrier signals and telecommunication signals.
The present application also provides a computer-readable storage medium storing computer-readable instructions that, when executed by a processor, implement an access request response method performed by a server, or that, when executed by a processor, implement an access request response method performed by a client.
The above embodiments are only for illustrating the technical solution of the present application, and are not limiting thereof; although the present application has been described in detail with reference to the foregoing embodiments, it should be understood by those of ordinary skill in the art that: the technical scheme described in the foregoing embodiments can be modified or some technical features thereof can be replaced by equivalents; such modifications and substitutions do not depart from the spirit and scope of the technical solutions of the embodiments of the present application, and are intended to be included in the scope of the present application.

Claims (10)

1. An access request response method, characterized by comprising the steps performed by a server of:
receiving a first type of request, wherein the first type of request is used for acquiring time characteristic data and an encryption key of the server, the server stores a decryption key, the decryption key is used for decrypting information encrypted by the encryption key, and the time characteristic data is determined according to the acquisition time;
Transmitting the time feature data and the encryption key to a client;
receiving a second type request, wherein the second type request comprises request parameters and duplicate checking information, the duplicate checking information is obtained by encrypting the encryption key according to the time characteristic data and a client random number, and the client random number is generated by the client;
decrypting the duplicate checking information by adopting the decryption key to obtain the time characteristic data and the client random number;
determining whether to respond to the second type request according to the request parameters according to the time characteristic data and the client random number; comprising the following steps:
when the time characteristic data are server random numbers and time stamps, checking the values of the server random numbers sent by the client and the server random numbers stored by the server, and if the values of the server random numbers sent by the client and the server random numbers stored by the server are the same, acquiring the time stamps sent by the client and the client random numbers;
if the time stamp sent by the client is different from the time stamp stored by the server, rejecting to respond to the second type request; if the time stamp sent by the client is the same as the time stamp stored by the server, comparing the client random number with a client comparison random number generated in a first preset time area; if the numerical comparison result of the client random number and the client comparison random number generated in the first preset time area is the same as the numerical value, responding to the first received second type request according to the request parameter;
When the time feature data is an identification index, if an index value which is the same as the identification index exists, responding to the second type request according to the request parameter based on the identification index; if the index value which is larger than one and is the same as the identification index exists, comparing the client random number with the client comparison random number generated in a second preset time area, wherein the request corresponding to the client random number is a request corresponding to the identification index with the same index value; and if the comparison result of the client-side random number and the client-side comparison random number generated in the second preset time area is the same as the numerical value, responding to the first received second type request according to the request parameter.
2. The method according to claim 1, wherein the method further comprises:
based on a pre-acquired client ID, verifying the server random number sent by the client and the numerical value of the server random number stored by the server, wherein a first mapping relation exists between the client ID and the server random number stored by the server;
and checking the timestamp sent by the client and the timestamp stored by the server based on a pre-acquired client ID, wherein a second mapping relation exists between the client ID and the timestamp stored by the server.
3. The method according to claim 1, wherein the method further comprises:
and checking the index value of the identification index.
4. A method according to claim 3, wherein prior to said receiving a request of the first type, the method further comprises:
and in a test stage of determining the time when the identification index exists in the cache, if the index value which is the same as the identification index does not exist, the time when the identification index exists in the cache is prolonged according to a preset time amount.
5. An access request response method for preventing excessive interaction between a client and a server, comprising the steps performed by the client of:
sending a first type request to a server, wherein the first type request is used for acquiring time characteristic data and an encryption key of the server;
receiving the time characteristic data and the encryption key;
generating a client random number;
encrypting by adopting the encryption key according to the time characteristic data and the client random number to obtain duplicate checking information;
sending a second type request to the server, wherein the second type request comprises a request parameter and the duplicate checking information, so that the server adopts a decryption key to decrypt the duplicate checking information to obtain the time characteristic data and the client random number; determining whether to respond to the second type request according to the request parameters according to the time characteristic data and the client random number; comprising the following steps:
When the time characteristic data are server random numbers and time stamps, if the time stamps sent by the client are different from the time stamps stored by the server, refusing to respond to the second type request; if the time stamp sent by the client is the same as the time stamp stored by the server, comparing the client random number with a client comparison random number generated in a first preset time area; if the numerical comparison result of the client random number and the client comparison random number generated in the first preset time area is the same as the numerical value, responding to the first received second type request according to the request parameter;
when the time feature data is an identification index, if an index value which is the same as the identification index exists, responding to the second type request according to the request parameter based on the identification index; if the index value which is larger than one and is the same as the identification index exists, comparing the client random number with the client comparison random number generated in a second preset time area, wherein the request corresponding to the client random number is a request corresponding to the identification index with the same index value; and if the comparison result of the client-side random number and the client-side comparison random number generated in the second preset time area is the same as the numerical value, responding to the first received second type request according to the request parameter.
6. The method according to claim 5, wherein encrypting the check repeat information with the encryption key according to the time feature data and the client random number comprises:
splicing the time characteristic data and the client random number in a preset splicing mode to obtain splicing information;
and encrypting the splicing information by adopting the encryption key to obtain the duplicate checking information.
7. An access request response device for performing the method of any of claims 1-4, the device comprising:
the system comprises a first receiving module, a second receiving module and a first receiving module, wherein the first receiving module is used for receiving a first type request, the first type request is used for acquiring time characteristic data and an encryption key of the server, the server stores a decryption key, the decryption key is used for decrypting information encrypted by the encryption key, and the time characteristic data is determined according to the acquisition time;
the first sending module is used for sending the time characteristic data and the encryption key to the client;
the second receiving module is used for receiving a second type request, wherein the second type request comprises request parameters and duplicate checking information, the duplicate checking information is obtained by encrypting the encryption key according to the time characteristic data and a client random number, and the client random number is generated by the client;
The decryption module is used for decrypting the duplicate checking information by adopting the decryption key to obtain the time characteristic data and the client random number;
and the response determining module is used for determining whether to respond to the second type of request according to the request parameters according to the time characteristic data and the client random number.
8. An access request response device for performing the method of claim 5 or 6, the device comprising:
the second sending module is used for sending a first type of request to the server, wherein the first type of request is used for acquiring time characteristic data and an encryption key of the server;
a third receiving module for receiving the time feature data and the encryption key;
the generation module is used for generating a client random number;
the encryption module is used for obtaining duplicate checking information by adopting the encryption key according to the time characteristic data and the client random number;
and the third sending module is used for sending a second type request to the server, wherein the second type request comprises a request parameter and the duplicate checking information.
9. A computer device comprising a memory, a processor and computer readable instructions stored in the memory and executable on the processor, wherein the processor, when executing the computer readable instructions, performs the steps of the access request response method according to any one of claims 1-4 or the processor, when executing the computer readable instructions, performs the steps of the access request response method according to claim 5 or 6.
10. A computer readable storage medium storing computer readable instructions which when executed by a processor perform the steps of the access request response method according to any one of claims 1 to 4 or which when executed by a processor perform the steps of the access request response method according to claim 5 or 6.
CN202111161126.3A 2021-09-30 2021-09-30 Access request response method, device, computer equipment and storage medium Active CN113922952B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202111161126.3A CN113922952B (en) 2021-09-30 2021-09-30 Access request response method, device, computer equipment and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202111161126.3A CN113922952B (en) 2021-09-30 2021-09-30 Access request response method, device, computer equipment and storage medium

Publications (2)

Publication Number Publication Date
CN113922952A CN113922952A (en) 2022-01-11
CN113922952B true CN113922952B (en) 2024-03-01

Family

ID=79237653

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202111161126.3A Active CN113922952B (en) 2021-09-30 2021-09-30 Access request response method, device, computer equipment and storage medium

Country Status (1)

Country Link
CN (1) CN113922952B (en)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114422259B (en) * 2022-01-26 2022-10-28 宋舒涵 Internet resource monitoring and distributing method facing high concurrent data request

Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106559217A (en) * 2015-09-29 2017-04-05 腾讯科技（深圳）有限公司 A kind of dynamic encrypting method, terminal, server
CN107454115A (en) * 2017-10-10 2017-12-08 北京奇艺世纪科技有限公司 A kind of abstract identification method and digest authentication system
CN108521393A (en) * 2018-01-31 2018-09-11 世纪龙信息网络有限责任公司 Data interactive method, device, system, computer equipment and storage medium
CN108616350A (en) * 2018-03-20 2018-10-02 如般量子科技有限公司 A kind of HTTP-Digest class AKA identity authorization systems and method based on pool of symmetric keys
CN110138772A (en) * 2019-05-13 2019-08-16 上海英恒电子有限公司 A kind of communication means, device, system, equipment and storage medium
CN111130798A (en) * 2019-12-24 2020-05-08 中国平安人寿保险股份有限公司 Request authentication method and related equipment
CN113067828A (en) * 2021-03-25 2021-07-02 中国建设银行股份有限公司 Message processing method and device, server, computer equipment and storage medium

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7231663B2 (en) * 2002-02-04 2007-06-12 General Instrument Corporation System and method for providing key management protocol with client verification of authorization
US10481872B2 (en) * 2017-08-29 2019-11-19 Colossio, Inc. Cryptographically secure random number generator

Patent Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106559217A (en) * 2015-09-29 2017-04-05 腾讯科技（深圳）有限公司 A kind of dynamic encrypting method, terminal, server
CN107454115A (en) * 2017-10-10 2017-12-08 北京奇艺世纪科技有限公司 A kind of abstract identification method and digest authentication system
CN108521393A (en) * 2018-01-31 2018-09-11 世纪龙信息网络有限责任公司 Data interactive method, device, system, computer equipment and storage medium
CN108616350A (en) * 2018-03-20 2018-10-02 如般量子科技有限公司 A kind of HTTP-Digest class AKA identity authorization systems and method based on pool of symmetric keys
CN110138772A (en) * 2019-05-13 2019-08-16 上海英恒电子有限公司 A kind of communication means, device, system, equipment and storage medium
CN111130798A (en) * 2019-12-24 2020-05-08 中国平安人寿保险股份有限公司 Request authentication method and related equipment
CN113067828A (en) * 2021-03-25 2021-07-02 中国建设银行股份有限公司 Message processing method and device, server, computer equipment and storage medium

Also Published As

Publication number Publication date
CN113922952A (en) 2022-01-11

Similar Documents

Publication Publication Date Title
CN108243188B (en) Interface access, interface call and interface verification processing method and device
CN114900338B (en) Encryption and decryption method, device, equipment and medium
CN112788036B (en) Identity verification method and device
CN108512845B (en) Interface calling verification method and device
CN111104675A (en) Method and device for detecting system security vulnerability
CN108768928B (en) Information acquisition method, terminal and server
JP2019519849A (en) Method and device for preventing attacks on servers
CN113922952B (en) Access request response method, device, computer equipment and storage medium
CN114021103A (en) Single sign-on method, device, terminal and storage medium based on identity authentication
CN111259428A (en) Data processing method and device based on block chain, node equipment and storage medium
CN114239026A (en) Information desensitization conversion processing method, device, computer equipment and storage medium
CN112132576B (en) Payment information processing method based on block chain communication and block chain information platform
CN113489741A (en) Password resetting method and device for Internet of things platform, Internet of things server and medium
CN111371811A (en) Resource calling method, resource calling device, client and service server
CN107395350B (en) Method and system for generating key and key handle and intelligent key safety equipment
CN114036546A (en) Identity verification method and device based on mobile phone number, computer equipment and medium
CN110769010B (en) Data management authority processing method and device and computer equipment
CN115935388B (en) Software package safe sending method, device, equipment and storage medium
CN111163466A (en) Method for 5G user terminal to access block chain, user terminal equipment and medium
CN112311716A (en) Data access control method and device based on openstack and server
CN112134705A (en) Data authentication method and device, storage medium and electronic device
CN114157712B (en) Data processing method, device, equipment and storage medium
CN114679336B (en) Authentication method, authentication system, authentication device, and readable storage medium
CN112559825B (en) Service processing method, device, computing equipment and medium
CN114449514B (en) Key generation method, device, equipment and medium

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
TA01 Transfer of patent application right
TA01 Transfer of patent application right

Effective date of registration: 20240122

Address after: 518000 Room 202, block B, aerospace micromotor building, No.7, Langshan No.2 Road, Xili street, Nanshan District, Shenzhen City, Guangdong Province

Applicant after: Shenzhen LIAN intellectual property service center

Country or region after: China

Address before: 518000 Room 201, building A, 1 front Bay Road, Shenzhen Qianhai cooperation zone, Shenzhen, Guangdong

Applicant before: PING AN PUHUI ENTERPRISE MANAGEMENT Co.,Ltd.

Country or region before: China

Effective date of registration: 20240122

Address after: 518000, 2-25A, Fulian Building, Lianhua North, Futian District, Shenzhen, Guangdong Province

Applicant after: Peng Ling

Country or region after: China

Applicant after: Cao Xing

Applicant after: Huang Shuyue

Applicant after: Ma Pengzhan

Address before: 518000 Room 202, block B, aerospace micromotor building, No.7, Langshan No.2 Road, Xili street, Nanshan District, Shenzhen City, Guangdong Province

Applicant before: Shenzhen LIAN intellectual property service center

Country or region before: China

TA01 Transfer of patent application right
TA01 Transfer of patent application right

Effective date of registration: 20240204

Address after: W402, Shenzhen Hong Kong industry university research base, 015 Gaoxin South 7th Road, high tech Zone community, Yuehai street, Nanshan District, Shenzhen, Guangdong 518000

Applicant after: Hengzhong Chuangmei (Shenzhen) Development Partnership Enterprise (L.P.)

Country or region after: China

Address before: 518000, 2-25A, Fulian Building, Lianhua North, Futian District, Shenzhen, Guangdong Province

Applicant before: Peng Ling

Country or region before: China

Applicant before: Cao Xing

Applicant before: Huang Shuyue

Applicant before: Ma Pengzhan

GR01 Patent grant
GR01 Patent grant