ITU-T Y 3042-2013 Smart ubiquitous networks C Smart traffic control and resource management functions (Study Group 13)《(预发布)智能无处不在的网络-智能交通控制和资源管理功能》.pdf

《ITU-T Y 3042-2013 Smart ubiquitous networks C Smart traffic control and resource management functions (Study Group 13)《(预发布)智能无处不在的网络-智能交通控制和资源管理功能》.pdf》由会员分享，可在线阅读，更多相关《ITU-T Y 3042-2013 Smart ubiquitous networks C Smart traffic control and resource management functions (Study Group 13)《(预发布)智能无处不在的网络-智能交通控制和资源管理功能》.pdf（36页珍藏版）》请在麦多课文档分享上搜索。

1、 International Telecommunication Union ITU-T Y.3042TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU (04/2013) SERIES Y: GLOBAL INFORMATION INFRASTRUCTURE, INTERNET PROTOCOL ASPECTS AND NEXT-GENERATION NETWORKS Future networks Smart ubiquitous networks Smart traffic control and resource management fun

2、ctions Recommendation ITU-T Y.3042 ITU-T Y-SERIES RECOMMENDATIONS GLOBAL INFORMATION INFRASTRUCTURE, INTERNET PROTOCOL ASPECTS AND NEXT-GENERATION NETWORKS GLOBAL INFORMATION INFRASTRUCTURE General Y.100Y.199 Services, applications and middleware Y.200Y.299 Network aspects Y.300Y.399 Interfaces and

3、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 applications Y.1100Y.1199 Architecture, access, network capabilities and resou

4、rce 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.1800Y.1899 IPTV over NGN Y.1900Y.1999 NEXT GENERATION NETWORKS Frameworks and

5、 functional architecture models Y.2000Y.2099 Quality of Service and performance Y.2100Y.2199 Service aspects: Service capabilities and service architecture Y.2200Y.2249 Service aspects: Interoperability of services and networks in NGN Y.2250Y.2299 Numbering, naming and addressing Y.2300Y.2399 Networ

6、k management Y.2400Y.2499 Network control architectures and protocols Y.2500Y.2599 Packet-based Networks Y.2600Y.2699 Security Y.2700Y.2799 Generalized mobility Y.2800Y.2899 Carrier grade open environment Y.2900Y.2999 FUTURE NETWORKS Y.3000Y.3499CLOUD COMPUTING Y.3500Y.3999 For further details, plea

7、se refer to the list of ITU-T Recommendations. Rec. ITU-T Y.3042 (04/2013) i Recommendation ITU-T Y.3042 Smart ubiquitous networks Smart traffic control and resource management functions Summary Recommendation ITU-T Y.3042 specifies the smart traffic control and resource management functions for SUN

8、. It defines the motivation and identifies the high-level requirements and functional architecture for providing relevant network capabilities. This Recommendation also identifies mechanisms in terms of “smart and ubiquitous“ aspects of networks. History Edition Recommendation Approval Study Group 1

9、.0 ITU-T Y.3042 2013-04-13 13 Keywords Smart resource management, smart traffic control, smart ubiquitous network, SUN. ii Rec. ITU-T Y.3042 (04/2013) FOREWORD The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and

10、 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 standardizing telecommunications on a worldwide bas

11、is. 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 is covered by the procedure laid down in WTSA Resol

12、ution 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 indicate both a telecommunication administration

13、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 achieved when all of these mandatory provisions are

14、 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. INTELLECTUAL PROPERTY RIGHTS ITU draws attention to the pos

15、sibility 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 asserted by ITU members or others outside of the

16、 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 cautioned that this may not represent the latest infor

17、mation and are therefore strongly urged to consult the TSB patent database at http:/www.itu.int/ITU-T/ipr/. ITU 2014 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 Y.3042 (04/2013) iii Table of Cont

18、ents Page 1 Scope 1 2 References. 1 3 Definitions 2 3.1 Terms defined elsewhere 2 3.2 Terms defined in this Recommendation . 2 4 Abbreviations and acronyms 3 5 Conventions 4 6 Introduction 4 6.1 Motivation 4 6.2 Objectives . 5 7 Fine-grained classifications of traffic . 5 7.1 Fine-grained bandwidth

