WO2018032884A1 - 一种计费方法、装置及系统 - Google Patents

一种计费方法、装置及系统 Download PDF

Info

Publication number
WO2018032884A1
WO2018032884A1 PCT/CN2017/090611 CN2017090611W WO2018032884A1 WO 2018032884 A1 WO2018032884 A1 WO 2018032884A1 CN 2017090611 W CN2017090611 W CN 2017090611W WO 2018032884 A1 WO2018032884 A1 WO 2018032884A1
Authority
WO
WIPO (PCT)
Prior art keywords
charging
information
vnfm
charging information
vim
Prior art date
Application number
PCT/CN2017/090611
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 EP17840860.5A priority Critical patent/EP3471337B1/en
Publication of WO2018032884A1 publication Critical patent/WO2018032884A1/zh
Priority to US16/271,868 priority patent/US20190173681A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/14—Charging, metering or billing arrangements for data wireline or wireless communications
    • H04L12/1403—Architecture for metering, charging or billing
    • H04L12/1407—Policy-and-charging control [PCC] architecture
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/14—Charging, metering or billing arrangements for data wireline or wireless communications
    • H04L12/1403—Architecture for metering, charging or billing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/58—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP based on statistics of usage or network monitoring
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/62—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP based on trigger specification
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/64—On-line charging system [OCS]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/66—Policy and charging system
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/70—Administration or customization aspects; Counter-checking correct charges
    • H04M15/785—Reserving amount on the account
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/82—Criteria or parameters used for performing billing operations
    • H04M15/8278—Event based

