WO2018035867A1 - 一种计费方法及装置 - Google Patents

一种计费方法及装置 Download PDF

Info

Publication number
WO2018035867A1
WO2018035867A1 PCT/CN2016/097012 CN2016097012W WO2018035867A1 WO 2018035867 A1 WO2018035867 A1 WO 2018035867A1 CN 2016097012 W CN2016097012 W CN 2016097012W WO 2018035867 A1 WO2018035867 A1 WO 2018035867A1
Authority
WO
WIPO (PCT)
Prior art keywords
charging
user
gateway device
information
local service
Prior art date
Application number
PCT/CN2016/097012
Other languages
English (en)
French (fr)
Inventor
何光伟
周军平
夏渊
孙晓东
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to PCT/CN2016/097012 priority Critical patent/WO2018035867A1/zh
Publication of WO2018035867A1 publication Critical patent/WO2018035867A1/zh

Links

Images

Classifications

    • 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 and apparatus.
  • the EPS network includes an Evolved Universal Mobile Telecommunication System Territorial Radio Access Network (E-UTRAN) and an Evolved Packet Core Network (EPC).
  • E-UTRAN Evolved Universal Mobile Telecommunication System Territorial Radio Access Network
  • EPC Evolved Packet Core Network
  • the EPS network can only provide packet switching (English: Packet Switched, PS for short).
  • the current EPC includes a service gateway (English: Serving Gateway, SGW for short), a Packet Data Network Gateway (PGW), and a Mobility Management Entity (MME). Network element.
  • SGW Serving Gateway
  • PGW Packet Data Network Gateway
  • MME Mobility Management Entity
  • the network elements such as the SGW and the PGW are deployed in the provincial trunk line transmission network.
  • the terminal device accesses the local network through the Internet (Internet)
  • the data needs to pass through the network elements such as the SGW and the PGW, resulting in the data of the terminal device.
  • the transmission path is cumbersome, resulting in inefficient transmission and poor user experience.
  • a gateway device may be deployed in an access network or a metropolitan area network that is closer to the terminal device, such as a base station location of the terminal device, and a local application server is deployed, and the deployed gateway device is used to connect the terminal.
  • the local service generated by the device accessing the local network is offloaded to the local application server, which shortens the data transmission path of the local service user and saves the transmission resources of the carrier network.
  • the other non-local services are transparently transmitted to the centralized gateway device.
  • the existing charging is generally based on the bearer granularity, such as the generation of offline charging bills, the quota application for online charging, and the like.
  • the charging of a service carrying all users is generally implemented by the same gateway device (such as PGW), but the local application proposed above is proposed.
  • the deployment plan of the server, the services on the same bearer, including the local service and the non-local service, will pass through different gateway devices, so that two different gateway devices need to be charged for different services on the same bearer, and two The billing information is summarized. Therefore, the local gateway and the non-local service billing by the same gateway device (such as PGW) in the prior art cannot guarantee the accuracy of the billing result.
  • the embodiment of the invention provides a charging method and device, which are used to solve the problem that the accuracy of the charging result cannot be guaranteed in the prior art.
  • an embodiment of the present invention provides a charging method, including:
  • the second gateway device identifies the local service data flow corresponding to the local service of the user in the received service data flow, and performs charging for the identified local service data flow to obtain second charging information, where the second charging is performed.
  • the information carries a second charging identifier, where the second charging identifier is used to identify charging information corresponding to the local service of the user.
  • the second gateway device Transmitting, by the second gateway device, the other service data flows of the received service data stream of the user, except the identified local service data flow, to the first gateway device, where the first gateway device receives the user's
  • charging is performed according to the case where the user sends the non-local service data flow, and the first charging information is generated, where the first charging information carries the first charging identifier, and the first charging is performed.
  • the information includes charging information for charging the non-local service of the user, where the first charging identifier is used to identify charging information corresponding to the non-local service of the user; the first gateway device A billing information is sent to the billing system.
  • the first gateway device charges the non-local service data stream of the user to generate the first charging information, and uses the first charging identifier to mark the first charging information and then sends the charging system, thereby After receiving the marked first charging information and the second charging information, the fee system can determine that the local service and the non-local service are different bearers according to the charging identifier, thereby performing separate charging and solving the same The problem that the different services carried are not accurately charged at different charging control points.
  • the second charging identifier is that the second gateway device receives the pre-received by the first gateway device.
  • the method before the first gateway device receives the second charging information that is sent by the second gateway device and is used for charging the local service data stream of the user, the method further includes:
  • the first gateway device generates the first charging identifier and the second charging identifier for the user
  • the first gateway device sends the second charging identifier to the second gateway device.
  • the second gateway device performs charging for the identified local service to obtain the second charging information, including:
  • the second gateway device collects statistical information for the user to use the identified local service data flow, and generates a charging bill based on the statistical information;
  • the second gateway device collects statistical information for the user to use the identified local service data flow, and generates online charging quota application information based on the statistical information;
  • the second gateway device collects statistical information for the user to use the identified local service data flow, and generates AAA charging information based on the statistical information.
  • an embodiment of the present invention further provides a charging method, including:
  • the second gateway device identifies the local service data flow corresponding to the local service of the user in the received service data flow, and obtains the second statistical information according to the situation that the user uses the identified local service data flow;
  • the gateway device sends the second statistic information to the first gateway device
  • the first gateway device When the first gateway device receives the second statistics information that is sent by the second gateway device and is obtained by using the local service data flow, the first gateway device generates the second charging information based on the second statistical information. And sending the second charging information to the charging system by using the second charging identifier, where the second charging identifier is used to identify the charging corresponding to the local service of the user. information.
  • the second gateway device transparently transmits the other service data flows of the received service data stream of the user to the first gateway device.
  • the first gateway device When receiving the non-local service data flow of the user, the first gateway device performs charging for the case where the user uses the non-local service data flow, and generates first charging information, where the first charging information carries The first charging identifier is used to identify charging information corresponding to the non-local service of the user; the first gateway device sends the first charging information to the charging system.
  • the method before the first gateway device receives the second statistics sent by the second gateway device, the method further includes:
  • the first gateway device generates the first charging identifier for the user and the second charging identifier for the user.
  • the implementation of the present invention provides a charging apparatus, where the charging apparatus is applied to a first gateway device, including:
  • a receiving unit configured to receive second charging information that is sent by the second gateway device and that is obtained by charging the local service data stream of the user;
  • a sending unit configured to send the second charging information to the charging system;
  • the second charging information carries a second charging identifier, where the second charging identifier is used to identify the local service corresponding to the user Billing information;
  • the receiving unit is further configured to receive a non-local service data flow of the user
  • a processing unit configured to perform charging according to the case that the user sends a non-local service data flow, and generate first charging information, where the first charging information carries a first charging identifier, where the first charging information includes The charging information used for charging the non-local service of the user, where the first charging identifier is used to identify charging information corresponding to the non-local service of the user;
  • the sending unit is further configured to send the first charging information to a charging system.
  • the processing unit is further configured to: before the receiving unit receives the second charging information that is sent by the second gateway device and is charged for the local service data flow of the user, The user generates the first charging identifier and the second charging identifier;
  • the sending unit is further configured to send the second charging identifier to the second gateway device.
  • the implementation of the present invention provides a charging apparatus, where the charging apparatus is applied to a first gateway device, including:
  • the communication interface is configured to receive and send data
  • a memory for storing program code executed by the processor
  • the processor is configured to execute the program code stored in the memory, and is specifically used to implement the functions implemented by the device of any one of the third aspect or the third aspect.
  • the embodiment of the present invention further provides a charging device, where the device is applied to the second gateway device, including:
  • a receiving unit configured to receive a service data flow of the user
  • a processing unit configured to identify a local service data flow corresponding to a local service of the user in the service data flow received by the receiving unit, and perform charging for the identified local service data flow to obtain second charging information, where
  • the second charging information carries a second charging identifier, where the second charging identifier is used to identify charging information corresponding to the local service of the user;
  • a sending unit configured to send, to the first gateway device, second charging information that is processed by the processing unit
  • the sending unit is further configured to transparently transmit, to the first gateway device, other service data flows except the identified local service data stream in the service data stream of the user received by the receiving unit.
  • the second charging identifier is that the receiving unit is previously received by the first gateway device.
  • the processing unit when the second charging information is obtained by charging for the identified local service, the processing unit is specifically configured to:
  • online charging For online charging, statistics are obtained for the user to use the identified local service data flow, and online charging quota application information is generated based on the statistical information; or
  • AAA charging For AAA charging, statistical information is obtained for the user to use the identified local service data flow, and AAA charging information is generated based on the statistical information.
  • the embodiment of the present invention further provides a charging device, where the device is applied to the second gateway device, including:
  • the communication interface is configured to receive and send data
  • a memory for storing program code executed by the processor
  • the processor is configured to execute the program code stored in the memory, and is specifically used to implement the functions implemented by the device according to any one of the fifth aspect or the fifth aspect.
  • an embodiment of the present invention provides a charging apparatus, where the apparatus is applied to a first gateway device, including:
  • a receiving unit configured to receive second statistical information that is sent by the second gateway device and collected by the user for using the local service data flow;
  • a processing unit configured to generate second charging information based on the second statistical information received by the receiving unit, and mark the second charging information by using a second charging identifier; the second charging identifier is used to Identifying charging information corresponding to the local service of the user;
  • a sending unit configured to send the marked second charging information to the charging system
  • the processing unit is further configured to: when the receiving unit receives the non-local service data flow of the user, perform charging for the user to use the non-local service data flow, and generate first charging information, where The first charging information carries a first charging identifier, where the first charging identifier is used to identify charging information corresponding to the non-local service of the user;
  • the sending unit is further configured to send the first charging information processed by the processing unit to the charging system.
  • the processing unit before the receiving unit receives the second statistical information sent by the second gateway device, the processing unit is further configured to generate the first charging identifier for the user and The user generates the second charging identifier.
  • an embodiment of the present invention further provides a charging apparatus, where the apparatus is applied to the first Gateway devices, including:
  • the communication interface is configured to receive and send data
  • a memory for storing program code executed by the processor
  • the processor is configured to execute the program code stored in the memory, and is specifically used to implement the functions implemented by the device according to any one of the seventh aspect or the seventh aspect.
  • a ninth aspect, the embodiment of the present invention provides a charging device, where the device is applied to a second gateway device, including:
  • a receiving unit configured to receive a service data flow of the user
  • a processing unit configured to identify a local service data flow corresponding to a local service of the user in the service data flow received by the receiving unit, and obtain statistics on the second statistical information for the user to use the identified local service data flow ;
  • a sending unit configured to send, to the first gateway device, second statistical information obtained by the processing unit
  • the sending unit is further configured to transparently transmit, by the receiving unit, the service data stream of the user, other than the identified local service data, to the first gateway device.
  • the embodiment of the present invention further provides a charging device, where the device is applied to the second gateway device, including:
  • the communication interface is configured to receive and send data
  • a memory for storing program code executed by the processor
  • the processor is configured to execute the program code stored in the memory, and is specifically used to implement the functions implemented by the device according to any one of the ninth aspect or the ninth aspect.
  • FIG. 1 is a schematic structural diagram of a communication network according to an embodiment of the present invention.
  • FIG. 2 is a schematic structural diagram of another communication network according to an embodiment of the present invention.
  • FIG. 3 is a schematic structural diagram of another communication network according to an embodiment of the present disclosure.
  • FIG. 4 is a flowchart of a charging method according to an embodiment of the present invention.
  • FIG. 5 is a schematic diagram of a charging process according to an embodiment of the present disclosure.
  • FIG. 6 is a flowchart of another charging method according to an embodiment of the present invention.
  • FIG. 7 is a schematic diagram of another charging process according to an embodiment of the present invention.
  • FIG. 8 is a schematic diagram of a first gateway device according to an embodiment of the present disclosure.
  • FIG. 9 is a schematic diagram of another first gateway device according to an embodiment of the present disclosure.
  • FIG. 10 is a schematic diagram of a second gateway device according to an embodiment of the present disclosure.
  • FIG. 11 is a schematic diagram of another second gateway device according to an embodiment of the present disclosure.
  • FIG. 12 is a schematic diagram of still another first gateway device according to an embodiment of the present disclosure.
  • FIG. 13 is a schematic diagram of still another first gateway device according to an embodiment of the present disclosure.
  • FIG. 14 is a schematic diagram of still another second gateway device according to an embodiment of the present disclosure.
  • FIG. 15 is a schematic diagram of still another second gateway device according to an embodiment of the present invention.
  • the embodiment of the invention provides a charging method and device, which are used to solve the problem that the accuracy of the charging result cannot be guaranteed in the prior art.
  • the method and the device are based on the same inventive concept. Since the principles of the method and the device for solving the problem are similar, the implementation of the device and the method can be referred to each other, and the repeated description is not repeated.
  • FIG. 1 a schematic diagram of a communication network architecture to which the charging method of the embodiment of the present invention can be applied is first described. It should be understood that the embodiments of the present invention are not limited to the communication network shown in FIG. 1.
  • the apparatus in FIG. 1 may be hardware, or may be functionally divided software or a structure of the above two.
  • the communication network architecture to which the charging method of the embodiment of the present invention can be applied may include a terminal device (English: User Equipment, UE for short), a base station, a first gateway device, a second gateway device, and mobility management. Entity (English: Mobility Management Entity, MME for short) and local application server, as well as the Internet (Internet) and billing system.
  • the terminal device can communicate with the MME through the base station, and the second gateway device is transparent to other network elements except the first gateway device.
  • the terminal sends the service data flow to the first gateway device by using the base station, the second gateway needs to go through the second gateway.
  • the second gateway device may forward the local service data flow interception in the service data flow to the local application server, and transparently transmit the non-local service data flow to the first gateway device.
  • the second gateway device and the dashed line of the first gateway device and the MME indicate that one of the first gateway device or the second gateway device can communicate with the MME.
  • the local application server can communicate with the second gateway device.
  • the second gateway device may be deployed in an access network or a metropolitan area network of the terminal device.
  • the first gateway device may send the generated charging information to the charging system.
  • the terminal device may communicate with one or more core networks (Core Network) via a radio access network (English: Radio Access Network, RAN for short), and the UE may also be referred to as an access terminal and a user.
  • Core Network Core Network
  • RAN Radio Access Network
  • the UE can be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, and a personal digital processing (English: Personal Digital) Assistant, referred to as PDA), a handheld device with wireless communication capabilities, a computing device or other processing device connected to a wireless modem, an in-vehicle device, a wearable device, and a terminal device in a future 5G network.
  • SIP Session Initiation Protocol
  • WLL Wireless Local Loop
  • PDA Personal Digital Processing
  • the base station may be a base station in a Global System for Mobile communication (GSM) system or a Code Division Multiple Access (CDMA) system.
  • Base Transceiver Station which may also be a base station (NodeB) in a Wideband Code Division Multiple Access (WCDMA) system, or an evolved base station in an LTE system ( English: Evolutional Node B, referred to as: eNB or eNodeB), or not
  • the present invention is not limited to the base station equipment and the small base station equipment in the 5G network.
  • the base station may represent the access network.
  • the MME is a control plane network element, and is mainly responsible for control plane functions such as mobility management and session management of the user equipment.
  • the local application server (English: Local Application Server, LAPP for short) is essentially an application server.
  • the application server and the terminal device are in a local geographical scope (such as a school, a factory, and an organization), the application server may be referred to as a local application server of the terminal device.
  • the terminal device can access the local application server through the base station and the second gateway device to access the local network without accessing the local network through the first gateway device and the Internet.
  • the local application server is usually deployed by the application service provider near the terminal device (such as the access network location). Therefore, the local service data flow of the terminal device can be directly routed from the second gateway device to the local application server, and the local service data is generated.
  • the direct routing mode of a flow can be referred to as local transmission.
  • FIG. 2 is a more specific schematic architectural diagram of the communication network shown in FIG. 1.
  • the apparatus in FIG. 2 may be hardware, or may be functionally divided software or a structure of both.
  • the second gateway device can be transparently connected to the S1-U interface, and all user plane traffic must pass through the second gateway device, and the second gateway device and the surrounding network element (such as MME, meter)
  • the fee system has no external interface, that is, the second gateway device is invisible to the surrounding network elements.
  • the first gateway device can perform control management and the like on the second gateway device through the control interface Sx interface.
  • the second gateway device may be deployed in combination with an access network (such as a base station) or may be deployed to the metropolitan area network.
  • the first gateway device may have the functions of a serving gateway (English: Serving Gate Way, SGW for short) and a packet data gateway (English: Packet Data Network Gateway, PGW for short).
  • a serving gateway English: Serving Gate Way, SGW for short
  • a packet data gateway English: Packet Data Network Gateway, PGW for short
  • the SGW and the PGW have both control plane and user plane functions, and mainly participate in mobility management and session management, such as access control, data forwarding, and charging.
  • the SGW and the PGW can be separately set, and the interface between them can be a standard S5 interface; the SGW and the PGW network element can also be combined.
  • the second gateway device is opposite to the first gateway.
  • the device is located closer to the terminal device, that is, the second gateway device is located in a remote location in the entire network. Therefore, the second gateway device may be referred to as a remote gateway (English: Remote Gateway, RGW for short), and the first gateway may be used.
  • the device is called a centralized gateway (English: Centralized Gateway, referred to as CGW).
  • FIG. 3 is another more detailed schematic architecture diagram of the communication network shown in FIG. 1.
  • the apparatus in FIG. 3 may be hardware, or may be functionally divided software or a structure of both.
  • the second gateway device may be deployed with an access network (such as a base station) or may be deployed in a metropolitan area network. At this time, the second gateway device is visible to the neighboring network elements (such as the MME and the eNB), and the S11 interface may exist between the second gateway device and the MME, so that the second gateway device and the MME can directly exchange signaling through the S11 interface.
  • the MME may select a second gateway device that serves the terminal device.
  • the first gateway device and the second gateway device have a signaling plane interface S5-C and a data plane interface S5-U, so that the first gateway device and the second gateway device perform signaling interaction through the S5-C. Data interaction through S5-U.
  • the second gateway device may have the function of the SGW and the local service data stream identification function and the offload function, and the first gateway device may have the function of the PGW.
  • the second gateway device since the second gateway device is closer to the terminal device than the first gateway device, that is, the second gateway device is located in a remote location in the entire network, the second gateway device can be used.
  • the first gateway device can be referred to as a CGW.
  • the embodiment of the present invention proposes that only two charging bearers are presented to the charging system in the first gateway device, and only one bearer is presented to other network elements (such as the MME), and one bearer for non-local service charging, and another A bearer for local service billing.
  • the bearer used for charging the non-local service may be referred to as a “primary bearer”, and the bearer used for local service charging may be referred to as a “shadow bearer”.
  • the shadow bearer is only used for charging, and only the first gateway device and the charging network element know that other network elements only know the primary bearer.
  • a charging identifier is assigned to the primary bearer, and a charging identifier is assigned to the shadow bearer, and the two charging identifiers are different.
  • the charging identifier used to identify the charging for the local service is referred to as a second charging identifier, that is, the charging identifier corresponding to the shadow bearer, which is used to identify the non-local
  • the charging identifier of the service charging is called the first charging identifier. That is, the charging identifier corresponding to the primary bearer.
  • FIG. 4 is a schematic flowchart of a charging method according to an embodiment of the present disclosure, where the method includes:
  • the second gateway device identifies the local service data flow corresponding to the local service of the user in the received service data flow, and performs charging for the identified local service data flow to obtain the second charging information.
  • the second charging information carries a second charging identifier, where the second charging identifier is used to identify charging information corresponding to the local service of the user.
  • the second gateway device forwards the local service data flow to the local application server when identifying the local service data flow corresponding to the local service of the user in the received service data flow.
  • the second gateway device sends the second charging information to the first gateway device.
  • the first gateway device when the first gateway device receives the second charging information that is sent by the second gateway device and is charged for the user's local service data flow, the first gateway device sends the second charging information to Billing System.
  • the second gateway device transparently transmits, to the first gateway device, the service data stream of the received service data stream of the user other than the identified local service data stream.
  • the first gateway device When receiving the non-local service data flow of the user, the first gateway device performs charging according to the situation that the user sends a non-local service data flow, and generates first charging information.
  • the first charging information includes a first charging identifier, where the first charging information includes charging information used for charging a non-local service of the user, where the first charging identifier is used to identify the user. Billing information corresponding to the non-local service.
  • the first gateway device sends the first charging information to a charging system.
  • the second charging identifier is that the second gateway device receives the pre-received by the first gateway device.
  • the first gateway device Before the first gateway device receives the second charging information that is sent by the second gateway device and is charged for the user's local service data flow, the first gateway device generates the first charging identifier for the user and The second charging identifier is sent by the first gateway device to the second gateway device.
  • the MME creates a default bearer for the user, and the default bearer remains connected until the terminal device detaches the network, and the MME sends the information corresponding to the default bearer to the first gateway. device.
  • the information corresponding to the default bearer includes information such as a Bearer ID.
  • the first gateway device allocates a first charging identifier based on the default bearer, and when the online charging is involved, the first session identifier (Session-Id) is also allocated, so that the first gateway device can perform non-local service through the first session identifier. Online billing quota management.
  • the second charging identifier is allocated, and the created shadow bearer is used for charging only, and the allocated second charging identifier is used to identify the local service. Fee information.
  • the second charging identifier is sent to the second gateway device, so that the second gateway device can perform charging for the local service data flow for the user and generate the second charging. And transmitting the second charging information to the first gateway device by using the second charging identifier, so that the first gateway device forwards the second charging information to the charging system.
  • the first gateway device also needs to allocate a second session identifier (Session-Id).
  • An online charging quota management for performing local services through the second session identifier After receiving the first charging information and the second charging information, the charging system can determine that the local service and the non-local service are different bearers according to the charging identifier, thereby performing separate charging, and solving the problem. The problem that the different services of the same bearer are not accurately charged at different charging control points.
  • the charging involved in the embodiments of the present invention may include online charging, offline charging, and AAA charging.
  • the second gateway device performs charging for the identified local service to obtain the second charging information, which can be implemented as follows:
  • the second charging information is an offline charging bill for the local service of the user
  • the second gateway device collects statistical information for the identified local service data flow, and generates charging based on the statistical information.
  • the bill is logged, and the offline billing CDR is marked using the second billing identifier.
  • the second gateway device forwards the offline charging bill carrying the second charging identifier to the offline charging system. (OFCS).
  • the second charging information is online charging quota application information for the local service of the user, and the second gateway device collects statistics for the user using the identified local service data flow, and is based on the statistics.
  • the statistics information generates online charging quota application information, and uses the second charging identifier to mark the online charging quota application information.
  • the second gateway device sends the online charging quota application information to an online charging system (OCS) for applying for an online charging quota.
  • OCS online charging system
  • the second charging information is AAA charging information for the local service of the user
  • the second gateway device collects statistical information for the user to use the identified local service data flow, and based on the calculation The fee statistics generate AAA billing information.
  • the second gateway device before the second gateway device identifies the local service data flow corresponding to the local service of the user in the received service data flow, determining charging policy information for the local service of the user, so that the second When the gateway device identifies the local service data flow corresponding to the local service of the user in the received service data flow, the second gateway device performs charging generation for the local service of the user based on the charging policy information. Two billing information.
  • the charging policy information includes at least one of the following charging methods:
  • billing it can be based on duration, traffic, or duration and traffic, or events.
  • the charging policy information further includes: online charging quota information; or includes: online charging quota information and a quota re-application threshold, or includes online charging quota information and charging information reporting conditions.
  • the charging policy information may also include other policy information for charging by the OCS.
  • the online charging quota information for example, it may be 500M traffic or 50 MMS in the monthly subscription of the user, and the quota re-application threshold may be that the remaining traffic is less than 50M, or the remaining number of MMS is five.
  • the charging policy information further includes a charging information reporting condition corresponding to offline charging.
  • the charging policy information further includes charging information corresponding to AAA charging. Report conditions.
  • FIG. 5 is a schematic diagram of a charging method for a local service data flow according to an embodiment of the present invention. The description is made by taking the first gateway device as the CGW and the second gateway device as the RGW.
  • the CGW creates a primary bearer for the terminal device, and allocates a charging-Id1 corresponding to the bearer.
  • the CGW creates a shadow bearer for the local service, and allocates a new Charging-Id2 for the shadow bearer. For online charging, the CGW allocates a Session-Id or the like for the online charging session to the shadow bearer.
  • the CGW performs charging processing based on different bearers (based on the shadow bearer and the primary bearer respectively), that is, performs charging management based on different charging identifiers, such as pre-application for online accounting to the OCS. Fee quotas, etc.
  • the CGW pre-applies an online charging quota to the OCS based on the Charging-Id2.
  • the CGW notifies the RGW to activate, and sends the charging policy information for charging the local service data flow to the RGW.
  • the accounting policy information includes charging mode, online charging quota, Charging ID2, and so on.
  • S505 The user initiates an uplink service data flow by using the UE.
  • the RGW identifies the uplink service data flow as a local service data flow based on the local traffic distribution policy.
  • the local offloading policy can be configured locally in the RGW or in advance by the PCRF.
  • step S507 If the online charging process is required to be performed for the local service data flow, and the online charging quota pre-application is not performed in step S503, the RGW applies for the online charging quota to the OCS through the CGW.
  • the RGW performs local offloading based on the local offloading policy, and sends the local service data stream of the user to the LAPP process. If the RGW identifies the uplink service data flow as a non-local service data flow based on the local traffic distribution policy, the RGW directly transmits the non-local service data flow to the CGW for processing.
  • the RGW performs statistical statistics according to the charging policy information corresponding to the local service data flow, and generates charging information based on the statistical information, where the generated information is generated.
  • the fee information carries Charging-Id2.
  • the RGW For online charging, the RGW generates online charging quota application information based on the statistical information, and the online charging quota application information carries Charging-Id2.
  • the RGW For offline charging, the RGW generates an offline charging bill based on the statistical information, and the offline charging bill carries the Charging-Id2.
  • the RGW For AAA charging, the RGW generates AAA charging information based on the statistical information, and the AAA charging information carries Charging-Id2.
  • the CGW reports the online charging quota application information of the local service to the OCS through the shadow bearer, and receives the online charging quota information that is newly sent by the OCS.
  • the CGW replies to the RGW with a response to the charging of the local service, and carries the online charging quota information that is newly sent by the OCS.
  • the CGW performs the charging information statistics, the CDR generation and the reporting, the online charging quota application, and the like, which are similar to the prior art. Therefore, the description of the embodiments of the present invention is not repeated.
  • FIG. 6 is a schematic flowchart of a charging method according to an embodiment of the present disclosure, where the method includes:
  • the second gateway device identifies the local service data flow corresponding to the local service of the user in the received service data flow, and obtains the second statistical information according to the situation that the user uses the identified local service data flow.
  • the second gateway device forwards the local service data flow to the local application server when identifying the local service data flow corresponding to the local service of the user in the received service data flow.
  • the second gateway device sends the second statistics information to the first gateway device.
  • the first gateway device receives, by using the second gateway device, the local usage for the user.
  • the first gateway device When the second statistical information obtained by the statistics is obtained, the first gateway device generates second charging information based on the second statistical information, and marks the second charging information by using the second charging identifier. Then sent to the billing system.
  • the second charging identifier is used to identify charging information corresponding to the local service of the user.
  • the second gateway device transparently transmits the other service data flows of the received service data stream of the user except the identified local service data stream to the first gateway device.
  • the first gateway device When receiving the non-local service data flow of the user, the first gateway device performs charging according to the situation that the user uses the non-local service data flow, and generates first charging information.
  • the first charging information includes a first charging identifier, where the first charging information includes charging information used for charging a non-local service of the user, where the first charging identifier is used to identify the user. Billing information corresponding to the non-local service.
  • the first gateway device sends the first charging information to a charging system.
  • the MME creates a default bearer for the user, and the default bearer remains connected until the terminal device detaches the network, and the MME sends the information corresponding to the default bearer to the first gateway. device.
  • the information corresponding to the default bearer includes information such as a Bearer ID.
  • the first gateway device allocates a first charging identifier based on the default bearer; when the online charging is involved, the first session identifier (Session-Id) is also allocated, so that the first gateway device can perform the non-local service through the first session identifier. Online billing quota management.
  • the second charging identifier is allocated, and the created shadow bearer is used for charging only, and the allocated second charging identifier is used to identify the local service. Fee information.
  • the second charging information is an offline charging bill for the local service of the user, and when the first gateway device receives the second statistical information, generating an offline charging bill and using the second charging identifier
  • the offline charging bill is marked and sent to the offline charging system (OFCS).
  • the second charging information is online charging quota application information for the local service of the user, and when the first gateway device receives the second statistical information, generates online charging quota application information, and uses the second The charging identifier marks the online charging quota application information and sends it to the online The Billing System (OCS) is used to apply for online billing quotas.
  • OCS The Billing System
  • the second charging information is AAA charging information for the local service of the user, and when the first gateway device receives the second statistical information, generates AAA charging information, and uses the second charging identifier.
  • the AAA charging information is marked and sent to the AAA charging server.
  • the second gateway device before the second gateway device identifies the local service data flow corresponding to the local service of the user in the received service data flow, determining charging policy information for the local service of the user, so that the second When the gateway device identifies the local service data flow corresponding to the local service of the user in the received service data flow, the second gateway device performs, according to the charging policy information, the local service data flow for the user. Statistics get the second statistical information.
  • the charging policy information includes at least one of the following charging methods:
  • billing it can be based on duration, traffic, or duration and traffic, or events.
  • the charging policy information further includes: online charging quota information; or includes: online charging quota information and a quota re-application threshold, or includes online charging quota information and charging information reporting conditions.
  • the charging policy information may also include other policy information for charging by the OCS.
  • the online charging quota information for example, it may be 500M traffic or 50 MMS in the monthly subscription of the user, and the quota re-application threshold may be that the remaining traffic is less than 50M, or the remaining number of MMS is five.
  • the charging policy information further includes a charging information reporting condition corresponding to offline charging.
  • the charging policy information further includes a charging information reporting condition corresponding to the AAA charging.
  • FIG. 7 is a schematic diagram of a charging method for a local service data flow according to an embodiment of the present invention. The description is made by taking the first gateway device as the CGW and the second gateway device as the RGW.
  • the CGW creates a primary bearer for the user, and allocates the Host the corresponding charging-Id1.
  • the CGW creates a shadow bearer for the local service, and allocates a new Charging-Id2 for the shadow bearer. For online charging, the CGW allocates a Session-Id or the like for the online charging session to the shadow bearer.
  • the CGW performs charging processing based on different bearers (based on the shadow bearer and the primary bearer respectively), that is, performs charging management based on different charging identifiers, such as pre-application for online accounting to the OCS. Fee quotas, etc.
  • the CGW pre-applies an online charging quota to the OCS based on the Charging-Id2.
  • the CGW notifies the RGW to activate, and sends the charging policy information for charging the local service data flow to the RGW.
  • the accounting policy information includes a charging mode and an online charging quota.
  • the user initiates an uplink service data flow by using the UE.
  • the RGW identifies the uplink service data flow as a local service data flow based on the local traffic distribution policy.
  • the local offloading policy can be configured locally in the RGW or in advance by the PCRF.
  • the RGW performs local offloading based on the local offloading policy, and sends the local service data stream of the user to the LAPP processing. If the RGW identifies the uplink service data flow as a non-local service data flow based on the local traffic distribution policy, the RGW directly transmits the non-local service data flow to the CGW for processing.
  • the RGW performs statistics according to the charging policy information corresponding to the local service data flow to obtain statistical information. Statistics include statistical session duration, traffic usage, and more.
  • the CGW During online charging, the CGW generates online charging quota application information based on the statistical information, and uses the Charging-Id2 to mark the online charging quota application information.
  • the CGW sends the online charging quota application information to the OCS.
  • the CGW For offline charging, the CGW generates an offline charging bill based on the statistical information, and marks the offline charging bill by using Charging-Id2.
  • the CGW sends the offline charging bill to the OFCS.
  • the CGW For AAA charging, the CGW generates AAA charging information based on the statistical information, and marks the AAA charging information by using Charging-Id2.
  • the CGW sends the AAA accounting information to the AAA accounting server.
  • the CGW replies to the RGW with a response to the charging of the local service, and carries the online charging quota information that is newly sent by the OCS.
  • the CGW performs the charging information statistics, the CDR generation and the reporting, the online charging quota application, and the like, which are similar to the prior art. Therefore, the description of the embodiments of the present invention is not repeated.
  • the present invention provides a charging device, which is applied to a first gateway device.
  • the device includes:
  • the receiving unit 801 is configured to receive, by the second gateway device, second charging information that is obtained by charging the local service data stream of the user.
  • the sending unit 802 is configured to send the second charging information to the charging system; the second charging information carries a second charging identifier, where the second charging identifier is used to identify the local service of the user. Corresponding billing information;
  • the receiving unit 801 is further configured to receive a non-local service data flow of the user;
  • the processing unit 803 is configured to perform charging according to the situation that the user sends a non-local service data flow, and generate first charging information, where the first charging information carries a first charging identifier, and the first charging information And including the charging information used for charging the non-local service of the user, where the first charging identifier is used to identify charging information corresponding to the non-local service of the user;
  • the sending unit 802 is further configured to send the first charging information to the charging system.
  • the processing unit 803 is further configured to: before the receiving unit 801 receives the second charging information that is sent by the second gateway device and is charged for the local service data stream of the user, The user generates the first charging identifier and the second charging identifier;
  • the sending unit 802 is further configured to send the second charging identifier to the second gateway device.
  • each functional unit in each embodiment of the present invention may be integrated into one processing. In the device, it may be physically present alone, or two or more units may be integrated in one unit.
  • the above integrated unit can be implemented in the form of hardware or in the form of a software function module.
  • the communication interface 901, the processor 902, and the memory 903 may be included.
  • the memory 903 is configured to store program code executed by the processor 902.
  • the communication interface 901 is for receiving and transmitting data.
  • the physical hardware corresponding to the receiving unit 801 and the sending unit 802 may be the communication interface 901, and the physical hardware corresponding to the processing unit 803 may be the processor 902. It is also possible that the receiving unit 801, the transmitting unit 802, and the processing unit 803 all correspond to the physical hardware processor 902, so that the processor 902 receives and transmits data through the communication interface 901.
  • the processor 902 can be a central processing unit (English: central processing unit, CPU for short), or a digital processing unit or the like.
  • the processor 902 is configured to execute the program code stored in the memory 903, specifically for performing the functions required by the receiving unit 801, the sending unit 802, and the processing unit 803.
  • connection medium between the communication interface 901, the processor 902, and the memory 903 is not limited in the embodiment of the present invention.
  • the communication interface 901, the processor 902, and the memory 903 are connected by a bus 904 in FIG. 9.
  • the bus is indicated by a thick line in FIG. 9, and the connection manner between other components is only schematically illustrated. , not limited to.
  • the bus can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only one thick line is shown in Figure 9, but it does not mean that there is only one bus or one type of bus.
  • the memory 903 may be a volatile memory (English: volatile memory), such as a random access memory (English: random-access memory, abbreviation: RAM); the memory 903 may also be a non-volatile memory (English: non-volatile memory)
  • read-only memory English: read-only memory, abbreviation: ROM
  • flash memory English: flash memory
  • hard disk English: hard disk drive, abbreviation: HDD
  • solid state drive English: solid-state drive , The abbreviation: SSD
  • memory 903 is any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer, but is not limited thereto.
  • the memory 903 may be a combination of the above memories.
  • an embodiment of the present invention further provides a charging device, where the device is applied to a second gateway device.
  • the device includes:
  • the receiving unit 1001 is configured to receive a service data flow of the user.
  • the processing unit 1002 is configured to identify a local service data flow corresponding to the local service of the user in the service data flow received by the receiving unit 1001, and perform charging for the identified local service data flow to obtain the second charging information.
  • the second charging information carries a second charging identifier, where the second charging identifier is used to identify charging information corresponding to the local service of the user;
  • the sending unit 1003 is configured to send, to the first gateway device, the second charging information that is processed by the processing unit 1002.
  • the sending unit 1003 is further configured to transparently transmit, to the first gateway device, other service data flows except the identified local service data stream in the service data stream of the user received by the receiving unit 1001.
  • the second charging identifier is that the receiving unit 1001 receives the information sent by the first gateway device in advance.
  • the processing unit 1002 when the second charging information is obtained by charging for the identified local service, the processing unit 1002 is specifically configured to:
  • online charging For online charging, statistics are obtained for the user to use the identified local service data flow, and online charging quota application information is generated based on the statistical information; or
  • AAA charging For AAA charging, statistical information is obtained for the user to use the identified local service data flow, and AAA charging information is generated based on the statistical information.
  • the division of the unit in the embodiment of the present invention is schematic, and is only a logical function division. In actual implementation, there may be another division manner, and in addition, various functions in various embodiments of the present invention. Units can be integrated into one processor, or they can exist physically alone, or two or more units can be integrated into one unit. The above integrated unit can be implemented in the form of hardware or in the form of a software function module.
  • a communication interface 1101, a processor 1102, and a memory 1103 may be included.
  • the memory 1103 is configured to store program code executed by the processor 1102.
  • the communication interface 1101 is for receiving and transmitting data.
  • the physical hardware corresponding to the receiving unit 1001 and the transmitting unit 1003 may be the communication interface 1101, and the physical hardware corresponding to the processing unit 1002 may be the processor 1102. It is also possible that the receiving unit 1001, the transmitting unit 1003, and the processing unit 1002 all correspond to the physical hardware processor 1102, so that the processor 1102 receives and transmits data through the communication interface 1101.
  • the processor 1102 can be a CPU, or a digital processing unit or the like.
  • the processor 1102 is configured to execute the program code stored by the memory 1103, specifically for performing functions required by the receiving unit 1001, the sending unit 1003, and the processing unit 1002.
  • connection medium between the communication interface 1101, the processor 1102, and the memory 1103 is not limited in the embodiment of the present invention.
  • the communication interface 1101, the processor 1102, and the memory 1103 are connected by a bus 1104 in FIG. 11, and the bus is indicated by a thick line in FIG. 11, and the connection manner between other components is only schematically illustrated. , not limited to.
  • the bus can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only one thick line is shown in Figure 11, but it does not mean that there is only one bus or one type of bus.
  • the memory 1103 may be a volatile memory such as a RAM; the memory 1103 may also be a non-volatile memory such as a ROM, a flash memory, an HDD or an SSD, or the memory 1103 is capable of carrying or storing a desired program in the form of an instruction or data structure. Code and any other medium that can be accessed by a computer, but is not limited thereto.
  • the memory 1103 may be a combination of the above memories.
  • the embodiment of the present invention provides a charging device, where the device is applied to a first gateway device.
  • the device includes:
  • the receiving unit 1201 is configured to receive, by using the second gateway device, the local service for the user.
  • the second statistical information obtained by statistical calculation of the data stream;
  • the processing unit 1202 is configured to generate second charging information based on the second statistical information received by the receiving unit 1201, and mark the second charging information by using a second charging identifier; the second charging identifier Accounting information corresponding to the local service of the user;
  • the sending unit 1203 is configured to send the marked second charging information to the charging system
  • the processing unit 1202 is further configured to: when the receiving unit 1201 receives the non-local service data flow of the user, perform charging for the user to use the non-local service data flow, and generate first charging information.
  • the first charging information carries a first charging identifier, where the first charging identifier is used to identify charging information corresponding to the non-local service of the user;
  • the sending unit 1203 is further configured to send the first charging information processed by the processing unit 1202 to the charging system.
  • the processing unit 1202 before the receiving unit 1201 receives the second statistical information sent by the second gateway device, the processing unit 1202 is further configured to generate the first charging identifier for the user and The user generates the second charging identifier.
  • each functional unit in each embodiment of the present invention may be integrated into one processing. In the device, it may be physically present alone, or two or more units may be integrated in one unit.
  • the above integrated unit can be implemented in the form of hardware or in the form of a software function module.
  • a communication interface 1301, a processor 1302, and a memory 1303 may be included.
  • the memory 1303 is configured to store program code executed by the processor 1302.
  • the communication interface 1301 is for receiving and transmitting data.
  • the physical hardware corresponding to the receiving unit 1201 and the transmitting unit 1203 may be the communication interface 1301, and the physical hardware corresponding to the processing unit 802 may be the processor 1302. It is also possible that the receiving unit 1201, the transmitting unit 1203, and the processing unit 1202 all correspond to the physical hardware processor 1302, so that the processor 1302 receives and transmits data through the communication interface 1301.
  • the processor 1302 can be a CPU, or a digital processing unit or the like.
  • the program code for executing the storage of the memory 1303 is specifically for performing functions required to be performed by the receiving unit 1201, the transmitting unit 1203, and the processing unit 1202.
  • the specific connection medium between the communication interface 1301, the processor 1302, and the memory 1303 is not limited in the embodiment of the present invention.
  • the embodiment of the present invention is connected in FIG. 13 between the communication interface 1301, the processor 1302, and the memory 1303 via a bus 1304.
  • the bus is indicated by a thick line in FIG. 13, and the connection manner between other components is merely illustrative. , not limited to.
  • the bus can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only one thick line is shown in FIG. 13, but it does not mean that there is only one bus or one type of bus.
  • the memory 1303 may be a volatile memory such as a RAM; the memory 1303 may also be a non-volatile memory such as a ROM, a flash memory, an HDD or an SSD, or the memory 1303 is capable of carrying or storing a desired program in the form of an instruction or a data structure. Code and any other medium that can be accessed by a computer, but is not limited thereto.
  • the memory 1303 may be a combination of the above memories.
  • the embodiment of the present invention provides a charging device, where the device is applied to a second gateway device.
  • the device includes:
  • the receiving unit 1401 is configured to receive a service data flow of the user.
  • the processing unit 1402 is configured to identify a local service data flow corresponding to the local service of the user in the service data flow received by the receiving unit 1401, and obtain a second statistics for the case where the user uses the identified local service data flow. Statistics;
  • the sending unit 1403 is configured to send the second statistic information obtained by the processing unit 1402 to the first gateway device;
  • the sending unit 1403 is further configured to transparently transmit, to the first gateway device, other service data flows except the identified local service in the service data stream of the user received by the receiving unit 1401.
  • each functional unit in each embodiment of the present invention may be integrated into one processing. In the device, it may be physically present alone, or two or more units may be integrated in one unit.
  • the above integrated unit can be implemented in the form of hardware. It can also be implemented in the form of a software function module.
  • a communication interface 1501, a processor 1502, and a memory 1503 may be included.
  • the memory 1503 is configured to store program code executed by the processor 1502.
  • the communication interface 1501 is for receiving and transmitting data.
  • the physical hardware corresponding to the receiving unit 1401 and the sending unit 1403 may be the communication interface 1501
  • the physical hardware corresponding to the processing unit 802 may be the processor 1502. It is also possible that the receiving unit 1401, the transmitting unit 1403, and the processing unit 1402 all correspond to the physical hardware processor 1502, so that the processor 1502 receives and transmits data through the communication interface 1501.
  • the processor 1502 can be a CPU, or a digital processing unit or the like.
  • the processor 1502 is configured to execute the program code stored by the memory 1503, specifically for performing the functions required by the receiving unit 1401, the sending unit 1403, and the processing unit 1402.
  • connection medium between the communication interface 1501, the processor 1502, and the memory 1503 is not limited in the embodiment of the present invention.
  • the communication interface 1501, the processor 1502, and the memory 1503 are connected by a bus 1504 in FIG. 15.
  • the bus is indicated by a thick line in FIG. 15, and the connection manner between other components is only schematically illustrated. , not limited to.
  • the bus can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only one thick line is shown in Figure 15, but it does not mean that there is only one bus or one type of bus.
  • the memory 1503 may be a volatile memory such as a RAM; the memory 1503 may also be a non-volatile memory such as a ROM, a flash memory, an HDD or an SSD, or the memory 1503 is capable of carrying or storing a desired program in the form of an instruction or data structure. Code and any other medium that can be accessed by a computer, but is not limited thereto.
  • the memory 1503 may be a combination of the above memories.
  • embodiments of the present invention can be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment, or a combination of software and hardware. Moreover, the invention can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) including computer usable program code.
  • computer-usable storage media including but not limited to disk storage, CD-ROM, optical storage, etc.
  • the computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture comprising the instruction device.
  • the apparatus implements the functions specified in one or more blocks of a flow or a flow and/or block diagram of the flowchart.
  • These computer program instructions can also be loaded onto a computer or other programmable data processing device such that a series of operational steps are performed on a computer or other programmable device to produce computer-implemented processing for execution on a computer or other programmable device.
  • the instructions provide steps for implementing the functions specified in one or more of the flow or in a block or blocks of a flow diagram.

