Application deployment method and device

Abstract

The invention provides an application deployment method and device, relates to the technical field of communication, and is used for solving the problem that the MEC application deployment process is relatively tedious. The method comprises the steps that a first application deployment request is received, the first application deployment request is used for indicating that a mobile edge computing MEC application is deployed in a target MEC system, the first application deployment request comprises application type information, and the application type information is used for indicating whether the MEC application is an application of a cross-operator network or not. And deploying the MEC application in the target MEC system based on the application type information.

Description

Technical Field

[0001] The present application relates to the field of communication technology, and in particular to a method and device for deploying an application. Background Art

[0002] Mobile edge computing (MEC) can be set up at the edge nodes of the communication network to provide computing power for terminals, thereby effectively reducing the service latency of terminals. MEC co-construction and sharing means that multiple operators jointly build and share MEC equipment resources, thereby reducing the operation and maintenance costs of MEC construction.

[0003] Currently, application deployers can deploy MEC applications in the MEC of each operator. However, as the MEC construction of more operators becomes popular, the process of deploying MEC applications in the MEC of each operator is more complicated and inefficient. Summary of the invention

[0004] The present application provides an application deployment method and device for solving the problem that the deployment process of MEC applications is relatively cumbersome.

[0005] In order to achieve the above objectives, this application adopts the following technical solutions:

[0006] In a first aspect, the present application provides an application deployment method. In the method, a first application deployment request is received, the first application deployment request is used to indicate that a mobile edge computing MEC application is deployed in a target MEC system, and the first application deployment request includes: application type information, the application type information is used to indicate 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.

[0007] Based on the above technical solution, a first application deployment request is received, and the first application deployment request is used to indicate that a mobile edge computing MEC application is deployed in a target MEC system. The first application deployment request includes: application type information, and the application type information is used to indicate 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. In this way, it is possible to determine whether the MEC application is an application across operator networks based on the application type information, and then deploy the MEC application in the corresponding target MEC system. In this way, there is no need to repeatedly deploy the same application multiple times, which improves deployment efficiency. In addition, by deploying the MEC application in the target MEC system with one request, stable MEC services can be provided to users.

[0008] In one possible design, the first application deployment request is specifically used to indicate that the MEC application of the first operator is deployed in the first MEC system; the application type information is the first type information or the second type information, the first type information is used to indicate that the MEC application is an application across operator networks, and the second type information is used to indicate that the MEC application is an application that is not across operator networks. If the application type information is the first type information, the first MEC 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, and the target MEC system includes the first MEC system and the second MEC system. If the application type information is the second type information, the first MEC of the first operator 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, where the second application deployment request is used to indicate that the second MEC application is deployed in the second MEC system.

[0010] In one possible design, the first application deployment request also includes: operator information, where the operator information is used to indicate the operator version of the MEC application.

[0011] In one possible design, the operator information includes: an 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 is specifically used to indicate that the MEC application of the first operator is deployed in the first MEC system, and the target MEC system is the first MEC system. If the application type information is the first type of information, the MEC application of the first operator and the MEC application of the second operator are deployed in the first MEC system, and the first type of information is used to indicate that the MEC application is an application across operator networks. If the application type information is the second type of information, the MEC application of the first operator is deployed in the first MEC system, and the second type of information is used to indicate that the MEC application is not an application across operator networks.

[0013] In a second aspect, the present application provides an application deployment device, which includes a receiving module and a processing module.

[0014] The receiving module is used to receive a first application deployment request, the first application deployment request is used to indicate that the MEC application is deployed in the target MEC system, and the first application deployment request includes: application type information, the application type information is used to indicate whether the MEC application is an application across operator networks. The processing module is used to deploy the MEC application in the target MEC system based on the application type information.

[0015] In a third aspect, the present application provides an application deployment device, the device comprising: a processor and a 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 execution instructions, and when the application deployment device is running, the processor executes the computer execution instructions stored in the memory to implement the method described in the first aspect and any possible implementation of the first aspect.

[0016] In a fourth aspect, the present application provides a computer-readable storage medium, which stores instructions. When the instructions are executed on a computer, the computer executes the method described in the above-mentioned first aspect and any possible implementation of the first aspect.

