Business path establishment method, communication device and storage medium

Abstract

This application discloses a service path establishment method, communication device, and storage medium. The method includes: receiving a first request message from a multi-access edge computing application, the first request message including a multi-access edge computing service, wherein the first request message is used to obtain a service path between a multi-access edge computing service instance and the multi-access edge computing application from the multi-access edge computing platform, and the multi-access edge computing service instance is used to provide the multi-access edge computing service; configuring the service path between the multi-access edge computing service instance and the multi-access edge computing application, and sending the service path to the multi-access edge computing application. This application embodiment helps reduce the operation and maintenance costs of multi-access edge computing applications.

Description

Technical Field

[0001] This invention relates to the field of edge computing, specifically to a service path establishment method, a communication device, and a storage medium. Background Technology

[0002] With the maturity and widespread adoption of 5G technology, high-bandwidth, low-latency applications are gradually maturing on the terminal side, making 5G connectivity + edge computing converged solutions a goal and vision pursued by major vendors. Multi-access Edge Computing (MEC), defined in the European Telecommunications Standards Institute (ETSI) standard, provides edge content to users by deploying Multi-access Edge Computing Applications (MEC APPs) at the network edge, achieving local offloading and meeting the demands of over-the-top (OTT) providers for low-latency, high-throughput services at the edge.

[0003] Currently, the European Telecommunications Standards Institute (ETSI) standards define a standard architecture for MEC technology. Within this standard architecture, deploying a new MEC application requires manual intervention. For example, it necessitates manually configuring the communication link between the MEC application's network and compute domains. Therefore, the current manual intervention required for MEC application deployment leads to low deployment efficiency and high operational costs. Summary of the Invention

[0004] This application provides a business path establishment method, communication device, and storage medium, which reduces the operation and maintenance costs of multi-access edge computing applications by automatically generating business paths between multi-access edge computing applications and multi-access edge computing service instances.

[0005] Firstly, embodiments of this application provide a method for establishing a service path. The method can be executed by a multi-access edge computing platform or by a chip applied within the multi-access edge computing platform. The following description uses a multi-access edge computing platform as the executing entity. The method includes: receiving a first request message from a multi-access edge computing application, the first request message including a multi-access edge computing service, wherein the first request message is used to obtain a service path between a multi-access edge computing service instance and the multi-access edge computing application from the multi-access edge computing platform, and the multi-access edge computing service instance is used to provide multi-access edge computing services; configuring the service path between the multi-access edge computing service instance and the multi-access edge computing application; and sending the service path to the multi-access edge computing application.

[0006] As can be seen from this embodiment, during the deployment of the multi-access edge computing application, the application can request a business path between the multi-access edge computing service instance and the application via a first request message from the application platform. The multi-edge access computing platform configures this business path according to requirements and distributes it to the application. In this way, the application can establish a business link with the service instance based on this path, thus automatically establishing the business link without manual intervention, reducing the operational costs of the application.

[0007] In some possible implementations, the service path includes service rules and / or routing parameters. The service rules are used to characterize the correspondence between multi-access edge computing service instances and service instances in multi-access edge computing applications, and the routing parameters are used to characterize the communication links between multi-access edge computing service instances and multi-access edge computing applications.

[0008] As can be seen, the multi-access edge computing platform can automatically generate the correspondence between multi-access edge computing applications and multi-access edge computing service instances without the need for manual configuration, thus reducing the difficulty of establishing the mapping relationship between the two. In addition, the multi-access edge computing platform can automatically configure the communication link without manual intervention, which reduces the cost of deploying multi-access edge computing applications and improves the automation level of deployment.

[0009] In some possible implementations, the first request message is received from the multi-access edge computing application through the first MP1 interface or through a newly added first interface. The first MP1 interface is an MP1 interface in the MP1 interface set used to provide the multi-access edge computing service subscription function, and the newly added first interface is used to provide the multi-access edge computing service application function.

[0010] As can be seen, the multi-access edge computing platform can receive the first request message through the first MP1 interface (subscription interface), which means that the multi-access edge computing platform itself can use the interface provided by the multi-access edge computing platform to make request messages for business path allocation, thereby improving the reusability of the first MP1 interface; the multi-access edge computing platform can also receive the first request message through the newly added first interface, thereby improving the flexibility of sending the first request message and enabling flexible configuration of business paths.

[0011] In some possible implementations, before receiving the first request message from the multi-access edge computing application, the method further includes: receiving a configuration message from the multi-access edge computing platform manager, the configuration message including network parameters of the multi-access edge computing application, the network parameters being used by the multi-access edge computing platform to configure the communication link between the multi-access edge computing application and the multi-access edge computing service instance.

[0012] As can be seen, by pre-defining the network parameters of multi-access edge computing applications, the multi-access edge computing platform can clearly know the network role to which the multi-access edge computing application belongs, such as knowing the network slice to which the multi-access edge computing application belongs. This allows it to allocate the corresponding slice instance, thereby improving the accuracy of the configured communication links.

[0013] In some possible implementations, network parameters include the virtual local area network (VLAN) to which the multi-access edge computing application belongs, the network slice to which it belongs, and the subscribed user group to which it belongs; configuring the service path between the multi-access edge computing service instance and the multi-access edge computing application includes: determining the network resources available between the multi-access edge computing application and the multi-access edge computing service instance based on the VLAN to which the multi-access edge computing application belongs, the network slice to which it belongs, and the subscribed user group to which it belongs; and configuring the communication link between the multi-access edge computing application and the multi-access edge computing service instance based on the network resources available between them.

[0014] As can be seen, by pre-defining the virtual local area network, network slice, and subscribed user group to which the multi-access edge computing application belongs, the multi-access edge computing platform can accurately determine the network resources (such as computing resources, storage resources, virtual machine resources, etc.) available between the multi-access edge computing application and the multi-access edge computing service instance, thereby improving the accuracy of the configured communication links.

[0015] In some possible implementations, the network parameters also include the interface capabilities of the multi-access edge computing application, which characterize the MP1 interface supported by the multi-access edge computing application in the MP1 interface. The method further includes: interfacing with the MP1 interface supported by the multi-access edge computing application based on the interface capabilities of the multi-access edge computing application.

[0016] As can be seen, by pre-defining the interface capabilities of multi-access computing applications, the multi-access edge computing application platform can clearly know which MP1 interfaces the multi-access edge computing application supports. This allows the platform to enable these MP1 interfaces and automatically interface with the MP1 interfaces supported by the multi-access edge computing application, thereby improving the flexibility of interface with the multi-access edge computing application.

