hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
5c408ecfef3e523a192afe3fd7249eaf | 102 831 | 16.1 Restrictions of T2-Lite | T2-Lite establishes further restrictions in terms of time interleaver memory, service date rate and FEC processing rate in order to reduce the complexity that is required for the implementation of T2-Lite only receivers. The time interleaving memory in T2-Lite has been reduced from 219 + 215 cells down to 218 cells. Th... |
5c408ecfef3e523a192afe3fd7249eaf | 102 831 | 16.2 Elements excluded in T2-Lite | The elements that are allowed in DVB-T2 and that have been excluded in T2-Lite can be divided in two categories; those that apply to the selection of FFT size, pilot pattern and guard interval, and those that apply to the MODCOD configuration. The 32 K FFT size is not included in T2-Lite, as the resulting separation be... |
5c408ecfef3e523a192afe3fd7249eaf | 102 831 | 16.3 Elements added in T2-Lite | The new elements added for T2-Lite are related to the FEC chain and the configuration of FEF parts. Regarding the FEC chain, two code rates 1/3 and 2/5 have been added together with their respective bit to cell demultiplexers. The new code rates have been inherited from DVB-S2 in order to enable reception at lower SNR ... |
5c408ecfef3e523a192afe3fd7249eaf | 102 831 | 16.4 Examples of possible use of the T2-Lite profile | The provision of stationary and mobile services in the same T2 multiplex is limited by the fact that the FFT mode and the pilot pattern cannot be adjusted during the same T2 signal. Stationary services should be generally transmitted with large FFTs and sparse pilot patterns in order to achieve a high spectral efficien... |
5c408ecfef3e523a192afe3fd7249eaf | 102 831 | 16.5 Deployment scenarios | DVB-T2 networks planned for stationary receivers are aimed at very high throughput with sufficient robustness for rooftop reception (e.g. 32 K FFT mode, 256QAM constellation, 2/3 code rate). While stationary reception is generally performed with rooftop antennas in Line of Sight conditions, portable and mobile receptio... |
5c408ecfef3e523a192afe3fd7249eaf | 102 831 | 17 Transmitter signature | |
5c408ecfef3e523a192afe3fd7249eaf | 102 831 | 17.1 Introduction | Reference [i.1] describes the coding and modulation for DVB-T2 and thus provides the means whereby digital content can be broadcast to viewers and other consumers of content. It offers many options for network operators, including the ability to support single frequency networks (SFNs). SFNs using OFDM, as DVB-T2 does,... |
5c408ecfef3e523a192afe3fd7249eaf | 102 831 | 17.2 General principles | Clearly, to include a signature unique to a transmitter implies at least a partial departure from the general SFN principle of radiating identical signals from every transmitter - some part of the signal will need to be different. However, a cardinal principle remains, that the addition of transmitter signatures should... |
5c408ecfef3e523a192afe3fd7249eaf | 102 831 | 17.3 Brief description of the auxiliary-stream method | This signature method uses one auxiliary stream in the DVB-T2 signal to carry transmitter identification information. There may also be other auxiliary streams, for other purposes, before or after (or both) the actual auxiliary stream used as a transmitter signature. In line with [i.1] there may also be dummy cells bef... |
5c408ecfef3e523a192afe3fd7249eaf | 102 831 | 17.4 Brief description of the FEF method | In this signature method, the transmitter signature is sent in a FEF part. Typically this FEF part would only be sent once per DVB-T2 superframe, and thus sufficiently infrequently to reduce capacity losses to a minimum. However, it may be sent more frequently if a network operator so chooses. Every transmitter in the ... |
6b77e172bdb4a3ee1a9d8c1436769e99 | 102 830 | 1 Scope | The present document describes standard API to manage GCM components at runtime in an interoperable way. It defines component management in a standard manner to create, introspect, monitor and reconfigure components at execution. The present document will help enterprises and laboratories to use their large-scale compu... |
6b77e172bdb4a3ee1a9d8c1436769e99 | 102 830 | 2 References | 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. • Non-specific reference may be made only to a complete document or a part thereof and only in the following cases: - if it is accept... |
6b77e172bdb4a3ee1a9d8c1436769e99 | 102 830 | 2.1 Normative references | The following referenced documents are indispensable for the application of the present document. For dated references, only the edition cited applies. For non-specific references, the latest edition of the referenced document (including any amendments) applies. [1] ETSI TS 102 829: "GRID; Grid Component Model (GCM); G... |
6b77e172bdb4a3ee1a9d8c1436769e99 | 102 830 | 2.2 Informative references | The following referenced documents are not essential to the use of the present document but they assist the user with regard to a particular subject area. For non-specific references, the latest version of the referenced document (including any amendments) applies. [i.1] "The Fractal Component Model". NOTE: Available a... |
6b77e172bdb4a3ee1a9d8c1436769e99 | 102 830 | 3 Definitions and abbreviations | |
6b77e172bdb4a3ee1a9d8c1436769e99 | 102 830 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply: binding: communication path between a client and a server interface cardinality: property of an interface type that indicates how many interfaces of this type a given component may have NOTE: The cardinality is singleton, collection, m... |
6b77e172bdb4a3ee1a9d8c1436769e99 | 102 830 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: ADL Architecture Description Language API Application Programming Interface GCM Grid Component Model |
6b77e172bdb4a3ee1a9d8c1436769e99 | 102 830 | 4 Overview of the Grid Component Model (GCM) | By enforcing a strict separation between interface and implementation and by making software architecture explicit, component-based programming can facilitate the implementation and maintenance of complex distributed software systems. ETSI ETSI TS 102 830 V1.1.1 (2010-03) 8 Existing component-based frameworks and archi... |
6b77e172bdb4a3ee1a9d8c1436769e99 | 102 830 | 5 Basic GCM component introspection | A GCM component provides introspection functions to introspect its external features, i.e. its boundary. This clause defines more precisely the external features of GCM components, and specifies the interfaces related to the introspection of these features. The interfaces related to the introspection (and reconfigurati... |
6b77e172bdb4a3ee1a9d8c1436769e99 | 102 830 | 5.1 External component structure | Depending on the level of observation, or scale, a GCM component can be seen as a black box or as a white box. When seen as a black box, i.e. when its internal organization is not visible, the only visible elements of a GCM component are some access points to this black box, called its external interfaces (see figure 1... |
6b77e172bdb4a3ee1a9d8c1436769e99 | 102 830 | 5.2 Component introspection API | In order to discover the external interfaces of a component, a component provides an interface that implements the Component interface (see figure 2). This language interface provides two operations named getFcInterfaces and getFcInterface, that can be used to retrieve the interfaces of the component. The first operati... |
6b77e172bdb4a3ee1a9d8c1436769e99 | 102 830 | 5.3 Interface introspection API | By default the references returned by the getFcInterface and getFcInterfaces operations provide access to the requested interfaces, and nothing more. In particular, it is impossible to find the names of these interfaces. In order to provide such interface introspection functions, a component ensures that the references... |
6b77e172bdb4a3ee1a9d8c1436769e99 | 102 830 | 6 GCM component configuration | At the next level of control capability, beyond the "introspection" level where components provide interfaces to introspect their external features, a GCM component can provide control interfaces to introspect and reconfigure its internal features. This clause defines these internal features, and specifies some predefi... |
6b77e172bdb4a3ee1a9d8c1436769e99 | 102 830 | 6.1 Internal component structure | A GCM component is formed out of two parts (see figure 4): a membrane and a content: The membrane (the grey part of the Composite component on the figure 4) is made of a set of controllers which expose non-functional interfaces (the green interface on the figure 4). The content of a component is either composed of an o... |
6b77e172bdb4a3ee1a9d8c1436769e99 | 102 830 | 6.2 Attribute control API | An attribute is a configurable property of a component, such as the text or color of a button, or the maximum size of a pool or cache component. Attributes are generally of primitive type, and are used to configure the state of components without needing to use bindings (it is possible to configure the text of a button... |
6b77e172bdb4a3ee1a9d8c1436769e99 | 102 830 | 6.3 Binding control API | A component can provide the BindingController interface to bind and unbind its client interfaces to other components through bindings (see figure 6). package org.objectweb.fractal.api.control; public interface BindingController { String[] listFc (); Object lookupFc (String clientItfName) throws NoSuchInterfaceException... |
6b77e172bdb4a3ee1a9d8c1436769e99 | 102 830 | 6.4 Content control API | A component can provide the ContentController interface to add and remove sub components in this component (see figure 7). package org.objectweb.fractal.api.control; public interface ContentController { Object[] getFcInternalInterfaces (); Object getFcInternalInterface (String itfName) throws NoSuchInterfaceException; ... |
6b77e172bdb4a3ee1a9d8c1436769e99 | 102 830 | 6.5 Life cycle control API | Changing an attribute or a binding, or removing a sub component, with the above control interfaces, and while components are executing, can be dangerous: messages can be lost, the application's state may become inconsistent, or the application may simply crash. In order to provide a minimal support to help implement su... |
6b77e172bdb4a3ee1a9d8c1436769e99 | 102 830 | 6.6 Collective interface control API | In order to provide facilities for parallel programming, GCM defines collective interfaces by adding new cardinalities in the specification of interfaces, namely multicast (see clause 6.7) and gathercast (see clause 6.8). The role and use of multicast and gathercast interfaces are complementary. Multicast interfaces ar... |
6b77e172bdb4a3ee1a9d8c1436769e99 | 102 830 | 6.7 Multicast control API | Multicast interfaces provide abstractions for 1-to-n communications, i.e. transform a single invocation into a list of invocations. A multicast server interface transforms each single invocation into a set of invocations that are forwarded either to implementation code of a primitive component, or to bound server inter... |
6b77e172bdb4a3ee1a9d8c1436769e99 | 102 830 | 6.8 Gathercast control API | A gathercast interface is an abstraction for n-to-1 communications, i.e. transforms a list of invocations into a single invocation. A gathercast interface coordinates incoming invocations before continuing the invocation flow: it may define synchronization barriers and may gather incoming data. Returned values are redi... |
6b77e172bdb4a3ee1a9d8c1436769e99 | 102 830 | 6.9 Migration control API | In distributed software systems, it is common to need to migrate some processes or some data from a node to another one. Within the context of the GCM, one may also need to do a migration on a component. In order to do that, a component can provide the MigrationController interface which allows the migration of this co... |
6b77e172bdb4a3ee1a9d8c1436769e99 | 102 830 | 6.10 Monitoring control API | Be informed in real time on the Quality of Service (QoS) of a component may be very useful. For instance, if a component has a bad QoS, then the user can decide to reconfigure the application by replacing this component by another one and thus improve the global performance. In term of GCM component, the QoS is defined... |
6b77e172bdb4a3ee1a9d8c1436769e99 | 102 830 | 6.11 Priority control API | By default, a component treats its requests, functional or non functional, in a FIFO order (First In First Out). Sometimes some non functional requests, like for instance life cycle management requests or reconfiguration requests, need to be executed before others. In order to define different priority levels for non f... |
6b77e172bdb4a3ee1a9d8c1436769e99 | 102 830 | 7 GCM component runtime instantiation | The frameworks presented in the previous clauses allow one to use, introspect, configure and reconfigure existing components. In order to be useful, they must be completed with a framework to create new components. This clause defines such a framework, based on factories. |
6b77e172bdb4a3ee1a9d8c1436769e99 | 102 830 | 7.1 Factories API | In the instantiation framework specified in this clause, components are created by other components called component factories. The GCM model distinguishes between generic component factories, which can create several kinds of components, and standard component factories, which can create only one kind of components, a... |
6b77e172bdb4a3ee1a9d8c1436769e99 | 102 830 | 7.2 Templates | A template is a special kind of standard factory component that creates components that are quasi "isomorphic" to itself. More precisely, the components created by a template component must have the same functional client and server interfaces as the template component (except for the Factory interface, which is provid... |
6b77e172bdb4a3ee1a9d8c1436769e99 | 102 830 | 7.3 Bootstrap | According to the above framework, components are created from component factories. But how are created component factories? They can be created from other component factories, but this leads to an infinite recursion. In order to stop it, a bootstrap component factory, which does not need to be created explicitly, and w... |
6b77e172bdb4a3ee1a9d8c1436769e99 | 102 830 | 8 GCM Typing | This clause defines a simple type system for components and component interfaces. This type system reflects the main characteristics of component interfaces, introduced in clause 5, i.e. their name, their language type, and their role (client or server). It also introduces two new characteristics named contingency and ... |
6b77e172bdb4a3ee1a9d8c1436769e99 | 102 830 | 8.1 Component interfaces contingency and cardinality | The contingency of an interface indicates if the functionality corresponding to this interface is guaranteed to be available or not, while the component is running: • The operations of a mandatory interface are guaranteed to be available when the component is running. This semantic is obvious for a server interface. Fo... |
6b77e172bdb4a3ee1a9d8c1436769e99 | 102 830 | 8.2 Type system API | In the type system specified here, a component type is just a set of component interface types. A component type is represented by the ComponentType interface (see figure 17). This interface defines a getFcInterfaceTypes operation, which returns the set of component interface types in this component type, as an array. ... |
6b77e172bdb4a3ee1a9d8c1436769e99 | 102 830 | 8.3 Sub typing relation | This clause defines a sub typing relation for component and component interface types, based on substitutability. This relation provides a sufficient (but not necessary) condition such that if a component type T1 is a sub type of T2, then a component of type T1 can replace a component of type T2 in any environment, thi... |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 1 Scope | The present document specifies IPCablecom, (also referred to as PacketCable) multimedia services over DOCSIS. |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 1.1 Purpose | The intent of the present document is to support the deployment of general Multimedia services by providing a technical definition of several IP-based signalling interfaces that leverage core QoS and policy management capabilities native to DOCSIS Versions 1.1 and greater. Throughout the present document, the term DOCS... |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 1.2 Relation to IPCablecom 1.x | Since its inception the IPCablecom initiative has been positioned as an IP-based Multimedia service deployment infrastructure, exploiting and enhancing the underlying QoS capabilities of the DOCSIS access network. Based on market demand and technology readiness, VoIP was chosen as the first IP-based service to leverage... |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 2 References | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the reference document (including any amendments) applies. Referenced documents which ar... |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 2.1 Normative references | The following referenced documents are necessary for the application of the present document. [1] ETSI TS 102 639-4: "Access and Terminals, Transmission and Multiplexing (ATTM); Third Generation Transmission Systems for Interactive Cable Television Services - IP Cable Modems; Part 4: MAC and Upper Layer Protocols [ITU-... |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 2.2 Informative references | The following referenced documents are not necessary for the application of the present document but they assist the user with regard to a particular subject area. [i.1] IETF RFC 2751 (January 2000): "Signaled Preemption Priority Policy Element". [i.2] SCTE 159-2 2010: "Multimedia Application and Service Part 2: IPCabl... |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 3 Definitions and abbreviations | |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply: Application Manager (AM): system that interfaces to Policy Server(s) for requesting QoS-based service on behalf of an end-user or network management system cable modem: layer two termination device that terminates the customer end of a... |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: AM Application Manager ACK Acknowledge AS Application Server BCID Billing Correlation ID NOTE: Defined in the IPCablecom Event Messaging specification. CM Cable Modem CMS Call Management Server CMSS Call Management Server Signalling ETSI ETSI ... |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 4 Void | |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 5 Technical Overview | This clause consists of background material which some readers may find to be useful context for the detailed protocol interface specifications that follow. The intent in this clause is to provide a high-level overview of the IPCablecom Multimedia architecture and the fundamental technologies upon which it is based. |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 5.1 QoS Background | As noted throughout the present document, one of the primary features of the IPCablecom Multimedia service framework lies in the fact that it provides IP-layer access to sophisticated QoS capabilities defined in DOCSIS versions 1.1 and greater and IPCablecom 1.x. This clause provides a brief overview of these capabilit... |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 5.1.1 DOCSIS QoS Summary | The DOCSIS 3.0 MAC and Upper Layer Protocols Interface Specification [1] defines a set of QoS facilities based on a fundamental network resource management construct known as a Service Flow. A Service Flow is defined as "a MAC-layer transport service which (1) provides unidirectional transport of packets from the upper... |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 5.1.1.1 DOCSIS 3.0 Multicast QoS Framework | In DOCSIS 3.0, a framework was developed for providing special QoS treatment for IP Multicast Sessions that were signalled via IP Multicast protocols such as IGMP and MLD. This framework relies on an incoming membership request or "JoinMulticastSession" to be evaluated against the CmtsGroupConfig table for the purposes... |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 5.1.2 IPCablecom 1.x QoS Summary | While the DOCSIS 3.0 MAC and Upper Layer Protocols Interface [1] specification defines the fundamental QoS mechanisms that form the core of the IPCablecom DQoS model, the IPCablecom DQoS specification [13] augments these capabilities with a COPS-based policy management framework. Just as the Service Flow represents the... |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 5.2 Architecture | The IPCablecom Multimedia technical report [15] describes an architecture framework and reference model for IPCablecom Multimedia. The present document applies the model contained in the architectural framework and adds normative requirements to provide a scalable, interoperable solution suitable for deploying IPCablec... |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 5.2.1 Client Types | The IPCablecom Multimedia tech report defines three kinds of client types: • Client Type 1, which represents existing "legacy" endpoints (e.g. PC applications, gaming consoles) that lack specific QoS awareness or signalling capabilities. This client has no awareness of DOCSIS, CableHome, or IPCablecom messaging, and he... |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 5.2.2 IPCablecom Multimedia Devices | In addition to the client (which typically resides at a subscriber's premises), IPCablecom Multimedia requires several network elements residing in, or accessible to and trusted by, the cable operator's network. In the process of describing these network elements throughout the present document we borrow heavily from s... |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 5.2.2.1 Application Server (AS) | The Application Server is a network entity that interfaces with the Application Manager that requests IPCablecom Multimedia services on behalf of clients. The AS may reside on the cable operator's network or it may reside outside of this domain and interact with the cable operator network via a particular trust relatio... |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 5.2.2.2 Application Manager (AM) | As noted in the preceding summary, the Application Manager is a network entity that defines SCD policies, coordinates subscriber-initiated requests for application sessions with access to the resources needed to meet those requests, and maintains application-level state. The AM may reside on the cable operator's networ... |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 5.2.2.3 Policy Server (PS) | As discussed in RFC 2753 [10], the policy management framework underlying IPCablecom Multimedia is based on the work of the IETF's Resource Allocation Protocol (RAP) working group. Since the Policy Server is situated between the Application Manager and the CMTS, it simultaneously plays a dual role as a "proxy" for AM-i... |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 5.2.2.3.1 Stateful and Stateless Policy Servers | There are two basic classes of Policy Servers - Stateful and Stateless. A Stateless Policy Server is a slight misnomer since it does maintain enough state to map Application Manager requests to the proper CMTS and maintain COPS session state, while a pure Stateless Policy Server maintains no state on any of the media s... |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 5.2.2.3.2 Modification of Requests and Responses by Policy Servers | Although nominally a part of the Resource Control Domain, the Policy Server can be an intermediary between the Service and the Resource Control Domains, in addition to its normal role of implementing cable operator-defined authorization and resource management procedures. In either of these capacities it may modify the... |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 5.2.2.4 Cable Modem Termination System (CMTS) | In describing the role of the CMTS network element, it is important to consider the relation among DOCSIS, IPCablecom 1.x and IPCablecom Multimedia functionality. While each of these suites of specifications addresses a specific set of functional requirements, each has also been defined in such a way that corresponding... |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 5.2.2.5 Record Keeping Server (RKS) | The IPCablecom Multimedia Record Keeping Server fulfils a similar role to the RKS in IPCablecom 1.x [14]. It receives Event Messages pertaining to policy decisions from the Policy Server and Event Messages pertaining to QoS resource usage from the CMTS. In the IPCablecom Multimedia architecture, the Record Keeping Serv... |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 5.2.3 IPCablecom Multimedia Interfaces | IPCablecom Multimedia builds on the IPCablecom 1.x suite of specifications. Where an IPCablecom Multimedia interface has a corollary in IPCablecom 1.x, IPCablecom Multimedia uses the same protocol, or an extension of the same protocol. ETSI ETSI TS 102 879 V1.1.1 (2010-06) 22 Cable Modem Policy Server CMTS Record Keepi... |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 5.2.3.1 Client and Application Manager Interface (mm-7) | The interface between the client and the Application Manager is out of scope. Typically, the Application Manager will, through some means beyond the scope of the present document, authenticate the client and ensure that the client is entitled to the Multimedia service. For example, the client may login to a web page an... |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 5.2.3.2 Application Manager and Policy Server Interface (pkt-mm-3) | This interface corresponds to the IPCablecom 1.x interface between a Call Agent and a Gate Controller. In IPCablecom 1.x this is a hidden, non-testable interface, and so there are no pre-existing protocol requirements on this interface. IPCablecom Multimedia requires the use of COPS [9] on this interface. In order to s... |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 5.2.3.3 Policy Server and CMTS Interface (pkt-mm-2) | This interface is essentially identical to the equivalent interface (between CMTS and Gate Controller) in IPCablecom 1.x. As in IPCablecom 1.x, COPS is used to transfer policy information between the Policy Server and the CMTS. The CMTS acts as a COPS PEP and the Policy Server acts as a COPS PDP. Following the IPCablec... |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 5.2.3.5 Client and Application Server Interface (mm-12) | The interface between the client and the Application Server is out of scope. Typically, the Application Server will, through some means beyond the scope of the present document, authenticate the client and ensure that the client is entitled to the Multimedia service. However it is accomplished, the Application Server m... |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 5.2.3.6 Application Server and Application Manager Interface (pkt-mm-11) | The interface between the Application Server and the Application Manager is defined in [i.2]. IPCablecom Multimedia requires the use Web Services on this interface as specified in [i.2]. Application Servers use this interface to send network resource requests on behalf of clients to the AM. The interface may also be us... |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 5.2.4 State Information | In this clause, we provide an overview of state location in an IPCablecom Multimedia system. In addition to maintaining detailed state information, devices send information about state transitions to the Record Keeping Server for purposes such as billing, fraud detection, session reconstruction, etc. |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 5.2.4.1 Application State | The Application Manager is at all times responsible for maintaining detailed knowledge of the state of the application media session. How it does so in detail is beyond the scope of the present document, but it is important to recognize that no devices other than the Application Manager are required or expected to main... |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 5.2.4.2 QoS Resource State | The CMTS naturally is aware of the detailed state of flows that it manages. The Policy Server (if it is a stateful Policy Server) may also maintain a notion of the state of QoS resources on a single CMTS; it may also collate the state information over several CMTSs so that it (and only it) knows the QoS state of the en... |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 6 Authorization Interface Description | This clause describes the interface between the Application Manager and the Policy Server, and the interface between the Policy Server(s) and the CMTS. The interface between the Application Manager and the Policy Server is translationally symmetric to the interface between the Policy Server and the CMTS. The interfaces... |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 6.1 Gates: The Framework for QoS Control | An IPCablecom Multimedia Gate is a logical representation of a policy decision that has been installed on the CMTS. A Gate is used to control access by a single IP flow to enhanced QoS Services provided by a DOCSIS cable network. Gates are unidirectional; a single Gate controls access to a flow in either the upstream o... |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 6.1.1 Gate Identification (GateID) | A GateID is an identifier that is locally allocated by the CMTS where the Gate resides. A GateID shall be associated with only one Gate. Whereas the IPCablecom 1.x DQoS Gate Control model generally assumed a pair of unidirectional Gates (one upstream and one downstream) per GateID in support of a typical two-way voice ... |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 6.1.2 Application Manager Identification (AMID) | The AMID consists of two fields: the Application Manager Tag and Application Type. Each Application Manager is pre-provisioned with an Application Manager Tag that is unique within the universe of a single service provider. The Application Manager may also be pre-provisioned with a set of Application Type values that c... |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 6.1.3 Subscriber Identification (SubscriberID) | The SubscriberID, consisting of the IPv4 or IPv6 address of either the CM or client CPE device (either directly connected to the CM or on a routable network behind the CM), identifies the user requesting the service. In complex network environments this address may be used to route Gate Control messages between a numbe... |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 6.1.4 Gate Specification (GateSpec) | The GateSpec describes some high-level attributes of the Gate, and contains information regarding the treatment of other objects specified in the Gate message. Information contained in a GateSpec is outlined below: • SessionClassID • Direction • Authorized Timer • Reserved Timer • Committed Timer • Committed Recovery T... |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 6.1.5 Classifier | A classifier shall be defined for a Gate. Additional classifiers may be included in the original Gate-Set. Classifiers may be added or deleted in a subsequent Gate-Set. Compliant implementations shall be able to support a minimum of four classifiers when processing a Gate-Set message for Unicast Gates. Compliant implem... |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 6.1.6 Traffic Profile | There are four basic ways to express the Traffic Profile for a Gate: 1) FlowSpec 2) DOCSIS Service Class Name, or 3) DOCSIS-Specific Parameterization 4) Upstream Drop The Policy Server or Application Manager shall define the Traffic Profile for a Gate using one of the following: (1) the FlowSpec, (2) DOCSIS Service Cla... |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 6.1.6.1 FlowSpec | The FlowSpec object contains RSVP FlowSpecs that are used to describe the Traffic Profile of the IP flow. The FlowSpec object can contain multiple RSVP FlowSpecs: • FlowSpec that defines the authorization resource envelope against which future reservations can be made. • FlowSpec that defines the reserved envelope agai... |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 6.1.6.2 DOCSIS Service Class Name | The DOCSIS Service Class Name indicates the DOCSIS Service Class to be used to describe the QoS attributes. A CMTS shall support DOCSIS Service Class Names. DOCSIS Service Class Name enables one to use pre-provisioned DOCSIS QoS parameters on the CMTS. On the CMTS, one can configure DOCSIS Named Service Classes with di... |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 6.1.6.3 DOCSIS Specific Parameterization | The third way of defining the Traffic Profile consists of using DOCSIS-specific Traffic Profile; this allows the Application Manager to explicitly specify the DOCSIS parameters of the DOCSIS flow. If the Application Manager wishes to use this third way of defining a Traffic Profile, it shall include an object containin... |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 6.1.6.4 Upstream Drop | An Upstream Drop Traffic Profile represents a null service flow for upstream traffic filtering at the CM. DOCSIS 3.0 refers to a null service flow at the CM as an Upstream Drop Classifier (UDC). An AM can push an Upstream Drop Traffic Profile to the CMTS, via the PS, which pushes the UDC to the CM. When a CM installs a... |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 6.1.7 Event Generation Info | This object contains information relevant to the CMTS in support of accounting and billing functions. Attributes include: • Primary Address: Port of the Primary Record Keeping Server to which the CMTS shall send event records. • Secondary Address: Port of the Secondary Record Keeping Server, the CMTS shall use as speci... |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 6.1.8 Time-Based Usage Limit | This object specifies amount of time a Gate can remain committed before meeting the time limit threshold for this Gate. The CMTS is not responsible for enforcing time limits, but shall store this object and return it upon request. |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 6.1.9 Volume-Based Usage Limit | The Application Manager uses the Volume-Based Usage Limit to signal the CMTS to generate a Gate Control message when the specified amount of data has traversed the Gate. The CMTS is not responsible for enforcing volume limits, but shall signal to the PS/AM when a volume limit is reached. |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 6.1.10 Opaque Data | Opaque Data consists of general information that a Policy Server or Application Manager can store on a CMTS. This data remains opaque to the CMTS, but contains information useful for the PS or AM. If provided by the PS/AM, the CMTS will return this object in all responses (see clause 6.4.2.11). |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 6.1.11 Gate Time Info | Gate Time Info contains a timestamp representing the time the Gate was committed. This may be queried and used by a Policy Server or Application Manager to enforce time-based network policy. |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 6.1.12 Gate Usage Info | Gate Usage Info consists of an octet counter indicating the number of bytes of data transmitted over this Gate (see clause 6.4.2.13). Analogous to the Gate Time Info object, this information may be used by a Policy Server or Application Manager to enforce volume-based network policy. ETSI ETSI TS 102 879 V1.1.1 (2010-0... |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 6.1.13 User Identification (UserID) | The UserID is a UTF-8 string value that identifies the user requesting the service. As defined earlier the SubscriberID defines the actual device requesting the service, but there may be multiple users that share that device. The UserID field allows the elements that manage the QoS to associate a request with a specifi... |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 6.1.14 Shared Resource Identification (SharedResourceID) | The SharedResourceID is only applicable to Multicast Gates and is locally generated by the CMTS. When a Multicast Gate request is successfully processed by the CMTS, the CMTS shall return a SharedResourceID in the Gate-Set-Ack to the Policy Server. The CMTS shall not include a SharedResourceID in Gate-Set-Ack messages ... |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 6.2 Gate Transitions | As briefly outlined earlier, a Gate may reside in the following logical states: • Authorized - a Policy Server has authorized the flow with resource limits defined • Reserved - resources have been reserved for the flow • Committed - resources are active and are being used • Committed-Recovery - inactivity has been dete... |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 6.2.1 Authorized | A Gate is created in the CMTS by a Gate-Set command from the Policy Server. The CMTS allocates a unique identifier called a GateID. The Gate is now said to be in the Authorized state and the CMTS shall start Timer T1. Timer T1 limits the amount of time the authorization remains valid. ETSI ETSI TS 102 879 V1.1.1 (2010-... |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 6.2.2 Reserved | A Gate in the Authorized state is expecting the client to attempt to reserve resources. In Scenario 1, the Policy Server reserves the resources on the client's behalf. To reserve resources, the Policy Server shall issue a subsequent Gate-Set message with a Traffic Profile that includes the Reserved Envelope. On receipt... |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 6.2.3 Committed | In the Reserved state the Gate is expecting the client to commit resources, and thereby activate them. In Scenario 1, the Policy Server commits the resources on the client's behalf. To commit resources, the Policy Server shall issue a Gate- Set command with a Traffic Profile that includes the Committed Envelope. The CM... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.