WO2019101056A1 - 一种配置方法及装置 - Google Patents

一种配置方法及装置 Download PDF

Info

Publication number
WO2019101056A1
WO2019101056A1 PCT/CN2018/116348 CN2018116348W WO2019101056A1 WO 2019101056 A1 WO2019101056 A1 WO 2019101056A1 CN 2018116348 W CN2018116348 W CN 2018116348W WO 2019101056 A1 WO2019101056 A1 WO 2019101056A1
Authority
WO
WIPO (PCT)
Prior art keywords
service flow
application
flow rule
nfp
platform
Prior art date
Application number
PCT/CN2018/116348
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 华为技术有限公司
Priority to EP18880585.7A priority Critical patent/EP3703321B1/en
Publication of WO2019101056A1 publication Critical patent/WO2019101056A1/zh
Priority to US16/877,322 priority patent/US11570277B2/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/64—Routing or path finding of packets in data switching networks using an overlay routing layer
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/302—Route determination based on requested QoS
    • H04L45/306—Route determination based on the nature of the carried application
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
    • H04L67/63—Routing a service request depending on the request content or context
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • H04L41/0813—Configuration setting characterised by the conditions triggering a change of settings
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/38—Flow based routing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/50—Address allocation
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/14—Session management
    • H04L67/141—Setup of application sessions
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/2866—Architectures; Arrangements
    • H04L67/30—Profiles