[0017] In some possible implementations, the method further includes: generating uplink traffic splitting rules corresponding to the multi-access edge computing application based on the network parameters of the multi-access edge computing application; configuring the uplink traffic splitting rules to the user plane function entity, wherein the user plane function entity and the multi-access edge computing platform are located at the same multi-access edge computing site.

[0018] It can be seen that the multi-access edge computing platform generates corresponding uplink traffic splitting rules based on the network parameters of the multi-access edge computing application. Since the uplink traffic splitting rules are obtained based on the network parameters, the accuracy of local traffic splitting and filtering is improved, that is, the accuracy of filtering out user devices that meet the local traffic splitting conditions is improved.

[0019] Secondly, embodiments of this application provide a method for establishing a service path. The execution subject of this method can be a multi-access edge computing application or a chip applied within the multi-access edge computing application. The following description uses a multi-access edge computing application as the execution subject. The method includes: sending a first request message to a multi-access edge computing platform, the first request message including a multi-access edge computing service, wherein the first request message is used to obtain a service path between a multi-access edge computing service instance and a multi-access edge computing application from the multi-access edge computing platform, and the multi-access edge computing service instance is used to provide multi-access edge computing services; and receiving the service path between the multi-access edge computing service instance and the multi-access edge computing application from the multi-access edge computing platform.

[0020] As can be seen from this embodiment, during the deployment of the multi-access edge computing application, the application can request a business path between the multi-access edge computing service instance and the application via a first request message from the application platform. The multi-edge access computing platform configures this business path according to requirements and distributes it to the application. In this way, the application can establish a business link with the service instance based on this path, thus automatically establishing the business link without manual intervention, reducing the operational costs of the application.

[0021] In some possible implementations, the service path includes service rules and / or routing parameters. The service rules are used to characterize the correspondence between multi-access edge computing service instances and service instances in multi-access edge computing applications, and the routing parameters are used to characterize the communication links between multi-access edge computing service instances and multi-access edge computing applications.

[0022] As can be seen, the multi-access edge computing platform can automatically generate the correspondence between multi-access edge computing applications and multi-access edge computing service instances without the need for manual configuration, thus reducing the difficulty of establishing the mapping relationship between the two. In addition, the multi-access edge computing platform can automatically configure the communication link without manual intervention, which reduces the cost of deploying multi-access edge computing applications and improves the automation level of deployment.

[0023] In some possible implementations, sending a first request message to a multi-access edge computing platform includes: sending a first request message to the multi-access edge computing platform through a first MP1 interface or sending a first request message to the multi-access edge computing platform through a newly added first interface, wherein the first MP1 interface is an MP1 interface in the MP1 interface set used to provide multi-access edge computing service subscription function, and the newly added first interface is used to provide multi-access edge computing service application function.

[0024] As can be seen, multi-access edge computing applications can send first request messages to the multi-access edge computing platform through the first MP1 interface (subscription interface), which improves the reusability of the first MP1 interface. They can also send first request messages to the multi-access edge computing platform through the newly added first interface, which improves the flexibility of sending first request messages and allows for flexible application and configuration of business paths between the application and the multi-access edge computing service instance.

[0025] In some possible implementations, the communication link is configured by the multi-access edge computing platform based on the network parameters of the multi-access edge computing application, which are sent to the multi-access edge computing platform by the multi-access edge computing platform manager via configuration messages.

[0026] As can be seen, by pre-defining the network parameters of multi-access edge computing applications, the multi-access edge computing platform can clearly know the network role to which the multi-access edge computing application belongs, such as knowing the network slice to which the multi-access edge computing application belongs. This allows it to allocate the corresponding slice instance, thereby improving the accuracy of the configured communication links.

[0027] In some possible implementations, the network parameters of the multi-access edge computing application include the virtual local area network to which the multi-access edge computing application belongs, the network slice to which it belongs, and the subscribed user group to which it belongs; the communication link is configured by the multi-access edge computing platform based on the network resources available between the multi-access edge computing application and the multi-access edge computing service instance, and the available network resources are determined by the multi-access edge computing platform based on the virtual local area network to which the multi-access edge computing application belongs, the network slice to which it belongs, and the subscribed user group to which it belongs.

[0028] As can be seen, by pre-defining the virtual local area network, network slice, and subscribed user group to which the multi-access edge computing application belongs, the multi-access edge computing platform can accurately determine the network resources (such as computing resources, storage resources, virtual machine resources, etc.) available between the multi-access edge computing application and the multi-access edge computing service instance, thereby improving the accuracy of the configured communication links.

[0029] In some possible implementations, network parameters also include the interface capabilities of the multi-access edge computing application, which characterize the MP1 interface supported by the multi-access edge computing application in the MP1 interface.

[0030] As can be seen, by pre-defining the interface capabilities of multi-access computing applications, the multi-access edge computing application platform can clearly know which MP1 interfaces the multi-access edge computing application supports. This allows the platform to enable these MP1 interfaces and automatically interface with the MP1 interfaces supported by the multi-access edge computing application, thereby improving the flexibility of interface with the multi-access edge computing application.

[0031] Thirdly, embodiments of this application provide a communication device, the beneficial effects of which are described in the first aspect and will not be repeated here. The communication device has the function of implementing the behavior in the method example of the first aspect described above. The function can be implemented by hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above functions. In one possible design, the communication device includes: a transceiver module, configured to receive a first request message from a multi-access edge computing application, the first request message including a multi-access edge computing service, wherein the first request message is used to obtain a service path between a multi-access edge computing service instance and the multi-access edge computing application from the multi-access edge computing platform, and the multi-access edge computing service instance is used to provide multi-access edge computing services; a processing module, configured to configure the service path between the multi-access edge computing service instance and the multi-access edge computing application; the transceiver module is further configured to send the service path to the multi-access edge computing application.

[0032] Fourthly, embodiments of this application provide a communication device, the beneficial effects of which are described in the second aspect and will not be repeated here. The communication device has the function of implementing the behavior in the method example of the first aspect described above. The function can be implemented by hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above functions. In one possible design, the communication device includes: a processing module, configured to control a transceiver module to send a first request message to a multi-access edge computing platform, the first request message including a multi-access edge computing service, wherein the first request message is used to obtain a business path between a multi-access edge computing service instance and a multi-access edge computing application from the multi-access edge computing platform, the multi-access edge computing service instance being used to provide multi-access edge computing services; and controlling the transceiver module to receive the business path between the multi-access edge computing service instance and the multi-access edge computing application from the multi-access edge computing platform.

