hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
ad6d8a84f35fc219abcc0f2eea83ed6c | 103 268-1 | 5.3 Identification of the Reference points | This clause illustrates candidate reference points (RPs) where test systems can be connected in order to test conformance of oneM2M protocols (IUTs) with oneM2M base standards. Table 5.3-1: RPs for oneM2M RP Identifier RP Type oneM2M node- entity oneM2M node- entity Network RP-SAP-1 Mca ASN-AE ASN-CSE RP-SAP-2 Mca MN-A... |
ad6d8a84f35fc219abcc0f2eea83ed6c | 103 268-1 | 5.4 Development of Conformance Test Specifications | |
ad6d8a84f35fc219abcc0f2eea83ed6c | 103 268-1 | 5.4.1 Protocol Implementation Conformance Statements (PICS) | The guidance to produce ICS pro forma is provided in ETSI EG 201 058 [i.5] and no extra guidance is required for the context of Smart Appliance. ETSI ETSI TS 103 268-1 V1.1.1 (2017-04) 13 |
ad6d8a84f35fc219abcc0f2eea83ed6c | 103 268-1 | 5.4.2 Test Suite Structure & Test Purposes (TSS & TP) | |
ad6d8a84f35fc219abcc0f2eea83ed6c | 103 268-1 | 5.4.2.1 Introduction | A test purpose is a prose description of a well-defined objective of testing. Applying to conformance testing, it focuses on a single conformance requirement or a set of related conformance requirements from the base standards. Several types of presentation of the test purposes exist. These presentations are combining ... |
ad6d8a84f35fc219abcc0f2eea83ed6c | 103 268-1 | 5.4.2.2 Test Suite Structure | Defining the test suite structure consists of grouping the test purposes according to different criteria like for instance: • The functional groups and sub-groups of procedures in the base standard, from which the requirement of the test purpose is derived. • The category of test applying to the test purposes, for inst... |
ad6d8a84f35fc219abcc0f2eea83ed6c | 103 268-1 | 5.4.2.3 Test Purpose | |
ad6d8a84f35fc219abcc0f2eea83ed6c | 103 268-1 | 5.4.2.3.1 Introduction | A test purpose is an informal description of the expected test behaviour. As such it is written in prose. ETSI ETSI TS 103 268-1 V1.1.1 (2017-04) 14 In order to increase the readability of the TP, the following two recommendations should be followed: • Each TP should be presented in a table, containing two main parts: ... |
ad6d8a84f35fc219abcc0f2eea83ed6c | 103 268-1 | 5.4.2.3.2 TP identifier | The TP identifier identifies uniquely the test purposes. In order to ensure the uniqueness of the TP identifier, it follows a naming convention. The more useful and straightforward naming convention consists of using the test suite structure, to form the first part of the TP identifier. Then the final part consists of ... |
ad6d8a84f35fc219abcc0f2eea83ed6c | 103 268-1 | 5.4.2.3.3 Test objective | The test objective clearly indicates which protocol requirement is intended to be tested in the test purpose. This part eases the understanding of the TP behaviour. This also eases the identification of the requirements, which were used as a basis for the test purpose. It is recommended to limit the length of the test ... |
ad6d8a84f35fc219abcc0f2eea83ed6c | 103 268-1 | 5.4.2.3.4 Reference | In the reference row, the TP writer indicates, in which clauses of the protocol standards, the requirement are expressed. This information is critical, because it justifies the existence and the behaviour of the TP. The reference row may refer to several clauses. When the clause containing the requirement is big (for i... |
ad6d8a84f35fc219abcc0f2eea83ed6c | 103 268-1 | 5.4.2.3.5 PICS selection | The PICS selection row contains a Boolean expression, made of PICS parameters. It is recommended to use PICS acronym, which clearly identify the role of the PICS, instead of using the PICS table and row references. A mapping table is included in the TP document to link the PICS acronym with its corresponding reference ... |
ad6d8a84f35fc219abcc0f2eea83ed6c | 103 268-1 | 5.4.2.3.6 TP behaviour | First of all, the following global rules apply, when writing the behaviour description: • The behaviour description is written in an explicit, exhaustive and unambiguous manner. • The behaviour description only refers to externally observable test events (send/receive PDUs, timer, counters, etc.) or to events or states... |
ad6d8a84f35fc219abcc0f2eea83ed6c | 103 268-1 | 5.4.3 Abstract Test Suite (ATS) | |
ad6d8a84f35fc219abcc0f2eea83ed6c | 103 268-1 | 5.4.3.1 Abstract protocol tester | An abstract protocol tester presented in figure 5.4.3.1-1 is a process providing the test behaviour for testing an IUT. Thus it will emulate a peer IUT of the same layer/the same entity. This type of test architecture provides a situation of communication which is equivalent to real operation between real M2M systems. ... |
ad6d8a84f35fc219abcc0f2eea83ed6c | 103 268-1 | 5.4.3.2 TTCN-3 test architecture | |
ad6d8a84f35fc219abcc0f2eea83ed6c | 103 268-1 | 5.4.3.2.1 Introduction | Clause 5.4.3.2 illustrates how to implement the abstract test architecture presented in clause 5.4.3.1 in a functional test environment. There are many possibilities to implement this abstract test architecture using different types of programming languages and test devices. This SAP M2M testing framework uses TTCN-3 b... |
ad6d8a84f35fc219abcc0f2eea83ed6c | 103 268-1 | 5.4.3.2.2 Generic Conformance architecture | Figure 5.4.3.2.2-1 presents the functional test architecture for M2M conformance testing, applying the TTCN-3 test system specified in ETSI ES 201 873-5 [i.3]. Figure 5.4.3.2.2-1: Conformance test system architecture The "System Under Test" (SUT) contains: • The "Implementation Under Test" (IUT), i.e. the object of the... |
ad6d8a84f35fc219abcc0f2eea83ed6c | 103 268-1 | 5.4.3.2.3 Smart Appliance Conformance architecture | Figure 5.4.3.2-3-1 shows the Smart Appliances TTCN-3 test architecture design used for the Smart Appliances ATS. The Test Suite needs to interact with the System Adapter to implement the collection of TTCN-3 test cases that are intended to be used to test the Smart Appliances IUTs. The Smart Appliances TTCN-3 test case... |
ad6d8a84f35fc219abcc0f2eea83ed6c | 103 268-1 | 5.4.3.3 TTCN-3 test suite | |
ad6d8a84f35fc219abcc0f2eea83ed6c | 103 268-1 | 5.4.3.3.1 TTCN-3 Test architecture | This clause presents the global M2M TTCN-3 test architecture to be used as a basis to develop further TTCN-3 test suites. This information will be used to provide the ATS documentation as part of the TTCN-3 test specification deliverables. |
ad6d8a84f35fc219abcc0f2eea83ed6c | 103 268-1 | 5.4.3.3.2 Importing XSD definition | The ETSI 118 104 [4] uses XSD for the definition of the message types. The process for using XSD data types and values in TTCN-3 modules consists of importing the existing XSD productions. For this purpose, the TTCN-3 "import from" statement should be used, in association with the "language" statement. |
ad6d8a84f35fc219abcc0f2eea83ed6c | 103 268-1 | 5.4.3.3.3 The TTCN-3 naming conventions | TTCN-3 core language contains several types of elements with different rules of usage. Applying naming conventions aims to enable the identification of the type when using specific identifiers according to the type of element. For instance, a variable declared in a component has different scoping rules than a local var... |
ad6d8a84f35fc219abcc0f2eea83ed6c | 103 268-1 | 5.4.3.3.4 TTCN-3 code documentation | In order to document the TTCN-3 code, the SAP TTCN-3 test suite shall follow the ETSI ES 201 873-10 [i.3]. Some of the most important rules are the following: • All TTCN-3 testcase, altstep and function statements should be documented at least with @desc tag and @param for each parameter. • All TTCN-3 modulepar stateme... |
ad6d8a84f35fc219abcc0f2eea83ed6c | 103 268-1 | 5.4.3.3.5 Test cases structure | In order to keep the readability, consistency and maintainability of the TTCN-3 code, SAP test cases are implemented following a certain structure. This framework defines this structure as follows: • Local variables, contains the declaration of the variables to be used within the test case. • Test control PICS, contain... |
ad6d8a84f35fc219abcc0f2eea83ed6c | 103 268-1 | 5.4.4 Protocol Implementation eXtra Information for Testing (PIXIT) | The PICS contains base specification dependent information. To derive executable tests this is insufficient; also information about the IUT and its environment shall be supplied. Such information is called Protocol Implementation eXtra Information for Testing (PIXIT). A PIXIT pro forma identifies which ICS items are to... |
ad6d8a84f35fc219abcc0f2eea83ed6c | 103 268-1 | 6 Interoperability testing | |
ad6d8a84f35fc219abcc0f2eea83ed6c | 103 268-1 | 6.1 Introduction | Interoperability testing can demonstrate that a product will work with other like products: it proves that end-to-end functionality between (at least) two devices is as required by the standard(s) on which those devices are based. In that context, the system under test is made of the combination of different devices un... |
ad6d8a84f35fc219abcc0f2eea83ed6c | 103 268-1 | 6.2 Basic concepts for interoperability testing | |
ad6d8a84f35fc219abcc0f2eea83ed6c | 103 268-1 | 6.2.1 Overview | Figure 6.2.1-1 presents the main concepts used in the context of interoperability testing and described in clause 6. Figure 6.2.1-1: Illustration of basic concepts |
ad6d8a84f35fc219abcc0f2eea83ed6c | 103 268-1 | 6.2.2 System Under Test (SUT) | |
ad6d8a84f35fc219abcc0f2eea83ed6c | 103 268-1 | 6.2.2.1 Introduction | In the context of interoperability testing, the System Under Test (SUT) is made of a number of Devices Under Test (DUTs) coming from different suppliers. Depending on the complexity of the end-to-end system, the overall amount of DUTs under study, and the interactions among them, it might be advisable to define differe... |
ad6d8a84f35fc219abcc0f2eea83ed6c | 103 268-1 | 6.2.2.2 Devices Under Test (DUT) | In the context of Smart Appliances, a Device Under Test is a combination of software and/or hardware items which implement the functionality of Smart Appliances and interact with other DUTs via one or more reference points. ETSI ETSI TS 103 268-1 V1.1.1 (2017-04) 29 NOTE: When using Interoperability Test Specifications... |
ad6d8a84f35fc219abcc0f2eea83ed6c | 103 268-1 | 6.2.2.3 Test interfaces | The interfaces that are made available by the SUT to enable the testing are usually known as the test interfaces. These interfaces are accessed by the test drivers to trigger and verify the test behaviour, Other interfaces offered by the SUT can be used for monitoring, log analysis, etc. In the simplest case, the test ... |
ad6d8a84f35fc219abcc0f2eea83ed6c | 103 268-1 | 6.2.3 Test Environment | |
ad6d8a84f35fc219abcc0f2eea83ed6c | 103 268-1 | 6.2.3.1 Introduction | Interoperability testing involves control and observation at the functional (rather than protocol) level. The Test Environment is the combination of equipment and procedures enabling testing the interoperability of the DUTs. Entities in the test environment access the different Devices Under Test via the Test Interface... |
ad6d8a84f35fc219abcc0f2eea83ed6c | 103 268-1 | 6.2.3.2 Test Descriptions | A test description provides the detailed set of instructions (or steps) that need to be followed in order to perform a test. Most often, interoperability tests are described in terms of actions that can be performed by the user(s) of the endpoint device(s). In the case where the test is executed by a human operator, te... |
ad6d8a84f35fc219abcc0f2eea83ed6c | 103 268-1 | 6.2.3.3 Test drivers | The test driver realizes the steps specified in a test description at one specific test interface. Testing efficiency and consistency can be improved by implementing the role of the test driver via an automatic device programmed to carry out the specified test steps. This approach may require standardized test interfac... |
ad6d8a84f35fc219abcc0f2eea83ed6c | 103 268-1 | 6.3 Development of Interoperability Test Specifications | |
ad6d8a84f35fc219abcc0f2eea83ed6c | 103 268-1 | 6.3.1 Overview | The main steps involved in the process of developing an interoperability test specification are as follows: - describing a generic architecture for the System Under Test; - identifying the test architecture; - collecting requirements in the Interoperable Features Statement (IFS); - defining a structure for the Test Spe... |
ad6d8a84f35fc219abcc0f2eea83ed6c | 103 268-1 | 6.3.2 Generic SUT Architecture | A generic SUT architecture provides an abstract framework within which any specific SUT configuration should fit in. The starting point for defining a generic SUT architecture is most often the functional architecture described in the base standards, in combination with pragmatic input on how the industry and open sour... |
ad6d8a84f35fc219abcc0f2eea83ed6c | 103 268-1 | 6.3.3 Test architecture and Interfaces | A test architecture is an abstract description of logical entities as well as their interfaces and communication links involved in a test. It describes all implementation (DUTs) involved in the interoperability tests, together with the set of equipment and procedures required to enable implementations to execute the te... |
ad6d8a84f35fc219abcc0f2eea83ed6c | 103 268-1 | 6.3.4 Interoperable Functions Statement (IFS) | An "Interoperable Functions Statement" (IFS) identifies standardized functions that a DUT shall support. These functions are either mandatory, optional or conditional (depending on other functions). In addition, the IFS can be used as a pro forma by a manufacturer to identify the functions a DUT will support when inter... |
ad6d8a84f35fc219abcc0f2eea83ed6c | 103 268-1 | 6.3.5 Test Descriptions (TD) | A "Test Description" (TD) is a well detailed description of a process that pretends to test one or more functionalities of an implementation. Applying to interoperability testing, these testing objectives address the interoperable functionalities between two or more vendor implementations. In order to ensure the correc... |
5ec215e0feaa2106310732a32b9ed5fb | 103 286-3 | 1 Scope | The present document specifies the architecture and protocols for discovering TV Devices in the home that implement, interfaces defined in the other parts of this multi-part deliverable. The discovery protocol is used by the Companion Screen Application to detect TV Devices. The discovery protocol supplies the informat... |
5ec215e0feaa2106310732a32b9ed5fb | 103 286-3 | 2 References | |
5ec215e0feaa2106310732a32b9ed5fb | 103 286-3 | 2.1 Normative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the reference document (including any amendments) applies. Referenced documents which ar... |
5ec215e0feaa2106310732a32b9ed5fb | 103 286-3 | 2.2 Informative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the reference document (including any amendments) applies. NOTE: While any hyperlinks in... |
5ec215e0feaa2106310732a32b9ed5fb | 103 286-3 | 3 Definitions and abbreviations | |
5ec215e0feaa2106310732a32b9ed5fb | 103 286-3 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply: action: named subroutine NOTE: This is UPnP™ terminology. The action is based on the RPC mechanism defined in the UDA. AppInfoList: XML document which describes an application NOTE: This is UPnP™ terminology specific to the Application... |
5ec215e0feaa2106310732a32b9ed5fb | 103 286-3 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: CSA Companion Screen Application CSS Companion Screens and Streams CSS-CII Interface for Content Identification and other Information DCP Device Control Protocol DHCP Dynamic Host Configuration Protocol DDD Device Description Document GENA Gen... |
5ec215e0feaa2106310732a32b9ed5fb | 103 286-3 | 4 Overview | |
5ec215e0feaa2106310732a32b9ed5fb | 103 286-3 | 4.1 Introduction | Universal Plug and Play (UPnP™) is a well known and established protocol to find and identify UPnP™-enabled devices on the network. UPnP™ is used to convey the information to enable the CSA to discover and associate with the TV Device as depicted in Figure 1, and thereby establish communication. See also ETSI TS 103 28... |
5ec215e0feaa2106310732a32b9ed5fb | 103 286-3 | 4.4 CSS-CII interface mapping on Application Management | The CSA acts as an Application Management Control Point. This will allow the CSA to detect the TV Device that will implement the UPnP™ Device that implements the Application Management service DCP. This is depicted in Figure 4. The Application Management service in the UPnP™ Device within the physical TV Device will li... |
5ec215e0feaa2106310732a32b9ed5fb | 103 286-3 | 4.5 CSA behaviour | The determination of the CSS-CII WebSocket address from a CSA towards a TV Device is achieved by the following sequence of steps as depicted in Figure 5: 1. Finding the TV Device on the home network, by issuing an M-Search. 2. Selecting a TV Device by filtering the responses of the M-Search. 3. Downloading the DDD of t... |
cd9fe6c362149696a04ae739f7b0ea8d | 103 286-2 | 1 Scope | The present document specifies the architecture and protocols for content identification, Timeline Synchronization and Trigger Events for companion screens and streams. The present document is applicable to: • the interfaces between the TV Device and the Companion Screen Application: - interface for metadata exchange, ... |
cd9fe6c362149696a04ae739f7b0ea8d | 103 286-2 | 2 References | |
cd9fe6c362149696a04ae739f7b0ea8d | 103 286-2 | 2.1 Normative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. Referenced documents which a... |
cd9fe6c362149696a04ae739f7b0ea8d | 103 286-2 | 2.2 Informative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. NOTE: While any hyperlinks i... |
cd9fe6c362149696a04ae739f7b0ea8d | 103 286-2 | 3 Definition of terms, symbols and abbreviations | |
cd9fe6c362149696a04ae739f7b0ea8d | 103 286-2 | 3.1 Terms | For the purposes of the present document, the following terms apply: active material: material that is considered to represent an aspect of the editorial content currently showing at this point in time on the TV Device NOTE: Zero, one or more than one Material could be considered to be an Active Material at a given poi... |
cd9fe6c362149696a04ae739f7b0ea8d | 103 286-2 | 3.2 Symbols | Void. |
cd9fe6c362149696a04ae739f7b0ea8d | 103 286-2 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: 4CC 4 Character Code ABNF Augmented BNF AIT Application Information Table AMP Adaptive Media Playout API Application Programming Interface APT Actual Presentation Timestamp ASCII American Standard Code for Information Interchange AV Audio and ... |
cd9fe6c362149696a04ae739f7b0ea8d | 103 286-2 | 4 Overview | |
cd9fe6c362149696a04ae739f7b0ea8d | 103 286-2 | 4.1 Interfaces | ETSI TS 103 286-1 [i.10] describes the functional roles, relationships and general architecture within which the specific functionality of the present document operates. The present document defines the following interfaces from the general architecture: • Content Identification and other Information (CSS-CII). • Mater... |
cd9fe6c362149696a04ae739f7b0ea8d | 103 286-2 | 4.2.1 General | For a Companion Screen Application (CSA) to be able to present Timed Content synchronized with a TV Device, information needs to flow between the TV Device and the CSA and between the CSA and supporting services on the Internet. The present document assumes that the TV Device only presents a single piece of content at ... |
cd9fe6c362149696a04ae739f7b0ea8d | 103 286-2 | 4.2.2 Media synchronization architecture | Figure 4.2.2.1 illustrates a generic architecture for synchronization of media streams, based on ETSI TS 182 027 [i.1]. Clause 4.2.3 describes how this generic architecture maps to the Timeline Synchronization aspect of the companion synchronization architecture already described. Figure 4.2.2.1: Generic architecture f... |
cd9fe6c362149696a04ae739f7b0ea8d | 103 286-2 | 4.2.4 Simplified scenario for the TV Device | The present document identifies a simplified scenario where CSAs receive their Timed Content at least as early as the TV Device receives its Timed Content (such as a broadcast). As a consequence, the TV Device is not required to buffer and delay the playout of its Timed Content. Also as a consequence, the TV Device is ... |
cd9fe6c362149696a04ae739f7b0ea8d | 103 286-2 | 4.3 Procedures | |
cd9fe6c362149696a04ae739f7b0ea8d | 103 286-2 | 4.3.1 Introduction | The following clauses describe the main procedures relating to the interfaces defined within the present document. The data model and data formats used in these procedures are defined in clause 5 and the underlying protocol details of each interface are then given in clauses 6 to 10. Clause 4.3.2 describes the procedur... |
cd9fe6c362149696a04ae739f7b0ea8d | 103 286-2 | 4.3.2 Content Identification and other Information (CSS-CII) | This clause is about the Companion Screen Application continuously obtaining Content Identification and other Information (CII) related to the content being presented by the TV Device. Figure 4.3.2.1 shows the procedures for obtaining the Content Identification and other Information. It is assumed that the discovery, p... |
cd9fe6c362149696a04ae739f7b0ea8d | 103 286-2 | 4.3.3 Material Resolution Service (CSS-MRS) | Figure 4.3.3.1 shows the procedures for Material resolution. It is assumed that the Companion Screen Application has obtained the Content Identifier and the location of the CSS-MRS interface service endpoint via the procedures of clause 4.3.2 or by some other means outside the scope of the present document. Figure 4.3.... |
cd9fe6c362149696a04ae739f7b0ea8d | 103 286-2 | 4.3.4 Wall Clock (CSS-WC) | Wall Clock synchronization synchronizes the Wall Clock at the Companion Device to the Wall Clock at the TV Device. Figure 4.3.4.1 illustrates the procedures for Wall Clock synchronization via the CSS-WC interface. It is assumed that the CSA has obtained the location of this interface's service endpoint via the procedur... |
cd9fe6c362149696a04ae739f7b0ea8d | 103 286-2 | 4.3.5 Timeline Synchronization (CSS-TS) | Timeline Synchronization synchronizes the presentation of Timed Content between multiple SCs, coordinated by the MSAS. Figure 4.3.5.1 shows the procedures for Timeline Synchronization via the CSS-TS interface. It is assumed that the CSA has obtained the location of this interface's service endpoint via the procedures o... |
cd9fe6c362149696a04ae739f7b0ea8d | 103 286-2 | 4.3.6 Trigger Events interface (CSS-TE) | This clause is about the Companion Screen Application continuously obtaining Trigger Events related to the content being presented by the TV Device via the CSS-TE interface. Figure 4.3.6.1 shows the procedures for obtaining the Trigger Events. It is assumed that the CSA has obtained the URL for this interface service e... |
cd9fe6c362149696a04ae739f7b0ea8d | 103 286-2 | 5 Data model | |
cd9fe6c362149696a04ae739f7b0ea8d | 103 286-2 | 5.1 Data model introduction | Clause 5 details the information conveyed in messages across the interfaces between TV Device and CSA and between MRS and CSA. It describes the formats, models and semantics and their representation in JSON as messages that are conveyed. The procedures that give rise to the exchange of these messages are detailed in cl... |
cd9fe6c362149696a04ae739f7b0ea8d | 103 286-2 | 5.2 Content Identification | |
cd9fe6c362149696a04ae739f7b0ea8d | 103 286-2 | 5.2.1 General | The Content Identifier (CI) is a composite identifier that serves to unambiguously identify content to the resolution of an individual programme or presentation. The CI is derived from information that identifies the delivery stream and information contained within it. The format of a CI is a URI [1] with restrictions ... |
cd9fe6c362149696a04ae739f7b0ea8d | 103 286-2 | 5.2.2 Content Identifier stem | A Content Identifier stem (CI stem) describes a set of CIs. A CI stem is a string representing the first n characters of any CI that is in the set. Given a CI stem string that is n characters long, then a CI is considered to match the CI stem if the first n characters of the CI match the CI stem string in a case sensit... |
cd9fe6c362149696a04ae739f7b0ea8d | 103 286-2 | 5.2.3 DVB Broadcast and IPTV services | |
cd9fe6c362149696a04ae739f7b0ea8d | 103 286-2 | 5.2.3.1 General | For DVB services with associated DVB Service Information (SI) as defined in ETSI EN 300 468 [13], the CI shall unambiguously and globally identify up to the level of detail denoted by a DVB event. The CI may also carry a TV-Anytime CRID relating to that event, if one is present in the SI, and additional ancillary data ... |
cd9fe6c362149696a04ae739f7b0ea8d | 103 286-2 | 5.2.3.2 Net path for DVB broadcast services | The net path of the CI for a DVB broadcast service shall comprise a pair of forward slashes "//" followed by the original network id, a full stop "." character, transport stream id, a full stop "." character and the service id: "//" original-network-id "." transport-stream-id "." service-id ETSI ETSI TS 103 286-2 V1.3.... |
cd9fe6c362149696a04ae739f7b0ea8d | 103 286-2 | 5.2.3.3 Net path for DVB IPTV services | Where original network id, transport stream id and service id are known by the receiver the dvb-net-path part of the CI for an IPTV service shall be formatted as defined for broadcast services in clause 5.2.3.2. If this is not possible, then net path of the CI for a DVB IPTV service shall be a textual service identifie... |
cd9fe6c362149696a04ae739f7b0ea8d | 103 286-2 | 5.2.3.4 Event Constraint | The event constraint conveys the event-id, a TVA_id (if one is exists), and a time constraint describing the UTC start time and duration from the start_time and duration fields for this event (coming from EIT present/following actual): ";" event-id [ ";" tva-id ] "~" time-constraint If there is EIT present in the DVB S... |
cd9fe6c362149696a04ae739f7b0ea8d | 103 286-2 | 5.2.3.5 Query | The query part of the CI, if present, shall be prefixed by a question mark "?" character followed by one or more key-value pairs, separated by ampersand "&" characters: "?" key-value-pair *("&" key "=" value) The query part shall be present if there is one or more key-value pair to convey. If there are to be no key-val... |
cd9fe6c362149696a04ae739f7b0ea8d | 103 286-2 | 5.2.3.6 Progressive build-up of CIs for DVB Broadcast and IPTV services | |
cd9fe6c362149696a04ae739f7b0ea8d | 103 286-2 | 5.2.3.6.1 Common | The TV Device may emit a sequence of zero or more "partial" CIs as the TV Device progressively acquires the signalling from which the CI is derived. Once the TV Device has acquired all of the signalling contributing to the CI or determined that the signalling is not present then the TV Device shall emit a "final" CI. T... |
cd9fe6c362149696a04ae739f7b0ea8d | 103 286-2 | 5.2.3.6.2 DVB Broadcast systems | Forms A, B and C are "partial" CIs. These are allowed transient states when some of signalling has not yet been acquired by the TV Device (or are not yet known to be absent). Form D is the normal "final" and steady state for the CI once all required signalling has been acquired (or has been determined to be absent). In... |
cd9fe6c362149696a04ae739f7b0ea8d | 103 286-2 | 5.2.3.6.3 DVB IPTV systems | DVB IPTV systems follow the rules for DVB broadcast systems with the following allowed variants: 1) If the IPTV system does not carry EIT information and the CRID of the current event is not known to the TV Device by some other means then event information in the CI is not available. If additionally the optional ciAnci... |
cd9fe6c362149696a04ae739f7b0ea8d | 103 286-2 | 5.2.4 DVB DASH services | DVB services may be delivered in an ISOBMFF format using the MPEG DASH specification [16]. As this delivery format does not include the same signalling information as a DVB Broadcast or IPTV service, it is not possible to generate a CI URI according to the rules set out in clause 5.2.3. In this case, the CI URI shall c... |
cd9fe6c362149696a04ae739f7b0ea8d | 103 286-2 | 5.2.5 Other types of service | For Timed Content that is not delivered as any of the other types of service defined in the previous sub clauses of clause 5.2, the URI used as the CI: • should still comply with the general requirements defined in clause 5.2.1; • and shall not use the URI scheme identifier "dvb" unless it is a DVB defined system for w... |
cd9fe6c362149696a04ae739f7b0ea8d | 103 286-2 | 5.3 Timelines | |
cd9fe6c362149696a04ae739f7b0ea8d | 103 286-2 | 5.3.1 General | A Timeline is a linear scale against which time can be measured for a particular system. Examples of such systems include: • a clock, whose tick count can be measured; • or a broadcast or streamed media system (for audio and/or video) where values of time correspond to particular moments in the media and are either sig... |
cd9fe6c362149696a04ae739f7b0ea8d | 103 286-2 | 5.3.2 Tick rate and accuracy properties | A Timeline is a linear scale against which time can be measured for a particular stream or content item (such as progress of a broadcast or position within a content item). A Timeline has properties that characterize it: • A Timeline has a scale that defines the rate of ticks as numbers of ticks per second. • A Timelin... |
cd9fe6c362149696a04ae739f7b0ea8d | 103 286-2 | 5.3.3 Sources of Timelines and the Timeline Selector | Different types of broadcast services and other Timed Content use different types of signalling mechanism to convey Timelines associated with the progress of presentation of the Timed Content. Some types of Timeline are signalled in a way that is intrinsic to the Timed Content, such as PTS in MPEG TS and Composition Ti... |
cd9fe6c362149696a04ae739f7b0ea8d | 103 286-2 | 5.3.4 MPEG-TS PTS: Presentation Time Stamp | If PTS is to be used as a Timeline, then the Time Value is the value of PTS (as defined in [6]) of the media stream being presented to the user. The unitsPerTick of the timeline shall be 1 and the unitsPerSecond shall be 90 000, corresponding to the tick rate of clock underpinning PTS. When PTS values wrap then the Tim... |
cd9fe6c362149696a04ae739f7b0ea8d | 103 286-2 | 5.3.5 ISOBMFF: composition time | Where media is provided in an ISOBMFF [7] encapsulation, the composition time may be used as the Time Value, in a manner analogous to the use of the PTS field of the PES packet header, as described in clause 5.3.4. NOTE 1: The composition time is derived from the decode time through the addition of a delta to the decod... |
cd9fe6c362149696a04ae739f7b0ea8d | 103 286-2 | 5.3.6 TS Adaptation Packet | Clause 11 defines methods by which an extrinsic Timeline can be carried in a ISO/IEC 13818-1 [6] transport stream packet's adaptation layer. The Time Value conveyed for the Timeline applies to the first access unit that follows the relevant adaptation layer packet, which may be in the same packet. Time Values for the T... |
cd9fe6c362149696a04ae739f7b0ea8d | 103 286-2 | 5.3.7 MPEG DASH: Period relative Timeline |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.