WO2022105807A1 - 服务实例部署方法、跨域互访通道建立方法及相关装置 - Google Patents

服务实例部署方法、跨域互访通道建立方法及相关装置 Download PDF

Info

Publication number
WO2022105807A1
WO2022105807A1 PCT/CN2021/131280 CN2021131280W WO2022105807A1 WO 2022105807 A1 WO2022105807 A1 WO 2022105807A1 CN 2021131280 W CN2021131280 W CN 2021131280W WO 2022105807 A1 WO2022105807 A1 WO 2022105807A1
Authority
WO
WIPO (PCT)
Prior art keywords
domain
access
network device
edge computing
cross
Prior art date
Application number
PCT/CN2021/131280
Other languages
English (en)
French (fr)
Inventor
曾侃
张营
侯玉柱
夏渊
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Publication of WO2022105807A1 publication Critical patent/WO2022105807A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W16/00—Network planning, e.g. coverage or traffic planning tools; Network deployment, e.g. resource partitioning or cells structures
    • H04W16/18—Network planning tools
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/16—Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]

Definitions

  • the present invention relates to the field of communication technologies, in particular to a method for deploying a service instance, a method for establishing a cross-domain mutual access channel, and a related device.
  • OTT Over The Top
  • MEC Multi-access Edge Computing
  • ETSI European Telecommunications Standards Institute
  • the present application provides a method for deploying a service instance, a method for establishing a cross-domain mutual access channel, and a related device, which reduce the operation and maintenance cost of MEC APP online and service enablement.
  • an embodiment of the present application provides a method for deploying a service instance, where the execution body of the method may be a first network device, or may be a chip applied in the first network device.
  • the following description will be given by taking the execution subject being the first network device as an example.
  • the first network device belongs to the multi-access edge computing system, and the multi-access edge computing system further includes a second network device and a third network device, wherein the first network device is located at the center side of the multi-access edge computing system, and the first network device is located on the central side of the multi-access edge computing system.
  • the second network device is located in the network domain on the edge side of the multi-access edge computing system
  • the third network device is located in the computing domain on the edge side of the multi-access edge computing system
  • the method includes: acquiring the multi-access edge computing application program description information; Receive topology information of the multi-access edge computing application from the third network device; send the first request information to the second network device according to the description information of the multi-access edge computing application and the topology information of the multi-access edge computing application, and sending second request information to the third network device, where the first request information is used to instruct the second network device to deploy the first multi-access edge computing service instance corresponding to the multi-access edge computing application in the network domain, and the second request The information is used to instruct the third network device to deploy the second multi-access edge computing service instance corresponding to the multi-access edge computing application in the computing domain.
  • the first network device in the embodiment of the present application, compared with the existing standard architecture of the multi-access edge technology defined by ETSI, in the multi-edge access of the present application, the first network device is deployed on the center side, and the first network device is deployed on the edge side.
  • the second network device is deployed in the network domain and the third network device is deployed in the computing domain on the edge side, so that after the multi-access edge computing application goes online and completes the instantiation, for example, the service is registered with the multi-access edge computing platform.
  • the third network device After the registration message (the topology information of the multi-access edge computing application), the third network device sends the topology information of the multi-access edge computing application forwarded by the multi-access edge computing platform to the first network device, so that the first network The device instructs the second network device to deploy the first multi-access edge computing service instance in the network domain and the third network device to deploy the second instance in the computing domain according to the topology information and the pre-obtained multi-access edge application description information.
  • Multi-access edge computing service instances so that after the instantiation of multi-access edge computing applications is completed, the corresponding multi-access edge computing service instances are automatically deployed in the network domain and computing domain on the edge side, without manual configuration, reducing the cost of Operational and maintenance costs of multi-access edge computing applications.
  • the coordination between the first network device, the second network device and the third network device completes the automatic deployment of multi-access edge computing applications, so that no manual participation is required, and the multi-access edge computing site does not need to be deployed.
  • the location information (that is, the deployment location of multi-access edge computing applications) is open to the information providers of multi-access edge computing applications, which is conducive to improving the competitiveness of telecom operators and protecting the security of multi-access edge computing sites.
  • the topology information is determined by the third network device according to a service registration message of the multi-access edge computing application, and the service registration message is the multi-access edge computing application registered with the network domain.
  • the computing platform is issued to the third network device by the multi-access edge computing platform of the network domain.
  • the third network device subscribes the service registration message of the multi-access edge computing application to the multi-access edge computing platform, so that after the multi-access edge computing application is instantiated online, the multi-access edge computing platform will Publish the service registration message of the multi-access edge computing application to the third network device, so that the third network device can automatically discover that the multi-access edge computing application is online without manual participation, thus facilitating subsequent multi-access edge computing services
  • the deployment of instances improves the online efficiency of multi-access edge computing applications.
  • the first request message includes a first edge access computing service and a first network resource corresponding to the first edge access computing service; the first request message is used to instruct the second network device to The topology information of the edge computing application, the first edge access computing service and the first network resources are entered, and the first multi-access edge computing service instance is deployed, and the first multi-access edge computing service instance is used to provide the first edge access computing services.
  • the first network device only allocates the first multi-access edge computing service and the first network resources that need to be deployed in the network domain to the second network device, and the second network device makes an autonomous decision on the The instantiation of the first multi-access edge computing service is completed locally, and the first multi-access edge computing service instance is locally deployed. Since the first network device only needs to complete the assignment of resources and multi-access edge services, the computing pressure of the first network device is reduced, and the stability of the work of the first network device is improved.
  • the first request message is further used to instruct the second network device to generate a first business rule corresponding to the first multi-access edge computing service instance, and insert the first multi-access edge computing service instance into the first multi-access edge computing service instance The first business rule.
  • the first network device can also instruct the second network device to generate the first business rule corresponding to the first multi-access edge computing service instance through the first request message, without manual configuration on the network
  • the business rules of the multi-access edge computing service instance deployed in the domain improve the automation of business rule generation in the network domain, and improve the service enabling efficiency after the multi-access edge computing application goes online.
  • the second request message includes a second edge access computing service and a second network resource corresponding to the second edge access computing service; the second request message is used to instruct the third network device to Enter the topology information of the edge computing application, the second edge access computing service and the second network resources, deploy a second multi-access edge computing service instance, and the second multi-access edge computing service instance is used to provide the first edge access computing services.
  • the first network device only allocates the second multi-access edge computing service and the second network resources that need to be deployed in the computing domain to the third network device, and the third network device makes an autonomous decision to The instantiation of the second multi-access edge computing service is completed locally, and the second multi-access edge computing service instance is locally deployed. Because the first network device only needs to complete the assignment of network resources and multi-access edge services required by the computing domain, the computing pressure of the first network device is reduced, and the stability of the work of the first network device is improved.
  • the second request message is further used to instruct the third network device to generate a second business rule corresponding to the second multi-access edge computing service instance, and insert it into the second multi-access edge computing service instance Second business rule.
  • the first network device can also instruct the third network device to generate the second business rule corresponding to the second multi-access edge computing service instance through the second request message, without manual configuration in the computing
  • the business rules of multi-access edge computing service instances deployed in the domain improve the automation of business rule generation in the computing domain and improve the online efficiency of multi-access edge computing applications.
  • the method further includes: receiving a first response message from the second network device, where the first response message includes downlink cross-domain channel parameters;
  • the second request message includes downlink cross-domain channel parameters, and the second request message is further used to instruct the third network device to establish a cross-domain mutual access channel between the network domain and the computing domain according to the downlink cross-domain channel parameters.
  • the downlink cross-domain channel parameter is the cross-domain channel parameter of the cross-domain channel service instance deployed in the network domain.
  • the downlink cross-domain channel parameter is sent to the first network device through the first response message, and the first network device passes the second
  • the request message sends the downlink cross-domain channel parameters to the third network device, so that the cross-domain channel service instance of the computing domain and the cross-domain access service instance in the computing domain can use the downlink cross-domain channel parameters and the upstream cross-domain of the local end of the computing domain.
  • the cross-domain access service is automatically established, and the computing domain and the computing domain are connected.
  • the channel between the network domains does not need to manually open up the network domain and the computing domain, thereby reducing the operation and maintenance cost of multi-access edge computing applications and improving the online efficiency of multi-access edge computing.
  • the method further includes: receiving a second response message from the third network device, where the second response message includes uplink cross-domain channel parameters;
  • the network device sends a third request message, where the third request message includes the upstream cross-domain channel parameters, and the third request message is used to instruct the second network device to establish a connection between the network domain and the computing domain according to the upstream cross-domain channel parameters and the downlink cross-domain channel parameters.
  • the uplink cross-domain access channel parameters are sent to the first network device, so that the first network device forwards the cross-domain access channel parameters to the second network device, so that the cross-domain access service instance in the network domain can use the uplink cross-domain access channel parameters.
  • Domain access channel parameters and local downlink cross-domain access channel parameters, cross-domain access to the computing domain that is, when the network domain and the computing domain are deployed separately, the channel between the network domain and the computing domain can be automatically opened without manual participation.
  • the method further includes: sending a fourth request message to the second network device, where the fourth request message is used to instruct the second network device to notify the user plane function entity of the network domain to enable the first service rule,
  • the user plane functional entity is determined by the second network device according to the topology information of the multi-access edge computing application.
  • the first network device individually instructs the user plane functional entity of the network domain to disable the first service rule generated before through the fourth request message.
  • multi-access edge computing applications cannot provide edge content. After multiple attempts by the user equipment, the user plane functional entity on the edge side will transfer the user data packets to the center side to obtain data content. On the contrary, the communication delay of the user is increased.
  • the multi-access edge computing application on the edge side will directly forward the user data packets to the center side without will affect the communication needs of users.
  • the first network device sends the fourth request message to the second network device, generally speaking, it is because the first network device determines that all service instances in the multi-access edge computing application have been enabled and taken effect. , which can normally provide edge content to user devices.
  • the method further includes: receiving a third response message from the second network device, where the third response message is used to instruct the user plane function entity to complete the enabling of the first service rule.
  • the method further includes: sending a fifth request message to the policy control function on the central side, where the fifth request message includes the instance identifier and location information of the multi-access edge computing application, and the fifth request message uses to instruct the policy control function to forward the instance identification and location information of the multi-access edge computing application to the session management function on the central side, so that the session management function selects the user plane functional entity according to the location information of the multi-access edge computing application, So that the user plane functional entity establishes the user session context, and inserts the instance identifier of the multi-access edge computing application.
  • the first network device can also send a fifth request message to the policy control function on the center side, so as to insert the instance information and location information of the newly launched multi-access edge computing application into the edge
  • the corresponding user plane functional entity on the side, and a user conversation document is recommended. There is no need to manually insert instance information and location information of the newly launched multi-access edge computing application into the insertion policy control function, which reduces labor costs.
  • the method before receiving the topology information of the multi-access edge computing application from the third network device, the method further includes: subscribing the access statistics of the application to a network data analysis function; according to the access statistics of the application data and service policy, and send first prompt information to the third network device, where the first prompt information is used to instruct the third network device to notify the network function virtualization infrastructure deployment of the computing domain to provide multiple access to edge content for applications Edge computing applications.
  • the first network device can also subscribe to the network data analysis function in advance for the access statistics of the application, so that the first network device can use the pre-injected service policy and the currently obtained application access Data, automatically trigger the launch and deployment of multi-access edge computing applications, without the need to manually trigger the launch and deployment of multi-access edge computing applications, improve the intelligence of the online and deployment of multi-access edge computing applications, reduce The manual deployment cost of multi-access edge computing applications.
  • the method before receiving the topology information of the multi-access edge computing application from the third network device, the method further includes: obtaining a sixth request message from the application provider, where the sixth request message is used to request deployment A multi-access edge computing application that provides edge content for applications; according to the sixth request message, first prompt information is sent to the third network device, where the first prompt information is used to instruct the third network device to notify the network function virtual of the computing domain Deploying multi-access edge computing applications for delivering edge content to applications.
  • the first network device can also receive the sixth request message from the application provider, and automatically trigger the deployment of the multi-access edge application according to the application provider's request, so as to improve the multi-access edge Flexibility and ease of application deployment.
  • an embodiment of the present application provides a method for deploying a service instance, where the execution body of the method may be a second network device, or may be a chip applied in the second network device.
  • the second network device belongs to the multi-access edge computing system, and the multi-access edge computing system further includes a first network device and a third network device, wherein the first network device is located at the center side of the multi-access edge computing system, and the first network device is located on the center side of the multi-access edge computing system.
  • the second network device is located in the network domain on the edge side of the multi-access edge computing system
  • the third network device is located in the computing domain on the edge side of the multi-access edge computing system
  • the method includes: receiving a first request message from the first network device,
  • the first request message is generated by the first network device according to the description information of the multi-access edge computing application and topology information of the multi-access edge computing application, and the topology information of the multi-access edge computing application is sent by the second network device.
  • To the first network device deploying the first multi-access edge computing service instance corresponding to the multi-access edge computing application program in the network domain according to the first request message.
  • the second network device can automatically deploy the first multi-access edge computing service instance in the network domain according to the first request information received from the first network device, without manual participation in the network domain
  • the deployment of multi-access edge service instances based on the Internet of Things improves the online efficiency of multi-access edge computing applications and reduces operation and maintenance costs.
  • the coordination between the first network device, the second network device and the third network device completes the automatic deployment of multi-access edge computing applications, so that no manual participation is required, and the multi-access edge computing site does not need to be deployed.
  • the location information (that is, the deployment location of multi-access edge computing applications) is open to the information providers of multi-access edge computing applications, which is conducive to improving the competitiveness of telecom operators and protecting the security of multi-access edge computing sites.
  • the topology information is determined by the third network device according to a service registration message of the multi-access edge computing application, and the service registration message is the multi-access edge computing application registered with the network domain.
  • the computing platform is issued to the third network device by the multi-access edge computing platform of the network domain.
  • the third network device subscribes the service registration message of the multi-access edge computing application to the multi-access edge computing platform, so that after the multi-access edge computing application is instantiated online, the multi-access edge computing platform will Publish the service registration message of the multi-access edge computing application to the third network device, so that the third network device can automatically discover that the multi-access edge computing application is online without manual participation, thus facilitating subsequent multi-access edge computing services
  • the deployment of instances improves the online efficiency of multi-access edge computing applications.
  • the first request message includes a first edge access computing service and a first network resource corresponding to the first edge access computing service
  • the multi-access edge is deployed in the network domain according to the first request message
  • the first multi-access edge computing service instance corresponding to the computing application includes: deploying the first multi-access edge computing according to the topology information of the multi-access edge computing application, the first edge access computing service and the first network resources A service instance, wherein the first multi-access edge computing service instance is used to provide the first edge access computing service.
  • the first network device only allocates the first multi-access edge computing service and the first network resources that need to be deployed in the network domain to the second network device; then, the second network device makes an autonomous decision The instantiation of the first multi-access edge computing service is completed locally, and the first multi-access edge computing service instance is locally deployed.
  • the first network device only needs to complete the assignment of resources and multi-access edge services, thereby reducing the computational pressure of the first network device and improving the stability of the first network device.
  • the second network device has an autonomous decision-making function, if the first multi-access edge computing service instance is subsequently changed (for example, failure or business rules are changed), the second network device can autonomously determine the first multi-access edge computing service instance. It is not necessary to report to the first network device, thereby improving the update efficiency of the multi-access edge computing service instance of the network domain.
  • the method further includes: generating a first multi-access edge computing service instance corresponding to the first multi-access edge computing application. the first business rule corresponding to the edge computing service instance, and insert the first business rule into the first multi-access edge computing service instance.
  • the second network device can also automatically generate a first service rule corresponding to the first multi-access edge computing service instance, and insert the first service into the first multi-access edge computing service instance It is not necessary to manually configure the first business rule and insert the first business rule, further reducing the operation and maintenance cost of the multi-access edge computing application, and improving the online efficiency of the multi-access edge computing application.
  • the method further includes: sending a first response message to the first network device, where the first response message includes downlink cross-domain channel parameters, so that the third network device establishes a network domain according to the downlink cross-domain channel parameters The cross-domain mutual access channel between the computing domain and the computing domain.
  • the second network device generates the downlink cross-domain channel parameters of the local end, and gives the downlink cross-domain channel parameters to the second network device, so that even in the case of separate deployment of the network domain and the computing domain Since the second network device and the third network device have obtained the uplink cross-domain channel parameters and the downlink cross-domain channel parameters, the cross-domain access channel can be automatically established, and the channel between the computing domain and the network domain can be opened without manually opening the network domain. and computing domain, thereby reducing the operation and maintenance cost of multi-access edge computing applications and improving the online efficiency of multi-access edge computing.
  • the method further includes: after sending the first response message to the first network device, the method further includes: receiving a third request message from the first network device, the third said third request message Including uplink cross-domain channel parameters; according to uplink cross-domain channel parameters and downlink cross-domain channel parameters, establish a cross-domain mutual access channel between the network domain and the computing domain.
  • the second network device can establish a cross-domain mutual access channel according to the downlink cross-domain channel parameters generated by the local end and the cross-domain mutual access channel generated by the third network device, so that a multi-access edge computing application goes online.
  • the network domain and the computing domain can be opened without manual participation, thereby reducing the operation and maintenance cost of multi-access edge computing applications and improving the multi-access edge computing. online efficiency.
  • the method further includes: receiving a fourth request message from the first network device; determining a user plane functional entity of the network domain according to the topology information of the application; notifying the network according to the user plane functional entity of the network domain The user plane functional entity of the domain enables the first service rule.
  • the second network device independently enables the first service rule generated before according to the fourth request message, which is reserved for the enabling and validating of the service instance in the multi-access edge computing application.
  • the first service rule and the second service rule are directly enabled, but the service instance in the multi-access edge computing application has not yet taken effect, when the user equipment performs local offloading on the edge side, the multi-access edge Computing applications will not be able to provide edge content.
  • the user plane function entity on the edge side will transfer user data packets to the center side to obtain data content, which increases the communication delay for users.
  • the multi-access edge computing application on the edge side will directly forward the user data packets to the center side without will affect the communication needs of users.
  • an embodiment of the present application provides a method for deploying a service instance, where the execution body of the method may be a third network device, or may be a chip applied in the third network device.
  • the following description will be given by taking the execution subject being the third network device as an example.
  • the third network device belongs to the multi-access edge computing system, and the multi-access edge computing system further includes a first network device and a second network device, wherein the first network device is located at the center side of the multi-access edge computing system, and the first network device is located on the center side of the multi-access edge computing system.
  • the second network device is located in the network domain on the edge side of the multi-access edge computing system
  • the third network device is located in the computing domain on the edge side of the multi-access edge computing system.
  • the method includes: sending the multi-access edge computing system to the first network device. topology information of the application; receiving a second request message from the first network device, where the second request message is generated by the first network device according to the multi-access edge computing application description information and the topology information of the multi-access edge computing application; A second multi-access edge computing service instance corresponding to the multi-access edge computing application is deployed in the network domain according to the second request message.
  • the third network device can send the topology information of the multi-access edge computing application program to the first network device, In this way, the third network device can automatically deploy the second multi-access edge computing service instance in the computing domain according to the second request information received from the first network device, without manual participation in the deployment of the multi-access edge computing service instance in the computing domain, It improves the online efficiency of multi-access edge computing applications and reduces operation and maintenance costs.
  • the coordination between the first network device, the second network device and the third network device completes the automatic deployment of multi-access edge computing applications, so that no manual participation is required, and the multi-access edge computing site does not need to be deployed.
  • the location information (that is, the deployment location of multi-access edge computing applications) is open to the information providers of multi-access edge computing applications, which is conducive to improving the competitiveness of telecom operators and protecting the security of multi-access edge computing sites.
  • the second request message includes a second edge access computing service and a second network resource corresponding to the second edge access computing service
  • the second request message includes the second edge access computing service and a
  • the second network resource corresponding to the second edge access computing service includes: deploying the second multi-access edge computing service according to the topology information of the multi-access edge computing application, the second edge access computing service and the second network resource Example, wherein the second multi-access edge computing service instance is used to provide the first edge access computing service.
  • the first network device only allocates the second multi-access edge computing service and the second network resources that need to be deployed in the computing domain to the third network device; then, the third network device makes an autonomous decision The instantiation of the second multi-access edge computing service is completed locally, and the second multi-access edge computing service instance is locally deployed.
  • the first network device only needs to complete the assignment of resources and multi-access edge services, thereby reducing the computational pressure of the first network device and improving the stability of the first network device.
  • the third network device has an autonomous decision-making function
  • the second multi-access edge computing service instance is subsequently changed (for example, invalid or business rules are changed)
  • the second network device can autonomously determine the second multi-access edge computing service instance. It is not necessary to report to the first network device, thereby improving the update efficiency of the multi-access edge computing service instance in the computing domain.
  • the method further includes: generating a second business rule corresponding to the second multi-access edge computing service instance, and inserting the second business rule into the second multi-access edge computing service instance.
  • the third network device can also automatically generate a second business rule corresponding to the second multi-access edge computing service instance, and insert the third-person business rule into the second multi-access edge computing service instance , without the need to manually configure the second business rule and insert the second business rule, further reducing the operation and maintenance cost of the multi-access edge computing application, and improving the online efficiency of the multi-access edge computing application.
  • the method further includes: sending a second response message to the first network device, where the second response message includes uplink cross-domain channel parameters, so that the second network device establishes a network according to the uplink cross-domain channel parameters The cross-domain mutual access channel between the domain and the computing domain.
  • the third network device generates the upstream cross-domain channel parameters of the local end, and gives the upstream cross-domain channel parameters to the second network device, so that even in the case of separate deployment of the network domain and the computing domain Since the second network device and the third network device have obtained the uplink cross-domain channel parameters and the downlink cross-domain channel parameters, the cross-domain access channel can be automatically established, and the channel between the computing domain and the network domain can be opened without manually opening the network domain. and computing domain, thereby reducing the operation and maintenance cost of multi-access edge computing applications and improving the online efficiency of multi-access edge computing.
  • the second request message includes downlink cross-domain channel parameters
  • the method further includes: establishing a cross-domain mutual access channel between the network domain and the computing domain according to the downlink cross-domain channel parameters.
  • the third network device can automatically establish a cross-domain access channel according to the uplink cross-domain channel parameters and downlink cross-domain channel parameters, and open the channel between the computing domain and the network domain, without manually opening the network. domain and computing domain, thereby reducing the operation and maintenance cost of multi-access edge computing applications and improving the online efficiency of multi-access edge computing.
  • the method before sending the topology information of the multi-access edge computing application to the first network device, the method further includes: receiving first prompt information from the first network device; notifying the computing domain according to the first prompt information
  • the Network Functions Virtualization infrastructure is deployed for multi-access edge computing applications serving applications with edge content.
  • the third network device can also receive the first prompt information from the first network device, and automatically trigger the deployment of the multi-access edge computing application according to the instructions of the first network device, without manually triggering the multi-access edge computing application. into edge computing applications, thereby improving the deployment and launch efficiency of multi-access edge computing applications.
  • the first prompt information is generated by the first network device according to the access statistics of the application and the service policy or generated according to the sixth request message obtained from the application provider.
  • the sixth request message Used for requesting deployment of multi-access edge computing applications that provide edge content to applications.
  • the first prompt information can be generated according to the access statistics of the application, or according to the request of the application information provider, thereby improving the flexibility of automatic deployment of multi-access edge computing applications.
  • an embodiment of the present application provides a method for establishing a cross-domain mutual access channel, where the execution body of the method may be a fifth network device, or may be a chip applied in the fifth network device.
  • the execution body of the method may be a fifth network device, or may be a chip applied in the fifth network device.
  • the following description is given by taking the execution subject being the fifth network device as an example.
  • the fifth network device belongs to the cross-domain mutual access system, and the cross-domain mutual access system further includes a fourth network device and a sixth network device, wherein the fourth network device is located at the center side of the cross-domain mutual access system, and the fifth network device is located in the first computing domain of the cross-domain mutual access system, and the sixth network device is located in the second computing domain of the cross-domain mutual access system; the method includes: sending instance information of the second computing domain and the first computing domain to the fourth network device The first cross-domain channel parameter of the first multi-access edge computing service instance used for cross-domain mutual access in the second computing domain; the second multi-access edge computing service used for cross-domain access in the second computing domain is received from the fourth network device The second cross-domain channel parameter of the instance; wherein the first cross-domain channel parameter and the second cross-domain channel parameter are used to characterize the crossover between the first multi-access edge computing service instance and the second multi-access edge computing service instance. Domain mutual access channel.
  • the fifth network device in the process of the multi-access edge computing application performing cross-domain access, can give the first cross-domain channel parameters of the local end to the second network device through the fourth network device.
  • the sixth network device of the computing domain, and the second cross-domain channel parameter of the second computing domain can be obtained through the fourth network device, so that the fifth network device can obtain the second cross-domain channel parameter according to the first cross-domain channel parameter and the second cross-domain channel
  • Establishing the cross-domain mutual access channel between the first computing domain and the second computing domain it can be seen that in the process of establishing the cross-domain mutual access channel, the establishment of the cross-domain mutual access channel can be automatically completed without manual participation, reducing the The operation and maintenance cost of multi-access edge computing applications.
  • the instance information of the second computing domain and the first cross-domain channel parameter of the first multi-access edge computing service instance used for cross-domain mutual access in the first computing domain are sent to the fourth network device
  • the method further includes: receiving a cross-domain mutual access request from the first multi-access edge computing platform of the first computing domain, where the cross-domain mutual access request is sent by the first multi-access edge computing application of the first computing domain
  • the cross-domain mutual access request includes instance information of the second computing domain
  • the cross-domain mutual access request is used to indicate The first multi-access edge computing application in the first computing domain requests cross-domain access to the second multi-access edge computing application in the second computing domain.
  • the method before receiving the cross-domain mutual access request from the first multi-access edge computing platform of the first computing domain, the method further includes: subscribing the first multi-access edge computing platform to the first multi-access edge computing platform Cross-domain mutual access requests for edge computing applications.
  • the fifth network device subscribes to the first multi-access edge computing application platform in advance for the cross-domain access request of the first multi-access edge computing application in the first computing domain, so that when the When a multi-access edge computing application has a cross-domain access requirement, the fifth network device can automatically discover the cross-domain access requirement without manual participation, thereby improving the efficiency of establishing a cross-domain mutual access channel.
  • the instance information of the second computing domain and the first cross-domain channel parameter of the first multi-access edge computing service instance used for cross-domain mutual access in the first computing domain are sent to the fourth network device Before, the method further includes: deploying the first multi-access edge computing service instance in the first computing domain and configuring the first cross-domain channel parameter.
  • the fifth network device can also deploy the first multi-access edge computing service instance on demand, for example, there is no multi-access edge service instance for cross-domain access in the first computing domain , the first multi-access edge computing service instance is automatically deployed, so as to achieve fully automatic establishment of cross-domain mutual access channels.
  • the method further includes: configuring the first multi-access edge computing service instance and the first multi-access edge computing service instance A first routing parameter between multi-access edge computing applications; after receiving the second cross-domain channel parameter of the second multi-access edge computing service instance used for cross-domain access in the second computing domain from the fourth network device , the method further includes: sending a cross-domain mutual access response to the first multi-access edge computing platform, and instructing the first multi-access edge computing platform to forward the cross-domain mutual access response to the first multi-access edge computing application,
  • the cross-domain mutual access response includes a first routing parameter, and the cross-domain access response is used to instruct the first multi-access edge computing application to establish the first multi-access edge computing service instance and the first multi-access edge computing application according to the first routing parameter.
  • a communication link between computing applications is used to instruct the first multi-access edge computing application to establish the first multi-access edge computing service instance and the first multi-access edge computing application according to the first routing parameter.
  • the fifth network device also configures the first routing parameter to the first multi-access edge computing application and the first multi-access edge computing service instance, thereby automatically opening up the first multi-access The communication link between the edge computing application and the first multi-access edge computing service instance without manual participation.
  • an embodiment of the present application provides a method for establishing a cross-domain mutual access channel, where the execution subject of the method may be a sixth network device, or may be a chip applied in the sixth network device.
  • the execution subject of the method may be a sixth network device, or may be a chip applied in the sixth network device.
  • the following description will be given by taking the execution subject being the sixth network device as an example.
  • the sixth network device belongs to the cross-domain mutual access system, and the cross-domain mutual access system further includes a fourth network device and a fifth network device, wherein the fourth network device is located at the center side of the cross-domain mutual access system, and the fifth network device is located in the first computing domain of the cross-domain mutual access system, and the sixth network device is located in the second computing domain of the cross-domain mutual access system; the method includes: receiving, from the fourth network device, the first computing domain used for cross-domain mutual access in the first computing domain.
  • a first cross-domain channel parameter of the multi-access edge computing service instance sending the second cross-domain channel parameter of the second multi-access edge computing service instance used for cross-domain mutual access in the second computing domain to the fourth network device , wherein the first cross-domain channel parameter and the second cross-domain channel parameter are used to represent the cross-domain mutual access channel between the first multi-access edge computing service instance and the second multi-access edge computing service instance.
  • the sixth network device in the process of the multi-access edge computing application performing cross-domain access, can receive the second cross-domain of the opposite end (second computing domain) through the fourth network device channel parameters, and the second cross-domain channel parameters of the local end can be given to the fifth network device of the opposite end through the fourth network device, so that the fifth network device and the sixth network device can
  • the second cross-domain channel parameter establishes the cross-domain mutual access channel between the first computing domain and the second computing domain. It can be seen that in the process of establishing the cross-domain mutual access channel, the cross-domain mutual access can be automatically completed without manual participation. The establishment of the channel reduces the operation and maintenance cost of enabling cross-domain mutual access channels.
  • the method before sending the second cross-domain channel parameter of the second multi-access edge computing service instance used for cross-domain mutual access in the second computing domain to the fourth network device, the method further includes: sending the second cross-domain channel parameter to the second computing domain for cross-domain mutual access.
  • the second multi-access edge computing platform in the second computing domain subscribes to the online of the second multi-access edge computing service instance for cross-domain mutual access.
  • the sixth network device subscribes to the second multi-access edge computing platform in advance for the online of the second multi-access edge computing service instance, so that the sixth network device is receiving cross-domain data from other computing domains.
  • the method before sending the second cross-domain channel parameter of the second multi-access edge computing service instance used for cross-domain mutual access in the second computing domain to the fourth network device, the method further includes: The second computing domain deploys a second multi-access edge computing service instance and configures second cross-domain channel parameters.
  • the sixth network device can decide to deploy the second multi-access edge computing service instance according to the demand, so that even if there is no corresponding service instance during cross-domain mutual access, the It can be deployed automatically, so as to achieve fully automatic establishment of cross-domain mutual access channels.
  • the method further includes: configuring the second multi-access edge computing service instance with the first The second routing parameter between two multi-access edge computing applications, and the second routing parameter is configured to the second multi-access edge computing service instance and the second multi-access edge computing platform of the second computing domain.
  • the multi-access edge computing platform is configured to forward the second routing parameter to the second multi-access edge computing application, where the second routing parameter is used for the second multi-access edge computing service instance and the second multi-access edge computing application Establish a communication link.
  • the sixth network device also configures the second routing parameters to the second multi-access edge computing application and the second multi-access edge computing service instance, thereby automatically opening up the second multi-access The communication link between the edge computing application and the second multi-access edge computing service instance without human involvement.
  • an embodiment of the present application provides a method for establishing a cross-domain mutual access channel, where the execution body of the method may be a fourth network device or a chip applied in the fourth network device.
  • the execution body of the method may be a fourth network device or a chip applied in the fourth network device.
  • the following description will be given by taking the execution subject being the fourth network device as an example.
  • the fourth network device belongs to the cross-domain mutual access system, and the cross-domain mutual access system further includes a fifth network device and a sixth network device, wherein the fourth network device is located at the center side of the cross-domain mutual access system, and the fifth network device is located in the first computing domain of the cross-domain mutual access system, and the sixth network device is located in the second computing domain of the cross-domain mutual access system; the method includes: receiving the instance information of the second computing domain and the first computing domain from the fifth network device The first cross-domain channel parameter of the first multi-access edge computing service instance used for cross-domain mutual access; according to the instance information of the second computing domain, the first cross-domain channel parameter is sent to the sixth network device; from the sixth network The device receives the second cross-domain channel parameter of the second multi-access edge computing service instance used for cross-domain mutual access in the second computing domain; Two second cross-domain channel parameters of the multi-access edge computing service instance; wherein, the first cross-domain channel parameter and the second cross-domain channel parameter are used to characterize the first multi
  • the fourth network device can forward the first multi-access edge computing service to the sixth network device
  • the first cross-domain channel parameter of the instance, and the second cross-domain channel parameter of the second multi-access edge computing service instance is forwarded to the fifth network device, so that both the fifth network device and the sixth network device can obtain the first cross-domain channel parameter.
  • Domain channel parameters and second cross-domain channel parameters thereby automatically establishing a cross-domain mutual access channel between the first computing domain and the second computing domain, without manual participation, reducing the operation and maintenance cost of multi-access edge computing applications .
  • an embodiment of the present application provides a communication device, and the beneficial effects can be referred to the description of the first aspect and will not be repeated here.
  • the communication device has a function to implement the behavior in the method example of the first aspect above.
  • the functions can be implemented by hardware, or by executing corresponding software by hardware.
  • the hardware or software includes one or more modules corresponding to the above functions.
  • the communication apparatus includes: a transceiver module for acquiring description information of the multi-access edge computing application, and receiving topology information of the multi-access edge computing application from a third network device; a processing module for using The control transceiver module sends the first request information to the second network device and the second request information to the third network device according to the description information of the multi-access edge computing application and the topology information of the multi-access edge computing application.
  • a request message is used to instruct the second network device to deploy the first multi-access edge computing service instance corresponding to the multi-access edge computing application in the network domain, and the second request message is used to instruct the third network device to deploy and The second multi-access edge computing service instance corresponding to the multi-access edge computing application.
  • These modules may perform the corresponding functions in the method example of the first aspect. For details, please refer to the detailed description in the method example of the first aspect, which will not be repeated here.
  • an embodiment of the present application provides a communication device, and the beneficial effects can be referred to the description of the second aspect and will not be repeated here.
  • the communication device has a function to implement the behavior in the method example of the second aspect above.
  • the functions can be implemented by hardware, or by executing corresponding software by hardware.
  • the hardware or software includes one or more modules corresponding to the above functions.
  • the communication apparatus includes: a transceiver module, configured to receive a first request message from the first network device, where the first request message is the first network device according to the multi-access edge computing application description information and the multi-access edge computing It is generated from the topology information of the incoming edge computing application, and the topology information of the multi-access edge computing application is sent by the second network device to the first network device; the processing module is used for deploying and The first multi-access edge computing service instance corresponding to the multi-access edge computing application.
  • These modules can perform the corresponding functions in the method example of the second aspect. For details, refer to the detailed description in the method example of the second aspect, which will not be repeated here.
  • an embodiment of the present application provides a communication device, and the beneficial effects can be referred to the description of the third aspect and will not be repeated here.
  • the communication device has a function to implement the behavior in the method example of the third aspect above.
  • the functions can be implemented by hardware, or by executing corresponding software by hardware.
  • the hardware or software includes one or more modules corresponding to the above functions.
  • the communication apparatus includes: a transceiver module, configured to send topology information of the multi-access edge computing application to the first network device, and receive a second request message from the first network device, the second request message It is generated by the first network device according to the description information of the multi-access edge computing application and the topology information of the multi-access edge computing application; the processing module is used for deploying the multi-access edge computing application in the network domain according to the second request message.
  • the second multi-access edge computing service instance corresponding to the program.
  • an embodiment of the present application provides a communication device, and for beneficial effects, reference may be made to the description of the fourth aspect and will not be repeated here.
  • the communication device has a function to implement the behavior in the method example of the first aspect above.
  • the functions can be implemented by hardware, or by executing corresponding software by hardware.
  • the hardware or software includes one or more modules corresponding to the above functions.
  • the communication apparatus includes: a processing module, configured to control the transceiver module to send the instance information of the second computing domain and the first multi-connection module used for cross-domain mutual access in the first computing domain to the fourth network device receiving the first cross-domain channel parameter of the incoming edge computing service instance; and receiving the second cross-domain channel parameter of the second multi-access edge computing service instance used for cross-domain access in the second computing domain from the fourth network device; wherein, The first cross-domain channel parameter and the second cross-domain channel parameter are used to represent the cross-domain mutual access channel between the first multi-access edge computing service instance and the second multi-access edge computing service instance.
  • These modules can perform the corresponding functions in the method example of the third aspect. For details, please refer to the detailed description in the method example of the third aspect, which will not be repeated here.
  • an embodiment of the present application provides a communication device, and the beneficial effects can be referred to the description of the fifth aspect and will not be repeated here.
  • the communication device has a function to implement the behavior in the method example of the fifth aspect above.
  • the functions can be implemented by hardware, or by executing corresponding software by hardware.
  • the hardware or software includes one or more modules corresponding to the above functions.
  • the communication apparatus includes: a processing module that controls the transceiver module to receive, from a fourth network device, a first cross-domain of the first multi-access edge computing service instance used for cross-domain mutual access in the first computing domain channel parameters; and sending the second cross-domain channel parameters of the second multi-access edge computing service instance used for cross-domain mutual access in the second computing domain to the fourth network device; wherein the first cross-domain channel parameters and the second cross-domain channel parameters
  • the cross-domain channel parameter is used to characterize the cross-domain mutual access channel between the first multi-access edge computing service instance and the second multi-access edge computing service instance.
  • an embodiment of the present application provides a communication device, and the beneficial effects can be referred to the description of the sixth aspect and will not be repeated here.
  • the communication device has a function to implement the behavior in the method example of the sixth aspect above.
  • the functions can be implemented by hardware, or by executing corresponding software by hardware.
  • the hardware or software includes one or more modules corresponding to the above functions.
  • the communication apparatus includes: a processing module configured to control the transceiver module to receive instance information of the second computing domain and a first multi-connection module used for cross-domain mutual access in the first computing domain from the fifth network device Enter the first cross-domain channel parameters of the edge computing service instance; send the first cross-domain channel parameters to the sixth network device according to the instance information of the second computing domain; receive the second computing domain from the sixth network device for cross-domain use The second cross-domain channel parameter of the second multi-access edge computing service instance for mutual access; and sending the second multi-access edge computing service instance of the second multi-access edge computing service instance for cross-domain mutual access in the second computing domain to the fifth network device.
  • Two cross-domain channel parameters wherein, the first cross-domain channel parameter and the second cross-domain channel parameter are used to represent cross-domain mutual access between the first multi-access edge computing service instance and the second multi-access edge computing service instance aisle.
  • These modules can perform the corresponding functions in the method example of the sixth aspect. For details, please refer to the detailed description in the method example of the sixth aspect, which will not be repeated here.
  • an embodiment of the present application provides a communication device, where the communication device may be the first network device in the above method embodiments, or a chip provided in the first network device.
  • the communication device includes a communication interface, a processor, and optionally, a memory.
  • the memory is used to store computer programs or instructions, and the processor is coupled to the memory and the communication interface.
  • the communication apparatus executes the method executed by the first network device in the above method embodiments.
  • an embodiment of the present application provides a communication device, where the communication device may be the second network device in the above method embodiments, or a chip provided in the second network device.
  • the communication device includes a communication interface, a processor, and optionally, a memory.
  • the memory is used to store computer programs or instructions, and the processor is coupled to the memory and the communication interface, and when the processor executes the computer program or instructions, the communication apparatus executes the method executed by the second network device in the above method embodiments.
  • an embodiment of the present application provides a communication device, where the communication device may be the third network device in the above method embodiments, or a chip provided in the third network device.
  • the communication device includes a communication interface, a processor, and optionally, a memory.
  • the memory is used to store computer programs or instructions, and the processor is coupled to the memory and the communication interface.
  • the communication apparatus executes the method executed by the third network device in the above method embodiments.
  • an embodiment of the present application provides a communication apparatus, where the communication apparatus may be the second network device in the above method embodiments, or a chip provided in the fourth network device.
  • the communication device includes a communication interface, a processor, and optionally, a memory.
  • the memory is used to store computer programs or instructions, and the processor is coupled to the memory and the communication interface.
  • the communication apparatus executes the method executed by the fourth network device in the above method embodiments.
  • an embodiment of the present application provides a communication device, where the communication device may be the fifth network device in the above method embodiments, or a chip provided in the fifth network device.
  • the communication device includes a communication interface, a processor, and optionally, a memory.
  • the memory is used to store computer programs or instructions, and the processor is coupled to the memory and the communication interface.
  • the communication apparatus executes the method executed by the fifth network device in the above method embodiments.
  • an embodiment of the present application provides a communication device, where the communication device may be the sixth network device in the above method embodiments, or a chip provided in the sixth network device.
  • the communication device includes a communication interface, a processor, and optionally, a memory.
  • the memory is used to store computer programs or instructions, and the processor is coupled to the memory and the communication interface, and when the processor executes the computer program or instructions, the communication apparatus executes the method executed by the sixth network device in the above method embodiments.
  • a nineteenth aspect provides a computer program product, the computer program product comprising: computer program code, when the computer program code is executed, the method performed by the first network device in the above aspects is performed.
  • a computer program product comprising: computer program code, when the computer program code is executed, the method performed by the second network device in the above aspects is performed.
  • a computer program product comprising: computer program code, when the computer program code is executed, the method performed by the third network device in the above aspects is performed.
  • a computer program product comprising: computer program code, when the computer program code is executed, the method performed by the fourth network device in the above aspects is performed.
  • a computer program product comprising: computer program code, which when executed, causes the method performed by the fifth network device in the above aspects to be performed.
  • a computer program product comprising: computer program code, when the computer program code is executed, the method performed by the sixth network device in the above aspects is performed.
  • the present application provides a chip system, where the chip system includes a processor for implementing the functions of the first network device in the methods of the above aspects.
  • the system-on-a-chip further 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.
  • the present application provides a chip system, where the chip system includes a processor for implementing the functions of the second network device in the methods of the above aspects.
  • the system-on-chip also includes memory for storing program instructions and/or data.
  • the chip system may be composed of chips, or may include chips and other discrete devices.
  • the present application provides a chip system, where the chip system includes a processor for implementing the functions of the third network device in the methods of the above aspects.
  • the system-on-a-chip further 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.
  • the present application provides a chip system, where the chip system includes a processor for implementing the functions of the fourth network device in the methods of the above aspects.
  • the system-on-a-chip further 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.
  • the present application provides a chip system, where the chip system includes a processor for implementing the functions of the fifth network device in the methods of the above aspects.
  • the system-on-a-chip further includes a memory for storing program instructions and/or data.
  • the chip system may be composed of chips, and may also include chips and other discrete devices.
  • the present application provides a chip system, where the chip system includes a processor for implementing the functions of the sixth network device in the methods of the above aspects.
  • the system-on-a-chip further includes a memory for storing program instructions and/or data.
  • the chip system may be composed of chips, and may also include chips and other discrete devices.
  • the present application provides a computer-readable storage medium, where a computer program is stored in the computer-readable storage medium, and when the computer program is executed, the method executed by the first network device in the above aspects is implemented .
  • the present application provides a computer-readable storage medium, where a computer program is stored in the computer-readable storage medium, and when the computer program is executed, the method executed by the second network device in the above aspects is implemented .
  • the present application provides a computer-readable storage medium, where a computer program is stored in the computer-readable storage medium, and when the computer program is executed, the method executed by the third network device in the above aspects is implemented .
  • the present application provides a computer-readable storage medium, where a computer program is stored in the computer-readable storage medium, and when the computer program is executed, the method executed by the fourth network device in the above aspects is implemented .
  • the present application provides a computer-readable storage medium, where a computer program is stored in the computer-readable storage medium, and when the computer program is executed, the method executed by the fifth network device in the above aspects is implemented .
  • the present application provides a computer-readable storage medium, where a computer program is stored in the computer-readable storage medium, and when the computer program is executed, the method executed by the sixth network device in the above aspects is implemented .
  • the present application provides a multi-access edge computing system, including the communication device of the thirteenth aspect, the communication device of the fourteenth aspect, and the communication device of the fifteenth aspect.
  • the present application provides a system for establishing a cross-domain mutual access channel, including the communication device of the sixteenth aspect, the communication device of the seventeenth aspect, and the communication device of the eighteenth aspect.
  • Fig. 1 is the schematic flow chart of a kind of MEC APP on-line deployment of the embodiment of the application;
  • FIG. 2 is a schematic flowchart of establishing a cross-domain mutual access channel for MEC APPs in a computing domain according to an embodiment of the present application
  • FIG. 3 is an architectural diagram of a multi-edge access computing system according to an embodiment of the present application.
  • FIG. 4 is a schematic flowchart of a method for deploying a multi-access edge service instance according to an embodiment of the present application
  • FIG. 5 is a schematic flowchart of another method for deploying a multi-access edge service instance according to an embodiment of the present application
  • FIG. 6 is a schematic flowchart of another method for deploying a multi-access edge service instance according to an embodiment of the present application
  • FIG. 7 is a schematic flowchart of a method for deploying a multi-access edge service instance according to an embodiment of the present application
  • FIG. 8 is a schematic flowchart of a method for establishing a cross-domain mutual access channel according to an embodiment of the present application
  • FIG. 9 is a schematic flowchart of another method for establishing a cross-domain mutual access channel according to an embodiment of the present application.
  • FIG. 10 is a schematic structural diagram of a communication device according to an embodiment of the application.
  • FIG. 11 is a schematic structural diagram of a communication device according to an embodiment of the application.
  • FIG. 12 is a schematic structural diagram of another communication device according to an embodiment of the present application.
  • FIG. 13 is a schematic structural diagram of another communication device according to an embodiment of the present application.
  • the methods in the embodiments of the present application may be applicable to various system architectures, for example, applied to the 5G system architecture.
  • the network architecture and service scenarios described in the embodiments of the present application are for the purpose of illustrating the technical solutions of the embodiments of the present application more clearly, and do not constitute a limitation on the technical solutions provided by the embodiments of the present application.
  • the evolution of the architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of the present application are also applicable to similar technical problems.
  • the user equipment (User Equipment, UE) involved in the embodiments of the present application may include a mobile phone (or referred to as a "cellular" phone), a wireless user equipment, a mobile user equipment, a device-to-device communication (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 (internet) of things, IoT) user equipment, subscriber unit (subscriber unit), subscriber station (subscriber station), mobile station (mobile station), remote station (remote station), access point (access point, AP), remote terminal (remote terminal) terminal), access terminal, user terminal, user agent, or user device, etc.
  • a mobile phone or referred to as a "cellular" phone
  • a wireless user equipment a mobile user equipment
  • a device-to-device communication device-to-device, D2D
  • V2X vehicle
  • ETSI European Telecommunications Standards Institute
  • MEC APP Multi-access Edge Computing Application Orchestrator
  • MEPM Multi-access Edge Computing Platform Manager
  • MEP Multi-access Edge Computing Platform
  • MEP and MEC APP separately from the User Plane Function (UPF) of the 5G core network (5G core).
  • the location of MEP and MEC APP is defined as a computing domain, which is used to complete the deployment of MEC APP, service registration of MEC APP, and activation of domain name system and distribution rules.
  • the location where the UPF is located is defined as the network domain, and the user data is transferred between the N6 interface and the computing domain, and the local offload of the edge site is completed.
  • MEAO requests the edge-side Network Functions Virtualization Infrastructure (NFVI) to allocate resources to the MEC APP through MEPM, such as Virtual Machine (VM) resources and hardware resources;
  • NFVI Network Functions Virtualization Infrastructure
  • the NFVI After the NFVI completes the allocation and deployment of the MEC APP resources, it returns a response to the MEPM, and the response carries the resource instance information of the MEC APP, such as the physical address (MAC Address) of the VM;
  • the MEPM sends the MEC APP instantiation configuration message to the MEP, instructing the MEP to instantiate the application service registered by the MEC APP, and to configure and activate the business rules of the service instance.
  • the MEC APP After the MEC APP completes the instantiation of the application service, it registers the application instance status information (such as application type, application instance identifier, etc., optionally, some applications may be registered with the MEP through the MP1 interface) Not implemented) and service instance status information of each application service instance (for example, the type, identification, IP address, port number (Port), etc. of the application service instance);
  • application instance status information such as application type, application instance identifier, etc., optionally, some applications may be registered with the MEP through the MP1 interface
  • service instance status information of each application service instance for example, the type, identification, IP address, port number (Port), etc. of the application service instance
  • MEP receives the MEC APP instantiation configuration message issued by MEPM in step (4), and receives the service instance status message registered by MEC APP in step (5), and judges that each application service of MEC APP is instantiated After completion, configure the business rules between the local multi-access edge computing service and the MEC APP, and deliver the business rules to Data Plane through the MP2 interface, for example, configure Domain Name System (DNS) rules To the local DNS service instance, and deliver the traffic rule (Traffic Rule) to Data Plane through the MP2 interface;
  • DNS Domain Name System
  • the business rules configured above are for the business rules of the locally deployed multi-access edge computing service instance. If the MEC APP has also applied for other multi-access edge computing services, that is, the multi-access edge computing service is checked in the APPD, and in step 4, the MEC APP instantiation configuration request message carries the same multi-access edge computing service. The parameters corresponding to the edge computing service are issued to the MEP, and before step 6 is executed, the network resources corresponding to the multi-access edge computing service are manually allocated to instantiate the multi-access edge computing service in Data Plane , and finally, configure the business rule of the multi-access edge computing service instance, and insert the business rule.
  • the MEC APP applies for the application load balancing (Application Load Balance, APP LB) service
  • the virtual application network protocol address resource pool (Virtual APP IP Pool) of the APP LB service is manually allocated, and the Virtual APP IP Pool is placed under the Send it to the Data Plane of the edge site where the MEC APP is located to deploy the APP LB service instance in the Data Plane to provide the APP LB service for the MEC APP; finally, configure the business rules between the APP LB service instance and the MEC APP , and insert the business rule in the APP LB service instance.
  • APP IP Pool Application Load Balance
  • the MEP returns a MEC APP instantiation configuration response message to the MEPM, wherein the MEC APP instantiation configuration response message is used to indicate the completion of the instantiation of the MEC APP and the instantiation of the multi-access edge computing service applied for by the MEC APP is completed, That is, it is equivalent to indicating that the user can perform subsequent operations in the network domain;
  • step (13) After completing step (11) and step (12), and manually knowing that the communication link between the MEC APP and the Data Plane is open, then manually issue the ULCL rule activation command to the edge side UPF;
  • the device can perform local distribution through the following steps:
  • A1 During the process of establishing a user session, the PCF inserts the MEC APP instance identifier and location identifier (DNAI) into the SMF for qualified user equipment (for example, user equipment that has signed a subscription plan or user equipment whose geographic location meets the requirements). ;
  • A2 SMF selects a matching edge-side UPF according to the DNAI of the MEC APP, establishes a user session context for the user equipment, and instructs the edge-side UPF to insert the MEC APP instance identifier (APP ID);
  • A3 The UPF at the edge side receives the upstream DNS query packet and user data packet from the user equipment, matches the service rules between the upstream DNS query packet and the user data packet, and distributes the data packet to the corresponding MEC APP.
  • Application service instance to achieve local offloading.
  • the edge content provided for a MEC APP is limited. Therefore, the MEC APP of this computing domain may access the MEC APP of another computing domain across domains, and obtain more data information from the MEC APP of another computing domain.
  • the MEC APP deployed on the edge side can be accessed across domains
  • the public cloud service on the center side that is, the MEC APP on the center side
  • a cross-domain access channel needs to be established first.
  • the following describes the process of establishing a cross-domain access channel by taking the establishment of a cross-domain access channel between the computing domain on the central side and the computing domain on the edge side as an example, which includes the following steps:
  • the MEC APP on the edge side initiates a cross-domain access request of the public cloud service to the MEP, and the cross-domain access request includes the domain name of the public cloud service.
  • the MEP performs DNS query according to the domain name of the cloud service, and registers the public cloud service access API routing rules with the edge side Data Plane;
  • the MEC APP on the edge side accesses public cloud services across domains through the Data Plane on the edge side and the Data Plane on the public cloud, and conforms to the API access rules.
  • the network domain and computing domain mentioned in this application may be located on the edge side, or on the center side, or any location where UPF and MEP of 5GC are deployed, such as a central cloud or a public cloud. That is to say, the service instance deployment method of the present application is not limited to the automatic deployment of multi-access edge computing service instances in the network domain and computing domain on the edge side, but can also be automated in the network domain and computing domain on the central side or other locations. Deploy multi-access edge computing service instances. This application takes the deployment of a multi-access edge computing service instance in the network domain and the computing domain on the edge side as an example for description, and the deployment methods in other locations are similar and will not be described again.
  • the multi-access edge computing system of the present application compared with the MEC standard system, deploys a first network device on the center side, deploys a second network device in the network domain on the edge side, and computes on the edge side.
  • a third network device is deployed in the domain, and the communication link between the first network device and the second network device and the communication link between the first network device and the third network device are opened in advance.
  • this application takes the deployment of the DNS service to the computing domain as an example for description. In practical applications, the DNS service may also be deployed to the network domain, and this application does not limit the deployment location of the DNS service.
  • each device performs different functions and works together to complete the automatic online and automatic deployment of the MEC APP, which is used to provide the MEC APP with multi-access edge computing services.
  • Edge computing service instances automatically generate and enable business rules for multiple access edge computing service instances, and automatically complete the dynamic expansion and contraction of MEC APP and the dynamic update of business rules.
  • the following examples illustrate the functions performed by each device.
  • the MEC APP is used to provide edge content to user equipment and realize the final processing of local offloaded data packets
  • MEAO used to manage MEC APP software packages, orchestrate the business rules/requirements/operation strategies of MEC APP, MEC node selection, trigger MEC APP online, offline and migration;
  • MEPM used to manage network elements of MEP, configure business rules and requirements of MEC APP (including but not limited to MEC APP-dependent service authorization, Traffic Rule, DNS, MEP life cycle management and MEC APP life cycle management);
  • the first network device is used for arranging corresponding multi-access edge computing services for the network domain and computing domain on the edge side according to the service topology information of the APPD and the MEC APP, and allocating corresponding network resources for the multi-access edge computing services, Deliver the multi-access edge computing service and corresponding network resources to the second network device of the network domain on the edge side and the third network device of the computing domain, and forward the second network device and/or the third network device to establish a cross-connection Cross-domain channel parameters required by the domain mutual access channel;
  • the second network device is used to deploy the multi-access edge computing service instance of the network domain, and deliver and activate the business rules of the multi-access edge computing service instance of the network domain to the UPF on the edge side; and the cross-domain mutual access channel Build, release, update;
  • the third network device is used to subscribe to the MEP and process the MEC APP service management related messages (including: MEC APP instance status information registration/update/deletion, MEC APP service instance status information registration/update/deletion, MEC APP service instance status information registration/update/deletion, MEC APP service instance status information registration/update/deletion) APP Traffic Rule activation/deactivation/update) and MP1 extension interface (the request message/response message for MEC APP to apply for the allocation of multi-access edge computing services), as well as the deployment of the multi-access edge computing service instance applied by MEC APP, and to Data Plane issues and activates business rules for multi-access edge computing service instances in computing domains; as well as establishment, release, and update of cross-domain mutual access data channels;
  • MEC APP service management related messages including: MEC APP instance status information registration/update/deletion, MEC APP service instance status information registration/update/deletion, MEC APP service
  • the MEC service platform is used to provide DNS services to the user equipment, return DNS response messages, and process uplink and downlink user data packets between the user equipment and the MEC APP, including the local offload of the user equipment's uplink data in the 5GC and to the MEC Load balancing and offloading of APP, and forwarding of downlink data of MEC APP to 5GC.
  • the first network device obtains the description information of the multi-access edge computing application
  • the multi-access edge computing system is configured by the user to the first network device, for example, the first network device
  • a northbound interface can be provided, and the user can inject the multi-access edge computing application description information into the first network device through the northbound interface
  • the third network device sends the topology information of the multi-access edge computing application to the first network device, wherein,
  • the topology information includes the instance information of the MEC APP and the service instance information of the MEC APP, wherein the instance information of the MEC APP is the basic information of the MEC APP, for example, the MEC APP type (Type), the MEC APP instance identifier (Identity), the MEC APP instance APP domain name (Domain)), where the service instance information of the MEC APP is the basic information of the service instance in the MEC APP, such as Service Name, Service Type, Service Instance ID, Service Instance status, etc.
  • the topology information of the MEC APP is registered to the MEP by the MEC APP in the process of instantiating the service in the MEC APP, and sent by the MEP to the third network device. Therefore, the third network device is sent to the MEP.
  • the topology information of the MEC APP of the first network device is called the topology information registered by the MEC APP;
  • the first network device sends a first request message to the second network device according to the multi-access edge computing application description information and the topology information of the MEC APP , and send the second request message to the third network device;
  • the second network device deploys the first multi-access edge computing service instance corresponding to the MEC APP in the network domain according to the first request message;
  • the second application program device according to the second request The message deploys the second multi-access edge computing service instance corresponding to the MEC APP in the computing domain.
  • the first network device, the second network device, and the third network device work cooperatively to complete the deployment of the MEC service instance corresponding to the MEC APP, without the need for Manual participation improves the online efficiency of MEC APP, reduces the operation and maintenance cost of MEC APP, and improves the deployment intelligence of MEC APP.
  • FIG. 4 provides a service instance deployment method according to an embodiment of the present application, and the method includes the following steps:
  • the first network device obtains description information of a multi-access edge computing application.
  • the multi-access edge computing application description (APPD) information may be configured by a user.
  • the first network device opens a northbound interface, and a user can inject manually arranged APPD information into the first network device through the northbound interface, where the APPD information is used to deploy the MEC APP in the computing domain.
  • the third network device sends the topology information of the multi-access edge computing application to the first network device.
  • the MEC APP needs to be deployed in the computing domain on the edge side.
  • manually arrange APPD and APP image template configure the manually arranged APPD and APP image template to MEAO, and manually trigger the deployment of MEC APP through MEAO.
  • the subsequent deployment of MEC APP is similar to that in Figure 1. , this application does not pay attention to the process of MEC APP.
  • the third network device determines the topology information of the MEC APP according to the service registration message of the MEC APP.
  • the service registration message is registered by the MEC APP to the MEP of the network domain, and issued by the MEP to the third network device.
  • the MEC APP in the process of instantiating the service in the MEC APP, after the instantiation of the service in the MEC APP is completed, the MEC APP will register a service registration message with the MEP, and the service registration message indicates that the service has completed the instance. and the service registration message includes the instance information of the MEC APP and the service instance information; finally, after all the services in the MEC APP are instantiated, the MEC APP registers with the MEP a service to indicate that all the services in the MEC APP are completed.
  • the instantiated service registration information so that the MEP publishes the service registration message registered by the MEC APP to the third network device.
  • the service registration message published by the MEP to the third network device includes the instance information and service instance information registered by the MEC APP, and the third network device can determine the topology information registered by the MEC APP according to the service registration information registered by the MEC APP.
  • the third network device can subscribe the service registration message of the MEC APP to the MEP in advance; in this way, the MEC APP goes online and registers the service registration message with the MEP. After that, the MEP can publish the service registration message registered by the MEC APP to the third network device according to the previous subscription information.
  • the first network device sends the manually arranged APPD to the third network device, and the APPD includes the topology information of the manually arranged MEC APP, in order to distinguish the MEC APP
  • the registered topology information and the topology information described in APPD the topology information describing the MEC APP in APPD can be called manually arranged topology information, wherein the manually arranged topology information includes manually arranged instance information and manually arranged service instance information ;
  • the third network device obtains the manually arranged instance information according to the manually arranged APPD, and subscribes the service registration message of the MEC APP to the MEP according to the manually arranged instance information.
  • the third network device requests the MEP to publish the service registration message of the MEC APP to the third network device when it receives the service registration message registered with the MEC APP corresponding to the APP ID. .
  • the topology information registered by the MEC APP is the real topology information of the MEC APP, and this real topology information may be the same as or different from the manually arranged topology information, which is not limited in this application. For example, 10 service instances are manually arranged in APPD, but only 9 service instances are actually registered in the MEC APP (maybe due to insufficient infrastructure resources or the failure of instantiation of the MEC APP's own services, etc.), then at this time the third network device After returning the MEC APP instantiation configuration response message to the MEPM, it should wait for the manual decision of the management plane (or according to the pre-injected policy of the management plane, such as whether to allow the instantiation of the MEC APP service to be partially successful, and the minimum percentage threshold for allowing partial success) to make an automatic decision.
  • the manual decision of the management plane or according to the pre-injected policy of the management plane, such as whether to allow the instantiation of the MEC APP service to be partially successful, and the minimum percentage threshold for allowing partial success
  • the third network device should report the real service instance information registered by the MEC APP to the first network device, and the first network device will establish the topology information table of the MEC APP based on this. And maintain the topology information of the MEC APP reported by the third network device.
  • the third network device determines, according to the manually arranged topology information and the topology information registered by the MEC APP, that after all services of the MEC APP have been instantiated, the manually arranged service instance information and the MEC APP actually registered services. The information is compared to determine that all services of the MEC APP have been instantiated, and the topology information of the MEC APP registered by the MEC APP is sent to the first network device.
  • the first network device sends first request information to the second network device according to the multi-access edge computing application description information and the topology information of the multi-access edge computing application, where the first request message is used to instruct the second network device A first multi-access edge computing service instance corresponding to the multi-access edge computing application is deployed in the network domain.
  • the second network device deploys the first multi-access edge computing service instance corresponding to the multi-access edge computing application in the network domain according to the first request message.
  • the first network device arranges the first MEC Service of the network domain and the network resources corresponding to the first MEC Service according to the topology information of the MEC APP registered by the APPD and the MEC APP, wherein the first MEC Service includes but is not limited to. Multi-access Edge Computing Service Gateway (MSG), where MSG is used to provide cross-domain services for MEC APP.
  • MSG Multi-access Edge Computing Service Gateway
  • the first network resource includes a channel IP Pool and a channel ID corresponding to the MSG, wherein the IP Pool and the ID corresponding to the MSG are used to establish a cross-domain mutual access channel.
  • multi-access edge computing services that provide edge computing services for the MEC APP can be manually programmed in the APPD. Therefore, the first network device can decide the first MEC Service that needs to be deployed in the network domain according to the multi-access edge computing service manually arranged in the APP and the service instance information of the MEC APP registered by the MEC APP. For example, if the MSG that provides cross-domain services for the MEC APP is manually programmed in the APPD, the decision needs to deploy the MSG in the network domain.
  • the first network device can combine the service instance information of the MEC APP registered with the MEC APP to comprehensively decide which first MEC services need to be deployed in the network domain.
  • the MSG is not programmed in the APPD, but the first network device determines that some service instances in the MEC APP require cross-domain access, and the decision needs to deploy the MSG in the network domain.
  • the second network device deploys the first request message in the network domain (that is, the UPF of the network domain on the edge side) according to the topology information registered by the MEC APP, the first MEC Service, and the first network resources.
  • the MEC Service instance that is, the second network device instantiates the first MEC Service according to the first network resource, and obtains the first MEC Service instance for providing the first MEC Service for the MEC APP.
  • the subsequent deployment of the MEC Service instance in the network domain is to deploy the MEC Service instance in the UPF of the network domain on the edge side, and will not be repeated here.
  • the first network device sends second request information to the third network device according to the application description information and the topology information of the multi-access edge computing application, where the second request message is used to instruct the third network device to deploy and The second multi-access edge computing service instance corresponding to the multi-access edge computing application.
  • the third network device deploys the second multi-access edge computing service instance corresponding to the multi-access edge computing application in the computing domain according to the second request message.
  • the first network device decides the second multi-access edge computing service that needs to be deployed in the computing domain and is related to the second multi-access edge computing service.
  • the corresponding second network resource is served, and second request information is sent to the third network device, instructing the third network device to deploy the second multi-access edge computing service instance corresponding to the multi-access edge computing application in the computing domain.
  • the second multi-access edge computing service includes but is not limited to: MSG, APP LB Service, first DNS Service, second DNS Service, and Network Address Translation (NAT) service, where MSG uses In order to realize the cross-domain mutual access data channel between the network domain and the computing domain, the first DNS Service is used to support the domain name query during the data transmission process between the user equipment and the MEC APP, and the second DNS Service is used to support the MEC APP to perform Domain name query of MEC APP/MECService in this domain or cross-domain mutual access.
  • the second network resource includes a channel IP Pool and a channel ID corresponding to the MSG, a virtual (Virtual) APP IP corresponding to the APP LB Service, and a NAT IP Pool corresponding to the NAT service.
  • the third network device receives the second request message, it is deployed in the computing domain (that is, the MEC Service platform in the computing domain on the edge side) according to the topology information registered by the MEC APP, the second MEC Service, and the second network resources.
  • the second MEC Service instance that is, the second network device instantiates the second MEC Service according to the second network resource, and obtains the second MEC Service instance for providing the second MEC Service for the MEC APP.
  • the subsequent deployment of the MEC Service instance in the computing domain is to deploy the MEC Service instance in the MEC Service platform of the computing domain on the edge side, and will not be repeated here.
  • the MEC APP in addition to arranging the MEC Service of the MEC APP in the APPD, can also dynamically apply for the MEC Service.
  • the MEC APP sends a MEC Service application message to the MEP, where the MEC Service application message is used to request the allocation of the MEC Service, and the MEC Service application message includes the type and identifier of the MEC Service applied for by the MEC APP, etc.;
  • the device forwards the MEC Service application message, where each service instance in the MEC APP can dynamically apply for the MEC Service.
  • the third network device can also report the MEC Service application message in the process of sending the MEC APP registration topology information to the first network device, so that the first network device is the MEC
  • the MEC Service dynamically applied for by the APP allocates corresponding network resources, so that the third network device instantiates the MEC Service dynamically applied for by the MEC APP locally; finally, after the third network device completes the instantiation of the MEC Service dynamically applied for by the MEC APP, Send a MEC Service allocation response message to the MEP, and the MEP forwards the MEC Service allocation response message to the MEC APP, where the MEC Service allocation response message is used to indicate the MEC Service instantiation information dynamically applied by the third network device to the MEC APP.
  • the MEC APP can dynamically apply for the MEC Service
  • the subsequent MEC APP can dynamically expand and shrink according to actual needs
  • the third network device automatically completes the dynamic expansion and shrinkage of the MEC APP. It can dynamically update the business rules after the content, so as to realize the automatic management of the MEC APP.
  • some multi-access edge computing services required by the MEC APP may not be configured in the APPD, nor need the MEC APP to apply dynamically, but statically configured, for example, MSG is a default Multi-access edge computing services, whether configured in APPD or not, and whether MEC APP is dynamically applied, have decided to deploy MSG in the network domain and computing domain. Improves the flexibility of multi-access edge computing service deployment.
  • the first network device only needs to decide which MEC services to deploy in the network domain and allocate the corresponding network resources. Then, the third network device autonomously deploys in the computing domain according to the topology information of the MEC APP and the first network resources.
  • the second multi-access edge computing service instance used to provide the second MEC Service reduces the processing pressure of the first network device, issues computing tasks to each third network device, and improves the working stability of the first network device.
  • the first network device decides that the APP LB Service needs to be deployed in the computing domain, and the third network device independently decides how many APP LB Service instances need to be deployed.
  • the third network device can determine the number of service instances in the MEC APP that need APP LB Service according to the service instance information registered in the MEC APP, and the third network device can make decisions according to the number of service instances in the MEC APP that require LB Service The number of APP LB Service instances that need to be deployed; then, the network resources corresponding to each APP LB Service instance are determined from the first network resources allocated by the first network device, and the deployment of each APP LB Service instance is completed locally. .
  • FIG. 5 is a schematic flowchart of another service instance deployment method provided by an embodiment of the present application.
  • the content of this embodiment is the same as that of the embodiment shown in FIG. 4, and the description is not repeated here.
  • the method of this embodiment includes the following steps. This embodiment includes the following steps:
  • the first network device obtains description information of a multi-access edge computing application.
  • the third network device sends the topology information of the multi-access edge computing application to the first network device.
  • the first network device sends first request information to the second network device according to the application description information and the topology information of the multi-access edge computing application, where the first request message is used to instruct the second network device to deploy and The first multi-access edge computing service instance corresponding to the multi-access edge computing application.
  • the second network device deploys the first multi-access edge computing service instance corresponding to the multi-access edge computing application in the network domain according to the first request message.
  • the second network device sends a first response message to the first network device, where the first response message includes downlink cross-domain channel parameters.
  • the second network device after deploying the first multi-access edge computing service instance, sends a first response message to the first network device, where the first response message is used to instruct the second network device to complete the first response.
  • Deployment of a multi-access edge computing service instance, and the first response message may also carry downlink cross-domain channel parameters of the network domain, and the downlink cross-domain channel parameters are generated by the second network device in the process of deploying the MSG instance in the network domain of.
  • the downlink data channel parameter includes the channel ID and the channel IP address of the MSG instance of the network domain.
  • the second network device may send the downlink cross-domain channel parameters to the first network device through a dedicated message, and the present application does not limit the manner in which the second network device feeds back the downlink cross-domain channel parameters.
  • the first network device forwards the downlink cross-domain channel parameter to the third network device.
  • the second network device may carry the downlink cross-domain channel parameter in the second request message, then the The second request message is further used to instruct the third network device to establish a cross-domain mutual access channel between the network domain and the computing domain according to the downlink cross-domain channel parameter.
  • the first network device may also forward the downlink cross-domain channel parameter to the third network device through a dedicated message, and this application does not limit the forwarding of the downlink cross-domain channel parameter.
  • the first network device sends second request information to the third network device according to the application description information, the topology information of the multi-access edge computing application, and the second request message is used to instruct the third network device to deploy and The second multi-access edge computing service instance corresponding to the multi-access edge computing application.
  • the third network device deploys the second multi-access edge computing service instance corresponding to the multi-access edge computing application in the computing domain according to the second request message.
  • the second request message includes downlink cross-domain channel parameters. Therefore, the third network device can establish a cross-domain connection between the slave computing domain and the network domain according to the channel ID and channel IP address of the MSG instance of the network domain and the channel ID and channel IP address of the MSG instance of the local end (computing domain). mutual access channel. For example, when accessing a network domain from a computing domain across domains, use the channel ID and channel IP address of the MSG instance of the computing domain as the source channel ID and source channel IP, and use the channel ID and channel IP of the network domain MSG instance as the destination. The channel ID and destination channel IP are used to establish a cross-domain mutual access channel between the computing domain and the network domain.
  • the second network device generates a first service rule corresponding to the first multi-access edge computing service instance, and inserts the first service rule into the first multi-access edge computing service instance.
  • the business rules involved in this application can be understood as the correspondence between the multi-access edge computing service instance and the MEC APP.
  • the business rules involved in this application can be understood as the correspondence between the multi-access edge computing service instance and the MEC APP.
  • two APP LB Service instances are deployed, and these two load balancing instances provide APP LB Service for ten service instances in the MEC APP, then it is necessary to establish each APP LB Service instance and MEC
  • This correspondence is the business rule corresponding to the APP LB Service instance.
  • the first business rule and the second business rule involved later are similar to the business rule unlocking here, and will not be described again.
  • the first request message is further used to instruct the second network device to generate a first service rule corresponding to the first multi-access edge computing service instance, and send the first multi-access edge computing service instance to the first multi-access edge computing service instance.
  • the service instance inserts the first business rule.
  • the first network device may also instruct the second network device to generate the first business rule corresponding to the first multi-access edge computing service instance through other request messages. For example, an additional request message may be sent to instruct the second network device to generate the first business rule. A first business rule corresponding to the first multi-access edge computing service instance.
  • the second network device will autonomously generate the first business rule corresponding to the first multi-access edge computing service instance, and insert the first business rule into the first multi-access edge computing service instance.
  • the first rule includes, but is not limited to, the uplink classification rule inserted into the local (network domain) offload service and the MSG rule inserted into the MSG.
  • the second network device only inserts the first business rule into the first multi-access edge computing service instance, but does not enable the first business rule, that is, the first multi-access edge computing service instance At the same time, the first multi-access edge computing service cannot be provided for the user equipment.
  • the third network device generates a second business rule corresponding to the second multi-access edge computing service instance, and inserts the second business rule into the second multi-access edge computing service instance.
  • the second request message is further used to instruct the third network device to generate a second service rule corresponding to the second multi-access edge computing service instance, and report it to the third network device.
  • the second multi-access edge computing service instance inserts the second business rule and enables the second business rule.
  • the first service rule is not directly enabled, and the second service rule is directly enabled after the second service rule is generated.
  • the enabling method of the domain's business rules In practical applications, there may also be other enabling methods.
  • the first business rule is directly enabled and the second business rule is not directly enabled; or, neither the first business rule nor the second business rule is directly enabled. and many more. This application does not limit the enabling manner of the business rule.
  • not directly enabling the first business rule is to leave a certain buffer time for the enabling and taking effect of the service instance in the MEC APP. If the first business rule and the second business rule are directly enabled, the MEC APP The service instance has not yet taken effect, so when the user equipment performs local offloading on the edge side, the MEC APP will not be able to provide edge content. After many attempts, the user equipment may go to the center side to obtain data content, which increases the number of users. communication delay. Instead of directly enabling the first service rule, if the service instance in the MEC APP has not yet taken effect, the UPF on the edge side will directly forward user data packets to the UPF on the central side, which will not affect the user's communication needs.
  • the first business rule is disabled.
  • the third network device forwards the indication information to the first network device.
  • the first network device may send a fourth request message to the second network device.
  • the third network device sends a second response message to the first network device, where the second response message includes uplink cross-domain channel parameters.
  • the second response message is used to instruct the third network device to complete the instantiation of the second multi-access edge computing service, and insert the second business rule into the second multi-access edge computing service instance.
  • the first network device sends a third request message to the second network device, where the third request message includes the uplink cross-domain channel parameters, and the third request message is used to instruct the second network device according to the uplink cross-domain channel parameters and the downlink cross-domain channel parameters. parameter to establish a cross-domain mutual access channel between the network domain and the computing domain.
  • the second network device establishes the cross-domain communication between the network domain and the computing domain according to the downlink cross-domain channel parameters of the MSG of the local end (network domain) and the uplink cross-domain channel parameters of the MSG of the opposite end (computing domain). access channel.
  • the first network device sends a fourth request message to the second network device, where the fourth request message is used to instruct the second network device to notify the user plane function entity of the network domain to enable the first service rule, and the user plane function entity is the second network device.
  • the network device is determined according to the topology information of the multi-access edge computing application.
  • the first network device independently disables the first service rule, which can ensure the communication needs of the user under the condition that the service instance in the MEC APP cannot take effect immediately.
  • an effective instruction can be sent to the first network device through the third network device, and the instruction can trigger the first network device to disable the first service rule, so that even if the MEC The service instance in the APP does not take effect immediately, and can also be automatically enabled to implement the business rules of the network domain and the business rules of the computing domain.
  • the second network device sends a third response message to the first network device, where the third response message is used to instruct the user plane function entity to complete the enabling of the first service rule.
  • the first network device sends a fifth request message to the policy control function on the central side, where the fifth request message includes the instance identifier of the multi-access edge computing application and the data network access identifier.
  • the policy control function on the center side forwards the instance identifier and data network access identifier of the multi-access edge computing application to the session management function on the center side, and inserts the multi-access edge computing application's ID into the session management function on the center side. Instance ID and location ID.
  • the first network device inserts the instance identifier (that is, the APP ID) and the data network access identifier (DNAI) of the MEC APP into the PCF, wherein the instance identifier (APP ID) of the MEC APP indicates the user subscription group of the MEC APP, Then in the subsequent process of establishing a context session, if it is determined that the user equipment belongs to the user subscription group, the instance identifier (APP ID) and data network access identifier (DNAI) of the MEC APP are inserted into the session management function SMF.
  • the instance identifier that is, the APP ID
  • DNAI data network access identifier
  • the session management function on the center side selects the user plane functional entity on the edge side according to the location identifier of the multi-access edge computing application, and inserts the instance identifier and data of the multi-access edge computing application into the user plane functional entity on the edge side Network access identifier.
  • the SMF selects a matching edge UPF to establish a session context for the user equipment according to the data network access identifier, that is, the DNAI, and determines if the user equipment meets the local offloading conditions (for example, the user equipment is currently at the DNAI location) , then instructs UPF to insert the APP ID of the MEC APP.
  • the data network access identifier that is, the DNAI
  • the subsequent edge UPF receives the upstream DNS query message of the user equipment that meets the local offloading conditions, performs L7ULCL rule matching based on the MEC APP domain name, and determines the local offloading, then uses the cross-domain channel service (MSG) of the computing domain and the network domain. ), forwards the upstream DNS query message to the MEC service instance in the computing domain (the DNS service instance in the computing domain), the DNS service processes the DNS query message, and queries the previously created MEC APP domain name according to the MEC APP domain name carried in the message. MEC APP domain name record, return DNS query response message (carrying MECAPP Virtual IP or MEC APP Real IP).
  • MSG cross-domain channel service
  • Subsequent edge UPFs receive user data packets from user equipment that meet the local offload conditions, and perform L3/L4ULCL rule matching based on the MECAPP Virtual IP/Port or MEC APP Real IP/Port to determine local offload, and then pass the computing domain and network Domain cross-domain channel service (MSG), which forwards uplink user data packets to the MEC service instance in the computing domain (APP LB service instance in the computing domain, MEC APP Virtual IP/Port) or service instance in the MEC APP ( MEC APP Real IP/Port).
  • MSG network Domain cross-domain channel service
  • the APP LB service instance distributes the user datagram to the corresponding service instance in the MEC APP according to the second business rule, and the corresponding service instance in the MEC APP determines the corresponding service instance according to the user data message Downlink edge content, and send the downlink edge content to the user equipment through the computing domain of the computing domain and the cross-domain channel service (MSG) of the network domain.
  • MSG cross-domain channel service
  • the MEC APP can also be automatically decided to deploy. As shown in FIG. 6 , before receiving the topology information of the multi-access edge computing application from the third network device, the following steps can also be used to trigger the MEC APP. Automated deployment:
  • the first network device subscribes the access statistical data of the APP to a network data analysis function (Network Data Analytics Function, NWDAF).
  • NWDAF Network Data Analytics Function
  • NWDAF publishes the access statistics of the APP to the first network device.
  • the first network device sends first prompt information to the third network device according to the access statistics of the application and the service policy, where the first prompt information is used to instruct the third network device to notify the network function virtualization infrastructure deployment of the computing domain MEC APP for providing edge content to APP.
  • the service policy is manually programmed and configured to the first network device through a northbound interface of the first network device.
  • the business policy may be a policy based on the number of visits. For example, when the number of visits to the APP is greater than the first threshold, it is necessary to deploy the MEC APP that provides edge content for the APP to achieve local traffic distribution; or , the service policy may be a policy based on the access duration. For example, when the total access duration to the APP is greater than the second threshold, it is necessary to deploy the MEC APP that provides edge content for the APP.
  • the business strategy can be arranged according to actual requirements, and the application does not limit the form of the business strategy.
  • NFVI after NFVI receives the first prompt information, it will allocate corresponding network resources to the MEC APP, return the allocated network resources to MEPM, and notify MEPM to complete the subsequent deployment of the MEC APP.
  • the deployment method shown in 1 is similar and will not be described again.
  • a business strategy can be pre-injected, and the deployment of the MEC APP can be dynamically triggered according to the business strategy and the obtained access statistics of the APP, so as to further improve the intelligence and automation of the deployment of the MEC APP.
  • the MEC APP can also be automatically decided to deploy. As shown in FIG. 7 , before receiving the topology information of the multi-access edge computing application from the third network device, the MEC APP can also be triggered by the following steps Automated deployment of:
  • the application provider sends a sixth request message to the first network device, where the sixth request message is used to request the deployment of the MEC APP that provides edge content for the APP.
  • the application provider may be the controller of the APP, that is, the APP Controller.
  • the APP Controller can obtain the access statistical data of the APP, generate the sixth request message according to the access statistical data and the service policy, and then send the sixth request message to the first network device through the development interface of the first network device.
  • the first network device instructs the third network device to notify the network function virtualization infrastructure of the computing domain to deploy the multi-access edge computing application for providing edge content for the application.
  • the first network device may send first prompt information to the third network device, using the first prompt information to instruct the third network device to notify the network function virtualization infrastructure deployment of the computing domain for providing edge content for applications.
  • the multi-access edge computing application may send first prompt information to the third network device, using the first prompt information to instruct the third network device to notify the network function virtualization infrastructure deployment of the computing domain for providing edge content for applications.
  • the method of deploying the MEC APP is similar to the above-mentioned deployment method, and will not be described again.
  • the first network device sends a sixth response message to the application provider, where the sixth response message is used to indicate completion of the deployment of the MEC APP and service enablement.
  • the online and deployment of the MEC APP can be automatically triggered by the information provider, which further improves the intelligence and automation of the deployment of the MEC APP.
  • the application scenario of the establishment of the cross-domain mutual access channel of the present application may be to establish a cross-domain mutual access channel between two edge-side computing domains, or to establish an edge-side computing domain and a central-side computing domain.
  • the cross-domain mutual access channel between computing domains may also be a cross-domain mutual access channel between two central computing domains. Therefore, the first computational domain and the second computational domain involved later can be either the computational domain on the edge side or the computational domain on the central side.
  • the first computational domain is mainly used as the computational domain on the edge side
  • the second computational domain is The computational domain in which the computational domain is the center side is taken as an example for illustration.
  • the fourth network device can be understood as the above-mentioned first network device
  • the fifth network device can be understood as the above-mentioned third network device
  • the sixth network device is a network device managing the second computing domain.
  • the establishment of the cross-domain access channel of the present application additionally deploys a fourth network device on the central side, and additionally deploys a fifth network device in the computing domain on the edge side.
  • the computing domain additionally deploys a sixth network device.
  • the fourth network device, the fifth network device, and the sixth network device work cooperatively to automatically establish a cross-domain mutual access channel between the first computing domain and the second computing domain.
  • the fifth network device configures the first cross-domain channel parameter and the first multi-access edge computing service instance of the first multi-access edge computing service instance in the first computing domain.
  • the first routing parameter between the service instance and the first multi-access edge computing application configure the first cross-domain channel parameter to the first multi-access edge computing service instance, and pass the first routing parameter through the first computing domain
  • the first multi-access edge computing platform is configured to the first multi-access edge computing application
  • the fifth network device sends the first cross-domain channel parameter and the instance information of the second computing domain to the fourth network device;
  • the fourth network device forwards the first cross-domain channel parameter to the sixth network device according to the instance information of the second computing domain, and instructs the sixth network device to establish a cross-domain mutual access channel. Therefore, the sixth network device configures the second cross-domain channel parameter of the second multi-access edge computing service instance in the second computing domain and the relationship between the second multi-access edge computing service instance and the second multi-access edge computing application program. the second routing parameter between the two domains, configure the first cross-domain channel parameter and the second cross-domain channel parameter to the second multi-access edge computing service instance, and pass the second routing parameter through the second multi-access edge computing service instance of the second computing domain.
  • the edge computing platform is configured to the second multi-access edge computing application; finally, the second cross-domain channel parameters are sent to the fourth network device;
  • the fourth network device forwards the second cross-domain channel parameter to the fifth network device, and the fifth network device configures the second cross-domain channel parameter to the first multi-access edge computing service instance;
  • the first multi-access edge computing application and the first multi-access edge computing service instance can establish a communication link based on the first routing parameter, and the first multi-access edge computing service instance and the second multi-access edge computing service instance can establish a communication link based on the first routing parameter.
  • a cross-domain mutual access channel can be established, and the second multi-access edge computing service instance and the second multi-access edge computing application can be based on The second routing parameter establishes the communication link.
  • a cross-domain mutual access communication link is automatically established: namely, the first multi-access edge computing application, the first multi-access edge computing service instance, the second multi-access edge computing service instance, and the second multi-access edge computing service instance.
  • the first multi-access edge computing application and the second multi-access edge computing application can perform cross-domain mutual access through this communication link.
  • the fourth network device, the fifth network device, and the sixth network device work cooperatively to automatically open up the cross-domain mutual access of the MEC APP between the two computing domains, reducing the MEC APP operation and maintenance costs.
  • FIG. 9 is a schematic flowchart of a method for establishing a cross-domain mutual access channel according to an embodiment of the present application, and the method includes:
  • the first multi-access edge computing application of the first computing domain sends a cross-domain access request to the first multi-access edge computing platform of the first computing domain, where the cross-domain mutual access request is used to indicate the first computing domain
  • the first multi-access edge computing application program requests cross-domain access to the second computing domain, and the cross-domain mutual access request includes instance information of the second computing domain.
  • the instance information of the second computing domain includes, but is not limited to, the domain name, identifier, and location of the second computing domain.
  • the first multi-access edge computing platform of the first computing domain publishes the cross-domain access request to the fifth network device.
  • the fifth network device pre-subscribes the cross-domain access request of the first multi-access edge computing application to the first multi-access edge computing platform, for example, according to the domain name of the first multi-access edge computing application or Sign to complete the subscription; then, after receiving the cross-domain access request from the first multi-access edge computing application, the first multi-access edge computing platform, according to the previous subscription situation, sends the first multi-access edge computing application
  • the cross-domain access request is issued to the fifth network device.
  • the fifth network device configures the first cross-domain channel parameters of the first multi-access edge computing service instance used for cross-domain mutual access in the first computing domain, and configures the first cross-domain channel parameters to the first multi-access edge computing service instance. into the edge computing service instance.
  • the first cross-domain channel parameter includes, but is not limited to, a channel ID, a channel IP, and a channel Port used by the first multi-access edge computing service instance for cross-domain access.
  • the fifth network device first determines whether the first multi-access edge computing service instance for cross-domain mutual access is deployed in the local (first computing domain), and if not deployed, then Deploy the first multi-access edge computing service instance first; if already deployed, you do not need to deploy the first multi-access edge computing service instance.
  • the first multi-access edge computing service instance has been deployed, you can Deploy the first multi-access edge computing service instance.
  • the current first multi-access edge computing service instance has provided edge computing services for many MEC APPs, and a first multi-access edge computing service instance needs to be redeployed.
  • the fifth network device autonomously decides on the deployment of the first multi-access edge computing service instance, configures the first cross-domain channel parameters for the first multi-access edge computing service instance, and assigns the first cross-domain channel to the first multi-access edge computing service instance.
  • the parameters are configured for the first multi-access edge computing service instance.
  • the fifth network device sends the instance information of the second computing domain and the first cross-domain channel parameter of the first multi-access edge computing service instance used for cross-domain mutual access in the first computing domain to the fourth network device.
  • the fourth network device sends, according to the instance information of the second computing domain, the first cross-domain channel parameter of the first multi-access edge computing service instance used for cross-domain mutual access in the first computing domain to the sixth network device.
  • the fourth network device determines a sixth network device corresponding to the second computing domain according to the instance information of the second computing domain, and then sends the first cross-domain channel parameter to the sixth network device, and The sixth network device is instructed to establish a cross-domain mutual access channel according to the first cross-domain channel parameter.
  • the sixth network device configures the second cross-domain channel parameter of the second multi-access edge computing service instance used for cross-domain mutual access and the second routing parameter of the second multi-access edge computing service instance in the second computing domain , and configure the first cross-domain channel parameter, the second cross-domain channel parameter, and the second routing parameter to the second multi-access edge computing service instance.
  • the second cross-domain channel parameter includes, but is not limited to, the channel ID, IP, and Port used by the second multi-access edge computing service instance for cross-domain access.
  • the second routing parameter includes the downlink IP address of the second multi-access edge computing service instance.
  • the sixth network device also decides the deployment of the second multi-access edge computing service instance as needed, configures corresponding second cross-domain channel parameters for the second multi-access edge computing service instance, and assigns the first cross-domain
  • the channel parameters and the second cross-domain channel parameters are configured to the second multi-access edge computing service instance.
  • the second multi-access edge computing service instance can establish a cross-domain access channel.
  • the second multi-access edge computing service instance uses the second cross-domain channel parameter as the source channel address , using the first cross-domain channel parameter as the target channel address to complete cross-domain access.
  • a subscription relationship is also completed between the sixth network device and the second multi-access edge computing platform of the second computing domain, which is used to discover whether there is a multi-access edge computing service for cross-domain channels in the second computing domain Online, so as to facilitate the decision whether to deploy the multi-access edge computing service.
  • the second multi-access edge computing application will register the uplink IP address of the second multi-access edge computing application with the second multi-access edge computing application.
  • Second MEP the second MEP will also publish the uplink IP address of the second multi-access edge computing application to the sixth network device according to the previous subscription situation, and the sixth network device can use the second multi-access edge computing application
  • the upstream IP address of the program is configured to the second multi-access edge computing application.
  • the second multi-access edge computing service instance can establish the first A communication link between the second multi-access edge computing service instance and the second multi-access edge computing application.
  • take the downlink IP address as the source IP address and the uplink IP address as the destination IP address to complete the downlink transmission from the second multi-access edge computing service instance to the second multi-access edge computing application .
  • the sixth network device sends the second routing parameter to the second multi-access edge computing platform of the second computing domain.
  • the second multi-access edge computing platform in the second computing domain forwards the second routing parameter to the second multi-access edge computing application in the second computing domain.
  • the second multi-access edge computing application program establishes the second multi-access edge computing service instance and the second multi-access edge computing service instance according to the local routing parameters (that is, the uplink routing parameters) and the second routing parameters (downlink routing parameters). Communication link between edge computing applications.
  • the sixth network device sends the second cross-domain channel parameter of the second multi-access edge computing service instance to the fourth network device.
  • the second response message is used to indicate that the establishment of the cross-domain access channel on the side of the sixth network device is completed.
  • the fourth network device forwards the second cross-domain channel parameter of the second multi-access edge computing service instance to the fifth network device.
  • the fifth network device configures the second cross-domain channel parameter of the second multi-access edge computing service instance to the first multi-access edge computing service instance.
  • the first multi-access edge computing service instance may establish a relationship between the first multi-access edge computing service instance and the second multi-access edge computing service instance according to the second cross-domain channel parameters and the first cross-domain channel parameters. cross-domain access channel between.
  • the fifth network device configures the first routing parameter of the first multi-access edge computing service instance, and sends a second response message to the first multi-access edge computing platform in the first computing domain, where the second response message includes the first route parameters.
  • the second response message is used to indicate that the establishment of the cross-domain access channel between the first computing domain and the second computing domain is completed.
  • the first multi-access edge computing platform of the first computing domain forwards the first routing parameter to the first multi-access edge computing application program of the first computing domain.
  • the first multi-access edge computing application program is based on the first routing parameters (downlink routing parameters) of the first multi-access edge computing service instance and the routing parameters of the local end (the first multi-access edge computing application program) ( Uplink routing parameters) to establish a communication link between the first multi-access edge computing application and the first multi-access edge computing service instance.
  • the first multi-access edge computing application can pass the communication between the first multi-access edge computing application and the first multi-access edge computing service instance.
  • the communication link sends the data packet to the first multi-access edge computing service instance, and the first multi-access edge computing service instance sends the data packet to the second multi-access edge computing service instance through the cross-domain mutual access channel,
  • the second multi-access edge computing service instance sends the multi-access edge computing service instance to the second multi-access edge computing application;
  • the second multi-access edge computing application provides edge content through the corresponding service instance, and The edge content is returned to the first multi-access edge computing application, thereby realizing cross-domain access from the first multi-access edge computing application to the second multi-access edge computing application.
  • the first network device decides the first multi-access edge computing service that needs to be deployed in the network domain and the corresponding first network resources.
  • the first network device may also allocate the first multi-access edge computing service instance required by the first multi-access edge computing service, as well as network resources and business rules corresponding to each first multi-access edge computing service, Then, deliver the first multi-access edge computing service instance required by the allocated first multi-access edge computing service, and the network resources and business rules corresponding to each first multi-access edge computing service to the first multi-access edge computing service.
  • the second network device only needs to simply perform the deployment process of the multi-access edge computing service instance, without resource allocation, and only acts as an information executor without decision-making function; similarly, for the second multi-access edge service instance
  • the first network device may also be deployed according to the deployment method of the first multi-access edge service instance, which will not be described again. That is to say, in the deployment process of the multi-access edge service instance, the first user equipment may act as a decision maker for a part of the process, or may act as a decision maker for the entire process, which is not limited in this application.
  • the first cross-domain channel parameters and the first routing parameters of the first multi-access edge computing service instance in the first computing domain The generation of the command can be executed by the fifth network device or by the fourth network device; in the case of being executed by the fourth network device, the fifth device only needs to act as the executor of the command, and the fourth network device generated A cross-domain channel parameter and the first routing parameter are configured for the first cross-domain channel parameter and the first routing parameter; similarly, for the second cross-domain channel parameter of the second multi-access edge computing service instance in the second computing domain , and the generation of the second routing parameter may be performed by the fifth network device or may be performed by the fourth network device, which is similar to the above and will not be described again.
  • the first network device, the second network device, the third network device, and the interaction between the first network device, the second network device, and the third network device respectively.
  • the methods provided by the embodiments of the present application are introduced from the perspective.
  • the first network device, the second network device, and the third network device may include hardware structures and/or software modules, and the hardware structures, software modules, or hardware structures plus
  • the above functions can be realized in the form of software modules. Whether one of the above functions is performed in the form of a hardware structure, a software module, or a hardware structure plus a software module depends on the specific application and design constraints of the technical solution.
  • FIG. 10 and FIG. 11 provide schematic structural diagrams of a communication device according to an embodiment of the present application.
  • These communication apparatuses can implement the functions of the first network device, the second network device, or the third network device in the above method embodiments, and thus can also achieve the beneficial effects of the above method embodiments.
  • the communication device may be the first network device shown in any of the embodiments corresponding to FIG. 4 to FIG. 7 , or may be a second network device, or a third network device, or It can be a module (such as a chip) applied to the first network device or the second network device or the third network device.
  • the communication device 1000 includes a transceiver module 1001 and a processing module 1002 .
  • the communication apparatus 1000 may be configured to implement the functions of the first network device or the second network device or the third network device in any of the embodiments corresponding to FIG. 4 to FIG. 7 .
  • the transceiver module 1001 is used to obtain the description information of the multi-access edge computing application
  • a processing module 1002 configured to control the transceiver module 1001 to send first request information to the second network device according to the multi-access edge computing application description information and the topology information of the multi-access edge computing application, and Sending second request information to the third network device, where the first request information is used to instruct the second network device to deploy the first multi-access edge computing application corresponding to the multi-access edge computing application in the network domain into the edge computing service instance, and the second request information is used to instruct the third network device to deploy the second multi-access edge computing service instance corresponding to the multi-access edge computing application in the computing domain.
  • a transceiver module 1001 configured to receive a first request message from the first network device, where the first request message is the first network device according to the multi-access edge computing application description information and the multi-access edge computing application
  • the topology information of the multi-access edge computing application is generated from the topology information, and the topology information of the multi-access edge computing application is sent by the second network device to the first network device;
  • the processing module 1002 is configured to deploy a first multi-access edge computing service instance corresponding to the multi-access edge computing application in the network domain according to the first request message.
  • a transceiver module 1001 configured to send topology information of a multi-access edge computing application to the first network device and to receive a second request message from the first network device, where the second request message is the first request message.
  • a network device is generated according to the description information of the multi-access edge computing application and the topology information of the multi-access edge computing application;
  • the processing module 1002 is configured to deploy a second multi-access edge computing service instance corresponding to the multi-access edge computing application in the network domain according to the second request message.
  • transceiver module 1001 For a more detailed description of the foregoing transceiver module 1001 and the processing module 1002, reference may be made to the relevant descriptions in the foregoing method embodiments, which are not described herein again.
  • the communication device 1100 includes a processor 1101 and an interface circuit 1102 .
  • the processor 1101 and the interface circuit 1102 are coupled to each other.
  • the interface circuit 1102 can be a transceiver or an input-output interface.
  • the communication device 1100 may further include a memory 1103 for storing instructions executed by the processor 1101 or input data required by the processor 1101 to run the instructions or data generated after the processor 1101 runs the instructions.
  • the processor 1101 is used to execute the functions of the foregoing processing module 1002
  • the interface circuit 1102 is used to execute the functions of the foregoing transceiver module 1001 .
  • the chip in the first network device implements the function of the first network device in the above method embodiment.
  • the chip in the first network device receives information from other modules (such as radio frequency modules or antennas) in the first network device, and the information is sent by the second network device or the third network device to the first network device; or, the The chip in the first network device sends information to other modules (such as a radio frequency module or an antenna) in the first network device, and the information is sent by the first network device to the second network device or the third network device.
  • the chip in the second network device implements the functions of the second network device in the above method embodiments.
  • the chip in the second network device receives information from other modules (such as a radio frequency module or an antenna) in the second network device, and the information is sent by the first network device to the second network device; or, in the second network device
  • the chip of the second network device sends information to other modules (such as a radio frequency module or an antenna) in the second network device, and the information is sent by the second network device to the first network device.
  • the chip in the third network device implements the functions of the third network device in the above method embodiments.
  • the chip in the third network device receives information from other modules (such as radio frequency modules or antennas) in the third network device, and the information is sent by the first network device to the third network device; or, in the third network device
  • the chip of the third network device sends information to other modules (such as a radio frequency module or an antenna) in the third network device, and the information is sent by the third network device to the first network device.
  • Embodiments of the present application further provide a multi-access edge computing system, including the above-mentioned communication device implementing the function of the first network device, the communication device implementing the second network device, and the above-mentioned communication device implementing the function of the third network device.
  • the fourth network device, the fifth network device, the sixth network device, the fourth network device, the fifth network device, and the sixth network device respectively The methods provided by the embodiments of the present application are introduced from the perspective of interaction between them.
  • the fourth network device, the fifth network device, and the sixth network device may include hardware structures and/or software modules, and the hardware structures, software modules, or hardware structures plus The above functions can be realized in the form of software modules. Whether a certain function of the above functions is performed in the form of a hardware structure, a software module, or a hardware structure plus a software module depends on the specific application and design constraints of the technical solution.
  • FIG. 12 and FIG. 13 provide schematic structural diagrams of another communication device according to an embodiment of the present application.
  • These communication apparatuses can implement the functions of the fourth network device, the fifth network device, and the sixth network device in the above method embodiments, and thus can also achieve the beneficial effects of the above method embodiments.
  • the communication device may be the fourth network device shown in any of the embodiments corresponding to FIG. 8 and FIG. 9 , may also be a fifth network device, or may be a sixth network device, or It can be a module (such as a chip) applied to the fourth network device, the fifth network device or the sixth network device.
  • the communication device 1200 includes a transceiver module 1201 and a processing module 1202 .
  • the communication apparatus 1200 may be configured to implement the functions of the fourth network device, the fifth network device, or the sixth network device in any of the foregoing embodiments corresponding to FIG. 8 or FIG. 9 .
  • the processing module 1202 is used to control the transceiver module 1201 to receive the instance information of the second computing domain and the first multi-access edge computing for cross-domain mutual access in the first computing domain from the fifth network device the first cross-domain channel parameter of the service instance; sending the first cross-domain channel parameter to the sixth network device according to the instance information of the second computing domain; receiving the second cross-domain channel parameter from the sixth network device The second cross-domain channel parameter of the second multi-access edge computing service instance used for cross-domain mutual access in the computing domain; sending the first cross-domain mutual access used in the second computing domain to the fifth network device Second cross-domain channel parameters of the multi-access edge computing service instance;
  • the first cross-domain channel parameter and the second cross-domain channel parameter are used to characterize the cross-domain connection between the first multi-access edge computing service instance and the second multi-access edge computing service instance mutual access channel.
  • the processing module 1202 is configured to control the transceiver module 1201 to send the instance information of the second computing domain and the first multi-access edge computing service for cross-domain mutual access in the first computing domain to the fourth network device the first cross-domain channel parameter of the instance; receiving the second cross-domain channel parameter of the second multi-access edge computing service instance used for cross-domain access in the second computing domain from the fourth network device;
  • the first cross-domain channel parameter and the second cross-domain channel parameter are used to characterize the cross-domain connection between the first multi-access edge computing service instance and the second multi-access edge computing service instance mutual access channel.
  • the processing module 1202 is configured to control the transceiver module 1201 to receive, from the fourth network device, the first cross-domain channel parameter of the first multi-access edge computing service instance used for cross-domain mutual access in the first computing domain;
  • the fourth network device sends the second cross-domain channel parameter of the second multi-access edge computing service instance used for cross-domain mutual access in the second computing domain; wherein the first cross-domain channel parameter and all The second cross-domain channel parameter is used to represent the cross-domain mutual access channel between the first multi-access edge computing service instance and the second multi-access edge computing service instance.
  • transceiver module 1201 For a more detailed description of the foregoing transceiver module 1201 and the processing module 1202, reference may be made to the relevant descriptions in the foregoing method embodiments, which are not described herein again.
  • the communication device 1300 includes a processor 1301 and an interface circuit 1302 .
  • the processor 1301 and the interface circuit 1302 are coupled to each other.
  • the interface circuit 1102 can be a transceiver or an input-output interface.
  • the communication device 1300 may further include a memory 1303 for storing instructions executed by the processor 1301 or input data required by the processor 1301 to execute the instructions or data generated after the processor 1301 executes the instructions.
  • the processor 1101 is used to execute the functions of the foregoing processing module 1202
  • the interface circuit 1302 is used to execute the functions of the foregoing transceiver module 1201 .
  • the chip in the fourth network device implements the function of the fourth network device in the above method embodiment.
  • the chip in the fourth network device receives information from other modules (such as a radio frequency module or an antenna) in the fourth network device, and the information is sent by the fifth network device or the sixth network device to the fourth network device; or, the The chip in the fourth network device sends information to other modules (such as a radio frequency module or an antenna) in the fourth network device, and the information is sent by the fourth network device to the fifth network device or the sixth network.
  • the chip in the fifth network device implements the functions of the fifth network device in the above method embodiments.
  • the chip in the fifth network device receives information from other modules (such as radio frequency modules or antennas) in the fifth network device, and the information is sent by the fourth network device to the fifth network device; or, in the fifth network device
  • the chip of the fifth network device sends information to other modules (such as a radio frequency module or an antenna) in the fifth network device, and the information is sent by the fifth network device to the fourth network device.
  • the chip in the third network device implements the functions of the sixth network device in the above method embodiments.
  • the chip in the sixth network device receives information from other modules (such as radio frequency modules or antennas) in the sixth network device, and the information is sent by the fourth network device to the sixth network device; or, in the sixth network device
  • the chip of the sixth network device sends information to other modules (such as a radio frequency module or an antenna) in the sixth network device, and the information is sent by the sixth network device to the fourth network device.
  • Embodiments of the present application further provide a system for establishing a cross-domain mutual access channel, including the above-mentioned communication device for implementing the function of the fourth network device, the communication device for implementing the fifth network device, and the above-mentioned communication device for implementing the function of the sixth network device.
  • processor in the embodiments of the present application may be a central processing unit (central processing unit, CPU), and may also be other general-purpose processors, digital signal processors (digital signal processors, DSP), application-specific integrated circuits (application specific integrated circuit, ASIC), field programmable gate array (field programmable gate array, FPGA) or other programmable logic devices, transistor logic devices, hardware components or any combination thereof.
  • CPU central processing unit
  • DSP digital signal processors
  • ASIC application specific integrated circuit
  • FPGA field programmable gate array
  • a general-purpose processor may be a microprocessor or any conventional processor.
  • the method steps in the embodiments of the present application may be implemented in a hardware manner, or may be implemented in a manner in which a processor executes software instructions.
  • Software instructions can be composed of corresponding software modules, and software modules can be stored in random access memory (RAM), flash memory, read-only memory (ROM), programmable read-only memory (programmable ROM) , PROM), erasable programmable read-only memory (erasable PROM, EPROM), electrically erasable programmable read-only memory (electrically EPROM, EEPROM), registers, hard disks, removable hard disks, CD-ROMs or known in the art in any other form of storage medium.
  • An exemplary storage medium is coupled to the processor, such that the processor can read information from, and write information to, the storage medium.
  • the storage medium can also be an integral part of the processor.
  • the processor and storage medium may reside in an ASIC.
  • the ASIC may be located in the first network device, the second network device, the third network device, the fourth network device, the fifth network device or the sixth network device.
  • the processor and the storage medium may also exist in the first network device, the second network device, the third network device, the fourth network device, the fifth network device or the sixth network device as discrete components.
  • a computer program product includes one or more computer programs or instructions.
  • the computer may be a general purpose computer, a special purpose computer, a computer network, or other programmable device.
  • the computer program or instructions may be stored in or transmitted over a computer-readable storage medium.
  • a 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 of the available media.
  • Useful media may be magnetic media such as floppy disks, hard disks, magnetic tapes; optical media such as DVDs; and semiconductor media such as solid state disks (SSDs).
  • “at least one” means one or more, and “plurality” means two or more.
  • “And/or”, which describes the association relationship of the associated objects, indicates that there can be three kinds of relationships, for example, A and/or B, which can indicate: the existence of A alone, the existence of A and B at the same time, and the existence of B alone, where A, B can be singular or plural.
  • the character “/” generally indicates that the related objects are a kind of "or” relationship; in the formula of this application, the character "/” indicates that the related objects are a kind of "division" Relationship.