Definitions

  • the present application relates to the field of information technology, and in particular, to a configuration method and apparatus.
  • the mobile edge (ME) computing is to provide the information technology (IT) services and cloud computing functions required by telecom users by using the wireless access network to form a high-performance, low-latency and high-bandwidth telecommunications.
  • the service environment accelerates the rapid download of various content, services and applications in the network, enabling consumers to enjoy an uninterrupted high-quality network experience.
  • the ME application packet contains a template file called an application descriptor (AppD).
  • the AppD describes the application's requirements for virtual computing, storage, network resources, dependent services, features, DNS rules, and service flow rules. And other information.
  • the ME management system can perform lifecycle management on the ME application through the information in the AppD, such as configuring resources for the ME application to create an application instance (also referred to as application instantiation), configuring service flow rules, and deleting application instances.
  • the service flow rule configuration of the ME application occurs after the ME application resource configuration.
  • the ME platform applies the service flow rule to forward the service flow or the packet of the ME application instance, the ME platform manager needs to be in accordance with the service flow rule.
  • the infrastructure layer creates a forwarding route for the traffic flow or packet, and then forwards the traffic flow or packet to the destination network node or destination application hop by hop.
  • the present application provides a configuration method and apparatus for solving the problem that the forwarding delay of a service flow or a packet is long in the prior art.
  • the application provides a configuration method, including: a mobile edge ME platform manager determining a network forwarding path NFP of an instantiated first ME application to a first destination application, where the NFP is used to indicate that the first The forwarding path of the service flow or packet sent by the ME application to the first destination application.
  • the ME platform manager sends an NFP creation request to the virtualized infrastructure manager VIM, requesting the VIM to create the NFP determined by the ME platform manager, and the NFP created by the VIM is used to forward the service flow or the packet.
  • the transmission path resource formed by assembling network resources is a special network resource.
  • the ME platform manager associates the NFP created by the VIM with a first service flow rule configured by the first ME application. For example, the ME platform manager may associate the identifier of the created NFP with the identification information of the first service flow rule.
  • the ME platform manager requests the VIM to assemble the network resource for transmitting the service flow or the packet of the first ME application to form an NFP, and associate the created NFP with the service flow rule of the first ME application, where After the association relationship is configured to the ME platform, the ME platform can directly select its associated NFP to transmit the service flow or packet of the first ME application according to the used service flow rule, and the actual technology needs to be forwarded by the ME platform.
  • the service flow or the packet of the first ME application is determined according to the service flow rule
  • the address of the forwarded next hop network function node is determined hop by hop according to the service flow rule, and the service flow of the first ME application or the additional forwarding path of the packet is established when forwarding. Handling delay overhead to ensure that MEs use low-latency or real-time transmission requirements.
  • the ME platform manager further sends a configuration request to the ME platform that manages the first ME application, requesting the ME platform to configure an instance of the first ME application, where
  • the configuration may be as follows: associate the created NFP with the first service flow rule configured by the first ME application.
  • the established network forwarding path NFP may be directly used to implement the next hop of the packet, thereby reducing the first ME application. The forwarding delay of the traffic flow or packet.
  • the ME platform manager determines that the first ME is applied to the NFP of the first destination application, and the ME platform manager may be configured according to the first service flow.
  • the rule determines a host address of the first destination application; the ME platform manager determines the NFP according to a host address of the first ME application and a host address of the first destination application.
  • the ME platform manager may determine the host address of the first destination application of the first ME application according to the service flow rule, and determine the network forwarding path NFP based on the host address of the first ME application and the host address of the first destination application.
  • the service flow or the packet sent by the first ME application is transmitted to the first destination application via the network function node indicated by the NFP, wherein the algorithm for determining the NFP can refer to various technical means in the prior art, and the application is implemented. The case will not be detailed.
  • the NFP includes a service flow of the first ME application or a connection point of a network function node that is grouped to the first destination application, and before and after forwarding the packet The sequence of join points formed by the jump sequence.
  • the NFP includes a connection point in the sequence of connection points that is a connection point of an available network function node in the ME platform manager management domain.
  • the ME platform manager may generate an NFP according to the service flow of the first ME application or the connection point of the network function node that is grouped to the first destination application, and then request the VIM to generate the NFP, so that the ME platform can use the NFP.
  • the service flow or grouping of the first ME application to the first destination application is forwarded according to the first service flow rule, and the implementation manner is simple and efficient.
  • the ME platform manager determines that a host address of the instantiated second ME application is the same as a host address of the first ME application, and that the second ME application configuration is The host address of the second destination application in the second service flow rule is the same as the host address of the first destination application.
  • the ME platform manager associates the second service flow rule with the created NFP.
  • the created NFP can be associated with the service flow rules of multiple ME applications, which can not only improve the utilization of the NFP, but also reduce the overhead of the ME platform manager to determine the resources of the NFP and the VIM to create the NFP.
  • the ME platform manager checks whether there is an ME application instance of the NFP that is associated with the creation; the ME application instance that is associated with the NFP, and the service flow rule of the ME application instance is associated with the NFP.
  • the ME platform may forward the service flow or packet indicated by the service flow rule by using the network resource provided by the NFP. If there is no ME application instance associated with the NFP, the VIM is instructed to release the NFP. Optionally, if there is no application instance associated with the NFP, the ME platform manager further instructs the ME platform to delete the locally stored NFP. Optionally, if there is no application instance associated with the NFP, the ME platform manager also deletes the locally stored NFP. In the foregoing technical solution, the ME platform manager may instruct the VIM to release the NFP, and reduce the cost of maintaining the NFP by the VIM.
  • the ME platform manager may further obtain a preset first service flow rule from an application descriptor of the first ME application, where the preset first service flow rule includes a filtering condition and a forwarding interface description, where the forwarding interface description includes a forwarding interface indication; the ME platform manager determines that the VIM is an address resource allocated by the forwarding interface to the indicated interface; and the ME platform manager according to the The address resource and the preset first service flow rule determine a first service flow rule to be configured, and the forwarding interface indication in the first service flow rule to be configured is associated with the address resource.
  • the application descriptor of the ME application may not set the address of the forwarding interface, but add the indication information of the forwarding interface (such as AppExtCp), and wait until the VIM allocates the address resource to the forwarding interface, and then allocates the address.
  • the resource is associated with the forwarding interface indication/forwarding interface description/service flow rule, for example, the associated MAC and/or IP address is associated with the service flow rule according to the specified interface type information, and the filtering rule for forwarding the service flow rule is implemented.
  • the setting of the address of the indicated service flow or the interface of the packet can be applied not only to the scenario in which the address resource of the ME application interface is dynamically allocated, but also to avoid the low utilization of the address resource caused by configuring the fixed address for the ME application.
  • the ME platform manager after the ME platform manager determines the first service flow rule to be configured, the ME platform manager sends a configuration request to the ME platform, where the configuration request includes The first service flow rule to be configured is used to request the ME platform to configure the first service flow rule to be configured, and forward the packet indicated by the filter condition to the first traffic flow rule according to the configured first service flow rule.
  • An interface of the first ME application that uses the address resource.
  • the ME platform manager determines an updated first service flow rule, the updated first service The forwarding interface indication in the flow rule is associated with the changed address resource; the ME platform manager sends a reconfiguration request to the ME platform, where the reconfiguration request includes the updated first service flow rule, And the first service flow rule for requesting the ME platform to configure the update, and forwarding the packet indicated by the filtering condition to the used updated address of the first ME application according to the configured updated first service flow rule The interface to the resource.
  • the ME platform manager updates the service flow rule, reconfigures the ME platform by using the updated service flow rule, and implements the service flow or packet forwarding indicated by the filtering condition.
  • the interface to the ME application instance the address of the interface can be dynamically changed.
  • the application provides a configuration method, where the ME platform manager obtains a preset service flow rule from an application descriptor of an ME application, where the preset service flow rule includes a filter condition and a forwarding interface description.
  • the forwarding interface description includes a forwarding interface indication, and the forwarding interface indication may be an application external connection point (AppExtCp) field in the application descriptor, and is used to indicate a service flow or a packet defined by the filtering condition in the forwarding service flow rule.
  • AppExtCp application external connection point
  • the application descriptor of the ME application may not set the address of the forwarding interface, but add the indication information of the forwarding interface (such as AppExtCp), and wait until the VIM allocates the address resource to the forwarding interface, and then allocates the address.
  • the resource is associated with the forwarding interface indication/forwarding interface description/service flow rule, for example, the associated MAC and/or IP address is associated with the service flow rule according to the specified interface type information, and the filtering rule for forwarding the service flow rule is implemented.
  • the setting of the address of the indicated service flow or the interface of the packet, the foregoing method can be applied not only to the scenario in which the address resource of the ME application interface is dynamically allocated, but also to avoid the low utilization of the address resource caused by configuring the fixed address for the ME application.
  • the ME platform manager further sends a configuration request to an ME platform that manages the ME application, where the configuration request includes the service flow rule to be configured, and is used to request the ME
  • the platform configures the service flow rule to be configured, and forwards the packet indicated by the filter condition to an interface of the ME application that uses the address resource according to the configured service flow rule.
  • the ME platform configures the ME application instance, and configures an interface of the ME application instance that uses the address resource to receive the packet indicated by the filtering condition.
  • the service flow rule to be configured is configured to the ME application instance, so that the ME platform forwards the service flow or the packet indicated by the filtering condition to the interface that is the ME application instance, and the address of the interface can be dynamically allocated.
  • the ME platform manager determines an updated service flow rule, where the updated service flow rule The forwarding interface indication is associated with the changed address resource; the ME platform manager sends a reconfiguration request to the ME platform, the reconfiguration request including the updated service flow rule, for requesting the ME The platform configures the updated service flow rule, and forwards the packet indicated by the filter condition to an interface of the ME application that uses the changed address resource according to the configured updated service flow rule.
  • the ME platform manager updates the service flow rule, reconfigures the ME platform by using the updated service flow rule, and implements the service flow or packet forwarding indicated by the filtering condition.
  • the interface to the ME application instance the address of the interface can be dynamically changed.
  • the application provides a method for creating a resource, including: receiving, by a VIM, an NFP creation request sent by an ME platform manager, where the NFP creation request includes an NFP generated by the ME platform manager; NFP and return the NFP creation result to the ME platform manager.
  • the VIM may allocate the transmission path resource formed by the network resource used for forwarding the service flow or the packet, so that the ME platform can directly select the network resource of the associated NFP according to the used service flow rule. Transmitting the service flow or packet of the first ME application, reducing the transmission time of the traffic flow or packet.
  • the application provides a configuration method, including: receiving, by the ME platform, a configuration request sent by an ME platform manager, where the configuration request includes an identifier of the created NFP and an identifier of a service flow rule of the ME application; Configuring an instance of the ME application to associate an identifier of the NFP with an identifier of the service flow rule.
  • the ME platform can associate the service flow rule of the ME application with the NFP resource, so that the ME platform can directly select the network resource of the associated NFP to transmit the service flow of the first ME application according to the used service flow rule. Or grouping, reducing the time-consuming transmission of traffic or packets.
  • the present application provides a configuration apparatus for performing the method of any of the first, second or fourth aspects described above, or any possible implementation of any of the first, second or fourth aspects .
  • the configuration means comprises means for performing the method of any of the first, second or fourth aspects described above, or any of the possible implementations of any of the first, second or fourth aspects.
  • the present application provides an apparatus for creating a resource, the apparatus for performing the method of the above third aspect.
  • the apparatus comprises means for performing the method of the third aspect described above.
  • the embodiment of the present application provides a communication device, where the communication device includes a processor, a memory, and a communication interface, where the communication interface is used to communicate with other communication devices, and the memory is used to store computer instructions;
  • the processor is operative to execute the computer instructions to perform the method of any one of the first to fourth aspects or any of the possible implementations of any of the first to fourth aspects when the computer instructions are executed.
  • the present application provides a computer readable storage medium having stored therein computer instructions that, when executed on a computer, cause the computer to perform any of the above first to fourth aspects Or the method of any of the possible implementations of any of the first to fourth aspects.
  • the present application provides a computer program product, when the computer program product is run on a computer, causing the computer to perform any of the first to fourth aspects or any of the first to fourth aspects The method in any possible implementation.
  • FIG. 1 is a schematic diagram of an architecture of a mobile edge calculation in at least one embodiment of the present application
  • FIG. 6 and FIG. 9 are schematic flowcharts of instantiation of an ME application in at least one embodiment of the present application.
  • 10-12 are schematic views of a configuration apparatus in at least one embodiment of the present application.
  • the present application provides a configuration method and apparatus for solving the problem that the forwarding delay of a service flow or a packet is long in the prior art.
  • the method and the device are based on the same inventive concept. Since the principles of the method and the device for solving the problem are similar, the implementation of the device and the method can be referred to each other, and the repeated description is not repeated.
  • the plurality referred to in the present application means two or more.
  • the terms "first”, “second” and the like are used for the purpose of distinguishing the description, and are not to be construed as indicating or implying a relative importance, and are not to be construed as indicating or implying the order.
  • 5G NR 5th Generation New Radio Access Technology
  • LTE long term evolution
  • FDD LTE frequency division duplex
  • TDD LTE time division duplex
  • CDMA code division multiple access
  • WCDMA wideband code division multiple Access
  • GSM global system of mobile communication
  • GPRS general packet radio services
  • UMTS universal mobile telecommunication systems
  • WiMAX global interconnected microwave access
  • FIG. 1 illustrates a reference architecture for mobile edge computing (MEC), which includes an ME host 10 and an ME management system 20.
  • MEC mobile edge computing
  • the ME host 10 includes an ME platform 11 and a virtualised infrastructure (VI) 12 that provides virtualized computing, storage, and network resources for ME applications, and the ME applications are deployed in the form of virtual machines or containers.
  • the virtualization infrastructure 12 includes a data plane that performs service flow rules from the ME platform 11 and completes the routing of messages.
  • the ME platform 10 also has an ME platform 11 deployed therein.
  • the ME platform 11 includes some public services, such as a terminal location service, a wireless network information service, a domain name system (DNS) server, or a DNS proxy service. Use these public services.
  • DNS domain name system
  • the service registration function of the ME platform 11 provides the ME application with the ability to discover and use ME services.
  • the service flow rule service receives the service flow rule from the ME management system 20 and delivers it to the data plane.
  • the DNS service receives mapping rules for domain names and IP addresses from the ME management system 20.
  • the ME management system 20 includes a mobile edge orchestrator (MEO) 21, a mobile edge platform manager (MEPM) 22, a virtualised infrastructure manager (VIM) 23, and the like.
  • the ME orchestrator 21 maintains an overall view of all ME hosts, available resources, and available ME services in the ME system, triggering instantiation and termination of the application.
  • the ME platform manager 22 is used to manage the ME platform, manage the life cycle of the ME application, manage the service flow rules of the application, and the DNS rules.
  • the virtualization infrastructure manager 23 manages the virtualized resources required by the ME application.
  • FIG. 2 shows a configuration method of an embodiment of the present application, including:
  • Step 301 The ME platform manager determines a network forwarding path (NFP) of the instantiated first ME application to the first destination application.
  • the NFP is used to indicate a forwarding path of a traffic flow or a packet sent by the first ME application to the first destination application.
  • Step 301 is performed after the first ME application instantiation (that is, the VIM allocates the virtual resource to the first ME application).
  • the step 301 is to instantiate the first ME application and the ME platform configures the service flow rule to the first ME.
  • the instance of the application is executed later.
  • Step 302 The ME platform manager sends an NFP creation request to the virtualization infrastructure manager VIM, where the NFP creation request is used to request the VIM to create the NFP.
  • Step 303 The VIM receives an NFP creation request, and creates an NFP according to the NFP request.
  • the so-called NFP can refer to a transmission path resource formed by assembling network resources used for forwarding a service flow or a packet, and is a special network resource.
  • Step 304 The VIM returns an NFP creation result to the ME platform manager, where the NFP creation result may be an identifier of the created NFP.
  • Step 305 The ME platform manager associates the NFP created by the VIM with the first service flow rule configured by the first ME application.
  • the association between the NFP and the first service flow rule may be implemented in multiple manners.
  • the ME platform manager may associate the identifier of the created NFP with the identifier information of the first service flow rule.
  • the ME platform manager may Add the identifier of the created NFP in the first service flow rule.
  • the ME platform manager requests the VIM to assemble the network resource for transmitting the service flow or the packet of the first ME application to form an NFP, and associate the created NFP with the service flow rule of the first ME application, where After the association relationship is configured to the ME platform, the ME platform can directly select its associated NFP to transmit the service flow or packet of the first ME application according to the used service flow rule, and the actual technology needs to be forwarded by the ME platform.
  • the service flow or the packet of the first ME application is determined according to the service flow rule
  • the address of the forwarded next hop network function node is determined hop by hop according to the service flow rule, and the service flow of the first ME application or the additional forwarding path of the packet is established when forwarding. Handling delay overhead to ensure that MEs use low-latency or real-time transmission requirements.
  • the first ME application instance may be configured with multiple service flow rules, and the ME platform manager may determine different NFPs according to different service flow rules of the first ME application, and the ME platform manager may separately set multiple service flow rules. Associated with their respective NFPs.
  • step 305 the method further includes:
  • Step 306 The ME platform manager sends a configuration request to the ME platform that manages the first ME application, where the configuration request is used to request the ME platform to configure the instance of the first ME application, and the configuration may be: creating the NFP and the first The first service flow rule association of an ME application configuration.
  • the established network forwarding path NFP may be directly used to implement the next hop of the packet, thereby reducing the first ME application.
  • the forwarding delay of the traffic flow or packet may be directly used to implement the next hop of the packet.
  • step 301 may include the following steps:
  • Step 3011 The ME platform manager determines, according to the first service flow rule configured by the first ME application, a host address of the first destination application.
  • the ME platform manager may read the application descriptor of the first ME application from the ME orchestration, and obtain the first service flow rule from the application descriptor. In the application descriptor, in the application descriptor.
  • the business flow rules can also be referred to as pre-set business flow rules.
  • the pre-set first service flow rule includes a host address of the first destination application of the first ME application.
  • the ME platform manager stores the first service flow rule configured by the first ME application, and the ME platform can read the first purpose of the first ME application from the configured first service flow rule. The host address of the application.
  • Step 3012 The ME platform manager determines the NFP according to the host address of the first ME application and the host address of the first destination application.
  • the host address of the first ME application and the type of the host address of the first destination application may be an IP address, a MAC address, or an identifier of a tunnel connection.
  • the ME platform manager may determine the host address of the first destination application of the first ME application according to the service flow rule, and determine the network forwarding path NFP based on the host address of the first ME application and the host address of the first destination application.
  • the service flow or the packet sent by the first ME application is transmitted to the first destination application via the network function node indicated by the NFP, wherein the algorithm for determining the NFP can refer to various technical means in the prior art, and the application is implemented. The case will not be detailed.
  • the network forwarding path NFP defines a forwarding path of the service flow or the packet applied by the first ME to the first destination application.
  • the NFP is actually located where the first ME application is located.
  • the NFP may include a connection point sequence, and the so-called connection point may be an external connection point (CP) of a virtual network function (VNF) or an external connection of a physical network function (PNF).
  • the point CP can also be a service access point (SAP) for network services. It should be understood that the types of connection points in one NFP may be different.
  • an NFP may include CP1 of VNF1, CP2 of PNF2, and SAP3 of Network Service 3.
  • the NFP includes a connection point in the sequence of connection points that is a connection point of an available network function node in the ME platform manager management domain.
  • connection point sequence included in the NFP may have multiple implementation manners.
  • the connection point sequence may be a service flow of the first ME application or a connection point of the network function node that is grouped to the first destination application, and the packet is passed according to the forwarding packet.
  • the sequence formed by the hopping sequence may be a service flow of the first ME application or a connection point of the network function node that is grouped to the first destination application, and the packet is passed according to the forwarding packet.
  • the NFP may further include a connection point of a host where the first ME application is located and/or a connection point where the first destination application is located.
  • the ME platform manager may generate an NFP according to the service flow of the first ME application or the connection point of the network function node that is grouped to the first destination application, and then request the VIM to generate the NFP, so that the ME platform can use the NFP.
  • the service flow or grouping of the first ME application to the first destination application is forwarded according to the first service flow rule, and the implementation manner is simple and efficient.
  • the configuration method of the embodiment of the present application further includes:
  • Step 307 The ME platform manager determines that the host address of the instantiated second ME application is the same as the host address of the first ME application, and the host address of the second destination application in the second service flow rule configured by the second ME application. Same as the host address of the first destination application.
  • Step 308 The ME platform manager associates the second service flow rule with the NFP that is associated with the first service flow rule of the first ME application.
  • the host address of the second destination application and the first destination application are The host address is the same, indicating that the service flow or packet applied by the second ME to the second destination application may be forwarded via the path defined by the NFP for the first ME application, and the ME platform manager may directly use the NFP and the second The second service flow rule of the ME application is associated, so that the data flow or packet applied by the second ME to the second destination application is forwarded according to the path defined by the NFP.
  • the created NFP can be associated with the service flow rules of multiple ME applications, which can not only improve the utilization of the NFP, but also reduce the overhead of the ME platform manager to determine the resources of the NFP and the VIM to create the NFP.
  • the ME platform manager may further determine whether the NFP is associated with the service flow rule of the first ME application, and if the NFP is associated with the service flow rule of the first ME application, and the ME platform manager Determining that the host address of the instantiated second ME application is the same as the host address of the first ME application, and the host address of the second destination application in the second service flow rule configured by the second ME application and the host of the first destination application If the addresses are the same, step 308 is performed.
  • the configuration method of the embodiment of the present application further includes:
  • Step 309 The ME platform manager checks whether there is an ME application instance associated with the NFP.
  • the ME application instance associated with the NFP refers to the service flow rule of the ME application instance being associated with the NFP, and the ME platform can forward the service flow or the packet indicated by the service flow rule by using the network resource provided by the NFP.
  • an NFP can be associated with multiple ME application instances. Only the ME application instances associated with the NFP are terminated. The ME platform manager determines that there is no ME application instance associated with the NFP.
  • Step 310 If there is no ME application instance associated with the NFP, the ME platform manager instructs the VIM to release the NFP.
  • the so-called VIM release NFP refers to the special network resources of the NFP created by the VIM release.
  • the ME platform manager further instructs the ME platform to delete the locally stored NFP.
  • the ME platform manager also deletes the locally stored NFP.
  • the ME platform manager may instruct the VIM to release the NFP, and reduce the cost of maintaining the NFP by the VIM.
  • FIG. 6 shows an application of the configuration method described in FIG. 2 to FIG. 5 in the ME application instantiation process. It should be understood that the process shown in FIG. 7 is only one possible application of the configuration method provided by the embodiment of the present application, and the scope of protection of the embodiment of the present application cannot be limited to the solution shown in FIG. 7. Referring to FIG. 7, the process of instantiating the ME application includes:
  • Step 401 An operation support system (OSS) initiates an instantiation request of the ME application to the ME orchestrator.
  • OSS operation support system
  • Step 402 The ME orchestrator selects an appropriate ME platform manager, and forwards the instantiation request of the ME application to the ME platform manager.
  • Step 403 The ME platform manager initiates a resource allocation request to the virtualized infrastructure manager VIM, and requests the VIM to allocate corresponding computing, storage, and network resources to the instantiated ME application.
  • Step 404 The VIM returns a resource allocation response to the ME platform manager, where the response message carries the computing, storage, and network resources allocated to the instantiated ME application.
  • Step 405 The ME platform manager initiates a configuration request to the ME platform, where the request message carries the service flow rule used by the ME application.
  • Step 406 The ME platform initiates a configuration request to the ME application instance to which the resource has been allocated, where the request message carries the service flow rule used by the ME application.
  • Step 407 The ME application instance accepts the service flow rule, and returns a configuration response to the ME platform, indicating a configuration result of the service flow rule.
  • Step 408 The ME platform further returns a configuration response to the ME platform manager, indicating a configuration result of the service flow rule.
  • Step 409 The ME platform manager initiates an NFP creation request to the VIM, and determines a network function node from the network function node where the ME application is located to the target application in the service flow rule according to the CP or SAP information of the available network function node in the management domain.
  • the packet forwarding path is used to forward the service flow or packet matching the service flow rule to the created NFP.
  • the NFP creation request carries a sequence of CPs or SAPs of all intermediately forwarded network function nodes, or according to a customized NFP rule, the NFP rules are used to dynamically generate a forwarding path that matches the service flow rules.
  • Step 410 The VIM returns an NFP creation response to the ME platform manager, and the response message indicates the result of the NFP creation.
  • Step 411 The ME platform manager initiates a configuration request to the ME platform, where the request message carries the NFP identification information and the service flow rule identification information matched by the service flow rule used by the ME application.
  • Step 412 The ME platform associates the newly created NFP with the service flow rule in the ME instance.
  • Step 413 The ME platform returns a configuration response to the ME platform manager, indicating the result of the association configuration between the NFP and the service flow rule.
  • Step 414 The ME platform manager returns a response of the ME application instantiation to the ME orchestrator, where the response message carries an execution result indicating that the ME application is instantiated.
  • Step 415 The ME orchestrator returns a response to the OS application instantiation to the OSS, where the response message carries an execution result indicating that the ME application is instantiated.
  • the subsequent ME platform first determines the forwarding action of the packet according to the service flow rule (for example, discard, copy and forward, and original forwarding). If the forwarding action is to perform forwarding, the ME platform further determines, according to the network forwarding path associated with the service flow rule, the CP or SAP of the next hop network function node of the network function node where the ME application is located, and forwards the packet to the next Jump the CP or SAP of the network function node.
  • the service flow rule for example, discard, copy and forward, and original forwarding.
  • all the intermediate forwarding network function nodes on the NFP path store the NFP identification information, and determine the NFP applied by the packet forwarding according to the NFP identification information carried by the forwarded packet, and further according to the sequence in the NFP.
  • the location of the network function node CP or SAP determines the network function node CP or SAP of the next hop until the network function node CP or SAP where the destination application is located reaches the path forwarding function of the packet.
  • the application descriptor of the ME application includes a service flow rule
  • the service flow rule includes a forwarding interface description, and is used to describe a policy for the ME application to forward the service flow or the packet.
  • the IP address and/or the MAC address of the forwarding interface are pre-configured in the forwarding interface description of the service flow rule of the application descriptor, so as to configure the ME platform to indicate the filtering condition of the service flow rule according to the service flow rule.
  • the packet is forwarded to the ME application using an interface with a pre-configured IP address and/or MAC address.
  • setting the address of the forwarding interface of the ME application to a fixed address in the application descriptor not only causes the use of the address resource to be inefficient, but also cannot be applied to the scenario where the address of the interface of the ME application is dynamically allocated.
  • the configuration method includes:
  • Step 501 The ME platform manager obtains a preset service flow rule from an application descriptor of the ME application, where the preset service flow rule includes a filter condition and a forwarding interface description, and the forwarding interface description includes a forwarding interface indication.
  • the application descriptor may also include resource requirement descriptions, DNS rules, dependent service descriptions, and the like.
  • the preset service flow rule may include (service flow rule) identification (ID), filter condition description, action description, and the like in addition to the forwarding interface description.
  • ID service flow rule
  • the filter (traffic filter) describes different service flows or packets that specify the ME application to perform differentiated transmission processing
  • the filter condition description includes a source/destination internet protocol (IP) address, a source/destination port number, and Protocol type, source/destination tunnel address, source/destination tunnel port, and so on.
  • IP internet protocol
  • the action description specifies the transmission policies to be performed on the target traffic or packet, including dropping packets, forwarding, encapsulation/decapsulation, replication, no processing, and so on.
  • the forwarding interface description indicates that the transmission policy is a forwarding object when forwarding, including interface type, tunnel information, source access control (MAC) address, destination MAC address, destination IP address, and so on.
  • Table 1 is a schematic implementation of a description of a forwarding interface in the embodiment of the present application.
  • Attribute name Quantity Parameter Type Interface type 1 Enum (Enum) Tunnel information (tunnelInfo) 0..1 TunnelInfo Source MAC address (srcMACAddress) 0..1 String (string) Destination MAC address (dstMACAddress) 0..1 String (string) Destination IP address (dstIPAddress) 0..1 String (string) Forwarding interface indication 0..1 Identifier
  • the forwarding interface indication in Table 1 may be an application external connection point (AppExtCp) field in the application descriptor, and is used to indicate a destination interface of the service flow or the packet defined by the filtering condition in the forwarding service flow rule.
  • AppExtCp application external connection point
  • Step 502 The ME platform manager determines that the VIM is an address resource allocated by the forwarding interface to the indicated interface.
  • Step 503 The ME platform manager determines the service flow rule to be configured according to the address resource and the preset service flow rule, where the forwarding interface indication in the service flow rule to be configured is associated with the address resource.
  • the forwarding interface indication may be associated with the address resource in multiple implementation manners, including but not limited to: adding the identifier of the address resource in the forwarding interface description, or adding the address or address range corresponding to the address resource in the forwarding interface description. Or, add other information indicating the address resource in the forwarding interface description, or add information from the AppExtCp to the forwarding interface description, such as the number of the forwarding interface description, in the application interface description of the AppD. Or, the ME platform manager maintains a mapping of the forwarding interface indication/forward interface description/service flow rule and the address resource.
  • the application descriptor of the ME application may not set the address of the forwarding interface, but add the indication information of the forwarding interface (such as AppExtCp), and wait until the VIM allocates the address resource to the forwarding interface, and then allocates the address.
  • the resource is associated with the forwarding interface indication/forwarding interface description/service flow rule, for example, the associated MAC and/or IP address is associated with the service flow rule according to the specified interface type information, and the filtering rule for forwarding the service flow rule is implemented.
  • the setting of the address of the indicated service flow or the interface of the packet can be applied not only to the scenario in which the address resource of the ME application interface is dynamically allocated, but also to avoid the low utilization of the address resource caused by configuring the fixed address for the ME application.
  • step 503 the method further includes:
  • Step 504 The ME platform manager sends a configuration request to the ME platform that manages the ME application, where the configuration request includes a service flow rule to be configured, and is used to request the ME platform to configure the service flow rule to be configured, according to the configured service flow rule.
  • the packet indicated by the filter condition is forwarded to an interface of the ME application that uses the address resource.
  • the service flow rule to be configured is configured to the ME application instance, so that the ME platform forwards the service flow or the packet indicated by the filtering condition to the interface that is the ME application instance, and the address of the interface can be dynamically allocated.
  • the ME platform configures the ME application instance, and configures the interface of the ME application instance that uses the address resource to receive the packet indicated by the filtering condition.
  • step 504 the method further includes:
  • Step 505 After the forwarding interface indicates that the address resource allocated by the indicated interface is changed, the ME platform manager determines the updated service flow rule, and the forwarding interface indication in the updated service flow rule is associated with the changed address resource.
  • Step 506 The ME platform manager sends a reconfiguration request to the ME platform, where the reconfiguration request includes an updated service flow rule, and is used to request the ME platform to configure the updated service flow rule, according to the configured updated service flow rule.
  • the packet indicated by the filter condition is forwarded to the interface of the ME application using the changed address resource.
  • the ME platform manager updates the service flow rule, reconfigures the ME platform by using the updated service flow rule, and implements the service flow or packet forwarding indicated by the filtering condition.
  • the interface to the ME application instance the address of the interface can be dynamically changed.
  • FIG. 9 shows an application of the configuration method described in FIG. 7 to FIG. 8 in the ME application instantiation process. It should be understood that the process shown in FIG. 8 is only one possible application of the configuration method provided by the embodiment of the present application, and the scope of protection of the embodiment of the present application cannot be limited to the solution shown in FIG. Referring to FIG. 9, the process of instantiating the ME application includes:
  • Step 601 The OSS sends an application instantiation request to the ME orchestrator.
  • Step 602 The ME orchestrator sends an application instantiation request to the ME platform manager.
  • Step 603 The ME platform manager sends a resource allocation request to the VIM, where the request parameter includes the number of interfaces of the application and the requirements for dynamically assigning addresses of each interface, such as a protocol type, an allocated address range, and the like.
  • Step 604 After completing the resource allocation, the VIM sends a resource allocation response to the ME platform manager, including the address information actually allocated by each application interface or the resource object identifier that can be used to query the allocated address.
  • Step 605 The ME platform manager associates the obtained interface address information with the application interface and the forwarding rule description in the AppD, and determines the service flow rule that needs to be configured. such as:
  • the packet whose source IP address is 192.168.2.1 is forwarded to the interface whose AppExtCpId is Eth1.
  • the ME platform manager allocates resources to the VIM according to the description of Eth1 in the AppD in step 603, and obtains the address actually allocated by Eth1 after instantiation in step 604 (or through the resource object identifier query in step 604), such as 10.1.1.1. .
  • the MEPM translates the service flow rules in the AppD to: Send the data packet with the source IP address 192.168.2.1 to the interface with the address 10.1.1.1, and send it as the request parameter in step 6.
  • Step 606 The ME platform manager sends the service flow rule to the ME platform for configuration.
  • Step 607 The ME platform performs related configuration on the ME application instance.
  • Step 608 The ME application instance returns a configuration response to the ME platform.
  • Step 609 The ME platform returns a configuration response to the ME platform manager.
  • Step 610 The ME platform manager returns an instantiation response to the ME orchestrator.
  • Step 611 The ME orchestrator returns an instantiation response to the OSS.
  • the configuration of the address of the dynamically allocated forwarding interface is implemented in the process of application instantiation, and the efficiency is high.
  • FIG. 10 shows a configuration apparatus of an embodiment of the present application, which can be used to implement the functions of the ME platform manager in any corresponding configuration method of FIG. 2-9.
  • the configuration device includes a determination module 71, a communication module 72, and an association module 73.
  • the determining module 71 is configured to determine a network forwarding path NFP that is applied by the first ME to the first destination application, where the NFP is used to indicate a service sent by the first ME application to the first destination application.
  • the communication module 72 is configured to send an NFP creation request to the VIM, requesting the VIM to create the NFP determined by the ME platform manager.
  • the association module 73 is configured to associate the NFP created by the VIM with the first service flow rule configured by the first ME application.
  • the communication module 72 is further configured to: send a configuration request to the ME platform that manages the first ME application, request the ME platform to configure an instance of the first ME application, where The created NFP is associated with the first service flow rule.
  • the determining module 71 is specifically configured to: determine, according to the first service flow rule, a host address of the first destination application; according to the host address of the first ME application, and the The host address of the first destination application determines the NFP.
  • the NFP includes a service flow of the first ME application or a connection point of a network function node that is grouped to the first destination application, and the forwarding sequence of the packet is forwarded according to the forwarding The sequence of junction points formed.
  • the determining module 71 is further configured to: determine that a host address of the instantiated second ME application is the same as a host address of the first ME application, and that is configured by the second ME application The host address of the second destination application in the second service flow rule is the same as the host address of the first destination application;
  • the association module 73 is further configured to: associate the second service flow rule with the created NFP.
  • the configuring device further includes:
  • the release module 74 is configured to check whether there is an ME application instance of the NFP that is associated with the creation; if not, the VIM is instructed to release the created NFP.
  • the determining module 71 is further configured to: before determining the NFP, obtain a preset first service flow rule from an application descriptor of the first ME application, where the preset The first service flow rule includes a filter condition and a forwarding interface description, and the forwarding interface description includes a forwarding interface indication; determining that the VIM is an address resource allocated by the forwarding interface to the indicated interface; according to the address resource and the The pre-set first service flow rule determines the first service flow rule to be configured, and the forwarding interface indication in the first service flow rule to be configured is associated with the address resource.
  • the communication module 72 is further configured to: send a configuration request to the ME platform, where the configuration request includes the first service flow rule to be configured, and is used to request the ME platform configuration. And the first service flow rule to be configured, the packet indicated by the filtering condition is forwarded to the interface of the first ME application that uses the address resource according to the configured first service flow rule.
  • the determining module 71 is further configured to: after the forwarding interface indicates that the address resource allocated by the indicated interface is changed, determine an updated first service flow rule, where the updated first The forwarding interface indication in the service flow rule is associated with the changed address resource;
  • the communication module 72 is further configured to: send a reconfiguration request to the ME platform, where the reconfiguration request includes the updated first service flow rule, configured to request the ME platform to configure the first update
  • the service flow rule forwards the packet indicated by the filter condition to the interface of the first ME application that uses the updated address resource according to the configured updated first service flow rule.
  • each functional module in each embodiment of the present invention may be integrated into one processing. In the device, it can also be physically existed alone, or two or more modules can be integrated into one module.
  • the above integrated modules can be implemented in the form of hardware or in the form of software functional modules.
  • the configuration device may include the processor 81.
  • the hardware of the entity corresponding to the determining module 71, the associating module 73, and the releasing module 74 may be the processor 81.
  • the processor 81 may be one or more central processing units (CPUs), or a digital processing module or the like.
  • the configuration device can also include a communication interface 82 through which the processor 81 communicates with the host or network management device.
  • the hardware of the entity corresponding to the communication module 72 may be the communication interface 82.
  • the configuration device also includes a memory 83 for storing a program executed by the processor 81.
  • the memory 83 may be a non-volatile memory, such as a hard disk drive (HDD) or a solid-state drive (SSD), or a volatile memory such as a random access memory (random- Access memory, RAM).
  • Memory 63 is any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer, but is not limited thereto.
  • FIG. 12 illustrates another configuration apparatus of an embodiment of the present application, which may be used to implement the functions of the ME platform manager in any corresponding configuration method of FIGS. 7-9.
  • the configuration device includes an acquisition module 91 and a determination module 92.
  • the obtaining module 91 is configured to obtain a pre-set service flow rule from an application descriptor of the ME application, where the preset service flow rule includes a filtering condition and a forwarding interface description, where the forwarding interface description includes a forwarding interface indication;
  • the module 92 is configured to determine an address resource that is allocated by the VIM to the indicated interface, and determine a service flow rule to be configured according to the address resource and the preset service flow rule, where the service to be configured is configured.
  • the forwarding interface indication in the flow rule is associated with the address resource.
  • the configuration apparatus further includes: a communication module 93, configured to send, after the determining module determines the service flow rule to be configured, a configuration request to the ME platform that manages the ME application, where the configuration request is
  • the service flow rule to be configured is configured to request the ME platform to configure the service flow rule to be configured, and forward the packet indicated by the filter condition to a usage of the ME application according to the configured service flow rule.
  • the interface that describes the address resource.
  • the determining module 92 is further configured to: after the forwarding interface indicates that the address resource allocated by the indicated interface is changed, determine an updated service flow rule, where the updated service flow rule is used.
  • the forwarding interface indication is associated with the changed address resource;
  • the communication module 93 is further configured to: send a reconfiguration request to the ME platform, where the reconfiguration request includes the updated service flow rule,
  • the ME platform is configured to configure the updated service flow rule, and forward the packet indicated by the filtering condition to an interface of the ME application that uses the changed address resource according to the configured updated service flow rule.
  • the configuration device may include a processor.
  • the hardware of the entity corresponding to the obtaining module 91 and the determining module 92 may be a processor.
  • the configuration device can also include a communication interface through which the processor communicates with the host or network management device.
  • the hardware of the entity corresponding to the communication module 93 may be a communication interface.
  • the configuration device also includes a memory for storing a program executed by the processor.
  • the memory may be a non-volatile memory, such as a hard disk drive (HDD) or a solid-state drive (SSD), or a volatile memory such as a random access memory (random- Access memory, RAM).
  • Memory 63 is any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer, but is not limited thereto.
  • the embodiment of the present application further provides an apparatus for creating a resource, including: a communication module and a resource creation module. And a communication module, configured to receive an NFP creation request sent by the ME platform manager, where the NFP request includes an NFP generated by the ME platform manager. A resource creation module for creating the NFP. The communication module is further configured to return a creation result to the ME platform manager.
  • the embodiment of the present application further provides a configuration apparatus, including: a communication module and a configuration module.
  • the communication module is configured to receive a configuration request sent by the ME platform manager, where the configuration request includes an identifier of the created NFP and an identifier of the service flow rule of the ME application.
  • the configuration module is configured to configure an instance of the ME application, and associate the identifier of the NFP with the identifier of the service flow rule.
  • the present application provides a computer readable storage medium having stored therein computer instructions that, when executed on a computer, cause the computer to perform any of the corresponding configuration methods of FIGS. 2-9 above.
  • the present application provides a computer program product that, when run on a computer, causes the computer to perform any of the corresponding configuration methods of FIGS. 2-9 above.
  • the computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture comprising the instruction device.
  • the apparatus implements the functions specified in one or more blocks of a flow or a flow and/or block diagram of the flowchart.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

