CN115470246A - CDN-based request response method, electronic equipment and storage medium - Google Patents
CDN-based request response method, electronic equipment and storage medium Download PDFInfo
- Publication number
- CN115470246A CN115470246A CN202211124866.4A CN202211124866A CN115470246A CN 115470246 A CN115470246 A CN 115470246A CN 202211124866 A CN202211124866 A CN 202211124866A CN 115470246 A CN115470246 A CN 115470246A
- Authority
- CN
- China
- Prior art keywords
- cache
- server
- identifier
- response data
- request
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/24—Querying
- G06F16/245—Query processing
- G06F16/2455—Query execution
- G06F16/24552—Database cache management
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/0703—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
- G06F11/0793—Remedial or corrective actions
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/22—Indexing; Data structures therefor; Storage structures
- G06F16/2228—Indexing structures
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/24—Querying
- G06F16/245—Query processing
- G06F16/2453—Query optimisation
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D30/00—Reducing energy consumption in communication networks
- Y02D30/50—Reducing energy consumption in communication networks in wire-line communication networks, e.g. low power modes or reduced link rate
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Databases & Information Systems (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Data Mining & Analysis (AREA)
- Computational Linguistics (AREA)
- Software Systems (AREA)
- Quality & Reliability (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention provides a request response method, electronic equipment and a storage medium based on a CDN (content delivery network), wherein the method comprises the following steps of: receiving a data acquisition request, and if the request type identifier is a first type service identifier, sending the data acquisition request to a second server; receiving first response data returned by the second server in response to the data acquisition request, and sending the first response data to the target terminal; if the request type identification is the second type service identification or the third type service identification, the target query index is used for querying the first database; if the cache information does not exist, sending a data acquisition request to a second server; receiving second response data and sending the second response data to the target terminal; and storing the second response data to the first database. The method and the device effectively relieve the query pressure of the second server, reduce the abnormal situation of the second server caused by overlarge access pressure, and simultaneously relieve the unfriendly experience that the client immediately displays the abnormal data to the user because the second server is abnormal.
Description
Technical Field
The present invention relates to the field of data request response, and in particular, to a request response method based on a CDN, an electronic device, and a storage medium.
Background
When hot news or an emergency occurs, a large amount of access data can be flooded into a server of an application client, so that pressure is applied to the server, even the server is crashed, the client loses the support of data service, all network requests and data query interaction are invalid requests, and very unfriendly experience is brought to a user.
Disclosure of Invention
Aiming at the technical problem, the technical scheme adopted by the invention is as follows:
a request response method based on a CDN is applied to a first server, the first server is connected with a first database, a second server and a plurality of target terminals, and the first server is used for acquiring corresponding response data from the second server or the first database according to a data acquisition request acquired from the target terminals and returning the response data to the target terminals;
the CDN-based request response method comprises the following steps:
s100, if a data acquisition request sent by a target terminal is received under the condition that a configuration bit of a first server is a first identifier, executing a step S200; the data acquisition request comprises domain name information, an identity identifier, a terminal identifier, a request category identifier and service protocol information;
s200, if the request type identifier is a first type service identifier, executing a step S310;
if the request type identifier is the second type service identifier or the third type service identifier, executing step S410;
the first server is configured to cache corresponding response data to the first database after the response data corresponding to the second type of service identifier or the third type of service identifier is acquired from the second server, and not cache the response data corresponding to the first type of service identifier to the first database; the cache aging of the response data corresponding to the second type of service identification is smaller than that of the response data corresponding to the third type of service identification;
s310, sending a data acquisition request to a second server;
s320, receiving first response data returned by the second server in response to the data acquisition request, sending the first response data to the target terminal, and ending the method;
s410, determining a target index generation method according to the request category identification;
s420, generating a target query index according to a target index generation method, and querying in a first database by using the target query index; if the first database does not have the cache information of which the corresponding cache identifier is the same as the target query index, executing step S430;
s430, sending a data acquisition request to a second server;
s440, receiving second response data returned by the second server in response to the data acquisition request, and sending the second response data to the target terminal;
s450, storing the second response data serving as cache information to a first database; and the cache identifier of the second response data is the target query index corresponding to the data acquisition request, and the method is ended.
The invention has at least the following beneficial effects:
according to the data acquisition request of different request category identifications and different request response methods, if the request category identification is the second service identification or the third service identification, whether corresponding cache information exists in the first database is inquired firstly, if the corresponding cache information exists, the cache information is directly called to the target terminal, if the corresponding cache information does not exist, the second server is used for acquiring response data, the response data is sent to the target terminal and is stored in the first database as the cache information, so that when a user sends the same data acquisition request again in an effective time period of cache timeliness, the cache information in the first database can be directly called without obtaining the response data in the second server, the inquiry pressure of the second server is effectively relieved, and the abnormal condition of the second server caused by overlarge access pressure is reduced. Further, even if the second server is abnormal, the second server can strive for effective recovery time through the support of effective cache information in the first database, and meanwhile unfriendly experience that the client displays abnormal data to a user immediately due to the fact that the second server is abnormal can be relieved.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings needed to be used in the description of the embodiments will be briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.
Fig. 1 is a schematic diagram of a system for responding to a data acquisition request based on a CDN according to an embodiment of the present invention.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be obtained by a person skilled in the art without inventive step based on the embodiments of the present invention, are within the scope of protection of the present invention.
A request response method based on a CDN is used for carrying out data response on different requests of a user through a CDN technology and relieving the pressure of a server.
Fig. 1 is a schematic diagram of a system for responding to a data acquisition request based on a CDN, where a first server is used to implement a request response method based on the CDN, the first server may be a CDN server, and the CDN (Content Delivery Network) is a Content Delivery Network, also called a Content Delivery Network, and is an intelligent virtual Network built on an existing Network basis. The first server is connected with a first database, a second server and a plurality of target terminals, the first database is a data storage space of the first server, the second server can be a data processing server of a navigation department, the target terminals can be mobile phone ends of users or other data sending ends capable of sending requests, and the first server is used for obtaining corresponding response data from the second server or the first database according to data obtaining requests obtained from the target terminals and returning the response data to the target terminals.
The CDN-based request response method comprises the following steps:
s100, if a data acquisition request sent by a target terminal is received under the condition that a configuration bit of a first server is a first identifier, executing a step S200; the data acquisition request comprises domain name information, an identity identifier, a terminal identifier, a request category identifier and service protocol information; the data acquisition request can be a personal information query request sent by a user or a public information query request, wherein domain name information is a data website of the data acquisition request, an identity identifier is identity information of the user, a terminal identifier is identification information of a target terminal, a request type identifier is type information of the data acquisition request, service protocol information is a protocol number or a protocol version number of the data acquisition request, and the identity identifier and the terminal identifier of different users are different, so that the data acquisition request sent by each target terminal is different, even if the request type identifiers are the same, namely request events corresponding to the data acquisition requests are the same, and the specific component information of the corresponding data acquisition requests are also different;
the step S100 further includes:
s101, under the condition that the configuration bit of the first server is the second identifier and within a set time length, when the number of acquired data acquisition requests for the third response data is larger than a set threshold value, the configuration bit is adjusted to be the first identifier; the service identifier corresponding to the third response data is a third type service identifier;
setting the time length as a preset time period, for example, within ten hours or within a natural day, the acquired third response data may be request response data of public information, then the service identifier corresponding to the third response data, that is, the third type service identifier may be a request identifier for querying the public information, and the set threshold is a preset request quantity threshold, and when the quantity of the data acquisition requests of the third type service identifier is within the set time length and is greater than the set threshold, it indicates that the data access quantity of the data acquisition requests within the preset time is greater than that at ordinary times, and it may be considered as a query request of the public information, then the configuration bit of the first server is adjusted from the second identifier to the first identifier. The first identifier and the second identifier are conditions for judging whether the data acquisition request applies the CDN technology, and if the configuration bit of the first server is the second identifier, the number of the data acquisition requests for the third type of service identifier is small, the first server is in a normal operation state, and the CDN technology does not need to be applied; if the configuration bit of the first server is the first identifier, it indicates that the number of data acquisition requests for the third type of service identifier suddenly increases, and if an emergency or hot news occurs, the number of requests for a user to search for a keyword suddenly increases, and the data processing pressure of the second server increases, the processing pressure of the second server is relieved by using the CDN technology.
S200, if the request type identifier is a first type service identifier, executing a step S310;
if the request type identifier is the second type service identifier or the third type service identifier, step S410 is executed;
after the second server acquires the response data corresponding to the second service identifier or the third service identifier, the first server caches the corresponding response data to the first database, and does not cache the response data corresponding to the first service identifier to the first database; the cache aging of the response data corresponding to the second type of service identification is smaller than that of the response data corresponding to the third type of service identification;
and caching the response data of the data acquisition request corresponding to the second type of service identification or the third type of service identification in the first database, and setting the caching time. The first service identifier may be a request category identifier of a data acquisition request for starting a related service, and the second service identifier may be a request category identifier of a data acquisition request related to personal information of a user, such as flight travel information of a purchased ticket queried by the user; the third type of service identifier may be a request type identifier of a data acquisition request related to public information, such as a user querying weather information on the day of flight departure. Because the personal information of the user is involved, the cache aging of the response data corresponding to the second service identification is smaller than that of the response data corresponding to the third service identification, and because the first service identification is a request for starting data, the first service identification has no aging requirement and does not influence the normal use of the user even in the network peak period.
S310, sending a data acquisition request to a second server;
s320, receiving first response data returned by the second server in response to the data acquisition request, sending the first response data to the target terminal, and ending the method;
steps S310 to S320 are data processing methods for a data acquisition request with a request type identifier being a first type service identifier, and first response data returned by the data acquisition request with the first type service identifier is directly returned to the target terminal without passing through the cache of the first database.
S410, determining a target index generation method according to the request category identification;
s420, generating a target query index according to a target index generation method, and querying in a first database by using the target query index; if the first database does not have the cache information with the corresponding cache identifier being the same as the target query index, executing step S430;
the step S420 further includes:
if the corresponding cache information with the cache identification same as the target query index exists in the first database, calling the cache information and sending the cache information to the target terminal;
the target query index is cache data of a data acquisition request with a request type identifier of a second type service identifier or a third type service identifier, different target query indexes are generated through a target index generation method according to different request type identifiers, when the data acquisition request with the second type service identifier or the third type service identifier passes through a first server, the target query index is used for querying in a first database, if corresponding cache information exists in the first database, namely a query result aiming at the data acquisition request, cache information is directly called from the first database to a target terminal, if the corresponding cache information does not exist in the first database, the cache record or the cache information does not exist in the first database, and the request is queried in a second server before the cache record or the cache information does not exist in the first database.
S430, sending a data acquisition request to a second server;
s440, receiving second response data returned by the second server in response to the data acquisition request, and sending the second response data to the target terminal;
s450, storing the second response data serving as cache information to a first database; the cache identifier of the second response data is a target query index corresponding to the data acquisition request, and the method is ended;
steps S430 to S450 are processing procedures performed by the first server when no cache information exists in the first database, and if no cache information exists in the first database, the data acquisition request is sent to the second server through the first server, the data acquisition request is queried by the second server, the corresponding second response data is returned to the target terminal by the second server, and the second response data is stored into the first database as cache information, so that when the user sends the same data acquisition request again, the second response data can be directly called from the first database, the query processing in the second server is not needed, the access pressure of the second server is reduced, an abnormal situation caused by the fact that the access pressure of the second server is too large is prevented, even if the second server has an abnormal situation, the effective time for recovery is won for the second server through the support of the effective cache information in the first database, and simultaneously, the occurrence of an abnormality of the second server and friendly experience that the client does not give the abnormal data to the user at once can be relieved.
The target query indexes comprise a first target query index and a second target query index; when the first target query index is the request type identifier and is the second type service identifier, generating a target query index according to a target index generation method; when the second target query index is the request type identifier and is the third type service identifier, generating a target query index according to a target index generation method;
the cache information comprises first cache information and second cache information; the first cache information is second response data returned by the second server in response to the data acquisition request aiming at the first target query index; the second cache information is second response data returned by the second server in response to the data acquisition request aiming at the second target query index;
the first type of service identification has no corresponding target query index and cache information, and the corresponding response data is first response data;
the target query index corresponding to the second service identifier is a first target query index, the corresponding cache information is first cache information, and the corresponding response data is second response data;
the target query index corresponding to the third type of service identifier is a second target query index, the corresponding cache information is second cache information, and the corresponding response data is second response data;
different target query indexes are generated through different request category identifications, the obtained response data and the cache information are different through the different target query indexes, different data obtaining requests sent by different users can be classified, and different data processing modes are implemented according to the different data obtaining requests.
The target index generation method comprises the following steps:
combining domain name information, identity identification, terminal identification, request category identification and service protocol information according to a first sequence to generate a target query index;
the first sequence of the target index generation method may be sequential positive sequence, such as domain name information + identity identifier + terminal identifier + request category identifier + service protocol information, to form a target query index; the method can also be arranged in a reverse order, such as service protocol information + request type identification + terminal identification + identity identification + domain name information; the target query index only has one domain name information, an identity identifier, a terminal identifier, a request category identifier and service protocol information, wherein the request category identifier is a judgment basis for judging whether CDN cache and cached response data are applied, the service protocol information is a protocol conversion standard when the response data are sent to the target terminal, and the service protocol information is a component of the target query index because different communication protocols of different target terminals are different and conversion protocols of the corresponding response data are also different.
The step S450 includes:
s451, obtaining the effective time length T of the cache; the cache effective duration T meets the following conditions:
if the request type identifier is a second type service identifier, determining the first cache duration as a cache effective duration T; if the request type identifier is a third type service identifier, determining the second cache duration as a cache effective duration T; the first cache duration is less than the second cache duration;
and S452, establishing an incidence relation between the effective cache duration T and the second response data, storing the second response data serving as cache information to the first database, and ending the method.
The first caching duration is caching timeliness corresponding to the second type of service identification, and the second caching duration is caching timeliness corresponding to the third type of service identification; the cache aging is the time when the corresponding response data is stored in the first database, if the response data corresponding to the second type of service identifier keeps a first cache time in the first database, the response data corresponding to the third type of service identifier keeps a second cache time in the first database, because the data acquisition request corresponding to the second type of service identifier is the personal information of the user, and the data acquisition request corresponding to the third type of service identifier is the public information, in order to protect the personal information of the user from being leaked, the first cache time is set to be shorter than the second cache time, as long as the retention time of the cache information in the first database exceeds the first cache time or the second cache time, the cache information in the first database is deleted, when the next data acquisition request is sent, the cache information is inquired again in the second server and is stored again in the first database, the time from the storage to the first database is the initial time, and the information is retained in the time period when the first cache time or the second cache time is prolonged from the initial time.
After the step S450, the method further includes:
and S460, if the same data acquisition request corresponding to the first target query index is received within the cache effective duration T, calling the first cache information and sending the first cache information to the target terminal.
And S470, if the same data acquisition request corresponding to the second target query index is received within the effective cache duration T, calling the second cache information and sending the second cache information to the target terminal.
And within the time period of the effective caching duration T, if the data acquisition requests corresponding to the same target query index are repeatedly received, directly calling the caching information from the first database to the target terminal. The response data does not need to be inquired in the second server, and the access pressure of the second server is relieved.
In specific implementation, the first type service identifier may be a request type identifier corresponding to a data acquisition request for starting a type service; the second type of service identification can be a request type identification corresponding to a data acquisition request of the personal information type service of the user, such as electronic boarding pass data of the user, the requirement on the timeliness is high, and the caching timeliness can be five minutes, so that the network peak can be eliminated, and the latest data can be acquired in time; the third type of service identifier may be a request type identifier corresponding to a data acquisition request of a public information type service, for example, dynamic information of a flight on a first page of a client, and because the state of the third type of service identifier changes infrequently, the requirement on the time efficiency of the third type of service identifier is slightly low, and the cache time efficiency may be fifteen minutes. If the request type identifier corresponding to the data acquisition request is a first type service identifier, directly sending the first response data to a second server through a first server to acquire first response data, sending the first response data to a target terminal through the first server, not caching the first response data in a first database, and not generating a target query index; if the request type identification corresponding to the data acquisition request is a second type service identification or a third type service identification, firstly inquiring cache information in a first database, if so, directly calling the cache information of the first database to a target terminal without acquiring the cache information in a second server; if not, second response data are obtained from the second server and sent to the target terminal, the second response data serve as cache information to be cached in the first database, so that the cache information in the first database can be directly called when a user sends the same data obtaining request in the caching timeliness, the second response data corresponding to the second type of service identification are different from the second response data corresponding to the third type of service identification, and the specific response data generate different response data according to different target query indexes.
According to the method, CDN cache is performed on data acquisition requests which possibly generate access pressure and are necessary for client functions, different request response methods are adopted through the data acquisition requests of different request type identifications, if the request type identifications are second type service identifications or third type service identifications, whether corresponding cache information exists in a first database is inquired, if the corresponding cache information exists, the cache information is directly called to a target terminal, if the corresponding cache information does not exist, response data are acquired from a second server and are sent to the target terminal and stored in the first database as cache information, so that when a user sends the same data acquisition request again in an effective time period of cache timeliness, the cache information in the first database can be directly called, the second server does not need to be sent to acquire the response data, the query pressure of the second server is effectively relieved, and abnormal conditions of the second server caused by overlarge access pressure are reduced. Further, even if the second server is abnormal, the second server can strive for effective recovery time through the support of effective cache information in the first database, and meanwhile unfriendly experience that the client displays abnormal data to a user immediately due to the fact that the second server is abnormal can be relieved.
Embodiments of the present invention also provide a non-transitory computer-readable storage medium, which may be disposed in an electronic device to store at least one instruction or at least one program for implementing a method of the method embodiments, where the at least one instruction or the at least one program is loaded into and executed by a processor to implement the method provided by the above embodiments.
Embodiments of the present invention also provide an electronic device comprising a processor and the aforementioned non-transitory computer-readable storage medium.
Embodiments of the present invention also provide a computer program product comprising program code means for causing an electronic device to carry out the steps of the method according to various exemplary embodiments of the invention described above in the present description, when said program product is run on the electronic device.
Although some specific embodiments of the present invention have been described in detail by way of illustration, it should be understood by those skilled in the art that the above illustration is only for the purpose of illustration and is not intended to limit the scope of the invention. It will also be appreciated by those skilled in the art that various modifications may be made to the embodiments without departing from the scope and spirit of the invention. The scope of the invention is defined by the appended claims.
Claims (10)
1. A CDN-based request response method is characterized by being applied to a first server, wherein the first server is connected with a first database, a second server and a plurality of target terminals, and is used for acquiring corresponding response data from the second server or the first database according to a data acquisition request acquired from a target terminal and returning the response data to the target terminal;
the method comprises the following steps:
s100, if a data acquisition request sent by a target terminal is received under the condition that the configuration bit of the first server is a first identifier, executing a step S200; the data acquisition request comprises domain name information, an identity identifier, a terminal identifier, a request category identifier and service protocol information;
s200, if the request type identifier is a first type service identifier, executing a step S310;
if the request type identifier is the second type service identifier or the third type service identifier, executing step S410;
after the second server acquires the response data corresponding to the second type of service identifier or the third type of service identifier, the first server caches the corresponding response data to the first database, and does not cache the response data corresponding to the first type of service identifier to the first database; the cache aging of the response data corresponding to the second type of service identifier is smaller than that of the response data corresponding to the third type of service identifier;
s310, sending the data acquisition request to a second server;
s320, receiving first response data returned by the second server in response to the data acquisition request, sending the first response data to the target terminal, and ending the method;
s410, determining a target index generation method according to the request category identification;
s420, generating a target query index according to the target index generation method, and querying in the first database by using the target query index; if the first database does not have the cache information with the corresponding cache identifier being the same as the target query index, executing step S430;
s430, sending the data acquisition request to a second server;
s440, receiving second response data returned by the second server in response to the data acquisition request, and sending the second response data to the target terminal;
s450, storing the second response data serving as cache information to the first database; and the cache identifier of the second response data is the target query index corresponding to the data acquisition request, and the method is ended.
2. The method according to claim 1, wherein the step S450 comprises:
s451, obtaining the effective time length T of the cache; the cache effective duration T meets the following conditions:
if the request type identifier is a second type service identifier, determining the first cache duration as a cache effective duration T; if the request type identifier is a third type service identifier, determining a second cache duration as a cache effective duration T; the first cache duration is less than the second cache duration;
s452, establishing an incidence relation between the cache effective duration T and the second response data, storing the second response data serving as cache information to the first database, and ending the method.
3. The method according to claim 1, wherein the step S100 further comprises:
s101, under the condition that the configuration bit of the first server is the second identifier and within a set time length, when the number of acquired data acquisition requests for third response data is larger than a set threshold value, the configuration bit is adjusted to be the first identifier; and the service identifier corresponding to the third response data is a third type service identifier.
4. The method according to claim 1, wherein the step S420 further comprises:
if the corresponding cache identification and the cache information with the same target query index exist in the first database, calling the cache information and sending the cache information to the target terminal.
5. The method of claim 2, wherein the target query index comprises a first target query index and a second target query index; when the first target query index is the request type identifier and is a second type service identifier, generating a target query index according to the target index generation method; when the second target query index is the request type identifier and is a third type service identifier, generating a target query index according to the target index generation method;
the target index generation method comprises the following steps:
and combining the domain name information, the identity identification, the terminal identification, the request category identification and the service protocol information according to a first sequence to generate a target query index.
6. The method of claim 5, wherein the cache information comprises first cache information and second cache information; the first cache information is second response data returned by the second server in response to the data acquisition request aiming at the first target query index; the second cache information is second response data returned by the second server in response to the data acquisition request for a second target query index.
7. The method according to claim 6, wherein after the step S450, the method further comprises:
and S460, if the same data acquisition request corresponding to the first target query index is received within the cache effective duration T, calling the first cache information and sending the first cache information to the target terminal.
8. The method according to claim 7, wherein after the step S460, the method comprises:
s470, if the same data acquisition request corresponding to the second target query index is received within the cache effective duration T, calling the second cache information and sending the second cache information to the target terminal.
9. A non-transitory computer readable storage medium having stored therein at least one instruction or at least one program, the at least one instruction or the at least one program being loaded and executed by a processor to implement the method of any one of claims 1-8.
10. An electronic device comprising a processor and the non-transitory computer readable storage medium of claim 9.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211124866.4A CN115470246B (en) | 2022-09-15 | 2022-09-15 | Request response method based on CDN, electronic equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211124866.4A CN115470246B (en) | 2022-09-15 | 2022-09-15 | Request response method based on CDN, electronic equipment and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN115470246A true CN115470246A (en) | 2022-12-13 |
| CN115470246B CN115470246B (en) | 2023-07-14 |
Family
ID=84334090
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202211124866.4A Active CN115470246B (en) | 2022-09-15 | 2022-09-15 | Request response method based on CDN, electronic equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115470246B (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116302484A (en) * | 2023-01-17 | 2023-06-23 | 广州高才信息科技有限公司 | Position search-based server optimization scheduling system and method |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109788319A (en) * | 2017-11-14 | 2019-05-21 | 中国科学院声学研究所 | A kind of data cache method |
| CN110597739A (en) * | 2019-06-03 | 2019-12-20 | 上海云盾信息技术有限公司 | Configuration management method, system and equipment |
| CN113343088A (en) * | 2021-06-09 | 2021-09-03 | 北京奇艺世纪科技有限公司 | Data processing method, system, device, equipment and storage medium |
| CN114138840A (en) * | 2021-12-08 | 2022-03-04 | 中国建设银行股份有限公司 | Data query method, device, equipment and storage medium |
| CN114676074A (en) * | 2022-03-30 | 2022-06-28 | 北京奇艺世纪科技有限公司 | Access request processing method and device, electronic equipment and storage medium |
| US20220237054A1 (en) * | 2021-01-26 | 2022-07-28 | Salesforce.Com, Inc. | Dynamic personalized api assembly |
| CN115002132A (en) * | 2022-05-23 | 2022-09-02 | 苏州思萃工业互联网技术研究所有限公司 | Distribution method, system and computer equipment for PCDN network pre-caching resource |
-
2022
- 2022-09-15 CN CN202211124866.4A patent/CN115470246B/en active Active
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109788319A (en) * | 2017-11-14 | 2019-05-21 | 中国科学院声学研究所 | A kind of data cache method |
| CN110597739A (en) * | 2019-06-03 | 2019-12-20 | 上海云盾信息技术有限公司 | Configuration management method, system and equipment |
| US20220237054A1 (en) * | 2021-01-26 | 2022-07-28 | Salesforce.Com, Inc. | Dynamic personalized api assembly |
| CN113343088A (en) * | 2021-06-09 | 2021-09-03 | 北京奇艺世纪科技有限公司 | Data processing method, system, device, equipment and storage medium |
| CN114138840A (en) * | 2021-12-08 | 2022-03-04 | 中国建设银行股份有限公司 | Data query method, device, equipment and storage medium |
| CN114676074A (en) * | 2022-03-30 | 2022-06-28 | 北京奇艺世纪科技有限公司 | Access request processing method and device, electronic equipment and storage medium |
| CN115002132A (en) * | 2022-05-23 | 2022-09-02 | 苏州思萃工业互联网技术研究所有限公司 | Distribution method, system and computer equipment for PCDN network pre-caching resource |
Non-Patent Citations (1)
| Title |
|---|
| 何锐等: "基于CDN内容分发的研究与应用", 《通信技术》, vol. 44, no. 03, pages 111 * |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116302484A (en) * | 2023-01-17 | 2023-06-23 | 广州高才信息科技有限公司 | Position search-based server optimization scheduling system and method |
Also Published As
| Publication number | Publication date |
|---|---|
| CN115470246B (en) | 2023-07-14 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110290217B (en) | Data request processing method and device, storage medium and electronic device | |
| CN110909025A (en) | Database query method, query device and terminal | |
| CN103607312B (en) | Data request processing method and system for server system | |
| US11188443B2 (en) | Method, apparatus and system for processing log data | |
| CN110851748A (en) | Short link generation method, server, storage medium and computer equipment | |
| CN107665235B (en) | Cache processing method and device, computer equipment and storage medium | |
| CN115470246A (en) | CDN-based request response method, electronic equipment and storage medium | |
| CN109710502B (en) | Log transmission method, device and storage medium | |
| CN114547214A (en) | Long-link data processing method, device and equipment | |
| CN114398520A (en) | Data retrieval method, system, device, electronic equipment and storage medium | |
| CN116501997B (en) | Short link generation method, device, electronic equipment and storage medium | |
| CN110798222B (en) | Data compression method and device | |
| JP6233846B2 (en) | Variable-length nonce generation | |
| CN115271861A (en) | Request filtering method, device, equipment and storage medium | |
| CN110134547B (en) | Middleware-based repeated data deleting method and related device | |
| CN107015999B (en) | Information sending method and device based on distributed environment | |
| WO2016003826A1 (en) | Method and system for data processing | |
| CN112714078A (en) | Network traffic identification method and device, storage medium and server | |
| CN113704652B (en) | Data processing method, device, transfer station and data processing system | |
| CN112580029B (en) | Network system and method and device for checking and killing viruses of all-isolated network terminal | |
| CN115248818A (en) | Data acquisition method and device, electronic equipment and medium | |
| CN116501708A (en) | Image file calling method and device | |
| CN116980349A (en) | Flow processing method and device, electronic equipment and computer readable medium | |
| CN117420944A (en) | Object computing storage system, and object storage method | |
| CN116049891A (en) | Operation request processing method, device, electronic equipment and storage 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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |