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

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

Info

Publication number
WO2017133342A1
WO2017133342A1 PCT/CN2016/111517 CN2016111517W WO2017133342A1 WO 2017133342 A1 WO2017133342 A1 WO 2017133342A1 CN 2016111517 W CN2016111517 W CN 2016111517W WO 2017133342 A1 WO2017133342 A1 WO 2017133342A1
Authority
WO
WIPO (PCT)
Prior art keywords
charging
plane gateway
user plane
trigger event
service usage
Prior art date
Application number
PCT/CN2016/111517
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 EP16889148.9A priority Critical patent/EP3402231B1/en
Publication of WO2017133342A1 publication Critical patent/WO2017133342A1/zh
Priority to US16/054,615 priority patent/US10924900B2/en

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
    • G06Q40/12—Accounting
    • 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
    • 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/141—Indication of costs
    • 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/1425—Charging, metering or billing arrangements for data wireline or wireless communications involving dedicated fields in the data packet for billing purposes
    • 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/1442—Charging, metering or billing arrangements for data wireline or wireless communications at network operator level
    • 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/1453—Methods or systems for payment or settlement of the charges for data transmission involving significant interaction with the data transmission network
    • H04L12/1482—Methods or systems for payment or settlement of the charges for data transmission involving significant interaction with the data transmission network involving use of telephony infrastructure for billing for the transport of data, e.g. call detail record [CDR] or intelligent network infrastructure
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
    • H04L41/5032—Generating service level reports
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/06—Generation of reports
    • H04L43/062—Generation of reports related to network traffic
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/06—Generation of reports
    • H04L43/065—Generation of reports related to network devices
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/535—Tracking the activity of the user
    • 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
    • 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/55—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP for hybrid networks
    • 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/60—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP based on actual use of network resources
    • 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/61—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP based on the service used
    • 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/65—Off-line 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/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/67—Transmitting arrangements for sending billing related information
    • 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/81—Dynamic pricing, e.g. change of tariff during call
    • 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/8214—Data or packet based
    • 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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/24—Accounting or billing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/50—Service provisioning or reconfiguring
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
    • H04W60/04—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration using triggered events
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/18—Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data
    • H04W8/183—Processing at user equipment or user record carrier
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/18—Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data
    • H04W8/20—Transfer of user or subscriber data
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M2215/00—Metering arrangements; Time controlling arrangements; Time indicating arrangements
    • H04M2215/20—Technology dependant metering
    • H04M2215/2046—Hybrid network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M2215/00—Metering arrangements; Time controlling arrangements; Time indicating arrangements
    • H04M2215/22—Bandwidth or usage-sensitve billing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/16—Gateway arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W92/00—Interfaces specially adapted for wireless communication networks
    • H04W92/02—Inter-networking arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W92/00—Interfaces specially adapted for wireless communication networks
    • H04W92/04—Interfaces between hierarchically different network devices
    • H04W92/06—Interfaces between hierarchically different network devices between gateways and public network devices

