WO2017148206A1 - 一种计费方法和装置 - Google Patents

一种计费方法和装置 Download PDF

Info

Publication number
WO2017148206A1
WO2017148206A1 PCT/CN2016/111531 CN2016111531W WO2017148206A1 WO 2017148206 A1 WO2017148206 A1 WO 2017148206A1 CN 2016111531 W CN2016111531 W CN 2016111531W WO 2017148206 A1 WO2017148206 A1 WO 2017148206A1
Authority
WO
WIPO (PCT)
Prior art keywords
data packet
service
service node
information
chain policy
Prior art date
Application number
PCT/CN2016/111531
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 EP16892384.5A priority Critical patent/EP3407538A4/en
Publication of WO2017148206A1 publication Critical patent/WO2017148206A1/zh
Priority to US16/114,872 priority patent/US20180367323A1/en

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
    • H04L12/1403—Architecture for metering, charging or billing
    • H04L12/1407—Policy-and-charging control [PCC] architecture
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/14—Charging, metering or billing arrangements for data wireline or wireless communications
    • 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
    • H04L12/1403—Architecture for metering, charging or billing
    • 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
    • H04L12/1432—Metric aspects
    • H04L12/1435—Metric aspects volume-based
    • 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
    • H04L12/1432—Metric aspects
    • H04L12/1439—Metric aspects time-based
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/24—Traffic characterised by specific attributes, e.g. priority or QoS
    • H04L47/2441—Traffic characterised by specific attributes, e.g. priority or QoS relying on flow classification, e.g. using integrated services [IntServ]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
    • H04L63/0876—Network architectures or network communication protocols for network security for authentication of entities based on the identity of the terminal or configuration, e.g. MAC address, hardware or software configuration or device fingerprint
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/61—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP based on the service used
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/62—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP based on trigger specification
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/66—Policy and charging system
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/68—Payment of value-added services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/80—Rating or billing plans; Tariff determination aspects
    • H04M15/8016—Rating or billing plans; Tariff determination aspects based on quality of service [QoS]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/80—Rating or billing plans; Tariff determination aspects
    • H04M15/8027—Rating or billing plans; Tariff determination aspects based on network load situation
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/82—Criteria or parameters used for performing billing operations
    • H04M15/8214—Data or packet based
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/24—Accounting or billing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/64—On-line charging system [OCS]

