# US 2019/0173681 A1 · Charging method and apparatus and system

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2019/0173681 A1
- Document ID: US20190173681A1
- Status: Published application
- Kind: A1
- Application number: 16/271,868
- Filed: 2019-02-10
- Published: 2019-06-06
- Earliest claimed: 2016-08-15
- Assignees: Huawei Technologies Co., Ltd.
- Applicants: Huawei Technologies Co., Ltd.
- Inventors: Jiangtao JIA; Xiaoqian CHAI; Ruinan SUN
- Web page: https://patentgrep.com/patent/US20190173681A1

## CPC

- H04L 12/1407: {Policy-and-charging control [PCC] architecture}
- H04M 15/58: {based on statistics of usage or network monitoring}
- H04M 15/62: {based on trigger specification}
- H04M 15/64: {On-line charging system [OCS]}
- H04M 15/66: {Policy and charging system}
- H04M 15/785: {Reserving amount on the account}
- H04M 15/8278: {Event based}
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- H04M: TELEPHONIC COMMUNICATION (circuits for controlling other apparatus via a telephone cable and not involving telephone switching apparatus G08)

## Abstract

Embodiments of the present invention provide a charging method, including: receiving, by a network function virtualization orchestrator NFVO, a quota from a charging system; when a trigger event occurs, obtaining, by the NFVO, charging information from a virtual network function manager VNFM and charging information from a virtualized infrastructure manager VIM, where the trigger event includes an internal trigger event or an external trigger event, and the charging information from the VNFM includes usage information of the quota; and sending, by the NFVO, the charging information from the VNFM and the charging information from the VIM to the charging system. NFV architecture-based charging is implemented.

## Claims

### Claim 1

A charging method, wherein the method is applied to network function virtualization (NFV) architecture-based charging, and comprises the following steps:
receiving, by a network function virtualization orchestrator (NFVO), a quota from a charging system;
when a trigger event occurs, obtaining, by the NFVO, charging information from a virtual network function manager (VNFM) and charging information from a virtualized infrastructure manager (VIM), wherein the trigger event comprises an internal trigger event or an external trigger event, occurrence of the internal trigger event being actively detected by the NFVO, occurrence of the external trigger event being reported by the VNFM or the VIM to the NFVO, and the charging information from the VNFM comprises usage information of the quota; and
sending, by the NFVO, the charging information from the VNFM and the charging information from the VIM to the charging system.

### Claim 2 (depends on 1)

The method according to claim 1, wherein before sending, by the NFVO, the charging information from the VNFM and the charging information from the VIM to the charging system, the NFVO associates the charging information from the VNFM and the charging information from the VIM, and sending, by the NFVO, the charging information from the VNFM and the charging information from the VIM to the charging system comprises: sending, by the NFVO, the associated charging information to the charging system.

### Claim 3 (depends on 2)

The method according to claim 2, wherein the NFVO associates the charging information from the VNFM and the charging information from the VIM based on a correspondence between a virtual network function VNF instance identifier and a virtual machine VM identifier.

### Claim 4 (depends on 2)

The method according to claim 2, wherein the charging information from the VNFM further comprises a VNF instance identifier, and the NFVO associates a VNF instance in the charging information from the VNFM with a corresponding NS based on the VNF instance identifier and a correspondence between a network service NS identifier and a VNF instance identifier.

### Claim 5 (depends on 1)

The method according to claim 1, wherein the internal trigger event comprises at least one of an NS state change or a VNF state change, the NS state change comprises at least one of NS instance update, NS instance scaling out, NS instance scaling in, NS instance scaling up/down, NS instantiation, or NS instance termination, and the VNF state change comprises at least one of VNF scaling out, VNF scaling in, VNF scaling up/down, VNF instantiation, VNF instance termination, a required-resource allocation request for a VNF, or a required-resource release request for a VNF.

### Claim 6 (depends on 1)

The method according to claim 1, wherein the external trigger event comprises at least one of status information reported by the VNFM or status information reported by the VIM, the status information reported by the VNFM comprises at least one of a change in a quantity of VMs used in a VNF instance, a VNF abnormality event, or a state change of a reserved VNF instance, and the status information reported by the VIM comprises a change in an area to which a resource used in the VNF belongs or a change in a state of a resource reserved by the VIM.

