WO2016078392A1 - 一种计费方法、计费设备和计费系统 - Google Patents

一种计费方法、计费设备和计费系统 Download PDF

Info

Publication number
WO2016078392A1
WO2016078392A1 PCT/CN2015/080679 CN2015080679W WO2016078392A1 WO 2016078392 A1 WO2016078392 A1 WO 2016078392A1 CN 2015080679 W CN2015080679 W CN 2015080679W WO 2016078392 A1 WO2016078392 A1 WO 2016078392A1
Authority
WO
WIPO (PCT)
Prior art keywords
traffic
charging
linear
request
linear flow
Prior art date
Legal status (The legal status 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 status listed.)
Ceased
Application number
PCT/CN2015/080679
Other languages
English (en)
French (fr)
Inventor
杨恩锋
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
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 Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Priority to BR112017000054A priority Critical patent/BR112017000054A2/pt
Priority to EP15860086.6A priority patent/EP3145224A4/en
Publication of WO2016078392A1 publication Critical patent/WO2016078392A1/zh
Priority to US15/412,737 priority patent/US20170134178A1/en
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

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 specially adapted for data communications, e.g. authentication, authorisation and accounting [AAA] framework
    • 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 specially adapted for data communications, e.g. authentication, authorisation and accounting [AAA] framework
    • H04L12/141—Indication of costs
    • H04L12/1414—Indication of costs in real-time
    • 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 specially adapted for data communications, e.g. authentication, authorisation and accounting [AAA] framework
    • H04L12/1485—Tariff-related aspects
    • 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/81—Dynamic pricing, e.g. change of tariff during call
    • 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

