Mobile edge computing application management for wireless networks

By providing a mobile edge computing application manager on a mobile edge computing server, receiving and managing the MEC application standards sent by external application controllers, the problem of underutilization and low management efficiency in the MEC environment is solved, and more efficient resources are achieved Management and user experience optimization.

CN112236989BActive Publication Date: 2024-11-19NOKIA TECHNOLOGIES OY
View PDF 10 Cites 0 Cited by

Patent Information

Application Number
CN201880094318.7
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2018-06-07
Publication Date
2024-11-19
Estimated Expiration
2038-06-07

AI Technical Summary

Technical Problem

In a mobile edge computing (MEC) environment, external application controllers are difficult to effectively manage the life cycle of MEC applications, resulting in underutilization of resources, large amounts of overhead and delays in application instantiation and termination, and the availability of resources cannot be accurately judged and Changes in demand.

Method used

By providing a mobile edge computing application manager on a mobile edge computing server close to a radio access network, it receives and stores MEC application standards sent by an external application controller, including management rules for managing the life cycle of the MEC application and is based on These rules determine the feasibility of applications and resource management strategies, and optimize resource utilization and application operations.

Benefits of technology

It improves the utilization rate of MEC resources, reduces the overhead and delay of application management, ensures that application instantiation and termination can be dynamically adjusted when resource changes, and achieves more efficient network resource management and user experience optimization.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN112236989B_ABST
    Figure CN112236989B_ABST
Patent Text Reader

Abstract

A technique may include: receiving, by a mobile edge computing application manager provided on a mobile edge computing server near a radio access network, a mobile edge computing application standard from an external application controller, the mobile edge computing application standard including management rules for managing at least a portion of a life cycle of a mobile edge computing application; and storing the mobile edge computing application standard. In an example embodiment, a technique may also include: managing at least a portion of a life cycle of a mobile edge computing application based on the mobile edge computing application standard.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This specification relates to wireless communications. Background Art

[0002] A communication system may be a facility that enables communication between two or more nodes or devices, such as fixed or mobile communication devices. Signals may be carried on wired or wireless carriers.

[0003] An example of a cellular communication system is an architecture standardized by the Third Generation Partnership Project (3GPP). The latest development in this field is generally referred to as the Long Term Evolution (LTE) of the Universal Mobile Telecommunications System (UMTS) radio access technology. E-UTRA (Evolved UMTS Terrestrial Radio Access) is the air interface of the 3GPP Long Term Evolution (LTE) upgrade path for mobile networks. In LTE, a base station or access point (AP), referred to as an enhanced node AP (eNB), provides wireless access within a coverage area or cell. In LTE, a mobile device or mobile station is referred to as a user equipment (UE). LTE includes many improvements or developments.

[0004] 5G New Radio (NR) development is part of the ongoing mobile broadband evolution process to meet the needs of 5G, similar to the early evolution of 3G and 4G wireless networks. In addition, in addition to mobile broadband, 5G also targets emerging use cases. The goal of 5G is to provide a significant increase in wireless performance, which can include new levels of data rate, latency, reliability and security. 5G NR can also scale to effectively connect the massive Internet of Things (IoT) and can provide new types of mission-critical services. For example, ultra-reliable and low-latency communication (URLLC) equipment may require high reliability and very low latency. Summary of the invention

[0005] According to an example embodiment, a method includes: receiving, by a mobile edge computing application manager provided on a mobile edge computing server near a radio access network, a mobile edge computing application standard from an external application controller, the mobile edge computing application standard including management rules for managing at least a portion of a life cycle of a mobile edge computing application; and storing the mobile edge computing application standard.

[0006] According to an example embodiment, a device includes at least one processor and at least one memory including computer instructions, which when executed by the at least one processor cause the device to: receive mobile edge computing application standards from an external application controller through a mobile edge computing application manager provided on a mobile edge computing server near a radio access network, the mobile edge computing application standards including management rules for managing at least a portion of a life cycle of a mobile edge computing application; and store the mobile edge computing application standards.

[0007] According to an example embodiment, a non-transitory computer-readable storage medium includes instructions stored thereon, which when executed by at least one processor are configured to cause a computing system to perform the following method: receiving a mobile edge computing application standard from an external application controller through a mobile edge computing application manager provided on a mobile edge computing server close to a radio access network, the mobile edge computing application standard including management rules for managing at least a portion of a life cycle of a mobile edge computing application; and storing the mobile edge computing application standard.

[0008] According to an example embodiment, a method includes sending, by an external application controller, a proposed mobile edge computing application standard to a mobile edge computing application manager provided on a mobile edge computing server close to a radio access network, the proposed mobile edge computing application standard including management rules for managing at least a portion of a life cycle of a mobile edge computing application.

[0009] According to an example embodiment, a device includes at least one processor and at least one memory including computer instructions, which when executed by the at least one processor cause the device to: send, via an external application controller, a proposed mobile edge computing application standard to a mobile edge computing application manager provided on a mobile edge computing server close to a radio access network, the proposed mobile edge computing application standard including management rules for managing at least a portion of a life cycle of a mobile edge computing application.

[0010] A device includes at least one processor and at least one memory including computer instructions, which when executed by the at least one processor cause the device to: receive a proposed mobile edge computing application standard from an external application controller through a mobile edge computing application manager provided on a mobile edge computing server near a radio access network, the proposed mobile edge computing application standard including management rules for managing at least a portion of a life cycle of a mobile edge computing application; determine, through the mobile edge computing application manager, that the proposed mobile edge computing application standard is feasible; send, through the mobile edge computing application manager, a confirmation indicating that the proposed mobile edge computing application standard is feasible to the external application controller; and manage, through the mobile edge computing application manager, at least a portion of a life cycle of a mobile edge computing application based on the mobile edge computing application standard. According to an example embodiment, a method is provided.

[0011] The details of one or more examples of the embodiments are set forth in the accompanying drawings and the description below. Other features will be apparent from the description and drawings, and from the claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0012] Figure 1 is a block diagram of a wireless network according to an example embodiment.

[0013] Figure 2 is a diagram illustrating a system according to an example embodiment.

[0014] Figure 3 is a diagram illustrating a mobile edge computing application manager according to an example embodiment.

[0015] Figure 4 is a diagram illustrating MEC application standard negotiation according to an example embodiment.

[0016] Figure 5 is a diagram illustrating MEC application standard negotiation triggered based on MEC resource conditions detected by a MEC application manager according to an example embodiment.

[0017] Figure 6 is a flow diagram illustrating the operation of a mobile edge computing application manager according to an example embodiment.

[0018] Figure 7 is a flowchart illustrating the operation of an external application controller according to an example embodiment.

[0019] Figure 8 is a block diagram of a node or wireless station (eg, a base station / access point or a mobile station / user equipment / UE) according to an example embodiment. DETAILED DESCRIPTION

[0020] Figure 1 is a block diagram of a wireless network 130 according to an example embodiment. Figure 1 In a wireless network 130 of FIG. 1 , user equipment 131 , 132 , 133 , and 135 (also referred to as mobile stations (MS) or user equipment (UE)) may be connected (and communicate) with a base station (BS) 134 (also referred to as an access point (AP), an enhanced Node B (eNB), or a network node). At least a portion of the functionality of an access point (AP), a base station (BS), or an (e) Node B (eNB) may also be performed by any node, server, or host that may be operably coupled to a transceiver, such as a remote radio head. BS (or AP) 134 provides wireless coverage within cell 136 , including providing wireless coverage to user equipment 131 , 132 , 133 , and 135. Although only four user equipment are shown as being connected or attached to BS 134 , any number of user equipment may be provided. BS 134 is also connected to a core network 150 via an S1 interface 151 . This is just one simple example of a wireless network, and other wireless networks may be used.

[0021] User equipment (user terminal, user equipment (UE)) may be referred to as a portable computing device, which includes wireless mobile communication devices operating with or without a subscriber identity module (SIM), including but not limited to the following types of devices: as examples, mobile stations (MS), mobile phones, cell phones, smart phones, personal digital assistants (PDAs), handsets, devices using wireless modems (alarm or measurement devices, etc.), laptop and / or touch screen computers, tablet computers, tablet phones, game consoles, notebook computers and multimedia devices or any other wireless devices. It should be understood that user equipment may also be almost exclusively uplink-only devices, an example of which is a camera or video camera that loads images or video clips to a network.

[0022] In LTE (as an example), the core network 150 may be referred to as an evolved packet core (EPC), which may include a mobility management entity (MME) that may handle or assist in mobility / handover of user equipment between BSs, one or more gateways that may forward data and control signals between the BSs and a packet data network or the Internet, and other control functions or blocks.

[0023] In addition, by way of illustrative example, various example embodiments or techniques described herein may be applied to various types of user equipment or data service types, or may be applied to user equipment that may have multiple applications running thereon (which may have different data service types). New radio (5G) developments may support many different applications or many different data service types, such as, for example: machine type communications (MTC), enhanced machine type communications (eMTC), Internet of Things (IoT) and / or narrowband IoT user equipment, enhanced mobile broadband (eMBB), and ultra-reliable and low latency communications (URLLC).

[0024] IoT may refer to the growing group of objects that may have internet or network connectivity, such that these objects may send information to and receive information from other network devices. For example, many sensor-type applications or devices may monitor physical conditions or states and may, for example, send reports to a server or other network device when an event occurs. For example, machine-type communications (MTC or machine-to-machine communications) may be characterized by fully automated data generation, exchange, processing, and actuation between intelligent machines with or without human intervention. Enhanced mobile broadband (eMBB) may support much higher data rates than those currently available in LTE.

[0025] Ultra-Reliable and Low-Latency Communication (URLLC) is a new type of data service or new usage scenario that the new radio (5G) system may support. This enables emerging new applications and services such as industrial automation, autonomous driving, vehicle safety, e-health services, etc. By way of illustrative example, 3GPP aims to provide a 5G-capable network with the same performance as 10G. -5 The reliability corresponding to the block error rate (BLER) of 100% and the connectivity of U-plane (user / data plane) latency of up to 1 ms. Therefore, for example, URLLC user equipment / UE may require a much lower block error rate and low latency than other types of user equipment / UE (with or without high reliability at the same time). Therefore, for example, URLLC UE (or URLLC application on UE) may require shorter latency compared to eMBB UE (or eMBB application running on UE).

[0026] Various example embodiments may be applied to various wireless technologies or wireless networks, such as LTE, LTE-A, 5G, cmWave and / or mmWave band networks, IoT, MTC, eMTC, eMBB, URLLC, etc., or any other wireless network or wireless technology. These example networks, technologies, or data service types are provided as illustrative examples only.

[0027] As noted, 5G technology is expected to significantly increase data rates (or bandwidth) and / or reduce latency. However, many network, cloud or IT applications or services may often be run (or hosted) on a server that may be hundreds or even thousands of miles away from a UE or mobile subscriber. For example, such a large distance between a server hosting an application or service and a UE or mobile subscriber that may be receiving the service may significantly increase the latency experienced by the user and, for some applications, may also result in inefficient use of network resources.

[0028] Therefore, according to an example embodiment, mobile edge computing (MEC) is an emerging technology in the 5G era that enables cloud and IT services or applications to be provided near mobile subscribers. It allows the availability of cloud or application servers near the BS (e.g., MEC servers within or as part of the BS, MEC servers provided within (multiple) enclosures or (multiple) buildings where the BS device is located, or MEC servers very close to the BS (such as, for example, within about 10 to 15 meters from the BS device)).

[0029] For example, by providing applications (which may be referred to as MEC applications) on MEC servers, the end-to-end latency perceived by mobile users is thereby reduced using the MEC platform. For example, augmented reality (AR) / virtual reality (VR) applications or services provided to mobile users or UEs may require relatively low latency (e.g., 20ms), while AR / VR services with higher latency may cause VR sickness. Therefore, for example, providing AR / VR applications running on MEC servers near the BS can greatly reduce the latency experienced by the UE or mobile user. Many other applications may require low latency (and therefore, may benefit from providing services hosted on MEC servers near the BS), including, for example, vehicle Internet, autonomous driving, industrial control, rapidly shrinking Internet video games, etc.

[0030] Moreover, some types of applications can significantly reduce latency and bandwidth consumption by hosting the service or application on a MEC server near the BS. As an illustrative example, a video streaming service may deliver a 20MB viral video to 1,000 users, which will generate 20GB of network traffic over the Internet and other networks because the video is transmitted individually to each UE or mobile user. However, in an example embodiment, the video streaming service can provide a video streaming application (and a cached version of the viral video) on a MEC server near the BS, so as to significantly reduce network bandwidth and latency when delivering the video to those 1,000 UEs or mobile users, for example. Therefore, for example, in order to support services with very strict latency, and / or to more efficiently deliver content to multiple mobile users or UEs, it may be advantageous to move such an application or service closer to the mobile subscribers or UEs receiving such services. These are just some examples of services that can benefit from hosting their applications on a MEC server within a radio access network (RAN), such as near the BS, for example, closer to mobile end users of such services, such as UEs or mobile subscribers.

[0031] Thus, it can be seen that for some applications or services, it may be quite valuable to provide or host such applications or services on a MEC server near the BS based on proximity to mobile subscribers or UEs that may be receiving such services (e.g., based on reduced latency and / or more efficient use of network resources). In addition, due to the limited physical space within and / or near the BS enclosure or building (therefore, limiting the number of MEC servers that can be provided near the BS), and because the resources on such MEC servers (e.g., processing resources, memory, and other resources) are also quite limited, MEC server resources may be quite limited. Therefore, based on the demand for MEC applications (applications instantiated or provided on MEC servers near the BS) and the limited MEC server resources, a mobile network operator (MNO) may propose to host such external (e.g., third-party) applications (e.g., non-MNO applications) on (multiple) MEC servers in exchange for compensation (e.g., based on billing rates) from an external or third-party service provider that owns and / or controls such external applications or services.

