ITU-T SERIES Q SUPP 58-2008 Organization of NGN transport user data (Study Group 11)《下一代网络传输用户数据的组织 研究小组11》.pdf

《ITU-T SERIES Q SUPP 58-2008 Organization of NGN transport user data (Study Group 11)《下一代网络传输用户数据的组织 研究小组11》.pdf》由会员分享，可在线阅读，更多相关《ITU-T SERIES Q SUPP 58-2008 Organization of NGN transport user data (Study Group 11)《下一代网络传输用户数据的组织 研究小组11》.pdf（18页珍藏版）》请在麦多课文档分享上搜索。

1、 International Telecommunication Union ITU-T Series QTELECOMMUNICATION STANDARDIZATION SECTOR OF ITU Supplement 58(01/2008) SERIES Q: SWITCHING AND SIGNALLING Organization of NGN transport user data ITU-T Q-series Recommendations Supplement 58 ITU-T Q-SERIES RECOMMENDATIONS SWITCHING AND SIGNALLING

2、SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE Q.1Q.3 INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING Q.4Q.59 FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN Q.60Q.99 CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS Q.100Q.119 SPECIFICATIONS OF SIGNALLING SYSTEMS No. 4, 5, 6, R1 AND R2 Q.120

3、Q.499 DIGITAL EXCHANGES Q.500Q.599 INTERWORKING OF SIGNALLING SYSTEMS Q.600Q.699 SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 Q.700Q.799 Q3 INTERFACE Q.800Q.849 DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 Q.850Q.999 PUBLIC LAND MOBILE NETWORK Q.1000Q.1099 INTERWORKING WITH SATELLITE MOBILE SYSTEMS Q.110

4、0Q.1199 INTELLIGENT NETWORK Q.1200Q.1699 SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2000 Q.1700Q.1799 SPECIFICATIONS OF SIGNALLING RELATED TO BEARER INDEPENDENT CALL CONTROL (BICC) Q.1900Q.1999 BROADBAND ISDN Q.2000Q.2999 SIGNALLING REQUIREMENTS AND PROTOCOLS FOR THE NGN Q.3000Q.3999 For further

5、details, please refer to the list of ITU-T Recommendations. Q series Supplement 58 (01/2008) i Supplement 58 to ITU-T Q-series Recommendations Organization of NGN transport user data Summary This supplement provides NGN transport user data while defining its structure with the parameters, incorporat

6、ing those defined in ITU-T Recommendation Y.2014. Those categorized here are transport user profile identification, access identification, location management, transport resource subscription, default configuration, access authentication, identification of other functional entities, mobility and eve

7、nt management. Source Supplement 58 to ITU-T Q-series Recommendations was agreed on 23 January 2008 by ITU-T Study Group 11 (2005-2008). Keywords NGN, transport user data, user data. ii Q series Supplement 58 (01/2008) FOREWORD The International Telecommunication Union (ITU) is the United Nations sp

8、ecialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU 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 the

9、m with a view to standardizing telecommunications on a worldwide basis. The World Telecommunication Standardization 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

10、 Recommendations is covered by the procedure laid down in WTSA Resolution 1. In some areas of information technology which fall within ITU-Ts purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. NOTE In this publication, the expression “Administration“ is used for

11、 conciseness to indicate both a telecommunication administration and a recognized operating agency. Compliance with this publication is voluntary. However, the publication may contain certain mandatory provisions (to ensure e.g., interoperability or applicability) and compliance with the publication

12、 is achieved when all of these mandatory provisions are met. The words “shall“ or some other obligatory 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 publication is required of any party. INTELLE

13、CTUAL PROPERTY RIGHTS ITU draws attention to the possibility that the practice or implementation of this publication 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

14、 asserted by ITU members or others outside of the publication development process. As of the date of approval of this publication, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this publication. However, implementers are cautioned that

15、 this may not represent the latest information and are therefore strongly urged to consult 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. Q ser

16、ies Supplement 58 (01/2008) iii CONTENTS Page 1 Scope 1 1.1 Relationship 1 2 References. 1 3 Definitions 1 3.1 Terms defined elsewhere 1 3.2 Terms defined in this supplement. 1 4 Abbreviations and acronyms 2 5 Conventions 2 6 Generic requirements on NGN transport user data. 2 7 User data for authent