一种配置方法及装置，用以解决现有技术中存在业务流或分组的转发时延较长的问题。所述配置方法包括：移动边缘ME平台管理器确定实例化的第一ME应用至第一目的应用的网络转发路径NFP，所述NFP用于指示由所述第一ME应用发送至所述第一目的应用的业务流或分组的转发路径；所述ME平台管理器向虚拟化基础设施管理器VIM发送NFP创建请求，请求所述VIM创建所述ME平台管理器确定的所述NFP；所述ME平台管理器将所述VIM创建的所述NFP与所述第一ME应用配置的第一业务流规则关联。

Description

一种配置方法及装置
本申请要求于2017年11月21日提交中国国家知识产权局、申请号为201711167051.3、发明名称为“一种配置方法及装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及信息技术领域，尤其涉及一种配置方法及装置。
背景技术
移动边缘(mobile edge，ME)计算是利用无线接入网络就近提供电信用户所需的信息技术(information technology，IT)服务和云计算功能，而形成一个具有高性能、低延迟和高带宽的电信级服务环境，加速网络中各项内容、服务及应用的快速下载，让消费者享有不间断的高质量网络体验。
ME应用的数据包中包含一个称为应用描述符(application descriptor，AppD)的模板文件，AppD描述了应用对虚拟计算、存储、网络资源的需求、依赖的服务、特性、DNS规则、业务流规则等信息。ME管理系统可以通过AppD中的信息，对ME应用进行生命周期管理，如对ME应用进行资源配置以创建应用实例(也称之为应用实例化)、进行业务流规则配置、删除应用实例等。其中，ME应用的业务流规则配置发生在ME应用资源配置之后，当ME平台应用业务流规则对该ME应用实例的业务流或分组进行转发时，ME平台管理器需要根据业务流规则按需在基础设施层创建业务流或分组的转发路由，然后逐跳转发业务流或分组到达目的网络节点或目的应用。
上述现有技术中，业务流或分组的转发时延较长。
发明内容
本申请提供一种配置方法及装置，用以解决现有技术中存在业务流或分组的转发时延较长的问题。
第一方面，本申请提供一种配置方法，包括：移动边缘ME平台管理器确定实例化的第一ME应用至第一目的应用的网络转发路径NFP，所述NFP用于指示由所述第一ME应用发送至所述第一目的应用的业务流或分组的转发路径。所述ME平台管理器向虚拟化基础设施管理器VIM发送NFP创建请求，请求所述VIM创建所述ME平台管理器确定的所述NFP，VIM创建的NFP是对用于转发业务流或分组的网络资源进行组装所形成的传输路径资源，是一种特殊的网络资源。所述ME平台管理器将所述VIM创建的所述NFP与所述第一ME应用配置的第一业务流规则关联。例如，ME平台管理器可以将创建的NFP的标识与第一业务流规则的标识信息相关联。
上述技术方案中，ME平台管理器请求VIM将用于传输第一ME应用的业务流或分组的网络资源进行组装形成NFP，并将创建的NFP与第一ME应用的业务流规则进行关联，在将该关联关系配置到ME平台之后，ME平台可以直接根据使用的业务流规则来选择其关联的NFP来传输第一ME应用的业务流或分组，与现有技术中需由ME平台在实际转发第 一ME应用的业务流或分组时根据业务流规则逐跳确定转发的下一跳网络功能节点的地址相比，能够有效避免第一ME应用的业务流或分组在转发时建立转发路径的额外处理时延开销，保障ME应用低时延或实时性的传输需求。
在第一方面的一些实现方式中，所述ME平台管理器还向管理所述第一ME应用的ME平台发送配置请求，请求所述ME平台对所述第一ME应用的实例进行配置，该配置具体可以为：将创建的NFP与第一ME应用配置的第一业务流规则关联。上述技术方案中，ME平台使用业务流规则进行该第一ME应用的业务流或分组的转发时，可以直接利用建立好的网络转发路径NFP来实施分组的下一跳，进而减少第一ME应用的业务流或分组的转发时延。
在第一方面的一些实现方式中，所述ME平台管理器确定所述第一ME应用至第一目的应用的NFP，的实现方式可以为：所述ME平台管理器根据所述第一业务流规则确定所述第一目的应用的主机地址；所述ME平台管理器根据所述第一ME应用的主机地址以及所述第一目的应用的主机地址确定所述NFP。上述技术方案中，ME平台管理器可以根据业务流规则确定第一ME应用的第一目的应用的主机地址，基于第一ME应用自身的主机地址、第一目的应用的主机地址确定网络转发路径NFP，使得由第一ME应用发送的业务流或分组经由该NFP指示的网络功能节点传输至第一目的应用，其中，确定该NFP的算法可以参照现有技术中的各种技术手段，本申请实施例不予详述。
在第一方面的一些实现方式中，所述NFP包括所述第一ME应用的业务流或分组到所述第一目的应用所经过的网络功能节点的连接点，按照转发所述分组经过的前后跳顺序所形成的连接点序列。可选的，NFP包括连接点序列中的连接点为ME平台管理器管理域内可用网络功能节点的连接点。上述技术方案中，ME平台管理器可以根据第一ME应用的业务流或分组到第一目的应用所经过的网络功能节点的连接点生成NFP，进而请求VIM生成该NFP，便于ME平台使用该NFP按照第一业务流规则转发第一ME应用到第一目的应用的业务流或分组，实现方式简单、高效。
在第一方面的一些实现方式中，所述ME平台管理器确定实例化的第二ME应用的主机地址与所述第一ME应用的主机地址相同，以及，所述第二ME应用配置的第二业务流规则中的第二目的应用的主机地址与所述第一目的应用的主机地址相同。所述ME平台管理器将所述第二业务流规则与创建的所述NFP关联。上述技术方案中，创建的NFP可以关联多个ME应用的业务流规则，不仅可以提高NFP的利用率，也可以减少ME平台管理器确定NFP以及VIM创建NFP的资源的开销。
在第一方面的一些实现方式中，所述ME平台管理器检查是否存在关联创建的所述NFP的ME应用实例；所谓关联NFP的ME应用实例，指该ME应用实例的业务流规则与NFP关联，ME平台可以使用该NFP提供的网络资源转发该业务流规则指示的业务流或分组。若不存在关联NFP的ME应用实例，则指示所述VIM释放所述NFP。可选的，若不存在关联NFP的应用实例，则ME平台管理器还指示ME平台删除的本地存储的该NFP。可选的，若不存在关联NFP的应用实例，则ME平台管理器还删除本地存储的该NFP。上述技术方案中，随着关联NFP的ME应用实例终结，ME平台管理器可以指示VIM释放该NFP，减少VIM维护该NFP的开销。
在第一方面的一些实现方式中，所述ME平台管理器还可以从所述第一ME应用的应用描述符获取预设置的第一业务流规则，所述预设置的第一业务流规则包括过滤条件以及转发接口描述，所述转发接口描述包括转发接口指示；所述ME平台管理器确定所述VIM为所述转发接口指示所指示的接口分配的地址资源；所述ME平台管理器根据所述地址资源以及所述预设置的第一业务流规则确定待配置的第一业务流规则，所述待配置的第一业务流规则中的所述转发接口指示与所述地址资源相关联。上述技术方案中，ME应用的应用描述符中可以不设置转发接口的地址，而是添加转发接口的指示信息(如AppExtCp)，待到VIM为该转发接口分配地址资源之后，再将分配的地址资源与该转发接口指示/转发接口描述/业务流规则相关联，比如根据指定的接口类型信息，将所分配的MAC和/或IP地址与业务流规则做关联，实现转发业务流规则的过滤规则指示的业务流或分组的接口的地址的设置，上述方法不仅可以适用于ME应用接口的地址资源动态分配的场景，而且避免为ME应用配置固定地址导致的地址资源利用率低下。
在第一方面的一些实现方式中，在所述ME平台管理器确定所述待配置的第一业务流规则之后，所述ME平台管理器向所述ME平台发送配置请求，所述配置请求包括所述待配置的第一业务流规则，用于请求所述ME平台配置所述待配置的第一业务流规则，根据配置的第一业务流规则将所述过滤条件指示的分组转发至所述第一ME应用的使用所述地址资源的接口。
在第一方面的一些实现方式中，在所述转发接口指示所指示的接口分配的地址资源发生变更后，所述ME平台管理器确定更新的第一业务流规则，所述更新的第一业务流规则中的所述转发接口指示与变更后的地址资源相关联；所述ME平台管理器向所述ME平台发送重配置请求，所述重配置请求包括所述更新的第一业务流规则，用于请求所述ME平台配置所述更新的第一业务流规则，根据配置的更新的第一业务流规则将所述过滤条件指示的分组转发至所述第一ME应用的使用更新后的地址资源的接口。上述技术方案中，在ME应用的接口的地址资源发生变更后，ME平台管理器更新业务流规则，通过更新的业务流规则对ME平台进行重配置，实现将过滤条件指示的业务流或分组转发至ME应用实例的接口，该接口的地址可动态变更。
第二方面，本申请提供一种配置方法，包括：ME平台管理器从ME应用的应用描述符获取预设置的业务流规则，所述预设置的业务流规则包括过滤条件以及转发接口描述，所述转发接口描述包括转发接口指示，该转发接口指示可以为应用描述符中的应用外部连接点(application external connection point，AppExtCp)字段，用于指示转发业务流规则中过滤条件定义的业务流或分组的目的接口。所述ME平台管理器确定VIM为所述转发接口指示所指示的接口分配的地址资源；根据所述地址资源以及所述预设置的业务流规则确定待配置的业务流规则，所述待配置的业务流规则中所述转发接口指示与所述地址资源相关联。上述技术方案中，ME应用的应用描述符中可以不设置转发接口的地址，而是添加转发接口的指示信息(如AppExtCp)，待到VIM为该转发接口分配地址资源之后，再将分配的地址资源与该转发接口指示/转发接口描述/业务流规则相关联，比如根据指定的接口类型信息，将所分配的MAC和/或IP地址与业务流规则做关联，实现转发业务流规则的过滤规则指示的业务流或分组的接口的地址的设置，上述方法不仅可以适用于ME应用接口的地址资源 动态分配的场景，而且避免为ME应用配置固定地址导致的地址资源利用率低下。
在第二方面的一些实现方式中，所述ME平台管理器还向管理所述ME应用的ME平台发送配置请求，所述配置请求包括所述待配置的业务流规则，用于请求所述ME平台配置所述待配置的业务流规则，根据配置的业务流规则将所述过滤条件指示的分组转发至所述ME应用的使用所述地址资源的接口。可选的，ME平台对ME应用实例进行配置，配置ME应用实例的使用该地址资源的接口接收该过滤条件指示的分组。上述技术方案中，通过将待配置的业务流规则向ME应用实例进行配置，使得ME平台将过滤条件指示的业务流或分组转发至为ME应用实例的接口，该接口的地址可动态分配。
在第二方面的一些实现方式中，在所述转发接口指示所指示的接口分配的地址资源发生变更后，所述ME平台管理器确定更新的业务流规则，所述更新的业务流规则中的所述转发接口指示与变更后的地址资源相关联；所述ME平台管理器向所述ME平台发送重配置请求，所述重配置请求包括所述更新的业务流规则，用于请求所述ME平台配置所述更新的业务流规则，根据配置的更新的业务流规则将所述过滤条件指示的分组转发至所述ME应用的使用变更后的地址资源的接口。上述技术方案中，在ME应用的接口的地址资源发生变更后，ME平台管理器更新业务流规则，通过更新的业务流规则对ME平台进行重配置，实现将过滤条件指示的业务流或分组转发至ME应用实例的接口，该接口的地址可动态变更。
第三方面，本申请提供一种创建资源的方法，包括：VIM接收ME平台管理器发送的NFP创建请求，所述NFP创建请求包括所述ME平台管理器生成的NFP；所述VM创建所述NFP，并向所述ME平台管理器返回NFP创建结果。上述技术方案中，VIM可以将对用于转发业务流或分组的网络资源进行组装所形成的传输路径资源，以便ME平台可以直接根据使用的业务流规则来选择其关联的NFP这一网络资源来传输第一ME应用的业务流或分组，减少业务流或分组的传输耗时。
第四方面，本申请提供一种配置方法，包括：ME平台接收ME平台管理器发送的配置请求，所述配置请求包括创建的NFP的标识以及ME应用的业务流规则的标识；所述ME平台对所述ME应用的实例进行配置，将所述NFP的标识与所述业务流规则的标识关联。上述技术方案中，ME平台可以将ME应用的业务流规则与NFP资源关联，以便ME平台可以直接根据使用的业务流规则来选择其关联的NFP这一网络资源来传输第一ME应用的业务流或分组，减少业务流或分组的传输耗时。
第五方面，本申请提供一种配置装置，该装置用于执行上述第一、第二或第四方面，或第一、第二或第四方面中任一方面的任意可能的实现中的方法。具体的，该配置装置包括用于执行上述第一、第二或第四方面，或第一、第二或第四方面中任一方面的任意可能的实现中的方法的模块。
第六方面，本申请提供一种创建资源的装置，该装置用于执行上述第三方面的方法。具体的，该装置包括用于执行上述第三方面的方法的模块。
第七方面，本申请实施例提供一种通信设备，所述通信设备包括处理器、存储器以及通信接口，所述通信接口用于与其他通信装置通信，所述存储器用于存储计算机指令；所述处理器用于执行所述计算机指令，以在执行所述计算机指令时执行上述第一至第四方面 中任一方面或第一至第四方面中任一方面的任意可能的实现中的方法。
第八方面，本申请提供了一种计算机可读存储介质，该可读存储介质中存储有计算机指令，所述指令在计算机上运行时，使得计算机执行上述第一至第四方面中任一方面或第一至第四方面中任一方面的任意可能的实现中的方法。
第九方面，本申请提供了一种计算机程序产品，所述计算机程序产品在计算机上运行时，使得计算机执行上述第一至第四方面中任一方面或第一至第四方面中任一方面的任意可能的实现中的方法。
本申请在上述各方面提供的实现的基础上，还可以进行进一步组合以提供更多实现。
附图说明
图1为本申请的至少一个实施例中移动边缘计算的架构的示意图；
图2-图5、图7-图8为本申请的至少一个实施例中配置方法的流程示意图；
图6、图9为本申请的至少一个实施例中ME应用实例化的流程示意图；
图10-图12为本申请的至少一个实施例中配置装置的示意图。
具体实施方式
为了使本申请的目的、技术方案和优点更加清楚，下面将结合附图对本申请作进一步地详细描述。
本申请提供一种配置方法及装置，用以解决现有技术中存在业务流或分组的转发时延较长的问题。其中，方法和装置是基于同一发明构思的，由于方法及装置解决问题的原理相似，因此装置与方法的实施可以相互参见，重复之处不再赘述。
本申请中所涉及的多个，是指两个或两个以上。另外，在本申请的描述中，“第一”、“第二”等词汇，仅用于区分描述的目的，而不能理解为指示或暗示相对重要性，也不能理解为指示或暗示顺序。
应理解，本申请实施例的技术方案可以应用于各种移动通信系统，例如：5G新无线接入技术(5th Generation New Radio Access Technology，5G NR)系统、长期演进(long termevolution，LTE)系统、LTE频分双工(frequency division duplex，FDD)系统、LTE时分双工(time division duplex，TDD)、码分多址(code division multiple access，CDMA)系统、宽带码分多址(wideband code division multiple access，WCDMA)系统、全球移动通讯(globalsystem of mobile communication，GSM)系统、通用分组无线业务(general packet radio service，GPRS)、通用移动通信系统(universal mobile telecommunication system，UMTS)、全球互联微波接入(worldwide interoperability for microwave access，WiMAX)通信系统等。
图1示出了移动边缘计算(mobile edge computing，MEC)的参考架构，该参考架构包括ME主机10以及ME管理系统20。
ME主机10包含ME平台11和虚拟化基础设施(virtualised infrastructure，VI)12，虚拟化基础设施12为ME应用提供虚拟化的计算、存储和网络资源，ME应用以虚拟机或者容器的形式部署在ME主机10上。虚拟化基础设施12包含一个数据面，它执行来自ME平台11的业务流规则并完成报文的路由功能。ME主机10上还部署了ME平台11，ME平台11中包含了一些公共服务，如终端位置服务、无线网络信息服务、域名系统(domain name system，DNS)服务器或者DNS代理服务等，ME应用可以使用这些公共服务。ME平台11的服务注册功能为ME应用提供了发现和使用ME服务的能力。业务流规则服务从ME管理系统20接收业务流规则并下发给数据面。DNS服务从ME管理系统20接收域名和IP地址的映射规则。
ME管理系统20包含ME编排器(mobile edge orchestrator，MEO)21、ME平台管理器(mobile edge platform manager，MEPM)22、虚拟化基础设施管理器(virtualisedinfrastructure manager，VIM)23等。ME编排器21维护ME系统中所有的ME主机、可用资源、可用ME服务的总体视图，触发应用的实例化和终结。ME平台管理器22用于管理ME平台、管理ME应用的生命周期、管理应用的业务流规则和DNS规则。虚拟化基础设施管理器23管理ME应用所需的虚拟化资源。
图2示出了本申请实施例的一种配置方法，包括：
步骤301、ME平台管理器确定实例化的第一ME应用至第一目的应用的网络转发路径(network forwarding path，NFP)。该NFP用于指示由第一ME应用发送至该第一目的应用的业务流或分组的转发路径。步骤301在第一ME应用实例化(即：VIM为第一ME应用分配虚拟资源)之后执行，可选的，步骤301在第一ME应用实例化以及ME平台将业务流规则配置至第一ME应用的实例之后执行。第一ME应用的实例化以及业务流规则的配置过程可以参见现有技术中的各种可能实施方式，本申请实施例不予详述。
步骤302、ME平台管理器向虚拟化基础设施管理器VIM发送NFP创建请求，该NFP创建请求用于请求VIM创建该NFP。
步骤303、VIM接收NFP创建请求，根据该NFP请求创建NFP。所谓NFP可以指对用于转发业务流或分组的网络资源进行组装所形成的传输路径资源，是一种特殊的网络资源。
步骤304、VIM向ME平台管理器返回NFP创建结果，该NFP创建结果可以为创建的NFP的标识。
步骤305、ME平台管理器将VIM创建的NFP与第一ME应用配置的第一业务流规则关联。上述NFP与第一业务流规则的关联可以有多种实现方式，例如，ME平台管理器可以将创建的NFP的标识与第一业务流规则的标识信息相关联，又例如，ME平台管理器可以在该第一业务流规则中添加创建的NFP的标识。
上述技术方案中，ME平台管理器请求VIM将用于传输第一ME应用的业务流或分组的网络资源进行组装形成NFP，并将创建的NFP与第一ME应用的业务流规则进行关联，在将该关联关系配置到ME平台之后，ME平台可以直接根据使用的业务流规则来选择其关联的NFP来传输第一ME应用的业务流或分组，与现有技术中需由ME平台在实际转发第一ME应用的业务流或分组时根据业务流规则逐跳确定转发的下一跳网络功能节点的地址相比，能够有效避免第一ME应用的业务流或分组在转发时建立转发路径的额外处理时延开销，保障ME应用低时延或实时性的传输需求。
应理解，第一ME应用的实例可以配置多个业务流规则，ME平台管理器根据第一ME应用的不同业务流规则所确定的NFP可以不同，ME平台管理器可以将多个业务流规则分别与各自对应的NFP相关联。
作为一种可选的方式，继续参照图2，在步骤305之后，还包括：
步骤306、ME平台管理器向管理第一ME应用的ME平台发送配置请求，该配置请求用于请求ME平台对第一ME应用的实例进行配置，该配置具体可以为：将创建的NFP与第一ME应用配置的第一业务流规则关联。
上述技术方案中，ME平台使用业务流规则进行该第一ME应用的业务流或分组的转发时，可以直接利用建立好的网络转发路径NFP来实施分组的下一跳，进而减少第一ME应用的业务流或分组的转发时延。
作为一种可选的方式，参照图3，步骤301的实施可以包括如下步骤：
步骤3011、ME平台管理器根据第一ME应用配置的第一业务流规则确定第一目的应用的主机地址。在一些实施例中，ME平台管理器可以从ME编排器读取第一ME应用的应用描述符，从该应用描述符中获取该第一业务流规则，本申请实施例中，应用描述符中的业务流规则又可称为预设置的业务流规则。预设置的第一业务流规则中包括第一ME应用的第一目的应用的主机地址。在另一些实施例中，ME平台管理器保存有第一ME应用已配置的第一业务流规则，ME平台可以从该已配置的第一业务流规则中读取第一ME应用的第一目的应用的主机地址。
步骤3012、ME平台管理器根据第一ME应用的主机地址以及第一目的应用的主机地址确定NFP。该第一ME应用的主机地址以及第一目的应用的主机地址的类型可以为IP地址、MAC地址或者隧道连接的标识等。
上述技术方案中，ME平台管理器可以根据业务流规则确定第一ME应用的第一目的应用的主机地址，基于第一ME应用自身的主机地址、第一目的应用的主机地址确定网络转发路径NFP，使得由第一ME应用发送的业务流或分组经由该NFP指示的网络功能节点传输至第一目的应用，其中，确定该NFP的算法可以参照现有技术中的各种技术手段，本申请实施例不予详述。
作为一种可选的方式，网络转发路径NFP定义第一ME应用至第一目的应用的业务流或分组的转发路径，在一些可能的实施例中，该NFP实际也是第一ME应用所位于的ME平台到第一目的应用所位于的主机或网络功能节点的业务流或分组的转发路径。NFP可以包括连接点序列，所谓的连接点可以为虚拟网络功能(virtual network function，VNF)的外部连接点(connection point，CP)，也可以为物理网络功能(physical network function，PNF)的外部连接点CP，还可以为网络服务的服务接入点(service access point，SAP)。应理解，一个NFP中的连接点的类型可以不相同，例如，一个NFP中可以包括VNF1的CP1、PNF2的CP2以及网络服务3的SAP3。可选的，NFP包括连接点序列中的连接点为ME平台管理器管理域内可用网络功能节点的连接点。
NFP包括的连接点序列可以有多种实现方式，例如，该连接点序列可以为第一ME应用的业务流或分组到第一目的应用所经过的网络功能节点的连接点，按照转发分组经过的前后跳顺序所形成的序列。
应理解，在一些可能实施例中，该NFP还可以包括第一ME应用所位于的主机的连接点和/或第一目的应用所位于主机的连接点。
上述技术方案中，ME平台管理器可以根据第一ME应用的业务流或分组到第一目的应 用所经过的网络功能节点的连接点生成NFP，进而请求VIM生成该NFP，便于ME平台使用该NFP按照第一业务流规则转发第一ME应用到第一目的应用的业务流或分组，实现方式简单、高效。
作为一种可选的方式，参照图4，本申请实施例的配置方法还包括：
步骤307、ME平台管理器确定实例化的第二ME应用的主机地址与第一ME应用的主机地址相同，以及，第二ME应用配置的第二业务流规则中的第二目的应用的主机地址与第一目的应用的主机地址相同。
步骤308、ME平台管理器将第二业务流规则与第一ME应用的第一业务流规则已关联的NFP关联。
上述技术方案中，针对在步骤304之后实例化或配置业务流规则的第二ME应用，若其主机地址与第一ME应用主机地址相同，其第二目的应用的主机地址与第一目的应用的主机地址相同，表明该第二ME应用到第二目的应用的业务流或分组可以经由针对第一ME应用已创建的该NFP定义的路径进行转发，ME平台管理器可以直接将该NFP与第二ME应用的第二业务流规则关联，以便之后根据该NFP定义的路径转发第二ME应用到第二目的应用的数据流或分组。上述技术方案中，创建的NFP可以关联多个ME应用的业务流规则，不仅可以提高NFP的利用率，也可以减少ME平台管理器确定NFP以及VIM创建NFP的资源的开销。
可选的，上述步骤307中，ME平台管理器还可以判断该NFP是否已经与第一ME应用的业务流规则关联，若NFP已经与第一ME应用的业务流规则关联，且ME平台管理器确定实例化的第二ME应用的主机地址与第一ME应用的主机地址相同，以及，第二ME应用配置的第二业务流规则中的第二目的应用的主机地址与第一目的应用的主机地址相同，则执行步骤308。
作为一种可选的方式，参照图5，本申请实施例的配置方法还包括：
步骤309、ME平台管理器检查是否存在关联NFP的ME应用实例。所谓关联NFP的ME应用实例，指该ME应用实例的业务流规则与NFP关联，ME平台可以使用该NFP提供的网络资源转发该业务流规则指示的业务流或分组。另外，一个NFP可以关联多个ME应用实例，只有关联该NFP的所有ME应用实例均终结，ME平台管理器才确定不存在关联NFP的ME应用实例。
步骤310、若不存在关联NFP的ME应用实例，则ME平台管理器指示VIM释放该NFP。所谓VIM释放NFP指的是，VIM释放创建的NFP这一特殊的网络资源。
可选的，若不存在关联NFP的应用实例，则ME平台管理器还指示ME平台删除的本地存储的该NFP。
可选的，若不存在关联NFP的应用实例，则ME平台管理器还删除本地存储的该NFP。
上述技术方案中，随着关联NFP的ME应用实例终结，ME平台管理器可以指示VIM释放该NFP，减少VIM维护该NFP的开销。
图6示出了图2至图5所述配置方法在ME应用实例化流程中的应用。应理解，图7所示的流程只是本申请实施例提供的配置方法的一种可能应用，不能将本申请实施例的保护范围限定为图7所示的方案。参照图7，ME应用实例化的流程包括：
步骤401、运营支撑系统(operation support system，OSS)向ME编排器发起ME应用的实例化请求。
步骤402、ME编排器选择适当的ME平台管理器，将该ME应用的实例化请求转发给该ME平台管理器。
步骤403、ME平台管理器向虚拟化基础设施管理器VIM发起资源分配请求，请求VIM为实例化的ME应用分配相应的计算、存储和网络资源。
步骤404、VIM向ME平台管理器返回资源分配应答，该应答消息中携带分配给实例化的ME应用的计算、存储和网络资源。
步骤405、ME平台管理器向ME平台发起配置请求，该请求消息中携带ME应用所使用的业务流规则。
步骤406、ME平台向已经分配了资源的ME应用实例发起配置请求，该请求消息中携带ME应用所使用的业务流规则。
步骤407、ME应用实例接纳该业务流规则，并向ME平台返回配置应答，指示业务流规则的配置结果。
步骤408、ME平台进一步向ME平台管理器返回配置应答，指示业务流规则的配置结果。
步骤409、ME平台管理器向VIM发起NFP创建请求，根据其管理域内的可用网络功能节点的CP或SAP信息确定一条从ME应用所位于的网络功能节点到业务流规则中目应用的网络功能节点的分组转发路径，用于将该ME应用匹配该业务流规则的业务流或分组在创建的NFP上进行转发。NFP创建请求中携带一个由所有中间转发的网络功能节点的CP或SAP组成的序列，或者根据自定义的NFP规则，该NFP规则用于动态生成与该业务流规则匹配的转发路径。
步骤410、VIM向ME平台管理器返回NFP创建应答，应答消息中指示NFP创建的结果。
步骤411、ME平台管理器向ME平台发起配置请求，该请求消息中携带ME应用使用的业务流规则所匹配的NFP的标识信息和业务流规则的标识信息。
步骤412、ME平台在该ME实例中将新创建的NFP和该业务流规则进行关联。
步骤413、ME平台向ME平台管理器返回配置应答，指示NFP和业务流规则关联配置的结果。
步骤414、ME平台管理器向ME编排器返回ME应用实例化的应答，该应答消息中携带指示ME应用实例化的执行结果。
步骤415、ME编排器向OSS返回ME应用实例化的应答，该应答消息中携带指示ME应用实例化的执行结果。
需要说明的是，后续ME平台在应用业务流规则进行该ME应用的业务流或分组的转发时，首先根据业务流规则判断该分组的转发动作(例如：丢弃、复制转发、原本转发)。如果转发动作是进行转发，那么ME平台进一步根据业务流规则所关联的网络转发路径确定该ME应用所位于的网络功能节点的下一跳网络功能节点的CP或SAP，将分组转发到该下一跳网络功能节点的CP或SAP。类似的，该NFP路径上所有的中间转发的网络功能节 点都存储该NFP的标识信息，并根据转发过来的分组所携带的NFP标识信息确定分组转发所应用的NFP，进一步根据该NFP中的序列中本网络功能节点CP或SAP的位置确定下一跳的网络功能节点CP或SAP，直至到达目的应用所位于的网络功能节点CP或SAP，完成分组的路径转发功能。
上述技术方案中，在应用实例化的过程中实现业务流规则与转发资源(NFP)的关联，效率较高。
另一方面，ME应用的应用描述符包括业务流规则，该业务流规则包括转发接口描述，用于描述ME应用对业务流或分组进行转发的策略。现有技术中，需要在应用描述符的业务流规则的转发接口描述中预配置转发接口的IP地址和/或MAC地址，以便根据该业务流规则配置ME平台将业务流规则的过滤条件指示的分组转发至ME应用的使用预配置的IP地址和/或MAC地址的接口。但是，在应用描述符中将ME应用的转发接口的地址设置为固定地址，不仅导致地址资源的使用效率较低，也无法适用于ME应用的接口的地址动态分配的场景。
为了解决上述转发接口描述无法适用ME应用的接口的地址动态分配的场景的问题，本申请实施例提供另一配置方法。参照图7，该配置方法包括：
步骤501、ME平台管理器从ME应用的应用描述符获取预设置的业务流规则，预设置的业务流规则包括过滤条件以及转发接口描述，转发接口描述包括转发接口指示。
应理解，除了业务流规则之外，应用描述符还可以包括资源需求描述、DNS规则、依赖的服务描述等内容。该预设置的业务流规则除了包括转发接口描述之外，还可以包括(业务流规则)标识(identification，ID)、过滤条件描述、动作描述等内容。其中，过滤条件(trafficfilter)描述指定了ME应用需要进行差异化的传输处理的不同的业务流或分组，过滤条件描述包括源/目的网际协议(internet protocol，IP)地址、源/目的端口号、协议类型、源/目的隧道地址、源/目的隧道端口等信息。动作描述规定了对目标业务流或分组所执行的传输策略，包括丢弃数据包、转发、封装/解封装、复制、不处理等。转发接口描述表示传输策略为转发时的转发对象，包括接口类型、隧道信息、源介质访问控制(media access control，MAC)地址、目的MAC地址、目的IP地址等信息描述。表1为本申请实施例中转发接口描述的一种可能实现示意。
属性名称 数量 参数类型
接口类型(interfaceType) 1 枚举(Enum)
隧道信息(tunnelInfo) 0..1 TunnelInfo
源MAC地址(srcMACAddress) 0..1 字符串(String)
目的MAC地址(dstMACAddress) 0..1 字符串(String)
目的IP地址(dstIPAddress) 0..1 字符串(String)
转发接口指示 0..1 标识符(Identifier)
表1
表1中转发接口指示可以为应用描述符中的应用外部连接点(application external connection point，AppExtCp)字段，用于指示转发业务流规则中过滤条件定义的业务流或分组的目的接口。
步骤502、ME平台管理器确定VIM为转发接口指示所指示的接口分配的地址资源。
步骤503、ME平台管理器根据地址资源以及预设置的业务流规则确定待配置的业务流规则，待配置的业务流规则中转发接口指示与地址资源相关联。其中，转发接口指示与地址资源相关联可以有多种实现方式，包括但不限于：在转发接口描述中添加该地址资源的标识，或者在转发接口描述中添加该地址资源对应的地址或地址范围，或者，在该转发接口描述中添加指向该地址资源的其它信息，或者，在AppD的应用接口描述中添加从AppExtCp指向该转发接口描述的信息，例如该转发接口描述的编号。又或者，ME平台管理器维护有转发接口指示/转发接口描述/业务流规则与该地址资源的映射。
上述技术方案中，ME应用的应用描述符中可以不设置转发接口的地址，而是添加转发接口的指示信息(如AppExtCp)，待到VIM为该转发接口分配地址资源之后，再将分配的地址资源与该转发接口指示/转发接口描述/业务流规则相关联，比如根据指定的接口类型信息，将所分配的MAC和/或IP地址与业务流规则做关联，实现转发业务流规则的过滤规则指示的业务流或分组的接口的地址的设置，上述方法不仅可以适用于ME应用接口的地址资源动态分配的场景，而且避免为ME应用配置固定地址导致的地址资源利用率低下。
作为一种可选的方式，参照图8，在步骤503之后，还包括：
步骤504、ME平台管理器向管理ME应用的ME平台发送配置请求，配置请求包括待配置的业务流规则，用于请求ME平台配置所述待配置的业务流规则，根据配置的业务流规则将所述过滤条件指示的分组转发至所述ME应用的使用该地址资源的接口。
上述技术方案中，通过将待配置的业务流规则向ME应用实例进行配置，使得ME平台将过滤条件指示的业务流或分组转发至为ME应用实例的接口，该接口的地址可动态分配。
作为一种可选的方式，步骤504之后，ME平台对ME应用实例进行配置，配置ME应用实例的使用该地址资源的接口接收该过滤条件指示的分组。
作为一种可选的方式，继续参照图8，在步骤504之后，还包括：
步骤505、在转发接口指示所指示的接口分配的地址资源发生变更后，ME平台管理器确定更新的业务流规则，更新的业务流规则中的转发接口指示与变更后的地址资源相关联。
步骤506、ME平台管理器向ME平台发送重配置请求，重配置请求包括更新的业务流规则，用于请求ME平台配置所述更新的业务流规则，根据配置的更新的业务流规则将所述过滤条件指示的分组转发至所述ME应用的使用变更后的地址资源的接口。
上述技术方案中，在ME应用的接口的地址资源发生变更后，ME平台管理器更新业务流规则，通过更新的业务流规则对ME平台进行重配置，实现将过滤条件指示的业务流或分组转发至ME应用实例的接口，该接口的地址可动态变更。
图9示出图7至图8所述配置方法在ME应用实例化流程中的应用。应理解，图8所示的流程只是本申请实施例提供的配置方法的一种可能应用，不能将本申请实施例的保护范围限定为图9所示的方案。参照图9，ME应用实例化的流程包括：
步骤601：OSS向ME编排器发送应用实例化请求。
步骤602：ME编排器向ME平台管理器发送应用实例化请求。
步骤603：ME平台管理器向VIM发送资源分配请求，请求参数中包含应用的接口数量及每个接口动态分配地址的需求，如协议类型、分配地址范围等。
步骤604：VIM完成资源分配后，向ME平台管理器发送资源分配应答，包含应用各接口实际分配的地址信息或能够用于查询所分配地址的资源对象标识。
步骤605：ME平台管理器将获取到的接口地址信息与AppD中的应用接口、转发规则描述进行对应，确定实际需要进行配置的业务流规则。比如：
AppD中的业务流规则定义如下：
源IP地址为192.168.2.1的数据包转发到AppExtCpId为Eth1的接口上。ME平台管理器在步骤603根据AppD中对Eth1的描述向VIM分配资源，并在步骤604(或通过步骤604中的资源对象标识查询)获得实例化之后Eth1实际分配到的地址，如10.1.1.1。MEPM将AppD中的业务流规则转换为：将源IP地址为192.168.2.1的数据包发送到地址为10.1.1.1的接口，并作为请求参数在第6步中发送。
步骤606：ME平台管理器将业务流规则下发给ME平台进行配置。
步骤607：ME平台对ME应用实例进行相关配置。
步骤608：ME应用实例向ME平台返回配置应答。
步骤609：ME平台向ME平台管理器返回配置应答。
步骤610：ME平台管理器向ME编排器返回实例化应答。
步骤611：ME编排器向OSS返回实例化应答。
上述技术方案中，在应用实例化的过程中实现动态分配的转发接口的地址的配置，效率较高。
应理解，上述图2至图6中任一所述的配置方法与图7至图9中任一所述的配置方法可以结合实现，即，在同一MEC架构中，上述图2至图6中任一所述的配置方法与图7至图9中任一所述的配置方法可以同时实施。
图10示出本申请实施例的一种配置装置，该配置装置可用于实现图2-图9任一对应的配置方法中ME平台管理器的功能。该配置装置包括：确定模块71、通信模块72以及关联模块73。
其中，确定模块71，用于确定实例化的第一ME应用至第一目的应用的网络转发路径NFP，所述NFP用于指示由所述第一ME应用发送至所述第一目的应用的业务流或分组的转发路径。通信模块72，用于向VIM发送NFP创建请求，请求所述VIM创建所述ME平台管理器确定的所述NFP。关联模块73，用于将所述VIM创建的所述NFP与所述第一ME应用配置的第一业务流规则关联。
作为一种可选的方式，所述通信模块72还用于：向管理所述第一ME应用的ME平台发送配置请求，请求所述ME平台对所述第一ME应用的实例进行配置，将创建的所述NFP与所述第一业务流规则关联。
作为一种可选的方式，所述确定模块71，具体用于：根据所述第一业务流规则确定所述第一目的应用的主机地址；根据所述第一ME应用的主机地址以及所述第一目的应用的主机地址确定所述NFP。
作为一种可选的方式，所述NFP包括所述第一ME应用的业务流或分组到所述第一目的应用所经过的网络功能节点的连接点，按照转发所述分组经过的前后跳顺序所形成的连接点序列。
作为一种可选的方式，所述确定模块71还用于：确定实例化的第二ME应用的主机地址与所述第一ME应用的主机地址相同，以及，所述第二ME应用配置的第二业务流规则中的第二目的应用的主机地址与所述第一目的应用的主机地址相同；
所述关联模块73还用于：将所述第二业务流规则与创建的所述NFP关联。
作为一种可选的方式，配置装置还包括：
释放模块74，用于检查是否存在关联创建的所述NFP的ME应用实例；若不存在，则指示所述VIM释放创建的所述NFP。
作为一种可选的方式，所述确定模块71还用于：在确定所述NFP之前，从所述第一ME应用的应用描述符获取预设置的第一业务流规则，所述预设置的第一业务流规则包括过滤条件以及转发接口描述，所述转发接口描述包括转发接口指示；确定所述VIM为所述转发接口指示所指示的接口分配的地址资源；根据所述地址资源以及所述预设置的第一业务流规则确定待配置的第一业务流规则，所述待配置的第一业务流规则中的所述转发接口指示与所述地址资源相关联。
作为一种可选的方式，所述通信模块72还用于：向所述ME平台发送配置请求，所述配置请求包括所述待配置的第一业务流规则，用于请求所述ME平台配置所述待配置的第一业务流规则，根据配置的第一业务流规则将所述过滤条件指示的分组转发至所述第一ME应用的使用所述地址资源的接口。
作为一种可选的方式，所述确定模块71还用于：在所述转发接口指示所指示的接口分配的地址资源发生变更后，确定更新的第一业务流规则，所述更新的第一业务流规则中的所述转发接口指示与变更后的地址资源相关联；
所述通信模块72，还用于：向所述ME平台发送重配置请求，所述重配置请求包括所述更新的第一业务流规则，用于请求所述ME平台配置所述更新的第一业务流规则，根据配置的更新的第一业务流规则将所述过滤条件指示的分组转发至所述第一ME应用的使用更新后的地址资源的接口。
本发明实施例中对模块的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，另外，在本发明各个实施例中的各功能模块可以集成在一个处理器中，也可以是单独物理存在，也可以两个或两个以上模块集成在一个模块中。上述集成的模块既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。
其中，集成的模块采用硬件的形式实现时，如图11所示，配置装置可以包括处理器81。上述确定模块71、关联模块73以及释放模块74对应的实体的硬件可以为处理器81。处理器81，可以是一个或多个中央处理单元(central processing unit，CPU)，或者为数字处理模块等。该配置装置还可以包括通信接口82，处理器81通过通信接口82与主机或网络管理装置通信。上述通信模块72对应的实体的硬件可以是通信接口82。该配置装置还包括：存储器83，用于存储处理器81执行的程序。存储器83可以是非易失性存储器，比如硬盘(harddisk drive，HDD)或固态硬盘(solid-state drive，SSD)等，还可以是易失性存储器(volatile memory)，例如随机存取存储器(random-access memory，RAM)。存储器63是能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质，但不限于此。
上述配置装置及其组成模块的实现方式可以参照图2至图9任一对应的配置方法中由ME平台管理器执行的步骤，在此不再重复。
图12示出本申请实施例的另一配置装置，该配置装置可用于实现图7-图9任一对应的配置方法中ME平台管理器的功能。该配置装置包括：获取模块91、确定模块92。
其中，获取模块91，用于从ME应用的应用描述符获取预设置的业务流规则，所述预设置的业务流规则包括过滤条件以及转发接口描述，所述转发接口描述包括转发接口指示；确定模块92，用于确定VIM为所述转发接口指示所指示的接口分配的地址资源；根据所述地址资源以及所述预设置的业务流规则确定待配置的业务流规则，所述待配置的业务流规则中所述转发接口指示与所述地址资源相关联。
作为一种可选的方式，配置装置还包括：通信模块93，用于在所述确定模块确定待配置的业务流规则之后，向管理所述ME应用的ME平台发送配置请求，所述配置请求包括所述待配置的业务流规则，用于请求所述ME平台配置所述待配置的业务流规则，根据配置的业务流规则将所述过滤条件指示的分组转发至所述ME应用的使用所述地址资源的接口。
作为一种可选的方式，所述确定模块92还用于：在所述转发接口指示所指示的接口分配的地址资源发生变更后，确定更新的业务流规则，所述更新的业务流规则中的所述转发接口指示与变更后的地址资源相关联；所述通信模块93，还用于：向所述ME平台发送重配置请求，所述重配置请求包括所述更新的业务流规则，用于请求所述ME平台配置所述更新的业务流规则，根据配置的更新的业务流规则将所述过滤条件指示的分组转发至所述ME应用的使用变更后的地址资源的接口。
上述集成的模块采用硬件的形式实现时，配置装置可以包括处理器。上述获取模块91、确定模块92对应的实体的硬件可以为处理器。该配置装置还可以包括通信接口，处理器通过通信接口与主机或网络管理装置通信。上述通信模块93对应的实体的硬件可以是通信接口。该配置装置还包括：存储器，用于存储处理器执行的程序。存储器可以是非易失性存储器，比如硬盘(hard disk drive，HDD)或固态硬盘(solid-state drive，SSD)等，还可以是易失性存储器(volatile memory)，例如随机存取存储器(random-access memory，RAM)。存储器63是能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质，但不限于此。
上述配置装置及其组成模块的实现方式可以参照图7至图9任一对应的配置方法中由ME平台管理器执行的步骤，在此不再重复。
本申请实施例还提供一种创建资源的装置，包括：通信模块以及资源创建模块。通信模块，用于接收ME平台管理器发送的NFP创建请求，所述NFP请求包括所述ME平台管理器生成的NFP。资源创建模块，用于创建所述NFP。所述通信模块，还用于向所述ME平台管理器返回创建结果。
上述配置装置及其组成模块的实现方式可以参照图2至图6任一对应的配置方法中由 VIM执行的步骤，在此不再重复。
本申请实施例还提供一种配置装置，包括：通信模块以及配置模块。通信模块，用于接收ME平台管理器发送的配置请求，所述配置请求包括创建的NFP的标识以及ME应用的业务流规则的标识。配置模块，用于对所述ME应用的实例进行配置，将所述NFP的标识与所述业务流规则的标识关联。
上述配置装置及其组成模块的实现方式可以参照图2至图9任一对应的配置方法中由ME平台执行的步骤，在此不再重复。
本申请提供一种计算机可读存储介质，该可读存储介质中存储有计算机指令，所述指令在计算机上运行时，使得计算机执行上述图2至图9任一对应的配置方法。
本申请提供一种计算机程序产品，所述计算机程序产品在计算机上运行时，使得计算机执行上述图2至图9任一对应的配置方法。
本申请是参照根据本申请的方法、设备(系统)、和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器，使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中，使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品，该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
以上，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以权利要求的保护范围为准。