[0017] In a fifth aspect, the present application provides a chip, comprising a processor and a communication interface, wherein the communication interface and the processor are coupled, and the processor is used to run a computer program or instructions to implement the method described in the first aspect and any possible implementation of the first aspect.

[0018] In a sixth aspect, the present application provides a computer program product comprising instructions, which, when executed by a computer, enables the computer to execute the method described in the above-mentioned first aspect and any possible implementation manner of the first aspect.

[0019] In the above scheme, the technical problems that can be solved and the technical effects achieved by the application deployment device, computer equipment, computer storage medium, chip or computer program product can be referred to the technical problems and technical effects solved by the above-mentioned first aspect, and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS

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

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

[0022] Figure 3 A flowchart of a method for deploying an application provided in an embodiment of the present application;

[0023] Figure 4 A flowchart of another application deployment method provided in an embodiment of the present application;

[0024] Figure 5 A flowchart of another application deployment method provided in an embodiment of the present application;

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

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

[0027] Figure 8 A conceptual partial view of a computer program product provided for an embodiment of the present application. DETAILED DESCRIPTION

[0028] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

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

[0030] In addition, the terms "including" and "having" and any variations thereof mentioned in the description of this application are intended to cover non-exclusive inclusions. For example, a process, method, system, product or device that includes a series of steps or modules is not limited to the listed steps or modules, but may optionally include other steps or modules that are not listed, or may optionally include other steps or modules that are inherent to these processes, methods, products or devices.

[0031] In addition, in the embodiments of the present application, words such as "exemplary" or "for example" are used to indicate examples, illustrations or descriptions. Any embodiment or design described as "exemplary" or "for example" in the present application should not be interpreted as being more preferred or more advantageous than other embodiments or designs. Specifically, the use of words such as "exemplary" or "for example" is intended to present concepts in a specific way.

[0032] The following explains the terms involved in the embodiments of the present application to facilitate the reader's understanding.

[0033] 1. Co-construction and sharing. Co-construction and sharing refers to the network service in which multiple operators jointly build network facilities and share network facilities. The co-construction and sharing solution can greatly reduce the operation and maintenance costs of network construction and improve the working efficiency of network facilities. At present, co-construction and sharing are mainly used in the co-construction and sharing of communication networks. For example, the co-construction and sharing of the fifth-generation mobile communication (5th-generation mobile communication technology, 5G) network includes two methods: inter-network roaming and access network sharing. In the case of inter-network roaming, the basic network facilities are the same as the normal construction plan, and the terminal accesses the 5G network through the access network equipment and core network equipment of other operators. This application does not go into too much detail on this method.

[0034] 2. Mobile edge computing, also known as multi-access edge computing, refers to a solution that places devices with computing capabilities at nodes in the communication network so that terminals can obtain the required service resources through MEC devices set at network nodes to reduce service latency.

[0035] Among them, MEC includes MEC system level (MECsystem level), MEC host level (MEC host level) and MEC network level (MEC networks level).

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

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

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

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

[0040] In order to support MEC co-construction and sharing, not only does the MEC network (user plane function (UPF)) need to be connected to the core networks of different operators at the same time, but the MEC business system also needs to be shared between different operators to support MEC applications deployed in different operator networks to meet the service needs of users of different operators at the same time. Therefore, from the perspective of system logical function division, the access of MEC systems to different operator networks can be divided into two parts: MEC network connection and MEC business connection.

[0041] Among them, MEC network docking can use the extension of UPF's own functions to support access to multiple operators' core networks, that is, UPF itself is required to support access to multiple operators' core networks. At this time, MEC can act as a local agent for the application layer function (AF), directly send local data flow filtering rules to the shared UPF, and configure UPF data flow forwarding and data flow filtering rules for different operators. This not only keeps the interface between the MEC system and UPF unchanged (N4 and MP interfaces defined by ETSI and 3GPP), but also enables the UPF proxy (UPF Proxy) and data network controller (Data Network Controller) to be implemented inside the UPF.

