Deployment method and apparatus for applications

Abstract

The application provides a deployment method and device of an application, relates to the technical field of communication, and is used for solving the problem that the deployment process of an MEC application is relatively complicated. The method comprises the following steps: receiving a first application deployment request, the first application deployment request being used for indicating that a mobile edge computing (MEC) application is to be deployed in a target MEC system, and the first application deployment request comprising application type information, the application type information being used for indicating whether the MEC application is an application across operator networks. Based on the application type information, the MEC application is deployed in the target MEC system.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a method and apparatus for deploying an application. Background Technology

[0002] Mobile edge computing (MEC) can be deployed at the edge nodes of a communication network to provide computing power to terminals, thereby effectively reducing the latency of terminal services. MEC co-construction and sharing refers to multiple operators jointly building and sharing MEC equipment resources, thereby reducing the operation and maintenance costs of MEC construction.

[0003] Currently, application deployers can deploy MEC applications on the MEC networks of various operators. However, with the increasing prevalence of MEC deployments across more operators, the process of deploying MEC applications on various operators' MEC networks has become cumbersome and inefficient. Summary of the Invention

[0004] This application provides a method and apparatus for deploying applications, which solves the problem of the cumbersome process of deploying MEC applications.

[0005] To achieve the above objectives, this application adopts the following technical solution:

[0006] Firstly, this application provides a method for deploying an application. In this method, a first application deployment request is received, which instructs the deployment of a mobile edge computing (MEC) application on a target MEC system. The first application deployment request includes application type information, which indicates whether the MEC application is a cross-carrier network application. Based on the application type information, the MEC application is deployed on the target MEC system.

[0007] Based on the above technical solution, a first application deployment request is received. This request instructs the deployment of a mobile edge computing (MEC) application on a target MEC system. The first application deployment request includes application type information, which indicates whether the MEC application is a cross-carrier network application. Based on the application type information, the MEC application is deployed on the target MEC system. This allows for the determination of whether an MEC application is a cross-carrier network application based on the application type information, thus enabling the deployment of the MEC application on the corresponding target MEC system. This eliminates the need for repeated deployments of the same application, improving deployment efficiency. Furthermore, deploying the MEC application on the target MEC system with a single request provides users with stable MEC services.

[0008] In one possible design, the first application deployment request specifically instructs the deployment of a first operator's MEC application in a first MEC system. The application type information is either a first type of information or a second type of information. The first type of information indicates that the MEC application is a cross-operator network application, while the second type of information indicates that the MEC application is a non-cross-operator network application. If the application type information is the first type of information, then the first operator's first MEC is deployed in the first operator's first MEC system, and the second operator's MEC application is deployed in the second operator's second MEC system. The target MEC system includes both the first and second MEC systems. If the application type information is the second type of information, then the first operator's first MEC is deployed in the first MEC system, and the target MEC system includes the first MEC system.

[0009] In one possible design, a second application deployment request is sent to the second MEC system, which instructs the second MEC application to be deployed on the second MEC system.

[0010] In one possible design, the first application deployment request may also include: carrier information, which indicates the carrier version of the MEC application.

[0011] In one possible design, the operator information includes: the identifier of the second operator. Based on the identifier of the second operator, a second application deployment request is sent to the second MEC system.

[0012] In one possible design, the first application deployment request specifically instructs the deployment of a first operator's MEC application in the first MEC system, with the first MEC system being the target MEC system. If the application type information is of type 1, then the MEC applications of both the first and second operators are deployed in the first MEC system; the type 1 information indicates that the MEC application is a cross-operator network application. If the application type information is of type 2, then the MEC application of the first operator is deployed in the first MEC system; the type 2 information indicates that the MEC application is a non-cross-operator network application.

[0013] Secondly, this application provides an application deployment apparatus, which includes a receiving module and a processing module.

[0014] A receiving module is used to receive a first application deployment request, which instructs that an MEC application be deployed on a target MEC system. The first application deployment request includes application type information, which indicates whether the MEC application is a cross-carrier network application. A processing module is used to deploy the MEC application on the target MEC system based on the application type information.

[0015] Thirdly, this application provides an application deployment apparatus, the apparatus comprising: a processor and a memory; the processor and the memory being coupled; the memory being used to store one or more programs, the one or more programs including computer-executable instructions, wherein when the application deployment apparatus is running, the processor executes the computer-executable instructions stored in the memory to implement the method as described in the first aspect and any possible implementation thereof.