Definitions

  • the present invention relates to the field of communications technologies, and in particular, to a charging method and apparatus.
  • QoS Quality of Service
  • 3GPP Third Generation Partnership Project
  • R7 a Policy and Charging Control
  • 3GPP enhanced the application-based charging and policy control of the PCC architecture in Release 12.
  • Service Chain refers to the service sequence (Service Enabler, SE) of the SGI/Gi-LAN, in which the data stream is transmitted in the network, in the order specified by the business logic. It can be a value-added service deployed by an operator, or a service provided by a third-party service provider, such as a firewall, load balancing (LB), video acceleration, advertisement, compression decoding, and antivirus.
  • SE Service Enabler
  • LB load balancing
  • video acceleration advertisement
  • compression decoding compression decoding
  • antivirus antivirus
  • the embodiment of the invention provides a charging method and device, which solves the problem of how to perform charging based on a service chain policy in the prior art, and there is currently no solution problem.
  • the first aspect provides a charging method, including: after receiving the data packet, the charging triggering entity determines, according to the identification information carried in the data packet, a service chain policy used by the data packet, where the service chain policy indicates The service node that processes the data packet; the charging triggering entity sends the usage information of the service chain policy to the charging system, wherein the usage information of the service chain policy is used for charging.
  • the service chain policy used by the data packet is determined by the identifier information carried by the data packet, and the service chain policy usage information for charging is sent to the charging system, so that the charging based on the service chain policy is implemented.
  • the charging triggering entity determines the service chain policy used by the data packet according to the identifier information carried in the data packet, the charging triggering entity Obtaining the correspondence between the identification information and the service chain policy; the charging triggering entity determines the service chain policy used by the data packet according to the identification information carried in the data packet, and the charging triggering entity determines the data packet usage according to the corresponding relationship.
  • Business chain strategy before the charging triggering entity determines the service chain policy used by the data packet according to the identifier information carried in the data packet, the charging triggering entity Obtaining the correspondence between the identification information and the service chain policy; the charging triggering entity determines the service chain policy used by the data packet according to the identification information carried in the data packet, and the charging triggering entity determines the data packet usage according to the corresponding relationship.
  • the billing triggering entity can determine the service chain policy used by the data packet according to the corresponding relationship, because the mapping relationship between the identifier information of the data packet and the service chain policy used by the data packet is configured.
  • the usage information of the service chain policy includes attribute information of a service node that processes the data packet, and includes using the service chain policy. At least one of time information, traffic information of a packet using a business chain policy.
  • the charging triggering entity is a policy and charging execution function PCEF entity, and the service detecting function TDF entity , shunt or business node.
  • the charging triggering entity when the preset reporting condition is met, sends the usage information of the service chain policy to the charging system, where the preset reporting conditions include immediate reporting, reporting within a specified time, or reaching a specified capacity. Reported at the time.
  • the service chain policy further indicates a sequence in which the service node processing the data packet processes the data packet .
  • a charging method including: a service node receives a data packet, and determines to process the data packet according to processing indication information carried by the data packet; the service node processes the data packet; and the service node sends the service node to the charging system.
  • the usage information wherein the usage information of the service node includes attribute information of the service node, and at least one of time information, event information, and traffic information of the service node processing the data packet.
  • the service node-based charging is implemented by the service node generating and reporting its usage information to the charging system.
  • the event information of the service node processing the data packet includes the number of times the service node performs processing.
  • the processing indication information includes an identifier of the service node or identifier information of the data packet.
  • the first possible implementation manner of the second aspect when the processing indication information includes the identifier information of the data packet, the service node obtains the identifier information before receiving the data packet.
  • determining, according to the processing indication information carried in the data packet, processing the data packet includes: determining, according to the identifier information carried by the data packet and the corresponding relationship, processing the data packet.
  • the service node sends the usage information of the service node to the charging system through the traffic splitter.
  • the usage information can be reported by the traffic shunt to avoid establishing an interface between the charging system and each service node to receive usage information of each service node, thereby reducing the pressure on the charging system.
  • the data packet further carries a service chain policy identifier
  • the service node sends the usage information of the service node to the charging system through the TSSF, where the service node usage information further includes a service chain policy identifier, and the service chain policy identifier is used.
  • the usage information of each service node is associated by the service chain policy identifier, which can increase the flexibility of the charging system for charging, for example, preferential charging for users who use a certain service chain policy. .
  • the service node when the preset reporting condition is met, sends the service node to the charging system.
  • the usage information wherein the preset reporting conditions include immediate reporting, reporting in a specified time period, or reporting when the specified capacity is reached.
  • a charging apparatus comprising: a processor, an input interface, an output interface, and a memory, wherein: the processor reads a program in the memory, and performs the method of the first aspect.
  • a charging apparatus comprising: a processor, an input interface, an output interface, and a memory, wherein: the processor reads a program in the memory, and performs the method of the second aspect.
  • a computer readable storage medium wherein executable program code is stored, the program code for implementing the method of the first aspect.
  • a computer readable storage medium wherein executable program code is stored, the program code for implementing the method of the second aspect.
  • a charging apparatus comprising means for performing the method of the first aspect.
  • a charging apparatus comprising means for performing the method of the second aspect.
  • the service chain policy used by the data packet is determined according to the identification information carried by the data packet, and the service chain policy usage information for charging is sent to the charging system, thereby implementing the service chain policy.
  • the service node-based charging is implemented by the service node generating and reporting its usage information to the charging system.
  • FIG. 1 is a schematic diagram of a network architecture according to an embodiment of the present invention
  • FIG. 2 is an exemplary flowchart of a charging method 200 based on a service chain policy in accordance with an embodiment of the present invention
  • FIG. 3 is an exemplary flowchart of a service node based charging method 300 in accordance with an embodiment of the present invention
  • FIG. 4 is a schematic diagram of another network architecture according to an embodiment of the present invention.
  • FIG. 5 is an exemplary flowchart of a charging method based on a service chain policy according to an embodiment of the invention
  • FIG. 6 is an exemplary flowchart of a service node based charging method 600 in accordance with an embodiment of the present invention
  • FIG. 7 is a schematic structural diagram of hardware of a computer device according to an embodiment of the invention.
  • FIG. 8 is a schematic structural diagram of a charging triggering entity 800 according to an embodiment of the invention.
  • FIG. 9 is a schematic structural diagram of a service node 900 according to an embodiment of the invention.
  • FIG. 1 is a schematic diagram of a network architecture according to an embodiment of the invention.
  • SE1, SE2, and SEN are service nodes.
  • the policy and the charging and performing function (PCEF) entity or the traffic detection function (TDF) entity are added.
  • PCEF policy and the charging and performing function
  • TDF traffic detection function
  • the packet parsing function can be integrated, that is, the parsing of the application layer L7 and the parsing of the data stream L3/L4 can be supported; the PCEF or TDF entity can also integrate the functions controlled by the service chain policy.
  • the PCEF or TDF entity detects the data packet flowing through the 3GPP network, and after determining the service chain policy used by the data packet according to the identification information of the data packet, adding label information to the data packet, and the data packet after adding the label information flows through
  • the service node in the S(Gi)-LAN the service node parses the tag information of the data packet, determines the service chain policy used by the data packet, and performs the service chain control according to the determined service chain policy.
  • the charging trigger entity is a PCEF or a TDF in the network architecture shown in FIG. 1.
  • the charging method 200 will be described below by taking the PCEF as an example.
  • the PCEF entity acquires a correspondence between the identifier information of the data packet and the service chain policy.
  • the PCEF entity can obtain the corresponding relationship by the following: the PCRF entity sends the corresponding relationship to the PCEF entity; the PCEF entity obtains the corresponding relationship from the server according to the service chain policy identifier delivered by the PCRF entity; the administrator is in the PCEF The entity configures the correspondence.
  • the PCEF entity detects the identification information of the data packet after receiving the data packet, and determines, according to the correspondence, a service chain policy used by the data packet, where the service chain policy indicates that the data packet is processed.
  • Business node detects the identification information of the data packet after receiving the data packet, and determines, according to the correspondence, a service chain policy used by the data packet, where the service chain policy indicates that the data packet is processed.
  • the service chain policy further instructs the service node that processes the data packet to process the sequence of the data packet.
  • the processing of the data packet by the service node includes using the service provided by the service node for the data packet, such as performing firewall, load balancing, video acceleration, advertisement, compression decoding, and antivirus.
  • a service chain policy is SE1-SE3-SE6, which indicates that the service nodes SE1, SE3, and SE6 need to process the data packets, and the processing sequence is SE1, SE3, and SE6.
  • the identifier information of the data packet may be at least one of an application identifier (Application ID) and a service flow filter.
  • the service flow filter may be an IP quintuple, including a source IP address, a source port, a destination IP address, a destination port, and a transport layer protocol.
  • the PCEF entity further includes: adding, by the PCEF entity, label information of the service chain policy to the data packet, where the label information is used. Indicates the service node and sequence through which the data packet flows.
  • the tag information includes the identifier of the service node, which may be an IP address of the service node.
  • a service chain policy is SE1-SE3-SE6, and the label information of the service chain policy added by the PCEF may be 192.168.200.201-192.168.200.203-192.168.200.206, where 192.168.200.201, 192.168.200.203, 192.168.200.206
  • the IP addresses of the service nodes SE1, SE3, and SE6 are respectively indicated.
  • the tag information includes a routing table formed by a service node that processes the data packet.
  • the traffic splitter parses the label information of the data packet, and sends the data packet to the location according to the label information.
  • the first service node through which the data packet flows; after receiving the data packet, the first service node parses the label information of the data packet, and determines, according to the label information, that the data packet needs to be processed, such as parental control, Antivirus processing, etc., and sending the data packet to the second service node through which the data packet flows according to the tag information, and so on.
  • the label information may be 192.168.200.201-192.168.200.203-192.168.200.206.
  • the service nodes SE1, SE3, and SE6 provide compression, antivirus, and acceleration services, respectively.
  • the SE1 receives the data packet, parses the label information, and determines that it should be sent to the SE3.
  • SE3 receives the data packet, parses the label information, and determines that it should be sent to SE6.
  • SE3 sends the data packet to service node SE6.
  • the SE6 receives the data packet, parses the label information, and determines that the data packet is no longer sent to other service nodes. After the data packet is accelerated, the number is According to the package, the business chain strategy is completed.
  • Mode 2 The label information indicates all service nodes, and whether each service node processes the data packet.
  • the traffic splitter parses the label information of the data packet, and sends the data packet to the S(Gi) a first service node connected to the splitter in the LAN; after receiving the data packet, the first service node parses the label information of the data packet to determine whether it needs to process the data packet, and if so, Processing the data packet, such as parental control, anti-virus processing, etc., then sending the data packet to the second service node of the S(Gi)-LAN connected to the first service node, and so on; Otherwise, the data packet is not processed, and the data packet is sent to the second service node in the S(Gi)-LAN connected thereto.
  • SE1 there are six service nodes, SE1, SE2, SE3, SE4, SE5, and SE6, which provide compression, advertisement, antivirus, firewall, load balancing, and acceleration services.
  • the SE1 is connected to the splitter.
  • the service nodes that need to process the data packet are SE1, SE3, and SE6, and the label information may be 192.168.200.201(Y)-192.168.200.202(N)-192.168.200.203(Y)-192.168. .200.204(N)-192.168.200.205(N)-192.168.200.206(Y), where Y indicates that the service node is to process the data packet, and N indicates that the service node does not process the data packet.
  • the splitter parses the tag information, it sends the packet to SE1.
  • SE1 parses the tag information and determines that it should process the packet. After compressing the packet, it sends it to SE2. After receiving the data packet, SE2 parses the label information and determines that it does not insert an advertisement into the data packet, and then directly sends the data packet to SE3. After receiving the data packet, SE3 parses the label information and determines that it should process the data packet. After the data packet is disinfected, it is sent to SE4. The process is similar until the data packet flows to the last service node SE6. After the SE6 completes the above process, the data packet completes the service chain policy.
  • the PCEF entity generates usage information of the service chain policy, where usage information of the service chain policy is used for charging.
  • the usage information of the service chain policy includes attribute information of a service node that processes the data packet, and includes time information of using the service chain policy, and traffic information of a data packet that uses the service chain policy. At least one.
  • the attribute information of the service node may be configured in the PCEF before receiving the data packet.
  • the attribute information of the service node that processes the data packet includes: name information of the service node, service provider information of the service node, and identifier information used to uniquely identify the service node, the service At least one of address information of the node and type information of the service node.
  • the time information of using the service chain policy includes a start time of using the service chain policy; or includes starting time (Start) and end time (Stop) of using the service chain policy; or includes using The time period between the start time and the end time of the business chain policy.
  • the traffic information of the data packet using the service chain policy may be the sum of traffic of multiple data packets.
  • the PCEF entity requests the OCS to use the credit authorization of the service chain policy before generating the usage information of the service chain policy. After obtaining the credit authorization, the PCEF entity performs step S23.
  • the PCEF entity sends the usage information of the service chain policy to the charging system, so that the charging system performs charging according to the usage information of the service chain policy.
  • the PCEF sends the usage information of the service chain policy to the charging system, where the preset reporting condition includes reporting immediately, reporting in a specified time, or reporting when the specified capacity is reached.
  • the immediate report may be reported when the PCEF detects the first data packet of the service chain policy, for example, reporting the start time of using the service chain policy, or may report the PCEF to report the completion of the service chain policy, for example, reporting Use the start time and end time of the business chain strategy.
  • the report can be reported within a preset time, for example, it can be reported periodically within a preset time.
  • the report can be reported when the preset storage capacity is reached.
  • the charging data record CDR
  • the charging data record can be reported when the CDR capacity reaches the preset 2M.
  • the PCEF entity reports the usage information of the service chain policy to the OCS. If the charging mode is offline charging, the PCEF entity generates a CDR CDR according to the usage information of the service chain policy, and reports the generated CDR CDR to the OFCS.
  • the charging triggering entity is a shunt in the network architecture shown in FIG. 1.
  • the shunt is a unified gateway deployed on the Gi-LAN network.
  • the charging method 200 can be performed by a classifier, and the specific process includes (not shown):
  • the shunt acquires the correspondence from the PCEF or the TDF.
  • the traffic information of the data packet is detected after receiving the data packet, and the service chain policy used by the data packet is determined according to the corresponding relationship, where the service chain policy indicates a service for processing the data packet. node.
  • the service chain policy further indicates a sequence in which the service node that processes the data packet processes the data packet.
  • the traffic offloader notifies the PCEF entity of the service chain policy used by the data packet.
  • the PCEF entity requests the online charging system for the credit authorization of the user to use the service chain policy.
  • the PCEF entity instructs the flow splitter to generate usage information of the service chain policy.
  • the flow divider adds tag information of the service chain policy to the data packet.
  • the flow splitter generates usage information of the service chain policy, where the usage information of the service chain policy includes attribute information of a service node that processes the data packet, and time information that uses the service chain policy, At least one of the traffic information of the data packet using the service chain policy.
  • the attribute information of the service node may be configured in the splitter before receiving the data packet.
  • the power splitter can directly report the usage information of the service chain policy to the billing system; if there is no interface between the splitter and the billing system, the shunt The usage information of the service chain policy is reported to the charging system through the PCEF or the TDF entity.
  • a part of the feature description of the embodiment of the PCEF as the charging triggering entity is applicable to the embodiment of the traffic accounting device as a charging triggering entity, and details are not described herein.
  • the usage information of the service chain policy may include the parameters as shown in Table 1:
  • the Volume parameter indicates the sum of the data traffic of the same service chain policy obtained by the charging trigger entity.
  • the PCEF, the TDF, and the splitter will detect the time of using the data packet of the service chain policy for the first time, and determine the start time of using the service chain policy; After detecting the data packet using the service chain policy for the first time, if the data packet using the service chain policy is not detected within the set time threshold, the end time of the time threshold is determined. To use the end time of the business chain strategy.
  • the service chain policy used by the data packet is determined by using the identifier information carried by the data packet, and the service chain policy usage information used for charging is sent to the charging system, and the service chain policy is implemented. fee.
  • the usage information of the service chain policy includes attribute information of the service node that processes the data packet, and at least one of using time information of the service chain policy and traffic information of the data packet using the service chain policy, thereby increasing the charging.
  • FIG. 3 is an exemplary flow diagram of a service node based charging method 300 in accordance with an embodiment of the present invention.
  • the charging triggering entity is a service node in the network architecture shown in FIG. 1.
  • a charging interface between the traffic splitter and the charging system is added, and a reporting interface between each service node and the power splitter is added.
  • the PCEF entity obtains a correspondence between the identifier information of the data packet and the service chain policy.
  • the PCEF entity After receiving the data packet, the PCEF entity determines the service chain policy used by the data packet according to the corresponding relationship. For details, refer to the related description of S22 in the embodiment of FIG. 2.
  • the PCEF entity after determining the service chain policy used by the data packet, the PCEF entity requests the OCS to use the credit authorization of the service chain policy by using the service chain policy.
  • the PCEF entity adds the label information of the service chain policy to the header of the data packet.
  • label information refer to the related description of S22 in the embodiment of FIG. 2.
  • the PCEF entity sends the data packet with the tag information added to the splitter.
  • the offloader parses the tag information in the received data packet, and sends the data packet to a corresponding service node.
  • the traffic diverter sends the data packet to a first service node that processes the data packet, according to The routing table sequentially jumps to the next service node; if the tag information indicates all service nodes, and each service node processes the data packet, the traffic diverter sends the data packet to the first connection A business node.
  • the service node After receiving the data packet, the service node determines, according to the label information carried in the data packet, that the data packet needs to be processed.
  • the service node processes the data packet.
  • the service node After the processing of the data packet is completed, the service node sends the data packet to the next service node according to the tag information.
  • the service node generates usage information of the service node, where the service node uses information.
  • the attribute information of the service node further includes at least one of time information, event information, and traffic information of the service node processing the data packet.
  • the time information that the service node processes the data packet includes: a start time and an end time of the service node to perform processing.
  • the event information of the service node processing the data packet includes the number of times the service node performs processing, and may also include a start time of performing processing.
  • the traffic information of the service node processing the data packet includes traffic flowing into the service node and traffic flowing out of the service node, and may also include a start time of performing processing.
  • the service node sends the usage information of the service node to the charging system, so that the charging system performs charging according to the usage information of the service node.
  • the service node when the preset reporting condition is met, sends the usage information of the service node to the charging system, where the preset reporting condition includes reporting immediately, reporting in a specified time, or reporting the specified capacity.
  • the immediate reporting may be reported to the service node when the processing of the data packet is completed.
  • SE1 reports the usage information when processing the data packet.
  • SE3 reports its usage information when it finishes processing the data packet, and
  • SE6 reports its usage information when it finishes processing the data packet.
  • the report can be reported within a preset time, for example, it can be reported periodically within a preset time.
  • the report can be reported when the preset storage capacity is reached.
  • the charging data record CDR
  • the charging data record can be reported when the CDR capacity reaches the preset 2M.
  • the service node sends the usage information of the service node to the charging system through the traffic splitter.
  • the usage information of the service node further includes a service chain policy identifier
  • the traffic distributor associates the service node usage information generated by the service node that processes the data packet according to the service chain policy identifier, and then sends the information to the charging system.
  • the default reporting condition in the embodiment of FIG. 2 can be referred to, and details are not described herein again.
  • S31 to S34 can be executed by the TDF, and will not be described again here.
  • the charging mode may be different for different service nodes, such as time-based charging, event-based charging, and flow-based charging.
  • a service node such as antivirus, it can be charged according to the number of antivirus.
  • the usage information of the service node includes time information for processing the data packet; if charging by event, the usage information of the service node includes event information for processing the data packet; if the traffic is charged, the service node
  • the usage information contains traffic information that processes the packet.
  • the usage information of the service node reported by the service node may include parameters as shown in Table 2:
  • the usage information of the service node reported by the service node may include parameters as shown in Table 3:
  • the usage information of the service node reported by the service node may include parameters as shown in Table 4:
  • the SE1 adopts a time-based charging method
  • the SE2 adopts an event-based charging method
  • the SE3 adopts a data flow-based fee method.
  • the usage information after the shunt is associated and summarized may include the parameters as shown in Table 5:
  • the service node generates and reports its usage information to the charging system, and implements charging based on the service node.
  • the use of the information reported by the splitter can avoid establishing an interface between the charging system and each service node. Receiving usage information of each service node can reduce the pressure on the billing system.
  • FIG. 4 is a schematic diagram of another network architecture according to an embodiment of the invention.
  • SE1, SE2, and SEN are service nodes.
  • a Traffic Steering Support Function (TSSF) entity is added to implement the service chain policy control, and the TSSF entity integrates the service chain policy control and reporting function to implement the Gi-
  • the service chain control on the LAN side the TSSF entity is a Software Defined Network (SDN) controller (Controller), which can be implemented on the 3GPP side or on the S (Gi) LAN side.
  • SDN Software Defined Network
  • the charging interface between the TSSF and the OCS is defined as Gyt
  • the charging interface between the TSSF and the OFCS is defined as Gzt.
  • the interface between the SG Controller and the shunt on the Gi-LAN side is reused between the TSSF and the shunt (using the Openflow protocol).
  • the TSSF entity is added under the original PCC architecture to implement the service chain policy control. Compared with the network architecture of the embodiment of FIG. 1, the pressure of the PCEF or TDF entity can be alleviated.
  • FIG. 5 is an exemplary flow diagram of a service chain policy based charging method 500 in accordance with an embodiment of the present invention.
  • the charging triggering entity is a shunt in the network architecture shown in FIG.
  • the shunt obtains a correspondence between the identifier information of the data packet and the service chain policy.
  • the splitter obtains the correspondence from the TSSF.
  • the TSSF entity may obtain the corresponding relationship by the following: the PCRF entity sends the corresponding relationship to the TSSF entity; the TSSF entity obtains the correspondence from the server according to the service chain policy identifier delivered by the PCRF entity; the administrator is in the TSSF The entity configures the correspondence.
  • the switch receives the identification information of the data packet after receiving the data packet, and determines, according to the correspondence, a service chain policy used by the data packet, where the service chain policy indicates that the data packet is processed.
  • Business node The switch receives the identification information of the data packet after receiving the data packet, and determines, according to the correspondence, a service chain policy used by the data packet, where the service chain policy indicates that the data packet is processed.
  • the service chain policy further indicates a sequence in which the service node that processes the data packet processes the data packet.
  • the traffic offloader notifies the TSSF entity of the service chain policy used by the data packet.
  • the TSSF entity requests the OCS for the credit authorization of the user to use the service chain policy.
  • the instruction points The streamer generates usage information of the service chain policy.
  • the offloader adds label information of the service chain policy to the data packet.
  • the offloader generates usage information of the service chain policy, where the usage information of the service chain policy is used for charging.
  • the usage information of the service chain policy includes attribute information of a service node that processes the data packet, and at least one of using time information of the service chain policy and traffic information of a data packet using the service chain policy.
  • the offloader sends the usage information of the service chain policy to the charging system, so that the charging system performs charging processing according to the usage information of the service chain policy.
  • the traffic diverter sends the usage information of the service chain policy to the charging system, where the preset reporting conditions include reporting immediately, reporting in a specified time, or reporting when the specified capacity is reached. .
  • the offloader sends the usage information of the service chain policy to the charging system through the TSSF entity.
  • the usage information of the service chain policy generated by the traffic divider may include parameters as shown in Table 1.
  • the charging triggering entity is a service node in the network architecture shown in FIG. 4, and the interface between the service node and the TSSF reuses the SDN Controller and the service node.
  • the charging method 500 can be performed by a first service node connected to the shunt, and the specific process includes (not shown):
  • the first service node connected to the current collector obtains a correspondence between the data packet identification information and the service chain policy.
  • the first service node connected to the current collector obtains the correspondence from the TSSF.
  • the first service node connected to the current splitter detects the data packet after receiving the data packet And identifying, according to the correspondence, a service chain policy used by the data packet, where the service chain policy indicates a service node that processes the data packet.
  • the service chain policy further indicates a sequence in which the service node that processes the data packet processes the data packet.
  • the first service node connected to the splitter determines that it needs to process the data packet according to the service chain policy, and after processing, sends the data packet to the next service node connected thereto.
  • the next service node determines whether the data packet uses the service chain policy according to the identification information of the data packet, and if yes, determines that the data packet needs to be processed according to the service chain policy, and after the processing is completed, the data packet is processed. Send to the next service node connected to it; if not, the packet is not processed, and the packet is directly sent to the next service node connected to it.
  • the first service node connected to the splitter generates usage information of the service chain policy, where the usage information of the service chain policy includes attribute information of a service node that processes the data packet, and includes using At least one of time information of the service chain policy and traffic information of a data packet using the service chain policy.
  • the attribute information of the service node that processes the data packet may be configured in advance in the first service node.
  • the first service node connected to the current collector sends the usage information of the service chain policy to the charging system.
  • the usage information of the service chain policy is sent to the charging system when the preset reporting condition is met.
  • preset reporting condition refer to the related content in the embodiment of FIG. 2, and details are not described herein again.
  • the first service node connected to the splitter sends the usage information of the service chain policy to the charging system through the TSSF entity.
  • the service chain policy used by the data packet is determined by the identifier information carried by the data packet, and the service chain policy usage information for charging is sent to the charging system, so that the charging based on the service chain policy is implemented.
  • the usage information of the service chain policy includes attribute information of the service node that processes the data packet, and also includes the use of the service. At least one of time information of the chain policy and traffic information of the data packet using the service chain policy increases the flexibility of the charging system to charge based on the service chain policy.
  • FIG. 6 is an exemplary flow diagram of a service node based charging method 600 in accordance with an embodiment of the present invention.
  • the charging triggering entity is a service node in the network architecture shown in FIG.
  • an interface between the SDN Controller and the service node is reused between each service node and the TSSF entity.
  • the TSSF entity obtains a correspondence between the data packet identifier information and the service chain policy.
  • the TSSF entity sends the correspondence to the flow divider.
  • the shunt device detects the identifier information of the data packet after receiving the data packet, and determines, according to the correspondence, a service chain policy used by the data packet.
  • the traffic offloader notifies the TSSF entity of the service chain policy used by the data packet.
  • the TSSF entity requests the OCS for the credit authorization of the user to use the service chain policy.
  • the TSSF entity notifies the shunt after obtaining the credit authorization.
  • the offloader adds label information of the service chain policy to the data packet, and sends the data packet to a corresponding service node.
  • the traffic diverter sends the data packet to a first service node that processes the data packet, according to The routing table sequentially jumps to the next service node; if the tag information indicates all service nodes, and each service node processes the data packet, the traffic diverter sends the data packet to the first connection A business node.
  • the service node After receiving the data packet, the service node determines, according to the label information carried in the data packet, that the data packet needs to be processed.
  • the service node processes the data packet.
  • the service node After the processing of the data packet is completed, the service node sends the data packet to the next service node according to the tag information.
  • the service node generates usage information of the service node, where the usage information of the service node includes attribute information of the service node, and further includes time information, event information, and traffic information of the service node processing the data packet. At least one of them.
  • the service node sends the usage information of the service node to the charging system.
  • the service node when the preset reporting condition is met, sends the usage information of the service node to the charging system.
  • preset reporting conditions refer to the related description in the embodiment of FIG. 3, and details are not described herein again.
  • the service node may report the usage information of the service node by using the TSSF entity.
  • the usage information of the service node further includes a service chain policy identifier, and the TSSF associates the service node usage information generated by the service node that processes the data packet according to the service chain policy identifier, and then sends the information to the charging system.
  • the service node may also report the usage information of the service node through the traffic diverter, and the traffic distributor associates the service node usage information generated by the service node that processes the data packet according to the service chain policy identifier, and then sends the information to the charging system.
  • the service node-based charging is implemented by the service node generating and reporting its usage information to the charging system.
  • the use of information by the shunt or the TSSF can avoid establishing an interface between the charging system and each service node to receive usage information of each service node, and can also avoid the charging system.
  • the pressure on the billing system can be alleviated.
  • FIG. 3 and FIG. 6 describes a process of correlating service node usage information by the service chain policy identifier and then sending the information to the billing system for charging. This process increases the billing system to the service node that executes the same service chain policy.
  • the flexibility of the charging policy for example, the charging policy can be set to SE1 and SE3 when using the same business chain strategy when it is free for SE1.
  • the embodiment of the invention further provides a charging method based on a service node, and does not associate the service node usage information:
  • the service node receives the data packet, and determines to process the data packet according to the processing indication information carried by the data packet; the service node processes the data packet; and the service node sends the service node to the charging system.
  • the information, the usage information of the service node includes attribute information of the service node, and further includes at least one of time information, event information, and traffic information of the service node processing the data packet.
  • the label information in the embodiment of FIG. 3 and FIG. 6 includes the identifier of the service node, and the label information is a specific implementation manner of the processing indication information.
  • the charging system can directly perform charging according to the usage information reported by each service node, regardless of the service chain policy used by the service nodes.
  • the embodiment of the present invention further provides a charging method based on a service chain policy.
  • the TSSF sends the correspondence between the data packet identification information and the service chain policy to the service indicated in the service chain policy.
  • the service node determines to process the data packet according to the identification information carried by the data packet and the corresponding relationship. After the processing of the data packet is completed, the data packet is sent to the next service node that should be processed.
  • the first service node that processes the data packet and the last service node that processes the data packet generate usage information of the service chain policy, specifically, the attribute information of the service node that processes the data packet.
  • the service node sends the usage information of the service chain policy to the TSSF, and the TSSF performs association according to the service chain policy identifier, and then sends the information to the charging system for charging.
  • the first service node that processes the data packet detects the time when the data packet of the service chain policy is used for the first time, and determines to use the start of the service chain policy. Time; the last service node that processes the data packet determines the end time of processing using the last data packet of the service chain policy to determine the end time of using the service chain policy.
  • the correspondence between the data packet identifier information and the service chain policy fragment identifier sent by the TSSF is sent to the service node that processes the data packet, and the service node processes the data packet after the service node processes the reported service chain policy usage information.
  • Carry the service chain policy fragmentation identifier, and TSSF according to the service chain strategy The fragmentation identifier associates the service node usage information and then sends it to the billing system for billing.
  • the service chain policy identifier is 3, and the service chain policy is SE1-SE3-SE6, and the fragment identifier may be 3-1, 3-3, 3-6, and the correspondence between 3-1 and the packet identification information is It is sent to the service node SE1, and the corresponding relationship between the 3-3 and the packet identification information is sent to the service node SE3, and the corresponding relationship between the 3-6 and the packet identification information is sent to the service node SE6, and the TSSF can simultaneously deliver the information. Routing information to SE1, SE3, and SE6. After SE1, SE3, and SE6 report the service node usage information to the TSSF, the TSSF associates the service node usage information according to the service chain policy identifier 3 in 3-1, 3-3, and 3-6.
  • the service node determines whether to process the data packet according to the identifier information carried in the data packet, and the identifier information carried in the data packet is a specific implementation manner of processing the indication information.
  • the process of adding the tag information to the data packet by the shunt is avoided, and the pressure of the shunt is reduced.
  • the embodiment of the present invention further provides a service node-based charging method.
  • the TSSF sends the correspondence between the data packet identification information and the service chain policy to the service node indicated in the service chain policy.
  • the service node determines to process the data packet according to the identification information carried by the data packet and the corresponding relationship. After the processing of the data packet is completed, the data packet is sent to the next service node that should be processed.
  • Each service node that processes the data packet generates usage information of the service node, including attribute information of the service node and the service chain policy identifier, and at least one of time information, event information, and traffic information of the service node processing the data packet.
  • the generated usage information of the service node is sent to the TSSF, and the TSSF associates the usage information of the service node that processes the data packet according to the service chain policy identifier, and then sends the information to the charging system for charging.
  • the TSSF sends the data packet identification information and the service chain policy fragment identifier to the service node that processes the data packet, and after the service node processes the data packet, the reported service node usage information carries the service chain.
  • the policy fragmentation identifier is used by the TSSF to associate the service node usage information according to the service chain policy fragmentation identifier, and then send the information to the charging system for charging.
  • the service chain policy identifier is 3, and the service chain policy is SE1-SE3-SE6, and the fragment identifier is 3-1, 3-3, and 3-6, the correspondence between the 3-1 and the packet identification information is sent to the service node SE1, and the correspondence between the 3-3 and the packet identification information is sent to the service node.
  • SE3 the corresponding relationship between the 3-6 and the packet identification information is sent to the service node SE6, and the TSSF can simultaneously send routing information to SE1, SE3, and SE6.
  • SE1, SE3, and SE6 report the service node usage information to the TSSF
  • the TSSF associates the service node usage information according to the service chain policy identifier 3 in 3-1, 3-3, and 3-6.
  • the process of adding the tag information to the data packet by the shunt is avoided, and the pressure of the shunt is reduced.
  • the embodiment of the present invention further provides a computer device 700, as shown in FIG. 7, comprising: a processor 71, an input interface 72, an output interface 73, a memory 74, and a system bus 75; wherein:
  • the processor 71 is responsible for logical operations and processing.
  • the processor 71 reads the program in the memory 74, specifically:
  • the usage information of the service chain policy is sent to the charging system, wherein the usage information of the service chain policy is used for charging.
  • the memory 74 includes a memory and a hard disk, and can store data used by the processor 71 when performing operations.
  • the input interface 72 is for reading in data under the control of the processor 71, and the output interface 73 is outputting data under the control of the processor 71.
  • the bus architecture may include any number of interconnected buses and bridges, specifically linked by one or more processors represented by processor 71 and various circuits of memory and hard disks represented by memory 74.
  • the bus architecture can also link various other circuits such as peripherals, voltage regulators, and power management circuits, which are well known in the art and, therefore, will not be further described herein.
  • the charging triggering entity may be implemented in the form of the foregoing computer device.
  • the charging triggering entity may be specifically: a PCEF entity, a TDF entity, a traffic splitter, or a service node.
  • the processor 71 reads the program in the memory 74, specifically:
  • Receiving a data packet determining, according to the processing indication information carried in the data packet, processing the data packet; processing the data packet; and transmitting, by using an output interface 73, usage information of the service node to a charging system, where the service node
  • the usage information includes attribute information of the service node, and further includes at least one of time information, event information, and traffic information of the service node processing the data packet.
  • the computer device 700 described above can be a general purpose computer device or a special purpose computer device.
  • the computer device 700 can be a desktop computer, a portable computer, a network server, a personal digital assistant (PDA), a mobile phone, a tablet, a wireless terminal device, a communication device, an embedded device, or have the same FIG. A device of similar structure.
  • PDA personal digital assistant
  • Embodiments of the invention do not limit the type of computer device 700.
  • the network devices in FIG. 1 and FIG. 4, such as a PCEF, a TDF, a shunt, a service node, etc., may be the computer device 700 shown in FIG. 7, and the PCEF is a computer device 700.
  • the PCEF is a computer device 700.
  • One or more of the PCEF's memories are stored.
  • the PCEF can implement the software module based on the processor and the program code in the memory to implement a charging method based on the service chain policy.
  • the service node as the computer device 700 as an example, one or more software modules are stored in the memory of the service node.
  • the service node can implement the software module by using the processor and the program code in the memory to implement the service node-based charging method.
  • FIG. 8 is a schematic structural diagram of a charging triggering entity 800 according to an embodiment of the invention.
  • the billing triggering entity 800 includes a receiving module 802, a processing module 804, and a sending module 806.
  • the billing trigger entity 800 is the PCEF or TDF or shunt shown in Figure 1 or the shunt or service node shown in Figure 4.
  • a receiving module 802 configured to receive a data packet
  • the processing module 804 is configured to determine, according to the identifier information carried in the data packet, a service chain policy used by the data packet, where the service chain policy indicates a service node that processes the data packet;
  • the sending module 806 is configured to send usage information of the service chain policy to the charging system, where the usage information of the service chain policy is used for charging.
  • the receiving module 802 is further configured to obtain a correspondence between the identifier information and the service chain policy, where the processing module 804 is further configured to determine, according to the correspondence, the use of the data packet.
  • Business chain strategy is further configured to determine, according to the correspondence, the use of the data packet.
  • the usage information of the service chain policy includes attribute information of the service node that processes the data packet, and at least one of using time information of the service chain policy and traffic information of the data packet using the service chain policy.
  • attribute information of the service node that processes the data packet and at least one of using time information of the service chain policy and traffic information of the data packet using the service chain policy.
  • the sending module 806 sends the usage information of the service chain policy to the charging system, where the preset reporting conditions include immediate reporting, reporting within a specified time, or meeting the requirements. Reported when capacity is available.
  • the service chain policy further indicates a sequence in which the service node that processes the data packet processes the data packet.
  • the receiving module 802, the processing module 804, and the sending module 806 are presented in the form of functional modules.
  • a “module” herein may refer to an application-specific integrated circuit (ASIC), circuitry, a processor and memory that executes one or more software or firmware programs, integrated logic circuitry, and/or other functions that provide the functionality described above. Device.
  • ASIC application-specific integrated circuit
  • the receiving module 802 can be implemented by a processor, a memory, and an input interface of the computer device 700.
  • the processing module 804 can be implemented by a processor and a memory of the computer device 700.
  • Transmit module 806 can pass through the processor, memory, and output interface of computer device 700.
  • FIG. 9 is a schematic structural diagram of a service node 900 according to an embodiment of the invention.
  • the service node 900 includes a receiving module 902, a processing module 904, and a transmitting module 906.
  • the service node 900 is the service node shown in FIG. 1 or the service node shown in FIG.
  • the receiving module 902 is configured to receive a data packet.
  • the processing module 904 is configured to determine, according to the processing indication information carried by the data packet, processing the data packet; and processing the data packet;
  • the sending module 906 is configured to send the usage information of the service node to the charging system, where the usage information of the service node includes attribute information of the service node, and further includes time information that the service node processes the data packet, At least one of event information and traffic information.
  • the processing indication information includes an identifier of the service node or identifier information of the data packet.
  • the receiving module 902 is further configured to acquire the identifier information and the service, before the receiving module 902 receives the data packet.
  • the processing module 904 is further configured to determine to process the data packet according to the identifier information carried by the data packet and the correspondence relationship.
  • the sending module 906 is configured to send usage information of the service node to the charging system by using a splitter.
  • the data packet further carries a service chain policy identifier
  • the sending module 906 is configured to send usage information of the service node to the charging system by using a TSSF, where the usage information of the service node further includes the A service chain policy identifier, where the service chain policy identifier is used to associate usage information of a plurality of the service nodes.
  • the sending module 906 sends the usage information of the service node to the charging system, where the preset reporting conditions include immediate reporting, reporting within a specified time, or reaching a specified capacity.
  • the preset reporting conditions include immediate reporting, reporting within a specified time, or reaching a specified capacity.
  • the receiving module 902, the processing module 904, and the transmitting module 906 are presented in the form of functional modules.
  • a “module” herein may refer to an application-specific integrated circuit (ASIC), circuitry, a processor and memory that executes one or more software or firmware programs, integrated logic circuitry, and/or other functions that provide the functionality described above. Device.
  • ASIC application-specific integrated circuit
  • the receiving module 902 can be implemented by a processor, a memory, and an input interface of the computer device 700.
  • the processing module 904 can be implemented by a processor and a memory of the computer device 700.
  • Transmit module 906 can pass through the processor, memory, and output interface of computer device 700.
  • embodiments of the present invention can be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment, or a combination of software and hardware. Moreover, the invention can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) including computer usable program code.
  • computer-usable storage media including but not limited to disk storage, CD-ROM, optical storage, etc.
  • the present invention is directed to a method, apparatus (system), and computer program product according to an embodiment of the present invention.
  • These computer program instructions can be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing device to produce a machine for the execution of instructions for execution by a processor of a computer or other programmable data processing device.
  • the computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture comprising the instruction device.
  • the apparatus implements the functions specified in one or more blocks of a flow or a flow and/or block diagram of the flowchart.
  • These computer program instructions can also be loaded onto a computer or other programmable data processing device such that a series of operational steps are performed on a computer or other programmable device to produce computer-implemented processing for execution on a computer or other programmable device.
  • the instructions provide steps for implementing the functions specified in one or more of the flow or in a block or blocks of a flow diagram.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Accounting & Taxation (AREA)
  • Business, Economics & Management (AREA)
  • Quality & Reliability (AREA)
  • Computing Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Hardware Design (AREA)
  • Power Engineering (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

本发明公开了一种计费方法和装置，解决了现有技术中关于如何基于业务链策略进行计费，目前还没有解决方案的问题。方法包括：计费触发实体接收到数据包后，根据所述数据包中携带的标识信息，确定出所述数据包使用的业务链策略，所述业务链策略指示对所述数据包进行处理的业务节点；所述计费触发实体向计费系统发送所述业务链策略的使用信息，其中，所述业务链策略的使用信息用于计费。

Description

一种计费方法和装置
本申请要求于2016年2月29日提交中国专利局、申请号为201610113042.5，发明名称为“一种计费方法和装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本发明涉及通信技术领域，特别涉及一种计费方法和装置。
背景技术
为了解决服务质量(Quality of Service，简称QoS)门控和基于流计费等问题，提供更好的基于流的计费和策略控制，第三代合作伙伴计划(The 3rd Generation Partnership，3GPP)在版本7(R7)中提出策略计费控制(Policy and Charging Control，PCC)机制，通过该机制可以使网络检测到不同的业务流，并针对业务流实现QoS控制，计费统计等需求。3GPP在版本12中增强了PCC架构基于应用的计费和策略控制。
业务链(Service Chain或者Traffic Service Steering)是指数据流在网络中传递时，按照业务逻辑所要求的既定顺序，依次经过SGi/Gi-LAN各式业务节点(Service Enabler，SE)，其中，SE可以是运营商部署的增值业务，也可以是第三方业务提供者提供的业务，如防火墙、负载均衡(Load Balance，LB)、视频加速，广告、压缩解码、杀毒等。为了配合长期演进(Long Term Evolution，简称LTE)时代移动互联网业务的高速发展和用户灵活的业务需求，运营商希望能够提供一种策略，可以跟据不同的业务特性、用户订阅信息、无线接入网(Radio Access Network，简称RAN)的网络状态、网络拥塞信息等，来实现Gi-LAN侧的业务链控制，以优化移动网络业务的数据流经3GPP网络到Gi-LAN网络的效率。业务链策略(Traffic Steering Policy)应运而生。
如何基于业务链策略进行计费，目前还没有解决方案。
发明内容
本发明实施例提供了一种计费方法和装置，解决了现有技术中关于如何基于业务链策略进行计费，目前还没有解决方案的问题。
第一方面，提供了一种计费方法，包括：计费触发实体接收到数据包后，根据数据包中携带的标识信息，确定出数据包使用的业务链策略，其中，业务链策略指示对数据包进行处理的业务节点；计费触发实体向计费系统发送业务链策略的使用信息，其中，业务链策略的使用信息用于计费。
通过数据包携带的标识信息确定其使用的业务链策略，并向计费系统发送用于计费的业务链策略使用信息，实现了基于业务链策略进行计费。
结合第一方面的实现方式，在第一方面第一种可能的实现方式中，在计费触发实体根据数据包中携带的标识信息，确定出数据包使用的业务链策略之前，计费触发实体获取标识信息与业务链策略的对应关系；则计费触发实体根据数据包中携带的标识信息，确定出数据包使用的业务链策略，包括：计费触发实体根据对应关系，确定出数据包使用的业务链策略。
由于配置了数据包的标识信息与该数据包所使用的业务链策略的对应关系，使得计费触发实体可以根据所述对应关系，确定出所述数据包使用的业务链策略。
结合第一方面、第一方面的第一种可能的实现方式，在第二种可能实现的方式中，业务链策略的使用信息包括处理数据包的业务节点的属性信息，还包括使用业务链策略的时间信息、使用业务链策略的数据包的流量信息中的至少一种。
这样增加了计费系统基于业务链策略计费的灵活性。
结合第一方面、第一方面的第一种至第二种可能的实现方式，在第三种可能实现的方式中，计费触发实体为策略及计费执行功能PCEF实体、业务检测功能TDF实体、分流器或业务节点。
将不同的网元作为计费触发实体，能够按照实际需求合理的分配网络资源。
结合第一方面、第一方面的第一种至第三种可能的实现方式，在第四种可 能实现的方式中，当满足预设的上报条件时，计费触发实体向计费系统发送业务链策略的使用信息，其中，预设的上报条件包括立即上报、规定时间内上报或达到规定容量时上报。
结合第一方面、第一方面的第一种至第四种可能的实现方式，在第五种可能实现的方式中，业务链策略还指示对数据包进行处理的业务节点处理该数据包的顺序。
第二方面，提供了一种计费方法，包括：业务节点接收数据包，根据数据包携带的处理指示信息确定对其进行处理；业务节点处理数据包；业务节点向计费系统发送业务节点的使用信息，其中，业务节点的使用信息包括业务节点的属性信息，还包括业务节点处理数据包的时间信息、事件信息、流量信息中的至少一种。
通过业务节点生成并向计费系统上报其使用信息，实现了基于业务节点的计费。
业务节点处理数据包的事件信息包括业务节点执行处理的次数。
结合第二方面的实现方式，在第二方面第一种可能的实现方式中，处理指示信息包括业务节点的标识或者数据包的标识信息。
结合第二方面、第二方面的第一种可能的实现方式，在第二种可能实现的方式中，当处理指示信息包括数据包的标识信息时，在接收数据包之前，业务节点获取标识信息与业务链策略的对应关系，则根据数据包携带的处理指示信息确定对数据包进行处理包括：根据数据包携带的标识信息以及对应关系确定对数据包进行处理。
结合第二方面、第二方面的第一种至第二种可能的实现方式，在第三种可能实现的方式中，业务节点通过分流器向计费系统发送业务节点的使用信息。
在有多个业务节点的情况下，通过分流器上报使用信息可以避免建立计费系统与各业务节点之间的接口来接收各业务节点的使用信息，能够减轻计费系统的压力。
结合第二方面、第二方面的第一种至第三种可能的实现方式，在第四种可 能实现的方式中，数据包还携带业务链策略标识，业务节点通过TSSF向计费系统发送业务节点的使用信息，其中，业务节点的使用信息还包括业务链策略标识，业务链策略标识用于关联多个业务节点。
在有多个业务节点的情况下，通过业务链策略标识将各业务节点的使用信息进行关联，能够增加计费系统进行计费的灵活性，例如对使用某一业务链策略的用户优惠计费。
结合第二方面、第二方面的第一种至第四种可能的实现方式，在第五种可能实现的方式中，当满足预设的上报条件时，业务节点向计费系统发送业务节点的使用信息，其中，预设的上报条件包括立即上报、规定时间内上报或达到规定容量时上报。
第三方面，提供了一种计费装置，包括：处理器、输入接口、输出接口、以及存储器，其中：所述处理器读取所述存储器中的程序，执行第一方面所述的方法。
第四方面，提供了一种计费装置，包括：处理器、输入接口、输出接口、以及存储器，其中：所述处理器读取所述存储器中的程序，执行第二方面所述的方法。
第五方面，提供了一种计算机可读存储介质，其中存储有可执行的程序代码，该程序代码用以实现第一方面所述的方法。
第六方面，提供了一种计算机可读存储介质，其中存储有可执行的程序代码，该程序代码用以实现第二方面所述的方法。
第七方面，提供了一种计费装置，包含用于执行第一方面中的方法的模块。
第八方面，提供了一种计费装置，包含用于执行第二方面中的方法的模块。
根据本发明实施例提供的计费方法，通过根据数据包携带的标识信息确定其使用的业务链策略，并向计费系统发送用于计费的业务链策略使用信息，实现了基于业务链策略进行计费。通过业务节点生成并向计费系统上报其使用信息，实现了基于业务节点的计费。
附图说明
图1为本发明一实施例应用的一种网络架构示意图；
图2为依据本发明一实施例的基于业务链策略的计费方法200的示范性流程图；
图3为依据本发明一实施例的基于业务节点的计费方法300的示范性流程图；
图4为本发明一实施例应用的另一种网络架构示意图；
图5为依据本发明一实施例的基于业务链策略的计费方法500的示范性流程图；
图6为依据本发明一实施例的基于业务节点的计费方法600的示范性流程图；
图7为依据本发明一实施例的计算机设备的硬件结构示意图；
图8是依据本发明一实施例的计费触发实体800的结构示意图；
图9是依据本发明一实施例的业务节点900的结构示意图。
具体实施方式
为使本发明实施例的目的、技术方案和优点更加清楚，下面将结合本发明实施例中的附图，对本发明实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例是本发明一部分实施例，而不是全部的实施例。基于本发明中的实施例，本领域普通技术人员在没有作出创造性劳动前提下所获得的所有其他实施例，都属于本发明保护的范围。
下面结合说明书附图对本发明实施例作进一步详细描述。应当理解，此处所描述的实施例仅用于说明和解释本发明，并不用于限定本发明。
图1是依据本发明一实施例的一种网络架构示意图。图中SE1、SE2、SEN为业务节点，本发明实施例中，在策略及计费执行功能(Policy and Charging Enforcement Function，简称PCEF)实体或业务检测功能(Traffic Detection Function，简称TDF)实体上增加执行业务链策略的功能，PCEF或TDF实体 可以集成数据包解析功能，即可以支持应用层L7的解析和数据流L3/L4的解析；PCEF或TDF实体还可以集成业务链策略的控制的功能。PCEF或TDF实体检测流经3GPP网络中的数据包，在根据数据包的标识信息确定出该数据包使用的业务链策略后，给该数据包添加标签信息，添加标签信息后的数据包流经S(Gi)-LAN中的业务节点，业务节点解析数据包的标签信息，确定出该数据包使用的业务链策略，并根据确定出的业务链策略执行业务链控制。图中PCEF实体与在线计费系统(Online Charging System，OCS)、离线计费系统(Offline Charging System，简称OFCS)之间的交互仍重用PCEF实体的Gy接口和Gz接口，TDF实体与OCS、OFCS之间的交互仍重用TDF实体现有的Gyn接口和Gzn接口。这种架构下的实现方式无需引入新的网元，在具体实现过程中更易操作。
图2是依据本发明一实施例的基于业务链策略的计费方法200的示范性流程图。在具体实现过程中，计费触发实体为图1所示的网络架构中的PCEF或TDF。下面以PCEF为例对计费方法200进行说明。
S21、PCEF实体获取数据包标识信息与业务链策略的对应关系。
具体的，PCEF实体可以通过以下方式来获取该对应关系：PCRF实体下发该对应关系到PCEF实体；PCEF实体根据PCRF实体下发的业务链策略标识，从服务器获取该对应关系；管理员在PCEF实体配置该对应关系。
S22、PCEF实体接收到数据包后检测数据包的标识信息，根据所述对应关系，确定出所述数据包使用的业务链策略，其中，所述业务链策略指示对所述数据包进行处理的业务节点。
可选的，业务链策略还指示对所述数据包进行处理的业务节点处理所述数据包的顺序。
业务节点对数据包进行处理包括对数据包使用该业务节点提供的业务，例如执行防火墙、负载均衡、视频加速，广告、压缩解码、杀毒等功能。
例如，一个业务链策略为SE1-SE3-SE6，表示业务节点SE1、SE3、SE6需要对数据包进行处理，进行处理的顺序为SE1、SE3、SE6。
其中，数据包的标识信息可以为应用标识(Application ID)和业务流过滤器(service flow filter)中的至少一种。例如，业务流过滤器可以为IP五元组，具体包括源IP地址、源端口、目的IP地址、目的端口、和传输层协议。
可选的，PCEF实体根据数据包的标识信息，确定出数据包使用的业务链策略之后，还包括：PCEF实体在所述数据包中添加该业务链策略的标签信息，所述标签信息用于指示所述数据包流经的业务节点及顺序。
标签信息包括业务节点的标识，具体可以为业务节点的IP地址。例如，一个业务链策略为SE1-SE3-SE6，PCEF添加的该业务链策略的标签信息可以为192.168.200.201-192.168.200.203-192.168.200.206，其中，192.168.200.201、192.168.200.203、192.168.200.206分别表示业务节点SE1、SE3、SE6的IP地址。
其中，所述标签信息包括以下两种可选的实现方式：
方式1、所述标签信息中包括对所述数据包进行处理的业务节点形成的路由表。
该方式下，所述数据包由3GPP网络流经到S(Gi)-LAN中后，先流入分流器；分流器解析所述数据包的标签信息，根据标签信息将所述数据包发送到所述数据包所流经的第一个业务节点；第一个业务节点接收到所述数据包后，解析数据包的标签信息，根据标签信息确定需要对所述数据包进行处理，如家长控制、杀毒处理等，并根据标签信息将所述数据包发送到所述数据包所流经的第二个业务节点，依次类推。例如，对数据包进行处理的业务节点为SE1、SE3、SE6，则标签信息可为192.168.200.201-192.168.200.203-192.168.200.206。业务节点SE1、SE3、SE6分别提供压缩、杀毒、加速业务。分流器解析标签信息后，将数据包发送至业务节点SE1，SE1接收到数据包，解析标签信息，确定应将其发送至SE3，则在对数据包进行压缩后，SE1将数据包发送至业务节点SE3。SE3接收到数据包，解析标签信息，确定应将其发送至SE6，则在对数据包进行杀毒后，SE3将数据包发送至业务节点SE6。SE6接收到数据包，解析标签信息，确定不再将数据包发送至其他业务节点，在对数据包进行加速后，该数 据包执行完毕业务链策略。
方式2、所述标签信息指示所有业务节点，以及每个业务节点是否对所述数据包进行处理。
该方式下，所述数据包由3GPP网络流经到S(Gi)-LAN中后，先流入分流器；分流器解析所述数据包的标签信息，将所述数据包发送到S(Gi)-LAN中与分流器连接的第一个业务节点；第一个业务节点接收到所述数据包后，解析数据包的标签信息，确定自身是否需要对所述数据包进行处理，若是，则对所述数据包进行处理，例如家长控制、杀毒处理等，之后将所述数据包发送到的S(Gi)-LAN中与该第一业务节点连接的第二个业务节点，以此类推；若否，则不对数据包进行处理，将所述数据包发送到的S(Gi)-LAN中与之连接的第二个业务节点。例如，共有SE1、SE2、SE3、SE4、SE5、SE6六个业务节点，分别提供压缩、广告、杀毒、防火墙、负载均衡、加速业务。SE1与分流器相连，其中需要对数据包进行处理的业务节点为SE1、SE3、SE6，则标签信息可以为192.168.200.201(Y)-192.168.200.202(N)-192.168.200.203(Y)-192.168.200.204(N)-192.168.200.205(N)-192.168.200.206(Y)，其中Y表示业务节点要对数据包进行处理，N表示业务节点不对数据包进行处理。则分流器在解析标签信息后，将数据包发送至SE1，SE1解析标签信息，确定其应对数据包进行处理，则在对数据包进行压缩后，将其发送至SE2。SE2接收到数据包后，解析标签信息，确定其不对数据包插入广告，则直接将数据包发送至SE3。SE3接收到数据包后，解析标签信息，确定其应对数据包进行处理，在对数据包进行杀毒后，将其发送至SE4。此后过程类似，直至数据包流至最后一个业务节点SE6，SE6在完成上述过程后，该数据包执行完毕业务链策略。
S23、PCEF实体生成所述业务链策略的使用信息，所述业务链策略的使用信息用于计费。
具体的，所述业务链策略的使用信息包括处理所述数据包的业务节点的属性信息，还包括使用所述业务链策略的时间信息、使用所述业务链策略的数据包的流量信息中的至少一种。
可选的，业务节点的属性信息可以在接收数据包之前配置在PCEF中。
可选的，处理所述数据包的业务节点的属性信息包括：所述业务节点的名称信息、所述业务节点的服务提供商信息、用于唯一标识所述业务节点的标识信息、所述业务节点的地址信息、以及所述业务节点的类型信息中的至少一种。
可选的，使用所述业务链策略的时间信息包括使用所述业务链策略的起始时间；或者包括使用所述业务链策略的起始时间(Start)和结束时间(Stop)；或者包括使用所述业务链策略的起始时间与结束时间之间的时间段。
当多个数据包使用相同业务链策略时，所述使用业务链策略的数据包的流量信息可以为多个数据包的流量总和。
可选的，PCEF实体在生成业务链策略的使用信息之前，向OCS请求用户使用所述业务链策略的信用授权。PCEF实体在获取到信用授权后，执行步骤S23。
S24、PCEF实体向计费系统发送所述业务链策略的使用信息，以使所述计费系统根据所述业务链策略的使用信息进行计费。
可选的，当满足预设的上报条件时，PCEF向计费系统发送所述业务链策略的使用信息，所述预设的上报条件包括立即上报、规定时间内上报或达到规定容量时上报。
具体的，立即上报可以为PCEF在检测到使用业务链策略的第一个数据包时上报，例如上报使用业务链策略的起始时间；或者可以为PCEF判断业务链策略执行完毕时上报，例如上报使用业务链策略的起始时间和结束时间。
规定时间内上报可以为在预设时间内上报，例如可以为在预设时间内定时上报。
达到规定容量时上报可以为达到预设存储容量时上报，例如可以为计费数据记录(Charging DataRecord，CDR)话单容量达到预设的2M时上报。
具体地，若计费方式为在线计费，则PCEF实体将所述业务链策略的使用信息上报给OCS。若计费方式为离线计费，则PCEF实体根据所述业务链策略的使用信息生成CDR话单，并将生成的CDR话单上报给OFCS。
在另一种可能的实现方式中，计费触发实体为图1所示网络架构中的分流器。分流器是部署在Gi-LAN网络的统一出入口。计费方法200可以由分流器(Classifier)执行，具体过程包括(图中未示出)：
S21’、分流器获取数据包标识信息与业务链策略的对应关系。
具体的，分流器从PCEF或TDF获取该对应关系。
S22’、分流器接收到数据包后检测数据包的标识信息，根据所述对应关系，确定出数据包使用的业务链策略，其中，所述业务链策略指示对所述数据包进行处理的业务节点。
可选的，所述业务链策略还指示对所述数据包进行处理的业务节点处理所述数据包的顺序。
可选的，分流器根据所述对应关系，确定出数据包使用的业务链策略之后，通知PCEF实体所述数据包使用的业务链策略。PCEF实体向在线计费系统请求用户使用所述业务链策略的信用授权。PCEF实体在获取到信用授权后，指示分流器生成所述业务链策略的使用信息。
S23’、分流器在所述数据包中添加该业务链策略的标签信息。
前文S22中已对标签信息的实现方式进行说明，此处不再赘述。
S24’、分流器生成所述业务链策略的使用信息，其中，所述业务链策略的使用信息包括处理所述数据包的业务节点的属性信息，还包括使用所述业务链策略的时间信息、使用所述业务链策略的数据包的流量信息中的至少一种。
处理数据包的业务节点的属性信息、使用业务链策略的时间信息、使用业务链策略的数据包的流量信息的详细内容前文已经说明，此处不再赘述。
可选的，业务节点的属性信息可以在接收数据包之前配置在分流器中。
进一步，若分流器与计费系统之间存在接口，则分流器可将所述业务链策略的使用信息直接上报给计费系统；若分流器与计费系统之间不存在接口，则分流器通过PCEF或TDF实体，将所述业务链策略的使用信息上报给计费系统。
PCEF作为计费触发实体的实施例的部分特征描述适用于分流器作为计费触发实体的实施例，在此不再赘述。
在一种可能的实现方式中，业务链策略的使用信息中可以包含如表1所示的参数：
表1
Figure PCTCN2016111531-appb-000001
其中，Volume参数表示计费触发实体统计得到的执行相同业务链策略的数据流量总和。
在实施中，作为一种可能的实现方式，PCEF、TDF、分流器将首次检测到使用所述业务链策略的数据包的时刻，确定为使用所述业务链策略的起始时间；所述计费触发实体在首次检测到使用所述业务链策略的数据包之后，若在设定的时间阈值内，未检测到使用所述业务链策略的数据包，将所述时间阈值的结束时刻，确定为使用所述业务链策略的结束时间。
根据本发明实施例提供的技术方案，通过数据包携带的标识信息确定其使用的业务链策略，并向计费系统发送用于计费的业务链策略使用信息，实现了基于业务链策略进行计费。同时，业务链策略的使用信息包括处理数据包的业务节点的属性信息，还包括使用业务链策略的时间信息、使用业务链策略的数据包的流量信息中的至少一种，这样增加了计费系统基于业务链策略计费的灵 活性。
图3是依据本发明一实施例的基于业务节点的计费方法300的示范性流程图。在具体实现过程中，计费触发实体为图1所示网络架构中的业务节点。本实施例中，新增分流器与计费系统之间的计费接口；新增各业务节点与分流器之间的上报接口。
S31、PCEF实体获取数据包标识信息与业务链策略的对应关系。
获取方式在图2实施例S21中已经说明，此处不再赘述。
S32、PCEF实体接收到数据包后，根据所述对应关系，确定出所述数据包使用的业务链策略，具体参见图2实施例中S22的相关描述。
可选的，PCEF实体根据所述对应关系，确定出所述数据包使用的业务链策略后，向OCS请求用户使用所述业务链策略的信用授权。
S33、PCEF实体在所述数据包的报头中添加该业务链策略的标签信息，其中，标签信息请参见图2实施例中S22的相关描述。
S34、PCEF实体将添加了标签信息的数据包发送到分流器。
S35、分流器解析接收到的数据包中的标签信息，将所述数据包发送到相应的业务节点。
具体的，若所述标签信息中包括对所述数据包进行处理的业务节点形成的路由表，则分流器将所述数据包发送到对所述数据包进行处理的第一个业务节点，根据路由表依次跳转到下一个业务节点；若所述标签信息指示所有业务节点，以及每个业务节点是否对所述数据包进行处理，则分流器将所述数据包发送到与其相连接的第一个业务节点。
S36、业务节点在接收到数据包后，根据所述数据包携带的标签信息确定出需要对所述数据包进行处理。
S37、业务节点处理所述数据包。
在完成对数据包的处理后，业务节点根据标签信息将所述数据包发送到下一个业务节点。
S38、业务节点生成业务节点的使用信息，其中，所述业务节点的使用信息 包括所述业务节点的属性信息，还包括所述业务节点处理所述数据包的时间信息、事件信息、流量信息中的至少一种。
可选的，业务节点处理所述数据包的时间信息包括：该业务节点执行处理的起始时间和结束时间。业务节点处理所述数据包的事件信息包括该业务节点执行处理的次数，还可以包括执行处理的起始时间。业务节点处理所述数据包的流量信息包括流入该业务节点的流量和流出该业务节点的流量，还可以包括执行处理的起始时间。
S39、业务节点将所述业务节点的使用信息发送给计费系统，以使计费系统根据业务节点的使用信息进行计费。
可选的，当满足预设的上报条件时，业务节点向计费系统发送业务节点的使用信息，所述预设的上报条件包括立即上报、规定时间内上报或达到规定容量时上报。
具体的，立即上报可以为业务节点在完成对数据包的处理时上报，例如一个业务链策略包含SE1、SE3、SE6对数据包进行处理，则SE1在完成对数据包的处理时上报其使用信息，SE3在完成对数据包的处理时上报其使用信息，SE6在完成对数据包的处理时上报其使用信息。
规定时间内上报可以为在预设时间内上报，例如可以为在预设时间内定时上报。
达到规定容量时上报可以为达到预设存储容量时上报，例如可以为计费数据记录(Charging DataRecord，CDR)话单容量达到预设的2M时上报。
可选的，业务节点通过分流器向计费系统发送业务节点的使用信息。
可选的，业务节点的使用信息还包括业务链策略标识，分流器根据业务链策略标识，将对所述数据包进行处理的业务节点生成的业务节点使用信息进行关联，之后发送给计费系统。
分流器向计费系统发送业务节点的使用信息的上报时机可以参考图2实施例中的预设上报条件，此处不再赘述。
S31至S34可由TDF执行，此处不再赘述。
在实际应用中，针对不同的业务节点，计费模式可能不同，如可按时间计费、按事件计费、按流量计费等。例如，一个业务节点的功能是杀毒，则可以按照杀毒次数来计费。若按时间计费，则业务节点的使用信息包含处理数据包的时间信息；若按事件计费，则业务节点的使用信息包含处理数据包的事件信息；若按流量计费，则业务节点的使用信息包含处理数据包的流量信息。
当业务节点按时长计费时，在一种实现方式中，该业务节点上报的业务节点的使用信息可以包含如表2所示的参数：
表2
Figure PCTCN2016111531-appb-000002
当业务节点按事件计费时，在一种实现方式中，该业务节点上报的业务节点的使用信息可以包含如表3所示的参数：
表3
Figure PCTCN2016111531-appb-000003
Figure PCTCN2016111531-appb-000004
当业务节点按流量计费时，在一种实现方式中，该业务节点上报的业务节点的使用信息可以包含如表4所示的参数：
表4
Figure PCTCN2016111531-appb-000005
在一种实现方式中，若对数据包进行处理的业务节点中，SE1采用按时长计费的方式，SE2采用按事件计费的方式，SE3采用按数据流量计费的方式，
则分流器进行关联汇总后的使用信息可以包含如表5所示的参数：
表5
Figure PCTCN2016111531-appb-000006
Figure PCTCN2016111531-appb-000007
根据本发明实施例提供的技术方案，通过业务节点生成并向计费系统上报其使用信息，实现了基于业务节点的计费。同时，在有多个业务节点的情况下，通过分流器上报使用信息可以避免建立计费系统与各业务节点之间的接口来接 收各业务节点的使用信息，能够减轻计费系统的压力。
图4是依据本发明一实施例的另一种网络架构示意图。图中SE1、SE2、SEN为业务节点。本发明实施例的方案，在原有PCC架构中，新增业务链支撑功能(Traffic Steering Support Function，TSSF)实体来实现业务链策略控制，TSSF实体集成业务链策略控制和上报功能，以实现Gi-LAN侧的业务链控制，TSSF实体作为软件定义网络(Software Defined Network，简称SDN)控制器(Controller)，可以在3GPP侧实现，也可以在S(Gi)LAN侧实现。图中新增了TSSF与计费系统之间的计费接口，如TSSF与OCS之间的计费接口定义为Gyt，TSSF与OFCS之间的计费接口定义为Gzt。TSSF与分流器之间重用Gi-LAN侧SDN Controller和分流器之间的接口(采用Openflow协议)。在原有PCC架构下新增TSSF实体来实现业务链策略控制，相比于图1实施例的网络架构，能够减轻PCEF或TDF实体的压力。
图5是依据本发明一实施例的基于业务链策略的计费方法500的示范性流程图。在具体实现过程中，计费触发实体为图4所示网络架构中的分流器。
S51、分流器获取数据包标识信息与业务链策略的对应关系。
可选的，分流器从TSSF获取该对应关系。
具体的，TSSF实体可以通过以下方式来获取该对应关系：PCRF实体下发该对应关系到TSSF实体；TSSF实体根据PCRF实体下发的业务链策略标识，从服务器获取该对应关系；管理员在TSSF实体配置该对应关系。
S52、分流器接收到数据包后检测数据包的标识信息，根据所述对应关系，确定出所述数据包使用的业务链策略，其中，所述业务链策略指示对所述数据包进行处理的业务节点。
可选的，所述业务链策略还指示对所述数据包进行处理的业务节点处理所述数据包的顺序。
可选的，分流器根据所述对应关系，确定出所述数据包使用的业务链策略之后，通知TSSF实体所述数据包使用的业务链策略。TSSF实体向OCS请求用户使用所述业务链策略的信用授权。TSSF实体在获取到信用授权后，指示分 流器生成所述业务链策略的使用信息。
S53、分流器在所述数据包中添加该业务链策略的标签信息。
前文S22中已对标签信息的实现方式进行说明，此处不再赘述。
S54、分流器生成所述业务链策略的使用信息，其中，所述业务链策略的使用信息用于计费。其中，所述业务链策略的使用信息包括处理所述数据包的业务节点的属性信息，还包括使用所述业务链策略的时间信息、使用所述业务链策略的数据包的流量信息中的至少一种。
处理数据包的业务节点的属性信息、使用业务链策略的时间信息、使用业务链策略的数据包的流量信息的详细内容前文已经说明，此处不再赘述。
S55、分流器向计费系统发送所述业务链策略的使用信息，以使计费系统根据业务链策略的使用信息进行计费处理。
可选的，当满足预设的上报条件时，分流器向计费系统发送所述业务链策略的使用信息，所述预设的上报条件包括立即上报、规定时间内上报或达到规定容量时上报。
预设上报条件的具体内容可参考图2实施例相关部分，此处不再赘述。
具体的，分流器通过TSSF实体向计费系统发送所述业务链策略的使用信息。
在一种可能的实现方式中，分流器生成的业务链策略的使用信息中可以包含如表1所示的参数。
在另一种可能的实现方式中，计费触发实体为图4所示网络架构中的业务节点，业务节点与TSSF之间重用SDN Controller和业务节点的接口。计费方法500可以由与分流器相连接的第一个业务节点执行，具体过程包括(图中未示出)：
S51’、与分流器相连接的第一个业务节点获取数据包标识信息与业务链策略的对应关系。
具体的，与分流器相连接的第一个业务节点从TSSF获取该对应关系。
S52’、与分流器相连接的第一个业务节点接收到数据包后检测数据包的标 识信息，根据所述对应关系，确定出数据包使用的业务链策略，其中，所述业务链策略指示对所述数据包进行处理的业务节点。
可选的，所述业务链策略还指示对所述数据包进行处理的业务节点处理所述数据包的顺序。
具体的，与分流器相连接的第一个业务节点根据业务链策略确定其需要对数据包进行处理，在处理完毕后，将该数据包发送至与其相连接的下一个业务节点。该下一个业务节点根据数据包的标识信息，确定该数据包是否使用所述业务链策略，若是，则根据该业务链策略确定其需要对数据包进行处理，在处理完毕后，将该数据包发送至与其相连接的下一个业务节点；若否，则不对该数据包进行处理，直接将该数据包发送至与其相连接的下一个业务节点。
S53’、与分流器相连接的第一个业务节点生成所述业务链策略的使用信息，其中，所述业务链策略的使用信息包括处理所述数据包的业务节点的属性信息，还包括使用所述业务链策略的时间信息、使用所述业务链策略的数据包的流量信息中的至少一种。
处理所述数据包的业务节点的属性信息可以提前配置在第一个业务节点中。
处理数据包的业务节点的属性信息、使用业务链策略的时间信息、使用业务链策略的数据包的流量信息的详细内容前文已经说明，此处不再赘述。
S54’、与分流器相连接的第一个业务节点向计费系统发送所述业务链策略的使用信息。
可选的，在满足预设上报条件时向计费系统发送所述业务链策略的使用信息。具体的预设上报条件参见图2实施例相关内容，此处不再赘述。
具体的，与分流器相连接的第一个业务节点通过TSSF实体向计费系统发送所述业务链策略的使用信息。
通过数据包携带的标识信息确定其使用的业务链策略，并向计费系统发送用于计费的业务链策略使用信息，实现了基于业务链策略进行计费。同时，业务链策略的使用信息包括处理数据包的业务节点的属性信息，还包括使用业务 链策略的时间信息、使用业务链策略的数据包的流量信息中的至少一种，这样增加了计费系统基于业务链策略计费的灵活性。
图6是依据本发明一实施例的基于业务节点的计费方法600的示范性流程图。在具体实现过程中，计费触发实体为图4所示网络架构中的业务节点。本实施例中，各业务节点和TSSF实体之间重用SDN Controller和业务节点之间的接口。
S61、TSSF实体获取数据包标识信息与业务链策略的对应关系。
获取方式在图5实施例S51中已经说明，此处不再赘述。
S62、TSSF实体将所述对应关系发送到分流器。
S63、分流器在接收到数据包后检测该数据包的标识信息，根据所述对应关系，确定出所述数据包使用的业务链策略。
可选的，分流器根据所述对应关系，确定出所述数据包使用的业务链策略之后，通知TSSF实体所述数据包使用的业务链策略。TSSF实体向OCS请求用户使用所述业务链策略的信用授权。TSSF实体在获取到信用授权后通知分流器。
S64、分流器在所述数据包中添加该业务链策略的标签信息，将所述数据包发送到相应的业务节点。
具体的，若所述标签信息中包括对所述数据包进行处理的业务节点形成的路由表，则分流器将所述数据包发送到对所述数据包进行处理的第一个业务节点，根据路由表依次跳转到下一个业务节点；若所述标签信息指示所有业务节点，以及每个业务节点是否对所述数据包进行处理，则分流器将所述数据包发送到与其相连接的第一个业务节点。
S65、业务节点在接收到数据包后，根据所述数据包携带的标签信息确定出需要对所述数据包进行处理。
S66、业务节点处理所述数据包。
在完成对数据包的处理后，业务节点根据标签信息将所述数据包发送到下一个业务节点。
S67、业务节点生成业务节点的使用信息，其中，所述业务节点的使用信息包括所述业务节点的属性信息，还包括所述业务节点处理所述数据包的时间信息、事件信息、流量信息中的至少一种。
业务节点的属性信息、业务节点处理数据包的时间信息、事件信息、流量信息的详细内容前文已经说明，此处不再赘述。
S68、业务节点将所述业务节点的使用信息发送给计费系统。
可选的，当满足预设的上报条件时，业务节点向计费系统发送业务节点的使用信息。具体的预设上报条件参考图3实施例中的相关描述，此处不再赘述。
具体的，业务节点可以通过TSSF实体上报所述业务节点的使用信息。业务节点的使用信息还包括业务链策略标识，TSSF根据业务链策略标识，将对所述数据包进行处理的业务节点生成的业务节点使用信息进行关联，之后发送给计费系统。业务节点也可以通过分流器上报业务节点的使用信息，分流器根据业务链策略标识，将对所述数据包进行处理的业务节点生成的业务节点使用信息进行关联，之后发送给计费系统。
分流器和TSSF向计费系统发送业务节点的使用信息的上报时机可以参考图2实施例中的预设上报条件，此处不再赘述。
通过业务节点生成并向计费系统上报其使用信息，实现了基于业务节点的计费。同时，在有多个业务节点的情况下，通过分流器或TSSF上报使用信息可以避免建立计费系统与各业务节点之间的接口来接收各业务节点的使用信息，也能够避免由计费系统对各业务节点的使用信息进行关联，能够减轻计费系统的压力。
图3与图6实施例描述了通过业务链策略标识将业务节点使用信息进行关联后发送给计费系统进行计费的过程，这一过程增加了计费系统对执行同一业务链策略的业务节点的计费策略的灵活性，例如，计费策略可设置为SE1与SE3使用同一业务链策略时，对SE1免费。
本发明实施例还提供一种基于业务节点的计费方法，不对业务节点使用信息进行关联：
业务节点接收数据包，根据所述数据包携带的处理指示信息确定对所述数据包进行处理；所述业务节点处理所述数据包；所述业务节点向计费系统发送所述业务节点的使用信息，所述业务节点的使用信息包括所述业务节点的属性信息，还包括所述业务节点处理所述数据包的时间信息、事件信息、流量信息中的至少一种。
图3与图6实施例中的标签信息包括业务节点的标识，标签信息是处理指示信息的一种具体实现方式。
计费系统可以直接根据各业务节点上报的使用信息进行计费，不考虑个业务节点使用的业务链策略。
本发明实施例还提供一种基于业务链策略的计费方法，在图4所示的网络架构下，TSSF将数据包标识信息与业务链策略的对应关系下发给业务链策略中指示的业务节点，业务节点在接收到数据包后，根据数据包携带的标识信息以及该对应关系，确定应对数据包进行处理。在完成对数据包的处理后，将该数据包发送至下一个应对其进行处理的业务节点。在一种实现方式中，第一个对数据包进行处理的业务节点以及最后一个对数据包进行处理的业务节点生成业务链策略的使用信息，具体包括处理所述数据包的业务节点的属性信息以及业务链策略标识，还包括使用所述业务链策略的时间信息、使用所述业务链策略的数据包的流量信息中的至少一种。业务节点将业务链策略的使用信息发送给TSSF，TSSF依据业务链策略标识进行关联后，发送给计费系统进行计费。
在实施中，作为一种可能的实现方式，对数据包进行处理的第一个业务节点将首次检测到使用所述业务链策略的数据包的时刻，确定为使用所述业务链策略的起始时间；对数据包进行处理的最后一个业务节点将对使用所述业务链策略的最后一个数据包完成处理的时刻，确定为使用所述业务链策略的结束时间。
在一种实现方式中，TSSF下发数据包标识信息与业务链策略分片标识的对应关系给应对数据包进行处理的业务节点，业务节点对数据包进行处理后，上报的业务链策略使用信息中携带业务链策略分片标识，TSSF根据该业务链策略 分片标识对业务节点使用信息进行关联，之后发送给计费系统进行计费。
例如，业务链策略标识为3，该业务链策略为SE1-SE3-SE6，则分片标识可为3-1、3-3、3-6，将3-1与数据包标识信息的对应关系下发给业务节点SE1，将3-3与数据包标识信息的对应关系下发给业务节点SE3，将3-6与数据包标识信息的对应关系下发给业务节点SE6，TSSF可以同时下发路由信息给SE1、SE3、SE6。SE1、SE3、SE6在上报业务节点使用信息给TSSF后，TSSF根据3-1、3-3、3-6中的业务链策略标识3对业务节点使用信息进行关联。
在本实施例中，业务节点根据数据包携带的标识信息来确定是否对数据包进行处理，数据包携带的标识信息是处理指示信息的一种具体实现方式。
前文所述实施例的部分特征描述适用于本实施例，此处不再赘述。
根据本发明实施例提供的技术方案，通过将对应关系下发给业务节点，避免了分流器在数据包中增加标签信息的过程，减轻了分流器的压力。
本发明实施例还提供一种基于业务节点的计费方法，在图4所示的网络架构下，TSSF将数据包标识信息与业务链策略的对应关系下发给业务链策略中指示的业务节点，业务节点在接收到数据包后，根据数据包携带的标识信息以及该对应关系，确定应对数据包进行处理。在完成对数据包的处理后，将该数据包发送至下一个应对其进行处理的业务节点。对数据包进行处理的各业务节点生成业务节点的使用信息，包括业务节点的属性信息以及业务链策略标识，还包括业务节点处理所述数据包的时间信息、事件信息、流量信息中的至少一种。将生成的业务节点的使用信息发送给TSSF，TSSF根据业务链策略标识将对数据包进行处理的上述业务节点的使用信息进行关联，之后发送给计费系统进行计费。
在一种实现方式中，TSSF下发数据包标识信息与业务链策略分片标识给应对数据包进行处理的业务节点，业务节点对数据包进行处理后，上报的业务节点使用信息中携带业务链策略分片标识，TSSF根据该业务链策略分片标识对业务节点使用信息进行关联，之后发送给计费系统进行计费。
例如，业务链策略标识为3，该业务链策略为SE1-SE3-SE6，则分片标识 可为3-1、3-3、3-6，将3-1与数据包标识信息的对应关系下发给业务节点SE1，将3-3与数据包标识信息的对应关系下发给业务节点SE3，将3-6与数据包标识信息的对应关系下发给业务节点SE6，TSSF可以同时下发路由信息给SE1、SE3、SE6。SE1、SE3、SE6在上报业务节点使用信息给TSSF后，TSSF根据3-1、3-3、3-6中的业务链策略标识3对业务节点使用信息进行关联。
前文所述实施例的部分特征描述适用于本实施例，此处不再赘述。
根据本发明实施例提供的技术方案，通过将对应关系下发给业务节点，避免了分流器在数据包中增加标签信息的过程，减轻了分流器的压力。
本发明实施例还提供了一种计算机设备700，如图7所示，包括：处理器71、输入接口72、输出接口73、存储器74和系统总线75；其中：
处理器71负责逻辑运算和处理。当计算机设备是计费触发实体时，在计费触发实体运行时，处理器71读取存储器74中的程序，具体为：
接收到数据包后，根据所述数据包中携带的标识信息，确定出所述数据包使用的业务链策略，所述业务链策略指示对所述数据包进行处理的业务节点；通过输出接口73向计费系统发送所述业务链策略的使用信息，其中，所述业务链策略的使用信息用于计费。
存储器74包括内存和硬盘，可以存储处理器71在执行操作时所使用的数据。输入接口72用于在处理器71的控制下读入数据，输出接口73在处理器71的控制下输出数据。
总线架构可以包括任意数量的互联的总线和桥，具体由处理器71代表的一个或多个处理器和存储器74代表的内存和硬盘的各种电路链接在一起。总线架构还可以将诸如外围设备、稳压器和功率管理电路等之类的各种其他电路链接在一起，这些都是本领域所公知的，因此，本文不再对其进行进一步描述。
本发明实施例中，计费触发实体可以通过上述计算机设备的形式来实现。计费触发实体具体可以为：PCEF实体、TDF实体、分流器或业务节点。
当计算机设备是业务节点时，在业务节点运行时，处理器71读取存储器74中的程序，具体为：
接收数据包，根据所述数据包携带的处理指示信息确定对所述数据包进行处理；处理所述数据包；通过输出接口73向计费系统发送所述业务节点的使用信息，所述业务节点的使用信息包括所述业务节点的属性信息，还包括所述业务节点处理所述数据包的时间信息、事件信息、流量信息中的至少一种。
上述的计算机设备700可以是一个通用计算机设备或者是一个专用计算机设备。在具体实现中，计算机设备700可以是台式机、便携式电脑、网络服务器、掌上电脑(Personal Digital Assistant，PDA)、移动手机、平板电脑、无线终端设备、通信设备、嵌入式设备或有图7中类似结构的设备。本发明实施例不限定计算机设备700的类型。
图1和图4中的网络设备如PCEF、TDF、分流器、业务节点等可以为图7所示的计算机设备700，以PCEF为计算机设备700为例，PCEF的存储器中存储了一个或多个软件模块。PCEF可以通过处理器以及存储器中的程序代码来实现软件模块，实现基于业务链策略的计费方法。以业务节点为计算机设备700为例，业务节点的存储器中存储了一个或多个软件模块。业务节点可以通过处理器以及存储器中的程序代码来实现软件模块，实现基于业务节点的计费方法。
图8是依据本发明一实施例的计费触发实体800的结构示意图。计费触发实体800包括接收模块802，处理模块804和发送模块806。计费触发实体800为图1中所示的PCEF或TDF或分流器或者图4中所示的分流器或业务节点。
接收模块802，用于接收数据包；
处理模块804，用于根据所述数据包中携带的标识信息，确定出所述数据包使用的业务链策略，所述业务链策略指示对所述数据包进行处理的业务节点；
发送模块806，用于向计费系统发送所述业务链策略的使用信息，其中，所述业务链策略的使用信息用于计费。
可选的，所述接收模块802，还用于获取所述标识信息与所述业务链策略的对应关系；所述处理模块804还用于根据所述对应关系，确定出所述数据包使用的业务链策略。
可选的，业务链策略的使用信息包括处理所述数据包的业务节点的属性信息，还包括使用所述业务链策略的时间信息、使用所述业务链策略的数据包的流量信息中的至少一种。
可选的，当满足预设的上报条件时，所述发送模块806向计费系统发送所述业务链策略的使用信息，所述预设的上报条件包括立即上报、规定时间内上报或达到规定容量时上报。
可选的，所述业务链策略还指示对所述数据包进行处理的业务节点处理所述数据包的顺序。
在本实施例中，接收模块802，处理模块804和发送模块806是以功能模块的形式来呈现。这里的“模块”可以指特定应用集成电路(application-specific integrated circuit，ASIC)，电路，执行一个或多个软件或固件程序的处理器和存储器，集成逻辑电路，和/或其他可以提供上述功能的器件。在一个简单的实施例中，本领域的技术人员可以想到接收模块802可以通过计算机设备700的处理器、存储器和输入接口来实现，处理模块804可以通过计算机设备700的处理器和存储器来实现，发送模块806可以通过计算机设备700的处理器、存储器和输出接口。
图9是依据本发明一实施例的业务节点900的结构示意图。业务节点900包括接收模块902，处理模块904和发送模块906。业务节点900为图1中所示的业务节点或或者图4中所示的业务节点。
接收模块902，用于接收数据包；
处理模块904，用于根据所述数据包携带的处理指示信息确定对所述数据包进行处理；以及处理所述数据包；
发送模块906，用于向计费系统发送所述业务节点的使用信息，所述业务节点的使用信息包括所述业务节点的属性信息，还包括所述业务节点处理所述数据包的时间信息、事件信息、流量信息中的至少一种。
可选的，所述处理指示信息包括所述业务节点的标识或者所述数据包的标识信息。
可选的，当所述处理指示信息包括所述数据包的标识信息时，在所述接收模块902接收所述数据包之前，所述接收模块902还用于获取所述标识信息与所述业务链策略的对应关系；所述处理模块904还用于根据所述数据包携带的标识信息以及所述对应关系确定对所述数据包进行处理。
可选的，所述发送模块906用于通过分流器向所述计费系统发送所述业务节点的使用信息。
可选的，所述数据包还携带业务链策略标识，所述发送模块906用于通过TSSF向所述计费系统发送所述业务节点的使用信息，所述业务节点的使用信息还包括所述业务链策略标识，所述业务链策略标识用于关联多个所述业务节点的使用信息。
可选的，当满足预设的上报条件时，所述发送模块906向计费系统发送所述业务节点的使用信息，所述预设的上报条件包括立即上报、规定时间内上报或达到规定容量时上报
在本实施例中，接收模块902，处理模块904和发送模块906是以功能模块的形式来呈现。这里的“模块”可以指特定应用集成电路(application-specific integrated circuit，ASIC)，电路，执行一个或多个软件或固件程序的处理器和存储器，集成逻辑电路，和/或其他可以提供上述功能的器件。在一个简单的实施例中，本领域的技术人员可以想到接收模块902可以通过计算机设备700的处理器、存储器和输入接口来实现，处理模块904可以通过计算机设备700的处理器和存储器来实现，发送模块906可以通过计算机设备700的处理器、存储器和输出接口。
本领域内的技术人员应明白，本发明的实施例可提供为方法、系统、或计算机程序产品。因此，本发明可采用完全硬件实施例、完全软件实施例、或结合软件和硬件方面的实施例的形式。而且，本发明可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器、CD-ROM、光学存储器等)上实施的计算机程序产品的形式。
本发明是参照根据本发明实施例的方法、设备(系统)、和计算机程序产品 的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器，使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中，使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品，该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上，使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理，从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
尽管已描述了本发明的优选实施例，但本领域内的技术人员一旦得知了基本创造性概念，则可对这些实施例作出另外的变更和修改。所以，所附权利要求意欲解释为包括优选实施例以及落入本发明范围的所有变更和修改。
显然，本领域的技术人员可以对本发明进行各种改动和变型而不脱离本发明的精神和范围。这样，倘若本发明的这些修改和变型属于本发明权利要求及其等同技术的范围之内，则本发明也意图包含这些改动和变型在内。

