IMS Technical Differences

Smart Cards 3GPP IMS terminals have smart cards (UICC) USIM, ISIM applications 3GPP2 IMS does not require a UICC 3GPP2 is in the very early stages of introducing the UICC + ISIM into specifications. Temporary Public/Private Identifiers 3GPP creates temporary Public/Private IDs to support terminals without ISIM application. This scenario is not required for 3GPP2; also, The method of generating these IDs would differ: E.212 vs MIN based IMSIs Support for IPv4 3GPP IMS supports only IPv6. 3GPP2 IMS supports both IPv6 and IPv4. Interworking issues have not been addressed in 3GPP2.

2003-05-14/c.rhoades

IMS Technical Differences

Network Security The use of Security Gateways (SEG) is still under discussion in 3GPP2. Note: Access Security (Security over Gm interface) is the same for both 3GPP and 3GPP2. HSS vs AAA In 3GPP2 IMS, AAA + databases represent an HSS. Also in 3GPP2 IMS, HSS is used only for PS domain. In 3GPP, HSS is used for both PS & CS domains. SLF and Dx Interface These are not specified in the 3GPP2 IMS Default Codecs 3GPP2 IMS has not specified default codecs Policy and the PDF The 3GPP2 work is still in the very early Stage 1 phase. The 3GPP2 PDF may include Policy for Packet Data Subsystem. The 3GPP2 PDF will likely include updates from Release 6. Separation of the PDF from the P-CSCF is important for 3GPP2 roaming scenarios.
2 2003-05-14/c.rhoades

IMS Technical Differences (Roaming)

P-CSCF & PDSN/GGSN location In 3GPP, GGSN and P-CSCF are located in the same network In 3GPP2, PDSN and P-CSCF may be located in different networks PDSN in visited and P-CSCF in home network.

Anchored GGSN In 3GPP, the GGSN is anchored for a given session. In 3GPP2, the PDSN may change. Likewise in 3GPP2, the PDF may change as the UE moves from one PDSN to another. The Go Interface and SBLP has been omitted from the first 3GPP2 IMS specification because of these complications.
Charging 3GPP2 IMS uses AAA for accounting, replacing the CCF with AAA. 3GPP2 IMS transfers accounting records through the AAA, rather than through Billing Servers.

2003-05-14/c.rhoades

Access Specific Terminology

3GPP IMS Rel-5, location information exchanged over the Sh interface is 3GPP specific Would be good if the information is access independent E.g., Cellid information is different. Naming of IMS objects Access network independent naming For example, 3gpp-ims+xml could be named as 3g-ims+xml

2003-05-14/c.rhoades