[0016] Fourthly, this application provides a computer-readable storage medium storing instructions that, when executed on a computer, cause the computer to perform the methods described in the first aspect and any possible implementation thereof.

[0017] Fifthly, this application provides a chip including a processor and a communication interface, the communication interface being coupled to the processor, the processor being used to run computer programs or instructions to implement the methods described in the first aspect and any possible implementation thereof.

[0018] Sixthly, this application provides a computer program product containing instructions that, when executed by a computer, cause the computer to perform the methods described in the first aspect and any possible implementation thereof.

[0019] The technical problems that can be solved and the technical effects that can be achieved by the deployment device, computer equipment, computer storage medium, chip or computer program product used in the above solution can be found in the technical problems and technical effects solved in the first aspect above, and will not be repeated here. Attached Figure Description

[0020] Figure 1 A system architecture diagram of a communication system provided in this application embodiment;

[0021] Figure 2 A system architecture diagram of another communication system provided in this application embodiment;

[0022] Figure 3 A flowchart illustrating an application deployment method provided in an embodiment of this application;

[0023] Figure 4 A flowchart illustrating another application deployment method provided in this application embodiment;

[0024] Figure 5 A flowchart illustrating another application deployment method provided in this application embodiment;

[0025] Figure 6 A schematic diagram of the structure of an application deployment device provided in an embodiment of this application;

[0026] Figure 7 A schematic diagram of the structure of a deployment device for another application provided in this application embodiment;

[0027] Figure 8 A conceptual partial view of a computer program product provided for an embodiment of this application. Detailed Implementation

[0028] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0029] The terms “first” and “second” in the specification and claims of this application are used to distinguish different objects, rather than to describe a specific order of objects.

[0030] Furthermore, the terms "comprising" and "having," and any variations thereof, used in the description of this application are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or device that includes a series of steps or modules is not limited to the steps or modules listed, but may optionally include other steps or modules not listed, or may optionally include other steps or modules inherent to such process, method, product, or device.

[0031] Furthermore, in the embodiments of this application, the words "exemplary" or "for example" are used to indicate that they are examples, illustrations, or descriptions. Any embodiment or design that is described as "exemplary" or "for example" in this application should not be construed as being more preferred or advantageous than other embodiments or design options. Specifically, the use of the words "exemplary" or "for example" is intended to present concepts in a concrete manner.

[0032] The following explanations of the terms used in the embodiments of this application are provided to facilitate the reader's understanding.

[0033] 1. Co-construction and sharing: Co-construction and sharing refers to multiple operators jointly building network infrastructure and sharing network services. This approach can significantly reduce the operation and maintenance costs of network construction and improve the efficiency of network infrastructure. Currently, co-construction and sharing is mainly applied to the co-construction and sharing of communication networks. For example, the co-construction and sharing of 5G networks includes two methods: inter-network roaming and access network sharing. In the case of inter-network roaming, the basic network infrastructure is the same as in the normal construction scheme, and the terminal accesses the 5G network through the access network equipment and core network equipment of other operators. This application will not elaborate further on this method.

[0034] 2. Mobile edge computing, also known as multi-access edge computing, refers to a solution that reduces service latency by placing devices with computing capabilities at nodes in a communication network, allowing terminals to obtain the necessary service resources through MEC devices located at network nodes.

[0035] MEC includes MEC system level, MEC host level, and MEC networks level.

[0036] The MEC system level includes the operator support system (OSS) and the MEC orchestrator (MEO). The OSS is the management entity that supports the operation of the MEC system. User terminal applications (UE apps) or customer-facing service portals (CFS portals) send service requests to the OSS in the MEC through the Mx2 and Mx1 interfaces, respectively. The OSS checks the authorization, integrity, and other configuration information of the corresponding MEC application based on the service request and instructs the MEO to instantiate or terminate the MEC application.

[0037] MEO is responsible for accessing the business resources of each MEC host. MEO can trigger the instantiation or termination of MEC applications according to OSS instructions, and send the instantiation or termination information to OSS.

[0038] The MEC host is the device that specifically performs MEC business processing. The MEC host is responsible for creating MEC application instances and providing computing, storage, and network communication resources for the MEC application instances.

[0039] In the context of 5G network co-construction and sharing, the co-construction and sharing of information infrastructure not only includes network resources, but also needs to be expanded and deepened to include shared computing resources. For example, operators can jointly build a public general-purpose MEC platform, which can effectively utilize the 5G co-construction and sharing network on the one hand, and reduce the construction cost of MEC system on the other hand, avoiding redundant investment in MEC construction.