Definitions

  • the present invention relates to a charging technology, and in particular, to a charging method, a charging device, and a charging system.
  • the 3rd Generation Partnership Project (3GPP) defines online charging.
  • the service monitoring and request is usually performed by a Gateway General Packet Radio Service Support Node (GGSN).
  • GGSN Gateway General Packet Radio Service Support Node
  • OCS Online Charging System
  • DCC Diameter Credit-Control
  • 3GPP began to define online charging for OCS, it emphasized the participation of billing for real-time services.
  • the rate control point (Tariff Time) was issued by credit control answer (CCA) message. Change, TTC), accurate accounting for traffic.
  • CCA credit control answer
  • FIG. 1 is an exemplary signaling diagram of an existing real-time charging method 100.
  • 8:00 is the rate switching point, ie rate switching will occur at 8:00.
  • step 102 the terminal user sends a login request to the GGSN.
  • Step 104 the GGSN sends an initial credit control request (CCR) to request to establish a bearer service and request OCS authorized traffic, with the size of the traffic requesting authorization.
  • CCR initial credit control request
  • step 106 the OCS performs authentication and reservation.
  • the OCS authenticates the rights of the terminal user and determines whether the terminal user has the right to use the bearer service established by the above request. If the end user has the right, the bearer service is established for it, and the authorized traffic reservation is made according to the account balance situation.
  • step 108 the OCS sends an initial credit control answer (CCA ⁇ Initial ⁇ ) to the GGSN with authorized traffic.
  • CCA ⁇ Initial ⁇ initial credit control answer
  • Step 110 After receiving the authorized traffic of the OCS, the GGSN provides services for the terminal user for use.
  • Step 112 When the user completes or is about to use the authorized traffic, the GGSN sends an update control request CCR ⁇ Update ⁇ to the OCS, and requests the next authorized traffic to the OCS, and simultaneously carries the CCR ⁇ Update ⁇ There is traffic that the user has used.
  • step 114 the OCS deducts the fee according to the traffic used by the user, and reserves a reservation for the next authorized traffic.
  • step 116 the OCS detects that the rate switching point is about to be encountered.
  • the CGS ⁇ Update ⁇ is sent to the GGSN with a rate switching point.
  • Step 118 When the user completes the use of the authorized traffic or is about to use, the GGSN sends a CCR ⁇ Update ⁇ to the OCS, requests the next authorized traffic to the OCS, and since the rate switching point is encountered, the GGSN will be in the CCR ⁇ Update ⁇
  • the usage traffic is divided into two parts by the rate switching point, and the usage traffic before and after the rate switching point is reported.
  • step 120 the OCS deducts the usage traffic before and after the rate switching point, and reserves the next authorized traffic, so that the user can continue to use the service. The subsequent steps are not described here.
  • the OCS deducts the fee according to the used traffic reported in the CCR during the charging.
  • the OCS can accurately calculate the usage traffic before and after the rate switching point. Fees will not cause billing errors due to changes in rates.
  • re-pricing is an essential billing system requirement. Since the 3GPP itself does not define the re-authentication service, it only supports the real-time charging of the Gy interface. Therefore, the re-pricing can only be based on the real-time traffic reported in the service process, that is, for example, the usage traffic in FIG. When the re-pricing design time node changes, there will be inaccuracies in re-rating.
  • the rate switching point in Figure 1 is at 8:00, then in normal real-time charging, OCS can realize the accuracy of charging because the GGSN reports traffic before 8:00 and traffic after 8:00.
  • the customer requests a re-pricing due to a package configuration error then there will be problems.
  • the customer reconfigured package rate switching point is at 9:00, but the OCS system cannot be obtained from the history. The traffic before 9:00 and the traffic after 9:00, the re-validation can not be completed.
  • the embodiment of the invention provides a charging method, which can enable the charging device to perform accurate charging according to the linear traffic information by reporting each piece of linear traffic information generated during the use of the authorized traffic.
  • the first aspect provides a charging method, where the terminal user initiates content access to generate traffic, the method includes: the access device sends a traffic request to the charging device; and the access device receives the charging device And the access device sends an accounting request to the charging device according to the usage of the authorized traffic by the terminal user, where the charging request carries the indication linearity a parameter of the traffic information, so that the charging device performs charging according to the linear traffic information; the linear traffic information is a related parameter of each linear traffic generated by the terminal user in using the authorized traffic.
  • the linear flow information includes a linear flow value per segment, a time at which each linear flow begins to be generated, and a duration of each linear flow.
  • the linear traffic information includes a rate of each linear traffic, a time when each linear traffic starts to be generated, and each time The duration of the segment linear flow.
  • the manner of obtaining the linear flow value includes: setting a timer, configuring a timing time, and when When the duration of the traffic is used to reach the timing, the access device acquires the used traffic size.
  • the manner of obtaining the linear traffic rate includes: setting a timer, configuring a timing time, when When the duration of the traffic reaches the timing, the access device acquires the used traffic size, and determines the linear traffic rate according to the used traffic size and the timing.
  • the traffic request and the charging request are a credit control request CCR message
  • the authorized traffic information is carried in a credit control response CCA message
  • the parameter indicating the linear traffic information is carried by an extended field or a reserved field in the CCR message.
  • the linear traffic value includes an uplink traffic value and a downlink traffic value, where the linear traffic rate is Includes upstream traffic rate and downstream traffic rate.
  • a second aspect provides a charging method for a terminal user to initiate content access to generate traffic.
  • the method includes the following steps: the charging device receives a traffic request sent by the access device; The traffic request returns the authorized traffic information to the access device; the charging device receives the charging request sent by the access device, where the charging request carries a parameter indicating linear traffic information, and the linear traffic information Used by the end user for the authorized traffic In the process, the relevant parameters of each piece of linear flow generated are generated; the charging device performs charging according to the linear flow information.
  • the linear flow information includes a linear flow value per segment, a time at which each linear flow begins to be generated, and a duration of each linear flow.
  • the linear traffic information includes a rate of each linear traffic, a time when each linear traffic starts to be generated, and each time The duration of the segment linear flow.
  • the performing charging according to the linear traffic information includes re-rating the traffic.
  • the charging request is a credit control request CCR, and the parameter indicating linear traffic information Carryed by an extension field or a reserved field in the credit control request.
  • the linear traffic value includes an uplink traffic value and a downlink traffic value, where the linear traffic rate is Includes upstream traffic rate and downstream traffic rate.
  • the third aspect provides an access device, where the terminal user initiates content access to generate traffic, including a sending module and a receiving module: the sending module is configured to send a traffic request to the charging device; the receiving module And receiving, by the charging device, the authorized traffic information returned according to the traffic request; the sending module is further configured to send the charging to the charging device according to the usage situation of the authorized traffic by the terminal user.
  • Requesting, the charging request carries a parameter indicating linear traffic information, so that the charging device performs charging according to the linear traffic information; and the linear traffic information is a process in which the terminal user is using the authorized traffic In the relevant parameters of each piece of linear flow generated.
  • the linear flow information includes a linear flow value per segment, a time at which each linear flow starts to be generated, and each segment The duration of the linear flow.
  • the linear traffic information includes a rate of each linear traffic, a time when each linear traffic starts to be generated, and each time The duration of the segment linear flow.
  • the manner of obtaining the linear flow value includes: setting a timer, configuring a timing time, and when When the duration of the traffic is used to reach the timing, the access device acquires the used traffic size.
  • the manner of obtaining the linear traffic rate includes: setting a timer, configuring a timing time, when When the duration of the traffic reaches the timing, the access device acquires the used traffic size, and determines the linear traffic rate according to the used traffic size and the timing.
  • the traffic request and the charging request are a credit control request CCR message
  • the authorized traffic information is carried in a credit control response CCA message
  • the parameter indicating the linear traffic information is carried by an extended field or a reserved field in the CCR message.
  • the linear traffic value includes an uplink traffic value and a downlink traffic value, where the linear traffic rate is Includes upstream traffic rate and downstream traffic rate.
  • the fourth aspect provides a charging device, where the terminal user initiates content access to generate traffic, including a receiving module, a sending module, and a charging module: the receiving module is configured to receive a traffic request sent by the access device.
  • the sending module is configured to return the authorized traffic information to the access device according to the traffic request;
  • the receiving module is further configured to receive a charging request sent by the access device, where the charging request is carried in the charging request a parameter indicating linear flow information, wherein the linear flow information is a related parameter of each linear flow generated in the process of using the authorized traffic by the end user;
  • the charging module is configured to use the linear flow according to the linear flow Information is billed.
  • the linear flow information includes a linear flow value per segment, a time at which each linear flow starts to be generated, and a duration of each linear flow.
  • the linear traffic information includes a rate of each linear traffic, a time when each linear traffic starts to be generated, and each time The duration of the segment linear flow.
  • the charging according to the linear traffic information includes re-authentication of traffic.
  • the charging request is a credit control request CCR
  • the parameter indicating linear traffic information It is carried by an extended field or a reserved field in the CCR message.
  • the linear traffic value includes an uplink traffic value and a downlink traffic value, where the linear traffic rate is Includes upstream traffic rate and downstream traffic rate.
  • a fifth aspect provides a charging system, including an access device and a charging device: the access device is configured to send a traffic request to the charging device, and receive the charging device according to the traffic request.
  • Authorizing the traffic information sending, according to the usage of the authorized traffic by the terminal user, a charging request to the charging device, where the charging request carries a parameter indicating linear traffic information, so that the charging device is based on The linear traffic information is used for charging; the linear traffic information is a related parameter of each linear traffic generated by the terminal user in the process of using the authorized traffic; the charging device is configured to receive the connection Receiving a traffic request sent by the device; returning the authorized traffic information to the access device according to the traffic request; receiving an accounting request sent by the access device, where the charging request carries the parameter indicating the linear traffic information Charging based on the linear traffic information.
  • a computing device comprising: 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 is in communication with the memory Passing through the bus connection, the processor executing the computer-executed instructions stored by the memory to cause the computing device to perform the first aspect to the second aspect and the first aspect to the first
  • the memory is configured to store a computing device to execute an instruction
  • the processor is in communication with the memory Passing through the bus connection, the processor executing the computer-executed instructions stored by the memory to cause the computing device to perform the first aspect to the second aspect and the first aspect to the first
  • the billing device obtains the detailed traffic usage situation by reporting the linear traffic information in the authorized traffic usage time, and can accurately backtrack the user at a certain moment according to the linear traffic information. Traffic usage, enabling accurate billing.
  • 1 is an exemplary signaling diagram of an existing real-time charging method
  • FIG. 2 is a schematic diagram of a network architecture applied to an embodiment of the present invention
  • FIG. 3 is an exemplary flowchart of a charging method according to an embodiment of the present invention.
  • FIG. 4 is an exemplary flowchart of a charging method according to an embodiment of the present invention.
  • FIG. 5 is an exemplary signaling diagram of a charging method according to an embodiment of the present invention.
  • FIG. 6 is a schematic diagram of linear flow information according to an embodiment of the invention.
  • FIG. 7 is a schematic structural diagram of an access device according to an embodiment of the present invention.
  • FIG. 8 is a schematic structural diagram of a charging device according to an embodiment of the present invention.
  • FIG. 9 is a schematic structural diagram of a charging system according to an embodiment of the present invention.
  • FIG. 10 is a block diagram showing the hardware structure of a general-purpose computer structure according to an embodiment of the invention.
  • Network architecture 200 includes policies And a Policy and Charging Rule Function (PCRF), a Policy and Charging Enforcement Function (PCEF) 2041, an Application Function (AF), and a User Contracting Database 208.
  • PCRF Policy and Charging Rule Function
  • PCEF Policy and Charging Enforcement Function
  • AF Application Function
  • AF User Contracting Database 208.
  • SPR Policy and Charging Rule Function
  • BBERF Bearer Binding and Event Report Function
  • TDF Traffic Detection Function
  • OCS214 Offline Charging System 216
  • OFCS Offline Charging System
  • the PCRF 202 includes a policy control decision and a flow-based charging control function.
  • the PCRF 202 receives an input from the PCEF 2041 through the Gx interface, and provides the PCEF 2041 with service data flow detection, Gating Control, and Quality of Service (QoS). Control and network charging based on flow accounting.
  • the PCRF 202 sends its formulated policies and charging rules to the PCEF 2041 for execution. At the same time, the PCRF 202 also needs to ensure that these rules are consistent with the user's subscription information.
  • the PCRF 202 formulates the policy and the charging rule according to the following: the information about the service is obtained from the AF 206; the subscription information of the user policy charging control is obtained from the SPR 208; and the information about the network related to the bearer is obtained from the PCEF 2041.
  • PCEF2041 mainly includes detection of service data flows, policy enforcement, and flow-based charging functions.
  • the PCEF2041 functional entity is usually located in the gateway 204 (Gateway, GW), such as a GGSN gateway, a packet data network gateway (P-GW) of a 4G core network (EPC), and a wireless local area network (Wireless Local Area). Packet Data Gateway (PDG) in Network, WLAN).
  • GW Gateway
  • GGSN gateway packet data network gateway
  • P-GW packet data network gateway
  • EPC 4G core network
  • WLAN wireless local area network
  • the PCEF2041 can also be deployed independently.
  • the BBERF210 features include bearer bonding, authentication of upstream bearer bindings, and event reporting.
  • the functional entity is located in the gateway, for example, based on the S5/S8 interface, using Proxy Mobile IP (PMIP), implementing a service gateway (S-GW) for 3GPP access, and high-speed packet data (High Rate Packet Data) HRPD service gateway in HRPD), access gateway (A-GW) in non-3G access occasions.
  • PMIP Proxy Mobile IP
  • S-GW service gateway
  • HRPD High Rate Packet Data
  • A-GW access gateway
  • the TDF 212 performs application detection and report detection. For example, TDF212 can recognize depth Deep packet inspection (DPI). If the TDF 212 does not detect this information, then the TDF 212 performs gating to redirect the bandwidth limit. If the application information can be detected, it is submitted to the PCRF 202, and the PCRF 202 generation decision is performed by the PCEF 2041.
  • DPI depth Deep packet inspection
  • the OCS214 provides credit control based on user and business data streams. It is mainly composed of modules such as online collection, billing control, pricing, and balance management. It implements the online charging function and cooperates with other charging network element devices (triggering session-based, event-based online charging event requesting devices, such as SCP, CCG, ISMP, etc.) perform real-time traffic control. Connected to the PCEF2041 through the Gy interface.
  • the OFCS216 and the PCEF2041 complete the charging operation in the offline charging mode.
  • the PCEF is considered to be located in the gateway GGSN.
  • the charging method 300 may be performed by, for example, but not limited to, an access device, which may be, for example, but not limited to, a GGSN.
  • the charging device and the access device communicate according to a Diameter protocol.
  • the access device sends a traffic request to the charging device.
  • the traffic request can be a CCR message.
  • the access device receives the authorized traffic information that is returned by the charging device according to the traffic request, where the “authorized traffic information returned by the charging device according to the traffic request” is specifically: the charging device is configured according to The message returned by the traffic request carries a parameter indicating the authorized traffic information.
  • the message carrying the authorized traffic information may be a CCA message, where the message carrying the parameter indicating the authorized traffic information may be a CCA message.
  • the access device sends a charging request to the charging device according to the usage of the authorized traffic by the terminal user, where the charging request carries a parameter indicating linear traffic information, so that the charging device And charging according to the linear traffic information; the linear traffic information is a related parameter of each piece of linear traffic generated by the terminal user in using the authorized traffic.
  • the linear flow information includes a linear flow value for each segment, a time at which each linear flow begins to be generated, and a duration of each linear flow, the linear flow value per segment being a linear flow value for each linear flow.
  • the linear flow information includes a rate of each linear flow, a time at which each linear flow starts to be generated, and a duration of each linear flow, and the rate of each linear flow refers to a flow rate of each linear flow.
  • the method for obtaining the linear traffic value includes setting a timer and configuring a timing time.
  • the access device obtains the used traffic.
  • the method for obtaining the linear traffic rate includes setting a timer, and configuring a timing time.
  • the access device obtains the used traffic size, according to the used traffic size and The timing time determines the linear flow rate.
  • the linear flow rate refers to the flow rate of the above linear flow.
  • the charging request is a CCR message, where the parameter indicating the linear traffic information is carried by an extended field or a reserved field in the CCR message, where the parameter indicating the linear traffic information passes the CCR message.
  • the extension field is carried or carried by a reserved field in the CCR message.
  • the billing device obtains the detailed traffic usage situation by reporting the linear traffic information in the authorized traffic usage time, and can accurately backtrack the user at a certain moment according to the linear traffic information. Traffic usage, enabling accurate billing.
  • the charging method 400 can be performed by, for example, but not limited to, a billing device.
  • the charging device may be, for example but not limited to, a Pre-Paid Server (PPS).
  • PPS Pre-Paid Server
  • the prepaid server may be specifically, for example but not limited to, an OCS.
  • the charging device receives a traffic request sent by the access device.
  • the charging device returns the authorized traffic information to the access device according to the traffic request, where the charging device returns the authorized traffic information to the access device according to the traffic request, specifically: the charging The device returns, according to the traffic request, a message carrying a parameter indicating the authorized traffic information to the access device.
  • the charging device receives the charging request sent by the access device, where the charging request carries a parameter indicating linear traffic information, where the linear traffic information is that the terminal user is using the authorization. In the process of flow, the relevant parameters of each piece of linear flow are generated.
  • the linear flow information includes a linear flow value per segment, a time at which each linear flow starts to be generated, and a duration of each linear flow, the linear flow value being a linear flow value of each linear flow.
  • the linear flow information includes a rate of each linear flow, a time at which each linear flow starts to be generated, and a duration of each linear flow, and the rate of each linear flow refers to a flow rate of each linear flow.
  • the charging device performs charging according to the linear traffic information.
  • charging according to the linear traffic information includes re-rating the traffic.
  • the billing device obtains the detailed traffic usage situation by reporting the linear traffic information in the authorized traffic usage time, and can accurately backtrack the user at a certain moment according to the linear traffic information. Traffic usage, enabling accurate billing.
  • FIG. 5 is an exemplary signaling diagram of a charging method in accordance with an embodiment of the present invention.
  • the charging method 500 can be performed by, for example, but not limited to, an access device and a charging device.
  • the access device may be, for example but not limited to, a GGSN.
  • the billing device may be, for example but not limited to, a PPS.
  • the prepaid server may be specifically, for example but not limited to, an OCS.
  • the access device communicates with the charging device according to a Diameter protocol.
  • a Diameter protocol In FIG.
  • the GGSN sends a CCR message requesting the OCS to authorize the traffic; the OCS sends the authorized traffic to the GGSN through the CCA message according to the CCR message; the GGSN provides the service to the terminal user after receiving the authorized traffic of the OCS, and the terminal user uses the Authorized traffic.
  • the linear traffic information is generated by the end user in the process of using the authorized traffic, and the GGSN reports the linear traffic information to the OCS through the CCR message, and the OCS performs charging according to the linear traffic information.
  • the GGSN sends a CCR message to the OCS, where the CCR message is a traffic request for requesting OCS authorized traffic.
  • the OCS sends a CCA message to the GGSN, where the authorized traffic information is carried.
  • the OCS authorizes the traffic requested by the GGSN in combination with the account balance of the end user. Specifically, when the account balance of the terminal user is sufficient to pay the traffic requested by the GGSN, the following two methods are included.
  • Authorize :
  • the OCS authorizes the traffic requested by the GGSN
  • the second type determines the authorized traffic according to the internal policy, and dynamically adjusts the authorized traffic according to the network, the network speed, and the package purchased by the user.
  • the authorized traffic is not necessarily the same as the traffic requested by the GGSN. .
  • the traffic that his account balance can be authorized is authorized.
  • the terminal user generates linear traffic information in the process of using the authorized traffic, and the GGSN sends the linear traffic information to the OCS through a CCR message.
  • the OCS performs charging according to the linear traffic information.
  • the OCS can accurately reclaim the traffic usage based on the linear traffic information and re-price the traffic.
  • the traffic rate is not necessarily constant during the process of using the service, for example, accessing the Internet. Therefore, when the authorized traffic is used, different traffic rates may occur in different time periods. .
  • the traffic rate is 1M in the period from 6:00 to 6:05. /S
  • the flow rate is 0.5M/S in the 6:05 to 6:10 period
  • the flow rate is 0M/S in the 6:10 to 6:15 period, from 6:15 to 6:20
  • the flow rate is 0.5 M/S.
  • the continuous time with the same flow rate is a linear flow segment.
  • the time range from 6:00 to 6:05 in the flow rate of 1 M/S in Fig. 6 is a linear flow segment.
  • the total amount of flow in the linear flow segment is called the linear flow value.
  • This continuous time is referred to as the duration of the linear flow of the segment, Phase-Duration.
  • 5 minutes is the duration of the linear flow of the segment.
  • the starting time of the duration is called the time Start-Time at which the linear flow of the segment starts to be generated.
  • the linear flow segment in FIG. 6 is 6:00 to 6:05, and 6:00 is the time at which the linear flow starts to be generated. .
  • the GGSN sends the linear traffic information of each linear traffic segment to the OCS.
  • the linear traffic information of each linear traffic segment includes but is not limited to any of the following two situations:
  • the first type includes a linear flow value, a time Start-Time at which the linear flow starts to be generated, and a duration Phase-Duration of the linear flow, wherein the linear flow includes an upstream flow Output-Quota and a downstream flow Input-Quota.
  • the GGSN can upload the total amount of the upstream traffic Output-Quota and the downstream traffic Input-Quota, and can also upload the upstream traffic Output-Quota and the downstream traffic Input-Quota as two data, wherein "the GGSN can upload the upstream traffic Output-Quota and The total amount of the downstream traffic Input-Quota can also be used to upload the upstream traffic Output-Quota and the downstream traffic Input-Quota as two data. Specifically, the GGSN can upload the total traffic value of the upstream traffic value and the downstream traffic value, or The upstream traffic value and the downstream traffic value are uploaded as two data.
  • the second type includes a linear flow rate, a time Start-Time at which the linear flow starts to be generated, and a duration Phase-Duration of the linear flow, wherein the linear flow rate includes an upstream flow rate Output-Quota-Ratio and a downstream flow rate.
  • Input-Quota-Ratio The GGSN may upload the sum rate of the uplink traffic rate Output-Quota-Ratio and the downlink traffic rate Input-Quota-Ratio, or upload the uplink traffic rate Output-Quota-Ratio and the downlink traffic rate Input-Quota-Ratio as two data.
  • the linear flow rate refers to the flow rate of the linear flow segment.
  • the timer can be configured to set the timing time.
  • the size of the used traffic is obtained to determine the linear traffic or the linear traffic rate.
  • the timing can be set to the OCS.
  • the time is set to 1 second.
  • the GGSN obtains the used traffic size.
  • the duration of each linear flow is the same as Phase-Duration, and Phase-Duration is equal to 1 second.
  • the GGSN acquires the usage traffic amount within the one second every 1 second, and sends the usage traffic size, the time at which the usage traffic starts to be generated, and the duration of 1 second to the OCS.
  • the traffic usage size includes upstream traffic and downstream traffic
  • the GGSN can upload upstream traffic and downstream traffic.
  • the total amount that is, the usage traffic amount within 1 second, can also upload the upstream traffic and the downstream traffic as two data.
  • the timing can be determined by the operator. Due to different timings, there may be an error between the traffic acquired by the GGSN and the traffic actually used by the user during the timing, and the operator can according to the error range that the operator can accept.
  • the present invention sets the timing to 1 second only to provide a feasible way, and is not intended to limit the scope of the present invention.
  • the Phase-Duration is different due to different timing times, and the timing is long, such as the timing time. For 5 minutes, the flow rate within the Phase-Duration may not be constant, so there may be an error between the timing as the duration of the linear flow segment and the duration of the true linear flow segment.
  • the multiple timing times may be combined as the duration of a linear traffic segment Phase-Duration, the combined duration Phase-Duration, and the merged
  • the total amount of traffic generated in the Phase-Duration and the time Start-Time at the beginning of the first of the plurality of timing times are reported to the OCS. For example, if the timing is 1 second, the GGSN acquires the usage traffic every 1 second. In 10 consecutive 1 seconds, the usage traffic per 1 second is 1M, and the usage traffic in the 11th 1 second is not For 1M, the 10 1 seconds can be combined into 10 seconds.
  • the 10 seconds is the duration of a linear flow segment, Phase-Duration, and the linear flow segment has a total linear flow of 10M. If the start time of the first 1 second of the 10 1 seconds is 6:00, the Start-Time of the linear traffic segment is 6:00. The GGSN will send information indicating 10 seconds, 10M, and 6:00 to the OCS through the CCR message. The Start-Time of the first timing time is equivalent to reporting the combined linear traffic of the first timing time. The Start-Time of the segment.
  • the timing time is set to 1 second for the GGSN to send the above-mentioned second type of linear traffic information, that is, to send the linear traffic rate, the time Start-Time at which each linear traffic starts to be generated, and the duration of each linear traffic to the OCS.
  • the GGSN obtains the usage traffic every 1 second, and the usage traffic obtained by the GGSN is the linear traffic rate. If the rate is the same for a few seconds, for example, a few seconds in a row
  • the rate is 1M/S, and these seconds can be combined as the duration of a linear traffic segment Phase-Duration, the combined duration Phase-Duration, the flow rate during the duration, and the time at which the duration begins.
  • the Start-Time is reported to the OCS.
  • the GGSN obtains the usage traffic every 1 second to obtain the traffic rate.
  • the traffic rate is always 1M/S for 10 consecutive seconds, and the traffic rate for the 11th second is not 1M/S.
  • the first 10 seconds can be combined.
  • the 10 seconds is the duration of a linear flow segment, Phase-Duration, and the linear flow rate of the linear flow segment is 1 M/S. If the starting time of the 10 seconds is 6:00, the Start-Time of the linear traffic segment is 6:00.
  • the GGSN sends information indicating 10 seconds, 1 M/S, 6:00 to the OCS through the CCR message.
  • the traffic rate per second can also be reported to the GGSN.
  • the Phase-Duration is not reported, and the reported linear traffic information is a linear traffic rate and a Start-Time at which each linear traffic starts to be generated.
  • the linear traffic segment that does not generate traffic is not reported.
  • the linear traffic segment that generates traffic is reported, for example, 6:00 in Figure 6.
  • no flow generated means that the flow is not consumed, and “generated flow” refers to the consumed flow.
  • the parameters indicating the linear traffic value, the linear traffic rate, the time at which each linear traffic starts to be generated, and the duration of each linear traffic can be carried by extending the field in the CCR message, or through the CCR.
  • the reserved field in the message is carried.
  • the following fields are extended in the CCR to report linear flow values, the time at which each linear flow begins to be generated, and the duration of each linear flow:
  • the GGSN sends the pieces of linear traffic information together to the OCS in the CCR message requesting the next authorized traffic.
  • the rate switching point during normal billing is at 5:00, but because of the package configuration error, the reconfigured package rate switching point is At 6:08, since the GGSN reports linear traffic information with a Start-Time of 6:05, a Phase-Duration of 5 minutes, and a flow rate of 0.5 M/S, the rate switching point can be calculated before 6:08.
  • the same method can be used to calculate the flow before 6:05 and after 6:10, 6:
  • the traffic before 05 plus the traffic from 6:05 to 6:08 will get the traffic before the rate switching point of 6:08, and the traffic after 6:10 plus the time range of 6:08 to 6:10.
  • the traffic gets the traffic after the rate switch point of 6:08, so the backtracking of the traffic usage is realized.
  • the cost generated by using the traffic before and after 6:08 can be obtained.
  • the traffic can be re-patented.
  • the billing device obtains the detailed traffic usage situation by reporting the linear traffic information in the authorized traffic usage time, and can accurately backtrack the user at a certain moment according to the linear traffic information.
  • the traffic usage can be accurately charged.
  • FIG. 7 is a schematic structural diagram of an access device according to an embodiment of the invention.
  • the access device is configured to perform the charging method in the foregoing embodiment of FIG. 3.
  • the access device 700 includes a transmitting module 702 and a receiving module 704.
  • the sending module 702 is configured to send a traffic request to the charging device.
  • the receiving module 704 is configured to receive authorized traffic information returned by the charging device according to the traffic request.
  • the sending module 702 is further configured to send a charging request to the charging device according to the usage of the authorized traffic by the terminal user, where the charging request carries a parameter indicating linear traffic information, where The billing device performs charging according to the linear traffic information; the linear traffic information is a related parameter of each piece of linear traffic generated by the terminal user in the process of using the authorized traffic.
  • the linear flow information includes a linear flow value for each segment, a time at which each linear flow begins to be generated, and a duration of each linear flow.
  • the linear traffic value can be obtained by setting a timer and configuring a timing time.
  • the access device acquires the used traffic.
  • the linear flow information includes the rate of each linear flow, the time at which each linear flow begins to be generated, and the duration of each linear flow.
  • the linear traffic rate can be obtained by setting a timer and configuring a timing.
  • the access device obtains the used traffic, according to the used traffic. And the timing time, the linear flow rate is determined.
  • the billing device obtains the detailed traffic usage situation by reporting the linear traffic information in the authorized traffic usage time, and can accurately backtrack the user at a certain moment according to the linear traffic information. Traffic usage, enabling accurate billing.
  • FIG. 8 is a schematic structural diagram of a charging device according to an embodiment of the present invention.
  • the charging device is configured to perform the charging method in the foregoing embodiment of FIG. 4.
  • the charging device 800 includes a receiving module 802, a transmitting module 804, and a charging module 806.
  • the receiving module 802 is configured to receive a traffic request sent by the access device.
  • the sending module 804 is configured to return, according to the traffic request, authorized traffic information to the access device.
  • the receiving module 802 is further configured to receive a charging request sent by the access device, where the charging request carries a parameter indicating linear traffic information, where the linear traffic information is used by the terminal user to use the authorized traffic. In the process, the relevant parameters of each piece of linear flow are generated.
  • the charging module 806 is configured to perform charging according to the linear traffic information.
  • the linear flow information includes a linear flow value for each segment, a time at which each linear flow begins to be generated, and a duration of each linear flow.
  • the linear flow information includes the rate of each linear flow, the time at which each linear flow begins to be generated, and the duration of each linear flow.
  • the billing device obtains the detailed traffic usage situation by reporting the linear traffic information in the authorized traffic usage time, and can accurately backtrack the user at a certain moment according to the linear traffic information. Traffic usage, enabling accurate billing.
  • FIG. 9 is a schematic structural diagram of a charging system according to an embodiment of the present invention.
  • the billing system 900 includes an access device 902 and a billing device 904.
  • the access device 902 is configured to send a traffic request to the charging device, and receive the authorized traffic information returned by the charging device according to the traffic request; and according to the usage of the authorized traffic by the terminal user, The charging device sends a charging request, where the charging request carries a parameter indicating linear traffic information, so that the charging device performs charging according to the linear traffic information; the linear traffic information is used by the terminal user.
  • the charging device 904 is configured to receive the traffic request sent by the access device, return the authorized traffic information to the access device according to the traffic request, and receive the charging request sent by the access device, where the charging is performed.
  • the request carries the parameter indicating the linear traffic information; charging is performed according to the linear traffic information.
  • the information that the charging device returns the authorized traffic information according to the traffic request is specifically: the message that the charging device returns, according to the traffic request, carrying a parameter indicating the authorized traffic information.
  • the billing device obtains the detailed traffic usage situation by reporting the linear traffic information in the authorized traffic usage time, and can accurately backtrack the user at a certain moment according to the linear traffic information. Traffic usage, enabling accurate billing.
  • FIG. 10 is a block diagram showing the hardware structure of a general purpose computer architecture 1000 in accordance with an embodiment of the present invention.
  • a general purpose computer architecture 1000 includes a processor 1002, a memory 1004, a communication interface 1006, and a bus 1008.
  • the processor 1002, the memory 1004, and the communication interface 1006 implement a communication connection with each other through the bus 1008.
  • the processor 1002 may 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 1004 may be a read only memory (ROM), a static storage device, a dynamic storage device, or a random access memory (RAM).
  • the memory 1004 can store an operating system and other applications.
  • the program code for implementing the technical solution provided by the embodiment of the present invention is saved in the memory 1004 and executed by the processor 1002.
  • Communication interface 1006 implements communication with other devices or communication networks using transceivers such as, but not limited to, transceivers.
  • Bus 1008 can include a path for communicating information between various components (e.g., processor 1002, memory 1004, input and communication interface 1006).
  • the processor 1002 when retrieving the instructions in the memory 1004, includes:
  • the processor 1002 controls the communication interface 1006 to send a traffic request to the charging device.
  • the processor 1002 controls the communication interface 1006 to receive the authorized traffic information returned by the charging device according to the traffic request.
  • the processor 1002 controls the communication interface 1006 to send a charging request to the charging device according to the usage of the authorized traffic by the terminal user, where the charging request carries a parameter indicating linear traffic information, so that the The fee device performs charging according to the linear traffic information; the linear traffic information is a related parameter of each linear traffic generated by the terminal user in using the authorized traffic.
  • the processor 1002 when retrieving the instructions in the memory 1004, includes:
  • the processor 1002 controls the communication interface 1006 to receive a traffic request sent by the access device.
  • the processor 1002 controls the communication interface 1006 to return authorized traffic information to the access device according to the traffic request.
  • the processor 1002 controls the communication interface 1006 to receive the charging request sent by the access device, where the charging request carries a parameter indicating linear traffic information, where the linear traffic information is that the terminal user is using the authorized traffic. In the process, the relevant parameters of each piece of linear flow are generated. The processor 1002 performs charging according to the linear traffic information.
  • the general purpose computer structure 1000 shown in FIG. 10 only shows the processor 1002, the memory 1004, the communication interface 1006, and the bus 1008, in the specific implementation process, those skilled in the art should understand that the above access device And the billing device also contains other devices necessary to achieve normal operation.
  • the above access device and charging device may also include hardware devices that implement other additional functions.
  • the access device and the charging device described above may also only include the devices necessary to implement the embodiments of the present invention, and do not necessarily include all of the devices shown in FIG.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Meter Arrangements (AREA)

