CN106790720B - Business service request implementation method and device - Google Patents
Business service request implementation method and device Download PDFInfo
- Publication number
- CN106790720B CN106790720B CN201710169660.6A CN201710169660A CN106790720B CN 106790720 B CN106790720 B CN 106790720B CN 201710169660 A CN201710169660 A CN 201710169660A CN 106790720 B CN106790720 B CN 106790720B
- Authority
- CN
- China
- Prior art keywords
- domain name
- name resolution
- service
- request
- resolution result
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/45—Network directories; Name-to-address mapping
- H04L61/4505—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols
- H04L61/4511—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols using domain name system [DNS]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
- Information Transfer Between Computers (AREA)
Abstract
The disclosure discloses a business service request implementation method and device. The method comprises the following steps: receiving a business service access instruction; inquiring a domain name resolution result cached locally according to the service access instruction to obtain an effective domain name resolution result of the service; initiating a service request according to the effective domain name resolution result; if the response request of the service request is overtime, initiating a domain name resolution request of the service according to the unconventional frequency to obtain a new domain name resolution result; initiating a service request again according to the new domain name resolution result; and when the re-initiated service request does not overtime response any more, switching the initiation frequency of the domain name resolution request to a conventionally specified frequency, wherein the conventionally specified frequency is lower than the unconventional frequency. According to the method, the service request is initiated according to the domain name resolution result of the local cache preferentially while the service request is not influenced, so that the frequency of the domain name resolution request is reduced, and the load pressure of the server is relieved.
Description
Technical Field
The present disclosure relates to the field of internet application technologies, and in particular, to a method and an apparatus for implementing a service request.
Background
With the development and popularization of Internet technology, a domain name of a service is resolved by a domain name resolution request service, so that an IP Address (Internet Protocol Address, chinese name Internet Protocol Address) corresponding to the domain name of the service is obtained according to a resolution result, and a service request is initiated according to the IP Address, which has become a main way for accessing the service.
The domain name resolution request service resolves the domain name of the service after the obtained server responds to the domain name resolution request by sending the domain name resolution request to the server. Because the high availability of a server of a business service needs to be ensured or under the condition that a plurality of servers of the business service exist in different places, the IP address corresponding to the domain name of the business service can be changed frequently, domain name resolution requests need to be carried out frequently, and the obtained IP address is refreshed frequently after the domain name resolution requests obtain the server response, so that the healthy IP address can be obtained. And initiating a service request according to the acquired IP address, and realizing normal access of the service after obtaining a response.
However, the request for domain name resolution is frequently initiated, so that the server can frequently respond to the domain name resolution request, the pressure of the server is too high, and the bandwidth occupation is high.
From the above process of accessing the service, it can be known that the server load is too high due to the frequent initiation of the domain name resolution request in the implementation of the service request in accessing the service.
Disclosure of Invention
In order to solve the problem that the server load is too high due to the fact that domain name resolution requests need to be frequently initiated for realizing service requests in service services in the related art, the disclosure provides a method and a device for realizing the service requests.
A method for realizing service request, the method comprises:
receiving a business service access instruction;
inquiring a domain name resolution result cached locally according to the service access instruction to obtain an effective domain name resolution result of the service;
initiating a service request according to the effective domain name resolution result;
if the response request of the service request is overtime, initiating a domain name resolution request of the service according to an unconventional frequency to obtain a new domain name resolution result;
initiating a service request again according to the new domain name resolution result;
and when the service request initiated again does not overtime respond any more, switching the initiation frequency of the domain name resolution request to a conventionally specified frequency, wherein the conventionally specified frequency is lower than the non-conventional frequency.
A business service request fulfillment apparatus, the apparatus comprising:
the instruction receiving module is used for receiving a business service access instruction;
the query acquisition module is used for querying a domain name resolution result cached locally according to the service access instruction to obtain an effective domain name resolution result of the service;
a service request module for initiating a service request according to the effective domain name resolution result;
a domain name resolution module, configured to initiate a domain name resolution request of the service according to an irregular frequency when a response request of the service request is overtime, so as to obtain a new domain name resolution result;
the frequent service request module is used for initiating a service request again according to the new domain name resolution result;
and the frequency switching module is used for switching the initiating frequency of the domain name resolution request to a conventionally specified frequency when the service request initiated again does not respond overtime any more, wherein the conventionally specified frequency is lower than the non-conventional frequency.
The technical scheme provided by the embodiment of the disclosure can have the following beneficial effects:
receiving a business service access instruction; inquiring a domain name resolution result cached locally according to the service access instruction to obtain an effective domain name resolution result of the service; initiating a service request according to the effective domain name resolution result; if the response request of the service request is overtime, initiating a domain name resolution request of the service according to the unconventional frequency to obtain a new domain name resolution result; initiating a service request again according to the new domain name resolution result; and when the re-initiated service request does not overtime response any more, switching the initiation frequency of the domain name resolution request to a conventionally specified frequency, wherein the conventionally specified frequency is lower than the unconventional frequency. According to the method, the service request is initiated according to the domain name resolution result cached locally, the new domain name resolution result is obtained and the service request is initiated again when the response request of the service is overtime, so that the service request is initiated according to the domain name resolution result cached locally preferentially while the service request is not influenced, the frequency of the domain name resolution request is reduced, and the load pressure of the server is relieved.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the invention and together with the description, serve to explain the principles of the invention.
FIG. 1 is a schematic illustration of an implementation environment according to the present disclosure;
FIG. 2 is a flow chart illustrating a method of business service request in accordance with an exemplary embodiment;
fig. 3 is a flowchart of an embodiment of querying a locally cached domain name resolution result according to a service access instruction to obtain an effective domain name resolution result of a service according to the embodiment of fig. 2;
fig. 4 is a flowchart of an embodiment of obtaining a new domain name resolution result by initiating a domain name resolution request of a service according to an irregular frequency when a response request of a service request of the embodiment corresponding to fig. 2 is overtime;
FIG. 5 is a diagram illustrating a specific implementation of a business service request in an application scenario;
FIG. 6 is a block diagram illustrating an apparatus for implementing a business service request in accordance with an exemplary embodiment;
FIG. 7 is a block diagram of one embodiment of a query acquisition module of the corresponding embodiment of FIG. 6.
Detailed Description
Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, like numbers in different drawings represent the same or similar elements unless otherwise indicated. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present invention. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the invention, as detailed in the appended claims.
FIG. 1 is a schematic illustration of an implementation environment according to the present disclosure. The implementation environment includes a terminal 110, a domain name resolution request server 120 and at least one service server 130.
The service server 130 is a server that stores information of service services. The terminal 110 initiates a domain name resolution request of a service to the domain name resolution request server 120, the domain name resolution request server 120 responds to the domain name resolution request, initiates a service request to the service server 130, and the service server 130 responds to the service request, so that the terminal 110 can access the service.
Fig. 2 is a flow chart illustrating a business service request method in accordance with an exemplary embodiment. As shown in fig. 1, the service request method may include the following steps.
In step 210, a business service access instruction is received.
The terminal accesses the service to acquire information externally displayed by the service. The business service access instruction is a control instruction which is generated by the terminal and enables the terminal to complete business service access when the terminal needs to access related business services. Therefore, when receiving the generated service access instruction in the operation of the terminal, the terminal sends a service request to the service server to be accessed, and when the service request is responded, the terminal can access the service.
In step 220, the local cached domain name resolution result is queried according to the service access instruction, so as to obtain an effective domain name resolution result of the service.
Wherein, for each business service access performed by the terminal itself, the obtained domain name resolution result is cached locally. When the terminal triggers the service access, the domain name resolution result cached for the service is inquired in the local cached domain name resolution result according to the received service access.
Specifically, after receiving the service access instruction, the terminal queries the domain name resolution result cached locally, and the domain name resolution result that can realize the service request in the queried domain name resolution result is the effective domain name resolution result.
In a specific implementation of an exemplary embodiment, the domain name resolution result includes a domain name of the service, an IP address of the service, and a time when the terminal obtains the domain name resolution result. The valid domain name resolution result may be a domain name resolution result that is confirmed to be valid in time according to the time when the terminal acquires the domain name resolution result.
In step 230, a service request is initiated according to the valid domain name resolution result.
The service request is a request instruction initiated to the service when the terminal needs to access the service. The service request initiates a request for accessing the service according to the IP address of the service in the effective domain name resolution result, and the terminal realizes the access to the service after the service request is responded by the request.
In step 240, if the response request of the service request is time out, the domain name resolution request of the service is initiated according to the irregular frequency, and a new domain name resolution result is obtained.
When the response time of the service request exceeds the configured time limit, the response of the service request is overtime, that is, the IP address of the service changes due to a problem generated by the service server corresponding to the IP address, so that the IP address does not conform to the IP address of the effective domain name resolution result of the currently-performed service request, and the service cannot be accessed according to the effective domain name resolution result.
Therefore, the time limit value of the configuration is reduced, and the time period for initiating the domain name resolution request is shortened, so that the domain name resolution request of the business service is initiated according to the irregular frequency, and the IP address capable of performing the business access request on the business service is obtained by refreshing. And the new domain name resolution result is the domain name resolution result which can be used for carrying out the service request and is obtained when the current service request is overtime and the service cannot be accessed according to the effective domain name resolution result. The new domain name resolution result includes an IP address obtained by refresh according to an irregular frequency.
In step 250, a business service request is initiated again based on the new domain name resolution result.
And sending a service request to the service according to the IP address of the service in the new domain name resolution result, so as to avoid the condition that the service request cannot be accessed due to overtime of the service request.
In step 260, when the re-initiated service request no longer responds to a timeout, the initiation frequency of the domain name resolution request is switched to a conventionally specified frequency.
The conventionally specified frequency is the frequency of initiating a domain name resolution request when the terminal can normally access the service. The regular designated frequency is lower than the irregular frequency.
When the request for initiating the service is not overtime any more, namely the terminal can realize the access of the service, the initiating frequency of the domain name resolution request is switched to the conventionally specified frequency by increasing the configured time limit value, so that the time period for initiating the domain name resolution request is increased, and the frequency of the domain name resolution request is reduced.
The embodiment reduces the times of domain name resolution requests while not influencing the service requests, thereby reducing the implementation cost of the service requests.
FIG. 3 is a flowchart illustrating details of step 220, according to an example embodiment. As shown in fig. 2, this step 220 may include the steps of:
in step 221, the domain name resolution result cached locally is queried according to the service access instruction, and whether the domain name resolution result of the service is cached locally is determined.
After receiving the service access instruction, the terminal queries the domain name resolution result cached locally according to the query information carried in the service access instruction, that is, searches whether the locally stored data has the cache of the domain name resolution result.
In step 222, if the domain name resolution result of the business service is cached locally, the cached domain name resolution result for the business service is queried.
When the cache of the domain name resolution result exists locally, the queried local cached domain name resolution result is the cached domain name resolution result for the service. The domain name resolution result cached for the service includes a time for acquiring the domain name resolution result.
In step 223, if the domain name resolution result of the service is not cached locally, an effective domain name resolution result returned according to the domain name resolution request is obtained by initiating the domain name resolution request of the service.
When the cache of the domain name resolution result does not exist locally, namely the effective domain name resolution result can not be obtained according to the cache of the domain name resolution result, a domain name resolution request of the service is sent to the server through the terminal, and the effective domain name resolution result returned in response to the domain name resolution request is obtained.
In step 224, the validity of the domain name resolution result in time is further determined.
In a specific implementation of an exemplary embodiment, determining the validity of the domain name resolution result over Time utilizes a configured TTL (Time To Live) value. And calculating the difference value between the time of acquiring the domain name resolution result by the terminal in the domain name resolution result and the time during calculation, comparing the difference value with the TTL value, and judging the validity of the domain name resolution result in time according to the comparison result.
In step 225, if the validity judgment is passed, it is determined that the domain name resolution result cached by the service is a valid domain name resolution result.
And when the difference value between the time of acquiring the domain name resolution result by the terminal in the domain name resolution result and the time during calculation is less than or equal to the TTL value, the validity judgment of the domain name resolution result in time is passed, and the domain name resolution result cached by the service is determined to be an effective domain name resolution result.
When the difference between the time of acquiring the domain name resolution result by the terminal in the domain name resolution result and the time when calculating is larger than the TTL value, namely an effective domain name resolution result cannot be acquired according to the cache of the domain name resolution result, a domain name resolution request of a service is initiated to the server through the terminal to obtain an effective domain name resolution result returned in response to the domain name resolution request.
In step 226, a valid domain name resolution result is obtained for the business service.
And outputting the effective domain name resolution result so as to obtain the effective domain name resolution result for the service.
In this embodiment, the validity of the domain name resolution result in time is determined, so as to obtain a valid domain name resolution result for the service.
FIG. 4 is a flowchart illustrating a description of details of step 240, according to an example embodiment. As shown in fig. 4, this step 240 may include the steps of:
in step 241, the response of the initiated service request is waited, and whether the service request is overtime is determined according to the specified time limit.
In a specific implementation of an exemplary embodiment, the specified time limit is the current configured TTL value. And when the response time of the service request exceeds the current configured TTL value, judging that the response request of the service request is overtime.
In step 243, if the service request is overtime, the domain name resolution request of the service is initiated according to the unconventional frequency by increasing the configured domain name refresh frequency, and a new domain name resolution result is obtained through the domain name resolution request.
When the service request is overtime, the configured domain name refreshing frequency is increased by reducing the current configured TTL value, so that the current domain name refreshing frequency is changed into an unconventional frequency. And initiating a domain name resolution request of the service more quickly according to the reduced current configured TTL value, thereby realizing the initiation of the domain name resolution request of the service according to the unconventional frequency, and obtaining a new domain name resolution result through the domain name resolution request, thereby being capable of reinitiating the service request after the response of the service request is overtime.
In step 245, if the service request is not timed out, the initiation frequency of the domain name resolution request is switched to the conventionally specified frequency by turning down the configured high domain name refresh frequency to the preconfigured domain name refresh frequency.
When the response time of the service request is less than the TTL value, namely the service request is not overtime, the high domain name refreshing frequency configured by turning down is changed into the domain name refreshing frequency configured in advance by increasing the TTL value to the TTL value configured in advance in the normal specified state, so that the initiating frequency of the domain name resolution request is changed into the normal specified frequency. The conventionally specified frequency is preconfigured, and the domain name resolution requests of the conventionally specified frequency are initiated less frequently than the high domain name refresh frequency.
In this embodiment, when the service request is overtime, a new domain name resolution result is obtained by frequently initiating a domain name resolution request for the service, and when the service request is not overtime, the initiation frequency of the domain name resolution request is switched to a conventionally specified frequency.
Taking the terminal as a mobile phone terminal as an example, a method for realizing the service request in the terminal is described by combining a specific application scene. For example, fig. 5 is a schematic diagram of a specific implementation of a business service request in an application scenario.
Referring to fig. 5, when the mobile phone terminal 110 needs to perform a service request, it receives a service access instruction triggering the service request, and performs a domain name resolution request to the domain name resolution server 120 before the local, and after the domain name resolution server 120 responds to the domain name resolution request, the domain name resolution result locally cached by the terminal 110 is queried, so as to obtain an effective domain name resolution result of the service. And initiating a service request to the service server 130 according to the effective domain name resolution result. Step 311 to step 313 are performed.
When the service server 130 responds that the service request exceeds the configured time limit, that is, the response of the service request is overtime, the terminal 110 will decrease the time limit, initiate a domain name resolution request of the service to the domain name resolution server 120 according to the irregular frequency, and the domain name resolution server 120 returns a new domain name resolution result to the terminal 110 after responding to the domain name resolution request. I.e., steps 314 through 315 are performed.
When the service server 130 does not exceed the configured time limit in response to the service request, that is, the response of the service request is not time out, the terminal 110 switches the originating frequency of the domain name resolution request to the conventionally specified frequency by increasing the time limit. Step 316 is performed.
The terminal 110 initiates a service request to the service server 130 according to the new domain name resolution result. Step 317 is performed.
Fig. 6 is a block diagram illustrating an apparatus for implementing a business service request in accordance with an example embodiment. The apparatus performs all or part of the steps of the service request method shown in any one of fig. 1. As shown in fig. 3, the apparatus includes, but is not limited to: the system comprises an instruction receiving module 410, a query obtaining module 420, a service request module 430, a domain name resolution module 440, a frequent service request module 450 and a frequency switching module 460.
The instruction receiving module 410 is used for receiving a business service access instruction.
The query obtaining module 420 is configured to perform query on a locally cached domain name resolution result according to the service access instruction, so as to obtain an effective domain name resolution result of the service.
The service request module 430 is configured to initiate a service request according to the result of the effective domain name resolution;
the domain name resolution module 440 is configured to initiate a domain name resolution request of the service according to an irregular frequency when a response request of the service request is overtime, so as to obtain a new domain name resolution result.
The frequent service request module 450 is configured to initiate a service request again according to the new domain name resolution result;
the frequency switching module 460 is configured to switch the initiating frequency of the domain name resolution request to a conventionally specified frequency when the service request initiated again no longer responds to a timeout, where the conventionally specified frequency is lower than the unconventional frequency.
FIG. 7 is a block diagram of one embodiment of a query acquisition module of the corresponding embodiment of FIG. 6. As shown in fig. 4, the query obtaining module 420 includes but is not limited to: an inquiry unit 421, a validity judgment unit 423, and a result acquisition unit 425.
The query unit 421 is configured to query a domain name resolution result cached locally according to the service access instruction, determine whether the domain name resolution result of the service exists, and if so, query the domain name resolution result cached for the service.
The validity judging unit 423 is configured to further judge the validity of the domain name resolution result in time, and if the validity judgment is passed, determine that the domain name resolution result cached for the service is a valid domain name resolution result.
The result obtaining unit 425 is configured to obtain a valid domain name resolution result for the service.
In an exemplary embodiment, the query obtaining module 420 is further configured to query a locally cached domain name resolution result according to the service access instruction, determine that there is no domain name resolution result of the service, obtain a new effective domain name resolution result returned according to the domain name resolution request by initiating the domain name resolution request of the service, and take the new effective domain name resolution result as the obtained effective domain name resolution result.
In an exemplary embodiment, the domain name resolution module 440 of the corresponding embodiment of fig. 3 includes, but is not limited to: a timeout determination unit.
The overtime judging unit is used for waiting for the response of the initiated business service request, judging whether the business service request is overtime according to the specified time limit, if so, initiating the domain name resolution request of the business service according to the unconventional frequency by increasing the configured domain name refreshing frequency, and obtaining a new domain name resolution result through the domain name resolution request.
In an exemplary embodiment, the frequency switching module 460 of the corresponding embodiment of fig. 3 includes, but is not limited to: a conventional frequency switching unit.
The conventional frequency switching unit is used for waiting for the response of the initiated service request, judging that the service request is not overtime according to the specified time limit, and switching the initiating frequency of the domain name resolution request to a conventionally specified frequency by reducing the configured high domain name refreshing frequency to the preconfigured domain name refreshing frequency.
The implementation processes of the functions and actions of the modules in the device are described in detail in the implementation processes of the corresponding steps in the implementation method of augmented reality in the television terminal, and are not described again here.
It will be understood that the invention is not limited to the precise arrangements described above and shown in the drawings and that various modifications and changes may be made without departing from the scope thereof. The scope of the invention is limited only by the appended claims.
Claims (10)
1. A method for realizing service request is characterized in that the method comprises the following steps:
receiving a business service access instruction;
inquiring a domain name resolution result cached locally according to the service access instruction to obtain an effective domain name resolution result of the service;
initiating a service request according to the effective domain name resolution result;
if the response request of the service request is overtime, initiating a domain name resolution request of the service according to an unconventional frequency to obtain a new domain name resolution result;
initiating a service request again according to the new domain name resolution result;
and when the service request initiated again does not overtime respond any more, switching the initiation frequency of the domain name resolution request to a conventionally specified frequency, wherein the conventionally specified frequency is lower than the non-conventional frequency.
2. The method according to claim 1, wherein the querying the locally cached domain name resolution result according to the service access instruction to obtain the valid domain name resolution result of the service comprises:
inquiring a domain name resolution result cached locally according to the service access instruction, judging whether the domain name resolution result of the service is cached locally, and inquiring the domain name resolution result cached for the service if the domain name resolution result cached for the service is cached locally;
further judging the validity of the domain name resolution result in time, and if the validity judgment is passed, determining that the domain name resolution result cached by the service is a valid domain name resolution result;
and obtaining the effective domain name resolution result for the service.
3. The method according to claim 2, wherein the step of querying the locally cached domain name resolution result according to the service access instruction to obtain the valid domain name resolution result of the service further comprises:
and inquiring a domain name resolution result cached locally according to the service access instruction, judging that the domain name resolution result of the service is not cached locally, and obtaining an effective domain name resolution result returned according to the domain name resolution request by initiating the domain name resolution request of the service.
4. The method of claim 1, wherein if the response request of the service request is time out, the domain name resolution request of the service is initiated according to an irregular frequency, and the step of obtaining a new domain name resolution result comprises:
waiting for the response of the initiated service request, judging whether the service request is overtime according to the specified time limit, if so, initiating the domain name resolution request of the service according to the unconventional frequency by increasing the configured domain name refreshing frequency, and obtaining the new domain name resolution result through the domain name resolution request.
5. The method of claim 4, wherein the step of switching the initiation frequency of the domain name resolution request to a regular designated frequency when the re-initiated traffic service request no longer times out comprises:
waiting for the response of the initiated service request, judging that the service request is not overtime according to the specified time limit, and switching the initiation frequency of the domain name resolution request to a conventionally specified frequency by reducing the configured high domain name refresh frequency to the preconfigured domain name refresh frequency.
6. A device for fulfilling service requests, the device comprising:
the instruction receiving module is used for receiving a business service access instruction;
the query acquisition module is used for querying a domain name resolution result cached locally according to the service access instruction to obtain an effective domain name resolution result of the service;
a service request module for initiating a service request according to the effective domain name resolution result;
a domain name resolution module, configured to initiate a domain name resolution request of the service according to an irregular frequency when a response request of the service request is overtime, so as to obtain a new domain name resolution result;
the frequent service request module is used for initiating a service request again according to the new domain name resolution result;
and the frequency switching module is used for switching the initiating frequency of the domain name resolution request to a conventionally specified frequency when the service request initiated again does not respond overtime any more, wherein the conventionally specified frequency is lower than the non-conventional frequency.
7. The apparatus of claim 6, wherein the query obtaining module comprises:
the query unit is used for querying a domain name resolution result cached locally according to the service access instruction, judging whether the domain name resolution result of the service is cached locally or not, and if so, querying the domain name resolution result cached for the service;
the validity judging unit is used for further judging the validity of the domain name resolution result in time, and if the validity judgment is passed, the domain name resolution result cached by the service is determined to be a valid domain name resolution result;
and the result acquisition unit is used for acquiring the effective domain name resolution result for the service.
8. The apparatus of claim 7, wherein the querying element is further configured to:
and inquiring a domain name resolution result cached locally according to the service access instruction, judging that the domain name resolution result of the service is not cached locally, and obtaining an effective domain name resolution result returned according to the domain name resolution request by initiating the domain name resolution request of the service.
9. The apparatus of claim 6, wherein the domain name resolution module comprises:
and the overtime judging unit is used for waiting for the response of the initiated service request, judging whether the service request is overtime according to the specified time limit, if so, initiating the domain name resolution request of the service according to the unconventional frequency by increasing the configured domain name refreshing frequency, and obtaining the new domain name resolution result through the domain name resolution request.
10. The apparatus of claim 8, wherein the frequency switching module comprises:
and the conventional frequency switching unit is used for waiting for the response of the initiated service request, judging that the service request is not overtime according to the specified time limit value, and switching the initiating frequency of the domain name resolution request to a conventionally specified frequency by reducing the configured high domain name refreshing frequency to the preconfigured domain name refreshing frequency.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710169660.6A CN106790720B (en) | 2017-03-21 | 2017-03-21 | Business service request implementation method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710169660.6A CN106790720B (en) | 2017-03-21 | 2017-03-21 | Business service request implementation method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN106790720A CN106790720A (en) | 2017-05-31 |
| CN106790720B true CN106790720B (en) | 2019-12-27 |
Family
ID=58967653
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201710169660.6A Active CN106790720B (en) | 2017-03-21 | 2017-03-21 | Business service request implementation method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN106790720B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114925241A (en) * | 2022-04-24 | 2022-08-19 | 杭州悦数科技有限公司 | Method, system, electronic device and storage medium for processing graph data |
| CN118433253B (en) * | 2024-07-02 | 2024-10-25 | 临沂大学 | Information security data storage method, system and electronic equipment |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102469167A (en) * | 2010-11-01 | 2012-05-23 | 中国移动通信集团北京有限公司 | Method and system for realizing domain name query |
| CN103546434A (en) * | 2012-07-13 | 2014-01-29 | 中国电信股份有限公司 | Network access control method, device and system |
| CN106161669A (en) * | 2015-04-28 | 2016-11-23 | 阿里巴巴集团控股有限公司 | A kind of quick domain name analytic method and system and terminal thereof and server |
Family Cites Families (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103929507B (en) * | 2014-04-28 | 2017-10-10 | 广东睿江云计算股份有限公司 | A kind of realize can change the method and device of DNS service offline |
| CN104506664B (en) * | 2014-11-24 | 2017-12-29 | 小米科技有限责任公司 | The method and apparatus of domain name system caching |
| US9935950B2 (en) * | 2015-01-12 | 2018-04-03 | Verisign, Inc. | Systems and methods for establishing ownership and delegation ownership of IOT devices using domain name system services |
-
2017
- 2017-03-21 CN CN201710169660.6A patent/CN106790720B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102469167A (en) * | 2010-11-01 | 2012-05-23 | 中国移动通信集团北京有限公司 | Method and system for realizing domain name query |
| CN103546434A (en) * | 2012-07-13 | 2014-01-29 | 中国电信股份有限公司 | Network access control method, device and system |
| CN106161669A (en) * | 2015-04-28 | 2016-11-23 | 阿里巴巴集团控股有限公司 | A kind of quick domain name analytic method and system and terminal thereof and server |
Also Published As
| Publication number | Publication date |
|---|---|
| CN106790720A (en) | 2017-05-31 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US20100281146A1 (en) | Dynamic domain name service system and automatic registration method | |
| CN111245972B (en) | Domain name resolution method, device, medium and equipment | |
| RU2500078C2 (en) | Method and apparatus for determining server responding to service request from mobile device, apparatus having mobile device or dns server | |
| CN101510902B (en) | Method, system and equipment for preventing wireless client terminal from disconnection during internet process | |
| CN107154963B (en) | Request processing method and device and electronic equipment | |
| CN109067936B (en) | Domain name resolution method and device | |
| WO2020228038A1 (en) | Domain name processing method, apparatus, electronic device, and storage medium | |
| US10187431B2 (en) | Network to network interface between service providers for web real time communication | |
| US20230022183A1 (en) | Systems and methods for processing requests for content of a content distribution network | |
| WO2020206660A1 (en) | Network resource request method and apparatus, electronic device and storage medium | |
| CN110730250A (en) | Information processing method and device, service system and storage medium | |
| CN109639748A (en) | Buffering updating method, device, system and the domain name system of dns server | |
| CN104811817A (en) | Method and device for using video client software to play videos | |
| CN106790720B (en) | Business service request implementation method and device | |
| CN103581351A (en) | Method and device for having access to network | |
| CN111064821A (en) | Method and device for determining IP address of edge node | |
| CN103312667B (en) | A kind of methods, devices and systems of information updating | |
| CN108494870B (en) | CDN-based dynamic data loading method and device | |
| CN115277380A (en) | Domain name resolution-based disaster tolerance method, device, system, equipment and storage medium | |
| CN109471713B (en) | Method and device for inquiring information | |
| CN106331205B (en) | The centralized management method, apparatus and relevant device of domain name resources record buffer memory | |
| CN110300308B (en) | Streaming media playback method and device | |
| CN114143332B (en) | Processing method, electronic equipment and medium based on content delivery network CDN | |
| CN110572485A (en) | Domain name resolution method, device and system | |
| KR101999719B1 (en) | Apparatus and method for managing contents |
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 |