Claims (26)

  1. 一种计费方法，其特征在于，所述方法包括：
    计费触发实体接收到数据包后，根据所述数据包中携带的标识信息，确定出所述数据包使用的业务链策略，所述业务链策略指示对所述数据包进行处理的业务节点；
    所述计费触发实体向计费系统发送所述业务链策略的使用信息，其中，所述业务链策略的使用信息用于计费。
  2. 如权利要求1所述的方法，其特征在于，在所述计费触发实体根据所述数据包中携带的标识信息，确定出所述数据包使用的业务链策略之前，该方法还包括：所述计费触发实体获取所述标识信息与所述业务链策略的对应关系；
    所述计费触发实体根据所述数据包中携带的标识信息，确定出所述数据包使用的业务链策略，包括：所述计费触发实体根据所述对应关系，确定出所述数据包使用的业务链策略。
  3. 如权利要求1或2所述的方法，其特征在于，所述业务链策略的使用信息包括处理所述数据包的业务节点的属性信息，还包括使用所述业务链策略的时间信息、使用所述业务链策略的数据包的流量信息中的至少一种。
  4. 如权利要求1至3任意一项所述的方法，其特征在于，所述计费触发实体为策略及计费执行功能PCEF实体、业务检测功能TDF实体、分流器或业务节点。
  5. 如权利要求1至4任意一项所述的方法，其特征在于，当满足预设的上报条件时，所述计费触发实体向计费系统发送所述业务链策略的使用信息，所述预设的上报条件包括立即上报、规定时间内上报或达到规定容量时上报。
  6. 如权利要求1至5任意一项所述的方法，其特征在于，所述业务链策略还指示对所述数据包进行处理的业务节点处理所述数据包的顺序。
  7. 一种计费方法，其特征在于，所述方法包括：
    业务节点接收数据包，根据所述数据包携带的处理指示信息确定对所述数 据包进行处理；
    所述业务节点处理所述数据包；
    所述业务节点向计费系统发送所述业务节点的使用信息，所述业务节点的使用信息包括所述业务节点的属性信息，还包括所述业务节点处理所述数据包的时间信息、事件信息、流量信息中的至少一种。
  8. 如权利要求7所述的方法，其特征在于，所述处理指示信息包括所述业务节点的标识或者所述数据包的标识信息。
  9. 如权利要求8所述的方法，其特征在于，当所述处理指示信息包括所述数据包的标识信息时，在接收所述数据包之前，所述业务节点获取所述标识信息与所述业务链策略的对应关系，所述根据所述数据包携带的处理指示信息确定对所述数据包进行处理包括：根据所述数据包携带的标识信息以及所述对应关系确定对所述数据包进行处理。
  10. 如权利要求7至9任意一项所述的方法，其特征在于，所述业务节点通过分流器向所述计费系统发送所述业务节点的使用信息。
  11. 如权利要求7至10任意一项所述的方法，其特征在于，所述数据包还携带业务链策略标识，所述业务节点通过TSSF向所述计费系统发送所述业务节点的使用信息，所述业务节点的使用信息还包括所述业务链策略标识，所述业务链策略标识用于关联多个所述业务节点的使用信息。
  12. 如权利要求7至11任意一项所述的方法，其特征在于，当满足预设的上报条件时，所述业务节点向计费系统发送所述业务节点的使用信息，所述预设的上报条件包括立即上报、规定时间内上报或达到规定容量时上报。
  13. 一种计费触发实体，其特征在于，包括接收模块，处理模块和发送模块：
    所述接收模块，用于接收数据包；
    所述处理模块，用于根据所述数据包中携带的标识信息，确定出所述数据包使用的业务链策略，所述业务链策略指示对所述数据包进行处理的业务节点；
    所述发送模块，用于向计费系统发送所述业务链策略的使用信息，其中， 所述业务链策略的使用信息用于计费。
  14. 如权利要求13所述的计费触发实体，其特征在于，所述接收模块，还用于获取所述标识信息与所述业务链策略的对应关系；
    所述处理模块还用于根据所述对应关系，确定出所述数据包使用的业务链策略。
  15. 如权利要求13或14所述的计费触发实体，其特征在于，所述业务链策略的使用信息包括处理所述数据包的业务节点的属性信息，还包括使用所述业务链策略的时间信息、使用所述业务链策略的数据包的流量信息中的至少一种。
  16. 如权利要求13至15任意一项所述的计费触发实体，其特征在于，所述装置为策略及计费执行功能PCEF实体、业务检测功能TDF实体、分流器或业务节点。
  17. 如权利要求13至16任意一项所述的计费触发实体，其特征在于，当满足预设的上报条件时，所述发送模块向计费系统发送所述业务链策略的使用信息，所述预设的上报条件包括立即上报、规定时间内上报或达到规定容量时上报。
  18. 如权利要求13至17任意一项所述的计费触发实体，其特征在于，所述业务链策略还指示对所述数据包进行处理的业务节点处理所述数据包的顺序。
  19. 一种业务节点，其特征在于，包括接收模块，处理模块和发送模块：
    所述接收模块，用于接收数据包；
    所述处理模块，用于根据所述数据包携带的处理指示信息确定对所述数据包进行处理；以及处理所述数据包；
    所述发送模块，用于向计费系统发送所述业务节点的使用信息，所述业务节点的使用信息包括所述业务节点的属性信息，还包括所述业务节点处理所述数据包的时间信息、事件信息、流量信息中的至少一种。
  20. 如权利要求19所述的业务节点，其特征在于，所述处理指示信息包括 所述业务节点的标识或者所述数据包的标识信息。
  21. 如权利要求20所述的业务节点，其特征在于，当所述处理指示信息包括所述数据包的标识信息时，在所述接收模块接收所述数据包之前，所述接收模块还用于获取所述标识信息与所述业务链策略的对应关系；所述处理模块还用于根据所述数据包携带的标识信息以及所述对应关系确定对所述数据包进行处理。
  22. 如权利要求19至21任意一项所述的业务节点，其特征在于，所述发送模块用于通过分流器向所述计费系统发送所述业务节点的使用信息。
  23. 如权利要求19至22任意一项所述的业务节点，其特征在于，所述数据包还携带业务链策略标识，所述发送模块用于通过TSSF向所述计费系统发送所述业务节点的使用信息，所述业务节点的使用信息还包括所述业务链策略标识，所述业务链策略标识用于关联多个所述业务节点的使用信息。
  24. 如权利要求19至23任意一项所述的业务节点，其特征在于，当满足预设的上报条件时，所述发送模块向计费系统发送所述业务节点的使用信息，所述预设的上报条件包括立即上报、规定时间内上报或达到规定容量时上报。
  25. 一种计费装置，其特征在于，包括：处理器、输入接口、输出接口、以及存储器，其中：
    所述处理器读取所述存储器中的程序，执行如权利要求1至6任意一项所述的方法。
  26. 一种计费装置，其特征在于，包括：处理器、输入接口、输出接口、以及存储器，其中：
    所述处理器读取所述存储器中的程序，执行如权利要求7至12任意一项所述的方法。