Abstract

本发明实施例提供了一种计费方法、计费设备和计费系统。计费方法包括接入设备发送流量请求给计费设备；所述接入设备接收所述计费设备根据所述流量请求返回的授权流量信息；所述接入设备根据所述终端用户对所述授权流量的使用情况，向所述计费设备发送计费请求，所述计费请求中携带指示线性流量信息的参数，以便所述计费设备依据所述线性流量信息进行计费；所述线性流量信息为所述终端用户在使用所述授权流量过程中，产生的每段线性流量的相关参数。根据本发明实施例提供的技术方案，通过上报授权流量使用时间内的每段线性流量信息，使得计费设备能够依据该线性流量信息准确的回溯用户在某一时刻的流量使用情况，从而能够进行准确的计费。

Description

一种计费方法、计费设备和计费系统
本申请要求于2014年11月17日提交中国专利局、申请号为201410654552.4，发明名称为“一种计费方法、计费设备和计费系统”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本发明涉及计费技术，尤其涉及一种计费方法、计费设备和计费系统。
背景技术
第三代合作伙伴计划(3rd Generation Partnership Project，3GPP)定义了在线计费。通常由分组无线业务网关支持节点(Gateway General Packet Radio Service Support Node，GGSN)执行业务监控和请求。GGSN通过Gy接口与在线计费系统(Online Charging System，OCS)通过直径信用控制(Diameter Credit-Control，DCC)消息进行交互，以完成数据业务的计费。3GPP从开始定义OCS在线计费的时候，强调的是计费对实时业务的参与，在业务进行的过程中，通过信用控制应答(credit control answer，CCA)消息下发费率切换点(Tariff Time change，TTC)，对流量做准确计费。下面结合图1对现有的实时计费技术进行说明。
图1是现有实时计费方法100的示范性信令图。在图1所示的场景中，8:00为费率切换点，即在8:00时将发生费率切换。
步骤102，终端用户向GGSN发出登录请求。
步骤104，GGSN发送初始信用控制请求(credit control request)CCR{Initial}，请求建立承载业务和请求OCS授权流量，其中带有请求授权的流量大小。
步骤106，OCS进行鉴权和预留。
OCS鉴定终端用户的权限，确定该终端用户是否有权限使用上述请求建立的承载业务。如果该终端用户有权限，则为其建立该承载业务，并依据其账户余额情况做出授权流量预留。
步骤108，OCS发送初始信用控制应答(credit control answer)CCA{Initial}给GGSN，其中带有授权流量。
步骤110，GGSN接收到OCS的授权流量后，为终端用户提供业务供其使用。
步骤112，在用户将上述授权流量使用完成或即将使用完成时，GGSN发送更新信用控制请求(credit control request)CCR{Update}给OCS，向OCS请求下一个授权流量，CCR{Update}中同时带有用户已使用的流量。
步骤114，OCS根据用户已使用的流量进行扣费，并对下一个授权流量做出预留。
步骤116，OCS检测到即将遇到费率切换点，在发送更新信用控制应答(credit control answer)CCA{Update}给GGSN中除带有授权流量外，还带有费率切换点。
步骤118，在用户将授权流量使用完成或即将使用完成时，GGSN发送CCR{Update}给OCS，向OCS请求下一个授权流量，并且由于遇到了费率切换点，GGSN在CCR{Update}中将使用流量以费率切换点为界分成两部分，上报费率切换点前后的使用流量。
步骤120，OCS根据费率切换点前后的使用流量进行扣费，并对下一个授权流量进行预留，以便用户继续使用业务。在此不再对后续步骤进行描述。
OCS在计费时依据CCR中上报的使用流量进行扣费，步骤118中，由于GGSN上报了费率切换点前后的使用流量，OCS就能够依据该费率切换点前后的使用流量进行准确的计费，不会因为费率发生变化而导致计费错误。
然而，有时会出现资费处理错误导致给用户计费错误的情况，需要重新按用户的实际使用业务情况进行扣费，即重新批价，达到计费准确的目的。但是3GPP从未支持重新批价，在整个3GPP规范中，都未提及重新批价的 处理，通信设备商一般也不对重新批价进行支持。通常的做法，是在资费上线前，通过模拟资费或者严格测试来保证上线后资费的准确性，尽量避免重新批价。但是实际上，随着在线计费系统的应用越来越广，在很多计费支撑系统(Billing support system，BSS)局点中，在线计费系统已经是全网预付费和后付费用户统一的支撑系统了，而对于脱胎于电信管理论坛组织(Tele Management Forum，TMF)的后付费系统来说，重新批价是必不可少的计费系统要求。由于3GPP本身不定义重新批价业务，只支持Gy接口的实时计费，因此重新批价只能基于业务过程中上报的实时流量，即例如图1中的使用流量。当重新批价设计时间节点变更时，重新批价就会存在不准确的情况。例如，图1中的费率切换点在8:00，那么在正常实时计费时，由于GGSN上报了8:00之前的流量和8:00点之后的流量，OCS能够实现计费的准确性；但是在某些场景下，如果客户因为套餐配置出错，要求重新批价，那么就会出现问题，例如客户重新配置的套餐费率切换点在9:00，但是OCS系统从历史记录中无法得到9:00之前的流量和9:00之后的流量，重新批价就无法完成了。
发明内容
本发明实施例提供了一种计费方法，通过上报授权流量使用过程中产生的每段线性流量信息，使得计费设备能够依据该线性流量信息进行准确的计费。
第一方面，提供了一种计费方法，用于终端用户发起内容访问产生流量的情况，所述方法包括接入设备发送流量请求给计费设备；所述接入设备接收所述计费设备根据所述流量请求返回的授权流量信息；所述接入设备根据所述终端用户对所述授权流量的使用情况，向所述计费设备发送计费请求，所述计费请求中携带指示线性流量信息的参数，以便所述计费设备依据所述线性流量信息进行计费；所述线性流量信息为所述终端用户在使用所述授权流量过程中，产生的每段线性流量的相关参数。
结合第一方面的实现方式，在第一方面第一种可能的实现方式中，所述线性流量信息包括每段线性流量值、开始产生每段线性流量的时刻以及每段线性流量的持续时间。
结合第一方面、第一方面的第一种可能的实现方式，在第二种可能实现的方式中，所述线性流量信息包括每段线性流量的速率、开始产生每段线性流量的时刻以及每段线性流量的持续时间。
结合第一方面、第一方面的第一种至第二种可能的实现方式，在第三种可能实现的方式中，所述线性流量值的获得方式包括：设置定时器，配置定时时间，当使用流量的时长达到定时时间时，所述接入设备获取已使用的流量大小。
结合第一方面、第一方面的第一种至第三种可能的实现方式，在第四种可能实现的方式中，所述线性流量速率的获得方式包括：设置定时器，配置定时时间，当使用流量的时长达到定时时间时，所述接入设备获取已使用的流量大小，根据所述已使用的流量大小和所述定时时间，确定所述线性流量速率。
结合第一方面、第一方面的第一种至第四种可能的实现方式，在第五种可能实现的方式中，所述流量请求和所述计费请求为信用控制请求CCR消息，所述授权流量信息携带在信用控制应答CCA消息中，所述指示线性流量信息的参数通过CCR消息中的扩展字段或保留字段携带。
结合第一方面、第一方面的第一种至第五种可能的实现方式，在第六种可能实现的方式中，所述线性流量值包括上行流量值和下行流量值，所述线性流量速率包括上行流量速率和下行流量速率。
第二方面，提供了一种计费方法，用于终端用户发起内容访问产生流量的情况，所述方法包括以下步骤：计费设备接收接入设备发送的流量请求；所述计费设备根据所述流量请求返回授权流量信息给所述接入设备；所述计费设备接收所述接入设备发送的计费请求，所述计费请求中携带指示线性流量信息的参数，所述线性流量信息为所述终端用户在使用所述授权流量的过 程中，产生的每段线性流量的相关参数；所述计费设备依据所述线性流量信息进行计费。
结合第二方面的实现方式，在第二方面第一种可能的实现方式中，所述线性流量信息包括每段线性流量值、开始产生每段线性流量的时刻以及每段线性流量的持续时间。
结合第二方面、第二方面的第一种可能的实现方式，在第二种可能实现的方式中，所述线性流量信息包括每段线性流量的速率、开始产生每段线性流量的时刻以及每段线性流量的持续时间。
结合第二方面、第二方面的第一种至第二种可能的实现方式，在第三种可能实现的方式中，所述依据所述线性流量信息进行计费包括流量重新批价。
结合第二方面、第二方面的第一种至第三种可能的实现方式，在第四种可能实现的方式中，所述计费请求为信用控制请求CCR，所述指示线性流量信息的参数通过所述信用控制请求中的扩展字段或保留字段携带。
结合第二方面、第二方面的第一种至第四种可能的实现方式，在第五种可能实现的方式中，所述线性流量值包括上行流量值和下行流量值，所述线性流量速率包括上行流量速率和下行流量速率。
第三方面，提供了一种接入设备，用于终端用户发起内容访问产生流量的情况，包括发送模块和接收模块：所述发送模块，用于发送流量请求给计费设备；所述接收模块，用于接收所述计费设备根据所述流量请求返回的授权流量信息；所述发送模块还用于根据所述终端用户对所述授权流量的使用情况，向所述计费设备发送计费请求，所述计费请求中携带指示线性流量信息的参数，以便所述计费设备依据所述线性流量信息进行计费；所述线性流量信息为所述终端用户在使用所述授权流量的过程中，产生的每段线性流量的相关参数。
结合第三方面的实现方式，在第三方面第一种可能的实现方式中，所述线性流量信息包括每段线性流量值、开始产生每段线性流量的时刻以及每段 线性流量的持续时间。
结合第三方面、第三方面的第一种可能的实现方式，在第二种可能实现的方式中，所述线性流量信息包括每段线性流量的速率、开始产生每段线性流量的时刻以及每段线性流量的持续时间。
结合第三方面、第三方面的第一种至第二种可能的实现方式，在第三种可能实现的方式中，所述线性流量值的获得方式包括：设置定时器，配置定时时间，当使用流量的时长达到定时时间时，所述接入设备获取已使用的流量大小。
结合第三方面、第三方面的第一种至第三种可能的实现方式，在第四种可能实现的方式中，所述线性流量速率的获得方式包括：设置定时器，配置定时时间，当使用流量的时长达到定时时间时，所述接入设备获取已使用的流量大小，根据所述已使用的流量大小和所述定时时间，确定所述线性流量速率。
结合第三方面、第三方面的第一种至第四种可能的实现方式，在第五种可能实现的方式中，所述流量请求和所述计费请求为信用控制请求CCR消息，所述授权流量信息携带在信用控制应答CCA消息中，所述指示线性流量信息的参数通过CCR消息中的扩展字段或保留字段携带。
结合第三方面、第三方面的第一种至第五种可能的实现方式，在第六种可能实现的方式中，所述线性流量值包括上行流量值和下行流量值，所述线性流量速率包括上行流量速率和下行流量速率。
第四方面，提供了一种计费设备，用于终端用户发起内容访问产生流量的情况，包括接收模块，发送模块和计费模块：所述接收模块，用于接收接入设备发送的流量请求；所述发送模块，用于根据所述流量请求返回授权流量信息给所述接入设备；所述接收模块还用于接收所述接入设备发送的计费请求，所述计费请求中携带指示线性流量信息的参数，所述线性流量信息为在所述终端用户使用所述授权流量的过程中，产生的每段线性流量的相关参数；所述计费模块，用于依据所述线性流量信息进行计费。
结合第四方面的实现方式，在第四方面第一种可能的实现方式中，所述线性流量信息包括每段线性流量值、开始产生每段线性流量的时刻以及每段线性流量的持续时间。
结合第四方面、第四方面的第一种可能的实现方式，在第二种可能实现的方式中，所述线性流量信息包括每段线性流量的速率、开始产生每段线性流量的时刻以及每段线性流量的持续时间。
结合第四方面、第四方面的第一种至第二种可能的实现方式，在第三种可能实现的方式中，所述依据所述线性流量信息进行计费包括流量重新批价。
结合第四方面、第四方面的第一种至第三种可能的实现方式，在第四种可能实现的方式中，所述计费请求为信用控制请求CCR，所述指示线性流量信息的参数通过所述CCR消息中的扩展字段或保留字段携带。
结合第四方面、第四方面的第一种至第四种可能的实现方式，在第五种可能实现的方式中，所述线性流量值包括上行流量值和下行流量值，所述线性流量速率包括上行流量速率和下行流量速率。
第五方面，提供了一种计费系统，包括接入设备和计费设备：所述接入设备，用于发送流量请求给计费设备；接收所述计费设备根据所述流量请求返回的授权流量信息；根据所述终端用户对所述授权流量的使用情况，向所述计费设备发送计费请求，所述计费请求中携带指示线性流量信息的参数，以便所述计费设备依据所述线性流量信息进行计费；所述线性流量信息为所述终端用户在使用所述授权流量过程中，产生的每段线性流量的相关参数；所述计费设备，用于接收所述接入设备发送的流量请求；根据所述流量请求返回授权流量信息给所述接入设备；接收所述接入设备发送的计费请求，所述计费请求中携带所述指示线性流量信息的参数；依据所述线性流量信息进行计费。
第六方面，提供了一种计算设备，包括：处理器、存储器、总线和通信接口；所述存储器用于存储计算设备执行指令，所述处理器与所述存储器通 过所述总线连接，当所述计算设备运行时，所述处理器执行所述存储器存储的所述计算机执行指令，以使所述计算设备执行第一方面至第二方面及第一方面至第二方面的任一可能的实现方式所述的方法。
根据本发明实施例提供的技术方案，通过上报授权流量使用时间内的每段线性流量信息，使得计费设备获得了详细的流量使用情况，能够依据该线性流量信息准确的回溯用户在某一时刻的流量使用情况，从而能够进行准确的计费。
附图说明
图1是现有实时计费方法的示范性信令图
图2是本发明实施例应用的网络架构的示意图；
图3是依据本发明一实施例的计费方法的示范性流程图；
图4是依据本发明一实施例的计费方法的示范性流程图；
图5是依据本发明一实施例的计费方法的示范性信令图；
图6是依据本发明一实施例的线性流量信息的示意图；
图7是依据本发明一实施例的接入设备的结构示意图；
图8是依据本发明一实施例的计费设备的结构示意图；
图9是依据本发明一实施例的计费系统的结构示意图
图10是依据本发明一实施例的通用计算机结构的硬件结构示意图。
具体实施方式
为使本发明实施例的目的、技术方案和优点更加清楚，下面将结合本发明实施例中的附图，对本发明实施例中的技术方案进行清楚地描述，显然，所描述的实施例是本发明一部分实施例，而不是全部的实施例。基于本发明中的实施例，本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例，都属于本发明保护的范围。
图2是本发明实施例应用的网络架构的示意图。网络架构200包括策略 和计费规则功能实体202(Policy and Charging Rule Function，PCRF)、策略和计费执行功能实体2041(Policy and Charging Enforcement Function，PCEF)、应用功能实体206(Application Function，AF)、用户签约数据库208(Subscription Profile Respository，SPR)、承载绑定及事件报告功能实体210(Bearing Binding and Event Report Function，BBERF)、流量内容识别部件212(Traffic Detection Function，TDF)、OCS214和离线计费系统216(Offline Charging System，OFCS)。
其中，PCRF202包含策略控制决策和基于流计费控制的功能，PCRF202通过Gx接口接收来自PCEF2041的输入，向PCEF2041提供关于业务数据流检测、门控(Gating Control)、服务质量(Quality of Service，QoS)控制和基于流计费的网络控制功能。PCRF202将其制定的策略和计费规则发送给PCEF2041执行，同时，PCRF202还需要保证这些规则和用户的签约信息一致。PCRF202制定策略和计费规则的依据包括：从AF206获取与业务相关的信息；从SPR208获取与用户策略计费控制签约信息；从PCEF2041获取与承载相关网络的信息。
PCEF2041主要包含业务数据流的检测、策略执行和基于流的计费功能。PCEF2041功能实体通常位于网关204(Gateway，GW)内，例如GGSN网关、4G核心网络(Evolved Packet Core，EPC)的分组数据网网关(Packet Data Network Gateway，P-GW)、无线局域网(Wireless Local Area Network，WLAN)中的分组数据网关(Packet Data Gateway，PDG)。PCEF2041也可独立部署。
BBERF210的功能包括承载绑定、上行承载绑定的验证、以及事件报告。该功能实体位于网关中，例如基于S5/S8接口，使用代理移动IP(Proxy Mobile IP，PMIP)，实现3GPP接入的服务网关(Service Gateway，S-GW)，高速分组数据(High Rate Packet Data，HRPD)中的HRPD服务网关，非3G接入场合下的接入网关(Access Gateway，A-GW)。
TDF212执行应用程序检测和报告检测。例如，TDF212可以识别深度 报文检测(deep packet inspection，DPI)。如果TDF212检测不出这些信息，则由TDF212执行门控，重定向带宽限制。如果能检测到应用程序信息，则会提交给PCRF202，由PCRF202产生决策交由PCEF2041执行控制。
OCS214提供基于用户和业务数据流的信用控制功能。主要由在线采集、计费控制、批价、余额管理等模块构成，实现了在线计费功能，并配合其它计费网元设备(触发基于会话、事件的在线计费事件请求设备，如SCP、CCG、ISMP等)进行实时话务控制。与PCEF2041通过Gy接口相连。
OFCS216与PCEF2041—起完成离线计费方式下的计费操作。
本发明实施例中，认为PCEF位于网关GGSN内。
图3是依据本发明一实施例的计费方法的示范性流程图。在具体实现过程中，计费方法300可由例如但不限于接入设备来执行，该接入设备可以是例如但不限于GGSN。在本实施例中，计费设备与接入设备之间根据直径(Diameter)协议进行通信。
S302，接入设备发送流量请求给计费设备。
可选的，流量请求可以为CCR消息。
S304，接入设备接收所述计费设备根据所述流量请求返回的授权流量信息，其中，“所述计费设备根据所述流量请求返回的授权流量信息”具体为：所述计费设备根据所述流量请求返回的携带指示授权流量信息的参数的消息。
可选的，携带授权流量信息的消息可以为CCA消息，具体为：携带指示授权流量信息的参数的消息可以为CCA消息。
S306，接入设备根据所述终端用户对所述授权流量的使用情况，向所述计费设备发送计费请求，所述计费请求中携带指示线性流量信息的参数，以便所述计费设备依据所述线性流量信息进行计费；所述线性流量信息为所述终端用户在使用所述授权流量过程中，产生的每段线性流量的相关参数。
可选的，线性流量信息包括每段线性流量值、开始产生每段线性流量的时刻以及每段线性流量的持续时间，该每段线性流量值指每段线性流量的线性流量值。
可选的，线性流量信息包括每段线性流量的速率、开始产生每段线性流量的时刻以及每段线性流量的持续时间，该每段线性流量的速率指每段线性流量的流量速率。
可选的，线性流量值的获得方式包括设置定时器，配置定时时间，当使用流量的时长达到定时时间时，该接入设备获取已使用的流量大小。
可选的，线性流量速率的获得方式包括设置定时器，配置定时时间，当使用流量的时长达到定时时间时，所述接入设备获取已使用的流量大小，根据所述已使用的流量大小和所述定时时间，确定所述线性流量速率。其中，线性流量速率指上述线性流量的流量速率。
可选的，计费请求为CCR消息，所述指示线性流量信息的参数通过所述CCR消息中的扩展字段或保留字段携带，具体为：所述指示线性流量信息的参数通过所述CCR消息中的扩展字段携带，或通过所述CCR消息中的保留字段携带。
根据本发明实施例提供的技术方案，通过上报授权流量使用时间内的每段线性流量信息，使得计费设备获得了详细的流量使用情况，能够依据该线性流量信息准确的回溯用户在某一时刻的流量使用情况，从而能够进行准确的计费。
图4是依据本发明一实施例的计费方法的示范性流程图。在具体实现过程中，计费方法400可由例如但不限于计费设备来执行。该计费设备可以是例如但不限于预付费服务器(Pre-Paid Server，PPS)。更进一步的说，该预付费服务器可具体为例如但不限于OCS。
S402，计费设备接收接入设备发送的流量请求。
S404，计费设备根据所述流量请求返回授权流量信息给所述接入设备，其中，所述计费设备根据所述流量请求返回授权流量信息给所述接入设备具体为：所述计费设备根据所述流量请求返回携带指示授权流量信息的参数的消息给所述接入设备。
S406，计费设备接收所述接入设备发送的计费请求，所述计费请求中携带指示线性流量信息的参数，所述线性流量信息为所述终端用户在使用所述授权 流量的过程中，产生的每段线性流量的相关参数。
可选的，该线性流量信息包括每段线性流量值、开始产生每段线性流量的时刻以及每段线性流量的持续时间，该每段线性流量值指每段线性流量的线性流量值。
可选的，线性流量信息包括每段线性流量的速率、开始产生每段线性流量的时刻以及每段线性流量的持续时间，该每段线性流量的速率指每段线性流量的流量速率。
S408，计费设备依据所述线性流量信息进行计费。
可选的，依据线性流量信息进行计费包括流量重新批价。
根据本发明实施例提供的技术方案，通过上报授权流量使用时间内的每段线性流量信息，使得计费设备获得了详细的流量使用情况，能够依据该线性流量信息准确的回溯用户在某一时刻的流量使用情况，从而能够进行准确的计费。
图5是依据本发明一实施例的计费方法的示范性信令图。在具体实现过程中，计费方法500可以由例如但不限于接入设备和计费设备执行。在本实施例中，接入设备可以是例如但不限于GGSN。计费设备可以是例如但不限于PPS。更进一步的说，该预付费服务器可具体为例如但不限于OCS。接入设备与计费设备之间根据直径(Diameter)协议进行通信。在图5中，GGSN发送CCR消息，请求OCS授权流量；OCS根据该CCR消息，将授权流量通过CCA消息发送给GGSN；GGSN在收到OCS的授权流量后给终端用户提供业务，终端用户使用该授权流量。在终端用户使用该授权流量的过程中产生线性流量信息，GGSN将该线性流量信息通过CCR消息上报给OCS，OCS根据该线性流量信息进行计费。
S502，GGSN向OCS发送CCR消息，该CCR消息是流量请求，用于请求OCS授权流量。
S504，OCS向GGSN发送CCA消息，其中携带授权流量信息。
OCS结合终端用户的账户余额情况对GGSN请求的流量进行授权，具体的，在终端用户的账户余额足以支付GGSN请求的流量时，包括按照以下两种方式 进行授权：
第一种，OCS授权GGSN请求的流量；
第二种，OCS根据内部策略确定授权流量，通常会根据用户上网的网络，网速，用户购买的套餐情况等信息动态调整授权流量大小；此时的授权流量不一定与GGSN请求的流量大小相同。
如果终端用户的账户余额不足以支付GGSN请求的流量，则授权其账户余额可以支付的流量。
S506，终端用户在使用该授权流量的过程中产生线性流量信息，GGSN将该线性流量信息通过CCR消息发送给OCS。
S508，OCS依据线性流量信息进行计费。
具体的，OCS可以根据线性流量信息准确的回溯流量使用情况，对流量重新批价。
在S506中，具体的，由于终端用户在使用业务例如访问Internet的过程中，流量速率并不一定是恒定的，因此在使用该授权流量的过程中会出现不同的时间段内流量速率不同的情况。例如图6所示的情况，在图6中，OCS授权给GGSN 600M的流量，在终端用户使用该600M流量访问Internet的过程中，在6:00至6:05时间段内，流量速率为1M/S，在6:05至6:10时间段内，流量速率为0.5M/S，在6:10至6:15时间段内，流量速率为0M/S，在6:15至6:20时间段内，流量速率为0.5M/S。
流量速率相同的连续时间即为一个线性流量段，例如图6中的流量速率为1M/S的6:00至6:05时间段即为一个线性流量段。线性流量段内的流量总量称为线性流量值，例如图6中的6:00至6:05时间段内的流量总量为1M/S*60S*5＝300M，300M即为这段线性流量段内的线性流量值。该连续时间称为该段线性流量的持续时间Phase-Duration，例如对于图6中的线性流量段6:00至6:05，5分钟即为该段线性流量的持续时间。该持续时间的起始时刻称为开始产生该段线性流量的时刻Start-Time，例如图6中的线性流量段6:00至6:05，6:00即为开始产生该段线性流量的时刻。
GGSN将每一个线性流量段的线性流量信息发送给OCS，每一个线性流量段的线性流量信息包括但不限于以下两种情况的任一种：
第一种，包括线性流量值、开始产生该段线性流量的时刻Start-Time和该段线性流量的持续时间Phase-Duration，其中，线性流量包括上行流量Output-Quota和下行流量Input-Quota。GGSN可以上传上行流量Output-Quota和下行流量Input-Quota的总量，也可以将上行流量Output-Quota和下行流量Input-Quota作为两个数据上传，其中，“GGSN可以上传上行流量Output-Quota和下行流量Input-Quota的总量，也可以将上行流量Output-Quota和下行流量Input-Quota作为两个数据上传”具体为：GGSN可以上传上行流量值和下行流量值的总流量值，也可以将上行流量值和下行流量值作为两个数据上传。
第二种，包括线性流量速率、开始产生该段线性流量的时刻Start-Time和该段线性流量的持续时间Phase-Duration，其中，线性流量速率包括上行流量速率Output-Quota-Ratio和下行流量速率Input-Quota-Ratio。GGSN可以上传上行流量速率Output-Quota-Ratio和下行流量速率Input-Quota-Ratio的总和速率，也可以将上行流量速率Output-Quota-Ratio和下行流量速率Input-Quota-Ratio作为两个数据上传，其中线性流量速率指该线性流量段的流量速率。
在具体实现过程中，可以通过设置定时器，配置定时时间，当使用流量的时长达到定时时间时，获取已使用的流量大小的方式来确定线性流量或线性流量速率。
具体的，对于GGSN发送上述第一种线性流量信息，即发送每段线性流量、开始产生每段线性流量的时刻Start-Time和每段线性流量的持续时间Phase-Duration给OCS时，可以将定时时间设置为1秒，当使用流量的时长达到1秒时，GGSN获取已使用的流量大小。这种方式使得每段线性流量的持续时间Phase-Duration相同，Phase-Duration等于1秒。在用户使用OCS的授权流量的过程中，GGSN每1秒获取在该1秒内的使用流量大小，将该使用流量大小、开始产生该使用流量的时刻和持续时间1秒发送给OCS。前已述及，使用流量大小包括上行流量和下行流量，GGSN可以上传上行流量和下行流量的 总量，即该1秒内的使用流量大小，也可以将上行流量和下行流量作为两个数据上传。在具体实现中，定时时间可以由运营商确定，由于定时时间不同，GGSN获取的流量与用户在该定时时间内真实使用的流量之间有可能存在误差，运营商可以根据其能够接受的误差范围来设定定时时间的长短，本发明将定时时间设置为1秒只是提供一种可行方式，并不用来对本发明的保护范围做出限制。上述“由于定时时间不同，GGSN获取的流量与用户在该定时时间内真实使用的流量之间有可能存在误差”具体为：由于定时时间不同，Phase-Duration不同，定时时间长时，例如定时时间为5分钟，Phase-Duration内的流量速率可能并不恒定，因此将定时时间作为线性流量段的持续时间与真正的线性流量段的持续时间之间可能存在误差。
可选的，如果连续多个定时时间内的使用流量大小相同，可以将这些多个定时时间合并作为一个线性流量段的持续时间Phase-Duration，将合并后的持续时间Phase-Duration、合并后的Phase-Duration内产生的流量总量、这些多个定时时间中第一个定时时间开始的时刻Start-Time上报给OCS。例如，定时时间为1秒，GGSN每1秒获取一次使用流量，在连续10个1秒的时间内，每1秒的使用流量大小都为1M，在第11个1秒内的使用流量大小不为1M，则可以将这10个1秒合并，成为10秒，此时这10秒就为一个线性流量段的持续时间Phase-Duration，该线性流量段的线性流量总量为10M。若这10个1秒中第一个1秒的开始时刻是6:00，则该线性流量段的Start-Time即为6:00。GGSN将指示10秒、10M、6:00的信息通过CCR消息发送给OCS。其中，由于第一个定时时间的Start-Time与多个定时时间合并成的一个线性流量段的Start-Time相同，因此上报第一个定时时间的Start-Time相当于上报该合并成的线性流量段的Start-Time。
对于GGSN发送上述第二种线性流量信息，即发送线性流量速率、开始产生每段线性流量的时刻Start-Time和每段线性流量的持续时间Phase-Duration给OCS时，将定时时间设置为1秒，GGSN每1秒获取一次使用流量，GGSN获取的使用流量即为线性流量速率。如果连续几秒的速率相同，例如连续几秒 的速率都为1M/S，可以将这几秒合并作为一个线性流量段的持续时间Phase-Duration，将合并后的持续时间Phase-Duration、持续时间内的流量速率、这段持续时间开始的时刻Start-Time上报给OCS。例如，将定时时间设置为1秒，GGSN每1秒获取一次使用流量，得到流量速率，在连续10秒的时间内流量速率始终为1M/S，第11秒流量速率大小不为1M/S，则可以将前10秒合并，此时这10秒就为一个线性流量段的持续时间Phase-Duration，该线性流量段的线性流量速率为1M/S。若这10秒的开始时刻是6:00，则该线性流量段的Start-Time即为6:00。GGSN将指示10秒、1M/S、6:00的信息通过CCR消息发送给OCS。
可选的，也可以将每秒的流量速率上报给GGSN，此时可以不上报Phase-Duration，上报的线性流量信息为线性流量速率、开始产生每段线性流量的时刻Start-Time。
上报上述线性流量信息时，可以不上报未产生流量的线性流量段，例如图6中的6:10至6:15时间段，只上报产生流量的线性流量段，例如图6中的6:00至6:05、6:05至6:10、6:15至6:20时间段。其中，“未产生流量”指未消耗流量，“产生流量”指消耗流量。
上报线性流量信息给OCS时，可以通过在CCR消息中扩展字段来携带指示线性流量值、线性流量速率、开始产生每段线性流量的时刻和每段线性流量的持续时间的参数，也可以通过CCR消息中的保留字段来携带。例如，在CCR中扩展如下字段来上报线性流量值、开始产生每段线性流量的时刻和每段线性流量的持续时间：
USU-Quota-Information::＝<AVP Header：**>
                       [Start-Time]
                       [Phase-Duration]
                       [Output-Quota]
                       [Input-Quota]
                       *[AVP]
