WO2011110006A1

WO2011110006A1 - Charging method, apparatus and network system for local routing bussiness

Info

Publication number: WO2011110006A1
Application number: PCT/CN2010/076467
Authority: WO
Inventors: 倪慧
Original assignee: 华为技术有限公司
Priority date: 2010-08-30
Filing date: 2010-08-30
Publication date: 2011-09-15
Also published as: CN102439902B; CN102439902A

Abstract

A charging method of local routing business includes: a local routing execution entity takes statistics on the count-relevant information of a business flow of a user local routing to obtain a first charging statistic information; the first charging statistic information is sent, so that a charging server charges the business flow of the local routing according to the first charging statistic information. Using the method, the charging for the local routing business can be realized.

Description

Charging method, device and network system for local routing service

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.

Background technique

In the Worldwide Interoperability for Microwave Access (WiMAX) network, when the terminal communicates with the external network, 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.

Schematic diagram of the WiMAX network architecture is shown in Figure 1. 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. Then, 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.

When the two terminals that need to communicate with each other are located under the same service gateway, as shown in Figure 2, 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. Similarly, when two users are under the same base station or the same anchor access gateway (Anchor GW), the local route can also be implemented at the base station or the anchor access gateway.

For the service flow of the local route, the operator also needs to perform charging. At the same time, compared to the normal traffic flow, the traffic accounting of the local route may adopt different charging models or rates.

The prior art has the following disadvantages:

In the prior art, charging information statistics are performed on a user service flow by an accounting agent located at an anchor access gateway. When a user's certain traffic flows locally at the serving gateway or base station When the route is forwarded, 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.

In view of this, the embodiments of the present invention provide:

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;

Sending the first charging statistics, so that the charging server charges the locally routed service flow according to 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;

And 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.

In the embodiment of the present invention, 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.

DRAWINGS

In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings used in the embodiments will be briefly described below. It is obvious that the drawings in the following description are only some embodiments of the present invention. One of ordinary skill in the art can also obtain other drawings based on these drawings without undue creative effort.

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;

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;

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;

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.

detailed description

Referring to FIG. 3, an embodiment of the present invention provides a charging method for a local routing service, where the method includes:

301. 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). In the Partnership Project, 3 GPP) GPRS Service Support Node (SGSN), Serving Gateway, NodeB or Evolved Node B (eNodeB).

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 first billing statistics information according to the billing delay. Time knows the time of this statistic.

When the user currently has a traffic flow that is not locally routed, 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 time difference between the time point of the fee-related information and the time when the second charging statistics information is sent, so that the subsequent charging server can know the time point of the statistics according to the charging delay time after receiving the second charging statistical information.

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. When the statistics result of the information, 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. Similarly, 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. When the statistics result of the charging related information, 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.

As described above, when the user currently has a service flow that is not locally routed, 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.

Optionally, before the step 301, 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. For details, refer to the detailed description of the subsequent embodiments. In this step, 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. Specifically, 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. In the 3GPP network, 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. For the 3GPP network, 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. In the WiMAX network, 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. In the 3GPP network, 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. Referring to 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:

401. When one or more service flows of the user need to be locally routed, 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.

Path—Reg— Rsp.

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. For example, 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.

402. 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. Obtaining the first charging statistical information, and performing statistics on the charging related information of the non-local routing service flow of the user, to obtain the second charging statistical information, so that the charging agent does not need the non-local routing service for the user. The billing related information of the stream is counted. The first charging statistics information includes: a statistical result of the charging related information of the local routing service flow of the user. Optionally, 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. It should be noted that, if 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, and 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. When the statistics result, the first charging statistics information needs to include the ID of the service flow of the local route. In this way, if the 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. Similarly, 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. When the statistics result of the charging related information, the second charging statistical information needs to include the ID of the non-local routing service flow.

403. 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.

Bulk—Interim—Update.

This step is an optional step. When 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.

405. 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.

406. The local route execution entity periodically sends a billing information update request message to the billing server according to the billing context information.

In this step, 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.

When the local routing execution entity performs statistics on the charging related information of all the service flows of the user, the charging information update request message may include: first charging statistical information and second charging statistical information. When the local routing execution entity only collects the accounting related information of the local routing service flow of the user, 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. In this step, 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. Sending a traffic update message Bulk_Interim_Update carrying the charging statistics information, and then 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.

407. 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.

