hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
7cf120a21056315aaef66bde1bab5205 | 102 792 | 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... |
7cf120a21056315aaef66bde1bab5205 | 102 792 | 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... |
7cf120a21056315aaef66bde1bab5205 | 102 792 | 3 Definitions, symbols and abbreviations | |
7cf120a21056315aaef66bde1bab5205 | 102 792 | 3.1 Definition | For the purposes of the present document, the following terms and definitions apply: CEN DSRC: dedicated short range communication as specified in CEN EN 12253 [3], CEN EN 12795 [4] and ETSI EN 300 674 [i.4] ETSI ETSI TS 102 792 V1.2.1 (2015-06) 7 coexistence mode: operational mode of an ITS station that avoids harmful... |
7cf120a21056315aaef66bde1bab5205 | 102 792 | 3.2 Symbols | For the purposes of the present document, the following symbols apply: d distance d0 reference distance for path loss model (1 m) Lant antenna loss due to polarization or windscreen N number of interfering ITS stations NITS number of ITS stations within the protected zone radius n path loss coefficient PL free space pa... |
7cf120a21056315aaef66bde1bab5205 | 102 792 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: CEN Comité Européen de Normalisation CVIS Cooperative Vehicle-Infrastructure Systems NOTE: CVIS was a European project. C-ITS Cooperative Intelligent Transport Systems DEC Decision DENM Decentralised Environmental Notification Message DSRC Ded... |
7cf120a21056315aaef66bde1bab5205 | 102 792 | 4 General overview | |
7cf120a21056315aaef66bde1bab5205 | 102 792 | 4.1 Introduction | Cooperative ITS (C-ITS) uses wireless communication between ITS stations in the frequency bands ITS-G5A/B/D according to ECC/DEC/(08)01 [i.2], ECC/REC/(08)01 [i.3] and ETSI EN 302 571 [i.5]. ITS stations can be: • fixed, mounted at a fixed geographical position, often close to a road or street (roadside ITS stations); ... |
7cf120a21056315aaef66bde1bab5205 | 102 792 | 4.2 Field strength thresholds for coexistence | A continuous interfering signal within the frequency band from 5 855 MHz to 5 925 MHz (ITS-G5A/B/D band) does not cause harmful interference to the CEN DSRC downlink from the RSU to the OBU, when the electric field strength of this signal within the tolling zone does not exceed 0,11 V/m (-51,6 dBm). A continuous linear... |
7cf120a21056315aaef66bde1bab5205 | 102 792 | 4.3 ITS output power thresholds for coexistence | Taking the field strength thresholds for coexistence at the CEN DSRC OBU antenna and RSU antenna from clause 4.2 into account, the TX power thresholds for ITS transmitters can be calculated for typical use cases. These calculation results are summarized in this clause and requirements based on them are given in clause ... |
7cf120a21056315aaef66bde1bab5205 | 102 792 | 4.4 Duty cycle limits | CEN DSRC is based on a packet communication. Typical frames have a duration of 0,5 ms to 2,5 ms. Inter frame time is implementation specific but often in the range 5 ms to 10 ms. The time of a payment transaction may vary between 25 ms and 1 s. C-ITS is also based on packet communication. Typical frames have a duration... |
7cf120a21056315aaef66bde1bab5205 | 102 792 | 4.5 Procedures | An ITS station may switch between two modes, normal mode and coexistence mode, where in normal mode: • transmit duty cycle is not limited; • output power level is limited to the values specified in ETSI EN 302 571 [i.5] clause 6.3; ETSI ETSI TS 102 792 V1.2.1 (2015-06) 11 • unwanted emissions in the band 5 795 MHz to 5... |
7cf120a21056315aaef66bde1bab5205 | 102 792 | 5 Interference mitigation mechanisms | 5.1 Introduction and basic requirements Each tolling CEN DSRC area shall be associated with a circular protected zone, surrounding the station, designed to protect it from harmful interference from ITS stations. An ITS station in the protected zone shall operate in coexistence mode (detailed in clause 5.4). For mobile ... |
7cf120a21056315aaef66bde1bab5205 | 102 792 | 5.2 Protected zone | 5.2.1 Protected zone definition The protected zone is defined by a centre position and a radius. Protected zones can be either permanently defined by their centre positon for e.g. fixed CEN DSRC tolling installations, or the centre positions are only temporary valid, e.g. for tolling enforcement vehicles. 5.2.2 Protect... |
7cf120a21056315aaef66bde1bab5205 | 102 792 | 5.2.2.1 Protected zone centre position overview | Mobile and personal ITS stations operating in normal mode shall be able to receive and interpret information about protected zones transmitted in the data field CenDsrcTollingZone and in the data field ProtectedCommunicationZone as described in ETSI EN 302 637-2 [1] and ETSI TS 102 894-2 [2], clauses A.105 and A.121. A... |
7cf120a21056315aaef66bde1bab5205 | 102 792 | 5.2.2.2 Temporary protected zone centre positions | Only one temporary position shall be considered by each mobile ITS-S at the same time. The stored temporary protected zone position shall be updated by either • the result of the detection of a protected zone centre position (see clause 5.2.5), or • the reception of one protected zone centre position in the data field ... |
7cf120a21056315aaef66bde1bab5205 | 102 792 | 5.2.2.3 Protected zone centre position list | A protected zone centre position list shall be implemented when no update mechanism (see clause 5.2.4) for the protected zone database solution is realized. Otherwise, the protected zone centre position list is optional. When a protected zone centre position list is used in an ITS station, following requirements apply:... |
7cf120a21056315aaef66bde1bab5205 | 102 792 | 5.2.3 Protected zone radius | For ITS stations with default ITS radio parameters the default protected zone radius is stored in the protected zone database or it can be transmitted in a CAM from a roadside ITS station. When a protected zone centre position list is used in an ITS station, and a CAM from a ITS station with a station type roadSideUnit... |
7cf120a21056315aaef66bde1bab5205 | 102 792 | 5.2.5 Short range protected zone radio detection | When a protected zone database solution is not used in a mobile or a personal ITS station, and it is not permanently operating in coexistence mode A or B (see clause 5.4), it shall detect the transmissions of a CEN DSRC or HDR DSRC tolling station by continuously monitoring the 5 795 MHz to 5 815 MHz band for either: •... |
7cf120a21056315aaef66bde1bab5205 | 102 792 | 5.4 Coexistence mode | In coexistence mode additional restrictions apply. These restrictions apply to output power level, unwanted emissions and transmit timing. The restrictions are designed to decrease the interference from ITS stations to a level which implies no harmful performance degradation of CEN DSRC based toll stations. An ITS stat... |
7cf120a21056315aaef66bde1bab5205 | 102 792 | 5.5 Procedures | 5.5.1 Mobile and personal ITS stations Mobile and personal ITS stations shall apply the following procedure: 1) All ITS stations shall determine the distance d to the closest protected zone centre position. The closest position shall be obtained from: - the temporary stored protected zone centre position (clause 5.2.2.... |
8630ac290c809951d9437f3a1bae6863 | 102 816 | 1 Scope | The present document defines the extension to the MHP specification supporting the recording of digital television content. It includes the scheduling of recordings, the management of scheduled recordings, the playback of completed recordings and the management of completed recordings. It includes the recording and pla... |
8630ac290c809951d9437f3a1bae6863 | 102 816 | 2 References | The following documents contain provisions which, through reference in this text, constitute 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. • ... |
8630ac290c809951d9437f3a1bae6863 | 102 816 | 3 Definitions and abbreviations | |
8630ac290c809951d9437f3a1bae6863 | 102 816 | 3.1 Definitions | For the purposes of the present document, the terms and definitions given in TS 102 817 [6] and the following apply: complete piece of content: content between two DVB-SI event boundaries content recording and access policy: policy controlling the ability for MHP applications from one broadcaster to use content from a ... |
8630ac290c809951d9437f3a1bae6863 | 102 816 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: AIT Application Information Table NOTE: As defined in clause 10.4 of ES 201 812 [1] and TS 102 812 [2]. API Application Program Interface NOTE: Sometimes also referred to as Application Programming Interface. BNF Backus-Naur Form CRID Content ... |
8630ac290c809951d9437f3a1bae6863 | 102 816 | 4 Conventions | Where modifications to other documents are defined by quoting text from those other documents and describing how the present document considers that text to be changed, text that the present document adds into the original document is shown underlined and text that the present document removes from the original documen... |
8630ac290c809951d9437f3a1bae6863 | 102 816 | 5 Basic Architecture | |
8630ac290c809951d9437f3a1bae6863 | 102 816 | 5.1 Relationship with MHP and GEM Specifications | Implementations of the present document shall additionally implement all mandatory requirements of either ES 201 812 [1] or TS 102 812 [2]. NOTE: Future versions of the present document may remove ES 201 812 [1] from the above and require implementation of all mandatory requirements of TS 102 812 [2]. All normative cla... |
8630ac290c809951d9437f3a1bae6863 | 102 816 | 5.2 Overview (informative) | Figure 1 shows an overview of the architecture assumed by the present document. A number of aspects are omitted for the sake of clarity. ETSI ETSI TS 102 816 V1.1.1 (2007-09) 10 list of recordings TV Anytime Content Referencing API Recording Management API Playback API MHP PVR application TVAnytime content referencing ... |
8630ac290c809951d9437f3a1bae6863 | 102 816 | 5.3 General requirements | The following requirements of ES 201 812 [1] shall also apply to the packages defined in the present document: • Clause 11.2.7 "Event model in DAVIC and DVB APIs". • Clause 11.2.5 "Event listeners". • Applications shall not define classes or interfaces in any package namespace defined in the present document. MHP termi... |
8630ac290c809951d9437f3a1bae6863 | 102 816 | 6 Recording and playback process | |
8630ac290c809951d9437f3a1bae6863 | 102 816 | 6.1 Managing scheduled recording | In addition to the activities defined in clause 6.1 of TS 102 817 [6], the process for managing scheduled recordings shall include the activities: 1) cross referencing the set of pending recordings with scheduling information to identify changes in the schedule and to schedule recordings not previously scheduled which ... |
8630ac290c809951d9437f3a1bae6863 | 102 816 | 6.2 The recording process | In addition to the activities defined in clause 6.2 of TS 102 817 [6], the recording process shall include the following activities: 1) Performing accurate recording using the mechanisms defined in clause 11 of TS 102 323 [4]. 2) Acquiring the broadcaster permissions for the pieces of content in the recording as define... |
8630ac290c809951d9437f3a1bae6863 | 102 816 | 9.1.2 Determining broadcaster permissions | . If evaluating the broadcaster permissions according to clause |
8630ac290c809951d9437f3a1bae6863 | 102 816 | 10.1.1 Common Core | determines that permission for recording is to be denied (see "Make a scheduled record request"), the recording shall not be started and the recording request shall transition to the FAILED_STATE. 3) Associating with the recording the DVB-SI descriptive metadata (title, synopsis & extended event descriptor) for the pie... |
8630ac290c809951d9437f3a1bae6863 | 102 816 | 6.2.1 Identifying streams to be recorded | In the present document, the term "recordable streams" used in TS 102 817 [6] shall be interpreted to mean those streams defined in clause 7.2 of ES 201 812 [1] and TS 102 812 [2]. Identifying the streams to be recorded shall be done as follows: • for each type of recordable stream, if the number of streams of each typ... |
8630ac290c809951d9437f3a1bae6863 | 102 816 | 6.2.2 Identifying and recording MHP applications | Identifying recordable MHP applications shall be done as follows: • If an application does not rely on dynamic data and does not rely on synchronization with audio/video and if this application is signalled as to be recorded (the scheduled_recording_flag in the application recording descriptor is set to '1'), then the ... |
8630ac290c809951d9437f3a1bae6863 | 102 816 | 6.3 Managing completed recordings | In addition to the activities defined in clause 6.3 of TS 102 817 [6], the process for managing completed recordings shall include the following activities: 1) Deleting the recording at some point once the expiration period is past. There is no requirement for this to be accurately enforced, either by deleting the reco... |
8630ac290c809951d9437f3a1bae6863 | 102 816 | 6.4 Playback | The process for playback shall be as defined in clause 6.4 of TS 102 817 [6]. During the playback of content recorded as the result of a scheduled recording, the following behaviour shall be supported. Table 1: Events during normal playback and resulting behaviour Event Behaviour Result on screen Java Event Fast forwar... |
8630ac290c809951d9437f3a1bae6863 | 102 816 | 6.5 Timeshift | The process for timeshift recording and playback shall be as defined in clause 6.5 of TS 102 817 [6] with the following clarification: 1) All streams within the service shall be recorded including those carrying dynamic data such as MHP application signalling, DSMCC object carousel(s), stream events and MPEG-2 private ... |
8630ac290c809951d9437f3a1bae6863 | 102 816 | 6.6 TV-Anytime | In a TV-Anytime environment, the following additional activities are required as part of the "managing scheduled recording" process defined in clause 6.1 Managing scheduled recording above: 1) resolving requests to record group CRIDs into their constituent elements. 2) monitoring when an additional resolution informati... |
8630ac290c809951d9437f3a1bae6863 | 102 816 | 7 Metadata | |
8630ac290c809951d9437f3a1bae6863 | 102 816 | 7.1 TV-Anytime | NOTE: The present document does not define functional profiles or levels of the TV-Anytime specifications. One place where such activity is happening in the DTG TV-Anytime Test Bed project, see Bibliography. |
8630ac290c809951d9437f3a1bae6863 | 102 816 | 7.1.1 Definition | The metadata defined by clause 8 of TS 102 323 [4] shall be supported. |
8630ac290c809951d9437f3a1bae6863 | 102 816 | 7.1.2 Transport by broadcast channel | Metadata transport as defined by clause 9 of TS 102 323 [4] shall be supported. TV-Anytime metadata fragments obtained from a DVBDatabase shall include fragmentVersion and fragmentId attributes values which are obtained from the corresponding fields of the encapsulation structure defined in TS 102 822-3-2 [3]. Any exis... |
8630ac290c809951d9437f3a1bae6863 | 102 816 | 7.1.3 Transport by interaction channel | Metadata transport as defined by of TS 102 822-6 [3] shall be supported. |
8630ac290c809951d9437f3a1bae6863 | 102 816 | 8 Application model | |
8630ac290c809951d9437f3a1bae6863 | 102 816 | 8.1 Playback of recorded applications | Clause 9 of TS 102 817 [6] shall be supported and additionally constrained as follows: • When playback leaves trick-mode and returns to normal, MHP-PVR terminals may delay re-starting applications for up to one minute. The behaviour for this minute is implementation dependent. |
8630ac290c809951d9437f3a1bae6863 | 102 816 | 8.2 Service contexts and support for virtual channels | MHP-PVR terminals shall be able support at least the following service contexts simultaneously: a) the service context created by the MHP terminal implementation that in MHP 1.0 is used by the navigator to present broadcast services; b) a service context created by MHP-PVR applications which could be used for the prese... |
8630ac290c809951d9437f3a1bae6863 | 102 816 | 8.3 Resource Management | The existing language in ES 201 812 [1] or TS 102 812 [2] clause 11.2.9 "Intra application media resource management" shall be extended to address the situation where an explicit request for media decoding resources by an application conflicts with existing resource usage associated with the service context in which th... |
8630ac290c809951d9437f3a1bae6863 | 102 816 | 8.4 Modifications to MHP 1.0 application model specification | When the present document is used in devices supporting ES 201 812 [1], the following changes shall be assumed to the text found in that document: a) In clause 9.1.6, the following text: "only a single application with a given Application identification is allowed to run at any time" shall be assumed to be changed as f... |
8630ac290c809951d9437f3a1bae6863 | 102 816 | 9 Application signalling | |
8630ac290c809951d9437f3a1bae6863 | 102 816 | 9.1 Recording specific security attributes | |
8630ac290c809951d9437f3a1bae6863 | 102 816 | 9.1.1 Signalling | The following descriptor is defined in order to enable one broadcaster or operator to signal the rights which they wish to grant (or exclude) to MHP applications from other organizations. This descriptor is defined for use in the SDT and the EIT. When used in the SDT, the scope of this descriptor is that service. When ... |
8630ac290c809951d9437f3a1bae6863 | 102 816 | 9.2 Signalling for application recording | |
8630ac290c809951d9437f3a1bae6863 | 102 816 | 9.2.1 Application recording descriptor | The application signalling defined in clause 8 of TS 102 817 [6] and the application recording descriptor defined in annex A of TS 102 817 [6] shall be supported. For the av_synced_flag, trigger events are as defined in clause B.2.4 of ES 201 812 [1] and TS 102 812 [2]. |
8630ac290c809951d9437f3a1bae6863 | 102 816 | 9.3 Extensions to application signalling | The present document extends the application control codes defined in clauses 10.6.2.1 and 10.6.2.2 of ES 201 812 [1] and TS 102 812 [2] as follows: Table 4: Extensions to application control codes Code Identifier Semantics 0x07 PLAYBACK_AUTOSTART Application shall not be run either direct from broadcast or when in tim... |
8630ac290c809951d9437f3a1bae6863 | 102 816 | 9.4 Modifications to MHP 1.0 application signalling specification | When the present document is used in devices supporting ES 201 812 [1], the following changes shall be assumed to the text found in that document: a) In clause 10.5.2, the following text: "Only a single instance of an application with a particular application identifier is allowed to execute at any time. So, if an appl... |
8630ac290c809951d9437f3a1bae6863 | 102 816 | 10 DVB-J platform | |
8630ac290c809951d9437f3a1bae6863 | 102 816 | 10.1 PDR | 10.1.1 Common Core Clause 7 of TS 102 817 [6] shall be supported. The behaviour of methods depending on recording request specific security attributes is defined as follows: 1) Where the application calling the method is from the same organization as the broadcaster of the content addressed by the recording request (as... |
8630ac290c809951d9437f3a1bae6863 | 102 816 | 10.1.2 DVB Extensions | The org.dvb.pvr and org.dvb.pvr.navigation packages shall be supported. All instances of org.ocap.shared.dvr.RecordedService created by the MHP-PVR terminal shall be instances of org.dvb.pvr.DVBRecordedService. All instances of org.ocap.shared.dvr.LeafRecordingRequest created by the MHP-PVR terminal shall be instances ... |
8630ac290c809951d9437f3a1bae6863 | 102 816 | 10.1.3 Related Content | The org.dvb.media.rct package shall be supported. This shall map onto the promotional links mechanism that is defined in clause 10 of TS 102 323 [4]. |
8630ac290c809951d9437f3a1bae6863 | 102 816 | 10.2 TV-Anytime | |
8630ac290c809951d9437f3a1bae6863 | 102 816 | 10.2.1 Content referencing | The org.dvb.tvanytime.resolution and org.dvb.locator,content packages shall be supported. When the method org.dvb.tvanytime.resolution.ResolutionResponse.getChildren returns a vector of ContentLocation objects, references to DVB locators in the resolution result shall be represented by instances of org.dvb.pvr.DVBConte... |
8630ac290c809951d9437f3a1bae6863 | 102 816 | 10.2.2 Metadata | This org.dvb.tvanytime.metadata and org.dvb.xml.jdom packages shall be supported. The classification schemes defined in annex A of TS 102 822-3-1 (V1.2.1) [3]shall be supported by the platform with the exception of the ActionTypeCS. These resident classification schemes can be referenced using the aliases listed in tab... |
8630ac290c809951d9437f3a1bae6863 | 102 816 | 10.3 Integration between PDR and TV-Anytime | |
8630ac290c809951d9437f3a1bae6863 | 102 816 | 10.3.1 TV-Anytime based recording | The org.dvb.tvanytime.pvr and org.dvb.tvanytime.pvr.navigation packages shall be supported. All instances of org.ocap.shared.pvr.RecordingManager shall be instances of org.dvb.tvanytime.pvr.navigation.CRIDRecordingManager. |
8630ac290c809951d9437f3a1bae6863 | 102 816 | 10.3.2 Content Identification API | The org.dvb.si.tva package shall be supported including both the Explicit and Indirect CRID signalling modes defined in clause 12 of TS 102 323 [4]. |
8630ac290c809951d9437f3a1bae6863 | 102 816 | 10.4 Version properties | The properties listed in the following table shall be included in the property set of the java.lang.System class. Thus these properties can be retrieved using java.lang.System.getProperty(). Since this API returns a string, numeric return values shall be encoded as defined by java.lang.Integer.toString(int). ETSI ETSI ... |
8630ac290c809951d9437f3a1bae6863 | 102 816 | 14.1 System constants | . |
8630ac290c809951d9437f3a1bae6863 | 102 816 | 10.5 Extended semantics for MHP DVB-J Platform | The present document defines the following extended behaviours for the APIs defined in ES 201 812 [1] and TS 102 812 [2]. |
8630ac290c809951d9437f3a1bae6863 | 102 816 | 10.5.1 User Settings and Preferences API | The user settings and preferences API defined in clause 11.9.2 of ES 201 812 [1] and TS 102 812 [2] shall be extended as follows: • An additional standardized preference shall be defined - "Recording List Access". • The encoding of this shall be as follows – String whose value is "true" if the end-user allows access to... |
8630ac290c809951d9437f3a1bae6863 | 102 816 | 10.5.2 DVB Service Information API | The DVB service information API defined in clause 11.6.1 of ES 201 812 [1] and TS 102 812 [2] shall be extended as follows: • Classes implementing org.dvb.si.SIEvent shall also implement org.dvb.si.tva.ContentIdentifierQuery as defined in the present document. • If an MHP application running as part of the playback of ... |
8630ac290c809951d9437f3a1bae6863 | 102 816 | 10.5.3 Application discovery and launching APIs | The Application discovery and launching APIs defined in clause 11.7.2 of ES 201 812 [1] and TS 102 812 [2] shall be extended as follows: • The class description of org.dvb.application.AppsDatabase shall be considered to be extended as follows: Applications whose control code is PLAYBACK_AUTOSTART (as defined in clause ... |
8630ac290c809951d9437f3a1bae6863 | 102 816 | 10.6 Modifications to MHP 1.0 DVB-J Platform | When the present document is used in devices supporting ES 201 812 [1] the following changes shall be assumed to the text found in that document: a) Additional fields and methods shall be added to the org.dvb.io.ixc.IxcRegistry class as follows: /** * Definition of the scope for bind or rebind - exported object is only... |
8630ac290c809951d9437f3a1bae6863 | 102 816 | 11 Security | |
8630ac290c809951d9437f3a1bae6863 | 102 816 | 11.1 Permission Request File Extensions | Clause 10 of TS 102 817 [6] shall be supported. MHP-PVR terminals implementing TS 102 812 [2] shall support a new DTD for the permission request file as follows: • The public identifier (referred to in TS 102 812 [2] as "PublicLiteral") to be used for specifying this DTD in document type declarations of the XML files i... |
8630ac290c809951d9437f3a1bae6863 | 102 816 | 12 System integration | |
8630ac290c809951d9437f3a1bae6863 | 102 816 | 12.1 TV-Anytime content referencing | NOTE: The present document does not define functional profiles or levels of the TV-Anytime specifications. One place where such activity is happening in the DTG TV-Anytime Test Bed project, see Bibliography. ETSI ETSI TS 102 816 V1.1.1 (2007-09) 27 |
8630ac290c809951d9437f3a1bae6863 | 102 816 | 12.1.1 Broadcast channel usage | Clauses 5, 6 and 7 of TS 102 323 [4] shall be supported. |
8630ac290c809951d9437f3a1bae6863 | 102 816 | 12.1.2 Resolution by interaction channel | For resolution of content references using an interaction channel, clause 12.3 "Location Resolution Over Bi-directional Networks" of TS 102 822-6 [3] shall be supported. |
8630ac290c809951d9437f3a1bae6863 | 102 816 | 13 Detailed platform profile definitions | Table 8: Detailed platform profile definitions Area Specification Enhanced Broadcast Profile Interactive Broadcast Profile and Internet Access Profile 6.1 Managing scheduled recording M M 6.2 The recording process M M 6.3 Managing completed recordings M M 6.4 Playback M M 6.5 Timeshift M M Recording and playback proces... |
8630ac290c809951d9437f3a1bae6863 | 102 816 | 14 Registry of constants | 14.1 System constants The following table defines the values for the system properties identifying the version of the present document supported by an implementation. Field Value Major 1 Minor 0 Micro 2 |
8630ac290c809951d9437f3a1bae6863 | 102 816 | 15 Minimum Platform Capabilities | Clause 11 of TS 102 817 [6] shall be supported. Additionally MHP-PVR terminals shall support: • For scheduled recording, the simultaneous recording of at least one video elementary stream, at least two audio elementary streams and at least two subtitle streams. • The monitoring for changes in metadata accessed through ... |
e8626f8fba9be95e658d8b3a912cd03a | 102 825-1 | 1 Scope | The present document specifies the Abbreviations, Definitions and Terms used for the Digital Video Broadcasting (DVB) Content Protection and Copy Management (CPCM) system. |
e8626f8fba9be95e658d8b3a912cd03a | 102 825-1 | 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... |
e8626f8fba9be95e658d8b3a912cd03a | 102 825-1 | 2.1 Normative references | The following referenced documents are necessary for the application of the present document. Not applicable. |
e8626f8fba9be95e658d8b3a912cd03a | 102 825-1 | 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... |
e8626f8fba9be95e658d8b3a912cd03a | 102 825-1 | 3 Definitions and abbreviations | |
e8626f8fba9be95e658d8b3a912cd03a | 102 825-1 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply: acquire: receive and ingest content from outside the CPCM System into the CPCM System Acquisition Point (AP): abstract CPCM Functional Entity where content Acquisition takes place acquisition: receipt and ingestion of content that was ... |
e8626f8fba9be95e658d8b3a912cd03a | 102 825-1 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: AAA Authorized Authenticated Agent AD Authorized Domain ADID AD Identifier ADID AD Identifier ADM Authorized Domain Management. ADMAAA AD Membership Assignment by Authorized Authenticated Agent ADS AD Secret ADSE Authorized Domain Size and Ext... |
e8626f8fba9be95e658d8b3a912cd03a | 102 825-1 | 4 Understanding the state charts | The notation used within CPCM State Charts is illustrated in figure 1. State Processing Decision Outgoing signal Incoming signal Flow of Control Signal Figure 1: Legend for State Charts ETSI ETSI TS 102 825-1 V1.2.1 (2011-03) 12 |
e8626f8fba9be95e658d8b3a912cd03a | 102 825-1 | 5 CPCM Content flows | Table 1 contain additional definitions surrounding the various types of CPCM Content flows. Table 1: CPCM Content flow definitions Ref. Content Flow Name Definition Composition/Notes C.0 CPCM Content Content protected and managed by the CPCM System Acquired Content | Stored Content | Retrieved Content | Processed Conte... |
9513ad827c8fd5eb84cd8a245fa99b13 | 102 812 | 0 Introduction | . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 |
9513ad827c8fd5eb84cd8a245fa99b13 | 102 812 | 0.1 Purpose | . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 |
9513ad827c8fd5eb84cd8a245fa99b13 | 102 812 | 0.2 Application areas | . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 |
9513ad827c8fd5eb84cd8a245fa99b13 | 102 812 | 0.3 Profiles | . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 |
9513ad827c8fd5eb84cd8a245fa99b13 | 102 812 | 0.4 Aim | . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 |
9513ad827c8fd5eb84cd8a245fa99b13 | 102 812 | 1 Scope | . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.