Definitions

  • the present invention relates to the field of communications, and in particular, to a charging method, apparatus, and system.
  • Network Function Virtualization technology can be simply understood as the migration of the functions of the various network elements used in the telecommunications network from the current dedicated hardware platform to the common commercial off-the-shelf (Commercial off-the- Shelf, COTS) on the server.
  • NFV Network Function Virtualization
  • COTS Commercial off-the-shelf
  • the functions of each network element can be flexibly deployed on a unified infrastructure platform built by other devices such as standards-based servers, storage, and switches.
  • virtualizing the infrastructure hardware device resources pooling and virtualization virtual resources can be provided to upper-layer applications, thereby realizing application and hardware decoupling, which enables each application to rapidly increase virtual resources to achieve rapid expansion of the system.
  • the common COTS server is used to form a shared resource pool, and the newly developed service does not need to separately deploy hardware devices, which greatly shortens the online time of new services.
  • the foundation of NFV technology includes cloud computing technology and virtualization technology.
  • Universal COTS computing, storage, networking and other hardware devices can be decomposed into multiple virtual resources through virtualization technology for use by various applications in the upper layers.
  • the decoupling between the application and the hardware is realized by the virtualization technology, so that the virtual resource supply speed is greatly increased.
  • the cloud computing technology the elastic scalability of the application can be realized, and the virtual resources are matched with the service load, which not only improves the utilization efficiency of the virtual resources, but also improves the response rate of the system.
  • Embodiments of the present invention provide a charging method and apparatus, which can implement charging based on an NFV architecture.
  • a system for charging based on an NFV architecture, including an NFVO and a charging system, wherein the NFVO receives a quota from a charging system, and when the triggering event occurs, acquiring the virtual network
  • the charging information of the function manager VNFM and the charging information of the virtual infrastructure manager VIM, wherein the charging information of the VNFM includes the usage information of the quota, and the charging information from the VNFM and the charging information from the VIM are sent to
  • the billing system performs billing based on the received billing information.
  • a charging method is provided, the method being applied to charging based on an NFV architecture, comprising: NFVO receiving a quota from a charging system, wherein the quota is used by an NFVO control network service NS or a virtual network The use of the function VNF instance; when the triggering event occurs, the NFVO acquires the charging information from the virtual network function manager VNFM and the charging information of the virtual infrastructure manager VIM, wherein the triggering event includes an internal triggering event or an external triggering event, The occurrence of internal trigger events is obtained by NFVO active detection. The occurrence of external trigger events is obtained by NFVO according to the active reporting of VNFM or VIM.
  • the charging information from VNFM contains the usage information of quotas.
  • NFVO sends the meter from VNFM to the billing system. Fee information and from VIM Billing information.
  • the charging system can perform charging according to the usage information of the quota, and implement charging based on the NFV architecture.
  • the quota includes a duration quota or an event quota, and specifically includes a duration quota corresponding to the NS, a duration quota corresponding to the VNF, and an event quota corresponding to the VNF. At least one.
  • the event quota corresponding to the VNF for example, the VNF is a virtualized short message service, and the corresponding event quota may be 100,000 short messages.
  • the flexibility of billing based on the NFV architecture is increased by billing time or event.
  • the first possible implementation manner of the second aspect in the second possible implementation manner, before the NFVO sends the charging information from the VNFM and the charging information from the VIM to the charging system, the NFVO Associated with the charging information from the VNFM and the charging information from the VIM, the NFVO sends the charging information from the VNFM to the charging system and the charging information from the VIM: the NFVO sends the associated charging information to the charging system.
  • the NFVO associates the charging from the VNFM according to the correspondence between the identifier of the VNF instance and the identifier of the VM.
  • Information and billing information from VIM from VIM.
  • the charging information from the VNFM further includes an identifier of the VNF instance, and the NFVO is based on the identifier of the NS
  • the corresponding relationship between the identifier of the VNF instance and the identifier of the VNF instance associates the VNF instance in the charging information from the VNFM to the corresponding NS.
  • the relevant parameters of the VNF may also include the provider of the VNF, abnormal information, and the like.
  • the charging system can perform charging for using the NS.
  • the internal trigger event includes a network service NS state change or a VNF state change.
  • the NS state change includes at least one of NS instance update, NS instance expansion, NS instance shrinkage, NS instance scaling, NS startup, and NS instance termination.
  • the VNF state change includes VNF instance expansion, VNF instance shrinkage, and VNF instance scaling. At least one of a VNF start, a VNF instance termination, a VNF required resource allocation request, and a VNF required resource release request.
  • the external triggering event includes the status information reported by the VNFM or the status information reported by the VIM.
  • the status information reported by the VNFM includes at least one of a change in the number of virtual machine VMs used by the VNF instance, a VNF abnormal event, and a state change of the reserved VNF instance.
  • the status information reported by the VIM includes the area to which the resource used by the VNF belongs. Or the resource status reserved by VIM changes.
  • the event reporting mechanism consisting of an internal trigger event and an external trigger event enables NFVO to more accurately and comprehensively determine the acquisition and reporting timing of billing information, and enhance the accuracy of billing.
  • the charging information from the VIM includes resource usage information of the VM.
  • a charging method is provided, which is applied to charging based on an NFV architecture, including: the charging system sends a quota to the NFVO, wherein the quota is used for the NFVO control network service NS or the virtual network function VNF instance. Use; the billing system receives billing information from NFVO, wherein billing information is carried The usage information of the amount includes charging information from the VNFM and charging information from the VIM; the charging system performs charging according to the received charging information.
  • the charging system can perform charging according to the usage information of the quota, and implements charging based on the NFV architecture.
  • the charging system after the charging system receives the charging information from the VNFM and the charging information from the VIM, the charging system associates the charging from the VNFM. The information and the charging information from the VIM, the charging system performs charging according to the received charging information: the charging system performs charging according to the associated charging information.
  • the charging system associates the charging information from the VNFM according to the correspondence between the identifier of the VNF instance and the identifier of the VM. Billing information from VIM.
  • the charging information from the VNFM further includes the identifier of the VNF instance, and the charging system is based on the NS Corresponding to the identifier of the VNF instance and the identifier of the VNF instance, the VNF instance in the charging information from the VNFM is associated with the corresponding NS.
  • the charging system can perform charging for using the NS.
  • a computing device in a fourth aspect, the device being applied to charging based on an NFV architecture, including a processor, a memory, a bus, and a communication interface; the memory is configured to store a computing device to execute an instruction, and the processor and the memory are connected through a bus When the computing device is in operation, the processor executes the memory-stored computing device to execute the instructions to cause the computing device to perform the method of any one of the second aspect and the second aspect.
  • a fifth aspect provides a computing device, which is applied to charging based on an NFV architecture, including a processor, a memory, a bus, and a communication interface; the memory is configured to store a computing device to execute an instruction, and the processor and the memory are connected through a bus.
  • the processor executes the memory-stored computing device to execute the instructions to cause the computing device to perform the method of any one of the third aspect and the third aspect.
  • a computer readable storage medium wherein executable program code is stored, the program code being used to implement the method of any one of the second aspect and the second aspect.
  • a computer readable storage medium wherein executable program code is stored, the program code being used to implement the method of any one of the third aspect and the third aspect.
  • a charging apparatus comprising means for performing the method of any of the possible implementations of the second aspect and the second aspect.
  • a charging apparatus comprising means for performing the method of any one of the third aspect and the third aspect.
  • the charging information from the VNFM and the charging information from the VIM are reported to the charging system by the NFVO, and the charging system performs charging according to the received charging information, and implements the NFV-based architecture.
  • Billing the event reporting mechanism consisting of an internal trigger event and an external trigger event enables NFVO to more accurately and comprehensively determine the acquisition and reporting timing of billing information, and enhance the accuracy of billing.
  • a tenth aspect provides a charging method, including: when a first triggering event occurs, the NFVO sends the first charging information to the charging system; when the second triggering event occurs, the VNFM sends the second to the charging system.
  • the charging information is sent by the VIM to the charging system when the third triggering event occurs; the charging system associates the first charging information, the second charging information, and the third charging information for charging.
  • the first trigger event includes a periodic report or an NS state change
  • the second trigger event includes a periodic report or a VNF state change
  • the third trigger event includes a periodic report or a state change of a resource required by the VNF.
  • the first charging information includes an identifier of the NS, an identifier of the VNF instance included in the NS, an identifier of the VM used by the VNF instance, and usage information of the NS, where the second charging information includes an identifier of the VNF instance, and the identifier
  • the usage information of the VNF instance; the third charging information includes an identifier of the VM, and usage information of the VM.
  • the NFVO, the VNFM, and the VIM respectively transmit the first charging information, the second charging information, and the third charging information to the charging system, so that the charging system can associate and charge the received charging information, thereby realizing Billing based on the NFV architecture.
  • the VNFM sends the second charging information to the charging system by using the NFVO, and the VIM sends the third charging information to the charging system by using the NFVO. This avoids the definition of new interfaces between VNFM, VIM and billing systems, reducing complexity.
  • a charging method including: when a second triggering event occurs, the VNFM sends the second charging information to the NFVO; when the third triggering event occurs, the VIM sends the third charging information to the NFVO.
  • the NFVO associates the second charging information with the third charging information to obtain the associated charging information.
  • the NFVO sends the associated charging information to the charging system.
  • the first trigger event includes a periodic report or an NS state change
  • the second trigger event includes a periodic report or a VNF state change
  • the third trigger event includes a periodic report or a state change of a resource required by the VNF.
  • the NFVO includes an NS identifier, an identifier of the VNF instance included in the NS, and an identifier of the VM used by the VNF instance.
  • the second charging information includes an identifier of the VNF instance and usage information of the VNF instance.
  • the third charging information includes The ID of the VM and the usage information of the VM.
  • the NFVO can send the associated second charging information and the third charging information to the charging system, so that the charging system can charge the received charging information, and implement the NFV-based charging.
  • FIG. 1 is a schematic diagram of an NFV system 100 to which an embodiment of the present invention is applied;
  • FIG. 2 is a schematic diagram showing the hardware structure of a computer device 200 according to an embodiment of the invention.
  • FIG. 3 is an exemplary flowchart of a charging method 300 in accordance with an embodiment of the present invention.
  • FIG. 4 is an exemplary flow diagram of a charging method 400 in accordance with an embodiment of the present invention.
  • FIG. 5 is an exemplary flowchart of a charging method 500 in accordance with an embodiment of the present invention.
  • FIG. 6 is a schematic diagram showing the location of each functional logic entity according to an embodiment of the invention.
  • FIG. 7 is a schematic diagram showing the location of each functional logic entity according to an embodiment of the invention.
  • FIG. 8 is a schematic structural diagram of a charging apparatus 800 according to an embodiment of the present invention.
  • FIG. 9 is a schematic structural diagram of a charging apparatus 900 according to an embodiment of the present invention.
  • the NFV system 100 can be implemented in various networks, such as a data center network, a carrier network, or a local area network.
  • the NFV system 100 includes an NFV Management and Orchestration (NFV MANO) 101, an NFV Infrastructure (NFV) 130, a plurality of virtual network functions (VNF) 108, and multiple network elements.
  • NFV MANO NFV Management and Orchestration
  • NFV NFV Infrastructure
  • VNF virtual network functions
  • EM Element Management
  • OSS/BSS Operation-Support System/Business Support System
  • VNF and Infrastructure Description Network Service, VNF and Infrastructure Description
  • the NFV management and orchestration system 101 includes an NFV Orchestrator (NFVO) 102, one or more VNF Managers (VNF Managers, VNFMs) 104, and a Virtualized Infrastructure Manager (VIM) 106.
  • the NFVI 130 includes computing hardware 112, storage hardware 114, network hardware 116, virtualization layer, virtual computing 110, virtual storage 118, and virtual network 120.
  • Network services, VNF and infrastructure descriptions 126, and OSS/BSS 124 are discussed further in the ETSI GS NFV 002 V1.1.1 standard.
  • the NFV MANO 101 is used to perform monitoring and management of the VNF 108 and NFVI 130.
  • the NFVO 102 may implement a Network Service (NS) on the NFVI 130, may also perform resource related requests from one or more VNFMs 104, send configuration information to the VNFM 104, and collect status information for the VNF 108.
  • NFVO 102 can communicate with VIM 106 to enable resource allocation or reservation, as well as to exchange configuration and status information for virtualized hardware resources.
  • NS Network Service
  • the VNFM 104 can manage one or more VNFs 108.
  • the VNFM 104 can perform various management functions such as instantiating, updating, querying, scaling, and terminating the VNF 108.
  • the VIM 106 can perform resource management functions, such as managing the allocation of infrastructure resources (eg, adding resources to virtual containers), or performing operational functions such as collecting NFVI failure information.
  • VNFM 104 and VIM 106 can communicate with each other for resource allocation and exchange of configuration and status information for virtualized hardware resources.
  • the NFVI 130 includes hardware resources, software resources, or a combination of both to complete the deployment of the virtualized environment.
  • the hardware resources and virtualization layers are used to provide virtualized resources, such as virtual machines and other forms of virtual containers, for VNF 108.
  • Hardware resources include computing hardware 112, storage hardware 114, and network hardware 116.
  • Computing hardware 112 may be off-the-shelf hardware or user-customized hardware used to provide processing and computing resources.
  • Storage hardware 114 may be storage capacity provided within the network or storage capacity resident in storage hardware 114 itself (local storage located within the server). In one implementation, the resources of computing hardware 112 and storage hardware 114 may be grouped together.
  • Network hardware 116 can be a switch, a router, or any other network device configured to have switching functionality.
  • Network hardware 116 can span multiple domains and can include multiple networks interconnected by one or more transport networks.
  • the virtualization layer within NFVI 130 can abstract hardware resources from the physical layer and decouple VNF 108 to provide virtualized resources to VNF 108.
  • the virtual resource layer includes virtual computing 110, virtual storage 118, and virtual network Network 120.
  • Virtual computing 110 and virtual storage 118 may be provided to VNF 108 in the form of a virtual machine, or other virtual container.
  • one or more VNFs 108 can be deployed on a virtual machine.
  • the virtualization layer abstracts network hardware 116 to form a virtual network 120, which may include a virtual switch that is used to provide connectivity between virtual machines and other virtual machines.
  • the transport network in network hardware 116 can be virtualized using a centralized control plane and a separate forwarding plane (eg, software defined network, SDN).
  • FIG. 2 is a schematic diagram showing the hardware structure of a computer device 200 according to an embodiment of the invention.
  • computer device 200 includes a processor 202, a memory 204, a communication interface 206, and a bus 208.
  • the processor 202, the memory 204, and the communication interface 206 implement a communication connection with each other through the bus 208.
  • the processor 202 can be a general-purpose central processing unit (CPU), a microprocessor, an application specific integrated circuit (ASIC), or one or more integrated circuits for executing related programs.
  • CPU central processing unit
  • ASIC application specific integrated circuit
  • the memory 204 can be a read only memory (ROM), a static storage device, a dynamic storage device, or a random access memory (RAM).
  • the memory 204 can store an operating system 2041 and other applications 2042.
  • the program code for implementing the technical solution provided by the embodiment of the present invention is stored in the memory 204 and executed by the processor 202.
  • Communication interface 206 enables communication with other devices or communication networks using transceivers such as, but not limited to, transceivers.
  • Bus 208 can include a path for communicating information between various components (e.g., processor 202, memory 204, communication interface 206).
  • the processor 202 is configured to perform receiving a quota from the billing system; when the triggering event occurs, acquiring billing information from the virtual network function manager VNFM and billing of the virtual infrastructure manager VIM Information, the trigger event includes an internal trigger event or an external trigger event, the occurrence of the internal trigger event being actively detected by the processor 202, the occurrence of the external trigger event being performed by the processor 202 according to the VNFM or the VIM
  • the billing information from the VNFM includes usage information of the quota; the billing information from the VNFM and the billing information from the VIM are sent to the billing system.
  • the processor 202 is configured to perform sending a quota to the NFVO, and receive charging information from the NFVO, where the charging information carries usage information of the quota, where the charging information includes Charging information from the VNFM and charging information from the VIM; charging is performed based on the received charging information.
  • FIG. 3 is an exemplary flow diagram of a charging method 300 in accordance with an embodiment of the present invention.
  • the charging method 300 may be provided by the NFVO 102, the VNFM 104, the VIM 106 shown in FIG. 1 and included in FIG. 1
  • the billing system in the illustrated BSS 124 is implemented.
  • the NFVO sends a quota request message to the charging system.
  • the charging system receives a quota request message from the NFVO.
  • the NFVO sends the quota request message by extending the existing interface Os-Ma-nfvo of the NFVO and the BSS, or may also send the quota request message by defining a new interface (for example, defining a new interface according to the requirements of the Diameter protocol).
  • the charging system sends a quota to the NFVO.
  • the quota is an NS granularity or a VNF granularity.
  • the quota is used for the use of the NFVO Control Network Service NS or the use of a virtual network function VNF instance.
  • the NFVO receives the quota from the billing system.
  • the NFVO acquires charging information from the virtual network function manager VNFM and charging information of the virtual infrastructure manager VIM, where the triggering event includes an internal triggering event or an external triggering event.
  • the charging information from the VNFM contains usage information of the quota.
  • the charging information from the VNFM further includes related parameters of the VNF, and the related parameters of the VNF include an identifier of the VNF instance, a provider of the VNF, an abnormality information of the VNF, and the like.
  • the charging information reported by the VNFM may include the following information, as shown in Table 1:
  • a network service NS is composed of one or more VNF instances.
  • the VNF instance is a concept in the prior art, and refers to a run-time instantiation of the VNF software, which is a result of completing the instantiation of the virtual deployment unit (VDU) and the connection between the VDUs.
  • the VNF describes the VNF deployment and operational information captured in the VNF Description (VNFD) 126, as well as additional runtime-specific information and constraints.
  • the accounting information sent by the VNFM carries the usage information of the quota by the VNF instance.
  • the accounting information sent by the VNFM carries the quota usage information of the VNF instance, and the NFVO determines the quota usage information of the NS according to the usage information of the quota by the VNF instance. For example, the quota is allowed to use NS for 10 hours.
  • the NS includes three VNF instances VNF1, VNF2, and VNF3. After the quota is issued by the billing system, the startup time of VNF1, VNF2, and VNF3 is different, and VNF1, VNF2, and VNF3 are respectively operated for 8 hours.
  • the accounting information sent by the VNFM carries the usage information of the quotas of VNF1, VNF2, and VNF3 for 8 hours, 5 hours, and 1 hour, and the maximum time of 8 hours for NFVO is used as the quota usage information of the NS.
  • NFVO applies quotas for each VNF instance.
  • NS contains 3 VNFs.
  • VNF1, VNF2, and VNF3 if the VNF1 quota is used up, NFVO will re-apply for VNF1 regardless of whether the VNF2 and VNF3 quotas are used up.
  • NFVO applies for quotas for all VNF instances.
  • NS contains three VNF instances VNF1, VNF2, and VNF3. As long as the quota usage of one of the VNF instances reaches the quota size issued, NFVO will re-establish Apply for quotas for VNF1, VNF2, and VNF3.
  • the charging information from the VIM includes resource usage information of a virtual machine (VM).
  • VM virtual machine
  • the accounting information reported by the VIM may include the following information, as shown in Table 2:
  • the resource usage information of the VM may be: for example, within 2 hours, the CPU usage rate is 30%, the Memory usage rate is 40%, the storage occupancy is 50G, and the Network bandwidth traffic is 300G.
  • the internal trigger event includes a network service NS state change or a VNF state change
  • the NS state change includes an NS instance update (Network service instance update), an NS instance expansion (Network service instance scaling out), and an NS instance shrinkage.
  • NS instance update Network service instance update
  • Network service instance scaling out Network service instance scaling out
  • NS instance shrinkage At least one of a network service instance scaling in, a network service instance scaling up/down, a network service instantiation, and a network service instance termination
  • the VNF state change includes VNF scaling out, VNF scaling in, VNF scaling up/down, VNF instantiation, VNF instance termination, VNF required resources
  • the external triggering event includes the status information reported by the VNFM or the status information reported by the VIM.
  • the status information reported by the VNFM includes the number of virtual machine VMs used by the VNF instance, and the VNF abnormality.
  • At least one of the VNF instance state changes, the status information reported by the VIM includes a regional change to which the resource used by the VNF belongs or a resource state change reserved by the VIM.
  • the state change of the reserved VNF instance includes the VNF instance changing from the active state to the waiting state, or from the waiting state to the active state.
  • the resource state change reserved by the VIM includes the reserved resource changing from the active state to the waiting state, or from the waiting state to the active state.
  • VNF anomalies include VNF restarts, alarms, and CPS per second below or above a preset threshold.
  • the occurrence of the internal trigger event can be obtained by the NFVO active detection.
  • the NFVO can periodically request the status of the NS or the status of the VNF.
  • the occurrence of an external trigger event can be obtained by the NFVO based on the active reporting of the VNFM or VIM. For example, when the VNF is restarted, the VNFM reports this event to the NFVO.
  • the event reporting mechanism consisting of an internal trigger event and an external trigger event enables NFVO to more accurately and comprehensively determine the acquisition and reporting timing of billing information, and enhance the accuracy of billing.
  • the NFVO obtains charging information from the VNFM and the VIM.
  • the charging information obtained from the VNFM may be Including the VNF identifier, and the start time and running time of the VNF
  • the billing information obtained from the VIM may include the identifier of the VM, the start time of the VM, and usage information of resources such as CPU, Memory, Storage, and Network.
  • the NFVO receives the information that the reserved VNF instance reported by the VNFM changes from the waiting state to the active state, the NFVO acquires the charging information from the VNFM and the VIM.
  • the NFVO sends the charging information from the VNFM and the charging information from the VIM to the charging system.
  • the charging system receives charging information from the NFVO, where the charging information carries usage information of the quota, where the charging information includes charging information from the VNFM and charging information from the VIM.
  • the charging system performs charging according to the received charging information.
  • the NFVO sends the charging information through the extended interface NFVO in the foregoing step 302 and the existing interface Os-Ma-nfvo of the BSS, or sends the charging information through the new interface defined in the foregoing step 302.
  • the NFVO associates the charging information from the VNFM with the The billing information of the VIM, the NFVO sending the billing information from the VNFM and the billing information from the VIM to the billing system: after the NFVO sends the association to the billing system Billing information.
  • the associated charging information may include the following information, as shown in Table 3.
  • the charging system can perform charging for using the NS.
  • the NFVO associates the charging information from the VNFM and the charging information from the VIM according to the correspondence between the identifier of the VNF instance and the identifier of the VM.
  • the correspondence between the identifier of the VNF instance and the identifier of the VM may be configured in the NFVO in advance.
  • the NFVO stores an identifier of the NS, and an identifier of the VNF instance included in the NS (or a correspondence between the identifier of the NS and the identifier of the VNF instance).
  • the NFVO associates the VNF instance in the charging information from the VNFM to the corresponding NS according to the identifier of the VNF instance included in the NS and the identifier of the VNF instance in the charging information of the VNFM, and obtains the charging information of the NS.
  • the charging information of the NS is sent to the charging system, and the charging system performs charging for using the NS according to the charging information.
  • the NFVO associates the charging information from the VNFM with the charging information from the VIM, and the obtained charging information of the NS includes the identifier of the NS, and the NS Start time, NS usage time, VNF list, VM list, where VM list contains CPU, Memory, Storage, and Network usage information.
  • the NFVO may also not associate the charging information from the VNFM with the charging information from the VIM, but send them to the charging system.
  • the charging system After the charging system receives the charging information from the VNFM and the charging information from the VIM, the charging system associates the charging information from the VNFM with the charging information from the VIM, Then, the charging system performs charging according to the received charging information: the charging system performs charging according to the associated charging information.
  • the charging system associates the received charging information, instead of the NFVO associating the charging information, which can reduce the burden of NFVO and reduce its complexity.
  • the charging system associates the charging information from the VNFM and the charging information from the VIM according to the correspondence between the identifier of the VNF instance and the identifier of the VM.
  • the VNF instance in the charging information from the VNFM is associated with the corresponding NS, and the charging information of the NS is obtained, and the charging system calculates the used NS according to the charging information. fee.
  • the correspondence between the identifier of the VNF instance and the identifier of the VM (or the identifier of the VM used by the VNF instance) may be configured in the charging system in advance, or may be sent by the NFVO to the charging system.
  • the identifier of the NS and the identifier of the instance of the VNF included in the NS may be configured in the charging system in advance, or may be sent by the NFVO to the charging system.
  • the charging system may also use the VNF to perform charging according to the charging information from the VNFM and the charging information from the VIM.
  • the charging information from the VNFM may further include a start time of each VNF instance, a duration of use of each VNF instance, and charging information from the VIM may also include a start time of the VM, and a CPU, a Memory, and a Storage.
  • Information such as the use of resources such as Network, the billing system can use the VNF to charge based on the information.
  • the charging information from the VNFM and the charging information from the VIM are reported to the charging system by the NFVO, and the charging system performs charging according to the received charging information, and implements the NFV based on the NFV.
  • Architecture billing the charging information from the VNFM and the charging information from the VIM are reported to the charging system by the NFVO, and the charging system performs charging according to the received charging information, and implements the NFV based on the NFV.
  • the billing method 400 can be performed by the NFVO 102, the VNFM 104, the VIM 106, and the billing system included in the BSS 124 shown in FIG.
  • the NFVO sends the first charging information to the charging system.
  • the NFVO sends the first charging information through the existing interface Os-Ma-nfvo of the NFVO and the BSS, or may also send the first by defining a new interface (for example, defining a new interface according to the requirements of the Diameter protocol). Billing information.
  • the first trigger event includes a periodic report (which can be implemented by setting a timer) or an NS state change.
  • the NS state change includes at least one of NS instance update, NS instance expansion, NS instance shrinkage, NS instance scaling, NS startup, and NS instance termination.
  • the first trigger event can be pre-configured in the NFVO.
  • the NFVO stores the collected first charging information, and then sends the first charging information to the charging system when the first triggering event occurs.
  • the first charging information includes an identifier of the NS, an identifier of the VNF instance included in the NS, an identifier of the VM used by the VNF instance, and usage information of the NS.
  • the usage information of the NS can be the duration of use of the NS or the number of uses of the NS.
  • the first charging information may include the following information, as shown in Table 4.
  • the VNFM sends the second charging information to the charging system.
  • the VNFM can send the second charging information through a new interface defined between the charging system and the charging system.
  • the second trigger event includes a periodic report or a VNF state change.
  • the VNF state change includes at least one of VNF instance expansion, VNF instance shrinkage, VNF instance expansion, VNF startup, and VNF instance termination.
  • the second trigger event can be pre-configured in the VNFM. When the second triggering event does not occur, the VNFM stores the collected second charging information, and then sends the second charging information to the charging system when the second triggering event occurs.
  • the second charging information includes an identifier of the VNF instance, and usage information of the VNF instance.
  • the usage information of the VNF instance includes the duration of use or the number of uses of the VNF instance.
  • the second charging information may include the following information, as shown in Table 5:
  • the VIM sends the third charging information to the charging system.
  • the VIM may send the third charging information through a new interface defined between the charging system and the charging system.
  • the third trigger event includes a periodic report or a state change of a resource required by the VNF.
  • the state change of the resources required by the VNF includes a request for allocation of resources required by the VNF or a request for release of resources required by the VNF.
  • the third trigger event can be pre-configured in the VIM.
  • the VIM stores the collected third charging information, and then sends the third charging information to the charging system when the third triggering event occurs.
  • the third charging information includes an identifier of the VM and usage information of the VM.
  • the usage information of the VM includes resource information used by the VM or the occupation time of the VM.
  • the third charging information may include the following information, as shown in Table 6:
  • the charging system associates the first charging information, the second charging information, and the third charging information for charging.
  • the charging system associates the first charging information and the second charging information according to the identifier of the VNF instance in the first charging information and the identifier of the VNF instance in the second charging information; according to the VNF instance in the first charging information Corresponding relationship between the identifier and the identifier of the VM, and the identifier of the VM in the third billing information is associated with the first billing information and the third billing information. Since the first charging information includes the identifier of the VNF instance included in the NS, the accounting information of the NS can be obtained after the association, and the charging system performs charging for using the NS. Since the second billing information includes the usage information of the VNF instance, the VNF can be used for billing after the association.
  • the VNFM sends the second charging information to the charging system by using the NFVO.
  • the VNFM sends the second charging information to the NFVO
  • the NFVO sends the second charging information to the charging system.
  • the VNFM sends the second charging information through the existing interface Or-vnfm of the NFVO and the VNFM, or the second charging information may be sent by defining a new interface.
  • the VIM sends the third charging information to the charging system through the NFVO.
  • the VIM sends the third charging information to the NFVO
  • the NFVO sends the third charging information to the charging system.
  • the VIM sends the third charging information through the existing interface Or-Vi of the NFVO and the VIM, or may also send the third charging information by defining a new interface.
  • S401, S402, and S403 sequence is for the purpose of clearly describing the embodiments of the present invention, and is not intended to limit the sequence in which the NFVO, VNFM, and VIM send charging information to the charging system, when the respective trigger events. If it occurs, the corresponding billing information is sent to the billing system.
  • the charging system can enable the charging system to associate the received charging information by transmitting the first charging information, the second charging information, and the third charging information to the charging system.
  • Billing which implements billing based on the NFV architecture.
  • FIG. 5 is an exemplary flow diagram of a charging method 500 in accordance with an embodiment of the present invention.
  • the billing method 500 can be performed by the NFVO 102, the VNFM 104, the VIM 106, and the billing system included in the BSS 124 shown in FIG. Different from the embodiment of Fig. 4, in the embodiment of Fig. 5, the second charging information and the third charging information are associated by NFVO.
  • the VNFM sends the second charging information to the NFVO.
  • the VNFM sends the second charging information through the existing interface of the NFVO and the VNFM, Or-vnfm, or
  • the second billing information can also be sent by defining a new interface.
  • related content of the second trigger event and the second charging information may refer to related content in the embodiment S402 of FIG. 4 .
  • the VIM sends the third charging information to the NFVO.
  • the VIM sends the third charging information through the existing interface Or-Vi of the NFVO and the VIM, or may also send the third charging information by defining a new interface.
  • the related content of the third trigger event and the third charging information may refer to related content in the embodiment S403 of FIG. 4 .
  • the NFVO associates the second charging information with the third charging information, and obtains the associated charging information.
  • the NFVO stores an NS identifier, an identifier of the VNF instance included in the NS, and an identifier of the VM used by the VNF instance (or a correspondence between the identifier of the VNF instance and the identifier of the VM).
  • the NFVO associates the usage information of the VNF instance in the second charging information with the corresponding NS according to the identifier of the VNF instance included in the NS and the identifier of the VNF instance in the second charging information; according to the identifier of the VNF and the identifier of the VM
  • the relationship, and the identifier of the VM in the third billing information associates the usage information of the VM in the third billing information to the corresponding VNF. After the association, the accounting information of the NS can be obtained.
  • the NFVO sends the associated charging information to the charging system.
  • the charging system charges the received charging information.
  • the NFVO sends the accounting information of the NS to the charging system, and the charging system performs charging for using the NS. Since the charging information of the NS includes the usage information of the VNF instance, the charging system can perform charging for using the VNF.
  • the charging system can enable the charging system to perform charging on the received charging information by transmitting the associated second charging information and third charging information to the charging system. Billing based on the NFV architecture.
  • the embodiment of FIG. 3 may be charged by the charging trigger function logical entity included in the NFVO 102 shown in FIG. 1, and the charging included in the VNFM 104 shown in FIG. 1.
  • the reporting function logical entity, the charging reporting function logical entity included in the VIM 106 shown in FIG. 1, and the charging system included in the BSS 124 shown in FIG. 1 are executed.
  • S301, S304, S305, and S306 in the embodiment of FIG. 3 are executed by the charging trigger function logic entity in the NFVO 102.
  • S305 the charging trigger function logic entity in the NFVO 102 acquires the charging information from the charging reporting function logical entity in the VNFM 104 and the charging information of the charging reporting function logical entity in the VIM 106.
  • the embodiment of FIG. 4 may be included in the VNFM 104 shown in FIG. 1 by the first charging trigger function logic entity included in the NFVO 102 shown in FIG. 1.
  • the second charging trigger function logical entity, the third charging trigger function logical entity included in the VIM 106 shown in FIG. 1, and the charging system included in the BSS 124 shown in FIG. 1 are executed.
  • the first charging trigger function logic entity executes S401 in the embodiment of FIG. 4
  • the second charging trigger function logic entity executes S402 in the embodiment of FIG. 4
  • the third charging trigger function logic entity executes the figure. 4 in the embodiment S403.
  • the embodiment of FIG. 5 may be included in the embodiment shown in FIG. 1.
  • the logical entity and the billing system included in the BSS 124 shown in FIG. 1 are executed.
  • the second charging trigger function logic entity executes S501 in the embodiment of FIG. 5
  • the third charging trigger function logic entity executes S502 in the embodiment of FIG. 5
  • the first charging trigger function logic entity executes the figure. 5, S503, S504 in the embodiment.
  • FIG. 8 is a schematic structural diagram of a charging apparatus 800 according to an embodiment of the present invention.
  • the charging device 800 includes a receiving module 802, a processing module 804, and a transmitting module 806.
  • the billing device 800 is the computer device 200 of FIG. 2 or the NFVO shown in FIG.
  • the receiving module 802 can be used to execute S304 in the example of FIG. 3.
  • the processing module 804 can be used to execute S305 in the embodiment of FIG. 3.
  • the sending module 806 can be used to execute S301, S306 in the embodiment of FIG.
  • the receiving module 802 is configured to receive a quota from the charging system.
  • the processing module 804 is configured to acquire charging information from the virtual network function manager VNFM and charging information of the virtual infrastructure manager VIM when the triggering event occurs, where the triggering event includes an internal trigger event or an external trigger event.
  • the occurrence of the internal trigger event is obtained by the processing module 804, and the occurrence of the external trigger event is obtained by the processing module 804 according to the VNFM or the active reporting of the VIM, and the charging information from the VNFM includes the Information on the use of quotas.
  • the sending module 806 is configured to send the charging information from the VNFM and the charging information from the VIM to the charging system.
  • the processing module 804 is further configured to associate the charging information from the VNFM with The charging module from the VIM sends the charging information from the VNFM and the charging information from the VIM to the charging system: the sending module 806 sends the charging system to the charging system.
  • the billing information after the association is described.
  • the processing module 804 associates the charging information from the VNFM and the charging information from the VIM according to the correspondence between the identifier of the VNF instance and the identifier of the VM.
  • the charging information from the VNFM further includes the identifier of the VNF instance, and the processing module 804, according to the correspondence between the identifier of the NS and the identifier of the VNF instance, and the identifier of the VNF instance, the VNF in the charging information from the VNFM.
  • the instance is associated with the corresponding NS.
  • the charging information from the VIM includes resource usage information of the VM.
  • FIG. 7 is a schematic structural diagram of a charging apparatus 900 according to an embodiment of the present invention.
  • the charging device 900 includes a transmitting module 902, a receiving module 904, and a processing module 906.
  • the billing device 900 is the computer device 200 of FIG. 2 or the billing system shown in FIG.
  • the sending module 902 can be used to execute S303 in the embodiment of FIG. 3.
  • the receiving module 904 can be used to execute S302, S307 in the embodiment of FIG. 3.
  • the processing module 906 can be used to execute S308 in the embodiment of FIG.
  • the sending module 902 is configured to send a quota to the NFVO.
  • the receiving module 904 is configured to receive charging information from the NFVO, where the charging information carries usage information of the quota, where the charging information includes charging information from the VNFM and charging information from the VIM.
  • the processing module 906 is configured to perform charging according to the received charging information.
  • the processing module 906 is further configured to associate the charging information from the VNFM with the meter from the VIM. For the fee information, the processing module 906 performs charging according to the received charging information:
  • the processing module 906 performs charging according to the associated charging information.
  • the processing module 906 associates the charging information from the VNFM and the charging information from the VIM according to the correspondence between the identifier of the VNF instance and the identifier of the VM.
  • the charging information from the VNFM further includes an identifier of the VNF instance, and the processing module 906 associates the VNF instance in the charging information from the VNFM according to the correspondence between the identifier of the NS and the identifier of the VNF instance and the identifier of the VNF instance. Go to the corresponding NS.
  • the charging information from the VNFM and the charging information from the VIM are reported to the charging system, and the charging system performs charging according to the received charging information, thereby implementing the NFV-based architecture. Billing.
  • the "module" in the embodiment of FIG. 8 and FIG. 9 may be an Application Specific Integrated Circuit (ASIC), an electronic circuit, a processor and a memory that execute one or more software or firmware programs, a combination logic circuit, and Other components that provide the above features.
  • ASIC Application Specific Integrated Circuit
  • the foregoing charging device is implemented by using a computer device.
  • the receiving module and the sending module may be implemented by a processor, a memory, and a communication interface of the computer device, where the processing module may be configured by a processor and a memory of the computer device.
  • the computer device 200 shown in FIG. 2 only shows the processor 202, the memory 204, the communication interface 206, and the bus 208, in the specific implementation process, those skilled in the art should understand that the above charging device also Contains other devices necessary to achieve proper operation. At the same time, those skilled in the art will appreciate that the above-described charging device may also include hardware devices that implement other additional functions, depending on the particular needs. Moreover, those skilled in the art will appreciate that the above-described charging device may also only include the components necessary to implement the embodiments of the present invention, and does not necessarily include all of the devices shown in FIG.
  • each functional unit in each embodiment of the present invention 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 above integrated unit can be implemented in the form of hardware or in the form of a software functional unit.
  • the integrated unit if implemented in the form of a software functional unit and sold or used as a standalone product, may be stored in a computer readable storage medium.
  • the technical solution of the present invention which is essential or contributes to the prior art, or all or part of the technical solution, may be embodied in the form of a software product stored in a storage medium.
  • a number of instructions are included to cause a computer device (which may be a personal computer, server, or network device, etc.) or a processor to perform all or part of the steps of the methods described in various embodiments of the present invention.
  • 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)
  • Physics & Mathematics (AREA)
  • Probability & Statistics with Applications (AREA)
  • Meter Arrangements (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

本发明的实施例提供一种计费方法，包括网络功能虚拟化编排器NFVO接收来自计费系统的配额；当触发事件发生时，所述NFVO获取来自虚拟网络功能管理器VNFM的计费信息和虚拟基础设施管理器VIM的计费信息，所述触发事件包括内部触发事件或外部触发事件，所述来自VNFM的计费信息包含所述配额的使用信息；所述NFVO向所述计费系统发送所述来自VNFM的计费信息和所述来自VIM的计费信息，实现了基于NFV架构的计费。

Description

一种计费方法、装置及系统
本申请要求于2016年8月15日提交中国专利局、申请号为201610671813.2，发明名称为“一种计费方法、装置及系统”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本发明涉及通信领域，尤其涉及一种计费方法、装置及系统。
背景技术
网络功能虚拟化(英文：Network Function Virtualization；缩写：NFV)技术可以简单地理解为将电信网络中使用的各个网元的功能从目前的专用硬件平台迁移至通用的商用现货(Commercial off-the-shelf，COTS)服务器上。通过NFV技术将电信网络中使用的各个网元转变成为独立的应用，可以实现将各个网元的功能灵活部署在基于标准的服务器、存储以及交换机等其他设备构建的统一基础设施平台上的目的。并且，通过虚拟化技术对基础设施硬件设备资源池化及虚拟化，能够实现对上层应用提供虚拟资源，从而实现应用与硬件解耦，这使得每一个应用能够快速增加虚拟资源以实现快速扩展系统容量的目的，或者能够快速减少虚拟资源以实现收缩系统容量的目的，大大提升了网络的弹性。采用通用的COTS服务器组成共享的资源池，新开发的业务不需要单独部署硬件设备，大大缩短了新业务的上线时间。
NFV技术的基础包含云计算技术和虚拟化技术。通用的COTS计算、存储、网络等硬件设备通过虚拟化技术可以分解为多种虚拟资源，以供上层各种应用使用。通过虚拟化技术实现应用与硬件之间的解耦，使得虚拟资源供给速度大大增加。通过云计算技术可以实现应用的弹性伸缩，实现虚拟资源与业务负荷相匹配，不仅提升了虚拟资源的利用效率，而且改善了系统的响应速率。
目前并没有基于NFV架构的计费方法。
发明内容
本发明的实施例提供一种计费方法和装置，能够实现基于NFV架构的计费。
第一方面，提供了一种系统，该系统应用于基于NFV架构下的计费，包括NFVO和计费系统，其中，NFVO接收来自计费系统的配额，当触发事件发生时，获取来自虚拟网络功能管理器VNFM的计费信息和虚拟基础设施管理器VIM的计费信息，其中，VNFM的计费信息中包含配额的使用信息，将来自VNFM的计费信息和来自VIM的计费信息发送给计费系统，计费系统根据接收到的计费信息进行计费。
第二方面，提供了一种计费方法，该方法应用于基于NFV架构下的计费，包括：NFVO接收来自计费系统的配额，其中，配额用于NFVO控制网络服务NS的使用或虚拟网络功能VNF实例的使用；当触发事件发生时，NFVO获取来自虚拟网络功能管理器VNFM的计费信息和虚拟基础设施管理器VIM的计费信息，其中，触发事件包括内部触发事件或外部触发事件，内部触发事件的发生由NFVO主动检测获得，外部触发事件的发生由NFVO根据VNFM或VIM的主动上报来获得，来自VNFM的计费信息包含配额的使用信息；NFVO向计费系统发送来自VNFM的计费信息和来自VIM的 计费信息。
通过向计费系统上报来自VNFM的计费信息和来自VIM的计费信息，使得计费系统能够依据配额的使用信息进行计费，实现了基于NFV架构的计费。
结合第二方面的实现方式，在第二方面第一种可能的实现方式中，配额包括时长配额或事件配额，具体包括NS对应的时长配额、VNF对应的时长配额、VNF对应的事件配额中的至少一种。其中，VNF对应的事件配额，例如VNF为虚拟化的短消息服务，对应的事件配额可以为发送10万条短消息。
通过对时长或事件计费增加了基于NFV架构计费的灵活性。
结合第二方面、第二方面的第一种可能的实现方式，在第二种可能实现的方式中，在NFVO向计费系统发送来自VNFM的计费信息和来自VIM的计费信息之前，NFVO关联来自VNFM的计费信息和来自VIM的计费信息，则NFVO向计费系统发送来自VNFM的计费信息和来自VIM的计费信息为：NFVO向计费系统发送关联后的计费信息。
结合第二方面、第二方面的第一种至第二种可能的实现方式，在第三种可能实现的方式中，NFVO根据VNF实例的标识与VM的标识的对应关系关联来自VNFM的计费信息和来自VIM的计费信息。
结合第二方面、第二方面的第一种至第三种可能的实现方式，在第四种可能实现的方式中，来自VNFM的计费信息还包含VNF实例的标识，NFVO根据NS的标识与VNF实例的标识的对应关系以及该VNF实例的标识，将来自VNFM的计费信息中的VNF实例关联到相应的NS下。
VNF的相关参数还可以包含VNF的提供商、异常信息等。
由于关联计费信息后可以得到NS的计费信息，因此使得计费系统可以对使用NS进行计费。
结合第二方面、第二方面的第一种至第四种可能的实现方式，在第五种可能实现的方式中，内部触发事件包括网络服务NS状态变化或VNF状态变化。NS状态变化包括NS实例更新、NS实例扩容、NS实例缩容、NS实例伸缩、NS启动、NS实例终止中的至少一种；VNF状态变化包括VNF实例扩容、VNF实例缩容、VNF实例伸缩、VNF启动、VNF实例终止、VNF所需资源的分配请求、VNF所需资源的释放请求中的至少一种。
结合第二方面、第二方面的第一种至第五种可能的实现方式，在第六种可能实现的方式中，外部触发事件包括VNFM上报的状态信息或VIM上报的状态信息。VNFM上报的状态信息包括VNF实例使用的虚拟机VM的数量变化、VNF异常事件、预留的VNF实例状态变化中的至少一种；VIM上报的状态信息包括VNF所使用的资源所属的区域发生变化或VIM预留的资源状态发生变化。
由内部触发事件和外部触发事件构成的事件上报机制使得NFVO能够更准确、全面的确定计费信息的获取和上报时机，增强了计费的准确性。
结合第二方面、第二方面的第一种至第六种可能的实现方式，在第七种可能实现的方式中，来自VIM的计费信息包含VM的资源使用信息。
第三方面，提供了一种计费方法，该方法应用于基于NFV架构下的计费，包括：计费系统向NFVO发送配额，其中，配额用于NFVO控制网络服务NS或虚拟网络功能VNF实例的使用；计费系统接收来自NFVO的计费信息，其中，计费信息携带配 额的使用信息，计费信息包括来自VNFM的计费信息和来自VIM的计费信息；计费系统根据接收到的计费信息进行计费。
通过接收来自VNFM的计费信息和来自VIM的计费信息，计费系统能够依据配额的使用信息进行计费，实现了基于NFV架构的计费。
结合第三方面的实现方式，在第三方面第一种可能的实现方式中，在计费系统接收来自VNFM的计费信息和来自VIM的计费信息后，计费系统关联来自VNFM的计费信息和来自VIM的计费信息，则计费系统根据接收到的计费信息进行计费为：计费系统根据关联后的计费信息进行计费。
结合第三方面、第三方面的第一种可能的实现方式，在第二种可能实现的方式中，计费系统根据VNF实例的标识与VM的标识的对应关系关联来自VNFM的计费信息和来自VIM的计费信息。
结合第三方面、第三方面的第一种至第二种可能的实现方式，在第三种可能实现的方式中，来自VNFM的计费信息还包含VNF实例的标识，计费系统根据NS的标识与VNF实例的标识的对应关系以及VNF实例的标识，将来自VNFM的计费信息中的VNF实例关联到相应的NS下。
由于关联计费信息后可以得到NS的计费信息，因此使得计费系统可以对使用NS进行计费。
第四方面，提供了一种计算设备，该设备应用于基于NFV架构下的计费，包括处理器、存储器、总线和通信接口；存储器用于存储计算设备执行指令，处理器与存储器通过总线连接，当计算设备运行时，处理器执行存储器存储的计算设备执行指令，以使计算设备执行第二方面及第二方面的任意一种可能的实现方式所述的方法。
第五方面，提供了一种计算设备，该设备应用于基于NFV架构下的计费，包括处理器、存储器、总线和通信接口；存储器用于存储计算设备执行指令，处理器与存储器通过总线连接，当计算设备运行时，处理器执行存储器存储的计算设备执行指令，以使计算设备执行第三方面及第三方面的任意一种可能的实现方式所述的方法。
第六方面，提供了一种计算机可读存储介质，其中存储有可执行的程序代码，该程序代码用以实现第二方面及第二方面的任意一种可能的实现方式所述的方法。
第七方面，提供了一种计算机可读存储介质，其中存储有可执行的程序代码，该程序代码用以实现第三方面及第三方面的任意一种可能的实现方式所述的方法。
第八方面，提供了一种计费装置，包含用于执行第二方面及第二方面的任意一种可能的实现方式中的方法的模块。
第九方面，提供了一种计费装置，包含用于执行第三方面及第三方面的任意一种可能的实现方式中的方法的模块。
根据本发明实施例提供的技术方案，通过NFVO向计费系统上报来自VNFM的计费信息和来自VIM的计费信息，计费系统根据接收到的计费信息进行计费，实现了基于NFV架构的计费。同时，由内部触发事件和外部触发事件构成的事件上报机制使得NFVO能够更准确、全面的确定计费信息的获取和上报时机，增强了计费的准确性。
第十方面，提供了一种计费方法，包括：当第一触发事件发生时，NFVO向计费系统发送第一计费信息；当第二触发事件发生时，VNFM向计费系统发送第二计费信息；当第三触发事件发生时，VIM向计费系统发送第三计费信息；计费系统关联第一计费信息、第二计费信息、第三计费信息进行计费。其中，第一触发事件包括周期上报或NS状态变化，第二触发事件包括周期上报或VNF状态变化，第三触发事件包括周期上报或VNF所需资源的状态变化。其中，第一计费信息包含NS的标识，该NS包含的VNF实例的标识，该VNF实例使用的VM的标识，以及该NS的使用信息；第二计费信息包含VNF实例的标识，及该VNF实例的使用信息；第三计费信息包含VM的标识，以及该VM的使用信息。
NFVO、VNFM、VIM通过向计费系统分别发送第一计费信息、第二计费信息、第三计费信息，使得计费系统能够对接收到的计费信息进行关联和计费，实现了基于NFV架构的计费。
结合第十方面，在第十方面的第一种可能的实现方式中，VNFM通过NFVO向计费系统发送第二计费信息，VIM通过NFVO向计费系统发送第三计费信息。这样能够避免定义VNFM、VIM与计费系统之间的新接口，降低复杂度。
第十一方面，提供了一种计费方法，包括：当第二触发事件发生时，VNFM向NFVO发送第二计费信息；当第三触发事件发生时，VIM向NFVO发送第三计费信息；NFVO关联第二计费信息和第三计费信息，得到关联后的计费信息；当第一触发事件发生时，NFVO向计费系统发送关联后的计费信息。其中，第一触发事件包括周期上报或NS状态变化，第二触发事件包括周期上报或VNF状态变化，第三触发事件包括周期上报或VNF所需资源的状态变化。其中，NFVO存储有NS标识，该NS包含的VNF实例的标识，VNF实例使用的VM的标识；第二计费信息包含VNF实例的标识，及该VNF实例的使用信息；第三计费信息包含VM的标识，以及该VM的使用信息。
NFVO通过向计费系统发送关联后的第二计费信息、第三计费信息，使得计费系统能够对接收到的计费信息进行计费，实现了基于NFV架构的计费。
附图说明
为了更清楚地说明本发明实施例或现有技术中的技术方案，下面将对实施例或现有技术描述中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本发明的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其他的附图。
图1是本发明实施例应用的NFV系统100的示意图；
图2是依据本发明一实施例的计算机设备200的硬件结构示意图；
图3是依据本发明一实施例的计费方法300的示范性流程图；
图4是依据本发明一实施例的计费方法400的示范性流程图；
图5是依据本发明一实施例的计费方法500的示范性流程图；
图6是依据本发明一实施例的各功能逻辑实体的位置示意图；
图7是依据本发明一实施例的各功能逻辑实体的位置示意图；
图8是依据本发明一实施例的计费装置800的结构示意图；
图9是依据本发明一实施例的计费装置900的结构示意图。
具体实施方式
以下描述中，为了说明而不是为了限定，提出了诸如特定系统结构、接口、技术之类的具体细节，以便透彻理解本发明。然而，本领域的技术人员应当清楚，在没有这些具体细节的其它实施例中也可以实现本发明。在其它情况中，省略对众所周知的装置、电路以及方法的详细说明，以免不必要的细节妨碍本发明的描述。
图1是本发明实施例应用的NFV系统100的示意图，NFV系统100可以在各种网络中使用，例如在数据中心网络、运营商网络或局域网来实现。NFV系统100包括NFV管理和编排系统(NFV Management and Orchestration,NFV MANO)101、NFV基础设施层(NFV Infrastructure,NFVI)130、多个虚拟网络功能(Virtual Network Function,VNF)108、多个网元管理(Element Management,EM)122、业务支持管理系统(Operation-Support System/Business Support System,OSS/BSS)124，以及网络服务、VNF和基础设施描述(Network Service,VNF and Infrastructure Description)126。其中，NFV管理和编排系统101包括NFV编排器(NFV Orchestrator,NFVO)102，一个或多个VNF管理器VNFM(VNF Manager,VNFM)104，虚拟基础设施管理器(Virtualized Infrastructure Manager,VIM)106。NFVI130包括计算硬件112、存储硬件114、网络硬件116、虚拟化层(Virtualization Layer)、虚拟计算110、虚拟存储118和虚拟网络120。网络服务、VNF和基础设施描述126以及OSS/BSS 124在ETSI GS NFV 002V1.1.1标准中有进一步的讨论。
NFV MANO 101用于执行对VNF 108和NFVI 130的监视和管理。
NFVO 102可以实现在NFVI 130上的网络服务(Network Service，NS)，也可以执行来自一个或多个VNFM 104的资源相关请求，发送配置信息到VNFM 104，并收集VNF 108的状态信息。另外，NFVO 102可以与VIM 106通信，以实现资源的分配或预留，以及交换虚拟化硬件资源的配置和状态信息。
VNFM 104可以管理一个或多个VNF 108。VNFM 104可以执行各种管理功能，如实例化、更新、查询、缩放和终止VNF 108等。
VIM 106可以执行资源管理的功能，例如管理基础设施资源的分配(例如增加资源到虚拟容器)，也可以执行操作功能，如收集NFVI故障信息。VNFM 104和VIM106可以相互通信进行资源分配和交换虚拟化硬件资源的配置和状态信息。
NFVI 130包括硬件资源、软件资源或两者的组合来完成虚拟化环境的部署。换句话说，硬件资源和虚拟化层用于提供虚拟化的资源，例如作为虚拟机和其它形式的虚拟容器，用于VNF 108。硬件资源包括计算硬件112、存储硬件114和网络硬件116。计算硬件112可以是市场上现成的硬件或用户定制的硬件，用来提供处理和计算资源。存储硬件114可以是网络内提供的存储容量或驻留在存储硬件114本身的存储容量(位于服务器内的本地存储器)。在一个实现方案中，计算硬件112和存储硬件114的资源可以被集中在一起。网络硬件116可以是交换机、路由器或配置成具有交换功能的任何其他网络设备。网络硬件116可以横跨多个域，并且可以包括多个由一个或一个以上传输网络互连的网络。
NFVI 130里面的虚拟化层可以从物理层抽象硬件资源和解耦VNF 108，以便向VNF 108提供虚拟化资源。虚拟资源层包括虚拟计算110，虚拟存储118和虚拟网 络120。虚拟计算110和虚拟存储118可以以虚拟机、或其他虚拟容器的形式提供给VNF 108。例如，一个或一个以上的VNF 108可以部署在一个虚拟机(Virtual Machine)上。虚拟化层抽象网络硬件116从而形成虚拟网络120，虚拟网络120可以包括虚拟交换机(Virtual Switch)，所述虚拟交换机用来提供虚拟机和其他虚拟机之间的连接。此外，网络硬件116中的传输网络，可以采用集中式控制平面和一个单独的转发平面(如软件定义网络，SDN)虚拟化。
NFVO可以通过计算机设备的形式实现。计费系统包含在BSS中，可以通过计算机设备的形式实现。图2是依据本发明一实施例的计算机设备200的硬件结构示意图。如图2所示，计算机设备200包括处理器202、存储器204、通信接口206和总线208。其中，处理器202、存储器204和通信接口206通过总线208实现彼此之间的通信连接。
处理器202可以采用通用的中央处理器(Central Processing Unit，CPU)，微处理器，应用专用集成电路(Application Specific Integrated Circuit，ASIC)，或者一个或多个集成电路，用于执行相关程序，以实现本发明实施例所提供的技术方案。
存储器204可以是只读存储器(Read Only Memory，ROM)，静态存储设备，动态存储设备或者随机存取存储器(Random Access Memory，RAM)。存储器204可以存储操作系统2041和其他应用程序2042。在通过软件或者固件来实现本发明实施例提供的技术方案时，用于实现本发明实施例提供的技术方案的程序代码保存在存储器204中，并由处理器202来执行。
通信接口206使用例如但不限于收发器一类的收发装置，来实现与其他设备或通信网络之间的通信。
总线208可包括一通路，在各个部件(例如处理器202、存储器204、通信接口206)之间传送信息。
当计算机设备200是NFVO时，处理器202用于执行接收来自计费系统的配额；当触发事件发生时，获取来自虚拟网络功能管理器VNFM的计费信息和虚拟基础设施管理器VIM的计费信息，所述触发事件包括内部触发事件或外部触发事件，所述内部触发事件的发生由处理器202主动检测获得，所述外部触发事件的发生由处理器202根据所述VNFM或所述VIM的主动上报来获得，所述来自VNFM的计费信息包含所述配额的使用信息；向所述计费系统发送所述来自VNFM的计费信息和所述来自VIM的计费信息。
当计算机设备200是计费系统时，处理器202用于执行向NFVO发送配额；接收来自所述NFVO的计费信息，所述计费信息携带所述配额的使用信息，所述计费信息包括来自VNFM的计费信息和来自VIM的计费信息；根据所述接收到的计费信息进行计费。
NFV架构中的VNF实例一般不是由同一个供应商提供，计费信息的采集和统一存在难度。本实施例中，通过NFVO向计费系统上报来自VNFM的计费信息和来自VIM的计费信息，计费系统根据接收到的计费信息进行计费，实现了基于NFV架构的计费。图3是依据本发明一实施例的计费方法300的示范性流程图。在具体实现过程中，计费方法300可以由图1所示的NFVO 102、VNFM 104、VIM 106和包含在图1 所示的BSS 124中的计费系统来执行。
S301，NFVO向计费系统发送配额请求消息。
S302，计费系统接收来自NFVO的配额请求消息。
具体的，NFVO通过扩展NFVO与BSS的现有接口Os-Ma-nfvo来发送配额请求消息，或者，也可以通过定义新接口(例如按照Diameter协议的要求来定义新接口)来发送配额请求消息。
S303，计费系统向NFVO发送配额。
可选的，所述配额为NS粒度或VNF粒度。所述配额用于所述NFVO控制网络服务NS的使用或虚拟网络功能VNF实例的使用。
S304，NFVO接收来自计费系统的配额。
S305，当触发事件发生时，所述NFVO获取来自虚拟网络功能管理器VNFM的计费信息和虚拟基础设施管理器VIM的计费信息，所述触发事件包括内部触发事件或外部触发事件，所述来自VNFM的计费信息包含所述配额的使用信息。
具体的，所述来自VNFM的计费信息还包含VNF的相关参数，所述VNF的相关参数包含VNF实例的标识，VNF的提供商，VNF的异常信息等。
例如，VNFM上报的计费信息可以包括如下信息，如表1所示：
表1
Figure PCTCN2017090611-appb-000001
其中，一个网络服务NS由一个或多个VNF实例组成。VNF实例是现有技术中的概念，指VNF软件的运行时实例(run-time instantiation)，是完成其虚拟部署单元(virtualization deployment unit，VDU)的实例化及VDU之间的连接的结果，使用VNF描述(VNF Description，VNFD)126中捕获的VNF部署和操作信息，以及额外的运行时实例特定的信息和条件(instance-specific information and constraints)。
当配额是VNF粒度时，VNFM发送的计费信息中携带VNF实例对配额的使用信息。当配额是NS粒度时，VNFM发送的计费信息中携带VNF实例对配额的使用信息，NFVO根据VNF实例对配额的使用信息确定NS的配额使用信息。例如，配额为允许使用NS10小时，该NS包含3个VNF实例VNF1、VNF2、VNF3，计费系统下发配额后，VNF1、VNF2、VNF3启动时间不同，VNF1、VNF2、VNF3分别运行了8小时、5小时、1小时，则VNFM发送的计费信息中携带VNF1、VNF2、VNF3对配额的使用信息8小时、5小时、1小时，NFVO将最大时长8小时作为NS的配额使用信息。
当配额是VNF粒度时，NFVO为各VNF实例分别申请配额，例如，NS包含3个VNF 实例VNF1、VNF2、VNF3，如果VNF1的配额使用完了，不管VNF2、VNF3的配额是否使用完，NFVO都会为VNF1重新申请配额。当配额是NS粒度时，NFVO为所有VNF实例统一申请配额，例如，NS包含3个VNF实例VNF1、VNF2、VNF3，只要其中一个VNF实例的配额使用量达到下发的配额大小，则NFVO会重新为VNF1、VNF2、VNF3申请配额。
具体的，所述来自VIM的计费信息包含虚拟机(virtual machine，VM)的资源使用信息。
例如，VIM上报的计费信息可以包括如下信息，如表2所示：
表2
Figure PCTCN2017090611-appb-000002
其中，VM的资源使用信息可以为：例如，在2个小时内，CPU使用率30％，Memory使用率40％，storage占用量50G，Network bandwidth流量300G。
具体的，所述内部触发事件包括网络服务NS状态变化或VNF状态变化，所述NS状态变化包括NS实例更新(Network service instance update)、NS实例扩容(Network service instance scaling out)、NS实例缩容(Network service instance scaling in)、NS实例伸缩(Network service instance scaling up/down)、NS启动(Network service instantiation)、NS实例终止(Network service instance termination)中的至少一种，所述VNF状态变化包括VNF实例扩容(VNF scaling out)、VNF实例缩容(VNF scaling in)、VNF实例伸缩(VNF scaling up/down)、VNF启动(VNF instantiation)、VNF实例终止(VNF instance termination)、VNF所需资源的分配请求(NFVI resources allocation request for a VNF)、VNF所需资源的释放请求(NFVI resources release request for a VNF)中的至少一种。
具体的，所述外部触发事件包括VNFM上报的状态信息或VIM上报的状态信息，所述VNFM上报的状态信息包括VNF实例使用的虚拟机VM的数量变化、VNF异常事 件、预留的VNF实例状态变化中的至少一种，所述VIM上报的状态信息包括VNF所使用的资源所属的区域变化或VIM预留的资源状态变化。其中，预留的VNF实例状态变化包括VNF实例从激活状态变为等待状态，或从等待状态变为激活状态。VIM预留的资源状态变化包括预留的资源从激活状态变为等待状态，或从等待状态变为激活状态。VNF异常事件包括VNF重启、告警以及每秒呼叫次数CPS低于或超过预设阈值。
其中，内部触发事件的发生可以由NFVO主动检测获得，例如，NFVO可以定期请求NS的状态或VNF的状态。外部触发事件的发生可以由NFVO根据VNFM或VIM的主动上报来获得，例如，当VNF重启时，VNFM将这一事件上报给NFVO。
由内部触发事件和外部触发事件构成的事件上报机制使得NFVO能够更准确、全面的确定计费信息的获取和上报时机，增强了计费的准确性。
当触发事件发生时，NFVO获取来自VNFM和VIM的计费信息，例如，当NFVO检测到NS实例缩容时，其从VNFM和VIM获取计费信息，具体的，从VNFM获取的计费信息可以包括VNF的标识，以及VNF的开始运行时间，运行时长，从VIM获取的计费信息可以包括VM的标识，VM的开始使用时间，以及CPU，Memory，Storage，Network等资源的使用信息。或者，例如，当NFVO接收到VNFM上报的预留的VNF实例从等待状态变为激活状态的信息时，NFVO从VNFM和VIM获取计费信息。
S306，所述NFVO向所述计费系统发送所述来自VNFM的计费信息和所述来自VIM的计费信息。
S307，所述计费系统接收来自所述NFVO的计费信息，所述计费信息携带所述配额的使用信息，所述计费信息包括来自VNFM的计费信息和来自VIM的计费信息。
S308，所述计费系统根据所述接收到的计费信息进行计费。
具体的，NFVO通过上述步骤302中扩展的NFVO与BSS的现有接口Os-Ma-nfvo来发送计费信息，或者，通过上述步骤302中定义的新接口来发送计费信息。
可选的，在所述NFVO向所述计费系统发送所述来自VNFM的计费信息和所述来自VIM的计费信息之前，所述NFVO关联所述来自VNFM的计费信息和所述来自VIM的计费信息，则所述NFVO向所述计费系统发送所述来自VNFM的计费信息和所述来自VIM的计费信息为：所述NFVO向所述计费系统发送所述关联后的计费信息。
例如，关联后的计费信息可以包括如下信息，如表3所示
表3
Figure PCTCN2017090611-appb-000003
Figure PCTCN2017090611-appb-000004
由于关联计费信息后可以得到NS的计费信息，因此使得计费系统可以对使用NS进行计费。
可选的，所述NFVO根据VNF实例的标识与VM的标识的对应关系关联所述来自VNFM的计费信息和所述来自VIM的计费信息。VNF实例的标识与VM的标识的对应关系可以事先配置在NFVO中。
可选的，所述NFVO存储有NS的标识，以及该NS包含的VNF实例的标识(或NS的标识与VNF实例的标识的对应关系)。NFVO根据NS包含的VNF实例的标识以及来自VNFM的计费信息中VNF实例的标识，将来自VNFM的计费信息中的VNF实例关联到相应的NS下，可以得到NS的计费信息。将NS的计费信息发送给计费系统，计费系统根据该计费信息对使用NS进行计费。
例如，以上述NS实例缩容时向计费系统发送计费信息为例，NFVO关联来自VNFM的计费信息和来自VIM的计费信息，得到的NS的计费信息包括NS的标识，NS的开始使用时间，NS的使用时长，VNF list，VM list，其中VM list包含了CPU、Memory、Storage、Network的使用信息。
可选的，NFVO也可以不关联来自VNFM的计费信息和来自VIM的计费信息，而是将它们发送给计费系统。在所述计费系统接收所述来自VNFM的计费信息和所述来自VIM的计费信息后，所述计费系统关联所述来自VNFM的计费信息和所述来自VIM的计费信息，则所述计费系统根据所述接收到的计费信息进行计费为：所述计费系统根据所述关联后的计费信息进行计费。
由计费系统对接收到的计费信息进行关联，而不是由NFVO对计费信息进行关联，能够减轻NFVO的负担，降低其复杂度。
可选的，所述计费系统根据VNF实例的标识与VM的标识的对应关系关联所述来自VNFM的计费信息和所述来自VIM的计费信息。依据NS包含的VNF实例的标识，将所述来自VNFM的计费信息中的VNF实例关联到相应的NS下，可以得到NS的计费信息，计费系统根据该计费信息对使用NS进行计费。VNF实例的标识与VM的标识的对应关系(或VNF实例使用的VM的标识)可以事先配置在计费系统中，也可以由NFVO发送给计费系统。NS的标识以及该NS包含的VNF的实例的标识可以事先配置在计费系统中，也可以由NFVO发送给计费系统。
可选的，计费系统也可以根据来自VNFM的计费信息和来自VIM的计费信息对使用VNF进行计费。
具体的，来自VNFM的计费信息中还可以包含各VNF实例的开始运行时间，各VNF实例的使用时长，来自VIM的计费信息中还可以包含VM的开始使用时间，以及CPU，Memory，Storage，Network等资源的使用信息，计费系统可以依据这些信息对使用VNF进行计费。
根据本发明实施例提供的计费方法，通过NFVO向计费系统上报来自VNFM的计费信息和来自VIM的计费信息，计费系统根据接收到的计费信息进行计费，实现了基于NFV架构的计费。
图4是依据本发明一实施例的计费方法400的示范性流程图。在具体实现过程中，计费方法400可以由图1所示的NFVO 102、VNFM 104、VIM 106和包含在图1所示的BSS 124中的计费系统来执行。
S401，当第一触发事件发生时，NFVO向计费系统发送第一计费信息。
具体的，NFVO通过NFVO与BSS的现有接口Os-Ma-nfvo来发送第一计费信息，或者，也可以通过定义新的接口(例如按照Diameter协议的要求来定义新接口)来发送第一计费信息。
具体的，第一触发事件包括周期上报(可以通过设置定时器的方式来实现)或NS状态变化。NS状态变化包括NS实例更新、NS实例扩容、NS实例缩容、NS实例伸缩、NS启动、NS实例终止中的至少一种。
第一触发事件可以预先配置在NFVO中。当第一触发事件未发生时，NFVO将采集的第一计费信息进行存储，待第一触发事件发生时再向计费系统发送第一计费信息。
具体的，第一计费信息包含NS的标识，该NS包含的VNF实例的标识，该VNF实例使用的VM的标识，以及该NS的使用信息。NS的使用信息可以为NS的使用时长或NS的使用次数。
可选的，第一计费信息可以包含如下信息如下信息，如表4所示
表4
Figure PCTCN2017090611-appb-000005
S402，当第二触发事件发生时，VNFM向计费系统发送第二计费信息。
具体的，VNFM可以通过定义的与计费系统之间的新接口来发送第二计费信息。
具体的，第二触发事件包括周期上报或VNF状态变化。VNF状态变化包括VNF实例扩容、VNF实例缩容、VNF实例伸缩、VNF启动、VNF实例终止中的至少一种。第二触发事件可以预先配置在VNFM中。当第二触发事件未发生时，VNFM将采集的第二计费信息进行存储，待第二触发事件发生时再向计费系统发送第二计费信息。
具体的，第二计费信息包含VNF实例的标识，及该VNF实例的使用信息。VNF实例的使用信息包括VNF实例的使用时长或使用次数。
可选的，第二计费信息可以包含如下信息，如表5所示：
表5
Figure PCTCN2017090611-appb-000006
S403，当第三触发事件发生时，VIM向计费系统发送第三计费信息。
具体的，VIM可以通过定义的与计费系统之间的新接口来发送第三计费信息。
具体的，第三触发事件包括周期上报或VNF所需资源的状态变化。VNF所需资源的状态变化包括VNF所需资源的分配请求或VNF所需资源的释放请求。
第三触发事件可以预先配置在VIM中。当第三触发事件未发生时，VIM将采集的第三计费信息进行存储，待第三触发事件发生时再向计费系统发送第三计费信息。
具体的，第三计费信息包含VM的标识，以及该VM的使用信息。VM的使用信息包括VM使用的资源信息或VM的占用时间。
可选的，第三计费信息可以包含如下信息，如表6所示：
表6
Figure PCTCN2017090611-appb-000007
Figure PCTCN2017090611-appb-000008
S404，计费系统关联第一计费信息、第二计费信息、第三计费信息进行计费。
具体的，计费系统根据第一计费信息中VNF实例的标识以及第二计费信息中VNF实例的标识关联第一计费信息和第二计费信息；根据第一计费信息中VNF实例的标识和VM的标识的对应关系，以及第三计费信息中VM的标识关联第一计费信息和第三计费信息。由于第一计费信息中包含了NS包含的VNF实例的标识，因此在关联后可以得到NS的计费信息，计费系统对使用NS进行计费。由于第二计费信息中包含了VNF实例的使用信息，因此关联后还可以对使用VNF进行计费。
可选的，S402中，VNFM通过NFVO向计费系统发送第二计费信息。具体的，当第二触发事件发生时，VNFM向NFVO发送第二计费信息，当第一触发事件发生时，NFVO向计费系统发送该第二计费信息。具体的，VNFM通过NFVO与VNFM的现有接口Or-vnfm来发送第二计费信息，或者，也可以通过定义新的接口来发送第二计费信息。
可选的，S403中，VIM通过NFVO向计费系统发送第三计费信息。具体的，当第三触发事件发生时，VIM向NFVO发送第三计费信息，当第一触发事件发生时，NFVO向计费系统发送该第三计费信息。具体的，VIM通过NFVO与VIM的现有接口Or-Vi来发送第三计费信息，或者，也可以通过定义新的接口来发送第三计费信息。
上述采用“S401、S402、S403”先后顺序的描述方式是为了清楚的描述本发明实施例，并非用来限定NFVO、VNFM、VIM向计费系统发送计费信息的先后顺序，当各自的触发事件发生，则相应的向计费系统发送计费信息。
根据本发明实施例提供的计费方法，通过向计费系统发送第一计费信息、第二计费信息、第三计费信息，使得计费系统能够对接收到的计费信息进行关联和计费，实现了基于NFV架构的计费。
图5是依据本发明一实施例的计费方法500的示范性流程图。在具体实现过程中，计费方法500可以由图1所示的NFVO 102、VNFM 104、VIM 106和包含在图1所示的BSS 124中的计费系统来执行。与图4实施例不同，在图5实施例中，由NFVO对第二计费信息和第三计费信息进行关联。
S501，当第二触发事件发生时，VNFM向NFVO发送第二计费信息。
具体的，VNFM通过NFVO与VNFM的现有接口Or-vnfm来发送第二计费信息，或 者，也可以通过定义新的接口来发送第二计费信息。
具体的，第二触发事件及第二计费信息的相关内容可参考图4实施例S402中的相关内容。
S502，当第三触发事件发生时，VIM向NFVO发送第三计费信息。
具体的，VIM通过NFVO与VIM的现有接口Or-Vi来发送第三计费信息，或者，也可以通过定义新的接口来发送第三计费信息。
具体的，第三触发事件及第三计费信息的相关内容可参考图4实施例S403中的相关内容。
S503，NFVO关联第二计费信息和第三计费信息，得到关联后的计费信息。
具体的，NFVO中存储有NS标识，该NS包含的VNF实例的标识，VNF实例使用的VM的标识(或VNF实例的标识与VM的标识的对应关系)。
NFVO根据NS包含的VNF实例的标识以及第二计费信息中VNF实例的标识，将第二计费信息中VNF实例的使用信息关联到对应的NS下；根据VNF的标识和VM的标识的对应关系，以及第三计费信息中VM的标识将第三计费信息中VM的使用信息关联到对应的VNF下。关联后可以得到NS的计费信息。
S504，当第一触发事件发生时，NFVO向计费系统发送关联后的计费信息。
S505，计费系统对接收到的计费信息进行计费。
具体的，NFVO向计费系统发送NS的计费信息，计费系统对使用NS进行计费。由于NS的计费信息中包含了VNF实例的使用信息，因此计费系统可以对使用VNF进行计费。
上述采用“S501、S502”先后顺序的描述方式是为了清楚的描述本发明实施例，并非用来限定VNFM、VIM向NFVO发送计费信息的先后顺序，当各自的触发事件发生，则相应的向NFVO发送计费信息。
根据本发明实施例提供的计费方法，通过向计费系统发送关联后的第二计费信息、第三计费信息，使得计费系统能够对接收到的计费信息进行计费，实现了基于NFV架构的计费。
在本发明实施例的另一种实现方式中，图3实施例可以由包含在图1所示的NFVO 102中的计费触发功能逻辑实体、包含在图1所示的VNFM 104中的计费上报功能逻辑实体、包含在图1所示的VIM 106中的计费上报功能逻辑实体和包含在图1所示的BSS 124中的计费系统来执行。如图6所示。具体的，由NFVO 102中的计费触发功能逻辑实体执行图3实施例中的S301、S304、S305、S306。在S305中，由NFVO 102中的计费触发功能逻辑实体获取来自VNFM 104中的计费上报功能逻辑实体的计费信息和VIM 106中的计费上报功能逻辑实体的计费信息。
在本发明实施例的另一种实现方式中，图4实施例可以由包含在图1所示的NFVO 102中的第一计费触发功能逻辑实体、包含在图1所示的VNFM 104中的第二计费触发功能逻辑实体、包含在图1所示的VIM 106中的第三计费触发功能逻辑实体和包含在图1所示的BSS 124中的计费系统来执行。如图7所示。具体的，由第一计费触发功能逻辑实体执行图4实施例中的S401，由第二计费触发功能逻辑实体执行图4实施例中的S402，由第三计费触发功能逻辑实体执行图4实施例中的S403。
在本发明实施例的另一种实现方式中，图5实施例可以由包含在图1所示的 NFVO 102中的第一计费触发功能逻辑实体、包含在图1所示的VNFM 104中的第二计费触发功能逻辑实体、包含在图1所示的VIM 106中的第三计费触发功能逻辑实体和包含在图1所示的BSS 124中的计费系统来执行。如图7所示。具体的，由第二计费触发功能逻辑实体执行图5实施例中的S501，由第三计费触发功能逻辑实体执行图5实施例中的S502，由第一计费触发功能逻辑实体执行图5实施例中的S503、S504。
图8是依据本发明一实施例的计费装置800的结构示意图。计费装置800包括接收模块802，处理模块804和发送模块806。计费装置800为图2中的计算机设备200或图3中所示的NFVO。接收模块802可以用来执行图3实例中的S304，处理模块804可以用来执行图3实施例中的S305，发送模块806可以用来执行图3实施例中的S301、S306。
接收模块802，用于接收来自计费系统的配额。
处理模块804，用于当触发事件发生时，获取来自虚拟网络功能管理器VNFM的计费信息和虚拟基础设施管理器VIM的计费信息，所述触发事件包括内部触发事件或外部触发事件，所述内部触发事件的发生由处理模块804主动检测获得，所述外部触发事件的发生由处理模块804根据所述VNFM或所述VIM的主动上报来获得，所述来自VNFM的计费信息包含所述配额的使用信息。
发送模块806，用于向所述计费系统发送所述来自VNFM的计费信息和所述来自VIM的计费信息。
可选的，在发送模块806向所述计费系统发送所述来自VNFM的计费信息和所述来自VIM的计费信息之前，处理模块804还用于关联所述来自VNFM的计费信息和所述来自VIM的计费信息，则发送模块806向所述计费系统发送所述来自VNFM的计费信息和所述来自VIM的计费信息为：发送模块806向所述计费系统发送所述关联后的计费信息。
具体的，处理模块804根据VNF实例的标识与VM的标识的对应关系关联所述来自VNFM的计费信息和所述来自VIM的计费信息。
所述来自VNFM的计费信息还包含VNF实例的标识，处理模块804根据NS的标识与VNF实例的标识的对应关系以及所述VNF实例的标识，将所述来自VNFM的计费信息中的VNF实例关联到相应的NS下。
可选的，所述来自VIM的计费信息包含VM的资源使用信息。
有关内部触发事件和外部触发事件的具体内容可参见图3实施例中S305中的描述，此处不再赘述。
图7是依据本发明一实施例的计费装置900的结构示意图。计费装置900包括发送模块902，接收模块904和处理模块906。计费装置900为图2中的计算机设备200或图3中所示的计费系统。发送模块902可以用来执行图3实施例中的S303，接收模块904可以用来执行图3实施例中的S302、S307，处理模块906可以用来执行图3实施例中的S308。
发送模块902，用于向NFVO发送配额。
接收模块904，用于接收来自所述NFVO的计费信息，所述计费信息携带所述配额的使用信息，所述计费信息包括来自VNFM的计费信息和来自VIM的计费信息。
处理模块906，用于根据所述接收到的计费信息进行计费。
可选的，在接收模块904接收所述来自VNFM的计费信息和所述来自VIM的计费信息后，处理模块906还用于关联所述来自VNFM的计费信息和所述来自VIM的计费信息，则处理模块906根据所述接收到的计费信息进行计费为：
处理模块906根据所述关联后的计费信息进行计费。
具体的，处理模块906根据VNF实例的标识与VM的标识的对应关系关联所述来自VNFM的计费信息和所述来自VIM的计费信息。
所述来自VNFM的计费信息还包含VNF实例的标识，处理模块906根据NS的标识与VNF实例的标识的对应关系以及VNF实例的标识，将所述来自VNFM的计费信息中的VNF实例关联到相应的NS下。
根据本发明实施例提供的计费方法，通过向计费系统上报来自VNFM的计费信息和来自VIM的计费信息，计费系统根据接收到的计费信息进行计费，实现了基于NFV架构的计费。
其中，图8和图9实施例中的“模块”可以为专用集成电路(Application Specific Integrated Circuit，ASIC)、电子线路、执行一个或多个软件或固件程序的处理器和存储器、组合逻辑电路和其他提供上述功能的组件。可选的，上述计费装置通过计算机设备的形式来实现，上述接收模块、发送模块可以通过计算机设备的处理器、存储器和通信接口来实现，上述处理模块可以通过计算机设备的处理器和存储器来实现。
应注意，尽管图2所示的计算机设备200仅仅示出了处理器202、存储器204、通信接口206和总线208，但是在具体实现过程中，本领域的技术人员应当明白，上述计费装置还包含实现正常运行所必须的其他器件。同时，根据具体需要，本领域的技术人员应当明白，上述计费装置还可包含实现其他附加功能的硬件器件。此外，本领域的技术人员应当明白，上述计费装置也可仅仅包含实现本发明实施例所必须的器件，而不必包含图2中所示的全部器件。
另外，在本发明各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。
所述集成的单元如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本发明的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的全部或部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)或处理器(processor)执行本发明各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(ROM，Read-Only Memory)、随机存取存储器(RAM，Random Access Memory)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本发明的具体实施方式，但本发明的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本发明揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本发明的保护范围之内。因此，本发明的保护范围应以所述权利要求的保护范围为准。