可选的，GGSN在请求下一个授权流量的CCR消息中，将各段线性流量信息一起发送给OCS。
通过以上步骤使得OCS获得了详细的流量使用情况，能够实现重新批价，例如，正常计费时的费率切换点在5:00，但是因为套餐配置出错，重新配置的套餐费率切换点在6:08，由于GGSN上报了Start-Time为6:05、Phase-Duration为5分钟、流量速率为0.5M/S的线性流量信息，则可以计算得出费率切换点6:08前，从6:05到6:08时间段内的流量为0.5M/S*60S*3＝90M，费率切换点6:08后，从6:08到6:10时间段内的流量为0.5M/S*60S*2＝60M。由于GGSN上报了每段线性流量的速率、开始产生每段线性流量的时刻和每段线性流量的持续时间，则利用同样的方法可以计算出6:05前和6:10后的流量，6:05前的流量加上6:05到6:08时间段内的流量就得到了费率切换点6:08前的流量，6:10后的流量加上6:08到6:10时间段内的流量就得到了费率切换点6:08后的流量，因此实现了对流量使用情况的回溯，再结合6:08前后的费率，可以得出6:08前后使用流量产生的费用，就可以对流量进行重新批价。
根据本发明实施例提供的技术方案，通过上报授权流量使用时间内的每段线性流量信息，使得计费设备获得了详细的流量使用情况，能够依据该线性流量信息准确的回溯用户在某一时刻的流量使用情况，从而能够进行准确的计费，通过将相同使用流量大小或相同速率的连续时间段合并，可以减少上报的数据量，降低网络负荷。
图7是依据本发明一实施例的接入设备的结构示意图。该接入设备用于执行前述图3实施例中的计费方法。接入设备700包括发送模块702和接收模块704。
发送模块702，用于发送流量请求给计费设备。
接收模块704，用于接收所述计费设备根据所述流量请求返回的授权流量信息。
所述发送模块702还用于根据所述终端用户对所述授权流量的使用情况，向所述计费设备发送计费请求，所述计费请求中携带指示线性流量信息的参数， 以便所述计费设备依据所述线性流量信息进行计费；所述线性流量信息为所述终端用户在使用所述授权流量的过程中，产生的每段线性流量的相关参数。
可选的，线性流量信息包括每段线性流量值、开始产生每段线性流量的时刻以及每段线性流量的持续时间。
可选的，线性流量值的获得方式可以为设置定时器，配置定时时间，当使用流量的时长达到定时时间时，所述接入设备获取已使用的流量大小。
可选的，线性流量信息包括每段线性流量的速率、开始产生每段线性流量的时刻以及每段线性流量的持续时间。
可选的，线性流量速率的获得方式可以为设置定时器，配置定时时间，当使用流量的时长达到定时时间时，所述接入设备获取已使用的流量大小，根据所述已使用的流量大小和所述定时时间，确定所述线性流量速率。
根据本发明实施例提供的技术方案，通过上报授权流量使用时间内的每段线性流量信息，使得计费设备获得了详细的流量使用情况，能够依据该线性流量信息准确的回溯用户在某一时刻的流量使用情况，从而能够进行准确的计费。
图8是依据本发明一实施例的计费设备的结构示意图。该计费设备用于执行前述图4实施例中的计费方法。计费设备800包括接收模块802、发送模块804和计费模块806。
接收模块802，用于接收接入设备发送的流量请求。
发送模块804，用于根据所述流量请求返回授权流量信息给所述接入设备。
所述接收模块802还用于接收所述接入设备发送的计费请求，所述计费请求中携带指示线性流量信息的参数，所述线性流量信息在所述终端用户使用所述授权流量的过程中，产生的每段线性流量的相关参数。
计费模块806，用于依据所述线性流量信息进行计费。
可选的，线性流量信息包括每段线性流量值、开始产生每段线性流量的时刻以及每段线性流量的持续时间。
可选的，线性流量信息包括每段线性流量的速率、开始产生每段线性流量的时刻以及每段线性流量的持续时间。
根据本发明实施例提供的技术方案，通过上报授权流量使用时间内的每段线性流量信息，使得计费设备获得了详细的流量使用情况，能够依据该线性流量信息准确的回溯用户在某一时刻的流量使用情况，从而能够进行准确的计费。
图9是依据本发明一实施例的计费系统的结构示意图。计费系统900包括接入设备902和计费设备904。
接入设备902，用于发送流量请求给计费设备；接收所述计费设备根据所述流量请求返回的授权流量信息；根据所述终端用户对所述授权流量的使用情况，向所述计费设备发送计费请求，所述计费请求中携带指示线性流量信息的参数，以便所述计费设备依据所述线性流量信息进行计费；所述线性流量信息为所述终端用户在使用所述授权流量过程中，产生的每段线性流量的相关参数；
计费设备904，用于接收所述接入设备发送的流量请求；根据所述流量请求返回授权流量信息给所述接入设备；接收所述接入设备发送的计费请求，所述计费请求中携带所述指示线性流量信息的参数；依据所述线性流量信息进行计费。
其中，“所述计费设备根据所述流量请求返回的授权流量信息”具体为：所述计费设备根据所述流量请求返回的携带指示授权流量信息的参数的消息。
根据本发明实施例提供的技术方案，通过上报授权流量使用时间内的每段线性流量信息，使得计费设备获得了详细的流量使用情况，能够依据该线性流量信息准确的回溯用户在某一时刻的流量使用情况，从而能够进行准确的计费。
图10是依据本发明一实施例的通用计算机结构1000的硬件结构示意图。如图10所示，通用计算机结构1000包括处理器1002、存储器1004、通信接口1006和总线1008。其中，处理器1002、存储器1004和通信接口1006通过总线1008实现彼此之间的通信连接。
处理器1002可以采用通用的中央处理器(Central Processing Unit，CPU)，微处理器，应用专用集成电路(Application Specific Integrated Circuit，ASIC)，或者一个或多个集成电路，用于执行相关程序，以实现本发明实施例所提供的技术方案。
存储器1004可以是只读存储器(Read Only Memory，ROM)，静态存储设备，动态存储设备或者随机存取存储器(Random Access Memory，RAM)。存储器1004可以存储操作系统和其他应用程序。在通过软件或者固件来实现本发明实施例提供的技术方案时，用于实现本发明实施例提供的技术方案的程序代码保存在存储器1004中，并由处理器1002来执行。
通信接口1006使用例如但不限于收发器一类的收发装置，来实现接与其他设备或通信网络之间的通信。
总线1008可包括一通路，在各个部件(例如处理器1002、存储器1004、输和通信接口1006)之间传送信息。
当接入设备包括该通用计算机结构1000时，处理器1002调取存储器1004中的指令时包括：
处理器1002控制通信接口1006发送流量请求给计费设备。
处理器1002控制通信接口1006接收计费设备根据所述流量请求返回的授权流量信息。处理器1002控制通信接口1006根据所述终端用户对所述授权流量的使用情况，向所述计费设备发送计费请求，所述计费请求中携带指示线性流量信息的参数，以便所述计费设备依据所述线性流量信息进行计费；所述线性流量信息为所述终端用户在使用所述授权流量过程中，产生的每段线性流量的相关参数。
当计费设备包括该通用计算机结构1000时，处理器1002调取存储器1004中的指令时包括：
处理器1002控制通信接口1006接收接入设备发送的流量请求。
处理器1002控制通信接口1006根据根据所述流量请求返回授权流量信息给所述接入设备。
处理器1002控制通信接口1006接收所述接入设备发送的计费请求，所述计费请求中携带指示线性流量信息的参数，所述线性流量信息为所述终端用户在使用所述授权流量的过程中，产生的每段线性流量的相关参数。处理器1002依据所述线性流量信息进行计费。
应注意，尽管图10所示的通用计算机结构1000仅仅示出了处理器1002、存储器1004、通信接口1006和总线1008，但是在具体实现过程中，本领域的技术人员应当明白，上述接入设备和计费设备还包含实现正常运行所必须的其他器件。同时，根据具体需要，本领域的技术人员应当明白，上述接入设备和计费设备还可包含实现其他附加功能的硬件器件。此外，本领域的技术人员应当明白，上述接入设备和计费设备也可仅仅包含实现本发明实施例所必须的器件，而不必包含图10中所示的全部器件。
本领域普通技术人员可知，上述方法中的全部或部分步骤可以通过程序指令相关的硬件完成，该程序可以存储于一计算机可读存储介质中，该计算机可读存储介质如ROM、RAM和光盘等。
综上所述，以上仅为本发明的较佳实施例而已，并非用于限定本发明的保护范围。凡在本发明的精神和原则之内，所作的任何修改、等同替换、改进等，均应包含在本发明的保护范围之内。

