WO2017193303A1 - 一种通信计费方法 - Google Patents

一种通信计费方法 Download PDF

Info

Publication number
WO2017193303A1
WO2017193303A1 PCT/CN2016/081692 CN2016081692W WO2017193303A1 WO 2017193303 A1 WO2017193303 A1 WO 2017193303A1 CN 2016081692 W CN2016081692 W CN 2016081692W WO 2017193303 A1 WO2017193303 A1 WO 2017193303A1
Authority
WO
WIPO (PCT)
Prior art keywords
service data
information
data information
mapping relationship
plane device
Prior art date
Application number
PCT/CN2016/081692
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/081692 priority Critical patent/WO2017193303A1/zh
Publication of WO2017193303A1 publication Critical patent/WO2017193303A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/14—Charging, metering or billing arrangements for data wireline or wireless communications

Definitions

  • the present invention relates to the field of communication charging technologies, and in particular, to a communication charging method and apparatus.
  • the gateway control plane (Gateway Control Plane, GW-C) and the Gateway User Plane (GW-U) are generally used to complete the user.
  • GW-C mainly completes user access, policy control, and billing management.
  • the GW-U is mainly responsible for forwarding data and performing control and charging policies issued by the control plane.
  • the GW-C and GW-U are used to pre-configure the charging control policy when processing the control and forwarding separate gateway charging.
  • the GW-C allocates a context for the bearer of the user, records the state charging information of the bearer, and sends the charging control information to the GW-U.
  • the GW-U performs charging based on the charging control information sent by the GW-C, and reports the obtained charging information to the GW-C, and the GW-C generates a bill according to the GW-C.
  • the prior art mainly deals with bearer level charging under the architecture of control and forwarding separation, which is not flexible enough and is not reasonable enough.
  • the embodiment of the invention provides a communication charging method and device.
  • the embodiment of the present invention can implement a more flexible and reasonable charging of the service requested by the user, thereby improving the user experience.
  • an embodiment of the present invention provides a communication charging method.
  • the gateway user plane device determines a first mapping relationship between the service data information and the charging rule.
  • Gateway user plane device is used
  • the network device that the user equipment provides the service receives the packet data, parses the packet data to obtain the first service data information, and determines the first charging rule according to the first service data information and the first mapping relationship, where the first mapping relationship includes the Determining a second mapping relationship between the first service data information and the first charging rule.
  • the gateway user plane device performs charging processing on the packet data according to the first charging rule.
  • the same charging rule may map one or more service data information, and the service corresponding to the one or more service data information needs to be charged by the same charging rule.
  • the service data information is corresponding to the charging rule.
  • the service can be differentiated according to the service data information of different granularities, and the charging process is separately performed, thereby realizing more flexible and reasonable. More accurate billing improves the user experience.
  • the foregoing service data information includes one or more of the following: bearer information, service flow information, and content information.
  • the bearer information, the service flow information, the content information, and the like may respectively include one or more specific information.
  • the charging rule corresponding to the service data information of the bearer information, the service flow information, the content information, and the like can be implemented, and the charging is also determined according to the service data information such as the bearer information, the service flow information, the content information, and the like during the charging. Rules and billing enable more flexible, more reasonable, and more accurate billing, which improves the user experience.
  • the method before the gateway user plane device determines the first mapping relationship between the service data information and the charging rule, the method further includes: the gateway user plane device receiving the configuration information sent by the gateway control plane device, where the configuration information is Including the first mapping relationship.
  • the embodiment of the present invention can realize that the mapping relationship between the service data information and the charging rule is uniformly configured by the gateway control plane device, which facilitates management, makes the charging more reasonable, and improves the user experience.
  • the first mapping relationship between the service data information and the charging rule includes: a first sub-map relationship between the service data information and the rate group identifier, and a fee group identifier and a charging rule.
  • the second sub-map relationship can be implemented to determine the mapping relationship by dividing the rate group, and the association is performed by the rate group identifier, so that the charging method is easier to implement, more flexible, and improves the user experience.
  • the foregoing determining, according to the first service data information, the first charging The rule includes: the gateway user plane device determines the first rate group identifier according to the first service data information and the first sub-map relationship of the service data information and the rate group identifier, where the first sub-map relationship includes the first service The mapping relationship between the data information and the first rate group identifier.
  • the gateway user plane device determines the first charging rule according to the first rate group identifier and the second sub-map relationship between the rate group identifier and the charging rule, where the second sub-map relationship includes the first rate group identifier and the first A mapping relationship of charging rules.
  • the embodiment of the present invention can be implemented to determine the charging rule by using the rate group identifier, so that the charging method is easier to implement, more flexible, and improves the user experience.
  • the method further includes: the gateway user plane device receiving the request message sent by the gateway control plane device, where the request message carries the third mapping relationship between the second service data information and the second charging rule.
  • the gateway user plane device modifies the mapping relationship between the service data information and the first mapping relationship of the charging rule regarding the second service data information to The third mapping relationship is: when the service data information does not include the second service data information, the gateway user plane device adds a third mapping relationship in the first mapping relationship between the service data information and the charging rule.
  • the embodiment of the present invention can implement the method of adding or modifying the mapping relationship between the service data information and the charging rule, so that the charging is more flexible and more reasonable, and the user experience is improved.
  • an embodiment of the present invention provides a communication charging method.
  • the gateway control plane device determines a first mapping relationship between the service data information and the charging rule; the gateway control plane device sends configuration information to the gateway user plane device, where the configuration information includes the first mapping relationship between the service data information and the charging rule.
  • the mapping relationship is used for determining the charging rule.
  • the embodiment of the present invention can realize that the mapping relationship between the service data information and the charging rule is uniformly configured by the gateway control plane device, which facilitates management, makes the charging more reasonable, and improves the user experience.
  • the gateway control plane device determines that the first mapping relationship between the service data information and the charging rule includes: the service user identifier and the charging rule sent by the gateway user plane device receiving policy and the charging rule function unit.
  • the fourth mapping relationship wherein any one of the foregoing service identifiers corresponds to service data information.
  • the gateway user plane device determines the service data letter corresponding to the service identifier.
  • the first mapping relationship is determined according to the fourth mapping relationship.
  • the gateway control plane device determines the mapping relationship between the service data information and the charging rule through the policy and charging rule function unit, and then performs unified configuration, facilitates management, makes charging more reasonable, and improves user experience. .
  • the determining, by the gateway control plane device, the first mapping relationship between the service data information and the charging rule includes: the first mapping relationship between the predefined control service data information of the gateway control plane device and the charging rule.
  • the embodiment of the present invention can implement the mapping between the predefined service data information and the charging rule, and then perform unified configuration, which facilitates management, makes the charging more reasonable, and improves the user experience.
  • the gateway control plane device determines that the first mapping relationship between the service data information and the charging rule includes: the gateway control plane device divides the rate group according to the service data information, and each rate group corresponds to one The rate group identifier, which maps all the service data information in the same rate group to the same charging rule.
  • the embodiment of the present invention can be implemented to determine the mapping relationship by dividing the rate group, and the association is performed by the rate group identifier, so that the charging method is easier to implement, more flexible, and improves the user experience.
  • an embodiment of the present invention provides a communication charging apparatus.
  • the system includes: an interface logic unit, each interface logic unit corresponding to one or more session logic units, each session logic unit corresponding to one or more billing logic units: an interface logic unit, configured to determine service data information and charging rules a first mapping relationship, configured according to the first mapping relationship between the service data information and the charging rule, the session logic unit and the charging logic unit; the interface logic unit is further configured to receive the packet data from the network device that provides the service for the user equipment, where The packet data is parsed to determine a session logic unit corresponding to the packet data, and the packet data is sent to a session logic unit corresponding to the packet data; the session logic unit is configured to receive the location sent by the interface logic unit Decoding the packet data, parsing the packet data to obtain the first service data information, determining, according to the first service data information and the first mapping relationship, the first charging rule to determine the charging logic unit corresponding to the first service data information, and sending the packet data to a billing logic unit, wherein the first
  • the service data information includes one or more of the following: bearer information, service flow information, and content information.
  • the interface logic unit is further configured to: receive configuration information sent by the gateway control plane device, where the configuration information includes a first mapping relationship between the service data information and the charging rule.
  • the first mapping relationship between the service data information and the charging rule includes: a first sub-map relationship between the service data information and the rate group identifier, and a fee group identifier and a charging rule. The second sub-map relationship. And configuring the session logic unit and the charging logic unit according to the first mapping relationship between the service data information and the charging rule, including: configuring the charging logic unit according to the first sub-map relationship between the rate group identifier and the charging rule, according to the service data information The session logic unit is configured with a second sub-map relationship of the rate group identification.
  • the session logic unit is further configured to: determine, according to the first service data information and the first sub-map relationship, the first rate group identifier, where the first sub-map relationship includes the first The mapping relationship between the service data information and the first rate group identifier, the first rate group identifier and the packet data are sent to the billing logic unit corresponding to the first rate group identifier, where the rate group identifier includes the first rate a group identifier; the billing logic unit is further configured to: determine, according to the first rate group identifier and the second sub-map relationship, the first billing rule, where the second sub-map relationship includes the first rate group identifier and the first meter The mapping relationship of the fee rules.
  • the method further includes: an interface logic unit, configured to receive a request message sent by the gateway control plane device, where the request message carries a third mapping of the second service data information and the second charging rule a relationship; when the service data information includes the second service data information, the interface logic unit modifies the session corresponding to the second service data information according to the mapping relationship between the second service data information and the second charging rule a logic unit, creating a charging logic unit corresponding to the second service data information; when the service data information does not include the second service data information, The interface logic unit creates a session logic unit and a charging logic unit corresponding to the second service data information according to the mapping relationship between the second service data information and the second charging rule.
  • an embodiment of the present invention provides a communication and charging apparatus, including: a determining unit, configured to determine a first mapping relationship between service data information and a charging rule; and a receiving unit, configured to be a user And the processing unit is configured to: The first mapping relationship includes a second mapping relationship between the first service data information and the first charging rule; and the charging unit is configured to perform charging processing on the packet data according to the first charging rule.
  • the service data information includes one or more of the following: bearer information, service flow information, and content information.
  • the receiving unit is further configured to receive configuration information sent by the gateway control plane device, where the configuration information includes a first mapping of the service data information and the charging rule. relationship.
  • the first mapping relationship between the service data information and the charging rule includes: a first sub-map relationship between the service data information and a rate group identifier, and the rate The group identifier is associated with the second sub-map relationship of the charging rule.
  • the processing unit is further configured to: determine, according to the first service data information and the first sub-map relationship, the first rate group identifier, where the first sub-map relationship includes the first service a mapping relationship between the data information and the first rate group identifier; determining, according to the first rate group identifier and the second sub-map relationship, the first charging rule, where the second sub-map relationship includes the first rate group identifier The mapping relationship with the first charging rule.
  • the receiving unit is further configured to receive a request message sent by the gateway control plane device, where the request message carries a third mapping relationship between the second service data information and the second charging rule;
  • the processing unit is further configured to: when the service data information includes the second service data information, modify the mapping relationship of the second service data information in the first mapping relationship to And the processing unit is further configured to: when the service data information does not include the second service data information, add a third mapping relationship in the first mapping relationship.
  • an embodiment of the present invention provides a communication charging apparatus, including: a determining unit, configured to determine a first mapping relationship between service data information and a charging rule; and a sending unit, configured to The gateway user plane device sends configuration information, where the configuration information includes a first mapping relationship between the service data information and the charging rule.
  • the receiving unit is further configured to receive a fourth mapping relationship between the service identifier sent by the policy and charging rule function unit and the charging rule, where the service identifier corresponds to service data.
  • the determining unit is further configured to determine, according to the fourth mapping relationship between the service identifier and the charging rule, the first mapping relationship between the service data information and the charging rule.
  • the determining unit is further configured to: pre-define a first mapping relationship between the service data information and the charging rule.
  • the determining unit is further configured to divide the rate group according to the service data information, where each rate group corresponds to a rate group identifier, and all the service data in the same rate group are divided.
  • the information maps the same charging rules.
  • an embodiment of the present invention provides a gateway user plane device, where the gateway user plane device has a function of implementing a behavior of a gateway user plane device in the foregoing method.
  • This function can be implemented in hardware or in hardware by executing the corresponding software.
  • the hardware or software includes one or more modules corresponding to the functions described above.
  • the gateway user plane device includes a processor and a communication unit, wherein the processor is configured to support the gateway user plane device to perform the corresponding function in the above method.
  • the communication unit is configured to support communication between the gateway user plane device and the gateway control plane device and other network devices, and send information or instructions involved in the foregoing method to the gateway control plane device and other network devices.
  • the gateway user plane device can also include a memory for coupling with the processor that retains program instructions and data necessary for the gateway user plane device.
  • an embodiment of the present invention provides a gateway control plane device.
  • the gateway control plane The device has the function of realizing the behavior of the gateway control plane device in the above method. This function can be implemented in hardware or in hardware by executing the corresponding software.
  • the hardware or software includes one or more modules corresponding to the functions described above.
  • the gateway control plane device includes a processor and a communication unit.
  • the processor is configured to support the gateway control plane device to perform the corresponding functions in the above methods.
  • the communication unit is configured to support communication between the gateway control plane device and the gateway user plane device and other network devices, and send information or instructions involved in the foregoing method to the gateway user plane device and other network devices.
  • the gateway control plane device can also include a memory for coupling with the processor that retains program instructions and data necessary for the gateway control plane device.
  • an embodiment of the present invention provides a communication charging system, where the system includes the gateway control plane device and the gateway user plane device of the foregoing aspect.
  • an embodiment of the present invention provides a computer storage medium for storing computer software instructions used by the gateway user plane device, which includes a program designed to perform the above aspects.
  • an embodiment of the present invention provides a computer storage medium for storing computer software instructions used by the gateway control plane device, including a program designed to perform the above aspects.
  • the embodiments provided by the present invention can implement correct decryption of the data packets encrypted by the user equipment using the key under the RRC connection, thereby ensuring normal communication of the user equipment and improving the user experience.
  • the rate group may be divided from the service data information of different granularities, and the charging rule corresponding to each rate group is determined.
  • the charging rule is determined according to the service data information, according to the accounting rule.
  • the fee rule is used for billing, which enables more flexible, more reasonable and more accurate billing, which improves the user experience.
  • FIG. 1 is a schematic diagram of a system architecture
  • FIG. 2 is a schematic diagram of another system architecture
  • FIG. 3 is a schematic diagram of communication of a communication charging method according to an embodiment of a method according to the present invention.
  • FIG. 4 is a schematic diagram of another communication charging method according to an embodiment of a method according to the present invention.
  • FIG. 5 is a schematic diagram of a virtual structure of a gateway user plane device according to an embodiment of the present disclosure
  • FIG. 6 is a schematic diagram of communication of another communication charging method according to an embodiment of a method according to the present invention.
  • FIG. 7 is a schematic diagram of communication of another communication charging method according to an embodiment of a method according to the present invention.
  • FIG. 8 is a schematic diagram of communication of another communication charging method according to an embodiment of a method according to the present invention.
  • FIG. 9 is a schematic diagram of communication of another communication charging method according to an embodiment of a method according to the present invention.
  • FIG. 10 is a schematic diagram of communication of another communication charging method according to an embodiment of a method according to the present invention.
  • FIG. 11 is a schematic diagram of a virtual structure of another communication charging apparatus according to an embodiment of the present invention.
  • FIG. 12 is a schematic diagram of a virtual structure of another communication charging apparatus according to an embodiment of the present invention.
  • FIG. 13 is a schematic structural diagram of a gateway user plane device entity according to an embodiment of the present disclosure.
  • FIG. 14 is a schematic structural diagram of an entity of a gateway control plane device according to an embodiment of the present invention.
  • Evolved Universal Terrestrial Radio Access Network Evolved Universal Terrestrial Radio Access Network
  • MME mobility management Mobility Management Entity
  • PGW Packet Data Network Gateway
  • SGW Serving Gateway
  • HSS Home Subscriber Server
  • PCRF Policy and Charging Rules Policy and Charging Rules Function
  • PDN Packet Data Network
  • AAA Authentication and Accounting
  • DHCP Dynamic Host Configuration Protocol
  • UTRAN Universal Terrestrial Radio Access Network
  • UTRAN Global System for Mobile Communications Enhanced Data Rate for GSM Evolution Radio Access Network
  • GERAN Global System for Mobile Communications Enhanced Data Rate for GSM Evolution Radio Access Network
  • SGSN Serving General Packet Radio Service Support Node
  • E-UTRAN is used to implement all functions related to the evolution network wireless.
  • the MME is responsible for the mobility management of the control plane, including user context and mobility state management, and assigning Temporary Mobile Subscriber Identity (TMSI).
  • TMSI Temporary Mobile Subscriber Identity
  • the S-GW is a user plane anchor between 3GPP access networks, terminating the interface of the E-TURAN.
  • the P-GW is a user plane anchor between the 3GPP access network and the non-3GPP access network, and an interface of the PDN.
  • the HSS is used to store user subscription information.
  • the MME, S-GW, P-GW, and HSS are usually used as core network devices.
  • the user equipment accesses the E-UTRAN through the wireless air interface, it first attaches to the MME, and the MME obtains the subscription data and the authentication information of the user equipment (User Equipment, UE) from the HSS, and initiates a process of authenticating the UE.
  • the MME completes the authentication process, the user equipment or the MME initiates a process of establishing a bearer for transmitting user data.
  • the MME notifies the S-GW to establish a bearer for the user, and carries the address of the P-GW and the address information of the E-UTRAN network device where the user is located in the notification message.
  • the S-GW establishes a bearer for transmitting user data from the E-UTRAN to the P-GW for the user.
  • P-GW will come from outside
  • the downlink data of the PDN is forwarded to the UE through the bearer, and the uplink data from the UE is forwarded to the corresponding PDN.
  • the UE may access the MME through the UTRAN or the GERAN and the SGSN, and may be connected through the UTRAN/GERAN, the SGSN, and the S-GW through a General Packet Radio Service Tunneling Protocol (GTP).
  • GTP General Packet Radio Service Tunneling Protocol
  • the S-GW converts the GTP tunnel into a corresponding bearer connected to the P-GW for transmitting user data.
  • the UTRAN can also establish a GTP tunnel that directly connects to the S-GW.
  • the MME becomes a network device that only processes control plane signaling, and the S-GW and the P-GW are mainly responsible for forwarding user plane data.
  • the S-GW and the P-GW can be combined into one network device, generally referred to as a gateway.
  • interface signaling includes: bearer interface signaling, policy control and charging (PCC) interface signaling, charging interface signaling, lawful interception interface signaling, and external PDN interface signaling (eg, DHCP, AAA, etc.) Processing function.
  • PCC policy control and charging
  • charging interface signaling charging interface signaling
  • lawful interception interface signaling e.g., DHCP, AAA, etc.
  • external PDN interface signaling e.g, DHCP, AAA, etc.
  • the S-GW, P-GW, and GGSN are basically the same on the platform architecture, we collectively call it a gateway. See Figure 2 for the architecture separating the control plane and user plane of the gateway.
  • the gateway user plane can be deployed in a distributed manner. For example, some GW-Us can be deployed at the core aggregation point of the transport network as the mobile anchor gateway user plane. Some GW-Us can be deployed at the convergence point of the transport network or integrated as a local access gateway user of the non-communication service at the base station. surface.
  • the gateway control plane device GW-C can perform unit function scheduling on the GW-U according to different services to determine whether the service data passes through the anchor point.
  • the control plane device (GW-C) of the gateway may be referred to as a Control Plane Gateway, and may also be referred to as a Gateway Controller, a Control Node, or a Control Gateway.
  • the user plane device (GW-U) of the gateway may be called a User Plane Gateway, and may also be called a Packet Data Forwarding Gateway, a Routing Forwarding Node, or a Switching Node (Switch). Node).
  • the SMSs (MME/SGSN) are all based on a common computing platform, so the two can be combined.
  • the GW-C can send control commands, configuration information, and the like to the GW-U.
  • the GW-U can perform charging processing on the passed packet data.
  • the embodiments of the present invention perform corresponding charging processing on packet data corresponding to different services according to different service requirements of different service granularity, so that the service of the user equipment is more reasonable. More accurate and flexible billing. Improve the user experience.
  • FIG. 3 is a flowchart of a communication charging method according to an embodiment of the present invention. As shown in Figure 3. The embodiments of the present invention are applicable to the foregoing system architecture. The method may specifically include:
  • the gateway user plane device determines a first mapping relationship between the service data information and the charging rule.
  • the rate group may be pre-defined by the service data information of different granularities corresponding to different services, and the charging rules corresponding to each rate group may be determined according to the different granularity requirements of the different services. That is, the first mapping relationship between the service data information and the charging rule is established.
  • the service data information may include one or more of bearer information, traffic flow information, content information, and the like.
  • the bearer information, the service flow information, and the content information belong to different granularity of service data information.
  • the corresponding rate group may be predefined according to one or more of the bearer information, the service flow information, and the content information.
  • the rate group can be divided according to different bearer information.
  • the bearer information corresponding to the service with the same rate can be classified into the same rate group.
  • each rate group corresponds to one or more bearer information with the same rate.
  • the rate group may be divided according to the service flow information or the content information, and the rate group divided according to the service flow information information, the one or more service flow information with the same rate may be classified into the same rate group; According to the rate group divided by the content information, one or more content information having the same rate may be classified into the same rate group.
  • the rate group In order to cope with different billing requirements, it can also combine bearer information, service flow information and content. Any two or more of the information is used to divide the rate group to provide a more detailed rate group definition.
  • the service data information of the video service, the call service, and the short message service of different user equipments are different, or the service data information of different video services, call services, and short message services of the same user equipment are also different.
  • Different services have different requirements for charging rules, charging granularity, etc., and even the same service has different requirements for charging rules and charging granularity of different user equipments.
  • the service data information corresponding to the user equipment and its corresponding video service, call service, and short message service may be divided into different rate groups, and the video service, the call service, and the short message service may also be performed.
  • the rate group is divided into the bearer information, the service flow information, and the content information, respectively.
  • the charging rule corresponding to the video service can be defined as the statistical traffic
  • the charging rule corresponding to the call service is defined as the statistical duration
  • the charging rule corresponding to the short message service is defined as The number of statistics.
  • the rate group may be divided according to the content information; for the call service, the rate group may be divided according to the service flow information, and for the short message service, the rate group may be divided by the bearer information.
  • charging measurement can be performed separately according to different types of services, and charging measurement can be performed according to different charging granularities, so that charging is more flexible and more reasonable.
  • the service data information may further include other granular data information except the bearer information, the service flow information, and the content information, which are merely examples and are not limited thereto.
  • one or more predefined rate groups may be selected by a gateway user plane device, a gateway control plane device, a Charging Gateway (CG), an Online charging function (OCF), and a PCRF. Determine the billing rules for each rate group. Specifically, the following implementation manners are possible.
  • the gateway control plane device may predefine the rate group according to the service data information, and determine the charging rule corresponding to each rate group.
  • the gateway control plane device may send the rate group information including the mapping relationship between the service data information and the charging rule to the gateway user plane device.
  • Gateway user plane The device is configured according to the received rate group information.
  • the gateway user plane device receives the packet data of the service, the corresponding charging process is performed according to the charging rule corresponding to the service.
  • the rate user group can be defined in advance according to the service data information, and the charging rule corresponding to each rate group can be determined.
  • the mapping relationship between the service and the charging rule may be predefined by the PCRF, the CG, or the COF.
  • the gateway control plane device can obtain the mapping relationship between the service and the charging rule from the PCRF, the CG, or the COF, or the PCRF, the CG, or the COF can actively send the mapping relationship between the service and the charging rule to the gateway control plane device.
  • the gateway control plane device generates a mapping relationship between the service data information and the charging rule according to the mapping relationship between the service and the charging rule.
  • the gateway control plane device may send the rate group information including the mapping relationship between the service data information and the charging rule to the gateway user plane device.
  • the PCRF, CG, or COF may further define a charging granularity requirement of the service and send it to the gateway control plane device, and the gateway control plane device may select the service data of the corresponding granularity according to the charging granularity requirement of the service to determine the rate. group.
  • rate group there may be multiple ways of pre-defining the rate group according to the service data information of different granularities, and determining the charging rules corresponding to each rate group, which are merely examples and are not limiting.
  • the charging rule may include one or more of the following information:
  • APN Charging Characteristic
  • accounting measurement configuration information charging method (offline charging or online charging), accounting reporting information (a certain duration threshold, traffic threshold or number threshold reporting), charging action Information (continue, discard or redirect packet data) and more.
  • the bearer information may include one or more of a bearer identifier, GTP tunnel information, and IP tunnel information.
  • the bearer identity may be an S1 bearer identity, an S5/8 bearer identity, or the like.
  • the GTP tunnel information may be a GTP tunnel address, a GTP tunnel identifier, or the like.
  • the GTP tunnel information can be the Internet Protocol (IP) and the number of users.
  • IP Internet Protocol
  • UDP User Datagram Protocol
  • TEID Tunnel Endpoint ID
  • the IP tunnel information may be Generic Routing Encapsulation (GRE) information, IP Security (IPSec) information, Layer 2 Tunneling Protocol (L2TP) information, and Virtual Local Area Network (Virtual Local Area Network).
  • GRE Generic Routing Encapsulation
  • IPSec IP Security
  • L2TP Layer 2 Tunneling Protocol
  • VLAN Virtual Local Area Network
  • VxLAN Virtual Extensible Local Area Network
  • MIP Multiple Information Passage
  • the service flow information may include one or more of a Service Flow Identifier (SFID), transport layer information, and network layer information.
  • SFID Service Flow Identifier
  • transport layer information and the network layer information are also quintuple information of the service data.
  • the network layer information may include a source and destination IP address, a source and destination port number, and the transport layer information may include a transport layer protocol, such as a source, a destination protocol type, and the like.
  • the content information may include one or more of content identification and application layer information and the like.
  • the application layer information may include Uniform Resource Locator (URL) information.
  • URL Uniform Resource Locator
  • one user equipment requests multiple services, that is, one user equipment corresponds to multiple services; one service data may need one or more bearers for transmission, and the service data is one or more.
  • the service flow is transmitted in the form of a service, that is, a service can correspond to one or more bearer information and one or more service flow information; the service flow includes one or more content information, that is, one service flow information or one bearer information. Can correspond to one or more content information.
  • the gateway user plane device receives packet data (Packet) from a network device that provides service for the user equipment.
  • the packet data includes service data information such as bearer information, traffic flow information, and content information.
  • the network device that provides services for the user equipment may include: an evolved base station (evolved Node) B, eNB), Internet Server (Internet Server), S-GW, P-GW, Evolved Packet Data Gateway (ePDG), High Rate Packet Data Serving Gateway (HSGW), etc. .
  • eNB evolved base station
  • Internet Server Internet Server
  • S-GW Internet Server
  • P-GW Evolved Packet Data Gateway
  • HSGW High Rate Packet Data Serving Gateway
  • the packet data that interacts with the user equipment is generally transmitted through the gateway user plane device, and the packet data includes the service data of the user equipment.
  • the gateway user plane device parses the received packet data to obtain the first service data information, and determines the first charging rule according to the first service data information and the first mapping relationship, where the first mapping relationship includes the first service data information.
  • a second mapping relationship with the first charging rule may be any one or more of bearer information, service flow information, and content information.
  • the bearer information obtained by parsing the packet data may include one or more of the following: a bearer identifier, GTP tunnel information, and the like.
  • the service flow information obtained by parsing the packet data may include one or more of the following: a service flow identifier, transport layer information, network layer information, and the like.
  • the content information obtained by parsing the packet data may include one or more of the following: content identification, application layer information, and the like.
  • the rate group is divided according to the service data information, that is, the charging rule is mapped to the service data information.
  • determining the service data information included in the packet data can determine its corresponding first charging rule.
  • the bearer information obtained by parsing the packet data of the service may be determined according to the mapping relationship between the bearer information and the bearer information in the first mapping relationship, and the corresponding first Billing rules.
  • the mapping between the TEID obtained by the parsing packet data and the locally stored service data information and the charging rule is matched by the gateway user plane device to obtain a mapping relationship between the TEID and the first charging rule.
  • an IP address can be obtained based on parsing the packet data.
  • the mapping between the address and the TEID, and the locally stored service data information and the charging rule, and the mapping between the IP address and the TEID and the first charging rule are obtained.
  • the corresponding bearer information may also be determined according to the content information and/or the service flow information.
  • the corresponding first flow rule may be determined by analyzing the service flow information obtained by the packet data of the service.
  • the gateway user plane device can obtain the quintuple information according to the parsed packet data, for example, the source IP address, the destination IP address, the source port number, the destination port number, and the protocol type, and determine the corresponding first billing according to the quintuple information.
  • Rules for example, for a rate group divided according to different source IP addresses, the mapping relationship between the source IP address and the locally stored service data information and the charging rule may be obtained according to the parsed packet data, and the matching source IP address and the first meter are obtained. The mapping relationship of the fee rules.
  • the source IP address and the source port number are mapped to the locally stored service data information and the charging rule according to the parsed packet data, and the source IP address and the source are matched.
  • the manner of determining the first charging rule according to the source IP address and the source IP address and the source port number is only an example, and does not constitute a limitation on the embodiment of the present invention, and uses other service flow information or other service flow information.
  • the manner in which the first charging rule is determined in combination is also within the scope of the embodiments of the present invention, and the determination is not described again.
  • the corresponding service flow information may be determined based on the content information.
  • the corresponding first charging rule may be determined by parsing the content information obtained by the packet data of the service.
  • the gateway user plane device For example, for a rate group divided according to different URL information, the gateway user plane device according to the solution The mapping relationship between the URL information obtained by the packet data and the locally stored service data information and the charging rule is matched, and the mapping relationship between the URL information and the first charging rule is obtained.
  • the manner of determining the first charging rule according to the URL information is only an example, and does not constitute a limitation on the embodiment of the present invention.
  • the manner of determining the first charging rule by using other content information is also in the embodiment of the present invention. Within the scope, we will not repeat them.
  • the gateway user plane device performs measurement according to the first charging rule, and after obtaining the charging measurement information, the charging measurement information may be sent to the gateway control plane device, and the gateway control plane device generates the user current service according to the charging measurement information. single.
  • the bill can also be generated directly by the gateway user plane device.
  • the gateway user plane device When the gateway user plane device performs the charging information measurement according to the first charging rule, the time length and the traffic information used by the service corresponding to the first service data information may be collected according to the charging measurement configuration information included in the first charging rule. And one or more of the number of times. In other words, the gateway user plane device may use the service data information corresponding to the first charging rule to measure one or more times, such as the length of time, the traffic information, and the number of times the network device provides the service for the user equipment.
  • the gateway user plane device may send the charging measurement information to the gateway control plane device according to the charging report information included in the first charging rule, for example, may report according to the set time interval; or may send according to the gateway control plane.
  • the configuration information is determined to be reported when the billing measurement information reaches the threshold, and may be reported after the end of the service.
  • the gateway user plane device can obtain account information corresponding to the user equipment, such as an account balance, a time limit, a traffic upper limit, or a maximum number of times. The information can be obtained from the gateway control plane.
  • the gateway user plane device performs the charging measurement, when the corresponding account balance is insufficient, or the usage upper limit is reached, the charging measurement information is reported to the gateway control plane device.
  • the duration, flow rate, or number of times that the charging information can be included in the charging measurement information.
  • the threshold information can be configured by the gateway control plane or by default on the gateway user plane.
  • the gateway user plane device may also report the charging measurement information to the gateway control plane device in the case of the rate change, the end of the user service, or the direct indication of the gateway control plane.
  • the gateway user plane device billing may continue to be provided. Forwarding service. For example, after the accounting reaches the threshold, the gateway control device is reported. After the gateway user plane device reports the packet, the accounting measurement information is cleared and the statistics are re-stated. Or, after the gateway user plane device reaches the threshold, directly discarding the received packet data of the corresponding user equipment, and after receiving the threshold sent by the gateway control plane device again, forwarding the packet data and performing charging. measuring. Alternatively, the data service corresponding to the user equipment can be redirected to a website, for example, can be redirected to the credit recharge page.
  • the gateway control plane device After receiving the charging measurement information, the gateway control plane device generates the current service charging information based on the charging measurement information, the first charging rule, and the user service information, and may also send the generated current service charging information to the CG or OCF and so on.
  • the user service information mainly includes an Access Point Name (APN), a bearer information, and a Quality of Service (QoS).
  • API Access Point Name
  • QoS Quality of Service
  • the gateway control plane device may send the current service charging information to the CG or the OCF when the one or more of the following conditions are met: the user service accumulates over the duration threshold, the traffic threshold or the number threshold, the user closes the service, and the like.
  • the gateway user plane device may receive a request message sent by the gateway control plane device, where the request message carries a third mapping relationship between the second service data information and the second charging rule.
  • the gateway user plane device modifies the mapping relationship of the second service data information in the first mapping relationship to the third mapping relationship; when the service data information does not include the first In the case of the second service data information, the gateway user plane device adds the third mapping relationship in the first mapping relationship.
  • the gateway user plane device receives packet data sent by the user equipment, and the packet data carries new content information (eg, a URL) of the acquisition request.
  • the gateway user plane device sends the new content information to the gateway control plane device, and requests to increase the rate group information corresponding to the content information and the charging rule.
  • the gateway control plane device receives a re-authorization request message sent by another network device, where the re-authorization request message is used to request to add a service flow and a charging rule corresponding to the service flow.
  • other network devices here may be PCRF and the like.
  • the gateway control plane device is connected. Received a create session request sent by another network device.
  • the other network devices herein may be an MME, an SGW, or the like.
  • the gateway control plane device may send, to the gateway user plane device, a request message carrying the rate group information and the charging rule (the third mapping relationship between the second service data information and the second charging rule), where The request message is used to request to add or modify the corresponding mapping.
  • the gateway user plane device After receiving the request message sent by the gateway control plane, the gateway user plane device adds or modifies the corresponding mapping relationship.
  • the rate group may be divided from the service data information of different granularities, and the charging rule corresponding to each rate group is determined. When charging is performed, the charging rule is determined according to the service data information, according to the accounting rule.
  • the fee rule performs charging, for example, the rate group is divided according to the service data information such as the bearer information, the service flow information, the content information, and the like, and is determined according to the service data information such as the bearer information, the service flow information, the content information, and the like during the charging.
  • Billing rules and billing enable more flexible, more reasonable, and more accurate billing, which improves the user experience.
  • a Rate Group Identity may also be assigned to each rate group, as shown in FIG. 4 .
  • the method may include the following steps:
  • the gateway user plane device determines a first sub-map relationship between the service data information and the rate group identifier, and a second sub-map relationship between the rate group identifier and the charging rule.
  • each rate group may also be assigned a rate group identifier.
  • one or more predefined rate groups may be selected by a gateway user plane device, a gateway control plane device, a Charging Gateway (CG), an Online charging function (OCF), and a PCRF.
  • CG Charging Gateway
  • OCF Online charging function
  • PCRF PCRF
  • the gateway control plane device pre-defines the rate group according to the service data information, and determines the charging rule corresponding to each rate group, assigns an RGID to each rate group, and establishes a mapping relationship between the RGID and the charging rule. And the mapping relationship between RGID and business data information.
  • the gateway control plane device may send the rate group information including the RGID and the charging rule mapping relationship and the mapping relationship between the RGID and the service data information to the gateway user plane device.
  • the rate user group can be defined in advance according to the service data information, and the charging rule corresponding to each rate group is determined, the RGID is assigned to each rate group, and the RGID and charging rule mapping are established. Relationship and mapping relationship between RGID and business data information.
  • the mapping relationship between the service and the charging rule can be predefined by PCRF, CG or COF.
  • the gateway control plane device can obtain the mapping relationship between the service and the charging rule from the PCRF, the CG, or the COF, or the PCRF, the CG, or the COF can actively send the mapping relationship between the service and the charging rule to the gateway control plane device.
  • the gateway control plane device allocates an RGID to the service according to the mapping relationship between the service and the charging rule, and generates a mapping relationship between the RGID and the charging rule and a mapping relationship between the RGID and the service data information.
  • the gateway control plane device may send the rate group information including the RGID and the charging rule mapping relationship and the mapping relationship between the RGID and the service data information to the gateway user plane device.
  • the PCRF, CG, or COF may further define a charging granularity requirement of the service and send it to the gateway control plane device, and the gateway control plane device may select the service data of the corresponding granularity according to the charging granularity requirement of the service to determine the rate. group.
  • the gateway user plane device receives the packet data from the network device that provides the service for the user equipment.
  • Step S420 is similar to the foregoing step S320 and will not be described again.
  • the gateway user plane device parses the received packet data to obtain first service data information, according to the first sub-map relationship between the first service data information and the first RGID, and the first RGID and the second sub-rule of the first charging rule. Mapping the relationship to determine the first charging rule.
  • Step S440 is similar to the foregoing step S340 and will not be described again.
  • the gateway user plane device may receive a request message sent by the gateway control plane device, where the request message carries the second service data information and the second RGID, and the mapping relationship between the second RGID and the second charging rule.
  • the gateway user plane device modifies the mapping relationship of the second service data information in the first mapping relationship to the second service data information and the second RGID, and the second RGID. a mapping relationship with the second charging rule; when the service data information does not include the second service data information, the gateway user plane device increases in the first mapping relationship And adding a second service data information and a second RGID, and a mapping relationship between the second RGID and the second charging rule.
  • the rate group identification corresponding rate group information may be pre-configured on the gateway user plane device. If the mapping message sent by the gateway control plane device has only the mapping relationship between the second service data information and the second RGID, or the mapping relationship between the service identifier and the second RGID, the gateway user plane device may determine the local configuration based on the second RGID information. Pre-configured other rate group information (second billing rules, etc.).
  • the rate group can be divided from the service data of different granularity, and the service data information of different granularity and the different charging rules are mapped by the rate group identifier, so that the charging data can be realized according to the service data.
  • the information determines the charging rule, and performs charging according to the charging rule, thereby implementing more flexible, more reasonable, and more accurate charging, and improving the user experience.
  • the gateway user plane device 500 can adopt a distributed deployment.
  • some gateway user plane devices can be deployed at a core convergence point of the transmission network, or can be deployed at a convergence point of the transmission network or integrated at the base station.
  • the set of units used by the gateway user plane device 500 to process user data may be divided into a service accounting logic unit 510, a session logic unit 520, an interface logic unit 530, and the like.
  • Each logical unit may contain a function set, attributes, information, and the like of the logical unit, and a function set of each logical unit may include all sub-functions owned by the entire logical unit.
  • session logic unit 520 can include functionality to maintain aggregated QoS control, IP address management under a certain APN of a certain user equipment.
  • the service of one user equipment can be managed by a session logic unit 520.
  • the business context of the user device may include a session context, a bearer context, a traffic flow context, and a content context.
  • User traffic contexts of the same user terminal may be associated with each other, for example, the session context may be associated with one or more bearer contexts, or associated with one or more traffic flow contexts, or associated with one or more content contexts.
  • a bearer context can be associated with one or more traffic flow contexts or associated with one or more content contexts.
  • the billing logic unit 510 can be divided into a bearer logic unit 511, a service flow logic unit 512, and/or a content logic unit 513 according to the requirements of the billing granularity.
  • the bearer logic unit 511 can be used to manage data forwarding, QoS control, and the like of a bearer of the user equipment.
  • the bearer logic unit 511 can distinguish the rate group according to different bearer information, and perform charging according to the charging rule of the corresponding rate group. Billing.
  • the traffic flow logic unit 512 may include functions such as data stream resolution and QoS control at the 5-tuple level of the data service flow of the user equipment.
  • the service flow logic unit 512 can determine the rate group corresponding to the service data according to the service flow information of the different service data, and perform charging according to the charging rule corresponding to the rate group.
  • the content logic unit 513 may include user equipment content source data stream parsing, content data level QoS control, and the so-called content may refer to specific services such as video, web browsing, downloading, or Voice over Internet Protocol (VoIP).
  • the so-called content source may refer to the application layer data service content information, such as a URL, etc., and the content logic unit 513 may determine a rate group corresponding to the corresponding service data according to the different content information, according to the rate group corresponding to the rate group. Billing rules are charged.
  • the template of the logical unit (the logical unit may refer to the session logic unit, the interface logic unit, the billing logic unit, etc.) described in the embodiments of the present invention may be specifically a class in the object-oriented technology (may include a session) Classes, hosting classes, business flow classes, and content classes).
  • the logical unit may be specifically an object instance instantiated by the class (the object instance may be simply referred to as "object” or simply "instance”), that is, the corresponding session logic unit, billing logic unit, and the like.
  • Object instances can be loaded or installed on the gateway user plane device.
  • Gateway user plane devices need to allocate resources for these object instances before loading or installing object instances, for example, allocating memory, CPU processes or threads for object instances, and optionally assigning network ports and network bandwidth. Or assign virtual machines, etc. in the virtualization system to the object instance.
  • the gateway control plane device may request the gateway user plane device to create an object instance of the session, bearer, service flow, and content, that is, the gateway control plane device may request the gateway user plane device to create a session logic unit, a bearer logic unit, Business flow logic unit and content logic unit.
  • the request message of the gateway control plane device includes object instance information, and the object instance information is similar to the foregoing logical unit description information, and includes an operation set of the object instance and attribute information of the object instance.
  • the rate group information is included in the attribute information of the object instance and can be dynamically modified by the gateway control plane device.
  • the ID of the object instance can be assigned by the gateway control plane device or by the gateway user plane device. If the object instance ID is allocated by the gateway user plane device, the gateway user plane device needs to modify the user data matching object instance ID information in the filled object instance when generating the object instance.
  • the embodiment of the present invention may specifically include the following steps:
  • the interface logic unit receives the packet data of the number of users, the packet data is from a network device that provides services for the user equipment, where the network device may be an eNB, an Internet server, an S-GW, a P-GW, an ePDG, an HSGW, and many more.
  • the network device may be an eNB, an Internet server, an S-GW, a P-GW, an ePDG, an HSGW, and many more.
  • the interface logic unit determines, according to the service data information of the packet data, a session logic unit corresponding to the packet data, where the interface logic unit sends the packet data to the corresponding session logic unit.
  • the interface logic unit of the gateway user plane may determine the corresponding session logic unit based on one or more packet data information such as the source of the packet data, the destination IP address, the GTP tunnel information, the IP tunnel information, and the like, and the packet data information may be parsed. Packet data is obtained.
  • the IP tunnel information may include one or more of GRE, IPSec, L2TP, VLAN, VxLAN, and MIP.
  • the mapping relationship between the packet data information and the session logical unit may be configured based on configuration information sent by the gateway control plane device.
  • the session logic unit parses the packet data to obtain service data information, where the service data information may include bearer information, service flow information or content information; and determining a target rate group according to the service data information.
  • the service data information may include bearer information, service flow information or content information; and determining a target rate group according to the service data information.
  • the correspondence between the rate group identifier of the session logic unit and the service data information may be configured according to the configuration information sent by the gateway control plane device.
  • the session logic unit determines, according to the target rate group identifier, a corresponding charging logic unit.
  • the voice logic unit sends the target rate group identifier and the packet data to the billing logic unit corresponding to the target rate group identifier.
  • the session logic unit may determine, according to configuration information sent by the gateway control plane device, a mapping relationship between the service data information and the rate group identifier, and a mapping relationship between the service data information and the charging logic unit, or a rate group identifier and charging logic unit. Mapping relationship.
  • the charging logic unit performs charging processing on the packet data according to the charging rule corresponding to the target rate group identifier.
  • the charging logic unit performs charging measurement according to the charging rule corresponding to the target rate group identifier and the packet data, and obtains charging measurement information, and the charging logic unit may send the charging measurement information to the gateway control plane device through the interface logic unit.
  • the charging logic unit identifier may also be sent together, for example, the logical unit ID, the service flow logical unit ID, or the content logical unit ID, and The corresponding charging measurement information is sent to the gateway control plane device through the interface logic unit.
  • the embodiments of the present invention can implement the charging of services of different granularities through different charging logic units, and achieve the purpose of flexible charging when the control plane and the user plane are separated.
  • the embodiment of the present invention is only an interface logic unit, a session logic unit, and a billing logic unit, and the present invention is not limited thereto.
  • Other logical unit structures capable of implementing the foregoing method should also be within the scope of protection of the present invention.
  • the embodiment of the present invention may further advance before step S650, including the following optional steps:
  • the gateway user plane device receives a configuration message sent by the gateway control plane, where the configuration information carries the accounting report information.
  • the gateway control plane device calculates a threshold value such as the duration, the traffic, or the number of times of the next reporting based on the charging rule and the charging balance information.
  • the gateway control plane device sends configuration information to the gateway user plane device, where the configuration information is used for configuration.
  • the billing logic unit may include the billing report information, for example, threshold information such as the duration, the flow rate, or the number of times the billing information is reported next time.
  • the gateway user plane device configures the charging logic unit according to the charging report information carried in the configuration message.
  • the gateway user plane device modifies the charging report information of the bearer logic unit, the service flow logic unit, or the content logic unit according to the configuration information.
  • the gateway user plane device returns a modify charging logic unit response message to the gateway control plane device.
  • steps S660 and S670 may also be performed after step S650.
  • the gateway control plane device can configure the gateway user plane device according to the requirements of the embodiment of the present invention, so that the gateway user plane device can flexibly measure and report the user service data.
  • the session user plane device may not be configured with a session logic unit or a billing logic unit, or the existing session logic unit or billing logic unit does not support the existing service well.
  • the gateway user plane device needs to be configured or added to configure a new session logic unit or a billing logic unit, the specific execution process may be as shown in FIG. 7.
  • the gateway user plane device receives a request message sent by the gateway user plane device, where the request message carries packet data information and rate group information, where the request message is used to indicate that the session logic unit is established according to the packet data information and the rate group information. Establish a charging logic unit, or modify the session logic unit, establish a charging logic unit, or modify the session logic unit to modify the charging logic unit.
  • the gateway device control plane device After the gateway control plane device receives the creation session request sent by the other network device, the gateway device control plane device sends a request message to the gateway user plane device, requests to establish a session logic unit, and establishes a charging logic unit. For example, when a new user equipment accesses a network device, the network device sends a create session request to the gateway control plane device, where the create session request may carry service data information or an identifier of the user equipment, etc., and the gateway user plane device is established. a logical unit that establishes a charging logic unit; when a new service needs to be provided for the user equipment, the modification session request may be sent. The user plane device modifies the session logic unit to establish a billing logic unit; when the configuration of the current service needs to be changed, the modify session request may be sent, the gateway user plane device modifies the session logic unit, and the billing logic unit is modified.
  • the gateway control plane device may generate rate group information and service data information based on charging rules and session information (eg, APN, etc., user terminal IP address information), bearer information, or content information, and carry the service data information and A request for rate group information is sent to the gateway user plane device.
  • the gateway control plane device can obtain the locally configured charging rule and/or the charging rule generated by the PCRF.
  • the rate group identification corresponding rate group information may be pre-configured on the interface management unit of the gateway user plane device. If there is only the rate group identifier in the message sent by the gateway control plane device, the gateway user plane device may determine other rate group information preconfigured locally according to the rate group identification information.
  • the rate group information may include a rate group identifier, a charging rule, and the like.
  • the gateway user plane device establishes a session logic unit according to the service data information and the rate group information, establishes a charging logic unit, or modifies the session logic unit, establishes a charging logic unit, or modifies the session logic unit, and modifies the charging logic. unit.
  • the rate group identifier and the service data information may be configured in the session logic unit, and the rate group identifier and the charging rule are configured in the billing logic unit.
  • the modifying the session logic unit may refer to adding a mapping entry of the service data information and the charging logic unit under the session logic unit.
  • the modify billing logic unit may be a mapping entry that is added under the billing logic unit, and the billing rule and the rate group identifier.
  • the gateway user plane device may return a setup success response message to the gateway control plane device. After receiving the response message, the gateway control plane can return a create session response to other network devices.
  • the present invention will be further described below in conjunction with a bearer logic unit, a service flow logic unit, and a content logic unit, respectively.
  • a bearer logic unit a service flow logic unit
  • a content logic unit a content logic unit
  • the following scheme is only to carry logical units, business flow
  • the logic unit, the content logic unit is used as an example for the modification and creation of the session logic unit and the billing logic unit.
  • Other implementation details may be understood by reference to the foregoing embodiments, and are not intended to limit the embodiments of the present invention.
  • FIG. 8 is a signaling interaction diagram of a bearer logic unit in an embodiment of the present invention. As shown in Figure 8:
  • the gateway control plane device receives a create session request sent by another network device.
  • the other network devices herein may be an MME, an SGW, or the like.
  • the MME or the SGW When a new user equipment accesses the network, or the user equipment re-accesses the network, the MME or the SGW establishes a connection with the user equipment, for example, a GTP tunnel of the network device and the user equipment is established, or may be transmitted for the user equipment. data.
  • the MME or the SGW may send a create session request to the gateway control plane device, so that the gateway control plane device instructs the gateway user plane device to perform charging control on the data transmission of the user equipment.
  • the creation session request may carry bearer information, for example, GTP tunnel information or content information, and the like.
  • the gateway control plane device sends a request message to the gateway user plane device, where the request message carries bearer information and rate group information, where the request message is used to instruct the gateway user plane device to establish a session logic unit according to the bearer information and the rate group information. And carrying logical units.
  • the gateway user plane device After receiving the request message sent by the user plane device, the gateway user plane device establishes a session logic unit and a bearer logic unit according to the bearer information and the rate group information carried in the request.
  • the gateway user plane device returns a response message to the gateway control plane device, where the response message may indicate that the gateway control plane device session logic unit and the charging logic unit have been established.
  • the gateway control plane device After receiving the response message sent by the gateway user plane device, the gateway control plane device returns a session creation response message to the other network device.
  • the gateway user plane device After receiving the packet data sent by the network device serving the user equipment by the interface logic unit, the gateway user plane device sends the packet data to the session logic unit corresponding to the user equipment.
  • the step S606 is similar to the foregoing step S420, and can be understood by mutual reference.
  • the session logic unit of the gateway user plane device receives the packet sent by the interface logic unit. After the data is parsed, the packet data is parsed to obtain bearer information, and the target rate group identifier is determined according to the bearer information.
  • the step S607 is similar to the foregoing step S430, and can be understood by mutual reference.
  • the session logic unit of the gateway user plane device determines a corresponding bearer logic unit according to the target rate group identifier, and sends the packet data and the target rate group identifier to the corresponding bearer logic unit.
  • the step S808 is similar to the foregoing step S640, and can be understood by mutual reference.
  • the bearer logic unit corresponding to the packet data of the gateway user plane device After receiving the packet data and the target rate group identifier, the bearer logic unit corresponding to the packet data of the gateway user plane device performs charging measurement according to the target tariff group identifier and the charging measurement of the packet data, to obtain the charging measurement. result.
  • the gateway user plane device sends the charging measurement result to the gateway control plane device.
  • steps S609 and S610 are similar to the foregoing step S450, and can be understood by mutual reference.
  • FIG. 9 is a signaling interaction diagram of a service flow logic unit in an embodiment of the present invention. As shown in Figure 9.
  • the gateway control plane device receives a re-authorization request message sent by another network device, where the re-authorization request message is used to request to add a service flow and a charging rule corresponding to the service flow.
  • other network devices here may be PCRF and the like.
  • the PCRF may send a re-authorization request to the gateway control plane device.
  • the gateway control plane device sends a request message to the gateway user plane device, where the request message carries the service flow information and the rate group information, where the request message is used to instruct the gateway user plane device to modify the session according to the service flow information and the rate group information.
  • the logical unit or bearer logic unit establishes a bearer logic unit or a service flow logic unit.
  • the request message may be used to indicate the session logic unit corresponding to the modified service flow information and the bearer logic unit.
  • the request message may be The session logic unit corresponding to the modified service flow information is used to establish a bearer logic unit corresponding to the service flow information.
  • the service flow logic unit performs charging.
  • the request message may be used to indicate the session logic unit corresponding to the modified service flow information, and the service flow logic unit corresponding to the service flow information is established.
  • the gateway user plane device After receiving the request message sent by the user plane device, the gateway user plane device modifies the session logic unit and the bearer logic unit according to the service flow information and the rate group information carried in the request, or modify the session logic unit to establish a bearer logic unit. Or modify the session logic unit to establish a business flow logic unit.
  • the gateway user plane device returns a response message to the gateway control plane device, where the response message may indicate that the gateway control plane device session logic unit and the charging logic unit have been established or modified.
  • the gateway control plane device After receiving the response message sent by the gateway user plane device, the gateway control plane device returns a session creation response message to the other network device.
  • the gateway user plane device After receiving the packet data that is sent by the network device serving the user equipment by the interface logic unit, the gateway user plane device sends the packet data to the session logic unit corresponding to the user equipment.
  • the step S906 is similar to the foregoing step S620, and can be understood by mutual reference.
  • the session logic unit of the gateway user plane device After receiving the packet data sent by the interface logic unit, the session logic unit of the gateway user plane device parses the packet data to obtain service flow information, and determines a target rate group identifier according to the service flow information.
  • the step S907 is similar to the foregoing step S630, and can be understood by mutual reference.
  • the session logic unit of the gateway user plane device determines a corresponding charging logic unit (a bearer logic unit or a service flow logic unit) according to the parsed service flow information, and sends the packet data and the target rate group identifier to the corresponding Billing logic unit.
  • a charging logic unit a bearer logic unit or a service flow logic unit
  • the step S908 is similar to the foregoing step S640, and can be understood by mutual reference.
  • the charging logic unit corresponding to the packet data of the gateway user plane device receives the packet data. And the target rate group identification, the charging measurement is performed on the packet data according to the charging rule corresponding to the target rate group identifier, and the charging measurement result is obtained.
  • the gateway user plane device sends the charging measurement result to the gateway control plane device.
  • Steps S909 and S910 are similar to the foregoing step S650, and can be understood by mutual reference.
  • FIG. 10 is a signaling interaction diagram taking a content logical unit as an example in the embodiment of the present invention. As shown in Figure 10.
  • the session logic unit of the gateway user plane device receives packet data sent by the user equipment, where the packet data carries new content information (for example, a URL) of the acquisition request, for example, a hypertext transfer protocol sent by the user equipment (HyperText Transfer Protocol) , HTTP) Get (get) the message.
  • the gateway user plane device sends the new content information to the gateway control plane device, and requests to increase the rate group information corresponding to the content information and the charging rule.
  • the gateway control plane device After receiving the content information, the gateway control plane device sends a request message to the gateway user plane device, where the request message carries content information and rate group information, where the request message is used to indicate that the gateway user plane device is based on the content information and the fee.
  • Rate group information modify the session logic unit and the bearer logic unit, or modify the session logic unit and the service flow logic unit, or modify the session logic unit and establish the bearer logic unit, or modify the session logic unit and establish a service flow logic unit, or modify the session logic Unit and establish a content logic unit.
  • the content information has a corresponding relationship with the service flow information and the bearer information, the service flow information, the bearer information, and the like can be further determined through the content information.
  • the indication message is used to instruct the gateway user plane device to modify the session logic unit according to the content information and the rate group information, and establish a content logic unit;
  • the indication message is used to instruct the gateway user plane device to modify the session logic unit according to the content information and the rate group information and establish a service flow logic unit, or modify the session logic.
  • the request message is used when the service of the user equipment needs to be charged by the bearer logic unit. Instructing the gateway user plane device to modify the session logic unit and establish the bearer logic unit based on the content information and the rate group information, or modify the session logic unit and modify the bearer logic unit;
  • the gateway user plane device modifies the session logic unit and the bearer logic unit according to the packet data information and the rate group information carried in the request message, or modifies the session logic unit and the service flow logic. Unit, either modify the session logic unit and establish a bearer logic unit, or modify the session logic unit and establish a traffic flow logic unit, or modify the session logic unit and establish a content logic unit.
  • the gateway user plane device returns a response message to the gateway control plane device, where the response message may indicate that the gateway control plane device session logic unit and the charging logic unit have been established or modified.
  • the gateway user plane device After receiving the packet data sent by the network device serving the user equipment by the interface logic unit, the gateway user plane device sends the packet data to the session logic unit corresponding to the user equipment.
  • Step S1005 is similar to the foregoing step S620, and can be understood by mutual reference.
  • the session logic unit of the gateway user plane device After receiving the packet data sent by the interface logic unit, the session logic unit of the gateway user plane device parses the packet data to obtain content information, and determines a target rate group identifier according to the content information.
  • Step S1006 is similar to the foregoing step S630, and can be understood by mutual reference.
  • the session logic unit of the gateway user plane device determines a corresponding charging logic unit (a bearer logic unit, a service flow logic unit, or a content logic unit) according to the parsed content information, and sends the packet data and the target rate group identifier. Give the corresponding billing logic unit.
  • a charging logic unit a bearer logic unit, a service flow logic unit, or a content logic unit
  • Step S1007 is similar to the foregoing step S640, and can be understood by mutual reference.
  • the charging logic unit corresponding to the packet data After receiving the packet data and the target rate group identifier, the charging logic unit corresponding to the packet data performs charging measurement on the packet data according to the charging rule corresponding to the target rate group identifier, to obtain a charging measurement result.
  • the gateway user plane device sends the charging measurement result to the gateway control plane device.
  • Steps S1008 and S1009 are similar to the foregoing step S650, and can be understood by mutual reference.
  • FIG. 11 is a schematic diagram of a virtual structure of another communication charging apparatus according to an embodiment of the present invention.
  • the device is used to implement the method embodiment corresponding to the gateway user plane device described in FIG. 3 to FIG. 4, and can be understood by mutual reference.
  • the device may specifically include:
  • a determining unit 1101 configured to determine a first mapping relationship between the service data information and the charging rule
  • the receiving unit 1102 is configured to receive packet data from a network device that provides a service for the user equipment;
  • the processing unit 1103 is configured to parse the packet data to obtain first service data information, and determine a first charging rule according to the first service data information and the first mapping relationship, where the first mapping The relationship includes a second mapping relationship between the first service data information and the first charging rule;
  • the charging unit 1104 is configured to perform charging processing on the packet data according to the first charging rule.
  • the service data information includes one or more of the following:
  • Bearer information business flow information, content information.
  • the receiving unit 1102 is further configured to: receive configuration information sent by the gateway control plane device, where the configuration information includes the first mapping relationship.
  • the first mapping relationship includes:
  • processing unit 1103 is further configured to:
  • the receiving unit 1102 is further configured to receive the request sent by the gateway control plane device. And requesting, the request message carries a third mapping relationship between the second service data information and the second charging rule;
  • the processing unit 1103 is further configured to: when the service data information includes the second service data information, modify a mapping relationship of the second mapping data information in the first mapping relationship to the first Three mapping relationship;
  • the processing unit 1103 is further configured to: when the service data information does not include the second service data information, add the third mapping relationship in the first mapping relationship.
  • FIG. 12 is a schematic diagram of a virtual structure of another communication charging apparatus according to an embodiment of the present invention.
  • the device is used to implement the method embodiment corresponding to the gateway control plane device described in FIG. 3 to FIG. 4, and can be understood by mutual reference.
  • the device may specifically include:
  • a determining unit 1201 configured to determine a first mapping relationship between the service data information and the charging rule
  • the sending unit 1202 is configured to send configuration information to the gateway user plane device, where the configuration information includes the first mapping relationship, where the mapping relationship is used for determining a charging rule.
  • the receiving unit 1203 is configured to receive a fourth mapping relationship between the service identifier sent by the policy and charging rule function unit and the charging rule, where the service identifier corresponds to the service data information;
  • the determining unit 1201 is further configured to: determine the service data information corresponding to the service identifier, and determine the first mapping relationship according to the fourth mapping relationship.
  • the determining unit 1201 is further configured to: predefined a first mapping relationship between the service data information and the charging rule.
  • the determining unit 1201 is further configured to divide the rate group according to the service data information, where each rate group corresponds to a rate group identifier, and all service data information mappings in the same rate group are the same. Billing rules.
  • FIG. 13 is a schematic structural diagram of a gateway user plane device entity according to an embodiment of the present invention.
  • the gateway user plane device may specifically include: a communication unit 1301, where The processor 1302 is a memory 1303. Individual modules can be connected via a bus.
  • the communication unit 1301 is configured to support the transmission and reception of information between the gateway user plane device and the gateway control plane device and other network devices in the foregoing embodiment.
  • the communication unit 1301 may be an interface circuit, and may support the gateway user plane device and the gateway control. Optical communication between surface devices and other network devices.
  • the packet data and signaling messages are processed by the processor 1302 and sent by the communication unit 1301 to the gateway control plane device or other network device.
  • the signals from the gateway control plane device and other network devices are received by the communication unit 1301 and coordinated, and further processed by the processor 1302 to obtain packet data and signaling information transmitted or forwarded by the gateway control plane device and other network devices.
  • Processor 1302 also performs the processes involved in the gateway user plane device and/or other processes for the techniques described herein in Figures 3-4 and 6-10.
  • the memory 1303 is used to store program codes and data of the access network device.
  • FIG. 14 is a schematic structural diagram of a gateway control plane device according to an embodiment of the present invention.
  • the gateway control plane device may specifically include: a communication unit 1401, a processor 1402, and a memory 1403. Individual modules can be connected via a bus.
  • the communication unit 1401 is configured to support the gateway control plane device to send and receive information between the gateway user plane device and other network devices in the foregoing embodiment.
  • the communication unit 1401 may be an interface circuit, and may support the gateway control plane device and the gateway user.
  • the packet data and signaling messages are processed by the processor 1402 and sent by the communication unit 1401 to the gateway user plane device or other network device.
  • the signals from the gateway user plane device and other network devices are received and coordinated by the communication unit 1401, and further processed by the processor 1402 to obtain packet data and signaling information transmitted or forwarded by the gateway user plane device and other network devices.
  • Processor 1402 also performs the processes involved in the gateway user plane device and/or other processes for the techniques described herein in Figures 3-4 and 6-10.
  • the memory 1403 is used to store program codes and data of the access network device.
  • the processor of the gateway user plane device or the gateway control plane device in the foregoing embodiment may be a processor or a collective name of multiple processing elements.
  • the processor may be a Central Processing Unit (CPU), an Application Specific Integrated Circuit (ASIC), or one or more integrated circuits configured to implement the embodiments of the present invention.
  • CPU Central Processing Unit
  • ASIC Application Specific Integrated Circuit
  • DSPs digital singal processors
  • FPGAs Field Programmable Gate Arrays
  • the memory of the gateway user plane device or the gateway control plane device in the foregoing embodiment may be a storage device, or may be a collective name of multiple storage elements, and used to store executable program code or parameters required for the operation of the access network management device. , data, etc.
  • the memory 903 may include random access memory (RAM), and may also include non-volatile memory such as a magnetic disk memory, a flash memory, or the like.
  • the bus of the gateway user plane device or the gateway control plane device in the above embodiment may be an Industry Standard Architecture (ISA) bus, a Peripheral Component (PCI) bus or an extended industry standard architecture (Extended Industry Standard Architecture, EISA) bus, etc.
  • ISA Industry Standard Architecture
  • PCI Peripheral Component
  • EISA Extended Industry Standard Architecture
  • the bus can be divided into an address bus, a data bus, a control bus, and the like.
  • the embodiment of the invention further provides a charging system, which comprises the gateway user plane device and the gateway control plane device of the above embodiment.
  • the steps of a method or algorithm described in connection with the embodiments disclosed herein can be implemented in hardware, a software module executed by a processor, or a combination of both.
  • the software module can be placed in random access memory (RAM), memory, read only memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disk, removable disk, CD-ROM, or technical field. Any other form of storage medium known.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

