WO2016078090A1 - 计费控制装置、方法及系统 - Google Patents

计费控制装置、方法及系统 Download PDF

Info

Publication number
WO2016078090A1
WO2016078090A1 PCT/CN2014/091929 CN2014091929W WO2016078090A1 WO 2016078090 A1 WO2016078090 A1 WO 2016078090A1 CN 2014091929 W CN2014091929 W CN 2014091929W WO 2016078090 A1 WO2016078090 A1 WO 2016078090A1
Authority
WO
WIPO (PCT)
Prior art keywords
service
identifier
charging
pcef
control device
Prior art date
Application number
PCT/CN2014/091929
Other languages
English (en)
French (fr)
Chinese (zh)
Inventor
王毓芳
王彩娟
罗武军
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to PCT/CN2014/091929 priority Critical patent/WO2016078090A1/zh
Priority to KR1020177016819A priority patent/KR101933594B1/ko
Priority to RU2017121274A priority patent/RU2669522C1/ru
Priority to CA2968439A priority patent/CA2968439C/en
Priority to BR112017010583-7A priority patent/BR112017010583B1/pt
Priority to JP2017527569A priority patent/JP6508660B2/ja
Priority to CN201480002360.3A priority patent/CN105814930B/zh
Priority to AU2014411891A priority patent/AU2014411891B2/en
Priority to EP14906599.7A priority patent/EP3214862B1/en
Publication of WO2016078090A1 publication Critical patent/WO2016078090A1/zh
Priority to US15/600,544 priority patent/US10666812B2/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
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • 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
    • 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
    • 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
    • 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/2483—Traffic characterised by specific attributes, e.g. priority or QoS involving identification of individual flows
    • 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/08—Metering calls to called party, i.e. B-party charged for the communication
    • 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/52—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP for operator independent billing 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/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
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/04—Arrangements for maintaining operational condition
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0289—Congestion control
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/24—Accounting or billing

