tech-invite   World Map     

3GPP     Specs     Glossaries     Architecture     IMS     UICC       IETF     RFCs     Groups     SIP     ABNFs       Search

Top          in Index          Prev          Next

TR 33.919 (SA3)
3G Security – Generic Authentication Architecture (GAA) – System description

|   ToC   |   3GPP‑Page   |   ETSI‑search   |   Help   |

(P) V14.0.0    2017/03    18 p.
(P) V13.0.0    2016/01    19 p.
(P) V12.0.0    2014/09    19 p.
(P) V11.0.0    2012/09    19 p.
(P) V10.0.0    2011/04    19 p.
(P) V9.1.0    2010/06    19 p.
(P) V8.0.0    2008/12    19 p.
(P) V7.2.0    2007/03    19 p.
(P) V6.2.0    2005/04    15 p.

Rapporteur:  Mrs. Van Moffaert, Annelies
See also:  GAA/GBA-related TS/TR    

A number of applications share a need for mutual authentication between a client (i.e. the UE ) and an application server before further communication can take place. Examples include (but are not limited to) communication between a client and a presence server (possibly via an authentication proxy), communication with a PKI portal where a client requests a digital certificate, communication with a Mobile Broadcast / Multicast Service (MBMS) content server, a BM-SC, etc.

Since a lot of applications share this common need for a peer authentication mechanism, it has been considered useful to specify a Generic Authentication Architecture (GAA). This GAA describes a generic architecture for peer authentication that can a priori serve for any (present and future) application.

This TR can be considered as a framework document for the generic authentication architecture. GBA, HTTPS and the Authentication Proxy (AP), and Certificates are the basic building blocks of the GAA in 3GPP Release 6 and they are specified each in a separate TS. Later on, many additions were made to accommodate specific needs for various use cases.

How the different GAA and GBA related specifications and technical reports fit together in GAA is explained in this document.


Here          Top