17、ication and authorization of network access . 2 7.1 Data related to access authentication 2 7.2 Data related to access authorization . 3 8 User data for access network configuration 3 8.1 Data related to transport user profile identification 3 8.2 Data related to access identification. 3 8.3 Data re

18、lated to location management . 4 8.4 Data related to transport resource subscription 4 8.5 Data related to default configuration (optional) . 5 8.6 Data related to access authentication 5 8.7 Data related to identification of other functional entities. 5 8.8 Data related to mobility 6 8.9 Data relat

19、ed to event management . 6 9 Summary of data stored in transport functional entities. 6 Appendix I Illustration of the relationship of IDs in transport user data 9 Q series Supplement 58 (01/2008) 1 Supplement 58 to ITU-T Q-series Recommendations Organization of NGN transport user data 1 Scope The s

20、cope of this supplement is to define data structure and parameters information of transport user data. 1.1 Relationship Work for this supplement is based upon the context of ITU-T Y.2014 and ITU-T Y.2012; this supplement complies with the information model and message exchanged between transport str

21、atum FEs which are specified in ITU-T Y.2014, and the functional requirements and architecture specified in ITU-T Y.2012. 2 References ITU-T Y.2011 ITU-T Recommendation Y.2011 (2004), General principles and general reference model for Next Generation Networks. ITU-T Y.2012 ITU-T Recommendation Y.201

22、2 (2006), Functional requirements and architecture of the NGN release 1. ITU-T Y.2014 ITU-T Recommendation Y.2014 (2008), Network attachment control functions in next generation networks. ITU-T Y.2000-Sup.1 ITU-T Y.2000-series Supplement 1 (2006), ITU-T Y.2000 series Supplement on NGN release 1 scop

23、e. ETSI TR 182 005 ETSI TR 182 005 V1.1.1 (2006), Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Organization of user data. ETSI ES 282 004 ETSI ES 282 004 (2008), NGN Functional Architecture; Network Attachment SubSystem (NASS). 3 Definitions 3.1

24、Terms defined elsewhere This Supplement uses the following terms defined elsewhere: 3.1.1 NGN transport stratum ITU-T Y.2011: That part of the NGN which provides the user functions that transfer data and the functions that control and manage transport resources to carry such data between terminating

25、 entities. 3.2 Terms defined in this supplement This supplement defines the following terms: 3.2.1 user data: All information that specifies identification, authentication, subscribed services, service provisions, access configuration, location management, routing and charging for the NGN user. Some

26、 user data are managed as permanent, i.e., they can only be changed by administration means, and other data are temporary which may change as a result of normal operation of the system. 2 Q series Supplement 58 (01/2008) 3.2.2 transport user data: User data that is stored, handled and maintained by

27、the functional entities in the transport stratum. 4 Abbreviations and acronyms This supplement uses the following abbreviations and acronyms: CPE Customer Premises Equipment HGW Home Gateway HGWC-FE Home Gateway Configuration Functional Entity ID Identifier IMS IP Multimedia Subsystem NACF Network A

28、ttachment Control Function P-CSCF Proxy-Call Session Control Function RACF Resource and Admission Control Function SCF Service Control Function SUP-FE Service User Profile Functional Entity TAA-FE Transport Authentication and Authorization Functional Entity TLM-FE Transport Location Management Funct

29、ional Entity TUP-FE Transport User Profile Functional Entity VCI Virtual Channel Identifier VPI Virtual Path Identifier xDSL x Digital Subscriber Line 5 Conventions There is no particular notation, style, presentation or other conventions used within this supplement. 6 Generic requirements on NGN tr

30、ansport user data The transport stratum needs to authenticate and authorize the user to access the network as the network resource is only available for authenticated users. Also, transport stratum should be able to provide related user data to other control functions. Service stratum may need to kn

31、ow the users location and access network type, and RACF will require transport resource subscription information from it. 7 User data for authentication and authorization of network access 7.1 Data related to access authentication When a user accesses the network, the network needs to authenticate t

32、he user, and then to decide whether to authorize the user to use the network. The data related to access authentication includes the user identity, supported authentication methods and authentication keys. In case of xDSL, for example, the web-based authentication method may be provided. A user is r

