[go: up one dir, main page]

WO2013060170A1 - Procédé et dispositif de fourniture de support de facturation basé sur un support lipa - Google Patents

Procédé et dispositif de fourniture de support de facturation basé sur un support lipa Download PDF

Info

Publication number
WO2013060170A1
WO2013060170A1 PCT/CN2012/078813 CN2012078813W WO2013060170A1 WO 2013060170 A1 WO2013060170 A1 WO 2013060170A1 CN 2012078813 W CN2012078813 W CN 2012078813W WO 2013060170 A1 WO2013060170 A1 WO 2013060170A1
Authority
WO
WIPO (PCT)
Prior art keywords
session
charging
policy
pcef
offloading
Prior art date
Legal status (The legal status 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 status listed.)
Ceased
Application number
PCT/CN2012/078813
Other languages
English (en)
Chinese (zh)
Inventor
张娟
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
China Academy of Telecommunications Technology CATT
Original Assignee
China Academy of Telecommunications Technology CATT
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 China Academy of Telecommunications Technology CATT filed Critical China Academy of Telecommunications Technology CATT
Publication of WO2013060170A1 publication Critical patent/WO2013060170A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • 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
    • H04L12/1403—Architecture for metering, charging or billing
    • H04L12/1407—Policy-and-charging control [PCC] architecture
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/14—Charging, metering or billing arrangements for data wireline or wireless communications
    • H04L12/1442—Charging, metering or billing arrangements for data wireline or wireless communications at network operator level
    • H04L12/145—Charging, metering or billing arrangements for data wireline or wireless communications at network operator level trading network capacity or selecting route based on tariff
    • 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/1485—Tariff-related aspects
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/80—Rating or billing plans; Tariff determination aspects
    • H04M15/8044—Least cost routing
    • H04M15/8055—Selecting cheaper transport technology for a given service