Definitions

  • Embodiments of the present invention relate to the field of communications, and, more particularly, to a charging control apparatus, method, and system.
  • the traffic 800 service is a service mainly charged to an Over Served (Over The Top, OTT) Service Provider (SP).
  • OTT SP can be called a corporate group or simply a group.
  • the traffic 800 business is mainly paid by the enterprise group, and can obtain more value-added business returns. For example, more traffic can be obtained, and the work efficiency of the employees of the enterprise group can be improved. Users can have a better experience of accessing traffic 800 services regardless of the cost. Operators' network investments can be more digested and gain more opportunities for expansion.
  • An OTT SP may provide multiple traffic 800 services.
  • the operator needs to separately assign a charging identifier to each traffic 800 service.
  • Operators need to be able to quickly and easily deploy new traffic 800 services, flexibly and dynamically adapt to changes in OTT SP servers, and ensure that users' traffic 800 services are accurately and free of charge.
  • each OTT SP provides a server address/host list of traffic 800 services, or a list of Uniform Resource Locators (URLs).
  • the service provider and the charging identifier corresponding to the server address/host list or the URL list are provided by the operator. All the information needs to be pre-configured on the Policy and Charging Enforcement Function (PCEF).
  • PCEF Policy and Charging Enforcement Function
  • Embodiments of the present invention provide a charging control apparatus, method, and system, which can reduce the workload of configuring on a PCEF.
  • a charging control apparatus when a user equipment UE accesses an operator When the OTT service provider SP charges the business, it includes:
  • a receiver configured to receive flow description information from a policy and charging enforcement function PCEF, where the flow description information is obtained by the PCEF according to a data flow received from the UE;
  • a processor configured to determine, according to the flow description information received by the receiver, a service identifier corresponding to the data flow
  • a transmitter configured to send the service identifier determined by the processor to the PCEF, so that the PCEF performs charging on the service according to the service identifier.
  • the processor is further configured to determine, according to the flow description information received by the receiver, a charging corresponding to the data flow.
  • the transmitter is further configured to send the charging identifier to the PCEF.
  • the receiver is further configured to receive a user identifier of the UE;
  • the processor is further configured to determine whether the user identifier has a corresponding relationship with the service identifier
  • the transmitter is configured to send the service identifier and the charging identifier to the PCEF when the processor determines that the user identifier has a corresponding relationship with the service identifier.
  • the receiver is further configured to receive the device or service operation of the OTT SP.
  • the processor is configured to generate first matching information according to the user registration information, where the first matching information includes a correspondence between a user identifier and a service identifier.
  • the processor is configured to: determine, according to the first matching information, Whether the user identifier has a corresponding relationship with the service identifier.
  • the receiver is further configured to receive a user that is sent by the device of the OTT SP. registration message;
  • the transmitter is further configured to send the user registration information to the service operation support system BOSS.
  • the receiver is further configured to obtain a service identifier and a charging identifier configured by an operator, and receive a service rule set sent by the device of the OTT SP;
  • the processor is further configured to generate second matching information according to the service rule set, where the second matching information includes a correspondence between a service rule set, a service identifier, and a charging identifier.
  • the processor is further configured to determine, according to the second matching information, The service identifier and the charging identifier corresponding to the data flow.
  • the receiver is further configured to acquire a service identifier and a billing configured by an operator. Identifying and receiving a set of business rules sent by the device of the OTT SP;
  • the transmitter is further configured to send the service identifier and the charging identifier to a policy and charging rule function PCRF;
  • the processor is further configured to generate third matching information according to the service rule set, where the third matching information includes a correspondence between a service rule set and a service identifier.
  • the receiver is further configured to receive a user that is sent by the device of the OTT SP. registration message;
  • the transmitter is further configured to send the user registration information to the PCRF.
  • the second aspect provides a policy and charging execution function PCEF.
  • PCEF policy and charging execution function
  • a receiver configured to receive a data stream sent by the UE
  • a processor configured to parse the data stream, and determine flow description information of the data stream
  • a transmitter configured to send the flow description information determined by the processor to a charging control device
  • the receiver is further configured to receive a service identifier sent by the charging control device, where the service identifier is determined by the charging control device according to the flow description information;
  • the processor is further configured to perform online/offline charging on the service according to the service identifier received by the receiver.
  • the receiver is further configured to receive a charging identifier sent by the charging control device;
  • the processor is specifically configured to perform online/offline charging on the service according to the service identifier and the charging identifier.
  • the processor is further configured to determine whether the UE is registered with the service
  • the transmitter is specifically configured to: when the processor determines that the UE is registered with the service, send the flow description information to the charging control device.
  • a policy and charging rule function PCRF including:
  • a receiver configured to receive a service identifier and a charging identifier from the charging control device, and receive user registration information from the charging control device or the service operation support system BOSS;
  • a processor configured to generate a policy control and charging PCC policy according to the user registration information, the service identifier, and the charging identifier received by the receiver.
  • a business operation support system BOSS including:
  • a transmitter configured to send the user registration information received by the receiver to the charging control device.
  • the receiver when the service that is charged to the OTT service provider SP on the operator is a backward-paid service, the receiver is specifically used to Receiving the user registration information from a device of the OTT SP;
  • the receiver is specifically configured to receive the user registration information from the user equipment UE.
  • a device for an OTT service provider SP above an operator including:
  • a transmitter configured to send the set of service rules to the charging control device.
  • the service charged to the OTT SP is a backward paid service
  • the processor is further configured to generate user registration information
  • the transmitter is further configured to send the user registration information to the charging control device or the service operation support system BOSS.
  • a billing system including:
  • a method for charging is provided.
  • the method includes:
  • the determining, according to the flow description information, the service identifier corresponding to the data flow including:
  • Sending the service identifier to the PCEF includes:
  • the user identifier of the UE is received from the PCEF;
  • Sending the service identifier and the charging identifier to the PCEF including:
  • the service identifier and the charging identifier are sent to the PCEF.
  • the method before the receiving the flow description information from the PCEF, the method further includes:
  • the first matching information is generated according to the user registration information, where the first matching information includes a correspondence between the user identifier and the service identifier.
  • the determining whether the user identifier and the service identifier have a corresponding relationship include:
  • the method before the receiving the flow description information from the PCEF, the method further includes:
  • the method before the receiving the flow description information from the PCEF, the method further includes:
  • the second matching information includes a correspondence between the service rule set, the service identifier, and the charging identifier.
  • the determining, according to the flow description information, the service identifier corresponding to the data flow And billing identifiers including:
  • the method before the receiving the flow description information from the PCEF, the method further includes:
  • the method before the receiving the flow description information from the PCEF, the method further includes:
  • the user registration information is sent to the PCRF.
  • the eighth aspect provides a method for charging, where the method is performed by the policy and charging execution function PCEF.
  • the method includes:
  • Receiving the service identifier sent by the charging control device including:
  • Performing online/offline charging for the service according to the service identifier including:
  • the method further includes:
  • the sending the flow description information to the charging control device includes:
  • the flow description information is sent to the charging control device.
  • a ninth aspect provides a method for charging, where the method is performed by a policy and charging rule function PCRF, including:
  • a method for charging is provided, where the method is performed by a service operation support system BOSS, including:
  • the user registration information is sent to the charging control device.
  • the receiving the user registration information includes:
  • the receiving the user registration information includes:
  • the user registration information is received from the user equipment UE.
  • a method for charging is provided, where the method is performed by an OTT service provider SP device on an operator, including:
  • the set of business rules is sent to the charging control device.
  • the service charged to the OTT SP is a backward paid service, it also includes:
  • the PCEF may obtain the service identifier from the charging control device.
  • the service identifier and the charging identifier corresponding to the data flow can be obtained by the PCEF without configuring the service identifier and the charging identifier on the PCEF, thereby reducing the workload during configuration.
  • 1 is a system or network framework diagram of an embodiment of the present invention.
  • FIG. 2 is a schematic structural diagram of a charge control apparatus according to an embodiment of the present invention.
  • FIG. 3 is a schematic structural view of a PCEF according to an embodiment of the present invention.
  • FIG. 4 is a schematic view showing the structure of a PCRF according to an embodiment of the present invention.
  • FIG. 5 is a schematic structural view of a BOSS according to an embodiment of the present invention.
  • FIG. 6 is a schematic structural diagram of an apparatus of an OTT SP according to an embodiment of the present invention.
  • FIG. 7 is a signaling flow diagram of a method of charging according to an embodiment of the present invention.
  • FIG. 8 is a signaling flow diagram of a method in accordance with another embodiment of the present invention.
  • FIG. 9 is a signaling flow diagram of a method of charging according to another embodiment of the present invention.
  • FIG. 10 is a signaling flow diagram of a method of charging according to another embodiment of the present invention.
  • FIG. 11 is a signaling flow diagram of a method of charging according to another embodiment of the present invention.
  • FIG. 12 is a signaling flow diagram of a method of charging according to another embodiment of the present invention.
  • FIG. 13 is a signaling flow diagram of a method of charging according to another embodiment of the present invention.
  • FIG. 14 is a signaling flow diagram of a method of charging according to another embodiment of the present invention.
  • 15 is a signaling flow diagram of a method of charging according to another embodiment of the present invention.
  • 16 is a signaling flow diagram of a method of charging according to another embodiment of the present invention.
  • 17 is a signaling flow diagram of a method of charging according to another embodiment of the present invention.
  • 18 is a signaling flow diagram of a method of charging according to another embodiment of the present invention.
  • FIG. 19 is a schematic structural diagram of a system for charging according to an embodiment of the present invention.
  • 20 is a flow chart of a method of charging in accordance with an embodiment of the present invention.
  • 21 is a flow chart of a method of charging according to another embodiment of the present invention.
  • 22 is a flow chart of a method of charging according to another embodiment of the present invention.
  • 23 is a flow chart of a method of charging according to another embodiment of the present invention.
  • 24 is a flow chart of a method of charging in accordance with another embodiment of the present invention.
  • FIG. 1 is a system or network framework diagram of an embodiment of the present invention.
  • the system 10 shown in FIG. 1 includes a charging control device 102, a Policy and Charging Enforcement Function (PCEF) 108, a Policy and Charging Rules Function (PCRF) 110, and a service operation.
  • PCEF Policy and Charging Enforcement Function
  • PCF Policy and Charging Rules Function
  • BOSS Support & System
  • FIG. 1 also shows a device 106, a base station 109, and a user equipment (UE) 112 of an Over The Top (OTT) Service Provider (SP).
  • OTT Over The Top
  • SP Service Provider
  • the UE may also be referred to as a terminal, a subscriber unit, a subscriber station, a mobile station, a mobile station, a remote station, a remote terminal, a mobile device, a user terminal, a mobile terminal, and a wireless communication device. Backup, user agent or user device.
  • the UE may be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA), with wireless communication.
  • SIP Session Initiation Protocol
  • WLL Wireless Local Loop
  • PDA Personal Digital Assistant
  • the system 10 shown in FIG. 1 is used to charge a service charged to an OTT SP.
  • the service charged to the OTT SP may also be referred to as a traffic 800 service or a unified payment service.
  • the PCRF 110 can make a decision on the charging and control policy of the user according to the subscription information of the user, and send it to the PCEF 108.
  • the PCEF 108 may be responsible for receiving the charging and control policies authorized by the PCRF 110 for individual users and implementing the charging and control policies.
  • the BOSS 104 is located in the carrier network and can be responsible for contract management of user packages and online/offline accounting.
  • the charging control device 102 may also be referred to as a traffic 800 service platform, or simply as a traffic 800 platform.
  • the charging control device 102 can have a first interface, a second interface, a third interface, and a fourth interface.
  • the charging control device 102 can communicate with the BOSS 104 via a first interface; communicate with the device 106 of the OTT SP via a second interface; communicate with the PCEF 108 via a third interface; and communicate with the PCRF 110 via a fourth interface.
  • the charging control apparatus 102 may include an interface processing unit, configured to manage the first interface, the second interface, the third interface, and the fourth interface.
  • the interface processing unit can be implemented by a processor within the billing control device 102.
  • the BOSS 104 can have a corresponding BOSS interface to communicate with the billing control device 102.
  • the device 106 of the OTT SP can have a corresponding interface to communicate with the charging control device 102.
  • the corresponding interface of the device of the OTT SP may be an interface on the server of the OTT SP.
  • the PCEF 108 may have a corresponding PCEF interface to communicate with the billing control device 102.
  • the PCEF has enabled the Service Awareness (SA) function.
  • SA Service Awareness
  • PCRF 110 may have a corresponding PCRF interface to communicate with the charging control device 102.
  • the PCRF 110 and the PCEF 108 can communicate via the Gx interface.
  • the PCEF 108 and the BOSS 104 can communicate via the Gy/Ga/Gz interface.
  • the device 106 of the OTT SP may be an OTT server, and the device 106 of the OTT SP has functions such as authentication, user group management, and the like.
  • the charging control device 102 can include a receiver 1022, a processor 1024, and a transmitter. Transmitter 1026.
  • PCEF 108 can include a receiver 1082, a processor 1084, and a transmitter 1086.
  • PCRF 110 may include a receiver 1102, a processor 1104, and a transmitter 1106.
  • BOSS 104 can include a receiver 1042, a processor 1044, and a transmitter 1046.
  • the device 106 of the OTT SP can include a receiver 1062, a processor 1064, and a transmitter 1066.
  • the UE 112 when the UE 112 performs service access, the UE 112 sends the data stream to the PCEF 108 through the base station 109. Further, the system shown in FIG. 1 can be used to complete a charging operation for the service.
  • the service may be a service that charges the OTT SP, that is, the service is a traffic 800 service.
  • FIG. 7 is a signaling flow diagram of a method of charging according to an embodiment of the present invention.
  • the method shown in Figure 7 includes:
  • Receiver 1082 of PCEF 108 receives the data stream transmitted by UE 112.
  • UE 112 may send the data stream to PCEF 108.
  • the data stream may be a data stream of traffic charged to the OTT SP.
  • the UE 112 sends a user activation request to the PCEF 108.
  • the PCEF 108 acquires a Policy Control and Charging (PCC) policy from the PCRF 110.
  • the PCRF 110 performs policy authorization and delivers the dynamic rules to the PCEF 108.
  • the PCEF 108 performs policy installation based on the dynamic rules and sends a User Activation Success Response message to the UE 112.
  • PCC Policy Control and Charging
  • the processor 1084 of the PCEF 108 parses the data stream and obtains stream description information of the data stream.
  • the parsing of the data stream may include identifying L3/4 information, L7 information, and the like of the data stream.
  • the L3/4 information may include an Internet Protocol (IP) address, a port number, a protocol number, and the like.
  • the L7 information may include: a URL address, an L7 protocol type, and the like.
  • the stream description information may include L3/4 information and/or L7 information of the data stream, and the like.
  • the transmitter 1086 of the PCEF 108 transmits the flow description information to the charging control device 102.
  • the processor 1024 of the charging control device 102 determines, according to the flow description information, a service identifier and a charging identifier of a service that is charged to the OTT SP.
  • the service identifier may be a service ID of the service
  • the charging identifier may be a charging group (RG).
  • the second matching information may be stored in the charging control device 102, where the second matching information includes a correspondence between a service rule set, a service identifier, and a charging identifier.
  • each business rule set may include L3/4 information, L7 information, and the like.
  • the L3/4 information may include an IP address, a port number, a protocol number, and the like;
  • the L7 information may include a URL address, an L7 protocol type, and the like.
  • the invention is not limited thereto.
  • the set of business rules may also be referred to as a set of filtering rule information.
  • the service identifier and the charging identifier corresponding to the certain service rule set may be determined according to the second matching information, and the service corresponding to the certain service rule set may be determined.
  • the identifier and the charging identifier are determined as the service identifier and the charging identifier corresponding to the stream description information, that is, the service identifier and the charging identifier corresponding to the data stream.
  • the sender 1026 of the charging control device 102 sends the service identifier and the charging identifier corresponding to the data stream to the PCEF 108, so that the PCEF 108 charges the service according to the service identifier and the charging identifier.
  • the PCEF 108 when the UE 112 performs the traffic 800 service access, the PCEF 108 sends the flow description information to the charging control device 102, and the charging control device 102 determines the service identifier and the charging identifier corresponding to the data flow. Send to PCEF 108.
  • the service identifier and the charging identifier are not required to be configured on the PCEF 108, and the PCEF 108 can obtain the service identifier and the charging identifier corresponding to the data flow, thereby reducing the configuration workload of the PCEF 108.
  • the processor 1084 of the PCEF 108 performs online/offline charging according to the service identifier and the charging identifier.
  • the billing is for the service with the service identifier.
  • the PCEF 108 can implement the online/offline charging function together with the BOSS 104. After 706, it may also be included (not shown in Figure 7):
  • the transmitter 1086 of the PCEF 108 sends a Credit Control Request (CCR) message to the BOSS 104.
  • CCR Credit Control Request
  • the CCR message may include the service identity, the charging identity, and the user identity of the UE 112.
  • the user identifier may be a Mobile Subscriber International ISDN (Integrated Service Digital Network)/PSTN (Public Switched Telephone Network) number (MSISDN).
  • MSISDN Mobile Subscriber International ISDN
  • PSTN Public Switched Telephone Network
  • the user identification can be a phone number.
  • the processor 1044 of the BOSS 104 performs a differentiated rating.
  • the BOSS 104 may determine, according to the user registration information, whether the UE 112 is registered with the service having the service identifier, and further determines that the service is charged or free for the UE 112.
  • the BOSS 104 may perform a chargeback process on the user account of the UE 112 based on the charging identifier. For example, different billing identifiers can correspond to different prices.
  • the service charged to the OTT SP is a backward paid service, that is, the service is completely paid by the OTT SP
  • the user registration information is provided by the device of the OTT SP.
  • the service is a forward-paid service, that is, the UE also needs to pay in addition to the payment by the OTT SP
  • the user registration information is generated by the user performing a service contract in the BOSS system.
  • the sender 1046 of the BOSS 104 sends a Credit Control Answer (CCA) message to the PCEF 108.
  • CCA Credit Control Answer
  • PCEF 108 and BOSS 104 can collectively complete online/offline billing.
  • the method shown in FIG. 8 may be further included before the method shown in FIG. 7.
  • the method shown in Figure 8 includes:
  • the receiver 1022 of the charging control device 102 acquires a service identifier and a charging identifier pre-configured by the operator.
  • the operator plans a service identification and a charging identifier for the service charged to the OTT SP, and performs pre-configuration on the charging control device 102.
  • the processor 1064 of the 802, OTT SP device 106 generates a set of business rules.
  • the set of business rules may include L3/4 information, L7 information, and the like.
  • the L3/4 information may include an IP address, a port number, a protocol number, and the like;
  • the L7 information may include a URL address, an L7 protocol type, and the like. The invention is not limited thereto.
  • the transmitter 1066 of the device 106 of the OTT SP sends the set of service rules to the charging control device 102.
  • the device 106 of the OTT SP may send the set of service rules in batches to the charging control device 102 in the form of a file, or the device 106 of the OTT SP may also provide or update the set of business rules in real time.
  • the processor 1024 of the charging control apparatus 102 generates second matching information according to the business rule set.
  • the second matching information includes a correspondence between a service rule set, a service identifier, and a charging identifier.
  • the second matching information may be in the form of a second matching table.
  • the second match table can include three columns. The first column is the service identifier, the second column is the billing identifier, and the third column is the business rule set. And, the business rule set, the service identifier, and the billing in the same row of the second matching table
  • the logo has a corresponding relationship.
  • the processor 1064 of the device 106 of 805, OTT SP generates user registration information.
  • the user registration information may include a correspondence between the user identifier and the service identifier. For example, assume that the user identifier of the first UE is A1, and the service identifier of the first service is B1. If the device 106 of the OTT SP determines that the first service is free for the first UE, the user registration information may include a correspondence between A1 and B1.
  • the transmitter 1066 of the device 106 of the OTT SP sends the user registration information to the BOSS 104.
  • serial numbers herein should not constitute a limitation on the order.
  • 802 and 803 can be executed before 801.
  • 805 can be executed prior to 802, or 805 can be executed concurrently with 802.
  • the invention is not limited thereto.
  • the charging control device 102 may receive a respective set of service rules transmitted from a plurality of devices of different OTT SPs.
  • the BOSS 104 can also receive user registration information transmitted from a plurality of different OTT SP devices.
  • the device of the OTT SP includes the device of the first OTT SP and the device of the second OTT SP.
  • the device of the first OTT SP is the server of Facebook
  • the device of the second OTT SP is the server of Cool Music.
  • Amazon's business includes Taobao and Alipay. Cool my music offers business including cool music. Then:
  • the operator can configure the following information on the charging control device 102:
  • the service identifier of Taobao is the first service identifier, and the billing identifier is the first billing identifier;
  • the service identifier of the Alipay is the second service identifier, and the billing identifier is the second billing identifier;
  • the service identifier of Cool Music is the third service identifier
  • the billing identifier is the third billing identifier.
  • the device of the first OTT SP can generate a first set of business rules and a second set of business rules.
  • the first set of business rules is used to represent Taobao
  • the second set of business rules is used to represent Alipay.
  • the device of the second OTT SP may generate a third set of business rules.
  • the third set of business rules is used to represent cool music.
  • the device of the first OTT SP transmits the first set of service rules to the charging control device 102.
  • the device of the second OTT SP transmits the second set of service rules to the charging control device 102.
  • the second matching information generated by the charging control device 102 can be as shown in Table 1.
  • the method may further include: the PCEF 108 performs a local cache (cache).
  • PCEF 108 builds a local cache, which can include:
  • the link with the charging control device 102 is first established.
  • the link may be an Internet Content Adaptation Protocol (ICAP) link.
  • ICAP Internet Content Adaptation Protocol
  • the PCEF 108 may send a first request message to the charging control device 102.
  • the first request message may carry a first identifier, where the first identifier is used to indicate that the PCEF 108 supports a cache function.
  • the charging control device 102 After receiving the first request message, the charging control device 102 checks the status of the business rule set on the charging control device 102. If the status is normal, the charging control device 102 transmits a first response message to the PCEF 108.
  • the first response message may carry a second identifier, and the second identifier may be a Ready identifier, where the Ready identifier is used to indicate that the status of the service rule search tree on the charging control device 102 is normal.
  • the PCEF 108 may send a second request message to the charging control device 102.
  • the second request message may carry a start and stop sequence number of the rule that is requested to be delivered.
  • start and stop sequence segments can be from 1 to 10.
  • the charging control device 102 sorts the business rules in the business rule set by heat. After receiving the second request message, the charging control device 102 transmits the service rule according to the start and stop sequence number segment. And sending a second response message to the PCEF 108.
  • the billing control device 102 can send the hottest 1-10 business rules to the PCEF 108.
  • the charging control device 102 can send the seven business rules to the PCEF 108 and carry the Total identifier in the second response message.
  • the PCEF 108 receives the business rule including the start and stop sequence number from the charging control device 102. Thereafter, after the PCEF 108 receives the Total flag from the charging control device 102, the local rule tree is constructed. In this way, PCEF 108 can complete the construction of the local cache.
  • PCEF 108 can also construct a local cache in other ways, which is not limited by the present invention.
  • the processor 1084 of the PCEF 108 may first look up the local cache, and when the business rules are not found, the sender 1086 resends the flow description information to the charging control device 102.
  • the number of communications between the PCEF 108 and the charge control device 102 can be reduced, thereby reducing the pressure on the interface between the PCEF 108 and the charge control device 102.
  • the method shown in FIG. 9 may be further included before the method shown in FIG. 7.
  • the method shown in Figure 9 includes: 801, 802, 803, 804, 805 and
  • the transmitter 1066 of the device 106 of the OTT SP transmits the user registration information to the charging control device 102.
  • the transmitter 1026 of the charging control device 102 transmits the user registration information to the BOSS 104.
  • user registration information is sent from the device 106 of the OTT SP to the BOSS 104 via the charging control device 102.
  • the user registration information received from the device 106 of the OTT SP is forwarded to the BOSS 104 by the charging control device 102.
  • the working pressure of the interface between the device 106 of the OTT SP and the BOSS 104 can be alleviated.
  • FIG. 8 801 to 805 in FIG. 9 can be referred to the description in FIG. 8. To avoid repetition, details are not described herein again.
  • serial numbers herein should not constitute a limitation on the order.
  • 804 can be executed after 807 and 808.
  • the invention is not limited thereto.
  • the method shown in FIG. 10 may be further included before the method shown in FIG. 7.
  • the method shown in Figure 10 includes: 801, 802, 803, 804 and
  • the receiver 1042 of the BOSS 104 acquires user registration information from the UE 112.
  • the UE 112 can actively register with the operator through SMS, telephone, online operation, etc., and provide the user registration information.
  • the user identifier of the second UE is A2
  • the service identifier of the second service is B2. If the second user is registered with the second service, the second UE may actively provide the user registration information to the BOSS 104, and the user registration information includes a correspondence between A2 and B2.
  • FIG. 8 801 to 804 in FIG. 10 can be referred to the description in FIG. 8. To avoid repetition, details are not described herein again.
  • the PCEF 108 acquires the corresponding service identifier and the charging identifier by transmitting the flow description information to the charging control device 102. In this way, it is not necessary to configure the service identifier and the charging identifier on the PCEF 108, which can reduce the workload when configuring on the PCEF 108, thereby reducing the error rate during configuration.
  • FIG. 11 is a signaling flow diagram of a method of charging according to another embodiment of the present invention.
  • the method shown in Figure 11 includes:
  • Receiver 1082 of PCEF 108 receives the data stream transmitted by UE 112.
  • UE 112 may send the data stream to PCEF 108.
  • the data stream may be a data stream of traffic charged to the OTT SP.
  • the UE 112 sends a user activation request to the PCEF 108.
  • the PCEF 108 acquires the PCC policy from the PCRF 110 after receiving the user activation request from the UE 112.
  • the PCRF 110 performs policy authorization and delivers the dynamic rules to the PCEF 108.
  • the PCEF 108 performs policy installation based on the dynamic rules and sends a User Activation Success Response message to the UE 112.
  • the processor 1084 of the PCEF 108 parses the data stream and obtains stream description information of the data stream.
  • the transmitter 1086 of the PCEF 108 transmits the flow description information and the user identification to the charging control device 102.
  • the user ID can be MSISDN.
  • the user identification can be the telephone number of the UE 112.
  • the processor 1024 of the charging control device 102 determines the service identifier and the charging identifier of the service that is charged to the OTT SP according to the flow description information, and determines whether the service identifier has a corresponding relationship with the user identifier.
  • the service identifier may be the service ID of the service, and the charging identifier may be an RG.
  • the second matching information may be stored in the charging control device 102, where the second matching information includes a correspondence between a service rule set, a service identifier, and a charging identifier.
  • the service identifier and the charging identifier corresponding to the certain service rule set may be determined according to the second matching information, and the service corresponding to the certain service rule set may be determined.
  • the identification and charging identifier is determined as a service corresponding to the flow description information
  • the identifier and the charging identifier that is, the service identifier and the charging identifier corresponding to the data stream.
  • the first matching information may be stored in the charging control device 102, where the first matching information includes a correspondence between the service identifier and the user identifier.
  • the charging control device 102 can determine, according to the first matching information, whether the user identifier received from the PCEF 108 has a corresponding relationship with the service identifier determined according to the flow description information.
  • the processor 1024 of the charging control device 102 determines that the user identifier received from the PCEF 108 has a corresponding relationship with the service identifier determined according to the flow description information, the processor 1024 of the charging control device 102 determines the transmitter of the charging control device 102. 1026 sends the service identity and the charging identity to the PCEF 108.
  • the charging control device Transmitter 1026 of 102 may send a null message to PCEF 108 or not send any message.
  • the PCEF 108 when the UE 112 performs the service access, the PCEF 108 sends the flow description information to the charging control device 102, and the charging control device 102 determines the service identifier and the charging identifier corresponding to the data flow and sends the The PCEF 108, in this way, does not need to configure the service identifier and the charging identifier on the PCEF 108, and the PCEF 108 can obtain the service identifier and the charging identifier corresponding to the data stream, thereby reducing the workload during configuration.
  • the processor 1084 of the PCEF 108 performs online/offline charging based on the service identification and the charging identifier.
  • the billing is for the service with the service identifier.
  • the PCEF 108 receives an empty message from the charging control device 102, or if the PCEF 108 does not receive any message sent by the charging control device 102 for a predetermined period of time, then the PCEF 108 follows the prior art manner. Perform online/offline billing.
  • the PCEF 108 can implement the online/offline charging function together with the BOSS 104. After 1106, it may also include:
  • the transmitter 1086 of the PCEF 108 sends a CCR message to the BOSS 104.
  • the CCR message may include a service identity and a charging identity.
  • the processor 1044 of the BOSS 104 performs unified pricing for the service identifier.
  • the BOSS 104 does not need to be differentiated according to the user. That is, in the embodiment shown in FIG. 11, the charging control device 102 determines whether the service identifier has a corresponding relationship with the user identifier, that is, the charging control device 102 determines whether the user has registered the service with the service identifier. , Therefore, the BOSS 104 does not need to receive the user registration information, and it is not necessary to determine whether the UE 112 has registered the traffic 800 service with the service identifier according to the user registration information, and the BOSS 104 can directly perform the unified rating, thereby reducing the workload of the BOSS 104.
  • the transmitter 1046 of the BOSS 104 sends a CCA message to the PCEF 108.
  • PCEF 108 and BOSS 104 can collectively complete online/offline billing.
  • the method shown in FIG. 12 may be further included before the method shown in FIG.
  • the method shown in Figure 12 includes: 801, 802, 803, 804, 805, 807 and
  • the processor 1024 of the charging control device 102 generates first matching information according to the user registration information.
  • the first matching information includes a correspondence between the service identifier and the user identifier.
  • the first matching information may be in the form of a first matching table.
  • the first match table can include two columns.
  • the first column is the service identifier and the second column is the user ID.
  • the service identifier and the user identifier in the same row of the first matching table have a corresponding relationship.
  • the first matching information can be as shown in Table 2.
  • serial numbers herein should not constitute a limitation on the order.
  • 810 can be performed prior to 804, or 810 can be performed concurrently with 804.
  • the invention is not limited thereto.
  • the method shown in FIG. 13 may be further included before the method shown in FIG.
  • the method shown in FIG. 13 includes: 801, 802, 803, 804, 805, 806,
  • the transmitter 1046 of the BOSS 104 transmits the user registration information to the charging control device 102.
  • the processor 1024 of the charging control device 102 generates first matching information.
  • 801 to 806 in FIG. 13 can be referred to the description in FIG. 8, and 810 in FIG. 13 can be used. Referring to the description in FIG. 12, in order to avoid repetition, details are not described herein again.
  • user registration information is transmitted from the device 106 of the OTT SP to the charging control device 102 via the BOSS 104.
  • the pressure of the interface between the device 106 of the OTT SP and the charging control device 102 can be alleviated.
  • the method shown in FIG. 14 may be further included before the method shown in FIG.
  • the method shown in FIG. 14 includes: 801, 802, 803, 804, 809,
  • the transmitter 1046 of the BOSS 104 transmits the user registration information to the charging control device 102.
  • the processor 1024 of the charging control device 102 generates first matching information.
  • 801 to 804 in FIG. 14 can be referred to the description in FIG. 8
  • 809 in FIG. 14 can be referred to the description in FIG. 10
  • 810 in FIG. 14 can be referred to the description in FIG. 12. To avoid repetition, no longer here. Narration.
  • the PCEF 108 when the UE 112 performs traffic 800 service access, the PCEF 108 transmits the flow description information and the user identification to the charging control device 102.
  • the corresponding service identifier and the charging identifier are determined by the charging control device 102, and the charging control device 102 determines whether the service identifier has a corresponding relationship with the user identifier.
  • the PCEF 108 can receive the service identifier and the charging identifier sent by the charging control device 102.
  • FIG. 15 is a signaling flow diagram of a method of charging according to another embodiment of the present invention.
  • the method shown in FIG. 15 includes:
  • the UE 112 sends a user activation request to the PCEF 108.
  • the transmitter 1086 of the PCEF 108 sends a CCR-1 message to the PCRF 110.
  • the receiver 1082 of the PCEF 108 after receiving the user activation request from the UE 112, sends a CCR-1 message to the PCRF 110 to further acquire the PCC policy from the PCRF 110.
  • the processor 1104 of the PCRF 110 determines the PCC policy authorization for the UE 112.
  • the PCRF 110 authorizes the service identifier and the charging identifier of the traffic 800 service registered by the UE 112 as the PCC policy of the UE 112.
  • the transmitter 1106 of the PCRF 110 sends a CCA-1 message to the PCEF 108.
  • the PCRF 110 can send dynamic rules to the PCEF 108.
  • the dynamic rule includes a Traffic Detection Function (TDF) Application Identifier. And also includes a charging identifier corresponding to the TDF Application Identifier field.
  • TDF Traffic Detection Function
  • the TDF Application Identifier field indicates the service identifier of the traffic 800 service registered by the UE 112.
  • the transmitter 1086 of the PCEF 108 sends a User Activation Success Response message to the UE 112.
  • the receiver 1082 of the PCEF 108 receives the data stream transmitted by the UE 112.
  • the processor 1084 of the PCEF 108 parses the data stream and obtains stream description information of the data stream.
  • the processor 1084 of the PCEF 108 further determines whether the UE 112 is registered with the service charged to the OTT SP, that is, whether the UE 112 has the registered traffic 800 service.
  • the transmitter 1086 of the PCEF 108 transmits the flow description information to the charging control device 102.
  • the PCEF 108 After determining that the UE 112 has registered the service charged to the OTT SP, the PCEF 108 transmits the flow description information to the charging control device 102, so that the subsequent charging control device 102 can perform only for the UE that has registered the service. better.
  • the PCEF 108 determines by decision that the UE 112 is not registering any traffic 800 traffic, then the PCEF 108 performs online/offline charging in accordance with prior art methods.
  • the processor 1024 of the charging control device 102 determines the service identifier according to the flow description information.
  • the third matching information may be stored in the charging control device 102, where the third matching information includes a correspondence between the service rule set and the service identifier.
  • the service identifier corresponding to the certain service rule set may be determined according to the third matching information, and the service identifier corresponding to the certain service rule set is determined to be
  • the traffic description corresponds to the service identifier, that is, the service identifier corresponding to the data flow.
  • the transmitter 1026 of the charging control device 102 transmits the service identification to the PCEF 108.
  • the processor 1084 of the PCEF 108 performs online/offline charging based on the service identifier.
  • the processor 1084 of the PCEF 108 matches the TDF Application Identifier field according to the received service identifier, and can determine the corresponding charging identifier. And, the PCEF 108 performs online/offline charging according to the corresponding charging identifier.
  • the PCEF 108 when the UE 112 performs the traffic 800 service access, the PCEF 108 obtains the service identifier by sending the flow description information to the charging control device 102, so that the service identifier does not need to be configured on the PCEF 108, and the configuration can be reduced. The amount of work, which in turn reduces the error rate during configuration.
  • the PCEF 108 can implement the online/offline charging function together with the BOSS 104. After 1511, it may also include:
  • the transmitter 1086 of the PCEF 108 sends a CCR message to the BOSS 104.
  • the CCR message may include a service identity and a charging identity.
  • the processor 1044 of the BOSS 104 performs unified pricing for the service identifier. That is, the BOSS 104 does not need to be differentiated according to the user.
  • the dynamic rule delivered by the PCRF 110 includes the service identifier and the charging identifier of the traffic 800 service registered by the UE 112, without the BOSS 104 being differentiated according to the user. This can reduce the workload of BOSS.
  • the transmitter 1046 of the BOSS 104 sends a CCA message to the PCEF 108.
  • PCEF 108 and BOSS 104 can collectively complete online/offline billing.
  • the method shown in FIG. 16 may be further included before the method shown in FIG.
  • the method shown in FIG. 16 includes: 801, 802, 803, 805, 807,
  • the processor 1024 of the charging control apparatus 102 generates third matching information, where the third matching information includes a correspondence between the service identifier and the service rule set.
  • the third matching information may be in the form of a third matching table.
  • the third match table can include two columns. The first column is the business identifier and the second column is the business rule set. Moreover, the business rule set and the service identifier located in the same row of the third matching table have a corresponding relationship.
  • the transmitter 1026 of the charging control device 102 transmits the user registration information, the service identifier, and the charging identifier to the PCRF 110.
  • the processor 1104 of the PCRF 110 generates a PCC policy.
  • each of the M UEs may register one or more traffic 800 services.
  • the PCC policy includes the PCC policies of the M UEs.
  • 8013 may be executed before 807, or 8013 may be executed after 8014.
  • the invention is not limited thereto.
  • the method shown in FIG. 17 may be further included before the method shown in FIG.
  • the method shown in FIG. 17 includes: 801, 802, 803, 805, 806, 813,
  • the transmitter 1026 of the charging control device 102 transmits the service identification and the charging identifier to the PCRF 110.
  • the transmitter 1046 of the BOSS 104 sends the user registration information to the PCRF 110.
  • the processor 1104 of the PCRF 110 generates a PCC policy.
  • serial numbers herein should not constitute a limitation on the order.
  • 816 and 817 can be executed simultaneously.
  • 816 and 817 can be executed before 813.
  • the invention is not limited thereto.
  • the method shown in FIG. 18 may be further included before the method shown in FIG.
  • the method shown in FIG. 18 includes: 801, 802, 803, 809, 813, 816, 817, and 815.
  • 801 to 803 in FIG. 18 can be referred to the description in FIG. 8, 809 in FIG. 18 can be referred to the description in FIG. 10, and 813 and 815 in FIG. 18 can be referred to the description in FIG. 16, and 816 in FIG. And 817 can refer to the description in FIG. 17, and to avoid repetition, details are not described herein again.
  • the PCEF 108 determines that the UE 112 has registered the traffic 800 service
  • the flow description information is sent to the charging control device 102.
  • the corresponding service identifier is determined by the charging control device 102.
  • the PCEF 108 can receive the service identity sent by the charging control device 102 and perform charging in conjunction with the dynamic rules acquired from the PCRF 110. In this way, it is not necessary to configure the service identifier on the PCEF 108, and the workload of the PCEF 108 configuration and the workload of the BOSS 104 can be reduced.
  • the charging of the traffic 800 service is combined with the existing PCC policy, and is more in line with the standard architecture of the 3rd Generation Partnership Project (3GPP).
  • the receiving unit 1022 is configured to receive flow description information from the PCEF, where the flow description information is obtained by the PCEF according to the data flow received from the UE.
  • the processor 1024 is configured to determine, according to the flow description information received by the receiver 1022, a service identifier corresponding to the data flow.
  • the sender 1026 is configured to send the service identifier determined by the processor 1024 to the PCEF, so that the PCEF charges the service according to the service identifier.
  • the various components in the billing control device 102 are coupled together by a bus system, wherein the bus system includes a power bus, a control bus, a status signal bus, and the like in addition to the data bus.
  • Processor 1024 may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the foregoing method may be completed by an integrated logic circuit of hardware in the processor 1024 or an instruction in a form of software.
  • the processor 1024 may be a general-purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), or the like. Programmable logic devices, discrete gates or transistor logic devices, discrete hardware components.
  • DSP digital signal processor
  • ASIC application specific integrated circuit
  • FPGA field programmable gate array
  • the general purpose processor may be a microprocessor or the processor or any conventional processor or the like.
  • the steps of the method disclosed in the embodiments of the present invention may be directly implemented by the hardware decoding processor, or may be performed by a combination of hardware and software modules in the decoding processor.
  • the software module can be located in a conventional storage medium such as random access memory, flash memory, read only memory, programmable read only memory or electrically erasable programmable memory, registers, and the like.
  • the storage medium is located in the memory 1024, and the processor 1024 reads the information in the memory and completes the steps of the above method in combination with its hardware.
  • the memory in the embodiments of the present invention may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memory.
  • the non-volatile memory may be a read-only memory (ROM), a programmable read only memory (PROM), an erasable programmable read only memory (Erasable PROM, EPROM), or an electric Erase programmable read only memory (EEPROM) or flash memory.
  • the volatile memory can be a Random Access Memory (RAM) that acts as an external cache.
  • RAM Random Access Memory
  • many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (Synchronous DRAM).
  • SDRAM double data rate synchronous dynamic random access memory
  • Double Data Rate SDRAM DDR SDRAM
  • ESDRAM Enhanced Synchronous Dynamic Random Access Memory
  • SDRAM Synchronous Connection Dynamic Random Access Memory
  • DR RAM Direct Memory Bus
  • the embodiments described herein can be implemented in hardware, software, firmware, middleware, microcode, or a combination thereof.
  • the processing unit can be implemented in one or more Application Specific Integrated Circuits (ASICs), Digital Signal Processing (DSP), Digital Signal Processing Equipment (DSP Device, DSPD), programmable Programmable Logic Device (PLD), Field-Programmable Gate Array (FPGA), general purpose processor, controller, microcontroller, microprocessor, other for performing the functions described herein In an electronic unit or a combination thereof.
  • ASICs Application Specific Integrated Circuits
  • DSP Digital Signal Processing
  • DSP Device Digital Signal Processing Equipment
  • PLD programmable Programmable Logic Device
  • FPGA Field-Programmable Gate Array
  • a code segment can represent a procedure, a function, a subprogram, a program, a routine, a subroutine, a module, a software group, a class, or any combination of instructions, data structures, or program statements.
  • a code segment can be combined into another code segment or hardware circuit by transmitting and/or receiving information, data, arguments, parameters or memory contents. Information, arguments, parameters, data, etc. can be communicated, forwarded, or transmitted using any suitable means including memory sharing, messaging, token passing, network transmission, and the like.
  • the techniques described herein can be implemented by modules (eg, procedures, functions, and so on) that perform the functions described herein.
  • the software code can be stored in a memory unit and executed by the processor.
  • the memory unit can be implemented in the processor or external to the processor, in the latter case the memory unit can be communicatively coupled to the processor via various means known in the art.
  • the receiver 1022 is configured to obtain a service identifier and a charging identifier pre-configured by the operator, and is further configured to receive a service rule set sent by the device of the OTT SP.
  • the processor 1024 is configured to generate third matching information.
  • the third matching information includes a correspondence between the service identifier and the set of business rules.
  • the sender 1026 is configured to send the service identifier and the charging identifier to the PCRF.
  • the processor 1024 can search the third matching information according to the flow description information to determine a corresponding service identifier.
  • the third matching information refer to the description of 813 in the embodiment of FIG. 16. To avoid repetition, details are not described herein again.
  • the receiving flow description letter is received.
  • the receiver 1022 is further configured to receive user registration information sent by the device of the OTT SP.
  • Transmitter 1026 is also used to send the user registration information to the PCRF.
  • the processor 1024 is further configured to determine, according to the flow description information received by the receiver 1022, a charging identifier corresponding to the data flow.
  • the sender 1026 is further configured to send the charging identifier to the PCEF.
  • the receiver 1022 is configured to obtain a service identifier and a charging identifier pre-configured by the operator, and is further configured to receive a service rule set sent by the device of the OTT SP.
  • the processor 1024 is configured to generate second matching information.
  • the second matching information includes a correspondence between a service rule set, a service identifier, and a charging identifier.
  • the second matching information refer to the description of 804 in the embodiment of FIG. 8. To avoid repetition, details are not described herein again.
  • the second matching information can be as shown in Table 1.
  • the processor 1024 may search the second matching information according to the flow description information to determine a corresponding service identifier and a charging identifier.
  • the processor 1024 may determine that the corresponding service identifier and the charging identifier are respectively the second service identifier and The second billing identifier.
  • the receiver 1022 is further configured to receive the user registration information sent by the device of the OTT SP.
  • the sender 1026 is also used to send the user registration information to the BOSS.
  • the receiver 1022 may further receive a user identifier of the UE sent by the PCEF.
  • the processor 1024 is specifically configured to determine, according to the flow description information, a service identifier and a charging identifier corresponding to the data flow, and determine whether the user identifier has a corresponding relationship with the service identifier.
  • the sender 1026 is specifically configured to send the service identifier and the charging identifier to the PCEF.
  • the receiver 1022 is configured to obtain a service identifier and a charging identifier pre-configured by the operator, and is further configured to receive a service rule set sent by the device of the OTT SP.
  • the receiver 1022 is further configured to receive the device registration information sent by the device of the OTT SP or the BOSS.
  • the processor 1024 is configured to generate second matching information.
  • the second matching information includes a correspondence between a service rule set, a service identifier, and a charging identifier.
  • the processor 1024 is further configured to generate first matching information, where the first matching information includes a service identifier and The correspondence between the user IDs.
  • the processor 1024 can determine whether the user identifier has a corresponding relationship with the service identifier by searching the first matching information.
  • first matching information refer to the description of 810 in the embodiment of FIG. 13. To avoid repetition, details are not described herein again.
  • the processor 1024 can determine, according to the first matching information, that the second service identifier has a corresponding relationship with the fourth user identifier.
  • the user registration information may be received by the receiver 1022 from the device of the OTT SP.
  • the user registration information may also be sent by the OTT SP device to the BOSS, and then received by the receiver 1022 from the BOSS.
  • the user registration information may be received by the receiver 1022 from the BOSS.
  • the embodiment of the present invention provides a charging control apparatus for charging a service charged to an OTT SP.
  • the operator can automatically synchronize to other network elements through the process.
  • the PCEF in each provincial network can obtain the required service identifier and charging identifier from the charging control device. It can eliminate the need for repeated configuration on the PCEF in each provincial network, so operators do not need to consider the Deep Packet Inspection (DPI) capability between different PCEFs produced by different vendors in each provincial network. Differences in configuration, configuration, and rule configuration can greatly reduce the workload of the operator's operation and maintenance department and avoid the impact of mismatch or mismatch during configuration.
  • DPI Deep Packet Inspection
  • the billing control device is an independent device of the operator, which is easy to maintain and expand, and can support the deployment of millions of services.
  • a receiver 1082 configured to receive a data stream sent by the UE
  • the processor 1084 is configured to parse the data stream, and determine flow description information of the data stream
  • a transmitter 1086 configured to send the flow description information to a charging control device
  • the receiver 1082 is further configured to receive a service identifier sent by the charging control device, where the service The identifier is determined by the charging control device according to the flow description information;
  • the processor 1084 is further configured to perform online/offline charging on the service according to the service identifier.
  • the processor 1084 is further configured to determine whether the UE is registered with the service.
  • the transmitter 1086 transmits the flow description information to the charging control device.
  • the receiver 1082 is further configured to receive dynamic rules from the PCRF before the receiver 1082 receives the data stream transmitted by the UE.
  • the dynamic rule includes a traffic detection function (TDF) application identifier (Application Identifier), and further includes a charging identifier corresponding to the TDF Application Identifier field.
  • TDF traffic detection function
  • Application Identifier Application Identifier
  • the processor 1084 is specifically configured to match the TDF Application Identifier field according to the service identifier received by the receiver 1082, and further determine the corresponding charging identifier. Further, the processor 1084 can perform online/offline charging according to the charging identifier.
  • the processor 1084 performs online/offline charging according to the charging identifier, and the online/offline charging function may be implemented by the PCEF and the BOSS.
  • the sender 1086 can also send a Credit Control Request (CCR) message to the BOSS. After the BOSS performs the rating, the receiver 1082 receives the Credit Control Answer (CCA) message sent by the BOSS.
  • CCR Credit Control Request
  • CCA Credit Control Answer
  • the transmitter 1086 is further configured to send the user identifier of the UE to the charging control device.
  • the receiver 1082 is specifically configured to receive the service identifier and the charging identifier from the charging control device.
  • the processor 1084 is configured to perform online/offline charging according to the service identifier and the charging identifier.
  • the billing is for a service with a service identifier.
  • the processor 1084 performs online/offline charging according to the charging identifier, and the online/offline charging function may be implemented by the PCEF and the BOSS.
  • Transmitter 1086 can also send a CCR message to BOSS. And after the BOSS performs the differential rating, the receiver 1082 receives the CCA message sent by the BOSS.
  • the receiver 1102 is configured to receive a service identifier and a charging identifier from the charging control device, and receive user registration information from the charging control device or the BOSS.
  • the processor 1104 is configured to generate a PCC policy according to the user registration information, the service identifier, and the charging identifier received by the receiver 1102.
  • the receiver 1102 may receive user registration information from the charging control device or the BOSS.
  • the user registration information is generated by the device of the OTT SP and sent to the charging control device or the BOSS.
  • the receiver 1102 may receive the user registration information from the BOSS.
  • the user registration information is actively registered by the UE.
  • the receiver 1042 is configured to receive user registration information.
  • the transmitter 1046 is configured to send the user registration information to the charging control device.
  • the receiver 1042 may receive the user registration information from the device of the OTT SP.
  • the receiver 1042 may receive the user registration information from the UE.
  • BOSS 104 may also include a processor 1044. Further, when the UE performs service access, the receiver 1042 can receive the CCR message sent by the PCEF. The processor 1044 can perform a rating. Transmitter 1046 can send a CCA message to the PCEF. Wherein, the processor 1044 does not need to be differentiated according to the user when the price is approved.
  • the receiver 1042 may receive the user registration information from the device of the OTT SP or to the charging control device. If the service charged to the OTT SP is a forward paying service, the receiver 1042 may receive the user registration information from the UE.
  • the receiver 1042 can receive the CCR message sent by the PCEF.
  • the processor 1044 can perform differentiated pricing based on the user registration information.
  • Transmitter 1046 can send a CCA message to the PCEF.
  • the receiver 1042 after receiving the user registration information, the receiver 1042 does not send to the charging control device, so that the BOSS 104 subsequently performs differentiated pricing according to the user registration information.
  • the processor 1064 is configured to generate a business rule set.
  • the transmitter 1066 is configured to send the service rule set to the charging control apparatus.
  • the processor 1064 is further configured to generate user registration information, and the further transmitter 1066 is further configured to send the user registration information to the charging control device. Or BOSS.
  • FIG. 19 is a schematic structural diagram of a system for charging according to an embodiment of the present invention.
  • the system 10 shown in FIG. 19 can include a billing control device 102, a PCEF 108, a PCRF 110, and a BOSS 104.
  • FIG. 20 is a flow chart of a method of charging in accordance with an embodiment of the present invention.
  • the method shown in FIG. 20 includes: when the user equipment UE accesses a service charged to an OTT service provider SP above the operator,
  • the service identifier is sent to the PCEF, so that the PCEF charges the service according to the service identifier.
  • the PCEF when the UE accesses the service, the PCEF sends the flow description information to the charging control device, and the charging control device determines the service identifier and the charging identifier corresponding to the data flow, and sends the information to the PCEF, so that The service identifier and the charging identifier are not required to be configured on the PCEF.
  • the PCEF can obtain the service identifier and the charging identifier corresponding to the data flow, thereby reducing the workload during configuration.
  • the determining, according to the flow description information, the service identifier corresponding to the data flow including: determining, according to the flow description information, a service identifier and a meter corresponding to the data flow.
  • the sending the service identifier to the PCEF includes: sending the service identifier and the charging identifier to the PCEF.
  • the method further includes: receiving, by the PCEF, a user identifier of the UE; determining whether the user identifier has a corresponding relationship with the service identifier;
  • the method before receiving the flow description information from the PCEF, the method further includes: receiving user registration information sent by the device of the OTT SP or the service operation support system BOSS; generating, according to the user registration information First matching information, the first matching information includes Correspondence between the user ID and the service ID.
  • the determining whether the user identifier has a corresponding relationship with the service identifier includes: determining, according to the first matching information, whether the user identifier and the service identifier have corresponding relationship.
  • the method before receiving the flow description information from the PCEF, the method further includes: receiving user registration information sent by the device of the OTT SP; and sending the user registration information to the service operation support system BOSS .
  • the method before receiving the flow description information from the PCEF, the method further includes: acquiring a service identifier and a charging identifier configured by the operator, and receiving a service rule set sent by the device of the OTT SP; And generating, according to the set of the service rules, the second matching information, where the second matching information includes a correspondence between the service rule set, the service identifier, and the charging identifier.
  • the determining, according to the flow description information, the service identifier and the charging identifier corresponding to the data flow including: determining, according to the second matching information, the data flow Corresponding service identifier and billing identifier.
  • the method before receiving the flow description information from the PCEF, the method further includes: acquiring a service identifier and a charging identifier configured by the operator, and receiving a service rule set sent by the device of the OTT SP; Sending the service identifier and the charging identifier to the policy and charging rule function PCRF; generating third matching information according to the service rule set, where the third matching information includes a service rule set and a service identifier Correspondence between the two.
  • the method before receiving the flow description information from the PCEF, the method further includes: receiving user registration information sent by the device of the OTT SP; and sending the user registration information to the PCRF.
  • the charging method shown in Fig. 20 can be implemented by the charging control device 102 in the foregoing embodiment.
  • FIG. 21 is a flow chart of a method of charging according to another embodiment of the present invention.
  • the method shown in FIG. 21 is performed by the policy and charging execution function PCEF.
  • the method includes:
  • the PCEF when the UE accesses the service, the PCEF sends the flow description information to the charging control device, and the charging control device determines the service identifier and the charging identifier corresponding to the data flow, and sends the information to the PCEF, so that The service identifier and the charging identifier are not required to be configured on the PCEF.
  • the PCEF can obtain the service identifier and the charging identifier corresponding to the data flow, thereby reducing the workload during configuration.
  • the receiving the service identifier sent by the charging control device includes: receiving a service identifier and a charging identifier sent by the charging control device, the service identifier, and the charging The identifier is determined by the charging control device according to the flow description information;
  • performing online/offline charging on the service according to the service identifier including: performing online/offline charging on the service according to the service identifier and the charging identifier.
  • the method before the sending the flow description information to the charging control device, the method further includes: determining whether the UE is registered with the service;
  • the sending the flow description information to the charging control device includes: when determining that the UE registers the service, sending the flow description information to the charging control device.
  • the method of charging shown in Fig. 21 can be implemented by the PCEF 108 in the foregoing embodiment.
  • PCRF Policy and Charging Rules function
  • the PCRF generates a PCC policy according to the service identifier and the charging identifier received by the charging control device, and receives the user registration information from the charging control device or the BOSS, and can be used to charge the OTT SP by the PCEF.
  • the service is billed.
  • the service identifier and the charging identifier corresponding to the data flow can be obtained by the PCEF without configuring the service identifier and the charging identifier on the PCEF, thereby reducing the workload during configuration.
  • the method of charging shown in FIG. 22 can be implemented by the aforementioned PCRF 110.
  • FIG. 23 is a flow chart of a method of charging according to another embodiment of the present invention.
  • the method shown in Figure 23 is performed by the business operation support system BOSS, including:
  • the method 2301 when the service that is charged to the OTT service provider SP on the operator is a backward-paid service, the method 2301 includes: receiving the user registration information from the device of the OTT SP. Or, when the service that is charged to the OTT service provider SP on the operator is a forward-paid service, the method 2301 includes: receiving the user registration information from the user equipment UE.
  • the method of charging shown in FIG. 23 can be implemented by the aforementioned BOSS 104.
  • FIG. 24 is a flow chart of a method of charging in accordance with another embodiment of the present invention.
  • the method shown in Figure 24 is performed by an OTT service provider SP device above the operator, including:
  • the method when the service that is charged to the OTT SP is a backward paid service, the method further includes: generating user registration information; and sending the user registration information to the charging control device or service operation support System BOSS.
  • the method of charging shown in FIG. 24 can be implemented by the aforementioned device 106 of the OTT SP.
  • the disclosed system, apparatus, and method may be implemented in other manners.
  • the device embodiments described above are merely illustrative.
  • the division of the unit is only a logical function division.
  • there may be another division manner for example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored or not executed.
  • the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be in an electrical, mechanical or other form.
  • the units described as separate components may or may not be physically separate.
  • the components displayed for the unit may or may not be physical units, ie may be located in one place, or may be distributed over multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of the embodiment.
  • each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
  • the functions may be stored in a computer readable storage medium if implemented in the form of a software functional unit and sold or used as a standalone product.
  • the technical solution of the present invention which is essential or contributes to the prior art, or a part of the technical solution, may be embodied in the form of a software product, which is stored in a storage medium, including
  • the instructions are used to cause a computer device (which may be a personal computer, server, or network device, etc.) to perform all or part of the steps of the methods described in various embodiments of the present invention.
  • the foregoing storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, and the like, which can store program codes. .

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • General Physics & Mathematics (AREA)
  • Physics & Mathematics (AREA)
  • General Business, Economics & Management (AREA)
  • Strategic Management (AREA)
  • Theoretical Computer Science (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Charge And Discharge Circuits For Batteries Or The Like (AREA)
  • Meter Arrangements (AREA)
  • Telephonic Communication Services (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Telephone Function (AREA)
PCT/CN2014/091929 2014-11-21 2014-11-21 计费控制装置、方法及系统 WO2016078090A1 (zh)

Priority Applications (10)

Application Number Priority Date Filing Date Title
PCT/CN2014/091929 WO2016078090A1 (zh) 2014-11-21 2014-11-21 计费控制装置、方法及系统
KR1020177016819A KR101933594B1 (ko) 2014-11-21 2014-11-21 과금 제어 장치, 방법 및 시스템
RU2017121274A RU2669522C1 (ru) 2014-11-21 2014-11-21 Устройство, способ и система управления начислением платы
CA2968439A CA2968439C (en) 2014-11-21 2014-11-21 Charging control apparatus, method, and system
BR112017010583-7A BR112017010583B1 (pt) 2014-11-21 2014-11-21 Aparelho e método de controle de cobrança
JP2017527569A JP6508660B2 (ja) 2014-11-21 2014-11-21 課金制御装置、方法、およびシステム
CN201480002360.3A CN105814930B (zh) 2014-11-21 2014-11-21 计费控制装置、方法及系统
AU2014411891A AU2014411891B2 (en) 2014-11-21 2014-11-21 Charging control apparatus, method, and system
EP14906599.7A EP3214862B1 (en) 2014-11-21 2014-11-21 Charging control device and method
US15/600,544 US10666812B2 (en) 2014-11-21 2017-05-19 Charging control apparatus, method, and system

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2014/091929 WO2016078090A1 (zh) 2014-11-21 2014-11-21 计费控制装置、方法及系统

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US15/600,544 Continuation US10666812B2 (en) 2014-11-21 2017-05-19 Charging control apparatus, method, and system

Publications (1)

Publication Number Publication Date
WO2016078090A1 true WO2016078090A1 (zh) 2016-05-26

Family

ID=56013105

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2014/091929 WO2016078090A1 (zh) 2014-11-21 2014-11-21 计费控制装置、方法及系统

Country Status (10)

Country Link
US (1) US10666812B2 (ko)
EP (1) EP3214862B1 (ko)
JP (1) JP6508660B2 (ko)
KR (1) KR101933594B1 (ko)
CN (1) CN105814930B (ko)
AU (1) AU2014411891B2 (ko)
BR (1) BR112017010583B1 (ko)
CA (1) CA2968439C (ko)
RU (1) RU2669522C1 (ko)
WO (1) WO2016078090A1 (ko)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108207006A (zh) * 2016-12-20 2018-06-26 中国移动通信有限公司研究院 数据域停机策略控制方法及通信系统
CN108307336A (zh) * 2016-09-26 2018-07-20 中国电信股份有限公司 动态策略恢复方法和 pcrf 以及系统
US11489969B2 (en) 2017-11-16 2022-11-01 Huawei Technologies Co., Ltd. Charging method, apparatus, and system

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3238049B1 (en) * 2014-12-24 2020-09-16 Orange A method and system for dynamically allocating operator specific billing rules for date exchange by an application on a user equipment

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101729996A (zh) * 2008-10-17 2010-06-09 中国移动通信集团天津有限公司 为彩铃用户提供集团广告服务的系统和方法
CN102647698A (zh) * 2012-04-10 2012-08-22 华为技术有限公司 一种策略和计费控制pcc系统与方法
CN103200552A (zh) * 2013-03-20 2013-07-10 广州从兴电子开发有限公司 一种通信控制方法
CN103888928A (zh) * 2014-03-04 2014-06-25 华为技术有限公司 一种业务策略控制方法及系统
WO2014110719A1 (zh) * 2013-01-15 2014-07-24 华为技术有限公司 计费的方法及设备

Family Cites Families (17)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
SE0301967D0 (sv) * 2003-03-27 2003-07-03 Ericsson Telefon Ab L M A method and apparatus for supporting content purchases over a public communication network
US7979890B2 (en) * 2005-05-03 2011-07-12 Cisco Technology, Inc. System and method for handling per subscriber application and bearer authorization in a communications environment
CN101232385B (zh) * 2007-01-22 2012-06-27 华为技术有限公司 在微波接入全球互通系统中进行计费的方法及系统
CN101325780B (zh) * 2007-06-15 2010-07-07 华为技术有限公司 策略控制实现方法和系统、及策略和计费执行实体
US8473546B2 (en) * 2010-05-28 2013-06-25 Alcatel Lucent Minimizing PCC rule instantiation latency
EP2596653B1 (en) * 2010-07-21 2018-10-31 Telefonaktiebolaget LM Ericsson (publ) Technique for packet flow analysis
US8601058B2 (en) * 2011-03-24 2013-12-03 Cisco Technology, Inc. Mobile videoconferencing
US9473986B2 (en) * 2011-04-13 2016-10-18 Interdigital Patent Holdings, Inc. Methods, systems and apparatus for managing and/or enforcing policies for managing internet protocol (“IP”) traffic among multiple accesses of a network
US20120296784A1 (en) * 2011-05-20 2012-11-22 Brenda Ann Connor Controlling quality of service provided to over the top applications in a telecommunications system
US8755342B2 (en) * 2011-10-05 2014-06-17 Cisco Technology, Inc. System and method for dynamic bearer selection for immersive video collaboration in mobile wireless networks
CN103220651A (zh) * 2012-01-21 2013-07-24 阿尔卡特朗讯 一种对应用层数据进行计费控制的方法与设备
US9807644B2 (en) * 2012-02-17 2017-10-31 Interdigital Patent Holdings, Inc. Hierarchical traffic differentiation to handle congestion and/or manage user quality of experience
US8818347B2 (en) * 2012-07-10 2014-08-26 Telefonaktiebolaget L M Ericsson (Publ) Node and method for service specific management
EP2898653B1 (en) * 2012-09-19 2016-07-20 Telefonaktiebolaget LM Ericsson (publ) Method and node for controlling resources for a media service as well as a corresponding system and computer program
CN102917331B (zh) * 2012-10-24 2015-07-15 中国联合网络通信集团有限公司 策略控制方法及系统
CN104349298B (zh) * 2013-08-09 2019-07-02 中兴通讯股份有限公司 一种网络计费方法、控制器、数据中心及系统
CN104378749B (zh) * 2013-08-12 2020-03-10 中兴通讯股份有限公司 基于sdn epc网络的计费实现方法与系统

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101729996A (zh) * 2008-10-17 2010-06-09 中国移动通信集团天津有限公司 为彩铃用户提供集团广告服务的系统和方法
CN102647698A (zh) * 2012-04-10 2012-08-22 华为技术有限公司 一种策略和计费控制pcc系统与方法
WO2014110719A1 (zh) * 2013-01-15 2014-07-24 华为技术有限公司 计费的方法及设备
CN103200552A (zh) * 2013-03-20 2013-07-10 广州从兴电子开发有限公司 一种通信控制方法
CN103888928A (zh) * 2014-03-04 2014-06-25 华为技术有限公司 一种业务策略控制方法及系统

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3214862A4 *

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108307336A (zh) * 2016-09-26 2018-07-20 中国电信股份有限公司 动态策略恢复方法和 pcrf 以及系统
CN108307336B (zh) * 2016-09-26 2020-11-03 中国电信股份有限公司 动态策略恢复方法和 pcrf 以及系统
CN108207006A (zh) * 2016-12-20 2018-06-26 中国移动通信有限公司研究院 数据域停机策略控制方法及通信系统
US11489969B2 (en) 2017-11-16 2022-11-01 Huawei Technologies Co., Ltd. Charging method, apparatus, and system
JP7478267B2 (ja) 2017-11-16 2024-05-02 華為技術有限公司 課金方法、装置、及びシステム

Also Published As

Publication number Publication date
BR112017010583A2 (pt) 2018-04-03
EP3214862A4 (en) 2017-11-29
RU2669522C1 (ru) 2018-10-11
CN105814930B (zh) 2019-05-28
AU2014411891B2 (en) 2018-12-06
KR20170085125A (ko) 2017-07-21
EP3214862B1 (en) 2020-05-20
KR101933594B1 (ko) 2018-12-28
JP2018504003A (ja) 2018-02-08
US20170257490A1 (en) 2017-09-07
JP6508660B2 (ja) 2019-05-08
BR112017010583B1 (pt) 2022-12-06
CN105814930A (zh) 2016-07-27
AU2014411891A1 (en) 2017-06-29
US10666812B2 (en) 2020-05-26
CA2968439C (en) 2020-04-14
CA2968439A1 (en) 2016-05-26
EP3214862A1 (en) 2017-09-06

Similar Documents

Publication Publication Date Title
US20200412706A1 (en) Connecting imsi-less devices to the epc
EP3834154B1 (en) Split billing for a user across multiple billing systems
WO2017049736A1 (zh) 一种移动通信网络接入方法及装置
TW201505464A (zh) 無線上網流量共用控制方法及系統
CN111466101A (zh) 用于电子通信设备的策略调节的方法和装置
WO2017041562A1 (zh) 一种识别终端设备用户身份的方法和装置
US10666812B2 (en) Charging control apparatus, method, and system
CN103067342A (zh) 一种使用eap进行外部认证的设备、系统及方法
CN103339989A (zh) 用于通信网络中的用户设备和数据网络之间的通信的技术
US20140101040A1 (en) Method and apparatus for charging in a communication network
US20180077573A1 (en) Untrusted device access to services over a cellular network
US20220408303A1 (en) Terminal Device, Application Server, Network Exposure Function Node and Methods Therein
CN109309907B (zh) 用于流量计费的方法、装置及其相关设备
US10299121B2 (en) System and method for providing differential service scheme
CN106878099B (zh) 一种流量管理方法、终端设备、服务器及系统
CN105306429B (zh) 一种状态通知方法及设备
US20190273794A1 (en) Method And Intermediate Network Node For Managing TCP Segment
WO2016101784A1 (zh) 一种获取用户信息的方法、装置及系统
EP3054642A1 (en) Data processing method, device and system
WO2020119768A1 (zh) 一种计费策略获取方法及装置
WO2014026624A1 (zh) 一种获取签约信息的方法及装置

Legal Events

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

Ref document number: 14906599

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2968439

Country of ref document: CA

ENP Entry into the national phase

Ref document number: 2017527569

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

REEP Request for entry into the european phase

Ref document number: 2014906599

Country of ref document: EP

ENP Entry into the national phase

Ref document number: 20177016819

Country of ref document: KR

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 2017121274

Country of ref document: RU

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 2014411891

Country of ref document: AU

Date of ref document: 20141121

Kind code of ref document: A

REG Reference to national code

Ref country code: BR

Ref legal event code: B01A

Ref document number: 112017010583

Country of ref document: BR

ENP Entry into the national phase

Ref document number: 112017010583

Country of ref document: BR

Kind code of ref document: A2

Effective date: 20170519