本发明实施例涉及一种通信计费方法及装置。包括，网关用户面设备确定一个或多个业务数据信息与一个或多个计费规则的映射关系。网关用户面设备从为用户设备提供服务的网络设备接收分组数据，解析该分组数据得到业务数据信息，根据该业务数据信息确定计费规则。网关用户面设备根据相应的计费规则对分组数据进行计费处理。通过本发明实施例，将业务数据信息与计费规则对应，在具体计费时，可以依据不同粒度的业务数据信息对业务进行区分，并分别进行计费处理，实现了更灵活、更合理、更精确的计费，提高了用户体验。

Description

一种通信计费方法 技术领域
本发明涉及通信计费技术领域，尤其涉及一种通信计费方法及装置。
背景技术
目前第三代伙伴计划(The 3rd Generation Partnership Project,3GPP)系统中，一般通过网关控制面设备Gateway Control Plane,GW-C)和网关用户面设备(Gateway User Plane，GW-U)来完成对用户使用网络资源的计费。其中，GW-C主要完成用户接入、策略控制和计费话单管理。GW-U主要负责对数据进行转发，并执行控制面下发的控制和计费策略。
在处理控制与转发分离的网关计费时，采用GW-C和GW-U预先配置计费控制策略。当用户接入建立承载时，GW-C为用户的承载分配上下文，记录用户使用承载的状态计费信息，向GW-U下发计费控制信息。GW-U基于接收GW-C发送的计费控制信息进行计费，将得到的计费信息上报给GW-C，GW-C据此生成话单。
现有技术主要处理控制与转发分离的架构下的承载级别的计费，不够灵活，也不够合理。
发明内容
本发明实施例提供了一种通信计费方法及装置。通过本发明实施例可以实现更灵活合理的对用户请求的业务进行计费，提高了用户体验。
第一方面，本发明实施例提供了一种通信计费方法。包括，网关用户面设备确定业务数据信息与计费规则的第一映射关系。网关用户面设备从为用 户设备提供服务的网络设备接收分组数据，解析该分组数据得到第一业务数据信息，并根据该第一业务数据信息和第一映射关系确定第一计费规则，其中，第一映射关系包括所述第一业务数据信息与第一计费规则的第二映射关系。网关用户面设备根据第一计费规则对分组数据进行计费处理。另外，同一计费规则可以映射一个或多个业务数据信息，且该一个或多个业务数据信息所对应的业务需要通过相同的计费规则进行计费的。通过本发明实施例，将业务数据信息与计费规则对应，在具体计费时，可以依据不同粒度的业务数据信息对业务进行区分，并分别进行计费处理，实现了更灵活、更合理、更精确的计费，提高了用户体验。
在一种可能的实现方式中，前述业务数据信息包括以下一项或多项：承载信息，业务流信息，内容信息。其中，承载信息，业务流信息以及内容信息等可以分别包括一个或多个具体信息。通过本发明实施例可以实现根据承载信息、业务流信息、内容信息等等业务数据信息对应计费规则，在计费时也是根据承载信息、业务流信息、内容信息等等业务数据信息确定计费规则，并进行计费，实现了更灵活、更合理、更精确的计费，提高了用户体验。
在另一种可能的实现方式中，在网关用户面设备确定业务数据信息与计费规则的第一映射关系之前，还包括：网关用户面设备接收网关控制面设备发送的配置信息，该配置信息包括第一映射关系。通过本发明实施例可以实现，由网关控制面设备统一配置业务数据信息与计费规则的映射关系，方便管理，使得计费更合理，提高了用户体验。
在又一种可能的实现方式中，业务数据信息与计费规则的第一映射关系包括：业务数据信息与费率组标识的第一子映射关系，以及费率组标识与计费规则的第二子映射关系。通过本发明实施例可以实现，通过划分费率组的方式来确定映射关系，并由费率组标识进行关联，使得该计费方法更容易实现，更灵活，提高了用户体验。
在再一种可能的实现方式中，上述根据第一业务数据信息确定第一计费 规则包括：网关用户面设备根据第一业务数据信息以及业务数据信息与费率组标识的第一子映射关系，确定所述第一费率组标识，其中，第一子映射关系包括第一业务数据信息与第一费率组标识的映射关系。网关用户面设备根据第一费率组标识以及费率组标识与计费规则的第二子映射关系，确定第一计费规则，其中，第二子映射关系包括第一费率组标识与第一计费规则的映射关系。通过本发明实施例可以实现，通过费率组标识确定计费规则，使得该计费方法更容易实现，更灵活，提高了用户体验。
在再一种可能的实现方式中，还包括：网关用户面设备接收网关控制面设备发送的请求消息，该请求消息携带有第二业务数据信息与第二计费规则的第三映射关系。当前述业务数据信息包含第二业务数据信息时，网关用户面设备将所述业务数据信息与所述计费规则的第一映射关系中关于所述第二业务数据信息的映射关系，修改为第三映射关系；当业务数据信息不包含第二业务数据信息时，网关用户面设备在所述业务数据信息与所述计费规则的第一映射关系中增加第三映射关系。通过本发明实施例可以实现，增加或修改业务数据信息与计费规则的映射关系，从而使得计费更灵活，更合理，提高了用户体验。
第二方面，本发明实施例提供了一种通信计费方法。包括，网关控制面设备确定业务数据信息与计费规则的第一映射关系；该网关控制面设备向网关用户面设备发送配置信息，该配置信息包括业务数据信息与计费规则的第一映射关系，该映射关系用于计费规则的确定。通过本发明实施例可以实现，由网关控制面设备统一配置业务数据信息与计费规则的映射关系，方便管理，使得计费更合理，提高了用户体验。
在一种可能的实现方式中，上述网关控制面设备确定业务数据信息与计费规则的第一映射关系包括：网关用户面设备接收策略与计费规则功能单元发送的业务标识与计费规则的第四映射关系，其中，上述业务标识中的任意一个对应有业务数据信息。网关用户面设备确定业务标识对应的业务数据信 息，根据第四映射关系，确定第一映射关系。通过本发明实施例可以实现，网关控制面设备通过策略与计费规则功能单元确定业务数据信息与计费规则的映射关系，再进行统一配置，方便管理，使得计费更合理，提高了用户体验。
在另一种可能的实现方式中，上述网关控制面设备确定业务数据信息与计费规则的第一映射关系包括：网关控制面设备预定义业务数据信息与计费规则的第一映射关系。通过本发明实施例可以实现，网关控制面设备通过预定义业务数据信息与计费规则的映射关系，再进行统一配置，方便管理，使得计费更合理，提高了用户体验。
在再一种可能的实现方式中，网关控制面设备确定业务数据信息与计费规则的第一映射关系包括：网关控制面设备根据业务数据信息划分费率组，每一个费率组对应有一个费率组标识，划分在同一个费率组中的全部业务数据信息映射相同的计费规则。通过本发明实施例可以实现，通过划分费率组的方式来确定映射关系，并由费率组标识进行关联，使得该计费方法更容易实现，更灵活，提高了用户体验。
第三方面，本发明实施例提供了一种通信计费装置。包括：接口逻辑单元，每个接口逻辑单元对应一个或多个会话逻辑单元，每个会话逻辑单元对应一个或多个计费逻辑单元：接口逻辑单元，用于确定业务数据信息与计费规则的第一映射关系，根据业务数据信息与计费规则的第一映射关系，配置会话逻辑单元以及计费逻辑单元；接口逻辑单元还用于，从为用户设备提供服务的网络设备接收分组数据，对所述分组数据进行解析，确定分组数据对应的会话逻辑单元，将所述分组数据发送给所述分组数据对应的会话逻辑单元；所述会话逻辑单元，用于接收所述接口逻辑单元发送的所述分组数据，解析分组数据得到第一业务数据信息，根据第一业务数据信息和第一映射关系确定第一计费规则确定所第一业务数据信息对应的计费逻辑单元，将分组数据发送给计费逻辑单元其中，第一映射关系包括第一业务数据信息与第一 计费规则的第二映射关系；计费逻辑单元，用于接收会话逻辑单元发送的第一计费规则，根据第一计费规则对分组数据进行计费处理，其中，业务数据信息包含第一业务数据信息。
在一种可能的实现方式中，所述业务数据信息包括以下一项或多项：承载信息，业务流信息，内容信息。
在另一种可能的实现方式中，接口逻辑单元还用于，接收网关控制面设备发送的配置信息，配置信息包括业务数据信息与计费规则的第一映射关系。
在又一种可能的实现方式中，业务数据信息与计费规则的第一映射关系包括，业务数据信息与费率组标识的第一子映射关系，以及费率组标识与计费规则的第二子映射关系。根据业务数据信息与计费规则的第一映射关系，配置会话逻辑单元以及计费逻辑单元包括：根据费率组标识与计费规则的第一子映射关系配置计费逻辑单元，根据业务数据信息与费率组标识的第二子映射关系配置所述会话逻辑单元。
在再一种可能的实现方式中，所述会话逻辑单元还用于，根据第一业务数据信息以及第一子映射关系，确定第一费率组标识，其中，第一子映射关系包括第一业务数据信息与第一费率组标识的映射关系，将第一费率组标识以及分组数据发送给第一费率组标识对应的计费逻辑单元，其中，费率组标识包括第一费率组标识；计费逻辑单元还用于，根据第一费率组标识以及第二子映射关系，确定第一计费规则，其中，第二子映射关系包括第一费率组标识与第一计费规则的映射关系。
在再一种可能的实现方式中，还包括：接口逻辑单元，用于接收网关控制面设备发送的请求消息，所述请求消息携带有第二业务数据信息与第二计费规则的第三映射关系；当业务数据信息包含第二业务数据信息时，所述接口逻辑单元根据所述第二业务数据信息与所述第二计费规则的映射关系，修改所述第二业务数据信息对应的会话逻辑单元，创建所述第二业务数据信息对应的计费逻辑单元；当业务数据信息不包含所述第二业务数据信息时，所 述接口逻辑单元根据所述第二业务数据信息与所述第二计费规则的映射关系，创建所述第二业务数据信息对应的会话逻辑单元以及计费逻辑单元。
第四方面，本发明实施例提供了一种通信计费装置，其特征在于，包括：确定单元，用于确定业务数据信息与计费规则的第一映射关系；接收单元，用于从为用户设备提供服务的网络设备接收分组数据；处理单元，用于解析所述分组数据，以得到第一业务数据信息，并根据第一业务数据信息和第一映射关系确定第一计费规则，其中，第一映射关系包括第一业务数据信息与第一计费规则的第二映射关系；计费单元，用于根据第一计费规则对分组数据进行计费处理。
在一种可能的实现方式中，所述业务数据信息包括以下一项或多项：承载信息，业务流信息，内容信息。
在另一种可能的实现方式中，所述接收单元还用于，接收所述网关控制面设备发送的配置信息，所述配置信息包括所述业务数据信息与所述计费规则的第一映射关系。
在又一种可能的实现方式中，所述业务数据信息与所述计费规则的第一映射关系包括：所述业务数据信息与费率组标识的第一子映射关系，以及所述费率组标识与所述计费规则的第二子映射关系。
在再一种可能的实现方式中，所述处理单元还用于，根据第一业务数据信息以及第一子映射关系，确定第一费率组标识，其中，第一子映射关系包括第一业务数据信息与第一费率组标识的映射关系；根据第一费率组标识以及所述第二子映射关系，确定第一计费规则，其中，第二子映射关系包括第一费率组标识与第一计费规则的映射关系。
在再一种可能的实现方式中，接收单元还用于，接收所述网关控制面设备发送的请求消息，该请求消息携带有第二业务数据信息与第二计费规则的第三映射关系；处理单元还用于，当所述业务数据信息包含所述第二业务数据信息时，将第一映射关系中关于第二业务数据信息的映射关系，修改为第 三映射关系；处理单元还用于，当所述业务数据信息不包含所述第二业务数据信息时，在第一映射关系中增加第三映射关系。
第五方面，本发明实施例提供了一种通信计费装置，其特征在于，包括：确定单元，用于确定业务数据信息与计费规则的第一映射关系；发送单元，用于向所述网关用户面设备发送配置信息，所述配置信息包括业务数据信息与计费规则的第一映射关系。
在一种可能的实现方式中，还包括接收单元，用于接收策略与计费规则功能单元发送的业务标识与所述计费规则的第四映射关系，其中，所述业务标识对应有业务数据信息；确定单元还用于，根据业务标识与计费规则的第四映射关系，确定业务数据信息与计费规则的第一映射关系。
在另一种可能的实现方式中，确定单元还用于，预定义业务数据信息与计费规则的第一映射关系。
在再一种可能的实现方式中，确定单元还用于，根据业务数据信息划分费率组，每一个费率组对应有一个费率组标识，划分在同一个费率组中的全部业务数据信息映射相同的计费规则。
第六方面，本发明实施例提供了一种网关用户面设备，该网关用户面设备具有实现上述方法实际中网关用户面设备行为的功能。该功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块。
在一个可能的设计中，网关用户面设备包括处理器和通信单元，其中，处理器被配置为支持网关用户面设备执行上述方法中相应的功能。通信单元用于支持网关用户面设备与网关控制面设备以及其他网络设备之间的通信，向网关控制面设备以及其他网络设备发送上述方法中所涉及的信息或者指令。该网关用户面设备还可以包括存储器，该存储器用于与处理器耦合，其保存网关用户面设备必要的程序指令和数据。
第七方面，本发明实施例提供了一种网关控制面设备。且该网关控制面 设备具有实现上述方法实际中网关控制面设备行为的功能。该功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块。
在一个可能的设计中，网关控制面设备包括处理器和通信单元。处理器被配置为支持网关控制面设备执行上述方法中相应的功能。通信单元用于支持网关控制面设备与网关用户面设备以及其他网络设备之间的通信，向网关用户面设备以及其他网络设备发送上述方法中所涉及的信息或者指令。该网关控制面设备还可以包括存储器，该存储器用于与处理器耦合，其保存网关控制面设备必要的程序指令和数据。
第八方面，本发明实施例提供了一种通信计费系统，该系统包括上述方面的网关控制面设备与网关用户面设备。
第九方面，本发明实施例提供了一种计算机存储介质，用于储存为上述网关用户面设备所用的计算机软件指令，其包含用于执行上述方面所设计的程序。
第十方面，本发明实施例提供了一种计算机存储介质，用于储存为上述网关控制面设备所用的计算机软件指令，其包含用于执行上述方面所设计的程序。
本发明提供的实施例，可以实现核心网设备能够对用户设备使用RRC连接下的密钥进行加密的数据包正确的解密，保证了用户设备的能够正常的通信，提高了用户体验。
通过本发明实施例，可以从不同粒度的业务数据信息划分费率组，以及确定每个费率组对应的计费规则，在进行计费时，根据业务数据信息确定计费规则，根据该计费规则进行计费，实现了更灵活、更合理、更精确的计费，提高了用户体验。
附图说明
图1为一种系统架构示意图；
图2为另一种系统架构示意图；
图3为本发明方法实施例提供的一种通信计费方法通信示意图；
图4为本发明方法实施例提供的另一种通信计费方法通信示意图；
图5为本发明实施例提供的一种网关用户面设备虚拟结构示意图；
图6为本发明方法实施例提供的又一种通信计费方法通信示意图；
图7为本发明方法实施例提供的再一种通信计费方法通信示意图；
图8为本发明方法实施例提供的再一种通信计费方法通信示意图；
图9为本发明方法实施例提供的再一种通信计费方法通信示意图；
图10为本发明方法实施例提供的再一种通信计费方法通信示意图；
图11为本方发明实施例提供的另一种通信计费装置虚拟结构示意图；
图12为本方发明实施例提供的再一种通信计费装置虚拟结构示意图；
图13为本发明实施例提供的一种网关用户面设备实体结构示意图；
图14为本发明实施例提供的一种网关控制面设备实体结构示意图。
具体实施方式
下面通过附图和实施例，对本发明的技术方案做进一步的详细描述。
为使本发明实施例的目的、技术方案和优点更加清楚，下面将结合本发明实施例中的附图，对本发明实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例是本发明一部分实施例，而不是全部的实施例。基于本发明中的实施例，本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例，都属于本发明保护的范围。
在3GPP标准版本8(Release8，R8)阶段，发展出一种全新的演进网络，其系统架构如图1所示，包括：演进的通用陆地无线接入网(Evolved Universal Terrestrial Radio Access Network，E-UTRAN)、移动性管理实 体(Mobility Management Entity，MME)、分组数据网络网关实体(Packet Data Network Gateway，PGW)、服务网关实体(Serving Gateway，SGW)和归属用户服务器(Home Subscriber Server，HSS)、策略与计费规则功能单元(Policy and Charging Rules Function,PCRF)、外部分组数据网络(Packet Data Network，PDN)、鉴权授权和计费(Authentication、Authorization和Accounting，AAA)服务器、动态主机配置协议(Dynamic Host Configuration Protocol，DHCP)服务器、陆地无线接入网(Universal Terrestrial Radio Access Network，UTRAN)、全球移动通讯系统/增强型数据速率演进技术无线接入网(Global System for Mobile Communications Enhanced Data Rate for GSM Evolution Radio Access Network，GERAN)、服务通用分组无线服务技术支持节点(Serving General Packet Radio Service Support Node，SGSN)等等。
其中，E-UTRAN用于实现所有与演进网络无线有关的功能。
MME负责控制面的移动性管理，包括用户上下文和移动状态管理，分配用户临时身份标识(Temporary Mobile Subscriber Identity，TMSI)等。
S-GW是3GPP接入网络间的用户面锚点，终止E-TURAN的接口。
P-GW是3GPP接入网络和非3GPP接入网络之间的用户面锚点，和PDN的接口。
HSS用于存储用户签约信息。
MME、S-GW、P-GW和HSS通常作为核心网设备。
当用户设备通过无线空口接入E-UTRAN后，先附着到MME上，MME从HSS获取用户设备(User Equipment，UE)的签约数据和鉴权信息，发起对UE进行鉴权的过程。MME完成鉴权过程后，由用户设备或者MME发起建立用于传输用户数据的承载的过程。在该过程中，MME通知S-GW为用户建立承载，在通知消息中携带P-GW的地址和用户所在的E-UTRAN网络设备的地址信息。S-GW为用户建立从E-UTRAN到P-GW的用于传输用户数据的承载。P-GW将来自外部 PDN的下行数据通过承载转发给UE，并将来自UE的上行数据转发给相应的PDN。
为了能兼容已有的UTRAN和GERAN的接入网络。UE可以通过UTRAN或者GERAN和SGSN接入MME，并且可以通过UTRAN/GERAN、SGSN建立和S-GW之间的通过通用分组无线业务隧道协议(General Packet Radio Service Tunnelling Protocol,GTP)连接。S-GW将GTP隧道转换为相应的连接P-GW的承载，用于传输用户数据。UTRAN也可以建立直接连接S-GW的GTP隧道。
MME成为只处理控制面信令的网络设备，S-GW和P-GW主要负责转发用户面数据。S-GW和P-GW可以合并为一个网络设备，一般统称为网关。
在演进网络中，网关仍然需要保留有大量的接口信令的处理能力。这些接口信令包括：承载接口信令、策略控制与计费(PCC)接口信令、计费接口信令、合法监听接口信令、外部PDN的接口信令(例如，DHCP、AAA等等)的处理功能。
因为S-GW、P-GW和GGSN在平台架构上基本上是相同的，我们统一称之为网关。将网关的控制面和用户面分离的架构参见图2。
网关用户面可以采用分布式部署。例如，一些GW-U可以部署在传输网络的核心汇聚点作为移动锚点网关用户面，一些GW-U可以部署在传输网络的汇聚点或者集成在基站作为非通讯类业务的本地接入网关用户面。网关控制面设备(GW-C)可以根据不同的业务来对GW-U进行单元功能编排，确定业务数据是否经过锚点。
其中，网关的控制面设备(GW-C)可以称为控制面网关(Control Plane Gateway)，也可以称为网关控制器(Gateway Controller)、控制节点(Control Node)或者控制网关(Control Gateway)。网关的用户面设备(GW-U)可以称为用户面网关(User Plane Gateway)，也可以称为分组数据转发网关(Packet Data Forwarding Gateway)、路由转发节点(Routing Forwarding Node)或者交换节点(Switch Node)。其中，考虑到网关控制面设备和移动 性管理实体(MME/SGSN)都是采用通用计算平台，因此两者可以合一设置。GW-C可以向GW-U发送控制指令以及配置信息等等。GW-U可以对通过的分组数据进行计费处理。
本发明实施例依据不同业务对计费粒度的不同需求，根据不同粒度的业务数据信息，对不同业务所对应的分组数据进行分别进行相应的计费处理，使得对于用户设备的业务进行更合理，更精确，更灵活的计费。提高了用户体验。
为便于对本发明实施例的理解，下面将结合附图以具体实施例做进一步的解释说明，实施例并不构成对本发明实施例的限定。
图3为本发明实施例提供的一种通信计费方法流程图。如图3所示。本发明实施例适用于前述系统架构中。该方法具体可以包括：
S310，网关用户面设备确定业务数据信息与计费规则的第一映射关系。
依据不同业务在计费时对粒度的不同要求，可以通过不同业务对应的不同粒度的业务数据信息预先定义费率组，以及确定每个费率组对应的计费规则。也就是将业务数据信息与计费规则建立第一映射关系。
例如，业务数据信息可以包括承载信息、业务流信息以及内容信息等等中的一个或多个。其中，承载信息、业务流信息以及内容信息属于不同粒度的业务数据信息。在定义费率组时，可以根据承载信息、业务流信息以及内容信息等中的一个或多个预先定义相应的费率组。换句话说，在定义费率组时，可以根据不同的承载信息来划分费率组，对于根据承载信息划分的费率组，费率相同的业务所对应的承载信息可以归为同一费率组，这样每个费率组对应费率相同的一个或多个承载信息。此外，也可以根据业务流信息或者内容信息来划分费率组，根据业务流信息信息划分的费率组，费率相同的一个或多个业务流信息可被归为同一个费率组；而根据内容信息划分的费率组，费率相同的一个或多个内容信息可被归为同一个费率组。
为了应对不同的计费需求，还可以结合承载信息、业务流信息以及内容 信息中的任意两项或两项以上来划分费率组，以提供更精细的费率组定义。
再例如，不同用户设备的视频业务、通话业务以及短信业务等等的业务数据信息是有不同的，或者相同用户设备的不同视频业务、通话业务以及短信业务等等的业务数据信息也是不同的。不同业务对于计费规则、计费粒度等的要求也是不同的，甚至是相同业务对于不同的用户设备的计费规则、计费粒度等的要求也是不同的。
在定义费率组时，可以将用户设备以及其对应的视频业务、通话业务以及短信业务等等对应的业务数据信息划分在不同的费率组内，还可以将视频业务、通话业务以及短信业务等等分别以承载信息、业务流信息以及内容信息来划分费率组。在为不同的费率组定义计费规则时，可以将视频业务对应的计费规则定义为统计流量，将通话业务对应的计费规则定义为统计时长，将短信业务对应的计费规则定义为统计次数。对于统计流量的业务，可以根据内容信息划分费率组；对于通话业务，可以依据业务流信息划分费率组，对于短信业务，可以通过承载信息来划分费率组。这样可以实现依据不同业务的类型，分别进行计费测量，甚至依据不同的计费粒度进行计费测量，使得计费更灵活，更合理。
需要说明的是，本发明实施例中业务数据信息还可以包括除承载信息、业务流信息以及内容信息以外其他粒度的数据信息，此处仅为举例，并不构成限定。
进一步地，可以由网关用户面设备、网关控制面设备、计费网关(Charging Gateway，CG)、在线计费设备(Online charging function，OCF)以及PCRF等中的一个或多个预先定义费率组，确定每个费率组对应的计费规则。具体可以有如下实现方式。
方式一，可以由网关控制面设备依据业务数据信息预先定义费率组，以及确定每个费率组对应的计费规则。网关控制面设备可以将包含业务数据信息与计费规则的映射关系的费率组信息发送给网关用户面设备。网关用户面 设备根据接收到的费率组信息进行配置，当网关用户面设备接收到业务的分组数据时，根据该业务对应的计费规则进行相应的计费处理。
方式二，可以直接在网关用户面设备预先依据业务数据信息定义费率组，以及确定每个费率组对应的计费规则。
方式三，可以由PCRF、CG或COF预先定义业务与计费规则的映射关系。网关控制面设备可以从PCRF、CG或COF获取业务与计费规则的映射关系，或者PCRF、CG或COF可以主动将业务与计费规则的映射关系发送给网关控制面设备。网关控制面设备依据业务与计费规则的映射关系，生成业务数据信息与计费规则的映射关系。网关控制面设备可以将包含业务数据信息与计费规则的映射关系的费率组信息发送给网关用户面设备。另外，PCRF、CG或COF还可以预先定义业务的计费粒度要求，并将其发送给网关控制面设备，网关控制面设备可以依据业务的计费粒度要求选择对应粒度的业务数据信息确定费率组。
需要说明的是，依据不同粒度的业务数据信息预先定义费率组，以及确定每个费率组对应的计费规则的方式可以有多种，此处仅为举例，并不构成限定。
需要说明的是，计费规则可以包括下述信息中的一项或多项：
APN、计费属性(Charging Characteristic)、计费测量配置信息、计费方式(离线计费或者在线计费)、计费上报信息(一定的时长阈值、流量阈值或者次数阈值上报)、计费动作信息(继续、丢弃或者重定向分组数据)等等。
承载信息可以包括承载的标识、GTP隧道信息以及IP隧道信息等的一个或多个。
例如，承载标识可以是S1承载标识、S5/8承载标识等等。GTP隧道信息可以是GTP隧道地址、GTP隧道标识等等。
GTP隧道信息可以是网络协议地址(Internet Protocol，IP)、用户数 据报协议(User Datagram Protocol，UDP)端口以及隧道端点标识符(Tunnel Endpoint ID，TEID)的组合等中的一个或多个。
IP隧道信息可以是通用路由封装(Generic Routing Encapsulation，GRE)信息、网络协议安全(IP Security，IPSec)信息、第二层隧道协议(Layer 2Tunneling Protocol，L2TP)信息、虚拟局域网(Virtual Local Area Network，VLAN)信息、虚拟可扩展局域网(Virtual extensible Local Area Network，VxLAN)信息、多信息通道方式(Multiple Information Passageway，MIP)信息等中的一个或者多个。
业务流信息可以包括业务流标识(Service Flow Identifier，SFID)、传输层信息以及网络层信息等中的一个或多个。其中，传输层信息以及网络层信息也就是业务数据的五元组信息。
例如，网络层信息可以包括，源、目的IP地址，源、目的端口号；传输层信息可以包括传输层协议，例如源、目的协议类型等等。
内容信息可以包括内容标识以及应用层信息等中的一个或多个。
例如，应用层信息可以包括统一资源定位符(Uniform Resource Locator，URL)信息。
应该知道的是，一般一个用户设备会请求多个业务，也就是一个用户设备对应有多个业务；一个业务的业务数据可能需要一个或多个承载来传输，且业务数据是以一个或多个业务流的形式进行传输，也就是一个业务可以对应一个或多个承载信息以及一个或多个业务流信息；业务流中包含有一个或多个内容信息，也就是一个业务流信息或一个承载信息可以对应一个或多个内容信息。
S320，网关用户面设备从为用户设备提供服务的网络设备接收分组数据(Packet)。该分组数据包括业务数据信息，例如，承载信息、业务流信息以及内容信息。
其中，为用户设备提供服务的网络设备可以包括：演进基站(evolved Node  B，eNB)、互联网服务器(Internet Server)、S-GW、P-GW、演进分组数据网关(Evolved Packet Data Gateway，ePDG)、高速分组数据服务网关(High Rate Packet Data Serving Gateway，HSGW)等等。
网络设备在为用户设备提供服务时，与用户设备交互的分组数据一般通过网关用户面设备进行传输，这些分组数据包括用户设备的业务数据。
S330，网关用户面设备解析接收到的分组数据得到第一业务数据信息，并根据第一业务数据信息和第一映射关系确定第一计费规则，其中，第一映射关系包括第一业务数据信息与第一计费规则的第二映射关系；该第一业务数据信息可以是承载信息、业务流信息以及内容信息的任意一个或多个。
其中，通过解析分组数据得到的承载信息可以包括以下一项或多项：承载标识、GTP隧道信息等等。
解析分组数据得到的业务流信息可以包括以下一项或多项：业务流标识、传输层信息以及网络层信息等等。
解析分组数据得到的内容信息可以包括以下一项或多项：内容标识、应用层信息等等。
通过前面的描述可以知道，费率组是依据业务数据信息来划分的，也就是计费规则是与业务数据信息有映射关系的。相应的，确定分组数据包括的业务数据信息能够确定其对应的第一计费规则。
对于依据承载划分的费率组的业务，可以通过解析该业务的分组数据得到的承载信息，根据该承载信息在第一映射关系中，与该承载信息相关的映射关系，确定其对应的第一计费规则。
例如，对于根据TEID划分的费率组，网关用户面设备根据解析分组数据得到的TEID与本地存储的业务数据信息与计费规则的映射关系，匹配得到TEID与第一计费规则的映射关系。
对于根据任意两种或两种以上的GTP隧道信息划分的费率组，例如，根据IP地址以及TEID的结合划分的费率组，可以根据解析分组数据得到IP地 址以及TEID，与本地存储的业务数据信息与计费规则的映射关系，匹配得到IP地址以及TEID与第一计费规则的映射关系。
应该知道的是，根据TEID以及IP地址和TEID确定第一计费规则的方式仅为举例说明，并不构成对本发明实施例的限定，利用其他承载信息确定第一计费规则的方式也在本发明实施例的范围内，不再赘述。
另外，由于内容信息以及业务流信息与承载信息对应，所以，也可以根据内容信息和/或业务流信息确定对应的承载信息。
对于依据业务流信息划分的费率组的业务，可以通过解析该业务的分组数据得到的业务流信息确定其对应的第一计费规则。
网关用户面设备可以根据解析分组数据得到五元组信息，例如，源IP地址、目的IP地址、源端口号、目的端口号和协议类型，根据该五元组信息确定其对应的第一计费规则，例如，对于根据不同的源IP地址划分的费率组，可以根据解析分组数据得到源IP地址与本地存储的业务数据信息与计费规则的映射关系，匹配得到源IP地址与第一计费规则的映射关系。对于根据源IP地址以及源端口号划分的费率组，可以根据解析分组数据得到源IP地址以及源端口号与本地存储的业务数据信息与计费规则的映射关系，匹配得到源IP地址以及源端口号与第一计费规则的映射关系。
应该知道的是，根据源IP地址以及源IP地址和源端口号确定第一计费规则的方式仅为举例说明，并不构成对本发明实施例的限定，利用其他业务流信息或者其他业务流信息的结合确定第一计费规则的方式也在本发明实施例的范围内，不再赘述确定。
另外，由于内容信息与业务流信息对应，所以，也可以根据内容信息确定对应的业务流信息。
对于需要依据内容信息进行计费的业务，可以通过解析该业务的分组数据得到的内容信息确定其对应的第一计费规则。
例如，对于根据不同的URL信息划分的费率组，网关用户面设备根据解 析分组数据得到的URL信息与本地存储的业务数据信息与计费规则的映射关系，匹配得到URL信息与第一计费规则的映射关系。
应该知道的是，根据URL信息确定第一计费规则的方式仅为举例说明，并不构成对本发明实施例的限定，利用其他内容信息确定第一计费规则的方式也在本发明实施例的范围内，不再赘述。
S340，根据第一计费规则对分组数据进行计费处理。
网关用户面设备根据第一计费规则进行测量，得到计费测量信息后，可以将该计费测量信息发送给网关控制面设备，网关控制面设备根据计费测量信息生成该用户本次服务的话单。也可以由网关用户面设备直接生成话单。
网关用户面设备根据第一计费规则进行计费信息测量时，可以根据第一计费规则中包含的计费测量配置信息，统计第一业务数据信息对应的业务所使用的时间长度、流量信息以及次数等的一项或多项。换句话说，网关用户面设备可以以第一计费规则对应的业务数据信息为测量粒度统计网络设备为用户设备提供服务的时间长度、流量信息以及次数一项或多项。网关用户面设备可以根据第一计费规则中包含的计费上报信息，将计费测量信息发送给网关控制面设备，例如，可以根据设定的时间间隔进行上报；也可以根据网关控制面发送的配置信息，判断当该计费测量信息达到阈值时，然后进行上报；还可以在业务结束后进行上报。例如，网关用户面设备可以获取用户设备对应的账户信息，例如账户余额、时间上限、流量上限，或者次数上限等等。该信息可以从网关控制面获取，在网关用户面设备进行计费测量时，当对应的账户余额不足，或者达到使用上限时，将计费测量信息上报给网关控制面设备。计费测量信息中可以包含的发送计费信息的时长、流量或者次数。阈值信息可以由网关控制面配置，也可以在网关用户面进行缺省配置。在费率变更、用户业务结束或者网关控制面直接指示等的情况下，网关用户面设备也可以向网关控制面设备上报计费测量信息。
另外，当网关用户面设备计费达到阈值之后，可以继续为用户设备提供 转发服务。例如，可以在计费达到阈值后上报给网关控制面设备，网关用户面设备上报之后，将计费测量信息清零，重新进行统计。或者，在网关用户面设备计费达到阈值之后，直接将接收到的对应用户设备的分组数据丢弃，当再次接收到网关控制面设备发送的阈值后，在对分组数据进行转发，并进行计费测量。或者，将用户设备对应的数据业务重新定向到一个网站，例如，可以重新定向到话费充值页面。
网关控制面设备在收到计费测量信息后，基于计费测量信息、第一计费规则和用户业务信息，生成本次业务计费信息，还可以将生成的本次业务计费信息发送给CG或者OCF等等。其中，用户业务信息主要包括会话信息(Access Point Name，APN)、承载信息和服务质量(Quality of Service，QoS)等。
网关控制面设备可以在达到下述一项或多项条件时，向CG或OCF发送本次业务计费信息：用户业务累计超过时长阈值、流量阈值或者次数阈值，用户关闭业务，等等。
另外，网关用户面设备可以接收网关控制面设备发送的请求消息，该请求消息携带有第二业务数据信息与第二计费规则的第三映射关系。当业务数据信息包含第二业务数据信息时，网关用户面设备将第一映射关系中关于所述第二业务数据信息的映射关系，修改为所述第三映射关系；当业务数据信息不包含第二业务数据信息时，网关用户面设备在所述第一映射关系中增加所述第三映射关系。
例如，网关用户面设备的接收到用户设备发送的分组数据，该分组数据携带有获取请求的新内容信息(例如，URL)。网关用户面设备将该新内容信息发送给网关控制面设备，用于请求增加该内容信息对应的费率组信息以及计费规则。或者，网关控制面设备接收到其他网络设备发送的重授权请求消息，该重授权请求消息用于请求增加一个业务流以及该业务流对应的计费规则。其中，这里的其他网络设备可以是PCRF等等。或者，网关控制面设备接 收到其他网络设备发送的创建会话请求。其中，这里的其他网络设备可以是MME或SGW等等。当出现上述情况时，网关控制面设备可以向网关用户面设备发送携带有费率组信息以及计费规则(第二业务数据信息与第二计费规则的第三映射关系)的请求消息，该请求消息用于请求添加或修改相应的映射关系。网关用户面设备接收到上述网关控制面发送的请求消息后，添加或修改相应的映射关系。通过本发明实施例，可以从不同粒度的业务数据信息划分费率组，以及确定每个费率组对应的计费规则，在进行计费时，根据业务数据信息确定计费规则，根据该计费规则进行计费，例如，根据承载信息、业务流信息、内容信息等等业务数据信息划分费率组，且在计费时也是根据承载信息、业务流信息、内容信息等等业务数据信息确定计费规则，并进行计费，实现了更灵活、更合理、更精确的计费，提高了用户体验。
在本发明实施例具体实施过程中，还可以为每个费率组分配费率组标识(Rating Group identity，RGID)，如图4所示。具体可以包括如下步骤：
S410，网关用户面设备确定业务数据信息与费率组标识的第一子映射关系，以及费率组标识与计费规则的第二子映射关系。
在依据不同粒度的业务数据信息预先定义费率组以及确定每个费率组对应的计费规则时，还可以为每个费率组分配一个费率组标识。
进一步地，可以由网关用户面设备、网关控制面设备、计费网关(Charging Gateway，CG)、在线计费设备(Online charging function，OCF)以及PCRF等中的一个或多个预先定义费率组，确定每个费率组对应的计费规则还可以为每个费率组分配一个RGID。具体还可以有如下实现方式。
方式一，可以通过网关控制面设备依据业务数据信息预先定义费率组，以及确定每个费率组对应的计费规则，为每个费率组分配RGID，并建立RGID与计费规则映射关系以及RGID与业务数据信息的映射关系。网关控制面设备可以将包含RGID与计费规则映射关系以及RGID与业务数据信息的映射关系的费率组信息发送给网关用户面设备。
方式二，可以直接在网关用户面设备预先依据业务数据信息定义费率组，以及确定每个费率组对应的计费规则，为每个费率组分配RGID，并建立RGID与计费规则映射关系以及RGID与业务数据信息的映射关系。
方式三，可以通过PCRF、CG或COF预先定义业务与计费规则的映射关系。网关控制面设备可以从PCRF、CG或COF获取业务与计费规则的映射关系，或者PCRF、CG或COF可以主动将业务与计费规则的映射关系发送给网关控制面设备。网关控制面设备依据业务与计费规则的映射关系，为该业务分配RGID，并生成RGID与计费规则映射关系以及RGID与业务数据信息的映射关系。网关控制面设备可以将包含RGID与计费规则映射关系以及RGID与业务数据信息的映射关系的费率组信息发送给网关用户面设备。另外，PCRF、CG或COF还可以预先定义业务的计费粒度要求，并将其发送给网关控制面设备，网关控制面设备可以依据业务的计费粒度要求选择对应粒度的业务数据信息确定费率组。
S420，网关用户面设备从为用户设备提供服务的网络设备接收分组数据。
步骤S420前述步骤S320类似，不再赘述。
S430，网关用户面设备解析接收到的分组数据得到第一业务数据信息，根据该第一业务数据信息与第一RGID的第一子映射关系以及第一RGID与第一计费规则的第二子映射关系，确定第一计费规则。
S440，根据第一计费规则对分组数据进行计费处理。
步骤S440与前述步骤S340类似，不再赘述。
另外，网关用户面设备可以接收网关控制面设备发送的请求消息，该请求消息携带有第二业务数据信息与第二RGID，以及第二RGID与第二计费规则的映射关系。当业务数据信息包含第二业务数据信息时，网关用户面设备将第一映射关系中关于所述第二业务数据信息的映射关系，修改为第二业务数据信息与第二RGID，以及第二RGID与第二计费规则的映射关系；当业务数据信息不包含第二业务数据信息时，网关用户面设备在所述第一映射关系中增 加第二业务数据信息与第二RGID，以及第二RGID与第二计费规则的映射关系。
费率组标识相对应的费率组信息可以预先配置在网关用户面设备。如果网关控制面设备发送的请求消息中仅有第二业务数据信息与第二RGID的映射关系，或者业务标识与第二RGID的映射关系，则网关用户面设备可以基于第二RGID信息确定本地配置预先配置的其他费率组信息(第二计费规则等)。
通过本发明实施例，可以从不同粒度的业务数据信息划分费率组，通过费率组标识映射不同粒度的业务数据信息以及不同的计费规则，从而可以实现在进行计费时，根据业务数据信息确定计费规则，根据该计费规则进行计费，实现了更灵活、更合理、更精确的计费，提高了用户体验。
下面结合附图，对本发明实施例做更详细的的解释说明，实施例并不构成对本发明实施例的限定。
网关用户面设备500可以采用分布式部署，例如，一些网关用户面设备可以部署在传输网络的核心汇聚点，或者可以部署在传输网络的汇聚点或者集成在基站。
如图5所示，网关用户面设备500用来处理用户数据的单元集合可以按照业务划分计费逻辑单元510，会话逻辑单元520，接口逻辑单元530等等。每一种逻辑单元可以包含有该逻辑单元的功能集合，属性以及信息等，每一逻辑单元的功能集合可以包含整个逻辑单元所拥有的全部子功能。例如，会话逻辑单元520可以包含维护某个用户设备的某个APN下的聚合QoS控制、IP地址管理的功能。
其中，一个用户设备的业务可以通过一个会话逻辑单元520进行管理。用户设备的业务上下文可以包括会话上下文、承载上下文、业务流上下文和内容上下文。同一个用户终端的用户业务上下文之间可以相互关联，例如，会话上下文可以关联一个或者多个承载上下文，或者关联到一个或者多个业务流上下文，或者关联到一个或者多个内容上下文。一个承载上下文可以关联到一个或者多个业务流上下文，或者关联到一个或者多个内容上下文。
计费逻辑单元510可以根据计费粒度的要求划分为承载逻辑单元511，业务流逻辑单元512，和/或内容逻辑单元513。
其中，承载逻辑单元511可以用来管理用户设备的一个承载的数据转发、QoS控制等功能，承载逻辑单元511可以依据不同的承载信息区分费率组，根据相应的费率组的计费规则进行计费。
业务流逻辑单元512可以包含用户设备的数据业务流的五元组级别的数据流解析和QoS控制等功能。业务流逻辑单元512可以依据不同的业务数据的业务流信息，确定出该业务数据对应的费率组，根据该费率组对应的计费规则进行计费。
内容逻辑单元513可以包含用户设备内容源数据流解析，内容数据级别的QoS控制，所谓的内容可以是指具体的业务是视频，网页浏览，下载，或者网络电话(Voice over Internet Protocol，VoIP)等等，所谓的内容源可以是指应用层数据业务内容信息，例如URL等，内容逻辑单元513可以依据不同的内容信息，确定出对应的业务数据对应的费率组，根据该费率组对应的计费规则进行计费。
需要说明的是，本发明实施例中描述的逻辑单元(逻辑单元可以是指会话逻辑单元，接口逻辑单元，计费逻辑单元等等)的模版可以具体为面向对象技术中的类(可以包括会话类、承载类、业务流类和内容类)。逻辑单元可以具体为类实例化的对象实例(对象实例可以简称为“对象”或者简称为“实例”)，也就是对应的会话逻辑单元、计费逻辑单元等等。对象实例可以被加载或者安装在网关用户面设备上。网关用户面设备在加载或安装对象实例之前需要为这些对象实例分配相应资源，例如，为对象实例分配内存、CPU进程(Process)或者线程(thread)、以及可选分配网络端口和网络带宽等，或者为对象实例分配虚拟化系统中的虚拟机等。网关控制面设备可以请求网关用户面设备创建会话、承载、业务流和内容的对象实例，也就是网关控制面设备可以请求网关用户面设备创建会话逻辑单元、承载逻辑单元、 业务流逻辑单元和内容逻辑单元。网关控制面设备的请求消息中包含有对象实例信息，对象实例信息和前述逻辑单元描述信息相似，包含对象实例的操作集合和对象实例的属性信息。费率组信息包含在对象实例的属性信息内，可以由网关控制面设备动态修改。对象实例的ID可以由网关控制面设备分配，也可以由网关用户面设备分配和关联。如果对象实例ID由网关用户面设备分配，则网关用户面设备在生成对象实例时，需要修改填写对象实例中的用户数据匹配对象实例ID信息。
基于上述结构，如图6所示，本发明实施例具体可以包括如下步骤：
S610，接口逻辑单元接收承载用户数的分组数据，该分组数据来自为用户设备提供服务的网络设备，其中，该网络设备可以是eNB，Internet Server，S-GW，P-GW，ePDG，HSGW，等等。
S620，接口逻辑单元基于分组数据的业务数据信息，确定该分组数据对应的会话逻辑单元，该接口逻辑单元将分组数据发送给对应的会话逻辑单元。
网关用户面的接口逻辑单元可以基于分组数据的源、目的IP地址、GTP隧道信息、IP隧道信息等其中一个或者多个分组数据信息来确定到相应的会话逻辑单元，上述分组数据信息可以通过解析分组数据得到。
其中，IP隧道信息可以包括GRE、IPSec、L2TP、VLAN、VxLAN、MIP等其中一个或者多个。
其中，分组数据信息以及会话逻辑单元的映射关系，可以基于网关控制面设备发送的配置信息进行配置。
S630，会话逻辑单元接收到接口逻辑单元发送的分组数据后，解析分组数据得到业务数据信息，该业务数据信息可以包括承载信息，业务流信息或者内容信息；根据该业务数据信息确定目标费率组标识。
会话逻辑单元的费率组标识与业务数据信息的对应关系可以根据网关控制面设备发送的配置信息进行配置。
S640，会话逻辑单元根据目标费率组标识确定对应的计费逻辑单元，会 话逻辑单元向该目标费率组标识对应的计费逻辑单元发送目标费率组标识以及分组数据。
其中，会话逻辑单元可以根据网关控制面设备发送的配置信息确定业务数据信息与费率组标识的映射关系以及业务数据信息与计费逻辑单元的映射关系，或者费率组标识与计费逻辑单元的映射关系。
S650，计费逻辑单元基于目标费率组标识对应的计费规则对分组数据进行计费处理。
计费逻辑单元依据目标费率组标识对应的计费规则以及分组数据进行计费测量，得到计费测量信息，计费逻辑单元可以将计费测量信息通过接口逻辑单元发送给网关控制面设备。另外，计费逻辑单元在向网关控制面设备发送计费测量信息时，还可以将计费逻辑单元标识一并发送，例如，将承载逻辑单元ID、业务流逻辑单元ID或者内容逻辑单元ID以及其对应的计费测量信息通过接口逻辑单元发送给网关控制面设备。
通过本发明实施例可以实现，通过不同的计费逻辑单元来对不同粒度要求的业务进行计费，实现控制面和用户面分离时的灵活计费的目的。
应该知道的是，本发明实施例仅是以接口逻辑单元、会话逻辑单元以及计费逻辑单元为例，对本发明做介绍，并不构成限定，其他能够实现前述方法的逻辑单元结构，也应在本发明的保护范围内。
本发明实施例在具体实现过程中，在步骤S650之前还可以进步包括如下可选步骤：
S660，网关用户面设备接收网关控制面发送的配置消息，该配置信息携带有计费上报信息。
例如，网关控制面设备接收到网关用户面设备发送计费测量信息后，基于计费规则和计费余额信息等等，计算出下一次上报的时长、流量或者次数等阈值。
网关控制面设备向网关用户面设备发送配置信息，该配置信息用于配置 计费逻辑单元，该配置信息中可以包括计费上报信息，例如，下一次上报计费信息的时长、流量或者次数等阈值信息。
S670,网关用户面设备依据配置消息携带的计费上报信息，配置计费逻辑单元。
网关用户面设备根据配置信息修改承载逻辑单元、业务流逻辑单元或者内容逻辑单元的计费上报信息。
网关用户面设备向网关控制面设备返回修改计费逻辑单元响应消息。
在本发明实施例具体实施过程中，步骤S660、S670也可以在步骤S650之后执行。
通过本发明实施例可以实现网关控制面设备根据需要配置网关用户面设备，使得网关用户面设备对用户业务数据的计费测量以及上报更灵活。
本发明实施例在具体实现过程中，网关用户面设备上可能并未配置有会话逻辑单元或者计费逻辑单元，或者现有的会话逻辑单元或者计费逻辑单元并不能很好的支持现有业务，网关用户面设备需要配置或增加配置新的会话逻辑单元或者计费逻辑单元时，具体的执行过程可以如图7所示。
S710，网关用户面设备接收网关用户面设备发送的请求消息，该请求消息携带有分组数据信息以及费率组信息，该请求消息用于指示根据分组数据信息以及费率组信息建立会话逻辑单元，建立计费逻辑单元，或者，修改会话逻辑单元，建立计费逻辑单元，或者，修改会话逻辑单元，修改计费逻辑单元。
网关控制面设备接收到其他网络设备发送的创建会话请求后，网关设备控制面设备会向网关用户面设备发送请求消息，请求建立会话逻辑单元，建立计费逻辑单元。例如，当有新用户设备接入网络设备等情况下，网络设备会向网关控制面设备发送创建会话请求，该创建会话请求可以携带业务数据信息或者用户设备的标识等等，网关用户面设备建立话逻辑单元，建立计费逻辑单元；当需要为用户设备提供新的服务时，可以发送修改会话请求，网 关用户面设备修改会话逻辑单元，建立计费逻辑单元；当需要更改当前服务的配置时，可以发送修改会话请求，网关用户面设备修改会话逻辑单元，修改计费逻辑单元。
网关控制面设备可以基于计费规则和会话信息(例如，APN等、用户终端IP地址信息)、承载信息或者内容信息生成费率组信息和业务数据信息等信息，并将携带有业务数据信息以及费率组信息的请求发送给网关用户面设备。其中，网关控制面设备可以获取本地配置的计费规则和/或PCRF生成的计费规则。
费率组标识相对应的费率组信息可以预先配置在网关用户面设备的接口管理单元上。如果网关控制面设备发送的消息中仅有费率组标识，则网关用户面设备可以基于费率组标识信息确定本地配置预先配置的其他费率组信息。
其中，费率组信息可以包括费率组标识以及计费规则等等。
S720，网关用户面设备根据业务数据信息以及费率组信息建立会话逻辑单元，建立计费逻辑单元，或者，修改会话逻辑单元，建立计费逻辑单元，或者，修改会话逻辑单元，修改计费逻辑单元。
网关用户面设备在建立会话逻辑单元和计费逻辑单元时，可以在会话逻辑单元中配置费率组标识和业务数据信息，在计费逻辑单元中配置费率组标识和计费规则。
其中，修改会话逻辑单元可以是指，在会话逻辑单元下添加业务数据信息与计费逻辑单元的映射表项。修改计费逻辑单元可以是指，在计费逻辑单元下添加，计费规则与费率组标识的映射表项。
另外，网关用户面设备可以向网关控制面设备返回建立成功响应消息。网关控制面收到响应消息后，可以向其他网络设备返回创建会话响应。
下面分别结合承载逻辑单元，业务流逻辑单元，以及内容逻辑单元，分别对本发明做进一步的介绍。其中，下述方案仅是以承载逻辑单元，业务流 逻辑单元，内容逻辑单元为例对于会话逻辑单元与计费逻辑单元的修改以及创建进行说明，其他实施细节可与前述是实施例进行相互参照理解，且并不构成对本发明实施例的限定。
图8为本发明实施例中以承载逻辑单元为例的信令交互图。如图8所示：
S801，网关控制面设备接收到其他网络设备发送的创建会话请求。其中，这里的其他网络设备可以是MME或SGW等等。
当有新的用户设备接入网络，或者用户设备重新接入网络时，MME或SGW等会与该用户设备建立连接，例如，会建立网络设备与用户设备的GTP隧道，或者会为用户设备传输数据。此时，MME或SGW可以向网关控制面设备发送创建会话请求，以便网关控制面设备指示网关用户面设备对该用户设备的数据传输进行计费控制。其中，该创建会话请求中可以携带承载信息，例如，GTP隧道信息或者内容信息等等。
S802，网关控制面设备向网关用户面设备发送请求消息，该请求消息携带有承载信息以及费率组信息，该请求消息用于指示网关用户面设备根据承载信息以及费率组信息建立会话逻辑单元以及承载逻辑单元。
S803，网关用户面设备接收到用户面设备发送的请求消息后，根据该请求中携带的承载信息以及费率组信息建立会话逻辑单元以及承载逻辑单元。
S804，网关用户面设备向网关控制面设备返回响应消息，该响应消息可以指示网关控制面设备会话逻辑单元以及计费逻辑单元已建立。
S805，网关控制面设备在接收到网关用户面设备发送的响应消息后，向其他网络设备返回会话创建响应消息。
S806，网关用户面设备通过接口逻辑单元接收到为用户设备提供服务的网络设备发送的分组数据后，将该分组数据发送给与该用户设备对应的会话逻辑单元。
其中，步骤S606与前述步骤S420类似，可相互参照理解。
S807，网关用户面设备的会话逻辑单元接收到接口逻辑单元发送的分组 数据后，解析该分组数据得到承载信息，根据该承载信息确定目标费率组标识。
其中，步骤S607与前述步骤S430类似，可相互参照理解。
S808，网关用户面设备的会话逻辑单元根据目标费率组标识确定对应的承载逻辑单元，并将该分组数据以及目标费率组标识发送给对应的承载逻辑单元。
其中，步骤S808与前述步骤S640类似，可相互参照理解。
S809，网关用户面设备的分组数据对应的承载逻辑单元接收到分组数据以及目标费率组标识后，根据目标费率组标识应的计费规则以及对分组数据进行计费测量，得到计费测量结果。
S810，网关用户面设备将计费测量结果发送给网关控制面设备。
其中，步骤S609和S610与前述步骤S450类似，可相互参照理解。
图9为本发明实施例中以业务流逻辑单元为例的信令交互图。如图9所示。
S901，网关控制面设备接收到其他网络设备发送的重授权请求消息，该重授权请求消息用于请求增加一个业务流以及该业务流对应的计费规则。其中，这里的其他网络设备可以是PCRF等等。
当用户设备请求新的业务时，PCRF可以向网关控制面设备发送重授权请求。
S902，网关控制面设备向网关用户面设备发送请求消息，该请求消息携带有业务流信息以及费率组信息，该请求消息用于指示网关用户面设备根据业务流信息以及费率组信息修改会话逻辑单元或者承载逻辑单元，建立承载逻辑单元或者业务流逻辑单元。
其中，若新增的业务流，通过承载逻辑单元进行计费，此时，请求消息可以用于指示修改业务流信息对应的会话逻辑单元以及承载逻辑单元。在此种情况下，当该业务流信息对应的承载信息也是新增信息时，请求消息可以 用于指示修改业务流信息对应的会话逻辑单元，建立业务流信息对应的承载逻辑单元。
若新增的业务流，通过业务流逻辑单元进行计费，此时，请求消息可以用于指示修改业务流信息对应的会话逻辑单元，建立业务流信息对应的业务流逻辑单元。
S903，网关用户面设备接收到用户面设备发送的请求消息后，根据该请求中携带的业务流信息以及费率组信息修改会话逻辑单元以及承载逻辑单元，或者修改会话逻辑单元建立承载逻辑单元，或者修改会话逻辑单元建立业务流逻辑单元。
S904，网关用户面设备向网关控制面设备返回响应消息，该响应消息可以指示网关控制面设备会话逻辑单元以及计费逻辑单元已建立或修改。
S905，网关控制面设备在接收到网关用户面设备发送的响应消息后，向其他网络设备返回会话创建响应消息。
S906，网关用户面设备通过接口逻辑单元接收到为用户设备提供服务的网络设备发送的承载着用户数的分组数据后，将该分组数据发送给与该用户设备对应的会话逻辑单元。
其中，步骤S906与前述步骤S620类似，可相互参照理解。
S907，网关用户面设备的会话逻辑单元接收到接口逻辑单元发送的分组数据后，解析该分组数据得到业务流信息，根据该业务流信息确定目标费率组标识。
其中，步骤S907与前述步骤S630类似，可相互参照理解。
S908，网关用户面设备的会话逻辑单元根据解析到的业务流信息确定对应的计费逻辑单元(承载逻辑单元或业务流逻辑单元)，并将该分组数据以及目标费率组标识发送给对应的计费逻辑单元。
其中，步骤S908与前述步骤S640类似，可相互参照理解。
S909，网关用户面设备的分组数据对应的计费逻辑单元接收到分组数据 以及目标费率组标识后，根据目标费率组标识对应的计费规则对分组数据进行计费测量，得到计费测量结果。
S910，网关用户面设备将计费测量结果发送给网关控制面设备。
其中，步骤S909和S910与前述步骤S650类似，可相互参照理解。
图10为本发明实施例中以内容逻辑单元为例的信令交互图。如图10所示。
S1001，网关用户面设备的会话逻辑单元接收到用户设备发送的分组数据，该分组数据携带有获取请求的新内容信息(例如，URL)，例如，用户设备发送的超文本传输协议(HyperText Transfer Protocol，HTTP)获取(get)消息。网关用户面设备将该新内容信息发送给网关控制面设备，用于请求增加该内容信息对应的费率组信息以及计费规则。
S1002，网关控制面设备接收到上述内容信息后，向网关用户面设备发送请求消息，该请求消息携带有内容信息以及费率组信息，该请求消息用于指示网关用户面设备根据内容信息以及费率组信息修改会话逻辑单元以及承载逻辑单元，或者修改会话逻辑单元以及业务流逻辑单元，或者修改会话逻辑单元且建立承载逻辑单元，或者修改会话逻辑单元且建立业务流逻辑单元，或者修改会话逻辑单元且建立内容逻辑单元。
由于，内容信息与业务流信息以及承载信息具有对应关系，所以通过内容信息还可以进一步确定业务流信息、承载信息等等。
例如，当用户设备的业务需要由内容逻辑单元进行计费时，该指示消息用于指示网关用户面设备根据内容信息以及费率组信息修改会话逻辑单元，建立内容逻辑单元；
当用户设备的该业务需要由业务流逻辑单元进行计费时，该指示消息用于指示网关用户面设备根据内容信息以及费率组信息修改会话逻辑单元且建立业务流逻辑单元，或者修改会话逻辑单元且修改业务流逻辑单元；
当用户设备的该业务需要由承载逻辑单元进行计费时，该请求消息用于 指示网关用户面设备根据内容信息以及费率组信息修改会话逻辑单元且建立承载逻辑单元，或者修改会话逻辑单元且修改承载逻辑单元；等等。
S1003，网关用户面设备接收到用户面设备发送的请求消息后，根据该请求消息中携带的分组数据信息以及费率组信息修改会话逻辑单元以及承载逻辑单元，或者修改会话逻辑单元以及业务流逻辑单元，或者修改会话逻辑单元且建立承载逻辑单元，或者修改会话逻辑单元且建立业务流逻辑单元，或者修改会话逻辑单元且建立内容逻辑单元。
S1004，网关用户面设备向网关控制面设备返回响应消息，该响应消息可以指示网关控制面设备会话逻辑单元以及计费逻辑单元已建立或修改。
S1005，网关用户面设备通过接口逻辑单元接收到为用户设备提供服务的网络设备发送的分组数据后，将该分组数据发送给与该用户设备对应的会话逻辑单元。
其中，步骤S1005与前述步骤S620类似，可相互参照理解。
S1006，网关用户面设备的会话逻辑单元接收到接口逻辑单元发送的分组数据后，解析该分组数据得到内容信息，根据该内容信息确定目标费率组标识。
其中，步骤S1006与前述步骤S630类似，可相互参照理解。
S1007，网关用户面设备的会话逻辑单元根据解析到的内容信息确定对应的计费逻辑单元(承载逻辑单元、业务流逻辑单元或内容逻辑单元)，并将该分组数据以及目标费率组标识发送给对应的计费逻辑单元。
其中，步骤S1007与前述步骤S640类似，可相互参照理解。
S1008，分组数据对应的计费逻辑单元接收到分组数据以及目标费率组标识后，根据目标费率组标识对应的计费规则对分组数据进行计费测量，得到计费测量结果。
S1009，网关用户面设备将计费测量结果发送给网关控制面设备。
其中，步骤S1008和S1009与前述步骤S650类似，可相互参照理解。
如图11所示，图11为本方发明实施例提供的另一种通信计费装置虚拟结构示意图。该装置用于实现图3-图4所描述的网关用户面设备对应的方法实施例，可相互参照理解。该装置具体可以包括：
确定单元1101，用于确定业务数据信息与计费规则的第一映射关系；
接收单元1102，用于从为用户设备提供服务的网络设备接收分组数据；
处理单元1103，用于解析所述分组数据，以得到第一业务数据信息，并根据所述第一业务数据信息和所述第一映射关系确定第一计费规则，其中，所述第一映射关系包括所述第一业务数据信息与所述第一计费规则的第二映射关系；
计费单元1104，用于根据所述第一计费规则对所述分组数据进行计费处理。
进一步地，业务数据信息包括以下一项或多项：
承载信息，业务流信息，内容信息。
可选地，所述接收单元1102还用于，接收所述网关控制面设备发送的配置信息，所述配置信息包括所述第一映射关系。
可选地，所述第一映射关系包括：
所述业务数据信息与费率组标识的第一子映射关系，以及所述费率组标识与所述计费规则的第二子映射关系。
可选地，所述处理单元1103还用于，
根据所述第一业务数据信息以及所述第一子映射关系，确定第一费率组标识，其中，所述第一子映射关系包括所述第一业务数据信息与所述第一费率组标识的映射关系；
根据所述第一费率组标识以及所述第二子映射关系，确定所述第一计费规则，其中，所述第二子映射关系包括所述第一费率组标识与所述第一计费规则的映射关系。
可选地，所述接收单元1102还用于，接收所述网关控制面设备发送的请 求消息，所述请求消息携带有第二业务数据信息与第二计费规则的第三映射关系；
所述处理单元1103还用于，当所述业务数据信息包含所述第二业务数据信息时，将所述第一映射关系中关于所述第二业务数据信息的映射关系，修改为所述第三映射关系；
所述处理单元1103还用于，当所述业务数据信息不包含所述第二业务数据信息时，在所述第一映射关系中增加所述第三映射关系。
如图12所示，图12为本方发明实施例提供的再一种通信计费装置虚拟结构示意图。该装置用于实现图3-图4所描述的网关控制面设备对应的方法实施例，可相互参照理解。该装置具体可以包括：
确定单元1201，用于确定业务数据信息与计费规则的第一映射关系；
发送单元1202，用于向所述网关用户面设备发送配置信息，所述配置信息包括所述第一映射关系，所述映射关系用于计费规则的确定。
进一步地，还包括，接收单元1203，用于接收策略与计费规则功能单元发送的业务标识与所述计费规则的第四映射关系，其中，所述业务标识对应有所述业务数据信息；
确定单元1201还用于，确定所述业务标识对应的所述业务数据信息，根据所述第四映射关系，确定所述第一映射关系。
可选地，确定单元1201还用于，预定义所述业务数据信息与所述计费规则的第一映射关系。
可选地，确定单元1201还用于，根据所述业务数据信息划分费率组，每一个费率组对应有一个费率组标识，划分在同一个费率组中的全部业务数据信息映射相同的计费规则。
如图13所示，图13为本发明实施例提供的一种网关用户面设备实体结构示意图。
如图13所示，该网关用户面设备具体可以包括：包括通信单元1301，处 理器1302，存储器1303。各个模块可以通过总线连接。
其中，通信单元1301用于支持网关用户面设备与上述实施例中的网关控制面设备以及其他网络设备之间收发信息，例如，通信单元1301可以是接口电路，可以支持网关用户面设备与网关控制面设备以及其他网络设备之间的光通信。在网关用户面设备与网关控制面设备通信过程中，分组数据和信令消息由处理器1302进行处理，并由通信单元1301发送给网关控制面设备或其他网络设备。来自网关控制面设备以及其他网络设备的信号经由通信单元1301接收，并进行调解，进一步由处理器1302进行处理得到网关控制面设备以及其他网络设备发送或转发的分组数据和信令信息。处理器1302还执行图3-图4以及图6-图10中涉及网关用户面设备的处理过程和/或用于本申请所描述的技术的其他过程。存储器1303用于存储接入网设备的程序代码和数据。
如图14所示，图14为本发明实施例提供的一种网关控制面设备实体结构示意图。
如图14所示，该网关控制面设备具体可以包括：包括通信单元1401，处理器1402，存储器1403。各个模块可以通过总线连接。
其中，通信单元1401用于支持网关控制面设备与上述实施例中的网关用户面设备以及其他网络设备之间收发信息，例如，通信单元1401可以是接口电路，可以支持网关控制面设备与网关用户面设备以及其他网络设备之间的光通信。在网关控制面设备与网关用户面设备以及其他网络设备通信过程中，分组数据和信令消息由处理器1402进行处理，并由通信单元1401发送给网关用户面设备或其他网络设备。来自网关用户面设备以及其他网络设备的信号经由通信单元1401接收，并进行调解，进一步由处理器1402进行处理得到网关用户面设备以及其他网络设备发送或转发的分组数据和信令信息。处理器1402还执行图3-图4以及图6-图10中涉及网关用户面设备的处理过程和/或用于本申请所描述的技术的其他过程。存储器1403用于存储接入网设备的程序代码和数据。
需要说明的是，上述实施例中的网关用户面设备或网关控制面设备的处理器可以是一个处理器，也可以是多个处理元件的统称。例如，该处理器可以是中央处理器(Central Processing Unit，CPU)，也可以是特定集成电路(Application Specific Integrated Circuit，ASIC)，或者是被配置成实施本发明实施例的一个或多个集成电路，例如：一个或多个微处理器(digital singnal processor，DSP)，或，一个或者多个现场可编程门阵列(Field Programmable Gate Array，FPGA)。
上述实施例中的网关用户面设备或网关控制面设备的存储器可以是一个存储装置，也可以是多个存储元件的统称，且用于存储可执行程序代码或接入网管理设备运行所需要参数、数据等。且存储器903可以包括随机存储器(RAM)，也可以包括非易失性存储器(non-volatile memory)，例如磁盘存储器，闪存(Flash)等。
上述实施例中的网关用户面设备或网关控制面设备的总线可以是工业标准体系结构(Industry Standard Architecture，ISA)总线、外部设备互连(Peripheral Component，PCI)总线或扩展工业标准体系结构(Extended Industry Standard Architecture，EISA)总线等。该总线可以分为地址总线、数据总线、控制总线等。
本发明实施例还提供了一种计费系统，该系统包括上述实施例的网关用户面设备以及网关控制面设备。
专业人员应该还可以进一步意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、计算机软件或者二者的结合来实现，为了清楚地说明硬件和软件的可互换性，在上述说明中已经按照功能一般性地描述了各示例的组成及步骤。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本发明的范围。
结合本文中所公开的实施例描述的方法或算法的步骤可以用硬件、处理器执行的软件模块，或者二者的结合来实施。软件模块可以置于随机存储器(RAM)、内存、只读存储器(ROM)、电可编程ROM、电可擦除可编程ROM、寄存器、硬盘、可移动磁盘、CD-ROM、或技术领域内所公知的任意其它形式的存储介质中。
以上所述的具体实施方式，对本发明的目的、技术方案和有益效果进行了进一步详细说明，所应理解的是，以上所述仅为本发明的具体实施方式而已，并不用于限定本发明的保护范围，凡在本发明的精神和原则之内，所做的任何修改、等同替换、改进等，均应包含在本发明的保护范围之内。