[0040] To support the co-construction and sharing of MEC (User Plane Function, UPF), not only does the MEC network need to be connected to the core networks of different operators simultaneously, but the MEC service system also needs to be shared among different operators. This ensures that MEC applications deployed in different operator networks can simultaneously meet the service needs of users from different operators. Therefore, from the perspective of system logical function division, the access of the MEC system to different operator networks can be divided into two parts: MEC network interface and MEC service interface.

[0041] In this context, MEC network integration can be achieved by extending the functionality of the UPF itself to support access to multiple operator core networks. This requires the UPF itself to support access to multiple operator core networks. In this case, the MEC can act as a local proxy for application functions (AF), directly distributing local data flow filtering rules to the shared UPF to handle data flow forwarding and filtering configuration for different operator UPFs. This not only maintains the interface between the MEC system and the UPF (the N4 and MP interfaces defined by ETSI and 3GPP) unchanged, but also allows the UPF proxy and data network controller to be implemented within the UPF.

[0042] In the MEC service interoperability section, a new Operator Support System (OSS) Federation network element is introduced into the MEC system-level control plane. This element is used to interconnect with the OSS of different operators and continues to use the N4, MP2, Mm1, and Mm2 interfaces already defined by ETSI and 3GPP to interact with the MEC orchestrator (MEO) and platform manager (MEPM) of the MEC system.

[0043] It should be noted that the MEC system supports a multi-tenant mode, which means allocating bare-metal isolated basic resources and business resources to different users. For example, in terms of resource isolation, the underlying cloud computing service model (Infrastructure asaService, IaaS) stack is used to achieve the ability of tenant isolation, computing isolation, network isolation and storage isolation. Moreover, for shared edge computing nodes, the edge network side can also maintain network security through technologies such as planar isolation, introducing firewalls, setting up security zones, and anti-virus gateways.

[0044] like Figure 1 The diagram illustrates a system architecture for a communication system. This system includes a network system 101 of the main operator, a network system 102 of the sharing operator, and an MEC system 103. Each of the main operator's network system 101, the sharing operator's network system 102, and the MEC system 103 includes a UPF (User-Generated Function), and multiple UPFs are interconnected via N9 interfaces. The MEC system 103 communicates with the main operator's network system 101 and the sharing operator's network system 102 through the UPFs.

[0045] It should be noted that the core network may include: Network Exposure Function (NEF), Policy Control Function (PCF), Unified Data Management (UDM), Network Repository Function (NRF), Authentication Server Function (AUSF), Access and Mobility Management Function (AMF), and Session Management Function (SMF), etc. In the MEC system, User Profile Function (UPF) agents and data network (DN) controllers are configured to enable network communication connections between the MEC and the core networks of multiple operators.

[0046] The MEC system may include a Multi-access Edge Platform (MEP), which can deploy MEC applications. The MEC system 103 can send local data flow filtering rules to its included UPFs, enabling the UPFs to filter and forward data flows from different operators.

[0047] Since this application enables communication between the MEC system and multiple operator core networks by sending local data stream filtering rules to the UPF, the technical solution provided by this application can be applied to both MEC and UPF coupled deployment schemes and MEC and UPF separated deployment schemes, and has good versatility.

[0048] It should be noted that, for ease of description, the above example uses a scenario of co-construction and sharing of MEC by two operators. The technical solution provided in this application is also applicable to application scenarios involving more than two operators.

[0049] With the introduction of MEC, workloads corresponding to cross-network MEC applications may need to be executed in environments involving multiple operators, each of which is part of the overall edge computing deployment solution. Cross-network MEC applications, because they need to be deployed simultaneously across two or more operator networks, resemble distributed multi-cloud environments: users need to deliver applications (workloads) generically at the optimal cost and faster, and the applications need to run (process) simultaneously across multiple public cloud platforms. Cross-network MEC applications require more application enablement features, such as application isolation and security, privacy protection across different operators, and application lifecycle management including application package loading, application registration, and instantiation, all of which need functional expansion and enhancement.

[0050] Currently, for non-cross-network MEC applications, deployment only requires deployment within a single operator's MEC network. For cross-network MEC applications, however, deployment requires deployment across different operators' MEC networks. This makes the MEC application deployment process complex and inefficient. Furthermore, since different operators' MEC networks are deployed in different regions, if a user is using a cross-network MEC application and traverses different areas, different operators' MEC networks are required to provide services. Consequently, if a user requests to deploy the MEC application during use, it may cause service interruptions.