[0033] Fifthly, embodiments of this application provide a communication device, which can be a multi-access edge computing platform as described in the above method embodiments, or a chip disposed within a multi-access edge computing platform. The communication device includes a communication interface and a processor, and optionally, a memory. The memory stores computer programs or instructions, and the processor is coupled to the memory and the communication interface. When the processor executes the computer program or instructions, it causes the communication device to perform the method executed by the multi-access edge computing platform as described in the above method embodiments.

[0034] Sixthly, embodiments of this application provide a communication device, which can be a multi-access edge computing application as described in the above method embodiments, or a chip disposed within a multi-access edge computing application. The communication device includes a communication interface and a processor, and optionally, a memory. The memory stores computer programs or instructions, and the processor is coupled to the memory and the communication interface. When the processor executes the computer program or instructions, it causes the communication device to perform the methods executed by the multi-access edge computing application as described in the above method embodiments.

[0035] In a seventh aspect, a computer program product is provided, comprising: computer program code, which, when executed, causes the methods executed by the multi-access edge computing platform in the above aspects to be performed.

[0036] Eighthly, a computer program product is provided, comprising: computer program code, which, when executed, causes the methods executed by the multi-access edge computing application in the above aspects to be performed.

[0037] Ninthly, this application provides a chip system including a processor for implementing the functions of a multi-access edge computing platform as described in the methods of the above aspects. In one possible design, the chip system also includes a memory for storing program instructions and / or data. The chip system may be composed of chips or may include chips and other discrete devices.

[0038] In a tenth aspect, this application provides a chip system including a processor for implementing the functions of the multi-access edge computing application described in the methods of the above aspects. In one possible design, the chip system also includes a memory for storing program instructions and / or data. The chip system may be composed of chips or may include chips and other discrete devices.

[0039] In one aspect, this application provides a computer-readable storage medium storing a computer program that, when run, implements the methods executed by the multi-access edge computing platform in the above aspects.

[0040] In a twelfth aspect, this application provides a computer-readable storage medium storing a computer program that, when run, implements the methods performed by the multi-access edge computing application described above.

[0041] In a thirteenth aspect, this application provides a business path establishment system, including the communication device of the fifth aspect and the communication device of the sixth aspect. Attached Figure Description

[0042] Figure 1 This is a schematic diagram illustrating the deployment process of a MEC APP according to an embodiment of this application.

[0043] Figure 2 An architecture diagram of a system is established for one of the business paths in an embodiment of this application;

[0044] Figure 3 This is a flowchart illustrating a method for establishing a computing service path according to an embodiment of this application.

[0045] Figure 4 This is a schematic diagram of the structure of a communication device according to an embodiment of this application;

[0046] Figure 5 This is a schematic diagram of another communication device according to an embodiment of this application. Detailed Implementation

[0047] The methods described in this application are applicable to various system architectures, such as 5G system architecture. The network architectures and service scenarios described in this application are for the purpose of more clearly illustrating the technical solutions of this application and do not constitute a limitation on the technical solutions provided in this application. As those skilled in the art will know, with the evolution of network architecture and the emergence of new service scenarios, the technical solutions provided in this application are also applicable to similar technical problems.

[0048] It should be understood that the User Equipment (UE) involved in the embodiments of this application may include mobile phones (or "cellular" phones), wireless user equipment, mobile user equipment, device-to-device (D2D) user equipment, vehicle-to-everything (V2X) user equipment, machine-to-machine / machine-type communications (M2M / MTC) user equipment, Internet of Things (IoT) user equipment, subscriber unit, subscriber station, mobile station, remote station, access point (AP), remote terminal, access terminal, user terminal, user agent, or user device, etc.

[0049] It should be understood that the core network elements involved in this application include, but are not limited to, the following network elements: Access and Mobility Management Function (AMF) network elements, Session Management Function (SMF) network elements, management network elements, User Plane Function (UPF), Unified Data Repository (UDR) network elements, and Policy Control Function (PCF).

[0050] AMF: Primarily responsible for UE authentication, UE mobility management, network slice selection, SMF selection, etc.; serves as the anchor point for N1 and N2 signaling connections and provides routing for N1 / N2 SM messages for SMF; maintains and manages UE state information;

[0051] SMF: Primarily responsible for all control plane functions of UE session management, including UPF selection, IP address allocation, session quality of service (QoS) management, and obtaining policy and charging control (PCC) policies from PCF, etc.

[0052] UPF: As the anchor point for PDU session connections, it is responsible for filtering data packets from user equipment, data transmission / forwarding, rate control, and generating billing information.

[0053] UDR network element: mainly used to store user data, including subscription data called by UDM, policy information called by PCF, structured data for capability opening, and application data called by NEF.

[0054] AF Entity: Application service function, interacts with core network elements to provide some services, such as interacting with PCF to control service policies, interacting with NEF to obtain some network capability information or provide some application information to the network, and providing some data network access point information to PCF to generate corresponding data service routing information.

[0055] PCF: Provides configuration policy information for UE and provides policy information for network control plane elements (such as AMF and SMF) to manage and control UE.

[0056] To facilitate understanding of this application, relevant technical knowledge involved in the embodiments of this application will be introduced first.

[0057] With the maturity and widespread adoption of 5G technology, high-bandwidth, low-latency applications are gradually maturing on the terminal side, making 5G connectivity + edge computing converged solutions a goal and vision pursued by major manufacturers. The Multi-access Edge Computing (MEC) solution defined in the European Telecommunications Standards Institute (ETSI) standard meets the demands of over-the-top (OTT) providers for low-latency, high-throughput services at the edge.

[0058] The ETSI standard defines two management components deployed on the central side: the Multi-access Edge Computing Application Orchestrator (MEAO) and the Multi-access Edge Computing Platform Manager (MEPM). It also defines Application Description (APPD) information, which describes the instance information of the Multi-access Edge Computing Application (MEC APP) to be deployed. This includes MEC APP resource information, dependent MEC services, provided services, traffic rules, graceful exit, MEC APP identifier, etc. Then, MEPM sends the key information from the APPD to the edge-side MEP (Moverage Provider) via the Mm5 interface using a Configure Request message. The MEP parses the Configure Request and completes the instantiation and deployment of the MEC APP with the local data platform. The following diagram illustrates the MEC APP instantiation and deployment process.

