WO2016206306A1 - 虚拟化核心网关开局方法、装置和系统 - Google Patents

虚拟化核心网关开局方法、装置和系统 Download PDF

Info

Publication number
WO2016206306A1
WO2016206306A1 PCT/CN2015/096002 CN2015096002W WO2016206306A1 WO 2016206306 A1 WO2016206306 A1 WO 2016206306A1 CN 2015096002 W CN2015096002 W CN 2015096002W WO 2016206306 A1 WO2016206306 A1 WO 2016206306A1
Authority
WO
WIPO (PCT)
Prior art keywords
core gateway
virtual machine
network
orchestrator
deployment
Prior art date
Application number
PCT/CN2015/096002
Other languages
English (en)
French (fr)
Inventor
齐磊
顾希
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2016206306A1 publication Critical patent/WO2016206306A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/02—Arrangements for optimising operational condition
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/16—Gateway arrangements

Definitions

  • This application relates to, but is not limited to, the field of communication technology.
  • SAE is short for System Architecture Evolution, meaning system architecture evolution.
  • 4G the 4th generation mobile communication technology
  • LTE Long Term Evolution
  • 3GPP 3rd Generation Partnership Project
  • SAE is the study of the long-term evolution of the core network, which defines a grouping of all-IP (Internet Protocol) protocols.
  • Core network EPC Evolved Packet Core, 4G core network
  • the system is characterized by only packet domain without circuit domain, based on all-IP structure, control and bearer separation and flat network structure, which mainly includes MME (Mobility Management Entity) Network elements such as the mobile management entity, the SGW (Serving GateWay), the PGW (PDN GateWay), and the PCRF (Policy and Charging Rules Function).
  • MME Mobility Management Entity
  • SGW Serving GateWay
  • PGW Packet Core
  • PCRF Policy and Charging Rules Function
  • VNF Virtualized Network Function
  • This paper provides a virtualized core gateway deployment method and device, which solves the problem of low efficiency of core gateway deployment.
  • a virtualization core gateway deployment method includes:
  • the network virtualization orchestrator collects parameters required for the core gateway to start;
  • the network virtualization orchestrator receives the virtual machine specification parameter, and creates a virtual machine of the core gateway according to the virtual machine specification parameter.
  • the method further includes:
  • the Network Virtualization Orchestrator creates a core gateway version package that includes the GuestOS image, software version, plug-ins, and customization information.
  • the network virtualization orchestrator creates a core gateway version package, where the core gateway version package includes a guest OS image, a software version, a plug-in, and customization information, and the network virtualization orchestrator collects parameters required for the core gateway deployment. Between the steps, it also includes:
  • the network virtual orchestrator uploads the GuestOS image to the cloud platform, so that the network virtualization orchestrator loads the guest OS image when creating a virtual machine of the core gateway.
  • the step of the network virtualization orchestrator collecting parameters required for the core gateway deployment includes:
  • the network virtualization orchestrator provides an operation interface for the user to operate
  • the parameters required for the core gateway deployment are collected according to the user input information on the operation interface.
  • a virtualized core gateway deployment device comprising:
  • the acquisition module is configured to: collect parameters required for the core gateway to start;
  • the sending module is set to: pass the parameter to the network function virtualization manager for the supply
  • the network function virtualization manager invokes the plug-in to obtain all the virtual machine specification parameters required for the core gateway to start, and sends the virtual machine specification parameters to the network virtualization orchestrator;
  • the first creating module is configured to: receive the virtual machine specification parameter, and create a virtual machine of the core gateway according to the virtual machine specification parameter.
  • the virtualized core gateway deployment device further includes a second creation module, configured to: create a core gateway version package, where the core gateway version package includes a GuestOS image, a software version, a plug-in, and customization information.
  • a second creation module configured to: create a core gateway version package, where the core gateway version package includes a GuestOS image, a software version, a plug-in, and customization information.
  • the virtualized core gateway deployment device further includes: an uploading module, configured to: upload the guestOS image to the cloud platform, where the network virtualization orchestrator loads the virtual machine of the core gateway The GuestOS image.
  • an uploading module configured to: upload the guestOS image to the cloud platform, where the network virtualization orchestrator loads the virtual machine of the core gateway The GuestOS image.
  • the collecting module includes:
  • Providing a unit configured to: provide an operation interface for the user to operate;
  • the collecting unit is configured to: collect the parameters required for the core gateway to start according to the user input information on the operation interface.
  • a virtualized core gateway deployment system where the virtualized core gateway deployment system includes a network virtualization orchestrator and a network function virtualization manager;
  • the network virtualization orchestration device comprising the device of any of the above;
  • the network virtualization manager is configured to: receive parameters required for the core gateway to start, invoke the plug-in according to the parameter to obtain all virtual machine specification parameters required for the core gateway deployment, and send the virtual machine specification parameters to the network virtualization. Orchestrator.
  • the network virtualization manager is configured to: invoke the first plug-in to obtain customized information according to parameters required for the core gateway deployment, and invoke the first plug-in to calculate a virtual parameter according to the required parameters of the core gateway deployment.
  • a computer readable storage medium storing computer executable instructions for performing the method of any of the above.
  • the network virtualization orchestrator collects parameters required for the core gateway to start, and the network virtualization manager receives the parameters required for the core gateway to start, and invokes the plug-in according to the parameter to obtain all virtual machine specification parameters required for the core gateway to start. And sending the virtual machine specification parameter to the network virtualization orchestrator; the network virtualization orchestrator receives the virtual machine specification parameter, and creates a virtual machine of the core gateway according to the virtual machine specification parameter.
  • the configuration information required for the core gateway deployment is synchronized, which improves the deployment efficiency of the core gateway and reduces the operation and maintenance costs and the capability requirements of the deployment personnel.
  • FIG. 1 is a schematic flowchart of a first embodiment of a method for starting a virtualized core gateway according to the present invention
  • FIG. 2 is a schematic flowchart of a parameter required for a network virtualization orchestrator to collect a core gateway for deployment in an embodiment of the present invention
  • FIG. 3 is a schematic flowchart of a second embodiment of a method for starting a virtualized core gateway according to the present invention
  • FIG. 4 is a schematic diagram of functional modules of a first embodiment of a virtualized core gateway deployment apparatus according to the present invention.
  • FIG. 5 is a detailed functional block diagram of an embodiment of an acquisition module according to an embodiment of the present invention.
  • FIG. 6 is a schematic diagram of functional modules of a second embodiment of a virtualized core gateway deployment apparatus according to the present invention.
  • FIG. 7 is a schematic diagram of functional modules of an embodiment of a virtualized core gateway deployment system according to the present invention.
  • the network virtualization orchestrator collects parameters required for the core gateway to start; and passes the parameters to the network function virtualization manager, so that the network function virtualization manager calls the plug-in to obtain the core gateway deployment requirement. All virtual machine specification parameters, and send the virtual machine specification parameters to the network virtualization orchestrator; the network virtualization orchestrator receives the virtual machine specification parameters, Create a virtual machine of the core gateway according to the virtual machine specification parameter. The network virtualization orchestrator collects the parameters required for the core gateway deployment and sends the parameters to the network function virtualization manager. The network function virtualization manager obtains all the virtual machine specification parameters required for the core gateway deployment, and the virtual machine specification parameters are obtained.
  • the network virtualization orchestrator creates a virtual machine according to the virtual machine specification parameters.
  • the configuration information required for the core gateway deployment is synchronized, which improves the deployment efficiency of the core gateway and reduces the operation and maintenance costs and the capability requirements of the deployment personnel.
  • the embodiment of the invention provides a method for starting a virtualized core gateway.
  • FIG. 1 is a schematic flowchart diagram of a first embodiment of a method for starting a virtualized core gateway according to the present invention.
  • the virtualization core gateway deployment method includes:
  • Step S10 the network virtualization orchestrator collects parameters required for the core gateway to start
  • the NFV-Orchestrator collects data parameters required for the deployment of the core gateway SAE-GW, including but not limited to APN (Access Point Name, access point), service IP ( Service IP), interface IP (interface IP), etc.
  • APN Access Point Name, access point
  • service IP Service IP
  • interface IP interface IP
  • the NFV-Orchestrator provides a download path to the VNFM (Network Functions Virtualisation Manager) for the VNFM to use the HTTP (Hyper Text Transfer Protocol) from the VNFM.
  • the NFV-Orchestrator downloads the SAE-GW software version, the SAE-GW plug-in, and the SAE-GW customization information.
  • the SAE-GW plug-in is called to parse the SAE-GW customization information to obtain the specification parameters of the SAE-GW virtual unit.
  • Step S20 the parameter is passed to a network function virtualization manager for the network function
  • the virtualization manager invokes the plug-in to obtain all virtual machine specification parameters required for the core gateway to start, and sends the virtual machine specification parameters to the network virtualization orchestrator;
  • the network virtualization orchestrator saves the collected data to a preset file, including but not limited to an excel table. For example, save the collected APN, service IP and interface IP into an excel table.
  • the network virtualization orchestrator passes the preset file to the VNFM in a preset manner.
  • the preset mode may be SFTP (Secure File Transfer Protocol), which provides a secure encryption method for transmitting files.
  • the VNFM When the VNFM receives the preset file, it will invoke a conversion plugin registered by the SAE-GW, that is, the first plug-in, convert the excel form data into a SAE-GW identifiable configuration file, and package the configuration file. Go to the SAE-GW registered custom package.
  • the conversion plug-in registered by the SAE-GW also calculates the virtual machine-related specification parameters that need to be created by the local office according to the SAE-GW traffic model in the data of the excel table, and saves it to an XML (Extensible Markup Language, scalable). Markup language) in the file.
  • the specification parameters include the number of virtual machines, the type of the virtual machine, the switching mode of the primary virtual machine and the standby virtual machine, and the like.
  • the types of the virtual machines include a Microsoft virtual machine, an Intel virtual machine, a Linux virtual machine, and the like.
  • the scene of the traffic model has a dense urban area, a general urban area, a suburb, and a rural area.
  • the virtual machine related specification parameters are created according to the traffic volume, service rate, and data service demand of different regions.
  • VNFM continues to call the second plug-in to parse the SAE-GW customization information, and combines the XML file generated by the first plug-in to obtain all the specifications of the virtual unit required for the SAE-GW start, and the output is identifiable by NFV-Orchestrator/VNFM. XML file.
  • the VNFM sends the identifiable XML file to NFV-Orchestrator.
  • Step S30 The network virtualization orchestrator receives the virtual machine specification parameter, and creates a virtual machine of the core gateway according to the virtual machine specification parameter.
  • the virtual machine of the SAE-GW is created according to the virtual machine specification parameter. That is, the virtual machine of the SAE-GW is created according to the number of virtual machines required, the type of the virtual machine, the switching mode of the primary virtual machine and the standby virtual machine, and the like.
  • the NFV-Orchestrator interacts with the VNFM, and the SAE-GW downloads the software version and configuration file of the SAE-GW from the hard disk of the VNFM.
  • the SAE-GW software runs successfully, it will automatically Load the configuration file of the SAE-GW and enter all the configuration information of the SAE-GW in this deployment.
  • the network virtualization orchestrator collects parameters required for the core gateway to start, and the network virtualization manager receives the parameters required for the core gateway to start, and invokes the plug-in according to the parameter to obtain all virtual machine specification parameters required for the core gateway to start, and And sending the virtual machine specification parameter to the network virtualization orchestrator; the network virtualization orchestrator receives the virtual machine specification parameter, and creates a virtual machine of the core gateway according to the virtual machine specification parameter. At the same time that the virtual machine of the core gateway is created and powered on, the configuration information required for the core gateway deployment is synchronized, which improves the efficiency of the gateway.
  • FIG. 2 is a schematic flowchart of a parameter required for a network virtualization orchestrator to collect a core gateway in a deployment according to an embodiment of the present invention.
  • the step S10 includes:
  • Step S11 the network virtualization orchestrator provides an operation interface for the user to operate
  • Step S12 Collect, on the operation interface, parameters required for the core gateway to start according to the user input information.
  • the NFV-Orchestrator provides a UI operation interface for the user to collect the data parameters required for the core gateway SAE-GW to start.
  • the data parameters include but are not limited to APN (Access Point Name) and service IP (Service IP). ), interface IP (interface IP) and so on.
  • the UI interface adopts a graphical interface, and the peripheral network element that needs to be connected to the SAE-GW is customized by dragging and dropping the icon, and the user is configured to complete the SAE-GW network element parameter, the surrounding network element parameter, and the route through the pop-up prompting and guiding manner. Docking and other settings.
  • the peripheral network element includes, but is not limited to, an eNodeB (Evolved Node B, ie, an evolved Node B, referred to as an eNB, a name of a base station in LTE, compared to a Node B in 3G (3rd Generation, 3rd Generation Mobile Communication Technology).
  • eNodeB Evolved Node B, ie, an evolved Node B, referred to as an eNB, a name of a base station in LTE, compared to a Node B in 3G (3rd Generation, 3rd Generation Mobile Communication Technology).
  • RNC Radio Network Controller
  • OCS Online Charging System
  • AAA Authentication, Authorization, Accounting, authentication and authorization billing.
  • the security service refers to authentication, which is to verify the identity of the user and determine whether it is a legitimate user.
  • Authorization is to authorize users who can authenticate to use those services; accounting, Is to record the resources of users using network services, these Information will be used as a basis for billing) and so on.
  • the peripheral network element parameters include, but are not limited to, server name, server IP, Username, and the like.
  • the UI virtual interface is provided by the network virtual orchestrator to collect the core gateway deployment parameters, which facilitates the operation of the deployment personnel.
  • FIG. 3 is a schematic flowchart of a second embodiment of a method for starting a virtualized core gateway according to the present invention.
  • a second embodiment of a method for starting a virtualized core gateway according to the present invention is provided based on the first embodiment.
  • the method before step S10, the method further includes:
  • Step S40 The network virtualization orchestrator creates a core gateway version package, where the core gateway version package includes a GuestOS (virtual machine operating system) image, a software version, a plug-in, and customization information.
  • GuestOS virtual machine operating system
  • step S50 the network virtual orchestrator uploads the guest OS image to the cloud platform for loading the guest OS image when creating the virtual machine of the core gateway.
  • the NFV-Orchestrator Before collecting the parameters required for the SAE-GW deployment, the NFV-Orchestrator will create a SAE-GW version package through its users, that is, its users apply to register a SAE-GW version package.
  • the SAE-GW version package generally includes four parts: a guest OS image, a SAE-GW software version, a SAE-GW plug-in, and a SAE-GW customization information.
  • the NFV-Orchestrator uploads the image file to the cloud platform during the registration process, so that it automatically loads the GuestOS image file when creating the GW virtual machine.
  • the core gateway version package is created, and the guest OS image is loaded when the virtual machine of the core gateway is created, so that all the configurations required for the gateway service deployment are completed simultaneously, and the virtual machine of the core gateway is automatically created and powered on. It improves the opening efficiency of the gateway and reduces the operation and maintenance costs and the ability requirements of the starters.
  • the embodiment of the invention further provides a virtualized core gateway deployment device.
  • FIG. 4 is a schematic diagram of functional modules of a first embodiment of a virtualized core gateway deployment apparatus according to the present invention.
  • the virtualized core gateway deployment device includes:
  • the collecting module 10 is configured to: collect parameters required for the core gateway to start;
  • the NFV-Orchestrator collects data parameters required for the SAE-GW core gateway deployment, including but not limited to APN (Access Point Name) and service IP (APN). Service IP), interface IP (interface IP), etc.
  • the NFV-Orchestrator provides a download path to the VNFM (Network Functions Virtualisation Manager) for the VNFM to use the HTTP (Hyper Text Transfer Protocol) from the VNFM.
  • the NFV-Orchestrator downloads the SAE-GW software version, the SAE-GW plug-in, and the SAE-GW customization information.
  • the SAE-GW plug-in is called to parse the SAE-GW customization information to obtain the specification parameters of the SAE-GW virtual unit.
  • the sending module 20 is configured to: pass the parameter to the network function virtualization manager, where the network function virtualization manager invokes the plug-in to obtain all virtual machine specification parameters required for the core gateway deployment, and the virtual function specification
  • the machine specification parameters are sent to the network virtualization orchestrator;
  • the network virtualization orchestrator saves the collected data to a preset file, including but not limited to an excel table. For example, save the collected APN, service IP and interface IP into an excel table.
  • the network virtualization orchestrator passes the preset file to the VNFM in a preset manner.
  • the preset mode may be SFTP (Secure File Transfer Protocol), which provides a secure encryption method for transmitting files.
  • the VNFM When the VNFM receives the preset file, it will invoke a conversion plugin registered by the SAE-GW, that is, the first plug-in, convert the excel form data into a SAE-GW identifiable configuration file, and package the configuration file. Go to the SAE-GW registered custom package.
  • the conversion plug-in registered by the SAE-GW also calculates the virtual machine-related specification parameters that need to be created by the local office according to the SAE-GW traffic model in the data of the excel table, and saves it to an XML (Extensible Markup Language, scalable). Markup language) in the file.
  • the specification parameters include the number of virtual machines, the type of the virtual machine, the switching mode of the primary virtual machine and the standby virtual machine, and the like.
  • the types of the virtual machines include a Microsoft virtual machine, an Intel virtual machine, a Linux virtual machine, and the like.
  • the scene of the traffic model has a dense urban area, a general urban area, a suburb, and a rural area.
  • the virtual machine related specification parameters are created according to the traffic volume, service rate, and data service demand of different regions.
  • VNFM continues to call the second plugin
  • the SAE-GW customization information is analyzed, and the XML files generated by the first plug-in are combined to obtain all the specification parameters of the virtual unit required for the SAE-GW start, and the output is an XML file recognizable by NFV-Orchestrator/VNFM.
  • the VNFM sends the identifiable XML file to NFV-Orchestrator.
  • the first creating module 30 is configured to: receive the virtual machine specification parameter, and create a virtual machine of the core gateway according to the virtual machine specification parameter.
  • the NFV-Orchestrator When the NFV-Orchestrator receives the identifiable XML file, that is, when the virtual machine specification parameter is received, in the cloud platform, the virtual machine of the SAE-GW is created according to the virtual machine specification parameter, that is, the virtual machine according to the requirement
  • the SAE-GW virtual machine is created by the number, the type of virtual machine, the switching mode of the primary virtual machine and the standby virtual machine.
  • the NFV-Orchestrator interacts with the VNFM, and the SAE-GW downloads the software version and configuration file of the SAE-GW from the hard disk of the VNFM.
  • the configuration file of the SAE-GW is automatically loaded, and all configuration information of the SAE-GW is dynamically entered.
  • the core gateway deployment parameter is collected by the network virtualization orchestrator, the network function virtualization manager obtains the virtual machine specification parameter, and sends the virtual machine specification parameter to the network virtualization orchestrator, and the network virtualization orchestrator Create a virtual machine based on the virtual machine specification parameters.
  • the configuration information required for the core gateway deployment is synchronized, which improves the efficiency of the gateway.
  • FIG. 5 is a refinement function of an embodiment of an acquisition module according to an embodiment of the present invention.
  • the collection module 10 includes:
  • the providing unit 11 is configured to: provide an operation interface for the user to operate;
  • the collecting unit 12 is configured to: collect, on the operation interface, parameters required for the core gateway to start according to the user input information.
  • the NFV-Orchestrator provides a UI operation interface for the user to collect the data parameters required for the core gateway SAE-GW to start.
  • the data parameters include but are not limited to APN (Access Point Name) and service IP (Service IP). ), interface IP (interface IP) and so on.
  • the UI interface adopts a graphical interface, and the SAE-GW needs to be docked by dragging and dropping icons.
  • the surrounding network element assists the user in completing the network element parameters of the SAE-GW, the surrounding network element parameters, routing and other settings through the pop-up prompting and guiding manner.
  • the peripheral network element includes, but is not limited to, an eNodeB (Evolved Node B, ie, an evolved Node B, referred to as an eNB, a name of a base station in LTE, compared to a Node B in 3G (3rd Generation, 3rd Generation Mobile Communication Technology).
  • eNodeB Evolved Node B, ie, an evolved Node B, referred to as an eNB, a name of a base station in LTE, compared to a Node B in 3G (3rd Generation, 3rd Generation Mobile Communication Technology).
  • RNC Radio Network Controller
  • OCS Online Charging System
  • AAA Authentication, Authorization, Accounting, authentication and authorization billing.
  • the security service refers to authentication, which is to verify the identity of the user and determine whether it is a legitimate user.
  • Authorization is to authorize users who can authenticate to use those services; accounting, It is to record the resources of users using network services, this information will be used as the basis for billing) and so on.
  • the peripheral network element parameters include, but are not limited to, server name, server IP, Username, and the like.
  • the UI virtual interface is provided by the network virtual orchestrator to collect the core gateway deployment parameters, which facilitates the operation of the deployment personnel.
  • FIG. 6 is a schematic diagram of functional modules of a second embodiment of a virtualized core gateway deployment apparatus according to the present invention.
  • a second embodiment of the virtualized core gateway deployment apparatus of the present invention is proposed based on the first embodiment.
  • the virtualized core gateway deployment device further includes:
  • the second creating module 40 is configured to: create a core gateway version package, where the core gateway version package includes a GuestOS image, a software version, a plug-in, and customization information.
  • the uploading module 50 is configured to upload the GuestOS image to the cloud platform for loading the guest OS image when creating the virtual machine of the core gateway.
  • the NFV-Orchestrator Before collecting the parameters required for the SAE-GW deployment, the NFV-Orchestrator will create a SAE-GW version package through its users, that is, its users apply to register a SAE-GW version package.
  • the SAE-GW version package generally includes four parts: a guest OS image, a SAE-GW software version, a SAE-GW plug-in, and a SAE-GW customization information.
  • the NFV-Orchestrator uploads the image file to the cloud platform during the registration process for the user to automatically load the GuestOS when creating the GW virtual machine. Image file.
  • the core gateway version package is created, and the guest OS image is loaded when the virtual machine of the core gateway is created, so that all the configurations required for the gateway service deployment are completed simultaneously, and the virtual machine of the core gateway is automatically created and powered on. It improves the opening efficiency of the gateway and reduces the operation and maintenance costs and the ability requirements of the starters.
  • the embodiment of the invention further provides a virtualized core gateway deployment system.
  • FIG. 7 is a schematic diagram of functional modules of an embodiment of a virtualized core gateway deployment system according to the present invention.
  • the virtualized core gateway deployment system includes a network virtualization orchestrator 110 and a network function virtualization manager 220.
  • the NFV-Orchestrator Before collecting the parameters required for the SAE-GW deployment, the NFV-Orchestrator will create a SAE-GW version package through its users, that is, its users apply to register a SAE-GW version package.
  • the SAE-GW version package generally includes four parts: a guest OS image, a SAE-GW software version, a SAE-GW plug-in, and a SAE-GW customization information.
  • the NFV-Orchestrator uploads the image file to the cloud platform during the registration process, so that it automatically loads the GuestOS image file when creating the GW virtual machine.
  • the NFV-Orchestrator provides a download path to the VNFM for the VNFM to download the SAE-GW software version, SAE-GW, from the NFV-Orchestrator via HTTP (Hyper Text Transfer Protocol). Plugin, SAE-GW custom information.
  • the NFV-Orchestrator (Network Functions Virtualisation Orchestrator 110) provides a UI (User Interface) operation interface for the user to collect data parameters required for the core gateway SAE-GW to start, the data parameters. Including but not limited to APN (Access Point Name), service IP (service IP), interface IP (interface IP) and so on.
  • APN Access Point Name
  • service IP service IP
  • interface IP interface IP
  • the UI interface adopts a graphical interface, and the peripheral network element that needs to be connected to the SAE-GW is customized by dragging and dropping the icon, and the user is configured to complete the SAE-GW network element parameter, the surrounding network element parameter, and the route through the pop-up prompting and guiding manner. Docking and other settings.
  • the peripheral network element includes, but is not limited to, an eNodeB (Evolved Node B, ie, an evolved Node B, referred to as an eNB, and an LTE base station).
  • eNodeB evolved Node B
  • eNB evolved Node B
  • LTE base station LTE base station
  • the name of the station compared to the Node B in 3G (3rd Generation, 3rd generation mobile communication technology), integrates some functions of the RNC (Radio Network Controller), reducing the level of communication protocol, OCS (Online Charging System, an online charging system, which is a real-time system for interactive charging based on service usage and system. Online charging collects billing information during the session, realizing settlement in real time. If the account has no money, The service is stopped.), AAA (Authentication, Authorization, Accounting, Authentication and Authorization Accounting.
  • AAA Authentication, Authorization, Accounting, Authentication and Authorization Accounting.
  • the security service provided by the authentication service is authentication, which is to verify the identity of the user and determine whether it is a legitimate user; (Authorization) is to authenticate users who are authorized to use those services; Accounting, which records the resources of users using network services, which will be used as the basis for billing) and so on.
  • the peripheral network element parameters include, but are not limited to, server name, server IP, Username, and the like.
  • the network virtualization orchestrator 110 saves the collected data to a preset file, including but not limited to an excel table. For example, save the collected APN, service IP and interface IP into an excel table.
  • the network virtualization orchestrator 110 passes the preset file to the VNFM (Network Functions Virtualisation Manager) by a preset manner.
  • the preset mode may be SFTP (Secure File Transfer Protocol), which provides a secure encryption method for transmitting files.
  • the virtual machine of the SAE-GW is created according to the virtual machine specification parameter, that is, the virtual machine according to the requirement
  • the SAE-GW virtual machine is created by the number, the type of virtual machine, the switching mode of the primary virtual machine and the standby virtual machine.
  • the network function virtualization manager 220 is configured to: invoke the plug-in to generate the extensible markup language file and parse the customized information of the core gateway, obtain the virtual machine specification parameter, and send the virtual machine specification parameter to the network virtualization orchestrator 110. .
  • the network virtualization manager 220 is configured to: invoke the first plug-in to obtain customized information according to parameters required for the core gateway deployment, and invoke the first plug-in to calculate a virtual machine-related specification according to parameters required for the core gateway deployment. And saving the specification parameter to the extensible markup language file; and invoking the second plug-in to parse the customized information, and combining the extensible markup language file to obtain all virtual machine specification parameters required for the core gateway to start.
  • the VNFM downloads the SAE-GW software version, the SAE-GW plug-in, and the SAE-GW customization information from the NFV-Orchestrator via HTTP.
  • the SAE-GW plug-in When the VNFM is successfully downloaded to the SAE-GW software version, the SAE-GW plug-in, SAE-GW
  • the SAE-GW plug-in When the information is customized, the SAE-GW plug-in is called to parse the SAE-GW customization information to obtain the specification parameters of the SAE-GW virtual unit.
  • the VNFM When the VNFM receives the preset file passed by the NFV-Orchestrator, it will call a conversion plugin registered by the SAE-GW, that is, the first plug-in, convert the excel table data into a SAE-GW identifiable configuration file, and The configuration file is packaged into a customized information package registered by the SAE-GW.
  • the conversion plug-in registered by the SAE-GW also calculates the virtual machine-related specification parameters that need to be created by the local office according to the SAE-GW traffic model in the data of the excel table, and saves it to an XML (Extensible Markup Language, scalable). Markup language) in the file.
  • XML Extensible Markup Language, scalable). Markup language
  • the specification parameters include the number of virtual machines, the type of the virtual machine, the switching mode of the primary virtual machine and the standby virtual machine, and the like.
  • the types of the virtual machines include a Microsoft virtual machine, an Intel virtual machine, a Linux virtual machine, and the like.
  • the scene of the traffic model has a dense urban area, a general urban area, a suburb, and a rural area.
  • the virtual machine related specification parameters are created according to the traffic volume, service rate, and data service demand of different regions.
  • VNFM continues to call the second plug-in to parse the SAE-GW customization information, and combines the XML file generated by the second plug-in to obtain all the specifications of the virtual unit required for the SAE-GW start, and the output is identifiable by NFV-Orchestrator/VNFM. XML file.
  • the VNFM sends the identifiable XML file to NFV-Orchestrator.
  • the NFV-Orchestrator interacts with the VNFM to download the software version and configuration file of the SAE-GW from the hard disk of the VNFM.
  • the configuration file of the SAE-GW is automatically loaded, and all configuration information of the SAE-GW is dynamically entered.
  • all or part of the steps of the above embodiments may also be implemented by using an integrated circuit. These steps may be separately fabricated into individual integrated circuit modules, or multiple modules or steps may be fabricated into a single integrated circuit module. achieve.
  • the devices/function modules/functional units in the above embodiments may be implemented by a general-purpose computing device, which may be centralized on a single computing device or distributed over a network of multiple computing devices.
  • the device/function module/functional unit in the above embodiment When the device/function module/functional unit in the above embodiment is implemented in the form of a software function module and sold or used as a stand-alone product, it can be stored in a computer readable storage medium.
  • the above mentioned computer readable storage medium may be a read only memory, a magnetic disk or an optical disk or the like.
  • the configuration information required for the core gateway deployment is completed simultaneously, and the deployment efficiency of the core gateway is improved, and the operation and maintenance cost and the capability requirement of the deployment personnel are reduced.

