ITU-T Q 3320-2010 Architectural framework for the Q 332x series of Recommendations (Study Group 11)《Q 332x系列建议的建筑框架(研究组11)》.pdf

《ITU-T Q 3320-2010 Architectural framework for the Q 332x series of Recommendations (Study Group 11)《Q 332x系列建议的建筑框架(研究组11)》.pdf》由会员分享，可在线阅读，更多相关《ITU-T Q 3320-2010 Architectural framework for the Q 332x series of Recommendations (Study Group 11)《Q 332x系列建议的建筑框架(研究组11)》.pdf（16页珍藏版）》请在麦多课文档分享上搜索。

1、 International Telecommunication Union ITU-T Q.3320TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU (03/2010) SERIES Q: SWITCHING AND SIGNALLING Signalling requirements and protocols for the NGN Resource control protocols Architectural framework for the Q.332x series of Recommendations Recommendation

2、 ITU-T Q.3320 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 THE ISDN Q.60Q.99 CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS Q.100Q

3、.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 DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 Q.850Q.999 PUBLIC LAND MOBILE

4、 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 INDEPENDENT CALL CONTROL (BICC) Q.1900Q.1999 BROADBAND ISDN Q.2000Q.2999 SIGNA

5、LLING 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.3130Q.3179 Signalling and control requirements and protocols to support

6、 attachment in NGN environments Q.3200Q.3249 Resource control protocols Q.3300Q.3369Service and session control protocols Q.3400Q.3499 Service and session control protocols supplementary services Q.3600Q.3649 NGN applications Q.3700Q.3849 Testing for NGN networks Q.3900Q.3999 For further details, pl

7、ease refer to the list of ITU-T Recommendations. Rec. ITU-T Q.3320 (03/2010) i Recommendation ITU-T Q.3320 Architectural framework for the Q.332x series of Recommendations Summary Recommendation ITU-T Q.3320 provides a framework by means of which the reader may understand the relationships between t

8、he various Recommendations of the Q.332x series. It defines the entities involved in resource control signalling and the interfaces across which signalling occurs. Appendix I provides a cross-reference between the interfaces defined in the main body of this Recommendation and the Recommendations def

9、ining the protocols operating across those interfaces. History Edition Recommendation Approval Study Group 1.0 ITU-T Q.3320 2010-03-01 11 Keywords Physical entity, RACF. ii Rec. ITU-T Q.3320 (03/2010) FOREWORD The International Telecommunication Union (ITU) is the United Nations specialized agency i

10、n 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 them with a view to s

11、tandardizing 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 Recommendations i

12、s 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 Recommendation, the expression “Administration“ is used for conciseness to

13、 indicate both a telecommunication administration and a recognized 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 ac

14、hieved 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 Recommendation is required of any party. INTELLECTU

15、AL PROPERTY RIGHTS ITU draws attention to the possibility that 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

16、 asserted by ITU members or others outside of the Recommendation 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 cauti

17、oned that 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 2010 All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of I

18、TU. Rec. ITU-T Q.3320 (03/2010) iii CONTENTS Page 1 Scope 1 2 References. 1 3 Definitions 1 3.1 Terms defined elsewhere 1 3.2 Terms defined in this Recommendation . 2 4 Abbreviations and acronyms 2 5 Conventions 2 6 Architectural specification 3 6.1 ITU-T Y.2111 functional architecture 3 6.2 Princip

19、les of mapping . 3 6.3 Implementations of functional entities . 4 6.4 Interfaces and protocols 4 Appendix I Tabulation of resource control protocol Recommendations 5 Appendix II Example of physical realization of the RACF architecture 6 Bibliography. 7 Rec. ITU-T Q.3320 (03/2010) 1 Recommendation IT

20、U-T Q.3320 Architectural framework for the Q.332x series of Recommendations 1 Scope This Recommendation specifies a concrete realization of the functional architecture defined in ITU-T Y.2111, including: the specification of the physical entities involved in resource control signalling; the interfac

