共找到 150 条与 DiffServ 相关的标准，共 10 页
ITU-T H.248.1定义了国际紧急优先方案（IEPS）呼叫指示符和优先级指示符，以支持优先服务，例如紧急电信服务（ETS）和多媒体优先服务（MPS）。使用IEPS呼叫指示符和优先级指示符，如ITU-T H.248.1所定义，满足ETS的要求，指示ETS上下文并携带优先级。 在媒体网关控制器（MGC）中对ITU-T H.248程序的优先级排序以及向媒体网关（MG）传输ITU-T H.248控制信号是基于ETS的识别。 IEPS呼叫指示符，识别ETS呼叫/会话，向MG指示上下文是ETS上下文，并在接收后启用ITU-T H.248控制信号的优先级排序。此外，它使MG能够优先分配ETS上下文的资源。 携带优先级的优先级指示符为MG提供了一种手段，以区分在ETS使用时MG资源的不同优先级处理。 本建议提供了在ITU-T H.248配置文件中使用IEPS呼叫指示符和优先级指示符的指南，适用于ITU-T H.323和NGN系统。这些指南可被其他标准开发组织（SDO）在定义其ITU-T H.248.1配置文件以支持优先服务（例如ETS和MPS）时使用。关于这些指南如何被其他网络使用的详细信息不在本建议的范围内。其他SDO在定义其配置文件时决定其使用。 ETS和IEPS分别在ITU-T E.107和ITU-T E.106中定义。ETS和IEPS涉及机构间通信。ITU-T H.248.1中定义的紧急指示符用于识别紧急呼叫（即个人与机构之间的通信）。IEPS呼叫指示符用于识别优先呼叫/会话（例如ETS呼叫/会话，IEPS呼叫/会话），允许与紧急呼叫/会话区分开来。紧急指示符的配置文件程序规范不在本建议的范围内。 国家监管机构可以以多种方式实施ETS。本建议描述了一种支持IEPS呼叫指示符和优先级指示符的实施方式。此外，它还描述了用于标记ETS呼叫/会话的DiffServ信号ITU-T H.248.52方法。 注1 - 国家、地区或地方的紧急和公共安全服务，其中公众个人寻求帮助（即个人与机构之间的通信），不在本建议的范围内。 注2 - [b-ITU-T Q-Sup.53]提供了支持IEPS的信号要求。它也适用于ITU-T H.248实体，但未指示除第7条之外的任何要求。 注3 - [b-ITU-T Q-Sup.57]提供了支持IP网络中ETS的信号要求。它也适用于ITU-T H.248实体，但未指示除第7条之外的任何要求。
DiffServ signalling approach
As Internet traffic is increasingly sourced from and destined to wireless endpoints@ it is crucial that Quality of Service (QoS) be aligned between wired and wireless networks; however@ this is not always the case by default. This document specifies a set of mappings from Differentiated Services Code Point (DSCP) to IEEE 802.11 User Priority (UP) to reconcile the marking recommendations offered by the IETF and the IEEE so as to maintain consistent QoS treatment between wired and IEEE 802.11 wireless networks
Mapping Diffserv to IEEE 802.11
This document specifies the protocol extensions for support of Diffserv-aware MPLS Traffic Engineering (DS-TE). This includes generalization of the semantics of a number of Interior Gateway Protocol (IGP) extensions already defined for existing MPLS Traffic Engineering in RFC 3630@ RFC 3784@ and additional IGP extensions beyond those. This also includes extensions to RSVP-TE signaling beyond those already specified in RFC 3209 for existing MPLS Traffic Engineering. These extensions address the requirements for DS-TE spelled out in RFC 3564.
Protocol Extensions for Support of Diffserv-aware MPLS Traffic Engineering
This Technical Report provides guidelines for the application of existing1 Differentiated Service (DiffServ) Per Hop Behaviors (PHB) and their associated DiffServ Code Points (DSCP) when Emergency Telecommunications Service (ETS) Voice over IP (VoIP) packets are transported in the media stream at Network-Network Interfaces (NNI). These guidelines are intended to facilitate the formulation of interconnection agreements between public domain service carriers by providing guidance with respect to the per hop queuing treatment to be provided for ETS calls@ thereby allowing for satisfactory end-to-end transport of ETS calls over multiple IP-based networks. These guidelines are intended for use until an acceptable future solution is standardized and available for implementation
ETS Packet Priority for IP NNI Interfaces - Use of Existing Diffserv per HOP Behaviors
The aim of the present document is to define an open specification for enabling QoS for IP-based multimedia satellite systems, based on the DiffServ model. If IP packets entering the BSM network require a particular QoS treatment, they have to be mapped onto QIDs. The choice of the QID to be used inside the BSM network is thus particularly important. So the present document specifies the allocation of the QIDs and their mapping to IP QoS classes, when DiffServ is used to provide QoS at IP layer. The present document assumes the QoS functional architecture described in ETSI TS 102 462 [2]. The present document describes in detail how QIDs are defined, how they are allocated and handled by the BSM network, and the requirements needed by sending and receiving Satellite Terminals (STs) in a BSM network to provide QID management functionalities. The present document also defines the primitives that should be used across the SI-SAP when allocating QIDs, when mapping DiffServ Code Points (DSCPs) and IP services to QIDs, when mapping QIDs to SD queues. Details on the QID mapping are presented with some examples. Some cases are presented to show the potential evolution from a simple QoS solution with quasi-static QID allocation to more sophisticated services with dynamic resource reservation. The combination of DiffServ with multicast transmissions is out of scope of the present document, as well as the use of Explicit Congestion Notification (ECN), which was linked to DiffServ only for historical reasons, as the ECN bits are the two least significant bits of the IPv4 ToS octet. This is better explained in clause 4.
Satellite Earth Stations and Systems (SES); Broadband Satellite Multimedia (BSM); Interworking with DiffServ QoS
The aim of the present document is to define an open specification for enabling QoS for IP-based multimedia satellite systems@ based on the DiffServ model. If IP packets entering the BSM network require a particular QoS treatment@ they have to be mapped onto QIDs. The choice of the QID to be used inside the BSM network is thus particularly important. So the present document specifies the allocation of the QIDs and their mapping to IP QoS classes@ when DiffServ is used to provide QoS at IP layer. The present document assumes the QoS functional architecture described in ETSI TS 102 462 [2]. The present document describes in detail how QIDs are defined@ how they are allocated and handled by the BSM network@ and the requirements needed by sending and receiving Satellite Terminals (STs) in a BSM network to provide QID management functionalities. The present document also defines the primitives that should be used across the SI-SAP when allocating QIDs@ when mapping DiffServ Code Points (DSCPs) and IP services to QIDs@ when mapping QIDs to SD queues. Details on the QID mapping are presented with some examples. Some cases are presented to show the potential evolution from a simple QoS solution with quasi-static QID allocation to more sophisticated services with dynamic resource reservation. The combination of DiffServ with multicast transmissions is out of scope of the present document@ as well as the use of Explicit Congestion Notification (ECN)@ which was linked to DiffServ only for historical reasons@ as the ECN bits are the two least significant bits of the IPv4 ToS octet. This is better explained in clause 4.
Satellite Earth Stations and Systems (SES); Broadband Satellite Multimedia (BSM); Interworking with DiffServ QoS (V1.2.1)
This document specifies a CLASSTYPE object to support Diffserv-Aware Traffic Engineering (DS-TE) where path computation is performed with the aid of a Path Computation Element (PCE).
Diffserv-Aware Class-Type Object for the Path Computation Element Communication Protocol
The aim of the present document is to define an open specification for enabling QoS for IP-based multimedia satellite systems, based on the DiffServ model. If IP packets entering the BSM network require a particular QoS treatment, they have to be mapped onto QIDs. The choice of the QID to be used inside the BSM network is thus particularly important. So the present document specifies the allocation of the QIDs and their mapping to IP QoS classes, when DiffServ is used to provide QoS at IP layer. The present document assumes the QoS functional architecture described in ETSI TS 102 462 [2]. The present document describes in detail how QIDs are defined, how they are allocated and handled by the BSM network, and the requirements needed by sending and receiving Satellite Terminals (STs) in a BSM network to provide QID management functionalities. The present document also defines the primitives that should be used across the SI-SAP when allocating QIDs, when mapping DiffServ Code Points (DSCPs) and IP services to QIDs, when mapping QIDs to SD queues. Details on the QID mapping are presented with some examples. Some cases are presented to show the potential evolution from a simple QoS solution with quasi-static QID allocation to more sophisticated services with dynamic resource reservation. The combination of DiffServ with multicast transmissions is out of scope of the present document, as well as the use of Explicit Congestion Notification (ECN), which was linked to DiffServ only for historical reasons, as the ECN bits are the two least significant bits of the IPv4 ToS octet.
Satellite Earth Stations and Systems (SES); Broadband Satellite Multimedia (BSM); Interworking with DiffServ QoS (V1.2.1)
Satellite Earth Stations and Systems (SES); Broadband Satellite Multimedia (BSM); Interworking with DiffServ Qos (V1.1.1)
本文件旨在定义基于DiffServ模型的IP多媒体卫星系统QoS开放规范。当进入BSM网络的IP数据包需要特定QoS处理时，必须映射到QID。本文档详细说明了QID的定义、分配和处理方式，以及发送和接收卫星终端（ST）在BSM网络中提供QID管理功能的要求。文档还定义了在分配QID、映射DiffServ代码点（DSCP）和IP服务到QID、映射QID到SD队列时在SI-SAP上使用的原语。DiffServ与多播传输的组合以及显式拥塞通知（ECN）的使用不在本文档范围内。
Satellite Earth Stations and Systems (SES); Broadband Satellite Multimedia (BSM); Interworking with DiffServ Qos
ETS Packet Priority for IP NNI Interfaces - Use of Existing Diffserv per HOP Behaviors
The objective of Pre-Congestion Notification (PCN) is to protect the quality of service (QoS) of inelastic flows within a Diffserv domain. The overall rate of PCN-traffic is metered on every link in the PCNdomain@ and PCN-packets are appropriately marked when certain configured rates are exceeded. Egress nodes pass information about these PCN-marks to Decision Points that then decide whether to admit or block new flow requests or to terminate some already admitted flows during serious pre-congestion. This document specifies how PCN-marks are to be encoded into the IP header by reusing the Explicit Congestion Notification (ECN) codepoints within a PCN-domain. The PCN wire protocol for non-IP protocol headers will need to be defined elsewhere. Nonetheless@ this document clarifies the PCN encoding for MPLS in an informational appendix. The encoding for IP provides for up to three different PCN marking states using a single Diffserv codepoint (DSCP): not-marked (NM)@ threshold-marked (ThM)@ and excess-traffic-marked (ETM). Hence@ it is called the 3-in-1 PCN encoding. This document obsoletes RFC 5696.
Encoding Three Pre-Congestion Notification (PCN) States in the IP Header Using a Single Diffserv Codepoint (DSCP)
Satellite Earth Stations and Systems (SES); Broadband Satellite Multimedia (BSM); Interworking with DiffServ Qos (V1.1.1)
本附录描述了在传输平面中基于 RSVP 的 QoS 信令时 H.323 QoS 信令的程序。资源预留协议（RSVP）是 IETF RFC 2205 中用于集成服务（IntServ）架构的 QoS 信令协议。在集成服务架构中使用 RSVP 的描述见 IETF RFC 2210。RSVP 是一种基于路径的 QoS 机制，用于为单个流和流聚合预留资源。RSVP 可纯用于 IntServ 架构，也可与区分服务架构（DiffServ）耦合，以在 DiffServ 网络上提供 IntServ 操作（见 IETF RFC 2998）。本附录描述了允许在传输平面中使用 RSVP 的 H.323 QoS 程序。
New Annex A "IntServ/RSVP support for H.323 systems", Annex B "DiffServ support for H.323 systems" and Annex C "Priority support for H.323 systems"
本文件提供了涉及GPRS的端到端服务质量框架，并补充了描述UMTS内服务质量框架的TS23.107。文档描述了TE/MT本地承载服务、GPRS承载服务和外部承载服务之间的交互，以及这些服务如何共同为端到端服务提供服务质量。文档还描述了在涉及GPRS网络时提供端到端服务质量所必需的IP级机制，包括IP级与GPRS级之间以及应用级与IP级之间可能的交互。与TS23.107相比，本文件仅适用于GPRS分组交换接入服务，并包括与IM子系统以及PSTN和其他网络互通的相关方面。文档不涵盖电路交换接入服务。
Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); End-to-end Quality of Service (QoS) concept and architecture (3GPP TS 23.207 version 6.5.0 Release 6)