19、6 7.2 Fine-grained service duration . 6 7.3 Fine-grained traffic classes . 7 8 Requirements 8 8.1 High-level requirements . 8 8.2 Functional requirements . 9 9 Architecture 10 9.1 High level architecture . 10 9.2 Functional architecture . 10 9.3 Reference points . 13 10 Mechanisms for smart traffic

20、control and resource management . 15 10.1 Mechanism based on data cap 15 10.2 Mechanism for heavy service traffic 16 10.3 Mechanism for heavy signalling traffic 17 10.4 Mechanism for heavy user traffic . 18 10.5 Mechanism for surge traffic . 19 10.6 Mechanism for over-sized traffic . 20 10.7 Mechani

21、sm for busy-hour traffic 21 10.8 Mechanism based on a list 23 11 Security consideration 24 Appendix I Data explosion and QoS degradation . 25 I.1 Data explosion caused by a small number of users in fixed and mobile networks . 25 I.2 QoS degradation for general users caused by a small number of heavy

22、 users 26 I.3 Need for smart network management to protect normal users QoS 26 iv Rec. ITU-T Y.3042 (04/2013) Page Appendix II Context information examples for STCRMF . 27 Rec. ITU-T Y.3042 (04/2013) 1 Recommendation ITU-T Y.3042 Smart ubiquitous networks Smart traffic control and resource managemen

23、t functions 1 Scope This Recommendation specifies smart traffic control and resource management functions to provide fair usage of network resources using context awareness capability in smart ubiquitous networks (SUN). This Recommendation covers the following: Motivation and objectives of smart tra

24、ffic control and resource management; Requirements for smart traffic control and resource management for SUN; High-level architecture and functional architecture; Control and management mechanisms. NOTE 1 Usage of context information is optional and the mechanism details of context awareness capabil

25、ity are outside of scope in this Recommendation. NOTE 2 Regulatory aspects of monitoring (e.g., depth of IP packet allowed to be monitored) are outside of scope in this Recommendation. NOTE 3 Traffic, means user or service provider traffic and resource, means operational status of network elements (

26、e.g., CPU usage, interface utilization, etc.) in this Recommendation. NOTE 4 Controlling traffic includes both application and network layer control. Some examples of application layer controls are video pacing, video transcoding and/or HTTP adaptive streaming (HAS). 2 References The following ITU-T

27、 Recommendations and other references contain provisions which, through reference 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 revision; users of this Recommendation

28、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 this Recommendation does not give it, a

29、s a stand-alone document, the status of a Recommendation. ITU-T E.600 Recommendation ITU-T E.600 (1993), Terms and definitions of traffic engineering. ITU-T Q.9 Recommendation ITU-T Q.9 (1988), Vocabulary of switching and signalling terms. ITU-T Y.1541 Recommendation ITU-T Y.1541 (2011), Network per

30、formance objectives for IP-based services. ITU-T Y.2701 Recommendation ITU-T Y.2701 (2007), Security requirements for NGN release 1. ITU-T Y.3041 Recommendation ITU-T Y.3041 (2013), Smart ubiquitous networks Overview. 2 Rec. ITU-T Y.3042 (04/2013) 3 Definitions 3.1 Terms defined elsewhere This Recom

31、mendation uses the following terms defined elsewhere: 3.1.1 smart ubiquitous networks (SUN) ITU-T Y.3041: IP-based packet networks that can provide transport and delivery of a wide range of existing and emerging services to people and things. The services provided by the SUN can cover aspects such a

32、s control, processing and storage. NOTE 1 The network is smart in the sense that it is knowledgeable, context-aware, adaptable, autonomous, programmable, and can perform services effectively and securely. NOTE 2 The network is ubiquitous in the sense that it allows access anytime, anywhere, through

33、varied access technologies, access devices, including end user devices, and human-machine interfaces. 3.1.2 context ITU-T Y.3041: The information that can be used to characterize the environment of a user. 3.1.3 busy hour ITU-T E.600: The continuous 1-hour period lying wholly in the time interval co

34、ncerned for which the traffic or the number of call attempts is greatest. 3.1.4 (signalling) traffic flow control ITU-T Q.9: Actions and procedures intended to limit signalling traffic at its source in the case when the signalling network is not capable of transferring all signalling traffic offered

