EP1732264B1 - Verfahren zur Steuerung der Gebührenberechnung des Paketdatendienstes - Google Patents

Verfahren zur Steuerung der Gebührenberechnung des Paketdatendienstes Download PDF

Info

Publication number
EP1732264B1
EP1732264B1 EP05738259A EP05738259A EP1732264B1 EP 1732264 B1 EP1732264 B1 EP 1732264B1 EP 05738259 A EP05738259 A EP 05738259A EP 05738259 A EP05738259 A EP 05738259A EP 1732264 B1 EP1732264 B1 EP 1732264B1
Authority
EP
European Patent Office
Prior art keywords
crf
charging
tpf
event trigger
charging rule
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
EP05738259A
Other languages
English (en)
French (fr)
Other versions
EP1732264B8 (de
EP1732264A1 (de
EP1732264A4 (de
Inventor
Xiaoqin Huawei Administration Building DUAN
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
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
Family has litigation
First worldwide family litigation filed litigation Critical https://patents.darts-ip.com/?family=34888201&utm_source=google_patent&utm_medium=platform_link&utm_campaign=public_patent_search&patent=EP1732264(B1) "Global patent litigation dataset” by Darts-ip is licensed under a Creative Commons Attribution 4.0 International License.
Application filed by Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Publication of EP1732264A1 publication Critical patent/EP1732264A1/de
Publication of EP1732264A4 publication Critical patent/EP1732264A4/de
Publication of EP1732264B1 publication Critical patent/EP1732264B1/de
Application granted granted Critical
Publication of EP1732264B8 publication Critical patent/EP1732264B8/de
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/24—Accounting or billing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/14—Charging, metering or billing arrangements for data wireline or wireless communications
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/14—Charging, metering or billing arrangements for data wireline or wireless communications
    • H04L12/1403—Architecture for metering, charging or billing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M2215/00—Metering arrangements; Time controlling arrangements; Time indicating arrangements
    • H04M2215/20—Technology dependant metering
    • H04M2215/2026—Wireless network, e.g. GSM, PCS, TACS
    • 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

Definitions

  • the present invention relates to a method of charging, and more specifically to a method of charging control for packet data service.
  • FIG. 1 is a flowchart illustrating an activation, data transmission and de-activation of a Packet Data Protocol Context (PDP Context).
  • PDP Context Packet Data Protocol Context
  • GPRS General Packet Radio Service
  • the charging starts when the PDP context is activated and comes to its end when the PDP context is de-activated, which means the present charging system can only charges according to a transmitted data flow or an activate time duration of the PDP context.
  • the UE after establishing a transmission channel with the PDN, the UE performs a plurality of services based on one activated PDP Context, i.e.
  • an activated PDP Context is able to bear various services provided by the PDN after the UE establishes a transmission channel with this PDN.
  • operators or service providers may adopt different charging approaches for different charging modes of various services, for instance, Send/Receive Email service may be charged based on trigger times of Sending and Receiving events, WAP browse service may be charged according to flow, file transfer service may also be charged according to flow, and yet, a charging rate of WAP browse service is different from that of file transfer service.
  • IP Flow Based Charging can be described like this: IP Flows of different services that the same PDP Context bears are separately screened out through some filters similar to sieves, then the IP Flows that are screened out by different filters are separately charged so as to reach the object of separately charging different Service Data Flows. In this way, a charging granularity based on IP Flows is far less than that based on a PDP Context.
  • the charging granularity may be regard as the size of a hole of a sieve, therefore the charging granularity based on one PDP Context will be like a sieve hole determined by one PDP Context while the charging granularity based on IP Flow will be like a sieve hole determined by one IP Flow, that is, there will be more than one sieve holes contained in one PDP Context. Therefore, comparing with the charging based on one PDP Context, charging based on IP Flow can provide more charging approaches for operators or service providers.
  • FIG. 2A The FBC system architecture supporting online charging is shown in Figure 2A , in which Online Charging System (OCS) 206 is composed of Service Control Point (SCP) 201of Customized Application for Mobile Network Enhanced Logic (CAMEL) and a service data flow based Credit Control Function (CCF) 202.
  • SCP Service Control Point
  • CAMEL Customized Application for Mobile Network Enhanced Logic
  • CCF Credit Control Function
  • CCF 202 is connected with service data flow based Charging Rule Function (CRF) 203 through an interface Ry.
  • the CRF 203 is connected with an Application Function (AF) 204 through an interface Rx and with the Traffic Plane Function (TPF) 205 through an interface Gx.
  • the CCF 202 is connected with TPF 205 through an interface Gy.
  • AF Application Function
  • TPF Traffic Plane Function
  • the FBC system architecture supporting offline charging is shown in Figure 2B , in which the CRF 203 is connected with the AF 204 through an interface Rx and with the TPF 205 through an interface Gx, and the TPF 205 is connected with a Charging Gateway Function (CGF) 207 and a Charging Collection Function (CCF) 208 respectively through Gz.
  • CGF Charging Gateway Function
  • CCF Charging Collection Function
  • the TPF 205 bears IP Flows.
  • the TPF 205 sends a Charging Rule Request to the CRF 203 through the Gx interface.
  • the Charging Rule Request carries relevant information of subscriber and the UE, bearer characteristics, network information, and so on.
  • the relevant information of subscriber and the UE may be a Mobile Station ISDN (MSISDN), an International Mobile Subscriber Identity (IMSI) and etc.
  • MSISDN Mobile Station ISDN
  • IMSI International Mobile Subscriber Identity
  • the bearer may be modified during the IP Flow transmission. For example, when QoS parameters of the same service are different, charging rules may be different accordingly. For instance, the charging rate may be decrease as QoS parameters decrease.
  • the TPF 205 resends a Charging Rule Request to the CRF 203 to request for new charging rules.
  • the CRF 203 selects a proper charging rule according to the said input information provided by the TPF 205 and then returns the selected charging rule to the TPF 205.
  • the charging rule includes information of charging mechanism, charging type, charging key, Service Data Flow Filter, and charging rule precedence.
  • the charging mechanism may be online charging or offline charging.
  • the charging type may be a type of time span based.
  • the charging key is a parameter related with the charging rate, and the CRF 203 may provide only parameters related with the charging rate for the TPF 205, rather than directly provide the charging rate for the TPF 205.
  • the Service Data Flow Filter is used to indicate the TPF 205 which IP Flows are to be filtered, and then the TPF 205 charges these filtered IP Flows according to the charging rules.
  • Service Data Flow Filter may include IP quintuple having such information as Source/Destination IP Address, Source/Destination Port Number, and Protocol ID.
  • the CRF 203 indicates the TPF 205 to filter the IP Flow with the Source IP Address 10.0.0.1, Destination IP Address 10.0.0.2, Source/Destination Port Number 20 and the protocol type Transmission Control Protocol (TCP), and then charges the filtered IP Flow according to the charging rule.
  • TPF 205 may as well send a Charging Rule Request to the CRF 203 to request a new charging rule from the CRF.
  • the CRF 203 may request the TPF 205 to delete the previously installed charging rule.
  • the CRF 203 may determine the charging rule according to the input information of the AF 204 or OCS 20 apart from the input information of the TPF 205.
  • the AF 204 may notify the CRF 203 of the current service type used by the user, and the CRF 203 may select the corresponding charging rule according to this service type.
  • the TPF 205 is the GGSN
  • the AF is a service gateway or a service server in the PDN
  • the CRF 203 is an added logical entity.
  • the TPF 205 is the executing point of charging rules and the CRF 203 is the control point of charging rules.
  • Figure 3A is the flow chart of issuing the charging rule when a bearer is established. As shown in Figure 3A , the implementing procedure of issuing the charging rule when a bearer is established includes the following steps:
  • Figure 3B is the flow chart of issuing the charging rule when a bearer is modified. As shown in Figure 3B , the implementing procedure of issuing the charging rule when a bearer is modified includes the following steps:
  • Figure 3C is the flow chart of issuing the charging rule when a bearer is deleted.
  • the implementing procedure of issuing the charging rule when a bearer is deleted includes the following steps:
  • the CRF may also voluntarily send a charging rule to the TPF. For instance, in the data transmission process between the UE and the AF, after receiving the input information relating to charging of the AF, the CRF selects a proper charging rule according to the input information provided by the AF, and then voluntarily issues the selected charging rule to the TPF.
  • the specific implementing procedure of the AF providing the input information of charging for the CRF is shown in Figure 4 :
  • Figure 5 is the flow chart of the CRF voluntarily issuing the charging rule to the TPF.
  • the implementing procedure of the CRF voluntarily issuing the charging rule to the TPF includes the following steps:
  • the interactive mode concerning charging rule between the TPF and the CRF is defined in 3GPP Specification like this:
  • the TPF sends a Charging Rule Request to the CRF when a certain trigger event is met.
  • the trigger event may be an event of establishing, modifying or deleting the bearer.
  • the CRF selects a proper charging rule according to the information carried in the Charging Rule Request and sends the selected charging rule to the TPF.
  • the event trigger of the Charging Rule Request is controlled by the TPF.
  • the event trigger of the Charging Rule Request shall be set in the TPF in advance. Whenever the event of establishing, modifying or deleting the bearer is met, the TPF sends the Charging Rule Request to the CRF.
  • the QoS parameters modified have little differences compared with original QoS parameters when the QoS parameters are modified during the modification of the bearer, and it is not necessary to modify the charging rules.
  • the CRF may select a charging rule similar to an original one to send to the TPF when the TPF sends the Charging Rule Request, thereby creating a great of redundant information.
  • a method, apparatus and system for controlling charging of packet data service are provided so as to make charging control of packet data service reasonable and perfect.
  • Event triggers each representing a bearer service modification are set by the CRF and then are provided to the TPF.
  • the event triggers are set according to self-stored information in the CRF, or charging-relevant input information provided by an Application Function (AF), an Online Charging System (OCS), the TPF, or any combinations of the AF, the OCS, and the TPF.
  • the TPF stores the event triggers received from the CRF and monitors if any of the event triggers is met.
  • the request sent from the TPF to the CRF when one of the event triggers is met selectively includes an event identifier which indicates a corresponding trigger event, and then the CRF responses for the request by providing a charging rule in a charging rules provision procedure according to the trigger event.
  • an event trigger is set such that the TPF requests corresponding charging rules from the CRF when the event trigger is met.
  • This event trigger may be set in the TPF or be determined by the CRF.
  • the CRF determines the event triggers according which the TPF needs to request charging rules therefrom and then sends the event triggers to the TPF.
  • the TPF requests the charging rules from the CRF and provides the charging-relevant input information to the CRF. Then the CRF selects a proper charging rule according to the charging-relevant input information and sends the selected charging rules to the TPF.
  • the CRF since it is possible for the CRF to obtain charging-relevant input information provided by the AF or the OCS and the charging-relevant input information may affect the charging rules.
  • the CRF is able to flexibly set event triggers according to the charging-relevant input information and send the current event triggers to the TPF so that the TPF requests new charging rules from the CRF when a certain event trigger is met. In this way, flexible and various applications of charging rules may be implemented.
  • functions mentioned above are completely impossible to be achieved by the existing methods of interaction between the TPF and the CRF.
  • a plurality of event triggers is set such that a TPF requests corresponding charging rules from a CRF when one of the event triggers is met.
  • These event triggers may be set in the TPF or be determined by the CRF.
  • the CRF determines the event triggers according which the TPF needs to request the charging rules therefrom, and then sends the event triggers to the TPF.
  • the TPF requests the charging rule from the CRF and provides charging-relevant input information.
  • the CRF selects the proper charging rule according to the charging-relevant input information and sends the selected charging rule to the TPF. In this way, it is possible to control the timing of the TPF requesting charging rules from the CRF, avoiding redundant information caused by the TPF when sending unwanted Charging Rule Requests to the CRF.
  • FIG. 6 is a flowchart showing the CRF controls the TPF to send the Charging Rule Requests. As shown in figure 6 , the implementation of the control includes the following steps:
  • Step 601 Setting a static event trigger enable the TPF to be triggered to request a corresponding charging rule from the CRF in the TPF, such as a static event trigger representing bearer establishment.
  • a static event trigger representing bearer establishment.
  • the TPF sends the Charging Rule Request to the CRF and the Charging Rule Request carries charging-relevant input information, such as the information related with the subscriber and the UE, the bearer characteristics and the information related with the network.
  • This Charging Rule Request may also carry an event identifier to indicate that the current Charging Rule Request is triggered by the static event trigger.
  • more than one static event trigger may be set in the TPF, such as bearer establishment, bearer deletion and so on.
  • the TPF requests the charging rule from the CRF.
  • the TPF may not set the static event trigger therein and periodically sends the Charging Rule Request to the CRF when the bearer is established.
  • Step 602 After receiving the Charging Rule Request, the CRF sets dynamic event triggers at which the TPF is required to request charging rules, and then sends a Request Dynamic Event Report to the TPF.
  • the Request Dynamic Event Report carries a list of dynamic event triggers, such as dynamic event trigger A, dynamic event trigger B and dynamic event trigger C. These events may be a plurality of various Modify Bearer Events, such as the change of the SGSN, of the Public Land Mobile Network (PLMN), of the Radio Access Technology (RAT) type, of the Traffic Flow Template, and of the QoS.
  • PLMN Public Land Mobile Network
  • RAT Radio Access Technology
  • Step 603 According to the charging-relevant input information carried by the Charging Rule Request, the CRF selects a proper charging rule, and then sends a Provision Charging Rule to the TPF.
  • the Provision Charging Rule may carry the selected charging rule, such as charging rule 1.
  • the information that the CRF sends to the TPF in steps 602 and 603 may be carried in one message.
  • Step 604 After receiving the dynamic event trigger list and the charging rule currently selected by the CRF, the TPF stores the dynamic event trigger list, performs charging information statistics according to the selected charging rule, and monitors if any of the dynamic event trigger is met.
  • Step 605 The TPF monitors the occurrence of a dynamic event trigger A, and then sends a Charging Rule Request to the CRF.
  • the Charging Rule Request carries the occurrence indicator of the dynamic event trigger A.
  • Step 606 After receiving the Charging Rule Request, the CRF confirms that this Charging Rule Request is triggered by the dynamic event trigger A according to the occurrence indicator of the dynamic event trigger A and selects a proper charging rule also according to the dynamic event trigger A, and then sends the Provision Charging Rule to the TPF.
  • the Provision Charging Rule carries a newly-selected charging rule, such as charging rule 2.
  • Step 607 After receiving the Provision Charging Rule, the TPF performs charging information statistics according to the Provision Charging Rule.
  • the TPF continues to monitor if any of other dynamic event triggers is met.
  • Step 608 the TPF monitors the occurrence of the dynamic event trigger B, and then sends the Charging Rule Request to the CRF.
  • the Charging Rule Request carries the occurrence indicator of the dynamic event trigger B.
  • Step 609 After receiving the Charging Rule Request, the CRF confirms that this Charging Rule Request is triggered by the dynamic event trigger B according to the occurrence indicator of the dynamic event trigger B and selects a proper charging rule also according to the dynamic event trigger B, and then the CRF sends the Provision Charging Rule to the TPF.
  • the Provision Charging Rule carries a newly-selected charging rule, such as charging rule 3.
  • Step 610 After receiving the Provision Charging Rule, the TPF take statistics of the charging information according to the Provision Charging Rule.
  • the CRF setting dynamic event triggers includes that said dynamic event triggers are set according to charging-relevant input information provided by an Application Function, AF, an Online Charging System, OCS, the TPF, or combinations of the AF, the OCS, and the TPF.
  • an Application Function AF
  • an Online Charging System OCS
  • the TPF or combinations of the AF, the OCS, and the TPF.
  • the same session means the same PDP Context in a GPRS network.
  • the CRF may set in the same session dynamic event triggers more than once and send these dynamic event triggers to the TPF. For instance, when receiving charging-relevant input information from the AF or the OCS, the CRF determines whether it is needed to set a new dynamic event trigger according to the charging-relevant input information, if yes, the CRF sets a new dynamic event trigger and sends the point to the TPF. After receiving the new dynamic event trigger, the TPF stores the new dynamic event trigger and monitors occurrence of the dynamic event trigger.
  • the static event triggers for requesting charging rule from the CRF may be set in the TPF, such routine events of bearer change as bearer establishment, bearer modification, bearer deletion, occurrence of events when a fixed value of flow or time duration is reached and so on, may be reported to the CRF directly by pre-configuring static event triggers in TPF and there is no need for the CRF to send dynamic event triggers to the TPF.
  • routine events of bearer change for example, it is always required for the TPF to report to the CRF when the service flow reaches 10M, or when the service has been activated for 100 minutes, without any other event point requiring dynamic configuration.
  • only appropriate static event triggers are pre-configured in the TPF while no dynamic event trigger will be issued by the CRF such that the signaling load between the TPF and the CRF can be reduced.
  • FIG. 7 is a schematic diagram illustrating Embodiment 1 of this invention, where the static event trigger for the TPF to request a charging rule from the CRF is set as bearer establishment, the CRF set the dynamic event triggers at which the TPF is required to send the Charging Rule Request to the CRF when the bearer is modified or removed, and the implementing procedure showing the CRF controls the TPF to send the Charging Rule Request includes the following steps:
  • Step 701 The UE sends an Establish Bearer Service Request to the TPF.
  • the corresponding step is that the GGSN receives Create PDP Context Request.
  • Step 702 After receiving Establish Bearer Service Request, the TPF confirms the occurrence of a static event trigger, and then sends the Charging Rule Request to the CRF.
  • the Charging Rule Request carries the charging-relevant input information, such as the relevant information of a subscriber and the UE, bearer characteristics and network information.
  • the request may also carry an event identifier for indicating that the current Charging Rule Request is triggered by a static event trigger.
  • Steps 703 ⁇ 704 After receiving the Charging Rule Request, the CRF confirms according to the event identifier that Charging Rule Request is triggered by a static event trigger, sets a dynamic event trigger list including bearer modification and bearer deletion, and then sends the Request Dynamic Event Report to the TPF.
  • the Request Dynamic Event Report carries the dynamic event trigger list.
  • the CRF may set a plurality of various values, such as various QoS parameter priorities, in the dynamic event trigger of the bearer modification and each value may be an independent dynamic event trigger.
  • Steps 705 ⁇ 706 The CRF selects a proper charging rule according to the charging-relevant input information carried by the Charging Rule Request, and then sends the Charging Rule Response to the TPF.
  • the Charging Rule Response carries the selected charging rule.
  • Steps 707 ⁇ 708 After receiving the dynamic event trigger list set by the CRF and the charging rule selected by the CRF, the TPF stores the dynamic event trigger list, performs charging information statistics according to the charging rule, and monitors occurrence of the dynamic event triggers. The TPF returns an Establish Bearer Service Accept message to the UE, accepts an Establish Bearer Service Request initiated by the UE and continues with the subsequent steps of the flow of the bearer establishment.
  • Step 709 After a while, the UE sends a Modify Bearer Service Request to the TPF.
  • the UE sends a Modify Bearer Service Request to the TPF.
  • the corresponding step is that the GGSN receives Update PDP Context Request.
  • Step 710 After receiving the Modify Bearer Service Request, the TPF confirms that the dynamic event trigger of the bearer modification in the dynamic event trigger list has occurred, and then sends the Charging Rule Request to the CRF.
  • the Charging Rule Request carries the occurrence indicator of the dynamic event trigger.
  • Steps 711 ⁇ 712 After receiving the Charging Rule Request, the CRF confirms according to the occurrence indicator of dynamic event trigger that the Charging Rule Request is triggered by the dynamic event trigger of bearer modification, selects a proper charging rule according to the bearer modification, and then sends the Provision Charging Rule to the TPF.
  • the Provision Charging Rule may carry the selected charging rule.
  • Steps 713 ⁇ 714 After receiving the Provision Charging Rule, the TPF installs a new charging rule according to the charging rule selected by the CRF, or removes the original charging rule, or installs a new charging rule while deleting the original one, then returns the Modify Bearer Service Accept to the UE, accepts the Modify Bearer Service Request initiated by the UE, and continues with the subsequent steps of the flow of the bearer modification.
  • Step 715 After a while, the UE sends a Remove Bearer Service Request to the TPF.
  • the UE sends a Remove Bearer Service Request to the TPF.
  • the corresponding step is that the GGSN receives Delete PDP Context Request.
  • Step 716 After receiving the Remove Bearer Service Request, the TPF confirms that the dynamic event trigger of bearer deletion in the dynamic event trigger list has occurred, and then sends the Charging Rule Request to the CRF.
  • the Charging Rule Request carries the occurrence indicator of dynamic event trigger.
  • Steps 717 ⁇ 718 After receiving the Charging Rule Request, the CRF confirms that the Charging Rule Request is triggered by the dynamic event trigger of bearer deletion according to the occurrence indicator of dynamic event trigger, selects the proper charging rule according to bearer deletion , and then sends the Provision Charging Rule to the TPF.
  • the Provision Charging Rule may carry the selected charging rule.
  • Steps 719 ⁇ 720 After receiving the Provision Charging Rule, the CRF installs a new charging rule according to the charging rule selected by the CRF, or deletes the original charging rule, or installs a new charging rule while deleting the original one, and then returns the Remove Bearer Service Accept message to the UE, accepts the Remove Bearer Service Request initiated by the UE and continues with the subsequent steps of the flow of the bearer deletion.
  • the AF sends the Application/Service Data Flow Charging Information to the CRF as the charging-relevant input information for the CRF to the select charging rules. Then, in the method provided in the present invention, the AF sends the Application/Service Data Flow Charging Information to the CRF as the input information for the CRF to dynamically set dynamic event triggers.
  • FIG. 8 is a schematic diagram illustrating Embodiment 2 of this invention, as shown in figure 8 , the implementing procedure in the present embodiment for the CRF to issue a dynamic event trigger to the TPF includes the following steps:
  • Step 801 The CRF receives a certain Internal or External Trigger Event.
  • the AF provides an accredited activity for the users. If the data flow of a certain service of this AF visited by one user reaches a set value, the subsequent charging rate of the user's to this service decreases. In this case, the AF requires the CRF to adopt a favorable charging rate to take charging information statistics for subsequent data flow when the data flow of a certain service filter reaches a set value. Or, if the duration for which a user has accessed a certain service of this AF reaches a set value, the subsequent charging rate of the user's to this service decreases. In this case, the AF requires the CRF to adopt a favorable charging rate to perform charging information statistics for subsequent data flow when the duration for which a certain service filter has been used arrives at a set value.
  • Step 802 The CRF sets a dynamic event trigger, for instance, as when the data flow of a certain service filter reaches a set value or as when a certain service filter has been used for a set time span. Furthermore, the CRF may select a proper charging rule according to the information currently acquired, such as the User/Terminal information, bearer characteristics, and network information provided by the TPF.
  • Step 803 the CRF sends the Request Dynamic Event Report carrying the current dynamic event trigger list to the TPF and requires the TPF to request a charging rule from the CRF when a dynamic event trigger thereof is met.
  • Step 804 The CRF sends the Provision Charging Rule to the TPF and the Provision Charging Rule carries the charging rule currently selected. This step is optional.
  • the TPF receives the current dynamic event trigger list set by the CRF and stores this dynamic event trigger list. If the TPF also receives the Provision Charging Rule, the TPF installs a new charging rule according to the charging rule selected by the CRF, or deletes the original charging rule, or installs a new charging rule while deleting the original one.
  • Step 806 After a while, the TPF monitors the occurrence of a dynamic event trigger, and then sends the Charging Rule Request to the CRF.
  • the Charging Rule Request carries an occurrence indicator of dynamic event trigger.
  • Step 807 ⁇ 808 After receiving the Charging Rule Request, the CRF confirms that which dynamic event trigger triggers this Charging Rule Request according to the occurrence indicator of the dynamic event trigger.
  • the event may be an event that the data flow of a certain service filter reaches the set value or an event that a certain service filter has been in use for a set time span.
  • the CRF selects a proper charging rule according to this dynamic event trigger and send the Provision Charging Rule to the TPF.
  • the Provision Charging Rule may carry the selected charging rule.
  • Step 809 After receiving the Provision Charging Rule, the TPF installs a new charging rule according to the charging rule selected by the CRF, or deletes the original charging rule, or installs a new charging rule while deleting the original one.
  • the CRF may also dynamically set dynamic event triggers according to the charging-relevant input information sent by the OCS concerning users' credit.
  • the corresponding flow is basically the same as the above and further description is not necessary.

Landscapes

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

Claims (15)

  1. Verfahren zum Kontrollieren der Gebührenberechnung eines Paketdatendienstes, umfassend:
    Überwachen eines Ereignisauslösers, der für eine Datenverkehrsebenenfunktion, TPF, vorgesehen ist; und
    Senden einer Gebührenberechnungsregelanfrage von der TPF an die Gebührenberechnungsregelfunktion, CRF, wenn der Ereignisauslöser ausgelöst wird; dadurch gekennzeichnet, dass der Ereignisauslöser durch die CRF der TPF bereitgestellt wird.
  2. Verfahren nach Anspruch 1, wobei
    der Ereignisauslöser durch die CRF eingestellt wird; und
    der Ereignisauslöser, der durch die CRF eingestellt wird, eine Bearer-Modifikation umfasst.
  3. Verfahren nach Anspruch 1, wobei
    der Ereignisauslöser durch die CRF eingestellt wird; und
    der Ereignisauslöser, der durch die CRF eingestellt wurde, zumindest eine der Änderungen von SGSN, PLMN, einer Funkzugangstechnologie, RAT, eines Datenverkehrsfluss-Templates und QoS umfasst.
  4. Verfahren nach einem der Ansprüche 1 - 3, umfassend:
    Speichern des Ereignisauslösers, der durch die CRF bereitgestellt wurde, durch die TPF.
  5. Verfahren nach einem der Ansprüche 1 - 4, wobei die Gebührenberechnungsregelanfrage, die von der TPF an die CRF gesendet wurde, einen Ereignisidentifizierer umfasst, der den Ereignisauslöser anzeigt.
  6. Verfahren nach Anspruch 5, wobei die CRF auf die Gebührenberechnungsregelanfrage antwortet, indem sie eine Gebührenberechnungsregel in einem Gebührenberechnungsregel-Bereitstellungsverfahren gemäß dem auslösenden Ereignis bereitstellt.
  7. Verfahren nach Anspruch 1, wobei der Ereignisauslöser entsprechend einer relevanten Information, die in der CRF gespeichert ist, oder gemäß einer gebührenberechnungsrelevanten Eingabeinformation, die bereitgestellt wurde durch zumindest eine aus einer Anwendungsfunktion, AF, eines Online-Gebühren-berechnungssystems, OCS, und der TPF, durch die CRF bereitgestellt wird.
  8. Datenverkehrsebenenfunktion , TPF, zum Kontrollieren der Gebührenberechnung eines Paketdatendienstes, umfassend:
    eine Überwachungseinheit, die konfiguriert ist, um den Ereignisauslöser zu überwachen; und
    eine Sendeeinheit, die konfiguriert ist, um eine Gebührenberechnungsregelanfrage an die Gebührenberechnungsregelfunktion, CRF, zu senden, wenn der Ereignisauslöser ausgelöst wird; dadurch gekennzeichnet, dass die TPF ferner eine Empfangseinheit umfasst, die konfiguriert ist, um einen Ereignisauslöser von der CRF zu empfangen.
  9. TPF nach Anspruch 8, wobei
    der Ereignisauslöser zumindest eines aus einer Bearer-Modifikation, einer Änderung von SGSN, PLMN, einer Funkzugangstechnologie, RAT, eines Datenverkehrsfluss-Templates und QoS umfasst.
  10. TPF nach einem Ansprüche 8 - 9 umfassend eine Einheit, die konfiguriert ist, um den Ereignisauslöser, der durch den CRF bereitgestellt ist, zu speichern.
  11. Gebührenberechnungsregelfunktion, CRF, zum Kontrollieren der Gebührenberechnung eines Paketdatendienstes, dadurch gekennzeichnet, dass sie umfasst:
    eine Bestimmungseinheit, die konfiguriert ist, um einen Ereignisauslöser zu bestimmen; und
    eine Bereitstellungseinheit, die konfiguriert ist, um den Ereignisauslöser an eine Datenverkehrsebenenfunktion, TPF, bereitzustellen.
  12. CRF nach Anspruch 11, wobei der Ereignisauslöser durch die CRF gemäß einer relevanten Information, die in der CRF gespeichert ist, oder gemäß einer gebührenberechnungsrelevanten Eingabeinformation, die bereitgestellt wurde durch zumindest eine von einer Anwendungsfunktion, AF, eines Online-Gebührenberechnungssystems, OCS, und der TPF, bereitgestellt wird.
  13. CRF nach Anspruch 11, wobei
    der Ereignisauslöser zumindest eins aus einer Bearer-Modifikation, einer Änderung von SGSN, PLMN, einer Funkzugangstechnologie, RAT, eines Datenverkehrsfluss-Templates und QoS umfasst.
  14. System zum Kontrollieren einer Gebührenberechnung eines Paketdatendienstes, dadurch gekennzeichnet, dass es umfasst:
    eine Gebührenberechnungsregelfunktion, CRF, die konfiguriert ist, um einen Ereignisauslöser bereitzustellen; und
    eine Datenverkehrsebenenfunktion, TPF, die gemäß irgendeinem der Ansprüche 8 und 9 definiert ist.
  15. System nach Anspruch 14, wobei der Ereignisauslöser durch die CRF bereitgestellt wird gemäß einer relevanten Information, die in der CRF gespeichert ist, oder gemäß gebührenberechnungsrelevanter
    Eingabeinformation, die durch zumindest eines aus einer Eingabefunktion, AF, eines Online-Gebührenberechnungssystems, OCS, und der TPF bereitgestellt ist.
EP05738259A 2004-04-01 2005-03-28 Verfahren zur Steuerung der Gebührenberechnung des Paketdatendienstes Active EP1732264B8 (de)

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
CN200410030955 2004-04-01
CNB2004100337219A CN1303781C (zh) 2004-04-01 2004-04-09 一种分组数据业务的计费控制方法
PCT/CN2005/000388 WO2005096547A1 (fr) 2004-04-01 2005-03-28 Procede permettant de commander la facturation d'un service de commutation de paquets

Publications (4)

Publication Number Publication Date
EP1732264A1 EP1732264A1 (de) 2006-12-13
EP1732264A4 EP1732264A4 (de) 2007-03-28
EP1732264B1 true EP1732264B1 (de) 2009-02-25
EP1732264B8 EP1732264B8 (de) 2009-08-26

Family

ID=34888201

Family Applications (1)

Application Number Title Priority Date Filing Date
EP05738259A Active EP1732264B8 (de) 2004-04-01 2005-03-28 Verfahren zur Steuerung der Gebührenberechnung des Paketdatendienstes

Country Status (7)

Country Link
US (3) US8009573B2 (de)
EP (1) EP1732264B8 (de)
JP (2) JP2007529925A (de)
CN (1) CN1303781C (de)
AT (1) ATE424068T1 (de)
DE (1) DE602005012935D1 (de)
WO (1) WO2005096547A1 (de)

Families Citing this family (25)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1303781C (zh) * 2004-04-01 2007-03-07 华为技术有限公司 一种分组数据业务的计费控制方法
CN1794638A (zh) * 2005-08-03 2006-06-28 华为技术有限公司 Oma业务应用接入计费系统的方法和计费引擎
CN100563388C (zh) * 2006-06-01 2009-11-25 华为技术有限公司 一种用户漫游状态下的策略及计费控制方法
CN102711053B (zh) * 2006-06-22 2014-11-05 华为技术有限公司 一种即按即通系统中的计费方法和装置
CN101094080B (zh) * 2006-06-22 2012-06-20 华为技术有限公司 一种即按即通系统中的计费方法
CN101291233B (zh) 2007-04-20 2011-04-20 华为技术有限公司 一种实现事件检测的方法及系统
US9379898B2 (en) * 2007-05-04 2016-06-28 Tekelec, Inc. Methods, systems, and computer program products for providing billing and usage data to downstream applications
CN101056448B (zh) * 2007-05-15 2010-12-08 华为技术有限公司 检测服务质量参数的方法及网络侧通信设备
US8155620B2 (en) 2007-06-13 2012-04-10 Qualcomm Incorporated Method and apparatus for accounting in a mobile data packet network
CN101325780B (zh) 2007-06-15 2010-07-07 华为技术有限公司 策略控制实现方法和系统、及策略和计费执行实体
CN101374055B (zh) 2007-08-20 2012-12-12 华为技术有限公司 计费处理方法和网络系统、分组数据网络网关及计费系统
CN101583152B (zh) 2008-05-15 2011-08-24 华为技术有限公司 一种信息传递方法、装置和系统
CN101511075B (zh) * 2009-03-17 2014-12-17 中国移动（深圳）有限公司 一种通信服务计费方法和通信服务计费系统
CN101883321B (zh) * 2009-05-05 2014-03-19 中兴通讯股份有限公司 多媒体广播组播业务中获取接入信息、计费的方法和系统
JP5047231B2 (ja) * 2009-06-25 2012-10-10 株式会社日立製作所 無線通信装置および無線通信方法
JPWO2011040511A1 (ja) * 2009-09-30 2013-02-28 日本電気株式会社 課金処理システム、ネットワークスイッチ、ネットワーク管理サーバ、課金処理方法、及び課金処理プログラム
EP2515475B1 (de) 2010-01-12 2018-06-13 Huawei Technologies Co., Ltd. Vergebührungsverfahren, netzwerkvorrichtung und mobilitätsverwaltungelement
US8352803B2 (en) * 2010-06-07 2013-01-08 Alcatel Lucent Framework for managing failures in outbound messages
CN102143467B (zh) * 2010-08-25 2014-07-30 华为技术有限公司 一种实现计费的方法、装置及系统
US9432520B2 (en) 2013-03-14 2016-08-30 Tracfone Wireless, Inc. Proxy-based usage tracking for a wireless device
EP3883181A1 (de) 2014-10-28 2021-09-22 Convida Wireless, LLC Verfahren und vorrichtungen für dienstschichtladekorrelation mit zugrunde liegenden netzwerken
CN104468135B (zh) 2014-11-18 2018-01-23 华为技术有限公司 一种在线计费中交互信息的方法及装置
JP6477084B2 (ja) * 2015-03-19 2019-03-06 日本電気株式会社 通信装置、通信方法
WO2017084092A1 (zh) * 2015-11-20 2017-05-26 华为技术有限公司 一种计费方法、控制面网元、转发面网元和计费系统
US10291790B2 (en) * 2017-10-06 2019-05-14 Wipro Limited System and method for dynamic charging in communication networks

Family Cites Families (55)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5790642A (en) * 1995-04-28 1998-08-04 Dialogic Corporation Competitively bidding service centers
US5598417A (en) 1995-04-28 1997-01-28 Motorola, Inc. Dynamic control of a data channel in a TDM wireless communication system
US5917897A (en) * 1997-02-24 1999-06-29 Summit Telecom System, Inc. System and method for controlling a telecommunication network in accordance with economic incentives
JPH10136126A (ja) 1996-09-04 1998-05-22 Nippon Telegr & Teleph Corp <Ntt> 分担課金方法
US5757894A (en) * 1996-09-09 1998-05-26 Bell Atlantic Network Services, Inc. Virtual foreign exchange service
US5963625A (en) * 1996-09-30 1999-10-05 At&T Corp Method for providing called service provider control of caller access to pay services
JP3359512B2 (ja) * 1996-10-30 2002-12-24 富士通株式会社 課金レート情報更新方法
US6023499A (en) 1997-11-26 2000-02-08 International Business Machines Corporation Real time billing via the internet for advanced intelligent network services
GB9927597D0 (en) * 1999-11-22 2000-01-19 Nokia Networks Oy Improving charging efficiency
US6434380B1 (en) * 1999-12-13 2002-08-13 Telefonaktiebolaget Lm Ericsson (Publ) Dynamic negotiation of resources for user equipment in wireless communications system
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
FI113726B (fi) * 2000-05-25 2004-05-31 Nokia Corp Tilaajan laskuttamisen järjestäminen tietoliikennejärjestelmässä
EP1168806A1 (de) * 2000-06-29 2002-01-02 TELEFONAKTIEBOLAGET LM ERICSSON (publ) Verfahren und Vorrichtung zur Berechnung von Telekommunikationsdiensten
ATE362251T1 (de) * 2000-09-11 2007-06-15 Transnexus Inc Verrechnungsserver für internet- und multimedia- kommunikationen
GB0031459D0 (en) * 2000-12-22 2001-02-07 Nokia Networks Oy Charging in a communication system
DE60138414D1 (de) * 2001-01-03 2009-05-28 Nokia Corp Aoc in ganz ip netze
EP1223737A1 (de) * 2001-01-15 2002-07-17 Lucent Technologies Inc. Bereitstellung von vorausbezahltem Funkdienst zu einer umherstreifenden GPRS-Mobilstation
US6879584B2 (en) * 2001-01-31 2005-04-12 Motorola, Inc. Communication services through multiple service providers
US20020138331A1 (en) * 2001-02-05 2002-09-26 Hosea Devin F. Method and system for web page personalization
US20020152319A1 (en) * 2001-02-08 2002-10-17 Amin Rajesh B. Accounting management support based on QOS in an IP centric distributed network
WO2002067545A2 (en) * 2001-02-17 2002-08-29 Inktomi Corporation Content based billing
KR20030020928A (ko) * 2001-05-14 2003-03-10 가부시키가이샤 엔티티 도코모 이동 통신 서비스 과금 장치 및 이동 통신 서비스 과금방법
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
JP4009136B2 (ja) * 2001-06-07 2007-11-14 富士通株式会社 課金システム
JP3553918B2 (ja) * 2001-11-14 2004-08-11 日本電信電話株式会社 エッジルータ装置及びネットワーク管理システムとそのプログラム並びにネットワーク管理方法
US20030125013A1 (en) * 2001-12-28 2003-07-03 Mizell Jerry L. Method, network and node for levying a tariff against an originator of a data transfer in a telecommunication network
US8606704B2 (en) * 2002-02-08 2013-12-10 Apple Inc. Customer billing in a communications network
US20030152039A1 (en) * 2002-02-08 2003-08-14 Timothy Roberts Customer billing in a communications network
CN1214555C (zh) * 2002-04-15 2005-08-10 华为技术有限公司 公共陆地移动网（plmn）分组网中统一管理资源的一种方法
US20030200313A1 (en) * 2002-04-17 2003-10-23 General Instrument Corporation Digital rights management system for clients with low level security
SE0201315L (sv) * 2002-04-30 2003-10-31 Ericsson Telefon Ab L M En metod och system för tariffberäkning i ett debiteringssystem
US7184530B2 (en) * 2002-07-25 2007-02-27 Utstarcom, Inc. Prepaid billing support for simultaneous communication sessions in data networks
CN1241355C (zh) * 2002-08-02 2006-02-08 华为技术有限公司 一种在智能网上实现主被叫付费业务的方法
US7203301B1 (en) * 2002-08-12 2007-04-10 Evercom Systems, Inc. System and method for call treatment
AU2002334297A1 (en) * 2002-09-20 2004-05-04 Nokia Corporation Method for charging of data reaching a network element of a communication network during a data session
US7831247B2 (en) * 2002-11-12 2010-11-09 Nokia Corporation Method of communication and communication system
US6954631B2 (en) * 2003-02-13 2005-10-11 Hewlett-Packard Development Company, L.P. Apparatus and method for telecommunications services
US7721296B2 (en) * 2003-06-13 2010-05-18 Ericsson Ab Event based charging in a communications system
EP1517469A1 (de) * 2003-09-18 2005-03-23 Comptel Corporation Verfahren, Vorrichtung und Computerprogrammprodukt zur Online-Abrechnung in einem Kommunikationsnetz
GB0329502D0 (en) * 2003-12-19 2004-01-28 Nokia Corp Control decisions in a communication system
US7792086B2 (en) * 2003-12-23 2010-09-07 Redknee Inc. Method for implementing an intelligent content rating middleware platform and gateway system
CN1303781C (zh) 2004-04-01 2007-03-07 华为技术有限公司 一种分组数据业务的计费控制方法
CN1275422C (zh) * 2004-04-09 2006-09-13 华为技术有限公司 一种分组数据业务中增强计费规则及进行操作的方法
CN100387093C (zh) * 2004-04-30 2008-05-07 华为技术有限公司 一种实现漫游计费的方法及系统
CN100479369C (zh) * 2004-05-12 2009-04-15 华为技术有限公司 一种针对用户选择计费规则的方法
CN1302636C (zh) * 2004-05-12 2007-02-28 华为技术有限公司 一种完善基于业务数据流在线计费的处理方法
CN1277371C (zh) * 2004-08-06 2006-09-27 华为技术有限公司 一种基于分组数据流计费重鉴权的处理方法
CN100474810C (zh) * 2004-08-10 2009-04-01 华为技术有限公司 一种基于业务数据流的承载计费信息收集方法
CN1319317C (zh) * 2004-08-11 2007-05-30 华为技术有限公司 一种基于分组数据流计费的对话建立方法
CN1260910C (zh) * 2004-08-11 2006-06-21 华为技术有限公司 基于分组数据流计费触发事件和重授权事件的处理方法
CN1327652C (zh) * 2004-11-08 2007-07-18 华为技术有限公司 一种在线计费的处理方法
ES2458295T3 (es) * 2004-11-10 2014-04-30 Telefonaktiebolaget Lm Ericsson (Publ) Disposición, nodos y método en relación con acceso a servicios sobre un sistema de comunicación
US7266116B2 (en) * 2004-12-13 2007-09-04 Skylead Assets Limited HTTP extension header for metering information
WO2006075042A1 (en) 2005-01-11 2006-07-20 Nokia Corporation Method for indicating and detecting transmission resource allocations in a multi-user communication system

Also Published As

Publication number Publication date
US8009573B2 (en) 2011-08-30
DE602005012935D1 (de) 2009-04-09
JP2007529925A (ja) 2007-10-25
EP1732264B8 (de) 2009-08-26
US20110280192A1 (en) 2011-11-17
EP1732264A1 (de) 2006-12-13
ATE424068T1 (de) 2009-03-15
EP1732264A4 (de) 2007-03-28
US20120033560A1 (en) 2012-02-09
CN1303781C (zh) 2007-03-07
CN1645805A (zh) 2005-07-27
US20070060101A1 (en) 2007-03-15
JP2010213302A (ja) 2010-09-24
WO2005096547A1 (fr) 2005-10-13
JP5190085B2 (ja) 2013-04-24
US8531971B2 (en) 2013-09-10

Similar Documents

Publication Publication Date Title
EP1732264B1 (de) Verfahren zur Steuerung der Gebührenberechnung des Paketdatendienstes
JP4891223B2 (ja) パケットデータサービスの課金ルールを強化する方法及びその機能する方法
US8798575B2 (en) Method for improving service data flow based charging and system thereof
EP1760932A1 (de) Verfahren zur bearbeitung von online-vergebührung
US8605585B2 (en) Method for establishing diameter session for packet flow based charging
EP1804419B1 (de) Verfahren zur verarbeitung der neuautorisation auf der basis der abrechnung des paketdatenflusses
CA2540922C (en) A method for handling event triggers and re-authorization triggers in flow based charging
WO2005101734A1 (fr) Procede de facturation de services de donnees par paquets et de controle d&#39;acces de flux de donnees de services
WO2006060964A1 (fr) Systeme et procede de traitement permettant une facturation en fonction du flux de paquets de donnees
WO2006015543A1 (en) A processing method for re-authorization and re-authorization event and event triggers
CN100397821C (zh) 一种基于分组数据流计费中的处理方法
CN101159567A (zh) 一种基于分组数据流计费中的处理方法
WO2006050670A1 (fr) Procede de traitement de cle de taxation
CN100362794C (zh) 一种基于业务数据流在线计费的信用控制方法

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

17P Request for examination filed

Effective date: 20060811

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IS IT LI LT LU MC NL PL PT RO SE SI SK TR

RIC1 Information provided on ipc code assigned before grant

Ipc: H04L 12/14 20060101AFI20051017BHEP

A4 Supplementary search report drawn up and despatched

Effective date: 20070222

17Q First examination report despatched

Effective date: 20070511

DAX Request for extension of the european patent (deleted)
GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

RTI1 Title (correction)

Free format text: A METHOD FOR CONTROLLING THE CHARCHING OF THE PACKET DATA SERVICE

GRAS Grant fee paid

Free format text: ORIGINAL CODE: EPIDOSNIGR3

GRAA (expected) grant

Free format text: ORIGINAL CODE: 0009210

AK Designated contracting states

Kind code of ref document: B1

Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IS IT LI LT LU MC NL PL PT RO SE SI SK TR

REG Reference to a national code

Ref country code: GB

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: CH

Ref legal event code: EP

REG Reference to a national code

Ref country code: IE

Ref legal event code: FG4D

REF Corresponds to:

Ref document number: 602005012935

Country of ref document: DE

Date of ref document: 20090409

Kind code of ref document: P

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: LT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20090225

Ref country code: SI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20090225

Ref country code: FI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20090225

RTI2 Title (correction)

Free format text: A METHOD FOR CONTROLLING THE CHARGING OF THE PACKET DATA SERVICE

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: IS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20090625

Ref country code: SE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20090525

Ref country code: AT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20090225

Ref country code: PL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20090225

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: BE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20090225

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: DK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20090225

Ref country code: CZ

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20090225

Ref country code: EE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20090225

Ref country code: ES

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20090605

Ref country code: PT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20090812

Ref country code: MC

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20090331

REG Reference to a national code

Ref country code: CH

Ref legal event code: PL

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20090225

Ref country code: RO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20090225

PLBE No opposition filed within time limit

Free format text: ORIGINAL CODE: 0009261

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: NO OPPOSITION FILED WITHIN TIME LIMIT

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: IE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20090328

Ref country code: CH

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20090331

Ref country code: BG

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20090525

Ref country code: LI

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20090331

26N No opposition filed

Effective date: 20091126

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: GR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20090526

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: IT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20090225

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: LU

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20090328

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: HU

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20090826

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: TR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20090225

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: CY

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20090225

REG Reference to a national code

Ref country code: FR

Ref legal event code: PLFP

Year of fee payment: 12

REG Reference to a national code

Ref country code: FR

Ref legal event code: PLFP

Year of fee payment: 13

REG Reference to a national code

Ref country code: FR

Ref legal event code: PLFP

Year of fee payment: 14

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: FR

Payment date: 20230208

Year of fee payment: 19

P01 Opt-out of the competence of the unified patent court (upc) registered

Effective date: 20230514

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: NL

Payment date: 20240214

Year of fee payment: 20

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: DE

Payment date: 20240130

Year of fee payment: 20

Ref country code: GB

Payment date: 20240208

Year of fee payment: 20