WO2019144899A1 - 一种回源关系管理系统、方法、装置、服务器及存储介质 - Google Patents

一种回源关系管理系统、方法、装置、服务器及存储介质 Download PDF

Info

Publication number
WO2019144899A1
WO2019144899A1 PCT/CN2019/072937 CN2019072937W WO2019144899A1 WO 2019144899 A1 WO2019144899 A1 WO 2019144899A1 CN 2019072937 W CN2019072937 W CN 2019072937W WO 2019144899 A1 WO2019144899 A1 WO 2019144899A1
Authority
WO
WIPO (PCT)
Prior art keywords
source
cdn node
relationship
management server
source relationship
Prior art date
Application number
PCT/CN2019/072937
Other languages
English (en)
French (fr)
Inventor
姜然
Original Assignee
北京金山云网络技术有限公司
北京金山云科技有限公司
北京金迅瑞博网络技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 北京金山云网络技术有限公司, 北京金山云科技有限公司, 北京金迅瑞博网络技术有限公司 filed Critical 北京金山云网络技术有限公司
Priority to US16/962,565 priority Critical patent/US11588723B2/en
Publication of WO2019144899A1 publication Critical patent/WO2019144899A1/zh

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/10—File systems; File servers
    • G06F16/17—Details of further file system functions
    • G06F16/172—Caching, prefetching or hoarding of files
    • 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/02—Topology update or discovery
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F12/00—Accessing, addressing or allocating within memory systems or architectures
    • G06F12/02—Addressing or allocation; Relocation
    • G06F12/08—Addressing or allocation; Relocation in hierarchically structured memory systems, e.g. virtual memory systems
    • G06F12/0802—Addressing of a memory level in which the access to the desired data or data block requires associative addressing means, e.g. caches
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/27—Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
    • 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/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • H04L41/0813—Configuration setting characterised by the conditions triggering a change of settings
    • H04L41/0816—Configuration setting characterised by the conditions triggering a change of settings the condition being an adaptation, e.g. in response to network events
    • 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/12—Discovery or management of network topologies
    • 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/22—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks comprising specially adapted graphical user interfaces [GUI]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/45—Network directories; Name-to-address mapping
    • H04L61/4505—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols
    • H04L61/4511—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols using domain name system [DNS]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/58—Caching of addresses or names
    • 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/2866—Architectures; Arrangements
    • H04L67/289—Intermediate processing functionally located close to the data consumer application, e.g. in same machine, in same home or in same sub-network
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F2212/00—Indexing scheme relating to accessing, addressing or allocation within memory systems or architectures
    • G06F2212/15—Use in a specific computing environment
    • G06F2212/154—Networked environment
    • 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/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • H04L41/084—Configuration by using pre-existing information, e.g. using templates or copying from other elements
    • H04L41/0843—Configuration by using pre-existing information, e.g. using templates or copying from other elements based on generic templates