Landscapes

  • Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Telephonic Communication Services (AREA)

Abstract

一种计费方法及装置，用以解决现有技术中存在的无法保证计费结果的准确性的问题。该计费方法包括：第一网关设备接收到第二网关设备发送的针对用户的本地业务数据流计费得到的第二计费信息时，第一网关设备将第二计费信息发送给计费系统；第二计费信息携带第二计费标识，第二计费标识用于标识用户的本地业务对应的计费信息；第一网关设备接收到用户的非本地业务数据流时，根据用户发送非本地业务数据流的情况进行计费并生成第一计费信息，第一计费信息携带第一计费标识，第一计费信息包括用于对用户的非本地业务计费的计费信息，第一计费标识用于标识用户的非本地业务对应的计费信息；第一网关设备将第一计费信息发送给计费系统。

Description

一种计费方法及装置 技术领域
本发明涉及通信技术领域，尤其涉及一种计费方法及装置。
背景技术
随着第三代合作伙伴项目(3GPP)不断演进和发展，出现了演进分组系统(英文：Evolved Packet System，简称：EPS)这一概念。EPS网络包括演进通用移动通信系统陆地无线接入网(英文：Evolved Universal Mobile Telecommunication System Territorial Radio Access Network，简称：E-UTRAN)和演进分组核心网(英文：Evolved Packet Core Network，简称：EPC)，EPS网络只能提供分组交换(英文：Packet Switched，简称：PS)业务。
当前EPC中包括服务网关(英文：Serving Gateway，简称：SGW)、分组数据网络网关(英文：Packet Data Network Gateway，简称：PGW)和移动性管理实体(英文：Mobility Management Entity，简称：MME)等网元。
网络部署时，通常将SGW和PGW等网元部署在省内干线传输网中，从而在终端设备通过互联网(Internet)访问本地网络时，数据需要经过SGW和PGW等网元，导致终端设备的数据传输路径迂回冗长，从而导致传输效率低下，用户体验较差。
为了解决上述问题，可以在距离终端设备较近的接入网或者城域网中部署一个网关设备，例如终端设备的接入的基站位置，并部署本地应用服务器，部署的网关设备用于将终端设备访问本地网络产生的本地业务分流到本地应用服务器上，从而缩短本地业务用户数据传输路径，节省运营商网络的传输资源，针对其他非本地业务会被透传到集中式网关设备。
现有计费一般是基于承载粒度进行的，比如离线计费话单的生成、在线计费的配额申请等。目前的EPS系统中，一个承载上所有用户的业务的计费一般都是由同一个网关设备(如PGW)实现，但是针对上述提出的本地应用 服务器的部署方案，同一个承载上的业务包括本地业务和非本地业务，会通过不同的网关设备，这样需要通过两个不同的网关设备针对同一个承载上的不同业务进行计费，并将两处计费信息进行汇总，因此现有技术中由同一个网关设备(如PGW)来实现本地业务和非本地业务计费将无法保证计费结果的准确性。
发明内容
本发明实施例提供一种计费方法及装置，用以解决现有技术中存在的无法保证计费结果的准确性的问题。
第一方面，本发明实施例提供了一种计费方法，包括：
第二网关设备识别出接收到的业务数据流中的用户的本地业务对应的本地业务数据流；并针对识别出的本地业务数据流进行计费得到第二计费信息，所述第二计费信息携带第二计费标识，所述第二计费标识用于标识所述用户的本地业务对应的计费信息。第一网关设备接收到第二网关设备发送的针对用户的本地业务数据流计费得到的第二计费信息时，所述第一网关设备将所述第二计费信息发送给计费系统；其中，第二网关设备在识别出接收到的业务数据流中的用户的本地业务对应的本地业务数据流时，将所述本地业务数据流转发给本地应用服务器。
所述第二网关设备将接收到的用户的业务数据流中除识别出的本地业务数据流外的其他业务数据流透传给第一网关设备，所述第一网关设备接收到所述用户的非本地业务数据流时，根据所述用户发送非本地业务数据流的情况进行计费并生成第一计费信息，所述第一计费信息携带第一计费标识，所述第一计费信息包括用于对用户的非本地业务计费的计费信息，所述第一计费标识用于标识所述用户的非本地业务对应的计费信息；所述第一网关设备将所述第一计费信息发送给计费系统。
而第一网关设备会对用户的非本地业务数据流进行计费生成第一计费信息，并采用第一计费标识对第一计费信息进行标记后发送计费系统，从而计 费系统在收到标记后的第一计费信息和第二计费信息后，能够根据计费标识认为对本地业务以及非本地业务采用的是不同的承载，从而进行分开计费，解决了同一承载的不同业务在不同计费控制点计费不准确的问题。
在一种可能的设计中，所述第二计费标识是所述第二网关设备预先接收到由所述第一网关设备发送的。
具体的，第一网关设备接收到第二网关设备发送的针对用户的本地业务数据流计费得到的第二计费信息之前，所述方法还包括：
所述第一网关设备为所述用户生成所述第一计费标识以及所述第二计费标识；
所述第一网关设备将所述第二计费标识发送给所述第二网关设备。
在一种可能的设计中，所述第二网关设备针对识别出的本地业务进行计费得到第二计费信息，包括：
针对离线计费，所述第二网关设备针对用户使用识别出的本地业务数据流的情况进行统计得到统计信息，并基于统计信息生成计费话单；或者，
针对在线计费，所述第二网关设备针对用户使用识别出的本地业务数据流的情况进行统计得到统计信息，并基于统计信息生成在线计费配额申请信息；或者，
针对AAA计费，所述第二网关设备针对用户使用识别出的本地业务数据流的情况进行统计得到统计信息，并基于统计信息生成AAA计费信息。
第二方面，本发明实施例还提供了一种计费方法，包括：
第二网关设备识别出接收到的业务数据流中的用户的本地业务对应的本地业务数据流；并针对用户使用识别出的本地业务数据流的情况进行统计得到第二统计信息；所述第二网关设备向第一网关设备发送所述第二统计信息
第一网关设备接收到第二网关设备发送的针对用户使用本地业务数据流的情况进行统计得到的第二统计信息时，所述第一网关设备基于所述第二统计信息生成第二计费信息并使用第二计费标识将所述第二计费信息标记后发送给计费系统；所述第二计费标识用于标识所述用户的本地业务对应的计费 信息。
所述第二网关设备将接收到的用户的业务数据流中除识别出的本地业务外的其他业务数据流透传给第一网关设备。所述第一网关设备接收到所述用户的非本地业务数据流时，针对所述用户使用非本地业务数据流的情况进行计费并生成第一计费信息，所述第一计费信息携带第一计费标识，所述第一计费标识用于标识所述用户的非本地业务对应的计费信息；所述第一网关设备将所述第一计费信息发送给计费系统。
在一种可能的设计中，第一网关设备接收到第二网关设备发送的第二统计信息之前，还包括：
第一网关设备为所述用户生成所述第一计费标识以及为所述用户生成所述第二计费标识。
第三方面，本发明实施提供了一种计费装置，所述计费装置应用于第一网关设备，包括：
接收单元，用于接收到第二网关设备发送的针对用户的本地业务数据流计费得到的第二计费信息；
发送单元，用于将所述第二计费信息发送给计费系统；所述第二计费信息携带第二计费标识，所述第二计费标识用于标识所述用户的本地业务对应的计费信息；
所述接收单元，还用于接收到所述用户的非本地业务数据流；
处理单元，用于根据所述用户发送非本地业务数据流的情况进行计费并生成第一计费信息，所述第一计费信息携带第一计费标识，所述第一计费信息包括用于对用户的非本地业务计费的计费信息，所述第一计费标识用于标识所述用户的非本地业务对应的计费信息；
所述发送单元，还用于将所述第一计费信息发送给计费系统。
在一种可能的设计中，所述处理单元，还用于在所述接收单元接收到第二网关设备发送的针对用户的本地业务数据流计费得到的第二计费信息之前，为所述用户生成所述第一计费标识以及所述第二计费标识；
所述发送单元，还用于将所述第二计费标识发送给所述第二网关设备。
第四方面，本发明实施提供了一种计费装置，所述计费装置应用于第一网关设备，包括：
通信接口、存储器以及处理器；
所述通信接口，用于接收和发送数据；
存储器，用于存储所述处理器执行的程序代码；
所述处理器，用于执行所述存储器存储的程序代码，具体用于实现第三方面或者第三方面的任意一种设计所述的装置所实现的功能。
第五方面，本发明实施例还提供了一种计费装置，所述装置应用于第二网关设备，包括：
接收单元，用于接收用户的业务数据流；
处理单元，用于识别出所述接收单元接收到的业务数据流中的用户的本地业务对应的本地业务数据流；并针对识别出的本地业务数据流进行计费得到第二计费信息，所述第二计费信息携带第二计费标识，所述第二计费标识用于标识所述用户的本地业务对应的计费信息；
发送单元，用于向第一网关设备发送所述处理单元处理得到的第二计费信息；
所述发送单元，还用于将所述接收单元接收到的用户的业务数据流中除识别出的本地业务数据流外的其他业务数据流透传给第一网关设备。
在一种可能的设计中，所述第二计费标识是所述接收单元预先接收到由所述第一网关设备发送的。
在一种可能的设计中，在针对识别出的本地业务进行计费得到第二计费信息时，所述处理单元具体用于：
针对离线计费，针对用户使用识别出的本地业务数据流的情况进行统计得到统计信息，并基于统计信息生成计费话单；或者，
针对在线计费，针对用户使用识别出的本地业务数据流的情况进行统计得到统计信息，并基于统计信息生成在线计费配额申请信息；或者，
针对AAA计费，针对用户使用识别出的本地业务数据流的情况进行统计得到统计信息，并基于统计信息生成AAA计费信息。
第六方面，本发明实施例还提供了一种计费装置，所述装置应用于第二网关设备，包括：
通信接口、存储器以及处理器；
所述通信接口，用于接收和发送数据；
存储器，用于存储所述处理器执行的程序代码；
所述处理器，用于执行所述存储器存储的程序代码，具体用于实现第五方面或者第五方面的任意一种设计所述的装置所实现的功能。
第七方面，本发明实施例提供了一种计费装置，所述装置应用于第一网关设备，包括：
接收单元，用于接收到第二网关设备发送的针对用户使用本地业务数据流的情况进行统计得到的第二统计信息；
处理单元，用于基于接收单元接收到的所述第二统计信息生成第二计费信息并使用第二计费标识将所述第二计费信息标记后；所述第二计费标识用于标识所述用户的本地业务对应的计费信息；
发送单元，用于将标记后的第二计费信息发送给计费系统；
所述处理单元，还用于在所述接收单元接收到所述用户的非本地业务数据流时，针对所述用户使用非本地业务数据流的情况进行计费并生成第一计费信息，所述第一计费信息携带第一计费标识，所述第一计费标识用于标识所述用户的非本地业务对应的计费信息；
所述发送单元，还用于将处理单元处理得到的所述第一计费信息发送给计费系统。
在一种可能的设计中，在所述接收单元接收到第二网关设备发送的第二统计信息之前，所述处理单元还用于为所述用户生成所述第一计费标识以及为所述用户生成所述第二计费标识。
第八方面，本发明实施例还提供了一种计费装置，所述装置应用于第一 网关设备，包括：
通信接口、存储器以及处理器；
所述通信接口，用于接收和发送数据；
存储器，用于存储所述处理器执行的程序代码；
所述处理器，用于执行所述存储器存储的程序代码，具体用于实现第七方面或者第七方面的任意一种设计所述的装置所实现的功能。
第九方面，本发明实施例提供了一种计费装置，所述装置应用于第二网关设备，包括：
接收单元，用于接收用户的业务数据流；
处理单元，用于识别出所述接收单元接收到的业务数据流中的用户的本地业务对应的本地业务数据流；并针对用户使用识别出的本地业务数据流的情况进行统计得到第二统计信息；
发送单元，用于向第一网关设备发送所述处理单元得到的第二统计信息；
所述发送单元，还用于将所述接收单元接收到的用户的业务数据流中除识别出的本地业务外的其他业务数据流透传给第一网关设备。
第十方面，本发明实施例还提供了一种计费装置，所述装置应用于第二网关设备，包括：
通信接口、存储器以及处理器；
所述通信接口，用于接收和发送数据；
存储器，用于存储所述处理器执行的程序代码；
所述处理器，用于执行所述存储器存储的程序代码，具体用于实现第九方面或者第九方面的任意一种设计所述的装置所实现的功能。
附图说明
图1为本发明实施例提供的一种通信网络架构示意图；
图2为本发明实施例提供的另一种通信网络架构示意图；
图3为本发明实施例提供的又一种通信网络架构示意图；
图4为本发明实施例提供的一种计费方法流程图；
图5为本发明实施例提供的一种计费流程示意图；
图6为本发明实施例提供的另一种计费方法流程图；
图7为本发明实施例提供的另一种计费流程示意图；
图8为本发明实施例提供的一种第一网关设备示意图；
图9为本发明实施例提供的另一种第一网关设备示意图；
图10为本发明实施例提供的一种第二网关设备示意图；
图11为本发明实施例提供的另一种第二网关设备示意图；
图12为本发明实施例提供的又一种第一网关设备示意图；
图13为本发明实施例提供的再一种第一网关设备示意图；
图14为本发明实施例提供的又一种第二网关设备示意图；
图15为本发明实施例提供的再一种第二网关设备示意图。
具体实施方式
为了使本发明的目的、技术方案和优点更加清楚，下面将结合附图对本发明作进一步地详细描述，显然，所描述的实施例仅仅是本发明一部分实施例，而不是全部的实施例。基于本发明中的实施例，本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其它实施例，都属于本发明保护的范围。
本发明实施例提供一种计费方法及装置，用以解决现有技术中存在的无法保证计费结果的准确性的问题。其中，方法和装置是基于同一发明构思的，由于方法及装置解决问题的原理相似，因此装置与方法的实施可以相互参见，重复之处不再赘述。
为了便于理解，先从整体上描述能够应用本发明实施例的计费方法的通信网络架构示意图。应理解，本发明实施例并不限于图1所示的通信网络中，此外，图1中的装置可以是硬件，也可以是从功能上划分的软件或者以上二者的结构。
如图1所示，可以应用本发明实施例的计费方法的通信网络架构中可以包括终端设备(英文：User Equipment，简称：UE)、基站、第一网关设备、第二网关设备、移动管理实体(英文：Mobility Management Entity，简称：MME)和本地应用服务器，以及互联网(Internet)以及计费系统。其中，终端设备可以通过基站与MME通信，第二网关设备针对除第一网关设备以外的其他网元是透明的，在终端通过基站向第一网关设备发送业务数据流时，需要经过第二网关设备，第二网关设备可以将业务数据流中的本地业务数据流截获直接转发至本地应用服务器，而将非本地业务数据流透传给第一网关设备。第二网关设备和第一网关设备与MME的虚线表示第一网关设备或第二网关设备二者之一可以与MME通信。本地应用服务器可以和第二网关设备通信。第二网关设备可以部署在终端设备的接入网或城域网中。第一网关设备可以将产生的计费信息发送给计费系统。
本发明的实施例中，终端设备可以经无线接入网(英文：Radio Access Network，简称：RAN)与一个或多个核心网(Core Network)进行通信，UE也可称为接入终端、用户设备、用户单元、用户站、移动站、移动台、远方站、远程终端、移动设备、用户终端、终端、无线通信设备、用户代理或用户装置等。UE可以是蜂窝电话、无绳电话、会话启动协议(英文：Session Initiation Protocol，简称：SIP)电话、无线本地环路(英文：Wireless Local Loop，简称：WLL)站、个人数字处理(英文：Personal Digital Assistant，简称：PDA)、具有无线通信功能的手持设备、计算设备或连接到无线调制解调器的其它处理设备、车载设备、可穿戴设备以及未来5G网络中的终端设备等。
本发明的实施例中，基站可以是全球移动通信(英文：Global System for Mobile communication，简称：GSM)系统或码分多址(英文：Code Division Multiple Access，简称：CDMA)系统中的基站(英文：Base Transceiver Station，简称：BTS)，也可以是宽带码分多址(英文：Wideband Code Division Multiple Access，简称：WCDMA)系统中的基站(NodeB)，还可以是LTE系统中的演进型基站(英文：Evolutional Node B，简称：eNB或eNodeB)，或者是未 来5G网络中的基站设备、小基站设备等，本发明对此并不限定。而且，本发明实施例中，基站可以表示接入网。
本发明的实施例中，MME是控制面网元，主要负责用户设备的移动性管理和会话管理等控制面功能。
本发明的实施例中，本地应用服务器(英文：Local Application Server，简称：LAPP)本质上是应用服务器。该应用服务器与终端设备共同处于一个局部的地理范围内(如一个学校、工厂和机关内)时，可以将该应用服务器称为终端设备的本地应用服务器。终端设备只需通过基站和第二网关设备即可访问本地应用服务器，以访问本地网络，而不用通过第一网关设备以及互联网来访问本地网络。本地应用服务器通常由应用服务商部署在靠近终端设备的地方(如接入网位置)，因此，终端设备的本地业务数据流可以从第二网关设备直接路由到本地应用服务器，这种本地业务数据流的直接路由模式可以称为本地发送。
图2为图1所示的通信网络的一种更具体的示意性架构图。图2中的装置可以是硬件，也可以是从功能上划分的软件或者以上二者的结构。
图2所示的通信网络架构示意图中，第二网关设备可以透明串接在S1-U接口，用户面流量全部都要经过第二网关设备，第二网关设备与周边网元(如MME、计费系统)没有对外接口，即第二网关设备对周边网元不可见。第一网关设备可以通过控制接口Sx接口对第二网关设备进行控制管理等。第二网关设备可以与接入网(比如基站)合并部署，也可以部署到城域网。
第一网关设备可以具有服务网关(英文：Serving Gate Way，简称：SGW)和分组数据网关(英文：Packet Data Network Gateway，简称：PGW)的功能。
本发明的实施例中，SGW和PGW兼有控制面和用户面功能，主要参与移动性管理和会话管理，如接入控制、数据转发和计费等。SGW与PGW可以分别设置，它们之间的接口可以为标准S5接口；SGW与PGW网元也可以合设。
图2所示的通信网络架构示意图中，由于第二网关设备相对于第一网关 设备，距离终端设备较近，即第二网关设备处于整个网络中较为偏远的位置，因此可以将第二网关设备称为远端网关(英文：Remote Gateway，简称：RGW)，可以将第一网关设备称为集中网关(英文：Centralized Gateway，简称：CGW)。
图3为图1所示的通信网络的另一种更具体的示意性架构图。图3中的装置可以是硬件，也可以是从功能上划分的软件或者以上二者的结构。
第二网关设备可以和接入网(如基站)部署在一起，也可以部署在城域网。此时，第二网关设备对周边网元(如MME和eNB)可见，第二网关设备与MME之间可以存在S11接口，从而第二网关设备与MME之间可以通过S11接口直接交互信令，MME可以选择为终端设备服务的第二网关设备。第一网关设备和第二网关设备之间既有信令面接口S5-C，也有数据面接口S5-U，从而第一网关设备和第二网关设备之间通过S5-C进行信令交互，通过S5-U进行数据交互。第二网关设备可以具有SGW的功能以及本地业务数据流识别功能、分流功能，第一网关设备可以具有PGW的功能。
图3所示的通信网络架构示意图中，由于第二网关设备相对于第一网关设备，距离终端设备较近，即第二网关设备处于整个网络中较为偏远的位置，因此可以将第二网关设备称为RGW，可以将第一网关设备称为CGW。
应注意，本发明实施例中对术语的解释只是示例性说明，不应构成本发明实施例的限制。
本发明实施例提出在第一网关设备仅对计费系统呈现两个计费承载，而对于其他网元(比如MME)呈现的仅是一个承载，一个用于非本地业务计费的承载，另一个用于本地业务计费的承载。具体的，可以将用于非本地业务计费的承载称为“主承载”，可以将用于本地业务计费的承载称为“影子承载”。其中，影子承载仅用于计费，且只有第一网关设备以及计费网元可知，其他网元仅知道主承载。对主承载分配一个计费标识，针对影子承载分配一个计费标识，两个计费标识不同。本发明实施例中为了区分两个计费标识，将用于标识针对本地业务计费的计费标识称为第二计费标识，即影子承载对应的计费标识，将用于标识针对非本地业务计费的计费标识称为第一计费标识， 即主承载对应的计费标识。
图4为本发明实施例提供的一种计费方法的流程示意图，该方法包括：
S401，第二网关设备识别出接收到的业务数据流中的用户的本地业务对应的本地业务数据流；并针对识别出的本地业务数据流进行计费得到第二计费信息。
所述第二计费信息携带第二计费标识，所述第二计费标识用于标识所述用户的本地业务对应的计费信息。
其中，第二网关设备在识别出接收到的业务数据流中的用户的本地业务对应的本地业务数据流时，将所述本地业务数据流转发给本地应用服务器。
S402，所述第二网关设备向第一网关设备发送所述第二计费信息。
S403，所述第一网关设备接收到第二网关设备发送的针对用户的本地业务数据流计费得到的第二计费信息时，所述第一网关设备将所述第二计费信息发送给计费系统。
S404，所述第二网关设备将接收到的用户的业务数据流中除识别出的本地业务数据流外的其他业务数据流透传给第一网关设备。
S405，所述第一网关设备接收到所述用户的非本地业务数据流时，根据所述用户发送非本地业务数据流的情况进行计费并生成第一计费信息。所述第一计费信息携带第一计费标识，所述第一计费信息包括用于对用户的非本地业务计费的计费信息，所述第一计费标识用于标识所述用户的非本地业务对应的计费信息。
S406，所述第一网关设备将所述第一计费信息发送给计费系统。
在一种可能的设计中，所述第二计费标识是所述第二网关设备预先接收到由所述第一网关设备发送的。
第一网关设备在接收到第二网关设备发送的针对用户的本地业务数据流计费得到的第二计费信息之前，所述第一网关设备为所述用户生成所述第一计费标识以及所述第二计费标识；所述第一网关设备将所述第二计费标识发送给所述第二网关设备。
具体的，在用户的终端设备附着到网络过程中，MME为用户创建默认承载，该默认承载会保持连接直到终端设备分离(detach)网络，并由MME将默认承载对应的信息发送给第一网关设备。默认承载对应的信息包括承载标识(Bearer ID)等信息。第一网关设备基于默认承载分配第一计费标识，在涉及在线计费时，还要分配第一会话标识(Session-Id)，从而第一网关设备能够通过第一会话标识对非本地业务进行在线计费配额管理。
第一网关设备创建影子承载，并通知第二网关设备创建承载时，分配第二计费标识，创建的影子承载仅用于计费，分配的第二计费标识用于标识针对本地业务的计费信息。第一网关设备分配第二计费标识后，将该第二计费标识发送给第二网关设备，从而使得第二网关设备能够为针对用户的本地业务数据流进行计费并生成第二计费信息，以及将第二计费信息使用第二计费标识进行标记发送给第一网关设备，从而第一网关设备将第二计费信息转发给计费系统。当然，在涉及在线计费时，第一网关设备还要分配第二会话标识(Session-Id)。用于通过第二会话标识进行本地业务的在线计费配额管理。计费系统在收到标记后的第一计费信息和第二计费信息后，能够根据计费标识认为对本地业务以及非本地业务采用的是不同的承载，从而进行分开计费，解决了同一承载的不同业务在不同计费控制点计费不准确的问题。
本发明实施例中涉及的计费可以包括在线计费、离线计费、以及AAA计费。
可选地，所述第二网关设备针对识别出的本地业务进行计费得到第二计费信息，可以通过如下方式实现：
针对离线计费，第二计费信息为针对用户的本地业务的离线计费话单，所述第二网关设备针对识别出的本地业务数据流进行统计得到统计信息，并基于统计信息生成计费话单，并使用第二计费标识对离线计费话单进行标记。另外，所述第二网关设备在生成携带有第二计费标识的离线计费话单后，通过第一网关设备将携带有第二计费标识的离线计费话单转发给离线计费系统(OFCS)。
针对在线计费，第二计费信息为针对用户的本地业务的在线计费配额申请信息，所述第二网关设备针对用户使用识别出的本地业务数据流的情况进行统计得到统计信息，并基于统计信息生成在线计费配额申请信息，使用第二计费标识对在线计费配额申请信息进行标记。另外，所述第二网关设备将所述在线计费配额申请信息发送给在线计费系统(OCS)用于申请在线计费配额。
针对AAA计费，第二计费信息则为针对用户的本地业务的AAA计费信息，所述第二网关设备针对用户使用识别出的本地业务数据流的情况进行统计得到统计信息，并基于计费统计信息生成AAA计费信息。
在一种可能的实现方式中，第二网关设备识别出接收到的业务数据流中的用户的本地业务对应的本地业务数据流之前，确定针对用户的本地业务的计费策略信息，从而第二网关设备在识别出接收到的业务数据流中的用户的本地业务对应的本地业务数据流时，所述第二网关设备基于所述计费策略信息针对所述用户的本地业务进行计费生成第二计费信息。
可选地，所述计费策略信息包括以下至少一种计费方法：
在线计费的计费方法、离线计费的计费方法以及AAA计费的计费方法。
其中在计费时，可以按时长、流量、或者时长和流量、或者事件等方式。
其中，针对在线计费，所述计费策略信息还包括：在线计费配额信息；或者包括：在线计费配额信息以及配额重申请阈值，或者包括在线计费配额信息、计费信息上报条件。所述计费策略信息还可以包括由OCS下发的其他用于计费的策略信息。
针对在线计费配额信息，例如可以是用户每月套餐中的500M流量或者50条彩信等等，则配额重申请阈值可以是剩余流量不足50M、或者彩信剩余条数为5条等。
针对离线计费，所述计费策略信息还包括离线计费对应的计费信息上报条件。
针对AAA计费，所述计费策略信息还包括AAA计费对应的计费信息上 报条件。
下面结合具体应用场景对本发明实施例作具体说明。
参见图5所示为本发明实施例提供的针对本地业务数据流的计费方法示意图。以第一网关设备为CGW，第二网关设备为RGW为例进行说明。
S501，在用户的终端设备附着到网络过程中，CGW为终端设备创建主承载，并分配所述承载对应的charging-Id1。
S502，CGW为本地业务创建影子承载，为所述影子承载分配新的Charging-Id2。针对在线计费时，CGW为所述影子承载分配在线计费会话的Session-Id等等。
对于本地业务数据流和非本地业务数据流，CGW基于不同的承载(分别基于影子承载和主承载)进行计费处理，即基于不同的计费标识进行计费管理，比如向OCS预申请在线计费配额等。
S503，针对在线计费，CGW基于Charging-Id2向OCS预申请在线计费配额。
S504：CGW通知RGW激活，并向RGW发送对本地业务数据流计费的计费策略信息。计费策略信息具体包括计费方式、在线计费配额，Charging ID2等。
S505，用户通过UE发起上行业务数据流。
S506，RGW基于本地分流策略识别出上行业务数据流为本地业务数据流。其中，本地分流策略可以在RGW本地配置，也可以预先由PCRF下发。
S507，如果需要为本地业务数据流执行在线计费处理时，且步骤S503未进行在线计费配额预申请时，RGW通过CGW则向OCS申请在线计费配额。
S508，RGW基于本地分流策略执行本地分流，将用户的本地业务数据流发送给LAPP处理。如果RGW基于本地分流策略识别出上行业务数据流为非本地业务数据流时，RGW直接将非本地业务数据流透传给CGW处理。
S509，对于本地业务数据流，RGW根据本地业务数据流对应的计费策略信息进行统计得到统计信息，并基于统计信息生成计费信息，其中生成的计 费信息携带了Charging-Id2。
针对在线计费，则RGW基于统计信息生成在线计费配额申请信息，在线计费配额申请信息携带了Charging-Id2。
针对离线计费，则RGW基于统计信息生成离线计费话单，离线计费话单携带了Charging-Id2。
针对AAA计费，则RGW基于统计信息生成AAA计费信息，AAA计费信息携带了Charging-Id2。
S510，当计费信息上报条件满足，则本地业务的计费信息给CGW。
S511：在线计费时，CGW通过影子承载把本地业务的在线计费配额申请信息上报给OCS，并接收OCS新下发的在线计费配额信息。
S512：离线计费时，CGW通过影子承载把本地业务的离线计费话单上报给OFCS。
S513：AAA计费时，CGW通过影子承载把本地业务的AAA计费信息上报给AAA计费服务器。
S514：CGW给RGW回复本地业务的计费信息上报应答，携带OCS新下发的在线计费配额信息。
此外，本发明实施例图5的流程中，仅描述了本地业务的计费处理流程。对于非本地分流业务的计费由CGW执行计费信息统计、话单生成及上报、在线计费配额申请等，和现有技术类似，因此本发明实施例不再重复描述。
图6为本发明实施例提供的一种计费方法的流程示意图，该方法包括：
S601，第二网关设备识别出接收到的业务数据流中的用户的本地业务对应的本地业务数据流；并针对用户使用识别出的本地业务数据流的情况进行统计得到第二统计信息。
其中，第二网关设备在识别出接收到的业务数据流中的用户的本地业务对应的本地业务数据流时，将所述本地业务数据流转发给本地应用服务器。
S602，所述第二网关设备向第一网关设备发送所述第二统计信息。
S603，所述第一网关设备接收到第二网关设备发送的针对用户使用本地 业务数据流的情况进行统计得到的第二统计信息时，所述第一网关设备基于所述第二统计信息生成第二计费信息并使用第二计费标识将所述第二计费信息标记后发送给计费系统。
所述第二计费标识用于标识所述用户的本地业务对应的计费信息。
S604，所述第二网关设备将接收到的用户的业务数据流中除识别出的本地业务数据流外的其他业务数据流透传给第一网关设备。
S605，所述第一网关设备接收到所述用户的非本地业务数据流时，根据所述用户使用非本地业务数据流的情况进行计费并生成第一计费信息。
所述第一计费信息携带第一计费标识，所述第一计费信息包括用于对用户的非本地业务计费的计费信息，所述第一计费标识用于标识所述用户的非本地业务对应的计费信息。
S606，所述第一网关设备将所述第一计费信息发送给计费系统。
具体的，在用户的终端设备附着到网络过程中，MME为用户创建默认承载，该默认承载会保持连接直到终端设备分离(detach)网络，并由MME将默认承载对应的信息发送给第一网关设备。默认承载对应的信息包括承载标识(Bearer ID)等信息。第一网关设备基于默认承载分配第一计费标识；在涉及在线计费时，还要分配第一会话标识(Session-Id)，从而第一网关设备能够通过第一会话标识对非本地业务进行在线计费配额管理。
第一网关设备创建影子承载，并通知第二网关设备创建承载时，分配第二计费标识，创建的影子承载仅用于计费，分配的第二计费标识用于标识针对本地业务的计费信息。
针对离线计费，第二计费信息为针对用户的本地业务的离线计费话单，所述第一网关设备接收到第二统计信息时，生成离线计费话单并使用第二计费标识将离线计费话单标记后发给离线计费系统(OFCS)。
针对在线计费，第二计费信息为针对用户的本地业务的在线计费配额申请信息，所述第一网关设备接收到第二统计信息时，生成在线计费配额申请信息，并使用第二计费标识将所述在线计费配额申请信息标记后发送给在线 计费系统(OCS)用于申请在线计费配额。
针对AAA计费，第二计费信息则为针对用户的本地业务的AAA计费信息，所述第一网关设备接收到第二统计信息时，生成AAA计费信息，并使用第二计费标识将所述AAA计费信息标记后发送给AAA计费服务器。
在一种可能的实现方式中，第二网关设备识别出接收到的业务数据流中的用户的本地业务对应的本地业务数据流之前，确定针对用户的本地业务的计费策略信息，从而第二网关设备在识别出接收到的业务数据流中的用户的本地业务对应的本地业务数据流时，所述第二网关设备基于所述计费策略信息针对所述用户使用本地业务数据流的情况进行统计得到第二统计信息。
可选地，所述计费策略信息包括以下至少一种计费方法：
在线计费的计费方法、离线计费的计费方法以及AAA计费的计费方法。
其中在计费时，可以按时长、流量、或者时长和流量、或者事件等方式。
其中，针对在线计费，所述计费策略信息还包括：在线计费配额信息；或者包括：在线计费配额信息以及配额重申请阈值，或者包括在线计费配额信息、计费信息上报条件。所述计费策略信息还可以包括由OCS下发的其他用于计费的策略信息。
针对在线计费配额信息，例如可以是用户每月套餐中的500M流量或者50条彩信等等，则配额重申请阈值可以是剩余流量不足50M、或者彩信剩余条数为5条等。
针对离线计费，所述计费策略信息还包括离线计费对应的计费信息上报条件。
针对AAA计费，所述计费策略信息还包括AAA计费对应的计费信息上报条件。
下面结合具体应用场景对本发明实施例作具体说明。
参见图7所示为本发明实施例提供的针对本地业务数据流的计费方法示意图。以第一网关设备为CGW，第二网关设备为RGW为例进行说明。
S701，在用户附着到网络过程中，CGW为用户创建主承载，并分配所述 承载对应的charging-Id1。
S702，CGW为本地业务创建影子承载，为所述影子承载分配新的Charging-Id2。针对在线计费时，CGW为所述影子承载分配在线计费会话的Session-Id等等。
对于本地业务数据流和非本地业务数据流，CGW基于不同的承载(分别基于影子承载和主承载)进行计费处理，即基于不同的计费标识进行计费管理，比如向OCS预申请在线计费配额等。
S703，针对在线计费，CGW基于Charging-Id2向OCS预申请在线计费配额。
S704：CGW通知RGW激活，并向RGW发送对本地业务数据流计费的计费策略信息。计费策略信息具体包括计费方式、在线计费配额等。
S705，用户通过UE发起上行业务数据流。
S706，RGW基于本地分流策略识别出上行业务数据流为本地业务数据流。其中，本地分流策略可以在RGW本地配置，也可以预先由PCRF下发。
S707，RGW基于本地分流策略执行本地分流，将用户的本地业务数据流发送给LAPP处理。如果RGW基于本地分流策略识别出上行业务数据流为非本地业务数据流时，RGW直接将非本地业务数据流透传给CGW处理。
S708，对于本地业务数据流，RGW根据本地业务数据流对应的计费策略信息进行统计得到统计信息。统计信息包括统计的会话时长，以及流量使用情况等等。
S709，当计费信息上报条件满足，则RGW将本地业务的统计信息发给CGW。
S710：在线计费时，则CGW基于统计信息生成在线计费配额申请信息，并使用Charging-Id2对在线计费配额申请信息进行标记。
S711，CGW将在线计费配额申请信息发送给OCS。
S712，针对离线计费，则CGW基于统计信息生成离线计费话单，并使用Charging-Id2对离线计费话单进行标记。
S713，CGW将离线计费话单发送给OFCS。
S714，针对AAA计费，则CGW基于统计信息生成AAA计费信息，并使用Charging-Id2对AAA计费信息进行标记。
S717，CGW将AAA计费信息发送给AAA计费服务器。
S716：CGW给RGW回复本地业务的计费信息上报应答，携带OCS新下发的在线计费配额信息。
此外，本发明实施例图5的流程中，仅描述了本地业务的计费处理流程。对于非本地分流业务的计费由CGW执行计费信息统计、话单生成及上报、在线计费配额申请等，和现有技术类似，因此本发明实施例不再重复描述。
基于与图4对应的方法实施例同样的发明构思，本发明实施提供了一种计费装置，所述计费装置应用于第一网关设备。如图8所示，该装置包括：
接收单元801，用于接收到第二网关设备发送的针对用户的本地业务数据流计费得到的第二计费信息；
发送单元802，用于将所述第二计费信息发送给计费系统；所述第二计费信息携带第二计费标识，所述第二计费标识用于标识所述用户的本地业务对应的计费信息；
所述接收单元801，还用于接收到所述用户的非本地业务数据流；
处理单元803，用于根据所述用户发送非本地业务数据流的情况进行计费并生成第一计费信息，所述第一计费信息携带第一计费标识，所述第一计费信息包括用于对用户的非本地业务计费的计费信息，所述第一计费标识用于标识所述用户的非本地业务对应的计费信息；
所述发送单元802，还用于将所述第一计费信息发送给计费系统。
在一种可能的设计中，所述处理单元803，还用于在所述接收单元801接收到第二网关设备发送的针对用户的本地业务数据流计费得到的第二计费信息之前，为所述用户生成所述第一计费标识以及所述第二计费标识；
所述发送单元802，还用于将所述第二计费标识发送给所述第二网关设备。
本发明实施例中对单元的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，另外，在本发明各个实施例中的各功能单元可以集成在一个处理器中，也可以是单独物理存在，也可以两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。
其中，在集成的单元采用硬件的形式实现时，如图9所示，可以包括通信接口901、处理器902以及存储器903。所述存储器903，用于存储所述处理器902执行的程序代码。通信接口901用于接收和发送数据。接收单元801、发送单元802对应的实体硬件可以为通信接口901，处理单元803对应的实体硬件可以为处理器902。还可以是接收单元801、发送单元802、处理单元803均对应实体硬件处理器902，从而处理器902通过通信接口901接收和发送数据。
处理器902，可以是一个中央处理单元(英文：central processing unit，简称CPU)，或者为数字处理单元等等。处理器902用于执行存储器903存储的程序代码，具体用于执行接收单元801、发送单元802、处理单元803所需执行的功能。
本发明实施例中不限定上述通信接口901、处理器902以及存储器903之间的具体连接介质。本发明实施例在图9中以通信接口901、处理器902以及存储器903之间通过总线904连接，总线在图9中以粗线表示，其它部件之间的连接方式，仅是进行示意性说明，并不引以为限。所述总线可以分为地址总线、数据总线、控制总线等。为便于表示，图9中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。
存储器903可以是易失性存储器(英文：volatile memory)，例如随机存取存储器(英文：random-access memory，缩写：RAM)；存储器903也可以是非易失性存储器(英文：non-volatile memory)，例如只读存储器(英文：read-only memory，缩写：ROM)，快闪存储器(英文：flash memory)，硬盘(英文：hard disk drive，缩写：HDD)或固态硬盘(英文：solid-state drive， 缩写：SSD)、或者存储器903是能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质，但不限于此。存储器903可以是上述存储器的组合。
基于图4所示的实施例同样的发明构思，本发明实施例还提供了一种计费装置，所述装置应用于第二网关设备。如图10所示，该装置包括：
接收单元1001，用于接收用户的业务数据流；
处理单元1002，用于识别出所述接收单元1001接收到的业务数据流中的用户的本地业务对应的本地业务数据流；并针对识别出的本地业务数据流进行计费得到第二计费信息，所述第二计费信息携带第二计费标识，所述第二计费标识用于标识所述用户的本地业务对应的计费信息；
发送单元1003，用于向第一网关设备发送所述处理单元1002处理得到的第二计费信息；
所述发送单元1003，还用于将所述接收单元1001接收到的用户的业务数据流中除识别出的本地业务数据流外的其他业务数据流透传给第一网关设备。
在一种可能的设计中，所述第二计费标识是所述接收单元1001预先接收到由所述第一网关设备发送的。
在一种可能的设计中，在针对识别出的本地业务进行计费得到第二计费信息时，所述处理单元1002具体用于：
针对离线计费，针对用户使用识别出的本地业务数据流的情况进行统计得到统计信息，并基于统计信息生成计费话单；或者，
针对在线计费，针对用户使用识别出的本地业务数据流的情况进行统计得到统计信息，并基于统计信息生成在线计费配额申请信息；或者，
针对AAA计费，针对用户使用识别出的本地业务数据流的情况进行统计得到统计信息，并基于统计信息生成AAA计费信息。
本发明实施例中对单元的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，另外，在本发明各个实施例中的各功能 单元可以集成在一个处理器中，也可以是单独物理存在，也可以两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。
其中，在集成的单元采用硬件的形式实现时，如图11所示，可以包括通信接口1101、处理器1102以及存储器1103。所述存储器1103，用于存储所述处理器1102执行的程序代码。通信接口1101用于接收和发送数据。接收单元1001、发送单元1003对应的实体硬件可以为通信接口1101，处理单元1002对应的实体硬件可以为处理器1102。还可以是接收单元1001、发送单元1003、处理单元1002均对应实体硬件处理器1102，从而处理器1102通过通信接口1101接收和发送数据。
处理器1102，可以是一个CPU，或者为数字处理单元等等。处理器1102用于执行存储器1103存储的程序代码，具体用于执行接收单元1001、发送单元1003、处理单元1002所需执行的功能。
本发明实施例中不限定上述通信接口1101、处理器1102以及存储器1103之间的具体连接介质。本发明实施例在图11中以通信接口1101、处理器1102以及存储器1103之间通过总线1104连接，总线在图11中以粗线表示，其它部件之间的连接方式，仅是进行示意性说明，并不引以为限。所述总线可以分为地址总线、数据总线、控制总线等。为便于表示，图11中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。
存储器1103可以是volatile memory，例如RAM；存储器1103也可以是non-volatile memory，例如ROM，flash memory，HDD或SSD、或者存储器1103是能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质，但不限于此。存储器1103可以是上述存储器的组合。
基于图6所示的实施例同样的发明构思，本发明实施例提供了一种计费装置，所述装置应用于第一网关设备，如图12所示，所述装置包括：
接收单元1201，用于接收到第二网关设备发送的针对用户使用本地业务 数据流的情况进行统计得到的第二统计信息；
处理单元1202，用于基于接收单元1201接收到的所述第二统计信息生成第二计费信息并使用第二计费标识将所述第二计费信息标记后；所述第二计费标识用于标识所述用户的本地业务对应的计费信息；
发送单元1203，用于将标记后的第二计费信息发送给计费系统；
所述处理单元1202，还用于在所述接收单元1201接收到所述用户的非本地业务数据流时，针对所述用户使用非本地业务数据流的情况进行计费并生成第一计费信息，所述第一计费信息携带第一计费标识，所述第一计费标识用于标识所述用户的非本地业务对应的计费信息；
所述发送单元1203，还用于将处理单元1202处理得到的所述第一计费信息发送给计费系统。
在一种可能的设计中，在所述接收单元1201接收到第二网关设备发送的第二统计信息之前，所述处理单元1202还用于为所述用户生成所述第一计费标识以及为所述用户生成所述第二计费标识。
本发明实施例中对单元的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，另外，在本发明各个实施例中的各功能单元可以集成在一个处理器中，也可以是单独物理存在，也可以两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。
其中，在集成的单元采用硬件的形式实现时，如图13所示，可以包括通信接口1301、处理器1302以及存储器1303。所述存储器1303，用于存储所述处理器1302执行的程序代码。通信接口1301用于接收和发送数据。接收单元1201、发送单元1203对应的实体硬件可以为通信接口1301，处理单元802对应的实体硬件可以为处理器1302。还可以是接收单元1201、发送单元1203、处理单元1202均对应实体硬件处理器1302，从而处理器1302通过通信接口1301接收和发送数据。
处理器1302，可以是一个CPU，或者为数字处理单元等等。处理器1302 用于执行存储器1303存储的程序代码，具体用于执行接收单元1201、发送单元1203、处理单元1202所需执行的功能。
本发明实施例中不限定上述通信接口1301、处理器1302以及存储器1303之间的具体连接介质。本发明实施例在图13中以通信接口1301、处理器1302以及存储器1303之间通过总线1304连接，总线在图13中以粗线表示，其它部件之间的连接方式，仅是进行示意性说明，并不引以为限。所述总线可以分为地址总线、数据总线、控制总线等。为便于表示，图13中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。
存储器1303可以是volatile memory，例如RAM；存储器1303也可以是non-volatile memory，例如ROM，flash memory，HDD或SSD、或者存储器1303是能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质，但不限于此。存储器1303可以是上述存储器的组合。
基于图6所示的实施例同样的发明构思，本发明实施例提供了一种计费装置，所述装置应用于第二网关设备，如图14所示，所述装置包括：
接收单元1401，用于接收用户的业务数据流；
处理单元1402，用于识别出所述接收单元1401接收到的业务数据流中的用户的本地业务对应的本地业务数据流；并针对用户使用识别出的本地业务数据流的情况进行统计得到第二统计信息；
发送单元1403，用于向第一网关设备发送所述处理单元1402得到的第二统计信息；
所述发送单元1403，还用于将所述接收单元1401接收到的用户的业务数据流中除识别出的本地业务外的其他业务数据流透传给第一网关设备。
本发明实施例中对单元的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，另外，在本发明各个实施例中的各功能单元可以集成在一个处理器中，也可以是单独物理存在，也可以两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现， 也可以采用软件功能模块的形式实现。
其中，在集成的单元采用硬件的形式实现时，如图15所示，可以包括通信接口1501、处理器1502以及存储器1503。所述存储器1503，用于存储所述处理器1502执行的程序代码。通信接口1501用于接收和发送数据。接收单元1401、发送单元1403对应的实体硬件可以为通信接口1501，处理单元802对应的实体硬件可以为处理器1502。还可以是接收单元1401、发送单元1403、处理单元1402均对应实体硬件处理器1502，从而处理器1502通过通信接口1501接收和发送数据。
处理器1502，可以是一个CPU，或者为数字处理单元等等。处理器1502用于执行存储器1503存储的程序代码，具体用于执行接收单元1401、发送单元1403、处理单元1402所需执行的功能。
本发明实施例中不限定上述通信接口1501、处理器1502以及存储器1503之间的具体连接介质。本发明实施例在图15中以通信接口1501、处理器1502以及存储器1503之间通过总线1504连接，总线在图15中以粗线表示，其它部件之间的连接方式，仅是进行示意性说明，并不引以为限。所述总线可以分为地址总线、数据总线、控制总线等。为便于表示，图15中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。
存储器1503可以是volatile memory，例如RAM；存储器1503也可以是non-volatile memory，例如ROM，flash memory，HDD或SSD、或者存储器1503是能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质，但不限于此。存储器1503可以是上述存储器的组合。
本领域内的技术人员应明白，本发明的实施例可提供为方法、系统、或计算机程序产品。因此，本发明可采用完全硬件实施例、完全软件实施例、或结合软件和硬件方面的实施例的形式。而且，本发明可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器、CD-ROM、光学存储器等)上实施的计算机程序产品的形式。
本发明是参照根据本发明实施例的方法、设备(系统)、和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器，使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中，使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品，该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上，使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理，从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
尽管已描述了本发明的优选实施例，但本领域内的技术人员一旦得知了基本创造性概念，则可对这些实施例做出另外的变更和修改。所以，所附权利要求意欲解释为包括优选实施例以及落入本发明范围的所有变更和修改。
显然，本领域的技术人员可以对本发明实施例进行各种改动和变型而不脱离本发明实施例的精神和范围。这样，倘若本发明实施例的这些修改和变型属于本发明权利要求及其等同技术的范围之内，则本发明也意图包含这些改动和变型在内。

