ITU-T Q 3220-2010 Architectural framework for NACF signalling interface Recommendations (Study Group 11)《网络附件控制功能(NACF)信令接口推荐性规范的体系结构框架 11号研究组》.pdf

《ITU-T Q 3220-2010 Architectural framework for NACF signalling interface Recommendations (Study Group 11)《网络附件控制功能(NACF)信令接口推荐性规范的体系结构框架 11号研究组》.pdf》由会员分享，可在线阅读，更多相关《ITU-T Q 3220-2010 Architectural framework for NACF signalling interface Recommendations (Study Group 11)《网络附件控制功能(NACF)信令接口推荐性规范的体系结构框架 11号研究组》.pdf（20页珍藏版）》请在麦多课文档分享上搜索。

1、 International Telecommunication Union ITU-T Q.3220TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU (06/2010) SERIES Q: SWITCHING AND SIGNALLING Signalling requirements and protocols for the NGN Signalling and control requirements and protocols to support attachment in NGN environments Architectural

2、framework for NACF signalling interface Recommendations Recommendation ITU-T Q.3220 ITU-T Q-SERIES RECOMMENDATIONS SWITCHING AND SIGNALLING 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

3、 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.120Q.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 DI

4、GITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 Q.850Q.999 PUBLIC LAND MOBILE NETWORK Q.1000Q.1099 INTERWORKING WITH SATELLITE MOBILE SYSTEMS Q.1100Q.1199 INTELLIGENT NETWORK Q.1200Q.1699 SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2000 Q.1700Q.1799 SPECIFICATIONS OF SIGNALLING RELATED TO BEARER INDEPEND

5、ENT CALL CONTROL (BICC) Q.1900Q.1999 BROADBAND ISDN Q.2000Q.2999 SIGNALLING REQUIREMENTS AND PROTOCOLS FOR THE NGN Q.3000Q.3999 General Q.3000Q.3029 Network signalling and control functional architecture Q.3030Q.3099 Network data organization within the NGN Q.3100Q.3129 Bearer control signalling Q.3

6、130Q.3179 Signalling and control requirements and protocols to support attachment in NGN environments Q.3200Q.3249Resource control protocols Q.3300Q.3369 Service and session control protocols Q.3400Q.3499 Service and session control protocols supplementary services Q.3600Q.3649 NGN applications Q.37

7、00Q.3849 Testing for NGN networks Q.3900Q.3999 For further details, please refer to the list of ITU-T Recommendations. Rec. ITU-T Q.3220 (06/2010) i Recommendation ITU-T Q.3220 Architectural framework for NACF signalling interface Recommendations Summary Recommendation ITU-T Q.3220 provides a framew

8、ork by means of which the reader may understand the relationships between the Q.322x and Q.323x series of ITU-T Recommendations dedicated to the realization of NACF signalling interfaces. It defines the entities involved in the network attachment control signalling and the interfaces across which th

9、is signalling takes place. History Edition Recommendation Approval Study Group 1.0 ITU-T Q.3220 2010-06-13 11 ii Rec. ITU-T Q.3220 (06/2010) FOREWORD The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communica

10、tion 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 them with a view to standardizing telecommunications on a worldwide basis. The Wo

11、rld 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 Recommendations is covered by the procedure laid down in WTSA Resolution 1. I

12、n 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 Recommendation, the expression “Administration“ is used for conciseness to indicate both a telecommunication administration and a reco

13、gnized operating agency. Compliance 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 w

14、ords “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 Recommendation is required of any party. INTELLECTUAL PROPERTY RIGHTS ITU draws attention to the possibility th

15、at the practice or implementation of 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 Recommenda

16、tion development process. As of the 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

17、are therefore strongly urged to consult the TSB patent database at http:/www.itu.int/ITU-T/ipr/. ITU 2010 All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. Rec. ITU-T Q.3220 (06/2010) iii CONTENTS Page 1 Scope 1

18、2 References. 1 3 Definitions 1 3.1 Terms defined elsewhere 1 3.2 Terms defined in this Recommendation . 1 4 Abbreviations 2 5 Conventions 4 6 NACF architectural specification . 4 6.1 NACF functional architecture 4 6.2 Principles of mapping . 5 6.3 Implementations of functional entities . 5 6.4 Inte