[0032] According to an example embodiment, the MEC server may receive a request from an external service provider to instantiate its external (or third-party) application (or MEC application) on (multiple) MEC servers. The MEC server may then grant or deny the request to instantiate the application. Various messages may be sent back and forth between the external service provider or application owner (controlling the service or application) and the MEC server to allow the MEC server to instantiate the external application and / or scale (or increase) resources for such an application, and / or notify the external service provider that the MEC server cannot instantiate the application, etc. Therefore, this may generate a lot of overhead and latency between these entities.

[0033] MEC enables operators to open their radio access network (RAN) edge to authorized third parties (or external service providers), allowing them to flexibly and quickly deploy innovative applications and services to mobile subscribers, enterprises, and vertical segments. In an example embodiment, the MEC server can receive requests from external service providers via a CFS (Customer-Facing Services) portal, or receive requests for instantiation or termination of applications from UE applications, and decide to grant these requests.

[0034] However, this approach to MEC application management may not provide effective management of MEC applications, for example, when the MEC application may include external or third-party (e.g., non-MNO) applications hosted or instantiated on the MEC server. As mentioned, instantiating or terminating each application on the MEC server may require a large amount of signaling or message overhead, which may lead to an inefficient process. Moreover, although the application service provider (application owner or application controller) may know the conditions for instantiating or terminating its application on the MEC server, the application service provider (application owner) may not be able to access such information (e.g., billing rates, network conditions, availability of MEC resources, etc.). For example, the application owner (or application service provider) may want to deploy MEC applications at low cost and / or during specific network conditions. Therefore, although the MEC server can receive a request from an external (or third-party or non-MNO) application owner or application service provider via a CFS (customer-facing services) portal, or can receive a request to instantiate or terminate an application from a UE, the external (or third-party) application owner may not be able to determine the best time or timing for such application instantiation or termination, for example, because the external (e.g., third-party) application owner may not generally have access to all relevant information.

[0035] In another example, when there are idle or available MEC resources (e.g., at the MEC server), the MNO may want to guide or encourage external or third-party application owners to trigger or request instantiation of applications. However, the problem that arises is that MEC server resources may be very busy at times, while MEC server resources may be available or under-utilized at other times. Therefore, in order to allow the MNO to generate more revenue and allow external third-party application owners to request application instantiation at the MEC server when MEC resources are available and / or resource billing rates may be low. Similarly, for example, when MEC resources are very limited, it may be desirable to replace lower value (or lower priority) applications with higher value (or higher priority) applications at the MEC server.

[0036] As mentioned, there may be several issues that may arise in the context of MEC application management. One or more of these issues or topics may be solved or improved by the systems and / or techniques described herein, including the following example topics:

[0037] 1) For example, an application owner may want to deploy a MEC application based on specific conditions (such as a specific cost or (multiple) billing rates, time, etc.). The MEC server may receive a request via a CFS (Customer Facing Services) portal, or receive a request from a UE application to instantiate or terminate an application. However, in some cases, an external or third-party application owner may not be able to determine the best time to perform such application instantiation or operation at the MEC server (e.g., because the application owner may not have access to the MEC server's update conditions, and / or due to other restrictions).

[0038] 2) Idle MEC resources (e.g., where there are idle or available MEC resources) present underutilization of valuable MEC resources. As described herein, an MNO (or operator) or MEC application manager may want to guide / encourage third-party application owners to trigger or request application instantiation when MEC resources are idle or become available, e.g., to improve MEC resource utilization.

[0039] 3) Furthermore, limited MEC resource scenarios may occur. If the mobile network operator (MNO) or MEC server cannot change or adjust based on changing (e.g., increasing) demand for resources or limited MEC resource scenarios, the operator may not be able to obtain the maximum value for limited MEC resources.

[0040] Figure 2 is a diagram illustrating a system according to an example embodiment. Figure 2 As shown, the MEC server 208 is a mobile edge computing server and can be provided at the edge of a RAN (Radio Access Network) network (e.g., at or near a BS). The RAN may include one or more BSs, and / or may include a BS and one or more UEs. Figure 2 , the MEC server 208 may be located near the BS 134. As illustrative examples, providing the MEC server 208 (including one or more applications running thereon) near the BS 134 may include, for example, a MEC server 208 within or as part of the BS, a MEC server provided within (multiple) enclosures or (multiple) buildings where the BS device is located, or a MEC server very close to the BS (e.g., within about 10 to 15 meters from the BS device). Other examples of proximity may also be used. As mentioned above, by providing the MEC server (and any applications running thereon) near the BS and therefore near the UE or mobile subscriber, one or more advantages may be provided, such as allowing a service provider to deliver its services to mobile end users with low latency and / or in a more network efficient manner.

[0041] The MEC server 208 may also include one or more applications running or hosted on the MEC server 208, including, for example, a MEC application 214. MEC applications may include, for example, applications hosted or run on a MEC server (possibly near a BS and therefore relatively close to a UE or mobile subscriber). In an illustrative example embodiment, the MEC application 214 may include an external (or third-party or non-mobile network operator) application running on the MEC server 208. A mobile network operator (MNO) may operate a wireless network, including a BS, a core network 150, and the like. The MNO may allow external or third-party (non-MNO) applications to be hosted or run on the MEC server. For example, an external (or third-party) application may include a non-mobile network operator (non-MNO) application or an application owned and / or controlled by an external or third party (e.g., an application owned or controlled by an entity or company other than the MNO operating the mobile or wireless network). Some examples of MEC applications may include augmented reality / virtual reality (AR / VR) applications, video delivery services or applications, data collection applications, autonomous driving applications, social media applications, video game applications, factory automation applications, and the like. According to example embodiments, while the MNO may have one or more (e.g., telecommunications-related) applications running on a server (computer) at the BS 208, the MEC applications may include external or third-party (e.g., non-MNO) applications that the MNO may host or run on (multiple) MEC servers in exchange for compensation (based on a billing rate or resource billing rate) from a MEC application owner or MEC application controller. Thus, for example, by providing its MEC resources to external (or third-party) applications, the MNO may, for example, obtain revenue based on a lease or rent of the MEC resources, while the external application owner or controller may advantageously obtain resources that allow the application to run at a location near the BS, which may, for example, provide lower latency, more efficient network usage, or (multiple) other advantages to the UE. Various techniques are described herein that may provide improved MEC application management.

[0042] Moreover, if Figure 2As shown, a MEC application manager 210 may be provided, for example, on a MEC server 208 or at another storage location that may or may not be near the BS 134. The MEC application manager 210 may manage the operation and / or life cycle of one or more MEC applications 214. According to an example embodiment, a MEC application standard 212 may be provided for each of the one or more MEC applications. Thus, for example, the MEC application standard 212 may be provided to (or associated with) the MEC application 214. Each MEC application standard 212 may be stored on a MEC server, such as, for example, stored on the MEC server 208, or stored at another location, and / or stored on the same (or different) server where the MEC application manager 210 is stored. According to an example embodiment, the MEC application standard 212 may include management rules for managing at least a portion of the operation and / or life cycle of (multiple) associated applications. Thus, there may be one or more MEC applications associated with each stored MEC application standard 212. In an example embodiment, the MEC application manager 210 may manage or control the operation and / or life cycle of the MEC application(s) 214 based on the MEC application standards 212 associated with the MEC application 214 .

[0043] According to an example embodiment, managing at least a portion of the life cycle of an MEC application may include performing and / or determining whether to perform one or more of the following based on a comparison of the MEC application standard 212 with one or more conditions associated with the life cycle management of the MEC application 214: instantiating a mobile edge computing application; terminating a mobile edge computing application; expanding (e.g., increasing) resources allocated to the mobile edge computing application; and reducing (e.g., reducing) resources allocated to the mobile edge computing application. Thus, according to an example embodiment, some example phases or cycles for the life cycle of an application may include, for example, instantiation of an application, termination of an application, expansion and / or reduction of resources for the application. These are some illustrative examples, and the MEC application manager 210 may perform other functions or tasks based on the MEC application standard 212 to manage or control the MEC application 214.

[0044] Moreover, refer to Figure 2, the external (e.g., third-party or non-MNO) application controller 218 may be provided, for example, by an application owner or other entity associated with the MEC application 214 running or hosted on the MEC server 208. The external application controller 218 may be coupled to (or in communication with) the MEC server 208 via the network 216. Thus, according to an example embodiment, in order to improve the management of MEC applications, the external application controller 218 may determine and send to the MEC application manager 210 a proposed MEC application standard 212 for one or more MEC applications (e.g., such as for managing the MEC application 214). According to an example embodiment, the MEC application manager 210 may receive the proposed MEC application standard 212 from the external (e.g., third-party) application controller 218.

[0045] According to an example embodiment, a mobile edge computing (MEC) application manager 210 (e.g., provided on a server near a radio access network) may receive a MEC application standard 212 from an external application controller 218, the MEC application standard including management rules for managing at least a portion of a life cycle of a MEC application 214; and store the mobile edge computing application standard. Moreover, for example, the MEC application manager 210 may manage at least a portion of a life cycle of the MEC application 214 based on the MEC application standard 212.

[0046] In another example embodiment, the MEC application manager 210 may determine the feasibility of the proposed MEC application standard. If the proposed MEC application standard 212 is determined to be feasible, the MEC application manager 210 may store the MEC application standard 212, for example, in a database or other storage location, and may control or manage at least a portion of the operation and / or life cycle of the associated application(s) 214 based on the stored MEC application standard 212.

[0047] In an example embodiment, the MEC application manager 210 may determine the feasibility of the proposed MEC application standard, for example, based on: comparing one or more parameters of the proposed MEC application standard with one or more constraints associated with MEC application management; determining the feasibility of the proposed MEC application standard by one of the following: based on the comparison, determining that the proposed MEC application standard is not feasible based on a determination that one or more parameters of the proposed mobile edge computing application standard violate one or more constraints associated with mobile edge computing application management; and based on the comparison, determining that the proposed MEC application standard is feasible based on the fact that one or more parameters of the proposed MEC application standard do not violate one or more constraints associated with mobile edge computing application management.

[0048] Therefore, the MEC application manager 210 can, for example: receive a proposed MEC application standard from an external application controller 218 through a MEC application manager 210 provided on a MEC server close to a radio access network (e.g., near a BS), the proposed MEC application standard including (proposed) management rules for managing at least a portion of the life cycle of a MEC application; determine the feasibility of the proposed MEC application standard through the MEC application manager 210; and, for example, if the proposed MEC application standard is feasible, store the proposed MEC application standard in a database for use in managing MEC applications. If the proposed MEC application standard 212 is feasible, the MEC application manager 210 can also manage at least a portion of the life cycle of the MEC application 214 based on the proposed MEC application standard.

[0049] In the case where the MEC application manager 210 determines that the MEC application standard 212 is not feasible, a negotiation may be performed between the MEC application manager 210 and the external application controller 218 to agree on a feasible revised MEC application standard. For example, if the proposed MEC application standard is not feasible, the MEC application manager 210 may also perform the following operations: negotiate with the external application controller 218 through the MEC application manager 210 to agree on a feasible revised MEC application standard; store the revised MEC application standard in a database for use in managing the MEC application 214; store the revised MEC application standard; and manage at least a portion of the life cycle of the MEC application 214 through the MEC application manager 210 based on the revised MEC application standard.

[0050] In an example embodiment, for example, if the proposed MEC application standard is not feasible, negotiating a revised MEC application standard may include the following: sending a revised MEC application standard to the external application controller 218 through the MEC application manager 210, the revised MEC application standard including at least one MEC application standard parameter different from the proposed MEC application standard, and the at least one MEC application annotates the parameter so that the revised MEC application standard is feasible; receiving confirmation of the revised MEC application standard from the external application controller 218 through the MEC application manager 210 (e.g., acknowledging or confirming that the revised MEC application standard is acceptable). Then, the MEC application manager 210 can manage at least a portion of the life cycle of the MEC application 214 based on the revised MEC application standard.

[0051] In an example embodiment, one or more conditions may occur or be detected by the MEC application manager 210, where it is desired that one or more external application controllers request the use of MEC resources for (multiple) external applications, such as to request to instantiate an application and / or increase the resources of such applications running on the MEC server. For example, the MEC application manager 210 may detect idle or available resources (e.g., processing, memory, or other MEC resources, or idle MEC resources greater than a threshold) on the (multiple) MEC server 208, or detect that the billing rate of the MEC resources is less than a threshold, or detect that the demand for the MEC resources has decreased or is less than a threshold. In this case, for example, the MEC application manager 210 may send information (e.g., a request or proposal or suggestion, such as a proposed MEC application standard) to the external application controller 218 to prompt the external application controller 218 to send the (e.g., proposed) MEC application standard 212 to the MEC application manager 210. In this example, the MEC application manager 210 may attempt to promote the use of idle or available MEC resources on one or more MEC servers by sending an implicit proposed MEC application standard to the external application controller 218. In this case, the proposed MEC application standard 212 sent by the external application controller 218 may be sent in response to receiving the proposed MEC application standard (e.g., the proposed MEC application standard may be sent in response to a request or hint from, for example, the MEC application manager 210). In other example embodiments, the proposed MEC application standard may be sent by the external application controller 218, for example, without any hint or prompt from the MEC application manager 210.

[0052] According to an example embodiment, the MEC application criteria 212 may include an application identifier that identifies the MEC application; and values ​​for one or more parameters for managing at least a portion of the life cycle of the MEC application, including action criteria and associated actions to be performed for the MEC application if the action criteria are met.

[0053] According to an example embodiment, the MEC application standard 212 may include at least one of the following: a first threshold value for determining one or more conditions for instantiating a MEC application; a second threshold value for determining one or more conditions for expanding or increasing resources for a MEC application; a third threshold value for determining one or more conditions for reducing or decreasing resources allocated to a MEC application; and a fourth threshold value for determining one or more conditions for terminating a MEC application.

[0054] For example, the MEC application standard 212 may indicate four (or other numbers) of different billing rate thresholds. For example, the MEC application standard may indicate that: if the MEC resource billing rate is less than the first billing rate threshold, then the MEC application manager 210 is requested to instantiate the corresponding application; if the MEC resource billing rate is less than the second billing rate threshold, then the MEC application manager 210 is requested to increase the resources for the corresponding application that has been instantiated; if the MEC resource billing rate is greater than the third billing rate threshold, then the MEC application manager 210 is requested to reduce the resources of the corresponding application; and if the MEC resource billing rate is greater than the fourth billing rate threshold, then the MEC application manager 210 is requested to terminate the corresponding application that has been instantiated.

[0055] Thus, the external application controller 218 may be able to indicate within the MEC application standard 212 one or more actions to be performed for the application and the criteria or conditions under which such actions should occur (e.g., without any other signaling or communication between the external application controller 218 and the MEC application manager 210). In this way, although the external application controller 218 may not have access to various network conditions, current rates, or resource availability at the MEC server, the external application controller is able to determine the requested actions for its (multiple) applications and under what conditions or criteria such actions are performed, and then communicate this information (e.g., in the form of MEC application standards) to the MEC application manager 210, so that the MEC application manager 210 can control or manage operations and / or control or manage at least a portion of the life cycle of the application based on the (approved or feasible) MEC application standard 212.

[0056] According to an example embodiment, the MEC application standard 212 may include at least one of the following, for example: a first billing rate threshold, used to determine the billing rate range for the MEC application manager to be requested to instantiate the MEC application; a second billing rate threshold, used to determine the billing rate range for the MEC application manager to be requested to add resources for the MEC application; a third billing rate threshold, used to determine the billing rate range for the MEC application manager to be requested to reduce the resources of the MEC application; and, a fourth threshold, used to determine one or more conditions under which the MEC application manager is requested to terminate the MEC application.

[0057] According to an example embodiment, the MEC application standard 212 may include values ​​for one or more of the following parameters, which are used to manage at least a portion of the life cycle of the MEC application 214: a valid timer parameter, identifying a time period during which the MEC application standard is valid; a billing rate threshold, used to determine whether to perform one or more actions or a period of life cycle management of the MEC application; memory resources, processing resources, or bandwidth resources requested for the MEC application; the amount of bandwidth resources requested for the MEC application; the requested performance of the MEC application related to at least one of latency, minimum bandwidth or data throughput, or quality of service; and Radio Network Information Service (RNIS) information related to the user equipment or the radio access bearer of the user equipment.

[0058] According to an example embodiment, the MEC application standard 212 may specify network conditions (e.g., a billing rate less than a first threshold or greater than a third threshold, or a threshold amount of MEC resources are idle or available, the demand for MEC resources is less than a threshold or greater than a threshold, or the performance of the MEC server or (multiple) MEC server resources is higher or lower than a threshold, ...) and associated actions to be performed for the MEC application when the network conditions are met (e.g., instantiating the application, adding or reducing resources and / or terminating the application or other actions), and wherein at least a portion of managing the life cycle of the MEC application may include, for example: determining that the network condition is met; performing associated actions for the MEC application based on the network condition being met, wherein the associated actions include one of the following: instantiating the MEC application, terminating the MEC application, expanding the resources of the MEC application, and reducing the resources of the MEC application.

[0059] Moreover, the MEC application manager 210 may detect changes in one or more network conditions (e.g., an increase in available MEC resources, a decrease in available MEC resources below a threshold, a billing rate less than a threshold or greater than a threshold, ...). For example, the MEC application manager 210 may detect changes in network conditions associated with at least one of a change in the availability of MEC server resources or a change in demand for MEC server resources. In another example embodiment, detecting a change in network conditions may include, for example, at least one of: detecting an increase or decrease in MEC server resources; detecting a change in (multiple) billing rates to be billed for MEC applications; and detecting a change in demand for MEC server resources based on resource requests for other MEC applications.

[0060] In response to detecting such a change in (multiple) network conditions, the MEC application manager may send a revised MEC application standard to the external application controller 218 based on the detected change in network conditions. For example, the initial MEC application standard 212 from the external application controller 218 was (at least initially) feasible and was therefore accepted by the MEC application manager to provide a first (e.g., higher) level of MEC resources for the application at a first (e.g., lower) billing rate. However, due to an increase in demand or requests for MEC server resources and / or an increase in the billing rate for MEC server resources, the initial MEC application standard is no longer feasible (e.g., no longer possible and / or no longer desired for the MEC application manager), and / or is now less beneficial than a proposed MEC application standard received from or negotiated for other applications, and / or is of lower priority or value than a recently received MEC application standard proposed by another application.

[0061] Thus, in order to allocate more MEC resources for higher value (e.g., higher priority and / or higher paid) applications, the MEC application manager 210 may send a message to the external application controller 218 to terminate (or previously agreed upon) initial MEC application criteria for low value (e.g., low priority applications or lower paid) applications (and / or renegotiate to provide MEC resources at a higher billing rate or cost by providing revised MEC application criteria), such that, for example, this may free up those MEC resources that may be allocated for instantiation (and / or resource addition) of higher value (e.g., higher priority or higher paid) MEC applications and / or, for example, increase rental fee revenue for MEC resources to the MNO. Thus, for example, the value of an application may be determined by many different criteria, such as the priority of the application and / or the rate at which the application is charged for MEC resources (e.g., a payment rate or billing rate), or other criteria. Thus, for example, when conditions change, the MEC application manager can take steps to reallocate MEC resources to higher value applications, or negotiate revised MEC application standards (e.g., at a higher billing rate) with current applications or external application controllers that previously allocated such MEC resources.

[0062] By way of illustrative example, a driving automation (autonomous driving) application (e.g., to assist or assist an autonomous car or vehicle) may be considered a higher priority than a video streaming application, e.g., because public safety has a higher priority. Also, higher value applications may also be such applications, e.g., to increase revenues for a mobile network operator (MNO) based on leasing or renting of limited MEC resources near the RAN (e.g., near the BS), a higher billing rate for MEC resources is available (from the same or different MEC application controller or application).

[0063] Various example embodiments may provide dynamic third-party MEC application management. For example, the MEC application standard 212 generated by the application owner may define context-dependent MEC application management rules for MEC application management. The MEC application standard 212 may be downloaded to the MEC server by the MEC application manager 210 for dynamic MEC application management. According to an example embodiment, the MEC application manager 210 may be provided on, for example, the MEC server 208, for example, to manage or control MEC applications based on the corresponding MEC application standard 212. In an example embodiment, the MEC application manager 210 may determine the feasibility of the MEC application standard proposed by the application owner. If the proposed MEC application standard is not feasible (or not approved by the MEC application manager 210), a MEC application standard negotiation is triggered between the application owner (or an external application controller 218 on behalf of the application owner) and the MEC application manager 210 until a revised (and feasible or approved) MEC application standard is agreed upon between the two parties (e.g., based on the knowledge of the MEC application manager 210 and the application owner or the external application controller 218).

[0064] The MEC application manager 210 may also guide the application owner or external application controller 218 by performing appropriate application management operations. For example, in a MEC resource idle scenario (e.g., when there are idle or available MEC server resources), the MEC application manager 210 on the MEC server 208 may start or initiate a negotiation with the external application controller 218 (e.g., by sending a proposed or implied MEC application standard) to trigger application instantiation for revenue generation by the MNO.

[0065] In a MEC resource-limited scenario (e.g., when MEC server resources are scarce or unavailable), the MEC application manager 210 may identify applications with lower (or lowest) value and trigger a negotiation with a third-party application owner (e.g., an external application controller) of (multiple) these low-value applications to dynamically replace such applications with high-value applications. For example, higher-value applications may include, for example, applications that may have a higher priority and / or applications that provide or pay a higher billing rate.

[0066] Figure 3 is a diagram illustrating a mobile edge computing application manager according to an example embodiment. Figure 3As shown, the MEC application manager 210 may include, for example, an application standards processor 310, an application standards manager 312, and an application management advisor 314. The MEC application manager 210 may be coupled to a database 316 that may store one or more MEC application standards. For example, MEC application standards may be stored for each of one or more MEC applications. As mentioned, the MEC application manager 210 may manage or control (multiple) MEC applications based on corresponding MEC application standards that may be stored, for example, in the database 316 or other locations.

[0067] like Figure 3 As shown, MEC application standard 212A may be provided to manage or control MEC applications with application ID1; MEC application standard 212B may be provided to manage or control MEC applications with application ID2; and MEC application standard 212C may be provided to manage or control MEC applications with application ID3.

[0068] Moreover, the database 316 may store other information, including some provisioning information for the MEC application manager 210, such as (multiple) thresholds for MEC resource idle thresholds (e.g., indicating that at least a threshold percentage of MEC resources are idle or available) and / or MEC resource limited thresholds (e.g., indicating that less than a threshold amount or percentage of MEC resources are available or idle). When MEC resources exceed any of these thresholds, this may cause or trigger the MEC application manager to take steps to better utilize the MEC resources as appropriate.

[0069] Application Criteria Manager 312 (e.g., feasibility checks and negotiations)

[0070] The application standards manager 312 interacts with the application owner (e.g., external application controller 218), for example, through a CFS portal or a UE application, to manage MEC applications based on the MEC application standards 212 defined by the application owner. Once the MEC application standards are downloaded from the external application controller (or other device or program) to the MEC server 208, the application standards manager 312 determines or checks the feasibility of the MEC application standards 212 defined by the application owner based on its own knowledge. If the received MEC application standards 212 are not feasible, the application standards manager 312 can trigger (and execute) MEC application standards negotiation between the MEC application manager 210 (e.g., application standards manager 312) and the external application controller 218 or the application owner until, for example, a feasible MEC application standard is determined or agreed upon for the application based on the knowledge of the MEC application manager 210 (or its application standards manager 312) and the external application controller 218. For example, once the parties finally determine or agree, the MEC application standards 212 of the application can be saved or stored in the database 316.

[0071] In an example embodiment, the MEC application standard may include a validity timer parameter indicating a time period during which the MEC application standard is valid. Moreover, for example, if the MEC application standard does not include a validity timer parameter, the MEC application standard is valid until the new MEC application standard is approved as feasible by the application standard manager 312 of the MEC application manager 210. If the validity timer parameter is included in the MEC application standard 212, the application standard manager 312 tracks the verification window (or the time period during which the MEC application standard is valid). That is, if the MEC application standard 212 expires, the application standard manager 312 can then remove or delete such MEC application standard from the database 316.

[0072] Application standard processor 310 (e.g., management or control of applications based on MEC application standards)

[0073] The application criteria processor 310 is responsible for controlling or managing the MEC application 214 based on the corresponding MEC application criteria 212 (eg, 212A, 212B, or 212C) stored in the database 316. Some illustrative examples are provided below, and other examples and parameters may be used.

[0074] Referring to Table 1 below, the MEC application standard 212 may provide MEC application management rules for a specific application identified by an application ID / name. In this illustrative example, an MEC application standard for a third-party application #1 (third-party APP #1) is shown. The MEC application standard may be (or may include) a list of one or more rules that describe the operations to be performed on the application when certain conditions exist or are detected. For example, the MEC application standard 212 may include an action standard that describes a standard or condition and a corresponding action to be performed for the application when the action standard (or condition) is met. Table 1 below illustrates four very simple examples of action standards and the associated actions to be performed when these standards are met or satisfied. (Although it should be understood that the action standards in the MEC application standard may contain various parameters and conditions, and the corresponding actions may include more actions than shown in Table 1). For example, as shown in Table 1, if the billing rate is less than threshold #1, the application is instantiated using the default resource request; when the billing rate is less than threshold #2, the application is expanded; when the billing rate is greater than threshold #3, the application is reduced; and when the billing rate is greater than threshold #4, the application is terminated.

[0075]

[0076] Table 1

[0077] NOTE: In the illustrative example embodiment:

[0078] 1. The billing rate relationship of thresholds #1, #2, #3, and #4 is shown below:

[0079] Threshold #2 < Threshold #1 < Threshold #3 < Threshold #4

[0080] 2. Optionally, a validity timer parameter may be carried by (or included as part of) the MEC application standard 212 to indicate that the MEC application standard expires. 2. Furthermore, if, for example, no validity timer parameter is carried, the MEC application standard is valid (e.g. and approved or determined to be feasible) until a new MEC application standard for the application is received. The "MEC application standard" may be carried as an optional parameter in an existing message from the CFS portal / UE application (e.g., such as an application context creation message, an application context deletion message, etc.), or as a separate new message, such as a MEC application standard message.

[0081] According to an example embodiment, once the MEC application standard 212 is (e.g., approved or determined to be feasible and) saved in the database 316 (or other location), the application standard processor 310 of the MEC application manager 210 will be triggered and then control or manage (multiple) corresponding applications based on the received MEC application standard.

[0082] Example steps for applying the standard processor 310:

[0083] Example step 1: Based on the received MEC application criteria, determine whether the current network conditions (such as business or charging rules, or other rules or parameters) meet the criteria. If so, perform (multiple) corresponding application operations (application instantiation, application termination, resource scaling, etc.) accordingly.

[0084] Example Step 2: Monitor network conditions (as they may change) and perform relevant actions based on MEC application criteria, such as performing new actions on applications when network conditions change. For example, if the billing rate exceeds the acceptable billing rate (e.g., the billing rate is greater than threshold #4), terminate the relevant application. Alternatively, once the billing rate meets the criteria (e.g., the billing rate is less than threshold #1), instantiate the application.

[0085] Application management advisor 314 (e.g., adjust when resource availability changes, such as initiating or prompting third-party resource usage for MEC idle resource scenarios, or adjust for MEC limited resource scenarios).

[0086] The application management advisor 314 may be responsible for guiding or prompting the application owner (or external application controller 318) by performing appropriate application management operations. Moreover, for example, in a MEC resource idle scenario, the application management advisor 314 of the MEC application manager on the MEC server 208 may initiate a negotiation with the application owner (or external application controller 218) (e.g., by sending a proposed MEC application standard) to trigger application instantiation for revenue generation. In a MEC resource limited scenario, the application management advisor 314 of the MEC application manager 210 on the MEC server 208 may identify applications with lower value and trigger a negotiation with (multiple) third-party application owners (or external application controllers 218) of such low-value applications to dynamically replace such applications with applications of higher value (e.g., higher priority applications or applications with higher billing rates). Thus, once necessary, when a MEC limited resource situation occurs, the application management advisor 314 may trigger a third-party application operation negotiation with the application owner or external application controller 218 to agree on an updated or revised MEC application standard, or the MEC resources may be reallocated to a higher value MEC application.

[0087] MEC application standard negotiation

[0088] According to an example embodiment, the MEC application manager 210 may check or determine the feasibility of the MEC application standard 212 defined by the application owner based on its own knowledge. If the MEC application standard is not feasible, a new MEC application standard negotiation may be triggered between the application owner (or external application controller 218) and the MEC application manager 210 until a revised MEC application standard is agreed upon between the parties, or until the effort is abandoned.

[0089] Upon receiving a message including (e.g., proposed) MEC application standards 212 from an external application controller 218 or application owner, for example, via a CFS portal or UE application, the MEC application manager 210 may check or determine whether the proposed MEC application standards are feasible, for example based on its own intelligence, and then save it to the database 316 for execution. The intelligence / knowledge of the MEC application manager 210 that may be used to determine the feasibility of the MEC application standards may include, but is not limited to:

[0090] -Historical network condition data.

[0091] - Input from other network elements (such as the 5G core network)

[0092] - Local provisions of the MEC application manager 210, such as those stored in the database 316, such as a range of acceptable MEC application standards defined by the operator (MNO), such as for one or more parameters (such as billing rates at different times of the day or different days of the week, size ranges or other information of resource allocations for different types of applications, thresholds for MEC idle resource conditions or thresholds for MEC limited resource conditions).

[0093] For example, if the billing rate standard included in the proposed MEC application standard is very rare, or has not occurred at all in the last 2 months, then the MEC application manager 210 may consider such proposed MEC application standard to be infeasible. For example, if the proposed MEC application standard requests to instantiate a video streaming application at a low billing rate during a 4-hour period (e.g., 6pm to 10pm), but only a high billing rate is available for 98% of the specified period in the last 2 months. Therefore, the MEC application manager 210 may reject the requested or proposed MEC application standard based on the historical network billing rates of the last 2 months (e.g., the requested MEC resources, and the requested time and billing rate of the video streaming application are not feasible or feasible, such as based on the historical billing rates of these times).

[0094] Figure 4 is a diagram illustrating MEC application standard negotiation according to an example embodiment. Figure 4 As shown, the external application controller 218 (e.g., acting on behalf of the application owner) communicates with the MEC application manager 210. In 410, the MEC application manager 210 receives the proposed MEC application standard from the external (e.g., third-party) application controller 218. The MEC application manager 210 can then determine the feasibility of the proposed MEC application standard. If the proposed MEC application standard is approved by the MEC application manager 210 (e.g., approved as feasible), then Figure 4 The process may jump down and perform operations 416, 418, and 420 for the proposed MEC application standard.

[0095] In 412, the MEC application manager may determine that the proposed MEC application standard is not feasible (not feasible). In 414, the MEC application manager 210 sends a revised MEC application standard, which includes at least one parameter that may be different from the proposed MEC application standard (from the perspective or point of view of the MEC application manager 210 or the MNO), and the at least one parameter makes the revised MEC application standard feasible or feasible. For example, for the revised MEC application standard, a higher billing rate may be indicated for the requested service, or slightly different times may be indicated (e.g., 3 to 7 p.m. at a lower billing rate, rather than the requested 6 p.m. to 10 p.m., because, for example, the higher billing rate is usually applied from 7 p.m. to 10 p.m.), or a smaller amount of MEC resources may be allocated to the application, etc. In 416, if the revised MEC application standard is acceptable to the external application controller 218, the external application controller 218 can confirm or acknowledge the revised MEC application standard (e.g., indicate that the revised MEC application standard has been accepted by the external application controller 218 or the application owner).

[0096] In 418, the MEC application manager 210 may then control or manage at least a portion of the life cycle of the corresponding application based on the revised MEC application standard (e.g., application instantiation, termination, or resource addition or reduction of the application, such as based on various network conditions or thresholds that may be indicated by the MEC application standard). Furthermore, if a validity timer parameter is included in the MEC application standard (e.g., indicating a time period during which the approved or agreed-upon MEC application standard is valid), the MEC application manager 210 may first confirm that the limited time period of the MEC application standard has not expired before managing the application according to the MEC application standard.

[0097] In addition, at 420, the MEC application manager may generate and provide an application management report to the external application controller 218, such as identifying the application (e.g., an application identifier) ​​and including information describing the control or management of the application in accordance with the approved or feasible MEC application standard. For example, the application management report may include information such as indicating the operations performed, the time or duration of performing each operation, the amount of MEC server resources allocated to the application, various billing rates applied for the time period during which the application runs on the MEC server, etc.

[0098] MEC application standards may include or may be based on various parameters, such as charging rates, types or quantities of resources, time periods, etc. These are just some example parameters of MEC application standards. For example, by indicating the expected or requested charging rate, this may, for example, allow application owners to maintain profitable services. However, MEC application standards may include various attributes or parameters as some example attributes or parameters, such as, for example, the time application of application running (possibly including start time, running duration, end time), bandwidth, latency, computing resources (such as CPU), memory and disk space or special permission requests, such as real-time network and radio information (such as Radio Network Information Service (RNIS) provided by, for example, MEC server) provided by telecommunications infrastructure, etc. For example, RNIS information may include parameters or information about UE context and established E-UTRAN radio access bearer (E-RAB), such as QoS (quality of service), cell ID (cell identifier) ​​of E-RAB (radio access bearer), identification of UE associated logical signaling connection, etc. RNIS information may also indicate when a modification to the E-RAB or UE context occurs, or when the E-RAB is released. This information is based on 3GPP radio network layer signaling messages such as S1 Application Protocol (S1-AP), X2 Application Protocol (X2-AP), and Radio Resource Control (RRC).

[0099] Below are some examples of MEC application standards and examples of feasibility checks (feasibility determinations) of such MEC application standards.

[0100] Example #1 IoT (Internet of Things) Data Analysis

[0101] An IoT company (e.g., for smart city management) may need to collect and analyze data from sensors deployed in certain specific areas of the city on a daily basis. Thus, in this example, an external application controller 218 acting on behalf of the city may send MEC application standards to the MEC application manager 210, such as for instantiation and operation of its data collection application to run on the MEC server 208. The MEC application standards for such an IoT data collection application may include (e.g., possibly among other parameters):

[0102]

[0103] In this case, the application owner does not specify the time when the application runs, and there is always (or at least usually) idle time every day on the MEC platform or MEC server 208, so the MEC application standard is feasible and accepted by the MEC application manager 210.

[0104] Example #2 AR / VR (Augmented Reality / Virtual Reality) Services.

[0105] The AR / VR service owner, for example, via its external application controller 218, can send the following recommended MEC application standards (see Figure 4 414) to request to run or instantiate its AR / VR application during a specific time window (e.g., May 18, 10:00-12:00), and also requires a large amount of MEC resources on the MEC platform or MEC server 208.

[0106]

[0107] The MEC application manager 210 may determine or check the feasibility of such a proposed MEC application standard. In this case, the MEC server (e.g., MEC platform) is unable to provide such a large MEC resource during the time period (e.g., due to other resource commitments of the MEC server 208). However, the MEC application manager 210 may determine a feasible alternative or slightly different MEC application standard. Therefore, in this case, the MEC application manager may send a revised MEC application standard, which may include or indicate one or more feasible possibilities for time and / or resources for the application. Therefore, for example, the revised MEC application standard may indicate the following options or possibilities for the application:

[0108] Option #1: Smaller MEC resources during the same time period;

[0109] Option #2: Use the same (larger) MEC resources in (multiple) different time periods when MEC resources are more available, such as 8:00-10:00 or 9:00-11:00.

[0110] Example #3 Requesting Radio Network Information Service (RNIS) permission in MEC application standards

[0111] In this example, the RNIS parameters are added to the action criteria or action field of the MEC application criteria. However, the MEC application criteria feasibility check finds that the application does not have permission to request one of these RNIS parameters. Therefore, the MEC application manager 210 will reject the MEC application criteria (e.g., because the application does not have permission to request MEC resources). The MEC application manager 210 may reject the MEC application criteria with a reason indicated in the response (e.g., no permission or no permission for RNIS parameters).

[0112] Similarly, a proposed MEC application standard may be rejected (e.g., as infeasible) if the requester or application does not have permission for the requested service, such as where the requester has requested resources, application operating hours, quality of service, or other parameters for which the MNO or MEC application manager 210 has not authorized the application.

[0113] Figure 5 is a diagram illustrating a MEC application standard negotiation triggered based on a MEC resource condition detected by a MEC application manager according to an example embodiment. In 508, the MEC application manager 210 may detect a MEC resource condition or scenario. For example, the MEC application manager 210 may detect one of a plurality of MEC resource conditions that may require or cause the MEC application manager 210 to make or request certain changes to MEC resources or MEC application standards. In 508A, the MEC application manager 210 may detect a MEC idle condition, such as one in which the number of idle or available MEC resources is greater than threshold #1. As another example, in 508B, the MEC application manager 210 may detect a MEC limited resource condition, such as one in which the number of idle or available MEC resources is less than threshold #2.

[0114] In 510, the MEC application manager 210 may send the proposed MEC application standard based on the detected MEC resource condition. For example, if the MEC idle resource condition is detected in 508A, the proposed MEC application standard in 510 may indicate a lower MEC resource billing rate to prompt the external application controller to approve the proposed MEC application, or send the proposed MEC application standard (not in Figure 5 ). Therefore, MEC-triggered negotiation may be performed to prompt or cause the external application controller 218 to request instantiation of an application or addition of resources in order to utilize idle MEC resources.

[0115] In another example embodiment, the MEC application manager 210 may detect a MEC limited resource condition in 508B. In this case, in 510, the MEC application manager 210 may send a proposed MEC application standard that may provide, for example, a higher MEC resource billing rate, an indication of a lower amount of resources allocated at the same billing rate, or other adjustments or changes to a previously agreed-upon MEC application standard based on the detected MEC limited resource condition. Thus, the MEC application standard proposed in 510 may be the beginning of a renegotiation of the MEC application standard due to fewer MEC resources now available and / or increased demand for MEC resources, etc. Although not in Figure 5As shown in , alternatively, the MEC application manager 210 may send an application termination indication in 510 to indicate that the application is being terminated and the resources allocated to the application will be reallocated to another (e.g., higher value) application. In either case (in response to the proposed MEC application standard or in response to an indication that the application will be terminated), in 512, the external application controller 218 may send the proposed MEC application standard to the MEC application manager 210, or may confirm that the proposed MEC application standard is acceptable. In 514, the MEC application manager 210 may confirm that the proposed MEC application standard is acceptable or approved. In 516, the MEC application manager 210 may then control or manage the operation of the application (e.g., application instantiation, termination, addition or reduction of resources) based on the approved or agreed-upon MEC application standard.

[0116] Use cases for dynamic third-party MEC application management

[0117] Assume that sharingvideo is a video sharing website. It rents out MEC server resources to deploy its own MEC video application to provide video services at the edge of the network (e.g., at the MEC server 208 near the RAN or BS) to obtain better user experience and high throughput. In order to ensure that this part of the business can be profitable, sharingvideo can define MEC application standards (or policies) to define the operation or management of its MEC video application, as follows:

[0118] The MEC video application is instantiated only in the scenario where the MEC billing rate is lower than threshold #1.

[0119] If the MEC billing rate is higher than threshold #1, the MEC video application on the MEC server is terminated.

[0120] Note: In this example, threshold #1 here is a baseline to ensure that its MEC video application is sufficiently profitable, such as achieving a 20% profit margin.

[0121] To pursue more revenue by taking advantage of MEC low billing rate time windows (e.g. during certain hours of the day), it can also define the following policies:

[0122] When the billing rate is lower than threshold #2, add MEC video applications (or increase MEC resources).

[0123] Once the policy (e.g., the proposed MEC application standard) is downloaded to the MEC application manager 210, the MEC application manager 210 can determine or check the feasibility of the above policy or MEC application standard based on its own knowledge. If the policy or the proposed MEC application standard is not feasible, a MEC application standard negotiation is triggered between the application owner (or external application controller 218) and the MEC application manager 210 until both parties agree on the MEC application standard for the application.

[0124] For example, in some scenarios (e.g., MEC idle resource conditions), in order to pursue optimal (or at least improved) MEC resource usage and generate more revenue for the operator (MNO), the MEC application manager 210 will detect the MEC idle resource scenario and will cause or trigger a negotiation with the application owner (in this example, it is the sharingvideo website) with a lower billing rate proposal, for example, via the external application controller 218. Due to the low billing rate proposal, this can prompt or trigger the application owner or the external application controller 218 to request instantiation or addition (increase) resources for its MEC video application (e.g., via sending a confirmation or sending the proposed MEC application standard).

[0125] Example Technology Benefits:

[0126] Various example embodiments of MEC application management may provide one or more technical advantages, such as, for example:

[0127] 1) Application owners can define policies for MEC application operations such as one or more various conditions under which various operations or application phases will be performed, such as, for example, instantiation, termination, expansion of resources, and reduction of resources. This allows external or third-party application owners (e.g., through their external application controllers) to indicate various conditions (e.g., acceptable billing rates for various operations, specific times of the day, requesting a specific amount of resources, or requesting specific performance), such as wishing to instantiate, add, reduce, or terminate their applications without requiring additional signaling or messages (or at least reducing the amount of signaling or messages) between the MEC server (or MEC application manager 210) and the external application controller or application owner. Therefore, the method can provide improved performance of external applications on the MEC server (e.g., based on conditions or instructions provided by the external application controller).

[0128] 2) For example, since the MEC application manager 210 can control or manage the operation of the application based on the received and approved MEC application standards, additional query signaling or messages between the MEC server 208 (e.g., the MEC application manager 210) and the third-party application owner (e.g., the external application controller 218) can be significantly reduced.

[0129] 3) This enables MEC applications to run or operate in scenarios or according to conditions defined or specified by the application owner (or an external application controller that can act on behalf of the application owner), which from the application owner's perspective can, for example, provide improved application operation, such as instantiating and / or adding (multiple) of its applications under its preferred conditions (e.g., low cost scenarios), at certain times when application demand exceeds a threshold, under certain network conditions, and similarly, under what conditions the application owner or external application controller 218 wants to request scaling down or terminating the application (e.g., during certain time periods or during high billing rates).

[0130] 4) If the proposed MEC application standard from the application owner or external application controller is not feasible (such as, as an example, when the requested billing rate does not occur during the indicated time period of the instantiated application, this may cause or trigger a negotiation to determine or agree on a revised MEC application standard for managing the operation of the application. For example, as part of the negotiation, the MEC application manager 210 may send a feasible or possible revised MEC application standard, which may be approved by the external application controller 218. If the revised MEC application standard is not acceptable to the external application controller 218, the external application controller may send a second proposed MEC application standard to the MEC application manager 210 or MEC server 208, and the negotiation may continue until both parties have agreed on a MEC application standard (or until the negotiation is abandoned by one or both parties).

[0131] 5) Techniques are also provided that allow the MEC application manager to respond to specific conditions or changes in conditions in order to provide improved utilization of MEC resources. Example conditions may include, for example: 1) MEC resource idle or available or idle MEC resource scenarios; in this case, the MEC application manager 210 can send an implied or proposed MEC application standard to prompt the external application controller to provide confirmation or negotiate the proposed MEC application standard or send back the proposed MEC application standard; and, 2) limited (or scarce) MEC resource scenarios, where there are few (if any) MEC resources, and the MEC application can reallocate some (e.g., previously allocated) MEC resources to higher value applications and / or can renegotiate MEC application standards for low-value applications to obtain greater value (e.g., higher billing rates) for certain MEC resources. Therefore, in limited MEC resource scenarios, (e.g., low-value) applications can be terminated in favor of higher-value applications. Or, alternatively, rather than simply terminating low-value applications in situations of limited or scarce MEC resources, a renegotiation may be performed between the MEC application manager 210 and the external application controller 218 in an attempt to agree upon revised MEC application standards (e.g., possibly including higher billing rates to reflect the current higher demand for MEC resources. This dynamic approach to MEC application management may allow the system to adapt to different or changing conditions and may, for example, provide techniques for maximizing (or at least improving) MEC resource usage (e.g., during idle MEC resource situations) while adapting to obtain more value (e.g., by running higher priority applications or running applications that are approved to run at higher billing rates), such as during limited MEC resource situations.

[0132] Some example embodiments are now described.

[0133] Example 1. Figure 6 6 is a flow chart illustrating the operation of a mobile edge computing application manager according to an example embodiment. Operation 610 includes: receiving a mobile edge computing application standard from an external application controller by a mobile edge computing application manager provided on a mobile edge computing server near a radio access network, the mobile edge computing application standard including management rules for managing at least a portion of a life cycle of a mobile edge computing application. Moreover, operation 620 includes: storing the mobile edge computing application standard.

[0134] Example 2. An example embodiment of the method according to Example 1, and further comprising: managing at least a portion of a life cycle of a mobile edge computing application based on a mobile edge computing application standard.

[0135] Example 3. An example embodiment of the method according to any one of Examples 1 to 2, and also includes: determining, by a mobile edge computing application manager, the feasibility of a mobile edge computing application standard; and if the mobile edge computing application standard is feasible, managing at least a portion of the life cycle of the mobile edge computing application based on the mobile edge computing application standard.

[0136] Example 4. An example embodiment of the method according to Example 3, wherein the received mobile edge computing application standard includes a proposed mobile edge computing application standard, wherein the management includes: determining, by a mobile edge computing application manager, that the proposed mobile edge computing application standard is not feasible; negotiating, by the mobile edge computing application manager, with an external application controller to agree on a feasible revised mobile edge computing application standard; storing the revised mobile edge computing application standard in a database for use in managing mobile edge computing applications; and managing, by the mobile edge computing application manager, at least a portion of the life cycle of the mobile edge computing application based on the revised mobile edge computing application standard.

[0137] Example 5. An example embodiment of the method according to Example 4, wherein the negotiation includes: sending a revised mobile edge computing application standard to an external application controller through a mobile edge computing application manager, the revised mobile edge computing application standard including at least one mobile edge computing application standard parameter that is different from the proposed mobile edge computing application standard, and the at least one mobile edge computing application standard parameter makes the revised mobile edge computing application standard feasible; and receiving confirmation of the revised mobile edge computing application standard from the external application controller through the mobile edge computing application manager.

[0138] Example 6. An example embodiment of the method of any one of Examples 1 to 5, wherein receiving the mobile edge computing application criteria is performed in response to sending the provided mobile edge computing application criteria to the external application controller by the mobile edge computing application manager.

[0139] Example 7. An example embodiment of the method according to any one of Examples 1 to 6, wherein determining the feasibility of a mobile edge computing application standard through a mobile edge computing application manager includes: comparing one or more parameters of the mobile edge computing application standard with one or more constraints associated with mobile edge computing application management; determining the feasibility of the mobile edge computing application standard by one of the following: based on the comparison, determining that the mobile edge computing application standard is not feasible based on determining that one or more parameters of the mobile edge computing application standard violate one or more constraints associated with mobile edge computing application management; and based on the comparison, determining that the mobile edge computing application standard is feasible based on determining that one or more parameters of the mobile edge computing application standard do not violate one or more constraints associated with mobile edge computing application management.

[0140] Example 8. An example embodiment of a method according to any one of Examples 2 to 7, wherein managing at least a portion of the lifecycle of a mobile edge computing application includes: executing and / or determining whether to execute one or more of the following based on a comparison of a mobile edge computing application standard or a revised mobile edge computing application standard with one or more conditions associated with the lifecycle management of the mobile edge computing application: instantiating a mobile edge computing application; terminating a mobile edge computing application; expanding resources allocated to the mobile edge computing application; and reducing resources allocated to the mobile edge computing application.

[0141] Example 9. An example embodiment of the method according to any one of Examples 1 to 8, wherein the mobile edge computing application standard or a revised mobile edge computing application standard includes at least: an application identifier that identifies the mobile edge computing application; and values ​​of one or more parameters for managing at least a portion of the life cycle of the mobile edge computing application, the one or more parameters including an action standard and an associated action to be performed for the mobile edge computing application if the action standard is met.

[0142] Example 10. An example embodiment of the method according to any one of Examples 1 to 9, wherein the mobile edge computing application standard or a revised mobile edge computing application standard includes at least one of the following: a first threshold for determining one or more conditions for instantiating a mobile edge computing application; a second threshold for determining one or more conditions for terminating a mobile edge computing application; a third threshold for determining one or more conditions for expanding resources allocated to the mobile edge computing application; and a fourth threshold for determining one or more conditions for reducing resources allocated to the mobile edge computing application.

[0143] Example 11. An example embodiment of the method according to any one of Examples 1 to 10, wherein the mobile edge computing application standard or the revised mobile edge computing application standard includes at least one of the following: a first billing rate threshold for determining a billing rate range for which the mobile edge computing application manager is being requested to instantiate a mobile edge computing application; a second billing rate threshold for determining a billing rate range for which the mobile edge computing application manager is being requested to expand resources used for the mobile edge computing application for the billing rate range; a third billing rate threshold for determining a billing rate range for which the mobile edge computing application manager is being requested to reduce resources used for the mobile edge computing application; and a fourth billing rate threshold for determining a billing rate range for which the mobile edge computing application manager is being requested to terminate the mobile edge computing application.

[0144] Example 12. An example embodiment of a method according to any one of Examples 1 to 11, wherein the mobile edge computing application standard or a revised mobile edge computing application standard includes values ​​of one or more of the following parameters for managing at least a portion of the life cycle of the mobile edge computing application: a valid timer parameter identifying a time period during which the mobile edge computing application standard is valid; a billing rate threshold for determining whether to perform a cycle or one or more actions of life cycle management of the mobile edge computing application; memory resources, processing resources, or bandwidth resources requested for the mobile edge computing application; the amount of bandwidth resources requested for the mobile edge computing application; requested performance for the mobile edge computing application related to at least one of latency, minimum bandwidth or data throughput, or quality of service; and radio network information service (RNIS) information related to a user device or a radio access bearer for the user device.

[0145] Example 13. An example embodiment of the method according to any one of Examples 1 to 12, wherein a mobile edge computing application standard or a revised mobile edge computing application standard specifies network conditions and associated actions to be performed on the mobile edge computing application when the network conditions are met, and wherein at least a portion of managing the life cycle of the mobile edge computing application includes: determining that the network conditions are met; based on the network conditions being met, performing associated actions on the mobile edge computing application, wherein the associated actions include one of: instantiating the mobile edge computing application, terminating the mobile edge computing application, adding resources to the mobile edge computing application, and reducing the resources of the mobile edge computing application.

[0146] Example 14. An example embodiment of a method according to any one of Examples 1 to 13, and also including: detecting changes in network conditions related to at least one of: changes in the availability of mobile edge computing server resources or changes in demand for mobile edge computing server resources; and based on the detected changes in network conditions, sending revised mobile edge computing application standards to an external application controller via a mobile edge computing application manager.

[0147] Example 15. In an example embodiment of the method according to any one of Examples 1 to 14, detecting changes in network conditions includes at least one of: detecting an increase or decrease in mobile edge computing server resources; detecting changes in (multiple) billing rates for mobile edge computing applications; and detecting changes in demand for mobile edge computing server resources based on resource requests for other mobile edge computing applications.

[0148] Example 16. An apparatus comprising means for performing the method of any one of Examples 1 to 15.

[0149] Example 17. A non-transitory computer-readable storage medium comprising instructions stored thereon that, when executed by at least one processor, are configured to cause a computing system to perform the method of any one of Examples 1 to 15.

[0150] Example 18. An apparatus comprising at least one processor and at least one memory comprising computer instructions that, when executed by the at least one processor, cause the apparatus to perform the method of any one of Examples 1 to 15.

[0151] Example 19. A device comprising at least one processor and at least one memory comprising computer instructions, which when executed by the at least one processor cause the device to: receive mobile edge computing application standards from an external application controller through a mobile edge computing application manager provided on a mobile edge computing server near a radio access network, the mobile edge computing application standards comprising management rules for managing at least a portion of a life cycle of the mobile edge computing application; and store the mobile edge computing application standards.

[0152] Example 20. The apparatus of Example 19, and further causing the apparatus to: manage at least a portion of a life cycle of a mobile edge computing application based on a mobile edge computing application standard.

[0153] Example 21. The apparatus of Example 19, and further causing the apparatus to: determine, through a mobile edge computing application manager, the feasibility of a mobile edge computing application standard; and if the mobile edge computing application standard is feasible, manage at least a portion of the life cycle of the mobile edge computing application based on the mobile edge computing application standard.

[0154] Example 22. An apparatus of any one of Examples 19 to 21, wherein the received mobile edge computing application standard includes a proposed mobile edge computing application standard, and wherein causing the apparatus to perform management includes causing the apparatus to: determine, through a mobile edge computing application manager, that the proposed mobile edge computing application standard is not feasible; negotiate, through the mobile edge computing application manager, with an external application controller to agree on a feasible revised mobile edge computing application standard; store the revised mobile edge computing application standard in a database for use in managing mobile edge computing applications; and manage, through the mobile edge computing application manager, at least a portion of the life cycle of the mobile edge computing application based on the revised mobile edge computing application standard.

[0155] Example 23. An apparatus of Example 22, wherein causing the apparatus to negotiate includes causing the apparatus to: send a revised mobile edge computing application standard to an external application controller through a mobile edge computing application manager, the revised mobile edge computing application standard including at least one mobile edge computing application standard parameter that is different from the proposed mobile edge computing application standard, and the at least one mobile edge computing application standard parameter makes the revised mobile edge computing application standard feasible; and receive confirmation of the revised mobile edge computing application standard from the external application controller through the mobile edge computing application manager.

[0156] Example 24. The apparatus of any one of Examples 19 to 23, wherein the apparatus is caused to: receive the mobile edge computing application standard in response to sending the provided mobile edge computing application standard to the external application controller through the mobile edge computing application manager.

[0157] Example 25. An apparatus of any one of Examples 19 to 24, wherein causing the apparatus to determine the feasibility of a mobile edge computing application standard through a mobile edge computing application manager includes causing the apparatus to: compare one or more parameters of the mobile edge computing application standard with one or more constraints associated with mobile edge computing application management; determine the feasibility of the mobile edge computing application standard by one of the following: based on the comparison, determining that the mobile edge computing application standard is not feasible based on a determination that one or more parameters of the mobile edge computing application standard violate one or more constraints associated with mobile edge computing application management; and based on the comparison, determining that the mobile edge computing application standard is feasible based on a determination that one or more parameters of the mobile edge computing application standard do not violate one or more constraints associated with mobile edge computing application management.

[0158] Example 26. An apparatus of any one of Examples 20 to 25, wherein causing the apparatus to manage at least a portion of the lifecycle of a mobile edge computing application includes causing the apparatus to: based on a comparison of a mobile edge computing application standard or a revised mobile edge computing application standard with one or more conditions associated with the lifecycle management of the mobile edge computing application, execute and / or determine whether to execute one or more of the following: instantiating a mobile edge computing application; terminating a mobile edge computing application; expanding resources allocated to the mobile edge computing application; and reducing resources allocated to the mobile edge computing application.

[0159] Example 27. An apparatus of any of Examples 19 to 26, wherein the mobile edge computing application standard or a revised mobile edge computing application standard includes at least: an application identifier that identifies the mobile edge computing application; and values ​​of one or more parameters for managing at least a portion of the life cycle of the mobile edge computing application, including action criteria and associated actions to be performed for the mobile edge computing application if the action criteria are met.

[0160] Example 28. An apparatus of any one of Examples 19 to 27, wherein the mobile edge computing application standard or the revised mobile edge computing application standard includes at least one of the following: a first threshold for determining one or more conditions for instantiating a mobile edge computing application; a second threshold for determining one or more conditions for terminating a mobile edge computing application; a third threshold for determining one or more conditions for expanding resources allocated to the mobile edge computing application; and a fourth threshold for determining one or more conditions for reducing resources allocated to the mobile edge computing application.

[0161] Example 29. An apparatus of any one of Examples 19 to 28, wherein the mobile edge computing application standard or the revised mobile edge computing application standard includes at least one of the following: a first billing rate threshold for determining a billing rate range for which the mobile edge computing application manager is being requested to instantiate a mobile edge computing application; a second billing rate threshold for determining a billing rate range for which the mobile edge computing application manager is being requested to expand resources for the mobile edge computing application; a third billing rate threshold for determining a billing rate range for which the mobile edge computing application manager is being requested to reduce resources for the mobile edge computing application; and a fourth billing rate threshold for determining a billing rate range for which the mobile edge computing application manager is being requested to terminate the mobile edge computing application.

[0162] Example 30. An apparatus of any one of Examples 19 to 29, wherein the mobile edge computing application standard or the revised mobile edge computing application standard includes values ​​of one or more of the following parameters for managing at least a portion of the life cycle of the mobile edge computing application: a valid timer parameter identifying a time period during which the mobile edge computing application standard is valid; a billing rate threshold for determining whether to perform a cycle or one or more actions of life cycle management of the mobile edge computing application; memory resources, processing resources, or bandwidth resources requested for the mobile edge computing application; the amount of bandwidth resources requested for the mobile edge computing application; requested performance for the mobile edge computing application related to at least one of latency, minimum bandwidth or data throughput, or quality of service; and radio network information service (RNIS) information related to a user device or a radio access bearer for the user device.

[0163] Example 31. An apparatus of any one of Examples 19 to 30, wherein a mobile edge computing application standard or a revised mobile edge computing application standard specifies network conditions and associated actions to be performed for the mobile edge computing application when the network conditions are met, and wherein enabling the apparatus to manage at least a portion of the life cycle of the mobile edge computing application includes enabling the apparatus to: determine that the network conditions are met; and based on the network conditions being met, perform associated actions for the mobile edge computing application, wherein the associated actions include one of: instantiating the mobile edge computing application, terminating the mobile edge computing application, expanding the resources of the mobile edge computing application, and reducing the resources of the mobile edge computing application.

[0164] Example 32. An apparatus of any one of Examples 19 to 31, and further causing the apparatus to: detect changes in network conditions related to at least one of: changes in the availability of mobile edge computing server resources or changes in demand for mobile edge computing server resources; and based on the detected changes in network conditions, send revised mobile edge computing application standards to an external application controller via a mobile edge computing application manager.

[0165] Example 33. An apparatus of Example 32, wherein causing the apparatus to detect changes in network conditions comprises at least one of: detecting an increase or decrease in mobile edge computing server resources; detecting a change in (multiple) billing rates for mobile edge computing applications; and detecting a change in demand for mobile edge computing server resources based on resource requests for other mobile edge computing applications.

[0166] Example 34. Figure 77 is a flow chart illustrating the operation of an external application controller according to an example embodiment. Operation 710 includes: sending, by the external application controller, to a mobile edge computing application manager provided on a mobile edge computing server proximate to a radio access network, a proposed mobile edge computing application standard including management rules for managing at least a portion of a life cycle of a mobile edge computing application.

[0167] Example 35. The method of claim 34, and also includes: receiving a revised mobile edge computing application standard from a mobile edge computing application manager through an external application controller, the revised mobile edge computing application standard including at least one mobile edge computing application standard parameter that is different from the proposed mobile edge computing application standard, and the at least one mobile edge computing application standard parameter makes the revised mobile edge computing application standard feasible with respect to the mobile edge computing application manager; and sending confirmation of the revised mobile edge computing application standard from the mobile edge computing application manager through the external application controller.

[0168] Example 36. A method of any of Examples 34 to 35, wherein the proposed or revised mobile edge computing application standard includes at least: an application identifier that identifies the mobile edge computing application; and values ​​of at least a portion of one or more parameters for managing the life cycle of the mobile edge computing application, including action criteria and associated actions to be performed for the mobile edge computing application if the action criteria are met.

[0169] Example 37. The method of any one of Examples 34 to 36, wherein the mobile edge computing application criteria includes at least one of: a first threshold for determining one or more conditions for instantiating a mobile edge computing application; a second threshold for determining one or more conditions for terminating a mobile edge computing application; a third threshold for determining one or more conditions for increasing resources allocated to the mobile edge computing application; and a fourth threshold for determining one or more conditions for reducing resources allocated to the mobile edge computing application.

[0170] Example 38. A method of any one of Examples 34 to 37, wherein the proposed mobile edge computing application standard or the revised mobile edge computing application standard includes at least one of the following: a first billing rate threshold for determining a billing rate range for which the mobile edge computing application manager is being requested to instantiate a mobile edge computing application; a second billing rate threshold for determining a billing rate range for which the mobile edge computing application manager is being requested to expand resources used for the mobile edge computing application; a third billing rate threshold for determining a billing rate range for which the mobile edge computing application manager is being requested to reduce resources used for the mobile edge computing application; and a fourth billing rate threshold for determining a billing rate range for which the mobile edge computing application manager is being requested to terminate the mobile edge computing application.

[0171] Example 39. A method of any one of Examples 34 to 38, wherein the proposed mobile edge computing application standard or the revised mobile edge computing application standard includes values ​​of one or more parameters for managing at least a portion of the life cycle of the mobile edge computing application: a valid timer parameter identifying a time period during which the mobile edge computing application standard is valid; a billing rate threshold for determining whether to perform a cycle or one or more actions of life cycle management of the mobile edge computing application; memory resources, processing resources, or bandwidth resources requested for the mobile edge computing application; the amount of bandwidth resources requested for the mobile edge computing application; requested performance for the mobile edge computing application related to at least one of latency, minimum bandwidth or data throughput, or quality of service; and radio network information service (RNIS) information related to a user device or a radio access bearer for the user device.

[0172] Example 40. An apparatus comprising components for performing the method of any of Examples 34 to 39.

[0173] Example 41. A non-transitory computer-readable storage medium comprising instructions stored thereon that, when executed by at least one processor, are configured to cause a computing system to perform the method of any one of Examples 34 to 39.

[0174] Example 42. An apparatus comprising at least one processor and at least one memory comprising computer instructions that, when executed by the at least one processor, cause the apparatus to perform the method of any one of Examples 34 to 39.

[0175] Example 43. A device comprising at least one processor and at least one memory comprising computer instructions, which when executed by the at least one processor cause the device to: send, via an external application controller, a recommended mobile edge computing application standard to a mobile edge computing application manager provided on a mobile edge computing server near a radio access network, the recommended mobile edge computing application standard including management rules for managing at least a portion of a life cycle of the mobile edge computing application.

[0176] Example 44. The apparatus of Example 43, and further causing the apparatus to: receive a revised mobile edge computing application standard from a mobile edge computing application manager through an external application controller, the revised mobile edge computing application standard including at least one mobile edge computing application standard parameter that is different from the proposed mobile edge computing application standard, and the at least one mobile edge computing application standard parameter makes the revised mobile edge computing application standard feasible for the mobile edge computing application manager; and send confirmation of the revised mobile edge computing application standard from the mobile edge computing application manager through the external application controller.

[0177] Example 45. An apparatus of any of Examples 43 to 44, wherein the proposed or revised mobile edge computing application standard includes at least: an application identifier that identifies the mobile edge computing application; and values ​​of one or more parameters for managing at least a portion of the life cycle of the mobile edge computing application, including action criteria and associated actions to be performed for the mobile edge computing application if the action criteria are met.

[0178] Example 46. An apparatus of any one of Examples 43 to 45, wherein the mobile edge computing application criteria include at least one of: a first threshold for determining one or more conditions for instantiating a mobile edge computing application; a second threshold for determining one or more conditions for terminating a mobile edge computing application; a third threshold for determining one or more conditions for expanding resources allocated to the mobile edge computing application; and a fourth threshold for determining one or more conditions for reducing resources allocated to the mobile edge computing application.

[0179] Example 47. An apparatus of any one of Examples 43 to 46, wherein the mobile edge computing application standard includes at least one of the following: a first billing rate threshold for determining a billing rate range for which the mobile edge computing application manager is being requested to instantiate a mobile edge computing application; a second billing rate threshold for determining a billing rate range for which the mobile edge computing application manager is being requested to expand resources used for the mobile edge computing application; a third billing rate threshold for determining a billing rate range for which the mobile edge computing application manager is being requested to reduce resources used for the mobile edge computing application; and a fourth billing rate threshold for determining a billing rate range for which the mobile edge computing application manager is being requested to terminate the mobile edge computing application.

[0180] Example 48. An apparatus of any one of Examples 43 to 47, wherein the mobile edge computing application standard includes values ​​for one or more of the following parameters, which are used to manage at least a portion of the life cycle of the mobile edge computing application: a valid timer parameter, identifying a time period during which the mobile edge computing application standard is valid; a billing rate threshold, used to determine whether to perform one or more actions or a period of life cycle management of the mobile edge computing application; memory resources, processing resources, or bandwidth resources requested for the mobile edge computing application; the amount of bandwidth resources requested for the mobile edge computing application; requested performance for the mobile edge computing application related to at least one of latency, minimum bandwidth or data throughput, or quality of service; and radio network information service (RNIS) information related to a user device or a radio access bearer for the user device.

[0181] Example 49. A device comprising at least one processor and at least one memory comprising computer instructions, which when executed by the at least one processor cause the device to: receive a proposed mobile edge computing application standard from an external application controller through a mobile edge computing application manager provided on a mobile edge computing server near a radio access network, the proposed mobile edge computing application standard comprising management rules for managing at least a portion of a life cycle of the mobile edge computing application; determine, through the mobile edge computing application manager, that the proposed mobile edge computing application standard is feasible; send, through the mobile edge computing application manager, a confirmation to the external application controller indicating that the proposed mobile edge computing application standard is feasible; and manage, through the mobile edge computing application manager, at least a portion of the life cycle of the mobile edge computing application based on the mobile edge computing application standard.

[0182] Example 50. The device of Example 49, and further causes the device to: send a proposed mobile edge computing application standard to a mobile edge computing application manager through an external application controller, wherein the proposed mobile edge computing application standard includes management rules for managing at least a part of the life cycle of the mobile edge computing application; and receive confirmation of the proposed mobile edge computing application standard through the external application controller.

[0183] Figure 8 900 is a block diagram of a wireless station (e.g., an AP or user equipment) according to an example embodiment. For example, the wireless station 900 may include one or two RF (radio frequency) or wireless transceivers 902A, 902B, each of which includes a transmitter for transmitting signals and a receiver for receiving signals. The wireless station also includes a processor or control unit / entity (controller) 904 for executing instructions or software and controlling the transmission and reception of signals, and a memory 906 for storing data and / or instructions.

[0184] The processor 904 may also make decisions or determinations, generate frames, packets or messages for transmission, decode received frames or messages for further processing, and other tasks or functions described herein. For example, the processor 904, which may be a baseband processor, may generate messages, packets, frames or other signals for transmission via the wireless transceiver 902 (902A or 902B). The processor 904 may control the transmission of signals or messages through a wireless network, and may control the reception of signals or messages via a wireless network, etc. (e.g., after being down-converted by, for example, the wireless transceiver 902). The processor 904 may be programmable and may be capable of executing software or other instructions stored in a memory or other computer medium to perform the various tasks and functions described above, such as one or more of the tasks or methods described above. For example, the processor 904 may be (or may include) hardware, programmable logic, a programmable processor that executes software or firmware, and / or any combination of these. For example, using other terms, the processor 904 and the transceiver 902 may be considered together as a wireless transmitter / receiver system.

[0185] In addition, refer to Figure 8 , the controller (or processor) 908 can execute software and instructions and can provide overall control of the station 900 and can provide Figure 8 Control of other systems not shown, such as control of input / output devices (e.g., display, keypad), and / or software that can execute one or more applications that may be provided on wireless station 900, such as, for example, an email program, an audio / video application, a word processor, an IP voice application, or other applications or software.

[0186] Additionally, a storage medium may be provided that includes stored instructions that, when executed by a controller or processor, may cause the processor 904 or other controller or processor to perform one or more of the functions or tasks described above.

[0187] According to another example embodiment, (multiple) RF or wireless transceiver 902A / 902B can receive signals or data and / or transmit or send signals or data. The processor 904 (and possibly the transceiver 902A / 902B) can control the RF or wireless transceiver 902A or 902B to receive, send, broadcast or transmit signals or data.

[0188] However, the embodiments are not limited to the systems given as examples, but a person skilled in the art may apply the solutions to other communication systems. Another example of a suitable communication system is the 5G concept. It is assumed that the network architecture in 5G will be quite similar to that of advanced LTE. 5G may use multiple-input multiple-output (MIMO) antennas, more base stations or nodes than LTE (the so-called small cell concept), including macro sites that operate in cooperation with smaller stations, and may also adopt various radio technologies to obtain better coverage and higher data rates.

[0189] It should be understood that future networks will most likely use network function virtualization (NFV), which is a network architecture concept that proposes virtualizing network node functions into "building blocks" or entities that can be operably connected or linked together to provide services. Virtualized network functions (VNFs) can include one or more virtual machines that run computer program code using standard or common types of servers rather than custom hardware. Cloud computing or data storage can also be used. In radio communications, this may mean that node operations can be performed at least in part in a server, host, or node that is operably coupled to a remote radio head. It is also possible that node operations will be distributed among multiple servers, nodes, or hosts. It should also be understood that the labor allocation between core network operations and base station operations may be different from LTE, or even non-existent.

[0190] The embodiments of the various technologies described herein may be implemented in a digital electronic circuit system or in computer hardware, firmware, software, or a combination thereof. The embodiments may be implemented as a computer program product, that is, a computer program tangibly implemented in an information carrier (e.g., tangibly implemented in a machine-readable storage device or a propagation signal) for a data processing device (e.g., a programmable processor, a computer, or multiple computers) to execute or control the operation of the data processing device. Embodiments may also be provided on a computer-readable medium or a computer-readable storage medium (which may be a non-transient medium). Embodiments of the various technologies may also include embodiments provided via transient signals or media and / or programs and / or software embodiments that may be downloaded via the Internet or (multiple) other networks (wired networks and / or wireless networks). In addition, embodiments may be provided via machine type communications (MTC) and also via the Internet of Things (IOT).

[0191] A computer program may be in source code form, object code form, or some intermediate form, and it may be stored in some carrier, distribution medium, or computer readable medium (which may be any entity or device capable of carrying the program). For example, such carriers include recording media, computer memories, read-only memories, optical and / or electrical carrier signals, telecommunication signals, and software distribution packages. Depending on the processing power required, a computer program may be executed in a single electronic digital computer, or it may be distributed among multiple computers.

[0192] In addition, embodiments of the various techniques described herein may use cyber-physical systems (CPS) (systems of collaborative computing elements that control physical entities). CPS can enable the implementation and development of a large number of interconnected ICT devices (sensors, actuators, processors, microcontrollers...) embedded in physical objects at different locations. Mobile cyber-physical systems, in which the physical systems discussed have inherent mobility, are a subcategory of cyber-physical systems. Examples of mobile physical systems include mobile robots and electronic products transported by people or animals. The popularity of smartphones has increased interest in the field of mobile cyber-physical systems. Therefore, various embodiments of the techniques described herein may be provided via one or more of these technologies.

[0193] A computer program (such as the computer program(s) described above) may be written in any form of programming language (including compiled or interpreted languages) and may be deployed in any form (including as a stand-alone program or module, component, subroutine, or other unit or portion thereof suitable for a computing environment). A computer program may be deployed to be executed on one computer or on multiple computers located at one site or distributed across multiple sites and interconnected by a communication network.

[0194] The method steps may be performed by one or more programmable processors executing a computer program or computer program portion to perform functions by operating on input data and generating output. The method steps may also be performed by, and the apparatus may be implemented as, a dedicated logic circuit system, such as an FPGA (field programmable gate array) or an ASIC (application-specific integrated circuit).

[0195] Processors suitable for executing computer programs include, for example, general-purpose microprocessors and special-purpose microprocessors and any one or more processors of any kind of digital computer, chip or chip set. Typically, the processor will receive instructions and data from a read-only memory or a random access memory or both. The elements of a computer may include at least one processor for executing instructions and one or more memory devices for storing instructions and data. Typically, a computer may also include or be operatively coupled to receive data from it or transfer data to it or both, to store data, such as magnetic disks, magneto-optical disks or optical disks. Information carriers suitable for implementing computer program instructions and data include all forms of non-volatile memory, including, for example, semiconductor memory devices (such as EPROM, EEPROM and flash memory devices); magnetic disks (such as internal hard disks or removable disks); magneto-optical disks; and CD-ROM and DVD-ROM disks. The processor and memory may be supplemented by or incorporated into a dedicated logic circuit system.

[0196] To provide interaction with a user, an embodiment may be implemented on a computer having: a display device for displaying information to a user, such as a cathode ray tube (CRT) or a liquid crystal display (LCD) monitor; and a user interface, such as a keyboard and a pointing device, such as a mouse or a trackball, through which a user can provide input to the computer. Other types of devices may also be used to provide interaction with a user; for example, the feedback provided to the user may be any form of sensory feedback, such as visual feedback, auditory feedback, or tactile feedback; and input from the user may be received in any form, including acoustic input, voice input, or tactile input.

[0197] Embodiments may be implemented in a computing system that includes a back-end component (e.g., as a data server), or a computing system that includes a middleware component (e.g., an application server), or a computing system that includes a front-end component (e.g., a client computer with a graphical user interface or a web browser through which a user can interact with the embodiment), or a computing system that includes any combination of such back-end components, middleware components, or front-end components. The components may be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include local area networks (LANs) and wide area networks (WANs), such as the Internet.

[0198] Although certain features of the described embodiments are illustrated as described herein, many modifications, substitutions, changes and equivalents will now occur to those skilled in the art. Therefore, it is to be understood that the appended claims are intended to cover all such modifications and changes that fall within the true spirit of the various embodiments.

Claims

1. A communication method, include: receiving, by a mobile edge computing application manager provided on a mobile edge computing server proximate to a radio access network, mobile edge computing application standards from an external application controller, the mobile edge computing application standards including management rules for managing at least a portion of a life cycle of a mobile edge computing application; determining availability of the mobile edge computing application standard; In response to determining that the mobile edge computing application standard is unavailable, Produce revised standards for mobile edge computing applications, sending the revised mobile edge computing application standard to the external application controller, receiving confirmation of said revised mobile edge computing application standard, and storing the revised mobile edge computing application standard; In response to determining that the mobile edge application standard is available, Storing the mobile edge computing application standard; as well as transmitting an application management report to the external application controller; The method further comprises: At least a portion of a life cycle of the mobile edge computing application is managed based on the mobile edge computing application standard.

2. The method according to claim 1, and further comprising: include: If the mobile edge computing application standard is feasible, at least a portion of a life cycle of the mobile edge computing application is managed based on the mobile edge computing application standard.

3. The method according to claim 1, wherein the received mobile edge computing application standard comprises a proposed mobile edge computing application standard, wherein the management include: Determining, by the mobile edge computing application manager, that the proposed mobile edge computing application standard is not feasible; Negotiating with the external application controller through the mobile edge computing application manager to agree on a feasible revised mobile edge computing application standard; as well as storing the mobile edge computing application standard or one of the revised mobile edge computing application standards in a database for use in managing the mobile edge computing application; At least a portion of the life cycle of the mobile edge computing application is managed, by the mobile edge computing application manager, based on the revised mobile edge computing application standard.

4. The method according to claim 3, wherein the negotiation include: A revised mobile edge computing application standard is sent to the external application controller through the mobile edge computing application manager, wherein the revised mobile edge computing application standard includes at least one mobile edge computing application standard parameter that is different from the mobile edge computing application standard, and the at least one mobile edge computing application standard parameter makes the revised mobile edge computing application standard feasible. 5 . The method of claim 1 , wherein receiving the mobile edge computing application standard is performed in response to sending the provided mobile edge computing application standard to the external application controller by the mobile edge computing application manager.

6. The method according to claim 2, wherein the feasibility of the mobile edge computing application standard is determined by the mobile edge computing application manager include: comparing one or more parameters of the mobile edge computing application criteria with one or more constraints associated with mobile edge computing application management; The feasibility of the mobile edge computing application standard is determined by one of the following: based on the comparing, determining that the mobile edge computing application standard is not feasible based on determining that the one or more parameters of the mobile edge computing application standard violate the one or more constraints associated with management of the mobile edge computing application; as well as Based on the comparing, it is determined that the mobile edge computing application standard is feasible based on a determination that the one or more parameters of the mobile edge computing application standard do not violate the one or more constraints associated with the mobile edge computing application management.

7. The method of claim 1, wherein managing at least a portion of a life cycle of a mobile edge computing application include: Based on a comparison of the mobile edge computing application standard or the revised mobile edge computing application standard and one or more conditions associated with the lifecycle management of the mobile edge computing application, performing and / or determining whether to perform one or more of the following: Instantiating the mobile edge computing application; terminating the mobile edge computing application; expanding resources allocated to the mobile edge computing application; as well as Resources allocated to the mobile edge computing application are reduced.

8. The method according to claim 1, wherein the mobile edge computing application standard or the revised mobile edge computing application standard at least include: An application identifier identifying the mobile edge computing application; as well as Values ​​of one or more parameters for managing at least a portion of a life cycle of the mobile edge computing application, the one or more parameters including action criteria and associated actions to be performed for the mobile edge computing application if the action criteria are met.

9. The method according to claim 1, wherein the mobile edge computing application standard or the revised mobile edge computing application standard comprises at least one of the following: a first threshold value, used to determine one or more conditions for instantiating the mobile edge computing application; a second threshold, used to determine one or more conditions for terminating the mobile edge computing application; a third threshold for determining one or more conditions for expanding resources allocated to the mobile edge computing application; as well as A fourth threshold is used to determine one or more conditions for reducing the resources allocated to the mobile edge computing application.

10. The method according to claim 1, wherein the mobile edge computing application standard or the revised mobile edge computing application standard comprises at least one of the following: a first billing rate threshold for determining a billing rate range for which the mobile edge computing application manager is being requested to instantiate the mobile edge computing application; a second billing rate threshold for determining a billing rate range for which the mobile edge computing application manager is being requested to expand resources for the mobile edge computing application; a third charging rate threshold for determining a charging rate range for which the mobile edge computing application manager is being requested to reduce resources for the mobile edge computing application; A fourth billing rate threshold for determining a billing rate range for which the mobile edge computing application manager is being requested to terminate the mobile edge computing application.

11. The method of claim 1 , wherein the mobile edge computing application standard or the revised mobile edge computing application standard comprises values ​​of one or more of the following parameters for managing at least a portion of a life cycle of the mobile edge computing application: A valid timer parameter, identifying a time period during which the mobile edge computing application standard is valid; a charging rate threshold, used to determine whether to execute a cycle or one or more actions of the lifecycle management of the mobile edge computing application; Memory resources, processing resources, or bandwidth resources requested by the mobile edge computing application; The amount of bandwidth resources requested by the mobile edge computing application; a requested performance for the mobile edge computing application related to at least one of latency, minimum bandwidth or data throughput, or quality of service; as well as Radio Network Information Service (RNIS) information related to a user equipment or a radio access bearer for said user equipment.

12. The method of claim 1, wherein the mobile edge computing application standard or the revised mobile edge computing application standard specifies network conditions and associated actions to be performed for the mobile edge computing application when the network conditions are met, and wherein managing at least a portion of the life cycle of the mobile edge computing application include: Determining that the network condition is met; Based on the network condition being met, the associated action is performed for the mobile edge computing application, wherein the associated action includes one of the following: instantiating the mobile edge computing application, terminating the mobile edge computing application, expanding resources used for the mobile edge computing application, and reducing resources used for the mobile edge computing application.

13. The method according to any one of claims 1 to 12, and further comprising: include: detecting a change in a network condition associated with at least one of: a change in availability of mobile edge computing server resources or a change in demand for mobile edge computing server resources; as well as Based on the detected change in the network condition, a revised mobile edge computing application standard is sent to the external application controller through the mobile edge computing application manager.

14. The method of claim 13, wherein detecting a change in network conditions comprises at least one of: detecting increases or decreases in mobile edge computing server resources; detecting a change in a billing rate for billing the mobile edge computing application; and Changes in demand for mobile edge computing server resources are detected based on resource requests for other mobile edge computing applications.

15. A non-transitory computer-readable storage medium comprising instructions stored thereon, which when executed by at least one processor are configured to cause a computing system to perform the method according to any one of claims 1 to 14.

16. An apparatus for communication, comprising at least one processor and at least one memory, the at least one memory comprising computer instructions which, when executed by the at least one processor, cause the apparatus to perform the method according to any one of claims 1 to 14.

17. An apparatus for communication, comprising at least one processor and at least one memory, the at least one memory comprising computer instructions which, when executed by the at least one processor, cause the apparatus to: receiving, by a mobile edge computing application manager provided on a mobile edge computing server proximate to a radio access network, mobile edge computing application standards from an external application controller, the mobile edge computing application standards including management rules for managing at least a portion of a life cycle of a mobile edge computing application; determining availability of the mobile edge computing application standard; In response to determining that the mobile edge computing application standard is unavailable, Produce revised standards for mobile edge computing applications, sending the revised mobile edge computing application standard to the external application controller, receiving confirmation of said revised mobile edge computing application standard, and storing the revised mobile edge computing application standard; In response to determining that the mobile edge computing application standard is available, Storing the mobile edge computing application standard; as well as transmitting an application management report to the external application controller; The device also enables: At least a portion of a life cycle of the mobile edge computing application is managed based on the mobile edge computing application standard.

18. The apparatus according to claim 17, further comprising: If the mobile edge computing application standard is feasible, at least a portion of a life cycle of the mobile edge computing application is managed based on the mobile edge computing application standard.

19. The apparatus of claim 17, wherein the received mobile edge computing application standard comprises a proposed mobile edge computing application standard, and wherein causing the apparatus to manage comprises causing the apparatus to: Determining, by the mobile edge computing application manager, that the proposed mobile edge computing application standard is not feasible; Negotiating with the external application controller through the mobile edge computing application manager to agree on a feasible revised mobile edge computing application standard; as well as storing the revised mobile edge computing application standard in a database for use in managing the mobile edge computing application; as well as At least a portion of the life cycle of the mobile edge computing application is managed, by the mobile edge computing application manager, based on the revised mobile edge computing application standard.

20. The apparatus of claim 19, wherein causing the apparatus to negotiate comprises causing the apparatus to: The revised mobile edge computing application standard is sent to the external application controller through the mobile edge computing application manager, wherein the revised mobile edge computing application standard includes at least one mobile edge computing application standard parameter that is different from the proposed mobile edge computing application standard, and the at least one mobile edge computing application standard parameter makes the revised mobile edge computing application standard feasible.

21. The apparatus according to claim 17, wherein the apparatus is caused to: receive the mobile edge computing application standard in response to sending the provided mobile edge computing application standard to the external application controller through the mobile edge computing application manager.

22. The apparatus of claim 18, wherein causing the apparatus to determine, through the mobile edge computing application manager, the feasibility of the mobile edge computing application standard comprises causing the apparatus to: comparing one or more parameters of the mobile edge computing application criteria with one or more constraints associated with mobile edge computing application management; The feasibility of the mobile edge computing application standard is determined by one of the following: Based on the comparing, determining that the mobile edge computing application standard is not feasible based on determining that the one or more parameters of the mobile edge computing application standard violate the one or more constraints associated with the mobile edge computing application management; and Based on the comparing, it is determined that the mobile edge computing application standard is feasible based on a determination that the one or more parameters of the mobile edge computing application standard do not violate the one or more constraints associated with the mobile edge computing application management.

23. The apparatus of claim 17, wherein causing the apparatus to manage at least a portion of a lifecycle of a mobile edge computing application comprises causing the apparatus to: perform and / or determine whether to perform one or more of the following based on a comparison of the mobile edge computing application standard or the revised mobile edge computing application standard and one or more conditions associated with the lifecycle management of the mobile edge computing application: Instantiating the mobile edge computing application; terminating the mobile edge computing application; expanding resources allocated to the mobile edge computing application; as well as Resources allocated to the mobile edge computing application are reduced.

24. The apparatus of claim 17, wherein the mobile edge computing application standard or the revised mobile edge computing application standard at least include: An application identifier identifying the mobile edge computing application; as well as Values ​​of one or more parameters for managing at least a portion of a life cycle of the mobile edge computing application, the one or more parameters including action criteria and associated actions to be performed for the mobile edge computing application if the action criteria are met.

25. The apparatus of claim 17, wherein the mobile edge computing application standard or the revised mobile edge computing application standard comprises at least one of the following: a first threshold value, used to determine one or more conditions for instantiating the mobile edge computing application; a second threshold, used to determine one or more conditions for terminating the mobile edge computing application; a third threshold for determining one or more conditions for expanding resources allocated to the mobile edge computing application; as well as A fourth threshold is used to determine one or more conditions for reducing the resources allocated to the mobile edge computing application.

26. The apparatus of claim 17, wherein the mobile edge computing application standard or the revised mobile edge computing application standard comprises at least one of the following: a first billing rate threshold for determining a billing rate range for which the mobile edge computing application manager is being requested to instantiate the mobile edge computing application; a second billing rate threshold for determining a billing rate range for which the mobile edge computing application manager is being requested to expand resources for the mobile edge computing application; a third charging rate threshold for determining a charging rate range for which the mobile edge computing application manager is being requested to reduce resources for the mobile edge computing application; A fourth billing rate threshold for determining a billing rate range for which the mobile edge computing application manager is being requested to terminate the mobile edge computing application.

27. The apparatus of claim 17, wherein the mobile edge computing application standard or the revised mobile edge computing application standard comprises values ​​for one or more of the following parameters for managing at least a portion of a life cycle of the mobile edge computing application: A valid timer parameter, identifying a time period during which the mobile edge computing application standard is valid; a charging rate threshold, used to determine whether to execute a cycle or one or more actions of the lifecycle management of the mobile edge computing application; Memory resources, processing resources, or bandwidth resources requested by the mobile edge computing application; The amount of bandwidth resources requested by the mobile edge computing application; a requested performance for the mobile edge computing application related to at least one of latency, minimum bandwidth or data throughput, or quality of service; as well as Radio Network Information Service (RNIS) information related to a user equipment or a radio access bearer for said user equipment.

28. The apparatus of claim 17, wherein the mobile edge computing application standard or the revised mobile edge computing application standard specifies network conditions and associated actions to be performed for the mobile edge computing application when the network conditions are met, and wherein causing the apparatus to manage at least a portion of a life cycle of the mobile edge computing application comprises causing the apparatus to: Determining that the network condition is met; Based on the network condition being met, the associated action is performed for the mobile edge computing application, wherein the associated action includes one of the following: instantiating the mobile edge computing application, terminating the mobile edge computing application, expanding resources used for the mobile edge computing application, and reducing resources used for the mobile edge computing application.

29. The device according to any one of claims 17 to 28, and further comprising: detecting a change in a network condition associated with at least one of: a change in the availability of mobile edge computing server resources or a change in demand for mobile edge computing server resources; and Based on the detected change in the network condition, a revised mobile edge computing application standard is sent to the external application controller through the mobile edge computing application manager.

30. The apparatus of claim 29, wherein causing the apparatus to detect a change in a network condition comprises at least one of: detecting increases or decreases in mobile edge computing server resources; detecting a change in a billing rate for billing the mobile edge computing application; as well as Changes in demand for mobile edge computing server resources are detected based on resource requests for other mobile edge computing applications.

31. A communication method, include: sending, by the external application controller, a first proposed mobile edge computing application standard to a mobile edge computing application manager provided on a mobile edge computing server proximate to a radio access network, the first proposed mobile edge computing application standard comprising management rules for managing at least a portion of a life cycle of a mobile edge computing application; receiving, by the external application controller, a second proposed mobile edge computing application standard; determining availability of said second proposed mobile edge computing application standard; In response to determining that the second proposed mobile edge computing application standard is not available, Produce revised standards for mobile edge computing applications, sending the revised mobile edge computing application standard to the mobile edge computing application manager, receiving confirmation of said revised mobile edge computing application standard; In response to determining that the second proposed mobile edge application standard is applicable, sending a confirmation of the first proposed mobile edge computing application standard to the mobile edge computing application manager; as well as receiving an application management report from the mobile edge computing application manager; The method further comprises: At least a portion of a life cycle of the mobile edge computing application is managed based on the mobile edge computing application criteria.

32. The method according to claim 31, and further comprising: include: receiving, by the external application controller, a revised mobile edge computing application standard from the mobile edge computing application manager, the second revised mobile edge computing application standard comprising at least one mobile edge computing application standard parameter different from the proposed mobile edge computing application standard, and the at least one mobile edge computing application standard parameter makes the revised mobile edge computing application standard feasible with respect to the mobile edge computing application manager; An acknowledgement of the second revised mobile edge computing application standard is sent from the mobile edge computing application manager through the external application controller.

33. The method of claim 31, wherein the proposed mobile edge computing application standard or the revised mobile edge computing application standard is at least include: An application identifier identifying the mobile edge computing application; as well as Values ​​of one or more parameters for managing at least a portion of a life cycle of the mobile edge computing application, the one or more parameters including action criteria and associated actions to be performed for the mobile edge computing application if the action criteria are met.

34. The method according to claim 31, wherein the mobile edge computing application standard comprises at least one of the following: a first threshold value, used to determine one or more conditions for instantiating the mobile edge computing application; a second threshold, used to determine one or more conditions for terminating the mobile edge computing application; a third threshold for determining one or more conditions for expanding resources allocated to the mobile edge computing application; as well as A fourth threshold is used to determine one or more conditions for reducing the resources allocated to the mobile edge computing application.

35. The method of claim 31, wherein the proposed mobile edge computing application standard or the revised mobile edge computing application standard comprises at least one of the following: a first billing rate threshold for determining a billing rate range for which the mobile edge computing application manager is being requested to instantiate the mobile edge computing application; a second billing rate threshold for determining a billing rate range for which the mobile edge computing application manager is being requested to expand resources for the mobile edge computing application; a third billing rate threshold for determining a billing rate range for which the mobile edge computing application manager is being requested to reduce a billing rate range for resources used for the mobile edge computing application; A fourth billing rate threshold for determining a billing rate range for which the mobile edge computing application manager is being requested to terminate the mobile edge computing application.

36. The method of any one of claims 31 to 35, wherein the proposed mobile edge computing application standard or the revised mobile edge computing application standard includes values ​​for one or more of the following parameters for managing at least a portion of a life cycle of the mobile edge computing application: A valid timer parameter, identifying a time period during which the mobile edge computing application standard is valid; a charging rate threshold, used to determine whether to execute a cycle or one or more actions of the lifecycle management of the mobile edge computing application; Memory resources, processing resources, or bandwidth resources requested by the mobile edge computing application; an amount of bandwidth resources requested by the mobile edge computing application; a requested performance for the mobile edge computing application related to at least one of latency, minimum bandwidth or data throughput, or quality of service; as well as Radio Network Information Service (RNIS) information related to a user equipment or a radio access bearer for said user equipment.

37. A non-transitory computer-readable storage medium comprising instructions stored thereon, which when executed by at least one processor are configured to cause a computing system to perform the method of any one of claims 31 to 36.

38. An apparatus for communication, comprising at least one processor and at least one memory, the at least one memory comprising computer instructions which, when executed by the at least one processor, cause the apparatus to perform a method according to any one of claims 31 to 36.

39. An apparatus for communication, comprising at least one processor and at least one memory, the at least one memory comprising computer instructions that, when executed by the at least one processor, cause the apparatus to: sending, by an external application controller, a first mobile edge computing application standard to a mobile edge computing application manager provided on a mobile edge computing server proximate to a radio access network, the proposed mobile edge computing application standard comprising management rules for managing at least a portion of a life cycle of a mobile edge computing application; receiving, by the external application controller, a second proposed mobile edge computing application standard; determining availability of said second proposed mobile edge computing application standard; In response to determining that the second proposed mobile edge computing application standard is not available, Produce revised standards for mobile edge computing applications, sending the revised mobile edge computing application standard to the mobile edge computing application manager, receiving confirmation of said revised mobile edge computing application standard; In response to determining that the second proposed mobile edge computing application standard is available, Sending a confirmation of the first mobile edge computing application standard to the mobile edge computing application manager; as well as receiving an application management report from the mobile edge computing application manager; The device wherein: At least a portion of a life cycle of the mobile edge computing application is managed based on the mobile edge computing application standard.

40. The apparatus of claim 39, further comprising: A revised mobile edge computing application standard is received from the mobile edge computing application manager through the external application controller, wherein the revised mobile edge computing application standard includes at least one mobile edge computing application standard parameter that is different from the proposed mobile edge computing application standard, and the at least one mobile edge computing application standard parameter makes the revised mobile edge computing application standard feasible for the mobile edge computing application manager.

41. The apparatus of claim 39, wherein the proposed mobile edge computing application or the revised mobile edge computing application standard is at least include: An application identifier identifying the mobile edge computing application; as well as Values ​​of one or more parameters for managing at least a portion of a life cycle of the mobile edge computing application, the one or more parameters including action criteria and associated actions to be performed for the mobile edge computing application if the action criteria are met.

42. The apparatus of claim 39, wherein the mobile edge computing application standard comprises at least one of the following: a first threshold value, used to determine one or more conditions for instantiating the mobile edge computing application; a second threshold, used to determine one or more conditions for terminating the mobile edge computing application; a third threshold for determining one or more conditions for expanding resources allocated to the mobile edge computing application; as well as A fourth threshold is used to determine one or more conditions for reducing the resources allocated to the mobile edge computing application.

43. The apparatus of claim 39, wherein the mobile edge computing application standard comprises at least one of the following: a first billing rate threshold for determining a billing rate range for which the mobile edge computing application manager is being requested to instantiate the mobile edge computing application; a second billing rate threshold for determining a billing rate range for which the mobile edge computing application manager is being requested to expand resources for the mobile edge computing application; a third charging rate threshold for determining a charging rate range for which the mobile edge computing application manager is being requested to reduce resources for the mobile edge computing application; A fourth billing rate threshold is used to determine a billing rate range for which the mobile edge computing application manager is being requested to terminate the mobile edge computing application.

44. The apparatus of any one of claims 39 to 43, wherein the mobile edge computing application criteria comprises values ​​of one or more of the following parameters for managing at least a portion of a life cycle of the mobile edge computing application: A valid timer parameter, identifying a time period during which the mobile edge computing application standard is valid; a charging rate threshold, used to determine whether to execute a cycle or one or more actions of the lifecycle management of the mobile edge computing application; Memory resources, processing resources, or bandwidth resources requested by the mobile edge computing application; an amount of bandwidth resources requested by the mobile edge computing application; a requested performance for the mobile edge computing application related to at least one of latency, minimum bandwidth or data throughput, or quality of service; as well as Radio Network Information Service (RNIS) information related to a user equipment or a radio access bearer for said user equipment.

45. An apparatus for communication, comprising at least one processor and at least one memory, the at least one memory comprising computer instructions that, when executed by the at least one processor, cause the apparatus to: receiving, by a mobile edge computing application manager provided on a mobile edge computing server proximate to a radio access network, a proposed mobile edge computing application standard from an external application controller, the proposed mobile edge computing application standard comprising management rules for managing at least a portion of a life cycle of a mobile edge computing application; Determining, by the mobile edge computing application manager, that the proposed mobile edge computing application standard is feasible; sending, by the mobile edge computing application manager, to the external application controller a confirmation indicating that the proposed mobile edge computing application standard is feasible; as well as At least a portion of a life cycle of the mobile edge computing application is managed by the mobile edge computing application manager based on the mobile edge computing application standard.

46. ​​The apparatus of claim 45, further comprising: Sending the proposed mobile edge computing application standard to the mobile edge computing application manager through the external application controller, wherein the proposed mobile edge computing application standard includes a management rule for managing at least a portion of a life cycle of the mobile edge computing application; and The confirmation of the proposed mobile edge computing application standard is received by the external application controller.

Citation Information

Patent Citations

  • Method and system for context-aware management of applications at the edge of a network

    CN104104538A

  • Policy based selection of resources for cloud service

    CN105518651A

  • Method, device and system for realizing mobile edge computing service

    CN107018534A

  • Application instance migration method and device

    CN107305502A

  • Multi-server mobile edge computing based control and resource scheduling method

    CN107734558A