Content for TS 29.240 Word version: 18.0.0
1 Scope
2 References
3 Definitions, symbols and abbreviations
3.1 Definitions
3.2 Symbols
3.3 Abbreviations
4 Main concept
...
...
1 Scope p. 7
The present document defines the stage 3 network protocol description to the 3GPP Generic User Profile (GUP), which includes the elements necessary to realise the stage 2 requirements in TS 23.240.
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 harmonised 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.
2 References p. 7
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.
[1]
TS 23.240: "3GPP Generic User Profile - Architecture; Stage 2".
[2]
"Web Services Description Language (WSDL) 1.1,": Christensen, Erik, Curbera, Francisco, Meredith, Greg, Weerawarana, Sanjiva, eds. World Wide Web Consortium W3C Note (15 March 2001). http://www.w3.org/TR/2001/NOTE-wsdl-20010315 .
[3]
Thompson, H.S., Beech, D., Maloney, M., Mendleshon, N., eds. (May 2002): "XML Schema Part 1: Structures," Recommendation, World Wide Web Consortium.http://www.w3.org/TR/xmlschema-1/
[4]
Biron, P.V., Malhotra, A., eds. (May 2002): "XML Schema Part 2: Datatypes," Recommendation, World Wide Web Consortium http://www.w3.org/TR/xmlschema-2/ .
[5]
"Simple Object Access Protocol (SOAP) 1.1,": Box, Don, Ehnebuske, David , Kakivaya, Gopal, Layman, Andrew, Mendelsohn, Noah, Nielsen, Henrik Frystyk, Thatte, Satish, Winer, Dave, eds. World Wide Web Consortium W3C Note (08 May 2000). http://www.w3.org/TR/2000/NOTE-SOAP-20000508/ .
[6] Void.
[7]
TS 29.228: "IP Multimedia (IM) Subsystem Cx and Dx interfaces; Signalling flows and message contents".
[8]
TS 23.008: "Organization of subscriber data".
[9]
TS 23.228: "IP Multimedia Subsystems (IMS); Stage 2".
[10]
TS 29.328: "IP Multimedia (IM) Subsystem Sh interface; Signalling flows and message contents".
[11]
TS 33.102: "3G Security; Security architecture".
[12]
TS 33.203: "3G security; Access security for IP-based services".
[13]
"Liberty ID-WSF Data Services Template Specification": Liberty Alliance Project. http://www.projectliberty.org/specs/draft-liberty-idwsf-dst-v2.0-01.pdf (draft)
[14]
"Liberty ID-WSF SOAP Binding Specification": Liberty Alliance Project. http://www.projectliberty.org/specs/liberty-idwsf-soap-binding-v1.1.pdf
[15]
"Liberty ID-WSF Security Mechanisms Specification": Liberty Alliance Project. http://www.projectliberty.org/specs/liberty-idwsf-security-mechanisms-v1.0.pdf
[16] Void.
[17]
"Liberty ID-WSF Discovery Service Specification": Liberty Alliance Project. http://www.projectliberty.org/specs/liberty-idwsf-disco-svc-v1.0.pdf
[18]
RFC 2396: "Uniform Resource Identifiers (URI): Generic Syntax".
[19]
RFC 3261: "SIP: Session Initiation Protocol".
[20]
RFC 2486:" The Network Access Identifier".
[21]
TS 23.003: "Numbering, addressing and identification".
[22]
RFC 2821:"Simple Mail Transfer Protocol".
[23]
"Liberty ID-WSF Interaction Service Specification": Liberty Alliance Project. http://www.projectliberty.org/specs/draft-liberty-idwsf-interaction-svc-1.0-errata-v1.0.pdf12
[24]
Hallam-Baker, Phillip, Kaler, Chris, Monzillo, Ronald, Nadalin, Anthony, eds. (January, 2004): "Web Services Security: SOAP Message Security," OASIS Standard V1.0 [OASIS 200401], Organization for the Advancement of Structured Information Standards http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0.pdf
[25]
RFC 7230: "Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing".
[26]
RFC 7231: "Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content".
[27]
RFC 7232: "Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests".
[28]
RFC 7233: "Hypertext Transfer Protocol (HTTP/1.1): Range Requests".
[29]
RFC 7234: "Hypertext Transfer Protocol (HTTP/1.1): Caching".
[30]
RFC 7235: "Hypertext Transfer Protocol (HTTP/1.1): Authentication".
3 Definitions, symbols and abbreviations p. 9
3.1 Definitions p. 9
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 standardised 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 Symbols p. 9
For the purposes of the present document the following symbols apply:
Rg
Reference Point between Applications and the GUP Server.
Rp
Reference Point between the GUP Server and GUP Data Repositories, and between Applications and GUP Data Repositories.
3.3 Abbreviations p. 9
For the purposes of the present document the following abbreviations apply:
GUP
3GPP Generic User Profile
SOAP
Simple Object Access Protocol
RAF
Repository Access Function
4 Main concept p. 9
This specification defines the binding of the GUP interfaces and procedures to SOAP protocol (defined in "Simple Object Access Protocol (SOAP) 1.1" [5]). Each interface is defined in terms of the messages sent and received. The payload of each message is XML, defined using an XML schema language. The framework, procedures, SOAP binding and security solutions of GUP are based on the Liberty Alliance Project work.
Throughout the rest of this specification the SOAP based binding of the 3GPP GUP is described
