EP1665630A1 - Procede de taxation et unites de taxation - Google Patents

Procede de taxation et unites de taxation

Info

Publication number
EP1665630A1
EP1665630A1 EP04766566A EP04766566A EP1665630A1 EP 1665630 A1 EP1665630 A1 EP 1665630A1 EP 04766566 A EP04766566 A EP 04766566A EP 04766566 A EP04766566 A EP 04766566A EP 1665630 A1 EP1665630 A1 EP 1665630A1
Authority
EP
European Patent Office
Prior art keywords
message
authorization
service
data transmission
protocol
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.)
Withdrawn
Application number
EP04766566A
Other languages
German (de)
English (en)
Inventor
Frank Burghardt
Andreas Kanbach
Peter Kim
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.)
Nokia Solutions and Networks GmbH and Co KG
Original Assignee
Siemens AG
Nokia Siemens Networks GmbH and Co KG
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 Siemens AG, Nokia Siemens Networks GmbH and Co KG filed Critical Siemens AG
Publication of EP1665630A1 publication Critical patent/EP1665630A1/fr
Withdrawn legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/83—Notification aspects
    • H04M15/85—Notification aspects characterised by the type of condition triggering a notification
    • 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
    • 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/1453—Methods or systems for payment or settlement of the charges for data transmission involving significant interaction with the data transmission network
    • H04L12/1457—Methods or systems for payment or settlement of the charges for data transmission involving significant interaction with the data transmission network using an account
    • 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/1453—Methods or systems for payment or settlement of the charges for data transmission involving significant interaction with the data transmission network
    • H04L12/1467—Methods or systems for payment or settlement of the charges for data transmission involving significant interaction with the data transmission network involving prepayment
    • 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/83—Notification aspects
    • H04M15/85—Notification aspects characterised by the type of condition triggering a notification
    • H04M15/851—Determined tariff
    • 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/83—Notification aspects
    • H04M15/85—Notification aspects characterised by the type of condition triggering a notification
    • H04M15/853—Calculate maximum communication time or volume
    • 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/83—Notification aspects
    • H04M15/85—Notification aspects characterised by the type of condition triggering a notification
    • H04M15/854—Available credit
    • 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/88—Provision for limiting connection, or expenditure
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M17/00—Prepayment of wireline communication systems, wireless communication systems or telephone systems
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M2215/00—Metering arrangements; Time controlling arrangements; Time indicating arrangements
    • H04M2215/01—Details of billing arrangements
    • H04M2215/0116—Provision for limiting expenditure, e.g. limit on call expenses or account
    • 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/81—Notifying aspects, e.g. notifications or displays to the user
    • H04M2215/815—Notification when a specific condition, service or event is met
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M2215/00—Metering arrangements; Time controlling arrangements; Time indicating arrangements
    • H04M2215/81—Notifying aspects, e.g. notifications or displays to the user
    • H04M2215/815—Notification when a specific condition, service or event is met
    • H04M2215/8162—Calculate maximum communication time or volume