Definitions

  • the present application relates to the field of network device management technologies, and in particular, to a source relationship management system, method, device, server, and storage medium.
  • CDN Content Delivery Network
  • the source configuration file is a file sent by the server to the CDN node.
  • the source configuration file is generated based on the correspondence between the domain name and the CDN node return source relationship. That is, when the CDN node needs to obtain a content from a source station, it needs to find the next hop device corresponding to the domain name of the content that needs to be returned to the source in the locally stored source configuration file, so as to find the next hop device. The hop device returns to the source and gets the content that needs to be returned.
  • the content refresh server also needs to issue a refresh command to the CDN node according to the CDN node return source relationship corresponding to the domain name, thereby implementing content refresh.
  • the CDN node return source relationship corresponding to a domain name can be understood as: starting from a CDN node and backtracking to the path of the source site corresponding to the domain name.
  • the CDN node return source relationship corresponding to the domain name a is: CDN1 node ⁇ CDN2 node ⁇ CDN3 node ⁇ the source station of the domain name a;
  • the CDN node corresponding source relationship of the domain name b is: CDN1 node ⁇ CDN3 node ⁇ CDN4 node ⁇ domain name b Source station, and source station of CDN1 node ⁇ CDN5 node ⁇ CDN6 node ⁇ domain name b.
  • each time a CDN node corresponding to a domain name is changed the technician needs to manually modify the CDN node corresponding to the domain name stored in each cache management server such as the source configuration file delivery server and the content refresh server. Back to source relationship.
  • the modification is large, time-consuming and laborious and error-prone.
  • the purpose of the embodiments of the present application is to provide a system, a method, a device, a server, and a storage medium, which are capable of uniformly managing the source relationship of CDN nodes corresponding to each domain name, thereby reducing the maintenance of the source relationship of the CDN nodes. Cost and error rate, and improve maintenance efficiency.
  • the embodiment of the present application provides a return source relationship management system, where the source relationship management system includes: a source relationship management server and a cache management server;
  • the source relationship management server is set to:
  • the cache management server is set to:
  • the adjusted source CDN node return source relationship is used to update the CDN node return source relationship corresponding to the target domain name stored in the cache management server, and the new CDN node return source relationship is obtained.
  • the cache management server includes: a source configuration file delivery server and/or a content refresh server;
  • the source configuration file delivery server is also set to:
  • the content refresh server is further configured to generate a refresh command of each CDN node in the new CDN node return source relationship based on the new CDN node return source relationship, and deliver the generated refresh command to the refresh command. Corresponding CDN node.
  • the source-back relationship management server is further configured to obtain, by using the following manner, a target domain name corresponding to the target CDN node return source relationship to be adjusted, and adjustment information for the target CDN node return source relationship:
  • the adjustment information for the topology map sent by the user terminal is received as the adjustment information for the source relationship of the target CDN node.
  • the adjustment information for the topology map may include at least one of the following information:
  • the operation information corresponding to the modification of the connection relationship between the CDN nodes is performed.
  • the source-back relationship management server is further configured to determine, according to the first mapping relationship table, a source CDN node return source relationship corresponding to the target domain name by:
  • the source CDN node corresponding to the target domain name in the first mapping relationship table is searched for the source relationship.
  • the source relationship management server may also be configured to:
  • the default CDN node is returned to the source relationship as the target CDN node corresponding to the target domain name.
  • the embodiment of the present application provides a return source relationship management method, which is applied to a back source relationship management server in a back source relationship management system, where the source relationship management system further includes a cache management server, and the cache management server is used for caching.
  • the mapping relationship between the domain name and the source relationship of the CDN node, the method may include:
  • the step of obtaining the target domain name corresponding to the source CDN node return source relationship to be adjusted, and the adjusting information for the target CDN node return source relationship may include:
  • the adjustment information for the topology map sent by the user terminal is received as the adjustment information for the source relationship of the target CDN node.
  • the adjustment information for the topology map may include at least one of the following information:
  • the operation information corresponding to the modification of the connection relationship between the CDN nodes is performed.
  • the step of determining, according to the first mapping relationship table, the source CDN node corresponding to the target domain name may include:
  • the method may further include:
  • the default CDN node is returned to the source relationship as the target CDN node corresponding to the target domain name.
  • the embodiment of the present application further provides a method for managing a return source relationship, which is applied to a cache management server in a source relationship management system, where the source relationship management system further includes a source relationship management server, and the method may include:
  • the adjusted source CDN node return source relationship is used to update the CDN node return source relationship corresponding to the target domain name stored in the cache management server, and the new CDN node return source relationship is obtained.
  • the cache management server includes: a source configuration file delivery server and/or a content refresh server; the method may further include:
  • the cache management server delivers the server to the source configuration file
  • the source configuration file of each CDN node in the source relationship of the new CDN node is generated based on the source relationship of the new CDN node, and the generated source configuration file is sent.
  • the refresh command of each CDN node in the new CDN node return source relationship is generated based on the new CDN node return source relationship, and the generated refresh command is sent to the corresponding CDN node.
  • the embodiment of the present application provides a return source relationship management apparatus, which is applied to a back source relationship management server in a back source relationship management system, where the source relationship management system further includes a cache management server, and the cache management server is set to be cached.
  • the mapping between the domain name and the source relationship of the CDN node, the device may include:
  • Obtaining a unit configured to obtain a target domain name corresponding to a source CDN node return source relationship to be adjusted, and adjustment information for a target CDN node return source relationship;
  • the adjusting unit is configured to adjust the return relationship of the target CDN node by using the adjustment information, and obtain the adjusted source CDN node return source relationship; wherein, the target CDN node return source relationship is: determined based on the target domain name and the first mapping relationship table
  • the first mapping relationship table is configured to store the domain name and the CDN node return source relationship correspondingly;
  • the synchronization unit is configured to synchronize the target domain name and the adjusted target CDN node back source relationship to the cache management server.
  • the obtaining unit may include:
  • a first receiving subunit configured to receive a target domain name corresponding to a source CDN node back source relationship to be adjusted
  • Determining a subunit configured to determine, according to the first mapping relationship table, a source CDN node return source relationship corresponding to the target domain name;
  • a sending subunit configured to send information determined by the target CDN node back source relationship to the user terminal, so that the user terminal obtains and displays a topology map corresponding to the source CDN node return source relationship based on the information;
  • the second receiving subunit is configured to receive the adjustment information for the topology map sent by the user terminal, as the adjustment information for the source CDN node return source relationship.
  • the adjustment information for the topology map may include at least one of the following information:
  • the operation information corresponding to the modification of the connection relationship between the CDN nodes is performed.
  • determining the subunit includes:
  • the determining module is configured to determine whether the target domain name can be found in the first mapping relationship table after obtaining the target domain name corresponding to the target CDN node return source relationship to be adjusted, and the adjustment information for the target CDN node return source relationship;
  • the search module is configured to: when the target domain name can be found in the first mapping table, search for a target CDN node return source relationship corresponding to the target domain name in the first mapping relationship table.
  • the apparatus may further include:
  • the determining module is configured to: when the target domain name cannot be found in the first mapping relationship table, the default CDN node return relationship is used as the target CDN node return source relationship corresponding to the target domain name.
  • the embodiment of the present application further provides a source-back relationship management device, which is applied to a cache management server in a source-back relationship management system, where the source relationship management system further includes a source-back relationship management server, and the device may include:
  • the receiving unit is configured to receive, by the source relation management server, the target domain name and the adjusted target CDN node return source relationship;
  • the update unit is configured to update the CDN node return source relationship corresponding to the target domain name stored in the cache management server by using the adjusted target CDN node return source relationship, and obtain a new CDN node return source relationship.
  • the cache management server includes: a source configuration file delivery server and/or a content refresh server; the device may further include:
  • the first generating unit is configured to: when the cache management server delivers the server as the source configuration file, generate a return source configuration file of each CDN node in the new CDN node return source relationship based on the new CDN node return source relationship, and generate The source configuration file is sent to the corresponding CDN node;
  • the second generating unit is configured to: when the cache management server is the content refreshing server, generate a refresh command of each CDN node in the source relationship of the new CDN node based on the source relationship of the new CDN node, and send the generated refresh command to the Corresponding CDN node.
  • the embodiment of the present application further provides a back source relationship management server, where the source relationship management server is a server in the source relationship management system, and the source relationship management system further includes a cache management server, and the cache management server is configured to a mapping relationship between the cache domain name and the CDN node return source relationship;
  • the source relationship management server includes a processor, a communication interface, a memory, and a communication bus, wherein the processor, the communication interface, and the memory complete communication with each other through the communication bus;
  • a memory configured to store a computer program
  • the embodiment of the present application further provides a cache management server, where the cache management server is a server in the source relationship management system, and the source relationship management system further includes a source relationship management server;
  • the cache management server includes a processor, a communication interface, a memory, and a communication bus, wherein the processor, the communication interface, and the memory complete communication with each other through the communication bus;
  • a memory configured to store a computer program
  • the processor when configured to execute a program stored on the memory, implements the method steps provided by any one of the method embodiments of the third aspect.
  • the embodiment of the present application further provides a storage medium, which is: a storage medium in a source relationship management server, and the source relationship management server is a server in the source relationship management system, and the source relationship management is The system further includes a cache management server, and the cache management server is configured to map a cache domain name to a relationship between the CDN node and the source relationship; the storage medium stores a computer program, and when the computer program is executed by the processor, the method of implementing the second aspect is implemented.
  • the storage medium is a computer readable storage medium.
  • the embodiment of the present application further provides a storage medium, which is: a storage medium in a cache management server, where the cache management server is a server in the source relationship management system, and the source relationship management system further includes The source relationship management server; the computer program is stored in the storage medium, and when the computer program is executed by the processor, the method steps provided in any one of the method embodiments are implemented.
  • the storage medium is a computer readable storage medium.
  • the embodiment of the present application further provides a computer program product, which is used to implement the method steps provided by any one of the method embodiments in the second aspect.
  • the embodiment of the present application further provides a computer program product, which is used to implement the method steps provided by any one of the method embodiments in the third aspect.
  • the back source relationship management server may obtain the target domain name corresponding to the target CDN node return source relationship. And obtaining, by using the target domain name and the first mapping relationship table stored in the source relationship management server, the source CDN node return source relationship corresponding to the target domain name.
  • the first mapping relationship table is used to store the domain name and the CDN node back source relationship.
  • the back source relationship management server may adjust the return relationship of the target CDN node according to the obtained adjustment information for the source CDN node return source relationship, and obtain the adjusted target CDN node return source relationship.
  • the adjusted target CDN node return source relationship can be synchronized to the cache management server. In this way, the technician does not need to manually modify the CDN node return source relationship corresponding to each domain name stored in the cache management server, thereby reducing the maintenance cost and error rate of the CDN node return source relationship, and improving the maintenance efficiency.
  • FIG. 1 is a flowchart of a method for managing a return source relationship according to an embodiment of the present application
  • FIG. 2 is a topological structural diagram provided by an embodiment of the present application.
  • FIG. 3 is a flowchart of another method for managing a return source relationship according to an embodiment of the present application
  • FIG. 4 is a schematic structural diagram of a device for returning source relationship management according to an embodiment of the present disclosure
  • FIG. 5 is a schematic structural diagram of another device for returning source relationship according to an embodiment of the present disclosure.
  • FIG. 6 is a schematic structural diagram of a back source relationship management server according to an embodiment of the present application.
  • FIG. 7 is a schematic structural diagram of a cache management server according to an embodiment of the present application.
  • FIG. 8 is a schematic diagram of a back source relationship management system according to an embodiment of the present application.
  • the embodiment of the present application provides a back source relationship management system, method, device, server, and storage medium.
  • the following is a description of the method for managing the return source relationship provided by the implementation of the present application from the perspective of the source relationship management server.
  • the back source relationship management method is applied to: a source relationship management server in the source relationship management system.
  • the back source relationship management system also includes a cache management server.
  • the back source relationship management system may also be referred to as a CDN (Content Delivery Network) central control system.
  • CDN Content Delivery Network
  • the number of cache management servers in the back source relationship management system may be one or more, which is reasonable.
  • Each cache management server is configured to: a mapping relationship between the cached domain name and the source relationship of the CDN node, and is cached by the CDN node based on a mapping relationship between the domain name cached by the cache management server and the source relationship of the CDN node. The content is managed.
  • the cache management server when the cache management server sends the server to the source configuration file, the cache server sends a source configuration file to the CDN node corresponding to the domain name based on the mapping relationship between the cached domain name and the CDN node's source relationship. The management of the content cached by the CDN node is thereby implemented by the source configuration file.
  • the source relationship management server may store: a CDN node return source relationship cached in the cache management server in the source relationship management system.
  • the switchback source relationship of the CDN node cached in the cache management server in the source management system can be managed in a unified manner. For the management mode, refer to the method steps shown in FIG.
  • the method can include the following steps:
  • S101 Obtain a target domain name corresponding to a source CDN node return source relationship to be adjusted, and adjustment information for a target CDN node return source relationship;
  • S102 Adjusting a return relationship of the target CDN node by using the adjustment information, and obtaining an adjusted target CDN node return source relationship; wherein, the target CDN node return source relationship is: determined based on the target domain name and the first mapping relationship table; A mapping relationship table is used to store a domain name and a CDN node back source relationship;
  • S103 Synchronize the target domain name and the adjusted target CDN node back source relationship to the cache management server.
  • the back source relationship management server may obtain the target CDN node back source relationship corresponding to the Target domain name. And obtaining, by using the target domain name and the first mapping relationship table stored in the source relationship management server, the source CDN node return source relationship corresponding to the target domain name.
  • the first mapping relationship table is used to store the domain name and the CDN node back source relationship.
  • the back source relationship management server may adjust the return relationship of the target CDN node according to the obtained adjustment information for the source CDN node return source relationship, and obtain the adjusted target CDN node return source relationship.
  • the adjusted target CDN node return source relationship can be synchronized to the cache management server.
  • the technician does not need to manually modify the CDN node return source relationship corresponding to each domain name stored in the cache management server, thereby reducing the maintenance cost and error rate of the CDN node return source relationship, and improving the maintenance efficiency.
  • the source relationship management server can simultaneously obtain the target domain name corresponding to the target CDN node return source relationship to be adjusted, and the adjustment information for the target CDN node return source relationship. In this way, the speed of obtaining the target domain name and adjusting the information can be improved.
  • the source relation management server can obtain the target domain name at the same time: the domain name a, and the source CDN node corresponding to the domain name a: CDN 1 node ⁇ CDN 2 node ⁇ CDN 3 node ⁇ the source station of the domain name a, And the adjustment information of the target CDN node return source relationship: the CDN 2 node is modified to the CDN 5 node.
  • the adjustment information is only an example, and is of course not limited thereto.
  • the back source relationship management server may first use the first mapping relationship table to determine the target CDN node corresponding to the target domain name. relationship. Then, the information determined by the target CDN node back source relationship is sent to the user terminal, so that the user terminal obtains a topology map corresponding to the source CDN node back source relationship based on the information, and displays the topology map to the user. Then, the user terminal generates adjustment information for the target structure topology map based on the adjustment of the topology map by the user, and sends the adjustment information to the return source relationship management server.
  • the return source relationship management server is enabled to obtain the adjustment information, and the adjustment information is used as adjustment information of the target CDN node return source relationship.
  • the target CDN node return relationship can be displayed to the user in an intuitive manner, so that the user can view and adjust the source CDN node return relationship.
  • the adjustment of the level of the CDN node in the return source relationship can also be implemented in the process of adjusting the source-back relationship of the target CDN node.
  • the information determined by the source CDN node return source relationship may be: the target CDN node return source relationship itself.
  • the user terminal may generate a topology map based on the target CDN node return source relationship, and then display the topology map to the user.
  • the information determined by the target CDN node return source relationship may also be: a topology map generated based on the target CDN node return source relationship, which is reasonable.
  • the target CDN node return source relationship may be stored by using a topology, and any service that depends on the topology may obtain the topology by calling an interface of the topology.
  • the user may adjust the topology map to: add, delete, and modify the CDN node in the topology map, and modify one or more operations on the connection relationship between the CDN nodes. This is all reasonable.
  • the adjustment information for the target structure topology map generated by the user terminal may include at least one of the following information: adding corresponding operation information to the CDN node in the topology map; and deleting the CDN node in the topology map The corresponding operation information; the operation information corresponding to the modification of the CDN node in the topology map; and the operation information corresponding to the modification of the connection relationship between the CDN nodes.
  • the topology diagram shown in FIG. 2 is a topology diagram generated based on the source CDN node return source relationship corresponding to the target domain name k.
  • the user terminal can display the topology map, and the user can adjust the topology map by operating the user terminal, for example, removing the connection of CDN A to CDN E.
  • the user terminal generates adjustment information for the topology map according to the operation, and sends the adjustment information to the source relationship adjustment server. Therefore, the source relationship management server can adjust the source CDN node corresponding to the target domain name k according to the adjustment information.
  • the source relationship management server may send the adjusted source CDN node back source relationship to the cache management server, so that the user does not need to manually adjust the source CDN node corresponding to the target domain name k in the cache server. Save time and effort and avoid mistakes. Moreover, it can be avoided that when there are multiple cache management servers that need to modify the source CDN node return source relationship, the technician manually modifies the time difference of the source CDN node return source relationship in each cache management server, thereby causing the time difference corresponding Data is heterogeneous in each cache management service during the time period.
  • the source relationship management server may synchronize the adjusted source CDN node return source relationship to all cache management servers in the source relationship management system.
  • the adjusted source CDN node return source relationship may be synchronized to the cache management server corresponding to the target domain name K in the return source relationship management system. This is reasonable.
  • determining, by using the first mapping relationship table, the source CDN node corresponding to the target domain name to return the source relationship operation may include: determining whether the target domain name can be found in the first mapping relationship table. If yes, look up the source CDN node return source relationship corresponding to the target domain name in the first mapping relationship table. If the target domain name cannot be found in the first mapping relationship table, the default CDN node return relationship may be used as the target CDN node return source relationship corresponding to the target domain name.
  • the default source relationship of the CDN node can be set by a person skilled in the art according to a specific situation, and is not described in detail herein.
  • the back source relationship management method is applied to: a cache management server in a CDN (Content Delivery Network) central control system.
  • the back source relationship management system also includes a cache management server.
  • the source relationship management server is configured to: store a CDN node return source relationship cached in the cache management server in the source relationship management system, and may cache the CDN in the cache management server in the source relationship management system.
  • the node back source relationship is adjusted, and the adjusted CDN node return source relationship can be synchronized to the cache management server.
  • the cache management server is configured to: manage the mapping relationship between the domain name cached by the cache management server and the source relationship of the CDN node, and based on the mapping relationship between the domain name cached by the cache management server and the source relationship of the CDN node, Manage the content cached by the CDN node. For example, when the cache management server sends the server to the source configuration file, the cache server sends a source configuration file to the CDN node corresponding to the domain name based on the mapping relationship between the cached domain name and the CDN node's source relationship. The management of the content cached by the CDN node is thereby implemented by the source configuration file.
  • the method may include the following steps:
  • S301 Receive a target domain name sent by the source relationship management server, and adjust the source CDN node return relationship;
  • S302 Update the source relationship of the CDN node corresponding to the target domain name stored in the cache management server by using the adjusted target CDN node return source relationship, and obtain a new CDN node return source relationship.
  • the cache management server may receive the target domain name sent by the source relationship management server and adjust the target domain name.
  • the target CDN node is back to the source relationship.
  • the cache management server may find the target CDN node return source relationship corresponding to the target domain name stored in the cache management server according to the target domain name, and use the adjusted target CDN node return source relationship to the target CDN node.
  • the source relationship is updated to obtain the source relationship of the new CDN node corresponding to the target domain name. In this way, the technician does not need to manually modify the CDN node return source relationship corresponding to each domain name stored in the cache management server, thereby reducing the maintenance cost and error rate of the CDN node return source relationship, and improving the maintenance efficiency.
  • the cache management server may include: a source configuration file delivery server and/or a content refresh server. Of course, it is not limited to this.
  • the cache management server may also perform the following operations: generating a return source configuration of each CDN node in the source relationship of the new CDN node based on the source relationship of the new CDN node.
  • the file is sent to the corresponding CDN node, so that the CDN node returns the source according to the received source configuration file.
  • the cache management server may further perform an operation of: generating a refresh instruction of each CDN node in a new CDN node return source relationship based on a new CDN node return source relationship, and generating a refresh instruction
  • the CDN node is sent to the corresponding CDN node, so that the CDN node refreshes the content cached by itself according to the received refresh command.
  • the implementation of the present application further provides a source relationship management apparatus.
  • the source-back relationship management device provided in the embodiment of the present application is applied to a source-back relationship management server in a source-back relationship management system, where the source-back relationship management system further includes a cache management server, and the cache management server is configured to cache the domain name and The mapping relationship between the CDN nodes and the source relationship, the device may include:
  • the obtaining unit 401 is configured to obtain a target domain name corresponding to the target CDN node return source relationship to be adjusted, and adjustment information for the target CDN node return source relationship;
  • the adjusting unit 402 is configured to adjust the return relationship of the target CDN node by using the adjustment information, to obtain the adjusted source CDN node return source relationship, wherein the target CDN node return source relationship is: determined based on the target domain name and the first mapping relationship table.
  • the first mapping relationship table is used to store the domain name and the CDN node return source relationship;
  • the synchronization unit 403 is configured to synchronize the target domain name and the adjusted target CDN node back source relationship to the cache management server.
  • the back source relationship management server may obtain the target CDN node back source relationship corresponding to the Target domain name. And obtaining, by using the target domain name and the first mapping relationship table stored in the source relationship management server, the source CDN node return source relationship corresponding to the target domain name.
  • the first mapping relationship table is used to store the domain name and the CDN node back source relationship.
  • the back source relationship management server may adjust the return relationship of the target CDN node according to the obtained adjustment information for the source CDN node return source relationship, and obtain the adjusted target CDN node return source relationship.
  • the adjusted target CDN node return source relationship can be synchronized to the cache management server.
  • the technician does not need to manually modify the CDN node return source relationship corresponding to each domain name stored in the cache management server, thereby reducing the maintenance cost and error rate of the CDN node return source relationship, and improving the maintenance efficiency.
  • the obtaining unit 401 may include:
  • a first receiving subunit configured to receive a target domain name corresponding to a source CDN node back source relationship to be adjusted
  • Determining a subunit configured to determine, according to the first mapping relationship table, a source CDN node return source relationship corresponding to the target domain name;
  • a sending subunit configured to send information determined by the target CDN node back source relationship to the user terminal, so that the user terminal obtains and displays a topology map corresponding to the source CDN node return source relationship based on the information;
  • the second receiving subunit is configured to receive the adjustment information for the topology map sent by the user terminal, as the adjustment information for the source CDN node return source relationship.
  • the adjustment information for the topology map may include at least one of the following information:
  • the operation information corresponding to the modification of the connection relationship between the CDN nodes is performed.
  • determining the subunit includes:
  • the determining module is configured to determine whether the target domain name can be found in the first mapping relationship table after obtaining the target domain name corresponding to the target CDN node return source relationship to be adjusted, and the adjustment information for the target CDN node return source relationship;
  • the search module is configured to: when the target domain name can be found in the first mapping table, search for a target CDN node return source relationship corresponding to the target domain name in the first mapping relationship table.
  • the apparatus may further include:
  • the determining module is configured to: when the target domain name cannot be found in the first mapping relationship table, the default CDN node return relationship is used as the target CDN node return source relationship corresponding to the target domain name.
  • the description is relatively simple, and the relevant part refers to the part of the method embodiment provided from the perspective of the source management server. instruction of.
  • the implementation of the present application further provides a source relationship management apparatus.
  • the source-back relationship management apparatus provided in the embodiment of the present application is applied to a cache management server in a source-resource relationship management system, and the source-resource relationship management system further includes a source-back relationship management server, and the device may include:
  • the receiving unit 501 is configured to receive, by the source relation management server, the target domain name and the adjusted target CDN node return source relationship;
  • the updating unit 502 is configured to update the CDN node return source relationship corresponding to the target domain name stored in the cache management server by using the adjusted target CDN node return source relationship to obtain a new CDN node return source relationship.
  • the cache management server may receive the target domain name sent by the source relationship management server and adjust the target domain name.
  • the target CDN node is back to the source relationship.
  • the cache management server may find the target CDN node return source relationship corresponding to the target domain name stored in the cache management server according to the target domain name, and use the adjusted target CDN node return source relationship to the target CDN node.
  • the source relationship is updated to obtain the source relationship of the new CDN node corresponding to the target domain name. In this way, the technician does not need to manually modify the CDN node return source relationship corresponding to each domain name stored in the cache management server, thereby reducing the maintenance cost and error rate of the CDN node return source relationship, and improving the maintenance efficiency.
  • the cache management server includes: a source configuration file delivery server and/or a content refresh server; the device may further include:
  • the first generating unit is configured to: when the cache management server delivers the server as the source configuration file, generate a return source configuration file of each CDN node in the new CDN node return source relationship based on the new CDN node return source relationship, and generate The source configuration file is sent to the corresponding CDN node;
  • the second generating unit is configured to: when the cache management server is the content refreshing server, generate a refresh command of each CDN node in the source relationship of the new CDN node based on the source relationship of the new CDN node, and send the generated refresh command to the Corresponding CDN node.
  • the apparatus embodiment is substantially similar to the method embodiment provided from the perspective of the cache management server, the description is relatively simple, and the relevant portion refers to the description of the part of the method embodiment provided from the perspective of the cache management server.
  • the implementation of the present application further provides a source relationship management server.
  • the back source relationship management server provided by the embodiment of the present application is a server in the source relationship management system, and the source relationship management system further includes a cache management server, and the cache management server is configured to cache the domain name and the CDN node return source relationship.
  • the mapping relationship between the source management server includes a processor 601, a communication interface 602, a memory 603, and a communication bus 604, wherein the processor 601, the communication interface 602, and the memory 603 complete communication with each other through the communication bus 604;
  • the processor 601 when configured to execute the program stored on the memory 603, implements the method steps of any of the embodiments of the source relationship management method provided from the perspective of the source relationship management server.
  • the back source relationship management server may obtain the target CDN node back source relationship corresponding to the Target domain name. And obtaining, by using the target domain name and the first mapping relationship table stored in the source relationship management server, the source CDN node return source relationship corresponding to the target domain name.
  • the first mapping relationship table is used to store the domain name and the CDN node back source relationship.
  • the back source relationship management server may adjust the return relationship of the target CDN node according to the obtained adjustment information for the source CDN node return source relationship, and obtain the adjusted target CDN node return source relationship.
  • the adjusted target CDN node return source relationship can be synchronized to the cache management server.
  • the technician does not need to manually modify the CDN node return source relationship corresponding to each domain name stored in the cache management server, thereby reducing the maintenance cost and error rate of the CDN node return source relationship, and improving the maintenance efficiency.
  • the implementation of the present application further provides a cache management server.
  • the cache management server provided by the embodiment of the present application is a server in the source relationship management system, and the source relationship management system further includes a source relationship management server.
  • the cache management server includes a processor 701, a communication interface 702, and a memory 703. And a communication bus 704, wherein the processor 701, the communication interface 702, and the memory 703 complete communication with each other through the communication bus 704;
  • the processor 701 when configured to execute the program stored on the memory 703, implements the method steps of any of the embodiments of the source relationship management method provided from the perspective of the cache management server.
  • the cache management server may receive the target domain name sent by the source relationship management server and adjust the target domain name.
  • the target CDN node is back to the source relationship.
  • the cache management server may find the target CDN node return source relationship corresponding to the target domain name stored in the cache management server according to the target domain name, and use the adjusted target CDN node return source relationship to the target CDN node.
  • the source relationship is updated to obtain the source relationship of the new CDN node corresponding to the target domain name. In this way, the technician does not need to manually modify the CDN node return source relationship corresponding to each domain name stored in the cache management server, thereby reducing the maintenance cost and error rate of the CDN node return source relationship, and improving the maintenance efficiency.
  • the communication bus mentioned by the above electronic device may be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus.
  • PCI Peripheral Component Interconnect
  • EISA Extended Industry Standard Architecture
  • the communication bus can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only one thick line is shown in the figure, but it does not mean that there is only one bus or one type of bus.
  • the communication interface is used for communication between the above electronic device and other devices.
  • the memory may include a random access memory (RAM), and may also include a non-volatile memory (NVM), such as at least one disk storage.
  • RAM random access memory
  • NVM non-volatile memory
  • the memory may also be at least one storage device located away from the aforementioned processor.
  • the above processor may be a general-purpose processor, including a central processing unit (CPU), a network processor (NP), etc.; or may be a digital signal processing (DSP), dedicated integration.
  • CPU central processing unit
  • NP network processor
  • DSP digital signal processing
  • ASIC Application Specific Integrated Circuit
  • FPGA Field-Programmable Gate Array
  • the embodiment of the present application further provides a source relationship management system.
  • the source relationship management system 800 may include: a source relationship management server 801. And a cache management server 802;
  • the source relationship management server 801 is set to:
  • the cache management server 802 is set to:
  • the adjusted source CDN node return source relationship is used to update the CDN node return source relationship corresponding to the target domain name stored in the cache management server, and the new CDN node return source relationship is obtained.
  • the return source relationship management server 801 can edit the topology, that is, can edit the CDN node return source relationship stored by itself, obtain the adjusted CDN node return source relationship, and can adjust the adjusted The CDN node returns the source relationship for storage. Moreover, after the adjusted CDN node returns the source relationship, the adjusted CDN node return source relationship may be actively sent to the cache management server 802. Of course, after receiving the acquisition request of the cache management server 802, the adjusted CDN node return source relationship may be sent to the cache management server 802, which is reasonable.
  • the cache management server 802 may generate a refresh command or a source configuration file based on the adjusted CDN node return source relationship, and then send the refresh command to the corresponding CDN node. Or return to the source configuration file.
  • the back source relationship management server may obtain the target domain name corresponding to the target CDN node return source relationship. And obtaining the source CDN node return source relationship corresponding to the target domain name by using the target domain name and the first mapping relationship table stored in the source relationship management server.
  • the first mapping relationship table is used to store the domain name and the CDN node back source relationship.
  • the back source relationship management server may adjust the return relationship of the target CDN node according to the obtained adjustment information for the source CDN node return source relationship, and obtain the adjusted target CDN node return source relationship.
  • the adjusted target CDN node return source relationship can be synchronized to the cache management server.
  • the cache management server may receive the target domain name sent by the source relationship management server and the adjusted target CDN node return source relationship. Then, the cache management server may find the target CDN node return source relationship corresponding to the target domain name stored in the cache management server according to the target domain name, and use the adjusted target CDN node return source relationship to the target CDN node. The source relationship is updated to obtain the source relationship of the new CDN node corresponding to the target domain name. In this way, the technician does not need to manually modify the CDN node return source relationship corresponding to each domain name stored in the cache management server, thereby reducing the maintenance cost and error rate of the CDN node return source relationship, and improving the maintenance efficiency.
  • the cache management server may include: a source configuration file delivery server and/or a content refresh server;
  • the source configuration file delivery server is also set to:
  • the content refresh server is further configured to generate a refresh command of each CDN node in the new CDN node return source relationship based on the new CDN node return source relationship, and deliver the generated refresh command to the refresh command. Corresponding CDN node.
  • the source-back relationship management server is further configured to obtain, by using the following manner, a target domain name corresponding to the target CDN node return source relationship to be adjusted, and adjustment information for the target CDN node return source relationship:
  • the adjustment information for the topology map sent by the user terminal is received as the adjustment information for the source relationship of the target CDN node.
  • the adjustment information for the topology map may include at least one of the following information:
  • the operation information corresponding to the modification of the connection relationship between the CDN nodes is performed.
  • the source-back relationship management server is further configured to determine, according to the first mapping relationship table, a source CDN node return source relationship corresponding to the target domain name by:
  • the source CDN node corresponding to the target domain name in the first mapping relationship table is searched for the source relationship.
  • the source relationship management server may also be configured to:
  • the default CDN node is returned to the source relationship as the target CDN node corresponding to the target domain name.
  • the implementation of the present application further provides a storage medium.
  • the storage medium is: a storage medium in the source relation management server, the source relationship management server is a server in the source relationship management system, and the source relationship management system further includes a cache management server, and the cache management server is configured to cache the domain name and the CDN.
  • the mapping relationship between the node and the source relationship; the computer program is stored in the storage medium, and the computer program is executed by the processor: the method step of any embodiment of the source relationship management method provided from the perspective of the source management server .
  • the back source relationship management server may obtain the target CDN node back source relationship corresponding to the Target domain name. And obtaining, by using the target domain name and the first mapping relationship table stored in the source relationship management server, the source CDN node return source relationship corresponding to the target domain name.
  • the first mapping relationship table is used to store the domain name and the CDN node back source relationship.
  • the back source relationship management server may adjust the return relationship of the target CDN node according to the obtained adjustment information for the source CDN node return source relationship, and obtain the adjusted target CDN node return source relationship.
  • the adjusted target CDN node return source relationship can be synchronized to the cache management server.
  • the technician does not need to manually modify the CDN node return source relationship corresponding to each domain name stored in the cache management server, thereby reducing the maintenance cost and error rate of the CDN node return source relationship, and improving the maintenance efficiency.
  • the implementation of the present application further provides a storage medium, which is a storage medium in the cache management server, and the cache management server is a source relationship.
  • the server in the management system, the return source relationship management system further includes a back source relationship management server; the storage medium stores a computer program, and when the computer program is executed by the processor, the above-mentioned source relationship is provided from the perspective of the cache management server.
  • the cache management server may receive the target domain name sent by the source relationship management server and adjust the target domain name.
  • the target CDN node is back to the source relationship.
  • the cache management server may find the target CDN node return source relationship corresponding to the target domain name stored in the cache management server according to the target domain name, and use the adjusted target CDN node return source relationship to the target CDN node.
  • the source relationship is updated to obtain the source relationship of the new CDN node corresponding to the target domain name. In this way, the technician does not need to manually modify the CDN node return source relationship corresponding to each domain name stored in the cache management server, thereby reducing the maintenance cost and error rate of the CDN node return source relationship, and improving the maintenance efficiency.
  • the implementation of the present application further provides a computer program product.
  • the computer program product is for implementing, at runtime, the method steps of any of the above-described methods of returning source relationship management methods provided from the perspective of a source management server.
  • the source relationship management server can obtain The target CDN node corresponds to the target domain name corresponding to the source relationship. And obtaining, by using the target domain name and the first mapping relationship table stored in the source relationship management server, the source CDN node return source relationship corresponding to the target domain name.
  • the first mapping relationship table is used to store the domain name and the CDN node back source relationship.
  • the back source relationship management server may adjust the return relationship of the target CDN node according to the obtained adjustment information for the source CDN node return source relationship, and obtain the adjusted target CDN node return source relationship.
  • the adjusted target CDN node return source relationship can be synchronized to the cache management server.
  • the technician does not need to manually modify the CDN node return source relationship corresponding to each domain name stored in the cache management server, thereby reducing the maintenance cost and error rate of the CDN node return source relationship, and improving the maintenance efficiency.
  • the implementation of the present application further provides a computer program product.
  • the computer program product is for implementing, at runtime, the method steps of any of the above-described methods of returning source management methods provided from the perspective of a cache management server.
  • the cache management server may receive the source relationship management server.
  • the target domain name sent and the adjusted target CDN node return source relationship Then, the cache management server may find the target CDN node return source relationship corresponding to the target domain name stored in the cache management server according to the target domain name, and use the adjusted target CDN node return source relationship to the target CDN node.
  • the source relationship is updated to obtain the source relationship of the new CDN node corresponding to the target domain name. In this way, the technician does not need to manually modify the CDN node return source relationship corresponding to each domain name stored in the cache management server, thereby reducing the maintenance cost and error rate of the CDN node return source relationship, and improving the maintenance efficiency.
  • the back source relationship management server may obtain the target corresponding to the target CDN node return source relationship.
  • a domain name, and the target mapping domain is stored in the first mapping relationship table, and the target CDN node corresponding to the target domain name is found, and then the source relationship management server can obtain the The adjustment information of the target CDN node return source relationship is adjusted, and the adjusted source CDN node return source relationship is adjusted to obtain the adjusted target CDN node return source relationship.
  • the adjusted target CDN node return source relationship can be synchronized to the cache management server. In this way, the technician does not need to manually modify the CDN node return source relationship corresponding to each domain name stored in the cache management server, thereby reducing the maintenance cost and error rate of the CDN node return source relationship, and improving the maintenance efficiency.