PCT/CN2016/111531 2016-02-29 2016-12-22 一种计费方法和装置 WO2017148206A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP16892384.5A EP3407538A4 (en) 2016-02-29 2016-12-22 CHARGING METHOD AND DEVICE
US16/114,872 US20180367323A1 (en) 2016-02-29 2018-08-28 Charging Method and Apparatus

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201610113042.5 2016-02-29
CN201610113042.5A CN107135083A (zh) 2016-02-29 2016-02-29 一种计费方法和装置

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/114,872 Continuation US20180367323A1 (en) 2016-02-29 2018-08-28 Charging Method and Apparatus

Publications (1)

Publication Number Publication Date
WO2017148206A1 true WO2017148206A1 (zh) 2017-09-08

Family

ID=59721442

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/111531 WO2017148206A1 (zh) 2016-02-29 2016-12-22 一种计费方法和装置

Country Status (4)

Country Link
US (1) US20180367323A1 (zh)
EP (1) EP3407538A4 (zh)
CN (1) CN107135083A (zh)
WO (1) WO2017148206A1 (zh)

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3485608B1 (en) * 2016-07-13 2020-06-24 Telefonaktiebolaget LM Ericsson (PUBL) Methods and servers for managing traffic steering policies
CN109995540B (zh) * 2017-12-30 2022-06-10 中国移动通信集团山西有限公司 事件性增值业务的计费方法、系统、设备及介质
CN110445623B (zh) * 2018-05-04 2020-11-10 华为技术有限公司 计费方法、设备及系统
CN111181800B (zh) * 2019-11-27 2023-09-19 腾讯科技（深圳）有限公司 测试数据处理方法、装置、电子设备及存储介质

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101212792A (zh) * 2006-12-27 2008-07-02 中国移动通信集团公司 融合类业务的计费信息处理方法
CN102098649A (zh) * 2010-12-09 2011-06-15 成都市华为赛门铁克科技有限公司 基于策略计费控制系统的增值业务处理方法、装置及系统
CN103905447A (zh) * 2014-04-01 2014-07-02 华为技术有限公司 业务链路选择控制方法以及设备
WO2015188682A1 (zh) * 2014-06-10 2015-12-17 华为技术有限公司 业务链的处理方法、装置与系统
WO2016012856A1 (en) * 2014-07-25 2016-01-28 Alcatel Lucent Methods and apparatuses of service function chain based on pcc architecture

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9065936B2 (en) * 2010-12-09 2015-06-23 Allot Communications Ltd. Cellular traffic monitoring and charging using application detection rules
EP2649843B1 (en) * 2010-12-09 2015-11-04 Allot Communications Ltd. Device, system and method of traffic detection
WO2015135572A1 (en) * 2014-03-11 2015-09-17 Telefonaktiebolaget Lm Ericsson (Publ) Methods, devices and computer programs for subjecting traffic associated with a service to a specific treatment
CN105450552B (zh) * 2014-07-02 2018-12-14 阿尔卡特朗讯 基于sdn网络对应用服务链的策略与计费控制方法与设备
US11044203B2 (en) * 2016-01-19 2021-06-22 Cisco Technology, Inc. System and method for hosting mobile packet core and value-added services using a software defined network and service chains
WO2018046081A1 (en) * 2016-09-07 2018-03-15 Telefonaktiebolaget Lm Ericsson (Publ) Methods and nodes for enabling management of traffic steering policy

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101212792A (zh) * 2006-12-27 2008-07-02 中国移动通信集团公司 融合类业务的计费信息处理方法
CN102098649A (zh) * 2010-12-09 2011-06-15 成都市华为赛门铁克科技有限公司 基于策略计费控制系统的增值业务处理方法、装置及系统
CN103905447A (zh) * 2014-04-01 2014-07-02 华为技术有限公司 业务链路选择控制方法以及设备
WO2015188682A1 (zh) * 2014-06-10 2015-12-17 华为技术有限公司 业务链的处理方法、装置与系统
WO2016012856A1 (en) * 2014-07-25 2016-01-28 Alcatel Lucent Methods and apparatuses of service function chain based on pcc architecture

