6 Definition of charging information
32.2523GPPCharging managementRelease 9Telecommunication managementTSWireless Local Area Network (WLAN) charging
6.1 Data description for WLAN offline charging
6.1.1 Rf message contents
The WLAN nodes generate accounting information that can be transferred from the CTF to the CDF. For this purpose, WLAN offline charging utilises the Charging Data Transfer operation that is specified in the 3GPP accounting application in 3GPP TS 32.299 [50].
6.1.1.1 WLAN Direct IP Access Charging message contents
The accounting message contents at Wa and Wd reference points are specified in 3GPP TS 29.234 [204].
The accounting information exchanged on the interface (Wf reference point) shall be the same as specified in 3GPP TS 32.299 [50] (reference point Rf). The Wf reference point shall transport the accounting Information Elements arriving over the Wa/Wd reference point. If the Wa/Wd reference point is RADIUS based, the RADIUS accounting messages and Information Elements shall be translated to Diameter accounting messages AVPs as defined in RFC 3588 [401] and in RFC 4005 [404]. If Wa/Wd reference point is Diameter incoming messages shall be passed on.
Editor’s Note: When Wf interface is based on the Rf interface, it is FFS if there is a need for Diameter – Diameter translation. Alternatively, Wf could be based on Wa/Wd.
The Charging Data Transfer operation employs the Charging Data Request and Charging Data Response messages. Table 6.1.1.1 describes the use of these messages in WLAN direct IP access offline charging.
Table 6.1.1.1: Offline Charging Messages Reference Table
Message | Source | Destination |
|---|---|---|
Charging Data Request | WLAN AN | CDF |
Charging Data Response | CDF | WLAN AN |
6.1.1.1.1 Charging Data Request Message
Table 6.1.1.1.1 illustrates the basic structure of the Charging Data Request message as used for WLAN direct IP access offline charging.
Table 6.1.1.1.1: Charging Data Request Message Contents
Field | Category | Description |
|---|---|---|
Session Identifier | M | This field identifies the operation session. |
Originator Node-Id | M | This field contains the identification of the source point of the operation and the realm of the operation originator. |
Originator Domain | M | This field contains the realm of the operation originator. |
Operation Type | M | This field defines the transfer type: event for event based charging and start, interim, stop for session based charging. |
Operation Number | M | This field contains the sequence number of the transferred messages. |
Operation Token | OM | This field identifies the domain, subsystem or service and release. |
Service Information | OM | This field holds the 3GPP specific WLAN parameter. |
6.1.1.1.2 Charging Data Response Message
Table 6.1.1.1.2 illustrates the basic structure of a Charging Data Response message as used for WLAN direct IP access offline charging.
Table 6.1.1.1.2: Charging Data Response Message
Field | Category | Description |
|---|---|---|
Session Identifier | M | This field identifies the operation session. |
Result |
6.1.2 GTP’ message contents
GTP’ is used between CDF and CGF on Wz reference point.
Editor’s note: more description needed
6.1.3 CDR Description on the Bw Interface
Dedicated types of CDRs can be generated in the service domain for WLAN by the WLAN AN/PDG/AAA Servers. The content of each CDR type is defined in one of the tables that are part of this clause. For each CDR type the parameter definition includes the parameter name, description and category.
6.1.3.1 CDR Field Types
The following Standard CDR content and format are considered:
– WLAN-AN-CDR generated based on information from the WLAN AN handled by 3GPP AAA Server.
– WLAN-PDG-CDR generated based on information from the PDG.
The content of each CDR type is defined in the tables 6.1.3.2.1 and 6.1.3.2.2. For each CDR type the field definition includes the field name, category and description. The CDF provides the CDRs at the Bw interface in the format and encoding described in 3GPP TS 32.298 [51]. Additional CDR formats and contents may be available at the interface to the billing system to meet the requirements of the billing system, these are outside of the scope of 3GPP standardisation.
6.1.3.2 CDR Content
Editor’s Note: Contents of the CDRs are for further study.
6.1.3.2.1 WLAN Direct IP Access CDR (WLAN-AN-CDR)
NOTE: This CDR should contain a WLAN-Radio-Container as defined in "WLAN Information".
Table 6.1.3.2.1 WLAN Direct IP Access CDR (WLAN-AN-CDR)
Field | Category | Description |
|---|---|---|
Record Type | M | WLAN Direct IP Access CDR |
Record Sequence Number | C | Partial record sequence number. Only present in case of partial records |
Served IMSI | M | IMSI of the served party |
Served IMEI | C | The IMEI of the ME, if available |
Operator Name | M | Hot Spot Operator Name as defined in IETF RFC 5580 [405] |
Location Information | C | Location information regarding the hotspot operator as defined in IETF RFC 5580 [405] |
Location Data | C | Location data regarding the hotspot operator as defined in IETF RFC 5580 [405] |
Charging ID | M | Accounting Session-ID from WLAN AN |
NAS Port | C | NAS Port of WLAN AN |
NAS Port-Id | C | NAS Port-Id of WLAN AN |
NAS Port Type | C | NAS-Port-Type of WLAN AN |
NAS-IP address | C | IPv4 address of the hot-spot |
NAS-Ipv6 address | C | IPv6 address of the hot-spot |
Local IP Address | OC | Local IP address of the served IMSI, i.e. IPv4 or IPv6 |
Data Volume Downlink | C | Downlink data volume for WLAN UE |
Data Volume Uplink | C | Uplink data volume for WLAN UE |
Record Opening Time | M | Time stamp when WLAN session is activated or record opening time on subsequent partial records |
Local Record Sequence Number | OM | Consecutive record number created by this node. The number is allocated sequentially including all CDR types |
Duration | M | Duration of this record |
Cause for Record Closing | M | The reason for closure of the record |
Node ID | OM | Name of the recording entity |
Service Context Id | OM | Holds the context information to which the CDR belongs. The information is obtained from the Operation Token of the Charging Data Request message |
Record Extensions | OC | A set of network operator/manufacturer specific extensions to the record |
6.1.3.2.2 WLAN 3GPP IP Access charging message contents
The content of WLAN 3GPP IP Access CDR is defined in the table 6.1.3.2.2. The field definition includes the field name, category and description. The detailed field descriptions are provided in 3GPP TS 32.298 [51].
If the collection of CDR data is enabled then the PDG shall make available the following data available for each WLAN 3GPP IP Access connection.
Table 6.1.3.2.2 : Wz interface CDR content (WLAN-CDR)
Field | Category | Description |
|---|---|---|
Record Type | M | WLAN PDG record. |
Served IMSI | M | IMSI of the served party. |
Served MSISDN | OM | The primary MSISDN of the subscriber. |
PDG Address used | M | IP address of the PDG used. |
Node ID | OM | Name of the recording entity. |
Serving WAG Address | M | Serving WAG address used during this record. |
WAG PLMN Identifier | OM | WAG PLMN Identifier (MCC and MNC) used during this record. |
Serving AAA Server/proxy Address | M | Serving AAA Server/Proxy address. |
WLAN UE remote IP address | OC | |
WLAN UE Local IP address | OC | |
Charging ID | M | PDG charging identifier used to correlate WLAN AN generated information to PDG generated information |
WLAN session id | M | WLAN session identifier used to correlate WLAN AN generated information to PDG generated information |
Access Point Name Network Identifier | OM | The logical name of the connected access point to the external packet data network (network identifier part of APN). |
Charging Characteristics? | M | The Charging Characteristics applied to the PDP context.? |
Charging Characteristics Selection Mode? | OM | Holds information about how Charging Characteristics were selected. |
Record Opening Time | M | Time stamp when End-to-end Tunnel is activated in this PDG? or record opening time on subsequent partial records. |
Duration | M | Duration of this record in the PDG. |
Cause for Record Closing | M | The reason for the release of record from this PDG. |
Record Sequence Number | C | Partial record sequence number, only present in case of partial records. |
Local Record Sequence Number | OM | Consecutive record number created by this node. The number is allocated sequentially including all CDR types. |
Diagnostics | OM | A more detailed reason for the release of the connection. |
Record Extensions | OC | A set of network operator/manufacturer specific extensions to the record. Conditioned upon the existence of an extension. |
6.2 Data description for WLAN online charging
Editor’s Note: To be completed
6.2.1 Ro message contents
6.2.1.1 WLAN Direct IP Access Charging message contents
The WLAN nodes generate debit/reserve unit information that can be transferred from the CTF to the OCF. For this purpose, WLAN online charging utilises the Debit Unit and Reserve Unit procedure that is specified in the 3GPP credit control application in 3GPP TS 32.299 [50].
The Debit/Reserve Unit procedure employs the Debit/Reserve Unit Request and Debit/Reserve Unit Response messages. Table 6.2.1.1 describes the use of these messages in WLAN Direct IP Access online charging.
Table 6.2.1.1: Online Charging Messages Reference Table
Command-Name | Source | Destination |
Debit/Reserve Unit Request | 3GPP AAA Server | OCS |
Debit/Reserve Unit Response | OCS | 3GPP AAA Server |
6.2.1.1.1 Debit/Reserve Unit Request message
Table 6.2.1.1.1 illustrates the basic structure of the Debit/Reserve Unit Request message as used for WLAN direct IP access online charging.
Table 6.2.1.1.1: Debit/Reserve Units Request Content
Debit/Reserve Units Request | Category | Description |
|---|---|---|
Session Identifier | M | This field identifies the operation session. |
Originator Node-Id | M | This field contains the identification of the source point of the operation. |
Originator Domain | M | This field contains the realm of the operation originator. |
Operation Token | M | This field is an unique operation identifier. |
Operation Type | M | This field defines the transfer type: event for event based charging and start, interim, stop for session based charging. |
Operation Number | M | This field contains the sequence number of the transferred messages. |
Subscriber Address | OC | This field contains the identification of the mobile subscriber (i.e. MSISDN) that uses the requested service. |
Service Token | OC | This field is a unique service identifier. |
Cause of Termination | OC | This field contains the termination reason of the service. |
Service Units Requested | OC | This field contains the amount of requested service units. |
Service Units Used | OC | This field contains the amount of used service units. |
Multiple Operation | OC | This field indicate the occurrence of multiple operations. |
Multiple Unit Operation | OC | This field contains the parameter for the quota management. |
Subscriber Equipment Number | OC | This field contains the identification of the mobile device (i.e. IMEI) that uses the subscriber. |
Service Information | OM | This field holts additional 3GPP service specific parameter: – PS Information; – WLAN Information; – IMS Information; – LCS Information; – PoC Information; – MBMS Information. |
6.2.1.1.2 Debit/Reserve Unit Response message
Table 6.2.1.1.2 illustrates the basic structure of the Debit/Reserve Unit Response message as used for WLAN direct IP access online charging.
Table 6.2.1.1.2: Debit/Reserve Units Response Content
Debit/ Reserve Units Response | Category | Description |
|---|---|---|
Session Identifier | M | This field identifies the operation session. |
Operation Result | M | This field identifies the result of the operation. |
Originator Node-Id | M | This field contains the identification of the source point of the operation. |
Originator Domain | M | This field contains the realm of the operation originator. |
Operation Type | M | This field defines the transfer type: event for event based charging and start, interim, stop for session based charging. |
Operation Number | M | This field contains the sequence number of the transferred messages. |
Service Units Granted | OC | This filed contains the amount of used service units. |
Unit Validity Time | OC | This field contains the time for the validity of the granted service units. |
Extended Information | OC | This field holds the 3GPP specific information. |
6.2.1.2 WLAN 3GPP IP Access Charging message contents
The Debit/Reserve Unit procedure employs the Debit/Reserve Unit Request and Debit/Reserve Unit Response messages. Table 6.2.1.2 describes the use of these messages in WLAN 3GPP IP Access online charging.
Table 6.2.1.2 Online Charging Messages Reference Table
Command-Name | Source | Destination |
Debit/Reserve Unit Request | PDG/3GPP AAA Server | OCS |
Debit/Reserve Unit Response | OCS | PDG/3GPP AAA Server |
6.2.1.2.1 Debit/Reserve Unit Request message
Table 6.2.1.2.1 illustrates the basic structure of the Debit/Reserve Unit Request message as used for WLAN 3GPP IP access online charging.
Table 6.2.1.2.1 Debit/Reserve Units Request Content
Debit/Reserve Units Request | Category | Description |
|---|---|---|
Session Identifier | M | This field identifies the operation session. |
Originator Node-Id | M | This field contains the identification of the source point of the operation. |
Originator Domain | M | This field contains the realm of the operation originator. |
Operation Token | M | This field is an unique operation identifier. |
Operation Type | M | This field defines the transfer type: event for event based charging and start, interim, stop for session based charging. |
Operation Number | M | This field contains the sequence number of the transferred messages. |
Subscriber Address | OC | This field contains the identification of the mobile subscriber (i.e. MSISDN) that uses the requested service. |
Service Token | OC | This field is a unique service identifier. |
Cause of Termination | OC | This field contains the termination reason of the service. |
Service Units Requested | OC | This field contains the amount of requested service units. |
Service Units Used | OC | This field contains the amount of used service units. |
Multiple Operation | OC | This field indicate the occurrence of multiple operations. |
Multiple Unit Operation | OC | This field contains the parameter for the quota management. |
Subscriber Equipment Number | OC | This field contains the identification of the mobile device (i.e. IMEI) that uses the subscriber. |
Service Information | OM | This field holts additional 3GPP service specific parameter: – PS Information; – WLAN Information; – IMS Information; – LCS Information; – PoC Information; – MBMS Information. |
6.2.1.2.2 Debit/Reserve Unit Response message
Table 6.2.1.2.2 illustrates the basic structure of the Debit/Reserve Unit Response message as used for WLAN 3GPP IP access online charging.
Table 6.2.1.2.2 Debit/Reserve Units Response Content
Debit/ Reserve Units Response | Category | Description |
|---|---|---|
Session Identifier | M | This field identifies the operation session. |
Operation Result | M | This field identifies the result of the operation. |
Originator Node-Id | M | This field contains the identification of the source point of the operation. |
Originator Domain | M | This field contains the realm of the operation originator. |
Operation Type | M | This field defines the transfer type: event for event based charging and start, interim, stop for session based charging. |
Operation Number | M | This field contains the sequence number of the transferred messages. |
Service Units Granted | OC | This filed contains the amount of used service units. |
Unit Validity Time | OC | This field contains the time for the validity of the granted service units. |
Extended Information | OC | This field holds the 3GPP specific information. |
6.2.2 Detailed Message Formats
FFS.
6.2.2.1 WLAN Direct IP Access Charging message contents
FFS.
6.2.2.2 WLAN 3GPP IP Access Charging message contents
FFS.
6.3 WLAN Charging specific parameters
The WLAN-Information parameter used for WLAN online charging is provided in the Service-Information parameter.
6.3.1.1 WLAN charging information assignment for Service-Information
The components in the Service-Information that are use for WLAN charging can be found in table 6.3.1.1.
Table 6.3.1.1: Service-Information used for WLAN Charging
Field | Category | Description |
Service-Information | OM | This is a structured field and holds the 3GPP specific parameter as defined in 3GPP TS 32.299 [50]. |
WLAN-Information | OM | This is a structured field and holds the WLAN specific parameters. |
6.3.1.2 Definition of WLAN Information
WLAN specific charging information is provided within the WLAN-Information. The fields of the WLAN-Information which are different coved in several WLAN network notes are indicated by the note specific type.
The detailed structure of the WLAN-Information parameter can be found in table 6.3.1.2.
Table 6.3.1.2 Structure of the WLAN-Information
Field | Category | Description |
|---|---|---|
PDG-Charging-Id | OC | TBD |
WLAN-Session-Id | OC | TBD |
PDG-Address | OC | TBD |
PDG-IPv6-Address | OC | TBD |
WAG-Address | OC | TBD |
WAG-IPv6-Address | OC | TBD |
WAG-PLMN-Id | OC | TBD |
AAA-Server/Proxy-Address | OC | TBD |
AAA-Server/Proxy-Ipv6-Address | OC | TBD |
Framed-IP-Address | OC | TBD |
Framed-IPv6-Prefix | OC | TBD |
WLAN-UE-Local-IP-Address | OC | TBD |
WLAN-UE-Local-Ipv6-Address | OC | TBD |
3GPP-CG-Address | OC | TBD |
3GPP-CG-IPv6-Address | OC | TBD |
Called-Station-Id (See note) | OC | TBD |
3GPP-Session-Stop-Indicator | OC | TBD |
3GPP-Charging-Characteristics | OC | TBD |
Charging-Rule-Base-Name | OC | TBD |
WLAN-Radio-Container | OC | TBD |
Operator-Name | OC | TBD |
Location-Data | OC | TBD |
Location-Information | OC | TBD |
WLAN-Technology | OC | TBD |
NOTE: This field contains the identifier of the access point (APN) the user is connected to
6.3.2 Formal WLAN charging parameter description
6.3.2.1 WLAN charging information for CDRs
The detailed definitions, abstract syntax and encoding of the WLAN CDR parameters are specified in TS 32.298 [51].
6.3.2.2 Definition of the WLAN charging events
The detailed event parameter definitions are specified in TS 32.299 [50].
Annex A (informative):
Bibliography
a) The 3GPP charging specifications
– 3GPP TS 32.250: "Telecommunication management; Charging management; Circuit Switched (CS) domain charging".
– 3GPP TS 32.251: "Telecommunication management; Charging management; Packet Switched (PS) domain charging".
– 3GPP TS 32.260: "Telecommunication management; Charging management; IP Multimedia Subsystem (IMS) charging".
– 3GPP TS 32.270: "Telecommunication management; Charging management; Multimedia Messaging Service (MMS) charging".
– 3GPP TS 32.271: "Telecommunication management; Charging management; Location Services (LCS) charging".
– 3GPP TS 32.296: "Telecommunication management; Charging management; Online Charging System (OCS): Applications and interfaces".
b) Other charging specifications
– ITU-T Recommendation D.93: "Charging and accounting in the international land mobile telephone service (provided via cellular radio systems)".
c) Common 3GPP specifications
– 3GPP TS 22.101: "Service aspects; Service principles".
– 3GPP TS 22.115: "Service aspects; Charging and billing".
– 3GPP TS 23.002: "Network architecture".
– 3GPP TS 23.003: "Numbering, addressing and identification".
– 3GPP TS 27.001: "General on Terminal Adaptation Functions (TAF) for Mobile Stations (MS)".
d) other Domain and Service specific 3GPP / ETSI specifications
– 3GPP TR 23.934: "3GPP system to Wireless Local Area Network (WLAN) interworking; Functional and architectural definition".
– 3GPP TS 24.234: "3GPP System to Wireless Local Area Network (WLAN) interworking; User Equipment (UE) to network protocols; Stage 3".
e) Relevant ITU Recommendations
– ITU-T Recommendation D.93: "Charging and accounting in the international land mobile telephone service (provided via cellular radio systems)".
– ITU-T Recommendation E.164: "The international public telecommunication numbering plan".
– ITU-T Recommendation Q.767: "Application of the ISDN user part of CCITT signalling System No.7 for international ISDN interconnections".
– ITU-T Recommendation X.25: "Interface between Data Terminal Equipment (DTE) and Data Circuit-terminating Equipment (DCE) for terminals operating in the packet mode and connected to public data networks by dedicated circuit".
– ITU-T Recommendation X.121: "International numbering plan for public data networks".
f) Relevant IETF RFCs
– IETF RFC 959 (1985): "File Transfer Protocol".
– IETF RFC 783 (1981): "Trivial File Transfer Protocol (TFTP)".
Annex B (informative):
Change history
Change history | ||||||||
Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Cat | Old | New |
Jun 2006 | SA_32 | SP-060246 | 0001 | — | Correction to I-WLAN Charging Identities | F | 6.0.0 | 6.1.0 |
Sep 2006 | SA_33 | SP-060521 | 0002 | — | Correction to Served PDP Address in WLAN-AN-CDR | F | 6.1.0 | 6.2.0 |
Dec 2006 | SA_34 | SP-060716 | 0003 | — | Add an identifier for the service initiating offline Diameter Accounting | B | 6.2.0 | 7.0.0 |
Jun 2008 | SA_40 | SP-080330 | 0004 | 1 | WLAN online charging | F | 7.0.0 | 8.0.0 |
Sep 2009 | SA_45 | SP-090537 | 0005 | – | Add I-WLAN related reference and some definitions | B | 8.0.0 | 9.0.0 |
Sep 2011 | SA_53 | SP-110528 | 0008 | 1 | Correction to Charging ID in WLAN-CDR content | A | 9.0.0 | 9.1.0 |
Mar 2015 | SA_67 | SP-150070 | 0013 | – | Correction on IETF references | A | 9.1.0 | 9.2.0 |