Claims (28)

  1. 一种配置方法，其特征在于，包括：
    移动边缘ME平台管理器确定实例化的第一ME应用至第一目的应用的网络转发路径NFP，所述NFP用于指示由所述第一ME应用发送至所述第一目的应用的业务流或分组的转发路径；
    所述ME平台管理器向虚拟化基础设施管理器VIM发送NFP创建请求，请求所述VIM创建所述ME平台管理器确定的所述NFP；
    所述ME平台管理器将所述VIM创建的所述NFP与所述第一ME应用配置的第一业务流规则关联。
  2. 根据权利要求1所述的方法，其特征在于，还包括：
    所述ME平台管理器向管理所述第一ME应用的ME平台发送配置请求，请求所述ME平台对所述第一ME应用的实例进行配置，将创建的所述NFP与所述第一业务流规则关联。
  3. 根据权利要求1或2所述的方法，其特征在于，所述ME平台管理器确定所述第一ME应用至第一目的应用的NFP，包括：
    所述ME平台管理器根据所述第一业务流规则确定所述第一目的应用的主机地址；
    所述ME平台管理器根据所述第一ME应用的主机地址以及所述第一目的应用的主机地址确定所述NFP。
  4. 根据权利要求3所述的方法，其特征在于，所述NFP包括所述第一ME应用的业务流或分组到所述第一目的应用所经过的网络功能节点的连接点，按照转发所述分组经过的前后跳顺序所形成的连接点序列。
  5. 根据权利要求1-4任一项所述的方法，其特征在于，还包括：
    所述ME平台管理器确定实例化的第二ME应用的主机地址与所述第一ME应用的主机地址相同，以及，所述第二ME应用配置的第二业务流规则中的第二目的应用的主机地址与所述第一目的应用的主机地址相同；
    所述ME平台管理器将所述第二业务流规则与创建的所述NFP关联。
  6. 根据权利要求1-5任一项所述的方法，其特征在于，还包括：
    所述ME平台管理器检查是否存在关联创建的所述NFP的ME应用实例；
    若不存在，则指示所述VIM释放所述NFP。
  7. 根据权利要求1-6任一项所述的方法，其特征在于，在所述ME平台管理器确定所述NFP之前，还包括：
    所述ME平台管理器从所述第一ME应用的应用描述符获取预设置的第一业务流规则，所述预设置的第一业务流规则包括过滤条件以及转发接口描述，所述转发接口描述包括转发接口指示；
    所述ME平台管理器确定所述VIM为所述转发接口指示所指示的接口分配的地址资源；
    所述ME平台管理器根据所述地址资源以及所述预设置的第一业务流规则确定待配置的第一业务流规则，所述待配置的第一业务流规则中的所述转发接口指示与所述地址资源相关联。
  8. 根据权利要求7所述的方法，其特征在于，在所述ME平台管理器确定所述待配置的第一业务流规则之后，还包括：
    所述ME平台管理器向所述ME平台发送配置请求，所述配置请求包括所述待配置的第一 业务流规则，用于请求所述ME平台配置所述待配置的第一业务流规则，根据配置的第一业务流规则将所述过滤条件指示的分组转发至所述第一ME应用的使用所述地址资源的接口。
  9. 根据权利要求8所述的方法，其特征在于，还包括：
    在所述转发接口指示所指示的接口分配的地址资源发生变更后，所述ME平台管理器确定更新的第一业务流规则，所述更新的第一业务流规则中的所述转发接口指示与变更后的地址资源相关联；
    所述ME平台管理器向所述ME平台发送重配置请求，所述重配置请求包括所述更新的第一业务流规则，用于请求所述ME平台配置所述更新的第一业务流规则，根据配置的更新的第一业务流规则将所述过滤条件指示的分组转发至所述第一ME应用的使用更新后的地址资源的接口。
  10. 一种配置方法，其特征在于，包括：
    ME平台管理器从ME应用的应用描述符获取预设置的业务流规则，所述预设置的业务流规则包括过滤条件以及转发接口描述，所述转发接口描述包括转发接口指示；
    所述ME平台管理器确定VIM为所述转发接口指示所指示的接口分配的地址资源；
    所述ME平台管理器根据所述地址资源以及所述预设置的业务流规则确定待配置的业务流规则，所述待配置的业务流规则中所述转发接口指示与所述地址资源相关联。
  11. 根据权利要求10所述的方法，其特征在于，在所述ME平台管理器确定待配置的业务流规则之后，还包括：
    所述ME平台管理器向管理所述ME应用的ME平台发送配置请求，所述配置请求包括所述待配置的业务流规则，用于请求所述ME平台配置所述待配置的业务流规则，根据配置的业务流规则将所述过滤条件指示的分组转发至所述ME应用的使用所述地址资源的接口。
  12. 根据权利要求11所述的方法，其特征在于，还包括：
    在所述转发接口指示所指示的接口分配的地址资源发生变更后，所述ME平台管理器确定更新的业务流规则，所述更新的业务流规则中的所述转发接口指示与变更后的地址资源相关联；
    所述ME平台管理器向所述ME平台发送重配置请求，所述重配置请求包括所述更新的业务流规则，用于请求所述ME平台配置所述更新的业务流规则，根据配置的更新的业务流规则将所述过滤条件指示的分组转发至所述ME应用的使用变更后的地址资源的接口。
  13. 一种创建资源的方法，其特征在于，包括：
    VIM接收ME平台管理器发送的NFP创建请求，所述NFP创建请求包括所述ME平台管理器生成的NFP；
    所述VM创建所述NFP，并向所述ME平台管理器返回NFP创建结果。
  14. 一种配置方法，其特征在于，包括：
    ME平台接收ME平台管理器发送的配置请求，所述配置请求包括创建的NFP的标识以及ME应用的业务流规则的标识；
    所述ME平台对所述ME应用的实例进行配置，将所述NFP的标识与所述业务流规则的标识关联。
  15. 一种配置装置，其特征在于，包括：
    确定模块，用于确定实例化的第一ME应用至第一目的应用的网络转发路径NFP，所述NFP用于指示由所述第一ME应用发送至所述第一目的应用的业务流或分组的转发路径；
    通信模块，用于向VIM发送NFP创建请求，请求所述VIM创建所述ME平台管理器确定的所述NFP；
    关联模块，用于将所述VIM创建的所述NFP与所述第一ME应用配置的第一业务流规则关联。
  16. 根据权利要求15所述的装置，其特征在于，所述通信模块还用于：向管理所述第一ME应用的ME平台发送配置请求，请求所述ME平台对所述第一ME应用的实例进行配置，将创建的所述NFP与所述第一业务流规则关联。
  17. 根据权利要求15或16所述的装置，其特征在于，所述确定模块，具体用于：根据所述第一业务流规则确定所述第一目的应用的主机地址；根据所述第一ME应用的主机地址以及所述第一目的应用的主机地址确定所述NFP。
  18. 根据权利要求17所述的装置，其特征在于，所述NFP包括所述第一ME应用的业务流或分组到所述第一目的应用所经过的网络功能节点的连接点，按照转发所述分组经过的前后跳顺序所形成的连接点序列。
  19. 根据权利要求15-18任一项所述的装置，其特征在于，所述确定模块还用于：确定实例化的第二ME应用的主机地址与所述第一ME应用的主机地址相同，以及，所述第二ME应用配置的第二业务流规则中的第二目的应用的主机地址与所述第一目的应用的主机地址相同；
    所述关联模块还用于：将所述第二业务流规则与创建的所述NFP关联。
  20. 根据权利要求15-19任一项所述的装置，其特征在于，还包括：
    释放模块，用于检查是否存在关联创建的所述NFP的ME应用实例；若不存在，则指示所述VIM释放创建的所述NFP。
  21. 根据权利要求15-20任一项所述的装置，其特征在于，所述确定模块还用于：在确定所述NFP之前，从所述第一ME应用的应用描述符获取预设置的第一业务流规则，所述预设置的第一业务流规则包括过滤条件以及转发接口描述，所述转发接口描述包括转发接口指示；确定所述VIM为所述转发接口指示所指示的接口分配的地址资源；根据所述地址资源以及所述预设置的第一业务流规则确定待配置的第一业务流规则，所述待配置的第一业务流规则中的所述转发接口指示与所述地址资源相关联。
  22. 根据权利要求21所述的装置，其特征在于，所述通信模块还用于：向所述ME平台发送配置请求，所述配置请求包括所述待配置的第一业务流规则，用于请求所述ME平台配置所述待配置的第一业务流规则，根据配置的第一业务流规则将所述过滤条件指示的分组转发至所述第一ME应用的使用所述地址资源的接口。
  23. 根据权利要求22所述的装置，其特征在于，所述确定模块还用于：在所述转发接口指示所指示的接口分配的地址资源发生变更后，确定更新的第一业务流规则，所述更新的第一业务流规则中的所述转发接口指示与变更后的地址资源相关联；
    所述通信模块，还用于：向所述ME平台发送重配置请求，所述重配置请求包括所述更新的第一业务流规则，用于请求所述ME平台配置所述更新的第一业务流规则，根据配置的更新的第一业务流规则将所述过滤条件指示的分组转发至所述第一ME应用的使用更新后的地址资源的接口。
  24. 一种配置装置，其特征在于，包括：
    获取模块，用于从ME应用的应用描述符获取预设置的业务流规则，所述预设置的业务流规则包括过滤条件以及转发接口描述，所述转发接口描述包括转发接口指示；
    确定模块，用于确定VIM为所述转发接口指示所指示的接口分配的地址资源；根据所述地址资源以及所述预设置的业务流规则确定待配置的业务流规则，所述待配置的业务流规则中所述转发接口指示与所述地址资源相关联。
  25. 根据权利要求24所述的装置，其特征在于，还包括：
    通信模块，用于在所述确定模块确定待配置的业务流规则之后，向管理所述ME应用的ME平台发送配置请求，所述配置请求包括所述待配置的业务流规则，用于请求所述ME平台配置所述待配置的业务流规则，根据配置的业务流规则将所述过滤条件指示的分组转发至所述ME应用的使用所述地址资源的接口。
  26. 根据权利要求25所述的装置，其特征在于，所述确定模块还用于：在所述转发接口指示所指示的接口分配的地址资源发生变更后，确定更新的业务流规则，所述更新的业务流规则中的所述转发接口指示与变更后的地址资源相关联；
    所述通信模块，还用于：向所述ME平台发送重配置请求，所述重配置请求包括所述更新的业务流规则，用于请求所述ME平台配置所述更新的业务流规则，根据配置的更新的业务流规则将所述过滤条件指示的分组转发至所述ME应用的使用变更后的地址资源的接口。
  27. 一种创建资源的装置，其特征在于，包括：
    通信模块，用于接收ME平台管理器发送的NFP创建请求，所述NFP请求包括所述ME平台管理器生成的NFP；
    资源创建模块，用于创建所述NFP；
    所述通信模块，还用于向所述ME平台管理器返回创建结果。
  28. 一种配置装置，其特征在于，包括：
    通信模块，用于接收ME平台管理器发送的配置请求，所述配置请求包括创建的NFP的标识以及ME应用的业务流规则的标识；
    配置模块，用于对所述ME应用的实例进行配置，将所述NFP的标识与所述业务流规则的标识关联。
