CN116389596A - Multi-dimensional domain name service perception method, device, equipment and storage medium - Google Patents

Multi-dimensional domain name service perception method, device, equipment and storage medium Download PDF

Info

Publication number
CN116389596A
CN116389596A CN202310176714.7A CN202310176714A CN116389596A CN 116389596 A CN116389596 A CN 116389596A CN 202310176714 A CN202310176714 A CN 202310176714A CN 116389596 A CN116389596 A CN 116389596A
Authority
CN
China
Prior art keywords
application
service
domain name
network demand
information
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.)
Pending
Application number
CN202310176714.7A
Other languages
Chinese (zh)
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.)
INTERNET DOMAIN NAME SYSTEM BEIJING ENGINEERING RESEARCH CENTER
Original Assignee
INTERNET DOMAIN NAME SYSTEM BEIJING ENGINEERING RESEARCH CENTER
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 INTERNET DOMAIN NAME SYSTEM BEIJING ENGINEERING RESEARCH CENTER filed Critical INTERNET DOMAIN NAME SYSTEM BEIJING ENGINEERING RESEARCH CENTER
Priority to CN202310176714.7A priority Critical patent/CN116389596A/en
Publication of CN116389596A publication Critical patent/CN116389596A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/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
    • H04L67/63—Routing a service request depending on the request content or context
    • 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]
    • 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
    • Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer And Data Communications (AREA)

Abstract

The application relates to a method, a device, equipment and a storage medium for multidimensional domain name service, which are applied to an operation server of a multidimensional domain name service system, wherein the multidimensional domain name service system comprises the operation server, a domain name server and a client, and the main technical scheme comprises the following steps: sending a query record request to a domain name server, wherein the query record request comprises application identification information; receiving application network demand information returned by a domain name server based on application identification information, wherein the application network demand information is information which is preset in the domain name server in advance and corresponds to the application identification information of each application installed on a client; and providing network demand service for the corresponding application installed on the client according to the application network demand information. The method and the device can meet the requirements of different business applications installed on the client on network capacity and the requirements of different application differentiated requirement perceptions of the operator network, so as to achieve the effect of rapidly and flexibly providing network services for each application installed on the client.

Description