[0042] In the MEC service docking part, a new operation support system (OSS) Federation network element is introduced in the control plane of the MEC system level, which is used to complete the interconnection with the OSS of different operators respectively, and continue to use the N4, MP2, Mm1 and Mm2 interfaces 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 multi-tenant mode, that is, basic resources and business resources of bare metal isolation are allocated to different users. For example, in terms of resource isolation, the underlying cloud computing service model (Infrastructure as a Service, IaaS) stack is used to achieve 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 plane isolation, introduction of firewalls, setting of security zones, antivirus gateways and other technologies.

[0044] like Figure 1 As shown, it shows a system architecture diagram of a communication system. The communication system includes a network system 101 of a construction operator, a network system 102 of a shared operator, and an MEC system 103. Among them, the network system 101 of the construction operator, the network system 102 of the shared operator, and the MEC system 103 all include UPFs, and multiple UPFs are connected through the N9 interface. The MEC system 103 is connected to the network system 101 of the construction operator and the network system 102 of the shared operator through the UPF.

[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), Session Management Function (SMF), etc. In the MEC system, a User Profile Function (UPF) agent and a data network (DN) controller are set to realize network communication connection between MEC and the core networks of multiple operators.

[0046] The MEC system may include a multi-access edge platform (MEP), which may deploy MEC applications. The MEC system 103 may send local data flow filtering rules to the UPF included therein, so that the UPF may filter and forward data flows of different operators.

[0047] Since the present application realizes communication between the MEC system and multiple operator core networks by sending local data flow filtering rules to UPF, the technical solution provided by the present application can be applied not only to the scheme of coupled deployment of MEC and UPF, but also to the scheme of separate deployment of MEC and UPF, and has good versatility.

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

[0049] With the introduction of MEC, the workloads corresponding to cross-network MEC applications may need to be executed in environments involving multiple operators, and each environment is part of the entire edge computing deployment solution. Since cross-network MEC applications need to be deployed in two or more operator networks at the same time, their deployment is similar to a distributed multi-cloud environment: users need to complete the universal delivery of applications (workloads) at the optimal cost and faster, and the applications need to run (process) across multiple public cloud platforms at the same time. More application-enabling functions are required for cross-network MEC applications, such as application isolation and security, privacy protection of different operators, and application lifecycle management of application package loading, application registration, and instantiation.

[0050] Currently, for non-cross-network MEC applications, the deployer only needs to deploy them in the MEC of one operator. For cross-network MEC applications, the deployer needs to deploy them in the MECs of different operators. This makes the process of deploying MEC applications more complicated and inefficient. In addition, since different operators' MECs are deployed in different areas, if a user is using a cross-network MEC application and passes through different areas, different operators' MECs are required to provide services for it. In this way, if you request to deploy the MEC application during use, it may cause service jams.

[0051] In order to solve the above technical problems, the present application provides an application deployment method. In this method, a first application deployment request is received, and the first application deployment request is used to indicate that a mobile edge computing MEC application is deployed in a target MEC system. The first application deployment request includes: application type information, and the application type information is used to indicate 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. In this way, it is possible to determine whether the MEC application is an application across operator networks based on the application type information, and then deploy the MEC application in the corresponding target MEC system. In this way, there is no need to repeatedly deploy the same application multiple times, which improves deployment efficiency. In addition, by deploying the MEC application in the target MEC system with one request, stable MEC services can be provided to users.

[0052] The implementation environment of the embodiments of the present application is introduced below.

[0053] like Figure 2 As shown, a communication system provided in an embodiment of the present application includes: a deployment device 201 and OSS202 of multiple MEC systems.

[0054] The deployment device 201 is connected to each OSS in the multiple MEC systems OSS 202 via a communication link. The deployment device 201 is used to receive a request message sent by any OSS in the multiple MEC systems OSS 202. The request message is used to request the deployment of the MEC application.

[0055] Exemplarily, the deployment device 201 may be OSS-Federation.

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

