WO2017162089A1 - 网络服务的业务配置方法和装置 - Google Patents

网络服务的业务配置方法和装置 Download PDF

Info

Publication number
WO2017162089A1
WO2017162089A1 PCT/CN2017/076928 CN2017076928W WO2017162089A1 WO 2017162089 A1 WO2017162089 A1 WO 2017162089A1 CN 2017076928 W CN2017076928 W CN 2017076928W WO 2017162089 A1 WO2017162089 A1 WO 2017162089A1
Authority
WO
WIPO (PCT)
Prior art keywords
service
service configuration
configuration
network
event
Prior art date
Application number
PCT/CN2017/076928
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 EP17769366.0A priority Critical patent/EP3373518B1/en
Publication of WO2017162089A1 publication Critical patent/WO2017162089A1/zh
Priority to US16/012,893 priority patent/US10911331B2/en

Links

Images

Classifications

    • 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/0895—Configuration of virtualised networks or elements, e.g. virtualised network function or OpenFlow elements
    • 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/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
    • H04L41/5041—Network service management, e.g. ensuring proper service fulfilment according to agreements characterised by the time relationship between creation and deployment of a service
    • H04L41/5054—Automatic deployment of services triggered by the service manager, e.g. service implementation by automatic configuration of network components
    • 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/084—Configuration by using pre-existing information, e.g. using templates or copying from other elements
    • H04L41/0843—Configuration by using pre-existing information, e.g. using templates or copying from other elements based on generic templates
    • 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/0876—Aspects of the degree of configuration automation
    • H04L41/0886—Fully automatic configuration
    • 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/0896—Bandwidth or capacity management, i.e. automatically increasing or decreasing capacities
    • H04L41/0897—Bandwidth or capacity management, i.e. automatically increasing or decreasing capacities by horizontal or vertical scaling of resources, or by migrating entities, e.g. virtual resources or entities
    • 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/40—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks using virtualisation of network functions or resources, e.g. SDN or NFV entities
    • 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/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
    • 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/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
    • H04L41/5041—Network service management, e.g. ensuring proper service fulfilment according to agreements characterised by the time relationship between creation and deployment of a service
    • H04L41/5048—Automatic or semi-automatic definitions, e.g. definition templates
    • 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/0806—Configuration setting for initial configuration or provisioning, e.g. plug-and-play
    • 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
    • H04L41/082—Configuration setting characterised by the conditions triggering a change of settings the condition being updates or upgrades of network functionality