[0059] like Figure 1As shown, the Operations Support Systems (OSS) sends an Instantiate application request message to MEAO, which forwards it to MEPM. MEPM then sends a resource allocation request message to the Network Functions Virtualization Infrastructure (NFVI). After completing resource allocation, NFVI returns a resource allocation response message to MEPM, carrying the allocated resource information. MEPM sends a Configure Request message to MEP, carrying key information about the MEC application and the allocated resources. MEP configures the MEC application based on this Configure Request message, i.e., instantiates the MEC application. Finally, after instantiation, MEP returns an Instantiate application response message to MEAO and forwards it to OSS.

[0060] Although the APPD describes the instance information of the MEC APP, the description fields are limited, and some information is not described. For this missing information, manual reconfiguration is required. For example, the MEP defined in the ETSI MEC standard provides a set of MP1 interfaces (MEP functional MP1 interfaces) for MEC APPs. This set includes MP1 interfaces with various functions, such as those for service publishing, service discovery, and subscription reception. However, not all MEC APPs support all MP1 interfaces in this set. Some application providers develop their own MP1 interfaces for MEC APPs based on their specific needs. To ensure successful integration between the MEP and the MEC APP on the MP1 interface set, when the MEC APP is deployed, the MP1 interfaces supported by the MEC APP are manually passed to the MEPM via the APPD description file, and then distributed to the MEP by the MEPM.

[0061] Furthermore, after instantiating the MEC App, communication links need to be established for local traffic offloading. These links include those between the MEC App, the MEC Service instance, and the User Plane Function (UPF). Currently, this is done manually after the MEC App's instantiation is confirmed as "Ready," and then manually configuring the communication links between the MEC App and the MEC Service instance, as well as between the MEC Service instance and the UPF.

[0062] It can be seen that the current MEC APP deployment process requires manual intervention, resulting in low deployment efficiency and high maintenance costs.

[0063] See Figure 2 , Figure 2 This application provides a system architecture diagram for establishing a business path. The system architecture includes a multi-access edge computing platform 10 and a multi-access edge computing application 20. The multi-access edge computing platform 10 deploys one or more access edge computing service instances, and the multi-access edge computing application 20 deploys one or more service instances. The multi-access edge computing service instances provide multi-access edge computing services to the service instances in the multi-access edge computing application 20, and each service instance provides edge content to the user.

[0064] For example, the multi-access edge computing application 20 sends a first request message to the multi-access edge computing platform 10, wherein the first request message is used to obtain the business path between the multi-access edge computing service instance and the multi-access edge computing application from the multi-access edge computing platform 10; the multi-access edge computing platform 10 configures the business path between the multi-access edge computing service instance and the multi-access edge computing application 20, and distributes the business path to the multi-access edge computing application 20; accordingly, the multi-access edge computing application 20 establishes a business path with the multi-access edge computing service instance according to the business path, that is, the business link between the multi-access edge computing application 20 and the multi-access edge computing service instance is established.

[0065] As can be seen from the embodiments of this application, the multi-access edge computing platform can automatically configure the business path between the multi-access edge computing application and the multi-access edge computing service instance according to the first request message, without the need for manual configuration, thereby reducing the operation and maintenance cost of the multi-access edge computing application.

[0066] It should be understood that this system architecture also includes a Multi-access Edge Orchestrator (EMAO), a Multi-access Edge Manager (MEPM), and so on. These devices are used to perform other business processes. For example, before establishing business paths, the MEAO, the Network Functions Virtualization Orchestrator (NFVO), and other devices coordinate to complete the deployment and instantiation of multi-access edge computing applications. This application does not describe the deployment process of multi-access edge computing applications.

[0067] See Figure 3 , Figure 3 This is a flowchart illustrating a business path establishment method provided in an embodiment of this application. The method includes the following steps:

[0068] 301: The multi-access edge computing application sends a first request message to the multi-access edge computing platform.

[0069] The first request message is used to obtain the business path between the multi-access edge computing service instance and the multi-access edge computing application from the multi-access edge computing platform. The multi-access edge computing service instance is used to provide multi-access edge computing services. For example, the business path includes business rules and / or communication links.

[0070] Specifically, business rules characterize the correspondence between the multi-access edge computing service instance and the service instances within the multi-access edge computing application. The multi-access edge computing service instance provides the multi-access edge computing service to the application, and the service instances within the application provide edge data to the user. For example, the multi-access edge computing service instance provides a load balancing (LB) service, and there are two such instances. These two instances provide LB services to ten service instances within the application. Then, a mapping relationship is established between these two instances and the ten service instances. For instance, the first instance provides LB services to the first five of the ten service instances, and the second instance provides LB services to the last five. This establishes the business rules between the multi-access edge computing service instances and the application.

[0071] Specifically, the routing parameter represents the communication link between the Multi-Access Edge Computing Service (MEC) instance and the MEC application. For example, the routing parameter can be the downlink routing parameter of the MEC instance. The MEC application can then establish a communication link with the MEC service instance based on the downlink routing parameter and its own uplink routing parameter. During uplink transmission, the uplink routing parameter is used as the source address, and the downlink routing parameter of the MEC instance is used as the destination address to establish the communication link and transmit data packets. The uplink routing parameter of the MEC application can be allocated by the MEC application's control plane, registered by the MEC application with the MEP, and then forwarded by the MEP to the MEC service instance. This will not be described in detail here.

[0072] Furthermore, the communication link also includes the VPN link, network slice instance, bandwidth, interface, etc., between the MEC APP and the multi-access edge computing service instance. That is, the computing and storage resources available between the MEC APP and the MEC service instance, which VPN link is used, and which interface (e.g., N6 interface) is used for data transmission.

[0073] For example, the MEC APP can send the first request message to the MEP through the first MP1 interface in the MP1 interface set. This first MP1 interface is the MP1 interface in the MP1 interface set of the multi-access edge computing platform that provides multi-access edge service subscription functionality. In other words, the first request message is a subscription message, indicating that the multi-access edge computing application is subscribing to the multi-access edge computing service from the multi-access edge computing platform. Correspondingly, the multi-access edge computing platform sends the service path to the multi-access edge computing application through the first MP1 interface.