[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 system of the construction operator and the MEC system of the shared operator. The construction operator refers to the operator responsible for building the network facility, that is, the owner of the network facility, and the shared operator refers to other operators who can use the network facility. Among them, the OSS in the MEC system of the construction operator is connected to the MEO, and the deployment device 201 is also connected to the MEO. MEO is used to instruct the MEC host to create an application instance of the MEC application.

[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 through the OSS in the MEC system of the operator.

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

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

[0063] In addition, the same operator can also deploy multiple MEC systems. 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 solution, multiple MEC systems in the MEC sharing system 30 can instantiate MEC applications in the MEC system of the operator through the deployment device 301, thereby realizing service sharing between MECs.

[0065] The embodiments of the present application are described in detail below in conjunction with the accompanying drawings.

[0066] like Figure 3 As shown, a deployment method of an application provided in an embodiment of the present application includes:

[0067] S301. Receive a first application deployment request.

[0068] The first application deployment request is used to instruct to deploy the MEC application in 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 an embodiment of the present application, the first application deployment request includes: application type information and an application identifier, where the application type information is used to indicate whether the MEC application is an application across operator networks.

[0071] The application type information is first type information or second type information, the first type information is used to indicate that the MEC application is an application across operator networks, and the second type information is used to indicate that the MEC application is an application across non-operator networks.

[0072] It should be noted that the embodiment of the present application does not limit the application type information. For example, the first type of information is a, and the second type of information is b. For another example, the first type of information is 0, and the second type is 1. It should be understood that when the MEC application is not an application across operator networks, the target MEC system is one MEC system, and when the MEC application is an application across operator networks, the target MEC system is multiple MEC systems.

[0073] Optionally, the first application deployment request further includes a Uniform Resource Identifier (URI) of the first application.

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

[0075] Exemplarily, 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. Afterwards, the MEO of the first operator determines that the application type information is the second type information, and sends the first application deployment request to the deployment device.

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

[0077] S302: Deploy the MEC application in the target MEC system based on the application type information.

[0078] In a possible implementation, based on the application type information, it is determined whether the MEC application is an application across operator networks. If the application type information is the first type of information, the first MEC 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, and the target MEC system includes the first MEC system and the second MEC system.

[0079] It should be noted that the first MEC system is the MEC system of the construction operator (also referred to as the local operator). The second MEC system is the MEC system of another operator. For the specific introduction of the deployment device deploying the MEC application in the MEC system, reference can be made to the method of deploying the MEC application in the MEC system of an operator in conventional technology, which will not be repeated here.

[0080] It is understandable that if the application type information is the first type of information, the MEC applications of different operators can be deployed in the MEC systems of their respective operators based on the first application deployment request. In this way, it is avoided that the application is deployed in one MEC system and then deployed in other MEC systems, thus realizing the pre-deployment of MEC applications.

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

[0082] In this way, if the application type information is the second type of information, it means that the MEC application is not a cross-operator network application. In this case, the application only needs to be deployed in the MEC system of the requester, and there is no need to deploy the application in the MEC systems of other operators, thus saving resources of the MEC systems of other operators.

[0083] Based on the above scheme, a first application deployment request is received, and the first application deployment request is used to indicate that the mobile edge computing MEC application is deployed in the target MEC system. The first application deployment request includes: application type information, and the application type information is used to indicate 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. In this way, it is possible to determine whether the MEC application is an application across operator networks based on the application type information, and then deploy the MEC application in the corresponding target MEC system. In this way, there is no need to repeatedly deploy the same application multiple times, which improves the deployment efficiency. In addition, by deploying the MEC application in the target MEC system with one request, stable MEC services can be provided to users.

[0084] In some embodiments, a second application deployment request may be sent to the second MEC system, where the second application deployment request is used to instruct that the second MEC application be deployed in the second MEC system.

[0085] In one possible design, the first application deployment request also includes: operator information, where the operator information is used to indicate the operator version of the MEC application.

[0086] It should be noted that the embodiment of the present application does not limit the operator information. For example, the operator information may be an operator network ID, a public land mobile network (PLMN), etc.

[0087] In a possible design, when the application type information is the first type information, the operator information may include the identifier of the second operator. Alternatively, when the application type information is the first type information, the operator information may include the identifier of the first operator and the identifier of the second operator.

[0088] In another possible design, when the application type information is the second type information, the operator information may include an identifier of the first operator. Alternatively, the operator information may be empty.

[0089] It can be understood that by carrying the operator information in the application deployment request, the deployment device can deploy the application in different MEC systems based on the operator information.

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

[0091] In some embodiments, after the MEC application of the second operator is deployed in the second MEC system, a deployment completion message sent by the second MEC system may be received, and then the deployment completion message may be sent to the first MEC system.

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

[0093] In an embodiment of the present application, the first application deployment request is specifically used to indicate that the MEC application of the first operator is deployed in the first MEC system, and the target MEC system is the first MEC system. If the application type information is the first type of information, the MEC application of the first operator and the MEC application of the second operator are deployed in the first MEC system, and the first type of information is used to indicate that the MEC application is an application across operator networks. If the application type information is the second type of information, the MEC application of the first operator is deployed in the first MEC system, and the second type of information is used to indicate that the MEC application is not an application across operator networks.

[0094] It is understandable that if the application type information is the first type of information, it means that users of different operators may use the MEC application. Therefore, the MEC applications of different operators can be deployed in the MEC system of one operator, so that users of different operators can share the MEC application in the MEC system. If the application type information is the second type of information, it means that only the users of the operator need to use the MEC application, so only the MEC application of the operator needs to be deployed on the MEC platform, which improves the resource utilization of the MEC platform.

[0095] The following is an introduction to the embodiments of the present application with reference to specific examples. Figure 4As shown, the OSS of the first operator (referred to as the first OSS) can send an edge application package loading request 1 (including operator information and application type information) to the MEO of the first operator (referred to as the first MEO), and the first MEO can reply to the edge application package loading request 1. In addition, the first MEO can send a package loading notification 1 to the MEPM of the first operator (referred to as the first MEPM), and the first MEPM sends a notification to the deployment device (such as OSS-Federation). If the application type information is the second type of information, the deployment device can deploy the application on the MEC platform of the first operator. In addition, the deployment device can send feedback to the first MEPM, and the first MEPM can send feedback to the first MEO.

[0096] Or, if 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. In addition, the first MEO can send a package loading notification 1 to the first MEPM, and the first MEPM sends a notification to the deployment device (such as OSS-Federation), and the deployment device can deploy the application on the MEC platform of the first operator. In addition, the deployment device can 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 the first type of information, the first MEO may forward the edge application package loading request 1 to OSS-Federation. OSS-Federation may send an edge application package loading request 2 to the OSS of the second operator (referred to as the second OSS). Then, the second OSS may send an edge application package loading request 2 to the MEO of the second operator (referred to as the second MEO), and the second MEO may reply to the edge application package loading request 2. Furthermore, the second MEO may send a package loading notification 2 to the MEPM of the second operator (referred to as the second MEPM), and the second MEPM may send feedback to the second MEO. Furthermore, the second MEPM may send a feedback message to the deployment device (such as OSS-Federation), and the feedback message is used to indicate that the MEC application has been deployed in the second MEC system. Then, OSS-Federation may send the feedback message to the first OSS.

[0098] The above mainly introduces the solution provided by the embodiment of the present application from the perspective of the method. It is understandable that, in order to realize the above functions, the deployment device of the application includes a hardware structure and / or software module corresponding to the execution of each function. Those skilled in the art should easily realize that, in combination with the deployment method steps of the application of each example described in the embodiment disclosed in this application, the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in the form of hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0099] The embodiment of the present application can divide the deployment device of the application into functional modules or functional units according to the above method example. For example, each functional module or functional unit can be divided according to each function, or two or more functions can be integrated into one processing module. The above integrated module can be implemented in the form of hardware or in the form of software functional modules or functional units. Among them, the division of modules or units in the embodiment of the present application is schematic, which is only a logical function division. There may be other division methods in actual implementation.

[0100] The present application embodiment provides a deployment device for an application. Figure 6 As shown, the application deployment device 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, the first application deployment request is used to indicate that the MEC application is deployed in the target MEC system, and the first application deployment request includes: application type information, the application type information is used to indicate whether the MEC application is an application across operator networks. The processing module 602 is used to deploy the MEC application in the target MEC system based on the application type information.

[0102] In one possible design, the first application deployment request is specifically used to indicate that the MEC application of the first operator is deployed in the first MEC system; the application type information is the first type information or the second type information, the first type information is used to indicate that the MEC application is an application across operator networks, and the second type information is used to indicate that the MEC application is an application that is not across operator networks. Processing module 602 is also used to deploy the first MEC of the first operator in the first MEC system of the first operator if the application type information is the first type information, and to deploy the MEC application of the second operator in the second MEC system of the second operator, and the target MEC system includes the first MEC system and the second MEC system. Processing module 602 is also used to deploy the first MEC of the first operator in the first MEC system if the application type information is the second type information, and the target MEC system includes the first MEC system.

[0103] In one possible design, the application deployment device also includes a sending module 603, which is used to send a second application deployment request to the second MEC system, and the second application deployment request is used to indicate that the second MEC application is deployed in the second MEC system.

[0104] In one possible design, the first application deployment request also includes: operator information, where the operator information is used to indicate the operator version of the MEC application.

[0105] In a possible design, the operator information includes: an identifier of the second operator. The processing module 602 is further 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 indicate that the MEC application of the first operator is deployed in the first MEC system, and the target MEC system is the first MEC system. Processing module 602 is also used to deploy the MEC application of the first operator and the MEC application of the second operator in the first MEC system if the application type information is the first type information, and the first type information is used to indicate that the MEC application is an application across operator networks. Processing module 602 is also used to deploy the MEC application of the first operator in the first MEC system if the application type information is the second type information, and the second type information is used to indicate that the MEC application is not an application across operator networks.

[0107] Figure 7 7 is a schematic diagram of a structure of an application deployment device according to an exemplary embodiment. The application deployment device may include a processor 702, and the processor 702 is used to execute application program code to implement the application deployment method in the present 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 for controlling the execution of the program of the present application.

[0109] like Figure 7 As shown, the application deployment device may further include a memory 703. The memory 703 is used to store application program codes for executing the solution of the present application, and the execution is controlled by the processor 702.

[0110] The memory 703 may be a read-only memory (ROM) or other types of static storage devices that can store static information and instructions, a random access memory (RAM) or other types of dynamic storage devices that can store information and instructions, or 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 disc, laser disc, optical disc, digital versatile disc, Blu-ray disc, etc.), a magnetic disk storage medium or other magnetic storage device, or any other medium that can be used to carry or store the desired program code in the form of an instruction or data structure and can be accessed 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, the processor 702, and the memory 703 may be coupled to each other, for example, via a bus 704. The communication interface 701 is used to perform information interaction with other devices, for example, to support information interaction between the application deployment device and other devices.

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

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