35、 by the User Parts due to network failures or overload situations. 3.2 Terms defined in this Recommendation This Recommendation defines the following terms: 3.2.1 data cap: Upper limit of the total traffic volume allowed by the SLA contracted between the traffic source (e.g., ISP) and destination (e

36、.g., user). 3.2.2 fair usage: Equal treatment for the same service(s), including application(s), between different users (e.g., end-user, applications) with the same SLA. 3.2.3 heavy service traffic: Traffic level measured in the volume of specific service(s) which overloads network resources at the

37、 interface from/to service providers. It has an impact on other service traffic on the same network resource (e.g., degrading the quality). 3.2.4 heavy signalling traffic: Traffic level measured in the volume and frequency that triggers signalling traffic flow control ITU-T Q.9 (e.g., heavy traffic

38、level caused by keep-alive messages). 3.2.5 heavy user traffic: Traffic level measured in the volume of traffic initiated by an end-user who overloads network resources at the interface from/to the end-user. It affects the traffic quality of other users. 3.2.6 surge traffic: Traffic level measured i

39、n the aggregated volume initiated by multiple users which overloads network resources at special events such as an abrupt occurrence of bad weather, a particular sports or music event that attracts a high number of users, etc. 3.2.7 monopolization: Condition of network resource overloads caused by h

40、eavy service or user traffic. It affects the traffic quality of other service(s) or user(s). 3.2.8 over-sized traffic: Traffic level that is larger in volume than the recommended size for a service. The recommended volume of such a service should be identified by SLA between the traffic source and d

41、estination. It is a special case of heavy service traffic. Rec. ITU-T Y.3042 (04/2013) 3 4 Abbreviations and acronyms This Recommendation uses the following abbreviations and acronyms: 3DTV 3 Dimensional TV CP Contents Provider DSCP Differentiated Services Code Point HDTV High Definition TV IoT Inte

42、rnet of Things IPTV Internet Protocol TV ISP Internet Service Provider OTT Over the Top PDL Progressive Down Load POP Point of Presence QCI QoS Class Identifier QoE Quality of Experience QoS Quality of Service RA-FE Resource Analysis Functional Entity RMAF Resource Monitoring and Analysis Function R

43、M-FE Resource Monitoring Functional Entity SCD-FE Smart Correlation and Decision Functional Entity SLA Service Level Agreement SRC-FE Smart Resource Control Functional Entity STC-FE Smart Traffic Control Functional Entity STCRMF Smart Traffic Control and Resource Management Functions STRCF Smart Tra

44、ffic and Resource Control Function SUN Smart Ubiquitous Network TA-FE Traffic Analysis Functional Entity TMAF Traffic Monitoring and Analysis Function TM-FE Traffic Monitoring Functional Entity TRAF Traffic Control and Analysis Function TRCMF Traffic Resource Control and Management Function VNO Virt

45、ual Network Operator 4 Rec. ITU-T Y.3042 (04/2013) 5 Conventions In this Recommendation: The keywords “is required to“ indicate a requirement which must be strictly followed and from which no deviation is permitted, if conformance to this Recommendation is to be claimed. The keywords “is prohibited

46、from“ indicate a requirement which must be strictly followed and from which no deviation is permitted, if conformance to this Recommendation is to be claimed. The keywords “is recommended“ indicate a requirement which is recommended but which is not absolutely required. Thus, this requirement need n

47、ot be present to claim conformance. The keywords “is not recommended“ indicate a requirement which is not recommended but which is not specifically prohibited. Thus, conformance with this Recommendation can still be claimed even if this requirement is present. The keywords “can optionally“ indicate

48、an optional requirement which is permissible, without implying any sense of being recommended. This term is not intended to imply that the vendors implementation must provide the option, and the feature can be optionally enabled by the network operator/service provider. Rather, it means the vendor m

49、ay optionally provide the feature and still claim conformance with this Recommendation. 6 Introduction 6.1 Motivation Developments of various smart devices (e.g., smartphones, pads, IoT devices, etc.) in user environments of IP networks combined with newly emerging services such as Smart TV, 3DTV, and network gaming have led to increases in service traffic. These smart devices require networks to allocate more resources to support requested bandwidth and various service features including