WO2006015547A1 - Procede d'etablissement de dialogues sur la charge de paquets de donnees - Google Patents

Procede d'etablissement de dialogues sur la charge de paquets de donnees Download PDF

Info

Publication number
WO2006015547A1
WO2006015547A1 PCT/CN2005/001237 CN2005001237W WO2006015547A1 WO 2006015547 A1 WO2006015547 A1 WO 2006015547A1 CN 2005001237 W CN2005001237 W CN 2005001237W WO 2006015547 A1 WO2006015547 A1 WO 2006015547A1
Authority
WO
WIPO (PCT)
Prior art keywords
tpf
crf
conversation
bearer
session
Prior art date
Application number
PCT/CN2005/001237
Other languages
English (en)
French (fr)
Inventor
Xiaoqin Duan
Original Assignee
Huawei Technologies Co., Ltd.
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 Huawei Technologies Co., Ltd. filed Critical Huawei Technologies Co., Ltd.
Priority to AT05780653T priority Critical patent/ATE451769T1/de
Priority to EP05780653A priority patent/EP1772990B1/en
Priority to DE602005018219T priority patent/DE602005018219D1/de
Publication of WO2006015547A1 publication Critical patent/WO2006015547A1/zh
Priority to US11/702,520 priority patent/US7889650B2/en
Priority to US13/004,082 priority patent/US8605585B2/en

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
    • 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
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/64—On-line charging system [OCS]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/66—Policy and charging system
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/82—Criteria or parameters used for performing billing operations
    • H04M15/8214—Data or packet based
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/82—Criteria or parameters used for performing billing operations
    • H04M15/8228—Session based
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M2215/00—Metering arrangements; Time controlling arrangements; Time indicating arrangements
    • H04M2215/20—Technology dependant metering
    • H04M2215/204—UMTS; GPRS
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M2215/00—Metering arrangements; Time controlling arrangements; Time indicating arrangements
    • H04M2215/22—Bandwidth or usage-sensitve billing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M2215/00—Metering arrangements; Time controlling arrangements; Time indicating arrangements
    • H04M2215/78—Metric aspects
    • H04M2215/782—Data or packet based
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M2215/00—Metering arrangements; Time controlling arrangements; Time indicating arrangements
    • H04M2215/78—Metric aspects
    • H04M2215/7833—Session based

Definitions

  • the present invention relates to the field of packet data charging, and more particularly to a dialog establishing method based on packet data stream charging. Background of the invention
  • FIG. 1 shows a packet data protocol context (PDP Context, Packet Data Protocol Context) activation, data transmission, deactivation flowchart, as shown in FIG. 1, in a general packet radio service (GPRS, General Packet Radio Service), activated
  • PDP Context the data interaction with the external packet data network (PDN, Packet Data Network)
  • PDN Packet Data Network
  • Step 101 The mobile terminal (MS) sends a PDP Context Request (Active PDP Context Request) to the Serving GPRS Support Node (SGSN), where the Activate PDP Context Request carries the network layer service access point identifier.
  • NSAPI Network Layer Service Access Point Identifier
  • PDP type Access Point Name
  • API Access Point Name
  • QoS quality of service
  • TI Transaction Identifier
  • GGSN gateway GPRS Support Node
  • TID Tunnel Identifier
  • the PDP type includes the end-to-end protocol (PPP, Peer-Peer).
  • APN can be provided by the MS to the SGSN, and the SGSN is addressed to the corresponding GGSN according to the APN, the GGSN root
  • the MS may not provide the APN to the SGSN according to the APN.
  • the SGSN may select the default APN according to the subscription information of the MS user.
  • the QoS parameter is the quality requirement of the packet data service specified by the MS.
  • TI is used by the MS to identify a PDP context.
  • Step 102 After receiving the Activate PDP Context Request, the SGSN performs security check and encryption with the MS. This step is optional.
  • Step 103 The SGSN parses the address information of the GGSN according to the APN. If the SGSN can parse the address information of the GGSN according to the APN, the TEID is created for the PDP Context, and the TEID can be an International Mobile Subscriber Identity (IMSI) and an NSAPI.
  • the SGSN sends a PDP Context Request to the GGSN.
  • the PDP Context Request contains the PDP type, PDP address, APN, QoS parameters, TEID, and selection mode.
  • the PDP address can be MS.
  • the IP address is an optional parameter.
  • the PDP Context creation request may not carry the PDP address.
  • the GGSN may assign an IP address to the MS in the subsequent processing, or may assign an IP to the MS by the PDN that finally establishes a connection with the MS. Address;
  • the selection mode refers to the APN selection mode, that is, whether the APN is selected by the MS or selected by the SGSN. If the SGSN cannot resolve the address information of the GGSN according to the APN, the SGSN rejects the PDP Context activation request initiated by the MS.
  • Step 104 After receiving the PDP Context creation request, the GGSN determines an external PDN according to the APN, then allocates a Charging ID, initiates charging, and negotiates QoS. If the GGSN can meet the quality of service requirements of the QoS parameter, the SGSN sends the SGSN to the SGSN.
  • the PDP Context Create Response (Representation PDP Context Response), which carries the TEID, the PDP address, the Backbone Bearer protocol, the agreed QoS parameters, and the Charging ID. If the GGSN fails to meet the quality of service requirements of the QoS parameters, the GGSN rejects the PDP Context creation initiated by the SGSN. The SGSN then rejects the PDP Context activation request initiated by the MS.
  • Step 105 After receiving the PDP Context creation response, the SGSN inserts NSAPI and GGSN address information for identifying the PDP Context in the PDP Context, and selects a radio priority according to the agreed QoS parameter, and then returns a PDP Context activation response to the MS (Activate PDP Context Accept), the PDP Context activation response carries information such as PDP type, PDP address, TI, agreed QoS parameters, wireless priority, PDP configuration options, and the like. And, the SGSN starts charging.
  • the MS Upon receiving the PDP Context activation response, the MS has established a direct route between the MS and the GGSN, and can perform packet data transmission.
  • Step 106 The MS performs packet data interaction through the SGSN, the GGSN, and the PDN.
  • Step 108 After receiving the PDP Context deactivation request, the SGSN performs security check and encryption with the MS. This step is an optional step.
  • Steps 109 to 111 The SGSN sends a PDP Context Request to the GGSN, and the PDP Context Delete Request carries the TEID.
  • the GGSN After receiving the PDP Context deletion request, the GGSN ends the charging of the MS, deletes the PDP Context corresponding to the TEID, and then sends a PDP Context Response (DDP) to the SGSN.
  • the PDP Context delete response carries the TEID.
  • the SGSN After receiving the PDP Context deletion response, the SGSN ends the charging of the MS, deletes the PDP Context corresponding to the TEID, and then sends a PDP Context Deactivation Response (Deactivate PDP Context Response) to the MS.
  • the PDP Context deactivation response carries the TI. .
  • the MS After receiving the PDP Context deactivation response, the MS deletes the PDP Context corresponding to ⁇ .
  • the charging termination point is set in the PDP Context.
  • the MS can perform multiple services based on an activated PDP Context, that is, if the PDN can provide multiple services, such as email (email), Based on the WAP (Wireless Application Protocol) browsing service and the file transfer protocol (FTP) file transfer service, the MS can pass an activated PDP after establishing a transmission channel with the PDN.
  • email email
  • WAP Wireless Application Protocol
  • FTP file transfer protocol
  • the Context carries various services that the PDN can provide.
  • the charging mode of the operator for various services is likely to adopt different charging methods.
  • the e-mail receiving and sending events may be triggered by the secondary charging, and the WAP browsing service may be based on the flow accounting fee.
  • the rate of the WAP browsing service and the rate of the file transfer service are different according to the flow rate. Therefore, according to the existing GPRS charging system, different services carried by the same PDP Context cannot be performed at all. Perform differentiated billing.
  • IP-based billing data streams (FBC, Flow Based Charging) 0 for a packet data service, MS users
  • IP Flow IP-based billing data streams
  • FBC Flow Based Charging
  • All IP data streams (IP Flow) transmitted and received may also be IP packets, which are collectively referred to as Service Data Flow, that is, the service data stream is multiple IP data.
  • the set of flows is composed, so the charging based on the IP data stream can truly reflect the occupation of resources by a certain service data flow.
  • IP data stream-based charging can be considered as filtering out IP data streams of different services carried in the same PDP Context through filters of similar filters, and then separately charging IP data streams filtered by different filters.
  • the granularity of the IP data-based charging is much smaller than the charging granularity based on a PDP Context.
  • the granularity can be regarded as the size of the screening hole.
  • the charging granularity based on a PDP Context is a PDP Context.
  • the meshing granularity based on the IP data stream is an IP service data stream is a sieve hole, that is, a plurality of sieve holes are included for one PDP Context, and therefore, the charging and ratio based on the IP data stream is based on Compared to the charging of a PDP Context, IP data stream based charging can provide operators or service providers with more abundant charging means.
  • the structure of FBC system supporting online charging is shown in Figure 2A.
  • the customized application based on mobile network enhanced logic (CAMEL, Customised Application for Mobile Network Enhanced Logic (SCP) Service Control Point (SCP) and Service Data Flow Based Credit Control Function (CCF) 202 constitute an online charging system (OCS, Online Charging System ) 206.
  • the CCF 202 communicates with the Service Data Flow Based Charging Rule Function (CRF) 203 through the Ry interface, and the CRF 203 communicates with the Application Function Entity (AF) through the Rx interface.
  • the CRF 203 communicates with the Traffic Plane Function (TPF) 205 through the Gx interface, and the CCF 202 communicates with the TPF 205 through the Gy interface.
  • CCF Service Data Flow Based Charging Rule Function
  • AF Application Function Entity
  • TPF Traffic Plane Function
  • the structure of the FBC system supporting offline charging is as shown in FIG. 2B.
  • the CRP 203 communicates with the AF 204 through the R interface, the CRF 203 communicates with the TPF 205 through the Gx interface, and the TPF 205 communicates with the charging gateway function entity through the Gz interface (CGF, Charging).
  • the Gateway Function 207 is interworking with a Charging Collection Function (CCF) 208.
  • CCF Charging Collection Function
  • the TPF 205 carries the IP data stream.
  • the TPF 205 sends a charging rule request to the CRF 203 through the Gx interface, where the charging rule request carries information related to the user and the MS, bearer characteristics, and Network related information, etc., wherein the information related to the user and the MS may be a mobile station international number (MSISDN), an international mobile subscriber identity (IMSI), etc., and the network related information may be a mobile network coding (MNC), a mobile country. Code (MCC), etc.
  • MSISDN mobile station international number
  • IMSI international mobile subscriber identity
  • MNC mobile network coding
  • MCC mobile country. Code
  • the TPF 205 may resend the charging rule request to the CRF 203 to request a new charging rule when the bearer is modified; the CRF 203 selects an appropriate charging rule according to the above input information provided by the TPF 205, and returns to the TPF 205.
  • the selected charging rule and charging rule include information such as charging mechanism, charging type, charging key, service data flow filter, and charging rule priority.
  • the charging mechanism may be online charging or offline charging; the charging type may be charging based on the length of time or based on data traffic; the charging button is a parameter related to the charging rate, CRF 203
  • the billing rate may not be provided directly to the TPF 205, but only the billing rate related parameters are provided to the TPF 205; the service data filter is used to indicate which IP data streams the TPF 205 filters, and then the TPF 205 is based on the charging rules.
  • the filtered IP data stream is charged.
  • the service data filter may include an IP5 tuple, and the IP5 tuple may include source/destination IP address, source/destination port number (Port Number), protocol identifier (Protocol ID), and the like.
  • the CRF 203 indicates the TPF 205 to the source address. Filters the IP data stream of 10.0.0.1, the destination address is 10.0.0.2, the source/destination port number is 20, the protocol type is Transmission Control Protocol (TCP), and the filtered IP data stream is calculated according to the charging rule. fee.
  • TCP Transmission Control Protocol
  • the CRF 203 may provide a trigger event (Event Trigger) to the TPF 205 to request the TPF 205 to request a new charging rule from the CRF 205 when a specific event occurs, such as the CRF 203 requesting the TPF 205 to perform an event modification on some bearers. At the time, a new charging rule is requested from the CRF 203.
  • Event Trigger a trigger event
  • the CRP 203 may also select an appropriate charging rule based on the input information of the AF 204 or the OCS 206, such as the AF 204 notifying the CRF 203 of the service currently used by the user.
  • Type CRF 203 selects the corresponding charging rule according to the type of service.
  • the OCS 206 is composed of two functional entities, the SCP 201 and the CCF (Service Data Flow Based Credit Control Function) 202.
  • the CCF (Service Data Flow Based Credit Control Function) 202 is a functional entity that performs credit control and is applied only to online charging. The system can be implemented by adding new functions to the existing OCS 206.
  • the CCF (Service Data Flow Based Credit Control Function) 202 manages and controls the user credit.
  • the CCF (Service Data Flow Based Credit Control Function) 202 is in the user credit pool.
  • the credit is authenticated, and the credit that the user can use is delivered to the TPF 205 through the Gy interface.
  • the TPF 205 is a GGSN
  • the AF is a service gateway or a service server in the PDN
  • the CRF 203 is a new logical entity.
  • TPF 205 is the enforcement point of the charging rule
  • CRF 203 is the control point of the charging rule.
  • the specification defines communication between CRF and TPF through dialogue, and different dialogs are identified by a dialog number. That is, when the bearer is established, the TPF requests charging rules from the CRF, and the CRF provides charging to the TPF. Rule, at this point a dialogue is established between the TPF and the CRF, and the dialogue established between the TPF and the CRF is identified by the session number.
  • the TPF identifies the correspondence between the current charging rule request and the previously established session through the session number; similarly, the CRF receives the charging relationship.
  • the CRF also needs to identify the correspondence between the currently provided charging rule and the previously established session through the session number.
  • the significance of establishing a dialogue between two entities is to establish a state machine between the two entities so that the two entities can directly use the data in the state machine for subsequent interactions without having to provide relevant information for each interaction.
  • the TPF needs to provide user information, bearer attributes, network information, and other related information to the CRF.
  • both the TPF and the CRF store the related information, and the subsequent interaction between the TPF and the CRF.
  • the TPF requests the charging rule from the CRF, or the OCS and the AF provide the CRF with the input information for determining the charging rule, and the CRF actively sends the charging rule to the TPF, and the sender does not need to provide the receiving party.
  • these related information but only provide the dialogue number to identify the corresponding dialogue.
  • an object of the present invention is to provide a dialog establishment method based on packet data flow charging, which clarifies a dialog establishment process and establishment manner between a TPF and a CRF.
  • the present invention provides a dialog establishment method based on packet data stream charging, the method comprising the step of: establishing a dialog for each bearer per user between the TPF and the CRF.
  • the step A1 is: when the bearer is established, the TPF establishes a TPF/CRF dialog state model, assigns a session number to the current session, and then provides the session number to the CRF, and the CRF establishes a TPF according to the received session number.
  • CRF conversation state model when the bearer is established, the TPF establishes a TPF/CRF dialog state model, assigns a session number to the current session, and then provides the session number to the CRF, and the CRF establishes a TPF according to the received session number.
  • the step A1 is: when the bearer is established, the CRF establishes a TPF/CRF dialog state model, assigns a session number to the current session, and then provides the session number to the TPF, and the TPF establishes a TPF according to the received session number.
  • CRF conversation state model when the bearer is established, the CRF establishes a TPF/CRF dialog state model, assigns a session number to the current session, and then provides the session number to the TPF, and the TPF establishes a TPF according to the received session number.
  • the step A1 further includes: the CRF determines whether a bearer establishment indication from the TPF is received, and if yes, performs step A1.
  • the step A1 is: when the bearer is established, the TPF establishes a TPF/CRF session state model, allocates a TPF part session number for the current session, and provides the TPF part of the session number to the CRF, and the CRF establishes a TPF.
  • /CRF conversation state model for The pre-conversation assigns the CRF part of the conversation number, and the TPF part of the conversation number and the CR part of the conversation number constitute the complete conversation number of the TPF/CRF conversation.
  • the step A1 further includes: the CRF provides a complete dialog number to the TPF, and the TPF indexes the previously established TPF/CRF conversation state model according to the TPF part conversation number in the complete conversation number, and updates the TPF conversation number to the complete conversation number.
  • the present invention also provides a dialog establishment method based on packet data flow charging, the method comprising the step A2: establishing a dialogue between the TPF and the CRJF for a bearer having the same APN per user.
  • the TPF allocates a session number.
  • the A2 is further included: the TPF determines, according to the user identifier information and the APN information, whether a dialog for the APN of the user has been established with the CRF. If not, the step is performed. A2.
  • the step A2 is as follows: The TPF establishes a TPF/CRF conversation state model, assigns a conversation number to the current conversation, and then provides the conversation number to the CRF, and the CRJF establishes a TPF/CRF conversation state model according to the received conversation number.
  • the CRF allocates a session number.
  • the A2 further includes: the CRF determines whether the bearer setup indication is received. If yes, the CRF determines whether the TPF has been established with the TPF according to the TPF address information, the user identifier information, and the APN information. The session of the APN of the user, if not established, performs step A2.
  • the step A2 is: CRF establishes a TPF/CRF dialog state model, assigns a dialog number to the current dialog, and then provides the dialog number to the TPF, and the TPF establishes a TPF/CRF dialog state model according to the received dialog number.
  • the bearer setup indication, TPF address information, user identification information, and APN information are from the TPF.
  • the TPF and the CRF jointly allocate a session number.
  • the A2 further includes: The TPF determines whether the CRF has been established according to the user identification information and the APN information. For the conversation of the APN of the user, if not, step A2 is performed.
  • the step A2 is: the TPF establishes a TPF/CRF conversation state model, allocates a TPF partial conversation number for the current conversation, and provides the TPF partial conversation number to the CRF, and the CRF establishes a TPF/CRF conversation state model to allocate a CRF partial conversation for the current conversation.
  • the method further includes: the CRF provides a complete dialog number to the TPF, and the TPF indexes to the previously established TPF/CRF conversation state model according to the TPF part conversation number in the complete conversation number, and the TPF session number Updated to the full conversation number.
  • the method further includes: the TPF assigning a bearer identifier to each newly established bearer, and providing the bearer identifier to the CRF.
  • the present invention also provides a dialog establishment method based on packet data flow charging, the method comprising the step A3: establishing a dialogue for the bearers owned by each user between the TPF and the CRF.
  • the TPF allocates a session number.
  • the A3 further includes: the TPF determines, according to the user identification information, whether a dialogue with the CRF has been established with the CRF, and if not, performs step A3.
  • the step A3 is as follows: The TPF establishes a TPF/CRF dialog state model, assigns a conversation number to the current conversation, and then provides the conversation number to the CRF, and the CRF establishes a TPF/CRF conversation state model according to the received conversation number.
  • the CRF allocates a session number.
  • the A3 further includes: the CRF determines whether the bearer setup indication is received, and if yes, the CRF determines, according to the TPF address information and the user identifier information, whether the user has been established with the TPF.
  • the dialog if not established, performs step A3.
  • the step A3 is: CRF establishes a TPF/CRF conversation state model, assigns a conversation number to the current conversation, and then provides the conversation number to the TPF, and the TPF establishes a TPF/CRF conversation state model according to the received conversation number.
  • the bearer setup indication, TPF address information, and user identity information are from the TPF.
  • the TPF and the CRF jointly allocate a session number.
  • the A3 further includes: The TPF determines, according to the user identification information, whether a dialogue with the CRF has been established with the CRF. If not, step A3 is performed.
  • the step A3 is: the TPF establishes a TPF/CRF conversation state model, allocates a TPF partial conversation number for the current conversation, and provides the TPF partial conversation number to the CRF, and the CR establishes a TPF/CRF conversation state model to allocate a CRF partial conversation for the current conversation.
  • the TPF part of the dialogue number and the CRF part of the dialogue number constitute the complete dialogue number of the TPF/CRF dialogue.
  • the step A3 further includes: the CRF provides a complete dialog number to the TPF, and the TPF indexes the previously established TPF/CRF conversation state model according to the TPF part conversation number in the complete conversation number, and updates the TPF conversation number to the complete conversation number.
  • the method further includes: the TPF assigning a bearer identifier to each newly established bearer, and providing the bearer identifier to the CRF.
  • the present invention provides a way for a plurality of TPFs to establish a dialogue with the CRF. For example, a dialogue between the TPF and the CRF can be established for each bearer of each user; and a dialogue between the TPF and the CRF can be directed to each user.
  • the bearer with the same APN is established; for example, the dialogue between the TPF and the CRP can be established for all bearers of each user, and the mechanism for establishing a dialogue between the TPF and the CRF is improved, so that the implementation of the entire billing process is more complete.
  • the present invention provides a manner of establishing a dialogue between a plurality of TPFs and CRFs, and can be flexibly selected according to actual billing conditions.
  • Figure 1 shows the PDP Context activation, data transmission, deactivation flowchart
  • Figure 2A shows the structure of the FBC system supporting online charging
  • FIG. 2B is a structural diagram of an FBC system supporting offline charging
  • FIG. 3 shows a schematic diagram of a dialog establishment process for establishing a TPF/CRF session for each bearer and assigning a session number by the TPF;
  • Figure 4 shows a schematic diagram of a dialog establishment process for establishing a TPF/CRF session for each bearer and assigning a session number by the CRF;
  • FIG. 5 is a schematic diagram showing a dialog establishment process for establishing a TPF/CRF session for each bearer and jointly assigning a session number by the TPF and the CRF;
  • Figure 6 shows a schematic diagram of establishing a TPF/CRF session for each bearer of each user
  • FIG. 7 is a schematic diagram showing a dialog establishment process for establishing a TPF/CRF session for a bearer having the same APN for each user and assigning a session number by the TPF;
  • FIG. 8 is a schematic diagram showing a dialog establishment process for establishing a TPF/CRF session for a bearer having the same APN for each user and assigning a session number by the CRF;
  • FIG. 9 is a schematic diagram showing a dialog establishment process for establishing a TPF/CRF session for each user's bearer with the same APN and jointly assigning a session number by the TPF and the CRF;
  • Figure 10 shows a schematic diagram of establishing a TPF/CRF session for each user's bearer with the same APN
  • Figure 11 shows a schematic diagram of a dialog establishment process for establishing a TPF/CRF session for all bearers of each user and assigning a session number by the TPF;
  • Figure 12 shows a schematic diagram of a dialog establishment process for establishing a TPF/CRF session for all bearers of each user and assigning a session number by the CRF;
  • Figure 13 shows a schematic diagram of a dialog establishment process for establishing a TPF/CRF session for all bearers of each user and jointly assigning a session number by the TPF and the CRF;
  • Figure 14 shows a schematic diagram of establishing a TPF/CRF session for all bearers for each user. Mode for carrying out the invention
  • the present invention provides a way for a plurality of TPFs to establish a dialogue with the CRF.
  • a dialogue between the TPF and the CRF can be established for each bearer of each user, and for GPRS, that is, each PDP Context for each user.
  • the state model establishes a dialogue between the TPF and the CRF; and the dialogue between the TPF and the CRJF can establish a dialogue between the TPF and the CRF for each user's bearer with the same APN, for GPRS, Establish a dialogue between the TPF and the CRF for all bearers with the same APN for each user; and the dialog between the TPF and the CRF can be established for all bearers of each user.
  • the user's GPRS bearer Activate/Deactivate state model establishes a dialogue between the TPF and the CRF. After the TPF/CRF session is established, the TPF exchanges information with the CRF. For example, the CRF provides charging rules to the TPF. The TPF charges the filtered IP data according to the charging rules provided by the CRF.
  • a dialogue between the TPF and the CRF is established for each bearer of each user, that is, a new dialogue between the TPF and the CRF is established when each bearer is established, and each TPF/CRF dialog state model corresponds to a single bearer.
  • the state model is established.
  • the TPF/CRF session is established.
  • the bearer is terminated, the TPF/CRF session is released.
  • each TPF/CRF conversation state model corresponds to a single PDP Context state model. In the GGSN, there is at most one PDP Context state model for each active GPRS PDP Context.
  • the session number is assigned by the TPF
  • a new TPF/CRF session state model is established in each bearer establishment TPF
  • a new session number is assigned to the dialog, and corresponding information, such as a session number, is stored.
  • the user information, the bearer attribute, the network information, and the like and then provide the CRF with the assigned session number, which may be carried in the charging rule request sent by the TPF to the CRF, and the CRF receives the request for carrying the new session number charging rule.
  • the new TPF/CRF dialog state model stores corresponding information, such as session number, user information, bearer attribute, network information, etc.; if the session number is assigned by the CRF, the TPF sends a bill to the CRF when each bearer is established.
  • a rule request and carrying a corresponding bearer setup indication, to identify that the charging rule request is initiated based on bearer establishment
  • the CRF establishes a new TPF/CRF dialog state model according to the bearer setup indication, and allocates a new session number to the dialog, and Storing corresponding information, such as a dialog number, user information, bearer attribute, network information, etc., and then providing the TPF with the assigned session number, which may be carried in the message that the CRF returns the charging rule to the TPF, and the TPF receives the carried
  • a new TPF/CRF dialog state model is established, and corresponding information such as a session number, user information, bearer attribute, network information, etc.
  • the TPF establishes a new TPF/CR dialog state model, assigns a new TPF part session number to the dialog, and saves
  • the corresponding information such as the TPF part conversation number, the user information, the bearer attribute, the network information, etc., and provides the allocated TPF part conversation number to the CRF, and the TPF part conversation number may be carried in the charging rule request sent by the TPF to the CRF.
  • the CRF After receiving the charging rule request carrying the TPF part conversation number, the CRF establishes a new TPF/CRF conversation state model, allocates the CRF part conversation number, and forms a complete conversation number with the TPF part conversation number provided by the TPF, and stores the corresponding conversation number.
  • the information such as the complete conversation number, the user information, the bearer attribute, the network information, etc.
  • the CRF provides the complete conversation number to the TPF, and the complete conversation number can be carried in the message that the CRF returns the charging rule to the TPF, and the TPF receives the carried
  • the charging rule of the complete session number responds, according to the TPF part conversation number in the complete session number, index to the previously established TPF/CRF conversation state model, and update the stored information, such as updating the TPF part conversation number to a complete dialogue. number.
  • FIG. 3 shows a schematic diagram of a dialog establishment process for establishing a TPF/CRF session for each bearer and assigning a session number by the TPF. As shown in FIG. 3, a TPF/CRF session is established for each bearer, and the session number is assigned by the TPF.
  • the dialogue establishment process includes the following steps:
  • Step 301 The user equipment (UE) sends a Bearer Service Request to the TPF.
  • the GGSN receives the Create PDP Context Request.
  • Step 302 After receiving the bearer setup request, the TPF establishes a TPF/CRF dialog state model, allocates a session number for the current session, and stores corresponding information, such as a session number, user information, bearer attribute, network information, etc., and then sends the message to the CR. Request Charging Rules, which carry the input information for the CRF to determine the charging rule and the assigned session number.
  • Step 303 After receiving the charging rule request, the CRF establishes a TPF/CRF session state model according to the new session number carried in the charging rule request, and stores corresponding information, such as a session number, user information, a bearer attribute, and network information. Then, the CRF can also input the information according to the charging rule request, and according to the relevant input information provided by the AF, if it is the online charging mode, the appropriate charging rule can also be selected according to the relevant input information provided by the OCS.
  • the CRF After receiving the charging rule request, the CRF establishes a TPF/CRF session state model according to the new session number carried in the charging rule request, and stores corresponding information, such as a session number, user information, a bearer attribute, and network information. Then, the CRF can also input the information according to the charging rule request, and according to the relevant input information provided by the AF, if it is the online charging mode, the appropriate charging rule can also be selected according to the relevant input information provided by the OCS.
  • Step 304 After selecting an appropriate charging rule, the CRF returns a Provision Charging Rule to the TPF as a response to the charging rule request, where the provided charging rule may carry the selected charging rule.
  • Step 305 After receiving the charging rule, the TPF indexes to the corresponding session according to the session number, and performs corresponding operations on the charging rule selected by the CRP according to the charging rule operation instruction. If the online charging mode is performed, the TPF continues to execute. Step 306 to step 308, if it is the offline charging mode, step 308 is directly executed. Step 306: The TPF sends a credit request (Credit Request) to the OCS according to the online charging indication in the charging rule, and requests the credit information of the user from the OCS.
  • a credit request Credit Request
  • Step 307 After receiving the credit request, the OCS determines the credit of the user, and then returns a credit response (Credit Response) to the TPF. If the OCS determines the credit of the user, the credit response carries the credit of the user; if the OCS is not determined The user's credit, the credit response may carry an error reason value.
  • Step 308 The TPF returns an bearer setup response (Establish Bearer Service Accept) to the UE. If the TPF can establish a bearer according to the existing information, if the OCS returns the credit of the user, the bearer setup response is a bearer setup success response, and the TPF accepts the UE to initiate the response. The bearer establishment request, and the subsequent bearer establishment process; if the TPF is unable to establish the bearer with the existing information, for example, the OCS does not return the credit of the user, the bearer setup response is a bearer setup failure response, and the TPF rejects the bearer setup request initiated by the UE. .
  • FIG. 4 shows a schematic diagram of a dialog establishment process for establishing a TPF/CRF session for each bearer and assigning a session number by the CRF.
  • a TPF/CRF session is established for each bearer, and the session number is assigned by the CRF.
  • the dialogue establishment process includes the following steps:
  • Step 401 is the same as step 301.
  • Step 402 After receiving the bearer setup request, the TPF sends a charging rule request to the CRF, where the charging rule request carries the input information for determining the charging rule by the CRF, and further carries the bearer establishment indication, which is used to identify the The fee rule request is initiated based on bearer establishment.
  • Step 403 After receiving the charging rule request, the CRF establishes a TPF/CRF session state model according to the bearer establishment indication carried in the charging rule request, allocates a new session number for the current session, and stores corresponding information, such as a session number. User information, bearer attributes, network information, etc., and then the CRF can input information according to the charging rule request, and according to the relevant input information provided by the AF, if it is an online charging mode, it can also be based on the relevant input provided by the OCS. Information, select the appropriate billing rules.
  • Step 404 After the CRF selects an appropriate charging rule, the CRF returns a charging rule to the TPF, where the charging rule can carry the selected charging rule, the charging rule operation indication, and the assigned session number.
  • Step 405 After receiving the charging rule, the TPF establishes a new TPF/CRF session state model according to the new session number carried in the charging rule message, and stores corresponding information, such as a session number, a user information, and a bearer attribute. And the network information, and the corresponding operation of the charging rule selected by the CRF according to the charging rule operation instruction. If it is the online charging mode, continue to perform steps 406 to 408, and if it is the offline charging mode, directly execute Step 408.
  • the TPF After receiving the charging rule, the TPF establishes a new TPF/CRF session state model according to the new session number carried in the charging rule message, and stores corresponding information, such as a session number, a user information, and a bearer attribute. And the network information, and the corresponding operation of the charging rule selected by the CRF according to the charging rule operation instruction. If it is the online charging mode, continue to perform steps 406 to 408, and if it is the offline charging mode, directly execute Step 408.
  • Steps 406 to 407 are the same as steps 306 to 307.
  • Step 408 is the same as step 308.
  • FIG. 5 shows a schematic diagram of a dialog establishment process for establishing a TPF/CRF session for each bearer and jointly assigning a session number by the TPF and the CRF.
  • a TPF/CRF session is established for each bearer, and is represented by the TPF.
  • the process of establishing a dialogue with the CRF to assign a session number includes the following steps:
  • Step 501 is the same as step 301.
  • Step 502 After receiving the bearer setup request, the TPF establishes a TPF/CRF session state model, allocates a TPF part session number for the current session, and stores corresponding information, such as a TPF part session number, user information, bearer attribute, network information, and the like. Then, the charging rule request is sent to the CRF, and the charging rule request carries the input information for the CRF to determine the charging rule and the allocated TPF part of the session number.
  • Step 503 After receiving the charging rule request, the CRF establishes a TPF/CRF session state model according to the incomplete session number carried in the charging rule request, that is, the TPF part conversation number, allocates the CRF part session number, and stores the corresponding Information, such as a complete dialog number (consisting of the TPF partial session number received in step 502 and the currently assigned CRF part session number), user information, bearer attributes, network information, etc., and then the CRF is carrying in the request according to the charging rule
  • the input information of 01237 can also be based on the relevant input information provided by AF. If it is online charging mode, it can also select the appropriate charging rule according to the relevant input information provided by OCS.
  • Step 504 After the CRF selects an appropriate charging rule, the CRF returns a charging rule to the TPF, as a response to the charging rule request, where the charging rule can carry the selected charging rule and the charging rule operation indication.
  • Step 505 After receiving the provided charging rule carrying the complete session number, the TPF indexes the previously established TPF/CRF session state model according to the TPF part conversation number in the complete session number, and updates the stored information, for example, The TPF part of the session number is updated to the complete session number, and then the TPF performs the corresponding operation on the charging rule selected by the CRF according to the charging rule operation instruction. If it is the online charging mode, the process proceeds to steps 506 to 508, if it is an offline meter. In the fee mode, step 508 is directly executed.
  • Steps 506 to 507 are the same as steps 306 to 307.
  • Step 508 is the same as step 308.
  • each TPF/CRF session When a TPF/CRF session is established for each bearer of each user, the operations in each TPF/CRF session (such as providing, modifying, deleting charging rules, or providing an event trigger) are independent of each other. That is, these operations are for each bearer of each user, and the CRF can perform corresponding FBC control on each user bearer through the TPF/CRF dialog state model.
  • FIG. 6 shows a schematic diagram of establishing a TPF/CRF session for each bearer of each user.
  • each bearer state model in the TPF Established Bearer State Model
  • TPF/CRF Instance State Model corresponds to a TPF/CRF Instance State Model (TPF/CRF Instance State Model)
  • TPF/CRF Instance State Model TPF/CRF Instance State Model
  • GPRS it is established when the Create PDP context request is received; Released when the state model is issued, for GPRS, released when the corresponding Delete PDP context request is received.
  • a dialogue between the TPF and the CRF can be established for each user with the same port, that is, when a new IP data stream bearer is established for each user, a new TPF and CRF are established.
  • the dialog for subsequent new bearers of the same APN established by the same user, directly performs FBC control on the bearer based on the previously established dialog, without establishing a new dialog.
  • a user can establish multiple bearers with the same APN at the same time. For GRPS, one user can simultaneously establish multiple PDP Contexts with the same APN.
  • the entity that assigns the session number determines whether the CRP/TPF dialog state model for the APN of the user has been established, and if so, the previously assigned APN for the user is used.
  • the session number identifies the relationship between the currently established bearer and the previously established TPF/CRF session. Otherwise, a new TPF/CRF dialog state model is established and a new session number is assigned.
  • the TPF determines whether the TPF/CRF conversation state model for the APN of the user has been established according to the user identifier and the APN information. If yes, the TPF directly uses the previously established session number in the TPF/CR session state model of the APN for the user to identify the relationship between the currently established bearer and the previously established TPF/CRF session.
  • the TPF establishes a The user's TPF/CRF conversation state model of the APN, assigning a new conversation number to the conversation, and storing corresponding information, such as a conversation number, user information, bearer attribute, network information, etc., and then providing the assigned conversation number to the CRF.
  • the session number may be carried in the charging rule request sent by the TPF to the CRF.
  • the CRF After receiving the new session number charging rule request, the CRF establishes a new TPF/CRF conversation state model and stores corresponding information, such as a dialogue. Number, user information, bearer attributes, network information, etc.
  • the TPF sends a charging rule request to the CRF, and carries a corresponding bearer setup indication, which is used to identify that the charging rule request is initiated based on the bearer establishment, and further TPF can provide user identification to CRF,
  • the APN information and the TPF address information, the CRF determines, according to the bearer establishment indication, the user identifier, the APN information, and the TPF address information provided by the TPF, whether the TPF/CRF conversation state model has been established for the APN of the user and the corresponding TPF, and if so, Then, the CRF directly uses the previously established session number in the TPF/CRF session state model of the APN for the user to identify the relationship between the currently established bearer and the previously established TPF/CRF session.
  • the CRJF establishes a target for the user.
  • the APN TPF/CRF conversation state model assigns a new session number to the conversation and stores corresponding information, such as a session number, user information, bearer attributes, network information, etc., and then provides the assigned session number to the TPF, the session number It can be carried in the message that the CRF returns the charging rule to the TPF.
  • the TPF After receiving the new session number charging rule response, the TPF establishes a new TPF/CRF session state model and stores corresponding information, such as the session number and user information. , hosting properties, network information, etc.
  • the TPF determines, according to the user identifier and the APN information, whether a TPF/CRF conversation state model for the APN of the user has been established with the CRF, if If yes, the TPF directly uses the previously established session number in the TPF/CRF dialog state model of the APN for the user to identify the relationship between the currently established bearer and the previously established TPF/CRF session.
  • the TPF establishes a The user's TPF/CR conversation state model of the APN, assigns a new TPF part conversation number, and stores corresponding information, such as TPF part conversation number, user information, bearer attribute, network information, etc., and provides the allocated TPF part to the CRF.
  • the conversation number, the TPF part conversation number may be carried in the charging rule request sent by the TPF to the CRF.
  • the CRF After receiving the charging rule request carrying the TPF part conversation number, the CRF establishes a new TPF/CRF conversation state model and allocates the CRF.
  • the TPF part of the dialogue number provided by the TPF constitutes the complete conversation number, and stores the corresponding information, such as the complete conversation number, user information Bearer properties, the network information, and providing the CRF to the TPF complete session number, which may be carried in full session number CRF to the TPF the charging rule returned message, carrying the TPF receives the complete
  • the charging rule of the conversation number responds, according to the TPF part conversation number in the complete conversation number, index to the previously established TPF/CRF conversation state model, and update the stored information, such as updating the TPF part conversation number to the complete conversation number.
  • the TPF exchanges information with the CRF.
  • the CRF provides charging rules to the TPF.
  • the TPF charges the filtered IP data according to the charging rules provided by the CRF.
  • FIG. 7 is a schematic diagram showing a dialog establishment process for establishing a TPF/CRF session for a bearer having the same APN for each user and assigning a session number by the TPF, as shown in FIG. 7, for each user having the same APN.
  • the process of establishing a TPF/CRF session and assigning a session number by the TPF includes the following steps:
  • Step 701 is the same as step 301.
  • Step 702 After receiving the bearer setup request, the TPF determines, according to the user identifier information and the APN information, whether a dialog for the APN of the user has been established with the CRF, and if yes, directly sends a charging rule request to the CRF.
  • the charging rule request carries the input information for the CRF to determine the charging rule and the previously assigned session number, and the previously assigned session number identifies the relationship between the charging rule request in the current session and the previously established TPF/CRP session; Otherwise, the TPF establishes a TPF/CRF dialog state model, assigns a new session number, and stores corresponding information, such as a session number, user information, bearer attributes, network information, etc., and then sends a charging rule request to the CRF, the charging rule The request carries the input information for the CRF to determine the charging rule and the currently assigned session number.
  • Step 703 is the same as step 303.
  • Step 704 is the same as step 304.
  • Step 705 is the same as step 305.
  • Steps 706 to 707 are the same as steps 306 to 307.
  • Step 708 is the same as step 608.
  • 8 is a schematic diagram showing a dialog establishment process for establishing a TPF/CRF session for a bearer having the same APN for each user and assigning a session number by the CRF, as shown in FIG. 8, for each user having the same APN.
  • the process of establishing a TPF/CRF session and the session establishment process by which the CR assigns a session number includes the following steps:
  • Step 801 is the same as step 401.
  • Step 802 After receiving the bearer setup request, the TPF sends a charging rule request to the CRF, where the charging rule request carries the input information for determining the charging rule by the CRF, and further carries a bearer establishment indication, which is used to identify the The fee rule request is initiated based on bearer establishment, as well as user identification information, APN information, and TPF address information.
  • Step 803 After receiving the charging rule request, the CRF determines, according to the bearer establishment indication, the user identification information, the APN information, and the TPF address information carried in the charging rule request, whether the APN has been established with the corresponding TPF for the user.
  • the dialog if yes, directly provides a charging rule to the TPF, and the provided charging rule carries the selected charging rule, the charging rule operation indication, and the previously assigned session number, by using the previously assigned session number. Identifies the relationship between the provisioning charging rule message in the current conversation and the previously established TPF/CR conversation; otherwise, the CRF establishes a TPF/CRF conversation state model, assigns a new conversation number to the current conversation, and stores corresponding information, such as a conversation number.
  • the CRF can input the information according to the charging rule request, and according to the relevant input information provided by the AF, if it is an online charging mode, it can also be based on the relevant input provided by the OCS. Information, select the appropriate billing rules.
  • Step 804 is the same as step 404.
  • Step 805 is the same as step 405.
  • Steps 806 to 807 are the same as steps 406 to 407.
  • Step 808 is the same as step 408.
  • FIG. 9 shows the establishment of a TPF/CRF for a bearer with the same APN for each user.
  • the establishment process includes the following steps:
  • Step 901 is the same as step 501.
  • Step 902 After receiving the bearer setup request, the TPF determines, according to the user identifier information and the APN information, whether a dialog for the APN of the user has been established with the CRF, and if yes, directly sends a charging rule request to the CRF.
  • the charging rule request carries the input information for the CR to determine the charging rule and the previously assigned session number, and the previously assigned session number identifies the relationship between the charging rule request in the current session and the previously established TPF/CRF session; Otherwise, the TPF establishes a TPF/CRF session state model, assigns a new TPF part session number to the current session, and stores corresponding information, such as a TPF part session number, user information, bearer attributes, network information, etc., and then sends a bill to the CRF.
  • the rule request, the charging rule request carries the input information for determining the charging rule by the CRF and the currently assigned TPF part session number.
  • Step 903 is the same as step 503.
  • Step 904 is the same as step 504.
  • Step 905 is the same as step 505.
  • Steps 906 to 907 are the same as steps 506 to 507.
  • Step 908 is the same as step 508.
  • the operations in each TPF/CRF session are for the same user.
  • the CRF can perform unified FBC control on the bearers with the same APN for the user through the conversation state model.
  • FIG 10 shows a schematic diagram of establishing a TPF/CRP session for each user's bearer with the same APN, as shown in Figure 10, for the same user in the TPF, each TPF/CRF conversation state model is always Contains at least one or more bearer build state models, and And these established multiple bearers have the same APN.
  • the TPF/CRF session state model consists of at least one or more GPRS PDP context state models (GPRS PDP context state models), and when the TPF/CRF dialog state model consists of multiple GPRS PDP Context state models, The bearers in these multiple GPRS PDP Context state models all have the same APN.
  • the TPF may be required to allocate a bearer ID (Bearer ID) to the bearer when each bearer is established, and the first time to the CRF for the bearer TPF.
  • the charging rule carries the assigned bearer identifier, or carries the bearer identifier when the TPF reports the trigger event to the CRF for the first time.
  • the bearer ID assigned by the TPF needs to be guaranteed to be the same for the bearer ID of the same APN.
  • the bearer IDs of different bearers under the same APN are not duplicated.
  • the CRF can perform different FBC control on different bearers of the same user according to the TPF/CRF conversation state model and bearer identity.
  • a dialogue between the TPF and the CRF can be established for all bearers of each user, that is, a new TPF/CRF session is established for each user's first bearer established in the TPF, and there is no need to follow the user in the TPF.
  • a new bearer established in the middle establishes a new dialogue.
  • the entity that assigns the session number determines whether a TPF/CRF session for all bearers in the TPF for the user has been established, and if so, directly uses the previously assigned The user-hosted session number identifies the relationship between the currently established bearer and the previously established TPF/CRF session. Otherwise, a TPF/CRF session state model for all bearers of the user is established and a new session number is assigned.
  • the TPF determines, according to the user identification information, whether a TPF/CRF conversation state model for all bearers of the user has been established, if Yes, then the TPF directly uses the previously established dialog in the TPF/CRF dialog state model for all bearers of the user. The number identifies the relationship between the currently established bearer and the previously established TPF/CRF session. Otherwise, the TPF determines that the bearer setup is the first bearer established by the user in the TPF, and then establishes a TPF/CRF for all bearers of the user.
  • the conversation state model assigns a new session number and stores corresponding information, such as a session number, user information, bearer attributes, network information, etc., and then provides the assigned session number to the CRF, which can be carried in the TPF to the CRF.
  • the CRF In the charging rule request, after receiving the new session number charging rule request, the CRF establishes a new TPF/CRF conversation state model, and stores corresponding information, such as a session number, user information, bearer attribute, network information, and the like.
  • the TPF sends a charging rule request to the CRF, and carries a corresponding bearer setup indication, which is used to identify that the charging rule request is initiated based on the bearer establishment, and further
  • the TPF can provide the user identifier and the TPF address information to the CRF.
  • the CRF determines whether the TPF/CRF session state model for all bearers of the user has been established with the corresponding TPF according to the bearer setup indication, the TPF address information, and the user identifier information provided by the TPF.
  • the CRF directly uses the previously established session number in the TPF/CRF dialog state model for all bearers of the user to identify the relationship between the currently established bearer and the previously established TPF/CRF session, otherwise, the CRF judgement
  • the bearer establishment is the first bearer established by the user in the corresponding TPF, then establishes a TPF/CRF conversation state model for all bearers of the user, assigns a new session number, and stores corresponding information, such as a session number, a user. Information, bearer attributes, network information, etc., and then provide the assigned dialog number to the TPF, the pair
  • the message number can be carried in the message that the CRF returns the charging rule to the TPF.
  • the TPF After receiving the new session number charging rule response, the TPF establishes a new TPF/CRF session state model, and stores corresponding information, such as a session number. User information, bearer properties, network information, and more.
  • the TPF determines, according to the user identification information, whether a TPF/CRF conversation state model for all bearers of the user has been established, and if so, the TPF Use previously created targeting
  • the session number in the user TPF/CRF session state model identifies the relationship between the currently established bearer and the previously established TPF/CRF session. Otherwise, the TPF determines that the bearer setup is the first bearer established by the user in the TPF.
  • TPF/CRF conversation state model for all bearers of the user, assigning a new TPF part conversation number, and storing corresponding information, such as a TPF part conversation number, user information, bearer attribute, network information, etc., and providing the CRF with the CRF
  • the assigned TPF part conversation number, the TPF part conversation number may be carried in the charging rule request sent by the TPF to the CRF, and the CRF establishes a new TPF/CRF conversation state after receiving the charging rule request carrying the TPF part conversation number.
  • the model assigns the CRF part of the conversation number, and the part of the conversation number provided by the TPF constitutes a complete conversation number, and stores corresponding information, such as complete conversation number, user information, bearer attribute, network information, etc., and then the CRF provides the complete dialogue to the TPF.
  • the complete session number can be carried in the message that the CRF returns the charging rule to the TPF, and the TPF receives the charging rule carrying the complete session number.
  • index to the previously established TPF/CRF conversation state model and update the stored information, such as updating the TPF part conversation number to the complete conversation number.
  • the method for determining whether the TPF/CRF dialog state model for all bearers of the same user has been established by the above TPF or CRF may be performed by establishing a bearer Activate/Deactivate state model in the TPF or CRF.
  • the TPF or CRF When receiving the first bearer setup request of a certain user, the TPF or CRF establishes a bearer activation Activate/deactivate Deactivate state model, and releases the bearer Activate/Deactivate state model when receiving the last bearer termination request from the user. In this way, it can be judged whether the TPF/CRF conversation state model for all the bearers of the user has been established by judging whether there is a load/deactivate state model for the user in the TPF or CRF.
  • FIG. 11 is a schematic diagram showing a dialog establishment process for establishing a TPF/CRJF session for all bearers of each user and assigning a session number by the TPF, as shown in FIG. 11, establishing a TPF/CRF session for all bearers of each user, And the dialog establishment process of assigning the conversation number by the TPF includes the following steps:
  • Step A1 is the same as step 301.
  • Step A2 After receiving the bearer setup request, the TPF determines, according to the user identifier information, whether a TPF/CRF session for all bearers of the user has been established with the CRF, and if yes, directly sends a charging rule request to the CRF, where the charging is performed.
  • the rule request carries the input information for the CRF to determine the charging rule and the previously assigned session number, and the previously assigned session number identifies the relationship between the charging rule request in the current session and the previously established TPF/CR; otherwise, the TPF Establish a TPF/CRF conversation state model for all bearers of the user, assign a new session number, and store corresponding information, such as a session number, user information, bearer attribute, network information, etc., and then send a charging rule request to the CRF.
  • the charging rule request carries the input information for the CRF to determine the charging rule and the currently assigned session number.
  • Step A3 is the same as step 303.
  • Step A4 is the same as step 304.
  • Step A5 is the same as step 305.
  • Steps A6 to 907 are the same as steps 306 to 307.
  • Step A8 is the same as step 308.
  • FIG. 12 is a schematic diagram showing a dialog establishment process for establishing a TPF/CRF session for all bearers of each user and assigning a session number by the CKF. As shown in FIG. 12, a TPF/CRF session is established for all bearers of each user, And the dialog establishment process of assigning the conversation number by the CRF includes the following steps:
  • Step B1 is the same as step 401.
  • Step B2 After receiving the bearer setup request, the TPF sends a charging rule request to the CRF.
  • the charging rule request carries the input information for determining the charging rule by the CRF, and further carries a bearer establishment indication, which is used to identify that the charging rule request is initiated based on the bearer establishment, and the user identification information and the TPF address information.
  • Step B3 After receiving the charging rule request, the CRF determines, according to the bearer establishment indication, the user identification information, and the TPF address information carried in the charging rule request, whether the TPF/CRF for all the bearers of the user has been established with the corresponding TPF.
  • the dialog if yes, directly provides a charging rule to the TPF, and the provided charging rule carries the selected charging rule, the charging rule operation indication, and the previously assigned session number, and identifies the previously assigned session number.
  • Step B4 is the same as step 404.
  • Step B5 is the same as step 405.
  • Steps B6 to A7 are the same as steps 406 to 407.
  • Step B8 is the same as step 408.
  • FIG. 13 is a schematic diagram showing a dialog establishment process for establishing a TPF/CRF session for all bearers of each user and jointly assigning a session number by the TPF and the CRF. As shown in FIG. 11, a TPF/ is established for all bearers of each user.
  • the CRF dialogue, and the dialog establishment process in which the TPF and the CRF jointly allocate the session number includes the following steps:
  • Step C1 is the same as step 501.
  • Step C2 After receiving the bearer setup request, the TPF determines, according to the user identifier information, whether a conversation for all bearers of the user has been established, and if yes, directly sends a report to the CRF.
  • the charging rule request carries the input information for the CRF to determine the charging rule and the previously assigned session number, and the previously assigned session number identifies the charging rule request in the current session and the previously established TPF/ The relationship of the CRF conversation; otherwise, the TPF establishes a TPF/CRF conversation state model, assigns a new TPF part conversation number to the current conversation, and stores corresponding information, such as a TPF part conversation number, user information, bearer attributes, network information, etc., and then The charging rule request is sent to the CRF, where the charging rule request carries the input information for determining the charging rule by the CRF and the currently assigned TPF part session number.
  • Step C3 is the same as step 503.
  • Step C4 is the same as step 504.
  • Step C5 is the same as step 505.
  • Steps C6 to C7 are the same as steps 506 to 507.
  • Step C8 is the same as step 508.
  • each TPF/CRF session When establishing a dialogue between TPF and CRF for all bearers of each user, the operations in each TPF/CRF session (such as providing, modifying, deleting charging rules, or providing Event trigger trigger events, etc.) are User bearers are irrelevant, that is, these operations are for all bearers of a user.
  • the CRF can perform unified FBC control on all bearers of the user through the dialog state model.
  • the TPF may be required to allocate a corresponding bearer identifier for the bearer when each bearer is established, and request the charging rule for the first time to the CRF for the bearer TPF. Carrying the assigned bearer identifier, or carrying the bearer identifier when reporting the trigger event report to the CRF for the first time.
  • the bearer ID assigned by the TPF needs to be guaranteed to be unique to the bearer ID of the same user and will not be duplicated with other bearer IDs of the user.
  • the CRF can perform different FBC control on different bearers of the same user according to the TPF/CRF dialog state model bearer identifier.
  • FIG 14 shows an illustration of establishing a TPF/CRF session for all bearers for each user.
  • each TPF/CRF dialog state model always contains at least one Bearer Activate/Deactivate State Model
  • TPF The /CRF dialog state model may further include a plurality of bearer setup state models associated with the bearer activation/deactivation state model.
  • the TPF/CRF session state model consists of at least one GPRS Activate/Deactivate State Model and optionally multiple GPRS PDP context State Models.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Telephonic Communication Services (AREA)
  • Meter Arrangements (AREA)
  • Auxiliary Devices For And Details Of Packaging Control (AREA)
  • Wrapping Of Specific Fragile Articles (AREA)
  • Communication Control (AREA)

Description

一种基于分组数据流计费的对话建立方法 技术领域
本发明涉及分组数据计费领域， 特别是指一种基于分组数据流计费 的对话建立方法。 发明背景
随着分组数据业务应用的逐渐广泛， 如何准确合理地对分组数据业 务进行计费， 已成为运营商普遍关注的问题。
图 1示出了分组数据协议上下文（ PDP Context, Packet Data Protocol Context )激活、 数据传输、 去激活流程图， 如图 1所示， 在通用分组无 线业务（GPRS, General Packet Radio Service ) 中， 激活 PDP Context、 与外部分组数据网络（PDN, Packet Data Network )进行数据交互、 去 激活该 PDP Context的实现过程包括以下步骤：
步骤 101 : 移动终端 （MS ) 向服务通用分组无线业务支持节点 ( SGSN, Serving GPRS Support Node )发送 PDP Context 激活请求 ( Activate PDP Context Request ), 该 Activate PDP Context Request中携 带有网络层业务访问点标识（ NSAPI, Network Layer Service Access Point Identifier ), PDP类型、 接入点名称 ( APN, Access Point Name ) 要求 的服务质量（ QoS )参数、事务标识（ TI, Transaction Identifier )等信息 , 其中， NSAPI在 SGSN和网关通用分组无线业务支持节点 （GGSN, Gateway GPRS Support Node )之间作为隧道标识（ TID, Tunnel Identifier ) 的组成部分， 用于标识 PDP Context; PDP类型包括端对端协议（ PPP, Peer-Peer Protocol )类型、 网际协议 ( IP, Internet Protocol )类型等； APN 可由 MS向 SGSN提供， SGSN根据 APN寻址到相应 GGSN, GGSN根 据 APN确定 MS所要访问的外部网络， MS也可不向 SGSN提供 APN, 此时， 由 SGSN根据 MS用户的签约信息选择缺省的 APN; QoS参数为 MS指定的分组数据业务所要达到的质量要求； TI用于 MS标识某个 PDP context。
步骤 102: SGSN收到 Activate PDP Context Request后， 与 MS进行 安全性检查和加密， 该步骤为可选步骤。
步骤 103: SGSN根据 APN解析 GGSN的地址信息， 如果 SGSN能 够根据 APN解析出 GGSN的地址信息， 则为 PDP Context创建 TEID , 该 TEID可为国际移动用户标识 ( IMSI, International Mobile Subscriber Identity ) 与 NSAPI的组合， 然后 SGSN向 GGSN发送 PDP Context创 建请求（ Create PDP Context Request ), 该 PDP Context创建请求中携带 有 PDP类型、 PDP地址、 APN, QoS参数、 TEID, 选择模式等， 其中， PDP地址可为 MS的 IP地址， 为可选参数， PDP Context创建请求中可 不携带 PDP地址， 此时， 在后续的处理过程中， 可由 GGSN为 MS分 配 IP地址， 也可由最终与 MS建立连接的 PDN为 MS分配 IP地址； 选 择模式是指 APN的选择模式， 即 APN是由 MS选定的还是由 SGSN选 定的。 如果 SGSN无法根据 APN解析出 GGSN的地址信息， 则 SGSN 拒绝 MS发起的 PDP Context激活请求。
步骤 104: GGSN收到 PDP Context创建请求后， 根据 APN确定外 部 PDN, 然后分配计费标识（Charging ID )、 启动计费， 并且协商 QoS, 如果 GGSN能够满足 QoS参数的服务质量要求， 则向 SGSN返回 PDP Context创建响应 （ Create PDP Context Response ), 该 PDP Context创建 响应中携带有 TEID、 PDP地址、 链路承载 （Backbone Bearer )协议、 商定的 QoS参数、 Charging ID等信息。 如果 GGSN无法满足 QoS参数 的服务质量要求， 则 GGSN拒绝 SGSN发起的 PDP Context创建倩求， 然后 SGSN拒绝 MS发起的 PDP Context激活请求。
步骤 105: SGSN收到 PDP Context创建响应后， 在 PDP Context中 插入用于标识 PDP Context的 NSAPI和 GGSN地址信息，并根据商定的 QoS 参数选择无线优先权， 然后向 MS 返回 PDP Context 激活响应 ( Activate PDP Context Accept ),该 PDP Context激活响应中携带有 PDP 类型、 PDP地址、 TI、 商定的 QoS参数、 无线优先权、 PDP配置选项等 信息。 并且， SGSN启动计费。 MS收到 PDP Context激活响应， 就已经 建立了 MS与 GGSN直接的路由， 可以进行分组数据的传输了。
步驟 106: MS通过 SGSN、 GGSN与 PDN进行分组数据的交互。 步骤 107: 结束分组数据交互后， MS向 SGSN发送 PDP Context去 激活请求（ Deactivate PDP Context Request )，该 PDP Context去激活请求 中携带有 TI。
步骤 108: SGSN收到 PDP Context去激活请求后 , 与 MS进行安全 性检查和加密， 该步骤为可选步骤。
步驟 109〜步骤 111 : SGSN向 GGSN发送 PDP Context删除请求 ( Delete PDP Context Request )，该 PDP Context删除请求中携带有 TEID。
GGSN收到 PDP Context删除请求后， 结束对 MS的计费， 删除对应于 TEID的 PDP Context, 然后向 SGSN发送 PDP Context删除响应（ Delete PDP Context Response ),该 PDP Context删除响应中携带有 TEID。 SGSN 收到 PDP Context删除响应后，结束对 MS的计费，删除对应于 TEID的 PDP Context, 然后向 MS发送 PDP Context去激活响应（ Deactivate PDP Context Response ), 该 PDP Context去激活响应中携带有 TI。 MS收到 PDP Context去激活响应后， 删除对应于 ΤΙ的 PDP Context。
由图 1描述的实现过程可见， 当前的 GPRS计费系统中， 由于计费 的起始点设置在 PDP Context激活时，计费的终止点设置在 PDP Context 删除时， 因此只能根据 PDP Context传输的数据流量进行计费， 或是根 据 PDP Context处于激活状态的时间长度进行计费。 然而， 在实际应用 中， MS与 PDN进行数据交互后，该 MS可以基于一个激活的 PDP Context 进行多种业务， 也就是说， 如果 PDN 能够提供多种业务， 如电子邮件 ( Email ) 收发业务、 基于无线应用协议的 （WAP, Wireless Application Protocol )的浏览业务、 基于文件传输协议 ( FTP, File Transfer Protocol ) 的文件传输等业务，则 MS在与该 PDN建立传输通道后，可通过一个激 活的 PDP Context承载该 PDN能够提供的各种业务。 但是， 运营商对于 各种业务的计费模式很可能采用不同的计费方式， 如对于 Email收发业 务可基于 Email接收和发送事件的触发按次计费， 对于 WAP浏览业务 可根据流量计费，对于文件传输业务也可根据流量计费， WAP浏览业务 的费率与文件传输业务的费率却不尽相同， 这样， 根据现有的 GPRS计 费系统， 根本无法对同一 PDP Context承载的不同业务进行区分计费。
针对上述情况， 第三代合作伙伴计划 ( 3GPP, The 3rd Generation Partnership Project )目前正在讨论如何实现基于 IP数据流的计费（ FBC, Flow Based Charging )0 对于一个分组数据业务而言， MS的用户使用该 业务时，传输和接收到的所有 IP数据流（IP Flow ),也可为 IP分组包（IP packet ), 总称为业务数据流（ Service Data Flow ), 即业务数据流是多个 IP数据流組成的集合， 因此基于 IP数据流的计费能够真实反映某个业 务数据流对资源的占用情况。基于 IP数据流的计费可被认为是通过一些 类似筛子的过滤器将同一 PDP Context中承载的不同业务的 IP数据流分 别筛选出来， 然后针对不同过滤器过滤出的 IP数据流进行分别计费， 以 达到对不同的业务数据流分别计费的目的。这样，基于 IP数据流的计费 粒度要远远小于基于一个 PDP Context的计费粒度， 粒度可看作是筛子 孔的大小，基于一个 PDP Context的计费粒度是一个 PDP Context就是一 个筛子孔， 而基于 IP数据流的计费粒度则是一个 IP业务数据流则为一 个筛子孔， 即针对一个 PDP Context中包含多个筛子孔， 因此， 基于 IP 数据流的计费与比基于一个 PDP Context的计费相比， 基于 IP数据流的 计费能够为运营商或业务提供者提供更为丰富的计费手段。
3GPP中对 FBC的系统结构、 功能要求以及消息交互流程等方面均 进行了描述， 支持在线计费的 FBC系统结构如图 2A所示， 基于移动网 络增强逻辑的客户化应用 （ CAMEL , Customised Application for Mobile Network Enhanced Logic ) 的业务控制点 （ SCP, Service Control Point ) 201和基于业务数据流计费的信用控制功能实体（ CCF, Service Data Flow Based Credit Control Function ) 202组成了在线计费系统（ OCS， Online Charging System ) 206。 CCF 202通过 Ry接口与基于业务数据流计费的 计费规则功能实体 ( CRF , Service Data Flow Based Charging Rule Function ) 203 互通， CRF 203 通过 Rx接口与应用功能实体（AF, Application Function ) 204互通， CRF 203通过 Gx接口与传输面功能实 体（TPF, Traffic Plane Function ) 205互通， CCF 202通过 Gy接口与 TPF 205互通。
支持离线计费的 FBC系统结构如图 2B所示， CRP 203通过 R 接 口与 AF 204互通， CRF 203通过 Gx接口与 TPF 205互通， TPF 205通 过 Gz接口分别与计费网关功能实体（ CGF， Charging Gateway Function ) 207和计费采集功能实体（ CCF, Charging Collection Function )208互通。
TPF 205承载 IP数据流， 当 IP数据流的承载建立时， TPF 205通过 Gx接口向 CRF 203发送计费规则请求， 该计费规则请求中携带有与用 户和 MS相关的信息、 承载特性以及与网絡相关的信息等， 其中与用户 和 MS相关的信息可为移动台国际号码（MSISDN )、 国际移动用户标识 ( IMSI )等， 与网络相关的信息可为移动网络编码（MNC )、 移动国家 码（MCC )等。 另外， 由于在 IP数据流传输过程中， 会对承载进行修 改， 如对 QoS参数进行重新协商， 当用户使用同一业务的 QoS参数不 同时， 计费规则可能不同， 如 QoS参数下降相应的费率也下降。 此时， TPF 205可在承载修改时， 重新向 CRF 203发送计费规则请求， 请求新 的计费规则； CRF 203根据 TPF 205提供的上述输入信息选择适当的计 费规则，并向 TPF 205返回选定的计费规则，计费规则.中包括计费机制、 计费类型、 计费键、 业务数据流过滤器、计费规则优先级等信息。 其中， 计费机制可为采用在线计费还是离线计费； 计费类型可为基于时间长度 进行计费还是基于数据流量进行计费； 计费键是与计费费率相关的参 数， CRF 203可不直接向 TPF 205提供计费费率， 而只是向 TPF 205提 供与计费费率相关的参数； 业务数据过滤器用于指示 TPF 205对哪些 IP 数据流进行过滤，然后 TPF 205根据计费规则对过滤出的 IP数据流进行 计费。业务数据过滤器可包含 IP5元组， IP5元組可包括源 /目的 IP地址、 源 /目的端口号（ Port Number )、 协议标识（ Protocol ID )等信息， 例如， CRF 203指示 TPF 205对源地址为 10.0.0.1、 目的地址为 10.0.0.2、 源 / 目的端口号为 20、 协议类型为传输控制协议（TCP ) 的 IP数据流进行 过滤 , 并根据计费规则对过滤出的 IP数据流进行计费。
CRF 203可向 TPF 205提供触发事件（ Event Trigger ),用以要求 TPF 205在特定事件发生时， 向 CRF 205请求新的计费规则， 如 CRF 203要 求 TPF 205在某些承载进行修改的事件发生时， 向 CRF 203请求新的计 费规则。
CRP 203除了根据 TPF 205提供的输入信息选择适当的计费规则之 外， CRP 203还可根据 AF 204或 OCS 206的输入信息选择适当的计费 规则， 如 AF 204通知 CRF 203用户当前使用的业务类型， CRF 203根 据该业务类型选择相应的计费规则。 OCS 206由 SCP 201和 CCF ( Service Data Flow Based Credit Control Function ) 202两个功能实体组成， 其中， CCF ( Service Data Flow Based Credit Control Function ) 202是执行信用控制的功能实体，仅应用于在线 计费系统， 可通过在现有的 OCS 206中增加新的功能来实现。 在在线计 费过程中， CCF ( Service Data Flow Based Credit Control Function ) 202 对用户信用进行管理和控制，当用户使用业务时 , CCF( Service Data Flow Based Credit Control Function ) 202对该用户信用池中的信用进行鉴权， 并通过 Gy接口向 TPF 205下发用户能够使用的信用。
对应于 GPRS网络， TPF 205为 GGSN, AF为 PDN中的一个业务 网关或业务服务器， CRF 203为新增的逻辑实体。 TPF 205为计费规则 的执行点 , CRF 203为计费规则的控制点。
目前， 规范中定义了在 CRF和 TPF之间通过对话的方式进行通信， 并且不同对话之间采用对话号进行标识， 即当承载建立时， TPF向 CRF 请求计费规则， CRF向 TPF提供计费规则， 此时 TPF和 CRF之间建立 对话， 并通过对话号标识 TPF和 CRF之间建立的对话。 在后续承载修 改、 承载删除的过程中， TPF需要向 CRF重新请求计费规则时， TPF通 过对话号标识当前计费规则请求与先前建立的对话之间的对应关系； 同 样地， 在 CRF收到 AF或 OCS提供的用于确定计费规则的输入信息， 需要主动向 TPF提供计费规则时， CRF也需要通过对话号标识当前提供 ' 的计费规则与先前建立的对话之间的对应关系。
在两个实体间建立对话的意义在于在两个实体间建立状态机，这样， 两个实体在进行后续交互时可直接使用状态机中的数据， 而无需在每次 交互时都提供相关信息。 例如， 承载建立时， TPF需向 CRF提供用户信 息、 承载属性、 网络信息等相关信息， TPF与 CRF之间建立对话后， TPF和 CRF均会存储这些相关信息，在 TPF与 CRF后续的交互过程中， 如承载修改、 承载删除时， TPF向 CRF请求计费规则， 或 OCS、 AF向 CRF提供确定计费规则的输入信息， CRF主动向 TPF发送计费规则等 过程， 发送方无需再向接收方提供这些相关信息， 而是仅仅提供对话号 标识出相应的对话即可。
虽然规范中定义了在 CRF和 TPF之间通过对话的方式进行通信， 但规范中并未指出对话的建立方式， 导致了现有流程在实现上的不确定 性， 造成了 TPF和 CRF之间交互的消息无法互通。 发明内容
有鉴于此， 本发明的目的在于提供一种基于分组数据流计费的对话 建立方法， 明确 TPF与 CRF之间的对话建立过程及建立方式。
为了达到上述目的， 本发明提供了一种基于分组数据流计费的对话 建立方法， 该方法包含步骤 Al : TPF与 CRF之间建立针对于每用户的 每个承载的对话。
TPF分配对话号时，所述步驟 A1为：承载建立时， TPF建立 TPF/CRF 对话状态模型， 为当前对话分配对话号， 然后向 CRF提供该对话号， CRF根据收到的对话号建立 TPF/CRF对话状态模型。
CRF分配对话号时，所述步骤 A1为：承载建立时， CRF建立 TPF/CRF 对话状态模型，为当前对话分配对话号，然后向 TPF提供该对话号， TPF 根据收到的对话号建立 TPF/CRF对话状态模型。
所述步骤 A1之前进一步包括： CRF判断是否收到来自 TPF的承载 建立指示， 如果是， 则执行步骤 Al。
TPF和 CRF共同分配对话号时，所述步骤 A1为：承载建立时， TPF 建立 TPF/CRF对话状态模型， 为当前对话分配 TPF部分对话号， 并向 CRF提供该 TPF部分对话号， CRF建立 TPF/CRF对话状态模型， 为当 前对话分配 CRF部分对话号， 将 TPF部分对话号与 CR 部分对话号构 成 TPF/CRF对话的完整对话号。
所述步骤 A1之后进一步包括： CRF向 TPF提供完整对话号， TPF 根据完整对话号中的 TPF部分对话号索引至先前建立的 TPF/CRF对话 状态模型， 并将 TPF对话号更新为完整对话号。
本发明还提供了一种基于分组数据流计费的对话建立方法， 该方法 包含步骤 A2: TPF与 CRJF之间建立针对于每用户具有相同 APN的承载 的对话。
TPF分配对话号， 承载建立时， 所述 A2之前进一步包括： TPF根 据用户标识信息和 APN信息， 判断是否已经与 CRF建立了针对于所述 用户的所述 APN的对话， 如果没有， 则执行步骤 A2。
所述步骤 A2为： TPF建立 TPF/CRF对话状态模型， 为当前对话分 配对话号， 然后向 CRF 提供该对话号， CRJF根据收到的对话号建立 TPF/CRF对话状态模型。
CRF分配对话号， 承载建立时， 所述 A2之前进一步包括： CRF判 断是否收到承载建立指示， 如果是， CRF根据 TPF地址信息、 用户标识 信息和 APN信息， 判断是否已经与 TPF建立了针对于所述用户的所述 APN的对话， 如果没有建立， 则执行步骤 A2。
所述步骤 A2为： CRF建立 TPF/CRF对话状态模型， 为当前对话分 配对话号， 然后向 TPF 提供该对话号， TPF根据收到的对话号建立 TPF/CRF对话状态模型。
所述承载建立指示、 TPF地址信息、用户标识信息和 APN信息来自 于 TPF。
TPF和 CRF共同分配对话号， 承载建立时， 所述 A2之前进一步包 括： TPF根据用户标识信息和 APN信息， 判断是否已经与 CRF建立了 针对于所述用户的所述 APN的对话， 如果没有， 则执行步骤 A2。
所述步骤 A2为： TPF建立 TPF/CRF对话状态模型， 为当前对话分 配 TPF部分对话号， 并向 CRF提供该 TPF部分对话号， CRF 建立 TPF/CRF对话状态模型， 为当前对话分配 CRF部分对话号， 将 TPF部 所述步骤 A2之后进一步包括： CRF向 TPF提供完整对话号，' TPF 根据完整对话号中的 TPF部分对话号索引至先前建立的 TPF/CRF对话 状态模型， 并将 TPF对话号更新为完整对话号。
该方法进一步包含： TPF为每个新建立的承载分配承载标识， 并向 CRF提供该承载标识。
本发明还提供了一种基于分组数据流计费的对话建立方法， 该方法 包含步骤 A3: TPF与 CRF之间建立针对于每用户所有的承载的对话。
TPF分配对话号， 承载建立时， 所述 A3之前进一步包括： TPF根 据用户标识信息判断是否已经与 CRF建立了针对于所述用户的对话，如 果没有， 则执行步骤 A3。
所述步骤 A3为： TPF建立 TPF/CRF对话状态模型， 为当前对话分 配对话号， 然后向 CRF 提供该对话号， CRF根据收到的对话号建立 TPF/CRF对话状态模型。
CRF分配对话号， 承载建立时， 所述 A3之前进一步包括： CRF判 断是否收到承载建立指示，如果是， CRF根据 TPF地址信息和用户标识 信息， 判断是否已经与 TPF建立了针对于所述用户的对话， 如果没有建 立， 则执行步骤 A3。
所述步骤 A3为： CRF建立 TPF/CRF对话状态模型， 为当前对话分 配对话号， 然后向 TPF提供该对话号， TPF 根据收到的对话号建立 TPF/CRF对话状态模型。 所述承载建立指示、 TPF地址信息和用户标识信息来自于 TPF。
TPF和 CRF共同分配对话号， 承载建立时， 所述 A3之前进一步包 括： TPF根据用户标识信息判断是否已经与 CRF建立了针对于所述用户 的对话， 如果没有， 则执行步骤 A3。
所述步骤 A3为： TPF建立 TPF/CRF对话状态模型， 为当前对话分 配 TPF部分对话号， 并向 CRF提供该 TPF部分对话号， CR 建立 TPF/CRF对话状态模型， 为当前对话分配 CRF部分对话号， 将 TPF部 分对话号与 CRF部分对话号构成 TPF/CRF对话的完整对话号。
所述步骤 A3之后进一步包括： CRF向 TPF提供完整对话号， TPF 根据完整对话号中的 TPF部分对话号索引至先前建立的 TPF/CRF对话 状态模型， 并将 TPF对话号更新为完整对话号。
该方法进一步包含： TPF为每个新建立的承载分配承载标识， 并向 CRF提供该承载标识。
本发明中提供了多种 TPF与 CRF建立对话的方式， 如 TPF与 CRF 之间的对话可针对于每个用户的每个承载建立； 又如 TPF与 CRF之间 的对话可针对于每个用户的具有相同 APN的承载建立；再如 TPF与 CRP 之间的对话可针对于每个用户的所有承载建立， 完善了 TPF与 CRF之 间对话的建立机制， 使得整个计费流程的实现更为完整。 并且， 本发明 中提供了多种 TPF与 CRF之间对话的建立方式， 可根据实际计费情况 进行灵活选择。 附图简要说明
图 1示出了 PDP Context激活、 数据传输、 去激活流程图； 图 2A示出了支持在线计费的 FBC系统结构图；
图 2B示出了支持离线计费的 FBC系统结构图； 图 3示出了针对于每个承载建立 TPF/CRF对话且由 TPF分配对话 号的对话建立过程示意图；
图 4示出了针对于每个承载建立 TPF/CRF对话且由 CRF分配对话 号的对话建立过程示意图；
图 5示出了针对于每个承载建立 TPF/CRF对话且由 TPF和 CRF共 同分配对话号的对话建立过程示意图；
图 6示出了针对于每个用户的每个承载建立 TPF/CRF对话的示意 图；
图 7示出了针对于每个用户的具有相同 APN的承载建立 TPF/CRF 对话且由 TPF分配对话号的对话建立过程示意图；
图 8示出了针对于每个用户的具有相同 APN的承载建立 TPF/CRF 对话且由 CRF分配对话号的对话建立过程示意图；
图 9示出了针对于每个用户的具有相同 APN的承载建立 TPF/CRF 对话且由 TPF和 CRF共同分配对话号的对话建立过程示意图；
图 10示出了针对于每个用户的具有相同 APN的承载建立 TPF/CRF 对话的示意图；
图 11 示出了针对于每个用户的所有承载建立 TPF/CRF 对话且由 TPF分配对话号的对话建立过程示意图；
图 12 示出了针对于每个用户的所有承载建立 TPF/CRF对话且由 CRF分配对话号的对话建立过程示意图；
图 13 示出了针对于每个用户的所有承载建立 TPF/CRF对话且由 TPF和 CRF共同分配对话号的对话建立过程示意图；
图 14示出了针对于每个用户的所有承载建立 TPF/CRF对话的示意 图。 实施本发明的方式
为使本发明的目的、 技术方案和优点更加清楚， 下面结合附图对本 发明作进一步的详细描述。
本发明中提供了多种 TPF与 CRF建立对话的方式， 如 TPF与 CRF 之间的对话可针对于每个用户的每个承载建立， 对于 GPRS, 即为针对 于每个用户的每个 PDP Context的状态模型建立一个 TPF与 CRF之间的 对话； 又如 TPF与 CRJF之间的对话可针对于每个用户的具有相同 APN 的承载建立一个 TPF与 CRF之间的对话，对于 GPRS， 即为针对于每个 用户的所有具有相同 APN的承载建立一个 TPF与 CRF之间的对话； 再 如 TPF 与 CRF之间的对话可针对于每个用户的所有承载建立， 对于 GPRS , 即为针对于每个用户的 GPRS 承载激活 （Activate ) /去激活 ( Deactivate ) 状态模型建立一个 TPF 与 CRF 之间的对话。 建立了 TPF/CRF对话后， TPF与 CRF进行信息交互， 如 CRF向 TPF提供计费 规则， TPF根据 CRF提供的计费规则， 对过滤出的 IP数据流进行计费。
针对于每个用户的每个承载建立 TPF与 CRF之间的对话， 即在每 个承载建立时， 均建立 TPF与 CRF之间新的对话， 每个 TPF/CRF对话 状态模型对应于单个的承载建立状态模型， 承载建立时， 建立 TPF/CRF 对话，承载终止时，释放 TPF/CRF对话。对于 GPRS,则是每个 TPF/CRF 对话状态模型对应于单个的 PDP Context状态模型。 在 GGSN中， 每个 激活的 GPRS PDP Context至多有一个 PDP Context状态模型。
针对具体的对话建立过程， 如果对话号由 TPF分配， 则在每个承载 建立 TPF均建立新的 TPF/CRF对话状态模型， 为对话分配新的对话 号， 并存储相应的信息， 如对话号、 用户信息、 承载属性、 网络信息等， 然后向 CRF提供分配的对话号， 该对话号可携带在 TPF向 CRF发送的 计费规则请求中， CRF接收到携带有新的对话号计费规则请求后， 建立 新的 TPF/CRF对话状态模型， 存储相应的信息， 如对话号、 用户信息、 承载属性、网络信息等；如果对话号由 CRF分配，则在每个承载建立时， TPF均向 CRF发送计费规则请求， 并携带相应的承载建立指示， 用以标 识该计费规则请求是基于承载建立发起的， CRF根据承载建立指示建立 新的 TPF/CRF对话状态模型， 为对话分配新的对话号， 并存储相应的信 息， 如对话号、 用户信息、 承载属性、 网络信息等， 然后向 TPF提供分 配的对话号， 该对话号可携带在 CRF向 TPF返回计费规则的消息中， TPF接收到携带有新的对话号计费规则响应后，建立新的 TPF/CRF对话 状态模型， 存储相应的信息， 如对话号、 用户信息、 承载属性、 网络信 息等； 如果对话号由 TPF和 CRF共同分配， 则在每个承载建立时， TPF 均建立新的 TPF/CR 对话状态模型， 为对话分配新的 TPF部分对话号， 存储相应的信息， 如 TPF部分对话号、 用户信息、 承载属性、 网络信息 等， 并向 CRF提供分配的 TPF部分对话号， 该 TPF部分对话号可携带 在 TPF向 CRF发送的计费规则请求中， CRF接收到携带有 TPF部分对 话号的计费规则请求后， 建立新的 TPF/CRF对话状态模型， 分配 CRF 部分对话号，与 TPF提供的 TPF部分对话号构成完整的对话号，并存储 相应的信息， 如完整对话号、 用户信息、 承载属性、 网络信息等， 然后 CRF向 TPF提供该完整对话号， 该完整对话号可携带在 CRF向 TPF返 回计费规则的消息中， TPF接收到携带有完整对话号的计费规则响应后， 根据完整对话号中的 TPF部分对话号， 索引到先前建立的 TPF/CRF对 话状态模型， 对存储的信息进行更新， 如将 TPF部分对话号更新为完整 对话号。
建立了 TPF/CRF对话后， TPF与 CRF进行信息交互，如 CRJF向 TPF 提供计费规则， TPF根据 CRF提供的计费规则， 对过滤出的 IP数据流 进行计费。 图 3示出了针对于每个承载建立 TPF/CRF对话且由 TPF分配对话 号的对话建立过程示意图， 如图 3所示， 针对于每个承载建立 TPF/CRF 对话， 并且由 TPF分配对话号的对话建立过程包括以下步骤：
步驟 301：用户设备（ UE )向 TPF发送承载建立请求（ Establish Bearer Service Request ),在 GPRS网络中，则是 GGSN收到 Create PDP Context Request
步骤 302: TPF收到承载建立请求后，建立 TPF/CRF对话状态模型， 为当前对话分配对话号， 并存储相应的信息， 如对话号、 用户信息、 承 载属性、 网络信息等， 然后向 CR 发送计费规则请求（Request Charging Rules ),该计费规则请求中携带有供 CRF确定计费规则的输入信息和分 配的对话号。
步骤 303: CRF收到计费规则请求后， 根据计费规则请求中携带的 新的对话号，建立 TPF/CRF对话状态模型，存储相应的信息，如对话号、 用户信息、承载属性、 网络信息等， 然后 CRF根据该计费规则请求中携 带的输入信息， 还可根据 AF提供的相关输入信息， 如果为在线计费方 式， 也可根据 OCS提供的相关输入信息， 选择适当的计费规则。
步驟 304: CRF选择了适当的计费规则后， 向 TPF返回提供计费规 则 （ Provision Charging Rules ), 作为计费规则请求的响应， 该提供计费 规则中可携带有选定的计费规则、 计费规则操作指示和 TPF在步骤 302 中分配的对话号， 通过该对话号标识当前计费规则响应与先前计费规则 请求之间的对应关系。
步骤 305: TPF收到提供计费规则后， 根据对话号索引到相应的对 话，并根据计费规则操作指示对 CRP选定的计费规则进行相应操作，如 果为在线计费方式， 则继续执行步驟 306~步骤 308, 如果为离线计费方 式， 则直接执行步骤 308。 步骤 306: TPF根据计费规则中的在线计费指示， 向 OCS发送信用 请求（ Credit Request )， 向 OCS请求用户的信用信息。
步骤 307: OCS收到信用请求后， 确定用户的信用， 然后向 TPF返 回信用响应 （Credit Response ), 如果 OCS确定出用户的信用， 则该信 用响应中携带有用户的信用； 如果 OCS未确定出用户的信用，则该信用 响应中可携带有差错原因值。
步骤 308: TPF向 UE返回承载建立响应 （Establish Bearer Service Accept ), 如果 TPF能够根据已有信息建立承载， 如 OCS返回了用户的 信用， 则该承载建立响应为承载建立成功响应， TPF接受 UE发起的承 载建立请求， 并继续后续的 载建立流程； 如果 TPF无法 居已有信息 建立承载，如 OCS未返回用户的信用，则该承载建立响应为承载建立失 败响应， TPF拒绝 UE发起的承载建立请求。
图 4示出了针对于每个 载建立 TPF/CRF对话且由 CRF分配对话 号的对话建立过程示意图， 如图 4所示， 针对于每个承载建立 TPF/CRF 对话， 并且由 CRF分配对话号的对话建立过程包括以下步骤：
步骤 401与步骤 301相同。
步骤 402: TPF收到承载建立请求后， 向 CRF发送计费规则请求， 该计费规则请求中携带有供 CRF确定计费规则的输入信息，并可进一步 携带承载建立指示， 用以标识该计费规则请求是基于承载建立发起的。
步骤 403: CRF收到计费规则请求后， 根据计费规则请求中携带的 承载建立指示，建立 TPF/CRF对话状态模型，为当前对话分配新的对话 号， 并存储相应的信息， 如对话号、 用户信息、 承载属性、 网络信息等， 然后 CRF根据该计费规则请求中携带的输入信息，还可根据 AF提供的 相关输入信息，如果为在线计费方式，也可根据 OCS提供的相关输入信 息， 选择适当的计费规则。 步骤 404: CRF选择了适当的计费规则后， 向 TPF返回提供计费规 则， 该提供计费规则中可携带有选定的计费规则、 计费规则操作指示和 分配的对话号。
步骤 405: TPF收到提供计费规则后， 根据提供计费规则消息中携 带的新的对话号， 建立新的 TPF/CRF对话状态模型， 存储相应的信息， 如对话号、 用户信息、 承载属性、 网络信息等， 并根据计费规则操作指 示对 CRF选定的计费规则进行相应操作，如果为在线计费方式， 则继续 执行步骤 406〜步骤 408, 如果为离线计费方式， 则直接执行步骤 408。
步驟 406〜步骤 407与步骤 306〜步骤 307相同。
步骤 408与步骤 308相同。
图 5示出了针对于每个承载建立 TPF/CRF对话且由 TPF和 CRF共 同分配对话号的对话建立过程示意图， 如图 5所示， 针对于每个承载建 立 TPF/CRF对话， 并且由 TPF和 CRF共同分配对话号的对话建立过程 包括以下步骤：
步驟 501与步驟 301相同。
步骤 502: TPF收到承载建立请求后，建立 TPF/CRF对话状态模型， 为当前对话分配 TPF部分对话号，并存储相应的信息，如 TPF部分对话 号、用户信息、承载属性、 网络信息等，然后向 CRF发送计费规则请求， 该计费规则请求中携带有供 CRF 确定计费规则的输入信息和分配的 TPF部分对话号。
步骤 503: CRF收到计费规则请求后， 根据计费规则请求中携带的 不完整的对话号， 即 TPF部分对话号， 建立 TPF/CRF对话状态模型， 分配 CRF部分对话号， 并存储相应的信息， 如完整对话号 （由在步骤 502中接收到的 TPF部分对话号和当前分配的 CRF部分对话号构成）、 用户信息、承载属性、 网络信息等， 然后 CRF根据该计费规则请求中携 01237 带的输入信息， 还可根据 AF提供的相关输入信息， 如果为在线计费方 式， 也可根据 OCS提供的相关输入信息， 选择适当的计費规则。
步骤 504: CRF选择了适当的计费规则后， 向 TPF返回提供计费规 则， 作为计费规则请求的响应， 该提供计费规则中可携带有选定的计费 规则、 计费规则操作指示和 TPF与 CRF共同分配的完整对话号。
步骤 505: TPF接收到携带有完整对话号的提供计费规则后， 根据 完整对话号中的 TPF部分对话号， 索引到先前建立的 TPF/CRF对话状 态模型， 对存储的信息进行更新， 如将 TPF部分对话号更新为完整对话 号， 然后 TPF根据计费规则操作指示对 CRF选定的计费规则进行相应 操作， 如果为在线计费方式， 则继续执行步骤 506〜步骤 508, 如果为离 线计费方式， 则直接执行步骤 508。
步骤 506〜步骤 507与步骤 306〜步骤 307相同。
步骤 508与步骤 308相同。
针对于每个用户的每个承载建立 TPF/CRF对话时， 每个 TPF/CRF 对话中的操作（如提供、 修改、 删除计费规则， 或提供触发事件（Event trigger )等）是相互独立的， 即这些操作是针对每个用户的每个承载的， CRF可通过 TPF/CRF对话状态模型对每个用户承载进行相应的 FBC控 制。
图 6示出了针对于每个用户的每个承载建立 TPF/CRF对话的示意 图， 如图 6所示， 对于 TPF的同一个用户而言， TPF中每个承载状态模 型 （Established Bearer State Model )对应于一个 TPF/CRF对话状态模型 ( TPF/CRF Instance State Model ),即 TPF/CRF对话状态模型在建立承载 状态模型时建立， 对于 GPRS， 则为收到 Create PDP context request时建 立；在释放承载状态模型时释放，对于 GPRS ,则为收到相应的 Delete PDP context request 时释放。 1237 另外，还可针对于每个用户的具有相同 ΑΡΝ的承载建立 TPF与 CRF 之间的对话， 即针对每个用户建立一个新的 ΑΡΝ的 IP数据流承载时， 建立新的 TPF与 CRF之间的对话， 对于后续同一用户建立的相同 APN 的新承载，则直接基于先前建立的对话对该承载进行 FBC控制，无需建 立新的对话。 一个用户可同时建立多个具有相同 APN 的承载， 对于 GRPS, 即为一个用户可同时建立多个具有相同 APN的 PDP Context。 当一个用户建立新的承载时， 分配对话号的实体判断是否已经建立了针 对于该用户的该 APN的 CRP/TPF对话状态模型， 如果是， 则使用先前 分配的针对于该用户的该 APN的对话号标识当前建立的承载与先前建 立的 TPF/CRF对话的关系， 否则， 建立新的 TPF/CRF对话状态模型， 并分配新的对话号。
针对具体的对话建立过程， 如果对话号由 TPF分配， 则当用户建立 新的承载时， TPF根据用户标识和 APN信息， 判断是否已经建立了针 对于该用户的该 APN的 TPF/CRF对话状态模型， 如果是， 则 TPF直接 使用先前建立的针对于该用户的该 APN的 TPF/CR 对话状态模型中的 对话号标识当前建立的承载与先前建立的 TPF/CRF对话的关系， 否则 , TPF建立针对于该用户的该 APN的 TPF/CRF对话状态模型， 为对话分 配新的对话号， 并存储相应的信息， 如对话号、 用户信息、 承载属性、 网络信息等， 然后向 CRF提供分配的对话号， 该对话号可携带在 TPF 向 CRF发送的计费规则请求中， CRF接收到携带有新的对话号计费规 则请求后， 建立新的 TPF/CRF对话状态模型， 存储相应的信息， 如对话 号、 用户信息、 承载属性、 网络信息等。
如果对话号由 CRF分配， 则当用户建立新的承载时， TPF向 CRF 发送计费规则请求， 并携带相应的承载建立指示， 用以标识该计费规则 请求是基于承载建立发起的， 进一步的 TPF可向 CRF提供用户标识、 APN信息和 TPF地址信息 , CRF根据 TPF提供的承载建立指示、 用户 标识、 APN信息和 TPF地址信息， 判断是否已经针对该用户的该 APN 与相应 TPF建立了 TPF/CRF对话状态模型， 如果是， 则 CRF直接使用 先前建立的针对于该用户的该 APN的 TPF/CRF对话状态模型中的对话 号标识当前建立的承载与先前建立的 TPF/CRF对话的关系， 否则， CRJF 建立针对于该用户的该 APN的 TPF/CRF对话状态模型， 为对话分配新 的对话号， 并存储相应的信息， 如对话号、 用户信息、 承载属性、 网络 信息等，然后向 TPF提供分配的对话号，该对话号可携带在 CRF向 TPF 返回计费规则的消息中， TPF接收到携带有新的对话号计费规则响应后， 建立新的 TPF/CRF对话状态模型， 存储相应的信息， 如对话号、 用户信 息、 承载属性、 网络信息等。
如果对话号由 TPF和 CRF共同分配， 则当用户建立新的承载时， TPF根据用户标识和 APN信息， 判断是否已经与 CRF建立了针对于该 用户的该 APN的 TPF/CRF对话状态模型， 如果是， 则 TPF直接使用先 前建立的针对于该用户的该 APN的 TPF/CRF对话状态模型中的对话号 标识当前建立的承载与先前建立的 TPF/CRF对话的关系， 否则， TPF 建立针对于该用户的该 APN的 TPF/CR 对话状态模型， 分配新的 TPF 部分对话号， 并存储相应的信息， 如 TPF部分对话号、 用户信息、 承载 属性、 网络信息等， 并向 CRF提供分配的 TPF部分对话号， 该 TPF部 分对话号可携带在 TPF向 CRF发送的计费规则请求中， CRF接收到携 带有 TPF部分对话号的计费规则请求后， 建立新的 TPF/CRF对话状态 模型 , 分配 CRF部分对话号， 然后与 TPF提供的 TPF部分对话号构成 完整的对话号， 并存储相应的信息， 如完整对话号、 用户信息、 承载属 性、 网络信息等， 然后 CRF向 TPF提供该完整对话号， 该完整对话号 可携带在 CRF向 TPF返回计费规则的消息中， TPF接收到携带有完整 对话号的计费规则响应后， 根据完整对话号中的 TPF部分对话号， 索引 到先前建立的 TPF/CRF对话状态模型， 对存储的信息进行更新， 如将 TPF部分对话号更新为完整对话号。
建立了 TPF/CRF对话后， TPF与 CRF进行信息交互，如 CRF向 TPF 提供计费规则， TPF根据 CRF提供的计费规则， 对过滤出的 IP数据流 进行计费。
图 7示出了针对于每个用户的具有相同 APN的承载建立 TPF/CRF 对话且由 TPF分配对话号的对话建立过程示意图， 如图 7所示， 针对于 每个用户的具有相同 APN的承载建立 TPF/CRF对话， 并且由 TPF分配 对话号的对话建立过程包括以下步骤：
步骤 701与步骤 301相同。
步骤 702: TPF收到承载建立请求后， 根据用户标识信息和 APN信 息， 判断是否已经与 CRF建立了针对于该用户的该 APN的对话， 如果 是，则直接向 CRF发送计费规则请求，该计费规则请求中携带有供 CRF 确定计费规则的输入信息和先前分配的对话号， 通过该先前分配的对话 号标识当前对话中的计费规则请求与先前建立的 TPF/CRP对话的关系； 否则， TPF建立 TPF/CRF对话状态模型， 分配新的对话号， 并存储相应 的信息， 如对话号、 用户信息、 承载属性、 网络信息等， 然后向 CRF 发送计费规则请求，该计费规则请求中携带有供 CRF确定计费规则的输 入信息和当前分配的对话号。
步驟 703与步骤 303相同。
步骤 704与步骤 304相同。
步骤 705与步驟 305相同。
步骤 706〜步骤 707与步骤 306〜步骤 307相同。
步骤 708与步骤 608相同。 图 8示出了针对于每个用户的具有相同 APN的承载建立 TPF/CRF 对话且由 CRF分配对话号的对话建立过程示意图，如图 8所示，针对于 每个用户的具有相同 APN的承载建立 TPF/CRF对话，并且由 CR 分配 对话号的对话建立过程包括以下步骤：
步骤 801与步骤 401相同。
步骤 802: TPF收到承载建立请求后， 向 CRF发送计费规则请求， 该计费规则请求中携带有供 CRF确定计费规则的输入信息，并进一步携 带有承载建立指示， 用以标识该计费规则请求是基于承载建立发起的 , 以及用户标识信息、 APN信息和 TPF地址信息。
步骤 803: CRF收到计费规则请求后， 根据计费规则请求中携带的 承载建立指示、 用户标识信息、 APN信息和 TPF地址信息， 判断是否 已经与相应 TPF建立了针对于该用户的该 APN的对话， 如果是， 则直 接向 TPF返回提供计费规则， 该提供计费规则中携带有选定的计费规 则、 计费规则操作指示和先前分配的对话号， 通过该先前分配的对话号 标识当前对话中的提供计费规则消息与先前建立的 TPF/CR 对话的关 系； 否则， CRF建立 TPF/CRF对话状态模型， 为当前对话分配新的对 话号， 并存储相应的信息， 如对话号、 用户信息、 承载属性、 网络信息 等， 然后 CRF根据该计费规则请求中携带的输入信息， 还可根据 AF提 供的相关输入信息，如果为在线计费方式，也可根据 OCS提供的相关输 入信息， 选择适当的计费规则。
步驟 804与步骤 404相同。
步骤 805与步骤 405相同。
步骤 806〜步骤 807与步骤 406〜步骤 407相同。
步驟 808与步骤 408相同。
图 9示出了针对于每个用户的具有相同 APN的承载建立 TPF/CRF 对话且由 TPF和 CRF共同分配对话号的对话建立过程示意图， 如图 9 所示， 针对于每个用户的具有相同 APN的承载建立 TPF/CR 对话， 并 且由 TPF和 CRF共同分配对话号的对话建立过程包括以下步骤：
步骤 901与步骤 501相同。
步骤 902: TPF收到承载建立请求后， 根据用户标识信息和 APN信 息， 判断是否已经与 CRF建立了针对于该用户的该 APN的对话， 如果 是，则直接向 CRF发送计费规则请求，该计费规则请求中携带有供 CR 确定计费规则的输入信息和先前分配的对话号， 通过该先前分配的对话 号标识当前对话中的计费规则请求与先前建立的 TPF/CRF对话的关系； 否则， TPF建立 TPF/CRF对话状态模型， 为当前对话分配新的 TPF部 分对话号， 并存储相应的信息， 如 TPF部分对话号、 用户信息、 承载属 性、 网络信息等， 然后向 CRF发送计费规则请求， 该计费规则请求中携 带有供 CRF确定计费规则的输入信息和当前分配的 TPF部分对话号。
步骤 903与步骤 503相同。
步骤 904与步驟 504相同。
步驟 905与步骤 505相同。
步骤 906〜步骤 907与步骤 506〜步骤 507相同。
步驟 908与步骤 508相同。
TPF和 CRF之间针对于每个用户的具有相同 APN的承载建立对话 时， 每个 TPF/CRF对话中的操作（如提供、 修改、 删除计费规则， 或提 供触发事件等）是针对同一用户的具有相同 APN的所有承载， CRF可 以通过对话状态模型对用户具有相同 APN的承载进行统一的 FBC控制。
图 10示出了针对于每个用户的具有相同 APN的承载建立 TPF/CRP 对话的示意图， 如图 10 所示， 对于在 TPF 的同一个用户而言， 每个 TPF/CRF对话状态模型总是至少包含一个或多个承载建立状态模型 , 并 且这些建立的多个承载具有相同的 APN。 对于 GPRS, 即为 TPF/CRF 对话状态模型由至少一个或多个 GPRS PDP Context状态模型 （GPRS PDP context State Models )组成， 并且当 TPF/CRF对话状态模型由多个 GPRS PDP Context状态模型组成时， 这些多个 GPRS PDP Context状态 模型中的承载都具有相同的 APN。
另外， 为了使 CRF对用户的每个承载也能够进行 FBC控制， 可以 要求 TPF在每个承载建立时，为该承载分配相应的承载标识（ Bearer ID ), 并对于该承载 TPF第一次向 CRF请求计费规则时携带分配的承载标识， 或是对于该承载 TPF第一次向 CRF上报触发事件报告时携带承载标识。 TPF分配的承载标识需要保证对于同一个用户相同 APN下的承载标识 是唯一的， 该用户相同 APN 下的不同承载的承载标识不会重复。 CRF 可根据和 TPF/CRF对话状态模型和承载标识对同一用户的不同承载进 行不同的 FBC控制。
此外， 还可针对于每个用户的所有承载建立 TPF与 CRF之间的对 话， 即针对每个用户在 TPF 中建立的第一个承载， 建立新的 TPF/CRF 对话， 无需针对用户后续在 TPF中建立的新承载建立新的对话。 当一个 用户在 TPF中建立新的承载时，分配对话号的实体判断是否已经建立了 针对该 TPF中针对于该用户所有承载的 TPF/CRF对话， 如果是， 则直 接使用先前分配的针对于该用户所有承载的对话号标识当前建立的承 载与先前建立的 TPF/CRF对话的关系， 否则，建立针对于该用户所有承 载的 TPF/CRF对话状态模型， 并分配新的对话号。
针对具体的对话建立过程， 如果对话号由 TPF分配， 则当用户建立 新的承载时， TPF根据用户标识信息， 判断是否已经建立了针对于该用 户的所有承载的 TPF/CRF对话状态模型， 如果是， 则 TPF直接使用先 前建立的针对于该用户的所有承载的 TPF/CRF对话状态模型中的对话 号标识当前建立的承载与先前建立的 TPF/CRF对话的关系， 否则， 即 TPF判断出该承载建立是用户在 TPF中建立的第一个承载，则建立针对 于该用户所有承载的 TPF/CRF对话状态模型，分配新的对话号，并存储 相应的信息，如对话号、用户信息、承载属性、 网络信息等，然后向 CRF 提供分配的对话号， 该对话号可携带在 TPF向 CRF发送的计费规则请 求中， CRF 接收到携带有新的对话号计费规则请求后， 建立新的 TPF/CRF对话状态模型， 存储相应的信息， 如对话号、 用户信息、 承载 属性、 网络信息等。
如果对话号由 CRF分配， 则当用户建立新的承载时， TPF向 CRF 发送计费规则请求， 并携带相应的承载建立指示， 用以标识该计费规则 请求是基于承载建立发起的， 进一步的 TPF可向 CRF提供用户标识和 TPF地址信息， CRF根据 TPF提供的承载建立指示、 TPF地址信息和用 户标识信息，判断是否已经与相应 TPF建立了针对该用户的所有承载的 TPF/CRF对话状态模型， 如果是， 则 CRF直接使用先前建立的针对于 该用户的所有承载的 TPF/CRF对话状态模型中的对话号标识当前建立 的承载与先前建立的 TPF/CRF对话的关系， 否则， 即 CRF判断出该承 载建立是用户在相应 TPF中建立的第一个承载，则建立针对于该用户所 有承载的 TPF/CRF对话状态模型 ,分配新的对话号，并存储相应的信息， 如对话号、 用户信息、 承载属性、 网络信息等， 然后向 TPF提供分配的 对话号， 该对话号可携带在 CRF向 TPF返回计费规则的消息中， TPF 接收到携带有新的对话号计费规则响应后，建立新的 TPF/CRF对话状态 模型， 存储相应的信息， 如对话号、 用户信息、 承载属性、 网络信息等。
如果对话号由 TPF和 CRF共同分配， 则当用户建立新的承载时， TPF根据用户标识信息， 判断是否已经建立了针对于该用户的所有承载 的 TPF/CRF对话状态模型， 如果是， 则 TPF直接使用先前建立的针对 于该用户 TPF/CRF对话状态模型中的对话号标识当前建立的承载与先 前建立的 TPF/CRF对话的关系， 否则， 即 TPF判断出该承载建立是用 户在 TPF 中建立的第一个承载， 则建立针对于该用户所有承载的 TPF/CRF对话状态模型，分配新的 TPF部分对话号，并存储相应的信息， 如 TPF部分对话号、 用户信息、 承载属性、 网络信息等， 并向 CRF提 供分配的 TPF部分对话号， 该 TPF部分对话号可携带在 TPF向 CRF发 送的计费规则请求中， CRF接收到携带有 TPF部分对话号的计费规则请 求后，建立新的 TPF/CRF对话状态模型，分配 CRF部分对话号，与 TPF 提供的部分对话号构成完整的对话号， 并存储相应的信息， 如完整对话 号、 用户信息、 承载属性、 网络信息等， 然后 CRF向 TPF提供该完整 对话号， 该完整对话号可携带在 CRF向 TPF返回计费规则的消息中， TPF接收到携带有完整对话号的计费规则响应后， 根据完整对话号中的 TPF部分对话号， 索引到先前建立的 TPF/CRF对话状态模型，对存储的 信息进行更新， 如将 TPF部分对话号更新为完整对话号。
上述 TPF或 CRF判断是否已经建立了针对于同一用户所有承载的 TPF/CRF对话状态模型的方法可以是通过在 TPF或 CRF 中建立承载 Activate/Deactivate状态模型来进行。 TPF或 CRF在收到某一用户的第 一条承载建立请求时， 建立承载激活 Activate/去激活 Deactivate状态模 型， 在收到用户最后一条承载终止请求时释放承载 Activate/Deactivate 状态模型。 这样， 可以通过判断 TPF或 CRF中是否有针对该用户的承 载 Activate/Deactivate状态模型来判断是否已经建立了针对于该用户所 有承载的 TPF/CRF对话状态模型。
建立了 TPF/CRF对话后， TPF与 CRF进行信息交互，如 CRF向 TPF 提供计费规则， TPF根据 CRF提供的计费规则， 对过滤出的 IP数据流 进行计费。 图 11 示出了针对于每个用户的所有承载建立 TPF/CRJF对话且由 TPF分配对话号的对话建立过程示意图，如图 11所示，针对于每个用户 的所有承载建立 TPF/CRF对话， 并且由 TPF分配对话号的对话建立过 程包括以下步骤：
步骤 A1与步骤 301相同。
步骤 A2: TPF收到承载建立请求后，根据用户标识信息判断是否已 经与 CRF建立了针对于该用户所有承载的 TPF/CRF对话， 如果是， 则 直接向 CRF发送计费规则请求， 该计费规则请求中携带有供 CRF确定 计费规则的输入信息和先前分配的对话号， 通过该先前分配的对话号标 识当前对话中的计费规则请求与先前建立的 TPF/CR 的关系； 否则， TPF建立针对于该用户所有承载的 TPF/CRF对话状态模型，分配新的对 话号， 并存储相应的信息， 如对话号、 用户信息、 承载属性、 网络信息 等， 然后向 CRF发送计费规则请求， 该计费规则请求中携带有供 CRF 确定计费规则的输入信息和当前分配的对话号。
步骤 A3与步骤 303相同。
步骤 A4与步骤 304相同。
步骤 A5与步骤 305相同。
步驟 A6〜步骤 907与步骤 306〜步骤 307相同。
步驟 A8与步驟 308相同。
图 12 示出了针对于每个用户的所有承载建立 TPF/CRF对话且由 CKF分配对话号的对话建立过程示意图， 如图 12所示， 针对于每个用 户的所有承载建立 TPF/CRF对话， 并且由 CRF分配对话号的对话建立 过程包括以下步骤：
步骤 B1与步骤 401相同。
步骤 B2: TPF收到承载建立请求后， 向 CRF发送计费规则请求， 该计费规则请求中携带有供 CRF确定计费规则的输入信息，并进一步携 带有承载建立指示， 用以标识该计费规则请求是基于承载建立发起的， 以及用户标识信息和 TPF地址信息。
步骤 B3: CRF收到计费规则请求后，根据计费规则请求中携带的承 载建立指示、 用户标识信息和 TPF地址信息， 判断是否已经与相应 TPF 建立了针对于该用户所有承载的 TPF/CRF对话，如果是， 则直接向 TPF 返回提供计费规则， 该提供计费规则中携带有选定的计费规则、 计费规 则操作指示和先前分配的对话号， 通过该先前分配的对话号标识当前对 话中的提供计费规则消息与先前建立的 TPF/CRF对话的关系； 否则， CRF建立 TPF/CRF对话状态模型， 为当前对话分配新的对话号， 并存 储相应的信息，如对话号、用户信息、承载属性、 网络信息等，然后 CRF 根据该计费规则请求中携带的输入信息， 还可根据 AF提供的相关输入 信息， 如果为在线计费方式， 也可根据 OCS提供的相关输入信息， 选择 适当的计费规则。
步骤 B4与步骤 404相同。
步骤 B5与步骤 405相同。
步骤 B6〜步骤 A7与步骤 406〜步骤 407相同。
步骤 B8与步骤 408相同。
图 13 示出了针对于每个用户的所有承载建立 TPF/CRF对话且由 TPF和 CRF共同分配对话号的对话建立过程示意图， 如图 11所示， 针 对于每个用户的所有承载建立 TPF/CRF对话， 并且由 TPF和 CRF共同 分配对话号的对话建立过程包括以下步驟：
步骤 C1与步驟 501相同。
步骤 C2: TPF收到承载建立请求后，根据用户标识信息判断是否已 经建立了针对于该用户所有承载的对话，如果是， 则直接向 CRF发送计 费规则请求，该计费规则请求中携带有供 CRF确定计费规则的输入信息 和先前分配的对话号， 通过该先前分配的对话号标识当前对话中的计费 规则请求与先前建立的 TPF/CRF对话的关系；否则， TPF建立 TPF/CRF 对话状态模型， 为当前对话分配新的 TPF部分对话号， 并存储相应的信 息， 如 TPF部分对话号、 用户信息、 承载属性、 网络信息等， 然后向 CRF发送计费规则请求， 该计费规则请求中携带有供 CRF确定计费规 则的输入信息和当前分配的 TPF部分对话号。
步骤 C3与步骤 503相同。
步驟 C4与步骤 504相同。
步驟 C5与步骤 505相同。
步骤 C6〜步骤 C7与步骤 506〜步骤 507相同。
步驟 C8与步骤 508相同。
TPF和 CRF之间针对于每个用户的所有承载的建立对话时， 每个 TPF/CRF对话中的操作 （如提供、 修改、 删除计费规则， 或提供 Event trigger触发事件等）是与每个用户承载无关的， 即这些操作是针对一个 用户的所有承载的， CRF可以通过对话状态模型对用户所有的承载进行 统一的 FBC控制。 '
另外， 为了使 CRF对用户的每个承载也能够进行 FBC控制， 可以 要求 TPF在每个承载建立时， 为该承载分配相应的承载标识， 并对于该 承载 TPF第一次向 CRF请求计费规则时携带分配的承载标识， 或是对 于该承载 TPF第一次向 CRF上报触发事件报告时携带承载标识。 TPF 分配的承载标识需要保证对于同一个用户其承载标识是唯一的， 不会与 该用户的其他承载标识重复。 CRF可根据 TPF/CRF对话状态模型承载 标识对同一用户的不同承载进行不同的 FBC控制。
图 14示出了针对于每个用户的所有承载建立 TPF/CRF对话的示意 图， 如图 14所示， 对于在 TPF的同一个用户而言， 每个 TPF/CRF对话 状态模型总是至少包含一个承载激活 /去激活状态模型 （ Bearer Activate/Deactivate State Model ), 并且， TPF/CRF对话状态模型可进一 步包含多个与该承载激活 /去激活状态模型相关的承载建立状态模型。对 于 GPRS,即为 TPF/CRF对话状态模型由至少一个 GPRS激活 /去激活状 态模型（ GPRS Activate/Deactivate State Model )和可选的多个 GPRS PDP Context状态模型 （ GPRS PDP context State Models )组成。
总之， 以上所述仅为本发明的较佳实施例而已， 并非用于限定本发 明的保护范围。