21、es across which signalling takes place; and the mapping between these entities and interfaces and the corresponding functional entities and reference points in ITU-T Y.2111. Appendix I provides a table illustrating the mapping between these interfaces and the protocol specifications which realize th

22、ose interfaces. NOTE ITU-T Y.2111 (11/2008) is a Revision 1 of ITU-T Y.2111 (09/2006), which was the base for b-ITU-T Q.3300. 2 References The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation.

23、At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed

24、 below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. ITU-T Y.2111 Recommendation ITU-T Y.2111 (2008), Resource and admission control func

25、tions in next generation networks. 3 Definitions 3.1 Terms defined elsewhere This Recommendation uses the following terms defined elsewhere: 3.1.1 network attachment control entity (NACE) b-ITU-T Q.3300: A general term used to refer to a device exercising one of the network attachment control functi

26、ons (NACF) as defined in clause 7.2.2 of ITU-T Y.2111. NOTE These functions may be distributed over multiple devices, but identification of specific devices is unnecessary so long as the necessary information flows are supported over the Ru interface. 3.1.2 policy decision physical entity (PD-PE) b-

27、ITU-T Q.3300: A device that implements the policy decision functional entity (PD-FE) as defined in clause 7.2.3.2 of ITU-T Y.2111. 3.1.3 policy enforcement physical entity (PE-PE) b-ITU-T Q.3300: A device that implements the policy enforcement functional entity (PE-FE) as defined in clause 7.2.4.1 o

28、f ITU-T Y.2111. NOTE One example of such a device is a border router. 3.1.4 transport physical entity (T-PE) b-ITU-T Q.3300: A term used to refer to any device implementing the transport functions in the limited sense provided in clause 7.2.4 of ITU-T Y.2111 (i.e., those with which the RACF interact

29、s). 3.1.5 transport resource control physical entity (TRC-PE) b-ITU-T Q.3300: A device that implements the transport resource control functional entity (TRC-FE) as defined in clause 7.2.3.3 of ITU-T Y.2111. 2 Rec. ITU-T Q.3320 (03/2010) 3.1.6 transport resource enforcement physical entity (TRE-PE) b

30、-ITU-T Q.3300: A device that implements the transport resource enforcement functional entity (TRC-FE) as defined in clause 7.2.4.2 of ITU-T Y.2111. 3.2 Terms defined in this Recommendation This Recommendation defines the following term: 3.2.1 CPN gateway policy enforcement physical entity (CGPE-PE):

31、 A device that implements the CPN gateway policy enforcement functional entity (CGPE-FE) as defined in clause 7.2.4.2 of ITU-T Y.2111. 4 Abbreviations and acronyms This Recommendation uses the following abbreviations and acronyms: CGPE CPN Gateway Policy Enforcement CPN Customer Premises Network FE

32、Functional Entity NACE Network Attachment Control Entity NACF Network Attachment Control Functions PD-FE Policy Decision Functional Entity PD-PE Policy Decision Physical Entity PE Physical Entity RACF Resource Admission and Control Function SCE Service Control Entity (e.g., implementation of a P-CSC

33、F) SCF Service Control Functions (as used in ITU-T Y.2111) TF Transport Functions (as used in ITU-T Y.2111) T-PE Transport Physical Entity (e.g., a router) TRC-FE Transport Resource Control Functional Entity TRC-PE Transport Resource Control Physical Entity 5 Conventions None. Rec. ITU-T Q.3320 (03/

34、2010) 3 6 Architectural specification 6.1 ITU-T Y.2111 functional architecture Figure 6-1 illustrates the RACF functional architecture defined in ITU-T Y.2111. Taken from Figure 5 of ITU-T Y.2111. Figure 6-1 Generic resource and admission control functional architecture in NGN The relevant functiona

35、l entities are: SCF (service control functions) PD-FE (policy decision functional entity) TRC-FE (transport resource control functional entity) TRE-FE (transport resource enforcement functional entity) PE-FE (policy enforcement functional entity) CGPE-FE (CPN gateway policy enforcement functional en

36、tity) NACF (network attachment control functions) 6.2 Principles of mapping The realization presented in this Recommendation accepts the considerations of scalability and domain independence that motivated the development of the functional architecture. As a result, it maps each functional entity of