Abstract

一种服务实例部署方法、跨域互访通道建立方法及相关装置。方法包括：获取多接入边缘计算应用程序描述信息；从第三网络设备接收多接入边缘计算应用程序的拓扑信息；根据多接入边缘计算应用程序描述信息和多接入边缘计算应用程序的拓扑信息，向第二网络设备发送第一请求信息，和向第三网络设备发送第二请求信息，第一请求信息用于指示第二网络设备在网络域部署与多接入边缘计算应用程序对应的第一多接入边缘计算服务实例，第二请求信息用于指示第三网络设备在计算域部署与多接入边缘计算应用程序对应的第二多接入边缘计算服务实例。

Description

服务实例部署方法、跨域互访通道建立方法及相关装置
本申请要求于2020年11月17日提交中国专利局、申请号为202011289415.7、申请名称为“服务实例部署方法、跨域互访通道建立方法及相关装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本发明涉及通信技术领域，具体涉及一种服务实例部署方法、跨域互访通道建立方法及相关装置。
背景技术
在5G网络(5th generation mobile networks)中，为了满足信息提供方(Over The Top，OTT)对低时延/高吞吐业务的诉求，将OTT提供信息的应用程序下沉到网络边缘位置部署，衍生出了多接入边缘计算(Multi-access Edge Computing，MEC)技术。并且将在网络边缘位置部署的用于为用户提供边缘内容给接入设备的应用程序称为多接入边缘计算应用程序(Multi-access Edge Computing Application，MEC APP)。
目前，欧洲电信标准化协会(European Telecommunications Standards Institute，ETSI)标准为MEC技术定义了标准架构，在MEC的标准架构程中，将网络域和计算域分离部署，并且由人工将部署MEC APP上线、人工对MEC APP进行业务使能以及人工编排MEC APP的跨域互访通道，导致在MEC APP的整个生命周期中，MEC APP的运维成本高。
发明内容
本申请提供了一种服务实例部署方法、跨域互访通道建立方法及相关装置，降低MEC APP上线及业务使能的运维成本。
第一方面，本申请实施例提供一种服务实例部署方法，该方法的执行主体可以是第一网络设备，也可以是应用于第一网络设备中的芯片。下面以执行主体是第一网络设备为例进行描述。其中，第一网络设备属于多接入边缘计算系统，多接入边缘计算系统还包括第二网络设备和第三网络设备，其中，第一网络设备位于多接入边缘计算系统的中心侧，第二网络设备位于多接入边缘计算系统的边缘侧的网络域，第三网络设备位于多接入边缘计算系统的边缘侧的计算域；该方法包括：获取多接入边缘计算应用程序描述信息；从第三网络设备接收多接入边缘计算应用程序的拓扑信息；根据多接入边缘计算应用程序描述信息和多接入边缘计算应用程序的拓扑信息，向第二网络设备发送第一请求信息，和向第三网络设备发送第二请求信息，第一请求信息用于指示第二网络设备在网络域部署与多接入边缘计算应用程序对应的第一多接入边缘计算服务实例，第二请求信息用于指示第三网络设备在计算域部署与多接入边缘计算应用程序对应的第二多接入边缘计算服务实例。
可以看出，在本申请实施例中，与现有的ETSI定义的多接入边缘技术的标准架构相比，本申请的多边缘接入中在中心侧部署了第一网络设备、在边缘侧的网络域部署了第二网络设备以及在边缘侧的计算域部署了第三网络设备，这样在多接入边缘计算应用程序上线并完成实例化之后，比如，向多接入边缘计算平台注册服务注册消息(多接入边缘计算应用程序的 拓扑信息)之后，第三网络设备将多接入边缘计算平台转发的多接入边缘计算应用程序的拓扑信息发送给第一网络设备，这样第一网络设备就根据该拓扑信息以及预先获取的到多接入边缘应用程序描述信息，指示第二网络设备在网络域部署第一多接入边缘计算服务实例以及指示第三网络设备在计算域部署第二多接入边缘计算服务实例，从而实现在多接入边缘计算应用程序实例化完成之后，自动在边缘侧的网络域和计算域部署相应的多接入边缘计算服务实例，无需人工配置，降低了多接入边缘计算应用程序的运维成本。此外，第一网络设备、第二网络设备以及第三网络设备之间的协调工作，完成多接入边缘计算应用程序的自动化部署，从而不需要人工参与，也就不用将多接入边缘计算站点的位置信息(即多接入边缘计算应用程序的部署位置)开放给多接入边缘计算应用程序的信息提供方，有利于提高电信运营商的竞争力，保护多接入边缘计算站点的安全。
在一些可能的实施方式中，拓扑信息是第三网络设备根据多接入边缘计算应用程序的服务注册消息确定的，服务注册消息是多接入边缘计算应用程序注册给网络域的多接入边缘计算平台，并由网络域的多接入边缘计算平台发布给第三网络设备的。
可以看出，第三网络设备向多接入边缘计算平台订阅多接入边缘计算应用程序的服务注册消息，从而在多接入边缘计算应用程序上线完成实例化后，多接入边缘计算平台会将多接入边缘计算应用程序的服务注册消息发布给第三网络设备，这样第三网络设备就可以自动发现多接入边缘计算应用程序上线，无需人工参与，从而便于后续多接入边缘计算服务实例的部署，提高了多接入边缘计算应用程序的上线效率。
在一些可能的实施方式中，第一请求消息包括第一边缘接入计算服务以及与第一边缘接入计算服务对应的第一网络资源；第一请求消息用于指示第二网络设备根据多接入边缘计算应用程序的拓扑信息、第一边缘接入计算服务以及第一网络资源，部署第一多接入边缘计算服务实例，第一多接入边缘计算服务实例用于提供第一边缘接入计算服务。
可以看出，在本实施方式中，第一网络设备只将需要在网络域部署的第一多接入边缘计算服务和第一网络资源分配给第二网络设备，由第二网络设备自主决策在本地完成对第一多接入边缘计算服务的实例化，在本地部署第一多接入边缘计算服务实例。由于第一网络设备只需要完成资源和多接入边缘服务的分配工作，从而减少了第一网络设备的计算压力，提高第一网络设备工作的稳定性。
在一些可能的实施方式中，第一请求消息还用于指示第二网络设备生成与第一多接入边缘计算服务实例对应的第一业务规则，并向第一多接入边缘计算服务实例插入第一业务规则。
可以看出，在本实施方式中，第一网络设备还可以通过第一请求消息指示第二网络设备生成与第一多接入边缘计算服务实例对应的第一业务规则，不需要人工配置在网络域部署的多接入边缘计算服务实例的业务规则，提高了网络域中的业务规则生成的自动化，提高了多接入边缘计算应用程序上线后的业务使能效率。
在一些可能的实施方式中，第二请求消息包括第二边缘接入计算服务以及与第二边缘接入计算服务对应的第二网络资源；第二请求消息用于指示第三网络设备根据多接入边缘计算应用程序的拓扑信息、第二边缘接入计算服务以及第二网络资源，部署第二多接入边缘计算服务实例，第二多接入边缘计算服务实例用于提供第一边缘接入计算服务。
可以看出，在本实施方式中，第一网络设备只将需要在计算域部署的第二多接入边缘计算服务和第二网络资源分配给第三网络设备，由第三网络设备自主决策在本地完成对第二多接入边缘计算服务的实例化，在本地部署第二多接入边缘计算服务实例。由于第一网络设备只需要完成计算域所需的网络资源和多接入边缘服务的分配工作，从而减少了第一网络设备 的计算压力，提高第一网络设备工作的稳定性。
在一些可能的实施方式中，第二请求消息还用于指示第三网络设备生成与第二多接入边缘计算服务实例对应的第二业务规则，并向第二多接入边缘计算服务实例插入第二业务规则。
可以看出，在本实施方式中，第一网络设备还可以通过第二请求消息指示第三网络设备生成与第二多接入边缘计算服务实例对应的第二业务规则，不需要人工配置在计算域部署的多接入边缘计算服务实例的业务规则，提高了计算域中业务规则生成的自动化，提高了多接入边缘计算应用程序的上线效率。
在一些可能的实施方式中，向第二网络设备发送第一请求消息之后，该方法还包括：从第二网络设备接收第一响应消息，第一响应消息包括下行跨域通道参数；其中，第二请求消息包括下行跨域通道参数，第二请求消息还用于指示第三网络设备根据下行跨域通道参数建立网络域和计算域之间的跨域互访通道。
应理解，下行跨域通道参数即在网络域部署的跨域通道服务实例的跨域通道参数，通过第一响应消息将下行跨域通道参数发送第一网络设备，由第一网络设备通过第二请求消息将下行跨域通道参数发送给第三网络设备，这样计算域的跨域通道服务实例，计算域中的跨域访问服务实例可以使用该下行跨域通道参数和计算域本端的上行跨域通道参数，跨域访问网络域。所以，本申请中在网络域和计算域分离部署的情况下，在为多接入边缘计算应用程序部署相应的多接入边缘服务实例的过程中，自动建立跨域访问服务，打通计算域和网络域之间的通道，无需人工打通网络域和计算域，进而降低了多接入边缘计算应用程序的运维成本，提高了多接入边缘计算的上线效率。
在一些可能的实施方式中，向第三网络设备发送第二请求消息之后，该方法还包括：从第三网络设备接收第二响应消息，第二响应消息包括上行跨域通道参数；向第二网络设备发送第三请求消息，第三请求消息包括上行跨域通道参数，第三请求消息用于指示第二网络设备根据上行跨域通道参数以及下行跨域通道参数，建立网络域和计算域之间的跨域互访通道。
应理解，将上行跨域访问通道参数发送给第一网络设备，以便第一网络设备将跨域访问通道参数转发给第二网络设备，从而网络域中的跨域访问服务实例可以使用该上行跨域访问通道参数和本端的下行跨域访问通道参数，跨域访问计算域，即在网络域和计算域分离部署的情况下，实现自动化打通网络域和计算域之间的通道，无需人工参与。
在一些可能的实施方式中，该方法还包括：向第二网络设备发送第四请求消息，第四请求消息用于指示第二网络设备通知网络域的用户面功能实体使能第一业务规则，用户面功能实体是第二网络设备根据多接入边缘计算应用程序的拓扑信息确定的。
可以看出，在本实施方式中，第一网络设备通过第四请求消息单独指示网络域的用户面功能实体去使能之前生成的第一业务规则，这样是给多接入边缘计算应用程序中的服务实例的使能和生效留一定的缓冲时长，若直接使能第一业务规则和第二业务规则，而多接入边缘计算应用程序中的服务实例还未生效，这样用户设备在边缘侧进行本地分流时，多接入边缘计算应用程序就会无法提供边缘内容，用户设备在多次尝试之后，会被边缘侧的用户面功能实体将用户数据报文转到中心侧去获取数据内容，反而增加了用户的通信时延。而不直接使能第一业务规则，若多接入边缘计算应用程序中的服务实例的还未生效，边缘侧的多接入边缘计算应用程序会将用户数据报文直接转发到中心侧，不会影响用户的通信需求。
应理解，第一网络设备向第二网络设备发送第四请求消息之前，一般来说，是因为第一网络设备确定出多接入边缘计算应用程序中的所有服务实例都已完成使能和生效，可以正常为用户设备提供边缘内容。
在一些可能的实施方式中，该方法还包括：从第二网络设备接收第三响应消息，第三响应消息用于指示用户面功能实体完成对第一业务规则的使能。
在一些可能的实施方式中，该方法还包括：向中心侧的策略控制功能发送第五请求消息，第五请求消息包括多接入边缘计算应用程序的实例标识和位置信息，第五请求消息用于指示策略控制功能将多接入边缘计算应用程序的实例标识和位置信息转发给中心侧的会话管理功能，以使会话管理功能根据多接入边缘计算应用程序的位置信息选择用户面功能实体，以使用户面功能实体建立用户会话上下文，并插入多接入边缘计算应用程序的实例标识。
可以看出，在本实施方式中，第一网络设备还可以向中心侧的策略控制功能发送第五请求消息，以便将新上线的多接入边缘计算应用程序的实例信息和位置信息插入给边缘侧对应的用户面功能实体，建议用户会话文。而无需人工向插入策略控制功能插入新上线的多接入边缘计算应用程序的实例信息和位置信息，减少了人工成本。
在一些可能的实施方式中，从第三网络设备接收多接入边缘计算应用程序的拓扑信息之前，该方法还包括：向网络数据分析功能订阅应用程序的访问统计数据；根据应用程序的访问统计数据以及业务策略，向第三网络设备发送第一提示信息，第一提示信息用于指示第三网络设备通知计算域的网络功能虚拟化基础设施部署用于为应用程序提供边缘内容的多接入边缘计算应用程序。
可以看出，在本实施方式中，第一网络设备还可以提前向网络数据分析功能订阅应用程序的访问统计数据，这样第一网络设备可以通过预先注入的业务策略以及当前获取的应用程序的访问数据，自动触发多接入边缘计算应用程序的上线和部署，无需人工触发多接入边缘计算应用程序的上线和部署，提高了对多接入边缘计算应用程序的上线和部署的智能化，降低了多接入边缘计算应用程序的人工部署成本。
在一些可能的实施方式中，从第三网络设备接收多接入边缘计算应用程序的拓扑信息之前，该方法还包括：从应用程序提供方获取第六请求消息，第六请求消息用于请求部署为应用程序提供边缘内容的多接入边缘计算应用程序；根据第六请求消息，向第三网络设备发送第一提示信息，第一提示信息用于指示第三网络设备通知计算域的网络功能虚拟化基础设施部署用于为应用程序提供边缘内容的多接入边缘计算应用程序。
可以看出，在本实施方式中，第一网络设备还可以接收应用程序提供方的第六请求消息，根据应用程序提供方的请求自动触发多接入边缘应用程序的部署，提高多接入边缘应用程序部署的灵活性，以及便捷性。
第二方面，本申请实施例提供一种服务实例部署方法，该方法的执行主体可以是第二网络设备，也可以是应用于第二网络设备中的芯片。下面以执行主体是第二网络设备为例进行描述。其中，第二网络设备属于多接入边缘计算系统，多接入边缘计算系统还包括第一网络设备和第三网络设备，其中，第一网络设备位于多接入边缘计算系统的中心侧，第二网络设备位于多接入边缘计算系统的边缘侧的网络域，第三网络设备位于多接入边缘计算系统的边缘侧的计算域；该方法包括：从第一网络设备接收第一请求消息，第一请求消息是第一网络设备根据多接入边缘计算应用程序描述信息以及多接入边缘计算应用程序的拓扑信息生成的，多接入边缘计算应用程序的拓扑信息是由第二网络设备发送给第一网络设备的；根据第一请求消息在网络域部署与多接入边缘计算应用程序对应的第一多接入边缘计算服务实例。
可以看出，在本申请实施例中，第二网络设备可以根据从第一网络设备接收的第一请求信息，自动在网络域部署第一多接入边缘计算服务实例，而无需人工参与网络域的多接入边缘服务实例的部署，提高了多接入边缘计算应用的上线效率，降低了运维成本。此外，第一 网络设备、第二网络设备以及第三网络设备之间的协调工作，完成多接入边缘计算应用程序的自动化部署，从而不需要人工参与，也就不用将多接入边缘计算站点的位置信息(即多接入边缘计算应用程序的部署位置)开放给多接入边缘计算应用程序的信息提供方，有利于提高电信运营商的竞争力，保护多接入边缘计算站点的安全。
在一些可能的实施方式中，拓扑信息是第三网络设备根据多接入边缘计算应用程序的服务注册消息确定的，服务注册消息是多接入边缘计算应用程序注册给网络域的多接入边缘计算平台，并由网络域的多接入边缘计算平台发布给第三网络设备的。
可以看出，第三网络设备向多接入边缘计算平台订阅多接入边缘计算应用程序的服务注册消息，从而在多接入边缘计算应用程序上线完成实例化后，多接入边缘计算平台会将多接入边缘计算应用程序的服务注册消息发布给第三网络设备，这样第三网络设备就可以自动发现多接入边缘计算应用程序上线，无需人工参与，从而便于后续多接入边缘计算服务实例的部署，提高了多接入边缘计算应用程序的上线效率。
在一些可能的实施方式中，第一请求消息包括第一边缘接入计算服务以及与第一边缘接入计算服务对应的第一网络资源，根据第一请求消息在网络域部署与多接入边缘计算应用程序对应的第一多接入边缘计算服务实例，包括：根据多接入边缘计算应用程序的拓扑信息、第一边缘接入计算服务以及第一网络资源，部署第一多接入边缘计算服务实例，其中，第一多接入边缘计算服务实例用于提供第一边缘接入计算服务。
可以看出，在本实施方式中，第一网络设备只将需要在网络域部署的第一多接入边缘计算服务和第一网络资源分配给第二网络设备；然后，第二网络设备自主决策在本地完成对第一多接入边缘计算服务的实例化，在本地部署第一多接入边缘计算服务实例。这样第一网络设备只需要完成资源和多接入边缘服务的分配工作，从而减少了第一网络设备的计算压力，提高第一网络设备工作的稳定性。由于第二网络设备具有自主决策功能，后续第一多接入边缘计算服务实例发生变更(比如，失效或者业务规则的变更)，第二网络设备可以自主对该第一多接入边缘计算服务实例的变更进行调整，无需向第一网络设备上报，从而提高对网络域的多接入边缘计算服务实例的更新效率。
在一些可能的实施方式中，根据第一请求消息在网络域部署与多接入边缘计算应用程序对应的第一多接入边缘计算服务实例之后，该方法还包括：生成与第一多接入边缘计算服务实例对应的第一业务规则，并向第一多接入边缘计算服务实例插入第一业务规则。
可以看出，在本实施方式中，第二网络设备还可以自动生成与第一多接入边缘计算服务实例对应的第一业务规则，并向第一多接入边缘计算服务实例插入第一业务规则，而不需要人工配置该第一业务规则以及插入第一业务规则，进一步降低了多接入边缘计算应用程序的运维成本，提高多接入边缘计算应用程序的上线效率。
在一些可能的实施方式中，该方法还包括：向第一网络设备发送第一响应消息，第一响应消息包括下行跨域通道参数，以使第三网络设备根据下行跨域通道参数建立网络域和计算域之间的跨域互访通道。
可以看出，在本实施方式中，第二网络设备生成本端的下行跨域通道参数，并将下行跨域通道参数给到的第二网络设备，这样即使在网络域和计算域分离部署的情况下，由于第二网络设备和第三网络设备获取到了上行跨域通道参数以及下行跨域通道参数，可以自动建立跨域访问通道，打通计算域和网络域之间的通道，无需人工打通网络域和计算域，进而降低了多接入边缘计算应用程序的运维成本，提高了多接入边缘计算的上线效率。
在一些可能的实施方式中，该方法还包括：向第一网络设备发送第一响应消息之后，所 述方法还包括：从第一网络设备接收第三请求消息，第三所述第三请求消息包括上行跨域通道参数；根据上行跨域通道参数以及下行跨域通道参数，建立网络域和计算域之间的跨域互访通道。
可以看出，在本实施方式中，第二网络设备可以根据本端生成的下行跨域通道参数以及第三网络设备生成的建立跨域互访通道，这样在一个多接入边缘计算应用程序上线之后，并且在网络域和计算域分离部署的情况下，无需人工参与，即可打通网络域和计算域，进而降低了多接入边缘计算应用程序的运维成本，提高了多接入边缘计算的上线效率。
在一些可能的实施方式中，该方法还包括：从第一网络设备接收第四请求消息；根据应用程序的拓扑信息，确定网络域的用户面功能实体；根据网络域的用户面功能实体通知网络域的用户面功能实体使能第一业务规则。
可以看出，在本实施方式中，第二网络设备根据第四请求消息单独使能之前生成的第一业务规则，这样是给多接入边缘计算应用程序中的服务实例的使能和生效留一定的缓冲时长，若直接使能第一业务规则和第二业务规则，而多接入边缘计算应用程序中的服务实例还未生效，这样用户设备在边缘侧进行本地分流时，多接入边缘计算应用程序就会无法提供边缘内容，用户设备在多次尝试之后，会被边缘侧的用户面功能实体将用户数据报文转到中心侧去获取数据内容，反而增加了用户的通信时延。而不直接使能第一业务规则，若多接入边缘计算应用程序中的服务实例的还未生效，边缘侧的多接入边缘计算应用程序会将用户数据报文直接转发到中心侧，不会影响用户的通信需求。
第三方面，本申请实施例提供一种服务实例部署方法，该方法的执行主体可以是第三网络设备，也可以是应用于第三网络设备中的芯片。下面以执行主体是第三网络设备为例进行描述。其中，第三网络设备属于多接入边缘计算系统，多接入边缘计算系统还包括第一网络设备和第二网络设备，其中，第一网络设备位于多接入边缘计算系统的中心侧，第二网络设备位于多接入边缘计算系统的边缘侧的网络域，第三网络设备位于多接入边缘计算系统的边缘侧的计算域，该方法包括：向第一网络设备发送多接入边缘计算应用程序的拓扑信息；从第一网络设备接收第二请求消息，第二请求消息是第一网络设备根据多接入边缘计算应用程序描述信息以及多接入边缘计算应用程序的拓扑信息生成的；根据第二请求消息在网络域部署与多接入边缘计算应用程序对应的第二多接入边缘计算服务实例。
可以看出，在本申请实施例中，在一个多接入边缘计算应用程序上线完成实例化之后，第三网络设备可以将该多接入边缘计算应用程序的拓扑信息发送给第一网络设备，这样第三网络设备可以根据从第一网络设备接收的第二请求信息，自动在计算域部署第二多接入边缘计算服务实例，而无需人工参与计算域的多接入边缘服务实例的部署，提高了多接入边缘计算应用的上线效率，降低了运维成本。此外，第一网络设备、第二网络设备以及第三网络设备之间的协调工作，完成多接入边缘计算应用程序的自动化部署，从而不需要人工参与，也就不用将多接入边缘计算站点的位置信息(即多接入边缘计算应用程序的部署位置)开放给多接入边缘计算应用程序的信息提供方，有利于提高电信运营商的竞争力，保护多接入边缘计算站点的安全。
在一些可能的实施方式中，第二请求消息包括第二边缘接入计算服务以及与第二边缘接入计算服务对应的第二网络资源，第二请求消息包括第二边缘接入计算服务以及与第二边缘接入计算服务对应的第二网络资源，包括：根据多接入边缘计算应用程序的拓扑信息、第二边缘接入计算服务以及第二网络资源，部署第二多接入边缘计算服务实例，其中，第二多接入边缘计算服务实例用于提供第一边缘接入计算服务。
可以看出，在本实施方式中，第一网络设备只将需要在计算域部署的第二多接入边缘计算服务和第二网络资源分配给第三网络设备；然后，第三网络设备自主决策在本地完成对第二多接入边缘计算服务的实例化，在本地部署第二多接入边缘计算服务实例。这样第一网络设备只需要完成资源和多接入边缘服务的分配工作，从而减少了第一网络设备的计算压力，提高第一网络设备工作的稳定性。由于第三网络设备具有自主决策功能，后续第二多接入边缘计算服务实例发生变更(比如，失效或者业务规则的变更)，第二网络设备可以自主对该第二多接入边缘计算服务实例的变更进行调整，无需向第一网络设备上报，从而提高对计算域中的多接入边缘计算服务实例的更新效率。
在一些可能的实施方式中，该方法还包括：生成与第二多接入边缘计算服务实例对应的第二业务规则，并向第二多接入边缘计算服务实例插入第二业务规则。
可以看出，在本实施方式中，第三网络设备还可以自动生成与第二多接入边缘计算服务实例对应的二业务规则，并向第二多接入边缘计算服务实例插入第人业务规则，而不需要人工配置该第二业务规则以及插入第二业务规则，进一步降低了多接入边缘计算应用程序的运维成本，提高多接入边缘计算应用程序的上线效率。
在一些可能的实施方式中，该方法还包括：向第一网络设备发送第二响应消息，第二响应消息包括上行跨域通道参数，以使第二网络设备根据上行跨域通道参数，建立网络域和计算域之间的跨域互访通道。
可以看出，在本实施方式中，第三网络设备生成本端的上行跨域通道参数，并将上行跨域通道参数给到的第二网络设备，这样即使在网络域和计算域分离部署的情况下，由于第二网络设备和第三网络设备获取到了上行跨域通道参数以及下行跨域通道参数，可以自动建立跨域访问通道，打通计算域和网络域之间的通道，无需人工打通网络域和计算域，进而降低了多接入边缘计算应用程序的运维成本，提高了多接入边缘计算的上线效率。
在一些可能的实施方式中，第二请求消息包括下行跨域通道参数，该方法还包括：根据下行跨域通道参数建立网络域和计算域之间的跨域互访通道。
可以看出，在本实施方式中，第三网络设备可根据上行跨域通道参数以及下行跨域通道参数，自动建立跨域访问通道，打通计算域和网络域之间的通道，无需人工打通网络域和计算域，进而降低了多接入边缘计算应用程序的运维成本，提高了多接入边缘计算的上线效率。
在一些可能的实施方式中，向第一网络设备发送多接入边缘计算应用程序的拓扑信息之前，该方法还包括：从第一网络设备接收第一提示信息；根据第一提示信息通知计算域的网络功能虚拟化基础设施部署用于为应用程序提供边缘内容的多接入边缘计算应用程序。
可以看出，在本实施方式中，第三网络设备还可以从第一网络设备接收第一提示信息，根据第一网络设备的指示自动触发部署多接入边缘计算应用程序，无需人工触发多接入边缘计算应用程序，进而提高了多接入边缘计算应用程序的部署和上线效率。
在一些可能的实施方式中，第一提示信息是第一网络设备根据应用程序的访问统计数据以及业务策略生成的或根据从应用程序提供方获取到的第六请求消息生成的，第六请求消息用于请求部署为应用程序提供边缘内容的多接入边缘计算应用程序。
可以看出，在本实施方式中，第一提示信息可以根据应用程序的访问统计数据生成，也可以根据应用程序信息提供方的请求，从而提高自动化部署多接入边缘计算应用程序的灵活性。
第四方面，本申请实施例提供一种跨域互访通道建立方法，该方法的执行主体可以是第五网络设备，也可以是应用于第五网络设备中的芯片。下面以执行主体是第五网络设备为例 进行描述。其中，第五网络设备属于跨域互访系统，跨域互访系统还包括第四网络设备和第六网络设备，其中，第四网络设备位于跨域互访系统的中心侧，第五网络设备位于跨域互访系统的第一计算域，第六网络设备位于跨域互访系统的第二计算域；该方法包括：向第四网络设备发送第二计算域的实例信息和第一计算域中用于跨域互访的第一多接入边缘计算服务实例的第一跨域通道参数；从第四网络设备接收第二计算域中用于跨域访问的第二多接入边缘计算服务实例的第二跨域通道参数；其中，第一跨域通道参数和第二跨域通道参数用于表征第一多接入边缘计算服务实例与第二多接入边缘计算服务实例之间的跨域互访通道。
可以看出，在本申请实施例中，在多接入边缘计算应用程序进行跨域访问的过程中，第五网络设备可以通过第四网络设备将本端的第一跨域通道参数给到第二计算域的第六网络设备，以及可以通过第四网络设备获取第二计算域的第二跨域通道参数，这样第五网络设备就可以根据该第一跨域通道参数和第二跨域通道参数建立第一计算域和第二计算域之间的跨域互访通道，可以看出，在建立跨域互访通道的过程中，无需人工参与，可以自动完成跨域互访通道的建立，降低了多接入边缘计算应用程序的运维成本。
在一些可能的实施方式中，向第四网络设备发送第二计算域的实例信息和第一计算域中用于跨域互访的第一多接入边缘计算服务实例的第一跨域通道参数之前，该方法还包括：从第一计算域的第一多接入边缘计算平台接收跨域互访请求，跨域互访请求是由第一计算域的第一多接入边缘计算应用程序发送给第一多接入边缘计算平台，并由第一多接入边缘计算平台发布给第五网络设备的，跨域互访请求包括第二计算域的实例信息，跨域互访请求用于指示第一计算域的第一多接入边缘计算应用程序请求跨域访问第二计算域中的第二多接入边缘计算应用程序。
在一些可能的实施方式中，从第一计算域的第一多接入边缘计算平台接收跨域互访请求之前，该方法还包括：向第一多接入边缘计算平台订阅第一多接入边缘计算应用程序的跨域互访请求。
可以看出，在本实施方式中，第五网络设备提前向第一多接入边缘计算应用平台订阅第一计算域中的第一多接入边缘计算应用程序的跨域访问请求，这样当第一多接入边缘计算应用程序有跨域访问需求时，第五网络设备可以自动发现该跨域访问需求，无需人工参与，提高跨域互访通道建立的效率。
在一些可能的实施方式中，向第四网络设备发送第二计算域的实例信息和第一计算域中用于跨域互访的第一多接入边缘计算服务实例的第一跨域通道参数之前，该方法还包括：在第一计算域部署第一多接入边缘计算服务实例以及配置第一跨域通道参数。
可以看出，在本实施方式中，第五网络设备还可以按需部署第一多接入边缘计算服务实例，比如，该第一计算域中没有用于跨域访问的多接入边缘服务实例时，则自动部署第一多接入边缘计算服务实例，从而实现完全自动化建立跨域互访通道。
在一些可能的实施方式中，在第一计算域部署第一多接入边缘计算服务实例以及配置第一跨域通道参数之后，该方法还包括：配置第一多接入边缘计算服务实例与第一多接入边缘计算应用程序之间的第一路由参数；从第四网络设备接收第二计算域中用于跨域访问的第二多接入边缘计算服务实例的第二跨域通道参数之后，该方法还包括：向第一多接入边缘计算平台发送跨域互访响应，并指示第一多接入边缘计算平台将跨域互访响应转发给第一多接入边缘计算应用程序，跨域互访响应包括第一路由参数，跨域访问响应用于指示第一多接入边缘计算应用程序根据第一路由参数，建立第一多接入边缘计算服务实例与第一多接入边缘计算应用程序之间的通信链路。
可以看出，在本实施方式中，第五网络设备还将第一路由参数配置给第一多接入边缘计算应用程序以及第一多接入边缘计算服务实例，从而自动化打通第一多接入边缘计算应用程序和第一多接入边缘计算服务实例之间的通信链路，无需人工参与。
第五方面，本申请实施例提供一种跨域互访通道建立方法，该方法的执行主体可以是第六网络设备，也可以是应用于第六网络设备中的芯片。下面以执行主体是第六网络设备为例进行描述。其中，第六网络设备属于跨域互访系统，跨域互访系统还包括第四网络设备和第五网络设备，其中，第四网络设备位于跨域互访系统的中心侧，第五网络设备位于跨域互访系统的第一计算域，第六网络设备位于跨域互访系统的第二计算域；方法包括：从第四网络设备接收第一计算域中用于跨域互访的第一多接入边缘计算服务实例的第一跨域通道参数；向第四网络设备发送第二计算域中用于跨域互访的第二多接入边缘计算服务实例的第二跨域通道参数，其中，第一跨域通道参数和第二跨域通道参数用于表征第一多接入边缘计算服务实例与第二多接入边缘计算服务实例之间的跨域互访通道。
可以看出，在本实施方式中，在多接入边缘计算应用程序进行跨域访问的过程中，第六网络设备可以通过第四网络设备接收对端(第二计算域)的第二跨域通道参数，以及可以通过第四网络设备将本端的第二跨域通道参数给到对端的第五网络设备，这样第五网络设备和第六网络设备就可以根据该第一跨域通道参数和第二跨域通道参数建立第一计算域和第二计算域之间的跨域互访通道，可以看出，在建立跨域互访通道的过程中，无需人工参与，可以自动完成跨域互访通道的建立，降低了跨域互访通道使能的运维成本。
在一些可能的实施方式中，向第四网络设备发送第二计算域中用于跨域互访的第二多接入边缘计算服务实例的第二跨域通道参数之前，该方法还包括：向第二计算域中的第二多接入边缘计算平台订阅用于跨域互访的第二多接入边缘计算服务实例的上线。
可以看出，在本实施方式中，第六网络设备提前向第二多接入边缘计算平台订阅第二多接入边缘计算服务实例的上线，这样第六网络设备在接收其他计算域的跨域需求时，就可以发现第二计算域是否有跨域通道服务实例的上线，以便决策是否需要在第二计算域部署用于跨域互访的第二多接入边缘服务实例，以便合理的分配第二计算域的网络资源。
在一些可能的实施方式中，向第四网络设备发送第二计算域中用于跨域互访的第二多接入边缘计算服务实例的第二跨域通道参数之前，该方法还包括：在第二计算域部署第二多接入边缘计算服务实例以及配置第二跨域通道参数。
可以看出，在本实施方式中，第六网络设备可以根据需求决策在第二就是关于部署第二多接入边缘计算服务实例，这样即使在跨域互访时，没有相应的服务实例，也可以自动化部署，从而实现完全自动化建立跨域互访通道。
在一些可能的实施方式中，在第二计算域部署第二多接入边缘计算服务实例以及配置第二跨域通道参数之后，该方法还包括：配置第二多接入边缘计算服务实例与第二多接入边缘计算应用程序之间的第二路由参数，并将第二路由参数配置给第二多接入边缘计算服务实例以及第二计算域的第二多接入边缘计算平台，第二多接入边缘计算平台用于将第二路由参数转发给第二多接入边缘计算应用程序，第二路由参数用于第二多接入边缘计算服务实例以及第二多接入边缘计算应用程序建立通信链路。
可以看出，在本实施方式中，第六网络设备还将第二路由参数配置给第二多接入边缘计算应用程序以及第二多接入边缘计算服务实例，从而自动化打通第二多接入边缘计算应用程序和第二多接入边缘计算服务实例之间的通信链路，无需人工参与。
第六方面，本申请实施例提供一种跨域互访通道建立方法，该方法的执行主体可以是第 四网络设备，也可以是应用于第四网络设备中的芯片。下面以执行主体是第四网络设备为例进行描述。其中，第四网络设备属于跨域互访系统，跨域互访系统还包括第五网络设备和第六网络设备，其中，第四网络设备位于跨域互访系统的中心侧，第五网络设备位于跨域互访系统的第一计算域，第六网络设备位于跨域互访系统的第二计算域；方法包括：从第五网络设备接收第二计算域的实例信息和第一计算域中用于跨域互访的第一多接入边缘计算服务实例的第一跨域通道参数；根据第二计算域的实例信息，向第六网络设备发送第一跨域通道参数；从第六网络设备接收第二计算域中用于跨域互访的第二多接入边缘计算服务实例的第二跨域通道参数；向第五网络设备发送第二计算域中用于跨域互访的第二多接入边缘计算服务实例的第二跨域通道参数；其中，第一跨域通道参数和第二跨域通道参数用于表征第一多接入边缘计算服务实例与第二多接入边缘计算服务实例之间的跨域互访通道。
可以看出，在本申请实施例中，在某个计算域中的多接入边缘计算应用程序需要跨域访问时，第四网络设备可以向第六网络设备转发第一多接入边缘计算服务实例的第一跨域通道参数，以及向第五网络设备转发第二多接入边缘计算服务实例的第二跨域通道参数，这样第五网络设备和第六网络设备都可以获取到第一跨域通道参数以及第二跨域通道参数，从而自动化建立了第一计算域和第二计算域之间的跨域互访通道，无需人工参与，降低了多接入边缘计算应用程序的运维成本。
第七方面，本申请实施例提供一种通信装置，有益效果可以参见第一方面的描述此处不再赘述。通信装置具有实现上述第一方面的方法实例中行为的功能。功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块。在一个可能的设计中，该通信装置包括：收发模块，用于获取多接入边缘计算应用程序描述信息，以及从第三网络设备接收多接入边缘计算应用程序的拓扑信息；处理模块，用于控制收发模块根据多接入边缘计算应用程序描述信息和多接入边缘计算应用程序的拓扑信息，向第二网络设备发送第一请求信息，和向第三网络设备发送第二请求信息，第一请求信息用于指示第二网络设备在网络域部署与多接入边缘计算应用程序对应的第一多接入边缘计算服务实例，第二请求信息用于指示第三网络设备在计算域部署与多接入边缘计算应用程序对应的第二多接入边缘计算服务实例。这些模块可以执行上述第一方面方法示例中的相应功能，具体参见第一方面方法示例中的详细描述，此处不做赘述。
第八方面，本申请实施例提供一种通信装置，有益效果可以参见第二方面的描述此处不再赘述。通信装置具有实现上述第二方面的方法实例中行为的功能。功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块。在一个可能的设计中，该通信装置包括：收发模块，用于从第一网络设备接收第一请求消息，第一请求消息是第一网络设备根据多接入边缘计算应用程序描述信息以及多接入边缘计算应用程序的拓扑信息生成的，多接入边缘计算应用程序的拓扑信息是由第二网络设备发送给第一网络设备的；处理模块，用于根据第一请求消息在网络域部署与多接入边缘计算应用程序对应的第一多接入边缘计算服务实例。这些模块可以执行上述第二方面方法示例中的相应功能，具体参见第二方面方法示例中的详细描述，此处不做赘述。
第九方面，本申请实施例提供一种通信装置，有益效果可以参见第三方面的描述此处不再赘述。通信装置具有实现上述第三方面的方法实例中行为的功能。功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块。在一个可能的设计中，该通信装置包括：收发模块，用于向第一网络设备发送多接入边缘计算应用程序的拓扑信息，以及从第一网络设备接收第二请求消息，第二请求消息是第一 网络设备根据多接入边缘计算应用程序描述信息以及多接入边缘计算应用程序的拓扑信息生成的；处理模块，用于根据第二请求消息在网络域部署与多接入边缘计算应用程序对应的第二多接入边缘计算服务实例。这些模块可以执行上述第三方面方法示例中的相应功能，具体参见第三方面方法示例中的详细描述，此处不做赘述。
第十方面，本申请实施例提供一种通信装置，有益效果可以参见第四方面的描述此处不再赘述。通信装置具有实现上述第一方面的方法实例中行为的功能。功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块。在一个可能的设计中，该通信装置包括：处理模块，用于控制收发模块向第四网络设备发送第二计算域的实例信息和第一计算域中用于跨域互访的第一多接入边缘计算服务实例的第一跨域通道参数；以及从第四网络设备接收第二计算域中用于跨域访问的第二多接入边缘计算服务实例的第二跨域通道参数；其中，第一跨域通道参数和第二跨域通道参数用于表征第一多接入边缘计算服务实例与第二多接入边缘计算服务实例之间的跨域互访通道。这些模块可以执行上述第三方面方法示例中的相应功能，具体参见第三方面方法示例中的详细描述，此处不做赘述。
第十一方面，本申请实施例提供一种通信装置，有益效果可以参见第五方面的描述此处不再赘述。通信装置具有实现上述第五方面的方法实例中行为的功能。功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块。在一个可能的设计中，该通信装置包括：处理模块，控制收发模块从第四网络设备接收第一计算域中用于跨域互访的第一多接入边缘计算服务实例的第一跨域通道参数；以及向第四网络设备发送第二计算域中用于跨域互访的第二多接入边缘计算服务实例的第二跨域通道参数；其中，第一跨域通道参数和第二跨域通道参数用于表征第一多接入边缘计算服务实例与第二多接入边缘计算服务实例之间的跨域互访通道。这些模块可以执行上述第五方面方法示例中的相应功能，具体参见第五方面方法示例中的详细描述，此处不做赘述。
第十二方面，本申请实施例提供一种通信装置，有益效果可以参见第六方面的描述此处不再赘述。通信装置具有实现上述第六方面的方法实例中行为的功能。功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块。在一个可能的设计中，该通信装置包括：处理模块，用于控制收发模块从第五网络设备接收第二计算域的实例信息和第一计算域中用于跨域互访的第一多接入边缘计算服务实例的第一跨域通道参数；根据第二计算域的实例信息，向第六网络设备发送第一跨域通道参数；从第六网络设备接收第二计算域中用于跨域互访的第二多接入边缘计算服务实例的第二跨域通道参数；以及向第五网络设备发送第二计算域中用于跨域互访的第二多接入边缘计算服务实例的第二跨域通道参数；其中，第一跨域通道参数和第二跨域通道参数用于表征第一多接入边缘计算服务实例与第二多接入边缘计算服务实例之间的跨域互访通道。这些模块可以执行上述第六方面方法示例中的相应功能，具体参见第六方面方法示例中的详细描述，此处不做赘述。
第十三方面，本申请实施例提供一种通信装置，该通信装置可以为上述方法实施例中的第一网络设备，或者为设置在第一网络设备中的芯片。该通信装置包括通信接口以及处理器，可选的，还包括存储器。其中，该存储器用于存储计算机程序或指令，处理器与存储器、通信接口耦合，当处理器执行计算机程序或指令时，使通信装置执行上述方法实施例中由第一网络设备所执行的方法。
第十四方面，本申请实施例提供一种通信装置，该通信装置可以为上述方法实施例中的 第二网络设备，或者为设置在第二网络设备中的芯片。该通信装置包括通信接口以及处理器，可选的，还包括存储器。其中，该存储器用于存储计算机程序或指令，处理器与存储器、通信接口耦合，当处理器执行计算机程序或指令时，使通信装置执行上述方法实施例中由第二网络设备所执行的方法。
第十五方面，本申请实施例提供一种通信装置，该通信装置可以为上述方法实施例中的第三网络设备，或者为设置在第三网络设备中的芯片。该通信装置包括通信接口以及处理器，可选的，还包括存储器。其中，该存储器用于存储计算机程序或指令，处理器与存储器、通信接口耦合，当处理器执行计算机程序或指令时，使通信装置执行上述方法实施例中由第三网络设备所执行的方法。
第十六方面，本申请实施例提供一种通信装置，该通信装置可以为上述方法实施例中的第二网络设备，或者为设置在第四网络设备中的芯片。该通信装置包括通信接口以及处理器，可选的，还包括存储器。其中，该存储器用于存储计算机程序或指令，处理器与存储器、通信接口耦合，当处理器执行计算机程序或指令时，使通信装置执行上述方法实施例中由第四网络设备所执行的方法。
第十七方面，本申请实施例提供一种通信装置，该通信装置可以为上述方法实施例中的第五网络设备，或者为设置在第五网络设备中的芯片。该通信装置包括通信接口以及处理器，可选的，还包括存储器。其中，该存储器用于存储计算机程序或指令，处理器与存储器、通信接口耦合，当处理器执行计算机程序或指令时，使通信装置执行上述方法实施例中由第五网络设备所执行的方法。
第十八方面，本申请实施例提供一种通信装置，该通信装置可以为上述方法实施例中的第六网络设备，或者为设置在第六网络设备中的芯片。该通信装置包括通信接口以及处理器，可选的，还包括存储器。其中，该存储器用于存储计算机程序或指令，处理器与存储器、通信接口耦合，当处理器执行计算机程序或指令时，使通信装置执行上述方法实施例中由第六网络设备所执行的方法。
第十九方面，提供了一种计算机程序产品，该计算机程序产品包括：计算机程序代码，当计算机程序代码被运行时，使得上述各方面中由第一网络设备执行的方法被执行。
第二十方面，提供了一种计算机程序产品，该计算机程序产品包括：计算机程序代码，当计算机程序代码被运行时，使得上述各方面中由第二网络设备执行的方法被执行。
第二十一方面，提供了一种计算机程序产品，该计算机程序产品包括：计算机程序代码，当计算机程序代码被运行时，使得上述各方面中由第三网络设备执行的方法被执行。
第二十二方面，提供了一种计算机程序产品，该计算机程序产品包括：计算机程序代码，当计算机程序代码被运行时，使得上述各方面中由第四网络设备执行的方法被执行。
第二十三方面，提供了一种计算机程序产品，该计算机程序产品包括：计算机程序代码，当计算机程序代码被运行时，使得上述各方面中由第五网络设备执行的方法被执行。
第二十四方面，提供了一种计算机程序产品，该计算机程序产品包括：计算机程序代码，当计算机程序代码被运行时，使得上述各方面中由第六网络设备执行的方法被执行。
第二十五方面，本申请提供了一种芯片系统，该芯片系统包括处理器，用于实现上述各方面的方法中第一网络设备的功能。在一种可能的设计中，该芯片系统还包括存储器，用于保存程序指令和/或数据。该芯片系统，可以由芯片构成，也可以包括芯片和其他分立器件。
第二十六方面，本申请提供了一种芯片系统，该芯片系统包括处理器，用于实现上述各方面的方法中第二网络设备的功能。在一种可能的设计中，该芯片系统还包括存储器，用于 保存程序指令和/或数据。该芯片系统，可以由芯片构成，也可以包括芯片和其他分立器件。
第二十七方面，本申请提供了一种芯片系统，该芯片系统包括处理器，用于实现上述各方面的方法中第三网络设备的功能。在一种可能的设计中，该芯片系统还包括存储器，用于保存程序指令和/或数据。该芯片系统，可以由芯片构成，也可以包括芯片和其他分立器件。
第二十八方面，本申请提供了一种芯片系统，该芯片系统包括处理器，用于实现上述各方面的方法中第四网络设备的功能。在一种可能的设计中，该芯片系统还包括存储器，用于保存程序指令和/或数据。该芯片系统，可以由芯片构成，也可以包括芯片和其他分立器件。
第二十九方面，本申请提供了一种芯片系统，该芯片系统包括处理器，用于实现上述各方面的方法中第五网络设备的功能。在一种可能的设计中，该芯片系统还包括存储器，用于保存程序指令和/或数据。该芯片系统，可以由芯片构成，也可以包括芯片和其他分立器件。
第三十方面，本申请提供了一种芯片系统，该芯片系统包括处理器，用于实现上述各方面的方法中第六网络设备的功能。在一种可能的设计中，该芯片系统还包括存储器，用于保存程序指令和/或数据。该芯片系统，可以由芯片构成，也可以包括芯片和其他分立器件。
第三十一方面，本申请提供了一种计算机可读存储介质，该计算机可读存储介质存储有计算机程序，当该计算机程序被运行时，实现上述各方面中由第一网络设备执行的方法。
第三十二方面，本申请提供了一种计算机可读存储介质，该计算机可读存储介质存储有计算机程序，当该计算机程序被运行时，实现上述各方面中由第二网络设备执行的方法。
第三十三方面，本申请提供了一种计算机可读存储介质，该计算机可读存储介质存储有计算机程序，当该计算机程序被运行时，实现上述各方面中由第三网络设备执行的方法。
第三十四方面，本申请提供了一种计算机可读存储介质，该计算机可读存储介质存储有计算机程序，当该计算机程序被运行时，实现上述各方面中由第四网络设备执行的方法。
第三十五方面，本申请提供了一种计算机可读存储介质，该计算机可读存储介质存储有计算机程序，当该计算机程序被运行时，实现上述各方面中由第五网络设备执行的方法。
第三十六方面，本申请提供了一种计算机可读存储介质，该计算机可读存储介质存储有计算机程序，当该计算机程序被运行时，实现上述各方面中由第六网络设备执行的方法。
第三十七方面，本申请提供了一种多接入边缘计算系统，包括第十三方面的通信装置、第十四方面的通信装置以及第十五方面的通信装置。
第三十八方面，本申请提供了一种跨域互访通道建立系统，包括第十六方面的通信装置、第十七方面的通信装置以及第十八方面的通信装置。
附图说明
图1为本申请实施例的一种MEC APP上线部署的流程示意图；
图2为本申请实施例的一种计算域中MEC APP跨域互访通道建立的流程示意图；
图3为本申请实施例的一种多边缘接入计算系统的架构图；
图4为本申请实施例的一种多接入边缘服务实例部署方法的流程示意图；
图5为本申请实施例的另一种多接入边缘服务实例部署方法的流程示意图；
图6为本申请实施例的另一种多接入边缘服务实例部署方法的流程示意图；
图7为本申请实施例的一种多接入边缘服务实例部署方法的流程示意图；
图8为本申请实施例的一种跨域互访通道建立方法的流程示意图；
图9为本申请实施例的另一种跨域互访通道建立方法的流程示意图；
图10为本申请实施例的一种通信装置的结构示意图；
图11为本申请实施例的一种通信装置的结构示意图；
图12为本申请实施例的另一种通信装置的结构示意图；
图13为本申请实施例的另一种通信装置的结构示意图。
具体实施方式
本申请实施例的方法可适用于多种系统架构，比如，应用到5G系统架构下。本申请实施例描述的网络架构以及业务场景是为了更加清楚的说明本申请实施例的技术方案，并不构成对于本申请实施例提供的技术方案的限定，本领域普通技术人员可知，随着网络架构的演变和新业务场景的出现，本申请实施例提供的技术方案对于类似的技术问题，同样适用。
应理解，本申请实施例涉及的用户设备(User Equipment，UE)可以包括移动电话(或称为“蜂窝”电话)，无线用户设备、移动用户设备、设备到设备通信(device-to-device，D2D)用户设备、车到一切(vehicle-to-everything，V2X)用户设备、机器到机器/机器类通信(machine-to-machine/machine-type communications，M2M/MTC)用户设备、物联网(internet of things，IoT)用户设备、订户单元(subscriber unit)、订户站(subscriber station)，移动站(mobile station)、远程站(remote station)、接入点(access point，AP)、远程终端(remote terminal)、接入终端(access terminal)、用户终端(user terminal)、用户代理(user agent)、或用户设备(user device)，等等。
为了便于理解本申请，首先在此介绍本申请实施例涉及的相关技术知识。
欧洲电信标准化协会(European Telecommunications Standards Institute，ETSI)标准为MEC技术定义了标准的系统架构，该系统架构包括MEC APP、多接入边缘计算应用编排器(Multi-access Edge Computing Application Orchestrator，MEAO)、多接入边缘计算平台管理器(Multi-access Edge Computing Platform Manager，MEPM)、多接入边缘计算平台(Multi-access Edge Computing Platform，MEP)和数据平台(Data Plane)。
在边缘侧位置，运营商是将MEP和MEC APP，与5G核心网(5G core)的用户面功能实体(User Plane Function，UPF)分离部署。并将MEP和MEC APP所在的位置定义为计算域，用于完成MEC APP的部署、MEC APP的服务注册以及域名系统和分流规则的激活。将UPF所在的位置定义为网络域，通过N6接口与计算域之间完成用户数据的传递，完成边缘站点的本地分流。
由于网络域和计算域的分离部署，在一个MEC APP上线之后，需要人工将该MEC APP所在的网络域和计算域之间的数据通道打通。下面结合图1说明从MEC APP上线到打通网络域和计算域之间的数据通道的整个过程。其主要包括以下步骤：
(1)首先人工决策在网络边缘位置，即边缘侧下沉部署一个MEC APP，该为用户进行本地分流，以减少用户的访问延时；因此，人工通过MEAO触发MEC APP上线部署，即相当于人工向MEAO配置部署MEC APP的命令，该命令包括多接入边缘应用程序描述(Application Descriptor，APPD)信息，该APPD中描述了该MEC APP的拓扑信息；
(2)MEAO通过MEPM请求边缘侧的网络功能虚拟化基础设施(Network Functions Virtualization Infrastructure，NFVI)为MEC APP分配资源，比如，虚拟机(Virtual Machine，VM)资源和硬件资源；
(3)NFVI完成MEC APP资源分配和部署后，给MEPM回响应，该响应携带MEC APP 的资源实例信息，比如，VM的物理地址(MAC Address)；
(4)MEPM给MEP下发MEC APP实例化配置消息，指示MEP实例化MEC APP注册的应用程序服务，以及服务实例的业务规则的配置以及激活。
(5)MEC APP对应用程序服务完成实例化之后，通过MP1接口，向MEP注册该应用程序实例状态信息(比如应用程序类型、应用程序实例标识等，可选的，还注册某些应用程序可能不实现)和各应用程序服务实例的服务实例状态信息(比如，该应用程序服务实例的类型、标识、IP地址、端口号(Port)，等等)；
(6)MEP收到第(4)步MEPM下发的MEC APP实例化配置消息，并收到第(5)步MEC APP注册的服务实例状态消息，判断MEC APP的各个应用程序服务都实例化完成之后，则配置本地的多接入边缘计算服务与该MEC APP之间的业务规则，并将该业务规则通过MP2接口下发给Data Plane，比如，配置域名系统(Domain Name System，DNS)规则给本地的DNS服务实例，并通过MP2接口下发分流规则(Traffic Rule)给Data Plane；
应理解，上述配置的业务规则针对的是已在本地部署了的多接入边缘计算服务实例的业务规则。若MEC APP还申请了其他的多接入边缘计算服务，即在APPD中勾选了该多接入边缘计算服务，并在第4步中MEC APP实例化配置请求消息中携带与该多接入边缘计算服务对应的参数下发给MEP，则在第6步执行之前，人工分配与该多接入边缘计算服务对应的网络资源，以便在Data Plane中对该多接入边缘计算服务进行实例化，最后，再配置该多接入边缘计算服务实例的业务规则，并插入该业务规则。
比如，MEC APP申请了应用程序负载均衡(Application Load Balance，APP LB)服务，则人工分配APP LB服务的虚拟应用程序网络协议地址资源池(Virtual APP IP Pool)，并将该Virtual APP IP Pool下发给该MEC APP所在边缘侧站点的Data Plane，以在该Data Plane中部署APP LB服务实例，为该MEC APP提供APP LB服务；最后，配置APP LB服务实例与该MEC APP之间的业务规则，并在APP LB服务实例中插入该业务规则。
(7)MEP给MEPM回MEC APP实例化配置响应消息，其中，MEC APP实例化配置响应消息用于指示MEC APP实例化的完成，以及指示MEC APP申请的多接入边缘计算服务实例化完成，即相当于指示用户可以在网络域执行后续操作；
(8)在计算域，人工查看到MEC APP的应用程序服务实例状态准备好之后，配置MEC APP到Data Plane之间的下行路由参数，以建立MEC APP到Data Plane的通信链路；
(9)在计算域，人工查看到MEPM接收到第(7)步的MEC APP实例化配置响应消息后，可以在中心侧的策略控制功能(Policy Control Function PCF)中插入该MEC APP实例标识(APP ID)和数据网络接入标识(Data Network Access Identity，DNAI)，其中，DNAI用于指示MEC APP的位置。这样便于后续选择相应的边缘侧UPF为用户建立会话；
(10)人工给网络域的边缘侧UPF配置上行分类器(Uplink Classification，ULCL)规则；
(11)人工给网络域的边缘侧UPF配置用于跨域访问的上下行通道路由参数，即网络域的边缘侧UPF和计算域的Data Plane之间的上下行通道路由参数；
(12)人工给计算域的Data Plane配置用于跨域访问的上下行通道路由参数，即网络域的边缘侧UPF和计算域的Data Plane之间的上下行通道路由参数；
(13)完成步骤(11)和步骤(12)之后，并人工获知MEC APP和Data Plane之间的通信链路打通，则人工给边缘侧UPF下发ULCL规则激活命令；
(14)边缘侧UPF收到ULCL规则激活命令后，正式生效UPF中的ULCL规则。
通过上述步骤(1)～步骤(14)完成了MEC APP的上线部署，并打通了该MEC APP所 在的网络域和计算域之间的跨域通道，以及业务规则的使能；这样，后续用户设备在获取数据的过程中，可以通过以下步骤进行本地分流：
A1：PCF在建立用户会话的过程中，对于符合条件的用户设备(比如，签约了套餐的用户设备或者地理位置满足要求的用户设备)，向SMF插入该MEC APP实例标识和位置标识(DNAI)；
A2：SMF根据MEC APP的DNAI，选择一个匹配的边缘侧UPF，并为用户设备建立用户会话上下文，并指示边缘侧UPF插入MEC APP实例标识(APP ID)；
A3：边缘侧UPF接收到来自用户设备的上行DNS查询报文和用户数据报文，对上行DNS查询报文和用户数据报文进行业务规则匹配，并把数据报文分发给MEC APP中相应的应用程序服务实例，从而实现本地分流。
此外，虽然建立了本地的MEC APP但是对于一个MEC APP来说，所提供的边缘内容是有限的。因此，本计算域的MEC APP可能去跨域访问另一个计算域的MEC APP，从另外一个计算域的MEC APP中获取更多的数据信息，比如，在边缘侧部署的MEC APP可以跨域访问中心侧的公有云服务(即中心侧的MEC APP)，从公有云服务中获取数据信息。然而，由于各个计算域之间分离部署，要想实现跨域访问则需先建立跨域访问通道。
下面结合图2，并以建立中心侧的计算域与边缘侧的计算域之间的跨域访问通道为例，说明跨域访问通道建立的过程，其包括以下步骤：
(1)在边缘侧，人工配置MEC APP到Data Plane的第一路由参数，该第一路由参数用于建立该MEC APP与Data Plane之间的通信链路；
(2)在边缘侧，人工配置边缘侧的Data Plane到公有云的Data Plane的上行通道参数；
(3)在公有云侧，人工配置公有云服务到公有云的Data Plane的第二路由参数，该第二路由参数用于建立公有云服务与公有云的Data Plane之间的通信链路。
(4)在公有云侧，人工配置公有云的Data Plane到边缘侧的Data Plane的下行通道参数；
(5)边缘侧MEC APP向MEP发起公有云服务的跨域访问请求，该跨域访问请求包括公有云服务的域名。
(6)MEP根据云服务的域名进行DNS查询，并向边缘侧Data Plane注册公有云服务访问API路由规则；
(7)边缘侧MEC APP通过边缘侧的Data Plane和公有云的Data Plane，并符合该API访问规则，跨域访问公有云服务。
可以看出，在部署MEC APP的过程中，需要人工静态触发APP下沉到边缘位置上线部署(MEC APP)，并需要人工触发MEC APP所需的MEC服务的实例化编排部署以及相应网络资源分配，以及需要人工编排和使能MEC APP的业务规则，导致MEC APP上线效率低。而且，MEC APP上线之后，如果进行跨域访问，则需要人工打通跨域互访通道，因此，需要投入大量的人力成本来运营和维护MEC APP，极大的增加了MEC APP上线及业务使能的运维成本。
应理解，本申请提到的网络域和计算域可以位于边缘侧，也可以位于中心侧，或者部署有5GC的UPF以及MEP的任意位置，比如，中心云或者公有云。也就是说，本申请的服务实例部署方法，不限定在边缘侧的网络域和计算域中自动化部署多接入边缘计算服务实例，也可以在中心侧或者其他位置的网络域和计算域中自动化部署多接入边缘计算服务实例。本申请以在边缘侧的网络域和计算域中部署多接入边缘计算服务实例为例进行说明，其他位置的部署方式与此类似，不再叙述。
为了便于理解本申请的多接入边缘计算服务实例部署方法，下面先结合附图介绍一下本申请的多接入边缘计算服务实例部署方法应用的多接入边缘计算系统。如图3所示，本申请的多接入边缘计算系统相对于MEC的标准系统，在中心侧部署了第一网络设备，在边缘侧的网络域部署了第二网络设备，在边缘侧的计算域部署了第三网络设备，并提前打通第一网络设备与第二网络设备之间的通信链路以及第一网络设备与第三网络设备之间的通信链路。另外，本申请是以将DNS服务部署到计算域为例进行说明，在实际应用中还可以将DNS服务部署到网络域，本申请不对DNS服务的部署位置进行限定。
示例性的，在图3示出的多接入边缘计算系统中，各个设备执行不同的功能并协同工作，完成MEC APP的自动化上线、自动化部署用于为MEC APP提供边缘计算服务的多接入边缘计算服务实例、自动化生成以及使能多接入边缘计算服务实例的业务规则以及自动化完成MEC APP的动态扩缩容以及业务规则的动态更新能。下面举例说明每个设备所执行的功能。
MEC APP，用于提供边缘内容给用户设备，实现本地分流数据报文的最终处理；
MEAO，用于管理MEC APP的软件包、编排生效MEC APP的业务规则/需求/操作策略、MEC节点选择、触发MEC APP上线、下线以及迁移；
MEPM，用于管理MEP的网元、配置MEC APP的业务规则以及需求(包括但不限于MEC APP依赖的服务授权、Traffic Rule、DNS、MEP生命周期管理以及MEC APP生命周期管理)；
第一网络设备，用于根据APPD以及MEC APP的服务拓扑信息，为边缘侧的网络域以及计算域编排相应的多接入边缘计算服务，以及为多接入边缘计算服务分配相应的网络资源，并将多接入边缘计算服务以及相应的网络资源下发给边缘侧的网络域的第二网络设备和计算域的第三网络设备，并且转发第二网络设备和/或第三网络设备建立跨域互访通道所需的跨域通道参数；
第二网络设备，用于部署网络域的多接入边缘计算服务实例、并向边缘侧的UPF下发和激活网络域的多接入边缘计算服务实例的业务规则；以及跨域互访通道的建立、释放、更新；
第三网络设备，用于完成向MEP订阅并处理MP1接口传递的MEC APP服务治理相关消息(包括：MEC APP实例状态信息注册/更新/删除、MEC APP服务实例状态信息注册/更新/删除、MEC APP Traffic Rule的激活/去活/更新)和MP1扩展接口(MEC APP申请分配多接入边缘计算服务的请求消息/响应消息)，以及部署MEC APP申请的多接入边缘计算服务实例，并向Data Plane下发和激活计算域的多接入边缘计算服务实例的业务规则；以及跨域互访数据通道的建立、释放、更新；
MEC service平台，用于向用户设备提供DNS服务，并返回DNS响应消息，以及处理用户设备和MEC APP之间的上下行用户数据报文，包括用户设备的上行数据在5GC的本地分流以及到MEC APP的负载均衡分流，以及MEC APP的下行数据到5GC的转发。
示例性的，在上述系统架构中，第一网络设备获取多接入边缘计算应用程序描述信息，该多接入边缘计算系统是由用户配置给该第一网络设备的，比如，第一网络设备可以提供北向接口，用户可通过北向接口将多接入边缘计算应用程序描述信息注入给第一网络设备；第三网络设备向第一网络设备发送多接入边缘计算应用程序的拓扑信息，其中，该拓扑信息包括MEC APP的实例信息以及MEC APP的服务实例信息，其中，MEC APP的实例信息即是MEC APP的基础信息，比如，MEC APP类型(Type)、MEC APP实例标识(Identity)、MEC APP域名(Domain))，其中，MEC APP的服务实例信息即是MEC APP中的服务实例的基础信息，比如，Service Name、Service Type，Service Instance ID、Service Instance状态等。具体 的，MEC APP的拓扑信息是在对MEC APP中的服务进行实例化的过程中，由MEC APP注册给MEP，并由MEP发送给第三网络设备的，因此，将第三网络设备发送给第一网络设备的MEC APP的拓扑信息称为MEC APP注册的拓扑信息；第一网络设备根据多接入边缘计算应用程序描述信息以及MEC APP的拓扑信息，向第二网络设备发送第一请求消息，以及向第三网络设备发送第二请求消息；第二网络设备根据第一请求消息在网络域部署与MEC APP对应的第一多接入边缘计算服务实例；第二应用程序设备根据第二请求消息在计算域部署与MEC APP对应的第二多接入边缘计算服务实例。
可以看出，在本申请实施例中，在MEC APP上线时，第一网络设备、第二网络设备以及第三网络设备之间协同工作，完成与该MEC APP对应的MEC service实例的部署，无需人工的参与，提高了MEC APP的上线效率降低了MEC APP的运维成本，提高了MEC APP的部署智能化程度。
参阅图4，图4为本申请实施例提供的一种服务实例部署方法，该方法包括以下步骤：
401：第一网络设备获取多接入边缘计算应用程序描述信息。
示例性的，该多接入边缘计算应用程序描述(APPD)信息可以由用户配置。比如，第一网络设备开放北向接口，用户可以通过北向接口将人工编排的APPD信息注入给第一网络设备，其中，APPD信息用于在计算域部署MEC APP。
402：第三网络设备向第一网络设备发送多接入边缘计算应用程序的拓扑信息。
应理解，第三网络设备在向第一网络设备发送多接入边缘计算应用程序的拓扑信息之前，需要在边缘侧的计算域部署MEC APP。如图4所示，人工编排APPD以及APP镜像模板，将人工编排的APPD以及APP镜像模板配置到MEAO，并通过MEAO人工触发部署MEC APP上线部署，后续部署MEC APP的方式与图1的方式类似，本申请不去关注MEC APP的过程。
示例性的，第三网络设备根据MEC APP的服务注册消息确定MEC APP的拓扑信息。该服务注册消息是MEC APP注册给网络域的MEP，并由MEP发布给该第三网络设备的。
示例性的，对MEC APP中的服务进行实例化的过程中，在MEC APP中的服务实例化完成后，MEC APP会向MEP注册一条服务注册消息，该条服务注册消息表征该服务已完成实例化，并且该条服务注册消息包括MEC APP的实例信息以及服务实例信息；最后，在MEC APP中的所有服务都完成实例化之后，MEC APP向MEP注册一个用于指示MEC APP中的服务全部完成实例化的服务注册信息，以便MEP将MEC APP注册的服务注册消息发布给第三网络设备。因此，MEP发布给第三网络设备的服务注册消息包括MEC APP注册的实例信息以及服务实例信息，第三网络设备可以根据MEC APP注册的服务注册信息确定出MEC APP注册的拓扑信息。
应理解，在MEP将该MEC APP的服务注册消息发布给第三网络设备之前，第三网络设备可提前向MEP订阅该MEC APP的服务注册消息；这样在MEC APP上线，向MEP注册服务注册消息之后，MEP根据之前的订阅信息，可将MEC APP注册的服务注册消息发布给第三网络设备。
此外，在第三网络设备向MEP订阅该MEC APP的服务注册消息之前，第一网络设备向第三网络设备发送人工编排的APPD，该APPD中包括人工编排MEC APP的拓扑信息，为了区分MEC APP注册的拓扑信息与APPD中描述的拓扑信息，可将APPD中描述MEC APP的拓扑信息称为人工编排的拓扑信息，其中，人工编排的拓扑信息包括人工编排的实例信息和人工编排的服务实例信息；则第三网络设备根据该人工编排的APPD，得到人工编排的实例信息，并根据人工编排的实例信息，向MEP订阅该MEC APP的服务注册消息。比如，第三 网络设备根据人工编排的MEC APP的APP ID，请求MEP在接收到与该APP ID对应的MEC APP注册的服务注册消息时，将该MEC APP的服务注册消息发布给第三网络设备。
应理解，MEC APP注册的拓扑信息为该MEC APP真实的拓扑信息，这个真实的拓扑信息可以与人工编排的拓扑信息可以相同，也可不同，本申请对此不做限定。比如，人工在APPD中编排了10个服务实例，但MEC APP实际注册的只有9个服务实例(可能因为基础设施资源不足或者MEC APP自身服务实例化失败等原因)，那么此时第三网络设备给MEPM回MEC APP实例化配置响应消息后，应等待管理面的人工决策(或者根据管理面预先注入的策略，比如是否允许MEC APP服务实例化部分成功，允许部分成功的最低比例门限)自动决策后续处理，本申请对此不作限制。假设管理面允许MEC APP服务实例化部分成功，则第三网络设备应向第一网络设备上报MEC APP注册的真实服务实例信息，第一网络设备则以此为准建立MEC APP的拓扑信息表，并维护第三网络设备上报的MEC APP的拓扑信息。
示例性的，第三网络设备根据人工编排的拓扑信息和MEC APP注册的拓扑信息，确定该MEC APP的所有服务都已经完成实例化后，即将人工编排的服务实例信息和MEC APP实际注册的服务信息进行比对，确定该MEC APP的所有服务都已经完成实例化，向第一网络设备发送MEC APP注册的MEC APP的拓扑信息。
403：第一网络设备根据多接入边缘计算应用程序描述信息和多接入边缘计算应用程序的拓扑信息，向第二网络设备发送第一请求信息，第一请求消息用于指示第二网络设备在网络域部署与多接入边缘计算应用程序对应的第一多接入边缘计算服务实例。相应的，第二网络设备根据第一请求消息，在网络域部署与多接入边缘计算应用程序对应的第一多接入边缘计算服务实例。
示例性的，第一网络设备根据APPD和MEC APP注册的MEC APP的拓扑信息，编排网络域的第一MEC Service以及与第一MEC Service对应的网络资源，其中，第一MEC Service包括但不限多接入边缘计算服务网关(Multi-access Edge Computing Service Gateway，MSG)，其中，MSG用于为MEC APP提供跨域服务。相应的，第一网络资源包括与MSG对应的通道IP Pool以及通道ID，其中，MSG对应的IP Pool以及ID用于建立跨域互访通道。
示例性，可以人工在APPD中编排为该MEC APP提供边缘计算服务的多接入边缘计算服务。因此，第一网络设备可以根据APP中人工编排的多接入边缘计算服务以及MEC APP注册的MEC APP的服务实例信息，决策需要在网络域部署的第一MEC Service。比如，人工在APPD中编排了为该MEC APP提供跨域服务的MSG，则决策需要在网络域部署MSG。
当然，在决策部署多接入边缘计算服务的过程中，第一网络设备可以结合MEC APP注册的MEC APP的服务实例信息，综合决策需要在网络域部署的第一MEC Service有哪些。比如，在APPD中没有编排MSG，但是，第一网络设备确定出MEC APP中的某些服务实例需要进行跨域访问，则决策需要在网络域部署MSG。
相应的，第二网络设备接收到第一请求消息后，根据MEC APP注册的拓扑信息、第一MEC Service以及第一网络资源在网络域(即在边缘侧的网络域的UPF)中部署第一MEC Service实例，即第二网络设备根据第一网络资源对第一MEC Service进行实例化，得到用于为MEC APP提供第一MEC Service的第一MEC Service实例。后续提到的在网络域部署MEC Service实例均是在边缘侧的网络域的UPF中部署MEC Service实例，不再赘述。
404：第一网络设备根据应用程序描述信息和多接入边缘计算应用程序的拓扑信息和向第三网络设备发送第二请求信息，第二请求消息用于指示第三网络设备在计算域部署与多接入边缘计算应用程序对应的第二多接入边缘计算服务实例。相应的，第三网络设备根据第二请 求消息，在计算域部署与多接入边缘计算应用程序对应的第二多接入边缘计算服务实例。
示例性的，与上述部署第一多接入边缘计算服务实例的方式类似，第一网络设备决策出需要在计算域部署的第二多接入边缘计算服务以及与该第二多接入边缘计算服务对应的第二网络资源，并向该第三网络设备发送第二请求信息，指示第三网络设备在计算域部署与多接入边缘计算应用程序对应的第二多接入边缘计算服务实例。
示例性的，第二多接入边缘计算服务包括但不限于：MSG、APP LB Service、第一DNS Service、第二DNS Service以及网络地址转换协议(Network Address Translation，NAT)服务，其中，MSG用于实现网络域与计算域之间的跨域互访数据通道，第一DNS Service用于支持用户设备与MEC APP之间进行数据传输过程中的域名查询，第二DNS Service用于支持MEC APP进行本域或跨域互访MEC APP/MECService的域名查询。相应的，第二网络资源包括与MSG对应的通道IP Pool和通道ID、与APP LB Service对应的虚拟(Virtual)APP IP、与NAT服务对应的NAT IP Pool。
相应的，第三网络设备接收到第二请求消息后，根据MEC APP注册的拓扑信息、第二MEC Service以及第二网络资源在计算域(即在边缘侧的计算域的MEC Service平台)中部署第二MEC Service实例，即第二网络设备根据第二网络资源对第二MEC Service进行实例化，得到用于为MEC APP提供第二MEC Service的第二MEC Service实例。后续提到的在计算域部署MEC Service实例均是在边缘侧的计算域的MEC Service平台中部署MEC Service实例，不再赘述。
在本申请的一个实施方式中，除了在APPD中编排MEC APP的MEC Service之外，MEC APP还可以动态申请MEC Service。比如，MEC APP向MEP发送MEC Service申请消息，其中，MEC Service申请消息用于请求分配MEC Service，且MEC Service申请消息包括MEC APP申请的MEC Service的类型以及标识，等等；MEP向第三网络设备转发该MEC Service申请消息，其中，该MEC APP中的每个服务实例都可以动态申请MEC Service。此外，若MEC APP的服务实例动态申请了MEC Service，则第三网络设备在向第一网络设备发送MEC APP注册拓扑信息的过程中，还可以上报MEC Service申请消息，以便第一网络设备为MEC APP动态申请的MEC Service分配相应的网络资源，以便第三网络设备在本地对MEC APP动态申请的MEC Service进行实例化；最后，第三网络设备对MEC APP动态申请的MEC Service完成实例化之后，向MEP发送MEC Service分配响应消息，并由MEP将该MEC Service分配响应消息转发给MEC APP，该MEC Service分配响应消息用于指示第三网络设备对MEC APP动态申请的MEC Service实例化信息。
可以看出，由于MEC APP可以动态申请MEC Service，因此，后续MEC APP可以根据实际需求进行动态扩缩容，然后，由第三网络设备自动化完成对该MEC APP的动态扩缩容以及动态扩缩容之后的业务规则的动态更新，从而实现对MEC APP的自动化管理。
在本申请的一个实施方式中，对于MEC APP所需的一些多接入边缘计算服务可以不用在APPD中配置，也不需要MEC APP去动态申请，而是静态配置，比如，MSG作为一个默认的多接入边缘计算服务，无论是否在APPD中配置，以及MEC APP是否动态申请，都决策出需要在网络域和计算域部署MSG。提高了多接入边缘计算服务部署的灵活性。
可以看出，第一网络设备只需决策在网络域部署哪些MEC Service以及分配好相应的网络资源，然后，由第三网络设备根据MEC APP的拓扑信息以及第一网络资源，自主在计算域部署用于提供第二MEC Service的第二多接入边缘计算服务实例，减轻了第一网络设备的处理压力，将计算任务下发到各个第三网络设备，提高第一网络设备的工作稳定性。
举例来说，第一网络设备决策出需要在计算域部署APP LB Service，由第三网络设备自主决策需要部署多少个APP LB Service实例。具体的，第三网络设备可以根据MEC APP注册的服务实例信息，确定出MEC APP中需要APP LB Service的服务实例信息的数量，第三网络设备根据MEC APP中需要LB Service的服务实例的数量决策需要部署的APP LB Service实例的数量；然后，从第一网络设备分配的第一网络资源中决策出每个APP LB Service实例对应的网络资源，并在本地完成对每个APP LB Service实例的部署。
参阅图5，图5为本申请实施例提供的另一种服务实例部署方法的流程示意图，该实施例中与图4所示的实施例相同的内容，此处不再重复描述。本实施例的方法包括以下步骤。本实施例包括以下步骤：
501：第一网络设备获取多接入边缘计算应用程序描述信息。
502：第三网络设备向第一网络设备发送多接入边缘计算应用程序的拓扑信息。
503：第一网络设备根据应用程序描述信息和多接入边缘计算应用程序的拓扑信息，向第二网络设备发送第一请求信息，第一请求消息用于指示第二网络设备在网络域部署与多接入边缘计算应用程序对应的第一多接入边缘计算服务实例。相应的，第二网络设备根据第一请求消息在网络域部署与多接入边缘计算应用程序对应的第一多接入边缘计算服务实例。
504：第二网络设备向第一网络设备发送第一响应消息，第一响应消息包括下行跨域通道参数。
示例性的，第二网络设备在部署完该第一多接入边缘计算服务实例之后，向第一网络设备发送第一响应消息，该第一响应消息用于指示该第二网络设备完成第一多接入边缘计算服务实例的部署，并且还可以在第一响应消息中携带网络域的下行跨域通道参数，该下行跨域通道参数是第二网络设备在网络域部署MSG实例的过程中生成的。
其中，该下行数据通道参数包括网络域的MSG实例的通道ID和通道IP地址。
当然，第二网络设备可以通过一条专用消息给第一网络设备发送下行跨域通道参数，本申请对第二网络设备反馈下行跨域通道参数的方式不进行限定。
在本申请的一个实施方式中，第一网络设备向第三网络设备转发该下行跨域通道参数，比如，第二网络设备可以在该第二请求消息中携带该下行跨域通道参数，则该第二请求消息还用于指示第三网络设备根据该下行跨域通道参数建立网络域和计算域之间的跨域互访通道。当然，第一网络设备也可以通过一条专用的消息向第三网络设备转发该下行跨域通道参数，本申请不对转发下行跨域通道参数进行限定。
505：第一网络设备根据应用程序描述信息和多接入边缘计算应用程序的拓扑信息和向第三网络设备发送第二请求信息，第二请求消息用于指示第三网络设备在计算域部署与多接入边缘计算应用程序对应的第二多接入边缘计算服务实例。相应的，第三网络设备根据第二请求消息在计算域部署与多接入边缘计算应用程序对应的第二多接入边缘计算服务实例。
在本申请的一个实施方式中，该第二请求消息包括下行跨域通道参数。因此，第三网络设备可根据网络域的MSG实例的通道ID和通道IP地址以及本端(计算域)的MSG实例的通道ID和通道IP地址，建立从计算域和网络域之间的跨域互访通道。比如，在从计算域跨域访问网络域的情况下，将计算域的MSG实例的通道ID和通道IP地址作为源通道ID和源通道IP，将网络域MSG实例的通道ID和通道IP作为目的通道ID和目的通道IP，从而建立出计算域和网络域之间的跨域互访通道。
506：第二网络设备生成与第一多接入边缘计算服务实例对应的第一业务规则，并向第一多接入边缘计算服务实例插入第一业务规则。
应理解，本申请所涉及的业务规则可以理解为多接入边缘计算服务实例与MEC APP之间的对应关系。比如，为了提供APP LB Service，部署了两个APP LB Service实例，且这两个负载均衡实例为MEC APP中的十个服务实例提供APP LB Service，那就需要建立每个APP LB Service实例与MEC APP中的服务实例之间的对应关系，这个对应关系就是APP LB Service实例对应的业务规则。后续所涉及的第一业务规则以及第二业务规则，均与此处的业务规则解锁类似，不再叙述。
在本申请的一个实施方式中，该第一请求消息还用于指示第二网络设备生成与该第一多接入边缘计算服务实例对应的第一业务规则，并向第一多接入边缘计算服务实例插入该第一业务规则。当然，第一网络设备也可以通过其他请求消息指示第二网络设备生成与该第一多接入边缘计算服务实例对应的第一业务规则，比如，可以额外发送一条请求消息指示第二网络设备生成与该第一多接入边缘计算服务实例对应的第一业务规则。
相应的，第二网络设备会自主生成第一多接入边缘计算服务实例对应的第一业务规则，并向该第一多接入边缘计算服务实例插入该第一业务规则。示例性的，该第一规则包括但不限于向本地(网络域)分流服务插入的上行分类规则以及向MSG插入的MSG规则。
应说明，第二网络设备只是向第一多接入边缘计算服务实例插入该第一业务规则，并未使能该第一业务规则，也就是说，该第一多接入边缘计算服务实例此时还不能未用户设备提供该第一多接入边缘计算服务。
507：第三网络设备生成与第二多接入边缘计算服务实例对应的第二业务规则，并向第二多接入边缘计算服务实例插入第二业务规则。
示例性的，与上述生成第一业务规则的方式类似，该第二请求消息还用于指示第三网络设备生成与第二多接入边缘计算服务实例对应的第二业务规则，并向该第二多接入边缘计算服务实例插入该第二业务规则，并使能该第二业务规则。
应理解，本申请是以在生成第一业务规则之后，不去直接使能第一业务规则，并且在生成第二业务规则后，直接使能第二业务规则为例说明了对网络域和计算域的业务规则的使能方式。在实际应用中，也可以有其他的使能方式，比如，直接使能第一业务规则，不直接使能第二业务规则；或者，第一业务规则和第二业务规则都不直接使能，等等。本申请不对业务规则的使能方式进行限定。
可以看出，不直接使能第一业务规则，是给MEC APP中的服务实例的使能和生效留一定的缓冲时长，若直接使能第一业务规则和第二业务规则，而MEC APP中的服务实例还未生效，这样用户设备在边缘侧进行本地分流时，MEC APP就会无法提供边缘内容，用户设备在多次尝试之后，可能会转到中心侧去获取数据内容，反而增加了用户的通信时延。而不直接使能第一业务规则，若MEC APP中的服务实例的还未生效，边缘侧的UPF会将用户数据报文直接转发到中心侧的UPF，不会影响用户的通信需求。因此，一般来说，在确定MEC APP中的服务实例的使能和生效之后，再去使能第一业务规则，比如，MEC APP向第三网络设备发送一条所有服务实例都生效的指示信息，第三网络设备将这条指示信息转发给第一网络设备，这个时候第一网络设备可以向第二网络设备发送第四请求消息。
508：第三网络设备向第一网络设备发送第二响应消息，第二响应消息包括上行跨域通道参数。
示例性的，第二响应消息用于指示第三网络设备完成对第二多接入边缘计算服务的实例化，以及向第二多接入边缘计算服务实例插入第二业务规则。
509：第一网络设备向第二网络设备发送第三请求消息，第三请求消息包括上行跨域通道 参数，第三请求消息用于指示第二网络设备根据上行跨域通道参数以及下行跨域通道参数，建立网络域和计算域之间的跨域互访通道。
相应的，第二网络设备根据本端(网络域)的MSG的下行跨域通道参数以及对端(计算域)的MSG的上行跨域通道参数，建立网络域和计算域之间的跨域互访通道。
510：第一网络设备向第二网络设备发送第四请求消息，第四请求消息用于指示第二网络设备通知网络域的用户面功能实体使能第一业务规则，用户面功能实体是第二网络设备根据多接入边缘计算应用程序的拓扑信息确定的。
应理解，如步骤507中所述，第一网络设备单独去使能第一业务规则，可以在MEC APP中的服务实例不能立即生效的情况下，保证用户的通信需求。此外，在MEC APP中的服务实例生效的情况下，可以通过第三网络设备向第一网络设备发送一个生效指示，该指示可触发第一网络设备去使能第一业务规则，从而实现即使MEC APP中的服务实例不能立即生效，也能自动使能实现网络域的业务规则以及计算域的业务规则。
511：第二网络设备向第一网络设备发送第三响应消息，第三响应消息用于指示用户面功能实体完成对第一业务规则的使能。
512：第一网络设备向中心侧的策略控制功能发送第五请求消息，第五请求消息包括多接入边缘计算应用程序的实例标识和数据网络接入标识。
513：中心侧的策略控制功能向中心侧的会话管理功能转发多接入边缘计算应用程序的实例标识和数据网络接入标识，并向中心侧的会话管理功能插入多接入边缘计算应用程序的实例标识和位置标识。
由于第一网络设备将MEC APP的实例标识(即APP ID)和数据网络接入标识(DNAI)插入到PCF，其中，该MEC APP的实例标识(APP ID)指示该MEC APP的用户签约组，则在后续建立上下会话文的过程中，确定用户设备属于该用户签约组的情况下，则向会话管理功能SMF插入该MEC APP的实例标识(APP ID)和数据网络接入标识(DNAI)。
514：中心侧的会话管理功能根据多接入边缘计算应用程序的位置标识选择边缘侧的用户面功能实体，并向边缘侧的用户面功能实体插入多接入边缘计算应用程序的实例标识和数据网络接入标识。
示例性的，SMF则根据数据网络接入标识，即DNAI，选择一个匹配的边缘UPF为用户设备建立会话上下文，并判断若该用户设备符合本地分流条件(比如，用户设备当前处于该DNAI位置)，则指示UPF插入MEC APP的APP ID。
示例性的，后续边缘UPF收到符合本地分流条件的用户设备的上行DNS查询报文，基于MEC APP域名进行L7ULCL规则匹配，决定本地分流，则通过计算域和网络域的跨域通道服务(MSG)，将上行DNS查询报文转发给计算域的MEC服务实例(计算域中的DNS服务实例)，DNS服务处理该DNS查询报文，并根据报文中携带的MEC APP域名查询之前创建好的MEC APP域名记录，返回DNS查询响应报文(携带MECAPP Virtual IP或MEC APP Real IP)。后续边缘UPF再收到符合本地分流条件的用户设备的用户数据报文，基于MECAPP Virtual IP/Port或MEC APP Real IP/Port，进行L3/L4ULCL规则匹配，决定本地分流，则通过计算域和网络域的跨域通道服务(MSG)，将上行用户数据报文转发给计算域中的MEC服务实例(计算域中的APP LB服务实例，MEC APP Virtual IP/Port)或MEC APP中的服务实例(MEC APP Real IP/Port)。如果是发给APP LB服务实例，则APP LB服务实例根据第二业务规则，将该用户数据报分发给MEC APP中相应的服务实例，MEC APP中相应的服务实例根据用户数据报文确定对应的下行边缘内容，并通过计算域的计算域和网络域的跨域通道服务 (MSG)将下行边缘内容发送给用户设备。这样通过上述过程，实现本地分流上下行DNS报文和用户数据报文转发，降低用户获取数据的时延，提高用户体验。
在本申请的一个实施方式中，还可以自动化决策部署MEC APP，如图6所示，从第三网络设备接收多接入边缘计算应用程序的拓扑信息之前，还可以通过以下步骤触发MEC APP的自动化部署：
P11：第一网络设备向网络数据分析功能(Network Data Analytics Function，NWDAF)订阅APP的访问统计数据。
P12：NWDAF向第一网络设备发布APP的访问统计数据。
P13：第一网络设备根据应用程序的访问统计数据以及业务策略，向第三网络设备发送第一提示信息，第一提示信息用于指示第三网络设备通知计算域的网络功能虚拟化基础设施部署用于为APP提供边缘内容的MEC APP。
示例性的，该业务策略是人工编排好的，并通过第一网络设备的北向接口配置给该第一网络设备。其中，该业务策略可以是基于访问次数的策略，比如，在对该APP的访问次数大于第一阈值的情况下，则需要去部署为该APP提供边缘内容的MEC APP，以实现本地分流；或者，该业务策略可以是基于访问时长的策略，比如，在对该APP的总访问时长大于第二阈值的情况下，则需要去部署为该APP提供边缘内容的MEC APP。实际应用中，可依据实际的需求去编排业务策略，本申请不对业务策略的形式进行限定。
相应的，NFVI接收第一提示信息之后，会为该MEC APP分配相应的网络资源，并将分配好的网络资源返回给MEPM，并通知MEPM完成MEC APP的后续部署，其MEC APP的部署与图1示出的部署方式类似，不再叙述。
可以看出，在本申请实施例中，可预先注入业务策略，根据这个业务策略以及获取到的APP的访问统计数据动态触发MEC APP的部署，进一步提高MEC APP部署的智能化以及自动化。
在本申请的另一个实施方式中，也可以自动化决策部署MEC APP，如图7所示，从第三网络设备接收多接入边缘计算应用程序的拓扑信息之前，还可以通过以下步骤触发MEC APP的自动化部署：
P21：应用程序提供方向第一网络设备发送第六请求消息，第六请求消息用于请求部署为APP提供边缘内容的MEC APP。
示例性的，应用程序提供方可以为APP的控制器，即APP Controller。APP Controller可以获取APP的访问统计数据，根据该访问统计数据以及业务策略生成第六请求消息，然后，通过第一网络设备的开发接口向第一网络设备发送第六请求消息。
P22：第一网络设备指示第三网络设备通知计算域的网络功能虚拟化基础设施部署用于为应用程序提供边缘内容的所述多接入边缘计算应用程序。
同样的，第一网络设备可以向第三网络设备发送第一提示信息，通过该第一提示信息指示第三网络设备通知计算域的网络功能虚拟化基础设施部署用于为应用程序提供边缘内容的所述多接入边缘计算应用程序。
示例性的，部署MEC APP的方式与上述的部署方式类似，不再叙述。
P23：第一网络设备向应用程序提供方发送第六响应消息，第六响应消息用于指示完成MEC APP的部署以及业务使能。
同样，在本申请实施例中，可由信息提供方自动触发MEC APP的上线和部署，进一步提高MEC APP部署的智能化以及自动化。
首先说明，本申请的跨域互访通道建立的应用场景，可以是建立两个边缘侧的计算域之间的跨域互访通道，也可以是建立一个边缘侧的计算域和一个中心侧的计算域之间的跨域互访通道，还可以是两个中心侧的计算域之间的跨域互访通道。因此，后续涉及的第一计算域以及第二计算域均可以是边缘侧的计算域，也可以是中心侧的计算域，本申请中主要以第一计算域为边缘侧的计算域，第二计算域为中心侧的计算域为例进行举例说明。相对应的，第四网络设备可以理解为上述的第一网络设备，第五网络设备可以理解为上述的第三网络设备，第六网络设备则为管理第二计算域的网络设备。
为了便于理解本申请的跨域访问通道建立方法，下面结合附图介绍一下本申请的多接入边缘计算服务实例部署方法应用的跨域访问通道建立系统。
如图8所示，本申请的跨域访问通道建立相对于标准的MEC系统，在中心侧额外部署了第四网络设备，在边缘侧的计算域额外部署了第五网络设备，在中心侧的计算域额外部署了第六网络设备。其中，第四网络设备、第五网络设备以及第六网络设备之间协同工作，自动化建立第一计算域和第二计算域之间的跨域互访通道。
示例性的，在接收到跨域访问请求的情况下，第五网络设备配置第一计算域中的第一多接入边缘计算服务实例的第一跨域通道参数以及第一多接入边缘计算服务实例与第一多接入边缘计算应用程序之间的第一路由参数，并将第一跨域通道参数配置给第一多接入边缘计算服务实例，将第一路由参数通过第一计算域的第一多接入边缘计算平台配置给第一多接入边缘计算应用程序；
第五网络设备将第一跨域通道参数以及第二计算域的实例信息发送给第四网络设备；
第四网络设备根据第二计算域的实例信息向第六网络设备转发该第一跨域通道参数，并指示该第六网络设备建立跨域互访通道。因此，第六网络设备配置第二计算域中的第二多接入边缘计算服务实例的第二跨域通道参数以及第二多接入边缘计算服务实例与第二多接入边缘计算应用程序之间的第二路由参数，并将第一跨域通道参数以及第二跨域通道参数配置给第二多接入边缘计算服务实例，将第二路由参数通过第二计算域的第二多接入边缘计算平台配置给第二多接入边缘计算应用程序；最后，将第二跨域通道参数发送给第四网络设备；
第四网络设备将第二跨域通道参数转发给第五网络设备，第五网络设备将第二跨域通道参数配置给第一多接入边缘计算服务实例；
综合上面的参数配置，第一多接入边缘计算应用程序和第一多接入边缘计算服务实例可基于第一路由参数建立通信链路，第一多接入边缘计算服务实例和第二多接入边缘计算服务计算实例，基于第一跨域通道参数和第二跨域通道参数可以建立跨域互访通道，第二多接入边缘计算服务实例和第二多接入边缘计算应用程序可基于第二路由参数建立通信链路。这样，就自动化的建立出了一条跨域互访通信链路：即第一多接入边缘计算应用程序、第一多接入边缘计算服务实例、第二多接入边缘计算服务实例和第二多接入边缘计算服务实例之间的通信链路。后续，第一多接入边缘计算应用程序和第二多接入边缘计算应用程序可以通过这条通信链路进行跨域互访。
可以看出，在本申请实施例中，第四网络设备、第五网络设备以及第六网络设备之间协同工作，自动化打通两个计算域之间的MEC APP的跨域互访，降低了MEC APP的运维成本。
参阅图9，图9为本申请实施例提供的一种跨域互访通道建立方法的流程示意图，该方法包括：
901：第一计算域的第一多接入边缘计算应用程序向第一计算域的第一多接入边缘计算平台发送跨域访问请求，其中，跨域互访请求用于指示第一计算域的第一多接入边缘计算应用 程序请求跨域访问第二计算域，跨域互访请求包括第二计算域的实例信息。
示例性的，第二计算域的实例信息包括但不限于第二计算域的域名、标识以及位置。
902：第一计算域的第一多接入边缘计算平台将跨域访问请求发布给第五网络设备。
示例性的，第五网络设备预先向第一多接入边缘计算平台订阅第一多接入边缘计算应用程序的跨域访问请求，比如，可根据第一多接入边缘计算应用程序的域名或者标识完成订阅；然后，第一多接入边缘计算平台在收到第一多接入边缘计算应用程序的跨域访问请求后，根据之前的订阅情况，将该第一多接入边缘计算应用程序的跨域访问请求发布给第五网络设备。
903：第五网络设备配置第一计算域中用于跨域互访的第一多接入边缘计算服务实例的第一跨域通道参数，并将第一跨域通道参数配置给第一多接入边缘计算服务实例。
示例性的，第一跨域通道参数包括但不限于第一多接入边缘计算服务实例用于跨域访问的通道ID、通道IP以及通道Port。
应理解，第五网络设备在接收到跨域访问请求后，先确定本地(第一计算域)中是否部署有用于跨域互访的第一多接入边缘计算服务实例，若未部署，则先部署该第一多接入边缘计算服务实例；若已经部署，则可以无需部署第一多接入边缘计算服务实例，当然，虽然已经部署有第一多接入边缘计算服务实例，也可以重新部署第一多接入边缘计算服务实例，比如，当前的第一多接入边缘计算服务实例已经为很多MEC APP提供边缘计算服务，需要重新部署一个第一多接入边缘计算服务实例。也就是说，第五网络设备自主决策第一多接入边缘计算服务实例的部署，并为该第一多接入边缘计算服务实例配置第一跨域通道参数，并将该第一跨域通道参数配置给第一多接入边缘计算服务实例。
904：第五网络设备向第四网络设备发送第二计算域的实例信息和第一计算域中用于跨域互访的第一多接入边缘计算服务实例的第一跨域通道参数。
905：第四网络设备根据第二计算域的实例信息，向第六网络设备发送第一计算域中用于跨域互访的第一多接入边缘计算服务实例的第一跨域通道参数。
示例性的，第四网络设备根据该第二计算域的实例信息，确定出与该第二计算域对应的第六网络设备，然后，向该第六网络设备发送第一跨域通道参数，并指示第六网络设备根据第一跨域通道参数建立跨域互访通道。
906：第六网络设备配置第二计算域中用于跨域互访的第二多接入边缘计算服务实例的第二跨域通道参数以及第二多接入边缘计算服务实例的第二路由参数，并将第一跨域通道参数、第二跨域通道参数以及第二路由参数配置给第二多接入边缘计算服务实例。
示例性的，第二跨域通道参数包括但不限于第二多接入边缘计算服务实例用于跨域访问的通道ID、IP以及Port。示例性的，第二路由参数包括第二多接入边缘计算服务实例的下行IP地址。
应理解，第六网络设备也按需决策第二多接入边缘计算服务实例的部署，并未第二多接入边缘计算服务实例配置相应的第二跨域通道参数，并将第一跨域通道参数以及第二跨域通道参数配置给第二多接入边缘计算服务实例。这样，第二多接入边缘计算服务实例可建立跨域访问通道，比如，第二多接入边缘计算服务实例在进行下行跨域访问的过程中，将第二跨域通道参数作为源通道地址，将第一跨域通道参数作为目标通道地址，完成跨域访问。因此，第六网络设备跟第二计算域的第二多接入边缘计算平台之间也完成了订阅关系，用于发现该第二计算域中是否有用于跨域通道的多接入边缘计算服务上线，从而便于决策是否需要进行部署该多接入边缘计算服务。
应理解，在部署第二多接入边缘计算应用程序的过程中，第二多接入边缘计算应用程序 会将第二多接入边缘计算应用程序的上行IP地址注册给第二计算域的第二MEP，第二MEP也会按照先前的订阅情况，将第二多接入边缘计算应用程序的上行IP地址发布给第六网络设备，则第六网络设备可以将第二多接入边缘计算应用程序的上行IP地址配置给第二多接入边缘计算应用程序。这样，第二多接入边缘计算服务实例可以根据本地(第二多接入边缘计算服务实例)的下行IP地址以及对端(第二多接入边缘计算应用程序)的上行IP地址，建立第二多接入边缘计算服务实例与第二多接入边缘计算应用程序之间的通信链路。同样，在下行传输的过程中，将下行IP地址作为源IP地址，将上行IP地址作为目标IP地址，完成第二多接入边缘计算服务实例到第二多接入边缘计算应用程序的下行传输。
907：第六网络设备将第二路由参数发送给第二计算域的第二多接入边缘计算平台。
908：第二计算域的第二多接入边缘计算平台将第二路由参数转发给第二计算域中的第二多接入边缘计算应用程序。
相应的，第二多接入边缘计算应用程序根据本端的路由参数(即上行路由参数)以及第二路由参数(下行路由参数)，建立第二多接入边缘计算服务实例与第二多接入边缘计算应用程序之间的通信链路。
909：第六网络设备向第四网络设备发送第二多接入边缘计算服务实例的第二跨域通道参数。
示例性的，第二响应消息用于指示第六网络设备侧的跨域访问通道完成建立。
910：第四网络设备向第五网络设备转发第二多接入边缘计算服务实例的第二跨域通道参数。
911：第五网络设备将第二多接入边缘计算服务实例的第二跨域通道参数配置给第一多接入边缘计算服务实例。
相应的，第一多接入边缘计算服务实例可根据该第二跨域通道参数以及第一跨域通道参数，建立第一多接入边缘计算服务实例与第二多接入边缘计算服务实例之间的跨域访问通道。
912：第五网络设备配置第一多接入边缘计算服务实例的第一路由参数，并向第一计算域的第一多接入边缘计算平台发送第二响应消息，第二响应消息包括第一路由参数。
示例性的，第二响应消息用于指示第一计算域和第二计算域之间的跨域访问通道完成建立。
913：第一计算域的第一多接入边缘计算平台将第一路由参数转发给第一计算域的第一多接入边缘计算应用程序。
相应的，第一多接入边缘计算应用程序根据第一多接入边缘计算服务实例的第一路由参数(下行路由参数)和本端(第一多接入边缘计算应用程序)的路由参数(上行路由参数)，建立第一多接入边缘计算应用程序和第一多接入边缘计算服务实例之间的通信链路。
应理解，在建立上述的跨域访问通道以及通信链路后，第一多接入边缘计算应用程序可通过第一多接入边缘计算应用程序与第一多接入边缘计算服务实例之间的通信链路将数据报文发送给第一多接入边缘计算服务实例，第一多接入边缘计算服务实例通过跨域互访通道将数据报文发送给第二多接入边缘计算服务实例，第二多接入边缘计算服务实例将多接入边缘计算服务实例发送给第二多接入边缘计算应用程序；最后，第二多接入边缘计算应用程序通相应的服务实例提供边缘内容，并将边缘内容返回给第一多接入边缘计算应用程序，从而实现了从第一多接入边缘计算应用程序到第二多接入边缘计算应用程序的跨域访问。
可以看出，在本申请实施例中，
在本申请的一个实施方式中，在多接入边缘服务实例的部署过程中，第一网络设备除了 决策需要在网络域部署的第一多接入边缘计算服务以及相应的第一网络资源之外，第一网络设备也可以分配好第一多接入边缘计算服务所需的第一多接入边缘计算服务实例，以及与每个第一多接入边缘计算服务对应的网络资源和业务规则，然后，将分配好的第一多接入边缘计算服务所需的第一多接入边缘计算服务实例，以及与每个第一多接入边缘计算服务对应的网络资源和业务规则下发给第二网络设备，第二网络设备只需简单执行多接入边缘计算服务实例的部署过程，无需资源分配，只充当信息的执行者，不具备决策功能；同样，对于第二多接入边缘服务实例的部署，第一网络设备也可以按照对第一多接入边缘服务实例的部署方式进行部署，不再叙述。也就是说，在多接入边缘服务实例的部署过程中，第一用户设备可以充当部分过程的决策者，也可以充当整个过程的决策者，本申请对此不作限定。
在本申请的另一个实施方式中，在跨域互访通道的建立过程中，对于第一计算域中的第一多接入边缘计算服务实例的第一跨域通道参数、以及第一路由参数的生成，可以由第五网络设备执行，也可以由第四网络设备执行；在由第四网络设备执行的情况下，第五设备只需充当命令的执行者，将第四网络设备生成的第一跨域通道参数以及第一路由参数配置给第一跨域通道参数、以及第一路由参数；同样，对于第二计算域中的第二多接入边缘计算服务实例的第二跨域通道参数、以及第二路由参数的生成，可以由第五网络设备执行，也可以由第四网络设备执行，与上述类似，不再叙述。
上述本申请提供用于实现服务实例部署的实施例中，分别从第一网络设备、第二网络设备、第三网络设备、以及第一网络设备、第二网络设备与第三网络设备之间交互的角度对本申请实施例提供的方法进行了介绍。为了实现上述本申请实施例提供的方法中的各功能，第一网络设备、第二网络设备、第三网络设备可以包括硬件结构和/或软件模块，以硬件结构、软件模块、或硬件结构加软件模块的形式来实现上述各功能。上述各功能中的某个功能以硬件结构、软件模块、还是硬件结构加软件模块的方式来执行，取决于技术方案的特定应用和设计约束条件。
图10和图11为本申请的实施例提供一种通信装置的结构示意图。这些通信装置可以实现上述方法实施例中第一网络设备、第二网络设备或者第三网络设备的功能，因此也能实现上述方法实施例所具备的有益效果。在本申请实施例中，该通信装置可以是如图4～图7对应的任一实施例中所示的第一网络设备，也可以是第二网络设备，也可以是第三网络设备，还可以是应用于第一网络设备或第二网络设备或第三网络设备的模块(如芯片)。
如图10所示，通信装置1000包括收发模块1001和处理模块1002。通信装置1000可用于实现上述图4～图7对应的任一实施例中第一网络设备或第二网络设备或第三网络设备的功能。
当通信装置1000用于实现图4～图7任一方法实施例中第一网络设备的功能时：
收发模块1001，用于获取多接入边缘计算应用程序描述信息；
处理模块1002，用于控制收发模块1001根据所述多接入边缘计算应用程序描述信息和所述多接入边缘计算应用程序的拓扑信息，向所述第二网络设备发送第一请求信息，和向所述第三网络设备发送第二请求信息，所述第一请求信息用于指示所述第二网络设备在所述网络域部署与所述多接入边缘计算应用程序对应的第一多接入边缘计算服务实例，所述第二请求信息用于指示所述第三网络设备在所述计算域部署与所述多接入边缘计算应用程序对应的第二多接入边缘计算服务实例。
当通信装置1000用于实现图4～图7任一方法实施例中第二网络设备的功能时：
收发模块1001，用于从所述第一网络设备接收第一请求消息，所述第一请求消息是所述 第一网络设备根据多接入边缘计算应用程序描述信息以及多接入边缘计算应用程序的拓扑信息生成的，所述多接入边缘计算应用程序的拓扑信息是由所述第二网络设备发送给所述第一网络设备的；
处理模块1002，用于根据所述第一请求消息在所述网络域部署与所述多接入边缘计算应用程序对应的第一多接入边缘计算服务实例。
当通信装置1000用于实现图4～图7任一方法实施例中第二网络设备的功能时：
收发模块1001，用于向所述第一网络设备发送多接入边缘计算应用程序的拓扑信息以及用于从所述第一网络设备接收第二请求消息，所述第二请求消息是所述第一网络设备根据多接入边缘计算应用程序描述信息以及多接入边缘计算应用程序的拓扑信息生成的；
处理模块1002，用于根据所述第二请求消息在所述网络域部署与所述多接入边缘计算应用程序对应的第二多接入边缘计算服务实例。
关于上述收发模块1001和处理模块1002更详细的描述，可参考上述方法实施例中的相关描述，在此不再说明。
如图11所示，通信装置1100包括处理器1101和接口电路1102。处理器1101和接口电路1102之间相互耦合。可以理解的是，接口电路1102可以为收发器或输入输出接口。可选的，通信装置1100还可以包括存储器1103，用于存储处理器1101执行的指令或存储处理器1101运行指令所需要的输入数据或存储处理器1101运行指令后产生的数据。
当通信装置1100用于实现上述方法实施例中的方法时，处理器1101用于执行上述处理模块1002的功能，接口电路1102用于执行上述收发模块1001的功能。
当上述通信装置为应用于第一网络设备中的芯片时，该第一网络设备中的芯片实现上述方法实施例中第一网络设备的功能。该第一网络设备中的芯片从第一网络设备中的其它模块(如射频模块或天线)接收信息，该信息是第二网络设备或第三网络设备发送给第一网络设备的；或者，该第一网络设备中的芯片向第一网络设备中的其它模块(如射频模块或天线)发送信息，该信息是第一网络设备发送给第二网络设备或第三网络设备的。
当上述通信装置为应用于第二网络设备中的芯片时，该第二网络设备中的芯片实现上述方法实施例中第二网络设备的功能。该第二网络设备中的芯片从第二网络设备中的其它模块(如射频模块或天线)接收信息，该信息是第一网络设备发送给第二网络设备的；或者，该第二网络设备中的芯片向第二网络设备中的其它模块(如射频模块或天线)发送信息，该信息是第二网络设备发送给第一网络设备的。
当上述通信装置为应用于第三网络设备中的芯片时，该第三网络设备中的芯片实现上述方法实施例中第三网络设备的功能。该第三网络设备中的芯片从第三网络设备中的其它模块(如射频模块或天线)接收信息，该信息是第一网络设备发送给第三网络设备的；或者，该第三网络设备中的芯片向第三网络设备中的其它模块(如射频模块或天线)发送信息，该信息是第三网络设备发送给第一网络设备的。
本申请实施例还提供了一种多接入边缘计算系统，包括上述实现第一网络设备功能的通信装置、实现第二网络设备的通信装置以及上述实现第三网络设备功能的通信装置。
上述本申请提供用于实现跨域互访通道建立的实施例中，分别从第四网络设备、第五网络设备、第六网络设备、以及第四网络设备、第五网络设备、第六网络设备之间交互的角度对本申请实施例提供的方法进行了介绍。为了实现上述本申请实施例提供的方法中的各功能，第四网络设备、第五网络设备、第六网络设备可以包括硬件结构和/或软件模块，以硬件结构、软件模块、或硬件结构加软件模块的形式来实现上述各功能。上述各功能中的某个功能以硬 件结构、软件模块、还是硬件结构加软件模块的方式来执行，取决于技术方案的特定应用和设计约束条件。
图12和图13为本申请的实施例提供另一种通信装置的结构示意图。这些通信装置可以实现上述方法实施例中第四网络设备、第五网络设备、第六网络设备的功能，因此也能实现上述方法实施例所具备的有益效果。在本申请实施例中，该通信装置可以是如图8和图9对应的任一实施例中所示的第四网络设备、也可以是第五网络设备、也可以是第六网络设备，还可以是应用于第四网络设备、第五网络设备或第六网络设备的模块(如芯片)。
如图12所示，通信装置1200包括收发模块1201和处理模块1202。通信装置1200可用于实现上述图8或图9对应的任一实施例中第四网络设备、第五网络设备或第六网络设备的功能。
当通信装置1200用于实现图8或图9任一方法实施例中第四网络设备的功能时：
处理模块1202，用于控制收发模块1201,从所述第五网络设备接收所述第二计算域的实例信息和所述第一计算域中用于跨域互访的第一多接入边缘计算服务实例的第一跨域通道参数；根据所述第二计算域的实例信息，向所述第六网络设备发送所述第一跨域通道参数；从所述第六网络设备接收所述第二计算域中用于跨域互访的第二多接入边缘计算服务实例的第二跨域通道参数；向所述第五网络设备发送所述第二计算域中用于跨域互访的第二多接入边缘计算服务实例的第二跨域通道参数；
其中，所述第一跨域通道参数和所述第二跨域通道参数用于表征所述第一多接入边缘计算服务实例与所述第二多接入边缘计算服务实例之间的跨域互访通道。
当通信装置1200用于实现图8或图9任一方法实施例中第五网络设备的功能时：
处理模块1202，用于控制收发模块1201向所述第四网络设备发送所述第二计算域的实例信息和所述第一计算域中用于跨域互访的第一多接入边缘计算服务实例的第一跨域通道参数；从所述第四网络设备接收所述第二计算域中用于跨域访问的第二多接入边缘计算服务实例的第二跨域通道参数；
其中，所述第一跨域通道参数和所述第二跨域通道参数用于表征所述第一多接入边缘计算服务实例与所述第二多接入边缘计算服务实例之间的跨域互访通道。
当通信装置1200用于实现图8或图9任一方法实施例中第六网络设备的功能时：
处理模块1202，用于控制收发模块1201从所述第四网络设备接收所述第一计算域中用于跨域互访的第一多接入边缘计算服务实例的第一跨域通道参数；向所述第四网络设备发送所述第二计算域中用于跨域互访的第二多接入边缘计算服务实例的第二跨域通道参数；其中，所述第一跨域通道参数和所述第二跨域通道参数用于表征所述第一多接入边缘计算服务实例与所述第二多接入边缘计算服务实例之间的跨域互访通道。
关于上述收发模块1201和处理模块1202更详细的描述，可参考上述方法实施例中的相关描述，在此不再说明。
如图13所示，通信装置1300包括处理器1301和接口电路1302。处理器1301和接口电路1302之间相互耦合。可以理解的是，接口电路1102可以为收发器或输入输出接口。可选的，通信装置1300还可以包括存储器1303，用于存储处理器1301执行的指令或存储处理器1301运行指令所需要的输入数据或存储处理器1301运行指令后产生的数据。
当通信装置1300用于实现上述方法实施例中的方法时，处理器1101用于执行上述处理模块1202的功能，接口电路1302用于执行上述收发模块1201的功能。
当上述通信装置为应用于第四网络设备中的芯片时，该第四网络设备中的芯片实现上述 方法实施例中第四网络设备的功能。该第四网络设备中的芯片从第四网络设备中的其它模块(如射频模块或天线)接收信息，该信息是第五网络设备或第六网络设备发送给第四网络设备的；或者，该第四网络设备中的芯片向第四网络设备中的其它模块(如射频模块或天线)发送信息，该信息是第四网络设备发送给第五网络设备或第六网络的。
当上述通信装置为应用于第五网络设备中的芯片时，该第五网络设备中的芯片实现上述方法实施例中第五网络设备的功能。该第五网络设备中的芯片从第五网络设备中的其它模块(如射频模块或天线)接收信息，该信息是第四网络设备发送给第五网络设备的；或者，该第五网络设备中的芯片向第五网络设备中的其它模块(如射频模块或天线)发送信息，该信息是第五网络设备发送给第四网络设备。
当上述通信装置为应用于第六网络设备中的芯片时，该第三网络设备中的芯片实现上述方法实施例中第六网络设备的功能。该第六网络设备中的芯片从第六网络设备中的其它模块(如射频模块或天线)接收信息，该信息是第四网络设备发送给第六网络设备的；或者，该第六网络设备中的芯片向第六网络设备中的其它模块(如射频模块或天线)发送信息，该信息是第六网络设备发送给第四网络设备的。
本申请实施例还提供了一种跨域互访通道建立系统，包括上述实现第四网络设备功能的通信装置、实现第五网络设备的通信装置以及上述实现第六网络设备功能的通信装置。
可以理解的是，本申请的实施例中的处理器可以是中央处理单元(central processing unit，CPU)，还可以是其它通用处理器、数字信号处理器(digital signal processor，DSP)、专用集成电路(application specific integrated circuit，ASIC)、现场可编程门阵列(field programmable gate array，FPGA)或者其它可编程逻辑器件、晶体管逻辑器件，硬件部件或者其任意组合。通用处理器可以是微处理器，也可以是任何常规的处理器。
本申请的实施例中的方法步骤可以通过硬件的方式来实现，也可以由处理器执行软件指令的方式来实现。软件指令可以由相应的软件模块组成，软件模块可以被存放于随机存取存储器(random access memory，RAM)、闪存、只读存储器(Read-Only Memory，ROM)、可编程只读存储器(programmable ROM，PROM)、可擦除可编程只读存储器(erasable PROM，EPROM)、电可擦除可编程只读存储器(electrically EPROM，EEPROM)、寄存器、硬盘、移动硬盘、CD-ROM或者本领域熟知的任何其它形式的存储介质中。一种示例性的存储介质耦合至处理器，从而使处理器能够从该存储介质读取信息，且可向该存储介质写入信息。当然，存储介质也可以是处理器的组成部分。处理器和存储介质可以位于ASIC中。另外，该ASIC可以位于第一网络设备、第二网络设备、第三网络设备、第四网络设备、第五网络设备或第六网络设备中。当然，处理器和存储介质也可以作为分立组件存在于第一网络设备、第二网络设备、第三网络设备、第四网络设备、第五网络设备或第六网络设备中。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。计算机程序产品包括一个或多个计算机程序或指令。在计算机上加载和执行计算机程序或指令时，全部或部分地执行本申请实施例所述的流程或功能。计算机可以是通用计算机、专用计算机、计算机网络、或者其它可编程装置。计算机程序或指令可以存储在计算机可读存储介质中，或者通过计算机可读存储介质进行传输。计算机可读存储介质可以是计算机能够存取的任何可用介质或者是集成一个或多个可用介质的服务器等数据存储设备。可用介质可以是磁性介质，例如，软盘、硬盘、磁带；也可以是光介质，例如，DVD；还可以是半导体介质，例如，固态硬盘(solid state disk，SSD)。
在本申请的各个实施例中，如果没有特殊说明以及逻辑冲突，不同的实施例之间的术语和/或描述具有一致性、且可以相互引用，不同的实施例中的技术特征根据其内在的逻辑关系可以组合形成新的实施例。
本申请中，“至少一个”是指一个或者多个，“多个”是指两个或两个以上。“和/或”，描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B的情况，其中A，B可以是单数或者复数。在本申请的文字描述中，字符“/”，一般表示前后关联对象是一种“或”的关系；在本申请的公式中，字符“/”，表示前后关联对象是一种“相除”的关系。
可以理解的是，在本申请的实施例中涉及的各种数字编号仅为描述方便进行的区分，并不用来限制本申请的实施例的范围。上述各过程的序号的大小并不意味着执行顺序的先后,各过程的执行顺序应以其功能和内在逻辑确定。

