hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
1ae034a75bbe7d46c2fae998c5f3b869 | 102 827 | 7.1.16 Sun Grid Engine | Group definition for the Grid Engine framework [i.12]. The Sun Grid Engine group definition has the following child elements: • resource (string): this element has the following attributes: - nodes (positive integer): number of nodes requested; - parallelEnvironment (string): the name of the Grid Engine parallel enviro... |
1ae034a75bbe7d46c2fae998c5f3b869 | 102 827 | 8 XML files examples (informative) | |
1ae034a75bbe7d46c2fae998c5f3b869 | 102 827 | 8.1 Bridge protocols | |
1ae034a75bbe7d46c2fae998c5f3b869 | 102 827 | 8.1.1 rsh | <rshBridge id="brSchubby" hostname="schubby.inria.fr" username="${USERNAME}" /> ETSI ETSI TS 102 827 V1.1.1 (2008-08) 30 |
1ae034a75bbe7d46c2fae998c5f3b869 | 102 827 | 8.1.2 ssh | <sshBridge id="SEA" hostname="sea.inria.fr" username="${USERNAME}" commandPath="" /> |
1ae034a75bbe7d46c2fae998c5f3b869 | 102 827 | 8.1.3 oarsh | <oarshBridge id="oarbridge" hostname="oargrid.inria.fr" jobId="12" /> |
1ae034a75bbe7d46c2fae998c5f3b869 | 102 827 | 8.1.4 gsissh | <gsisshBridge id="gsibridge" hostname="grid11.lal.in2p3.fr" port="2222" certificate="${HOME}/.globus/usercred.p12" /> |
1ae034a75bbe7d46c2fae998c5f3b869 | 102 827 | 8.2 Group protocols | |
1ae034a75bbe7d46c2fae998c5f3b869 | 102 827 | 8.2.1 GroupSSH | <sshGroup id="LAN_INRIA" hostList="node2 node4 host[10-20]" username="${USERNAME}" commandPath="/usr/local/bin/ssh"> <scriptPath base="proactive" relpath="myscript.sh" /> </sshGroup> |
1ae034a75bbe7d46c2fae998c5f3b869 | 102 827 | 8.2.2 GroupRSH | <rshGroup id="LAN_INRIA" hostList="node2 node4 host[10-20]" username="${USERNAME}"> <scriptPath base="proactive" relpath="myscript.sh" /> </rshGroup> |
1ae034a75bbe7d46c2fae998c5f3b869 | 102 827 | 8.2.3 GroupOARSH | <oarshGroup id="oarshgroup" hostList="host1 host2" jobId="42"> <scriptPath base="proactive" relpath="scripts/unix/cluster/oarStartRuntime.sh" /> </oarshGroup> |
1ae034a75bbe7d46c2fae998c5f3b869 | 102 827 | 8.2.4 ARC (Nordugrid) | <arcGroup id="arcgroup" jobName="arcjob"> <scriptPath base="root" relpath="/usr/local/arc/scripts/unix/cluster/startRuntime.sh" /> <stderr>trace/err.log</stderr> <maxTime>10000000</maxTime> </arcGroup> |
1ae034a75bbe7d46c2fae998c5f3b869 | 102 827 | 8.2.5 CGSP China Grid | <cgspGroup id="cgspgroup" hostname="cgsp.inria.fr"> <scriptPath base="root" relpath="./calc" /> <count>50</count> <directory>datadir/jobdata1</directory> <stdout>trace/results.log</stdout> <stderr>trace/err.log</stderr> </cgspGroup> |
1ae034a75bbe7d46c2fae998c5f3b869 | 102 827 | 8.2.6 EGEE gLite | <gLiteGroup id="gliteGroup" virtualOrganisation="proactive" jobType="normal" retryCount="3"> <rank>-other.GlueCEStateEstimatedResponseTime</rank> <stdout>stdout.log</stdout> <stderr>error.log</stderr> <configFile>scripts/unix/proactiveVO/proactiveVO.conf</configFile> </gLiteGroup> ETSI ETSI TS 102 827 V1.1.1 (2008-08) ... |
1ae034a75bbe7d46c2fae998c5f3b869 | 102 827 | 8.2.7 Fura/InnerGrid | <furaGroup id="furagroup" jobName="furajob"> <scriptPath base="root" relpath="/usr/local/fura/scripts/jobscript.sh" /> <description>Fura job descriptor sample</description> <stdout>trace/results.log</stdout> <stderr>trace/err.log</stderr> <maxTime>15000000</maxTime> </furaGroup> |
1ae034a75bbe7d46c2fae998c5f3b869 | 102 827 | 8.2.8 GLOBUS | <globusGroup hostname="globus_frontend" id="globusgroup"> <count>8</count> <maxTime>120</maxTime> <stderr>${GLOBUS_USER_HOME}/error.txt</stderr> </globusGroup> |
1ae034a75bbe7d46c2fae998c5f3b869 | 102 827 | 8.2.9 GridBus | <gridbusGroup id="gridbusgroup"> <scriptPath base="root" relpath="./calc" /> <arguments> <arg>arg1</arg> <arg>arg2</arg> </arguments> </gridbusGroup> |
1ae034a75bbe7d46c2fae998c5f3b869 | 102 827 | 8.2.10 IBM load leveler | <loadLevelerGroup id="loadlevelergroup"> <scriptPath base="root" relpath="/usr/local/loadleveler/scripts/jobscript.sh" /> <directory>datadir/jobdata1</directory> <stdout>trace/results.log</stdout> <stderr>trace/err.log</stderr> <maxTime>15000000</maxTime> <arguments> <arg>arg1</arg> <arg>25</arg> <arg>foo bar</arg> </a... |
1ae034a75bbe7d46c2fae998c5f3b869 | 102 827 | 8.2.11 LSF | <lsfGroup id="lsfgroup"> <scriptPath base="proactive" relpath="scripts/unix/cluster/startRuntime.sh" /> <processorsNumber>2</processorsNumber> <resourceRequirement>value="span[ptile=2]"</resourceRequirement> </lsfGroup> |
1ae034a75bbe7d46c2fae998c5f3b869 | 102 827 | 8.2.12 Microsoft CCS | <ccsGroup id="ccs" bookedNodesAccess="rsh"> <resources cpus="9" runtime="01:01:01"/> <!-runtime=days:hours:min --> <stdout>\\HN\work\out</stdout> <stderr>\\HN\work\err</stderr> </ccsGroup> |
1ae034a75bbe7d46c2fae998c5f3b869 | 102 827 | 8.2.13 OAR | <oarGroup bookedNodesAccess="ssh" id="oargroup" interactive="true"> <scriptPath base="proactive" relpath="scripts/unix/cluster/oarStartRuntime.sh" /> <resource nodes="2" cpu="4" /> <stderr>trace/err.log</stderr> </oarGroup> ETSI ETSI TS 102 827 V1.1.1 (2008-08) 32 |
1ae034a75bbe7d46c2fae998c5f3b869 | 102 827 | 8.2.14 PBS / Torque | <pbsGroup id="pbsgroup1" queue="queue01@pbsserver" jobName="demoJob" commandPath="/usr/local/bin/pbs"> <scriptPath base="home" relpath="scripts/pbsjob.sh" /> <nodes>50</nodes> </pbsGroup> |
1ae034a75bbe7d46c2fae998c5f3b869 | 102 827 | 8.2.15 PRUN | <prunGroup id="prungroup1" queue="prunqueue"> <hostList>prunhost[00-10]</hostList> <processorPerNode>2</processorPerNode> </prunGroup> |
1ae034a75bbe7d46c2fae998c5f3b869 | 102 827 | 8.2.16 Sun Grid Engine | <gridEngineGroup id="gridEngineGroup"> <scriptPath base="home" relpath="jobs/jobscript1.sh" /> <hostsNumber>10</hostsNumber> <wallTime>500000</wallTime> <directory>"jobs/job_datas</directory> <stderr>jobs/jobtrace_err.txt</stderr> </gridEngineGroup> ETSI ETSI TS 102 827 V1.1.1 (2008-08) 33 Annex A (normative): XML Sche... |
f9c06bdedc6dec42cf383c16bfc752af | 102 826 | 1 Scope | DVB has produced a specification for the delivery of MPEG-2 TS based DVB services over IP networks, referred to as the DVB-IPTV handbook [1]. The DVB-IPTV handbook covers several types of IPTV services (e.g. Live Media Broadcast, Content on Demand, Content Download). It has become evident that every building block in t... |
f9c06bdedc6dec42cf383c16bfc752af | 102 826 | 2 References | |
f9c06bdedc6dec42cf383c16bfc752af | 102 826 | 2.1 Normative 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... |
f9c06bdedc6dec42cf383c16bfc752af | 102 826 | 2.2 Informative 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. NOTE: While any hyperlinks in... |
f9c06bdedc6dec42cf383c16bfc752af | 102 826 | 3 Definitions and abbreviations | |
f9c06bdedc6dec42cf383c16bfc752af | 102 826 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply: extension: non-required option that can be added to a profile in order to enhance it module: set of options (protocol and media format) for fulfilling a given functionality of the DVB-IPTV handbook option: one technical possibility for... |
f9c06bdedc6dec42cf383c16bfc752af | 102 826 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: AL-FEC Application Layer Forward Error Control BCG Broadband Content Guide CDS Content Download Service CoD Content on Demand DVBSTP DVB SD&S Transport Protocol EIT Event Information Table EPG Electronic Program Guide FEC Forward Error Control... |
f9c06bdedc6dec42cf383c16bfc752af | 102 826 | 4 Overview | |
f9c06bdedc6dec42cf383c16bfc752af | 102 826 | 4.1 Rationale | The DVB-IPTV handbook specifies the protocols and mechanisms that shall be supported on the interface to the HNED defined as IPI-1 in ETSI TS 102 034 [1], clause 4 and covers several types of IPTV services (e.g. Live Media Broadcast, CoD, Content Download). In order to be compliant, an HNED will need to support all the... |
f9c06bdedc6dec42cf383c16bfc752af | 102 826 | 4.2 Concept | The present document uses the following terminology: profile: a collection of functionalities making use of a set of options taken from the modules, that defines a point of interoperability for DVB-IPTV ecosystems. Profiles may additionally include extensions, which may enhance or complement functionalities. module: a ... |
f9c06bdedc6dec42cf383c16bfc752af | 102 826 | 4.3 Service and Device Impacts | The DVB-IPTV handbook defines the protocols and data structures that are used "on the wire", i.e. between servers and clients and that shall be supported on the interface to the HNED (IPI-1). So when different technologies are available in the handbook to perform a specific functionality, the HNED will need to implemen... |
f9c06bdedc6dec42cf383c16bfc752af | 102 826 | 5 DVB-IPTV Handbook Modules | |
f9c06bdedc6dec42cf383c16bfc752af | 102 826 | 5.1 Foundation Layer/Provisioning Module | This module provides all IP connectivity (i.e. addressing, routing; etc.) needed for the HNED to communicate with its IP environment and to connect to a service provider. It regroups: • Address assignment and device configuration. • IP address autoconfiguration. NOTE: This module is mandatory in every profile. |
f9c06bdedc6dec42cf383c16bfc752af | 102 826 | 5.2 Media Transport Module | Two transport technologies may be used to deliver streamed IPTV services (LMB and CoD): • UDP only (ETSI TS 102 034 [1], clause 7.1.2); • RTP/UDP (ETSI TS 102 034 [1], clause 7.1.1). ETSI ETSI TS 102 826 V2.1.1 (2016-04) 9 NOTE: The RTP layer as defined within the DVB-IPTV handbook does not require all the features des... |
f9c06bdedc6dec42cf383c16bfc752af | 102 826 | 5.3 Connection Module | The DVB-IPTV handbook specifies connection protocols depending on the type of IPTV services: • For a Live Media Broadcast Service (delivered over multicast), IGMP is required for IPv4 and MLD Version 2 for IPv6 (ETSI TS 102 034 [1], clause 7.3.1); additionally RTSP may be used (ETSI TS 102 034 [1], clause 6.5). • For a... |
f9c06bdedc6dec42cf383c16bfc752af | 102 826 | 5.4 Media Format Module | The DVB-IPTV handbook references ETSI TS 101 154 [3] for audio and video coding formats based on MPEG-2 Transport Stream content delivery. ETSI TS 101 154 [3] proposes a set of coding formats for audio and video. For example, video can be MPEG2, H264 SD, H264 HD, VC-1 SD, etc. The profiles defined in the present docume... |
f9c06bdedc6dec42cf383c16bfc752af | 102 826 | 5.5 Service Discovery Module | SD&S is the mandatory service discovery solution of the DVB-IPTV handbook. There are two ways to receive SD&S data: • Pull mode with HTTP (ETSI TS 102 034 [1], clause 5.4.2). • Push mode with DVBSTP (ETSI TS 102 034 [1], clause 5.4.1). Both modes shall be supported by an HNED to discover DVB-IPTV services. The Broadban... |
f9c06bdedc6dec42cf383c16bfc752af | 102 826 | 5.6 Metadata Module | The DVB-IPTV handbook relies on three options to define a complete set of DVB-IPTV metadata: • The SI/PSI tables of the MPEG-2 TS stream. • The SD&S XML data structure for service related metadata. • TV-A elements for content related metadata delivered via the Broadband Content Guide, called BCG-TVA hereafter. Furtherm... |
f9c06bdedc6dec42cf383c16bfc752af | 102 826 | 5.7 Reliable Transport Module | For LMB and CoD services, the DVB-IPTV handbook defines two options for packet loss repair, enabling reliable transport for streamed IPTV services: • Application Layer Forward Error Correction (AL-FEC), (ETSI TS 102 034 [1], annex E). • Retransmission (RET), (ETSI TS 102 034 [1], annex F). Either option may be used in ... |
f9c06bdedc6dec42cf383c16bfc752af | 102 826 | 6 Profiles | 6.0 Overview This clause defines four profiles for DVB-IPTV systems. Each profile lists the required modules and the required options within each module. NOTE: The foundation layer/provisioning module is required in each profile and is not listed under each profile to ease readability. |
f9c06bdedc6dec42cf383c16bfc752af | 102 826 | 6.1 Basic | This profile is defined to accommodate existing IPTV deployments. It can therefore be seen as a first step for an operator to achieve a basic degree of DVB-IPTV compliancy with its existing network and HNEDs. The following options shall be supported: • transport: UDP; • connection: IGMP for IPv4 or MLD for IPv6; • form... |
f9c06bdedc6dec42cf383c16bfc752af | 102 826 | 6.2 Live Media Broadcast (LMB) | This profile defines the required subset to build live IPTV services. The following options shall be supported: • transport: UDP and RTP/UDP; • connection: IGMP for IPv4 or MLD for IPv6; • format: Refer to ETSI TS 101 154 [3]; • discovery: SD&S; • metadata: SI/PSI tables in the MPEG2-TS stream and SD&S XML data. |
f9c06bdedc6dec42cf383c16bfc752af | 102 826 | 6.3 Content On Demand (CoD) | This profile defines the required subset to build On-Demand IPTV services. The following options shall be supported: • transport: UDP and RTP/UDP; ETSI ETSI TS 102 826 V2.1.1 (2016-04) 12 • connection: RTSP; • format: Refer to ETSI TS 101 154 [3]; • discovery: SD&S and BCG; • metadata: SD&S XML data and BCG-TVA. |
f9c06bdedc6dec42cf383c16bfc752af | 102 826 | 6.4 Content Download (CDS) | This profile defines the required subset to build IPTV Content Download Services. The following options shall be supported: • Transport: HTTP/TCP and FLUTE/UDP • Connection: HTTP and IGMP for IPv4 or MLD for IPv6 • Format: - Audio/Video: Refer to ETSI TS 101 154 [3] document. - Content-Item-Format: 0, 1, and 2. - File-... |
f9c06bdedc6dec42cf383c16bfc752af | 102 826 | 7 Extensions | Extensions can be defined as enhancement to profiles. This clause presents a non exhaustive list of possible extensions: Reliable transport • The addition of the Hybrid AL-FEC system, as defined in the DVB-IPTV handbook, enables a more reliable streaming technology. - Targeted Profiles: LMB, CoD. • The addition of the ... |
f9c06bdedc6dec42cf383c16bfc752af | 102 826 | 8 Profile Summary | Table 1 summarizes the four defined profiles. Please refer to the relevant profile clause for more details. For each of those profiles, the foundation/provisioning module (not shown) is required and extensions can be used, as presented in clause 7. Table 1 Profiles Modules Transport Connection Format Discovery Metadata... |
8160ae4af643c46b22f2fcd33650562f | 102 842 | 1 Scope | The present document applies to the following radio equipment types: • Very High Frequency (VHF) Digital Link (VDL) Mode 4 aeronautical mobile (airborne) radio transmitters, transceivers and receivers for air-ground and air-air communications operating in the VHF band, using Gaussian Filtered Frequency Shift Keying (GF... |
8160ae4af643c46b22f2fcd33650562f | 102 842 | 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... |
8160ae4af643c46b22f2fcd33650562f | 102 842 | 2.1 Normative references | The following referenced documents are necessary for the application of the present document. [1] ICAO Doc. 9816 - AN/448 (First Edition 2004): "Manual on VHF Digital Link (VDL) Mode 4, Part 2, Detailed Technical Specifications". [2] ICAO Annex 10 to the Convention on International Civil Aviation: "Aeronautical Telecom... |
8160ae4af643c46b22f2fcd33650562f | 102 842 | 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] ISO/IEC 7498-1 (1994): "Information technology - Open Systems Interconnection - Basic Reference Model: The Basic Model". [i.2] ISO/IEC 10731 (1994): "... |
8160ae4af643c46b22f2fcd33650562f | 102 842 | 3 Definitions and abbreviations | |
8160ae4af643c46b22f2fcd33650562f | 102 842 | 3.1 Definitions | |
8160ae4af643c46b22f2fcd33650562f | 102 842 | 3.1.1 Basic reference model definitions | The present document is based on the concepts developed in the open systems interconnect basic reference model and makes use of the following terms defined in ISO/IEC 7498-1 [i.1]: • layer; • sublayer; • entity; • service; • service access point; ETSI ETSI TS 102 842 V1.2.3 (2011-11) 8 • service data unit; • physical l... |
8160ae4af643c46b22f2fcd33650562f | 102 842 | 3.1.2 Service conventions definitions | The present document makes use of the following terms defined in ISO/IEC 10731 [i.2]: • service provider; • service user; • service primitive; • request; • indication; • confirm. |
8160ae4af643c46b22f2fcd33650562f | 102 842 | 3.1.3 General definitions | For the purposes of the present document, the terms and definitions given in EN 302 842-1 [3], EN 302 842-2 [4] and the following apply: Aeronautical Mobile Service (AMS): mobile service between aeronautical stations and aircraft stations, or between aircraft stations, in which survival craft stations may participate A... |
8160ae4af643c46b22f2fcd33650562f | 102 842 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: A/A Air-to-Air A/G Air-to-Ground ADS-B Automatic Dependent Surveillance - Broadcast AMS Aeronautical Mobile Service ANSP Air Navigation Service Provider ATN Aeronautical Telecommunication Network DLE Data Link Entity DLS Data Link Service FIS-... |
8160ae4af643c46b22f2fcd33650562f | 102 842 | 4 General description and architecture of VDL Mode 4 | |
8160ae4af643c46b22f2fcd33650562f | 102 842 | 4.1 General | A description of VDL Mode 4, the communication services provided, the equipment classes, the structure of the standards material and guidance on equipment performance verification is provided in EN 302 842-2 [4], clause 4. In most respects, the VDL Mode 4 mobile station follows the provisions of the ICAO standards mate... |
8160ae4af643c46b22f2fcd33650562f | 102 842 | 4.2 Coverage of the interoperability Regulation | Table 4.1 indicates which of the essential requirements in the interoperability Regulation [i.3] are considered in the present document. Table 4.1: Coverage of the interoperability regulation Essential requirements Part A: General requirements No. Title Constituent level System level Explanation A1 Seamless operation P... |
8160ae4af643c46b22f2fcd33650562f | 102 842 | 4.3 Scope of interoperability | It is only possible to trace the constituent parts of the VDL Mode 4 airborne equipment with the interoperability Regulation. System-level configurations are outside the scope of the present document, as they are not manufacturer-specific. |
8160ae4af643c46b22f2fcd33650562f | 102 842 | 5 Traceability to interoperability essential requirements | |
8160ae4af643c46b22f2fcd33650562f | 102 842 | 5.1 Requirement traceability | EC 552/2004 [i.3] has been examined by ETSI TC AERO and the VDLM4 ground station equipment shows compliance with the requirements stated in the present document. ETSI ETSI TS 102 842 V1.2.3 (2011-11) 13 Annex A (informative): Bibliography • EUROCAE ED-78A: "Guidelines for approval of the provision and use of ATS suppor... |
07b87412fe3e812cff4e859a34ef2e84 | 102 825-14 | 1 Scope | The present document is the specification of the Digital Video Broadcasting (DVB) Content Protection and Copy Management (CPCM) Extensions. It contains the normative specifications of each standardized Extension to CPCM. |
07b87412fe3e812cff4e859a34ef2e84 | 102 825-14 | 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 referenced document (including any amendments) applies. Referenced documents which a... |
07b87412fe3e812cff4e859a34ef2e84 | 102 825-14 | 2.1 Normative references | The following referenced documents are necessary for the application of the present document. [1] ETSI TS 102 825-1: "Digital Video Broadcasting (DVB); Content Protection and Copy Management (DVB-CPCM); Part 1: CPCM Abbreviations, Definitions and Terms". [2] ETSI TS 102 825-4: "Digital Video Broadcasting (DVB); Content... |
07b87412fe3e812cff4e859a34ef2e84 | 102 825-14 | 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] ETSI TS 101 154: "Digital Video Broadcasting (DVB); Specification for the use of Video and Audio Coding in Broadcasting Applications based on the MPEG... |
07b87412fe3e812cff4e859a34ef2e84 | 102 825-14 | 3 Definitions and abbreviations | |
07b87412fe3e812cff4e859a34ef2e84 | 102 825-14 | 3.1 Definitions | For the purposes of the present document, the terms and definitions given in TS 102 825-1 [1] apply. |
07b87412fe3e812cff4e859a34ef2e84 | 102 825-14 | 3.2 Abbreviations | For the purposes of the present document, the abbreviations given in TS 102 825-1 [1] apply. ETSI ETSI TS 102 825-14 V1.1.1 (2011-02) 6 |
07b87412fe3e812cff4e859a34ef2e84 | 102 825-14 | 4 Introduction | The CPCM System provides an interoperability platform and common trusted destination for commercial content in the consumer environment. CPCM is a flexible system that can be extended both in a standard way and in a proprietary way. The present document describes CPCM Extensions standardised by DVB together with corres... |
07b87412fe3e812cff4e859a34ef2e84 | 102 825-14 | 5 Interoperability | A CPCM Extension implementation is optional. A CPCM Instance receiving a CPCM message as described in TS 102 825-4 [2] shall ignore any element relative to an extension it does not contain and shall thus behave as if the extension element was not present. It shall ignore any message dedicated to an extension, such as C... |
07b87412fe3e812cff4e859a34ef2e84 | 102 825-14 | 6 Play Count Extension | |
07b87412fe3e812cff4e859a34ef2e84 | 102 825-14 | 6.1 Play Count Extension definition | The purpose of this extension is to limit the number of consecutive plays of a given content item. If USI SVCA is not asserted, any number of simultaneous plays is allowed. If SVCA is asserted, the number of granted permissions in SVCA determines the maximum number of simultaneous viewings that constitutes one play. Th... |
07b87412fe3e812cff4e859a34ef2e84 | 102 825-14 | 6.2 Play Count Data element | Play count extension makes use of one extension data element CPCM_play_count_data_element. This, data element is composed of two fields: CPCM_play_limit and CPCM_play_remaining. CPCM_play_limit is an 8-bit integer that, when inserted in a CPCM Auxiliary Data relative to a CPCM Content Licence, gives the original play c... |
07b87412fe3e812cff4e859a34ef2e84 | 102 825-14 | 6.3 Play Count protocols | There are no protocols specific to the play count Extension. Play count extension affects the Move protocol. This protocol can be used to move content with a partial amount of the outstanding authorised plays to another Storage Entity. To that end, play count data element shall be inserted in the optional part, as desc... |
07b87412fe3e812cff4e859a34ef2e84 | 102 825-14 | 6.4 Content Management | |
07b87412fe3e812cff4e859a34ef2e84 | 102 825-14 | 6.4.1 USI setting | The Play Count extension may be used in conjunction with any USI settings. However, when used with the following USI, the Play Count extension can no more be enforced: • If Copy Control Information is set to Copy Control Not Asserted, any number of copies may be made by any CPCM Instance, including a CPCM Instance that... |
07b87412fe3e812cff4e859a34ef2e84 | 102 825-14 | 6.4.2 Device and Content Discovery | The presence of Play Count Extension in Auxiliary Data shall be signalled with other present Auxiliary Data. In addition to advertising the content as "Not Viewable" with "Copy Once" or with "Copy No More", as described in clause 6.4.1, and play count extension, Storage Entities and Acquisition Points shall also advert... |
07b87412fe3e812cff4e859a34ef2e84 | 102 825-14 | 6.4.3 CPCM Functional Entity Behaviour | A CPCM Instance that does not support this extension shall ignore it and enforce the USI as if the Extension was not present. Only CPCM Acquisition Points and Storage Entities shall adopt a specific behaviour with regard to Play Count Extension. This specific behaviour concerns the USI enforcement step, as described in... |
07b87412fe3e812cff4e859a34ef2e84 | 102 825-14 | 6.4.4 USI Enforcement | |
07b87412fe3e812cff4e859a34ef2e84 | 102 825-14 | 6.4.4.1 Controls prior to content transfer | All the controls related to the USI setting shall be performed with exception to the "Viewable" USI that can be sourced to Consumption Points or Export Point under the conditions described below. The behaviour described below regards only Acquisition Points or Storage Entities implementing the Extension. All other Acqu... |
07b87412fe3e812cff4e859a34ef2e84 | 102 825-14 | 6.4.4.2 Controls to be enforced when receiving content | All the controls related to the other USI setting shall be performed. There is no specific control related to Play Count extension. |
07b87412fe3e812cff4e859a34ef2e84 | 102 825-14 | 6.5 Move Protocol | Before starting the Move protocol, the Source CPCM Instance checks whether the number of counts to be moved is lower than the remaining count. If not, or if this number was not given in the Move invitation, either from the peer CPCM Instance of from the user interface, it shall Move the entire count. If all the remaini... |
07b87412fe3e812cff4e859a34ef2e84 | 102 825-14 | 6.6 Content Licence Management | |
07b87412fe3e812cff4e859a34ef2e84 | 102 825-14 | 6.6.1 Content Licence Generation | Content Licence is generated as described in TS 102 825-4 [2]. A new CL shall be generated, with updated Auxiliary Data digest, each time a new play or a CL move with partial count occurs. |
07b87412fe3e812cff4e859a34ef2e84 | 102 825-14 | 6.6.2 Content Licence Verification | Content Licence shall be verified as described in TS 102 825-4 [2]. |
07b87412fe3e812cff4e859a34ef2e84 | 102 825-14 | 6.6.3 Content Licence Protection | The Play Count Extension requires SAC/Device protection mode for the associated Content Licence. The protection mode for Content Licence shall be chosen as described in TS 102 825-4 [2]. ETSI ETSI TS 102 825-14 V1.1.1 (2011-02) 11 List of Tables Table 1: CPCM Extension Identifiers ......................................... |
41d5ff7eaa72e4aeb997791237125391 | 102 836-2 | 1 Scope | The present document specifies the internal network interfaces to enable the lawful interception (LI) of IP Data services over cable operators broadband IP Networks. The current document describes the LI functional elements and interfaces for both the NCS based and SIP protocol signalling architectures within a PacketC... |
41d5ff7eaa72e4aeb997791237125391 | 102 836-2 | 1.1 Requirements notation | If the present document is implemented, the key words "MUST" and "SHALL" as well as "REQUIRED" are to be interpreted as indicating a mandatory aspect of the present document. The keywords indicating a certain level of significance of a particular requirement that are used throughout the present document are summarized ... |
41d5ff7eaa72e4aeb997791237125391 | 102 836-2 | 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... |
41d5ff7eaa72e4aeb997791237125391 | 102 836-2 | 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] Council Resolution of 17 January 1995 on the lawful i... |
41d5ff7eaa72e4aeb997791237125391 | 102 836-2 | 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] ETSI TR 102 661 (November 2008): "Lawful Interce... |
41d5ff7eaa72e4aeb997791237125391 | 102 836-2 | 3 Abbreviations | For the purposes of the present document, the following abbreviations apply: CC Call Content CCC Communication Call Content CMTS Cable Modem Termination System CRD Call Related Details DA Destination Address DHCP Dynamic Host Configuration Protocol eMTA embedded Media Terminal Adapter HFC Hybrid Fiber Coax HI Handover ... |
41d5ff7eaa72e4aeb997791237125391 | 102 836-2 | 4 Requirements | European cable operators are required to have the capability of intercepting messages passed over their networks system in any form. This capability should be covert, not affect the operation of the system in any discernible way or be detectable by the end user. Therefore, a European implementation for a Cable Broadban... |
41d5ff7eaa72e4aeb997791237125391 | 102 836-2 | 5 Overview | The overall interception framework is extended from the model described in clause 5.2 of ES 201 158 [14] and from the architecture identified in clause 5 of TS 101 671 as given by [3]. NW O/AP /SvP’s adm inistration function IRI m ediation function CC m ediation function Network Internal Functions IIF INI inte rcept re... |
41d5ff7eaa72e4aeb997791237125391 | 102 836-2 | 6 Internal Cable Network Interfaces |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.