[0051] To address the aforementioned technical problems, this application provides an application deployment method. In this method, a first application deployment request is received. This first application deployment request instructs the deployment of a mobile edge computing (MEC) application on a target MEC system. The first application deployment request includes application type information, which indicates whether the MEC application is a cross-carrier network application. Based on the application type information, the MEC application is deployed on the target MEC system. This allows for the determination of whether an MEC application is a cross-carrier network application based on the application type information, thereby enabling the deployment of the MEC application on the corresponding target MEC system. This eliminates the need for repeated deployments of the same application, improving deployment efficiency. Furthermore, deploying the MEC application on the target MEC system with a single request provides users with stable MEC services.

[0052] The implementation environment of the embodiments of this application is described below.

[0053] like Figure 2 As shown, a communication system provided in an embodiment of this application is provided. The system includes: a deployment device 201 and an OSS 202 of multiple MEC systems.

[0054] The deployment device 201 is connected to each of the multiple MEC systems OSS 202 via a communication link. The deployment device 201 receives a request message from any one of the multiple MEC systems OSS 202. This request message is used to request the deployment of a MEC application.

[0055] For example, the deployment device 201 can be OSS-Federation.

[0056] The deployment device 201 is also used to determine the configuration information required to deploy MEC applications.

[0057] The deployment device 201 is also used to instantiate the MEC application according to the configuration information and send the instantiation information of the MEC application to the corresponding OSS.

[0058] It should be noted that the multiple MEC systems include the MEC systems of the contracting operator and the MEC systems of the sharing operator. The contracting operator refers to the operator responsible for building the network infrastructure, i.e., the owner of the network infrastructure, while the sharing operator refers to other operators who can use the network infrastructure. In the contracting operator's MEC system, the OSS is connected to the MEO, and the deployment device 201 is also connected to the MEO. The MEO is used to instruct the MEC host to create application instances of MEC applications.

[0059] In one possible implementation, the deployment device 201 directly instructs the MEO to instantiate the MEC application.

[0060] In another possible implementation, the deployment device 201 instructs the MEO to instantiate the MEC application via the OSS in the contractor's MEC system.

[0061] Secondly, the MEC system to which the OSS that sends the request message belongs can be the MEC system to which the MEC application is to be deployed, or it can be another MEC system.

[0062] For example, the MEC shared system includes three OSSs: OSS-1, OSS-2, and OSS-3. The request message sent by OSS-1 to the deployment device can be a request to deploy a MEC application in the MEC system of OSS-1, a request to deploy a MEC application in the MEC system of OSS-2, or a request to deploy a MEC application in the MEC system of OSS-3.

[0063] In addition, multiple MEC systems can be deployed by the same operator. The technical solution provided in this application can also solve the problem that multiple MEC systems in the same operator cannot achieve service sharing.

[0064] Through the above scheme, multiple MEC systems in the MEC shared system 30 can instantiate MEC applications in the MEC system of the contractor through the deployment device 301, thereby realizing service sharing between MECs.

[0065] The embodiments of this application will now be described in detail with reference to the accompanying drawings.

[0066] like Figure 3 The illustration shows an application deployment method provided in an embodiment of this application. The method includes:

[0067] S301, Receive the first application deployment request.

[0068] The first application deployment request is used to instruct the deployment of the MEC application on the target MEC system. The target MEC system may include one or more MEC systems.

[0069] It should be noted that when the target MEC system includes multiple MEC systems, each MEC system belongs to a different operator.

[0070] In this embodiment of the application, the first application deployment request includes: application type information and application identifier, wherein the application type information is used to indicate whether the MEC application is an application that crosses carrier networks.

[0071] The application type information is either a first type of information or a second type of information. The first type of information is used to indicate that the MEC application is a cross-carrier network application, and the second type of information is used to indicate that the MEC application is a non-cross-carrier network application.

[0072] It should be noted that the embodiments of this application do not limit the application type information. For example, the first type information is a, and the second type information is b. Or, for example, the first type information is 0, and the second type is 1. It should be understood that when the MEC application is not a cross-carrier network application, the target MEC system is one MEC system; when the MEC application is a cross-carrier network application, the target MEC system is multiple MEC systems.

[0073] Optionally, the first application deployment request may also include the Uniform Resource Identifier (URI) of the first application.