Claims (20)

  1. 一种通信计费方法，其特征在于，包括：
    网关用户面设备确定业务数据信息与计费规则的第一映射关系；
    所述网关用户面设备从为用户设备提供服务的网络设备接收分组数据；
    所述网关用户面设备解析所述分组数据，以得到第一业务数据信息，并根据所述第一业务数据信息和所述第一映射关系确定第一计费规则，其中，所述第一映射关系包括所述第一业务数据信息与所述第一计费规则的第二映射关系；
    所述网关用户面设备根据所述第一计费规则对所述分组数据进行计费处理。
  2. 根据权利要求1所述的方法，其特征在于，所述业务数据信息包括以下一项或多项：
    承载信息，业务流信息，内容信息。
  3. 根据权利要求1或2所述的方法，其特征在于，在所述网关用户面设备确定所述业务数据信息与所述计费规则的第一映射关系之前，还包括：
    所述网关用户面设备接收所述网关控制面设备发送的配置信息，所述配置信息包括所述第一映射关系。
  4. 根据权利要求1-3任意一项所述的方法，其特征在于，所述第一映射关系包括：
    所述业务数据信息与费率组标识的第一子映射关系，以及所述费率组标识与所述计费规则的第二子映射关系。
  5. 根据权利要求4所述的方法，其特征在于，所述根据所述第一业务数据信息确定第一计费规则包括：
    所述网关用户面设备根据所述第一业务数据信息以及所述第一子映射关系，确定第一费率组标识，其中，所述第一子映射关系包括所述第一业务数据信息与所述第一费率组标识的映射关系；
    所述网关用户面设备根据所述第一费率组标识以及所述第二子映射关系，确定所述第一计费规则，其中，所述第二子映射关系包括所述第一费率组标识与所述第一计费规则的映射关系。
  6. 根据权利要求1-5任意一项所述的方法，其特征在于，还包括：
    所述网关用户面设备接收所述网关控制面设备发送的请求消息，所述请求消息携带有第二业务数据信息与第二计费规则的第三映射关系；
    当所述业务数据信息包含所述第二业务数据信息时，所述网关用户面设备将所述第一映射关系中关于所述第二业务数据信息的映射关系，修改为所述第三映射关系；
    当所述业务数据信息不包含所述第二业务数据信息时，所述网关用户面设备在所述第一映射关系中增加所述第三映射关系。
  7. 一种通信计费方法，其特征在于，包括：
    网关控制面设备确定业务数据信息与计费规则的第一映射关系；
    所述网关控制面设备向所述网关用户面设备发送配置信息，所述配置信息包括所述第一映射关系，所述映射关系用于计费规则的确定。
  8. 根据权利要求7所述的方法，其特征在于，所述网关控制面设备确定所述业务数据信息与所述计费规则的第一映射关系包括：
    所述网关控制面设备接收策略与计费规则功能单元发送的业务标识与所述计费规则的第四映射关系，其中，所述业务标识对应有所述业务数据信息；所述网关控制面设备确定所述业务标识对应的所述业务数据信息，根据所述第四映射关系，确定所述第一映射关系。
  9. 根据权利要求7所述的方法，其特征在于，所述网关控制面设备确定所述业务数据信息与所述计费规则的第一映射关系包括：
    网关控制面设备预定义所述业务数据信息与所述计费规则的第一映射关系。
  10. 根据权利要求7-9任意一项所述的方法，其特征在于，所述网关控 制面设备确定所述业务数据信息与所述计费规则的第一映射关系包括：
    所述网关控制面设备根据所述业务数据信息划分费率组，每一个费率组对应有一个费率组标识，划分在同一个费率组中的全部业务数据信息映射相同的计费规则。
  11. 一种通信计费装置，其特征在于，包括：
    确定单元，用于确定业务数据信息与计费规则的第一映射关系；
    接收单元，用于从为用户设备提供服务的网络设备接收分组数据；
    处理单元，用于解析所述分组数据，以得到第一业务数据信息，并根据所述第一业务数据信息和所述第一映射关系确定第一计费规则，其中，所述第一映射关系包括所述第一业务数据信息与所述第一计费规则的第二映射关系；
    计费单元，用于根据所述第一计费规则对所述分组数据进行计费处理。
  12. 根据权利要求11所述的装置，其特征在于，所述业务数据信息包括以下一项或多项：
    承载信息，业务流信息，内容信息。
  13. 根据权利要求11或12所述的装置，其特征在于，所述接收单元还用于，接收所述网关控制面设备发送的配置信息，所述配置信息包括所述第一映射关系。
  14. 根据权利要求11-13任意一项所述的装置，其特征在于，所述第一映射关系包括：
    所述业务数据信息与费率组标识的第一子映射关系，以及所述费率组标识与所述计费规则的第二子映射关系。
  15. 根据权利要求14所述的装置，其特征在于，所述处理单元还用于，
    根据所述第一业务数据信息以及所述第一子映射关系，确定第一费率组标识，其中，所述第一子映射关系包括所述第一业务数据信息与所述第一费率组标识的映射关系；
    根据所述第一费率组标识以及所述第二子映射关系，确定所述第一计费规则，其中，所述第二子映射关系包括所述第一费率组标识与所述第一计费规则的映射关系。
  16. 根据权利要求11-15任意一项所述的装置，其特征在于，
    所述接收单元还用于，接收所述网关控制面设备发送的请求消息，所述请求消息携带有第二业务数据信息与第二计费规则的第三映射关系；
    所述处理单元还用于，当所述业务数据信息包含所述第二业务数据信息时，将所述第一映射关系中关于所述第二业务数据信息的映射关系，修改为所述第三映射关系；
    所述处理单元还用于，当所述业务数据信息不包含所述第二业务数据信息时，在所述第一映射关系中增加所述第三映射关系。
  17. 一种通信计费装置，其特征在于，包括：
    确定单元，用于确定业务数据信息与计费规则的第一映射关系；
    发送单元，用于向所述网关用户面设备发送配置信息，所述配置信息包括所述第一映射关系，所述映射关系用于计费规则的确定。
  18. 根据权利要求17所述的装置，其特征在于，还包括：
    接收单元，用于接收策略与计费规则功能单元发送的业务标识与所述计费规则的第四映射关系，其中，所述业务标识对应有所述业务数据信息；
    所述确定单元还用于，确定所述业务标识对应的所述业务数据信息，根据所述第四映射关系，确定所述第一映射关系。
  19. 根据权利要求17所述的装置，其特征在于，所述确定单元还用于，预定义所述业务数据信息与所述计费规则的第一映射关系。
  20. 根据权利要求17-19任意一项所述的装置，其特征在于，所述确定单元还用于，根据所述业务数据信息划分费率组，每一个费率组对应有一个费率组标识，划分在同一个费率组中的全部业务数据信息映射相同的计费规则。
