3GPP2 X50-20100426-xxx

Title: SIP6 access and MIP6 Access Differentiation

Sources: ZTE

Contact: Rajesh Bhalla (rabhalla@zteusa.com) Mao Yuxin (mao.yuxin@zte.com.cn) Bi Yifeng (bi.yifeng@zte.com.cn)

Abstract: The PDSN needs to differentiate between a SimpleIP6 access and MobileIP6 access so as to establish appropriate PCC session (Gateway Control Session or IP-CAN Session) with the PCRF. This contribution highlights the problem scenario and proposes two solutions for discussions and concept approval.

Recommendation: Review and concept approve.

ZTE grants a free, irrevocable license to 3GPP2 and its Organizational Partners to incorporate text or other copyrightable material contained in the contribution and any modifications thereof in the creation of 3GPP2 publications; to copyright and sell in Organizational Partner's name any Organizational Partner's standards publication even though it may include all or portions of this contribution; and at the Organizational Partner's sole discretion to permit others to reproduce in whole or in part such contribution or the resulting Organizational Partner's standards publication. ZTE is also willing to grant licenses under such contributor copyrights to third parties on reasonable, non-discriminatory terms and conditions for purpose of practicing an Organizational Partner’s standard which incorporates this contribution.This document has been prepared by ZTE to assist the development of specifications by 3GPP2. It is proposed to the Committee as a basis for discussion and is not to be construed as a binding proposal on contributors . ZTE specifically reserves the right to amend or modify the material contained herein and to any intellectual property of contributors other than provided in the copyright statement above.

2

Background PCC in cdma2000 networks supports several IP address operation

modes

SimpleIPv4 (SIP4), SimpleIPv6 (SIP6), MobileIPv4 (MIP4), MobileIPv6 (MIPV6), Proxy Mobile IP (PMIP)

The PDSN needs to distinguish between Simple IP and Mobile IP & Proxy Mobile IP address operation modes

Why such differentiation of the IP Address Operation Modes at the PDSN?

For Simple IP address modes, PDSN acts as PCEF and establishes IP-CAN Session with the PCRF

For Mobile IP and Proxy Mobile IP address operation modes, PDSN acts as BBERF and establishes Gateway Control Session with the PCRF

Hence PDSN needs to know the IP address operation mode and provide appropriate PCC related functionality (PCEF or BBERF)

Note: Reference to cdma2000 networks in this contribution refers to cdma2000 1x and HRPD networks

3

Differentiation of IP Address Mode

Differentiation between IPv4 and IPv6 addressing modes is provided by the use of IPCP or IPv6CP NCP procedures between the MS and the PDSN

Differentiation between SIP4 and MIP4 address operation modes is provided by the presence or absence of IP Address Configuration Option during IPCP Configure Request procedures

PMIP mode is indicated the AAA during authentication and authorization procedures

However, no mechanisms have been identified to enable differentiation between SIP6 and MIP6 address operation modes

– From the descriptions in section 5.1.1 X.S0011-E[002], from a packet data session setup perspective, MIP6 access is equivalent to SIP6 access at the PDSN. Then how does the PDSN differentiate SIP6 access and MIP6 access the MS is requesting?

4

Possible Solutions Option-1

– When PDSN cannot distinguish its role as a PCEF or a BBERF; PDSN establishes both, a GW Control Session and an IP-CAN Session with the PCRF

Later, on receiving an IP-CAN Session Establishment request from HA/LMA, it is known to be a

MIP6 access. The PCRF removes the old IP-CAN session with the PDSN

If the PCRF receives an IP-CAN Session Modification Request from the PDSN, it is known to

be a SIP6 access. The PCRF removes Gateway Control Session with the PDSN

PCRF needs to be enhanced to support more than one PCC session type from the PDSN

during the IP address operation determination mode. Additional 3GPP2 specific logic at the

PCRF. Additional logic at the PDSN as well.

Option-2

– For SIP6 and MIP6 access, use a 3GPP2 specific Configuration Option (viz. something similar to ‘MS-PDSN Version/Capability indicator’) during NCP procedures – in addition to the IPv6CP NCP procedures

Bit C2 set to 1 if the MS requests SIP6 access; C3 set to 1 if the MS requests MIP6 access

Distinguish MS access type during NCP phase, similar to differentiation between SIP4 and

MIP4 differentiation during IPCP NCP procedures

Enhancements at the MS and the PDSN

Any other solutions?

5

Discussions and Recommendations Discuss the proposed Option-1 and Option-2 solutions

Investigate and discuss any other possible solutions

Concept approve one of the proposed solutions or any other discussed solution as the way forward

6

Thanks

7

Differentiation Between SIP4 and MIP4

For SIP4 and MIP4 access differentiation:

– PPP session authentication is different. For MIP4, in order to reduce initial setup time, authentication (CHAP or PAP) is not performed

– IPCP negotiation is different. For MIP4, the MS does not include ‘IP Address Configuration Option’ in IPCP Configure-Request message to the PDSN. If the MS includes it, the PDSN considers this as MS requesting SIP4 access

According to the PPP session establishment procedure between the MS and the PDSN, the PDSN can differentiate the MS requesting SIP4 access or MIP4 access