[0074] In one possible implementation, the first application deployment request is specifically used to instruct the deployment of the first operator's MEC application in the first MEC system. The deployment device can receive the first application deployment request sent by the first MEC system.

[0075] For example, the deployment device may receive a first application deployment request sent by the OSS of the first operator. Alternatively, the OSS of the first operator may send the first application deployment request to the MEO of the first operator. Then, the MEO of the first operator determines that the application type information is second type information and sends the first application deployment request to the deployment device.

[0076] In another possible implementation, the deployment device can receive a first application deployment request sent by the server of the MEC application.

[0077] S302. Based on the application type information, deploy the MEC application on the target MEC system.

[0078] In one possible implementation, based on application type information, it is determined whether the MEC application is a cross-carrier network application. If the application type information is of the first type, then the first MEC of the first carrier is deployed in the first MEC system of the first carrier, and the MEC application of the second carrier is deployed in the second MEC system of the second carrier. The target MEC system includes the first MEC system and the second MEC system.

[0079] It should be noted that the first MEC system refers to the MEC system of the contracting operator (also known as the local operator). The second MEC system refers to the MEC system of another operator. For details on deploying MEC applications on an MEC system, please refer to the methods for deploying MEC applications on an operator's MEC system in conventional technologies, which will not be elaborated here.

[0080] Understandably, if the application type information is the first type, then based on the first application deployment request, MEC applications from different operators can be deployed separately on their respective operators' MEC systems. This avoids deploying an application on one MEC system and then on other MEC systems, thus achieving pre-deployment of MEC applications.

[0081] In one possible design, if the application type information is the second type of information, then the first MEC of the first operator will be deployed in the first MEC system, and the target MEC system includes the first MEC system.

[0082] Therefore, if the application type information is the second type, it means that the MEC application is not a cross-carrier network application. In this case, the application only needs to be deployed on the requester's MEC system, without having to deploy the application on other carriers' MEC systems, thus saving resources of other carriers' MEC systems.

[0083] Based on the above scheme, a first application deployment request is received. This request instructs the deployment of a mobile edge computing (MEC) application on a target MEC system. The first application deployment request includes application type information, indicating whether the MEC application is a cross-carrier network application. Based on the application type information, the MEC application is deployed on the target MEC system. This allows for the determination of whether an MEC application is a cross-carrier network application based on the application type information, thus enabling the deployment of the MEC application on the corresponding target MEC system. This eliminates the need for repeated deployments of the same application, improving deployment efficiency. Furthermore, deploying the MEC application on the target MEC system with a single request provides users with stable MEC services.

[0084] In some embodiments, a second application deployment request may be sent to the second MEC system, the second application deployment request being used to instruct the deployment of the second MEC application in the second MEC system.

[0085] In one possible design, the first application deployment request also includes: carrier information, which indicates the carrier version of the MEC application.

[0086] It should be noted that the embodiments of this application do not limit the operator information. For example, operator information can be the operator network ID, Public Land Mobile Network (PLMN), etc.

[0087] In one possible design, if the application type information is of the first type, the operator information may include the identifier of the second operator. Alternatively, if the application type information is of the first type, the operator information may include the identifiers of both the first and second operators.

[0088] In another possible design, if the application type information is of type two, the carrier information may include the identifier of the first carrier. Alternatively, the carrier information may be empty.

[0089] Understandably, by including carrier information in the application deployment request, it is easier for the deployment device to deploy applications on different MEC systems based on the carrier information.

[0090] In one possible implementation, a second application deployment request is sent to the second MEC system based on the identifier of the second operator.

[0091] In some embodiments, after deploying the MEC application of the second operator to the second MEC system, a deployment completion message can be received from the second MEC system. Then, the deployment completion message can be sent to the first MEC system.

[0092] In some embodiments, MEC applications from different operators can be deployed on the same MEC system.

[0093] In this embodiment, the first application deployment request is specifically used to instruct the deployment of a first operator's MEC application in a first MEC system, where the target MEC system is the first MEC system. If the application type information is first type information, then the first operator's MEC application and the second operator's MEC application are deployed in the first MEC system, where the first type information indicates that the MEC application is a cross-operator network application. If the application type information is second type information, then the first operator's MEC application is deployed in the first MEC system, where the second type information indicates that the MEC application is a non-cross-operator network application.

[0094] Understandably, if the application type information is type one, it means that users from different operators may use the MEC application. Therefore, MEC applications from different operators can be deployed on a single operator's MEC system, allowing users from different operators to share the MEC application within the same MEC system. If the application type information is type two, it means that only users from that specific operator need to use the MEC application. In this case, only that operator's MEC application needs to be deployed on the MEC platform, improving the resource utilization of the MEC platform.