PCT/CN2016/081692 2016-05-11 2016-05-11 一种通信计费方法 WO2017193303A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2016/081692 WO2017193303A1 (zh) 2016-05-11 2016-05-11 一种通信计费方法

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2016/081692 WO2017193303A1 (zh) 2016-05-11 2016-05-11 一种通信计费方法

Publications (1)

Publication Number Publication Date
WO2017193303A1 true WO2017193303A1 (zh) 2017-11-16

Family

ID=60266053

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/081692 WO2017193303A1 (zh) 2016-05-11 2016-05-11 一种通信计费方法

Country Status (1)

Country Link
WO (1) WO2017193303A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110620716A (zh) * 2018-06-19 2019-12-27 华为技术有限公司 数据传输方法、相关装置及系统

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1859128A (zh) * 2005-05-16 2006-11-08 华为技术有限公司 一种对数据业务进行内容计费的方法
CN101075884A (zh) * 2007-06-29 2007-11-21 中国移动通信集团公司 业务内容计费方法
US20070274481A1 (en) * 2003-07-31 2007-11-29 Huawei Technologies Co., Ltd. Method For Implementing Account Charging And Account Charging System
CN102739409A (zh) * 2012-06-15 2012-10-17 中兴通讯股份有限公司 一种上网流量计费装置及方法

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20070274481A1 (en) * 2003-07-31 2007-11-29 Huawei Technologies Co., Ltd. Method For Implementing Account Charging And Account Charging System
CN1859128A (zh) * 2005-05-16 2006-11-08 华为技术有限公司 一种对数据业务进行内容计费的方法
CN101075884A (zh) * 2007-06-29 2007-11-21 中国移动通信集团公司 业务内容计费方法
CN102739409A (zh) * 2012-06-15 2012-10-17 中兴通讯股份有限公司 一种上网流量计费装置及方法

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110620716A (zh) * 2018-06-19 2019-12-27 华为技术有限公司 数据传输方法、相关装置及系统