[0114] The present application also provides a computer-readable storage medium, on which instructions are stored, and when the instructions in the computer-readable storage medium are executed by a processor of a computer device, the computer can execute the deployment method of the application provided in the above-mentioned embodiment. For example, the computer-readable storage medium may be a memory 703 including instructions, and the above instructions may be executed by a processor 702 of a computer device to complete the above method. Optionally, the computer-readable storage medium may be a non-temporary computer-readable storage medium, for example, a non-temporary computer-readable storage medium may be a ROM, RAM, CD-ROM, magnetic tape, floppy disk, optical data storage device, etc.

[0115] Figure 8 A conceptual partial view of a computer program product provided by an embodiment of the present application is schematically shown, where the computer program product includes a computer program for executing a computer process on a computing device.

[0116] In one embodiment, the computer program product is provided using a signal bearing medium 800. The signal bearing medium 800 may include one or more program instructions that, when executed by one or more processors, may provide the above-described Figure 3 Thus, for example, reference to Figure 3 In the embodiment shown in , one or more features of S301-S302 may be undertaken by one or more instructions associated with the signal bearing medium 800. In addition, Figure 8 The program instructions in also describe example instructions.

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

[0118] In some implementations, the signal bearing 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, or the like.

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

[0120] The signal bearing medium 800 may be communicated by a wireless form of communication medium 803. The one or more program instructions may be, for example, computer executable instructions or logic implemented 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 via computer-readable medium 801 , computer-recordable medium 802 , and / or communication medium 803 .

