id
stringlengths 7
13
| title
stringlengths 7
396
| type
stringclasses 2
values | version
stringclasses 245
values | url
stringlengths 90
98
| scope
stringlengths 0
83.8k
|
|---|---|---|---|---|---|
102 826
|
Digital Video Broadcasting (DVB); DVB-IPTV Profiles for TS 102 034
|
TS
|
1.2.1
|
http://www.etsi.org/deliver/etsi_ts/102800_102899/102826/01.02.01_60/ts_102826v010201p.pdf
|
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 the DVB-IPTV handbook is not necessarily required for the deployment of specific IPTV systems. It is however currently not possible to implement a subset of the building blocks and claim compliancy to the DVB-IPTV handbook. Therefore, the present document defines a small set of service oriented profiles in order to facilitate and maximize the stepwise deployment of IPTV services. A profile is a coherent subset of the DVB-IPTV handbook, allowing companies to claim a degree of DVB compliancy for IPTV services. Details about specific technologies referenced in the present document are described in the DVB IPTV handbook [1].
|
102 841
|
Digital Enhanced Cordless Telecommunications (DECT); New Generation DECT; Extended wideband speech services; Profile Test Specification (PTS) and Test Case Library (TCL)
|
TS
|
1.5.1
|
http://www.etsi.org/deliver/etsi_ts/102800_102899/102841/01.05.01_60/ts_102841v010501p.pdf
|
The present document contains the Profile Test Specification (PTS) and the Test Case Library (TCL) for "New Generation DECT; Part 3: Extended wideband speech" (TS 102 527-3 [14]). The present document covers both the Portable (PT) and the Fixed (FT) Radio terminations. The Test Case Library (TCL) covers also some test cases for "DECT New Generation; Part 1: Wideband speech" (TS 102 527-1 [13]) and for the "Generic Access Profile" (EN 300 444 [12]). This is done because such test cases are mandatory or especially relevant for New Generation DECT part 3 (see TS 102 527-3 [14]), and are not covered by existing GAP test specifications. Due to the ascending compatibility of DECT profiles, all New Generation DECT part 3 devices (see TS 102 527-3 [14]) are required to be also compliant with "DECT New Generation; Part 1: Wideband speech" (TS 102 527-1 [13]) and with the "Generic Access Profile" (GAP, EN 300 444 [12]). Annex D of the present document specifies the modifications to GAP test cases for requirements and tests that are optional in GAP test specifications (see note), but that become mandatory by the support of the corresponding GAP features in New Generation DECT Part 3. NOTE: The industry de-facto standard practice for insuring the compliance to GAP [12] is the use of TBR 022 [i.4] amended by TBR 022/A1 [i.5], even when these two documents do not have any longer their initial regulatory signification. TBR 022 [i.4] relies on the GAP Profile Test Specification (EN 300 494 parts 1 [i.6] to 3 [i.8]) and on the DECT Test Case Library (EN 300 497 parts 1 [i.9] to 9 [i.17]). GAP test suite includes also the GAP Profile Implementation Conformance Statement (PICS) (EN 300 474 parts 1 [i.25] and 2 [i.26]) and the DECT Common Interface (CI) Profile Implementation Conformance Statement (PICS) (EN 300 476 parts 1 [i.18] to 7 [i.24]). The objective of the present document is to provide a basis for approval tests of NG-DECT Part 3 equipment giving a high probability of air interface inter-operability between different manufacturer's DECT equipment.
|
102 874-6
|
Access, Terminals, Transmission and Multiplexing (ATTM); External Common Power Supply for Customer Premises Network and Access Equipment; Part 6: CPS Type 2.d implementation details
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/102800_102899/10287406/01.01.01_60/ts_10287406v010101p.pdf
|
The present document describes the specification for a high performance External Power Supply Unit for powering the Customer Premises Equipment to a maximum voltage rating of 12 V dc. The specifications define the input, output characteristics and performance requirements for a switching mode AC to DC CPS rated to a maximum 12 V dc, and maximum 3,2 A. The present document also specifies tests to verify the compliance of the external CPS. Disclaimer: The present document does not guarantee compliance to legal directives or regulations. Details about these aspects can be found on the following links: • http://ec.europa.eu/enterprise/sectors/electrical/index_en.htm • http://ec.europa.eu/enterprise/sectors/electrical/documents/lvd/standardisation/index_en.htm • http://ec.europa.eu/enterprise/sectors/electrical/documents/emc/standardisation/index_en.htm NOTE: Examples of documents to be considered are CE Marking 93/68/EEC [13], LVD Low Voltage Directive 2006/95/EC [12], EMC Directive 2004/108/EC [14]; for Ecodesign aspects: RoHS (Restriction of Hazardous Substances) European Directive 2011/65/EC [8] 8th June 2011 and WEEE Management Regulations (Waste Electrical and Electronic Equipment) European Directives 2002/96/EC [9] 27th January 2003 and amendments.
|
102 825-1
|
Digital Video Broadcasting (DVB); Content Protection and Copy Management (DVB-CPCM); Part 1: CPCM Abbreviations, Definitions and Terms
|
TS
|
1.2.1
|
http://www.etsi.org/deliver/etsi_ts/102800_102899/10282501/01.02.01_60/ts_10282501v010201p.pdf
|
The present document specifies the Abbreviations, Definitions and Terms used for the Digital Video Broadcasting (DVB) Content Protection and Copy Management (CPCM) system.
|
102 824
|
Digital Video Broadcasting (DVB); Remote Management and Firmware Update System for DVB IPTV Services (Phase 2)
|
TS
|
2.1.1
|
http://www.etsi.org/deliver/etsi_ts/102800_102899/102824/02.01.01_60/ts_102824v020101p.pdf
|
The present document contains the specification for the remote management and firmware update system for DVB IPTV services and forms an addendum to the DVB IPTV Handbook ETSI TS 102 034 [1]. All aspects of the RMS and FUS functionality which are standardized by DVB are described within this single common document, but since the RMS and associated FUS service is specified to be directly associated with the DVB IPTV Handbook ETSI TS 102 034 [1] some direct references to parts of that specification are included. The association with [1] does not prevent the present document partially or completely being used in conjunction with other IPTV delivery services. Remote Management is the ability of a server entity outside the home environment to monitor and configure the devices within the home and covers provisioning and assurance tasks. It optionally includes firmware updates to the equipment. The remote management entity is referred to as the Remote Management System (RMS) and the firmware update capability as the Firmware Update System (FUS). This updated version of the document also now includes: • Addition of specific RMS-FUS payloadID for DVBSTP announcement messages (0xB2). • The definition of the data model extension objects to support the DVB Content Delivery System specific functionality, intended to be used in conjunction with the data models for IPTV CPEs defined by other organization, e.g. Broadband Forum, Cablelabs. • An annex defining the way in which the DVB specific data model objects may work within the Broadband Forum data model. Similar modelling could be for data models from other standards organizations but that has not been done in the present document. • DVB RMS-FUS profiling of the authentication method specified for the SAP multicast protocol for carrying the firmware update announcement messages. • An extension to the metadata which may support usage of multiple file objects in a single carousel (FLUTE or DSM-CC), and multiple DSM-CC data components within a service for firmware update delivery. • Profiling of the dvb-mcast URI specific to each delivery protocol, allowing support for usage of multiple file objects in a single delivery carousel (FLUTE or DSM-CC), multiple DSM-CC data components within a service for firmware update delivery and multiple channels for FLUTE. The present document is intended to provide additional functionality that may be used in conjunction with existing RMS specifications standardized by other bodies and primarily focuses on defining a multicast firmware update capability. A description of the additional functionality for an RMS interface based on the Broadband Forum TR-069 framework is presented in annex A. The targeting of the firmware updates may include all the devices in the home environment if the CE manufacturer supplies updates. It should be noted that the method presented in the present document does not preclude delivery to home network devices which would potentially be "hidden" behind a gateway device in future phases. The term "CPE" has been adopted in the present document in preference to the more well-known DVB-IPI terms "HNED" (Home Network End Device) and "DNG" (Delivery Network Gateway) in order to take other DVB devices such as the home network devices currently being specified by DVB-IPI HN task force into account. Both DNG and HNED are included in the scope of CPE in this context. The logical architecture required to realise the RMS and FUS environments is described in the present document. The RMS and FUS may be provided by the same or different agencies, and may be co-located. The entities identified as building blocks of RMS and FUS are logical entities rather than physical devices, and a single manufacturer could integrate multiple logical entities into a single physical device. The RMS and the FUS service may be provided by the service provider, network operator or a third party on an agreed contract basis. ETSI ETSI TS 102 824 V2.1.1 (2016-04) 9 Note that there may be several CE manufacturers contributing firmware files, and several FUSs, which may be managed by one or more RMSs (but with only one active management service at a time for any single CPE) delivered through multiple networks to the various populations of CPEs. However, some rules on prioritization in terms of CPE management are defined within the present document. The options for delivery of the update files over the IPTV delivery network to the CPEs are specified in the present document in the following clauses. Security is an important aspect of all communications in an IP environment and the requirements for and methods of securely either exchanging messaging or sending firmware update payloads are described in each clause of the present document where it is possible and in a way appropriate to the part of the specification. These are referenced to a central clause describing the principles used within the present document. However, it is not intended for carrying the most secure downloads, such as those where DRM related or contractual conditions apply. Packaging and authentication of firmware updates delivered over multicast DVBSTP is not specified in the present document, it is assumed that those functions will be defined at a manufacturer-specific level.
|
102 823
|
Digital Video Broadcasting (DVB); Specification for the carriage of synchronized auxiliary data in DVB transport streams
|
TS
|
1.3.1
|
http://www.etsi.org/deliver/etsi_ts/102800_102899/102823/01.03.01_60/ts_102823v010301p.pdf
|
The present document describes a method by which auxiliary data, which needs to be synchronized with linear components of a service, such as video and audio streams, may be carried in a DVB transport stream.
|
102 822-9
|
Broadcast and On-line Services: Search, select, and rightful use of content on personal storage systems ("TV-Anytime"); Part 9: Phase 2 - Remote Programming
|
TS
|
1.6.1
|
http://www.etsi.org/deliver/etsi_ts/102800_102899/10282209/01.06.01_60/ts_10282209v010601p.pdf
|
The present document is one in a series of Technical Specification documents produced by the TV-Anytime Forum. These documents establish the fundamental specifications for the services, systems and devices that will conform to the TV-Anytime standard, to a level of detail that is implementable for compliant products and services. TS 102 822-1 [1] and TS 102 822-2 [2] set the context and system architecture in which the standards for Metadata, Content referencing, Bi-directional metadata and Metadata protection are to be implemented in the TV-Anytime environment. TS 102 822-1 [1] provides benchmark business models against which the TV-Anytime system architecture is evaluated to ensure that the specification enables key business applications. TS 102 822-2 [2] presents the TV-Anytime System Architecture and the relationship between Phase 1 and Phase 2 technologies. These first two documents are largely informative, while the remainder of the series is normative. The present document has been developed during the second phase of TV-Anytime and covers the definition of the interchange data format for the delivery of TV-Anytime metadata and content referencing information from different data sources. The TV-Anytime Forum has defined a number of data types that can be exchanged between TV-Anytime devices. These include program metadata, content referencing information, and user-centric metadata. There is an interest to remotely control a PDR from other devices and locations such as a personal computer in the office or a PDA on the move. The present document defines how a mailing service may be used to remotely control a home PDR from outside. There is also an interest to make use of an NDR (Network Digital Recorder) when the home PDR is not in a position to record content the end-user wants to obtain. The present document defines how to declare an NDR service, how to discover it and how to make use of it to record content to be delivered to the end-user.
|
102 822-8
|
Broadcast and On-line Services: Search, select, and rightful use of content on personal storage systems ("TV-Anytime"); Part 8: Phase 2 - Interchange Data Format
|
TS
|
1.6.1
|
http://www.etsi.org/deliver/etsi_ts/102800_102899/10282208/01.06.01_60/ts_10282208v010601p.pdf
|
The present document is one in a series of Technical Specification documents produced by the TV-Anytime Forum. These documents establish the fundamental specifications for the services, systems and devices that will conform to the TV-Anytime standard, to a level of detail that is implementable for compliant products and services. TS 102 822-1 [1] and TS 102 822-2 [2] set the context and system architecture in which the standards for Metadata, Content referencing, Bi-directional metadata and metadata protection are to be implemented in the TV-Anytime environment. TS 102 822-1 [1] provides benchmark business models against which the TV-Anytime system architecture is evaluated to ensure that the specification enable key business applications. TS 102 822-2 [2] presents the TV-Anytime System Architecture and the relationship between Phase 1 and Phase 2 technologies. These first two documents are largely informative, while the remainder of the series is normative. The present document has been developed during the second phase of TV-Anytime and covers the definition of the interchange data format for the delivery of TV-Anytime metadata and content referencing information from different data sources. The interchange data format described in the present document was selected in order to satisfy the usage scenarios listed in TS 102 822-1 [1]. The TV-Anytime Forum has defined a number of data types that can be exchanged between TV-Anytime devices. These include program metadata, content referencing information, and user-centric metadata. The present document addresses data delivery from non TV-Anytime sources to TV-Anytime clients. A TV-Anytime client is typically a PDR, although in the present document the client can be any Internet connected device. These devices do not necessarily need to have the ability to display or store content, since many types of devices can exploit TV-Anytime metadata services (e.g. a mobile phone displaying an EPG). Programme metadata and content referencing information can be delivered unidirectionally (e.g. via traditional broadcast or IP multicast) or via a bi-directional network. A TV-Anytime data provider might choose to deliver data using the interchange data format described because it allows: • a simple adaptation of existing non-TV Anytime content selection and location services to provide data for TV-Anytime clients; • the delivery of the TV-Anytime data to clients by TV-Anytime data providers without access to a broadcast system; • TV-Anytime data providers to personalize the metadata they offer according to the source of the request; • a range of client devices, which are not necessarily able to receive broadcast data, to access and exploit TV-Anytime data. For example, a mobile phone or personal organizer could use the metadata service to show the user an EPG. Figure 1 shows the relation between non-TV-Anytime content selection and location services and TV-Anytime clients. ETSI ETSI TS 102 822-8 V1.6.1 (2012-12) 7 E-mail Web server TVA world TVA data EPG Web browsing Web browser encapsulation decapsulation SP008 Publish Search Locate View Acquire Finish Figure 1: TV-Anytime data delivery from alternate data sources
|
102 822-7
|
Broadcast and On-line Services: Search, select, and rightful use of content on personal storage systems ("TV-Anytime Phase 1"); Part 7: Bi-directional metadata delivery protection
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/102800_102899/10282207/01.01.01_60/ts_10282207v010101p.pdf
|
The present document is the seventh document of a series of "S-documents" produced by the TV-Anytime Forum. These documents establish the fundamental specifications for the services, systems and devices that will conform to the TV-Anytime standard, to a level of detail that is implementable for compliant products and services. As is common practice in such standardization efforts, these specification documents were preceded by requirements documents ("R-series"), which define the requirements for the TV-Anytime services, systems, and devices. Congruent with the structure defined in the initial TV-Anytime Call for Contributions (TV014r3), these specifications are parsed into three major areas: Metadata, Content Referencing and Rights Management and Protection. Within these general areas, four specifications have been developed to date: Metadata (S-3), Content Referencing (S-4), Bi- directional Metadata (S-6) and Metadata Protection (S-7). A specification for Rights Management and Protection (S-5) is still under development. See the several TV-Anytime Calls for Contributions for more detail on the derivation and background of these categories and their respective roles in the TV-Anytime standardization process. Two documents in the TV-Anytime S-series are intended to define the context and system architecture in which the standards in S-3, S-4, S-6 and S-7 are to be implemented in "Phase 1" of the TV-Anytime environment. The first document in the series (S-1) provides benchmark business models against which the TV-Anytime system architecture is evaluated to ensure that the specification enable key business applications. The next document in the series (S-2) presents the TV-Anytime System Architecture. These two documents are placed ahead of the other three for their obvious introductory value. (Note that S-1 and S-2 are largely informative documents, while the remainder of the S-series is normative. Also note that a "Phase 2" of the TV-Anytime process is currently underway, in which additional requirements and specifications that will build on Phase 1 are being developed. Readers are encouraged to check the TV-Anytime Forum's website at www.tv-anytime.org for the most recent status of its specifications.) Although each of the S-series documents is intended to stand alone, a complete and coherent sense of the TV-Anytime system standard can be gathered by reading all of the Phase 1 specification documents in numerical order. This scope of the present document, comprises the protection of metadata delivered via bi-directional networks. The requirements for this technology are outlined as follows: • Provide message integrity • Authenticate service provider (entity that delivers metadata) • Support bi-directional transport models • Optional encryption With the present document, TV-Anytime Forum mandates TLS as its baseline method of securing bi-directional delivery of metadata over point to point network connections. While the present document addresses metadata transport security during delivery, it does not address persistent protection of metadata within the consumer space. To ensure persistent protection of metadata additional means of protection have to be applied in conjunction with the present document. The basic aim of the present document is to provide means to enable the delivery of trusted metadata to end-users. However, end to end content protection is to be addressed in a separate specification (TS 102 822-5) as per the fundamental TV-Anytime RMP requirements: "TV-Anytime RMP-compliant systems, which aim to securely manage content from creation to final consumption shall accommodate the various needs of the different players in the value chain, specially enabling content owners and distributors to persistently protect their intellectual property and enforce content usage rules within the full content lifecycle." (RMP CFC section 3) ETSI ETSI TS 102 822-7 V1.1.1 (2003-10) 7
|
102 825-3
|
Digital Video Broadcasting (DVB); Content Protection and Copy Management (DVB-CPCM); Part 3: CPCM Usage State Information
|
TS
|
1.2.1
|
http://www.etsi.org/deliver/etsi_ts/102800_102899/10282503/01.02.01_60/ts_10282503v010201p.pdf
|
The present document specifies the Usage State Information (USI) for the Digital Video Broadcasting (DVB) Content Protection and Copy Management (CPCM) system. Additionally, the present document specifies USI-related Auxiliary Data that will be carried along with the USI by mechanisms to be specified further by CPCM. NOTE: USI has been designed to accommodate a variety of business models and regulatory regimes. The existence of any particular field of USI does not imply that it will be asserted by a particular business or that it will be allowed to be asserted.
|
102 825-2
|
Digital Video Broadcasting (DVB); Content Protection and Copy Management (DVB-CPCM); Part 2: CPCM Reference Model
|
TS
|
1.2.1
|
http://www.etsi.org/deliver/etsi_ts/102800_102899/10282502/01.02.01_60/ts_10282502v010201p.pdf
|
The present document specifies the Reference Model (Ref Mod) for the Digital Video Broadcasting (DVB) Content Protection and Copy Management (CPCM) system.
|
102 829
|
<empty>
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/102800_102899/102829/01.01.01_60/ts_102829v010101p.pdf
|
The present document describes an XML based Architecture Description Language (ADL), used to define the composition of software components in distributed and parallel infrastructures. The standard will help enterprises and laboratories to manage large-scale computer and telecom infrastructures with the necessary virtualization. Its primary audience are grid system developers who need to specify complex applications by composing existing software components.
|
102 824
|
Digital Video Broadcasting (DVB); Remote Management and Firmware Update System for DVB IPTV Services (Phase 2)
|
TS
|
1.2.1
|
http://www.etsi.org/deliver/etsi_ts/102800_102899/102824/01.02.01_60/ts_102824v010201p.pdf
|
The present document contains the specification for the remote management and firmware update system for DVB IPTV services and forms an addendum to the DVB IPTV Handbook ETSI TS 102 034 [1]. All aspects of the RMS and FUS functionality which are standardized by DVB are described within this single common document, but since the RMS and associated FUS service is specified to be directly associated with the DVB IPTV Handbook ETSI TS 102 034 [1] some direct references to parts of that specification are included. The association with [1] does not prevent the present document partially or completely being used in conjunction with other IPTV delivery services. Remote Management is the ability of a server entity outside the home environment to monitor and configure the devices within the home and covers provisioning and assurance tasks. It optionally includes firmware updates to the equipment. The remote management entity is referred to as the Remote Management System (RMS) and the firmware update capability as the Firmware Update System (FUS). This updated version of the document also now includes: • Addition of specific RMS-FUS payloadID for DVBSTP announcement messages (0xB2). • The definition of the data model extension objects to support the DVB Content Delivery System specific functionality, intended to be used in conjunction with the data models for IPTV CPEs defined by other organization, e.g. Broadband Forum, Cablelabs. • An annex defining the way in which the DVB specific data model objects may work within the Broadband Forum data model. Similar modelling could be for data models from other standards organizations but that has not been done in the present document. • DVB RMS-FUS profiling of the authentication method specified for the SAP multicast protocol for carrying the firmware update announcement messages. • An extension to the metadata which may support usage of multiple file objects in a single carousel (FLUTE or DSM-CC), and multiple DSM-CC data components within a service for firmware update delivery. • Profiling of the dvb-mcast URI specific to each delivery protocol, allowing support for usage of multiple file objects in a single delivery carousel (FLUTE or DSM-CC), multiple DSM-CC data components within a service for firmware update delivery and multiple channels for FLUTE. The present document is intended to provide additional functionality that may be used in conjunction with existing RMS specifications standardized by other bodies and primarily focuses on defining a multicast firmware update capability. A description of the additional functionality for an RMS interface based on the Broadband Forum TR-069 framework is presented in annex A. The targeting of the firmware updates may include all the devices in the home environment if the CE manufacturer supplies updates. It should be noted that the method presented in the present document does not preclude delivery to home network devices which would potentially be "hidden" behind a gateway device in future phases. The term "CPE" has been adopted in the present document in preference to the more well-known DVB-IPI terms "HNED" (Home Network End Device) and "DNG" (Delivery Network Gateway) in order to take other DVB devices such as the home network devices currently being specified by DVB-IPI HN task force into account. Both DNG and HNED are included in the scope of CPE in this context. The logical architecture required to realise the RMS and FUS environments is described in the present document. The RMS and FUS may be provided by the same or different agencies, and may be co-located. The entities identified as building blocks of RMS and FUS are logical entities rather than physical devices, and a single manufacturer could integrate multiple logical entities into a single physical device. The RMS and the FUS service may be provided by the service provider, network operator or a third party on an agreed contract basis. ETSI ETSI TS 102 824 V2.1.1 (2016-04) 9 Note that there may be several CE manufacturers contributing firmware files, and several FUSs, which may be managed by one or more RMSs (but with only one active management service at a time for any single CPE) delivered through multiple networks to the various populations of CPEs. However, some rules on prioritization in terms of CPE management are defined within the present document. The options for delivery of the update files over the IPTV delivery network to the CPEs are specified in the present document in the following clauses. Security is an important aspect of all communications in an IP environment and the requirements for and methods of securely either exchanging messaging or sending firmware update payloads are described in each clause of the present document where it is possible and in a way appropriate to the part of the specification. These are referenced to a central clause describing the principles used within the present document. However, it is not intended for carrying the most secure downloads, such as those where DRM related or contractual conditions apply. Packaging and authentication of firmware updates delivered over multicast DVBSTP is not specified in the present document, it is assumed that those functions will be defined at a manufacturer-specific level.
|
102 822-5
|
Broadcast and On-line Services: Search, select, and rightful use of content on personal storage systems ("TV-Anytime Phase 1"); Part 5: Rights Management and Protection (RMP) Information for Broadcast Applications
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/102800_102899/10282205/01.01.01_60/ts_10282205v010101p.pdf
|
RMPI for Broadcast Applications, made up of RMPI-Micro Broadcast and RMPI-Micro, is a component of the TV-Anytime Rights Management and Protection system suite of specifications. The present document provides the semantics, syntax and encoding for the usage rights, controls and permissions to be conveyed in RMPI-MB and RMPI-M.
|
102 822-4
|
Broadcast and On-line Services: Search, select, and rightful use of content on personal storage systems ("TV-Anytime"); Part 4: Phase 1 - Content referencing
|
TS
|
1.7.1
|
http://www.etsi.org/deliver/etsi_ts/102800_102899/10282204/01.07.01_60/ts_10282204v010701p.pdf
|
The present document is part 4 of multi-part deliverable "TS 102 822 series" documents produced by the TV-anytime Forum. These documents establish the fundamental specifications for the services, systems and devices that will conform to the TV-anytime standard, to a level of detail which is implementable for compliant products and services. Although each of the TS 102 822 series documents is intended to stand alone, a complete and coherent sense of the TV-anytime system standard can be gathered by reading all of the specification documents in numerical order. The scope of the present document is comprises of the location independent identification of content, the location information, and the process of finding the location when an identifier is given. The content referencing process begins after a content item has been selected by a consumer through to, but not including, the actual acquisition of the desired content item. The content referencing specification provides the mechanisms for location resolution in unidirectional network environments, as well as support for location resolution in a bi-directional environment as defined in TS 102 822-1 [8].
|
102 822-3-4
|
Broadcast and On-line Services: Search, select, and rightful use of content on personal storage systems ("TV-Anytime"); Part 3: Metadata; Sub-part 4: Phase 2 - Interstitial metadata
|
TS
|
1.6.1
|
http://www.etsi.org/deliver/etsi_ts/102800_102899/1028220304/01.06.01_60/ts_1028220304v010601p.pdf
|
The present document is one in a series of Technical Specification documents produced by the TV-Anytime Forum. These documents establish the fundamental specifications for the services, systems and devices that will conform to the TV-Anytime standard, to a level of detail that is implementable for compliant products and services. TS 102 822-1 [1] and TS 102 822-2 [2] set the context and system architecture in which the standards for Metadata, Content referencing, Bi-directional metadata and Metadata protection are to be implemented in the TV-Anytime environment. TS 102 822-1 [1] provides benchmark business models against which the TV-Anytime system architecture is evaluated to ensure that the specifications enable key business applications. TS 102 822-2 [2] presents the TV-Anytime System Architecture and the relationship between Phase 1 and Phase 2 technologies. These first two documents are largely informative, while the remainder of the series is normative. The Phase 2 TV-Anytime Metadata schema is a backwards-compatible extension of the Phase 1 schema. It extends Phase 1 datatypes for content description and user description and makes use of imported datatypes from MPEG-21 to enable new areas of functionality. It also extends the TV-Anytime root document type, TVAMainType, to enable publication of metadata described using the new datatypes. The present document has been developed during the second phase of TV-Anytime and deals with the metadata necessary to enable interstitial replacement, within a PDR device. The set of metadata described in the present document was selected in order to satisfy the usage scenarios listed in TS 102 822-1 [1]. The formal definitions of metadata schemas should be read in conjunction with the system specification (TS 102 822-2 [2]) defining how they could be used in an end-to-end system. TV-Anytime only defines the format for metadata that may be exchanged between various entities such as between content providers and consumers, among consumers, or between a third-party metadata provider and consumers. XML is the "representation format" used to define schemas in TV-Anytime specifications. Although XML Schema is used to define how metadata is represented in XML, it can also be used to describe equivalent, non-XML representations of the same metadata.
|
102 822-3-3
|
Broadcast and On-line Services: Search, select, and rightful use of content on personal storage systems ("TV-Anytime"); Part 3: Metadata; Sub-part 3: Phase 2 - Extended Metadata Schema
|
TS
|
1.6.1
|
http://www.etsi.org/deliver/etsi_ts/102800_102899/1028220303/01.06.01_60/ts_1028220303v010601p.pdf
|
The present document is part of TV-Anytime Phase 2 that proposes an evolutionary range of features which describe PDR (Personal Digital Recorder) usage models that the TV-Anytime standards facilitate. The TV-Anytime specifications enable search, select, acquire and rightful use of content on local and/or remote personal storage systems from both broadcast and online services. The features are supported and enabled by the specifications for Metadata (TS 102 822-3-1 [3], TS 102 822-3-2 [4], the present document and TS 102 822-3-4 [5]), Content Referencing (TS 102 822-4 [6]), Rights Management (TS 102 822-5-1 [7] and TS 102 822-5-2 [8]), Bi-directional Metadata Delivery (TS 102 822-6-1 [9], TS 102 822-6-2 [10] and TS 102 822-6-3 [11]) and Protection (TS 102 822-7 [12]), Interchange Data Format (TS 102 822-8 [13]) and Remote Programming (TS 102 822-9 [14]). The present document addresses more specifically the Phase 2 extended metadata features of the TV-Anytime specification as identified in TS 102 822-1 [1]. Metadata is generally defined as "data about data". Within the TV-Anytime environment, the most visible parts of metadata are the attractors/descriptors or hyperlinks used in Electronic Programme Guides, or in Web pages. This is the information that the consumer or agent will use to decide whether or not to acquire a particular piece of content. The TV-Anytime metadata system allows the consumer to find, navigate and manage content from a variety of internal and external sources including, for example, enhanced broadcast, interactive TV, Internet and local storage. It defines a standard way to describe device profiles, consumer preferences to facilitate automatic filtering and acquisition of content by agents on behalf of the consumer. Consumers, as used in the present document, include educators and students, who may use selected programme segments in the classroom or laboratory. There is a need to associate metadata with content to facilitate human and automated searching for content of interest. Such metadata includes descriptive elements and attractors to aid the search process as well as elements essential to the acquisition, capture and presentation processes; content rights, formats, duration, etc. Many of these descriptive elements can be found in EPGs and HTML documents. The process of creation and evolution of metadata for an individual content item may involve many organizations during the course of creation, distribution and delivery to the consumer. Thus, there is a clear need to define a common metadata framework and a standard set of metadata elements in order to ensure a high level of interoperability within the chain from content creation to content delivery. TV-Anytime Phase 2 extends the definition of TV-Anytime Phase 1 metadata to cover descriptive data about content, such as content title and synopsis, but also data about how the content should be consumed. Such metadata is called "attractors" because they can attract a consumer to content. Attractors allow consumers to find, navigate and manage content from various sources. New Phase 2 attractors include: • Content Packaging. • Targeting metadata. • Device Capabilities. • Interstitial Content. • New Content Type. The formal definitions of metadata schemas should be read in conjunction with the system specification defining how they could be used in an end-to-end system TV-Anytime only defines the metadata format for metadata that may be exchanged between various entities such as between the content provider and consumer, among consumers or between a third-party metadata provider and the consumer. XML [15] is the "representation format" used to define the schemas of the TV-Anytime Metadata Specification. Although XML Schema is used to define how metadata is represented in XML, it can also be used to describe equivalent, non-XML representations of the same metadata. ETSI ETSI TS 102 822-3-3 V1.6.1 (2012-12) 8
|
102 822-3-2
|
Broadcast and On-line Services: Search, select, and rightful use of content on personal storage systems ("TV-Anytime"); Part 3: Metadata; Sub-part 2: System aspects in a uni-directional environment
|
TS
|
1.6.1
|
http://www.etsi.org/deliver/etsi_ts/102800_102899/1028220302/01.06.01_60/ts_1028220302v010601p.pdf
|
The present document is one in a series of Technical Specification documents produced by the TV-Anytime Forum. These documents establish the fundamental specifications for the services, systems and devices that will conform to the TV-Anytime standard, to a level of detail that is implementable for compliant products and services. TS 102 822-1 [7] and TS 102 822-2 [8] set the context and system architecture in which the standards for Metadata, Content referencing, Bi-directional metadata and Metadata protection are to be implemented in the TV-Anytime environment. TS 102 822-1 [7] provides benchmark business models against which the TV-Anytime system architecture is evaluated to ensure that the specification enable key business applications. TS 102 822-2 [8] presents the TV-Anytime System Architecture. These first two documents are largely informative, while the remainder of the series is normative. Although each in the series of documents is intended to stand alone, a complete and coherent sense of the TV-Anytime system standard can be gathered by reading all the specification documents in numerical order. Figure 1 depicts the combined scope of the TV-Anytime Specifications on Metadata TS 102 822-3-1 [9], TS 102 822-3-3 [10], TS 102 822-3-4 [11], TS 102 822-8 [19], TS 102 822-9 [20] and the present document "System Aspects in a Unidirectional Environment". Metadata access interfaces for applications Description language for metadata types Metadata types and associated semantics Encoding and encapsulation of metadata for uni-directional delivery Requirements on delivery layer Format and semantics of delivery layer Scope of the TvA metadata standard Figure 1: Overview of the scope of TVA Specification on Metadata and System The metadata specifications TS 102 822-3-1 [9], TS 102 822-3-3[10], TS 102 822-3-4 [11], TS 102 822-8 [19] and TS 102 822-9 [20] address the description language, structure and semantics of TV-Anytime metadata descriptions. The present document introduces new network agnostic technologies used to process these descriptions for the purpose of transmission in a unidirectional environment. The actual format and semantics of the delivery layer are specific to the particular uni-directional environment in which TV-Anytime is deployed. However, in order for the encoding and encapsulation mechanisms to operate as intended the delivery layer must meet certain requirements. These normative requirements are defined in annex B of TS 102 822-2 [8]. ETSI ETSI TS 102 822-3-2 V1.6.1 (2010-07) 9
|
102 822-3-1
|
Digital Video Broadcasting (DVB); Broadcast and On-line Services: Search, select, and rightful use of content ("TV-Anytime"); Part 3: Metadata; Sub-part 1: Phase 1 - Metadata schemas
|
TS
|
1.13.1
|
http://www.etsi.org/deliver/etsi_ts/102800_102899/1028220301/01.13.01_60/ts_1028220301v011301p.pdf
|
The present document is one in a series of Technical Specifications produced by the TV-Anytime Forum. These documents establish the fundamental specifications for the services, systems and devices that will conform to the TV-Anytime standard, to a level of detail that is implementable for compliant products and services. As is common practice in such standardization efforts, these specifications were preceded by requirements documents which define the requirements for the TV-Anytime services, systems and devices. ETSI TS 102 822-1 [i.5] and ETSI TS 102 822-2 [3] set the context and system architecture in which the standards for Metadata, Content referencing, Bi-directional metadata and Metadata protection are to be implemented in the TV-Anytime environment. ETSI TS 102 822-1 [i.5] provides Phase 1 and Phase 2 benchmark business models against which the TV-Anytime system architecture is evaluated to ensure that the specification enable key business applications. ETSI TS 102 822-2 [3] presents the TV-Anytime System Architecture. These two documents are placed ahead of the others for their obvious introductory value. Note that these first two documents are largely informative, while the remainder of the series is normative. Although each in the series of documents is intended to stand alone, a complete and coherent sense of the TV-Anytime system standard can be gathered by reading all parts of this multi-part deliverable in numerical order. The present document deals with Metadata Phase 1 features of the TV-Anytime specification as identified in ETSI TS 102 822-1 [i.5]. The term "metadata" is used to mean descriptive data about content, such as programme title and synopsis. Such metadata are called "attractors" because they can attract a consumer to content. Attractors allow consumers to find, navigate and manage content from various sources. In addition to attractors, metadata as defined by TV-Anytime also includes information about user preferences and history. User preference information, such as favourite actors or TV shows, is included within the scope of TV-Anytime metadata to allow software agents to select content on the consumer's behalf. The formal definitions of metadata schemas should be read in conjunction with the system specification ETSI TS 102 822-2 [3] defining how they could be used in an end-to-end system. TV-Anytime only defines the metadata format for metadata that may be exchanged between various entities such as between the content provider and consumer, among consumers, or between a third-party metadata provider and the consumer. There are two sub-parts to ETSI TS 102 822-3 addressing Phase 1: • In sub-part 1, XML is the "representation format" used to define the schemas of the TV-Anytime Metadata Specification (the present document). Although XML Schema is used to define how metadata is represented in XML, it can also be used to describe equivalent, non-XML representations of the same metadata. • Sub-part 2 of the TV-Anytime Metadata Specification (ETSI TS 102 822-3-2 [4]) addresses the formatting of metadata including a recommended binary format, fragmentation, encapsulation of fragments and indexing of metadata descriptions. ETSI TS 102 822-2 [3] defines how these schemas are used in an end-to-end system. Although the transport of metadata is out of scope of TV-Anytime, requirements have been identified. Other bodies such as DVB, ATSC and ARIB will specify the appropriate transport mechanisms for their respective systems. Furthermore, the manner in which metadata is stored, accessed and used on the PDR is also out of scope of the present document. ETSI ETSI TS 102 822-3-1 V1.13.1 (2024-05) 12
|
102 822-2
|
Broadcast and On-line Services: Search, select, and rightful use of content on personal storage systems ("TV-Anytime"); Part 2: Phase 1 - System description
|
TS
|
1.4.1
|
http://www.etsi.org/deliver/etsi_ts/102800_102899/10282202/01.04.01_60/ts_10282202v010401p.pdf
|
The present document shows the system behaviour of a TV-Anytime broadcast system with an interaction channel used for consumer response. The present document contains examples of how to use the TV-Anytime specifications both from static and dynamic viewpoints, i.e. it will highlight the parties involved in the processes and show the interaction between them. The present document is a cookbook or white paper to the TS 102 822-3 sub-parts 1 [2], 2 [3], 3 [4] and 4 [5], TS 102 822-4 [6], TS 102 822-5 sub parts 1 [7] and 2 [8], TS 102 822-6 sub-parts 1 [9], 2 [10], and 3 [11], TS 102 822-7 [12], TS 102 822-8 [13] and TS 102 822-9 [14]. The present document is mainly informative and has therefore not the intention to mandate certain system implementation solutions. Preferred solutions, from a technology stand point, will be indicated to allow implementers to build more efficient systems. Annex B to this document is normative and contains requirements for delivery systems being designed by users of the TV-Anytime specification for their specific operational environment.
|
102 822-1
|
Broadcast and On-line Services: Search, select, and rightful use of content on personal storage systems ("TV-Anytime"); Part 1: Benchmark Features
|
TS
|
1.3.1
|
http://www.etsi.org/deliver/etsi_ts/102800_102899/10282201/01.03.01_60/ts_10282201v010301p.pdf
|
The present document lists and defines the TV-Anytime Phase 1 and Phase 2 evolutionary range of features which describe PDR (Personal Digital Recorder) usage models that the TV-Anytime standards facilitate. The features are supported and enabled by the specifications for Metadata (TS 102 822-3 sub-parts 1 [2], 2 [3], 3 [4] and 4 [5]), Content Referencing (TS 102 822-4 [6]), Rights Management (TS 102 822-5 sub-parts 1 [7] and 2 [8]), Bi-directional Metadata Delivery (TS 102 822-6 sub-parts 1 [999], 2 [10] and 3 [11]) and Protection (TS 102 822-7 [12]), Interchange Data Format (TS 102 822-8 [13]) and Remote Programming (TS 102 822-9 [14]). These specifications enable search, selection, acquisition and rightful use of content on local and/or remote personal storage systems from both broadcast and online services.
|
102 871-1
|
Intelligent Transport Systems (ITS); Testing; Conformance test specifications for GeoNetworking; Part 1: Test requirements and Protocol Implementation Conformance Statement (PICS) pro forma
|
TS
|
1.5.1
|
http://www.etsi.org/deliver/etsi_ts/102800_102899/10287101/01.05.01_60/ts_10287101v010501p.pdf
|
The present document provides the Protocol Implementation Conformance Statement (PICS) pro forma for Conformance test specifications for ITS GeoNetworking as defined in ETSI EN 302 636-4-1 [1] in compliance with the relevant requirements and in accordance with the relevant guidance given in ISO/IEC 9646-7 [i.2].
|
102 825-4
|
Digital Video Broadcasting (DVB); Content Protection and Copy Management (DVB-CPCM); Part 4: CPCM System Specification
|
TS
|
1.2.2
|
http://www.etsi.org/deliver/etsi_ts/102800_102899/10282504/01.02.02_60/ts_10282504v010202p.pdf
|
The present document is the specification of the Digital Video Broadcasting (DVB) Content Protection and Copy Management (CPCM) System. It contains the generic specification applicable to all deployments of CPCM. Technology-specific adaptations for content formats, storage formats, home network ecosystems and application-specific physical interfaces are contained in TS 102 825-9 [5].
|
102 822-6-3
|
Broadcast and On-line Services: Search, select, and rightful use of content on personal storage systems ("TV-Anytime"); Part 6: Delivery of metadata over a bi-directional network; Sub-part 3: Phase 2 - Exchange of Personal Profile
|
TS
|
1.6.1
|
http://www.etsi.org/deliver/etsi_ts/102800_102899/1028220603/01.06.01_60/ts_1028220603v010601p.pdf
|
The present Phase 2 document extends the scope for data exchange between users and content/service providers. The exchange of such user profiles offers a number of possible benefits to both consumers and service providers. For example, a personalized web-service in which a service provider provides the response of user's request using his consumer profile data in a secure environment, can offer the consumer a personally relevant content. TV-Anytime Phase 1 and Phase 2 offers an evolutionary range of features which describe PDR (Personal Digital Recorder) usage models that the TV-Anytime standards facilitate. The features are supported and enabled by the specifications for Metadata (TS 102 822-3-1 [3], TS 102 822-3-2 [4], TS 102 822-3-3 [5] and TS 102 822-3-4 [6]), Content Referencing (TS 102 822-4 [7]), Rights Management (TS 102 822-5-1 [8] and TS 102 822-5-2 [9]), Bi-directional Metadata Delivery (TS 102 822-6-1 [10], TS 102 822-6-2 [11] and the present document) and Protection (TS 102 822-7 [12]), Interchange Data Format (TS 102 822-8 [13]) and Remote Programming (TS 102 822-9 [14]). These specifications enable search, select, acquire and rightful use of content on local and/or remote personal storage systems from both broadcast and online services. Although TV-Anytime Phase 1 already provides a rich and varied set of metadata including user preferences and usage history to describe content and usage, the possibilities of exchanging this data were limited (TS 102 822-6-1 [10] and TS 102 822-6-2 [11]). The exchange of personal data should be designed to support: • Providers receiving data from a wide range of PDR devices from different users. • Service providers receiving detailed and comprehensive user related data. • Consumers confidence in the services (e.g. billing, tracking, monitoring). • Consumers searching, selecting and acquiring content of their direct interest such as programmes with additional audio description services for improved access, or local news, or specific travel data. • Consumers "carrying" their profiles and other personal data. • Content providers and creators understanding their audiences better. • Developing a wider range of t-Commerce (particularly PPV) and other network service business models. • Maximizing the resources of a wide range of user appliances like a set-top-box or a PDA. The present document describes mechanisms for requesting metadata from, and submitting user's personal profile data to, IP based web services. In the present document, these web services are termed "personalized services". The present document complements TS 102 822-6-1 [10], which specifies a client initiated means for requesting TV-Anytime metadata from IP-based metadata services and also provides detailed service scenarios.
|
102 822-6-2
|
Broadcast and On-line Services: Search, select, and rightful use of content on personal storage systems ("TV-Anytime"); Part 6: Delivery of metadata over a bi-directional network; Sub-part 2: Phase 1 - Service discovery
|
TS
|
1.3.1
|
http://www.etsi.org/deliver/etsi_ts/102800_102899/1028220602/01.03.01_60/ts_1028220602v010301p.pdf
|
The present document is the sixth in a series of specification documents produced by the TV-Anytime Forum. These documents establish the fundamental specifications for the services, systems and devices that will conform to the TV-Anytime standard, to a level of detail that is implementable for compliant products and services. Congruent with the structure initially defined by TV-Anytime, these specifications are parsed into three major areas: Metadata, Content Referencing, and Rights Management and Protection. Within these general areas, the following specifications have been developed : TS 102 822-3-1 [4], TS 102 822-3-2 [5], TS 102 822-3-3 [6], TS 102 822-3-4 [7] TS 102 822-4 [8], TS 102 822-5-1 [9], TS 102 822-5-2 [10], TS 102 822-6-1 [11], TS 102 822-6-2 (the present document), TS 102 822-6-3 [12], TS 102 822-7 [13], TS 102 822-8 [14] and TS 102 822-9 [15]. TS 102 822-1 [2], TS 102 822-2 [3] define the context and system architecture in which these specification shall be implemented. TS 102 822-1 [2] provides benchmark business models against which the TV-Anytime system architecture is evaluated to ensure that the specification enable key business applications. TS 102 822-2 [3] presents the TV-Anytime System Architecture. These two documents are largely informative documents, while the others in the series are normative. The scope of the present document comprises the delivery of TV-Anytime metadata and content referencing information via a bi-directional network using a PDR's return path. The requirements for this technology are outlined in TS 102 822-1 [2]. The following is an overview of the return path's use: • "The consumer can get more information about the programme from either the content provider or from a programme information service offered by a third party. This could include programme specifications (such as source, duration, format, storage location, etc.), programme schedules, commentary, critiques, liner notes from the provider or third parties, etc." • "A Return Path is a data connection from a consumer's home digital storage system (e.g. PDR) to one or more service providers. The return path gives the consumer access to interactive content, such as the Internet and interactive television. It also allows service providers to access consumer profile/preference information in order to make business decisions regarding content that is provided to the consumer." The present document describe the mechanism for describing and discovering IP-based web "metadata services" from which a client shall request metadata from, and submit user-centric data to. The present document does not address the unidirectional delivery of metadata over IP networks, or the delivery of content over IP networks.
|
102 822-6-1
|
Broadcast and On-line Services: Search, select, and rightful use of content on personal storage systems ("TV-Anytime"); Part 6: Delivery of metadata over a bi-directional network; Sub-part 1: Service and transport
|
TS
|
1.8.1
|
http://www.etsi.org/deliver/etsi_ts/102800_102899/1028220601/01.08.01_60/ts_1028220601v010801p.pdf
|
The present document is the sixth in a series of specification documents produced by the TV-Anytime Forum. These documents establish the fundamental specifications for the services, systems and devices that will conform to the TV-Anytime standard, to a level of detail that is implementable for compliant products and services. Congruent with the structure initially defined by TV-Anytime, these specifications are parsed into three major areas: Metadata, Content Referencing, and Rights Management and Protection. Within these general areas, the following specifications have been developed: TS 102 822-3-1 [8], TS 102 822-3-2 [9], TS 102 822-3-3 [10], TS 102 822-3-4 [11], TS 102 822-4 [12], TS 102 822-5-1 [13], TS 102 822-5-2 [14], TS 102 822-6-1 (the present document), TS 102 822-6-2 [15], TS 102 822-6-3 [16], TS 102 822-7 [17], TS 102 822-8 [18] and TS 102 822-9 [19]. TS 102 822-1 [6] and TS 102 822-2 [7] define the context and system architecture in which these specifications would be implemented. TS 102 822-1 [6] provides benchmark business models against which the TV-Anytime system architecture is evaluated to ensure that the specification enable key business applications. TS 102 822-2 [7]) presents the TV-Anytime System Architecture. These two documents are largely informative documents, while the others in the series are normative. The scope of the present document comprises the delivery of TV-Anytime metadata and content referencing information via a bi-directional network using a PDR's return path. The requirements for this technology are outlined in TS 102 822-1 [6]. The following is an overview of the return path's use: • "The consumer can get more information about the programme from either the content provider or from a programme information service offered by a third party. This could include programme specifications (such as source, duration, format, storage location, etc.), programme schedules, commentary, critiques, liner notes from the provider or third parties, etc." • "A Return Path is a data connection from a consumer's home digital storage system (e.g. PDR) to one or more service providers. The return path gives the consumer access to interactive content, such as the Internet and interactive television. It also allows service providers to access consumer profile/preference information in order to make business decisions regarding content that is provided to the consumer." The present document describes a client-initiated means for requesting metadata from, and submitting user-centric data to, IP based web services. In the present document, these web services are termed "metadata services". The present document also defines a means for describing and discovering such metadata services, but does not address the unidirectional delivery of metadata over IP networks, or the delivery of content over IP networks.
|
102 822-5-2
|
Broadcast and On-line Services: Search, select, and rightful use of content on personal storage systems ("TV-Anytime"); Part 5: Rights Management and Protection (RMP) Sub-part 2: RMPI binding
|
TS
|
1.2.1
|
http://www.etsi.org/deliver/etsi_ts/102800_102899/1028220502/01.02.01_60/ts_1028220502v010201p.pdf
|
Binding of Rights Management and Protection Information is a component of the TV-Anytime Rights Management and Protection system suite of specifications. When used in conjunction with the RMPI specification as components of an end-to-end RMP system, binding ensures that RMPI is appropriately applied. TVAF RMP defines Binding as the process of creating a strong association between a given set of RMPI and the content to which it applies. TVAF RMP defines Secure Binding as a Binding adequate to ensure that bound RMPI cannot be reassigned to unintended content without detection. Non-secure binding is binding which is not secure, and includes insufficient mechanisms to protect against tampering and/or modifications to RMPI. The present document specifies methods for both Secure Binding and Non-Secure Binding. Different binding methods are given for both content broadcast in the clear (e.g. free-to-air broadcast) and scrambled content (e.g. content protected by CA or DRM). Different binding methods allow for the detection of RMPI tampering and/or unauthorized modifications to the binding. RMPI under such conditions is treated as invalid by the RMP system. Compliance bodies will specify RMP system detection obligations and required behaviours when either of the conditions (tampering/modification) occur. It is mandatory that RMPI binding be verified before RMPI may be acted upon by the RMP system. All the proposed binding methods in principle enable the binding of multiple RMPI, if so required. The implementation of the present document requires the use of cryptographic technologies, however, the selection of such technologies are left to the compliance body. These include but are not limited to: ciphers, trust models, key management and watermark algorithms.
|
102 822-5-1
|
Broadcast and On-line Services: Search, select, and rightful use of content on personal storage systems ("TV-Anytime"); Part 5: Rights Management and Protection (RMP); Sub-part 1: Information for Broadcast Applications
|
TS
|
1.7.1
|
http://www.etsi.org/deliver/etsi_ts/102800_102899/1028220501/01.07.01_60/ts_1028220501v010701p.pdf
|
The present document addresses RMPI for Broadcast Applications, made up of RMPI-Micro Broadcast and RMPI-Micro. The present document is a component of the TV-Anytime Rights Management and Protection system suite of specifications. The present document provides the semantics, syntax and encoding for the usage rights, controls and permissions to be conveyed in RMPI-MB and RMPI-M.
|
102 821
|
Digital Radio Mondiale (DRM); Distribution and Communications Protocol (DCP)
|
TS
|
1.4.1
|
http://www.etsi.org/deliver/etsi_ts/102800_102899/102821/01.04.01_60/ts_102821v010401p.pdf
|
The present document gives the specification for a general purpose distribution link suitable for multicasting data to many recipients using a uni-directional communications network.
|
102 820
|
Digital Radio Mondiale (DRM); Multiplex Distribution Interface (MDI)
|
TS
|
4.1.1
|
http://www.etsi.org/deliver/etsi_ts/102800_102899/102820/04.01.01_60/ts_102820v040101p.pdf
|
The present document gives the specification for the link between a Digital Radio Mondiale (DRM) Multiplexer and a DRM Modulator.
|
102 820
|
Digital Radio Mondiale (DRM); Multiplex Distribution Interface (MDI)
|
TS
|
3.1.1
|
http://www.etsi.org/deliver/etsi_ts/102800_102899/102820/03.01.01_60/ts_102820v030101p.pdf
|
The present document gives the specification for the link between a Digital Radio Mondiale (DRM) Multiplexer and a DRM Modulator.
|
102 820
|
Digital Radio Mondiale (DRM); Multiplex Distribution Interface (MDI)
|
TS
|
1.2.1
|
http://www.etsi.org/deliver/etsi_ts/102800_102899/102820/01.02.01_60/ts_102820v010201p.pdf
|
The present document gives the specification for the link between a Digital Radio Mondiale (DRM) Multiplexer and a DRM Modulator.
|
102 819
|
Digital Video Broadcasting (DVB); Globally Executable MHP version 1.0.3 (GEM 1.0.3)
|
TS
|
1.4.1
|
http://www.etsi.org/deliver/etsi_ts/102800_102899/102819/01.04.01_60/ts_102819v010401p.pdf
|
The present document defines the GEM platform based on MHP [1]. GEM is applicable for specifications and standards based on the MHP APIs, content formats, and semantic guarantees. The present document is firstly intended to be used by entities writing terminal specifications and/or standards based on MHP. Secondly it is intended for developers of applications that use the GEM functionality and APIs. The GEM specification aims to ensure interoperability between GEM applications and different implementations of platforms supporting GEM applications. This includes interoperability across different middleware specifications, e.g. MHP, OCAP 1.0 [3], and ARIB AE [5]. Implementers should consult the publisher of specifications which reference GEM regarding conformance. NOTE: The present document defines the interfaces visible to applications. Application developers should not assume that any related interface is available unless it is specifically listed. Terminal standards or implementations may have other interfaces present. One of the primary goals of the present document is to minimize the number of divergences between MHP and GEM terminal specifications, wherever practical. Divergence is defined in clause 3.1. Where divergences are inescapable, the present document serves as a place to document and control the permitted divergences, so that they will be predictable to terminal manufacturers, broadcasters, and application authors.
|
102 818
|
Hybrid Digital Radio (DAB, DRM, RadioDNS); XML Specification for Service and Programme Information (SPI)
|
TS
|
3.5.1
|
http://www.etsi.org/deliver/etsi_ts/102800_102899/102818/03.05.01_60/ts_102818v030501p.pdf
|
The present document defines the XML schema data model for Service and Programme Information (SPI) and methods for delivery by broadcast digital radio - DAB and DRM - and IP. This data format may be used both for transmitting service and schedule data to SPI applications on devices and as the basis for exchanging information between broadcasters, service providers, network operators and content providers. In respect to the previous version of the present document, provision is added for the following: • creation date for logo objects to improve version control; • presentation language for services and schedule, programme, programme events and clarification of the use of xml:lang in the SPI.
|
102 818
|
Digital Audio Broadcasting (DAB); Digital Radio Mondiale (DRM); XML Specification for Electronic Programme Guide (EPG)
|
TS
|
1.5.1
|
http://www.etsi.org/deliver/etsi_ts/102800_102899/102818/01.05.01_60/ts_102818v010501p.pdf
|
The present document defines the XML schema data model for Service and Programme Information (SPI) and methods for delivery by broadcast digital radio - DAB and DRM - and IP. This data format may be used both for transmitting service and schedule data to SPI applications on devices and as the basis for exchanging information between broadcasters, service providers, network operators and content providers. In respect to the previous version of the present document, provision is added for the following: • creation date for logo objects to improve version control; • presentation language for services and schedule, programme, programme events and clarification of the use of xml:lang in the SPI.
|
102 817
|
Digital Video Broadcasting (DVB); Digital Recording Extension to Globally Executable Multimedia Home Platform (GEM)
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/102800_102899/102817/01.01.01_60/ts_102817v010101p.pdf
|
The present document defines a modular extension to GEM [1] which defines how the recording and playback of digital video (and audio) content is integrated with the GEM platform. The present document is firstly intended to be used by entities writing terminal specifications and/or standards that extend a GEM terminal specification with digital video (and audio) recording and playback. Secondly it is intended for developers of GEM applications that wish to use digital video (and audio) recording and playback. Implementers should consult the publisher of specifications which reference GEM regarding conformance. NOTE: The present document defines the interfaces visible to applications. Application developers should not assume that any related interface is available unless it is specifically listed. Terminal standards or implementations may have other interfaces present. One of the primary goals of the present document is to maximize the common aspects concerning the integration of digital video / audio recording between MHP and the various GEM terminal specifications.
|
102 816
|
Digital Video Broadcasting (DVB); Personal Video Recorder (PVR)/Personal Data Recorder (PDR) Extension to the Multimedia Home Platform
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/102800_102899/102816/01.01.01_60/ts_102816v010101p.pdf
|
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 playback of MHP applications that form part of the digital television content being recorded. It includes access to the metadata and content resolution mechanisms defined by TV-Anytime.
|
102 814
|
Digital Video Broadcasting (DVB); Ethernet Home Network Segment
|
TS
|
1.2.1
|
http://www.etsi.org/deliver/etsi_ts/102800_102899/102814/01.02.01_60/ts_102814v010201p.pdf
|
The present document defines a wired Home Network Segment (HNS) based on Ethernet 100BASE-T, as described in TR 102 033 [1]. The present document defines how IP traffic for DVB services will be carried over the 100BASE-T Ethernet HNS, and describes how IP QoS is mapped to the Ethernet layer. All the IP related functionality such as initial registration and configuration (including IP address assignment) of a Home Network End Device (HNED) is defined in Draft IPI 2001-071 (see Bibliography). The present document applies to interfaces IPI-1, IPI-2 and IPI-3, as defined in TR 102 033 [1]. It is not the intention to come up with a completely new standard but to refer as far as possible to existing standards. The present document should meet the existing commercial requirements as defined in CM255rev4 and DVB CM159R2 (see Bibliography).
|
102 813
|
Digital Video Broadcasting (DVB); IEEE 1394 Home Network Segment
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/102800_102899/102813/01.01.01_60/ts_102813v010101p.pdf
|
The present document covers a wired Home Network Segment based on IEEE 1394 technology, as described in the Architecture Framework document [1]. The present document concentrates on how IP traffic for DVB services will be carried over IEEE 1394 technology. This covers the encapsulation of IP packets in the IEEE 1394 Serial Bus packets. All the IP related functionality such as initial registration and configuration (including IP address assignment) are covered in other standards. In terms of the IPI Architecture document, the present document pertains to the interfaces IPI-1, IPI-2 and IPI-3. It is not the intention to come up with a completely new standard but to refer as far as possible to existing standards. The present document should meet the existing commercial requirements as defined in CM255rev4 (see Bibliography).
|
102 812
|
Digital Video Broadcasting (DVB); Multimedia Home Platform (MHP) Specification 1.1.3
|
TS
|
1.3.1
|
http://www.etsi.org/deliver/etsi_ts/102800_102899/102812/01.03.01_60/ts_102812v010301p.pdf
|
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
|
102 811
|
<empty>
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/102800_102899/102811/01.01.01_60/ts_102811v010101p.pdf
|
The present document specifies interoperability tests for ETSI GCM deployment and application descriptor standards.
|
102 809
|
Digital Video Broadcasting (DVB); Signalling and carriage of interactive applications and services in Hybrid broadcast/broadband environments
|
TS
|
1.3.1
|
http://www.etsi.org/deliver/etsi_ts/102800_102899/102809/01.03.01_60/ts_102809v010301p.pdf
|
The present document defines a framework for the signalling and carriage of interactive applications or services in broadcast and broadband networks. This framework covers: • Signalling interactive applications or services in both classical broadcast networks and broadband networks. • Distributing the files of interactive applications or services through either classical broadcast networks or broadband networks. • Synchronizing interactive applications or services to video or audio content distributed through classical broadcast networks or broadband networks. • Referencing video, audio or subtitle content distributed through classical broadcast networks or broadband networks from interactive applications or services. The present document is independent of any particular technology for interactive applications or services. It is intended to be referenced by organizations defining how interactive applications or services are to be deployed and not used as a stand-alone document in its own right. It is expected that those organizations will make a selection appropriate for their market or deployment from among the functionality defined here. The use of "shall", "should" and similar terms in the present document is intended to apply only if the particular feature is used and not to imply that the feature itself is mandatory.
|
102 804
|
Access, Terminals, Transmission and Multiplexing (ATTM); Access transmission systems on metallic access cables; Multi-Operation DSL Performance Requirements
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/102800_102899/102804/01.01.01_60/ts_102804v010101p.pdf
|
The present document specifies the European performance and functional requirements of multi-operation DSL equipment as defined in clause 3.1 and applied to Line Termination Units (such as an exchange-based or cabinet-based DSLAM) and Network Termination Units (such as a CPE) equipment. Auto-mode operation and autosensing are out of scope of the present document.
|
102 800
|
Electromagnetic compatibility and Radio spectrum Matters (ERM); Cognitive Programme Making and Special Events (C-PMSE); Protocols for spectrum access and sound quality control systems using cognitive interference mitigation techniques
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/102800_102899/102800/01.01.01_60/ts_102800v010101p.pdf
|
The present document defines the architecture and functional blocks for a C-PMSE system together with the protocols and interfaces which link them. The findings are based on the technical recommendations in TR 102 799 [i.1].
|
102 797-3
|
Intelligent Transport Systems (ITS); Communications Access for Land Mobiles (CALM); Test specifications for ITS station management (ISO 24102); Part 3: Abstract Test Suite (ATS) and partial PIXIT proforma
|
TS
|
1.2.1
|
http://www.etsi.org/deliver/etsi_ts/102700_102799/10279703/01.02.01_60/ts_10279703v010201p.pdf
|
The present document provides the Abstract Test Suite (ATS) and partial PIXIT proforma for the protocols specified in ISO 24102-4 [1], ISO 24102-5 [2] based on the related TSS & TP specification TS 102 797-2 [4] and the PICS proforma TS 102 797-1 [3] and in accordance with the relevant guidance given in ISO/IEC 9646-1 [5], ISO/IEC 9646-2 [6], ETS 300 406 [7] and EG 202 798 [i.4].
|
102 797-2
|
Intelligent Transport Systems (ITS); Communications Access for Land Mobiles (CALM); Test specifications for ITS station management (ISO 24102); Part 2: Test Suite Structure and Test Purposes (TSS & TP)
|
TS
|
1.2.1
|
http://www.etsi.org/deliver/etsi_ts/102700_102799/10279702/01.02.01_60/ts_10279702v010201p.pdf
|
The present document provides the test suite structure and test purpose specification for the ISO protocols specified in ISO 24102-4 [1] and ISO 24102-5 [2] in compliance with the relevant requirements, and in accordance with the relevant guidance given in EG 202 798 [i.1].
|
102 797-1
|
Intelligent Transport Systems (ITS); Communications Access for Land Mobiles (CALM); Test specifications for ITS station management (ISO 24102); Part 1: Protocol Implementation Conformance Statement (PICS) specification
|
TS
|
1.2.1
|
http://www.etsi.org/deliver/etsi_ts/102700_102799/10279701/01.02.01_60/ts_10279701v010201p.pdf
|
The present document provides the "Protocol Implementation Conformance Statement" (PICS) proforma for the ISO protocols specified in ISO 24102-4 [1] and ISO 24102-5 [2] in compliance with the relevant requirements, and in accordance with the relevant guidance given in ISO/IEC 9646-7 [4], ETS 300 406 [3] and EG 202 798 [i.1].
|
102 796
|
Hybrid Broadcast Broadband TV
|
TS
|
1.7.1
|
http://www.etsi.org/deliver/etsi_ts/102700_102799/102796/01.07.01_60/ts_102796v010701p.pdf
|
The present document defines a platform for signalling, transport and presentation of enhanced and interactive applications designed for running on hybrid terminals that include both a DVB compliant broadcast connection and a broadband connection to the internet.
|
102 795
|
Electromagnetic compatibility and Radio spectrum Matters (ERM); digital Private Mobile Radio (dPMR); Part 3: Requirements catalogue
|
TS
|
2.1.1
|
http://www.etsi.org/deliver/etsi_ts/102700_102799/102795/02.01.01_60/ts_102795v020101p.pdf
|
The present document is to provide a catalogue of requirements extracted from ETSI Specifications. The catalogues has been written based on the test specification framework defined in TS 102 351 [2].
|
102 795
|
Electromagnetic compatibility and Radio spectrum Matters (ERM); Testing for Modes 1, 2 and 3 of the Digital Private Mobile Radio (dPMR); Testing for Modes 1, 2 and 3 of the Digital Private Mobile Radio (dPMR); Requirements catalogue
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/102700_102799/102795/01.01.01_60/ts_102795v010101p.pdf
|
The present document is to provide a catalogue of requirements extracted from ETSI Specifications. The catalogues has been written based on the test specification framework defined in TS 102 351 [2].
|
102 792
|
Intelligent Transport Systems (ITS); Mitigation techniques to avoid interference between European CEN Dedicated Short Range Communication (CEN DSRC) equipment and Intelligent Transport Systems (ITS) operating in the 5 GHz frequency range
|
TS
|
1.2.1
|
http://www.etsi.org/deliver/etsi_ts/102700_102799/102792/01.02.01_60/ts_102792v010201p.pdf
|
Radio transmissions in the ITS-G5A/B/D frequency bands (see ETSI EN 302 571 [i.5]) interfere with CEN DSRC using the TTT band (see EC Decision 2013/752/EC [i.12]) when equipment from both systems are close to each other. This was shown in ECC Report 101 [i.1], ECC Report 228 [i.8], ETSI TR 102 960 [i.7] and ETSI TR 102 654 [i.6]. The present document specifies requirements to ensure coexistence between ITS stations using the frequency bands ITS-G5A/B/D and CEN DSRC using the TTT band. It is intended to be used as a basis for product development and for development of suitable testing procedures to prove conformance to regulations.
|
102 790-3
|
IMS Network Testing (INT); IMS specific use of Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Conformance Testing; Part 3: Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma specification
|
TS
|
2.1.1
|
http://www.etsi.org/deliver/etsi_ts/102700_102799/10279003/02.01.01_60/ts_10279003v020101p.pdf
|
The purpose of the present document is to provide the Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma for conformance tests of the IP Multimedia core network Subsystem (IMS) equipment supporting the Internet Protocol (IP) multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP) as specified in TS 124 229 [2] in compliance with the relevant requirements and in accordance with the relevant guidance given in ISO/IEC 9646-7 [5] and ETS 300 406 [6]. The content of the present document follows the requirements that have been first collected in an internal unpublished requirements catalogue and is written according to the guidelines of TS 102 351 [12], ISO/IEC 9646-1 [4] and ETS 300 406 [6]. The following test specification- and design considerations can be found in the body of the present document: • the overall test suite structure; • the testing architecture; • the test methods and port definitions; • the test configurations; • the design principles, assumptions, and used interfaces to the TTCN3 tester (System Simulator); • TTCN styles and conventions; • the partial PIXIT proforma; • the modules containing the TTCN-3 ATS. Annex A provides the Partial Implementation Extra Information for Testing (PIXIT) Proforma of the ATS. Annex B provides the Testing and Test Control Notation (TTCN-3) part of the ATS.
|
102 790-3
|
Technical Committee for IMS Network Testing (INT); Network Integration Testing; IMS specific use of Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Conformance Testing; Part 3: Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma specification
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/102700_102799/10279003/01.01.01_60/ts_10279003v010101p.pdf
|
The purpose of the present document is to provide the Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma for conformance tests of the IP Multimedia core network Subsystem (IMS) equipment supporting the Internet Protocol (IP) multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP) as specified in TS 124 229 [2] in compliance with the relevant requirements and in accordance with the relevant guidance given in ISO/IEC 9646-7 [5] and ETS 300 406 [6]. The content of the present document follows the requirements that have been first collected in an internal unpublished requirements catalogue and is written according to the guidelines of TS 102 351 [12], ISO/IEC 9646-1 [4] and ETS 300 406 [6]. The following test specification- and design considerations can be found in the body of the present document: • the overall test suite structure; • the testing architecture; • the test methods and port definitions; • the test configurations; • the design principles, assumptions, and used interfaces to the TTCN3 tester (System Simulator); • TTCN styles and conventions; • the partial PIXIT proforma; • the modules containing the TTCN-3 ATS. Annex A provides the Partial Implementation Extra Information for Testing (PIXIT) Proforma of the ATS. Annex B provides the Testing and Test Control Notation (TTCN-3) part of the ATS.
|
102 790-2
|
IMS Network Testing (INT); IMS specific use of Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Conformance Testing; Part 2: Test Suite Structure (TSS) and Test Purposes (TP)
|
TS
|
2.1.1
|
http://www.etsi.org/deliver/etsi_ts/102700_102799/10279002/02.01.01_60/ts_10279002v020101p.pdf
|
The present document provides the Test Suite Structure (TSS) and Test Purposes (TP) for the IP Multimedia core network Subsystem (IMS) equipment supporting the Internet Protocol (IP) multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP) as specified in TS 124 229 [1] in compliance with the relevant requirements and in accordance with the relevant guidance given in ISO/IEC 9646-7 [4] and ETS 300 406 [5].
|
102 790-2
|
Technical Committee for IMS Network Testing (INT); Network Integration Testing; IMS specific use of Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Conformance Testing; Part 2: Test Suite Structure (TSS) and Test Purposes (TP)
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/102700_102799/10279002/01.01.01_60/ts_10279002v010101p.pdf
|
The present document provides the Test Suite Structure (TSS) and Test Purposes (TP) for the IP Multimedia core network Subsystem (IMS) equipment supporting the Internet Protocol (IP) multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP) as specified in TS 124 229 [1] in compliance with the relevant requirements and in accordance with the relevant guidance given in ISO/IEC 9646-7 [4] and ETS 300 406 [5].
|
102 790-1
|
IMS Network Testing (INT); IMS specific use of Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Conformance Testing; Part 1: Protocol Implementation Conformance Statement (PICS)
|
TS
|
2.1.1
|
http://www.etsi.org/deliver/etsi_ts/102700_102799/10279001/02.01.01_60/ts_10279001v020101p.pdf
|
The present document provides the Protocol Implementation Conformance Statement (PICS) proforma for the IP Multimedia core network Subsystem (IMS) equipment supporting the Internet Protocol (IP) multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP) as specified in TS 124 229 [1] in compliance with the relevant requirements and in accordance with the relevant guidance given in ISO/IEC 9646-7 [4] and ETS 300 406 [5]. The supplier of a protocol implementation which is claimed to conform to TS 124 229 [1] is required to complete a copy of the PICS proforma provided in annex A of the present document and is required to provide the information necessary to identify both the supplier and the implementation.
|
102 790-1
|
Technical Committee for IMS Network Testing (INT); Network Integration Testing; IMS specific use of Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Conformance Testing; Part 1: Protocol Implementation Conformance Statement (PICS)
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/102700_102799/10279001/01.01.01_60/ts_10279001v010101p.pdf
|
The present document provides the Protocol Implementation Conformance Statement (PICS) proforma for the IP Multimedia core network Subsystem (IMS) equipment supporting the Internet Protocol (IP) multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP) as specified in TS 124 229 [1] in compliance with the relevant requirements and in accordance with the relevant guidance given in ISO/IEC 9646-7 [4] and ETS 300 406 [5]. The supplier of a protocol implementation which is claimed to conform to TS 124 229 [1] is required to complete a copy of the PICS proforma provided in annex A of the present document and is required to provide the information necessary to identify both the supplier and the implementation.
|
102 786
|
<empty>
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/102700_102799/102786/01.01.01_60/ts_102786v010101p.pdf
|
The present document defines a grid testing framework based on existing testing and validation methodologies, best practices and tools used, in IT and Telecom sectors to obtain ICT Interoperability.
|
102 778-6
|
Electronic Signatures and Infrastructures (ESI); PDF Advanced Electronic Signature Profiles; Part 6: Visual Representations of Electronic Signatures
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/102700_102799/10277806/01.01.01_60/ts_10277806v010101p.pdf
|
The present document specifies requirements and recommendations for the visual representations of advanced electronic signatures (AdES) in PDFs. This covers: a) Signature appearance: The visual representation of the human act of signing placed within a PDF document at signing time and linked to an advanced electronic signature; and b) Signature verification representation: The visual representation of the verification of an advanced electronic signature. The aim of the present document is to provide requirements and recommendations for signature appearances and the visual representation of advanced electronic signatures. This is particularly aimed to help the untrained human understanding of the signature and to further consistency between the signature appearance and the visual representations of the AdES verification in order to help human comparison. The present document includes further explanation of the two different visual representations of electronic signatures related to PDF. The present document does not cover printable forms of signature values (e.g. using barcodes) which may be verifiable from the printed document. NOTE: This use of printable forms of signature value is to be covered in a separate report.
|
102 773
|
Digital Video Broadcasting (DVB); Modulator Interface (T2-MI) for a second generation digital terrestrial television broadcasting system (DVB-T2)
|
TS
|
1.4.1
|
http://www.etsi.org/deliver/etsi_ts/102700_102799/102773/01.04.01_60/ts_102773v010401p.pdf
|
The present document defines the interface to a modulator for a second generation terrestrial television system (DVB-T2). The present document also describes a mechanism to allow the operation of over the air regenerative repeaters in SFN or non-SFN networks.
|
102 772
|
Digital Video Broadcasting (DVB); Specification of Multi-Protocol Encapsulation - inter-burst Forward Error Correction (MPE-iFEC)
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/102700_102799/102772/01.01.01_60/ts_102772v010101p.pdf
|
The present document specifies a protection scheme for the MPE sections specifically adapted for broadcasting environments supporting long duration fadings such as DVB-SH. • Clause 3 introduces the (normative) definitions, symbols and abbreviations. • Clause 4 introduces the (normative) sender operation. The present document specifies a generic framework that exhibits enough flexibility for a variety of applications, some of which are mandated for a usage in DVB-SH in the "framework mapping" in clause 6. • Clause 5 describes the (normative) carriage of MPE-IFEC sections. • Clause 6 provides (normative) syntax of Time Slice and FEC identifier descriptor. Two mapping of the generic framework are given: - One based on MPE-FEC Reed Solomon code (EN 301 192 [1], clause 9.5.1) and called "sliding RS encoding" is normative. - Another based on Raptor code (TS 102 472 [2]) and called "generalized encoding with Raptor code" is informative. • Annex A introduces (informative) prototype IFEC decoding. NOTE: The present document is intended to be ultimately added as an annex to EN 301 192 [1] but can be used independently as it is natively self-contained.
|
102 771
|
Digital Video Broadcasting (DVB); Generic Stream Encapsulation (GSE) implementation guidelines
|
TS
|
1.2.1
|
http://www.etsi.org/deliver/etsi_ts/102700_102799/102771/01.02.01_60/ts_102771v010201p.pdf
|
The present document gives guidelines for the implementation of the Generic Stream Encapsulation (GSE) Protocol. The guidelines are intended to be recommended rules, advice and good practices for the usage of the GSE specifications defined in TS 102 606 [1], in order to assist systems integrators and equipment manufacturers. As such, they aim at facilitating the efficient and reliable implementation of GSE. Outline of the present document The present document: • provides examples of system scenarios where GSE is applicable, with recommendations and advice for using specific GSE features for each scenario; • provides extensive details about the use and implementation of advanced GSE features, and proposes transmitter and receiver functional architectures; • addresses the use of the DVB signalling to locate GSE streams; • presents the physical layer requirements assumed by GSE; • specifies the use of GSE as an encapsulation protocol for physical layers. GSE was initially devised for efficiently carrying IP data over DVB-S2 Generic Stream, however it provides a generic encapsulation mechanism potentially applicable to other second generation DVB standards. As a consequence, future revisions may provide new clauses referring to other second generation DVB standards not addressed in the present document. Updates to the present document will be produced when more results from GSE compliant implementation tests and experience become available.
|
102 770
|
Digital Video Broadcasting (DVB); System Renewability Messages (SRM) in DVB Systems
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/102700_102799/102770/01.01.01_60/ts_102770v010101p.pdf
|
The present document defines mechanisms for locating and conveying System Renewability Messages (SRM) in DVB systems. Here, "System Renewability" primarily refers to the renewal of typically non-volatile information relating to security functionalities including, but not limited to Conditional Access (CA) and Content Protection and Copy Management (CPCM). This characterization does however not preclude use of these mechanisms for similar, but not security-related applications, provided that the receiver can unambiguously establish such alternate context. The syntax and semantics of SRM payloads are explicitly excluded from the present document's scope. They are defined and scoped by the originator of the messages.
|
102 760-3
|
Intelligent Transport Systems (ITS); Communications Access for Land Mobiles (CALM); Test specifications for Access Technology Support (ISO 21218); Part 3: Abstract Test Suite (ATS) and partial PIXIT proforma
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/102700_102799/10276003/01.01.01_60/ts_10276003v010101p.pdf
|
The present document provides the Abstract Test Suite (ATS) and partial PIXIT proforma for the protocols specified in ISO 21218 [1] based on the related TSS & TP specification ETSI TS 102 760-2 [3] and the PICS proforma ETSI TS 102 760-1 [2], and in accordance with the relevant guidance given in ISO/IEC 9646-1 [4], ISO/IEC 9646-2 [5], ETSI ETS 300 406 [6] and ETSI EG 202 798 [i.1].
|
102 760-2
|
Intelligent Transport Systems (ITS); Communications Access for Land Mobiles (CALM); Test specifications for Access Technology Support (ISO 21218); Part 2: Test Suite Structure and Test Purposes (TSS & TP)
|
TS
|
1.2.1
|
http://www.etsi.org/deliver/etsi_ts/102700_102799/10276002/01.02.01_60/ts_10276002v010201p.pdf
|
The present document provides the test suite structure and test purposes (TSS & TP) specification for the protocols specified in ISO 21218 [1] in compliance with the relevant requirements, and in accordance with the relevant guidance given in ETSI TS 102 760-1 [2] and in ETSI EG 202 798 [i.2]. NOTE: ISO 21218 [1] cannot be tested without being applied to a specific CALM-compliant communication interface (CI). Conformance with ISO 21218 [1] thus always is restricted to the CALM-compliant CI declared in the ICS proforma ETSI TS 102 760-1 [2].
|
102 760-1
|
Intelligent Transport Systems (ITS); Communications Access for Land Mobiles (CALM); Test specifications for Access Technology Support (ISO 21218); Part 1: Implementation Conformance Statement (ICS) proforma
|
TS
|
1.2.1
|
http://www.etsi.org/deliver/etsi_ts/102700_102799/10276001/01.02.01_60/ts_10276001v010201p.pdf
|
The present document specifies "Implementation Conformance Statement" (ICS) proformas for functionality of the ITS-S access layer service access points MI-SAP and IN-SAP and related procedures as defined in ISO 21218 [1] in accordance with the relevant guidance given in ETSI EG 202 798 [i.2]. This proforma is intended for use by suppliers of equipment which is claimed to conform to the functionality of the ITS-S access layer service access points and procedures as specified in ISO 21218 [1] in combination with a defined "Communication interface" (CI) described in ISO 21217 [i.1] . Without a CI supporting ISO 21218 [1], this proforma is not applicable. To evaluate conformance of a particular implementation, it is necessary to have a statement of which capabilities and options have been implemented for a specific CI. Such a statement is called an Implementation Conformance Statement (ICS). The present document provides proforma ICS templates, to be filled in by equipment suppliers.
|
102 759
|
Digital Radio Mondiale (DRM); AMSS Distribution Interface (ASDI)
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/102700_102799/102759/01.01.01_60/ts_102759v010101p.pdf
|
The present document gives the specification of the link between an AMSS generator and an AMSS modulator.
|
102 744-3-9
|
Satellite Earth Stations and Systems (SES); Family SL Satellite Radio Interface (Release 1); Part 3: Control Plane and User Plane Specifications; Sub-part 9: Initiation and Operation of User Plane
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/102700_102799/1027440309/01.01.01_60/ts_1027440309v010101p.pdf
|
The present document defines the necessary control plane behaviour for instantiation and initiation of the User Plane entities, and also describes the operation of the User Plane entities for the Family SL satellite radio interface between the Radio Network Controller (RNC) and the User Equipment (UE) used in the satellite network.
|
102 744-2-2
|
Satellite Earth Stations and Systems (SES); Family SL Satellite Radio Interface (Release 1); Part 2: Physical Layer Specifications; Sub-part 2: Radio Transmission and Reception
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/102700_102799/1027440202/01.01.01_60/ts_1027440202v010101p.pdf
|
The present document defines the radio reception and transmission requirements for all classes of UE that comply with the Family SL physical layer specifications as defined in ETSI TS 102 744-2-1 [11]. The Family SL radio interface operates in spectrum allocated to mobile satellite services (see ETSI TS 102 744-2-1 [11], clauses 5.1.2 and 6.1.2).
|
102 755
|
Digital Video Broadcasting (DVB); Frame structure channel coding and modulation for a second generation digital terrestrial television broadcasting system (DVB-T2)
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/102700_102799/102755/01.01.01_60/ts_102755v010101p.pdf
|
The present document describes a second generation baseline transmission system for digital terrestrial television broadcasting. It specifies the channel coding/modulation system intended for digital television services and generic data streams. The scope is as follows: • it gives a general description of the baseline system for digital terrestrial TV; • it specifies the digitally modulated signal in order to allow compatibility between pieces of equipment developed by different manufacturers. This is achieved by describing in detail the signal processing at the modulator side, while the processing at the receiver side is left open to different implementation solutions. However, it is necessary in this text to refer to certain aspects of reception.
|
102 744-3-6
|
Satellite Earth Stations and Systems (SES); Family SL Satellite Radio Interface (Release 1); Part 3: Control Plane and User Plane Specifications; Sub-part 6: Adaptation Layer Operation
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/102700_102799/1027440306/01.01.01_60/ts_1027440306v010101p.pdf
|
The present document defines the Adaptation Layer (AL) operation of the Family SL satellite radio interface between the Radio Network Controller (RNC) and the User Equipment (UE) used in the satellite network. The Adaptation Layer (AL) peer-to-peer interface is described in TS 102 744-3-5 [11].
|
102 744-3-5
|
Satellite Earth Stations and Systems (SES); Family SL Satellite Radio Interface (Release 1); Part 3: Control Plane and User Plane Specifications; Sub-part 5: Adaptation Layer Interface
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/102700_102799/1027440305/01.01.01_60/ts_1027440305v010101p.pdf
|
The present document defines the Adaptation Layer (AL) peer-to-peer interface of the Family SL satellite radio interface between the Radio Network Controller (RNC) and the User Equipment (UE) used in the satellite network.
|
102 744-3-4
|
Satellite Earth Stations and Systems (SES); Family SL Satellite Radio Interface (Release 1); Part 3: Control Plane and User Plane Specifications; Sub-part 4: Bearer Connection Layer Operation
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/102700_102799/1027440304/01.01.01_60/ts_1027440304v010101p.pdf
|
The present document defines the Bearer Connection Layer operation of the Family SL satellite radio interface between the Radio Network Controller (RNC) and the User Equipment (UE) used in the satellite network. The Bearer Connection Layer (BCn) peer-to-peer interface is described in ETSI TS 102 744-3-3 [9].
|
102 744-3-3
|
Satellite Earth Stations and Systems (SES); Family SL Satellite Radio Interface (Release 1); Part 3: Control Plane and User Plane Specifications; Sub-part 3: Bearer Connection Layer Interface
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/102700_102799/1027440303/01.01.01_60/ts_1027440303v010101p.pdf
|
The present document defines the Bearer Connection Layer (BCn) peer-to-peer interface of the Family SL satellite radio interface between the Radio Network Controller (RNC) and the User Equipment (UE) used in the satellite network.
|
102 744-3-2
|
Satellite Earth Stations and Systems (SES); Family SL Satellite Radio Interface (Release 1); Part 3: Control Plane and User Plane Specifications; Sub-part 2: Bearer Control Layer Operation
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/102700_102799/1027440302/01.01.01_60/ts_1027440302v010101p.pdf
|
The present document defines the Bearer Control Layer (BCt) operation of the Family SL satellite radio interface between the Radio Network Controller (RNC) and the User Equipment (UE) used in the satellite network. The Bearer Control Layer (BCt) peer-to-peer interface is described in ETSI TS 102 744-3-1 [8].
|
102 744-3-1
|
Satellite Earth Stations and Systems (SES); Family SL Satellite Radio Interface (Release 1); Part 3: Control Plane and User Plane Specifications; Sub-part 1: Bearer Control Layer Interface
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/102700_102799/1027440301/01.01.01_60/ts_1027440301v010101p.pdf
|
The present document defines the Bearer Control Layer (BCt) peer-to-peer interface of the Family SL satellite radio interface between the Radio Network Controller (RNC) and the User Equipment (UE) used in the satellite network.
|
102 744-3-7
|
Satellite Earth Stations and Systems (SES); Family SL Satellite Radio Interface (Release 1); Part 3: Control Plane and User Plane Specifications; Sub-part 7: NAS Layer Interface Extensions for MBMS Services
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/102700_102799/1027440307/01.01.01_60/ts_1027440307v010101p.pdf
|
The present document defines the extension to the Non-Access Stratum (NAS) Layer peer-to-peer interface (defined in ETSI TS 124 007 [1] and ETSI TS 124 008 [2]) of the Family SL satellite radio interface between the Radio Network Controller (RNC) and the User Equipment (UE) used in the satellite network, that is required in order to support MBMS services.
|
102 754
|
Electromagnetic compatibility and Radio spectrum Matters (ERM); Short Range Devices (SRD); Technical characteristics of Detect And Avoid (DAA) mitigation techniques for SRD equipment using Ultra Wideband (UWB) technology
|
TS
|
1.3.1
|
http://www.etsi.org/deliver/etsi_ts/102700_102799/102754/01.03.01_60/ts_102754v010301p.pdf
|
The present document provides the technical specifications of Detect And Avoid (DAA) mitigation techniques. These techniques are focused on the protection of active radio services. The following DAA mechanisms have been identified to protect the: • radio location services in the band 3,1 GHz to 3,4 GHz; • broadband wireless access services in the band 3,4 GHz to 3,8 GHz; • radio location services in the band 8,5 GHz to 9,0 GHz. NOTE: The DAA mitigation techniques are to some extent generic and may also be used with modifications for the protection of other radio services in the future if the technical requirements are identified. The proposed methods can be deployed by all kinds of Ultra WideBand (UWB) based applications and can be extended to other radio technologies.
|
102 751
|
Methods for Testing and Specification (MTS); Internet Protocol Testing (IPT): IPv4 to IPv6 Transitioning; Conformance Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/102700_102799/102751/01.01.01_60/ts_102751v010101p.pdf
|
The present document specifies the Abstract Test Suite (ATS) for the IPv4 to IPv6 transitioning functions of the Internet Protocol, as defined in the specifications [11] through to [14]. The ATS is based on the requirements defined in the IPv6 requirements catalogue (TS 102 599 [2]) and theIPv6 test purposes (TS 102 518 [3]) and written according to the guidelines of TS 102 514 [1], ISO/IEC 9646-2 [5] and ETS 300 406 [9]. The objective of the present document is to provide a basis for conformance tests for IPv6 equipment giving a high probability of inter-operability between different manufacturer's IPv6 equipments. Annex A provides the Tree and Tabular Combined Notation (TTCN-3) part of the ATS. Annex B provides the Partial Protocol Implementation Extra Information for Testing (PIXIT) Proforma of the ATS. Annex C provides the Protocol Conformance Test Report (PCTR) Proforma of the ATS. NOTE: Annex B provides only the PIXIT items relevant for the IPv4 to IPv6 transitioning functions. It is therefore necessary to also fill the core PIIXT item in TS 102 516 [15] to gain all PIXIT values needed to run the mobility test campaign.
|
102 747
|
Human Factors (HF); Personalization and User Profile Management; Architectural Framework
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/102700_102799/102747/01.01.01_60/ts_102747v010101p.pdf
|
The present document defines an architectural framework supporting the personalization and user profile management concepts described in EG 202 325 [i.1]. The present document addresses issues related to network requirements, functions and procedures. It also covers User Profile security and privacy issues. Capabilities provided by the architecture are: • data editing (e.g. creation, templates, update); • data storage; • synchronization; • backup; • access control respecting user preferences and legal policies; Profile solutions within the scope of the present document are: • those provided for the primary benefit of the end-user; • those which the end-user has rights to manage the profile contents; • those where the end-user has the right to have a dialogue with the information owning stakeholder. Intended readers of the present document are user profile providers, operators, service developers, service providers, device manufacturers, standards developers.
|
102 744-4-2
|
Satellite Earth Stations and Systems (SES); Family SL Satellite Radio Interface (Release 1); Part 4: Enhanced Services and Applications; Sub-part 2: Aeronautical Safety Services
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/102700_102799/1027440402/01.01.01_60/ts_1027440402v010101p.pdf
|
The present document specifies the mandatory requirements for the Aeronautical Safety Services for the Family SL satellite network.
|
102 744-4-1
|
Satellite Earth Stations and Systems (SES); Family SL Satellite Radio Interface (Release 1); Part 4: Enhanced Services and Applications; Sub-part 1: Multiple Voice Services
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/102700_102799/1027440401/01.01.01_60/ts_1027440401v010101p.pdf
|
The present document specifies the mandatory requirements for User Equipment (UE) implementing multiple voice communications via the Voice-over-IP (VoIP) service for the Family SL satellite radio interface.
|
102 757
|
Digital Video Broadcasting (DVB); Content Purchasing API
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/102700_102799/102757/01.01.01_60/ts_102757v010101p.pdf
|
The present document defines an API whose main goal is to to permit MHP or GEM applications to purchase protected content. Several other features can be supported in addition to this main goal including secure messaging and access to smart cards - including ones not related to a conditional access or content protection system. Although the package name includes "ca", the API is not specific to content protected by a content protection system, the API can also be used with content protected by a DRM system or other means. Although the package name includes "dtt", the API is neither specific to DTT nor to broadcast content, as it can also be used with IPTV delivered content . These naming conventions are kept to maintain backwards compatibility with current implementation in the market. The scope of the API includes the following features: • Obtaining lists of content available to be purchased. • Requesting the purchasing of a one or more items of content from a content protection system. • Support information about purchasing and smart card general management including, for example, giving access to purchase history, recharge history or information about the specific smart card. The API itself is not intended to be secure. All security requirements are intended to be addressed by the underlying content protection system. The present document is intentionally not a complete specification either for implementers or for application developers. It is intended to be read in conjunction with a document specific to a particular deployment of a particular content protection system. Such additional document would address issues such as the following: • How many of the API features are implemented in that particular deployment. • Which of the implemented API features are available to which applications - with or without authentication. Neither of these are addressed in the present document. It is important to emphasize that the API defined in the present document is optional and that: - No conditional access or content protection system used in an MHP deployment is obligated to use this API or any part of it. - Any MHP deployment that does choose to use this API, or any part of it, can extend it in any way. The specific extensions and the extension mechanism will be defined by an additional document specific to that deployment. Extensions should not override any functionality already defined in the API.
|
102 744-3-8
|
Satellite Earth Stations and Systems (SES); Family SL Satellite Radio Interface (Release 1); Part 3: Control Plane and User Plane Specifications; Sub-part 8: NAS Layer and User Plane Operation for MBMS Services
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/102700_102799/1027440308/01.01.01_60/ts_1027440308v010101p.pdf
|
The present document defines the operation of Multimedia Broadcast Multicast Services (MBMS) in support of efficient delivery of IP multicast traffic across the Family SL satellite radio interface. This includes extensions to the Non-Access Stratum (NAS) Layer peer-to-peer interface (defined in ETSI TS 124 007 [1] and ETSI TS 124 008 [2]) between the User Equipment (UE) and a new architectural entity defined as the Broadcast Multicast Service Node (BMSN). In addition, extensions to the IP User Plane Handler (UPH) to interpret IP multicast management and routing protocols are defined in the present document to allow automated triggering of MBMS services as defined for the Family SL satellite radio interface.
|
102 728
|
Digital Video Broadcasting (DVB); Globally Executable MHP (GEM) Specification 1.3 (including OTT and hybrid broadcast/broadband)
|
TS
|
1.2.1
|
http://www.etsi.org/deliver/etsi_ts/102700_102799/102728/01.02.01_60/ts_102728v010201p.pdf
|
The present document defines the GEM platform. GEM is applicable for specifications and standards based on the GEM APIs, content formats, and semantic guarantees. The present document is firstly intended to be used by entities writing terminal specifications and/or standards based on GEM. Secondly it is intended for developers of applications that use the GEM functionality and APIs. The GEM specification aims to ensure interoperability between GEM applications and different implementations of platforms supporting GEM applications. This includes interoperability across different middleware specifications, e.g. MHP [1], Blu-ray [13], OCAP [5], ACAP [7], ARIB [6], and the Open IPTV Procedural Application Gateway [8]. Implementers should consult the publisher of specifications which reference GEM regarding conformance. NOTE: The present document defines the interfaces visible to applications. Application developers should not assume that any related interface is available unless it is specifically listed. Terminal standards or implementations may have other interfaces present. Since the current business models for delivery of DVB services via broadband IP networks are more operator controlled than was assumed for the original GEM, the present document extends GEM with support for operator supplied applications which run all the time that the GEM environment is running. There is also the possibility that where an operator has subsidised the GEM terminal, applications from that operator may have specially privileges not available to normal applications. Clauses 1 to 14 specify the applicable technologies and technical definitions in a generic way. Clause 15 provides detailed profile definitions for the following initial profiles: • Enhanced Broadcasting; • Interactive Broadcasting; • Enhanced Packaged Media; • Interactive Packaged Media; • IPTV; • OTT, which can be extended with future additional profile definitions. Clause 16 provides a registry of constants and clause 17 describes requirements for internet access clients. One of the primary goals of the present document is to minimize the number of divergences between GEM and MHP terminal specifications, wherever practical. Divergence is defined in clause 3.1. Where divergences are inescapable, the present document serves as a place to document and control the permitted divergences, so that they will be predictable to terminal manufacturers, broadcasters, and application authors.
|
102 727
|
Digital Video Broadcasting (DVB); Multimedia Home Platform (MHP) Specification 1.2.2
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/102700_102799/102727/01.01.01_60/ts_102727v010101p.pdf
|
The present document defines the DVB solution for Multimedia Home Platforms (MHPs) that was developed to fulfil the related DVB commercial requirements MHP045. As with previous versions of the MHP specification it relies on the use of appropriate DVB specifications for digital video broadcast and associated interactive services TR 101 200 [i.4]. The MHP is applicable to all DVB defined transmission media and networks such as satellite, cable, terrestrial, microwave and TCP/IP.
|
102 726-3
|
Electromagnetic compatibility and Radio spectrum Matters (ERM); Conformance testing for Mode 1 of the digital Private Mobile Radio (dPMRTM); Part 3: Interoperability Test Suite Structure and Test Purposes (TSS&TP) specification
|
TS
|
2.2.1
|
http://www.etsi.org/deliver/etsi_ts/102700_102799/10272603/02.02.01_60/ts_10272603v020201p.pdf
|
The present document specifies the interoperability Test Purposes (TPs) for the Digital Private Mobile Radio (dPMR™) standard, ETSI TS 102 658 [1]. TPs are defined using the TPLan notation described in ETSI ES 202 553 [i.1]. Test purposes have been written based on the test specification framework described in ETSI TS 102 351 [2] and based on the methodology defined in ISO/IEC 9646-2 [3].
|
102 726-3
|
Electromagnetic compatibility and Radio spectrum Matters (ERM); Conformance testing for Mode 1 of the digital Private Mobile Radio (dPMR); Part 3: Interoperability Test Suite Structure and Test Purposes (TSS&TP) specification
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/102700_102799/10272603/01.01.01_60/ts_10272603v010101p.pdf
|
The present document specifies the interoperability Test Purposes (TPs) for the Digital Private Mobile Radio (dPMR™) standard, ETSI TS 102 658 [1]. TPs are defined using the TPLan notation described in ETSI ES 202 553 [i.1]. Test purposes have been written based on the test specification framework described in ETSI TS 102 351 [2] and based on the methodology defined in ISO/IEC 9646-2 [3].
|
102 726-2
|
Electromagnetic compatibility and Radio spectrum Matters (ERM); Conformance testing for Mode 1 of the digital Private Mobile Radio (dPMR); Part 2: Test Suite Structure and Test Purposes (TSS&TP) specification
|
TS
|
2.1.1
|
http://www.etsi.org/deliver/etsi_ts/102700_102799/10272602/02.01.01_60/ts_10272602v020101p.pdf
|
The present document specifies the conformance Test Purposes (TPs) for the Peer-to-Peer Digital Private Mobile Radio (dPMR) standard, TS 102 658 [1]. TPs are defined using the TPLan notation described in ES 202 553 [i.1]. Test purposes have been written based on the test specification framework described in TS 102 351 [2] and based on the methodology defined in ISO/IEC 9646-2 [3].
|
102 726-2
|
Electromagnetic compatibility and Radio spectrum Matters (ERM); Conformance testing for Mode 1 of the digital Private Mobile Radio (dPMR); Part 2: Test Suite Structure and Test Purposes (TSS&TP) specification
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/102700_102799/10272602/01.01.01_60/ts_10272602v010101p.pdf
|
The present document specifies the conformance Test Purposes (TPs) for the Peer-to-Peer Digital Private Mobile Radio (dPMR) standard, TS 102 658 [1]. TPs are defined using the TPLan notation described in ES 202 553 [i.1]. Test purposes have been written based on the test specification framework described in TS 102 351 [2] and based on the methodology defined in ISO/IEC 9646-2 [3].
|
102 726-1
|
Electromagnetic compatibility and Radio spectrum Matters (ERM); Conformance testing for Mode 1 of the digital Private Mobile Radio (dPMRTM); Part 1: Protocol Implementation Conformance Statement (PICS) proforma
|
TS
|
2.2.1
|
http://www.etsi.org/deliver/etsi_ts/102700_102799/10272601/02.02.01_60/ts_10272601v020201p.pdf
|
The present document provides the Protocol Implementation Conformance Statement (PICS) proforma for the ERM; Digital Private Mobile Radio using FDMA with a channel spacing of 6,25 kHz as defined in TS 102 658 [1] in compliance with the relevant requirements, and in accordance with the relevant guidance given in ISO/IEC 9646-7 [3] and ETS 300 406 [4]. The present document details in tabular form the implementation options, i.e. the optional functions additional to those which are mandatory to implement.
|
102 726-1
|
Electromagnetic compatibility and Radio spectrum Matters (ERM); Conformance testing for Mode 1 of the digital Private Mobile Radio (dPMR) Part 1: Protocol Conformance Implementation Statement (PICS) proforma
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/102700_102799/10272601/01.01.01_60/ts_10272601v010101p.pdf
|
The present document provides the Protocol Implementation Conformance Statement (PICS) proforma for the ERM; Digital Private Mobile Radio using FDMA with a channel spacing of 6,25 kHz as defined in TS 102 658 [1] in compliance with the relevant requirements, and in accordance with the relevant guidance given in ISO/IEC 9646-7 [3] and ETS 300 406 [4]. The present document details in tabular form the implementation options, i.e. the optional functions additional to those which are mandatory to implement.
|
102 724
|
Intelligent Transport Systems (ITS); Harmonized Channel Specifications for Intelligent Transport Systems operating in the 5 GHz frequency band
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/102700_102799/102724/01.01.01_60/ts_102724v010101p.pdf
|
The present document specifies details of the channel usage in the ITS G5A and ITS G5B bands including multi- channel operation support which includes • Control and service channels operation for ITS G5; • Usage of ITS G5 channels for road safety and traffic efficiency ITS applications; • ITS G5 transmit and receive policies, channel selection and configuration; • Per-traffic-stream and per-channel rate control; • Reference usage scenarios and parameters; • ITS G5 adjacent channel interference considerations. The specified parameters and procedures will be used in the definition of the cross layer DCC algorithms and management entities.
|
102 744-1-4
|
Satellite Earth Stations and Systems (SES); Family SL Satellite Radio Interface (Release 1); Part 1: General Specifications; Sub-part 4: Applicable External Specifications, Symbols and Abbreviations
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/102700_102799/1027440104/01.01.01_60/ts_1027440104v010101p.pdf
|
The present document provides a list of the 3GPP specifications and other external specifications that are referred to in the Family SL document series. The list highlights where an external specification applies and where Family SL documentation supersedes an external specification. The present document also provides a complete list of symbols and abbreviations applicable to this multi-part deliverable.
|
102 744-1-3
|
Satellite Earth Stations and Systems (SES); Family SL Satellite Radio Interface (Release 1); Part 1: General Specifications; Sub-part 3: Satellite Radio Interface Overview
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/102700_102799/1027440103/01.01.01_60/ts_1027440103v010101p.pdf
|
The present document provides an overview of the Family SL radio interface between the Radio Network Controller (RNC) and the User Equipment (UE). The Family SL radio interface operates in spectrum allocated to mobile satellite services (see ETSI TS 102 744-2-1 [i.7], clauses 5.1.2 and 6.1.2).
|
102 744-1-2
|
Satellite Earth Stations and Systems (SES); Family SL Satellite Radio Interface (Release 1); Part 1: General Specifications; Sub-part 2: System Operation Overview
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/102700_102799/1027440102/01.01.01_60/ts_1027440102v010101p.pdf
|
The present document provides an overview of the Family SL system operation, and describes fundamental UMTS elements such as mobility management, numbering and addressing, and idle mode behaviour as they apply to the Family SL satellite network. In general, these elements are the same for both terrestrial UMTS and the satellite network. Where appropriate, references to 3GPP documents are given, otherwise the text highlights the areas where the terrestrial UMTS and Family SL elements differ.
|
102 744-1-1
|
Satellite Earth Stations and Systems (SES); Family SL Satellite Radio Interface (Release 1); Part 1: General Specifications; Sub-part 1: Services and Architectures
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/102700_102799/1027440101/01.01.01_60/ts_1027440101v010101p.pdf
|
The present document describes the range of user services that are provided by the Family SL satellite radio interface and the associated satellite network. The present document also describes the satellite network architecture, the radio interface protocol architecture, and the network interfaces. The Family SL satellite radio interface is intended to form part of the satellite component of IMT-2000 systems and is based on the components and interfaces of terrestrial UMTS.
|
102 721-6
|
Satellite Earth Stations and Systems (SES); Air Interface for S-band Mobile Interactive Multimedia (S-MIM); Part 6: Protocol Specifications, System Signalling
|
TS
|
1.2.1
|
http://www.etsi.org/deliver/etsi_ts/102700_102799/10272106/01.02.01_60/ts_10272106v010201p.pdf
|
The present document specifies the S-MIM (S-band Mobile Interactive Multimedia) system in which a standardized S-band satellite mobile broadcast system is complemented by the addition of a return channel The present document is part 6 of the standard and concerns aspects of the air interface for the S-band Mobile Interactive Multimedia (S-MIM) system, and in particular it specifies the system signalling. The other parts are listed in the foreword of part 1 [2].
|
102 731
|
Intelligent Transport Systems (ITS); Security; Security Services and Architecture; Release 2
|
TS
|
2.0.0
|
http://www.etsi.org/deliver/etsi_ts/102700_102799/102731/02.00.00_60/ts_102731v020000p.pdf
|
The present document is the baseline for the definition of the Release 2 Security services and Architecture.
|
102 723-5
|
Intelligent Transport Systems (ITS); OSI cross-layer topics; Part 5: Interface between management entity and facilities layer; Release 2
|
TS
|
2.0.0
|
http://www.etsi.org/deliver/etsi_ts/102700_102799/10272305/02.00.00_60/ts_10272305v020000p.pdf
|
The present document is the baseline for the definition of the Release 2 interface between the management entity and the facilities layer.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.