Landscapes

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

Abstract

本文公布一种虚拟化核心网关开局方法、装置和系统，所述方法包括：网络虚拟化编排器采集核心网关开局所需参数；将所述参数传递给网络功能虚拟化管理器，以供所述网络功能虚拟化管理器调用插件得到核心网关开局所需的所有虚拟机规格参数，并将所述虚拟机规格参数发送给网络虚拟化编排器；网络虚拟化编排器接收所述虚拟机规格参数，根据所述虚拟机规格参数创建核心网关的虚拟机。

Description

虚拟化核心网关开局方法、装置和系统 技术领域
本申请涉及但不限于通信技术领域。
背景技术
SAE是System Architecture Evolution的简写，意为系统架构演进。在4G(the 4th Generation mobile communication technology，第四代移动通信技术)中，LTE(Long Term Evolution，长期演进)主要研究3GPP(3rd Generation Partnership Project，第三代合作伙伴计划)无线接入网的长期演进技术，升级版的LTE Advanced将最终满足国际电信联盟对4G系统的要求，SAE则是研究核心网的长期演进，它定义了一个全IP(Internet Protocol，网络之间互连的协议)的分组核心网EPC(Evolved Packet Core，4G核心网络)，该系统的特点为仅有分组域而无电路域、基于全IP结构、控制与承载分离且网络结构扁平化，其中主要包含MME(Mobility Management Entity，移动管理实体)、SGW(Serving GateWay，服务网关)、PGW(PDN GateWay，PDN网关)、PCRF(Policy and Charging Rules Function，策略与计费规则功能单元)等网元。其中SGW和PGW常常合设并被称为SAE-GW(核心网关)。
目前大部分虚拟化GW(GateWay，网关)产品都可以做到自动部署，通过在Orchestrator上注册并实例化VNF(Virtualized Network Function，虚拟化网络功能)，把一个GW局的所有虚拟机创建起来。但对于核心网关开局来说,这只是第一步，大量的业务配置还等着开局人员手工配置和调试。这使得核心网关开局效率低下，不利于降低运维成本。
上述内容仅用于辅助理解本发明的技术方案，并不代表承认上述内容是现有技术。
发明内容
以下是对本文详细描述的主题的概述。本概述并非是为了限制权利要求的保护范围。
本文提供一种虚拟化核心网关开局方法和装置，解决了核心网关开局效率低下的问题。
一种虚拟化核心网关开局方法，包括：
网络虚拟化编排器采集核心网关开局所需参数；
将所述参数传递给网络功能虚拟化管理器，以供所述网络功能虚拟化管理器调用插件得到核心网关开局所需的所有虚拟机规格参数，并将所述虚拟机规格参数发送给网络虚拟化编排器；
网络虚拟化编排器接收所述虚拟机规格参数，根据所述虚拟机规格参数创建核心网关的虚拟机。
可选地，所述网络虚拟化编排器采集核心网关开局所需参数的步骤之前，还包括：
网络虚拟化编排器创建核心网关版本包，所述核心网关版本包包括GuestOS镜像、软件版本、插件和定制信息。
可选地，所述网络虚拟化编排器创建核心网关版本包，所述核心网关版本包包括GuestOS镜像、软件版本、插件和定制信息，与所述网络虚拟化编排器采集核心网关开局所需参数步骤之间，还包括：
网络虚拟编排器将所述GuestOS镜像上传到云平台中，以供所述网络虚拟化编排器在创建核心网关的虚拟机时加载所述GuestOS镜像。
可选地，所述网络虚拟化编排器采集核心网关开局所需参数的步骤包括：
网络虚拟化编排器提供一个供用户操作的操作界面；
在所述操作界面上根据用户输入信息采集核心网关开局所需参数。
一种虚拟化核心网关开局装置，该装置包括：
采集模块，设置为：采集核心网关开局所需参数；
发送模块，设置为：将所述参数传递给网络功能虚拟化管理器，以供所 述网络功能虚拟化管理器调用插件得到核心网关开局所需的所有虚拟机规格参数，并将所述虚拟机规格参数发送给网络虚拟化编排器；
第一创建模块，设置为：接收所述虚拟机规格参数，根据所述虚拟机规格参数创建核心网关的虚拟机。
可选地，所述虚拟化核心网关开局装置还包括第二创建模块，设置为：创建核心网关版本包，所述核心网关版本包包括GuestOS镜像、软件版本、插件和定制信息。
可选地，所述虚拟化核心网关开局装置还包括上传模块，设置为：将所述GuestOS镜像上传到云平台中，以供所述网络虚拟化编排器在创建核心网关的虚拟机时加载所述GuestOS镜像。
可选地，所述采集模块包括：
提供单元，设置为：提供一个供用户操作的操作界面；
采集单元，设置为：在所述操作界面上根据用户输入信息采集核心网关开局所需参数。
一种虚拟化核心网关开局系统，所述虚拟化核心网关开局系统包括网络虚拟化编排器和网络功能虚拟化管理器；
所述网络虚拟化编排器包括上述任一项所述的装置；
所述网络虚拟化管理器设置为：接收核心网关开局所需参数，根据所述参数调用插件得到核心网关开局所需的所有虚拟机规格参数，并将所述虚拟机规格参数发送给网络虚拟化编排器。
可选地，所述网络虚拟化管理器，是设置为：调用第一插件根据核心网关开局所需参数得到定制信息，并调用所述第一插件根据所述核心网关开局所需参数计算出虚拟机相关的规格参数，并将所述规格参数保存到可扩展标记语言文件中；以及，
调用第二插件解析所述定制信息，结合所述可扩展标记语言文件得到核心网关开局所需的所有虚拟机规格参数。
一种计算机可读存储介质，存储有计算机可执行指令，所述计算机可执行指令用于执行上述任一项的方法。
本发明实施例通过网络虚拟化编排器采集核心网关开局所需参数，网络虚拟化管理器接收核心网关开局所需参数，根据所述参数调用插件得到核心网关开局所需的所有虚拟机规格参数，并将所述虚拟机规格参数发送给网络虚拟化编排器；网络虚拟化编排器接收所述虚拟机规格参数，根据所述虚拟机规格参数创建核心网关的虚拟机。在核心网关的虚拟机创建和上电的同时，核心网关开局所需要的配置信息同步完成，提升了核心网关的开局效率，降低了运维成本和开局人员的能力要求。
在阅读并理解了附图和详细描述后，可以明白其他方面。
附图概述
图1为本发明虚拟化核心网关开局方法的第一实施例的流程示意图；
图2为本发明实施例中网络虚拟化编排器采集核心网关开局所需参数的一种流程示意图；
图3为本发明虚拟化核心网关开局方法的第二实施例的流程示意图；
图4为本发明虚拟化核心网关开局装置的第一实施例的功能模块示意图；
图5为本发明实施例中采集模块的一实施例的细化功能模块图；
图6为本发明虚拟化核心网关开局装置的第二实施例的功能模块示意图；
图7为本发明虚拟化核心网关开局系统实施例的功能模块示意图。
本发明的实施方式
本发明实施例中，网络虚拟化编排器采集核心网关开局所需参数；将所述参数传递给网络功能虚拟化管理器，以供所述网络功能虚拟化管理器调用插件得到核心网关开局所需的所有虚拟机规格参数，并将所述虚拟机规格参数发送给网络虚拟化编排器；网络虚拟化编排器接收所述虚拟机规格参数， 根据所述虚拟机规格参数创建核心网关的虚拟机。通过网络虚拟化编排器采集核心网关开局所需参数并发送给网络功能虚拟化管理器，网络功能虚拟化管理器得到核心网关开局所需的所有虚拟机规格参数，并将所述虚拟机规格参数发送给网络虚拟化编排器，所述网络虚拟化编排器根据所述虚拟机规格参数创建虚拟机。在核心网关的虚拟机创建和上电的同时，核心网关开局所需要的配置信息同步完成，提升了核心网关的开局效率，降低了运维成本和开局人员的能力要求。
在相关技术的核心网关开局中，大量的业务配置都等着开局人员手工配置和调试，导致网关开局效率低下。
本发明实施例提供一种虚拟化核心网关开局方法。
参照图1，图1为本发明虚拟化核心网关开局方法的第一实施例的流程示意图。
在本实施例中，所述虚拟化核心网关开局方法包括：
步骤S10，网络虚拟化编排器采集核心网关开局所需参数；
NFV-Orchestrator(Network Functions Virtualisation Orchestrator，网络虚拟化编排器)采集核心网关SAE-GW开局所需要的数据参数，所述数据参数包括但不限于APN(Access Point Name，接入点)、service IP(服务IP)、interface IP(接口IP)等。
在自动部署过程中，NFV-Orchestrator提供一个下载路径给VNFM(Network Functions Virtualisation Manager，网络功能虚拟化管理器)，以供所述VNFM通过HTTP(Hyper Text Transfer Protocol，超文本传输协议)从所述NFV-Orchestrator下载SAE-GW软件版本，SAE-GW插件，SAE-GW定制信息，当所述VNFM成功下载到所述SAE-GW软件版本，SAE-GW插件，SAE-GW定制信息时，就会调用SAE-GW插件解析SAE-GW定制信息，从而得到SAE-GW虚拟机组的规格参数。
步骤S20，将所述参数传递给网络功能虚拟化管理器，以供所述网络功 能虚拟化管理器调用插件得到核心网关开局所需的所有虚拟机规格参数，并将所述虚拟机规格参数发送给网络虚拟化编排器；
网络虚拟化编排器将采集的数据保存到一个预设的文件中，所述预设的文件包括但不限于excel表。如将所采集的APN、service IP和interface IP等保存到一个excel表格中。网络虚拟化编排器通过预设方式将所述预设的文件传递给VNFM。所述预设方式可以为SFTP(Secure File Transfer Protocol，安全文件传送协议)，为传输文件提供一种安全的加密方法。
当VNFM接收到所述预设文件时，会调用SAE-GW注册的一个转换插件即第一插件，将这份excel表格数据转换成SAE-GW可识别的配置文件，并把所述配置文件打包到SAE-GW注册的定制信息包里。同时，所述SAE-GW注册的转换插件还要根据excel表的数据中的SAE-GW话务模型计算出本局需要创建的虚拟机相关的规格参数，保存到一个XML(Extensible Markup Language，可扩展标记语言)文件中。所述规格参数包括虚拟机数量、虚拟机类型、主用虚拟机和备用虚拟机的切换方式等等，如虚拟机的类型有微软虚拟机、Intel虚拟机、Linux虚拟机等。所述话务模型的场景有密集城区、一般城区、郊区和农村。如根据不同地区的话务量、业务速率和数据业务需求量的等的大小去创建虚拟机相关的规格参数。然后VNFM继续调用第二插件解析SAE-GW的定制信息，结合第一插件生成的XML文件，得到本次SAE-GW开局需要的虚拟机组的所有规格参数，输出为NFV-Orchestrator/VNFM可识别的XML文件。VNFM将所述可识别的XML文件发送给NFV-Orchestrator。
步骤S30，网络虚拟化编排器接收所述虚拟机规格参数，根据所述虚拟机规格参数创建核心网关的虚拟机。
当NFV-Orchestrator接收到所述可识别的XML文件时，即接收到虚拟机规格参数时，在云平台中，根据所述虚拟机规格参数创建SAE-GW的虚拟机。即根据需要的虚拟机数量、虚拟机的类型、主用虚拟机和备用虚拟机的切换方式等去创建SAE-GW的虚拟机。当SAE-GW的虚拟机上电后，NFV-Orchestrator和VNFM进行交互，所述SAE-GW从所述VNFM的硬盘上下载SAE-GW的软件版本和配置文件。在所述SAE-GW软件成功运行后，会自动 加载SAE-GW的配置文件，批量录入SAE-GW本次开局的所有配置信息。
本实施例通过网络虚拟化编排器采集核心网关开局所需参数，网络虚拟化管理器接收核心网关开局所需参数，根据所述参数调用插件得到核心网关开局所需的所有虚拟机规格参数，并将所述虚拟机规格参数发送给网络虚拟化编排器；网络虚拟化编排器接收所述虚拟机规格参数，根据所述虚拟机规格参数创建核心网关的虚拟机。在核心网关的虚拟机创建和上电的同时，核心网关开局所需要的配置信息同步完成，提升了网关的开局效率。
参照图2，图2为本发明实施例中网络虚拟化编排器采集核心网关开局所需参数的一种流程示意图。所述步骤S10包括：
步骤S11，网络虚拟化编排器提供一个供用户操作的操作界面；
步骤S12，在所述操作界面上根据用户输入信息采集核心网关开局所需参数。
NFV-Orchestrator提供一个UI操作界面给用户，用于采集核心网关SAE-GW开局所需要的数据参数，所述数据参数包括但不限于APN(Access Point Name，接入点)、service IP(服务IP)、interface IP(接口IP)等等。所述UI界面采用图形化界面，通过拖拽图标的方式定制SAE-GW需要对接的周边网元，通过弹窗提示引导的方式辅助用户完成SAE-GW的网元参数，周边网元参数，路由对接等设置。所述周边网元包括但不限于eNodeB(Evolved Node B，即演进型Node B，简称eNB，LTE中基站的名称，相比3G(3rd Generation，第三代移动通信技术)中的Node B，集成了部分RNC(Radio Network Controller，无线网络控制器)的功能，减少了通信时协议的层次)、OCS(Online Charging System，在线计费系统，它是一个实时的基于业务使用和系统进行交互计费的系统。在线计费在会话进行过程中收集计费信息，实现实时结算。如果账户没有钱了，业务也就停止了。)、AAA(Authentication，Authorization，Accounting，认证授权计费。它所提供的安全服务是指认证(Authentication)，是对用户的身份进行验证，判断其是否为合法用户；授权(Authorization)，是对通过认证的用户，授权其可以使用那些服务；计费(Accounting)，是记录用户使用网络服务的资源情况，这些 信息将作为计费的依据)等等。所述周边网元参数包括但不限于server name(服务器名)、server IP(服务IP)、Username(用户名)等。
本实施例通过网络虚拟编排器提供UI界面采集核心网关开局参数，方便了开局人员的操作。
图3为本发明虚拟化核心网关开局方法的第二实施例的流程示意图，基于第一实施例提出本发明虚拟化核心网关开局方法的第二实施例。在本实施例中，步骤S10之前，还包括：
步骤S40，网络虚拟化编排器创建核心网关版本包，所述核心网关版本包包括GuestOS(虚拟机操作系统)镜像、软件版本、插件和定制信息。
步骤S50，网络虚拟编排器将所述GuestOS镜像上传到云平台中，以供其在创建核心网关的虚拟机时加载所述GuestOS镜像。
NFV-Orchestrator在采集SAE-GW开局所需参数之前，会通过其用户创建一个SAE-GW版本包，即其用户申请注册一个SAE-GW版本包。所述SAE-GW版本包一般包括GuestOS镜像，SAE-GW软件版本，SAE-GW插件，SAE-GW定制信息四个部分。NFV-Orchestrator在注册过程中将所述镜像文件上传到云平台中，以供其在创建GW虚拟机的时候自动加载所述GuestOS镜像文件。
本实施例通过创建核心网关版本包，在创建核心网关的虚拟机时加载所述GuestOS镜像，实现使核心网关的虚拟机完成自动创建和上电的同时，网关业务开局所需要的所有配置同步完成，提升了网关的开局效率，降低了运维成本和开局人员的能力要求。
本发明实施例进一步提供一种虚拟化核心网关开局装置。
参照图4，图4为本发明虚拟化核心网关开局装置的第一实施例的功能模块示意图。
在本实施例中，所述虚拟化核心网关开局装置包括：
采集模块10，设置为：采集核心网关开局所需参数；
NFV-Orchestrator(Network Functions Virtualisation Orchestrator，网络虚拟化编排器)采集SAE-GW核心网关开局所需要的数据参数，所述数据参数包括但不限于APN(Access Point Name，接入点)、service IP(服务IP)、interface IP(接口IP)等。
在自动部署过程中，NFV-Orchestrator提供一个下载路径给VNFM(Network Functions Virtualisation Manager，网络功能虚拟化管理器)，以供所述VNFM通过HTTP(Hyper Text Transfer Protocol，超文本传输协议)从所述NFV-Orchestrator下载SAE-GW软件版本，SAE-GW插件，SAE-GW定制信息，当所述VNFM成功下载到所述SAE-GW软件版本，SAE-GW插件，SAE-GW定制信息时，就会调用SAE-GW插件解析SAE-GW定制信息，从而得到SAE-GW虚拟机组的规格参数。
发送模块20，设置为：将所述参数传递给网络功能虚拟化管理器，以供所述网络功能虚拟化管理器调用插件得到核心网关开局所需的所有虚拟机规格参数，并将所述虚拟机规格参数发送给网络虚拟化编排器；
网络虚拟化编排器将采集的数据保存到一个预设的文件中，所述预设的文件包括但不限于excel表。如将所采集的APN、service IP和interface IP等保存到一个excel表格中。网络虚拟化编排器通过预设方式将所述预设的文件传递给VNFM。所述预设方式可以为SFTP(Secure File Transfer Protocol，安全文件传送协议)，为传输文件提供一种安全的加密方法。
当VNFM接收到所述预设文件时，会调用SAE-GW注册的一个转换插件即第一插件，将这份excel表格数据转换成SAE-GW可识别的配置文件，并把所述配置文件打包到SAE-GW注册的定制信息包里。同时，所述SAE-GW注册的转换插件还要根据excel表的数据中的SAE-GW话务模型计算出本局需要创建的虚拟机相关的规格参数，保存到一个XML(Extensible Markup Language，可扩展标记语言)文件中。所述规格参数包括虚拟机数量、虚拟机类型、主用虚拟机和备用虚拟机的切换方式等等，如虚拟机的类型有微软虚拟机、Intel虚拟机、Linux虚拟机等。所述话务模型的场景有密集城区、一般城区、郊区和农村。如根据不同地区的话务量、业务速率和数据业务需求量的等的大小去创建虚拟机相关的规格参数。然后VNFM继续调用第二插件 解析SAE-GW的定制信息，结合第一插件生成的XML文件，得到本次SAE-GW开局需要的虚拟机组的所有规格参数，输出为NFV-Orchestrator/VNFM可识别的XML文件。VNFM将所述可识别的XML文件发送给NFV-Orchestrator。
第一创建模块30，设置为：接收所述虚拟机规格参数，根据所述虚拟机规格参数创建核心网关的虚拟机。
当NFV-Orchestrator接收到所述可识别的XML文件时，即接收到虚拟机规格参数时，在云平台中，根据所述虚拟机规格参数创建SAE-GW的虚拟机，即根据需要的虚拟机数量、虚拟机的类型、主用虚拟机和备用虚拟机的切换方式等去创建SAE-GW的虚拟机。当SAE-GW的虚拟机上电后，NFV-Orchestrator和VNFM进行交互，所述SAE-GW从所述VNFM的硬盘上下载SAE-GW的软件版本和配置文件。在所述SAE-GW软件成功运行后，会自动加载SAE-GW的配置文件，批量录入SAE-GW本次开局的所有配置信息。
本实施例通过网络虚拟化编排器收集核心网关开局参数，网络功能虚拟化管理器得到虚拟机规格参数，并将所述虚拟机规格参数发送给网络虚拟化编排器，所述网络虚拟化编排器根据所述虚拟机规格参数创建虚拟机。在核心网关的虚拟机创建和上电的同时，核心网关开局所需要的配置信息同步完成，提升了网关的开局效率。
参照图5，图5为本发明实施例中采集模块的一实施例的细化功能
模块图。在本实施例中，所述采集模块10包括：
提供单元11，设置为：提供一个供用户操作的操作界面；
采集单元12，设置为：在所述操作界面上根据用户输入信息采集核心网关开局所需参数。
NFV-Orchestrator提供一个UI操作界面给用户，用于采集核心网关SAE-GW开局所需要的数据参数，所述数据参数包括但不限于APN(Access Point Name，接入点)、service IP(服务IP)、interface IP(接口IP)等等。所述UI界面采用图形化界面，通过拖拽图标的方式定制SAE-GW需要对接 的周边网元，通过弹窗提示引导的方式辅助用户完成SAE-GW的网元参数，周边网元参数，路由对接等设置。所述周边网元包括但不限于eNodeB(Evolved Node B，即演进型Node B，简称eNB，LTE中基站的名称，相比3G(3rd Generation，第三代移动通信技术)中的Node B，集成了部分RNC(Radio Network Controller，无线网络控制器)的功能，减少了通信时协议的层次)、OCS(Online Charging System，在线计费系统，它是一个实时的基于业务使用和系统进行交互计费的系统。在线计费在会话进行过程中收集计费信息，实现实时结算。如果账户没有钱了，业务也就停止了。)、AAA(Authentication，Authorization，Accounting，认证授权计费。它所提供的安全服务是指认证(Authentication)，是对用户的身份进行验证，判断其是否为合法用户；授权(Authorization)，是对通过认证的用户，授权其可以使用那些服务；计费(Accounting)，是记录用户使用网络服务的资源情况，这些信息将作为计费的依据)等等。所述周边网元参数包括但不限于server name(服务器名)、server IP(服务IP)、Username(用户名)等。
本实施例通过网络虚拟编排器提供UI界面采集核心网关开局参数，方便了开局人员的操作。
参照图6，图6为本发明虚拟化核心网关开局装置的第二实施例的功能模块示意图。基于第一实施例提出本发明虚拟化核心网关开局装置的第二实施例。在本实施例中，所述虚拟化核心网关开局装置还包括：
第二创建模块40，设置为：创建核心网关版本包，所述核心网关版本包包括GuestOS镜像、软件版本、插件和定制信息。
上传模块50，设置为：将所述GuestOS镜像上传到云平台中，以供其在创建核心网关的虚拟机时加载所述GuestOS镜像。
NFV-Orchestrator在采集SAE-GW开局所需参数之前，会通过其用户创建一个SAE-GW版本包，即其用户申请注册一个SAE-GW版本包。所述SAE-GW版本包一般包括GuestOS镜像，SAE-GW软件版本，SAE-GW插件，SAE-GW定制信息四个部分。NFV-Orchestrator在注册过程中将所述镜像文件上传到云平台中，以供其在创建GW虚拟机的时候自动加载所述GuestOS 镜像文件。
本实施例通过创建核心网关版本包，在创建核心网关的虚拟机时加载所述GuestOS镜像，实现使核心网关的虚拟机完成自动创建和上电的同时，网关业务开局所需要的所有配置同步完成，提升了网关的开局效率，降低了运维成本和开局人员的能力要求。
本发明实施例进一步地提供了一种虚拟化核心网关开局系统。
参照图7，图7为本发明虚拟化核心网关开局系统实施例的功能模块示意图。
在本实施例中，所述虚拟化核心网关开局系统包括网络虚拟化编排器110和网络功能虚拟化管理器220。
NFV-Orchestrator在采集SAE-GW开局所需参数之前，会通过其用户创建一个SAE-GW版本包，即其用户申请注册一个SAE-GW版本包。所述SAE-GW版本包一般包括GuestOS镜像，SAE-GW软件版本，SAE-GW插件，SAE-GW定制信息四个部分。NFV-Orchestrator在注册过程中将所述镜像文件上传到云平台中，以供其在创建GW虚拟机的时候自动加载所述GuestOS镜像文件。在自动部署过程中，NFV-Orchestrator提供一个下载路径给VNFM，以供所述VNFM通过HTTP(Hyper Text Transfer Protocol，超文本传输协议)从所述NFV-Orchestrator下载SAE-GW软件版本，SAE-GW插件，SAE-GW定制信息。
NFV-Orchestrator(Network Functions Virtualisation Orchestrator，网络虚拟化编排器110)提供一个UI(User Interface，用户界面)操作界面给用户，用于采集核心网关SAE-GW开局所需要的数据参数，所述数据参数包括但不限于APN(Access Point Name，接入点)、service IP(服务IP)、interface IP(接口IP)等等。所述UI界面采用图形化界面，通过拖拽图标的方式定制SAE-GW需要对接的周边网元，通过弹窗提示引导的方式辅助用户完成SAE-GW的网元参数，周边网元参数，路由对接等设置。所述周边网元包括但不限于eNodeB(Evolved Node B，即演进型Node B，简称eNB，LTE中基 站的名称，相比3G(3rd Generation，第三代移动通信技术)中的Node B，集成了部分RNC(Radio Network Controller，无线网络控制器)的功能，减少了通信时协议的层次)、OCS(Online Charging System，在线计费系统，它是一个实时的基于业务使用和系统进行交互计费的系统。在线计费在会话进行过程中收集计费信息，实现实时结算。如果账户没有钱了，业务也就停止了。)、AAA(Authentication，Authorization，Accounting，认证授权计费。它所提供的安全服务是指认证(Authentication)，是对用户的身份进行验证，判断其是否为合法用户；授权(Authorization)，是对通过认证的用户，授权其可以使用那些服务；计费(Accounting)，是记录用户使用网络服务的资源情况，这些信息将作为计费的依据)等等。所述周边网元参数包括但不限于server name(服务器名)、server IP(服务IP)、Username(用户名)等。
网络虚拟化编排器110将采集的数据保存到一个预设的文件中，所述预设的文件包括但不限于excel表。如将所采集的APN、service IP和interface IP等保存到一个excel表格中。网络虚拟化编排器110通过预设方式将所述预设的文件传递给VNFM(Network Functions Virtualisation Manager，网络功能虚拟化管理器)。所述预设方式可以为SFTP(Secure File Transfer Protocol，安全文件传送协议)，为传输文件提供一种安全的加密方法。
当NFV-Orchestrator接收到所述可识别的XML文件时，即接收到虚拟机规格参数时，在云平台中，根据所述虚拟机规格参数创建SAE-GW的虚拟机，即根据需要的虚拟机数量、虚拟机的类型、主用虚拟机和备用虚拟机的切换方式等去创建SAE-GW的虚拟机。
所述网络功能虚拟化管理器220设置为：调用插件生成可扩展标记语言文件和解析核心网关的定制信息，得到虚拟机规格参数，并将所述虚拟机规格参数发送给网络虚拟化编排器110。
所述网络虚拟化管理器220是设置为：调用第一插件根据核心网关开局所需参数得到定制信息，并调用所述第一插件根据所述核心网关开局所需参数计算出虚拟机相关的规格参数，并将所述规格参数保存到可扩展标记语言文件中；以及，调用第二插件解析所述定制信息，结合所述可扩展标记语言文件得到核心网关开局所需的所有虚拟机规格参数。
VNFM通过HTTP从所述NFV-Orchestrator下载SAE-GW软件版本，SAE-GW插件，SAE-GW定制信息，当所述VNFM成功下载到所述SAE-GW软件版本，SAE-GW插件，SAE-GW定制信息时，就会调用SAE-GW插件解析SAE-GW定制信息，从而得到SAE-GW虚拟机组的规格参数。
当VNFM接收到NFV-Orchestrator传递的预设的文件时，会调用SAE-GW注册的一个转换插件，即第一插件，将这份excel表格数据转换成SAE-GW可识别的配置文件，并把所述配置文件打包到SAE-GW注册的定制信息包里。同时，所述SAE-GW注册的转换插件还要根据excel表的数据中的SAE-GW话务模型计算出本局需要创建的虚拟机相关的规格参数，保存到一个XML(Extensible Markup Language，可扩展标记语言)文件中。所述规格参数包括虚拟机数量、虚拟机类型、主用虚拟机和备用虚拟机的切换方式等等，如虚拟机的类型有微软虚拟机、Intel虚拟机、Linux虚拟机等。所述话务模型的场景有密集城区、一般城区、郊区和农村。如根据不同地区的话务量、业务速率和数据业务需求量的等的大小去创建虚拟机相关的规格参数。然后VNFM继续调用第二插件解析SAE-GW的定制信息，结合第二插件生成的XML文件，得到本次SAE-GW开局需要的虚拟机组的所有规格参数，输出为NFV-Orchestrator/VNFM可识别的XML文件。VNFM将所述可识别的XML文件发送给NFV-Orchestrator。
当SAE-GW的虚拟机上电后，NFV-Orchestrator和VNFM进行交互，从所述VNFM的硬盘上下载SAE-GW的软件版本和配置文件。在所述SAE-GW软件成功运行后，会自动加载SAE-GW的配置文件，批量录入SAE-GW本次开局的所有配置信息。
本领域普通技术人员可以理解上述实施例的全部或部分步骤可以使用计算机程序流程来实现，所述计算机程序可以存储于一计算机可读存储介质中，所述计算机程序在相应的硬件平台上(如系统、设备、装置、器件等)执行，在执行时，包括方法实施例的步骤之一或其组合。
可选地，上述实施例的全部或部分步骤也可以使用集成电路来实现，这些步骤可以被分别制作成一个个集成电路模块，或者将它们中的多个模块或步骤制作成单个集成电路模块来实现。
上述实施例中的装置/功能模块/功能单元可以采用通用的计算装置来实现，它们可以集中在单个的计算装置上，也可以分布在多个计算装置所组成的网络上。
上述实施例中的装置/功能模块/功能单元以软件功能模块的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。上述提到的计算机可读取存储介质可以是只读存储器，磁盘或光盘等。
工业实用性
通过本发明实施例，在核心网关的虚拟机创建和上电的同时，核心网关开局所需要的配置信息同步完成，提升了核心网关的开局效率，降低了运维成本和开局人员的能力要求。