Claims (25)

  1. 一种计费方法，所述方法应用于基于网络功能虚拟化NFV架构下的计费，其特征在于，包括以下步骤：
    网络功能虚拟化编排器NFVO接收来自计费系统的配额；
    当触发事件发生时，所述NFVO获取来自虚拟网络功能管理器VNFM的计费信息和虚拟基础设施管理器VIM的计费信息，所述触发事件包括内部触发事件或外部触发事件，所述内部触发事件的发生由所述NFVO主动检测获得，所述外部触发事件的发生由所述NFVO根据所述VNFM或所述VIM的主动上报来获得，所述来自VNFM的计费信息包含所述配额的使用信息；
    所述NFVO向所述计费系统发送所述来自VNFM的计费信息和所述来自VIM的计费信息。
  2. 如权利要求1所述的方法，其特征在于，在所述NFVO向所述计费系统发送所述来自VNFM的计费信息和所述来自VIM的计费信息之前，所述NFVO关联所述来自VNFM的计费信息和所述来自VIM的计费信息，则所述NFVO向所述计费系统发送所述来自VNFM的计费信息和所述来自VIM的计费信息为：所述NFVO向所述计费系统发送所述关联后的计费信息。
  3. 如权利要求2所述的方法，其特征在于，所述NFVO根据虚拟网络功能VNF实例的标识与虚拟机VM的标识的对应关系关联所述来自VNFM的计费信息和所述来自VIM的计费信息。
  4. 如权利要求2或3所述的方法，其特征在于，所述来自VNFM的计费信息还包含VNF实例的标识，所述NFVO根据网络服务NS的标识与VNF实例的标识的对应关系以及所述VNF实例的标识，将所述来自VNFM的计费信息中的VNF实例关联到相应的NS下。
  5. 如权利要求1至4任意一项所述的方法，其特征在于，所述内部触发事件包括NS状态变化或VNF状态变化，所述NS状态变化包括NS实例更新、NS实例扩容、NS实例缩容、NS实例伸缩、NS启动、NS实例终止中的至少一种，所述VNF状态变化包括VNF实例扩容、VNF实例缩容、VNF实例伸缩、VNF启动、VNF实例终止、VNF所需资源的分配请求、VNF所需资源的释放请求中的至少一种。
  6. 如权利要求1至5任意一项所述的方法，其特征在于，所述外部触发事件包括VNFM上报的状态信息或VIM上报的状态信息，所述VNFM上报的状态信息包括VNF实例使用的VM的数量变化、VNF异常事件、预留的VNF实例状态变化中的至少一种，所述VIM上报的状态信息包括VNF所使用的资源所属的区域发生变化或VIM预留的资源状态发生变化。
  7. 如权利要求1至6中任意一项所述的方法，其特征在于，所述来自VIM的计费信息包含VM的资源使用信息。
  8. 一种计费方法，所述方法应用于基于网络功能虚拟化NFV架构下的计费，其特征在于，包括以下步骤：
    计费系统向网络功能虚拟化编排器NFVO发送配额；
    所述计费系统接收来自所述NFVO的计费信息，所述计费信息携带所述配额的使用信息，所述计费信息包括来自虚拟网络功能管理器VNFM的计费信息和来自虚 拟基础设施管理器VIM的计费信息；
    所述计费系统根据所述接收到的计费信息进行计费。
  9. 如权利要求8所述的方法，其特征在于，在所述计费系统接收所述来自VNFM的计费信息和所述来自VIM的计费信息后，所述计费系统关联所述来自VNFM的计费信息和所述来自VIM的计费信息，则所述计费系统根据所述接收到的计费信息进行计费为：
    所述计费系统根据所述关联后的计费信息进行计费。
  10. 如权利要求9所述的方法，其特征在于，所述计费系统根据VNF实例的标识与VM的标识的对应关系关联所述来自VNFM的计费信息和所述来自VIM的计费信息。
  11. 如权利要求9或10所述的方法，其特征在于，所述来自VNFM的计费信息还包含VNF实例的标识，所述计费系统根据NS的标识与VNF实例的标识的对应关系以及所述VNF实例的标识，将所述来自VNFM的计费信息中的VNF实例关联到相应的NS下。
  12. 一种计费装置，所述装置应用于基于网络功能虚拟化NFV架构下的计费，其特征在于，包括接收模块，处理模块和发送模块：
    所述接收模块，用于接收来自计费系统的配额；
    所述处理模块，用于当触发事件发生时，获取来自虚拟网络功能管理器VNFM的计费信息和虚拟基础设施管理器VIM的计费信息，所述触发事件包括内部触发事件或外部触发事件，所述内部触发事件的发生由所述处理模块主动检测获得，所述外部触发事件的发生由所述处理模块根据所述VNFM或所述VIM的主动上报来获得，所述来自VNFM的计费信息包含所述配额的使用信息；
    所述发送模块，用于向所述计费系统发送所述来自VNFM的计费信息和所述来自VIM的计费信息。
  13. 如权利要求12所述的装置，其特征在于，在所述发送模块向所述计费系统发送所述来自VNFM的计费信息和所述来自VIM的计费信息之前，所述处理模块还用于关联所述来自VNFM的计费信息和所述来自VIM的计费信息，则所述发送模块向所述计费系统发送所述来自VNFM的计费信息和所述来自VIM的计费信息为：所述发送模块向所述计费系统发送所述关联后的计费信息。
  14. 如权利要求13所述的装置，其特征在于，所述处理模块根据虚拟网络功能VNF实例的标识与虚拟机VM的标识的对应关系关联所述来自VNFM的计费信息和所述来自VIM的计费信息。
  15. 如权利要求13或14所述的装置，其特征在于，所述来自VNFM的计费信息还包含VNF实例的标识，所述处理模块根据网络服务NS的标识与VNF实例的标识的对应关系以及所述VNF实例的标识，将所述来自VNFM的计费信息中的VNF实例关联到相应的NS下。
  16. 如权利要求12至15任意一项所述的装置，其特征在于，所述内部触发事件包括NS状态变化或VNF状态变化，所述NS状态变化包括NS实例更新、NS实例扩容、NS实例缩容、NS实例伸缩、NS启动、NS实例终止中的至少一种，所述VNF状态变化包括VNF实例扩容、VNF实例缩容、VNF实例伸缩、VNF启动、VNF实例终 止、VNF所需资源的分配请求、VNF所需资源的释放请求中的至少一种。
  17. 如权利要求12至16任意一项所述的装置，其特征在于，所述外部触发事件包括VNFM上报的状态信息或VIM上报的状态信息，所述VNFM上报的状态信息包括VNF实例使用的VM的数量变化、VNF异常事件、预留的VNF实例状态变化中的至少一种，所述VIM上报的状态信息包括VNF所使用的资源所属的区域发生变化或VIM预留的资源状态发生变化。
  18. 如权利要求12至17中任意一项所述的装置，其特征在于，所述来自VIM的计费信息包含VM的资源使用信息。
  19. 一种计费装置，所述装置应用于基于网络功能虚拟化NFV架构下的计费，其特征在于，包括发送模块，接收模块和处理模块：
    所述发送模块，用于向网络功能虚拟化编排器NFVO发送配额；
    所述接收模块，用于接收来自所述NFVO的计费信息，所述计费信息携带所述配额的使用信息，所述计费信息包括来自虚拟网络功能管理器VNFM的计费信息和来自虚拟基础设施管理器VIM的计费信息；
    所述处理模块，用于根据所述接收到的计费信息进行计费。
  20. 如权利要求19所述的装置，其特征在于，在所述接收模块接收所述来自VNFM的计费信息和所述来自VIM的计费信息后，所述处理模块还用于关联所述来自VNFM的计费信息和所述来自VIM的计费信息，则所述处理模块根据所述接收到的计费信息进行计费为：
    所述处理模块根据所述关联后的计费信息进行计费。
  21. 如权利要求20所述的装置，其特征在于，所述处理模块根据虚拟网络功能VNF实例的标识与虚拟机VM的标识的对应关系关联所述来自VNFM的计费信息和所述来自VIM的计费信息。
  22. 如权利要求20或21所述的装置，其特征在于，所述来自VNFM的计费信息还包含VNF实例的标识，所述处理模块根据NS的标识与VNF实例的标识的对应关系以及VNF实例的标识，将所述来自VNFM的计费信息中的VNF实例关联到相应的NS下。
  23. 一种计算设备，所述设备应用于基于网络功能虚拟化NFV架构下的计费，包括：处理器、存储器、总线和通信接口；所述存储器用于存储计算设备执行指令，所述处理器与所述存储器通过所述总线连接，当所述计算设备运行时，所述处理器执行所述存储器存储的所述计算设备执行指令，以使所述计算设备执行权利要求1至7所述的方法。
  24. 一种计算设备，所述设备应用于基于网络功能虚拟化NFV架构下的计费，包括：处理器、存储器、总线和通信接口；所述存储器用于存储计算设备执行指令，所述处理器与所述存储器通过所述总线连接，当所述计算设备运行时，所述处理器执行所述存储器存储的所述计算设备执行指令，以使所述计算设备执行权利要求8至11所述的方法。
  25. 一种系统，所述系统应用于基于网络功能虚拟化NFV架构下的计费，其特征在于，包括网络功能虚拟化编排器NFVO和计费系统：
    所述NFVO，用于接收来自计费系统的配额；当触发事件发生时，获取来自虚拟 网络功能管理器VNFM的计费信息和虚拟基础设施管理器VIM的计费信息，所述触发事件包括内部触发事件或外部触发事件，所述内部触发事件的发生由所述NFVO主动检测获得，所述外部触发事件的发生由所述NFVO根据所述VNFM或所述VIM的主动上报来获得，所述来自VNFM的计费信息包含所述配额的使用信息；向所述计费系统发送所述来自VNFM的计费信息和所述来自VIM的计费信息；
    所述计费系统，用于向所述NFVO发送配额；接收来自所述NFVO的计费信息；根据所述接收到的计费信息进行计费。