Specifically, 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 statistics result and the ID of the local routing service flow, according to the tariff of each local routing service flow in the preset rule, the local routing service flow is charged; according to the non-local routing indication in the second charging statistical information, Determining, by the second accounting information, a statistical result of the non-local routing service flow, according to the second charging statistical information, according to the tariff of the non-local routing service flow in the preset rule, 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. When 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.

In the embodiment of the present invention, 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.

In order to make the technical solutions provided by the present invention more clear, the following embodiments will provide detailed technical solutions to the technical solutions provided by the present invention. FIG. 5 is a diagram showing a charging method of a local routing service according to an embodiment of the present invention. In this method, a local routing execution entity is located on a serving gateway in a WiMAX network, and 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. In this embodiment, 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. .

502. 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.

503. 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.

504. 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.

505. 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.

506. 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.

Optionally, if the resource reservation request message includes the indication information for performing the local route, in this step, 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.

507. 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. In this embodiment, the time when the service gateway receives the charging context information and the first time the traffic update message is received. For example, 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.

508. 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.

When the user has a non-local routing 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 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. For the first accounting statistics and the second accounting statistics, refer to the related description in step 402, and details are not described herein.

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.

509. 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.

510. 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.

511. The base station sends a path registration confirmation message Path_Reg_Ack to the serving gateway.

512. 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.

513. 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.

514. 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).

When the serving gateway not only counts the charging related information of the local routing service flow of the user, but also collects the charging related information of the non-local routing service flow of the user, 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.

If the service gateway only collects statistics about the charging related information of the user's local routing service flow, the traffic update message carries the identifier of the new charging proxy to notify the charging client that a new charging proxy has joined.

515. The charging client sends a traffic update confirmation message to the anchor access gateway. Bulk—Interim—Update—Ack;.

516. 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.

In this step, 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.

When the serving gateway performs statistics on the charging related information of all the service flows of the user, 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.

517. The charging client sends a traffic update confirmation message to the service gateway Bulk—Interim—Update—Ack;.

518. The charging client sends an accounting request message to the AAA server, The charging request message carries the foregoing charging statistical information.

519. 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.

For details, how to charge the user to the AAA server is described in detail in step 407, and details are not described herein.

In the embodiment of the present invention, 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. In this method, a local routing execution entity is located on a base station in a WiMAX network, and 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.

608. The serving gateway sends a path registration response message Path_Reg_Rsp to the base station, where the message includes charging context information.

609. 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.

610. 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.

611. 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.

When the user has a non-local routing service flow, 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.

613. 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.

614. The base station periodically sends a traffic update message to the anchor access gateway according to the charging context information.

Bulk—Interim—Update, the traffic update message carries the charging statistics information; the message can be forwarded to the anchor access gateway through the serving gateway.

In this step, 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.

When the base station performs statistics on the charging related information of all the service flows of the user, the traffic update message may include: first charging statistics information and second charging statistics information. When the base station performs statistics on the charging related information of the local routing service flow of the user, the traffic update message includes: first charging statistics information.

615. The charging proxy in the anchor access gateway sends a traffic update confirmation message to the base station through the serving gateway. Bulk—Interim—Update—Ack;.

616. The charging proxy in the anchor access gateway reports the traffic update message Bulk_Interim_Update carrying the charging statistics to the charging client.

617. The charging client sends a traffic update confirmation message to the charging proxy in the anchor access gateway. Bulk—Interim—Update—Ack;.

618. The charging client sends an accounting request message to the AAA server, where the charging request message carries the charging statistics information.

619. 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.

In the embodiment of the present invention, when the user's service flow is locally routed, the base station obtains the user charging context, and performs statistics on the charging related information of the service flow, and reports the charging statistical information, so that the charging server can calculate the charging statistics. The information implements accounting statistics and bill generation for the local routing service. FIG. 7 is a diagram showing a charging method of a local routing service according to another embodiment of the present invention. In this method, 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. -GW) Performs the accounting information statistics function. After the local route occurs, 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:

701. 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.

702. 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.

It should be noted that, if the network is configured to perform statistics on the charging related information of all the service flows of the user by the serving gateway, 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.

703. 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.

When the user has a non-local routing 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.

When the service gateway collects the charging related information of all the service flows of the user, 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. When 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.

704. 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.