Claims

权利要求书
1、 一种基于分组数据流计费的对话建立方法， 其特征在于， 该方法 包含：
Al、 TPF与 CRF之间建立针对于每用户的每个承载的对话。
2、 根据权利要求 1所述的方法， 其特征在于， TPF分配对话号时， 所述步骤 A1为： 承载建立时， TPF建立 TPF/CR 对话状态模型， 为当 前对话分配对话号， 然后向 CRF提供该对话号， CRF根据收到的对话 号建立 TPF/CRF对话状态模型。
3、 根据权利要求 1所述的方法， 其特征在于， CRF分配对话号时， 所述步驟 A1为： 承载建立时， CRF建立 TPF/CRP对话状态模型， 为当 前对话分配对话号， 然后向 TPF提供该对话号， TPF根据收到的对话号 建立 TPF/CRF对话状态模型。
4、 根据权利要求 3所述的方法， 其特征在于， 所述步驟 A1之前进 一步包括： CRF判断是否收到来自 TPF的承载建立指示， 如果是， 则执 行步骤 Al。
5、 根据权利要求 1所述的方法， 其特征在于， TPF和 CRF共同分 配对话号时， 所述步骤 A1为： 承载建立时， TPF建立 TPF/CRF对话状 态模型， 为当前对话分配 TPF部分对话号 , 并向 CRF提供该 TPF部分 对话号， CRF建立 TPF/CRF对话状态模型， 为当前对话分配 CRF部分 整对话号。
6、 根据权利要求 5所述的方法， 其特征在于， 所述步骤 A1之后进 一步包括： CRF向 TPF提供完整对话号， TPF根据完整对话号中的 TPF 部分对话号索引至先前建立的 TPF/CRF对话状态模型， 并将 TPF对话 号更新为完整对话号。
7、 一种基于分组数据流计费的对话建立方法， 其特征在于， 该方法 包含：
A2、 TPF与 CRF之间建立针对于每用户具有相同 APN的承载的对 话。
8、根据权利要求 7所述的方法， 其特征在于， TPF分配对话号， 承 载建立时， 所述 A2之前进一步包括： TPF根据用户标识信息和 APN信 息， 判断是否已经与 CRF建立了针对于所述用户的所述 APN的对话， 如果没有， 则执行步骤 A2。
9、根据权利要求 8所述的方法，其特征在于，所述步骤 A2为： TPF 建立 TPF/CRF对话状态模型， 为当前对话分配对话号， 然后向 CRF提 供该对话号， CRF根据收到的对话号建立 TPF/CRF对话状态模型。
10、 根据权利要求 7所述的方法， 其特征在于， CRF分配对话号， 承载建立时， 所述 A2之前进一步包括： CRF判断是否收到承载建立指 示， 如果是， CRF根据 TPF地址信息、 用户标识信息和 APN信息， 判 断是否已经与 TPF建立了针对于所述用户的所述 APN的对话， 如果没 有建立， 则执行步骤 A2。
11、 根据权利要求 10所述的方法， 其特征在于， 所述步驟 A2为： CRF建立 TPF/CRF对话状态模型，为当前对话分配对话号 ,然后向 TPF 提供该对话号， TPF根据收到的对话号建立 TPF/CRF对话状态模型。
12、根据权利要求 10所述的方法，其特征在于，所述承载建立指示、 TPF地址信息、 用户标识信息和 APN信息来自于 TPF。
13、 根据权利要求 7所述的方法， 其特征在于， TPF和 CRF共同分 配对话号， 承载建立时， 所述 A2之前进一步包括： TPF根据用户标识 信息和 APN信息， 判断是否已经与 CRF建立了针对于所述用户的所述 APN的对话， 如果没有， 则执行步驟 A2。
14、 根据权利要求 13所述的方法， 其特征在于， 所述步骤 A2为： TPF建立 TPF/CRF对话状态模型， 为当前对话分配 TPF部分对话号， 并向 CRF提供该 TPF部分对话号， CRF建立 TPF/CRF对话状态模型， 为当前对话分配 CRF部分对话号， 将 TPF部分对话号与 CRF部分对话 号构成 TPF/CRF对话的完整对话号。
15、 根据权利要求 14所述的方法， 其特征在于， 所述步骤 A2之后 进一步包括： CRF向 TPF提供完整对话号， TPF根据完整对话号中的 TPF部分对话号索引至先前建立的 TPF/CRF对话状态模型， 并将 TPF 对话号更新为完整对话号。
16、根据权利要求 7所述的方法， 其特征在于， 该方法进一步包含： TPF为每个新建立的承载分配承载标识， 并向 CRF提供该承载标识。
17、 一种基于分组数据流计费的对话建立方法， 其特征在于， 该方 法包含：
A3、 TPF与 CRF之间建立针对于每用户所有的承载的对话。
18、 根据权利要求 17所述的方法， 其特征在于， TPF分配对话号， 承载建立时， 所述 A3之前进一步包括： TPF 用户标识信息判断是 否已经与 CRF建立了针对于所述用户的对话， 如果没有， 则执行步骤 A3。
19、 根据权利要求 18所述的方法， 其特征在于， 所述步骤 A3为： TPF建立 TPF/CR 对话状态模型，为当前对话分配对话号，然后向 CRF 提供该对话号， CRF根据收到的对话号建立 TPF/CRF对话状态模型。
20、 根据权利要求 17所述的方法， 其特征在于， CRF分配对话号， 承载建立时， 所述 A3之前进一步包括： CRF判断是否收到承载建立指 示， 如果是， CRF根据 TPF地址信息和用户标识信息， 判断是否已经与 TPF建立了针对于所述用户的对话， 如果没有建立， 则执行步骤 A3。
21、 根据权利要求 20所述的方法， 其特征在于， 所述步骤 A3为： CRF建立 TPF/CRF对话状态模型，为当前对话分配对话号，然后向 TPF 提供该对话号， TPF根据收到的对话号建立 TPF/CRF对话状态模型。
22、根据权利要求 20所述的方法，其特征在于，所述承载建立指示、 TPF地址信息和用户标识信息来自于 TPF。
23、 根据权利要求 17所述的方法， 其特征在于， TPF和 CRF共同 分配对话号， 承载建立时， 所述 A3之前进一步包括： TPF才艮据用户标 识信息判断是否已经与 CRF建立了针对于所述用户的对话, 如果没有， 则执行步骤 A3。
24、 根据权利要求 23所述的方法， 其特征在于， 所述步骤 A3为： TPF建立 TPF/CRF对话状态模型， 为当前对话分配 TPF部分对话号， 并向 CRF提供该 TPF部分对话号， CRF建立 TPF/CRF对话状态模型， 为当前对话分配 CRF部分对话号， 将 TPF部分对话号与 CRF部分对话 号构成 TPF/CRF对话的完整对话号。 .
25、 根据权利要求 14所述的方法， 其特征在于， 所述步骤 A3之后 进一步包括： CRF向 TPF提供完整对话号， TPF根据完整对话号中的 TPF部分对话号索引至先前建立的 TPF/CRF对话状态模型， 并将 TPF 对话号更新为完整对话号。
26、根据权利要求 17所述的方法，其特征在于，该方法进一步包含： TPF为每个新建立的承载分配承载标识， 并向 CRF提供该承载标识。
PCT/CN2005/001237 2004-08-11 2005-08-11 Procede d'etablissement de dialogues sur la charge de paquets de donnees WO2006015547A1 (fr)