[0122] Through the description of the above implementation methods, technical personnel in the relevant field can clearly understand that for the convenience and simplicity of description, only the division of the above-mentioned functional modules is used as an example. In actual applications, the above-mentioned 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 the present application, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic, for example, the division of modules or units is only a logical function division, and there may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another device, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0124] The units described as separate components may or may not be physically separated, and the components shown as units may be one physical unit or multiple physical units, that is, they may be located in one place or distributed in multiple different places. Some or all of the units may be selected according to actual needs to achieve the purpose of the present embodiment.

[0125] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0126] If the integrated unit is implemented in the form of 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 embodiment of the present application is essentially or the part that contributes to the prior art or the full classification part or part of the technical solution can be embodied in the form of a software product, which is stored in a storage medium, including a number of instructions to enable a device (which can be a single-chip microcomputer, chip, etc.) or a processor (processor) to execute the full classification part or part of the steps of each embodiment method of the present application. The aforementioned storage medium includes various media that can store program codes, such as-U disk, mobile hard disk, ROM, RAM, disk or CD.

[0127] The above are only specific implementations of the present application, but the protection scope of the present application is not limited thereto, and any changes or substitutions within the technical scope disclosed in the present application should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

Claims

1. A method for deploying an application, characterized in that: The method comprises: receiving a first application deployment request, where the first application deployment request is used to instruct to deploy a mobile edge computing MEC application in a target MEC system, where the first application deployment request includes: application type information, where the application type information is used to indicate 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.