[0095] The embodiments of this application are described below with reference to specific examples. For example... Figure 4As shown, the first operator's OSS (hereinafter referred to as the first OSS) can send an edge application package loading request 1 (including operator information and application type information) to the first operator's MEO (hereinafter referred to as the first MEO). The first MEO can reply to the edge application package loading request 1. Furthermore, the first MEO can send a package loading notification 1 to the first operator's MEPM (hereinafter referred to as the first MEPM), and the first MEPM will send a notification to the deployment device (such as OSS-Federation). If the application type information is type two, the deployment device can deploy the application on the first operator's MEC platform. The deployment device can also send feedback to the first MEPM, and the first MEPM can send feedback to the first MEO.

[0096] Or, as Figure 5 As shown, the first OSS can send an edge application package loading request 1 (including operator information and application type information) to the first MEO, and the first MEO can reply to the edge application package loading request 1. Furthermore, the first MEO can send a package loading notification 1 to the first MEPM, which in turn sends a notification to a deployment device (such as OSS-Federation), which can deploy the application on the first operator's MEC platform. The deployment device can also send feedback to the first MEPM, and the first MEPM can send feedback to the first MEO.

[0097] Furthermore, if the application type information is of type one, the first MEO can forward the edge application package loading request 1 to OSS-Federation. OSS-Federation can then send the edge application package loading request 2 to the second operator's OSS (hereinafter referred to as the second OSS). The second OSS can then send the edge application package loading request 2 to the second operator's MEO (hereinafter referred to as the second MEO), and the second MEO can reply to the edge application package loading request 2. The second MEO can also send a package loading notification 2 to the second operator's MEPM (hereinafter referred to as the second MEPM), and the second MEPM can send feedback to the second MEO. The second MEPM can then send a feedback message to the deployment device (such as OSS-Federation), indicating that the MEC application has been deployed in the second MEC system. OSS-Federation can then send this feedback message to the first OSS.

[0098] The foregoing primarily describes the solutions provided by the embodiments of this application from a methodological perspective. It is understood that the application deployment apparatus, in order to achieve the aforementioned functions, includes hardware structures and / or software modules corresponding to the execution of each function. Those skilled in the art should readily recognize that, based on the application deployment method steps described in conjunction with the embodiments disclosed in this application, this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed in hardware or by computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0099] This application embodiment can divide the application deployment device into functional modules or functional units according to the above method examples. For example, each function can be divided into a separate functional module or functional unit, or two or more functions can be integrated into one processing module. The integrated module can be implemented in hardware or in software functional modules or functional units. The module or unit division in this application embodiment is illustrative and represents only one logical functional division; other division methods may be used in actual implementation.

[0100] This application provides an application deployment apparatus. For example... Figure 6 As shown, the deployment device for this application may include: a receiving module 601 and a processing module 602.

[0101] The receiving module 601 is used to receive a first application deployment request, which instructs the MEC application to be deployed on the target MEC system. The first application deployment request includes application type information, which indicates whether the MEC application is a cross-carrier network application. The processing module 602 is used to deploy the MEC application on the target MEC system based on the application type information.

[0102] In one possible design, the first application deployment request specifically instructs the deployment of a first operator's MEC application in a first MEC system; the application type information is either first type information or second type information, where the first type information indicates that the MEC application is a cross-operator network application, and the second type information indicates that the MEC application is a non-cross-operator network application. Processing module 602 is further configured to, if the application type information is first type information, deploy the first operator's first MEC in the first operator's first MEC system and deploy the second operator's MEC application in the second operator's second MEC system, where the target MEC system includes both the first and second MEC systems. Processing module 602 is also configured to, if the application type information is second type information, deploy the first operator's first MEC in the first MEC system, where the target MEC system includes the first MEC system.

[0103] In one possible design, the application deployment device further includes a sending module 603, which is used to send a second application deployment request to the second MEC system, the second application deployment request being used to instruct the deployment of the second MEC application in the second MEC system.

[0104] In one possible design, the first application deployment request also includes: carrier information, which indicates the carrier version of the MEC application.

[0105] In one possible design, the operator information includes: the identifier of the second operator. The processing module 602 is also configured to send a second application deployment request to the second MEC system based on the identifier of the second operator.