Priority Applications (5)

Application Number Priority Date Filing Date Title
AT05780653T ATE451769T1 (de) 2004-08-11 2005-08-11 Verfahren zur herstellung des gebührendialogs basierend auf den paketdaten
EP05780653A EP1772990B1 (en) 2004-08-11 2005-08-11 A method for establishing the dialog of the charge based on the packet data
DE602005018219T DE602005018219D1 (de) 2004-08-11 2005-08-11 Verfahren zur herstellung des gebührendialogs basierend auf den paketdaten
US11/702,520 US7889650B2 (en) 2004-08-11 2007-02-06 Method for establishing diameter session for packet flow based charging
US13/004,082 US8605585B2 (en) 2004-08-11 2011-01-11 Method for establishing diameter session for packet flow based charging

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN200410056106.X 2004-08-11
CNB200410056106XA CN1319317C (zh) 2004-08-11 2004-08-11 一种基于分组数据流计费的对话建立方法

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US11/702,520 Continuation US7889650B2 (en) 2004-08-11 2007-02-06 Method for establishing diameter session for packet flow based charging

Publications (1)

Publication Number Publication Date
WO2006015547A1 true WO2006015547A1 (fr) 2006-02-16

Family

ID=35839141

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2005/001237 WO2006015547A1 (fr) 2004-08-11 2005-08-11 Procede d'etablissement de dialogues sur la charge de paquets de donnees