Definitions

  • the invention relates to a method for charging, in which the following method steps are carried out:
  • the data transmission network is in particular a data packet transmission network, in particular the Internet or a 3GPP network (third generation partnership program), in particular a UMTS network (Universal Mobile Telecommunication System).
  • a data packet header In a data packet header, a destination address is saved.
  • the user data is located in a data packet call.
  • a charging procedure is b> spw. in the standards of the 3GPP group (explained in the third generation), which are published, for example, on the Internet at ftp://ftp.3gpp.org/specs/archive, especially in the standards:
  • a suitable protocol is the Diameter Base Protocol, which is an extension of the RADIUS protocol (Remote Authentication Dial In User Service) and is referred to below as the Diameter Protocol.
  • the Diameter protocol is still in de facto standardization and is available as a draft or later as a draft on the website (www.ietf.org) of the IETF (Internet Engineering Task Force). Both protocols are so-called AAA protocols (Authentication, Authorization, Accounting).
  • simply structured charging units should be specified.
  • the invention is based in particular on the following considerations.
  • second generation mobile radio networks ie in particular in the European GSM network (Global System Mobile)
  • authorized mobile radio customers can without a fixed contractual relationship between the mobile radio network operator and the Customers use various services, such as voice services or SMS (Short Massage Service), if the payment of the desired service is guaranteed before the service is carried out.
  • the amount of money can be debited or reserved directly from the customer's credit account.
  • the so-called prepaid customers can monitor the costs at any time.
  • budget control takes place in a different network element than the credit account management.
  • the services offered are either time-based, e.g. with voice telephony, or charged for after events, e.g. with SMS.
  • Parcel services e.g. MMS (Multimedia Message Service) in mobile networks of the 2.5th generation can also be billed according to volume, e.g. in kilobytes.
  • the GPRS (Global iere Radio Service) service is used in particular.
  • 3rd generation mobile phone networks in particular UMTS networks (Universal Mobile Telecommunication Service) are not only designed for voice and variable data streams, but also allow the customer to use multimedia services.
  • the charging for the use of multimedia services is very complex and has not yet been satisfactorily resolved.
  • Various charging models should be available for online charging and offline charging.
  • the time-based charging in third generation mobile radio networks is currently only possible with a very high technical outlay, so that a simple and inexpensive method has to be found.
  • An essential feature of such a procedure should be a monitoring of the allocated budget, ie the credit at the time a service is carried out. This property is also referred to as budget control and can be implemented in various network elements, particularly with the IP (Internet Protocol) multimedia subsystem (IMS).
  • IMS Internet Protocol multimedia subsystem
  • the charging method with charging messages had to be transmitted to the network elements, for example via an address of the Event Charging Function (ECF) contained in the OCS or CCF, which is part of a so-called OCS (Online Charging System).
  • ECF Event Charging Function
  • the method according to the invention enables the selection of the charging method to be left to the OCS or a CCF (Charging Collection Function) for offline charging.
  • the Diameter Protocol is particularly suitable as a suitable protocol for the authorization message and the charging message. So far, however, only the accounting part of this protocol has been used in connection with charging. For example. However, the inclusion of the authorization part in the charging results in numerous advantages. In particular, charging can be stopped from a charging server. The accounting section has not yet offered such a possibility.
  • the authorization part can be embedded in the accounting part.
  • the accounting part for example of the diameter protocol, can be embedded in the authorization part of this protocol.
  • the core network elements involved no longer need to know the charging method.
  • the selection of the charging method is left to the charging function, i.e. for example the OCS or the CCF.
  • the granularity of the reservation vation ie the time or volume interval, can be as small as desired without excessively influencing the network performance.
  • the procedure is independent of the access network, e.g. GPRS, UMTS, Bluetooth, WLAN IEEE 802.11.
  • Diameter Base protocol does not have to - but - can be expanded.
  • the log can be reduced to a few messages.
  • commercially available network nodes can be used for various charging methods.
  • - New charging methods can be introduced easily because only changes in the OCS / CCF are required.
  • an authorization message is used to prepare the charging or when the charging ends.
  • the authorization messages are used both to prepare the charge and to end the authorization.
  • the authorization message contains a user identifier that indicates the user of the data transmission. Depending on the user identifier, the authorization or authorization of the user for data transmission is checked. On the basis of the authorization message and / or depending on the content of the authorization message, a fee type and / or a billing type is also selected.
  • a reservation of a fee amount or a fee time is made on the basis of the authorization message and / or depending on the content of the authorization message. Additionally or alternatively, when editing the authorization message, a Record for the charge is generated. The authorization message is thus used in an unchanged format for additional purposes compared to the previous use.
  • the authorization message is transmitted before the preparation of the data transmission is completed, so that a secure procedure against misuse arises.
  • the authorization message is transmitted after the preparation of the data transmission has been completed, so that user data, e.g. Voice data and / or video data can be transmitted.
  • the authorization message fulfills the requirements of the diameter protocol or a protocol based on it.
  • the authorization message is processed in particular in accordance with the diameter protocol or in accordance with a protocol based on this protocol.
  • the specific structure of the authorization message is not specified in the diameter protocol and depends on the application in question.
  • the authorization message used when terminating is an abort message which leads to the abort of the user data transmission, in particular the abort session request message of the diameter protocol or a protocol based thereon.
  • the service request message contains a user identifier that indicates the user of the data transmission. Depending on the user identifier, the authorization of the user for data transmission is checked, so that no separate authorization message has to be sent for this purpose. In addition, a charging type and / or a billing type is selected in particular in accordance with the actual purpose of the charging message.
  • the charge is an online charge that affects the transmission of user data can.
  • the monitoring of the charge is carried out in a service provider computer which is provided in addition to a service provider computer which controls the data transmission.
  • the same service request messages are transmitted for online charging and for offline charging, in particular messages with the same message identifier.
  • Account request message in accordance with the diameter protocol is preferably used, the same account record type preferably being used in both messages, in particular an EVENT_RECORD. This creates a simple procedure in which the same messages are used for several charging methods. The method of charging does not have to be known or determined in the tax calculator.
  • the invention also relates to a server billing unit and a client billing unit, in particular with units for carrying out the method steps of the method according to the invention or one of its developments.
  • the technical effects mentioned above also apply to the fee units.
  • FIG. 1 shows functional units for signaling data transmission and for billing
  • FIG. 2 shows the message flow for a SIP session with online billing, with authorization before the data transmission possibility is set up and with triggering by a terminal
  • FIG. 3 shows the message flow for a SIP -Session online billing, with authorization after setting up the data transmission option and with triggering by a fee calculator
  • FIG. 4 shows part of the message flow of a SIP session online billing, triggered by a control unit for controlling the data transmission
  • FIG. 5 the message flow of a SIP session with offline charging
  • FIG. 6 functional units of a server unit, which is used for charging
  • Figure 7 functional units of a client unit, which is used for charging.
  • FIG. 1 shows functional units of a data transmission network 10 for signaling data transmission and for charging.
  • a terminal 12 is connected via an access network 14.
  • the access network 14 leads via a GPRS unit 16 (Global Packet Radio Service) to an IP multimedia subsystem 18 (IMS).
  • GPRS unit 16 Global Packet Radio Service
  • IMS IP multimedia subsystem 18
  • the GPRS unit contains an SGSN unit 20 (serving GPRS service node) and a GGSN unit (gateway GPRS service node) 22, the functions of which are explained in particular in the 3GPP TS 32.200 standard.
  • the subsystem 18 contains an OCS / CCF unit or an authorization / charging unit 24 and a control unit 26, in particular a P-CSCF (Proxy Call Session Control Function) or an S-CSCF (Serving Call Session Control Function).
  • Subsystem 18 also includes an application server 28, e.g. a video server, an MRF unit (Media Resource Function) or an MRFC unit (Media Resource Function Controller).
  • the budget control function BC 1. the online charging system (OCS) and
  • the diameter base protocol is used between the OCS / CCF and the control unit 26 or the unit 28, as explained below with reference to FIGS. 2 to 5. This means that the standardized interfaces Ro (online) and Rf (offline) are already more similar to one another than originally intended.
  • the messages used in the following scenarios can be represented by the following commands of the Diameter Base protocol:
  • the budget control function BC is positioned on the OCS and the CCF.
  • the authorization protocol of the Diameter protocol is used for the time-based charging of multimedia services.
  • the authorization protocol is used in combination with the accounting protocol (Event__Method).
  • Event__Method the accounting protocol
  • originally independent parts of the Diameter Base protocol are used to charge multimedia services with optional credit reservation, in particular in accordance with the Diameter extension for credit control applications.
  • - Mapping rules for controlling a SIP session using diameter messages are given.
  • FIG. 2 shows the message flow for a SIP session with online billing (prepaid), with authorization before the data transmission option is set up, and with triggering by a terminal. A prepaid fee is explained. The timers for waiting for messages are not shown.
  • prepaid online billing
  • connection control control unit 52 e.g. an S-CSCF
  • the terminal 50 operates according to the SIP protocol and is used to transmit multimedia data (for example audio and video data), in particular voice data, in the data packet transmission network 10, for example on the Internet or in 3GPP networks.
  • the connection control unit 52 also works in accordance with the SIP protocol and serves to control the connection when transmitting data from and to the terminal 50.
  • the terminal 54 is also used for voice transmission or the transmission of multimedia data.
  • an application server 54 can also be used, which also works according to the SIP protocol (RFC3261) and provides a service, for example viewing, buying or renting videos.
  • RCF3261 SIP protocol
  • MRFC multimedia resource function control unit
  • MRF takes the place of the application server 54.
  • the A subscriber wants to set up a connection from his terminal 50 to the B subscriber's terminal 54 in order to make calls.
  • an INVITE message 60 is generated in the terminal 50 and transmitted to the control unit 52.
  • the control unit 52 processes the INVITE message in accordance with the SIP protocol.
  • the control unit 52 sends a SIP INVITE message 61 to the terminal 54.
  • the SIP messages 61, 76, 94 can also be routed to the terminal 54 via a number of control units 52.
  • the control unit 52 sends an authorization request message 62 to the authorization / charging unit 24.
  • the message 62 is in the diameter
  • message 62 contains, inter alia:
  • the INVITE message is therefore 60 trigger point for the authorization or for the preparation of the charge.
  • the message 62 is processed by the authorization / charging unit 24. It is checked whether the A subscriber is authorized, see method step 64. This is the case in the exemplary embodiment. Therefore, the method of charging is determined in a subsequent step 66, e.g. Prepaid. In a method step 68, it is checked whether the A participant's cash balance has a minimum value. In a next method step 70, a minimum sum is reserved, for example, for the "voice telephony" service.
  • An authorization response message 72 is then generated at a time t4, which in the exemplary embodiment includes contains the following data fields or AVPs (Attribute Value Pairs):
  • the message 72 is transmitted from the network element with the authorization / charging unit 24 to the control unit 52 and processed there.
  • the requested service is permitted in accordance with the Diameter Protocol.
  • the INVITE message 61 is processed in the application server 54 in accordance with the SIP protocol and answered with a confirmation message 76 at a time t8.
  • the confirmation message 76 is also referred to as a 200 ⁇ K message.
  • the confirmation message 76 is transmitted from the application server 54 to the control unit 52.
  • the control unit 76 generates at a time after receipt of the confirmation message 76 tlO a confirmation message 78 to the side of the terminal 50 according to the SIP protocol.
  • a SIP session 80 has then been set up between the terminal 50 and the application server 54. Via a UDP (User Datagram Protocol) or RTP connection (Real Time Protocol), i.a. Transfer voice data between the terminals 50 and 54.
  • the user data transmission connection belonging to the SIP session 80 has a call ID (identifier) which has to be correlated with the session ID specified in the message 62.
  • the control unit 52 sends a diameter charge request message 82 to the authorization / charge unit 24 after the establishment of the SIP session 80 or the user data transmission connection (RTP / UDP).
  • the message 82 is also used as accounting -Request message referred.
  • the message 82 contains, among other things: the session identifier or the session ID and the accountign record type Event_Record.
  • the message 82 is processed by the authorization / charging unit 24, a timer for the budget control being started in a method step 84.
  • the authorization / charging unit 24 sends a diameter charging response message 86 to the control unit 52 at a time t14.
  • Message 86 also includes the session ID.
  • the control unit 52 processes the message 86 and permits the transmission of the voice data.
  • subscriber A ends the call, an end message 92 being generated in his terminal 50 and being sent to control unit 52.
  • the control unit 52 uses the message 92 to generate a session end request message 90, which according to the diameter protocol is also used as a session Termination request message (STR) is called and was actually not intended to terminate the charge.
  • STR session Termination request message
  • the message 90 is sent to the authorization / charging unit 24 and is used here to end the charging.
  • the charge timer is stopped and any remaining credit, if any, is credited to the account of subscriber A.
  • control unit 52 At a time t20, the control unit 52 generates an end message 94 in accordance with the SIP protocol.
  • the end message 94 is transmitted to the terminal 54 and processed there in accordance with the SIP protocol.
  • the SIP session or the SIP session is ended in a subsequent method step 96.
  • the authorization / billing unit 24 sends a session end response message 98 at a time t22, which is also called a session
  • Termination Answer Message STA is called and according to the Diameter Protocol only in the context of a de-auto ⁇ stechnik and not as used here in connection with the end of the charge.
  • FIG. 3 shows the message flow for a SIP session online billing (prepaid), with authorization after the data transmission option has been set up, and triggered by a billing computer.
  • prepaid SIP session online billing
  • the A subscriber wants to establish a connection from his terminal 50 to the B subscriber's terminal 54 in order to make calls. For this an INVITE message 150 generated in the terminal 50 and transmitted to the control unit 52.
  • the control unit 52 processes the INVITE message in accordance with the SIP protocol.
  • the control unit 52 sends a SIP INVITE message 152 to the terminal 54.
  • the terminal 54 processes the message 152 in accordance with the SIP protocol and sends a confirmation message 154 at a time t54, which is also referred to as a 200 ⁇ K message.
  • the confirmation message 154 is transmitted from the terminal 54 to the control unit 52.
  • the control unit 52 After receiving the confirmation message 154 at a time t56, the control unit 52 generates a confirmation message 156 for the terminal 50 in accordance with the SIP protocol.
  • a SIP session 80 is then set up between the terminal 50 and the terminal 54. In addition, Transfer voice data between the terminals 50 and 54.
  • the SIP session 80 has a session ID (identifier), which is required below.
  • the control unit 52 sends an authorization request message 162 to the authorization / charging unit 24.
  • the message 162 corresponds to the message 62.
  • this is not an INVITE message but the confirmation message 154 as a trigger point for authorization or for preparations for charging.
  • the message 162 is processed by the authorization / charging unit 24. It is checked whether the A-subscriber is authorized, see procedural step
  • a subsequent step 166 the type of charging is determined, e.g. Prepaid.
  • a check is carried out to determine whether the A participant's cash balance has a minimum value.
  • An authorization response message 172 corresponding to message 72 is then generated at a time t104.
  • the message 172 is transmitted from the network element with the authorization / charging unit 24 to the control unit 52 and processed there.
  • the requested service is permitted in accordance with the Diameter Protocol.
  • the control unit 52 sends a diameter charge request message 182 to the authorization / charge unit 24.
  • the message 182 corresponds to the message 82. Since the messages correspond, they have the same data fields and same functions.
  • the message 182 is processed by the authorization / charging unit 24, a timer for the budget control being started in a method step 184.
  • the authorization / charging unit 24 sends a diameter charging response message 186 to the control unit 52 at a time tll4.
  • Message 186 also includes the session ID.
  • the control unit 52 processes the message 186 and permits the transmission of the voice data.
  • the budget timer expires at a certain point in time, see method step 188. the budget granted to participant A has been used up.
  • the authorization / charging unit 24 then generates a diameter abort session request message 190 at a time tll ⁇ , which is also referred to as an abort session request message (ASR).
  • the message 190 also contains the session ID and is transmitted to the control unit 52.
  • the control unit 52 generates an end message 192 for the terminal 50 based on the message 190 at a time t11 ⁇ according to the SIP protocol.
  • the end message 192 is also referred to as a BYE message.
  • the control unit 52 On the basis of the message 190, the control unit 52 also generates a SIP end message 194 for the terminal 54 at a subsequent time tl20.
  • the receipt of the message 190 is thus the criterion for triggering the SIP session on both sides.
  • the SIP session is ended on the basis of the end messages 192 and 194, see method step 196.
  • the control unit 52 then generates a parameter termination session response message 98 at a time tl22, which is also an abort session answer message (ASA ) referred to as.
  • the message 198 is transmitted to the authorization / charging unit 24 and processed there according to the diameter protocol.
  • Message 198 includes, among other things:
  • the SIP session according to FIG. 2 or according to FIG. 3 is ended.
  • trigger points according to FIG. 1 or FIG. 2 is independent of the charging method or the debiting method, prepaid or postpaid.
  • FIG. 4 shows part of the message flow of a SIP session online billing (prepaid), triggered by a control unit for controlling the data transmission.
  • prepaid SIP session online billing
  • the control unit At a point in time t212 following method step 260 or 280, the control unit generates a message 282 which corresponds to message 82 or 182.
  • the billing time counter timer
  • a message 286 is then generated which corresponds to message 86 or 186.
  • an unexpected SIP session error 285 occurs.
  • the following unexpected SIP session errors are possible, for example: - Operator blocks the A subscriber via the Cx interface, which is provided between the HSS (Home Subscriber Server) and the S-CSCF according to the standard, or - the authentication / is faulty ,
  • control unit 52 sends an SIP end message 292 to the terminal 50 at a time t218 and an SIP end message 294 to the terminal 54 at a time t220.
  • SIP session then ends in a method step 296.
  • a session end request message 290 is sent from the control unit 52 to the authorization / charging unit 24 at a time t221.
  • the message 290 corresponds to the message 90.
  • the authorization / charging unit 24 stops the charging timer or time counter in a method step 291.
  • the authorization / charging unit 24 then sends a session end response message 298, which corresponds to the message 98, to the control unit 52 at a time t222.
  • FIG. 5 shows the message flow of a SIP session with offline charging. Except for the deviations explained below, the same messages are transmitted and processed in the same way as explained above with reference to FIG. 2. Therefore, the same points in time and the same messages are denoted by the same reference symbols, the points in time and messages according to FIG.
  • method step 366 which is carried out instead of method step 66, it is recognized from the user identifier and / or from the service that an offline charge is to be carried out which is billed using a postpaid method.
  • step 370 a fee data record is generated instead of a reservation, which is called S-CSCF CDR (Charging
  • Such a charge data record is explained in more detail, for example, in the 3GPP TS 32.225 standard.
  • step 384 the CDR data record is changed in accordance with message 382. - In step 391, the CDR data record is stored or closed properly.
  • FIG. 6 shows a server unit 400, which performs the functions of the authorization / charging unit 24 and contains the following units:
  • a storage unit 402 a transceiver unit 404 which can receive the authorization messages 62, 162, 262 and 362 and the charging messages 82, 182, 282 and 282,
  • a charging unit 406 which changes a charging date depending on the content of the charging messages 82, 182, 282 and 282, and
  • an authorization unit which carries out the authorization after receipt of the authorization message 62, 162, 262 or 362, see method steps 64, 164, 264 or 364.
  • the server unit 100 also contains further units 410 for carrying out the methods explained above with reference to FIGS. 2 to 5.
  • all units 404 to 410 access memory 402 in order to perform their functions, see arrow 414.
  • the interaction between charging unit 406 and authorization unit 408 is particularly close, in particular when performing method steps 66 to 70,
  • the server unit 400 does not contain a processor that processes a program.
  • Units 404 through 410 contain circuits that are hardwired. In an alternative variant, however, the functions of the units 404 to 410 are performed by a processor 416 when a program stored in the memory 102 is processed.
  • FIG. 7 shows functional units of a client unit 450 which cooperates with the server unit 400 in the methods explained with reference to FIGS. 2 to 5.
  • the client unit 450 includes:
  • a storage unit 452 for storing data records
  • a transceiver 454 for sending messages 62, 162, 262, 362, 82, 182, 282, 382, 90, 290 and 390, and
  • a generation unit 456 which can generate the messages just mentioned.
  • the generation unit 456 accesses the same data record in the storage unit 452 when generating the authorization message and when generating the charging message.
  • the client unit 450 also contains further units 458 in order to provide the functions for the authorization and the charging, in particular a receiving unit for receiving the response messages or the message 190.
  • all units 454 through 458 access memory 452 to perform their functions, see arrow 460.
  • the client unit 450 does not contain a processor that executes a program.
  • Units 454 through 458 include circuitry that is hardwired.
  • the functions of the units 454 to 456 are performed by a processor 462 when a program stored in the memory 452 is processed.

Landscapes

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

Abstract

L'invention concerne entre autres un procédé de taxation selon lequel il est prévu les étapes suivantes: dans un élément de réseau (24) d'un réseau de transmission de données, mémoriser un jeu de données de taxation avec une date de taxation; transmettre un message de demande de service (82) en vue de l'utilisation d'un service par un utilisateur; en fonction du message de demande de service (82), indiquer la date de cessation de service pour l'utilisateur; modifier la date de cessation de service en fonction de l'utilisation dudit service sans l'élément de réseau (24); et déterminer la fin du service en fonction de la date de cessation de service dans l'élément de réseau (62). Ledit procédé est aisé à mettre en oeuvre et offre de multiples avantages.
EP04766566A 2003-09-15 2004-08-20 Procede de taxation et unites de taxation Withdrawn EP1665630A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
DE10342558A DE10342558A1 (de) 2003-09-15 2003-09-15 Verfahren zum Vergebühren und Vergebührungseinheiten
PCT/EP2004/051868 WO2005027406A1 (fr) 2003-09-15 2004-08-20 Procede de taxation et unites de taxation

Publications (1)

Publication Number Publication Date
EP1665630A1 true EP1665630A1 (fr) 2006-06-07

Family

ID=34305772

Family Applications (1)

Application Number Title Priority Date Filing Date
EP04766566A Withdrawn EP1665630A1 (fr) 2003-09-15 2004-08-20 Procede de taxation et unites de taxation

Country Status (7)

Country Link
US (1) US20070103117A1 (fr)
EP (1) EP1665630A1 (fr)
JP (1) JP2007506314A (fr)
KR (1) KR20060076298A (fr)
CN (1) CN1853368A (fr)
DE (1) DE10342558A1 (fr)
WO (1) WO2005027406A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11729588B1 (en) 2021-09-30 2023-08-15 T-Mobile Usa, Inc. Stateless charging and message handling

Families Citing this family (15)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7529813B2 (en) * 2005-04-14 2009-05-05 Hewlett-Packard Development Company, L.P. Multimedia transfer for wireless network
CN1885780B (zh) * 2005-06-24 2012-03-28 朗迅科技公司 集中式离线收费和在线收费的方法及系统
CN1794867A (zh) * 2005-06-30 2006-06-28 华为技术有限公司 多播业务中停止用户会话的方法
GB0517065D0 (en) 2005-08-19 2005-09-28 Nokia Corp Online charging management server
CN101009572B (zh) * 2006-01-24 2012-07-04 朗迅科技公司 对于ims会话期间的媒体改变的ims预算控制
DE102006037511B4 (de) 2006-08-10 2019-12-12 O2 (Germany) Gmbh & Co. Ohg Kommunikationssystem
US8116728B2 (en) * 2008-04-22 2012-02-14 Alcatel Lucent Charging in LTE/EPC communication networks
US9438746B2 (en) * 2008-05-01 2016-09-06 Alcatel Lucent Centralized charging systems for offline charging and online charging
KR101262689B1 (ko) * 2008-07-30 2013-05-15 알카텔-루센트 유에스에이 인코포레이티드 네트워크 도메인들 사이에서 전송되는 세션들에 대한 온라인 차징
EP2748969A1 (fr) * 2011-08-25 2014-07-02 Nokia Solutions and Networks Oy Optimisation des déclencheurs de facturation en ligne dans les réseaux de communication
US9467301B2 (en) * 2012-03-19 2016-10-11 Nokia Solutions And Networks Oy Network interface utilization dependent charging determination
KR101431772B1 (ko) * 2014-03-18 2014-08-20 주식회사선박무선 선원 복지용 유무선통신 접속 및 제공 시스템
CN105472591A (zh) * 2014-09-12 2016-04-06 阿尔卡特朗讯 一种用于邻近服务计费的方法、用户设备与计费系统
US10644893B2 (en) 2018-08-06 2020-05-05 At&T Intellectual Property I, L.P. Ensuring correctness of session identifiers in call duration records in mobile networks
DE102020209581A1 (de) * 2020-07-30 2022-02-03 Volkswagen Aktiengesellschaft Vorrichtung und Verfahren zur Diagnose eines Zustands einer Ladeschnittstelle

Family Cites Families (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
FI112143B (fi) * 2000-08-14 2003-10-31 Sonera Oyj Prepaid-palvelu
US6999449B2 (en) * 2000-08-18 2006-02-14 Telefonaktiebolaget Lm Ericsson (Publ) System and method of monitoring and reporting accounting data based on volume
US20020133457A1 (en) * 2001-01-31 2002-09-19 Gerlach Charles Althoff Apparatus and method for prepaid charging of wireless packet data services
DE60225035T2 (de) * 2001-10-08 2009-02-05 Telefonaktiebolaget Lm Ericsson (Publ) System und verfahren zum vergebühren in einem kommunikationsnetzwerk und kommunikationsnetzwerk-server hierzu
US7720960B2 (en) * 2003-03-04 2010-05-18 Cisco Technology, Inc. Method and apparatus providing prepaid billing for network services using explicit service authorization in an access server
US20050009500A1 (en) * 2003-06-24 2005-01-13 Openwave Systems Inc. System and method for extending billing services to applications on a carrier's network
US20050243746A1 (en) * 2004-04-29 2005-11-03 Nokia Corporation Session inspection scheme

Non-Patent Citations (1)

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

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11729588B1 (en) 2021-09-30 2023-08-15 T-Mobile Usa, Inc. Stateless charging and message handling
US12041521B2 (en) 2021-09-30 2024-07-16 T-Mobile Usa, Inc. Stateless charging and message handling

Also Published As

Publication number Publication date
KR20060076298A (ko) 2006-07-04
US20070103117A1 (en) 2007-05-10
DE10342558A1 (de) 2005-04-14
JP2007506314A (ja) 2007-03-15
WO2005027406A1 (fr) 2005-03-24
CN1853368A (zh) 2006-10-25

Similar Documents

Publication Publication Date Title
DE602004012458T2 (de) Flexible gebührenberechnungsmechanismen für ip-multimedia-dienste
DE602005002524T2 (de) IMS Übergangseinrichtung und Verfahren zur Online-Vergebührung in IMS Netzwerken
EP1665630A1 (fr) Procede de taxation et unites de taxation
DE602005001435T2 (de) Anrufsteuerung mit integrierter Anwendungsserver- und Übergangseinrichtungs-Logik in IMS Netzwerken
DE602005002791T2 (de) Verfahren zur wahl einer gebührenerfassungsregel in verbindung mit einem teilnehmer
DE60305671T2 (de) Gebuehrenberechnung in einem kommunikationsnetzwerk
EP1802028B1 (fr) Reseau de charge, appareil formant agent de charge et procede de charge correspondant
DE602005006094T2 (de) Verarbeitungsverfahren auf der basis eines charging-trigger-ereignisses und eines neuauthorisationsereignisses eines paketdatenflusses
DE602004010936T2 (de) Gebührenberechnungsmechanismen für IP-Multimediadienste
WO2007128693A1 (fr) Procédé pour permettre la distribution d'une qualité de service et/ou la taxation du service dans le cas de services de télécommunication
EP1278383A2 (fr) Méthode, dispositifs et programmes pour transmettre des messages entre élements d'un réseau de télécommunications
DE102005037874B4 (de) Verfahren und Anordnung zur Kontrolle und Vergebührung von Peer to Peer-Diensten in einem IP-basierten Kommunikationsnetzwerk
CN102934393B (zh) 服务递送条件改变管理的方法和设备
EP2993820A1 (fr) Chargement efficace de session sur interface diamètre Ro
US10158764B2 (en) Methods and apparatus for allocating service costs in a telecommunications network
EP1503538B1 (fr) Procédé pour la détermination de tarif pour une transmission de données
EP1503539B1 (fr) Méthode pour le calcul d'un tarif pour la facturation d'une transmission de données
EP1488627B1 (fr) Procede pour decompter les taxes telephoniques d'une liaison entre des terminaux de communication
DE602004012872T2 (de) System und verfahren zur implementierung einer vorausbezahlung für datendienste
DE102005001905A1 (de) Echtzeit-Vergebührung von Diensten
EP1582027B1 (fr) Procede pour acceder a un systeme de paiement
EP3203714A1 (fr) Informations de comptes multiples pour une indication de prix
WO2005027407A1 (fr) Procede de taxation dans des reseaux de transmission de donnees et elements de reseau pour mettre ledit procede en oeuvre
WO2002080517A2 (fr) Procede de facturation de services par l'intermediaire d'un compte de credit
WO2004062193A1 (fr) Procede pour facturer une communication internet entre des terminaux de communication

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

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 IT LI LU MC NL PL PT RO SE SI SK TR

DAX Request for extension of the european patent (deleted)
17Q First examination report despatched

Effective date: 20070628

RAP1 Party data changed (applicant data changed or rights of an application transferred)

Owner name: NOKIA SIEMENS NETWORKS GMBH & CO. KG

RAP3 Party data changed (applicant data changed or rights of an application transferred)

Owner name: NOKIA SIEMENS NETWORKS S.P.A.

RAP3 Party data changed (applicant data changed or rights of an application transferred)

Owner name: NOKIA SIEMENS NETWORKS GMBH & CO. KG

RAP1 Party data changed (applicant data changed or rights of an application transferred)

Owner name: NOKIA SOLUTIONS AND NETWORKS GMBH & CO. KG

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

Free format text: STATUS: THE APPLICATION IS DEEMED TO BE WITHDRAWN

18D Application deemed to be withdrawn

Effective date: 20160301