Claims (16)

  1. 一种计费方法，其特征在于，包括：
    第一网关设备接收到第二网关设备发送的针对用户的本地业务数据流计费得到的第二计费信息时，所述第一网关设备将所述第二计费信息发送给计费系统；所述第二计费信息携带第二计费标识，所述第二计费标识用于标识所述用户的本地业务对应的计费信息；
    所述第一网关设备接收到所述用户的非本地业务数据流时，根据所述用户发送非本地业务数据流的情况进行计费并生成第一计费信息，所述第一计费信息携带第一计费标识，所述第一计费信息包括用于对用户的非本地业务计费的计费信息，所述第一计费标识用于标识所述用户的非本地业务对应的计费信息；
    所述第一网关设备将所述第一计费信息发送给计费系统。
  2. 如权利要求1所述的方法，其特征在于，第一网关设备接收到第二网关设备发送的针对用户的本地业务数据流计费得到的第二计费信息之前，所述方法还包括：
    所述第一网关设备为所述用户生成所述第一计费标识以及所述第二计费标识；
    所述第一网关设备将所述第二计费标识发送给所述第二网关设备。
  3. 一种计费方法，其特征在于，包括：
    第二网关设备识别出接收到的业务数据流中的用户的本地业务对应的本地业务数据流；并针对识别出的本地业务数据流进行计费得到第二计费信息，所述第二计费信息携带第二计费标识，所述第二计费标识用于标识所述用户的本地业务对应的计费信息；
    所述第二网关设备向第一网关设备发送所述第二计费信息；
    所述第二网关设备将接收到的用户的业务数据流中除识别出的本地业务数据流外的其他业务数据流透传给第一网关设备。
  4. 如权利要求3所述的方法，其特征在于，所述第二计费标识是所述第二网关设备预先接收到由所述第一网关设备发送的。
  5. 如权利要求3或4所述的方法，其特征在于，所述第二网关设备针对识别出的本地业务进行计费得到第二计费信息，包括：
    针对离线计费，所述第二网关设备针对用户使用识别出的本地业务数据流的情况进行统计得到统计信息，并基于统计信息生成计费话单；或者，
    针对在线计费，所述第二网关设备针对用户使用识别出的本地业务数据流的情况进行统计得到统计信息，并基于统计信息生成在线计费配额申请信息；或者，
    针对AAA计费，所述第二网关设备针对用户使用识别出的本地业务数据流的情况进行统计得到统计信息，并基于统计信息生成AAA计费信息。
  6. 一种计费方法，其特征在于，包括：
    第一网关设备接收到第二网关设备发送的针对用户使用本地业务数据流的情况进行统计得到的第二统计信息时，所述第一网关设备基于所述第二统计信息生成第二计费信息并使用第二计费标识将所述第二计费信息标记后发送给计费系统；所述第二计费标识用于标识所述用户的本地业务对应的计费信息；
    所述第一网关设备接收到所述用户的非本地业务数据流时，针对所述用户使用非本地业务数据流的情况进行计费并生成第一计费信息，所述第一计费信息携带第一计费标识，所述第一计费标识用于标识所述用户的非本地业务对应的计费信息；
    所述第一网关设备将所述第一计费信息发送给计费系统。
  7. 如权利要求6所述的方法，其特征在于，第一网关设备接收到第二网关设备发送的第二统计信息之前，还包括：
    第一网关设备为所述用户生成所述第一计费标识以及为所述用户生成所述第二计费标识。
  8. 一种计费方法，其特征在于，包括：
    第二网关设备识别出接收到的业务数据流中的用户的本地业务对应的本地业务数据流；并针对用户使用识别出的本地业务数据流的情况进行统计得到第二统计信息；
    所述第二网关设备向第一网关设备发送所述第二统计信息；
    所述第二网关设备将接收到的用户的业务数据流中除识别出的本地业务外的其他业务数据流透传给第一网关设备。
  9. 一种计费装置，其特征在于，所述计费装置应用于第一网关设备，包括：
    接收单元，用于接收到第二网关设备发送的针对用户的本地业务数据流计费得到的第二计费信息；
    发送单元，用于将所述第二计费信息发送给计费系统；所述第二计费信息携带第二计费标识，所述第二计费标识用于标识所述用户的本地业务对应的计费信息；
    所述接收单元，还用于接收到所述用户的非本地业务数据流；
    处理单元，用于根据所述用户发送非本地业务数据流的情况进行计费并生成第一计费信息，所述第一计费信息携带第一计费标识，所述第一计费信息包括用于对用户的非本地业务计费的计费信息，所述第一计费标识用于标识所述用户的非本地业务对应的计费信息；
    所述发送单元，还用于将所述第一计费信息发送给计费系统。
  10. 如权利要求9所述的装置，其特征在于，所述处理单元，还用于在所述接收单元接收到第二网关设备发送的针对用户的本地业务数据流计费得到的第二计费信息之前，为所述用户生成所述第一计费标识以及所述第二计费标识；
    所述发送单元，还用于将所述第二计费标识发送给所述第二网关设备。
  11. 一种计费装置，其特征在于，所述装置应用于第二网关设备，包括：
    接收单元，用于接收用户的业务数据流；
    处理单元，用于识别出所述接收单元接收到的业务数据流中的用户的本 地业务对应的本地业务数据流；并针对识别出的本地业务数据流进行计费得到第二计费信息，所述第二计费信息携带第二计费标识，所述第二计费标识用于标识所述用户的本地业务对应的计费信息；
    发送单元，用于向第一网关设备发送所述处理单元处理得到的第二计费信息；
    所述发送单元，还用于将所述接收单元接收到的用户的业务数据流中除识别出的本地业务数据流外的其他业务数据流透传给第一网关设备。
  12. 如权利要求11所述的装置，其特征在于，所述第二计费标识是所述接收单元预先接收到由所述第一网关设备发送的。
  13. 如权利要求11或12所述的装置，其特征在于，在针对识别出的本地业务进行计费得到第二计费信息时，所述处理单元具体用于：
    针对离线计费，针对用户使用识别出的本地业务数据流的情况进行统计得到统计信息，并基于统计信息生成计费话单；或者，
    针对在线计费，针对用户使用识别出的本地业务数据流的情况进行统计得到统计信息，并基于统计信息生成在线计费配额申请信息；或者，
    针对AAA计费，针对用户使用识别出的本地业务数据流的情况进行统计得到统计信息，并基于统计信息生成AAA计费信息。
  14. 一种计费装置，其特征在于，所述装置应用于第一网关设备，包括：
    接收单元，用于接收到第二网关设备发送的针对用户使用本地业务数据流的情况进行统计得到的第二统计信息；
    处理单元，用于基于接收单元接收到的所述第二统计信息生成第二计费信息并使用第二计费标识将所述第二计费信息标记后；所述第二计费标识用于标识所述用户的本地业务对应的计费信息；
    发送单元，用于将标记后的第二计费信息发送给计费系统；
    所述处理单元，还用于在所述接收单元接收到所述用户的非本地业务数据流时，针对所述用户使用非本地业务数据流的情况进行计费并生成第一计费信息，所述第一计费信息携带第一计费标识，所述第一计费标识用于标识 所述用户的非本地业务对应的计费信息；
    所述发送单元，还用于将处理单元处理得到的所述第一计费信息发送给计费系统。
  15. 如权利要求14所述的装置，其特征在于，在所述接收单元接收到第二网关设备发送的第二统计信息之前，所述处理单元还用于为所述用户生成所述第一计费标识以及为所述用户生成所述第二计费标识。
  16. 一种计费装置，其特征在于，所述装置应用于第二网关设备，包括：
    接收单元，用于接收用户的业务数据流；
    处理单元，用于识别出所述接收单元接收到的业务数据流中的用户的本地业务对应的本地业务数据流；并针对用户使用识别出的本地业务数据流的情况进行统计得到第二统计信息；
    发送单元，用于向第一网关设备发送所述处理单元得到的第二统计信息；
    所述发送单元，还用于将所述接收单元接收到的用户的业务数据流中除识别出的本地业务外的其他业务数据流透传给第一网关设备。
