WO2011110006A1 - Procédé de facturation, dispositif et système de réseau pour entreprise de routage local - Google Patents

Procédé de facturation, dispositif et système de réseau pour entreprise de routage local Download PDF

Info

Publication number
WO2011110006A1
WO2011110006A1 PCT/CN2010/076467 CN2010076467W WO2011110006A1 WO 2011110006 A1 WO2011110006 A1 WO 2011110006A1 CN 2010076467 W CN2010076467 W CN 2010076467W WO 2011110006 A1 WO2011110006 A1 WO 2011110006A1
Authority
WO
WIPO (PCT)
Prior art keywords
charging
information
service flow
statistics
local routing
Prior art date
Application number
PCT/CN2010/076467
Other languages
English (en)
Chinese (zh)
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 CN201080006014.4A priority Critical patent/CN102439902B/zh
Priority to PCT/CN2010/076467 priority patent/WO2011110006A1/fr
Publication of WO2011110006A1 publication Critical patent/WO2011110006A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/14—Charging, metering or billing arrangements for data wireline or wireless communications
    • 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
    • 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 the field of communications technologies, and in particular, to a charging method, device, and network system for a local routing service.
  • the uplink packet sent by the terminal is transmitted to the serving gateway through the base station, and then transmitted to the anchor access by the serving gateway.
  • the gateway is finally transmitted to the external network via the Home Agent (HA).
  • the downlink packet is routed to the terminal through the bearer path in the reverse direction.
  • the Accounting Agent is located at the Anchor GW.
  • the accounting agent performs charging statistics based on the traffic flow of the user, such as the upper and lower statistics traffic. Traffic, number of service packets, and more.
  • the charging proxy periodically sends the accounting statistics to the charging client through the R4 interface, and the charging client notifies the accounting authorization information to the Authentication Authorization ⁇ Accounting AAA server, so as to implement the user's
  • the charging of the service flow wherein the solid line in FIG. 1 is the service flow transmission path, and the broken line in FIG. 1 is the charging statistical information transmission path.
  • the serving gateway can send the packets sent by the source terminal directly to the destination terminal through the local routing technology (as shown by the thick solid line in Figure 2). ), thereby achieving the purpose of reducing the packet transmission delay and reducing the transmission load of the core network.
  • the local route in Figure 2 is done at the services gateway.
  • the local route can also be implemented at the base station or the anchor access gateway.
  • the operator also needs to perform charging.
  • the traffic accounting of the local route may adopt different charging models or rates.
  • charging information statistics are performed on a user service flow by an accounting agent located at an anchor access gateway.
  • an accounting agent located at an anchor access gateway.
  • the traffic accounting packet does not pass through the anchor access gateway.
  • the existing accounting architecture cannot perform accounting information statistics on the part of the service flow.
  • the embodiments of the present invention provide a charging method, a device, and a network system for a local routing service, which can implement charging for a local routing service.
  • a charging method for a local routing service including:
  • the local routing execution entity performs statistics on the charging related information of the service flow of the local route of the user, and obtains the first charging statistical information
  • a local routing execution entity including:
  • the local routing service flow information statistics unit is configured to perform statistics on the charging related information of the service flow that is locally routed by the user, to obtain the first charging statistical information;
  • a sending unit configured to send the first charging statistics, so that the charging server charges the locally routed service flow according to the first charging statistical information.
  • a network system comprising: the local routing execution entity and a charging server for receiving first charging statistics, and charging a locally routed service flow according to the first charging statistical information.
  • the local routing execution entity performs statistics on the charging related information of the local routing service flow, and notifies the accounting server of the accounting statistics, so that the charging server can perform charging on the locally routed service flow.
  • FIG. 1 is a schematic diagram of a WiMAX network architecture provided by the prior art
  • 2 is a schematic diagram of a local route of a service flow in a WiMAX network provided by the prior art
  • FIG. 3 is a flowchart of a method for charging a local route service according to an embodiment of the present invention
  • FIG. 4 is a flow chart of a charging method for a local routing service according to another embodiment of the present invention
  • FIG. 5 is a flow chart of a charging method for a local routing service in a WiMAX network according to an embodiment of the present invention
  • FIG. 6 is a flowchart of a charging method of a local routing service in a WiMAX network according to another embodiment of the present invention.
  • FIG. 7 is a flow chart of a charging method of a local routing service in a 3GPP network according to an embodiment of the present invention.
  • FIG. 8 is a structural diagram of a local route execution entity according to an embodiment of the present invention.
  • FIG. 9 is a structural diagram of a network system according to an embodiment of the present invention.
  • an embodiment of the present invention provides a charging method for a local routing service, where the method includes:
  • the local routing execution entity performs statistics on the charging related information of the service flow of the local route of the user, and obtains the first charging statistical information.
  • the local routing execution entity refers to a network entity that performs local forwarding of service flows in the network, and may be located in a serving gateway or a base station or an anchor access gateway in the WiMAX network, or may be located in a third generation partnership plan (3rd Generation).
  • 3rd Generation 3rd Generation
  • SGSN GPRS Service Support Node
  • eNodeB Evolved Node B
  • the first charging statistic information includes a statistic result of the charging related information of the service flow that is locally routed by the user, and optionally includes a local routing indication or a charging identifier, optionally, which may also include local
  • the ID of the service flow of the route; the statistics of the traffic-related information of the service flow that is locally routed by the user include: the number of uplink bytes of the service flow of the user local route and/or the downlink byte of the service flow of the user local route Or the number of the uplink information of the service flow of the local route of the user, and/or the number of downlink packets of the service flow of the local route of the user, or
  • the statistical result of the charging related information of the service flow that is locally routed by the user may further include: a duration of the session performed by the user in the local route, and a charging delay time,
  • the billing delay time is the time difference between the time point at which the local route executing entity collects the billing related information and the first billing statistics information, so that the subsequent billing server can receive
  • the local route execution entity may also perform statistics on the charging related information of the service flow that is not locally routed by the user, to obtain second charging statistics information.
  • the second charging statistics information includes: a statistical result of the charging related information of the service flow that is not locally routed by the user, and optionally includes a non-local routing indication.
  • the statistics of the charging related information of the service flow that is not locally routed by the user include: the number of uplink bytes of the service flow that is not locally routed by the user and/or the number of downlink bytes of the service flow that is not locally routed by the user; or
  • the statistics of the accounting related information of the service flow that is not locally routed by the user include: the number of uplink packets of the service flow that is not locally routed by the user, and/or the number of downlink packets of the service flow that is not locally routed by the user, or
  • the statistics of the charging related information of the service flow that is not locally routed by the user may also include: the duration of the session performed by the user in the non-local route and the charging delay time, and the charging delay time refers to the statistics of the local routing executing entity.
  • the first charging statistic information may include a statistic result of charging related information of one or more local routing service flows of the user, where the first charging statistic information includes charging related to multiple local routing service flows.
  • the first charging statistical information needs to include the ID of the service flow of the local route. In this way, if different service flows have different tariff standards, after the accounting server receives the first charging statistical information, according to the statistics of the ID of each service flow and the charging related information of the corresponding service flow, each service is used. The flow is billed.
  • the second charging statistics information may include statistics results of charging related information of one or more non-local routing service flows of the user, where the second charging statistics information includes multiple non-local routing service flows.
  • the second charging statistical information needs to include the ID of the non-local routing service flow. And the second charging statistics, do not need to anchor the charging proxy in the access gateway or the Packet Data Network Gateway (PDN-GW) in the 3GPP network and then calculate the local routing service flow of the user. Statistics related to the fee. 302. Send the first charging statistics, so that the charging server performs charging on the locally routed service flow according to the first charging statistical information.
  • PDN-GW Packet Data Network Gateway
  • the local route execution entity may also perform statistics on the charging related information of the service flow that is not locally routed by the user, and obtain the second charging statistics information. Then, the local routing execution entity also sends the second charging statistics in this step.
  • the local routing execution entity may send the first charging statistical information and the second charging statistical information by using a charging information update request message.
  • the local routing execution entity obtains the charging context information, where, in the WiMAX network, the charging context information may include a reporting interval, a remaining reporting time, and the like.
  • the charging context information may include a reporting interval, a remaining reporting time, and the like.
  • the local routing execution entity sends a charging information update request message including the first charging statistical information and the second charging statistical information according to the charging context information.
  • the local routing execution entity may directly send the charging information update request message to the charging server; or the local routing executing entity sends the charging information update request message to the charging server through the charging proxy; or, the local routing executing entity passes
  • the charging client sends a charging information update request message to the charging server.
  • the charging context information includes the charging server address and the charging identifier corresponding to the service flow of the local route, and the local routing execution entity sends the first to the charging server according to the charging server address in this step.
  • the billing statistics information includes: the billing identifier and a statistical result of the billing related information of the service flow locally routed by the user, where the billing identifier is used to indicate the service flow of the local route.
  • the fee model, the subsequent billing server, according to the billing identifier can know what rate is used to charge the service stream.
  • the first charging statistics may also include a local routing indication.
  • the accounting server refers to a network entity in the network that is responsible for charging the user.
  • the accounting server knows how many service flows are used by the user according to the charging statistics, and then charges the user.
  • the accounting server may be an AAA server in a WiMAX network, an Offline Charging System (OFCS) or a Charging Gateway Functionality (CGF) in a 3GPP network.
  • OFCS Offline Charging System
  • CGF Charging Gateway Functionality
  • the accounting server performs the accounting result of the charging related information of the user service flow according to the preset rule and the local routing, and uses the different rates for the local routing service flow and the non-local routing service flow to perform charging.
  • Pre-set rules stipulate the local routing industry Information such as the rate used by the service flow and non-local routing service flows.
  • the accounting server performs charging on the service flow according to the charging result in the charging statistical information and the statistical result of the charging related information of the local service execution entity to the user service flow.
  • the embodiment of the present invention uses the local routing execution entity to perform statistics on the charging related information of the local routing service flow, and notifies the charging server, so that the charging server can refer to the traffic flow of the local routing.
  • FIG. 4 another implementation of the present invention An example provides a charging method for a local routing service, where the method is applicable to a wimax network, and the method specifically includes:
  • the charging proxy sends a charging context delivery request message to the local routing execution entity, where the message includes the user's charging context information.
  • the charging context delivery request message may be a path registration response message.
  • the charging context information of the user includes: a reporting interval, a remaining reporting time, and the like.
  • the reporting interval indicates that the accounting statistics are reported once every other time.
  • the remaining reporting time is the time when the charging information update request message is reported next time, that is, the time when the local routing executing entity receives the charging context information and reports the charging information update request message for the first time.
  • the reporting interval is 30 s. Because the terminal may communicate with the terminal in the external network before the local routing is performed, the charging proxy always collects statistics on the charging related information of the service flow transmitted by the terminal to the external network. The traffic of the service flow is counted, and the service flow of the local route may be 10s after the last time the accounting information update request message is reported to the accounting server. The remaining reporting time is 10s, indicating the local route. After the execution entity 10s, the accounting information update request message carrying the accounting statistics information is reported for the first time, and then reported in the time interval of 30s.
  • the method for detecting the local route by the charging agent can be implemented by using the prior art, for example, by determining the destination IP address of the service flow, or by receiving a successful authorization indication of the local route of the service flow, etc., without affecting the present Implementation of the invention.
  • the local routing execution entity After receiving the charging context delivery request message, the local routing execution entity starts to collect statistics about the charging related information of the service flow of the user. Specifically, when the user has a non-local routing service flow, in this step, the local routing execution entity may perform statistics only on the charging related information of the local routing service flow of the user, and obtain the first charging statistical information, which is not for the user. The local routing service flow is not counted, and the non-local routing service flow of the user is still counted by the charging agent for charging related information; or the local routing executing entity not only performs statistics on the charging related information of the user's local routing service flow.
  • the first charging statistics information includes: a statistical result of the charging related information of the local routing service flow of the user.
  • the method further includes a local routing indication, which may further include an ID of the locally routed service flow.
  • the second charging statistics information includes: a statistical result of the charging related information of the non-local routing service flow of the user, optionally, the non-local routing indication, which may also include the non-local routing service flow. ID.
  • the local routing execution entity performs statistics on the local routing service flow of the user and the charging related information of the non-local routing service flow
  • the first charging statistical information must include the local routing indication
  • the second accounting The fee statistics must include non-local routing indications.
  • the first charging statistic information may include a statistic result of charging related information of one or more local routing service flows of the user, where the first charging statistic information includes charging related information of multiple local routing service flows.
  • the first charging statistics information needs to include the ID of the service flow of the local route.
  • the second charging statistics information may include statistics results of charging related information of one or more non-local routing service flows of the user, where the second charging statistics information includes multiple non-local routing service flows.
  • the local route execution entity sends a charging context delivery response message to the charging proxy.
  • the charging context delivery response message may be a path registration confirmation message Path_Reg_Ack. This step is an optional step and may be performed prior to step 402 or concurrently with step 402. 404.
  • the charging proxy sends a charging information update request message to the accounting server, and the current time interval is The accounting statistics of the non-local routing service flow in the interval are sent to the accounting server.
  • the charging information update request message in the step may be a traffic update message.
  • This step is an optional step.
  • the local routing execution entity performs the statistics on the charging related information of the non-local routing service flow of the user in step 402
  • the subsequent charging proxy no longer counts the charging related information of the service flow of the user. The user will no longer report the billing information update request for the user.
  • the charging server returns a charging information update response message to the charging proxy.
  • the charging information update response message may be a traffic update confirmation message Bulk_Interim_Update_Ack;.
  • This step is an optional step.
  • the local route execution entity periodically sends a billing information update request message to the billing server according to the billing context information.
  • the local route execution entity sends a charging information update request message to the charging server according to the reporting time interval and the remaining reporting time. Assuming that the remaining reporting time is 10s and the reporting interval is 30s, the local routing executing entity sends the user's charging information update request message to the accounting server for the first time after 10s, and then sends it every 30s.
  • the charging information update request message may include: first charging statistical information and second charging statistical information.
  • the charging information update request message includes only: the first charging statistical information.
  • the charging information update request message may be forwarded by the local routing execution entity to the charging server through the charging proxy.
  • the local route execution entity may send a charging information update request message to the accounting server, or send the charging information update request by the charging client.
  • the local routing executing entity sends the charging information to the charging client.
  • the traffic update message Bulk_Interim_Update of the charging statistics information and then the charging client sends an accounting request message carrying the charging statistics information to the charging server; or, the local routing executing entity charges the accounting agent through the charging agent.
  • the server sends a charging information update request, and specifically, the local routing executing entity sends the charging proxy to the charging proxy.
  • the charging proxy sends the charging statistical information to the charging server; or, the local routing executing entity charges to the charging proxy through the charging proxy
  • the server sends a charging information update request. Specifically, the local routing executing entity sends a traffic update message Bulk_Interim_Update carrying the charging statistical information to the charging proxy, and then the charging proxy will carry the traffic update message Bulk of the charging statistical information.
  • the Interim-Update is reported to the charging client, and then the charging client sends an accounting request message Accounting Request; carrying the charging statistics to the charging server.
  • the accounting server returns a charging information update response message to the local routing executing entity, and implements charging for the local routing service flow.
  • the accounting server determines, according to the preset rule, that the statistics result in the first charging statistics information is a charging statistics result of the local routing service flow, according to the local routing indication in the first charging statistics information, according to the The first accounting statistics information is used to charge the local routing service flow according to the tariff of the local routing service flow in the preset rule, and the first charging statistical information includes charging related information for multiple local routing service flows.
  • the non-local routing service flow of the user performs charging, and the second charging statistical information includes charging related information for multiple non-local routing service flows.
  • the statistics result and the ID of the non-local routing service flow the non-local routing service flows are charged according to the tariffs of the non-local routing service flows in the preset rule.
  • the charging information update response message may be directly sent to the local routing execution entity, or may be forwarded to the local routing executing entity by the charging proxy.
  • the local routing execution entity performs statistics on the charging related information of the local routing service flow, and directly notifies or notifies the charging server through the charging proxy, so that the charging server can charge the locally routed service flow.
  • FIG. 5 is a diagram showing a charging method of a local routing service according to an embodiment of the present invention.
  • a local routing execution entity is located on a serving gateway in a WiMAX network
  • a charging proxy is located on an anchor access gateway, and the serving gateway directly
  • the billing statistics are sent to the billing client, and then reported by the billing client to the billing server.
  • the billing server is an AAA server, and the method specifically includes: 501.
  • the terminal sends a dynamic service flow to the base station.
  • the message DSA-REQ is requested to request the establishment of a radio bearer for transporting the traffic flow.
  • the service flow increase request message includes service flow information, such as a service flow IP quintuple, where the service flow IP quintuple includes a source IP address, a destination IP address, a source port number, a destination port number, and a protocol type. .
  • service flow IP quintuple includes a source IP address, a destination IP address, a source port number, a destination port number, and a protocol type.
  • the base station sends a dynamic service flow to the terminal to add a receiving message DSA-RVD, where the message indicates that the base station has received the dynamic service flow increase request message.
  • the base station sends a path registration request message Path_Reg_Req to the serving gateway to request to establish a network bearer for transmitting the service flow, where the message includes the IP quintuple information of the service flow.
  • the serving gateway sends a path registration request message Path_Reg_Req to the anchor access gateway to request to establish a network bearer for transmitting the service flow.
  • the anchor access gateway determines, according to the IP quintuple information of the service flow, that the peer end communicating with the terminal is also located under the service gateway, and performing local routing on the service flow, and anchoring the access gateway to the wrong
  • the Service Flow Authorization (ARP) sends a resource reservation request message RR_Req, and the resource reservation request message may include indication information for performing local routing.
  • the anchor service flow authorization entity determines QoS information such as bandwidth and delay of the service flow requested by the user according to the subscription information of the user, the policy of the operator, and the service information, and anchors the service flow authorization entity to anchor access.
  • the gateway returns a resource reservation response message RR_Rsp, and the message includes QoS information of the service flow.
  • the anchor service flow authorization entity determines whether to allow the service according to the subscription information of the user, the policy of the operator, and the service information.
  • the flow performs the local route, and carries the indication information indicating whether the service flow is allowed to perform the local route in the resource reservation response message.
  • the anchor access gateway sends a path registration response message Path_Reg_Rsp to the serving gateway, where
  • the path registration response message includes charging context information, where the charging context information may include a reporting time interval, a remaining reporting time, and the like, and the charging context information may further include a local routing charging indication.
  • the reporting interval indicates that the accounting statistics are reported once every other time.
  • the remaining reporting time is the time from the next reporting of the traffic update message.
  • the upper time interval is 30 s. Since the terminal may communicate with the terminal in the external network before the local route is executed, the charging proxy in the anchor access gateway always reports the traffic flow of the terminal to the external network. The fee-related information is collected, for example, the traffic of the service flow is counted. After the traffic update message is reported to the accounting server for the last 20 seconds, the user has a service flow for performing local routing. The remaining reporting time is 10s. After the service gateway 10s, the traffic update message carrying the accounting statistics is reported for the first time, and then reported in the time interval of 30s.
  • the serving gateway After receiving the charging context information, the serving gateway starts to collect statistics on the charging related information of the service flow of the user, to obtain charging statistical information.
  • the serving gateway sends a path registration response message Path_Reg_Rsp to the base station.
  • the service gateway may perform statistics only on the charging related information of the local routing service flow of the user, and obtain the first charging statistical information, and the non-local routing service flow of the user is not The statistic is performed, and the non-local routing service flow of the user is still statistic of the charging related information by the charging proxy; or the serving gateway not only performs statistics on the charging related information of the local routing service flow of the user, but also obtains the first charging statistic.
  • the information also collects the charging related information of the non-local routing service flow of the user, and obtains the second charging statistical information, so that the charging proxy in the access gateway does not need to be anchored to the non-local routing service of the user.
  • the billing related information of the stream is counted.
  • the charging related information of the service flow may include: the number of service packets, the number of bytes of service packets, and the like.
  • the base station completes the allocation of the air interface resource, and sends a dynamic service flow increase response message DSA-RSP to the terminal.
  • the terminal sends a dynamic service flow increase confirmation message DSA-ACK to the base station, indicating that the completion is empty.
  • the port service flow bearer is established.
  • the base station sends a path registration confirmation message Path_Reg_Ack to the serving gateway.
  • the serving gateway sends a path registration confirmation message Path_Reg_Ack to the anchor access gateway, indicating that the network side service flow bearer establishment is completed.
  • the anchor access gateway sends a resource reservation acknowledgement message to the anchor service flow authorization entity.
  • RR_Ack to inform the anchoring service flow, that the radio bearer of the authorized entity service flow has been established.
  • the anchor access gateway sends a traffic update message.
  • Bulk Interim—Updates to the charging client, where the message carries the identifier of the new charging proxy (ie, the identifier of the serving gateway).
  • the traffic update message carries the new charging proxy.
  • the identifier is used to notify the charging client that the charging proxy has been migrated, and the charging gateway is subsequently used by the serving gateway.
  • the traffic update message carries the identifier of the new charging proxy to notify the charging client that a new charging proxy has joined.
  • the charging client sends a traffic update confirmation message to the anchor access gateway.
  • Bulk Interim—Update—Ack;.
  • the serving gateway periodically sends a traffic update message Bulk_Interim_Update to the charging client according to the charging context information, where the traffic update message includes charging statistics.
  • the serving gateway sends a traffic update message to the charging client according to the reporting interval and the remaining reporting time. Assuming that the remaining reporting time is 10s and the reporting interval is 30s, the service gateway sends a traffic update message to the accounting client for the first time after 10s, and then sends it every 30s.
  • the traffic update message may include: first charging statistics information and second charging statistics information; when the serving gateway only localizes the service to the user When the charging related information of the flow is counted, the traffic update message includes the first charging statistical information.
  • the charging client sends a traffic update confirmation message to the service gateway Bulk—Interim—Update—Ack;.
  • the charging client sends an accounting request message to the AAA server,
  • the charging request message carries the foregoing charging statistical information.
  • the AAA server completes one-time charging for the user according to the charging statistics, and returns a charging acceptance message Accounting Accept to the charging client.
  • the service gateway obtains the user charging context, and collects the accounting related information of the service flow, and reports the accounting statistics, so that the accounting server can perform accounting statistics according to the charging statistics.
  • the information implements accounting statistics and bill generation for the local routing service.
  • FIG. 6 is a diagram showing a charging method of a local routing service according to another embodiment of the present invention.
  • a local routing execution entity is located on a base station in a WiMAX network
  • a charging proxy is located on an anchor access gateway, and the base station is local.
  • the charging statistic information of the routing service flow is sent to the charging proxy located at the anchoring access gateway, and is sent by the charging proxy to the charging client, and then reported by the charging client to the charging server, and the charging is performed in this embodiment.
  • the server is an AAA server, and the method specifically includes:
  • 601-607 is the same as 501-507 and will not be mentioned here.
  • the serving gateway sends a path registration response message Path_Reg_Rsp to the base station, where the message includes charging context information.
  • the base station completes the allocation of the air interface resource, and sends a dynamic service flow increase response message DSA-RSP to the terminal.
  • the terminal sends a dynamic service flow increase acknowledgement message DSA-ACK to the base station, indicating that the bearer service flow bearer establishment is completed.
  • the base station may start to perform statistics on charging related information of the service flow of the user, to obtain accounting statistics.
  • the base station sends a path registration confirmation message Path_Reg_Ack to the serving gateway.
  • the base station may perform statistics only on the charging related information of the local routing service flow of the user, and obtain the first charging statistical information, and the non-local routing service flow of the user is not performed.
  • Statistics the non-local routing service flow of the user is still the statistics of the charging related information by the charging agent; or the base station not only statistics the charging related information of the local routing service flow of the user, but also obtains the first charging statistical information.
  • the charging related information of the non-local routing service flow of the user is also counted, and the second charging statistical information is obtained, so that the charging proxy in the access gateway does not need to be anchored to the non-local routing service flow of the user.
  • Billing related information is counted. 612.
  • the serving gateway sends a path registration confirmation message Path_Reg_Ack to the anchor access gateway, indicating that the network side service flow bearer establishment is completed.
  • the anchor access gateway sends a resource reservation acknowledgement message RR_Ack to the anchor service flow authorization entity to notify that the bearer of the anchor service flow authorization entity service flow has been established.
  • the base station periodically sends a traffic update message to the anchor access gateway according to the charging context information.
  • the traffic update message carries the charging statistics information; the message can be forwarded to the anchor access gateway through the serving gateway.
  • the base station sends a traffic update message according to the reporting time interval, the remaining reporting time, and the like. Assuming that the remaining reporting time is 10s and the reporting interval is 30s, the base station sends a traffic update message for the first time after 10s, and then sends it every 30s.
  • the traffic update message may include: first charging statistics information and second charging statistics information.
  • the traffic update message includes: first charging statistics information.
  • the charging proxy in the anchor access gateway sends a traffic update confirmation message to the base station through the serving gateway.
  • the charging proxy in the anchor access gateway reports the traffic update message Bulk_Interim_Update carrying the charging statistics to the charging client.
  • the charging client sends a traffic update confirmation message to the charging proxy in the anchor access gateway.
  • Bulk Interim—Update—Ack;.
  • the charging client sends an accounting request message to the AAA server, where the charging request message carries the charging statistics information.
  • the AAA server completes one-time charging for the user according to the charging statistics, and returns a charging acceptance message Accounting Accept to the charging client.
  • FIG. 7 is a diagram showing a charging method of a local routing service according to another embodiment of the present invention.
  • a local routing execution entity is located at a 3GPP serving gateway, and a packet data network gateway (PDN) is used before a local route occurs.
  • PDN packet data network gateway
  • -GW Performs the accounting information statistics function.
  • the service gateway collects the accounting related information of the local routed service flow of the user, and the service gateway directly sends the charging statistics information to the charging gateway function entity ( Charging Gateway Function, CGF), the method specifically includes:
  • the terminal sends a create PDP context request message to the packet data network gateway, where the create PDP context request message includes service flow information, such as a service flow IP quintuple, where the service flow IP quintuple includes a source IP address and a destination IP address. Address, source port number, destination port number, and protocol type.
  • service flow IP quintuple includes a source IP address and a destination IP address. Address, source port number, destination port number, and protocol type.
  • the PDN-GW determines, according to the service flow IP quintuple, that the peer end that communicates with the terminal is located at the same serving gateway as the terminal, and may perform local routing on the service flow, and the user calculates the PDP context response message.
  • the fee context information informs the service gateway.
  • the charging context information may include a charging identifier, a charging gateway function entity address, and the like, where the charging identifier indicates a charging model of the service flow, and the charging context information may further include a local routing charging indication.
  • the charging context information in the step includes the charging identifier corresponding to each service flow of the user;
  • the network is configured to collect statistics on the charging related information of the local routing service flow of the user by the serving gateway, and the charging context information in the step includes the charging identifier corresponding to the local routing service flow.
  • the serving gateway After receiving the charging context information, the serving gateway starts to collect statistics about the charging related information of the service flow of the user, and sends the charging statistical information through the data record according to the charging gateway function entity address in the charging context information.
  • the message Data Record Transfer Request is reported to the CGF.
  • the accounting statistics information includes: a statistical result of the charging related information of the service flow of the user and a charging identifier of the service flow.
  • the service gateway may perform statistics only on the charging related information of the local routing service flow of the user, and obtain the first charging statistical information, and the non-local routing service flow of the user is not Statistics are performed, and the non-local routing service flow of the user is still counted by the charging agent for charging related information; or the serving gateway is not only related to the charging of the local routing service flow of the user.
  • the information is collected to obtain the first charging statistical information, and the charging related information of the non-local routing service flow of the user is also collected, and the second charging statistical information is obtained, so that the PDN GW is not required to be non-local to the user.
  • the billing related information of the routing service flow is counted.
  • the data record transfer request message may include: first charging statistics information and second charging statistics information;
  • the statistics information includes: a charging identifier corresponding to the service flow of the local route and a statistics result of the charging related information of the service flow of the local route;
  • the second charging statistics information includes: a charging identifier corresponding to the service flow of the non-local route The statistical result of the billing related information for the service flow of the non-local route.
  • the serving gateway only counts the charging related information of the local routing service flow of the user, the data record transfer request message only includes: the first charging statistical information.
  • the first charging statistics information may include statistics results of charging related information of one or more local routing service flows of the user, and the second charging statistics information may include one or more non-local routes to the user.
  • the statistical result of the billing related information of the service flow may include statistics results of charging related information of one or more local routing service flows of the user, and the second charging statistics information may include one or more non-local routes to the user.
  • the CGF completes one-time charging for the user according to the charging statistics information, and returns a data record delivery response message Data Record Transfer Response message to the service gateway.
  • the CGF charges the corresponding service flow according to the charging identifier corresponding to the service flow in the charging statistics information; specifically, the local accounting in the first charging statistical information
  • the charging identifier corresponding to the traffic flow of the non-local route is used to charge the non-local routing service flow by using the statistics corresponding to the charging identifier and the charging related information of the service flow of the non-local routing.
  • the service gateway in the 3GPP network obtains the user charging context, performs statistics on the charging related information of the service flow, and uploads accounting statistics, so that the charging server can
  • the accounting statistics are used to implement accounting statistics and bill generation for the local routing service.
  • an embodiment of the present invention provides a local routing execution entity, where the entity may be located in a base station or a serving gateway or an anchor access gateway in a WiMAX network, or the entity is located.
  • the entity includes:
  • the local routing service flow information statistics unit 801 is configured to perform statistics on the charging related information of the service flow that is locally routed by the user, to obtain the first charging statistical information, where the first charging statistical information includes the local routing service flow information statistical unit. 801.
  • the statistics result of the charging related information of the service flow that is locally routed by the user, where the first charging statistics information may further include a local routing indication.
  • the sending unit 802 is configured to send the first charging statistics, so that the charging server charges the locally routed service flow according to the first charging statistical information.
  • the entity further includes: a non-local routing service flow information statistics unit 803, configured to perform statistics on the charging related information of the service flow that is not locally routed by the user, to obtain the second charging statistical information.
  • the sending unit 802 is specifically used to Sending a charging information update request message including the first charging statistical information and the second charging statistical information; wherein the first charging statistical information includes a local routing indication and charging related information of a service flow locally routed by the user
  • the statistical result of the second charging statistics includes: a non-local routing indication and a statistical result of charging related information of a service flow that is not locally routed by the user.
  • the local routing execution entity further includes: a context obtaining unit 804, configured to obtain the charging context information.
  • the sending unit 802 is configured to send the first charging according to the charging context information.
  • Statistics In the WiMAX network, the charging context information includes: a reporting time interval; the sending unit 802 is specifically configured to periodically send the first charging statistical information according to the reporting time interval in the charging context information;
  • the charging context information includes a charging server address and a charging identifier corresponding to the service flow of the local route.
  • the sending unit 802 is specifically configured to send the first charging statistics to the charging server according to the charging server address.
  • the first charging statistics information includes: the charging identifier and a statistical result of charging related information of a service flow that is locally routed by the user.
  • the sending unit 802 specifically sends the information including the first charging statistical information and the second charging statistical information.
  • Fee information update request message may be sent to the billing server directly; or the billing information update request message may be sent to the billing server by the billing agent; or The charging server sends the charging information update request message.
  • the embodiment of the present invention uses the local routing execution entity to perform charging related information on the local routing service flow.
  • the statistic is provided, and the accounting server is configured to enable the accounting server to perform the traffic flow of the local routing.
  • the embodiment of the present invention provides a network system, where the system includes:
  • the local routing execution entity 901 is configured to perform statistics on the charging related information of the service flow that is locally routed by the user, to obtain the first charging statistical information, and send the first charging statistical information; where the first charging statistical information includes the local routing
  • the statistic result of the charging related information of the service flow of the local route of the user, the first charging statistic information may further include a local routing indication.
  • the accounting server 902 is configured to receive the first charging statistical information, and perform charging on the locally routed service flow according to the first charging statistical information.
  • the first charging statistic information includes a local routing indication and a statistic result of the charging related information of the service flow that is locally routed by the user; in order to perform statistics on the charging related information of the user by the same entity, it is no longer needed.
  • the accounting agent performs statistics on the non-local routing service flow of the user, and the local routing execution entity 901 is further configured to perform statistics on the charging related information of the service flow that is not locally routed by the user, to obtain the second charging statistical information.
  • the second charging statistics information includes: a non-local routing indication and a statistical result of the charging related information of the service flow that is not locally routed by the user; the charging server 902 is further configured to receive the second charging statistical information, according to the The second charging statistics information is used to charge a service flow that is not locally routed.
  • the local routing execution entity performs statistics on the charging related information of the local routing service flow, and notifies the charging server, so that the charging server can perform the local routing service flow. All or part of the steps of the embodiment method may be completed by a program to instruct related hardware, and the program may be stored in a computer readable storage medium such as a read only memory, a magnetic disk or an optical disk.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Physics & Mathematics (AREA)
  • Probability & Statistics with Applications (AREA)
  • Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