Claims (41)

  1. 一种服务实例部署方法，其特征在于，应用于第一网络设备，所述第一网络设备属于多接入边缘计算系统，所述多接入边缘计算系统还包括第二网络设备和第三网络设备，其中，所述第一网络设备位于所述多接入边缘计算系统的中心侧，所述第二网络设备位于所述多接入边缘计算系统的边缘侧的网络域，所述第三网络设备位于所述多接入边缘计算系统的边缘侧的计算域；所述方法包括：
    获取多接入边缘计算应用程序描述信息；
    从所述第三网络设备接收多接入边缘计算应用程序的拓扑信息；
    根据所述多接入边缘计算应用程序描述信息和所述多接入边缘计算应用程序的拓扑信息，向所述第二网络设备发送第一请求信息，和向所述第三网络设备发送第二请求信息，所述第一请求信息用于指示所述第二网络设备在所述网络域部署与所述多接入边缘计算应用程序对应的第一多接入边缘计算服务实例，所述第二请求信息用于指示所述第三网络设备在所述计算域部署与所述多接入边缘计算应用程序对应的第二多接入边缘计算服务实例。
  2. 根据权利要求1所述的方法，其特征在于，
    所述拓扑信息是所述第三网络设备根据所述多接入边缘计算应用程序的服务注册消息确定的，所述服务注册消息是所述多接入边缘计算应用程序注册给所述网络域的多接入边缘计算平台，并由所述网络域的多接入边缘计算平台发布给所述第三网络设备的。
  3. 根据权利要求1或2所述的方法，其特征在于，
    所述第一请求消息包括第一边缘接入计算服务以及与所述第一边缘接入计算服务对应的第一网络资源；所述第一请求消息用于指示所述第二网络设备根据所述多接入边缘计算应用程序的拓扑信息、所述第一边缘接入计算服务以及所述第一网络资源，部署所述第一多接入边缘计算服务实例，所述第一多接入边缘计算服务实例用于提供所述第一边缘接入计算服务。
  4. 根据权利要求1-3中任一项所述的方法，其特征在于，
    所述第一请求消息还用于指示所述第二网络设备生成与所述第一多接入边缘计算服务实例对应的第一业务规则，并向所述第一多接入边缘计算服务实例插入所述第一业务规则。
  5. 根据权利要求1-4中任一项所述的方法，其特征在于，
    所述第二请求消息包括第二边缘接入计算服务以及与所述第二边缘接入计算服务对应的第二网络资源；所述第二请求消息用于指示所述第三网络设备根据所述多接入边缘计算应用程序的拓扑信息、所述第二边缘接入计算服务以及所述第二网络资源，部署所述第二多接入边缘计算服务实例，所述第二多接入边缘计算服务实例用于提供所述第一边缘接入计算服务。
  6. 根据权利要求1-5中任一项所述的方法，其特征在于，
    所述第二请求消息还用于指示所述第三网络设备生成与所述第二多接入边缘计算服务实例对应的第二业务规则，并向所述第二多接入边缘计算服务实例插入所述第二业务规则。
  7. 根据权利要求1-6中任一项所述的方法，其特征在于，向所述第二网络设备发送第一请求消息之后，所述方法还包括：
    从所述第二网络设备接收第一响应消息，所述第一响应消息包括下行跨域通道参数；
    其中，所述第二请求消息包括所述下行跨域通道参数，所述第二请求消息还用于指示所述第三网络设备根据所述下行跨域通道参数建立所述网络域和所述计算域之间的跨域互访通道。
  8. 根据权利要求1-7中任一项所述的方法，其特征在于，向所述第三网络设备发送第二请求消息之后，所述方法还包括：
    从所述第三网络设备接收第二响应消息，所述第二响应消息包括上行跨域通道参数；
    向所述第二网络设备发送第三请求消息，所述第三请求消息包括所述上行跨域通道参数，所述第三请求消息用于指示所述第二网络设备根据所述上行跨域通道参数以及所述下行跨域通道参数，建立所述网络域和所述计算域之间的跨域互访通道。
  9. 根据权利要求4-8中任一项所述的方法，其特征在于，所述方法还包括：
    向所述第二网络设备发送第四请求消息，所述第四请求消息用于指示所述第二网络设备通知所述网络域的用户面功能实体使能所述第一业务规则，所述用户面功能实体是所述第二网络设备根据所述多接入边缘计算应用程序的拓扑信息确定的。
  10. 根据权利要求9所述的方法，其特征在于，所述方法还包括：
    从所述第二网络设备接收第三响应消息，所述第三响应消息用于指示所述用户面功能实体完成对所述第一业务规则的使能。
  11. 根据权利要求10所述的方法，其特征在于，所述方法还包括：
    向所述中心侧的策略控制功能发送第五请求消息，所述第五请求消息包括所述多接入边缘计算应用程序的实例标识和位置信息，所述第五请求消息用于指示所述策略控制功能将所述多接入边缘计算应用程序的实例标识和位置信息转发给所述中心侧的会话管理功能，以使所述会话管理功能根据所述多接入边缘计算应用程序的位置信息选择所述用户面功能实体，以使所述用户面功能实体建立用户会话上下文，并插入所述多接入边缘计算应用程序的实例标识。
  12. 根据权利要求1-11中任一项所述的方法，其特征在于，从所述第三网络设备接收多接入边缘计算应用程序的拓扑信息之前，所述方法还包括：
    向网络数据分析功能订阅应用程序的访问统计数据；
    根据所述应用程序的访问统计数据以及业务策略，向所述第三网络设备发送第一提示信息，所述第一提示信息用于指示所述第三网络设备通知所述计算域的网络功能虚拟化基础设施部署用于为所述应用程序提供边缘内容的所述多接入边缘计算应用程序。
  13. 根据权利要求1-11中任一项所述的方法，其特征在于，从所述第三网络设备接收多接入边缘计算应用程序的拓扑信息之前，所述方法还包括：
    从应用程序提供方获取第六请求消息，所述第六请求消息用于请求部署为所述应用程序提供边缘内容的所述多接入边缘计算应用程序；
    根据所述第六请求消息，向所述第三网络设备发送第一提示信息，所述第一提示信息用于指示所述第三网络设备通知所述计算域的网络功能虚拟化基础设施部署用于为所述应用程序提供边缘内容的所述多接入边缘计算应用程序。
  14. 一种服务实例部署方法，其特征在于，应用于第二网络设备，所述第二网络设备属于多接入边缘计算系统，所述多接入边缘计算系统还包括第一网络设备和第三网络设备，其中，所述第一网络设备位于所述多接入边缘计算系统的中心侧，所述第二网络设备位于所述多接入边缘计算系统的边缘侧的网络域，所述第三网络设备位于所述多接入边缘计算系统的边缘侧的计算域；所述方法包括：
    从所述第一网络设备接收第一请求消息，所述第一请求消息是所述第一网络设备根据多接入边缘计算应用程序描述信息以及多接入边缘计算应用程序的拓扑信息生成的，所述多接入边缘计算应用程序的拓扑信息是由所述第二网络设备发送给所述第一网络设备的；
    根据所述第一请求消息在所述网络域部署与所述多接入边缘计算应用程序对应的第一多接入边缘计算服务实例。
  15. 根据权利要求14所述的方法，其特征在于，
    所述拓扑信息是所述第三网络设备根据所述多接入边缘计算应用程序的服务注册消息确定的，所述服务注册消息是所述多接入边缘计算应用程序注册给所述网络域的多接入边缘计算平台，并由所述网络域的多接入边缘计算平台发布给所述第三网络设备的。
  16. 根据权利要求14或15所述的方法，其特征在于，所述第一请求消息包括第一边缘接入计算服务以及与所述第一边缘接入计算服务对应的第一网络资源，
    所述根据所述第一请求消息在所述网络域部署与多接入边缘计算应用程序对应的第一多接入边缘计算服务实例，包括：
    根据所述多接入边缘计算应用程序的拓扑信息、所述第一边缘接入计算服务以及所述第一网络资源，部署所述第一多接入边缘计算服务实例，其中，所述第一多接入边缘计算服务实例用于提供所述第一边缘接入计算服务。
  17. 根据权利要求14-16中任一项所述的方法，其特征在于，根据所述第一请求消息在所述网络域部署与多接入边缘计算应用程序对应的第一多接入边缘计算服务实例之后，所述方法还包括：
    生成与所述第一多接入边缘计算服务实例对应的第一业务规则，并向所述第一多接入边缘计算服务实例插入所述第一业务规则。
  18. 根据权利要求14-17中任一项所述的方法，其特征在于，所述方法还包括：
    向所述第一网络设备发送第一响应消息，所述第一响应消息包括下行跨域通道参数，以使所述第三网络设备根据所述下行跨域通道参数建立所述网络域和所述计算域之间的跨域互访通道。
  19. 根据权利要求18所述的方法，其特征在于，向所述第一网络设备发送第一响应消息之后，所述方法还包括：
    从所述第一网络设备接收第三请求消息，所述第三请求消息包括所述上行跨域通道参数；
    根据所述上行跨域通道参数以及所述下行跨域通道参数，建立所述网络域和所述计算域之间的跨域互访通道。
  20. 根据权利要求17-19中任一项所述的方法，其特征在于，所述方法还包括：
    从所述第一网络设备接收第四请求消息；
    根据所述应用程序的拓扑信息，确定网络域的用户面功能实体；
    根据所述网络域的用户面功能实体通知所述网络域的用户面功能实体使能所述第一业务规则。
  21. 一种服务实例部署方法，其特征在于，应用于第三网络设备，所述第三网络设备属于多接入边缘计算系统，所述多接入边缘计算系统还包括第一网络设备和第二网络设备，其中，所述第一网络设备位于所述多接入边缘计算系统的中心侧，所述第二网络设备位于所述多接入边缘计算系统的边缘侧的网络域，所述第三网络设备位于所述多接入边缘计算系统的边缘侧的计算域；所述方法包括：
    向所述第一网络设备发送多接入边缘计算应用程序的拓扑信息；
    从所述第一网络设备接收第二请求消息，所述第二请求消息是所述第一网络设备根据多接入边缘计算应用程序描述信息以及多接入边缘计算应用程序的拓扑信息生成的；
    根据所述第二请求消息在所述网络域部署与所述多接入边缘计算应用程序对应的第二多 接入边缘计算服务实例。
  22. 根据权利要求21所述的方法，其特征在于，所述第二请求消息包括第二边缘接入计算服务以及与所述第二边缘接入计算服务对应的第二网络资源，
    所述第二请求消息包括第二边缘接入计算服务以及与所述第二边缘接入计算服务对应的第二网络资源，包括：
    根据所述多接入边缘计算应用程序的拓扑信息、所述第二边缘接入计算服务以及所述第二网络资源，部署所述第二多接入边缘计算服务实例，其中，所述第二多接入边缘计算服务实例用于提供所述第一边缘接入计算服务。
  23. 根据权利要求21或22所述的方法，其特征在于，所述方法还包括：
    生成与所述第二多接入边缘计算服务实例对应的第二业务规则，并向所述第二多接入边缘计算服务实例插入所述第二业务规则。
  24. 根据权利要求21-23中任一项所述的方法，其特征在于，所述方法还包括：
    向所述第一网络设备发送第二响应消息，所述第二响应消息包括上行跨域通道参数，以使所述第二网络设备根据所述上行跨域通道参数，建立所述网络域和所述计算域之间的跨域互访通道。
  25. 根据权利要求24所述的方法，其特征在于，第二请求消息包括所述下行跨域通道参数，所述方法还包括：
    根据所述下行跨域通道参数建立所述网络域和所述计算域之间的跨域互访通道。
  26. 根据权利要求21-25中任一项所述的方法，其特征在于，向所述第一网络设备发送多接入边缘计算应用程序的拓扑信息之前，所述方法还包括：
    从所述第一网络设备接收第一提示信息；
    根据所述第一提示信息通知所述计算域的网络功能虚拟化基础设施部署用于为所述应用程序提供边缘内容的所述多接入边缘计算应用程序。
  27. 根据权利要求26所述的方法，其特征在于，
    所述第一提示信息是所述第一网络设备根据所述应用程序的访问统计数据以及业务策略生成的或根据从应用程序提供方获取到的第六请求消息生成的，所述第六请求消息用于请求部署为所述应用程序提供边缘内容的所述多接入边缘计算应用程。
  28. 一种跨域互访通道建立方法，其特征在于，应用于第五网络设备，所述第五网络设备属于跨域互访系统，所述跨域互访系统还包括第四网络设备和第六网络设备，其中，所述第四网络设备位于所述跨域互访系统的中心侧，所述第五网络设备位于所述跨域互访系统的第一计算域，所述第六网络设备位于所述跨域互访系统的第二计算域；所述方法包括：
    向所述第四网络设备发送所述第二计算域的实例信息和所述第一计算域中用于跨域互访的第一多接入边缘计算服务实例的第一跨域通道参数；
    从所述第四网络设备接收所述第二计算域中用于跨域访问的第二多接入边缘计算服务实例的第二跨域通道参数；
    其中，所述第一跨域通道参数和所述第二跨域通道参数用于表征所述第一多接入边缘计算服务实例与所述第二多接入边缘计算服务实例之间的跨域互访通道。
  29. 根据权利要求28所述的方法，其特征在于，向所述第四网络设备发送所述第二计算域的实例信息和所述第一计算域中用于跨域互访的第一多接入边缘计算服务实例的第一跨域通道参数之前，所述方法还包括：
    从所述第一计算域的第一多接入边缘计算平台接收跨域互访请求，所述跨域互访请求是 由所述第一计算域的第一多接入边缘计算应用程序发送给所述第一多接入边缘计算平台，并由所述第一多接入边缘计算平台发布给所述第五网络设备的，所述跨域互访请求包括所述第二计算域的实例信息，所述跨域互访请求用于指示第一计算域的第一多接入边缘计算应用程序请求跨域访问所述第二计算域中的第二多接入边缘计算应用程序。
  30. 根据权利要求29所述的方法，其特征在于，从所述第一计算域的第一多接入边缘计算平台接收跨域互访请求之前，所述方法还包括：
    向所述第一多接入边缘计算平台订阅所述第一多接入边缘计算应用程序的跨域互访请求。
  31. 根据权利要求28-30中任一项所述的方法，其特征在于，向所述第四网络设备发送所述第二计算域的实例信息和所述第一计算域中用于跨域互访的第一多接入边缘计算服务实例的第一跨域通道参数之前，所述方法还包括：
    在所述第一计算域部署所述第一多接入边缘计算服务实例以及配置所述第一跨域通道参数。
  32. 根据权利要求31所述的方法，其特征在于，
    在所述第一计算域部署所述第一多接入边缘计算服务实例以及配置所述第一跨域通道参数之后，所述方法还包括：
    配置所述第一多接入边缘计算服务实例与所述第一多接入边缘计算应用程序之间的第一路由参数；
    从所述第四网络设备接收所述第二计算域中用于跨域访问的第二多接入边缘计算服务实例的第二跨域通道参数之后，所述方法还包括：
    向所述第一多接入边缘计算平台发送跨域互访响应，并指示所述第一多接入边缘计算平台将所述跨域互访响应转发给所述第一多接入边缘计算应用程序，所述跨域互访响应包括所述第一路由参数，所述跨域访问响应用于指示所述第一多接入边缘计算应用程序根据所述第一路由参数，建立所述第一多接入边缘计算服务实例与所述第一多接入边缘计算应用程序之间的通信链路。
  33. 一种跨域互访通道建立方法，其特征在于，应用于第六网络设备，所述第六网络设备属于跨域互访系统，所述跨域互访系统还包括第四网络设备和第五网络设备，其中，所述第四网络设备位于所述跨域互访系统的中心侧，所述第五网络设备位于所述跨域互访系统的第一计算域，所述第六网络设备位于所述跨域互访系统的第二计算域；所述方法包括：
    从所述第四网络设备接收所述第一计算域中用于跨域互访的第一多接入边缘计算服务实例的第一跨域通道参数；
    向所述第四网络设备发送所述第二计算域中用于跨域互访的第二多接入边缘计算服务实例的第二跨域通道参数；
    其中，所述第一跨域通道参数和所述第二跨域通道参数用于表征所述第一多接入边缘计算服务实例与所述第二多接入边缘计算服务实例之间的跨域互访通道。
  34. 根据权利要求33所述的方法，其特征在于，向所述第四网络设备发送所述第二计算域中用于跨域互访的第二多接入边缘计算服务实例的第二跨域通道参数之前，所述方法还包括：
    向所述第二计算域中的第二多接入边缘计算平台订阅用于跨域互访的第二多接入边缘计算服务实例的上线。
  35. 根据权利要求33或34所述的方法，其特征在于，向所述第四网络设备发送所述第二计算域中用于跨域互访的第二多接入边缘计算服务实例的第二跨域通道参数之前，所述方法 还包括：
    在所述第二计算域部署所述第二多接入边缘计算服务实例以及配置所述第二跨域通道参数。
  36. 根据权利要求35所述的方法，其特征在于，在所述第二计算域部署所述第二多接入边缘计算服务实例以及配置所述第二跨域通道参数之后，所述方法还包括：
    配置所述第二多接入边缘计算服务实例与所述第二多接入边缘计算应用程序之间的第二路由参数，并将所述第二路由参数配置给所述第二多接入边缘计算服务实例以及所述第二计算域的第二多接入边缘计算平台，所述第二多接入边缘计算平台用于将所述第二路由参数转发给所述第二多接入边缘计算应用程序，所述第二路由参数用于所述第二多接入边缘计算服务实例以及所述第二多接入边缘计算应用程序建立通信链路。
  37. 一种跨域互访通道建立方法，其特征在于，应用于第四网络设备，所述第四网络设备属于跨域互访系统，所述跨域互访系统还包括第五网络设备和第六网络设备，其中，所述第四网络设备位于所述跨域互访系统的中心侧，所述第五网络设备位于所述跨域互访系统的第一计算域，所述第六网络设备位于所述跨域互访系统的第二计算域；所述方法包括：
    从所述第五网络设备接收所述第二计算域的实例信息和所述第一计算域中用于跨域互访的第一多接入边缘计算服务实例的第一跨域通道参数；
    根据所述第二计算域的实例信息，向所述第六网络设备发送所述第一跨域通道参数；
    从所述第六网络设备接收所述第二计算域中用于跨域互访的第二多接入边缘计算服务实例的第二跨域通道参数；
    向所述第五网络设备发送所述第二计算域中用于跨域互访的第二多接入边缘计算服务实例的第二跨域通道参数；
    其中，所述第一跨域通道参数和所述第二跨域通道参数用于表征所述第一多接入边缘计算服务实例与所述第二多接入边缘计算服务实例之间的跨域互访通道。
  38. 一种通信装置，其特征在于，包括用于执行如权利要求1-13或权利要求14-20或权利要求21-27或权利要求28-32或权利要求33-36或权利要求37中任一项所述方法的模块。
  39. 一种通信装置，其特征在于，包括处理器和通信接口，所述通信接口用于接收来自所述通信装置之外的其它通信装置的信号并传输至所述处理器或将来自所述处理器的信号发送给所述通信装置之外的其它通信装置，所述处理器通过逻辑电路或执行代码指令用于实现如权利要求1-13或权利要求14-20或权利要求21-27或权利要求28-32或权利要求33-36或权利要求37中任一项所述的方法。
  40. 一种计算机可读存储介质，其特征在于，所述计算机可读存储介质存储有计算机程序，当所述计算机程序被运行时，实现如权利要求1-13或权利要求14-20或权利要求21-27或权利要求28-32或权利要求33-36或权利要求37中任一项所述的方法。
  41. 一种计算机程序产品，其特征在于，所述计算机程序产品包括：计算机程序代码，当计算机程序代码被运行时，实现如权利要求1-13或权利要求14-20或权利要求21-27或权利要求28-32或权利要求33-36或权利要求37中任一项所述的方法。