PCT/CN2016/097012 2016-08-26 2016-08-26 一种计费方法及装置 WO2018035867A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2016/097012 WO2018035867A1 (zh) 2016-08-26 2016-08-26 一种计费方法及装置

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2016/097012 WO2018035867A1 (zh) 2016-08-26 2016-08-26 一种计费方法及装置

Publications (1)

Publication Number Publication Date
WO2018035867A1 true WO2018035867A1 (zh) 2018-03-01

Family

ID=61246718

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/097012 WO2018035867A1 (zh) 2016-08-26 2016-08-26 一种计费方法及装置

Country Status (1)

Country Link
WO (1) WO2018035867A1 (zh)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2007091819A1 (en) * 2006-02-07 2007-08-16 Ktfreetel Co., Ltd. Method and system for charging in multi-pdp enviroment
CN101998347A (zh) * 2009-08-24 2011-03-30 中兴通讯股份有限公司 本地ip访问计费信息的获取方法和系统
CN102439902A (zh) * 2010-08-30 2012-05-02 华为技术有限公司 本地路由业务的计费方法、装置及网络系统
CN103634774A (zh) * 2012-08-21 2014-03-12 中兴通讯股份有限公司 一种对无线侧本地流量进行计费的方法和装置

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2007091819A1 (en) * 2006-02-07 2007-08-16 Ktfreetel Co., Ltd. Method and system for charging in multi-pdp enviroment
CN101998347A (zh) * 2009-08-24 2011-03-30 中兴通讯股份有限公司 本地ip访问计费信息的获取方法和系统
CN102439902A (zh) * 2010-08-30 2012-05-02 华为技术有限公司 本地路由业务的计费方法、装置及网络系统
CN103634774A (zh) * 2012-08-21 2014-03-12 中兴通讯股份有限公司 一种对无线侧本地流量进行计费的方法和装置