Definitions

  • the present invention relates to the field of communications, and in particular, to a charging method, apparatus, and system.
  • EPC Evolved Packet Core
  • the data packets sent/received by the terminal need to be processed and split by the PGW (Public Data Network Gateway).
  • PGW Public Data Network Gateway
  • the location of the PGW is too high. This causes each packet to be transmitted over the network for a long distance to be forwarded.
  • 3GPP proposes the concept of CU (control and user) separation, that is, splitting the PGW into a user plane and a control plane for separation and deployment.
  • the control plane includes control protocols and support functions for the user plane, such as controlling the E-UTRA (Evolved Universal Terrestrial Radio Access) network access connection, controlling the routing path of the established network connection to support user movement, and controlling network resources. Allocate to meet user needs.
  • E-UTRA Evolved Universal Terrestrial Radio Access
  • the user plane transmits the data stream.
  • the user plane gateway (PGW-U) can be deployed in a distributed manner, and can be moved down to a lower position than a conventional PGW, such as a residential access network (RAN). Among them, the downward shift is from the perspective of network control, pointing to the user side.
  • Some local services (server local) end-to-end (E2E) data plane transmission can be done locally, saving a lot of transmission delay.
  • the Control Plane Gateway (PGW-C) still retains centralized deployment.
  • Embodiments of the present invention provide a charging method and apparatus, which can implement offline charging under PGW CU separation.
  • the first aspect provides a system, including a control plane gateway and a user plane gateway, where the control plane gateway sends a first charging trigger event to the user plane gateway, where the first charging trigger event is used to trigger the user plane gateway to generate a service.
  • the control plane gateway uses the information, when the user plane detects that the first charging trigger event occurs, the service usage information is generated, and the service usage information is sent to the control plane gateway.
  • the control plane gateway generates a charging request according to the service usage information, and sends a charging request to the charging system.
  • the first accounting triggering event is monitored by the control plane gateway or the user plane gateway, and the traffic used by the user is charged after the first charging triggering event occurs, and the charging under the CU separation architecture is implemented.
  • the second aspect provides a charging method, including: the control plane gateway sends a first charging triggering event to the user plane gateway, where the first charging triggering event is used to trigger the user plane gateway to generate service usage information.
  • the control plane gateway receives the service usage information from the user plane gateway, and generates a charging request according to the service usage information.
  • the control plane gateway sends a charging request to the charging system.
  • control plane gateway further receives the first charging trigger event from the user plane gateway, and the control plane gateway further generates the event according to the first charging trigger. Generate a billing request.
  • the service usage information can be associated with the first charging trigger event, and the accuracy of the charging is ensured when multiple first charging trigger events occur.
  • the control plane gateway before the control plane gateway sends the first charging trigger event to the user plane gateway, the control plane gateway is from at least one The first charging trigger event is distinguished from the charging trigger event.
  • a third aspect provides a charging method, including: receiving, by a user plane gateway, a first charging trigger event from a control plane gateway, where the first charging triggering event is used to trigger a user plane gateway to generate service usage information.
  • the user plane gateway detects that the first charging trigger event occurs, the user plane gateway generates service usage information.
  • the user plane gateway sends service usage information to the control plane gateway.
  • the user plane gateway when the first charging trigger event does not cause the charging session to end or the bill to be closed, the user plane gateway sends the gateway to the control plane. Before the service usage information, the user plane gateway stores the first charging trigger event and the generated service usage information. The user plane gateway re-accumulates the subsequent service usage information.
  • the user plane gateway sends the service usage information to the control plane gateway, which can reduce the amount of information interaction between the control plane gateway and the user plane gateway. Frequency, saving network resources.
  • the user plane gateway receives at least one charging trigger event from the control plane gateway, where the at least one charging trigger The event contains the first billing trigger event.
  • the user plane gateway distinguishes the first charging trigger event from at least one charging trigger event.
  • the user plane gateway also sends a first charging trigger event to the control plane gateway.
  • the service usage information is carried by the billing container.
  • a charging apparatus including a processor, a memory, a communication interface, and a bus, and the processor is connected to the memory and the communication interface through a bus.
  • the memory is for storing instructions for the processor to execute
  • the communication interface is for communicating with the user plane gateway under the control of the processor.
  • a charging apparatus including a processor, a memory, a communication interface, and a bus, and the processor is connected to the memory and the communication interface through a bus.
  • the memory is for storing instructions for the processor to execute
  • the communication interface is for communicating with the control plane gateway under the control of the processor.
  • a computer readable storage medium wherein executable program code is stored, the program code for implementing the method of the second aspect.
  • a computer readable storage medium wherein executable program code is stored, the program code for implementing the method of the third aspect.
  • a charging apparatus comprising means for performing the method of the second aspect.
  • a charging apparatus comprising means for performing the method of the third aspect.
  • a tenth aspect provides a system, including a control plane gateway and a user plane gateway, where the control plane gateway sends a first charging trigger event to the user plane gateway, and the first charging trigger event is used to trigger the user plane gateway generation meter. Fee request. After detecting the occurrence of the first charging trigger event, the user plane gateway generates an accounting request and sends the charging request to the control plane gateway. The control plane gateway sends the charging request to the charging system.
  • the first accounting triggering event is monitored by the control plane gateway or the user plane gateway, and the traffic used by the user is charged after the first charging triggering event occurs, and the charging under the CU separation architecture is implemented.
  • the eleventh aspect provides a charging method, including: the control plane gateway sends a first charging trigger event to the user plane gateway, where the first charging triggering event is used to trigger the user plane gateway to generate a charging request.
  • the control plane gateway receives the charging request from the user plane gateway.
  • the control plane gateway sends a charging request to the charging system.
  • the control plane gateway obtains the at least one charging trigger event before the control plane gateway sends the first charging trigger event to the user plane gateway.
  • the first charging trigger event is distinguished.
  • a twelfth aspect provides a charging method, including: receiving, by a user plane gateway, a first charging trigger event from a control plane gateway, where the first charging triggering event is used to trigger a user plane gateway to generate a charging request.
  • the user plane gateway detects that the first charging trigger event occurs, the user plane gateway generates a charging request according to the service usage information.
  • the user plane gateway sends a charging request to the control plane gateway.
  • the user plane gateway when the first charging triggering event does not cause the charging session to end or the bill is closed, the user plane gateway is in the control plane. Before the gateway sends the generated charging request, the user plane gateway stores the first charging trigger event and the service usage information before the first charging trigger event occurs. The user plane gateway re-accumulates the subsequent service usage information.
  • the user plane gateway when the first charging trigger event causes the charging session to end or the bill is closed, the user plane gateway sends a charging request to the control plane gateway, which can reduce the amount of information interaction between the control plane gateway and the user plane gateway. Frequency, saving network resources.
  • the user plane gateway receives at least one charging trigger event from the control plane gateway, where at least one The fee triggering event includes a first charging trigger event.
  • the user plane gateway distinguishes the first charging trigger event from at least one charging trigger event.
  • a charging apparatus including a processor, a memory, a communication interface, and a bus, and the processor is connected to the memory and the communication interface through a bus.
  • the memory is for storing instructions for the processor to execute, and the communication interface is for communicating with the user plane gateway under the control of the processor.
  • the processor executes the instructions stored in the memory, the processor is caused to perform the method of the eleventh aspect.
  • a charging apparatus including a processor, a memory, a communication interface, and a bus, and the processor is connected to the memory and the communication interface through a bus.
  • the memory is for storing instructions for the processor to execute
  • the communication interface is for communicating with the control plane gateway under the control of the processor.
  • a computer readable storage medium wherein executable program code is stored, the program code for implementing the method of the eleventh aspect.
  • a computer readable storage medium wherein the executable is stored Program code for implementing the method of the twelfth aspect.
  • a charging apparatus comprising means for performing the method of the eleventh aspect.
  • a charging apparatus comprising means for performing the method of the twelfth aspect.
  • the first charging trigger event is monitored by the control plane gateway or the user plane gateway, and the traffic used by the user can be charged after the first charging trigger event occurs.
  • the user plane gateway sends the service usage information to the control plane gateway to reduce the information interaction between the control plane gateway and the user plane gateway. Data volume and frequency save network resources.
  • FIG. 1 is a schematic diagram of a network architecture 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 structural diagram of a charging apparatus 600 according to an embodiment of the present invention.
  • FIG. 7 is a schematic structural diagram of a charging apparatus 700 according to an embodiment of the present 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 billing trigger event when the event indicated by the billing trigger event occurs, the billing information before the event occurs needs to be packaged and added to the bill, and the billing information needs to be restarted. For example, if the user location changes to a charging trigger event, the user is originally located in the A area, and then moved to the B area, the user uses the charging information generated by the service in the A area, and the charging information generated by the user using the service in the B area is The bills need to be listed separately.
  • FIG. 1 is a schematic diagram of a network architecture 100 applied to an embodiment of the present invention for implementing offline charging under a CU separation architecture.
  • the user plane gateway 101 is configured to perform forwarding processing of the data stream, and the control plane gateway 102 is configured to provide a billing interface.
  • the user plane gateway 101 or the control plane gateway 102 monitors the charging trigger event. When the charging triggering event occurs, the user plane gateway 101 cooperates with the control plane gateway 102 to send the charging request to the charging.
  • the system 103 performs charging to implement offline charging under the CU separation architecture.
  • 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 send a first charging trigger event to the user plane gateway, where the first charging trigger event is used to trigger the
  • the user plane gateway generates service usage information; receives service usage information from the user plane gateway; generates a charging request according to the service usage information; and sends the charging request to the charging system.
  • the processor 202 is configured to perform receiving a first charging trigger event from the control plane gateway, where the first charging trigger event is used to trigger the user plane gateway to generate service usage information. Generating service usage information when detecting the occurrence of the first charging trigger event; and transmitting the generated service usage information to the control plane gateway.
  • 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 can be performed by the user plane gateway 101 and the control plane gateway 102 in FIG.
  • the user plane gateway establishes an IP-CAN bearer with the control plane gateway.
  • the control plane gateway sends a first charging triggering event to the user plane gateway, where the first charging triggering event is used to trigger the user plane gateway to generate service usage information.
  • the user plane gateway receives a first charging trigger event from the control plane gateway, where the first charging triggering event is used to trigger the generation of service usage information.
  • business usage information includes business usage.
  • the service usage information may further include at least one of QoS information, a rate group, a service identifier, a PCC rule identifier, and an ADC rule identifier.
  • the service usage includes at least one of service usage time, uplink traffic, downlink traffic, and duration.
  • the user plane gateway When the user plane gateway detects that the first charging trigger event occurs, the user plane gateway generates service usage information.
  • the first charging trigger event may be a trigger event monitored by the user plane gateway, or may be a trigger event monitored by the control plane gateway.
  • the user plane gateway may obtain the first charging trigger event by: before the control plane gateway sends the first charging trigger event to the user plane gateway, The control plane gateway distinguishes the first charging trigger event from the at least one charging trigger event, and then sends the first charging trigger event to the user plane gateway.
  • the user plane gateway receives at least one charging trigger event from the control plane gateway, where the first charging triggering event is included; the user plane gateway distinguishes the first charging triggering event from the at least one charging triggering event.
  • the “control plane gateway” sends the first charging trigger event to the user plane gateway” in S302, including the control plane gateway
  • the user plane gateway sends a monitoring indication, where the monitoring indication carries the first charging triggering event, indicating that the user plane gateway monitors the first triggering event; and the “user plane gateway receives the first charging triggering event from the control plane gateway” in S303, including the user.
  • the gateway receives the monitoring indication from the control plane gateway, and the monitoring indication carries the first charging triggering event, indicating that the user plane gateway monitors the first triggering event.
  • the user plane gateway detects that the first charging trigger event occurs, and the user plane gateway itself monitors that the first charging trigger event occurs.
  • the control plane gateway can obtain the first charging trigger event in the following manner: the control plane gateway distinguishes the first charging from the at least one charging trigger event. trigger event. Or the user plane gateway receives at least one charging trigger event from the control plane gateway, where the first charging triggering event is included; the user plane gateway distinguishes the first charging triggering event from the at least one charging triggering event, and then the first A billing trigger event is sent to the control plane gateway.
  • the “control plane gateway” sends the first charging trigger event to the user plane gateway” in S302, where the control plane gateway sends a notification message to the user plane gateway, where The notification message carries a first charging trigger event, indicating that the first triggering event occurs;
  • the “user plane gateway receiving the first charging triggering event from the control plane gateway” in S303 includes the user plane gateway receiving the notification message from the control plane gateway, The notification message carries a first charging trigger event, indicating that the first triggering event occurs.
  • the user plane gateway detects that the first charging trigger event occurs.
  • the user plane gateway sends the service usage information to the control plane gateway.
  • the user plane gateway further sends a first charging trigger event to the control plane gateway.
  • the control plane gateway receives service usage information from the user plane gateway.
  • control plane gateway further receives a first charging trigger event from the user plane gateway.
  • the user plane gateway when the first charging trigger event causes the charging session to end or the bill to be closed, the user plane gateway sends the generated service usage information to the control plane gateway. This can reduce the amount and frequency of information exchange between the control plane gateway and the user plane gateway, and save network resources.
  • the user plane gateway stores the first charging trigger event before the user plane gateway sends the generated service usage information to the control plane gateway. And service usage information; the user plane gateway re-accumulates the subsequent service usage information.
  • the user plane gateway can record the service usage information in the form of a bill, and send the recorded multiple words to the control plane gateway, thereby reducing the user plane gateway and the control.
  • the control plane gateway generates a charging request according to the service usage information.
  • the control plane gateway further generates a charging request according to the first charging trigger event sent by the user plane gateway and at least one of the self configuration information, the user information, the network information, and the service information.
  • the self-configuration information, the user information, the network information, and the service information include a user name, a serving node type, a serving gateway address (SGW address), and a time zone.
  • control plane gateway can generate a bill according to the service usage information, and send the bill to the billing system after a certain time. Or, after the bill reaches a certain amount, the bill is sent to the billing system.
  • the control plane gateway sends the charging request to a charging system.
  • the first charging trigger event is monitored by the control plane gateway or the user plane gateway, and the traffic used by the user can be charged after the first charging trigger event occurs.
  • the user plane gateway sends the service usage information to the control plane gateway to reduce the information interaction between the control plane gateway and the user plane gateway. Data volume and frequency save network resources.
  • the user plane gateway when the service usage information sent by the user plane gateway only includes the service usage, the user plane gateway does not need to obtain other information for generating the charging request, which can alleviate the pressure of the user plane gateway; when the user side gateway sends the service usage information
  • the control plane gateway does not need to acquire the information, and the pressure on the control plane gateway can be reduced.
  • the service usage information may be carried by the charging container.
  • the specific process is as follows. See FIG. 4 .
  • the billing container is an important part of the billing request and bill, and is a structured data set.
  • the billing container includes a service usage amount, and may further include at least one of a container opening and closing time, a rate group, a service identifier, and a billing trigger event of closing the container.
  • the billing container can be represented by a service data container field.
  • the service data container can contain the following fields:
  • the user plane gateway establishes an IP-CAN bearer with the control plane gateway.
  • the control plane gateway sends the first charging trigger event and the information about the charging container to the user plane gateway, where the first charging triggering event is used to trigger the user plane gateway to generate the charging container.
  • the information generated by the control plane gateway to generate the charging container to the user plane gateway includes information required to generate the charging container but not available to the user plane gateway.
  • the information for generating the charging container includes a Serving GPRS Support Node (SGSN) address, a user location information, a Presence Reporting Area state, and a Closed Subscriber Group of the user. CSG) at least one of the information.
  • SGSN Serving GPRS Support Node
  • CSG Closed Subscriber Group of the user.
  • the user plane gateway receives the first charging trigger event from the control plane gateway and the information about generating the charging container, where the first charging triggering event is used to trigger the user plane gateway to generate the charging container.
  • the first charging trigger event and the information about generating the charging container may be sent by using one message, or may be sent by multiple messages, which is not limited by the present invention.
  • the user plane gateway When the user plane gateway detects that the first charging trigger event occurs, the user plane gateway generates a charging container according to the information about the generated charging container.
  • S404 The specific description of S404 is the same as that of S304 in the embodiment of FIG. 3, and details are not described herein again. It should be noted that in the specific description of S404, the specific description of S304 should be "S302" and “S303" referred to in the description are respectively changed to “S402" and “S403" in the embodiment of Fig. 4.
  • the user plane gateway sends the generated charging container to the control plane gateway.
  • the control plane gateway receives a charging container from the user plane gateway.
  • the control plane gateway generates a charging request according to the charging container.
  • FIG. 4 is a specific implementation of the embodiment of FIG. 3, and the feature description of the embodiment of FIG. 3 is applicable to the embodiment, and details are not described herein again.
  • the first charging trigger event is monitored by the control plane gateway or the user plane gateway, and the traffic used by the user can be charged after the first charging trigger event occurs.
  • the user plane gateway sends the charging container to the control plane gateway to reduce the information interaction between the control plane gateway and the user plane gateway. Data volume and frequency save network resources.
  • FIG. 5 is an exemplary flow diagram of a charging method 500 in accordance with an embodiment of the present invention.
  • the charging method 500 can be performed by the user plane gateway 101 and the control plane gateway 102 in FIG.
  • S501 The user plane gateway establishes an IP-CAN bearer with the control plane gateway.
  • the control plane gateway sends a first charging triggering event to the user plane gateway, where the first charging triggering event is used to trigger the user plane gateway to generate a charging request.
  • the control plane gateway further sends information for generating a charging request to the user plane gateway, including at least one of user information, network information, and service information.
  • the user plane gateway receives a first charging trigger event from the control plane gateway, where the first charging triggering event is used to trigger the generation of the charging request.
  • S504 The specific description of S504 is the same as that of S304 in the embodiment of FIG. 3, and details are not described herein again. It should be noted that, in the specific description of S504, "S302" and “S303” involved in the detailed description of S304 should be changed to “S502" and "S503" in the embodiment of Fig. 5, respectively.
  • the user plane gateway also generates a charging request according to the first charging trigger event and its own configuration information.
  • the user plane gateway further generates a charging request according to the cache charging information triggered by the charging trigger event that occurs before the first charging trigger event occurs.
  • the cache charging information includes service usage information.
  • the user plane gateway sends the charging request to the control plane gateway.
  • the control plane gateway receives a charging request from the user plane gateway.
  • the user plane gateway when the first charging trigger event causes the charging session to end or the bill to be closed, the user plane gateway sends a charging request to the control plane gateway. This can reduce the amount and frequency of information exchange between the control plane gateway and the user plane gateway, and save network resources.
  • the user plane gateway stores the first charging trigger event and the first time before the user plane gateway sends the charging request to the control plane gateway.
  • the user plane gateway may record the charging information in the form of a bill, and send the recorded multiple bills to the control plane gateway through the charging request, thereby reducing the user plane gateway and the control plane gateway.
  • the frequency of interactions thereby reducing network consumption.
  • the control plane gateway sends the charging request to a charging system.
  • the first charging trigger event is monitored by the control plane gateway or the user plane gateway, and the traffic used by the user can be charged after the first charging trigger event occurs.
  • the user plane gateway sends a charging request to the control plane gateway to reduce information interaction between the control plane gateway and the user plane gateway. Data volume and frequency save network resources.
  • FIG. 6 is a schematic structural diagram of a charging apparatus 600 according to an embodiment of the present invention.
  • the charging device 600 includes a transmitting module 602, a receiving module 604, and a processing module 606.
  • the billing device 600 is the control plane gateway 102 shown in FIG. 1 or the computer device 200 of FIG.
  • the sending module 602 is configured to send a first charging triggering event to the user plane gateway, where the first charging triggering event is used to trigger the user plane gateway to generate service usage information.
  • the receiving module 604 is configured to receive service usage information from the user plane gateway.
  • the processing module 606 is configured to generate a charging request according to the service usage information.
  • the sending module 602 is further configured to send the charging request to the charging system.
  • the service usage information may be carried by the charging container.
  • the receiving module 604 is further configured to receive the first charging trigger event from the user plane gateway, and the processing module 606 is further configured to generate the charging request according to the first charging trigger event. .
  • the processing module 604 is further configured to distinguish, according to the at least one charging trigger event.
  • the first charging trigger event is further configured to distinguish, according to the at least one charging trigger event.
  • FIG. 7 is a schematic structural diagram of a charging apparatus 700 according to an embodiment of the present invention.
  • the charging device 700 includes a receiving module 702, a processing module 704, and a sending module 706.
  • the billing device 700 is the user plane gateway 101 shown in FIG. 1 or the computer device 200 in FIG.
  • the receiving module 702 is configured to receive a first charging trigger event from the control plane gateway, where the first charging triggering event is used to trigger the processing module 704 to generate service usage information.
  • the processing module 704 is configured to generate service usage information when detecting that the first charging trigger event occurs.
  • the sending module 706 is configured to send the service usage information to the control plane gateway.
  • the service usage information may be carried by the charging container.
  • the charging device 700 further includes a storage module 708, where the sending module 706 sends the control module to the control plane gateway when the first charging trigger event does not cause the charging session to end or the bill is closed.
  • the storage module 708 is configured to store the first charging trigger event and the generated service usage information, and the processing module 704 is further configured to re-accumulate the subsequent service usage information.
  • the receiving module 702 is further configured to receive at least one charging trigger event from the control plane gateway, where the at least one charging triggering event includes the first charging triggering event; the processing module 704, And is further configured to distinguish the first charging trigger event from the at least one charging trigger event.
  • the optional sending module 706 is further configured to send the first charging trigger event to the control plane gateway.
  • 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 transmitting module 802 and a receiving module 804.
  • the billing device 800 is the control plane gateway 102 shown in FIG. 1 or the computer device 200 of FIG.
  • the sending module 802 is configured to send a first charging trigger event to the user plane gateway, where the first charging triggering event is used to trigger the user plane gateway to generate a charging request.
  • the receiving module 804 is configured to receive a charging request from the user plane gateway.
  • the sending module 802 is further configured to send the charging request to the charging system.
  • the charging device 800 further includes a processing module 806, before the sending module 802 sends the first charging trigger event to the user plane gateway, the processing module 806 distinguishes the at least one charging trigger event.
  • the first billing trigger event before the sending module 802 sends the first charging trigger event to the user plane gateway, the processing module 806 distinguishes the at least one charging trigger event.
  • the first billing trigger event before the sending module 802 sends the first charging trigger event to the user plane gateway, the processing module 806 distinguishes the at least one charging trigger event.
  • the first billing trigger event before the sending module 802 sends the first charging trigger event to the user plane gateway
  • FIG. 9 is a schematic structural diagram of a charging apparatus 900 according to an embodiment of the present invention.
  • Charging The 900 includes a receiving module 902, a processing module 904, and a transmitting module 906.
  • the billing device 900 is the user plane gateway 101 shown in FIG. 1 or the computer device 200 in FIG.
  • the receiving module 902 is configured to receive a first charging trigger event from the control plane gateway, where the first charging triggering event is used to trigger the generation of the charging request.
  • the processing module 904 is configured to generate a charging request according to the service usage information when detecting that the first charging trigger event occurs.
  • the sending module 906 is configured to send the charging request to the control plane gateway.
  • the charging device 900 further includes a storage module 908, where the sending module 906 sends the generating to the control plane gateway when the first charging triggering event does not cause the charging session to end or the bill is closed.
  • the storage module 908 is configured to store the first charging trigger event and the service usage information before the first charging trigger event occurs; the processing module 904 re-accumulates the subsequent service usage information.
  • the receiving module 902 is further configured to receive at least one charging trigger event from the control plane gateway, where the at least one charging trigger event includes the first charging trigger event; and the processing module 904 is further configured to The first charging trigger event is distinguished from the at least one charging trigger event.
  • the "module" in the embodiment of FIG. 6 to 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 above storage module can be implemented by a memory of a 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 It is implemented 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)
  • Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • Finance (AREA)
  • Physics & Mathematics (AREA)
  • Marketing (AREA)
  • General Business, Economics & Management (AREA)
  • Economics (AREA)
  • Theoretical Computer Science (AREA)
  • Strategic Management (AREA)
  • Technology Law (AREA)
  • General Physics & Mathematics (AREA)
  • Development Economics (AREA)
  • Databases & Information Systems (AREA)
  • Probability & Statistics with Applications (AREA)
  • Computer Hardware Design (AREA)
  • General Engineering & Computer Science (AREA)
  • Charge And Discharge Circuits For Batteries Or The Like (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Meter Arrangements (AREA)

Abstract

本发明的实施例提供一种计费方法，包括控制面网关向用户面网关发送第一计费触发事件，所述第一计费触发事件用于触发所述用户面网关生成业务使用信息；当所述用户面网关检测到所述第一计费触发事件发生时，所述用户面网关生成业务使用信息；所述用户面网关向所述控制面网关发送所述业务使用信息；所述控制面网关根据所述业务使用信息生成计费请求；所述控制面网关向计费系统发送所述计费请求，实现了PGW CU分离下的离线计费。

Description

一种计费方法、装置及系统
本申请要求于2016年2月4日提交中国专利局、申请号为201610079306.X，发明名称为“一种计费方法、装置及系统”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本发明涉及通信领域，尤其涉及一种计费方法、装置及系统。
背景技术
当前的演进分组核心网(Evolved Packet Core，EPC)网络架构中，终端所发送/接收的数据包需要通过PGW(Public Data Network Gateway，公共数据网网关)处理和分流，PGW所在的位置过高，导致每一个数据包都要在网络中传输很长距离才能得到转发处理。在这样的情况下，3GPP提出了CU(control and user)分离的构想，即将PGW拆分成用户面(user plane)与控制面(control plane)进行分离布署。控制面包含控制协议(protocols)和对用户面的支撑功能，如控制E-UTRA(Evolved Universal Terrestrial Radio Access)网络接入连接，控制已建立的网络连接的路由路径以支持用户移动，控制网络资源分配以满足用户需求。用户面传输数据流。用户面网关(PGW-U)可以分布式部署，与传统PGW相比可以下移到位置较低的地方，比如靠近居民接入网(Residential Access Network，RAN)。其中，下移是站在网络控制的角度，指向用户侧靠近。一些本地业务(服务器在本地)端到端(End to End，E2E)的数据面传输可以在本地进行，节省了很多传输时延。同时控制面网关(PGW-C)仍然保留集中部署。
在PGW CU分离的构想中，没有针对CU分离时的离线计费方案。
发明内容
本发明的实施例提供一种计费方法和装置，能够实现PGW CU分离下的离线计费。
第一方面，提供了一种系统，包括控制面网关和用户面网关，其中，控制面网关向用户面网关发送第一计费触发事件，第一计费触发事件用于触发用户面网关生成业务使用信息，当用户面网关检测到第一计费触发事件发生时，生成业务使用信息，向控制面网关发送业务使用信息， 控制面网关根据业务使用信息生成计费请求，向计费系统发送计费请求。
通过控制面网关或用户面网关对第一计费触发事件进行监控，能够在第一计费触发事件发生后对用户使用的业务量进行计费，实现了CU分离架构下的计费。
第二方面，提供了一种计费方法，包括：控制面网关向用户面网关发送第一计费触发事件，其中，第一计费触发事件用于触发用户面网关生成业务使用信息。控制面网关接收来自用户面网关的业务使用信息，根据业务使用信息生成计费请求。控制面网关向计费系统发送计费请求。
结合第二方面的实现方式，在第二方面第一种可能的实现方式中，控制面网关还接收来自用户面网关的第一计费触发事件，则控制面网关还根据第一计费触发事件生成计费请求。
这样可以将业务使用信息与第一计费触发事件对应，在多个第一计费触发事件发生时保证计费的准确性。
结合第二方面、第二方面的第一种可能的实现方式，在第二种可能实现的方式中，在控制面网关向用户面网关发送第一计费触发事件之前，控制面网关从至少一个计费触发事件中区分出第一计费触发事件。
第三方面，提供了一种计费方法，包括：用户面网关接收来自控制面网关的第一计费触发事件，其中，第一计费触发事件用于触发用户面网关生成业务使用信息。当用户面网关检测到第一计费触发事件发生时，用户面网关生成业务使用信息。用户面网关向控制面网关发送业务使用信息。
结合第三方面的实现方式，在第三方面第一种可能的实现方式中，当第一计费触发事件不会导致计费会话结束或话单关闭时，在用户面网关向控制面网关发送业务使用信息之前，用户面网关存储第一计费触发事件和生成的业务使用信息。用户面网关重新累计后续业务使用信息。
这样可以在第一计费触发事件导致计费会话结束或话单关闭时，用户面网关才向控制面网关发送业务使用信息，能够减少控制面网关与用户面网关之间的信息交互数据量与频率，节省网络资源。
结合第三方面、第三方面的第一种可能的实现方式，在第二种可能实现的方式中，用户面网关接收来自控制面网关的至少一个计费触发事件，其中，至少一个计费触发事件包含第一计费触发事件。用户面网关从至少一个计费触发事件中区分出第一计费触发事件。
结合第三方面、第三方面的第一种至第二种可能的实现方式，在第 三种可能实现的方式中，用户面网关还向控制面网关发送第一计费触发事件。
结合上述第二方面和第三方面，业务使用信息通过计费容器携带。
第四方面，提供了一种计费装置，包括处理器，存储器，通信接口和总线，处理器与存储器、通信接口通过总线连接。存储器用于存储指令，处理器用于执行该指令，在处理器的控制下，通信接口用于与用户面网关通信。当处理器执行存储器存储的指令时，使得处理器执行第二方面所述的方法。
第五方面，提供了一种计费装置，包括处理器，存储器，通信接口和总线，处理器与存储器、通信接口通过总线连接。存储器用于存储指令，处理器用于执行该指令，在处理器的控制下，通信接口用于与控制面网关通信。当处理器执行存储器存储的指令时，使得处理器执行第三方面所述的方法。
第六方面，提供了一种计算机可读存储介质，其中存储有可执行的程序代码，该程序代码用以实现第二方面所述的方法。
第七方面，提供了一种计算机可读存储介质，其中存储有可执行的程序代码，该程序代码用以实现第三方面所述的方法。
第八方面，提供了一种计费装置，包含用于执行第二方面中的方法的模块。
第九方面，提供了一种计费装置，包含用于执行第三方面中的方法的模块。
第十方面，提供了一种系统，包括控制面网关和用户面网关，其中，控制面网关向用户面网关发送第一计费触发事件，第一计费触发事件用于触发用户面网关生成计费请求。用户面网关在检测到第一计费触发事件发生后，生成计费请求并向控制面网关发送。控制面网关向计费系统发送该计费请求。
通过控制面网关或用户面网关对第一计费触发事件进行监控，能够在第一计费触发事件发生后对用户使用的业务量进行计费，实现了CU分离架构下的计费。
第十一方面，提供了一种计费方法，包括：控制面网关向用户面网关发送第一计费触发事件，其中，第一计费触发事件用于触发用户面网关生成计费请求。控制面网关接收来自用户面网关的计费请求。控制面网关向计费系统发送计费请求。
结合第十一方面的实现方式，在第十一方面第一种可能的实现方式中，在控制面网关向用户面网关发送第一计费触发事件之前，控制面网关从至少一个计费触发事件中区分出第一计费触发事件。
第十二方面，提供了一种计费方法，包括：用户面网关接收来自控制面网关的第一计费触发事件，第一计费触发事件用于触发用户面网关生成计费请求。当用户面网关检测到第一计费触发事件发生时，用户面网关根据业务使用信息生成计费请求。用户面网关向控制面网关发送计费请求。
结合第十二方面的实现方式，在第十二方面第一种可能的实现方式中，当第一计费触发事件不会导致计费会话结束或话单关闭时，在用户面网关向控制面网关发送生成的计费请求之前，用户面网关存储第一计费触发事件和第一计费触发事件发生之前的业务使用信息。用户面网关重新累计后续业务使用信息。
这样可以在第一计费触发事件导致计费会话结束或话单关闭时，用户面网关才向控制面网关发送计费请求，能够减少控制面网关与用户面网关之间的信息交互数据量与频率，节省网络资源。
结合第十二方面、第十二方面的第一种可能的实现方式，在第二种可能实现的方式中，用户面网关接收来自控制面网关的至少一个计费触发事件，其中，至少一个计费触发事件包含第一计费触发事件。用户面网关从至少一个计费触发事件中区分出第一计费触发事件。
第十三方面，提供了一种计费装置，包括处理器，存储器，通信接口和总线，处理器与存储器、通信接口通过总线连接。存储器用于存储指令，处理器用于执行该指令，在处理器的控制下，通信接口用于与用户面网关通信。当处理器执行存储器存储的指令时，使得处理器执行第十一方面所述的方法。
第十四方面，提供了一种计费装置，包括处理器，存储器，通信接口和总线，处理器与存储器、通信接口通过总线连接。存储器用于存储指令，处理器用于执行该指令，在处理器的控制下，通信接口用于与控制面网关通信。当处理器执行存储器存储的指令时，使得处理器执行第十二方面所述的方法。
第十五方面，提供了一种计算机可读存储介质，其中存储有可执行的程序代码，该程序代码用以实现第十一方面所述的方法。
第十六方面，提供了一种计算机可读存储介质，其中存储有可执行 的程序代码，该程序代码用以实现第十二方面所述的方法。
第十七方面，提供了一种计费装置，包含用于执行第十一方面中的方法的模块。
第十八方面，提供了一种计费装置，包含用于执行第十二方面中的方法的模块。
根据本发明实施例提供的技术方案，通过控制面网关或用户面网关对第一计费触发事件进行监控，能够在第一计费触发事件发生后对用户使用的业务量进行计费，实现了CU分离架构下的计费。进一步的，可以在第一计费触发事件导致计费会话结束或话单关闭的时，用户面网关才向控制面网关发送业务使用信息，以减少控制面网关与用户面网关之间的信息交互数据量与频率，节省网络资源。
附图说明
为了更清楚地说明本发明实施例或现有技术中的技术方案，下面将对实施例或现有技术描述中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本发明的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其他的附图。
图1是本发明实施例应用的网络架构100的示意图；
图2是依据本发明一实施例的计算机设备200的硬件结构示意图；
图3是依据本发明一实施例的计费方法300的示范性流程图；
图4是依据本发明一实施例的计费方法400的示范性流程图；
图5是依据本发明一实施例的计费方法500的示范性流程图；
图6是依据本发明一实施例的计费装置600的结构示意图；
图7是依据本发明一实施例的计费装置700的结构示意图；
图8是依据本发明一实施例的计费装置800的结构示意图；
图9是依据本发明一实施例的计费装置900的结构示意图。
具体实施方式
以下描述中，为了说明而不是为了限定，提出了诸如特定系统结构、接口、技术之类的具体细节，以便透彻理解本发明。然而，本领域的技术人员应当清楚，在没有这些具体细节的其它实施例中也可以实现本发明。在其它情况中，省略对众所周知的装置、电路以及方法的详细说明，以免不必要的细节妨碍本发明的描述。
为方便理解和说明本发明提供的实施例，首先介绍几个与本发明相关的概念。计费触发事件，计费触发事件所指的事件发生时，该事件发生之前的计费信息需要被打包并增加到话单当中，计费信息后续需要重新开始累计。例如，配置用户位置变化为计费触发事件，用户原来位于A区域，后来移动到B区域，则用户在A区域使用业务产生的计费信息，与用户在B区域使用业务产生的计费信息在话单中需要分别列出。
图1是本发明实施例应用的网络架构100的示意图，用于实现CU分离架构下的离线计费。其中用户面网关101用于进行数据流的转发处理，控制面网关102用于向外提供计费接口。在本发明的实施例中，用户面网关101或控制面网关102监控计费触发事件，当计费触发事件发生时，用户面网关101与控制面网关102配合，将计费请求发送给计费系统103进行计费，以实现CU分离架构下的离线计费。
用户面网关101和控制面网关102可以通过计算机设备的形式实现。图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是控制面网关102时，处理器202用于执行向用户面网关发送第一计费触发事件，所述第一计费触发事件用于触发所述 用户面网关生成业务使用信息；接收来自所述用户面网关的业务使用信息；根据所述业务使用信息生成计费请求；向计费系统发送所述计费请求。
当计算机设备200是用户面网关101时，处理器202用于执行接收来自控制面网关的第一计费触发事件，所述第一计费触发事件用于触发所述用户面网关生成业务使用信息；当检测到所述第一计费触发事件发生时，生成业务使用信息；向所述控制面网关发送所述生成的业务使用信息。
图3是依据本发明一实施例的计费方法300的示范性流程图。在具体实现过程中，计费方法300可以由图1中的用户面网关101和控制面网关102来执行。
S301，用户面网关与控制面网关建立IP-CAN承载。
S302，控制面网关向用户面网关发送第一计费触发事件，所述第一计费触发事件用于触发所述用户面网关生成业务使用信息。
S303，用户面网关接收来自控制面网关的第一计费触发事件，所述第一计费触发事件用于触发生成业务使用信息。
其中，业务使用信息包括业务使用量。业务使用信息还可以包括QoS信息，费率组，业务标识，PCC规则标识、ADC规则标识中的至少一种。
其中，业务使用量包括业务使用时间、上行流量、下行流量、时长中的至少一种。
S304，当所述用户面网关检测到所述第一计费触发事件发生时，所述用户面网关生成业务使用信息。
具体的，第一计费触发事件可以为由用户面网关监控的触发事件，也可以为由控制面网关监控的触发事件。
当第一计费触发事件为由用户面网关监控的触发事件时，用户面网关可以通过以下方式获取第一计费触发事件：在控制面网关向用户面网关发送第一计费触发事件之前，控制面网关从至少一个计费触发事件中区分出第一计费触发事件，之后将第一计费触发事件发送给用户面网关。或者，用户面网关接收来自控制面网关的至少一个计费触发事件，其中包含第一计费触发事件；用户面网关从至少一个计费触发事件中区分出第一计费触发事件。
当第一计费触发事件为由用户面网关监控的触发事件时，S302中的“控制面网关向用户面网关发送第一计费触发事件”包括控制面网关向 用户面网关发送监控指示，该监控指示携带第一计费触发事件，指示用户面网关监控第一触发事件；S303中的“用户面网关接收来自控制面网关的第一计费触发事件”包括用户面网关接收来自控制面网关的监控指示，该监控指示携带第一计费触发事件，指示用户面网关监控第一触发事件。用户面网关检测到第一计费触发事件发生包括用户面网关自身监控到第一计费触发事件发生。
当第一计费触发事件为由控制面网关监控的触发事件时，控制面网关可以通过以下方式获取第一计费触发事件：控制面网关从至少一个计费触发事件中区分出第一计费触发事件。或者，用户面网关接收来自控制面网关的至少一个计费触发事件，其中包含第一计费触发事件；用户面网关从至少一个计费触发事件中区分出第一计费触发事件，之后将第一计费触发事件发送给控制面网关。
当第一计费触发事件为由控制面网关监控的触发事件时，S302中的“控制面网关向用户面网关发送第一计费触发事件”包括控制面网关向用户面网关发送通知消息，该通知消息携带第一计费触发事件，指示第一触发事件发生；S303中的“用户面网关接收来自控制面网关的第一计费触发事件”包括用户面网关接收来自控制面网关的通知消息，该通知消息携带第一计费触发事件，指示第一触发事件发生。当用户面网关接收到指示第一计费触发事件发生的通知消息时，用户面网关检测第一计费触发事件发生。
S305，所述用户面网关向所述控制面网关发送所述业务使用信息。
可选的，用户面网关还向控制面网关发送第一计费触发事件。
S306，所述控制面网关接收来自所述用户面网关的业务使用信息。
可选的，控制面网关还接收来自用户面网关的第一计费触发事件。
可选的，当第一计费触发事件会导致计费会话结束或话单关闭时，用户面网关向控制面网关发送生成的业务使用信息。这样可以减少控制面网关与用户面网关之间的信息交互数据量与频率，节省网络资源。
可选的，当第一计费触发事件不会导致计费会话结束或话单关闭时，在用户面网关向控制面网关发送生成的业务使用信息之前，用户面网关存储第一计费触发事件和业务使用信息；用户面网关重新累计后续业务使用信息。
可选的，用户面网关可以将业务使用信息以话单的形式记录下来，并将记录的多个话单一并发送给控制面网关，从而减小用户面网关与控 制面网关的交互频率，从而减小网络消耗。
S307，所述控制面网关根据所述业务使用信息生成计费请求。
控制面网关还根据用户面网关发送的第一计费触发事件以及自身配置信息、用户信息、网络信息、业务信息中的至少一种生成计费请求。其中，自身配置信息、用户信息、网络信息、业务信息包括用户标识(User Name)，服务节点类型(serving node type)，服务网关地址(serving gateway address，SGW address)，时区(timezone)。
可选的，控制面网关可以根据业务使用信息生成话单，当一定时间之后，将话单发送给计费系统。或者，当话单达到一定数量之后，将话单发送给计费系统。
S308，所述控制面网关向计费系统发送所述计费请求。
根据本发明实施例提供的技术方案，通过控制面网关或用户面网关对第一计费触发事件进行监控，能够在第一计费触发事件发生后对用户使用的业务量进行计费，实现了CU分离架构下的计费。进一步的，可以在第一计费触发事件导致计费会话结束或话单关闭的时，用户面网关才向控制面网关发送业务使用信息，以减少控制面网关与用户面网关之间的信息交互数据量与频率，节省网络资源。另外，当用户面网关发送的业务使用信息只包含业务使用量时，用户面网关不需要获取其他生成计费请求的信息，能够减轻用户面网关的压力；当用户面网关发送的业务使用信息还包含上述的QoS、费率组等信息时，控制面网关无需获取这些信息，能够减轻控制面网关的压力。
在本发明实施例的一种具体实现方式中，可以通过计费容器来携带业务使用信息，其具体过程如下，参见图4。
计费容器是计费请求和话单中的重要组成部分，是结构化的数据集合。计费容器包括业务使用量，还可以包括容器打开和关闭时间，费率组，业务标识，关闭容器的计费触发事件等信息中的至少一种。计费容器可以通过service data container字段表示。在一种实现方式中，service data container可以包含以下字段：
Service-Data-Container::＝<AVP Header:TBD>
[AF-Correlation-Information]
[Charging-Rule-Base-Name]
[Accounting-Input-Octets]
[Accounting-Output-Octets]
[Accounting-Input-Packets]
[Accounting-Output-Packets]
[Local-Sequence-Number]
[QoS-Information]
[Rating-Group]
[Change-Time]
[Service-Identifier]
[Service-Specific-Info]
[SGSN-Address]
[Time-First-Usage]
[Time-Last-Usage]
[Time-Usage]
*[Change-Condition]
[3GPP-User-Location-Info]
S401，用户面网关与控制面网关建立IP-CAN承载。
S402，控制面网关向用户面网关发送第一计费触发事件和生成计费容器的信息，所述第一计费触发事件用于触发所述用户面网关生成计费容器。
可选的，控制面网关向用户面网关发送的生成计费容器的信息包括生成计费容器所需但用户面网关没有的信息。具体的，生成计费容器的信息包括服务GPRS支持节点(Serving GPRS Support Node，SGSN)地址，用户位置信息，用户状态报告区域(Presence Reporting Area)状态，用户的紧密用户群组(Closed Subscriber Group，CSG)信息中的至少一种。
S403，用户面网关接收来自控制面网关的第一计费触发事件和生成计费容器的信息，所述第一计费触发事件用于触发所述用户面网关生成计费容器。
具体的，第一计费触发事件和生成计费容器的信息可以通过一个消息发送，也可以通过多个消息发送，本发明对此不做限制。
S404，当所述用户面网关检测到所述第一计费触发事件发生时，所述用户面网关根据所述生成计费容器的信息生成计费容器。
对S404的具体说明与图3实施例中对S304的具体说明相同，此处不再赘述。应注意的是，对S404的具体说明中，应将对S304的具体说 明中涉及的“S302”与“S303”分别改为图4实施例中的“S402”与“S403”。
S405，所述用户面网关向所述控制面网关发送所述生成的计费容器。
S406，所述控制面网关接收来自所述用户面网关的计费容器。
S407，所述控制面网关根据所述计费容器生成计费请求。
应理解，图4实施例是图3实施例的一种具体实现，图3实施例部分的特征描述适用于本实施例，在此不再赘述。
根据本发明实施例提供的技术方案，通过控制面网关或用户面网关对第一计费触发事件进行监控，能够在第一计费触发事件发生后对用户使用的业务量进行计费，实现了CU分离架构下的计费。进一步的，可以在第一计费触发事件导致计费会话结束或话单关闭的时，用户面网关才向控制面网关发送计费容器，以减少控制面网关与用户面网关之间的信息交互数据量与频率，节省网络资源。
图5是依据本发明一实施例的计费方法500的示范性流程图。在具体实现过程中，计费方法500可以由图1中的用户面网关101和控制面网关102来执行。
S501，用户面网关与控制面网关建立IP-CAN承载。
S502，控制面网关向用户面网关发送第一计费触发事件，所述第一计费触发事件用于触发所述用户面网关生成计费请求。
其中，控制面网关还向用户面网关发送生成计费请求的信息，包括用户信息、网络信息、业务信息中的至少一种。
S503，用户面网关接收来自控制面网关的第一计费触发事件，所述第一计费触发事件用于触发生成计费请求。
S504，所述用户面网关检测到所述第一计费触发事件发生时，所述用户面网关根据业务使用信息生成计费请求。
对S504的具体说明与图3实施例中对S304的具体说明相同，此处不再赘述。应注意的是，对S504的具体说明中，应将对S304的具体说明中涉及的“S302”与“S303”分别改为图5实施例中的“S502”与“S503”。
用户面网关还根据第一计费触发事件以及自身配置信息生成计费请求。
可选的，用户面网关还根据在第一计费触发事件发生之前发生的计费触发事件引发的缓存计费信息生成计费请求。其中，缓存计费信息包含业务使用信息。
S505，所述用户面网关向所述控制面网关发送所述计费请求。
S506，所述控制面网关接收来自所述用户面网关的计费请求。
可选的，当第一计费触发事件会导致计费会话结束或话单关闭时，用户面网关向控制面网关发送计费请求。这样可以减少控制面网关与用户面网关之间的信息交互数据量与频率，节省网络资源。
可选的，当第一计费触发事件不会导致计费会话结束或话单关闭时，在用户面网关向控制面网关发送计费请求之前，用户面网关存储第一计费触发事件和第一计费触发事件发生之前的计费信息；用户面网关重新累计后续业务使用信息。
可选的，用户面网关可以将计费信息以话单的形式记录下来，并将记录的多个话单通过计费请求一并发送给控制面网关，从而减小用户面网关与控制面网关的交互频率，从而减小网络消耗。
S507，所述控制面网关向计费系统发送所述计费请求。
根据本发明实施例提供的技术方案，通过控制面网关或用户面网关对第一计费触发事件进行监控，能够在第一计费触发事件发生后对用户使用的业务量进行计费，实现了CU分离架构下的计费。进一步的，可以在第一计费触发事件导致计费会话结束或话单关闭的时，用户面网关才向控制面网关发送计费请求，以减少控制面网关与用户面网关之间的信息交互数据量与频率，节省网络资源。
图6是依据本发明一实施例的计费装置600的结构示意图。计费装置600包括发送模块602，接收模块604和处理模块606。计费装置600为图1中所示的控制面网关102或图2中计算机设备200。
发送模块602，用于向用户面网关发送第一计费触发事件，所述第一计费触发事件用于触发所述用户面网关生成业务使用信息。
接收模块604，用于接收来自所述用户面网关的业务使用信息。
处理模块606，用于根据所述业务使用信息生成计费请求。
发送模块602，还用于向计费系统发送所述计费请求。
在本发明实施例的一种具体实现方式中，可以通过计费容器来携带业务使用信息。
可选的，接收模块604，还用于接收来自所述用户面网关的所述第一计费触发事件，处理模块606，还用于根据所述第一计费触发事件生成所述计费请求。
可选的，在发送模块602向所述用户面网关发送所述第一计费触发事件之前，所述处理模块604还用于从至少一个计费触发事件中区分出 所述第一计费触发事件。
图7是依据本发明一实施例的计费装置700的结构示意图。计费装置700包括接收模块702，处理模块704和发送模块706。计费装置700为图1中所示的用户面网关101或图2中计算机设备200。
接收模块702，用于接收来自控制面网关的第一计费触发事件，所述第一计费触发事件用于触发所述处理模块704生成业务使用信息。
处理模块704，用于当检测到所述第一计费触发事件发生时，生成业务使用信息。
发送模块706，用于向所述控制面网关发送所述业务使用信息。
在本发明实施例的一种具体实现方式中，可以通过计费容器来携带业务使用信息。
可选的，计费装置700还包括存储模块708，当所述第一计费触发事件不会导致计费会话结束或话单关闭时，在所述发送模块706向所述控制面网关发送所述业务使用信息之前，所述存储模块708，用于存储所述第一计费触发事件和所述生成的业务使用信息；所述处理模块704，还用于重新累计后续业务使用信息。
可选的，接收模块702，还用于接收来自所述控制面网关的至少一个计费触发事件，所述至少一个计费触发事件包含所述第一计费触发事件；所述处理模块704，还用于从所述至少一个计费触发事件中区分出所述第一计费触发事件。
可选的发送模块706，还用于向所述控制面网关发送所述第一计费触发事件。
图8是依据本发明一实施例的计费装置800的结构示意图。计费装置800包括发送模块802和接收模块804。计费装置800为图1中所示的控制面网关102或图2中计算机设备200。
发送模块802，用于向用户面网关发送第一计费触发事件，所述第一计费触发事件用于触发所述用户面网关生成计费请求。
接收模块804，用于接收来自所述用户面网关的计费请求。
发送模块802，还用于向计费系统发送所述计费请求。
可选的，计费装置800还包括处理模块806，在发送模块802向所述用户面网关发送所述第一计费触发事件之前，处理模块806从至少一个计费触发事件中区分出所述第一计费触发事件。
图9是依据本发明一实施例的计费装置900的结构示意图。计费装 置900包括接收模块902，处理模块904和发送模块906。计费装置900为图1中所示的用户面网关101或图2中计算机设备200。
接收模块902，用于接收来自控制面网关的第一计费触发事件，所述第一计费触发事件用于触发生成计费请求。
处理模块904，用于当检测到所述第一计费触发事件发生时，根据业务使用信息生成计费请求。
发送模块906，用于向所述控制面网关发送所述计费请求。
可选的，计费装置900还包括存储模块908，当所述第一计费触发事件不会导致计费会话结束或话单关闭时，在发送模块906向所述控制面网关发送所述生成的计费请求之前，存储模块908用于存储所述第一计费触发事件和所述第一计费触发事件发生之前的业务使用信息；处理模块904重新累计后续业务使用信息。
可选的，接收模块902还用于接收来自所述控制面网关的至少一个计费触发事件，所述至少一个计费触发事件包含所述第一计费触发事件；处理模块904还用于从所述至少一个计费触发事件中区分出所述第一计费触发事件。
其中，图6至图9实施例中的“模块”可以为专用集成电路(Application Specific Integrated Circuit，ASIC)、电子线路、执行一个或多个软件或固件程序的处理器和存储器、组合逻辑电路和其他提供上述功能的组件。可选的，上述计费装置通过计算机设备的形式来实现，上述接收模块、发送模块可以通过计算机设备的处理器、存储器和通信接口来实现，上述处理模块可以通过计算机设备的处理器和存储器来实现，上述存储模块可以通过计算机设备的存储器来实现。
应注意，尽管图2所示的计算机设备200仅仅示出了处理器202、存储器204、通信接口206和总线208，但是在具体实现过程中，本领域的技术人员应当明白，上述计费装置还包含实现正常运行所必须的其他器件。同时，根据具体需要，本领域的技术人员应当明白，上述计费装置还可包含实现其他附加功能的硬件器件。此外，本领域的技术人员应当明白，上述计费装置也可仅仅包含实现本发明实施例所必须的器件，而不必包含图2中所示的全部器件。
另外，在本发明各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以 采用软件功能单元的形式实现。
所述集成的单元如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本发明的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的全部或部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)或处理器(processor)执行本发明各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(ROM，Read-Only Memory)、随机存取存储器(RAM，Random Access Memory)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本发明的具体实施方式，但本发明的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本发明揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本发明的保护范围之内。因此，本发明的保护范围应以所述权利要求的保护范围为准。

