Source: https://patents.google.com/patent/US7725097?oq=6%2C600%2C481
Timestamp: 2018-04-20 17:32:23
Document Index: 23118151

Matched Legal Cases: ['art\n04', 'Application No. 2', 'Application No. 01985456', 'Application No. 06076820', 'Application No. 7016009', 'Application No. 7016009', 'Application No. 7008499', 'Application No. 2003']

US7725097B2 - Charging in a communication system - Google Patents
US7725097B2
US7725097B2 US11396537 US39653706A US7725097B2 US 7725097 B2 US7725097 B2 US 7725097B2 US 11396537 US11396537 US 11396537 US 39653706 A US39653706 A US 39653706A US 7725097 B2 US7725097 B2 US 7725097B2
US11396537
US20060234674A1 (en )
Juha Vallinen
Merja Hopeaharju
A method and system for charging for services in a communication system comprises a charging entity and at least two connection support entities for providing resources to support a connection in the communication system. Various steps include detecting initiation of a connection by the connection support entities; generating a charging identity for identifying the connection; determining a first charge for supporting the connection by the first connection support entity; determining a second charge for the support of the connection by the second connection support entity; transmitting a first charging message from the first connection support entity to the charging entity, the message specifying the first charge and including the charging identity; and transmitting a second charging message from the second connection support entity to the charging entity, the second charging message specifying the second charge and including the charging identity.
This application is a Continuation of U.S. Ser. No. 10/450,609, filed on Nov. 24, 2003, which is a national stage of PCT/IB01/02815, filed on Dec. 30, 2001. The subject matter of these earlier filed applications is hereby incorporated by reference.
Pre-paid communication accounts are becoming increasingly popular. Under a pre-paid account scheme a user pays in advance for communication services. As the user makes use of services the charges for those services are deducted from the balance of the user's account until the balance has diminished to zero. Then the network blocks the usage of services by the user until the account has been topped up. Pre-paid services have the advantage that the network operator does not need to trust the user to pay in arrears for services. However, in order to successfully implement a pre-paid system the operator's network must be able to stop the user using services when the balance of his account falls to zero. In the basic communication system described above this can be achieved simply by the network estimating the charge for a call whilst it is in progress, comparing that charge with the remaining balance of the pre-paid account that is to be charged for the call and terminating the call if the charge exceeds the remaining balance.
The step of generating the charging identity is preferably performed by one of the first and second connection support entities. There is preferably a step of transmitting the charging identity from the said one of the first and second connection support entities to the other of the connection support entitles. Preferably each of the first and second connection support entities maintains a count of the charging identities it has generated, and the charging identity is formed by combining the unique identity of the entity that generates the charging identity and the next number in the count maintained by that entity.
Preferably a charging unit of the system compares the said estimate with a pre-paid balance of an account of the user who initiated the connection and if the balance is insufficient terminates the connection. The balance is suitably deemed to be insufficient if it does not exceed the estimate by a predetermined amount. The predetermined amount may be zero.
FIG. 1 depicts the architecture of an all-IP (internet protocol) UMTS communication system. Boxes and ellipses in FIG. 1 indicate network elements, which are annotated by their standard abbreviations. The network elements are connected by interfaces indicated by lines, whose types are indicated by their standard abbreviations next to the lines. Network elements whose abbreviations carry the suffix “*)” in FIG. 1 are duplicated in the figure for ease of layout, but belong to the same logical element in the UMTS reference model.
1. The applications and services unit 5 (SCP or otherwise): for example to make a charge to a user for the use of a supplementary or value-added service (e.g. call forwarding, call transfer or recommendation of a restaurant local to the user).
2. The access network (the SGSN 6 or GGSN 7): for provision to the user of access for his terminal to the UMTS network.
3. The multimedia IP network (4 a): for provision of access to that network and/or for access to specific data from the network and optionally for guarantees of quality of service on the network.
4. Legacy networks such as legacy mobile communication network 4 b and legacy PSTN network 4 c: for provision of access to those networks.
5. Core network (CPS—a physical element which includes the CSCF and optionally the MGCF too): for use of the UMTS core network for transfer of data.
Record Type BI CPS transaction type
Local Record BI Consecutive record number created by
Sequence this node. The number is allocated
Number sequentially including all CDR types.
Charging ID BI PDP context identifier used to identify
Record Length BI Length of the record
User ID BI Served party LN/MSISDN
User IMSI BI Served party IMSI
Cause for BI The reason for the release of record
Record Closing from this CPS.
Record Sequence BI Partial record sequence number in this
Number CPS. Only present in case of partial
Partial Indicator BI Identify the type of partial record (last)
CPS address BI The IP address of the CPS
Originating NE UIO The address of originating side
Address network element
Connected ID UIT Connected party LN/MSISDN
Terminating NE UIT The address of terminating side
Access Time TI Time stamp when PDP context
Opening time TI Record opening time.
Closing Time TI Record closing time.
Duration TI Duration of this record in the CPS.
Uplink Data TDI Amount of transferred data (uplink)
Downlink Data TDI Amount of transferred data (downlink)
QoS TDI Quality of Service required/accepted
Shared Charging CI Type of shared charging. If not used
value is “Normal Charging”
Shared CI Amount of fee charged from subscriber
Percentage “User ID”
Received Pulses Pulses received from network
Local BI Consecutive record number created by
Record Sequence this node. The number is allocated
Served Time SI Service usage time
Service Code SI Used service
Examples of record types
01 IP originated transaction (GPRS or other CPS)
02 IP terminated transaction (GPRS or other CPS)
03 PSTN originated transaction (Including GSM)
04 PSTN terminated transaction (Including GSM)
05 Camel originated transaction
06 Camel terminated transaction
07 FORW (For forwarding subscriber)
08 ROAM (For roaming subscriber)
09 Service CDR (SE-CDR)
Amount of fee charged from user identified in field “User ID”
BI Basic information
UIO User information originating - information relating
to the user that originated the connection
UIT User information terminating - information relating
to the user that terminated the connection
TI Time information - information relating to the time
and temporal duration of the connection
TDI Transferred data information - information relating to
the amount of data transferred during the connection
CI Charging information - information relating to
the charging structure for the connection
SI Service information - information relating to the
service(s) used in the connection
Other CEDRs may be formed in a like way to those described above.
Once a global charging ID has been generated in relation to a call that same global charging ID is used by all the entities that generate charges for the call, being included as the charging ID field of each of their CDRs for the call. To allow this to happen the first unit to generate a CDR or to begin charging for a call—i.e. the unit that generated the charging ID or requested it from the server—causes the charging ID to be made available to the other entities that may need to generate CDRs for the call. This is preferably done by transfer of the charging ID over the protocols used between the entities, for example the SIP and GTP protocols in UMTS. This may require the addition of an element to such protocols as they are presently formed, including the protocols that are used for communication with legacy networks such as GSM networks that may also need to generate CDRs. However, support for this feature allows the unit that generates or first acquires the charging ID pushes it to the other entities that may need to generate CDRs for the call.
When a call is to be made from TE 20 via the GPRS system to a terminal of the PSTN 23 the call first reaches the GPRS system (step 30), which recognises that it has no global charging ID for the call and therefore generates one according to the method described above (step 31). In passing the call to the core network of the UMTS system the GPRS system passes the global charging ID it has generated for the call (step 32). In passing the call to the PSTN the core network of the UMTS system passes the global charging ID it has received for the call (step 33). When the call is complete the entities that need to generate charges for the call each generate CDRs that include the global charging ID of the call. These are sent to a central point, preferably the charging entity of the home network of the user of the TE 20, where that user's account is homed. In this example that is assumed to be the UMTS network. Therefore, the entities 21 and 23 generate CDRs (steps 34, 35) and send them to the unit 22 (steps 36, 37). The unit 22 sends those CDRs when it receives them to the charging entity 24 (step 38). The unit 22 also generates a CDR itself, which it sends to the charging entity 24. Even if the CORs arrive at the charging entity 24 at different times the charging entity can match them up because they include the same global charging ID.
The elements of the network that generate charges and that modify or use charging information support the transfer of charging information elements (CIEs). CIEs describe the basis that is to be used for charging of a call and the information they carry allows the total or itemised charge for a call to be estimated whilst the call is in progress and before CDRs have been generated. Information in a CIE has two general purposes: providing a user with advice of charge (mobile charging part—MCP) and providing network elements with a specification of how charges are to be levied (network charging part—NCP). Different CIEs may be used for these purposes, but for simplicity and compatibility preferably a unified form of CIE is used.
Field description NCP ? MCP ?
Tariff currency (ETSI ISUP) - used as described in Yes Yes
Units per time interval - defines how many currency Yes Yes
units are charged per time interval defined
in the time interval field
Time interval - defines the time interval used as the Yes Yes
Switchover time (ETSI ISUP) - used as described in Yes
Shared charging information - describes the type of fee Yes
Shared charging percentage - describes the Yes
percentage that the service provider is willing
to pay according to the shared
charging information field
Call attempt charge (ETSI ISUP) - used as described in Yes
Call set-up charge (ETSI ISUP) - used as described in Yes
Quality of service - describes the quality of service Yes
Global charging ID - indicates the unique Yes
reference described above
Pre-paid information - indicates a pre-paid Yes
threshold value for the subscriber, which
could be network-dependent
Since the charging entity for the user's home network can, using the CIEs, estimate the total charges that will be levied for a call the CIEs provide a means whereby pre-paid accounts may be supported under a charging structure of the type described herein. If the user who originated the call has a pre-paid account then the operator with whom the user has his account will wish to terminate a call whilst it is in progress if it would otherwise result in the user's account having no remaining credit.
As a call progresses the charging entity periodically estimates the charge for the call so far using the CIEs received for the call. This may be done, for example, every second or every five seconds, depending on the load on the charging entity. The charging entity compares that estimated charge with the balance of the account to which the call will be charged. The operator causes the call to be ended if the estimated charge exceeds the balance, or—to take account of potential errors in the estimation—if the estimated charge is not greater than the balance by a predetermined threshold. To do this the charging entity should have knowledge of or should be able to estimate the call-dependant factors, such as the duration of the call or the amount of data transferred during the call, that may have an impact on the charge. These may be transmitted periodically to the entity by at least one of the entities involved in carrying the call, for example unit 22 in FIG. 2. Alternatively, they may be estimated by the charging entity from a knowledge of the time when the call began (e.g. approximately the time at which the CIEs for the call were received by the charging entity), the present time, and (if needed) an average data transmission rate. The duration of the call may be estimated by subtracting the time at which the call began from the present time. The amount of data transmitted may be estimated by multiplying the duration of the call by the expected data rate.
00 Normal charging - Charges not shared. Used when the user of
the terminating part is not to bear any of the cost of the call.
The originating subscriber is charged for the full cost
01 Network access fee - Indicates that the user of the terminating
part will bear part or all of the network access charge.
02 Transferred data towards used service - Indicates that the user
03 Used service - Indicates that the user of the terminating part
04 CallControl and MobilityManagement - Indicates that the
user of the terminating part will bear part
or all of the charge due to call routing and mobility
management (due to the CallProcessing server).
05 Total cost of transaction excluding other services' fees -
06 Total cost of transaction - Indicates that the user of the
1. The order in which they were received by that charging entity.
2. Calculating the fee from the original cost. When the remaining part of the corresponding charge is zero then further shared charging indications are deemed invalid.
If more than one CIE for a call indicates a different shared charging value then they are settled by the charging entity of the originating party according to the following priority:
1. Charging types 01 to 04 as indicated above are handled first.
2. Charging type 05 as indicated above is handled thereafter.
3. Charging type 06 as indicated above is handled thereafter.
FIG. 3 illustrates an example of shared charging in action. In the scenario illustrated in FIG. 3 a subscriber A of mobile terminal/user equipment (MT/UE) 40 accesses a UMTS MIPT (mobile internet protocol telephony) network via a GPRS network. Subscriber A has activated services which are handled by the SCP 41 of the MIPT network. SCP 41 includes the user's charging entity. The user also uses other internet-related services from multimedia IP network 44 before the actual call is routed and connected to the PSTN 42 that is its destination. The PSTN leads to the service number of the terminating terminal part (not shown in FIG. 3).
receiving at a communications network charging entity a charging identity identifying a connection initiated by a communication terminal, the connection being supported by a first connection support entity and a second connection support entity;
receiving at the communications network charging entity a first charging message from the first connection support entity, the first charging message specifying a first tariff and including the charging identity;
receiving at the communications network charging entity a second charging message from the second connection support entity, the second charging message specifying a second tariff and including the charging identity;
storing in the communications network charging entity the first tariff and the second tariff;
the communications network charging entity performing the steps of
determining according to the first stored tariff a first charge for the support of the connection by the first connection support entity;
determining according to the second stored tariff a second charge for the support of the connection by the second connection support entity; and
periodically estimating a charge for the connection according to the first and second charges and comparing the estimated charge with the balance of an account to which the connection is to be charged; and
dividing a total estimate charge into at least two portions and comparing one of those portions to a first account and the second of those portions to a second account.
2. The method as claimed in claim 1, wherein at least one of the first and second charges is determined based on the duration of the connection.
3. The method as claimed in claim 1, wherein at least one of the first and second charges is determined based on the amount of data transmitted during the connection.
4. The method as claimed in claim 3, wherein the connection supports the carrying of data in packet form and at least one of the first and second charges is determined based on the number of packets transmitted during the connection.
5. The method as claimed in claim 1, wherein at least one of the first and second charges is of a fixed value.
6. The method as claimed in claim 1, wherein each of the first and second connection support entities has a unique identity.
7. The method as claimed in claim 6, wherein each of the connection support entities maintains a count of the charging identities it has generated, and the charging identity is formed by combining the unique identity of the entity that generates the charging identity and a next sequential number in the count maintained by that entity.
transmitting from the first connection support entity to the communications network charging entity the unique identity of the first connection support entity; and
transmitting from the second connection support entity to the communications network charging entity the unique identity of the second connection support entity.
9. The method as claimed in claim 1, comprising the step of transmitting the charging identity from the first connection support entity to the second connection support entity.
10. The method as claimed in claim 1, wherein the first account is associated with a terminal that initiated the connection.
11. The method as claimed in claim 10, wherein the second account is associated with another terminal to which the terminal that initiated the connection has been connected by means of the connection.
12. The method as claimed in claim 10, wherein the second account is unassociated with another terminal to which the terminal that initiated the connection has been connected by means of the connection.
13. The method of claim 1, wherein the first connection support entity is operated by a first system operator and the second connection support entity is operated by a second system operator different from the first system operator.
at a connection support entity in a communication system, detecting initiation of a connection with a communication terminal;
generating at the connection support entity a unique charging identity for identifying the connection to another connection support entity located in a different network and to a communications network charging entity, wherein the unique charging identity is also assigned for use by the another connection support entity in forming a combined charge for the connection;
making available the charging identity to the another connection support entity and to the communications network charging entity;
determining according to a tariff stored in the connection support entity a charge for supporting the connection by the connection support entity;
transmitting a charging message to the communications network charging entity, the charging message specifying the charge and including the charging identity; and
periodically estimating a charge for the connection according to a first charge received from the connection support entity and a second charge received from the another connection support entity and comparing the estimated charge with a balance of an account.
15. The method as claimed in claim 14, wherein the charge is determined based on the duration of the connection.
16. The method as claimed in claim 14, wherein the charge is determined based on the amount of data transmitted during the connection.
17. The method as claimed in claim 16, wherein the connection supports a carrying of data in packet form and the charge is determined based on the number of packets transmitted during the connection.
18. The method as claimed in claim 14, wherein the charge is of a fixed value.
19. The method as claimed in claim 14, wherein the connection support entity has a unique identity.
20. The method as claimed in claim 19, further comprising maintaining in the connection support entity a count of the charging identities it has generated, and the charging identity is formed by combining the unique identity of the connection support entity and a next sequential number in the count.
21. The method as claimed in claim 14, further comprising transmitting the charging identity from the connection support entity to the another connection support entity.
22. The method of claim 14, wherein the first connection support entity corresponds to a first operator network and the second connection support entity corresponds to a second operator network different from the first operator network.
at a communications network charging entity, receiving a charging identity from a first connection support entity that identifies a connection to a communication terminal, the connection supported by the first connection support entity and a second connection support entity;
receiving a first charging message from the first connection support entity, the message specifying a first charge and including the charging identity;
receiving a second charging message from the second connection support entity, the second charging message specifying a second charge and including the charging identity;
adding the first and second charging messages to a transaction to form a total value for the transaction;
debiting the total value of the transaction from an account indicated in the first or second charging message;
periodically estimating a charge for the connection according to the first and second charges and comparing the estimated charge with the balance of the account.
24. The method as claimed in claim 23, wherein the communications network charging entity receives from the first connection support entity the unique identity of the first connection support entity and from the second connection support entity the unique identity of the second support entity.
25. The method of claim 23, wherein the first connection support entity corresponds to a first operator network and the second connection support entity corresponds to a second operator network different from the first operator network.
a charging entity configured to operate in a communication system and to receive a charging identity identifying a connection initiated by a communication terminal, the connection being supported by a first connection support entity and a second connection support entity;
the charging entity configured to receive a first charging message from the first connection support entity, the first charging message specifying a first tariff and including the charging identity;
the charging entity configured to receive a second charging message from the second connection support entity, the second charging message specifying a second tariff and including the charging identity;
the charging entity configured to store the first tariff and the second tariff and configured to determine according to the first stored tariff a first charge for the support of the connection by the first connection support entity, determine according to the second stored tariff a second charge for the support of the connection by the second connection support entity; and
periodically estimate a charge for the connection according to the first and second charges and comparing the estimated charge with a balance of an account to which the connection is to be charged;
the charging entity configured to divide a total estimate charge into at least two portions and comparing one of those portions to a first account and the second of those portions to a second account.
US11396537 2000-12-22 2006-04-04 Charging in a communication system Active 2024-08-25 US7725097B2 (en)
GB0031459.1 2000-12-22
GB0031459A GB0031459D0 (en) 2000-12-22 2000-12-22 Charging in a communication system
US10450609 US7058165B2 (en) 2000-12-22 2001-12-20 Charging in a communication system
PCT/IB2001/002815 WO2002052833A3 (en) 2000-12-22 2001-12-20 Method and system for charging in communication systems
US11396537 US7725097B2 (en) 2000-12-22 2006-04-04 Charging in a communication system
US10450609 Continuation
US10450609 Continuation US7058165B2 (en) 2000-12-22 2001-12-20 Charging in a communication system
PCT/IB2001/002815 Continuation WO2002052833A3 (en) 2000-12-22 2001-12-20 Method and system for charging in communication systems
US20060234674A1 true US20060234674A1 (en) 2006-10-19
US7725097B2 true US7725097B2 (en) 2010-05-25
ID=9905744
US10450609 Active US7058165B2 (en) 2000-12-22 2001-12-20 Charging in a communication system
US11396537 Active 2024-08-25 US7725097B2 (en) 2000-12-22 2006-04-04 Charging in a communication system
US (2) US7058165B2 (en)
EP (3) EP1771030B1 (en)
JP (1) JP2004517526A (en)
KR (2) KR100932599B1 (en)
CN (1) CN1262140C (en)
CA (1) CA2432551C (en)
GB (1) GB0031459D0 (en)
WO (1) WO2002052833A3 (en)
EP1532804B1 (en) * 2002-06-28 2014-08-20 Nokia Corporation Charging for an ip based communication system
US20050268328A1 (en) * 2002-07-03 2005-12-01 Gabriele Corliano Trust establishment for multi-party communications
CN1249965C (en) * 2002-11-12 2006-04-05 华为技术有限公司 Method for forwarding multimedia message among different multimedia message centers
GB0311004D0 (en) * 2003-05-13 2003-06-18 Nokia Corp Charging in communication networks
CN100433624C (en) 2004-03-24 2008-11-12 华为技术有限公司 Method for realizing communication business payment metering
CN1303781C (en) * 2004-04-01 2007-03-07 华为技术有限公司 Accounting and controlling method for grouped data service
GB0414662D0 (en) * 2004-06-30 2004-08-04 Nokia Corp Charging in a communication system
KR100707441B1 (en) * 2005-03-08 2007-04-13 엘지전자 주식회사 Network Converting Mobile Communication System and the Converting Method for the Same
KR100726617B1 (en) * 2005-11-23 2007-06-11 에스케이 텔레콤주식회사 Method and system for operating billing policy
KR100794416B1 (en) * 2006-04-13 2008-01-16 포스데이타 주식회사 Method of obtaining the packet charge data for the voice over internet protocol call using session initiation protocol
DE102006028088A1 (en) * 2006-06-19 2008-03-27 Nokia Siemens Networks Gmbh & Co.Kg Call set up attempt fee charging method for e.g. fixed network, involves receiving answer on notification to implement solvency test, where answer displays attempt status, and accomplishing fee charging of attempt after status evaluation
US7970930B2 (en) * 2007-06-05 2011-06-28 Ellacoya Networks, Inc. Communications system and method to control and manage both session-based and non-session-based application services
WO2010014088A1 (en) * 2008-07-30 2010-02-04 Lucent Technologies Inc. Online charging for sessions that are transferred between network domains
JP5016582B2 (en) * 2008-10-28 2012-09-05 日本電信電話株式会社 Communication system, charging apparatus, and program
US8620262B2 (en) * 2009-01-21 2013-12-31 Alcatel Lucent Advice of charging (AoC) services in IMS networks
CN101645782B (en) * 2009-02-10 2012-05-23 中国科学院声学研究所 Online billing method and system based on user traffic volume
CN103814583A (en) * 2011-09-20 2014-05-21 阿尔卡特朗讯 Method of implementing master service control function for facilitating enhanced inter carrier value added services
CN105247903A (en) * 2013-05-07 2016-01-13 诺基亚技术有限公司 Method and apparatus for dynamic charging over multiple network nodes
US6173171B2 (en) *
EP0483091A2 (en) 1990-10-26 1992-04-29 Ericsson Inc. Toll ticketing record generation for billing of intersystem handoff calls in a mobile telephone system
GB2273628A (en) 1992-12-21 1994-06-22 American Telephone & Telegraph Call billing and measurement methods for redirected calls
WO1995022230A2 (en) 1994-02-01 1995-08-17 Telefonaktiebolaget Lm Ericsson A method and a system for identifying call records
WO1998039910A1 (en) 1997-03-07 1998-09-11 At & T Corp. Dynamic split billing of telephone calls
JPH10285304A (en) 1997-04-04 1998-10-23 Casio Comput Co Ltd Telephone system, center equipment of telephone line network, terminal equipment and speech charge split calculation method
WO1999000971A1 (en) 1997-06-30 1999-01-07 Motorola Inc. Method of making a communication interconnection
WO1999033253A1 (en) 1997-12-19 1999-07-01 Telefonaktiebolaget Lm Ericsson Method for transferring information regarding telephony charges, and telephone exchange arranged for such method
WO1999038313A1 (en) 1998-01-26 1999-07-29 E-Plus Mobilfunk Gmbh Method and device for calculating charges in telecommunications networks
US5991375A (en) 1996-04-30 1999-11-23 Alcatel Alsthom Compagnie Generale D'electricite Method of operating a communications network as well as a communications network and an interworking facility
WO2000011859A1 (en) 1998-08-21 2000-03-02 Telefonaktiebolaget L M Ericsson (Publ) Charging in a telecommunications system
US6038439A (en) 1996-09-10 2000-03-14 Telefonaktiebolaget Lm Ericsson Method and device in a telecommunications system
EP1052825A1 (en) 1999-05-03 2000-11-15 Nokia Corporation Sim based authentication as payment method in public isp access networks
WO2000069201A1 (en) 1999-05-06 2000-11-16 Telefonaktiebolaget Lm Ericsson (Publ) Tariff determination in mobile telecommunication networks
WO2000070858A1 (en) 1999-05-12 2000-11-23 Elisa Communications Oyj Method and system for charging value-added calls
KR20010001199A (en) 1999-06-02 2001-01-05 허진호 Internet information billing system
US6307924B1 (en) * 1998-03-28 2001-10-23 Alcatel Method of charging for services, network node, and gateway node
WO2001091445A1 (en) 2000-05-25 2001-11-29 Nokia Corporation Arranging subscriber billing in telecommunication system
US7110760B1 (en) 1999-02-22 2006-09-19 Koninklijke Kpn N.V. Access-point-dependent rate fixing of telecommunication links
JPH09504150A (en) 1994-02-01 1997-04-22 テレフオンアクチーボラゲツト エル エム エリクソン Linked record
KR20000071580A (en) 1999-04-07 2000-11-25 요트.게.아. 롤페즈 Terminal, telecommunications system and connection method
3rd Generation Partnership Project 2 "3GPP2", Version 1, dated Jul. 14, 2000-TIA/EIA-41D Pre-Paid Charging Revision: 1 Copyright.
3rd Generation Partnership Project 2 "3GPP2", Version 1, dated Jul. 14, 2000—TIA/EIA-41D Pre-Paid Charging Revision: 1 Copyright.
Canadian Office Action dated Oct. 7, 2008 for Canadian Patent Application No. 2,432,551.
EPO Examination Report in European Patent Application No. 01985456.1-2412, dated May 5, 2008. (Note: For the citation to documents D1-D5, refer to the IDS filed in this U.S. Appl. No. 11/396,537 on Apr. 30, 2008, Cite No. NP3 (EPO Examination Report, Dec. 13, 2006)).
EPO Examination Report in European Patent Application No. 06076820.7-2412, dated Oct. 25, 2007.
EPO Examination Report, Dec. 13, 2006.
EPO Examination Report, Mar. 28, 2006.
Korean Office Action dated Oct. 14, 2008 with English translation, Transmittal No. 9-5-2008-052634419, for Korean Application No. 7016009/2008.
Korean Office Action transmittal No. 9-5-2008-052634419, dated Oct. 14, 2008 for Korean Divisional Patent Application No. 7016009/2008.
Korean Office Action transmittal No. 9-5-2008-060816533, dated Nov. 29, 2008 for Korean Patent Application No. 7008499/2003.
Korean Office Action transmittal No. 9-5-2009-045763291, dated Nov. 5, 2009 for Korean Patent Application No. 2003-7008499.
PCT International Preliminary Examination Report, Mar. 28, 2003.
PCT Written Opinion, Nov. 28, 2002.
US20060234674A1 (en) 2006-10-19 application
EP1771030A1 (en) 2007-04-04 application
EP1744584A1 (en) 2007-01-17 application
KR100932599B1 (en) 2009-12-17 grant
GB0031459D0 (en) 2001-02-07 grant
WO2002052833A2 (en) 2002-07-04 application
US20040101117A1 (en) 2004-05-27 application
EP1744584B1 (en) 2016-10-12 grant
EP1771030B1 (en) 2016-05-04 grant
CA2432551A1 (en) 2002-07-04 application
EP1344422A2 (en) 2003-09-17 application
CN1262140C (en) 2006-06-28 grant
WO2002052833A3 (en) 2002-11-21 application
CA2432551C (en) 2012-03-06 grant
CN1531831A (en) 2004-09-22 application
KR20080069277A (en) 2008-07-25 application
US7058165B2 (en) 2006-06-06 grant
JP2004517526A (en) 2004-06-10 application
KR20040007430A (en) 2004-01-24 application
KR100945351B1 (en) 2010-03-08 grant
US20030031160A1 (en) 2003-02-13 Implementing an intelligent network service for a packet-switched service using a node interfacing a mobile communications network to a packet data network
US20040266394A1 (en) 2004-12-30 Method for extending content aware accounting to a serving GPRS node
US20060114932A1 (en) 2006-06-01 IMS gateway systems and methods for online charging in IMS networks
US20020106064A1 (en) 2002-08-08 Controlling setup or continuation of a call charged from a pre-paid group account
US6856674B1 (en) 2005-02-15 Platform for prepaid calling card calls
US6952575B1 (en) 2005-10-04 Prepaid call management in intelligent network