Edge application method and apparatus
By reserving resources in the edge data network, the problems of edge application server deployment failure and user access delay are solved, and efficient resource utilization and low-latency access are achieved.
Patent Information
- Application Number
- PCT/CN2024/092368
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2023-05-11
- Filing Date
- 2024-05-10
- Publication Date
- 2024-11-14
AI Technical Summary
In edge computing, the deployment of edge application servers may fail due to insufficient remaining resources, resulting in high deployment failure rates and increased user access latency, especially when using the 'first come first served' mechanism, deploying to distance due to limited resources User location is farther in the edge data network.
By reserving resources in an edge data network, application service providers allow requests for reserved resources before deploying edge application servers, ensuring resource availability and performance parameters, including the number of reserved resources, performance parameters and expiration time, thereby reducing the number of reserved resources. The probability of deployment failure and reduces user access latency.
It effectively reduces the probability of deployment of edge application servers failing, improves resource utilization, and reduces user access latency, ensuring the stable and efficient operation of edge application servers.
Smart Images

Figure CN2024092368_14112024_PF_FP_ABST
Abstract
Description
Edge application method and device
[0001] CROSS-REFERENCE TO RELATED APPLICATIONS
[0002] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office of China on May 11, 2023, with application number 202310532533.3 and application name “A Method and Device for Edge Application”, the entire contents of which are incorporated by reference into this application. Technical Field
[0003] The embodiments of the present application relate to the field of communication technology, and in particular to an edge application method and device. Background Art
[0004] The fundamental concept of edge computing is to place computing tasks on computing resources close to the data source. This effectively reduces computing system latency, reduces data transmission bandwidth, alleviates pressure on cloud computing centers, improves availability, and protects data security and privacy. When deploying edge application servers (EAS) in an edge data network (EDN), a "first-come, first-served" mechanism is used. If the remaining resources in the EDN cannot meet the EAS deployment requirements, this can lead to problems such as EAS deployment failure.
[0005] Summary of the Invention
[0006] The embodiments of the present application provide an edge application method and apparatus, which reduces the probability of EAS deployment failure due to insufficient remaining resources in the EDN, etc., by reserving resources for deploying the EAS in advance in the EDN.
[0007] In a first aspect, an edge application method is provided. The method is applied to an edge computing service provider (ECSP) management system. The method may be executed by the ECSP management system, or by a chip or circuit applied to the ECSP management system. Taking the ECSP management system as an example, the method includes: the ECSP management system receiving reserved resource demand information from an application service provider (ASP), where the reserved resource demand information includes location information of the reserved resources; and the ECSP management system sending a first request to a management and orchestration system (MANO) based on the reserved resource demand information, where the first request is used to request the MANO to reserve resources in an EDN corresponding to the location information. The reserved resources are connected to a user plane function (UPF) corresponding to the location information, and the reserved resources are used to deploy an edge application server (EAS) of the ASP.
[0008] Through this design, the ASP can request to reserve some resources before deploying an EAS application. For example, the ASP sends its resource reservation request to the ECSP management system. Based on this request, the ECSP management system sends a first request to the MANO. Based on this first request, the MANO reserves resources in the EDN corresponding to the location information of the requested resources. After the resources are successfully reserved, the ASP can request the ECSP management system to deploy the EAS within the reserved resources. This way, as long as the resources are within the reserved quota, the ECSP management system can meet the ASP's EAS application deployment needs, thus resolving the high EAS deployment failure rate that can occur due to the "first-come, first-served" mechanism.
[0009] In one design, the reserved resource requirement information also includes at least one of the following: the quantity of reserved resources, performance parameters of reserved resources, or expiration time of reserved resources.
[0010] Through the above design, the demand information for reserved resources may include the quantity of reserved resources, the performance parameters of reserved resources, etc. For example, the performance parameters of reserved resources include at least one of the central processing unit (CPU) parameters of the reserved resources, the storage capacity of the reserved resources, or the network bandwidth of the reserved resources. Based on at least one of the quantity of reserved resources or the performance parameters of the reserved resources, a resource that meets the quantity and performance parameters can be selected in the EDN at the corresponding position as the reserved resource. Furthermore, the demand information for reserved resources also includes the expiration time of the reserved resource. The expiration time of the reserved resource can also be called the effective time of the reserved resource. When the expiration time is reached or exceeds the effective time, the reserved resource becomes invalid and is no longer reserved for the ASP to deploy EAS. This avoids the situation where the ASP does not use a certain reserved resource but occupies the reserved resource for a long time, thereby improving the utilization rate of the reserved resources.
[0011] In one design, it also includes: when the reserved resources are successfully reserved, determining the usage status information of the reserved resources, the usage status information of the reserved resources includes at least one of the following: an identifier of the reserved resources, a usage status of the reserved resources, an identifier of the EAS deployed in the reserved resources, or a utilization rate of the reserved resources.
[0012] Through the above design, based on the usage information of reserved resources, at least one of the following information can be determined: which reserved resources are occupied, which reserved resources are idle, the utilization rate of occupied reserved resources, or the deployment of EAS in occupied reserved resources. This can then facilitate EAS deployment, such as prioritizing the deployment of EAS in idle reserved resources or prioritizing the deployment of ESA in reserved resources with low occupancy rates. Alternatively, when deleting reserved resources, the usage information of the reserved resources can be used to determine which reserved resources can be deleted, thereby avoiding the deletion of reserved resources for deploying EAS. When deleting reserved resources, the reserved resources will not be affected by the services provided by the reserved resources to the already deployed EAS.
[0013] In one design, the identifier of the reserved resources includes: the identifier of the virtualized network function VNF and the identifier of the network service NS to which the VNF belongs; the usage of the reserved resources includes: whether the VNF is in an idle state or an occupied state.
[0014] In one design, after sending the first request to the MANO based on the resource reservation requirement information, the method further includes:
[0015] A second request is sent to the operator management system, where the second request is used to request the operator management system to establish a network connection between the UPF and the reserved resources, and the second request includes connection information of the reserved resources.
[0016] Through the above design, when reserving resources, the connection network between the reserved resources and UPF is opened in advance. In this way, when EAS is deployed on the reserved resources, the network between EAS and UPF is in a connected state, so that EAS can provide services to users at any time, and the latency from EAS deployment to EAS providing services to users is low.
[0017] In one design, after sending the second request to the operator management system, it also includes: receiving a second response from the operator management system, the second response including the connection information of the UPF; sending a third request to the MANO, the third request is used to request the MANO to update the connection information between the reserved resources and the UPF, and the third request includes the connection information of the UPF.
[0018] In one design, before sending a first request to MANO based on the demand information for reserved resources, it also includes: sending a fourth request to the operator management system, the fourth request is used to request the connection information of the UPF corresponding to the location information; receiving a fourth response from the operator management system, the fourth response including the connection information of the UPF corresponding to the location information.
[0019] In one design, the method further includes: receiving a fifth request from the ASP, where the fifth request is used to request deployment of the EAS in the reserved resources, and the fifth request includes an identifier of the reserved resources.
[0020] Through the above design, after successfully reserving resources, ASP can deploy EAS in the reserved resources, thereby solving the problem of high latency in user access to EAS caused by deploying EAS in an EDN far away from the user location due to the "first come, first served" mechanism and limited resources of the EAS at the corresponding location during EAS deployment.
[0021] In one design, the fifth request also includes: EAS migration policy information, and the migration policy information includes at least one of the following: a migration condition or a migration range.
[0022] With this design, when an ASP requests EAS deployment, the fifth request also includes the EAS migration policy. When EAS migration is needed, for example, if some EAS servers within the EDN may need to be shut down for maintenance or upgrades, the EAS needs to be migrated to other servers. Alternatively, due to insufficient EDN resources, the EAS may need to be migrated to other servers. Based on the EAS migration policy, the EAS can be migrated to ensure that the services provided by the EAS are not affected, or are minimally affected.
[0023] In one design, the migration conditions include: allowing migration, not allowing migration, or whether to query the ASP before migration; the migration scope includes: migrating the EAS within the same reserved resource, migrating the EAS within different reserved resources in the same EDN, or migrating the EAS between different EDNs.
[0024] In the second aspect, an edge application method is provided. The second aspect is the ASP side corresponding to the first aspect. The beneficial effects can be found in the description of the first aspect. The method is applied to an application service provider ASP. The execution subject of the method is the ASP, or a chip or circuit applied to the ASP, etc., including: determining the demand information of reserved resources, the demand information of reserved resources includes at least the location information of the reserved resources; sending the demand information of reserved resources to the edge computing service provider ECSP management system, there is a network connection between the reserved resources and the UPF corresponding to the location information, and the reserved resources are used to deploy the edge application server EAS of the ASP.
[0025] In one design, the reserved resource requirement information also includes at least one of the following: the quantity of reserved resources, performance parameters of reserved resources, or expiration time of reserved resources.
[0026] In one design, the method further includes sending a fifth request to the ECSP management system, where the fifth request is used to request deployment of the EAS in the reserved resources, and the fifth request includes an identifier of the reserved resources.
[0027] In one design, the fifth request also includes: EAS migration policy information, and the migration policy information includes at least one of the following: a migration condition or a migration range.
[0028] In one design, the migration conditions include: allowing migration, not allowing migration, or whether to query the ASP before migration; the migration scope includes: migrating the EAS within the same reserved resource, migrating the EAS within different reserved resources in the same EDN, or migrating the EAS between different EDNs.
[0029] A third aspect provides an edge application method. This third aspect is a system corresponding to the first aspect. The beneficial effects can be found in the description of the first aspect. The method includes: an edge computing service provider (ECSP) management system receiving reserved resource demand information from an application service provider (ASP) and, based on the reserved resource demand information, sending a first request to a management and orchestration system (MANO). The reserved resource demand information includes location information of the reserved resources. The first request is used to request the MANO to reserve resources in an edge data network (EDN) corresponding to the location information. The reserved resources have a network connection with a user plane function (UPF) corresponding to the location information. The reserved resources are used to deploy the ASP's edge application server (EAS). The MANO receives the first request from the ECSP management system.
[0030] In one design, the further configuration includes: the MANO reserving resources in the EDN corresponding to the location information based on the first request.
[0031] In one design, the ASP also sends resource reservation requirement information to the ECSP management system.
[0032] In one design, the reserved resource requirement information also includes at least one of the following: the quantity of reserved resources, performance parameters of reserved resources, or expiration time of reserved resources.
[0033] In one design, the ECSP management system further includes determining, when the reserved resource is successfully reserved, usage status information of the reserved resource, where the usage status information of the reserved resource includes at least one of the following: an identifier of the reserved resource, usage status of the reserved resource, an identifier of the EAS deployed in the reserved resource, or a usage rate of the reserved resource.
[0034] In one design, the identifier of the reserved resources includes: the identifier of the virtualized network function VNF and the identifier of the network service NS to which the VNF belongs; the usage of the reserved resources includes: whether the VNF is in an idle state or an occupied state.
[0035] In one design, after the ECSP management system sends a first request to the MANO based on the reserved resource demand information, the following further includes: the ECSP management system sends a second request to the operator management system, where the second request is used to request the operator management system to establish a network connection between the UPF and the reserved resources, and the second request includes connection information of the reserved resources; and the operator management system establishes the network connection between the UPF and the reserved resources based on the second request.
[0036] In one design, the further configuration includes: the operator management system sending a second response to the ECSP management system, where the second response includes the connection information of the UPF; the ECSP management system sending a third request to the MANO, where the third request is used to request the MANO to update the connection information between the reserved resources and the UPF; and the MANO updating the connection information between the reserved resources and the UPF based on the UPF connection information included in the third request.
[0037] In one design, before the ECSP management system sends the first request to the MANO based on the reserved resource requirement information, the ECSP management system further includes: sending a fourth request to the operator management system, where the fourth request is used to request connection information of the UPF corresponding to the location information; and the operator management system sending a fourth response to the ECSP management system, where the fourth response includes the connection information of the UPF corresponding to the location information.
[0038] In one design, the method further includes: the ECSP management system receiving a fifth request from the ASP, where the fifth request is used to request deployment of the EAS in the reserved resources, and the fifth request includes an identifier of the reserved resources.
[0039] In one design, the ASP further includes sending a fifth request to the ECSP management system.
[0040] In one design, the fifth request also includes: EAS migration policy information, and the migration policy information includes at least one of the following: a migration condition or a migration range.
[0041] In one design, the migration conditions include: allowing migration, not allowing migration, or whether to query the ASP before migration; the migration scope includes: migrating the EAS within the same reserved resource, migrating the EAS within different reserved resources in the same EDN, or migrating the EAS between different EDNs.
[0042] In a fourth aspect, a communication device is provided, which can implement the method of any one of the first to third aspects above. For example, the communication device includes means corresponding to performing any one of the first to third aspects above. The communication device can be implemented through hardware, software, or hardware executing corresponding software implementations.
[0043] In one design, the communication device includes a unit that performs any one of the first to third aspects above.
[0044] In one design, the communication device includes a processor and a memory, and the processor is used to execute a computer program or instructions stored in the memory, so that the communication device implements the method of any one of the first to third aspects above.
[0045] In one design, the communication device includes a processor and an interface circuit, the interface circuit is used to receive signals from other communication devices outside the communication device and transmit them to the processor or send signals from the processor to other communication devices outside the communication device, and the processor is used to implement the method of any one of the first to third aspects above through logic circuits or executing code instructions.
[0046] In a fifth aspect, a computer-readable storage medium is provided, which stores a computer program or instruction. When the computer program or instruction is executed on a computer, the computer implements the method of any one of the first to third aspects above.
[0047] In a sixth aspect, a computer program product is provided, comprising a computer program or instructions, which, when executed by a computer, enables the method of any one of the first to third aspects to be executed.
[0048] In the seventh aspect, a chip is provided, comprising a processor, wherein the processor is coupled to a memory and is configured to execute a computer program or instruction stored in the memory, so that the chip implements the method of any one of the first to third aspects above.
[0049] In an eighth aspect, a communication system is provided, comprising: a first communication device and a MANO, wherein the first communication device is configured to implement the method of the first aspect. Optionally, the system further comprises: an operator management system. Further, the system further comprises: a second communication device, wherein the second communication device is configured to implement the method of the second aspect. BRIEF DESCRIPTION OF THE DRAWINGS
[0050] FIG1 is a schematic diagram of a communication system provided in an embodiment of the present application;
[0051] FIG2 is a schematic diagram of deploying EAS in an EDN according to an embodiment of the present application;
[0052] FIG3 is a flowchart of reserving resources according to an embodiment of the present application;
[0053] FIG4 is another flowchart of reserving resources provided in an embodiment of the present application;
[0054] FIG5 is another flowchart of reserving resources provided in an embodiment of the present application;
[0055] FIG6 is a flow chart of deploying EAS in reserved resources according to an embodiment of the present application;
[0056] FIG7 is a flow chart of deploying and migrating EAS in reserved resources according to an embodiment of the present application;
[0057] FIG8 is a flowchart of deleting reserved resources according to an embodiment of the present application;
[0058] FIG9 is a schematic structural diagram of a device provided in an embodiment of the present application;
[0059] FIG10 is another schematic diagram of the structure of the device provided in an embodiment of the present application. DETAILED DESCRIPTION
[0060] FIG1 shows a communication system provided by an embodiment of the present application. As shown in FIG1 , it includes:
[0061] Edge data network (EDN) 101 is a small local data center at the edge. EDN 101 includes computing, storage, and network resources, which can be provided to application service providers (ASPs) for use in deploying edge application servers (EASs). In other words, ASPs can deploy EASs in EDNs. For ease of explanation, FIG1 uses two EDNs as an example, which is not intended to limit the embodiments of the present application. For example, the communication system shown in FIG1 may also include other numbers of EDNs.
[0062] The edge computing service provider (ECSP) management system 102 is responsible for managing the edge computing network. This includes, for example, creating and deleting EASs and monitoring their performance. For example, an ASP can request EAS deployment from the ECSP management system. The ECSP management system can then select an EDN that meets the requirements for deployment, such as resource size and location, and deploy the EAS.
[0063] In the embodiments of the present application, the device used to implement the functions of an ECSP management system can be an ECSP management system; it can also be a device capable of supporting the ECSP management system in implementing the functions, such as a chip system, hardware circuit, software module, or a combination of hardware circuit and software module. This device can be installed in the ECSP management system or used in conjunction with the ECSP management system. The chip system can be composed of a chip or include chips or other discrete components. For ease of description, the technical solutions provided in the embodiments of the present application are described below using the ECSP management system as an example of the device implementing the functions of the ECSP management system.
[0064] The management and orchestration system (MANO) 103 is responsible for managing virtualized network functions (VNFs). For example, EAS can be deployed within the EDN as a VNF based on cloud computing technology. Network function virtualization (NFV) uses general-purpose hardware devices and virtualization technology to carry the functions of dedicated equipment in traditional networks, thereby reducing the expensive cost of deploying dedicated equipment. By decoupling software and hardware, network functions are no longer dependent on dedicated hardware. At the same time, the characteristics of cloud computing are utilized to enable fully and flexibly share resources, enabling rapid development and deployment of new services, and performing automatic deployment, elastic scaling, fault isolation, and self-healing based on actual business needs.
[0065] In the embodiments of the present application, the device for implementing the functions of a MANO may be a MANO; it may also be a device capable of supporting a MANO in implementing such functions, such as a chip system, a hardware circuit, a software module, or a combination of a hardware circuit and a software module. This device may be installed in a MANO or used in conjunction with a MANO. A chip system may be composed of a chip or may include chips or other discrete components. For ease of description, the technical solutions provided in the embodiments of the present application are described below using a MANO as an example of a device implementing the functions of a MANO.
[0066] ASP 104 is an application service provider. The application service provider applies to deploy an EAS in the EDN through the ECSP management system and the MANO. For example, the application service provider may identify an EAS and send a request to deploy the EAS to the ECSP management system. The MANO then deploys the EAS in the corresponding EDN.
[0067] In the embodiments of the present application, the device used to implement the functions of an ASP can be an ASP; it can also be a device that supports the ASP in implementing the functions, such as a chip system, a hardware circuit, a software module, or a hardware circuit and a software module. This device can be installed in the ASP or used in conjunction with the ASP. The chip system can be composed of a chip or can include chips or other discrete devices. For ease of description, the following describes the technical solutions provided in the embodiments of the present application using an ASP as an example of a device that implements the functions of an ASP.
[0068] In the embodiment of the present application, after the EAS is deployed, when a user is near an EDN, such as EDN1, they can access EAS applications deployed in EDN1, such as a game server or a geo-location application server, through proximity access. For example, a user uses terminal 107 to connect to a user plane function (UPF) 105 that meets the requirements through access network device 106, and then accesses the EAS to be accessed through UPF 105.
[0069] Optionally, the network architecture shown in Figure 1 may also include: UPF 105, access network equipment 106, and terminal 107. UPF 105 is a network element in the core network responsible for data plane functions. For example, the UPF is primarily responsible for forwarding and receiving user data. For example, in downlink transmission, the UPF may receive user data from the data network (DN) and transmit it to the terminal via the access network equipment. In uplink transmission, the UPF network element may receive user data from the terminal via the access network equipment and forward the user data to the DN. It will be understood that in addition to UPF 105, the network architecture shown in Figure 1 may also include other core network devices, such as at least one of the access and mobility management function (AMF), session management function (SMF), policy control function (PCF), application function (AF), unified data management (UDM), authentication server function (AUSF), or network slice selection function (NSSF).
[0070] It is understood that, in the description of this application, "at least one" means one or more, and "a plurality" means two or more. "At least one of the following: A, B, or C" or "at least one of A, B, or C" can mean: including A; including B; including C; including A and B; including A and C; including B and C; including A, B, and C, etc.
[0071] The access network device 106 may be a base station, an evolved NodeB (eNodeB), a transmission reception point (TRP), a next generation NodeB (gNB) in a fifth generation (5G) mobile communication system, an access network device in an open radio access network (O-RAN), a next generation base station in a sixth generation (6G) mobile communication system, a base station in a future mobile communication system, or an access node in a wireless fidelity (WiFi) system; or it may be a module or unit that performs some functions of a base station, for example, a central unit (CU), a distributed unit (DU), a radio unit (RU), a central unit control plane (CU-CP) module, or a central unit user plane (CU-UP) module. The access network device may be a macro base station, a micro base station, an indoor station, a relay node, a donor node, or the like. This application does not limit the specific technology and specific device form used by the access network equipment.
[0072] The terminal 107 can be referred to as a terminal device, user equipment (UE), mobile station, mobile terminal, etc. The terminal can be widely used for communication in various scenarios, such as but not limited to one or more of the following scenarios: device-to-device (D2D), vehicle to everything (V2X), machine-type communication (MTC), Internet of Things (IOT), virtual reality, augmented reality, industrial control, autonomous driving, telemedicine, smart grid, smart furniture, smart office, smart wearable, smart transportation, or smart city, etc. The terminal can be a mobile phone, a tablet computer, a computer with wireless transceiver function, a wearable device, a vehicle, a drone, a helicopter, an airplane, a ship, a robot, a robotic arm, or a smart home device, etc. This application does not limit the specific technology and specific device form adopted by the terminal.
[0073] The access network equipment and terminals can be fixed or movable. The access network equipment and / or terminals can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; they can also be deployed on the water surface; they can also be deployed on airplanes, balloons and artificial satellites in the air. The embodiments of the present application do not limit the application scenarios of the access network equipment and terminals. The access network equipment and terminals can be deployed in the same scenario or different scenarios. For example, the access network equipment and terminals are deployed on land at the same time; or, the access network equipment is deployed on land and the terminal is deployed on the water surface, etc., and no further examples are given.
[0074] Furthermore, the communication system shown in FIG1 may further include an operator management system, which is not shown in FIG1 . For example, the operator management system includes one or more network elements, which interact with the ECSP management system in the embodiment of the present application to implement operations such as establishing or deleting a connection between reserved resources and the UPF. For example, the operator management system includes a management system (MS) in a public land mobile network (PLMN), which interacts with the ECSP management system to implement operations such as establishing or deleting a connection between reserved resources and the UPF.
[0075] In the embodiments of the present application, the device for implementing the functions of the operator management system may be one or more network elements in the operator management system; or it may be a device capable of supporting the operator management system to implement the functions, such as a chip system, a hardware circuit, a software module, or a hardware circuit plus a software module, etc. The device may be installed in one or more network elements in the operator management system or may be used in conjunction with the operator management system. The chip system may be composed of a chip, or may include a chip or other discrete devices. For ease of description, the following describes the technical solutions provided in the embodiments of the present application using the example of an operator management system as the device for implementing the functions of the operator management system.
[0076] The communication system shown in FIG1 above can support various radio access technologies (RAT). For example, the communication system shown in FIG1 can be a 5G communication system (also referred to as a new radio (NR) communication system), a WiFi system, or a future-oriented evolution system. The communication system and service scenarios described in the embodiments of the present application are intended to more clearly illustrate the technical solutions of the embodiments of the present application and do not constitute a limitation on the technical solutions provided in the embodiments of the present application. It is known to those skilled in the art that with the evolution of the communication system and the emergence of new service scenarios, the technical solutions provided in the embodiments of the present application are also applicable to similar technical problems.
[0077] An EDN is a small data center deployed by the ECSP management system at the edge, close to users. It typically has limited resources. The ECSP management system may need to serve multiple ASPs simultaneously, such as internet application vendors and gaming application vendors. According to the current EAS deployment process, the ECSP management system and the MANO select an EDN that meets the requirements for EAS deployment based on the ASP's needs. For example, the EDN corresponding to the ASP's deployment location is selected. Typically, an ECSP management system manages only one EDN in a given area. If that EDN has sufficient remaining resources and meets the EAS deployment requirements, EAS deployment can be completed. However, if the EDN is too busy and lacks sufficient remaining resources to meet the EAS deployment requirements, EAS deployment may fail. Alternatively, the ECSP management system and the MANO may select another, more distant EDN for EAS deployment.
[0078] For example, as shown in Figure 2, EAS1 is primarily targeted at users near EDN1. Because EDN1's remaining resources are insufficient to meet the requirements for deploying EAS1, the ECSP management system and MANO deploy EAS1 in EDN2. Each EDN serves a specific area. When users in its service area access applications within the EDN through terminals, access network equipment, and UPFs, the EDN provides optimal service, allowing users to enjoy the best possible experience, such as low latency and high bandwidth. If EDN1 lacks sufficient resources and the edge application EAS1 can only be deployed in EDN2, users in EDN1's service area cannot access EAS1 locally. For example, users can only access UPF2 in EDN2's service area through UPF1, and then access EAS1 in EDN2 through UPF2. This results in a poor service experience for users in EDN1's service area, such as high latency. In an EAS deployment, a "first-come, first-served" mechanism is used, giving the ASP that sends the request first a greater chance of being deployed in the desired area, even for more important ASPs.
[0079] In view of this, the present application provides an edge application method and device, which includes: the ASP can request to reserve a portion of resources before deploying the EAS application. After the resource reservation is successful, the ASP can request the ECSP management system to deploy the EAS within the reserved resources. In this way, as long as it is within the reserved resource quota, the ECSP management system can meet the ASP's needs for deploying the EAS application, thereby solving the problems of EAS deployment failure due to the "first come, first served" mechanism during EAS deployment, or high latency in user access to EAS due to deploying the EAS in an EDN that is far away from the user's location.
[0080] It will be appreciated that in the embodiments of this application, the ASP, ECSP management system, MANO, or operator management system cooperate with each other to implement the solutions described in the embodiments of this application. The functions implemented by the ASP can be implemented by the ASP, or by chips or circuits implemented within the ASP. The following description uses the ASP implementation as an example. Similarly, the functions of the ECSP management system, MANO, or operator management system can be implemented by the ECSP management system, MANO, or operator management system, or by chips implemented within each. The following description uses the ECSP management system, MANO, or operator management system as an example of implementing the corresponding functions.
[0081] [Example 1]
[0082] Figure 3 provides a process for reserving resources, including:
[0083] Step 301: The ECSP management system receives reserved resource demand information from the ASP.
[0084] The demand information for reserved resources includes the location information of the reserved resources. For example, the location information is the latitude and longitude information of the reserved resources, or the geographic location information of the reserved resources. Furthermore, the demand information for reserved resources also includes at least one of: the number of reserved resources, the performance parameters of the reserved resources, or the expiration time of the reserved resources. The performance parameters of the reserved resources include at least one of: the central processing unit (CPU) parameters of the reserved resources, the storage capacity of the reserved resources, or the network bandwidth of the reserved resources. The expiration time of the reserved resources may also be referred to as the effective time of the reserved resources. When the expiration time is reached or the effective time is exceeded, the reserved resources become invalid and are no longer reserved for the ASP to deploy EAS.
[0085] Taking a virtual machine (VM) as an example, the reserved resource requirement information includes at least one of the following:
[0086] The number of virtual machines: for example, 10.
[0087] Performance parameters of the virtual machine: CPU: for example, it can be 1800 megahertz (MHz); storage capacity: for example, it can be 2024 megabytes (M); network bandwidth: for example, it can be 100M.
[0088] Expiration time: For example, it could be 20230501. This means that the reserved resources are valid until May 1, 2023. That is, after May 1, 2023, the reserved resources become invalid and are no longer reserved for the ASP deploying EAS. The reserved resources can be used for other purposes, such as being allocated to other ASPs deploying EAS. The expiration time is also called reservation expiration.
[0089] Or location information: for example, it can be a certain district in Nanjing. This means that resources can be reserved in the EDN in a certain district in Nanjing. Location information can also be called location requirement.
[0090] Through the above design, the reserved resource demand information can include the number of reserved resources, the performance parameters of the reserved resources, etc. For example, the performance parameters of the reserved resources include at least one of the central processing unit (CPU) parameters of the reserved resources, the storage capacity of the reserved resources, or the network bandwidth of the reserved resources. Based on at least one of the number of reserved resources or the performance parameters of the reserved resources, a resource that meets the number and performance parameters can be selected from the EDN at the corresponding location as the reserved resource. Furthermore, the reserved resource demand information also includes the expiration time of the reserved resource. The expiration time of the reserved resource, also known as the effective time of the reserved resource, reaches or exceeds the effective time, and the reserved resource becomes invalid and is no longer reserved for the ASP to deploy the EAS. This prevents the ASP from not using a reserved resource but occupying it for a long time, thereby improving the utilization rate of the reserved resources.
[0091] In one design, the reserved resource requirement information can be carried in an object that includes the reserved resource requirement information. For example, this object can be called a reservation job object. For example, one implementation of step 301 includes: the ECSP management system receives a reservation job object from the ASP, where the reservation job object includes the reserved resource requirement information. Furthermore, one implementation of step 201 includes: the ECSP management system receives a request from the ASP to create a reservation object instance, where the request includes the reservation job object, and the reservation job object includes the reserved resource requirement information.
[0092] Step 302: The ECSP management system sends a first request to the MANO based on the reserved resource requirement information. The first request is used to request the MANO to reserve resources in the EDN corresponding to the location information. The reserved resources are connected to the UPF corresponding to the location information. The reserved resources are used to deploy the EAS of the ASP.
[0093] In one implementation, the MANO includes a network function virtualization orchestrator (NFV MANO, NFVO), which can communicate with a virtualized infrastructure manager (VIM) within the MANO to perform at least one of resource allocation and resource reservation. In step 302, the ECSP management system can specifically send a first request to the NFVO. Based on the first request, the NFVO can reserve resources in the EDN corresponding to the location information.
[0094] In the following description, the specific implementation of step 302 will be explained in the following two cases.
[0095] Case 1: The operator management system is responsible for reserving resources and network connections with the UPF.
[0096] After sending a first request to the MANO, the ECSP management system may receive a first response from the MANO. The first response includes connection information for the reserved resources. The ECSP management system may request the operator management system to establish a network connection between the reserved resources and the UPF. For example, the ECSP management system may send a second request to the operator management system, requesting the operator management system to establish a network connection between the UPF and the reserved resources. The second request includes connection information for the reserved resources. The operator management system establishes a network connection between the UPF and the reserved resources based on the second request.
[0097] Through the above design, when reserving resources, the connection network between the reserved resources and UPF is opened in advance. In this way, when EAS is deployed on the reserved resources, the network between EAS and UPF is in a connected state, so that EAS can provide services to users at any time, and the latency from EAS deployment to EAS providing services to users is low.
[0098] For the above situation 1, as shown in FIG4 , a process is provided, including:
[0099] Step 401: The ECSP management system receives a request from an ASP to create a reservation object instance, where the reservation object instance includes demand information for reserved resources.
[0100] Step 402: The ECSP management system sends a first request to the MANO based on the resource reservation requirement information. The first request is used to request the MANO to reserve resources in the EDN corresponding to the location information.
[0101] For example, MANO can reserve resources based on virtualized network functions (VNFs) based on cloud computing technology. The network service virtualized by network function virtualization (NFV) can be called a network service (NS). An NS can include at least one VNF. When a NS is virtualized and deployed, the service requester (e.g., the ECSP management system) needs to provide the service provider (e.g., MANO) with a description of the service, which can be called a network service descriptor (NSD) or an NS deployment template. This description information mainly describes the topology of the service and the description information of each VNF. The topology information describes the connection between VNFs. For example, a virtual link (VL) or a virtual private cloud (VPC) can be used to describe the connection between VNFs.
[0102] In one design, the ECSP management system determines an NSD based on the reserved resource requirement information. Each VM in the reserved resource requirement information is implemented by one or more VNFs. The following description uses the example of each VM in the reserved resource requirement information being implemented by a single VNF. The NSD may include a topology and description information for each VNF. For example, the topology includes the number of VNFs and the network connections of all VNFs. Continuing with the example of 10 VMs in the reserved resource requirement information, the NSD topology may include the 10 VNFs and their network connections. In one implementation, the 10 VNFs may be implemented in a single network, which may be referred to as a VL or VPC. This single network may be an internal virtual local area network (VLAN), in which the 10 VNFs can communicate with each other and may be isolated from other networks. The description information for each VNF includes performance parameters for each VNF, including at least one of the following: the VNF's CPU, storage, or network bandwidth requirements. The ECSP management system can send a request to instantiate NS to MANO. Furthermore, the request to instantiate NS also includes location information and NSD information. Alternatively, the request to instantiate NS includes NSD information (information for obtaining NSD files), and in addition to the topology structure and description information of each VNF mentioned above, NSD can also include location information. MANO selects the corresponding EDN based on the location information and instantiates NS in the corresponding EDN. For example, in the corresponding EDN, a VL or VPC is created, and the VL or VPC includes 10 VNFs, and the CPU, storage space, and network bandwidth of the 10 VNFs meet the requirements. MANO returns an NS instance creation response to the ECSP management system. That is, a specific implementation of the first request is: a request to instantiate NS. A specific implementation of the first response is: an NS instance creation response.
[0103] Step 403: MANO sends a first response to the ECSP management system. The first response is used to indicate that the resource reservation is successful. The first response may include connection information of the reserved resource.
[0104] The first response may be an NS instance creation response. When the NS instance is successfully created, the ECSP management system may query the MANO for information about the created NS instance. Based on the query request, the MANO returns the NS instance information to the ECSP management system, including connection information for reserved resources. The connection information for reserved resources may include access address information for the NS, such as the NS service access point (SAP), which may be information about the VPC's egress gateway.
[0105] Step 404: The ECSP management system sends a second request to the operator management system, where the second request is used to request to reserve resources for the network connection with the UPF.
[0106] For example, the second request is a request to create an edge computing management connection information (EcmconnectionInfo) object instance. The second request includes an EcmconnectionInfo object, which includes the access address information of the NS corresponding to the reserved resources. In addition, the second request also includes location information. In one implementation, the operator management system executes step 405, finds a UPF that meets the conditions, establishes a network connection between the UPF and the NS, creates an EcmconnectionInfo object instance, executes step 406, and sends a second response to the ECSP management system. The second response may be a response to the successful creation of the EcmconnectionInfo object instance.
[0107] Optionally, step 405: the operator management system selects a UPF that meets the conditions according to the location information, and establishes a network connection between the UPF and the NS.
[0108] For example, each UPF has a certain service area, and the UPF whose service area includes the location corresponding to the above-mentioned location information can be used as a UPF that meets the conditions. Alternatively, the UPF that is closest to the location corresponding to the location information can be used as a UPF that meets the conditions, etc. In one design, the operator management system can send the received access address information of the NS to the SMF that manages the UPF, and the SMF can send the access address information of the NS to the UPF, and the UPF establishes a network connection with the NS. Optionally, the access address information of the NS can be stored on the UPF side. For example, the access address information of the NS is configured in the routing of the UPF. After the UPF completes the network connection with the NS, the operator management system can return the connection information of the UPF, which can be the IP address of the UPF, etc., to the ECSP management system through a second response.
[0109] Step 406: The operator management system sends a second response to the ECSP management system. The second response includes the connection information of the UPF.
[0110] Step 407: The ECSP management system sends a third request to the MANO. The third request is used to request the MANO to update the connection information between the reserved resources and the UPF. The third request includes the connection information of the UPF.
[0111] Because, in previous operations, the MANO only deployed the NS in the EDN and did not configure specific routes in the external connection information (e.g., SAP), or it can be understood that the routes in the NS external connection information were empty, when the ECSP management system obtains the UPF connection information, it can send a third request to the MANO, which includes the UPF connection information. The third request can be an update request, in which the MANO updates the routes in the NS external connection information from empty to the UPF connection information, or the third request can be a configuration request, in which the MANO configures the UPF connection information in the routes in the NS external connection information, etc.
[0112] Optionally, after step 407, the process may further include: the MANO sending a third response to the ECSP management system, where the third response is a response indicating that the connection information between the reserved resources and the UPF is successfully updated.
[0113] Step 408: The ECSP management system creates a reserved work object instance and sends a response to the ASP indicating that the reserved work object instance has been successfully created.
[0114] For example, the reserved work object instance created by the ECSP management system includes at least one of: the identifier of the reserved work object, the address of the reserved resource corresponding to the reserved work object, or the usage status information of the reserved resource. Optionally, when the resource reservation is successful, the ECSP management system determines the usage status information of the reserved resource. For example, in case 1, after the ECSP management system sends a third request requesting an NS update and receives a third response indicating a successful NS update, it deems that the resource reservation is successful. The usage status of the reserved resource includes at least one of the following: the identifier of the reserved resource, the usage status of the reserved resource, the identifier of the EAS deployed in the reserved resource, or the utilization rate of the reserved resource. Optionally, the identifier of the reserved resource includes: the identifier of the VNF and the identifier of the NS to which the VNF belongs. The usage status of the reserved resource includes: whether the VNF is in an idle state or an occupied state, etc. As shown in Table 1, the usage status of the reserved resource is specifically:
[0115] Table 1
[0116] In Table 1, the reserved resources are implemented in NS-1. NS-1 can be the identifier of the NS corresponding to the reserved resources, or the instance identifier of the NS corresponding to the resources. The NS identifier and the instance identifier of the NS can be the same or different, without limitation. In Table 1, NS-1 includes 10 VNFs, whose identifiers are VNF1 to VNF10. Each VNF identifier can be the VNF identifier or the instance identifier of the VNF. The VNF identifier and the instance identifier of the VNF can be the same or different. It should be understood that Table 1 describes the usage status of the reserved resources determined by the ECSP management system when the resource reservation is successful. At this point, each reserved resource is not occupied. Therefore, the usage status of each reserved resource is idle, the utilization rate of each reserved resource is 0, and the EAS deployment flag in each reserved resource is empty. It should be understood that the idle usage status of a reserved resource means that the VNF corresponding to the reserved resource has been successfully created, but no EAS application software is deployed or running in the VNF. When EAS application software is deployed or running on a VNF, the VNF is considered occupied, and the corresponding usage status of the VNF is occupied. Optionally, as shown in Table 1, the working status of the reserved resources may also include: the usage status of the VPC corresponding to the NS, the identifier of the EAS deployed in the VPC, and the utilization rate of the VPC. In the example in Table 1, the VPC corresponding to VPC-1 includes 10 VNFs, and these 10 VNFs form a VPC identified as VPC-1. It is understood that if any VNF in a VPC is occupied, the VPC is considered occupied.
[0117] Through the above design, based on the usage information of reserved resources, at least one of the following information can be determined: which reserved resources are occupied, which reserved resources are idle, the utilization rate of occupied reserved resources, or the deployment of EAS in occupied reserved resources. This can then facilitate EAS deployment, such as prioritizing the deployment of EAS in idle reserved resources or prioritizing the deployment of ESA in reserved resources with low occupancy rates. Alternatively, when deleting reserved resources, the usage information of the reserved resources can be used to determine which reserved resources can be deleted, thereby avoiding the deletion of reserved resources for deploying EAS. When deleting reserved resources, the reserved resources will not be affected by the services provided by the reserved resources to the already deployed EAS.
[0118] Case 2: MANO is responsible for reserving resources and establishing network connections with UPF.
[0119] The ECSP management system sends a fourth request to the operator management system, where the fourth request is used to request connection information of the UPF corresponding to the location information. The operator management system sends a fourth response to the ECSP management system, where the fourth response includes the connection information of the UPF corresponding to the location information. The ECSP management system sends a first request to the MANO based on the reserved resource requirement information. In addition to reserving resources in the EDN corresponding to the location information, the first request is also used to request a network connection between the UPF and the reserved resources. The first request includes, for example, the connection information of the UPF.
[0120] For the above situation 2, as shown in FIG5 , a process is provided, including:
[0121] Step 501: The ECSP management system receives a request from an ASP to create a reservation object instance, where the reservation object instance includes demand information for reserved resources.
[0122] Step 502: The ECSP management system sends a fourth request to the operator management system, where the fourth request is used to request connection information of the UPF corresponding to the location information.
[0123] For example, the fourth request may include the location information of the reserved resources. The operator management system selects a UPF that meets the requirements based on the reserved resource location information. For example, in a region, there may be multiple UPFs, some of which are busy and some of which are idle. The idle UPF is the qualified UPF, etc. Alternatively, if there is a single UPF in a region, and the UPF can be uniquely identified based on the reserved resource location information, then this UPF is the qualified UPF, etc. The fourth request may also include network requirement information, such as bandwidth requirements. This network requirement information may be determined based on the bandwidth information in the reserved resource requirement information. For example, in the example above, if the bandwidth requirement of each VM in the reserved resource requirement information is 100 Mbps, then the network requirement information in the fourth request may be 100 Mbps. Alternatively, if there are 10 VMs in the reserved resources and the bandwidth requirement of these 10 VMs is 1000 Mbps, then the network requirement information in the fourth request may be 1000 Mbps, etc. The operator management system may determine the qualified UPF based on the network requirement information. For example, one or more UPFs may be determined based on the reserved resource location information. A UPF that meets the requirements can be determined based on the network demand information. For example, among the one or more UPFs that meet the location information, a UPF with a bandwidth greater than or equal to the UPF in the network demand information can be selected as the UPF that meets the requirements. For example, among the one or more UPFs that meet the location information, a UPF with a bandwidth greater than or equal to 100M (or 1000M) can be selected as the UPF that meets the requirements.
[0124] Step 503: The operator management system sends a fourth response to the ECSP management system. The fifth response includes the connection information of the UPF that meets the conditions. For example, the connection information of the UPF may be the IP address of the UPF.
[0125] Optionally, in step 504, the ECSP management system determines an NSD based on the UPF connection information and the reserved resource requirements. The NSD includes the topology and descriptions of each VNF. For details about the topology and descriptions of each VNF, see the description in Case 1. In addition, the NSD may also include network requirements for the connection between the reserved resources and the UPF, such as the network requirements (e.g., bandwidth) for the connection between the VL or VPC of the NS corresponding to the reserved resources and the UPF. Furthermore, the NSD also includes the address information of the UPF.
[0126] Step 505: The ECSP management system sends a first request to the MANO, where the first request is a request to instantiate the NSD.
[0127] MANO instantiates a network service provider (NS) based on the NSD. The NS instantiation process includes reserving resources in the EDN corresponding to the location information and establishing a network connection between the reserved resources and the UPF. In one design, the NS instantiation process includes creating a virtual network (VL) or virtual private network (VPC) containing the VNFs to be reserved. Furthermore, based on the network requirements in the NSD, MANO configures the network of the VL or VPC, such as its network bandwidth. A network connection is established between the VL or VPC and the UPF, configuring the UPF's address information in the VL or VPC's routes, and configuring the VL or VPC's routes in the UPF's routes. It should be noted that a reserved resource corresponds to at least one NS, and an NS corresponds to one VL or VPC. Therefore, the network connection between the reserved resource and the UPF can be described as a network connection between the NS and the UPF, or as a network connection between the VL or VPC and the UPF, etc. The address information of the reserved resource can be described as the address information of the NS, the address information of the VL or VPC, etc.
[0128] Step 506: MANO sends a first response to the ECSP management system. The first response is used to indicate that resource reservation is successful.
[0129] For example, the first response may be a response of instantiating the NS, etc.
[0130] Step 507: The ECSP management system creates a reserved work object instance and sends a response to the ASP indicating that the reserved work object instance has been successfully created.
[0131] For details about the reservation work object instance, refer to the description in Scenario 1. The difference is that the reservation work object now includes the usage status of the reserved resources. The ECSP management system can determine the usage status of the reserved resources when the reservation is successful. In Scenario 2, when the ECSP management system receives the first response from the MANO, it can be considered that the reservation of the reserved resources is successful, and the ECSP management system can determine the usage status of the reserved resources.
[0132] In either case 1 or 2, the ASP can query the ECSP management system for the reserved resource usage status based on the identifier of the reserved work object instance. The ASP can then deploy EAS, etc., based on the reserved resource usage status. For example, the ASP can deploy EAS in VNFs with idle reserved resources or in VNFs with utilization rates below a threshold.
[0133] With this design, before deploying an EAS application, the ASP reserves some resources in the EDN through the ECSP management system and MANO. These resources are called reserved resources. Subsequently, when the ASP requests EAS deployment from the ECSP management system, the ECSP management system will accommodate the ASP's EAS deployment request as long as the resource limit is within the reserved resources. This reduces the probability of EAS deployment failure and shortens the latency for users accessing the EAS application.
[0134] [Example 2]
[0135] In Example 2, an EAS is deployed within the reserved resources described in Example 1. For example, the ECSP management system receives a fifth request from the ASP requesting the deployment of an EAS within the reserved resources. The fifth request includes an identifier for the reserved resources. Through this design, after successfully reserving the resources, the ASP can deploy the EAS within the reserved resources. This resolves the issue of high latency for user access to the EAS, which can occur when the EAS is deployed in an EDN far from the user's location due to limited resources in the corresponding location and a "first-come, first-served" basis.
[0136] As shown in FIG6 , a process is provided, which can be used to deploy EAS. For example, the process of FIG6 can be used to deploy EAS in the reserved resources in the first embodiment, including:
[0137] Step 601: The reservation of the reserved resources is successful.
[0138] For example, one implementation method of successfully reserving the reserved resource is that the creation of the reserved work object instance is completed. For the specific implementation of step 601, please refer to the description of the first embodiment above.
[0139] Step 602: The ECSP management system receives a fifth request from the ASP, where the fifth request includes an identifier of reserved resources.
[0140] In one design, the identifier of the reserved resource may be the identifier of the reserved work object instance associated with the reserved work object. The ECSP management system may deploy the ASP's EAS in the reserved resources corresponding to the reserved work object instance. In one implementation, the ASP may query the usage status of the reserved resources through the ECSP management system, and the ASP may decide to deploy the EAS in one or more VNFs. At this time, the ASP needs to notify the ECSP management system of the identifiers of one or more VNFs. For example, the fifth request also includes: the identifiers of the one or more VNFs in which the EAS is deployed, etc. Alternatively, the ECSP management system determines whether to deploy the EAS in one or more VNFs in an idle state of the reserved resources, or to deploy the EAS in one or more VNFs whose usage rate is lower than a threshold. For example, the ECSP management system queries the usage status of the reserved resources shown in Table 1, and determines the VNF in which the EAS is deployed based on the usage status of the reserved resources, etc. It can be understood that an EAS can be deployed in one or more VNFs, etc., without limitation. At this time, the fifth request may no longer include the identifiers of the one or more VNFs in which the EAS is deployed.
[0141] Step 603: The ECSP management system sends a sixth request to the MANO, where the sixth request is used to request the MANO to deploy the EAS in the reserved resources.
[0142] For example, upon receiving the sixth request, MANO may deploy EAS in one or more VNFs that meet the conditions in the reserved resources. Deploying EAS includes loading the EAS application file in one or more VNFs that meet the conditions. Optionally, the EAS application file may also be referred to as an EAS image file. The EAS application file is preset, or obtained by MANO through the ECSP management system. For example, the sixth request includes EAS application file information (such as the address information of the application file). MANO can download the application file at the corresponding location based on the address information of the application file.
[0143] Furthermore, the ECSP management system can obtain EAS application file information through the ASP. For example, the fifth request also includes EAS application file information. The one or more VNFs that meet the conditions, that is, the one or more VNFs deployed with EAS, can be determined by the MANO itself, or determined by the ECSP and indicated to the MANO. For example, the sixth request includes the identifiers of the one or more VNFs, or determined by the ASP, indicated to the ECSP, and then indicated to the MANO. For example, both the fifth and sixth requests include the identifiers of the one or more VNFs.
[0144] In one implementation, the ECSP management system can determine the NS corresponding to the reserved resources based on the identifier of the reserved work object instance sent by the ASP, and obtain the usage status of the reserved resources. In the usage status of the reserved resources, a VNF that meets the conditions is selected. For example, the VNF that meets the conditions is a VNF whose usage status is idle, or a VNF whose usage rate is less than a threshold. Optionally, the VNF that meets the conditions is a VNF that deploys EAS. A specific implementation of the sixth request in step 602 is an update request, and the sixth request is used to request MANO to update the VNF that meets the conditions, that is, to load the EAS application software in the VM corresponding to the VNF that meets the conditions, and the sixth request includes the identifier of the VNF that meets the conditions. Furthermore, it also includes: the identifier of the NS corresponding to the VNF that meets the conditions.
[0145] In one implementation, a specific implementation of step 602 and step 603 is as follows: the ASP generates an EAS requirement object, and the ASP sends a fifth request to the ECSP management system. The fifth request is a request to create an EAS requirement object instance, and the fifth request includes the identifier of the EAS requirement object and the reserved work object instance. The EAS requirement object includes the requirement information required for deploying EAS, such as the location information for deploying EAS, the virtual resources required for deploying EAS, and the EAS application files. The ECSP management system needs the EAS requirement object to determine the EAS function object. For example, the EAS requirement object includes one or more EAS deployment requirements. For example, if an EAS requirement object is a game-related requirement object, the EAS requirement object includes the requirements for deploying location-related EAS and the requirements for recharge service-related EAS. The ECSP management system determines at least one EAS function object based on the EAS requirement object, and each EAS function object includes an EAS deployment requirement. For each EAS functional object, the ECSP management system selects a VNF that meets the requirements based on the reserved resource usage status and sends a sixth request to the MANO to deploy EAS in the VNF that meets the requirements. For example, the sixth request can be an update request, requesting that the EAS application files, etc., be loaded in the VNF that meets the requirements.
[0146] Step 604: The MANO sends a sixth response to the ECSP management system. The sixth response is used to indicate that the EAS is successfully deployed in the reserved resources.
[0147] As described above, the sixth request may be an update request, which is used to request the MANO to update the VNF that meets the conditions, that is, to deploy EAS in the VNF that meets the conditions. The sixth response may be a NS instance update success response.
[0148] Step 605: The ECSP management system updates the usage status of the reserved resources.
[0149] For example, the ECSP management system updates VNF and other information in the usage status of the reserved resources shown in Table 1. For example, as shown in Table 2, the identifier of the VNF deployed with EAS is VNF1, and EAS occupies all resources of the VNF, then the reserved resource utilization rate of VNF1 is updated to 100%, the usage status of VNF1's reserved resources is updated to occupied, and the identifier of EAS deployment in VNF1's reserved resources is updated to the identifier of EAS deployment. In Table 2, the identifier of EAS deployment is EAS-1 as an example. Further, the information of the VPC to which VNF1 belongs (i.e., VPC-1) is updated. For example, the usage status of VPC-1's reserved resources is updated to occupied, and the identifier of EAS deployment in VPC-1's reserved resources is updated to EAS-1. Since VPC-1 includes 10 VNFs and only VNF-1 is occupied, the usage rate of VPC-1's reserved resources is 10%.
[0150] Table 2
[0151] Optionally, after step 605, the ECSP management system sends an update indication of the reserved work object instance to the ASP. Upon receiving the indication, the ASP determines that the reserved resources corresponding to the reserved work object instance have been updated. The ASP queries the usage status of the reserved resources through the ECSP management system.
[0152] Step 606: The ECSP management system creates an EAS requirement object instance and an EAS function object instance, and sends a successful creation response of the EAS requirement object instance and the EAS function object instance to the ASP.
[0153] In the embodiments of the present application, after an EAS is successfully deployed, it may be migrated. For example, if some servers within the EDN running the EAS need to be shut down for maintenance or upgrades, the EAS may need to be migrated to other servers. Alternatively, due to insufficient resources within the EDN, the EAS may need to be migrated to other servers. The ASP can configure a migration policy when deploying the EAS. For example, the fifth request may also include information about the EAS migration policy, thereby ensuring that the services provided by the EAS are not affected, or are minimally affected.
[0154] As shown in FIG7 , a process is provided. The main difference from the process in FIG6 is that when deploying EAS, an EAS migration policy can be configured. Then, the deployed EAS can be migrated according to the configured migration policy, including:
[0155] Step 701: The reservation of the reserved resources is successful.
[0156] In one design, a successful reservation of the reserved resources is achieved by completing instantiation of the reserved work object.
[0157] Step 702: The ECSP management system receives a fifth request from the ASP. The fifth request includes not only the identifier of the reserved resources but also migration policy information.
[0158] Illustratively, the migration policy information includes at least one of the following: a migration condition or a migration scope. Optionally, the migration condition includes whether migration is allowed, not allowed, or whether the ASP needs to be consulted before migration. The migration scope includes whether the EAS can be migrated within the same reserved resource, between different reserved resources in the same EDN, or between different EDNs.
[0159] In one design, the ASP may generate an EAS requirement object that includes a migration policy, which may be referred to as a movement and notification parameter. The value of the parameter may be any of the following:
[0160] 1. Migration allowed: movement allowed.
[0161] The scope of migration is: EAS migration is allowed within the same reserved resource, or EAS migration is allowed between different reserved resources in the same EDN, or EAS migration is allowed between different EDNs, etc.
[0162] 2. Allow migration, but you need to ask ASP before migration: movement allowed with notification.
[0163] The scope of migration is the same as that when migration is allowed and will not be repeated here.
[0164] 3. No migration allowed: no movement.
[0165] For example, if a condition is met, a successfully deployed EAS cannot be migrated. For example, a condition could be: If the migration is across EDNs, a successfully deployed EAS cannot be migrated. Alternatively, if no condition is defined, the ECSP management system is not recommended to migrate the EAS to other servers after it is successfully deployed.
[0166] Step 703: The ECSP management system sends a sixth request to the MANO according to the identification information of the reserved resources. The sixth request is used to request the MANO to deploy the EAS in the reserved resources.
[0167] For example, the ECSP management system can determine EAS functional objects based on the EAS requirement object. Each EAS required for deployment in the EAS requirement object corresponds to an EAS functional object. For each EAS functional object, the ECSP management system can select a VNF that meets the requirements from the reserved resources and request the MANO to instantiate the VNF. Instantiating the VNF includes deploying the EAS in the VNF that meets the requirements.
[0168] Step 704: MANO sends a sixth response to the ECSP management system, where the sixth response includes an instantiation success response.
[0169] Step 705: Update the usage status of the reserved resources.
[0170] Step 706: The ECSP management system creates an EAS requirement object instance and an EAS function object instance, and sends a successful creation response of the EAS requirement object instance and the EAS function object instance to the ASP.
[0171] The EAS requirement object instance includes the identifier of the EAS requirement object instance, the identifier of the deployed EAS, the identifier of the VNF deployed by each EAS, the identifier of the NS to which the VNF belongs, and the address information of each EAS, etc. One EAS corresponds to one EAS function object instance, or it can be described as one EAS function object instance corresponding to one EAS deployment, etc. The EAS function object instance includes the identifier of the EAS function object instance, the identifier of the deployed EAS, the identifier of the VNF deployed by the EAS, the identifier of the NS to which the VNF belongs, and the address information of each EAS, etc.
[0172] Step 707: When the ECSP management system needs to trigger the EAS to perform migration, it obtains migration policy information according to the EAS requirement object instance associated with the EAS and takes corresponding actions.
[0173] For example, when the ECSP management system finds that the deployed EAS needs to be migrated due to upgrade, resource shortage or other reasons within the EDN, it obtains the migration policy information based on the EAS requirement object instance associated with the EAS.
[0174] If the migration policy information is: migration is allowed; the migration scope is: migration is allowed within the same reserved resource. Then the ECSP management system requests the MANO to migrate the EAS within the resources reserved by the same reserved work object instance. Or,
[0175] If the migration policy information indicates "allow migration, but require pre-migration notification to the EAS" and the migration scope is "migration across different EDNs," the ECSP management system may send a query message to the ASP, asking whether the ASP agrees to the EAS migration. If the ASP agrees to the EAS migration, the ECSP management system then requests the MANO to migrate the EAS between different EDNs. In one implementation, in step 706, when creating the EAS function object instance, the EAS function object instance includes a movement action parameter, with the initial value of "no movement." If the migration policy information indicates "allow migration, but require pre-migration notification to the EAS," the ECSP management system updates the movement action parameter in the EAS function object instance associated with the EAS to be migrated to "movement required" and sends the updated EAS function object instance information to the ASP. The ASP determines whether to allow the EAS migration based on the operational status of the EAS associated with the EAS function object instance. For example, if the operational status of the associated EAS indicates that the EAS is currently providing services to users, the ASP may determine that the EAS migration is not allowed; otherwise, the ASP may determine that the EAS migration is allowed. Furthermore, if the ASP allows EAS migration, the ASP updates the migration behavior parameter in the EAS function object instance to "movement allowed," and the ECSP management system requests the MANO to execute the migration operation. Alternatively, if the ASP does not allow EAS migration, the ASP updates the migration behavior parameter in the EAS function object instance to "movement not allowed," and the ECSP management system executes a temporary hold on migration operation.
[0176] Through the above design, ASP configures a migration policy when deploying EAS. When EDN needs to migrate EAS to another server due to maintenance or upgrade, it can migrate EAS according to the EAS migration policy to ensure that the services provided by EAS are not affected or the impact is minimized.
[0177] [Example 3]
[0178] As shown in FIG8 , the embodiment of the present application further provides a process that can be used to delete reserved resources. For example, the process can be used to delete the reserved resources in Example 1, including:
[0179] Step 801: The ECSP management system receives a seventh request from the ASP, the seventh request being used to request deletion of a reserved resource, for example, the seventh request being used to request deletion of a reserved work object instance, and the seventh request including an identifier of the reserved work object instance.
[0180] In case 1, the ASP inquires the ECSP management system about the usage of the reserved resources based on the identifier of the reserved object instance, and deletes or migrates all EAS deployed on the reserved resources as needed. When all reserved resources are idle, the ASP sends a request to the ECSP management system to delete the reserved work object instance.
[0181] In case 2, the ASP directly sends a request to delete the reserved work object instance to the ECSP management system. The request may carry an instruction to retain the EAS deployed in the reserved resources.
[0182] Optionally, step 802: the ECSP management system determines usage of reserved resources corresponding to the reserved work object instance.
[0183] Step 803: The ECSP management system sends an NS update request to the MANO. The NS update request is used to delete the reserved resources.
[0184] In case 1, all reserved resources are idle, and the ECSP management system can directly delete the reserved work object instance. In case 2, the ECSP management system requests the MANO to delete the unoccupied VNFs from the reserved resources and retain the occupied VNFs in the reserved resources. The occupied VNFs are the VNFs deployed with EAS. For example, in the example in Table 2, the reserved resources include 10 VNFs, and only VNF1 is occupied. In this case, only VNF1 can be retained, and VNF2 through VNF10 can be deleted. Furthermore, only the VL or VPC network resources used by VNF1 can be retained, and the network resources for other VNFs can be deleted. For example, if a VL or VPC network reserves 100M bandwidth, but EAS1 deployed in VNF1 only uses 10% of the network bandwidth, only 10M bandwidth can be retained, and the remaining 90M bandwidth can be released.
[0185] Step 804: MANO sends an NS update success response to the ECSP management system.
[0186] Optionally, if all reserved resources associated with the reserved work object instance are deleted, the following may also be included:
[0187] Step 805: If the operator management system is responsible for establishing the connection between the NS and the UPF, the ECSP management system requests the operator management system to delete the connection between the NS and the UPF, for example, by deleting the EcmConnectionInfo object instance.
[0188] Optionally, the EcmConnectionInfo object instance is created by the operator management system, and the object instance stores the connection information between the NS and the UPF.
[0189] Step 806: The operator management system sends a successful deletion response of the NS and UPF connection to the ECSP management system, for example, a successful deletion response of the reserved work object instance. Or,
[0190] If the connection between NS and UPF is established by MANO, MANO may also delete the network connection between NS and UPF when deleting all reserved resources.
[0191] Through the above design, when the reserved resources are successfully reserved, if the ASP no longer uses the reserved resources, the reserved resources can be deleted to avoid waste of the reserved resources.
[0192] It should be noted that, in the embodiments of this application:
[0193] 1. The differences between different embodiments are described emphatically. The descriptions of different embodiments can refer to each other.
[0194] 2. In each embodiment, unless otherwise specified or there is a logical conflict, the terms and / or descriptions between different embodiments are consistent and can be referenced to each other. The technical features in different embodiments can be combined to form a new embodiment based on their inherent logical relationships.
[0195] 3. The various numbers used in the embodiments of this application are for ease of description only and are not intended to limit the scope of the embodiments of this application. The order of the numbers of the above-mentioned processes does not imply a specific order of execution. The order of execution of each process should be determined by its function and internal logic.
[0196] 4. In the processes of Figures 3 to 8, the order in which the different steps are executed is not limited. For example, in Figure 6, step 605 may be executed before or after step 606, etc. Each process of Figures 3 to 8 may include fewer or more steps than the flowchart or text description, without limitation.
[0197] In the embodiments provided above, the methods provided in the embodiments of this application are described from the perspective of the interaction between various devices. To implement the various functions of the methods provided in the embodiments of this application, the ASP, ECSP management system, MANO, or operator management system, etc., may include hardware structures and / or software modules, and implement the aforementioned functions in the form of hardware structures, software modules, or hardware structures and software modules. Whether a particular function is implemented in the form of hardware structures, software modules, or hardware structures and software modules depends on the design constraints of the specific application of the technical solution.
[0198] Figures 9 and 10 are schematic diagrams of possible devices provided in embodiments of the present application. These communication devices can implement one or more corresponding functions in the above-described method embodiments. For example, functions implemented by an ECSP management system or an ASP, etc., can thus achieve the beneficial effects of the above-described method embodiments.
[0199] As shown in FIG9 , the communication device 900 includes a processing unit 910 and a transceiver unit 920. Optionally, a unit may also be referred to as a module. For example, the processing unit may also be referred to as a processing module, and the transceiver unit may also be referred to as a transceiver module.
[0200] For example, a processing unit may also be referred to as a processor, processing board, processing module, processing device, etc. A communication unit may also be referred to as a transceiver, transceiver, transceiver module, transceiver device, etc. Furthermore, a communication unit may include at least one of a transmitting unit and a receiving unit. The transmitting unit and the receiving unit may be integrated or two independent units.
[0201] In one design, a communication device 900 is used to implement the functions of the ECSP management system in Figures 3 to 8. Specifically, a transceiver unit 920 is used to receive reserved resource demand information from an application service provider (ASP), where the reserved resource demand information includes location information of the reserved resources. A processing unit 910 is used to control the transceiver unit 920 to send a first request to a management and orchestration system (MANO) based on the reserved resource demand information. The first request is used to request the MANO to reserve resources in an edge data network (EDN) corresponding to the location information. The reserved resources have a network connection with a user plane function (UPF) corresponding to the location information. The reserved resources are used to deploy an edge application server (EAS) of the ASP.
[0202] In another design, the communication device 900 is used to implement the functions in the ASP in Figures 3 to 8, specifically: the processing unit 910 is used to determine the demand information of reserved resources, and the demand information of reserved resources includes at least the location information of the reserved resources; the transceiver unit 920 is used to send the demand information of the reserved resources to the edge computing service provider ECSP management system, and there is a network connection between the reserved resources and the user plane function UPF corresponding to the location information, and the reserved resources are used to deploy the edge application server EAS of the ASP.
[0203] For a more detailed description of the processing unit 910 and the transceiver unit 920, reference may be made to the descriptions of FIG. 3 to FIG. 8 in the above method embodiment, which will not be repeated here.
[0204] It is understood that the division of units in the embodiments of the present application is schematic and is only a logical functional division. In actual implementation, there may be other division methods. In addition, the various functional units in the embodiments of the present application can be integrated into a physical device (for example, a processor), or each functional unit can be a separate physical device, or two or more units can be integrated into a unit for implementation. The above-mentioned integrated units can be implemented in the form of hardware or in the form of software functional modules.
[0205] Figure 10 shows another schematic diagram of the structure of a communication device 1000 provided in an embodiment of the present application. For example, the communication device 1000 shown in Figure 10 can be a hardware circuit implementation of the communication device 900 shown in Figure 9. For ease of illustration, Figure 10 only shows the main parts of the communication device.
[0206] As shown in Figure 10, the communication device 1000 includes a processor 1010 and an interface circuit 1020. The processor 1010 and the interface circuit 1020 are coupled to each other.
[0207] For example, the processor 1010 may be a central processing unit (CPU), other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field programmable gate arrays (FPGA), other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. The general-purpose processor may be a microprocessor or any conventional processor. The interface circuit 1020 may be a transceiver or an input / output circuit, etc.
[0208] Optionally, the communication device 1000 may further include a memory 1030 for storing instructions executed by the processor 1010, or storing input data required by the processor 1010 to execute instructions, or storing data generated after the processor 1010 executes instructions. For example, instructions may also be referred to as computer programs, or computer program codes, etc.
[0209] For example, the memory 1030 can be a random access memory (RAM), a flash memory, a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), a register, a hard disk, a mobile hard disk, a CD-ROM, or any other form of storage medium known in the art.
[0210] When the communication device 1000 is used to implement the methods shown in FIG. 3 to FIG. 8 , the processor 1010 is used to implement the functions of the processing unit 910 , and the interface circuit 1020 is used to implement the functions of the transceiver unit 920 .
[0211] In one implementation, the interface circuit 1020 is used to receive signals from other communication devices outside the communication device 1000 and transmit them to the processor 1010, or to send signals from the processor 1010 to other communication devices outside the communication device. The processor 1010 implements the functions in Figures 3 to 8 above through logic circuits or executing code instructions.
[0212] An embodiment of the present application also provides a communication device, which includes a processor and a memory, the processor and the memory are coupled, and the processor is used to implement the functions in Figures 3 to 8. For example, the processor can execute instructions in the memory so that the communication device implements one or more functions in the above-mentioned method embodiments, such as the functions of Figures 3 or 8. An exemplary storage medium is coupled to the processor so that the processor can read information from the storage medium and write information to the storage medium. Of course, the storage medium can also be an integral part of the processor. The processor and the storage medium can be located in an ASIC. In addition, the ASIC can be located in an ECSP management system or ASP in Figures 3 to 8, etc. The processor and the storage medium can also exist as discrete components in the ECSP management system or ASP in Figures 3 to 8, etc.
[0213] The present application also provides a computer-readable storage medium storing instructions, which may also be referred to as a computer program, computer program code, etc. The instructions, when executed on a computer, cause the computer to perform the functions illustrated in Figures 3 through 8 of the method embodiments described above, such as the functions of the ECSP management system or ASP in Figures 3 through 8 .
[0214] Optionally, the computer may be a general-purpose computer, a special-purpose computer, a computer network, a network device, a user device, or other programmable device. The computer program or instructions may be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer program or instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via a wired or wireless method. 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 that integrates one or more available media. The available medium may be a magnetic medium, such as a floppy disk, a hard disk, or a magnetic tape; an optical medium, such as a digital video disc; or a semiconductor medium, such as a solid-state drive. The computer-readable storage medium may be a volatile or non-volatile storage medium, or may include both volatile and non-volatile types of storage media.
[0215] The present application also provides a computer program product, including a computer program or instructions. When the computer program or instructions are executed on a computer, the methods described in Figures 3 through 8 are performed. For example, the functions of the ECSP management system or ASP described in Figures 3 through 8 are performed. For example, the computer program product includes one or more computer programs or instructions. When the computer program or instructions are loaded and executed on a computer, the processes or functions described in Figures 3 through 8 of the present application are performed in whole or in part.
[0216] It is understood that the methods in the embodiments of the present application can be implemented in whole or in part by software, hardware, firmware, or any other combination. When implemented by software, they can be implemented in whole or in part in the form of a computer program product.
[0217] An embodiment of the present application further provides a chip, comprising a processor coupled to a memory. The processor is configured to execute computer programs or instructions stored in the memory, enabling the chip to implement the functions shown in Figures 3 to 8. For example, the chip implements the functions of the ECSP management system or ASP shown in Figures 3 to 8. For example, using the chip as an example of implementing the functions of the ECSP management system, the chip can receive information from other modules (such as a radio frequency or antenna) within the ECSP management system. This information can be sent by the ASP to the ECSP management system. Alternatively, the ECSP management system can send information to other modules (such as a radio frequency or antenna) within the ECSP management system. This information is sent by the ECSP management system to the MANO, etc.
[0218] An embodiment of the present application also provides a communication system, including: a first communication device and a MANO. The first communication device can implement the functions of the ECSP management system described in Figures 3 to 8 above. For the specific structure of the first communication device, please refer to the description above, such as the description in Figures 9 or 10. Optionally, it also includes: an operator management system. Furthermore, it also includes: a second communication device. The second communication device can implement the functions of the ASP described in Figures 3 to 8 above. For the specific structure of the second communication device, please refer to the description above, such as the description in Figures 9 or 10.
[0219] Obviously, those skilled in the art may make various changes and modifications to the present application without departing from the scope of the present application. Thus, if these modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is intended to include these modifications and variations.
Claims
1. An edge application method, characterized in that: The method is applied to an edge computing service provider ECSP management system, including: Receiving demand information for reserved resources from an application service provider ASP, wherein the demand information for reserved resources includes location information of the reserved resources; According to the demand information of the reserved resources, a first request is sent to the management and orchestration system MANO, wherein the first request is used to request the MANO to reserve resources in the edge data network EDN corresponding to the location information, and the reserved resources are network connected to the user plane function UPF corresponding to the location information, and the reserved resources are used to deploy the edge application server EAS of the ASP.
2. The method according to claim 1, characterized in that The demand information of the reserved resources also includes at least one of the following: the quantity of the reserved resources, the performance parameters of the reserved resources, or the expiration time of the reserved resources.
3. The method according to claim 1 or 2, characterized in that Also includes: When the reserved resource is successfully reserved, the usage status information of the reserved resource is determined, and the usage status information of the reserved resource includes at least one of the following: an identifier of the reserved resource, a usage status of the reserved resource, an identifier of the EAS deployed in the reserved resource, or a usage rate of the reserved resource.
4. The method according to claim 3, characterized in that The identifier of the reserved resources includes: the identifier of the virtualized network function VNF and the identifier of the network service NS to which the VNF belongs; the usage of the reserved resources includes: whether the VNF is in an idle state or in an occupied state.
5. The method according to any one of claims 1 to 4, characterized in that After sending the first request to the MANO according to the demand information for the reserved resources, the method further includes: A second request is sent to the operator management system, where the second request is used to request the operator management system to establish a network connection between the UPF and the reserved resources, and the second request includes connection information of the reserved resources.
6. The method according to claim 5, characterized in that After sending the second request to the operator management system, the method further includes: receiving a second response from the operator management system, wherein the second response includes connection information of the UPF; Send a third request to the MANO, where the third request is used to request the MANO to update connection information between the reserved resources and the UPF, and the third request includes the connection information of the UPF.
7. The method according to any one of claims 1 to 4, characterized in that Before sending the first request to the MANO according to the demand information for the reserved resources, the method further includes: Sending a fourth request to the operator management system, where the fourth request is used to request connection information of the UPF corresponding to the location information; A fourth response is received from the operator management system, wherein the fourth response includes connection information of the UPF corresponding to the location information.
8. The method according to any one of claims 1 to 7, characterized in that Also includes: A fifth request is received from the ASP, where the fifth request is used to request to deploy the EAS in the reserved resources, and the fifth request includes an identifier of the reserved resources.
9. The method according to claim 8, characterized in that The fifth request also includes: migration policy information of the EAS, and the migration policy information includes at least one of the following: a migration condition or a migration range.
10. The method according to claim 9, characterized in that The migration conditions include: allowing migration, not allowing migration, or whether the ASP needs to be consulted before migration; the migration scope includes: migrating the EAS within the same reserved resource, migrating the EAS within different reserved resources in the same EDN, or migrating the EAS in different EDNs.
11. An edge application method, characterized in that: The method is applied to an application service provider ASP, and comprises: Determining demand information for reserved resources, wherein the demand information for reserved resources includes at least location information of the reserved resources; The demand information of the reserved resources is sent to the edge computing service provider ECSP management system, a network connection exists between the reserved resources and the user plane function UPF corresponding to the location information, and the reserved resources are used to deploy the edge application server EAS of the ASP.
12. The method according to claim 11, characterized in that The demand information of the reserved resources also includes at least one of the following: the quantity of the reserved resources, the performance parameters of the reserved resources, or the expiration time of the reserved resources.
13. The method according to claim 11 or 12, characterized in that Also includes: Sending a fifth request to the ECSP management system, where the fifth request is used to request to deploy the EAS in the reserved resources, and the fifth request includes an identifier of the reserved resources.
14. The method according to claim 13, characterized in that The fifth request also includes: migration policy information of the EAS, and the migration policy information includes at least one of the following: a migration condition or a migration range.
15. The method according to claim 14, characterized in that The migration conditions include: allowing migration, not allowing migration, or whether the ASP needs to be consulted before migration; the migration scope includes: migrating the EAS within the same reserved resource, migrating the EAS within different reserved resources in the same EDN, or migrating the EAS in different EDNs.
16. An edge application method, characterized in that: include: The edge computing service provider ECSP management system receives the reserved resource demand information from the application service provider ASP, and sends a first request to the management and orchestration system MANO according to the reserved resource demand information; The demand information for the reserved resources includes location information of the reserved resources, the first request is used to request the MANO to reserve resources in an edge data network EDN corresponding to the location information, the reserved resources are network connected to a user plane function UPF corresponding to the location information, and the reserved resources are used to deploy an edge application server EAS of the ASP; The MANO receives the first request from the ECSP management system.
17. The method according to claim 16, characterized in that Also includes: The MANO reserves resources in the EDN corresponding to the location information according to the first request.
18. The method according to claim 16 or 17, characterized in that Also includes: The ASP sends the demand information of the reserved resources to the ECSP management system.
19. The method according to any one of claims 16 to 18, characterized in that The demand information of the reserved resources also includes at least one of the following: the quantity of the reserved resources, the performance parameters of the reserved resources, or the expiration time of the reserved resources.
20. The method according to any one of claims 16 to 19, characterized in that Also includes: When the reserved resource is successfully reserved, the ECSP management system determines usage status information of the reserved resource, where the usage status information of the reserved resource includes at least one of the following: an identifier of the reserved resource, a usage status of the reserved resource, an identifier of an EAS deployed in the reserved resource, or a usage rate of the reserved resource.
21. The method of claim 20, wherein: The identifier of the reserved resources includes: the identifier of the virtualized network function VNF and the identifier of the network service NS to which the VNF belongs; the usage of the reserved resources includes: whether the VNF is in an idle state or in an occupied state.
22. The method according to any one of claims 16 to 21, characterized in that After the ECSP management system sends the first request to the MANO according to the demand information of the reserved resources, the method further includes: The ECSP management system sends a second request to the operator management system, where the second request is used to request the operator management system to establish a network connection between the UPF and the reserved resources, and the second request includes connection information of the reserved resources; The operator management system establishes a network connection between the UPF and the reserved resources according to the second request.
23. The method of claim 22, wherein: Also includes: The operator management system sends a second response to the ECSP management system, where the second response includes connection information of the UPF; The ECSP management system sends a third request to the MANO, where the third request is used to request the MANO to update connection information between the reserved resources and the UPF; The MANO updates the connection information between the reserved resources and the UPF according to the connection information of the UPF included in the third request.
24. The method according to any one of claims 16 to 21, characterized in that Before the ECSP management system sends the first request to the MANO according to the demand information of the reserved resources, the ECSP management system further includes: The ECSP management system sends a fourth request to the operator management system, where the fourth request is used to request connection information of the UPF corresponding to the location information; The operator management system sends a fourth response to the ECSP management system, where the fourth response includes connection information of the UPF corresponding to the location information.
25. The method according to any one of claims 16 to 24, characterized in that Also includes: The ECSP management system receives a fifth request from the ASP, where the fifth request is used to request to deploy the EAS in the reserved resources, and the fifth request includes an identifier of the reserved resources.
26. The method of claim 25, wherein: Also includes: The ASP sends the fifth request to the ECSP management system.
27. The method according to claim 25 or 26, characterized in that The fifth request also includes: migration policy information of the EAS, and the migration policy information includes at least one of the following: a migration condition or a migration range.
28. The method of claim 27, wherein: The migration conditions include: allowing migration, not allowing migration, or whether the ASP needs to be consulted before migration; the migration scope includes: migrating the EAS within the same reserved resource, migrating the EAS within different reserved resources in the same EDN, or migrating the EAS in different EDNs.
29. A communication device, characterized in that: include: Unit for performing the method according to any one of claims 1 to 10.
30. A communication device, characterized in that: The device comprises a processor and a memory, wherein the processor is configured to execute a computer program or instruction stored in the memory, so that the communication device implements the method according to any one of claims 1 to 10.
31. A communication device, characterized in that: It includes a processor and an interface circuit, wherein the interface circuit is used to receive signals from other communication devices outside the communication device and transmit them to the processor or send signals from the processor to other communication devices outside the communication device, and the processor is used to implement the method as described in any one of claims 1 to 10 through a logic circuit or executing code instructions.
32. A communication device, characterized in that: include: Unit for performing the method according to any one of claims 11 to 15.
33. A communication device, characterized in that: The device comprises a processor and a memory, wherein the processor is configured to execute a computer program or instruction stored in the memory, so that the communication device implements the method according to any one of claims 11 to 15.
34. A communication device, characterized in that: It includes a processor and an interface circuit, wherein the interface circuit is used to receive signals from other communication devices outside the communication device and transmit them to the processor or send signals from the processor to other communication devices outside the communication device, and the processor is used to implement the method as described in any one of claims 11 to 15 through a logic circuit or executing code instructions.
35. A chip, characterized in that: The chip comprises a processor, which is coupled to a memory and is used to execute a computer program or instruction stored in the memory, so that the chip implements the method of any one of claims 1 to 10, or the method of any one of claims 11 to 15.
36. A computer-readable storage medium, characterized in that: A computer program or instruction is stored, and when the computer program or instruction is executed on a computer, the computer is caused to implement the method according to any one of claims 1 to 10, or the method according to any one of claims 11 to 15.
37. A computer program product, characterized in that The device comprises a computer program or an instruction, and when the computer program or the instruction is executed by the device, the method according to any one of claims 1 to 10 is executed, or the method according to any one of claims 11 to 15 is executed.
38. A communication system, characterized in that: include: A first communication device and a management orchestration system MANO, wherein the first communication device is used to implement the method according to any one of claims 1 to 10.
39. The system of claim 38, wherein: Also includes: Operator management system.
40. The system of claim 38 or 39, wherein: Also includes: A second communication device, wherein the second communication device is used to implement the method according to any one of claims 11 to 15.
Citation Information
Patent Citations
Resource processing method and related device
CN109587024A
Virtual machine resource allocation method, device and system and storage medium
CN112860370A
Edge computing applications for 5g systems
WO2022020043A1
Support for edge enabler server and edge configuration server lifecycle management
WO2022154961A1
Methods and apparatus for enhanced lifecycle management in 5g edge computing servers
WO2023018727A1