PCT/CN2018/116348 2017-11-21 2018-11-20 一种配置方法及装置 WO2019101056A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP18880585.7A EP3703321B1 (en) 2017-11-21 2018-11-20 Configuration method and apparatus
US16/877,322 US11570277B2 (en) 2017-11-21 2020-05-18 Configuration method and apparatus

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201711167051.3A CN109818867B (zh) 2017-11-21 2017-11-21 一种配置方法及装置
CN201711167051.3 2017-11-21

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/877,322 Continuation US11570277B2 (en) 2017-11-21 2020-05-18 Configuration method and apparatus

Publications (1)

Publication Number Publication Date
WO2019101056A1 true WO2019101056A1 (zh) 2019-05-31

Family

ID=66600476

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/116348 WO2019101056A1 (zh) 2017-11-21 2018-11-20 一种配置方法及装置

Country Status (4)

Country Link
US (1) US11570277B2 (zh)
EP (1) EP3703321B1 (zh)
CN (2) CN109818867B (zh)
WO (1) WO2019101056A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022021176A1 (zh) * 2020-07-28 2022-02-03 苏州大学 云边协同网络资源平滑迁移与重构方法及系统
CN114079637A (zh) * 2020-08-04 2022-02-22 中国移动通信集团重庆有限公司 基于移动边缘计算的业务处理方法及系统