[0106] In one possible design, the first application deployment request is specifically used to instruct the deployment of a first operator's MEC application in a first MEC system, with the first MEC system being the target MEC system. Processing module 602 is further configured to, if the application type information is first type information, deploy the first operator's MEC application and the second operator's MEC application in the first MEC system, where the first type information indicates that the MEC application is a cross-operator network application. Processing module 602 is also configured to, if the application type information is second type information, deploy the first operator's MEC application in the first MEC system, where the second type information indicates that the MEC application is a non-cross-operator network application.

[0107] Figure 7 This is a schematic diagram illustrating the structure of an application deployment apparatus according to an exemplary embodiment. The application deployment apparatus may include a processor 702, which executes application code to implement the application deployment method of this application.

[0108] The processor 702 may be a central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits used to control the execution of the program of the present application.

[0109] like Figure 7 As shown, the application deployment apparatus may further include a memory 703. The memory 703 stores the application code that executes the scheme of this application, and its execution is controlled by the processor 702.

[0110] The memory 703 may be a read-only memory (ROM) or other type of static storage device capable of storing static information and instructions, random access memory (RAM) or other type of dynamic storage device capable of storing information and instructions, or it may be an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage (including compressed optical discs, laser discs, optical discs, digital versatile optical discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or any other medium capable of carrying or storing desired program code in the form of instructions or data structures and accessible by a computer, but is not limited thereto. The memory 703 may exist independently and be connected to the processor 702 via a bus 704. The memory 703 may also be integrated with the processor 702.

[0111] like Figure 7 As shown, the application deployment device may further include a communication interface 701, wherein the communication interface 701, processor 702, and memory 703 may be coupled to each other, for example, through a bus 704. The communication interface 701 is used for information interaction with other devices, for example, supporting information interaction between the application deployment device and other devices.

[0112] It should be pointed out that, Figure 7 The device structure shown does not constitute a limitation on the deployment device of this application, except Figure 7 In addition to the components shown, the deployment apparatus for this application may include more or fewer components than illustrated, or combine certain components, or have different component arrangements.

[0113] In actual implementation, the functions implemented by the processing unit can be derived from... Figure 7 The processor 702 shown calls the program code in memory 703 to implement this.

[0114] This application also provides a computer-readable storage medium storing instructions that, when executed by a processor of a computer device, enable the computer to perform the deployment method of the application provided in the embodiments described above. For example, the computer-readable storage medium may be a memory 703 including instructions, which may be executed by a processor 702 of a computer device to complete the described method. Optionally, the computer-readable storage medium may be a non-transitory computer-readable storage medium, such as a ROM, RAM, CD-ROM, magnetic tape, floppy disk, or optical data storage device.

[0115] Figure 8 A conceptual partial view of a computer program product provided in an embodiment of this application is shown schematically. The computer program product includes a computer program for executing computer processes on a computing device.

[0116] In one embodiment, the computer program product is provided using a signal bearer medium 800. The signal bearer medium 800 may include one or more program instructions that, when executed by one or more processors, can provide the above-mentioned... Figure 3 The described function or part of the function. Therefore, for example, refer to... Figure 3 In the embodiment shown, one or more features of S301-S302 can be fulfilled by one or more instructions associated with the signal carrying medium 800. Furthermore, Figure 8 The program instructions in the document also describe example instructions.

[0117] In some examples, the signal carrying medium 800 may include a computer-readable medium 801, such as, but not limited to, a hard disk drive, a compact disc (CD), a digital video optical disc (DVD), a digital magnetic tape, a memory, a read-only memory (ROM), or a random access memory (RAM), and so on.

[0118] In some implementations, the signal carrying medium 800 may include a computer recordable medium 802, such as, but not limited to, a memory, a read / write (R / W) CD, a R / W DVD, and so on.

[0119] In some implementations, the signal carrying medium 800 may include a communication medium 803, such as, but not limited to, digital and / or analog communication media (e.g., fiber optic cables, waveguides, wired communication links, wireless communication links, etc.).

[0120] The signal-bearing medium 800 can be transmitted by a wireless communication medium 803. One or more program instructions can be, for example, computer-executable instructions or logical implementation instructions.

[0121] In some examples, the application deployment apparatus may be configured to provide various operations, functions, or actions in response to one or more program instructions in a computer-readable medium 801, a computer-recordable medium 802, and / or a communication medium 803.

[0122] Through the above description of the embodiments, those skilled in the art can clearly understand that, for the sake of convenience and brevity, only the division of the above functional modules is used as an example. In actual applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above.

[0123] In the several embodiments provided in this application, it should be understood that the disclosed apparatus and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of modules or units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another apparatus, or some features may be ignored or not executed. Furthermore, the mutual coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0124] The units described as separate components may or may not be physically separate. A component shown as a unit can be one or more physical units; that is, it can be located in one place or distributed in multiple different locations. Some or all of the constituent units can be selected to achieve the purpose of this embodiment, depending on actual needs.