37、 the functional architecture to a separate type of physical entity. Furthermore, each reference point is assumed to map to a separate interface. At a particular interface one protocol, from a set of recommended protocols, may be used. Because the mapping between reference points and interfaces is on

38、e-to-one, each interface is named after the reference point to which it corresponds (e.g., Rs interface corresponding to the Rs reference point). Depending on the technology involved, some of the physical entities identified in this Recommendation could be combined. In such a case, each combined ent

39、ity will support the combined set of external interfaces of its component elements. Note that interfaces that would lie between the component elements if they were separate are absorbed into the interior of the combined entity. 4 Rec. ITU-T Q.3320 (03/2010) 6.3 Implementations of functional entities

40、 Table 6-1 indicates the mapping from the functional entities to the physical entities implementing them. Table 6-1 Mapping from functional to physical entities concerned with resource admission and control Functional entity Abbrev. Physical entity Abbrev. Service Control Functions SCF Service Contr

41、ol Entity (e.g., implementation of P-CSCF) SCE Network Attachment Control Functions NACF Network Attachment Control Entity NACE Policy Decision Functional Entity PD-FE Policy Decision Physical Entity PD-PE Transport Resource Control Functional Entity TRC-FE Transport Resource Control Physical Entity

42、 TRC-PE Transport Resource Enforcement Functional Entity TRE-FE Transport Resource Enforcement Physical Entity TRE-PE Transport Functions in general TF Transport Physical Entity (of various types, possibly limited by context) T-PE Policy Enforcement Functional Entity PE-FE Policy Enforcement Physica

43、l Entity PE-PE CPN Gateway Policy Enforcement Functional Entity CGPE-FE CPN Gateway Policy Enforcement Physical Entity CGPE-PE Clause 7.1 of ITU-T Y.2111 implies a number of relationships between the physical entities named in Table 6-1. These relationships are listed here and illustrated in Figure

44、II.1 below: One PD-PE may serve SCE belonging to multiple service stratum service providers (where each SCE is individually owned by a particular service provider). Multiple PD-PEs within the same domain may be interconnected via the Rd interface. One PD-PE can communicate directly with one or sever

45、al TRC-PEs belonging to the same network operators domain, and a TRC-PE may communicate directly with multiple PD-PEs. A mode of operation is possible, whereby for a specific request for the allocation of QoS resources, the PD-PE contacts a single TRC-PE. The TRC-PE then communicates to other TRC-PE

46、s via the Rp interface as required to fulfil the request. Appendix II contains an example of configuration of the physical entities identified in Table 6-1 and the interfaces between them. 6.4 Interfaces and protocols A cross-reference between the interfaces defined in this Recommendation, the proto

47、cols used at those interfaces, and the Recommendations within which those protocols are documented, is provided in Appendix I. Rec. ITU-T Q.3320 (03/2010) 5 Appendix I Tabulation of resource control protocol Recommendations (This appendix does not form an integral part of this Recommendation) Table

48、I.1 lists Recommendations which define protocols applicable to each resource control interface specified in the body of this Recommendation. Table I.1 Resource control protocol Recommendations Interface Supporting entities Protocol base (Notes) Rec. No. Rs SC-PE, PD-PE Diameter b-ITU-T Q.3321.1 Rp B

49、etween TRC-PEs RCIP TBD Rw PD-PE, PE-PE TBD COPS-PR TBD H.248 TBD Diameter TBD Rc TRC-PE, T-PE COPS-PR TBD SNMP TBD Rt PD-PE, TRC-PE Diameter TBD Rd PD-PE to PD-PE (intra-domain) Diameter b-ITU-T Q.3306.1 Ri PD-PE to PD-PE (inter-domain) Diameter b-ITU-T Q.3307.1 Rh PD-PE to CGPE-PE Interface is for further study TBD Rn TRC-PE, TRE-PE Interface is for further study NOTE 1 Diameter: b-IETF RFC 3588. NOTE 2 COPS-PR: Common Open Policy Service Policy