Families Citing this family (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11290561B2 (en) * 2019-02-07 2022-03-29 Verizon Patent And Licensing Inc. Methods and systems for managing applications of a multi-access edge computing environment
CN111949364A (zh) * 2019-05-16 2020-11-17 华为技术有限公司 容器化vnf的部署方法和相关设备
US11489930B2 (en) * 2019-06-11 2022-11-01 At&T Intellectual Property I, L.P. Telecommunication network edge cloud interworking via edge exchange point
CN113381871B (zh) * 2020-03-10 2023-04-07 中国电信股份有限公司 移动边缘业务编排方法、编排器和移动边缘计算系统
CN113411200B (zh) * 2021-05-08 2022-07-15 中国科学院计算技术研究所 一种基于仿真网络封装、解封及传输虚拟流量的方法及系统
EP4375092A1 (de) 2022-11-24 2024-05-29 Reinhold Schulte Reifendruckventilbaugruppe und gruppe mit reifendruckventilbaugruppen

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107305502A (zh) * 2016-04-21 2017-10-31 中兴通讯股份有限公司 一种应用实例迁移的方法及设备

Family Cites Families (17)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102714628B (zh) * 2010-01-05 2015-11-25 日本电气株式会社 通信系统、控制装置、处理规则设置方法和分组传输方法
WO2013035342A1 (en) * 2011-09-09 2013-03-14 Nec Corporation Network management service system, control apparatus, method, and program
CN103430516B (zh) 2013-02-21 2017-02-22 华为技术有限公司 业务提供系统、方法、移动边缘应用服务器及支持节点
EP3094049B1 (en) * 2014-01-29 2018-01-10 Huawei Technologies Co., Ltd. Method for upgrading virtualized network function and network function virtualization orchestrator
EP3138251A4 (en) * 2014-04-28 2017-09-13 Hewlett-Packard Enterprise Development LP Data distribution based on network information
US10257869B2 (en) * 2014-10-29 2019-04-09 Hewlett Packard Enterprise Development Lp Dynamically including an active tunnel as a member of a virtual network
US9560078B2 (en) * 2015-02-04 2017-01-31 Intel Corporation Technologies for scalable security architecture of virtualized networks
US9769694B2 (en) * 2015-03-13 2017-09-19 Intel IP Corporation MME overload or underload mitigation by MME VNF apparatus and method
CN106302574B (zh) * 2015-05-15 2019-05-28 华为技术有限公司 一种业务可用性管理方法、装置及其网络功能虚拟化架构
WO2017020203A1 (zh) * 2015-07-31 2017-02-09 华为技术有限公司 路由规则的获取方法、设备和系统
US10447605B2 (en) * 2015-10-27 2019-10-15 Avago Technologies International Sales Pte. Limited Flow-based host discovery in SDN networks
US10129108B2 (en) * 2015-11-13 2018-11-13 Huawei Technologies Co., Ltd. System and methods for network management and orchestration for network slicing
CN106921977B (zh) * 2015-12-26 2020-11-06 华为技术有限公司 一种基于业务流的服务质量规划方法、装置及系统
WO2018059682A1 (en) * 2016-09-29 2018-04-05 Nokia Solutions And Networks Oy Enhancement of traffic detection and routing in virtualized environment
CN108307434B (zh) * 2017-01-12 2023-04-07 马维尔以色列(M.I.S.L.)有限公司 用于流控制的方法和设备
CN108574728B (zh) * 2017-03-08 2021-05-04 中兴通讯股份有限公司 用于移动边缘计算的流量路径改变检测的方法和装置
WO2019086719A1 (en) * 2017-11-06 2019-05-09 Athonet S.R.L. Policy-driven local offload of selected user data traffic at a mobile edge computing platform

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107305502A (zh) * 2016-04-21 2017-10-31 中兴通讯股份有限公司 一种应用实例迁移的方法及设备

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
INTEL.: "Paper to discuss edge computing management issues", 3GPP TSG SA WG5 MEETING #115, 6 October 2017 (2017-10-06), XP051361963 *
See also references of EP3703321A4

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022021176A1 (zh) * 2020-07-28 2022-02-03 苏州大学 云边协同网络资源平滑迁移与重构方法及系统
CN114079637A (zh) * 2020-08-04 2022-02-22 中国移动通信集团重庆有限公司 基于移动边缘计算的业务处理方法及系统
CN114079637B (zh) * 2020-08-04 2023-10-27 中国移动通信集团重庆有限公司 基于移动边缘计算的业务处理方法及系统

Also Published As

Publication number Publication date
EP3703321A4 (en) 2020-11-18
CN112202673A (zh) 2021-01-08
CN112202673B (zh) 2022-01-04
CN109818867B (zh) 2020-10-27
CN109818867A (zh) 2019-05-28
EP3703321A1 (en) 2020-09-02
EP3703321C0 (en) 2023-06-07
US11570277B2 (en) 2023-01-31
US20200329119A1 (en) 2020-10-15
EP3703321B1 (en) 2023-06-07

Similar Documents

Publication Publication Date Title
WO2019101056A1 (zh) 一种配置方法及装置
US10375015B2 (en) Methods and system for allocating an IP address for an instance in a network function virtualization (NFV) system
US20240223612A1 (en) Method and system for virtual machine aware policy management
US9749145B2 (en) Interoperability for distributed overlay virtual environment
US10397132B2 (en) System and method for granting virtualized network function life cycle management
US8819211B2 (en) Distributed policy service
US20120297384A1 (en) Virtual Managed Network
US10594586B2 (en) Dialing test method, dialing test system, and computing node
CN108737271B (zh) 一种报文路由方法、装置及系统
CN111835878A (zh) 混合云管理方法、装置和计算设备
WO2018218977A1 (zh) 一种编排软件定义网络的方法及sdn控制器
US11625280B2 (en) Cloud-native proxy gateway to cloud resources
WO2017113300A1 (zh) 路由确定方法、网络配置方法以及相关装置
WO2020253631A1 (zh) Ip地址的配置方法、设备及系统
CN111130838B (zh) 一种进程级服务实例动态扩展及网络带宽限制方法及装置
US10237235B1 (en) System for network address translation
CN110798541B (zh) 接口共享、报文转发方法、装置、电子设备及存储介质
CN106471777B (zh) 网络资源均衡的方法和装置
CN110336730B (zh) 一种网络系统及数据传输方法
WO2023030218A1 (zh) 网络业务部署方法、nfvo以及nfv系统
CN113127145B (zh) 信息处理方法、装置以及存储介质
WO2022089645A1 (zh) 通信方法、装置、设备、系统及计算机可读存储介质
CN118118348A (zh) 一种虚拟化网络功能vnf的实例化方法及装置
WO2021121595A1 (en) Discovering an instance of a virtual network function

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: 18880585

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2018880585

Country of ref document: EP

Effective date: 20200526