[0125] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0126] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a readable storage medium. Based on this understanding, the technical solution of the embodiments of this application, essentially, or the part that contributes to the prior art, or a complete or partial classification of the technical solution, can be embodied in the form of a software product. This software product is stored in a storage medium and includes several instructions to cause a device (which may be a microcontroller, chip, etc.) or processor to execute all or part of the steps of the methods of the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, ROM, RAM, magnetic disks, or optical disks.

[0127] The above are merely specific embodiments of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions within the technical scope disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A method for deploying an application, characterized in that, The method includes: A first application deployment request is received, which instructs the deployment of a mobile edge computing (MEC) application on a target MEC system. The first application deployment request includes: application type information, which indicates whether the MEC application is a cross-carrier network application; specifically, the first application deployment request instructs the deployment of the MEC application of a first operator on a first MEC system; the application type information is either first type information or second type information, where the first type information indicates that the MEC application is a cross-carrier network application, and the second type information indicates that the MEC application is a non-cross-carrier network application. If the application type information is the first type information, then the first MEC application of the first operator is deployed in the first MEC system of the first operator, and the MEC application of the second operator is deployed in the second MEC system of the second operator. The target MEC system includes the first MEC system and the second MEC system. If the application type information is the second type information, then the first MEC application of the first operator will be deployed in the first MEC system, and the target MEC system includes the first MEC system.

2. The method according to claim 1, characterized in that, Deploying the MEC application of the second operator in the second operator's second MEC system includes: Send a second application deployment request to the second MEC system. The second application deployment request is used to instruct the deployment of the second MEC application on the second MEC system.

3. The method according to claim 2, characterized in that, The first application deployment request also includes: carrier information, which is used to indicate the carrier version of the MEC application.

4. The method according to claim 3, characterized in that, The operator information includes: the identifier of the second operator; the step of sending the second application deployment request to the second MEC system includes: Based on the identifier of the second operator, the second application deployment request is sent to the second MEC system.

5. The method according to claim 1, characterized in that, The first application deployment request is specifically used to instruct the deployment of the MEC application of the first operator in the first MEC system, wherein the target MEC system is the first MEC system; the method further includes: If the application type information is the first type information, then the MEC application of the first operator and the MEC application of the second operator will be deployed in the first MEC system. The first type information is used to indicate that the MEC application is a cross-operator network application. If the application type information is the second type information, then the MEC application of the first operator will be deployed in the first MEC system. The second type information is used to indicate that the MEC application is a non-cross-operator network application.

6. An application deployment apparatus, characterized in that, The device includes: A receiving module is configured to receive a first application deployment request, which instructs the deployment of an MEC application on a target MEC system. The first application deployment request includes: application type information, which indicates whether the MEC application is a cross-carrier network application; specifically, the first application deployment request instructs the deployment of the MEC application of a first carrier on a first MEC system; the application type information is either first type information or second type information, where the first type information indicates that the MEC application is a cross-carrier network application, and the second type information indicates that the MEC application is a non-cross-carrier network application. The processing module is configured to, if the application type information is the first type information, deploy the first MEC application of the first operator in the first MEC system of the first operator, and deploy the MEC application of the second operator in the second MEC system of the second operator, wherein the target MEC system includes the first MEC system and the second MEC system; The processing module is further configured to deploy the first MEC application of the first operator in the first MEC system if the application type information is the second type information, wherein the target MEC system includes the first MEC system.

7. An application deployment apparatus, characterized in that, include: Processor and memory; The processor and the memory are coupled; The memory is used to store one or more programs, the one or more programs including computer-executable instructions, and when the application deployment device is running, the processor executes the computer-executable instructions stored in the memory to cause the application deployment device to perform the method as described in any one of claims 1-5.

8. A computer-readable storage medium storing instructions, characterized in that, When the computer executes the instruction, the computer performs the method as described in any one of claims 1-5.

9. A computer program product containing instructions, characterized in that, When the instruction is executed by the computing device, the computing device performs the method as described in any one of claims 1-5.

Images