WO2021160113A1 - 部署应用实例和调度应用实例的方法和装置 - Google Patents

部署应用实例和调度应用实例的方法和装置 Download PDF

Info

Publication number
WO2021160113A1
WO2021160113A1 PCT/CN2021/076193 CN2021076193W WO2021160113A1 WO 2021160113 A1 WO2021160113 A1 WO 2021160113A1 CN 2021076193 W CN2021076193 W CN 2021076193W WO 2021160113 A1 WO2021160113 A1 WO 2021160113A1
Authority
WO
WIPO (PCT)
Prior art keywords
management platform
client
application
application instance
request message
Prior art date
Application number
PCT/CN2021/076193
Other languages
English (en)
French (fr)
Inventor
王楠楠
许阳
衣波
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to EP21753267.0A priority Critical patent/EP4096175A4/en
Publication of WO2021160113A1 publication Critical patent/WO2021160113A1/zh
Priority to US17/886,017 priority patent/US20220385586A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/24—Traffic characterised by specific attributes, e.g. priority or QoS
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/24—Traffic characterised by specific attributes, e.g. priority or QoS
    • H04L47/2416—Real-time traffic
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/80—Responding to QoS
    • 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/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
    • H04L41/5041—Network service management, e.g. ensuring proper service fulfilment according to agreements characterised by the time relationship between creation and deployment of a service
    • H04L41/5051—Service on demand, e.g. definition and deployment of services in real time
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/32—Flow control; Congestion control by discarding or delaying data units, e.g. packets or frames
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/40—Support for services or applications
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/34—Network arrangements or protocols for supporting network services or applications involving the movement of software or configuration parameters 
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0268—Traffic management, e.g. flow control or congestion control using specific QoS parameters for wireless networks, e.g. QoS class identifier [QCI] or guaranteed bit rate [GBR]
    • 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/04—Network management architectures or arrangements
    • H04L41/044—Network management architectures or arrangements comprising hierarchical management structures
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/12—Discovery or management of network topologies
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]

