1 / 12

An Overview of 3GPP2 RADUIS VSAs

An Overview of 3GPP2 RADUIS VSAs. QUALCOMM Inc. March 11 , 2004 Masa Shirota and Raymond Hsu. Contents. Architectural Assumptions in 3GPP2 Wireless IP Network Why 3GPP2 VSAs are necessary? 3GPP2 VSAs Difference between 3GPP2 recommendation and CDG recommendation on RADIUS attribute

rahim-mays
Download Presentation

An Overview of 3GPP2 RADUIS VSAs

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. An Overview of 3GPP2 RADUIS VSAs QUALCOMM Inc. March 11, 2004 Masa Shirota and Raymond Hsu

  2. Contents • Architectural Assumptions in 3GPP2 Wireless IP Network • Why 3GPP2 VSAs are necessary? • 3GPP2 VSAs • Difference between 3GPP2 recommendation and CDG recommendation on RADIUS attribute • Possible replacement of 3GPP2 VSA with IETF attribute

  3. Architectural Assumptions in 3GPP2 Wireless IP Network • The home AAA and the Visited AAA are owned by the 3GPP2 operators. • A 3rd party AAA support is out of scope of the standardization.

  4. Why 3GPP2 VSAs are necessary? • Incorporate Air link specific information to the accounting • 3GPP2 system’s specific identifiers • Packet-data user profiles are sent from AAA to PDSN • Exchange Security related information for Mobile IP • PDNS or HAindicates its capability to the AAA • Support 3GPP2 specific features • Backward compatibility support • Network administration

  5. 3GPP2 VSAs (1)This presentation outlines 3GPP2 VSAs. It does not explain all of them. • Air link specific information • RAN sends the following records: • Mobile Station ID (ESN) • Infrastructure ID (Serving PCF, BSID) • Air interface related information (Service Option, Radio Configuration, Frame size) • PDSN needs to map those records to 3GPP2 VSAs. • 3GPP2 system’s specific identifiers: • Mobile Station • ESN • Session • Correlation ID, Session Continue, Beginning Session, Service Reference ID, Accounting-Stop-triggered-by-Active-Stop-Indication • Infrastructure ID • Home Agent, Serving PCF, BSID, Foreign Agent Address • Zone • User zone

  6. 3GPP2 VSAs (2)This presentation outlines 3GPP2 VSAs. It does not explain all of them. • User profiles for packet data services • Service Option Profile • This attribute specifies the authorized packet data service options, the maximum number of simultaneous service instance of the given service option number(n), andthe total maximum number of simultaneous service instances. • Always on • To indicate if the user has the ‘Always on’ service or not. • Allowed Differentiated Service Marking • Specifies if the user is allowed to mark packets with AF, EF and the Max Class (i.e. Max Selector Class). • Allowed Persistent TFT (Traffic Flow Template) • This attribute specifies the number of simultaneous persistent TFTs allowed for an user. • Reverse Tunnel Specification • This attribute indicates if the reverse tunneling is required. • Remote Address Accounting • This attribute identifies an IP address to be used for Remote Address Accounting. • Compulsory Tunnel Indictor • This attribute indicates invocation of compulsory tunnel established on behalf of MS for providing private network and/or ISP access during a single packet data connection.

  7. 3GPP2 VSAs (3)This presentation outlines 3GPP2 VSAs. It does not explain all of them. • Security related information for Mobile IP • HAAA indicates whether IP security should be applied to MIP registration messages and MIP tunneled data between PDSN and HA, or not to use IPSec at all. • If IPsec is required and IPSec SA does not exist, Pre-shared secret for IKE is distributed using 3GPP2 VSAs. • If dynamic HA assignment is requested, the IKE pre-shared Secret Request is sent with the RADIUS Access Request. • Capability Notification • Session Termination Capability • This attribute is used to convey what kind of Session Termination Capability is supported by the PDSN. • AAA uses this attribute to tell the PDSN apreferred resource management mechanism.

  8. 3GPP2 VSAs (4)This presentation outlines 3GPP2 VSAs. It does not explain all of them. • 3GPP2 Specific Services • Prepaid Packet Data Service • A number of VSAs are defined to support 3GPP2 Prepaid Packet Data Services. • Remote Address Accounting • Backward compatibility support • MN-AAA Removal Indication • Until IS-835-A, MN-AAA Authentication Extension is always required in MIP Registration Request (RRQ). However, there was a clarification during IS-835-B development, MN-AAA Authentication should not be presented in MIP RRQ when the PDSN relays MIP RRQ to HA. If this attribute is received at the PDSN, the PDSN shall remove MN-AAA Authentication Extension. • Network administration • Disconnect Reason • This attribute indicates the reason for disconnecting the user at the PDSN. • RN Packet Data Inactivity Timer • This attribute indicates the value of the RAN packet data inactivity timer. • DNS Update Request • Container • This attribute is used for carrying UDR when the parameters have been changed.

  9. Difference between 3GPP2 recommendation and CDG recommendation on RADIUS attribute (1) • Correlation ID is defined as mandatory attribute for the Access Request, Accounting Start, Stop and Interim in 3GPP2 specification, but not mentioned in CDG recommendation. • Recommendation: Correlation ID should be added to the list in CDG recommendation. The list already has 3GPP2 VSA (BSID). • Calling-Station-ID is defined as mandatory attribute in the CDG recommendation. But, it is optional in Access Request in 3GPP2 specification. • Recommendation: Request 3GPP2 TSG-X to make it be mandatory. • Acct-Status-Type is also not included in the table in 3GPP2 specification. But, it is indispensable for Accounting Request operation. It is too obvious. • Recommendation: No need to take action. • Acct-Delay-Time is not explicitly specified in a table that describes Accounting Parameter Attribute RADIUS Definitions (Table 6 in X.S0011.5-C), or not required to send in Accounting Request. Support of RFC 2866 is mandatory. • Recommendation: Request 3GPP2 TSG-X to specify it in the table.

  10. Difference between 3GPP2 recommendation and CDG recommendation on RADIUS attribute (2) • Acct-Session-ID is not specified in the Access Request in 3GPP2 Specification. • Recommendation: Request 3GPP2 TSG-X to specify and make it be mandatory. • Source IP address (IPv4 or IPv6), Correlation ID, IP Technology and Compulsory Tunnel Indicator are required in Accounting Start, Stop and Interim in 3GPP2 specification. But, those are not defined in CDG recommendation. • Recommendation: Specify them in CDG recommendation. Or encourage to use 3GPP2 specification in case of roaming between 3GPP2 carriers. • Session Continue Attribute is required in Accounting Stop in 3GPP2 Specification. But, not specified in CDG Recommendation. • Specify them in CDG recommendation. Or encourage to use 3GPP2 specification in case of roaming between 3GPP2 carriers. • Acct-Input-Octets and Acct-Output-Octets are required in Accounting Start in 3GPP2 Specification. But, not in CDG Recommendation. • Specify them in CDG recommendation. Or encourage to use 3GPP2 specification in case of roaming between 3GPP2 carriers.

  11. Difference between 3GPP2 recommendation and CDG recommendation on RADIUS attribute (3) • 3GPP2 Specification has a table that specify which VSA is required (optional/mandatory) in each RADIUS message. But, there is no similar table for IETF compliant attribute as described in CDG Recommendation. (There are tables for Access Request and Accept. But, those are not the same as CDG’s.) It might be good to develop such table in 3GPP2 specification. • Recommendation: Request 3GPP2 TSG-X to specify it • CDG Recommendation does not talk about attribute for the Access Accept. • Recommendation: Specify them in CDG recommendation.

  12. Possible replacement of 3GPP2 VSA with IETF attribute • Incorporate Air link specific information to the accounting. • This is 3GPP2 specific. No alternatives in IETF. • 3GPP2 system’s specific identifiers. • This is 3GPP2 specific. No alternatives in IETF. • AAA (with Data base) stores user profiles for packet data services. • We may be able to think about replacing Compulsory Tunnel Indicator with the attributes specified in RFC2868 RADIUS Attributes for Tunnel Protocol Support. However, a VSA, Compulsory Tunnel Indicator is mandatory attribute for Accounting Request. In order to support backward compatibility, this VSA will be supported in any of event. Others are 3GPP2 specific. No alternatives in IETF. • Exchange Security related information for Mobile IP. • This is 3GPP2 specific. No alternatives in IETF. • PDNS or HAindicates its capability to the AAA. • This is 3GPP2 specific. No alternatives in IETF. • Support 3GPP2 specific features. • This is 3GPP2 specific. No alternatives in IETF. • Backward compatibility support. • This is 3GPP2 specific. No alternatives in IETF. • Network administration • This is 3GPP2 specific. No alternatives in IETF.

More Related