19、rfaces and protocols 6 7 NACF revision 1 architectural specification 6 7.1 NACF revision 1 functional architecture . 6 7.2 Principles of mapping . 8 7.3 Implementations of functional entities . 8 7.4 Interfaces and protocols 9 Appendix I Tabulation of NACF Recommendations . 10 Appendix II Tabulation

20、 of NACF revision 1 Recommendations . 11 Bibliography. 12 Rec. ITU-T Q.3220 (06/2010) 1 Recommendation ITU-T Q.3220 Architectural framework for NACF signalling interface Recommendations 1 Scope This Recommendation specifies a concrete realization of the functional architecture of the network attachm

21、ent control functions (NACF), including the specification of the physical entities involved in network attachment control signalling, the interfaces across which signalling takes place, and the mapping between these entities and interfaces and the corresponding functional entities and reference poin

22、ts. 2 References The following ITU-T Recommendations and other references contain provisions which, through references in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to re

23、vision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within th

24、is Recommendation does not give it, as a stand-alone document, the status of a Recommendation. ITU-T Y.2014-2008 Recommendation ITU-T Y.2014 (2008), Network attachment control functions in next generation networks. ITU-T Y.2014-2010 Recommendation ITU-T Y.2014 (2010), Network attachment control func

25、tions in next generation networks. ITU-T Y.2018 Recommendation ITU-T Y.2018 (2009), Mobility management and control framework and architecture within the NGN transport stratum. 3 Definitions 3.1 Terms defined elsewhere This Recommendation uses the following terms defined elsewhere: 3.1.1 network att

26、achment control entity (NACE): b-ITU-T Q.3300. 3.1.2 policy decision physical entity (PD-PE): b-ITU-T Q.3300. 3.1.3 policy enforcement physical entity (PE-PE): b-ITU-T Q.3300. 3.2 Terms defined in this Recommendation This Recommendation defines the following terms: 3.2.1 access management physical e

27、ntity (AM-PE): A device that implements the network access management functional entity (AM-FE) as defined in clause 7.2.2 of ITU-T Y.2014-2010. 3.2.2 access relay physical entity (AR-PE): A device that implements the access relay functional entity (AR-FE) as defined in clause 7.2.7 of ITU-T Y.2014-

28、2010. 3.2.3 handover decision and control physical entity (HDC-PE): A device that implements the handover decision and control functional entity (HDC-FE) as defined in clause 6.4.2 of ITU-T Y.2018. 2 Rec. ITU-T Q.3220 (06/2010) 3.2.4 home gateway configuration physical entity (HGWC-PE): A device tha

29、t implements the home gateway configuration functional entity (HGWC-FE) as defined in clause 7.2.6 of ITU-T Y.2014-2010. 3.2.5 mobile location management physical entity (MLM-PE): A device that implements the mobility location management functional entity (MLM-FE) as defined in clause 6.4.1 of ITU-T

30、 Y.2018. 3.2.6 mobility management control entity (MMCE): A general term used to refer to a device exercising one of the mobility management and control functions (MMCF) as defined in clause 6.3.3 of ITU-T Y.2018. NOTE These functions may be distributed over multiple devices, but identification of s

31、pecific devices is unnecessary so long as the necessary information flows are supported over the M1, M2 and M13 interfaces. 3.2.7 network access configuration physical entity (NAC-PE): A device that implements the network access configuration functional entity (NAC-FE) as defined in clause 7.2.1 of

32、ITU-T Y.2014-2010. 3.2.8 network information distribution physical entity (NID-PE): A device that implements the network information distribution functional entity (NID-FE) as defined in clause 6.4.3 of ITU-T Y.2018. 3.2.9 resource and administration control entity (RACE): A general term used to ref

33、er to a device exercising one of the resource and administration control functions (RACF) as defined in clause 7.1 of ITU-T Y.2014-2010. NOTE These functions may be distributed over multiple devices, but identification of specific devices is unnecessary so long as the necessary information flows are

34、 supported over the Ru interface. 3.2.10 service control entity (SCE): A general term used to refer to a device exercising one of the service control functions (SCF) as defined in clause 7.1 of ITU-T Y.2014-2010. NOTE These functions may be distributed over multiple devices, but identification of sp

35、ecific devices is unnecessary so long as the necessary information flows are supported over the S-TC1 interface. 3.2.11 transport authentication and authorization physical entity (TAA-PE): A device that implements the transport authentication and authorization functional entity (TAA-FE) as defined i