L'invention concerne un procédé de facturation d'entreprise de routage local, qui comprend les étapes suivantes: une entité d'exécution de routage local établit des statistiques sur la base des données relatives aux chiffres d'un flux d'affaires de routage local d'utilisateur afin d'obtenir des premières données statistiques de facturation; les premières données statistiques de facturation sont envoyées afin qu'un serveur de facturation puisse facturer le flux d'affaires du routage local sur la base de celles-ci. Ce procédé permet de mettre en œuvre la facturation pour une entreprise de routage local.
PCT/CN2010/076467 2010-08-30 2010-08-30 Procédé de facturation, dispositif et système de réseau pour entreprise de routage local WO2011110006A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN201080006014.4A CN102439902B (zh) 2010-08-30 2010-08-30 本地路由业务的计费方法、装置及网络系统
PCT/CN2010/076467 WO2011110006A1 (fr) 2010-08-30 2010-08-30 Procédé de facturation, dispositif et système de réseau pour entreprise de routage local

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2010/076467 WO2011110006A1 (fr) 2010-08-30 2010-08-30 Procédé de facturation, dispositif et système de réseau pour entreprise de routage local

Publications (1)

Publication Number Publication Date
WO2011110006A1 true WO2011110006A1 (fr) 2011-09-15

Family