[0074] It should be understood that if a Multi-Access Edge Computing (MEP) service instance has already been deployed to provide the MEP service, and this MEP service instance has sufficient resources to provide the MEP service to the MEC App, for example, if there are two MEP service instances, currently only providing MEP service to five service instances in one MEC App, and each MEP service instance can provide service to a maximum of five service instances in the MEC App, then if it is determined that the MEP service instance has remaining resources to provide service to the MEC App, then it is not necessary to deploy the MEP service instance; only the corresponding business rules and communication links need to be configured. Of course, if it is determined that the MEP service instance has no remaining resources or has not been deployed, then it is necessary to deploy the MEP service instance first. However, this multi-access edge computing service instance may not necessarily be requested by the MEC APP. The MEC APP may only have subscribed to this multi-access edge computing service. In other words, without a corresponding MEC service instance, the MEP may not immediately deploy one, but instead wait for the MEC service instance to come online. For example, if other MEC APPs subsequently request and deploy this MEC service instance, the MEP can configure the business path between the MEC APP and the MEC service instance.

[0075] For example, the MEC APP can also send the first request message to the MEP through the newly added first interface, which is used to provide the function of applying for multi-access edge computing services. That is, the MEC APP sends the first request message through the newly added first interface to dynamically apply for multi-access edge computing services from the MEP.

[0076] It should be understood that before the multi-access edge computing application receives the first request message, the MEP needs to expand a first interface for receiving MEC service request messages and a second interface for sending MEC service request response messages, and then expose these newly added first and second interfaces to the MEC application. Therefore, after receiving the first request message through the newly added first interface, the MEP can parse the message to obtain the multi-access edge computing service; then, based on the function of the newly added first interface, the MEP determines that the MEC application is requesting the deployment of the multi-access edge computing service. Correspondingly, the MEP sends the service path to the MEC application through the newly added second interface.

[0077] It should be understood that if a multi-access edge computing service instance is already deployed in the MEP to provide the multi-access edge computing service, and this multi-access edge computing service instance has sufficient resources to provide the multi-access edge computing service to the MEC APP, then it is not necessary to deploy the multi-access edge computing service instance; only the corresponding business rules and routing parameters need to be configured. If it is determined that the multi-access edge computing service instance has no remaining resources or has not been deployed, then the multi-access edge computing service instance needs to be deployed immediately, and after deployment, the business path between the multi-access edge computing service instance and the MEC APP should be configured.

[0078] For example, the MEC APP can also send the first request message through any MP1 interface in the MP1 interface set. This first request message matches the format of the MP1 interface, but with added new fields, and definitions for these fields are added in both the MEP and the MEC APP. Thus, after receiving the first request message, the MEP can not only parse the message itself but also the function of the field. For instance, if a registration message adds a field for MEC service application, carrying the multi-access edge computing service, the MEP can parse this field to obtain not only the MEC APP's topology information but also the fact that the MEC APP is requesting the deployment of the MEC service.

[0079] 302: The multi-access edge computing platform configures the business path between the multi-access edge computing service instance and the multi-access edge computing application, and distributes the business path to the multi-access edge computing application. Correspondingly, the multi-access edge computing application establishes the business path between itself and the multi-access edge computing service instance.

[0080] It should be understood that the multi-access edge computing platform simultaneously sends the business path to the multi-access edge computing service instance. Correspondingly, the multi-access edge computing service instance establishes a business path with the multi-access edge computing application.

[0081] As can be seen from the embodiments of this application, the multi-access edge computing platform can automatically generate the business path between the multi-access edge computing service instance and the multi-access edge computing application without manual configuration, thereby reducing the operation and maintenance cost of the multi-access edge computing application.

[0082] For example, the MEP configures the business rules and routing parameters between the multi-access edge computing service instance and the multi-access edge computing application. For example, the MEP can configure the business rules according to a pre-injected business policy template, such as configuring each LB service instance, serving 5 service instances in the MEC APP, and configuring them sequentially from front to back; it can also be configured according to a preset algorithm, etc. This application does not limit the configuration method.

[0083] It should be understood that since this business rule is essentially a mapping between the multi-access edge computing service instance and the service instances in the multi-access edge computing application, the multi-access edge computing application can specifically send this business rule to the service instances within the multi-access edge computing application. This means sending the identifier of the multi-access edge computing service that each service instance in the multi-access edge computing application can use to the application. For example, if the LB service instances include LB Service1 and LB Service2, and LB Service1 provides edge computing services to service instances 1 through 5 in the MEC APP, and LB Service2 provides edge computing services to service instances 6 through 10 in the MEC APP, then the identifier of LB Service1 (e.g., a virtual IP address) can be sent to service instances 1 through 5, instructing them to use LB Service1 for load balancing.

[0084] For example, the MEP can allocate network resources to the MEC service instance based on the network resources currently available at the MEC site, and configure the communication link between the multi-access edge computing service instance and the multi-access edge computing application based on the network resources.

[0085] In one embodiment of this application, before receiving a first request message from a multi-access edge computing application, the multi-access edge computing platform also receives a configuration message from a multi-access edge computing manager. The configuration message includes network parameters of the multi-access edge computing application, which are used by the multi-access edge computing platform to configure the communication link between the access edge computing application and the multi-access edge computing service instance. Figure 3As shown, when deploying the MEC APP, the APPD is first manually orchestrated. The newly added field of the APPD indicates the network parameters of the multi-access edge computing application. Then, the manually orchestrated APPD is injected into the MEAO through the northbound interface provided by MEAO. MEAO forwards the APPD to the MEPM. The MEPM parses the APPD to obtain the network parameters of the multi-access edge computing application and sends the configuration message to the MEP through the Mm5 interface. The configuration message includes the network parameters of the multi-access edge computing application. Then, the MEP parses the configuration message to obtain the network parameters of the multi-access edge computing application.

[0086] For example, the network parameters of an MEC APP include the virtual LAN to which the MEC APP belongs, the network slice to which it belongs, the interface capabilities, the subscribed user group to which it belongs, and the Data Network Access Identifier (DNAI). Among these, the interface capabilities refer to the MP1 interfaces supported by the MEC APP within the MP1 interface set provided by the MEP; the subscribed user group refers to the subscribed user group to which the MEC APP can provide local traffic offloading. It should be understood that the network parameters mentioned in this application are illustrative and do not limit the form of the network parameters. Other network parameters can be described later in the APPD.

[0087] For example, an APPD is manually orchestrated, adding new fields to the existing APPD, and the newly added fields indicate the network parameters of the MEC APP; then, the orchestrated APPD and APP image template are manually injected into MEAO or MEPM, and MEPM then distributes the manually orchestrated APPD to MEP.