Claims (21)

  1. 一种计费方法，其特征在于，包括以下步骤：
    控制面网关向用户面网关发送第一计费触发事件，所述第一计费触发事件用于触发所述用户面网关生成业务使用信息；
    所述控制面网关接收来自所述用户面网关的业务使用信息；
    所述控制面网关根据所述业务使用信息生成计费请求；
    所述控制面网关向计费系统发送所述计费请求。
  2. 如权利要求1所述的方法，其特征在于，所述业务使用信息通过计费容器携带。
  3. 如权利要求1或2所述的方法，其特征在于，所述控制面网关还接收来自所述用户面网关的所述第一计费触发事件，则所述控制面网关还根据所述第一计费触发事件生成所述计费请求。
  4. 如权利要求1至3任意一项所述的方法，其特征在于，在所述控制面网关向所述用户面网关发送所述第一计费触发事件之前，所述方法还包括：
    所述控制面网关从至少一个计费触发事件中区分出所述第一计费触发事件。
  5. 一种计费方法，其特征在于，包括以下步骤：
    用户面网关接收来自控制面网关的第一计费触发事件，所述第一计费触发事件用于触发所述用户面网关生成业务使用信息；
    当所述用户面网关检测到所述第一计费触发事件发生时，所述用户面网关生成业务使用信息；
    所述用户面网关向所述控制面网关发送所述业务使用信息。
  6. 如权利要求5所述的方法，其特征在于，所述业务使用信息通过计费容器携带。
  7. 如权利要求5或6所述的方法，其特征在于，当所述第一计费触发事件不会导致计费会话结束或话单关闭时，在所述用户面网关向所述控制面网关发送所述业务使用信息之前，所述用户面网关存储所述第一计费触发事件和所述生成的业务使用信息；所述用户面网关重新累计后续业务使用信息。
  8. 如权利要求5至7任意一项所述的方法，其特征在于，所述用户面网关接收来自所述控制面网关的至少一个计费触发事件，所述至少一个计费触发事件包含所述第一计费触发事件；所述用户面网关从所述至 少一个计费触发事件中区分出所述第一计费触发事件。
  9. 如权利要求5至8任意一项所述的方法，其特征在于，所述用户面网关还向所述控制面网关发送所述第一计费触发事件。
  10. 一种计费装置，其特征在于，包括发送模块，接收模块和处理模块：
    所述发送模块，用于向用户面网关发送第一计费触发事件，所述第一计费触发事件用于触发所述用户面网关生成业务使用信息；
    所述接收模块，用于接收来自所述用户面网关的业务使用信息；
    所述处理模块，用于根据所述业务使用信息生成计费请求；
    所述发送模块，还用于向计费系统发送所述计费请求。
  11. 如权利要求10所述的装置，其特征在于，所述业务使用信息通过计费容器携带。
  12. 如权利要求10或11所述的装置，其特征在于，所述接收模块，还用于接收来自所述用户面网关的所述第一计费触发事件，所述处理模块，还用于根据所述第一计费触发事件生成所述计费请求。
  13. 如权利要求10至12任意一项所述的装置，其特征在于，在所述发送模块向所述用户面网关发送所述第一计费触发事件之前，所述处理模块还用于从至少一个计费触发事件中区分出所述第一计费触发事件。
  14. 一种计费装置，其特征在于，包括接收模块，处理模块和发送模块：
    所述接收模块，用于接收来自控制面网关的第一计费触发事件，所述第一计费触发事件用于触发所述处理模块生成业务使用信息；
    所述处理模块，用于当检测到所述第一计费触发事件发生时，生成业务使用信息；
    所述发送模块，用于向所述控制面网关发送所述业务使用信息。
  15. 如权利要求14所述的装置，其特征在于，所述业务使用信息通过计费容器携带。
  16. 如权利要求14或15所述的装置，其特征在于，还包括存储模块，当所述第一计费触发事件不会导致计费会话结束或话单关闭时，在所述发送模块向所述控制面网关发送所述业务使用信息之前，所述存储模块，用于存储所述第一计费触发事件和所述生成的业务使用信息；所 述处理模块，还用于重新累计后续业务使用信息。
  17. 如权利要求14至16任意一项所述的装置，其特征在于，所述接收模块，还用于接收来自所述控制面网关的至少一个计费触发事件，所述至少一个计费触发事件包含所述第一计费触发事件；所述处理模块，还用于从所述至少一个计费触发事件中区分出所述第一计费触发事件。
  18. 如权利要求14至17任意一项所述的装置，其特征在于，所述发送模块，还用于向所述控制面网关发送所述第一计费触发事件。
  19. 一种计算设备，包括：处理器、存储器、总线和通信接口；所述存储器用于存储计算设备执行指令，所述处理器与所述存储器通过所述总线连接，当所述计算设备运行时，所述处理器执行所述存储器存储的所述计算机执行指令，以使所述计算设备执行权利要求1至4所述的方法。
  20. 一种计算设备，包括：处理器、存储器、总线和通信接口；所述存储器用于存储计算设备执行指令，所述处理器与所述存储器通过所述总线连接，当所述计算设备运行时，所述处理器执行所述存储器存储的所述计算机执行指令，以使所述计算设备执行权利要求5至9所述的方法。
  21. 一种系统，包括控制面网关和用户面网关：
    所述控制面网关，用于向用户面网关发送第一计费触发事件，所述第一计费触发事件用于触发所述用户面网关生成业务使用信息；接收来自所述用户面网关的业务使用信息；根据所述业务使用信息生成计费请求；向计费系统发送所述计费请求；
    所述用户面网关，用于接收来自控制面网关的第一计费触发事件；当检测到所述第一计费触发事件发生时，生成业务使用信息；向所述控制面网关发送所述业务使用信息。
