ETSI TR 182 005-2006 Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN) Organization of user data (V1 1 1)《电信和互联网融合业务及高级网络协议(TISPAN) .pdf

1、 ETSI TR 182 005 V1.1.1 (2006-03)Technical Report Telecommunications and Internet converged Services andProtocols for Advanced Networking (TISPAN);Organization of user dataETSI ETSI TR 182 005 V1.1.1 (2006-03) 2 Reference DTR/TISPAN-02027-NGN-R1 Keywords architecture, data, user ETSI 650 Route des L

2、ucioles 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 Individual copies of the present document can be downloaded from: h

3、ttp:/www.etsi.org The present document may be made available in more than one electronic version or in print. In any case of existing or perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF). In case of dispute, the reference shall be the

4、 printing on ETSI printers of the PDF version kept on a specific network drive within ETSI Secretariat. Users of the present document should be aware that 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 h

5、ttp:/portal.etsi.org/tb/status/status.asp If you find errors in the present document, please send your comment to one of the following services: http:/portal.etsi.org/chaircor/ETSI_support.asp Copyright Notification No part may be reproduced except as authorized by written permission. The copyright

6、and the foregoing restriction extend to reproduction in all media. European Telecommunications Standards Institute 2006. All rights reserved. DECTTM, PLUGTESTSTM and UMTSTM are Trade Marks of ETSI registered for the benefit of its Members. TIPHONTMand the TIPHON logo are Trade Marks currently being

7、registered by ETSI for the benefit of its Members. 3GPPTM is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. ETSI ETSI TR 182 005 V1.1.1 (2006-03) 3 Contents Intellectual Property Rights5 Foreword.5 1 Scope 6 2 References 6 3 Definitions and ab

8、breviations.6 3.1 Definitions6 3.2 Abbreviations .6 4 Introduction 7 4.1 Definition .7 4.2 Storage facilities.7 4.2.1 Network Attachment Functional Units .7 4.2.2 Common Components Functional Units.7 4.3 Relationship with 3GPP subscriber data 8 5 Subscriber data for IMS core subsystem8 6 Data relate

9、d to CAMEL support of IMS services 8 7 Data related to Generic Authentication Architecture .9 8 Subscriber data for I-WLAN domain.9 9 Definition of subscriber data related to access.9 9.1 Data related to Subscriber Identification9 9.1.1 Globally Unique Address Information9 9.1.1.1 Assigned IP Addres

10、s .9 9.1.1.2 Address Realm 9 9.1.2 Subscriber ID9 9.1.3 Default Subscriber ID .9 9.2 Data related to Access Identification9 9.2.1 Physical Access ID .9 9.2.2 Logical Access ID.9 9.2.3 Access Network Type.10 9.2.4 Terminal Type 10 9.3 Data related to Location Management10 9.3.1 Privacy Indicator.10 9

11、.3.2 Location Information 10 9.3.3 Geographic Location Information.10 9.4 Data related to QoS and Gate Control10 9.4.1 QoS Profile Information .10 9.4.2 Initial Gate Settings 10 9.5 Data related to Identification of other functional entities .11 9.5.1 RACS Point of Contact.11 9.5.2 CNGCF Address.11

12、9.5.3 P-CSCF Identity11 9.5.4 AF Identity11 10 Summary of data stored in location registers .11 Annex A (informative): Additional Information .12 A.1 Data related to subscription, identification and numbering12 A.1.1 User type 12 A.1.2 User Identifier 12 A.2 Data related to registration .12 A.2.1 Re

13、gistration Timestamp .12 ETSI ETSI TR 182 005 V1.1.1 (2006-03) 4 A.2.2 Application Server Identifier12 A.2.3 Event Name 12 A.2.4 Event Subscription Expire Date .12 A.2.5 Event Subscription Timestamp.12 A.3 Data related S-CSCF selection information .13 A.3.1 Dynamic Service Activation Info.13 A.4 Def

14、inition of subscriber data related to Basic services 13 A.4.1 Accounting Type 13 A.4.2 Arrearage13 A.4.3 Lawful Interception 13 A.4.4 Number portability .13 A.4.5 Carrier pre-selection.13 History 14 ETSI ETSI TR 182 005 V1.1.1 (2006-03) 5 Intellectual Property Rights IPRs essential or potentially es

15、sential to the present document 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 in ETSI SR 000 314: “Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs not

16、ified to ETSI in respect of ETSI standards“, which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web server (http:/webapp.etsi.org/IPR/home.asp). Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee c