[0088] For example, Table 1 shows one way to indicate network parameters for an MEC APP.

[0089] Table 1:

[0090]

[0091] It should be understood that the methods for indicating network parameters of the MEC APP shown in Table 1 are merely illustrative examples, illustrating that network parameters of the MEC APP can be indicated by adding fields in the APPD. Specific indications can vary; for example, multiple network parameters can be indicated by a single field, etc. This application does not limit the indication methods.

[0092] It should be understood that after injecting a manually orchestrated APPD into MEAO or MEPM, the MEC APP can be deployed online manually in MEAO or MEPM. MEAO can select a target MEC site based on the DNAI in the APPD and complete the deployment of the MEC APP at that target MEC site. This application does not describe the deployment of MEC APP in detail.

[0093] For example, the MEP allocates available network resources to the multi-access edge computing application based on the application's network parameters; then, it configures the communication link between the multi-access edge computing application and the multi-access edge computing service instance based on the available network resources.

[0094] For example, the communication link includes, but is not limited to, downlink routing parameters, network slice instances, bandwidth, Virtual Private Network (VPN) links, and communication interfaces. For instance, the MEP can map network slice instances based on the network slice to which the MEC APP belongs, determining the network slice instances that the MEC APP can use; configure the VPN link for the MEC APP based on its subscribed user group and its virtual LAN; allocate corresponding bandwidth and communication interfaces to the MEC APP based on its subscribed user group, and so on.

[0095] Furthermore, the MEP can also perform network isolation and access control for the MEC APP based on its network parameters. For example, the MEP can isolate the MEC APP's behavior within the network area corresponding to the network slice to which the MEC APP belongs. This means isolating the MEC Services that the MEC APP can subscribe to or the service instances it can register within this network area. For instance, if the network slice to which the MEC APP belongs provides 2B services, the service instances registered by the MEC APP can only be used to provide 2B services, and illegally registered service instances will be invalidated, meaning the MEC APP cannot provide such services. In addition, the MEP can manage the MEC APP's access permissions based on its contracted user group. For instance, if the MEC APP belongs to a contracted user group that has been authorized to access location information or bandwidth management, then the MEC APP can perform location access and bandwidth management.

[0096] For example, the multi-access edge computing platform (MEP) interfaces with the MP1 interface supported by the MEC application based on the interface capabilities of the MEC application. The MEP automatically receives interaction messages from the MEC application's MP1 interface. For instance, the MP1 interfaces supported by the MEC application can be imported into the MP1 interface interaction and automatic enabling state machine. This allows for automatic integration with the MEC application through the MP1 interface interaction and automatic enabling state machine. For example, if the MEC application supports the first MP1 interface, the MEP can enable that first MP1 interface and automatically receive subscription messages from the MEC application. For MP1 interfaces not supported by the MEC application, these interfaces are not enabled, and therefore not exposed to the MEC application.

[0097] As can be seen, by describing the interface capabilities of the MEC APP in the APPD, the MEP can only interface with the MP1 interface supported by the MEC APP, selectively opening some MP1 interfaces and improving the flexibility of the MEP interface with the MEC APP.

[0098] In one embodiment of this application, the multi-access edge computing platform generates an uplink traffic rule corresponding to the multi-access edge computing application based on the network parameters of the multi-access edge computing application, and configures the uplink traffic rule to the user plane function entity, wherein the user plane function entity and the multi-access edge computing platform are located in the same multi-access edge computing site.

[0099] For example, the multi-access edge computing platform determines the VPN of the multi-access edge computing application based on the user subscription group to which the application belongs, and inserts the VPN as an uplink traffic offloading rule into the user plane function entity. Thus, when a user device subsequently accesses the multi-access edge computing application, the user plane function entity determines whether the VPN used by the user device conforms to the uplink traffic offloading rule. If so, it determines that the user device meets the local traffic offloading conditions and forwards the user device's user data packets to the multi-access edge computing application, achieving local traffic offloading.

[0100] It should be understood that the MEP can also configure the communication link between the MEC service instance and the UPF based on the network parameters of the MEC APP, that is, configure the communication link between the multi-access edge service instance in the MEP and the multi-access edge computing service instance in the UPF. Similarly, this communication link includes network slice instances, bandwidth, interfaces, VPNs, etc.

[0101] In one embodiment of this application, for the network domain, the Policy Control Function (PCF) obtains the topology information and selection rules of the MEC APP. The topology information includes the network parameters and instance information of the MEC APP, where the instance information can be the APP identity, APP type, etc. The selection rules are used to select the corresponding core network device. The selection rules in this application are rules for selecting core network devices based on a comprehensive analysis of the MEC APP's network parameters and instance information. The MEC APP's topology information and selection rules are manually compiled, registered with the Unified Data Repository (UDR), and forwarded to the PCF by the UDR.

[0102] For example, such as Figure 3 As shown, the topology information and selection rules for the MEC APP can be manually arranged and manually registered with the UDR. The UDR forwards the MEC APP's topology information and selection rules to the PCF. Then, the PCF selects the appropriate Session Management Function (SMF) based on the network parameters. For example, the PCF performs slice mapping based on the network slice to which the MEC belongs, obtains a network slice instance, selects the corresponding SMF within that network slice instance, and sends the MEC APP's topology information and network parameters to that SMF. The SMF selects the appropriate UPF based on the network parameters, for example, selecting a matching UPF based on the network slice to which the MEC APP belongs and its DNAI. Then, the SMF inserts the MEC APP's instance information and uplink traffic splitting rules into the UPF.

[0103] As can be seen, through the above communication link configuration, the communication links between the MEC APP, the multi-access edge computing service instances in the MEP, and the multi-access edge computing service instances in the UPF are automatically established. For example... Figure 3 As shown, each MECAPP can perform local traffic splitting on its own communication link. That is, each MECAPP uses the corresponding network slice instance in its own network domain (network slice) to perform local traffic splitting on its own communication link.

[0104] As can be seen, describing the network parameters of the MEC APP in the APPD allows for the selection of core network devices in the corresponding network slice instance, thereby making the selection of core network devices more precise and enhancing the tightness of the connection with core network devices.

[0105] It should be understood that after a user session is established, the UPF can receive edge access requests from user devices. Based on these requests, the UPF determines the instance information of the MEC APP that the user device wants to access and the VPN used for access. The UPF then obtains the uplink traffic splitting rules corresponding to the instance information of the MEC APP. If the VPN meets the local traffic splitting conditions, the user device will undergo local traffic splitting. If it does not meet the conditions, the user's data packets will be forwarded to the central UPF to obtain the data content.