### Claim 7 (depends on 1)

The method according to claim 1, wherein the charging information from the VIM comprises resource usage information of the VM.

### Claim 8

A charging method, wherein the method is applied to network function virtualization (NFV) architecture-based charging, and the method comprises:
sending, by a charging system, a quota to a network function virtualization orchestrator (NFVO);
receiving, by the charging system, charging information from the NFVO, wherein the charging information carries usage information of the quota, and the charging information comprises charging information from a virtual network function manager (VNFM) and charging information from a virtualized infrastructure manager (VIM); and
performing, by the charging system, charging based on the received charging information.

### Claim 9 (depends on 8)

The method according to claim 8, wherein 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 and the charging information from the VIM, and the performing, by the charging system, charging based on the received charging information is:
performing, by the charging system, charging based on the associated charging information.

### Claim 10 (depends on 9)

The method according to claim 9, wherein the charging system associates the charging information from the VNFM and the charging information from the VIM based on a correspondence between a VNF instance identifier and a VM identifier.

### Claim 11 (depends on 9)

The method according to claim 9, wherein the charging information from the VNFM further comprises a VNF instance identifier, and the charging system associates a VNF instance in the charging information from the VNFM with a corresponding NS based on the VNF instance identifier and a correspondence between an NS identifier and a VNF instance identifier.

### Claim 12

A charging apparatus, the apparatus being applied to network function virtualization (NFV) architecture-based charging, and comprising
a computer-readable storage medium configured to store programming instructions; and
a processor coupled to the computer-readable storage medium, the programming instructions causing the processor to be configured to:
receive a quota from a charging system;
when a trigger event occurs, obtain charging information from a virtual network function manager (VNFM) and charging information from a virtualized infrastructure manager (VIM), wherein the trigger event comprises an internal trigger event or an external trigger event, occurrence of the internal trigger event being detected by the processing module, occurrence of the external trigger event being actively reported by the VNFM or the VIM to the processing module, and the charging information from the VNFM comprising usage information of the quota; and
send the charging information from the VNFM and the charging information from the VIM to the charging system.

### Claim 13 (depends on 12)

The apparatus according to claim 12, wherein the programming instructions further cause the processor to be configured to associate the charging information from the VNFM and the charging information from the VIM, and send the associated charging information to the charging system.

### Claim 14 (depends on 13)

The apparatus according to claim 13, wherein the programming instructions further cause the processor to be configured to associate the charging information from the VNFM and the charging information from the VIM based on a correspondence between a virtual network function VNF instance identifier and a virtual machine VM identifier.

### Claim 15 (depends on 13)

The apparatus according to claim 13, wherein the charging information from the VNFM further comprises a VNF instance identifier, and the processing module associates a VNF instance in the charging information from the VNFM with a corresponding NS based on the VNF instance identifier and a correspondence between a network service NS identifier and a VNF instance identifier.

### Claim 16 (depends on 12)

The apparatus according to claim 12, wherein the charging information from the VIM comprises resource usage information of the VM.

### Claim 17

A charging apparatus, the apparatus being applied to network function virtualization (NFV) architecture-based charging, and comprising:
a computer-readable storage medium configured to store programming instructions; and
a processor coupled to the computer-readable storage medium, the programming instructions causing the processor to be configured to:
send a quota to a network function virtualization orchestrator (NFVO);
receive charging information from the NFVO, wherein the charging information carries usage information of the quota, and the charging information comprises charging information from a virtual network function manager (VNFM) and charging information from a virtualized infrastructure manager (VIM); and
perform charging based on the received charging information.

### Claim 18 (depends on 17)

The apparatus according to claim 17, wherein the programming instructions further cause the processor to be configured to associate the charging information from the VNFM and the charging information from the VIM, and perform charging based on the associated charging information.

### Claim 19 (depends on 18)

The apparatus according to claim 18, wherein the processing module associates the charging information from the VNFM and the charging information from the VIM based on a correspondence between a virtual network function VNF instance identifier and a virtual machine VM identifier.

### Claim 20 (depends on 18)

The apparatus according to claim 18, wherein the charging information from the VNFM further comprises a VNF instance identifier, and the processing module associates a VNF instance in the charging information from the VNFM with a corresponding NS based on the VNF instance identifier and a correspondence between an NS identifier and a VNF instance identifier.