Abstract

本申请实施例提供了回源关系管理系统、方法、装置、服务器及存储介质。回源关系管理系统包括：回源关系管理服务器，设置为获得待调整的目标CDN节点回源关系对应的目标域名及调整信息；利用调整信息对目标CDN节点回源关系进行调整，得到调整后的目标CDN节点回源关系；将目标域名和调整后的目标CDN节点回源关系同步至缓存管理服务器；缓存管理服务器，设置为接收目标域名和调整后的目标CDN节点回源关系；利用调整后的目标CDN节点回源关系更新目标域名对应的CDN节点回源关系，得到新CDN节点回源关系。这样能够对各个域名对应的CDN节点回源关系进行统一管理，降低CDN节点回源关系的维护成本和出错率，并提高维护效率。

Description

一种回源关系管理系统、方法、装置、服务器及存储介质
本申请要求于2018年1月26日提交中国专利局、申请号为201810078366.9、发明名称为“一种回源关系管理系统、方法、装置、服务器及存储介质”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及网络设备管理技术领域，特别是涉及一种回源关系管理系统、方法、装置、服务器及存储介质。
背景技术
目前，网络系统中存在大量的CDN(Content Delivery Network，内容分发网络)节点。其中，由于CDN节点设置在近用户端，并且可以缓存从源站回源得到的内容。其中，CDN节点缓存的每一内容均对应一源站，一内容对应的源站可以理解为：这一内容的原始存储位置。因而，当用户访问一内容时，可以直接从其附近的CDN节点获得这一内容，而不需要从远处的、存储这一内容的源站获取这一内容，提高了用户获得这一内容的速度。
CDN节点从一源站回源得到一内容时，一般需要依赖回源配置文件实现。其中，上述回源配置文件为：回源配置文件下发服务器下发至CDN节点的文件。且该回源配置文件是基于域名与CDN节点回源关系之间的对应关系生成的。也就是，CDN节点需要从一源站回源得到一内容时，需要在本地存储的回源配置文件中，查找需要进行回源的内容的域名对应的下一跳设备，从而依据查找到的下一跳设备进行回源，得到需要进行回源的内容。另外，当需要刷新CDN节点缓存的内容时，内容刷新服务器也需要根据域名对应的CDN节点回源关系，给CDN节点下发刷新指令，实现内容刷新。
其中，一个域名对应的CDN节点回源关系可以理解为：从一个CDN节点开始回溯到该域名所对应源站点的路径。例如，域名a对应的CDN节点回源关系为：CDN1节点→CDN2节点→CDN3节点→域名a的源站；域名b对应的CDN节点回源关系为：CDN1节点→CDN3节点→CDN4节点→域名b的源站，和CDN1节点→CDN5节点→CDN6节点→域名b的源站。
相关技术中，每当一个域名对应的CDN节点回源关系发生变更时，技术 人员需要手动修改回源配置文件下发服务器和内容刷新服务器等各个缓存管理服务器中存储的、该域名对应的CDN节点回源关系。使得修改工作量较大，费时费力且容易出错。
因此，如何提供一种回源关系管理方案，以能够对各个域名对应的CDN节点回源关系进行统一管理，进而降低CDN节点回源关系的维护成本和出错率，并提高维护效率，成为亟待解决的技术问题。
发明内容
本申请实施例的目的在于提供一种回源关系管理系统、方法、装置、服务器及存储介质，以能够对各个域名对应的CDN节点回源关系进行统一管理，进而降低CDN节点回源关系的维护成本和出错率，并提高维护效率。
第一方面，本申请实施例提供了一种回源关系管理系统，回源关系管理系统包括：回源关系管理服务器和缓存管理服务器；
回源关系管理服务器设置为：
获得待调整的目标CDN节点回源关系对应的目标域名，以及针对目标CDN节点回源关系的调整信息；
利用调整信息对目标CDN节点回源关系进行调整，得到调整后的目标CDN节点回源关系；其中，目标CDN节点回源关系为：基于目标域名以及第一映射关系表确定得到的；第一映射关系表用于对域名与CDN节点回源关系进行对应存储；
将目标域名和调整后的目标CDN节点回源关系同步至缓存管理服务器；
缓存管理服务器设置为：
接收回源关系管理服务器发送的、目标域名和调整后的目标CDN节点回源关系；
利用调整后的目标CDN节点回源关系，对缓存管理服务器中存储的、目标域名对应的CDN节点回源关系进行更新，得到新CDN节点回源关系。
可选地，缓存管理服务器包括：回源配置文件下发服务器和/或内容刷新服务器；
当缓存管理服务器为回源配置文件下发服务器时，回源配置文件下发服务器还设置为：
基于新CDN节点回源关系，生成新CDN节点回源关系中的各个CDN节点的回源配置文件，并将生成的回源配置文件下发至对应的CDN节点；
当缓存管理服务器为内容刷新服务器时，内容刷新服务器还设置为：基于新CDN节点回源关系，生成新CDN节点回源关系中的各个CDN节点的刷新指令，并将生成的刷新指令下发至对应的CDN节点。
可选地，回源关系管理服务器还设置为通过以下方式获得待调整的目标CDN节点回源关系对应的目标域名，以及针对目标CDN节点回源关系的调整信息：
接收待调整的目标CDN节点回源关系对应的目标域名；
基于第一映射关系表，确定目标域名对应的目标CDN节点回源关系；
将由目标CDN节点回源关系确定的信息发送至用户终端，以使用户终端基于信息，获得并展示目标CDN节点回源关系对应的拓扑结构图；
接收用户终端发送的、针对拓扑结构图的调整信息，作为针对目标CDN节点回源关系的调整信息。
可选地，针对拓扑结构图的调整信息可以包括以下至少之一信息：
对拓扑结构图中的CDN节点进行增加对应的操作信息；
对拓扑结构图中的CDN节点进行删除对应的操作信息；
对拓扑结构图中的CDN节点进行修改对应的操作信息；
对CDN节点之间的连接关系进行修改对应的操作信息。
可选地，回源关系管理服务器还设置为基于第一映射关系表，通过以下方式确定目标域名对应的目标CDN节点回源关系：
判断在第一映射关系表中，是否能查找到目标域名；
若在第一映射关系表中能查找到目标域名，查找第一映射关系表中目标域名对应的目标CDN节点回源关系。
可选地，若在第一映射关系表中，不能查找到目标域名，回源关系管理服务器还可以设置为：
将预设CDN节点回源关系，作为目标域名对应的目标CDN节点回源关系。
第二方面，本申请实施例提供了一种回源关系管理方法，应用于回源关系管理系统中的回源关系管理服务器，回源关系管理系统还包括缓存管理服务器，缓存管理服务器用于缓存域名与CDN节点回源关系之间的映射关系，该方法可以包括：
获得待调整的目标CDN节点回源关系对应的目标域名，以及针对目标CDN节点回源关系的调整信息；
利用调整信息对目标CDN节点回源关系进行调整，得到调整后的目标CDN节点回源关系；其中，目标CDN节点回源关系为：基于目标域名以及第一映射关系表确定得到的；第一映射关系表用于对域名与CDN节点回源关系进行对应存储；
将目标域名和调整后的目标CDN节点回源关系同步至缓存管理服务器。
可选地，获得待调整的目标CDN节点回源关系对应的目标域名，以及针对目标CDN节点回源关系的调整信息的步骤，可以包括：
接收待调整的目标CDN节点回源关系对应的目标域名；
基于第一映射关系表，确定目标域名对应的目标CDN节点回源关系；
将由目标CDN节点回源关系确定的信息发送至用户终端，以使用户终端基于信息，获得并展示目标CDN节点回源关系对应的拓扑结构图；
接收用户终端发送的、针对拓扑结构图的调整信息，作为针对目标CDN节点回源关系的调整信息。
可选地，针对拓扑结构图的调整信息，可以包括以下至少之一信息：
对拓扑结构图中的CDN节点进行增加对应的操作信息；
对拓扑结构图中的CDN节点进行删除对应的操作信息；
对拓扑结构图中的CDN节点进行修改对应的操作信息；
对CDN节点之间的连接关系进行修改对应的操作信息。
可选地，该基于所述第一映射关系表，确定所述目标域名对应的目标CDN节点回源关系的步骤，可以包括：
判断在第一映射关系表中，是否能查找到目标域名；
若在所述第一映射关系表中能查找到所述目标域名，查找第一映射关系 表中目标域名对应的目标CDN节点回源关系。
可选地，若在第一映射关系表中，不能查找到目标域名，该方法还可以包括：
将预设CDN节点回源关系，作为目标域名对应的目标CDN节点回源关系。
第三方面，本申请实施例还提供了一种回源关系管理方法，应用于回源关系管理系统中的缓存管理服务器，回源关系管理系统还包括回源关系管理服务器，该方法可以包括：
接收回源关系管理服务器发送的、目标域名和调整后的目标CDN节点回源关系；
利用调整后的目标CDN节点回源关系，对缓存管理服务器中存储的、目标域名对应的CDN节点回源关系进行更新，得到新CDN节点回源关系。
可选地，缓存管理服务器包括：回源配置文件下发服务器和/或内容刷新服务器；该方法还可以包括：
当缓存管理服务器为回源配置文件下发服务器时，基于新CDN节点回源关系，生成新CDN节点回源关系中的各个CDN节点的回源配置文件，并将生成的回源配置文件下发至对应的CDN节点；
当缓存管理服务器为内容刷新服务器时，基于新CDN节点回源关系，生成新CDN节点回源关系中的各个CDN节点的刷新指令，并将生成的刷新指令下发至对应的CDN节点。
第四方面，本申请实施例提供了一种回源关系管理装置，应用于回源关系管理系统中的回源关系管理服务器，回源关系管理系统还包括缓存管理服务器，缓存管理服务器设置为缓存域名与CDN节点回源关系之间的映射关系，该装置可以包括：
获得单元，设置为获得待调整的目标CDN节点回源关系对应的目标域名，以及针对目标CDN节点回源关系的调整信息；
调整单元，设置为利用调整信息对目标CDN节点回源关系进行调整，得到调整后的目标CDN节点回源关系；其中，目标CDN节点回源关系为：基于目标域名以及第一映射关系表确定得到的；第一映射关系表用于对域名与 CDN节点回源关系进行对应存储；
同步单元，设置为将目标域名和调整后的目标CDN节点回源关系同步至缓存管理服务器。
可选地，获得单元可以包括：
第一接收子单元，设置为接收待调整的目标CDN节点回源关系对应的目标域名；
确定子单元，设置为基于第一映射关系表，确定目标域名对应的目标CDN节点回源关系；
发送子单元，设置为将由目标CDN节点回源关系确定的信息发送至用户终端，以使用户终端基于信息，获得并展示目标CDN节点回源关系对应的拓扑结构图；
第二接收子单元，设置为接收用户终端发送的、针对拓扑结构图的调整信息，作为针对目标CDN节点回源关系的调整信息。
可选地，针对拓扑结构图的调整信息，可以包括以下至少之一信息：
对拓扑结构图中的CDN节点进行增加对应的操作信息；
对拓扑结构图中的CDN节点进行删除对应的操作信息；
对拓扑结构图中的CDN节点进行修改对应的操作信息；
对CDN节点之间的连接关系进行修改对应的操作信息。
可选地，在本申请实施例中，确定子单元包括：
判断模块，设置为在获得待调整的目标CDN节点回源关系对应的目标域名，以及针对目标CDN节点回源关系的调整信息之后，判断在第一映射关系表中，是否能查找到目标域名；
查找模块，设置为当在第一映射表中能查找到目标域名时，查找第一映射关系表中目标域名对应的目标CDN节点回源关系。
可选地，在本申请实施例中，装置还可以包括：
确定模块，设置为在第一映射关系表中不能查找到目标域名时，将预设CDN节点回源关系，作为目标域名对应的目标CDN节点回源关系。
第五方面，本申请实施例还提供了一种回源关系管理装置，应用于回源关系管理系统中的缓存管理服务器，回源关系管理系统还包括回源关系管理 服务器，该装置可以包括：
接收单元，设置为接收回源关系管理服务器发送的、目标域名和调整后的目标CDN节点回源关系；
更新单元，设置为利用调整后的目标CDN节点回源关系，对缓存管理服务器中存储的、目标域名对应的CDN节点回源关系进行更新，得到新CDN节点回源关系。
可选地，缓存管理服务器包括：回源配置文件下发服务器和/或内容刷新服务器；该装置还可以包括：
第一生成单元，设置为当缓存管理服务器为回源配置文件下发服务器时，基于新CDN节点回源关系，生成新CDN节点回源关系中的各个CDN节点的回源配置文件，并将生成的回源配置文件下发至对应的CDN节点；
第二生成单元，设置为当缓存管理服务器为内容刷新服务器时，基于新CDN节点回源关系，生成新CDN节点回源关系中的各个CDN节点的刷新指令，并将生成的刷新指令下发至对应的CDN节点。
第六方面，本申请实施例还提供了一种回源关系管理服务器，回源关系管理服务器为回源关系管理系统中的服务器，回源关系管理系统还包括缓存管理服务器，缓存管理服务器设置为缓存域名与CDN节点回源关系之间的映射关系；回源关系管理服务器包括处理器、通信接口、存储器和通信总线，其中，处理器，通信接口，存储器通过通信总线完成相互间的通信；
存储器，设置为存放计算机程序；
处理器，设置为执行存储器上所存放的程序时，实现第二方面任一项方法实施例提供的方法步骤。
第七方面，本申请实施例还提供了一种缓存管理服务器，缓存管理服务器为回源关系管理系统中的服务器，回源关系管理系统还包括回源关系管理服务器；缓存管理服务器包括处理器、通信接口、存储器和通信总线，其中，处理器，通信接口，存储器通过通信总线完成相互间的通信；
存储器，设置为存放计算机程序；
处理器，设置为执行存储器上所存放的程序时，实现第三方面任一项方法实施例提供的方法步骤。
第八方面，本申请实施例还提供了一种存储介质，该存储介质为：回源关系管理服务器中的存储介质，回源关系管理服务器为回源关系管理系统中的服务器，回源关系管理系统还包括缓存管理服务器，缓存管理服务器设置为缓存域名与CDN节点回源关系之间的映射关系；存储介质内存储有计算机程序，计算机程序被处理器执行时实现第二方面任一项方法实施例提供的方法步骤。其中，该存储介质为计算机可读存储介质。
第九方面，本申请实施例还提供了一种存储介质，该存储介质为：缓存管理服务器中的存储介质，缓存管理服务器为回源关系管理系统中的服务器，回源关系管理系统还包括回源关系管理服务器；存储介质内存储有计算机程序，计算机程序被处理器执行时实现第三方面任一项方法实施例提供的方法步骤。其中，该存储介质为计算机可读存储介质。
第十方面，本申请实施例还提供了一种计算机程序产品，该计算机程序产品用于在运行时实现第二方面任一项方法实施例提供的方法步骤。
第十一方面，本申请实施例还提供了一种计算机程序产品，该计算机程序产品用于在运行时实现第三方面任一项方法实施例提供的方法步骤。
在本申请实施例中，当需要对该回源关系服务器中存储的目标CDN节点回源关系进行调整时，该回源关系管理服务器可以获得该目标CDN节点回源关系对应的目标域名。并通过该目标域名与该回源关系管理服务器中存储的第一映射关系表，找到该目标域名对应的目标CDN节点回源关系。其中，该第一映射关系表用于对域名与CDN节点回源关系进行对应存储。然后，该回源关系管理服务器可以根据获得的、针对该目标CDN节点回源关系的调整信息，对该目标CDN节点回源关系进行调整，得到调整后的目标CDN节点回源关系。进而，可以将该调整后的目标CDN节点回源关系同步至缓存管理服务器中。这样，不需要技术人员通过手动修改的方式来修改缓存管理服务器中存储的各个域名对应的CDN节点回源关系，降低了CDN节点回源关系的维护成本和出错率，并且提高了维护效率。
附图说明
为了更清楚地说明本申请实施例和现有技术的技术方案，下面对实施例和现有技术中所需要使用的附图作简单地介绍，显而易见地，下面描述中的 附图仅仅是本申请的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其他的附图。
图1为本申请实施例提供的一种回源关系管理方法的流程图；
图2为本申请实施例提供的一种拓扑结构图；
图3为本申请实施例提供的另一种回源关系管理方法的流程图；
图4为本申请实施例提供的一种回源关系管理装置的结构示意图；
图5为本申请实施例提供的另一种回源关系管理装置的结构示意图；
图6为本申请实施例提供的一种回源关系管理服务器的结构示意图；
图7为本申请实施例提供的一种缓存管理服务器的结构示意图；
图8为本申请实施例提供的一种回源关系管理系统的示意图。
具体实施方式
为使本申请的目的、技术方案、及优点更加清楚明白，以下参照附图并举实施例，对本申请进一步详细说明。显然，所描述的实施例仅仅是本申请一部分实施例，而不是全部的实施例。基于本申请中的实施例，本领域普通技术人员在没有作出创造性劳动前提下所获得的所有其他实施例，都属于本申请保护的范围。
为了解决现有技术中存在的问题，本申请实施例提供了一种回源关系管理系统、方法、装置、服务器及存储介质。
下面首先从回源关系管理服务器的角度，对本申请实施提供的回源关系管理方法进行说明。
在本申请实施例中，该回源关系管理方法应用于：回源关系管理系统中的回源关系管理服务器。该回源关系管理系统还包括缓存管理服务器。其中，回源关系管理系统也可以称为CDN(Content Delivery Network，内容分发网络)中心控制系统。
其中，该回源关系管理系统中的缓存管理服务器的数量可以是一个或者多个，这都是合理的。其中，每个缓存管理服务器设置为：缓存域名与CDN节点回源关系之间的映射关系，并基于该缓存管理服务器缓存的域名与CDN节点回源关系之间的映射关系，对CDN节点所缓存的内容进行管理。
例如，当该缓存管理服务器为回源配置文件下发服务器时，该缓存服务器基于缓存的域名与CDN节点回源关系之间的映射关系，给该域名对应的CDN节点下发回源配置文件，从而通过该回源配置文件实现对CDN节点所缓存的内容的管理。
该回源关系管理服务器中可以存储有：该回源关系管理系统中的缓存管理服务器中缓存的CDN节点回源关系。并可以对该回源关系管理系统中的缓存管理服务器中缓存的CDN节点回源关系进行统一管理，管理方式具体可参见图1所示的方法步骤。
参见图1，该方法可以包括如下步骤：
S101：获得待调整的目标CDN节点回源关系对应的目标域名，以及针对目标CDN节点回源关系的调整信息；
S102：利用调整信息对目标CDN节点回源关系进行调整，得到调整后的目标CDN节点回源关系；其中，目标CDN节点回源关系为：基于目标域名以及第一映射关系表确定得到的；第一映射关系表用于对域名与CDN节点回源关系进行对应存储；
S103：将目标域名和调整后的目标CDN节点回源关系同步至缓存管理服务器。
可以理解的是，在本申请实施例中，当需要对该回源关系服务器中存储的目标CDN节点回源关系进行调整时，该回源关系管理服务器可以获得该目标CDN节点回源关系对应的目标域名。并通过该目标域名与该回源关系管理服务器中存储的第一映射关系表，找到该目标域名对应的目标CDN节点回源关系。其中，该第一映射关系表用于对域名与CDN节点回源关系进行对应存储。然后，该回源关系管理服务器可以根据获得的、针对该目标CDN节点回源关系的调整信息，对该目标CDN节点回源关系进行调整，得到调整后的目标CDN节点回源关系。进而，可以将该调整后的目标CDN节点回源关系同步至缓存管理服务器中。这样，不需要技术人员通过手动修改的方式来修改缓存管理服务器中存储的各个域名对应的CDN节点回源关系，降低了CDN节点回源关系的维护成本和出错率，并且提高了维护效率。
可以理解的是，在一种实现方式中，回源关系管理服务器可以同时获得待调整的目标CDN节点回源关系对应的目标域名，以及针对该目标CDN节点回源关系的调整信息。这样，可以提高获取目标域名和调整信息的速度。
举例而言，回源关系管理服务器可以同时获得目标域名：域名a，以及针对该域名a对应的目标CDN节点回源关系：CDN 1节点→CDN 2节点→CDN 3节点→域名a的源站，以及该目标CDN节点回源关系的调整信息：将CDN 2节点修改为CDN 5节点。其中，该调整信息仅为示例，当然并不局限于此。
在另一种实现方式中，回源关系管理服务器也可以在获得待调整的目标CDN节点回源关系对应的目标域名之后，先利用第一映射关系表，确定目标域名对应的目标CDN节点回源关系。然后，将由该目标CDN节点回源关系确定的信息发送至用户终端，使得用户终端基于该信息，获得该目标CDN节点回源关系对应的拓扑结构图，并将拓扑结构图展示给用户。然后，用户终端基于用户对该拓扑结构图的调整，生成针对该目标结构拓扑图的调整信息，并将该调整信息发送给该回源关系管理服务器。从而，使得回源关系管理服务器能够获得该调整信息，并将该调整信息作为该目标CDN节点回源关系的调整信息。这样，可以很直观的将目标CDN节点回源关系展示给用户，便于用户对该目标CDN节点回源关系进行查看与调整。
本领域技术人员可以理解的是，在对目标CDN节点回源关系进行调整的过程中，也可以实现对该回源关系中的CDN节点的层级进行调整。
其中，该由目标CDN节点回源关系确定的信息可以为：目标CDN节点回源关系本身。在该种情况下，用户终端可以基于该目标CDN节点回源关系生成拓扑结构图，进而给用户显示该拓扑结构图。当然，该由目标CDN节点回源关系确定的信息也可以为：基于该目标CDN节点回源关系生成的拓扑结构图，这都是合理的。另外，该目标CDN节点回源关系可以是利用拓扑结构进行存储的，并且依赖这个拓扑结构的任一服务均可以通过调用该拓扑结构的接口来获得该拓扑结构。
并且，用户对该拓扑结构图的调整可以为：对所述拓扑结构图中的CDN 节点进行增加、删除和修改，以及对CDN节点之间的连接关系进行修改等操作中的一项或多项，这都是合理的。
相应地，用户终端生成的针对该目标结构拓扑图的调整信息，可以包括以下至少之一信息：对拓扑结构图中的CDN节点进行增加对应的操作信息；对拓扑结构图中的CDN节点进行删除对应的操作信息；对拓扑结构图中的CDN节点进行修改对应的操作信息；对CDN节点之间的连接关系进行修改对应的操作信息。
参见图2，假设图2所示的拓扑结构图为：基于目标域名k对应的目标CDN节点回源关系生成的拓扑结构图。那么，用户终端可以显示该拓扑结构图，且用户可以通过操作该用户终端来对该拓扑结构图进行调整，例如，将CDN A至CDN E的连线去掉。这样，用户终端会根据该操作，生成针对该拓扑结构图的调整信息，并将该调整信息发送给回源关系调整服务器。从而该回源关系管理服务器可以根据该调整信息，对目标域名k对应的目标CDN节点回源关系进行调整。进而，该回源关系管理服务器可以将调整得到的目标CDN节点回源关系发送给缓存管理服务器，这样，不需要用户手动对缓存服务器中该目标域名k对应的目标CDN节点回源关系进行调整，省时省力并且避免了出错。而且，可以避免当需要对目标CDN节点回源关系进行修改的缓存管理服务器存在多个时，技术人员通过手动方式修改各个缓存管理服务器中的目标CDN节点回源关系存在时差，从而导致在时差对应的时间段内各个缓存管理服务中的数据异构。
其中，该回源关系管理服务器可以将该调整得到的目标CDN节点回源关系，同步至该回源关系管理系统中的所有缓存管理服务器。当然，也可以根据预存的标域名和缓存管理服务器的映射关系，将该调整得到的目标CDN节点回源关系，同步至该回源关系管理系统中的、该目标域名K对应的缓存管理服务器，这是合理的。
另外，回源关系管理服务器所执行的利用第一映射关系表，确定目标域名对应的目标CDN节点回源关系操作可以包括：判断在第一映射关系表中，是否能查找到目标域名。若是，查找第一映射关系表中目标域名对应的目标CDN节点回源关系。若在第一映射关系表中，不能查找到目标域名，则可以 将预设CDN节点回源关系，作为目标域名对应的目标CDN节点回源关系。
其中，该预设CDN节点回源关系可以由本领域技术人员根据具体情况进行设定，在此不做详述。
下面从缓存管理服务器的角度，对本申请实施例提供的回源关系管理方法进行说明。
在本申请实施例中，该回源关系管理方法应用于：CDN(Content Delivery Network，内容分发网络)中心控制系统中的缓存管理服务器。该回源关系管理系统还包括缓存管理服务器。
其中，该回源关系管理服务器设置为：存储该回源关系管理系统中的缓存管理服务器中缓存的CDN节点回源关系，并可以对该回源关系管理系统中的缓存管理服务器中缓存的CDN节点回源关系进行调整，并可以将调整得到的CDN节点回源关系同步至缓存管理服务器。
该缓存管理服务器设置为：对该缓存管理服务器缓存的域名与CDN节点回源关系之间的映射关系进行管理，并且基于该缓存管理服务器缓存的域名与CDN节点回源关系之间的映射关系，对CDN节点所缓存的内容进行管理。例如，当该缓存管理服务器为回源配置文件下发服务器时，该缓存服务器基于缓存的域名与CDN节点回源关系之间的映射关系，给该域名对应的CDN节点下发回源配置文件，从而通过该回源配置文件实现对CDN节点所缓存的内容的管理。
其中，管理CDN节点回源关系的方式可参见图3所示的方法步骤。参见图3，该方法可以包括如下步骤：
S301：接收回源关系管理服务器发送的、目标域名和调整后的目标CDN节点回源关系；
S302：利用调整后的目标CDN节点回源关系，对缓存管理服务器中存储的、目标域名对应的CDN节点回源关系进行更新，得到新CDN节点回源关系。
可以理解的是，在本申请实施例中，当需要对该缓存管理服务器中存储的目标CDN节点回源关系进行调整时，该缓存管理服务器可以接收回源关系管理服务器发送的目标域名和调整后的目标CDN节点回源关系。然后，该缓存管理服务器可以根据该目标域名，查找到该缓存管理服务器中存储的该目标域名对应的目标CDN节点回源关系，并利用该调整后的目标CDN节点回源关系对该目标CDN节点回源关系进行更新，得到该目标域名对应的新CDN节点回源关系。这样，不需要技术人员通过手动修改的方式来修改缓存管理服务器中存储的各个域名对应的CDN节点回源关系，降低了CDN节点回源关系的维护成本和出错率，并且提高了维护效率。
可以理解的是，缓存管理服务器可以包括：回源配置文件下发服务器和/或内容刷新服务器。当然并不局限于此。
其中，当缓存管理服务器为回源配置文件下发服务器时，该缓存管理服务器还可以执行如下操作：基于新CDN节点回源关系，生成新CDN节点回源关系中的各个CDN节点的回源配置文件，并将生成的回源配置文件下发至对应的CDN节点，以使CDN节点根据接收到的回源配置文件进行回源。
当缓存管理服务器为内容刷新服务器时，该缓存管理服务器还可以执行如下操作：基于新CDN节点回源关系，生成新CDN节点回源关系中的各个CDN节点的刷新指令，并将生成的刷新指令下发至对应的CDN节点，以使CDN节点根据接收到的刷新指令对自身缓存的内容进行刷新。
相应于上述从回源关系管理服务器的角度提供的回源关系管理方法实施例，本申请实施还提供了一种回源关系管理装置。
参见图4，本申请实施例提供的回源关系管理装置，应用于回源关系管理系统中的回源关系管理服务器，回源关系管理系统还包括缓存管理服务器，缓存管理服务器设置为缓存域名与CDN节点回源关系之间的映射关系，该装置可以包括：
获得单元401，设置为获得待调整的目标CDN节点回源关系对应的目标 域名，以及针对目标CDN节点回源关系的调整信息；
调整单元402，设置为利用调整信息对目标CDN节点回源关系进行调整，得到调整后的目标CDN节点回源关系；其中，目标CDN节点回源关系为：基于目标域名以及第一映射关系表确定得到的；第一映射关系表用于对域名与CDN节点回源关系进行对应存储；
同步单元403，设置为将目标域名和调整后的目标CDN节点回源关系同步至缓存管理服务器。
可以理解的是，在本申请实施例中，当需要对该回源关系服务器中存储的目标CDN节点回源关系进行调整时，该回源关系管理服务器可以获得该目标CDN节点回源关系对应的目标域名。并通过该目标域名与该回源关系管理服务器中存储的第一映射关系表，找到该目标域名对应的目标CDN节点回源关系。其中，该第一映射关系表用于对域名与CDN节点回源关系进行对应存储。然后，该回源关系管理服务器可以根据获得的、针对该目标CDN节点回源关系的调整信息，对该目标CDN节点回源关系进行调整，得到调整后的目标CDN节点回源关系。进而，可以将该调整后的目标CDN节点回源关系同步至缓存管理服务器中。这样，不需要技术人员通过手动修改的方式来修改缓存管理服务器中存储的各个域名对应的CDN节点回源关系，降低了CDN节点回源关系的维护成本和出错率，并且提高了维护效率。
可选地，在本申请实施例中，获得单元401可以包括：
第一接收子单元，设置为接收待调整的目标CDN节点回源关系对应的目标域名；
确定子单元，设置为基于第一映射关系表，确定目标域名对应的目标CDN节点回源关系；
发送子单元，设置为将由目标CDN节点回源关系确定的信息发送至用户终端，以使用户终端基于信息，获得并展示目标CDN节点回源关系对应的拓扑结构图；
第二接收子单元，设置为接收用户终端发送的、针对拓扑结构图的调整信息，作为针对目标CDN节点回源关系的调整信息。
可选地，在本申请实施例中，针对拓扑结构图的调整信息可以包括以下至少之一信息：
对拓扑结构图中的CDN节点进行增加对应的操作信息；
对拓扑结构图中的CDN节点进行删除对应的操作信息；
对拓扑结构图中的CDN节点进行修改对应的操作信息；
对CDN节点之间的连接关系进行修改对应的操作信息。
可选地，在本申请实施例中，确定子单元包括：
判断模块，设置为在获得待调整的目标CDN节点回源关系对应的目标域名，以及针对目标CDN节点回源关系的调整信息之后，判断在第一映射关系表中，是否能查找到目标域名；
查找模块，设置为当在第一映射表中能查找到目标域名时，查找第一映射关系表中目标域名对应的目标CDN节点回源关系。
可选地，在本申请实施例中，该装置还可以包括：
确定模块，设置为在第一映射关系表中不能查找到目标域名时，将预设CDN节点回源关系，作为目标域名对应的目标CDN节点回源关系。
其中，由于本装置实施例基本相似于从回源关系管理服务器的角度提供的方法实施例，所以描述的比较简单，相关之处参见该从回源关系管理服务器的角度提供的方法实施例的部分的说明。
相应于上述从缓存管理服务器的角度提供的回源关系管理方法实施例，本申请实施还提供了一种回源关系管理装置。
参见图5，本申请实施例提供的回源关系管理装置，应用于回源关系管理系统中的缓存管理服务器，回源关系管理系统还包括回源关系管理服务器，该装置可以包括：
接收单元501，设置为接收回源关系管理服务器发送的、目标域名和调整后的目标CDN节点回源关系；
更新单元502，设置为利用调整后的目标CDN节点回源关系，对缓存管理服务器中存储的、目标域名对应的CDN节点回源关系进行更新，得到新CDN节点回源关系。
可以理解的是，在本申请实施例中，当需要对该缓存管理服务器中存储的目标CDN节点回源关系进行调整时，该缓存管理服务器可以接收回源关系管理服务器发送的目标域名和调整后的目标CDN节点回源关系。然后，该缓存管理服务器可以根据该目标域名，查找到该缓存管理服务器中存储的该目标域名对应的目标CDN节点回源关系，并利用该调整后的目标CDN节点回源关系对该目标CDN节点回源关系进行更新，得到该目标域名对应的新CDN节点回源关系。这样，不需要技术人员通过手动修改的方式来修改缓存管理服务器中存储的各个域名对应的CDN节点回源关系，降低了CDN节点回源关系的维护成本和出错率，并且提高了维护效率。
可选地，在本申请实施例中，缓存管理服务器包括：回源配置文件下发服务器和/或内容刷新服务器；该装置还可以包括：
第一生成单元，设置为当缓存管理服务器为回源配置文件下发服务器时，基于新CDN节点回源关系，生成新CDN节点回源关系中的各个CDN节点的回源配置文件，并将生成的回源配置文件下发至对应的CDN节点；
第二生成单元，设置为当缓存管理服务器为内容刷新服务器时，基于新CDN节点回源关系，生成新CDN节点回源关系中的各个CDN节点的刷新指令，并将生成的刷新指令下发至对应的CDN节点。
其中，由于本装置实施例基本相似于从缓存管理服务器的角度提供的方法实施例，所以描述的比较简单，相关之处参见该从缓存管理服务器的角度提供的方法实施例的部分的说明。
相应于上述从回源关系管理服务器的角度提供的回源关系管理方法实施例，本申请实施还提供了一种回源关系管理服务器。
参见图6，本申请实施例提供的回源关系管理服务器为回源关系管理系统中的服务器，回源关系管理系统还包括缓存管理服务器，缓存管理服务器设置为缓存域名与CDN节点回源关系之间的映射关系；回源关系管理服务器包括处理器601、通信接口602、存储器603和通信总线604，其中，处理器601，通信接口602，存储器603通过通信总线604完成相互间的通信；
存储器603，设置为存放计算机程序；
处理器601，设置为执行存储器603上所存放的程序时，实现上述从回源关系管理服务器角度提供的任一回源关系管理方法实施例的方法步骤。
可以理解的是，在本申请实施例中，当需要对该回源关系服务器中存储的目标CDN节点回源关系进行调整时，该回源关系管理服务器可以获得该目标CDN节点回源关系对应的目标域名。并通过该目标域名与该回源关系管理服务器中存储的第一映射关系表，找到该目标域名对应的目标CDN节点回源关系。其中，该第一映射关系表用于对域名与CDN节点回源关系进行对应存储。然后，该回源关系管理服务器可以根据获得的、针对该目标CDN节点回源关系的调整信息，对该目标CDN节点回源关系进行调整，得到调整后的目标CDN节点回源关系。进而，可以将该调整后的目标CDN节点回源关系同步至缓存管理服务器中。这样，不需要技术人员通过手动修改的方式来修改缓存管理服务器中存储的各个域名对应的CDN节点回源关系，降低了CDN节点回源关系的维护成本和出错率，并且提高了维护效率。
相应于上述从缓存管理服务器的角度提供的回源关系管理方法实施例，本申请实施还提供了一种缓存管理服务器。
参见图7，本申请实施例提供的缓存管理服务器为回源关系管理系统中的服务器，回源关系管理系统还包括回源关系管理服务器；缓存管理服务器包括处理器701、通信接口702、存储器703和通信总线704，其中，处理器701，通信接口702，存储器703通过通信总线704完成相互间的通信；
存储器703，设置为存放计算机程序；
处理器701，设置为执行存储器703上所存放的程序时，实现上述从缓存 管理服务器角度提供的任一回源关系管理方法实施例的方法步骤。
可以理解的是，在本申请实施例中，当需要对该缓存管理服务器中存储的目标CDN节点回源关系进行调整时，该缓存管理服务器可以接收回源关系管理服务器发送的目标域名和调整后的目标CDN节点回源关系。然后，该缓存管理服务器可以根据该目标域名，查找到该缓存管理服务器中存储的该目标域名对应的目标CDN节点回源关系，并利用该调整后的目标CDN节点回源关系对该目标CDN节点回源关系进行更新，得到该目标域名对应的新CDN节点回源关系。这样，不需要技术人员通过手动修改的方式来修改缓存管理服务器中存储的各个域名对应的CDN节点回源关系，降低了CDN节点回源关系的维护成本和出错率，并且提高了维护效率。
其中，上述电子设备提到的通信总线可以是外设部件互连标准(Peripheral Component Interconnect，PCI)总线或扩展工业标准结构(Extended Industry Standard Architecture，EISA)总线等。该通信总线可以分为地址总线、数据总线、控制总线等。为便于表示，图中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。
通信接口用于上述电子设备与其他设备之间的通信。
存储器可以包括随机存取存储器(Random Access Memory，RAM)，也可以包括非易失性存储器(Non-Volatile Memory，NVM)，例如至少一个磁盘存储器。可选的，存储器还可以是至少一个位于远离前述处理器的存储装置。
上述的处理器可以是通用处理器，包括中央处理器(Central Processing Unit，CPU)、网络处理器(Network Processor，NP)等；还可以是数字信号处理器(Digital Signal Processing，DSP)、专用集成电路(Application Specific Integrated Circuit，ASIC)、现场可编程门阵列(Field-Programmable Gate Array，FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件。
相应于上述回源关系管理服务器和缓存管理服务器实施例，本申请实施 例还提供了一种回源关系管理系统，参见图8，该回源关系管理系统800可以包括：回源关系管理服务器801和缓存管理服务器802；
回源关系管理服务器801设置为：
获得待调整的目标CDN节点回源关系对应的目标域名，以及针对目标CDN节点回源关系的调整信息；
利用调整信息对目标CDN节点回源关系进行调整，得到调整后的目标CDN节点回源关系；其中，目标CDN节点回源关系为：基于目标域名以及第一映射关系表确定得到的；第一映射关系表用于对域名与CDN节点回源关系进行对应存储；
将目标域名和调整后的目标CDN节点回源关系同步至缓存管理服务器；
缓存管理服务器802设置为：
接收回源关系管理服务器发送的、目标域名和调整后的目标CDN节点回源关系；
利用调整后的目标CDN节点回源关系，对缓存管理服务器中存储的、目标域名对应的CDN节点回源关系进行更新，得到新CDN节点回源关系。
其中，由图8可知，回源关系管理服务器801可以编辑拓扑，也就是，可以对自身存储的CDN节点回源关系进行编辑，得到调整后的CDN节点回源关系，并可以对该调整后的CDN节点回源关系进行存储。并且，在得到调整后的CDN节点回源关系后，还可以主动将该调整后的CDN节点回源关系发送至缓存管理服务器802。当然，也可以在接收到缓存管理服务器802的获取请求后，将该调整后的CDN节点回源关系发送至缓存管理服务器802，这都是合理的。并且，缓存管理服务器802在接收到该调整后的CDN节点回源关系后，可以基于该调整后的CDN节点回源关系生成刷新指令或者回源配置文件，进而给相应的CDN节点发送该刷新指令或回源配置文件。
在本申请实施例中，当需要对该回源关系服务器中存储的目标CDN节点回源关系进行调整时，该回源关系管理服务器可以获得该目标CDN节点回源关系对应的目标域名。并通过该目标域名与该回源关系管理服务器中存储的 第一映射关系表，找到该目标域名对应的目标CDN节点回源关系。其中，该第一映射关系表用于对域名与CDN节点回源关系进行对应存储。然后，该回源关系管理服务器可以根据获得的、针对该目标CDN节点回源关系的调整信息，对该目标CDN节点回源关系进行调整，得到调整后的目标CDN节点回源关系。进而，可以将该调整后的目标CDN节点回源关系同步至缓存管理服务器中。
该缓存管理服务器可以接收回源关系管理服务器发送的目标域名和调整后的目标CDN节点回源关系。然后，该缓存管理服务器可以根据该目标域名，查找到该缓存管理服务器中存储的该目标域名对应的目标CDN节点回源关系，并利用该调整后的目标CDN节点回源关系对该目标CDN节点回源关系进行更新，得到该目标域名对应的新CDN节点回源关系。这样，不需要技术人员通过手动修改的方式来修改缓存管理服务器中存储的各个域名对应的CDN节点回源关系，降低了CDN节点回源关系的维护成本和出错率，并且提高了维护效率。
可选地，缓存管理服务器可以包括：回源配置文件下发服务器和/或内容刷新服务器；
当缓存管理服务器为回源配置文件下发服务器时，回源配置文件下发服务器还设置为：
基于新CDN节点回源关系，生成新CDN节点回源关系中的各个CDN节点的回源配置文件，并将生成的回源配置文件下发至对应的CDN节点；
当缓存管理服务器为内容刷新服务器时，内容刷新服务器还设置为：基于新CDN节点回源关系，生成新CDN节点回源关系中的各个CDN节点的刷新指令，并将生成的刷新指令下发至对应的CDN节点。
可选地，回源关系管理服务器还设置为通过以下方式获得待调整的目标CDN节点回源关系对应的目标域名，以及针对目标CDN节点回源关系的调整信息：
接收待调整的目标CDN节点回源关系对应的目标域名；
基于第一映射关系表，确定目标域名对应的目标CDN节点回源关系；
将由目标CDN节点回源关系确定的信息发送至用户终端，以使用户终端基于信息，获得并展示目标CDN节点回源关系对应的拓扑结构图；
接收用户终端发送的、针对拓扑结构图的调整信息，作为针对目标CDN节点回源关系的调整信息。
可选地，针对拓扑结构图的调整信息可以包括以下至少之一信息：
对拓扑结构图中的CDN节点进行增加对应的操作信息；
对拓扑结构图中的CDN节点进行删除对应的操作信息；
对拓扑结构图中的CDN节点进行修改对应的操作信息；
对CDN节点之间的连接关系进行修改对应的操作信息。
可选地，回源关系管理服务器还设置为基于第一映射关系表，通过以下方式确定目标域名对应的目标CDN节点回源关系：
判断在第一映射关系表中，是否能查找到目标域名；
若在第一映射关系表中能查找到目标域名，查找第一映射关系表中目标域名对应的目标CDN节点回源关系。
可选地，若在第一映射关系表中，不能查找到目标域名，回源关系管理服务器还可以设置为：
将预设CDN节点回源关系，作为目标域名对应的目标CDN节点回源关系。
其中，由于本系统实施例基本相似于从回源关系管理服务器和缓存管理服务器的角度提供的方法实施例，所以描述的比较简单，相关之处参见该从回源关系管理服务器和缓存管理服务器的角度提供的方法实施例的部分的说明。
相应于上述从回源关系管理服务器的角度提供的回源关系管理方法实施 例，本申请实施还提供了一种存储介质。该存储介质为：回源关系管理服务器中的存储介质，回源关系管理服务器为回源关系管理系统中的服务器，回源关系管理系统还包括缓存管理服务器，缓存管理服务器设置为缓存域名与CDN节点回源关系之间的映射关系；存储介质内存储有计算机程序，计算机程序被处理器执行时实现：上述从回源关系管理服务器的角度提供的任一回源关系管理方法实施例的方法步骤。
可以理解的是，在本申请实施例中，当需要对该回源关系服务器中存储的目标CDN节点回源关系进行调整时，该回源关系管理服务器可以获得该目标CDN节点回源关系对应的目标域名。并通过该目标域名与该回源关系管理服务器中存储的第一映射关系表，找到该目标域名对应的目标CDN节点回源关系。其中，该第一映射关系表用于对域名与CDN节点回源关系进行对应存储。然后，该回源关系管理服务器可以根据获得的、针对该目标CDN节点回源关系的调整信息，对该目标CDN节点回源关系进行调整，得到调整后的目标CDN节点回源关系。进而，可以将该调整后的目标CDN节点回源关系同步至缓存管理服务器中。这样，不需要技术人员通过手动修改的方式来修改缓存管理服务器中存储的各个域名对应的CDN节点回源关系，降低了CDN节点回源关系的维护成本和出错率，并且提高了维护效率。
相应于上述从缓存管理服务器的角度提供的回源关系管理方法实施例，本申请实施还提供了一种存储介质，该存储介质为：缓存管理服务器中的存储介质，缓存管理服务器为回源关系管理系统中的服务器，回源关系管理系统还包括回源关系管理服务器；存储介质内存储有计算机程序，计算机程序被处理器执行时实现：上述从缓存管理服务器的角度提供的任一回源关系管理方法实施例的方法步骤。
可以理解的是，在本申请实施例中，当需要对该缓存管理服务器中存储的目标CDN节点回源关系进行调整时，该缓存管理服务器可以接收回源关系管理服务器发送的目标域名和调整后的目标CDN节点回源关系。然后，该缓存管理服务器可以根据该目标域名，查找到该缓存管理服务器中存储的该目标域名对应的目标CDN节点回源关系，并利用该调整后的目标CDN节点回源 关系对该目标CDN节点回源关系进行更新，得到该目标域名对应的新CDN节点回源关系。这样，不需要技术人员通过手动修改的方式来修改缓存管理服务器中存储的各个域名对应的CDN节点回源关系，降低了CDN节点回源关系的维护成本和出错率，并且提高了维护效率。
相应于上述从回源关系管理服务器的角度提供的回源关系管理方法实施例，本申请实施还提供了一种计算机程序产品。该计算机程序产品用于在运行时实现：上述从回源关系管理服务器的角度提供的任一回源关系管理方法实施例的方法步骤。
本申请实施例提供的计算机程序产品被回源关系管理服务器的处理器执行后，当需要对该回源关系服务器中存储的目标CDN节点回源关系进行调整时，该回源关系管理服务器可以获得该目标CDN节点回源关系对应的目标域名。并通过该目标域名与该回源关系管理服务器中存储的第一映射关系表，找到该目标域名对应的目标CDN节点回源关系。其中，该第一映射关系表用于对域名与CDN节点回源关系进行对应存储。然后，该回源关系管理服务器可以根据获得的、针对该目标CDN节点回源关系的调整信息，对该目标CDN节点回源关系进行调整，得到调整后的目标CDN节点回源关系。进而，可以将该调整后的目标CDN节点回源关系同步至缓存管理服务器中。这样，不需要技术人员通过手动修改的方式来修改缓存管理服务器中存储的各个域名对应的CDN节点回源关系，降低了CDN节点回源关系的维护成本和出错率，并且提高了维护效率。
相应于上述从缓存管理服务器的角度提供的回源关系管理方法实施例，本申请实施还提供了一种计算机程序产品。该计算机程序产品用于在运行时实现：上述从缓存管理服务器的角度提供的任一回源关系管理方法实施例的方法步骤。
本申请实施例提供的计算机程序产品被缓存管理服务器的处理器执行后，当需要对该缓存管理服务器中存储的目标CDN节点回源关系进行调整时，该 缓存管理服务器可以接收回源关系管理服务器发送的目标域名和调整后的目标CDN节点回源关系。然后，该缓存管理服务器可以根据该目标域名，查找到该缓存管理服务器中存储的该目标域名对应的目标CDN节点回源关系，并利用该调整后的目标CDN节点回源关系对该目标CDN节点回源关系进行更新，得到该目标域名对应的新CDN节点回源关系。这样，不需要技术人员通过手动修改的方式来修改缓存管理服务器中存储的各个域名对应的CDN节点回源关系，降低了CDN节点回源关系的维护成本和出错率，并且提高了维护效率。
需要说明的是，在本文中，诸如第一和第二等之类的关系术语仅仅用来将一个实体或者操作与另一个实体或操作区分开来，而不一定要求或者暗示这些实体或操作之间存在任何这种实际的关系或者顺序。而且，术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含，从而使得包括一系列要素的过程、方法、物品或者设备不仅包括那些要素，而且还包括没有明确列出的其他要素，或者是还包括为这种过程、方法、物品或者设备所固有的要素。在没有更多限制的情况下，由语句“包括一个……”限定的要素，并不排除在包括所述要素的过程、方法、物品或者设备中还存在另外的相同要素。
本说明书中的各个实施例均采用相关的方式描述，各个实施例之间相同相似的部分互相参见即可，每个实施例重点说明的都是与其他实施例的不同之处。尤其，对于装置、服务器、系统、存储介质和计算机程序产品实施例而言，由于其基本相似于方法实施例，所以描述的比较简单，相关之处参见方法实施例的部分说明即可。
以上所述仅为本申请的较佳实施例而已，并非用于限定本申请的保护范围。凡在本申请的精神和原则之内所作的任何修改、等同替换、改进等，均包含在本申请的保护范围内。
工业实用性
基于本申请实施例提供的上述技术方案，当需要对该回源关系服务器中存储的目标CDN节点回源关系进行调整时，该回源关系管理服务器可以获得该目标CDN节点回源关系对应的目标域名，并通过该目标域名与该回源关系管理服务器中存储的第一映射关系表，找到该目标域名对应的目标CDN节点 回源关系，然后，该回源关系管理服务器可以根据获得的、针对该目标CDN节点回源关系的调整信息，对该目标CDN节点回源关系进行调整，得到调整后的目标CDN节点回源关系。进而，可以将该调整后的目标CDN节点回源关系同步至缓存管理服务器中。这样，不需要技术人员通过手动修改的方式来修改缓存管理服务器中存储的各个域名对应的CDN节点回源关系，降低了CDN节点回源关系的维护成本和出错率，并且提高了维护效率。

Claims (21)

  1. 一种回源关系管理系统，所述回源关系管理系统包括：回源关系管理服务器和缓存管理服务器；
    所述回源关系管理服务器设置为：
    获得待调整的目标CDN节点回源关系对应的目标域名，以及针对所述目标CDN节点回源关系的调整信息；
    利用所述调整信息对所述目标CDN节点回源关系进行调整，得到调整后的目标CDN节点回源关系；其中，所述目标CDN节点回源关系为基于所述目标域名以及第一映射关系表确定得到的，所述第一映射关系表用于对域名与CDN节点回源关系进行对应存储；
    将所述目标域名和调整后的目标CDN节点回源关系同步至所述缓存管理服务器；
    所述缓存管理服务器设置为：
    接收所述回源关系管理服务器发送的、目标域名和调整后的目标CDN节点回源关系；
    利用所述调整后的目标CDN节点回源关系，对所述缓存管理服务器中存储的、所述目标域名对应的CDN节点回源关系进行更新，得到新CDN节点回源关系。
  2. 根据权利要求1所述的系统，其中，所述缓存管理服务器包括：回源配置文件下发服务器和/或内容刷新服务器；
    当所述缓存管理服务器为所述回源配置文件下发服务器时，所述回源配置文件下发服务器还设置为：
    基于所述新CDN节点回源关系，生成所述新CDN节点回源关系中的各个CDN节点的回源配置文件，并将生成的回源配置文件下发至对应的CDN节点；
    当所述缓存管理服务器为所述内容刷新服务器时，所述内容刷新服务器还设置为：基于所述新CDN节点回源关系，生成所述新CDN节点回源关系中 的各个CDN节点的刷新指令，并将生成的刷新指令下发至对应的CDN节点。
  3. 根据权利要求1所述的系统，所述回源关系管理服务器还设置为通过以下方式获得待调整的目标CDN节点回源关系对应的目标域名，以及针对所述目标CDN节点回源关系的调整信息：
    接收待调整的目标CDN节点回源关系对应的目标域名；
    基于所述第一映射关系表，确定所述目标域名对应的目标CDN节点回源关系；
    将由所述目标CDN节点回源关系确定的信息发送至用户终端，以使所述用户终端基于所述信息，获得并展示所述目标CDN节点回源关系对应的拓扑结构图；
    接收所述用户终端发送的、针对所述拓扑结构图的调整信息，作为针对所述目标CDN节点回源关系的调整信息。
  4. 根据权利要求3所述的系统，其中，所述针对所述拓扑结构图的调整信息，包括以下至少之一信息：
    对所述拓扑结构图中的CDN节点进行增加对应的操作信息；
    对所述拓扑结构图中的CDN节点进行删除对应的操作信息；
    对所述拓扑结构图中的CDN节点进行修改对应的操作信息；
    对CDN节点之间的连接关系进行修改对应的操作信息。
  5. 根据权利要求3所述的系统，其中，所述回源关系管理服务器还设置为基于所述第一映射关系表，通过以下方式确定所述目标域名对应的目标CDN节点回源关系：
    判断在所述第一映射关系表中，是否能查找到所述目标域名；
    若在所述第一映射关系表中能查找到所述目标域名，查找所述第一映射关系表中所述目标域名对应的目标CDN节点回源关系。
  6. 根据权利要求5所述的系统，其中，若在所述第一映射关系表中，不能查找到所述目标域名，所述回源关系管理服务器还设置为：
    将预设CDN节点回源关系，作为所述目标域名对应的目标CDN节点回源关系。
  7. 一种回源关系管理方法，，应用于回源关系管理系统中的回源关系管理服务器，所述回源关系管理系统还包括缓存管理服务器，所述缓存管理服务器用于缓存域名与CDN节点回源关系之间的映射关系，所述方法包括：
    获得待调整的目标CDN节点回源关系对应的目标域名，以及针对所述目标CDN节点回源关系的调整信息；
    利用所述调整信息对所述目标CDN节点回源关系进行调整，得到调整后的目标CDN节点回源关系；其中，所述目标CDN节点回源关系为基于所述目标域名以及第一映射关系表确定得到的，所述第一映射关系表用于对域名与CDN节点回源关系进行对应存储；
    将所述目标域名和调整后的目标CDN节点回源关系同步至所述缓存管理服务器。
  8. 根据权利要求7所述的方法，其中，所述获得待调整的目标CDN节点回源关系对应的目标域名，以及针对所述目标CDN节点回源关系的调整信息的步骤，包括：
    接收待调整的目标CDN节点回源关系对应的目标域名；
    基于所述第一映射关系表，确定所述目标域名对应的目标CDN节点回源关系；
    将由所述目标CDN节点回源关系确定的信息发送至用户终端，以使所述用户终端基于所述信息，获得并展示所述目标CDN节点回源关系对应的拓扑结构图；
    接收所述用户终端发送的、针对所述拓扑结构图的调整信息，作为针对所述目标CDN节点回源关系的调整信息。
  9. 根据权利要求8所述的方法，其中，所述针对所述拓扑结构图的调整信息，包括以下至少之一信息：
    对所述拓扑结构图中的CDN节点进行增加对应的操作信息；
    对所述拓扑结构图中的CDN节点进行删除对应的操作信息；
    对所述拓扑结构图中的CDN节点进行修改对应的操作信息；
    对CDN节点之间的连接关系进行修改对应的操作信息。
  10. 根据权利要求8所述的方法，其中，所述基于所述第一映射关系表，确定所述目标域名对应的目标CDN节点回源关系的步骤，包括：
    判断在所述第一映射关系表中，是否能查找到所述目标域名；
    若在所述第一映射关系表中能查找到所述目标域名，查找所述第一映射关系表中所述目标域名对应的目标CDN节点回源关系。
  11. 根据权利要求10所述的方法，其中，若在所述第一映射关系表中，不能查找到所述目标域名，所述方法还包括：
    将预设CDN节点回源关系，作为所述目标域名对应的目标CDN节点回源关系。
  12. 一种回源关系管理方法，应用于回源关系管理系统中的缓存管理服务器，所述回源关系管理系统还包括回源关系管理服务器，所述方法包括：
    接收所述回源关系管理服务器发送的、目标域名和调整后的目标CDN节点回源关系；
    利用所述调整后的目标CDN节点回源关系，对所述缓存管理服务器中存储的、所述目标域名对应的CDN节点回源关系进行更新，得到新CDN节点回源关系。
  13. 根据权利要求12所述的方法，其中，所述缓存管理服务器包括：回源配置文件下发服务器和/或内容刷新服务器；所述方法还包括：
    当所述缓存管理服务器为所述回源配置文件下发服务器时，基于所述新CDN节点回源关系，生成所述新CDN节点回源关系中的各个CDN节点的回源配置文件，并将生成的回源配置文件下发至对应的CDN节点；
    当所述缓存管理服务器为所述内容刷新服务器时，基于所述新CDN节点回源关系，生成所述新CDN节点回源关系中的各个CDN节点的刷新指令，并 将生成的刷新指令下发至对应的CDN节点。
  14. 一种回源关系管理装置，应用于回源关系管理系统中的回源关系管理服务器，所述回源关系管理系统还包括缓存管理服务器，所述缓存管理服务器设置为缓存域名与CDN节点回源关系之间的映射关系，所述装置包括：
    获得单元，设置为获得待调整的目标CDN节点回源关系对应的目标域名，以及针对所述目标CDN节点回源关系的调整信息；
    调整单元，设置为利用所述调整信息对所述目标CDN节点回源关系进行调整，得到调整后的目标CDN节点回源关系；其中，所述目标CDN节点回源关系为基于所述目标域名以及第一映射关系表确定得到的，所述第一映射关系表设置为对域名与CDN节点回源关系进行对应存储；
    同步单元，设置为将所述目标域名和调整后的目标CDN节点回源关系同步至所述缓存管理服务器。
  15. 一种回源关系管理装置，应用于回源关系管理系统中的缓存管理服务器，所述回源关系管理系统还包括回源关系管理服务器，所述装置包括：
    接收单元，设置为接收所述回源关系管理服务器发送的、目标域名和调整后的目标CDN节点回源关系；
    更新单元，设置为利用所述调整后的目标CDN节点回源关系，对所述缓存管理服务器中存储的、所述目标域名对应的CDN节点回源关系进行更新，得到新CDN节点回源关系。
  16. 一种回源关系管理服务器，所述回源关系管理服务器为回源关系管理系统中的服务器，所述回源关系管理系统还包括缓存管理服务器，所述缓存管理服务器设置为缓存域名与CDN节点回源关系之间的映射关系；所述回源关系管理服务器包括处理器、通信接口、存储器和通信总线，其中，处理器，通信接口，存储器通过通信总线完成相互间的通信；
    存储器，设置为存放计算机程序；
    处理器，设置为执行存储器上所存放的程序时，实现权利要求7-11中任一所述的方法步骤。
  17. 一种缓存管理服务器，所述缓存管理服务器为回源关系管理系统中的服务器，所述回源关系管理系统还包括回源关系管理服务器；所述缓存管理服务器包括处理器、通信接口、存储器和通信总线，其中，处理器，通信接口，存储器通过通信总线完成相互间的通信；
    存储器，设置为存放计算机程序；
    处理器，设置为执行存储器上所存放的程序时，实现权利要求12-13中任一所述的方法步骤。
  18. 一种存储介质，所述存储介质为：回源关系管理服务器中的存储介质，所述回源关系管理服务器为回源关系管理系统中的服务器，所述回源关系管理系统还包括缓存管理服务器，所述缓存管理服务器用于缓存域名与CDN节点回源关系之间的映射关系；所述存储介质内存储有计算机程序，所述计算机程序被处理器执行时实现权利要求7-11中任一项所述的方法步骤。
  19. 一种存储介质，所述存储介质为：缓存管理服务器中的存储介质，所述缓存管理服务器为回源关系管理系统中的服务器，所述回源关系管理系统还包括回源关系管理服务器；所述存储介质内存储有计算机程序，所述计算机程序被处理器执行时实现权利要求12-13中任一项所述的方法步骤。
  20. 一种计算机程序产品，所述计算机程序产品用于在运行时执行权利要求7-11中任一项所述的方法步骤。
  21. 一种计算机程序产品，所述计算机程序产品用于在运行时执行权利要求12-13中任一项所述的方法步骤。
PCT/CN2019/072937 2018-01-26 2019-01-24 一种回源关系管理系统、方法、装置、服务器及存储介质 WO2019144899A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US16/962,565 US11588723B2 (en) 2018-01-26 2019-01-24 Return source relationship management system, method, device, and server, and storage medium

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201810078366.9A CN110086721B (zh) 2018-01-26 2018-01-26 一种回源关系管理系统、方法、装置、服务器及存储介质
CN201810078366.9 2018-01-26

Publications (1)

Publication Number Publication Date
WO2019144899A1 true WO2019144899A1 (zh) 2019-08-01

Family

ID=67394505

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/072937 WO2019144899A1 (zh) 2018-01-26 2019-01-24 一种回源关系管理系统、方法、装置、服务器及存储介质

Country Status (3)

Country Link
US (1) US11588723B2 (zh)
CN (1) CN110086721B (zh)
WO (1) WO2019144899A1 (zh)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112751912B (zh) * 2020-12-15 2021-12-03 北京金山云网络技术有限公司 配置调整方法、装置及电子设备
CN114244714B (zh) * 2021-12-14 2024-04-09 北京金山云网络技术有限公司 域名配置管理方法、装置及系统、计算机可读存储介质
CN114900562B (zh) * 2022-05-09 2023-07-21 北京百度网讯科技有限公司 一种资源获取方法、装置、电子设备和存储介质

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104011701A (zh) * 2011-12-14 2014-08-27 第三雷沃通讯有限责任公司 内容传送网络
CN105450780A (zh) * 2015-12-31 2016-03-30 深圳市网心科技有限公司 一种cdn系统及其回源方法
CN105871649A (zh) * 2016-06-21 2016-08-17 上海帝联信息科技股份有限公司 节点服务器、服务端及其配置文件更新、更新控制方法
CN105991459A (zh) * 2015-02-15 2016-10-05 上海帝联信息科技股份有限公司 Cdn节点回源路由分配方法、装置和系统
WO2017218473A1 (en) * 2016-06-15 2017-12-21 Alibaba Group Holding Limited Dynamic acceleration in content delivery network

Family Cites Families (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6925504B1 (en) * 2002-01-31 2005-08-02 Cisco Technology, Inc. Methods and apparatus for obtaining content from a content-originating device within a computerized network
US7368961B2 (en) * 2005-12-22 2008-05-06 Rambus Inc. Clock distribution network supporting low-power mode
US8606847B2 (en) * 2010-05-28 2013-12-10 Juniper Networks, Inc. Application-layer traffic optimization service map updates
CN102647299B (zh) * 2012-04-24 2014-10-15 网宿科技股份有限公司 基于内容分发网络的层次化报警分析方法和系统
US9634918B2 (en) * 2012-12-13 2017-04-25 Level 3 Communications, Llc Invalidation sequencing in a content delivery framework
WO2015104583A1 (en) * 2014-01-08 2015-07-16 Telefonaktiebolaget L M Ericsson (Publ) Method, node and distributed system for configuring a network of cdn caching nodes
CN104967873A (zh) * 2015-06-29 2015-10-07 上海帝联信息科技股份有限公司 流媒体直播调度方法、系统和调度服务器
CN105898352A (zh) * 2015-11-13 2016-08-24 乐视云计算有限公司 基于m3u8的流媒体文件直播方法及系统
CN105847401A (zh) * 2016-04-25 2016-08-10 乐视控股（北京）有限公司 一种请求信息处理方法及设备
US10530852B2 (en) * 2016-05-19 2020-01-07 Level 3 Communications, Llc Network mapping in content delivery network
CN106603703B (zh) * 2016-12-29 2020-09-04 北京奇艺世纪科技有限公司 一种回源节点确定方法及装置
CN106888270B (zh) * 2017-03-30 2020-06-23 网宿科技股份有限公司 回源选路调度的方法和系统

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104011701A (zh) * 2011-12-14 2014-08-27 第三雷沃通讯有限责任公司 内容传送网络
CN105991459A (zh) * 2015-02-15 2016-10-05 上海帝联信息科技股份有限公司 Cdn节点回源路由分配方法、装置和系统
CN105450780A (zh) * 2015-12-31 2016-03-30 深圳市网心科技有限公司 一种cdn系统及其回源方法
WO2017218473A1 (en) * 2016-06-15 2017-12-21 Alibaba Group Holding Limited Dynamic acceleration in content delivery network
CN105871649A (zh) * 2016-06-21 2016-08-17 上海帝联信息科技股份有限公司 节点服务器、服务端及其配置文件更新、更新控制方法

Also Published As

Publication number Publication date
CN110086721B (zh) 2021-03-12
US20200344149A1 (en) 2020-10-29
CN110086721A (zh) 2019-08-02
US11588723B2 (en) 2023-02-21

Similar Documents

Publication Publication Date Title
WO2019144899A1 (zh) 一种回源关系管理系统、方法、装置、服务器及存储介质
KR101841311B1 (ko) 디렉토리 리싱
TWI431978B (zh) Methods, devices and systems for obtaining resources
TWI671643B (zh) 配置變更方法、設備及系統
US10642787B1 (en) Pre-file-transfer update based on prioritized metadata
TWI536789B (zh) 一種網際網路協定的管理方法及其系統、用戶端與伺服器
WO2021007752A1 (zh) 内容分发网络中的回源方法及相关装置
CN103916277B (zh) 实现重启时不中断转发业务的方法和装置
US20190075182A1 (en) Partitioned Serialized Caching and Delivery of Large Files
WO2022222438A1 (zh) 配置文件状态同步方法、装置、终端、服务器和存储介质
WO2021031905A1 (zh) 数据管理方法、装置、设备、系统及计算机可读存储介质
WO2015183373A1 (en) Partitioning a database
US11082522B2 (en) Information acquisition
CN113271359A (zh) 刷新缓存数据的方法、装置、电子设备和存储介质
CN109617817B (zh) 一种mlag组网的转发表项的生成方法及装置
WO2017092184A1 (zh) 一种fru的读取/写入方法及读/写系统
CN115297085B (zh) 一种域名解析的更新方法、装置、电子设备及存储介质
CN112615727B (zh) 获取设备缺省配置的方法及装置
US20140359072A1 (en) Maintaining state synchronization of an application between computing devices as well as maintaining state synchronization of common information between different applications without requiring perioidic synchronization
TW201605214A (zh) 網路協定位址之設定方法及伺服管理系統
US11281683B1 (en) Distributed computation system for servicing queries using revisions maps
JP2018067084A (ja) 共同作業システム及び編集管理プログラム並びに編集管理方法
WO2020024375A1 (zh) 一种数据传输管理的方法及装置
CN111600958A (zh) 服务发现系统、服务数据管理方法、服务器及存储介质
CN114424179A (zh) 将规则应用于客户端对共享记录的更新以触发系统生成的更新

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 19744065

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 16/11/2021)

122 Ep: pct application non-entry in european phase

Ref document number: 19744065

Country of ref document: EP

Kind code of ref document: A1