CN107517162B - CDN cache server determination method and device - Google Patents
CDN cache server determination method and device Download PDFInfo
- Publication number
- CN107517162B CN107517162B CN201610440363.6A CN201610440363A CN107517162B CN 107517162 B CN107517162 B CN 107517162B CN 201610440363 A CN201610440363 A CN 201610440363A CN 107517162 B CN107517162 B CN 107517162B
- Authority
- CN
- China
- Prior art keywords
- address
- user equipment
- communication information
- cache server
- determining
- 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/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/74—Address processing for routing
-
- 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)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The embodiment of the application provides a method and a device for determining a CDN cache server, wherein the method for determining the CDN cache server comprises the following steps: obtaining a source address corresponding to user equipment, and determining a first address field to which the source address belongs; determining a historical routing path corresponding to the first address segment; determining a second address field of which the hop count with the first address field is less than or equal to a preset value N from the historical routing path; and obtaining communication information corresponding to the second address segment, and determining a CDN cache server corresponding to the user equipment according to the communication information. Therefore, in the embodiment of the present application, the CDN cache server is determined according to the communication information corresponding to the second address segment, instead of randomly setting the communication information or randomly designating the CDN cache server. Because the hop count of the second address field and the first address field is less than or equal to the preset value N, the probability of being suitable for the user equipment is higher, and the access speed of the user equipment is improved.
Description
Technical Field
The present application relates to the field of internet technologies, and in particular, to a method and an apparatus for determining a CDN cache server.
Background
The Content Delivery Network (CDN) technology is to cache Network resources in each CDN cache server, guide the user equipment to a corresponding CDN cache server when a user requests a Network resource, and enable the user equipment to obtain the Network resource at a higher speed by accessing the corresponding CDN cache server, so as to speed up access.
How to determine the CDN cache server corresponding to the user equipment is an important process for ensuring accelerated access. Currently, when a CDN cache server corresponding to a user equipment is determined, a source address corresponding to the user equipment is obtained, communication information corresponding to the source address is obtained from a network Protocol (IP) address library, and the CDN cache server corresponding to the user equipment is determined according to the communication information.
However, in the above process, it may not be possible to determine the CDN cache server corresponding to the user equipment, for example, the obtained communication information is incomplete due to reasons such as non-normative IP address repository information or incomplete information, which is not enough to determine the CDN cache server; and for example, a CDN cache server corresponding to the communication information is not deployed. At this time, communication information is generally set randomly or a CDN cache server is designated randomly, however, the access speed of the user equipment is often slow due to the manner in which the communication information is set randomly or the CDN cache server is designated randomly.
Disclosure of Invention
The technical problem to be solved by the application is to provide a method and a device for determining a CDN cache server, so that when the CDN cache server cannot be determined according to communication information corresponding to user equipment, the CDN server suitable for the user equipment is determined according to a historical routing path of the user equipment, and therefore the access speed of the user equipment when accessing the CDN cache server is improved.
Therefore, the technical scheme for solving the technical problem is as follows:
the application provides a method for determining a CDN cache server, which comprises the following steps:
obtaining a source address corresponding to user equipment, and determining a first address field to which the source address belongs;
determining a historical routing path corresponding to the first address segment;
determining a second address segment of which the hop count with the first address segment is less than or equal to a preset value N from the historical routing path, wherein the preset value N is more than or equal to 1;
and obtaining communication information corresponding to the second address segment, and determining a CDN cache server corresponding to the user equipment according to the communication information corresponding to the second address segment.
Optionally, the historical routing path is a historical autonomous domain path; determining a first address segment to which the source address belongs, including:
determining a first autonomous domain to which the source address belongs, wherein the first autonomous domain corresponds to the first address field;
determining a second address field with the hop count of the first address field being less than or equal to a preset value N, comprising:
and determining a second autonomous domain of which the hop count is less than or equal to the preset value N, wherein the second autonomous domain corresponds to the second address field.
Optionally, determining, from the historical routing path, a second address segment whose hop count with the first address segment is less than or equal to a preset value N, including:
and determining a second address field corresponding to the previous hop of the first address field from the historical routing path.
Optionally, before determining the CDN cache server corresponding to the user equipment according to the communication information corresponding to the second address segment, the determining method further includes:
acquiring communication information corresponding to the user equipment;
and judging that the CDN cache server corresponding to the user equipment cannot be determined according to the communication information corresponding to the user equipment.
Optionally, determining, according to the communication information corresponding to the second address segment, a CDN cache server corresponding to the user equipment includes:
determining a CDN cache server corresponding to the user equipment according to the communication information corresponding to the second address segment and the communication information corresponding to the user equipment; the communication information corresponding to the user equipment and the communication information corresponding to the second address field are communication information with different types.
Optionally, after the CDN cache server corresponding to the user equipment is determined according to the communication information corresponding to the second address segment, the determining method further includes:
and returning the address of the CDN cache server to the user equipment.
Optionally, the source address includes an address of the user equipment, or an address of a local DNS server corresponding to the user equipment.
Optionally, the communication information corresponding to the second address field includes: operator information and/or geolocation information for the second address field.
The application provides a CDN cache server's confirming device, the device includes:
the first determining unit is used for acquiring a source address corresponding to the user equipment and determining a first address field to which the source address belongs;
a second determining unit, configured to determine a historical routing path corresponding to the first address segment;
a third determining unit, configured to determine, from the historical routing path, a second address segment whose hop count with the first address segment is less than or equal to a preset value N, where the preset value N is greater than or equal to 1;
and the fourth determining unit is configured to obtain communication information corresponding to the second address segment, and determine, according to the communication information corresponding to the second address segment, a CDN cache server corresponding to the user equipment.
Optionally, the historical routing path is a historical autonomous domain path;
when the first address segment to which the source address belongs is determined, the first determining unit is specifically configured to determine a first autonomous domain to which the source address belongs, where the first autonomous domain corresponds to the first address segment;
when a second address segment with the hop count of the first address segment smaller than or equal to a preset value N is determined, the third determining unit is specifically configured to determine a second autonomous domain with the hop count of the first autonomous domain smaller than or equal to the preset value N, where the second autonomous domain corresponds to the second address segment.
Optionally, the third determining unit is specifically configured to determine, from the historical routing path, a second address segment corresponding to a previous hop of the first address segment.
Optionally, the method further includes:
an obtaining unit, configured to obtain communication information corresponding to the user equipment before the fourth determining unit determines, according to the communication information corresponding to the second address segment, the CDN cache server corresponding to the user equipment;
and the judging unit is used for judging that the CDN cache server corresponding to the user equipment cannot be determined according to the communication information corresponding to the user equipment.
Optionally, when the CDN cache server corresponding to the user equipment is determined according to the communication information corresponding to the second address segment, the fourth determining unit is specifically configured to:
determining a CDN cache server corresponding to the user equipment according to the communication information corresponding to the second address segment and the communication information corresponding to the user equipment; the communication information corresponding to the user equipment and the communication information corresponding to the second address field are communication information with different types.
Optionally, the method further includes:
a sending unit, configured to return an address of the CDN cache server to the user equipment after the fourth determining unit determines the CDN cache server corresponding to the user equipment according to the communication information corresponding to the second address segment.
Optionally, the source address includes an address of the user equipment, or an address of a local DNS server corresponding to the user equipment.
Optionally, the communication information corresponding to the second address field includes: operator information and/or geolocation information for the second address field.
According to the technical scheme, when the CDN cache server cannot be determined according to the communication information corresponding to the user equipment, the CDN cache server corresponding to the user equipment is determined according to the communication information corresponding to the second address segment instead of randomly setting the communication information or randomly designating the CDN cache server in the embodiment of the application. Because the hop count of the second address segment and the first address segment is less than or equal to the preset value N, it indicates that data transmitted to the first address segment generally passes through the second address segment, that is, the transmission quality from the second address segment to the first address segment is better, so that the CDN cache server determined according to the communication information corresponding to the second address segment has a higher probability of being suitable for the user equipment, and the speed when the user equipment accesses the CDN cache server can be faster.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed to be used in the description of the embodiments are briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and other drawings can be obtained by those skilled in the art according to the drawings.
FIG. 1 is a schematic flow chart of an embodiment of a method provided herein;
FIG. 2 is a schematic diagram of an AS-path provided herein;
FIG. 3 is a schematic flow chart diagram of another embodiment of a method provided herein;
fig. 4 is a schematic structural diagram of an embodiment of the apparatus provided in the present application.
Detailed Description
The conventional access procedure includes: the user equipment sends a Domain Name resolution request to a local Domain Name System (DNS) server, the local DNS server resolves the Domain Name in the request, returns the resolved destination IP address, and accesses the destination IP address to obtain the corresponding network resource.
The CDN technology is an intelligent DNS technology, and instead of returning a destination IP address to a user in a DNS resolution process, a CDN cache server corresponding to the user equipment is determined according to communication information of the user equipment, for example, operator information and/or geographical location information of the user equipment, that is, the user equipment accesses a CDN cache server corresponding to a faster network resource, and returns an IP address of the corresponding CDN cache server to the user equipment, so that the user equipment accesses the corresponding CDN cache server, and if the CDN cache server stores the network resource, the network resource is directly returned to the user equipment, so that the user equipment can obtain the network resource at a faster speed, and the purpose of accelerating access is achieved.
How to determine the CDN cache server corresponding to the user equipment is an important process for ensuring accelerated access. At present, when a CDN cache server corresponding to a user equipment is determined, a source address corresponding to the user equipment is obtained, communication information corresponding to the source address is obtained from an IP address library, and the CDN cache server corresponding to the user equipment is determined according to the communication information.
However, in the above process, it may not be possible to determine the CDN cache server corresponding to the user equipment. This will be explained in detail below.
For example, the obtained communication information is incomplete due to reasons such as non-normative or incomplete information of the IP address repository, and the like, which is not enough to determine a CDN cache server that accesses corresponding network resources quickly. The IP address base stores communication information such as address fields, geographic positions, operators and the like corresponding to each address. Although the information in the IP address base can be perfected according to the registration information in the WHOIS server, the IP address base still has the problems of informatization, informatization and the like, especially for operator information. The following are exemplified separately: 1. the information is not standardized: operators are all IP address fields communicated in China, and the operator information in an IP address library may be 'China Unicom backhaul' or 'Unicom Global network', that is to say, the same operator adopts different identifiers; 2. incomplete information: it is difficult to cover all operators who purchased IP address segments worldwide, especially some operators of smaller scale, in the IP address base.
For another example, no corresponding CDN cache server is deployed for communication information such as operator information of the corresponding user equipment. For example, the operator information corresponding to the user equipment is determined, but for some smaller-scale operators, it is very likely that a CDN cache server corresponding to the operator is not deployed.
If the CDN cache server corresponding to the user equipment and having the faster access to the network resource cannot be determined according to the communication information corresponding to the user equipment, for example, the communication information is incomplete (i.e., missing a key factor), which is not enough to determine the CDN cache server having the faster access to the corresponding network resource, the communication information is usually set randomly. For example, an operator is randomly set as an operator corresponding to the user equipment; for another example, a CDN cache server is not deployed, and usually one CDN cache server is randomly designated as the cache server corresponding to the user equipment. However, in this way of randomly setting communication information or randomly designating a CDN cache server, the speed of accessing network resources by a user is often slow.
The technical problem to be solved by the embodiment of the application is to provide a method and a device for determining a CDN cache server, so that when the CDN cache server cannot be determined according to communication information corresponding to user equipment, the CDN server suitable for the user equipment is determined according to a historical routing path of the user equipment, and therefore the access speed of the user equipment when accessing the CDN cache server is improved.
Referring to fig. 1, an embodiment of a method for determining a CDN cache server is provided in the present application. The determining method of the embodiment includes:
s101: the method comprises the steps of obtaining a source address corresponding to user equipment and determining a first address field to which the source address belongs.
In the embodiment of the present application, the address may refer to an IP address. For example, in step S101, a source IP address corresponding to the user equipment is obtained, and a first IP address segment to which the source IP address belongs is determined.
Since the application information of the user at the time of applying for the IP address field is usually stored in the IP address library, the first IP address field can be determined from the IP address library. For example, the source IP address is 198.0.0.1, and the first IP address segment to which the source IP address belongs is 198.0.0.1-198.0.0.255.
In this embodiment of the present application, the source address corresponding to the user equipment may be an address of the user equipment, that is, a client IP address, or may also be an address of a local DNS server corresponding to the user equipment, that is, a local DNS IP address.
S102: and determining a historical routing path corresponding to the first address segment.
The historical routing path can reflect the routing path of the user equipment in the historical communication process. And each node on the historical routing path corresponds to an address field respectively. For example, the historical routing path is node 1 → node 2 → node 3 → node 4. Wherein, the node 4 corresponds to the first address field, and the node 1, the node 2 and the node 3 correspond to one address field respectively.
Step S102 may determine a latest historical routing path from all historical routing paths corresponding to the first address segment, where the latest historical routing path may reflect the latest communication condition of the first address segment. For example, the above history routing path: node 1 → node 2 → node 3 → node 4 is the most recent historical routing path for node 4.
S103: and determining a second address field of which the hop count with the first address field is less than or equal to a preset value N from the historical routing path, wherein the preset value N is more than or equal to 1.
When the hop count of the second address field and the first address field is less than or equal to the preset value N, it indicates that data transmitted to the first address field usually passes through the second address field, i.e., the transmission quality from the second address field to the first address field is better.
The specific value of the preset value N is preset and may be equal to 1 or 2. For example, the historical routing path is node 1 → node 2 → node 3 → node 4, the node 4 corresponds to the first address segment, and since the number of hops between the node 3 and the node 4 is 1 and the number of hops between the node 2 and the node 4 is 2, the address segment of the node 2 or the node 3 is determined as the second address segment.
Since the address field of the previous hop is more likely to be the address field through which data is transmitted to the first address field, the second address field corresponding to the previous hop of the first address field may be determined from the historical routing path in step S103. For example, the last hop of the node 4, i.e., the address field corresponding to the node 3, is determined as the second address field.
S104: and obtaining communication information corresponding to the second address segment, and determining a CDN cache server corresponding to the user equipment according to the communication information corresponding to the second address segment.
In the embodiment of the application, when the corresponding CDN cache server cannot be determined according to the communication information corresponding to the user equipment, the CDN cache server is determined by using the communication information corresponding to the second address segment. After the CDN cache server is determined, an address of the CDN cache server may be returned to the user equipment, so that the user equipment accesses the CDN cache server. The communication information corresponding to the second address field may include: operator information and/or geolocation information for the second address field.
Because the transmission quality from the second address segment to the first address segment is better, compared with randomly setting communication information or randomly appointing a CDN cache server, the embodiment of the application can allocate the CDN cache server more suitable for the user equipment to the user equipment, thereby improving the speed of the user equipment accessing the CDN cache server.
It should be noted that, in the embodiment of the present application, the communication information corresponding to the second address field obtained according to steps S101 to S104 may be obtained in real time after receiving a domain name resolution request of the user equipment, or may be obtained in advance and stored in a corresponding database. The information in the database can be regularly updated in a pre-acquired and stored mode, so that the pre-stored information can be directly utilized in the domain name resolution process, and the access speed is further increased. Specifically, after the communication information corresponding to the second address field is acquired, the communication information is stored in a corresponding database as the communication information corresponding to the user equipment or the first address field. After receiving a domain name resolution request of user equipment, according to the domain name resolution request, communication information corresponding to the user equipment can be directly obtained from the database, and a corresponding CDN cache server is determined according to the obtained communication information.
According to the technical scheme, when the CDN cache server cannot be determined according to the communication information corresponding to the user equipment, the CDN cache server corresponding to the user equipment is determined according to the communication information corresponding to the second address segment instead of randomly setting the communication information or randomly designating the CDN cache server in the embodiment of the application. Because the hop count of the second address segment and the first address segment is less than or equal to the preset value N, it indicates that data transmitted to the first address segment generally passes through the second address segment, that is, the transmission quality from the second address segment to the first address segment is better, so that the CDN cache server determined according to the communication information corresponding to the second address segment has a higher probability of being suitable for the user equipment, and the speed when the user equipment accesses the CDN cache server can be faster.
In this embodiment of the present application, the determining method may be used in a device for determining a CDN cache server, where the determining device may be located in an intelligent DNS server or a CDN system. The user equipment in this embodiment may be any electronic equipment for a client, such as a mobile phone, a tablet computer, and a notebook.
The embodiment of the application is used for determining the condition of the CDN cache server corresponding to the user equipment according to the communication information corresponding to the user equipment. Therefore, before step S104, the determining method of the present embodiment further includes: acquiring communication information corresponding to the user equipment; and judging whether the CDN cache server corresponding to the user equipment cannot be determined according to the communication information corresponding to the user equipment. For example, the operator information corresponding to the user equipment cannot be acquired in the IP address repository, or a CDN cache server of a corresponding operator is not deployed.
When the CDN cache server corresponding to the user equipment is determined in step S104, the method may also be based on communication information corresponding to the second address segment and communication information corresponding to the user equipment, where at this time, the communication information corresponding to the user equipment and the communication information corresponding to the second address segment are communication information of different types. For example, according to the operator information corresponding to the second address segment and the geographic location information corresponding to the user equipment, a CDN cache server corresponding to the user equipment is determined.
In the embodiment of the application, if it is determined that the CDN cache server corresponding to the user equipment can be determined according to the communication information corresponding to the user equipment, the CDN cache server corresponding to the user equipment is determined by directly using the communication information corresponding to the user equipment.
Since each address field has a corresponding Autonomous domain (hereinafter referred to AS "), in the embodiment of the present application, all address fields can be represented by AS, and one AS has an Autonomous domain Number (hereinafter referred to AS" ASN "). An AS, also called a routing domain, is a network element that has the authority to autonomously decide what routing protocol to use in the system, and may be, for example, a university or a company's network.
The historical routing path may be an historical autonomous domain path (AS-path). When a user accesses a network, Border Gateway Protocol (BGP) routing may be routed from one AS to another, thereby traversing multiple ases. When the BGP route is sent to the next AS, the ASN of the current AS will be carried in the route, and after the next AS receives the route, the next AS will continue to add its own ASN to the route, thereby generating an AS-path carried in the BGP route. For example, the network shown in fig. 2 includes AS10, AS20, AS30, AS40, and AS50, and one AS-path from AS10 to AS50 is AS10 → AS20 → AS30 → AS 50. Many AS-path information is searchable, for example, a RouteViews item provides a relatively real-time global routing table, and an aspath.
Therefore, in the embodiment of the application, the second address field can be determined by using the AS and the historical AS-path. Specifically, the historical routing path is a historical AS-path; the step S101 of determining the first address segment to which the source address belongs includes: determining a first AS to which the source address belongs, wherein the first AS corresponds to the first address field; the step S103 of determining a second address segment having a hop count smaller than or equal to the preset value N with respect to the first address segment includes: and determining a second AS of which the hop count is smaller than or equal to the preset value N and which corresponds to the second address field. This is illustrated by a specific example.
Referring to fig. 3, another method embodiment of a method for determining a CDN cache server is provided in the present application.
The determining method of the embodiment includes:
s301: and acquiring communication information corresponding to the user equipment from an IP address library, judging whether a CDN cache server can be determined according to the communication information, and if not, executing S302.
Whether the CDN cache server can be determined according to the communication information is judged, whether the communication information comprises operator information can be judged, and whether the CDN cache server corresponding to the operator information is deployed can also be judged.
S302: and acquiring a source address corresponding to the user equipment, and determining that the source address corresponds to AS50, wherein the AS50 corresponds to the first IP address field.
The source address may be a client IP address or a local DNS IP address.
S303: determining a latest AS-path corresponding to the AS50 from the global routing table provided by the RouteViews project: AS10 → AS20 → AS30 → AS 50.
S304: and determining the ASN corresponding to the last hop of the AS50, namely AS30, from the AS-path, wherein the AS30 corresponds to the second IP address field.
S305: and acquiring the operator information corresponding to the AS30 from the IP address library, and storing the operator information in the IP address library AS the operator information corresponding to the user equipment.
S306: and receiving a domain name resolution request sent by the user equipment.
S307: and determining a corresponding CDN cache server according to the operator information and the geographic position information corresponding to the user equipment in the IP address library, and returning the IP address of the CDN cache server to the user equipment so that the user equipment accesses the CDN cache server.
In the embodiment of the application, the CDN cache server determined according to the communication information corresponding to the last hop, that is, AS30, can better adapt to the user equipment than the CDN cache server determined according to the communication information corresponding to AS10 or AS20, thereby further improving the access speed.
Corresponding to the above method embodiments, the present application also provides corresponding apparatus embodiments, which are specifically described below.
Referring to fig. 4, an embodiment of a device for determining a CDN cache server is further provided. The apparatus of this embodiment includes: a first determining unit 401, a second determining unit 402, a third determining unit 403, and a fourth determining unit 404.
A first determining unit 401, configured to obtain a source address corresponding to a user equipment, and determine a first address field to which the source address belongs.
In the embodiment of the present application, the address may refer to an IP address. For example, the first determining unit 401 obtains a source IP address corresponding to the user equipment, and determines a first IP address field to which the source IP address belongs.
Since the application information of the user when applying for the IP address field is usually stored in the IP address library, the first determining unit 401 may determine the first IP address field from the IP address library. For example, the source IP address is 198.0.0.1, and the first IP address segment to which the source IP address belongs is 198.0.0.1-198.0.0.255.
In this embodiment of the present application, the source address corresponding to the user equipment may be an address of the user equipment, that is, a client IP address, or may also be an address of a local DNS server corresponding to the user equipment, that is, a local DNS IP address.
A second determining unit 402, configured to determine a historical routing path corresponding to the first address segment.
The historical routing path can reflect the routing path of the user equipment in the historical communication process. And each node on the historical routing path corresponds to an address field respectively. For example, the historical routing path is node 1 → node 2 → node 3 → node 4. Wherein, the node 4 corresponds to the first address field, and the node 1, the node 2 and the node 3 correspond to one address field respectively.
The second determining unit 402 may determine a latest historical routing path from all historical routing paths corresponding to the first address segment, where the latest historical routing path reflects the latest communication condition of the first address segment. For example, the above history routing path: node 1 → node 2 → node 3 → node 4 is the most recent historical routing path for node 4.
A third determining unit 403, configured to determine, from the historical routing path, a second address segment whose hop count with the first address segment is less than or equal to a preset value N, where the preset value N is greater than or equal to 1.
When the hop count of the second address field and the first address field is less than or equal to the preset value N, it indicates that data transmitted to the first address field usually passes through the second address field, i.e., the transmission quality from the second address field to the first address field is better.
The specific value of the preset value N is preset and may be equal to 1 or 2. For example, the historical routing path is node 1 → node 2 → node 3 → node 4, the node 4 corresponds to the first address segment, and since the number of hops between the node 3 and the node 4 is 1 and the number of hops between the node 2 and the node 4 is 2, the address segment of the node 2 or the node 3 is determined as the second address segment.
Since the address field of the previous hop is more likely to be an address field through which data is transmitted to the first address field, the third determination unit 403 may determine the second address field corresponding to the previous hop of the first address field from the historical routing path. For example, the last hop of the node 4, i.e., the address field corresponding to the node 3, is determined as the second address field.
A fourth determining unit 404, configured to obtain communication information corresponding to the second address segment, and determine, according to the communication information corresponding to the second address segment, a CDN cache server corresponding to the user equipment.
In this embodiment of the application, when the corresponding CDN cache server cannot be determined according to the communication information corresponding to the user equipment, the fourth determining unit 404 determines the CDN cache server by using the communication information corresponding to the second address segment. After the CDN cache server is determined, a sending unit may return an address of the CDN cache server to the user equipment, so that the user equipment accesses the CDN cache server. The communication information corresponding to the second address field may include: operator information and/or geolocation information for the second address field.
Because the transmission quality from the second address segment to the first address segment is better, compared with randomly setting communication information or randomly appointing a CDN cache server, the embodiment of the application can allocate the CDN cache server more suitable for the user equipment to the user equipment, thereby improving the speed of the user equipment accessing the CDN cache server.
It should be noted that the communication information corresponding to the second address field obtained in this embodiment may be obtained in real time after receiving a domain name resolution request of the user equipment, or may be obtained in advance and stored in a corresponding database. The information in the database can be regularly updated in a pre-acquired and stored mode, so that the pre-stored information can be directly utilized in the domain name resolution process, and the access speed is further increased. Specifically, after the communication information corresponding to the second address field is acquired, the communication information is stored in a corresponding database as the communication information corresponding to the user equipment or the first address field. After receiving a domain name resolution request of user equipment, according to the domain name resolution request, communication information corresponding to the user equipment can be directly obtained from the database, and a corresponding CDN cache server is determined according to the obtained communication information.
In the embodiment of the present application, the determining means may be located in an intelligent DNS server or a CDN system. The user equipment in this embodiment may be any electronic equipment for a client, such as a mobile phone, a tablet computer, and a notebook.
Optionally, the historical routing path is a historical autonomous domain path; when the first address segment to which the source address belongs is determined, the first determining unit is specifically configured to determine a first autonomous domain to which the source address belongs, where the first autonomous domain corresponds to the first address segment; when a second address segment with the hop count of the first address segment smaller than or equal to a preset value N is determined, the third determining unit is specifically configured to determine a second autonomous domain with the hop count of the first autonomous domain smaller than or equal to the preset value N, where the second autonomous domain corresponds to the second address segment.
Optionally, the third determining unit is specifically configured to determine, from the historical routing path, a second address segment corresponding to a previous hop of the first address segment.
Optionally, the apparatus further comprises: an obtaining unit, configured to obtain communication information corresponding to the user equipment before the fourth determining unit determines, according to the communication information corresponding to the second address segment, the CDN cache server corresponding to the user equipment; and the judging unit is used for judging that the CDN cache server corresponding to the user equipment cannot be determined according to the communication information corresponding to the user equipment.
Optionally, when the CDN cache server corresponding to the user equipment is determined according to the communication information corresponding to the second address segment, the fourth determining unit is specifically configured to:
determining a CDN cache server corresponding to the user equipment according to the communication information corresponding to the second address segment and the communication information corresponding to the user equipment; the communication information corresponding to the user equipment and the communication information corresponding to the second address field are communication information with different types.
Optionally, the method further includes:
a sending unit, configured to return an address of the CDN cache server to the user equipment after the fourth determining unit determines the CDN cache server corresponding to the user equipment according to the communication information corresponding to the second address segment.
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 server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and other various media capable of storing program codes.
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 (14)
1. A CDN cache server determination method is characterized by comprising the following steps:
obtaining a source address corresponding to user equipment, and determining a first address field to which the source address belongs;
determining a historical routing path corresponding to the first address segment;
determining a second address segment of which the hop count with the first address segment is less than or equal to a preset value N from the historical routing path, wherein the preset value N is more than or equal to 1;
acquiring communication information corresponding to the second address segment, and determining a CDN cache server corresponding to the user equipment according to the communication information corresponding to the second address segment, where the communication information corresponding to the second address segment includes: operator information and/or geolocation information for the second address field.
2. The determination method according to claim 1, wherein the historical routing path is a historical autonomous domain path; determining a first address segment to which the source address belongs, including:
determining a first autonomous domain to which the source address belongs, wherein the first autonomous domain corresponds to the first address field;
determining a second address field with the hop count of the first address field being less than or equal to a preset value N, comprising:
and determining a second autonomous domain of which the hop count is less than or equal to the preset value N, wherein the second autonomous domain corresponds to the second address field.
3. The method of claim 1, wherein determining a second address segment from the historical routing path having a hop count less than or equal to a predetermined value N from the first address segment comprises:
and determining a second address field corresponding to the previous hop of the first address field from the historical routing path.
4. The method according to claim 1, wherein before determining the CDN cache server corresponding to the user equipment according to the communication information corresponding to the second address segment, the method further includes:
acquiring communication information corresponding to the user equipment;
and judging that the CDN cache server corresponding to the user equipment cannot be determined according to the communication information corresponding to the user equipment.
5. The method according to claim 4, wherein determining the CDN cache server corresponding to the user equipment according to the communication information corresponding to the second address segment includes:
determining a CDN cache server corresponding to the user equipment according to the communication information corresponding to the second address segment and the communication information corresponding to the user equipment; the communication information corresponding to the user equipment and the communication information corresponding to the second address field are communication information with different types.
6. The method according to claim 1, wherein after the CDN cache server corresponding to the user equipment is determined according to the communication information corresponding to the second address segment, the method further includes:
and returning the address of the CDN cache server to the user equipment.
7. The determination method according to any one of claims 1 to 6, wherein the source address comprises an address of the user equipment or an address of a local DNS server corresponding to the user equipment.
8. An apparatus for determining a CDN cache server, the apparatus comprising:
the first determining unit is used for acquiring a source address corresponding to the user equipment and determining a first address field to which the source address belongs;
a second determining unit, configured to determine a historical routing path corresponding to the first address segment;
a third determining unit, configured to determine, from the historical routing path, a second address segment whose hop count with the first address segment is less than or equal to a preset value N, where the preset value N is greater than or equal to 1;
a fourth determining unit, configured to obtain communication information corresponding to the second address segment, and determine, according to the communication information corresponding to the second address segment, a CDN cache server corresponding to the user equipment, where the communication information corresponding to the second address segment includes: operator information and/or geolocation information for the second address field.
9. The determination apparatus of claim 8, wherein the historical routing path is a historical autonomous domain path;
when the first address segment to which the source address belongs is determined, the first determining unit is specifically configured to determine a first autonomous domain to which the source address belongs, where the first autonomous domain corresponds to the first address segment;
when a second address segment with the hop count of the first address segment smaller than or equal to a preset value N is determined, the third determining unit is specifically configured to determine a second autonomous domain with the hop count of the first autonomous domain smaller than or equal to the preset value N, where the second autonomous domain corresponds to the second address segment.
10. The apparatus according to claim 8, wherein the third determining unit is specifically configured to determine, from the historical routing path, a second address segment corresponding to a previous hop of the first address segment.
11. The determination apparatus according to claim 8, further comprising:
an obtaining unit, configured to obtain communication information corresponding to the user equipment before the fourth determining unit determines, according to the communication information corresponding to the second address segment, the CDN cache server corresponding to the user equipment;
and the judging unit is used for judging that the CDN cache server corresponding to the user equipment cannot be determined according to the communication information corresponding to the user equipment.
12. The apparatus according to claim 11, wherein when the CDN cache server corresponding to the user equipment is determined according to the communication information corresponding to the second address segment, the fourth determining unit is specifically configured to:
determining a CDN cache server corresponding to the user equipment according to the communication information corresponding to the second address segment and the communication information corresponding to the user equipment; the communication information corresponding to the user equipment and the communication information corresponding to the second address field are communication information with different types.
13. The determination apparatus according to claim 8, further comprising:
a sending unit, configured to return an address of the CDN cache server to the user equipment after the fourth determining unit determines the CDN cache server corresponding to the user equipment according to the communication information corresponding to the second address segment.
14. The apparatus according to any one of claims 8 to 13, wherein the source address comprises an address of the user equipment or an address of a local DNS server corresponding to the user equipment.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610440363.6A CN107517162B (en) | 2016-06-17 | 2016-06-17 | CDN cache server determination method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610440363.6A CN107517162B (en) | 2016-06-17 | 2016-06-17 | CDN cache server determination method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN107517162A CN107517162A (en) | 2017-12-26 |
| CN107517162B true CN107517162B (en) | 2020-09-04 |
Family
ID=60719956
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201610440363.6A Active CN107517162B (en) | 2016-06-17 | 2016-06-17 | CDN cache server determination method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN107517162B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110430290B (en) * | 2019-08-02 | 2022-06-10 | 深圳市网心科技有限公司 | Resource address updating method, computer device and storage medium |
| CN114615550B (en) * | 2022-03-17 | 2023-12-08 | 北京奇艺世纪科技有限公司 | Video acquisition method and device |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101729591A (en) * | 2008-10-29 | 2010-06-09 | 中国移动通信集团公司 | User guide device, system and method |
| CN101808079A (en) * | 2009-02-12 | 2010-08-18 | 华为技术有限公司 | Method, server and client for determining direct neighbor nodes |
| CN104427005A (en) * | 2013-08-20 | 2015-03-18 | 阿里巴巴集团控股有限公司 | Method and system for realizing accurate request scheduling on content delivery network |
| CN104954219A (en) * | 2014-03-27 | 2015-09-30 | 北京奇虎科技有限公司 | CDN (Content Delivery Network) access path optimization method, device and system |
| CN105634784A (en) * | 2014-11-06 | 2016-06-01 | 阿里巴巴集团控股有限公司 | Method, device and system for distributing control data |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103024001B (en) * | 2012-11-30 | 2018-07-31 | 中兴通讯股份有限公司 | A kind of business scheduling method and device and fusion device |
-
2016
- 2016-06-17 CN CN201610440363.6A patent/CN107517162B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101729591A (en) * | 2008-10-29 | 2010-06-09 | 中国移动通信集团公司 | User guide device, system and method |
| CN101808079A (en) * | 2009-02-12 | 2010-08-18 | 华为技术有限公司 | Method, server and client for determining direct neighbor nodes |
| CN104427005A (en) * | 2013-08-20 | 2015-03-18 | 阿里巴巴集团控股有限公司 | Method and system for realizing accurate request scheduling on content delivery network |
| CN104954219A (en) * | 2014-03-27 | 2015-09-30 | 北京奇虎科技有限公司 | CDN (Content Delivery Network) access path optimization method, device and system |
| CN105634784A (en) * | 2014-11-06 | 2016-06-01 | 阿里巴巴集团控股有限公司 | Method, device and system for distributing control data |
Non-Patent Citations (2)
| Title |
|---|
| "Integrating routing with cntent delivery networks";BrianField等;《IEEE》;20120503;全文 * |
| "一种CDN Web缓存系统的设计与实现";张天一;《中国优秀硕士学位论文全文数据库 信息科技辑I137-27》;20131115;全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN107517162A (en) | 2017-12-26 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11064325B2 (en) | Method of discovering services provided by a network repository function | |
| US20230224273A1 (en) | Network containers | |
| US9866576B2 (en) | Rule-based network-threat detection | |
| US9984158B2 (en) | Finding services in a service-oriented architecture (SOA) network | |
| WO2021004528A1 (en) | Method, device and apparatus for address acquisition of application example and storage medium | |
| CN108494755B (en) | Method and device for transmitting Application Programming Interface (API) request | |
| US20210314156A1 (en) | Authentication method, content delivery network cdn, and content server | |
| CN109088909B (en) | Service gray level publishing method and device based on merchant type | |
| US10237805B2 (en) | Telecommunications routing system | |
| CN108429739B (en) | Method, system and terminal equipment for identifying honeypots | |
| KR20190007041A (en) | Method and device for data version comparison between time zone transit stations | |
| US11411839B1 (en) | System and method to correlate end user experience with location | |
| CN113489636A (en) | Location-based access control for human dialog entities | |
| CN110968356A (en) | Method and device for acquiring configuration information | |
| CN112825524B (en) | Method, device and system for determining network service node | |
| JP2016218975A (en) | Connection destination server instruction device, service use system, client terminal, connection destination server instruction method, and program | |
| CN107517162B (en) | CDN cache server determination method and device | |
| WO2017000669A1 (en) | Centralised management control method, apparatus, and related device for domain name resource record caching | |
| US10143022B2 (en) | Dynamic generation of geographically bound MANET IDs | |
| CN107682271B (en) | Method and device for generating routing line | |
| CN110769462B (en) | Network access control method and device | |
| US10958580B2 (en) | System and method of performing load balancing over an overlay network | |
| KR20150112127A (en) | Local resource sharing method of machine to machine component and apparatus thereof | |
| CN113676540B (en) | Connection establishment method and device | |
| CN106165359B (en) | Data stream distribution method and device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| 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 |