Claims (11)

  1. 一种虚拟化核心网关开局方法，包括：
    网络虚拟化编排器采集核心网关开局所需参数；
    将所述参数传递给网络功能虚拟化管理器，以供所述网络功能虚拟化管理器调用插件得到核心网关开局所需的所有虚拟机规格参数，并将所述虚拟机规格参数发送给网络虚拟化编排器；
    网络虚拟化编排器接收所述虚拟机规格参数，根据所述虚拟机规格参数创建核心网关的虚拟机。
  2. 如权利要求1所述的虚拟化核心网关开局方法，其中，所述网络虚拟化编排器采集核心网关开局所需参数的步骤之前，还包括：
    网络虚拟化编排器创建核心网关版本包，所述核心网关版本包包括虚拟机操作系统GuestOS镜像、软件版本、插件和定制信息。
  3. 如权利要求2所述的虚拟化核心网关开局方法，其中，所述网络虚拟化编排器创建核心网关版本包，所述核心网关版本包包括GuestOS镜像、软件版本、插件和定制信息，与所述网络虚拟化编排器采集核心网关开局所需参数步骤之间，还包括：
    网络虚拟编排器将所述GuestOS镜像上传到云平台中，以供所述网络虚拟化编排器在创建核心网关的虚拟机时加载所述GuestOS镜像。
  4. 如权利要求1至3任一项所述的虚拟化核心网关开局方法，其中，所述网络虚拟化编排器采集核心网关开局所需参数的步骤包括：
    网络虚拟化编排器提供一个供用户操作的操作界面；
    在所述操作界面上根据用户输入信息采集核心网关开局所需参数。
  5. 一种虚拟化核心网关开局装置，所述虚拟化核心网关开局装置包括：
    采集模块，设置为：采集核心网关开局所需参数；
    发送模块，设置为：将所述参数传递给网络功能虚拟化管理器，以供所述网络功能虚拟化管理器调用插件得到核心网关开局所需的所有虚拟机规格参数，并将所述虚拟机规格参数发送给网络虚拟化编排器；
    第一创建模块，设置为：接收所述虚拟机规格参数，根据所述虚拟机规格参数创建核心网关的虚拟机。
  6. 如权利要求5所述的虚拟化核心网关开局装置，所述虚拟化核心网关开局装置还包括第二创建模块，设置为：创建核心网关版本包，所述核心网关版本包包括GuestOS镜像、软件版本、插件和定制信息。
  7. 如权利要求6所述的虚拟化核心网关开局装置，所述虚拟化核心网关开局装置还包括上传模块，设置为：将所述GuestOS镜像上传到云平台中，以供所述网络虚拟化编排器在创建核心网关的虚拟机时加载所述GuestOS镜像。
  8. 如权利要求5至7任一项所述的虚拟化核心网关开局装置，其中，所述采集模块包括：
    提供单元，设置为：提供一个供用户操作的操作界面；
    采集单元，设置为：在所述操作界面上根据用户输入信息采集核心网关开局所需参数。
  9. 一种虚拟化核心网关开局系统，所述虚拟化核心网关开局系统包括网络虚拟化编排器和网络功能虚拟化管理器；
    所述网络虚拟化编排器包括权利要求5至8中任一项所述的装置；
    所述网络虚拟化管理器设置为：接收核心网关开局所需参数，根据所述参数调用插件得到核心网关开局所需的所有虚拟机规格参数，并将所述虚拟机规格参数发送给网络虚拟化编排器。
  10. 如权利要求9所述的虚拟机核心网关开局系统，其中，所述网络虚拟化管理器是设置为：调用第一插件根据核心网关开局所需参数得到定制信息，并调用所述第一插件根据所述核心网关开局所需参数计算出虚拟机相关的规格参数，并将所述规格参数保存到可扩展标记语言文件中；以及，
    调用第二插件解析所述定制信息，结合所述可扩展标记语言文件得到核心网关开局所需的所有虚拟机规格参数。
  11. 一种计算机可读存储介质，存储有计算机可执行指令，所述计算机可执行指令用于执行权利要求1-4任一项的方法。