17、an 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. Foreword This Technical Report (TR) has been produced by ETSI Technical Committee Telecommunications and Int

18、ernet converged Services and Protocols for Advanced Networking (TISPAN). ETSI ETSI TR 182 005 V1.1.1 (2006-03) 6 1 Scope The present document provides guidance concerning information, regarding NGN subscribers, to be stored in the Network. It considers the following “types“ of user data: Network att

19、achment data, to be stored in the NASS functional entities ES 282 004 3, the Profile Database Function (PDBF) and the Connectivity Session Location and Repository Function (CLF). Service attachment data (for the IMS subsystem ES 282 007 4) to be stored in the User Profile Server Function (UPSF) in t

20、he Common components in the IMS core subsystem,. This data is described in TS 123 008, clause 3 1. Data related to CAMEL support of IMS services to be stored in the User Profile Server Function (UPSF) in the Common components in the IMS core subsystem,. This data is described in TS 123 008, clause 3

21、.8 1. Data related to Generic Authentication Architecture to be stored in the User Profile Server Function (UPSF) in the Common components in the IMS core subsystem,. This data is described in TS 123 008, clause 3A 1. Subscriber data for I-WLAN domain to be stored in the User Profile Server Function

22、 (UPSF) in the Common components in the IMS core subsystem,. This data is described in TS 123 008, clause 3B 1. Subscriber data related to the PSTN Emulation subsystem (PES, or IMS based PES) is not considered in the present document. Furthermore the present document provides information whether the

23、 information is stored permanently or temporarily in the concerned functional entities. 2 References For the purposes of this Technical Report (TR), the following references apply: 1 ETSI TS 123 008: “Organization of subscriber data“. 2 ETSI TR 180 000: “Telecommunications and Internet converged Ser

24、vices and Protocols for Advanced Networking (TISPAN); NGN Terminology“. 3 ETSI ES 282 004: “Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); NGN Functional Architecture; Network Attachment Sub-System (NASS)“. 4 ETSI ES 282 007: “Telecommunications an

25、d Internet converged Services and Protocols for Advanced Networking (TISPAN); IP Multimedia Subsystem (IMS) Functional architecture“. 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions given in TR 180 000 2 apply. 3.2 Abbreviations For

26、 the purposes of the present document, the following abbreviations apply: AuC Authentication Center CLF Connectivity session Location and repository Function GGSN Gateway GPRS Support Node ETSI ETSI TR 182 005 V1.1.1 (2006-03) 7 GPRS General Packet Radio Service HLR Home Location Register IMS IP Mul

27、timedia Subsystem IN Intelligent Networks ISDN Integrated Services Digital Network NACF Network Access Configuration Function NASS Network Attachment SubSystem NGN Next Generation Network P-CSCF Proxy Call Session Control Function PDBF Profile Data Base Function PSTN Public Switched Telephony Networ

28、k S-CSCF Serving Call Session Control Function SGSN Serving GPRS Support Node UAAF User Access Authorization Function UE User Equipment UPSF User Profile Server Function VLR Visitor Location Register 4 Introduction 4.1 Definition The term subscriber data is used to designate all information associat

29、ed with a subscription which is required for service provisions, identification, authentication, routing, call handling, charging, subscriber tracing, operation and maintenance purposes. Some subscriber data are referred to as permanent subscriber data, i.e. they can only be changed by administratio

30、n means. Other data are temporary subscriber data which may change as a result of normal operation of the system. Unless shown to be conditional, all data items are considered to be mandatory. 4.2 Storage facilities 4.2.1 Network Attachment Functional Units The present document considers network att

31、achment related user data stored in the following types of functional unit: The Connectivity Session Location and Repository Function (CLF) registers the association between the IP address allocated to the UE and related network location information provided by the NACF, the association between netw

32、ork location information received from the NACF and geographical location information, stores the identity of the user / UE to which the IP address has been allocated (information received from the UAAF), as well as the user network QoS profile and user preferences regarding the privacy of location

33、information. The Profile Database Function (PDBF) is the functional entity that contains the “user network profile“ consisting of user authentication data (e.g. user identity, list of supported authentication methods, key materials), and information related to the required network access configurati

34、on. 4.2.2 Common Components Functional Units The present document considers IMS service related user data stored in the following type of common components functional unit: User Profile Server Function (UPSF) which contains all permanent subscriber data and all relevant temporary subscriber data to