PCT/CN2016/111517 2016-02-04 2016-12-22 一种计费方法、装置及系统 WO2017133342A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP16889148.9A EP3402231B1 (en) 2016-02-04 2016-12-22 Charging method, device, and system
US16/054,615 US10924900B2 (en) 2016-02-04 2018-08-03 Charging method and apparatus, and system

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201610079306.XA CN107040674B (zh) 2016-02-04 2016-02-04 一种计费方法、装置及系统
CN201610079306.X 2016-02-04

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/054,615 Continuation US10924900B2 (en) 2016-02-04 2018-08-03 Charging method and apparatus, and system

Publications (1)

Publication Number Publication Date
WO2017133342A1 true WO2017133342A1 (zh) 2017-08-10

Family

ID=59500554

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/111517 WO2017133342A1 (zh) 2016-02-04 2016-12-22 一种计费方法、装置及系统

Country Status (4)

Country Link
US (1) US10924900B2 (zh)
EP (1) EP3402231B1 (zh)
CN (2) CN107040674B (zh)
WO (1) WO2017133342A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20200035141A (ko) * 2017-08-14 2020-04-01 후아웨이 테크놀러지 컴퍼니 리미티드 Cups 프로토콜에 기초한 오프라인 과금 레코드 임계값 제어 방법 및 시스템
RU2752247C1 (ru) * 2018-01-19 2021-07-23 Гуандун Оппо Мобайл Телекоммьюникейшнс Корп., Лтд. Способ и устройство для передачи информации посредством терминала и компьютерный носитель данных

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110138572B (zh) * 2018-02-09 2022-06-07 中国移动通信有限公司研究院 一种计费同步方法、装置及设备
CN112449317B (zh) * 2019-09-02 2022-06-10 华为技术有限公司 一种计费信息上报方法及装置
CN114765749A (zh) * 2021-01-15 2022-07-19 华为技术有限公司 对移动局域网业务进行计费处理的方法、系统及相关设备
CN113238982A (zh) * 2021-04-25 2021-08-10 深圳市广和通无线股份有限公司 数据通信方法、装置、计算机设备和存储介质
CN113747493B (zh) * 2021-09-17 2024-04-05 杭州阿里云飞天信息技术有限公司 数据传输方法、设备、系统及存储介质

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101374055A (zh) * 2007-08-20 2009-02-25 华为技术有限公司 计费处理方法和网络系统、分组数据网络网关及计费系统
CN102118729A (zh) * 2010-01-05 2011-07-06 中兴通讯股份有限公司 离线计费方法及装置
CN102209309A (zh) * 2010-03-30 2011-10-05 华为技术有限公司 流计费方法、装置和一种流计费系统
WO2015065701A1 (en) * 2013-10-31 2015-05-07 Intel IP Corporation Gateway arrangements for wireless communication networks
CN105515793A (zh) * 2014-09-23 2016-04-20 中国电信股份有限公司 在线计费处理方法和系统、Openflow控制器和Openflow交换机