PCT/CN2015/096002 2015-06-23 2015-11-30 虚拟化核心网关开局方法、装置和系统 WO2016206306A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201510349769.9 2015-06-23
CN201510349769.9A CN106304144A (zh) 2015-06-23 2015-06-23 虚拟化核心网关开局方法、装置和系统

Publications (1)

Publication Number Publication Date
WO2016206306A1 true WO2016206306A1 (zh) 2016-12-29

Family

ID=57584406

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2015/096002 WO2016206306A1 (zh) 2015-06-23 2015-11-30 虚拟化核心网关开局方法、装置和系统

Country Status (2)

Country Link
CN (1) CN106304144A (zh)
WO (1) WO2016206306A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114217708A (zh) * 2021-12-15 2022-03-22 腾讯科技（深圳）有限公司 虚拟场景中开局操作的控制方法、装置、设备及存储介质

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107231296B (zh) * 2017-05-11 2020-04-14 京信通信系统（中国）有限公司 一种网关装置
CN112867035B (zh) * 2021-01-18 2023-08-25 中盈优创资讯科技有限公司 一种5g传输网spn网元一键开局方法及装置

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104348873A (zh) * 2013-08-05 2015-02-11 中兴通讯股份有限公司 虚拟网元自动装载及虚拟机ip地址获取的方法与系统
CN104410672A (zh) * 2014-11-12 2015-03-11 华为技术有限公司 网络功能虚拟化应用升级的方法、转发业务的方法及装置
CN104601592A (zh) * 2015-01-31 2015-05-06 华为技术有限公司 一种接入云服务的方法及接入设备

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8954515B2 (en) * 2010-06-30 2015-02-10 Alcatel Lucent Method and apparatus for reducing application update traffic in cellular networks
CN102710814B (zh) * 2012-06-21 2016-03-30 北京奇虎科技有限公司 虚拟机ip地址的控制方法及装置
CN102799464B (zh) * 2012-06-25 2015-11-11 北京奇虎科技有限公司 虚拟机创建方法及系统、虚拟机重装方法及系统
US10033595B2 (en) * 2013-08-27 2018-07-24 Futurewei Technologies, Inc. System and method for mobile network function virtualization
WO2015113278A1 (zh) * 2014-01-29 2015-08-06 华为技术有限公司 虚拟网络功能的升级方法和网络功能虚拟化编排器

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104348873A (zh) * 2013-08-05 2015-02-11 中兴通讯股份有限公司 虚拟网元自动装载及虚拟机ip地址获取的方法与系统
CN104410672A (zh) * 2014-11-12 2015-03-11 华为技术有限公司 网络功能虚拟化应用升级的方法、转发业务的方法及装置
CN104601592A (zh) * 2015-01-31 2015-05-06 华为技术有限公司 一种接入云服务的方法及接入设备

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114217708A (zh) * 2021-12-15 2022-03-22 腾讯科技（深圳）有限公司 虚拟场景中开局操作的控制方法、装置、设备及存储介质
CN114217708B (zh) * 2021-12-15 2023-05-26 腾讯科技（深圳）有限公司 虚拟场景中开局操作的控制方法、装置、设备及存储介质