Multi-dimensional domain name service perception method, device, equipment and storage medium
Technical Field
The present disclosure relates to the field of domain name systems, and in particular, to a method, an apparatus, a device, and a storage medium for multidimensional domain name service.
Background
With the continuous evolution of 5G, satellite Internet, edge computing, 6 th edition Internet protocol, enhancement and virtual reality technology, a great deal of application is rapidly and vigorously developed, the network scale is continuously expanding, the variety of network service application is more and more, and the requirements of different service applications on the network are different. The requirements of network service application on differentiated network quality are also higher and higher, for example, video service needs high bandwidth, automatic driving service needs low delay, and the integration of application requirements and network differentiated service capability becomes a necessary trend.
It is well known that in conventional implementations, the domain name system provides a query translation service from an internet domain name to an internet IP address, which is a basic service required for users to access various internet applications, and is an entrance to the internet. However, as the first link of network application access, the domain name system can only be responsible for realizing name-to-address conversion, and cannot reflect the network capacity requirements of various service applications of the client, and cannot meet the requirements of the network for the differentiated requirement perception of each application installed on the client.
Disclosure of Invention
Based on the above, the application provides a method, a device, equipment and a storage medium for multidimensional sensing domain name service, which can provide application network demand service for corresponding applications installed on a client according to application response information, can meet the demands of different business applications installed on the client on network capacity and the demands of different application demand sensing by an operator network, and can achieve the effect of rapidly and flexibly providing network service for each application installed on the client.
In a first aspect, a method for multidimensional sensing domain name service is provided, and the method is applied to an operation server of a multidimensional domain name service system, wherein the multidimensional domain name service system comprises the operation server, a domain name server and a client, and the method comprises the following steps:
sending a query record request to a domain name server, wherein the query record request comprises application identification information;
receiving application network demand information returned by a domain name server based on application identification information, wherein the application network demand information is information which is preset in the domain name server in advance and corresponds to the application identification information of each application installed on a client;
and providing network demand service for the corresponding application installed on the client according to the application network demand information.
According to an implementation manner in the embodiments of the present application, providing an application network demand service for a corresponding application installed on a client according to received application response information includes:
acquiring a network service support list, and judging whether network demand services matched with application network demand information exist in the network service support list;
if yes, providing network demand service matched with the application network demand information for the corresponding application installed on the client;
if not, triggering an exception handling mechanism.
According to one implementation manner in the embodiments of the present application, the method further includes:
receiving response failure information returned by the domain name server;
and triggering an exception handling mechanism according to the response failure information.
According to one implementation manner in the embodiments of the present application, the exception handling mechanism includes a plurality of exception service policies, and triggering the exception handling mechanism includes:
determining an application service type according to the application identification information;
triggering a corresponding abnormal service strategy according to the application service type.
According to one implementation manner in the embodiment of the present application, the abnormal service policies include a regular network demand service policy, a minimum network demand service policy, a maximum network demand service policy, and a stop service policy; the application service types include entertainment application services, office application services, financial application services, and telemedicine application services; triggering a corresponding abnormal service strategy according to the application service type, including:
when the application service type is entertainment application service or office application service, triggering any one of a conventional network demand service strategy, a minimum network demand service strategy and a maximum network demand service strategy to provide default network demand service for the corresponding application installed on the client;
and when the application service type is financial application service or remote medical application service, triggering a service stopping strategy to stop providing network demand service for the corresponding application installed on the client.
According to one implementation manner in the embodiment of the present application, before the step of sending the query record request to the domain name server, the method further includes:
acquiring application identification information of each application installed on a client;
checking whether network demand information corresponding to the application identification information exists in the caching mechanism according to the application identification information;
and if the network demand information does not exist, sending a query record request to the domain name server.
According to one implementation manner in the embodiments of the present application, the method further includes:
if the network demand information exists, checking whether the corresponding preset cache valid time of the network demand information is within the valid period;
if the service is in the validity period, providing application network demand service for the corresponding application installed on the client according to the network demand information;
and if the time is not within the validity period, sending a query record request to a domain name server.
In a second aspect, a multidimensional aware domain name service device is provided, and is applied to an operation server of a multidimensional domain name service system, wherein the multidimensional domain name service system comprises the operation server, a domain name server and a client, the device is arranged on the operation server, and the device comprises:
the query module is used for sending a query record request to the domain name server, wherein the query record request comprises application identification information;
the response module is used for receiving application network demand information returned by the domain name server based on the application identification information, wherein the application network demand information is information which is preset in the domain name server in advance and corresponds to the application identification information of each application installed on the client;
and the network service providing module is used for providing network demand services for the corresponding application installed on the client according to the application network demand information.
In a third aspect, there is provided a computer device comprising:
at least one processor; and
a memory communicatively coupled to the at least one processor; wherein,,
the memory stores computer instructions executable by the at least one processor to enable the at least one processor to perform the method referred to in the first aspect above.
In a fourth aspect, there is provided a computer readable storage medium having stored thereon computer instructions for causing a computer to perform the method referred to in the first aspect above.
According to the technical content provided by the embodiment of the application, a query record request is sent to a domain name server, wherein the query record request comprises application identification information; receiving application network demand information returned by a domain name server based on application identification information, wherein the application network demand information is information which is preset in the domain name server in advance and corresponds to the application identification information of each application installed on a client; and providing network demand service for the corresponding application installed on the client according to the application network demand information. Through the operation, the application network demand service is provided for the corresponding application installed on the client according to the application response information, the demands of different service applications installed on the client on network capacity and the demands of different application demand perception by an operator network can be met, the network service capacity and the network access efficiency are improved, and the network service effect is provided for each application installed on the client rapidly and flexibly.
Drawings
FIG. 1 is a system architecture diagram of a multi-dimensional domain name service aware method in one embodiment;
FIG. 2 is a flow diagram of a method for multidimensional aware domain name service in one embodiment;
FIG. 3 is a schematic diagram of a preferred flow of a multi-dimensional domain name service aware method according to one embodiment;
FIG. 4 is a block diagram of a multi-dimensional aware domain name service device according to one embodiment;
fig. 5 is a schematic block diagram of a computer device in one embodiment.
Detailed Description
The present application will be described in further detail with reference to the accompanying drawings and examples. It should be understood that the specific embodiments described herein are for purposes of illustration only and are not intended to limit the present application.
For ease of understanding, a system architecture to which the present application applies will first be described. The multi-dimensional domain name service perception method provided by the application can be applied to a system architecture shown in fig. 1. The system architecture comprises: the operation server 101, domain name server 103 and client 105, the processing flow of the system architecture is as follows: the operation server 101 sends a query record request to the domain name server 103; the domain name server 103 performs query operation after receiving the query record request sent by the operation server 101, and returns a query response result to the operation server 101; the operation server 101 provides corresponding network demand services for each application installed on the client 105 according to the returned query response result. And further, the requirements of different service applications installed on the client on network capability and the requirements of operator networks on differentiated requirement perception of each application are met, so that the effects of improving network service capability and network access efficiency and rapidly and flexibly providing network services for each application installed on the client are achieved.
It should also be noted that the domain name server 103 includes a recursive domain name server and an authoritative domain name server, the recursive domain name server is generally used for recursive queries, and the authoritative domain name server is generally used for iterative queries. The specific query operation flow of the domain name server 103 is as follows: receiving a query record request sent by the operation server 101 by a recursive domain name server, and after receiving the query record request, checking whether corresponding application network demand information exists in a local cache by the recursive domain name server; if so, returning the application network demand information to the operation domain name server 101; if the application network demand information does not exist, the recursive domain name server sends a query record request to the authoritative domain name server, the authoritative domain name server queries corresponding application network demand information through iterative query operation, the application network demand information is returned to the recursive domain name server, and the recursive domain name server returns the application network demand information to the operation server 101, so that the effect of providing corresponding network demand service for different service applications installed on a client side is achieved. It should also be emphasized that each time the authoritative domain name server returns the query result obtained by the iterative query to the recursive domain name server, the recursive domain name server may save the query result to its local cache for the next use.
Fig. 2 is a flowchart of a method for multidimensional domain name service, which can be performed by the operation server 101 in the system architecture shown in fig. 1. As shown in fig. 2, the method may include the steps of:
step S201: and sending a query record request to the domain name server, wherein the query record request comprises the application identification information.
The application identification information includes, but is not limited to, application ID, application name, reserved field, and the like. The application ID is unique, and the application ID and the application name can be applied and distributed by a unified organization, so that the enterprise intranet can manage automatically. Wherein, the application ID can be assigned a value of 32; the application name may be assigned as online. The reserved field can be used for subsequent expansion and can be assigned as live broadcast.
In particular, as domain name servers are evolving from being primarily responsible for static conversion of names to addresses, to intelligent conversion of indirectly aware networks. Therefore, the operation server can send a query record request to the domain name server, so that the domain name server can query corresponding application network demand information based on the query record request, and further the operation server can provide corresponding network demand services for different service applications installed on the client.
Step S203: and receiving the application network demand information returned by the domain name server based on the application identification information.
The application network demand information is information which is preset in the domain name server in advance and corresponds to application identification information of each application installed on the client. The application network requirement information includes, but is not limited to, application broadband information, delay information, jitter information, packet loss rate information, failure handling information, session hold time information, requirement reservation field information, application description information, and the like. Wherein, the application broadband information can be the minimum bandwidth required by the application to run, such as the value of 100 (M); the delay information may be the minimum delay required for the application to run, e.g., may be assigned 1000 (μs); the jitter information may be the minimum network jitter required for the application to run, e.g. may be assigned 1000 (μs); the packet loss rate information may be the minimum network packet loss rate required by the application running, for example, may be assigned to 1 (%); the failure processing information can be an abnormal service policy of failed application demand matching, including 1, a conventional network demand service policy; 2. minimum network demand service policies; 3. a maximum network demand service policy; 4. any one or more of the out-of-service policies; if can be assigned a value of 1; the session keeping time information may be the time that the original requirement continues to provide after the application requirement is changed, for example, the value may be assigned to 120(s); the requirement reservation field information may be a reservation field for subsequent extended use; the application description information may be a description of the application.
Specifically, since the domain name server is preset with application network requirement information corresponding to application identification information of each application installed on the client, and the application network requirement information is provided by the network content provider according to different requirements of each application, the domain name server can return corresponding application network requirement information based on the application identification information, and the operation server can receive the application network requirement information so as to provide network services for the corresponding application installed on the client.
Step S205: and providing network demand service for the corresponding application installed on the client according to the application network demand information.
Specifically, the operation server provides network demand service for the corresponding application installed on the client according to the application network demand information. It should be noted that, the application identification information and the application network requirement information are preset in a domain name server in an APR (application requirement) record configuration form, the subdomain name of the region included in the APR record configuration is the application name in the application identification information, the record type is the APR record type, and the record value is the application network requirement information preset according to the requirement of the network content provider.
Here, for example, the application ID of the application identification information is 137, the application name is meta.example.cn, and the reserved field information is none; the application broadband information of the application network demand information corresponding to the requirement is 100 (M), the delay information is 1000 (mu s), the jitter information is 1000 (mu s), the packet loss rate information is 1 (%), the failure processing information is 1, the session holding time information is 120(s), the demand reservation field information is none, and the application description information is none. It configures in the domain name server the APR record as: domain name: meta. Type (2): APR; record the value: 137meta.sample.cn "" "100100100011120" "". Therefore, when the operation server sends a query record request with the application ID 137, the application name meta.example.cn, and the reserved field information being absent to the domain name server, the domain name server may return application network requirement information of 137meta.example.cn "" "100100100011120" "" based on the query record request, so that the operation server can provide network requirement services for the corresponding application according to the application network requirement information.
It can be seen that, in the embodiment of the present application, by sending a query record request to a domain name server, the query record request includes application identification information; receiving application network demand information returned by a domain name server based on application identification information, wherein the application network demand information is information which is preset in the domain name server in advance and corresponds to the application identification information of each application installed on a client; and providing network demand service for the corresponding application installed on the client according to the application network demand information. Through the operation, the application network demand service is provided for the corresponding application installed on the client according to the application response information, the demands of different service applications installed on the client on network capacity and the demands of different application demand perception by an operator network can be met, the network service capacity and the network access efficiency are improved, and the network service effect is provided for each application installed on the client rapidly and flexibly.
Step S205 in the above-mentioned method flow is described in detail as "providing network demand service for the corresponding application installed on the client according to the application network demand information".
Acquiring a network service support list, and judging whether network demand services matched with application network demand information exist in the network service support list; if yes, providing network demand service matched with the application network demand information for the corresponding application installed on the client; if not, triggering an exception handling mechanism.
Specifically, although the operation server has acquired the application network requirement information corresponding to the application identification information, the application network requirement information may not be provided directly, and a situation that the application network requirement information cannot be provided may occur, so the operation server may acquire a network service support list that can be supported currently, and determine whether a network requirement service matching the application network requirement information exists in the network service support list; if the network demand service exists, providing network demand service matched with the application network demand information for the corresponding application installed on the client; if not, an exception handling mechanism is triggered.
By the method, after the application network demand information of the corresponding application identification information is acquired, whether the application network demand information can be normally provided is determined, and if the application network demand information can be normally provided, network demand service matched with the application network demand information is provided for the corresponding application installed on the client; if not, an exception handling mechanism needs to be triggered to further guarantee the providing condition of the network demand service.
It should be noted that, the operation server may directly provide network demand service for the corresponding application installed on the client based on the application network demand information corresponding to the application identifier returned by the domain name server; meanwhile, the client can directly initiate the required corresponding application network demand information to the operation server based on the IPv6 protocol, and at the moment, the operation server can confirm and verify the corresponding application network demand information queried by the domain name server, so that network demand service is provided for the corresponding application installed on the client, and the adaptability of the network demand service is further ensured.
In one embodiment, the method further comprises: receiving response failure information returned by the domain name server; and triggering an exception handling mechanism according to the response failure information.
Specifically, after the domain name server receives the query record request sent by the operation server, it needs to determine whether application network requirement information corresponding to the application identification information in the query record request is preset in the domain name server, or the application network requirement information corresponding to the application identification information is not preset at all or because of reasons such as an APR record configuration error and a query type error, the corresponding application network requirement information cannot be queried, at this time, the domain name server returns response failure information, and after receiving the response failure information returned by the domain name server, the operation server triggers an exception handling mechanism according to the response failure information.
Through the operation, when the returned information is response failure information, an exception handling mechanism is triggered, so that the adaptability of the network demand service is further ensured.
In one embodiment, the exception handling mechanism includes a plurality of exception service policies, triggering the exception handling mechanism, including: determining an application service type according to the application identification information; triggering a corresponding abnormal service strategy according to the application service type.
The abnormal service policies include, but are not limited to, a regular network demand service policy, a minimum network demand service policy, a maximum network demand service policy, and a stop service policy; application service types include, but are not limited to, entertainment application services, office application services, financial application services, and telemedicine application services.
Specifically, the application service type may be determined according to the application identifier information, that is, each application identifier information has a corresponding application service type, and then a corresponding abnormal service policy may be triggered according to the application service type.
In one implementation, when the application service type is entertainment application service or office application service, any one of a regular network demand service policy, a minimum network demand service policy and a maximum network demand service policy is triggered to provide a default network demand service for a corresponding application installed on the client. Because the entertainment application service or the office application service belongs to a relatively conventional application, even if the network service does not meet the requirement, the entertainment application service or the office application service does not have great influence on the user, and therefore, any one of the conventional network demand service strategy, the minimum network demand service strategy and the maximum network demand service strategy can be selected to be installed in the corresponding application of the client to provide default network demand service. And when the application service type is financial application service or remote medical application service, triggering the service stopping strategy to stop providing network demand service for the corresponding application installed on the client. Since the financial application service or the remote medical application service belongs to an application which can greatly affect the property or the physical health of a user after the network has a problem, the service stopping strategy needs to be triggered to stop, and the service is continuously provided after the network state is good.
Through the operation, the corresponding abnormal service strategy is triggered according to the application service type, so that the better effect of providing network demand service for the corresponding application installed on the client is achieved.
In one embodiment, before the step of sending the query record request to the domain name server, the method further comprises:
acquiring application identification information of each application installed on a client; checking whether network demand information corresponding to the application identification information exists in the caching mechanism according to the application identification information; if the network demand information does not exist, sending a query record request to a domain name server; if the network demand information exists, checking whether the corresponding preset cache valid time of the network demand information is within the valid period; if the service is in the validity period, providing application network demand service for the corresponding application installed on the client according to the network demand information; and if the time is not within the validity period, sending a query record request to a domain name server.
Here, the APR record configuration further includes effective buffer time information, i.e., TTL (time to live), for determining the validity of the current network requirement information.
Specifically, before sending a query record request to the domain name server, the operation server may first obtain application identification information of each application installed on the client, and check whether network requirement information corresponding to the application identification information exists in the caching mechanism according to the application identification information. Because the operation server stores the corresponding network demand information into the cache mechanism every time the operation server acquires the network demand information, whether the network demand information corresponding to the application identification information exists in the cache mechanism can be checked.
In one implementation, if there is no network requirement information, then a query record request is sent to the domain name server.
In another implementation manner, if the network demand information exists, checking whether a preset cache validity time corresponding to the network demand information is within a validity period; if the service is in the validity period, providing application network demand service for the corresponding application installed on the client according to the network demand information; and if the time is not within the validity period, sending a query record request to a domain name server.
Through the operation, before the query record request is sent to the domain name server, whether the network demand information corresponding to the application identification information exists in the caching mechanism or not can be checked based on the application identification information, and the network demand information is acquired according to the existence condition, so that unnecessary resource waste is reduced.
It should be noted that, after the operation server provides the application network requirement information to the corresponding application installed on the client, the access effect of the application may also be checked periodically to determine whether the application network requirement information needs to be updated, or the client actively reports the network state of the current application to the operation server to indicate that the corresponding network requirement information needs to be updated. And a security authentication mechanism and an access control mechanism are further arranged in the Domain name server, the security authentication mechanism can ensure the security communication among the operator server, the authoritative server and the client, and the effects of phishing, counterfeiting and information leakage are avoided, wherein the security authentication mechanism comprises, but is not limited to, DNSSEC (Domain NameSystemSecurityExtensions, DNS security extension), doH (DNSoverHTTPS, secure HTTPS protocol), blockchain technology and the like. The access control mechanism can ensure the access rights among the operator server, the authority server and the client to achieve the effect of preventing data leakage, wherein the access control mechanism comprises but is not limited to IPACL, secret keys and the like.
In connection with the implementation of the above embodiments, a preferred method flow provided in connection with fig. 3 is described below by way of example. As shown in fig. 3, the method may include the steps of:
step S301, a query record request is sent to a domain name server, the query record request comprises application identification information, and response information returned by the domain name server is received; when the received response information is the application network demand information returned by the domain name server based on the application identification information, executing step S302; when the received response information is response failure information returned by the domain name server, step S304 is executed.
Step S302, a network service support list is obtained, whether network demand service matched with application network demand information exists in the network service support list is judged, if yes, step S303 is executed; if not, step S304 is performed.
In step S303, a network requirement service matching the application network requirement information is provided for the corresponding application installed on the client.
Step S304, triggering an exception handling mechanism, wherein the exception handling mechanism comprises a plurality of exception service policies.
Step S305, determining the application service type according to the application identification information.
Step S306, triggering a corresponding abnormal service strategy according to the application service type, and executing step S307 when the application service type is entertainment application service or office application service; when the application service type is a financial application service or a telemedicine application service, step S308 is performed.
Step S307 triggers any one of the regular network demand service policy, the minimum network demand service policy, and the maximum network demand service policy to provide the default network demand service for the corresponding application installed on the client.
In step S308, the stop service policy is triggered to stop providing the network demand service for the corresponding application installed on the client.
It should be understood that, although the steps in the flowcharts of fig. 2-3 are shown in order as indicated by the arrows, these steps are not necessarily performed in order as indicated by the arrows. The steps are not strictly limited to the order of execution unless explicitly stated in the present application, and the steps may be executed in other orders. Moreover, at least some of the steps in fig. 2-3 may include multiple sub-steps or stages that are not necessarily performed at the same time, but may be performed at different times, nor does the order in which the sub-steps or stages are performed necessarily occur in sequence, but may be performed alternately or alternately with at least a portion of the other steps or sub-steps of other steps.
Fig. 4 is a schematic structural diagram of a multi-dimensional domain name service aware device according to an embodiment of the present application, where the device may be disposed in an operation server in the system architecture shown in fig. 1, so as to perform the method flows shown in fig. 2-3. As shown in fig. 4, the apparatus may include: a query module 401, a response module 403, and a web service provision module 405. The main functions of each component module are as follows:
a query module 401, configured to send a query record request to a domain name server, where the query record request includes application identification information;
a response module 403, configured to receive application network requirement information returned by the domain name server based on the application identification information, where the application network requirement information is information preset in the domain name server in advance and corresponding to application identification information of each application installed on the client;
the network service providing module 405 is configured to provide a network demand service for a corresponding application installed on the client according to the application network demand information.
In one embodiment, the network service providing module 405 is further configured to:
acquiring a network service support list, and judging whether network demand services matched with application network demand information exist in the network service support list;
if yes, providing network demand service matched with the application network demand information for the corresponding application installed on the client;
if not, triggering an exception handling mechanism.
In one embodiment, the apparatus is further for:
receiving response failure information returned by the domain name server;
and triggering an exception handling mechanism according to the response failure information.
In one embodiment, the exception handling mechanism in the apparatus includes a plurality of exception service policies, the triggered exception handling mechanism further to:
determining an application service type according to the application identification information;
triggering a corresponding abnormal service strategy according to the application service type.
In one embodiment, the abnormal service policies of the apparatus include a regular network demand service policy, a minimum network demand service policy, a maximum network demand service policy, and a stop service policy; the application service types include entertainment application services, office application services, financial application services, and telemedicine application services; the device is also used for:
when the application service type is entertainment application service or office application service, triggering any one of a conventional network demand service strategy, a minimum network demand service strategy and a maximum network demand service strategy to provide default network demand service for the corresponding application installed on the client;
and when the application service type is financial application service or remote medical application service, triggering a service stopping strategy to stop providing network demand service for the corresponding application installed on the client.
In one embodiment, the apparatus is further for:
acquiring application identification information of each application installed on a client;
checking whether network demand information corresponding to the application identification information exists in the caching mechanism according to the application identification information;
and if the network demand information does not exist, sending a query record request to the domain name server.
In one embodiment, the apparatus is further for:
if the network demand information exists, checking whether the corresponding preset cache valid time of the network demand information is within the valid period;
if the service is in the validity period, providing application network demand service for the corresponding application installed on the client according to the network demand information;
and if the time is not within the validity period, sending a query record request to a domain name server.
The same and similar parts of the above embodiments are all referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, for the device embodiments, since they are substantially similar to the method embodiments, the description is relatively simple, and reference is made to the description of the method embodiments in part.
It should be noted that, in the embodiments of the present application, the use of user data may be involved, and in practical applications, user specific personal data may be used in the schemes described herein within the scope allowed by applicable laws and regulations under the condition that the applicable laws and regulations of the country are met (for example, the user explicitly agrees, the user is explicitly notified, the user is explicitly authorized, etc.).
According to embodiments of the present application, there is also provided a computer device, a computer-readable storage medium.
As shown in fig. 5, is a block diagram of a computer device according to an embodiment of the present application. Computer equipment is intended to represent various forms of digital computers or mobile devices. Wherein the digital computer may comprise a desktop computer, a portable computer, a workstation, a personal digital assistant, a server, a mainframe computer, and other suitable computers. The mobile device may include a tablet, a smart phone, a wearable device, etc.
As shown in fig. 5, the apparatus 500 includes a computing unit 501, a ROM502, a RAM503, a bus 504, and an input/output (I/O) interface 505, the computing unit 501, the ROM502, and the RAM503 being connected to each other through the bus 504. An input/output (I/O) interface 505 is also connected to bus 504.
The computing unit 501 may perform various processes in the method embodiments of the present application according to computer instructions stored in a Read Only Memory (ROM) 502 or computer instructions loaded from a storage unit 508 into a Random Access Memory (RAM) 503. The computing unit 501 may be a variety of general and/or special purpose processing components having processing and computing capabilities. The computing unit 501 may include, but is not limited to, a Central Processing Unit (CPU), a Graphics Processing Unit (GPU), various specialized Artificial Intelligence (AI) computing chips, various computing units running machine learning model algorithms, a Digital Signal Processor (DSP), as well as any suitable processor, controller, microcontroller, etc. In some embodiments, the methods provided by embodiments of the present application may be implemented as a computer software program tangibly embodied on a computer-readable storage medium, such as storage unit 508.
RAM503 may also store various programs and data required for the operation of device 500. Part or all of the computer program may be loaded and/or installed onto the device 500 via the ROM502 and/or the communication unit 509.
An input unit 506, an output unit 507, a storage unit 508, and a communication unit 509 in the device 500 may be connected to the I/O interface 505. Wherein the input unit 506 may be such as a keyboard, mouse, touch screen, microphone, etc.; the output unit 507 may be, for example, a display, a speaker, an indicator light, etc. The device 500 can exchange information, data, and the like with other devices through the communication unit 509.
It should be noted that the device may also include other components necessary to achieve proper operation. It may also include only the components necessary to implement the present application, and not necessarily all the components shown in the figures.
Various implementations of the systems and techniques described here can be implemented in digital electronic circuitry, integrated circuitry, field Programmable Gate Arrays (FPGAs), application Specific Integrated Circuits (ASICs), application Specific Standard Products (ASSPs), systems On Chip (SOCs), load programmable logic devices (CPLDs), computer hardware, firmware, software, and/or combinations thereof.
Computer instructions for implementing the methods of the present application may be written in any combination of one or more programming languages. These computer instructions may be provided to the computing unit 501 such that the computer instructions, when executed by the computing unit 501, such as a processor, cause the steps involved in the method embodiments of the present application to be performed.
The computer readable storage medium provided herein may be a tangible medium that may contain, or store, computer instructions for performing the steps involved in the method embodiments of the present application. The computer readable storage medium may include, but is not limited to, storage media in the form of electronic, magnetic, optical, electromagnetic, and the like.
The above embodiments do not limit the scope of the application. It will be apparent to those skilled in the art that various modifications, combinations, sub-combinations and alternatives are possible, depending on design requirements and other factors. Any modifications, equivalent substitutions and improvements made within the spirit and principles of the present application are intended to be included within the scope of the present application.

