WO2022068333A1 - 访问请求的处理方法、装置、电子设备及计算机可读存储介质 - Google Patents

访问请求的处理方法、装置、电子设备及计算机可读存储介质 Download PDF

Info

Publication number
WO2022068333A1
WO2022068333A1 PCT/CN2021/107856 CN2021107856W WO2022068333A1 WO 2022068333 A1 WO2022068333 A1 WO 2022068333A1 CN 2021107856 W CN2021107856 W CN 2021107856W WO 2022068333 A1 WO2022068333 A1 WO 2022068333A1
Authority
WO
WIPO (PCT)
Prior art keywords
domain name
access request
node
processing
target domain
Prior art date
Application number
PCT/CN2021/107856
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 北京金山云网络技术有限公司
Publication of WO2022068333A1 publication Critical patent/WO2022068333A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/56—Provisioning of proxy services
    • H04L67/568—Storing data temporarily at an intermediate stage, e.g. caching
    • 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/06—Management of faults, events, alarms or notifications
    • H04L41/0654—Management of faults, events, alarms or notifications using network fault recovery
    • H04L41/0659—Management of faults, events, alarms or notifications using network fault recovery by isolating or reconfiguring faulty entities
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network

Definitions

  • the present application relates to the field of Internet technologies, and in particular, to a method, apparatus, electronic device, and computer-readable storage medium for processing an access request.
  • CDN nodes are divided into two levels: edge nodes and upper-level nodes, and nodes at different levels play different roles.
  • the edge node is used to serve users' access to the domain name and cache the content of the domain name.
  • the edge node will access its corresponding upper-level node. If the upper-level node has the cached content of the domain name, it will directly respond to the edge node. If there is no cached content of the domain name, the upper-level node will The node will go back to the domain name origin site to pull the corresponding cached content, then cache it on this node, and then respond to the edge node.
  • the related CDN node back-to-source methods such as optimal back-to-source, because edge nodes do not distinguish domain names when back-to-source to upper-layer nodes, but detect the connectivity of upper-layer nodes and use round-robin training to select the best back-to-source.
  • This method will cause multiple upper-level nodes to cache the same resources at the same time, and if the caches of these multiple upper-level nodes do not have the required resources, they will all pull the resources back to the origin site, which will result in a higher return-to-origin rate for domain name access. It also causes redundant storage of upper-layer nodes, which reduces the overall caching capability of the content distribution network.
  • the related CDN node back-to-source methods also have the problems of high back-to-source rate of domain name access, serious redundant storage of upper-level nodes, and weak overall caching capability of the content distribution network.
  • the purpose of this application is to provide an access request processing method, device, electronic device and computer-readable storage medium, which can reduce the return rate of domain name access, reduce redundant storage of upper-layer nodes in the CDN network, and then Enhance the overall caching capability of the CDN network.
  • an embodiment of the present application provides an access request processing method, which is applied to a node device of a content distribution network.
  • the method includes: receiving an access request from a client for a target domain name; judging whether the node device has stored locally The data of the target domain name; and if the data of the target domain name is not stored, according to the target domain name, determine the upper-layer node that processes the access request, and process the access request through the determined upper-layer node.
  • the node device pre-stores the first association relationship between the domain name and the upper-layer node; the above-mentioned step of determining the upper-layer node processing the access request according to the target domain name includes: according to the first association relationship, determining an upper-layer node associated with the target domain name; and determining the determined upper-layer node as the upper-layer node processing the access request.
  • the above-mentioned first association relationship is pre-stored in the domain name system of the node device in the form of a server resource record;
  • the above-mentioned step of determining the upper-level node associated with the target domain name according to the first association relationship includes: : Find the server resource record associated with the target domain name from the domain name system, wherein the server resource record includes: the domain name, the IP address of the upper-layer node associated with the domain name, and the weight of the upper-layer node;
  • the server resource record determines the upper-level node associated with the target domain name.
  • the above-mentioned server resource record is generated by receiving the second association relationship between the preset domain name and the preset hash ring issued by the preset management node in the content distribution network, and the corresponding hash ring.
  • Hash ring rule wherein, the hash ring rule includes: the identity of the upper node constituting the hash ring and the weight of the upper node; and according to the second association relationship and the hash ring rule, generate the domain name corresponding to the server resource records.
  • the above-mentioned step of generating the server resource record corresponding to the domain name according to the second association relationship and the hash ring rule includes: calculating by hashing according to the second association relationship and the hash ring rule. Get the server resource record corresponding to the domain name.
  • the server resource record includes multiple domain names, and the multiple domain names are divided into at least one domain name group, and each domain name group is associated with the IP address of the same upper-layer node.
  • the weight of the upper-layer node in the above-mentioned hash ring is determined in the following manner: according to the uplink bandwidth of the upper-layer node in the hash ring, the weight of the upper-layer node is determined.
  • the above-mentioned step of determining the upper-level node associated with the target domain name according to the found server resource record includes: through a domain name resolution service, parse the found server resource record, and obtain the server resource record. and determine the node device corresponding to the IP address as the upper-layer node associated with the target domain name.
  • the above-mentioned step of processing the access request through the determined upper-layer node includes: if there are multiple determined upper-layer nodes, screening out the upper-layer node with the largest weight from the determined multiple upper-layer nodes. ; and process the access request through the filtered upper-level node.
  • the above-mentioned step of processing the access request by the determined upper-layer node includes: if it is detected that the determined upper-layer node is faulty, removing the preset association with the target domain name from the content distribution network.
  • a target upper-layer node is determined; and the access request is processed through the target upper-layer node.
  • the embodiments of the present application also provide an access request processing apparatus, which is applied to a node device of a content distribution network, the apparatus includes: an access request receiving module configured to receive an access request from a client for a target domain name; The module is set to judge whether the data of the target domain name is stored locally in the node device; and the access request processing module is set to if the data of the target domain name is not saved, according to the target domain name, determine the upper node that processes the access request, The access request is processed through the determined upper-layer node.
  • a first association relationship between a domain name and an upper node is pre-stored in the node device; the access request processing module is configured to: determine the upper node associated with the target domain name according to the first association relationship; The upper-layer node is determined as the upper-layer node that processes the access request.
  • the first association relationship is pre-stored in the domain name system of the node device in the form of a server resource record; the access request processing module is configured to search for the server resource record associated with the target domain name from the domain name system, wherein , the server resource record includes: the domain name, the IP address of the upper-layer node associated with the domain name, and the weight of the upper-layer node; according to the found server resource record, the upper-layer node associated with the target domain name is determined.
  • the above-mentioned access request processing module is set to: if there are multiple upper-layer nodes determined, filter out the upper-layer node with the largest weight from the determined multiple upper-layer nodes; process the access request through the selected upper-layer nodes. .
  • the above-mentioned access request processing module is set to: if it is detected that the determined upper-layer nodes are all faulty, the target Upper node; process the access request through the target upper node.
  • an embodiment of the present application further provides an electronic device, the electronic device includes a processor and a memory, the memory stores computer-executable instructions that can be executed by the processor, and the processor executes the computer-executable instructions In order to realize the processing method of the above access request.
  • embodiments of the present application further provide a computer-readable storage medium, where the computer-readable storage medium stores computer-executable instructions, and when the computer-executable instructions are called and executed by a processor, the computer-executable instructions The processor is prompted to implement the above-mentioned processing method for the access request.
  • FIG. 1 is a schematic flowchart of a method for processing an access request provided by an embodiment of the present application
  • FIG. 2 is a schematic flowchart of a method for processing an access request provided by an embodiment of the present application
  • FIG. 3 is a schematic diagram of the framework of a hash back-to-source system provided by an embodiment of the present application.
  • FIG. 4 is a schematic structural diagram of an apparatus for processing an access request provided by an embodiment of the present application.
  • FIG. 5 is a schematic structural diagram of an electronic device according to an embodiment of the present application.
  • Icons 41-access request receiving module; 42-judging module; 43-access request processing module; 51-processor; 52-memory; 53-bus; 54-communication interface.
  • the embodiment of the present application provides an access request processing method, device, and electronic device, the The technology can be applied in various scenarios where the content distribution network processes the access request.
  • a method for processing an access request disclosed in this embodiment of the present application is first introduced in detail.
  • FIG. 1 a schematic flowchart of a method for processing an access request provided by the present embodiment is shown, wherein the method is applied to a node device of a content distribution network. As can be seen from FIG. 1 , the method includes the following steps:
  • Step S102 Receive an access request from the client for the target domain name.
  • the above-mentioned content distribution network also known as CDN (Content Delivery Network) network
  • CDN Content Delivery Network
  • the central node server of the CDN network distributes user content to the node server.
  • the server provides content data to the user, thereby effectively solving the Internet network congestion, and improving the response speed of the user accessing the website and the usability of the website.
  • the CDN network includes many nodes, which are set to provide users with services such as caching and acceleration; nodes are usually divided into edge nodes, middle-level nodes, and upper-level nodes. Among them, nodes with different levels play different roles.
  • the edge node is set as the main access to the service domain name and caches the content of the domain name; when the content of the domain name is not cached in the edge node, it will visit the upper-level node. If the upper-level node has the domain name to cache the content, Then it directly responds to the result of the edge node. If there is no domain name cached content, it will be pulled back to the domain name origin site and cached on this node, and then responded to the edge node.
  • the node device of the above-mentioned content distribution network may be a single device, such as a cache device, or a multi-machine cluster, for example, a Linux virtual server (LVS for short), a relay device (also called Relay) , Cache cache equipment, Live equipment and other multi-machine clusters.
  • the node device is a cache server belonging to an edge node.
  • the node device receives an access request from a client for a target domain name, where the target domain name may be any domain name, such as baidu.com, abc.com, and so on.
  • Step S104 Determine whether the data of the target domain name is stored locally in the node device.
  • the content cache about the target domain name is searched locally to determine whether the data of the target domain name is stored locally. If it is not the first time that the node device receives the access request for the target domain name, it is possible that the content of the target domain name has already been cached locally, so that the access request can be responded to according to the locally cached content. If the node device receives an access request for the target domain name for the first time, the content of the target domain name may not be cached locally. At this time, it needs to pull the relevant content back to the source to cache it to the node and respond to the access request.
  • Step S106 If the data of the target domain name is not stored, determine the upper-layer node processing the access request according to the target domain name, and process the access request through the determined upper-layer node.
  • the corresponding upper-layer node can be determined according to the domain name when back-to-source is required.
  • the node device determines that the data of the target domain name is not stored locally after receiving the access request from the client, it can determine the corresponding associated upper-level node according to the target domain name, so as to process the access request through the associated node.
  • the above-mentioned node device forwards the access request to the determined upper-level node, and if the cached content of the target domain name is stored in the upper-level node, the node device directly responds; if the cached content of the target domain name is not stored; content, the upper-layer node needs to go back to the domain name source site to pull the content of the target domain name, and then cache it to the upper-layer node, and then the upper-layer node responds to the node device.
  • the association between the domain name and the back-to-source node since the association between the domain name and the back-to-source node is preset, when the content data of the target domain name requested to be accessed is not stored in the node device, the corresponding target domain name can be determined according to the target domain name.
  • the associated back-to-origin node performs back-to-origin, so that the resources related to the target domain name only need to be cached on the associated upper-level node.
  • this method does not need to poll the upper-layer nodes, which alleviates the redundant storage problem caused by caching the same resources in multiple upper-layer nodes.
  • a method for processing an access request includes receiving an access request from a client for a target domain name; judging whether the data of the target domain name is stored locally on the node device; if the data of the target domain name is not stored, according to the Target domain name, determine the upper-layer node that processes the access request, and process the access request through the determined upper-layer node.
  • This method alleviates the redundant storage problem caused by caching the same resources in multiple upper-layer nodes, saves the cache space of the upper-layer nodes, and enhances the overall caching capability of the CDN network.
  • an embodiment of the present application provides a method for processing an access request, which focuses on step S106 (determining to process the access request according to the target domain name) in the foregoing embodiment.
  • step S106 determining to process the access request according to the target domain name
  • Figure 2 shows a schematic flow chart of a method for processing an access request. The method is applied to a node device of a content distribution network, wherein the method includes the following steps:
  • Step S202 Receive an access request from the client for the target domain name.
  • Step S204 Determine whether the data of the target domain name is stored locally in the node device, wherein the node device pre-stores the first association relationship between the domain name and the upper-layer node.
  • step S202 and step S204 in this embodiment correspond to the above-mentioned step S102 and step S104, and the description of the corresponding content may refer to the above-mentioned corresponding part, which will not be repeated here.
  • Step S206 If the data of the target domain name is not stored, determine the upper-layer node associated with the target domain name according to the first association relationship.
  • the first association relationship is pre-stored in the domain name system of the node device in the form of a server resource record.
  • the above-mentioned step of determining the upper-layer node associated with the target domain name according to the first association relationship can be implemented through the following steps 11-12:
  • the server resource record includes: the domain name, the IP address of the upper-layer node associated with the domain name, and the weight of the upper-layer node.
  • Server Resource Records record the services provided by the server, and are set to describe what kind of services a server can provide.
  • a server resource record is: ⁇ baidu.com, 202.108.22.5, 0.7; cn.bing.com, 47.104.150.239, 0.3>
  • the meaning of this record is: it contains two domain names, one domain name It is baidu.com, the IP address of the upper node associated with this domain name is 202.108.22.5, and the weight of the upper node is 0.7; the other domain name is cn.bing.com, and the IP address of the upper node associated with this domain name is 47.104.150.239 , the weight of the upper node is 0.3.
  • domain names can also be divided into one or more domain name groups, and each domain name group is associated with the IP address of the same upper-layer node. Domain names of the same magnitude and similar business logic are divided into a domain name group, so as to implement the back-to-origin strategy of managing domain names by group.
  • the content of the server resource record corresponds to: the domain name group, the IP address of the upper-layer node associated with the domain name group, and the weight of the upper-layer node.
  • the above-mentioned server resource record is generated through the following steps 21-22:
  • (21) Receive the second association relationship between the preset domain name and the preset hash ring issued by the preset management node in the content distribution network, and the hash ring rule corresponding to the hash ring; wherein, the hash ring rule Including: the identity of the upper node that constitutes the hash ring, and the weight of the upper node.
  • a management node in the content distribution network may create a hash ring in advance, where the hash ring refers to storing the data to be stored in a specified storage location through a hash algorithm , and retrieve the data after finding the storage location through the same algorithm when querying.
  • a hash ring is created according to a preset hash ring rule, wherein the hash ring rule includes an identity identifier of an upper-layer node constituting the hash ring and a weight of the upper-layer node.
  • the weight of the upper-layer node may be determined according to the uplink bandwidth of the upper-layer node in the hash ring.
  • the uplink bandwidth refers to the maximum bandwidth that the node can actually use, wherein, the larger the uplink bandwidth is, the greater the weight corresponding to the node is.
  • the hash ring includes 3 upper-layer nodes, and their corresponding identities are A, B, and C, and their corresponding uplink bandwidths are 10GB/s, 25GB/s, and 15GB/s, you can set this accordingly.
  • the weights of the three nodes are: 0.2, 0.5 and 0.3.
  • the management node creates a hash ring in advance, builds a hash ring rule, and establishes a second association relationship between the hash ring and the domain name, and then sends the hash ring rule and the second association relationship to each edge system. node, so as to realize the configuration of the hash ring strategy on each node.
  • the node device obtains the server resource record corresponding to the domain name through hash calculation according to the received second association relationship and the hash ring rule, and loads the generated server resource record to the domain name of the node device in the system.
  • the found server resource record can be parsed through a domain name resolution service to obtain the IP address in the server resource record; then the node device corresponding to the IP address is determined as the upper layer associated with the target domain name. node.
  • Step S208 Determine the determined upper-layer node as the upper-layer node processing the access request, and process the access request through the determined upper-layer node.
  • the upper-level node with the largest weight can be selected from the determined multiple upper-level nodes; and the access request is processed through the selected upper-level nodes.
  • the upper-layer nodes associated with the target domain name include node A, node B, node C, and node D through the above steps S202 to S206, and the corresponding weights of the above nodes in the server resource record are: 0.2, 0.4, 0.1 and 0.3, then node B can be filtered out as the upper-level node with the largest weight, so the access request is processed through node B.
  • the upper-layer node that finally processes the access request will only be processed by one of the upper-layer nodes, thereby avoiding the situation that the access request is returned to the source by multiple upper-layer nodes .
  • the management node when the upper node in the hash rule fails or the service is overloaded, the management node will perceive the change in real time, and recalculate the hash result according to the above-mentioned second association relationship and the hash ring rule, and generate a new server resource record. And save it to the internal domain name resolution system, so as to ensure the real-time removal of faulty nodes and the protection of overloaded nodes.
  • the target upper-layer node is determined from the upper-layer nodes in the content distribution network except the upper-layer nodes preset associated with the target domain name. ; and then process the access request through the target upper node. That is, when the access request is processed through the above-mentioned hash back-to-source method, if each upper-level node in the hash ring associated with the target domain name fails, the optimal back-to-source method is triggered to ensure the client's access request. get processed.
  • the domain name is divided into multiple groups by using the hash ring algorithm.
  • the domain name group is used as a unit to return to the source upper node, the domain name of the same group is only returned to a certain node to the source, which avoids excessive resource utilization.
  • FIG. 3 it is a schematic diagram of the framework of a hash back-to-source system, wherein the system is implemented based on the processing method of the access request in the foregoing embodiment.
  • the system includes three parts: centrally controlled hash ring management, scheduling system and nodes.
  • the central control hash ring management includes: creating a hash ring, adjusting the weight value of the nodes in the hash ring, editing the rules for the edge nodes to return to the hash ring, editing the rules for returning the hash ring to the source, and issuing the hash ring rules
  • the scheduling system includes: parsing the hash ring configuration, parsing the domain name group and combining the hash ring configuration to generate the domain name srv record, adjusting the hash strategy according to the node load, providing the domain name srv record query, and regenerating the domain name srv after the faulty node removes the hash ring Record and return the processing result of the preferred back-to-source when the hash is abnormal;
  • the node part includes: querying the domain name srv record, calculating the node address of the domain name back-to-source according to the srv record through the hash algorithm, and adopting the optimal method when the hash is abnormal back to the source.
  • the scheduling system generates an internally used hash domain name srv record based on the hash ring rules issued by the node and the association between the domain name group and the hash ring, and loads the srv record into the internal domain name resolution.
  • the cache service of the node resolves the target domain name of the client's access request, it obtains the back-to-source upper node IP address corresponding to the target domain name through the internal domain name resolution system, so as to perform the back-to-source operation.
  • the above scheduling system will perceive the change in real time, recalculate the hash result and regenerate the srv record, and save the newly produced srv record to the internal domain name resolution In the system, thus ensuring the real-time removal of faulty nodes and the protection of overloaded nodes.
  • the system also supports the use of the optimal back-to-source strategy scheme.
  • the edge node when processing the access request of the client, the request for the same file can be realized, which only exists on the same node in the upper-layer node.
  • the edge node when the edge node returns to the upper-layer node, it finds the corresponding upper-layer node through hash algorithm calculation to obtain file resources.
  • the hash result will be recalculated.
  • the back-to-source is limited to the cached content involved in the upper-level node, and has no effect on the cached content of other upper-level nodes.
  • the hash back-to-source system provided by this embodiment has the same technical features as the access request processing method provided by the above-mentioned embodiment, so it can also solve the same technical problem and achieve the same technical effect.
  • an embodiment of the present application further provides an apparatus for processing an access request.
  • FIG. 4 it is a schematic structural diagram of an apparatus for processing an access request.
  • the apparatus is applied to The node equipment of the content distribution network, as can be seen from Figure 4, the device includes an access request receiving module 41, a judgment module 42 and an access request processing module 43 that are connected in sequence, wherein the functions of each module are as follows:
  • the access request receiving module 41 is set to receive the client's access request for the target domain name; the judgment module 42 is set to judge whether the local of the node device has the data of the target domain name; the access request processing module 43 is set to if not saved The data of the target domain name, according to the target domain name, determine the upper-layer node that processes the access request, and process the access request through the determined upper-layer node.
  • An access request processing apparatus receives an access request from a client for a target domain name; judges whether the data of the target domain name is stored locally in the node device; if the data of the target domain name is not stored, according to the Target domain name, determine the upper-layer node that processes the access request, and process the access request through the determined upper-layer node.
  • the corresponding back-to-source node can be determined according to the target domain name to perform back-to-source, so that only The resources related to the target domain name need to be cached on the associated upper-level node, and there is no need to poll the upper-level nodes, which effectively alleviates the redundant storage problem caused by caching the same resources in multiple upper-level nodes in the preferred back-to-source method. , which saves the cache space of upper-layer nodes and enhances the overall cache capacity of the CDN network.
  • the node device pre-stores the first association relationship between the domain name and the upper-layer node; the access request processing module 43 is further configured to: determine the upper-layer node associated with the target domain name according to the first association relationship; The determined upper-layer node is determined as the upper-layer node processing the access request.
  • the above-mentioned first association relationship is pre-stored in the domain name system of the node device in the form of a server resource record; the above-mentioned access request processing module 43 is further configured to: search the domain name system from the domain name system to be associated with the target domain name.
  • the server resource record wherein, the server resource record includes: the domain name, the IP address of the upper-layer node associated with the domain name, and the weight of the upper-layer node; According to the server resource record found, determine the upper-layer node associated with the target domain name .
  • the above-mentioned server resource record is generated by receiving the second association relationship between the preset domain name and the preset hash ring issued by the preset management node in the content distribution network, and the corresponding hash ring.
  • the hash ring rule wherein, the hash ring rule includes: the identity of the upper node constituting the hash ring and the weight of the upper node; according to the second association relationship and the hash ring rule, generate the domain name corresponding to the server resource records.
  • the above-mentioned step of generating the server resource record corresponding to the domain name according to the second association relationship and the hash ring rule includes: calculating by hashing according to the second association relationship and the hash ring rule. Get the server resource record corresponding to the domain name.
  • the server resource record includes multiple domain names, and the multiple domain names are divided into at least one domain name group, and each domain name group is associated with the IP address of the same upper-layer node.
  • the weight of the upper-layer node in the above-mentioned hash ring is determined in the following manner: according to the uplink bandwidth of the upper-layer node in the hash ring, the weight of the upper-layer node is determined.
  • the above-mentioned step of determining the upper-level node associated with the target domain name according to the found server resource record includes: through a domain name resolution service, parse the found server resource record, and obtain the server resource record.
  • the IP address; the node device corresponding to the IP address is determined as the upper-layer node associated with the target domain name.
  • the above-mentioned access request processing module 43 is further configured to: if there are multiple upper-level nodes determined, filter out the upper-level node with the largest weight from the determined multiple upper-level nodes; Process the access request.
  • the above-mentioned access request processing module 43 is further configured to: if it is detected that the determined upper-layer nodes are all faulty, remove the upper-layer nodes from the content distribution network except the upper-layer nodes preset associated with the target domain name. In the node, the target upper-layer node is determined; the access request is processed through the target upper-layer node.
  • FIG. 5 is a schematic structural diagram of the electronic device, wherein the electronic device includes a processor 51 and a memory 52 , and the memory 52 stores data that can be used by the processor 51
  • the electronic device further includes a bus 53 and a communication interface 54 , wherein the processor 51 , the communication interface 54 and the memory 52 are connected through the bus.
  • the memory 52 may include a high-speed random access memory (RAM, Random Access Memory), and may also include a non-volatile memory (non-volatile memory), such as at least one disk memory.
  • the communication connection between the network element of the system and at least one other network element is realized through at least one communication interface 54 (which may be wired or wireless), which may use the Internet, a wide area network, a local network, a metropolitan area network, and the like.
  • the bus can be an ISA bus, a PCI bus, an EISA bus, or the like.
  • the bus can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only one bidirectional arrow is shown in FIG. 5, but it does not mean that there is only one bus or one type of bus.
  • the processor 51 may be an integrated circuit chip with signal processing capability. In the implementation process, each step of the above-mentioned method can be completed by a hardware integrated logic circuit in the processor 51 or an instruction in the form of software.
  • the above-mentioned processor 51 can be a general-purpose processor, including a central processing unit (Central Processing Unit, referred to as CPU), a network processor (Network Processor, referred to as NP), etc.; it can also be a digital signal processor (Digital Signal Processing, referred to as DSP) ), Application Specific Integrated Circuit (ASIC), Field-Programmable Gate Array (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, and discrete hardware components.
  • CPU Central Processing Unit
  • NP Network Processor
  • DSP Digital Signal Processing
  • ASIC Application Specific Integrated Circuit
  • FPGA Field-Programmable Gate Array
  • a general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
  • the steps of the method disclosed in conjunction with the embodiments of the present application may be directly embodied as executed by a hardware decoding processor, or executed by a combination of hardware and software modules in the decoding processor.
  • the software modules may be located in random access memory, flash memory, read-only memory, programmable read-only memory or electrically erasable programmable memory, registers and other storage media mature in the art.
  • the storage medium is located in the memory, and the processor 51 reads the information in the memory 52, and completes the steps of the access request processing method in the foregoing embodiment in combination with its hardware.
  • Embodiments of the present application further provide a computer-readable storage medium, where machine-executable instructions are stored in the computer-readable storage medium, and when the machine-executable instructions are invoked and executed by a processor, the machine-executable instructions cause the processor to
  • machine-executable instructions are stored in the computer-readable storage medium, and when the machine-executable instructions are invoked and executed by a processor, the machine-executable instructions cause the processor to
  • the method for processing an access request, an apparatus for processing an access request, and a computer program product of an electronic device provided by the embodiments of the present application include a computer-readable storage medium storing program codes, and the instructions included in the program codes can be configured to execute the preceding steps.
  • the specific implementation can refer to the method embodiment, which will not be repeated here.
  • the functions, if implemented in the form of software functional units and sold or used as stand-alone products, may be stored in a processor-executable non-volatile computer-readable storage medium.
  • the technical solution of the present application can be embodied in the form of a software product in essence, or the part that contributes to the related technology or the part of the technical solution.
  • the computer software product is stored in a storage medium, including several
  • the instructions are used to cause a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present application.
  • the aforementioned storage medium includes: U disk, mobile hard disk, Read-Only Memory (ROM, Read-Only Memory), Random Access Memory (RAM, Random Access Memory), magnetic disk or optical disk and other media that can store program codes .
  • the access request processing method, device, electronic device, and computer-readable storage medium provided by the embodiments of the present application receive an access request from a client for a target domain name; determine whether the node device locally stores the data of the target domain name; if not The data of the target domain name is saved, the upper-layer node processing the access request is determined according to the target domain name, and the access request is processed through the determined upper-layer node.
  • the corresponding back-to-source node can be determined according to the target domain name to perform back-to-source, so that only The resources of the target domain name need to be cached on the associated upper-layer node, and there is no need to poll the upper-layer node, which effectively alleviates the redundant storage problem caused by caching the same resources in multiple upper-layer nodes in the preferred back-to-source method. It saves the cache space of the upper node and enhances the overall cache capacity of the CDN network.
  • the terms “installed”, “connected” and “connected” should be understood in a broad sense, for example, it may be a fixed connection or a detachable connection , or integrally connected; it can be a mechanical connection or an electrical connection; it can be a direct connection, or an indirect connection through an intermediate medium, or the internal communication between the two components.
  • installed should be understood in a broad sense, for example, it may be a fixed connection or a detachable connection , or integrally connected; it can be a mechanical connection or an electrical connection; it can be a direct connection, or an indirect connection through an intermediate medium, or the internal communication between the two components.
  • the present application can be applied to the field of Internet technology, and provides an access request processing method, device, electronic device and computer-readable storage medium, which can reduce the return rate of domain name access, reduce redundant storage of upper-layer nodes in the CDN network, and further Enhance the overall caching capability of the CDN network.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Information Transfer Between Computers (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

本申请提供了一种访问请求的处理方法、装置、电子设备及计算机可读存储介质，涉及互联网技术领域，该方法包括接收客户端针对目标域名的访问请求；判断该节点设备的本地是否保存有该目标域名的数据；如果没有保存目标域名的数据，根据该目标域名，确定处理该访问请求的上层节点，通过确定出的上层节点处理该访问请求。本申请实施例通过预先设置域名和回源节点的关联关系，当节点设备中没有保存请求访问的目标域名的内容数据时，可以根据该目标域名确定对应关联的回源节点进行回源，从而只需要将与该目标域名的资源缓存到该关联的上层节点上，有效缓解了择优回源方式因在多个上层节点中缓存相同的资源而造成的冗余存储问题，增强了CDN网络的整体缓存能力。

Description

访问请求的处理方法、装置、电子设备及计算机可读存储介质
相关申请的交叉引用
本申请要求于2020年09月30日提交中国专利局的申请号为202011069197.6、名称为“访问请求的处理方法、装置及电子设备”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及互联网技术领域，尤其是涉及一种访问请求的处理方法、装置、电子设备及计算机可读存储介质。
背景技术
通常情况下，内容分发网络(Content Delivery Network，CDN)节点划分为边缘节点和上层节点两种层级，不同层级的节点发挥的作用不同。其中，边缘节点用来服务用户对域名的访问，并缓存域名的内容。当边缘节点内没有访问请求对应域名的内容缓存时，边缘节点会访问其对应的上层节点，如果上层节点有该域名的缓存内容则会直接响应边缘节点，如果没有该域名的缓存内容，则上层节点将回域名源站拉取对应的缓存内容，然后将其缓存到本节点上，再响应给边缘节点。
目前，相关的CDN节点回源方式，例如择优回源，因为边缘节点在回源上层节点时不区分域名，而是通过探测上层节点的连通性，并采用轮询轮训的方式择优回源，这种方式会导致多个上层节点同时缓存相同资源，而如果这多个上层节点的缓存中没有所需资源，则它们都将回源站拉取资源，进而导致域名访问的回源率较高，并造成上层节点冗余存储，降低内容分发网络的整体缓存能力。
整体而言，相关的CDN节点回源方式还存在域名访问的回源率较高、上层节点冗余存储较为严重，以及内容分发网络的整体缓存能力较弱的问题。
发明内容
有鉴于此，本申请的目的在于提供一种访问请求的处理方法、装置、电子设备及计算机可读存储介质，可以降低域名访问的回源率，减少CDN网络中上层节点的冗余存储，进而增强CDN网络的整体缓存能力。
第一方面，本申请实施例提供了一种访问请求的处理方法，应用于内容分发网络的节点设备，该方法包括：接收客户端针对目标域名的访问请求；判断该节点设备的本地是否 保存有该目标域名的数据；以及如果没有保存该目标域名的数据，根据该目标域名，确定处理该访问请求的上层节点，通过确定出的上层节点处理该访问请求。
在一实施方式中，该节点设备中预先保存有域名和上层节点的第一关联关系；上述根据该目标域名，确定处理该访问请求的上层节点的步骤，包括：根据该第一关联关系，确定与该目标域名关联的上层节点；以及将确定出的该上层节点确定为处理该访问请求的上层节点。
在一实施方式中，上述第一关联关系以服务器资源记录的形式，预先保存在该节点设备的域名系统中；上述根据该第一关联关系，确定与该目标域名关联的上层节点的步骤，包括：从该域名系统中查找与该目标域名关联的服务器资源记录，其中，该服务器资源记录包括：域名、与该域名关联的上层节点的IP地址以及该上层节点的权重；以及根据查找到的该服务器资源记录，确定与该目标域名关联的上层节点。
在一实施方式中，上述服务器资源记录通过下述方式生成：接收该内容分发网络中预设管理节点下发的预设域名与预设哈希环的第二关联关系以及该哈希环对应的哈希环规则，其中，该哈希环规则包括：构成该哈希环的上层节点的身份标识以及该上层节点的权重；以及根据该第二关联关系和该哈希环规则，生成该域名对应的服务器资源记录。
在一实施方式中，上述根据该第二关联关系和该哈希环规则，生成该域名对应的服务器资源记录的步骤，包括：根据该第二关联关系和该哈希环规则，通过哈希计算得到该域名对应的服务器资源记录。
在一实施方式中，上述服务器资源记录中有多个域名，且该多个域名被划分为至少一个域名组，每个域名组关联同一上层节点的IP地址。
在一实施方式中，上述哈希环中上层节点的权重通过下述方式确定：根据该哈希环中上层节点的上联带宽，确定该上层节点的权重。
在一实施方式中，上述根据查找到的该服务器资源记录，确定与该目标域名关联的上层节点的步骤，包括：通过域名解析服务，解析查找到的该服务器资源记录，得到该服务器资源记录中的IP地址；以及将该IP地址对应的节点设备，确定为与该目标域名关联的上层节点。
在一实施方式中，上述通过确定出的该上层节点处理该访问请求的步骤，包括：如果确定出的该上层节点有多个，从确定出的多个上层节点中筛选出权重最大的上层节点；以及通过筛选出的上层节点处理该访问请求。
在一实施方式中，上述通过确定出的该上层节点处理该访问请求的步骤，包括：如果检测到确定出的该上层节点均出现故障，从该内容分发网络中除预设与该目标域名关联的上层节点之外的上层节点中，确定目标上层节点；以及通过该目标上层节点处理该访问请 求。
第二方面，本申请实施例还提供了一种访问请求的处理装置，应用于内容分发网络的节点设备，该装置包括：访问请求接收模块，设置为接收客户端针对目标域名的访问请求；判断模块，设置为判断该节点设备的本地是否保存有该目标域名的数据；以及访问请求处理模块，设置为如果没有保存该目标域名的数据，根据该目标域名，确定处理该访问请求的上层节点，通过确定出的该上层节点处理该访问请求。
在一实施方式中，上述节点设备中预先保存有域名和上层节点的第一关联关系；上述访问请求处理模块设置为：根据第一关联关系，确定与目标域名关联的上层节点；将确定出的上层节点确定为处理所述访问请求的上层节点。
在一实施方式中，第一关联关系以服务器资源记录的形式，预先保存在节点设备的域名系统中；上述访问请求处理模块设置为：从域名系统中查找与目标域名关联的服务器资源记录，其中，服务器资源记录包括：域名、与域名关联的上层节点的IP地址以及上层节点的权重；根据查找到的服务器资源记录，确定与目标域名关联的上层节点。
在一实施方式中，上述访问请求处理模块设置为：如果确定出的上层节点有多个，从确定出的多个上层节点中筛选出权重最大的上层节点；通过筛选出的上层节点处理访问请求。
在一实施方式中，上述访问请求处理模块设置为：如果检测到确定出的上层节点均出现故障，从内容分发网络中除预设与目标域名关联的上层节点之外的上层节点中，确定目标上层节点；通过目标上层节点处理该访问请求。
第三方面，本申请实施例还提供了一种电子设备，该电子设备包括处理器和存储器，该存储器存储有能够被该处理器执行的计算机可执行指令，该处理器执行该计算机可执行指令以实现上述访问请求的处理方法。
第四方面，本申请实施例还提供了一种计算机可读存储介质，该计算机可读存储介质存储有计算机可执行指令，该计算机可执行指令在被处理器调用和执行时，计算机可执行指令促使处理器实现上述访问请求的处理方法。
本申请的其他特征和优点将在随后的说明书中阐述，或者，部分特征和优点可以从说明书推知或毫无疑义地确定，或者通过实施本申请的上述技术即可得知。
为使本申请的上述目的、特征和优点能更明显易懂，下文特举较佳实施例，并配合所附附图，作详细说明如下。
附图说明
为了更清楚地说明本申请具体实施方式或相关技术中的技术方案，下面将对具体实施 方式或相关技术描述中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图是本申请的一些实施方式，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其他的附图。
图1为本申请实施例提供的一种访问请求的处理方法的流程示意图；
图2为本申请实施例提供的一种访问请求的处理方法的流程示意图；
图3为本申请实施例提供的一种哈希回源系统框架示意图；
图4为本申请实施例提供的一种访问请求的处理装置的结构示意图；
图5为本申请实施例提供的一种电子设备的结构示意图。
图标：41-访问请求接收模块；42-判断模块；43-访问请求处理模块；51-处理器；52-存储器；53-总线；54-通信接口。
具体实施方式
为使本申请实施例的目的、技术方案和优点更加清楚，下面将结合附图对本申请的技术方案进行清楚、完整地描述，显然，所描述的实施例是本申请一部分实施例，而不是全部的实施例。基于本申请中的实施例，本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例，都属于本申请保护的范围。
考虑到相关的CDN节点回源方式还存在域名访问的回源率较高、上层节点冗余存储较为严重的问题，本申请实施例提供的一种访问请求的处理方法、装置及电子设备，该技术可以应用于内容分发网络对访问请求进行处理的各种场景中。为便于对本实施例进行理解，首先对本申请实施例所公开的一种访问请求的处理方法进行详细介绍。
参见图1，所示为本实施例提供的一种访问请求的处理方法的流程示意图，其中，该方法应用于内容分发网络的节点设备，由图1可见，该方法包括下述步骤：
步骤S102：接收客户端针对目标域名的访问请求。
这里，上述内容分发网络，也即CDN(Content Delivery Network)网络，其是由分布在不同区域的节点服务器集群组成的分布式网络，CDN网络的中心节点服务器将用户内容分发到节点服务器，通过节点服务器向用户提供内容数据，从而有效解决互联网网络拥塞状况，提高用户访问网站的响应速度与网站的可用性。CDN网络中包括很多节点，设置为向用户提供缓存与加速等服务；节点通常划分为边缘节点、中层节点、上层节点等。其中，层级不同的节点发挥的作用不同，边缘节点设置为服务域名的主要访问，缓存域名的内容；当边缘节点内没有域名的内容缓存时，会访问上层节点，上层节点如果有域名缓存内容，则直接响应边缘节点结果，如果没有域名缓存内容，则回域名源站拉取后缓存到本节点上，再响应给边缘节点。
在本实施例中，上述内容分发网络的节点设备可以是单台设备，例如Cache缓存设备；也可以是多机集群，例如，由Linux虚拟服务器(简称LVS)、中继设备(也称Relay)、Cache缓存设备、Live设备等构成的多机集群。在一实施方式中，该节点设备是属于边缘节点的缓存服务器。在本实施例中，节点设备接收客户端针对目标域名的访问请求，其中，该目标域名可以是任意域名，例如：baidu.com、abc.com等等。
步骤S104：判断该节点设备的本地是否保存有该目标域名的数据。
从本地查找关于该目标域名的内容缓存，以判断本地是否保存有该目标域名的数据。如果该节点设备不是第一次接收到针对该目标域名的访问请求，则有可能在本地已经缓存有该目标域名的内容，从而可以根据本地缓存的内容响应该访问请求。若是该节点设备第一次接收到针对该目标域名的访问请求，则可能本地未缓存该目标域名的内容，此时需要回源拉取相关内容以缓存到本节点，并响应该访问请求。
步骤S106：如果没有保存该目标域名的数据，根据该目标域名，确定处理该访问请求的上层节点，通过确定出的上层节点处理该访问请求。
这里，通过预先建立域名与上层节点的关联关系，从而可以在需要回源时根据域名确定对应的上层节点。在本实施例中，如果节点设备接收到客户端的访问请求后，判断本地未保存该目标域名的数据，则可以根据该目标域名确定对应关联的上层节点，以通过该关联节点处理该访问请求。在一实施方式中，由上述节点设备将访问请求转发至确定出的上层节点，该上层节点中如果存储有该目标域名的缓存内容，则直接响应该节点设备；如果没有存储该目标域名的缓存内容，则需该上层节点回域名源站拉取该目标域名的内容后缓存到该上层节点，再由该上层节点响应该节点设备。
这样，通过本实施例提供的访问请求的处理方法，由于预先设置了域名和回源节点的关联关系，当节点设备中没有保存请求访问的目标域名的内容数据时，可以根据该目标域名确定对应关联的回源节点进行回源，从而只需要将与该目标域名的资源缓存到该关联的上层节点上。相比于相关技术中的择优回源方式，本方式不需要对上层节点进行轮询，缓解了在多个上层节点中缓存相同的资源而造成的冗余存储问题。
本申请实施例提供的一种访问请求的处理方法，接收客户端针对目标域名的访问请求；判断该节点设备的本地是否保存有该目标域名的数据；如果没有保存该目标域名的数据，根据该目标域名，确定处理该访问请求的上层节点，通过确定出的上层节点处理该访问请求。该方式缓解了在多个上层节点中缓存相同的资源而造成的冗余存储问题，节省了上层节点的缓存空间，增强了CDN网络的整体缓存能力。
在图1所示访问请求的处理方法的基础上，本申请实施例提供了一种访问请求的处理方法，该方法重点描述了前述实施例中步骤S106(根据该目标域名，确定处理该访问请求 的上层节点)的具体实现过程。
在图2中示出一种访问请求的处理方法的流程示意图，该方法应用于内容分发网络的节点设备，其中，该方法包括以下步骤：
步骤S202：接收客户端针对目标域名的访问请求。
步骤S204：判断该节点设备的本地是否保存有该目标域名的数据，其中，该节点设备中预先保存有域名和上层节点的第一关联关系。
这里，本实施例中的步骤S202和步骤S204，对应上述的步骤S102和步骤S104，相应内容的描述可以参考前述的对应部分，在此不再赘述。
步骤S206：如果没有保存该目标域名的数据，根据该第一关联关系，确定与该目标域名关联的上层节点。
在一实施方式中，该第一关联关系以服务器资源记录的形式，预先保存在该节点设备的域名系统中。并且，上述根据该第一关联关系，确定与该目标域名关联的上层节点的步骤可以通过下述步骤11-12实现：
(11)从该域名系统中查找与该目标域名关联的服务器资源记录；其中，该服务器资源记录包括：域名、与该域名关联的上层节点的IP地址以及该上层节点的权重。
这里，服务器资源记录(Server Resource Records，SRV)是记录服务器提供的服务，设置为说明一个服务器能够提供什么样的服务。例如，假设一条服务器资源记录为：<baidu.com,202.108.22.5，0.7；cn.bing.com，47.104.150.239，0.3>，则该条记录表达的含义为：其包含两个域名，一个域名为baidu.com，该域名关联的上层节点的IP地址为202.108.22.5，该上层节点的权重为0.7；另一个域名为cn.bing.com，该域名关联的上层节点的IP地址为47.104.150.239，该上层节点的权重为0.3。
在实际操作中，如果上述服务器资源记录中的域名有多个，还可以将这些域名划分为一个或多个域名组，并且，每个域名组关联同一上层节点的IP地址，其中，可以将具有相同量级、业务逻辑相似的域名划分为一个域名组，从而实现以组为单位管理域名的回源策略。这样，服务器资源记录的内容对应为：域名组，与该域名组关联的上层节点的IP地址，以及该上层节点的权重。
在一实施方式中，上述服务器资源记录通过下述步骤21-22生成：
(21)接收该内容分发网络中预设管理节点下发的预设域名与预设哈希环的第二关联关系，以及该哈希环对应的哈希环规则；其中，该哈希环规则包括：构成该哈希环的上层节点的身份标识，以及该上层节点的权重。
在实际操作中，可以由内容分发网络中的管理节点，例如管理服务器，预先创建哈希(hash)环，其中，该哈希环是指通过hash算法将需要存储的数据存放到指定的存储位置， 在查询时通过同样的算法，找到存储位置后取出该数据。这里，根据预设的哈希环规则创建哈希环，其中，该哈希环规则包括构成该哈希环的上层节点的身份标识和该上层节点的权重。
在一实施方式中，可以根据该哈希环中上层节点的上联带宽，确定该上层节点的权重。这里，上联带宽是指该节点实际可以使用的最大带宽，其中，上联带宽越大则对应该节点的权重也越大。例如，假设该哈希环中包括3个上层节点，各自对应的身份标识为A、B和C，分别对应的上联带宽为10GB/s、25GB/s和15GB/s，则可以对应设置这三个节点的权重为:0.2、0.5和0.3。
这样，由管理节点预先创建哈希环，并构建哈希环规则，以及建立哈希环与域名的第二关联关系，再将该哈希环规则以及该第二关联关系统一下发至各个边缘节点，从而实现哈希环策略在各个节点上的配置。
(22)根据该第二关联关系和该哈希环规则，生成该域名对应的服务器资源记录。
在本实施例中，节点设备根据接收到的该第二关联关系和该哈希环规则，通过哈希计算得到该域名对应的服务器资源记录，并将生成的服务器资源记录加载到节点设备的域名系统中。
(12)根据查找到的该服务器资源记录，确定与该目标域名关联的上层节点。
在一实施方式中，可以先通过域名解析服务解析查找到的该服务器资源记录，得到该服务器资源记录中的IP地址；然后将该IP地址对应的节点设备，确定为与该目标域名关联的上层节点。
步骤S208：将确定出的该上层节点确定为处理该访问请求的上层节点，通过确定出的上层节点处理该访问请求。
在实际操作中，假设确定出的该上层节点有多个，则可以从确定出的多个上层节点中筛选出权重最大的上层节点；并通过筛选出的上层节点处理该访问请求。
例如，假设通过上述步骤S202至S206确定出与该目标域名关联的上层节点包括节点A、节点B、节点C和节点D，并且，上述各个节点在服务器资源记录中对应的权重分别为：0.2、0.4、0.1和0.3，则可筛选出节点B为其中权重最大的上层节点，因而通过节点B处理该访问请求。这样，即使与目标域名关联的上层节点有多个时，最终处理该访问请求的上层节点只会由其中的一个上层节点进行处理，从而避免了针对该访问请求由多个上层节点回源的情况。
此外，当哈希规则内的上层节点出现故障或者过载服务时，管理节点会实时感知到变化，并根据上述第二关联关系和哈希环规则重新计算哈希结果，生成新的服务器资源记录，并保存到内部域名解析系统内，从而可以保证故障节点的实时摘除和过载节点的保护。
在一实施方式中，如果节点设备检测到确定出的该上层节点均出现故障，则从该内容分发网络中除预设与该目标域名关联的上层节点之外的上层节点中，确定目标上层节点；然后通过该目标上层节点处理该访问请求。也即，当通过上述哈希回源的方式处理访问请求时，如果因与目标域名关联的哈希环中的各个上层节点都出现故障，则触发择优回源的方式，以保证客户端的访问请求得到处理。
本实施例提供的访问请求的处理方法，通过哈希环算法将域名分成多组，以域名组为单位在回源上层节点时，同一组的域名只回源某个节点，避免了资源在多个上层节点的大量冗余，从而提升了上层节点的整体缓存容量，减少了域名的源站回源率。
为了更清楚理解前述实施例提供的访问请求的处理方法，下面介绍一个应用实例。
参见图3，其为一种哈希回源系统框架示意图，其中，该系统基于前述实施例中的访问请求的处理方法得以实现。在图3示出的实施方式中，该系统包括三个部分：中控哈希环管理、调度系统和节点。其中，中控哈希环管理包括：创建哈希环、调整哈希环中节点的权重值、编辑边缘节点回哈希环的规则、编辑哈希环回源规则、以及下发哈希环规则；调度系统包括：解析哈希环配置、解析域名组并结合哈希环配置生成域名srv记录、根据节点负载调整哈希策略、提供域名srv记录查询、故障节点摘除哈希环后重新生成域名srv记录、以及哈希异常时返回择优回源的处理结果；节点部分包括：查询域名srv记录、根据srv记录通过哈希算法计算得出域名回源的节点地址、以及当哈希异常时采用择优方式回源。
在实际操作中，图3所示系统中哈希环的具体实现以及操作如下：
首先通过中控产品化页面创建哈希环，创建时需要定义哈希环包括的节点以及各个节点的权重，其中，各节点的权重可按节点的上联带宽粗略配比。创建好哈希环后，通过编辑节点回源拓扑，将哈希环加入拓扑内，然后下发拓扑配置至各个节点，此时即完成了哈希环策略在节点上的配置。
然后，调度系统通过节点上下发的哈希环规则以及域名组与哈希环的关联，生成内部使用的哈希域名srv记录，并将此srv记录加载到内部的域名解析内。
最后，当节点的cache服务在解析客户端访问请求的目标域名时，通过内部的域名解析系统获取到该目标域名对应的回源上层节点IP地址，从而进行回源操作。
其中，当哈希规则内的节点出现故障或者过载服务时，上述调度系统会实时感知到变化，同时重新计算哈希结果并重新生成srv记录，且将该新生产的srv记录保存到内部域名解析系统内，从而保证了故障节点的实时摘除和过载节点的保护。此外，为了避免哈希环系统故障，系统同时还支持使用择优回源策略方案。
这样，通过本实施例中的哈希回源系统，在处理客户端的访问请求时，可以实现对于同一文件的请求，在上层节点内只存在于同一节点上。其中，边缘节点在回源上层节点时， 通过哈希算法计算找到对应的上层节点以获取文件资源，当该存储文件的上层节点发生故障时，将会重新计算哈希结果，从而故障带来的回源只限于该上层节点所涉及的缓存内容，对于其他上层节点缓存的内容无影响。
本实施例提供的哈希回源系统，与上述实施例提供的访问请求的处理方法具有相同的技术特征，所以也能解决相同的技术问题，达到相同的技术效果。
对应于图1中所示的访问请求的处理方法，本申请实施例还提供了一种访问请求的处理装置，参见图4，其为一种访问请求的处理装置的结构示意图，该装置应用于内容分发网络的节点设备，由图4可见，该装置包括依次相连的访问请求接收模块41、判断模块42和访问请求处理模块43，其中，各个模块的功能如下：
访问请求接收模块41，设置为接收客户端针对目标域名的访问请求；判断模块42，设置为判断该节点设备的本地是否保存有该目标域名的数据；访问请求处理模块43，设置为如果没有保存该目标域名的数据，根据该目标域名，确定处理该访问请求的上层节点，通过确定出的该上层节点处理该访问请求。
本申请实施例提供的一种访问请求的处理装置，接收客户端针对目标域名的访问请求；判断该节点设备的本地是否保存有该目标域名的数据；如果没有保存该目标域名的数据，根据该目标域名，确定处理该访问请求的上层节点，通过确定出的上层节点处理该访问请求。该装置中，通过预先设置域名和回源节点的关联关系，当节点设备中没有保存请求访问的目标域名的内容数据时，可以根据该目标域名确定对应关联的回源节点进行回源，从而只需要将与该目标域名的资源缓存到该关联的上层节点上，无需对上层节点进行轮询，有效缓解了择优回源方式因在多个上层节点中缓存相同的资源而造成的冗余存储问题，节省了上层节点的缓存空间，增强了CDN网络的整体缓存能力。
在一实施方式中，该节点设备中预先保存有域名和上层节点的第一关联关系；上述访问请求处理模块43还设置为：根据该第一关联关系，确定与该目标域名关联的上层节点；将确定出的该上层节点确定为处理该访问请求的上层节点。
在一实施方式中，上述第一关联关系以服务器资源记录的形式，预先保存在该节点设备的域名系统中；上述访问请求处理模块43还设置为：从该域名系统中查找与该目标域名关联的服务器资源记录；其中，该服务器资源记录包括：域名、与该域名关联的上层节点的IP地址以及该上层节点的权重；根据查找到的该服务器资源记录，确定与该目标域名关联的上层节点。
在一实施方式中，上述服务器资源记录通过下述方式生成：接收该内容分发网络中预设管理节点下发的预设域名与预设哈希环的第二关联关系，以及该哈希环对应的哈希环规则；其中，该哈希环规则包括：构成该哈希环的上层节点的身份标识以及该上层节点的权 重；根据该第二关联关系和该哈希环规则，生成该域名对应的服务器资源记录。
在一实施方式中，上述根据该第二关联关系和该哈希环规则，生成该域名对应的服务器资源记录的步骤，包括：根据该第二关联关系和该哈希环规则，通过哈希计算得到该域名对应的服务器资源记录。
在一实施方式中，上述服务器资源记录中有多个域名，且该多个域名被划分为至少一个域名组，每个域名组关联同一上层节点的IP地址。
在一实施方式中，上述哈希环中上层节点的权重通过下述方式确定：根据该哈希环中上层节点的上联带宽，确定该上层节点的权重。
在一实施方式中，上述根据查找到的该服务器资源记录，确定与该目标域名关联的上层节点的步骤，包括：通过域名解析服务，解析查找到的该服务器资源记录，得到该服务器资源记录中的IP地址；将该IP地址对应的节点设备，确定为与该目标域名关联的上层节点。
在一实施方式中，上述访问请求处理模块43还设置为：如果确定出的该上层节点有多个，从确定出的多个上层节点中筛选出权重最大的上层节点；通过筛选出的上层节点处理该访问请求。
在一实施方式中，上述访问请求处理模块43还设置为：如果检测到确定出的该上层节点均出现故障，从该内容分发网络中除预设与该目标域名关联的上层节点之外的上层节点中，确定目标上层节点；通过该目标上层节点处理该访问请求。
本申请实施例提供的访问请求的处理装置，其实现原理及产生的技术效果和前述访问请求的处理方法实施例相同，为简要描述，访问请求的处理装置的实施例部分未提及之处，可参考前述访问请求的处理方法实施例中相应内容。
本申请实施例还提供了一种电子设备，如图5所示，为该电子设备的结构示意图，其中，该电子设备包括处理器51和存储器52，该存储器52存储有能够被该处理器51执行的机器可执行指令，该处理器51执行该机器可执行指令以实现上述访问请求的处理方法。
在图5示出的实施方式中，该电子设备还包括总线53和通信接口54，其中，处理器51、通信接口54和存储器52通过总线连接。
其中，存储器52可能包含高速随机存取存储器(RAM，Random Access Memory)，也可能还包括非不稳定的存储器(non-volatile memory)，例如至少一个磁盘存储器。通过至少一个通信接口54(可以是有线或者无线)实现该系统网元与至少一个其他网元之间的通信连接，可以使用互联网、广域网、本地网、城域网等。总线可以是ISA总线、PCI总线或EISA总线等。所述总线可以分为地址总线、数据总线、控制总线等。为便于表示，图5中仅用一个双向箭头表示，但并不表示仅有一根总线或一种类型的总线。
处理器51可能是一种集成电路芯片，具有信号的处理能力。在实现过程中，上述方法的各步骤可以通过处理器51中的硬件的集成逻辑电路或者软件形式的指令完成。上述的处理器51可以是通用处理器，包括中央处理器(Central Processing Unit，简称CPU)、网络处理器(Network Processor，简称NP)等；还可以是数字信号处理器(Digital Signal Processing，简称DSP)、专用集成电路(Application Specific Integrated Circuit，简称ASIC)、现成可编程门阵列(Field-Programmable Gate Array，简称FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件。可以实现或者执行本申请实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。结合本申请实施例所公开的方法的步骤可以直接体现为硬件译码处理器执行完成，或者用译码处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器，闪存、只读存储器，可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器，处理器51读取存储器52中的信息，结合其硬件完成前述实施例的访问请求的处理方法的步骤。
本申请实施例还提供了一种计算机可读存储介质，该计算机可读存储介质存储有机器可执行指令，该机器可执行指令在被处理器调用和执行时，该机器可执行指令促使处理器实现上述访问请求的处理方法，具体实现可参见前述方法实施例，在此不再赘述。
本申请实施例所提供的访问请求的处理方法、访问请求的处理装置和电子设备的计算机程序产品，包括存储了程序代码的计算机可读存储介质，所述程序代码包括的指令可设置为执行前面方法实施例中所述的访问请求的处理方法，具体实现可参见方法实施例，在此不再赘述。
所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个处理器可执行的非易失的计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对相关技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(ROM，Read-Only Memory)、随机存取存储器(RAM，Random Access Memory)、磁碟或者光盘等各种可以存储程序代码的介质。
本申请实施例提供的访问请求的处理方法、装置、电子设备及计算机可读存储介质，接收客户端针对目标域名的访问请求；判断该节点设备的本地是否保存有该目标域名的数据；如果没有保存该目标域名的数据，根据该目标域名，确定处理该访问请求的上层节点，通过确定出的上层节点处理该访问请求。该方式中，通过预先设置域名和回源节点的关联 关系，当节点设备中没有保存请求访问的目标域名的内容数据时，可以根据该目标域名确定对应关联的回源节点进行回源，从而只需要将该目标域名的资源缓存到该关联的上层节点上，无需对上层节点进行轮询，有效缓解了择优回源方式因在多个上层节点中缓存相同的资源而造成的冗余存储问题，节省了上层节点的缓存空间，增强了CDN网络的整体缓存能力。
另外，在本申请实施例的描述中，除非另有明确的规定和限定，术语“安装”、“相连”、“连接”应做广义理解，例如，可以是固定连接，也可以是可拆卸连接，或一体地连接；可以是机械连接，也可以是电连接；可以是直接相连，也可以通过中间媒介间接相连，可以是两个元件内部的连通。对于本领域的普通技术人员而言，可以具体情况理解上述术语在本申请中的具体含义。
在本申请的描述中，需要说明的是，术语“中心”、“上”、“下”、“左”、“右”、“竖直”、“水平”、“内”、“外”等指示的方位或位置关系为基于附图所示的方位或位置关系，仅是为了便于描述本申请和简化描述，而不是指示或暗示所指的装置或元件必须具有特定的方位、以特定的方位构造和操作，因此不能理解为对本申请的限制。此外，术语“第一”、“第二”、“第三”仅用于描述目的，而不能理解为指示或暗示相对重要性。
最后应说明的是：以上所述实施例，仅为本申请的具体实施方式，用以说明本申请的技术方案，而非对其限制，本申请的保护范围并不局限于此，尽管参照前述实施例对本申请进行了详细的说明，本领域的普通技术人员应当理解：任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，其依然可以对前述实施例所记载的技术方案进行修改或可轻易想到变化，或者对其中部分技术特征进行等同替换；而这些修改、变化或者替换，并不使相应技术方案的本质脱离本申请实施例技术方案的精神和范围，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以所述权利要求的保护范围为准。
工业实用性
本申请能够应用于互联网技术领域，提供一种访问请求的处理方法、装置、电子设备及计算机可读存储介质，可以降低域名访问的回源率，减少CDN网络中上层节点的冗余存储，进而增强CDN网络的整体缓存能力。

Claims (17)

  1. 一种访问请求的处理方法，应用于内容分发网络的节点设备，所述方法包括：
    接收客户端针对目标域名的访问请求；
    判断所述节点设备的本地是否保存有所述目标域名的数据；以及
    如果没有保存所述目标域名的数据，根据所述目标域名，确定处理所述访问请求的上层节点，通过确定出的所述上层节点处理所述访问请求。
  2. 根据权利要求1所述的访问请求的处理方法，其中，所述节点设备中预先保存有域名和上层节点的第一关联关系；
    所述根据所述目标域名，确定处理所述访问请求的上层节点的步骤，包括：
    根据所述第一关联关系，确定与所述目标域名关联的上层节点；以及
    将确定出的所述上层节点确定为处理所述访问请求的上层节点。
  3. 根据权利要求2所述的访问请求的处理方法，其中，所述第一关联关系以服务器资源记录的形式，预先保存在所述节点设备的域名系统中；
    所述根据所述第一关联关系，确定与所述目标域名关联的上层节点的步骤，包括：
    从所述域名系统中查找与所述目标域名关联的服务器资源记录，其中，所述服务器资源记录包括：域名、与所述域名关联的上层节点的IP地址以及该上层节点的权重；以及
    根据查找到的所述服务器资源记录，确定与所述目标域名关联的上层节点。
  4. 根据权利要求3所述的访问请求的处理方法，其中，所述服务器资源记录通过下述方式生成：
    接收所述内容分发网络中预设管理节点下发的预设域名与预设哈希环的第二关联关系以及所述哈希环对应的哈希环规则，其中，所述哈希环规则包括：构成所述哈希环的上层节点的身份标识以及该上层节点的权重；以及
    根据所述第二关联关系和所述哈希环规则，生成所述域名对应的服务器资源记录。
  5. 根据权利要求4所述的访问请求的处理方法，其中，所述根据所述第二关联关系和所述哈希环规则，生成所述域名对应的服务器资源记录的步骤，包括：
    根据所述第二关联关系和所述哈希环规则，通过哈希计算得到所述域名对应的服务器资源记录。
  6. 根据权利要求3-5中任一项所述的访问请求的处理方法，其中，所述服务器资源记录中有多个域名，且所述多个域名被划分为至少一个域名组，每个所述域名组关联同一上层节点的IP地址。
  7. 根据权利要求4所述的访问请求的处理方法，其中，所述哈希环中上层节点的权重通过下述方式确定：
    根据所述哈希环中上层节点的上联带宽，确定该上层节点的权重。
  8. 根据权利要求3所述的访问请求的处理方法，其中，所述根据查找到的所述服务器资源记录，确定与所述目标域名关联的上层节点的步骤，包括：
    通过域名解析服务，解析查找到的所述服务器资源记录，得到所述服务器资源记录中的IP地址；以及
    将所述IP地址对应的节点设备，确定为与所述目标域名关联的上层节点。
  9. 根据权利要求1-8中任一项所述的访问请求的处理方法，其中，所述通过确定出的所述上层节点处理所述访问请求的步骤，包括：
    如果确定出的所述上层节点有多个，从确定出的多个所述上层节点中筛选出权重最大的上层节点；以及
    通过筛选出的上层节点处理所述访问请求。
  10. 根据权利要求1至9中任一项所述的访问请求的处理方法，其中，所述通过确定出的所述上层节点处理所述访问请求的步骤，包括：
    如果检测到确定出的所述上层节点均出现故障，从所述内容分发网络中除预设与所述目标域名关联的上层节点之外的上层节点中，确定目标上层节点；以及
    通过所述目标上层节点处理所述访问请求。
  11. 一种访问请求的处理装置，应用于内容分发网络的节点设备，所述装置包括：
    访问请求接收模块，设置为接收客户端针对目标域名的访问请求；
    判断模块，设置为判断所述节点设备的本地是否保存有所述目标域名的数据；以及
    访问请求处理模块，设置为如果没有保存所述目标域名的数据，根据所述目标域名，确定处理所述访问请求的上层节点，通过确定出的所述上层节点处理所述访问请求。
  12. 根据权利要求11所述的访问请求的处理装置，其中，所述节点设备中预先保存有域名和上层节点的第一关联关系；
    所述访问请求处理模块设置为：根据所述第一关联关系，确定与所述目标域名关联的上层节点；将确定出的所述上层节点确定为处理所述访问请求的上层节点。
  13. 根据权利要求12所述的访问请求的处理装置，其中，所述第一关联关系以服务器资源记录的形式，预先保存在所述节点设备的域名系统中；
    所述访问请求处理模块设置为：从所述域名系统中查找与所述目标域名关联的服务器资源记录，其中，所述服务器资源记录包括：域名、与所述域名关联的上层节点的IP地址以及所述上层节点的权重；根据查找到的所述服务器资源记录，确定与所述目标域名关联的上层节点。
  14. 根据权利要求11-13中任一项所述的访问请求的处理装置，其中，所述访问请求处 理模块设置为：如果确定出的所述上层节点有多个，从确定出的所述多个上层节点中筛选出权重最大的上层节点；通过筛选出的上层节点处理所述访问请求。
  15. 根据权利要求11-14中任一项所述的访问请求的处理装置，其中，所述访问请求处理模块设置为：如果检测到确定出的所述上层节点均出现故障，从所述内容分发网络中除预设与所述目标域名关联的上层节点之外的上层节点中，确定目标上层节点；通过所述目标上层节点处理该访问请求。
  16. 一种电子设备，所述电子设备包括处理器和存储器，所述存储器存储有能够被所述处理器执行的计算机可执行指令，所述处理器执行所述计算机可执行指令以实现权利要求1至10中任一项所述的访问请求的处理方法。
  17. 一种计算机可读存储介质，所述计算机可读存储介质存储有计算机可执行指令，所述计算机可执行指令在被处理器调用和执行时，计算机可执行指令促使处理器实现权利要求1至10任一项所述的访问请求的处理方法。
PCT/CN2021/107856 2020-09-30 2021-07-22 访问请求的处理方法、装置、电子设备及计算机可读存储介质 WO2022068333A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202011069197.6 2020-09-30
CN202011069197.6A CN112153160A (zh) 2020-09-30 2020-09-30 访问请求的处理方法、装置及电子设备

Publications (1)

Publication Number Publication Date
WO2022068333A1 true WO2022068333A1 (zh) 2022-04-07

Family

ID=73952543

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/107856 WO2022068333A1 (zh) 2020-09-30 2021-07-22 访问请求的处理方法、装置、电子设备及计算机可读存储介质

Country Status (2)

Country Link
CN (1) CN112153160A (zh)
WO (1) WO2022068333A1 (zh)

Families Citing this family (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112153160A (zh) * 2020-09-30 2020-12-29 北京金山云网络技术有限公司 访问请求的处理方法、装置及电子设备
CN113014422B (zh) * 2021-02-09 2022-09-23 北京金山云网络技术有限公司 一种内容分发网络带宽调度的方法、装置及设备
CN115150258A (zh) * 2021-03-30 2022-10-04 天翼云科技有限公司 Cdn节点配置方法、系统以及存储介质
CN115250294B (zh) * 2021-04-25 2024-03-22 贵州白山云科技股份有限公司 基于云分发的数据请求处理方法及其系统、介质、设备
CN112929456B (zh) * 2021-05-11 2022-04-01 杭州又拍云科技有限公司 一种集中回源和源站异常状态保护方法
CN113472852B (zh) * 2021-06-02 2023-07-25 乐视云网络技术(北京)有限公司 一种cdn节点的回源方法、装置、设备以及存储介质
CN113312612A (zh) * 2021-07-29 2021-08-27 支付宝(杭州)信息技术有限公司 多方安全计算中的应用访问方法和装置
CN113873302B (zh) * 2021-09-29 2024-04-26 北京金山云网络技术有限公司 内容分发方法、装置、存储介质和电子设备
CN113992760B (zh) * 2021-10-22 2024-03-01 北京百度网讯科技有限公司 回源流量的调度方法、装置、设备以及存储介质
CN114025023B (zh) * 2022-01-04 2022-05-10 北京金山云网络技术有限公司 回源方法、装置、设备及计算机可读存储介质
CN114900562B (zh) * 2022-05-09 2023-07-21 北京百度网讯科技有限公司 一种资源获取方法、装置、电子设备和存储介质
CN118413572B (zh) * 2024-06-28 2024-09-10 北京火山引擎科技有限公司 一种基于cdn的访问请求处理方法及装置

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20150100664A1 (en) * 2013-10-04 2015-04-09 Akamai Technologies, Inc. Systems and methods for caching content with notification-based invalidation with extension to clients
CN104754073A (zh) * 2015-03-25 2015-07-01 百度在线网络技术（北京）有限公司 一种资源访问方法及装置
US20170085674A1 (en) * 2012-11-26 2017-03-23 Go Daddy Operating Company, LLC Dns overriding-based methods of accelerating content delivery
CN109639801A (zh) * 2018-12-17 2019-04-16 深圳市网心科技有限公司 数据节点分配及数据获取方法及系统
CN112153160A (zh) * 2020-09-30 2020-12-29 北京金山云网络技术有限公司 访问请求的处理方法、装置及电子设备

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6754699B2 (en) * 2000-07-19 2004-06-22 Speedera Networks, Inc. Content delivery and global traffic management network system
CA2939921A1 (en) * 2014-02-19 2015-08-27 Level 3 Communications, Llc Proxy server failover and load clustering
CN105262841A (zh) * 2015-11-06 2016-01-20 浪潮软件集团有限公司 一种cdn网络负载均衡的实现方法及cdn调度服务器
CN111464649B (zh) * 2017-04-19 2022-10-21 贵州白山云科技股份有限公司 一种访问请求回源方法和装置
CN110430286A (zh) * 2019-08-30 2019-11-08 杭州领智云画科技有限公司 Cdn系统中获取资源的方法、装置、设备及存储介质

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20170085674A1 (en) * 2012-11-26 2017-03-23 Go Daddy Operating Company, LLC Dns overriding-based methods of accelerating content delivery
US20150100664A1 (en) * 2013-10-04 2015-04-09 Akamai Technologies, Inc. Systems and methods for caching content with notification-based invalidation with extension to clients
CN104754073A (zh) * 2015-03-25 2015-07-01 百度在线网络技术（北京）有限公司 一种资源访问方法及装置
CN109639801A (zh) * 2018-12-17 2019-04-16 深圳市网心科技有限公司 数据节点分配及数据获取方法及系统
CN112153160A (zh) * 2020-09-30 2020-12-29 北京金山云网络技术有限公司 访问请求的处理方法、装置及电子设备

Also Published As

Publication number Publication date
CN112153160A (zh) 2020-12-29

Similar Documents

Publication Publication Date Title
WO2022068333A1 (zh) 访问请求的处理方法、装置、电子设备及计算机可读存储介质
US11431791B2 (en) Content delivery method, virtual server management method, cloud platform, and system
US10104037B2 (en) Method and system for network access request control
KR102295664B1 (ko) 글로벌 서버 로드 밸런서 장치 및 상기 장치에서의 동적 캐쉬 유효 기간 제어 방법
US20190182351A1 (en) Route selection method and system, network acceleration node, and network acceleration system
US8706864B1 (en) Behavior monitoring and compliance for multi-tenant resources
US20140280606A1 (en) Method and Apparatus for Content Management
US8434156B2 (en) Method, access node, and system for obtaining data
US20170331667A1 (en) Method and system for guaranteeing resource utilization rate of website using content distribution network
CN106230971B (zh) 基于cdn的大文件分发方法
US10866894B2 (en) Controlling memory usage in a cache
US9407687B2 (en) Method, apparatus, and network system for acquiring content
JP2013525931A (ja) コンテンツ配信に利用される動的バインド
US10567492B1 (en) Methods for load balancing in a federated identity environment and devices thereof
US11431603B2 (en) Dynamic cloning of application infrastructures
US10117140B2 (en) Network storage method, switch device, and controller
CN113472852A (zh) 一种cdn节点的回源方法、装置及设备
US20210084100A1 (en) Packet Processing Method, Related Device, and Computer Storage Medium
WO2021017907A1 (zh) 一种优化的微服务间通信的方法及装置
JP7392168B2 (ja) Ｃｄｎにおけるｕｒｌリフレッシュ方法、装置、機器及びｃｄｎノード
WO2020098773A1 (zh) 一种请求响应方法、装置、边缘节点和鉴权系统
US20120102225A1 (en) Method and apparatus for routing requests for service using bgp community attributes
US10516742B2 (en) Access session management
CN117978809A (zh) 网关节点推荐方法、装置、计算机设备和存储介质

Legal Events

Date Code Title Description
NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 21873995

Country of ref document: EP

Kind code of ref document: A1