Country Status (8)

Country Link
US (2) US7889650B2 (zh)
EP (2) EP2159955B1 (zh)
CN (1) CN1319317C (zh)
AT (2) ATE554596T1 (zh)
DE (1) DE602005018219D1 (zh)
ES (1) ES2335354T3 (zh)
RU (1) RU2349045C2 (zh)
WO (1) WO2006015547A1 (zh)

Families Citing this family (29)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1303781C (zh) * 2004-04-01 2007-03-07 华为技术有限公司 一种分组数据业务的计费控制方法
CN1319317C (zh) * 2004-08-11 2007-05-30 华为技术有限公司 一种基于分组数据流计费的对话建立方法
US8942668B2 (en) * 2007-04-20 2015-01-27 Alcatel Lucent Camel service charging in IMS networks
US20090279543A1 (en) * 2008-05-06 2009-11-12 Lucent Technologies Inc. Method and System for Handling Tethered User Devices in a Telecommunications Network
US8949447B2 (en) 2009-04-01 2015-02-03 Nokia Solutions And Networks Oy Optimized interface between two network elements operating under an authentication, authorization and accounting protocol
US20100260098A1 (en) * 2009-04-10 2010-10-14 Qualcomm Incorporated Header compression for ip relay nodes
US9480092B2 (en) * 2009-04-23 2016-10-25 Qualcomm Incorporated Establishing packet data network connectivity for local internet protocol access traffic
US8787174B2 (en) * 2009-12-31 2014-07-22 Tekelec, Inc. Methods, systems, and computer readable media for condition-triggered policies
US9185510B2 (en) * 2010-03-03 2015-11-10 Tekelec, Inc. Methods, systems, and computer readable media for managing the roaming preferences of mobile subscribers
US9917700B2 (en) 2010-03-15 2018-03-13 Tekelec, Inc. Systems, methods, and computer readable media for policy enforcement correlation
CN102209309B (zh) * 2010-03-30 2013-10-09 华为技术有限公司 流计费方法、装置和一种流计费系统
US8352803B2 (en) * 2010-06-07 2013-01-08 Alcatel Lucent Framework for managing failures in outbound messages
KR101413570B1 (ko) * 2010-10-05 2014-06-30 에이치티씨 코퍼레이션 Ａｐｎ 기반의 혼잡 제어의 처리 방법 및 관련 통신 장치
US8812020B2 (en) 2010-10-15 2014-08-19 Tekelec, Inc. Methods, systems, and computer readable media for location-based policy enhancement
US8626156B2 (en) 2010-10-20 2014-01-07 Tekelec, Inc. Methods, systems, and computer readable media for selective policy enhancement (PE) for high-usage roamers
JP4927213B1 (ja) * 2010-12-03 2012-05-09 株式会社エヌ・ティ・ティ・ドコモ 移動通信方法、ゲートウェイ装置、移動管理ノード及び呼セッション制御サーバ装置
US8681622B2 (en) 2010-12-17 2014-03-25 Tekelec, Inc. Policy and charging rules function (PCRF) and performance intelligence center (PIC) based congestion control
TWI429308B (zh) * 2011-02-14 2014-03-01 Wistron Corp 建立點對點傳輸的方法及行動通訊系統
EP2544487B1 (en) 2011-07-07 2015-11-18 HTC Corporation Method of handling access network discovery and selection function and related communication device
US9860390B2 (en) 2011-08-10 2018-01-02 Tekelec, Inc. Methods, systems, and computer readable media for policy event record generation
WO2014014823A1 (en) 2012-07-14 2014-01-23 Tekelec, Inc. Methods, systems, and computer readable media for policy-based local breakout (lbo)
US9369910B2 (en) 2012-07-14 2016-06-14 Tekelec, Inc. Methods, systems, and computer readable media for dynamically controlling congestion in a radio access network
CN104769980B (zh) 2012-07-20 2019-05-03 泰科来股份有限公司 向移动端分配策略规则的方法、系统和计算机可读介质
US20140059201A1 (en) * 2012-08-22 2014-02-27 Alcatel-Lucent Canada, Inc. Per flow dynamic metering selection
US10194414B2 (en) * 2013-01-07 2019-01-29 Futurewei Technologies, Inc. Information centric networking based service centric networking
EP2981108A4 (en) * 2013-05-15 2016-04-13 Huawei Tech Co Ltd BILLING LOADING METHOD, GATEWAY DEVICE, BILLING DEVICE AND COMMUNICATION SYSTEM
US10038796B2 (en) 2014-06-03 2018-07-31 Telefonaktiebolaget Lm Ericsson (Publ) Preemptive credit control
US11653284B1 (en) 2021-05-27 2023-05-16 T-Mobile Innovations Llc International call route generation based on analyzing minutes of use key performance indicators (KPIS) associated with an international communication service carrier
US11888598B1 (en) * 2023-04-18 2024-01-30 T-Mobile Innovations Llc Central routing function (CRF) implementation on a call route

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20040028055A1 (en) * 2002-07-26 2004-02-12 Lila Madour Differentiated accounting in a packet data network
CN1507200A (zh) * 2002-12-07 2004-06-23 ��Ϊ�������޹�˾ 能够基于用户数据流量计费的无线局域网服务系统及方法
KR20040064081A (ko) * 2003-01-09 2004-07-16 에스케이 텔레콤주식회사 무선 패킷 데이터 네트워크 상에서의 통합 과금 실시간한도 관리 시스템 및 그 운영 방법