Definitions

  • the present invention relates to the field of communications, and in particular, to a method and apparatus for providing charging support based on LIPA bearers. Background technique
  • the Local IP Access (LIP) function is to support user equipment (UE) to directly access the IP network through the home base station (Home eNB, HeNB) and L-GW (Local GateWay, local gateway) without passing through A new technology for delivering data to the core network.
  • Home eNB home base station
  • L-GW Local GateWay, local gateway
  • the L-GW and the Packet Data Network Gateway (Packet Data Network Gateway, The function of the PGW is similar, but the L-GW is located inside the local network, rather than located in the core network like the PGW.
  • the local network that the UE can access through the L-GW is usually a home network or an intranet.
  • the Serving Gateway selects the connection to the L-GW for the UE.
  • an Sxx interface is also established between the L-GW and the HeNB.
  • the uplink data of the UE is directly transmitted from the HeNB to the L-GW through the Sxx interface, and the downlink data received by the L-GW is directly sent from the L-GW to the He B through the Sxx interface.
  • the data connected by the LIPA PDN does not need to pass through the core network. In the connected state, no data is transmitted on the S 1-U interface between the HeNB and the SGW and on the S5 interface between the SGW and the L-GW.
  • the L-GW is equivalent to the PGW, and this function is also called
  • the function of the selected IP traffic offload at local network is that the UE can directly access the external network connection through the local network, and the data does not need to be transmitted through the core network.
  • the UE directly accesses the L-GW through the HeNB, and then accesses the external network through the L-GW without transmitting through the SGW.
  • the difference between the first case and the second case is mainly that, in the first case, the L-GW can only connect to an internal network such as a home or an enterprise network, and in the second case, the L-GW can access an external device such as the Internet. Network, but not the intranet.
  • the Policy and Charging Enforcement Function is located in the PGW, and its main execution service data is Service data flow detection (SDF detection), Quality of Service (QoS) mapping, billing, etc.
  • the S5/S8 interface between the SGW and the PGW is the GPRS Tunneling Protocol (GPRS Tunnelling Protocol) , GTP) protocol
  • the service data flow file (SDF) mapping to the bearer binding function (Bearer binding) function is executed in the PCEF
  • the S5/S8 interface between the SGW and the PGW uses the proxy
  • the S5/S8 interface between the SGW and the PGW uses the proxy
  • bearer binding is performed in the Bearing Binding and Event Report Function (BBERF) module.
  • BBERF Bearing Binding and Event Report Function
  • IP-Connectivity Access Network IP-CAN session
  • the PCEF sends a credit control request (CC-Request) to the Policy and Charging Rules Function (PCRF) entity, and indicates the CC-Request-Type AVP as the initial request (INITIAL_REQUEST)
  • the PCEF passes the user identification and other information to the PCRF.
  • the PCRF decides the policy to be used in subsequent operations based on the received information.
  • the information may include IP-CAN type (IP-CAN type), grouping. Packet data network information (PDN information), public network connection indication (PDN connection identifier), UE IP address (UE IP address), and the PCRF receives the CC-Request and then registers the server according to the identity from the PCEF.
  • the Subscripton Profile Repository (SPR) and the Information Control and Charging (PCC) rules obtained in the Application Function (AF) entity are sent to the PCEF.
  • SPR Subscripton Profile Repository
  • PCC Information Control and Charging
  • the PCC rules include Charging related parameters, which are carried in the charging information attribute (Charging-Information).
  • the AVP is sent to the PCEF.
  • the PCEF obtains the information for charging according to the charging related parameter indicated in the received PCC rules, and generates the information required for the charging to the corresponding charging center. For example, if the PCRF indicates that online charging is performed for an SDF, the PCEF sends the user's charging information to the Online Charging System (OCS) through the Gy interface, if the PCRF indicates to a certain The SDF implements offline charging, and the PDEF sends the user's charging information to the Offline Charging System (OFCS) through the Gz interface.
  • OCS Online Charging System
  • the carrier allocates different charging policies for the UEs that access the network through the He B. Therefore, the PCRF reports the AVP (CSG-information-Reporting AVP) by closing the user group information when returning the PCC rules to the PCEF.
  • the PCEF is instructed to request the closed subscriber group (CSG) information of the UE. For example, if the UE enters/leaves a CSG cell, the PCEF is required to report to the charging center that the CSG identity (ID) of the UE has changed. If the UE enters/leaves a hybrid cell
  • the PCEF is required to report the CSG ID to the charging center and whether the UE is a member of the hybrid cell. After the PCEF receives the information that the UE enters/leaves the CSG cell or the hybrid cell, the PCEF will send the CSG ID. And the member information is sent to the corresponding billing center together with other billing related information.
  • the LIPA bearer does not support the interface to the PCC.
  • the charging problem of the LIPA bearer is not discussed. Therefore, the impact of the LIPA bearer on the charging policy is not considered in the PCC policy.
  • the LIPA mechanism in the subsequent network evolution, it is highly probable that the interface between the L-GW and the PCC will be supported. Since the LIPA bearer does not need to use the user plane resources of the core network, the calculation for the LIPA bearer The billing fee may be different from the normal non-LIPA bearer. Therefore, it is necessary to reformulate the corresponding PCC policy for the LIPA bearer.
  • the PCRF generates a charging policy according to the information of the Radio Access Technology (RAT), APN, etc. accessed by the UE.
  • the fee policy is passed to the PCEF for execution.
  • the PCEF also needs to pass the obtained charging information of the UE to the charging center for charging by the operator.
  • the LIPA bearer is different from the network resources occupied by the non-LIPA bearer, the LIPA bearer only needs to occupy the air interface bearer of the operator, and does not need to occupy the core network bearer. Therefore, the PCC allocates a charging policy to the UE and applies LIPA to the last charging.
  • the bearer is different from the non-LIPA bearer.
  • the embodiments of the present invention provide a method and an apparatus for providing charging support based on a LIPA bearer, so as to implement accurate charging of a LIPA bearer when the LIPA is connected to the PCC architecture.
  • a method for providing charging support based on LIPA bearers including:
  • the charging related parameter of the IP-CAN session is reported to the corresponding charging center according to the charging policy, and The offloading mode of the IP-CAN session is reported, so that the charging center performs related charging for the IP-CAN session according to the obtained data.
  • a method for providing charging support based on LIPA bearers including:
  • a response message carrying the charging policy and the offloading report information so that the PCEF determines that the IP-CAN session is used to access the IP network according to the offloading report information, according to the The fee policy reports the charging related parameters of the IP-CAN Session to the corresponding charging center, and reports the IP-CAN
  • the split mode used by the session enables the billing center to perform related charging for the IP-CAN session according to the obtained data.
  • a device for providing charging support based on LIPA bearer comprising:
  • a first communication unit configured to send, to the PCRF entity, a request message for indicating that an IP-CAN session is required to be performed for the IP connection, and receiving a response that is sent by the PCRF and carrying the charging policy and the offloading report information Message
  • a second communication unit configured to report the IP-CAN session to the corresponding charging center according to the charging policy when the IP-CAN session is used to access the IP network according to the split report information.
  • the billing related parameter, and the shunting method for reporting the IP-CAN session causes the billing center to perform related billing for the IP-CAN session according to the obtained data.
  • a device for providing charging support based on LIPA bearer comprising:
  • a receiving unit configured to receive a request message sent by the PCEF entity to indicate that the IP-CAN session needs to be performed for the IP connection to access the network session;
  • a sending unit configured to return, to the PCEF, a response message carrying the charging policy and the offloading report information, so that the PCEF determines, according to the offloading, the IP-CAN session to use the offloading mode to access
  • the charging-related parameters of the IP-CAN session are reported to the corresponding charging center according to the charging policy, and the offloading mode of the IP-CAN session is reported, so that the charging center obtains the The data is correlated for the IP-CAN session.
  • the PCRF entity sets corresponding Charging information for the IP-CAN Session, and notifies the PCEF at least the Charging information and the offload-reporting information, and the PCEF is based on offload-reporting
  • the information indicates that the IP-CAN Session uses the offloading mode to access the IP network, collects the corresponding charging related parameters according to the obtained Charging information, and reports the charging related parameters and offload information to the charging center to make the charging.
  • the center can charge the above IP-CAN Session according to the obtained information. In this way, under the PCC architecture, the billing center can accurately charge the IP-CAN session based on the LIPA bearer, and improve the billing center. Performance also increases the system's service shield.
  • FIG. 1 is a schematic structural diagram of a LIPA bearer system in the prior art
  • FIG. 2 is a schematic diagram of a PCC architecture in the prior art
  • FIG. 3 is a schematic diagram of a connection between a LIPA bearer and a PCC architecture according to an embodiment of the present invention
  • FIG. 4 is a schematic structural diagram of a PCEF entity in an embodiment of the present invention.
  • FIG. 5 is a schematic structural diagram of a function of a PCRF entity according to an embodiment of the present invention.
  • FIG. 6 is a flowchart of charging support based on a LIPA bearer in a PCC architecture according to an embodiment of the present invention
  • FIG. 7 is a flowchart of performing bearer setup based on a LIPA bearer in a PCC architecture according to an embodiment of the present invention
  • FIG. 8 is a flowchart of performing bearer modification based on a LIPA bearer in a PCC architecture according to an embodiment of the present invention.
  • the PCRF entity (hereinafter referred to as PCRF) sets a corresponding charging policy for the IP-CAN Session currently processed (eg, established or modified), and at least notifies the PCEF of the charging policy and the offloading report information, and the PCEF according to the offloading report information
  • PCRF sets a corresponding charging policy for the IP-CAN Session currently processed (eg, established or modified), and at least notifies the PCEF of the charging policy and the offloading report information, and the PCEF according to the offloading report information
  • the corresponding charging related parameters are calculated according to the obtained charging policy, and the charging related parameters and the shunting manner of the IP-CAN session are reported to the charging center.
  • the billing center can perform related billing on the above IP-CAN session according to the obtained information.
  • the PCEF is a logical functional entity. In practical applications, the PCEF may be independent.
  • the device is preferably disposed inside the L-GW as a functional module.
  • PCRF used to set the corresponding PCC ruleso for the bearer
  • the BBERF may also be an independent device, or, preferably, a functional module is disposed inside the SGW.
  • the PCEF includes at least a first communication unit 40 and a second communication unit 41,
  • the first communication unit 40 is configured to send, to the PCRF entity, a request message for indicating that a related operation needs to be performed for the IP connection access network session IP-CAN session, and receive a response message that is returned by the PCRF and carries the charging policy and the offload report information. ;
  • the second communication unit 41 is configured to report the charging related parameter of the IP-CAN session to the corresponding charging center according to the charging policy when determining the IP-CAN session to use the offloading mode to access the IP network according to the offloading report information, and The IP-CAN session is used for the offloading mode, so that the billing center performs related billing for the IP-CAN session based on the obtained data.
  • the first communication unit 40 when the first communication unit 40 sends a request message for indicating that the related operation needs to be performed for the IP-CAN session, the first communication unit 40 directly sends a request message to the home PCRF entity to indicate that the related operation needs to be performed for the IP-CAN session. Or, the request message indicating that the related operation needs to be performed for the IP-CAN session is sent to the home PCRF entity by the roaming PCRF entity.
  • the first communication unit 40 when the first communication unit 40 sends a request message for indicating that the related operation needs to be performed for the IP-CAN session, the first communication unit 40 sends a request message for instructing to establish an IP-CAN session to the PCRF entity, or to the PCRF entity. A request message is sent to indicate the modification of the IP-CAN session.
  • the first communication unit 40 when receiving the response message that is sent by the PCRF and carrying the charging policy and the offloading report information, the first communication unit 40 receives a response message that is sent by the PCRF and carries the policy and charging control PCC rules, the PCC rules At least the charging policy, the QoS policy, and the offloading report information set for the IP-CAN session are included; or, the response message carrying the PCC rules returned by the PCRF is received, and the PCC rules include at least the Accounting policy and offload report information set by IP-CAN session.
  • the method includes: confirming that the data transmitted by the IP-CAN session does not pass through the core network, but is directly through the local gateway L-GW.
  • the method includes: confirming that the data transmitted by the IP-CAN session does not pass through the core network, but is directly through the local gateway L-GW.
  • the second communication unit 41 reports the charging related parameter of the IP-CAN session to the corresponding charging center according to the charging policy, and reports the offloading mode used by the IP-CAN session to enable charging.
  • the center performs related charging for the IP-CAN session according to the obtained data, the center includes:
  • the second communication unit reports the IP-CAN session to the online charging system 0CS through the Gy interface.
  • the 0CS performs related charging for the IP-CAN session according to the obtained data;
  • the second communication unit reports the IP-CAN session to the offline charging system 0FCS through the Gz interface.
  • the offloading mode, and reporting the charging related parameters for the IP-CAN session statistics, is performed by the 0FCS according to the obtained data, and the related charging is performed for the IP-CAN session.
  • the PCRF includes at least a receiving unit 50 and a sending unit 51, where the receiving unit 50 is configured to receive an IP-CAN session sent by the PCEF entity for indicating that the network session needs to be accessed for the IP connection. a request message for performing related operations;
  • the sending unit 51 is configured to return a response message carrying the charging policy and the offloading report information to the PCEF, so that the PCEF, when determining the IP-CAN session to use the offloading mode to access the IP network according to the diverting report information, according to the charging policy
  • the billing center reports the billing related parameters of the IP-CAN Session and the shunting method used for reporting the IP-CAN session, so that the billing center performs related billing for the IP-CAN session according to the obtained data.
  • the receiving unit 50 receives the request message sent by the PCEF entity to indicate that the related operation needs to be performed for the IP-CAN session, and receives the request sent directly by the PCEF entity to indicate that the related operation needs to be performed for the IP-CAN session. Or requesting, by the PCEF entity, a request message sent by the roaming policy and charging rule function PCRF entity to indicate that the related operation needs to be performed for the IP-CAN session.
  • the receiving unit 50 receives a request message sent by the PCEF entity to indicate that the related operation needs to be performed for the IP-CAN session, and receives a request message sent by the PCEF entity to indicate that the IP-CAN session is established, or receives the request message.
  • the sending unit 51 returns a response message carrying the charging policy and the offloading report information to the PCEF, and returns a response message carrying the PCC rules to the PCEF, where the PCC rules include at least the The charging policy, the QoS policy, and the offloading report information set by the IP-CAN session; or the response message carrying the PCC rules returned to the PCEF, the PCC rules including at least the setting for the IP-CAN session The fee policy and the offload report information, and the response message carrying the QoS policy set for the IP-CAN session to the bearer binding and event reporting function BBERF entity.
  • the sending unit 51 causes the PCEF to access the IP network according to the offloading report information, and determine the IP-CAN session to use the offloading mode to access the IP network, according to the charging policy to the corresponding charging center.
  • the sending unit 51 causes the PCEF to determine, according to the obtained charging policy, that the online charging method is used for the IP-CAN session, and the IP-CAN session is sent to the online charging system OCS through the Gy interface. Using the offloading method, and reporting the charging related parameters for the IP-CAN session statistics, the OCS performs related charging for the IP-CAN session according to the obtained data;
  • the sending unit 51 causes the PCEF to determine, according to the obtained charging policy, that the offline offline charging mode is used for the IP-CAN session, and the IP-CAN session is sent to the offline charging system OFCS through the Gz interface.
  • the offloading mode, and reporting the charging related parameters for the IP-CAN session statistics, the OFCS performs related charging for the IP-CAN session according to the obtained data.
  • Step 600 The PCEF requests the PCRF to perform related operations for the IP CAN session.
  • the PCEF may send a request message to the PCRF, indicating that an "IP CAN session" needs to be established, or indicating that an IP CAN session needs to be modified.
  • Step 610 The PCEF receives a response message that is sent by the PCRF and carries a charging policy and an offload-reporting information.
  • the PCEF sends a request message to the PCRF to indicate that a bearer needs to be established or modified.
  • the PCRF sends a PCC rules for the bearer to the PCF in the response message returned to the PCEF.
  • the PCRF returns the PCC rules to the PCEF, in addition to the AVP of the CSG-Information-Reporting, It will also carry an AVP in the above response message.
  • This AVP can be called a split-reporting message.
  • the function is to indicate to the PCEF whether the IP-CAN session that is required to be established or modified by the UE is determined. It is accessed by offload.
  • the PCRF may send at least the charging policy to the PCEF. If the BBERF exists in the system, the PCRF may send the PCC rules including at least the charging policy and the offloading information to the PCEF, and send at least the BBERF to the BBERF.
  • the PCC rules of the QoS policy will be described in detail in the following examples.
  • Step 620 The PCEF reports the IP-CAN session charging to the corresponding charging center according to the obtained charging policy when determining that the IP-CAN session uses the offloading mode to access the IP network according to the obtained offload-reporting information.
  • the relevant parameters, and the shunting method used for reporting the IP-CAN session enable the billing center to perform related charging for the above IP-CAN session according to the obtained data.
  • the PCEF will send an offload indication to the corresponding billing center to indicate that the IP-CAN session is not normal.
  • the core network connects to the bearer of the IP network, but accesses the bearer of the IP network through the offload mode; that is, the PCEF confirms that the data transmitted by the IP-CAN session does not pass through the core network, but is directly transmitted to the internal through the L-GW.
  • the PCEF reports the IP-CAN session offload mode (ie, the LIPA mode) to the online charging system (OCS) through the Gy interface. Or SIPTO at local network mode), and reporting the charging related parameters for the IP-CAN session statistics, and the OCS uses the online charging method to perform related charging on the IP-CAN session according to the obtained data; If the charging policy indicated by the PCRF indicates that the IP-CAN session is in the offline charging mode, the PCEF reports the IP-CAN session offload mode to the offline charging system (OFCS) through the Gz interface (ie, LIPA mode or SIPTO at). The local network mode), and reporting the charging related parameters for the IP-CAN session statistics, the OFCS performs related charging on the IP-CAN session according to the obtained data and the offline charging method.
  • OCS online charging system
  • the indication charging center is based on
  • Step 700 Start a control session establishment process based on the LIPA bearer.
  • both PCEF and BBERF are logical entities located in the Gateway. The difference is that the PCEF is located at the L-GW and the BBERF is located at the SGW.
  • Step 701 The PCEF receives an Establish IP-CAN Bear Rquest.
  • the Establish IP-CAN Bear Rquest received by the PCEF may be sent by the UE, or may be
  • the MME sends it, and details are not described here.
  • Step 702 The PCEF sends an Indication of IP-CAN Session to the PCRF (this PCRF is an H-PCRF). Establishment (IP-CAN Session establishment indication).
  • the PCEF directly sends an Establish IP-CAN Bearer Request to the H-PCRF (home H-PCRF). If the PCEF is roaming, the PCEF passes a V-PCRF (Roaming PCRF) Send an Establish IP-CAN Bearer Request to the H-PCRF,
  • Step 703 The PCRF sends an identity request (Profile Request) to the SPR.
  • Profile Request an identity request
  • the PCRF sends a Profile Request to the SPR to obtain the subscription information of the UE, so as to formulate a more suitable PCC rules.
  • Step 704 The SPR returns an identity response (Profile Response ) to the PCRF.
  • Step 705 The PCRF creates PCC rules for the IP-CAN Session according to the information returned by the SPR, that is, performs Policy Decision.
  • Step 706 The PCRF returns an Acknowledge IP-CAN Session Establishment to the PCEF.
  • the message needs to carry the established PCC rules, and the PCC rules must carry at least the calculation for the IP-CAN Session.
  • the fee policy and offload-reporting information require the PCEF to report whether the IP-CAN Session uses the offload access method.
  • the PCEF after receiving the request for establishing an IP-CAN bearer in step 701, the PCEF sends an IP-CAN session establishment indication to the PCRF to obtain PCC rules for the established bearer request, and the PCRF is according to step 702.
  • the received information further, may also set a corresponding PCC rule for the above IP-CAN Session by obtaining the subscription information of the UE to the SPR.
  • the PCRF may directly send the PCC rules to the PCEF in the non-roaming state, or may indirectly send the PCC rules to the PCEF in the roaming state through the PCRF of the roaming place.
  • step 706 the PCRF returns PCC rules to the PCEF, and the PCC rules mainly contain the following information (in the absence of a BBERF entity):
  • the PCRF indicates to the PCEF the charging information (ie, charging policy), the QoS information, the service data flow file (SDF filer) information, etc. for the established IP-CAN Session setting through the information; wherein, in addition to Charging -Rule-Remove, Charging-Rule-Install and Charging-Information are billing related information, online and offline options indicate whether this IP-CAN Session is billed via online or offline; if it is online If the PCEF collects the accounting related parameters of the IP-CAN Session according to the charging information, the data will be transmitted to the OCS for charging processing through the Gy interface. If it is offline charging, then the PCEF counts the IP according to the charging information. After the charging related parameters of the CAN Session, the data will be transmitted to the OFCS through the Gz interface for charging processing.
  • charging information ie, charging policy
  • SDF filer service data flow file
  • CSG-Information-Reporting and User-CSG-Information are used for charging in the CSG cell.
  • the charging mode used by the charging center may be different from that of the macro cell, so the PCEF After the CSG information is transmitted to the charging center, the charging center can retrieve the charging policy related to the CSG.
  • the PCF rules transmitted by the PCRF to the PCEF further include an offload reporting information.
  • the PCEF When the PCEF is required to report the charging related information of the IP-CAN session, it is necessary to further report whether the bearer is offloaded. If the bearer is connected to the local network in the LIPA mode or is connected to the external network in the SIPTO at load network mode, the PCEF needs to report the offload information to the charging center, indicating that the UE is accessed through the offload mode.
  • the PCEF reports the offload indication to the OCS through the Gy interface, that is, notifies the OCS of the offload mode of the IP-CAN Session; if the PCRF indicates This bearer uses the offline charging mode, and the PCEF reports the offload indication to the OFCS through the Gz interface, that is, also notifies the OCS of the offloading mode of the IP-CAN Session.
  • Step 707 The PCEF sends a credit request to the billing center to request authentication through the billing center.
  • Step 708 The charging center returns an authentication response (Credit Response) to the PCEF, and notifies the PCEF to pass the identity authentication.
  • Auit Response an authentication response
  • step 707 and step 708 may not be performed.
  • Step 709 The PCEF returns an IP-CAN bearer response to the process initiator (eg, UE or MME).
  • the process initiator eg, UE or MME
  • IP-CAN Bearer Response IP-CAN Bearer Response
  • Step 710 The IP-CAN bearer signal (IP-CAN Bearer Signaling) is started to be transmitted between the PCEF and the process initiator.
  • Step 711 The PCEF sends an IP-CAN Session Establishment Acknowledge message to the PCRF transmission.
  • IP-CAN Bearer Signaling IP-CAN Bearer Signaling
  • the IP-CAN Session has been successfully established, and data transmission can be performed based on the IP-CAN Session.
  • the SGW performs the function of the BBERF, that is, the logic module with the BBERF function is set in the SGW, and the IP-CAN session is established at this time.
  • the PCRF receives the information sent from the BBERF, it needs to generate PCC rules according to the information received from the BBERF and the information obtained from the SPR. Unlike the procedure shown in FIG. 6, in step 706, the PCRF will PCC.
  • the QoS policy set for the IP-CAN session and the information related to the event trugger need to be transmitted to the BBERF.
  • the BBERF performs the bearer binding process and the charging information set for the IP-CAN session. (ie, the charging policy) is still sent to the PCEF.
  • the PCRF sends the charging information to the PCEF by initiating an IP-CAN session modification procedure.
  • the detailed process of instructing the charging center to perform charging based on the LIPA bearer is as follows:
  • Step 800 The AF sends application/service information (Application/Service Info) to the PCRF (ie, H-PCRF).
  • Step 801 The PCRF returns an acknowledgement (ACK) to the AF.
  • ACK acknowledgement
  • Step 802 The PCRF formulates corresponding PCC rules for a changed IP-CAN Session, that is, performs Policy Decision.
  • Step 803 Provide the BBERF with a QoS policy for the modified IP-CAN Session setting through the Network Control and QoS Rules Provision process.
  • Step 804 The PCRF provides PCC rules to the PCEF through a Policy and Charging Rules Provision message, and the PCC rules carry at least the Charging information and the offload-reporting information set by the PCRF for the modified IP-CAN Session.
  • step 803 and step 804 are described by taking the BBERF in the system as an example. If there is no BBERF, the PCRF provides the PCEF with the PCC rules including at least the Charging information, the Qos policy, and the offload-reporting information. . For details, refer to the related description of step 706, and details are not described herein again.
  • the PCRF ie, H-PCRF
  • the PCRF may directly provide the PCC rules to the PCEF, and may also provide the PCC rules to the PCEF through the PCRF of the roaming place. This will not be repeated here.
  • Step 805 The PCEF executes the received PCC rules, that is, according to the instruction of the offload-reporting information, reports whether the IP-CAN session uses the offload access mode in the subsequent process to the corresponding charging center, that is, reports the offload.
  • the PCEF determines that the modified IP-CAN Session is connected to the IP network by using the LIPA connection or the SIPTO at load network, the PCEF needs to report the offload information to the charging center.
  • the IP-CAN Session is accessed to the IP network through offload. For example, if the PCRF indicates that the IP-CAN Session uses the online charging mode in the Charging information, the PCEF reports the offload information to the OCS through the Gy interface, so that the OAC performs the modified IP-CAN Session according to the obtained data. Related billing; If the PCRF indicates that the IP-CAN Session uses the offline charging mode, the PCEF reports the offload information to the OFCS through the Gz interface, so that the OFCS correlates the modified IP-CAN Session according to the obtained data. fee.
  • Step 806 The PCEF sends a Credit Request to the billing center to request identity authentication through the billing center.
  • Step 807 The charging center returns a Credit Response to the PCEF, and notifies the PCEF to pass the identity authentication.
  • step 806 and step 807 may not be performed.
  • Step 808 The PCEF sends an IP-CAN Bearer Signaling (IP-CAN Bearer Signaling).
  • IP-CAN Bearer Signaling IP-CAN Bearer Signaling
  • Step 809 PCEF receives IP-CAN Bearer Signaling.
  • Step 810 The PCEF returns an ACK to the PCRF.
  • Step 811 The PCEF sends a Notification of Bearer Level Event to the AF.
  • Step 812 Each PCEF of the AF sends an ACK.
  • IP-CAN Session modification process is completed, and the IP-CAN Session's split access mode has been successfully enabled by the billing center, which enables the billing center to achieve accurate billing.
  • the PCRF entity sets corresponding Charging information for the IP-CAN Session, and notifies the PCEF at least the Charging information and the offload-reporting information.
  • the PCEF determines, according to the indication of the offload-reporting information, that the IP-CAN session uses the offloading mode to access the IP network, and then collects corresponding charging related parameters according to the obtained Charging information, and reports the charging related parameters and offload to the charging center.
  • the billing center can perform related billing on the above IP-CAN Session according to the obtained information, so that under the PCC architecture, the billing center can accurately charge the IP-CAN session based on the LIPA bearer, perfecting
  • the performance of the billing center also increases the service shield of the system.
  • embodiments of the present invention can be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment, or a combination of software and hardware. Moreover, the present invention is in the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage and optical storage, etc.) in which computer usable program code is embodied.
  • the computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture comprising the instruction device.
  • the apparatus implements the functions specified in one or more blocks of a flow or a flow and/or block diagram of the flowchart.
  • These computer program instructions can also be loaded onto a computer or other programmable data processing device such that a series of operational steps are performed on a computer or other programmable device to produce computer-implemented processing for execution on a computer or other programmable device.
  • the instructions provide steps for implementing the functions specified in one or more of the flow or in a block or blocks of a flow diagram.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Meter Arrangements (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

La présente invention concerne un procédé et un dispositif qui sont destinés à fournir un support de facturation sur la base d'un support LIPA (support d'accès IP local) et qui sont utilisés pour facturer avec précision le support LIPA par un centre de facturation. Le procédé consiste en ce que : dans un processus d'installation ou de modification d'un support, une entité PCRF (entité à fonction de règles de politique et de facturation) envoie une politique de facturation correspondante pour le support et signale à au moins une entité PCEF (entité à fonction de mise en œuvre de politique et de facturation) des informations sur la politique de facturation et des informations de rapport de délestage; et lorsqu'il est déterminé, selon l'indication des informations de rapport de délestage, que le support accède à un réseau IP dans un mode de délestage, l'entité PCEF collecte des statistiques concernant des paramètres relatifs à une facturation correspondante selon la politique de facturation obtenue et signale les paramètres relatifs à la facturation et l'indication de délestage à un centre de facturation de sorte que le centre de facturation facture le support selon les informations obtenues. Avec l'architecture de politique et de commande de facturation (PCC), le centre de facturation peut facturer avec précision le support LIPA, améliorant de cette façon la performance du centre de facturation et la qualité de service d'un système.
PCT/CN2012/078813 2011-10-26 2012-07-18 Procédé et dispositif de fourniture de support de facturation basé sur un support lipa Ceased WO2013060170A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN 201110330228 CN102332985B (zh) 2011-10-26 2011-10-26 一种提供基于lipa承载的计费支持的方法及装置
CN201110330228.3 2011-10-26