Similar Documents

Publication Publication Date Title
US9973989B2 (en) Co-location of application service platform with access node and local gateway
US9479917B1 (en) Rating group-specific actions for mobile networks
EP2932745B1 (en) Method and system for hub breakout roaming
EP3424231B1 (en) A method and a base station for controlling user data traffic between the wireless device and a local cloud
CN101227391B (zh) 非漫游场景下策略和计费规则功能实体的选择方法
US8989116B2 (en) Method and system for setting up a bearer
US11272333B2 (en) Convergent charging method and device
US20200162855A1 (en) Multicast data transmission method, related device, and communications system
CN103636283A (zh) 网关系统、设备和通信方法
US10348678B2 (en) Network device and method for allocating access point name
EP3484203B1 (en) Service data transmitting method and equipment
CN108781361A (zh) 用于处理数据包的方法及设备
WO2015143856A1 (zh) 一种漫游场景下的应用检测控制方法及v-pcrf
CN102238507A (zh) 确定策略和计费规则功能的方法及系统
WO2018201999A1 (zh) 用户面链路建立方法、基站及移动性管理设备
WO2017113967A1 (zh) 数据报文发送方法、装置和系统
CN105532012B (zh) 视频分发方法、设备和系统
CN103369502B (zh) 一种策略控制会话的处理方法及网元
WO2014134819A1 (zh) 计费方法、接入网设备及网关设备
WO2018035867A1 (zh) 一种计费方法及装置
CN110890967A (zh) 一种计费处理方法、网元及网络系统
WO2018120246A1 (zh) 一种数据传输方法及相关网元
JP2014531159A (ja) 潜在的な複数のエンティティと互いに関連するメッセージを処理すること
WO2016041365A1 (zh) 数据传输的方法和设备
KR102135714B1 (ko) 이동통신 서비스 정책 관리 장치 및 방법

Legal Events

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

Ref document number: 16913888

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

Country of ref document: EP

Kind code of ref document: A1