Claims (10)

1. A multi-dimensional domain name service aware method, characterized by being applied to an operation server of a multi-dimensional domain name service system, the multi-dimensional domain name service system comprising the operation server, a domain name server and a client, the method comprising:
sending a query record request to the domain name server, wherein the query record request comprises application identification information;
receiving application network demand information returned by the domain name server based on the application identification information, wherein the application network demand information is information which is preset in the domain name server in advance and corresponds to the application identification information of each application installed on the client;
and providing network demand service for the corresponding application installed on the client according to the application network demand information.
2. The method according to claim 1, wherein the providing the application network demand service for the corresponding application installed at the client according to the received application response information includes:
acquiring a network service support list, and judging whether network demand services matched with the application network demand information exist in the network service support list;
if yes, providing network demand service matched with the application network demand information for the corresponding application installed on the client;
if not, triggering an exception handling mechanism.
3. The method according to claim 1, wherein the method further comprises:
receiving response failure information returned by the domain name server;
and triggering an exception handling mechanism according to the response failure information.
4. A method according to any of claims 2-3, wherein the exception handling mechanism comprises a plurality of exception service policies, the triggering exception handling mechanism comprising:
determining an application service type according to the application identification information;
and triggering a corresponding abnormal service strategy according to the application service type.
5. The method of claim 4, wherein the abnormal service policies include a regular network demand service policy, a minimum network demand service policy, a maximum network demand service policy, and a stop service policy; the application service types comprise entertainment application service, office application service, financial application service and remote medical application service; the triggering the corresponding abnormal service policy according to the application service type includes:
when the application service type is entertainment application service or office application service, triggering any one of the conventional network demand service strategy, the minimum network demand service strategy and the maximum network demand service strategy to provide default network demand service for the corresponding application installed on the client;
and triggering the service stopping strategy to stop providing network demand service for the corresponding application installed on the client when the application service type is financial application service or remote medical application service.
6. The method of claim 1, wherein prior to the step of sending a query record request to the domain name server, further comprising:
acquiring application identification information of each application installed on the client;
checking whether network demand information corresponding to the application identification information exists in a caching mechanism according to the application identification information;
and if the network demand information does not exist, sending a query record request to the domain name server.
7. The method of claim 6, wherein the method further comprises:
if the network demand information exists, checking whether the corresponding preset cache valid time of the network demand information is within the valid period;
if the network demand information is in the validity period, providing the application network demand service for the corresponding application installed on the client according to the network demand information;
and if the domain name server is not in the validity period, sending a query record request to the domain name server.
8. A multi-dimensional domain name service aware device, characterized by an operation server applied to a multi-dimensional domain name service system, the multi-dimensional domain name service system comprising the operation server, a domain name server and a client, the device being disposed in the operation server, the device comprising:
the query module is used for sending a query record request to the domain name server, wherein the query record request comprises application identification information;
the response module is used for receiving application network demand information returned by the domain name server based on the application identification information, wherein the application network demand information is information which is preset in the domain name server in advance and corresponds to the application identification information of each application installed on the client;
and the network service providing module is used for providing network demand service for the corresponding application installed on the client according to the application network demand information.
9. A computer device, comprising:
at least one processor; and
a memory communicatively coupled to the at least one processor; wherein,,
the memory stores computer instructions executable by the at least one processor to enable the at least one processor to perform the method of any one of claims 1-7.
10. A computer readable storage medium having stored thereon computer instructions for causing a computer to perform the method of any of claims 1 to 7.
CN202310176714.7A 2023-02-28 2023-02-28 Multi-dimensional domain name service perception method, device, equipment and storage medium Pending CN116389596A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202310176714.7A CN116389596A (en) 2023-02-28 2023-02-28 Multi-dimensional domain name service perception method, device, equipment and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202310176714.7A CN116389596A (en) 2023-02-28 2023-02-28 Multi-dimensional domain name service perception method, device, equipment and storage medium

