Skip to content
TechSpec
  • Foreword
  • Introduction
  • 1. Scope
  • 2. References
  • 3 Definitions and abbreviations
  • 4 General description
  • 5 Stakeholder requirements
  • 6 General Requirements
  • 7 Security
  • 8 Privacy and Authorisation
  • 9 Charging

5 Stakeholder requirements

22.2403GPPRelease 17Service requirements for 3GPP Generic User Profile (GUP)Stage 1TS

Tools: ARFCN - Frequency Conversion for 5G NR/LTE/UMTS/GSM

These requirements are given from the perspective of the key stakeholders.

The stakeholders within the context of GUP are:

– the Subscriber

Note: The subscriber may hold subscriptions for one user (e.g. in the case the subscriber is identical with the user) or several users (e.g. in the case of a company – the subscriber – holding subscriptions for it’s employees – the users)

– the User

Note: The user may or may not be identical with the Subscriber.

– the Value Added Service Provider

– the Home Network Operator

– the Roamed-to Network Operator

– the Regulator

5.1 Subscriber Requirements

For a subscriber’s services, that support and are supported by GUP:

– The subscriber shall be able to customise her subscribed services and interrogate customisation settings, subject to limitations by the Home operator and/or value added service provider. The user interface for customisation/interrogation is service specific and out of scope of this specification.

5.1.1 User Requirements

For a user’s services, that support and are supported by GUP:

– The user shall be able to customise the services , that have been subscribed to her by the subscriber and interrogate customisation settings, subject to limitations by the Home operator and/or value added service provider and/or subscriber. The user interface for customisation/interrogation is service specific and out of scope of this specification.

5.2 Value Added Service Provider Requirements

VASP services, i.e. services provided by Value Added Service Providers (VASP), shall – via mechanisms of the GUP – be able to:

– Identify the network, the service and the user in any GUP related operation

– Check a user’s subscription information for the service.

– Provide access to a user’s service specific GUP data stored by the application (according to the access rights set by the user).

– Access other GUP data of the user subject to limitations of access rights

VASP services – standardised and non-standardised – may be part of the 3GPP system (as operator supplied services in the home-network or in a different 3GPP network) or may reside outside the 3GPP system.

It shall be possible for VASP services outside the 3GPP domain to access GUP only via a secure interface to the 3GPP system.

5.3 Home Network Operator Requirements

The home network operator shall, via GUP mechanisms, be able to:

– support On-line Service Registration

Subscriber service registration can be set up by on-line subscription not just by customer care. This will also reduce Customer Relationship Management (CRM) workload.

– access Terminal Capabilities

Terminal capabilities (e.g. software and hardware information, application features, etc) shall be accessible to the network. This information may be used to enable any services within network.

– access Value Added Service Provider Capability Information

Value Added Service Provider capability information (e.g. Compression algorithms, Billing capabilities) should be accessible to the network. This information may be used to provide end-to-end service according to UE, Network and the Value Added Service Provider’s capabilities.

5.4 Roamed-to Network Operator Requirements

None yet identified.

5.5 Regulatory Requirements

None identified in addition to the considerations in clause 8. Privacy and Authorisation.