36、n clause 7.2.4 of ITU-T Y.2014-2010. 3.2.12 transport location management physical entity (TLM-PE): A device that implements the transport location management functional entity (TLM-FE) as defined in clause 7.2.3 of ITU-T Y.2014-2010. 3.2.13 transport user profile physical entity (TUP-PE): A device

37、that implements the transport user profile functional entity (TUP-FE) as defined in clause 7.2.5 of ITU-T Y.2014-2010. 4 Abbreviations This Recommendation uses the following abbreviations and acronyms: AM-FE Access Management Functional Entity AM-PE Access Management Physical Entity AR-FE Access Rel

38、ay Functional Entity AR-PE Access Relay Physical Entity CPE Customer Premises Equipment HDC-FE Handover Decision and Control Functional Entity HDC-PE Handover Decision and Control Physical Entity Rec. ITU-T Q.3220 (06/2010) 3 HGW Home Gateway HGWC-FE Home Gateway Configuration Functional Entity HGWC

39、-PE Home Gateway Configuration Physical Entity HTTP HyperText Transfer Protocol IMS IP Multimedia Subsystem IP Internet Protocol MLM-FE Mobile Location Management Functional Entity MLM-FE(P) An Instance of the MLM-FE performing the proxy mobile location management role MLM-PE Mobile Location Managem

40、ent Physical Entity MLM-PE(P) An Instance of the MLM-PE performing the proxy mobile location management role MMCE Mobility Management Control Entity MMCF Mobility Management and Control Functions NACE Network Attachment Control Entity NACF Network Attachment Control Functions NAC-FE Network Access C

41、onfiguration Functional Entity NAC-PE Network Access Configuration Physical Entity NGN Next Generation Networks NID-FE Network Information Distribution Functional Entity NID-PE Network Information Distribution Physical Entity P-CSCF Proxy-Call Session Control Function PD-FE Policy Decision Functiona

42、l Entity PD-PE Policy Decision Physical Entity PE-FE Policy Enforcement Functional Entity RACE Resource and Admission Control Entity RACF Resource and Admission Control Functions SCE Service Control Entity SCF Service Control Functions TAA-FE Transport Authentication and Authorization Functional Ent

43、ity TAA-PE Transport Authentication and Authorization Physical Entity TE Terminal Equipment TLM-FE Transport Location Management Functional Entity TLM-PE Transport Location Management Physical Entity TUP-FE Transport User Profile Functional Entity TUP-PE Transport User Profile Physical Entity 4 Rec.

44、 ITU-T Q.3220 (06/2010) 5 Conventions This Recommendation does not make use of specific conventions. 6 NACF architectural specification 6.1 NACF functional architecture Figure 6-1 illustrates the NACF functional architecture in the first version of ITU-T Y.2014 (2008). Transport FunctionsOther NGNsP

45、D-FEAR-FECPEHGWC-FETUP-FEAM-FENAC-FETC-UxTC-T1NaNdNkRuNeNcNbNxService Control FunctionsS-TC1TAA-FENiTLM-FENgT-U1TE HGWRACFNACFPE-FEFigure 6-1 NACF functional architecture The NACF comprises the following functional entities: Network access configuration functional entity (NAC-FE). Access management

46、functional entity (AM-FE). Transport location management functional entity (TLM-FE). Transport authentication and authorization functional entity (TAA-FE). Transport user profile functional entity (TUP-FE). Home gateway configuration functional entity (HGWC-FE). The NACF has interaction with the fol

47、lowing NGN components and entities: Service control functions (SCF) (e.g., such as those of the IMS service component) at the S-TC1 reference point for exporting information on access sessions. Resource and admission control functions (RACF) at the Ru reference point for exporting transport subscrip

48、tion profile information. Transport functions (i.e., access relay functional entity (AR-FE) acting as relays to/from the CPE for address allocation, authentication and authorization purposes (TC-T1 and T-U1 reference points). Rec. ITU-T Q.3220 (06/2010) 5 The customer premises equipment (CPE) at the

49、 TC-Ux reference point for configuration purposes. One or more functional entities may be mapped onto a single physical entity. If one functional entity is implemented by two physical entities, the interface between these physical entities is outside the scope of standardization. Administrative domains are not represented in Figure 6-1. Functional entities in the NACF may be distributed over two administrative domains. The NGN architecture does not require