hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
d704d778b6f59221d480f918cfc38ebe | 102 796 | 13.5.1 General | Terminals have buffers for normal operation, for example input and output buffers for codecs. In the case of media synchronization between two or more pieces of timed content, additional buffer capacity is needed, as one timed content will be the most laggard and the other piece(s) of timed content need to be buffered ... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 13.5.2 Media synchronization buffering cases | For any timed content one of the cases of Table 19 applies. ETSI ETSI TS 102 796 V1.5.1 (2018-09) 162 Table 19: Buffering for media synchronization of timed content in the network Case The timed content was PVR-recorded The timed content is buffered in the network The terminal has a buffer for media synchronization 1 Y... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 13.5.3 Media synchronization buffer model | The media synchronization buffer is optional. The terminal exposes the presence of a buffer for media synchronization through a non-zero value of the property minSyncBufferSize of the MediaSynchroniser embedded object (see clause 8.2.3.2.1). The following are requirements on media synchronization buffer model and size.... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 13.6 Content Identification Information service endpoint | |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 13.6.1 General | To facilitate inter-device synchronization of the presentation of media, a master terminal implements the CSS-CII service endpoint (as defined in clause 6 of ETSI TS 103 286-2 [47]). A Companion Screen application or a slave terminal subscribes to the CSS-CII service endpoint when performing inter-device synchronizatio... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 13.6.2 CSS-CII service endpoint (master terminal) | A master terminal shall implement a CSS-CII service endpoint as defined in clause 6 of ETSI TS 103 286-2 [47] at the terminal's broadband interface. The master terminal shall provide an active CSS-CII protocol service endpoint when the HbbTV® application has enabled inter-device synchronization functionality. The termi... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 13.6.3 Use of CSS-CII service endpoint (slave terminal) | When a terminal becomes a slave terminal, it shall connect to the CSS-CII service endpoint of the master terminal as indicated by the URL of the service endpoint provided as an argument to the initSlaveMediaSynchroniser() method if it has not already done so. ETSI ETSI TS 102 796 V1.5.1 (2018-09) 166 If any of the foll... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 13.7 Wall clock synchronization | |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 13.7.1 General | To facilitate inter-device synchronization of the presentation of media, a terminal has an internal Wall Clock against which the progress of the timeline of media being presented by the terminal can be measured. The master terminal responds to Wall Clock Synchronization protocol requests from slave HbbTV® terminals or ... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 13.7.2 Wall clock properties | The terminal shall have a Wall Clock as defined in clause 8.3 of ETSI TS 103 286-2 [47]. The Wall Clock of the master terminal shall be monotonic and without discontinuities. The Wall Clock should not be directly derived from any real time clock source in the master or slave terminal. NOTE 1: It is possible to derive a... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 13.7.3 WC-Server (master terminal) | When the terminal is a master terminal, it shall implement a WC-Server as defined in clause 8 of ETSI TS 103 286-2 [47]. The WC-Server shall provide the CSS-WC service endpoint on the terminal's broadband interface. The master terminal WC-Server function shall provide an active Wall Clock Synchronization service endpoi... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 13.7.4 WC-Client (slave terminal) | While a terminal is a slave terminal, or in the process of becoming a slave terminal, it shall implement a WC-Client function (as defined in clause 8 of ETSI TS 103 286-2 [47]). ETSI ETSI TS 102 796 V1.5.1 (2018-09) 168 During the process of becoming a slave terminal, the WC-Client function of the slave terminal commen... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 13.8 Timeline Synchronization service endpoint | |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 13.8.1 General | To facilitate inter-device synchronization of the presentation of media, a master terminal implements the CSS-TS service endpoint (as defined in clause 9 of ETSI TS 103 286-2 [47]). A slave terminal or Companion Screen application connects to the CSS-TS service endpoint to establish a session of the Timeline Synchroniz... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 13.8.2 CSS-TS service endpoint (master terminal) | |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 13.8.2.1 General | When the terminal is a master terminal, it shall implement an MSAS function that implements a CSS-TS service endpoint as defined in clause 9 of ETSI TS 103 286-2 [47]. The MSAS function of the master terminal shall provide the CSS-TS service endpoint on the master terminal's broadband interface. For each media object i... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 13.8.2.2 Synchronization timeline availability | As the first stage of the protocol session, the MSAS function of the master terminal awaits a setup-data message from the slave terminal or CSA. This message requests the Synchronization Timeline to be used for the remainder of the protocol session. The Synchronization Timeline defines the reference frame for contentTi... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 13.8.2.3 Frequency of control timestamp messages | The MSAS function of the master terminal shall send its first Control Timestamp within 500 ms of receiving the setup- data message and having determined the availability of the timeline. NOTE: This means that the master terminal sends the first Control Timestamp at most 500 ms after having played 2,5 seconds of the bro... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 13.8.2.4 Controlling timing of presentation | As described in clause 9 of ETSI TS 103 286-2 [47], the MSAS function of the master terminal exchanges timestamp messages with SC functions of CSAs and slave terminals to coordinate the synchronized presentation of content between the master terminal and the CSAs and slave terminals. SC functions of slave terminals and... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 13.8.3 SC function (slave terminal) | |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 13.8.3.1 General | When the terminal becomes a slave terminal, the SC function of the slave terminal shall wait until the CSS-CII messages received from the master terminal have provided: • a URL in the tsUrl property; • an entry in the timelines property; and • a presentationStatus property of "okay". The terminal shall then commence th... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 13.8.3.2 Setup-data message | The SC function of the slave terminal shall use the following values for properties in the setup-data message that it sends at the start of the protocol session: • The value of the contentIdStem property shall be the empty string. • The value of the timelineSelector property shall be the value of the timelineSelector p... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 13.8.3.3 Sending Actual, Earliest and Latest Presentation Timestamps | If the SC function of the slave terminal has sent at least one Actual, Earliest and Latest Presentation Timestamp, then the SC function of the slave terminal shall send a new Actual, Earliest and Latest Presentation Timestamp if, and only if, all of the following are true: • 500 ms has passed since the previous Actual,... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 13.8.3.4 Value of Actual, Earliest and Latest Presentation Timestamps | An Actual, Earliest and Latest Presentation Timestamp message contains an Earliest and a Latest Presentation Timestamp and can contain an Actual Presentation Timestamp. If an Actual Presentation Timestamp is included in the message then it shall consist of a point on the Synchronization Timeline (called a contentTime) ... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 13.8.3.5 Adjusting timing of presentation in response to Control Timestamps | Before the SC function of the slave terminal receives a first Control Timestamp message from the MSAS (in response to sending a setup data message), the SC function of the slave terminal has no knowledge of what time it should present content. At this stage, it shall therefore not change the playback state or adjust th... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 13.9 Trigger Events | The terminal is not required to implement the Trigger Events service endpoint as defined in clause 10 of ETSI TS 103 286-2 [47]. ETSI ETSI TS 102 796 V1.5.1 (2018-09) 175 13.10 Sequence diagrams for timeline synchronization (Informative) 13.10.1 General This clause provides a set of informational sequence diagrams to a... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 14 Companion screens | |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 14.1 Introduction | This clause introduces the methods to allow for interaction between HbbTV® and Companion Screens. Whilst primarily targeted at iOS™ and Android™ devices, the framework described here should allow Companion Screens of any type to be used. The HbbTV® terminal and the Companion Screens have to be connected to the same loc... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 14.2 Description of framework (informative) | |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 14.2.1 Supported features | This clause is written to allow for the following features: • An HbbTV® application launching a Companion Screen application. The Companion Screen application may be an HTML application running in a browser on the Companion Screen, or may be a native Companion Screen application. There is also the facility for the HbbT... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 14.2.2 Model | |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 14.2.2.1 Launching a companion screen application | Figure 31 provides an architecture for launching a CS application. Figure 31: Architecture for launching a CS application The following functions are distinguished in this architecture: • Web Browser: running the web application consists of HTML5 and associated web technologies. The application environment for the HbbT... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 14.2.2.2 Application to application communication | Figure 32 provides an architecture for application to application communication. Figure 32: Architecture for application to application communication The following functions are distinguished in this architecture. • HbbTVCSManager: HbbTVCSManager is responsible for providing service endpoints for application to applica... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 14.2.2.3 Remotely launching HbbTV® applications | Figure 33 provides an architecture for remotely launching HbbTV® applications. Figure 33: Architecture for remotely launching HbbTV® applications The following functions are distinguished in this architecture: • HbbTVCSManager: responsible for responding to discovery requests from Companion Screens and launching the Hb... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 14.3.1 Support for 'launching a CS application from an HbbTV® application' | Terminals shall, in conjunction with an application (provided by the terminal manufacturer or one of their agents) running on a Companion Screen, support the 'Launching a CS application from an HbbTV® application' feature if the terminal manufacturer (or one of their agents) provides a Companion Screen application that... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 14.3.2 The Launcher application | The protocol between the HbbTV® terminal and the Companion Screen device is not defined by the present document. Where the 'Launching a CS application from an HbbTV® application' feature is supported, a Launcher application is required to be provided and the following behaviours of the Launcher application shall be sup... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 14.4 Launching a CS application from an HbbTV® application | |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 14.4.1 CS OS identification | |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 14.4.1.1 General (informative) | A Companion Screen OS Identifier (CS OS ID) is a string containing the following information about a Companion Screen Device: 1) the identity of the Launcher application; 2) a list of app store(s) that the Launcher application is aware of; 3) an existing User Agent string representative of a browser engine on the Compa... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 14.4.1.2 Syntax and semantics | The syntax is expressed as augmented BNF as defined in Table 15 of IETF RFC 5234 [39]. ETSI ETSI TS 102 796 V1.5.1 (2018-09) 200 Table 28: Augmented BNF syntax of the Companion Screen OS Identifier string BNF syntax of the Companion Screen OS Identifier string csoid = launcher WS user_agent_string launcher = launcher_p... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 14.4.2 Payload format for Install and Launch operations | |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 14.4.2.1 Permissible Operations | There are two operation instructions that may be carried in the payload data of the launchCSapp() JS API. These are: • Install application (for Native applications only) • Launch application (for either Native or HTML applications) The format of these instructions is described in clause 14.4.2.2. Either one or two of t... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 14.4.2.2 JSON payload format | |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 14.4.2.2.1 Introduction | The payload data for the install and launch operations are carried as strings which contain JSON formatted data. The exact format of the JSON payload is described here. JSON not conforming to these rules (including empty strings) are invalid and shall cause the onCSLaunch callback to return with an error code of 4 (gen... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 14.4.2.2.2 Install operation | This Installation Operation may contain multiple sources for an installation to be sourced from, but shall include at least one source. If there are multiple sources, then each source shall contain a store name, except for the last one in the list, which may optionally contain a store name. If the last one in the list ... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 14.4.2.2.3 Launch operation | The Launch Operation shall contain either a single launch entry or two launch entries. Zero, or more than two entries are invalid. If there is a single launch entry then the type shall be either "native" or "html" as shown below. If there are two launch entries, then the first launch entry shall be of type "native", an... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 14.4.2.2.4 JSON payload schema | The JSON schema for the install and launch operations payload of the launchCSapp() function is defined as follows: { "id": "http://hbbtv.org/cs-install#", "$schema": "http://json-schema.org/draft-04/schema#", "title": "HbbTV CS Application Install", "description": "HbbTV CS Application Install Schema as defined in HbbT... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 14.4.2.2.5 Handling Special Characters in URLs (Informative) | application authors should take care to avoid the use of, or correctly escape, any special characters in URL parameters. In particular, authors should note that the parameters in any URLs are carried in JSON data defined by the schema in clause 14.4.2.2.4 and that any such JSON passed via the launchCSApp() API is expec... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 14.5 Application to application communications | |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 14.5.1 General | A terminal shall provide an application-to-application communication service as described here to enable an HbbTV® application to communicate concurrently with one or more Companion Screen applications and/or applications running on other HbbTV® terminals present on devices on the same home network as the terminal. NOT... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 14.5.2 Service endpoints provided by the terminal | The terminal shall provide two service endpoints implementing the server-side of the WebSocket protocol specification IETF RFC 6455 [40]: • The local endpoint is for connecting to by clients that are HbbTV® applications on the terminal. • The remote endpoint is for connecting to by clients that are applications on othe... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 14.5.3 Handling of new connections from clients | The terminal shall support a minimum of 10 concurrent WebSocket connections to the local service endpoint from local HbbTV® applications and, simultaneously, a minimum of 10 concurrent WebSocket connections to the remote service endpoint from other terminals or companion screen applications. The terminal shall reject r... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 14.5.4 Connection pairing | A WebSocket URL, as defined in clause 3 of IETF RFC 6455 [40], defines the host, port, security, and resource-name of a service endpoint that supports the WebSocket protocol. The terminal provides WebSocket URLs, known as the base WebSocket URLs, for each of the local and remote service endpoints. The WebSocket URL for... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 14.5.5 Paired connections | When connections from two clients enter into a state of being paired to each other, the terminal shall immediately inform both clients by sending them a Data frame of type Text (as defined by the WebSocket protocol specification clause 5.6 in IETF RFC 6455 [40]) with as Payload data the UTF-8 encoded text 'pairingcompl... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 14.6 Launching an HbbTV® application from a CS application | |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 14.6.1 Introduction | This clause introduces the methods to launch a broadcast independent HbbTV® application on an HbbTV® terminal from a Companion Screen application. It consists of the following steps: • first, the Companion Screen application discovers available DIAL servers; • then for each DIAL server, it discovers the location of its... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 14.6.2 Launching an HbbTV® application protocol | The protocol for launching an HbbTV® application from a Companion Screen application is described in this clause. The Companion Screen requests the launch of the HbbTV® application using the mechanisms defined in clause 6.2.1 of DIAL [50]. It is done by sending an HTTP POST request to the DIAL REST Service URL with the... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 14.6.3 Providing HbbTV® user agent | The Companion Screen can determine the value of the User-Agent header that is supplied by the terminal on behalf of an HbbTV® application by sending an HTTP GET request to the DIAL application Resource for HbbTV®, as described in clause 14.7.2. The HTTP response contains an <X_HbbTV_UserAgent> element which carries the... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 14.7 Discovering terminals and their service endpoints | |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 14.7.1 Introduction | In the situation where a CS application has been launched by an HbbTV® application, information regarding the location of the service endpoints exposed by the terminal may be conveyed as parameters in the launch URL, as described in clause 14.4.2.2.3. However, if the CS application has launched the HbbTV® application, ... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 14.7.2 Terminal and service endpoint discovery | HbbTV® is a DIAL [50] application registered at the DIAL registry [i.8]. The registered name for HbbTV® applications is 'HbbTV'. For terminal and service endpoint discovery, the terminal shall support DIAL [50] except that the response to an M-SEARCH request, as specified by section 5.2 of DIAL [50], may be compliant w... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 14.7.3 Discovery example (informative) | |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 14.7.3.1 DIAL Service Discovery | This is as per DIAL Service Discovery - there are no additional aspects required for HbbTV®. See the example messages B.1 to B.4 in annex B of DIAL [50]. DIAL Device Discovery Request A device on a home network initiates device discovery by performing an M-SEARCH from the SSDP protocol with the Search Target header (ST... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 14.7.3.2 DIAL Rest Service | As, from the Device Description Response example, the DIAL REST service is on an Application-URL of http://192.168.1.11:11111/apps then the following are examples of how the HbbTV® service endpoints and the User-Agent header value are discovered. Application information request A HTTP GET message is sent to 192.168.1.1... |
d704d778b6f59221d480f918cfc38ebe | 102 796 | 14.8 Cross-Origin support | The HbbTV® terminal shall allow cross-origin requests to the HbbTV® UPnP device description (for the DIAL service) and the DIAL REST Service. It shall do this by implementing the resource processing model defined in the W3C Cross-Origin Resource Sharing recommendation [42] and authorizing all HTTP requests made by a CS... |
bddccf3ce90a4e3e3383f925d1066958 | 102 795 | 1 Scope | 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]. |
bddccf3ce90a4e3e3383f925d1066958 | 102 795 | 2 References | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the reference document (including any amendments) applies. Referenced documents which ar... |
bddccf3ce90a4e3e3383f925d1066958 | 102 795 | 2.1 Normative references | The following referenced documents are necessary for the application of the present document. [1] ETSI TS 102 658 (V2.1.1): "Electromagnetic compatibility and Radio spectrum Matters (ERM); Digital Private Mobile Radio (dPMR) using FDMA with a channel spacing of 6,25 kHz". [2] ETSI TS 102 351 (V2.1.1): "Methods for Test... |
bddccf3ce90a4e3e3383f925d1066958 | 102 795 | 2.2 Informative references | The following referenced documents are not necessary for the application of the present document but they assist the user with regard to a particular subject area. [i.1] ETSI ETS 300 230: "Radio Equipment and Systems (RES); Land mobile service; Binary Interchange of Information and Signalling (BIIS) at 1 200 bit/s (BII... |
bddccf3ce90a4e3e3383f925d1066958 | 102 795 | 3 Definitions and abbreviations | |
bddccf3ce90a4e3e3383f925d1066958 | 102 795 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply: base station: two frequency duplex equipment with uplink access and downlink re-transmission conditionally mandatory: requirement that is supported by a standard conformant equipment if and only if the condition(s) stated within its re... |
bddccf3ce90a4e3e3383f925d1066958 | 102 795 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: ACK ACKnowledgment AI Air Interface ARQ Automatic Retransmission reQuest BS2 Mode 2 Repeater BS3 Mode 3 Repeater CC Colour Code CCH Control CHannel CI Call Information Cont Continuation flag CRC Cyclic Redundancy Checksum for data error detect... |
bddccf3ce90a4e3e3383f925d1066958 | 102 795 | 4 dPMR requirements catalogue | |
bddccf3ce90a4e3e3383f925d1066958 | 102 795 | 4.1 Framing | RQ_001_0401 Framing TS 102 658 [1] Clause: 4.2.2.2 Type: Mandatory Applies to: M1, M2, M3 Requirement: All transmissions are made up from 80 ms (384 bits) frames. Normal frames (not packet data) are the concatenation of: 24 bits of either FrameSync or ColourCode 72 bits of Control Channel data Followed by 4 blocks of 7... |
bddccf3ce90a4e3e3383f925d1066958 | 102 795 | 4.1.1 Addressing | |
bddccf3ce90a4e3e3383f925d1066958 | 102 795 | 4.1.1.1 All Call | RQ_001_0838 All call TS 102 490 [3] Clause: 8.2 ¶1 Type: Conditionally Optional Applies to: M1, M2 Requirement: For Voice group calls a dPMR radio may support supplementary service "Broadcast Call". Specification Text: {{Table 8.3}} Family: No Duplicates Test Purposes: TP_PMR_0838_01 (Conformance) ETSI ETSI TS 102 795 ... |
bddccf3ce90a4e3e3383f925d1066958 | 102 795 | 4.1.1.2 Dialling Plan | RQ_001_0814 Dialling Plan TS 102 658 [1] Clause: A.1.2.1.1.6 Type: Conditionally Mandatory Applies to: M1, M2, M3 Requirement: A dPMR radio complying to the Standard User Interface shall use a 7 digit addressing scheme that is encoded into the 24 bit address field as defined by the algorithm: SUM( K1 * 1464100, K2 * 14... |
bddccf3ce90a4e3e3383f925d1066958 | 102 795 | 4.1.1.3 TPID | RQ_001_0803 TPID TS 102 658 [1] Clause: 8.1, 8.2 ¶1 Type: Optional Applies to: M1, M2, M3 Requirement: A dPMR radio may support "Talking Party Identification". Specification Text: {{Table 8.1 and Table 8.2}} Family: RQ_001_0803, RQ_001_0845 Test Purposes: TP_PMR_0803_01 (Interoperability), TP_PMR_0803_02 (Interoperabil... |
bddccf3ce90a4e3e3383f925d1066958 | 102 795 | 4.1.2 Base Station framing | RQ_001_0409 Base Station framing TS 102 658 [1] Clause: 10.2.1 Type: Conditionally Mandatory Applies to: BS2 Requirement: Where a BS receives a MS to MS call request AND the MS placing the call has a valid calling station ID for that BS THEN the BS shall retransmit the call request on the downlink and shall append pres... |
bddccf3ce90a4e3e3383f925d1066958 | 102 795 | 4.1.3 Channel Access | RQ_001_1001 Channel access TS 102 658 [1] Clause: 12.1.1 Type: Mandatory Applies to: M1, M2 Requirement: A caller radio shall listen before transmit. When the received signal level has not exceeded -105 dBm for the duration of the T_ch_chk timer then the radio shall assume the channel to be free. Specification Text: Wh... |
bddccf3ce90a4e3e3383f925d1066958 | 102 795 | 4.1.3.1 OACSU | RQ_001_0840 OACSU TS 102 658 [1] Clause: 8.1 ¶1 Type: Conditionally Optional Applies to: M1, M2 Requirement: For Voice individual calls a dPMR radio may support supplementary service "Off Air Call Set Up (OACSU)". Specification Text: {{Table 8.1}} Family: No Duplicates Test Purposes: TP_PMR_0840_01 (Interoperability), ... |
bddccf3ce90a4e3e3383f925d1066958 | 102 795 | 4.1.3.2 PTT Call | RQ_001_0801 PTT Call TS 102 658 [1] Clause: 8.1 ¶1 Type: Conditionally Mandatory Applies to: M1, M2 Requirement: A dPMR radio shall support PTT calls. Specification Text: See {{tables 8.1 }} Family: No Duplicates Test Purposes: TP_PMR_0801_01 (Interoperability), TP_PMR_0801_02 (Interoperability), TP_PMR_0801_01 (Confor... |
bddccf3ce90a4e3e3383f925d1066958 | 102 795 | 4.1.4 End Frame | RQ_001_0913 End frame TS 102 490 [3] Clause: 11.6 Type: Mandatory Applies to: M1, M2, M3 Requirement: In each End frame the End Data shall be sent in duplicate. Specification Text: These 24 bits are now separated into 3 bytes. Each byte is now coded by a shortened 12,8 Hamming Code (clause 7.2) giving 3 x 12 bit blocks... |
bddccf3ce90a4e3e3383f925d1066958 | 102 795 | 4.1.5 Message Frame | RQ_001_0901 Message frames TS 102 490 [3] Clause: 11.5 Type: Mandatory Applies to: M1, M2, M3, BS2 Requirement: Each header shall have a single bit Preservation field (PM). 0 BS is idle 1 BS is reserved Specification Text: {{The next bit is the Preservation message according to clause 5.5.23. This bit will be used by B... |
bddccf3ce90a4e3e3383f925d1066958 | 102 795 | 4.1.5.1 Message Information field | RQ_001_0968 Message Information field TS 102 658 [1] Clause: 11.5 Type: Mandatory Applies to: M1, M2, M3 Requirement: Each Header shall contain the Message Information (MI) field, formed by 3 bits of data type and 8 bits of detail. The information contained in this field is depending on the Message type: Message Inform... |
bddccf3ce90a4e3e3383f925d1066958 | 102 795 | 4.1.6 Payload | |
bddccf3ce90a4e3e3383f925d1066958 | 102 795 | 4.1.6.1 Packet data | RQ_001_0808 Packet data TS 102 658 [1] Clause: 8.1, 8.2 Type: Optional Applies to: M1, M2, M3 Requirement: A dPMR radio may support Individual Short Data Message service (Type 3, Packet data) Specification Text: {{Table 8.1 and Table 8.2}}. Family: No Duplicates Test Purposes: TP_PMR_0808_01 (Interoperability), TP_PMR_... |
bddccf3ce90a4e3e3383f925d1066958 | 102 795 | 4.1.6.2 Short data | RQ_001_0501 Short data TS 102 658 [1] Clause: 5.6.1 Type: Mandatory Applies to: M1, M2 Requirement: Each appended data frame shall contain 72 bits Specification Text: {{Figure 5.9}} Family: No Duplicates Test Purposes: None ETSI ETSI TS 102 795 V2.1.1 (2011-06) 65 RQ_001_0502 Short data TS 102 658 [1] Clause: 5.6.2 Typ... |
bddccf3ce90a4e3e3383f925d1066958 | 102 795 | 4.1.6.3 T1 data | RQ_001_0807 T1 data TS 102 658 [1] Clause: 8.1, 8.2 ¶1 Type: Optional Applies to: M1, M2, M3 Requirement: A dPMR radio may support Type 1 Group Short Data Message. Specification Text: {{Table 8.1 and Table 8.2}} Family: No Duplicates Test Purposes: TP_PMR_0807_01 (Interoperability), TP_PMR_0807_02 (Interoperability), T... |
bddccf3ce90a4e3e3383f925d1066958 | 102 795 | 4.1.6.4 T2 data | RQ_001_0806 T2 data TS 102 658 [1] Clause: 8.1, 8.2 ¶1 Type: Optional Applies to: M1, M2, M3 Requirement: A dPMR radio may support type 2 Group short Data Message Specification Text: {{Table 8.1 and Table 8.2}} Family: No Duplicates Test Purposes: TP_PMR_0806_01 (Interoperability), TP_PMR_0806_02 (Interoperability), TP... |
bddccf3ce90a4e3e3383f925d1066958 | 102 795 | 4.1.6.5 Voice | |
bddccf3ce90a4e3e3383f925d1066958 | 102 795 | 4.1.6.5.1 Attached data | RQ_001_0837 Attached data TS 102 658 [1] Clause: 8.2 ¶1 Type: Conditionally Optional Applies to: M1, M2 Requirement: For Voice group calls a dPMR radio may support supplementary service "Short appended data". Specification Text: {{Table 8.1}} Family: No Duplicates Test Purposes: TP_PMR_0837_01 (Interoperability), TP_PM... |
bddccf3ce90a4e3e3383f925d1066958 | 102 795 | 4.1.6.5.2 Late entry | RQ_001_0802 Late entry TS 102 658 [1] Clause: 8.1, 8.2 ¶1 Type: Mandatory Applies to: M1, M2, M3 Requirement: A dPMR radio shall support late entry for all Voice calls Specification Text: See {{tables 8.1 and 8.2 }}in document. Family: RQ_001_0802, RQ_001_0839 Test Purposes: TP_PMR_0802_01 (Interoperability), TP_PMR_08... |
bddccf3ce90a4e3e3383f925d1066958 | 102 795 | 4.1.6.5.3 Slow user data | RQ_001_0836 Slow user data TS 102 658 [1] Clause: 8.1 ¶1 Type: Conditionally Optional Applies to: M1, M2, M3 Requirement: For Voice group calls a radio may support supplementary service "Slow user data". Specification Text: {{Table 8.1}} {{Table 8.3}} Family: No Duplicates Test Purposes: TP_PMR_0836_01 (Interoperabilit... |
bddccf3ce90a4e3e3383f925d1066958 | 102 795 | 4.1.7 Powersave | RQ_001_1101 Powersave TS 102 658 [1] Clause: 10.1.4.1 Type: Conditionally Mandatory Applies to: M1, M2 Requirement: IF powersave is supported AND repeated headers are used for powersave THEN the preamble by each header shall be fixed at 72 bits. Specification Text: {{In the case of repeated Headers for powersave use, t... |
bddccf3ce90a4e3e3383f925d1066958 | 102 795 | 4.1.8 Superframe | |
bddccf3ce90a4e3e3383f925d1066958 | 102 795 | 4.1.8.1 Traffic Channel | RQ_001_0904 Traffic Channel TS 102 490 [3] Clause: 11.1 Type: Mandatory Applies to: M1, M2, M3 Requirement: Each 2nd and 4th frame of the superframe shall start with a 24 bit field containing the Colour Code Specification Text: {{The frame is completed by prefixing with either the 24 bits of FS2 (frame numbers 002 or 1... |
bddccf3ce90a4e3e3383f925d1066958 | 102 795 | 4.1.8.2 Voice Traffic Channel | RQ_001_0930 Voice TCH TS 102 658 [1] Clause: 11.1 Type: Mandatory Applies to: M1, M2, M3 Requirement: Each frame of the voice Superframe shall end with four 72 bits long Traffic Channel (TCH) fields. Each field shall contain the 72 bit block of Forward Error corrected vocoder data. Specification Text: {{Finally the 4 x... |
7cf120a21056315aaef66bde1bab5205 | 102 792 | 1 Scope | 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... |
7cf120a21056315aaef66bde1bab5205 | 102 792 | 2 References |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.