Family Cites Families (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
GB9927597D0 (en) * 1999-11-22 2000-01-19 Nokia Networks Oy Improving charging efficiency
FI112151B (fi) * 1999-12-23 2003-10-31 Nokia Corp Sanoman välitys
US6834300B1 (en) * 2000-03-10 2004-12-21 Telefonaktiebolaget Lm Ericsson (Publ) Method in a packet data network of negotiating reporting mechanisms and reporting accounting records
US8699472B2 (en) * 2000-05-24 2014-04-15 Nokia Corporation Common charging identifier for communication networks
GB0021543D0 (en) * 2000-09-01 2000-10-18 Nokia Networks Oy Charging in communication systems
US20020068545A1 (en) * 2000-11-06 2002-06-06 Johnson Oyama Method and apparatus for coordinating charging for services provided in a multimedia session
ATE375690T1 (de) * 2000-11-06 2007-10-15 Ericsson Telefon Ab L M Verfahren und gerät für die koordinierte verrechnung von diensten in einem multimedia sitzung
WO2002100044A1 (en) * 2001-06-01 2002-12-12 Watercove Networks Implementing an intelligent network service for a packet-switched service using a node interfacing a mobile communications network to a packet data network
US20030152039A1 (en) * 2002-02-08 2003-08-14 Timothy Roberts Customer billing in a communications network
WO2005109938A1 (en) * 2004-05-12 2005-11-17 Telefonaktiebolaget L M Ericsson (Publ) Authentication system
DE602004010936T2 (de) * 2004-06-03 2009-01-02 Telefonaktiebolaget Lm Ericsson (Publ) Gebührenberechnungsmechanismen für IP-Multimediadienste
CN1319317C (zh) * 2004-08-11 2007-05-30 华为技术有限公司 一种基于分组数据流计费的对话建立方法

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20040028055A1 (en) * 2002-07-26 2004-02-12 Lila Madour Differentiated accounting in a packet data network
CN1507200A (zh) * 2002-12-07 2004-06-23 ��Ϊ�������޹�˾ 能够基于用户数据流量计费的无线局域网服务系统及方法
KR20040064081A (ko) * 2003-01-09 2004-07-16 에스케이 텔레콤주식회사 무선 패킷 데이터 네트워크 상에서의 통합 과금 실시간한도 관리 시스템 및 그 운영 방법

Also Published As

Publication number Publication date
ATE451769T1 (de) 2009-12-15
RU2007108378A (ru) 2008-09-20
EP1772990A1 (en) 2007-04-11
RU2349045C2 (ru) 2009-03-10
CN1735017A (zh) 2006-02-15
US7889650B2 (en) 2011-02-15
CN1319317C (zh) 2007-05-30
DE602005018219D1 (de) 2010-01-21
EP2159955B1 (en) 2012-04-18
ES2335354T3 (es) 2010-03-25
EP1772990A4 (en) 2008-01-23
EP2159955A1 (en) 2010-03-03
US20070189297A1 (en) 2007-08-16
ATE554596T1 (de) 2012-05-15
US20110103261A1 (en) 2011-05-05
EP1772990B1 (en) 2009-12-09
US8605585B2 (en) 2013-12-10

Similar Documents

Publication Publication Date Title
WO2006015547A1 (fr) Procede d'etablissement de dialogues sur la charge de paquets de donnees
US8798575B2 (en) Method for improving service data flow based charging and system thereof
JP4402714B2 (ja) フローベース課金におけるイベント・トリガと再認証トリガを取り扱う方法
EP1760932A1 (en) A method for processing the online charging
EP1732264B1 (en) A method for controlling the charching of the packet data service
EP1804419B1 (en) A method for processing the re-authorisation based on the charging of the packet data flow
JP4891223B2 (ja) パケットデータサービスの課金ルールを強化する方法及びその機能する方法
WO2005109748A1 (fr) Procede de selection de la regle de taxation destine a des utilisateurs
WO2006050669A1 (fr) Procede de chargement en fonction d'un flux de paquets de donnees
WO2005101734A1 (fr) Procede de facturation de services de donnees par paquets et de controle d'acces de flux de donnees de services
WO2006015543A1 (en) A processing method for re-authorization and re-authorization event and event triggers
WO2006060964A1 (fr) Systeme et procede de traitement permettant une facturation en fonction du flux de paquets de donnees
CN1322708C (zh) 一种移动分组数据业务中实现用户设备重定向的方法
WO2006050670A1 (fr) Procede de traitement de cle de taxation
WO2006015550A1 (fr) Procede de distribution du numero de dialogue du chargement fonde sur le flux de paquets de donnees

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A1

Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BW BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EC EE EG ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KM KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NA NG NI NO NZ OM PG PH PL PT RO RU SC SD SE SG SK SL SM SY TJ TM TN TR TT TZ UA UG US UZ VC VN YU ZA ZM ZW

AL Designated countries for regional patents

Kind code of ref document: A1

Designated state(s): BW GH GM KE LS MW MZ NA SD SL SZ TZ UG ZM ZW AM AZ BY KG KZ MD RU TJ TM AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IS IT LT LU LV MC NL PL PT RO SE SI SK TR BF BJ CF CG CI CM GA GN GQ GW ML MR NE SN TD TG

121 Ep: the epo has been informed by wipo that ep was designated in this application
WWE Wipo information: entry into national phase

Ref document number: 2005780653

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 11702520

Country of ref document: US

NENP Non-entry into the national phase

Ref country code: DE

WWE Wipo information: entry into national phase

Ref document number: 2007108378

Country of ref document: RU

WWP Wipo information: published in national office

Ref document number: 2005780653

Country of ref document: EP

WWP Wipo information: published in national office

Ref document number: 11702520

Country of ref document: US