Family Cites Families (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102859931A (zh) * 2010-01-12 2013-01-02 华为技术有限公司 一种计费方法、设备及系统
US9473986B2 (en) * 2011-04-13 2016-10-18 Interdigital Patent Holdings, Inc. Methods, systems and apparatus for managing and/or enforcing policies for managing internet protocol (“IP”) traffic among multiple accesses of a network
CN103517245B (zh) * 2012-06-21 2018-02-13 中兴通讯股份有限公司 一种d2d通信的计费方法和系统
WO2014000302A1 (zh) * 2012-06-30 2014-01-03 华为技术有限公司 一种网关计费处理方法及网关
CN104349298B (zh) * 2013-08-09 2019-07-02 中兴通讯股份有限公司 一种网络计费方法、控制器、数据中心及系统
CN103684802A (zh) * 2013-12-05 2014-03-26 大唐移动通信设备有限公司 离线计费的方法及设备
CN107547212A (zh) 2016-06-24 2018-01-05 中兴通讯股份有限公司 一种基于分离架构的计费方法、装置和系统

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101374055A (zh) * 2007-08-20 2009-02-25 华为技术有限公司 计费处理方法和网络系统、分组数据网络网关及计费系统
CN102118729A (zh) * 2010-01-05 2011-07-06 中兴通讯股份有限公司 离线计费方法及装置
CN102209309A (zh) * 2010-03-30 2011-10-05 华为技术有限公司 流计费方法、装置和一种流计费系统
WO2015065701A1 (en) * 2013-10-31 2015-05-07 Intel IP Corporation Gateway arrangements for wireless communication networks
CN105515793A (zh) * 2014-09-23 2016-04-20 中国电信股份有限公司 在线计费处理方法和系统、Openflow控制器和Openflow交换机

Non-Patent Citations (1)

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

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20200035141A (ko) * 2017-08-14 2020-04-01 후아웨이 테크놀러지 컴퍼니 리미티드 Cups 프로토콜에 기초한 오프라인 과금 레코드 임계값 제어 방법 및 시스템
EP3657730A4 (en) * 2017-08-14 2020-08-26 Huawei Technologies Co., Ltd. OFFLINE INVOICE RECORDING THRESHOLD CONTROL PROCESS AND SYSTEM BASED ON THE CUPS PROTOCOL
KR102351415B1 (ko) 2017-08-14 2022-01-17 후아웨이 테크놀러지 컴퍼니 리미티드 Cups 프로토콜에 기초한 오프라인 과금 레코드 임계값 제어 방법 및 시스템
RU2752247C1 (ru) * 2018-01-19 2021-07-23 Гуандун Оппо Мобайл Телекоммьюникейшнс Корп., Лтд. Способ и устройство для передачи информации посредством терминала и компьютерный носитель данных
US11363561B2 (en) 2018-01-19 2022-06-14 Guangdong Oppo Mobile Telecommunications Corp., Ltd. Method and apparatus for reporting information by terminal, and computer storage medium

Also Published As

Publication number Publication date
CN107040674A (zh) 2017-08-11
EP3402231B1 (en) 2022-09-28
EP3402231A4 (en) 2019-01-02
CN107040674B (zh) 2021-04-20
CN110634057B (zh) 2022-12-13
US20180343347A1 (en) 2018-11-29
EP3402231A1 (en) 2018-11-14
CN110634057A (zh) 2019-12-31
US10924900B2 (en) 2021-02-16

Similar Documents

Publication Publication Date Title
WO2017133342A1 (zh) 一种计费方法、装置及系统
EP2548119B1 (en) Diverse message synchronization
US8917615B2 (en) Method, apparatus and system for detecting service data of a packet data connection
US8995305B2 (en) Sy session creation and recovering from inconsistent session state between PCRF and OCS
EP2560430A1 (en) Method and system for obtaining network load
WO2017063427A1 (zh) 一种通信方法、装置及终端
US20140066004A1 (en) Handling of ocs counter information
CN109495857B (zh) 计费方法、移动边缘计算服务器、计费系统及策略控制规则网元
JP7379596B2 (ja) エンベロープ報告のサポート
WO2015131331A1 (zh) 一种计费会话管理方法、装置
US11206515B2 (en) Method and system for enhancing charging for co-located SGW and PGW
KR20150004893A (ko) 크레딧 초과 pcc 규칙의 일시적 디스에이블
WO2021136132A1 (zh) 报文处理方法及装置
WO2017148206A1 (zh) 一种计费方法和装置
CN106162733B (zh) 一种异常流量抑制方法及装置
US20140064183A1 (en) Fast acceptance of diameter peer failover
WO2009138016A1 (zh) 信息传递方法、装置和系统
KR20150039642A (ko) Lte 시스템에서의 ddn 제어를 위한 장치, 방법, 및 기록 매체
US8549116B2 (en) PCRF triggered rules cleanup
CN102439902A (zh) 本地路由业务的计费方法、装置及网络系统
WO2020173548A1 (en) Sx protocol extension to support pause measurement on user plane
TWI821882B (zh) 丟包率的檢測方法、通信裝置及通信系統
WO2017193303A1 (zh) 一种通信计费方法
WO2019007387A1 (en) BANDWIDTH SHARING BETWEEN A PLURALITY OF FLOWS

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

WWE Wipo information: entry into national phase

Ref document number: 2016889148

Country of ref document: EP

ENP Entry into the national phase

Ref document number: 2016889148

Country of ref document: EP

Effective date: 20180809