Publications (1)

Publication Number Publication Date
CN116389596A true CN116389596A (en) 2023-07-04

Family

ID=86966424

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202310176714.7A Pending CN116389596A (en) 2023-02-28 2023-02-28 Multi-dimensional domain name service perception method, device, equipment and storage medium

Country Status (1)

Country Link
CN (1) CN116389596A (en)

Similar Documents

Publication Publication Date Title
US10158620B2 (en) DNSSEC signing server
US10063599B2 (en) Controlling registration floods in VOIP networks via DNS
US8495220B2 (en) Managing CDN registration by a storage provider
US9985927B2 (en) Managing content delivery network service providers by a content broker
EP2769307B1 (en) Answer augmentation system for authoritative dns servers
US20100217890A1 (en) Using server type to obtain network address
US10182033B1 (en) Integration of service scaling and service discovery systems
CN111917900A (en) Request processing method and device for domain name proxy
CN112235408A (en) Network system, reverse proxy method and reverse proxy server
US20190166127A1 (en) Preventing leakage of cookie data
WO2023050933A1 (en) Method and apparatus for determining lost host
CN110177096B (en) Client authentication method, device, medium and computing equipment
CN116389596A (en) Multi-dimensional domain name service perception method, device, equipment and storage medium
US10298539B2 (en) Passive delegations and records
CN114124442B (en) Method and system for defending DDOS attack
CN112965763B (en) Service processing system, method, device and storage medium
CN112929429B (en) Request processing method, device and equipment
CN109618014B (en) Message forwarding method and device
CN117938809A (en) Domain name access path optimization method, system and readable storage medium
CN116915546A (en) Authentication gateway system and authentication method based on object storage
CN117640754A (en) Request processing method, device, equipment and storage medium
CN112637316A (en) Communication method and device

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