[0106] The embodiments provided above for establishing business paths in this application describe the methods provided by this application from the perspectives of a multi-access edge computing platform, a multi-access edge computing application, and the interaction between the multi-access edge computing platform and the multi-access edge computing application. To implement the functions of the methods provided in the embodiments above, the multi-access edge computing platform and the multi-access edge computing application may include hardware structures and / or software modules, implementing the above functions in the form of hardware structures, software modules, or a combination of hardware structures and software modules. Whether a particular function is executed in the form of hardware structures, software modules, or a combination of hardware structures and software modules depends on the specific application and design constraints of the technical solution.

[0107] Figure 4 and Figure 5 This application provides a schematic diagram of a communication device according to its embodiments. These communication devices can implement the functions of the multi-access edge computing platform or multi-access edge computing application described in the above method embodiments, and therefore also achieve the beneficial effects of the above method embodiments. In the embodiments of this application, the communication device can be as follows: Figure 3 The multi-access edge computing platform shown in the corresponding embodiment can also be a multi-access edge computing application, or a module (such as a chip) applied to the multi-access edge computing platform or the multi-access edge computing application.

[0108] like Figure 4 As shown, the communication device 400 includes a transceiver module 401 and a processing module 402. The communication device 400 can be used to implement the above-mentioned... Figure 3 The corresponding embodiments describe the functionality of the multi-access edge computing platform or the multi-access edge computing application.

[0109] When the communication device 400 is used to implement Figure 3 The functionality of the multi-access edge computing platform in the method embodiments is as follows:

[0110] The transceiver module 401 is used to receive a first request message from the multi-access edge computing application. The first request message includes a multi-access edge computing service. The first request message is used to obtain the business path between the multi-access edge computing service instance and the multi-access edge computing application from the multi-access edge computing platform. The multi-access edge computing service instance is used to provide multi-access edge computing services.

[0111] Processing module 402 is used to configure the business path between the multi-access edge computing service instance and the multi-access edge computing application;

[0112] The transceiver module is also used to send service paths to multi-access edge computing applications.

[0113] When the communication device 400 is used to implement Figure 3 The functionality of the multi-access edge computing application in the method embodiment is as follows:

[0114] The processing module 402 is used to control the transceiver module 401 to send a first request message to the multi-access edge computing platform. The first request message includes a multi-access edge computing service. The first request message is used to obtain the business path between the multi-access edge computing service instance and the multi-access edge computing application from the multi-access edge computing platform. The multi-access edge computing service instance is used to provide multi-access edge computing services. The processing module 402 is used to receive the business path between the multi-access edge computing service instance and the multi-access edge computing application from the multi-access edge computing platform.

[0115] For a more detailed description of the transceiver module 401 and the processing module 402, please refer to the relevant descriptions in the above method embodiments, which will not be repeated here.

[0116] like Figure 5 As shown, the communication device 500 includes a processor 501 and an interface circuit 502. The processor 501 and the interface circuit 502 are coupled to each other. It is understood that the interface circuit 502 can be a transceiver or an input / output interface. Optionally, the communication device 500 may also include a memory 503 for storing instructions executed by the processor 501, or storing input data required by the processor 501 to execute instructions, or storing data generated after the processor 501 executes instructions.

[0117] When the communication device 500 is used to implement the method in the above method embodiment, the processor 501 is used to execute the function of the processing module 402, and the interface circuit 502 is used to execute the function of the transceiver module 401.

[0118] When the aforementioned communication device is a chip used in a multi-access edge computing platform, the chip in the multi-access edge computing platform implements the functions of the multi-access edge computing platform in the above method embodiments. The chip in the multi-access edge computing platform receives information from other modules (such as radio frequency modules or antennas) in the multi-access edge computing platform, which is sent to the multi-access edge computing platform by the multi-access edge computing application; or, the chip in the multi-access edge computing platform sends information to other modules (such as radio frequency modules or antennas) in the multi-access edge computing platform, which is sent to the multi-access edge computing application by the multi-access edge computing platform.

[0119] When the aforementioned communication device is a chip used in a multi-access edge computing application, the chip in the multi-access edge computing application implements the functions of the multi-access edge computing application in the above method embodiments. The chip in the multi-access edge computing application receives information from other modules (such as radio frequency modules or antennas) within the multi-access edge computing application, which is sent by the multi-access edge computing platform to the multi-access edge computing application; or, the chip in the multi-access edge computing application sends information to other modules (such as radio frequency modules or antennas) within the multi-access edge computing application, which is sent by the multi-access edge computing application to the multi-access edge computing platform.

[0120] This application also provides a business path establishment system, including the communication device that implements the multi-access edge computing platform function and the communication device that implements the multi-access edge computing application function.

[0121] This application also provides a computer-readable storage medium storing a computer program thereon, which, when executed by a processor, can implement the processes related to the multi-access edge computing platform in the business path establishment method provided in the above method embodiments.

[0122] This application also provides a computer-readable storage medium storing a computer program thereon, which, when executed by a processor, can implement the processes related to the multi-access edge computing application in the business path establishment method provided in the above method embodiments.

[0123] This application also provides a computer program product that, when run on a computer or processor, causes the computer or processor to execute one or more steps in any of the above-described business path establishment methods. If the constituent modules of the aforementioned devices are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium.

[0124] It is understood that the processor in the embodiments of this application may be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. A general-purpose processor may be a microprocessor or any conventional processor.

[0125] The method steps in the embodiments of this application can be implemented in hardware or by a processor executing software instructions. The software instructions can consist of corresponding software modules, which can be stored in random access memory (RAM), flash memory, read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), registers, hard disks, portable hard disks, CD-ROMs, or any other form of storage medium known in the art. An exemplary storage medium is coupled to a processor, enabling the processor to read information from and write information to the storage medium. Of course, the storage medium can also be a component of the processor. The processor and storage medium can reside in an ASIC. Furthermore, the ASIC can reside in a multi-access edge computing platform or a multi-access edge computing application. Alternatively, the processor and storage medium can exist as discrete components in a multi-access edge computing platform or application.

[0126] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented in software, it can be implemented, in whole or in part, as a computer program product. A computer program product includes one or more computer programs or instructions. When the computer program or instructions are loaded and executed on a computer, the processes or functions of the embodiments of this application are performed, in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer program or instructions can be stored in or transmitted through a computer-readable storage medium. The computer-readable storage medium can be any available medium that a computer can access, or a data storage device such as a server that integrates one or more available media. The available medium can be a magnetic medium, such as a floppy disk, hard disk, or magnetic tape; it can also be an optical medium, such as a DVD; or it can be a semiconductor medium, such as a solid-state disk (SSD).