Publications (1)

Publication Number Publication Date
WO2013060170A1 true WO2013060170A1 (fr) 2013-05-02

Family

ID=45484597

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2012/078813 Ceased WO2013060170A1 (fr) 2011-10-26 2012-07-18 Procédé et dispositif de fourniture de support de facturation basé sur un support lipa

Country Status (2)

Country Link
CN (1) CN102332985B (fr)
WO (1) WO2013060170A1 (fr)

Families Citing this family (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102332985B (zh) * 2011-10-26 2013-12-25 电信科学技术研究院 一种提供基于lipa承载的计费支持的方法及装置
CN103379479B (zh) * 2012-04-27 2016-08-03 电信科学技术研究院 一种确定用户标识和通知参数信息的方法、系统及设备
CN103379555B (zh) * 2012-04-28 2016-05-18 电信科学技术研究院 一种通信系统、装置和方法
CN104105082B (zh) * 2013-04-01 2018-05-04 华为技术有限公司 计费策略信息生成方法及策略与计费制定功能实体
CN105554721B (zh) * 2014-09-10 2019-09-13 北京佰才邦技术有限公司 通信业务信息的处理方法和装置
CN106921954B (zh) * 2015-12-25 2021-02-19 中兴通讯股份有限公司 进出区域监控的处理方法及装置
CN112383405B (zh) * 2015-12-31 2022-04-08 华为技术有限公司 一种数据业务计费方法、装置和系统
CN107333338B (zh) * 2016-04-29 2020-02-21 中国电信股份有限公司 基于lipa的动态承载策略控制方法、装置和通信网络

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2011021875A2 (fr) * 2009-08-21 2011-02-24 Lg Electronics Inc. Serveur pour plan de commande au niveau d'un réseau de communication mobile et procédé de commande de service d'accès ip local
CN101998340A (zh) * 2009-08-25 2011-03-30 中兴通讯股份有限公司 一种本地ip访问的计费方法及系统
CN101998348A (zh) * 2009-08-25 2011-03-30 中兴通讯股份有限公司 一种计费系统及其进行计费的方法
CN101998347A (zh) * 2009-08-24 2011-03-30 中兴通讯股份有限公司 本地ip访问计费信息的获取方法和系统
CN101998341A (zh) * 2009-08-25 2011-03-30 中兴通讯股份有限公司 一种本地ip访问的计费方法及系统
CN102332985A (zh) * 2011-10-26 2012-01-25 电信科学技术研究院 一种提供基于lipa承载的计费支持的方法及装置

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101552682B (zh) * 2008-04-03 2011-08-10 华为技术有限公司 策略和计费控制信息控制方法及系统

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2011021875A2 (fr) * 2009-08-21 2011-02-24 Lg Electronics Inc. Serveur pour plan de commande au niveau d'un réseau de communication mobile et procédé de commande de service d'accès ip local
CN101998347A (zh) * 2009-08-24 2011-03-30 中兴通讯股份有限公司 本地ip访问计费信息的获取方法和系统
CN101998340A (zh) * 2009-08-25 2011-03-30 中兴通讯股份有限公司 一种本地ip访问的计费方法及系统
CN101998348A (zh) * 2009-08-25 2011-03-30 中兴通讯股份有限公司 一种计费系统及其进行计费的方法
CN101998341A (zh) * 2009-08-25 2011-03-30 中兴通讯股份有限公司 一种本地ip访问的计费方法及系统
CN102332985A (zh) * 2011-10-26 2012-01-25 电信科学技术研究院 一种提供基于lipa承载的计费支持的方法及装置

Also Published As

Publication number Publication date
CN102332985A (zh) 2012-01-25
CN102332985B (zh) 2013-12-25

Similar Documents

Publication Publication Date Title
US8874715B2 (en) Charging method, system and reporting method for terminal accessing through multiple access networks
CN101646149B (zh) 一种删除dra中会话信息的方法
EP2424160A1 (fr) Procédé pour mettre en uvre une commande de politique et de facturation limitée et système associé
WO2013060170A1 (fr) Procédé et dispositif de fourniture de support de facturation basé sur un support lipa
WO2010031316A1 (fr) Procédé et système pour réaliser la commande de politique et de facturation sur la scène de multiples réseaux de données par paquets (pdn)
WO2011029289A1 (fr) Procédé et système de transmission d'un mode de commande de support dans des scénarios d'itinérance
WO2011026385A1 (fr) Procédé et système de facturation en ligne dans des scénarios d'itinérance à raccordement local
CN103929725B (zh) 漫游本地业务的在线计费方法、h-ocs及v-ocs
CN101771986A (zh) 基于多接入技术的策略计费控制方法、装置和系统
WO2006015548A1 (fr) Methode de traitement fondee sur un evenement de declenchement de chargement et sur un evenement de reautorisation de flux de donnees de paquets
WO2014094488A1 (fr) Procédé et dispositif de gestion de politique de facturation destinés à un service local d'itinérance
CN101841798B (zh) 计费标识的关联方法和装置
WO2012071956A1 (fr) Procédé, système et appareil destinés à supporter une connectivité de données organisées dans des scénarios itinérants
CN102711086B (zh) 被赞助数据连接的处理方法及策略与计费规则功能实体
CN112702180B (zh) 一种策略控制方法、装置及系统
WO2012083779A1 (fr) Procédé et dispositif de commande de politique
CN102791042B (zh) S9子会话建立方法、系统及pcrf
CN101742471A (zh) 一种数据流与接入网连接绑定的方法
EP3335372B1 (fr) Amélioration du contrôle de congestion par redémarrage sélectif de sessions de contrôle de crédit
CN102369775B (zh) 计费处理方法、计费处理装置和计费处理系统
WO2013113263A1 (fr) Procédé et système d'identification de mode fonction de commande de détection d'application
CN104105082B (zh) 计费策略信息生成方法及策略与计费制定功能实体
CN105284141B (zh) 一种计费的方法及装置
WO2013091705A1 (fr) Procédés et appareils pour établissement de session avec commande de politique entre réseaux mobiles et fixes
WO2011029349A1 (fr) Procédé et système de traitement de multiples fonctions d'association de support et de rapport d'événement

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 12844157

Country of ref document: EP

Kind code of ref document: A1