33、edirected to a web authentication page, and a user name and password are required. The access network will authenticate the user according to the information provided by the user. Q series Supplement 58 (01/2008) 3 7.2 Data related to access authorization When a user is authenticated to access the n

34、etwork, the network should authorize the user to use the network resources according to the subscription and the current status of the network. The data includes the transport resource subscription information. 8 User data for access network configuration 8.1 Data related to transport user profile i

35、dentification 8.1.1 Transport subscriber identifier The transport subscriber identifier is a globally unique identifier of the CPE requesting IP connectivity. This identifier is used for locating the transport subscription information for the CPE. The transport subscriber identifier is also used as

36、the user identity for transport stratum authentication. 8.1.2 Default transport subscriber identifier The default transport subscriber identifier is used to query the TAA-FE in case no transport subscriber identifier is received from the TAA-FE. The default transport subscriber identifier is derived

37、 from the physical connection identifier. 8.1.3 Sub-profile identifier This transport user profile may be sub-divided into sub-profiles. The sub-profile identifier identifies sub-profiles, each of which is associated to one or more logical connection identifiers. 8.2 Data related to access identific

38、ation 8.2.1 Unique IP address The unique IP address is the IP address of the attached CPE allocated by NACF. 8.2.2 Address realm The address realm is the addressing domain in which the assigned IP address is significant. The address realm is managed by the NACF. In case IPv4 is used, unique IP addre

39、ss combined with address realm uniquely identifies address information of the user equipment globally. In case IPv6 is used, unique IP address is enough to identify the globally unique address information of the CPE. 8.2.3 Physical connection identifier The physical connection identifier is the iden

40、tity of the physical access to which the CPE is connected. In case of xDSL, the physical connection identifier identifies the copper line. 8.2.4 Logical connection identifier The logical connection identifier is used to identify a pipe carrying service traffic. It is the identity of the logical acce

41、ss used by the attached CPE. In case of xDSL, the logical connection identifier may explicitly contain the identity of the port, VPI and/or VCI carrying the traffic. 8.2.5 Type of access transport network The type of access transport network is the type of access network over which IP connectivity i

42、s provided to the CPE. It is derived from the logical connection identifier. 8.2.6 CPE type The CPE type is the type of CPE to which the IP address is allocated. 4 Q series Supplement 58 (01/2008) 8.3 Data related to location management 8.3.1 Privacy indicator The privacy indicator indicates whether

43、 location information can be exported to services and applications depending on the subscribers security level. The privacy indicator is stored in TUP-FE permanently, and in TLM-FE temporarily. 8.3.2 Location information The location information is derived from the physical connection identifier and

44、 is stored temporarily in the TLM-FE. 8.3.3 Geographic location information (optional) The geographic location information is stored temporarily in the TLM-FE. 8.4 Data related to transport resource subscription The transport resource subscription data may contain one or more sets of the following i

45、nformation elements. 8.4.1 Transport subscription profile identifier The transport subscription profile identifier is the identifier of a set of transport profile information. 8.4.2 Transport subscription profile description The transport subscription profile description is the description of a set

46、of transport subscription profile information. Either the transport subscription profile identifier or the transport subscription profile description may be presented, but not both at the same time. 8.4.3 Network class of service The network class of service is the network service class subscribed b

47、y the attached CPE. 8.4.4 Subscribed upstream bandwidth The subscribed upstream bandwidth is the maximum amount of the bandwidth subscribed by the attached CPE in the uplink direction. 8.4.5 Subscribed downstream bandwidth The subscribed downstream bandwidth is the maximum amount of the bandwidth su

48、bscribed by the attached CPE in the downlink direction. 8.4.6 Level of priority The level of priority is the maximum priority allowed for any reservation request. 8.4.7 Requestor name The requestor name identifies the requestors that are allowed to request resources for the transport resource subscr

49、iption. 8.5 Data related to default configuration (optional) 8.5.1 Default configuration identifier The default configuration identifier is the identifier for default configuration. Q series Supplement 58 (01/2008) 5 8.5.2 Default configuration description The default configuration description is the description of a default configuration. Either the default configuration identifier or the default configuration description may be presented, but not both at the same time. 8.5.3 Default access control List: allowed de