Tech-invite3GPPspaceIETF RFCsSIP

Content for  TS 23.240  Word version:  17.0.0

Top   Top   None   None   Next
0…   4…   4.3…


0  Introductionp. 5

The fact of having several domains within the 3GPP mobile system (e.g. Circuit-Switched, Packet-Switched, IP Multimedia Subsystem) and access technologies (e.g. GERAN, UTRAN and WLAN) introduces a wide distribution of data associated with the user. Further, the new functions both in terminals and networks mean that the data related to users, services and user equipment will be increased greatly. This causes difficulties for users, subscribers, network operators and value added service providers to create, access and manage the user-related data located in different entities.
The objective of specifying the 3GPP Generic User Profile is to provide a conceptual description to enable harmonized usage of the user-related information located in different entities. Technically the 3GPP Generic User Profile provides an architecture, data description and interface with mechanisms to handle the data.

1  Scopep. 6

The present document defines the stage 2 architecture description to the 3GPP Generic User Profile (GUP), which includes the elements necessary to realise the stage 1 requirements in TS 22.240.
The present document includes the GUP reference architecture with descriptions of functional entities, and their interfaces and procedures, as well as the high-level information model for the GUP data.

2  Referencesp. 6

The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
  • References are either specific (identified by date of publication, edition number, version number, etc.) or non specific.
  • For a specific reference, subsequent revisions do not apply.
  • For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.
TS 22.240: "Stage 1 Service Requirement for the 3GPP Generic User Profile (GUP)".
Liberty Discovery Service Specification,
Liberty ID-WSF SOAP Binding Specification,
Liberty ID-WSF Data Services Template,
Liberty ID-WSF Security and Privacy Overview,
Liberty ID-WSF Security Mechanisms,
TS 23.141: "Presence Service; Architecture and functional description".

3  Definitions, symbols and abbreviationsp. 6

3.1  Definitionsp. 6

For the purposes of the present document the following definitions apply:
3GPP Generic User Profile (GUP):
The 3GPP Generic User Profile is the collection of user related data which affects the way in which an individual user experiences services and which may be accessed in a standardized manner as described in this specification.
GUP Component:
A GUP component is logically an individual part of the Generic User Profile.
Data Element:
the indivisible unit of Generic User Profile information.
Data Element Group:
A pre-defined set of Data Elements and/or other Data Element Groups closely related to each other. One or more Data Element Groups can constitute the GUP Component.
Data Description Method:
A method describing how to define the data contained in the Generic User Profile.

3.2  Symbolsp. 7

For the purposes of the present document the following symbols apply:
Reference Point between Applications and the GUP Server.
Reference Point between the GUP Server and GUP Data Repositories, and between Applications and GUP Data Repositories.

3.3  Abbreviationsp. 7

For the purposes of the present document the following abbreviations apply:
For Further Study
3GPP Generic User Profile
Location services
Open Service Access
Public Land Mobile Network
Repository Access Function
User Equipment
eXtensible Markup Language

Up   Top   ToC