ETSI TS 181 018-2007 Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN) Requirements for QoS in a NGN (V2 0 0)《电信和互联网融合业务及高级网络协议(TISP.pdf

1、 ETSI TS 181 018 V2.0.0 (2007-08)Technical Specification Telecommunications and Internet converged Services andProtocols for Advanced Networking (TISPAN);Requirements for QoS in a NGNETSI ETSI TS 181 018 V2.0.0 (2007-08) 2 Reference DTS/TISPAN-01046-NGN-R2 Keywords analysis, QoS ETSI 650 Route des L

2、ucioles F-06921 Sophia Antipolis Cedex - FRANCE Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 Siret N 348 623 562 00017 - NAF 742 C Association but non lucratif enregistre la Sous-Prfecture de Grasse (06) N 7803/88 Important notice Individual copies of the present document can be downloaded from: h

3、ttp:/www.etsi.org The present document may be made available in more than one electronic version or in print. In any case of existing or perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF). In case of dispute, the reference shall be the

4、 printing on ETSI printers of the PDF version kept on a specific network drive within ETSI Secretariat. Users of the present document should be aware that the document may be subject to revision or change of status. Information on the current status of this and other ETSI documents is available at h

5、ttp:/portal.etsi.org/tb/status/status.asp If you find errors in the present document, please send your comment to one of the following services: http:/portal.etsi.org/chaircor/ETSI_support.asp Copyright Notification No part may be reproduced except as authorized by written permission. The copyright

6、and the foregoing restriction extend to reproduction in all media. European Telecommunications Standards Institute 2007. All rights reserved. DECTTM, PLUGTESTSTM and UMTSTM are Trade Marks of ETSI registered for the benefit of its Members. TIPHONTMand the TIPHON logo are Trade Marks currently being

7、registered by ETSI for the benefit of its Members. 3GPPTM is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. ETSI ETSI TS 181 018 V2.0.0 (2007-08) 3 Contents Intellectual Property Rights4 Foreword.4 1 Scope 5 2 References 5 3 Definitions and ab

8、breviations.5 3.1 Definitions5 3.2 Abbreviations .6 4 General requirements .6 5 Specific requirements.6 5.1 QoS reporting .6 5.1.1 Information sources 6 5.1.2 Services.7 5.1.3 QoS reporting information7 5.1.4 Granularity7 5.1.5 Use of QoS Reporting information.7 5.2 Resource monitoring 8 5.2.1 Gener

9、al8 5.2.2 Information sources 8 5.2.3 Resource Monitoring information.8 5.2.4 Granularity9 5.2.5 Use of resource monitoring information.9 5.3 Dynamic policy provisioning .10 5.4 End-to-end QoS requirements 10 5.5 Charging.10 Annex A (informative): Scenarios.11 A.1 Use of sophisticated admission cont

10、rol algorithms11 A.2 L2 topology awareness and traffic management options .12 A.3 Coexistence of managed and un-managed traffic 13 A.4 Bandwidth on Demand.13 Annex B (informative): Bibliography.16 History 17 ETSI ETSI TS 181 018 V2.0.0 (2007-08) 4 Intellectual Property Rights IPRs essential or poten

11、tially essential to the present document may have been declared to ETSI. The information pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found in ETSI SR 000 314: “Intellectual Property Rights (IPRs); Essential, or potentially Essential,

12、 IPRs notified to ETSI in respect of ETSI standards“, which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web server (http:/webapp.etsi.org/IPR/home.asp). Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No gu

13、arantee can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web server) which are, or may be, or may become, essential to the present document. Foreword This Technical Specification (TS) has been produced by ETSI Technical Committee Telecommun

14、ications and Internet converged Services and Protocols for Advanced Networking (TISPAN). ETSI ETSI TS 181 018 V2.0.0 (2007-08) 5 1 Scope The present document identifies the capabilities that a TISPAN NGN shall provide in order to guarantee an adequate Quality of Service (QoS) to the media flows and

15、it defines the specific requirements for an NGN environment related to the identified capabilities. The present document defines requirements for a TISPAN Release 2 NGN. The present document does not define classes of services or values for the parameters used to define the classes of services: this