ID=44562835

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2010/076467 WO2011110006A1 (fr) 2010-08-30 2010-08-30 Procédé de facturation, dispositif et système de réseau pour entreprise de routage local

Country Status (2)

Country Link
CN (1) CN102439902B (fr)
WO (1) WO2011110006A1 (fr)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018035867A1 (fr) * 2016-08-26 2018-03-01 华为技术有限公司 Procédé et appareil de facturation
CN110234084B (zh) * 2019-05-16 2020-06-19 中国联合网络通信集团有限公司 一种用户接入方法、pgw-c和核心网

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1798040A (zh) * 2004-12-22 2006-07-05 华为技术有限公司 一种在通信系统中进行计费的方法
CN1798041A (zh) * 2004-12-22 2006-07-05 华为技术有限公司 一种在通信系统中进行计费的方法
CN101720541A (zh) * 2007-06-13 2010-06-02 高通股份有限公司 在移动数据分组网络中用于计账的方法和装置

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101277202B (zh) * 2007-03-29 2012-06-27 华为技术有限公司 计费方法以及计费系统
EP2319207B1 (fr) * 2008-07-30 2019-06-19 Alcatel-Lucent USA Inc. Facturation en ligne de sessions qui sont transférées entre des domaines de réseau
WO2010083443A1 (fr) * 2009-01-15 2010-07-22 Starent Networks, Corp Relocalisation entre passerelles dans des réseaux de communication

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1798040A (zh) * 2004-12-22 2006-07-05 华为技术有限公司 一种在通信系统中进行计费的方法
CN1798041A (zh) * 2004-12-22 2006-07-05 华为技术有限公司 一种在通信系统中进行计费的方法
CN101720541A (zh) * 2007-06-13 2010-06-02 高通股份有限公司 在移动数据分组网络中用于计账的方法和装置