Definitions

  • the embodiments of the present invention relate to communication technologies, and in particular, to a service configuration method and apparatus for a network service.
  • the European Telecommunications Standards Association ETSI
  • NFV ISG Network Function Virtulization Industry Specification Group
  • IT Internet Technology
  • MME Mobile Management Entity
  • VNF virtualized network function
  • VMs virtual machines
  • the NFV-MANO can be used to manage the Network Function Virtualization Infrastructure (NFV Infrastructure).
  • the NFVI is composed of hardware resources and virtual resources
  • the NS is a network service composed of multiple VNFs or multiple VNFs and PNFs to provide more complicated functions, for example, by a virtual or physical MME, a service gateway (Serving GateWay).
  • An Evolved Packet Core (EPC) consisting of a Home Subscriber Server (HSS) and a virtual link between them can be called an NS.
  • EPC Evolved Packet Core
  • VNF management The above-mentioned NFV-MANO management and orchestration capabilities of the VNF actually include traditional fault management, configuration management, billing management, performance management, and security management (Fault Management, Accounting Management, Performance Management, Security Management, FCAPS).
  • FCAPS Fault Management, Accounting Management, Performance Management, Security Management, FCAPS.
  • VNF management the management capabilities of the NFVI resources required to create VNF and VNF lifecycle management, collectively referred to as VNF management.
  • VNF management needs to support VNF lifecycle management capabilities, including at least the following operational functions: VNF instantiation (creating a VNF), VNF resiliency (increasing or decreasing VNF capacity), VNF updates and upgrades (VNF software and configuration changes) VNF terminates (releases the NFVI resources occupied by the VNF).
  • VNF can provide services to the VNF.
  • the VNF needs to support the VNF service configuration.
  • the VNF instantiation process needs to include the VNF service. Configuration), where the service configuration of the VNF is related to the current network environment of the operator and the specific NS.
  • VNF virtual resource allocation and software installation and "VNF service configuration” which are manually operated by the operator. Perform twice to complete the VNF lifecycle management actions.
  • the service configuration command of the VNF involved is edited and executed by the operator, and it is possible to introduce a human configuration error, and the service configuration of the above VNF requires the operator to perform two operations, interrupting the VNF lifecycle management transaction flow, and the VNF online efficiency. low.
  • the embodiment of the present invention provides a network service service configuration method and device, which are used to solve the technical problem that the VNF service configuration error is caused by the human configuration service command in the prior art, and the VNF online efficiency is low.
  • the embodiment of the present application provides a service configuration method for a network service, including: receiving a network service instantiation request, where the network service instantiation request includes: a preset service of a network service related to an operator network environment.
  • the configuration event is sent to the configuration system according to the service configuration event, so that the configuration system performs service configuration on the network service according to the service configuration information.
  • the service configuration event can effectively reflect the current operator's network environment, and can directly or indirectly provide parameters or scripts required for service configuration when the network service in the NFVMANO system performs service configuration in the current operator's network environment.
  • the form or content of the service configuration event is not limited here, as long as it enables the network service in the NFV MANO system to automatically complete the service configuration without interrupting the instantiation process or other processes.
  • the service configuration information is related to the service configuration event, and may be a direct or indirect form of the service configuration event, and may be other information related to the service configuration event.
  • the specific form of the service configuration information in the embodiment of the present application is not It is limited as long as it enables the network service in the NFV MANO system to automatically complete the service configuration without interrupting the instantiation process or other processes.
  • the service configuration method of the network service provided by the first aspect, by carrying the preset service configuration event of the network service related to the operator network environment in the network service instantiation request sent to the MANO, so that the MANO can according to the service
  • the configuration event sends the service configuration information to the configuration system, so that the configuration system performs service configuration on the network service according to the service configuration information after the MANO completes the resource allocation of the network service and the service software installation, so that the network service is not required to be interrupted manually.
  • the instantiation process that is, does not need to manually modify the service configuration command in the network service service configuration phase, avoids the configuration error caused by the human modification, and also improves the network service because the instantiation process of the network service is not interrupted. On-line efficiency.
  • the service configuration event is used to indicate a service configuration template or a workflow executed by the network service in a current operation scenario.
  • the service configuration event may include an identifier of the service configuration template or a workflow identifier that the network service should perform in the current scenario, and the corresponding service configuration template or the workflow may be stored in the directory server corresponding to the MANO.
  • the service configuration event may directly include the service configuration template or the specific content of the workflow that the network service should perform in the current scenario.
  • the service configuration event includes a service configuration event name, a service configuration template in the current scenario, and a service parameter required to execute the service configuration template.
  • the service configuration information is sent to the configuration system according to the service configuration event, so that the configuration system performs service configuration on the network service according to the service configuration information, which includes: The system sends a service configuration event, so that the configuration system configures event events according to the service The network service performs service configuration.
  • the service configuration information is sent to the configuration system according to the service configuration event, so that the configuration system performs service configuration on the network service according to the service configuration information, which includes: The service configuration event name in the service configuration event, the service configuration template in the current operation scenario, and the service parameter generation service configuration command; sending the service configuration command to the configuration system, so that the The configuration system performs service configuration on the network service according to the service configuration command.
  • the method further includes: receiving a service configuration result sent by the configuration system.
  • the service configuration method of the network service provided by each of the above possible designs, the service configuration information exchanged between the MANO and the configuration system may include different forms, enriching the diversity of the interaction between the MANO and the configuration system, and thus improving the network service. Reliability when configuring the business.
  • the embodiment of the present application provides a service configuration method for a network service, including: receiving service configuration information sent by a management orchestrator MANO according to a service configuration event of a network service related to an operator network environment; The information is configured for the network service.
  • the service configuration event is used to indicate a service configuration template or a workflow executed by the network service in a current operation scenario.
  • the service configuration event includes a service configuration event name, a service configuration template in the current scenario, and a service parameter required to execute the service configuration template.
  • the performing service configuration on the network service according to the service configuration information includes: parsing the service configuration event, obtaining the service configuration event name, and the service in the current scenario.
  • the configuration template and the service parameter are configured to generate a service configuration command according to the service configuration event name, the service configuration template in the current scenario, and the service parameter, and perform service configuration on the network service according to the service configuration command.
  • the service configuration information sent by the receiving management orchestrator MANO according to the service configuration event of the network service related to the network environment of the operator specifically includes: receiving a service configuration command sent by the MANO, The service configuration command is generated by the MANO according to the service configuration event name, the service configuration template in the current scenario, and the service parameter;
  • performing service configuration on the network service according to the service configuration information including: performing service configuration on the network service according to the service configuration command.
  • the method further includes transmitting a service configuration result to the MANO.
  • the second aspect and the possible configuration of the second aspect, the service configuration method of the network service, the beneficial effects can be referred to the first aspect and the beneficial effects brought by the possible designs of the first aspect, where No longer.
  • the embodiment of the present application provides a network service service configuration apparatus, including: a receiving module, configured to receive a network service instantiation request, where the network service instantiation request includes: a preset related to a carrier network environment The service configuration event of the network service, the sending module, configured to send the service configuration information to the configuration system according to the service configuration event, so that the configuration system performs service configuration on the network service according to the service configuration information.
  • the service configuration event is used to indicate a service configuration template or a workflow executed by the network service in a current operation scenario.
  • the service configuration event includes a service configuration event name, a service configuration template in the current scenario, and a service parameter required to execute the service configuration template.
  • the sending module is configured to send a service configuration event to the configuration system, so that the configuration system performs service configuration on the network service according to the service configuration event.
  • the sending module includes: a generating unit, configured to configure, according to the service configuration event, the service configuration event name, the service configuration template in the current operation scenario, and the service parameter. Generating a service configuration command; the sending unit is configured to send the service configuration command to the configuration system, so that the configuration system performs service configuration on the network service according to the service configuration command.
  • the receiving module is further configured to receive a service configuration result sent by the configuration system.
  • the embodiment of the present application provides a network service service configuration apparatus, including: a receiving module, configured to receive service configuration information sent by a management orchestrator MANO according to a service configuration event of a network service related to an operator network environment; And a configuration module, configured to perform service configuration on the network service according to the service configuration information.
  • the service configuration event is used to indicate a service configuration template or a workflow executed by the network service in a current operation scenario.
  • the service configuration event includes a service configuration event name, a service configuration template in the current scenario, and a service parameter required to execute the service configuration template.
  • the configuration module includes: a parsing unit, configured to parse the service configuration event, obtain the service configuration event name, the service configuration template in the current scenario, and the service parameter. a generating unit, configured to generate a service configuration command according to the service configuration event name, the service configuration template in the current scenario, and the service parameter, and a configuration unit, configured to perform, according to the service configuration command, the network service Business configuration.
  • the receiving module is configured to receive a service configuration command sent by the MANO, where the service configuration command is configured by the MANO according to the service, an event name, and a service in the current scenario.
  • the configuration template and the service parameter are generated; the configuration module is specifically configured to perform service configuration on the network service according to the service configuration command.
  • the apparatus further includes: a sending module, configured to send a service configuration result to the MANO.
  • the fourth aspect and the possible configuration of the fourth aspect provide a service configuration method for the network service, and the beneficial effects thereof can be referred to the first aspect and the beneficial effects brought by the possible designs of the first aspect, where No longer.
  • the embodiment of the present application provides a management orchestrator MANO, including: a receiver, configured to receive a network service instantiation request, where the network service instantiation request includes: a preset network environment with a carrier A service configuration event of the related network service; the sender is configured to send the service configuration information to the configuration system according to the service configuration event, so that the configuration system performs service configuration on the network service according to the service configuration information.
  • a management orchestrator MANO including: a receiver, configured to receive a network service instantiation request, where the network service instantiation request includes: a preset network environment with a carrier A service configuration event of the related network service; the sender is configured to send the service configuration information to the configuration system according to the service configuration event, so that the configuration system performs service configuration on the network service according to the service configuration information.
  • the management orchestrator MANO may further include a processor independently connected to the receiver and the transmitter, and having a communication connection with the two, the processor is configured to obtain service configuration information according to the service configuration event, and pass the The transmitter sends the service configuration information to the configuration system.
  • the MANO may include a Network Function Virtulization Orchestration (NFVO), a Virtualized Network Function Management (VNFM) VNFM, and a Virtualized Infrastructure Manager (VIM).
  • NFVO Network Function Virtulization Orchestration
  • VNFM Virtualized Network Function Management
  • VIM Virtualized Infrastructure Manager
  • the components, namely NFVO, VNFM and VIM, are all part of MANO.
  • the three can be deployed on different hardware devices to form all or part of MANO through physical connection, or they can be deployed on the same hardware device (ie in the hardware).
  • the software can load all or part of MANO by loading software with the functions of NFVO, VNFM and VIM mentioned above.
  • the above receiver and transmitter may be integrated on the VNFM; optionally, when the MANO includes NFVO and VNFM deployed on the same hardware device.
  • the integrated location of the receiver and transmitter is not limited.
  • the transmitter may be an output interface having a communication function and a function of transmitting information in the MANO
  • the receiver may be an input interface having a communication function and a receiving information function in the MANO.
  • the service configuration event is used to indicate a service configuration template or a workflow executed by the network service in a current operation scenario.
  • the service configuration event includes a service configuration event name, a service configuration template in the current scenario, and a service parameter required to execute the service configuration template.
  • the sender is specifically configured to send a service configuration event to the configuration system, so that the configuration system performs service configuration on the network service according to the service configuration event.
  • the MANO further includes a processor; optionally, the processor may be a processing chip having a function of generating a service configuration command and other functions, which may be integrated in the VNFM;
  • the processor is configured to generate a service configuration command according to the service configuration event name, the service configuration template in the current operation scenario, and the service parameter in the service configuration event;
  • the transmitter is configured to send the service configuration command generated by the processor to the configuration system, so that the configuration system performs service configuration on the network service according to the service configuration command.
  • the receiver is further configured to receive a service configuration result sent by the configuration system.
  • the fifth aspect and the possible configuration of the fifth aspect provide a service configuration method for the network service, and the beneficial effects thereof can be referred to the first aspect and the beneficial effects brought by the possible designs of the first aspect, where No longer.
  • the embodiment of the present application provides a configuration system, including: a receiver, configured to receive service configuration information sent by a management orchestrator MANO according to a service configuration event of a network service related to an operator network environment; And performing service configuration on the network service according to the service configuration information.
  • the configuration system may be an element management system (EM). It can be an Operation Support System (OSS).
  • EM element management system
  • OSS Operation Support System
  • the above receiver may be an input interface having a communication function and a receiving information function in the configuration system
  • the processor may be a processing chip having a service configuration function and other functions in the configuration system.
  • the service configuration event is used to indicate a service configuration template or a workflow executed by the network service in a current operation scenario.
  • the service configuration event includes a service configuration event name, a service configuration template in the current scenario, and a service parameter required to execute the service configuration template.
  • the processor is configured to parse the service configuration event, obtain the service configuration event name, the service configuration template in the current scenario, and the service parameter, and according to the The service configuration event name, the service configuration template in the current scenario, and the service parameter generate a service configuration command, and perform service configuration on the network service according to the service configuration command.
  • the receiver is configured to receive a service configuration command sent by the MANO, where the service configuration command is configured by the MANO according to the service, an event name, and a service in the current scenario. Configuring a template and the business parameters generated;
  • the processor is specifically configured to perform service configuration on the network service by using the service configuration command.
  • the configuration system further includes: a transmitter for transmitting a service configuration result to the MANO.
  • the transmitter may be an output interface configured to have a communication function and a function of transmitting information in the system.
  • the network service includes a virtual network function VNF
  • the service configuration event is used to indicate a service configuration template or a workflow executed by the VNF in a current operation scenario.
  • the network service includes a virtual network function VNF and a physical network function PNF, where the service configuration event is used to indicate a first service configuration template or a first workflow executed by the VNF in a current operation scenario, and The second service configuration template or the second workflow executed by the PNF.
  • the service configuration event is carried in a virtual network function description VNFD in the VNF instantiation request received by the MANO.
  • the service configuration event is carried in a network service description NSD in the network service instantiation request received by the MANO.
  • the service configuration event is further used to indicate a service configuration template or a workflow executed by the virtualized deployment unit VDU of the VNF in the current operation scenario.
  • the current operation scenario includes any one of an initial scenario, an elastic scenario, an upgrade scenario, a security matrix scenario, and a service termination scenario, where the service parameters include an IP address of the local end, a port number of the local end, and an IP address of the peer end. At least one of an address, a port of the peer, and a type of service supported by the network service.
  • the embodiment of the present application provides a service configuration system for a network service, where the service configuration system may include the MANO involved in each of the foregoing possible designs and the configurations involved in each of the foregoing possible designs.
  • the service configuration system may include the MANO involved in each of the foregoing possible designs and the configurations involved in each of the foregoing possible designs.
  • the MANO can implement a communication connection with the configuration system through a corresponding communication bus and communication interface.
  • the embodiment of the present application further provides a computer program product, where the computer program product includes a computer program, which can be implemented by a processor or other type of chip to implement the foregoing embodiment provided by the present application.
  • the service configuration method of the network service The beneficial effects and specific working principles of the computer program product are referred to the foregoing embodiments, and are not described herein again.
  • FIG. 1 is a first schematic diagram of an NFV MANO architecture provided by an embodiment of the present application
  • FIG. 2 is a signaling flowchart of Embodiment 1 of a service configuration method of a network service according to an embodiment of the present disclosure
  • FIG. 3 is a signaling flowchart of Embodiment 2 of a service configuration method of a network service according to an embodiment of the present disclosure
  • Embodiment 4 is a signaling flowchart of Embodiment 3 of a service configuration method of a network service according to an embodiment of the present disclosure
  • FIG. 5 is a schematic structural diagram of Embodiment 1 of a service configuration apparatus for a network service according to an embodiment of the present disclosure
  • FIG. 6 is a schematic structural diagram of Embodiment 2 of a service configuration apparatus for a network service according to an embodiment of the present disclosure
  • FIG. 7 is a schematic structural diagram of Embodiment 3 of a service configuration apparatus for a network service according to an embodiment of the present disclosure
  • FIG. 8 is a schematic structural diagram of Embodiment 4 of a service configuration apparatus for a network service according to an embodiment of the present disclosure
  • FIG. 9 is a schematic structural diagram of an embodiment of a management arranger according to an embodiment of the present application.
  • FIG. 10 is a schematic structural diagram of an embodiment of a configuration system according to an embodiment of the present disclosure.
  • FIG. 11 is a schematic structural diagram of an embodiment of a service configuration system for a network service according to an embodiment of the present disclosure
  • FIG. 12 is a second diagram of the NFV MANO architecture provided by the embodiment of the present application.
  • the service configuration method of the VNF in the embodiment of the present application may be applied to the NFV MANO architecture shown in FIG. 1.
  • the NFV MANO architecture may include an Operation Support System (OSS) or a service support system (Business Support). System, hereinafter referred to as BSS), configuration system, VNF, Physical Network Function (PNF), Network Function Virtualization Infrastructure (NFV Infrastructure, hereinafter referred to as NFVI), NFV Orchestrator (NFV Orchestrator, hereinafter referred to as NFVO) ), VNF Manager (VNF Manager, hereinafter referred to as VNFM) and Virtual Infrastructure Manager (VIM).
  • the foregoing configuration system may be an Element Management (EM), which may be an OSS.
  • EM Element Management
  • the configuration system is an EM.
  • the above NFVI is composed of hardware resources, virtual resources and virtual layers.
  • VIM is used to control and manage virtualized entities.
  • NFVO is responsible for network side scheduling and management of NFVI resources, and implements NFV service topology on NFVI.
  • VNFM is responsible for the management of the life cycle of VNF instances.
  • NFVO, VNFM and VIM in Figure 1 are all part of MANO.
  • NFVO, VNFM, and VIM can all be deployed on different or the same hardware device, as long as the software with the functions of NFVO, VNFM, and VIM described above is loaded on the hardware device.
  • the configuration system when configuring the VNF service, the configuration system cannot obtain sufficient information from the notification of the MANO to complete the service configuration action of the VNF, and therefore requires an artificial interruption of the VNF instantiation process.
  • the editor has modified the service configuration commands required to configure the system, and then started the configuration system to complete the VNF service configuration. Therefore, the VNF automatic service configuration cannot be implemented, and the technical problems of human configuration errors are easily brought, and the human VNF is interrupted.
  • the instantiation process so there are also technical problems with low efficiency of VNF online.
  • the VNF service configuration method and apparatus provided by the embodiments of the present application are directed to solving the problems of the prior art.
  • FIG. 2 is a signaling flowchart of Embodiment 1 of a service configuration method of a network service according to an embodiment of the present disclosure.
  • the embodiment relates to carrying a service configuration event related to the network environment of the operator in the network service instantiation request sent to the MANO, so that the MANO sends the service configuration information to the configuration system according to the service configuration event, so that the configuration system is configured according to the configuration
  • the method may include:
  • S101 The MANO receives the network service instantiation request.
  • the network service instantiation request includes: a preset service configuration event of a network service related to an operator network environment.
  • the service configuration event can effectively reflect the current operator's network environment, and can provide the service configuration directly or indirectly when the network service in the NFV MANO system is configured in the current carrier's network environment.
  • the parameters or the scripts, etc. are not limited in the form or content of the service configuration event, as long as they enable the network service in the NFV MANO system to automatically complete the service configuration without interrupting the instantiation process or other processes.
  • the network environment of the carrier may be the number of IP addresses in the specific carrier network, or the number of global resources of the signaling point in the carrier network, etc.
  • the specific content is not limited.
  • the network service instantiation request in this embodiment may be initiated by the operator to the MANO, and may also be initiated by other software or hardware devices to the MANO.
  • the operator may send a network service instantiation request to the MANO, and the MANO may transmit the network service instantiation request to the internal VNFM, so that the VNFM parses the network service implementation request.
  • the network service in this embodiment may be composed of a link between the VNF and each VNF, and may also be composed of a link between the VNF, the PNF, and the VNF and the PNF.
  • the link may include The link between the VNF and the VNF may also include a link between the VNF and the PNF, and may also include a link between the PNF and the PNF. Therefore, the foregoing network service instantiation request may be a VNF instantiation request, and may also be an NS instantiation request (if the NS instantiation request is required, the VNF is required to complete the service configuration, and the PNF service configuration is also completed).
  • the network service includes a simple VNF as an example.
  • the VNF provider may pre-define the service configuration event in the VNF package file (VNF Package).
  • VNF Package VNF package file
  • the operator can edit and modify these service configuration events in the current carrier network environment to obtain service configuration events that are adapted to the current carrier network environment.
  • the definition and modification of the service configuration event can also be performed by referring to the above description, except that the definition and modification of the service configuration event of the PNF are added.
  • the foregoing network service instantiation request may carry the VNFD, and may also carry the PNFD, and may also carry the PNFD.
  • the service configuration event of the network service related to the network environment of the operator may be included in the VNFD, and may also be included in the PNFD, and may also be included in the NSD, specifically, the network element included in the network service.
  • Type is a reference.
  • the VNFD can be used to describe the information about the resource needs of the VNF.
  • the PNFD can be used to describe the information about the resource needs of the PNF.
  • the NSD is a network service description template corresponding to the network service, and can be used to describe the information of the NS.
  • VNFs and PNFs included in the NS may include a VNFD in the NSD, and may also include a PNFD, specifically referring to a network element type included in the network service.
  • S102 The MANO parses the network service instantiation request to obtain a service configuration event.
  • the MANO parses the network service, and not only obtains the foregoing service configuration event, but also obtains the related information of the NFVI resource in the VNFD or PNFD or the NSD in the network service instantiation request. Business software installation information. Therefore, the MANO can complete the resource allocation and service installation of the network service according to the NFVI resource allocation information and the service software installation information required by the parsed network service.
  • S103 The MANO sends the service configuration information to the configuration system according to the foregoing service configuration event.
  • the MANO may send the service configuration information to the configuration system according to the foregoing service configuration event, or may be based on the foregoing service when the resource allocation and service installation of the network service are performed.
  • the configuration event sends the service configuration information to the configuration system, and the service configuration information is sent to the configuration system according to the service configuration event before the resource allocation and the service installation of the network service.
  • the embodiment of the present application sends the service configuration information to the configuration system to the MANO.
  • the timing is not limited.
  • the service configuration information is related to the service configuration event, and may be a direct or indirect form of the service configuration event, and may be other information related to the service configuration event.
  • the specific form of the service configuration information in the embodiment of the present application is not It is limited as long as it enables the network service in the NFV MANO system to automatically complete the service configuration without interrupting the instantiation process or other processes.
  • S104 The configuration system performs service configuration on the network service according to the service configuration information.
  • the configuration system directly performs the service on the network service according to the service configuration information after receiving the service configuration information.
  • the configuration system receives the service configuration when the service configuration information is sent to the configuration system by the MANO before the resource allocation and service installation of the network service or when the MANO allocates the resources and services to the network service.
  • the MANO can notify the configuration system of the current resource allocation and service software for the network service. The progress of the installation.
  • the service configuration method of the network service provided by the embodiment of the present application, by carrying the preset service configuration event of the network service related to the operator network environment in the network service instantiation request sent to the MANO, enables the MANO to configure according to the service
  • the event sends the service configuration information to the configuration system, so that the configuration system performs service configuration on the network service according to the service configuration information after the MANO completes the resource allocation of the network service and the service software installation.
  • the method provided in this embodiment carries a pre-configured service configuration event related to the current network environment of the operator in the network service instantiation request, so that the instantiation process of the network service is not required, that is, the network does not need to be in the network.
  • Service service configuration phase manually modify the service configuration command to avoid The configuration error caused by the artificial editing modification, and the network service's instantiation process is not interrupted, so the online service efficiency is also improved.
  • the service configuration event included in the network service instantiation request may be used to indicate a service configuration template or a workflow that the network service should perform in the current operation scenario.
  • the service configuration event may include an identifier of a service configuration template or a workflow identifier that the network service should perform in the current scenario, and the corresponding service configuration template or workflow may be stored in a directory server corresponding to the MANO.
  • the service configuration event may directly include a service configuration template or a specific content of the workflow that the network service should perform in the current scenario.
  • the operation scenario herein may be any operation scenario of the network service, such as a scenario of performing software or hardware upgrade on the network service, or a scenario of increasing capacity or reducing capacity of the network service.
  • the operation scenario is not limited.
  • the service configuration template indicated by the service configuration event may include a plurality of configuration command lines for performing the network service, and the service configuration template may include any one of an initial configuration template, an elastic configuration template, an upgrade configuration template, and a security matrix configuration template.
  • the workflow indicated by the service configuration event may be a configuration action used to indicate the next execution of the network service.
  • the embodiment relates to a specific process in which the MANO directly sends the service configuration event parsed from the network service instantiation request to the configuration system. That is, the foregoing S102 may specifically include: the MANO sends a service configuration event to the configuration system, so that the configuration system performs service configuration on the network service according to the service configuration event.
  • the service configuration event may include an identifier of the service configuration template or a workflow identifier that the network service should perform in the current scenario, so that the MANO sends the service configuration event to the configuration system, and then configures the system.
  • the service configuration template or the workflow to be executed by the network service in the current scenario can be obtained from the directory server corresponding to the MANO through the service configuration template identifier or the workflow identifier in the service configuration event, and then according to the service configuration template or The workflow configures the service for the network service.
  • the service configuration event may directly include the service configuration template or the specific content of the workflow that the network service should perform in the current scenario, and the MANO may directly send the content to the configuration system.
  • the configuration system can perform service configuration on the network service according to the content.
  • the embodiment relates to a specific process in which the MANO generates a service configuration command according to the service configuration event in the network service instantiation request, and sends the service configuration command to the configuration system. That is, the foregoing S102 may specifically include: the MANO generates a service configuration command according to the service configuration event, and sends the service configuration command to the configuration system, so that the configuration system performs service configuration on the network service according to the service configuration command.
  • the service configuration event may include the identifier of the service configuration template or the identifier of the workflow that the network service should perform in the current scenario, so that the MANO passes the service configuration in the service configuration event after obtaining the service configuration event.
  • the identifier of the template or the identifier of the workflow, the service configuration template or the workflow to be executed by the network service in the current scenario is obtained from the directory server corresponding to the MANO, and then sent to the configuration system according to the service configuration template or the workflow generation service configuration command.
  • the configuration system configures the network service according to the service configuration command.
  • the service configuration event may directly include the service configuration template or the specific content of the workflow that the network service should perform in the current scenario, so that the MANO can be directly Generate a service configuration command based on the content, and send it to the configuration system to make the configuration The system performs service configuration on the network service according to the service configuration command.
  • the service configuration information exchanged between the MANO and the configuration system may include different forms, enriching the diversity of the interaction between the MANO and the configuration system, and further improving the network service. Reliability when performing business configuration.
  • FIG. 3 is a signaling flowchart of Embodiment 2 of a service configuration method of a network service according to an embodiment of the present disclosure.
  • This embodiment relates to the process in which the MANO and the configuration system perform service configuration information interaction to complete the service configuration of the network service.
  • the service configuration event includes a service configuration event name, a service configuration template in the current scenario, and a service parameter required to execute the service configuration template.
  • the service configuration template in the current scenario and the service parameter required to execute the service configuration template in the service configuration event may also be replaced with “the workflow in the current scenario and the execution of the workflow. Required business parameters.”
  • the content included in the service configuration event in this embodiment is described by taking the former as an example. Referring to Figure 3, the method includes:
  • S201 The MANO receives the network service instantiation request.
  • the MANO parses the network service instantiation request to obtain a service configuration event.
  • the service configuration event includes: a service configuration event name, a service configuration template in the current scenario, and a service parameter required to execute the service configuration template.
  • the service configuration event refers to the information model shown in Table 1.
  • the service configuration event name in the service configuration event can be any type of character or field.
  • the service configuration template in the current operation scenario in the service configuration event can be The specific service configuration script may also be a path information of a specific service configuration script, that is, the service configuration template in the current operation scenario may include a specific service configuration script, and may include path information indicating the service configuration script.
  • the path information is directed to the Config of a server, and the current operation scenario may include any one of an initialization scenario, an elastic scenario, an upgrade scenario, a security matrix scenario, and a service termination scenario;
  • the required service parameters may include at least one of the IP address of the local end, the port number of the local end, the IP address of the peer end, the port of the peer end, and the service type supported by the network service. See Table 1 for details:
  • the foregoing network service may include a VNF, or the network service may include a VNF and a PNF.
  • the foregoing network service instantiation request is instantiated by the VNF.
  • the service configuration event in the network service instantiation request may be a service configuration event of the VNFD that is carried in the VNF instantiation request, and the service configuration event may be used to indicate a service configuration template executed by the VNF in the current operation scenario. Or workflow.
  • the service configuration event may also be used to indicate a service configuration template or a workflow that should be executed by the Virtualization Deployment Unit (VDU) of the VNF in the current operation scenario, where a VNF may include Multiple VDUs.
  • VDU Virtualization Deployment Unit
  • the service configuration event in the network service instantiation request may be a service configuration event carried in the NSD, where the service configuration event may be used to indicate that the current operation scenario is The first service configuration template or the first workflow that the VNF should execute, and the second service configuration template or the second workflow that is used to indicate that the PNF should be executed.
  • the service configuration event may be divided into two parts, one part is carried in the VNFD in the NSD, and a part is carried in the PNFD in the NSD.
  • S203 The MANO generates a service configuration command according to the service configuration event name, the service configuration template in the current operation scenario, and the service parameter.
  • the MANO can automatically generate a service configuration command according to the three.
  • the configuration command can include at least one command line. It should be noted that there is no timing relationship between the process of generating a service configuration command by MANO and the process of performing NFVI resource allocation and service software installation on the network service by MANO, which may be performed simultaneously, or may be performed one after the other.
  • S204 The MANO sends the service configuration command to the configuration system.
  • the MANO needs to send the service configuration command to the configuration system after completing the NFVI resource allocation and service software installation of the network service according to the network service instantiation request.
  • S205 The configuration system sends the service configuration command to the network service.
  • the configuration system sends the service configuration command to the network service, which may include two sending modes, specifically:
  • the first type the configuration system can put the received service configuration commands in the memory or the cache, and then configure the system to connect the command lines in the memory or the configuration commands in the cache one by one after establishing a connection with the network service.
  • the network service can be sent to the network service by the first command line. After the network service is successfully executed, the second command line is sent, and so on. When the network service fails to execute a certain command line, you can enter the configuration rollback state. The configuration system re-issues the command line.
  • the configuration system sends all command lines of the service configuration command directly to the VNF.
  • S206 The network service executes the service configuration command to perform service configuration on the network service.
  • the foregoing service configuration command is generated by the MANO according to the service configuration event.
  • the foregoing S203 and S204 may be replaced by the following S203' to S205', specifically:
  • S203' The MANO sends a service configuration event to the configuration system.
  • S204' The configuration system parses the service configuration event, and obtains the service configuration event name, the service configuration template in the current scenario, and the service parameter.
  • S205' The configuration system generates a service configuration command according to the service configuration event name, the service configuration template in the current scenario, and the service parameter.
  • the above MANO can provide a global resource management function, so that MANO can generate specific service configuration commands.
  • the advantage of this is that the configuration system in the operator's existing network is often an existing inventory system, which is not suitable. To make too many modifications and adaptations to the configuration system, the ability to generate specific service configuration commands on MANO will reduce the workload of modifying the configuration system.
  • the design tool used by the operator to edit and modify the service configuration events already defined by the VNF provider according to the operator's network environment can be provided by MANO.
  • MANO can provide An editing tool for the service configuration script of the network service, which can be used to easily associate the service configuration template provided by the network element provider with the current network resource of the operator, so that the MANO or the configuration system can automatically generate the service configuration command without Artificial configuration reduces the configuration errors caused by human editing changes.
  • the VNF instantiation process is taken as an example, the network service is a VNF, and the foregoing configuration system may be an EM.
  • the method includes:
  • the VNFM receives the VNF instantiation request.
  • the VNFM parses the VNFD in the VNF instantiation request to obtain a service configuration event in the VNFD.
  • the service configuration event includes: a service configuration event name, a service configuration template in the current scenario, and a service configuration template. Required business parameters.
  • the VNFM performs NFVI resource allocation and service software installation on the VNF according to the VNFD.
  • the VNFM can provide the EM with a service configuration event that represents the deployment of the VNF.
  • the EM can also provide the VNF service configuration result to the VNFM.
  • the EM After receiving the service configuration event, the EM parses the service configuration event, and obtains the service configuration event name, the service configuration template and the service parameter in the current scenario.
  • S306 The EM generates a service configuration command according to the service configuration event name, the service configuration template in the current scenario, and the service parameter.
  • the EM sends the service configuration command to the VNF.
  • the service configuration command can be sent to the VNF.
  • the service configuration method of the network service enables the MANO to configure the event according to the service by carrying a preset service configuration event of the network service related to the operator network environment in the network service instantiation request sent to the MANO.
  • the service configuration command is generated, and the service configuration command is sent to the configuration system, so that the configuration system completes the service configuration of the network service according to the service configuration command.
  • the method provided in this embodiment carries a pre-configured service configuration event related to the current network environment of the operator in the network service instantiation request, so that the instantiation process of the network service is not required, that is, the network does not need to be in the network.
  • the service configuration phase manually modified the service configuration commands to avoid the configuration caused by human editing.
  • the error, and the automatic service configuration of the network service is realized, and since the instantiation process of the network service is not interrupted, the online service efficiency of the network service is also improved.
  • FIG. 5 is a schematic structural diagram of Embodiment 1 of a service configuration apparatus for a network service according to an embodiment of the present disclosure.
  • the service configuration device can implement part or all of the management arranger MANO by software, hardware or a combination of software and hardware.
  • the apparatus includes a receiving module 10 and a transmitting module 20.
  • the receiving module 10 is configured to receive a network service instantiation request, where the network service instantiation request includes: a preset service configuration event of a network service related to an operator network environment;
  • the sending module 20 is configured to send service configuration information to the configuration system according to the service configuration event, so that the configuration system performs service configuration on the network service according to the service configuration information.
  • the receiving module 10 may correspond to an input interface or an input component of the MANO having a communication function and a receiving information function
  • the sending module 20 may correspond to an output interface or an output component of the MANO having a communication function and a sending information function.
  • the service configuration device of the network service provided by the embodiment of the present application may perform the foregoing method embodiment, and the implementation principle and the technical effect are similar, and details are not described herein again.
  • the service configuration event is used to indicate a service configuration template or a workflow executed by the network service in a current operation scenario.
  • the service configuration event includes a service configuration event name, a service configuration template in the current scenario, and a service parameter required to execute the service configuration template.
  • the sending module 20 is configured to send a service configuration event to the configuration system, so that the configuration system performs service configuration on the network service according to the service configuration event.
  • the foregoing sending module 20 may include a generating unit 21 and a sending unit 22.
  • the generating unit 21 is configured to generate a service configuration command according to the service configuration event name in the service configuration event, the service configuration template in the current operation scenario, and the service parameter.
  • the sending unit 22 is configured to send the service configuration command to the configuration system, so that the configuration system performs service configuration on the network service according to the service configuration command.
  • the receiving module 10 is further configured to receive a service configuration result sent by the configuration system.
  • the network service is a virtual network function VNF
  • the network service instantiation request is a VNF instantiation request
  • the service configuration event is used to indicate a service configuration template or work performed by the VNF in a current operation scenario. flow.
  • the service configuration event is carried in a virtual network function description VNFD in the VNF instantiation request.
  • the network service includes a virtual network function VNF and a physical network function PNF, where the service configuration event is used to indicate a first service configuration template or a first workflow executed by the VNF in a current operation scenario, and The second service configuration template or the second workflow executed by the PNF.
  • the service configuration event is carried in a network service description NSD in the network service instantiation request.
  • the service configuration event is further used to indicate a service configuration template or a workflow executed by the virtualized deployment unit VDU of the VNF in the current operation scenario.
  • the current operation scenario includes any one of an initialization scenario, an elastic scenario, an upgrade scenario, a security matrix scenario, and a service termination scenario.
  • the service parameter includes at least one of an IP address of the local end, a port number port of the local end, an IP address of the opposite end, a port of the opposite end, and a service type supported by the network service.
  • the service configuration device of the network service provided by the embodiment of the present application may perform the foregoing method embodiment, and the implementation principle and the technical effect are similar, and details are not described herein again.
  • FIG. 7 is a schematic structural diagram of Embodiment 3 of a service configuration apparatus for a network service according to an embodiment of the present disclosure.
  • the service configuration device can implement part or all of the configuration system by software, hardware or a combination of software and hardware.
  • the apparatus includes a receiving module 30 and a configuration module 31.
  • the receiving module 30 is configured to receive service configuration information that is sent by the management orchestrator MANO according to a service configuration event of a network service related to an operator network environment;
  • the configuration module 31 is configured to perform service configuration on the network service according to the service configuration information.
  • the receiving module 30 may correspond to an input interface or an input component in the configuration system having a communication function and a receiving information function, where the configuration module 31 may correspond to a processing component or a processing component having a service configuration function and other functions in the configuration system. chip.
  • the service configuration device of the network service provided by the embodiment of the present application may perform the foregoing method embodiment, and the implementation principle and the technical effect are similar, and details are not described herein again.
  • the service configuration event is used to indicate a service configuration template or a workflow executed by the network service in a current operation scenario.
  • the service configuration event includes a service configuration event name, a service configuration template in the current scenario, and a service parameter required to execute the service configuration template.
  • FIG. 8 is a schematic structural diagram of Embodiment 4 of a service configuration apparatus for a network service according to an embodiment of the present disclosure.
  • the configuration module 31 may further include: a parsing unit 32, a generating unit 33, and a configuration unit 34.
  • the parsing unit 32 is configured to parse the service configuration event, obtain the service configuration event name, the service configuration template in the current scenario, and the service parameter.
  • the generating unit 33 is configured to generate a service configuration command according to the service configuration event name, the service configuration template in the current scenario, and the service parameter.
  • the configuration unit 34 is configured to perform service configuration on the network service according to the service configuration command.
  • the foregoing apparatus may further include a sending module 35, configured to send a service configuration result to the MANO.
  • a sending module 35 configured to send a service configuration result to the MANO.
  • the receiving module 30 is configured to receive a service configuration command sent by the MANO, where the service configuration command is configured by the MANO according to the service, an event configuration name, a service configuration template in the current scenario, and
  • the configuration module 31 is configured to perform service configuration on the network service according to the service configuration command.
  • the network service includes a virtual network function VNF, where the service configuration event is used to indicate a service configuration template or a workflow executed by the VNF in a current operation scenario.
  • the service configuration event is carried in a virtual network function description VNFD in the VNF instantiation request received by the MANO.
  • the network service includes a virtual network function VNF and a physical network function PNF, where the service configuration event is used to indicate a first service configuration template or a first workflow executed by the VNF in a current operation scenario, and The second service configuration template or the second workflow executed by the PNF.
  • the service is configured The event is carried in the network service description NSD in the network service instantiation request received by the MANO.
  • the service configuration event is further used to indicate a service configuration template or a workflow executed by the virtualized deployment unit VDU of the VNF in the current operation scenario.
  • the current operation scenario includes any one of an initial scenario, an elastic scenario, an upgrade scenario, a security matrix scenario, and a service termination scenario, where the service parameters include an IP address of the local end, a port number of the local end, and an IP address of the peer end. At least one of an address, a port of the peer, and a type of service supported by the network service.
  • the service configuration device of the network service provided by the embodiment of the present application may perform the foregoing method embodiment, and the implementation principle and the technical effect are similar, and details are not described herein again.
  • FIG. 9 is a schematic structural diagram of an embodiment of a management orchestrator provided by an embodiment of the present application.
  • the management orchestrator can include a receiver 40, a transmitter 41, a memory 42, a processor 43, and at least one communication bus 44.
  • Communication bus 44 is used to implement a communication connection between the components.
  • Memory 42 may include high speed RAM memory, and may also include non-volatile memory NVM, such as at least one disk memory, in which various programs may be stored for performing various processing functions and implementing the method steps of the present embodiments.
  • the receiver 40 in this embodiment may be a corresponding input interface having a communication function and a function of receiving information.
  • the transmitter 41 in this embodiment may be a corresponding output interface having a communication function and a function of transmitting information, and the sending The device 41 and the receiver 40 may be integrated in one communication interface, or may be separate communication interfaces.
  • the processor 43 may be, for example, a central processing unit (CPU), or may be a processing chip having a function of generating a service configuration command and other functions.
  • the communication bus may be an ISA (Industry Standard Architecture) bus, a PCI (Peripheral Component Interconnect) bus, or an EISA (Extended Industry Standard Architecture) bus. Wait.
  • the communication bus may be one or more physical lines, and when it is a plurality of physical lines, it may be divided into an address bus, a data bus, a control bus, and the like.
  • the receiver 40 is configured to receive a network service instantiation request, where the network service instantiation request includes: a preset service configuration event of a network service related to an operator network environment;
  • the transmitter 41 is configured to send service configuration information to the configuration system according to the service configuration event, so that the configuration system performs service configuration on the network service according to the service configuration information.
  • the MANO can include three components: NFVO, VNFM, and VIM.
  • NFVO, VNFM, and VIM are all part of MANO.
  • the three can be deployed on different hardware devices to form all or part of MANO through physical connections. All or part of the MANO can be constructed on the same hardware device (ie, software loaded with the functions of the above NFVO, VNFM, and VIM on the hardware device).
  • the receiver 40, the transmitter 41, and the processor 43 may be integrated on the VNFM; optionally, when the MANO is deployed on the same hardware
  • the integrated positions of the receiver 40 and the transmitter 41 are not limited when NFVO, VNFM, and VIM are provided on the device.
  • the service configuration event is used to indicate a service configuration template or a workflow executed by the network service in a current operation scenario.
  • the service configuration event includes a service configuration event name, a service configuration template in the current scenario, and a service parameter required to execute the service configuration template.
  • the sender 41 is configured to send a service configuration event to the configuration system, so that the configuration system performs service configuration on the network service according to the service configuration event.
  • the processor 43 is configured to generate a service configuration command according to the service configuration event name, the service configuration template in the current operation scenario, and the service parameter in the service configuration event;
  • the device 41 is configured to send the service configuration command generated by the processor 43 to the configuration system, so that the configuration system performs service configuration on the network service according to the service configuration command.
  • the receiver 40 is further configured to receive a service configuration result sent by the configuration system.
  • the network service is a virtual network function VNF
  • the network service instantiation request is a VNF instantiation request
  • the service configuration event is used to indicate a service configuration template or work performed by the VNF in a current operation scenario. flow.
  • the service configuration event is carried in a virtual network function description VNFD in the VNF instantiation request.
  • the network service includes a virtual network function VNF and a physical network function PNF, where the service configuration event is used to indicate a first service configuration template or a first workflow executed by the VNF in a current operation scenario, and The second service configuration template or the second workflow executed by the PNF.
  • the service configuration event is carried in a network service description NSD in the network service instantiation request.
  • the service configuration event is further used to indicate a service configuration template or a workflow executed by the virtualized deployment unit VDU of the VNF in the current operation scenario.
  • the current operation scenario includes any one of an initialization scenario, an elastic scenario, an upgrade scenario, a security matrix scenario, and a service termination scenario.
  • the service parameter includes at least one of an IP address of the local end, a port number port of the local end, an IP address of the opposite end, a port of the opposite end, and a service type supported by the network service.
  • the management orchestrator provided by the embodiment of the present application may perform the foregoing method embodiments, and the implementation principles and technical effects thereof are similar, and details are not described herein again.
  • FIG. 10 is a schematic structural diagram of an embodiment of a configuration system according to an embodiment of the present disclosure.
  • the configuration system can be EM or OSS.
  • the configuration system can include a receiver 50, a memory 51, a processor 52, and at least one communication bus 53.
  • a transmitter 54 may also be included.
  • the communication bus 53 is used to implement a communication connection between components.
  • the memory 51 may include a high speed RAM memory, and may also include a non-volatile memory NVM, such as at least one disk memory, in which various programs may be stored for performing various processing functions and implementing the method steps of the present embodiment.
  • the receiver 50 in this embodiment may be a corresponding input interface having a communication function and a function of receiving information.
  • the transmitter 54 in this embodiment may be a corresponding output interface having a communication function and a function of transmitting information, and the sending The 54 and the receiver 50 may be integrated in one communication interface or may be separate communication interfaces.
  • the processor 52 can be, for example, a central processing unit (CPU), or a processing chip having a service configuration function and other functions.
  • the receiver 50 is configured to receive service configuration information that is sent by the management orchestrator MANO according to a service configuration event of a network service related to an operator network environment;
  • the processor 52 is configured to perform service configuration on the network service according to the service configuration information.
  • the service configuration event is used to indicate a service configuration template or a workflow executed by the network service in a current operation scenario.
  • the service configuration event includes a service configuration event name, a service configuration template in the current scenario, and a service parameter required to execute the service configuration template.
  • the processor 52 is configured to parse the service configuration event, obtain the service configuration event name, the service configuration template in the current scenario, and the service parameter, and configure the event according to the service.
  • the service configuration template and the service parameter in the current scenario generate a service configuration command, and perform service configuration on the network service according to the service configuration command.
  • the receiver 50 is configured to receive a service configuration command sent by the MANO, where the service configuration command is configured by the MANO according to the service, an event configuration name, a service configuration template in the current scenario, and
  • the processor 52 is configured to perform service configuration on the network service by using the service configuration command.
  • the transmitter 54 is configured to send a service configuration result to the MANO.
  • the network service includes a virtual network function VNF, where the service configuration event is used to indicate a service configuration template or a workflow executed by the VNF in a current operation scenario.
  • the service configuration event is carried in a virtual network function description VNFD in the VNF instantiation request received by the MANO.
  • the network service includes a virtual network function VNF and a physical network function PNF, where the service configuration event is used to indicate a first service configuration template or a first workflow executed by the VNF in a current operation scenario, and The second service configuration template or the second workflow executed by the PNF.
  • the service configuration event is carried in a network service description NSD in the network service instantiation request received by the MANO.
  • the service configuration event is further used to indicate a service configuration template or a workflow executed by the virtualized deployment unit VDU of the VNF in the current operation scenario.
  • the current operation scenario includes any one of an initial scenario, an elastic scenario, an upgrade scenario, a security matrix scenario, and a service termination scenario, where the service parameters include an IP address of the local end, a port number of the local end, and an IP address of the peer end. At least one of an address, a port of the peer, and a type of service supported by the network service.
  • FIG. 11 is a schematic structural diagram of an embodiment of a service configuration system for a network service according to an embodiment of the present disclosure.
  • the service configuration system may include the above MANO and configuration system.
  • the service configuration system can be applied to the NFV MANO architecture shown in FIG. 1 or to the NFV MANO architecture shown in FIG.
  • the NFV MANO architecture diagram shown in FIG. 12 is a refinement of the NFV MANO architecture diagram shown in FIG. 1 above.
  • this embodiment first introduces the NFV MANO architecture by taking FIG. 12 as an example.
  • the NFV MANO system can be implemented over a variety of networks, such as data center networks, service provider networks, or local area networks (LANs).
  • the NFV MANO system may include MANO 128, NFVI 130, a plurality of VNFs 108, a plurality of element management systems (EMS) 122, a service, VNF, and a VNF and Infrastructure Description system 126.
  • EMS element management systems
  • EMS element management systems
  • VNF VNF and Infrastructure Description system
  • OSS/BSS 124 one or more OSS/BSS 124.
  • the configuration system in the embodiment of the present application may be the OSS in FIG. 12, and may also be the EMS in FIG.
  • MANO128 can include Network Function Virtualization (Network Function Virtulization) Orchestration (NFVO) 102, one or more VNF Manager (VNFM) 104, and one or more Virtualized Infrastructure Manager (VIM) 106.
  • NFVO Network Function Virtualization
  • VNFM VNF Manager
  • VIP Virtualized Infrastructure Manager
  • the NFVI 130 may include a computing hardware 112, storage hardware 114, a hardware resource layer composed of network hardware 116, a virtualization layer, and a virtual resource layer composed of virtual computing 110 (eg, virtual machine), virtual storage 118, and virtual network 120.
  • Computing hardware 112 can be a dedicated processor or a general purpose processor for providing processing and computing functions.
  • the storage hardware 114 is configured to provide storage capabilities, which may be provided by the storage hardware 114 itself (eg, a server's local memory), or may be provided over a network (eg, the server connects to a network storage device over a network).
  • Network hardware 116 may be a switch, router, and/or other network device, and network hardware 116 is used to enable communication between multiple devices, with wireless or wired connections between multiple devices.
  • the virtualization layer in NFVI130 is used to abstract the hardware resources of the hardware resource layer, decouple the VNF 108 from the physical layer to which the hardware resources belong, and provide virtual resources to the VNF.
  • virtual resources may include virtual computing 110, virtual storage 118, and virtual network 120.
  • Virtual computing 110, virtual storage 118 may be provided to VNF 108 in the form of a virtual machine or other virtual container, such as one or more VNFs 108 may be deployed on a virtual machine.
  • the virtualization layer forms a virtual network 120 through abstract network hardware 116.
  • Virtual networks 120 such as virtual switches (eg, Vswitches), are used to enable communication between multiple virtual machines, or between other types of virtual containers hosting VNFs.
  • Virtualization of network hardware can be virtualized by virtual LAN (Vritual LAN, VLAN), Virtual Private LAN Service (VPLS), Virtual eXtensible Local Area Network (VxLAN), or general routing encapsulation network ( Nerwork Virtualization using Generic Routing Encapsulation, NVGRE) and other technical implementations.
  • virtual LAN Virtual LAN
  • VPLS Virtual Private LAN Service
  • VxLAN Virtual eXtensible Local Area Network
  • NVGRE General routing encapsulation network
  • OSS/BSS124 is mainly for telecom service operators, providing comprehensive network management and service operation functions, including network management (such as fault monitoring, network information collection, etc.), billing management, and customer service management.
  • network management such as fault monitoring, network information collection, etc.
  • billing management billing management
  • customer service management customer service management.
  • the VNF and the infrastructure description system 126 are described in detail in the ETSI GS NFV 002 v1.1.1 standard, and the details of the present application are not described herein again.
  • the above MANO 128 can be used to implement monitoring and management of VNF 108 and NFVI 130.
  • the NFVO 102 can communicate with one or more VNFMs 104 to implement resource related requests, send configuration information to the VNFM 104, and collect status information for the VNF 108.
  • the NFVO 102 can also communicate with the VIM 106 to enable resource allocation, and/or to implement configuration and status information reservation and exchange of virtualized hardware resources.
  • the VNFM 104 can be used to manage one or more VNFs 108, performing various management functions, such as initializing, updating, querying, and/or terminating the VNF 108.
  • the VIM 106 can be used to control and manage the interaction of the VNF 108 and computing hardware 112, storage hardware 114, network hardware 116, virtual computing 110, virtual storage 118, virtual network 120.
  • VIM 106 can be used to perform resource allocation operations to VNF 108.
  • the VNFM 104 and VIM 106 can communicate with one another to exchange virtualized hardware resource configuration and status information.
  • NFVI 130 includes both hardware and software that together create a virtualized environment to deploy, manage, and execute VNF 108.
  • the hardware resource layer and the virtual resource layer are used to provide virtual resources, such as virtual machines and/or other forms of virtual containers, to the VNF 108.
  • VNFM 104 can communicate with VNF 108 and EMS 122 to perform VNF lifecycle management and implement exchange of configuration information/status information.
  • the VNF 108 is a virtualization of at least one network function that was previously provided by a physical network device.
  • the VNF 108 can be A virtualized Mobility Management Entity (MME) node is used to provide all the network functions provided by a typical non-virtualized MME device.
  • MME Mobility Management Entity
  • the VNF 108 can be used to implement the functionality of some of the components provided on the non-virtualized MME device.
  • One or more VNFs 108 can be deployed on a virtual machine (or other form of virtual container).
  • the EMS 122 can be used to manage one or more VNFs.
  • the service configuration system involved in the embodiments of the present application may include the MANO 60 and the configuration system 70.
  • the MANO 60 is configured to receive a network service instantiation request, and send service configuration information to the configuration system 70 according to the service configuration event;
  • the network service instantiation request includes: a preset network related to an operator network environment. Service configuration event of the service;
  • the configuration system 70 is configured to receive service configuration information sent by the MANO 70 according to a service configuration event of the network service related to the network environment of the operator, and perform service configuration on the network service according to the service configuration information.
  • the service configuration event is used to indicate a service configuration template or a workflow executed by the network service in a current operation scenario.
  • the service configuration event includes a service configuration event name, a service configuration template in the current scenario, and a service parameter required to execute the service configuration template.
  • the MANO 60 is configured to send a service configuration event to the configuration system 70, so that the configuration system 70 performs service configuration on the network service according to the service configuration event.
  • the configuration system 70 is configured to parse the service configuration event, obtain the service configuration event name, the service configuration template in the current scenario, and the service parameter, and configure the event name according to the service,
  • the service configuration template and the service parameter in the current scenario generate a service configuration command, and perform service configuration on the network service according to the service configuration command.
  • the MANO 60 is configured to generate a service configuration command according to the service configuration event name in the service configuration event, the service configuration template in the current operation scenario, and the service parameter, and The service configuration command is sent to the configuration system 70, so that the configuration system 70 performs service configuration on the network service according to the service configuration command.
  • the configuration system 70 is configured to receive a service configuration command sent by the MANO 60, and perform service configuration on the network service according to the service configuration command.
  • the configuration system 70 is further configured to send a service configuration result to the MANO 60.
  • the MANO 60 is further configured to receive a service configuration result sent by the configuration system 70.
  • the network service is a virtual network function VNF
  • the network service instantiation request is a VNF instantiation request
  • the service configuration event is used to indicate a service configuration template or work performed by the VNF in a current operation scenario. flow.
  • the service configuration event is carried in a virtual network function description VNFD in the VNF instantiation request.
  • the network service includes a virtual network function VNF and a physical network function PNF, where the service configuration event is used to indicate a first service configuration template or a first workflow executed by the VNF in a current operation scenario, and The second service configuration template or the second workflow executed by the PNF.
  • the service configuration event is carried in a network service description NSD in the network service instantiation request.
  • the service configuration event is further used to indicate a service configuration template or a workflow executed by the virtualized deployment unit VDU of the VNF in the current operation scenario.
  • the current operation scenario includes any one of an initial scenario, an elastic scenario, an upgrade scenario, a security matrix scenario, and a service termination scenario, where the service parameters include an IP address of the local end, a port number of the local end, and an IP address of the peer end. At least one of an address, a port of the peer, and a type of service supported by the network service.
  • the service configuration system of the network service provided by the embodiment of the present application may perform the foregoing method embodiments, and the working principle and technical effects thereof are similar, and details are not described herein again.
  • the various embodiments in the specification are described in a progressive manner, and the same or similar parts between the various embodiments may be referred to each other, and each embodiment focuses on the differences from the other embodiments.
  • the description is relatively simple, and the relevant parts can be referred to the description of the method embodiment.
  • the device embodiments described above are merely illustrative, wherein the units described as separate components may or may not be physically separate, and the components displayed as units may or may not be physical units, ie may be located A place, or it can be distributed to multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of the embodiment. Those of ordinary skill in the art can understand and implement without any creative effort.
  • the disclosed systems, devices, and methods may be implemented in other manners.
  • the device embodiments described above are merely illustrative.
  • the division of the unit is only a logical function division.
  • there may be another division manner for example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored or not executed.
  • the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be in an electrical, mechanical or other form.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of the embodiment.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
  • the function can be implemented in the form of a software functional unit and sold or used as a stand-alone product.
  • the technical solution of the present application which is essential or contributes to the prior art, or a part of the technical solution, may be embodied in the form of a software product, which is stored in a storage medium, including
  • the instructions are used to cause a computer device (which may be a personal computer, server, or network device, etc.) to perform all or part of the steps of the methods described in various embodiments of the present application.
  • the foregoing storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, and the like. .

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Automation & Control Theory (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Stored Programmes (AREA)

Abstract

本申请实施例提供一种网络服务的业务配置方法和装置。该方法包括：接收网络服务实例化请求，所述网络服务实例化请求包括：预设的与运营商网络环境相关的网络服务的业务配置事件；根据所述业务配置事件向配置***发送业务配置信息，以使所述配置***根据所述业务配置信息对所述网络服务进行业务配置。本申请实施例无需人为中断网络服务的实例化流程，避免了人为编辑修改所带来的配置错误，并且由于网络服务的实例化流程并未中断，因此也提高了网络服务的上线效率。

Description

网络服务的业务配置方法和装置 技术领域
本申请实施例涉及通信技术，尤其涉及一种网络服务的业务配置方法和装置。
背景技术
目前，欧洲电信标准协会(European Telecommunications Sdandards Institut，以下简称ETSI)成立了网络功能虚拟化行业规范组(Network Function Virtulization Industry Specification Group，以下简称NFV ISG)，目的是通过借鉴互联网技术(Internet Technology，以下简称IT)的虚拟化技术，使得通用的硬件能够实现部分网络功能，因而需要网络功能以虚拟网络功能(Virtualized Network Function，以下简称VNF)方式在通用的硬件上可以运行起来，这里的VNF是具有网络功能的虚拟化实体。例如：具有移动管理实体(Mobile Management Entity，以下简称MME)功能的VNF，则这个VNF就是一个虚拟的MME。另外，将该VNF部署在一个或多个虚拟机(Virtual Machine，以下简称VM)上使其运行起来，成为VNF实例，即就是对该VNF进行实例化的过程。
当前标准中涉及的网络功能虚拟化管理和编排(Network Function Virtulization Management and Orchestration，以下简称NFV MANO)架构中，NFV-MANO可以用于管理网络功能虚拟化基础设施(NFV Infrastructure，以下简称NFVI)并编排网络服务(Network Service，简称NS)和VNF所需的资源。其中，NFVI由硬件资源和虚拟资源等组成，NS是由多个VNF或多个VNF和PNF组成的以提供更复杂的功能的网络服务，例如，由虚拟或物理的MME、服务网关(Serving GateWay，简称SGW)、归属用户签约服务器(Home Subscriber Server，简称HSS)以及它们之间的虚拟链路组成的演进的分组核心网(Evolved Packet Core，简称EPC)就可以称作一个NS。上述NFV-MANO对VNF的管理和编排能力实际包含了传统的故障管理、配置管理、计费管理、性能管理和安全管理(FaultManagement，Configuration Management，Accounting Management，Performance Management，Security Management，简称FCAPS)，但是当前NFV-MANO主要聚焦于创建VNF和VNF生命周期管理中所需NFVI资源的管理能力，这里统称为VNF管理。
上述VNF管理需支持VNF生命周期管理能力，至少包括以下操作功能：VNF实例化(创建一个VNF)、VNF弹性(增加或减少VNF的容量)、VNF更新和升级(VNF的软件和配置的变更)、VNF终结(释放VNF所占用的NFVI资源)。为保证对VNF执行这些操作后，VNF还能正常对外提供业务能力，除了需支持对VNF分配NFVI资源外，还需要支持对VNF进行业务配置(例如，VNF实例化流程中需包括对VNF进行业务配置)，其中VNF的业务配置与运营商的现网环境以及具体的NS相关。
当前在对VNF进行业务配置时，是将VNF的NFVI资源编排和业务配置拆分成“VNF虚拟资源分配及软件安装”和“VNF的业务配置”两个独立的阶段，由操作员手动 分两次执行以完成VNF生命周期管理动作。其中所涉及的VNF的业务配置命令由操作员人为编辑和执行，有可能引入人为配置错误，并且上述VNF的业务配置需要操作员进行两次操作，中断了VNF生命周期管理事务流，VNF上线效率低。
发明内容
本申请实施例提供一种网络服务的业务配置方法和装置，用以解决现有技术中人为配置业务命令带来VNF的业务配置错误，以及VNF上线效率低的技术问题。
第一方面，本申请实施例提供一种网络服务的业务配置方法，包括：接收网络服务实例化请求，所述网络服务实例化请求包括：预设的与运营商网络环境相关的网络服务的业务配置事件；根据所述业务配置事件向配置***发送业务配置信息，以使所述配置***根据所述业务配置信息对所述网络服务进行业务配置。
该业务配置事件可以有效的反映当前运营商的网络环境，并且可以为NFVMANO***中的网络服务在当前运营商的网络环境中进行业务配置时直接或者间接的提供业务配置所需的参数或者脚本等，这里对业务配置事件的形式或者内容并不做限定，只要其能够使得NFV MANO***中的网络服务在不中断实例化流程或者其他流程的情况下自动完成业务配置即可。
另外，业务配置信息与业务配置事件相关，其可以是业务配置事件的直接形式或者间接形式，还可以是其他的与业务配置事件相关的信息，本申请实施例对业务配置信息的具体形式并不做限定，只要其能够使得NFV MANO***中的网络服务在不中断实例化流程或者其他流程的情况下自动完成业务配置即可。
该第一方面所提供的网络服务的业务配置方法，通过在发送给MANO的网络服务实例化请求中携带预设的与运营商网络环境相关的网络服务的业务配置事件，使得MANO可以根据该业务配置事件向配置***发送业务配置信息，进而使得配置***在MANO完成对网络服务的资源分配和业务软件安装后，根据该业务配置信息对网络服务进行业务配置，从而并不需要人为中断网络服务的实例化流程，即并不需要在网络服务业务配置阶段人为修改业务配置命令，避免了人为编辑修改所带来的配置错误，并且由于网络服务的实例化流程并未中断，因此也提高了网络服务的上线效率。
在一种可能的设计中，所述业务配置事件用于指示在当前操作场景下所述网络服务执行的业务配置模板或工作流。可选的，该业务配置事件可以包括当前场景下网络服务应该执行的业务配置模板的标识或者工作流的标识，而对应的业务配置模板或者工作流可以存储在MANO对应的目录服务器中。可选的，该业务配置事件还可以直接包括当前场景下网络服务应该执行的业务配置模板或者工作流的具体内容。
在一种可能的设计中，所述业务配置事件包括业务配置事件名称、所述当前场景下的业务配置模板和执行所述业务配置模板时所需的业务参数。
在一种可能的设计中，所述根据所述业务配置事件向配置***发送业务配置信息，以使所述配置***根据所述业务配置信息对所述网络服务进行业务配置，具体包括：向配置***发送业务配置事件，以使所述配置***根据所述业务配置事件对 所述网络服务进行业务配置。
在一种可能的设计中，所述根据所述业务配置事件向配置***发送业务配置信息，以使所述配置***根据所述业务配置信息对所述网络服务进行业务配置，具体包括：根据所述业务配置事件中的所述业务配置事件名称、所述当前操作场景下的业务配置模板和所述业务参数生成业务配置命令；将所述业务配置命令发送至所述配置***，以使所述配置***根据所述业务配置命令对所述网络服务进行业务配置。
在一种可能的设计中，所述方法还包括：接收所述配置***发送的业务配置结果。
上述各可能的设计所提供的网络服务的业务配置方法，MANO与配置***所交互的业务配置信息可以包括不同的形式，丰富了MANO与配置***交互的多样性，进而也提高了网络服务在进行业务配置时的可靠性。
第二方面，本申请实施例提供一种网络服务的业务配置方法，包括：接收管理编排器MANO根据与运营商网络环境相关的网络服务的业务配置事件发送的业务配置信息；根据所述业务配置信息对所述网络服务进行业务配置。
在一种可能的设计中，所述业务配置事件用于指示在当前操作场景下所述网络服务执行的业务配置模板或工作流。
在一种可能的设计中，所述业务配置事件包括业务配置事件名称、所述当前场景下的业务配置模板和执行所述业务配置模板时所需的业务参数。
在一种可能的设计中，所述根据所述业务配置信息对所述网络服务进行业务配置，具体包括：解析所述业务配置事件，获得所述业务配置事件名称、所述当前场景下的业务配置模板和所述业务参数；根据所述业务配置事件名称、所述当前场景下的业务配置模板和所述业务参数生成业务配置命令；根据所述业务配置命令对所述网络服务进行业务配置。
在一种可能的设计中，所述接收管理编排器MANO根据与运营商网络环境相关的网络服务的业务配置事件发送的业务配置信息，具体包括：接收所述MANO发送的业务配置命令，所述业务配置命令为所述MANO根据所述业务配置事件名称、所述当前场景下的业务配置模板和所述业务参数生成的；
则根据所述业务配置信息对所述网络服务进行业务配置，包括：根据所述业务配置命令对所述网络服务进行业务配置。
在一种可能的设计中，所述方法还包括：向所述MANO发送业务配置结果。
上述第二方面以及第二方面的各可能的设计所提供的网络服务的业务配置方法，其有益效果可以参照上述第一方面以及第一方面的各可能的设计所带来的有益效果，在此不再赘述。
第三方面，本申请实施例提供一种网络服务的业务配置装置，包括：接收模块，用于接收网络服务实例化请求，所述网络服务实例化请求包括：预设的与运营商网络环境相关的网络服务的业务配置事件；发送模块，用于根据所述业务配置事件向配置***发送业务配置信息，以使所述配置***根据所述业务配置信息对所述网络服务进行业务配置。
在一种可能的设计中，所述业务配置事件用于指示在当前操作场景下所述网络服务执行的业务配置模板或工作流。
在一种可能的设计中，所述业务配置事件包括业务配置事件名称、所述当前场景下的业务配置模板和执行所述业务配置模板时所需的业务参数。
在一种可能的设计中，所述发送模块，具体用于向配置***发送业务配置事件，以使所述配置***根据所述业务配置事件对所述网络服务进行业务配置。
在一种可能的设计中，所述发送模块，包括：生成单元，用于根据所述业务配置事件中的所述业务配置事件名称、所述当前操作场景下的业务配置模板和所述业务参数生成业务配置命令；发送单元，用于将所述业务配置命令发送至所述配置***，以使所述配置***根据所述业务配置命令对所述网络服务进行业务配置。
在一种可能的设计中，所述接收模块，还用于接收所述配置***发送的业务配置结果。
上述第三方面以及第三方面的各可能的设计所提供的网络服务的业务配置方法，其有益效果可以参照上述第一方面以及第一方面的各可能的设计所带来的有益效果，在此不再赘述。
第四方面，本申请实施例提供一种网络服务的业务配置装置，包括：接收模块，用于接收管理编排器MANO根据与运营商网络环境相关的网络服务的业务配置事件发送的业务配置信息；配置模块，用于根据所述业务配置信息对所述网络服务进行业务配置。
在一种可能的设计中，所述业务配置事件用于指示在当前操作场景下所述网络服务执行的业务配置模板或工作流。
在一种可能的设计中，所述业务配置事件包括业务配置事件名称、所述当前场景下的业务配置模板和执行所述业务配置模板时所需的业务参数。
在一种可能的设计中，所述配置模块，具体包括：解析单元，用于解析所述业务配置事件，获得所述业务配置事件名称、所述当前场景下的业务配置模板和所述业务参数；生成单元，用于根据所述业务配置事件名称、所述当前场景下的业务配置模板和所述业务参数生成业务配置命令；配置单元，用于根据所述业务配置命令对所述网络服务进行业务配置。
在一种可能的设计中，所述接收模块，具体用于接收所述MANO发送的业务配置命令，所述业务配置命令为所述MANO根据所述业务配置事件名称、所述当前场景下的业务配置模板和所述业务参数生成的；所述配置模块，具体用于根据所述业务配置命令对所述网络服务进行业务配置。
在一种可能的设计中，所述装置还包括：发送模块，用于向所述MANO发送业务配置结果。
上述第四方面以及第四方面的各可能的设计所提供的网络服务的业务配置方法，其有益效果可以参照上述第一方面以及第一方面的各可能的设计所带来的有益效果，在此不再赘述。
第五方面，本申请实施例提供一种管理编排器MANO，包括：接收器，用于接收网络服务实例化请求，所述网络服务实例化请求包括：预设的与运营商网络环境 相关的网络服务的业务配置事件；发送器，用于根据所述业务配置事件向配置***发送业务配置信息，以使所述配置***根据所述业务配置信息对所述网络服务进行业务配置。
在其他实现方式中，该管理编排器MANO还可以包括独立与接收器和发送器，并与二者具有通信连接的处理器，该处理器用于根据所述业务配置事件获得业务配置信息，并通过所述发送器向所述配置***发送所述业务配置信息。
该MANO可以包括网络功能虚拟化编制器(Network Function Virtulization Orchestration，简称NFVO)、虚拟网络功能管理器(Virtualized Network Function Management，简称VNFM)VNFM和虚拟基础设施管理器(Virtualized Infrastructure Manager，简称VIM)三种组件，即NFVO、VNFM和VIM均属于MANO的一部分，三者可以分别部署在不同的硬件设备上通过物理连接构成MANO的全部或者部分，也可以部署在同一个硬件设备上(即在该硬件设备上加载具有上述NFVO、VNFM和VIM的功能的软件即可)构成MANO的全部或者部分。可选的，当MANO包括部署在不同硬件设备上的NFVO、VNFM和VIM时，上述接收器和发送器可以集成在VNFM上；可选的，当MANO包括部署在同一硬件设备上的NFVO、VNFM和VIM时，对接收器和发送器的集成位置不做限定。
可选的，上述发送器可以为MANO中具有通信功能和发送信息功能的输出接口，上述接收器，可以为MANO中具有通信功能和接收信息功能的输入接口。
在一种可能的设计中，所述业务配置事件用于指示在当前操作场景下所述网络服务执行的业务配置模板或工作流。
在一种可能的设计中，所述业务配置事件包括业务配置事件名称、所述当前场景下的业务配置模板和执行所述业务配置模板时所需的业务参数。
在一种可能的设计中，所述发送器，具体用于向配置***发送业务配置事件，以使所述配置***根据所述业务配置事件对所述网络服务进行业务配置。
在一种可能的设计中，所述MANO还包括处理器；可选的，该处理器可以为具有生成业务配置命令功能以及其他功能的处理芯片，其可以集成在VNFM中；
所述处理器，用于根据所述业务配置事件中的所述业务配置事件名称、所述当前操作场景下的业务配置模板和所述业务参数生成业务配置命令；
所述发送器，用于将所述处理器生成的所述业务配置命令发送至所述配置***，以使所述配置***根据所述业务配置命令对所述网络服务进行业务配置。
在一种可能的设计中，所述接收器，还用于接收所述配置***发送的业务配置结果。
上述第五方面以及第五方面的各可能的设计所提供的网络服务的业务配置方法，其有益效果可以参照上述第一方面以及第一方面的各可能的设计所带来的有益效果，在此不再赘述。
第六方面，本申请实施例提供一种配置***，包括：接收器，用于接收管理编排器MANO根据与运营商网络环境相关的网络服务的业务配置事件发送的业务配置信息；处理器，用于根据所述业务配置信息对所述网络服务进行业务配置。
可选的，该配置***可以为网元管理***(Element Management，简称EM)， 可以是运营支撑***(Operation Support System，以下简称OSS)。上述接收器，可以为配置***中具有通信功能和接收信息功能的输入接口，处理器，可以为配置***中具有业务配置功能以及其他功能的处理芯片。
在一种可能的设计中，所述业务配置事件用于指示在当前操作场景下所述网络服务执行的业务配置模板或工作流。
在一种可能的设计中，所述业务配置事件包括业务配置事件名称、所述当前场景下的业务配置模板和执行所述业务配置模板时所需的业务参数。
在一种可能的设计中，所述处理器，具体用于解析所述业务配置事件，获得所述业务配置事件名称、所述当前场景下的业务配置模板和所述业务参数，并根据所述业务配置事件名称、所述当前场景下的业务配置模板和所述业务参数生成业务配置命令，并根据所述业务配置命令对所述网络服务进行业务配置。
在一种可能的设计中，所述接收器，具体用于接收所述MANO发送的业务配置命令，所述业务配置命令为所述MANO根据所述业务配置事件名称、所述当前场景下的业务配置模板和所述业务参数生成的；
所述处理器，具体用于所述业务配置命令对所述网络服务进行业务配置。
在一种可能的设计中，所述配置***还包括：用于向所述MANO发送业务配置结果的发送器。可选的，该发送器可以为配置***中具有通信功能和发送信息功能的输出接口。
在上述各方面的各可能的设计中，可选的，所述网络服务包括虚拟网络功能VNF，所述业务配置事件用于指示在当前操作场景下所述VNF执行的业务配置模板或工作流。
可选的，所述网络服务包括虚拟网络功能VNF和物理网络功能PNF，所述业务配置事件用于指示在当前操作场景下所述VNF执行的第一业务配置模板或第一工作流，以及，所述PNF执行的第二业务配置模板或第二工作流。
可选的，所述业务配置事件携带在所述MANO接收的VNF实例化请求中的虚拟网络功能描述VNFD中。
可选的，所述业务配置事件携带在所述MANO接收的网络服务实例化请求中的网络服务描述NSD中。
可选的，所述业务配置事件还用于指示在当前操作场景下所述VNF的虚拟化部署单元VDU执行的业务配置模板或工作流。
可选的，所述当前操作场景包括初始化场景、弹性场景、升级场景、安全矩阵场景、服务终结场景中的任一个，所述业务参数包括本端的IP地址、本端的端口号Port、对端的IP地址、对端的Port、所述网络服务支持的业务类型中的至少一个参数。
上述第六方面以及第六方面的各可能的设计所提供的网络服务的业务配置方法，其有益效果可以参照上述第一方面以及第一方面的各可能的设计所带来的有益效果，在此不再赘述。
第七方面，本申请实施例提供一种网络服务的业务配置***，该业务配置***可以包括上述各可能的设计中所涉及的MANO以及上述各可能的设计中所涉及的配 置***。该MANO可以通过相应的通信总线、通信接口实现与配置***的通信连接。该业务配置***的具体工作原理和有益效果，可以参照上述各可能的设计，在此不再赘述。
第八方面，本申请实施例还提供一种计算机程序产品，该计算机程序产品中包含计算机程序，该计算机程序当被处理器或其它类型芯片读取并执行时可以实现本申请前述实施例提供的网络服务的业务配置方法。该计算机程序产品可达到的有益效果和具体工作原理参考前述实施例，在此不再赘述。
附图说明
图1为本申请实施例提供的NFV MANO架构图一；
图2为本申请实施例提供的网络服务的业务配置方法实施例一的信令流程图；
图3为本申请实施例提供的网络服务的业务配置方法实施例二的信令流程图；
图4为本申请实施例提供的网络服务的业务配置方法实施例三的信令流程图；
图5为本申请实施例提供的网络服务的业务配置装置实施例一的结构示意图；
图6为本申请实施例提供的网络服务的业务配置装置实施例二的结构示意图；
图7为本申请实施例提供的网络服务的业务配置装置实施例三的结构示意图；
图8为本申请实施例提供的网络服务的业务配置装置实施例四的结构示意图；
图9为本申请实施例提供的管理编排器实施例的结构示意图；
图10为本申请实施例提供的配置***实施例的结构示意图；
图11为本申请实施例提供的网络服务的业务配置***实施例的结构示意图；
图12为本申请实施例提供的NFV MANO架构图二。
具体实施方式
本申请实施例涉及的VNF的业务配置方法，可以适用于图1所示的NFV MANO架构，该NFV MANO架构可以包括：运营支撑***(Operation Support System，以下简称OSS)或业务支撑***(Business Support System，以下简称BSS)、配置***、VNF、物理网络功能(Physical Network Function，以下简称PNF)、网络功能虚拟化基础设施(NFV Infrastructure，以下简称NFVI)、NFV编排器(NFV Orchestrator，以下简称NFVO)、VNF管理器(VNF Manager，以下简称VNFM)和虚拟基础设施管理器(Virtualized Infrastructure Manager，以下简称VIM)。可选的，上述配置***可以为网元管理***(Element Management，简称EM)，可以是OSS，图1中示出的是配置***为EM的情况。结合图1，上述NFVI由硬件资源和虚拟资源以及虚拟层组成，VIM用来控制和管理虚拟化的实体，NFVO负责对NFVI资源进行网络侧的编排和管理，以及在NFVI上实现NFV的业务拓扑，VNFM负责VNF实例的生命周期的管理。其中，图1中的NFVO、VNFM和VIM三者均属于MANO中的一部分。另外，NFVO、VNFM和VIM均可以部署在不同或者同一硬件设备上，只要在硬件设备上加载具有上述NFVO、VNFM和VIM的功能的软件即可。
现有技术中，在进行VNF业务配置时，配置***无法从MANO的通知中获得足够的信息完成对VNF的业务配置动作，因此需要人为的中断VNF的实例化流程，通 过人为编辑修改配置***所需的业务配置命令，进而再次启动配置***完成VNF的业务配置，因此无法实现VNF的自动化业务配置，并且容易带来人为配置错误的技术问题，并且由于人为的中断VNF的实例化流程，因此也存在VNF上线效率低的技术问题。本申请实施例提供的VNF的业务配置方法和装置，旨在解决现有技术的这些问题。
下面以具体地实施例对本申请的技术方案进行详细说明。下面这几个具体的实施例可以相互结合，对于相同或相似的概念或过程可能在某些实施例中不再赘述。
图2为本申请实施例提供的网络服务的业务配置方法实施例一的信令流程图。本实施例涉及的是在发送给MANO的网络服务实例化请求中携带与运营商的网络环境相关的业务配置事件，使得MANO根据该业务配置事件向配置***发送业务配置信息，从而使得配置***根据该业务配置信息对当前的网络服务进行业务配置的具体过程。如图2所示，该方法可以包括：
S101：MANO接收网络服务实例化请求。
其中，所述网络服务实例化请求包括：预设的与运营商网络环境相关的网络服务的业务配置事件。可选的，该业务配置事件可以有效的反映当前运营商的网络环境，并且可以为NFV MANO***中的网络服务在当前运营商的网络环境中进行业务配置时直接或者间接的提供业务配置所需的参数或者脚本等，本申请实施例对业务配置事件的形式或者内容并不做限定，只要其能够使得NFV MANO***中的网络服务在不中断实例化流程或者其他流程的情况下自动完成业务配置即可。可选的，上述运营商的网络环境可以是具体的运营商网络中的IP地址的个数、还可以是运营商网络中信令点的全局资源的多少等，本申请对运营商网络环境的具体内容并不做限定。
另外，本实施例中的网络服务实例化请求可以是操作员向MANO发起的，还可以是其他的软件或者硬件设备向MANO发起的。可选的，以操作员为例，操作员可以向MANO发送网络服务实例化请求，MANO可以将该网络服务实例化请求传送给内部的VNFM，使得VNFM解析该网络服务实施化请求。可选的，本实施例所涉及的网络服务，可以单纯的由VNF以及各个VNF之间的链路组成，还可以由VNF、PNF以及VNF和PNF之间的链路组成，该链路可以包括VNF与VNF之间的链路，还可以包括VNF和PNF之间的链路，还可以包括PNF和PNF之间的链路。因此，上述网络服务实例化请求可以为VNF实例化请求，还可以为NS实例化请求(若是该NS实例化请求，则要求既对VNF完成业务配置，也要完成对PNF的业务配置)。
可选的，以网络服务包括单纯的VNF为例，在MANO获得该网络服务实例化请求之前，VNF供应商可以在VNF包文件(VNF Package)中预先定义业务配置事件。当VNF供应商定义了业务配置事件之后，在运营商进行网络设计阶段，操作员可以结合当前的运营商网络环境对这些业务配置事件进行编辑修改，获得适应于当前运营商网络环境的业务配置事件。当网络服务包括VNF和PNF时，业务配置事件的定义和修改也可以参照上述描述进行，不同的是增加了PNF的业务配置事件的定义和修改。
可选的，上述网络服务实例化请求中可以携带VNFD，还可以携带PNFD，还可 以携带NSD，则上述预设的与运营商网络环境相关的网络服务的业务配置事件可以包含在VNFD中，还可以包括在PNFD中，还可以包含在NSD中，具体以网络服务包括的网元类型为参照。其中，VNFD可以用于描述VNF对资源的需求等信息，PNFD可以用于描述PNF对资源的需求等信息，NSD是网络服务对应的网络服务描述模板，可以用于描述NS的信息，例如描述一个NS中包括的VNF和PNF的个数，以及各网元之间的链路等，该NSD中可以包括VNFD，还可以包括PNFD，具体以网络服务包括的网元类型为参照。
S102：MANO解析该网络服务实例化请求，获得业务配置事件。
具体的，MANO接收到网络服务实例化请求后，对其进行解析处理，不仅可以获得上述业务配置事件，还可以获知网络服务实例化请求中的VNFD或者PNFD或者NSD中相关的NFVI资源分配信息以及业务软件安装信息。因此，MANO可以根据所解析得到的网络服务所需的NFVI资源分配信息以及业务软件安装信息，完成对网络服务的资源分配和业务安装。
S103：MANO根据上述业务配置事件向配置***发送业务配置信息。
可选的，MANO可以在完成对网络服务的资源分配和业务安装后，根据上述业务配置事件向配置***发送业务配置信息，还可以是在对网络服务的资源分配和业务安装的同时根据上述业务配置事件向配置***发送业务配置信息，还可以是在对网络服务的资源分配和业务安装之前根据上述业务配置事件向配置***发送业务配置信息，本申请实施例对MANO发送业务配置信息给配置***的时机并不做限制。另外，业务配置信息与业务配置事件相关，其可以是业务配置事件的直接形式或者间接形式，还可以是其他的与业务配置事件相关的信息，本申请实施例对业务配置信息的具体形式并不做限定，只要其能够使得NFV MANO***中的网络服务在不中断实例化流程或者其他流程的情况下自动完成业务配置即可。
S104：配置***根据该业务配置信息对网络服务进行业务配置。
具体的，当上述业务配置信息是MANO在完成对网络服务的资源分配和业务安装后发送给配置***的，则配置***在接收到该业务配置信息之后直接根据该业务配置信息对网络服务进行业务配置；当上述业务配置信息是MANO在对网络服务的资源分配和业务安装之前或者是在MANO对网络服务的资源分配和业务安装的同时发送给配置***的，则配置***在接收到该业务配置信息之后需要等到MANO完成对网络服务的资源分配和业务安装后，才可根据该业务配置信息对网络服务进行业务配置，可选的，MANO可以通知配置***当前对网络服务的资源分配和业务软件安装的进度。
本申请实施例提供的网络服务的业务配置方法，通过在发送给MANO的网络服务实例化请求中携带预设的与运营商网络环境相关的网络服务的业务配置事件，使得MANO可以根据该业务配置事件向配置***发送业务配置信息，进而使得配置***在MANO完成对网络服务的资源分配和业务软件安装后，根据该业务配置信息对网络服务进行业务配置。本实施例提供的方法，在网络服务实例化请求中携带预先配置好的与运营商现网环境相关的业务配置事件，从而并不需要人为中断网络服务的实例化流程，即并不需要在网络服务业务配置阶段人为修改业务配置命令，避免 了人为编辑修改所带来的配置错误，并且由于网络服务的实例化流程并未中断，因此也提高了网络服务的上线效率。
进一步地，上述网络服务实例化请求中所包含的业务配置事件，可以用于指示在当前操作场景下网络服务应该执行的业务配置模板或工作流。在一种可能的设计中，该业务配置事件可以包括当前场景下网络服务应该执行的业务配置模板的标识或者工作流的标识，而对应的业务配置模板或者工作流可以存储在MANO对应的目录服务器中。可选的，在另一种可能的设计中，该业务配置事件可以直接包括当前场景下网络服务应该执行的业务配置模板或者工作流的具体内容。
需要说明的是，这里的操作场景可以为网络服务的任一操作场景，例如对网络服务进行软件或者硬件升级的场景、或者是对网络服务增加容量或者减少容量的场景，本申请实施例对当前的操作场景并不做限定。该业务配置事件所指示的业务配置模板中可以包括多条供网络服务执行的配置命令行，该业务配置模板可以包括初始化配置模板、弹性配置模板、升级配置模板、安全矩阵配置模板中的任一个，该业务配置事件所指示的工作流可以是用来指示网络服务下一步执行的配置动作。
作为本申请实施例的一种可能的实施方式，本实施例涉及的是MANO将从网络服务实例化请求中解析得到的业务配置事件直接发送给配置***的具体过程。即上述S102具体可以包括：MANO向配置***发送业务配置事件，以使所述配置***根据所述业务配置事件对所述网络服务进行业务配置。
具体的，在该可能的实施方式下，业务配置事件可以包括当前场景下网络服务应该执行的业务配置模板的标识或者工作流的标识，这样MANO将该业务配置事件发送给配置***之后，配置***就可以通过业务配置事件中的业务配置模板的标识或者工作流的标识，从MANO对应的目录服务器中获取当前场景下网络服务所应执行的业务配置模板或者工作流，进而根据该业务配置模板或者工作流对网络服务进行业务配置；可选的，该业务配置事件也可以直接包括当前场景下网络服务应该执行的业务配置模板或者工作流的具体内容，MANO可以直接将这些内容发送给配置***，使得配置***可以根据这些内容对网络服务进行业务配置。
作为本申请实施例的另一种可能的实施方式，本实施例涉及的是MANO根据网络服务实例化请求中业务配置事件生成业务配置命令，将该业务配置命令发送给配置***的具体过程。即，上述S102具体可以包括：MANO根据业务配置事件生成业务配置命令，并将该业务配置命令发送给配置***，以使配置***根据所述业务配置命令对所述网络服务进行业务配置。
在该可能的实施方式下，业务配置事件可以包括当前场景下网络服务应该执行的业务配置模板的标识或者工作流的标识，使得MANO在获得该业务配置事件之后，通过业务配置事件中的业务配置模板的标识或者工作流的标识，从MANO对应的目录服务器中获取当前场景下网络服务所应执行的业务配置模板或者工作流，进而根据该业务配置模板或者工作流生成业务配置命令发送给配置***，使得配置***根据该业务配置命令对网络服务进行业务配置；可选的，该业务配置事件也可以直接包括当前场景下网络服务应该执行的业务配置模板或者工作流的具体内容，使得MANO可以直根据这些内容生成业务配置命令，从而发送给配置***，使得配置 ***根据该业务配置命令对网络服务进行业务配置。
上述两种可能的实施方式所提供的网络服务的业务配置方法，MANO与配置***所交互的业务配置信息可以包括不同的形式，丰富了MANO与配置***交互的多样性，进而也提高了网络服务在进行业务配置时的可靠性。
图3为本申请实施例提供的网络服务的业务配置方法实施例二的信令流程图。本实施例涉及的是MANO和配置***进行业务配置信息的交互，共同完成对网络服务进行业务配置的具体过程。在上述实施例的基础上，上述业务配置事件包括业务配置事件名称、所述当前场景下的业务配置模板和执行所述业务配置模板时所需的业务参数。可选的，该业务配置事件中的当前场景下的业务配置模板和执行所述业务配置模板时所需的业务参数，也可以被替换为“当前场景下的工作流和执行所述工作流时所需的业务参数”。本实施例中的业务配置事件所包括的内容是以前者为例来进行说明的。参见图3所示，该方法包括：
S201：MANO接收网络服务实例化请求。
S202：MANO解析该网络服务实例化请求，获得业务配置事件；该业务配置事件包括：业务配置事件名称、所述当前场景下的业务配置模板和执行所述业务配置模板时所需的业务参数。
具体的，上述S201和S202的具体过程可以参照上述实施例的具体描述，在此不再赘述。上述业务配置事件可以参见表1所示的信息模型，该业务配置事件中的业务配置事件名称可以为任一类型的字符或者字段，上述业务配置事件中的当前操作场景下的业务配置模板可以是具体的业务配置脚本，还可以是指向具体的业务配置脚本的路径信息，即当前操作场景下的业务配置模板中可以包括具体的业务配置脚本，还可以包括指向该业务配置脚本的路径信息，该路径信息指向某个服务器的Config中，并且，上述当前操作场景可以包括初始化场景、弹性场景、升级场景、安全矩阵场景、服务终结场景中的任一个；上述业务配置事件中的执行业务配置模板时所需的业务参数可以包括本端的IP地址、本端的端口号Port、对端的IP地址、对端的Port、所述网络服务支持的业务类型中的至少一个参数。具体参见表1所示：
表1
Figure PCTCN2017076928-appb-000001
另外，需要说明的是，上述网络服务可以包括VNF，或者，该网络服务可以包括VNF和PNF。
可选的，当该网络服务为VNF时，上述网络服务实例化请求为VNF实例化请 求，则上述网络服务实例化请求中的业务配置事件可以是携带在VNF实例化请求中的VNFD的业务配置事件，该业务配置事件可以用于指示在当前操作场景下该VNF执行的业务配置模板或工作流。可选的，当业务配置事件还可以用于指示在当前操作场景下该VNF的虚拟化部署单元(Virtualization Deployment Unit，简称VDU)所应执行的业务配置模板或工作流，其中，一个VNF可以包括多个VDU。
可选的，当该网络服务为VNF和PNF时，则上述网络服务实例化请求中的业务配置事件可以是携带在NSD中的业务配置事件，该业务配置事件可以用于指示在当前操作场景下VNF所应执行的第一业务配置模板或第一工作流，以及，用于指示PNF所应执行的第二业务配置模板或第二工作流。可选的，该业务配置事件可以分为两部分，一部分携带在NSD中的VNFD中，一部分携带在NSD中的PNFD中。
S203：MANO根据所述业务配置事件名称、所述当前操作场景下的业务配置模板和所述业务参数生成业务配置命令。
具体的，MANO在解析业务配置事件得到业务配置事件名称、当前操作场景下的业务配置模板和执行该业务配置模板所需的业务参数后，MANO可以根据这三者自动生成业务配置命令，该业务配置命令可以包括至少一条命令行。需要说明的是，MANO生成业务配置命令的过程与MANO对网络服务进行NFVI资源分配和业务软件安装的过程之间没有时序关系的限定，可以是同时进行，还可以是一前一后进行。
S204：MANO将所述业务配置命令发送至所述配置***。
需要说明的是，MANO需要在根据网络服务实例化请求完成对网络服务的NFVI资源分配和业务软件安装后，将该业务配置命令发送给配置***。
S205：配置***将该业务配置命令发送给网络服务。
具体的，配置***将业务配置命令发送给网络服务，可以包括两种发送方式，具体为：
第一种：配置***可以将接收到的业务配置命令放在内存或者缓存中，然后配置***在与网络服务建立连接后，配置***将内存或者缓存中的配置命令中的命令行一条一条的发给网络服务，可以是第一条命令行发给网络服务，网络服务执行成功后，再发第二条命令行，以此类推。当网络服务执行某一条命令行失败时，可以进入配置回滚状态，由配置***重新下发该条命令行。
第二种：配置***直接将业务配置命令的所有命令行发送给VNF。
S206：网络服务执行该业务配置命令，对网络服务进行业务配置。
S207：网络服务向配置***发送业务配置结果。
上述所涉及的业务配置命令是由MANO根据业务配置事件生成的，可替换的，上述S203和S204可以被替换为下述S203’至S205’，具体为：
S203’：MANO将业务配置事件发送给配置***。
S204’：配置***解析所述业务配置事件，获得所述业务配置事件名称、所述当前场景下的业务配置模板和所述业务参数。
S205’：配置***根据所述业务配置事件名称、所述当前场景下的业务配置模板和所述业务参数生成业务配置命令。
需要说明的是，上述MANO中可以提供一个全局资源管理功能，使得MANO可以生成具体的业务配置命令，这样做的好处是，在运营商现网中配置***往往是已有的存量***，不适宜对配置***做过多的修改适配工作，能够在MANO上生成具体的业务配置命令会减轻对配置***的修改适配工作量。另外，在准备阶段，操作员根据运营商网络环境对VNF供应商已经定义的业务配置事件进行编辑修改时所用的设计工具(Designer)可以是由MANO提供的，除此之外，MANO还可以提供一个网络服务的业务配置脚本的编辑工具，通过这个工具可以便捷的将网元供应商提供的业务配置模板和运营商的现网资源相关联，使得MANO或者配置***可以自动生成业务配置命令，无需人为配置，降低了因人为编辑修改所带来的配置错误。
为了更清楚的解释本申请实施例的具体过程，以VNF实例化流程为例，上述网络服务为VNF，上述配置***可以为EM，参见图4所示，该方法包括：
S301：VNFM接收VNF实例化请求。
S302：VNFM解析该VNF实例化请求中的VNFD，获得VNFD中的业务配置事件；该业务配置事件包括：业务配置事件名称、所述当前场景下的业务配置模板和执行所述业务配置模板时所需的业务参数。
S303：VNFM根据上述VNFD对VNF进行NFVI资源的分配和业务软件的安装。
需要说明的是，上述S302和S303之间没有时序关系的限制。
S304：VNFM将业务配置事件发送给EM。
需要说明的是，上述S303和S304之前没有时序关系的限制。这里VNFM和EM之间具有消息接口，通过该消息接口，VNFM可以向EM提供表征VNF部署情况的业务配置事件，同时EM也可通过此接口向VNFM提供VNF的业务配置结果。
S305：EM在接收到业务配置事件之后，解析该业务配置事件，获得业务配置事件名称、当前场景下的业务配置模板和业务参数。
S306：EM根据所述业务配置事件名称、所述当前场景下的业务配置模板和所述业务参数生成业务配置命令。
S307：EM将该业务配置命令发送给VNF。
需要说明的是，EM将业务配置命令发送给VNF需要在MANO完成对VNF的NFVI资源和业务软件安装之后才可以将业务配置命令发送给VNF。
S308：VNF执行该业务配置命令。
S309：VNF向EM发送业务配置结果。
上述S301至S309的具体过程可以参照上述S201至S207的具体操作过程，在此不再赘述。
本申请实施例提供的网络服务的业务配置方法，通过在发送给MANO的网络服务实例化请求中携带预设的与运营商网络环境相关的网络服务的业务配置事件，使得MANO可以根据业务配置事件生成业务配置命令，并将该业务配置命令发送给配置***，进而使得配置***根据该业务配置命令完成对网络服务的业务配置。本实施例提供的方法，在网络服务实例化请求中携带预先配置好的与运营商现网环境相关的业务配置事件，从而并不需要人为中断网络服务的实例化流程，即并不需要在网络服务业务配置阶段人为修改业务配置命令，避免了人为编辑修改所带来的配置 错误，并且实现了网络服务的自动化业务配置，另外由于网络服务的实例化流程并未中断，因此也提高了网络服务的上线效率。
图5为本申请实施例提供的网络服务的业务配置装置实施例一的结构示意图。该业务配置装置可以通过软件、硬件或者软硬结合的方式实现管理编排器MANO的部分或者全部。如图5所示，该装置包括接收模块10和发送模块20。
其中，接收模块10，用于接收网络服务实例化请求，所述网络服务实例化请求包括：预设的与运营商网络环境相关的网络服务的业务配置事件；
发送模块20，用于根据所述业务配置事件向配置***发送业务配置信息，以使所述配置***根据所述业务配置信息对所述网络服务进行业务配置。
可选的，上述接收模块10可以对应于MANO中具有通信功能和接收信息功能的输入接口或者输入组件，上述发送模块20可以对应于MANO中具有通信功能和发送信息功能的输出接口或者输出组件。
本申请实施例提供的网络服务的业务配置装置，可以执行上述方法实施例，其实现原理和技术效果类似，在此不再赘述。
可选的，所述业务配置事件用于指示在当前操作场景下所述网络服务执行的业务配置模板或工作流。
可选的，所述业务配置事件包括业务配置事件名称、所述当前场景下的业务配置模板和执行所述业务配置模板时所需的业务参数。
可选的，所述发送模块20，具体用于向配置***发送业务配置事件，以使所述配置***根据所述业务配置事件对所述网络服务进行业务配置。
可选的，参见图6所示的网络服务的业务配置装置实施例二。在上述实施例的基础上，上述发送模块20，可以包括生成单元21和发送单元22。
生成单元21，用于根据所述业务配置事件中的所述业务配置事件名称、所述当前操作场景下的业务配置模板和所述业务参数生成业务配置命令；
发送单元22，用于将所述业务配置命令发送至所述配置***，以使所述配置***根据所述业务配置命令对所述网络服务进行业务配置。
进一步地，所述接收模块10，还用于接收所述配置***发送的业务配置结果。
可选的，所述网络服务为虚拟网络功能VNF，所述网络服务实例化请求为VNF实例化请求，所述业务配置事件用于指示在当前操作场景下所述VNF执行的业务配置模板或工作流。可选的，所述业务配置事件携带在所述VNF实例化请求中的虚拟网络功能描述VNFD中。
可选的，所述网络服务包括虚拟网络功能VNF和物理网络功能PNF，所述业务配置事件用于指示在当前操作场景下所述VNF执行的第一业务配置模板或第一工作流，以及所述PNF执行的第二业务配置模板或第二工作流。可选的，所述业务配置事件携带在所述网络服务实例化请求中的网络服务描述NSD中。
可选的，所述业务配置事件还用于指示在当前操作场景下所述VNF的虚拟化部署单元VDU执行的业务配置模板或工作流。
可选的，所述当前操作场景包括初始化场景、弹性场景、升级场景、安全矩阵场景、服务终结场景中的任一个，
所述业务参数包括本端的IP地址、本端的端口号Port、对端的IP地址、对端的Port、所述网络服务支持的业务类型中的至少一个参数。
本申请实施例提供的网络服务的业务配置装置，可以执行上述方法实施例，其实现原理和技术效果类似，在此不再赘述。
图7为本申请实施例提供的网络服务的业务配置装置实施例三的结构示意图。该业务配置装置可以通过软件、硬件或者软硬结合的方式实现配置***的部分或者全部。如图7所示，该装置包括接收模块30和配置模块31。
其中，接收模块30，用于接收管理编排器MANO根据与运营商网络环境相关的网络服务的业务配置事件发送的业务配置信息；
配置模块31，用于根据所述业务配置信息对所述网络服务进行业务配置。
可选的，上述接收模块30可以对应于配置***中具有通信功能和接收信息功能的输入接口或者输入组件，上述配置模块31可以对应于配置***中具有业务配置功能以及其他功能的处理组件或者处理芯片。
本申请实施例提供的网络服务的业务配置装置，可以执行上述方法实施例，其实现原理和技术效果类似，在此不再赘述。
可选的，所述业务配置事件用于指示在当前操作场景下所述网络服务执行的业务配置模板或工作流。
可选的，所述业务配置事件包括业务配置事件名称、所述当前场景下的业务配置模板和执行所述业务配置模板时所需的业务参数。
图8为本申请实施例提供的网络服务的业务配置装置实施例四的结构示意图。在上述实施例的基础上，进一步地，上述配置模块31，可以包括：解析单元32、生成单元33和配置单元34。
其中，解析单元32，用于解析所述业务配置事件，获得所述业务配置事件名称、所述当前场景下的业务配置模板和所述业务参数；
生成单元33，用于根据所述业务配置事件名称、所述当前场景下的业务配置模板和所述业务参数生成业务配置命令；
配置单元34，用于根据所述业务配置命令对所述网络服务进行业务配置。
可选的，上述装置还可以包括发送模块35，用于向所述MANO发送业务配置结果。
可选的，所述接收模块30，具体用于接收所述MANO发送的业务配置命令，所述业务配置命令为所述MANO根据所述业务配置事件名称、所述当前场景下的业务配置模板和所述业务参数生成的；所述配置模块31，具体用于根据所述业务配置命令对所述网络服务进行业务配置。
可选的，所述网络服务包括虚拟网络功能VNF，所述业务配置事件用于指示在当前操作场景下所述VNF执行的业务配置模板或工作流。可选的，所述业务配置事件携带在所述MANO接收的VNF实例化请求中的虚拟网络功能描述VNFD中。
可选的，所述网络服务包括虚拟网络功能VNF和物理网络功能PNF，所述业务配置事件用于指示在当前操作场景下所述VNF执行的第一业务配置模板或第一工作流，以及，所述PNF执行的第二业务配置模板或第二工作流。可选的，所述业务配 置事件携带在所述MANO接收的网络服务实例化请求中的网络服务描述NSD中。
可选的，所述业务配置事件还用于指示在当前操作场景下所述VNF的虚拟化部署单元VDU执行的业务配置模板或工作流。
可选的，所述当前操作场景包括初始化场景、弹性场景、升级场景、安全矩阵场景、服务终结场景中的任一个，所述业务参数包括本端的IP地址、本端的端口号Port、对端的IP地址、对端的Port、所述网络服务支持的业务类型中的至少一个参数。
本申请实施例提供的网络服务的业务配置装置，可以执行上述方法实施例，其实现原理和技术效果类似，在此不再赘述。
图9为本申请实施例提供的管理编排器实施例的结构示意图。如图9所示，该管理编排器可以包括接收器40、发送器41、存储器42、处理器43和至少一个通信总线44。通信总线44用于实现元件之间的通信连接。存储器42可能包含高速RAM存储器，也可能还包括非易失性存储NVM，例如至少一个磁盘存储器，存储器42中可以存储各种程序，用于完成各种处理功能以及实现本实施例的方法步骤。另外，本实施例中的接收器40可以为相应的具有通信功能和接收信息功能的输入接口，本实施例中的发送器41可以为相应的具有通信功能和发送信息功能的输出接口，该发送器41和接收器40可以集成在一个通信接口中，也可以分别为独立的两个通信接口。该处理器43例如可以为中央处理器(Central Processing Unit，简称CPU)，还可以为具有生成业务配置命令功能以及其他功能的处理芯片。
需要说明的是，该通信总线可以是ISA(Industry Standard Architecture，工业标准体系结构)总线、PCI(Peripheral Component Interconnect，外部设备互连)总线或EISA(Extended Industry Standard Architecture，扩展工业标准体系结构)总线等。所述通信总线可以是一条或多条物理线路，当是多条物理线路时可以分为地址总线、数据总线、控制总线等。
在本申请实施例中，接收器40，用于接收网络服务实例化请求，所述网络服务实例化请求包括：预设的与运营商网络环境相关的网络服务的业务配置事件；
发送器41，用于根据所述业务配置事件向配置***发送业务配置信息，以使所述配置***根据所述业务配置信息对所述网络服务进行业务配置。
该MANO可以包括NFVO、VNFM和VIM三种组件，即NFVO、VNFM和VIM均属于MANO的一部分，三者可以分别部署在不同的硬件设备上通过物理连接构成MANO的全部或者部分，也可以部署在同一个硬件设备上(即在该硬件设备上加载具有上述NFVO、VNFM和VIM的功能的软件即可)构成MANO的全部或者部分。可选的，当MANO包括部署在不同硬件设备上的NFVO、VNFM和VIM时，上述接收器40、发送器41和处理器43可以集成在VNFM上；可选的，当MANO包括部署在同一硬件设备上的NFVO、VNFM和VIM时，对接收器40和发送器41的集成位置不做限定。
可选的，所述业务配置事件用于指示在当前操作场景下所述网络服务执行的业务配置模板或工作流。
可选的，所述业务配置事件包括业务配置事件名称、所述当前场景下的业务配置模板和执行所述业务配置模板时所需的业务参数。
可选的，所述发送器41，具体用于向配置***发送业务配置事件，以使所述配置***根据所述业务配置事件对所述网络服务进行业务配置。
可选的，所述处理器43，用于根据所述业务配置事件中的所述业务配置事件名称、所述当前操作场景下的业务配置模板和所述业务参数生成业务配置命令；所述发送器41，用于将所述处理器43生成的所述业务配置命令发送至所述配置***，以使所述配置***根据所述业务配置命令对所述网络服务进行业务配置。
可选的，所述接收器40，还用于接收所述配置***发送的业务配置结果。
可选的，所述网络服务为虚拟网络功能VNF，所述网络服务实例化请求为VNF实例化请求，所述业务配置事件用于指示在当前操作场景下所述VNF执行的业务配置模板或工作流。可选的，所述业务配置事件携带在所述VNF实例化请求中的虚拟网络功能描述VNFD中。
可选的，所述网络服务包括虚拟网络功能VNF和物理网络功能PNF，所述业务配置事件用于指示在当前操作场景下所述VNF执行的第一业务配置模板或第一工作流，以及所述PNF执行的第二业务配置模板或第二工作流。可选的，所述业务配置事件携带在所述网络服务实例化请求中的网络服务描述NSD中。
可选的，所述业务配置事件还用于指示在当前操作场景下所述VNF的虚拟化部署单元VDU执行的业务配置模板或工作流。
可选的，所述当前操作场景包括初始化场景、弹性场景、升级场景、安全矩阵场景、服务终结场景中的任一个，
所述业务参数包括本端的IP地址、本端的端口号Port、对端的IP地址、对端的Port、所述网络服务支持的业务类型中的至少一个参数。
本申请实施例提供的管理编排器，可以执行上述方法实施例，其实现原理和技术效果类似，在此不再赘述。
图10为本申请实施例提供的配置***实施例的结构示意图。该配置***可以是EM，还可以是OSS。如图10所示，该配置***可以包括：接收器50、存储器51、处理器52和至少一个通信总线53。可选的，还可以包括发送器54。通信总线53用于实现元件之间的通信连接。存储器51可能包含高速RAM存储器，也可能还包括非易失性存储器NVM，例如至少一个磁盘存储器，存储器51中可以存储各种程序，用于完成各种处理功能以及实现本实施例的方法步骤。另外，本实施例中的接收器50可以为相应的具有通信功能和接收信息功能的输入接口，本实施例中的发送器54可以为相应的具有通信功能和发送信息功能的输出接口，该发送器54和接收器50可以集成在一个通信接口中，也可以分别为独立的两个通信接口。该处理器52例如可以为中央处理器52(Central Processing Unit，简称CPU)，还可以为具有业务配置功能以及其他功能的处理芯片。
在本实施例中，接收器50，用于接收管理编排器MANO根据与运营商网络环境相关的网络服务的业务配置事件发送的业务配置信息；
处理器52，用于根据所述业务配置信息对所述网络服务进行业务配置。
可选的，所述业务配置事件用于指示在当前操作场景下所述网络服务执行的业务配置模板或工作流。
可选的，所述业务配置事件包括业务配置事件名称、所述当前场景下的业务配置模板和执行所述业务配置模板时所需的业务参数。
可选的，所述处理器52，具体用于解析所述业务配置事件，获得所述业务配置事件名称、所述当前场景下的业务配置模板和所述业务参数，并根据所述业务配置事件名称、所述当前场景下的业务配置模板和所述业务参数生成业务配置命令，并根据所述业务配置命令对所述网络服务进行业务配置。
可选的，所述接收器50，具体用于接收所述MANO发送的业务配置命令，所述业务配置命令为所述MANO根据所述业务配置事件名称、所述当前场景下的业务配置模板和所述业务参数生成的；所述处理器52，具体用于所述业务配置命令对所述网络服务进行业务配置。
可选的，所述发送器54，用于向所述MANO发送业务配置结果。
可选的，所述网络服务包括虚拟网络功能VNF，所述业务配置事件用于指示在当前操作场景下所述VNF执行的业务配置模板或工作流。可选的，所述业务配置事件携带在所述MANO接收的VNF实例化请求中的虚拟网络功能描述VNFD中。
可选的，所述网络服务包括虚拟网络功能VNF和物理网络功能PNF，所述业务配置事件用于指示在当前操作场景下所述VNF执行的第一业务配置模板或第一工作流，以及，所述PNF执行的第二业务配置模板或第二工作流。可选的，所述业务配置事件携带在所述MANO接收的网络服务实例化请求中的网络服务描述NSD中。
可选的，所述业务配置事件还用于指示在当前操作场景下所述VNF的虚拟化部署单元VDU执行的业务配置模板或工作流。
可选的，所述当前操作场景包括初始化场景、弹性场景、升级场景、安全矩阵场景、服务终结场景中的任一个，所述业务参数包括本端的IP地址、本端的端口号Port、对端的IP地址、对端的Port、所述网络服务支持的业务类型中的至少一个参数。
本申请实施例提供的配置***，可以执行上述方法实施例，其实现原理和技术效果类似，在此不再赘述。
图11为本申请实施例提供的网络服务的业务配置***实施例的结构示意图。如图11所示，该业务配置***可以包括上述MANO和配置***。该业务配置***可以应用于图1所示的NFV MANO架构图一中，也可以应用图12所示的NFV MANO架构图二中。该图12所示的NFV MANO架构图为上述图1所示的NFV MANO架构图的细化。为了更清楚的说明业务配置***的工作原理和有益效果，本实施例首先以图12为例介绍该NFV MANO架构。
图12中，NFV MANO***可以通过多种网络实现，例如数据中心网络、服务提供者网络、或者局域网(Local Area Network,LAN)。该NFV MANO***可以包括MANO 128，NFVI 130，多个VNF 108，多个网元管理***(element management system,EMS)122，服务、VNF和基础设施描述(Service,VNF and Infrastructure Description)***126，以及一个或多个OSS/BSS 124。需要说明的是，本申请实施例中的配置***可以是图12中的OSS，还可以是图12中的EMS。
MANO128可以包括网络功能虚拟化编制器(Network Function Virtulization  Orchestration，简称NFVO)102、一个或多个VNF管理器(VNF Manager，简称VNFM)104，以及一个或多个虚拟基础设施管理器(Virtualized Infrastructure Manager，简称VIM)106。
NFVI 130可以包括计算硬件112、存储硬件114、网络硬件116组成的硬件资源层、虚拟化层、以及虚拟计算110(例如虚拟机)、虚拟存储118和虚拟网络120组成的虚拟资源层。计算硬件112可以为专用的处理器或通用的用于提供处理和计算功能的处理器。存储硬件114用于提供存储能力，该存储能力可以是存储硬件114本身提供的(例如一台服务器的本地内存)，也可以通过网络提供(例如服务器通过网络连接一个网络存储设备)。网络硬件116可以是交换机、路由器和/或其他网络设备，网络硬件116用于实现多个设备之间的通信，多个设备之间通过无线或有线连接。NFVI130中的虚拟化层用于抽象硬件资源层的硬件资源，将VNF108和硬件资源所属的物理层解耦，向VNF提供虚拟资源。如图12所示，虚拟资源可以包括虚拟计算110、虚拟存储118和虚拟网络120。虚拟计算110、虚拟存储118可以以虚拟机或其他虚拟容器的形式向VNF108提供，例如一个或多个VNF108可以部署在一台虚拟机上。虚拟化层通过抽象网络硬件116形成虚拟网络120。虚拟网络120，例如虚拟交换机(例如Vswitches)，用于实现多个虚拟机之间，或多个承载VNF的其他类型的虚拟容器之间的通信。网络硬件的虚拟化可以通过虚拟LAN(Vritual LAN,VLAN)、虚拟专用局域网业务(Virtual Private LAN Service,VPLS)、虚拟可扩展局域网(Virtual eXtensible Local Area Network,VxLAN)或通用路由封装网络虚拟化(Nerwork Virtualization using Generic Routing Encapsulation，NVGRE)等技术实现。
OSS/BSS124主要面向电信服务运营商，提供综合的网络管理和业务运营功能，包括网络管理(例如故障监控、网络信息收集等)、计费管理以及客户服务管理等。VNF和基础设施描述***126在ETSI GS NFV 002v1.1.1标准中有详细介绍，本申请实施例在此不再赘述。
上述MANO128可以用于实现VNF 108和NFVI 130的监控和管理。NFVO102可以与一个或多个VNFM104通信以实现与资源相关的请求、发送配置信息给VNFM104、以及收集VNF 108的状态信息。另外，NFVO102还可以与VIM106进行通信以实现资源分配，和/或实现虚拟化硬件资源的配置信息和状态信息的预留和交换。VNFM104可以用于管理一个或多个VNF 108，执行各种管理功能，例如初始化、更新、查询、和/或终止VNF 108。VIM106可以用于控制和管理VNF108和计算硬件112、存储硬件114、网络硬件116、虚拟计算110、虚拟存储118、虚拟网络120的交互。例如，VIM106可以用于执行资源向VNF108的分配操作。VNFM104和VIM106可以互相通信以交换虚拟化硬件资源配置和状态信息。
NFVI 130包含硬件和软件，二者共同建立虚拟化环境以部署、管理和执行VNF108。换句话说，硬件资源层和虚拟资源层用于向VNF108提供虚拟资源，例如虚拟机和/或其他形式的虚拟容器。
继续参照图12所示，VNFM104可以与VNF108和EMS122通信以执行VNF生命周期管理和实现配置信息/状态信息的交换。VNF108是至少一个网络功能的虚拟化，该网络功能之前是由物理网络设备提供的。在一种实现方式下，VNF108可以是 一个虚拟化的移动管理实体(Mobility Management Entity，MME)节点，用于提供典型的非虚拟化的MME设备提供的所有网络功能。在另一种实现方式下，VNF108可以用于实现非虚拟化的MME设备上提供的全部组件中的部分组件的功能。一个虚拟机(或其他形式的虚拟容器)上可以部署有一个或多个VNF108。EMS122可以用于管理一个或多个VNF。
因此，结合图12所示的NFV MANO的架构，本申请实施例所涉及的业务配置***可以包括MANO60和配置***70。
其中，该MANO60，用于接收网络服务实例化请求，并根据所述业务配置事件向配置***70发送业务配置信息；所述网络服务实例化请求包括：预设的与运营商网络环境相关的网络服务的业务配置事件；
配置***70，用于接收MANO70根据与运营商网络环境相关的网络服务的业务配置事件发送的业务配置信息，并根据所述业务配置信息对所述网络服务进行业务配置。
可选的，所述业务配置事件用于指示在当前操作场景下所述网络服务执行的业务配置模板或工作流。
可选的，所述业务配置事件包括业务配置事件名称、所述当前场景下的业务配置模板和执行所述业务配置模板时所需的业务参数。
可选的，所述MANO60，具体用于向配置***70发送业务配置事件，以使所述配置***70根据所述业务配置事件对所述网络服务进行业务配置；
所述配置***70，具体用于解析所述业务配置事件，获得所述业务配置事件名称、所述当前场景下的业务配置模板和所述业务参数，并根据所述业务配置事件名称、所述当前场景下的业务配置模板和所述业务参数生成业务配置命令，并根据所述业务配置命令对所述网络服务进行业务配置。
可选的，所述MANO60，具体用于根据所述业务配置事件中的所述业务配置事件名称、所述当前操作场景下的业务配置模板和所述业务参数生成业务配置命令，并将所述业务配置命令发送至所述配置***70，以使所述配置***70根据所述业务配置命令对所述网络服务进行业务配置；
所述配置***70，具体用于接收所述MANO60发送的业务配置命令，并根据所述业务配置命令对所述网络服务进行业务配置。
可选的，所述配置***70，还用于向所述MANO60发送业务配置结果；所述MANO60，还用于接收所述配置***70发送的业务配置结果。
可选的，所述网络服务为虚拟网络功能VNF，所述网络服务实例化请求为VNF实例化请求，所述业务配置事件用于指示在当前操作场景下所述VNF执行的业务配置模板或工作流。可选的，所述业务配置事件携带在所述VNF实例化请求中的虚拟网络功能描述VNFD中。
可选的，所述网络服务包括虚拟网络功能VNF和物理网络功能PNF，所述业务配置事件用于指示在当前操作场景下所述VNF执行的第一业务配置模板或第一工作流，以及所述PNF执行的第二业务配置模板或第二工作流。可选的，所述业务配置事件携带在所述网络服务实例化请求中的网络服务描述NSD中。
可选的，所述业务配置事件还用于指示在当前操作场景下所述VNF的虚拟化部署单元VDU执行的业务配置模板或工作流。
可选的，所述当前操作场景包括初始化场景、弹性场景、升级场景、安全矩阵场景、服务终结场景中的任一个，所述业务参数包括本端的IP地址、本端的端口号Port、对端的IP地址、对端的Port、所述网络服务支持的业务类型中的至少一个参数。
本申请实施例提供的网络服务的业务配置***，可以执行上述方法实施例，其工作原理和技术效果类似，在此不再赘述。
本说明书中的各个实施例均采用递进的方式描述，各个实施例之间相同相似的部分互相参见即可，每个实施例重点说明的都是与其他实施例的不同之处。尤其，对于装置实施例而言，由于其基本相似于方法实施例，所以描述得比较简单，相关之处参见方法实施例的部分说明即可。以上所描述的装置实施例仅仅是示意性的，其中所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部模块来实现本实施例方案的目的。本领域普通技术人员在不付出创造性劳动的情况下，即可以理解并实施。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的***、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的***、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个***，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可 以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(ROM，Read-Only Memory)、随机存取存储器(RAM，Random Access Memory)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以所述权利要求的保护范围为准。

Claims (48)

  1. 一种网络服务的业务配置方法，其特征在于，包括：
    接收网络服务实例化请求，所述网络服务实例化请求包括：预设的与运营商网络环境相关的网络服务的业务配置事件；
    根据所述业务配置事件向配置***发送业务配置信息，以使所述配置***根据所述业务配置信息对所述网络服务进行业务配置。
  2. 根据权利要求1所述的方法，其特征在于，所述业务配置事件用于指示在当前操作场景下所述网络服务执行的业务配置模板或工作流。
  3. 根据权利要求2所述的方法，其特征在于，所述业务配置事件包括业务配置事件名称、所述当前场景下的业务配置模板和执行所述业务配置模板时所需的业务参数。
  4. 根据权利要求3所述的方法，其特征在于，所述根据所述业务配置事件向配置***发送业务配置信息，以使所述配置***根据所述业务配置信息对所述网络服务进行业务配置，具体包括：
    向配置***发送业务配置事件，以使所述配置***根据所述业务配置事件对所述网络服务进行业务配置。
  5. 根据权利要求3所述的方法，其特征在于，所述根据所述业务配置事件向配置***发送业务配置信息，以使所述配置***根据所述业务配置信息对所述网络服务进行业务配置，具体包括：
    根据所述业务配置事件中的所述业务配置事件名称、所述当前操作场景下的业务配置模板和所述业务参数生成业务配置命令；
    将所述业务配置命令发送至所述配置***，以使所述配置***根据所述业务配置命令对所述网络服务进行业务配置。
  6. 根据权利要求1-5任一项所述的方法，其特征在于，所述方法还包括：
    接收所述配置***发送的业务配置结果。
  7. 根据权利要求1-6任一项所述的方法，其特征在于，所述网络服务为虚拟网络功能VNF，所述网络服务实例化请求为VNF实例化请求，所述业务配置事件用于指示在当前操作场景下所述VNF执行的业务配置模板或工作流。
  8. 根据权利要求1-6任一项所述的方法，其特征在于，所述网络服务包括虚拟网络功能VNF和物理网络功能PNF，所述业务配置事件用于指示在当前操作场景下所述VNF执行的第一业务配置模板或第一工作流，以及所述PNF执行的第二业务配置模板或第二工作流。
  9. 根据权利要求7所述的方法，其特征在于，所述业务配置事件携带在所述VNF实例化请求中的虚拟网络功能描述VNFD中。
  10. 根据权利要求8所述的方法，其特征在于，所述业务配置事件携带在所述网络服务实例化请求中的网络服务描述NSD中。
  11. 根据权利要求9或10所述的方法，其特征在于，所述业务配置事件还用于指示在当前操作场景下所述VNF的虚拟化部署单元VDU执行的业务配置模板或工作流。
  12. 根据权利要求1-11任一项所述的方法，其特征在于，所述当前操作场景包括初始化场景、弹性场景、升级场景、安全矩阵场景、服务终结场景中的任一个，
    所述业务参数包括本端的IP地址、本端的端口号Port、对端的IP地址、对端的Port、所述网络服务支持的业务类型中的至少一个参数。
  13. 一种网络服务的业务配置方法，其特征在于，包括：
    接收管理编排器MANO根据与运营商网络环境相关的网络服务的业务配置事件发送的业务配置信息；
    根据所述业务配置信息对所述网络服务进行业务配置。
  14. 根据权利要求13所述的方法，其特征在于，所述业务配置事件用于指示在当前操作场景下所述网络服务执行的业务配置模板或工作流。
  15. 根据权利要求14所述的方法，其特征在于，所述业务配置事件包括业务配置事件名称、所述当前场景下的业务配置模板和执行所述业务配置模板时所需的业务参数。
  16. 根据权利要求15所述的方法，其特征在于，所述根据所述业务配置信息对所述网络服务进行业务配置，具体包括：
    解析所述业务配置事件，获得所述业务配置事件名称、所述当前场景下的业务配置模板和所述业务参数；
    根据所述业务配置事件名称、所述当前场景下的业务配置模板和所述业务参数生成业务配置命令；
    根据所述业务配置命令对所述网络服务进行业务配置。
  17. 根据权利要求15所述的方法，其特征在于，所述接收管理编排器MANO根据与运营商网络环境相关的网络服务的业务配置事件发送的业务配置信息，具体包括：
    接收所述MANO发送的业务配置命令，所述业务配置命令为所述MANO根据所述业务配置事件名称、所述当前场景下的业务配置模板和所述业务参数生成的；
    则根据所述业务配置信息对所述网络服务进行业务配置，包括：
    根据所述业务配置命令对所述网络服务进行业务配置。
  18. 根据权利要求13-17任一项所述的方法，其特征在于，所述方法还包括：
    向所述MANO发送业务配置结果。
  19. 根据权利要求13-18任一项所述的方法，其特征在于，所述网络服务包括虚拟网络功能VNF，所述业务配置事件用于指示在当前操作场景下所述VNF执行的业务配置模板或工作流。
  20. 根据权利要求13-18任一项所述的方法，其特征在于，所述网络服务包括虚拟网络功能VNF和物理网络功能PNF，所述业务配置事件用于指示在当前操作场景下所述VNF执行的第一业务配置模板或第一工作流，以及，所述PNF执行的第二业务配置模板或第二工作流。
  21. 根据权利要求19所述的方法，其特征在于，所述业务配置事件携带在所述MANO接收的VNF实例化请求中的虚拟网络功能描述VNFD中。
  22. 根据权利要求20所述的方法，其特征在于，所述业务配置事件携带在所述 MANO接收的网络服务实例化请求中的网络服务描述NSD中。
  23. 根据权利要求21或22所述的方法，其特征在于，所述业务配置事件还用于指示在当前操作场景下所述VNF的虚拟化部署单元VDU执行的业务配置模板或工作流。
  24. 根据权利要求13-23任一项所述的方法，其特征在于，所述当前操作场景包括初始化场景、弹性场景、升级场景、安全矩阵场景、服务终结场景中的任一个，所述业务参数包括本端的IP地址、本端的端口号Port、对端的IP地址、对端的Port、所述网络服务支持的业务类型中的至少一个参数。
  25. 一种网络服务的业务配置装置，其特征在于，包括：
    接收模块，用于接收网络服务实例化请求，所述网络服务实例化请求包括：预设的与运营商网络环境相关的网络服务的业务配置事件；
    发送模块，用于根据所述业务配置事件向配置***发送业务配置信息，以使所述配置***根据所述业务配置信息对所述网络服务进行业务配置。
  26. 根据权利要求25所述的装置，其特征在于，所述业务配置事件用于指示在当前操作场景下所述网络服务执行的业务配置模板或工作流。
  27. 根据权利要求26所述的装置，其特征在于，所述业务配置事件包括业务配置事件名称、所述当前场景下的业务配置模板和执行所述业务配置模板时所需的业务参数。
  28. 根据权利要求27所述的装置，其特征在于，所述发送模块，具体用于向配置***发送业务配置事件，以使所述配置***根据所述业务配置事件对所述网络服务进行业务配置。
  29. 根据权利要求27所述的装置，其特征在于，所述发送模块，包括：
    生成单元，用于根据所述业务配置事件中的所述业务配置事件名称、所述当前操作场景下的业务配置模板和所述业务参数生成业务配置命令；
    发送单元，用于将所述业务配置命令发送至所述配置***，以使所述配置***根据所述业务配置命令对所述网络服务进行业务配置。
  30. 根据权利要求25-29任一项所述的装置，其特征在于，所述接收模块，还用于接收所述配置***发送的业务配置结果。
  31. 根据权利要求25-30任一项所述的装置，其特征在于，所述网络服务为虚拟网络功能VNF，所述网络服务实例化请求为VNF实例化请求，所述业务配置事件用于指示在当前操作场景下所述VNF执行的业务配置模板或工作流。
  32. 根据权利要求25-30任一项所述的装置，其特征在于，所述网络服务包括虚拟网络功能VNF和物理网络功能PNF，所述业务配置事件用于指示在当前操作场景下所述VNF执行的第一业务配置模板或第一工作流，以及所述PNF执行的第二业务配置模板或第二工作流。
  33. 根据权利要求31所述的装置，其特征在于，所述业务配置事件携带在所述VNF实例化请求中的虚拟网络功能描述VNFD中。
  34. 根据权利要求32所述的装置，其特征在于，所述业务配置事件携带在所述网络服务实例化请求中的网络服务描述NSD中。
  35. 根据权利要求33或34所述的装置，其特征在于，所述业务配置事件还用于指示在当前操作场景下所述VNF的虚拟化部署单元VDU执行的业务配置模板或工作流。
  36. 根据权利要求25-35任一项所述的装置，其特征在于，所述当前操作场景包括初始化场景、弹性场景、升级场景、安全矩阵场景、服务终结场景中的任一个，
    所述业务参数包括本端的IP地址、本端的端口号Port、对端的IP地址、对端的Port、所述网络服务支持的业务类型中的至少一个参数。
  37. 一种网络服务的业务配置装置，其特征在于，包括：
    接收模块，用于接收管理编排器MANO根据与运营商网络环境相关的网络服务的业务配置事件发送的业务配置信息；
    配置模块，用于根据所述业务配置信息对所述网络服务进行业务配置。
  38. 根据权利要求37所述的装置，其特征在于，所述业务配置事件用于指示在当前操作场景下所述网络服务执行的业务配置模板或工作流。
  39. 根据权利要求38所述的装置，其特征在于，所述业务配置事件包括业务配置事件名称、所述当前场景下的业务配置模板和执行所述业务配置模板时所需的业务参数。
  40. 根据权利要求39所述的装置，其特征在于，所述配置模块，具体包括：
    解析单元，用于解析所述业务配置事件，获得所述业务配置事件名称、所述当前场景下的业务配置模板和所述业务参数；
    生成单元，用于根据所述业务配置事件名称、所述当前场景下的业务配置模板和所述业务参数生成业务配置命令；
    配置单元，用于根据所述业务配置命令对所述网络服务进行业务配置。
  41. 根据权利要求39所述的装置，其特征在于，所述接收模块，具体用于接收所述MANO发送的业务配置命令，所述业务配置命令为所述MANO根据所述业务配置事件名称、所述当前场景下的业务配置模板和所述业务参数生成的；
    所述配置模块，具体用于根据所述业务配置命令对所述网络服务进行业务配置。
  42. 根据权利要求37-41任一项所述的装置，其特征在于，所述装置还包括：
    发送模块，用于向所述MANO发送业务配置结果。
  43. 根据权利要求37-42任一项所述的装置，其特征在于，所述网络服务包括虚拟网络功能VNF，所述业务配置事件用于指示在当前操作场景下所述VNF执行的业务配置模板或工作流。
  44. 根据权利要求37-42任一项所述的装置，其特征在于，所述网络服务包括虚拟网络功能VNF和物理网络功能PNF，所述业务配置事件用于指示在当前操作场景下所述VNF执行的第一业务配置模板或第一工作流，以及，所述PNF执行的第二业务配置模板或第二工作流。
  45. 根据权利要求43所述的装置，其特征在于，所述业务配置事件携带在所述MANO接收的VNF实例化请求中的虚拟网络功能描述VNFD中。
  46. 根据权利要求44所述的装置，其特征在于，所述业务配置事件携带在所述 MANO接收的网络服务实例化请求中的网络服务描述NSD中。
  47. 根据权利要求45或46所述的装置，其特征在于，所述业务配置事件还用于指示在当前操作场景下所述VNF的虚拟化部署单元VDU执行的业务配置模板或工作流。
  48. 根据权利要求37-47任一项所述的装置，其特征在于，所述当前操作场景包括初始化场景、弹性场景、升级场景、安全矩阵场景、服务终结场景中的任一个，所述业务参数包括本端的IP地址、本端的端口号Port、对端的IP地址、对端的Port、所述网络服务支持的业务类型中的至少一个参数。
PCT/CN2017/076928 2016-03-22 2017-03-16 网络服务的业务配置方法和装置 WO2017162089A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP17769366.0A EP3373518B1 (en) 2016-03-22 2017-03-16 Service configuration method and device for network service
US16/012,893 US10911331B2 (en) 2016-03-22 2018-06-20 Service configuration method and apparatus for network service

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201610165089.6A CN107222324B (zh) 2016-03-22 2016-03-22 网络服务的业务配置方法和装置
CN201610165089.6 2016-03-22

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/012,893 Continuation US10911331B2 (en) 2016-03-22 2018-06-20 Service configuration method and apparatus for network service

Publications (1)

Publication Number Publication Date
WO2017162089A1 true WO2017162089A1 (zh) 2017-09-28

Family

ID=59899221

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/076928 WO2017162089A1 (zh) 2016-03-22 2017-03-16 网络服务的业务配置方法和装置

Country Status (4)

Country Link
US (1) US10911331B2 (zh)
EP (1) EP3373518B1 (zh)
CN (1) CN107222324B (zh)
WO (1) WO2017162089A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3787232A4 (en) * 2018-05-11 2021-06-23 Huawei Technologies Co., Ltd. METHOD, DEVICE AND SYSTEM FOR NETWORK CONFIGURATION

Families Citing this family (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10469317B1 (en) * 2017-03-29 2019-11-05 Juniper Networks, Inc. Virtualized network function descriptors for virtualized network function configuration
US11665012B2 (en) * 2017-08-11 2023-05-30 Harmonic, Inc. Virtual access hub
CN109818768B (zh) * 2017-11-21 2022-02-25 ***通信有限公司研究院 一种物理设施管理***、pnf网络管理***及方法
CN109842892B (zh) * 2017-11-24 2020-11-10 ***通信有限公司研究院 一种nsi的pnf更新方法、设备和计算机可读存储介质
CN110740053B (zh) * 2018-07-20 2022-07-01 ***通信集团浙江有限公司 业务编排方法及装置
CN109471676B (zh) * 2018-10-30 2022-03-01 中国建设银行股份有限公司 参数配置处理方法和装置
CN111399866B (zh) * 2019-01-02 2023-05-05 ***通信有限公司研究院 Vnf包的更新方法及装置
CN112953751B (zh) * 2019-12-11 2023-11-28 ***通信有限公司研究院 一种模板处理方法、装置、设备及计算机可读存储介质
CN111176792B (zh) * 2019-12-31 2023-11-17 华为技术有限公司 一种资源调度方法、装置及相关设备
US11489712B1 (en) * 2020-04-11 2022-11-01 Juniper Networks, Inc. Systems and methods for efficient configuration file management and distribution by network management systems
CN115967617A (zh) * 2021-10-11 2023-04-14 中兴通讯股份有限公司 网络服务部署方法、装置及计算机可读存储介质

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104639361A (zh) * 2013-11-15 2015-05-20 中兴通讯股份有限公司 网络服务模板的管理方法和装置
CN104954220A (zh) * 2014-03-31 2015-09-30 华为技术有限公司 一种虚拟网络业务部署方法和设备
WO2015157896A1 (zh) * 2014-04-14 2015-10-22 华为技术有限公司 一种云计算架构下的容灾方案配置方法及装置
CN105282765A (zh) * 2014-06-30 2016-01-27 中兴通讯股份有限公司 一种管理配置信息的方法、设备及网元管理***
WO2016029821A1 (zh) * 2014-08-30 2016-03-03 华为技术有限公司 一种虚拟网络实例的创建方法以及设备

Family Cites Families (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8837493B2 (en) * 2010-07-06 2014-09-16 Nicira, Inc. Distributed network control apparatus and method
CN102739426B (zh) * 2011-04-13 2017-05-24 中兴通讯股份有限公司 一种dpoe***及基于该***业务自动配置方法和网络
WO2015172362A1 (zh) * 2014-05-15 2015-11-19 华为技术有限公司 一种网络功能虚拟化网络***、数据处理方法及装置
JP6478134B2 (ja) * 2014-09-25 2019-03-06 インテル アイピー コーポレーション ネットワーク機能の可視化
JP2016103771A (ja) * 2014-11-28 2016-06-02 富士通株式会社 通信経路制御方法、および情報処理装置
JP6686910B2 (ja) * 2015-01-23 2020-04-22 日本電気株式会社 ネットワーク機能仮想化管理およびオーケストレーション方法と装置とプログラム
CN104734931B (zh) 2015-03-31 2018-06-05 华为技术有限公司 一种虚拟网络功能间链路建立方法及装置
US9690613B2 (en) * 2015-04-12 2017-06-27 At&T Intellectual Property I, L.P. Using diversity to provide redundancy of virtual machines
WO2017014803A1 (en) * 2015-07-23 2017-01-26 Intel Corporation Network resource model to support network function virtualization lifecycle management

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104639361A (zh) * 2013-11-15 2015-05-20 中兴通讯股份有限公司 网络服务模板的管理方法和装置
CN104954220A (zh) * 2014-03-31 2015-09-30 华为技术有限公司 一种虚拟网络业务部署方法和设备
WO2015157896A1 (zh) * 2014-04-14 2015-10-22 华为技术有限公司 一种云计算架构下的容灾方案配置方法及装置
CN105282765A (zh) * 2014-06-30 2016-01-27 中兴通讯股份有限公司 一种管理配置信息的方法、设备及网元管理***
WO2016029821A1 (zh) * 2014-08-30 2016-03-03 华为技术有限公司 一种虚拟网络实例的创建方法以及设备

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3373518A4 *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3787232A4 (en) * 2018-05-11 2021-06-23 Huawei Technologies Co., Ltd. METHOD, DEVICE AND SYSTEM FOR NETWORK CONFIGURATION
US11394607B2 (en) 2018-05-11 2022-07-19 Huawei Technologies Co., Ltd. Method and system for network configuration

Also Published As

Publication number Publication date
US10911331B2 (en) 2021-02-02
CN107222324B (zh) 2021-05-14
CN107222324A (zh) 2017-09-29
EP3373518A1 (en) 2018-09-12
EP3373518B1 (en) 2023-05-03
US20180316578A1 (en) 2018-11-01
EP3373518A4 (en) 2018-12-12

Similar Documents

Publication Publication Date Title
WO2017162089A1 (zh) 网络服务的业务配置方法和装置
JP6834033B2 (ja) ネットワークスライス管理方法、ユニット、及びシステム
US11936548B2 (en) Active assurance for virtualized services
RU2643451C2 (ru) Система и способ виртуализации функции мобильной сети
WO2017036288A1 (zh) 一种网元升级方法及设备
WO2016155394A1 (zh) 一种虚拟网络功能间链路建立方法及装置
CN110476453A (zh) 用于向客户提供网络切片的服务发放
EP3676699B1 (en) Apparatus and method for configuring and monitoring virtual applications
WO2016119631A1 (zh) 一种接入云服务的方法及接入设备
WO2019127418A1 (zh) 网络服务管理方法、相关装置及***
US20210289435A1 (en) Virtualization management method and apparatus
WO2021254001A1 (zh) 会话建立方法、装置、***及计算机存储介质
US20220350637A1 (en) Virtual machine deployment method and related apparatus
WO2020220937A1 (zh) 一种安全策略管理方法及装置
WO2023197815A1 (zh) 一种消息的接收、发送方法及装置
US20230105269A1 (en) Virtualized network service deployment method and apparatus
WO2022183796A1 (zh) 一种创建网络服务ns的方法及相关装置
WO2021129868A1 (zh) 网络服务实例化的方法及网络功能虚拟化编排器
WO2022193897A1 (zh) 一种业务的部署方法、装置及***
JP7486597B2 (ja) ダイアルアップ・パケット処理方法、ネットワーク要素、システム、ネットワーク装置
Santos Deploying and managing network services over programmable virtual networks
CN116530130A (zh) 用于虚拟化服务的主动保证

Legal Events

Date Code Title Description
WWE Wipo information: entry into national phase

Ref document number: 2017769366

Country of ref document: EP

NENP Non-entry into the national phase

Ref country code: DE