16、 work is done by other standardization bodies. The present document defines detailed requirements based on clause 4.11 in 1. NOTE: The present document uses the term “NGN“ only in the context of TISPAN. 2 References The following documents contain provisions which, through reference in this text, co

17、nstitute provisions of the present document. References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For a specific reference, subsequent revisions do not apply. For a non-specific reference, the latest version applies. Referenced d

18、ocuments which are not found to be publicly available in the expected location might be found at http:/docbox.etsi.org/Reference. NOTE: While any hyperlinks included in this clause were valid at the time of publication ETSI cannot guarantee their long term validity. 1 ETSI TS 181 005: “Telecommunica

19、tions and Internet converged Services and Protocols for Advanced Networking (TISPAN); Services and Capabilities Requirements“. 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions given in TR 180 000 and the following apply: network prob

20、e: network element able to intercept the media flow and provide some information to the control layer QoS reporting: this mechanism identifies the ability for some network elements to collect the values of some QoS metrics of a single service instance NOTE: Example of QoS metrics could be delay, pac

21、ket loss, etc. resource monitoring: this mechanism identifies the ability to monitor the topologies and resources of the transport segments controlled by RACS NOTE: Resource monitoring includes detecting the actual usage of these resources. ETSI ETSI TS 181 018 V2.0.0 (2007-08) 6 3.2 Abbreviations F

22、or the purposes of the present document, the following abbreviations apply: ADSL Asymmetrical Digital Subscriber Line AF Application Function ATM Asynchronous Transfer Mode BGF Border Gateway Function BoD Bandwidth on Demand BRAS Broadband Remote Access Server CAC Call Admission Control CAC Connecti

23、on Admission Control CBR Constant Bit Rate CLP Cell Loss Priority CoS Class of Service CPE Customer Premises Equipment NGN Next Generation Network OSS Operating Support Systems PCR Peak Cell Rate QoS Quality of Service RACS Resource Admission Control Subsystem TRIM Topology and Resource Information

24、Model UE User Equipment VBR Variable Bit Rate VC Virtual Channel VP Virtual Path 4 General requirements The following general requirements shall be fulfilled in a TISPAN NGN: The NGN shall support QoS reporting mechanisms in order to indicate to the control/service/management elements (e.g. RACS, ac

25、counting functions) the QoS really achieved by the bearer flows. The NGN shall support resource monitoring mechanisms in order to determine the available network resources (e.g. link bandwidth, port utilization, queue depth). The assumption is made that creation of the inventory of the network resou

26、rces shall be done via suitable interfaces. The NGN shall support dynamic policy provisioning mechanisms in order to allow the change on demand of the policies applied to a single user access (e.g. change the maximum bandwidth of an ADSL access). The NGN shall support end-to-end QoS control to allow

27、 guaranteed QoS levels to be provided between connectivity end points. Several QoS classes should be supported. In a single provider domain environment, according to the user service profile, the NGN shall be able to downgrade the QoS after a QoS degradation is detected. 5 Specific requirements 5.1

28、QoS reporting 5.1.1 Information sources It is required that at least one of the following elements is able to provide QoS reporting information per service basis: CPE/Customer Network Gateway. ETSI ETSI TS 181 018 V2.0.0 (2007-08) 7 Border Gateway Function (BGF). Network probes. In addition it shoul

29、d be possible to have also other information sources such as Access Nodes, IP edge nodes, etc. 5.1.2 Services Gathering of QoS reporting information shall be provided for both session and non session based services (e.g. content based services). 5.1.3 QoS reporting information QoS reporting informat

30、ion: For session based services reporting at least the following information shall be provided: number of packets received, packet loss, average delay, and jitter. In addition, it should be possible to also report other quality metrics. For non session based services reporting at least the following

31、 information should be supported: number of packets received, packet loss, number of retransmitted packets. In addition, it should be possible to also report other quality metrics. It may also be possible for the information sources to process the information gathered. For example, processing can be