PCT/CN2021/131280 2020-11-17 2021-11-17 服务实例部署方法、跨域互访通道建立方法及相关装置 WO2022105807A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202011289415.7 2020-11-17
CN202011289415.7A CN114513852A (zh) 2020-11-17 2020-11-17 服务实例部署方法、跨域互访通道建立方法及相关装置

Publications (1)

Publication Number Publication Date
WO2022105807A1 true WO2022105807A1 (zh) 2022-05-27

Family

ID=81547276

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/131280 WO2022105807A1 (zh) 2020-11-17 2021-11-17 服务实例部署方法、跨域互访通道建立方法及相关装置

Country Status (2)

Country Link
CN (1) CN114513852A (zh)
WO (1) WO2022105807A1 (zh)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN117560280A (zh) * 2022-08-05 2024-02-13 华为技术有限公司 一种通信方法和装置
CN115460091A (zh) * 2022-09-09 2022-12-09 中国电信股份有限公司 边缘业务的处理方法及装置、存储介质、电子设备

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109347739A (zh) * 2018-11-14 2019-02-15 电子科技大学 为多接入边缘计算提供资源配置和接入点选择策略的方法
CN111200797A (zh) * 2018-11-18 2020-05-26 华为技术有限公司 车联网消息通知方法和装置
CN111565404A (zh) * 2020-04-15 2020-08-21 中国联合网络通信集团有限公司 一种数据分流方法和装置

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109347739A (zh) * 2018-11-14 2019-02-15 电子科技大学 为多接入边缘计算提供资源配置和接入点选择策略的方法
CN111200797A (zh) * 2018-11-18 2020-05-26 华为技术有限公司 车联网消息通知方法和装置
CN111565404A (zh) * 2020-04-15 2020-08-21 中国联合网络通信集团有限公司 一种数据分流方法和装置

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
HUAWEI ET AL.: "Discussion on Supporting MEC with CAPIF", 3GPP TSG-SA WG6 MEETING #25 S6-181078, 19 July 2018 (2018-07-19), XP051545031 *