2. The method according to claim 1, characterized in that The first application deployment request is specifically used to indicate that the MEC application of the first operator is deployed in the first MEC system; the application type information is first type information or second type information, the first type information is used to indicate that the MEC application is an application across operator networks, and the second type information is used to indicate that the MEC application is an application across non-operator networks; The deploying the MEC application in the target MEC system based on the application type information includes: If the application type information is the first type information, the first MEC 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, and the target MEC system includes the first MEC system and the second MEC system; If the application type information is the second type information, the first MEC of the first operator is deployed in the first MEC system, and the target MEC system includes the first MEC system.

3. The method according to claim 2, characterized in that Deploying the MEC application of the second operator in a second MEC system of the second operator includes: A second application deployment request is sent to the second MEC system, where the second application deployment request is used to instruct that the second MEC application be deployed in the second MEC system.

4. The method according to claim 3, characterized in that The first application deployment request also includes: operator information, where the operator information is used to indicate an operator version of the MEC application.

5. The method according to claim 4, characterized in that The operator information includes: an identifier of the second operator; and the sending a 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.

6. The method according to claim 1, characterized in that The first application deployment request is specifically used to instruct that the MEC application of the first operator is deployed in the first MEC system, and the target MEC system is the first MEC system; and the deploying the MEC application in the target MEC system based on the application type information includes: If the application type information is first type information, the MEC application of the first operator and the MEC application of the second operator are deployed in the first MEC system, and the first type information is used to indicate that the MEC application is an application across operator networks; If the application type information is second type information, the MEC application of the first operator is deployed in the first MEC system, and the second type information is used to indicate that the MEC application is a non-cross-operator network application.

7. An application deployment device, characterized in that: The device comprises: A receiving module, configured to receive a first application deployment request, wherein the first application deployment request is used to instruct to deploy an MEC application in a target MEC system, and the first application deployment request includes: application type information, wherein the application type information is used to indicate whether the MEC application is an application across operator networks; A processing module is used to deploy the MEC application in the target MEC system based on the application type information.

8. An application deployment device, characterized in that: include: Processor and memory; The processor is coupled to the memory; The memory is used to store one or more programs, and one or more of the programs include computer-executable instructions. When the application deployment device is running, the processor executes the computer-executable instructions stored in the memory to enable the application deployment device to perform the method as described in any one of claims 1-6.

9. A computer-readable storage medium, wherein instructions are stored in the computer-readable storage medium, characterized in that: When a computer executes the instruction, the computer performs the method according to any one of claims 1 to 6.

10. A computer program product comprising instructions, characterized in that When the instructions are executed by a computing device, the computing device is caused to perform the method according to any one of claims 1 to 6.

Images