Tech-invite3GPPspecsGlossariesIETFRFCsGroupsSIPABNFsWorld Map
Top   in Index   Prev   Next

TR 22.895 (SA1)
Study on service aspects of integration of Single Sign-On (SSO) frameworks with 3GPP operator-controlled resources and mechanisms

ToC   3GPP‑Page   Help    
V12.0.0 (Wzip)  2012/03  17 p.


Rapporteur:  Mr. Wallace, Christopher
See also:  –

The Single Sign-On (SSO) framework integration with 3GPP network resource and services intends to execute a comprehensive set of use cases and service requirements to serve various operator authentication configurations.

The scope of the Single Sign-On (SSO) integration study is to:
  • provide service and deployment scenarios for 3GPP operators adopting an integrated approach to SSO, including web, person-to-person and M2M service scenarios;
  • provide transparent identification and seamless authentication to Application Services on behalf of the user;
  • support a comprehensive set of use cases of integration of different Identity and SSO frameworks (e.g OpenID) for various operator authentication configurations;
  • define use cases and provide service requirements for Operators sharing controlled user credentials with Affiliated Application Service Providers;
  • define use cases and service requirements associated with ensuring that the intended user is making use of the associated SSO capability (including the case when the UE has been stolen or lost);
  • realize the Identity Provider role within the 3GPP network ecosystem and its influence among outside internet web service providers; and
  • provide an enhanced user experience with secure, reliable access and authentication to Affiliated Application Services.


 

Here   Top

 

1 Scope2 References3 Definitions, symbols and abbreviations3.1 Definitions3.2 Abbreviations4 Use cases, services and user groups4.1 Introduction4.2 Use case 1: Affiliated Application Service access4.3 Use case 2: Seamless SSO access between Operator service and multiple Affiliated Application Services4.4 Use case 3: Seamless mobility access to an Affiliated Application Service Provider across Operator/IdP domains4.5 Use case 4: Accessing an Affiliated Application Service using OpenID4.6 Use case 5: User authentication4.7 Use case 6: Automation of authentication method4.8 Use case 7: Seamless service detection, redirection and supply of credentials by a UE4.9 Use Case 8: Seamless transition between 3GPP access and non-3GPP access to a service via the SSO of a single IdP4.10 Use case 9: User identity acknowledgement for SSO usage4.11 Use case 10: Using the 3GPP SSO Service by another (non-MNO or other MNO) SSO Provider4.12 Use case 11: SSO-provided attribute exchange and associated user consent4.13 Use case 12: User management of the association between an Application Service and the SSO Service5 Business Models6 Deployment Scenarios7 Service Aspects8 Charging Aspects9 Security Aspects10 Privacy Aspects11 Suggested Requirements11.1 Requirements for the UE11.2 Requirements for an SSO Service12 Summary and conclusionsA Change history

 

1  ScopeWord-p. 6
2  References
3  Definitions, symbols and abbreviations
4  Use cases, services and user groups
4.1  Introduction
4.2  Use case 1: Affiliated Application Service accessWord-p. 8
4.3  Use case 2: Seamless SSO access between Operator service and multiple Affiliated Application Services
4.4  Use case 3: Seamless mobility access to an Affiliated Application Service Provider across Operator/IdP domainsWord-p. 9
4.5  Use case 4: Accessing an Affiliated Application Service using OpenID
4.6  Use case 5: User authenticationWord-p. 10
4.7  Use case 6: Automation of authentication method
4.8  Use case 7: Seamless service detection, redirection and supply of credentials by a UEUp
4.9  Use Case 8: Seamless transition between 3GPP access and non-3GPP access to a service via the SSO of a single IdP
4.10  Use case 9: User identity acknowledgement for SSO usage
4.11  Use case 10: Using the 3GPP SSO Service by another (non-MNO or other MNO) SSO Provider
4.12  Use case 11: SSO-provided attribute exchange and associated user consentWord-p. 14
4.13  Use case 12: User management of the association between an Application Service and the SSO ServiceUp
5  Business ModelsWord-p. 15
6  Deployment Scenarios
7  Service Aspects
8  Charging Aspects
9  Security Aspects
10  Privacy Aspects
11  Suggested RequirementsUp
12  Summary and conclusions
A  Change historyWord-p. 17

Up   Top