Also Published As

Publication number Publication date
CN102439902A (zh) 2012-05-02
CN102439902B (zh) 2014-04-02

Similar Documents

Publication Publication Date Title
JP4828608B2 (ja) 課金方法、課金システム、課金クライアントおよび課金処理手段
US8874715B2 (en) Charging method, system and reporting method for terminal accessing through multiple access networks
WO2013104234A1 (fr) Procédé et système de contrôle de règles pour un réseau convergé
WO2010072107A1 (fr) Procédé et dispositif de déduction de facture de flux de service d'utilisateur
WO2014169877A1 (fr) Procédé, système et support de stockage pour mise en œuvre de facturation basée sur réseau epc sdn
WO2011110000A1 (fr) Procédé et dispositif de transmission d'un message de perte de support radio
WO2015131331A1 (fr) Procédé et dispositif pour gérer une session de facturation
WO2006012798A1 (fr) Procede de traitement de reautorisation a base de taxation du flux de donnees par paquets
WO2011085614A1 (fr) Procédé de gestion de ressources dans un réseau convergent à service complet et système correspondant
WO2013091410A1 (fr) Procédé, système et dispositif d'accès au réseau
WO2013060170A1 (fr) Procédé et dispositif de fourniture de support de facturation basé sur un support lipa
WO2011095025A1 (fr) Procédé et système de commande de politique pour accès local d'utilisateur mobile
WO2007051413A1 (fr) Procede de comptabilite et systeme de comptabilite associe
WO2010078761A1 (fr) Procédé, appareil et système de détermination de la politique et de la facturation
WO2014000302A1 (fr) Procédé et passerelle de traitement de facturation de passerelle
WO2014094488A1 (fr) Procédé et dispositif de gestion de politique de facturation destinés à un service local d'itinérance
WO2009056046A1 (fr) Procédé de fin de session
WO2011088702A1 (fr) Procédé et système permettant de contrôler des ressources dans un réseau de convergence multiservice
WO2011018020A1 (fr) Procede et systeme de commande d'equilibre de charge de pcrf et dra de redirection
WO2012129992A1 (fr) Procédé de traitement de connectivité de données sponsorisées, et fonction d'imputation et de règles
WO2012010036A1 (fr) Procédé et système de contrôle de politique
WO2010066157A1 (fr) Procédé de facturation, dispositif de facturation, passerelle de facturation et système de facturation
WO2011110006A1 (fr) Procédé de facturation, dispositif et système de réseau pour entreprise de routage local
WO2011020419A1 (fr) Procédé de mise en œuvre, système correspondant et agent de routage diameter (dra) adaptés pour contrôler l'équilibrage de charge d'une entité pcrf (fonction d’imputation et de règles)
WO2012155774A1 (fr) Procédé, système d'établissement d'une sous-session s9, et fonction "règles de politique et de facturation"

Legal Events

Date Code Title Description
WWE Wipo information: entry into national phase

Ref document number: 201080006014.4

Country of ref document: CN

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

Ref document number: 10847264

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 10847264

Country of ref document: EP

Kind code of ref document: A1