1、 ETSI TS 123 240 V15.0.0 (2018-06) Universal Mobile Telecommunications System (UMTS); LTE; 3GPP Generic User Profile (GUP); Architecture (Stage 2) (3GPP TS 23.240 version 15.0.0 Release 15) TECHNICAL SPECIFICATION ETSI ETSI TS 123 240 V15.0.0 (2018-06)13GPP TS 23.240 version 15.0.0 Release 15Referen
2、ce RTS/TSGS-0223240vf00 Keywords LTE,UMTS ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Cedex - FRANCE Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 Siret N 348 623 562 00017 - NAF 742 C Association but non lucratif enregistre la Sous-Prfecture de Grasse (06) N 7803/88 Important notice The p
3、resent document can be downloaded from: http:/www.etsi.org/standards-search The present document may be made available in electronic versions and/or in print. The content of any electronic and/or print versions of the present document shall not be modified without the prior written authorization of
4、ETSI. In case of any existing or perceived difference in contents between such versions and/or in print, the only prevailing document is the print of the Portable Document Format (PDF) version kept on a specific network drive within ETSI Secretariat. Users of the present document should be aware tha
5、t the document may be subject to revision or change of status. Information on the current status of this and other ETSI documents is available at https:/portal.etsi.org/TB/ETSIDeliverableStatus.aspx If you find errors in the present document, please send your comment to one of the following services
6、: https:/portal.etsi.org/People/CommiteeSupportStaff.aspx Copyright Notification No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm except as authorized by written permission of ETSI. The content of the PDF version shall
7、not be modified without the written authorization of ETSI. The copyright and the foregoing restriction extend to reproduction in all media. ETSI 2018. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTMand the ETSI logo are trademarks of ETSI registered for the benefit of its Members. 3GPPTM and LTETMa
8、re trademarks of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. oneM2M logo is protected for the benefit of its Members. GSMand the GSM logo are trademarks registered and owned by the GSM Association. ETSI ETSI TS 123 240 V15.0.0 (2018-06)23GPP TS 23.240 vers
9、ion 15.0.0 Release 15Intellectual Property Rights Essential patents IPRs essential or potentially essential to normative deliverables may have been declared to ETSI. The information pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found i
10、n ETSI SR 000 314: “Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in respect of ETSI standards“, which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web server (https:/ipr.etsi.org/). Pursuant to the ETSI IPR Policy
11、, no investigation, including IPR searches, has been carried out by ETSI. No guarantee can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web server) which are, or may be, or may become, essential to the present document. Trademarks The prese
12、nt document may include trademarks and/or tradenames which are asserted and/or registered by their owners. ETSI claims no ownership of these except for any which are indicated as being the property of ETSI, and conveys no right to use or reproduce any trademark and/or tradename. Mention of those tra
13、demarks in the present document does not constitute an endorsement by ETSI of products, services or organizations associated with those trademarks. Foreword This Technical Specification (TS) has been produced by ETSI 3rd Generation Partnership Project (3GPP). The present document may refer to techni
14、cal specifications or reports using their 3GPP identities, UMTS identities or GSM identities. These should be interpreted as being references to the corresponding ETSI deliverables. The cross reference between GSM, UMTS, 3GPP and ETSI identities can be found under http:/webapp.etsi.org/key/queryform
15、.asp. Modal verbs terminology In the present document “shall“, “shall not“, “should“, “should not“, “may“, “need not“, “will“, “will not“, “can“ and “cannot“ are to be interpreted as described in clause 3.2 of the ETSI Drafting Rules (Verbal forms for the expression of provisions). “must“ and “must
16、not“ are NOT allowed in ETSI deliverables except when used in direct citation. ETSI ETSI TS 123 240 V15.0.0 (2018-06)33GPP TS 23.240 version 15.0.0 Release 15Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 5g3Introduction 5g31 Scope 6g32 References 6g33 D
17、efinitions, symbols and abbreviations . 6g33.1 Definitions 6g33.2 Symbols 6g33.3 Abbreviations . 7g34 Reference Architecture . 7g34.1 GUP Functionalities . 7g34.1.1 Harmonized access interface. 7g34.1.2 Single point of access . 7g34.1.3 Authentication of profile access 7g34.1.4 Authorization of prof
18、ile access . 7g34.1.5 Privacy control 8g34.1.6 Synchronization of data storage 8g34.1.7 Access of profile from visited network . 8g34.1.8 Location of Profile Components . 8g34.1.9 Charging for profile access . 8g34.2 GUP functional entities 8g34.2.1 GUP Server . 9g34.2.1.1 Single point of access 11g
19、34.2.1.2 Location of profile components 11g34.2.1.3 Authentication of profile request . 11g34.2.1.4 Authorization of profile request 11g34.2.1.5 Synchronization of profile components 12g34.2.1.6 Additional functionality 12g34.2.2 Repository Access Function (RAF) 12g34.2.3 GUP Data Repository . 12g34
20、.2.4 Reference Points . 12g34.2.5 Applications 13g34.2.6 Message flow of using GUP . 13g34.3 Rg reference point procedures 15g34.3.1 Create procedure . 16g34.3.2 Delete procedure. 16g34.3.2a List procedure . 17g34.3.3 Modify procedure . 18g34.3.4 Query procedure . 19g34.3.5 Subscribe procedure 20g34
21、.3.6 Unsubscribe procedure . 21g34.3.7 Notify procedure . 21g34.3.8 Common information definitions 22g34.3.8.1 Requestor data . 22g34.3.8.2 Redirection data 22g34.3.9 Error handling and common error types . 22g34.4 Rp reference point procedures 23g34.4.1 Create Component procedure . 23g34.4.2 Delete
22、 Component procedure . 24g34.4.2a List Data procedure . 24g34.4.3 Modify Data procedure . 25g34.4.4 Read Data procedure . 25g3ETSI ETSI TS 123 240 V15.0.0 (2018-06)43GPP TS 23.240 version 15.0.0 Release 154.4.5 Subscribe To Data procedure 26g34.4.6 Unsubscribe To Data procedure 27g34.4.7 Notify Data
23、 procedure 27g34.4.8 Define Data procedure 28g34.4.9 Common information definitions 28g34.4.9.1 Requestor data . 28g34.4.10 Error handling and common error types . 28g35 GUP information model . 29g3Annex A (informative): Examples of 3GPP Generic User Profile usage . 32g3Annex B (informative): 3GPP G
24、eneric User Profile candidates 33g3Annex C (informative): Change history . 34g3History 35g3ETSI ETSI TS 123 240 V15.0.0 (2018-06)53GPP TS 23.240 version 15.0.0 Release 15Foreword This Technical Specification has been produced by the 3rdGeneration Partnership Project (3GPP). The contents of the prese
25、nt document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: Version x.y.z
26、 where: x the first digit: 1 presented to TSG for information; 2 presented to TSG for approval; 3 or greater indicates TSG approved document under change control. y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. z the third digit
27、 is incremented when editorial only changes have been incorporated in the document. Introduction 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 d
28、istribution 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
29、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
30、Profile provides an architecture, data description and interface with mechanisms to handle the data. ETSI ETSI TS 123 240 V15.0.0 (2018-06)63GPP TS 23.240 version 15.0.0 Release 151 Scope The present document defines the stage 2 architecture description to the 3GPP Generic User Profile (GUP), which
31、includes the elements necessary to realise the stage 1 requirements in TS 22.240 1. 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 References T
32、he 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
33、 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 3GPP TS 22.240: “Stage
34、 1 Service Requirement for the 3GPP Generic User Profile (GUP)“. 2 Liberty Discovery Service Specification, http:/www.projectliberty.org/. 3 Liberty ID-WSF SOAP Binding Specification, http:/www.projectliberty.org/. 4 Liberty ID-WSF Data Services Template, http:/www.projectliberty.org/. 5 Liberty ID-
35、WSF Security and Privacy Overview, http:/www.projectliberty.org/. 6 Liberty ID-WSF Security Mechanisms, http:/www.projectliberty.org/. 7 3GPP TS 23.141: “Presence Service; Architecture and functional description“. 3 Definitions, symbols and abbreviations 3.1 Definitions For the purposes of the prese
36、nt 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 specificat
37、ion. 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
38、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 For the purposes of the present document the following symbols apply: Rg Reference Point between Applications and the GUP Serve
39、r. Rp Reference Point between the GUP Server and GUP Data Repositories, and between Applications and GUP Data Repositories. ETSI ETSI TS 123 240 V15.0.0 (2018-06)73GPP TS 23.240 version 15.0.0 Release 153.3 Abbreviations For the purposes of the present document the following abbreviations apply: FFS
40、 For Further Study GUP 3GPP Generic User Profile HPLMN Home PLMN LCS Location servicesOSA Open Service Access PLMN Public Land Mobile Network RAF Repository Access Function UE User EquipmentXML eXtensible Markup Language 4 Reference Architecture 4.1 GUP Functionalities 4.1.1 Harmonized access interf
41、ace The GUP harmonized access interface is the interface which can be used by the GUP suppliers and GUP consumers to access, manage and transfer the profile data. This application layer interface is independent of the profile structure. 4.1.2 Single point of access There exists for each Profile a si
42、ngle point of access, which knows the location of the various components of the Profile. A discovery service, e.g. Liberty Discovery Service Specification 2 may be used to get the contact reference information for this access point if not known by other means. 4.1.3 Authentication of profile access
43、A GUP functionality exists that is responsible to authenticate applications. Authentication is a vital function to be passed before any kind of access to GUP data is granted. GUP shall adopt generic mechanisms such as used for the OSA framework approach. More specifically GUP shall use authenticatio
44、n mechanisms from Liberty Alliance Project as specified in Liberty ID-WSF Security and Privacy Overview 5, Liberty Discovery Service 2 and Liberty ID-WSF Security Mechanisms 6. 4.1.4 Authorization of profile access A GUP functionality exists that is responsible to authorise applications to access GU
45、P data based on User specific or common privacy rules. All attempts to access the GUP data are to be authorized according to the defined policies which shall include the requestor information, the requested data, the target subscriber and the performed operation, or some of those. GUP shall use auth
46、orization mechanisms from Liberty Alliance Project as specified in Liberty ID-WSF Security and Privacy Overview 5 and Liberty ID-WSF Security Mechanisms 6. The GUP data structures need to satisfy the requirement to provide the authorization information on the different levels: profile, component or
47、data element. In addition to the generic authorization data, additional service specific data may be defined (e.g. for LCS). The same applies for the authorization decision logic. The execution of the authorization logic leads to a decision whether a requestor is allowed to make the request at all,
48、and additionally to which part of data the requestor has the appropriate access rights with regard to the nature of the request. GUP provides mechanisms for the different GUP entities for managing the authorization data. Both HPLMN based applications and non-HPLMN based applications are expected to
49、send requests to the GUP Server. The GUP server shall have functionality to apply different authorization criteria, policy control and load control to HPLMN and non-HPLMN applications. Policy control and load control are out of the scope of the present document. ETSI ETSI TS 123 240 V15.0.0 (2018-06)83GPP TS 23.240 version 15.0.0 Release 154.1.5 Privacy control The tight connection of authentication, authorization and subscriber specific privacy requirements results in privacy control. Privacy control implies a centralized management for access
