Methods for processing computing power information, first network equipment and system
By transmitting computing node power information in the ALTO protocol and supporting a publish/subscribe mechanism, the problem of low resource and network utilization in existing technologies is solved, achieving more efficient computing task scheduling and improved user experience.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2021-03-04
- Publication Date
- 2026-04-03
AI Technical Summary
The existing ALTO protocol cannot effectively improve resource utilization when transmitting network information, resulting in low efficiency in resource and network utilization.
The ALTO protocol transmits computing power information of computing nodes, supports publish/subscribe mechanisms, and allows ALTO clients to dynamically schedule computing tasks according to business needs and actively publish messages when computing power information changes.
It improves resource and network utilization, enhances user experience, and enables more efficient computing task scheduling, especially for application requests with high real-time requirements and large data volumes.
Smart Images

Figure CN114979130B_ABST
Abstract
Description
[0001] This application claims priority to Chinese Patent Application No. 202110196283.1, filed with the State Intellectual Property Office of China on February 22, 2021, entitled "A Method, Device and System for Processing Computing Power Information", the entire contents of which are incorporated herein by reference. Technical Field
[0002] This application relates to the field of network communication, and more specifically, to a method for processing computing power information, a first network device, and a system. Background Technology
[0003] The Application-Layer Traffic Optimization (ALTO) protocol is based on a client / server (C / S) architecture and uses JavaScript Object Notation (JSON) as its encoding format. This design makes the ALTO protocol flexible and scalable, and it can leverage the existing Hypertext Transfer Protocol (HTTP) to achieve communication between ALTO clients and ALTO servers. The ALTO protocol adopts a modular design approach, and the communication mechanism between ALTO clients and ALTO servers follows the design specifications of the ALTO protocol.
[0004] In related technical solutions, ALTO clients and ALTO servers can transmit network information about computing resources through the ALTO protocol, but relying solely on network information cannot improve resource utilization. Summary of the Invention
[0005] This application provides a method for processing computing power information, a first network device, and a system, which can improve resource and network utilization and enhance user experience.
[0006] In a first aspect, a method for processing computing power information is provided, comprising: a first network device acquiring first computing power information, wherein the first computing power information indicates the computing power information of a computing node corresponding to the first network device; the first network device generating a first application layer traffic optimization (ALTO) message, wherein the first ALTO message carries the first computing power information; and the first network device sending the first ALTO message to a second network device based on the ALTO protocol.
[0007] In the above technical solution, the computing power information of computing nodes can be transmitted through the ALTO protocol. This allows for dynamic and flexible scheduling of computing tasks according to business needs, thereby improving resource and network utilization and enhancing user experience.
[0008] In conjunction with the first aspect, in some implementations of the first aspect, the computing node is located in a first network domain, which is associated with the first network device.
[0009] In conjunction with the first aspect, in some implementations of the first aspect, the first computing power information is carried in the property map field of the first ALTO message.
[0010] In conjunction with the first aspect, in some implementations of the first aspect, the method further includes: the first network device receiving a first subscription request message sent by the second network device, the first subscription request message being used to request that the first network device report the first computing power information to the second network device when the first computing power information changes; and the first network device sending the first ALTO message to the second network device based on the ALTO protocol when the first computing power information changes.
[0011] In the above technical solution, the ALTO protocol, based on the original request / response mechanism, supports a publish / subscribe mechanism. This allows ALTO clients to subscribe based on the attribute values of a specific entity. When the attribute value collected by the ALTO server changes, the ALTO server can proactively publish a message to the ALTO client. This publish / subscribe mechanism is relatively flexible and efficient for applications with high real-time requirements and large data transmission volumes.
[0012] In conjunction with the first aspect, in some implementations of the first aspect, the method further includes: the first network device receiving a first subscription request message sent by the second network device, the first subscription request message being used to request the first network device to periodically report the first computing power information to the second network device; the first network device sending the first ALTO message to the second network device according to a preset period based on the ALTO protocol.
[0013] In conjunction with the first aspect, in some implementations of the first aspect, the first subscription request message further includes a combination of any one or more of the following attribute information: location information of the computing node, link status information, service type identifier, and computing power type information; the first computing power information carried in the first ALTO message indicates the computing power information of the first computing node; and the first computing node is determined by the first network device from the computing nodes based on the attribute information.
[0014] In conjunction with the first aspect, in some implementations of the first aspect, the method further includes: the first network device receiving a second subscription request message sent by the second network device, the second subscription request message being used to request the first network device to report the service type information supported by the computing node to the second network device; the first network device sending a second ALTO message to the second network device based on the ALTO protocol, the second ALTO message carrying the service type information supported by the computing node.
[0015] In conjunction with the first aspect, in some implementations of the first aspect, the method further includes: the first network device sending first network information to the second network device, the first network information indicating network information of a computing node corresponding to the first network device, the network information including but not limited to any one or more combinations of the following information: location information of the computing node, link status information, and supported service type information.
[0016] In conjunction with the first aspect, in some implementations of the first aspect, the first network device is a first local ALTO server of a first operator network, and the second network device is a second local ALTO server of the first operator network; or the first network device is a local ALTO server of the first operator network, and the second network device is a global ALTO server of the first operator network; or the first network device is a global ALTO server of the first operator network, and the second network device is a global ALTO server of a second operator network; or the first network device is a local ALTO server of the first operator network, and the second network device is a local ALTO server of the second operator network; or the first network device is an ALTO server, and the second network device is an ALTO client, wherein the ALTO server is any one of the following: a local ALTO server of the first operator network, a global ALTO server of the first operator network, a local ALTO server of the second operator network, or a global ALTO server of the second operator network.
[0017] It should be understood that the local ALTO server of the first operator network is used to collect local information corresponding to the local ALTO server in the first operator network, and the global ALTO server of the first operator network is used to summarize the information collected by all local ALTO servers in the first operator network.
[0018] In conjunction with the first aspect, in some implementations of the first aspect, the first network device is the ALTO server, the second network device is the ALTO client, the ALTO client is a computing power network management system, and the method further includes: the first network device receiving a third subscription request message sent by the second network device, the third subscription request message being used to request first capability information, the first capability information indicating capability deployment information of the computing node corresponding to the first network device; the first network device sending a third ALTO message to the second network device based on the ALTO protocol, the third ALTO message carrying the first capability information.
[0019] As an example, the above deployment information includes, but is not limited to, any one or more combinations of the following information: the remaining computing load, remaining storage space, remaining memory space of the computing node, computing node service identifier, computing node service type (e.g., firewall, load balancer), computing node location information, total computing load information, computing load usage information, memory usage information, total storage space information, total memory information, and disk space information. The computing node location may include the computing node's geographical location information, Internet Protocol (IP) address information, and the computing node's deployment location information in the data center (e.g., which rack or virtual machine (VM) image it is deployed in).
[0020] Secondly, a first network device is provided, comprising: an acquisition module, a processing module, and a transmission module.
[0021] The acquisition module is used to acquire first computing power information, wherein the first computing power information indicates the computing power information of the computing node corresponding to the first network device;
[0022] The processing module is used to generate a first application layer traffic optimization ALTO message, wherein the first ALTO message carries the first computing power information;
[0023] The sending module is used to send the first ALTO message to the second network device based on the ALTO protocol.
[0024] In conjunction with the second aspect, in some implementations of the second aspect, the computing node is located in a first network domain, which is associated with the first network device.
[0025] In conjunction with the second aspect, in some implementations of the second aspect, the first computing power information is carried in the property map field of the first ALTO message.
[0026] In conjunction with the second aspect, in some implementations of the second aspect, the first network device further includes: a receiving module.
[0027] The receiving module is configured to receive a first subscription request message sent by the second network device, wherein the first subscription request message is configured to request the first network device to report the first computing power information to the second network device when the first computing power information changes; the sending module 630 is specifically configured to send the first ALTO message to the second network device based on the ALTO protocol when the first computing power information changes.
[0028] In conjunction with the second aspect, in some implementations of the second aspect, the receiving module is used to receive a first subscription request message sent by the second network device, the first subscription request message being used to request the first network device to periodically report the first computing power information to the second network device; the sending module 630 is specifically used to: send the first ALTO message to the second network device according to a preset period based on the ALTO protocol.
[0029] In conjunction with the second aspect, in some implementations of the second aspect, the first subscription request message further includes a combination of any one or more of the following attribute information: location information of the computing node, link status information, service type identifier, and computing power type information; the first computing power information carried in the first ALTO message indicates the computing power information of the first computing node; and the first computing node is determined by the first network device from the computing nodes based on the attribute information.
[0030] In conjunction with the second aspect, in some implementations of the second aspect, the receiving module is further configured to receive a second subscription request message sent by the second network device, the second subscription request message being used to request the first network device to report the service type information supported by the computing node to the second network device; the sending module is further configured to send a second ALTO message to the second network device based on the ALTO protocol, the second ALTO message carrying the service type information supported by the computing node.
[0031] In conjunction with the second aspect, in some implementations of the second aspect, the sending module is further configured to send first network information to the second network device, the first network information indicating the network information of the computing node corresponding to the first network device, the network information including but not limited to any one or more combinations of the following information: location information of the computing node, link status information, and supported service type information.
[0032] In conjunction with the second aspect, in some implementations of the second aspect, the first network device is a first local ALTO server of a first operator network, and the second network device is a second local ALTO server of the first operator network; or the first network device is a local ALTO server of the first operator network, and the second network device is a global ALTO server of the first operator network; or the first network device is a global ALTO server of the first operator network, and the second network device is a global ALTO server of a second operator network; or the first network device is a local ALTO server of the first operator network, and the second network device is a local ALTO server of the second operator network; or the first network device is an ALTO server, and the second network device is an ALTO client, wherein the ALTO server is any one of the following: a local ALTO server of the first operator network, a global ALTO server of the first operator network, a local ALTO server of the second operator network, or a global ALTO server of the second operator network.
[0033] In conjunction with the second aspect, in some implementations of the second aspect, the first network device is the ALTO server, the second network device is the ALTO client, the ALTO client is a computing power network management system, and the receiving module is further configured to receive a third subscription request message sent by the second network device, the third subscription request message being used to request first capability information, the first capability information indicating the capability deployment information of the computing node corresponding to the first network device; the sending module 630 is further configured to send a third ALTO message to the second network device based on the ALTO protocol, the third ALTO message carrying the first capability information.
[0034] Thirdly, a first network device is provided, which has the function of implementing the behavior of the first network device in the above method. The function can be implemented in hardware or in software. The hardware or software includes one or more modules corresponding to the above function.
[0035] In one possible design, the first network device includes a processor and an interface in its structure, the processor being configured to support the first network device in performing the corresponding functions in the above-described method.
[0036] The first network device may further include a memory for coupling with a processor, which stores necessary program instructions and data for the first network device.
[0037] In another possible design, the first network device includes a processor, a transmitter, a receiver, random access memory (RAM), read-only memory (ROM), and a bus. The processor is coupled to the transmitter, receiver, RAM, and ROM via the bus. When the first network device needs to operate, it is booted by a bootloader embedded in the ROM or a basic input / output system, guiding the first network device into normal operation. After the first network device enters normal operation, an application program and operating system are run in the RAM, causing the processor to execute the methods of the first aspect or any possible implementation thereof.
[0038] Fourthly, a first network device is provided, comprising: a main control board and an interface board, and further, a switching board. The first network device is used to execute the methods of the first aspect or any possible implementation thereof. Specifically, the first network device includes modules for executing the methods of the first aspect or any possible implementation thereof.
[0039] Fifthly, a first network device is provided, comprising a control module and a first forwarding sub-device. The first forwarding sub-device includes an interface board, and further may include a switching board. The first forwarding sub-device performs the functions of the interface board in the fourth aspect, and further may perform the functions of the switching board in the fourth aspect. The control module includes a receiver, a processor, a transmitter, random access memory (RAM), read-only memory (ROM), and a bus. The processor is coupled to the receiver, transmitter, RAM, and ROM via the bus. When the control module needs to run, it is booted by a bootloader embedded in the ROM or a basic input / output system, guiding the control module into normal operation. After the control module enters normal operation, an application program and operating system run in the RAM, enabling the processor to perform the functions of the main control board in the fourth aspect.
[0040] Understandably, in practical applications, the first network device can contain any number of interfaces, processors, or memory.
[0041] In a sixth aspect, a computer program product is provided, comprising: computer program code, which, when run on a computer, causes the computer to perform the methods described in the first aspect or any possible execution thereof.
[0042] In a seventh aspect, a computer-readable medium is provided that stores program code, which, when executed on a computer, causes the computer to perform the methods described in the first aspect or any possible execution method of the first aspect. Such computer-readable storage includes, but is not limited to, one or more of the following: read-only memory (ROM), programmable ROM (PROM), erasable PROM (EPROM), flash memory, electrically EPROM (EEPROM), and hard drive.
[0043] Eighthly, a chip is provided, comprising a processor and a data interface, wherein the processor reads instructions stored in a memory through the data interface to execute the method of the first aspect or any possible implementation thereof. In specific implementation, the chip may be implemented as a central processing unit (CPU), a microcontroller unit (MCU), a microprocessor (MPU), a digital signal processor (DSP), a system-on-chip (SoC), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or a programmable logic device (PLD).
[0044] Ninthly, a computing power information processing system is provided, which includes the aforementioned first network device. Attached Figure Description
[0045] Figure 1 This is a system architecture diagram applied to an embodiment of this application.
[0046] Figure 2 This is a schematic flowchart of a method for processing computing power information provided in an embodiment of this application.
[0047] Figure 3 This is a schematic flowchart illustrating another method for processing computing power information provided in the embodiments of this application.
[0048] Figure 4This is a schematic flowchart illustrating another method for processing computing power information provided in the embodiments of this application.
[0049] Figure 5 This is a schematic flowchart illustrating a method for deploying computing instances at edge sites, as provided in an embodiment of this application.
[0050] Figure 6 This is a schematic structural diagram of a first network device 600 provided in an embodiment of this application.
[0051] Figure 7 This is a schematic diagram of the hardware structure of the first network device 2000 according to an embodiment of this application. Detailed Implementation
[0052] The technical solutions in this application will now be described with reference to the accompanying drawings.
[0053] This application will present various aspects, embodiments, or features relating to systems comprising multiple devices, components, modules, etc. It should be understood and appreciated that individual systems may include additional devices, components, modules, etc., and / or may not include all devices, components, modules, etc. discussed in conjunction with the accompanying drawings. Furthermore, combinations of these approaches are also possible.
[0054] Furthermore, in the embodiments of this application, the words "exemplary," "for example," etc., are used to indicate that they are examples, illustrations, or descriptions. Any embodiment or design scheme described as "exemplary" in this application should not be construed as being more preferred or advantageous than other embodiments or design schemes. Specifically, the use of the term "exemplary" is intended to present the concept in a concrete manner.
[0055] In the embodiments of this application, "corresponding" and "corresponding" can sometimes be used interchangeably. It should be noted that when the distinction is not emphasized, their intended meanings are consistent.
[0056] The network architecture and business scenarios described in the embodiments of this application are for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and do not constitute a limitation on the technical solutions provided in the embodiments of this application. As those skilled in the art will know, with the evolution of network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems.
[0057] References to "one embodiment" or "some embodiments" as described in this specification mean that one or more embodiments of this application include a specific feature, structure, or characteristic described in connection with that embodiment. Therefore, the phrases "in one embodiment," "in some embodiments," "in other embodiments," "in still other embodiments," etc., appearing in different parts of this specification do not necessarily refer to the same embodiment, but rather mean "one or more, but not all, embodiments," unless otherwise specifically emphasized. The terms "comprising," "including," "having," and variations thereof mean "including but not limited to," unless otherwise specifically emphasized.
[0058] In this application, "at least one" means one or more, and "more than one" means two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can mean: A alone, A and B simultaneously, and B alone, where A and B can be singular or plural. The character " / " generally indicates that the preceding and following related objects are in an "or" relationship. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, or c can mean: a, b, c, ab, ac, bc, or abc, where a, b, and c can be single or multiple.
[0059] Figure 1 This is a system architecture diagram applied to an embodiment of this application. For example... Figure 1 As shown in the diagram, there can be multiple networks, such as network 110, network 120, and network 130. Each network can belong to a separate domain, which can be a network domain or a management domain; this embodiment does not specifically limit this.
[0060] In one example, network 110 and network 120 in the system architecture diagram can be two edge clouds (also called edge sites), and network 130 can be a central cloud. Edge sites can be edge cloud data center networks closer to end users, while central clouds can be large data center networks. It should be understood that computing resources and services in cloud computing are typically concentrated in large data centers (e.g., central clouds), while end users access these resources and services at the "edge" of the network. Therefore, compared to services and functions located in cloud data centers, computing, storage, and other infrastructure can be "sinked" to the network edge (also called edge clouds or edge sites) closer to users, providing computing, storage, networking, and communication resources at the network edge.
[0061] In another example, network 110 and network 120 in the system architecture diagram can be two edge data centers, and network 130 can be a large data center network.
[0062] In another example, network 110 and network 120 in the system architecture diagram can be enterprise networks or campus networks, and network 1320 can be the core network.
[0063] Networks 110, 120, and 130 can all provide resources such as computing, storage, networking, and communication. Specifically, taking network 110 as an example, network 110 may include one or more computing nodes, such as computing node 112 and computing node 113. It should be understood that a computing node is a computing entity in the network capable of providing computing resource services; it can be a physical server or a computing instance on a physical server, and this application does not specifically limit this. Multiple different computing instances can exist on a single computing node, and different computing instances can provide different computing services. Each computing instance can exist in the same network or belong to different networks, and this application does not specifically limit this.
[0064] An application-layer traffic optimization (ALTO) server is a server running the ALTO protocol, associated with one or more of the aforementioned networks, and responsible for collecting relevant information and computing power information of computing nodes in the associated networks. Taking one ALTO server associated with each network as an example, assuming ALTO server 111 is associated with network 110, ALTO server 111 is responsible for collecting network information and computing power information of computing nodes 112 and 113 in network 110. ALTO server 111 can be located within or outside network 110; this application does not specifically limit this. As an example, ALTO server 111 is located within network 110; it can be a standalone device in network 110, or it can be deployed together with other devices in network 110, for example, ALTO server 111 can be deployed together with computing nodes in network 110.
[0065] It should be understood that the ALTO protocol is based on a client / server (C / S) architecture, employs a representational state transfer (REST)-full interface design, and uses JavaScript object notation (JSON) as its encoding format. This design makes the ALTO protocol flexible and scalable, and allows communication between ALTO clients and ALTO servers to be achieved using existing Hypertext Transfer Protocol (HTTP). The ALTO protocol adopts a modular design approach, and the communication mechanism between ALTO clients and ALTO servers follows the design specifications of the ALTO protocol.
[0066] This application provides a method for processing computing power information. In this method, the computing power information of computing nodes can be transmitted through the ALTO protocol. This allows for dynamic and flexible scheduling of computing tasks according to business needs, thereby improving resource and network utilization and enhancing user experience.
[0067] Figure 2 This is a schematic flowchart illustrating a method for processing computing power information provided in an embodiment of this application. Figure 2 As shown, the method may include steps 210-230, which will be described in detail below.
[0068] Step 210: The first network device obtains the first computing power information, which indicates the computing power information of the computing node corresponding to the first network device.
[0069] by Figure 1 Taking the system architecture diagram shown as an example, the first network device can be... Figure 1 The first network device can obtain the computing power information of any ALTO server in the network. The first computing power information obtained by the first network device can be the computing power information of one or more computing nodes corresponding to it. For example, if the first network device is ALTO server 111, ALTO server 111 can obtain the computing power information of computing nodes 112 and 113 in its associated network 110. There are various specific implementation methods for the first network device to obtain the first computing power information. The following describes different implementation methods in detail, taking ALTO server 111 as an example, where ALTO server 111 is responsible for obtaining the computing power information of computing nodes 112 and 113 in its associated network 110.
[0070] In one possible implementation, the ALTO server 111 is deployed or interacts with the computing power network management and orchestration system deployed in the network 110 to obtain computing power information of computing nodes 112 and 113.
[0071] In another possible implementation, ALTO server 111 can also collect computing power information from compute node 112 and compute node 113 through border gateway protocol (BGP) extensions, etc.
[0072] In another possible implementation, a distributed database can be deployed in the ALTO server 111, and the computing power information of the computing nodes 112 and 113 can be periodically written to and updated by the computing power network management and orchestration system deployed in the computing nodes 112 and 113 or the network 110.
[0073] It should be understood that computing power information can be expressed as computing power or computing resource performance, referring to the performance of computing resources or computing and storage resources, including information on the computing nodes' ability to perform various processing tasks such as computing and storage of data.
[0074] Step 220: The first network device generates a first ALTO message, which carries first computing power information.
[0075] As an example, embodiments of this application can extend the property map field of the ALTO protocol, enabling the first network device to carry first computing power information through the property map field. For example, the first computing power information can be carried in the property map field of the first ALTO message.
[0076] Optionally, in some embodiments, the network map field can be extended to describe the types of service instances that the edge site can handle and the addresses of computing nodes.
[0077] Step 230: The first network device sends the first ALTO message to the second network device based on the ALTO protocol.
[0078] by Figure 1Taking the system architecture diagram shown as an example, assuming that network 110 and network 120 are two edge sites, and network 130 is the central site, ALTO server 111 can be called local ALTO server 111, ALTO server 121 can be called local ALTO server 121, and ALTO server 131 can be called global ALTO server 131. In one example, the first network device can be local ALTO server 111, and the second network device can be local ALTO server 121. In another example, the first network device can be either local ALTO server 111 or local ALTO server 121, and the second network device can be global ALTO server 131. In yet another example, the first network device can be the global ALTO server of the first operator's network (e.g., networks 110, 120, and 130 belong to the first operator, and the global ALTO server of the first operator's network is global ALTO server 131), and the second network device can be the global ALTO server of the second operator's network. Figure 1 (Not shown in the image). In another example, the first network device is a local ALTO server for a first operator's network (e.g., networks 110, 120, and 130 belong to the first operator, and the local ALTO server for the first operator's network is local ALTO server 111 or local ALTO server 121), and the second network device is a local ALTO server for a second operator's network. Figure 1 (Not shown in the image). In another example, the first network device is an ALTO server and the second network device is an ALTO client, wherein the ALTO server is any of the following: local ALTO server 111, local ALTO server 121, or global ALTO server 131.
[0079] It should be understood that if both the first network device and the second network device are ALTO servers, the first network device can act as an ALTO server and the second network device can act as an ALTO client. Thus, based on a client / server (C / S) architecture, the first network device can send the first ALTO message to the second network device according to the ALTO protocol.
[0080] Optionally, before step 230, the first network device may also receive a first subscription request message sent by the second network device, and the first network device may send the first ALTO message to the second network device according to the first subscription request message. There are several specific implementation methods; two possible implementation methods are described in detail below.
[0081] In one possible implementation, the first subscription request message sent by the second network device to the first network device is used to request the first network device to periodically report the first computing power information to the second network device. After receiving the first subscription request message, the first network device can send the first ALTO message to the second network device according to a preset period based on the ALTO protocol.
[0082] In another possible implementation, the first subscription request message sent by the second network device to the first network device requests that the first network device report the first computing power information to the second network device when the first computing power information changes. Upon receiving the first subscription request message, the first network device sends the first ALTO message to the second network device based on the ALTO protocol when the first computing power information changes. It should be understood that the period during which the first network device detects whether the first computing power information has changed can be the same as the period during which it collects the first computing power information, or the second network device can specify the period for detecting whether the first computing power information has changed through the first subscription request message; this application does not specifically limit this.
[0083] Optionally, in some embodiments, the first subscription request message sent by the second network device to the first network device may also carry some attribute information, which may include, but is not limited to, any one or more combinations of the following: location information of the computing node, link status information, and service type identifier. The first network device can report the computing power information corresponding to a specified computing node to the second network device based on the attributes carried in the first subscription request message. In this way, the second network device can obtain the computing power information corresponding to a specified computing node without needing to obtain the computing power information of all computing nodes associated with the first network device, thus improving work efficiency.
[0084] Optionally, in some embodiments, the first network device may also send network information of the computing node corresponding to the first network device to the second network device. That is, the first network device may send network information and computing power information of the computing node corresponding to the first network device to the second network device. In this way, the second network device can determine the optimal computing node based on the network information and computing power information of the computing node, thereby achieving load balancing of services, improving resource utilization, and enhancing user experience.
[0085] As an example, the network information of the aforementioned computing node may include, but is not limited to, any one or more combinations of the following: the location information of the computing node, link state information, and supported service type information. The location information of the computing node generally refers to its location within a single domain (which can be a network domain or a management domain). Link state information may include data related to latency, bandwidth, jitter, and service level agreement (SLA) between computing nodes. Supported service type information may include the types of services supported on the computing node, such as firewall (FW) services and load balancing (LB) services.
[0086] Optionally, in some embodiments, the second network device can also obtain information about the service types supported by the computing node by sending a subscription request to the first network device. For example, the second network device can also send a second subscription request message to the first network device, which requests the first network device to report information such as the service types supported on its associated computing nodes.
[0087] The following is combined with Figure 3 This application provides a detailed description of a specific implementation of the computing power information processing method provided in its embodiments. It should be understood that... Figure 3 The examples provided are merely to help those skilled in the art understand the embodiments of this application, and are not intended to limit the embodiments to the specific numerical values or specific scenarios illustrated. Those skilled in the art will understand based on the following... Figure 3 The examples can obviously be modified or changed in various ways, and such modifications and changes also fall within the scope of the embodiments of this application.
[0088] Figure 3 This is a schematic flowchart illustrating another method for processing computing power information provided in an embodiment of this application. Figure 3 As shown, the method may include steps 310-390, which will be described in detail below.
[0089] Step 310: Edge sites report network and computing power information to their associated local ALTO servers.
[0090] In other words, a local ALTO server deployed within a single domain can collect network and computing power information from all edge sites within that domain. This embodiment of the application assumes that each edge site belongs to a single domain. As an example, let's take... Figure 1Taking the scenario shown as an example, the local ALTO server 111 can collect network information and computing power information of compute nodes 112 and 113 in network 110. The local ALTO server 121 can collect network information and computing power information of compute nodes 122 and 123 in network 120.
[0091] There are various specific implementation methods, and this application does not limit them. Taking the local ALTO server 111 as an example, in one possible implementation, the local ALTO server 111 is jointly deployed or interacts with the computing power network management and orchestration system deployed in network 110 to obtain the network information and computing power information of computing nodes 112 and 113. In another possible implementation, the local ALTO server 111 can also collect network information and computing power information from computing nodes 112 and 113 respectively through border gateway protocol (BGP) extensions. In yet another possible implementation, a distributed database can be deployed in the local ALTO server 111, and the computing nodes 112 and 113, or the computing power network management and orchestration system deployed in network 110, can periodically write and update the network information and computing power information of computing nodes 112 and 113. For a description of the network information and computing power information, please refer to [link to relevant documentation]. Figure 2 The description in the text will not be repeated here.
[0092] Step 320: The local ALTO server publishes the network and computing power information collected within the domain to the global ALTO server.
[0093] Specifically, local ALTO servers within each domain publish the acquired network and computing power information to the global ALTO server deployed in the central cloud via the ALTO protocol. Figure 1 Taking the scenario shown as an example, local ALTO server 111 and local ALTO server 121 respectively publish the acquired network information and computing power information to global ALTO server 131 through the ALTO protocol.
[0094] It should be understood that communication between the local ALTO server and the global ALTO server follows the communication guidelines of the ALTO protocol. That is, the global ALTO server acts as an ALTO client, sending requests to the local ALTO server to obtain network and computing power information collected within its domain.
[0095] As an example, one way to facilitate the interaction between the global ALTO server 131 and the local ALTO servers in each domain is for the global ALTO server 131 to first obtain network information (e.g., network map) in each domain, and then query or subscribe to computing power information (e.g., computing power and load) on the computing instances of a specified edge site.
[0096] It should be understood that the information collected by the global ALTO server is not static. For example, network location information in the network map may remain relatively stable for a considerable period of time, while some information in the cost map or property map may require frequent updates. Therefore, the global ALTO server's collection of network and computing power information may need to be triggered periodically. The execution of steps 310 and 320 is not a one-time event, but rather a periodic process.
[0097] For example, suppose there are two edge sites: PID1 (ID 25100) and PID2 (ID 25200). PID1 is associated with local ALTO server 111, providing both Firewall (FW) and Load Balancer (LB) services. The IPv4 addresses of the compute nodes providing FW services in this edge site are 10.247.0.10 and 10.247.0.20, respectively, while the address of the compute node providing LB services is 10.247.0.30. PID2 is associated with local ALTO server 121, providing both LB and Acceleration services. The address of the compute node providing LB services in this edge site is 20.247.0.10, and the address of the compute node providing Acceleration services is 20.247.0.20. The following example illustrates a possible communication method between the global ALTO server and local ALTO servers within various domains. It should be understood that the content after / / represents JSON code interpretation information.
[0098] 1. Global ALTO server 131 first requests the network map to obtain the location information of edge sites and the types of services they can handle:
[0099] GET / networkmap HTTP / 1.1
[0100] The local ALTO server within a single domain responds to a request from the global ALTO server 131, with the response body being a string of JSON code. There are several ways to implement this response; the following example, using the local ALTO server 111 responding to a request from the global ALTO server 131, illustrates two different response methods through JSON code.
[0101] One possible response is as follows:
[0102] Response: HTTP / 1.1 200 OK
[0103]
[0104]
[0105] In this response, the Service Instance ID is introduced between the PID and the IPv4 layer to describe that a service has multiple service instances located in different locations. The Service Instance ID is used to identify each service instance, such as a firewall service, and the IPv4 address is used to describe the different locations of the specified service instances.
[0106] Another possible response would be to declare the location of the edge site as "bsid":
[0107] Response: HTTP / 1.1 200 OK
[0108]
[0109]
[0110] The local ALTO server 121 can also respond to the request of the global ALTO server 131 in the same way as the local ALTO server 111 responds to the global ALTO server 131. For details, please refer to the response process of the local ALTO server 111, which will not be repeated here.
[0111] 2. Query or subscribe to the computing power and load of service instances at a specified edge site using the global ALTO server 131:
[0112] Query request: POST / propmap / lookup / ane-dc HTTP / 1.1
[0113]
[0114] Step 330: The ALTO client receives the service request from the user side.
[0115] As an example, the service request could be a virtual reality (VR) request or an artificial intelligence (AI) training request for an individual user.
[0116] Step 340: The ALTO client obtains the current network information and computing power information from the local ALTO server.
[0117] When an ALTO client communicates with a local ALTO server, it follows the communication guidelines of the ALTO protocol. For example, an ALTO client can send a query request to a local ALTO server 111. The local ALTO server 111 can then report the network and computing power information it has collected within the corresponding domain to the ALTO client based on the ALTO protocol. In another example, an ALTO client can also send a subscription request to a local ALTO server 111. The local ALTO server 111 can then periodically report the network and computing power information it has collected within the corresponding domain to the ALTO client based on the ALTO protocol, or proactively report network and computing power information to the ALTO client when the network or computing power information within the corresponding domain changes, based on the ALTO protocol.
[0118] In one scenario, if the local ALTO server has relevant network and computing power information, step 350 can be executed. In another scenario, if the local ALTO server is unable to respond to the ALTO client's request, steps 360-370 can be executed.
[0119] Step 350: The local ALTO server sends the current network information and computing power information to the ALTO client.
[0120] If the local ALTO server has relevant network and computing power information, it can return this information to the ALTO client. For the specific response process, please refer to step 320; it will not be repeated here.
[0121] Optionally, if the local ALTO server is unable to respond to the ALTO client's request, for example, if the local ALTO server is currently overloaded and unable to handle the ALTO client's request, the method may further include steps 360-370.
[0122] Step 360: The ALTO client obtains network information and computing power information from the global ALTO server.
[0123] Specifically, the local ALTO server returns an HTTP 307 (temporary redirect) status code to the ALTO client and indicates the address of the global ALTO server. The ALTO client then uses this address to retrieve network and computing power information from the global ALTO server. The request method is the same as in step 340; please refer to the description in step 340 for details, which will not be repeated here.
[0124] Step 370: The global ALTO server returns network information and computing power information to the ALTO client.
[0125] The following example illustrates a possible interaction method in which a global ALTO server returns network and computing power information collected from various domains to ALTO clients.
[0126] 1. The ALTO client queries the global ALTO server for the location of compute nodes in all edge sites and returns the results.
[0127] Request: GET / networkmap HTTP / 1.1
[0128] One possible response from the global ALTO server is as follows:
[0129] Response: HTTP / 1.1 200 OK
[0130]
[0131]
[0132] Another possible response from the global ALTO server is as follows:
[0133] Response: HTTP / 1.1 200 OK
[0134]
[0135]
[0136] 2. The ALTO client specifies an edge site and queries the global ALTO server for the specified service capabilities and service load information:
[0137] Request: POST / propmap / lookup / ane-dc HTTP / 1.1
[0138]
[0139] 3. The ALTO client specifies a compute node in an edge site that can handle requests for a specified service, and queries the global ALTO server for the service capacity and load information of that single node:
[0140] Request: POST / propmap / lookup / ane-dc HTTP / 1.1
[0141]
[0142]
[0143] Step 380: The ALTO client determines the optimal edge site based on the obtained network and computing power information.
[0144] Specifically, as an example, after obtaining the network and computing power information of each edge site or a specified edge site, the ALTO client determines the optimal edge site based on the decision-making algorithm of the internal device.
[0145] Step 390: The ALTO client sends the service request to the optimal edge site.
[0146] Specifically, as an example, an ALTO client can send service requests to compute nodes in the optimal edge site.
[0147] Optionally, in some embodiments, if there is currently no computing node capable of handling the ALTO client's request (e.g., the computing instance of the computing node is overloaded or does not support the computing capability), the central cloud can coordinate with the edge site to distribute some resources. In this case, the ALTO client can subscribe to the computing power changes from the ALTO server and request services from the optimal edge computing node once the resources are ready. The following is combined with... Figure 4 This section provides a detailed description of the specific implementation method.
[0148] Figure 4 This is a schematic flowchart illustrating another method for processing computing power information provided in an embodiment of this application. Figure 4 As shown, the method may include steps 410-495, which will be described in detail below.
[0149] Step 410: The edge site reports network information and computing power information to the local ALTO server associated with it.
[0150] Step 420: The local ALTO server publishes the network and computing power information collected within the domain to the global ALTO server.
[0151] Step 430: The ALTO client receives the service request from the user side.
[0152] Step 440: The ALTO client obtains the current network information and computing power information from the local ALTO server.
[0153] It should be understood that steps 410-440 are the same as steps 310-340. For details, please refer to the description in steps 310-340, which will not be repeated here.
[0154] Step 450: The local ALTO server redirects the ALTO client's request to the global ALTO server.
[0155] As an example, the local ALTO server returns an HTTP 307 (temporary redirect) status code to the ALTO client and indicates the address of the global ALTO server. The ALTO client then sends a request to the global ALTO server based on that address. See [link to details] for further information. Figure 3 The description of step 360 is omitted here.
[0156] Step 460: The global ALTO server allocates computing resources and sends configuration information to edge sites.
[0157] If the global ALTO server determines that no compute node in any domain is capable of handling the service request (e.g., the compute node's compute instance is overloaded or does not support the computing capacity), the global ALTO server can select a suitable edge site based on certain internally defined strategies. It then interacts with the management and orchestration system of the computing network to deploy compute instances for the edge site and distribute configuration information to the edge site. For example, one implementation of this step is to increase the number of service instance replicas in the mainstream compute scheduling platform Kubernetes. For a detailed explanation of the process of the global ALTO server interacting with the management and orchestration system of the computing network to deploy compute instances for the edge site, please refer to [link to relevant documentation]. Figure 5 The description in the text will not be repeated here.
[0158] Step 470: The global ALTO server sends the location information of the ALTO server corresponding to the domain where the edge site that distributed the resource and configuration information is located to the ALTO client.
[0159] Specifically, the global ALTO server sends an HTTP 503 (service unavailable) response to the ALTO client, and the error message includes the location information of the ALTO server corresponding to the domain of the edge site that distributed the resources and configuration information. For example, the ALTO server corresponding to the domain of the edge site that distributed the resources and configuration information is the local ALTO server 121.
[0160] Step 480: The ALTO client sends a request to the local ALTO server 121 in step 470 to subscribe to the edge site load capacity and load changes.
[0161] Specifically, after receiving the response message in step 470, the ALTO client can send a request to the local ALTO server 121 carried in step 470 to subscribe to the edge site's load capacity and load changes.
[0162] The following example illustrates a specific implementation process of ALTO client subscribing to the load capacity and load changes of an edge site, using the example of an ALTO client requesting to subscribe to the compute load of service Acceleration-service-ID3 on the edge site PID1 associated with the local ALTO server 121.
[0163]
[0164] Step 490: When there are changes in computing resources, the local ALTO server 121 publishes a message to the ALTO client.
[0165] Taking an ALTO client requesting to subscribe to the compute load of service Acceleration-service-ID3 on edge site PID1 associated with local ALTO server 121 as an example, when the compute load of Acceleration-service-ID3 on local ALTO server 121 changes, local ALTO server 121 publishes a response message to the ALTO client. One possible implementation is listed below.
[0166]
[0167] Step 495: The ALTO client sends the service request to the optimal edge site.
[0168] Similar to step 390, please refer to the explanation in step 390 for details, which will not be repeated here.
[0169] The following is combined with Figure 5 This paper provides a detailed description of the specific implementation process of how the global ALTO server interacts with the management and orchestration system of the computing network to deploy computing instances for edge sites. It should be understood that... Figure 5 The examples provided are merely to help those skilled in the art understand the embodiments of this application, and are not intended to limit the embodiments to the specific numerical values or specific scenarios illustrated. Those skilled in the art will understand based on the following... Figure 5 The examples can obviously be modified or changed in various ways, and such modifications and changes also fall within the scope of the embodiments of this application.
[0170] Figure 5 This is a schematic flowchart illustrating a method for deploying computing instances at edge sites, as provided in an embodiment of this application. Figure 5 As shown, the method may include steps 510-540, which will be described in detail below.
[0171] Step 510: The global ALTO server obtains network information and site deployment capabilities of the edge sites.
[0172] The method for obtaining it is the same as that in step 420. Please refer to the description in step 420 for details, which will not be repeated here.
[0173] It should be understood that the deployment capabilities of an edge site may include, but are not limited to, any one or more combinations of the following information: the remaining computing load, remaining storage space, remaining memory space of the edge site, the service identifier of the edge site, the service type of the edge site (e.g., firewall, load balancer), the location information of the edge site, the total load information of the edge site, the computing load already used information, the memory already used information, the total storage space information, the total memory information, and the disk space information. The location of the edge site may include the geographical location information of the edge site, the Internet Protocol (IP) address information, and the location information of the computing nodes in the edge site in the data center (e.g., which rack or virtual machine (VM) image they are deployed in).
[0174] Step 520: The computing network management and orchestration system subscribes to the global ALTO server for changes in the deployment capability information (such as load) of all edge sites.
[0175] Specifically, as an example, the computing network management and orchestration system, acting as an ALTO client, subscribes to the ALTO server for changes in deployment capacity information (such as load) for all edge sites. A possible message example is shown below:
[0176] Subscription deployment information changes:
[0177]
[0178] In another example, the computing network management and orchestration system acts as an ALTO client, periodically subscribing to the ALTO server for deployment capability information (such as load) of all edge sites. The ALTO server sends this information to the computing network management and orchestration system every 30ms. A possible message example is shown below:
[0179] Periodic (30ms) subscription to deployment information:
[0180]
[0181] Step 530: The global ALTO server pushes the deployment capability information of the edge sites to the computing power network management and orchestration system.
[0182] When the deployment information subscribed in step 520 changes, for example, the compute-load attribute decreases to 10%, the global ALTO server pushes relevant content to it. An example of a possible return message is shown below:
[0183]
[0184] Optionally, the ALTO client can also subscribe based on the dimension of compute nodes in the edge site. The global ALTO server's publishing information will provide deployment capability information such as CPU load, free memory, and number of CPU cores for all compute nodes in each edge site.
[0185] The management and orchestration system can be designed with some judgment criteria. For example, when the remaining computing load resources of a computing node in a certain site are greater than 80%, the computing instance of the service will be deployed on that edge computing node.
[0186] Step 540: The computing power network management and orchestration system allocates certain resources to its selected edge sites and sends computing power deployment configuration information to the edge site side.
[0187] In the above technical solution, in the edge computing scenario, the computing power network management and orchestration system uses the ALTO protocol to sense the computing deployment information such as the load of edge sites, selects the lightest edge site to deploy computing tasks, and improves the user experience.
[0188] It should be understood that in the various embodiments of this application, the order of the above-mentioned processes does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.
[0189] The above text combined Figures 1 to 5 This application describes in detail a method for processing computing power information provided by an embodiment of the present application. The following will be combined with... Figures 6 to 7 The embodiments of the apparatus described in this application are described in detail below. It should be understood that the descriptions of the method embodiments correspond to the descriptions of the apparatus embodiments; therefore, any parts not described in detail can be found in the foregoing method embodiments.
[0190] Figure 6 This is a schematic structural diagram of a first network device 600 provided in an embodiment of this application. Figure 6 The first network device 600 shown can perform the corresponding steps executed by the first network device in the method of the above embodiments. For example... Figure 6 As shown, the first network device 600 includes: an acquisition module 610, a processing module 620, and a sending module 630.
[0191] The acquisition module 610 is used to acquire first computing power information, wherein the first computing power information indicates the computing power information of the computing node corresponding to the first network device;
[0192] Processing module 620 is used to generate a first application layer traffic optimization ALTO message, wherein the first ALTO message carries the first computing power information;
[0193] The sending module 630 is used to send the first ALTO message to the second network device based on the ALTO protocol.
[0194] Optionally, the computing node is located in a first network domain, which is associated with the first network device.
[0195] Optionally, the first computing power information is carried in the property map field of the first ALTO message.
[0196] Optionally, the first network device 600 further includes: a receiving module 640,
[0197] The receiving module 640 is configured to receive a first subscription request message sent by the second network device, wherein the first subscription request message is configured to request the first network device to report the first computing power information to the second network device when the first computing power information changes; the sending module 630 is specifically configured to send the first ALTO message to the second network device based on the ALTO protocol when the first computing power information changes.
[0198] Optionally, the receiving module 640 is configured to receive a first subscription request message sent by the second network device, the first subscription request message being used to request the first network device to periodically report the first computing power information to the second network device; the sending module 630 is specifically configured to: send the first ALTO message to the second network device according to a preset period based on the ALTO protocol.
[0199] Optionally, the first subscription request message may further include a combination of any one or more of the following attribute information: location information of the computing node, link status information, service type identifier, and computing power type information. The first computing power information carried in the first ALTO message indicates the computing power information of the first computing node. The first computing node is determined by the first network device from the computing nodes based on the attribute information.
[0200] Optionally, the receiving module 640 is further configured to receive a second subscription request message sent by the second network device, the second subscription request message being used to request the first network device to report the service type information supported by the computing node to the second network device; the sending module is further configured to send a second ALTO message to the second network device based on the ALTO protocol, the second ALTO message carrying the service type information supported by the computing node.
[0201] Optionally, the sending module 630 is further configured to send first network information to the second network device, the first network information indicating the network information of the computing node corresponding to the first network device, the network information including but not limited to any one or more combinations of the following information: location information of the computing node, link status information, and supported service type information.
[0202] Optionally, the first network device is a first local ALTO server of a first operator network, and the second network device is a second local ALTO server of the first operator network; or the first network device is a local ALTO server of the first operator network, and the second network device is a global ALTO server of the first operator network; or the first network device is a global ALTO server of the first operator network, and the second network device is a global ALTO server of the second operator network; or the first network device is a local ALTO server of the first operator network, and the second network device is a local ALTO server of the second operator network; or the first network device is an ALTO server, and the second network device is an ALTO client, wherein the ALTO server is any one of the following: a local ALTO server of the first operator network, a global ALTO server of the first operator network, a local ALTO server of the second operator network, or a global ALTO server of the second operator network.
[0203] Optionally, the first network device is the ALTO server, the second network device is the ALTO client, the ALTO client is a computing power network management system, and the receiving module 640 is further configured to receive a third subscription request message sent by the second network device, the third subscription request message being used to request first capability information, the first capability information indicating the capability deployment information of the computing node corresponding to the first network device; the sending module 630 is further configured to send a third ALTO message to the second network device based on the ALTO protocol, the third ALTO message carrying the first capability information.
[0204] Figure 7This is a schematic diagram of the hardware structure of the first network device 2000 according to an embodiment of this application. Figure 7 The first network device 2000 shown can execute the corresponding steps performed by the first network device in the method of the above embodiments.
[0205] like Figure 7 As shown, the first network device 2000 includes a processor 2001, a memory 2002, an interface 2003, and a bus 2004. The interface 2003 can be implemented wirelessly or via a wired connection; specifically, it can be a network interface card (NIC). The processor 2001, memory 2002, and interface 2003 are connected via the bus 2004.
[0206] The interface 2003 may specifically include a transmitter and a receiver, used by the first network device to implement the aforementioned sending and receiving. For example, the interface 2003 is used to support the first network device in sending the first ALTO message to the second network device based on the ALTO protocol.
[0207] The processor 2001 is used to execute the processing performed by the first network device in the above embodiments. For example, it is used to acquire first computing power information; generate a first application layer traffic optimization (ALTO) message, the first ALTO message carrying the first computing power information; and / or other processes used in the techniques described herein. The memory 2002 includes an operating system 20021 and an application program 20022, used to store programs, code, or instructions, which can complete the processing involving the first network device in the method embodiments when the processor or hardware device executes these programs, code, or instructions. Optionally, the memory 2002 may include read-only memory (ROM) and random access memory (RAM). The ROM includes a basic input / output system (BIOS) or an embedded system; the RAM includes application programs and the operating system. When the first network device 2000 needs to be run, the system is booted through the BIOS embedded in the ROM or the bootloader in the embedded system, guiding the first network device 2000 into normal operation. After the first network device 2000 enters normal operation, the application program and operating system running in RAM complete the processing procedures involving the first network device 2000 in the method embodiment.
[0208] Understandable Figure 7 Only a simplified design of the first network device 2000 is shown. In practical applications, the first network device can contain any number of interfaces, processors, or memory.
[0209] This application also provides a computer-readable medium storing program code that, when executed on a computer, causes the computer to perform the method described above by the first network device. Such computer-readable storage includes, but is not limited to, one or more of the following: read-only memory (ROM), programmable ROM (PROM), erasable PROM (EPROM), flash memory, electrically EPROM (EEPROM), and hard drive.
[0210] This application embodiment also provides a chip system applied in a first network device. The chip system includes: at least one processor, at least one memory, and an interface circuit. The interface circuit is responsible for information interaction between the chip system and the outside world. The at least one memory, the interface circuit, and the at least one processor are interconnected via lines. The at least one memory stores instructions. The instructions are executed by the at least one processor to perform the operation of the first network device in the methods described in the above aspects.
[0211] In specific implementation, the chip can be implemented in the form of a central processing unit (CPU), micro controller unit (MCU), micro processing unit (MPU), digital signal processor (DSP), system on chip (SoC), application-specific integrated circuit (ASIC), field-programmable gate array (FPGA), or programmable logic device (PLD).
[0212] This application also provides a computer program product applied in a first network device. The computer program product includes a series of instructions, which, when executed, perform the operations of the first network device as described in the above aspects.
[0213] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.
[0214] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.
[0215] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.
[0216] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.
[0217] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.
[0218] If the aforementioned functions are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.
[0219] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the technical scope disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.
Claims
1. A method for processing computing power information, characterized in that, include: The first network device obtains the first computing power information, which indicates the computing power information of the computing node corresponding to the first network device. The first network device generates a first application layer traffic optimization ALTO message, the first ALTO message carries the first computing power information, and the first computing power information is carried in the property map field of the first ALTO message; The first network device sends the first ALTO message to the second network device based on the ALTO protocol; The first network device receives a second subscription request message sent by the second network device. The second subscription request message is used to request the first network device to report the service type information supported by the computing node to the second network device. The first network device sends a second ALTO message to the second network device based on the ALTO protocol. The second ALTO message carries information about the service types supported by the computing node.
2. The method according to claim 1, characterized in that, The computing node is located in a first network domain, which is associated with the first network device.
3. The method according to claim 1, characterized in that, The method further includes: The first network device receives a first subscription request message sent by the second network device. The first subscription request message is used to request that the first network device report the first computing power information to the second network device when the first computing power information changes. The first network device sends the first ALTO message to the second network device based on the ALTO protocol, including: When the first computing power information changes, the first network device sends the first ALTO message to the second network device based on the ALTO protocol.
4. The method according to claim 1, characterized in that, The method further includes: The first network device receives a first subscription request message sent by the second network device. The first subscription request message is used to request the first network device to periodically report the first computing power information to the second network device. The first network device sends the first ALTO message to the second network device based on the ALTO protocol, including: The first network device sends the first ALTO message to the second network device according to the ALTO protocol at a preset period.
5. The method according to claim 3 or 4, characterized in that, The first subscription request message also includes a combination of any one or more of the following attribute information: location information of the computing node, link status information, service type identifier, and computing power type information. The first computing power information carried in the first ALTO message indicates the computing power information of the first computing node. The first computing node is determined by the first network device from the computing nodes based on the attribute information.
6. The method according to any one of claims 1 to 4, characterized in that, The method further includes: The first network device sends first network information to the second network device. The first network information indicates the network information of the computing node corresponding to the first network device. The network information includes, but is not limited to, any one or more combinations of the following information: location information of the computing node, link status information, and supported service type information.
7. The method according to any one of claims 1 to 4, characterized in that, The first network device is a first local ALTO server in the first operator's network, and the second network device is a second local ALTO server in the first operator's network; or The first network device is a local ALTO server of the first operator's network, and the second network device is a global ALTO server of the first operator's network; or The first network device is a global ALTO server for the first operator's network, and the second network device is a global ALTO server for the second operator's network; or The first network device is a local ALTO server in the first operator's network, and the second network device is a local ALTO server in the second operator's network; or The first network device is an ALTO server, and the second network device is an ALTO client. The ALTO server is any one of the following: a local ALTO server of the first operator network, a global ALTO server of the first operator network, a local ALTO server of the second operator network, or a global ALTO server of the second operator network.
8. The method according to claim 7, characterized in that, The first network device is the ALTO server, the second network device is the ALTO client, the ALTO client is a computing power network management system, and the method further includes: The first network device receives a third subscription request message sent by the second network device. The third subscription request message is used to request first capability information, which indicates the capability deployment information of the computing node corresponding to the first network device. The first network device sends a third ALTO message to the second network device based on the ALTO protocol, and the third ALTO message carries the first capability information.
9. A first network device, characterized in that, include: The acquisition module is used to acquire first computing power information, wherein the first computing power information indicates the computing power information of the computing node corresponding to the first network device; The processing module is used to generate a first application layer traffic optimization ALTO message. The first ALTO message carries the first computing power information, which is carried in the property map field of the first ALTO message. The sending module is configured to send the first ALTO message to the second network device based on the ALTO protocol; the sending module is also configured to send a second ALTO message to the second network device based on the ALTO protocol, wherein the second ALTO message carries service type information supported by the computing node; The receiving module is configured to receive a second subscription request message sent by the second network device, wherein the second subscription request message is used to request the first network device to report the service type information supported by the computing node to the second network device.
10. The first network device according to claim 9, characterized in that, The computing node is located in a first network domain, which is associated with the first network device.
11. The first network device according to claim 9, characterized in that, Also includes: The receiving module is configured to receive a first subscription request message sent by the second network device. The first subscription request message is configured to request the first network device to report the first computing power information to the second network device when the first computing power information changes. The sending module is specifically used to: send the first ALTO message to the second network device based on the ALTO protocol when the first computing power information changes.
12. The first network device according to claim 9, characterized in that, Also includes: The receiving module is configured to receive a first subscription request message sent by the second network device, wherein the first subscription request message is configured to request the first network device to periodically report the first computing power information to the second network device; The sending module is specifically used to: send the first ALTO message to the second network device according to the ALTO protocol at a preset period.
13. The first network device according to claim 11 or 12, characterized in that, The first subscription request message also includes a combination of any one or more of the following attribute information: location information of the computing node, link status information, and service type identifier. The first computing power information carried in the first ALTO message indicates the computing power information of the first computing node. The first computing node is determined by the first network device from the computing nodes based on the attribute information.
14. The first network device according to any one of claims 9 to 12, characterized in that, The sending module is further configured to send first network information to the second network device. The first network information indicates the network information of the computing node corresponding to the first network device. The network information includes, but is not limited to, any one or more combinations of the following information: location information of the computing node, link status information, supported service type information, and computing power type information.
15. The first network device according to any one of claims 9 to 12, characterized in that, The first network device is a first local ALTO server in the first operator's network, and the second network device is a second local ALTO server in the first operator's network; or The first network device is a local ALTO server of the first operator's network, and the second network device is a global ALTO server of the first operator's network; or The first network device is a global ALTO server for the first operator's network, and the second network device is a global ALTO server for the second operator's network; or The first network device is a local ALTO server in the first operator's network, and the second network device is a local ALTO server in the second operator's network; or The first network device is an ALTO server, and the second network device is an ALTO client. The ALTO server is any one of the following: a local ALTO server of the first operator network, a global ALTO server of the first operator network, a local ALTO server of the second operator network, or a global ALTO server of the second operator network.
16. The first network device according to claim 15, characterized in that, The first network device is the ALTO server, and the second network device is the ALTO client, wherein the ALTO client is a computing power network management system. The receiving module is further configured to receive a third subscription request message sent by the second network device, the third subscription request message being used to request first capability information, the first capability information indicating capability deployment information of the computing node corresponding to the first network device; The sending module is further configured to send a third ALTO message to the second network device based on the ALTO protocol, wherein the third ALTO message carries the first capability information.
17. A computing power information processing system, characterized in that, Includes the first network device as described in any one of claims 9 to 16.