Similar Documents

Publication Publication Date Title
US11588656B2 (en) Selecting a user plane function based on a device type received by a session management function
EP3695639B1 (en) Monitoring and reporting service performance
US9973989B2 (en) Co-location of application service platform with access node and local gateway
EP3424231B1 (en) A method and a base station for controlling user data traffic between the wireless device and a local cloud
US9560549B2 (en) Reporting of aggregated RAN congestion information
US9479917B1 (en) Rating group-specific actions for mobile networks
WO2017143915A1 (zh) 一种实现接入点带宽限制的方法和装置
US20140169286A1 (en) Method and System For Hub Breakout Roaming
JP6627980B2 (ja) コアネットワーク・エンティティ及びそれにより行われる方法、並びにポリシー機能により行われる方法
EP3065451B1 (en) Congestion mitigation for roamers
KR101655641B1 (ko) 크레딧 초과 pcc 규칙의 일시적 디스에이블
EP3110197B1 (en) Method for application detection and control in roaming scenario and v-pcrf
US11206515B2 (en) Method and system for enhancing charging for co-located SGW and PGW
TWI659660B (zh) 用於在異質無線通訊系統中的重新路由封包之收費
CN107431953B (zh) 业务流分流的方法和装置
WO2013135213A1 (zh) Tdf会话的处理方法及pcrf
WO2017193303A1 (zh) 一种通信计费方法
EP3982598A1 (en) Method and apparatus for sending and receiving message, and communication system
WO2014110966A1 (zh) 一种业务数据的处理方法、装置和系统
US8843128B2 (en) Roaming session termination triggered by roaming agreement/partner deletion
US20210160677A1 (en) Orchestrator equipment in a cellular telecommunication system
EP2873292B1 (en) Co-location of application service platform with access node and local gateway
WO2016019985A1 (en) Method computer program product and apparatus for traffic flow differentiation
WO2017088163A1 (zh) 一种信息内容传输方法和装置
WO2015032073A1 (zh) 一种用于通用路由封装隧道的数据包转发方法及装置

Legal Events

Date Code Title Description
NENP Non-entry into the national phase

Ref country code: DE

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

Ref document number: 16901258

Country of ref document: EP

Kind code of ref document: A1

122 Ep: pct application non-entry in european phase

Ref document number: 16901258

Country of ref document: EP

Kind code of ref document: A1