Specifically, 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 billing identifier corresponding to the service flow of the route, and the statistics of the billing identifier corresponding to the billing identifier and the billing related information of the service flow of the local route, the billing of the local routing service flow; according to the second billing statistics 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.

In the embodiment of the present invention, when the user's service flow is locally routed, 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.

Referring to FIG. 8, 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. In the service gateway in the 3GPP network, 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. Specifically, 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.

In order to obtain the charging context information, the local routing execution entity further includes: a context obtaining unit 804, configured to obtain the charging context information. Specifically, 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.

If the non-local routing service flow information statistics unit 803 performs statistics on the charging related information of the service flow that is not 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. Specifically, the billing 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. Referring to FIG. 9, 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 specific functions of the local routing execution entity 901 and the charging server 902 and the delivery manner of the message are described in detail in the method embodiment section, and are not described herein.

In the embodiment of the present invention, 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.

The foregoing description of the charging method, device, and network system of the local routing service provided by the embodiments of the present invention is only for assisting in understanding the method and core idea of the present invention. Meanwhile, for those skilled in the art. According to the idea of the present invention, in the specific embodiment and application range There is a change in the above, and the contents of the present specification should not be construed as limiting the invention.

Claims

Rights request

A charging method for a local routing service, which is characterized by comprising:

And sending the first charging statistics, so that the charging server charges the locally routed service flow according to the first charging statistical information.

2. The method of claim 1 wherein

The method also includes:

The local route execution entity acquires charging context information;

The sending the first charging statistics information is specifically:

The local route execution entity sends the first charging statistics according to the charging context information.

3. The method of claim 2, wherein

The local routing execution entity obtains the charging context information specifically:

The local route execution entity acquires charging context information from a charging proxy;

Or,

The local routing enforcement entity obtains charging context information from a packet data network gateway.

4. The method of claim 2, wherein

The charging context information includes a reporting time interval;

The sending the first charging statistics information is specifically:

The local routing execution entity periodically sends the first charging statistics according to the reporting time interval in the charging context information; the first charging statistics information includes: charging the service flow locally routed by the user The statistical result of the related information, or the first charging statistical information includes: a local routing indication and a statistical result of charging related information of a service flow that is locally routed by the user;

Or,

The charging context information includes a charging server address and a charging identifier corresponding to the service flow of the local route;

The sending the first charging statistics information is specifically:

Sending, by the local routing execution entity, the charging server 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.

5. The method of claim 1 wherein:

The sending the first charging statistics information is specifically:

The local routing execution entity directly sends the first charging statistics information to the charging server; or

The local routing execution entity sends the first charging statistics message to the charging server through the charging proxy or

The local routing execution entity sends the first charging statistics information to the charging server by using the charging client.

6. A method according to any one of claims 1-5, characterized in that

The method further includes: the local routing execution entity performing statistics on the charging related information of the service flow that is not locally routed by the user, and obtaining the second charging statistical information; the second charging statistical 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; and sending the second charging statistical information.

7. A local routing execution entity, comprising:

The local routing execution entity according to claim 7, wherein the local routing execution entity further includes:

a context obtaining unit, configured to obtain charging context information;

The sending unit is configured to send the first charging statistics according to the charging context information

9. The local routing enforcement entity of claim 8 wherein:

The charging context information includes: a reporting time interval;

The sending unit is configured to periodically send according to the reporting time interval in the charging context information. And sending the first charging statistic information; the first charging statistic information includes: a statistical result of the charging related information of the service flow that is locally routed by the user, or the first charging statistic information includes: a statistical result indicating the charging related information of the service flow that is locally routed to the user;

Or,

The sending unit is configured to send the first charging statistical information to the charging server according to the charging server address, where the first charging statistical information includes: the charging identifier and a local to the user The statistical result of the billing related information of the routed service flow.

10. The local routing enforcement entity of claim 7, wherein:

The local routing execution entity further includes:

The non-local routing service flow information statistics unit is configured to perform statistics on the charging related information of the service flow that is not locally routed by the user, and obtain the second charging statistical information;

The sending unit is configured to send a charging information update request message that includes the first charging statistical information and the second charging statistical information, where the second charging statistical information includes: a non-local routing indication and a non-local The statistical result of the billing related information of the service flow of the local route.

A network system, comprising: a local routing execution entity according to any one of claims 7-10; and a service for receiving the first charging statistical information and locally routing according to the first charging statistical information A billing server that performs billing.