35、support the call control, session management entities and service execution of the different Subsystems. NOTE: The IMS service related data is the same as the IMS service data in TS 123 008 1. ETSI ETSI TR 182 005 V1.1.1 (2006-03) 8 4.3 Relationship with 3GPP subscriber data IMSAccessAuthenticationd

36、ata 3GPP user dataIMSAccess UPSF + S-CSCF PDBF + CLF PDBFIMS 3GPP Access Authentication data NGN Access3GPP user dataTISPAN NGN user dataAuthenticationdata HSS + S-CSCF HLR + VLR + SGSN + GGSN AuCAuthentication data NGN user dataCommon Subset Figure 1: Relationship between 3GPP user data and NGN use

37、r data At the 3GPP side the IMS service related user data is stored in the HSS and the S-CSCF. The same user data at the TISPAN NGN side are stored in the UPSF. The (packet switched or GPRS) Access related user data at 3GPP side is stored in the HLR, VLR, SGSN and GGSN. The (packet switched or NASS)

38、 Access related user data at the TISPAN NGN side is stored in the PDBF and CLF. Some authentication data at 3GPP side is stored in the AuC. Similar TISPAN NGN data is stored in the PDBF. 5 Subscriber data for IMS core subsystem This clause gives guidance on the use in TISPAN NGN of the subscriber da

39、ta related to IMS core subsystem as described in the TS 123 008 1 in clause 3 Definition of data for IP Multimedia domain. All subscriber data related to IMS is used in the same way as described in TS 123 008 1. The following general comment applies: Where ever HSS is mentioned replace this with UPS

40、F. 6 Data related to CAMEL support of IMS services Although the TISPAN NGN architecture foresees the use of IN in order to support some services, the support of IMS services based on CAMEL can not be excluded. In fact TISPAN NGN services can be accessed from a 3GPP IP-CAN. Consequently the data rela

41、ted to CAMEL for the support of IMS services is relevant to be included in the UPSF. ETSI ETSI TR 182 005 V1.1.1 (2006-03) 9 7 Data related to Generic Authentication Architecture Since the TISPAN NGN architecture endorses the Generic Authentication Architecture as described by 3GPP the data related

42、to Generic Authentication Architecture is relevant to be included in the UPSF. 8 Subscriber data for I-WLAN domain Since the TISPAN NGN architecture endorses I-WLAN IP-CAN as defined by 3GPP the data related to I-WLAN is relevant to be included in the UPSF. 9 Definition of subscriber data related to

43、 access This clause describes the subscriber data related to the access. These data are taken from ES 282 004 3. This has to be intended as an informative description of access data: for every discrepancy between this text and the text in ES 282 004 3, ES 282 004 3 remains the normative reference. 9

44、.1 Data related to Subscriber Identification 9.1.1 Globally Unique Address Information 9.1.1.1 Assigned IP Address The Assigned IP Address is the IP address of the attached user equipment as allocated by the NACF. The Assigned IP Address is stored temporarily in the CLF. 9.1.1.2 Address Realm The Ad

45、dress Realm is the addressing domain in which the IP address is significant The Address Realm is allocated by the NACF and stored temporarily in the CLF. 9.1.2 Subscriber ID The Subscriber Id is the identity of the attached user. The Subscriber ID is stored permanently in the PDBF and is stored temp

46、orarily in the CLF. 9.1.3 Default Subscriber ID The Default Subscriber ID is used to query the UAAF in case no Subscriber ID is received from the UAAF. The Default Subscriber ID is stored permanently in the CLF. 9.2 Data related to Access Identification 9.2.1 Physical Access ID The Physical Access I

47、D is the identity of the physical access to which the user equipment is connected. The Physical Access ID is stored temporarily in the CLF. 9.2.2 Logical Access ID The Logical Access ID is the identity of the logical access used by the attached user equipment. In the xDSL case, the Logical Access ID

48、 may explicitly contain the identity of the port, VP and/or VC carrying the traffic. The Logical Access ID is stored temporarily in the CLF. ETSI ETSI TR 182 005 V1.1.1 (2006-03) 109.2.3 Access Network Type The Access Network Type is the type of access network over which IP connectivity is provided

49、to the user equipment. The Access Network Type is derived from the Logical Access ID and is stored permanently in the CLF. 9.2.4 Terminal Type The Terminal Type is the type of user equipment to which the IP address has been allocated. The Terminal Type is stored temporarily in the CLF. 9.3 Data related to Location Management 9.3.1 Privacy Indicator The Privacy Indicator indicates whether location information can be exported to services and applications. It provides an indication whether applications can access location informat