5 Miscellaneous Compliance
Compliance to RFC 2548 (Microsoft Vendor-specific RADIUS Attributes)
In parameterized mode, RCA does not support these attributes.
In parameterised mode, RCA can be configured to read any of these attributes and / or send any of these attribute in a Radius message, on a per message type basis.
Compliance to 3GPP TS 29.061
3GPP TS 29.061
This section states RCA’s compliance to this document:
3GPP TS 29.061 V3.14.1 (2005-06)
Technical Specification
3rd Generation Partnership Project;
Technical Specification Group Core Network and Terminals;
Interworking between the Public Land Mobile Network (PLMN)
supporting packet based services and
Packet Data Networks (PDN)
(Release 1999)
GLOBAL SYSTEM FOR
MOBILE COMMUNICATIONS
This document is not reproduced in full here, with differences, as is done for the RFCs, for copyright reasons.
The use of the RADIUS protocol is described in section 16 of 3GPP TS 29.061.
Convergent Charging Controller Implementation Note:
In 3GPP2 mode, RCA does not comply with this document.
In parameterised mode, RCA can be configured to comply with this section, apart from the following comments and observations:
Convergent Charging Controller Implementation Note:
- RCA does not perform authentication, other than identifying the subscriber and performing credit control.
- RCA does not act as a proxy.
- RCA does not use the DHCP protocol and cannot assign IP addresses.
- RCA assumes that there is only one PDP context per session. I.e. it cannot cope with receiving one Access-Request and then several strams of Accounting-Requests, one for each PDP context, as described in section 16.3.1, figure 2.
- RCA does not take any special notice of the "Session stop indicator" VSA. (RCA assumes that, as there is only one PDP per session then the whole session is over when Accounting-Request (STOP) is received.)
- RCA does not deal with Accounting ON and Accounting OFF messages.
- All the attributes listed in section 16.4.1 can be read by RCA and saved for use in RADIUS messages sent by RCA. The following attributes are of additional note:
- User-Name, 3GPP-IMSI, Calling-Station-ID RCA will probably be configured to use one of these attributes to identify the subscriber.
- Frames—IP-Address RCA does not assign IP addresses so it is not sensible to configure RCA to put this attribute in Access-Accept messages.
- RCA will usually be configured to perform correlation of sessions based on a combination of 3GPP-Charging-ID and 3GPP-GGSN-Address.
Compliance to 3GPP2 X.S0011-005-C (cdma2000 Wireless IP Network Standard: Accounting Services and 3GPP2 RADIUS VSAs)
3GPP2 X.S0011-005-C
RCA only complies with this document when run in 3GPP2 mode.
Convergent Charging Controller Implementation Notes:
Section 3.1.2, shown below, is not implemented in RCA:
- Section 3.1.2 "It is the responsibility of the Visited RADIUS server to ensure the remote address table indices returned in a RADIUS Access-Accept message are consistent with the tables stored in the PDSN. For example, the Visited RADIUS server may filter out the Remote Address Table Index attributes contained in the RADIUS Access-Accept messages received from uncoordinated realms." RCA does not do this.
In addition:
- RCA does not produce any usage data records. It only performs credit control.
- In RCA in 3GPP2 mode, Accounting-request messages do not affect credit control in any way.
Section 5 3GPP2VSA Table: Not all the attributes for 3GPP2VSA are supported by RCA. The RCA ignores any unexpected attributes that it receives.
This table lists the attributes that are supported by RCA:
| VSA | Type | Access-Request | Access-Accept | Accounting Start | Accounting Stop | Accounting Interim-Update |
|---|---|---|---|---|---|---|
| Correlation ID | 26/44 | 1 | 0-1 (not implemented or non-standard in RCA) | 1 | 1 | 1 |
| Service Option Profile | 26/74 | 0 | 0-1 (Note 1) | 0 | 0 | 0 |
|
Session Termination Capability [Note 2] |
26/88 | 1 | 1 | 0 | 0 | 0 |
|
PrePaidAccounting Quota (PPAQ) [Note 3] |
26/90 | 0-1 (not implemented or non-standard in RCA) | 0-1 | 0 | 0 | 0 |
|
PrePaidAccounting Capability (PPAC) [Note 4] |
26/91 | 0-1 | 0-1 | 0 | 0 | 0 |
This table lists the attributes that RCA does not expect, or that RCA does not send, and that are not supported:
| VSA | Type | Access-Request | Access-Accept | Accounting Start | Accounting Stop | Accounting Interim-Update |
|---|---|---|---|---|---|---|
| IKE Pre-shared Secret Request | 26/01 | 0-1 | 0 | 0 | 0 | 0 |
| Security Level | 26/02 | 0 | 0-1 | 0 | 0 | 0 |
| Pre-shared Secret | 26/03 | 0 | 0-1 | 0 | 0 | 0 |
| Reverse Tunnel Specification | 26/04 | 0 | 0-1 | 0 | 0 | 0 |
| Differentiated Services Class Option | 26/05 | 0 | 0-1 | 0 | 0 | 0 |
| Container | 26/06 | 0 | 0 | 0 | 0+ | 0+ |
| Home Agent | 26/07 | 0-1 | 0-1 | 0-1 | 0-1 | 0-1 |
| KeyID | 26/08 | 0 | 0-1 | 0 | 0 | 0 |
| Serving PCF | 26/09 | 0 | 0 | 1 | 1 | 1 |
| BSID | 26/10 | 0 | 0 | 1 | 1 | 1 |
| User Zone | 26/11 | 0 | 0 | 0-1 | 0-1 | 0-1 |
| Forward Mux Option | 26/12 | 0 | 0 | 0-1 | 0-1 | 0-1 |
| Reverse Mux Option | 26/13 | 0 | 0 | 0-1 | 0-1 | 0-1 |
| Service Option | 26/16 | 0-1 | 0 | 1 | 1 | 1 |
| Forward Traffic Type | 26/17 | 0 | 0 | 0-1 | 0-1 | 0-1 |
| Reverse Traffic Type | 26/18 | 0 | 0 | 0-1 | 0-1 | 0-1 |
| Fundamental Frame Size | 26/19 | 0 | 0 | 0-1 | 0-1 | 0-1 |
| Forward Fundamental RC | 26/20 | 0 | 0 | 0-1 | 0-1 | 0-1 |
| Reverse Fundamental RC | 26/21 | 0 | 0 | 0-1 | 0-1 | 0-1 |
| IP Technology | 26/22 | 0-1 | 0 | 1 | 1 | 1 |
| Compulsory Tunnel Indicator | 26/23 | 0 | 0-1 | 1 | 1 | 1 |
| Release Indicator | 26/24 | 0 | 0 | 0 | 1 | 0 |
| Bad PPP Frame Count | 26/25 | 0 | 0 | 0 | 0-1 | 0-1 |
| Number of Active Transitions | 26/30 | 0 | 0 | 0 | 1 | 1 |
| SDB Octet Count | 26/31 | 0 | 0 | 0 | 0-1 | 0-1 14 See X.S0011-006-C for attributes of PrePaid Accounting (Terminating) |
| SDB Octet Count (Originating) | 26/32 | 0 | 0 | 0 | 0-1 | 0-1 |
| Number of SDBs (Terminating) | 26/33 | 0 | 0 | 0 | 0-1 | 0-1 |
| Number of SDBs (Originating) | 26/34 | 0 | 0 | 0 | 0-1 | 0-1 |
| IP Quality of Service | 26/36 | 0 | 0 | 0-1 | 0-1 | 0-1 |
| Airlink Priority15 | 26/39 | 0 | 0 | 0-1 | 0-1 | 0-1 |
| Airlink Record Type15 | 26/40 | 0 | 0 | 0 | 0 | 0 |
| Airlink Sequence Number15 | 26/42 | 0 | 0 | 0 | 0 | 0 |
| Number of HDLC layer bytes received | 26/43 | 0 | 0 | 0 | 0-1 | 0-1 |
| Mobile Originated / Mobile Terminated Indicator15 | 26/45 | 0 | 0 | 0 | 0 | 0 |
| Inbound Mobile IP Signaling Octet Count | 26/46 | 0 | 0 | 0 | 0-1 | 0-1 |
| Outbound Mobile IP Signaling Octet Count | 26/47 | 0 | 0 | 0 | 0-1 | 0-1 |
| Session Continue | 26/48 | 0 | 0 | 0 | 1 | 0-1 |
| Active Time | 26/49 | 0 | 0 | 0 | 0-1 | 0-1 |
| DCCH Frame Format | 26/50 | 0 | 0 | 0-1 | 0-1 | 0-1 |
| Beginning Session | 26/51 | 0 | 0 | 0-1 | 0 | 0 |
| ESN | 26/52 | 0 | 0 | 1 | 1 | 1 |
| .S. Key | 26/54 | 0 | 0-1 | 0 | 0 | 0 |
| .S. Request | 26/55 | 0-1 | 0 | 0 | 0 | 0 |
| .S. Lifetime | 26/56 | 0 | 0-1 | 0 | 0 | 0 |
| MN-HA SPI | 26/57 | 0-1 | 0 | 0 | 0 | 0 |
| MN-HA Shared Key | 26/58 | 0 | 0-1 | 0 | 0 | 0 |
| Remote Ipv4 Address | 26/59 | 0 | 0+ | 0 | 0 | 0 |
| Reserved16 | 26/60-69 | |||||
| Remote Ipv6 Address | 26/70 | 0 | 0+ | 0 | 0 | 0 |
| Remote Address Table Index | 26/71 | 0 | 0+ | 0 | 0 | 0 |
| Remote IPv4 Address Octet Count | 26/72 | 0 | 0 | 0 | 0+ | 0+ |
| Allowed Differentiated Services Marking | 26/73 | 0 | 0-1 | 0 | 0 | 0 |
| DNS-Update- Required | 26/75 | 0 | 0-1 | 0 | 0 | 0 |
| Always On | 26/78 | 0 | 0-1 | 0-1 | 0-1 | 0-1 |
| Foreign Agent Address | 26/79 | 0-1 | 0 | 0 | 0 | 0 |
| Last User Activity | 26/80 | 0 | 0 | 0 | 0-1 | 0-1 |
| MN-AAA Removal Indication | 26/81 | 0 | 0-1 | 0 | 0 | 0 |
| RN Packet Data Inactivity Timer | 26/82 | 0 | 0-1 | 0 | 0 | 0 |
| Forward PDCH RC | 26/83 | 0 | 0 | 0-1 | 0-1 | 0-1 |
| Forward DCCH Mux Option | 26/84 | 0 | 0 | 0-1 | 0-1 | 0-1 |
| Reverse DCCH Mux Option | 26/85 | 0 | 0 | 0-1 | 0-1 | 0-1 |
| Forward DCCH RC | 26/86 | 0 | 0 | 0-1 | 0-1 | 0-1 |
| Reverse DCCH RC | 26/87 | 0 | 0 | 0-1 | 0-1 | 0-1 |
| Allowed Persistent TFTs | 26/89 | 0 | 0-1 | 0 | 0 | 0 |
| MIP Lifetime | 26/92 | 0-1 | 0-1 | 0 | 0 | 0 |
| Accounting-Stop-triggered-by-Active-Stop-Indication | 26/93 | 0 | 0-1 | 0 | 0 | 0 |
| Service Reference ID | 26/94 | 0-1 | 0 | 1 | 1 | 1 |
| DNS-Update-Capability | 26/95 | 0-1 | 0 | 0 | 0 | 0 |
| Remote IPv6 Address Octet Count17 | 26/97 | 0 | 0 | 0 | 0+ | 0+ |
| PrePaidTariffSwitch (PTS) | 26/98 | 0 | 0-1 | 0 | 0 | 0 |
Convergent Charging Controller Implementation Notes:
Note 1 – RCA may be configured to add Service-Option-Profile to the first Access-Accept only. The contents of this attribute are completely configurable and are the same for all sessions.
Note 2 – The value of this attribute in the Access-Accept is configurable. RCA uses the value of this attribute in the Access-Request to determinewhether it is allowed to send Disconnect-Request messages.
Note 3 – In the Access-Accept message, RCA puts only the following sub-types in the PPAQ attribute:
- Update Reason
- Volume Quota
- Duration Quota
In the Access-request message, processes only the following sub-types in the PPAQ attribute:
- Update-Reason
- Volume-Quota (Only one out of Volume-Quota and Duration-Quota is expected.)
- Duration-Quota
Note 4 – In the Access-Accept message, RCA puts only the SelectForSession sub-type in the PPAC attribute. Possible values are “Prepaid Accounting for Volume” or “PrePaidAccounting for duration”. The value is the same for all sessions.
In the Access-Request message, RCA reads only the availableInClient sub-type of the PPAC attribute, checking that this indicates volume if RCA is configured for volume accounting, or duration if RCA is configured for duration accounting.
Service Factory
RCA supports one Service factory vendor specific attribute: SF-Access-Point-Id. This is is an ASCII string (the name of the WiFi hotspot the mobile user is connected to) and may be present in the Access-Request. RCA can use the value of this attribute to make decisions when performing credit control.
Compliance to RFC 3162 (RADIUS and IPv6)
RCA does not comply to this RFC. In parameterised mode, RCA can be configured to read attributes of type IPv6 address and store them for sending in other RADIUS messages. That is the limit of RCA support for IPv6. Source and destination addresses for UDP packets can only be IPv4 address with RCA.
In order to comply to RFC 3576, RCA should be configured to add the NAS-IPv6-Address parameter, if present in the Access-Accept, to Disconnect-request messages.
Chapter 6