Claims (23)

  1. 一种计费方法，其特征在于，包括以下步骤：
    接入设备发送流量请求给计费设备；
    所述接入设备接收所述计费设备根据所述流量请求返回的授权流量信息；
    所述接入设备根据终端用户对所述授权流量的使用情况，向所述计费设备发送计费请求，所述计费请求中携带指示线性流量信息的参数，以便所述计费设备依据所述线性流量信息进行计费；所述线性流量信息为所述终端用户在使用所述授权流量过程中，产生的每段线性流量的相关参数。
  2. 如权利要求1所述的计费方法，其特征在于，所述线性流量信息包括每段线性流量值、开始产生每段线性流量的时刻以及每段线性流量的持续时间。
  3. 如权利要求1所述的计费方法，其特征在于，所述线性流量信息包括每段线性流量的速率、开始产生每段线性流量的时刻以及每段线性流量的持续时间。
  4. 如权利要求2所述的计费方法，其特征在于，所述线性流量值的获得方式包括：
    设置定时器，配置定时时间，当使用流量的时长达到定时时间时，所述接入设备获取已使用的流量大小。
  5. 如权利要求3所述的计费方法，其特征在于，所述线性流量速率的获得方式包括：
    设置定时器，配置定时时间，当使用流量的时长达到定时时间时，所述接入设备获取已使用的流量大小，根据所述已使用的流量大小和所述定时时间，确定所述线性流量速率。
  6. 如权利要求1至5中任意一项所述的计费方法，其特征在于，所述流量请求和所述计费请求为信用控制请求CCR消息，所述授权流量信息携带在信用控制应答CCA消息中，所述指示线性流量信息的参数通过CCR消息中的扩展字段或保留字段携带。
  7. 一种计费方法，其特征在于，包括以下步骤：
    计费设备接收接入设备发送的流量请求；
    所述计费设备根据所述流量请求返回授权流量信息给所述接入设备；
    所述计费设备接收所述接入设备发送的计费请求，所述计费请求中携带指示线性流量信息的参数，所述线性流量信息为终端用户在使用所述授权流量的过程中，产生的每段线性流量的相关参数；
    所述计费设备依据所述线性流量信息进行计费。
  8. 如权利要求7所述的计费方法，其特征在于，所述线性流量信息包括每段线性流量值、开始产生每段线性流量的时刻以及每段线性流量的持续时间。
  9. 如权利要求7所述的计费方法，其特征在于，所述线性流量信息包括每段线性流量的速率、开始产生每段线性流量的时刻以及每段线性流量的持续时间。
  10. 如权利要求7所述的计费方法，其特征在于，所述依据所述线性流量信息进行计费包括流量重新批价。
  11. 如权利要求7所述的计费方法，其特征在于，所述计费请求为信用控制请求CCR，所述指示线性流量信息的参数通过所述信用控制请求中的扩展字段或保留字段携带。
  12. 一种接入设备，其特征在于，包括发送模块和接收模块：
    所述发送模块，用于发送流量请求给计费设备；
    所述接收模块，用于接收所述计费设备根据所述流量请求返回的授权流量信息；
    所述发送模块还用于根据终端用户对所述授权流量的使用情况，向所述计费设备发送计费请求，所述计费请求中携带指示线性流量信息的参数，以便所述计费设备依据所述线性流量信息进行计费；所述线性流量信息为所述终端用户在使用所述授权流量的过程中，产生的每段线性流量的相关参数。
  13. 如权利要求12所述的接入设备，其特征在于，所述线性流量信息包括每段线性流量值、开始产生每段线性流量的时刻以及每段线性流量的持续时间。
  14. 如权利要求12所述的接入设备，其特征在于，所述线性流量信息包括每段线性流量的速率、开始产生每段线性流量的时刻以及每段线性流量的持续时间。
  15. 如权利要求13所述的接入设备，其特征在于，所述线性流量值的获得方式包括：
    设置定时器，配置定时时间，当使用流量的时长达到定时时间时，所述接入设备获取已使用的流量大小。
  16. 如权利要求14所述的计费方法，其特征在于，所述线性流量速率的获得方式包括：
    设置定时器，配置定时时间，当使用流量的时长达到定时时间时，所述接入设备获取已使用的流量大小，根据所述已使用的流量大小和所述定时时间，确定所述线性流量速率。
  17. 如权利要求12至16中任意一项所述的接入设备，其特征在于，所述流量请求和所述计费请求为信用控制请求CCR消息，所述授权流量信息携带在信用控制应答CCA消息中，所述指示线性流量信息的参数通过CCR消息中的扩展字段或保留字段携带。
  18. 一种计费设备，其特征在于，包括接收模块，发送模块和计费模块：
    所述接收模块，用于接收接入设备发送的流量请求；
    所述发送模块，用于根据所述流量请求返回授权流量信息给所述接入设备；
    所述接收模块还用于接收所述接入设备发送的计费请求，所述计费请求中携带指示线性流量信息的参数，所述线性流量信息为在终端用户使用所述授权流量的过程中，产生的每段线性流量的相关参数；
    所述计费模块，用于依据所述线性流量信息进行计费。
  19. 如权利要求18所述的计费设备，其特征在于，所述线性流量信息包括每段线性流量值、开始产生每段线性流量的时刻以及每段线性流量的持续时间。
  20. 如权利要求18所述的计费设备，其特征在于，所述线性流量信息包括每段线性流量的速率、开始产生每段线性流量的时刻以及每段线性流量的持续 时间。
  21. 如权利要求18所述的计费设备，其特征在于，所述依据所述线性流量信息进行计费包括流量重新批价。
  22. 如权利要求18所述的计费设备，其特征在于，所述计费请求为信用控制请求CCR，所述指示线性流量信息的参数通过所述CCR消息中的扩展字段或保留字段携带。
  23. 一种计费系统，其特征在于，包括接入设备和计费设备：
    所述接入设备，用于发送流量请求给计费设备；接收所述计费设备根据所述流量请求返回的授权流量信息；根据所述终端用户对所述授权流量的使用情况，向所述计费设备发送计费请求，所述计费请求中携带指示线性流量信息的参数，以便所述计费设备依据所述线性流量信息进行计费；所述线性流量信息为所述终端用户在使用所述授权流量过程中，产生的每段线性流量的相关参数；
    所述计费设备，用于接收所述接入设备发送的流量请求；根据所述流量请求返回授权流量信息给所述接入设备；接收所述接入设备发送的计费请求，所述计费请求中携带所述指示线性流量信息的参数；依据所述线性流量信息进行计费。
