1、 International Telecommunication Union ITU-T J.360TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU Amendment 1(06/2007) SERIES J: CABLE NETWORKS AND TRANSMISSION OF TELEVISION, SOUND PROGRAMME AND OTHER MULTIMEDIA SIGNALS IPCablecom IPCablecom2 architecture framework Amendment 1: New Appendix IV Home
2、 subscriber server (HSS) ITU-T Recommendation J.360 (2006) Amendment 1 ITU-T Rec. J.360 (2006)/Amd.1 (06/2007) i ITU-T Recommendation J.360 IPCablecom2 architecture framework Amendment 1 New Appendix IV Home subscriber server (HSS) Summary Appendix IV to ITU-T Recommendation J.360 provides an overvi
3、ew of the reference points for the home subscriber server (HSS) and related components. In addition, this appendix describes the specific HSS related enhancements to the 3GPP IMS Release 6 specifications to support the IPCablecom2 requirements. Source Amendment 1 to ITU-T Recommendation J.360 (2006)
4、 was agreed on 20 June 2007 by ITU-T Study Group 9 (2005-2008). ii ITU-T Rec. J.360 (2006)/Amd.1 (06/2007) FOREWORD The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU
5、Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. The World Telecommunication Standardizat
6、ion Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. In some areas of information techno
7、logy which fall within ITU-Ts purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. NOTE In this Recommendation, the expression “Administration“ is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. Complianc
8、e with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure e.g. interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words “shall“ or some other obligato
9、ry language such as “must“ and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. INTELLECTUAL PROPERTY RIGHTS ITU draws attention to the possibility that the practice or implementation o
10、f this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. As of the
11、 date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to con
12、sult the TSB patent database at http:/www.itu.int/ITU-T/ipr/. ITU 2008 All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. ITU-T Rec. J.360 (2006)/Amd.1 (06/2007) iii CONTENTS Page New Appendix IV Home subscriber s
13、erver (HSS) . 1 IV.1 Introduction and purpose 1 IV.2 References 2 IV.3 Terms and definitions. 3 IV.4 Abbreviations and acronyms 3 IV.5 IPCablecom2 home subscriber server (HSS) . 3 IV.6 IPCablecom2 HSS enhancements 7 IV.7 Non-HSS impacting requirements considered . 16 ITU-T Rec. J.360 (2006)/Amd.1 (0
14、6/2007) 1 ITU-T Recommendation J.360 IPCablecom2 architecture framework Amendment 1 New Appendix IV Home subscriber server (HSS) (This appendix does not form an integral part of this Recommendation) IV.1 Introduction and purpose This appendix provides an overview of the reference points for the home
15、 subscriber server (HSS) and related components. In addition, this appendix describes the specific HSS related enhancements to the 3GPP IMS Release 6 specifications to support the IPCablecom2 requirements. IV.1.1 Scope The IPCablecom2 architecture framework ITU-T J.360 describes the overall document
16、 organization plan for IPCablecom2. Since the IPCablecom2 HSS is closely aligned with 3GPP Release 6 IMS, the IPCablecom2 HSS normative requirements are defined in the delta specifications, which are enhanced versions of 3GPP specifications and accommodate cable-specific requirements. The IPCablecom
17、2 HSS requirements are documented in the following IMS Delta specifications: ITU-T J.366.1, ITU-T J.366.6, ITU-T J.366.5 and ITU-T J.366.10. NOTE 1 The IMS Delta specifications listed above may also contain requirements related to other portions of the IPCablecom2 architecture. NOTE 2 In the presenc
18、e of any contradictions, the IPCablecom2 specifications take precedence over this technical report. IV.1.1.1 Relationship to IPCablecom2 features and services This appendix and its associated IMS delta specifications serve as a base for the handling of subscriber related data within IPCablecom2. Thi
19、s foundation provides for the support of a wide variety of communication services, ranging from legacy telephony features to new and enhanced communication applications and services. This foundation is service independent and, therefore, requirements specific to each IPCablecom2 service and feature
20、are out-of-scope for this appendix, and defined separately in IPCablecom2 service specifications. Any requirements that are deemed to be non-service specific are included and are addressed within this appendix. IV.1.1.2 Relationship to other IPCablecom2 documents The IPCablecom2 HSS specifications t
21、ogether define the generic HSS requirements for the following general capabilities: identification handling; user profile management (Cx and non-transparent data); application specific user profile management (transparent data); service profile provisioning; 2 ITU-T Rec. J.360 (2006)/Amd.1 (06/2007)
22、 call/session establishment support; user security support; registration state management. The IPCablecom2 architecture uses these general capabilities, and, to fulfil service specific requirements, may document additional capabilities in IPCablecom2 service specifications. IV.1.2 Organization Claus
23、e IV.5 describes the IPCablecom2 HSS architecture, including the main functional elements and reference points. Clause IV.6 describes the IPCablecom2 HSS enhancements to the 3GPP Release 6 IMS specifications motivated by the IPCablecom2 architecture or service requirements. Clause IV.7 summarizes re
24、quirements considered that do not impact the HSS. IV.2 References IV.2.1 Informative references This appendix uses the following additional informative references: ITU-T E.164 ITU-T Recommendation E.164 (2005), The international public telecommunication numbering plan. ITU-T J.360 ITU-T Recommendati
25、on J.360 (2006), IPCablecom2 architecture framework. ITU-T J.366.1 ITU-T Recommendation J.366.1 (2007), Organization of subscriber data specification (3GPP TS 23.008). ITU-T J.366.5 ITU-T Recommendation J.366.5 (2007), IP multimedia (IM) subsystem Cx and Dx interfaces; signalling flows and message c
26、ontents specification (3GPP TS 29.228). ITU-T J.366.6 ITU-T Recommendation J.366.6 (2007), Cx/Dx interfaces based on the Diameter protocol specification (3GPP TS 29.229). ITU-T J.366.9 ITU-T Recommendation J.366.9 (2006), IPCablecom2 IP Multimedia Subsystem (IMS); generic authentication architecture
27、 specification (3GPP TS 33.220). ITU-T J.366.10 ITU-T Recommendation J.366.10 (2007), Zh and Zn interfaces based on the Diameter protocol; Stage 3 specification (3GPP TS 29.109). IETF RFC 2617 IETF RFC 2617 (1999), HTTP Authentication: Basic and Digest Access Authentication. IETF RFC 3261 IETF RFC 3
28、261 (2002), SIP: Session Initiation Protocol. IETF RFC 3310 IETF RFC 3310 (2002), Hypertext Transfer Protocol (HTTP) Digest Authentication Using Authentication and Key Agreement (AKA). IETF RFC 3966 IETF RFC 3966 (2004), The tel URI for Telephone Numbers. IETF RFC 4740 IETF RFC 4740 (2006), Diameter
29、 Session Initiation Protocol (SIP) Application. ID GRUU IETF draft, Obtaining and Using Globally Routable User Agent (UA) URIs (GRUU) in the Session Initiation Protocol (SIP), draft-ietf-sip-gruu-10, July 2006. ITU-T Rec. J.360 (2006)/Amd.1 (06/2007) 3 IV.2.2 Reference acquisition Internet Engineeri
30、ng Task Force (IETF), Internet: http:/www.ietf.org IV.3 Terms and definitions This appendix introduces no additional new terms. IV.4 Abbreviations and acronyms This appendix uses the following additional abbreviations and acronyms: AKA Authentication and Key Agreement AVP Attribute-Value Pair BSF Bo
31、otstrapping Server Function CNAM Calling NAMe GBA Generic Bootstrapping Architecture GUSS GBA User Security Setting IM CN IP Multimedia Core Network IMPI IM Private Identity IMPU IM Public Identity ISIM IMS Subscriber Identity Module MAA Multimedia-Auth-Answer MAR Multimedia-Auth-Request SAA Server-
32、Assignment-Answer SAR Server-Assignment-Request SIM Subscriber Identity Module UAR User-Authorization-Request UICC Universal Integrated Circuit Card XML eXtensible Markup Language IV.5 IPCablecom2 home subscriber server (HSS) The home subscriber server (HSS) is the master database containing the sub
33、scription related information for a particular user. There may be one or more HSSs in the network. When multiple HSSs are in the network, a subscription locator function (SLF) is used to locate the proper HSS. IV.5.1 IPCablecom2 HSS architecture and reference points The reference points associated w
34、ith the HSS are illustrated in Figure IV.1. These reference points are as defined in the 3GPP IMS, with appropriate enhancements identified by IPCablecom2. 4 ITU-T Rec. J.360 (2006)/Amd.1 (06/2007) J.360A.1(07)_F.IV.1DxHSSS-CSCF AS BSFSLFI-CSCFCxCxDxShDhDzZhFigure IV.1 HSS reference points The HSS p
35、rovides several logical functions needed by the various entities throughout the network in order to support session handling. Here is a list of some of the logical functions provided by the HSS: Registration state management: This function supports the management of the users registration state. Ses
36、sion establishment support: The HSS supports the session establishment procedures in the IP multimedia core network (IM CN) subsystem. For terminating traffic, it provides information on which session control entity currently hosts the user. User security information generation: The architecture sup
37、ports the storage and generation of user security credentials and parameters required for authentication. This task may be handled by the HSS or other elements in the network depending on the authentication method and network architecture being used. User security support: The HSS supports the authe
38、ntication procedures to access the IM CN subsystem services by storing the generated data for authentication, integrity, and ciphering, and by providing these data to the appropriate entity in the CN. User identification handling: The HSS provides the appropriate relations among all the identifiers
39、that uniquely determine the user in the system (private identity and public identities for IM CN subsystem). Access authorization: The HSS authorizes the user for access when requested by the call session control function (CSCF) by checking that the user is allowed to roam in a given visited network
40、. Service authorization support: The HSS provides basic authorization for terminating call/session establishment and service invocation. The HSS updates the appropriate serving entities (i.e., CSCF) with the relevant information related to the services to be provided to the user. Service profile pro
41、visioning support: The HSS provides access to the service profile data for use within the IM CN subsystem. ITU-T Rec. J.360 (2006)/Amd.1 (06/2007) 5 IV.5.1.1 HSS functional components IV.5.1.1.1 Home subscriber server (HSS) The HSS is the master database for a given user. It is the entity containing
42、 the subscription-related information to support the network entities managing sessions. A home network may contain one or more HSSs depending on the number of subscribers, the capacity of the network elements, and the organization of the network. The HSS provides support to the call control servers
43、 in order to complete the routing/roaming procedures by solving authentication, authorization, naming/addressing resolution, location dependencies, etc. The HSS is responsible for holding the following user related information: User identification, numbering and addressing information. User security
44、 information: Network access control information for authentication and authorization. User location information at inter-system level: The HSS supports the user registration, and stores inter-system location information, etc. User profile information. The HSS may generate user security information
45、for mutual authentication, communication integrity check and ciphering, depending on the authentication mechanism and the chosen architecture being used. IV.5.1.1.2 Subscription locator function (SLF) When more than one independently addressable HSS is utilized by a network operator, there is a need
46、 to associate a given subscriber with the HSS that contains the subscribers data. This functionality is provided by the SLF, which is a Diameter redirect agent. The SLF is: Queried by the interrogating call session control function (I-CSCF) during the registration and session setup to retrieve the a
47、ddress of the HSS that contains the subscriber specific data. Furthermore, the SLF is also queried by the S-CSCF during registration. Queried by the AS in conjunction with the Sh interface operation to retrieve the address of the HSS that contains the subscriber specific data. Accessed via the Dx in
48、terface by the CSCF and via the Dh interface by the AS. A single HSS environment can still be achieved when there are physically multiple HSSs by using techniques such as server farms or clustering. The SLF is not required when such techniques are used to provide a logical single HSS environment. IV
49、.5.1.2 HSS reference points The reference points depicted in Figure IV.1 are described in Table IV.1. All reference points are DIAMETER-based. 6 ITU-T Rec. J.360 (2006)/Amd.1 (06/2007) Table IV.1 Call signalling reference points Reference point IPCablecom2 network elements Reference point description I-CSCF HSS Cx S-CSCF HSS The Cx reference point supports information transfer between CSCF and HSS. The main procedures that require information transfer between CSCF and HSS are:
