CN112261153B - Network resource management method and related device - Google Patents
Network resource management method and related device Download PDFInfo
- Publication number
- CN112261153B CN112261153B CN202011278376.0A CN202011278376A CN112261153B CN 112261153 B CN112261153 B CN 112261153B CN 202011278376 A CN202011278376 A CN 202011278376A CN 112261153 B CN112261153 B CN 112261153B
- Authority
- CN
- China
- Prior art keywords
- terminal
- path
- domain name
- information
- name system
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/56—Provisioning of proxy services
- H04L67/568—Storing data temporarily at an intermediate stage, e.g. caching
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F18/00—Pattern recognition
- G06F18/20—Analysing
- G06F18/23—Clustering techniques
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/14—Network analysis or design
- H04L41/142—Network analysis or design using statistical or mathematical methods
-
- 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]
Landscapes
- Engineering & Computer Science (AREA)
- Data Mining & Analysis (AREA)
- Signal Processing (AREA)
- Computer Networks & Wireless Communication (AREA)
- Physics & Mathematics (AREA)
- Theoretical Computer Science (AREA)
- General Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- Life Sciences & Earth Sciences (AREA)
- Evolutionary Biology (AREA)
- Computer Vision & Pattern Recognition (AREA)
- Bioinformatics & Computational Biology (AREA)
- Bioinformatics & Cheminformatics (AREA)
- Artificial Intelligence (AREA)
- Evolutionary Computation (AREA)
- Algebra (AREA)
- Mathematical Analysis (AREA)
- Mathematical Optimization (AREA)
- Mathematical Physics (AREA)
- Probability & Statistics with Applications (AREA)
- Pure & Applied Mathematics (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The application discloses a management method of network resources and a related device, which are characterized in that user access logs of a plurality of terminals are obtained; then determining path information corresponding to the user access log; clustering is further carried out according to the similarity of the path information to obtain a path cluster; and scheduling network resources according to the membership of the terminal to the path cluster. Therefore, the process of scheduling network resources based on user requirements is realized, the problem of overhigh equipment flow load caused by overlarge domain name flow is solved, and the load balancing capability and stability are improved; and the scheduling granularity is finer based on the user requirement, so that the capacity can be fully used without exceeding the capacity during scheduling, and the accuracy of network resource scheduling is improved.
Description
The application is a divisional application of Chinese patent application with the name of 'a management method of network resources and related devices', which is submitted to the Chinese patent office on 3, month and 4 in 2020 and has the application number of 202010143223.9.
Technical Field
The present application relates to the field of computer technologies, and in particular, to a method and a related apparatus for managing network resources.
Background
The Domain Name System (DNS) service is an infrastructure. When a user accesses a Domain Name, a request needs to be initiated to a Local Domain Name System (LDNS) to acquire a service IP, and the LDNS requests an authoritative DNS through a recursive request. For an authoritative DNS, by replying to the LDNS request and responding to different service IPs, the user request can be guided to corresponding equipment, and the user traffic is scheduled and controlled while the user request is served.
In general, in order to reduce the load situation of the network device, the local domain name system LDNS may adopt the proximity principle scheduling according to its operator geographical attribute. Namely, users with the same operator geographic attribute are taken as scheduling objects to carry out load balancing of network resources.
However, due to uneven flow distribution in an actual scene, when the single domain name flow reaches the level of more than T, the base number of the users in the region is large, and the required flow is overlarge. When the authoritative DNS replies the request, the condition that the maximum number of reply resources does not meet the requirement exists, so that the scheduling precision and the control force are reduced, and the stability and the precision of network resource scheduling are influenced.
Disclosure of Invention
In view of this, the present application provides a method for managing network resources, which can effectively avoid the problem of unstable scheduling in a large flow scene, and improve the stability and accuracy of the management process of the network resources.
A first aspect of the present application provides a method for managing network resources, which may be applied to a system or a program that includes a management function of network resources in a server, and specifically includes: acquiring user access logs of a plurality of terminals;
determining path information corresponding to the user access log, wherein the path information comprises an association relation between a front-end cache server in a local domain name system, a rear-end recursive server in the local domain name system and an authoritative domain name system;
clustering according to the similarity of the path information to obtain a path cluster;
and scheduling network resources according to the membership of the terminal to the path cluster, wherein the membership is determined based on the proportion of the access times of the terminal to the corresponding paths in the path cluster.
Optionally, in some possible implementation manners of the present application, the clustering according to the similarity of the path information to obtain a path cluster includes:
determining a feature vector of the path information, wherein the feature vector is used for indicating an association relationship between the front-end cache server and the back-end recursive server;
and clustering according to the similarity of the feature vectors to obtain a path cluster.
Optionally, in some possible implementation manners of the present application, the determining the feature vector of the path information includes:
determining a back-end recursive server indicated in the path information;
traversing corresponding front-end cache servers by taking the rear-end recursive server indicated in the path information as a key respectively to generate path characteristics;
and generating the feature vector according to the similarity between the path features.
Optionally, in some possible implementation manners of the present application, the determining the feature vector of the path information includes:
controlling the terminal to send a test instruction to the local domain name system so as to obtain the corresponding relation between the back-end recursive server and the front-end cache server;
and clustering according to the corresponding relation between the back-end recursive server and the front-end cache server to obtain the characteristic vector.
Optionally, in some possible implementation manners of the present application, the scheduling the network resource according to the membership of the terminal to the path cluster includes:
determining a path set corresponding to the path cluster;
acquiring access information of the terminal to the paths in the path set respectively;
determining the membership relationship according to the access information;
and scheduling the network resources based on the membership.
Optionally, in some possible implementation manners of the present application, the scheduling of the network resource based on the membership relationship includes:
acquiring real-time flow information;
determining resource allocation information based on the membership;
and determining deviation information according to the resource allocation information and the real-time flow information so as to indicate the authoritative domain name system to carry out network resource scheduling.
Optionally, in some possible implementations of the present application, the determining resource allocation information based on the membership includes:
determining a network resource processing threshold of the authoritative domain name system;
and distributing the network resource processing threshold value according to the membership to obtain the resource distribution information.
Optionally, in some possible implementation manners of the present application, the determining a network resource processing threshold of the authoritative domain name system includes:
determining weight information corresponding to the terminal;
and determining a network resource processing threshold value of the authoritative domain name system for the terminal according to the weight information.
Optionally, in some possible implementation manners of the present application, the determining the path information corresponding to the user access log includes:
controlling a terminal corresponding to the user access log to perform recursive query so as to obtain an association relationship between the terminal and the front-end cache server and an association relationship between the rear-end recursive server and the authoritative domain name system;
controlling an edge server to respectively send inquiry messages to the front-end cache server and the authoritative domain name system so as to obtain the incidence relation between the front-end cache server and the rear-end recursive server;
and determining the path information according to the association relationship between the terminal and the front-end cache server, the association relationship between the rear-end recursive server and the authoritative domain name system and the association relationship between the front-end cache server and the rear-end recursive server.
Optionally, in some possible implementation manners of the present application, the obtaining the user access logs of the multiple terminals includes:
acquiring attribution information of a terminal;
and screening the user access log meeting preset conditions according to the attribution information, wherein the preset conditions are determined based on the similarity of different dimensions in the attribution information.
Optionally, in some possible implementation manners of the present application, the obtaining the user access logs of the multiple terminals includes:
determining a set of associated terminals in response to a scheduling request sent by the terminal;
and acquiring user access logs of a plurality of terminals in the associated terminal set.
Optionally, in some possible implementation manners of the present application, the management method of the network resource is applied to a block chain device, where the block chain device is a node in a block chain.
A second aspect of the present application provides an apparatus for management of network resources, comprising: an acquisition unit configured to acquire user access logs of a plurality of terminals;
a determining unit, configured to determine path information corresponding to the user access log, where the path information includes an association relationship between a front-end cache server in a local domain name system, a back-end recursive server in the local domain name system, and an authoritative domain name system;
the clustering unit is used for clustering according to the similarity of the path information to obtain a path cluster;
and the management unit is used for scheduling the network resources according to the membership of the terminal to the path cluster, and the membership is determined based on the proportion of the access times of the terminal to the corresponding paths in the path cluster.
Optionally, in some possible implementation manners of the present application, the clustering unit is specifically configured to determine a feature vector of the path information, where the feature vector is used to indicate an association relationship between the front-end cache server and the back-end recursive server;
and the clustering unit is specifically used for clustering according to the similarity of the feature vectors to obtain a path cluster.
Optionally, in some possible implementation manners of the present application, the clustering unit is specifically configured to determine a back-end recursive server indicated in the path information;
the clustering unit is specifically configured to traverse corresponding front-end cache servers by using a rear-end recursive server indicated in the path information as a key, respectively, to generate a path feature;
the clustering unit is specifically configured to generate the feature vector according to the similarity between the path features.
Optionally, in some possible implementation manners of the present application, the clustering unit is specifically configured to control the terminal to send a test instruction to the local domain name system, so as to obtain a corresponding relationship between the back-end recursive server and the front-end cache server;
the clustering unit is specifically configured to perform clustering according to a correspondence between the back-end recursive server and the front-end cache server to obtain the feature vector.
Optionally, in some possible implementation manners of the present application, the management unit is specifically configured to determine a path set corresponding to the path cluster;
the management unit is specifically configured to acquire access information of the terminal to the paths in the path set respectively;
the management unit is specifically configured to determine the membership relationship according to the access information;
and the management unit is specifically used for scheduling the network resources based on the membership.
Optionally, in some possible implementation manners of the present application, the management unit is specifically configured to obtain real-time traffic information;
the management unit is specifically configured to determine resource allocation information based on the membership;
the management unit is specifically configured to determine deviation information according to the resource allocation information and the real-time traffic information, so as to instruct the authoritative domain name system to perform network resource scheduling.
Optionally, in some possible implementation manners of the present application, the management unit is specifically configured to determine a network resource processing threshold of the authoritative domain name system;
the management unit is specifically configured to allocate the network resource processing threshold according to the membership, so as to obtain the resource allocation information.
Optionally, in some possible implementation manners of the present application, the management unit is specifically configured to determine weight information corresponding to the terminal;
the management unit is specifically configured to determine, according to the weight information, a network resource processing threshold of the authoritative domain name system for the terminal.
Optionally, in some possible implementation manners of the present application, the determining unit is specifically configured to control a terminal corresponding to the user access log to perform recursive query, so as to obtain an association relationship between the terminal and the front-end cache server, and an association relationship between the back-end recursive server and the authoritative domain name system;
the determining unit is specifically configured to control the edge server to send inquiry messages to the front-end cache server and the authoritative domain name system, respectively, so as to obtain an association relationship between the front-end cache server and the back-end recursive server;
the determining unit is specifically configured to determine the path information according to an association relationship between the terminal and the front-end cache server, an association relationship between the rear-end recursive server and the authoritative domain name system, and an association relationship between the front-end cache server and the rear-end recursive server.
Optionally, in some possible implementation manners of the present application, the obtaining unit is specifically configured to obtain attribution information of a terminal;
the obtaining unit is specifically configured to filter the user access log meeting a preset condition according to the attribution information, where the preset condition is determined based on similarities of different dimensions in the attribution information.
Optionally, in some possible implementations of the present application, the obtaining unit is specifically configured to determine an associated terminal set in response to a scheduling request sent by the terminal;
the obtaining unit is specifically configured to obtain user access logs of multiple terminals in the associated terminal set.
A third aspect of the present application provides a computer device comprising: a memory, a processor, and a bus system; the memory is used for storing program codes; the processor is configured to perform the method for management of network resources according to the first aspect or any one of the first aspects according to instructions in the program code.
A fourth aspect of the present application provides a computer-readable storage medium having stored therein instructions, which, when run on a computer, cause the computer to perform the method of management of network resources of the first aspect or any of the first aspects.
According to the technical scheme, the embodiment of the application has the following advantages:
obtaining user access logs of a plurality of terminals; then determining path information corresponding to the user access log, wherein the path information comprises an incidence relation between a front-end cache server in a local domain name system, a rear-end recursive server in the local domain name system and an authoritative domain name system; clustering is further carried out according to the similarity of the path information to obtain a path cluster; and scheduling network resources according to the membership of the terminal to the path cluster. Therefore, the process of scheduling network resources based on user requirements is realized, the problem of overhigh equipment flow load caused by overlarge domain name flow is solved, and the load balancing capability and stability are improved; and the scheduling granularity is finer based on the user requirement, so that the capacity can be fully used without exceeding the capacity during scheduling, and the accuracy of network resource scheduling is improved.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly introduced below, it is obvious that the drawings in the following description are only embodiments of the present application, and for those skilled in the art, other drawings can be obtained according to the provided drawings without creative efforts.
FIG. 1 is a diagram of a network architecture in which a management system for network resources operates;
fig. 2 is a system architecture diagram of management of network resources according to an embodiment of the present application;
fig. 3 is a flowchart of a method for managing network resources according to an embodiment of the present application;
fig. 4 is a schematic view of a scenario of a network resource management method according to an embodiment of the present application;
fig. 5 is a flowchart of another method for managing network resources according to an embodiment of the present application;
fig. 6 is a schematic view of a scenario of another network resource management method according to an embodiment of the present application;
fig. 7 is a schematic structural diagram of a network resource management device according to an embodiment of the present application;
fig. 8 is a schematic structural diagram of a server according to an embodiment of the present application;
fig. 9A is a data sharing system according to an embodiment of the present application;
fig. 9B is a block chain composition according to an embodiment of the present disclosure;
fig. 9C is a schematic diagram of input information of a block link point according to an embodiment of the present disclosure.
Detailed Description
The embodiment of the application provides a method and a related device for managing network resources, which can be applied to a system or a program containing a network resource management function in terminal equipment and can acquire user access logs of a plurality of terminals; then determining path information corresponding to the user access log, wherein the path information comprises an incidence relation between a front-end cache server in a local domain name system, a rear-end recursive server in the local domain name system and an authoritative domain name system; clustering is further carried out according to the similarity of the path information to obtain a path cluster; and scheduling network resources according to the membership of the terminal to the path cluster. Therefore, the process of scheduling network resources based on user requirements is realized, the problem of overhigh equipment flow load caused by overlarge domain name flow is solved, and the load balancing capability and stability are improved; and the scheduling granularity is finer based on the user requirement, so that the capacity can be fully used without exceeding the capacity during scheduling, and the accuracy of network resource scheduling is improved.
The terms "first," "second," "third," "fourth," and the like in the description and in the claims of the present application and in the drawings described above, if any, are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used is interchangeable under appropriate circumstances such that the embodiments of the application described herein are, for example, capable of operation in sequences other than those illustrated or otherwise described herein. Furthermore, the terms "comprises," "comprising," and "corresponding" and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed, but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.
First, some nouns that may appear in the embodiments of the present application are explained.
Domain Name System (DNS): a distributed network directory service is mainly used for interconversion of domain names and IP addresses and for controlling transmission of electronic mails of the Internet.
Authoritative domain name system: the method is used for domain name resolution, and final management authority is held for a specific domain name.
Edge server (Outer Center, OC): and the nodes are dispersed on the user side to provide the user with the nearby content service.
Maximum Transmission Unit (MTU): and the two communication parties restrict the contract of the message size.
Local Domain Name System (LDNS): the operator sets up a service node local to the user.
Front-end cache server (Front _ ldns): and the cache DNS of the LDNS service node faces the user.
Back-end recursive server (Back _ ldns): recursive DNS of LDNS service nodes faces authoritative DNS.
It should be understood that the management method for network resources provided by the present application may be applied to a system or a program that includes a management function for network resources in a terminal device, for example, a scheduling system platform, specifically, the management system for network resources may operate in a network architecture as shown in fig. 1, which is a network architecture diagram of the management system for network resources, as can be seen from the diagram, the management system for network resources may provide management for network resources from multiple information sources, a terminal establishes a connection with a server through a network, sends a required network resource to the server, and the server performs scheduling management and then performs allocation of the network resource; it is understood that, fig. 1 shows various terminal devices, in an actual scenario, there may be more or fewer types of terminal devices participating in the process of managing network resources, and the specific number and types depend on the actual scenario, which is not limited herein, and in addition, fig. 1 shows one server, but in an actual scenario, there may also be participation of multiple servers, especially in a scenario of multi-content application interaction, the specific number of servers depends on the actual scenario.
It is understood that the management system of the network resources can be operated in a personal mobile terminal, for example: the application as a DNS scheduling system can also be operated in a server, and can also be operated in a third-party device to provide management of network resources so as to obtain a management processing result of the network resources of the information source; the specific network resource management system may be operated in the above-mentioned device in the form of a program, may also be operated as a system component in the above-mentioned device, and may also be used as one of cloud service programs, and a specific operation mode is determined by an actual scene, which is not limited herein.
With the popularization of 4G, the development of mobile internet, the development of large-flow services such as live broadcast video and the like, the bandwidth in the market is doubled. The single domain name flow crosses the T level already, and the 5G stage large flow growth trend still continues. The large traffic increases the scheduling scale, the granularity is very long, and the control of equipment load and bandwidth cost is challenged.
The impact on scheduling granularity is further exacerbated by the development of IPV 6. The DNS message size is controlled in a minimum physical link MTU (500-520), the number of message content IPs for replying LDNS requests by an authoritative DNS is limited within a limited number, generally set to be 15 IPs, and the DNS interaction process efficiency is highest at the moment. In the IPV6 network, the IPV6 address is 4 times that of IPV4, and the number of IP contained in the message is further limited. How to solve the problem of the risk of overload of the IP bearing the traffic demand.
The domain name system service is an infrastructure network. When a user accesses a domain name, firstly, a request needs to be sent to the LDNS to acquire a service IP, and the LDNS requests an authoritative DNS through a recursive request. For an authoritative DNS, by replying to the LDNS request and responding to different service IPs, the user request can be guided to corresponding equipment, and the user traffic is scheduled and controlled while the user request is served.
In general, in order to reduce the load situation of the network device, the local domain name system LDNS may adopt the proximity principle scheduling according to its operator geographical attribute. Namely, users with the same operator geographic attribute are taken as scheduling objects to carry out load balancing of network resources.
However, due to uneven flow distribution in an actual scene, when the single domain name flow reaches the level of more than T, the base number of the users in the region is large, and the required flow is overlarge. When the authoritative DNS replies the request, the condition that the maximum number of reply resources does not meet the requirement exists, so that the scheduling precision and the control force are reduced, and the stability and the precision of network resource scheduling are influenced.
In order to solve the above problem, the present application provides a method for managing network resources, which is applied to a system framework for managing network resources shown in fig. 2, and as shown in fig. 2, the method for managing network resources provided in the embodiment of the present application is a system framework diagram for managing network resources, that is, each LDNS is divided again based on a path cluster (LDNS _ id), so that when performing network resource management, an authoritative DNS can perform resource scheduling according to a traffic requirement of the LDNS _ id, thereby accurately interacting with an edge server to implement a scheduling process.
It can be understood that the LDNS is divided into LDNS _ id according to the association relationship among the terminal (User _ ip), the Front-end cache server (Front _ LDNS), and the Back-end recursive server (Back _ LDNS); wherein Front _ ldns faces the user and Back _ ldns faces the authoritative DNS, i.e. the visiting object of the authoritative DNS is Back _ ldns. By dividing Back _ ldns with similar user groups into the same ldns _ id, the user group served by the ldns _ id is more stable, and the traffic behind it is also more stable. And the number of user groups is large, because the Front _ LDNS is directly associated with the user, the Front _ LDNS corresponding to the user is also fixed, and the Back _ LDNS with similar Front _ LDNS is divided into the same LDNS _ id, so that the LDNS division process based on the user requirements is realized.
It is understood that two terminals, two LDNS and two OCs are shown in fig. 2, but in an actual scenario there may be a greater or lesser number, and the specific number depends on the actual scenario.
It can be understood that the method provided by the present application may be a program written as a processing logic in a hardware system, or may be a network resource management device, and the processing logic is implemented in an integrated or external manner. As one implementation manner, the network resource management device obtains user access logs of a plurality of terminals; then determining path information corresponding to the user access log, wherein the path information comprises an incidence relation between a front-end cache server in a local domain name system, a rear-end recursive server in the local domain name system and an authoritative domain name system; clustering is further carried out according to the similarity of the path information to obtain a path cluster; and scheduling network resources according to the membership of the terminal to the path cluster. Therefore, the process of scheduling network resources based on user requirements is realized, the problem of overhigh equipment flow load caused by overlarge domain name flow is solved, and the load balancing capability and stability are improved; and the scheduling granularity is finer based on the user requirement, so that the capacity can be fully used without exceeding the capacity during scheduling, and the accuracy of network resource scheduling is improved.
With reference to the above flow architecture, a method for managing network resources in the present application will be introduced below, please refer to fig. 3, where fig. 3 is a flow chart of a method for managing network resources according to an embodiment of the present application, where the method for managing network resources may be applied to an authoritative DNS in the architecture shown in fig. 2, and the embodiment of the present application at least includes the following steps:
301. an authoritative DNS obtains user access logs of a plurality of terminals.
In this embodiment, the terminal is a device interacting with the user, and may be a mobile phone, a portable computer, or the like; a user can perform required network service through a terminal, so as to generate a corresponding user access log; the user access log may be extracted from data streams of a plurality of current terminals, or may be integrated from historical data.
Optionally, in the domain name management, different operators correspond to different data, so that the attribution information of the terminal may be obtained, and then the user access log meeting the preset condition is screened according to the attribution information, for example: screening user access logs indicating that the user access logs and the user access logs are in the same province and the same operator; therefore, the data pertinence is improved, and the management of network resources is facilitated.
In a possible scenario, network data of multiple terminals may have a certain association, and to ensure the integrity of a scheduling object, an associated terminal set may be determined in response to a scheduling request sent by a terminal, and then user access logs of multiple terminals in the associated terminal set are obtained, thereby improving the accuracy of the scheduling object.
302. And determining path information corresponding to the user access log by the authoritative DNS.
In this embodiment, the path information includes an association relationship between a front-end cache server in the local domain name system, a back-end recursive server in the local domain name system, and an authoritative domain name system; the association relationship is described below with reference to the accompanying drawing, and as shown in fig. 4, a scene diagram of a network resource management method provided in the embodiment of the present application is shown, where an LDNS node is shown as a reference, and the LDNS node is divided into a Front-end cache server Front _ LDNS and a Back-end cache server Back _ LDNS, where Front _ LDNS faces a user, and Back _ LDNS faces an authoritative DNS, that is, a visiting object of the authoritative DNS is Back _ LDNS. In this embodiment, the LDNS is divided into LDNS _ id according to the association relationship between User _ ip, Front _ LDNS, and Back _ LDNS.
Specifically, by dividing Back _ ldns with similar user groups into the same ldns _ id, the user group served by the ldns _ id is more stable, and the traffic behind the user group is also more stable. And the number of user groups is large, because the user is directly associated with Front _ LDNS, the Front _ LDNS corresponding to the user is also fixed, and Back _ LDNS with similar Front _ LDNS is divided into the same LDNS _ id, so that the division process of the LDNS based on the user requirements is realized, for example: in fig. 4, Back _ ldns1, Back _ ldns2 and Back _ ldns 3 are similar to each other in user orientation, and are divided into the same ldns _ id.
Optionally, the path information may be history information stored in the authoritative DNS, or may be obtained by performing real-time detection, and specifically, the terminal corresponding to the user access log may be controlled to perform recursive query, so as to obtain an association relationship between the terminal and the front-end cache server, and an association relationship between the back-end recursive server and the authoritative domain name system; correspondingly, the control edge server sends inquiry messages to the front-end cache server and the authoritative domain name system respectively to obtain the incidence relation between the front-end cache server and the rear-end recursive server; and determining path information according to the incidence relation between the terminal and the front-end cache server, the incidence relation between the rear-end recursion server and the authoritative domain name system and the incidence relation between the front-end cache server and the rear-end recursion server.
It can be understood that the process of controlling the terminal to perform the recursive query may be initiated by an authoritative DNS, or by a network resource management plug-in the authoritative DNS, or may be initiated by the terminal application in response to the operation of the user, where a specific manner depends on an actual scenario.
303. And clustering the authoritative DNS according to the similarity of the path information to obtain a path cluster.
In this embodiment, a path cluster (ldns _ id) is a set of multiple paths with similar path characteristics, where the path characteristics are association relationships between devices involved in the paths, such as Front _ ldns, Back _ ldns, and terminals. In one possible scenario, the LDNS contains Front _ LDNS1 and Front _ LDNS2, and Back _ LDNS 1. The terminal can perform data interaction with an authoritative DNS by accessing Front _ ldns1 and then Back _ ldns1, and the process is path 1(ldnsip 1); the terminal can also perform data interaction with an authoritative DNS by accessing Front _ ldns2 and then Back _ ldns1, and the process is path 2(ldnsip 2); since terminals indicated by ldnsip1 and ldnsip2 both access the authoritative DNS through Back _ ldns1, it is possible to group ldnsip1 and ldnsip2 into the same type of path, i.e., the set of ldnsip1 and ldnsip2 is a path cluster.
Specifically, the similarity of the path information may be based on a feature vector of the path information, and the formation of the feature vector is described below with reference to fig. 4, where Back _ ldns is used as a key and Front _ ldns is used as a value to generate the following feature vector:
Back_ldns1(Front_ldns1,Front_ldns 2,Front_ldns3,Front_ldns4)
Back_ldns2(Front_ldns1,Front_ldns2)
Back_ldns3(Front_ldns5,Front_ldns6)
then, comparing the three with each other, wherein the similar number is a value; where Back _ ldns1 is compared to Back _ ldns1 with a value of 4, Back _ ldns1 is compared to Back _ ldns2 with a value of 2, and so on, ultimately producing a feature vector:
ldnsip1(4,2,0)
ldnsip2(2,2,0)
ldnsip3(0,0,2)
further, according to the similarity of the feature vectors, clustering is performed, and then the clustering can be performed as the following two path clusters ldns _ id0 and ldns _ id1:
ldns_id0：ldnsip1，ldnsip2
ldns_id1：ldnsip3
it can be understood that the feature vector indicates the corresponding relationship between Front _ ldns and Back _ ldns, so that a test instruction, for example www.encode (User _ ip, Front _ ldns). test.com, can be sent to the local domain name system through the control terminal to obtain the corresponding relationship between the Back-end recursive server and the Front-end cache server; and then clustering is carried out according to the corresponding relation between the back-end recursive server and the front-end cache server to obtain the characteristic vector. Because the data obtained by the test can be strongly associated with (User _ ip, Front _ ldns, Back _ ldns), the topological relation association of the path information is more direct, and the data is clearer.
304. And the authoritative DNS schedules network resources according to the membership of the terminal to the path cluster.
In this embodiment, the membership is determined based on a ratio between access times of the terminal to corresponding paths in the path cluster. This is due to the fact that the flow demand is based on membership of the users and the ldns _ id, combined with real-time on-line flow statistics.
It can be understood that a user may correspond to multiple Front _ ldns, and the user may belong to multiple ldns _ ids at the same time, and by counting the probability of the user accessing the ldns _ id, the membership relationship between the user and the ldns _ id may be calculated, specifically, a path set corresponding to a path cluster is determined first; then acquiring access information of the terminal to the paths in the path set respectively; determining membership according to the access information; and then scheduling the network resources based on the membership.
For example: a user accesses the ldnsip 17 times, 2 accesses the ldnsip2 1 times and 1 accesses the ldnsip3 1 time, so that the membership relationship between the user and the ldnsip _ id is ldns _ id0:9 and ldns _ id1:1, namely the network resource distribution ratio of ldns _ id0 to ldns _ id1 is 9: 1; if there is a traffic demand of 10G, 9G comes from ldns _ id0, and 1G comes from ldns _ id1, and then the edge server is scheduled to perform corresponding traffic distribution.
In an actual scene, flow adjustment can be performed based on flow distribution of facts, namely, real-time flow information is obtained firstly; then determining resource allocation information based on the membership; and determining deviation information, namely adjusting the proportion according to the resource allocation information and the real-time flow information, thereby indicating the authoritative domain name system to carry out network resource scheduling.
Optionally, since the authoritative DNS may have a limited network resource processing capability, at this time, the assignment process based on the membership may be performed based on the network resource processing threshold of the authoritative DNS, so as to obtain the resource assignment information.
In a possible scenario, related personnel may also perform flow limitation on flow allocation, for example, in a flow control scenario, weight information corresponding to a terminal is determined first; and then determining the network resource processing threshold of the authoritative domain name system for the terminal according to the weight information, thereby improving the flexibility of network resource management.
With the above embodiment, it can be known that the user access logs of a plurality of terminals are obtained; then determining path information corresponding to the user access log, wherein the path information comprises an incidence relation between a front-end cache server in a local domain name system, a rear-end recursive server in the local domain name system and an authoritative domain name system; clustering is further carried out according to the similarity of the path information to obtain a path cluster; and scheduling network resources according to the membership of the terminal to the path cluster. Therefore, the process of scheduling network resources based on user requirements is realized, the problem of overhigh equipment flow load caused by overlarge domain name flow is solved, and the load balancing capability and stability are improved; and the scheduling granularity is finer based on the user requirement, so that the capacity can be fully used without exceeding the capacity during scheduling, and the accuracy of network resource scheduling is improved.
The foregoing embodiment describes a process of managing network resources, where it is described that path information may be obtained in real time, and this scenario is described below; referring to fig. 5, fig. 5 is a flowchart of another method for managing network resources according to an embodiment of the present application, where the embodiment of the present application at least includes the following steps:
501. the terminal initiates scheduling.
In this embodiment, the terminal may respond to a scheduling instruction sent by an authoritative DNS to perform a scheduling process; the method can also respond to the initiation of the terminal application, specifically, the initiation can be triggered manually by a user, or can be initiated automatically by the client application.
502. And the terminal sends an iteration request to a local domain name system.
503. The local domain name system performs recursive queries. That is, initiate an HTTP request with Uniform Resource Locator (URL) carrying User _ ip.
504. The local domain name system sends a query request to the authoritative domain name system. Wherein the query request is used for instructing the LDNS to access the authoritative DNS through recursive query.
505. The authoritative domain name system determines the access information. The authoritative DNS analyzes the User _ ip according to the URL and generates the associated information of the User _ ip and the Back _ ldns, namely access information, by combining the visited Back _ ldns.
506. A path test is initiated between the edge server and the authoritative domain name system. For example, the edge OC sends down a dig @ Front _ ldns www.encode (Front _ ldns) command test.com, so that the message is directed to pass through the Front _ ldns node, pass through the corresponding Back _ ldns and then reach the authoritative DNS; thereby obtaining the association relationship between Front _ ldns and Back _ ldns.
507. The authoritative domain name system determines the feature vector. After acquiring the association relationship between Front _ ldns and Back _ ldns, the authoritative DNS generates a feature vector by using Back _ ldns as a key and Front _ ldns as a value.
508. The authoritative domain name system determines the scheduling information. The authoritative DNS calculates the composition of the path cluster according to the real-time User access log, the association information of the User _ ip and the Back _ ldns and the association relationship of Front _ ldns and Back _ ldns, and further calculates the proportion between ldns _ id.
509. And initiating network resource scheduling between the authoritative domain name system and the edge server.
In this embodiment, flow distribution is performed according to the ratio between the ldns _ ids; in addition, the ldns _ id ratio can be corrected in real time according to the on-line deviation feedback information.
Next, a scheduling process of network resources is described with reference to a specific scenario, and as shown in fig. 6, the scheduling process is another scenario diagram of network resource management provided in this embodiment of the present application. The path cluster information, user information and user access log are shown to be obtained through the above steps 501-508.
Wherein the IP of the LDNS included in the path cluster information indicating the path cluster 1(LDNS _ id 60048) is 60.174.56.5; the path cluster 2(LDNS _ id 60049) contains LDNSs with IPs 120.10.32.7, 120.10.32.8, 120.10.32.11;
the user information can obtain that the IP address of the user is 32.1.23.3 and the address of a corresponding back-end recursive server (back _ dns) is 60.174.56.5 by sending a request instruction http:// encode (userip).
In addition, the IP address of the user is 32.1.23.3, the access domain name (domain) is dldir1.qq.com, and the size is 1024B, which can be obtained through the user access log; its real-time requirement is dldir1.qq. com requirement 2.8G. Performing off-line calculation on the information, and obtaining a proportion parameter between path clusters of the same province and the operator according to the access condition of a user, wherein the proportion parameter is 0: 0.25; 60048: 0.38; 60049: 0.37; thereby obtaining scheduling information and distributing the scheduling information to the OC for scheduling the network resources; and during scheduling, the OC can feed back the current real-time allocation situation and perform deviation calculation so as to enable the authoritative DNS to adjust the proportion of network resource allocation.
By combining the above embodiments, it can be seen that the problem of too high equipment traffic load caused by too large domain name traffic is solved due to the reduction of scheduling granularity, and the load balancing capability is improved. And because the scheduling precision is improved, the capacity can be fully used without exceeding the capacity during scheduling, and the cost is saved.
In order to better implement the above-mentioned aspects of the embodiments of the present application, the following also provides related apparatuses for implementing the above-mentioned aspects. Referring to fig. 7, fig. 7 is a schematic structural diagram of a network resource management device according to an embodiment of the present application, where the network resource management device 700 includes:
an obtaining unit 701, configured to obtain user access logs of multiple terminals;
a determining unit 702, configured to determine path information corresponding to the user access log, where the path information includes an association relationship between a front-end cache server in a local domain name system, a back-end recursive server in the local domain name system, and an authoritative domain name system;
a clustering unit 703, configured to perform clustering according to the similarity of the path information to obtain a path cluster;
a management unit 704, configured to schedule a network resource according to a membership of the terminal to the path cluster, where the membership is determined based on a ratio between access times of the terminal to corresponding paths in the path cluster.
Optionally, in some possible implementation manners of the present application, the clustering unit 703 is specifically configured to determine a feature vector of the path information, where the feature vector is used to indicate an association relationship between the front-end cache server and the back-end recursive server;
the clustering unit 703 is specifically configured to perform clustering according to the similarity of the feature vectors to obtain a path cluster.
Optionally, in some possible implementation manners of the present application, the clustering unit 703 is specifically configured to determine a back-end recursive server indicated in the path information;
the clustering unit 703 is specifically configured to traverse the corresponding front-end cache servers by using the back-end recursive server indicated in the path information as a key, respectively, to generate a path feature;
the clustering unit 703 is specifically configured to generate the feature vector according to the similarity between the path features.
Optionally, in some possible implementation manners of the present application, the clustering unit 703 is specifically configured to control the terminal to send a test instruction to the local domain name system, so as to obtain a corresponding relationship between the back-end recursive server and the front-end cache server;
the clustering unit 703 is specifically configured to perform clustering according to the correspondence between the back-end recursive server and the front-end cache server to obtain the feature vector.
Optionally, in some possible implementation manners of the present application, the management unit 704 is specifically configured to determine a path set corresponding to the path cluster;
the management unit 704 is specifically configured to obtain access information of the terminal to the paths in the path set respectively;
the management unit 704 is specifically configured to determine the membership relationship according to the access information;
the management unit 704 is specifically configured to schedule network resources based on the membership.
Optionally, in some possible implementation manners of the present application, the management unit 704 is specifically configured to obtain real-time traffic information;
the management unit 704 is specifically configured to determine resource allocation information based on the membership;
the management unit 704 is specifically configured to determine deviation information according to the resource allocation information and the real-time traffic information, so as to instruct the authoritative domain name system to perform network resource scheduling.
Optionally, in some possible implementations of the present application, the management unit 704 is specifically configured to determine a network resource processing threshold of the authoritative domain name system;
the management unit 704 is specifically configured to allocate the network resource processing threshold according to the membership, so as to obtain the resource allocation information.
Optionally, in some possible implementation manners of the present application, the management unit 704 is specifically configured to determine weight information corresponding to the terminal;
the management unit 704 is specifically configured to determine, according to the weight information, a network resource processing threshold of the authoritative domain name system for the terminal.
Optionally, in some possible implementation manners of the present application, the determining unit 702 is specifically configured to control a terminal corresponding to the user access log to perform recursive query, so as to obtain an association relationship between the terminal and the front-end cache server, and an association relationship between the back-end recursive server and the authoritative domain name system;
the determining unit 702 is specifically configured to control the edge server to send inquiry messages to the front-end cache server and the authoritative domain name system, respectively, so as to obtain an association relationship between the front-end cache server and the back-end recursive server;
the determining unit 702 is specifically configured to determine the path information according to an association relationship between the terminal and the front-end cache server, an association relationship between the rear-end recursive server and the authoritative domain name system, and an association relationship between the front-end cache server and the rear-end recursive server.
Optionally, in some possible implementation manners of the present application, the obtaining unit 701 is specifically configured to obtain attribution information of a terminal;
the obtaining unit 701 is specifically configured to filter the user access log meeting a preset condition according to the attribution information, where the preset condition is determined based on similarities of different dimensions in the attribution information.
Optionally, in some possible implementation manners of the present application, the obtaining unit 701 is specifically configured to determine an associated terminal set in response to a scheduling request sent by the terminal;
the obtaining unit 701 is specifically configured to obtain user access logs of multiple terminals in the associated terminal set.
Obtaining user access logs of a plurality of terminals; then determining path information corresponding to the user access log, wherein the path information comprises an incidence relation between a front-end cache server in a local domain name system, a rear-end recursive server in the local domain name system and an authoritative domain name system; clustering is further carried out according to the similarity of the path information to obtain a path cluster; and scheduling network resources according to the membership of the terminal to the path cluster. Therefore, the process of scheduling network resources based on user requirements is realized, the problem of overhigh equipment flow load caused by overlarge domain name flow is solved, and the load balancing capability and stability are improved; and the scheduling granularity is finer based on the user requirement, so that the capacity can be fully used without exceeding the capacity during scheduling, and the accuracy of network resource scheduling is improved.
Referring to fig. 8, fig. 8 is a schematic structural diagram of a server provided in this embodiment, where the server 800 may have a relatively large difference due to different configurations or performances, and may include one or more Central Processing Units (CPUs) 822 (e.g., one or more processors) and a memory 832, and one or more storage media 830 (e.g., one or more mass storage devices) storing applications 842 or data 844. Memory 832 and storage medium 830 may be, among other things, transient or persistent storage. The program stored in the storage medium 830 may include one or more modules (not shown), each of which may include a series of instruction operations for the server. Still further, a central processor 822 may be provided in communication with the storage medium 830 for executing a series of instruction operations in the storage medium 830 on the server 800.
The Server 800 may also include one or more power supplies 826, one or more wired or wireless network interfaces 850, one or more input-output interfaces 858, and/or one or more operating systems 841, such as a Windows ServerTM，Mac OS XTM，UnixTM,LinuxTM，FreeBSDTMAnd so on.
The steps performed by the image rendering apparatus in the above embodiments may be based on the computer device configuration shown in fig. 8.
Also provided in the embodiments of the present application is a computer-readable storage medium, which stores network resource management instructions and when the computer-readable storage medium is executed on a computer, causes the computer to perform the steps performed by the network resource management apparatus in the methods described in the foregoing embodiments shown in fig. 2 to 6.
Also provided in the embodiments of the present application is a computer program product including network resource management instructions, which when run on a computer, causes the computer to perform the steps performed by the network resource management apparatus in the method described in the foregoing embodiments shown in fig. 2 to 6.
An embodiment of the present application further provides a network resource management system, where the network resource management system may include the network resource management device in the embodiment described in fig. 7 or the server described in fig. 8.
It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.
In the several embodiments provided in the present application, it should be understood that the disclosed system, apparatus and method may be implemented in other manners. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.
The integrated unit, if implemented in the form of a software functional unit and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application may be substantially implemented or contributed to by the prior art, or all or part of the technical solution may be embodied in a software product, which is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a network resource management apparatus, or a network device) to perform all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: various media capable of storing program codes, such as a usb disk, a removable hard disk, a read-only memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk.
In a possible scenario, the method for network resource management in the present application is applied to a blockchain device, that is, an authoritative DNS, an LDNS, or a terminal is a blockchain device, and the blockchain device is a node in a blockchain, which is described below with reference to the accompanying drawings; referring to the data sharing system shown in fig. 9A, the data sharing system 900 refers to a system for performing data sharing between nodes, the data sharing system may include a plurality of nodes 901, and the plurality of nodes 901 may refer to respective clients in the data sharing system. Each node 901 may receive input information during normal operation and maintain shared data within the data sharing system based on the received input information. In order to ensure information intercommunication in the data sharing system, information connection can exist between each node in the data sharing system, and information transmission can be carried out between the nodes through the information connection. For example, when an arbitrary node in the data sharing system receives input information, other nodes in the data sharing system acquire the input information according to a consensus algorithm, and store the input information as data in shared data, so that the data stored on all the nodes in the data sharing system are consistent.
Each node in the data sharing system has a node identifier corresponding thereto, and each node in the data sharing system may store a node identifier of another node in the data sharing system, so that the generated block is broadcast to the other node in the data sharing system according to the node identifier of the other node in the following. Each node may maintain a node identifier list as shown in the following table, and store the node name and the node identifier in the node identifier list correspondingly. The node identifier may be an IP (Internet Protocol) address and any other information that can be used to identify the node, and table 1 only illustrates the IP address as an example.
TABLE 1 correspondence of node names to node identifiers
| Node name | |
| Node | |
| 1 | 117.114.151.174 |
| |
117.116.189.145 |
| … | … |
| Node N | 119.123.789.258 |
Each node in the data sharing system stores one identical blockchain. The block chain is composed of a plurality of blocks, as shown in fig. 9B, the block chain is composed of a plurality of blocks, the starting block includes a block header and a block main body, the block header stores an input information characteristic value, a version number, a timestamp and a difficulty value, and the block main body stores input information; the next block of the starting block takes the starting block as a parent block, the next block also comprises a block head and a block main body, the block head stores the input information characteristic value of the current block, the block head characteristic value of the parent block, the version number, the timestamp and the difficulty value, and the like, so that the block data stored in each block in the block chain is associated with the block data stored in the parent block, and the safety of the input information in the block is ensured.
When each block in the block chain is generated, referring to fig. 9C, when the node where the block chain is located receives the input information, the input information is verified, after the verification is completed, the input information is stored in the memory pool, and the hash tree for recording the input information is updated; and then, updating the updating time stamp to the time when the input information is received, trying different random numbers, and calculating the characteristic value for multiple times, so that the calculated characteristic value can meet the following formula:
SHA256(SHA256(version+prev_hash+merkle_root+ntime+nbits+x))＜TARGET
wherein, SHA256 is a characteristic value algorithm used for calculating a characteristic value; version is version information of the relevant block protocol in the block chain; prev _ hash is a block head characteristic value of a parent block of the current block; merkle _ root is a characteristic value of the input information; ntime is the update time of the update timestamp; nbits is the current difficulty, is a fixed value within a period of time, and is determined again after exceeding a fixed time period; x is a random number; TARGET is a feature threshold, which can be determined from nbits.
Therefore, when the random number meeting the formula is obtained through calculation, the information can be correspondingly stored, and the block head and the block main body are generated to obtain the current block. And then, the node where the block chain is located respectively sends the newly generated blocks to other nodes in the data sharing system where the newly generated blocks are located according to the node identifications of the other nodes in the data sharing system, the newly generated blocks are verified by the other nodes, and the newly generated blocks are added to the block chain stored in the newly generated blocks after the verification is completed.
The above embodiments are only used for illustrating the technical solutions of the present application, and not for limiting the same; although the present application has been described in detail with reference to the foregoing embodiments, it should be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; and such modifications or substitutions do not depart from the spirit and scope of the corresponding technical solutions in the embodiments of the present application.
Claims (15)
1. A method for managing network resources, comprising:
responding to a scheduling request of a terminal to acquire path information corresponding to the terminal, wherein the path information comprises a front-end cache server in a local domain name system, a rear-end recursive server in the local domain name system and an association relation between the authoritative domain name system;
clustering according to the similarity of the path information to obtain a path cluster;
determining a path cluster corresponding to the terminal to obtain the path set;
determining access information of the terminal to the paths in the path set respectively to determine a membership of the terminal to the paths in the path set, wherein the membership is determined based on a proportion of access times of the terminal to corresponding paths in the path cluster;
determining resource allocation information based on the membership;
and determining deviation information according to the resource allocation information and the real-time flow information corresponding to the terminal so as to indicate an authoritative domain name system to carry out network resource scheduling.
2. The method of claim 1, wherein the obtaining the path set corresponding to the terminal in response to the scheduling request of the terminal comprises:
responding to the scheduling request of a terminal to obtain a user access log of the terminal;
determining path information corresponding to the user access log, wherein the path information comprises a front-end cache server in a local domain name system, a rear-end recursive server in the local domain name system and an association relation of the authoritative domain name system;
clustering according to the similarity of the path information to obtain a path cluster;
and determining a path cluster corresponding to the terminal to obtain the path set.
3. The method of claim 2, wherein the obtaining the user access log of the terminal in response to the scheduling request of the terminal comprises:
responding to a scheduling request of a terminal and sending an iteration request to a local domain name system, so that the local domain name system sends a query request to an authoritative domain name system;
and the authoritative domain name system determines access information according to the query request so as to determine the user access log.
4. The method of claim 3, further comprising:
acquiring attribution information of the terminal;
and screening the user access log meeting preset conditions according to the attribution information, wherein the preset conditions are determined based on the similarity of different dimensions in the attribution information.
5. The method of claim 3, further comprising:
determining a set of associated terminals in response to a scheduling request sent by the terminal;
and acquiring user access logs of a plurality of terminals in the associated terminal set.
6. The method of claim 2, wherein the determining the path information corresponding to the user access log comprises:
controlling a terminal corresponding to the user access log to perform recursive query so as to obtain an association relationship between the terminal and the front-end cache server and an association relationship between the rear-end recursive server and the authoritative domain name system;
controlling an edge server to respectively send inquiry messages to the front-end cache server and the authoritative domain name system so as to obtain the incidence relation between the front-end cache server and the rear-end recursive server;
and determining the path information according to the association relationship between the terminal and the front-end cache server, the association relationship between the rear-end recursive server and the authoritative domain name system and the association relationship between the front-end cache server and the rear-end recursive server.
7. The method according to claim 2, wherein the clustering according to the similarity of the path information to obtain a path cluster comprises:
determining a feature vector of the path information, wherein the feature vector is used for indicating an association relationship between the front-end cache server and the back-end recursive server;
and clustering according to the similarity of the feature vectors to obtain a path cluster.
8. The method of claim 7, wherein the determining the feature vector of the path information comprises:
determining a back-end recursive server indicated in the path information;
traversing corresponding front-end cache servers by taking the rear-end recursive server indicated in the path information as a key respectively to generate path characteristics;
and generating the feature vector according to the similarity between the path features.
9. The method of claim 7, wherein the determining the feature vector of the path information comprises:
controlling the terminal to send a test instruction to the local domain name system so as to obtain the corresponding relation between the back-end recursive server and the front-end cache server;
and clustering according to the corresponding relation between the back-end recursive server and the front-end cache server to obtain the characteristic vector.
10. The method of claim 1, wherein the determining resource allocation information based on the membership comprises:
determining a network resource processing threshold of the authoritative domain name system;
and distributing the network resource processing threshold value according to the membership to obtain the resource distribution information.
11. The method of claim 10, wherein determining the network resource handling threshold for the authoritative domain name system comprises:
determining weight information corresponding to the terminal;
and determining a network resource processing threshold value of the authoritative domain name system for the terminal according to the weight information.
12. The method according to claim 1, wherein the management method of the network resource is applied to a blockchain device, and the blockchain device is a node in a blockchain.
13. An apparatus for management of network resources, comprising:
the system comprises an acquisition unit, a processing unit and a processing unit, wherein the acquisition unit is used for responding to a scheduling request of a terminal to acquire path information corresponding to the terminal, and the path information comprises a front-end cache server in a local domain name system, a rear-end recursive server in the local domain name system and an incidence relation between the authoritative domain name system; clustering according to the similarity of the path information to obtain a path cluster; determining a path cluster corresponding to the terminal to obtain the path set;
a determining unit, configured to determine access information of the terminal on paths in the path set, respectively, so as to determine a membership relationship of the terminal on the paths in the path set, where the membership relationship is determined based on a ratio between access times of the terminal on corresponding paths in the path cluster;
the determining unit is further configured to determine resource allocation information based on the membership;
and the management unit is used for determining deviation information according to the resource allocation information and the real-time flow information corresponding to the terminal so as to indicate an authoritative domain name system to carry out network resource scheduling.
14. A computer device, the computer device comprising a processor and a memory:
the memory is used for storing program codes; the processor is configured to perform the method of management of network resources of any of claims 1 to 12 according to instructions in the program code.
15. A computer-readable storage medium having stored therein instructions which, when run on a computer, cause the computer to perform the method of management of network resources of any of the above claims 1 to 12.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011278376.0A CN112261153B (en) | 2020-03-04 | 2020-03-04 | Network resource management method and related device |
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010143223.9A CN111385357B (en) | 2020-03-04 | 2020-03-04 | Network resource management method and device, computer equipment and storage medium |
| CN202011278376.0A CN112261153B (en) | 2020-03-04 | 2020-03-04 | Network resource management method and related device |
Related Parent Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010143223.9A Division CN111385357B (en) | 2020-03-04 | 2020-03-04 | Network resource management method and device, computer equipment and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112261153A CN112261153A (en) | 2021-01-22 |
| CN112261153B true CN112261153B (en) | 2021-07-13 |
Family
ID=71218598
Family Applications (2)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010143223.9A Active CN111385357B (en) | 2020-03-04 | 2020-03-04 | Network resource management method and device, computer equipment and storage medium |
| CN202011278376.0A Active CN112261153B (en) | 2020-03-04 | 2020-03-04 | Network resource management method and related device |
Family Applications Before (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010143223.9A Active CN111385357B (en) | 2020-03-04 | 2020-03-04 | Network resource management method and device, computer equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (2) | CN111385357B (en) |
Families Citing this family (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113079226B (en) * | 2021-06-04 | 2021-10-15 | 北京达佳互联信息技术有限公司 | Domain name allocation method, device, server and storage medium |
| CN113342612B (en) * | 2021-06-25 | 2022-07-15 | 长江存储科技有限责任公司 | Abnormal access behavior detection method, device and equipment and readable storage medium |
| CN115277573A (en) * | 2022-08-09 | 2022-11-01 | 康键信息技术（深圳）有限公司 | Load balancing processing method and device for issuing application tasks |
Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105357335A (en) * | 2015-11-25 | 2016-02-24 | 中国互联网络信息中心 | DNS authority log information mining processing method |
Family Cites Families (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102123100B (en) * | 2008-02-05 | 2013-06-12 | 华为技术有限公司 | Method and device for maintaining routing information |
| CN103037442A (en) * | 2011-09-29 | 2013-04-10 | 中国移动通信集团江苏有限公司 | Method and system for achieving flow separation scheduling |
| CN104754640B (en) * | 2013-12-26 | 2019-01-08 | 中国移动通信集团公司 | A kind of network resource scheduling method and network resource management server |
| US9426171B1 (en) * | 2014-09-29 | 2016-08-23 | Amazon Technologies, Inc. | Detecting network attacks based on network records |
| US10142386B2 (en) * | 2014-10-29 | 2018-11-27 | DLVR, Inc. | Determining manifest file data used in adaptive streaming video delivery |
| CN105376344B (en) * | 2015-11-26 | 2019-01-04 | 中国互联网络信息中心 | A kind of analytic method and system of recurrence name server relevant to source address |
| CN105574539B (en) * | 2015-12-11 | 2018-09-21 | 中国联合网络通信集团有限公司 | A kind of DNS log analysis methods and device |
| US20180331946A1 (en) * | 2017-05-09 | 2018-11-15 | vIPtela Inc. | Routing network traffic based on performance |
| CN107071089B (en) * | 2017-05-18 | 2020-09-15 | 腾讯科技（深圳）有限公司 | Scheduling control method, device and system |
| CN108494891A (en) * | 2018-02-28 | 2018-09-04 | 网宿科技股份有限公司 | A kind of domain name analytic method, server and system |
| CN110213227B (en) * | 2019-04-24 | 2020-12-22 | 华为技术有限公司 | Network data flow detection method and device |
-
2020
- 2020-03-04 CN CN202010143223.9A patent/CN111385357B/en active Active
- 2020-03-04 CN CN202011278376.0A patent/CN112261153B/en active Active
Patent Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105357335A (en) * | 2015-11-25 | 2016-02-24 | 中国互联网络信息中心 | DNS authority log information mining processing method |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111385357A (en) | 2020-07-07 |
| CN111385357B (en) | 2021-04-27 |
| CN112261153A (en) | 2021-01-22 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112261153B (en) | Network resource management method and related device | |
| EP3968605A1 (en) | Method for providing edge service, apparatus and device | |
| CN109547517B (en) | Method and device for scheduling bandwidth resources | |
| US10499279B2 (en) | Method and apparatus for dynamic association of terminal nodes with aggregation nodes and load balancing | |
| US6965930B1 (en) | Methods, systems and computer program products for workload distribution based on end-to-end quality of service | |
| US10715479B2 (en) | Connection redistribution in load-balanced systems | |
| WO2021098407A1 (en) | Mec-based service node allocation method and apparatus, and related server | |
| CN111669719B (en) | Method, system and related equipment for carrying out charging processing on network slice client | |
| CN111541796A (en) | CDN access flow scheduling method, device, communication system and storage medium | |
| CN110430274A (en) | A kind of document down loading method and system based on cloud storage | |
| CN103825975A (en) | Cdn node distribution server and system | |
| CN111614748A (en) | Scalable peer-to-peer matching | |
| CN110888735A (en) | Distributed message distribution method and device based on consistent hash and scheduling node | |
| US7203768B2 (en) | Managing network traffic using hashing functions | |
| CN112738288A (en) | DNS domain name resolution method, DNS server, GSLB system and domain name resolution system | |
| CN107332744B (en) | Routing path selection method and system and user access server | |
| US20220166842A1 (en) | Data distribution method and electronic device | |
| CN111275495A (en) | Advertisement putting monitoring method, device and system based on block chain | |
| TW201732729A (en) | Service processing method and device | |
| EP2874368B1 (en) | Method and device for generating aggregate layer networkmap and aggregate layer costmap | |
| CN110958124B (en) | Multicast group management method, device, readable storage medium and computer | |
| CN110995890B (en) | Domain name request scheduling method and device | |
| CN107172129B (en) | Server configuration method and device | |
| CN112104888B (en) | Method and system for grouping live broadcast users | |
| CN111147617B (en) | Method and system for distributing addresses based on DHCP server cluster load |
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 |