Also Published As

Publication number Publication date
CN114513852A (zh) 2022-05-17

Similar Documents

Publication Publication Date Title
US20200228405A1 (en) Network slice management method and apparatus
US10448320B2 (en) System and method for virtualized functions in control and data planes
US11134410B2 (en) Quality of service (QoS) control in mobile edge computing (MEC)
US10129108B2 (en) System and methods for network management and orchestration for network slicing
WO2023000935A1 (zh) 一种数据处理方法、网元设备以及可读存储介质
CN113891430A (zh) 一种通信的方法、装置及系统
US20210392561A1 (en) Path, path information processing method and device, storage medium and electronic device
US20220174585A1 (en) Information Obtaining Method And Apparatus
US20220217611A1 (en) Service Configuration Method, Communication Apparatus, and Communication System
WO2022152238A1 (zh) 一种通信方法及通信装置
WO2022105807A1 (zh) 服务实例部署方法、跨域互访通道建立方法及相关装置
EP3788766A1 (en) Direct user equipment to user equipment without data network access identifier
JP2019504564A (ja) ローミング接続を確立するための方法
WO2022105897A1 (zh) 业务路径建立方法、通信装置及存储介质
US11558491B2 (en) Information-centric networking over 5G or later networks
WO2022067829A1 (zh) 动态触发边缘应用服务器实例化的方法及装置
US20230156828A1 (en) Session establishment method and apparatus, system, and computer storage medium
KR102436981B1 (ko) 무선 액세스 네트워크 정보 처리 방법 및 장치, 네트워크 요소 및 저장 매체
CN114080054A (zh) 一种pdu会话建立方法、终端设备和芯片系统
CN114365518A (zh) 一种通过服务应用影响核心网络中数据业务路由的方法
US20210227608A1 (en) Method And Apparatus For Sending Multicast Data
EP4132100A1 (en) Method and device for providing local data network information to terminal in wireless communication system
CN112533177A (zh) 一种提供、发现移动边缘计算的方法及设备、装置、介质
WO2021115429A1 (zh) 一种通信方法及装置
KR20210144491A (ko) 무선 통신 시스템에서 단말의 데이터 세션 앵커의 재배치를 위한 방법 및 장치

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 21893954

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 21893954

Country of ref document: EP

Kind code of ref document: A1