Also Published As

Publication number Publication date
CN107135083A (zh) 2017-09-05
EP3407538A1 (en) 2018-11-28
US20180367323A1 (en) 2018-12-20
EP3407538A4 (en) 2019-01-09

Similar Documents

Publication Publication Date Title
US9743269B1 (en) Analytics triggered subscriber policies
KR101906742B1 (ko) Sdn 네트워크에 기초한 애플리케이션 서비스 체인에 대한 정책 및 과금 제어 방법 및 장치
EP3213535B1 (en) Methods and apparatuses for service layer charging correlation with underlying networks
US9641346B2 (en) Method and apparatus for performing charging control to application-layer data
WO2017148206A1 (zh) 一种计费方法和装置
US10924900B2 (en) Charging method and apparatus, and system
CN102948137B (zh) 用于使用Gx规则检测服务数据流的启动的方法、系统和计算机可读介质
WO2012083795A1 (zh) 业务控制方法、装置及系统
WO2009012686A1 (fr) Procédé, équipement et système de mise en œuvre du contrôle des conditions d'utilisation et de facturation
CN105451207B (zh) 基于pcc架构的业务功能链的控制方法及装置
WO2011079773A1 (zh) 用户会话策略控制方法、装置及系统
CN109495857B (zh) 计费方法、移动边缘计算服务器、计费系统及策略控制规则网元
WO2015058549A1 (zh) 业务同步方法、内容管理设备及策略管理设备
US20170310493A1 (en) Network entity and service policy management method
KR20130116343A (ko) 일시적 가입 레코드
WO2015113284A1 (zh) 计费处理方法、集中网络控制节点、功能节点和系统
KR102601122B1 (ko) 패킷 보고 방법과 시스템
EP2950581B1 (en) Policy server, policy enforcement device, and various methods for dynamically excluding active service add-ons from bearer throttling for user terminals
WO2018177003A1 (zh) 一种计费方法、相关设备和系统
WO2012106881A1 (zh) 一种计费方法、网络接入设备、核心网设备
KR20130079423A (ko) 아웃바운드 메시지의 실패 관리를 위한 프레임워크
WO2014110966A1 (zh) 一种业务数据的处理方法、装置和系统
WO2020173548A1 (en) Sx protocol extension to support pause measurement on user plane
WO2017128817A1 (zh) 第三方应用访问方法及装置
WO2017193303A1 (zh) 一种通信计费方法

Legal Events

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

Ref document number: 2016892384

Country of ref document: EP

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2016892384

Country of ref document: EP

Effective date: 20180823