PCT/CN2017/090611 2016-08-15 2017-06-28 一种计费方法、装置及系统 WO2018032884A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP17840860.5A EP3471337B1 (en) 2016-08-15 2017-06-28 Charging methods and devices
US16/271,868 US20190173681A1 (en) 2016-08-15 2019-02-10 Charging method and apparatus and system

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201610671813.2 2016-08-15
CN201610671813.2A CN107769932B (zh) 2016-08-15 2016-08-15 一种计费方法、装置及系统

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/271,868 Continuation US20190173681A1 (en) 2016-08-15 2019-02-10 Charging method and apparatus and system

Publications (1)

Publication Number Publication Date
WO2018032884A1 true WO2018032884A1 (zh) 2018-02-22

Family

ID=61196318

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/090611 WO2018032884A1 (zh) 2016-08-15 2017-06-28 一种计费方法、装置及系统

Country Status (4)

Country Link
US (1) US20190173681A1 (zh)
EP (1) EP3471337B1 (zh)
CN (1) CN107769932B (zh)
WO (1) WO2018032884A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020259116A1 (zh) * 2019-06-26 2020-12-30 中兴通讯股份有限公司 一种计费系统、方法、存储介质及电子装置

Families Citing this family (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3769547B1 (en) * 2018-03-20 2022-11-02 Nokia Solutions and Networks Oy Quota management in mobile edge computing (mec)
CN111385754B (zh) * 2018-12-29 2022-05-31 华为技术有限公司 计费的方法、装置及系统
CN109756372B (zh) * 2018-12-29 2022-03-04 亚信科技（中国）有限公司 一种电信计费系统的弹性伸缩方法及装置
TWI692987B (zh) * 2019-10-04 2020-05-01 中華電信股份有限公司 適用於sdn或nfv網路之計費方法
CN111242597B (zh) * 2020-01-03 2023-09-08 湖北省楚天云有限公司 一种政务云平台基于项目计费的方法和系统
EP3952208A1 (en) * 2020-08-04 2022-02-09 Deutsche Telekom AG Method for providing improved charging capabilities regarding at least one mobile communication network whose functionality is at least partly provided by means of a cloud infrastructure, mobile communication network, cloud infrastructure, procedure charging system, program and computer-readable medium

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104734931A (zh) * 2015-03-31 2015-06-24 华为技术有限公司 一种虚拟网络功能间链路建立方法及装置
CN105284094A (zh) * 2014-05-15 2016-01-27 华为技术有限公司 一种网络功能虚拟化网络系统、数据处理方法及装置
WO2016028927A1 (en) * 2014-08-19 2016-02-25 Huawei Technologies Co., Ltd. Methods and system for allocating an ip address for an instance in a network function virtualization (nfv) system

Family Cites Families (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104349298B (zh) * 2013-08-09 2019-07-02 中兴通讯股份有限公司 一种网络计费方法、控制器、数据中心及系统
CN104170323B (zh) * 2014-04-09 2018-02-02 华为技术有限公司 基于网络功能虚拟化的故障处理方法及装置、系统
CN104050045B (zh) * 2014-06-27 2017-06-27 华为技术有限公司 基于磁盘io的虚拟资源分配方法及装置
CN107533484B (zh) * 2015-05-07 2021-03-02 华为技术有限公司 用于动态管理虚拟网络功能描述符的系统和方法
EP3332332A4 (en) * 2015-08-25 2018-08-08 Huawei Technologies Co., Ltd. System and method for network function virtualization resource management
US11005773B2 (en) * 2015-12-10 2021-05-11 Microsoft Technology Licensing, Llc Data driven automated provisioning of telecommunication applications
EP3452906B1 (en) * 2016-05-02 2023-01-04 Telefonaktiebolaget LM Ericsson (publ) Techniques for virtualized network capacity management
WO2018033878A1 (en) * 2016-08-18 2018-02-22 Telefonaktiebolaget Lm Ericsson (Publ) A network service design and deployment process for nfv systems

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105284094A (zh) * 2014-05-15 2016-01-27 华为技术有限公司 一种网络功能虚拟化网络系统、数据处理方法及装置
WO2016028927A1 (en) * 2014-08-19 2016-02-25 Huawei Technologies Co., Ltd. Methods and system for allocating an ip address for an instance in a network function virtualization (nfv) system
CN104734931A (zh) * 2015-03-31 2015-06-24 华为技术有限公司 一种虚拟网络功能间链路建立方法及装置

Non-Patent Citations (1)

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

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020259116A1 (zh) * 2019-06-26 2020-12-30 中兴通讯股份有限公司 一种计费系统、方法、存储介质及电子装置

Also Published As

Publication number Publication date
CN107769932A (zh) 2018-03-06
EP3471337A1 (en) 2019-04-17
EP3471337B1 (en) 2021-09-22
EP3471337A4 (en) 2019-07-10
US20190173681A1 (en) 2019-06-06
CN107769932B (zh) 2021-02-09

Similar Documents

Publication Publication Date Title
WO2018032884A1 (zh) 一种计费方法、装置及系统
US10908936B2 (en) System and method for network function virtualization resource management
EP3461087A1 (en) Network-slice resource management method and apparatus
EP3471342A1 (en) Method and device for service deployment in virtualized network
US8032780B2 (en) Virtualization based high availability cluster system and method for managing failure in virtualization based high availability cluster system
US11093296B2 (en) System, virtualization control apparatus, method for controlling a virtualization control apparatus, and program
US20160328258A1 (en) Management system, overall management node, and management method
CN109428764B (zh) 虚拟网络功能的实例化方法
EP2838243B1 (en) Capability aggregation and exposure method and system
EP3211531B1 (en) Virtual machine start method and apparatus
US11871280B2 (en) VNF instantiation method, NFVO, VIM, VNFM, and system
CN109995552B (zh) Vnf服务实例化方法及装置
CN107155403A (zh) 一种生命周期事件的处理方法及vnfm
JP6369730B2 (ja) 仮想マシン始動方法及び装置
CN113098705B (zh) 网络业务的生命周期管理的授权方法及装置
EP4319084A1 (en) Method and apparatus for deploying container service
CN117632531A (zh) 集群中消息的处理方法、装置及存储介质

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

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2017840860

Country of ref document: EP

Effective date: 20190108

NENP Non-entry into the national phase

Ref country code: DE