[0127] In the various embodiments of this application, unless otherwise specified or in case of logical conflict, the terminology and / or descriptions of different embodiments are consistent and can be referenced by each other. The technical features of different embodiments can be combined to form new embodiments according to their inherent logical relationship.

[0128] In this application, "at least one" means one or more, and "more than one" means two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, or B alone, where A and B can be singular or plural. In the textual description of this application, the character " / " generally indicates an "or" relationship between the preceding and following related objects; in the formulas of this application, the character " / " indicates a "division" relationship between the preceding and following related objects.

[0129] It is understood that the various numerical designations used in the embodiments of this application are merely for descriptive convenience and are not intended to limit the scope of the embodiments of this application. The order of the process numbers described above does not imply the order of execution; the execution order of each process should be determined by its function and internal logic.

Claims

1. A method for establishing a business path, characterized in that, Applications include multi-access edge computing platforms, including: A first request message is received from a multi-access edge computing application. The first request message includes a multi-access edge computing service. The first request message is used to obtain a business path between a multi-access edge computing service instance and the multi-access edge computing application from the multi-access edge computing platform. The multi-access edge computing service instance is used to provide the multi-access edge computing service. Configure the service path between the multi-access edge computing service instance and the multi-access edge computing application, and send the service path to the multi-access edge computing application; The business path includes business rules and / or routing parameters. The business rules are used to characterize the correspondence between the multi-access edge computing service instance and the service instance in the multi-access edge computing application. The routing parameters are used to characterize the communication link between the multi-access edge computing service instance and the multi-access edge computing application.

2. The method according to claim 1, characterized in that, Receiving the first request message from the multi-access edge computing application includes: The first request message is received from the multi-access edge computing application through the first MP1 interface or through the newly added first interface, wherein the first MP1 interface is an MP1 interface in the MP1 interface set used to provide multi-access edge computing service subscription function, and the newly added first interface is used to provide multi-access edge computing service application function.

3. The method according to claim 1 or 2, characterized in that, Before receiving the first request message from the multi-access edge computing application, the method further includes: The system receives a configuration message from the Multi-Access Edge Computing Platform Manager. The configuration message includes network parameters for the Multi-Access Edge Computing Application. These network parameters are used by the Multi-Access Edge Computing Platform to configure the communication link between the Multi-Access Edge Computing Application and the Multi-Access Edge Computing Service Instance.

4. The method according to claim 3, characterized in that, The network parameters include the virtual local area network to which the multi-access edge computing application belongs, the network slice to which it belongs, and the subscribed user group to which it belongs; The configuration of the business path between the multi-access edge computing service instance and the multi-access edge computing application includes: Based on the virtual local area network, network slice, and subscribed user group to which the multi-access edge computing application belongs, determine the network resources available between the multi-access edge computing application and the multi-access edge computing service instance; Configure the communication link between the multi-access edge computing application and the multi-access edge computing service instance based on the network resources available between them.

5. The method according to claim 4, characterized in that, The network parameters also include the interface capabilities of the multi-access edge computing application, which characterize the MP1 interface supported by the multi-access edge computing application in the MP1 interface. The method further includes: Based on the interface capabilities of the multi-access edge computing application, it interfaces with the MP1 interface supported by the multi-access edge computing application.

6. The method according to any one of claims 1, 2, 4, and 5, characterized in that, The method further includes: Based on the network parameters of the multi-access edge computing application, generate uplink traffic splitting rules corresponding to the multi-access edge computing application; The uplink traffic splitting rules are configured for the user plane function entity, which is located at the same multi-access edge computing site as the multi-access edge computing platform.

7. A method for establishing a business path, characterized in that, Applications include multi-access edge computing applications, including: Send a first request message to a multi-access edge computing platform. The first request message includes a multi-access edge computing service. The first request message is used to obtain a business path between a multi-access edge computing service instance and the multi-access edge computing application from the multi-access edge computing platform. The multi-access edge computing service instance is used to provide the multi-access edge computing service. Receive the business path between the multi-access edge computing service instance and the multi-access edge computing application from the multi-access edge computing platform; The business path includes business rules and / or routing parameters. The business rules are used to characterize the correspondence between the multi-access edge computing service instance and the service instance in the multi-access edge computing application. The routing parameters are used to characterize the communication link between the multi-access edge computing service instance and the multi-access edge computing application.

8. The method according to claim 7, characterized in that, Sending the first request message to the multi-access edge computing platform includes: The first request message is sent to the multi-access edge computing platform through the first MP1 interface or through the newly added first interface, wherein the first MP1 interface is an MP1 interface in the MP1 interface set used to provide multi-access edge computing service subscription function, and the newly added first interface is used to provide multi-access edge computing service application function.

9. The method according to claim 7 or 8, characterized in that, The communication link is configured by the multi-access edge computing platform according to the network parameters of the multi-access edge computing application. The network parameters of the multi-access edge computing application are sent to the multi-access edge computing platform by the multi-access edge computing platform manager through configuration messages.

10. The method according to claim 9, characterized in that, The network parameters of the multi-access edge computing application include the virtual local area network to which the multi-access edge computing application belongs, the network slice to which it belongs, and the subscribed user group to which it belongs. The communication link is configured by the multi-access edge computing platform based on the network resources available between the multi-access edge computing application and the multi-access edge computing service instance. The available network resources are determined by the multi-access edge computing platform based on the virtual local area network, network slice, and subscribed user group to which the multi-access edge computing application belongs.

11. The method according to claim 10, characterized in that, The network parameters also include the interface capabilities of the multi-access edge computing application, which characterize the MP1 interface supported by the multi-access edge computing application in the MP1 interface.

12. A communication device, characterized in that, Includes modules for performing the method as described in any one of claims 1-6 or 7-11.

13. A communication device, characterized in that, The device includes a processor and a communication interface, wherein the communication interface is used to receive signals from other communication devices outside the communication device and transmit them to the processor, or to send signals from the processor to other communication devices outside the communication device, and the processor is used to implement the method as described in any one of claims 1-6 or 7-11 through logic circuits or executing code instructions.

14. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when executed, implements the method as claimed in any one of claims 1-6 or 7-11.

Images