Edge application method and device
By reserving resources in the edge data network and establishing connections with user plane function network elements, the problems of edge application server deployment failure and user access latency are solved, achieving more efficient resource utilization and lower user access latency.
Patent Information
- Application Number
- CN202310532533.3
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2023-05-11
- Publication Date
- 2024-11-12
AI Technical Summary
In edge data networks, the deployment of edge application servers may fail due to insufficient remaining resources, and due to the "first-come, first-served" mechanism, EAS may be deployed in EDN that is far from the user's location, resulting in increased user access latency.
By reserving resources in the edge computing service provider management system, including location information, quantity, performance parameters, and expiration time, sufficient resources are ensured before deployment, and network connections with user plane function network elements are established in advance to avoid deployment failures and user access latency caused by insufficient resources.
It effectively reduces the probability of edge application server deployment failure, reduces user access latency, and improves resource utilization and service reliability.
Smart Images

Figure CN118945733A_ABST
Abstract
Description
Technical Field
[0001] 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
[0002] The basic concept of edge computing is to run computing tasks on computing resources close to the data source, thereby effectively reducing the latency of the computing system, reducing the data transmission bandwidth, alleviating the pressure on the cloud computing center, improving availability, and protecting data security and privacy. When deploying edge application servers (EAS) in the edge data network (EDN), a "first come, first served" mechanism is adopted. When the remaining resources in the EDN cannot meet the deployment requirements of the EAS, it may lead to problems such as EAS deployment failure. Summary of the invention
[0003] The embodiments of the present application provide an edge application method and device, which reduce 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.
[0004] In a first aspect, an edge application method is provided. The method is applied to an edge computing service provider ECSP management system. The execution subject of the method may be the ECSP management system, or a chip or circuit applied to the ECSP management system. Taking the ECSP management system as an execution subject as an example, the method includes: the ECSP management system receives demand information of reserved resources from an application service provider ASP, where the demand information of the reserved resources includes location information of the reserved resources; the ECSP management system sends a first request to a management and orchestration system MANO according to the demand information of the reserved resources, 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 network element UPF corresponding to the location information, and the reserved resources are used to deploy an edge application server EAS of the ASP.
[0005] Through the above design, ASP can request to reserve some resources before deploying EAS applications. For example, ASP sends the demand information of reserved resources to ECSP management system, and ECSP management system sends a first request to MANO based on the demand information of reserved resources, and MANO reserves resources in the EDN corresponding to the location information required by the reserved resources based on the first request. After that, after the resource reservation is successful, ASP can request to ECSP management system to deploy EAS within the reserved resources. In this way, as long as it is within the reserved resource quota, ECSP management system can meet the needs of ASP to deploy EAS applications, thereby solving the problem of high failure rate of EAS deployment due to the "first come, first served" mechanism when deploying EAS.
[0006] In one design, the demand information for reserved resources also includes at least one of the following: the quantity of reserved resources, performance parameters of reserved resources, or expiration time of reserved resources.
[0007] Through the above design, the demand information of reserved resources may include the number of reserved resources, 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 reserved resources, the storage capacity of reserved resources, or the network bandwidth of reserved resources. According to at least one of the number of reserved resources or the performance parameters of reserved resources, resources that meet the number and performance parameters can be selected in the EDN at the corresponding position as reserved resources. Furthermore, the demand information of reserved resources also includes the expiration time of reserved resources. The expiration time of reserved resources can also be called the effective time of reserved resources. When the expiration time is reached or exceeds the effective time, the reserved resources become invalid and are no longer reserved for 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 reserved resources.
[0008] 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 usage rate of the reserved resources.
[0009] Through the above design, at least one of the following information can be determined based on the usage status information of the reserved resources: which reserved resources are occupied, which reserved resources are idle, the utilization rate of the occupied reserved resources, or the deployment of EAS in the occupied reserved resources. Afterwards, it can facilitate the deployment of EAS, such as giving priority to deploying EAS in idle reserved resources, or giving priority to deploying ESA in reserved resources with low occupancy rates. Alternatively, when deleting reserved resources, it is also possible to determine which reserved resources can be deleted based on the usage information of the reserved resources, thereby avoiding deleting the reserved resources for deploying EAS. When deleting reserved resources, it does not affect the reserved resources to provide services for the already deployed EAS.
[0010] 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 in an occupied state.
[0011] In one design, after sending a first request to MANO based on the demand information of reserved resources, it also includes: sending a second request to the operator management system, 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.
[0012] 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 connected, 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.
[0013] 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 MANO, the third request is used to request MANO to update the connection information between the reserved resources and the UPF, and the third request includes the connection information of the UPF.
[0014] 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 connection information of the UPF corresponding to the location information; receiving a fourth response from the operator management system, the fourth response including connection information of the UPF corresponding to the location information.
[0015] In one design, the method further includes: receiving a fifth request from the ASP, the fifth request being used to request deployment of the EAS in the reserved resources, the fifth request including an identifier of the reserved resources.
[0016] 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 when EAS is deployed.
[0017] 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.
[0018] Through the above design, when ASP requests to deploy EAS, the fifth request for deploying EAS also includes the migration strategy of EAS. When EAS has a migration requirement, for example, some servers running EAS may need to be shut down due to maintenance or upgrade in EDN, then EAS needs to be migrated to other servers. Or, due to insufficient resources in EDN, EAS may also need to be migrated to other servers, etc. EAS can be migrated according to the migration strategy information of EAS, so as to ensure that the services provided by EAS are not affected, or the impact is small.
[0019] 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 resources, migrating the EAS within different reserved resources in the same EDN, or migrating the EAS in different EDNs.
[0020] In a 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 ASP, or a chip or circuit applied to ASP, etc., including: determining demand information for reserved resources, the demand information for reserved resources at least includes location information of the reserved resources; sending the demand information for reserved resources to an 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.
[0021] In one design, the demand information for reserved resources also includes at least one of the following: the quantity of reserved resources, performance parameters of reserved resources, or expiration time of reserved resources.
[0022] 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.
[0023] 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.
[0024] 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 resources, migrating the EAS within different reserved resources in the same EDN, or migrating the EAS in different EDNs.
[0025] In a third aspect, an edge application method is provided. The third aspect is a system corresponding to the first aspect. The beneficial effects can be found in the description of the first aspect, including: an edge computing service provider ECSP management system receives demand information of reserved resources from an application service provider ASP, and sends a first request to a management and orchestration system MANO according to the demand information of reserved resources; wherein the demand information of reserved resources includes location information of reserved resources, the first request is used to request MANO to reserve resources in an edge data network 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. MANO receives the first request from the ECSP management system.
[0026] In one design, the further configuration includes: the MANO reserving resources in the EDN corresponding to the location information based on the first request.
[0027] In one design, the ASP also sends resource reservation requirement information to the ECSP management system.
[0028] In one design, the demand information for reserved resources also includes at least one of the following: the quantity of reserved resources, performance parameters of reserved resources, or expiration time of reserved resources.
[0029] In one design, the ECSP management system further includes determining usage status information of the reserved resources when the reserved resources are successfully reserved, where 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 usage rate of the reserved resources.
[0030] 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 in an occupied state.
[0031] In one design, after the ECSP management system sends a first request to the MANO according to the demand information of the reserved resources, the further includes: the ECSP management system sends a second request to the operator management system, 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 the connection information of the reserved resources; the operator management system establishes the network connection between the UPF and the reserved resources according to the second request.
[0032] In one design, it also includes: the operator management system sends a second response to the ECSP management system, the second response including the connection information of the UPF; 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 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.
[0033] In one design, before the ECSP management system sends the first request to the MANO based on the demand information for reserved resources, the further step 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; and 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.
[0034] In one design, the method further includes: the ECSP management system receiving a fifth request from the ASP, the fifth request being used to request deployment of the EAS in the reserved resources, and the fifth request including an identifier of the reserved resources.
[0035] In one design, the process also includes: the ASP sending a fifth request to the ECSP management system.
[0036] 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.
[0037] 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 resources, migrating the EAS within different reserved resources in the same EDN, or migrating the EAS in different EDNs.
[0038] 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 executing any one of the first to third aspects above. The communication device can be implemented by hardware, software, or by executing corresponding software implementation by hardware.
[0039] In one design, the communication device includes a unit that performs any one of the first to third aspects above.
[0040] In one design, the communication device includes a processor and a memory, and the processor is used to execute a computer program or instruction stored in the memory, so that the communication device implements any one of the methods of the first to third aspects above.
[0041] 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 execution code instructions.
[0042] In a fifth aspect, a computer-readable storage medium is provided, storing 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.
[0043] In a sixth aspect, a computer program product is provided, comprising a computer program or instructions, wherein when the computer program or instructions are executed by a computer, the method of any one of the first to third aspects described above is executed.
[0044] In a seventh aspect, a chip is provided, comprising a processor, wherein the processor 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 the first to third aspects above.
[0045] In an eighth aspect, a communication system is provided, comprising: a first communication device and a MANO, wherein the first communication device is used 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 used to implement the method of the second aspect. BRIEF DESCRIPTION OF THE DRAWINGS
[0046] Figure 1 A schematic diagram of a communication system provided in an embodiment of the present application;
[0047] Figure 2 A schematic diagram of deploying EAS in EDN provided in an embodiment of the present application;
[0048] Figure 3 A flowchart of reserving resources provided in an embodiment of the present application;
[0049] Figure 4 Another flowchart of reserving resources provided in an embodiment of the present application;
[0050] Figure 5 Another flow chart of reserving resources provided in an embodiment of the present application;
[0051] Figure 6 A flow chart for deploying EAS in reserved resources provided in an embodiment of the present application;
[0052] Figure 7 A flow chart of deploying EAS in reserved resources and migrating EAS provided in an embodiment of the present application;
[0053] Figure 8 A flowchart for deleting reserved resources provided in an embodiment of the present application;
[0054] Fig. 9 A schematic diagram of a structure of a device provided in an embodiment of the present application;
[0055] Fig.10 Another schematic diagram of the structure of the device provided in an embodiment of the present application.
[0056] Specific example method
[0057] Figure 1 The communication system provided by the embodiment of the present application is shown. Figure 1 As shown, including:
[0058] The 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) to deploy edge application servers (EASs). In other words, ASPs can deploy EASs in EDNs. Figure 1 , is illustrated by taking two EDNs as an example, and is not intended to limit the embodiments of the present application. Figure 1 The communication system shown may also include other numbers of EDNs.
[0059] The edge computing service provider (ECSP) management system 102 is responsible for the management of the edge computing network. For example, the creation, deletion and performance monitoring of EAS. For example, the ASP can apply to the ECSP management system for the deployment of EAS, and the ECSP management system can select an EDN that meets the conditions to deploy EAS according to the deployment requirements, such as resource size and location.
[0060] In the embodiments of the present application, the device for implementing the function of the ECSP management system may be an ECSP management system; or it may be a device that can support the ECSP management system to implement the function, 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 the ECSP management system or may be used in conjunction with the ECSP 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 technical solution provided in the embodiments of the present application is described below by taking the ECSP management system as an example in which the device for implementing the function of the ECSP management system is an ECSP management system.
[0061] The management and orchestration system (MANO) 103 is responsible for the management of virtualized network functions (VNF). For example, based on cloud computing technology, EAS can be deployed in the EDN in the form of VNF. Network function virtualization (NFV) uses general 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, by utilizing the characteristics of cloud computing, resources can be fully and flexibly shared, and new services can be rapidly developed and deployed. Automatic deployment, elastic scaling, fault isolation and self-healing can be performed based on actual business needs.
[0062] In the embodiment of the present application, the device for implementing the function of MANO may be MANO; or it may be a device that can support MANO to implement the function, 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 MANO or may be used in combination with MANO. The chip system may be composed of a chip, or may include a chip or other discrete devices. For the convenience of description, the technical solution provided in the embodiment of the present application is described below by taking MANO as an example of the device for implementing the function of MANO.
[0063] ASP 104 is an application service provider, which applies to deploy EAS in EDN through ECSP management system and MANO. For example, the application service provider can determine EAS, send a request to deploy EAS to ECSP management system, and MANO deploys EAS in the corresponding EDN.
[0064] In the embodiment of the present application, the device for implementing the function of ASP may be ASP; or it may be a device that can support ASP to implement the function, 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 ASP or may be used in combination with ASP. The chip system may be composed of chips, or may include chips or other discrete devices. For the convenience of description, the technical solution provided in the embodiment of the present application is described below by taking ASP as an example in which the device for implementing the function of ASP is ASP.
[0065] In the embodiment of the present application, when the EAS is deployed, when the user is near the EDN, such as near EDN1, the EAS application deployed in EDN1 can be accessed by the nearest access method, such as a game server or a geographic location application server. For example, the user uses the terminal 107 to connect to the nearest user plane function network element (UPF) 105 that meets the conditions through the access network device 106, and accesses the EAS that needs to be accessed through the UPF 105.
[0066] Optional, in Figure 1 The network architecture shown may also include: UPF 105, access network equipment 106 and terminal 107. Among them, UPF 105 is a network element in the core network responsible for data plane functions. For example, UPF is mainly responsible for forwarding and receiving user data. For example, in downlink transmission, UPF can receive user data from the data network (DN) and transmit it to the terminal through the access network equipment; in uplink transmission, UPF network element can receive user data from the terminal through the access network equipment and forward the user data to the DN. It can be understood that in Figure 1 The network architecture shown may include, in addition to UPF105, other devices in the core network, such as 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), etc.
[0067] It is understood that in the description of the present application, "at least one" means one or more, and "more" 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.
[0068] 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, etc.; or may be a module or unit that completes part of the 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 or an indoor station, a relay node or a donor node, etc. This application does not limit the specific technology and specific device form used by the access network device.
[0069] The terminal 107 may be referred to as a terminal device, user equipment (UE), mobile station, mobile terminal, etc. The terminal may be widely used for communication in various scenarios, including 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 wear, smart transportation, or smart city, etc. The terminal may 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.
[0070] 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 aircraft, 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 examples are not given one by one.
[0071] further, Figure 1 The communication system shown in the figure may also include: an operator management system, Figure 1 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 UPF. For example, the operator management system includes a management system (MS) in a public land mobile network (PLMN), and the MS in the PLMN interacts with the ECSP management system to implement operations such as establishing or deleting a connection between reserved resources and UPF.
[0072] In the embodiments of the present application, the device for implementing the function of the operator management system may be one or more network elements in the operator management system; or it may be a device that can support the operator management system to implement the function, such as a chip system, a hardware circuit, a software module, or a hardware circuit plus a software module, etc. The device can be installed in one or more network elements in the operator management system or can be used in conjunction with the operator management system. The chip system can be composed of a chip, or it can include a chip or other discrete devices. For ease of description, the following takes the case where the device for implementing the function of the operator management system is an operator management system as an example to describe the technical solution provided in the embodiments of the present application.
[0073] Above Figure 1 The communication system shown may support various radio access technologies (RATs), such as Figure 1 The communication system shown may 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 scenario described in the embodiment of the present application are intended to more clearly illustrate the technical solution of the embodiment of the present application, and do not constitute a limitation on the technical solution provided in the embodiment 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 solution provided in the embodiment of the present application is also applicable to similar technical problems.
[0074] EDN is a small data center deployed by the ECSP management system at the edge, close to the user area, and generally has limited resources. The ECSP management system may need to serve multiple ASPs at the same time, such as Internet application manufacturers and game application manufacturers. According to the current EAS deployment process, the ECSP management system and MANO select an EDN that meets the conditions to deploy EAS according to the needs of the ASP. For example, according to the ASP's requirements for the deployment location, select the EDN corresponding to the location. Usually, in a certain area, an ECSP management system only manages one EDN. If the EDN has enough remaining resources at this time and meets the resource requirements of EAS deployment, the EAS deployment can be completed. However, if the EDN is too busy and there are not enough remaining resources to meet the requirements of EAS deployment, the deployment of EAS may fail, or the ECSP management system and MANO select other EDNs farther away to deploy EAS.
[0075] For example, Figure 2As shown in the figure, the application of EAS1 is mainly for users near EDN1. Since the remaining resources of EDN1 cannot meet the requirements of deploying EAS1, the ECSP management system and MANO deploy EAS1 in EDN2. Each EDN has a service area. When users in its service area access applications in EDN through terminals, access network devices and UPF, EDN can provide the best service and users can enjoy the best service experience, such as low latency and large bandwidth. If the edge application EAS1 can only be deployed in EDN2 because EDN1 does not have enough resources, users in the service area of EDN1 cannot access EAS1 nearby if they want to access EAS1. For example, users can only access UPF2 in the service area of EDN2 through UPF1, and then access EAS1 in EDN2 through UPF2. The service experience for users in the service area of EDN1 is poor, such as high latency. In an EAS deployment, a "first come, first served" mechanism is adopted, and the ASP that sends the request first has a greater chance of being deployed in the desired deployment area, even for more important ASPs.
[0076] In view of this, the present application provides an edge application method and device, the method comprising: 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 needs of the ASP to deploy the EAS application, thereby solving the problem 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 far away from the user's location.
[0077] It is understandable that in the embodiments of the present application, the ASP, ECSP management system, MANO, or operator management system cooperate with each other to implement the solutions in the embodiments of the present application. The functions implemented by the ASP can be implemented by the ASP, or by a chip or circuit applied to the ASP. In the following description, the ASP implementation is taken 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 a chip applied to each. In the following description, the corresponding functions implemented by the ECSP management system, MANO, or operator management system are taken as an example.
[0078] [Example 1]
[0079] Figure 3 A process is provided that can be used to reserve resources, including:
[0080] Step 301: The ECSP management system receives reserved resource demand information from the ASP.
[0081] The demand information of the 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 of the 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 exceeds the effective time, the reserved resources become invalid and are no longer reserved for the ASP to deploy EAS.
[0082] Taking the reserved resource as a virtual machine (VM) as an example, the demand information of the reserved resource includes at least one of the following:
[0083] The number of virtual machines: for example, 10.
[0084] The performance parameters of the virtual machine: CPU: for example, it can be 1800 megahertz (MHz); storage capacity: for example, it can be 2024 megahertz (M); network bandwidth: for example, it can be 100M.
[0085] Expiration time: For example, it can be 20230501. It means that the reserved resources are valid before May 1, 2023. That is, after May 1, 2023, the reserved resources become invalid and are no longer reserved for ASP to deploy EAS. The reserved resources can be used for other purposes. For example, they can be allocated to other ASP to deploy EAS. The expiration time can also be called reservation expiration.
[0086] Or location information: for example, it can be a certain district in Nanjing. Its meaning is: resources can be reserved in an EDN in a certain district in Nanjing, etc. Location information can also be called location requirement.
[0087] Through the above design, the demand information of reserved resources may include the number of reserved resources, 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 reserved resources, the storage capacity of reserved resources, or the network bandwidth of reserved resources. According to at least one of the number of reserved resources or the performance parameters of reserved resources, resources that meet the number and performance parameters can be selected in the EDN at the corresponding position as reserved resources. Furthermore, the demand information of reserved resources also includes the expiration time of reserved resources. The expiration time of reserved resources can also be called the effective time of reserved resources. When the expiration time is reached or exceeds the effective time, the reserved resources become invalid and are no longer reserved for 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 reserved resources.
[0088] In one design, the demand information for the reserved resources may be carried in an object, and the object includes the demand information for the reserved resources. For example, the object may be called a reservation job object. For example, an implementation of step 301 includes: the ECSP management system receives a reservation job object from an ASP, and the reservation job object includes the demand information for the reserved resources. Further, an implementation of step 201 includes: the ECSP management system receives a request from an ASP to create a reservation object instance, and the request includes the reservation job object, and the reservation job object includes the demand information for the reserved resources, etc.
[0089] Step 302: The ECSP management system sends a first request to the MANO according to the demand information for reserved resources. 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.
[0090] In one implementation, the MANO includes a network function virtualization orchestrator (NFV MANO, NFVO), which can communicate with a virtualized infrastructure manager (VIM) in the MANO to perform at least one of resource allocation or resource reservation. In step 302, the ECSP management system can specifically send a first request to the NFVO. The NFVO can reserve resources in the EDN corresponding to the location information according to the first request.
[0091] In the following description, the specific implementation of step 302 will be explained in the following two cases.
[0092] Case 1: The operator management system is responsible for reserving resources and network connection with the UPF.
[0093] After sending the first request to MANO, the ECSP management system may receive a first response from MANO, wherein the first response includes connection information of 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 sends a second request to the operator management system, wherein 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.
[0094] 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 connected, 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.
[0095] For the above situation 1, if Figure 4 As shown, a process is provided, including:
[0096] 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.
[0097] Step 402: The ECSP management system sends a first request to the MANO according to the requirement information for reserving resources. The first request is used to request the MANO to reserve resources in the EDN corresponding to the location information.
[0098] For example, MANO can reserve resources according to virtualized network functions (VNF) based on cloud computing technology. The network service virtualized by network functions virtualization (NFV) can be called a network service (NS). A NS can include at least one VNF. When a NS is deployed in a virtualized manner, the service requester (e.g., ECSP management system) needs to provide the service provider (e.g., MANO) with description information of the service, which can be called a network service description (NSD) or NS deployment template. The description information mainly describes the topology of the service and the description information of each VNF. Among them, 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.
[0099] In one design, the ECSP management system determines the NSD based on the demand information of the reserved resources. Each VM in the demand information of the reserved resources is implemented by one or more VNFs. In the following description, each VM in the demand information of the reserved resources is implemented by one VNF as an example. The NSD may include a topology structure and description information of each VNF. For example, the topology structure includes the number of VNFs and the network connections of all VNFs. Taking the example that the demand information of the reserved resources includes 10 VMs, the topology structure of the NSD may include: 10 VNFs and the network connections of the 10 VNFs. In one implementation, the 10 VNFs may be implemented in one network, and the one network may be called a VL or VPC. The one network may be an internal virtual local area network, etc. In the virtual local area network, the 10 VNFs may communicate with each other, and the virtual local area network may be isolated from other networks. The description information of each VNF includes performance parameters of each VNF, and the performance parameters include at least one of the following: CPU, storage space, or network bandwidth requirements of the VNF. The ECSP management system can send a request to MANO to instantiate NS. 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 NSD may include location information in addition to the topology structure and description information of each VNF mentioned above. 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.
[0100] 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.
[0101] The first response may be a NS instance creation response. When the NS instance is successfully created, the ECSP management system may query the MANO for the created NS instance information, and the MANO returns the NS instance information to the ECSP management system according to the query request, including the connection information of the reserved resources. The connection information of the reserved resources may be the access address information of the NS, such as the service access point (SAP) of the NS, and the SAP may be the egress gateway information of the VPC, etc.
[0102] 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.
[0103] For example, the second request is a request to create an edge computing management connection information (EcmconnectionInfo) object instance, and 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 can be a response to the successful creation of the EcmconnectionInfo object instance.
[0104] 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.
[0105] 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 then 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.
[0106] Step 406: The operator management system sends a second response to the ECSP management system, where the second response includes the connection information of the UPF.
[0107] Step 407: The ECSP management system sends a third request to MANO. The third request is used to request MANO to update the connection information between the reserved resources and the UPF. The third request includes the connection information of the UPF.
[0108] Since in the previous operation, MANO only deployed NS in EDN and did not configure specific routes in external connection information (such as SAP), or it can be understood that the routes in NS external connection information are empty. Therefore, when the ECSP management system obtains the connection information of UPF, it can send a third request to MANO, and the third request includes the connection information of UPF. The third request can be an update request, and MANO can update the routes in NS external connection information from empty to UPF connection information, or the third request can be a configuration request, and MANO can configure the connection information of UPF in the routes in NS external connection information, etc.
[0109] Optionally, after step 407, the process may further include: 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 updated successfully.
[0110] 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.
[0111] For example, the reserved work object instance created by the ECSP management system includes: at least one of: an identifier of the reserved work object, an address of the reserved resource corresponding to the reserved work object, or usage status information of the reserved resource, etc. Optionally, when the reserved resource is successfully reserved, the ECSP management system determines the usage status information of the reserved resource. For example, in situation 1, after the ECSP management system sends a third request to request an NS update and receives a third response indicating successful update of the NS, it deems that the resource is successfully reserved. The usage status of the reserved resource includes at least one of the following: an identifier of the reserved resource, the usage status of the reserved resource, an identifier of the EAS deployed in the reserved resource, or a utilization rate of the reserved resource. Optionally, the identifier of the reserved resource includes: an identifier of the VNF and an 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:
[0112] Table 1
[0113]
[0114] In Table 1, the reserved resources are implemented in NS-1, and 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, etc. The identifier of the NS 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 respectively. The identifier of each VNF can be the identifier of the VNF, or the instance identifier of the VNF. The identifier of the VNF and the instance identifier of the VNF can be the same or different. It can be understood that Table 1 describes the usage status of the reserved resources determined by the ECSP management system when the reserved resources are successfully reserved. At this time, each reserved resource has not been occupied, so the usage status of each reserved resource is idle, the usage rate of each reserved resource is 0, and the identifier of the EAS deployed in each reserved resource is empty, etc. It can be understood that the usage status of the reserved resource is idle, which means that the VNF corresponding to the reserved resource is successfully created, but no EAS application software is deployed or run in the VNF. When the EAS application software is deployed or run on a VNF, the VNF is considered to be 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 usage rate of the VPC. In the example of Table 1, the VPC corresponding to VPC-1 includes 10 VNFs, and the 10 VNFs form a VPC, and the identifier of the VPC is VPC-1. It can be understood that if any VNF in a VPC is occupied, the VPC is considered to be occupied.
[0115] Through the above design, at least one of the following information can be determined based on the usage status information of the reserved resources: which reserved resources are occupied, which reserved resources are idle, the utilization rate of the occupied reserved resources, or the deployment of EAS in the occupied reserved resources. Afterwards, it can facilitate the deployment of EAS, such as giving priority to deploying EAS in idle reserved resources, or giving priority to deploying ESA in reserved resources with low occupancy rates. Alternatively, when deleting reserved resources, it is also possible to determine which reserved resources can be deleted based on the usage information of the reserved resources, thereby avoiding deleting the reserved resources for deploying EAS. When deleting reserved resources, it does not affect the reserved resources to provide services for the already deployed EAS.
[0116] Case 2: MANO is responsible for reserving resources and connecting to the UPF network.
[0117] The ECSP management system sends a fourth request to the operator management system, where the fourth request is used to request the 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 demand information of the reserved resources, where the first request is used not only to reserve resources in the EDN corresponding to the location information, but also to request the network connection between the UPF and the reserved resources, and the first request includes the connection information of the UPF, etc.
[0118] For the above situation 2, if Figure 5 As shown, a process is provided, including:
[0119] 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.
[0120] 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.
[0121] For example, the fourth request may include the location information of the reserved resources. The operator management system selects a UPF that meets the conditions according to the location information of the reserved resources. For example, in an area, there may be multiple UPFs, some of which are busy, and some of which are idle. The idle UPF is a UPF that meets the conditions, etc. Alternatively, in an area, there is a UPF, and the UPF can be uniquely determined according to the location information of the reserved resources, then the UPF is a UPF that meets the conditions, etc. Further, the fourth request also includes: network demand information, such as bandwidth demand. The network demand information can be determined according to the bandwidth information in the reserved resource demand information. For example, in the above example, the bandwidth demand in the performance parameters of each VM in the demand information of the reserved resources is 100M, then the network demand information in the fourth request can be 100M. Alternatively, the number of VMs in the reserved resources is 10, and the bandwidth demand of the 10 VMs is 1000M, then the network demand information in the fourth request can be 1000M, etc. The operator management system can determine a UPF that meets the conditions according to the network demand information. For example, one or more UPFs can be determined according to the location information of the reserved resources. According to the network demand information, a UPF that meets the conditions can be determined. For example, among the one or more UPFs that meet the location information, a UPF whose bandwidth is greater than or equal to the UPF in the network demand information can be selected, and the UPF can be used as a UPF that meets the conditions. For example, among the one or more UPFs that meet the location information, a UPF whose bandwidth is greater than or equal to 100M (or 1000M) can be selected as a UPF that meets the conditions.
[0122] 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.
[0123] Optionally, step 504: the ECSP management system determines the NSD based on the connection information of the UPF and the demand information of the reserved resources. The NSD includes the topology structure and the description information of each VNF. For the description information of the topology structure and each VNF, please refer to the description in Case 1. In addition, the NSD may also include the network demand information of the connection between the reserved resources and the UPF, for example: the network demand information (for example, bandwidth, etc.) of 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.
[0124] Step 505: The ECSP management system sends a first request to MANO, where the first request is a request for instantiating NSD.
[0125] MANO instantiates NS according to NSD. The process of instantiating NS includes: reserving resources in the EDN corresponding to the location information, and establishing a network connection between the reserved resources and UPF. In one design, in the process of instantiating NS, MANO includes: creating a VL or VPC, which includes the VNF that needs to be reserved. Further, according to the network demand information in the NSD, the network of the VL or VPC is configured, for example, the network bandwidth of the VL or VPC is configured. A network connection between the VL or VPC and UPF is established, and the address information of the UPF is configured in the route of the VL or VPC, and the route of the VL or VPC is configured in the route of the UPF. It should be noted that the reserved resources correspond to at least one NS, and the NS corresponds to one VL or VPC. Therefore, the network connection between the reserved resources 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 resources can be described as the address information of the NS, the address information of the VL or VPC, etc.
[0126] Step 506: MANO sends a first response to the ECSP management system, where the first response is used to indicate that resource reservation is successful.
[0127] For example, the first response may be a response of an instantiated NS, etc.
[0128] 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.
[0129] For the description of the reserved work object instance, refer to the description in case 1. The difference is that the reserved work object includes the usage status of the reserved resources. The ECSP management system can determine the usage status of the reserved resources when the reservation of the reserved resources is successful. In case 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.
[0130] In case 1 or 2, the ASP can query the ECSP management system for the usage status of the reserved resources according to the identifier of the reserved work object instance. Afterwards, the ASP can deploy EAS, etc. according to the usage status of the reserved resources. For example, the ASP can deploy EAS in the VNF in the idle state of the reserved resources, or can deploy EAS in the VNF whose usage rate is lower than the threshold, etc.
[0131] Through the above design, before deploying EAS applications, ASP reserves some resources in EDN through ECSP management system and MANO. The reserved resources are called reserved resources. Afterwards, when ASP requests EAS deployment from ECSP management system, as long as the resource quota is within the reserved resources, ECSP management system will meet the ASP's demand for deploying EAS applications, reduce the probability of EAS deployment failure, and reduce the delay of users accessing EAS applications.
[0132] [Example 2]
[0133] In the second embodiment, the EAS is deployed in the reserved resources in the first embodiment. For example, the ECSP management system receives a fifth request from the ASP, the fifth request is used to request the deployment of the EAS in the reserved resources, and the fifth request includes an identifier of the reserved resources. Through the above design, after the resources are successfully reserved, the ASP can deploy the EAS in the reserved resources, thereby solving the problem that when the EAS is deployed, due to the "first come, first served" mechanism and the limited resources of the EAS at the corresponding location, the EAS is deployed in the EDN far away from the user's location, resulting in a high latency for users to access the EAS.
[0134] like Figure 6 As shown, a process is provided, which can be used to deploy EAS, for example, Figure 6 The process may be used to deploy EAS etc. in the reserved resources in the first embodiment, including:
[0135] Step 601: The reservation of the reserved resources is successful.
[0136] For example, one implementation of the successful reservation of 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.
[0137] Step 602: The ECSP management system receives a fifth request from the ASP, where the fifth request includes an identifier of reserved resources.
[0138] 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 EAS of the ASP 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 decides 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 one or more VNFs in which the EAS is deployed, etc. Alternatively, the ECSP management system determines 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. 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 one or more VNFs in which the EAS is deployed.
[0139] 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.
[0140] For example, when MANO receives the sixth request, it can 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 can also be called 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 address information of the application file, etc.). MANO can download the application file at the corresponding location according to the address information of the application file. Further, the ECSP management system can obtain EAS application file information through the ASP. For example, the fifth request also includes EAS application file information, etc. One or more VNFs that meet the conditions, that is, one or more VNFs that deploy EAS, can be determined by MANO itself, or determined by ECSP and indicated to MANO, for example, the sixth request includes the identifier of one or more VNFs, or determined by ASP, indicating ECSP, and ECSP then indicates to MANO, etc. For example, both the fifth request and the sixth request include the identifier of one or more VNFs.
[0141] In one implementation, the ECSP management system can determine the NS corresponding to the reserved resources and obtain the usage status of the reserved resources according to the identifier of the reserved work object instance sent by the ASP. In the usage status of the reserved resources, select a VNF that meets the conditions. 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. Further, it also includes: the identifier of the NS corresponding to the VNF that meets the conditions.
[0142] In one implementation, a specific implementation of step 602 and step 603 is: 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 for creating an EAS requirement object instance, and the fifth request includes the identifier of the EAS requirement object and the reserved work object instance. Among them, 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 function object, the ECSP management system selects a VNF that meets the conditions in the reserved resources according to the usage status of the reserved resources, and sends a sixth request to MANO to deploy EAS in the VNF that meets the conditions. For example, the sixth request may be an update request, which is used to request to load EAS application files in the VNF that meets the conditions.
[0143] Step 604: MANO sends a sixth response to the ECSP management system, where the sixth response is used to indicate that the EAS is successfully deployed in the reserved resources.
[0144] As described above, the sixth request may be an update request, and the sixth request is used to request 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.
[0145] Step 605: The ECSP management system updates the usage status of the reserved resources.
[0146] 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%.
[0147] Table 2
[0148]
[0149] Optionally, after step 605, the method further includes: the ECSP management system sends an update indication of the reserved work object instance to the ASP, and when the ASP receives the indication information, it 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.
[0150] 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.
[0151] In the embodiment of the present application, after the EAS is successfully deployed, the EAS may be migrated. For example, due to maintenance or upgrades in the EDN, some servers running the EAS may need to be shut down, and the EAS needs to be migrated to other servers. Alternatively, due to insufficient resources in the EDN, the EAS may also need to be migrated to other servers. For the ASP, the migration strategy can be configured when the EAS is deployed. For example, the fifth request may also include the migration strategy information of the EAS, so as to ensure that the services provided by the EAS are not affected, or the impact is minimal.
[0152] like Figure 7 As shown, a process is provided, and Figure 6 The main difference in the process is that when deploying EAS, you can configure the EAS migration policy, and then migrate the deployed EAS according to the configured migration policy, including:
[0153] Step 701: The reservation of the reserved resources is successful.
[0154] In one design, a successful reservation of the reserved resources is achieved by completing instantiation of the reserved work object.
[0155] 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 the migration policy information.
[0156] Exemplarily, the migration policy information includes at least one of the following: migration conditions, migration scope, etc. Optionally, the migration conditions include: allowing migration, not allowing migration, or whether to inquire 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 in different EDNs, etc.
[0157] In one design, the ASP may generate an EAS requirement object, which includes a migration strategy, which may be referred to as a movement and notification parameter, and the value of the parameter may be any of the following:
[0158] 1. Migration allowed: movement allowed.
[0159] The scope of migration is: allowing EAS migration within the same reserved resource, or allowing EAS migration in different reserved resources within the same EDN, or allowing EAS migration in different EDNs, etc.
[0160] 2. Allow migration, but you need to ask ASP before migration: movement allowed with notification.
[0161] The scope of migration is the same as that when migration is allowed and will not be repeated here.
[0162] 3. No migration allowed: no movement.
[0163] For example, when the conditions are met, the successfully deployed EAS is not allowed to migrate. For example, the condition can be: if the migration is across EDNs, the successfully deployed EAS is not allowed to migrate. Or no condition is defined, that is, after the EAS is successfully deployed, the ECSP management system is not recommended to migrate it to other servers.
[0164] Step 703: The ECSP management system sends a sixth request to the MANO according to the identification information of the reserved resources, where the sixth request is used to request the MANO to deploy the EAS in the reserved resources.
[0165] For example, the ECSP management system can determine the EAS function object based on the EAS requirement object. Each EAS that needs to be deployed in the EAS requirement object corresponds to an EAS function object. For each EAS function object, the ECSP management system can select a VNF that meets the conditions in the reserved resources and request MANO to instantiate the VNF. Instantiating the VNF includes: deploying EAS in the VNF that meets the conditions, etc.
[0166] Step 704: MANO sends a sixth response to the ECSP management system, where the sixth response includes an instantiation success response.
[0167] Step 705: Update the usage status of the reserved resources.
[0168] 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.
[0169] 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 is described as one EAS function object instance corresponds 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 EAS, the identifier of the NS to which the VNF belongs, and the address information of each EAS, etc.
[0170] Step 707: When the ECSP management system needs to trigger the EAS to migrate, it obtains migration policy information according to the EAS requirement object instance associated with the EAS and takes corresponding actions.
[0171] For example, when the ECSP management system finds that the deployed EAS needs to be migrated due to upgrade, resource shortage or other reasons in the EDN, it obtains the migration strategy information according to the EAS requirement object instance associated with the EAS.
[0172] 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,
[0173] If the migration policy information is: migration is allowed, but EAS needs to be notified and queried before migration; the scope of migration is: migration across different EDNs. The ECSP management system can send an inquiry message to the ASP, which is used to inquire whether the ASP agrees to the migration of EAS. If the ASP agrees to the migration of EAS, it is executed: the ECSP management system requests MANO to migrate EAS in different EDNs. In one implementation, in step 706, when creating an EAS function object instance, the EAS function object instance includes a migration behavior (movement action) parameter, and the initial value of the parameter is no migration (no movement). When the migration policy information is to allow migration, but EAS needs to be queried before migration, the ECSP management system updates the migration behavior parameter in the EAS function object instance associated with the EAS to be migrated to a migration requirement (movement required), and sends the updated EAS function object instance information to the ASP. The ASP judges the operating status of the EAS associated with the EAS function object instance to determine whether the EAS migration is allowed. For example, when the operating status of the associated EAS is that the EAS is currently providing services to users, the ASP can determine that the EAS migration is not allowed; otherwise, it is determined that the EAS migration is allowed, etc. Further, if the ASP allows EAS migration, the ASP updates the migration behavior parameter in the EAS function object instance to allow migration (movement allowed), and the ECSP management system requests MANO to perform 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 not allow migration (movement not allowed), and the ECSP management system performs a temporary non-migration operation.
[0174] Through the above design, ASP configures the migration strategy when deploying EAS. When EDN needs to migrate EAS to other servers due to maintenance or upgrade, it can migrate EAS according to the migration strategy of EAS to ensure that the services provided by EAS are not affected or reduce the impact.
[0175] [Example 3]
[0176] like Figure 8 As shown, the embodiment of the present application further provides a process, which can be used to delete reserved resources. For example, the process can be used to delete the reserved resources in embodiment 1, including:
[0177] 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.
[0178] In case 1, the ASP inquires the ECSP management system about the usage of the reserved resources according to the identifier of the reserved object instance, and deletes or migrates all EAS deployed on the reserved resources according to the demand. When all the reserved resources are idle, the ASP sends a request to delete the reserved work object instance to the ECSP management system.
[0179] In case 2, the ASP directly sends a request to delete the reserved work object instance to the ECSP management system, and the request may carry an instruction to deploy the EAS in the reserved resources.
[0180] Optionally, step 802: the ECSP management system determines usage of reserved resources corresponding to the reserved work object instance.
[0181] Step 803: The ECSP management system sends a NS update request to the MANO, where the NS update request is used to delete the reserved resources.
[0182] For case 1, the reserved resources are all in an idle state at this time, and the ECSP management system can directly delete the reserved work object instance. For case 2, the ECSP management system requests MANO to delete the unoccupied VNFs in the reserved resources and retain the occupied VNFs in the reserved resources. The occupied VNFs are the VNFs where EAS is deployed. 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 to VNF10 can be deleted. Furthermore, only the network resources of the VL or VPC used by VNF1 are retained, and the network resources of other VNFs are deleted. For example, a VL or VPC network reserves 100M bandwidth, but EAS1 deployed in VNF1 only uses 10% of the network bandwidth. In this case, only 10M bandwidth can be retained, and the remaining 90M bandwidth can be released.
[0183] Step 804: MANO sends a NS update success response to the ECSP management system.
[0184] Optionally, if all reserved resources associated with the reserved work object instance are deleted, the following may also be included:
[0185] Step 805: If the connection between NS and UPF is established by the operator management system, the ECSP management system requests the operator management system to delete the connection between NS and UPF, for example, by deleting the EcmConnectionInfo object instance.
[0186] 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.
[0187] Step 806: The operator management system sends a successful deletion response of the connection between NS and UPF to the ECSP management system, for example, a successful deletion response of the reserved work object instance. Or,
[0188] 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.
[0189] 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 wasting the reserved resources.
[0190] It should be noted that in the embodiments of the present application:
[0191] 1. The differences between different embodiments are described emphatically, and the descriptions of different embodiments can refer to each other.
[0192] 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 internal logical relationships.
[0193] 3. The various numbers involved in the embodiments of the present application are only for the convenience of description and are not used to limit the scope of the embodiments of the present application. The size of the sequence number of the above-mentioned processes does not mean the order of execution. The execution order of each process should be determined by its function and internal logic.
[0194] 4. In Figures 3 to 8 In the process, there is no restriction on the order in which different steps are executed. For example, Figure 6 In the embodiment, step 605 may be performed before step 606, or after step 605, etc. Figures 3 to 8 Each process may include fewer steps or more steps than the flowchart or text description, without limitation.
[0195] In the embodiments provided by the present application, the methods provided by the embodiments of the present application are introduced from the perspective of the interaction of each device. In order to implement the functions in the methods provided by the embodiments of the present application, the ASP, ECSP management system, MANO, or operator management system, etc., may include hardware structures and / or software modules to implement the above functions in the form of hardware structures, software modules, or hardware structures plus software modules. Whether one of the above functions is executed in the form of hardware structures, software modules, or hardware structures plus software modules depends on the design constraints of the specific application of the technical solution.
[0196] Fig. 9 and Fig.10A schematic diagram of the structure of possible devices provided in the embodiments of the present application. These communication devices can implement one or more corresponding functions in the above method embodiments. For example, the functions implemented by the ECSP management system, or ASP, etc., may thus achieve the beneficial effects possessed by the above method embodiments.
[0197] like Fig. 9 As shown, the communication device 900 includes a processing unit 910 and a transceiver unit 920. Optionally, the 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.
[0198] Exemplarily, the processing unit may also be referred to as a processor, a processing board, a processing module, a processing device, etc. The communication unit may also be referred to as a transceiver, a transceiver, a transceiver module, a transceiver device, etc. Further, the communication unit may include at least one of a sending unit or a receiving unit. The sending unit and the receiving unit may be integrated together, or may be two independent units, etc.
[0199] In one design, communication apparatus 900 is used to implement Figures 3 to 8 The functions in the ECSP management system are specifically: a transceiver unit 920 is used to receive 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; a processing unit 910 is used to control the transceiver unit 920 to send a first request to the management and orchestration system MANO according to the demand information for reserved resources, wherein the first request is used to request the MANO to reserve resources in an edge data network EDN corresponding to the location information, wherein 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.
[0200] In another design, communication device 900 is used to implement Figures 3 to 8 The functions in the ASP are as follows: a processing unit 910 is used to determine the demand information of reserved resources, wherein the demand information of the reserved resources includes at least the location information of the reserved resources; a 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.
[0201] For more detailed description of the processing unit 910 and the transceiver unit 920, please refer to the above method embodiment. Figures 3 to 8 The description is not repeated here.
[0202] It is understandable that the division of units in the embodiments of the present application is schematic and is only a logical function division. There may be other division methods in actual implementation. In addition, each functional unit in the embodiments of the present application may be integrated into a physical device (for example, a processor), or each functional unit may be a separate physical device, or two or more units may be integrated into one unit for implementation. The above-mentioned integrated unit may be implemented in the form of hardware, or in the form of software functional modules, etc.
[0203] Fig.10 Another structural diagram of the communication device 1000 provided in an embodiment of the present application is shown. For example, Fig.10 The communication device 1000 shown may be Fig. 9 A hardware circuit implementation of the communication device 900 shown in FIG. Fig.10 Only the essential parts of the communication device are shown.
[0204] like Fig.10 As shown, 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.
[0205] For example, the processor 1010 may be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSP), application specific integrated circuits (ASIC), field programmable gate arrays (FPGA) or 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.
[0206] 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.
[0207] For example, the memory 1030 may 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.
[0208] When the communication device 1000 is used to implement Figures 3 to 8 When the method is shown, the processor 1010 is used to implement the function of the processing unit 910, and the interface circuit 1020 is used to implement the function of the transceiver unit 920.
[0209] 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 send signals from the processor 1010 to other communication devices outside the communication device. The processor 1010 uses a logic circuit or executes code instructions to implement the above Figures 3 to 8 Function in .
[0210] The 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 Figures 3 to 8 For example, the processor may execute the instructions in the memory so that the communication device implements one or more functions in the above method embodiments, such as Figure 3 or Figure 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 Figures 3 to 8 The processor and storage medium can also exist as discrete components in the ECSP management system or ASP in the Figures 3 to 8 ECSP management system or ASP in medium.
[0211] The present application also provides a computer-readable storage medium, which stores instructions, which may also be referred to as computer programs, computer program codes, etc. The instructions are executed on a computer, so that the computer executes the method in the above embodiment. Figures 3 to 8 Functions in, for example, Figures 3 to 8 The functions of the ECSP management system or ASP.
[0212] 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 instruction 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 instruction may be transmitted from one website, computer, server or data center to another website, computer, server or data center by wired or wireless means. 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; it may also be an optical medium, such as a digital video disc; it may also be a semiconductor medium, such as a solid-state hard disk. 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.
[0213] The present application also provides a computer program product, including a computer program or an instruction. When the computer program or the instruction is executed on a computer, the above Figures 3 to 8 The method in is executed. For example, Figures 3 to 8 The functions of the ECSP management system or ASP in the computer are executed. For example, the computer program product includes one or more computer programs or instructions. When the computer program or instruction is loaded and executed on the computer, all or part of the embodiments of the present application are executed. Figures 3 to 8 The process or function in.
[0214] It is understood that the method 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, it can be implemented in whole or in part in the form of a computer program product.
[0215] The present application also provides a chip, which includes a processor, the processor is coupled to a memory, and the processor is used to execute a computer program or instruction stored in the memory, so that the chip implements Figures 3 to 8 For example, to implement Figures 3 to 8 The ECSP management system or ASP functions in the ECSP management system, etc. Taking the chip realizing the functions of the ECSP management system as an example, the chip can receive information from other modules (such as radio frequency or antenna, etc.) in the ECSP management system, and the 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 radio frequency or antenna, etc.) in the ECSP management system, and the information is sent by the ECSP management system to the MANO, etc.
[0216] The 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 above Figures 3 to 8 The specific structure of the first communication device can be found in the above description, for example Fig. 9 or Fig.10 Optionally, it also includes: an operator management system. Further, it also includes: a second communication device. The second communication device can implement the above Figures 3 to 8 For the specific structure of the second communication device, please refer to the above description, for example Fig. 9 or Fig.10 Description, etc.
[0217] Obviously, those skilled in the art can 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 also 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 resources, 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 resources, 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 of the reserved resources includes the location information of the reserved resources, the first request is used to request the MANO to reserve resources in the edge data network EDN corresponding to the location information, the reserved resources are 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; 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 according to claim 20, 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.
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 resources, 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: include: Unit for performing the method according to any one of claims 11 to 15.
32. 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.
33. 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.
34. 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.
35. 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.
36. The system of claim 35, wherein: Also includes: Operator management system.
37. The system of claim 35 or 36, 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
Cited By
Edge application method and apparatus
EP4694322A1