PCT/CN2015/080679 2014-11-17 2015-06-03 一种计费方法、计费设备和计费系统 Ceased WO2016078392A1 (zh)

Priority Applications (3)

Application Number Priority Date Filing Date Title
BR112017000054A BR112017000054A2 (pt) 2014-11-17 2015-06-03 método de cobrança, dispositivo de cobrança e sistema de cobrança
EP15860086.6A EP3145224A4 (en) 2014-11-17 2015-06-03 Charging method, charging device and charging system
US15/412,737 US20170134178A1 (en) 2014-11-17 2017-01-23 Charging Method, Charging Device, and Charging System

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201410654552.4A CN104469728A (zh) 2014-11-17 2014-11-17 一种计费方法、计费设备和计费系统
CN201410654552.4 2014-11-17

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US15/412,737 Continuation US20170134178A1 (en) 2014-11-17 2017-01-23 Charging Method, Charging Device, and Charging System

Publications (1)

Publication Number Publication Date
WO2016078392A1 true WO2016078392A1 (zh) 2016-05-26

Family

ID=52914943

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2015/080679 Ceased WO2016078392A1 (zh) 2014-11-17 2015-06-03 一种计费方法、计费设备和计费系统

Country Status (5)

Country Link
US (1) US20170134178A1 (zh)
EP (1) EP3145224A4 (zh)
CN (1) CN104469728A (zh)
BR (1) BR112017000054A2 (zh)
WO (1) WO2016078392A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3554004A4 (en) * 2016-12-28 2019-12-11 Huawei Technologies Co., Ltd. PROCESS AND DEVICE FOR QUOTA MANAGEMENT

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104469728A (zh) * 2014-11-17 2015-03-25 华为技术有限公司 一种计费方法、计费设备和计费系统
CN106533705A (zh) * 2015-09-15 2017-03-22 中国移动通信集团公司 一种数据业务流量配额的分配方法及分配装置
EA202190711A1 (ru) * 2018-09-07 2021-07-30 Эффортел Текнолоджиз Система и способ для онлайновой тарификации телекоммуникационных услуг в режиме реального времени
US12401973B2 (en) * 2022-06-16 2025-08-26 T-Mobile Usa, Inc. Fee re-rating for a wireless carrier network

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1437352A (zh) * 2002-02-04 2003-08-20 华为技术有限公司 统计数据流量的方法
CN101222559A (zh) * 2008-01-23 2008-07-16 中兴通讯股份有限公司 业务计费方法及系统
CN102083045A (zh) * 2009-11-30 2011-06-01 中国移动通信集团安徽有限公司 一种业务计费处理方法和装置
CN102761851A (zh) * 2011-04-25 2012-10-31 中国移动通信集团设计院有限公司 一种利用分割话单进行计费的方法及设备
CN104469728A (zh) * 2014-11-17 2015-03-25 华为技术有限公司 一种计费方法、计费设备和计费系统