Definitions

  • This application relates to the field of edge computing, and in particular to a method and device for deploying and scheduling application instances.
  • edge application instances In the process of deploying edge application instances, users first specify resources, areas, and locations according to their own coverage requirements. Then, the global management platform filters the available edge sites at the location specified by the user and deploys application examples. After that, the user can view the area and geographic location of the application instance.
  • creating edge application instances based on user-specified regions and locations is only a compromise under the current global management platform capabilities, and cannot truly provide edge cloud services with low latency and large traffic.
  • This application provides a method for deploying application instances and scheduling application instances, which can provide users with edge cloud services with high service quality.
  • a method for deploying an application instance includes: a global management platform receives quality of service (QoS) requirement information from a first client, where the QoS requirement information includes the first delay requirement , The second delay demand and the first number of connections, the second delay demand is better than the first delay demand, the QoS demand information is input by the first user to the first client; the global management platform manages The first available site that meets the first delay requirement is selected among the sites; the global management platform deploys one or more first application instances on the first available site, and the number of connectable first application instances is less than or equal to the first available site. A number of connections.
  • QoS quality of service
  • the global management platform selects to deploy an application instance on a site that meets the first delay requirement based on the first delay requirement input by the first user to the first client. Therefore, the application instances deployed by the global management platform can provide edge cloud services with high service quality for the first user's customers.
  • the global management platform selects the first available site that meets the first delay requirement from the managed sites, including: the global management platform selects the first available site according to the first global QoS
  • the information table selects the first available station that meets the first delay requirement from the managed stations, and the first global QoS information table includes the QoS information of the stations managed by the global management platform.
  • the method further includes: the global management platform selects a second application that does not meet the second delay requirement from one or more of the first application instances Examples; the global management platform selects a second available site that meets the second delay requirement from the managed sites; the global management platform deploys the second application instance on the second available site.
  • the global management platform optimizes and updates the deployment location of application instances that do not meet the second delay requirement based on the second delay requirement, so that the optimized application instance can provide the first user's customer with a higher quality edge cloud service.
  • the method further includes: the global management platform sets a resource reservation threshold according to the number of connectable third application instances deployed on the first site under management; In the case that the remaining number of connections of the first site is less than the resource reservation threshold, the global management platform deploys a fourth application instance on the first site, and the QoS information of the fourth application instance is the same as that of the third application instance.
  • the QoS information is the same or equivalent.
  • the method further includes: the global management platform predicts the increase in the number of connections of the first network segment based on historical access data, and the first network segment is the third network segment.
  • the network segment carried by the application instance; the global management platform calculates the number of the fourth application instance according to the increase in the number of connections of the first network segment.
  • the method further includes: the global management platform receives a first request message from a second client or a regional management platform, where the first request message is used to request The second client scheduling application instance, the first request message includes the identification information of the second client; the global management platform according to the second request message and the second global QoS information table, from one or more of the first Available application instances are filtered out of the application instances, and the second global QoS information table includes QoS information of the first application instance.
  • the first request message further includes a third delay requirement input by the second user to the second client.
  • the method further includes: the global management platform schedules an application instance for the second user according to the QoS level of the second user.
  • a method for deploying an application instance includes: a first client receives QoS requirement information input by a first user through a first interface, and the QoS requirement information includes a first delay requirement and a second delay requirement. The delay demand and the first number of connections, the second delay demand is better than the first delay demand; the first client sends the QoS demand information to the global management platform.
  • the global management platform selects to deploy an application instance on a site that meets the first delay requirement based on the first delay requirement input by the first user to the first client. Therefore, the application instances deployed by the global management platform can provide edge cloud services with high service quality for the first user's customers.
  • the first interface includes an application programming interface interface.
  • a method for scheduling an application instance includes: an area management platform receives a second request message from a second client, where the second request message is used to request that the application instance be scheduled for the second client;
  • the second request message includes the identification information of the second client;
  • the area management platform filters out available application instances from one or more fifth application instances according to the second request message and the service QoS information table, and the fifth
  • the application instance is an application instance deployed by the global management platform on the site managed by the regional management platform according to the QoS requirement information from the first client, and the service QoS information table includes the QoS information of the fifth application instance.
  • the regional management platform schedules application instances for the second client based on the request message from the second client and the service QoS information table, which can provide users with high-quality edge cloud services.
  • the second request message further includes a third delay requirement input by the second user to the second client.
  • the method further includes: the area management platform schedules an application instance for the second user according to the QoS level of the second user.
  • the method further includes: the area management platform sends a first request message to the global management platform according to the second request message, and the first request message is used to request The second client schedules an application instance.
  • the regional management platform can request the global management platform to schedule the application instances for the second client.
  • a global management platform including a transceiving unit and a processing unit: the transceiving unit is used to receive QoS requirement information from a first client, and the QoS requirement information includes a first delay requirement and a second delay requirement. Demand and the first number of connections, the second delay demand is better than the first delay demand, and the QoS demand information is input by the first user to the first client; the processing unit is used to select from the managed sites to meet The first available site for the first delay requirement; the processing unit is further configured to deploy one or more first application instances on the first available site, and the number of connectable first application instances is less than or equal to the first connection quantity.
  • the processing unit is specifically configured to select the first available site that meets the first delay requirement from the managed sites according to the first global QoS information table, the The first global QoS information table includes QoS information of sites managed by the global management platform.
  • the processing unit is further configured to select a second application instance that does not meet the second delay requirement from one or more of the first application instances; the The processing unit is further configured to select a second available site that meets the second delay requirement from the managed sites; the processing unit is also configured to deploy the second application instance on the second available site.
  • the processing unit is further configured to set a resource reservation threshold according to the number of connectable third application instances deployed on the first site under management; In the case that the number of remaining connections of a site is less than the resource reservation threshold, the processing unit is further configured to deploy a fourth application instance on the first site, the QoS information of the fourth application instance and the QoS of the third application instance The information is the same or equivalent.
  • the processing unit is further configured to predict the increase in the number of connections of the first network segment based on historical access data, and the first network segment is the bearer of the third application instance.
  • the processing unit is also used to calculate the number of the fourth application instance according to the increase in the number of connections of the first network segment.
  • the transceiving unit is further configured to receive a first request message from a second client or an area management platform, and the first request message is used to request for the second A client scheduling application instance, the first request message includes the identification information of the second client; the processing unit is further configured to obtain information from one or more of the first applications according to the second request message and the second global QoS information table Available application instances are filtered out in the instance, and the second global QoS information table includes QoS information of the first application instance.
  • the first request message further includes a third delay requirement input by the second user to the second client.
  • the processing unit is further configured to schedule an application instance for the second user according to the QoS level of the second user.
  • a client including a receiving unit and a sending unit: the receiving unit is configured to receive QoS requirement information input by a first user through a first interface, and the QoS requirement information includes a first delay requirement, a second The second delay demand and the first number of connections, the second delay demand is better than the first delay demand; the transceiver unit is used to send the QoS demand information to the global management platform.
  • the first interface includes an application programming interface interface.
  • an area management platform including a transceiving unit and a processing unit: the transceiving unit is used to receive a second request message from a second client, and the second request message is used to request scheduling for the second client
  • the second request message includes the identification information of the second client
  • the processing unit is configured to filter out available application examples from one or more fifth application instances according to the second request message and the service QoS information table
  • the fifth application instance is an application instance deployed by the global management platform on a site managed by the regional management platform according to the QoS requirement information from the first client, and the service QoS information table includes the QoS information of the fifth application instance.
  • the second request message further includes a third delay requirement input by the second user to the second client.
  • the processing unit is further configured to schedule an application instance for the second user according to the QoS level of the second user.
  • the transceiver unit is further configured to send a first request message to the global management platform according to the second request message, where the first request message is used to request the second Client scheduling application instance.
  • a global management platform including a processor.
  • the processor is coupled with the memory and can be used to execute instructions in the memory to implement the foregoing first aspect or the method in any one of the possible implementation manners of the first aspect.
  • a client including a processor.
  • the processor is coupled with the memory and can be used to execute instructions in the memory to implement the foregoing second aspect or the method in any one of the possible implementation manners of the second aspect.
  • an area management platform including a processor.
  • the processor is coupled with the memory and can be used to execute instructions in the memory to implement the third aspect or the method in any one of the possible implementation manners of the third aspect.
  • a processor including: an input circuit, an output circuit, and a processing circuit.
  • the processing circuit is configured to receive a signal through the input circuit, and transmit a signal through the output circuit, so that the processor executes any one of the foregoing first to third aspects or any one of the first to third aspects. In the method.
  • the above-mentioned processor may be a chip, the input circuit may be an input pin, the output circuit may be an output pin, and the processing circuit may be a transistor, a gate circuit, a flip-flop, and various logic circuits.
  • the input signal received by the input circuit may be received and input by, for example, but not limited to, a receiver, and the signal output by the output circuit may be, for example, but not limited to, output to the transmitter and transmitted by the transmitter, and the input circuit and output
  • the circuit can be the same circuit, which is used as an input circuit and an output circuit at different times.
  • the embodiments of the present application do not limit the specific implementation manners of the processor and various circuits.
  • a processing device including a processor and a memory.
  • the processor is used to read instructions stored in the memory, receive signals through a receiver, and transmit signals through a transmitter to execute any one of the first to third aspects or any one of the first to third aspects mentioned above. Methods.
  • processors there are one or more processors, and one or more memories.
  • the memory may be integrated with the processor, or the memory and the processor may be provided separately.
  • the memory can be a non-transitory (non-transitory) memory, such as a read only memory (ROM), which can be integrated with the processor on the same chip, or can be set in different On the chip, the embodiment of the present application does not limit the type of the memory and the setting mode of the memory and the processor.
  • ROM read only memory
  • sending instruction information may be a process of outputting instruction information from the processor
  • receiving capability information may be a process of receiving input capability information by the processor.
  • the processed output data may be output to the transmitter, and the input data received by the processor may come from the receiver.
  • the transmitter and receiver can be collectively referred to as a transceiver.
  • the processing device in the above-mentioned eleventh aspect may be a chip, and the processor may be implemented by hardware or software.
  • the processor When implemented by hardware, the processor may be a logic circuit, an integrated circuit, etc.; When implemented, the processor may be a general-purpose processor, which is implemented by reading software codes stored in the memory.
  • the memory may be integrated in the processor, may be located outside the processor, and exist independently.
  • a computer program product includes: a computer program (also called code, or instruction), which when the computer program is executed, causes the computer to execute the first to the first
  • a computer program also called code, or instruction
  • the method in the three aspects or any one of the possible implementation manners of the first to third aspects.
  • a computer-readable medium stores a computer program (also called code, or instruction) when it runs on a computer, causing the computer to execute the first to the first.
  • a computer program also called code, or instruction
  • an edge cloud scheduling system which includes the aforementioned global management platform, a first client, and a regional management platform.
  • Fig. 1 is a schematic diagram of an application scenario provided by an embodiment of the present application.
  • FIGS. 2 to 4 are schematic flowcharts of methods for deploying application instances provided by embodiments of the present application.
  • Fig. 5 is a schematic flowchart of a method for scheduling an application instance provided by an embodiment of the present application.
  • 6 to 7 are schematic block diagrams of the global management platform provided by embodiments of the present application.
  • FIGS. 8 to 9 are schematic block diagrams of a first client provided in an embodiment of the present application.
  • 10 to 11 are schematic block diagrams of area management platforms provided by embodiments of the present application.
  • Edge cloud computing is a cloud computing platform built on edge infrastructure based on the core of cloud computing technology and the capabilities of edge computing. Form a flexible cloud platform with comprehensive capabilities in computing, network, storage, and security at the edge, and form an end-to-end technical architecture of "cloud edge-end three-body synergy" with the central cloud and IoT terminals.
  • intelligent data analysis and other tasks are processed at the edge to reduce response delays, reduce cloud pressure, reduce bandwidth costs, and provide cloud services such as network-wide scheduling and computing power distribution.
  • Edge cloud is a kind of public cloud, based on small sites with extensive coverage, generally content delivery network (CDN), Internet access point (POP), mobile edge computing (mobile edge computing, MEC) ), each node in the form of a small cluster provides public cloud services to the outside. It has the characteristics of low latency, 5ms latency in the general area, and large bandwidth (40Gb-600Gb+). The number will reach more than one thousand, or even tens of thousands. Generally, it is also called fog computing, edge computing, edge cloud, cloudlet, etc. in the industry.
  • Region and available zone (AZ) are concepts involved in cloud computing.
  • Region refers to the area where the data center is located, which can be a region (South China) or a city (Shenzhen, Dongguan);
  • the availability zone refers to the physical area where the computer room and site are located, and has the characteristics of energy consumption and network independence.
  • An area usually contains multiple low-latency interconnected available areas, which are used for scenarios and services such as disaster recovery, backup and load balancing in the same area. The vast majority of cloud computing services do not support cross-regional.
  • Edge cloud users are pursuing the ultimate experience. In other words, the ultimate need for edge cloud users is the guarantee of delay and traffic.
  • users first specify resources, regions, and locations according to their own coverage requirements. Then, the global management platform filters available sites and deploys application instances at locations specified by users. After that, the user can view the area and geographic location of the application instance.
  • creating edge application instances based on user-specified regions and locations is only a compromise under the current global management platform capabilities, and cannot truly provide edge cloud services with low latency and large traffic.
  • Application examples can be virtual machines, containers, or software modules.
  • the embodiments of the present application provide a method for deploying application instances and scheduling application instances to provide users with edge cloud services with low latency and large traffic.
  • the first user mentioned in this embodiment of the application is a user using client #1
  • the second user is a user using client #2.
  • the first application instance is the initially deployed application instance
  • the second application instance is the application instance that does not meet the second delay requirement in the first application instance
  • the third application instance is the final deployed application instance
  • the fourth application instance is in the When the third application example is not enough, a new application example is added.
  • Fig. 1 shows a schematic diagram of an application scenario applicable to the method provided in the embodiment of the present application.
  • the application scenario of this application may be in the field of edge computing.
  • the global management platform manages all sites in multiple edge clouds. For example, in Figure 1, the global management platform manages the sites in Edge Cloud #1 and the sites in Edge Cloud #2.
  • the edge cloud can be composed of an edge cluster, which can include multiple processing devices. Each processing device in the edge cloud can be connected to other clients not in the edge cloud, and information can be collected through other clients and transmitted to the edge cloud In the regional management platform, it is transmitted to the global management platform or processed at the regional management platform.
  • edge cloud #1 is composed of site #1, site #2, and regional management platform #1, and regional management platform #1 can manage site #1 and site #2.
  • Edge cloud #2 is composed of site #3, site #4, and regional management platform #2, and regional management platform #2 can manage site #3 and site #4.
  • the physical form of the site can be a single processing device, and the global management platform can deploy application instances on the site.
  • Application instances refer to specific applications deployed on different sites for the same application service, that is, one application service can correspond to multiple application instances. As shown in Figure 1, multiple application instances (application instance #1 to application instance #5) corresponding to the same application service can be deployed on the same or different sites. For example, application instance #1 and application instance #2 are deployed on site #1, application instance #3 is deployed on site #2, and application instance #4 and application instance #5 are deployed on site #3.
  • the client connected to the processing device may be an access terminal, a user unit, a user station, a mobile station, a mobile station, a remote station, a remote terminal, a mobile device, a user terminal, a terminal, a wireless communication device, a user agent, or a user Device.
  • the physical form of a site can also be a cellular phone, a cordless phone, a session initiation protocol (session initiation protocol, SIP) phone, a wireless local loop (WLL) station, a personal digital assistant (PDA), Handheld devices with wireless communication functions, computing devices, or other processing devices connected to wireless modems, vehicle-mounted devices, wearable devices, etc., are not limited in the embodiments of the present application.
  • Fig. 2 is a method for deploying an application instance provided by an embodiment of the present application.
  • the method 200 shows a flow of interaction between a global management platform and a client.
  • the global management platform and the client may be, for example, the global management platform and the client in FIG. 1, respectively.
  • the method 200 includes S201 to S203, and each step is described in detail below.
  • Client #1 (an example of the first client) sends QoS requirement information to the global management platform.
  • the global management platform receives the QoS requirement information from the client #1.
  • the QoS demand information includes a first delay demand, a second delay demand, and a first number of connections, and the second delay demand is better than the first delay demand.
  • the QoS requirement information is input by the first user to client #1.
  • the first delay requirement may be the maximum delay acceptable to the user
  • the second delay requirement may be the delay desired by the user
  • the first connection quantity may be the maximum connectable quantity of the application instance.
  • the first user can input QoS requirement information through an application program interface (API).
  • API application program interface
  • the existing edge cloud service API interface does not have relevant settings for service QoS requirement information. Therefore, the embodiment of the present application adds information related to service QoS on the basis of the existing edge cloud service API interface.
  • the detailed description related to the demand information forms an edge cloud service API interface based on the business QoS demand information.
  • An example of the edge cloud service API interface provided by the embodiment of the present application is as follows:
  • the assignment method of the parameter "demand" in the area description is removed, that is, the description of the number of instances is removed.
  • the number of instances can be determined according to the parameters in the access capability. For example, it can be calculated according to formula (1):
  • InstanceNum (minlinksNum/maxlinksPerInstance)*120% formula (1)
  • the parameter "QoS” is added to the resource description of the existing solution, and the description about the QoS requirement information is added.
  • the parameter “Delay” is a self-defined data structure, which represents the description of the delay QoS.
  • the parameter “Access capability” is also a self-defined data structure, which represents the description of the number of access QoS.
  • the “Delay” structure contains two parameters: the parameter "max” represents the maximum delay; the parameter “expection” represents the expected delay.
  • the “Access capability” structure contains three parameters: the parameter “maxlinksPerInstance” represents the maximum number of connections per application instance; the parameter “maxlinksNum” represents the maximum number of connections per site; the parameter “minlinksNum” represents each site The minimum number of connections.
  • the first user can input the first delay requirement, the second delay requirement, and the parameters related to the configuration of the first connection quantity to the client #1.
  • the above-mentioned parameter assignment is only an example, and should not be limited to the embodiment of the present application. It should be understood that the first user can assign the above-mentioned parameter according to his own needs.
  • the client #1 may also predict the QoS requirement information according to the time delay requirement information input by the first user history, and then send the QoS requirement information to the global management platform.
  • S202 The global management platform selects the first available site that meets the first delay requirement from the managed sites.
  • the global management platform selects the first available site that meets the first delay requirement from all or part of the managed sites.
  • the global management platform can filter out the first available site that meets the first delay requirement information according to the QoS information of the site stored locally.
  • the global management platform may establish a first global QoS information table, and the first global QoS information table includes QoS information of the site. Then, the global management platform filters out the first available site that meets the first QoS requirement information according to the first global QoS information table.
  • the method for the global management platform to establish the first global QoS information table may be:
  • the global management platform establishes the first global QoS information table according to the managed site and the designated operator network segment.
  • the designated operator may be, for example, China Mobile, or China Telecom, or China Unicom, or other operators, which is not limited in the embodiment of the application. It can be understood that the network segments corresponding to different operators are different, and the corresponding network segments are different for different regions. Therefore, in the case of a designated operator and a designated area, the corresponding network segment is also fixed.
  • Table 1 shows an example of the first QoS information table.
  • the site identifier is used to identify the site, and the site identifier may be a different number assigned to each site by the global management platform.
  • the correspondence between the site, the network segment, and the delay is: the communication delay for a client with an Internet Protocol (IP) address belonging to the network segment to access the site.
  • IP Internet Protocol
  • Table 1 the communication delay for clients with IP addresses belonging to 10.1.1.1-10.2.2.2 to access site #1 is 5ms; when the clients with IP addresses belonging to 10.3.3.3-10.4.4.4 access the communication of site #1 The delay is 15ms; the communication delay for the client whose IP address belongs to 10.6.6.0-10.7.7.7 to access site #1 is 25ms.
  • Table 1 also shows the communication delays when clients with IP addresses belonging to different network segments respectively access site #2 to site #4.
  • the corresponding relationship between the site and the area is: the site is set in the area. As shown in Table 1, edge #1 to site #4 are set in the same area.
  • the global management platform knows from Table 1 that the communication delay for all clients to access edge point #4 is 25 ms, and therefore, station #4 is unavailable. Therefore, the global management platform can determine site #1 to site #3 as the first available site.
  • S203 The global management platform deploys one or more first application instances on the first available site.
  • the connectable number of the one or more first application instances is less than or equal to the first connection number.
  • the global management platform can randomly deploy application instance #1 to application instance #5 on site #1 to site #3.
  • the global management platform randomly selects site #1 to site #4 in the area designated by the first user, and randomly deploys application instance #1 and application instance #2 on site #1, and the application instance #3 is deployed on site #2, and application instance #4 and application instance #5 are deployed on site #3 respectively.
  • the global management platform allocates the network segment that each application instance is responsible for, and calculates the communication delay for the client to access each application instance.
  • application example #1 is responsible for 10.1.1.1-10.2.2.2
  • application example #2 is responsible for 10.3.3.3-10.4.4.
  • application example #3 is responsible for 10.6.6.6-10.7.7.7
  • application example #4 is responsible for 10.1.1.1- 10.2.2.2
  • Application Example #5 is responsible for 10.3.3.3-10.4.4.4.
  • the communication delay for the client to access the application instance can also be understood as the communication delay for the client to access the site where the application instance is located.
  • the communication delay of client access site #1 with IP addresses belonging to 10.1.1.1-10.2.2.2 is 5ms, so it can be seen that client access application instance #1 with IP addresses belonging to 10.1.1.1-10.2.2.2
  • the communication delay is also 5ms.
  • the communication delay of client access application instance #2 with IP addresses belonging to 10.3.3.3-10.4.4.4 is 15ms; client access application instance# with IP addresses belonging to 10.6.6.6--10.7.7.7
  • the communication delay of 3 is 5ms; the communication delay of client access application instance# with IP addresses belonging to 10.1.1.1-10.2.2.2 is 25ms; the communication delay of client access application instance# belonging to IP addresses 10.3.3.3-10.4.4.4#
  • the communication delay of 5 is 5ms.
  • the global management platform does not perform the step of allocating the network segment responsible for each application instance.
  • each application instance is responsible for a unique network segment in this area.
  • the global management platform may also adjust the deployment location of the first application instance according to the second delay requirement.
  • the method 200 may further include S204 to S206.
  • S204 The global management platform selects a second application instance that does not meet the second delay requirement from the deployed one or more first application instances.
  • the IP address belongs to 10.1.1.1-10.2.2.2
  • the communication delay of client access application instance #1 is 5ms
  • the communication delay of client access application instance #2 with an IP address of 10.3.3.3-10.4.4.4 is 15ms
  • the IP address belongs to
  • the communication delay of the client accessing application instance #3 from 10.6.6.6-10.7.7.7 is 5ms
  • the communication delay of the client accessing application instance #4 with the IP address belonging to 10.1.1.1-10.2.2.2 is 25ms
  • the IP address belongs to 10.3.3.3-10.4.4.4
  • the communication delay of client access to application example #5 is 5ms.
  • application example #2 and application example #4 can be determined as second application examples that do not meet the second delay requirement.
  • S205 The global management platform selects a second available site that meets the second delay requirement from the managed sites.
  • the global management platform selects the second available site that meets the second delay requirement from all or part of the managed sites.
  • the global management platform can filter out the second available site that meets the second delay requirement information according to the QoS information of the site stored locally.
  • the global management platform may filter out the second available sites that meet the second delay requirement according to the first global QoS information table.
  • S206 The global management platform deploys the second application instance on the second available site.
  • the global management platform After the global management platform selects the second application instance that does not meet the second delay requirement, it can query the optimal deployment location of the network segment responsible for the second application instance according to the first QoS information table, and move the second application instance. Then, after the second application instance moves, the total communication delay for the client to access all application instances is calculated. If it is better than the original total communication delay, the deployment location of the second application instance is changed.
  • the scheduling target of the global management platform to move the deployment location of the first application instance is all network segments provided by the designated operator within the coverage of the first application instance.
  • termination conditions for the above deployment location update process are: (1) the coverage network segment of all application instances meets the user's expected delay; or (2) the scheduling time is greater than 1 minute. As long as any one of the termination conditions is reached, the above update process is terminated.
  • the update process will also be terminated. For another example, within one minute, the update process of application instance #2 and application instance #4 is completed. At this time, if the coverage network segments of all application instances meet the user's expected delay, the update process is terminated.
  • the method 200 may further include S207 and S208.
  • S207 The global management platform sets a resource reservation value according to the number of connectable third application instances deployed on the first site.
  • the number of connections that can be connected may be the maximum number of connections of the deployed third application instance.
  • the resource reservation threshold may be, for example, 20% of the maximum number of connections of the third application instance. And in the case that the remaining number of connections of the third application instance is less than the resource reservation threshold, the deployment of new application instances is added in advance to meet the access of more clients.
  • the global management platform can set different resource reservation thresholds.
  • the global management platform can set a fixed resource reservation threshold. For example, for a site with a QoS level of 99, the global management platform can set 10% of the site’s maximum number of connections as the resource reservation threshold; for a site with a QoS level of 9999, the global management platform can set the maximum number of connections for the site 40% is set as the resource reservation threshold; for the site with the highest priority, the global management platform can also set 100% of the site’s maximum number of connections as the resource reservation threshold.
  • the global management platform can dynamically adjust the resource reservation threshold according to historical access data over a period of time (for example, within a year). If in a period of time, the number of clients #2 visiting a site of a certain QoS level is large, increase the resource reservation threshold; if in a period of time, the number of clients #2 visiting a site of a certain QoS level is larger. If less, reduce the resource reservation threshold. For example, in the last year, the number of client #2 accessing a site with a QoS level of 9999 was very small. Therefore, the global management platform can reduce the reserved resources from 40% to 20%.
  • S208 The global management platform deploys a fourth application instance on the first site.
  • the QoS information of the fourth application instance is the same or equivalent to the QoS information of the third application instance. For example, if the third application instance is deployed on the first site, and the network segment responsible for the third application instance is 10.1.1.1-10.2.2.2, and the maximum number of connections is 2000, the fourth application instance is also deployed on the first site. And the fourth application instance is also responsible for 10.1.1.1-10.2.2.2, and the maximum number of connections is 2000.
  • the relevant information of the deployment of the third application instance can be determined.
  • the global management platform can also determine the number of fourth application instances.
  • the method for the global management platform to determine the number of fourth application instances may include the following steps:
  • Step 1 The global management platform predicts the increase in the number of connections in the first network segment based on historical access data.
  • the first network segment is a network segment carried by the third application instance.
  • the global management platform counts the network segment where the IP address of each client accessing the same service domain name is located; then the global management platform counts the number of clients whose IP address belongs to the first network segment; then the global management platform Predict the increase in the number of connections of the first network segment based on the number of the clients. For example, the increase in the number of connections in the first network segment may be 100 times the number of clients corresponding to the first network segment.
  • Step 2 The global management platform calculates the number of fourth application instances that need to be added based on the predicted increase in the number of connections in the first network segment.
  • the number of fourth application instances that need to be added is equal to the increase in the number of connections in the first network segment divided by the maximum number of connections in the fourth application instance.
  • the maximum number of connections of the fourth application instance is equal to the maximum number of connections of the third application instance.
  • Step 3 The global management platform deploys the fourth application instance on the first site.
  • the global management platform can deploy application instances according to user-acceptable delay demand information, so that the global management platform can provide users with services required by users. Further, the global management platform can also optimize and update the deployment location of the application instance according to the delay requirement information expected by the user, so that the global management platform can provide users with better services. For example, it can provide users with time-delay and high-traffic services.
  • the global management platform can record the application instance identifier, the network segment that the application instance is responsible for, and the QoS information of the application instance, and establish a second QoS information table.
  • Table 2 shows an example of the second QoS information table.
  • the application instance identifier is used to identify the application instance, the application instance identifier may be a number assigned to each application instance by the global management platform, and the number of connections is the number of users currently connected to the application instance.
  • Fig. 5 shows a schematic flowchart of a method for scheduling an application instance provided by an embodiment of the present application. As shown in FIG. 5, the method 300 includes S301 to S304, and each step is described in detail below.
  • the area management platform receives a request message #1 (an example of the second request message) from the client #2 (an example of the second client), and the request message #1 is used to request the area management platform to serve the client Terminal #2 allocates application examples.
  • the request message #1 carries the address and IP information of the client #2.
  • the request message #1 may also carry the third delay requirement input by the second user of the client terminal #2.
  • the third delay requirement may be the expected delay of the second user.
  • the request message #1 may be sent by the second user using the client #2 to the area management platform through the client #2.
  • the client #2 sends the request message #1 to the area management platform closest to the client #2.
  • the service domain name accessed by the second user through client #2 is 1111, and the edge cloud closest to client #2 is edge cloud #1. Therefore, client #2 is in the edge cloud #1
  • the area management platform #1 sends a request message #1 to request the area management platform #1 to allocate an application instance to it.
  • the address information carried in the request message #1 is the address where the client #2 is located, and the IP information of the client #2 carried in the request message #1 is the IP address of the client.
  • the IP address of the client #2 is 10.1.1.3.
  • the area management platform filters the available application instances from one or more fifth application instances according to the service QoS information table, and redirects to the IP address of the optimal application instance.
  • the service QoS information table is established by the regional management platform for the sites included in the edge cloud to which it belongs and the application instances deployed on the sites.
  • the fifth application example is an application example deployed by the global management platform on the site managed by the regional management platform according to the QoS requirement information from the client #1.
  • the service QoS information table established by the area management platform #2 is shown in Table 4.
  • the area management platform After the area management platform receives the request message #1 from the client #2, it can first allocate an application instance to the client #2 according to the address information in the request message #1. Then, the regional management platform determines the network segment where the IP address is located according to the IP address carried in the request message #1; then, the regional management platform finds the application instance responsible for the network segment according to the service QoS information table; finally, according to the application instance The corresponding QoS information determines whether the application instance is available.
  • the application instance is unavailable, and if it has not reached the maximum value, the application instance is available.
  • the area management platform may also determine whether the communication delay corresponding to the application instance meets the third delay requirement. If the third delay requirement is required, the application instance is available, and if the third delay requirement is not met, the application instance is unavailable.
  • the IP address of client #2 is 10.1.1.3.
  • the area management platform #1 After the area management platform #1 receives the request message #1 from client #2, it allocates application instance #1 to the client #2 nearby. Then, according to the IP address carried in the request message #1, it is determined that the network segment where the IP address is located is 10.1.1.1. Then, the area management platform #1 finds the application examples responsible for 10.1.1.1 as application example #1 and application example #4 according to Table 3.
  • the parameter "maxlinksPerInstance" is assigned a value of 2000 as an example.
  • the regional management platform knows that the current number of connections of application instance #1 has reached the maximum number of connections. Therefore, the application Instance #1 is not available; while the current number of connections for application #4 is 1000, which has not reached the maximum number of connections, therefore, application #4 is available.
  • the communication delay corresponding to application example #4 is 5ms. If the request message #1 sent by the client to the area management platform #1 carries the third delay requirement, and the third delay requirement is less than 5ms, then Application example #4 is also not available; if the third delay requirement is greater than or equal to 5 ms, application example #4 is available.
  • the method 300 may also perform S304-S305.
  • the area management platform sends a request message #2 (an example of the first request message) to the global management platform, where the request message #2 is used to request the client #2 to be allocated an application instance.
  • the request message #2 corresponds to the content of the request message #1. For example, if request message #1 carries the address and IP information of client #2, request message #2 also carries the address and IP information of client #2; for another example, request message #1 carries the address and IP information of client #2. The address, IP information, and the third delay requirement, the request message #2 also carries the address, IP information, and the third delay requirement of the client #2.
  • the global management platform filters the available application instances from one or more first application instances according to the second QoS information table, and directs them to the IP address of the optimal application instance.
  • the global management platform After receiving the request message #2 from the regional management platform, the global management platform first allocates an application instance to the client #2 according to the address information carried in the request message #2; then, it determines the location of the IP address based on the IP address Then, the global management platform finds the application instance responsible for the network segment according to the service QoS information; finally, it judges whether the application instance is available according to the QoS information corresponding to the application instance.
  • the application instance is unavailable, and if it has not reached the maximum value, the application instance is available.
  • the global management platform may also determine whether the communication delay corresponding to the application instance meets the third delay requirement. If the third delay requirement is met, the application instance is available, and if the third delay requirement is not met, the application instance is unavailable.
  • the IP address of client #2 is 10.3.3.5.
  • the global management platform After the global management platform receives the request message #2 from the regional management platform #1, it assigns application instance #1 to the client #2 nearby, and then According to the IP address carried in the request message #2, it is determined that the network segment where the IP address is located is 10.3.3.3.
  • the global management platform finds the application examples responsible for 10.3.3.3 according to Table 2 as application example #2 and application example #5.
  • the parameter "maxlinksPerInstance" is assigned a value of 2000 as an example.
  • the global management platform shows that the current number of connections of application instance #2 and application instance #5 have not reached the current number of connections. The maximum number of connections, therefore, application example #2 and application example #5 are available.
  • the communication delays corresponding to application instance #2 and application instance #5 are both 5ms. If the request message #2 sent by the regional management platform #1 to the global management platform carries the third delay requirement, and the third If the delay requirement is less than 5 ms, application instance #2 and application instance #5 are unavailable; if the third delay requirement is greater than or equal to 5 ms, application instance #2 and application instance #5 are available.
  • the global management platform determines that there is an available application instance according to the request message #2 and the second QoS information table, the global management platform sends a response message to the client, and the response message carries the identifier of the available application instance.
  • the response message is also used to redirect the client device to the edge cloud of the site where the available application instance is managed.
  • the global management platform determines that there is no available application instance according to the request message #2 and the second QoS information table, the global management platform initiates resource scheduling and adds new application instances to meet the user's service request.
  • the regional management platform or the global management platform may schedule the application instance for the client #2 according to the QoS level of the client #2.
  • the regional management platform or the global management platform preferentially schedules application instances for client #2 with a high QoS level.
  • the embodiment of this application does not limit how to determine the QoS level of client #2.
  • the QoS level management device sets the QoS level of the client #2 according to the ratio of the total number of satisfied requests of the client #2 to the total number of requests of the client #2.
  • the statistics of this ratio can be in units of years. If the ratio of the total number of satisfied requests from client #2 to the total number of requests from client #2 is 99%, the QoS level management device sets the QoS level of client #2 to 99; if client #2 is satisfied The ratio of the total number of requests from client #2 to the total number of requests from client #2 is 99.99%, and the QoS level management device sets the QoS level of client #2 to 9999.
  • the client #2 with a high QoS level can preempt the resources of the client #2 with a low QoS level.
  • client #2 with a QoS level of 9999 can preempt the calculation example resources of client #2 with a QoS level of 99.
  • the above in conjunction with Figure 3 shows the process of the end client requesting the regional management platform to allocate an application instance.
  • the client #1 can also directly send the request message #1 to the global management platform to request the global management platform cloud to be the client Distributed application examples at the end.
  • the method for the client #1 to directly request the global management platform to allocate an application instance can refer to the descriptions of S303 to S304 above. For the sake of brevity, details are not repeated in this embodiment of the application.
  • FIG. 6 is a schematic block diagram of a global management platform 500 provided by an embodiment of the present application.
  • the global management platform 500 may include: a transceiver unit 510 and a processing unit 520.
  • the global management platform 500 may include a unit for executing the method 200 in FIG. 2 to FIG. 4 and the method executed by the global management platform in the method 300 in FIG. 5.
  • each unit in the global management platform 500 and other operations and/or functions described above are used to implement the corresponding processes of the method 200 in FIG. 2 to FIG. 4 and the method 300 in FIG. 5, respectively. It should be understood that the specific process for each unit to execute the foregoing corresponding steps has been described in detail in the foregoing method embodiment, and is not repeated here for brevity.
  • the transceiving unit in the global management platform 500 may correspond to the communication interface 620 in the global management platform 600 shown in FIG. 7, and the processing unit 520 in the global management platform 500 may correspond to the communication interface 620 shown in FIG.
  • the processor 610 in the global management platform 600 may correspond to the communication interface 620 in the global management platform 600.
  • FIG. 7 is a schematic block diagram of a global management platform 600 provided by an embodiment of the present application.
  • the global management platform 600 may include: a communication interface 620, a processor 610, and a memory 630.
  • the global management platform 600 may further include a bus 640.
  • the communication interface 620, the processor 610, and the memory 630 may be connected to each other through a bus 640; the bus 640 may be a peripheral component interconnect standard (PCI) bus or an extended industry standard architecture (EISA) Bus and so on.
  • the bus 640 can be divided into an address bus, a data bus, a control bus, and so on. For ease of representation, only one thick line is used in FIG. 7, but it does not mean that there is only one bus or one type of bus.
  • the memory 630 may be used to store program codes and data executed by the computer system. Therefore, the memory 630 may be a storage unit inside the processor 610, or an external storage unit independent of the processor 610, or may include a storage unit inside the processor 610 and an external storage unit independent of the processor 610. part.
  • the processor 610 may be composed of one or more general-purpose processors, such as a central processing unit (CPU), a general-purpose processor, a digital signal processor (digital signal processor, DSP), and an application-specific integrated circuit (application-specific integrated circuit). Specific integrated circuit (ASIC), field programmable gate array (FPGA) or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. It can implement or execute various exemplary logical blocks, modules, and circuits described in conjunction with the disclosure of this application.
  • the processor may also be a combination for realizing computing functions, for example, including a combination of multiple microprocessors, a combination of DSP and microprocessor, and so on.
  • the processor 610 may be used to run programs for processing functions in related program codes. In other words, the processor 610 executes the program code to realize the functions of determining the module and creating the module. For details about the functions of the determining module and the creating module, reference may be made to the relevant description in the foregoing embodiment.
  • the processor 610 is configured to run related program codes to implement the methods described in S202 to S208 shown in FIGS. 2 to 4 in this application, or to implement the above The method described in S304 shown in FIG. 5, and/or other steps for implementing the technology described herein, etc., are not detailed and limited herein in this application.
  • the communication interface 620 may be a wired interface (such as an Ethernet interface) or a wireless interface (such as a cellular network interface or using a wireless local area network interface) for communicating with other modules/devices.
  • a wired interface such as an Ethernet interface
  • a wireless interface such as a cellular network interface or using a wireless local area network interface
  • the memory 630 may include volatile memory (volatile memory), such as random access memory (random access memory, RAM); the memory may also include non-volatile memory (non-volatile memory), such as read-only memory (read-only memory). memory, ROM), flash memory (flash memory), hard disk drive (HDD), or solid-state drive (SSD); the memory 630 may also include a combination of the foregoing types of memories.
  • volatile memory volatile memory
  • RAM random access memory
  • non-volatile memory non-volatile memory
  • read-only memory read-only memory
  • memory read-only memory
  • ROM read-only memory
  • flash memory flash memory
  • HDD hard disk drive
  • SSD solid-state drive
  • the memory 630 may be used to store a set of program codes, so that the processor 610 can call the program codes stored in the memory 630 to implement the functions of the communication module and/or the processing module involved in the embodiment of the present invention.
  • the global management platform 600 can be caused to execute the method in the foregoing method embodiment 200 or 300.
  • FIG. 8 is a schematic block diagram of a first client 700 provided by an embodiment of the present application.
  • the first client 700 may include: a receiving unit 710 and a sending unit 720.
  • the first client 700 may include a unit for executing the method executed by the first client in the method 200 in FIG. 2.
  • the units in the first client 700 and the other operations and/or functions described above are respectively intended to implement the corresponding processes of the method 200 in FIGS. 2 to 4. It should be understood that the specific process for each unit to execute the foregoing corresponding steps has been described in detail in the foregoing method embodiment, and is not repeated here for brevity.
  • receiving unit and the sending unit in the first client 700 may correspond to the transceiver 820 in the first client 800 shown in FIG. 9.
  • FIG. 9 is a schematic block diagram of a first client 800 provided in an embodiment of the present application.
  • the first client 800 includes a processor 810 and a transceiver 820.
  • the processor 810 is coupled with the memory, and is configured to execute instructions stored in the memory to control the transceiver 820 to send signals and/or receive signals.
  • the first client 800 further includes a memory 830 for storing instructions.
  • processor 810 and the memory 830 may be combined into one processing device, and the processor 810 is configured to execute the program code stored in the memory 830 to implement the foregoing functions.
  • the memory 830 may also be integrated in the processor 810 or independent of the processor 810.
  • the transceiver 820 may include a receiver (or referred to as a receiver) and a transmitter (or referred to as a transmitter).
  • the transceiver may further include an antenna, and the number of antennas may be one or more.
  • the first client 800 may include a unit for executing the method executed by the first client in the method 200 in FIG. 2.
  • the units in the first client 800 and the other operations and/or functions described above are used to implement the corresponding processes of the method 200 in FIGS. 2 to 4, respectively. It should be understood that the specific process for each unit to execute the foregoing corresponding steps has been described in detail in the foregoing method embodiment, and is not repeated here for brevity.
  • FIG. 10 is a schematic block diagram of an area management platform 1000 provided by an embodiment of the present application.
  • the area management platform 1000 may include: a transceiver unit 1010 and a processing unit 1020.
  • the area management platform 1000 may include a unit for the method executed by the area management platform in the method 300 in FIG. 5.
  • the units in the area management platform 1000 and the other operations and/or functions described above are used to implement the corresponding process of the method 300 in FIG. 5. It should be understood that the specific process for each unit to execute the foregoing corresponding steps has been described in detail in the foregoing method embodiment, and is not repeated here for brevity.
  • transceiver unit in the area management platform 1000 may correspond to the communication interface 1120 in the area management platform 1100 shown in FIG. 11, and the processing unit 1020 in the area management platform 1000 may correspond to the communication interface shown in FIG. The processor 1110 in the area management platform 1100.
  • FIG. 11 is a schematic block diagram of an area management platform 1100 according to an embodiment of the present application.
  • the area management platform 1100 may include: a communication interface 1120, a processor 1110, and a memory 1130.
  • the area management platform pipe 1100 may further include a bus 1140.
  • the communication interface 1120, the processor 1110, and the memory 1130 may be connected to each other through a bus 1140; the bus 1140 may be a PCI bus, an EISA bus, or the like.
  • the bus 1140 can be divided into an address bus, a data bus, a control bus, and so on. For ease of representation, only one thick line is used to represent in FIG. 11, but it does not mean that there is only one bus or one type of bus.
  • the memory 1130 may be used to store program codes and data executed by the computer system. Therefore, the memory 1130 may be a storage unit inside the processor 1110, or an external storage unit independent of the processor 1110, or may include a storage unit inside the processor 1110 and an external storage unit independent of the processor 1110. part.
  • the processor 1110 may be composed of one or more general-purpose processors, for example, a CPU, a general-purpose processor, DSP, ASIC, FPGA, or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. It can implement or execute various exemplary logical blocks, modules, and circuits described in conjunction with the disclosure of this application.
  • the processor may also be a combination for realizing computing functions, for example, including a combination of multiple microprocessors, a combination of DSP and microprocessor, and so on.
  • the processor 1110 may be used to run programs for processing functions in related program codes. In other words, the processor 1110 executes the program code to realize the functions of determining the module and creating the module. For details about the functions of the determining module and the creating module, reference may be made to the relevant description in the foregoing embodiment.
  • the processor 1110 is configured to run related program codes to implement the method described in S302 shown in FIG. 5 of the present application, and/or implement other technologies described herein. Steps, etc., are not detailed and limited here in this application.
  • the communication interface 1120 may be a wired interface (such as an Ethernet interface) or a wireless interface (such as a cellular network interface or using a wireless local area network interface) for communicating with other modules/devices.
  • a wired interface such as an Ethernet interface
  • a wireless interface such as a cellular network interface or using a wireless local area network interface
  • the memory 1130 may include a volatile memory (volatile memory), such as RAM; the memory may also include a non-volatile memory (non-volatile memory), such as ROM, flash memory (flash memory), HDD or SSD; the memory 1130 also A combination of the above-mentioned types of memories may be included.
  • the memory 1130 may be used to store a set of program codes, so that the processor 1110 can call the program codes stored in the memory 1130 to implement the functions of the communication module and/or processing module involved in the embodiment of the present invention.
  • the area management platform 1100 can be caused to execute the method in the foregoing method embodiment 300.
  • the present application also provides a computer program product, the computer program product includes: computer program code, when the computer program code is run on a computer, the computer executes the steps shown in FIGS. 2 to 5 The method of any one of the embodiments is shown.
  • the present application also provides a computer-readable medium that stores program code, and when the program code runs on a computer, the computer executes the steps shown in FIGS. 2 to 5 The method of any one of the embodiments is shown.
  • the present application also provides a system, which includes the aforementioned global management platform, the first client, and the regional management platform.
  • the computer program product includes one or more computer instructions.
  • the computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices.
  • the computer instructions may be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium.
  • the computer instructions may be transmitted from a website, computer, server, or data center.
  • the computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server or data center integrated with one or more available media.
  • the usable medium may be a magnetic medium (for example, a floppy disk, a hard disk, and a magnetic tape), an optical medium (for example, a high-density digital video disc (digital video disc, DVD)), or a semiconductor medium (for example, a solid state disk, SSD)) etc.
  • Each network element in the above device embodiments can completely correspond to each network element in the method embodiment, and the corresponding unit or unit executes the corresponding steps, for example, the transceiver unit (transceiver) executes the receiving or sending steps in the method embodiment In addition to sending and receiving, other steps can be executed by the processing unit (processor).
  • the processing unit processor
  • the functions of specific units refer to the corresponding method embodiments. Among them, there may be one or more processors.
  • one embodiment or “an embodiment” mentioned throughout the specification means that a specific feature, structure, or characteristic related to the embodiment is included in at least one embodiment of the present application. Therefore, the appearances of "in one embodiment” or “in an embodiment” in various places throughout the specification do not necessarily refer to the same embodiment. In addition, these specific features, structures or characteristics can be combined in one or more embodiments in any suitable manner. It should be understood that in the various embodiments of the present application, the size of the sequence numbers of the above-mentioned processes does not mean the order of execution. The execution order of the processes should be determined by their functions and internal logic, and should not be used in the embodiments of the present invention. The implementation process constitutes any limitation.
  • unit used in this specification are used to denote computer-related entities, hardware, firmware, a combination of hardware and software, software, or software in execution.
  • the component may be, but is not limited to, a process, a processor, an object, an executable file, an execution thread, a program, and/or a computer running on a processor.
  • the application running on the computing device and the computing device can be components.
  • One or more components may reside in processes and/or threads of execution, and components may be located on one computer and/or distributed among two or more computers.
  • these components can be executed from various computer readable media having various data structures stored thereon.
  • the component can be based on, for example, a signal having one or more data packets (e.g. data from two components interacting with another component in a local system, a distributed system, and/or a network, such as the Internet that interacts with other systems through a signal) Communicate through local and/or remote processes.
  • a signal having one or more data packets (e.g. data from two components interacting with another component in a local system, a distributed system, and/or a network, such as the Internet that interacts with other systems through a signal) Communicate through local and/or remote processes.
  • the disclosed system, device, and method can be implemented in other ways.
  • the device embodiments described above are merely illustrative, for example, the division of the units is only a logical function division, and there may be other divisions in actual implementation, for example, multiple units or components may be combined or It can be integrated into another system, or some features can be ignored or not implemented.
  • the displayed or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices or units, and may be in electrical, mechanical or other forms.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the objectives of the solutions of the embodiments.
  • the functional units in the various embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units may be integrated into one unit.
  • the function is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer readable storage medium.
  • the technical solution of the present application essentially or the part that contributes to the existing technology or the part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including Several instructions are used to make a computer device (which may be a personal computer, a server, or a network device, etc.) execute all or part of the steps of the methods described in the various embodiments of the present application.
  • the aforementioned storage media include: U disk, mobile hard disk, read-only memory (read-only memory, ROM), random access memory (random access memory, RAM), magnetic disks or optical disks and other media that can store program codes. .

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Multimedia (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Computer And Data Communications (AREA)

Abstract

本申请提供了一种部署应用实例和调度应用实例的方法和装置。该方法包括：全局管理平台接收来自第一客户端的服务质量QoS需求信息，该QoS需求信息中包括第一时延需求、第二时延需求以及第一连接数量，该第二时延需求优于该第一时延需求，该QoS需求信息是第一用户输入至该第一客户端的；该全局管理平台从管理的站点中选择满足该第一时延需求的第一可用站点；该全局管理平台在该第一可用站点上部署一个或多个第一应用实例，该第一应用实例的可连接数量小于该第一连接数量。全局管理平台基于时延需求部署的应用实例可以为客户提供高质量的边缘云服务。

Description

部署应用实例和调度应用实例的方法和装置
本申请要求于2020年2月11日提交中国专利局、申请号为202010086421.6、申请名称为“部署应用实例和调度应用实例的方法和装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及边缘计算领域，尤其涉及一种部署应用实例和调度应用实例的方法和装置。
背景技术
目前在部署边缘应用实例的过程中，用户首先根据自身的覆盖需求指定资源、区域和位置。然后，全局管理平台在用户指定的位置过滤可用边缘站点并部署应用例。之后，用户可以查看应用实例所在的区域以及地理位置。然而，基于用户指定的区域和位置创建边缘应用实例只是当前全局管理平台能力下的折中选择，无法真正提供低时延与大流量的边缘云服务。
发明内容
本申请提供一种部署应用实例和调度应用实例的方法，可以为用户提供高服务质量的边缘云服务。
第一方面，提供了一种部署应用实例的方法，该方法包括：全局管理平台接收来自第一客户端的服务质量(quality of service，QoS)需求信息，该QoS需求信息中包括第一时延需求、第二时延需求以及第一连接数量，该第二时延需求优于该第一时延需求，该QoS需求信息是第一用户输入至该第一客户端的；该全局管理平台从管理的站点中选择满足该第一时延需求的第一可用站点；该全局管理平台在该第一可用站点上部署一个或多个第一应用实例，该第一应用实例的可连接数量小于或等于第一连接数量。
基于上述技术方案，全局管理平台基于第一用户输入至第一客户端的第一时延需求，选择在满足第一时延需求的站点上部署应用实例。因此，全局管理平台部署的应用实例可以为第一用户的客户提供高服务质量的边缘云服务。
结合第一方面，在第一方面的某些实现方式中，该全局管理平台从管理的站点中选择满足该第一时延需求的第一可用站点，包括：该全局管理平台根据第一全局QoS信息表，从管理的站点中选择满足该第一时延需求的第一可用站点，该第一全局QoS信息表包括该全局管理平台管理的站点的QoS信息。
结合第一方面，在第一方面的某些实现方式中，该方法还包括：该全局管理平台从一个或多个该第一应用实例中选择出不满足该第二时延需求的第二应用实例；该全局管理平台从管理的站点中选择满足该第二时延需求的第二可用站点；该全局管理平台在该第二可 用站点上部署该第二应用实例。
基于上述技术方案，全局管理平台基于第二时延需求，优化更新不满足第二时延需求的应用实例的部署位置，使得优化后的应用实例可以为第一用户的客户提供更高质量的边缘云服务。
结合第一方面，在第一方面的某些实现方式中，该方法还包括：该全局管理平台根据管理的第一站点上已部署的第三应用实例的可连接数量，设置资源预留阈值；在该第一站点的剩余连接数量小于该资源预留阈值的情况下，该全局管理平台在该第一站点上部署第四应用实例，该第四应用实例的QoS信息与该第三应用实例的QoS信息相同或等同。
结合第一方面，在第一方面的某些实现方式中，该方法还包括：该全局管理平台根据历史访问数据，预测第一网段连接数量的增加量，该第一网段是该第三应用实例承载的网段；该全局管理平台根据该第一网段连接数量的增加量计算该第四应用实例的数量。
结合第一方面，在第一方面的某些实现方式中，该方法还包括：该全局管理平台接收来自第二客户端或区域管理平台的第一请求消息，该第一请求消息用于请求为该第二客户端调度应用实例，该第一请求消息包括该第二客户端的标识信息；该全局管理平台根据该第二请求消息和该第二全局QoS信息表，从一个或多个该第一应用实例中过滤出可用的应用实例，该第二全局QoS信息表包括该第一应用实例的QoS信息。
结合第一方面，在第一方面的某些实现方式中，该第一请求消息中还包括第二用户输入至该第二客户端的第三时延需求。
结合第一方面，在第一方面的某些实现方式中，该方法还包括：该全局管理平台根据第二用户的QoS等级为该第二用户调度应用实例。
第二方面，提供了一种部署应用实例的方法，该方法包括：第一客户端通过第一接口接收第一用户输入的QoS需求信息，该QoS需求信息中包括第一时延需求、第二时延需求以及第一连接数量，该第二时延需求优于该第一时延需求；该第一客户端向全局管理平台发送该QoS需求信息。
基于上述技术方案，全局管理平台基于第一用户输入至第一客户端的第一时延需求，选择在满足第一时延需求的站点上部署应用实例。因此，全局管理平台部署的应用实例可以为第一用户的客户提供高服务质量的边缘云服务。
结合第二方面，在第二方面的某些实现方式中，该第一接口包括应用编程界面接口。
第三方面，提供了一种调度应用实例的方法，该方法包括：区域管理平台接收来自第二客户端的第二请求消息，该第二请求消息用于请求为该第二客户端调度应用实例，该第二请求消息包括该第二客户端的标识信息；该区域管理平台根据该第二请求消息和业务QoS信息表，从一个或多个第五应用实例中过滤出可用的应用实例，该第五应用实例是全局管理平台根据来自第一客户端的QoS需求信息，部署在该区域管理平台管理的站点上的应用实例，该业务QoS信息表包括该第五应用实例的QoS信息。
基于上述技术方案，区域管理平台基于来自第二客户端的请求消息和业务QoS信息表为第二客户端调度的应用实例，可以为用户提供高质量的边缘云服务。
结合第三方面，在第三方面的某些实现方式中，该第二请求消息还包括第二用户输入至该第二客户端的第三时延需求。
结合第三方面，在第三方面的某些实现方式中，该方法还包括：该区域管理平台根据 第二用户的QoS等级为该第二用户调度应用实例。
结合第三方面，在第三方面的某些实现方式中，该方法还包括：该区域管理平台根据该第二请求消息向全局管理平台发送第一请求消息，该第一请求消息用于请求为该第二客户端调度应用实例。
基于上述技术方案，在区域管理平台无法为第二客户端调度可用应用实例的情况下，区域管理平台可用向全局管理平台请求为第二客户端调度应用实例。
第四方面，提供了一种全局管理平台，包括收发单元和处理单元：该收发单元用于接收来自第一客户端的QoS需求信息，该QoS需求信息中包括第一时延需求、第二时延需求以及第一连接数量，该第二时延需求优于该第一时延需求，该QoS需求信息是第一用户输入至该第一客户端的；该处理单元用于从管理的站点中选择满足该第一时延需求的第一可用站点；该处理单元还用于在该第一可用站点上部署一个或多个第一应用实例，该第一应用实例的可连接数量小于或等于第一连接数量。
结合第四方面，在第四方面的某些实现方式中，该处理单元具体用于根据第一全局QoS信息表，从管理的站点中选择满足该第一时延需求的第一可用站点，该第一全局QoS信息表包括该全局管理平台管理的站点的QoS信息。
结合第四方面，在第四方面的某些实现方式中，该处理单元还用于从一个或多个该第一应用实例中选择出不满足该第二时延需求的第二应用实例；该处理单元还用于从管理的站点中选择满足该第二时延需求的第二可用站点；该处理单元还用于在该第二可用站点上部署该第二应用实例。
结合第四方面，在第四方面的某些实现方式中，该处理单元还用于根据管理的第一站点上已部署的第三应用实例的可连接数量，设置资源预留阈值；在该第一站点的剩余连接数量小于该资源预留阈值的情况下，该处理单元还用于在该第一站点上部署第四应用实例，该第四应用实例的QoS信息与该第三应用实例的QoS信息相同或等同。
结合第四方面，在第四方面的某些实现方式中，该处理单元还用于根据历史访问数据，预测第一网段连接数量的增加量，该第一网段是该第三应用实例承载的网段；该处理单元还用于根据该第一网段连接数量的增加量计算该第四应用实例的数量。
结合第四方面，在第四方面的某些实现方式中，该收发单元还用于接收来自第二客户端或区域管理平台的第一请求消息，该第一请求消息用于请求为该第二客户端调度应用实例，该第一请求消息包括该第二客户端的标识信息；该处理单元还用于根据该第二请求消息和该第二全局QoS信息表，从一个或多个该第一应用实例中过滤出可用的应用实例，该第二全局QoS信息表包括该第一应用实例的QoS信息。
结合第四方面，在第四方面的某些实现方式中，该第一请求消息中还包括第二用户输入至该第二客户端的第三时延需求。
结合第四方面，在第四方面的某些实现方式中，该处理单元还用于根据第二用户的QoS等级为该第二用户调度应用实例。
第五方面，提供了一种客户端，包括接收单元和发送单元：该接收单元用于通过第一接口接收第一用户输入的QoS需求信息，该QoS需求信息中包括第一时延需求、第二时延需求以及第一连接数量，该第二时延需求优于该第一时延需求；该收发单元用于向全局管理平台发送该QoS需求信息。
结合第五方面，在第五方面的某些实现方式中，该第一接口包括应用编程界面接口。
第六方面，提供了一种区域管理平台，包括收发单元和处理单元：该收发单元用于接收来自第二客户端的第二请求消息，该第二请求消息用于请求为该第二客户端调度应用实例，该第二请求消息包括该第二客户端的标识信息；该处理单元用于根据该第二请求消息和业务QoS信息表，从一个或多个第五应用实例中过滤出可用的应用实例，该第五应用实例是全局管理平台根据来自第一客户端的QoS需求信息，部署在该区域管理平台管理的站点上的应用实例，该业务QoS信息表包括该第五应用实例的QoS信息。
结合第六方面，在第六方面的某些实现方式中，该第二请求消息还包括第二用户输入至该第二客户端的第三时延需求。
结合第六方面，在第六方面的某些实现方式中，该处理单元还用于根据第二用户的QoS等级为该第二用户调度应用实例。
结合第六方面，在第六方面的某些实现方式中，该收发单元还用于根据该第二请求消息向全局管理平台发送第一请求消息，该第一请求消息用于请求为该第二客户端调度应用实例。
第七方面，提供了一种全局管理平台，包括处理器。该处理器与存储器耦合，可用于执行存储器中的指令，以实现上述第一方面或第一方面中任一种可能实现方式中的方法。
第八方面，提供了一种客户端，包括处理器。该处理器与存储器耦合，可用于执行存储器中的指令，以实现上述第二方面或第二方面中任一种可能实现方式中的方法。
第九方面，提供了一种区域管理平台，包括处理器。该处理器与存储器耦合，可用于执行存储器中的指令，以实现上述第三方面或第三方面中任一种可能实现方式中的方法。
第十方面，提供了一种处理器，包括：输入电路、输出电路和处理电路。所述处理电路用于通过所述输入电路接收信号，并通过所述输出电路发射信号，使得所述处理器执行上述第一至第三方面或第一至第三方面中任一种可能实现方式中的方法。
在具体实现过程中，上述处理器可以为芯片，输入电路可以为输入管脚，输出电路可以为输出管脚，处理电路可以为晶体管、门电路、触发器和各种逻辑电路等。输入电路所接收的输入的信号可以是由例如但不限于接收器接收并输入的，输出电路所输出的信号可以是例如但不限于输出给发射器并由发射器发射的，且输入电路和输出电路可以是同一电路，该电路在不同的时刻分别用作输入电路和输出电路。本申请实施例对处理器及各种电路的具体实现方式不做限定。
第十一方面，提供了一种处理装置，包括处理器和存储器。该处理器用于读取存储器中存储的指令，并可通过接收器接收信号，通过发射器发射信号，以执行上述第一至第三方面或第一至第三方面中任一种可能实现方式中的方法。
可选地，所述处理器为一个或多个，所述存储器为一个或多个。
可选地，所述存储器可以与所述处理器集成在一起，或者所述存储器与处理器分离设置。
在具体实现过程中，存储器可以为非瞬时性(non-transitory)存储器，例如只读存储器(read only memory，ROM)，其可以与处理器集成在同一块芯片上，也可以分别设置在不同的芯片上，本申请实施例对存储器的类型以及存储器与处理器的设置方式不做限定。
应理解，相关的数据交互过程例如发送指示信息可以为从处理器输出指示信息的过程，接收能力信息可以为处理器接收输入能力信息的过程。具体地，处理输出的数据可以输出给发射器，处理器接收的输入数据可以来自接收器。其中，发射器和接收器可以统称为收发器。
上述第十一方面中的处理装置可以是一个芯片，该处理器可以通过硬件来实现也可以通过软件来实现，当通过硬件实现时，该处理器可以是逻辑电路、集成电路等；当通过软件来实现时，该处理器可以是一个通用处理器，通过读取存储器中存储的软件代码来实现，该存储器可以集成在处理器中，可以位于该处理器之外，独立存在。
第十二方面，提供了一种计算机程序产品，所述计算机程序产品包括：计算机程序(也可以称为代码，或指令)，当所述计算机程序被运行时，使得计算机执行上述第一至第三方面或第一至第三方面中任一种可能实现方式中的方法。
第十三方面，提供了一种计算机可读介质，所述计算机可读介质存储有计算机程序(也可以称为代码，或指令)当其在计算机上运行时，使得计算机执行上述第一至第三方面或第一至第三方面中任一种可能实现方式中的方法。
第十四方面，提供了一种边缘云调度系统，包括前述全局管理平台，第一客户端和区域管理平台。
附图说明
图1是本申请实施例提供的应用场景的示意图。
图2至图4是本申请实施例提供的部署应用实例的方法的示意性流程图。
图5是本申请实施例提供的调度应用实例的方法的示意性流程图。
图6至图7是本申请实施例提供的全局管理平台的示意性框图。
图8至图9是本申请实施例提供的第一客户端的示意性框图。
图10至图11是本申请实施例提供的区域管理平台的示意性框图。
具体实施方式
边缘云计算，简称边缘云，是基于云计算技术的核心和边缘计算的能力，构筑在边缘基础设施之上的云计算平台。形成边缘位置的计算、网络、存储、安全等能力全面的弹性云平台，并与中心云和物联网终端形成“云边端三体协同”的端到端的技术架构，通过将网络转发、存储、计算，智能化数据分析等工作放在边缘处理，降低响应时延、减轻云端压力、降低带宽成本，并提供全网调度、算力分发等云服务。
边缘云是公有云的一种，基于广泛覆盖的小站点，一般是内容分发网络(content delivery network，CDN)、因特网接入点(point of presence，POP)、移动边缘计算(mobile edge computing，MEC)，每个节点小集群形态对外提供公有云服务。具备低时延，一般区域内时延5ms，大带宽(40Gb-600Gb+)的特性，个数会达到一千以上，甚至个数上万。一般业内也叫雾计算、边缘计算、边缘云、微云计算(cloudlet)等。
地区(region)、可用区(available zone，AZ)是云计算涉及的概念。地区指数据中心所在地区、可以是地区(华南)、也可以是城市(深圳、东莞)；可用区指机房、站点所在的物理区域，具有能耗、网络所独立的特点。一个地区通常包含多个低时延互联的可 用区，用于同区域容灾备份和负载均衡等场景与服务。绝大多数云计算服务不支持跨地区。
边缘云用户追求的是极致体验，也就是说，边缘云用户最终需要其实是时延、流量的保障。目前在创建边缘应用实例的过程中，用户首先根据自身的覆盖需求指定资源、区域和位置，然后，全局管理平台在用户指定的位置过滤可用站点并部署应用实例。之后，用户可以查看应用实例所在的区域以及地理位置。然而，基于用户指定的区域和位置创建边缘应用实例只是当前全局管理平台能力下的折中选择，无法真正提供低时延与大流量的边缘云服务。应用实例，可以是虚拟机、容器，或软件模块。
因此，本申请实施例提供一种部署应用实例和调度应用实例的方法，为用户提供低时延与大流量的边缘云服务。
需要说明的是，本申请实施例提及的第一用户是使用客户端#1的用户，第二用户是使用客户端#2的用户。第一应用实例是初始部署的应用实例，第二应用实例是第一应用实例中不满足第二时延需求的应用实例，第三应用实例是最终部署好的应用实例，第四应用实例是在第三应用实例不够用的情况下，新增的应用实例。
图1示出了适用于本申请实施例提供的方法的应用场景的一个示意图。如图1所示，本申请的应用场景可以是在边缘计算领域中。
全局管理平台管理多个边缘云内的所有站点。例如图1中，全局管理平台管理边缘云#1内的站点和边缘云#2内的站点。
边缘云可以由边缘集群构成，其可以包括多个处理设备，边缘云中的每个处理设备都可以与不在边缘云中的其他客户端连接，可以通过其他客户端采集信息，传输至边缘云中区域管理平台中，再向全局管理平台进行传输或在区域管理平台处进行处理。例如图1中，边缘云#1由站点#1、站点#2以及区域管理平台#1组成，区域管理平台#1可以管理站点#1和站点#2。边缘云#2由站点#3、站点#4以及区域管理平台#2组成，区域管理平台#2可以管理站点#3和站点#4。
站点的物理形态可以是单个处理设备，全局管理平台可以在站点上部署应用实例。
应用实例是指同一个应用服务部署在不同的站点上的具体的应用，即一个应用服务可以对应多个应用实例。如图1所示，对应于同一个应用服务的多个应用实例(应用实例#1至应用实例#5)可以部署在相同或不同的站点上。例如，应用实例#1和应用实例#2部署在站点#1上，应用实例#3部署在站点#2上，应用实例#4和应用实例#5部署在站点#3上。
应理解，与处理设备连接的客户端可以是接入终端、用户单元、用户站、移动站、移动台、远方站、远程终端、移动设备、用户终端、终端、无线通信设备、用户代理或用户装置。站点的物理形态还可以是蜂窝电话、无绳电话、会话启动协议(session initiation protocol，SIP)电话、无线本地环路(wireless local loop，WLL)站、个人数字助手(personal digital assistant，PDA)、具有无线通信功能的手持设备、计算设备或连接到无线调制解调器的其它处理设备、车载设备、可穿戴设备等，本申请实施例对此并不限定。
图2是本申请实施例提供的部署应用实例的方法，该方法200示出了全局管理平台和客户端交互的流程。该全局管理平台和客户端例如分别可以是图1中的全局管理平台和客户端。如图2所示，该方法200包括S201至S203，下面详细描述每个步骤。
S201，客户端#1(所述第一客户端的一例)向全局管理平台发送QoS需求信息。相应地，全局管理平台接收来自客户端#1的QoS需求信息。
该QoS需求信息中包括第一时延需求、第二时延需求以及第一连接数量，该第二时延需求优于第一时延需求。该QoS需求信息是第一用户输入至客户端#1的。例如，该第一时延需求可以是用户可以接受的最大时延；第二时延需求可以是用户期望的时延；该第一连接数量可以是应用实例的最大可连接数量。
第一用户可以通过应用程序接口(application program interface，API)输入QoS需求信息。
以边缘云服务为例，现有的边缘云服务API接口并没有关于业务QoS需求信息的相关设置，因此，本申请实施例在现有的边缘云服务API接口的基础上，加入了与业务QoS需求信息相关的细节描述，形成了一种基于业务QoS需求信息的边缘云服务API接口。本申请实施例提供的边缘云服务API接口的一个示例如下：
Figure PCTCN2021076193-appb-000001
如上文所述，本申请实施例提供的边缘云服务API接口中，去掉了区域描述中的参数“demand”的赋值方式，即去掉了实例数量的描述。根据本申请实施例的方法，实例数量可以根据接入能力中的参数来确定。例如，可以根据公式(1)进行计算：
InstanceNum＝(minlinksNum/maxlinksPerInstance)*120％公式(1)
本申请实施例在现有方案的资源描述中添加了参数“QoS”，增加了关于QoS需求信息的描述。其中，参数“Delay”为一个自定义数据结构，表示对时延QoS的描述。参数“Access capability”也为一个自定义数据结构，表示对接入数QoS的描述。“Delay”结构体中包含两个参数：参数“max”表示为最大时延；参数“expection”表示为期望时延。“Access capability”结构体中包含三个参数：参数“maxlinksPerInstance”表示为每个应用实例的最大连接数量；参数“maxlinksNum”表示为每个站点的最大连接数量；参数“minlinksNum”表示为每个站点的最小连接数量。
应理解，上文示出的API接口中，仅以增加了关于时延和每个应用实例的最大连接数量为例进行说明，但这不应对本申请实施例造成限定。在本申请实施例提供的API接口中， 还可以增加关于传输带宽、数据的丢包率等参数的描述。
可以理解，通过上文所述的边缘服务API接口，第一用户可以向客户端#1输入第一时延需求、第二时延需求以及第一连接数量配置相关的参数。上文所述的参数的赋值仅为示例，不应对本申请实施例造成限定，应理解，第一用户可以根据自己的需求对上述参数进行赋值。
可选地，客户端#1还可以根据第一用户历史输入的时延需求信息预测出QoS需求信息，然后向全局管理平台发送该QoS需求信息。
S202，全局管理平台从管理的站点中选择满足第一时延需求的第一可用站点。
可选地，全局管理平台从管理的所有站点或部分站点中选择满足第一时延需求的第一可用站点。
全局管理平台可以根据本地储存的站点的QoS信息过滤出满足第一时延需求信息的第一可用站点。
可选地，全局管理平台可以建立一个第一全局QoS信息表，该第一全局QoS信息表中包括站点的QoS信息。然后，全局管理平台根据第一全局QoS信息表过滤出满足第一QoS需求信息的第一可用站点。
全局管理平台建立第一全局QoS信息表的方法可以是：
全局管理平台根据管理的站点及指定运营商网段建立第一全局QoS信息表。
其中，指定运营商例如可以是中国移动，或者是中国电信，或者是中国联通，或者是其他的运用商，本申请实施例对此不做限定。可以理解，不同的运营商对应的网段是不同的，以及不同的区域，对应的网段是不同的。因此，在指定运营商以及指定区域的情况下，相应的网段也是固定的。
表1给出了一个第一QoS信息表的示例。
表1
站点标识符 网段 时延 区域
站点#1 10.1.1.1-10.2.2.2 5ms 经度-纬度
站点#1 10.3.3.3-10.4.4.4 15ms 经度-纬度
站点#1 10.6.6.6-10.7.7.7 25ms 经度-纬度
站点#2 10.1.1.1-10.2.2.2 25ms 经度-纬度
站点#2 10.3.3.3-10.4.4.4 15ms 经度-纬度
站点#2 10.6.6.6-10.7.7.7 5ms 经度-纬度
站点#3 10.1.1.1-10.2.2.2 25ms 经度-纬度
站点#3 10.3.3.3-10.4.4.4 5ms 经度-纬度
站点#3 10.6.6.6-10.7.7.7 25ms 经度-纬度
站点#4 10.1.1.1-10.2.2.2 25ms 经度-纬度
站点#4 10.3.3.3-10.4.4.4 25ms 经度-纬度
站点#4 10.6.6.6-10.7.7.7 25ms 经度-纬度
如表1所示，以全局管理平台管理了站点#1至站点#4为例，以及，以指定运营商和区域之后，对应的网段为：10.1.1.1-10.2.2.2、10.3.3.3-10.4.4.4、10.6.6.6-10.7.7.7为例，对第一QoS信息表的内容进行说明。
其中，站点标识符用于标识站点，站点标识符可以是全局管理平台为每个站点分配的不同的编号。
站点、网段以及时延之间的对应关系为：某一个互联网协议(internet protocol，IP)地址属于该网段的客户端访问该站点的通信时延。如表1所示，IP地址属于10.1.1.1-10.2.2.2的客户端访问站点#1的通信时延是5ms；IP地址属于10.3.3.3-10.4.4.4的客户端访问站点#1的通信时延是15ms；IP地址属于10.6.6.6-10.7.7.7的客户端访问站点#1的通信时延是25ms。类似的，表1中还示出了IP地址属于不同网段的客户端分别访问站点#2至站点#4的通信时延。
站点与区域之间的对应关系为：该站点设置在该区域中。如表1所示，边缘#1至站点#4设置在同一区域中。
以第一时延需求信息是最大通信时延为20ms为例，全局管理平台根据表1可知，所有客户端访问边缘点#4的通信时延都是25ms，因此，站点#4不可用。因此，全局管理平台可以将站点#1至站点#3确定为第一可用站点。
S203，全局管理平台在第一可用站点上部署一个或多个第一应用实例。
该一个或多个第一应用实例的可连接数量小于或等于第一连接数量。
以根据公式(1)计算出的实例数量等于5为例。全局管理平台可以将应用实例#1至应用实例#5随机部署在站点#1至站点#3。
例如，如图1所示，全局管理平台随机选择第一用户指定区域中的站点#1至站点#4，并随机将应用实例#1和应用实例#2部署在站点#1上，将应用实例#3部署在站点#2上，将应用实例#4和应用实例#5分别部署在站点#3上。
然后，全局管理平台分配每个应用实例负责的网段，并且计算客户端访问每个应用实例的通信时延。
例如，应用实例#1负责10.1.1.1-10.2.2.2，应用实例#2负责10.3.3.3-10.4.4.4，应用实例#3负责10.6.6.6-10.7.7.7，应用实例#4负责10.1.1.1-10.2.2.2，应用实例#5负责10.3.3.3-10.4.4.4。
客户端访问应用实例的通信时延，也可以理解为客户端访问应用实例所在的站点的通信时延。根据表1可知，IP地址属于10.1.1.1-10.2.2.2的客户端访问站点#1的通信时延是5ms，因此可知，IP地址属于10.1.1.1-10.2.2.2的客户端访问应用实例#1的通信时延也是5ms。类似的，根据表1可知，IP地址属于10.3.3.3-10.4.4.4的客户端访问应用实例#2的通信时延是15ms；IP地址属于10.6.6.6-10.7.7.7的客户端访问应用实例#3的通信时延是5ms；IP地址属于10.1.1.1-10.2.2.2的客户端访问应用实例#4的通信时延是25ms；IP地址属于10.3.3.3-10.4.4.4的客户端访问应用实例#5的通信时延是5ms。
应理解，若指定区域内，指定运营商的网段只有一个，则全局管理平台不执行分配每个应用实例负责的网段的步骤。在此情况下，每个应用实例都负责此区域内唯一的一个网段。
在一些实现方式中，全局管理平台还可以根据第二时延需求对第一应用实例的部署位置进行调整。在此情况下，如图3所示，该方法200还可以包括S204至S206。
S204，全局管理平台从部署的一个或多个第一应用实例中选择出不满足第二时延需求的第二应用实例。
以第二时延需求信息是期望时延为5ms为例，以及以部署的第一应用实例是上文所述的应用实例#1至应用实例#5为例，如上文所述，IP地址属于10.1.1.1-10.2.2.2的客户端访问应用实例#1的通信时延是5ms，IP地址属于10.3.3.3-10.4.4.4的客户端访问应用实例#2的通信时延是15ms；IP地址属于10.6.6.6-10.7.7.7的客户端访问应用实例#3的通信时延是5ms；IP地址属于10.1.1.1-10.2.2.2的客户端访问应用实例#4的通信时延是25ms；IP地址属于10.3.3.3-10.4.4.4的客户端访问应用实例#5的通信时延是5ms。
因此，可以将应用实例#2和应用实例#4确定为不满足第二时延需求的第二应用实例。
S205，全局管理平台从管理的站点中选择满足第二时延需求的第二可用站点。
可选地，全局管理平台从管理的所有或部分站点中选择满足第二时延需求的第二可用站点。
全局管理平台可以根据本地储存的站点的QoS信息过滤出满足第二时延需求信息的第二可用站点。
可选地，全局管理平台可以根据第一全局QoS信息表过滤出满足第二时延需求的第二可用站点。
以应用实例#2和应用实例#4是第二应用实例为例，根据表1可知，IP地址属于10.3.3.3-10.4.4.4的客户端访问站点#3的通信时延是5ms，满足第二时延需求。IP地址属于10.1.1.1-10.2.2.2的客户端访问站点#1的通信时延是5ms，满足第二时延需求。因此，全局管理平台可以将站点#1和站点#3确定为第二可用站点。
S206，全局管理平台在第二可用站点上部署第二应用实例。
全局管理平台选择出不满足第二时延需求的第二应用实例之后，可以根据第一QoS信息表查询该第二应用实例负责的网段的最优部署位置，并移动该第二应用实例。然后计算第二应用实例移动之后，客户端访问所有应用实例的总的通信时延，若优于原有的总的通信时延，则更改第二应用实例的部署位置。
以应用实例#2和应用实例#4是第二应用实例为例，根据表1可知，IP地址属于10.3.3.3-10.4.4.4的客户端访问站点#3的通信时延是5ms。因此，全局管理平台可以将应用实例#2从站点#1移动到站点#3上。移动应用实例#2之后，客户端访问应用实例#1至应用实例#5的总的通信时延为45ms，小于原有的55ms。因此，更改应用实例#2的部署位置为站点#3。
根据表1可知，IP地址属于10.1.1.1-10.2.2.2的客户端访问站点#1的通信时延最小，因此，将应用实例#4从站点#3移动到站点#1上。移动应用实例#4之后，客户端访问所有应用实例的总的通信时延为25ms，小于原有的45ms。因此，更改应用实例#4的部署位置为站点#1。
可以理解，在S205和S206中，全局管理平台移动第一应用实例部署位置的调度目标为，第一应用实例覆盖范围内指定运营商提供的所有网段。
需要说明的是，上述部署位置更新过程的终止条件为：(1)所有应用实例覆盖网段满足用户的期望时延；或(2)调度时间大于1分钟。只要达到其中任意一个终止条件，上述更新过程就终止。
例如，在更新应用实例#2和应用实例#4的部署位置的过程中，若更新完应用实例#2的部署位置之后，调度时间达到了一分钟，则即使更新应用实例#4的步骤还没有完成， 更新的过程也会终止。又例如，在一分钟之间，应用实例#2和应用实例#4的更新过程都完成了，此时，所有的应用实例的覆盖网段都满足用户期望时延，则更新过程终止。
可以理解，在一段时间之后，可能会出现某些应用实例的连接数量达到了最大值。若有新的客户端请求应用实例，则无法为其调度可用的应用实例。在此情况下，如图4所示，该方法200还可以包括S207和S208。
S207，全局管理平台根据第一站点上已部署的第三应用实例的可连接数量，设置资源预留值。
其中，可连接数量可以是已部署的第三应用实例的最大连接数量。该资源预留阈值例如可以是，第三应用实例的最大连接数量的20％。并且在第三应用实例的剩余连接数量小于该资源预留阈值的情况下，提前增加新的应用实例的部署，以满足更多客户端的接入。
可选地，针对不同QoS等级的站点，全局管理平台可以设置不同的资源预留阈值。
作为一个示例，针对不同QoS等级的站点，全局管理平台可以设置固定的资源预留阈值。例如，对于QoS等级为99的站点，全局管理平台可以将该站点的最大连接数量的10％设置为资源预留阈值；对于QoS等级为9999的站点，全局管理平台可以将该站点的最大连接数量的40％设置为资源预留阈值；对于优先级最高的站点，全局管理平台还可以将该站点的最大连接数量的100％设置为资源预留阈值。
作为另一个示例，针对每一个QoS等级的站点，全局管理平台可以根据一段时间内的(例如，一年内)历史访问数据，动态调整资源预留阈值。若在一段时间内，访问某一个QoS等级的站点的客户端#2数量较多，则增大资源预留阈值；若在一段时间内，访问某一个QoS等级的站点的客户端#2数量较少，则减小资源预留阈值。例如，在上一年内，访问QoS等级为9999的站点的客户端#2的数量很少，因此，全局管理平台可以将预留的资源从40％减少到20％。
S208，全局管理平台在第一站点上部署第四应用实例。
该第四应用实例的QoS信息与第三应用实例的QoS信息相同或等同。例如，第三应用实例部署在第一站点上，且第三应用实例负责的网段是10.1.1.1-10.2.2.2，最大连接数量是2000，则第四应用实例也部署在第一站点上，且第四应用实例也负责10.1.1.1-10.2.2.2，最大连接数量是2000。
根据部署第三应用实例的相关信息可以确定部署第四应用参数的相关信息。除此之外，全局管理平台还可以确定第四应用实例的数量。
全局管理平台确定第四应用实例的数量的方法可以包括如下步骤：
第一步：全局管理平台根据历史访问数据，预测第一网段连接数量的增加量。该第一网段是第三应用实例承载的网段。
例如，在某一时间段内，全局管理平台统计访问同一服务域名的每个客户端的IP地址所在的网段；然后全局管理平台统计IP地址属于第一网段的客户端的数量；然后全局管理平台根据该客户端的数量预测该第一网段连接数量增加量。例如，该第一网段连接数量增加量可以是与第一网段对应的客户端的数量的100倍。
第二步：全局管理平台根据预测的第一网段连接数量增加量，计算需要增加的第四应用实例的数量。
需要增加的第四应用实例的数量等于第一网段连接数量增加量除以第四应用实例最 大连接数量。第四应用实例最大连接数量等于第三应用实例最大连接数量。
第三步：全局管理平台在第一站点上部署第四应用实例。
在本申请实施例中，全局管理平台可以根据用户可以接受的时延需求信息部署应用实例，因此可以使得全局管理平台为用户提供用户需求的服务。进一步地，全局管理平台还可以根据根据用户期望的时延需求信息优化更新应用实例的部署位置，从而使得全局管理平台可以为用户提供更优的服务。例如，可以为用户提供时延与大流量的服务。
在全局管理平台部署完应用实例之后，全局管理平台可以记录应用实例标识符、应用实例负责的网段以及应用实例的QoS信息，建立第二QoS信息表。
表2给出了一个第二QoS信息表的示例。
表2
服务域名 应用实例标识符 站点标识符 承载网段 时延 连接数量
1111 应用实例#1 站点#1 10.1.1.1-10.2.2.2 5ms 2000
1111 应用实例#2 站点#3 10.3.3.3-10.4.4.4 5ms 1500
1111 应用实例#3 站点#2 10.6.6.6-10.7.7.7 5ms 1000
1111 应用实例#4 站点#1 10.1.1.1-10.2.2.2 5ms 1000
1111 应用实例#5 站点#3 10.3.3.3-10.4.4.4 5ms 800
其中，应用实例标识符用于标识应用实例，该应用实例标识符可以是全局管理平台为每个应用实例分配的编号，连接数量为应用实例目前已连接的用户的数量。
以上，结合图2至图4对本申请实施例提供的部署应用实例的方法进行了说明。下面将结合图5对本申请实施例提供的调度应用实例的方法进行说明。
图5示出了本申请实施例提供的调度应用实例的方法的示意性流程图。如图5所示，该方法300包括S301至S304，下面详细描述每个步骤。
S301，区域管理平台接收来自客户端#2(所述第二客户端的一例)的请求消息#1(所述第二请求消息的一例)，该请求消息#1用于请求区域管理平台为该客户端#2分配应用实例。
该请求消息#1中携带该客户端#2的地址及IP信息。
可选地，该请求消息#1中还可以携带第二用户输入客户端#2的第三时延需求。该第三时延需求可以第二用户的期望时延。
可以理解，该请求消息#1可以是使用该客户端#2的第二用户通过该客户端#2向区域管理平台发送的。例如，在第二用户通过该客户端#2访问某一个服务域名时，该客户端#2向距离该客户端#2最近的区域管理平台发送该请求消息#1。
如图1所示，第二用户通过客户端#2访问的服务域名是1111，距离该客户端#2最近的边缘云是边缘云#1，因此，该客户端#2向边缘云#1内的区域管理平台#1发送请求消息#1，用于请求区域管理平台#1为其分配应用实例。该请求消息#1中携带的地址信息是该客户端#2所在的地址，该请求消息#1中携带的该客户端#2的IP信息是该客户端的IP地址。如图1所示，该客户端#2的IP地址是10.1.1.3。
S302，区域管理平台根据业务QoS信息表从一个或多个第五应用实例中过滤可用应用实例，并重新定向到最优应用实例的IP地址。
其中，业务QoS信息表是区域管理平台针对其归属的边缘云包含的站点以及该站点 上部署的应用实例建立的。第五应用实例是全局管理平台根据来自客户端#1的QoS需求信息部署在区域管理平台管理的站点上的应用实例。
如图1所示，区域管理平台#1管理站点#1和站点#2，区域管理平台#2管理站点#3和站点#4。因此，区域管理平台#1建立的业务QoS信息表如表3所示。
表3
服务域名 应用实例标识符 站点标识符 承载网段 时延 连接数量
1111 应用实例#1 站点#1 10.1.1.1-10.2.2.2 5ms 2000
1111 应用实例#3 站点#2 10.6.6.6-10.7.7.7 5ms 1000
1111 应用实例#4 站点#1 10.1.1.1-10.2.2.2 5ms 1000
区域管理平台#2建立的业务QoS信息表如表4所示。
表4
服务域名 应用实例标识符 站点标识符 承载网段 时延 连接数量
1111 应用实例#2 站点#3 10.3.3.3-10.4.4.4 5ms 1500
1111 应用实例#5 站点#3 10.3.3.3-10.4.4.4 5ms 800
区域管理平台接收到来自客户端#2的请求消息#1之后，可以先根据该请求消息#1中的地址信息为该客户端#2就近分配一个应用实例。然后，区域管理平台根据该请求消息#1中携带的IP地址确定该IP地址所在的网段；然后，区域管理平台根据业务QoS信息表找到负责该网段的应用实例；最后，根据该应用实例对应的QoS信息判断该应用实例是否可用。
例如，判断该应用实例所在的站点的连接数量是否达到了最大值，若达到了最大值，则该应用实例不可用，若没有达到最大值，则该应用实例可用。
再例如，若客户端向区域管理平台发送的请求消息#1中还携带第三时延需求，则区域管理平台还可以判断该应用实例对应的通信时延是否满足第三时延需求，若满足第三时延需求，则该应用实例可用，若不满足第三时延需求，则该应用实例不可用。
如图1所示，客户端#2的IP地址是10.1.1.3，区域管理平台#1收到来自客户端#2的请求消息#1之后，就近为该客户端#2分配应用实例#1。然后根据该请求消息#1中携带的IP地址确定该IP地址所在的网段为10.1.1.1。然后，区域管理平台#1根据表3找到负责10.1.1.1的应用实例为应用实例#1和应用实例#4。
以第一用户创建边缘应用实例的过程中，对参数“maxlinksPerInstance”的赋值为2000为例，区域管理平台根据表3可知，应用实例#1目前的连接数量已达到了最大连接数量，因此，应用实例#1不可用；而应用实例#4目前的连接数量是1000，没有达到最大连接数量，因此，应用实例#4可用。
根据表3可知，应用实例#4对应的通信时延是5ms，若客户端向区域管理平台#1发送的请求消息#1中携带第三时延需求，且第三时延需求小于5ms，则应用实例#4也不可用；若第三时延需求大于或等于5ms，则应用实例#4可用。
若区域管理平台根据来自客户端的请求消息#1和业务QoS信息表，判断所有的应用实例都不可用，则该方法300还可以执行S304-S305。
S303，区域管理平台向全局管理平台发送请求消息#2(所述第一请求消息的一例)，该请求消息#2用于请求为客户端#2分配应用实例。
该请求消息#2与请求消息#1的内容相对应。例如，请求消息#1中携带客户端#2的地址和IP信息，则请求消息#2中也携带客户端#2的地址和IP信息；再例如，请求消息#1中携带客户端#2的地址、IP信息以及第三时延需求，则请求消息#2中也携带客户端#2的地址、IP信息以及第三时延需求。
S304，全局管理平台根据第二QoS信息表从一个或多个第一应用实例中过滤可用应用实例，并定向到最优应用实例的IP地址。
全局管理平台接收到来自区域管理平台的请求消息#2之后，首先根据该请求消息#2中携带的地址信息为该客户端#2就近分配一个应用实例；然后，根据IP地址确定该IP地址所在的网段；然后，全局管理平台根据业务QoS信息找到负责该网段的应用实例；最后，根据该应用实例对应的QoS信息判断该应用实例是否可用。
例如，判断该应用实例所在的站点的连接数量是否达到了最大值，若达到了最大值，则该应用实例不可用，若没有达到最大值，则该应用实例可用。
再例如，若客户端#2向全局管理平台发送的请求消息#2中还包括第三时延需求，则全局管理平台还可以判断该应用实例对应的通信时延是否满足第三时延需求，若满足第三时延需求，则该应用实例可用，若不满足第三时延需求，则该应用实例不可用。
如图1所示，客户端#2的IP地址是10.3.3.5，全局管理平台收到来自区域管理平台#1的请求消息#2之后，就近为该客户端#2分配应用实例#1，然后根据该请求消息#2中携带的IP地址确定该IP地址所在的网段为10.3.3.3。
然后，全局管理平台根据表2找到负责10.3.3.3的应用实例为应用实例#2和应用实例#5。以用户创建边缘应用实例的过程中，对参数“maxlinksPerInstance”的赋值为2000为例，全局管理平台根据表2可知，应用实例#2目前的连接数量和应用实例#5目前的连接数量都没有达到最大连接数量，因此，应用实例#2和应用实例#5可用。
根据表2可知，应用实例#2和应用实例#5对应的通信时延都是5ms，若区域管理平台#1向全局管理平台发送的请求消息#2中携带第三时延需求，且第三时延需求小于5ms，则应用实例#2和应用实例#5也不可用；若第三时延需求大于或等于5ms，则应用实例#2和应用实例#5可用。
若全局管理平台根据请求消息#2和第二QoS信息表判断有可用的应用实例，则全局管理平台向客户端发送一个响应消息，该响应消息中携带可用应用实例的标识符。除此之外，该响应消息还用于使该客户端备重新定向到管理该可用应用实例所在的站点的边缘云。
若全局管理平台根据请求消息#2和第二QoS信息表判断无可用的应用实例，则全局管理平台启动资源调度，新增应用实例以满足用户的业务请求。
可选地，区域管理平台或全局管理平台可以根据客户端#2的QoS等级为客户端#2调度应用实例。
例如，区域管理平台或全局管理平台优先为QoS等级高的客户端#2调度应用实例。
本申请实施例对如何确定客户端#2的QoS等级不做限定。
例如，QoS等级管理设备根据客户端#2被满足的请求总数量与客户端#2请求总数量的比值，设置客户端#2的QoS等级。该比值的统计可以以年为单位。若客户端#2被满足的请求总数量与客户端#2请求总数量的比值为99％，则QoS等级管理设备将该客户端#2 的QoS等级设置为99；若客户端#2被满足的请求总数量与客户端#2请求总数量的比值为99.99％，则QoS等级管理设备将该客户端#2的QoS等级设置为9999。
可以理解，在客户端#2初始接入区域管理平台或全局管理平台的情况下，可以认为区域管理平台或全局管理平台都可以满足该客户端#2的请求。
可选地，在极端情况下(例如，预留的资源已使用完，且还没有新增应用实例)，高QoS等级的客户端#2可以抢占低QoS等级的客户端#2的算例资源。例如，QoS等级为9999的客户端#2可以抢占QoS等级为99的客户端#2的算例资源。
上文结合图3示出了终客户端向区域管理平台请求分配应用实例的过程，应理解，客户端#1还可以直接向全局管理平台发送请求消息#1，以请求全局管理平台云为客户端分配应用实例。客户端#1直接请求全局管理平台为其分配应用实例的方法可以参考上文S303至S304的描述，为了简洁，本申请实施例不再赘述。
以上，结合图2至图5详细说明了本申请实施例提供的部署应用实例和调度应用实例的方法。以下，结合图6至图11详细说明本申请实施例提供的装置。
图6是本申请实施例提供的全局管理平台500的示意性框图。如图所示，该全局管理平台500可以包括：收发单元510和处理单元520。
具体地，该全局管理平台500可以包括用于执行图2至图4中的方法200以及图5中的方法300中的全局管理平台执行的方法的单元。并且，该全局管理平台500中的各单元和上述其他操作和/或功能分别为了实现图2至图4中的方法200、图5中的方法300的相应流程。应理解，各单元执行上述相应步骤的具体过程在上述方法实施例中已经详细说明，为了简洁，在此不再赘述。
应理解，该全局管理平台500中的收发单元可对应于图7中示出的全局管理平台600中的通信接口620，该全局管理平台500中的处理单元520可对应于图7中示出的全局管理平台600中的处理器610。
图7是本申请实施例提供的一种全局管理平台600的示意性框图。如图所示，该全局管理平台600可以包括：通信接口620、处理器610和存储器630。
可选地，全局管理平台600还可以包括总线640。其中，通信接口620、处理器610以及存储器630可以通过总线640相互连接；总线640可以是外设部件互连标准(peripheral component interconnect，PCI)总线或扩展工业标准结构(extended industry standard architecture，EISA)总线等。所述总线640可以分为地址总线、数据总线、控制总线等。为便于表示，图7中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。
该存储器630可以用于存储该计算机系统执行的程序代码和数据。因此，该存储器630可以是处理器610内部的存储单元，也可以是与处理器610独立的外部存储单元，还可以是包括处理器610内部的存储单元和与处理器610独立的外部存储单元的部件。
处理器610可以由一个或者多个通用处理器构成，例如可以是中央处理器(central processing unit，CPU)，通用处理器，数字信号处理器(digital signal processor，DSP)，专用集成电路(application-specific integrated circuit，ASIC)，现场可编程门阵列(field programmable gate array，FPGA)或者其他可编程逻辑器件、晶体管逻辑器件、硬件部件或者其任意组合。其可以实现或执行结合本申请公开内容所描述的各种示例性的逻辑方框，模块和电路。所述处理器也可以是实现计算功能的组合，例如包含多个微处理器组合， DSP和微处理器的组合等等。处理器610可用于运行相关的程序代码中处理功能的程序。也就是说，处理器610执行程序代码可以实现确定模块和创建模块的功能。其中，关于确定模块和创建模块的功能具体可参见前述实施例中的相关阐述。
在一种可能的实施方式中，所述处理器610用于运行相关的程序代码，以实现本申请上述图2至图4示出的S202至S208中所述的方法，或以实现本申请上述图5示出的S304中所述的方法，和/或实现本文所描述的技术的其它步骤等，本申请这里不做详述和限定。
通信接口620可以为有线接口(例如以太网接口)或无线接口(例如蜂窝网络接口或使用无线局域网接口)，用于与其他模块/设备进行通信。
存储器630可以包括易失性存储器(volatile memory)，例如随机存取存储器(random access memory，RAM)；存储器也可以包括非易失性存储器(non-volatile memory)，例如只读存储器(read-only memory，ROM)、快闪存储器(flash memory)、硬盘(hard disk drive，HDD)或固态硬盘(solid-state drive，SSD)；存储器630还可以包括上述种类的存储器的组合。存储器630可用于存储一组程序代码，以便于处理器610调用存储器630中存储的程序代码以实现本发明实施例中涉及的通信模块和/或处理模块的功能。
当存储器630中的程序代码被处理器610执行时，可以使得该全局管理平台600执行上述方法实施例200或300中的方法。
图8是本申请实施例提供的第一客户端700的示意性框图。如图所示，该第一客户端700可以包括：接收单元710和发送单元720。
具体地，该第一客户端700可以包括用于执行图2中的方法200中的第一客户端执行的方法的单元。并且，该第一客户端700中的各单元和上述其他操作和/或功能分别为了实现图2至图4中的方法200的相应流程。应理解，各单元执行上述相应步骤的具体过程在上述方法实施例中已经详细说明，为了简洁，在此不再赘述。
应理解，该第一客户端700中的接收单元和发送单元可对应于图9中示出的第一客户端800中的收发器820。
图9是本申请实施例提供的第一客户端800的示意性框图。如图所示，该第一客户端800包括：处理器810和收发器820。该处理器810与存储器耦合，用于执行存储器中存储的指令，以控制收发器820发送信号和/或接收信号。可选地，该第一客户端800还包括存储器830，用于存储指令。
应理解，上述处理器810和存储器830可以合成一个处理装置，处理器810用于执行存储器830中存储的程序代码来实现上述功能。具体实现时，该存储器830也可以集成在处理器810中，或者独立于处理器810。
还应理解，收发器820可以包括接收器(或者称，接收机)和发射器(或者称，发射机)。收发器还可以进一步包括天线，天线的数量可以为一个或多个。
具体地，该第一客户端800可以包括用于执行图2中的方法200中的第一客户端执行的方法的单元。并且，该第一客户端800中的各单元和上述其他操作和/或功能分别为了实现图2至图4中的方法200的相应流程。应理解，各单元执行上述相应步骤的具体过程在上述方法实施例中已经详细说明，为了简洁，在此不再赘述。
图10是本申请实施例提供的区域管理平台1000的示意性框图。如图所示，该区域管理平台1000可以包括：收发单元1010和处理单元1020。
具体地，该区域管理平台1000可以包括用于图5中的方法300中的区域管理平台执行的方法的单元。并且，该区域管理平台1000中的各单元和上述其他操作和/或功能分别为了实现图5中的方法300的相应流程。应理解，各单元执行上述相应步骤的具体过程在上述方法实施例中已经详细说明，为了简洁，在此不再赘述。
应理解，该区域管理平台1000中的收发单元可对应于图11中示出的区域管理平台1100中的通信接口1120，该区域管理平台1000中的处理单元1020可对应于图11中示出的区域管理平台1100中的处理器1110。
图11是本申请实施例提供的一种区域管理平台1100的示意性框图。如图所示，该区域管理平台1100可以包括：通信接口1120、处理器1110和存储器1130。
可选地，区域管理平台管1100还可以包括总线1140。其中，通信接口1120、处理器1110以及存储器1130可以通过总线1140相互连接；总线1140可以是PCI总线或EISA总线等。所述总线1140可以分为地址总线、数据总线、控制总线等。为便于表示，图11中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。
该存储器1130可以用于存储该计算机系统执行的程序代码和数据。因此，该存储器1130可以是处理器1110内部的存储单元，也可以是与处理器1110独立的外部存储单元，还可以是包括处理器1110内部的存储单元和与处理器1110独立的外部存储单元的部件。
处理器1110可以由一个或者多个通用处理器构成，例如可以是CPU，通用处理器，DSP，ASIC，FPGA或者其他可编程逻辑器件、晶体管逻辑器件、硬件部件或者其任意组合。其可以实现或执行结合本申请公开内容所描述的各种示例性的逻辑方框，模块和电路。所述处理器也可以是实现计算功能的组合，例如包含多个微处理器组合，DSP和微处理器的组合等等。处理器1110可用于运行相关的程序代码中处理功能的程序。也就是说，处理器1110执行程序代码可以实现确定模块和创建模块的功能。其中，关于确定模块和创建模块的功能具体可参见前述实施例中的相关阐述。
在一种可能的实施方式中，所述处理器1110用于运行相关的程序代码，以实现本申请上述图5示出的S302中所述的方法，和/或实现本文所描述的技术的其它步骤等，本申请这里不做详述和限定。
通信接口1120可以为有线接口(例如以太网接口)或无线接口(例如蜂窝网络接口或使用无线局域网接口)，用于与其他模块/设备进行通信。
存储器1130可以包括易失性存储器(volatile memory)，例如RAM；存储器也可以包括非易失性存储器(non-volatile memory)，例如ROM、快闪存储器(flash memory)、HDD或SSD；存储器1130还可以包括上述种类的存储器的组合。存储器1130可用于存储一组程序代码，以便于处理器1110调用存储器1130中存储的程序代码以实现本发明实施例中涉及的通信模块和/或处理模块的功能。
当存储器1130中的程序代码被处理器1110执行时，可以使得该区域管理平台1100执行上述方法实施例300中的方法。
根据本申请实施例提供的方法，本申请还提供一种计算机程序产品，该计算机程序产品包括：计算机程序代码，当该计算机程序代码在计算机上运行时，使得该计算机执行图2至图5所示实施例中任意一个实施例的方法。
根据本申请实施例提供的方法，本申请还提供一种计算机可读介质，该计算机可读介 质存储有程序代码，当该程序代码在计算机上运行时，使得该计算机执行图2至图5所示实施例中任意一个实施例的方法。
根据本申请实施例提供的方法，本申请还提供一种系统，其包括前述的全局管理平台、第一客户端以及区域管理平台。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行所述计算机指令时，全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(digital subscriber line，DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质(例如，软盘、硬盘、磁带)、光介质(例如，高密度数字视频光盘(digital video disc，DVD))、或者半导体介质(例如，固态硬盘(solid state disk，SSD))等。
上述各个装置实施例中各网元可以和方法实施例中的各网元完全对应，由相应的单元或单元执行相应的步骤，例如收发单元(收发器)执行方法实施例中接收或发送的步骤，除发送、接收外的其它步骤可以由处理单元(处理器)执行。具体单元的功能可以参考相应的方法实施例。其中，处理器可以为一个或多个。
应理解，说明书通篇中提到的“一个实施例”或“一实施例”意味着与实施例有关的特定特征、结构或特性包括在本申请的至少一个实施例中。因此，在整个说明书各处出现的“在一个实施例中”或“在一实施例中”未必一定指相同的实施例。此外，这些特定的特征、结构或特性可以任意适合的方式结合在一个或多个实施例中。应理解，在本申请的各种实施例中，上述各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定，而不应对本发明实施例的实施过程构成任何限定。
在本说明书中使用的术语“单元”、“系统”等用于表示计算机相关的实体、硬件、固件、硬件和软件的组合、软件、或执行中的软件。例如，部件可以是但不限于，在处理器上运行的进程、处理器、对象、可执行文件、执行线程、程序和/或计算机。通过图示，在计算设备上运行的应用和计算设备都可以是部件。一个或多个部件可驻留在进程和/或执行线程中，部件可位于一个计算机上和/或分布在2个或更多个计算机之间。此外，这些部件可从在上面存储有各种数据结构的各种计算机可读介质执行。部件可例如根据具有一个或多个数据分组(例如来自与本地系统、分布式系统和/或网络间的另一部件交互的二个部件的数据，例如通过信号与其它系统交互的互联网)的信号通过本地和/或远程进程来通信。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可 以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(read-only memory，ROM)、随机存取存储器(random access memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以所述权利要求的保护范围为准。

Claims (22)

  1. 一种部署应用实例的方法，其特征在于，包括：
    全局管理平台接收来自第一客户端的服务质量QoS需求信息，所述QoS需求信息中包括第一时延需求、第二时延需求以及第一连接数量，所述第二时延需求优于所述第一时延需求，所述QoS需求信息是第一用户输入至所述第一客户端的；
    所述全局管理平台从管理的站点中选择满足所述第一时延需求的第一可用站点；
    所述全局管理平台在所述第一可用站点上部署一个或多个第一应用实例，所述第一应用实例的可连接数量小于或等于所述第一连接数量。
  2. 根据权利要求1所述的方法，其特征在于，所述全局管理平台从管理的站点中选择满足所述第一时延需求的第一可用站点，包括：
    所述全局管理平台根据第一全局QoS信息表，从管理的站点中选择满足所述第一时延需求的第一可用站点，所述第一全局QoS信息表包括所述全局管理平台管理的站点的QoS信息。
  3. 根据权利要求1或2所述的方法，其特征在于，所述方法还包括：
    所述全局管理平台从一个或多个所述第一应用实例中选择出不满足所述第二时延需求的第二应用实例；
    所述全局管理平台从管理的站点中选择满足所述第二时延需求的第二可用站点；
    所述全局管理平台在所述第二可用站点上部署所述第二应用实例。
  4. 根据权利要求1至3中任一项所述的方法，其特征在于，所述方法还包括：
    所述全局管理平台根据管理的第一站点上已部署的第三应用实例的可连接数量，设置资源预留阈值；
    在所述第一站点的剩余连接数量小于所述资源预留阈值的情况下，所述全局管理平台在所述第一站点上部署第四应用实例，所述第四应用实例的QoS信息与所述第三应用实例的QoS信息相同或等同。
  5. 根据权利要求1至4中任一项所述的方法，其特征在于，所述方法还包括：
    所述全局管理平台接收来自第二客户端或区域管理平台的第一请求消息，所述第一请求消息用于请求为所述第二客户端调度应用实例，所述第一请求消息包括所述第二客户端的标识信息；
    所述全局管理平台根据所述第一请求消息和第二全局QoS信息表，从一个或多个所述第一应用实例中过滤出可用的应用实例，所述第二全局QoS信息表包括所述第一应用实例的QoS信息。
  6. 根据权利要求5所述的方法，其特征在于，所述第一请求消息中还包括第二用户输入至所述第二客户端的第三时延需求。
  7. 一种部署应用实例的方法，其特征在于，包括：
    第一客户端通过第一接口接收第一用户输入的服务质量QoS需求信息，所述QoS需求信息中包括第一时延需求、第二时延需求以及第一连接数量，所述第二时延需求优于所述第一时延需求；
    所述第一客户端向全局管理平台发送所述QoS需求信息。
  8. 根据权利要求7所述的方法，其特征在于，所述第一接口包括应用编程界面接口。
  9. 一种调度应用实例的方法，其特征在于，包括：
    区域管理平台接收来自第二客户端的第二请求消息，所述第二请求消息用于请求为所述第二客户端调度应用实例，所述第二请求消息中包括所述第二客户端的标识信息；
    所述区域管理平台根据所述第二请求消息和业务服务质量QoS信息表，从一个或多个第五应用实例中过滤出可用的应用实例，所述第五应用实例是全局管理平台根据来自第一客户端的QoS需求信息，部署在所述区域管理平台管理的站点上的应用实例，所述业务QoS信息表包括所述第五应用实例的QoS信息。
  10. 根据权利要求9所述的方法，其特征在于，所述第二请求消息中还包括第二用户输入至所述第二客户端的第三时延需求。
  11. 根据权利要求9或10所述的方法，其特征在于，所述方法还包括：
    所述区域管理平台根据所述第二请求消息向所述全局管理平台发送第一请求消息，所述第一请求消息用于请求为所述第二客户端调度应用实例。
  12. 一种全局管理平台，其特征在于，包括收发单元和处理单元：
    所述收发单元用于接收来自第一客户端的服务质量QoS需求信息，所述QoS需求信息中包括第一时延需求、第二时延需求以及第一连接数量，所述第二时延需求优于所述第一时延需求，所述QoS需求信息是第一用户输入至所述第一客户端的；
    所述处理单元用于从管理的站点中选择满足所述第一时延需求的第一可用站点；
    所述处理单元还用于在所述第一可用站点上部署一个或多个第一应用实例，所述第一应用实例的可连接数量小于或等于第一连接数量。
  13. 根据权利要求12所述的全局管理平台，其特征在于，所述处理单元具体用于根据第一全局QoS信息表，从管理的站点中选择满足所述第一时延需求的第一可用站点，所述第一全局QoS信息表包括所述全局管理平台管理的站点的QoS信息。
  14. 根据权利要求12或13所述的全局管理平台，其特征在于，所述处理单元还用于从一个或多个所述第一应用实例中选择出不满足所述第二时延需求的第二应用实例；
    所述处理单元还用于从管理的站点中选择满足所述第二时延需求的第二可用站点；
    所述处理单元还用于在所述第二可用站点上部署所述第二应用实例。
  15. 根据权利要求12至14中任一项所述的全局管理平台，其特征在于，所述处理单元还用于根据管理的第一站点上已部署的第三应用实例的可连接数量，设置资源预留阈值；
    在所述第一站点的剩余连接数量小于所述资源预留阈值的情况下，所述处理单元还用于在所述第一站点上部署第四应用实例，所述第四应用实例的QoS信息与所述第三应用实例的QoS信息相同或等同。
  16. 根据权利要求12至15中任一项所述的全局管理平台，其特征在于，所述收发单元还用于接收来自第二客户端或区域管理平台的第一请求消息，所述第一请求消息用于请求为所述第二客户端调度应用实例，所述第一请求消息中包括所述第二客户端的标识信息；
    所述处理单元还用于根据所述第一请求消息和所述第二全局QoS信息表，从一个或 多个所述第一应用实例中过滤出可用的应用实例，所述第二全局QoS信息表中包括所述第一应用实例的QoS信息。
  17. 根据权利要求16所述的全局管理平台，其特征在于，所述第一请求消息中还包括第二用户输入至所述第二客户端的第三时延需求。
  18. 一种客户端，其特征在于，包括接收单元和发送单元：
    所述接收单元用于通过第一接口接收第一用户输入的服务质量QoS需求信息，所述QoS需求信息中包括第一时延需求、第二时延需求以及第一连接数量，所述第二时延需求优于所述第一时延需求；
    所述收发单元用于向全局管理平台发送所述QoS需求信息。
  19. 根据权利要求18所述的客户端，其特征在于，所述第一接口包括应用编程界面接口。
  20. 一种区域管理平台，其特征在于，包括收发单元和处理单元：
    所述收发单元用于接收来自第二客户端的第二请求消息，所述第二请求消息用于请求为所述第二客户端调度应用实例，所述第二请求消息中包括所述第二客户端的标识信息；
    所述处理单元用于根据所述第二请求消息和业务服务质量QoS信息表，从一个或多个第五应用实例中过滤出可用的应用实例，所述第五应用实例是全局管理平台根据来自第一客户端的QoS需求信息，部署在所述区域管理平台管理的站点上的应用实例，所述业务QoS信息表中包括所述第五应用实例的QoS信息。
  21. 根据权利要求20所述的区域管理平台，其特征在于，所述第二请求消息中还包括第二用户输入至所述第二客户端的第三时延需求。
  22. 根据权利要求20或21所述的区域管理平台，其特征在于，所述收发单元还用于根据所述第二请求消息向全局管理平台发送第一请求消息，所述第一请求消息用于请求为所述第二客户端调度应用实例。
PCT/CN2021/076193 2020-02-11 2021-02-09 部署应用实例和调度应用实例的方法和装置 WO2021160113A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP21753267.0A EP4096175A4 (en) 2020-02-11 2021-02-09 Application example deploying and application example scheduling method and apparatus
US17/886,017 US20220385586A1 (en) 2020-02-11 2022-08-11 Application instance deployment method, application instance scheduling method, and apparatus

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202010086421.6A CN113259260A (zh) 2020-02-11 2020-02-11 部署应用实例和调度应用实例的方法和装置
CN202010086421.6 2020-02-11

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US17/886,017 Continuation US20220385586A1 (en) 2020-02-11 2022-08-11 Application instance deployment method, application instance scheduling method, and apparatus

Publications (1)

Publication Number Publication Date
WO2021160113A1 true WO2021160113A1 (zh) 2021-08-19

Family

ID=77220362

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/076193 WO2021160113A1 (zh) 2020-02-11 2021-02-09 部署应用实例和调度应用实例的方法和装置

Country Status (4)

Country Link
US (1) US20220385586A1 (zh)
EP (1) EP4096175A4 (zh)
CN (1) CN113259260A (zh)
WO (1) WO2021160113A1 (zh)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114070851A (zh) * 2021-11-15 2022-02-18 中国电信集团系统集成有限责任公司 一种基于mec边缘云的业务恢复方法、存储介质及系统
CN114422477B (zh) * 2021-12-30 2023-07-21 联想(北京)有限公司 基于边缘云架构的域名解析方法、装置及存储介质
CN114401183A (zh) * 2022-01-17 2022-04-26 杭州瑞网广通信息技术有限公司 一种基于分布式云平台的边缘云灾备系统、方法和装置

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101083517A (zh) * 2006-05-30 2007-12-05 华为技术有限公司 业务网络内提供端到端服务质量保证的装置和方法
CN101977242A (zh) * 2010-11-16 2011-02-16 西安电子科技大学 一种分层分布式云计算体系结构及服务提供方法
WO2018219229A1 (zh) * 2017-06-01 2018-12-06 华为技术有限公司 通信方法和网络设备
CN109831490A (zh) * 2019-01-14 2019-05-31 中国联合网络通信集团有限公司 业务访问方法及系统
CN110365787A (zh) * 2019-07-19 2019-10-22 南京工业大学 一种应用容器并基于微服务框架的边缘计算最优化布局方法

Family Cites Families (18)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6976087B1 (en) * 2000-11-24 2005-12-13 Redback Networks Inc. Service provisioning methods and apparatus
US7773624B2 (en) * 2002-12-12 2010-08-10 Alcatel Lucent Network system and method with centralized flow behavioral mapping between layers
US8429630B2 (en) * 2005-09-15 2013-04-23 Ca, Inc. Globally distributed utility computing cloud
US8589558B2 (en) * 2010-11-29 2013-11-19 Radware, Ltd. Method and system for efficient deployment of web applications in a multi-datacenter system
US9003141B2 (en) * 2011-11-14 2015-04-07 Ca, Inc. Enhanced software application platform
US9007899B2 (en) * 2012-06-07 2015-04-14 Verizon Patent And Licensing Inc. Quality of service treatement for applications with multiple traffic classes
US20150195858A1 (en) * 2012-06-22 2015-07-09 Interdigital Patent Holdings, Inc. Methods, apparatus and systems for implementing hierarchical policy servers and for control of coordinated femtocell-wifi operation in co-sited deployments
US9325585B1 (en) * 2012-07-10 2016-04-26 The Boeing Company Mission-driven autonomous and adaptive resource management
US10942776B2 (en) * 2016-09-21 2021-03-09 Accenture Global Solutions Limited Dynamic resource allocation for application containers
US11165868B2 (en) * 2017-03-30 2021-11-02 Microsoft Technology Licensing, Llc Systems and methods for achieving session stickiness for stateful cloud services with non-sticky load balancers
WO2018215046A1 (en) * 2017-05-22 2018-11-29 Telefonaktiebolaget Lm Ericsson (Publ) Edge cloud broker and method therein for allocating edge cloud resources
CN107370673B (zh) * 2017-06-20 2020-04-28 华为技术有限公司 一种网络中建立转发路径的方法、控制器及系统
CN113194157B (zh) * 2017-06-30 2022-10-28 华为技术有限公司 一种应用实例地址的转换方法和装置
CN110167068A (zh) * 2018-02-14 2019-08-23 华为技术有限公司 一种处理服务质量QoS参数的方法、网元、系统及存储介质
US10470059B1 (en) * 2019-03-04 2019-11-05 Cisco Technology, Inc. Dynamic network device selection for containerized application deployment
US10856158B2 (en) * 2019-03-12 2020-12-01 T-Mobile Usa, Inc. Network resource function supporting multi-region querying
US10715463B1 (en) * 2020-02-20 2020-07-14 Robert Gelfond System and method for controlling access to resources in a multicomputer network
US11409555B2 (en) * 2020-03-12 2022-08-09 At&T Intellectual Property I, L.P. Application deployment in multi-cloud environment

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101083517A (zh) * 2006-05-30 2007-12-05 华为技术有限公司 业务网络内提供端到端服务质量保证的装置和方法
CN101977242A (zh) * 2010-11-16 2011-02-16 西安电子科技大学 一种分层分布式云计算体系结构及服务提供方法
WO2018219229A1 (zh) * 2017-06-01 2018-12-06 华为技术有限公司 通信方法和网络设备
CN109831490A (zh) * 2019-01-14 2019-05-31 中国联合网络通信集团有限公司 业务访问方法及系统
CN110365787A (zh) * 2019-07-19 2019-10-22 南京工业大学 一种应用容器并基于微服务框架的边缘计算最优化布局方法

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP4096175A4

Also Published As

Publication number Publication date
CN113259260A (zh) 2021-08-13
EP4096175A1 (en) 2022-11-30
EP4096175A4 (en) 2023-06-28
US20220385586A1 (en) 2022-12-01

Similar Documents

Publication Publication Date Title
EP3732846B1 (en) Quality of service (qos) control in mobile edge computing (mec)
WO2021160113A1 (zh) 部署应用实例和调度应用实例的方法和装置
JP7183416B2 (ja) 時間依存ネットワーキング通信方法及び装置
US11368904B2 (en) Network slice selection method and apparatus
CN113596191B (zh) 一种数据处理方法、网元设备以及可读存储介质
WO2018161803A1 (zh) 一种网络切片的选择方法及装置
CN109392024B (zh) 一种业务质量流的控制方法及相关设备
US11558491B2 (en) Information-centric networking over 5G or later networks
WO2014094310A1 (zh) 资源调度的方法和装置
WO2021147402A1 (zh) 一种数据传输方法及装置
WO2020125573A1 (zh) 通信方法、装置、终端、网络设备及存储介质
WO2018082035A1 (zh) 一种功能调度方法、设备和系统
JP2015530821A (ja) ワイヤレスローカルエリアネットワークにおけるサービスの差別化に基づく動的なアソシエーションの順序付けのためのシステムおよび方法
JP7106639B2 (ja) アップリンクデータパケットリソース割り当て方法およびユーザ端末
WO2020185132A1 (en) Method and current edge cloud manager for controlling resources
CN106465387B (zh) 多跳能力的发现和每链路基础上的路由
EP3962157A1 (en) Mdbv determining method, apparatus, and system
WO2021227600A1 (zh) 一种网络切片控制方法及通信装置
WO2023035925A1 (zh) 一种业务处理方法、装置和系统
WO2018049626A1 (zh) 一种业务处理方法、相关设备及系统
CN112714071A (zh) 一种数据发送方法及装置
CN114514764A (zh) 设备、方法和计算机程序
WO2024032603A1 (zh) 一种通信方法及装置
WO2024114731A1 (zh) 一种业务链策略处理方法、装置和系统
WO2023088118A1 (zh) 数据传输方法及装置

Legal Events

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

Ref document number: 21753267

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2021753267

Country of ref document: EP

Effective date: 20220823

NENP Non-entry into the national phase

Ref country code: DE