Also Published As

Publication number Publication date
CN106304144A (zh) 2017-01-04

Similar Documents

Publication Publication Date Title
US20220150746A1 (en) Systems and methods for providing mobility aspects to applications in the cloud
RU2643451C2 (ru) Система и способ виртуализации функции мобильной сети
US20120303776A1 (en) Methods and systems for data compliance management associated with cloud migration events
US20170048200A1 (en) Providing a Basic Firewall Using a Virtual Networking Function
US20160057234A1 (en) Service Compiler Component and Service Controller for Open Systems Interconnection Layer 4 Through Layer 7 Services in a Cloud Computing System
US12069202B2 (en) Charging apparatus, method, system, and non-transitory medium
WO2013040917A1 (zh) 虚拟桌面实现系统及其使用方法
WO2016206306A1 (zh) 虚拟化核心网关开局方法、装置和系统
CN105677663A (zh) 对自助办税终端进行统一管理的方法和系统
US20220239783A1 (en) Charging and collection function in microservices
CN110505069A (zh) 一种生成定制化话单的方法及装置
Rusti et al. Deploying Smart City components for 5G network slicing
WO2020048504A1 (zh) 网络功能所需资源的部署方法、装置、存储介质及电子装置
WO2017088347A1 (zh) 基于云平台的应用用户使用信息管理的方法、设备及系统
CN106341463A (zh) 一种基于物联网的移动互联音视频管控系统
JP2019213161A (ja) 管理装置、移動体通信システム、プログラム及び管理方法
CN108667873A (zh) 一种分流方法、分流装置、电子设备和可读存储介质
EP3466120B1 (en) Systems and methods for providing mobility aspects to applications in the cloud
CN105357097A (zh) 虚拟网络的调节方法及系统
KR102425978B1 (ko) 클라우드 서비스 플랫폼에서 Composite 웹 UI 제공시스템
US20240364817A1 (en) Charging apparatus, method, system, and non-transitory medium
Harsh et al. A highly available generic billing architecture for heterogenous mobile cloud services
Carapinha et al. VNFaaS with end-to-end full service orchestration
Kaura-aho Scalable IoT traffic generation system using LTE network
Jonnalagadda Generation and Validation of Network Configuration for Evolved Packet Core

Legal Events

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

Ref document number: 15896190

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 15896190

Country of ref document: EP

Kind code of ref document: A1