Family Cites Families (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6947724B2 (en) * 2002-01-04 2005-09-20 Telefonaktiebolaget Lm Ericsson (Publ) System and method of billing based on the reported traffic load in a telecommunications network
US20110003579A1 (en) * 2008-02-26 2011-01-06 Yigang Cai Online charging for supplementary services in ims networks
EP2509254A1 (en) * 2011-04-06 2012-10-10 Telefonaktiebolaget L M Ericsson (publ) Method and apparatus for controlling service traffic in a communication network
EP2563053B1 (en) * 2011-05-09 2017-08-02 Huawei Technologies Co., Ltd. Method and related device for controlling service charging
GB201207816D0 (en) * 2012-05-04 2012-06-13 Vodafone Ip Licensing Ltd Telecommunication networks
CN103874043B (zh) * 2012-12-11 2017-12-08 阿尔卡特朗讯 一种用于为用户设备进行漫游业务计费的方法与装置
EP2965498A1 (en) * 2013-03-07 2016-01-13 Alcatel Lucent Multiple tariff switches management
CN103957517B (zh) * 2014-04-25 2018-06-15 华为技术有限公司 一种ocs、前端网元、批价方法与速率监控方法

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1437352A (zh) * 2002-02-04 2003-08-20 华为技术有限公司 统计数据流量的方法
CN101222559A (zh) * 2008-01-23 2008-07-16 中兴通讯股份有限公司 业务计费方法及系统
CN102083045A (zh) * 2009-11-30 2011-06-01 中国移动通信集团安徽有限公司 一种业务计费处理方法和装置
CN102761851A (zh) * 2011-04-25 2012-10-31 中国移动通信集团设计院有限公司 一种利用分割话单进行计费的方法及设备
CN104469728A (zh) * 2014-11-17 2015-03-25 华为技术有限公司 一种计费方法、计费设备和计费系统

Non-Patent Citations (1)

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

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3554004A4 (en) * 2016-12-28 2019-12-11 Huawei Technologies Co., Ltd. PROCESS AND DEVICE FOR QUOTA MANAGEMENT
US11330114B2 (en) 2016-12-28 2022-05-10 Huawei Technologies Co., Ltd. Quota management method and apparatus

Also Published As

Publication number Publication date
EP3145224A1 (en) 2017-03-22
CN104469728A (zh) 2015-03-25
EP3145224A4 (en) 2017-10-04
US20170134178A1 (en) 2017-05-11
BR112017000054A2 (pt) 2017-11-07

Similar Documents

Publication Publication Date Title
JP6077664B2 (ja) 無線アクセス・ネットワーク（ｒａｎ）のための輻輳制御
US11647085B2 (en) Service redirection from a policy and charging control architecture
JP5606617B2 (ja) Ｌｔｅ／ｅｐｃネットワークにおけるローカル・ローミング課金
US8989056B2 (en) Methods, systems, and computer readable media for utilizing quota usage policy control in a diameter-based communication network
US9647848B2 (en) Application charging method, device, and system
CN104363572A (zh) 一种重定向方法、计费设备、接入设备和重定向系统
WO2015143851A1 (zh) 用量监控方法、装置和系统
WO2016078392A1 (zh) 一种计费方法、计费设备和计费系统
CN111866778A (zh) 基于漫游场景的鉴权方法、设备及系统
CN112702180B (zh) 一种策略控制方法、装置及系统
WO2016107280A1 (zh) 数据业务的计费方法、系统和相关设备
EP3389218B1 (en) Data service charging method, device and system
WO2016107177A1 (zh) 一种计费方法、装置及系统
KR20130001439A (ko) 서비스 품질 및 과금 제어를 위한 방법, 애플리케이션 기능 장치, 및 정책 및 과금 규칙 기능 장치
CN101998323B (zh) 一种基于策略和计费控制的重定向方法及装置
WO2014110966A1 (zh) 一种业务数据的处理方法、装置和系统
CN104105082A (zh) 计费策略信息生成方法及策略与计费制定功能实体
WO2012041148A1 (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: 15860086

Country of ref document: EP

Kind code of ref document: A1

REEP Request for entry into the european phase

Ref document number: 2015860086

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 2015860086

Country of ref document: EP

REG Reference to national code

Ref country code: BR

Ref legal event code: B01A

Ref document number: 112017000054

Country of ref document: BR

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 112017000054

Country of ref document: BR

Kind code of ref document: A2

Effective date: 20170102