1、 International Telecommunication Union ITU-T Y.2122TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU Amendment 1(11/2011) SERIES Y: GLOBAL INFORMATION INFRASTRUCTURE, INTERNET PROTOCOL ASPECTS AND NEXT-GENERATION NETWORKS Next Generation Networks Quality of Service and performance Flow aggregate infor
2、mation exchange functions in NGN Amendment 1: Information model Recommendation ITU-T Y.2122 (2009) Amendment 1 ITU-T Y-SERIES RECOMMENDATIONS GLOBAL INFORMATION INFRASTRUCTURE, INTERNET PROTOCOL ASPECTS AND NEXT-GENERATION NETWORKS GLOBAL INFORMATION INFRASTRUCTURE General Y.100Y.199 Services, appli
3、cations and middleware Y.200Y.299 Network aspects Y.300Y.399 Interfaces and protocols Y.400Y.499 Numbering, addressing and naming Y.500Y.599 Operation, administration and maintenance Y.600Y.699 Security Y.700Y.799 Performances Y.800Y.899 INTERNET PROTOCOL ASPECTS General Y.1000Y.1099 Services and ap
4、plications Y.1100Y.1199 Architecture, access, network capabilities and resource management Y.1200Y.1299 Transport Y.1300Y.1399 Interworking Y.1400Y.1499 Quality of service and network performance Y.1500Y.1599 Signalling Y.1600Y.1699 Operation, administration and maintenance Y.1700Y.1799 Charging Y.1
5、800Y.1899 IPTV over NGN Y.1900Y.1999 NEXT GENERATION NETWORKS Frameworks and functional architecture models Y.2000Y.2099 Quality of Service and performance Y.2100Y.2199Service aspects: Service capabilities and service architecture Y.2200Y.2249 Service aspects: Interoperability of services and networ
6、ks in NGN Y.2250Y.2299 Numbering, naming and addressing Y.2300Y.2399 Network management Y.2400Y.2499 Network control architectures and protocols Y.2500Y.2599 Smart ubiquitous networks Y.2600Y.2699 Security Y.2700Y.2799 Generalized mobility Y.2800Y.2899 Carrier grade open environment Y.2900Y.2999 Fut
7、ure networks Y.3000Y.3099 For further details, please refer to the list of ITU-T Recommendations. Rec. ITU-T Y.2122 (2009)/Amd.1 (11/2011) i Recommendation ITU-T Y.2122 Flow aggregate information exchange functions in NGN Amendment 1 Information model Summary Recommendation ITU-T Y.2122 specifies th
8、e requirements for flow aggregate information exchange functions (FIXF) in NGNs. This Amendment extends ITU-T Y.2122 and defines the information model for the FIXF. The information model represents the data structure of the flow aggregate (FA) table entry defined in ITU-T Y.2122. It is essential for
9、 FA information to be exchanged in an unambiguous way. History Edition Recommendation Approval Study Group 1.0 ITU-T Y.2122 2009-06-29 13 1.1 ITU-T Y.2122 (2009) Amd. 1 2011-11-29 13 ii Rec. ITU-T Y.2122 (2009)/Amd.1 (11/2011) FOREWORD The International Telecommunication Union (ITU) is the United Na
10、tions specialized 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 Recommendation
11、s on them 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
12、of ITU-T 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 Recommendation, the expression “Administration“
13、is used for conciseness to 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 wi
14、th the Recommendation 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 Recommendation is requir
15、ed of any party. INTELLECTUAL 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 Intellectu
16、al Property Rights, whether 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. Howe
17、ver, implementers are cautioned 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 2012 All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the pr
18、ior written permission of ITU. Rec. ITU-T Y.2122 (2009)/Amd.1 (11/2011) iii Table of Contents Page 1) Clause 3, Definitions 1 2) Clause 4, Abbreviations and acronyms 1 3) Clauses 9 and 10 . 1 4) New Appendix VIII 4 5) New Appendix IX . 4 Rec. ITU-T Y.2122 (2009)/Amd.1 (11/2011) 1 Recommendation ITU-
19、T Y.2122 Flow aggregate information exchange functions in NGN Amendment 1 Information model 1) Clause 3, Definitions Add the following new definitions to clause 3 and list them in alphabetical order: 3.3bis FIXF entity: One of the three functional entities, i.e., the FIE-FE, the FIG-FE, or the FIM-F
20、E, defined in flow aggregate information exchange (FIXF). 3.5bis flow aggregate information element: A protocol and encoding-independent description of attributes about the characteristics (e.g., the total number of flows) and treatments (e.g., number of hops in the aggregation region) of a specific
21、 flow aggregate (FA), an arbitrary collection of multiple FAs, or an aggregation region. 3.5ter flow aggregate information model: An abstraction and representation of the entities regarding flow aggregates, their properties, attributes and operations, and the way that they relate to each other. NOTE
22、 Flow aggregate information model is independent of protocol, encoding, or implementation. 3.8bis information model: An abstraction and representation of the entities in a managed environment as well as their properties, attributes and operations, and way of relating to each other. NOTE Information
23、model is independent of any specific repository, application, protocol or platform. 2) Clause 4, Abbreviations and acronyms Add the following new abbreviations and acronyms to clause 4: IE Information Element T.E Table Entry 3) Clauses 9 and 10 Renumber existing clause 9, Security considerations, as
24、 clause 10, and add the following text as a new clause 9: 9 Information model FIXF entities are required to support the information model defined in this clause. 9.1 The structure of FA information message and FA table The FIXF information model has a hierarchical data structure with entities such a
25、s FA information message, FA table, FA table entry, sets, and FA information elements (IEs). Figure 9-1 describes the hierarchical structure of the FIXF information model. FA IE is the basic building block of the data structure. Sets are either composed of a set of IE identifiers or a set of IE valu
26、es. The FA information message and FA table entry (T.E) are composed of the sets. The FA table is composed of the T.Es. Descriptions of each item are given in separate clauses. 2 Rec. ITU-T Y.2122 (2009)/Amd.1 (11/2011) .Y.2122(09)-Amd.1(11)_F9-1FA informationelement (IE)Template setName IE IDData t
27、ypeStatusOptional propertiesIE IDIE IDHeaderHeader (includingtemplate set ID)IE value IE valueData setTemplate setTemplate setData setData setHeader (includingFA ID)Header (includingFA ID)T.EFA tableFA tableentry (T.E)FA informationmessageT.E T.E.Figure 9-1 The hierarchical structure of the FIXF inf
28、ormation model 9.1.1 FA information elements and sets FA IEs capture attributes of a specific flow aggregate, an arbitrary collection of multiple FAs, or an aggregation region (AR). An attribute may be either a characteristic (e.g., the total number of flows) or a treatment (e.g., number of hops in
29、the aggregation region). FA IE is required to be the basic entity of the FA information model hierarchy. FA IE is required to have the mandatory and optional properties (see clause 9.2). FA IE is also required to have the identifier associated with it. The IEs may be distributed from a central entit
30、y or dynamically decided among the entities. The determination and distribution mechanisms are out of scope of this Recommendation. Examples of the IE can be seen in Appendix VIII. How an IE is encoded is also out of the scope of this Recommendation. The sets (including data set, template set, or ot
31、her sets to be defined in the future), are the building blocks of the FA information message and FA table entry. The template set specifies the IEs to be included in the data sets. The data set carries the values of the IEs specified in the template set. A data set is thus required to indicate the t
32、emplate set that determines the IE values that the data set has to carry. The FA information message and the FA table entry may consist of one or more sets. 9.1.2 FA table and FA table entry It is required that the FIXF supports the addition, update, and deletion of FA information in the FA table. A
33、n FA table may be stored in a FIXF entity. An FA table may contain one or more entries. An FA table entry may contain one or more sets. How an FA table is implemented is out of the scope of this Recommendation. 9.1.3 FA information message Information among FIFX entities is exchanged through FA info
34、rmation messages. An FA information message may contain one or more sets. The FIXF information message may have a format similar to the FA table entry. The FA information message is required to have a message header and at least one data or template set. An FA information message may be constructed
35、directly from an FA table with a new message header for transfer between FA entities. Rec. ITU-T Y.2122 (2009)/Amd.1 (11/2011) 3 Many forms of the FA information message are possible. Some examples of the structures of an FA information message are: 1) An FA information message consisting of an arbi
36、trarily interleaved template and data sets, as depicted below: Y.2122(09)-Amd.1(11)_F10MessageheaderTemplatesetDatasetDatasetTemplatesetDatasetFigure 9-2 An example of an FA information message 2) An FA information message consisting entirely of data sets: After the appropriate template records have
37、 been defined and transmitted to the collecting entity, the majority of the FA information message consists solely of data sets. 3) An FA information message consisting entirely of template sets. For detailed FA information message examples, see Appendix IX. 9.2 Properties in the information element
38、 of FIXF An IE specified for the FIXF is required to have the following properties: Name the name of the IE. Element ID the identifier of the IE. Description the explanation of the IE and possibly how this IE is derived from the flow aggregate, or other information available to the observer. Data ty
39、pe the data type of the IE. For example, the data type can be unsigned8 ranged from 0 to 255 or a string of 4 octets for the IPv4 address or 6 octets for the MAC address. Status the status of the specification of this IE. For example, the status value can be current, deprecated, or obsolete. Proprie
40、tary IEs are required to have the additional property as defined below: Proprietary tag the proprietary tag indicating whether this IE is used for enterprise use only. Enterprises and institutions may wish to define IEs for enterprise-internal purposes. An IE specified for the FIXF reference points
41、or by any future extension may have the following properties defined: Data type semantic additional detail describing the data type. Unit the unit of measure for the IE, for example, second or microsecond. Range the range of values that can be assigned to the IE, for example, 0 through 511 inclusive
42、. Reference the additional references that further define the IE or provide additional context for its use, for example, a document such as an ITU-T Recommendation or a uniform resource locator (URL). The FIXF is required to allow further limiting of the IE scope. By default, most IEs have a scope o
43、f “a specific flow aggregate“. Further definitions for the scope of the IE are required to be possible, for example, for the aggregation region or a subset of the flow aggregate. IEs to be exchanged are conveyed by an FA table entry. Table 2 in clause 8.3 in this Recommendation specifies the IE that
44、 may be gathered, stored, updated, and exchanged over networks at the reference points. 4 Rec. ITU-T Y.2122 (2009)/Amd.1 (11/2011) 4) New Appendix VIII Add the following new Appendix VIII: Appendix VIII Information element examples for flow aggregate information exchange functions (FIXF) (This appen
45、dix does not form an integral part of this Recommendation.) Examples of IEs for attributes of flow aggregates in flow aggregate information exchange functions (FIXF) are given below. The description in these examples is in between a general high-level description and the actual protocol-dependent fo
46、rmat. These examples are not intended to specify detail of the stage 3 level. 1) FA ID Name: FA ID (identifier) Description: a value assigned for recognition of a flow aggregate. This value is locally unique; i.e., it is meaningful only between the exchanging entities. Data type: variable length str
47、ing Data type semantics: identifier 2) Number of flows within the FA Name: number of flows within the FA Description: the number of flows within the FA. Data type: integer Data type semantics: number 3) Maximum sum of Rs divided by link capacity Name: maximum sum of Rs divided by link capacity Descr
48、iption: the maximum value of the sum of sustainable transfer rates (Rs) of flows within the FA divided by the link capacity, among all the links the FA traverses in the aggregation region. Data type: real number Data type semantics: number 5) New Appendix IX Add the following new Appendix IX: Rec. I
49、TU-T Y.2122 (2009)/Amd.1 (11/2011) 5 Appendix IX Typical message examples for flow aggregate information exchange functions (FIXF) (This appendix does not form an integral part of this Recommendation.) Consider the case where FIE-FE resides in domain A as shown in Figure IX.1. Assume that the FIE-FE has three FA table entries, each of which corresponds to different flow aggregate, to FIE-FE in domain B. Y.2122(09)-Amd.1(11)_FIX.1FuFaFaFaFbFbFdFbFcFcAggregation regionFIE-FED