32、 used to determine the urgency in reporting the information and/or to reduce the forwarding capacity needed to transfer the information or for generating aggregate information starting from raw ones. 5.1.4 Granularity The granularity used by the network elements to generate the QoS reporting informa

33、tion shall be an operator choice on a per service basis and per information source basis. The QoS reporting may be triggered by pre-defined events, e.g. thresholds violation, during a session or a service instance. Exhaustive QoS reporting information at the end of service shall be supported (e.g. c

34、ommunication session, video streaming). The level of granularity shall be such that it is sufficient for purpose without causing excessive load to the requester and responder of QoS reporting, as well as the network traffic. The QoS reporting should contain a timestamp indicating the time at which t

35、he observation was made. 5.1.5 Use of QoS Reporting information Use of the QoS reporting information: The control/service/management elements that use the QoS reporting information shall be able to process the information gathered. The QoS control layer shall be able to change the admission control

36、and/or enforcement policies used for QoS purposes based on QoS reporting information. The policies to be changed are an operator choice and could be one or more of the following: square4 the enforcement policies for the media flow related to the QoS reporting information; square4 the enforcement pol

37、icies for other media flows of the same user; square4 the enforcement policies for the media flows of other users; square4 the admission control and/or enforcement policies for a particular network segment; square4 the admission control and/or enforcement policies for new media flows requests. The a

38、ccounting functionalities shall be able to use the QoS reporting information to enrich the CDR provided to the billing systems. ETSI ETSI TS 181 018 V2.0.0 (2007-08) 8 The management functionalities shall be able to use the QoS reporting information for off line analysis (e.g. for planning purposes)

39、. 5.2 Resource monitoring 5.2.1 General The ability to offer end-to-end QoS control in an NGN is of fundamental importance as new services and applications with ever increasing QoS requirements become available. Management of application QoS requirements where a number of services are being provided

40、 over individual links requires knowledge of the available bandwidth on the link. In order to achieve these requirements the RACS needs to have an accurate and current knowledge of the available network resources in the transport layer, e.g. in case of a network device failure or congestion occurrin

41、g this may impact on available QoS due to increased load or delays caused by re-routing. The RACS needs also to have knowledge of the status of each network component (nodes and links) under its control. This information may be held in accordance with a Topology and Resource Information Model (TRIM)

42、 and made available to RACS to provide the required information for QoS control. The sources and types of information are described in the following clauses. In general, RACS shall have knowledge of the network topology, routing information and total resource capacity including capacity in each forw

43、arding class and shall be made aware of dynamic changes in the network (e.g. device or link failure). 5.2.2 Information sources Topology, resource and routing information may be acquired from a number of different sources, including external systems such as OSS and directly from the network elements

44、 controlled by the RACS system. The information may be stored in accordance with the information model and made available to the RACS system. Resource Monitoring employs a number of different sources: primarily the Access Node and IP Edge, but where true end-to-end QoS provision requires knowledge o

45、f the number or type of CPE connections, the CPE/Customer Network Gateway must support the resource monitoring mechanism in order to monitor the whole network from CPE to BGF. The information sources are dependent on the access technologies in use. Information Sources: sources of the information sha

46、ll be OSS Functions and whatever resource(s) the RACS controls. RACS may need information from one or more elements about their environment. Although information must be maintained about the whole network, aggregation may allow RACS to receive the required information from a subset of these elements

47、. In addition to the above list it may be possible to identify other information sources (e.g. CPE) depending on the type of access network in use. Consideration should be given to a range of access architectures when identifying the possible information sources. 5.2.3 Resource Monitoring informatio

48、n The Resource monitoring information available may vary depending on the type of resource in use. This in turn depends upon the type of access architecture involved. Some consideration also needs to be given to the types of application in use and their QoS requirements as these have an impact on th

49、e resource information required. The information are dynamically updated and stored in such a way as to be accessible to the RACS. Types of information: can be separated into three different categories: Devices and interfaces of the physical network topology. Routing information that describes the connectivity through the topology. Resource availability information. ETSI ETSI TS 181 018 V2.0.0 (2007-08) 9 Within these categories there may be static and dynamic information. For instance the topology information may comprise static inf